Chill Validation

Results 109 comments of Chill Validation

Rebased on master. No surprises. Is there anybody I could discuss the questions above with?

Do you think this code might help other validators save some disk space? I see some panicked messages starting to come out from some blockchains and my theory is that...

Thanks for the feedback. Since there's no "large danger" to this idea, I'll make an iteration and provide it to you for comment.

@marbar3778 Do you know of an example (link is totally fine) of how to get all versions on disk? It sounds very practical. I'll look for it myself as well,...

So I have a few thoughts. The AvailableVersions() []int return potentially returns many ints. * There's always this spooky danger of loading 4 million 32/64bit ints into an array and...

> I tested this and if the application db is large this will take forever, Let's make sure we're looking at the same thing You tested my code that slowly...

I've added code that will prevent pruning from taking longer than a total configured time: https://github.com/cosmos/cosmos-sdk/pull/11064/files#diff-2bc7a86169d4c2f891d7ae74b21ca4bcc5787d10114e2eee215fe1ddba5c999eR543 I've hard coded simulated delays and indeed this accomplishes the things we both value:...

Prior to compact, the states that we delete "free up" some logical space. Can the store typically reuse those "freed areas" even if it doesn't give space back to the...

Following up to check if you agree this PR is technically acceptable to finish and submit.

What you're saying is so interesting. Some validators save a lot of disk space by only keeping the last 100 states (and disable every X states). That triggers this same...