DarkWalletRH

Builder activity

Build timeline

1. Dark Contracts 1.0.4: Audit package

   22h ago

   GitHub release · Source verified

   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 allShow less

   • 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 evidenceShare

2. Code changes, week of 2026-10-05 – 2026-10-11 · 6 commits

   22h ago

   Code activity · Source linked

   5 active days in darkwalletrh/dark-contracts.

   What changed, in the repository’s own words:

   • Dark Contracts 1.0.4: audit package (AUDIT.md, protocol spec, threat model, invariants, mutation and circuit reports)
   • CI: pin every action to a commit SHA
   • Dark Contracts 1.0.3: corrected mutation harness, pinned CI

   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

3. Dark Contracts 1.0.3: Corrected mutation harness

   2d ago

   GitHub release · Source verified

   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 allShow less

   • 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 evidenceShare

4. Dark SDK 0.4.3: Robustness and hardening

   2d ago

   GitHub release · Source verified

   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 allShow less

   • 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 evidenceShare

5. Dark Contracts 1.0.2: Documentation release

   2d ago

   GitHub release · Source verified

   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 allShow less

   • 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 evidenceShare

6. Dark Contracts 1.0.1: Audit package

   2d ago

   GitHub release · Source verified

   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 allShow less

   • 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 evidenceShare

7. Dark Contracts 0.9.0: Hardened testnet release

   2d ago

   GitHub release · Source verified

   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 allShow less

   • 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 evidenceShare

8. Dark Contracts 1.0.0: Mainnet launch

   2d ago

   GitHub release · Source verified

   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 allShow less

   • 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 evidenceShare

9. Dark SDK 0.4.2: Recipient key cross-check

   2d ago

   GitHub release · Source verified

   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 allShow less

   • 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 evidenceShare

10. Dark SDK 0.4.1: Standalone tests and CI

    2d ago

    GitHub release · Source verified

    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 allShow less

    • 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 evidenceShare

11. Dark SDK 0.4.0: Mainnet support

    2d ago

    GitHub release · Source verified

    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 allShow less

    • 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 evidenceShare

12. Dark SDK 0.3.2

    2d ago

    GitHub release · Source verified

    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 allShow less

    • 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 evidenceShare

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about DarkWalletRH? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

Research coverage

HEY can answer 8 of the 10 research questions that apply.

Sources

• Website
  https://darkwallet.cash/docsUnverified
• Docs
  https://darkwallet.cash/docsOfficial
• Repository
  https://github.com/DarkWalletRH/dark-contractsOfficial
• Repository
  https://github.com/DarkWalletRH/dark-sdkOfficial
• GitHub org
  https://github.com/DarkWalletRHOfficial
• X
  https://x.com/darkwalletrhOfficial