Update 0015-slatepack.md - fix for mimblewimble/grin-wallet#663#92
Open
Anynomouss wants to merge 2 commits into
Open
Update 0015-slatepack.md - fix for mimblewimble/grin-wallet#663#92Anynomouss wants to merge 2 commits into
Anynomouss wants to merge 2 commits into
Conversation
…t#663 I took better and more explicit documentation on SlatepackAddress key derivation from parts of grin's cod base to make this RFC more clear to readers and in line with the current implementation in grin-wallet. This PR addresses the following GitHub issue: mimblewimble/grin-wallet#663
This was referenced Oct 9, 2025
aglkm
reviewed
May 29, 2026
| |m/0 | m/0/1/x |m/0/1/x | | ||
| |m/1 | m/1/1/x |m/1/1/x | | ||
|
|
||
| In _grin-wallet_ the x for slatepack address generation is currently fixed (`x=0`) per account. `SlatepackAddress` keys may be derived in parallel to the blinding factor derivation path such that a unique `SlatepackAddress` is derived each time a new blinding factor is derived for a transaction to satisfy the requirement for a unique `SlatepackAddress` to be used for each transaction by default. |
There was a problem hiding this comment.
If my understanding is correct and in derivation path (depth=2) we use: 0 for outputs and 1 for slatepack addresses, then the above example is wrong.
Should be:
| Account | OutputKeys | SlatepackAddress key(s) |
|---|---|---|
| m/0 | m/0/0/x | m/0/1/x |
| m/1 | m/1/0/x | m/1/1/x |
Author
There was a problem hiding this comment.
You are correct. I think I copy pasted a column and forgot to change the values 🤦♂️.
Fixing my sloppy edit. |Account|OutputKeys |SlatepackAddress key(s)| |-------|------------|----------------------| |m/0 | m/0/0/x |m/0/1/x | |m/1 | m/1/0/x |m/1/1/x |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I took better and more explicit documentation on SlatepackAddress key derivation from parts of grin's cod base to make this RFC more clear to readers and in line with the current implementation in grin-wallet.
This PR addresses the following GitHub issue:
mimblewimble/grin-wallet#663