Weekly Brief #14 | Visible, Learnable, Distributable — Midnight Adds Operational Depth

日本語版 →

Published: 2026-07-11 JST · Epoch: 642 · Issue 14

Midnight did not move forward this week because of one blockbuster announcement.

Instead, several operational pieces arrived together: a data partnership for observing the economy from the outside, technical education for verifying zero-knowledge proofs, the resumption of suspended NIGHT distribution operations, and a way for users to check whether their wallets may be connected to a known security incident.

This week’s thesis is “visible, learnable, distributable.”

Meanwhile, Cardano mainnet remains at Protocol Version 10. Expectations for van Rossem remain, but Koios still measured version 10 on July 11. ADA and NIGHT also declined week over week.

In other words, this was not a week when expectations pulled prices higher. It was a week when the machinery of real-world operations quietly gained depth.

INDEX

1. Executive Summary
2. Market Pulse
3. Cardano Ecosystem Watch
4. Midnight Watch
5. Risk Dimensions
6. What to Watch Next Week

Executive Summary

Three different kinds of progress became visible across Midnight this week.

The first is “visible.” Token Terminal announced a Data Partnership with Midnight, and Midnight’s official account shared it. A privacy-focused network does not need to make the growth and usage of its economy invisible. The practical question is what should remain private and what should be aggregated and disclosed. This partnership is an entry point for connecting Midnight to externally verifiable metrics while designing that boundary.

The second is “learnable.” Input Output Research began its first ZK Verification Technical Workshop. The agenda covered proof-system trade-offs, SNARK standardization including Halo2 and Plonk, ZK-Rollup security for Hydra Tail, and tooling interoperability between BN254 and BLS12-381. This moves privacy technology beyond a story about adoption and toward the people who will implement and verify it.

The third is “distributable.” Following the security incident involving SecondFi-related wallets, the Midnight Foundation resumed Glacier Drop redemptions at 17:00 UTC on July 9, or 2 a.m. JST on July 10. The Foundation said its assessment found no risk to the redemption infrastructure or systems. It also said the original schedule was unchanged and that NIGHT thawed during the pause is now redeemable.

Lace 2.1’s Wallet Security Check adds a fourth component. It lets users check an existing or restored wallet for a potential match with a known security incident.

In one sentence, Midnight moved another step from explaining privacy toward operating systems for observation, education, distribution, and safety checks.

Important caveats remain. A Data Partnership is not proof of usage growth. Holding a workshop does not mean standardization or production implementation is complete. The resumption of Glacier Drop does not eliminate the individual risks faced by SecondFi users.

What increased this week was not proof of utility, but the set of components needed to measure, learn, distribute, and handle that utility safely.

1. Market Pulse — BTC and ETH Rose While ADA and NIGHT Pulled Back

Comparing the July 4 baseline from the previous issue with SITION SDE’s July 11 baseline, the crypto market did not move in one direction.

BTC, ETH, and U.S. equities rose, while VIX fell to 15.03. The broader market leaned risk-on.

ADA and NIGHT, however, both fell by roughly 5%. In the previous issue, ADA had rebounded +19.3% week over week while NIGHT lagged that rise. This week’s move looks like a pullback after that rebound.

The important point is that, at least in weekly prices, the market did not buy Midnight’s group of announcements.

That is not a negative verdict. It is discipline against immediately linking “partnership,” “workshop,” and “redemptions resumed” to price. The value of the Data Partnership will depend on which metrics are actually published and updated consistently. The value of restarting Glacier Drop should be measured through stable portal operation and safe redemptions for users.

NIGHT prices also continue to vary across venues, and the DexScreener pair was still not configured in SITION’s live feed on July 11. This issue therefore uses only the same SDE auto series for the weekly comparison and does not overstate the precision of the price.

2. Cardano Ecosystem Watch — Still on PV10 as Next-Generation Integration Advances

van Rossem — The Enactment Floor Has Not Moved Yet

When SIPO checked Koios cli_protocol_params on July 11, Cardano mainnet’s protocolVersion.major was 10 and its minor version was 0.

That means the van Rossem hard fork, Protocol Version 11, has not yet been enacted on mainnet.

