For developers, this is more than an endpoint change. Preprod is where teams test contracts, run continuous integration, stage wallets and validate releases before sending software to Mainnet. A configuration that works in production but still points to a retired Midnight URL can now break a test pipeline or leave a staging environment without access.
Midnight’s network release notes say that Blockfrost is now the public provider for the network’s environments. The same notice requires developers to use separate Blockfrost project tokens for Preprod and Mainnet. That separation is operationally important. A token is not a universal key for every Midnight environment. It identifies the network a project is allowed to access.
The practical migration is therefore not simply a matter of replacing one hostname with another. Teams need to identify which applications use RPC, which depend on indexer data, and which environment each application is meant to reach. That includes local development files, deployment manifests, CI secrets, wallet configuration and scripts used during release checks.
Blockfrost’s API documentation explains that Midnight has network-specific RPC and GraphQL endpoints. It also states that each network requires its own project_id token. In a typical setup, Preprod services should receive the Preprod project token, while Mainnet services should receive the Mainnet token. Mixing the two is not a harmless mistake. It can make a valid credential appear invalid to the service receiving it.
Midnight’s wallet documentation shows the failure mode directly. The wallet funding guide says that Preprod workflows use a Blockfrost project token through the BLOCKFROST_PROJECT_ID environment variable. It also documents a 403 response when the token belongs to the wrong network.
That detail turns the migration into a reliability test. A missing token may be easy to spot, but an incorrectly scoped token can be more confusing. The application may be configured with a real credential, yet still fail because the credential does not match the endpoint. Developers should treat a 403 response as a possible environment mismatch, not only as evidence that a token was revoked or copied incorrectly.
The first task for teams is an inventory. Search repositories, infrastructure files, CI variables and operational documentation for Midnight-hosted URLs and old authentication assumptions. Then define Preprod and Mainnet as separate environments, with separate secrets and explicit endpoint values. A deployment should make its target visible rather than relying on whichever token happens to be present in a developer’s shell.
The second task is a repeatable test. A pipeline should verify that it can authenticate to the intended network, query the required RPC or indexer service and complete a basic wallet or transaction workflow. That check belongs before release validation, not after a developer discovers that staging has been disconnected.
The migration also raises a broader question for a privacy-focused network. Moving public access to one primary provider can simplify onboarding and give developers a consistent interface. It can also concentrate an important dependency. If Blockfrost access is interrupted, rate-limited or misconfigured, many applications could encounter the same failure point.
That does not make the migration unsound. It does mean reliability now depends on how well teams document provider assumptions and maintain fallback procedures. For Midnight builders, the immediate standard is straightforward: know which network each service targets, store the matching token, test the configuration automatically and keep the difference between Preprod and Mainnet explicit. A testnet migration is successful only when the next release can still be tested.
Noah Brown is not a person. No notebook, no deadlines, no face behind the name — just a byline this newsroom publishes under. Here is the production line underneath it, because a name beside a portrait reads like a journalist, and this one is not one.
The models. Writing: gpt-5.6-luna and gpt-5.6-terra. Out on the live web: gpt-5.6-terra and gpt-5.6-luna. Pictures: gpt-image-1 and flux. Swap one in the newsroom and this line swaps with it — it is read off the machines, not typed here.
How a story is made
- Research. The searching model reads around the story, pointed at primary sources — the filing, the post, the repository — rather than at somebody else's write-up of them.
- Writing. The writing model drafts it against what was found, at Noah Brown's usual length and in Noah Brown's usual register.
- The loop. A reviewer reads the draft and sends it back with notes. Then reads it again. A piece can go round several times before it leaves the building.
- Enrichment. A quotation has to appear word for word on the page it is taken from. A chart may only use figures that appear in the source it cites. Whatever fails is dropped, and the reason is kept.
- Fact check. A last pass hunts for claims the article makes and its sources do not.
- A human stop. Sensitive subjects are held for a person to read before publication, and a person can kill any of it at any point.
If that sounds less like a newsroom and more like a factory: quite. It is called Press Factory.
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.