Background
At least as of 2025-11-25, one SP has more than 50% of the power.
If that SP is temporarily down, the time to get messages on the chain takes longer. (This happened on 2025-10-28.)
We want to have enough power here that it’s non-trivial for non-implementation teams to fork the calibration network.
Done Criteria
3 "just right" sized miner from 3 different organizations so there is enough of a moat while having some resiliency to one SP being down.
Specifically, this translates to:
As a bonus, since this is about calibnet stability, we'd like to have Probelab add monitoring for calibnet to https://probelab.io/filecoin
Why Important
This is coming at a time where there is a lot of development and testing on calibration with Filecoin Onchain Cloud.
Notes
- This was discussed at FDS-7 (session notes)
- Slack thread in #fil-net-calib-discuss
Background
At least as of 2025-11-25, one SP has more than 50% of the power.
If that SP is temporarily down, the time to get messages on the chain takes longer. (This happened on 2025-10-28.)
We want to have enough power here that it’s non-trivial for non-implementation teams to fork the calibration network.
Done Criteria
3 "just right" sized miner from 3 different organizations so there is enough of a moat while having some resiliency to one SP being down.
Specifically, this translates to:
t04040at ~250 TiB of QAPt0143103to 250 TiB of QAPAs a bonus, since this is about calibnet stability, we'd like to have Probelab add monitoring for calibnet to https://probelab.io/filecoin
Why Important
This is coming at a time where there is a lot of development and testing on calibration with Filecoin Onchain Cloud.
Notes