Filecoin NV28 Fire Horse upgrade is the primary keyword for this chain-ops update. The Lotus v1.36.0 release says it is a mandatory stable release for Filecoin network version 28.
Radar is covering it because node and storage-provider readiness is a protocol operations issue with a concrete mainnet deadline.
The decision note stays narrow: use the source-backed fact to update the chain checklist, then wait for venue, market or protocol confirmation before adding risk.
That scope guard matters because the update is useful only when it changes a concrete next step. The article avoids broad prediction language and keeps the reader focused on the venue, chain, contract, route or operating surface that can actually be checked today.
The timestamped source should remain attached to the decision log so a later reader can separate the original announcement from any follow-up market reaction, interface change or operator status update.
What Happened
The official Lotus release sets the mainnet upgrade epoch at 6052800, corresponding to 2026-05-27T14:00:00Z. It says all Lotus node and storage-provider operators on mainnet must upgrade before that epoch.
The release highlights FEVM-related FIPs and FRCs, including sector status export to FEVM, a P-256 verification precompile and EIP-7939 CLZ opcode support.
Why It Matters
Chain upgrades matter because operational readiness decides whether applications, RPC providers and storage providers experience avoidable downtime.
This is Radar-fit because the owner angle is protocol ops, not exchange trading. The useful reader is checking binaries, migration timing, Go version requirements and whether infrastructure providers are ready.
What To Watch Next
Watch Lotus operator notices, RPC provider status, storage-provider upgrade reports and post-epoch chain health after 14:00 UTC on May 27.
A clean activation keeps Filecoin's FEVM and storage workflows moving. If operators lag, app teams should monitor RPC reliability and transaction behavior until the network settles.
For validation, keep the source URL, timestamp, affected market or protocol surface, and the exact decision that changes because of the update. If that decision is unclear, the item belongs on watch rather than in execution.
Continue this cluster
Continue this cluster with RWA, robotics, tokenized asset and chain-ops updates that separate exchange activity from protocol readiness.
