The change is documented in Midnight’s endpoint notice, which says the project’s hosted Mainnet RPC and indexer endpoints have been retired and that the remaining Mainnet RPC access will shut down on November 16. The same notice directs developers to Blockfrost endpoints authenticated with a project token. Midnight’s Preview endpoints remain unchanged.
An RPC endpoint is the interface through which a wallet or application sends requests to a blockchain node. An indexer is a separate service that organizes chain data into queries an application can use. A DApp may rely on both: the RPC for submitting transactions and calling contracts, and the indexer for balances, transaction history or application state.
That distinction matters during this migration. Replacing a URL in one configuration file may not be sufficient if an application has separate settings for transaction submission, contract queries, historical data and real-time connections. A wallet integration that reaches the indexer but cannot submit through the RPC can still appear partially functional while failing at the point where a user signs or broadcasts a transaction.
Midnight’s October network update described a wider infrastructure transition. In its State of the Network report, Midnight said its hosted Mainnet and Preprod indexer and RPC services shut down on October 9. It directed developers toward Blockfrost or independently operated infrastructure, and warned that locally stored wallet data might need to be resynchronized from genesis.
The timeline leaves a practical distinction for developers. The hosted service changes reported in October affect the broader set of foundation-operated environments, while the endpoint notice gives the November 16 deadline for the Mainnet RPC address still referenced by applications. Teams should therefore check each environment and service separately rather than treating the migration as a single endpoint replacement.
Blockfrost presents its service as managed infrastructure for Midnight. In its announcement supporting Midnight, the provider describes Mainnet, Preview and Preprod RPC and indexer services, along with authentication requirements. Its model removes the need for developers to maintain their own nodes and indexing systems, but it also makes the application dependent on Blockfrost credentials, availability and API behavior.
For privacy-focused applications, the infrastructure layer remains part of the security and reliability story even when the privacy mechanism is enforced by zero-knowledge proofs. A proof can allow a contract to verify a statement without exposing the private inputs used to construct it. The DApp still needs a working path to obtain chain state, submit the proof-bearing transaction and confirm the resulting state transition. If an RPC or indexer configuration fails, the proof system does not repair the application’s connectivity.
Hamza Tariq, writing in an analysis of the migration, says developers must review endpoint configuration, authentication, WebSocket connections and environment-specific deployments. Tariq’s analysis also warns that waiting for the legacy RPC to fail can disrupt wallet connections, contract calls and transaction flows.
That warning is an opinion from the analysis, not an incident report. No opposing view was identified in the supplied sources. The documented facts are the endpoint retirement, the November 16 Mainnet RPC deadline, the unchanged Preview endpoints and Midnight’s direction to Blockfrost or independent infrastructure.
The operational tradeoff is straightforward. Moving to a managed provider can reduce the burden of running nodes, maintaining indexes and handling service upgrades. It can also add a provider dependency and another set of credentials and failure modes. Running infrastructure independently avoids reliance on a single hosted provider, but transfers responsibility for synchronization, indexing, availability and recovery to the DApp team.
Developers should inventory every reference to the retired Mainnet endpoint, obtain and securely store the required Blockfrost project token, test RPC and indexer calls independently, and verify wallet resynchronization where local state is used. They should also test Preview and Preprod configurations separately. On November 16, an application that still assumes the old Mainnet route will not have a graceful fallback merely because its contracts and proofs remain valid.
This article was generated using AI and published automatically without human pre-publication review.
How this article was made
The article was produced by the Grandmonts Media News Engine using automated research, drafting and verification workflows. No human editor reviewed the article before publication. Grandmonts Media remains responsible for the published content. Errors can be reported at office@grandmonts.cz.