Verification Record
The AI-Blockchain Symbiosis: Verification, Power, and Autonomy in the Age of Synthetic Intelligence
What this page is
This page is not a showcase of the book's contents. It is a public anchor of integrity.
The base version of the manuscript — the exact PDF file that produced the paperback edition — was subjected to two independent cryptographic operations: the computation of its SHA-256 hash, and the anchoring of that hash on the Bitcoin blockchain via the OpenTimestamps protocol. This page publishes the artefacts of that operation so that anyone, at any time, can confirm that the manuscript has existed since a specific date (proof of anteriority) and that it has been registered with a public authority (proof of institutional registration).
A third proof also exists — the proof of correspondence between a specific copy and the registered version. That verification presupposes access to the base file and is therefore reserved for specific contexts: authorship disputes, audits, academic investigation, forensic examination. It is not a routine action for the general reader, but it is an action available when required.
The page applies to the book itself the verification architecture the book describes. It does not ask you to trust the thesis — it publishes the proofs that allow you to test it.
Cryptographic proof
Files for verification
- hash_sha256_EN_base.txt — hash as plain text
- The_AI_Blockchain_Symbiosis_EN_base_2026-04-20.pdf.ots — OpenTimestamps proof
How to verify
The chain of proof has three links. The first two are executable by anyone with an internet connection, and are sufficient to confirm that the manuscript existed on 20 April 2026 and has been registered with the Portuguese state. The third is executable only by those with access to the base file — in cases of authorship dispute, audit, or investigation — and is documented here for when it becomes necessary.
1. Verify the Bitcoin blockchain anchor
The OpenTimestamps proof (the .ots file) establishes that the hash existed on the Bitcoin blockchain from block 945970 onward (mined on 20 April 2026). The file contains multiple attestations to different Bitcoin blocks — a normal OTS practice that strengthens the proof through redundancy across independent calendars.
There are three paths to confirm this anchor, with increasing rigor. Choose the one that fits your context.
Path A — Existence of the Bitcoin block (30 seconds, no files)
Click the link to the block referenced in the proof panel above: mempool.space/block/945970. The public explorer shows that the block exists on the blockchain, was mined on 20 April 2026, and is buried under the accumulated proof-of-work of every Bitcoin block mined since. Altering its content retroactively would require computational capacity exceeding that of the entire Bitcoin network over the whole elapsed period, an energy cost that in practice makes the anchor immutable.
This path confirms that the block we reference is real. It does not, by itself, prove that the .ots file on this page points to that block — for that, path B.
Path B — Verify the OpenTimestamps proof (2 minutes, no PDF needed)
Download the .ots file from this page and submit it to a public verifier that processes the .ots alone:
- dgi.io/ots/ — tool maintained by the Digital Gold Institute. Drop the file into the box and the verifier returns the Bitcoin block and date directly.
- Command-line client (if you prefer):
pipx install opentimestamps-clientfollowed byots info file.ots, which lists the Bitcoin attestations in its output.
This verification proves that the file you hold points to block 945970. Combined with path A, it establishes that a real Bitcoin anchor exists for the manuscript's hash — without requiring the base PDF.
Note that opentimestamps.org also performs verification, but requires the original PDF in addition to the .ots, so it falls under path C below.
Path C — Full cryptographic verification (requires access to the PDF)
This path reconstructs the entire proof chain: from the PDF's SHA-256 hash, through the operation tree, up to the merkle root inside the Bitcoin block. It is executable only by those with access to the base PDF file — documented in section 3 below.
2. Verify the institutional registration
The IGAC (Portuguese Inspectorate-General for Cultural Activities) maintains the literary-work registration in its own archive. The cross-reference between the cryptographic anchor (proof of public anteriority, impossible to forge) and the institutional deposit (proof of formal registration with the state) makes it virtually impossible to contest the manuscript's authorship and creation date. The Portuguese edition holds registration number 596/2026, granted on 22 April 2026; the English edition holds registration number 610/2026, granted on 27 April 2026.
Any person can, in principle, consult the IGAC's records through the normal administrative channels. In practice, for the reader who merely wishes to confirm that the book is registered, the public reference to the registration number on this page and in the published copies is, in itself, verifiable by documentary comparison.
3. Verify exact file correspondence (reserved for specific contexts)
This third proof establishes that a specific PDF copy is, bit for bit, the one that was hashed and anchored. It is executable only by those with access to the base file — typically in contexts of dispute, expert examination, or formal investigation.
For those in such contexts, the procedure is trivial. On Linux or macOS, from the terminal:
sha256sum The_AI_Blockchain_Symbiosis_EN_base_2026-04-20.pdf
On Windows, from PowerShell:
Get-FileHash The_AI_Blockchain_Symbiosis_EN_base_2026-04-20.pdf -Algorithm SHA256
If the resulting value is identical to the one published above, the file is, bit for bit, the registered base version. If it differs by even a single character, it has been altered. Access to the base file outside these contexts is not provided by this page — the commercial edition (the published book) is a distinct editorial object, with an embedded Verification Note, which by definition produces a different hash.
Scope of the proof
The proof refers exclusively to the base version of the paperback — the final manuscript as it existed before the Verification Note was added to the published edition. The Verification Note in the published book cites the hash of the base version, which would make it circular to hash the published version itself.
The ebook and hardcover are derivatives of the same editorial manuscript and share the content of the base version. The paperback proof substantively covers all three formats.
Source
Tiago Pinto, author. Contact via @cryptogeekpt. This page is served from the author's dedicated server, in static HTML, without JavaScript, without analytics, without cookies, without external dependencies. The source code for this page, along with the cryptographic artefacts, is published on GitHub for public inspection and mirroring.