Skip to content
Menu

DarkRoute

$dark

StockFi

Contract 0xebb4c5b97e4117e30ec82ce025e6f21dded05436

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

Is this your project? Claim and verify →

Private swaps that still tell the truth. Pick a pair, paste an address, and DarkRoute routes the order through hidden liquidity, then shows you the real venue and a 0.3% fee. Every swap pays cashback in tokenized stocks. Hold $DARK, pay less.

Read more

What HEY knows

Building
Last shipped 40 days agoActive: 0 meaningful events in 30 days; latest ship 40 days ago. Evidence Source

Build Momentum 14How it is measured

Latest ship
Code changes, week of 2026-09-14 – 2026-09-20 · at least 1 commit · · Code activity
This change
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-09-16; HEY first knew on 2026-09-16. HEY indexed it later, as history.
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.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts DarkRoute 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 DarkRoute’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 — market too thin. What the Discovery Gap is
Product usage
Fact1 of 1 watched contract active · 747 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 verified source; no implementation or interface change recorded.
Token market · context
Active market$10K fully diluted valuationToken verified

Same ticker, different contract: 2 other published projects use the ticker $DARK. This page: its site darkroute.exchange names 0xebb4…5436. Dark Arena: no official source HEY read names 0xd1d4…90da; Darkwoods: its site darkwoods.ai does not name 0xdc45…b54e. HEY does not say which is the real one — only what each project’s own sources name.

Not yet known
Unknown1 gap: API description (no source). Its website links no API description.

HEY can answer 18 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
Active.
“Active” by the activity rule's longer window: 2 meaningful events in the last 45 days (the rule needs at least 2); the newest, 2026-09-16, is more than 30 days old.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · at least 1 commitCode changes, week of 2026-09-07 – 2026-09-13 · at least 2 commitsWhat 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".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source5 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · at least 1 commitCode changes, week of 2026-09-07 – 2026-09-13 · at least 2 commitssource:988092cf-e430-4ce5-9396-e47ed016e3a6+3 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.
Source9 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.
Discovery Gap: Not measured — market too thin.
Not measured — market too thin: the tracked token's market reads “Active market” but traded $666.83 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.
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-14 – 2026-09-20 · at least 1 commit

Code activitySource linked

What changed, in the repository’s own words:

3 active days in darkrouteRH/contracts.

This week HEY looked inside 1 commit to see what changed: 1 changed code.

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

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.

Questions HEY can answer about DarkRoute — as of 26 Oct

Is DarkRoute still being built?
DerivedActive: 0 meaningful events in 30 days; latest ship 40 days ago. Evidence
What did DarkRoute ship last?
FactCode changes, week of 2026-09-14 – 2026-09-20 · at least 1 commit — Code activity, 40 days ago. Evidence
Is 0xebB4C5B97E4117e30EC82ce025E6f21dded05436 DarkRoute’s own contract?
FactToken verified: The project’s own site names this contract. Details
What does HEY not know about DarkRoute?
Unknown1 gap: API description (no source). Its website links no API description. Details

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-07 – 2026-09-13 · at least 2 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in darkrouteRH/contracts.

    How HEY read this week

    This week HEY looked inside 2 commits to see what changed: 1 changed code, 1 documentation or maintenance only.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · at least 2 commits (opens in a new tab)

What changed

3 changes on HEY’s record for DarkRoute: 1 market check · 2 weeks of code pushed.

  • Market check32d ago

    Trading was 113 trades a day in the seven days to 2026-09-26, down from 8,772 a day at its peak in the seven days to 2026-09-10 (16 days earlier), in HEY's decoded on-chain trades.

    See the change

  • Code pushed40d ago

    Code changes, week of 2026-09-14 – 2026-09-20 · at least 1 commit

    See the change Source ↗

  • Code pushed43d ago

    Code changes, week of 2026-09-07 – 2026-09-13 · at least 2 commits

    See the change Source ↗

DarkRoute on What changed →

The full change record holds 3 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 18 of the 19 research questions that apply.

18 of 19 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 6h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 2d ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 2d ago.

Code and packages

  • Repository detailsMeasuredRead 6d ago.
  • Published packagesMeasuredRead 6d ago.

Contracts

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

Market

  • Current marketMeasuredRead 50m ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead yesterday.
  • LocksMeasuredRead 5h 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.

Sources

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

Contract
0xebb4…54360xebb4c5b97e4117e30ec82ce025e6f21dded05436