Multi-Chain Support
One BIP39 seed, three independent chain derivations — materialized simultaneously every time you unlock, not sequentially.
| Chain | Derivation path | Curve | Address format |
|---|---|---|---|
| EVM (Ethereum & compatible) | m/44'/60'/0'/0/0 | secp256k1 | EIP-55 checksummed hex |
| Bitcoin | m/84'/0'/0'/0/0 (BIP84) | secp256k1 | Native segwit — bc1... |
| Solana | m/44'/501'/0'/0' | ed25519 (SLIP-0010) | Base58 of the raw public key |
Why one seed works for all three
All three chains derive from the exact same 64-byte BIP39 seed produced by the
KDF pipeline — using a single BIP39 implementation
(blockchain_utils) as the one source of truth for BIP39/BIP32/SLIP-0010 across every chain,
rather than mixing separate per-chain mnemonic libraries that could drift out of sync with
each other.
EVM
Standard BIP32 derivation over secp256k1 at m/44'/60'/0'/0/0. The address is the
Keccak-256 hash of the public key, checksummed per EIP-55 (mixed-case hex).
Bitcoin
BIP84 (purpose 84') native segwit derivation over secp256k1 at m/84'/0'/0'/0/0, producing
a P2WPKH address on mainnet.
Solana
SLIP-0010 ed25519 derivation at m/44'/501'/0'/0'. Every level of this path is hardened —
unlike secp256k1, SLIP-0010's ed25519 variant has no unhardened/public derivation at all, so
every child key requires the parent private key.
Note
A Solana address is simply the base58 encoding of the raw 32-byte ed25519 public key — no hashing, no prefix, unlike Bitcoin or EVM addresses.