Learn · 06
Native account abstraction
Batched actions, session keys and sponsored gas, built into the protocol instead of added on.
Checked against official docs on 2026-10-29
StatusDevnet feature, available from genesis on the devnet.
What "account abstraction" means
A normal wallet account can do one thing per transaction and must pay its own gas. Account abstraction makes accounts more flexible: they can bundle actions, delegate limited permissions and let someone else pay fees.
Built in, not bolted on
On most EVM chains this needs extra infrastructure, such as smart-contract wallets, bundlers and an EntryPoint contract. On New L1, the rules are part of the protocol and every node enforces them. An existing account keeps its address and simply uses a new transaction type, 0x76. The docs say there is nothing to deploy or opt into.
What it lets you do
- Batching. One transaction can carry 1 to 64 calls. Either all of them take effect, or none do.
- Session keys. Give an app a temporary key with limits: which calls it can make, how much it can spend, and when it expires.
- Sponsored gas. Another account can pay your fees, and can optionally be repaid on-chain in a token.
- Modern signing. Supports secp256k1 (standard wallets), P-256 and WebAuthn, which is what passkeys use.
Why this matters
Our analysis (unofficial)These features remove common beginner pain points: buying gas before you can do anything, approving every single step, and managing seed phrases. How wallets and apps adopt them is still to be seen.
Things to know
- Gas is charged on the declared gas limit, and unused gas is not refunded.
- A root key cannot be revoked, so treat it like any wallet's master key.