Crescendo Hardfork discussion thread

Consensus
1

This is a discussion thread for KIP-14 — The 10-BPS Crescendo Hardfork: kips/kip-0014.md at master · kaspanet/kips · GitHub

2 Likes
2

RE

    • The pruning depth formula provides a lower bound, yet the actual pruning period can be set longer. Plugging in the scaled parameters, the lower bound is calculated to be 627,258 blocks, representing approximately ~17.4238 hours. We suggest rounding this up to 30 hours for simplicity and practical application. A 30-hour period is closer to the current mainnet pruning period (~51 hours) and aligns closely with the value used and benchmarked throughout TN11 (~31 hours).

I think setting it as some (integer) multiplication of finality depth (something like 3ϕ) can simplify pruning point calculation, since the difference between pruning points is at least the finality depth.

3

36 hours will slightly increase the storage upper bound (from 190GB for transient storage to ~230GB), but it does seem reasonable.

4

Dear community - I propose to consider including KIP-15 to the Crescendo HF.

The change is tiny (literally few lines of code) but still IMHO very powerful.

1 Like
5

Any decision about KIP-15?

6

Being tested … Hope it will be ok