Hi guys, while working on our state channel application we face the following scenario:
Application is under base-aepp. User A initiates a transfer update from B to A, previously arranged. When the update is sent by A, the user B is asked by the base-aepp to confirm the update by signing it. At this point, user B decides to change his mind and cancels the transaction.
Now, the channel becomes unusable (no messages can be received or sent); we assume in the “awaiting_signing” state for the duration of the timeout which is 500000 ms by default.
a. Is there a proper way to reject the update which does not involve any timeout? (in both scenarios, standalone nodejs application and base-aepp hosted).
b. Is it possible that if a channel is in the mentioned timeout (awaiting for signing), and ONE of the endpoints disconnects and connects back (no reconnection) the new opened channel will be in the same state? (perhaps reusing the same channel)
Thanks in advance.