-
Notifications
You must be signed in to change notification settings - Fork 379
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
Allow a channel re-open or a new channel to be created after a close #93
Comments
Should this happen right after |
I think so, the users will need to wait for |
Also clean up the BC when a channel is settled by calling suicide |
If we're planning on making changes to the messages anyway, we might as well add |
I'm strongly against adding another field to the message (making it longer) unless necessary. There are two alternative ways of solving the problem:
I'm in favor of 2) |
I agree 2) is the best solution. I will however need to change the messages to change the length of the |
Increasing the Why not go with option 1? |
Valid point. If we try to avoid increasing the size of the messages, then it makes more sense to go with option 1. |
how is 8 bytes not enough? 4bytes for all possible block offsets during the next 100 years and 4 billion transfers during the lifetime of the channels sounds good to me. |
my assumption would be that hashing in the address of the contract might be more changes to the code base. but no strong preferences. |
This issue is very close to being done. PR will be submitted tomorrow. |
To enforce version including matrix-org/matrix-python-sdk#236 from @pcppcp
Remove the channel address from the manager once the channel is settled is a possible solution, this allows a new contract to be created.
The text was updated successfully, but these errors were encountered: