Benchmark PoV Size to avoid bricking the chain with custom consensus #527
Labels
A-ci
Area: Continuous Integration
A-consensus
Area: Issues and PRs related to Consensus
A-runtime
Area: Issues and PRs related to Runtimes
A-testing
Area: Testing-related Issues and PRs
C-enhancement
Category: An issue proposing an enhancement or a PR with one
P-medium
Priority: Medium
Milestone
Companion to and blocked by: paritytech/polkadot-sdk#398
Related to paritytech/substrate#387
Once we start modifying consensus inherents, it's possible to overflow the allowed 5MB PoV size with heavy on_initialize/on_finalize hooks and brick the chain.
We need to add PoV benchmarking once parity ships it to have an insight on PoV heaviness and prevent that from happening
The text was updated successfully, but these errors were encountered: