Skip to content
Menu

OpenZaps

$0xZAPS

Uncategorised

Contract 0xdd90bfa4adc7f4401e611abac692d939f9f4cb07

HEY holds 40 other Robinhood Chain tokens that use $0XZAPS. This page is only the contract above. See them

Is this your project? Claim and verify →

OpenZaps turn approved DeFi workflows into sealed, immutable policy capsules a Hermes agent can simulate, submit, monitor, and revoke — without ever holding discretionary wallet authority. 0xZAPS is the token for it.

What HEY knows

Building
Shipping consistentlyShipping: 3 meaningful events in 30 days; latest ship 3 days ago. Evidence Source

Build Momentum 37How it is measured

Latest ship
Code changes this week (since Mon 12 Oct) · 8 commits · · Code activity

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

Latest change
DerivedMarket event yesterday: Outside pools, lockers and burns, 9 addresses now hold half of the remaining supply. Context, not building. Evidence
FollowCreate alertTerminal previewView latest ship
Share

Follow puts OpenZaps on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me OpenZaps’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Attention
Building ranks ahead of market attention among comparable projects: 96.2 of 100 for building, 95.6 of 100 for market attention (a gap of 0.5). What the Discovery Gap is

It compares building with market attention; it is not a prediction and not a reason to trade.

Product usage
Fact2 of 2 watched contracts active · 2 calls to the contracts' own functions in 7 days; the other 33,257 of 33,259 calls were ERC-20 token transfers and approvals, which trading alone produces.

Counted from the chain. Usage says the contracts are used, not that anyone is building.

Contracts
Fact2 contracts on record for code changes, 1 behind a proxy, 2 with verified source; no implementation or interface change recorded.
Token market · context
Active market$1.1M fully diluted valuationToken verified
Not yet known
Unknown2 gaps: Repositories (source unavailable), API description (no source). Every repository HEY holds has stopped answering.

HEY can answer 17 of the 19 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 3 meaningful events in the last 30 days, the newest 2026-10-15.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 12 Oct) · 8 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 2 commitsCode changes, week of 2026-09-28 – 2026-10-04 · 2 commits+1 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source7 registered sources, 0 of them context only.ReadRecordsCode changes this week (since Mon 12 Oct) · 8 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 2 commitsCode changes, week of 2026-09-28 – 2026-10-04 · 2 commits+6 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Token verified.
Token verified: the project's own site, a deploy record in its own repository, or an on-chain signature names this contract.
SourceThe project's own published sources and HEY's check of the contract.ReadWhat HEY derivedToken verified: the project’s own site names it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Active market.
Active market: the pool holds liquidity and the token traded in the last day.
Source8 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Active market”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Market figures are context only and never change activity status. Methodology
LinksWebsiteGitHubXDEX ScreenerRHToolsSources

Latest ship

Checked

Code changes this week (since Mon 12 Oct) · 8 commits

Code activitySource linked

What changed, in the repository’s own words:

2 active days in 0pen-zaps/openzaps.

This week HEY looked inside 1 of 8 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

Record ship:34c982b1… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 5 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about OpenZaps — as of 2026-10-18

Is OpenZaps still being built?
DerivedShipping: 3 meaningful events in 30 days; latest ship 3 days ago. Evidence
What did OpenZaps ship last?
FactCode changes this week (since Mon 12 Oct) · 8 commits — Code activity, 3 days ago. Evidence
Is 0xDd90bFa4adC7F4401E611AbaC692D939F9F4CB07 OpenZaps’s own contract?
FactToken verified: The project’s own site names this contract. Details
What does HEY not know about OpenZaps?
Unknown2 gaps: Repositories (source unavailable), API description (no source). Every repository HEY holds has stopped answering. Details

