Is Your Midnight App Ready for the Blockfrost Switch?
Developers using retired Midnight endpoints need to review their RPC, indexer and authentication settings for Mainnet and Preprod.
By SongMarketCap
Updated:
Midnight developers should check how their applications connect to the network after the retirement of Midnight-hosted RPC and indexer endpoints.
Blockfrost is now the primary public provider of those services for Mainnet and Preprod. Applications that still rely on retired addresses need to move to supported infrastructure to maintain access to network data and transaction services.
The change affects the connection between an application and Midnight. It does not introduce a new NIGHT token or require holders to move their assets.
What Happened to the Old Endpoints?
Midnight’s documentation lists October 9, 2026, at 22:00 UTC as the retirement date for its hosted Mainnet and Preprod RPC and indexer endpoints.
The documentation adds that, since October 13, both retired indexer hostnames have returned HTTP 410 with an ENDPOINT_DECOMMISSIONED error.
For the old Mainnet RPC, Midnight separately lists November 16 as the shutdown date. It also warns that the retired Preprod RPC may still respond but can stop at any time.
A retirement date and the moment an endpoint stops responding are not necessarily the same. The exact time at which the old Mainnet RPC stopped responding has not been independently confirmed. Midnight directs developers to use supported endpoints instead of relying on the retired addresses.
Connecting to Mainnet Through Blockfrost
Midnight applications use an RPC connection to communicate with a node and an indexer to query organized blockchain data. Blockfrost provides both services, including WebSocket connections for applications that subscribe to network events.
For Mainnet, the documented addresses are:
Node RPC: https://rpc.midnight-mainnet.blockfrost.io
Indexer: https://midnight-mainnet.blockfrost.io/api/v0
Indexer WebSocket: wss://midnight-mainnet.blockfrost.io/api/v0/ws
Developers need to create a Blockfrost project for the appropriate environment and authenticate requests using its project_id. Mainnet and Preprod use separate project tokens, and a token created for one environment does not work for the other.
The Preview endpoints remain unchanged, according to Midnight’s documentation. Teams should therefore check each environment individually rather than apply the same configuration across every network.
Blockfrost is the primary public provider named in the documentation, but Midnight has also identified running an independent indexer as an option for projects that want to maintain their own infrastructure.
Blockfrost previously listed a free tier with 50,000 requests per day. Developers should verify current plan limits, pricing and service terms against their expected usage before deploying.
[NEWSBREAK]
What Developers and NIGHT Holders Need to Do
Application teams should locate references to retired endpoints, update the relevant settings and test RPC requests, indexer queries and WebSocket subscriptions where used. They should also confirm that each environment is using its matching project token.
The endpoint transition is separate from the Ledger 9 upgrade. Midnight Mainnet moved to Ledger 9 on November 6, and the documented Mainnet configuration lists Wallet SDK 2.0.0 and Midnight.js 5.0.0. Teams operating their own components should check the compatibility matrix for their installation.
For NIGHT holders, endpoint configuration is generally handled by the application provider. There is no general requirement to move NIGHT or enter a recovery phrase because of this change.
If an application experiences connection problems, that does not automatically mean the Midnight network has stopped or that assets are lost. Users should check the application’s official updates and avoid sharing private keys or recovery phrases with anyone offering to “migrate” their wallet.