darkpoolVerify the release.
Publish the actual deployment and the evidence that supports each available feature.
From testing to
a verified release.
The roadmap covers the wallet, payments, integrations and privacy research. Each phase includes its scope and the evidence needed to move forward.
Phases can overlap. Onchain features open only after their release criteria are met.
Establish the foundation.
A verifiable first release.
Turn the tested wallet into a carefully bounded public utility. The first milestone is a working, recoverable privacy product on Ethereum.
What we will work on
- Finalize proving artifacts (done: one-operator setup for the capped beta); add independent contributions in a future pool set.
- Publish verified contracts, operating roles, custody caps and release evidence.
- Complete public testnet flows and production relay, indexing and recovery checks.
- Record independent security findings and the release decision before opening access.
COMPLETION CRITERIA
View release status →Public deposit, private transfer, withdrawal and direct recovery succeed against the exact published deployment. Release checks and outstanding security decisions are recorded.
Evidence: Verified receipts, recovery success and resolved release blockers.Make privacy easier to use.
A wallet people can understand.
Refine the everyday experience so users can understand each action, its cost and its privacy boundaries before signing.
What we will work on
- Improve onboarding, seed backup, restore and accessible mobile layouts.
- Make transaction previews, gas estimates and public-data disclosures clearer.
- Reduce proving and synchronization friction with measured performance work.
- Strengthen error recovery, transaction reconciliation and the local activity journal.
COMPLETION CRITERIA
Read the recovery model →Representative users complete onboarding, a transfer and recovery without critical errors; supported devices meet published performance budgets.
Evidence: Task completion, recovery outcomes and proof latency on documented devices.Build useful private payments.
From one payment to a workflow.
Bring the payment tools now being tested into a coherent experience for individuals, teams and merchants.
What we will work on
- Refine payment requests, exact-amount invoice links and local invoice records.
- Complete batch payouts, split withdrawals and scheduled submission workflows.
- Make selective disclosure and one-payment receipts easier to understand.
- Verify persistence, restarts, retries and reconciliation in hosted environments.
COMPLETION CRITERIA
Explore payment workflows →Each payment module has deployed dependencies, end-to-end public-network evidence, recovery coverage and explicit disclosure limits.
Evidence: Payment reconciliation, retry correctness and successful disclosure reviews.Connect more of Ethereum.
Privacy-aware access to applications.
Expand useful activity around the shielded balance while explaining every public market interaction. More integrations must not mean weaker user understanding.
What we will work on
- Harden the existing fresh-wallet trading and shielded-swap implementations.
- Evaluate additional assets and venues with token-behavior and route-risk reviews.
- Improve quote verification, execution constraints and transaction preview coverage.
- Publish the observable data and trust assumptions of every supported integration.
COMPLETION CRITERIA
Understand public trade legs →Each integration has a documented threat model, reproducible execution tests and a recovery path. Public trade data is clearly disclosed.
Evidence: Route reliability, quote consistency and integration-specific review coverage.Open the building blocks.
Tools for privacy-conscious builders.
Develop a documented integration layer so other applications can compose with Darkpool without recreating its wallet and privacy model.
What we will work on
- Stabilize versioned SDK interfaces, examples and integration documentation.
- Publish test vectors and compatibility guidance for notes, receipts and recovery.
- Explore payment and application integrations with explicitly scoped permissions.
- Define contribution, review and vulnerability-reporting processes before a wider developer release.
COMPLETION CRITERIA
Read the architecture →An independent integrator can build and test a supported flow using only the published documentation, release artifacts and test environment.
Evidence: Independent integration success and compatibility across supported releases.Extend the privacy frontier.
A broader Ethereum privacy stack.
Research privacy beyond the wallet: how requests travel, how addresses are linked, how applications disclose data and how users retain meaningful control.
What we will work on
- Study RPC and relayer metadata exposure, data minimization and alternative submission paths.
- Evaluate stealth-address interoperability and scoped disclosure designs.
- Develop the association-set experiment into a reviewed protocol proposal, if justified.
- Investigate proving-system improvements and other Ethereum execution environments with explicit migration plans.
COMPLETION CRITERIA
Read the research agenda →A research result becomes a product commitment only after a published threat model, prototype evaluation, security review and compatibility or migration decision.
Evidence: Reviewed research, reproducible experiments and documented tradeoffs.Release criteria
come first.
Future phases are intended directions, not guarantees or fixed launch dates. Research moves into the product only when its privacy benefit, security assumptions and user experience can be explained and tested.
Preserve recovery.
Keep users’ ability to recover and exit central to architecture and migration decisions.
Explain the tradeoffs.
Make public data, dependencies and remaining privacy limits visible.