Skip to content

NUT-11: Optional P2PKWitness.digest for multi-party SIG_ALL #318

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.

Sign up for GitHub

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

Open
robwoodgate wants to merge 2 commits into
base: main
Choose a base branch
from
Open

NUT-11: Optional P2PKWitness.digest for multi-party SIG_ALL #318

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
03c732e
Adds optional P2PKWitness.digest
robwoodgate Dec 3, 2025
5c472f3
Added witness.mts for flexibility
robwoodgate Dec 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion 11.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,12 +105,20 @@ Signatures are stored in `P2PKWitness` objects and are provided in either each `

```json
{
"signatures": <Array[<hex_str>]>
"signatures": <Array[<hex_str>]>,
"digest": <str>, // Optional.
"mts": <str>, // Optional.
}
```

The `signatures` are an array of signatures in hex and correspond to the signatures by one or more signing public keys.

To facilitate the signing of multi-party `SIG_ALL` transactions, the SHA256 digest of the message to be signed can be stored in the optional `P2PKWitness.digest` of the `Proof` to be signed. Wallets SHOULD sign a `SIG_ALL` proof over this digest, if present, and ignore it entirely for `SIG_INPUTS` proofs.

In cases where `SIG_ALL` signers require detailed information about the inputs and outputs (eg: where there are multiple receivers), the plain text _message to sign_ can be stored in the `P2PKWitness.mts` of the `Proof` to be signed. Wallets **MUST** sign a `SIG_ALL` proof over the SHA256 of this message. if present, and ignore it entirely for `SIG_INPUTS` proofs.

If both `digest` and `mts` are included, a wallet SHOULD use the `mts` and IGNORE the `digest`, or MUST validate the `digest` matches the `SHA256(mts)` before using it.

#### Signature flag `SIG_ALL`

`SIG_ALL` is enforced only if the following conditions are met:
Expand Down