Vechain Namespace - Addresses

Author Darren Kelly
Status Draft
Type Standard
Created 2023-07-17
Updated 2023-07-17
Requires CAIP-2, CAIP-10

CAIP-10

For context, see the [CAIP-10][] specification.

Rationale

VechainThor uses Secp256k1 for transaction signing. The account addresses are derived by taking the Keccak-256 hash of the public key and representing it as a hexadecimal number. The last 20 bytes of the Keccak-256 hash are used to generate the address.

VechainThor addresses are hex-encoded strings with a length of 42 characters, prefixed with 0x.

Private keys used for other EVM compatible chains will produce the same account address.

Syntax

Vechain addresses match the following regular expression:

0x[a-fA-F0-9]{40}

Test Cases

Account address:

# Vechain Thor MainNet
vechain:b1ac3413d346d43539627e6be7ec1b4a:0xf077b491b355E64048cE21E3A6Fc4751eEeA77fa

# Vechain Thor TestNet
vechain:87721b09ed2e15997f466536b20bb127:0xf077b491b355E64048cE21E3A6Fc4751eEeA77fa

Contract address:

# Vechain Thor MainNet
vechain:b1ac3413d346d43539627e6be7ec1b4a:0x0000000000000000000000000000456E65726779

# Vechain Thor TestNet
vechain:87721b09ed2e15997f466536b20bb127:0x0000000000000000000000000000456E65726779

References

Copyright and related rights waived via CC0.

Citation

Please cite this document as:

Darren Kelly, "namespaces/vechain-caip10: Vechain Namespace - Addresses [DRAFT]," Chain Agnostic Namespaces, vechain-caip10, July 2023 / July 2023. [Online serial]. Available: https://github.com/ChainAgnostic/namespaces/vechain-caip10.md