Cumulative transactions on Midnight’s mainnet passed one million in the early hours of October 28 JST. About a month after smart contract deployment was opened to everyone on September 28, daily transactions have risen from the low hundreds to around 48,000.
In the same week, Midnight partnered with Sig Network to bring its privacy to Ethereum applications, and the Cardano wallet Lace gained the ability to generate DUST from NIGHT. On the Cardano side, cardano-node 11.2.0, two weeks late, was published as a pre-release on October 28, and the conditions for moving testing of the next hard fork, Dijkstra, to its next stage are falling into place.
In governance, EMURGO announced that the EMURGO and Yoroi DReps will be deregistered on November 30. About 613.44 million ADA of delegation will lose its destination, and wallets that stay delegated will be unable to withdraw staking rewards unless they choose a new DRep by that date. On treasury actions, the Cardano Foundation voted No as a DRep on the copper reserve proposal, and Intersect proposed splitting the 2027 budget into seven domains.
SIPO is one of the five DReps that EMURGO’s announcement named as examples of where to move. SIPO is also part of Midnight’s Nightforce ambassador program. SIPO’s DRep has not yet voted on any of the three treasury actions. Full disclosures are in Chapters 6 and 2.
Executive Summary
- Midnight reaches one million cumulative transactions: Midnight Explorer, an independent block explorer, reported 1,019,963 at 00:07 JST on October 28, and IOG shared the post. On October 25, a daily record of 49,229 transactions was also set. Midnight’s official October report does not include usage figures.
- More ways into Midnight: through the Sig Network partnership, Ethereum applications can keep assets on Ethereum while shielding users’ balances and identities on Midnight (currently in a test environment). Lace 2.5.0 added DUST generation from NIGHT, and Nightshade, a static analyzer for Compact, was released.
- cardano-node 11.2.0 as a pre-release: the distributed configuration files move to a new format that nodes older than 11.2 cannot read. The steps for registering BLS voting keys and building sub-transactions arrive together for the first time in this version. The release notes say it is not yet recommended for mainnet use.
- The Dijkstra ledger: a rule that validates Leios certificates entered the ledger code, along with a reward-calculation change that adopts the CIP-23 approach. For Peras, the TSC confirmed the direction of using BLS for voting cryptography.
- EMURGO and Yoroi DReps deregister on November 30: delegation to the two DReps totals about 613.44 million ADA from roughly 16,000 addresses. What stops is reward *withdrawals*, not the rewards themselves.
- Three treasury actions: No votes cast on the copper proposal rose to 43.67% of the denominator, and the Cardano Foundation voted No, citing five concerns. DRep Yes on PFMS rose to 20.39%, and the Foundation voted Yes on PFMS, but it remains far from the 67% needed. There were no new Committee votes.
- How budgets get decided: Intersect opened feedback on “CEBP,” a proposal to split the 2027 treasury budget into seven domains, with the first info action targeted for submission on November 10. Version 4 of constitutional amendment CAP-3 would write per-category allocations into the constitution.
- The k poll is removed from the chain: at the epoch 664 boundary, the SPO poll on raising k to 1000 was recorded as dropped. k remains 500.
- Network: epoch 663 recorded 126,711 transactions, down 18.81% from the previous epoch.
- Keys and exchange incidents: hardware wallet maker Keystone suffered a leak of customers’ shipping information, and on October 30 a large outflow hit Binance’s hot wallet. Binance said it “will cover all losses.”
- ADA fell, NIGHT edged up: ADA −9.23%, BTC −5.62%, ETH −6.69%, NIGHT +2.11%.
1. Market Pulse
Morning fixed-point readings from October 24 to October 31.
| Asset | 10/24 | 10/31 | Week |
|---|---|---|---|
| ADA | $0.21401 | $0.19425 | −9.23% |
| BTC | $81,392.0 | $76,820.0 | −5.62% |
| ETH | $2,399.20 | $2,238.70 | −6.69% |
| NIGHT | $0.039207 | $0.040036 | +2.11% |
Three of the four assets fell, with ADA down the most. NIGHT is calculated at both ends from Cardano DEX prices, so the source is consistent. Priced in ADA, NIGHT went from 0.183203 ADA to 0.206105 ADA, +12.50%.
At epoch boundaries, ADA moved from $0.22840837 (¥36.11) at 06:45 on October 22, when epoch 663 began, to $0.20535050 (¥32.34) at 06:45 on October 27, when epoch 664 began: −10.10%. Because the readings were taken at different times, the range differs from the weekly −9.23%.
We do not link price movements to the events covered in this brief.
A few other network figures: across the epoch 663→664 boundary, the staking ratio went from 56.77% to 56.84%, and the number of delegators fell by 592 to 1,332,711. The treasury stood at 1,389,274,981 ada in epoch 664.
2. Midnight Mainnet Reaches One Million
Counted by an independent explorer
The first to report the one-million mark was Midnight Explorer, a block explorer run by TexLabs. In a post at 00:07 JST on October 28, it reported that cumulative mainnet transactions had passed 1,019,963.
“According to Midnight Explorer, Mainnet has now recorded over 1,019,963 transactions.”
The same post showed daily transactions growing from 128 on September 27 to 47,714 on October 26. About two hours later, at 02:18, IOG quoted the post from its official X account and shared it as a milestone for Midnight and “the builders putting privacy to work.” The one million figure is an external explorer’s count that the developer then acknowledged (Midnight の取引100万件、直近1週間で3分の1).
Two days earlier, a daily record had also appeared. MSB Intel, which covers markets and new technology, posted that Midnight processed 49,229 transactions on October 25, more than double the 20,445 on Zcash that day. SIPO.TOKYO’s editors checked Midnight Explorer’s daily chart and Blockchair’s daily Zcash figures, and both values matched (Midnight、1日4万9229件の取引で最多更新).
A month of growth
| Date | Daily transactions | Source |
|---|---|---|
| September 27 | 128 | Midnight Explorer post |
| October 5 | 22,655 | Midnight Explorer daily chart |
| October 20–24 | 48,353–49,007 | same |
| October 25 | 49,229 (record) | MSB Intel post, daily chart |
| October 26 | 47,714 | Midnight Explorer post |
The rise began right after the move to permissionless deployment — contracts published without review — announced on September 28 in Midnight’s official blog post “State of the Network – September 2026.” MSB Intel also reported that more than 334,000 of the million transactions came in the past seven days. That works out to about 48,000 a day, consistent with the table above.
How to read the count
Zcash, the comparison point, is a currency focused on shielding transfers themselves. Midnight is a smart contract platform that lets applications choose which data to reveal and which to hide, and most of its transactions are applications running contracts. On Midnight Explorer’s front page as of the morning of October 27, there were 1,433 deployed contracts and about 880,000 contract operations. What the volume shows is how often applications run on Midnight; the amount of shielded transfers or economic value cannot be read from this number.
The official October report
On October 27, Midnight’s official blog published “State of the Network – October 2026.” Its focus is a roadmap through Q1 2027 and products shown at TOKEN2049 in Singapore (Midnight Passport for managing identity and assets, Midnight Companions privacy-preserving AI agents, and Nightmode). It does not include usage figures such as transaction or contract counts.
The same report says Midnight shut down the indexer and RPC it had operated for mainnet and Preprod on October 9, directing developers to Blockfrost or to running their own. With the windows for reading chain data now outside Midnight’s own operation, independent counts like Midnight Explorer’s have become the main way to check usage from the outside. The report also says all mainnet validators have upgraded to node 1.0.400.
Disclosure: SIPO is part of Midnight’s Nightforce ambassador program and, as a Cardano SPO, is in a position that could fall within the opening of block production described in the roadmap.
3. Ways Into Midnight: Ethereum, Lace and Developer Tools
Sig Network and Ethereum applications
On October 28, the Midnight Foundation announced a partnership with Sig Network, a signing network, on its official blog and X. It lets applications running on Ethereum keep assets and liquidity on Ethereum while shielding each user’s balance and identity on the Midnight side.
The blog describes four steps. A Midnight contract verifies a user’s request and prepares one Ethereum transaction; Sig Network signs it with a threshold signature from multiple independent signers; the transaction executes from an Ethereum account held by the contract; and the result returns to Midnight as a proof. The blog says there is no bridging and no wrapping. Sig Network CEO David Millar-Durrant says in the blog:
“Teams shouldn’t have to rebuild an application to make it private.”
Transactions on the Ethereum side remain public, so amounts and timing are visible. What is hidden is each user’s activity, balance and transaction history. It currently runs on Midnight’s stagenet (a pre-release test environment) and supports deposits, swaps on Uniswap, supplying to Aave and withdrawals to any Ethereum address. The blog does not say when it will be available on mainnet (Sig Network、Midnight のコントラクトに Ethereum の口座を用意).
Where October 20’s Nightmode was an entrance for “users shielding their own assets,” this is an entrance for “applications calling Midnight’s privacy as a component.” The Midnight Foundation wrote on X: “Welcome to Midnight, Ethereum.”
Lace 2.5.0 generates DUST inside the wallet
Version 2.5.0 of the Lace browser extension, a Cardano wallet, was published in the early hours of October 30 JST. The release notes describe the new feature:
“Designate NIGHT held in your Cardano account to a Midnight address and generate DUST directly from Lace.”
DUST is a resource used only for transaction fees on Midnight and cannot be sent to others. According to Midnight’s technical documentation, the cap is 5 DUST per NIGHT, and the time to reach the cap is about one week regardless of how much NIGHT is held. When the backing NIGHT is sent, DUST starts decaying toward zero from that moment. The feature, announced in 2.4.0 on September 23 as coming “shortly after” release, arrived about five weeks later (Lace 2.5.0、NIGHT から DUST を生む機能を搭載).
Developer tools and the ecosystem
- Nightshade (October 29): a static analyzer that reads Compact contracts without running them, looking for privacy leaks, spoofable authentication, ignored signature checks and more, was released under Apache-2.0. It has 96 rules, 28 of which run by default. The repository documentation says the absence of findings should not be treated as proof of safety (Compact の静的解析 Nightshade、96 の規則で公開).
- ShadowLabz: in the early hours of October 27, Midnight’s official account featured ShadowLabz, a team that demonstrated at TOKEN2049 a vote whose results anyone can verify while hiding who chose what (ShadowLabz、TOKEN2049 で Midnight の秘密投票を実演).
- Indexer advisory: on October 28, a “high” severity advisory (GHSA-67mp) was published for midnight-indexer. It says “Carefully crafted Tx can halt indexer”; what stops is the component that organizes and serves data, not the chain itself.
There were no midnight-node or Compact releases this week. The October report says “Sig Network announced TRON as the next target for Nightmode, scheduling deployment for December 2026.”
4. cardano-node 11.2.0 Released as a Pre-Release
The starting point, two weeks late
At 21:53 JST on October 28, Intersect published cardano-node 11.2.0 on GitHub as a pre-release. As we reported last week, the Hard Fork Working Group minutes had said “pre-release in the week of October 12” as of October 13, and “tagged version expected this week” as of October 20. On October 29, Intersect announced on X:
“Node 11.2 is out as a pre-release, bringing Dijkstra closer to ecosystem-wide testing and integration.”
The public Dijkstra testnet opened on October 23 but has been running on protocol version 11 (Conway) with node 11.1.3. In Intersect’s sequence, a governance action initiating the hard fork follows the 11.2 pre-release, and the network then moves to version 12 (Dijkstra) on 11.2. The Hard Fork Working Group’s October 27 minutes say that once 11.2 is available it “will be used to fork DijkstraNet into the Dijkstra era,” and for 11.3, which includes Leios: “Realistically 3-4 weeks for 11.3 version tagged and pre-released.” Intersect’s Upgrade Bulletin #40 asks SPOs to upgrade to 11.2 before the testnet hard fork. As of the morning of October 31, the testnet is still on version 11.
Changes for node operators
The core “breaking change” in the release notes concerns configuration files.
- Distributed configuration files in a new format: published configuration files such as mainnet-config.json now wrap their contents in four fields —
$schema,Version,MinNodeVersionandConfiguration— and nodes older than 11.2 cannot read them. Updating the configuration files first will leave older nodes unable to start. Existing flat-format configuration files still work with 11.2. - Communication with wallets and indexers: old versions (V16–V22) of the protocol that local tools use to talk to the node were dropped, along with some queries only available through them.
- Ledger state save interval: by default, the ledger state is now saved roughly once a day on mainnet.
- Mithril signer: the bundled Mithril signer has been raised to 1.2.5.
What arrives together for Dijkstra for the first time
The most concrete item for SPOs is BLS voting key registration. In the 11.2.0 cardano-cli, a BLS signing key is passed to the pool registration certificate, and the release notes make this registration mandatory from Dijkstra onward. Proof of possession is now built into the certificate, and the standalone commands for it were removed.
On the transaction side, steps were added to build and sign sub-transactions, transactions nested within a transaction, with cardano-cli. Only native scripts and Plutus V4 can be used inside sub-transactions. Plutus V4 is now usable at protocol version 12, but according to the release notes, V4 in this version has the same built-in functions as today’s V1–V3, with the new functions to be enabled in a later version. Groundwork for Leios and Peras is included, but both are disabled by default (Node 11.2、Dijkstra の取引を組み立て可能に).
What remains blank
The pre-release notes still have blank sections for “known issues,” benchmark reports and system test results. Whether these are filled in and the pre-release label is removed when it becomes a full release is the next thing to check (cardano-node 11.2.0 先行版、設定ファイルが新形式に).
Elsewhere, cardano-cli 11.6.0.0 (October 27) and v3.0.0 of GovTool, the governance interface (October 26), were also released.
Disclosure: SIPO is an SPO running three pools, and upgrading to 11.2, ordering the configuration-file swap and registering BLS voting keys are SIPO’s own work.
5. The Dijkstra Ledger and the Direction for Peras
A rule to validate Leios certificates
On October 27 JST, a rule called “LEIOSCERT” that validates Leios certificates was merged into Cardano’s ledger code (cardano-ledger #6209). According to the issue describing its design, the rule checks three things: that the current slot is not too early relative to the slot in which the batch of transactions (the endorser block) was announced, that the announcement is not from a previous epoch, and that the certificate itself is valid.
On October 29, an interface was also added so that the node’s consensus layer can check just the certificate before the endorser block’s contents arrive (#6216). In its October 30 announcement of the weekly development report, IOG listed “Leios certificate checks” first among the week’s items (Cardano の台帳、Leios 証明書の検証規則を実装).
Minimum values in reward calculation
The same week, the ledger also gained a change that directly affects SPOs and delegators. Under Dijkstra, registering or updating a pool with a declared fixed cost below the minimum pool cost (minPoolCost) will no longer be rejected with an error; instead, reward calculation uses the larger of the declared fixed cost and the minimum. The minimum pool margin (minPoolMargin) is treated the same way: reward calculation uses the larger of the declared margin and the minimum margin.
This is the CIP-23 implementation we covered last week (cardano-ledger #6197) being merged into the ledger. Last week we described #6197 as still a draft; it had in fact been merged at 10:32 JST on October 23. We correct that here. This change does not set the minimum margin’s value, and as we reported last week, version 4 of constitutional amendment CAP-12 says it will be “introduced at 0, and a later Parameter Update sets its initial value.” The cardano-node 11.2.0 release notes likewise say the maximum pledge leverage from CIP-50 and the minimum pool margin from CIP-23 were added to the ledger as parameters for future eras, with no effect until values are set.
Because declared values and the values used in reward calculation can diverge, lists that compare pools by declared values alone may not match delegators’ expected rewards.
CAP-12 moved to version 5 on October 30. The author’s summary says “Leios parameters cannot be set to zero,” and that should Leios ever need to be deactivated temporarily, “a contingency plan in the spirit of the Disaster Recovery Plan for Cardano networks (CIP-0135) is the desirable route, outside the Constitution, rather than a parameter setting.” Six items that had values in version 4 went back to placeholders pending Parameter Committee review. The October 28 TSC meeting that was to consider this shutdown procedure was not quorate, and no formal position was issued.
Peras: BLS and a higher quorum
In its weekly update dated October 23, Tweag, which develops Ouroboros Peras to speed up transaction settlement, reported that Intersect’s Technical Steering Committee (TSC) confirmed, as the preferred direction for now, using BLS signatures for voting cryptography together with a higher quorum threshold. The design document had listed Pixel signatures as a candidate, which have forward security — the property that past signatures cannot be forged even if a key is later stolen. The update does not give the raised quorum value or the reason for choosing BLS (Peras の暗号方式、TSC が BLS と定足数引き上げを確認).
SIPO’s three pools run at a 3.9% margin and a 340 ada fixed cost. While the minimum margin enters at 0, reward calculation does not change for any pool, SIPO included.
6. EMURGO and Yoroi DReps Deregister on November 30
A date for the August notice
At 13:27 JST on October 28, EMURGO announced on its official X account that the EMURGO and Yoroi DReps will be formally deregistered on November 30. On August 3 it had said it intended to deregister eventually, to focus on supporting users affected by the security incident at SecondFi (formerly Yoroi); the plan now has a date. The announcement asks delegators:
“If your wallet is currently delegated to either the EMURGO or Yoroi DRep, please delegate to another active DRep of your choice before 30 November 2026 to ensure you can continue to withdraw your staking rewards and keep your voice represented in Cardano governance. De-registration date may be extended further based on extenuating circumstances.”
As of October 28 (epoch 664), delegation to the two DReps stood as follows.
| DRep | Delegated ADA | Delegating stake addresses |
|---|---|---|
| Yoroi | about 401.26 million ADA | 15,171 |
| EMURGO | about 212.18 million ADA | 815 |
| Total | about 613.44 million ADA | about 16,000 |
What stops is withdrawals
CIP-1694, which defines Cardano’s governance, says that reward account withdrawals are blocked when a stake address is not delegated to a DRep. What stops is withdrawals, not the rewards themselves. Delegation to a stake pool is a separate step, so rewards from the pool keep accumulating in the reward account and can be withdrawn again once delegation is redone. Delegating to the predefined Abstain or No Confidence options instead of a specific DRep also keeps withdrawals working.
As the August announcement said, users who moved wallets with SecondFi’s migration tool already lost their DRep delegation at the time of the move. This deadline affects wallets still delegated to either of the two DReps.
The criteria and five DReps named
The announcement lists four criteria for choosing a new DRep — a consistent voting record with clearly published rationales, long-term involvement in the ecosystem, knowledge across commercial and technical areas, and a balanced view that weighs priorities evenly — and names five DReps as examples: Cardano Foundation, Nagamaru, Phil UPLC, SIPO and Socious. The original says “DReps such as,” so the list is not limited to these five.
Large DReps’ votes also showed up on this week’s treasury actions. The EMURGO and Yoroi DReps voted Abstain on the copper reserve proposal on October 29.
Disclosure: SIPO is one of the five DReps named as examples in EMURGO’s announcement and, as of October 28, has about 104.63 million ADA from 417 delegations. It has a direct interest in where delegators move. How each DRep voted on which action, and with what rationale, can be checked in the DRep directory on gov.tools (EMURGO と Yoroi の DRep、11月30日で登録解除).
7. Three Treasury Actions, and the Cardano Foundation’s No on Copper
Where the votes stand
DRep votes retrieved at 07:16 JST on October 31. The denominator is explicit Yes plus No votes cast, non-voters and Always No Confidence.
| Action | Amount | DRep Yes | No votes cast | Deadline |
|---|---|---|---|---|
| Copper | 22,000,000 ADA | 4 votes, 0.36% | 87 votes, 43.67% | 06:44:51, November 16 |
| AURORA | 940,000 ADA | 13 votes, 3.32% | 45 votes, 29.27% | 06:44:51, November 21 |
| PFMS | 9,600,000 ADA | 26 votes, 20.39% | 27 votes, 13.30% | 06:44:51, November 21 |
Since last week, No votes cast on copper rose from 51 (25.75%) to 87, and Yes votes on PFMS from 10 (3.46%) to 26. Each needs 67% DRep approval and two-thirds of the Constitutional Committee judging it “constitutional.” There were no new Committee votes this week. Copper and AURORA still have two “unconstitutional” votes each, and PFMS one “constitutional.”
The Cardano Foundation votes No on copper
On October 28, the Cardano Foundation voted No on the copper reserve proposal as a DRep and wrote on X:
“We see real promise in RWA tokenization, but we believe this proposal is too risky for the Treasury: 22M $ADA under a single party’s control, with high fees and safeguards still in…”
The rationale it recorded on-chain divides its concerns into five: the full amount goes to a key-controlled address managed by the recipient, with no safeguards for audit or custody described; by the proposer’s own estimate, copper would need to rise about 49%, from $6.73 to about $10.06 per pound, for the treasury to recover its ADA; concentrating in a single real-world asset is not diversification; of up to 3,360,023 ADA paid directly to the proposer, 2,640,000 ADA is set as 12% of the total rather than by workload; and the warehouse is not named, so the reserve can neither be verified nor enforced from the Cardano side. The rationale says that if the proposer became insolvent, the copper would enter the bankruptcy estate and the treasury might recover nothing. The Foundation also states, in both its summary and the opening of the rationale, that it is not rejecting RWA tokenization itself (Cardano 財団、銅準備金の国庫案に反対票).
PFMS and the Uttar Pradesh case
PFMS seeks development funding for a police evidence-management system built by India’s Trivolve Tech, with the Cardano Foundation saying it will act as administrator of the funds. On October 26, the Foundation published a case study saying police in Uttar Pradesh, India’s most populous state, record hashes of evidence scans and forensic results on Cardano and use them on active cases. The system was built by the same Trivolve Tech (ウッタルプラデーシュ州警察、証拠の記録を Cardano に).
At 17:27 JST on October 30, the Cardano Foundation voted Yes on PFMS as a DRep. Its rationale says “Four of five tranches, totaling 7,800,000 ada, are released only after the independent assurer and the administrator verify the deliverables,” and discloses: “the Cardano Foundation is a co-author of this proposal and its named administrator, and receives the 200,000 ada Administration budget line to cover its administration expenses and taxes.”
Cardano’s official account has announced “Governance Hour #13” on PFMS, starting at 01:30 JST on November 6.
SIPO’s DRep has not yet voted on copper, AURORA or PFMS.
8. How Budgets Get Decided: CEBP and CAP-3
Intersect’s 2027 budget proposal
On October 28, Intersect published the “Cardano Ecosystem Budget Process (CEBP),” a proposal to decide Cardano’s 2027 treasury budget across seven domains, and opened feedback on DRepTalk. It is being developed in cooperation with the Cardano Foundation.
| Domain | Candidate Steward |
|---|---|
| Core development and maintenance | Intersect |
| Applied research | Intersect |
| Developer support | PRAGMA |
| Marketing, analytics and events | Cardano Foundation |
| Adoption and ecosystem growth | Cardano Foundation |
| Governance coordination | Intersect |
| Open Contributions | None (anyone can propose directly to DReps) |
The proposal states that “stewardship is not gatekeeping,” keeping spending decisions, annual goals, per-domain allocations and Steward approval with DReps. It proceeds in three stages: in November, an info action seeking approval of the concept, domain definitions and Steward nominations (targeted for submission on November 10, with 51% DRep support as the benchmark); then from December to January 2027, per-domain info actions (60% benchmark) and an info action setting the 2027 limit. For the second stage, Intersect states that it “does not yet bind DReps to the 2027 CEBP” (Intersect、Cardano の2027年予算を7領域に分ける案を公開).
CAP-3 version 4
Intersect’s Weekly Update #134 (October 24) introduced version 4 of constitutional amendment CAP-3. It adds per-category allocations, decided in the same action, to the cap on total treasury withdrawals (the Net Change Limit); each withdrawal would state its category and amount in metadata and could not exceed that category’s allocation. The key design point of this version is a new standalone guardrail requiring at least 67% of active voting stake to adopt the limit (CAP-3 第4版、トレジャリー引き出しに区分ごとの上限).
CEBP would proceed through info actions and stakeholder agreement without changing the constitution, while CAP-3 is a binding constitutional amendment. Intersect’s CEBP page does not mention CAP-3, and the relationship between the two has not been described.
The return path works for the first time
On the evening of October 24, Intersect announced that it had, for the first time on mainnet, executed the function in its 2025 budget smart contract that returns unspent funds to the treasury, sending back 115,172 ADA. The two transactions on October 20 and 21 returned part of 750,000 ADA withdrawn in 2025 for Intersect’s Product Committee (Intersect の準備金コントラクト、初の返却で 115,172 ADA).
9. Recounting Voting Power and Decentralization
- Two-thirds with the top 20 DReps: on October 24, the SPO BKIND published a count showing that the top 20 of 294 active DReps alone reach the two-thirds of voting power needed to pass treasury withdrawals. SIPO.TOKYO’s editors recounted with Koios data as of October 25 and found the top 19 at 67.9% (Cardano の DRep 投票力、上位20で3分の2に).
- A format for disclosing overlapping roles: on October 29, BKIND submitted a CIP, “Disclosure of Governance Roles,” setting where and how people holding more than one of the SPO, DRep and Constitutional Committee roles disclose the overlap. The constitution requires disclosure but sets neither place nor format (SPO と DRep の兼任開示、BKIND が書式の CIP を提出).
- A developer survey on-chain: at 19:27 on October 28, the Cardano Foundation submitted its 2026 developer survey as an info action. The action says “There’s nothing to vote on here,” and responses are accepted until November 30 (Cardano 財団の開発者調査 2026、回答はすべてチェーン上に).
SIPO is an operator holding both SPO (three pools) and DRep roles, and falls within the disclosure covered by BKIND’s CIP.
10. SIPO’s Three Pools After the k Poll
This is SIPO’s own position, so we disclose the record and our interests together.
As we reported last week, the SPO poll on raising k from 500 to 1000 reached its deadline with explicit Yes at 2.20%, and at the epoch 664 boundary (06:44:51 on October 27), it was also recorded on-chain as dropped. As an info action, it has no binding effect. On October 7, SIPO voted No on the poll with its three pools and Abstain as a DRep.
The k debate is not over, so as last week, here is a mechanical calculation dividing on-chain circulation as of the morning of October 31, 36,819,240,008 ada, by k.
| k | Saturation point (circulation ÷ k) | SIPO’s three pools (live stake at end of epoch 663) |
|---|---|---|
| 500 (current) | about 73,638,480 ada | all three below |
| 1000 (poll’s proposal) | about 36,819,240 ada | SIPO 56,272,492 ada = 1.528x / SIPO2 35,221,046 ada (0.957) / SIPO3 24,276,980 ada (0.659) |
SIPO’s first pool would sit above the saturation point at k=1000, and it grew by about 2.32 million ada in a week. Its delegator count barely changed, from 1,106 to 1,105.
In epoch 663, the three pools produced 129 blocks in total: SIPO 60, SIPO2 38 and SIPO3 31 (121 in epoch 662). Delegators number 1,105, 476 and 543.
11. Network: 126,711 Transactions in Epoch 663
| Epoch | Period (JST) | Blocks | Transactions | Per block | Fees |
|---|---|---|---|---|---|
| 661 | 10/12 6:44 – 10/17 6:44 | 21,385 | 253,314 | 11.85 | 67,761.27 ada |
| 662 | 10/17 6:44 – 10/22 6:44 | 21,268 | 156,063 | 7.34 | 54,576.59 ada |
| 663 | 10/22 6:44 – 10/27 6:44 | 21,471 | 126,711 | 5.90 | 40,210.07 ada |
Epoch 663 recorded 126,711 transactions, down 18.81% from the previous epoch, with fees down 26.32%.
On the rewards side, total rewards for epoch 662 were finalized at 6,146,980 ada, down 0.30% from 6,165,276 ada in epoch 661. The treasury balance rose by +3,602,917 ada at the epoch 664 boundary. Rewards are funded by a payout from the reserve plus fees, 20% of which goes to the treasury. What we can state here is the arithmetic of these figures.
12. Tooling and Layer 2
- Daedalus 11.6.0 (October 24): a mainnet maintenance release that detects missing chain data left by Mithril partial syncs in versions before 11.5.0 and rebuilds it from complete, verified Mithril data. Se7en Labs, which provides support, says “We recommend all Daedalus users upgrade” (Daedalus 11.6.0、部分同期で欠けたチェーンデータを再構築).
- Dingo v0.88.0 (October 25): the Go node Dingo added connection settings for the Dijkstra testnet, taking nodes other than the Haskell cardano-node a step closer to joining the test network (Dingo v0.88.0、Dijkstra テストネットに対応).
There were no full releases of Hydra or Mithril this week.
13. DeFi
- Nine Cardano PRIME teams: on the morning of October 24, Cardano PRIME, which funds Cardano DeFi, announced its first nine funded teams, including Liqwid’s lending V3, an Indigo overhaul, new SundaeSwap features, a bridge to EVM chains, a real-world-asset bond market and two audit firms (Cardano PRIME、最初の資金提供先9チームを発表).
- Liqwid’s cleanup: in the early hours of October 31, Liqwid announced that all bad-debt positions left by the July and August NIGHT liquidations are now closed. Every affected market except wanUSDC was made whole through loan repayment, and reimbursement for the wanUSDC market can be claimed from November 2.
- Strike’s volume: on the evening of October 30, perpetuals exchange Strike announced a new all-time high of $30 million in 24-hour trading volume. On October 26 it launched SUI perpetuals with up to 20x leverage (Strike、24時間取引高3,000万ドルで過去最高).
14. Key and Exchange Incidents
Keystone customer data
In the early hours of October 25 JST, hardware wallet maker Keystone disclosed that unauthorized access to its official website had given a third party customers’ names, contact details, shipping addresses and order contents. It says it detected the access on October 20 and confirmed it on October 23. Private keys and recovery phrases are said to be out of scope, but someone who knows order details could contact customers posing as staff. In a follow-up, it asked owners of devices delivered on or after October 20 to contact support and said current inventory will be destroyed (Keystone 公式サイトに不正アクセス、購入者の配送情報が流出).
The Binance outflow
Early on October 30 JST, a large outflow of assets occurred from the hot wallet of exchange Binance. At 09:13, Binance announced on its official X account:
“We are working non-stop to resolve this issue. Binance will cover all losses. As a precaution, all deposits and withdrawals are temporarily suspended while our team conducts security checks, freezes funds, and works with law enforcement.”
Estimates of the amount vary among research firms, and Binance has not yet confirmed the method. Binance’s announcement does not address the treatment of individual assets such as ADA or NIGHT. That same morning, Hoskinson quoted a post about the incident and wrote “Midnight Fixes this,” without saying how (Binance で大規模流出、ADA・NIGHT を持つ方へ現時点の整理).
15. Organizations and People
- The Cardano Foundation joins CMTA: on October 29, the Foundation announced it had become a member of CMTA (Capital Markets and Technology Association), the Swiss industry body that sets the CMTAT standard for tokenized securities. Three weeks earlier, CMTA recognized Cardano’s programmable token standard CIP-0113 as equivalent to CMTAT (Cardano 財団、トークン化証券のスイス業界団体 CMTA に加盟).
16. Risk Dimensions
- Operations (configuration file order). The new 11.2 configuration files cannot be read by nodes older than 11.2. After the full release, swapping in the configuration files before the node binary will leave the node unable to start. Tools that connect to the node, such as wallets and indexers, also need checking for reliance on old protocol versions.
- Operations (BLS voting keys). From Dijkstra, pool registration requires a BLS voting key, and pools without one cannot vote in Leios. Since the steps changed in 11.2, there is value in running through them on the test network first.
- Pool economics (two floors). A change that uses the larger of the declared and minimum values for fixed cost and margin in reward calculation has entered the ledger. The values are not yet set, and the gap between declared and effective values also affects how pool lists appear to delegators.
- Delegation (November 30). Wallets still delegated to the EMURGO or Yoroi DRep will be unable to withdraw rewards after the deadline. Users who do not usually follow governance announcements are the most likely to reach the date unaware.
- Treasury. All three actions are far from the 67% needed, and Committee judgments of “unconstitutional” came first on copper and AURORA. Two paths for deciding the 2027 budget, CEBP and CAP-3, are being discussed at the same time.
- Midnight. The one million figure is an external explorer’s count, and which applications generate the volume has not been published. Sig Network’s mechanism is still in a test environment, with no mainnet date given.
- Keys and exchanges. In the Keystone case, beware of fake contacts posing as staff. In the Binance case, the resumption of deposits and withdrawals and the treatment of individual assets will be announced only through Binance’s official channels.
17. What to Watch Next Week
- Epoch 665 boundary — 06:44:51 on November 1. Epoch 664’s transaction count and the three pools’ block counts are finalized. Check Koios epoch data.
- Liqwid’s wanUSDC reimbursement — claims open from November 2. Check @liqwidfinance on X.
- Dijkstra testnet hard fork — the action initiating the hard fork that follows the 11.2 pre-release, and the switch to version 12. Check Intersect’s Upgrade Bulletin and the testnet explorer Kleioscan.
- Blanks in the cardano-node 11.2.0 release notes — whether known issues, benchmarks and system tests are filled in and the pre-release label is removed. Check the
IntersectMBO/cardano-nodereleases page. - PFMS Governance Hour #13 — 01:30 JST on November 6. Check the announcement on @Cardano’s X.
- IOG weekly development report — Friday, November 6. How far the Leios endorser-block rules extend. Check the development report page on Essential Cardano.
- CEBP stage-two info action — targeted for submission on November 10. Check GovTool and the “A More Strategic 2027 Cardano Budget” thread on DRepTalk.
- Copper action deadline — 06:44:51 on November 16. The remaining five Committee members’ votes can be followed on the action’s page on gov.tools.
- What drives Midnight’s usage — which contracts generate the volume. Check Midnight Explorer’s contract list and the November edition of “State of the Network” on Midnight’s official blog.
- Sig Network on mainnet — check the supported networks listed in Sig Network’s documentation (docs.sig.network).
- EMURGO and Yoroi DRep deregistration — November 30. Any extension can be checked on @emurgo_io’s X.
Summary
This week, Midnight entered the stage of being measured by usage. Mainnet transactions passed one million cumulatively about a month after permissionless deployment, and around 48,000 a day has held steady. In the same week, a path for Ethereum applications to use Midnight’s privacy as a component and the steps to generate DUST inside Lace were added, widening the entrances on both the user and application sides. Which applications generate that volume, however, has not yet been officially explained.
On the Cardano side, node 11.2.0, two weeks late, arrived as a pre-release, bringing together the steps for BLS voting key registration and sub-transactions. Leios certificate validation and reward calculation that applies minimum values were written into the ledger, and Dijkstra is now waiting for its switch on the test network.
In governance, about 600 million ADA of delegation will lose its destination on November 30, and two proposals to decide treasury spending by domain or category up front now sit side by side. Whom to entrust one’s voice to, and in what order to decide how money is spent: it was a week that gave both delegators and DReps more material for those judgments.
Next week, the first thing to check is whether the action to begin the Dijkstra testnet hard fork appears in Intersect’s Upgrade Bulletin.
References and Sources
Where the text refers to SIPO’s own articles, links are given in place. The following are primary sources.
- Koios REST API (epoch information, rewards and treasury, action status, vote timestamps, circulation): https://api.koios.rest/api/v1
- Cardano governance actions: https://gov.tools/governance_actions
- Midnight Explorer post (1,019,963 cumulative): https://x.com/midnightexplr/status/2115098116269670899
- IOG post (sharing the one million mark): https://x.com/IOGroup/status/2115130924287644054
- MSB Intel post (October 25 record): https://x.com/MSBIntel/status/2114816838744051735
- MSB Intel post (more than 334,000 in the past seven days): https://x.com/MSBIntel/status/2115111279689892236
- Midnight blog, “State of the Network – October 2026”: https://midnight.network/blog/state-of-the-network-october-2026
- Midnight blog, “State of the Network – September 2026”: https://midnight.network/blog/state-of-the-network-september-2026
- IOG post (Sig Network partnership): https://x.com/IOGroup/status/2115501629860634895
- Midnight official account, Sig Network announcement: https://x.com/MidnightNtwrk/status/2115476383841276074
- Midnight Foundation post (Sig Network): https://x.com/midnightfdn/status/2115489716707733551
- Lace browser extension 2.5.0: https://github.com/input-output-hk/lace/releases/tag/lace-extension%402.5.0
- Nightshade announcement: https://x.com/DicksonWuML/status/2115778927490699575
- Midnight official account, ShadowLabz feature: https://x.com/MidnightNtwrk/status/2114755181342867967
- cardano-node 11.2.0: https://github.com/IntersectMBO/cardano-node/releases/tag/11.2.0
- Intersect’s 11.2 announcement: https://x.com/IntersectMBO/status/2115892192283668498
- Hard Fork Working Group minutes (October 27): https://cardanoupgrades.docs.intersectmbo.org/general/hard-fork-working-group-meeting-minutes/27th-october-2026
- cardano-ledger pull request #6197: https://github.com/IntersectMBO/cardano-ledger/pull/6197
- CAP-12 (CAP portal): https://cap-portal-api.onrender.com/proposals/12
- midnight-indexer advisory GHSA-67mp: https://github.com/midnightntwrk/midnight-indexer/security/advisories/GHSA-67mp-mh58-qx5h
- Intersect’s public Dijkstra testnet announcement: https://x.com/IntersectMBO/status/2113511556411478174
- Cardano Operations Book (Dijkstra): https://book.play.dev.cardano.org/adv-dijkstra.html
- cardano-cli 11.6.0.0: https://github.com/IntersectMBO/cardano-cli/releases/tag/cardano-cli-11.6.0.0
- GovTool v3.0.0: https://github.com/IntersectMBO/govtool/releases/tag/v3.0.0
- IOG weekly development report announcement (October 30): https://x.com/IOGroup/status/2116153156329685293
- Tweag’s Peras weekly update announcement: https://x.com/tweagio/status/2114731259779752002
- EMURGO announcement: https://x.com/emurgo_io/status/2115299422850683118
- Cardano Foundation’s No on the copper action: https://x.com/Cardano_CF/status/2115515373684507100
- Copper action: https://gov.tools/governance_actions/6eddf4f1dbad06f329aa69743559c4930b7b689f16c073061d228d9c6613d19c#0
- AURORA action: https://gov.tools/governance_actions/14d6a48df8b9099a3e727e1bf6a9ac6c911341a9601e91c7d3ac799bfd89b01b#0
- PFMS action: https://gov.tools/governance_actions/72491608dc1a500d38613214069a2bd3b7e9a0e670d5abd7d6374e6bb54fc0e8#0
- Cardano Foundation’s Uttar Pradesh case study announcement: https://x.com/Cardano_CF/status/2114715936179486892
- Cardano official account, Governance Hour #13 announcement: https://x.com/Cardano/status/2116245547593908636
- Intersect’s CEBP announcement: https://x.com/IntersectMBO/status/2115422937910055415
- Cardano Foundation’s CEBP announcement: https://x.com/Cardano_CF/status/2115426022317580674
- Intersect’s reserve contract return announcement: https://x.com/IntersectMBO/status/2113992409247830274
- Intersect Weekly Update #134 announcement: https://x.com/IntersectMBO/status/2114344068931051956
- BKIND post (voting power concentration): https://x.com/BKINDSPO/status/2113942214388687204
- BKIND post (role disclosure CIP): https://x.com/BKINDSPO/status/2115804795579548054
- Cardano Foundation’s developer survey announcement: https://x.com/Cardano_CF/status/2115400500963312112
- Daedalus 11.6.0 announcement (Se7en Labs): https://x.com/se7en_labs/status/2113821019861610990
- Daedalus 11.6.0: https://github.com/input-output-hk/daedalus/releases/tag/11.6.0
- Dingo v0.88.0 announcement: https://x.com/blinklabs_io/status/2114150156106932565
- Cardano PRIME announcement: https://x.com/Cardano_Prime/status/2113781018939568311
- Liqwid announcement: https://x.com/liqwidfinance/status/2116213550238912591
- Strike announcement: https://x.com/strikeperps/status/2116168939680219166
- Keystone announcement: https://x.com/KeystoneWallet/status/2114054080754770137
- Keystone follow-up: https://x.com/KeystoneWallet/status/2115826835900792966
- Binance announcement: https://x.com/binance/status/2115960292115124558
- Hoskinson’s post (Binance incident): https://x.com/IOHK_Charles/status/2115949830354977136
- Cardano Foundation’s CMTA announcement: https://x.com/Cardano_CF/status/2115749391126384861
- Morning fixed-point values (ADA / BTC / ETH / NIGHT): https://www.coingecko.com
- Weekly Brief #29: https://sipo.tokyo/language/en/weekly-brief-29-en/
Transparency Notes
- Votes on the three treasury actions: retrieved from Koios at 07:16 JST on October 31. The denominator is explicit Yes plus what counts against (No votes cast, non-voters and Always No Confidence): copper 4,529,167,284 ada, AURORA 4,383,912,770 ada, PFMS 5,250,708,763 ada. The Yes ratio is Yes ÷ denominator, and the No-votes-cast share is No votes cast ÷ denominator (copper 1,978,059,943 ÷ 4,529,167,284 = 43.67%, AURORA 1,282,969,957 ÷ 4,383,912,770 = 29.27%, PFMS 698,554,799 ÷ 5,250,708,763 = 13.30%). The No ratio returned by the public API includes non-voters and Always No Confidence, so we do not use it. Abstentions are excluded from the denominator.
- Committee votes: no new votes were recorded this week. We do not name Committee members in the text.
- The k poll: its on-chain status is “expired” (epoch 663) and “dropped” (epoch 664). Info actions have no ratification process and no “rejected” state.
- Midnight transaction counts: one million (1,019,963) is from Midnight Explorer’s post, and 49,229 on October 25 is from MSB Intel’s post and Midnight Explorer’s daily chart. Zcash’s 20,445 matches Blockchair’s daily figures. Midnight Explorer is not an official Midnight Foundation service.
- Delegation to the EMURGO and Yoroi DReps: values checked on Koios on October 28 (epoch 664). SIPO’s DRep delegation is from the same time.
- cardano-node 11.2.0: based on the GitHub release record (2026-10-28 12:53:25 UTC, pre-release). We did not confirm any fix described with the word “security” in the release notes, so we do not call it a “security fix.”
- Reward calculation change: based on the description of the change merged into the ledger repository. The merge time of #6197 is from GitHub’s record (2026-10-23 01:32:29 UTC). The minimum margin’s value has not been set.
- Cardano Foundation’s votes: the No on copper is based on its X announcement and on-chain rationale; the Yes on PFMS is based on the on-chain record (17:27 JST on October 30) and verbatim rationale. For PFMS, we note alongside it the Foundation’s own disclosure that it is co-author and administrator and receives 200,000 ada.
- Rewards and treasury: total rewards are from Koios epoch information. The treasury increase is the difference between epoch balances (1,389,274,981.55 − 1,385,672,064.61).
- Saturation calculation: a mechanical calculation dividing on-chain circulation as of the morning of October 31, 36,819,240,008 ada, by k. SIPO’s three pool figures are live stake taken right after the end of epoch 663.
- Market value timestamps: October 24 values are from the 06:35:01 morning reading and October 31 values from 06:35:08. The epoch-boundary ADA figure (−10.10%) is the value at the exact boundary time.
- SIPO’s interests: in the text we disclose that, regarding EMURGO’s announcement, SIPO is one of the five DReps named as examples and has about 104.63 million ADA from 417 delegations; regarding Midnight, that SIPO is part of the Nightforce ambassador program and could fall within the opening of block production; regarding node 11.2 and Dijkstra, that swapping configuration files and registering BLS voting keys are SIPO’s own work; regarding reward calculation, that the three pools run a 3.9% margin and 340 ada fixed cost; regarding the k poll, that SIPO voted No with three pools and Abstain as a DRep and that its first pool would sit above the k=1000 saturation point; regarding the three treasury actions, that SIPO’s DRep has not yet voted; and regarding role disclosure, that SIPO holds both SPO and DRep roles.
- What we did not write: the amount and method of the Binance outflow (not officially confirmed), whether NIGHT was affected by the Binance incident (no official Binance statement), Sig Network’s mainnet timing (not confirmed in official materials), outlooks on any action’s passage, and speculation about why any DRep voted as it did.
- Prices and events: not linked.
This is not investment advice. For information and research purposes only.
