Skip to content

Deterministic pay to public key generation #331

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
lescuer97 wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Deterministic pay to public key generation #331

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2ce332e
pay to public key standard derivation
lescuer97 Jan 19, 2026
75fa183
fix: wording
lescuer97 Jan 21, 2026
04cce64
use correct purpose and tests
lescuer97 Mar 27, 2026
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
12 changes: 12 additions & 0 deletions 13.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,18 @@ The HMAC-SHA256 KDF is built as the following:
2. `hmac_digest = HMAC_SHA256(seed, message)`, where `HMAC_SHA256` is the [hash-based message authentication code](https://en.wikipedia.org/wiki/HMAC) using SHA-256 as the hashing algorithm.
3. `secret = hmac_digest` and `blinding_factor = hmac_digest % N`.

#### P2PK Derivation
Copy link
Copy Markdown
Collaborator

@thesimplekid thesimplekid Mar 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder of this should just be a new nut would be easier to track who supports it and think we should avoid changing existing nuts where we can especially widely supported ones like nut13. Though it would be a very small nut.

Copy link
Copy Markdown
Contributor Author

@lescuer97 lescuer97 Mar 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought about the same but I don't think it's needed in this case. Maybe if we start making more deterministic generation we would move it there.


Wallet are able to generate private keys in a deterministic way to have proofs locked to them.

The following BIP32 derivation path for derivation of the key: `m/129373'/10'/0'/0'/{counter}`:

- 129373': Purpose picked for P2PK derivation.
- 10': Account for generating private keys for usage in P2PK.
- {counter}: Incrementing counter encoded as an unsigned 64-bit integer in big-endian format.
Copy link
Copy Markdown
Contributor

@a1denvalu3 a1denvalu3 Jan 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this using BIP32? Should be more clear.

Copy link
Copy Markdown
Contributor Author

@lescuer97 lescuer97 Jan 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, I'll make it clearer


This will allow wallets to swap proof that are still locked to a public key during a restore process.
Copy link
Copy Markdown
Contributor

@robwoodgate robwoodgate Jan 22, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This will allow wallets to swap proof that are still locked to a public key during a restore process.
Wallets can deterministically generate private keys for P2PK using the following BIP32 derivation path:
`m/129372'/10'/0'/0'/{counter}`
Where:
- Purpose' = `129372'` (UTF-8 for 🥜)
- Coin type' = `10'` - reserved for generating private keys.
- `{counter}` is an Incrementing counter, encoded as an unsigned 64-bit integer in big-endian format.
This allows wallets to swap Proofs still locked to a corresponding public key during a restore process.
In line with BIP-32, if the resulting private key is out of range (`> N`), it should be discarded.


### Code Examples

#### Versioned Secret Derivation
Expand Down
22 changes: 22 additions & 0 deletions tests/13-tests.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,3 +91,25 @@ The corresponding blinding factors `r` are:
"r_4": "5550337312d223ba62e3f75cfe2ab70477b046d98e3e71804eade3956c7b98cf"
}
```

## P2PK Derivation

Using [NUT-13](13.md) derivation procedure for P2PK, we derive values starting from the following BIP39 mnemonic:

```json
{
"mnemonic": "half depart obvious quality work element tank gorilla view sugar picture humble"
}
```

The public keys derived for the first five counters from `counter=0` to `counter=4` are:

```json
{
"m/129373'/10'/0'/0'/0": "021693d45f4fdf610ae641fedb0944fb460fbb8264f21c19d2626c3da755fcbbcb",
"m/129373'/10'/0'/0'/1": "0395461ab678058c0ed6aa39f38dda490eaa163e9ad27070b23ec3d06b41e07535",
"m/129373'/10'/0'/0'/2": "02a05e4e593a633e9b4405f01c9632c8afde24cb613017a1aee56fd76291ad26d1",
"m/129373'/10'/0'/0'/3": "033addea25c3873b93d67d536c61c9d9c993f6efd8b9dfa657951b66b5001e51dd",
"m/129373'/10'/0'/0'/4": "03c964bdf42fc82b6c574615746eeca37527a24f1fdfc1b34a732c53843b5744a5"
}
```
Loading