What Happened in the Last Month and Why Developers Should Pay Attention to Midnight Network
--
There is a particular kind of momentum that happens right before a network goes live. The conversations shift. The builder activity accelerates. The infrastructure decisions that seemed theoretical start having real deadlines attached to them. That is exactly where Midnight is right now, and if you have been building on the network or just watching from the outside, the last few weeks have been genuinely significant.
Here is what actually happened, with context for why each of it matters.
Mainnet is coming in late March 2026. This is now official.
At Consensus Hong Kong, the main stage announcement confirmed that the Midnight mainnet is coming at the end of March 2026. This is the primary milestone of the Kūkolu phase of the roadmap, a period defined by infrastructure strengthening and the shift toward live production.
This is not a soft target or a “we are working toward” kind of statement. It is a confirmed timeline, which means developers currently building on the Preview environment now have a concrete deadline to work with. If your DApp is still in the testnet stage, this is the window to migrate.
Testnet-02 is gone. The Preview Network is where you build now.
One of the most practically important transitions happened quietly but matters a lot for anyone with code deployed. Testnet-02 validators were allowed to continue running nodes until February 28, 2026, with the Preview environment now temporarily maintained by core engineering as Midnight moves toward the Kūkolu federated mainnet phase.
The Midnight Preview Network went live on Midnight Explorer at 16:00 UTC on January 7, 2026, with near-zero downtime.
What this means in practice: the Preview environment is now the active development chain. Any smart contract work you are doing needs to target this environment. If you have contracts sitting on testnet-02, they are not automatically migrated. You need to redeploy against the latest Compact compiler on Preview. The Discord #dev-chat channel is the fastest place to get help if you run into issues during the migration.
The Midnight MCP Server is a genuinely useful developer tool
This one is easy to underestimate if you are not regularly using AI coding assistants, but it solves a real problem.
When developers ask AI assistants to write Compact contracts, the AI hallucinates. It invents syntax that does not exist, references functions that were never defined, and produces code that fails at compile time. Compact uses ledger for state, not state. There is no Int type. It uses Uint<32>, Field, and other specific types. Void does not exist. State mutations require witness functions, not direct assignment.
The Midnight MCP server fixes this by connecting your AI assistant directly to the actual Compact compiler and ecosystem documentation. It requires no API keys and installs in under 60 seconds. When you ask Claude to write a Compact contract, it queries the MCP server for the correct syntax, generates the code, validates it against the real compiler, and only shows you working code. This compile-validate-fix loop happens automatically.
The server currently indexes every non-archived repository in the Midnight ecosystem, including all 88 repositories from midnightntwrk and 14 community and partner repositories. The search is semantic, not keyword-based.
To add it to Claude Desktop, the config is:
{
"mcpServers": {
"midnight": {
"command": "npx",
"args": ["-y", "midnight-mcp@latest"]
}
}
}The same config works for Cursor and VS Code Copilot with minor path differences. For any developer actively writing Compact code, this is worth installing today.
The federated node partners are serious infrastructure names
The transition to mainnet means Midnight will expand to encompass distinct federated node operators. Four node partners were announced, including global technology leaders like Google Cloud, alongside Blockdaemon, which brings institutional-grade infrastructure expertise. They are joined by AlphaTON Capital, focusing on confidential AI for the Telegram ecosystem, and Shielded Technologies, the primary engineering team behind the protocol.
The latest partners to join the federated model include Pairpoint by Vodafone and eToro, which brings a high standard of regulated fintech compliance.
What is interesting about this lineup is the deliberate mix of categories. You have cloud infrastructure (Google Cloud), institutional node operation (Blockdaemon), regulated fintech (eToro), telecoms (Vodafone’s Pairpoint), and AI-focused infrastructure (AlphaTON). This is not a validator set assembled for optics. Each partner represents a different category of real-world use case that Midnight is trying to enable from day one.
Google Cloud will also provide threat monitoring through its Mandiant division and will leverage Confidential Computing to protect private data, including removing the operator of the environment from the trust boundary. That last detail matters technically: it means the cloud provider itself cannot access the private computation. That is a meaningful architectural constraint for anyone building regulated applications.
Midnight City went live as a network stress test
Midnight City is a simulation that uses autonomous AI agents to create a persistent, interactive economy reflecting real-world usage patterns. It demonstrates that the network can scale and maintain privacy without sacrificing the functionality required for complex social and financial interactions. Public access to the simulation began February 26, 2026 at midnight.city.
From a developer perspective, this is significant for a different reason than it might appear. AI agent economies are among the most demanding transaction workloads you can put on a privacy-preserving network. Each agent interaction requires ZK proof generation. Running this as a live demonstration before mainnet is essentially a public stress test. The fact that it went live is evidence the team has confidence in the network’s performance under load.
Aliit Fellowship Cohort 2 is now accepting applications
The Aliit Fellowship, the technical contributor program for the Midnight network, is now accepting applications for Cohort 2. Cohort 1 is active and the program has evolved.
The inaugural cohort consists of 17 fellows from 11 countries, including open-source maintainers, ZK researchers, and educators who have already demonstrated a commitment to the network.
If you have been building in the ecosystem, completing quests, contributing to docs, or shipping example applications, this is the program that recognizes that work formally. The fellowship is also where pattern creation happens, meaning the reference architectures and open-source templates that new developers will build on. That is meaningful leverage if you care about shaping how people learn to build on Midnight.
The Developer Academy has a new practical module incoming
A new practical module is arriving for the Midnight Developer Academy. While the initial courses established the core concepts of zero-knowledge proofs, this new module focuses on hands-on application development, guiding builders through writing Compact smart contracts and assembling a functional DApp.
If you have not completed the foundational Academy modules yet, now is the right time. The practical module building on top of them will land before mainnet, which means there is a clean learning path from ZK fundamentals to a deployed DApp in time for the live network.
The bigger picture
The move from testnet to mainnet is often treated as a single event. In practice it is a shift in the entire character of an ecosystem. The infrastructure decisions made in this window, which partners operate nodes, which developer tools get standardized, which example applications ship first, become the foundation that future builders build on top of.
The unique NIGHT holder count grew 300% in two months, surpassing 57,000 holders as of mid-March 2026. That is a measure of how fast the community is growing ahead of mainnet.
If you are a developer who has been sitting on the sidelines waiting for Midnight to feel real, this is the month where that changes. The tooling is better, the network environment is stable, the federated infrastructure partners are confirmed, and there is a hard launch date at the end of the month.
The question is not whether Midnight is coming. It is whether you are building on it when it arrives.
Follow @MidnightNtwrk on X and Midnight on LinkedIn for ecosystem updates. If you are building on Midnight and want to connect with other developers, the Midnight Discord server is the most active space for technical discussion.
