feat: add dashevo namespace for Dash Platform WalletConnect support#177
Open
PastaPastaPasta wants to merge 1 commit intoChainAgnostic:mainfrom
Open
feat: add dashevo namespace for Dash Platform WalletConnect support#177PastaPastaPasta wants to merge 1 commit intoChainAgnostic:mainfrom
PastaPastaPasta wants to merge 1 commit intoChainAgnostic:mainfrom
Conversation
Adds CASA namespace files (README.md, caip2.md, caip10.md) for the dashevo namespace. Dash Platform uses Tenderdash consensus with identity-based accounts, requiring a separate namespace from bip122 (Dash Core).
3 tasks
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
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 the
dashevonamespace for Dash Platform, the identity and data contract layer built on top of the Dash payment network.Dash Platform uses Tenderdash (a Dash fork of Tendermint) for consensus and an identity-based account model — fundamentally different from Dash Core, which already has a listing under the
bip122namespace. This requires a separate namespace because the consensus engine, account model, state model, and transport are all incompatible withbip122.Files
dashevo/README.md— Namespace overview, rationale for separation frombip122, governancedashevo/caip2.md— Chain identification using Tenderdashchain_idstrings (evo1for mainnet,dash-testnet-51for testnet)dashevo/caip10.md— Account identification using base58-encoded 256-bit Platform identity IDsKey design decisions
[-a-zA-Z0-9]{1,32}sha256(sha256(funding_outpoint)), base58-encoded (no checksum), 43-44 characters, regex:[1-9A-HJ-NP-Za-km-z]{43,44}Related
bip122)