Finality
History starts at a pinned anchor, and money only moves on finalized state. Safety starts before signing.
Which blocks count, and from which one on?
Everyone computing the QLYP ledger must agree on three things: which chain, which runtime, and the exact block where interpretation begins. Change any of them and you get a different set of assets, so all three are pinned.
- 01 / 05
History starts at an anchor
The mainnet configuration pins block 102,161 as the anchor. It is excluded: QLYP state starts empty there. Nothing in that block or before it creates an asset.
- 02 / 05
The first block must follow it
Block 102,162 is the first one interpreted, and its parent must be the anchor’s exact hash. Pinning a hash, not a date, leaves no room to argue about where the ledger begins.
- 03 / 05
New blocks are provisional
Quantus targets a block every 12 seconds. The newest blocks can still be replaced by a reorganization, so any state computed from them is shown as provisional.
- 04 / 05
Finality trails the tip
Quantus clients finalize about 100 blocks behind the best tip, roughly 20 minutes. Qlyphs reads the node’s actual finalized head rather than counting confirmations itself.
- 05 / 05
Money moves on final state only
A protected purchase needs a finalized reservation, and witnesses attest to finalized state. If the chain’s runtime changes to one the rules were not pinned for, processing and signing stop until it is reviewed.
The mainnet pins
| Pin | Configured value |
|---|---|
| Excluded anchor block | 102,161 |
| First interpreted block | 102,162 |
| Runtime version / transaction version | 153 / 6 |
| Genesis | 0xfb5487c0…31626fba |
These are the values the wallet and indexer are built with. Check the runtime your node reports before relying on them: a runtime upgrade stops processing and signing until the pins are reviewed.
Included is not final
Quantus targets a block every 12 seconds and its clients finalize about 100 blocks behind the best tip, roughly 20 minutes. Until then, a block can be replaced. Qlyphs reads the node's own finalized head instead of counting confirmations, and your wallet shows the difference: submitted, included, then final.
Provisional state is useful to watch. Purchases and witness proofs use finalized state only.
Activation is part of the protocol
Moving the anchor changes which assets exist. Moving a new operation's activation height changes which messages mean something. Neither is ever read from an untrusted service or chosen after the fact.