Passively Test F3 on Mainnet nv25

[BigLep]

Done Criteria

Passive testing is performed on the network post the nv25 upgrade with updated software and a wider set of dynamically configurable parameters. Passive testing is finished when we either:

1. Identify a set of parameters that will work for the go-f3 release associated with nv25 that will enable a successful followup activation (see more specifics below) OR
2. Determine that the go-f3 code in mainnet needs further changes in order to have a manifest that will yield a "successful f3 activation" (as happened with nv24)

Why Important

1. F3 is a major shift for Filecoin from a network perspective given how much extra data is being transferred. In the past, propagation delay was on the order of seconds, but with nv24 F3 passive testing, we observed this increase to minutes in some cases. This magnitude of change requires a larger testing effort to catch the unexpected.
2. Passive testing has been a huge engineering productivity boost. It has allowed for lots of learning with minimal engineering time and no network upgrades.

User/Customer

1. f3 engineering team
2. SPs and network at large for visibility into passive testing plans/progress

Notes

1. This is the nv25 equivalent of Passively Test F3 on Mainnet nv24 #213
2. "Successful mainnet passive testing" from as engineering perspective is a consistent baseline that we can iteratively improve in future. It includes…

• Bootstrap phase
  • Complete within 2 hours
  • Average Bandwidth Up/Down less then 15MiB/s
• Steady State
  • At least 3 days of consistent progress
  • Average bandwidth Up/Down less then 3MiB/s.
  • Each instance takes less than 10 minutes (which means we can’t be more than 30-50 epochs behind)
    • Lookback is 10 epoch
    • Finalizing takes ~10 minutes (20 epochs)
    • Right before we’ve finalized (which took 10 minutes) we got another 20 epoch behind

3. When nv25 passive testing begins, updates will be posted in F3 passive testing lotus#12287 as before