For the complete documentation index, see llms.txt

Midnight Q2 2026 beta delivery document

Draft

This section is a draft shared for partner review. Content is subject to change and is not part of the published documentation set.

What is in this document

• List of Q2 deliverables and their delivery status.
• The compatibility matrix needed to exercise these features on Stagenet.
• Link to the release artifact checksum document.
• Links to the low-level protocol documentation.
• How to access Stagenet, including RPC and faucet URLs.

Q2 SOW deliverables

ID	Deliverable	Components	Status
SOW-01	Native cryptographic primitives for Prime stablecoin integration (USDCx)	Language, Smart Compliance	Delivered
SOW-02	ECDSA signature support (custodian integrations)	Ledger, Crypto	Delivered
SOW-03	Contract-to-contract calls, phase 1 (unshielded data only)	Midnight.js, Compact	Delivered
SOW-04	ZKIR v3	Crypto, Language, Ledger	Delivered
SOW-05	cNIGHT to mNIGHT protocol token bridge	Protocol, Ledger, Cardano integration	Delivered
SOW-06	Native Keccak hashing	Crypto, Language	Delivered
SOW-07	Native secp256k1	Crypto, Language	Delivered
SOW-08	Event emission support for Compact smart contracts, phase 1 (unshielded only)	Ledger, Language	Delivered
SOW-09	Low-level protocol documentation	Ledger	Delivered

Component versions

Stagenet testing (Ledger RC3 compatible stack)

Component	Version
Ledger	9.1.0.0-rc.3
Node	2.0.0-rc.4
Indexer	4.4.0-pre-alpha.16
Proof server	9.0.0-rc.5_experimental
Compact compiler	0.33.0-rc.2
Compact runtime	0.18.0-rc.1
Compact.js	2.5.5-rc.6
Midnight.js	5.0.0-beta.4
Wallet SDK	2.0.0-beta.2

note

ZKIR v3 support requires the experimental build of the proof server. --feature-zkir-v3 is a Compact compiler flag; contracts compiled with it must run against that experimental proof-server build.

How to access Stagenet

• Access model: publicly accessible over RPC (TLS, under stagenet.shielded.tools), like Preview and Preprod. A brand-new chain with its own genesis, connected to Cardano through a partner-chain bridge.

• Wallet and setup: use the wallet SDK version above; point tools and wallets at the RPC endpoint below. Endpoints and partner configuration are preserved across resets, so connection settings do not change. This reset regenerated the chain genesis, so Stagenet is a new chain and on-chain state is wiped: resync wallets from scratch, re-request faucet funds, and redeploy any contracts.

• View the chain in a browser: open the Polkadot/Substrate apps explorer at polkadot.js.org/apps → Stagenet. No install is needed; if it warns about an unknown chain, continue.

• Faucet: get a Stagenet address, open the faucet URL below, paste the address, and request tokens. A small daily rate limit applies per requester.

• Quick health check:

  curl -s https://rpc.stagenet.shielded.tools \
    -H 'Content-Type: application/json' \
    -d '{"jsonrpc":"2.0","id":1,"method":"system_health","params":[]}'

  A healthy response has isSyncing: false and peers greater than 0.

Purpose	URL
Node RPC	wss://rpc.stagenet.shielded.tools
Indexer (GraphQL)	https://indexer.stagenet.shielded.tools/api/v4/graphql
Faucet	https://faucet.stagenet.shielded.tools
Browser explorer	polkadot.js.org/apps → Stagenet

Policy IDs on Stagenet

Stagenet has the same policy ID as Preview for cNIGHT:

0xd2dbff622e509dda256fedbd31ef6e9fd98ed49ad91d5c0e07f68af1

Check this through chain state on the Polkadot apps explorer, or in the source code.

Stagenet updates

Stagenet continues to get updated as STL tests further and finds and fixes issues. Expect further RC versions deployed to this environment over the coming days. STL keeps MNF up to date on what is changing so that all interested parties can continue testing these delivered features on Stagenet.

Artifacts

Download links and SHA-256 checksums for every component above are provided in the companion manifest: artifact checksums. It covers the npm packages (including Midnight.js 5.0.0-beta.4), the node release assets, the Compact compiler, and the proof-server and indexer image digests.

Per the statement of work, the manifest carries a SHA-256 checksum per artifact. Containerized components with no tarball (indexer, proof server) are verified by their SHA-256 registry image digest, anonymously verifiable on the registry.

Low-level protocol documentation (SOW-09)

Low-level protocol specifications in the midnight-ledger repository:

• Impact opcodes
• Transaction format
• Transaction types