TACITLENS 🔍

One page, both chains. Tacit issues and moves assets in Taproot envelopes on Bitcoin, the same confidential notes live in a pool on Ethereum (plus the multichain EVM pool on Ethereum, Base & Robinhood Chain), and SP1 proofs carry state between them. Everything below is fetched live from public mainnet sources when you open this page, and re-read in full every 30 seconds — no mock data, no wallet, no sign-in, no keys, ever.

Bitcoin Tacit API Ethereum Base Robinhood

🌉 The bridge — Bitcoin reflection into the EVM pool BRIDGE

Source: Tacit relay API GET /reflection/status?network=mainnet · relay GET /confidential/relay · Bitcoin headers are relayed on-chain by the BitcoinLightRelay (0x20A6…19D0) — its tip is also read directly from the contract here via eth_call tipHeight(), and the lag is coloured against the fold depth; SP1 proofs fold Bitcoin state into the pool once blocks are 24 confirmations deep.

…loading

✔️ Cross-checks — the headline numbers, read twice VERIFY

Every explorer asks you to trust its numbers. This panel re-reads the load-bearing ones from a second, independent source — or recomputes them from raw values — right here in your browser, and shows both sides whether they agree or not.

CheckFirst readSecond read / recomputedVerdict
Running cross-checks…

A mismatch is shown, not hidden: the two reads happen seconds apart, so a one-block difference on a moving chain is normal — anything larger is flagged as-is.

🧪 Reproduce every number yourself VERIFY

The cross-checks above re-read the numbers inside your browser. These commands re-derive the same figures from your own terminal, against the same public sources — no wallet, no signature, no gas, every one of them a read. cast is Foundry's CLI (getfoundry.sh); the two curl commands need nothing else. Values move with the chain, so re-run a command and compare it with the panel above — that is the point.

FigureCommand (tap copy)What it checks
Bitcoin tip heightcurl -s https://mempool.space/api/blocks/tip/heightThe chain tip the bridge lag is measured against.
Reflection / bridge statecurl -s "https://api.tacit.finance/reflection/status?network=mainnet"Attested height, relay tip, lag, bridge burns vs mints, live notes — the same JSON the bridge panel reads.
Header-relay tip, on-chaincast call 0x20A6ddc2C6E620c6248B5A34E85996516FDd19D0 "tipHeight()(uint256)" --rpc-url https://ethereum-rpc.publicnode.comThe relay contract itself, not the API's view of it — the second read behind the cross-checks panel.
cBTC backing (sats)cast call 0x000000000Ed1eabD231Be41d93b719056F7febFC "cbtcBackingSats()(uint256)" --rpc-url https://ethereum-rpc.publicnode.comReflection-attested BTC locks in the ConfidentialPool, in sats.
cUSD debt outstandingcast call 0x000000003f608BDdF0ca45934003ffb9DbDF70DB "outstandingCusd()(uint256)" --rpc-url https://ethereum-rpc.publicnode.comCDP debt outstanding on the CollateralEngine.
TAC supplycast call 0xA1313eb9f3A445606D9583bcAc3ebeB56a858279 "totalSupply()(uint256)" --rpc-url https://ethereum-rpc.publicnode.comCanonical TAC ERC-20 supply (18 decimals) — the same read behind the pool panel's token table.
XNS name resolution, both directionscast call 0x6e797ba2d3103aF167918e71a7E01DE40D45f74b "getAddress(string)(address)" "vitalik@eth" --rpc-url https://ethereum-rpc.publicnode.comXNS resolution on-chain: vitalik@eth → 0xd8dA…6045, and the reverse getName for that address returns vitalik@eth — both directions verified live 9 Nov 2026.

If a command and its panel disagree, trust the command — then tell us: the page is a reader of these same sources, not a source of its own.

⚖️ How this entry meets the bounty's four judging criteria JUDGING

The bounty judges on four things — Useful, Correct, Clear, Honest about privacy. Each one points at the panel above that proves it, so a contributor can check the claim instead of taking our word for it.

UsefulWould you keep it open? One page, both chains: bridge, envelopes, confidential pool, EVM pool & farms, secondary market and footprint lookup — re-read live every 30 seconds.
CorrectDo the numbers match the chain? Cross-checks re-reads every load-bearing figure from a second, independent source or recomputes it from raw values — the reproduce panel lists the exact terminal commands to re-derive each one yourself, and the provenance table gathers every contract this page reads in one place. A mismatch is shown, not hidden.
ClearDoes it make two chains easier to understand? The bridge panel folds Bitcoin reflection, relay lag and in-flight burns/mints into one view, and every figure carries its source chip.
Honest about privacyWhat's public and what's hidden: the privacy panel is measured from the panels above, names the relay-witness caveat, and the lookup applies the same boundary to your own footprint.

✉️ Bitcoin — recent envelopes BITCOIN

