-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lower transfer expiration for dApp #2409
Comments
This comment has been minimized.
This comment has been minimized.
taleldayekh
added
the
Ready 🎬
Issues which are ready to be pulled into the iteration
label
Dec 4, 2020
I read the code and tested it manually: The PC accepts mediations up until the reveal timeout, so no action on the python side is necessary. |
palango
added a commit
that referenced
this issue
Dec 10, 2020
palango
added a commit
that referenced
this issue
Dec 10, 2020
palango
added a commit
that referenced
this issue
Dec 10, 2020
palango
added a commit
that referenced
this issue
Dec 10, 2020
palango
added a commit
that referenced
this issue
Dec 16, 2020
palango
added a commit
that referenced
this issue
Dec 16, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In https://github.com/raiden-network/team/issues/894 and https://github.com/raiden-network/team/issues/891 we made the case for a shorter time between receiving a secret and the on-chain transaction in case we don't receive an unlock.
A decision has been made, and we need to implement it for the dApp (and possibly the CLI).
The text was updated successfully, but these errors were encountered: