Explore every DeFi Zap, straight from the chain.
Creations, Zaps, AutoZaps, and recoveries are read directly from Robinhood Chain logs. An execution counts only when the Zap contract that emitted it was deployed by one of the canonical factories. No indexer, no estimates.
Onchain activity
creations, Zaps, AutoZaps, permanent stops, and recoveries — newest firstReading Robinhood Chain logs…
Reading creations, Zaps, AutoZaps, policy stops, and recoveries from chain logs…
Zap, AutoZap, recovery, and policy-halt rows are read only from Zaps recorded in a factory's own ZapCreated log. Policy halts are accepted only from configured v1.2 and v3.2 emitters; v1.1, v3, and v3.1 remain unsupported. An AutoZap row is a Zap an executor submitted against a standing authorization its owner signed. Each row opens its own transaction; the v1.1 factory is on Blockscout ↗.
The Robinhood RPC log query failed, so this list is unavailable. An empty list would be a claim that the canonical factories have deployed nothing. Nothing is shown instead.
Read the v1.1 factory directly ↗An address reaches this list one way: one of this release's configured canonical factories emitted its ZapCreated log. What a Zap does is stored in the Zap, not here — open a row to read the policy it committed to and the Executed and EmergencyExit logs it has emitted.
Verified contracts
source-verified on Robinhood Blockscout0xFC775017b25d2458623E2f3E735A4B750dD8b4E4Implementation0x2a5EB455952d25b8060Ee933d2bADB022c7aE11ASwap adapter0x04f62dA4b51a010eFa32aa81569169C47AEd602CAdapter registry0x9E56e444f490C00A6277326A47Cb462E12dF1f17Token allowlist0x87fBb77a4328B068CADbA2eBE5dBCE0ffbd7141B0xZAPS token0xDd90bFa4adC7F4401E611AbaC692D939F9F4CB07Six source-verified core contracts on Robinhood Blockscout. Expansion adapters and automation-lineage contracts are recorded in the deployment registry; fully configured lineages feed the live lists above.
Depositing funds can result in total loss. Onchain actions are irreversible. Read the security model.
Trade it. Use the app. Inspect the first fixed fee campaign.
OpenZaps can buy 0xZAPS through its pinned aeWETH → 0xZAPS route. Every Zap contract created by the current app converts its visible 0.00001 ETH creation fee into 0xZAPS atomically. A connected wallet holding 100,000+ 0xZAPS also gets auto-refreshing quotes, more saved Zaps and receipts, and receipt JSON export. The first 0xZAPS fee rewards campaign is fixed to a seven-day Aug 3–10, 2026 staking window. It was funded at launch with 50 of 100 tokenized Clanker fee shares and is configured to use time-weighted stake to allocate campaign-accounted WETH to eligible deposits during that window. Its harvest path was configured for Clanker fees, while direct WETH transfers can also be synchronized. Check /rewards for the current phase and later claim deadline. Every core workflow stays open without holding or staking the token.
Pinned Uniswap v4 pool, one bounded policy execution.
0.00001 ETH, converted atomically with a reviewed floor or the whole creation reverts.
Auto-refresh quotes, 50 saved Zaps, 100 receipts, JSON export.
Raises the app's saved-zap limit to 100.
Seven-day Aug 3–10, 2026 staking window; /rewards shows the current phase and later claim deadline.
Ownership alone grants no governance, automatic staking benefit, fee right, revenue claim, yield, equity, or return. The first campaign was limited to eligible deposits made during its fixed Aug 3–10, 2026 staking window; /rewards shows the current phase and later claim deadline.