Build timeline

  1. Code changes, week of 2026-10-05 – 2026-10-11 · 2 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in 0pen-zaps/openzaps.

    This week HEY looked inside 1 of 2 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence

  2. Code changes, week of 2026-09-28 – 2026-10-04 · 2 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in 0pen-zaps/openzaps.

    This week HEY looked inside 1 of 2 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence

  3. Code changes, week of 2026-08-31 – 2026-09-06 · 3 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in 0pen-zaps/openzaps.

    This week HEY looked inside 1 of 3 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence

  4. Inspect the first fixed 0xZAPS fee campaign

    AnnouncementSource linked

    Inspect the separately funded 2026 campaign, active from Aug 3 00:23 UTC until Aug 10 00:23 UTC; claims remain available until Sep 9 00:23 UTC. It uses 50 of 100 tokenized Clanker fee shares, 0xZAPS stake principal, and WETH-only campaign rewards allocated by time-weighted… Show all

    Inspect the separately funded 2026 campaign, active from Aug 3 00:23 UTC until Aug 10 00:23 UTC; claims remain available until Sep 9 00:23 UTC. It uses 50 of 100 tokenized Clanker fee shares, 0xZAPS stake principal, and WETH-only campaign rewards allocated by time-weighted stake. Holding 0xZAPS alone grants no fee rights.

    View evidence

  5. Practice deployed routes in Virtual Trading

    AnnouncementSource linked

    Paper-trade the deployed 0xZAPS/USDG and aeWETH/USDG routes with 10,000 virtual USDG and live read-only quotes, without a wallet or real funds.

    View evidence

  6. Request a bounded Zap workflow

    AnnouncementSource linked

    Submit one DeFi workflow to request a human-reviewed authority map covering what an agent may trigger and what it can never change. Request a Zap: https://www.0xzaps.com/request-a-zap?utm_source=openzaps&utm_medium=rss&utm_campaign=request_a_zap&utm_content=feed_update

    View evidence

  7. Connect an agent with the OpenZaps Agent Kit

    AnnouncementSource linked

    The published SDK compiles exact policy and unsigned EIP-712 artifacts; the read-only MCP server discovers capsules and can request deployment-gated, block-pinned simulation. Neither package signs or broadcasts. Explore the Agent Kit… Show all

    The published SDK compiles exact policy and unsigned EIP-712 artifacts; the read-only MCP server discovers capsules and can request deployment-gated, block-pinned simulation. Neither package signs or broadcasts. Explore the Agent Kit: https://www.0xzaps.com/agent-kit?utm_source=openzaps&utm_medium=rss&utm_campaign=agent_kit&utm_content=feed_update

    View evidence

  8. Give an Agent the Trigger, Never the Authority

    AnnouncementSource linked

    Read the source-reviewed walkthrough on DeFi Tutorials. Verify every bound before using real funds.

    View evidence

  9. Give an agent the trigger, never the authority

    AnnouncementSource linked

    How OpenZaps separates owner creation authority, immutable execution authority, and the executor that submits a due run.

    View evidence

  10. Verify OpenZaps activity from chain evidence

    AnnouncementSource linked

    The OpenZaps explorer exposes factory-derived Zaps, executions, automated runs, recoveries, and the block used for each live read.

    View evidence

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about OpenZaps? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

19 changes on HEY’s record for OpenZaps: 1 contract in use again or for the first time · 7 other ships · 1 build pace change · 6 market moves · 4 other changes in 1 more kind.

All 19 changes for OpenZaps →

The full change record holds 10 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 17 of the 19 research questions that apply.

17 of 19 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 4m ago.
  • RepositoriesSource unavailableEvery repository HEY holds has stopped answering.
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 1h ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 20d ago.

Code and packages

  • Published packagesMeasuredRead 42m ago.
  • Package advisoriesMeasuredRead 5d ago.

Contracts

  • Contract creationMeasuredRead 1mo ago.
  • Contract activityMeasuredRead yesterday.
  • Verified sourceMeasuredRead 3d ago.
  • Contract interfaceMeasuredRead 3d ago.

Market

  • Current marketMeasuredRead 3m ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead yesterday.
  • LocksMeasuredRead 3h ago.
  • Market checksMeasured

Not applicable here: Repository details, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources

Security context: a published security contact. An audit shows an audit took place; it is not a guarantee of safety.

Contract
0xdd90…cb070xdd90bfa4adc7f4401e611abac692d939f9f4cb07