Skip to content

Updates to the blocktime reduction ZIP#1271

Draft
ValarDragon wants to merge 8 commits into
mainfrom
dev/blocktime_reduction_updates
Draft

Updates to the blocktime reduction ZIP#1271
ValarDragon wants to merge 8 commits into
mainfrom
dev/blocktime_reduction_updates

Conversation

@ValarDragon
Copy link
Copy Markdown
Collaborator

This PR does 3 things to the blocktime reduction ZIP:

  • Update the final action limit numbers. (Orchard 306 -> 330, same for global)
  • Update timing benchmarks
  • Chunk up motivation section and move data around

Before this exits Draft, we will add a section for DAA parameter updates.

evan-forbes and others added 6 commits May 14, 2026 18:15
Replace ambiguous '4 physical-core benchmark machine' wording with
'modern AMD laptop CPU with 4 pinned threads' in both the Security
and Measured timing sections.
Today's Orchard worst case is ~436 actions / 556.53 ± 9.81 ms (was
~616 / 769.85 ± 16.18). Updates the derived ratio in the proposed
worst-case prose accordingly (a little over half -> about three quarters).
Refresh verification benchmark numbers
Specify PostNU7PoWAveragingWindow := 51 and redefine
PoWAveragingWindow as a height-dependent function (17 pre-NU7, 51
post-NU7), preserving the 1,275-second wall-clock smoothing window
across the target-spacing reduction. Add a Difficulty averaging
window rationale section covering motivation, simulator recovery,
Blossom as a real-world reference point, and devnet variance
measurements. Trim the duplicated rationale from the Effect on
difficulty adjustment section.

Also restore the dense-Orchard worst-case row to the earlier
~616-action / 769.85 ms figure pending verification of the re-run
benchmark.
The reference is today's global worst case = Sapling at 3,174.90 ms.

- New Orchard worst case: 432.11 / 3,174.90 ≈ 14%
- New Sapling worst case: 271.51 / 3,174.90 ≈ 8.6% ("less than one tenth")

This also makes the sentence internally consistent. The previous
wording compared new-Orchard to today's-Orchard (432/770 ≈ 56%,
"a little over half") but compared new-Sapling to today's-Sapling
(272/3175 ≈ 8.6%, "less than one tenth") — two different denominators.
With "14%", both halves now reference the same denominator (today's
overall worst case).
Raise PoWAveragingWindow to 51 at NU7 activation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants