T✦TapeOutUPGRADE GUARD
X LAYER MAINNET · READ ONLY

Know what changed
before you trust the upgrade.

Proof of deployed bytecode and implementation pointers for TapeOut factory and beacon contracts. One pinned block. Independently reproducible.

Independent, AI-assisted owner-operated prototype. Not affiliated with TapeOut or OKX. Not a security audit, exploit report, continuously running monitor, or investment recommendation.

01 / ONCHAIN EVIDENCE

Verified runtime snapshot

LOADING
CHAIN ID—X Layer mainnet
PINNED BLOCK—UTC timestamp
COMPONENTS—Factory / Beacons
SPENT / SIGNED0Read-only collection

ACTUAL RUNTIME ADDRESSES · CODE SHA-256

Loading locally published evidence…

Documentation vs. live pointer

A third-party deployment reference may be stale. A difference is a signal for further verification—not proof of a malicious upgrade.

Checking…

Pinned block hash: —

02 / OFFLINE COMPARISON

Did the implementation change?

BROWSER-LOCAL

Upload two locally generated JSON snapshots. Files stay in your browser; no web3 wallet, token, tracking SDK or backend upload. Compare the EIP-1967 pointer, beacon implementation pointers, runtime code hashes and owner() observations.

Select two locally generated snapshots to compare them. An unchanged pair does not rule out intermediate changes.

03 / OPTIONAL PAID PILOT

Need a change-evidence report?

QUOTE ONLY · NO SALE CLAIMED

For an X Layer integrator maintaining an owner-authorized public deployment: request a bounded, evidence-first release comparison. Public core verification stays free. You pay only under separately agreed terms; no wallet connection or token transfer is needed to inquire.

STARTER CHECK · PROPOSED PRICE9 USDC

Two pinned X Layer snapshots, implementation-pointer drift table, code hash comparison, concise factual exceptions. Buyer provides public addresses only.

RELEASE EVIDENCE REPORT · PROPOSED PRICE19 USDC

Starter output plus a source-reference discrepancy table, one bounded question-and-answer round and a human-reviewed delivery if scope is agreed.

Request scope and payment terms

Briefly describe your public contract addresses, approximate release window and the one decision the evidence must support. AI assistance will be disclosed. No live exploits, financial guarantees, private production access or security certification are offered. A written agreement, owner eligibility and supported payout network must precede delivery.

Ask for a quote ↗

These are seller-proposed indicative fees, not customer-approved budgets. Confirmed clients: 0. Confirmed sales: 0. Wallet signing, deposits, up-front setup fees and secret keys are not requested.

04 / METHODS & LIMITS

Evidence, not inference

01

Pin a block

Read chain ID 196, block number, hash and UTC timestamp.

02

Resolve pointers

Factory EIP-1967 implementation storage and each beacon implementation() response.

03

Hash code

SHA-256 of runtime bytes for each proxy, beacon and referenced implementation.

04

Compare snapshots

Surface changed addresses, code fingerprints and optional control observations.

REPRODUCE WITH NO WALLET
python3 -B tapeout_guard.py snapshot --out evidence/now.json
python3 -B tapeout_guard.py diff evidence/previous.json evidence/now.json
This is not a security guarantee.

Contract safety, code-to-source matching, timelock/multisig signers, intermediate upgrades, payment backing, fee safety and treasury reserves are not established by this prototype. The deployment source is a third-party reference and should be cross-verified. RPC responses are not consensus proofs. SHA-256 fingerprints are not Ethereum keccak-256 hashes.