Skip to content
Menu

Dark Wallet

$DRKW

Utility

Contract 0x9c6b8a6a86acd2a147b086d2bccfbdfbece37b80

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

Is this your project? Claim it →

Your crypto, minus the audience. The most private wallet on Robinhood Chain.

What HEY knows

Building
Last shipped 6 days agoShipping: 5 counted ships in 30 days; latest ship 6 days ago. Evidence Source

Build Momentum 40How it is measured

Latest
Code changes, week of 2026-10-19 – 2026-10-25 · 1 commit
FollowCreate alertTerminal previewView latest ship
Share

Follow puts Dark Wallet 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 Dark Wallet’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
Product usage
Fact1 of 1 watched contract active · 3 calls to the contracts' own functions in 7 days; the other 34,311 of 34,314 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
Fact1 contract on record for code changes, 1 with verified source; latest change 4 days ago: Contract 0x9c6b…7b80 source verified on the explorer. Source
Token market · context
Active market$4.1K fully diluted valuationProject names this contract
Not yet known
Unknown1 gap: API description (no source). Its website links no API description.
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: 5 counted ships in the last 30 days, the newest 2026-10-22.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-19 – 2026-10-25 · 1 commitCode changes, week of 2026-10-05 – 2026-10-11 · 5 commitsDark Contracts 1.0.4: Audit package+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 verified building evidence from the project's own sources.
Source9 registered sources, 1 of them context only.ReadRecordsCode changes, week of 2026-10-19 – 2026-10-25 · 1 commitCode changes, week of 2026-10-05 – 2026-10-11 · 5 commitsDark Contracts 1.0.4: Audit package+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.
Discovery Gap: Not measured — 24h volume under $1,000.
Not measured — market too thin: the tracked token's market reads “Active market” but traded $156.8 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 18 of the 19 research questions that apply.
18 of 19 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 7d ago.

Building

  • Building activityMeasuredRead 27m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 20d ago.
  • TimelineMeasured

Official site

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

Code and packages

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

Contracts

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

Market

  • Current marketMeasuredRead 18m ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead today.
  • LocksMeasuredRead 1h 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-10-19 – 2026-10-25 · 1 commit darkwalletrh/dark-contracts

Code activitySource-backed

Why it matters: First week of code changes after 14 quiet days.

What changed, in the repository’s own words:

1 active day in darkwalletrh/dark-contracts.

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

Record ship:3b425aff… · 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)

Shared change · Contract source verified

The source code of a Dark Wallet contract was verified on the explorer (0x9c6b…7b80).

