WatchExplorechain 4663
← Deployed Zaps

0x6d737680BA157C1f0B6668E71d0cd9736e88a72D

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.

Verification

read at one pinned blockFork in Composer✓ Verified onchain

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
22,712,433
Snapshot taken
7/29/2026, 7:40:41 PM
Lifecycle
Deployed, never funded
Lineage
v3.1
Policy execution
Unsupported on deployed v3.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
Bound input0.001 aeWETH — the exact amount the policy hash commits to.
0x0Bd7…AD73
ERC-20
Swap aeWETH → 0xZAPS through the allowlisted adapter, with no adapter calldata.
0x04f6…602C
ERC-20
Owner
0x8Cbc…5F66
Recipient
0x8Cbc…5F66
Relayer fee cap
0 — no execution of this policy can pay a relayer fee.
Optimization
Enabled
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 modelled
0Executions
0Of those, automated
0Emergency exits
None yetFirst execution
None yetLast execution

Produced by executions

None yet — this Zap has never emitted an execution log.

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
Custody balances at block 22,712,433. aeWETH, 0xZAPS, and ETH are the only balances this snapshot reads, so this is not a full inventory of what the Zap holds.

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 logs

Executions

None yet.

Emergency exits

None yet.

Where this address came from

provenance
Created in block
22,612,988Jul 29, 2026, 4:54 PM
Creation transaction
0x477c7b1e…3971e512
Owner at creation
0x8Cbc…5F66
CREATE2 salt
Implementation codehash
Factory implementation
0x0fE5…1063Factory version 3.1.0-candidate
Contract type
Automated · v3.1Can hold a recurring series whose per-run floor is derived from an allowlisted price source at execution, or a one-shot price trigger. Any eligible executor may submit a run this Zap owes.

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 on

Questions 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.