SIG_ALL: extent aggregated message to secret + C for inputs and amount + B_ for outputs #302
No reviewers
Labels
No labels
breaking change
bug
documentation
enhancement
needs discussion
needs implementation
new nut
ready
wallet-only
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo-admin/nuts!302
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-nut11-sigall-msg-aggregation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The aggregation message now contains
secret+Cfor each input and the keysetid+amount+B_of each output in the transaction.todo:
fix test vectors
nutshell: https://github.com/cashubtc/nutshell/pull/811
cdk: https://github.com/cashubtc/cdk/pull/1212
nutmix:
cashu-ts: https://github.com/cashubtc/cashu-ts/issues/386
@ -126,15 +126,15 @@ The message to be signed depends on the type of transaction containing an inputThe
idhere is now unnecessary:@ -126,15 +126,15 @@ The message to be signed depends on the type of transaction containing an inputI have tested the SIG_ALL test vectors for SwapRequest and MeltRequest and they seem ok.
This file probably shouldn't be in here?
@ -102,33 +102,29 @@ Example `SwapRequest`:The following is the `msg_to_sign` on the above `SwapRequest`.Some weirdness in the formatting here.
Yeah sorry. Added a gitignore pr so I stop doing this https://github.com/cashubtc/nuts/pull/309
@ -102,33 +102,29 @@ Example `SwapRequest`:The following is the `msg_to_sign` on the above `SwapRequest`.fixed in https://github.com/cashubtc/nuts/pull/302/commits/e4a08a7f3c417ad88b49afd6b10197bdeffff585