Current
BCS testnet access
Deploy and read-only verify Bcash / BCS on Base Sepolia, then attach the public thirdweb claim or purchase link to the testnet page.
BaseCash
ROADMAP
Mainnet only happens after testnet proof, review, and explicit authorization.
This roadmap tracks the practical path from the current Base Sepolia build to a future mainnet deployment. Each phase must close with evidence before the next one begins.
Next
Pool and proof route
Deploy the BCS-bound testnet pool, verify contract code, verify proof artifacts, and keep browser proof generation gated until manifests are reviewed.
Testers
Controlled public tester loop
Run purchase, approve, cloak, send, and uncloak with public receipts, local note recovery, root reconstruction, and failure-case testing.
Security
Audit and ceremony review
Complete independent verifier review, ceremony/provenance acceptance, adversarial testing, relayer/paymaster review, and operational monitoring design.
Mainnet gate
Production deployment decision
Only after source verification, legal/compliance review, incident response, and explicit mainnet authorization can a production pool deployment be considered.
No production pool, mainnet user-testing pool, or active shielded BCS route is live from this page.
Every contract, proof artifact, and relayer/paymaster path needs independent review before production use.
Mainnet requires a separate explicit deployment approval, not a generic continuation or UI publish.