\n
![](\"https:\/\/media.crypto.news\/2025\/02\/crypto-news-Mainnet-option08.webp\")
<\/p>\n
\n<\/p>\n
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.<\/p>\n
\n Summary<\/span>\n <\/p>\n <\/p>\n Input Output Group said Midnight mainnet had passed one million transactions in an Oct. 27 X post quoting the explorer\u2019s announcement. \u201cA milestone for Midnight and the builders putting privacy to work,\u201d the organization wrote.<\/p>\n Midnight Explorer\u2019s 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.<\/p>\n 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.<\/p>\n <\/p>\n Midnight\u2019s Sep. 28 network update announced<\/a> that permissionless smart contract deployment was live. Developers could deploy directly to mainnet without a mandatory security review on Preprod, the project\u2019s preproduction environment.<\/p>\n 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.<\/p>\n As crypto.news previously reported on Oct. 5, Midnight had opened contract deployment<\/a> following that initial controlled phase. The network continued recommending that developers check application logic on Preprod before moving software into production.<\/p>\n 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.<\/p>\n The same release supported sponsored DUST fees. A Gero user with several Midnight wallets could use one wallet generating DUST to sponsor another wallet\u2019s transaction costs.<\/p>\n 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.<\/p>\n The network\u2019s NIGHT and DUST model<\/a> was detailed in May 26 coverage. Holding registered NIGHT generates DUST, while transactions consume the resource without spending the underlying NIGHT holdings.<\/p>\n 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\u2019 transaction costs.<\/p>\n 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.<\/p>\n Midnight\u2019s launch materials describe a combination of public and private data, with proofs generated on the user\u2019s device. Developers can program disclosure conditions into applications and give authorized parties access to specific records.<\/p>\n The March announcement<\/a> 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.<\/p>\n\n\n
Midnight opened mainnet contract deployment in September<\/h2>\n
NIGHT generates the resource used for Midnight transactions<\/h2>\n
Midnight has announced banking and analytics integrations<\/h2>\n