Protocol-Native Smart Accounts
Three validation layers, key rotation, and custom validators — built into the base protocol without ERC-4337.
Three-Layer Validation Flow
First-Use Validation
Derive address from (version, algo_id, pubkey) via BLAKE3 and verify PQ signature — account created on first transaction.
Default PQ Validation
Existing accounts verify pubkey_hash + PQ signature. Key rotation changes the key but keeps the same address.
Custom Validator
Delegate validation to account-specific EVM logic — multisig, social recovery, time locks, or any custom policy.
No Bundler Required
Validation is part of the base protocol — no ERC-4337 EntryPoint or separate alt-mempool.
32-byte 0x Addresses
Bech32m encoding with PQ HRP — visually distinct from Ethereum, binds to the signing algorithm.
Key Rotation
Rotate keypair or switch PQ algorithm — your on-chain address and identity stay the same.
Custom Validators
Multisig, social recovery, time locks — deploy your own validation logic as an EVM contract.
Shell AA vs ERC-4337
| Dimension | Shell Chain ✦ | ERC-4337 |
|---|---|---|
| Validation Location | Protocol-level | EntryPoint contract |
| Bundler Required | No | Yes |
| Separate Alt-Mempool | No | Usually yes |
| Default Validator | Built into the chain | Wallet contract-defined |
| Address Format | 0x + 64 hex (32-byte) | 0x... (hex) |