Filecoin activates Solstice reward overhaul on mainnet

Filecoin activated network version 29, called Solstice, on mainnet at epoch 6,470,279 at 12:59:30 UTC on October 19, changing how the storage network assigns quality-adjusted power and distributes newly minted block rewards. Filecoin’s status service marked the scheduled maintenance complete at 13:59 UTC and currently lists mainnet and chain height as operational.

The upgrade matters because it replaces Filecoin Plus’s administrative datacap system with an economic model intended to reward paid services. It also redirects part of issuance away from the miner that wins each block. That is a material change to network incentives, but it is not evidence that customer demand, storage revenue or token value has increased.

What changed at activation

Accepted Filecoin Improvement Proposal 0118 deprecates datacap minting, new allocations and new claims. Previously minted but unused datacap becomes inert, while existing claims remain only as historical records. The proposal says existing sectors retain their quality-adjusted power at migration, avoiding an automatic retroactive change to their standing.

New sectors now receive 10-times quality-adjusted power by default, regardless of content. Existing active sectors below that level can opt into an upgrade, subject to additional pledge requirements. The 10-times multiplier is an incentive-accounting measure; it does not mean a sector stores 10 times more physical data, performs 10 times faster or serves 10 times as much customer traffic.

Solstice also divides newly minted block rewards into three possible streams. The consensus stream pays the winning miner, the service stream credits registered Service Orchestrators according to the mechanism’s rules, and any residual goes to Filecoin’s burn actor. Gas rewards still go fully to the winning miner, and the FIP says existing penalty treatment is unchanged.

A scheduled shift, with a demand gate

At launch, the accepted specification assigns 95% of each newly minted block reward to the consensus stream and 5% to the service stream. During an initial bootstrap quarter, the service share is scheduled to reach 10% without a volume-gate test. The consensus share then follows a published decline toward a 50% floor over roughly nine quarters.

After the bootstrap period, further service-share increases are conditional. The service allocation can rise by five percentage points per quarter only when aggregated payment volume settled through Filecoin Pay reaches the applicable U.S.-dollar target. If the target is missed, the service share holds while the gap opened by the declining consensus share is burned. These percentages are protocol schedule parameters, not observations of realized customer revenue.

The model initially relies on one registered Service Orchestrator. Additional orchestrators may be admitted by Service Rewards Actor governance during the first phase; permissionless admission requires a future specification and code change. That creates a governance dependency alongside the onchain volume calculation. The FIP says discretionary changes to stream weights require an accepted proposal, approval from both governing multisignature entities and a delay before taking effect.

What the completion record proves

The public status log establishes that the planned upgrade window began at 12:59 UTC and was marked complete one hour later. The protocol’s community record lists compatible releases for Lotus, Forest, Venus, Curio and Boost. Together, those records support the narrow conclusion that Filecoin crossed the designated epoch with the Solstice rules deployed.

They do not provide an independent post-upgrade measurement of block production, provider profitability, paid-service volume, storage utilization or client reliability. “Operational” is the project status page’s current service designation, not an audit of every node or storage provider. The first meaningful tests will be whether the new reward accounting behaves as specified, whether Filecoin Pay volume clears later gates, and how providers respond as the consensus share changes.