ZecOne — wallet and shielded-payment demo

Customers pay with shielded Zcash; merchants receive ETH on Base.

How to test (judges): 5 minutes, nothing to install

Live site: https://zecone.xyz · API: https://api.zecone.xyz

No wallet, funds, faucet or account is needed for steps 1–3.

1. Try a checkout (simulated, no real money). Open zecone.xyz/checkout and buy an item, or pick an amount in the homepage widget and choose Continue to demo checkout. You see the exact ZEC amount, the 5-minute quote window and a Simulated badge. Without any action from you, the server replays recorded mainnet transactions and the checkout walks through each step to Payment complete with a Basescan link. A simulated checkout never shows a payable address.

2. See real mainnet evidence. Open zecone.xyz/explorer and follow the links to the Zcash and Base block explorers.

3. Check the live service from a terminal:

   curl https://api.zecone.xyz/api/v1/health
   curl "https://api.zecone.xyz/api/v1/quote/preview?amountUsd=5"
   

   Health reports mode: monitor, realPayments: restricted-pilot, and livePayoutEnabled: false / zcashBroadcastEnabled: false (nothing moves funds automatically). The quote preview is labeled as a fixed demo rate.

4. Developer integration. Read the create-payment snippet in zecone.xyz/docs. In zecone.xyz/dashboard you can sign in with any Base wallet (a signature, no transaction), get an API key, and send a test webhook. During the restricted pilot, creating a payment with your own key returns 403 real_payments_restricted; use step 1 to see the checkout flow.

5. Privacy model. zecone.xyz/security explains what is private (the shielded Zcash leg) and what is public (the Base payout).

Real mainnet payment (restricted pilot)

Real payments are limited to one approved pilot merchant and run by the operator, so judges cannot trigger one. Verified on 1 November 2026: order pay_d9aae1aea3104f6995e6c04746 was paid with 810 zatoshis in Zcash transaction cad53524…032163 (block 3,538,167). The watcher confirmed it after 20 confirmations, checking two independent providers and the raw blocks (proof of work, Merkle inclusion, continuity). The order reached ZEC_CONFIRMED, then completed the separately approved Base payout on 4 November 2026. The finalized payout sent 4,424,465,524,565 wei in transaction 0x8ab550cd…f321289. This is evidence of the restricted operator-controlled path, not unrestricted public settlement.

To build and run everything locally, see Install and verify.

Project history

Launch status (28 October 2026): the paired local browser wallet can switch explicitly between Testnet and a read-only projection of the existing verified Mainnet wallet. Mainnet receive, balance, history and sync freshness are visible locally; the public website cannot pair with that wallet or request a signature. A separate operator-reviewed workflow executed and finalized a real Zcash mainnet transfer (0f0e9442…1def47) with exact SIGN and BROADCAST gates. The public merchant experience remains a demo-only replay with no payable address or live cross-chain settlement. See wallet audit, mainnet evidence, demo deployment, and submission package.

The historical prototype is a Next.js wallet over a native Rust Zcash wallet, durable TypeScript/SQLite order service, and prefunded Base Sepolia settlement. Its minting, dApp requests, and marketplace purchase features remain testnet only; mainnet is limited to the read-only wallet projection and separately documented operator-controlled pilot evidence. There is no bridge or public real-asset exchange.

Latest: Phase 4E. Actual OpenSea discovered the installed extension, connected the local test account, accepted an explicitly approved Base Sepolia login signature, and revoked access on logout. The public test profile is zecone-test-c714. No asset transaction occurred. See results, installation/runbook, security, and limitations. The Phase 4D read-only API preview and earlier testnet functionality are preserved. Phase 5 has not begun.

Open the wallet: double-click Launch-ZecOne.cmd. It starts the local gateway and securely opens your browser at http://127.0.0.1:3210. The existing funded wallets and deployed contract are reused. See the Phase 1 runbook, implementation results, and browser security review.

Phase 0 remains preserved. Its real 0.01 TAZ shielded payment, ten-confirmation authorization, Base NFT receipt, ownership and idempotency evidence are recorded in Phase 0 results. Checkpoint 482fc57 precedes all Phase 1 changes. NU7 requires the pinned official prerelease Rust libraries; this remains a trusted testnet relayer prototype.

Phase 3: start the independent marketplace with npm.cmd run marketplace:dev and open http://127.0.0.1:4322. Connect the local wallet, review an NFT quote, and separately approve the shielded payment. See results and live evidence, runbook, security model, and limitations. Phase 2 connectivity and its evidence are preserved in Phase 2 results.

This is the beginning of the README. Read the rest at the original. Read the full README ↗