Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Improve Remasc storage before 0.5.0 activation #793
This PR is interesting in many ways. I will try to explain the basics here, but I think it deserves a blog post.
When we launched our mainnet we overlooked a feature that made the
We were able to claim back some resources through a process we call
Basically we won't validate state roots before 0.5.0. This is in a sense similar to what fast-sync would do: you ignore some part of the history and continue from then on.
Apply RSKIP85 storage changes from the beginning
This is the crux of this change. We want that nodes never store this information from the beginning, which means we won't ever face the current storage problems. This means we can also get rid of the
State roots won't be validated until
I think we could, but then we wouldn't be able to simplify our codebase as this PR does. In fact, supporting more options makes it more complex. I think that archive versions (such as
3 times, most recently
Mar 28, 2019
SonarQube analysis reported 17 issues
Top 10 issues