IronChain - the proof protocol on Solana

A proof is easy to start and hard to finish

IronChain writes verifiable records of things that happened in the real world: a training session, a shift, an inspection, a rehabilitation exercise. The hard part is not writing to a chain. It is doing so without leaking personal data, without paying a fee per event, and without trusting the person being measured.

Nothing personal is ever written

The session itself stays on the device. What goes on chain is a cryptographic fingerprint of it, plus a window of time and a set of signals. Anyone can later prove that a given record matches the fingerprint; nobody can read the record from the chain.

Each record is canonicalised with RFC 8785 before hashing, so the same data always produces the same digest whatever the language or the platform. The test vectors are published with the specification, so a third-party implementation can check itself against ours.

Six signals, four from machines and two from humans

A proof carries what backs it: a declaration, photographs, sensor measurements, numerical coherence, and where it applies a witness or a notarised counter-signature. A proof with nothing but a declaration is still a proof, and it says so. Nothing is hidden behind a badge.

Twelve writes a year, not one per event

Individual records are signed locally and queued. Once a month they are folded into a Merkle root and a single attestation is written for that person. One write per person per month: twelve a year rather than one per session, which is what makes the economics work at all.

Built on existing infrastructure

No custom program was written. The month attestations use the Solana Attestation Service, with an IronChain credential and a published schema; badges are Metaplex Core assets, non-transferable, and they outlive the application that issued them.

Where it stands

The specification and the schemas are public under Apache-2.0. The credential, the schema and the anchoring tooling are deployed and running on devnet, and the first real proofs have been signed on a phone and anchored from the command line. The protocol is not on mainnet, and the application does not yet anchor a month on its own.