cool-developer
cool-developer
@marbar3778 It looks like we couldn't modify the key format as `write_version|node_path_in_tree`. Because when rotating the tree, the path would be changed.
> @cool-develope this is more or less solved with your removal of orphans right? yeah, I think removing orphans is helpful for their group commit logic.
for example, which interval is best for pruning. It is not only for iavl/v2, SS is also considered
Importing the snapshot is slower than directly sync the latest state, I am a little worried if it may lead to delays due to load the snapshot after binary switching....
we can't process new blocks against SC until state sync, since the tree is not constructed yet. Maybe, if the state sync is done at C+V, then we will fetch...
@tac0turtle I think we can close this, the only missing feature is #19438, this is a little tricky this time and will figure out later
> Unforturntely it don't work with current IAVL I think, the main issue is the `WorkingHash` don't modify current version, so if the next `Commit` happens before the background `SaveVersion`,...
the design is changed
Rollback feature is missed (DeleteVersionsFrom in v1). @kocubinski, I think MultiTree has the potential advantages in terms of deferred pruning and also would be easy to manage the flow, for...
how do we test v2 ?