[eth] Designated Funding timeout #5
Labels
Comments
RmbRT
referenced
this issue
in hyperledger-labs/go-perun
Feb 8, 2022
The adjudicator test has a funding timeout of one challenge duration (measured in blocks), but the challenge duration was in the range [0, 3600). Now, it is generated in the range[200, 3600). Issue #239 (adding a designated funding timeout parameter) would solve this problem in a cleaner way, however, the implementation concept is still unclear. Signed-off-by: Steffen Rattay <[email protected]>
RmbRT
referenced
this issue
in hyperledger-labs/go-perun
Feb 9, 2022
The adjudicator test has a funding timeout of one challenge duration (measured in blocks), but the challenge duration was in the range [0, 3600). Now, it is generated in the range[200, 3600). Issue #239 (adding a designated funding timeout parameter) would solve this problem in a cleaner way, however, the implementation concept is still unclear. Signed-off-by: Steffen Rattay <[email protected]>
RmbRT
referenced
this issue
in hyperledger-labs/go-perun
Feb 9, 2022
The adjudicator test has a funding timeout of one challenge duration (measured in blocks), but the challenge duration was in the range [0, 3600). Now, it is generated in the range[200, 3600). Issue #239 (adding a designated funding timeout parameter) would solve this problem in a cleaner way, however, the implementation concept is still unclear. Signed-off-by: Steffen Rattay <[email protected]>
RmbRT
referenced
this issue
in hyperledger-labs/go-perun
Feb 9, 2022
The adjudicator test has a funding timeout of one challenge duration (measured in blocks), but the challenge duration was in the range [0, 3600). Now, it is generated in the range[200, 3600). Issue #239 (adding a designated funding timeout parameter) would solve this problem in a cleaner way, however, the implementation concept is still unclear. Signed-off-by: Steffen Rattay <[email protected]>
RmbRT
referenced
this issue
in hyperledger-labs/go-perun
Feb 9, 2022
The adjudicator test has a funding timeout of one challenge duration (measured in blocks), but the challenge duration was in the range [0, 3600). Now, it is generated in the range[200, 3600). Issue #239 (adding a designated funding timeout parameter) would solve this problem in a cleaner way, however, the implementation concept is still unclear. Signed-off-by: Steffen Rattay <[email protected]>
matthiasgeihs
referenced
this issue
in hyperledger-labs/go-perun
Feb 9, 2022
The adjudicator test has a funding timeout of one challenge duration (measured in blocks), but the challenge duration was in the range [0, 3600). Now, it is generated in the range[200, 3600). Issue #239 (adding a designated funding timeout parameter) would solve this problem in a cleaner way, however, the implementation concept is still unclear. Signed-off-by: Steffen Rattay <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Location
[backend/eth/channel] Funder.Fund:135
Problem
The Ethereum Funder uses the
ChallengeDurationas funding timeout which is just a "best effort" solution.A problem arises in honest tests where the funding times out too quickly when
ChallengeDuration=1is used.Concrete: The HLL talk example code has this problem.
Proposal
The user should be able to set a designated funding timeout.
Just adding an option to the
client.Proposefunction would not be enough since the receiver of the proposal would need to be able to set his timeout as well.The solution that i had in mind does not seem to work, so i will leave the concept open for later.
The text was updated successfully, but these errors were encountered: