X LAYER MAINNET · CHAIN 196 · PUBLIC READS ONLY
Understand the contract.
Before the transaction.
Independent, live-read TapeOut factory, circuit market and processor transparency. Inspect fees, upgradeability and on-chain state without connecting a wallet or broadcasting a transaction.
▶ Watch 29-second real comparison ↗
Request a paid evidence pilot ↗
Free agent API preview · no payment ↗
Paid agent API · 0.005 Base USDC (HTTP 402) ↗
Not loadedConnect to public X Layer RPC to begin.
01 / CONTRACT CONTROLS
Upgrade & authority surface
Factory implementation—
Factory owner—
Factory sealed—
Market implementation—
Market owner—
Market sealed—
Market next listing ID—
A proxy implementation slot and a false sealing flag signal that administrative changes may remain possible. They do not establish malicious behavior or prove the current implementation unsafe.
02 / PROCESSOR INSPECTOR
Inspect any TapeOut CPU
Circuits contract—
Transistor token—
Processor creator—
Circuits minted (last ID)—
Transistors minted / cap—
Transistor mint unit price—
Tapeout fixed fee—
Processor 0 is TapeOut's genesis X Layer CPU. CPU address and protocol terms are read from the factory and processor contracts at the same block.
03 / COST SIMULATOR
Fee preview — no transaction
Mint transaction value—Token units × current processor mintPrice + its flat protocolFee; network gas not included.
One tapeout contract fee—Excludes gas and NAND/LATCH input inventory consumed by circuit design.
Quotes are snapshots, not executable offers. Read fees again before any owner-operated transaction; this tool never creates or signs one.
04 / VERIFICATION NOTES
What deserves a second look
- No data yet. Read chain state to inspect configuration.
05 / HISTORY · CROSS-BLOCK DIFF
What changed since your last snapshot?
Import an earlier JSON export of the same TapeOut processor, then compare its recorded block to the current X Layer reading. Try the bundled public historical CPU0 example in one click or import your own local file; only a strict allowlist of 20 on-chain fields is compared. Partial reads, wrong networks, mismatched CPU indexes and malformed values fail closed.
The file stays in your browser: no uploads, wallet connection, signing or transaction. You may use our earlier CPU0 snapshot when inspecting CPU 0. A real two-block example from 23 October illustrates an observed count change and a proxy implementation-address difference (not a security finding). Imported JSON is user-supplied, not cryptographically authenticated; a detected difference is not proof of an exploit, threat or security audit.
Load the live state, then select an older JSON snapshot to compare.
Inspect the source, not the marketing.
Every value comes from public on-chain reads pinned to a common block. Export an evidence snapshot with block number, contract addresses and retrieved values. This is operational transparency—not a security audit, token endorsement, custody check, escrow verification or financial advice.