Add "import Locked Transfer"
Description
Users should be able to create Locked transfers outside of the Raiden SDK and just provide the SDK with the already signed locked transfer. This function should return either a notification that the secret was requested by the receiver or a timeout
Acceptance criteria
- Implement a function that takes a locked transfer and sends it.
Remarks
I'm not sure if waiting for the "reveal secret" request should be done in this function or if this function should just be executed and we implement a different function that returns if a "reveal secret" was requested.
This is quite simple in our side, but has some pitfalls we (and specially the user) need to be careful with: both the composition and signing of the LockedTransfer/balance proof happens inside a special epic which serializes all changes to the internal channel state/balance proof, as signing is an asynchronous operation which needs to be strictly performed in a thread-safe run path. We can provide actions and methods for receiving this message and using it, but it'll also need to be in this context, and validated, and if validation fail (e.g. a message was processed in the meantime which incremented the nonce), we'll need to reject the action/state change.
@eorituz Is this still important to you?