From bed374cdd49b26ea363e3575d0babf3237443575 Mon Sep 17 00:00:00 2001 From: Marcin Pawlowski Date: Wed, 5 Aug 2026 17:28:22 +0200 Subject: [PATCH] Pin the audited spec revision without dating it The audit note said the released logos-lips copy is still 1.1.0 and a reader checking it will not find uncle references. That is news, not report text: it goes stale the moment the RFC lands, and reports/tsi is meant to read as a standalone timeless document. Keep the provenance pin, drop the rest. Co-Authored-By: Claude Opus 5 (1M context) --- reports/tsi/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reports/tsi/README.md b/reports/tsi/README.md index 388a17f..efe4e44 100644 --- a/reports/tsi/README.md +++ b/reports/tsi/README.md @@ -860,7 +860,7 @@ The whole recipe coheres: accurate to the true stake (the ~1 % rounding removed) ### 8.5 Recommendation vs the current spec -The deltas this report recommends, in one place. This is a parameter-selection report meant to inform the spec, and it answers an open task the spec states: `analysis-total-stake-inference.md` records that its analysis "covers the total stake inference design **without** uncle references … the results below apply to the design without uncle references", and that "re-analyzing the algorithm with the block count that includes referenced uncles is an open task." That re-analysis is what this report is. Everything below is measured against the spec at revision **1.2.1** (`cryptarchia-v1-protocol.md`); the uncle-reference rules it audits live on the in-flight uncle-references RFC rather than in the released `logos-lips` copy, which is still at 1.1.0 and has no uncle references at all — so a reader comparing against a released spec will not find them. +The deltas this report recommends, in one place. This is a parameter-selection report meant to inform the spec, and it answers an open task the spec states: `analysis-total-stake-inference.md` records that its analysis "covers the total stake inference design **without** uncle references … the results below apply to the design without uncle references", and that "re-analyzing the algorithm with the block count that includes referenced uncles is an open task." That re-analysis is what this report is. Everything below is measured against `cryptarchia-v1-protocol.md` at revision **1.2.1**, the revision that introduces uncle references. | parameter | current spec / default | recommended | why | |---|---|---|---|