Intersect’s official notice gives July 18 as the deadline for the hard fork initiation governance action. It also lists potential ratification and enactment dates, but those are not confirmed dates.

SIPO is keeping the same verification method used in the previous issue: submission, voting, ratification, and enactment are separate stages, and a Koios change from 10 to 11 is the definitive enactment signal.

The market priced expectations for van Rossem first last week. One week later, the measured state is still PV10. ADA’s pullback this week is another reminder that expectations and enactment do not move on the same clock.

Leios Enters the Dijkstra Ledger

Implementation of the next-generation design is progressing at the same time.

Cardano’s July 10 weekly development report says LeiosCert was added as an optional field in DijkstraBlockBody. A new cardano-protocol package was also introduced to house protocol-level code.

This does not mean Leios mainnet implementation is complete.

It is nevertheless important that Leios is no longer present only in research papers and a standalone testnet; it is beginning to connect to the block body of Dijkstra, the next ledger era.

The same report also covered integrating StAnnTx memoization back to Alonzo, removing the legacy Coders machinery, and improvements across Plutus, Hydra, Mithril, and developer pathways.

Cardano is waiting for the immediate PV11 hard fork while simultaneously working to integrate Leios and Dijkstra beyond it into the core system.

Lace 2.1 — Checking Known Incidents From the Wallet

Lace Browser Extension 2.1 introduced Wallet Security Check.

Users can run the check on an existing wallet or after restoring one to see whether it may be affected by a known security incident. If there is a potential match, Lace directs the user to the relevant incident page.

This is not a universal safety guarantee. It cannot automatically prevent unknown attacks, phishing, compromised devices, malicious signatures, or leaked seed phrases.

Even so, it is meaningful progress from a model in which users must find external warnings themselves to one in which they can check known risks inside the wallet they use every day.

3. Midnight Watch — “Visible, Learnable, Distributable” in the Same Week

Visible — Data Partnership With Token Terminal

Token Terminal announced a Data Partnership with Midnight, and Midnight’s official account shared the announcement.

Data disclosure is not straightforward for a privacy-focused network.

Publishing every transaction or item of user information would undermine the value of privacy. Publishing nothing would make it impossible for outsiders to verify whether the economy is growing or which functions are being used.

The key boundary lies between individual data that must remain private and aggregate KPIs that should be public.

The Token Terminal partnership is an entry point for defining that boundary in practice. As of this issue’s cutoff, however, SIPO had not confirmed a continuously updated Midnight dashboard or usage KPIs.

The Data Partnership is not the destination; it is the starting point for measurement.

Learnable — ZK Verification Technical Workshop

Input Output Research began its first ZK Verification Technical Workshop.

The official announcement lists proof-system trade-offs, SNARK standardization including Halo2 and Plonk, ZK-Rollup security in Hydra Tail, and tooling interoperability between BN254 and BLS12-381.

This was not simply “ZK for beginners.”

Which proof system should be selected? What should standardization align? How should different curves and tooling connect? Where should Rollup security be verified? The workshop provides a place to share the concrete choices implementers face.

For Midnight to expand privacy functionality, it needs more than users. It needs people able to select, implement, and verify proof systems correctly.

Holding a workshop does not mean production implementation is complete. It does, however, provide a foundation for turning privacy from a “feature” into a verifiable professional capability.

Distributable — Glacier Drop Redemptions Resume

The Midnight Foundation resumed Glacier Drop redemptions at 17:00 UTC on July 9, or 2 a.m. JST on July 10, after pausing them in response to a security incident involving some Cardano wallets associated with SecondFi.

The Foundation said its assessment found no risk to the Glacier Drop redemption infrastructure or systems.

It also said the pause did not affect the original redemption schedule and that NIGHT thawed during the pause is now redeemable.

Two facts need to remain separate:

1. The Glacier Drop redemption infrastructure was judged safe to resume.
2. Users who used SecondFi still need to follow SecondFi’s official guidance.

“Redemptions resumed” must not be reinterpreted as “every SecondFi-related issue has been resolved.”

Midnight paused operations as a precaution while uncertainty remained around an adjacent wallet, separated the affected scope, and then resumed. Operational capability includes not only the ability to stop, but also the ability to assess safety, explain conditions, and restart.

4. Risk Dimensions

This week’s thesis is not a list of bullish headlines.

Midnight moved closer to being visible, learnable, and distributable, but each step creates another verification task.

The Data Partnership must become public KPIs. The workshop must flow into implementation and standardization. Resumed redemptions must become stable operation. Lace’s check must strengthen user protection. LeiosCert must progress into ledger integration.

Whether announcements turn into measurements will determine the next weekly assessment.

5. What to Watch Next Week

1 | van Rossem: PV10→11

The deadline for the hard fork initiation governance action is July 18. Rather than submissions or expectations, SIPO will check whether Koios protocolVersion.major changes from 10 to 11.

2 | What Token Terminal Publishes

The next focus is which Midnight metrics — such as a dashboard, fees, activity, and token metrics — are published, how often they are updated, and under what privacy boundary.

3 | Operations After Glacier Drop’s Restart

SIPO will track the redemption of NIGHT thawed during the pause, stable portal operation, and updates to guidance for SecondFi users.

4 | Turning the ZK Workshop Into Implementation

The question is whether materials, recordings, code, standardization discussions, and future workshops turn a learning event into reusable technical assets.

5 | Constitutional Committee Election

The DRep voting deadline is 21:45 UTC on July 23, or 6:45 a.m. JST on July 24. Voting continues to select 4 seats from 10 candidates.

Conclusion — Midnight Moves From “Explanation” to “Operations”

This was not a week when Midnight merely discussed the importance of privacy.

It connected with Token Terminal to measure the economy, developed people who can verify ZK systems, resumed NIGHT redemptions, and brought a path for checking known wallet incidents into Lace.

Visible. Learnable. Distributable. And handled safely.

Only when these four elements come together can privacy technology move from research and brand messaging toward infrastructure used in society.

At the same time, Cardano mainnet is still at PV10. Leios has begun entering the Dijkstra ledger, but mainnet implementation is not complete. ADA and NIGHT also fell this week.

That is precisely why this week’s progress should not be measured by price or declarations of completion.

Can it be observed? Can it be verified? Can it be distributed safely? When an incident occurs, can it be stopped, isolated, and restarted?

Midnight and Cardano added another layer of operational depth this week.

References and Sources

• Midnight Foundation, Glacier Drop Redemptions Update

https://midnight.network/blog/glacier-drop-redemptions-update

• Midnight Foundation official X account

https://x.com/midnightfdn/status/2075259474860728756

• Midnight Network / Token Terminal Data Partnership

https://x.com/MidnightNtwrk/status/2075270160076751340

• Input Output, ZK Verification Technical Workshop

https://x.com/IOGroup/status/2075203319522337237

• Lace, Browser Extension 2.1 / Wallet Security Check

https://x.com/lace_io/status/2075204996438605835

• Essential Cardano, Weekly development report as of 2026-07-10

https://www.essentialcardano.io/development-update/weekly-development-report-as-of-2026-07-10

• Intersect, Cardano upgrade: van Rossem hard fork

https://intersectmbo.org/news/cardano-upgrade-van-rossem-hard-fork

• Koios, Cardano mainnet protocol parameters

https://api.koios.rest/api/v1/cli_protocol_params

Transparency Note

Market values compare the July 4 and July 11 baselines in SITION SDE’s market_indicators.jsonl. CoinGecko supplied the auxiliary live crypto value on July 11, and Koios supplied Cardano network state. Because the live DexScreener pair for NIGHT was not configured, this issue uses only the same SDE auto series for its weekly comparison.

SIPO retrieved Koios cli_protocol_params again on July 11, 2026 and confirmed protocolVersion.major: 10. This issue does not include preliminary voting-rate figures because different aggregation methods can produce different results.

For the Token Terminal Data Partnership, SIPO confirmed the official announcement but did not confirm a continuously updated Midnight dashboard or usage KPIs. The partnership is not treated as proof of usage growth.

This article is for informational purposes only and does not recommend buying, selling, or holding crypto assets.