Accounts & Wallets
EOAs, smart accounts, and wallet support on Mandala. Mostly the EVM you already know.
This page is short because most of the answer is "the same as Ethereum." Mandala is EVM-equivalent and inherits Ethereum's account model, address format, and wallet ecosystem.
EOAs
Externally-owned accounts (EOAs) on Mandala work exactly as on Ethereum. Same secp256k1 keys, same address derivation, same signing. If you have an Ethereum address, you have a Mandala address; the same private key controls both.
A few practical implications:
- An address that holds ETH on Ethereum holds 0 KPG on Mandala by default, until you bridge or someone sends to that address on L2.
- The same wallet seed signs both Ethereum and Mandala transactions. No new mnemonic, no new derivation path.
- Address checksumming follows EIP-55; lowercase and checksummed forms address the same account.
Smart-contract accounts
ERC-4337 (account abstraction) works on Mandala. You can deploy entry points, bundlers, and paymasters using the standard ERC-4337 contracts. There is no chain-specific bundler infrastructure that needs custom configuration.
Smart-contract wallets (Safe, Argent, and similar) work as long as their factories are deployed on Mandala. The deterministic deployer at 0x4e59b44847b379578588920ca78fbf26c0b4956c is available, so contracts deployed deterministically on other EVM chains land at the same address on Mandala.
Wallet support
Any EVM wallet that lets you add a custom RPC works with Mandala. The most common paths:
| Wallet | Setup |
|---|---|
| MetaMask | Add a custom network with chain ID 20010 and RPC https://rpc1-mainnet.mandalachain.io. |
| Rabby | Add as a custom chain with the same parameters; Rabby auto-detects most fields after the first connection. |
| WalletConnect-compatible wallets | Connect via your dApp; the dApp passes the chain config. |
| Hardware wallets (Ledger, Trezor) | Work behind MetaMask or Rabby. No firmware update needed. |
Step-by-step setup walkthroughs live in the Network section: MetaMask, Rabby, and the bridge.
ENS resolution
ENS names resolve on Ethereum, not on Mandala. To resolve vitalik.eth from a Mandala dApp, your client should query the L1 ENS registry. There is no chain-specific name service on Mandala today.
What does not change
To save you time looking for it: the following work identically on Mandala and Ethereum mainnet, and you do not need a Mandala-specific wallet, signer, or library.
- Transaction signing (legacy, EIP-2930, EIP-1559).
- Personal sign and EIP-712 typed-data signing.
- ethers.js, viem, web3.js (point them at the Mandala RPC).
- ABIs, function selectors, event topics.
- Common precompiles (
ecrecover,sha256). The Arbitrum-specific precompiles (ArbSysand friends) are documented in the Arbitrum docs.
Read more on Arbitrum
Arbitrum's precompiles reference lists the Arbitrum-specific precompiles available on every Orbit chain, including Mandala.