EXP-01 / Supersaturate / Badge and board key
Tier Badge
Balance gate
Applied to two surfaces
Supersaturation is the condition that makes a track visible. The chamber does not produce the particle and does not certify it -- it holds the vapour past the point where it should have condensed, so that a passage which would otherwise leave nothing drags a line of droplets into existence behind it.
The trace on chain is the passage, and it is free to read. This page is the condition: the two surfaces that carry a record out to where the output is actually being read.
Free, and staying free
Verification is the product, and it is not for sale. Everything in this list works with no wallet, no balance, no account and no rate limit, and nothing below can change that.
- Verification itself
- Committing a trace, re-running it, opening an incident and ruling on it. The protocol charges Solana rent and fees and nothing else.
- The trace card
- Any committed inference by id: input hash, output hash, model fingerprint, seed, tier, re-run comparison and incident history.
- Tier pages
- What each tier proves, what it refuses to prove, the sampling detection table and the published cost of producing a proof.
- The public Track Board
- Provider reproducibility ranked by measured evidence, with the failure attribution behind each score.
- The indexer's read paths
- The same figures this site renders, served over HTTP without a key: /trace, /plate, /track, /incident, /ionize/verifiers, /stats.
No page in that list reads a wallet balance, and none of them can. The one component on this site that reads one lives on this route and nowhere else.
What a balance opens
A cloud chamber does not produce particles. It produces the condition under which one becomes visible: vapour held past the point where it should have condensed, so that anything crossing it drags a line of droplets into existence behind itself.
Take the condition away and the particle still crosses. Nothing is falsified and nothing is hidden. It is simply not seen, because nothing carried the passage to a place anyone was looking.
A committed trace is the passage. It is on chain, it is free to read, and it stays that way. What is on this page is the condition: the two surfaces that carry a record out to where the output is actually read.
Both are distribution. Neither is a permission to read a record, because a permission to read a record is not a thing this system has to give.
The two surfaces
The embeddable tier badge
An SVG served from this site that renders a trace's live tier wherever the output is published. The tier is drawn from the record at request time and cannot be relabelled by the embedder.
A programmatic board key
A wallet signature that lets another service pull the Track Board on a schedule instead of by hand, through /api/board.
| Surface | Threshold | Why it is priced there |
|---|---|---|
| Embeddable tier badge | 25,000 KORTX | One mark on one page, clicked through to one record. The lower of the two, because it costs this site one small render per view. |
| Programmatic board key | 250,000 KORTX | Automated pulls against the indexer, unattended and repeating. The figures are the same ones on the public board; the schedule is what is being paid for. |
Both thresholds are launch settings rather than measurements, and both are read from the environment so that moving one is a configuration change and not a release. The gate is applied against the published contract address.
Your position
Connecting reads one number: the balance of this mint in your wallet. It asks for no transaction, and nothing on the free surfaces of this site changes whether you connect or not.
Looking for wallets in this browser...
| Surface | Threshold | State |
|---|---|---|
| Embeddable tier badge | 25,000 KORTX | Closed -- Balance could not be read: No wallet is connected. |
| Programmatic board key | 250,000 KORTX | Closed -- Balance could not be read: No wallet is connected. |
Issue a badge
Paste a trace address, or any link ending in one. The mark is drawn from the record at the moment each visitor loads it, so it follows a ruling rather than freezing on the day it was pasted.
Not open on this wallet
Connect a wallet above to have a balance read. Reading the record itself stays free either way -- the trace card, the tier pages and the board are open with no wallet at all.
Sign a board key
For pulling the board on a schedule. The same figures are on kortx.fi/track and on the indexer's open /track path with no key at all; what is signed here is machine access, not access.
Wallet required
A key is a wallet signature, so one has to be connected before there is anything to sign. Reading the board needs neither.
- The key is a detached wallet signature, not a secret this site stored. There is no key list here to leak and no account to recover -- the server re-derives the signed sentence and checks it on every call.
- The balance is checked when the key is used, not when it was signed. A position sold is a key that stops working on the next request, with no revocation step in between.
- It is bearer material. Anyone holding the string can read the board as that wallet until it expires. It signs no transaction and moves no funds, because the message it covers is not a transaction.
- Signing again produces a different key and does not invalidate the previous one. Keys expire on their own; that is the only way they end.
What it answers when it refuses
| Code | HTTP | Meaning |
|---|---|---|
| key_missing | 401 | No key on the request. |
| key_malformed | 401 | The string is not a kortx_v1 key. |
| key_signature | 401 | The signature does not match the wallet it names. |
| key_expired | 401 | Past its 90 days. Sign a new one. |
| holding_below_threshold | 403 | The wallet is under the threshold right now. The body reports both figures. |
| holding_unreadable | 503 | The RPC did not answer, so the gate did not run. This is not a refusal. |
| storage_unavailable / index_unavailable | 503 | Passed through from the indexer unchanged. Not an empty board -- an unread one. |
What the badge does not say
- The badge states a tier and points at a record. It does not state that the model is good, that the answer is correct, or that the provider is honest about anything the record does not cover.
- There is no parameter that removes the tier, renames the label or picks a colour. A mark reading only "Traced by KORTX" is not served by this site at any address, because it would let the weakest evidence class borrow the credibility of the strongest.
- When the indexer cannot be read the badge renders the words "unreadable" and the response carries HTTP 503. It never falls back to a tier, and that response is never cached.
- A record under challenge, ruled a mismatch, or slashed carries that word next to its tier in alert orange. The badge follows the record; it is not a snapshot of the day it was issued.
The tier is what makes a verification claim checkable, so a mark that dropped it would not be a shorter claim -- it would be an unfalsifiable one. That is the whole reason the label is fixed at the server rather than passed in by whoever embeds it. What each tier does and does not cover is set out on the tier page.