BlockchainCommons / BlockchainCommons/Community
PUBLISH: xpub Privacy Best Practices #writing
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 68
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Lead: TBD
This topic continues to haunt the bitcoin ecosystem with some proposed approaches that are likely bad long-term architecture.
Goal: define legacy best practices to avoid reuse of xpubs when creating multisigs for stateless wallets (for instance for single key signer), and higher standard for stateful wallets (Sparrow Wallet, Gordian SeedTool, etc.) but also start dialogue in community about architectures to do this right (probably xpub private commitments related to commitments also needed for FROST).
See: https://github.com/BlockchainCommons/Airgapped-Wallet-Community/discussions/53
#wallets #airgap #standards
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Community discussion 53 and the issue's distinction between stateless and stateful wallets. Define the scope for legacy xpub-reuse guidance and the proposed longer-term architecture dialogue; done should be a published best-practices document that addresses multisig and single-key signer cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain
- Domain
- cryptography, documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100