feat(bsv): add CAIP-10 profile for BRC-100 identity keys - #202
Open
sirdeggen wants to merge 2 commits into
Open
Conversation
Follow-up to ChainAgnostic#190: a BSV account in this namespace is a BRC-100 wallet identity public key (compressed secp256k1 PubKeyHex), not a Bitcoin address. Document the BTC/BCH assumptions this breaks — bip122 CAIP-10 excludes legacy P2PKH, BSV has no SegWit/Taproot/ CashAddr, and on-chain outputs pay BRC-42 children rather than the identity key. Signed-off-by: Deggen <d.kellenschwiler@bsvassociation.org>
Signed-off-by: Deggen <d.kellenschwiler@bsvassociation.org>
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
1 participant
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.
Summary
Follow-up to #190, specifically @bumblefudge's review: BSV's account model is not BTC/BCH, and a CAIP-10 profile is needed so those assumptions are not smuggled across.
A BSV account in this namespace is a BRC-100 wallet identity public key (compressed secp256k1
PubKeyHex, 66 hex chars), not a Bitcoin address.Resolved with
getPublicKey({ identityKey: true })on a BRC-100 wallet whosegetNetwork()matches the CAIP-2 prefix.Why this is not bip122 CAIP-10
bip122)1…) is excluded as obsolete1…address is visually identical to a BTC1…addressThe identity key never appears on chain. Paying
hash160(identityKey)as P2PKH is not a BRC-29 payment. Derived child keys have the same compressed-pubkey syntax as identity keys; syntactic validity does not prove identity, which the profile states explicitly.This follows the casper CAIP-10 precedent of using a public key as the account identifier.
Files
bsv/caip10.md— profile (semantics, syntax, resolution, test cases, BTC/BCH warnings)bsv/README.md—requiresCAIP-10 and a short pointer at the profileRelated: x402-foundation/x402#2890 (x402
exacton BSV uses this identity key aspayTo).