Arkadiy Paronyan
Arkadiy Paronyan
I guess this is mostly needed to pin unfinalized blocks. A lot of this logic, including maintaining pinned set and reference counting is already in `StateDb`. Would it be possible...
There a couple of additional issues with this PR: 1. The spec: > The current finalized block reported in the initialized event, and each subsequent block reported with a newBlock...
Would be good to compare memory usage for a polkadot node running with and without the delay.
Looks good module some naming and CLI options
I think `delay` should rather be a separate setting. Otherwise we'd need separate delay options for `--block-pruning` and `--state-pruning`. You should be able to have 1000 blocks of state history,...
> I don't really get what the difference to --state-pruning 32 --blocks-pruning 32 is? `--state-pruning` sets how many recent finalized states are available `--blocks-pruning` sets how many recent finalized block...
> In general I still don't think that this is a great solution. Yes it works, but it will break the moment someone plays around with the CLI args or...
> invoking host functions are viewed as non deterministic from PoV of the WebAssembly spec, but we can ensure that only deterministic functions are available to the STVF. Are there...
> I think memory is not such a big concern either IMO. WebAssembly memories can be limited in size statically (i.e. in declaration) and they are capped with the absolute...
@hzy1919 You are welcome to try. Reach me (`@arkadiy:matrix.parity.io` ) or @cheme (`@emeric:matrix.parity.io`) on element if you need any hints.