Documents
Every document published here comes with a checksum and a timestamp proof. Nothing has to be taken on trust.
Published
| Document | Version | Date | SHA-256 | Proof |
|---|---|---|---|---|
| White paper | 2.6 | 2026-09-11 | 6b9197b6c631a5e2a391a231aba505ebfaad3f10a90845d8602414bea6e256786b9197…e25678 | .ots |
| Periphery — appendix to the White Paperappendix | P1.0 | 2026-09-15 | f03efc9f6935ad9b269c6fa7ca2699945424ad89003d694b3a72b44f1b6e0a83f03efc…6e0a83 | .ots |
| White paper | 2.4 | 2026-09-08 | 6c06e6cd8c0a8f7ad33bf316ec57712336da34d74ece2ff0a10f36f90ea2897a6c06e6…a2897a | .ots |
| White paper | 2.3 | 2026-09-05 | d119a6d1a183326d3d3eb77cdcdebc0df86a2efeb72e34ca3279e52716db4abbd119a6…db4abb | .ots |
| White paper | 2.2 | 2026-09-02 | e7a2a2709b686ff2a42fd43f14dc3f0264acf65c6ce36b8be628b962d896ad47e7a2a2…96ad47 | .ots |
| Overview | 2.2 | 2026-09-03 | 255486f4c325e23ef59e4573456f0b33b226636e404e4151ca9e0e2bf35b3724255486…5b3724 | .ots |
| Overview, Chinese | 2.2 | 2026-09-03 | e1202ce1dab4a3a09351bec99ec6473d96895d7335886b3c23e6690094ef3d87e1202c…ef3d87 | .ots |
| Overview, Spanish | 2.2 | 2026-09-03 | 8225448d0d9828b3049ee3a0b03f4b1b0d6fa68c64ace4fe9eb7a88b832f0d14822544…2f0d14 | .ots |
| Presentation, September 2026 | 1.0 | 2026-09-04 | 4b870019a1acb0e4fcbe071a1516430a748c881690bdbd576bffe37141755b534b8700…755b53 | .ots |
| Brand guide | 1.3 | 2026-09-04 | 14709c26a76f1b5e6010d36e666860ace9237afb0eb37f7d120b157ef822ce9b14709c…22ce9b | .ots |
| Media kit: logo and banners | 1.2 | 2026-09-04 | a31a4faf4b44672ef139cf3ca8b101bf23540ccfdeff315152b14a9ba19411bca31a4f…9411bc | .ots |
Earlier versions are never removed. New rows are added below the current ones. The protocol specification is published together with the source code, after deployment. The full white paper and the specification are English only; the Overview is also published in Chinese and Spanish. Where a translation and the English text differ, the English text governs.
Changelog — Dated entries, newest first.
Around the protocol — Three things stand next to the protocol without being part of it: a router for Uniswap, a reader for the protection gate, and a planned position manager.
Testnet deployment — Assetrix runs on Arbitrum Sepolia, the test network of Arbitrum. This page says what is deployed there now and how to check it.
Verifying a checksum
Download the file, compute its SHA-256, and compare it with the value in the table. If the two match, the file you hold is byte-for-byte the one released.
macOS
shasum -a 256 Assetrix_DAO_White_Paper_2_6_EN.docx
Linux
sha256sum Assetrix_DAO_White_Paper_2_6_EN.docx
Windows, PowerShell
Get-FileHash Assetrix_DAO_White_Paper_2_6_EN.docx -Algorithm SHA256
Verifying a timestamp
The .ots file next to each document is an OpenTimestamps proof, anchored in the Bitcoin blockchain. It establishes the date on which that exact file existed. It does not establish who wrote it. Neither the checksum nor the timestamp requires trusting this project.
To verify, install the OpenTimestamps client and run it against the document and its proof:
ots verify Assetrix_DAO_White_Paper_2_6_EN.docx.ots
The client reports the block and the date. Do not re-save a document in a word processor before verifying: any change to its bytes invalidates the checksum and the proof alike.