-
Notifications
You must be signed in to change notification settings - Fork 377
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
Add off-chain settlement period negotiation #864
Comments
#43 proposal for the off-chain settlement period:
|
I see the current max as:
|
I think the idea makes sense. We have to balance the cost of extra steps against the possible channel-opening attacks. Maybe we can wait till we see those attacks. |
We don't have variable settle timeouts since raiden-network/raiden-contracts#1550. |
Problem Definition
The choice for the settlement period is unilateral, it's chosen by the node opening the channel. Ideally the value chosen is good enough for both nodes, and the channel is used normally.
A problem arises when the creator uses a settlement period too small. The channel creator rationale is to reduce the waiting time required to withdraw, if the period is lower than the required reveal timeout by the partner, it will inadvertently create an unusable channel, since the counterparty will just ignore the channel considering the settlement period unsafe.
Solution
This may be fixed on-chain, allowing the nodes to increase settlement period while the channel is opened, the drawback is the additional transaction required (note that it may still be useful to support this operation to extend the maximum number of possible hops in a mediation path).
Additionally this may be done off-chain, exchanging setup configuration among the nodes prior to the channel instantiation.
Tasklist
The text was updated successfully, but these errors were encountered: