app.racethesky.run
A single Race the Sky time-trial run, published by the player into their own repo. The record stores the raw input log rather than a result: the game's physics are deterministic, so re-simulating the log reproduces the run exactly. Owning the record is the identity proof, and replaying it is the time proof — the claimed time in this record is advisory and is never trusted by a leaderboard.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | racethesky.app |
| Indexed |
Showing version bafyreihjx3jjg6hn7r5jh4fdri55oip2ighkbz5ynljqey3vcl6wj2g4xa. Show the latest
Record
record · key tidProperties
bestMs
integerThe client's own best-lap figure in milliseconds, for display before a run is verified. Advisory only — the authoritative time is whatever replaying `events` produces.
minimum: 0
Client-reported time the run was set.
The whole run, as the only input the game takes: when the tether was held. Comma-separated `<delta><d|u>` pairs, where delta is ticks since the previous event at a fixed 120 Hz step, `d` is press and `u` is release. Example: `43d,17u,29d`.
maxLength: 20000
laps
integerLaps the session ran. Session length is a player preference, not a fairness variable — circuits rank best single lap — but the replay must run the same number of laps to reproduce it.
minimum: 1maximum: 9
Which physics produced this log. A verifier must replay under the matching version or refuse the run — replaying under different physics yields a plausible wrong time rather than an error.
minimum: 1
style
stringOpaque encoding of the player's ship livery, so a replayed ghost looks like the ship that set the time.
maxLength: 64
track
integerDEPRECATED. The course's index in the client's built-in roster, which is a display-order detail and may change. Present only so a client and server deployed minutes apart still agree. Readers must prefer trackId and ignore this whenever trackId is present.
minimum: 0
Permanent identity of the course raced. An id is never renamed, reused, or pointed at different geometry; a retired course keeps its id (solar-loop, quasar-gp, photon-oval, aurora-run and eclipse retired in October 2026) and its runs simply stop ranking.
maxLength: 64knownValues: nebula-weave | solar-loop | quasar-gp | photon-oval | aurora-run | eclipse | baja | comet-rail | pulsar-switchback | gravity-well | umbra-crossing | odyssey
weather
stringConditions the run was set under. Non-clear conditions change the physics and are ranked separately from clear times.
knownValues: clear | rain | fog | night
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
app.racethesky.course
recordA racing course built in the Race the Sky editor, published by its designer into their own repo. The course belongs to whoever drew it: it outlives any gallery, contest, or leaderboard that happens to index it, and can be played from this record alone.
-
com.gamethesky.skytanks.run
recordOne Sky Tanks run, published by the player into their own repo. The record stores every input rather than trusting a score: the sim is deterministic, so replaying the log on the same seed reproduces the run exactly. Owning the record is the identity proof, and replaying it is the score proof; score, ticks, level and the rest are advisory and never trusted by a board.
-
com.gamethesky.skyvortex.run
recordOne Sky Vortex run, published by the player into their own repo. The record stores every input rather than trusting a score: the sim is deterministic, so replaying the log on the same seed reproduces the run exactly. Owning the record is the identity proof, and replaying it is the score proof; score, ticks, level and the rest are advisory and never trusted by a board.
-
com.gamethesky.make.run
recordOne play of a Make the Sky game, published by the player into their own repo. It stores every input rather than trusting a score: each chapter's engine is deterministic, so replaying its log on the same game reproduces the run exactly. Owning the record is the identity proof and replaying it is the score proof; score and the rest are advisory.
-
One run of The Epstein Files, published by the player into their own repo. The record stores every input rather than a score: the sim is deterministic, so re-running the input log against the same seed reproduces the run exactly. Owning the record is the identity proof, and replaying it is the score proof — score, level and the rest are advisory and never trusted by a leaderboard.