Midnight has passed one million mainnet transactions, with Input Output Group announcing the milestone after Midnight Explorer reported a total of 1,019,963 on Oct. 27.
Summary
- Midnight Explorer reported 1,019,963 cumulative transactions, with Input Output Group amplifying the milestone on Oct. 27.
- Daily transactions reached 47,714 on Oct. 26, compared with 128 recorded on Sep. 27.
- Permissionless smart contract deployment went live in September, allowing developers to deploy directly to mainnet.
- Neither milestone post disclosed active-address counts or a breakdown of the applications behind the transactions.
Input Output Group said Midnight mainnet had passed one million transactions in an Oct. 27 X post quoting the explorer’s announcement. “A milestone for Midnight and the builders putting privacy to work,” the organization wrote.
Midnight Explorer’s accompanying dashboard image showed the cumulative count above one million. Its post compared two daily readings separated by 29 days, describing activity as more than 372 times the earlier level.
Using the figures in the post, 47,714 divided by 128 equals approximately 372.8. The daily count was 47,586 transactions higher on Oct. 26 than on Sep. 27.
Midnight opened mainnet contract deployment in September
Midnight’s Sep. 28 network update announced that permissionless smart contract deployment was live. Developers could deploy directly to mainnet without a mandatory security review on Preprod, the project’s preproduction environment.
Applications gained the ability to deploy contracts on behalf of users. The update described the change as a planned step after the initial March rollout, when work concentrated on operational stability, security and developer preparation.
As crypto.news previously reported on Oct. 5, Midnight had opened contract deployment following that initial controlled phase. The network continued recommending that developers check application logic on Preprod before moving software into production.
Wallet access developed alongside contract deployment. Gero Wallet version 2.7.1, released Sep. 16, introduced shielded mainnet balances and a connector that could prove, fund, and submit transactions for users, according to the September update.
The same release supported sponsored DUST fees. A Gero user with several Midnight wallets could use one wallet generating DUST to sponsor another wallet’s transaction costs.
NIGHT generates the resource used for Midnight transactions
Midnight separates its native asset from the resource consumed when applications run. Its official token documentation identifies NIGHT as the public, unshielded native and governance token, while DUST is a shielded, nontransferable resource used for fees and smart contract execution.
The network’s NIGHT and DUST model was detailed in May 26 coverage. Holding registered NIGHT generates DUST, while transactions consume the resource without spending the underlying NIGHT holdings.
In its March launch announcement, Midnight explained that holders could designate a recipient for the DUST generated by their registered tokens. Developers could use their own holdings to cover application users’ transaction costs.
According to that announcement, a DUST address takes seven days to reach its full charge, with shorter periods needed for partial replenishment. The token documentation describes applications that sponsor fees so users can interact without separately acquiring the transaction resource.
Midnight’s launch materials describe a combination of public and private data, with proofs generated on the user’s device. Developers can program disclosure conditions into applications and give authorized parties access to specific records.
The March announcement described an initial federated operator model, with a defined group running the protocol under participation and coordination rules. Midnight listed Google Cloud, MoneyGram, Worldpay and other institutions among its infrastructure partners. Subsequent roadmap phases were intended to move the network toward decentralized operation.
Midnight has announced banking and analytics integrations
Institutional projects form another part of Midnight’s documented application plans. On Oct. 1, coverage of its Monument Bank partnership described a proposed first phase targeting £250 million in tokenized retail deposits.
The March 25 partnership announcement said each token would represent funds held at the U.K. bank on a one-to-one basis under the proposed banking program. The deposits would remain redeemable in pounds and subject to existing banking protections. The £250 million figure was a project target, with no allocation to the October transaction count disclosed in either milestone post.
The partnership announcement set out later phases involving tokenized investment products through the Monument app and lending secured against customers’ investments. Monument Technology, an affiliate of the bank, planned to make tokenized-deposit functionality available to other institutions through its banking technology platform. The announcement described those steps as parts of a phased rollout.
For network analytics, Midnight’s July 23 update described a Token Terminal partnership covering transaction counts, block times and contract deployments. A Dune integration covered public-state metrics such as NIGHT flows, validator block production and aggregate DUST generation and consumption.
The July update recorded U.S. policy engagement as well. The Midnight Foundation submitted comments on the Treasury’s joint FinCEN and OFAC proposal concerning the GENIUS Act, arguing that compliance should be assessed through operational outcomes and regulatory visibility.
In the foundation’s account, selective disclosure and zero-knowledge proofs could support sanctions screening before settlement while keeping user information private. Its response urged regulators to avoid requiring public-chain architectures as the default design for compliance programs.
