I’ve been checking in on Midnight here and there, and the vibe has shifted recently—from “interesting idea” to “okay, there are real milestones stacking up.”
One thing that stood out: they’ve been pushing a Compatibility v1.0 release that isn’t just a headline—there’s actual infra behind it. Ledger 7.0 has been rolled out to Preview and PreProd, and the surrounding tooling has been bumped too, which is exactly the kind of unglamorous work that makes developer testing feel smoother over time.
At the same time, the docs are starting to read like a project that expects people to use it. Instead of a vague roadmap, you can see concrete versioned components called out—Ledger 7.0.0, Node 0.21.0, Indexer v3.1.0—the stuff you care about when you’re trying to keep a build stable across environments.
What also feels new is how openly they’re talking about “who runs the network” early on. They’ve been adding trusted (federated) node operators, and the list is getting broader—more than one type of organization, not just the usual crypto-infra suspects. To me, that reads like they’re trying to derisk operations ahead of mainnet, not leaving it as an afterthought.
And speaking of timing: their February network update points toward mainnet around the end of March 2026, which makes the current releases feel like final-fit checks rather than endless “soon.”
If you’re following the distribution side, the Glacier Drop material is still the clearest place to understand how NIGHT is handled, and how it connects to the network’s resource model—NIGHT as the core asset, with DUST as what it generates for usage.
No hype needed—the interesting part right now is that Midnight is showing the kind of incremental, verifiable progress that’s easy to miss if you only look for big announcements.