Skip to content
HEY Research Lab
Menu

Verge Snowy x402

$VERGE402

AI Agents

Contract 0xb73b18267d23087e3af1390edfeb8c4308921d59

HEY holds 9 other Robinhood Chain tokens with the ticker $VERGE402. This page is only the contract above. See them

Is this your project? Claim it →

HTTP 402 for AI agents. Robinhood-native facilitator for x402 micropayments. Settled in 400ms, 0.5% fee. Verge is an HTTP 402 gateway and SDK. Your server returns a payment challenge, the caller pays on a supported rail, then retries with the transaction proof. Robinhood Chain + USDG is the default; other rails are selected with a single network option. Build paid APIs for agents, apps, and users.

Read more

What HEY knows

Development

Quiet for 42 daysQuiet: 0 counted ships in 30 days; latest ship 42 days ago. Evidence Source

Build Momentum 14How it is measured

Latest: Code changes, week of 2026-09-28 – 2026-10-04 · 12 commits

Token market · context

Low liquidity

Token check

Project names this contract
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Verge Snowy x402 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 Verge Snowy x402

No account? Email me Verge Snowy x402’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
Discovery Gap not measured — 24h volume under $1,000. What the Discovery Gap is
More detail
Product usage
Fact1 of 1 watched contract active · 10 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
Unknown2 gaps: API description (not enough yet), Official site changes (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
Quiet.
“Quiet” by the activity rule: 0 counted ships in the last 30 days, the newest 2026-10-01.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-28 – 2026-10-04 · 12 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 56 commitsv1.2.0 — ZK batch proofs + standalone facilitator binaryWhat HEY derivedHEY’s activity rule reads the counted events as “Quiet”.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.
Source5 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-09-28 – 2026-10-04 · 12 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 56 commitsv1.2.0 — ZK batch proofs + standalone facilitator binary+5 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.
Low liquidity.
Low liquidity: the pool holds less than $5,000 of liquidity.
Source8 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Low liquidity”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Discovery Gap: Not measured — 24h volume under $1,000.
Not measured — market too thin: the tracked token's market reads “Low liquidity” but traded $0 in the 24 hours of its reading, under the $1,000 a measured market needs. A Discovery Gap is measured only on an active market that is more than a launch curve and trades at least $1,000 a day: a thin market's attention percentile sits near the floor, so its gap would measure the thinness, not the building.
SourceThe score row: the Build Momentum percentile and the market-attention percentile, both taken over the projects with a market reading.ReadWhat HEY derivedNot measured — market too thin.Not concludedIt compares building with market attention; it is not a prediction and not a reason to trade.
Research coverage: HEY can answer 17 of the 19 research questions that apply.
17 of 19 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 46d ago.

Building

  • Building activityMeasuredRead 19h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 46d ago.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 2d ago.
  • API descriptionNot enough yetHEY has not read its website’s published files yet.
  • Official site changesNot enough yetHEY has no first reading of its website to compare against yet.

Code and packages

  • Repository detailsMeasuredRead 18h ago.
  • Published packagesMeasuredRead 18h ago.

Contracts

  • Contract creationMeasuredRead 6d ago.
  • Contract activityMeasuredRead 3d ago.
  • Published source codeMeasuredRead 3d ago.
  • Contract interfaceMeasuredRead 3d ago.

Market

  • Current marketMeasuredRead 3h ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead 13d ago.
  • LocksMeasuredRead 2h ago.
  • Market checksMeasured

Not applicable here: Package advisories, 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, week of 2026-09-28 – 2026-10-04 · 12 commits

Code activitySource-backed

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

What changed, in the repository’s own words:

3 active days in vergex402/verge.

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

Record ship:e8b38c03… · 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 2 commits 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-10-01; HEY first knew on 2026-09-28.
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)

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-09-21 – 2026-09-27 · 56 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    5 active days in vergex402/verge.

    How HEY read this week

    This week HEY looked inside 4 of 56 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 · 56 commits (opens in a new tab)

  2. 4 releases in vergex402/verge on 27 Sep

    GitHub release

    Show all 4 releases

    1. v1.2.0 — ZK batch proofs + standalone facilitator binary

      GitHub releaseSource-backed

      v1.2.0 — ZK batch proofs + standalone facilitator binary The final two roadmap items. Roadmap is now 100% shipped. ZK batch settlement proofs (zk/) Real Groth16 SNARK over a Poseidon Merkle tree of settlement leaves. · Circuit compiled: 3468 constraints, 2 public inputs (root… Show all
      • v1.2.0 — ZK batch proofs + standalone facilitator binary The final two roadmap items. Roadmap is now 100% shipped. ZK batch settlement proofs (zk/) Real Groth16 SNARK over a Poseidon Merkle tree of settlement leaves.
      • Circuit compiled: 3468 constraints, 2 public inputs (root, numLeaves), 32 private
      • Proven + verified: snarkjs groth16 verify → OK
      • Solidity verifier generated (verifier.sol) — deployable on-chain
      • Negative test: corrupted root rejected at witness generation
      • Design: positional (index-ordered) Merkle removes the entire…
      View evidence: v1.2.0 — ZK batch proofs + standalone facilitator binary (opens in a new tab)

    2. v1.1.0 — Merkle batch settlement proofs

      GitHub releaseSource-backed

      v1.1.0 — Merkle Batch Settlement Proofs Tamper-evident settlement history. Anyone can verify any payment was in a batch — cryptographically, without trusting Verge. How it works POST /api/proofs → picks up all unbatched settlements → builds SHA3-256 Merkle tree (commutative… Show all

      v1.1.0 — Merkle Batch Settlement Proofs Tamper-evident settlement history. Anyone can verify any payment was in a batch — cryptographically, without trusting Verge. How it works POST /api/proofs → picks up all unbatched settlements → builds SHA3-256 Merkle tree (commutative sorted pairs) → stores root in proof_batches table → returns { batchId, merkleRoot, leafCount } GET /api/proofs?batch= &settle= → returns { leaf, proof: string[], merkleRoot } → verify offline in 5 lines of JS (see below) Verify any settlement offline import { createHash } from…

      View evidence: v1.1.0 — Merkle batch settlement proofs (opens in a new tab)

    3. v1.0.0 — Fastify adapter, self-host binary, multi-chain analytics

      GitHub releaseSource-backed

      v1.0.0 — Complete roadmap: Fastify adapter, self-host binary, multi-chain analytics All Q4 2026 roadmap items are now shipped. Full open-source stack. --- @vergex402/fastify — Fastify v4 adapter npm install @vergex402/fastify import Fastify from "fastify"; import { paywall }… Show all

      v1.0.0 — Complete roadmap: Fastify adapter, self-host binary, multi-chain analytics All Q4 2026 roadmap items are now shipped. Full open-source stack. --- @vergex402/fastify — Fastify v4 adapter npm install @vergex402/fastify import Fastify from "fastify"; import { paywall } from "@vergex402/fastify"; const app = Fastify(); app.register(paywall({ amount: 0.001, // USDG per request recipient: process.env.WALLET!, network: "robinhood-mainnet", })); app.get("/api/data", async (req, reply) => { return { data: "unlocked" }; }); Uses Fastify v4's onRequest hook.…

      View evidence: v1.0.0 — Fastify adapter, self-host binary, multi-chain analytics (opens in a new tab)

    4. v0.9.0 — @vergex402/ai-sdk, Revenue Splits, Live Feed, MCP Server

      GitHub releaseSource-backed

      v0.9.0 — Vercel AI SDK gate, Revenue Splits, Live Feed, MCP Server 🆕 New SDKs @vergex402/ai-sdk — Vercel AI SDK v7 middleware Gate any AI route or wrap any model with per-call USDG payment. // Server: monetize a Next.js AI route import { createX402Gate } from… Show all

      v0.9.0 — Vercel AI SDK gate, Revenue Splits, Live Feed, MCP Server 🆕 New SDKs @vergex402/ai-sdk — Vercel AI SDK v7 middleware Gate any AI route or wrap any model with per-call USDG payment. // Server: monetize a Next.js AI route import { createX402Gate } from "@vergex402/ai-sdk"; const { POST: gate } = createX402Gate({ amount: 0.001, recipient: "0x..." }); // Agent: pay automatically before each model call import { wrapWith402 } from "@vergex402/ai-sdk"; const model = wrapWith402(openai("gpt-4o-mini"), { endpoint, privateKey }); npm install…

      View evidence: v0.9.0 — @vergex402/ai-sdk, Revenue Splits, Live Feed, MCP Server (opens in a new tab)

Other changes on HEY’s record

28 changes on HEY’s record for Verge Snowy x402: 4 releases · 1 new Verified Builder or owner proof · 1 token check change · 1 new project on HEY · 21 other changes in 3 more kinds.

All 28 changes for Verge Snowy x402 →

The full change record holds 12 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 0xb73B18267d23087e3aF1390edFeB8c4308921D59 on Robinhood Chain

0xb73b…1d590xb73b18267d23087e3af1390edfeb8c4308921d59

Project names this contract.

Market context

Low liquidity · FDV (fully diluted) $3.1K · current liquidity $4.8K · reading 3 h old (GeckoTerminal).

Token

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

Market

24h volume
$0
Trades 24h
0 buys · 0 sells
Price 24h
unchanged over 24 hours· 6hunchanged over 6 hours· 1hunchanged over 1 hour

The tracked token has a small pool. Trades move the price a lot.

Market history, trading and checks →

Market integrity

Liquidity is 70% below the level it held two days running ($16.0K, 2026-10-18).

Market
Low liquidity
Last day with trading
2026-11-09

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-12 06:55 UTC · How HEY checks this

Sources

5 places HEY reads for Verge Snowy x402