The browser coordinates public data. Participants create notes, generate proofs, and sign source coins with the local client.
i
A local companion is available
Start the reviewed companion on your device, then use its browser interface to unlock an encrypted vault, create proofs, and approve the batch. Wallet passwords are entered only at the separate loopback address.
Windows testnet client
Development setup
Download both archives and the release manifest. Follow the bootstrap archive’s README to check the independently supplied manifest fingerprint, install the pinned runtimes, and open the local wallet. These public files contain no wallet keys or blockchain data.
This build uses the development verification key and accepts testnet11 only. Until HTTPS is enabled, verify the manifest fingerprint using a trusted copy outside this website before running the client.
A local window for the private work.
Your device only
Run this from the reviewed checkout with its Python dependencies installed. Replace the uppercase paths and pin with your independently checked values. The service binds only to your own device and does not broadcast transactions.
Start the command first. The new window opens at http://127.0.0.1:8878. This public site never connects to the local API or asks for your vault password. The local window can create an encrypted vault from your standard coin and its already-synthetic signing key, or import an encrypted backup.
01
Choose a batch and review its terms.
Check testnet11, denomination, total network fee, expiry height, and the pool identifier. Each of the four owners needs a distinct standard source coin and key; the sponsor is a fifth source.
02
Create your note on your own machine.
Keep the private note and signing key locally. Export only the funding registration. Submit the anonymous claim request through a separate, unlinkable channel if you need privacy from the coordinator.
03
Download the frozen transcript. Prove locally.
Independently verify its hash and terms. Your client locates your claim without exposing which source belongs to it, then generates one Groth16 proof. Import only the public proof packet.
04
Check the entire candidate before signing.
Download the unsigned candidate. The local client must validate all four proofs, your registered source, your exact intended recipient, change, fee limit, and expiry before signing. Upload only the signature fragment.
05
Watch for confirmed settlement.
After all five source approvals, the coordinator finalizes and submits the exact batch. Submission is not confirmation. Keep your note and source records until the receipt reports independently checked on-chain settlement.
Local client commands
No secrets in the browser
Run these from the reviewed source checkout with its Python dependencies installed. Replace uppercase placeholders with your independently checked values and paths. Create the public output directory first. Passwords are requested locally; never enter them into this website.
The source key file must contain the raw 32-byte signing key for the selected standard coin, in a private directory with restricted permissions. Each participant uses their own vault and source. No seed phrase is accepted by this command.
Import funding.json as a funding registration. A claim request contains a nullifier and fresh recipient puzzle hash; submitting it through the same connection can reveal its association with the source.
Obtain the artifact configuration and its hash through an independently trusted channel. Download the public transcript from the batch record. Only proof.json is uploaded.
Your local policy must contain the independently reviewed expected_transcript_hash, pool_id, denomination_mojos, maximum_total_fee, current chain_height, latest_expiry_height, and minimum_remaining_blocks. Upload signature.json after the local checks pass.
Fee sponsor commands
The sponsor uses a separate source and vault. Its public registration has no note commitment, and it does not produce a membership proof.
Restore into a new local vault path. For an output spend, obtain the actual confirmed coin record and choose your destination, amount, and fee. The client creates a signed public bundle; this command itself makes no network or broadcast calls.
Mulcher combines Groth16 membership proofs with Chia’s coinset model to settle four contributions and four payouts in one atomic transaction.
01 /
One atomic settlement
The source spends, reserve claims, and closure are included together. Before confirmation, funds remain in the source coins. A missing approval prevents the complete batch from being submitted successfully.
02 /
Local ownership
The coordinator receives public registrations, claims, proofs, and signatures. The intended client workflow never sends it a note secret or signing key. Each source owner approves the entire candidate.
03 /
Proof privacy has a boundary
The proof hides the note membership witness. All four sources and destinations remain publicly visible. IP addresses, session identity, timing, and out-of-band knowledge can still connect them.
04 /
Four is the whole set
There are four claims in this version. Do not treat that as a large anonymity set. Equal amounts avoid an amount-based distinction within the batch; they do not guarantee anonymity.
Know exactly what this release does.
Network
Chia testnet11 · TXCH only
Execution
On-chain Rue / Chialisp puzzles
Proof system
Groth16 over BLS12-381
Setup
Uses pinned proving and verification artifacts. See deployment setup provenance.
Fees
The displayed network fee covers the whole batch. One source contributes the 1-mojo bootstrap marker; the sponsor covers the rest. This console adds no service fee.
Timing
One inclusion block once prepared and accepted. Proof preparation, coordination, and block inclusion still take time.
