Provenance
Last updated: .
This page lists the public records that fix the AXL Protocol v1.0.0 whitepaper to a specific moment in time. The artifact is a single HTML file, axl-whitepaper-v1.0.0.html, with SHA-256 87c9f72fbb9f45aa34d34b20f4a78a27ff128d49c6275ec155774341b6000b86. It is anchored to four independent services. Each anchor was created by an operator we do not control, and each is verifiable from its source without trusting axlprotocol.org.
The reason a semantic-layer protocol needs this is narrow. A grammar for agent-to-agent communication makes testable claims about token counts, comprehension, and priority. Those claims need a time axis that a third party can confirm. "March 2026" printed in a PDF is not that. A SHA-256 of the exact bytes, submitted to public services at a timestamp those services record independently, is.
Summary: four anchors, 19-hour window
| # | Anchor | Timestamp (UTC) | Operator |
|---|---|---|---|
| 1 | OpenTimestamps + Bitcoin calendars | 2026-03-19T18:18:40 | OpenTimestamps network |
| 2 | GitHub release axl-core@v0.4.0 | 2026-03-19T22:08:43 | GitHub, Inc. |
| 3 | PyPI release axl-core==0.4.0 | 2026-03-19T22:43:27 | Python Package Index |
| 4 | Wayback Machine snapshots | 2026-03-20T14:33 to 14:37 | Internet Archive |
A retroactive backdate of any of these would require collusion across four unrelated services. The composite record is materially stronger than any single anchor.
01 OpenTimestamps + Bitcoin Bitcoin block: confirmed
What this anchors. The SHA-256 of the whitepaper bytes, committed to the OpenTimestamps calendar network at 2026-03-19T18:18:40 UTC (the protocol-level embedded timestamp in the .ots receipt). OpenTimestamps aggregates submitted hashes into a Merkle tree and embeds the tree root in a Bitcoin transaction; once included in a block, the block's proof-of-work retroactively pins every hash in that tree.
Status. Confirmed in Bitcoin. The receipt was upgraded on 2026-04-25 by running ots upgrade against the live calendars, which returned BitcoinBlockHeaderAttestation entries for three of the four calendars. The earliest confirmed block is Bitcoin block 941334 (block hash 000000000000000000013536f01dd0b8463cce61bab3c914e5ac8eb78f99597f, mined 2026-03-19 20:20:24 UTC), via btc.calendar.catallaxy.com. Two additional calendars (alice.btc, bob.btc) confirmed at blocks 941335 and 941338 respectively. finney.calendar.eternitywall.com has not yet returned a BitcoinBlockHeaderAttestation and its path still carries a PendingAttestation. The three confirmed paths are sufficient: any one of them independently proves the hash was known before block 941334.
Calendars this proof aggregates through:
- finney.calendar.eternitywall.com
- btc.calendar.catallaxy.com
- alice.btc.calendar.opentimestamps.org
- bob.btc.calendar.opentimestamps.org
Raw artifacts on this page:
Verify from source
# Install the client
pip install opentimestamps-client
# Download the artifact and its receipt
curl -O https://axlprotocol.org/timestamps/axl-whitepaper-v1.0.0.html
curl -O https://axlprotocol.org/timestamps/axl-whitepaper-v1.0.0.html.ots
# Confirm the hash
sha256sum axl-whitepaper-v1.0.0.html
# Expected: 87c9f72fbb9f45aa34d34b20f4a78a27ff128d49c6275ec155774341b6000b86
# Inspect the receipt (no network required)
ots info axl-whitepaper-v1.0.0.html.ots
# Full on-chain verification against Bitcoin
ots verify -f axl-whitepaper-v1.0.0.html axl-whitepaper-v1.0.0.html.otsOn macOS replace sha256sum with shasum -a 256. ots info reads only the local file; ots verify queries the calendar servers and your Bitcoin node, if present.
How the upgrade was done
When the receipt was first created on 2026-03-19, it contained only PendingAttestation entries because the calendar servers had accepted the hash but had not yet settled it into a Bitcoin block. On 2026-04-25, ots upgrade axl-whitepaper-v1.0.0.html.ots was run against the live calendars. Three of the four returned a complete Merkle path terminating in a BitcoinBlockHeaderAttestation. The .ots files on this page are the upgraded receipts. Running ots info on them now shows the Bitcoin block path inline.
02 GitHub release v0.4.0 Verified
What this anchors. The first public release of axl-core (parser, emitter, validator, translator, CLI), published less than four hours after the OpenTimestamps submission. The release body links to the v1.0.0 whitepaper at axlprotocol.org/whitepaper/. The release is not a cryptographic anchor of the whitepaper hash itself, but it is a GitHub-attested, same-day public artifact that names the whitepaper and cannot be backdated on the API (any edit updates updated_at).
| Release URL | github.com/axlprotocol/axl-core/releases/tag/v0.4.0 |
| API URL | api.github.com/repos/axlprotocol/axl-core/releases/299176686 |
| Release ID | 299176686 |
| Tag | v0.4.0 |
| Tag commit SHA | 3410b0be0e51eac0373ce919d01a593eb2715eed |
| Author | dcarranza-axl (user id 269558077) |
| created_at | 2026-03-19T22:08:29Z |
| published_at | 2026-03-19T22:08:43Z |
Raw artifacts on this page:
Verify from source
curl -s https://api.github.com/repos/axlprotocol/axl-core/releases/299176686 \
| jq '{tag:.tag_name, id, commit:.target_commitish, author:.author.login, published_at, created_at}'03 PyPI axl-core 0.4.0 Verified, immutable
What this anchors. The same codebase tagged at GitHub, packaged and uploaded to the Python Package Index roughly 35 minutes after the GitHub release. PyPI disallows file replacement after upload: once a version is published, the file digests are fixed for the life of the release. Deleting and re-uploading the same version number is not permitted.
| Project URL | pypi.org/project/axl-core/0.4.0/ |
| API URL | pypi.org/pypi/axl-core/0.4.0/json |
| Wheel upload_time | 2026-03-19T22:43:27 |
| Wheel sha256 | 31cc8f2051ea7787fd0aeec6c7a130b08cb407207ea9d0906251213178041b90 |
| sdist upload_time | 2026-03-19T22:43:28 |
| sdist sha256 | dc73c4158679776cf4619dacd1bb23b230a34014c420d2d0806a513d06b1c4e4 |
Raw artifacts on this page:
Verify from source
curl -s https://pypi.org/pypi/axl-core/0.4.0/json \
| jq '.urls[] | {filename, sha256:.digests.sha256, upload_time, packagetype}'04 Wayback Machine Verified
What this anchors. The Internet Archive captured axlprotocol.org and the axlprotocol/axl-core GitHub repository on 2026-03-20 between 14:33:00 and 14:37:17 UTC. The whitepaper plaintext snapshot opens with the literal byline:
AXL: Agent eXchange Language. A Universal Communication Protocol for Agents and Autonomous Machines. Whitepaper v1.0.0. Diego Carranza. AXLPROTOCOL INC . March 2026. https://axlprotocol.org
That fixes the whitepaper content, byline, and self-declared publication month inside a third-party archive at a timestamp that archive records. The CDX digest column below is the Internet Archive's content fingerprint for each snapshot; snapshots are not synthesizable retroactively because the archive is an external, multi-tenant, operator-independent service.
| Page | CDX timestamp | Digest | Bytes |
|---|---|---|---|
| github.com/AXLPROTOCOL/axl-core | 20260320143300 | Z5A2HEYX6VOS66UBSWODRJXA6IMW7JKL | 62,605 |
| axlprotocol.org/rosetta | 20260320143346 | 63UR4VPN54Q3HFEV4XGQRM5OB6K72OJC | 3,876 |
| axlprotocol.org/whitepaper/ | 20260320143646 | CS5PQMV7OSXRMW7J5RASUUI6H7PADVVV | 4,759 |
| axlprotocol.org/whitepaper (plaintext) | 20260320143647 | YXWUBHMGLSWDXNC6YK4C7YMLGETBMJ3Q | 14,452 |
| axlprotocol.org (landing) | 20260320143705 | BKK4AWBOF3V6HYELG72R2KVRITISZB5F | 8,059 |
| axlprotocol.org/results/v2/ | 20260320143657 | J5SFP2CK4Z5QQUXEDHRH3DDVNNESCSFY | 5,618 |
| axlprotocol.org/terminal/ | 20260320143657 | 4DEJZ7O4FZQSA24MHNXLTTCDWWRFYMIK | 3,602 |
Raw artifacts on this page:
Verify from source
curl 'https://web.archive.org/cdx/search/cdx?url=axlprotocol.org/*&from=20260319&to=20260322&output=json'What this does not prove
These anchors fix the document hash and the public reachability of the axlprotocol.org site to a specific moment in time (2026-03-19 to 2026-03-20 UTC). They do not prove that the ideas in the whitepaper originated at that moment, nor that this document is the first articulation of those ideas. Prior work, prior art, and independent discovery are separate questions that a cryptographic timestamp cannot answer. Provenance is necessary but not sufficient evidence of priority. Anyone reviewing these artifacts for priority purposes should also examine the research log, the commit history, and contemporaneous context, not the timestamp alone.
A note on negatives: the whitepaper is not anchored to IPFS, Arweave, sigstore, cosign, PGP, Zenodo, DOI, arXiv, or any non-Bitcoin blockchain. Those records do not exist. The surface is exactly the four anchors listed on this page.