Midnight Move Mainnet RPC and Indexer go Blockfrost

Midnight don retire im public mainnet RPC and indexer endpoints on September 30 at 22:00 UTC. Na Blockfrost now dey provide the main public access to those services, and e don change how applications and wallets dey connect to the production network.

Midnight Mainnet Endpoints Don Retire

The change cover rpc.mainnet.midnight.network and indexer.mainnet.midnight.network. According to Midnight documentation, the indexer hostname stop to resolve on October 1. The former RPC endpoint still dey answer requests, but e fit stop at any time.

Midnight na data protection blockchain inside the Cardano ecosystem. Im smart contracts fit verify conditions using zero-knowledge proofs while sensitive inputs still remain private. Applications dey depend on network services to read blockchain records, follow contract activity, and submit transactions.

Node RPC dey handle communication with the network node, including transaction submission. The indexer dey organize blocks, transactions, contract state, and wallet-related events so that applications fit retrieve dem or follow dem through live subscriptions.

Blockfrost Add Authentication and Usage Limits

Blockfrost dey provide hosted blockchain APIs, wey dey give developers access to network data and transaction submission without make dem operate the underlying infrastructure by themselves. Im Midnight service dey support GraphQL queries and WebSocket subscriptions along with node RPC.

Access require Blockfrost project wey dem create specifically for Midnight Mainnet. Each request must include im project_id, either through HTTP header or URL parameter. Requests wey no get valid token go reject, and tokens wey dem issue for other networks no fit authenticate mainnet access.

Usage go count against the application own Blockfrost plan. Teams fit choose plan wey match their traffic or run independent node and indexer, wey Midnight still dey support. Paid plan no be compulsory for every application.

This API authentication different from transaction funding. Midnight transactions dey consume DUST, the resource wey registered NIGHT tokens dey generate.

The documentation still warn say tokens wey dem expose inside browser-side code fit get copied and used against project quota. E describe how to route requests through backend wey go add the token for server side when applications need keep am private.

Some Wallets Fit Need Rebuild Synchronization State

Preview and Preprod still keep their Midnight-hosted endpoints without project authentication. The local proof server, wey dey handle private inputs during proof generation, still remain outside Blockfrost service.

For existing mainnet wallets, the migration fit pass just connection settings. Midnight service desk runbook identify one compatibility issue when wallet wan resume synchronization state wey e save against the former indexer. Event and transaction identifiers fit differ between providers, wey fit make stored references no suitable for the new indexer.

Wallets wey don already connect to Blockfrost or their own indexer no go affected by the provider change. The same apply to wallets wey dey synchronize from genesis on every startup and applications wey only dey read contract state or dey submit transactions without keeping indexer-issued identifiers.

If affected wallet stall with errors wey indicate say events dey apply out of sequence, the runbook talk say make dem discard the saved synchronization state and rebuild am from genesis through the new indexer.