NIGHT’s Dual-Chain Supply Is Now an Accounting Problem, Not Just a Token Listing

NIGHT’s entry into a widely followed benchmark makes its supply mechanics an investable data problem. CoinDesk Indices announced on April 2 that NIGHT would join the CoinDesk 80 with a preliminary 1.16% weight, with implementation scheduled for April 30, 2026. That date matters. The issue is no longer a future listing narrative. It is whether the data used to describe NIGHT’s float, liquidity and market capitalization can distinguish two technical locations for one economic asset.

The protocol’s stated invariant is straightforward: 24 billion NIGHT is the maximum supply. The accounting needed to demonstrate that invariant is not. NIGHT exists on Cardano and on Midnight. A transfer between them can leave an observer looking at a Cardano asset balance, a Midnight balance and a bridge reserve at the same time. Add those figures without understanding their relationship and the result can exceed the cap, even when the protocol has created nothing.

That is the tension behind a number such as circulating supply. It is a useful market measure only if it identifies tokens available to the market without counting a locked backing balance and its live representation as two separate coins.

One asset, two ledgers

Midnight says in its FAQ that NIGHT is live on both Cardano and Midnight, and that its bridge is being deployed in stages. The same FAQ describes DUST as a non-transferable resource generated from registered NIGHT without requiring the holder to spend the underlying NIGHT.

The critical distinction is between where NIGHT is recorded and what claim it represents. Cardano can record the original native asset. Midnight can record NIGHT that is active for use in its privacy network. The bridge must ensure that a token active on one chain has an offsetting restriction on the other chain.

A simple way to model the system is to treat Cardano as the canonical issuance ledger and Midnight as a second operating ledger. If a holder moves 100 NIGHT from Cardano to Midnight, the relevant Cardano balance is locked in bridge custody. Midnight then recognizes or releases 100 NIGHT for activity there. The holder has not gained 200 NIGHT. They have changed the ledger on which their 100 NIGHT is usable.

This is why an explorer can be correct and still be misleading. The Cardano explorer can correctly show tokens sitting in a bridge-controlled address. The Midnight ledger can correctly show the corresponding active balance. A market analyst who adds both has not found extra supply. They have counted a locked asset and the claim backed by it.

The invariant is simple, the classification is not

Midnight’s tokenomics whitepaper says NIGHT has a fixed 24 billion supply and sets out its distribution, cross-chain functionality and treatment of DUST as the resource used for transaction fees. The protocol claim to test is therefore not whether every visible NIGHT balance across every system sums to 24 billion. It is whether the nonduplicated economic claims do.

For a lock-and-mint or lock-and-release bridge design, the basic reconciliation can be written as:

Cardano NIGHT total = 24 billion

Midnight active NIGHT = Cardano NIGHT held in the bridge reserve

Nonduplicated NIGHT = Cardano NIGHT outside the bridge + Midnight active NIGHT

The second line is the essential bridge check. If Midnight has 500 million active NIGHT, an auditor should expect the bridge or its designated reserve process to account for 500 million NIGHT that is unavailable for separate use on Cardano. A mismatch does not automatically prove inflation. It could reflect snapshot timing, an in-flight transaction, an administrative staging balance or a reporting delay. But it is the number that deserves explanation.

The reverse direction follows the same logic. A Midnight to Cardano transfer should remove or immobilize the Midnight-side claim before the Cardano-side token becomes spendable again. The exact technical action can differ. A system may lock and release existing balances, or burn a representation before releasing collateral. The accounting requirement does not differ: only one side may be economically live at a time.

That state machine is more useful than a single supply number because it identifies the moments when data feeds can disagree. A price service may update a reported circulating supply daily. A Cardano explorer reflects the lock transaction when it lands. Midnight may recognize the balance after proof verification and finality. During that interval, the data sources are measuring different stages of the same transfer.

Circulation is not the same as liquidity

The word “circulating” often performs too much work in token markets. It can mean distributed rather than reserved. It can mean unlocked rather than subject to a vesting rule. It can mean held outside a foundation treasury. It can also be used loosely to mean tradable.

Those are different classifications.

CoinDesk’s NIGHT market page lists a fixed total supply of 24 billion NIGHT and a circulating supply figure, while also describing the token’s cross-chain function and its DUST-generating role. A displayed circulating number should therefore be treated as a methodology result, not as a direct substitute for either the protocol cap or immediately executable exchange liquidity.

An effective supply calculation should begin by partitioning balances, rather than adding wallet totals:

The exchange row is especially important. An exchange wallet can hold a large balance on Cardano while customer trading occurs through internal database entries. That wallet balance is an asset held in custody. The customers’ account balances are liabilities of the exchange. Adding both doubles the same claim before the analyst has even reached the cross-chain bridge.

The same principle applies to staking or delegation. If NIGHT remains transferable while it is delegated or registered to generate DUST, it is still NIGHT held by the owner. The registration may affect utility, governance or access to capacity, but it does not create another NIGHT balance. If a venue presents “staked NIGHT” and “wallet NIGHT” as separate aggregates, the analyst must establish whether they are mutually exclusive categories or merely two descriptions of one holding.

DUST is capacity, not another monetary supply

DUST introduces a second source of confusion because it is generated by NIGHT but is not a transferable token balance in the ordinary sense. Midnight describes it as a shielded, non-transferable and decaying resource for transaction fees. In other words, a NIGHT holder can retain the underlying NIGHT while accumulating an ability to consume Midnight blockspace.

That separation is economically meaningful. NIGHT is the governance and value-bearing asset. DUST is the mechanism through which ownership or registration can translate into private transaction capacity. A rise in DUST availability may mean more capacity for applications or users. It does not mean more NIGHT has entered circulation, and it should not be folded into market capitalization.

This also separates market liquidity from spendable Midnight capacity. A holder can have significant NIGHT yet little immediately available DUST, depending on registration and timing. Conversely, an application may arrange transaction capacity for users without transferring NIGHT ownership to them. Neither condition changes the 24 billion cap.

What an auditor or index provider should test

A credible reconciliation should use synchronized block heights or timestamps for both ledgers. First, identify the canonical Cardano asset supply and the bridge-controlled balance. Second, identify Midnight active NIGHT, plus any pending bridge states that have been finalized on one ledger but not the other. Third, verify that the active Midnight amount is matched by restricted collateral or an equivalent protocol-accounted offset.

Fourth, classify holdings by economic availability: treasury, reserve, unreleased allocations, bridge collateral, customer custody and independently controlled wallets. Fifth, count each claim once. This is the point at which index calculations and market data can diverge legitimately, because they may use different definitions of eligible supply. The definitions must be disclosed.

There is one further operational risk. Midnight Foundation said in an update on the Wanchain Cardano-BNB bridge incident that NIGHT was stolen through third-party Wanchain infrastructure, while maintaining that the event did not affect Midnight’s protocol or the 24 billion total supply. No opposing assessment was supplied for this story. The distinction is important: a theft can change ownership and available market float without changing protocol issuance.

NIGHT’s supply question will become simpler only if reporting converges on a common rule: count the economic claim, not every ledger entry that refers to it. Until then, a price feed, a Cardano explorer, a Midnight balance and an index supply input can all differ without contradiction.

The conclusion would change if Midnight’s active NIGHT were shown to exceed its locked or otherwise offset backing, or if a bridge process allowed both sides of a transfer to remain independently spendable. That would be a supply integrity problem. Short of that, the harder issue is more familiar: data providers and investors must decide whether they are measuring protocol supply, circulating ownership, exchange float or usable privacy-network capacity, and stop treating those four things as interchangeable.