How ZeroDev works in Tapioca
ZeroDev contributes three distinct pieces of infrastructure to your experience:Smart account (Kernel)
Your on-chain account is a ZeroDev Kernel smart contract — an ERC-4337 compliant smart account. Unlike a standard externally-owned account (EOA), it can enforce custom logic, batch transactions, and support Session Keys.
Paymaster (gas sponsorship)
ZeroDev’s paymaster pays your gas fees on your behalf. Every transaction you submit through Tapioca is covered — you never need to hold ETH to interact with the protocol.
Bundler (transaction submission)
ZeroDev’s bundler collects your user operations and submits them to the Base network. It handles the complexity of ERC-4337’s transaction flow so your actions confirm quickly and reliably.
Session Keys
ZeroDev’s Kernel supports a plugin system that enables Session Keys — a feature built on EIP-7702. Session Keys allow Tapioca to perform pre-authorized actions on your behalf (such as auto-compounding yield) within strict limits you define, without requiring your signature for every individual transaction.Session Keys are scoped and time-limited. Tapioca can only take the specific actions you’ve authorized, and only for the duration you’ve set.
What this means for you
- No gas fees — ZeroDev’s paymaster covers all transaction costs
- No ETH required — you never need to fund your account with ETH to get started
- Faster interactions — operations are batched and submitted efficiently by the bundler
- Programmable automation — Session Keys let Tapioca act on your behalf without interrupting you for every action
Service availability
In the unlikely event that the ZeroDev bundler is temporarily unavailable, transaction submissions may be delayed. Tapioca will surface an error if this occurs. Your funds remain safe on-chain and no action is lost — operations will resume once the bundler recovers.