CAIP-10: Account ID Specification

Metadata

Status: FinalStandardCreated: 2020-03-13

Authors

Pedro Gomes (@pedrouid)

Requires

EIP-2

Links

GitHub page Discussion on Ethereum Magicians

Simple Summary

CAIP-10 defines a way to identify an account in any blockchain specified by CAIP-2 blockchain id.

Abstract

This proposal aims to facilitate specifying accounts for any blockchain 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 differentiate accounts. This proposal aims to standardize these identifiers for accounts to allow interoperability.

Motivation

The motivation for proposal stem from designing a chain-agnostic protocol for communication between dapps and wallets that was independent of any blockchain but provide the flexibility to be backwards compatible with existing applications.

Specification

The account id specification will be prefixed with the CAIP-2 blockchain ID and delimited with a colon sign (:)

Syntax

The account_id is a case-sensitive string in the form

Note that -, % and . characters are allowed, but no other non-alphanumerics such as :, / or \. Implementers are recommended to use "URL encoding" (% + 2-character codes, canonically capitalized) as per Section 2 of RFC 3986 to escape any further non-alphanumeric characters, and to consider homograph attack surfaces in the handling of any non-alphanumerics.

Semantics

The chain_id is specified by the CAIP-2 which describes the blockchain id. The account_address is a case sensitive string which its format is specific to the blockchain that is referred to by the chain_id.

Rationale

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
Restricted to constrained set of characters and length for parsing

Canonicalization

Note that some namespaces like the EVM offer canonicalization schemes that use capitalization (e.g. EIP-55), an option suffix (e.g. HIP-15), or some other transformation. At the present time, this specification does NOT require canonicalization, and implementers are advised to consider deduplication or canonicalization in their consumption of CAIP-addresses. CAIP-10 profiles in CASA namespaces may contain additional information per namespace.

Test Cases

This is a list of manually composed examples

Backwards Compatibility

Previously, the character set was much more restrictive for CAIP-10s, allowing no non-alphanumeric characters. See pre-2022-10-23 version of specification for details.

Before that, legacy CAIP-10 schema was defined by appending as suffix the CAIP-2 chainId delimited by the at sign (@). See pre-2021-08-21 version of specification for details.

Changelog

2022-10-23: expanded charset to include -,., and %; also added canonicalization section and links
2022-03-10: update RegEx to incorporate CAIP-2 reference
2021-08-11: switch from {account id}@{chain id} to {chain id}:{account id} syntax