Skip to content
HEY Research Lab
Menu

Verdex

$VERDEX

RWA

Contract 0x96f455a90a80dcf0c2df6703ea4ba3bedf286e43

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

Is this your project? Claim it →

The front door to tokenized markets. 226 real-world assets, 12 issuers, 70 chains, one order.

What HEY knows

Development

Last shipped 42 days agoActive: 0 counted ships in 30 days; latest ship 42 days ago. Evidence Source

Build Momentum 18How it is measured

Latest: Deployed a new contract: VerdexLeverage

Token market · context

Active market$23K fully diluted valuation

Token check

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

Get updates

Follow puts Verdex 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 Verdex

No account? Email me Verdex’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, and the market already notices it, among comparable projects: its building is ahead of 89.6% of them, its market attention ahead of 75.2% (a gap of 14.4). 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 · 3,393 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
Fact8 contracts on record for code changes, 6 with published source code; latest change 42 days ago: Deployed a new contract: VerdexLeverage. Source
Not yet known
Unknown4 gaps: Repositories (no source), Releases (no source), Official docs (no source), Official site changes (not enough yet). No repository the project claims as its own.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Active.
“Active” by the activity rule's longer window: 7 counted ships in the last 45 days (the rule needs at least 2); the newest, 2026-10-04, is more than 30 days old.
SourceHEY holds no repository, changelog or feed it can read for this project; the status rests on building events it counted from the chain or from corroborated sources.ReadRecordsDeployed a new contract: VerdexLeverageDeployed a new contract: 0x5b6d…dd0bDeployed a new contract: VerdexLend+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.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".
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 — the project’s own site names it in its own script.
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 in its own script.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 12 of the 16 research questions that apply.
12 of 16 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 48d ago.

Building

  • Building activityMeasured
  • RepositoriesNo sourceNo repository the project claims as its own.
  • ReleasesNo sourceNo source HEY reads releases from.
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • Official site changesNot enough yetHEY has no first reading of its website to compare against yet.

Contracts

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

Market

  • Current marketMeasuredRead 48m ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead today.
  • LocksMeasuredRead 6m ago.
  • Market checksMeasured

Not applicable here: API description, Repository details, Published packages, 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)X (opens in a new tab)DEX Screener (opens in a new tab)RHTools (opens in a new tab)Sources

Latest ship

Deployed a new contract: VerdexLeverage

New contractSource-backed

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

The account that launched Verdex’s token deployed VerdexLeverage at 0x2763…3ef5 on 2026-10-04. Read from the chain; the creating transaction is the evidence.

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

Contract deployment, recorded on chain · no release names it
What it names
A new contract. The chain record names no capability.
Stage
A contract on chain. A deployment says nothing about whether anything uses it.
Reported by
Recorded on chain. Independently recorded: HEY read it from the chain, not from the team.
Release and deployment
Not established: no release text HEY holds names this contract. Timing alone never links a release to a deployment.
Activity
HEY does not count calls to 0x2763…3ef5 (a contract the project’s deployer put up) for this project. Its activity is not measured, not zero.
When
The source dates it 2026-10-04 21:22 UTC; HEY first knew on 2026-10-05. HEY indexed it later, as history.
Not known
  • No source HEY holds names what this change does.
  • Not established: no release text HEY holds names this contract. Timing alone never links a release to a deployment.
  • HEY does not count calls to 0x2763…3ef5 (a contract the project’s deployer put up) for this project. Its activity is not measured, not zero.

Evidence: ship record

A contract record says what the chain shows about a contract. It is not a safety check, and it does not say who runs the contract.

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

Build timeline

  1. Deployed a new contract: 0x5b6d…dd0b

    New contractSource-backed

    The account that launched Verdex’s token deployed 0x5b6d…dd0b on 2026-10-04. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0x5b6d…dd0b (opens in a new tab)

  2. Deployed a new contract: VerdexLend

    New contractSource-backed

    The account that launched Verdex’s token deployed VerdexLend at 0xc565…c6bb on 2026-10-04. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: VerdexLend (opens in a new tab)

  3. Deployed a new contract: 0xb3b6…395b

    New contractSource-backed

    The account that launched Verdex’s token deployed 0xb3b6…395b on 2026-10-04. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0xb3b6…395b (opens in a new tab)

  4. Deployed a new contract: 0x45de…d4c9

    New contractSource-backed

    The account that launched Verdex’s token deployed 0x45de…d4c9 on 2026-10-04. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0x45de…d4c9 (opens in a new tab)

  5. Deployed a new contract: 0xba49…ca23

    New contractSource-backed

    The account that launched Verdex’s token deployed 0xba49…ca23 on 2026-10-04. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0xba49…ca23 (opens in a new tab)

  6. Deployed a new contract: 0x56b2…0b9b

    New contractSource-backed

    The account that launched Verdex’s token deployed 0x56b2…0b9b on 2026-10-02. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0x56b2…0b9b (opens in a new tab)

Other changes on HEY’s record

17 changes on HEY’s record for Verdex: 1 token check change · 1 market check · 1 new project on HEY · 7 contract changes · 7 other changes in 1 more kind.

All 17 changes for Verdex →

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

0x96f4…6e430x96f455a90a80dcf0c2df6703ea4ba3bedf286e43

Project names this contract: The project’s own site names this contract in one of its own script files.

Market context

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

Token

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

Market

24h volume
$3.8K
Trades 24h
45 buys · 28 sells
Price 24h
down 25.7 percent over 24 hours· 6hdown 0.1 percent over 6 hours

The tracked token has liquidity, and trading volume was read for it within a day of its newest market reading — in that reading, or in HEY’s record of on-chain trades.

Market history, trading and checks →

Market integrity

Liquidity is 74% below the level it held two days running ($45.7K, 2026-10-14).

Market
Active market
Last day with trading
2026-11-14
  1. seen 2026-10-10Trading fell from 2,730 trades a day (the seven days to 2026-09-30) to 52 a day in the seven days to 2026-11-10, 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-15 12:55 UTC · How HEY checks this

Sources

2 places HEY reads for Verdex