Skip to content
Bitcoin Roots

v31.1-roots.1 · Commit 3: [PATCH 03/17] feat(policy): preserve cluster accounting and repair dynamic dust

doc/feature-contracts/effective-policy.md

Before: doc/feature-contracts/effective-policy.md · After: doc/feature-contracts/effective-policy.md

File metadata
index c53e2ef750ebdd0bdb275229b1fdd3edfdc210ff..e14c0301eb735f1abf7552bd29ac8582775a1727 100644

Download original patch · Release notes

Diff rows 1–14 of 14. Line numbers refer to the original before/after files.

+ Added− RemovedUnmarked lines are context.

Scroll the code area horizontally to read long lines. Before is on the left; after is on the right. Unified view fits narrow screens more easily.

doc/feature-contracts/effective-policy.md CHANGED
@@ -96,9 +96,11 @@ The globals and option controls above are startup-only in this implementation
96
  and initialized before RPC warmup finishes. The live dust rate and top-level
97
  rolling minimum are read with existing locking; there is no policy setter RPC.
98
 
99
- Non-off `dustdynamic` currently fails startup because production scheduler wiring
100
- is missing. Reporting a live dust rate does not imply that dynamic modes operate
101
- in this revision. Dormant `getmempoolstats` is outside this contract. Mining
 
 
102
  options are reconstructed and clamped by individual block assemblers, with no
103
  single retained active instance to report here; this mempool schema deliberately
104
  does not claim to represent their limits.
 
96
  and initialized before RPC warmup finishes. The live dust rate and top-level
97
  rolling minimum are read with existing locking; there is no policy setter RPC.
98
 
99
+ The historical source's non-off `dustdynamic` failed startup because scheduler
100
+ wiring was missing. Candidate L8.2 repairs node-owned scheduling, retry/teardown
101
+ lifetime, synchronized live-rate reads, estimate fallback and bounded scaling;
102
+ see [runtime semantics](subdust.md). The effective-policy RPC schema itself
103
+ remains L12. Dormant `getmempoolstats` is outside this contract. Mining
104
  options are reconstructed and clamped by individual block assemblers, with no
105
  single retained active instance to report here; this mempool schema deliberately
106
  does not claim to represent their limits.