Repository navigation
Clear state simply #1266
Replies: 5 comments 1 reply
|
Would it make sense to do it on all future network upgrades, i.e., introduce this cleanup as a permanent step in the network upgrade process? |
Pausing the chain to fiddle with global state is a process that should not be taken lightly. Also, after this clear, GiB will become a mix of Sectors, PDP, and other state. It's unlikely to have the same impact (in percentage terms) again. So it'll be available to enact again cheaply, but only with careful testing first (as this round should also get). |
|
would you like to discuss this on next core devs? |
|
2 additional considerations:
|
|
A quick AI assisted measurement of state suggests we can cut state costs by half if we do this simple state clearing procedure: I have not validated the result myself so take it with some uncertainty. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I propose that old miners with zero power lose their sector state tree on the next network upgrade.
Old Miners will be those with IDs created before 6 months ago. A simple less-than check should work.
Reasoning:
All this information is at the top of the state tree and should be fast and straightforward. This reduces the state tree easily. It doesn't include complexity nor the timing risks of compaction of existing miners.
The miners remain valid for future use.
Why:
Provers are incentivized to prefer this fork as it will significantly reduce their state storage obligation by removing terminated sectors. The migration time will be consistent for everyone and is expected to be very short. Therefore no network expenditure will be necessary.
This will result in smaller snapshots. It will dispel concerns temporarily about state size.
Looking Forward:
FOC PDP has its own funded cleanup mechanism. Compacting existing miners remains viable if further reductions become necessary from that part of the tree.
All reactions