Notes
Arguments and explanations that did not fit inside a specification: the reasoning behind a choice, an objection worth answering, a walk through what something costs in practice. No cadence is promised and nothing here is written to be long.
Changes to a document are recorded separately, in the changelog, so an argument worth reading in a year does not get buried under a version bump.
Every note
| Date | Title | Summary |
|---|---|---|
| 9 November 2026 | Most of this is already law, for one trade, in twenty-seven countries | The usual objection to RVW-5 is that no government would ever agree to it. One has, since 2006, across the whole union. |
| 9 November 2026 | Expiry does more work than revocation | Revocation assumes somebody tells you. Nobody tells you. |
| 9 November 2026 | What a signed file actually costs | A walk through the work of publishing tier B, step by step, with the hard part named. |
| 9 November 2026 | A licence number is not a credential | What a register entry proves, what it does not, and why that gap decides the whole project. |
| 9 November 2026 | The register that counts is a room | Three jurisdictions on three continents landed on the same architecture, and nobody seems to have noticed. |
| 9 November 2026 | Why SHA-256 and not keccak | The identifier has to be checkable by somebody who installs nothing. |
| 9 November 2026 | A wallet per job has to stay free | Fresh addresses are normal practice. A protocol that punishes them will not be used. |
| 9 November 2026 | An API is the wrong ask | Why every conversation with a licence register stalls, and what to ask for instead. |
What goes here
A note is an argument or an explanation that did not fit inside a specification. It should still be worth reading in a year, which is the test that keeps it out of the changelog.
What does not go here: anything written to rank rather than to be read, product announcements, and opinions about companies. The protocol work is the subject.
Every note is also available as a JSON feed.