Skip to content
HEY Research Lab
Menu

Agent Wormhole

$WORM

AI Agents

Contract 0x3ba500f1ababbcf0f0247d06d1c56fd7e6c4c09d

HEY holds 357 other Robinhood Chain tokens that use $WORM. This page is only the contract above. See them

Is this your project? Claim it →

The security layer for agentic finance.

What HEY knows

Development

Shipped this weekShipping: 2 counted ships in 30 days; latest ship yesterday. Evidence Source

Build Momentum 33How it is measured

Latest: Code changes this week (since Mon 2 Nov) · 9 commits

Token market · context

Active market$2.4M fully diluted valuation

Token check

Project names this contract
FollowCreate alertTerminal preview
Get updates

Get updates

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

Sign in to follow Agent Wormhole

No account? Email me Agent Wormhole’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.

View latest ship
Share
Attention
Building and market attention rank about level among comparable projects: its building is ahead of 95.5% of them, its market attention ahead of 97.4% (a gap of -1.9). What the Discovery Gap is

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

More detail
Product usage
Fact1 of 1 watched contract active · 221,013 calls in 7 days — all token transfers and approvals (ERC-20), which trading alone produces; none reached another function HEY watches.

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

Contracts
Fact1 contract on record for code changes, 1 with published source code; no implementation or interface change recorded.
Not yet known
Unknown1 gap: API description (not enough yet). HEY has not read its website’s published files yet.
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: 2 counted ships in the last 30 days, the newest 2026-11-02.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 2 Nov) · 9 commitsCode changes, week of 2026-10-26 – 2026-11-01 · 17 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 78 commits+2 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 counted building from the project's own sources.
Source14 registered sources, 0 of them context only.ReadRecordsCode changes this week (since Mon 2 Nov) · 9 commitsCode changes, week of 2026-10-26 – 2026-11-01 · 17 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 78 commits+7 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.
Project names this contract.
Project names this contract: 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 derivedProject names this contract: 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.
Research coverage: HEY can answer 19 of the 20 research questions that apply.
19 of 20 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 50m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 3mo ago.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 2h ago.
  • API descriptionNot enough yetHEY has not read its website’s published files yet.
  • Official site changesMeasuredRead 1d ago.

Code and packages

  • Repository detailsMeasuredRead 6d ago.
  • Published packagesMeasuredRead 18m ago.
  • Package advisoriesMeasuredRead 6d ago.

Contracts

  • Contract creationMeasuredRead 1d ago.
  • Contract activityMeasuredRead yesterday.
  • Published source codeMeasuredRead 5d ago.
  • Contract interfaceMeasuredRead 5d ago.

Market

  • Current marketMeasuredRead 17m ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead yesterday.
  • LocksMeasuredRead 45m ago.
  • Market checksMeasured

Not applicable here: 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.

Market figures are context only and never change activity status. Methodology
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)X (opens in a new tab)DEX Screener (opens in a new tab)RHTools (opens in a new tab)Sources

Latest ship

Checked

Code changes this week (since Mon 2 Nov) · 9 commits

Code activitySource-backed

What changed, in the repository’s own words:

1 active day in runningoffcode/agent-wormhole.

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

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

Code changes, read from the team’s GitHub · not a deployment
What it names
1 of 1 commit HEY read changed code. A week of code names no capability.
Stage
Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not a release or a deployment: code is not a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it to the week of 2026-11-02; HEY first knew on 2026-11-02.
Not known
  • No source HEY holds names what this change does.
  • HEY has not observed a deployment of this change.

Evidence: ship record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

View evidence ↗ (opens in a new tab)

Shared change · Official source change

Agent Wormhole's official site changed.

Links the official site declares changed: 1 added, 0 removed. Added docs link….

Observed by HEY on 2026-11-02Source: Project’s official site

