0xd03281bcF44656215d6888aC0cBD0AEcc9DCB4d4
Everything below was read from Robinhood Chain at one pinned block. This page reports what the contract stores and what its own logs say. Nothing is estimated, modelled, or priced. A read that fails is reported as unavailable, never as a zero.
The factory's own ZapCreated log names this address. Its runtime is the EIP-1167 clone of the canonical implementation. The policy it exposes rehashes to the policyHash it committed to.
- Read at block
- 56,819,703
- Snapshot taken
- 9/7/2026, 12:04:10 PM
- Lifecycle
- Executed
- Lineage
- v1.1
- Policy execution
- Unsupported on deployed v1.1; this runtime predates the one-way policy stop.
Every contract read and log query on this page is pinned to that one block, so the policy, the balances, and the event history describe the same moment. Nothing here is estimated or priced.
The deployed chain
drawn from this Zap's own policy fields, not from a template- Owner
- 0x5a52…4aA2 ↗
- Recipient
- 0x5a52…4aA2 ↗
- Relayer fee cap
- 0 — no execution of this policy can pay a relayer fee.
- Optimization
- Enabled
- Tracked assets
- 0x0Bd7…AD73 ↗0xDd90…CB07 ↗
- Policy hash
- Rehashes from the live policy fields.
The same block vocabulary the builder uses. A fork copies only the verified route, exact input and reproducible safety defaults; owner, recipient, nonce, executor and prior signatures never travel. Connectors are coloured by the shape of value moving along them.
What has happened
measured, not modelledProduced by executions
- 12,522,405.28368 0xZAPSnet to the recipient · gross out of the adapter 12,522,405.28368 0xZAPS
Fee withheld from output
Zero, and not because none happened to be taken. This policy commits maxRelayerFeeCap = 0, so no execution of it can pay a relayer fee. The bound comes from the policy hash, not from a measurement.
Stacked into 0xZAPS
None — no recurring-stack execution appears in this Zap's logs.
Swept by emergency exit
None — the owner has never pulled assets back out of this Zap.
Held right now
- 0 aeWETH
- 0 0xZAPS
- 0 ETH
Counts and totals come only from this contract's own execution logs — Executed for an owner-signed run, ExecutedRecurring, ExecutedRecurringRelative, ExecutedRecurringStack and ExecutedTrigger for an automated one — plus its EmergencyExit logs. No USD value, token price, PnL, APY, or success rate appears on this page. A reverted execution emits no log at all, so a success rate computed from these logs would be unfalsifiable, and none is shown.
Every execution and exit
read from this contract's own logsExecutions
Executed3,210,282.149177 0xZAPS to 0x5a52…4aA2nonce 454156…49910x8daa…48bf ↗Jul 22, 2026, 5:00 PMExecuted3,263,608.302462 0xZAPS to 0x5a52…4aA2nonce 107659…38440x4292…5362 ↗Jul 22, 2026, 4:48 PMExecuted3,134,379.405988 0xZAPS to 0x5a52…4aA2nonce 451227…52140xaa4b…c416 ↗Jul 22, 2026, 4:33 PMExecuted2,914,135.426051 0xZAPS to 0x5a52…4aA2nonce 723665…20100xb582…219a ↗Jul 22, 2026, 3:57 PMEmergency exits
None yet.
Where this address came from
provenance- Created in block
- 16,550,544Jul 22, 2026, 3:57 PM
- Creation transaction
- 0x24e9663f…d7cfbc7a ↗
- Owner at creation
- 0x5a52…4aA2 ↗
- CREATE2 salt
- Implementation codehash
- Factory implementation
- 0x2a5E…E11A ↗Factory version 1.1.0
- Contract type
- One-shotExecutes its frozen policy once, against an owner-signed intent.
This Zap is only on the site because the canonical factory's own ZapCreated log names it. An identically-shaped contract deployed by anything else would never reach this page.
Ask this capsule
answers cite the fields they rest onQuestions are answered only from what this capsule reports onchain. Any figure that does not appear in its own record is refused rather than guessed at.