NIGHTGATE 0.42 Moves to Ledger 9 With Mainnet Submission Disabled by Default

ODATANO released NIGHTGATE 0.42.0, moving its Midnight gateway and transaction builder to Ledger 9. Self-hosted installations default to Midnight mainnet, where transaction submission is disabled by default. ODATANO reported testing fee sponsorship, sponsored contract deployments, swaps and transfers on Preview.

What Changes for NIGHTGATE Users

NIGHTGATE connects business applications to Midnight through OData V4 and can run as a plug-in for SAP Cloud Application Programming Model or as a standalone container. Version 0.42.0 removes the legacy /api/v1 routes. Applications using those routes need to switch to the gateway’s /odata/v4/midnight service paths.

ODATANO’s release notes call for redeploying and relinking NIGHTGATE contracts that use updated verification keys. Wallets also need a full sync because the new release cannot restore snapshots created with the previous wallet SDK. ODATANO recommends syncing sponsor wallets before the upgrade.

Version 0.42.1 Adds Calls to Older Contracts

The 0.42.1 patch lets developers use @odatano/nightgate-tx 0.21.1 with a Ledger 8 contract build to produce a Ledger 9 transaction containing a single call to a contract deployed before the upgrade. For those calls, the gateway’s server-side contract actions direct developers to the transaction builder.

Existing mainnet contracts carried over when Midnight upgraded to Ledger 9 on November 6. The patch lets NIGHTGATE developers call those deployments using the transaction format mainnet now accepts. Midnight reset Preview as a new chain on the same date, so contracts from the previous Preview chain need to be deployed again there.

[NEWSBREAK]

What NIGHTGATE Supports on Mainnet and Preview

NIGHTGATE 0.42 can index mainnet when configured with a node and indexer, and its transaction builder can create and prove Ledger 9 transactions. The crawler can still decode historical Ledger 8 blocks. Preprod remains on Ledger 8 and requires the earlier NIGHTGATE 0.41 release line.

Self-hosted operators can enable submission through allowMainnetSubmission. ODATANO’s production checklist describes mainnet submission as unsupported and instructs operators to leave the setting disabled. Developers can use Preview to test the full Ledger 9 workflow, including submission of sponsored deployments, swaps and transfers.