View evidence ↗Evidence receipt

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: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes, week of 2026-10-26 – 2026-11-01 · 17 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in runningoffcode/agent-wormhole.

    How HEY read this week

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

    View evidence: Code changes, week of 2026-10-26 – 2026-11-01 · 17 commits (opens in a new tab)

  2. Code changes, week of 2026-09-21 – 2026-09-27 · 78 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    5 active days in runningoffcode/agent-wormhole.

    How HEY read this week

    This week HEY looked inside 4 of 78 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 78 commits (opens in a new tab)

  3. Code changes, week of 2026-09-14 – 2026-09-20 · at least 9 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    4 active days in runningoffcode/agent-wormhole.

    How HEY read this week

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

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 9 commits (opens in a new tab)

  4. 3 releases in runningoffcode/agent-wormhole on 26 Jul

    GitHub release

    Show all 3 releases

    1. wormhole-guard 0.1.2

      GitHub releaseSource-backed

      On-chain memos: a permissionless injection channel New wormhole memos command and readguard coverage for the one inbound channel that requires nothing of the agent. Every other vector needs the agent to go somewhere — fetch a page, clone a repo, install a skill. An on-chain memo… Show all

      On-chain memos: a permissionless injection channel New wormhole memos command and readguard coverage for the one inbound channel that requires nothing of the agent. Every other vector needs the agent to go somewhere — fetch a page, clone a repo, install a skill. An on-chain memo needs none of that: anyone can pay a fraction of a cent to write arbitrary text into an agent's transaction history, unsolicited. The payload lands when the agent reads its own history, and it arrives as tool output. The worm case is why this ships beside the config scanners rather than in the payment guard: a…

      View evidence: wormhole-guard 0.1.2 (opens in a new tab)

    2. wormhole-x402 0.1.3

      GitHub releaseSource-backed

      Security hardening from the post-launch review, plus first-class facilitator support. Closed bypasses · guardSigner now guards every signing method a wallet exposes — signAllTransactions, signAndSendTransaction, and signAndSendAllTransactions previously routed around the check… Show all
      • Security hardening from the post-launch review, plus first-class facilitator support. Closed bypasses
      • guardSigner now guards every signing method a wallet exposes — signAllTransactions, signAndSendTransaction, and signAndSendAllTransactions previously routed around the check entirely.
      • The System program is now a strict allowlist (only AdvanceNonceAccount passes). TransferWithSeed, Assign, WithdrawNonceAccount, allocation instructions, and unclassifiable tags are refused (X402-007 / new X402-009).
      • Burn / BurnChecked riding beside a correct payment are refused…
      View evidence: wormhole-x402 0.1.3 (opens in a new tab)

    3. wormhole-guard 0.1.1 · wormhole-x402 0.1.2

      GitHub releaseSource-backed

      Two packages, one thesis: an agent obeys instructions it did not write, so the places those instructions live need integrity checks. wormhole-guard (PyPI, Python 3.8+, zero dependencies) — integrity monitoring and hardening for agent instruction files (AGENTS.md, CLAUDE.md… Show all

      Two packages, one thesis: an agent obeys instructions it did not write, so the places those instructions live need integrity checks. wormhole-guard (PyPI, Python 3.8+, zero dependencies) — integrity monitoring and hardening for agent instruction files (AGENTS.md, CLAUDE.md, .cursor/rules, and eleven more formats), MCP tool definitions, and agent-to-agent handoffs. Prevention first: harden drops the write bit and pre-creates absent config paths, guard inspects writes before they land, outbound refuses to pass a payload to another agent. Detection rules are triage on top, and…

      View evidence: wormhole-guard 0.1.1 · wormhole-x402 0.1.2 (opens in a new tab)

Other changes on HEY’s record

17 changes on HEY’s record for Agent Wormhole: 3 releases · 1 new Verified Builder or owner proof · 1 market check · 1 official source change · 11 other changes in 2 more kinds.

All 17 changes for Agent Wormhole →

The full change record holds 23 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

The token’s market, checks, locks and stamps below are context only: none of it changes activity status or Build Momentum.

Contract 0x3bA500F1AbabbCF0F0247D06D1c56Fd7E6C4c09D on Robinhood Chain

0x3ba5…c09d0x3ba500f1ababbcf0f0247d06d1c56fd7e6c4c09d

Project names this contract.

Market context

Active market · FDV (fully diluted) $2.4M · current liquidity $252K · reading under an hour old (DEX Screener).

Token

Launch stage
Trading in a DEX pool
Pair age
56d ago

Market

24h volume
$294K
Trades 24h
2,128 buys · 1,832 sells
Price 24h
down 6.8 percent over 24 hours· 6hup 14.6 percent over 6 hours· 1hdown 0.7 percent over 1 hour

The tracked token has liquidity and traded in the last 24 hours.

Market history, trading and checks →

Market integrity

Liquidity is 6% below the level it held two days running ($260.3K, 2026-10-31).

Market
Active market
Last day with trading
2026-11-02
  1. seen 2026-09-29Trading fell from 119,970 trades a day (the seven days to 2026-09-22) to 10,082 a day in the seven days to 2026-09-29, in HEY's decoded on-chain trades.

From HEY’s own daily readings of the token’s pools and its decoded on-chain trades, and the locker’s record · checked 2026-11-03 06:52 UTC · How HEY checks this

Locks

Token supply locked
1.52%
Next unlock
2026-11-30 · 0.52% of supply
Last unlock
2026-12-31
Pair locked
Not applicable

Locked by HoodLock, read from the locker contract HEY watches. No locked pair holds this token; most pools on this chain have no pair token to lock. Locked supply says what cannot move today, not that the price will do anything.

Questions HEY can answer about Agent Wormhole — as of 3 Nov

Show the answers
Is Agent Wormhole still being built?
DerivedShipping: 2 counted ships in 30 days; latest ship yesterday. Evidence
What did Agent Wormhole ship last?
FactCode changes this week (since Mon 2 Nov) · 9 commits — Code activity, yesterday. Evidence
Is 0x3bA500F1AbabbCF0F0247D06D1c56Fd7E6C4c09D Agent Wormhole’s own contract?
FactProject names this contract: The project’s own site names this contract. Details
What does HEY not know about Agent Wormhole?
Unknown1 gap: API description (not enough yet). HEY has not read its website’s published files yet.

Sources

14 places HEY reads for Agent Wormhole
7 more sources (docs)