Accounts & Identity
An Orbinum account is a plain Substrate AccountId32. For any wallet holding a Secp256k1 keypair — every standard Ethereum wallet — that AccountId32 and the corresponding Ethereum H160 address are two views of the same account, sharing a single ORB balance. No registration or on-chain call is required.
Account model
Every wallet starts here. An AccountId32 (SS58) that holds ORB and signs extrinsics. No registration required.
A Secp256k1 account also has an Ethereum H160 address, derived structurally as [H160 | 0x00×12]. Both address forms resolve to the same balance. Compatible with MetaMask.
One key, both address spaces
The relationship is structural, not stateful — the runtime computes it on every transaction:
AccountId32 = H160 (20 bytes) ++ 0x00 x 12
The 12 trailing zero bytes mark the AccountId32 as EVM-derived. Both forms index the same entry in pallet_balances: there is no synchronisation, copy, or lock between them.
Accounts with a pure Sr25519 or Ed25519 key have no H160 counterpart. They operate on the Substrate side only, and can still receive native transfers from Solidity via the Balances precompile.
Reading this section
- EVM ↔ Substrate mapping — the dual-address model, signature verification, and address derivation reference