Observed by HEY on 2026-10-24Source: Block explorer

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: 8 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-19 – 2026-10-25 · 1 commit darkwalletrh/dark-sdk

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in darkwalletrh/dark-sdk.

    How HEY read this week

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

    View evidence: Code changes, week of 2026-10-19 – 2026-10-25 · 1 commit (opens in a new tab)

  2. Code changes, week of 2026-10-05 – 2026-10-11 · 5 commits darkwalletrh/dark-sdk

    Code activitySource-backed

    What changed, in the repository’s own words:

    3 active days in darkwalletrh/dark-sdk.

    How HEY read this week

    This week HEY looked inside 3 of 5 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-05 – 2026-10-11 · 5 commits (opens in a new tab)

  3. Dark Contracts 1.0.4: Audit package darkwalletrh/dark-contracts

    GitHub releaseSource-backed

    Audit package. No contract or circuit changes: the deployed bytecode is unchanged and still reproduces from this release byte-for-byte. Commit under review: 1ffe0d46c38603b612b165c54de403a5002a0fa6 Start here · AUDIT.md: scope (2,488 hand-written lines plus 7,395 generated… Show all
    • Audit package. No contract or circuit changes: the deployed bytecode is unchanged and still reproduces from this release byte-for-byte. Commit under review: 1ffe0d46c38603b612b165c54de403a5002a0fa6 Start here
    • AUDIT.md: scope (2,488 hand-written lines plus 7,395 generated verifier lines), how to tie this commit to the deployed contracts on both chains, deployments and governance, build and test commands, known issues and accepted risks, and where we would like you to look hardest.…
    View evidence: Dark Contracts 1.0.4: Audit package (opens in a new tab)

  4. Code changes, week of 2026-10-05 – 2026-10-11 · 6 commits darkwalletrh/dark-contracts

    Code activitySource-backed

    What changed, in the repository’s own words:

    3 active days in darkwalletrh/dark-contracts.

    How HEY read this week

    This week HEY looked inside 1 of 6 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-10-05 – 2026-10-11 · 6 commits (opens in a new tab)

  5. 5 releases in darkwalletrh/dark-contracts on 7 Oct

    GitHub release

    Show all 5 releases

    1. Dark Contracts 1.0.3: Corrected mutation harness darkwalletrh/dark-contracts

      GitHub releaseSource-backed

      Test and tooling release. No contract or circuit changes: the deployed bytecode is unchanged and still reproduces from this release byte-for-byte. Changes · The mutation harness (contracts/script/mutate.mjs) now runs an unmutated baseline first, copies everything the suite needs… Show all
      • Test and tooling release. No contract or circuit changes: the deployed bytecode is unchanged and still reproduces from this release byte-for-byte. Changes
      • The mutation harness (contracts/script/mutate.mjs) now runs an unmutated baseline first, copies everything the suite needs into its scratch tree, and counts a mutant as killed only when a test assertion fails; a mutant that fails to compile is reported separately as invalid. The previous harness could report a mutant as killed because of a setup error.
      • Re-run on the corrected harness: 44 mutants, 44 killed, 0 survived, 0…
      View evidence: Dark Contracts 1.0.3: Corrected mutation harness (opens in a new tab)

    2. Dark Contracts 1.0.2: Documentation release darkwalletrh/dark-contracts

      GitHub releaseSource-backed

      Documentation release. No contract or circuit changes: the deployed bytecode is unchanged and still reproduces from this release byte-for-byte. Changes · Comments and tool headers rewritten to state what each check guarantees; stale references and internal labels removed.… Show all
      • Documentation release. No contract or circuit changes: the deployed bytecode is unchanged and still reproduces from this release byte-for-byte. Changes
      • Comments and tool headers rewritten to state what each check guarantees; stale references and internal labels removed.
      • circuits/VERSIONS.toml describes the toolchain pins accurately and drops an unused block.
      • circuits/tools declares its own dependencies and ships a lockfile.
      • The npm package depends on Dark SDK 0.4.2.
      View evidence: Dark Contracts 1.0.2: Documentation release (opens in a new tab)

    3. Dark Contracts 1.0.1: Audit package darkwalletrh/dark-contracts

      GitHub releaseSource-backed

      Audit package. No contract or circuit changes: the deployed bytecode is unchanged and still reproduces from this release byte-for-byte. Changes · Public CI: contract tests, circuit tests, generated-verifier tests, the verifier ↔ circuit tie, and deployed-bytecode reproduction on… Show all
      • Audit package. No contract or circuit changes: the deployed bytecode is unchanged and still reproduces from this release byte-for-byte. Changes
      • Public CI: contract tests, circuit tests, generated-verifier tests, the verifier ↔ circuit tie, and deployed-bytecode reproduction on every push.
      • npm package @darkwalletrh/dark-contracts: ABIs, the deployment record and the verifier pins for integrators.
      • Every mainnet contract is source-verified on Blockscout as an exact match.
      • Documentation: trust model, repository layout, build and test instructions, how to reproduce the deployed…
      View evidence: Dark Contracts 1.0.1: Audit package (opens in a new tab)

    4. Dark Contracts 0.9.0: Hardened testnet release darkwalletrh/dark-contracts

      GitHub releaseSource-backed

      The reviewed, hardened testnet release of Dark's on-chain components. Contents · DarkVault: deposit, apply-pending, private transfer and withdraw over twisted-ElGamal ciphertexts; caps with immutable hard ceilings; a guardian that can pause and tighten caps, nothing else; an… Show all
      • The reviewed, hardened testnet release of Dark's on-chain components. Contents
      • DarkVault: deposit, apply-pending, private transfer and withdraw over twisted-ElGamal ciphertexts; caps with immutable hard ceilings; a guardian that can pause and tighten caps, nothing else; an owner that acts only through a 48-hour timelock. No proxy, no delegatecall, no upgrade path. Withdrawals can never be paused.
      • DarkKeyRegistry: immutable, ownerless key registry proven with dark_register.
      • DarkGrumpkin: clean-room Grumpkin arithmetic, differentially tested against…
      View evidence: Dark Contracts 0.9.0: Hardened testnet release (opens in a new tab)

    5. Dark Contracts 1.0.0: Mainnet launch darkwalletrh/dark-contracts

      GitHub releaseSource-backed

      Mainnet launch. Deployment The contract and circuit source of 0.9.0, unchanged, deployed to Robinhood Chain mainnet (chain id 4663) at block 75151289: | Contract | Address | |---|---| | DarkVault | 0xeD7a…DA9C | | DarkKeyRegistry | 0x2E24…9C87 | | DarkTimelock (owner, 48 h) |… Show all
      • Mainnet launch. Deployment The contract and circuit source of 0.9.0, unchanged, deployed to Robinhood Chain mainnet (chain id 4663) at block 75151289: | Contract | Address | |---|---| | DarkVault | 0xeD7a…DA9C | | DarkKeyRegistry | 0x2E24…9C87 | | DarkTimelock (owner, 48 h) | 0xADbF…BC54 |
      • Owner: the timelock, whose only proposer, executor and canceller is a 2-of-3 Safe. The deployer holds no role.
      • Guardian: a 1-of-2 Safe that can pause deposits and transfers and…
      View evidence: Dark Contracts 1.0.0: Mainnet launch (opens in a new tab)

  6. 5 releases in darkwalletrh/dark-sdk on 7 Oct

    GitHub release

    Show all 5 releases

    1. Dark SDK 0.4.3: Robustness and hardening darkwalletrh/dark-sdk

      GitHub releaseSource-backed

      Robustness and hardening. Upgrading is recommended; no API changes. Changes · One incoming transfer that will not open no longer blocks the wallet. A transfer whose hint cannot be opened (malformed, or above the bound for its block) used to make getBalances, applyPending… Show all
      • Robustness and hardening. Upgrading is recommended; no API changes. Changes
      • One incoming transfer that will not open no longer blocks the wallet. A transfer whose hint cannot be opened (malformed, or above the bound for its block) used to make getBalances, applyPending, history and Dark Exit throw. The pending total is now recovered by a bounded search over the whole pending ciphertext, and that one transfer shows no amount in the history.
      • The solved witness and the prover input, which contain the account's secret, live only in an owner-only temporary directory (0700, files…
      View evidence: Dark SDK 0.4.3: Robustness and hardening (opens in a new tab)

    2. Dark SDK 0.4.2: Recipient key cross-check darkwalletrh/dark-sdk

      GitHub releaseSource-backed

      Security release. Upgrading is recommended for every integration that sends private transfers. Changes · A transfer encrypts to a recipient key only when two independent RPC sources agree on it. The recipient's registry key decides who can read a transfer's amount and note, so… Show all
      • Security release. Upgrading is recommended for every integration that sends private transfers. Changes
      • A transfer encrypts to a recipient key only when two independent RPC sources agree on it. The recipient's registry key decides who can read a transfer's amount and note, so one RPC's answer is no longer enough: LiveDarkClient.transfer() cross-checks registry.keyOf(to) against a second source before it builds the ciphertext and the hint. The second source is the chain's public RPC when the client reads through anything else, or Dark's relay when an api is configured. A…
      View evidence: Dark SDK 0.4.2: Recipient key cross-check (opens in a new tab)

    3. Dark SDK 0.4.1: Standalone tests and CI darkwalletrh/dark-sdk

      GitHub releaseSource-backed

      Maintenance release. No runtime, API or package-metadata changes. Changes · The test suite runs standalone, outside the monorepo it is developed in: the checks that need the Noir workspace skip when circuits/ is absent. · A GitHub Actions workflow runs npm ci, the build and the… Show all
      • Maintenance release. No runtime, API or package-metadata changes. Changes
      • The test suite runs standalone, outside the monorepo it is developed in: the checks that need the Noir workspace skip when circuits/ is absent.
      • A GitHub Actions workflow runs npm ci, the build and the tests on Node 22 for every push. Upgrading from 0.4.0 requires no code changes.
      View evidence: Dark SDK 0.4.1: Standalone tests and CI (opens in a new tab)

    4. Dark SDK 0.4.0: Mainnet support darkwalletrh/dark-sdk

      GitHub releaseSource-backed

      Mainnet support. Changes · deployments[4663] now carries the Robinhood Chain mainnet deployment: vault 0xeD7a…DA9C, key registry, the three verifiers, timelock, guardian and deploy block 75151289. isDeployed(4663) returns true. · The deployment record is read back from chain… Show all
      • Mainnet support. Changes
      • deployments[4663] now carries the Robinhood Chain mainnet deployment: vault 0xeD7a…DA9C, key registry, the three verifiers, timelock, guardian and deploy block 75151289. isDeployed(4663) returns true.
      • The deployment record is read back from chain, not transcribed: every address was cross-checked against the vault's own getters and the pinned verifier codehashes. No API changes. Upgrading from 0.3.2 requires no code changes.
      View evidence: Dark SDK 0.4.0: Mainnet support (opens in a new tab)

    5. Dark SDK 0.3.2 darkwalletrh/dark-sdk

      GitHub releaseSource-backed

      The first public release of the Dark SDK: the TypeScript client for confidential USDG balances on Robinhood Chain. Highlights · Confidential balances. Deterministic privacy-key derivation from an account's secp256k1 key, twisted ElGamal encryption over the Grumpkin curve, and… Show all
      • The first public release of the Dark SDK: the TypeScript client for confidential USDG balances on Robinhood Chain. Highlights
      • Confidential balances. Deterministic privacy-key derivation from an account's secp256k1 key, twisted ElGamal encryption over the Grumpkin curve, and bounded discrete-log decryption.
      • Zero-knowledge proofs. Witnesses and public inputs for the register, transfer, withdraw and disclose_range circuits, proved on Node (NodeDarkProver) or in the browser (WebDarkProver).
      • Live client. LiveDarkClient reads and writes the vault through viem…
      View evidence: Dark SDK 0.3.2 (opens in a new tab)

Other changes on HEY’s record

19 changes on HEY’s record for Dark Wallet: 11 releases · 1 verification change · 1 new project on HEY · 1 contract change · 5 other changes in 2 more kinds.

All 19 changes for Dark Wallet →

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

0x9c6b…7b800x9c6b8a6a86acd2a147b086d2bccfbdfbece37b80

Project names this contract: The project’s own site names this contract.

Market context

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

Token

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

Market

24h volume
$157
Trades 24h
4 buys · 10 sells
Price 24h
down 3.4 percent over 24 hours· 6hup 1.2 percent over 6 hours

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

Market history, trading and checks →

Market integrity

Liquidity is 71% below the level it held two days running ($20.1K, 2026-10-21).

Market
Active market
Last day with trading
2026-10-27

From HEY’s own daily readings of the token’s pools and its decoded on-chain trades, and the locker’s record · checked 2026-10-28 18:53 UTC · How HEY checks this

Questions HEY can answer about Dark Wallet — as of 28 Oct

Show the answers
Is Dark Wallet still being built?
DerivedShipping: 5 counted ships in 30 days; latest ship 6 days ago. Evidence
What did Dark Wallet ship last?
FactCode changes, week of 2026-10-19 – 2026-10-25 · 1 commit — Code activity, 6 days ago. Evidence
Is 0x9c6b8a6A86AcD2a147b086D2bcCfBdfBEce37B80 Dark Wallet’s own contract?
FactProject names this contract: The project’s own site names this contract. Details
What does HEY not know about Dark Wallet?
Unknown1 gap: API description (no source). Its website links no API description.

Sources

9 places HEY reads for Dark Wallet

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