Sources: Tacit indexer GET /assets?network=mainnet (etches & burns are envelope events; the indexer API only allows the tacit.finance origin via CORS, so from here it is read through a public CORS relay — the data is still Tacit's own JSON) · cross-check on tacitscan.io (its JSON feed sends no CORS header, so this page links out instead of embedding it). Amounts inside transfer/mint envelopes are Pedersen commitments — the feed can show that an envelope exists, never how much moved. One cadence note, stated plainly: transfers — the frequent activity, thousands counted in the stats above — are published by Tacit's indexer only as totals, never as individual events, so this feed lists the envelope events that are individually published: etches, mints and burns. Those are rare on Tacit by nature, so a fresh fetch can still show an old event — that is the chain's pace, not stale data; the fetch itself is live every load.

Loading envelope events…

🪙 Bitcoin — assets & the native AMM pool BITCOIN

Sources: Tacit indexer /assets + /amm/pools (network=mainnet, read via a public CORS relay — see the envelopes panel). Holder/transfer counts are the indexer's chain-derived state.

Loading AMM pool…

AssetHoldersTransfersEtched at block
Loading…

🏷️ Bitcoin — the secondary market BITCOIN

Source: Tacit indexer GET /market?network=mainnet (read via a public CORS relay — see the envelopes panel). Listings are signed Bitcoin-side offers: the amount and the price in sats are public by design — a market cannot hide its own prices. Expired listings are filtered out.

…loading
AssetLive listings24h volumeHolders
Loading…

Latest listings

Loading listings…

Latest trades

Loading trades…

🤫 Ethereum — the ConfidentialPool ETHEREUM

Sources: public Ethereum RPC (ethereum-rpc.publicnode.com) eth_call on the immutable pool 0x0000…ebFC (deployed block 25,998,736) + CollateralEngine 0x0000…70DB · relay board GET /confidential/open.

…loading

Canonical ERC-20s minted by the pool (live totalSupply)

TokenSupplyContract
Loading…

cBTC / cUSD mostly live as confidential notes inside the pool — the ERC-20 supply is only the part that has been unwrapped to public form. wTAC is the 1:1 farm-reward wrapper of TAC.

⛓️ EVM pool — Ethereum, Base + Robinhood, and the launch farms ETH BASE ROBINHOOD

Sources: Tacit EVM-pool keepers (keeper /head, /events — the separate private-ETH pool, same address 0x0000…BEE9 on every chain — all three read live here, Robinhood Chain (4663) included) · farms GET /farm/program + /farm/health.

…loading

Latest EVM-pool transactions (keeper events)

Loading…

🕵️ The privacy boundary — what this page can and cannot see HONEST

This panel is grounded in what the panels above actually fetched. Tacit hides amounts (Pedersen commitments + Bulletproofs) and note-to-note links — it does not hide that activity happened. Anyone telling you otherwise is overselling it.

…measuring from the panels above
👀 An observer CAN see
  • That a Bitcoin envelope exists, its type (etch / transfer / mint / burn), its txid, block and time — the feed above is exactly that.
  • Counts: holders, transfers, burns, live notes in the pool, bridge burns vs mints, farm emissions.
  • Public legs: wrap/unwrap recipients and amounts when value enters or exits the pool in public form, ERC-20 supplies, fees and relay job types on the open board.
  • Timing and public addresses on both chains — including yours, if you look yourself up below.

Relay caveat (from Tacit's own build guide): if you ask Tacit's relay to prove a transaction for you, the relay sees that op's witness — the notes it spends/creates and, for non-blind swaps, its amounts. Proving locally keeps the witness on your device. This page never asks for a key, a seed, or a signature, and it moves no funds — it only reads public endpoints.

📜 Provenance — every contract this page reads, in one place SOURCES

Each address below is already cited in the panel that reads it — this table only gathers them, so a contributor can check any figure against the contract itself without hunting through the page. All addresses come from Tacit's official DEPLOYMENTS.md. The Bitcoin-side numbers come from Tacit's public indexer (api.tacit.finance, no key) and public Bitcoin explorers; the EVM numbers are eth_call reads on the contracts below via public RPC.

ContractChainAddressRead by
ConfidentialPoolEthereum0x000000000Ed1eabD231Be41d93b719056F7febFCConfidentialPool panel, reproduce
CollateralEngineEthereum0x000000003f608BDdF0ca45934003ffb9DbDF70DBConfidentialPool panel, reproduce
BitcoinLightRelayEthereum0x20A6ddc2C6E620c6248B5A34E85996516FDd19D0Bridge panel, reproduce
TACEthereum0xA1313eb9f3A445606D9583bcAc3ebeB56a858279Token table, reproduce
tacBTC / cBTCEthereum0xdf1d99148bEb7a9AFf1d95C49B3d22b7ed90D696Token table
tacUSD / cUSDEthereum0x23cACFFAc2674514A6d4F6cD420B4cc2aC921564Token table
wTACEthereum0x2018139a8FDd3666855BE3315C7683b4D6aB7AEfToken table
TacitEvmPool (pay pool)Ethereum · Base · Robinhood Chain0x000000c2A20657CE25f2Ba99737933D031AFBEE9EVM pool & farms panel
XNS registryEthereum0x6e797ba2d3103aF167918e71a7E01DE40D45f74bLookup, reproduce

If any address here disagreed with DEPLOYMENTS.md, the panels reading it would be wrong — that is why the list is explicit: the check takes one click per row.

🔎 Look up your own footprint LOOKUP

Paste a tacit1… ID, a Bitcoin txid (64 hex), a Bitcoin address (bc1…), an EVM address (0x…), an EVM tx hash, or an XNS name (name@namespace). See exactly what is public about it — that is the privacy boundary, applied to you. XNS resolution is read on-chain from the XNS registry 0x6e79…f74b (getName/getAddress) — bonus implemented ✅ (e.g. vitalik@eth resolves on-chain to 0xd8dA…6045).

Nothing entered yet. Try the pool contract itself: 0x000000000Ed1eabD231Be41d93b719056F7febFC, or vitalik@eth — tap an example to run it.