Create account
Home › Features › Unified EVM Address
Features · one address, every EVM chain

One address on every EVM chain

The identical address string on Ethereum, Base, BSC, Arbitrum, Polygon, Optimism

Pure key math, no smart-contract wrappers: the same derivation index under your vault's MPC key produces the same address everywhere. Counterparties whitelist one address once; reconciliation stops branching per chain.

Share the Trust, Guard the Keys

Create accountLive on testnet in an afternoon
Compare PlansIncluded in a plan, not an add-on
The problem

One user, eight EVM chains, eight addresses to reconcile

Deriving a different address per EVM chain multiplies your reconciliation surface for no cryptographic reason — the curve and the derivation are identical. Vaultody derives one address string that is valid on every EVM chain you use, so a user, a merchant or a desk has one identity across the set.

  • Same key, same addressPure key mathematics. No smart-contract wrapper, no account-abstraction dependency, nothing to deploy per chain.
  • Reconciliation stops branchingOne address in your database, one row per counterparty, whichever chain the funds arrive on.
  • Whitelist onceCounterparties that allow-list your address do it once for the whole EVM set.

How it works

One key, one identity

Your vault holds one MPC key; derivation walks the same path on every EVM chain, so index n is the same address on all of them. No account-abstraction contracts, which means no contract risk and no per-chain deployment.

  • ✓Whitelist once — literally the same string everywhere
  • ✓Enable a chain and monitoring starts there — same address, new coverage
  • ✓Funds sent to a not-yet-enabled chain are safe: the key controls the address regardless
one user, six chains
user-84712 ethereum 0x7a4f…c19e base 0x7a4f…c19e bsc 0x7a4f…c19e arbitrum 0x7a4f…c19e polygon 0x7a4f…c19e optimism 0x7a4f…c19e
Specification

EVM coverage

The set that shares one address, and what still differs per chain.

ChainsEthereum, Ethereum Classic, BNB Smart Chain, Polygon, Arbitrum, Optimism, Base and Avalanche.
Address modelOne derived address per vault account, valid across the EVM set.
MonitoringEach chain is monitored independently, so incoming funds are detected per chain against the same address.
Asset registrationRegister the asset once per chain you intend to hold it on, and it appears in balances and reporting.
FeesSponsored transactions are available on six of the EVM chains via EIP-7702.
Contract interactionAvailable on modern v2 vaults for calls beyond plain transfers.
BatchingThe batch endpoint fans one sender out to many recipients on six EVM chains.
SigningECDSA across the set — the same signing path as Bitcoin-family chains.

Frequently asked questions

Get answers to commonly asked questions.

Are funds safe on a chain we have not enabled?

Yes — the key controls the address on every EVM chain regardless. Enable the chain and the balance is visible; nothing is ever lost.

Is this account abstraction?

No — plain EOA key derivation. No wrapper contracts, no relayers, no per-chain deployments to audit.

Which plans include it?

All of them.

Share the Trust Guard the Keys

One identity across EVM — fewer addresses, fewer mistakes.

Create accountRequest Demo