WHITEPAPER

BaseCash current build

BaseCash is a Base Sepolia testnet privacy-payment prototype. It separates public asset acquisition from local shielded-note review, and it keeps production claims blocked until contracts, proofs, relayers, legal review, and user testing are independently verified.

1. Product goal

BaseCash aims to make private payment workflows understandable: acquire a public test asset, cloak it into a shielded note, send the note, and uncloak back to a public wallet. The current page is a testnet interface, not a production financial product.

2. Current build

• Base Sepolia UI with tUSDC, tBCS, and client-held tzkBCS states.
• Circom and Groth16 V2 pool route with pool, asset, and chain-domain binding.
• Noir/UltraHonk compile and verifier work tracked separately from the Groth16 browser route.
• Encrypted local note backup and public pool event indexing models.
• BCS token readiness for a user-controlled thirdweb deployment route.

3. Privacy boundary

BCS itself is public. Privacy, when enabled, is an application layer that depends on reviewed proof artifacts, deployed pool contracts, public root reconstruction, note recovery, and strict handling of local note material. tzkBCS is not a public ERC-20.

4. Token and chain direction

The current public token design is Bcash / BCS with a fixed 100,000,000 testnet supply on Base Sepolia. The selected longer-term architecture remains an Ethereum-settled BaseCash OP Stack chain with a shielded pool, while Base remains a separate future bridge endpoint.

5. Open gates

Before a public tester route or production claim, BaseCash still needs live BCS verification, pool deployment review, browser proof artifact review, relayer/paymaster policy review, security testing, legal/compliance review, and an explicit publish/deployment step.