What we know we do not know
The paper no longer carries a list of open questions: every value it was waiting on is fixed, and what is left are limits rather than decisions. This page is those limits, collected because a figure that rests on one should say so.
Everything fixed at genesis is fixed permanently — the validator cannot be changed — so the settled values below are settled in the strong sense.
Three limits that no decision removes
- Provenance
- Migrated, revived and newly built hashpower are indistinguishable from this chain's own data, and no estimator recovers the split. See what the ledger can and cannot say about where it came from.
- The test is one-sided
- One outcome carries information and the other does not, so no price observed can close the question by itself. See which outcome tells you what.
- The block-producer edge
- A Cardano stake pool operator who also mines decides orphan races in the blocks it forges. Bounded rather than unknown: races exist in at most about four per cent of discoveries at the target, so the uplift is roughly that times the operator's stake share, which is a hundredth of a per cent at Cardano's saturation cap. See how races are settled during a catch-up.
And six that were open and are not any more
The half-life H is ten minutes, compiled into the validator beside the ten-minute target, so a different H would be a different chain. Mining ahead is the waiting case with the work done early, and earns nothing the schedule had not released. The hashrate estimator, its two windows and the Bitcoin source are specified down to the arithmetic, and the testable claim carries a bound fixed in advance, which is the only kind worth anything. The pool payout batch ceiling is a question for pool software rather than for the chain. The software is public as of the paper, so no future date is left to commit to. And validity-interval granularity closed earliest: Cardano's slots are one second and a script reads the interval as POSIX milliseconds, finer than the rule needs, so what the validator fixes is the maximum interval width instead. That is where it is checked.
Together with the index of objections, that is every soft spot this project knows about in one place — which is the right place to start if you are working out what is actually being claimed.