Arkadiy Paronyan

Sync 2.0

4

This is a tracking for the new implementation of syncing protocol and algorithm in substrate. It mostly concerns full/fast sync, but not warp sync. ### Current implementation issues. 1. Reliance...

Allow longer state pruning history

7

Currently when state pruning is enabled `state-db` reqeuires O(n) memory w.r.t. the number of blocks pending pruning. Therefore long pruning history requires a lot of memory. It should be possible...

Remove discarded block bodies and states from the database.

3

Block header and bodies currently account for 90% of the database size on disk. By default the node keeps all headers and bodies in the database, even ones that are...

See https://github.com/paritytech/substrate/pull/10698

Node keeps loosing peers.

5

Start a new warp sync using latest polkadot+substrate master with an empty db dir in GCP. The nodes keeps loosing almost all peers every couple of minutes. ``` a@a-db:~/src/polkadot$ ./target/release/polkadot...

State-db refactoring

4

Remove "pending" state in statedb, which greatly simplifies implementation. Now in case there's a backend error the in-memory state is reverted by simply reloading from disk. Also fixes an issue...

Fixes #13179 See https://github.com/paritytech/parity-db/pull/170 polkadot companion: https://github.com/paritytech/polkadot/pull/6617 cumulus companion: https://github.com/paritytech/cumulus/pull/2132

Get rid of junk in storage proofs.

2

Currently block execution storage proofs contain nodes that are not actually necessary to validate the block. There's a common pattern in the runtime that we use to store intermediate values....