FIX-137
Reference implementationA dependency-free standard that names a moment from the observed sky — small enough to store on-chain, frozen so it never drifts.
- 0
- dependencies · no network
- 8
- bodies tracked
- 3
- millisecond pulsars
- 27 KB
- the entire implementation
- JavaScript
- Meeus / ELP-2000
- JPL Keplerian elements
- ATNF pulsar timing
- VerusID
You already ran it
The stamp at the top of the homepage was computed in your browser, for the instant you arrived, from this file. No network call, no dependency, no server. That is the entire claim: anyone, anywhere, at any later date, recomputes the identical name.
FIX-137 is a celestial fix — position and time locked from observing the sky. The 137 nods to the fine-structure constant, α ≈ 1/137.
The name and the witness
This distinction is the whole design.
The name is a pure function of one number: t, TDB seconds since J2000.0. Everything in it — the moon’s distance, illumination, lunation, node and perigee longitudes; the geocentric ecliptic position of the sun and seven planets; the rotational phase of three millisecond pulsars — derives from t alone. Hash the name and you get the stamp ID.
The witness is chain tips: Bitcoin, Verus, Ethereum, with a slot reserved for Solana. These sit deliberately outside the hash. Two honest observers at the same instant may have seen different tips, so including them would break the guarantee that one moment always produces one identifier. They ride along as provenance instead.
Getting that boundary wrong is the obvious failure mode, and it’s why the stored envelope is { id, name, witness } rather than one blob.
Why the models are frozen
A timestamp standard whose underlying ephemeris drifts is not a standard — the same instant would name itself differently depending on when you asked. So every model is versioned and frozen, never silently updated. Adding a chain means adding a fetcher and a slot; it never means reordering the existing ones.
| Layer | Model |
|---|---|
| Timescale | UTC → TAI → TT → TDB ladder |
| Moon | Meeus / truncated ELP-2000 |
| Bodies | JPL approximate Keplerian elements (Standish) |
| Pulsars | φ = φ₀ + f·Δt + ½ḟ·Δt², from ATNF |
Earth has no row — it’s the observer, so the sun takes that slot as the geocentric mirror of Earth’s heliocentric position, and it leads the sky signature.
Validated against known references: the Earth row reproduces the sun’s longitude to about 0.02 arcminutes after precession, and the moon matches Meeus’s worked example to roughly 90 km and half an arcsecond of parallax.
Why the sky
A timestamp is a claim about when, and every ordinary timestamp asks you to trust something: a server’s clock, an authority’s signature, a chain that has to still exist. The sky is the one reference nobody administers. Two parties who agree on the models and disagree about everything else still compute the same name.
That’s also why it stays small. At 27 KB with no dependencies it fits in a VerusID contentmultimap — the stamp lives on-chain beside the thing it timestamps, rather than pointing at a service that has to survive.
Where it sits in the stack
FIX-137 is substrate, next to Verus itself, and it’s the least visible piece here by design.
Junction41 settles jobs on-chain and opens a review window on delivery — receipts that need to resolve years later, long after the container is gone. A signature proves who; the chain proves that; FIX-137 provides a when that doesn’t depend on anyone’s clock being honest.
Its inclusion of a Verus tip is partly redundant when a stamp is stored inside a Verus block — but it matters the moment a stamp lives anywhere else, which is the case the standard is really for.