1 · Bitcoin — Taproot envelopes mainnet
Tacit's Bitcoin lane lives in Taproot envelope transactions: etches that define assets, transfers, mints and burns of confidential assets, all readable on-chain. Amounts and who-owns-what are hidden inside the envelope commitments; the transactions, counts and fees are public.
2 · The bridge — burns in, mints out
Moving value across the privacy boundary burns notes on one side and mints on the other. What the chain shows is that a bridge happened and when — never how much.
3 · Ethereum — the confidential pool mainnet
0x000000000Ed1eabD231Be41d93b719056F7febFC (deploy block 25,998,736). Deposits (wraps) put value in as commitments; spends publish nullifiers; notes move without public amounts. The indexer mirrors the on-chain Merkle tree entry by entry.
All-time wrapped volume per asset (summed live from every wrap entry in the indexer)
| asset | asset id | wrapped (all-time) | wraps |
|---|
Latest pool events
| seq | type | block | detail | tx |
|---|
Leaves = commitments added to the Merkle tree (new notes or memo updates — the memo bytes are public, what they mean is not). Nullifiers = notes spent. Wraps = public deposits (amount and asset are public by design). Cross-outs = a note cancelled against a deposit. These txs carry zero public amounts for leaves/nullifiers: the point of the design.
Relay fee floors (quote API)
3b · Lifetime ledger, decoded straight from the logs
Everything above trusts Tacit's indexer. This section does not: the numbers here are decoded by us from the 14,578 event logs of the ConfidentialPool, from its deployment block (…) to the head read at build time (…). If the indexer and the chain ever disagree, this is the column that shows it.
cross-checking against the indexer…
Notes minted vs spent, per week
▮ minted ▮ spent · a note is a private claim on the pool: minting is a deposit entering, spending is a transfer, a withdrawal or a cross-out. The two bars tracking each other is what healthy private flow looks like.
Wrapped volume per asset, summed over every Wrap in the log
| asset | deposits | wrapped | share of deposits | underlying |
|---|
Amounts are token amounts, decoded with each asset's own decimals. Two rows carry an assetId that the current registry no longer answers for — earlier generations of the pool — so they are labelled unregistered instead of being guessed at.
4 · EVM pools — Ethereum, Base, Robinhood, MegaETH
The Groth16 EVM pool ("Secret Sats", asset = ETH) runs the same circuit on every chain: transact, 2 public inputs, 2 public outputs. Reads below are live eth_calls through public RPCs.
Per-chain deployments (contracts/deployments/evm-pool.json)
| chain | pool | deploy block | keeper |
|---|---|---|---|
| Ethereum (1) | 0x000000c2A20657CE25f2Ba99737933D031AFBEE9 | 26,069,245 | keeper |
| Base (8453) | 0x000000c2A20657CE25f2Ba99737933D031AFBEE9 | 51,864,014 | keeper |
| Robinhood Chain (4663) | 0x000000c2A20657CE25f2Ba99737933D031AFBEE9 | 73,991,661 | keeper |
| MegaETH (4326) | 0x000000c2A20657CE25f2Ba99737933D031AFBEE9 | 28,397,750 | keeper |
5 · Bitcoin-side assets & AMM snapshot
Etched confidential assets on Tacit's Bitcoin mainnet and the private AMM pools over them. This block is a build-time snapshot (see the timestamp below): the indexer's /assets and /amm/pools routes send CORS only to tacit.finance, so this page cannot call them from your browser. The snapshot files carry the raw API responses, and the live confidential-pool numbers above are fetched live instead.
AMM pool (/amm/pools?network=mainnet)
| pool | asset A | asset B | reserve A | reserve B | LP shares |
|---|
Etched assets (… total)
| ticker | decimals | etched at | mintable | asset id | etch tx |
|---|
6 · The privacy frontier — what is public, what stays hidden
Tacit's privacy has a precise boundary. This page shows you the public side and refuses to fake the hidden side.
Public (on-chain, anyone can see)
- That transactions exist, and when (timing, block heights, timestamps)
- Counts: how many leaves, nullifiers, wraps, cross-outs, bridge burns/mints
- Fees and tips paid to relayers and provers
- Addresses that deposit (wrap) or receive withdrawals
- Wrap amounts and assets (deposit sizes are public by design)
- Memo bytes on leaves (encrypted payload — contents hidden, existence public)
- The Merkle tree root and size
7 · Lookup — tacit1 ID / txid / address / XNS name
Enter any of: a tacit1… unified address (decoded locally in your browser — the address never leaves this page), a Bitcoin txid or address, an Ethereum/Base tx or 0x address, or an XNS name like vitalik@eth (resolved live on-chain via getAddress()).
8 · Sources, CORS status & honesty notes
| source | used for | CORS for this page |
|---|---|---|
| api.tacit.finance /reflection/status | header relay height, bridge burns/mints, live notes | allows * |
| api.tacit.finance /confidential/index | full event index of the Ethereum ConfidentialPool (14k+ entries, wrapped volume) | allows * |
| api.tacit.finance /confidential/quote | fee floors and tips per asset | allows * |
| api.tacit.finance /assets, /amm/pools | Bitcoin-side etched assets, AMM reserves | build-time snapshot (CORS allowlists tacit.finance only) |
| mempool.space | Bitcoin tip height, tx/address lookup | allows * |
| mainnet.base.org | Base RPC: pool tree root/size, custody balance | origin echoed |
| ethereum-rpc.publicnode.com | Ethereum RPC: pool balance, XNS resolution | allows * |
| Base pool keeper | relayer fee quote for the Base EVM pool | allows * |
- Every live number above is fetched by your browser on page load; live marks the source. Reload to refresh.
- The assets/AMM table is a timestamped snapshot of the same indexer's mainnet data, saved at build time because of the route's CORS policy. Raw responses ship in
data/. - "All-time wrapped volume" is summed from the indexer's wrap entries — it is historical flow, not the pool's current balance (deposits get spent and withdrawn; the contracts' ETH custody is shown separately).
- Nullifier count can exceed leaf count because wraps and cross-outs consume nullifiers too.
- This page is read-only and has no backend: it cannot ask for keys, cannot sign, cannot move anything. Lookups of
tacit1…addresses are decoded in your browser and sent nowhere.