MultiversX Namespace - Addresses

CAIP-10

For context, see the CAIP-10 specification.

Rationale

The MultiversX Address format is bech32, specified by the BIP_0173. The human-readable-part of the bech32 addresses is “erd” and the universal separator 1, which means that the MultiversX address always starts with an erd1, e.g.: erd1sea63y47u569ns3x5mqjf4vnygn9whkk7p6ry4rfpqyd6rd5addqyd9lf2.

The MultiversX network defines the address of an account as the bech32 representation of the public key of its corresponding pair of keys (the secret key remains known only to the user that owns the key pair). The public key is 32 bytes in length (64 hex characters), while the address (bech32) is 62 characters long.

On MultiversX, deployed Smart Contracts and only deployed Smart Contracts have their hex (raw) addresses prefixed with 8 zero bytes (meaning that their bech32 address will begin with erd1qqqqqqqqqqqq )

Syntax

caip10-like address:    namespace + ":" chainId + ":" + address
namespace:              mvx
chain Id:               1, D or T
address:                bech32-formatted MultiversX address (erd1...)

Test Cases

#Wallet address on MultiversX Mainnet
mvx:1:erd1uapegx64zk6yxa9kxd2ujskkykdnvzlla47uawh7sh0rhwx6y60sv68me9

#Deployed Smart Contract on MultiversX Mainnet
mvx:1:erd1qqqqqqqqqqqqqpgqhe8t5jewej70zupmh44jurgn29psua5l2jps3ntjj3 

MultiversX Devnet
mvx:D:erd1devnet6uy8xjusvusfy3q83qadfhwrtty5fwa8ceh9cl60q2p6ysra7aaa

MultiversX Testnet
mvx:T:erd1sea63y47u569ns3x5mqjf4vnygn9whkk7p6ry4rfpqyd6rd5addqyd9lf2

References

• MultiversX Documentation
• MultiversX Specifications
• Integrators Guide
• BIP_0173, the Bitcoin Improvement Proposal that includes the bech32 algorithm and python code

Copyright

Copyright and related rights waived via CC0.

Citation

Please cite this document as:

MultiversX Team, "namespaces/mvx-caip10: MultiversX Namespace - Addresses [DRAFT]," Chain Agnostic Namespaces, mvx-caip10, September 2023 / . [Online serial]. Available: https://github.com/ChainAgnostic/namespaces/mvx-caip10.md