[SEV3] F3 Instance: 465951 and then 466454 not reaching a decision

[rjan90]

Purpose

This issue will serve to communicate status, investigation steps, and fixes for this F3 not-making-progress event.

Status at 2026-03-10T05:46:04Z

• Overall chain is advancing as expected. All metrics, including block production and chain quality, indicate healthy chain progression.
• F3 is not finalizing. We advanced past the stall at instance 465951 due to lack of participation. We're now halted on instance 466454
• This is slightly different than before, as the Commit3 participation is only 63%

• We have 3 participants fewer on Commit 3 than on Commit 2:
  • f01083768
  • f01084949
  • f01084968
• We are not in exponential backoff, because there is no participation to finish Commit phase. If they come back, things should resume, but we will be back to square one. Miner shuts down again, and we lose F3.

Next steps

• Understand the situation with the minerIds that have dropped out (i.e., confirm if they are terminating/faulting sectors and not bringing power back over days vs they are keep sectors/nodes/block mining running w/o participating in f3)

[BigLep]

Instance 465951 notes

There was a bit of power loss, and we were already right at the edge. You can see by looking right at the start of the event, before it we were are 68% now we are at 66.8%

We recovered from instance 465951 and progressed for about a day. Now it is stuck at instance 466454

Future correspondence in this issue will be about 466454

[BigLep]

I updated the the issue description with the latest about how we're not finalizing as of instance 466454.

[dennis-tra]

Hey folks,

We @probelab have just launched an F3 Instance explorer (beta/not indexed). It's currently in a very early stage but I thought of sharing it here anyways because it may help to debug the issue.

The explorer view for instance 466454 can be found here:

https://probelab.io/filecoin/f3/explorer?instance=466454

Feedback welcome 👍

[beck-8]

I interviewed a few SPs who turned this feature off, not those three. I have not been able to contact those three. They said they turned off the feature because they were afraid of traffic surges.