Add bsv namespace (BSV Blockchain)#190
Open
sirdeggen wants to merge 1 commit into
Open
Conversation
Registers bsv:mainnet and bsv:testnet, identifying BSV networks by human-readable network name (mirroring BRC-100 getNetwork and SV Node getblockchaininfo.chain), following the casper precedent of a Chain ID distinct from the genesis hash. Rationale acknowledges that bip122 can represent BSV via its fork-block hash.
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
Adds a new namespace,
bsv, for the BSV Blockchain, with a completeREADME.mdand CAIP-2 profile. Registers two Chain IDs:bsv:mainnet— BSV main networkbsv:testnet— BSV test networkApproach and rationale
BSV descends from the original Bitcoin protocol and shares Satoshi's genesis block with BTC and BCH. I want to be upfront that
bip122can represent BSV: it disambiguates forks by the first post-fork block hash (as it does for Bitcoin Cash,bip122:000000000000000000651ef99cb9fcbe), and a BSV entry could be built the same way from its fork block.This namespace uses the human-readable network name as the CAIP-2 reference instead, following the casper precedent (a Chain ID that "should not be confused with the genesis_hash"). The reason is that the BSV application layer — BRC-100 wallets, overlay services, ARC broadcasters, SPV clients — universally identifies a network by name, never by fork-block hash. A BRC-100 wallet self-reports via
getNetwork→mainnet/testnet; SV Node'sgetblockchaininfo.chainreturnsmain/test. Cross-chain tooling (e.g. the x402 payment protocol, CAIP-10/CAIP-19 references) can then map directly onto identifiers applications already exchange without a full-node round-trip. The two schemes can coexist — a hash-basedbip122BSV entry and this name-based one occupy different namespaces.Resolution mechanics, syntax (
bsv:(mainnet|testnet)), and test cases are inbsv/caip2.md.Context
This registration supports adding BSV as a payment mechanism to the x402 protocol, where the design discussion for these identifiers is ongoing. Happy to adjust the reference scheme (including moving to
bip122) based on editor guidance.Author: @sirdeggen (BSV Association).