Blockchains

@agntn/keysv0.3.1

Blockchains

Eleven drivers and one class shape. Pick a chain to see its address rules and the traps.

Every driver below answers the same calls: generateWallet, getAddress, validateAddress, signMessage, deriveHDWallet. What changes is the hashing, the encoding, and which arguments actually matter. The pages are short on purpose, the interesting part of each one is the gotcha list.

Bitcoin

secp256k1. Five address formats, testnet, and a taproot that does the real BIP341 tweak.

Litecoin

secp256k1. Bitcoin's five formats behind L, M and ltc1, plus its own message preamble.

Decred

secp256k1. BLAKE-256 in every hash, addresses that start with Ds, and no HD walk, on purpose.

Ethereum

secp256k1. EIP-55 checksummed hex and the personal_sign preamble.

Base

Same driver as Ethereum under a different name. Same key, same address.

TRON

secp256k1. Ethereum's 20 bytes wrapped in base58check, so it starts with T.

Solana

ed25519. The address is the public key in base58, no hashing at all.

Stellar

ed25519. The public key as a G StrKey with a CRC16 checksum, and SEP-53 message signing.

Aptos

ed25519. SHA3-256 over the key and a scheme byte, 0x hex out.

Sui

ed25519 or secp256k1 on one chain. Blake2b over a flag byte and the key.

Cardano

ed25519. bech32 base, enterprise, and stake addresses. No mnemonic derivation, on purpose.

Edit this pageorReport an issue

Creating Custom Blockchains

Extend AbstractBlockchain. Implement five methods. Register it and test it.

Aptos

ed25519 with addresses from SHA3-256 over the public key and a scheme byte.