What triggers a sector to start replotting

i sure would like some clarification on how old is a sector before it starts re-plotting?
as it has me worried, after you get done plotting 100%, it starts all over replotting, and want to understand what triggers it, a timestamp is my guess.
as at moment i see this in a never ending loop replotting.

1 Like

During initial plotting farmer will pick pieces of the archival history of the blockchain available at the time. The way plotting is implemented will write data sequentially as much as possible, so write amplification is very low.

As history of the blockchain is growing, we need to ensure that newly produced pieces are persisted as well. This is where replotting comes into play, ensuring both old and new pieces of the history are uniformly persisted by the network.

By the time blockchain history size doubles (some sectors expire every time segment of archival history is created), ~50% of the plot expires and needs to be re-plotted. Since over time blockchain gets bigger and bigger interval for doubling increases too and you will see replotting messages less and less frequently. It can still be quite a lot if you have a lot of space pledged.

So it is not really a function of time as such, but rather of blockchain utilization multiplied by time.


So repotting happens at about the same time for all farmers? Does that have any implications on security?

Archiving happens every time segment of recorded history fills up, but not all segments trigger replotting. Replotting happens on average for half of the sectors every time history doubles, you can find the exact details about this in the specification of the protocol: Notion – The all-in-one workspace for your notes, tasks, wikis, and databases.

Additional info on replotting can be found in the Autonomys Academy: Plotting | Autonomys Academy

1 Like