Check back here: this article will be updated with key information throughout the upgrade.
In the upcoming weeks Midnight testnet-02 will undergo a major upgrade to improve developer experience and scalability across the network. Key improvements include the transition from Partner Chains v1.2.0 to v1.5.0, a shift from the Pluto-Eris proving system to BLS12-381, and a new ledger storage implementation. These changes will empower developers, validators, and users alike as Midnight continues to evolve.
- Please note: this upgrade will require a reset of the chain state and re-registration of validators.
1. Leap from Partner Chains v1.2.0 to Partner Chains v1.5.0
Midnight leverages the Partner Chains SDK, enabling it to operate as a partner-chain to Cardano. Specifically, Midnight testnet is paired with the Cardano Preview testnet.
As a downstream user of the Partner Chains SDK, Midnight testnet currently runs on version 1.2.0. To adopt Partner Chains Node v1.5.0, a chain reset will be required, which is expected to take place in the coming weeks.
This upgrade will bring significant enhancements, particularly for Midnight block producers, including:
- Support for Cardano’s BIP32-Ed25519 Extended Keys: Unlike v1.2.0, which supports only standard Ed25519 keys, v1.5.0 adds compatibility with BIP32-Ed25519 extended keys—a widely accepted Cardano standard. This addresses a key request from block producers, many of whom rely on extended keys via tools like CNTools.
- Elimination of Kupo: v1.5.0 removes the dependency on Kupo previously required by partner-chains-cli, simplifying the setup process.
- Removal of pc-contracts-cli: In v1.2.0, partner-chains-cli required the separate pc-contracts-cli tool, which wasn’t packaged with it. v1.5.0 eliminates this need, streamlining operations.
- Reduced Risk of Re-registration: Upgrading to v1.5.0 lowers the likelihood of needing to re-register for future upstream Partner Chains updates. However, block producers will be required to re-register to testnet-02 for this upgrade.
2. Switch from Pluto-Eris to BLS
Midnight currently uses the Pluto-Eris proving system for generating efficient zero-knowledge proofs, specifically zkSNARKs. However, the testnet upgrade includes a transition to the BLS proving system, specifically utilizing the BLS12-381 curve. This shift brings notable advantages over Pluto-Eris:
- Better Proving Efficiency: BLS12-381 delivers faster proof generation and verification, reducing computational overhead for nodes and users.
- More Scalable Proofs: The system supports higher transaction volumes and larger ledger states, aligning with Midnight’s growth trajectory.
- Interoperability: BLS is widely adopted across blockchains and ZKP ecosystems.
3. New ledger storage implementation
Midnight-node currently handles the ledger state in a suboptimal method by serializing and deserializing the ledger from a single input. The testnet upgrade will feature a new ledger storage implementation that handles the ledger state in a more manageable Merkle tree than a global ledger state. This new ledger storage brings:
- Better Node Performance and Scalability: The new ledger storage implementation allows the node to sync more smoothly as the ledger state grows.
- Lower operational costs: The new ledger storage implementation improves operational memory cost by approximately 2x (~32gb down to ~16gb).
What should I do now?
Follow Midnight channels for more announcements and guidance around the upgrade.
- For questions or support join Discord: https://discord.com/invite/midnightnetwork
- Midnight on X: https://x.com/MidnightNtwrk
- Midnight on Telegram: https://t.me/Midnight_Network_Official
Bookmark the compatibility matrix in the Midnight documentation. The compatibility matrix is kept up-to-date with every release.
TL:DR:
Midnight testnet, upgrade in the coming weeks:
- BIP32-Ed25519 Support: Adds extended key compatibility for block producers (unlike v1.2.0’s standard Ed25519).
- No More Kupo: Removes Kupo/Ogmios dependency, simplifying Validator setup.
- No pc-contracts-cli: Eliminates need for separate tool, streamlining operations.
- Fewer Re-registrations: Reduces risk of re-registering for future updates.
- Faster Proving System: Switch to BLS.
- Better Nodes: Node is 2x more efficient.