tidex6 — What is already built

01 What it gives you

if you pay people

Your payroll stops being public

Salaries, contractor rates, supplier terms — every one of them is a negotiating position, and on a normal chain all of them are readable forever by anyone, including the person you are about to negotiate with.

if you receive

One address, forever

You publish a single wallet and never rotate it. Payments arrive without anyone being able to total them up, and you find them by scanning the chain with your own key — nothing is handed to you, so nothing can be intercepted on the way.

if you answer to someone

Disclosure without surrender

The sender names a reader — an accountant, an auditor, a regulator — and that reader sees the date, the amount and the purpose. They can never spend the money and never freeze it. Audit without seizure.

if you build

Privacy as a dependency

Seven crates on crates.io and a reference program that pays privately in about thirty lines of Rust. You do not host a prover, run a ceremony, or understand a circuit. You add a dependency.

02 The privacy itself

The amount is hidden on chain Token-2022 confidential transfers carry the value as ciphertext. An observer sees that a transfer happened, not how much moved.

The link between sender and recipient is broken A Groth16 proof over BN254, verified on chain by native syscalls. Deposits and withdrawals cannot be paired, and a nullifier PDA makes a second spend impossible rather than merely detectable.

Nothing is handed to the recipient No note, no link, no message. The recipient scans the chain with their own key and reconstructs the payment. There is no secret in transit to steal, and a leaked chat history reveals nothing.

The memo is post-quantum sealed ML-KEM-768 with ChaCha20-Poly1305. A payment recorded today and stored by a patient adversary does not become readable when quantum hardware arrives.

Scanning is fast enough to be usable A one-byte X25519 view tag lets a wallet skip envelopes that are not addressed to it without attempting decryption — a hundred envelopes are checked in hundredths of a second instead of one heavy operation each.

The sender can take it back Every deposit has a revoke window. If it went to the wrong reader, or was never collected, the money returns — the mistake is recoverable instead of permanent.

03 Ways to actually use it

In a browser, with your own wallet The proof is generated inside the tab in WebAssembly, roughly two seconds. Your secret never leaves the machine — the compiled module imports no network function at all, which is a fact anyone can verify rather than a promise we make.

From an AI agent, two custody models Hosted: the agent holds no key and prepares a link you sign yourself. Local: cargo install tidex6-mcp-local, the key stays on your machine, limits are enforced in code, and the amounts are a fixed set — an injected instruction cannot express “send everything”.

From another Solana program A reference integration pays privately through one CPI call in about thirty lines of Rust, and the resulting payment is indistinguishable from any other.

From the command line, or from Rust directly A CLI for people and an SDK with a builder API for programs. Both talk to the same pools as everything above.

Without the recipient paying gas A relayer submits the withdrawal and pays the fee, so the receiving wallet never appears on chain as a fee payer — which would have undone the privacy at the last step.

04 Why you can check instead of trusting

The verifier can never be changed Upgrade authority is renounced. Not “we promise not to touch it” — there is no key left that could. It is also independently verified by OtterSec against its published source.

The browser code is the published code The WebAssembly served to you can be rebuilt from source and compared byte for byte.

The setup ceremony is public Anyone with a Solana wallet contributes and the transcript is open. One honest participant out of all of them is enough to make the key trustworthy — and nobody has to take our word for which one was honest.

An external audit already found and closed things Automated analysis surfaced an unchecked-arithmetic issue that is fixed, and a vulnerable dependency was replaced before it could bite.

05 Live numbers

on mainnet: 46 payments, all received
envelopes on chain: 105
disclosed to an auditor: 18
programs deployed: 4 verifier, two pools, registry
published crates: 7 on crates.io
ceremony: 4 of 20+ contributors

Three independent paths were exercised end to end on the same day in August — command line, browser with a wallet, and a third-party AI agent — each completing send, audit and receive with real money.

06 How long this took

Four months, and the useful way to read them is by what was forcing the work.

before 9 April 2026 Nothing

No repository, no line of code. The project did not exist.

9 April — 11 May · first hackathon A working proof, and an awkward one

164 commits. The zero-knowledge pool worked and the first verifier went to mainnet — but payments were in SOL, amounts were public, and the sender had to hand a secret note to the recipient somehow. It proved the idea. It was not something you would ask a colleague to use.

12 May — 4 August · no deadline at all The product was rebuilt

326 commits across three repositories — twice the hackathon itself, with nothing forcing it. SOL became USDC and USDT. Public amounts became hidden ones through confidential transfers. Handing over a note became stealth scanning, so nothing is transmitted at all. The memo encryption was replaced with a post-quantum one.

Everything on this page above — agents, the relayer, in-browser proving, the reader registry, the public ceremony, the immutable verifier — was built in this stretch.

5 August — 2 September · now Closing the one thing code cannot close

The ceremony, from 4 contributors to 20-plus, which turns the development key into a real one. A rewritten indexer so proving stays fast as the pool grows. And the first integrations by people who are not us — the only number on this page that we cannot produce ourselves.

07 What is not finished

A list of accomplishments with nothing unfinished in it is an advertisement. These are the three things we would ask about if we were reading this page.

The ceremony is not closed

Four contributors of the twenty-plus we want. Until that is done the verifying key is still a development key, and we say so here rather than in a footnote. This is the one thing that cannot be solved by writing code — it needs people, and you can be one of them.

The operator sees the send side

Wrapping into confidential tokens requires the mint authority, so the operator knows which wallet paid how much. Privacy from the public is complete; privacy from the operator on the send path is not.

There are no outside users yet

Those 46 payments are our own, made with real money to prove the thing works rather than to claim traction. Inviting strangers onto a development key would be dishonest, which is why the ceremony comes first.