Check it yourself
Check it yourself — before you ever call us
Attest1618, our enterprise evidence engine, seals evidence into documents any holder can check offline — no account, no network, no software of ours you cannot read first. It is licensable on its own: TXRA, our tokenised real-world asset platform, is its first customer, and any platform can license it without taking TXRA. This page is the whole kit, handed over in the open: the published specification, a verifier that is one dependency-free file, and sample documents to try it on — including a real record history carrying real receipts from authorities we do not run. Most prospects run it before the first meeting. We would rather you did.
The formats this kit specifies are Seal1618 — the enterprise protocol the engine checks against. Anyone may implement it, verification is free and stays free, and the format identifiers keep their producer prefix (txra.*) as stable technical identifiers rather than marketing names. Adopt the protocol and your records are accepted on sight, by parties who have never met you.
The kit
| File | What it is |
|---|---|
| txra-verify.cjs sha256 1d96d0323a843a33f5680d62279d7964e13bb1ea04c37f23ea2d6af4178021c7 | The reference verifier. One dependency-free file — read it in full, then run it. |
| SPEC.md sha256 cb7cabb3b8e7630c027158aac75099f614f8805d585431aaf09a12c4bf66aa36 | The complete verification specification: formats, hashing rules, and the exact recipe the verifier follows. |
| browser-verify.html ↗ sha256 bc881394a01bf7c742b57cd17054087e50326afdd64430da5525f60fcdd7ba72 | Every format in this kit, verified in a browser — paste or open any document and the page routes it by its tag, exactly as the CLI does, with no network request of any kind. |
| sample-receipt.html sha256 59847f61ef6b839a9f42571fa47fcd6e6e68ea706c01abf3f774bc877742c0c6 | The same pack as a finished deliverable — open it in any browser and it re-checks the seal on your own machine, offline. This is what a counterparty hands their client. |
| sample-pack.json sha256 2fd2ccd029e362379755e992c9abc985f2a6757da3074c40cde5b50cb5567a15 | A ten-item synthetic sealed pack. Every value is invented; the seal is real. Carries the deliverable envelope — who sealed it, and how to check it — and commits two documents from other systems: an operating-record export and an agent’s audit trail. |
| assetdna-export-synthetic.json sha256 c74b43d79976cc9c959df9ba282f1ec9641a0d8485540f8ad640bf1d2923ee2d | A synthetic operating-record export from a sibling platform, committed into the sample pack. Its own hash chain is real and re-derives under its published rule. |
| agenttrail-vectors.json sha256 84d531c4289a38c1b1539914fa533b87454147a3a19144be7075aca66b6ed9d4 | Conformance vectors for the agent-trail profile: twenty-one documents, each with the verdict a conforming verifier reaches and the checks that fail — intact, open, tombstoned, every tamper class, signatures with a test key. Implement the profile from the specification and check your verifier against these. |
| reconpack-vectors.json sha256 16fdb369ddbf83fec9adda59cb893d4c54293a893a8d03bcf026f025e985dd89 | Conformance vectors for the sealed reconciliation: eleven documents, each with the verdict a conforming verifier reaches and the checks that fail — two that verify, then one per defect, including a sealed payload that carries more than it shows. |
| reconhistory-vectors.json sha256 b87b23a03deeb3c8621af3af8d68c7dfad94eaca5a2fb1a2096cf7f9af3a1571 | Conformance vectors for the reconciliation history: thirteen documents — a cadence kept, a cadence broken, an entry left out that no reading can see, and every structural defect. |
| roothistory-vectors.json sha256 74fc36e5894b8361952f130063d125813b06ee0ddf78783d0d07ee226b863963 | Conformance vectors for the root history: fourteen documents — one valid, one per check, and four that verify on their own and can be contradicted only by a copy someone held earlier. |
| txra_agenttrail.py sha256 10c15db6ffa9a36875de7650bea8bef9b48528dead8005b676cedec3b8d38db4 | A second implementation of the agent-trail profile, in Python, written from the specification’s text with no code shared with the reference: it verifies trails, produces them, and runs the conformance vectors. Standard library plus the openssl command. |
| sample-agenttrail.json sha256 63901be7efbd6fe871696692f46c83aaa3561d9a5c764e9669da3e39660f0811 | A synthetic audit trail of one AI-assistant session, under the specification’s profile of an IETF Internet-Draft for tamper-evident agent logs: five hash-chained records ending in a session hash, committed into the sample pack. Every hash is over invented content; the chain is real, and the verifier also accepts the draft’s own raw JSONL export. |
| roothistory-sample.json sha256 58285a0eb7f475901a9fcab638c8c7c09a50e80a6dd354b949a78d274e0282a7 | A real root-history document from a development stack — three anchors, entangled, each carrying two real receipts: an RFC 3161 timestamp token from a free public timestamp authority, and an entry in a public transparency log you can fetch yourself by its log index, without anything we issued. The production configuration is a separate decision and is not shown here. |
| sample-reconpack.json sha256 ffd64be1ab5772b54b9b5d817f31fcee32f684f3077cfcdc8c3614a9d19505fe | A synthetic sealed reconciliation — the register-to-token comparison as a sealed document. The holdings are invented; the seal, and the arithmetic under it, re-derive for real. |
| sample-reconhistory.json sha256 b41842dc2dfbdec1d67476e2b30d020b66cade41f8f6cacc27ab80c23580fdac | A synthetic reconciliation history that deliberately does not look good: fourteen daily seals, then seventy-seven days of silence against a cadence committed before the window opened. The document is well-formed either way — the silence is the information. |
| LICENSE.md sha256 176e568b7c557ad27c3b2a9619fc3be5d0c157f3ac81eeec3dc27d743451f2a4 | The licence the kit is published under: free to verify and free to implement, in writing — a permissive licence for the specification and the verifier files, and a patent non-assertion. |
The receipt needs nothing installed — open it and it verifies itself in your browser. For the raw documents, checksums are also in SHA256SUMS.txt. Then, with Node installed:
node txra-verify.cjs sample-pack.json --evidence assetdna-export-synthetic.json --evidence sample-agenttrail.json node txra-verify.cjs sample-agenttrail.json node txra-verify.cjs roothistory-sample.json node txra-verify.cjs sample-reconpack.json node txra-verify.cjs sample-reconhistory.json
A pass tells you the seal is intact, the history re-derives and holds together, the committed external document is byte-identical to what was relied on — and, where receipts are present, that each one is over exactly the record it claims. The verifier also prints what it did not check, every run; the specification states each limit in full.
What we refuse to claim
- We do not claim the facts inside a sealed record are true. We prove which facts were relied on, under which written policy, sealed before the outcome was known.
- We do not claim "tamper-proof". The claim is tamper-evident, with its exact scope written into the specification — and the verifier prints what it did not check, every run.
- We do not claim that verifying a record requires a public blockchain, a token, or any chain at all. The record of authority is private; the proof of it is portable and chain-agnostic — it verifies offline, on no chain and every chain. Where a platform issues tokens of its own, that is its product decision and the proof layer never inherits it: the token mirrors the register, and the reconciliation between them becomes one more thing you can check here rather than take on trust.
- We do not claim a chain proves more than it does. The kit can now read a receipt that publishes a record’s fingerprint — one 32-byte value, never an event, a payload, or anything derived from a person — to a public Ethereum network, and it checks that receipt from its own bytes offline. What it deliberately does not do is tell you the network accepted it: that is the one thing you can establish without us, from any block explorer, and a verifier that reported it on our say-so would have spent the only thing a public chain buys.
- We do not claim a receipt from a test network is permanence. Test networks are reset at their operators’ discretion; a receipt from one rehearses the path and proves nothing about what survives. The verifier says so beside the receipt rather than letting a passing check imply otherwise.
- We do not claim certifications we do not hold, and our demonstration data never names a real body as having registered or certified an invented thing.
- We do not claim a receipt exists where none does. Unwitnessed records are counted and reported, never invented.
If you hold a sealed document of ours and want to check it, everything you need is above. If you want one of your own — talk to us. Demonstration access is granted personally, never automated.