We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Because then the return value can be used as **balance_proof instead of *balance_proof. That plays more nicely with the kwarg usage.
**balance_proof
*balance_proof
The text was updated successfully, but these errors were encountered:
See #1150 (comment) for an example.
Sorry, something went wrong.
This approach does not work in a straightforward way. It's unclear how to name the signature.
closeChannel() wants
closeChannel()
bytes memory non_closing_signature,
while
create_balance_proof_countersignature() wants
create_balance_proof_countersignature()
original_signature: bytes,
non_closing_signature
original_signature
I think, for now, option 2 is the most reasonable.
#1272 fixed this.
pirapira
No branches or pull requests
Because then the return value can be used as
**balance_proof
instead of*balance_proof
. That plays more nicely with the kwarg usage.The text was updated successfully, but these errors were encountered: