ICPO X™ · Public Transparency Record
Claims need
evidence states.
This page distinguishes confirmed commitments from pending work and legacy assertions under review. A blockchain reference is not treated as proof of an ICPO X record unless the relevant transaction, payload, and status are available for independent examination.
What anchoring proves
A Bitcoin anchor might prove that a particular fingerprint existed no later than a certain time. It does not, by itself, prove authorship, accuracy, lawful possession, contractual assent, or the truth of the underlying document.
Baby Shakespeare publication record
The publication record has a confirmed Bitcoin OP_RETURN at block 961,305 and a public Arweave record.
Open record →
COMMONS-VATS-001 Bitcoin commitment
The VATS specification has confirmed Arweave publication. Its Bitcoin OP_RETURN commitment is pending and is not represented here as confirmed.
Open record →
Legacy system-disclosure assertions
Earlier block-height and capital-accounting assertions are not presented as confirmed anchors. They remain outside the public proof record until independently reconciled with a transaction ID and payload.
Open record →
Verification standard
A confirmed Bitcoin record requires a transaction ID, independently retrievable OP_RETURN data, and a confirmed block. Arweave publication is described separately because it is a different permanence layer.
A pending status is not a failed record or a completed Bitcoin anchor. It means the claimed Bitcoin commitment has not yet met the confirmation standard above.
This is a provenance disclosure, not an offer of a security, an investment product, or financial advice.