# tidex6 — private payments on Solana [Health: Active] **Category:** 💰 Finance & Fintech **Repository:** https://github.com/koshak01/tidex6 **GitHub Stars:** 1 **Views:** 0 **Installs:** 0 **Upvotes:** 0 **Directory Page:** https://allmcps.com/mcp/tidex6-private-payments-on-solana ## Description Private USDC/USDT payments on Solana: hidden amounts, unlinkable, optional auditor. ## Claude Desktop Quick Installation Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low): ```json "mcpServers": { "tidex6-private-payments-on-solana": { "command": "npx", "args": ["-y","tidex6-private-payments-on-solana"] } } ``` ## Documentation & README

tidex6

tidex6

I grant access, not permission.
The Rust-native privacy framework for Solana.

--- tidex6 is a Rust-native, open-source framework that lets Solana developers add full transaction privacy to their Anchor programs through a small SDK surface. Transactions are private by default — sender, receiver, and amount are hidden. Privacy comes in **two layers**: a Groth16 shielded pool hides the *link* between sender and receiver, and a Token-2022 Confidential Transfers layer (wUSDC / wUSDT hidden-amount pools, live on mainnet and devnet) hides the *amount* itself. Users can optionally share a viewing key with someone they trust (an accountant, an auditor, a family member) to selectively disclose history, on their own terms. **Status:** full MVP product stack **live on Solana mainnet**. The privacy-core verifier program at [`CSDD31Zmm3pRMHAMB8c3TBqsj9mbmH2rXBzV7jrsJhcd`](https://solscan.io/account/CSDD31Zmm3pRMHAMB8c3TBqsj9mbmH2rXBzV7jrsJhcd) is OtterSec-verified and immutable (upgrade authority renounced). The full feature stack — deposit, ZK withdraw (Groth16 `WithdrawCircuit<20>` verified via `alt_bn128` syscalls), per-nullifier double-spend PDA, recipient-binding front-run protection, **unlinkable withdraw via reference relayer** at [`relayer.tidex6.com`](https://relayer.tidex6.com), opaque hex notes + **post-quantum ML-KEM-768 encrypted memos in a dedicated on-chain account**, **stealth payments** (the recipient is never handed the note — they scan the chain with their own ML-KEM secret) and **per-deposit revoke**, **client-side proof generation in the browser via WebAssembly** (`tidex6-prover-wasm`, ~1.7 s per proof, secret never leaves the user's tab), user-facing `tidex6` CLI, `tidex6-client` SDK, web app at [tidex6.com](https://tidex6.com), the flagship `examples/private-payroll` three-binary demo, and a **third-party CPI integration example** (`tidex6-tip-jar`, ~30 lines of Rust to add privacy to any Anchor program — deployed and OtterSec-verified on mainnet at [`5WohQRRzC31SkFMSWgEqJC9p2KvNhGkQbzUSsNUi9b9x`](https://solscan.io/account/5WohQRRzC31SkFMSWgEqJC9p2KvNhGkQbzUSsNUi9b9x) in April 2026, demo deployment since closed) — all validated end-to-end on mainnet. MVP shipped for the **Colosseum Frontier hackathon (2026-05-11)**; development continues — since then the **hidden-amount pools** (Token-2022 Confidential Transfers, wUSDC [`AYTRKmF8VBdqRWGZr9c6Mx582SRm2tbUEwMesFMhcPcU`](https://solscan.io/account/AYTRKmF8VBdqRWGZr9c6Mx582SRm2tbUEwMesFMhcPcU) and wUSDT [`QGPYpwyMnWhJUPGieXyJU5jhAkKsKuU7iGN53VCWPz2`](https://solscan.io/account/QGPYpwyMnWhJUPGieXyJU5jhAkKsKuU7iGN53VCWPz2)), a configurable **per-operation fee** paid on top by the sender and **collected privately** as a stealth note (ADR-016), and the live **public trusted-setup ceremony** at [ceremony.tidex6.com](https://ceremony.tidex6.com) (ADR-017) have shipped. > **DEVELOPMENT ONLY.** Pre-audit, single-contributor trusted setup, hackathon-grade trust assumptions. Verifier `upgrade-authority` has been renounced with `solana program set-upgrade-authority --final` — the program is immutable. Do not use to secure real funds. A **public multi-party trusted-setup ceremony is live** at [ceremony.tidex6.com](https://ceremony.tidex6.com) (publicly verifiable transcript, see [CEREMONY.md](https://github.com/koshak01/tidex6/blob/HEAD/docs/release/CEREMONY.md)); the on-chain VK is replaced only when the ceremony finalizes and a fresh immutable verifier ships. See [`docs/release/security.md`](https://github.com/koshak01/tidex6/blob/HEAD/docs/release/security.md). --- ## What builds from a clean clone Everything in this repository builds with `cargo build --release` after a plain `git clone`, and the on-chain programs build reproducibly in Docker via `solana-verify build`. Three crates are deliberately outside the workspace and build on their own terms: | crate | how to build it | why it is separate | |---|---|---| | `crates/tidex6-prover-wasm` | `wasm-pack build` | targets `wasm32-unknown-unknown` and pulls browser-only crates | | `crates/tidex6-ct-lab` | `cargo build --manifest-path crates/tidex6-ct-lab/Cargo.toml` | pinned to newer `spl-token-2022` / `solana-*` than the workspace | | `crates/tidex6-mcp` | `cargo build --manifest-path crates/tidex6-mcp/Cargo.toml` | **needs a checkout of our internal core (`forge`) next to this repo**, so it cannot build for anyone else | The last one is worth stating plainly rather than leaving to be discovered: the hosted MCP server depends on a private crate outside this repository. While it was a workspace member, `cargo build` failed in a clean clone for everybody who does not have that checkout — which is everybody but us — and for the same reason a program verifier could not build the repository on its own machine. It is now its own workspace. Nothing else here depends on it: the payment protocol, the programs, the SDK, the CLI and the local MCP server (`crates/tidex6-mcp-local`) are all self-contained. --- ## Quick start — stablecoins (USDC / USDT) The pools in production move **USDC and USDT with the amount hidden on chain**. Two ways in, neither of which needs this repository built from source: **In a browser** — [tidex6.com](https://tidex6.com), any Solana wallet. The proof is generated inside your tab; the secret never leaves it. **From an AI agent or the command line** — the local MCP server signs with a key that stays on your machine, under limits enforced in code: ```bash cargo install tidex6-mcp-local ``` ```json { "mcpServers": { "tidex6": { "command": "tidex6-mcp-local", "args": [] } } } ``` Tools: `send`, `payments`, `collect`, `audit`, `whoami`. Full description in [`crates/tidex6-mcp-local/README.md`](https://github.com/koshak01/tidex6/blob/HEAD/crates/tidex6-mcp-local/README.md). ## Quick start — the original SOL pool The `tidex6` CLI below talks to the **v0.1 fixed-denomination SOL pool**, which predates the stablecoin pools and remains available — it carries no issuer `freeze_authority`, which is the reason to keep it. Amounts there are visible on chain; only the link between sender and recipient is hidden. For hidden amounts use the stablecoin path above. ```bash # Generate a tidex6 identity (spending + viewing key). cargo run --release -p tidex6-cli -- keygen # Make a private 0.5 SOL deposit to the shielded pool. cargo run --release -p tidex6-cli -- deposit \ --amount 0.5 --note-out parents.note # Redeem the note into any recipient wallet. The CLI rebuilds # the offchain Merkle tree from on-chain history via the # indexer, generates a Groth16 withdraw proof, and submits it # to the verifier program. # # Default is the direct path — the user signs their own tx. # For full unlinkability (ADR-011) add `--relayer` to delegate # the tx to a relayer service that signs and pays on the user's # behalf: # --relayer https://relayer.tidex6.com \ # --relayer-pubkey cargo run --release -p tidex6-cli -- withdraw \ --note parents.note --to ``` ## Quick start — SDK Integrate a shielded pool into your own Rust app in a handful of lines using the `tidex6-client` builder API: ```rust use anchor_client::Cluster; use tidex6_client::PrivatePool; use tidex6_core::note::Denomination; # fn demo( # payer: &solana_keypair::Keypair, # recipient: anchor_client::anchor_lang::prelude::Pubkey, # ) -> anyhow::Result<()> { let pool = PrivatePool::connect(Cluster::Mainnet, Denomination::OneSol)?; // Deposit side: keep the note locally — with stealth payments the recipient // is never handed the note; they discover the deposit by scanning the chain // with their own ML-KEM secret. let (deposit_sig, note, _leaf_index) = pool.deposit(payer).send()?; std::fs::write("parents.note", note.to_text())?; // Withdraw side: rebuild the tree, prove, submit. // Default direct path — user signs the tx themselves. let withdraw_sig = pool .withdraw(payer) .note(note) .to(recipient) .send()?; // Full unlinkability via the reference relayer (ADR-011): the // user's keypair never signs the withdraw tx, the relayer pays // fees and becomes the on-chain payer. Circuit binds the specific // relayer so a front-runner cannot swap them in mempool. // let withdraw_sig = pool // .withdraw(payer) // .note(note) // .to(recipient) // .via_relayer("https://relayer.tidex6.com", relayer_hot_wallet_pubkey) // .send()?; # drop((deposit_sig, withdraw_sig)); # Ok(()) # } ``` ## Try the flagship demo [`examples/private-payroll`](https://github.com/koshak01/tidex6/blob/HEAD/examples/private-payroll/) is the full story of Lena sending monthly support to her parents, with her accountant Kai producing a tax report from a shared scan file. Three binaries — `sender`, `receiver`, `accountant` — hit live mainnet. ```bash cd examples/private-payroll ./scripts/run_demo.sh ``` The script splits one terminal into three tmux panes and runs the whole flow side by side — deposit → rebuild → prove → withdraw → report — in under a minute. --- ## Architecture at a glance - **Groth16** zero-knowledge proofs on the **BN254** curve, verified onchain via native Solana `alt_bn128` syscalls in under 200,000 compute units per proof. - **Poseidon** hash function, parameter-aligned between offchain (`light-poseidon`) and onchain (`solana-poseidon`) components. - **Offchain Merkle tree** (depth 20, ~1M capacity) with an onchain root ring buffer. - **Hidden amounts** — a Token-2022 Confidential Transfers layer (wUSDC / wUSDT wrapped-mint pools, live on mainnet and devnet) hides the transferred amount itself on top of the Groth16 link-privacy pool. Two layers: the pool hides *who↔whom*, confidential transfers hide *how much*. - **Per-deposit selective disclosure** via post-quantum ML-KEM-768 auditor tags — users choose who sees what, per transaction. - **Shielded memos** — post-quantum ML-KEM-768 encrypted notes stored in a dedicated on-chain account (separate from the deposit event), readable only by the viewing-key holder. Supports **stealth payments** (the recipient scans the chain with their own ML-KEM secret rather than receiving the note) and **per-deposit revoke**. - **Non-upgradeable verifier** — the core proof verifier is locked after deployment, so users do not have to trust the deployer forever. - **Relayer unlinkability** — ADR-011: a reference HTTPS service at `relayer.tidex6.com` signs and submits withdraw transactions so the user's wallet never appears on-chain as the payer. The proof commits to the specific relayer (public input) so front-runners cannot redirect the fee. The in-circuit `relayer_fee` policy for the reference service is zero; anyone may run their own relayer with any fee. Separately, deposits carry a configurable per-operation fee (ADR-016): the sender pays it on top (it may be zero), it is shown before signing, and it is collected privately — as a stealth note to the operator inside the same shielded pool. - **Client-side proof generation** — `tidex6-prover-wasm` compiles the Rust prover to WebAssembly. The browser parses the deposit note locally, derives `commitment` and `nullifier_hash` via in-WASM Poseidon, and runs Groth16 entirely on the user's machine in ~1.7 s on M-series CPUs. The user's `secret` and `nullifier` never reach our server, the relayer, or anyone else — formally provable by inspecting `WebAssembly.Module.imports(...)` of the deployed `.wasm` artefact, which contains zero `fetch` / `XMLHttpRequest` / `WebSocket` symbols. Sandbox is the proof. - **Composable as a CPI primitive** — any Anchor program can route SOL through `tidex6_verifier::deposit` and inherit the full privacy stack. The reference example [`tidex6-tip-jar`](https://solscan.io/account/5WohQRRzC31SkFMSWgEqJC9p2KvNhGkQbzUSsNUi9b9x) shows the pattern in ~30 lines of Rust (built and OtterSec-verified against the historical v1 verifier — re-point it at the current verifier before reuse); payroll, royalty splitters, subscription protocols, and dark-pool DEX hooks follow the same pattern. - **Built with Anchor 1.1.2.** Full technical detail: [docs/release/PROJECT_BRIEF.md](https://github.com/koshak01/tidex6/blob/HEAD/docs/release/PROJECT_BRIEF.md). --- ## Technical stack **Onchain (Anchor 1.1.2 program):** - `anchor-lang = "=1.1.2"` - `groth16-solana = "0.2"` — Groth16 verifier via `alt_bn128` syscalls - `solana-poseidon = "4"` — native Poseidon syscall **Offchain (client and prover):** - `arkworks 0.5.x` — `ark-bn254`, `ark-groth16`, `ark-crypto-primitives`, `ark-r1cs-std`, `ark-relations`, `ark-ff`, `ark-ec`, `ark-serialize`, `ark-ed-on-bn254` - `light-poseidon = "0.4"` — circom-compatible Poseidon, byte-for-byte equivalent to the onchain syscall - `ml-kem = "0.2"`, `chacha20poly1305 = "0.10"` — post-quantum ML-KEM-768 memo encryption - `anchor-client = "1.0"`, `solana-sdk = "4.0"` --- ## Philosophy Closed by default. Open by user choice. The protocol enforces nothing about who uses it — it builds rails where honest behaviour is the shortest path. Users who choose to prove their legitimacy do so to someone *they* picked, through a key *they* hold. There is no backdoor, no key escrow, no recovery service. The architecture has a strong opinion about *how* the tool can be used; it has no opinion about *who* uses it. Full manifesto: [docs/release/THE_LEGEND.md](https://github.com/koshak01/tidex6/blob/HEAD/docs/release/THE_LEGEND.md). --- ## Documentation Public documentation lives in [`docs/release/`](https://github.com/koshak01/tidex6/blob/HEAD/docs/release/): - **[THE_LEGEND.md](https://github.com/koshak01/tidex6/blob/HEAD/docs/release/THE_LEGEND.md)** — mission, philosophy, design principles. - **[PROJECT_BRIEF.md](https://github.com/koshak01/tidex6/blob/HEAD/docs/release/PROJECT_BRIEF.md)** — technical brief: architecture, data flow, workspace layout, developer experience. - **[ROADMAP.md](https://github.com/koshak01/tidex6/blob/HEAD/docs/release/ROADMAP.md)** — now / next / later, shipping milestones. - **[security.md](https://github.com/koshak01/tidex6/blob/HEAD/docs/release/security.md)** — threat model, known limitations, vulnerability classes and mitigations. - **[CEREMONY.md](https://github.com/koshak01/tidex6/blob/HEAD/docs/release/CEREMONY.md)** — the public trusted-setup ceremony: how to contribute, how to verify the chain, how finalization works. - **[PR_CHECKLIST_PROOF_LOGIC.md](https://github.com/koshak01/tidex6/blob/HEAD/docs/release/PR_CHECKLIST_PROOF_LOGIC.md)** — Fiat-Shamir discipline checklist for every PR that touches proof logic. - **[adr/](https://github.com/koshak01/tidex6/blob/HEAD/docs/release/adr/)** — Architecture Decision Records (seventeen ADRs covering commitment scheme, Merkle tree storage, nullifier storage, ElGamal implementation, non-upgradeable verifier, builder pattern vs macros, killer features, pool isolation, proving time budget, memo transport, relayer architecture, opaque note format, browser-side proof generation, post-quantum ML-KEM memo in a dedicated account, the two-layer confidential-amount architecture, configurable fee with private collection, and public ceremony finalization). **Russian translations** of all of the above are available in [`docs/release/ru/`](https://github.com/koshak01/tidex6/blob/HEAD/docs/release/ru/). --- ## Workspace layout ``` tidex6/ ├── crates/ │ ├── tidex6-core/ — commitments, nullifiers, Merkle tree, keys, Poseidon, DepositNote, pqc (ML-KEM-768) │ ├── tidex6-circuits/ — arkworks R1CS: DepositCircuit, WithdrawCircuit<20> with relayer binding │ ├── tidex6-indexer/ — offchain Merkle tree rebuild from on-chain DepositEvent logs │ ├── tidex6-client/ — Rust SDK with builder pattern API (PrivatePool, DepositBuilder, WithdrawBuilder direct + via_relayer) │ ├── tidex6-cli/ — developer CLI: `tidex6 keygen | deposit | withdraw | accountant` │ ├── tidex6-prover-wasm/ — ADR-013: Rust prover compiled to WebAssembly (~1.7 s in-browser proof, secret never leaves the tab); excluded from workspace, built via wasm-pack │ ├── tidex6-notifier-client/ — bitcode IPC client for the Telegram notifier microservice (shared between tidex6-web and the relayer service) │ ├── tidex6-ui-shared/ — shared brand/css/template assets embedded via include_dir!; single source of truth for tidex6-web and the relayer status pages │ └── tidex6-day1/ — Day-1..15 mainnet flight harnesses (Day-1 gates, Day-5 deposit, Day-11 withdraw, Day-12 negative, Day-13 accountant) ├── programs/ │ ├── tidex6-verifier/ — singleton non-upgradeable Anchor verifier program (deployed at CSDD31Zm…sJhcd) │ ├── tidex6-tip-jar/ — ADR-013 reference CPI integration example (deployed + OtterSec-verified Apr 2026, deployment since closed) │ ├── tidex6-confidential-amounts/ — early v0.3 Token-2022 Confidential-Transfers exploration (not on mainnet yet) │ └── tidex6-caller/ — test CPI caller used by Day-1 gate 4 ├── examples/ │ ├── private-payroll/ — flagship example: sender, receiver, accountant binaries │ └── confidential-amount-demo/ — companion to programs/tidex6-confidential-amounts (v0.3 exploration) ├── brand/ — logo assets, brandbook, Solscan PNGs └── video/ — pitch, demo, and weekly progress scripts External repos (sibling path-deps, not part of this workspace): - tidex6-web — production website at tidex6.com (5-microservice IPC architecture) - tidex6-relayer — production relayer at relayer.tidex6.com (Axum HTTPS service, ADR-011) Planned for v0.2, not yet in the workspace: - Proof of Innocence circuit + Association Set Provider (ADR-007 v2) - Relayer hardening: HSM keypair, multi-sig cold wallet, federated discovery - Ergonomic proc macros (`#[private_withdraw]` etc.) layered over the builder API (ADR-006) - Auditor key lifecycle — BIP32-style HD derivation for forward secrecy (extends ADR-014) ``` --- ## License Dual licensed under either **MIT** or **Apache-2.0** at your option. No token, no SaaS tier. The Groth16 verifier is a permissionless, immutable primitive anyone can integrate; the hidden-amount pools are operated deployments with a configurable (possibly zero) per-operation fee. --- ## Contact Issues and pull requests on GitHub. *tidex6.rs — I grant access, not permission.*