On the on-chain votes as of 7:15 a.m. JST on November 14, the three actions seeking to withdraw funds from the Cardano treasury can no longer reach the 67% they need to pass, even if every DRep (delegated representative) who has not yet voted were to vote Yes. On PFMS, the police evidence-management proposal, 57 voted No votes (34.77%) now outweigh 41 Yes votes (29.51%), and the Copper strategic reserve reaches its deadline at 6:44:51 a.m. JST on November 16.
This is arithmetic that assumes delegation and the votes already cast stay as they are, not a forecast. DReps can change their votes until the deadline, and delegation moves. In the same week, the 21 million ADA from a cancelled Catalyst budget appeared in the treasury balance, and Midnight published release notes describing what Ledger 9 fixed.
SIPO is a party to these votes: as a DRep, it voted No on Copper, Yes on PFMS and Abstain on AURORA on November 5. Full disclosures are in Chapters 2, 5 and 10.
Executive Summary
- Three treasury actions: if every non-voter voted Yes, the ceilings would be 26.1% for Copper, 52.5% for AURORA and 62.5% for PFMS. PFMS, which could still reach the threshold on last week’s numbers (70.5%), has moved to the side that cannot. The Constitutional Committee cast a third “constitutional” vote on PFMS on November 10.
- Catalyst’s 21 million ADA: the treasury in Epoch 667 stands at 1,423,162,698 ADA, up about 26.69 million ADA from the previous epoch. Intersect announced the return on November 10; together with October’s return, it has returned 21,115,172 ADA.
- The next requests are not on chain yet: neither Intersect’s CEBP info action for the 2027 budget (target: November 10) nor the Cardano Foundation’s Global Events 2027 has been submitted. A Foundation forum post says it goes “on-chain next week.”
- Midnight’s Ledger 9: the release notes for ledger 9.1.0.1 call it a “security patch release” and disclose after the fact that it went to node operators on November 3. There is no mention of exploitation or losses. Preprod also moved to Ledger 9 on November 9, so all three public networks now run the same versions.
- Around Midnight: a release candidate of node 2.1.200, a draft MIP for staking NIGHT with Cardano pools, and a new indexer advisory (availability only) were published.
- cardano-node 11.2.1: published as a pre-release in the early hours of November 11 JST. The notes say it is “not yet recommended for use on mainnet,” and the recommended version is still 11.1.3.
- The Dijkstra schedule: Intersect’s Upgrade Bulletin #42 expected a mainnet-ready 11.2.1 and the sixth draft of the constitution “later this week,” but neither had appeared by the morning of November 14. The TSC will review how to switch Leios off on November 18.
- Node diversity: according to Intersect, four node implementations have now produced mainnet blocks. The Node Diversity Workshop was held in London on November 12–13.
- Network: Epoch 666 had 253,993 transactions, about 1.78 times the previous epoch. We have not identified the cause.
- SPO work: Ubuntu began general distribution of the kernel fix for CVE-2026-98432, and it is the same build SIPO installed in testing on November 3.
- Markets: ADA −9.16%, BTC −9.98%, ETH −13.50%, NIGHT +21.23%.
1. Market Pulse
These are morning fixed-point readings from November 7 to November 14. ADA, BTC and ETH are Hyperliquid perpetual futures prices.
| Asset | 11/7 | 11/14 | Week |
|---|---|---|---|
| ADA | $0.18525 | $0.16828 | −9.16% |
| BTC | $75,750.8 | $68,194.0 | −9.98% |
| ETH | $2,225.90 | $1,925.40 | −13.50% |
| NIGHT | $0.038599 | $0.046795 | +21.23% |
ADA, BTC and ETH fell by around 10%, while NIGHT alone rose. NIGHT at both ends is calculated from Cardano DEX prices, so the source is consistent. Priced in ADA, NIGHT moved from 0.208361 ADA to 0.278079 ADA, or +33.46%.
At epoch boundaries, ADA went from $0.18313272 (¥28.87) at 6:45 a.m. on November 6, when Epoch 666 began, to $0.17391629 (¥27.62) at 6:45 a.m. on November 11, when Epoch 667 began: −5.03%. The sampling times differ, so this does not match the weekly figure.
We do not link price moves to the events covered in this article.
The remaining network figures: at the boundary from Epoch 666 to 667, the staking ratio went from 56.77% to 56.72%, and delegators fell by 1,162 to 1,325,121.
2. Three Treasury Actions and the Arithmetic Short of 67%
Where the votes stand
These are DRep votes retrieved from Koios (Cardano’s public API) at 7:15 a.m. JST on November 14. The denominator is explicit Yes plus voted No, not voted and always No Confidence.
| Action | Amount | DRep Yes | Voted No | Committee (Yes−No) | Deadline |
|---|---|---|---|---|---|
| Copper | 22,000,000 ADA | 5 votes, 0.48% | 121 votes, 70.67% | 0−3 | 6:44:51 a.m. JST, November 16 |
| AURORA | 940,000 ADA | 14 votes, 3.99% | 74 votes, 44.06% | 0−3 | 6:44:51 a.m. JST, November 21 |
| PFMS | 9,600,000 ADA | 41 votes, 29.51% | 57 votes, 34.77% | 3−0 | 6:44:51 a.m. JST, November 21 |
Since last week, PFMS Yes rose from 37 votes (24.88%) to 41, and voted No rose from 43 votes (26.86%) to 57. Voted No on Copper went from 55.88% to 70.67%, and on AURORA from 36.43% to 44.06%. Each action needs 67% of DReps and two-thirds “constitutional” votes from the Constitutional Committee to pass.
Even if every non-voter says Yes
If delegation and the votes already cast stay unchanged, the ceiling if every non-voter voted Yes is as follows.
| Action | Ceiling last week (11/7) | Ceiling this week (11/14) |
|---|---|---|
| Copper | 41.1% | 26.1% |
| AURORA | 60.4% | 52.5% |
| PFMS | 70.5% | 62.5% |
Last week, PFMS would have reached 67% if 92% of non-voters had voted Yes. This week, even if all 1,561,063,820 ADA of non-voting power voted Yes, it would be 4.5 points short. Any votes needed to change sides would have to come from those already voting No.
Two things can move this arithmetic. DReps can change their votes until the deadline, and if delegators move their delegation, both the denominator and the votes move. What is written here is a line drawn from the numbers on the morning of November 14. An action that does not meet the conditions by its deadline “expires,” which is treated differently from being voted down.
The Committee’s fourth voter
At 2:38 a.m. JST on November 10, one Constitutional Committee member voted “constitutional” on PFMS and on the developer survey info action. That brings PFMS to three Committee Yes votes. The Committee has seven members, and two-thirds requires five.
The rationale says the member checked the document against the hash recorded on chain themselves, and then takes up one counterargument.
“A reviewer might argue that Article II.7.6 is not satisfied, because the proposal states that withdrawn funds ‘are held by the administrator’s multi-sig wallet address,’ while the on-chain destination is an ordinary key-hash stake address with no multisignature script.”
“We acknowledge that this argument has force: the custody the metadata describes is not the custody the chain records, and DReps are entitled to weigh that inaccuracy. We reject that view on these facts.”
Last week we noted that SIPO voted Yes on PFMS while asking for the “multisig” description to be corrected. The Committee’s rationale takes up the same discrepancy and finds that it does not make the action unconstitutional. As we wrote last week, on Copper and AURORA the Committee cannot reach two-thirds even if the remaining four members all vote Yes.
DRep rationales
Votes and rationales from Japanese DReps stood out this week.
- Yes (SASA_nagamaru, November 8): “PFMS builds on FMS’s existing operational record on Cardano mainnet,” while adding that “the annual target of 1.53 million transactions remains uncertain, and transaction count alone cannot establish value for money.”
- No (hix_coffeepool, November 9): “the Treasury bears the full development cost, while the state government contributes nothing to development.”
- No (Aichi/Tokai_DRep, November 9): “with the remaining Net Change Limit headroom now very limited, I believe Treasury priorities must be applied more conservatively,” adding, “My vote should not be interpreted as a rejection of the project’s merits.”
- No (Cerkoryn, November 8): presented an estimate that recovering the requested amount through transaction fees alone would take about 138 years.
Transaction figures differ by source. The Cardano Foundation’s November 13 post describes the first year with the police in Uttar Pradesh as “roughly 163,000 mainnet transactions.” Some DRep rationales cite figures from a different count.
On Copper, the large DRep Everstake voted No without a rationale at 0:56 a.m. JST on November 14.
SIPO’s three votes
These are SIPO’s own votes, so we write as a party to them. On November 5, SIPO voted No on Copper, Yes with expectations on PFMS and Abstain on AURORA, and has not changed those votes. The rationales are in the respective articles (SIPO DRep: No on the 22M ADA Copper strategic reserve withdrawal / SIPO DRep: Yes on the 9.6M ADA PFMS police evidence-management withdrawal / SIPO DRep: Abstain on the 940k ADA AURORA credit-market infrastructure withdrawal).
As of the morning of November 14, SIPO’s DRep holds about 117.26 million ADA from 431 delegations, about 2.5% of the PFMS denominator. The path to the deadlines is also summarized in our November 10 article (PFMS and AURORA treasury proposals close voting on November 21).
3. Catalyst’s 21 Million ADA Reaches the Treasury Balance
Last week’s check is now filled in
Last week we reported, from the on-chain record, that the 21 million ADA from a cancelled Catalyst milestone was sent as a donation to the treasury at 4:57 a.m. JST on November 7. Our check point was that it would show up in the balance only after the November 11 boundary.
In Koios’s Epoch 667 figures, the treasury went from 1,396,473,702 ADA to 1,423,162,698 ADA, +26,688,995 ADA. The 21 million ADA is included in this increase. The previous epoch’s increase was about 3.58 million ADA, and the remaining roughly 5.69 million ADA corresponds to the usual flows from fees and reserves.
Intersect’s announcement
At 6:57 p.m. JST on November 10, Intersect posted on its official X account:
“On November 6, Intersect returned a further 21M ada from the Catalyst 2025 budget held in our Treasury Reserve Smart Contract.”
“This brings the total Intersect has returned to the treasury to 21,115,172 ada, including 115,172 ada returned in October from a completed Product budget.”
The announcement’s “November 6” is the UTC date, which corresponds to early morning on November 7 in Japan. The reason matches the transaction metadata: because administration of Catalyst is moving from Input Output to the Cardano Foundation, the Fund 15 milestone under the existing scope was cancelled (Intersect returns 21M ADA of the Catalyst budget to the treasury).
What was cancelled is “Fund 15 under Input Output’s proposal.” When and with what budget the next fund will run under the Foundation is not stated in the announcement or the transaction. Neither the Foundation nor the official Catalyst account posted about it this week.
Withdrawing from the treasury requires a DRep vote, but returning funds takes a single transaction. The Net Change Limit allows 500 million ADA against the 457,395,629 ADA of withdrawals enacted since Epoch 613; we have not confirmed from official material how this return is treated in that calculation.
4. The Next Requests, Not Yet Submitted
CEBP has passed November 10 without submission
Intersect’s 2027 budget proposal, CEBP, set “November 10 as the target” for submitting its first info action. As of the morning of November 14, there is no on-chain submission and no announcement of a changed target. No new governance actions were submitted this week, and four remain pending.
Global Events 2027: “next week”
In the early hours of November 10 JST, the Cardano Foundation held its second DRep briefing on Global Events 2027. Laura Mattiucci, director of marketing and communications, said the Foundation would not exhibit in Nairobi in February if the proposal fails. A Foundation representative wrote on the forum that the proposal goes “on-chain next week,” and the request remains USD 4,999,155 (24,995,775 ada at an assumed USD 0.20 per ada) (Cardano Foundation’s events treasury proposal: no Nairobi booth if it fails).
Against the assumed USD 0.20 per ada, ADA stood at $0.16828 on the morning of November 14. How this gap will be reflected in the requested amount at submission has not been stated.
The developer survey info action
The developer survey info action has 10 DRep Yes votes (10.36%) and 47 abstentions, with two Committee Yes votes. Info actions are not ratified, and the deadline is 6:44:51 a.m. JST on December 1. SIPO’s DRep has not yet voted on this action.
5. Midnight Discloses What Ledger 9 Fixed
What the release notes say
Last week we reported that Midnight applied Ledger 9 to mainnet without going through Preprod, giving no more of a reason than “security fixes.” At 2:14 a.m. JST on November 8, the release notes for ledger 9.1.0.1 were published on GitHub.
“Ledger 9.1.0.1 is a security patch release on the ledger-9 line. It was released to node operators on 2026-11-03 and is already live on mainnet; its source and these notes are published after the fact.”
“It bounds the work an attacker can force during transaction pricing, decoding and well-formedness checks over shared storage nodes, closes several fee and block-limit bypasses in contract call transcripts, and rejects repeated entries in a transaction.”
The list of fixes includes more than ten advisory numbers. Examples include a problem where a few hundred bytes could force exponential work before fees were checked, and one where a contract could absorb surplus Dust credited by a registration while the registrant still received the full entitlement. There is no mention of exploitation or losses. The notes say no governance action was required and that the fix was handled by the node release.
On the node side, node-2.1.101 was published on GitHub at 10:21 p.m. JST on November 8, resolving the point we noted last week that no matching tag could be found. The notes explain that Dust state is reset at the hard fork and that wallets must reset their local Dust state at the fork block (Midnight node 2.1.101 requires TLS for db-sync connections).
All three networks aligned
| Network | Migration | Method |
|---|---|---|
| Mainnet | November 6 | In place. Balances, contracts and history carried over |
| Preview | November 7 | Relaunched as a new chain |
| Preprod | November 9 (block 3,348,434) | In place. History continues |
The official support matrix states that “Mainnet, Preview, and Preprod all run ledger 9 with the same versions,” with ledger 9.1.0.1, node 2.1.101, indexer 4.4.101 and Midnight.js 5.0.0. The situation we described last week, where Preprod, meant to test ahead of production, was one ledger behind production, was resolved within three days (Midnight’s Preprod moves to Ledger 9 with its history intact).
Two pieces of indexer news
Indexer 4.4.101 (7:17 a.m. JST on November 9) fixed three issues: contract balances holding shielded tokens or Dust halted block indexing, SPO registrations halted SPO indexing, and unverified SPO registrations could claim a pool’s identity (Midnight Indexer 4.4.101 fixes three security issues).
At 6:16 a.m. JST on November 14, a new indexer advisory was published with “high” severity. A single unauthenticated request of about 100 bytes to the resolvers that return per-epoch SPO data could pin a database connection for a long time or drive the API toward running out of memory. The advisory states that it is “availability-only, no theft, forgery, or disclosure.”
What Ledger 9 added, and what it did not
Ledger 9 added contract-to-contract calls, contract event emission, ECDSA and Keccak-256 support, and a new version of the zero-knowledge intermediate representation. Midnight’s official account highlighted the Keccak-256 and ECDSA support again on November 9. The bridge that moves cNIGHT from Cardano to Midnight is built into the node but stays inert until governance configures it (Midnight’s Ledger 9: four new features and a NIGHT bridge not yet enabled).
6. Around Midnight
A release candidate for node 2.1.200
node-2.1.200-rc.1 (November 11) is a release candidate that raises the limit on the number of nodes a single transaction can declare from 1,024 to 8,192. In 2.1.101, a limit that caused the new runtime to refuse even transactions the chain had already accepted remained as a known issue “with no workaround.” The limit moves into runtime storage, so it can be changed without replacing the runtime. Switching requires a federated authority motion (Midnight node 2.1.200 candidate raises the transaction node limit to 8,192).
A draft for staking NIGHT with Cardano pools
At 2:42 a.m. JST on November 12, a draft titled “NIGHT Staking on Cardano” was opened in Midnight’s improvement proposal repository.
“Today only ADA stake decides which Cardano stake pools produce Midnight blocks. This MIP makes NIGHT count too.”
Under the design, a holder locks cNIGHT on Cardano for a pool, and Midnight counts it with the pool’s ADA stake when selecting each epoch’s committee. Unlocking requires a wait of four Cardano epochs, and locked cNIGHT generates no Dust. The reward split is in a separate proposal, and the draft says “four questions are open.” It has not been merged or adopted.
In the same week, MIP-0033, which delegates scoped permissions over custody accounts, was added to the repository (Midnight’s MIP-0033 draft: scoped delegation of contract account permissions).
Disclosure: SIPO is a Cardano SPO and a member of Midnight’s Nightforce ambassadors. The NIGHT staking draft bears directly on how SIPO’s pools could be selected to produce Midnight blocks.
Users and connectors
- Monument Bank: at 6:45 p.m. JST on November 11, Fahmi Syed of the Midnight Foundation and Mintoo Bhandari, founder of UK-based Monument Bank, discussed tokenized deposits at Blockworks’ Digital Asset Summit in London. Midnight’s official account posted, “Banks need more than access to blockchain infrastructure. They need control over what happens on it” (Midnight and UK’s Monument Bank discuss tokenized deposits in London).
- NightKit: on November 12, 1AM, which builds a wallet for Midnight, released a connection kit in testnet beta that lets users open a Midnight account from wallets they already have, such as MetaMask or Phantom (1AM previews a kit for entering Midnight with existing wallets).
- Wallets catching up: Lace added Ledger 9 support in browser version 2.5.1 (Lace 2.5.1 supports Midnight’s Ledger 9). GeroWallet announced on November 8 that NIGHT transfers and Dust registration are unavailable until its update is complete (GeroWallet pauses NIGHT transfers until Ledger 9 support).
- Partners: the Midnight Foundation welcomed Blockenfy, which tokenizes real-world assets, as an ecosystem partner (Midnight Foundation names Blockenfy an ecosystem partner), and added Ventari as an adviser to Build Club (Midnight’s Build Club adds Ventari as token-launch adviser).
- Nightmode: Sig Network wrote on November 10 that “Ledger 9 is the first version of Midnight that can run private Ethereum apps,” and described mainnet as being at the “last round of pre-launch checks.”
- Hoskinson: SIPO summarized his AMA published on November 8, in which he described Midnight as the biggest project on Cardano (Hoskinson’s AMA: Nightstream to market in 2028).
Third-party posts cite daily and cumulative Midnight transaction counts, but we have not been able to confirm any official announcement, so we do not use them. WingRiders announced that the final round of NIGHT distribution to liquidity providers would take place at 9:00 a.m. JST on November 14 (WingRiders schedules final NIGHT distribution to LPs for November 14).
7. cardano-node 11.2.1 Is a Pre-Release
What changed
cardano-node 11.2.1 was published as a pre-release on GitHub at 0:27 a.m. JST on November 11. The release notes open:
“Node version 11.2.1 is a pre-release version of cardano-node that is not yet recommended for use on mainnet. It is a maintenance release on top of 11.2.0.”
| Item | Change |
|---|---|
| Memory | Writing a ledger snapshot no longer temporarily grows live memory by about the snapshot’s size |
| Snapshots while syncing | Written as soon as requested until the node first catches up |
| LSM | The on-disk UTxO backend confirmed to meet performance requirements for block production |
| Maximum snapshot delay | 1 hour on all networks (down from 6 hours on mainnet and preprod) |
| Header protocol version | From 11.1 to 11.3 |
The notes say “there are no breaking changes for node operators in 11.2.1.” The performance report says that on a cluster of 52 block-producing nodes, memory use under load (kernel RSS) fell by 1.16 GiB, or 14%. The report notes that it does not directly recreate mainnet operating conditions (cardano-node 11.2.1 pre-release removes memory growth during snapshots).
“Later this week” and the state on November 14
Intersect’s Upgrade Bulletin #42 (5:47 a.m. JST on November 14) wrote that “Node 11.2.1 was given a Pre-Release on November 10, with the Mainnet-ready approval expected by the end of the week.” The Hard Fork Working Group minutes of November 10 also say “by the end of the week.”
As of 7 a.m. JST on November 14, 11.2.1 on GitHub still carries the pre-release flag, and the text still says “not yet recommended for use on mainnet.” The sign-off section shows all six roles in green, while the known-issues section is still awaiting entries. The latest version marked as recommended on GitHub is 11.1.3 from September 29.
The 11.2.1 release notes contain no entry described with the word “security.” The Bulletin describes it this way: “11.2.1 is not the hard fork-ready release, but an important step toward it.”
Disclosure: SIPO is an SPO running three pools, and updating to 11.2.1 and registering BLS voting keys for Dijkstra are SIPO’s own work.
8. The Dijkstra and Leios Schedule
11.3, then 12.0
Bulletin #42 put 11.3, which includes Linear Leios and Fair Min Fees (CIP-23), “in the coming weeks,” and continued:
“Provided no serious issues are identified, 11.3 could potentially be promoted to Node 12.0, forming the hard fork-ready candidate.”
On the point we noted last week, that CIP-23 was not yet in 11.2, the Dijkstra overview page has been updated to reflect the full inclusion of CIP-23 in the planned hard fork scope. The minutes say DijkstraNet is expected to move to 11.2.1, and SanchoNet is expected to fork into the Dijkstra era soon.
A safety concern and a cost estimate
The Bulletin reported that “a previously identified concern about Linear Leios affecting Praos safety under adversarial conditions can no longer be reproduced by the Leios team following implementation adjustments.” It also says appropriate benchmarks are needed to assess the costs and benefits of Linear Leios for mainnet.
On the ledger side, the ledger can now validate and apply Leios endorser blocks (additional blocks that carry transactions). Pool updates that change only BLS keys no longer require owner signatures (Cardano’s ledger now validates and applies Leios endorser blocks).
The sixth constitution draft and November 18
The Bulletin and the minutes said the sixth draft of constitutional amendment CAP-12 was expected “later this week,” but as of the morning of November 14, the latest version on the CAP portal is still the fifth, from October 30. On the target we mentioned last week of submitting “by November 25,” this week’s Bulletin and minutes neither confirm nor change it. We could not find a public record of the outcome of the November 12 CAP review.
On November 10, TSC member Kevin Hammond proposed additional guardrails in the CAP-12 comments: for example, maxEndorserBlockTxsSize must not be raised again within 18 epochs of the previous increase, and an action to raise it must not be submitted until pools holding at least 90% of active stake have registered BLS keys. He stated that “the numbers are placeholders.” In the same comment, citing a straw-man estimate, he wrote that SPO costs could be up to about USD 3 million for a 10x–15x throughput increase, “which is not sustainable from fee income.” The TSC’s decision on how to switch Leios off is scheduled for November 18.
SIPO has commented in the CAP discussions. The debate over SPO costs and guardrails bears directly on the operating conditions of SIPO, which runs three pools.
9. Node Diversity: Four Implementations on Mainnet
According to Bulletin #42, four node implementations have now produced mainnet blocks.
| Implementation | Language |
|---|---|
| cardano-node | Haskell |
| Amaru | Rust |
| Dingo | Go |
| cardano-bean | (not stated in the Bulletin) |
The Bulletin says Amaru “has produced 200+ blocks on Mainnet,” up from 57 in the November 10 minutes. These are Intersect’s figures, and SIPO has not checked the block count on chain. Amaru’s “Minimum Viable Block producer” milestone has moved from November 12 to November 19 and remains open. Version v10.11.20261112, released November 13, adds a command for inspecting a pool’s block production schedule.
The Node Diversity Workshop, organized by the Amaru team, took place in London on November 12–13. Cardano’s official account said teams were working on mainnet readiness, shared testing standards and network upgrades (Daily Intel 11/14). No written record of agreements has been published yet. Dingo, written in Go, has published that its mainnet database in API mode is about 941 GiB (Dingo’s API mode: about 941 GiB of mainnet data).
10. Who Holds Your Voice
Check your DRep
On November 9, Intersect’s Civics Committee asked on X: “This November, Intersect Civics Committee is asking ADA holders to take a few minutes to check in on their DRep, review recent votes, and active DReps.” It added, “Keep your DRep or choose a new one. The choice is yours” (Intersect Civics calls on holders to “Check your DRep”). EMURGO’s official account’s latest post is still from October 28, and there is no announcement changing the November 30 deregistration of the EMURGO and Yoroi DReps.
A format for holders to record their views
CIP-204, a common format for ADA holders to record Yes, No or Abstain on governance actions, has been merged into the CIP repository. DReps still cast the formal votes, but holders now have a shared way to record their views on chain without changing their delegation (CIP-204 merged: a common format for ADA holders to record their views).
Disclosure: SIPO is a DRep and has a direct interest in delegators reviewing their choices. As of the morning of November 14, it holds about 117.26 million ADA from 431 delegations (about 118.88 million ADA and 430 delegations as of November 7, last week).
11. SIPO’s Three Pools and the Kernel Fix’s General Release
This section is SIPO’s own record.
CVE-2026-98432
Ubuntu began general distribution of kernels that fix Linux kernel vulnerability CVE-2026-98432, and on the morning of November 12, 6.8.0-149.149 for 24.04 LTS reached the security updates. Ubuntu’s distribution records show that it is the same build SIPO installed in its testing stage on November 3. For operators who were waiting for general release, this is the signal to update and reboot (Ubuntu releases the kernel fix for CVE-2026-98432).
Pool figures
In Epoch 666, the three pools produced 116 blocks: SIPO 58, SIPO2 34 and SIPO3 24 (142 in Epoch 665).
| Pool | Live stake at end of Epoch 666 | Delegators | Ratio to k=1000 saturation |
|---|---|---|---|
| SIPO | 54,900,958 ada | 1,097 | 1.491x |
| SIPO2 | 35,535,977 ada | 477 | 0.965 |
| SIPO3 | 23,940,451 ada | 539 | 0.650 |
A mechanical estimate dividing Epoch 667 circulation of 36,816,370,531 ada by k gives a saturation point of about 73,632,741 ada at k=500 (current) and about 36,816,371 ada at k=1000. The three pools charge a 3.9% margin and a 340 ada fixed cost, and have produced 48,663 blocks in total.
12. Network: Epoch 666 Had 253,993 Transactions
| Epoch | Period (JST) | Blocks | Transactions | Per block | Fees |
|---|---|---|---|---|---|
| 664 | 10/27 6:44 – 11/1 6:44 | 21,225 | 138,147 | 6.51 | 42,320.14 ada |
| 665 | 11/1 6:44 – 11/6 6:44 | 21,565 | 142,991 | 6.63 | 41,673.49 ada |
| 666 | 11/6 6:44 – 11/11 6:44 | 21,161 | 253,993 | 12.00 | 60,379.81 ada |
Transactions in Epoch 666 rose 77.63% from the previous epoch, and fees rose 44.89%. In the daily values compiled in SIPO’s Epoch 666 article, November 8 had 54,126 transactions, and the share of transactions using scripts was 11.75%. Working back from that share, the increase came from transactions that do not use scripts (Epochal Days 666). We have not identified what drove the increase.
On the rewards side, total rewards for Epoch 665 were finalized at 6,250,546 ada, up 1.69% from 6,146,940 ada in Epoch 664. Epoch 667 had 73,001 transactions as of 7:15 a.m. JST on November 14.
13. Tools and Wallets
- Daedalus 11.6.2 (November 10): fixes a problem on Windows where the update installer kept running after Daedalus quit (Daedalus 11.6.2 fixes updates failing on Windows).
- Lace Android 2.5.2 (November 12): can now cover shortfalls in a send from staking rewards, and strengthens checks against signing dApp transactions for mainnet while on a testnet, or vice versa (Lace Android 2.5.2 can use staking rewards when sending).
- Hydra: a change raising the outputs a single Head can hold from 4,095 to 32,767 has been merged, and the next release will be a breaking change. No new version was released in the period.
- cardano-init 0.4.0: the developer experience team added six templates, including Plutarch and Pebble (cardano-init 0.4.0 adds six templates including Plutarch and Pebble).
- IBC: Cosmos and the Interchain Foundation announced that IBC will be contributed to the Linux Foundation’s LF Decentralized Trust, and the Cardano Foundation is among the supporting organizations (Cardano Foundation supports IBC joining the Linux Foundation).
14. DeFi
- TVL: on DefiLlama’s daily data, Cardano’s DeFi TVL was USD 49.58 million on November 9, about 29% of the USD 169.80 million at the start of the year (Cardano’s DeFi TVL falls below USD 50 million).
- October DEX activity: SundaeSwap’s monthly report puts October DEX volume at USD 65.7 million (+14%) on its own count.
- Aggregators: SteelSwap took first place in seven-day volume on DefiLlama (SteelSwap ranks first in weekly volume among Cardano DEX aggregators), and Minswap Aggregator added SundaeSwap V4 to its routing (Minswap Aggregator adds SundaeSwap V4 routing).
- SundaeSwap: rebuilt its trading screens and now shows profit and loss for each LP position, including impermanent loss (SundaeSwap’s new interface shows LPs’ net profit and loss).
- Strike: added Aave, Ethena and Uniswap perpetuals with up to 20x leverage (Strike adds three DeFi perpetuals with up to 20x leverage).
- Indigo: introduced Indigo Prime, funded through PRIME, in an X article.
This week, within what we could check, no protocol’s official account reported a new incident.
SIPO operates a scooper for SundaeSwap v4.
15. Key and Wallet Warnings
- worse_query: on November 10, Binance warned that an iPhone vulnerability called “worse_query” lets a malicious app read other apps’ files. VESPR explained in the early hours of November 11 JST that “Your VESPR recovery phrase is NOT exposed” (iOS worse_query: VESPR denies exposure of recovery phrases).
- SecondFi: on November 12, launched an asset recovery tool for wallets affected by the June incident. It writes, “There are no recovery fees, and SecondFi will never contact you first to start a recovery.”
- Binance: phased reopening of withdrawals continues, but the text of its posts up to the morning of November 14 does not mention ADA or NIGHT. The final report has not been published.
16. Risk Dimensions
- Treasury (consecutive expiries). If the three actions do not meet the conditions by their deadlines, they will expire one after another. Only votes switching from No to Yes and shifts in delegation can change the arithmetic.
- Treasury (the next requests). CEBP and Global Events 2027 have not been submitted, and Global Events is priced on an assumed USD 0.20 per ada. Submission timing and how the amount is handled will inform DReps’ decisions.
- Midnight (after-the-fact disclosure). The content of the fixes has been published, but whether they were exploited is not stated. Publication of the individual advisory pages remains a point to check.
- Midnight (operations). The new indexer advisory is an availability issue, and operators running public indexers need to decide on updates. The node limit change takes effect only after a motion.
- Operations (11.2.1). The pre-release status continues while mainnet-ready approval was expected “by the end of the week.” The new 11.2 configuration files cannot be read by nodes before 11.2, so the order of upgrading the node binary first does not change.
- The Dijkstra schedule. 11.3, the sixth constitution draft and the TSC decision on November 18 fall close together. This week’s material does not mention the November 25 submission target.
- Delegation. Wallets still delegated to the EMURGO and Yoroi DReps will be unable to withdraw rewards after November 30.
- Keys. Caution is needed around the iPhone vulnerability and messages posing as recovery offers.
17. What to Watch Next Week
- Mainnet-ready approval of cardano-node 11.2.1 — whether the pre-release flag is removed and the known-issues section is filled in. Check the release page of
IntersectMBO/cardano-node. - Intersect Weekly Update #137 — not published as of the morning of November 14. Check Intersect’s news page.
- Copper deadline — 6:44:51 a.m. JST on November 16, the Epoch 668 boundary. Check the action’s page on gov.tools.
- Final Epoch 667 figures — at the same boundary, Epoch 667 transaction counts and the three pools’ block counts are finalized. Check Koios epoch information.
- Submission of Global Events 2027 and CEBP — the Foundation’s post says “next week.” Check GovTool and the Foundation’s forum post.
- TSC review — November 18, on how to switch Leios off. Check the CAP-12 comments.
- Sixth draft of CAP-12 — check CAP-12 on the CAP portal.
- Amaru milestone — “Minimum Viable Block producer” is due November 19. Check the milestone list of
pragma-org/amaru. - PFMS and AURORA deadlines — 6:44:51 a.m. JST on November 21, the Epoch 669 boundary.
- Midnight node 2.1.200 — whether it moves from release candidate to release, and whether a motion is announced. Check the release page of
midnightntwrk/midnight-node. - The NIGHT staking draft — discussion of its four open questions. Check PR #419 in
midnightntwrk/midnight-improvement-proposals. - Deregistration of the EMURGO and Yoroi DReps — November 30. Any postponement can be checked on @emurgo_io on X.
- Developer survey info action deadline — 6:44:51 a.m. JST on December 1.
Summary
This week, if delegation and votes stay as they are, Cardano’s three treasury actions cannot reach 67% even if every non-voter votes Yes. PFMS, which could still reach the threshold on last week’s numbers, has moved to the side that cannot, with voted No now outweighing Yes. The Committee’s rationale acknowledged the discrepancy between PFMS’s metadata and its actual receiving address before finding it constitutional.
On the treasury side, the 21 million ADA from the cancelled Catalyst budget appeared in the balance, while CEBP and Global Events, which are expected next, are not yet on chain. Debate over withdrawals, money flowing back, and the next requests all lined up in the same week.
Midnight disclosed in its release notes the content of fixes it had not described last week, and Preprod caught up to Ledger 9. On the Cardano side, 11.2.1 reached the weekend still as a pre-release, with 11.3 and the sixth constitution draft still to come.
Next week, the first thing we will check is how the Copper action was handled at the 6:44:51 a.m. JST boundary on November 16, on its page on gov.tools.
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, DRep delegation): https://api.koios.rest/api/v1
- Cardano governance actions: https://gov.tools/governance_actions
- 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 PFMS post (November 13): https://x.com/Cardano_CF/status/2121205190049075497
- Intersect’s Catalyst return announcement: https://x.com/IntersectMBO/status/2120093587094348130
- Catalyst return transaction (November 7): https://adastat.net/transactions/ce63f0c11391080ea89d50f84bd27f13ce56a591ea0cbb6b89ed097e3a4419d4
- Global Events 2027 proposal (forum): https://forum.cardano.org/t/cardano-global-events-2027-a-proposal-for-the-ecosystem/157729
- Intersect’s CEBP proposal: https://www.intersectmbo.org/news/a-more-strategic-2027-cardano-budget
- Midnight ledger 9.1.0.1: https://github.com/midnightntwrk/midnight-ledger/releases/tag/ledger-9.1.0.1
- Midnight node 2.1.101: https://github.com/midnightntwrk/midnight-node/releases/tag/node-2.1.101
- Midnight node 2.1.200-rc.1: https://github.com/midnightntwrk/midnight-node/releases/tag/node-2.1.200-rc.1
- Midnight indexer 4.4.101: https://github.com/midnightntwrk/midnight-indexer/releases/tag/v4.4.101
- Midnight indexer advisory (November 14): https://github.com/midnightntwrk/midnight-indexer/security/advisories/GHSA-6746-qxvv-3hwg
- Midnight support matrix: https://docs.midnight.network/relnotes/support-matrix
- NIGHT Staking on Cardano draft: https://github.com/midnightntwrk/midnight-improvement-proposals/pull/419
- Midnight’s official post on ECDSA and Keccak-256: https://x.com/MidnightNtwrk/status/2119790523082817934
- Midnight’s official post from DAS London: https://x.com/MidnightNtwrk/status/2120474786405232946
- 1AM’s NightKit announcement: https://x.com/OneAmXYZ/status/2120736549411475764
- Sig Network’s post: https://x.com/Sig_Network/status/2119840283642765655
- cardano-node 11.2.1: https://github.com/IntersectMBO/cardano-node/releases/tag/11.2.1
- cardano-node 11.2.1 performance report: https://updates.cardano.intersectmbo.org/reports/2026-11-performance-11.2.1/
- Intersect’s Upgrade Bulletin #42: https://x.com/IntersectMBO/status/2121344312189522298
- Hard Fork Working Group minutes (November 10): https://cardanoupgrades.docs.intersectmbo.org/general/hard-fork-working-group-meeting-minutes/10th-november-2026
- CAP-12 (CAP portal): https://cap-portal-api.onrender.com/proposals/12
- Input Output weekly development report (November 13): https://www.essentialcardano.io/development-update/weekly-development-report-2026-11-13
- Ledger team update (November 11): https://updates.cardano.intersectmbo.org/2026-11-11-ledger
- Amaru v10.11.20261112: https://github.com/pragma-org/amaru/releases/tag/v10.11.20261112
- Amaru milestone: https://github.com/pragma-org/amaru/milestone/25
- Cardano’s official post on the Node Diversity Workshop: https://x.com/Cardano/status/2121198399085003207
- Intersect Civics’ Check your DRep: https://x.com/IntersectCIVICS/status/2119717151628026197
- EMURGO’s DRep announcement: https://x.com/emurgo_io/status/2115299422850683118
- Ubuntu’s CVE-2026-98432 page: https://ubuntu.com/security/CVE-2026-98432
- Daedalus 11.6.2: https://github.com/input-output-hk/daedalus/releases/tag/11.6.2
- Lace Android 2.5.2: https://github.com/input-output-hk/lace/releases/tag/lace-android%402.5.2
- Lace browser 2.5.1: https://github.com/input-output-hk/lace/releases/tag/lace-extension%402.5.1
- Cardano DeFi TVL: https://defillama.com/chain/Cardano
- SundaeSwap monthly report: https://x.com/SundaeSwap/status/2120187069465325990
- Indigo Prime article: https://x.com/Indigo_protocol/status/2120201200671076689
- VESPR’s explanation: https://x.com/vesprwallet/status/2120216166430023756
- SecondFi’s recovery tool: https://x.com/secondfiapp/status/2120702768029827301
- Binance’s withdrawal reopening update: https://x.com/binance/status/2119655363385659500
- Morning fixed-point values (ADA / BTC / ETH are Hyperliquid perpetual futures prices): https://app.hyperliquid.xyz
- ADA at epoch boundaries: https://www.coingecko.com
- Weekly Brief #31: https://sipo.tokyo/language/en/weekly-brief-31-en/
Transparency Notes
- Votes on the three treasury actions: values retrieved from Koios at 7:15 a.m. JST on November 14. The denominator is explicit Yes plus the power that counts as No (voted No, not voted, and always No Confidence of 130,588,301 ada): 4,001,345,891 ada for Copper, 3,758,036,571 ada for AURORA and 4,735,763,329 ada for PFMS. The Yes rate is Yes ÷ denominator, and the voted-No share is voted No ÷ denominator (Copper 2,827,572,706 ÷ 4,001,345,891 = 70.67%, AURORA 1,655,850,369 ÷ 3,758,036,571 = 44.06%, PFMS 1,646,492,255 ÷ 4,735,763,329 = 34.77%). The No rate returned by the public API includes non-voters and always No Confidence, so it is not used in the text. Abstentions are excluded from the denominator.
- Ceiling if non-voters voted Yes: arithmetic that assumes delegation and votes already cast are unchanged. Copper (19,230,710 + 1,023,954,174) ÷ 4,001,345,891 = 26.1%, AURORA (149,764,388 + 1,821,833,514) ÷ 3,758,036,571 = 52.5%, PFMS (1,397,618,954 + 1,561,063,820) ÷ 4,735,763,329 = 62.5%. This is not a forecast. Last week’s ceilings (Copper 41.1%, AURORA 60.4%, PFMS 70.5%) are values as of 9:30 a.m. JST on November 7.
- Committee votes: from the Koios record. Committee members’ names are not given in the text. Quotations from the rationale are from the English original.
- DRep rationales: quoted from the documents each DRep attached to their vote. Names are the display names registered by each DRep.
- SIPO’s DRep delegation: values retrieved from Koios at 7:19 a.m. JST on November 14 (117,263,931 ada, 431 delegations). The share of the PFMS denominator is 117,263,931 ÷ 4,735,763,329 = 2.48%.
- Catalyst’s 21,000,000 ada: the treasury change is the difference between 1,396,473,702.51 ada in Epoch 666 and 1,423,162,697.98 ada in Epoch 667 (+26,688,995.47 ada). Describing the difference from the previous epoch’s increase (+3,576,727 ada) as “usual flows” is an arithmetic explanation; we did not verify the breakdown item by item. The transaction time is 19:57:07 UTC on November 6, 2026 = 4:57:07 a.m. JST on November 7.
- cardano-node 11.2.1: checked against GitHub release information at around 7 a.m. JST on November 14. The release notes contain no entry described with the word “security,” so we do not call it a “security fix.” The memory reduction is from the performance report, which itself states that it does not recreate mainnet conditions.
- Midnight ledger 9.1.0.1: quotations are from the English original of the release notes. There is no mention of exploitation or losses. We have not checked whether the individual pages for the listed advisories are published.
- Amaru block counts: as stated in Intersect’s Bulletin #42 and the minutes. Not checked against the on-chain block count.
- Epoch 666 transactions: counts and fees are from Koios epoch information; daily values are from SIPO’s Epoch 666 article (Dune values). We have not identified the cause.
- Saturation estimate: a mechanical estimate dividing on-chain circulation of 36,816,370,531 ada in Epoch 667 by k. SIPO’s three pool values are live stake taken just after the end of Epoch 666.
- Market sampling times: the November 7 values are from the 6:35:02 a.m. morning reading and the November 14 values from the 6:35:09 a.m. reading. ADA at epoch boundaries (−5.03%) uses CoinGecko values at the boundary times.
- SIPO’s interests: the text discloses that on the three treasury actions SIPO is a party, having voted No on Copper, Yes on PFMS and Abstain on AURORA; that it has not yet voted on the developer survey info action; that for Midnight it is a member of the Nightforce ambassadors and an SPO whose pool selection would be affected by the NIGHT staking draft; that for node 11.2.1 and Dijkstra updating and registering BLS voting keys are SIPO’s own work; that for CAP it has posted public comments; that for delegation it is a DRep holding about 117.26 million ADA from 431 delegations; that for its pools the three pools charge a 3.9% margin and a 340 ada fixed cost, and pool one sits above the k=1000 saturation point; and that for SundaeSwap it operates a v4 scooper.
- What we did not write: forecasts of whether each action will pass, speculation about why each DRep or Committee member voted as they did, the cause of the Epoch 666 transaction increase, daily and cumulative Midnight transaction counts (no official announcement), third-party statements about the timing of Monument Bank’s plans, new remarks from Hoskinson’s streams (no verbatim record), the amount of delegation remaining with the EMURGO and Yoroi DReps (not verified), and Binance reopening ADA and NIGHT withdrawals (not confirmed in text).
- Price and events: not linked.
This is not investment advice. For information and research purposes only.
