Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update caip-10.md #333

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update caip-10.md #333

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions CAIPs/caip-10.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ extending [CAIP-2][] chain id specification. This is useful for both
decentralized applications and wallets to communicate user accounts (EOA in EVM
terminology) or smart contracts/abstraction for multiple chains using string
identifiers specific to each chain. Currently, wallets are usually designed for
each chain and multi-chain wallets use proprietray data structures to
each chain and multi-chain wallets use proprietary data structures to
differentiate accounts. This proposal aims to standardize these identifiers for
accounts to allow interoperability.

Expand Down Expand Up @@ -66,7 +66,7 @@ the blockchain that is referred to by the `chain_id`.
The goals of the general account ID format is:

- Uniqueness between chains regardless if they are mainnet or testnet
- Readibility using the prefix of a chainId to quickly identify before parsing the address
- Readability using the prefix of a chainId to quickly identify before parsing the address
- Restricted to constrained set of characters and length for parsing

## Canonicalization
Expand Down