| Report Date | 2025/09/05 |
| Submitted by | Michał Kucharczyk |
@michal:parity.io2024/06/022025/06/13Substrate node ,Transaction Pool, ChainSpec/GenesisConfigThe fork-aware transaction pool became the default starting with the 2506-01 release. The new transaction pool is now in maintenance mode, and no active development is planned for it.
Over the last three months, I made a few small improvements and bug fixes in the txpool. These include adjusted metrics buckets for the reliability dashboard, a fix for instant-seal nodes, and relaxed re-validation for implicitly dependent transactions, which should make it easier to transact from newly funded accounts. I also started some work on throughput testing on the versi network, which was not concluded yet.
My main focus during reporting period was improving the PoV storage size reclaim mechanism. The current issue is that storage root calculation, done in the final step of block building, may include nodes that were not counted during extrinsic execution. This can cause the storage size limit to be exceeded. I evaluated and optimized the performance of several approaches and, based on brainstorming sessions with teammates, was able to find an acceptable solution. The details are described in this write-up, this undertaking is still proof of concept stage.
As part of this work, I also explored the details of how the Substrate state trie is implemented.
| Ranks | Activity thresholds | Agreement thresholds | Member's voting activities | Comments |
|---|---|---|---|---|
| I | 90% | N/A | None. | |
| II | 80% | N/A | ||
| III | 70% | 100% | ||
| IV | 60% | 90% | ||
| V | 50% | 80% | ||
| VI | 40% | 70% |
Question(s):
Concern(s):
Comment(s):
No referendum was created