The governance action to pay 9.6 million ADA from the Cardano treasury for PFMS, a police evidence-management system in India, expired without passing at the Epoch 669 boundary at 6:44:51 a.m. JST on November 21. The Constitutional Committee’s fifth “constitutional” vote arrived four hours before the deadline, but DRep (delegated representative) support was 41.59%, short of the 67% required.
AURORA, the shared infrastructure for lending markets, expired at the same boundary, and the Copper strategic reserve had already expired on November 16. All three treasury actions we followed last week have closed without moving any funds. In their place, the Cardano Foundation’s Global Events 2027 (24,995,775 ADA) and Mesh SDK maintenance funding (600,000 ADA) went on chain in the early hours of November 17 JST. On Midnight, the UK’s Monument Bank began offering tokenised deposits.
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. It has not yet voted on the two new actions or on the developer survey. Full disclosures are in Chapters 2, 3 and 12.
Executive Summary
- All three treasury actions expired: PFMS ended with 41.59% DRep Yes (56 votes) and 40.13% voted No (72 votes), with the committee at 5 Yes, 0 No. AURORA had 4.36% DRep Yes and 5 committee No votes. Copper expired on November 16 with Yes at 0.50%. The funds of expired actions stay in the treasury.
- Committee rationales: a rationale against AURORA pointed out that the metadata URL pointing to the full proposal sits in a location that can be edited. One rationale in favour of PFMS says it confirmed the receiving account is not delegated to a pool and is set to “always abstain.”
- Two new requests: the Cardano Foundation’s Global Events 2027 and Mesh SDK maintenance were submitted early on November 17 JST, and both have a deadline of 6:44:51 a.m. JST on December 21. The receiving stake address for Global Events is the same as the one for PFMS. Intersect’s CEBP info action for the 2027 budget has still not been submitted.
- Money returned to the treasury: Intersect announced that it returned 23,063,600 ADA from the Catalyst budget in two transactions, bringing its total to 23,178,772 ADA. We correct one point in last week’s breakdown of the treasury increase using this figure (Chapter 4).
- Monument Bank: the UK’s Monument Bank launched a tokenised 12-month fixed-term deposit paying 5.20% (AER) on Midnight. It says up to £250 million of client deposits will be represented in the first phase.
- Midnight infrastructure: a case study showed proof generation running in production on Google Cloud’s confidential computing, and MIP-0018, a standard for token names, was accepted 10–0. A High-severity advisory was published for midnight-node, with the fix already in 2.1.101, which is now running.
- cardano-node: 11.2.1 remains a pre-release. 11.2.2 and 11.2.3 exist only as tags on GitHub, with no release page yet. The recommended version for mainnet is still 11.1.3.
- The Dijkstra schedule: version 6 of the constitutional amendment CAP-12 has not been published, and the outcome of the TSC’s November 18 review has not been made public. The minutes say the constitution update action could be submitted “on 25th November” at the earliest.
- People and teams moving: Hydra development moves from Input Output to BlockPQR on December 1. Dingo, the node written in Go, reached its 100th mainnet block.
- Delegation and DeFi: EMURGO and Yoroi postponed the de-registration of their DReps to the end of December. The ADA-backed stablecoin DJED and its reserve token SHEN will wind down at 8:59 a.m. JST on January 1, 2027.
- Markets: ADA −16.40%, BTC −13.82%, ETH −16.12%, NIGHT −10.78%.
1. Market Pulse
These are morning fixed-point readings from November 14 to November 21. ADA, BTC and ETH are Hyperliquid perpetual futures prices; NIGHT is calculated from Cardano DEX prices.
| Asset | 11/14 | 11/21 | Week |
|---|---|---|---|
| ADA | $0.16828 | $0.14068 | −16.40% |
| BTC | $68,194.0 | $58,772.0 | −13.82% |
| ETH | $1,925.40 | $1,615.00 | −16.12% |
| NIGHT | $0.046795 | $0.041750 | −10.78% |
All four fell: ADA and ETH by around 16%, BTC by around 14% and NIGHT by around 11%. NIGHT at both ends comes from the same source. Priced in ADA, NIGHT moved from 0.278079 ADA to 0.296776 ADA, or +6.72%.
At epoch boundaries, ADA went from $0.15380160 (¥24.56) at 6:45 a.m. on November 16, when Epoch 668 began, to $0.14240288 (¥22.58) at 6:45 a.m. on November 21, when Epoch 669 began: −7.41%. 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.
At the start of Epoch 669, the staking ratio was 56.80% and there were 1,324,674 delegators (versus 56.72% and 1,325,121 at the start of Epoch 667, as reported last week).
2. All Three Treasury Actions Expire
The final votes
These figures were retrieved from Koios (Cardano’s public API) at 7:15 a.m. JST on November 21. The denominator is explicit Yes votes plus voted No, non-voters and always-no-confidence; abstentions are excluded.
| Action | Amount | Expired | DRep Yes | Voted No | Committee (Yes−No) |
|---|---|---|---|---|---|
| Copper | 22,000,000 ADA | 6:44:51 a.m., Nov 16 | 5 votes · 0.50% | 126 votes · 71.84% | 0−3 |
| AURORA | 940,000 ADA | 6:44:51 a.m., Nov 21 | 15 votes · 4.36% | 97 votes · 62.67% | 0−5 |
| PFMS | 9,600,000 ADA | 6:44:51 a.m., Nov 21 | 56 votes · 41.59% | 72 votes · 40.13% | 5−0 |
A treasury withdrawal passes only when it has both 67% of DReps and two-thirds of the Constitutional Committee (seven members), that is, five “constitutional” votes. An action that does not meet both conditions by its deadline epoch “expires,” and the funds stay in the treasury. The 100,000 ADA deposit paid at submission goes back to the proposer’s return address.
PFMS: the committee condition was met; DReps fell short
PFMS met the committee condition. To the three Yes votes it had as of last week, one more “constitutional” vote was added at 9:04 p.m. on November 20 and another at 2:58 a.m. on November 21, for a total of five.
Among DReps, Yes votes rose over the week from 41 (29.51%) to 56 (41.59%), an increase of about 412.88 million ADA in delegated stake. Voted No also rose, from 57 (34.77%) to 72 (40.13%). By vote count No was ahead; by delegated stake, Yes finished slightly ahead of voted No at the deadline.
At the end, about 664.93 million ADA (15.27% of the denominator) had not voted, and even if all of it had voted Yes, support would have been 56.86%. The situation we described last week, where the action could not reach the threshold even if every non-voter voted Yes, held to the end.
Committee rationales
The rationale for the “constitutional” vote at 2:58 a.m. on November 21 lists what it checked about the receiving account.
“the custody account has no SPO delegation and is set to always-abstain; the 9.6M ada withdrawal is denominated in ada and within the supplied Net Change Limit”
The same rationale also notes that one reviewer’s question was left undetermined.
“One reviewer’s Section 7(6) question on segregation of pending treasury funds from ordinary Foundation funds remained cannot_determine, but neither commingling nor an omitted mandatory disclosure was established.”
On AURORA, two members voted “unconstitutional” at the same two times. One rationale points out that the metadata URL pointing to the full proposal sits in a location that can be changed.
“The verified metadata makes the full proposal part of the funding request, but its hash fixes only a mutable link. Payment and refund terms can change without changing the metadata digest.”
AURORA’s metadata was placed at a URL pointing to the head of a GitHub branch. In the same week, on the CAP portal, CAP-9, which would remove the requirement that governance metadata be stored immutably, was revised to version 4.
DRep rationales
From votes cast with rationales this week, here is one on each side.
- Yes (Eternl DRep Committee, about 221 million ADA, November 20): “EDC votes YES, even if the proposal won’t make it.”
- No (Dave, about 78.9 million ADA, November 17): “I am voting NO because a single ask of 9.6 million ADA is simply too significant.”
On November 18, the Cardano Foundation’s official X account noted that the PFMS deadline was approaching and, citing a report from Trivolve Tech, wrote: “163,000 transactions in, @TrivolveTech reports cases can reach trial 29% faster.”
SIPO’s votes
These are SIPO’s own votes, so we record them as a party. On November 5, SIPO voted No on Copper, Yes on PFMS with stated expectations, and Abstain on AURORA, and did not change its votes before the deadlines (SIPO DRep: No on the 22 million ADA withdrawal for a strategic copper reserve / SIPO DRep: Yes on the 9.6 million ADA withdrawal for the PFMS police evidence system / SIPO DRep: Abstain on the 940,000 ADA withdrawal for AURORA). We covered Copper’s expiry in our November 16 article (Copper strategic reserve treasury action expires with 0.51% DRep support).
As of the morning of November 21, SIPO’s DRep has about 120.02 million ADA delegated from 438 delegators, about 2.76% of PFMS’s final denominator.
3. Two New Requests Go On Chain
Cardano Global Events 2027
The Cardano Foundation submitted its Global Events 2027 treasury withdrawal in a block at 12:15 a.m. JST on November 17. The abstract reads:
“The Cardano Foundation requests 24,995,775 ada (US$4,999,155 at an assumed rate of US$0.20 per ada) to run a single Cardano-branded presence at 12 industry conferences between January and December 2027, each with a side event, four of them hackathons”
“The Foundation will not charge for its own staff time and will make no profit from this proposal.”
Compared with the November 4 draft, the amount and the list of 12 conferences are unchanged, while new language was added, including a quarterly review of the dollar value of the ada received and a provision to scale back later events if the price falls (Cardano Foundation submits events treasury action, keeping the 1 ada = $0.20 rate). At the ADA price on the morning of November 21 ($0.14068), the request is worth about $3.52 million, roughly 70% of the assumed amount.
On custody, the proposal says:
“Funds withdrawn under this Treasury Withdrawal Action are held on an appropriately secured multi-signature address. While the key credential is single-signature on-chain, there are cryptographic processes in place to implement multi-signature controls operationally within the Foundation.”
According to on-chain records, the receiving stake address for this action is the same address that received PFMS’s withdrawal request.
Mesh SDK maintenance
Thirty-three minutes later, at 12:48 a.m., the team behind Mesh SDK, a development kit for Cardano, submitted an action requesting 600,000 ADA (50,000 ADA a month). It treats 2026 as the “reference year” and pays for a year of maintenance already done.
“This proposal bootstraps something Cardano doesn’t have yet: year-based Treasury funding for maintaining a core developer SDK.”
Payments require a wallet signed by three of four team members, and from 2027 the team plans quarterly public reports and payments (Mesh SDK requests 600,000 ADA from the treasury for 2026 maintenance).
Early votes and rationales
| Action | DRep Yes | Voted No | Abstain | Deadline |
|---|---|---|---|---|
| Global Events 2027 | 14 votes · 3.03% | 15 votes · 14.65% | 5 votes | 6:44:51 a.m. JST, Dec 21 |
| Mesh SDK | 20 votes · 13.55% | 4 votes · 0.02% | 4 votes | 6:44:51 a.m. JST, Dec 21 |
YUTA, a DRep with about 482.5 million ADA delegated, voted No on Global Events and Yes on Mesh at 11:11 p.m. on November 20. The Global Events rationale says: “In its AMA, the Foundation said it attended about 150 events this year and that events outside these twelve are paid from its own budget. So the question is not whether Cardano should be present at events.” The Mesh rationale says: “600,000 ada pays five people for one year and is about 0.04% of the treasury. The work is already done, so there is no delivery risk.”
On Global Events, SASA_nagamaru voted No, writing: “Before supporting a further allocation of approximately 25 million ADA, I need verifiable evidence connecting previous spending to adoption and real-world usage.” Chris of Straightpool voted Yes: “I vote YES, so Cardano is present throughout next year when the protocol makes significant progress.”
CEBP still not submitted
As of the morning of November 21, Intersect’s CEBP info action for the 2027 budget is still not on chain. The Global Events proposal says that if CEBP is approved, its amount will be deducted from the cap for the events area.
The withdrawal cap (Net Change Limit) is a 500 million ADA allowance against 457,395,629 ADA in withdrawals enacted since Epoch 613, leaving about 42.6 million ADA. This week’s two requests total about 25.6 million ADA.
SIPO’s DRep has not yet voted on Global Events 2027, Mesh SDK or the developer survey info action.
4. Money Returned to the Treasury, and a Correction to Last Week’s Breakdown
In its weekly update #137 on November 15, Intersect reported returning a total of 23,063,600 ADA from the Catalyst budget to the treasury in two transactions, on November 6 and November 10 (both UTC). At 12:19 a.m. JST on November 19, its official X account announced: “23,178,772 ada has now been returned to Cardano’s treasury through Intersect-administered contracts.” The figure includes 115,172 ADA returned in October from the product committee’s budget.
The second transaction, 2,063,600 ADA, returned the remaining milestones after the Catalyst operations contract with Input Output was ended by mutual agreement. In the on-chain record that SIPO checked, the transaction was recorded at 6:43 a.m. JST on November 11, at the end of Epoch 666 (Intersect’s returns to the treasury reach 23.17 million ADA).
We correct one point in last week’s issue. Last week we wrote that of the +26,688,995 ADA increase in the treasury in Epoch 667, 21 million ADA was the Catalyst return and the remaining roughly 5.69 million ADA was “the usual flow from fees and reserves.” In fact, that remainder included the second return of 2,063,600 ADA. The roughly 3.62 million ADA left after subtracting it is in line with this week’s increases in Epoch 668 (+3,552,713 ADA) and Epoch 669 (+3,604,349 ADA).
The treasury in Epoch 669 stands at 1,430,319,760 ADA. There were no donations to or withdrawals from the treasury in these two epochs.
5. The Debate over the Foundation’s Accountability
Early on November 16 JST, Cardano Foundation CEO Frederik Gregaard posted a long piece on X, “Cardano: Let’s Talk About It,” and 16 minutes later Charles Hoskinson quoted it in reply. The long post says:
“I welcome accountability. Every organization receiving or deploying significant resources within the ecosystem should be able to demonstrate the value it creates. That includes the Cardano Foundation.”
A line from Hoskinson’s quote post:
“Accountability is having a board made up of the community to hold you accountable as a community organization with community money.”
Both agree that accountability is needed: Gregaard frames it as demonstrating results, Hoskinson as how the board is chosen (Cardano Foundation CEO and Hoskinson trade views on what accountability means).
The Foundation held an AMA with its executive team on X on November 19 (16:00 CET). Early on November 20 JST, Hoskinson posted: “my main complaint is that they need a community-elected board, and they sidestepped it again.” We have not verified a primary record of the Foundation’s remarks for this article.
How the Foundation’s board is chosen, and how DRep votes are becoming the place where the Foundation’s requests are weighed, are covered in our November 17 Deep Dive (The Cardano Foundation board nobody can elect, and the treasury vote DReps hold). Global Events 2027 is the first Foundation request to go to a vote while this debate continues.
6. Midnight: Monument Bank’s Tokenised Deposits
Product terms
On November 17 (UK time), the UK bank Monument began offering a tokenised 12-month fixed-term deposit for individuals on Midnight. Midnight’s official blog writes:
“Up to £250 million of client deposits will be represented on Midnight in this opening phase.”
In a post at 2:13 a.m. JST on November 18, the Midnight Foundation wrote that Monument had become “the first UK bank to tokenize retail deposits on a public blockchain,” explaining that deposits are represented one-to-one in sterling while remaining held by Monument as standard fiat capital protected under the UK’s Financial Services Compensation Scheme (FSCS).
According to Monument’s product page, the product is called “Tokenised Saver,” with these terms (UK’s Monument Bank launches tokenised deposits on Midnight):
- 5.20% AER fixed for a 12-month term
- Open to existing customers who are 18 or older, UK resident and applying in a sole name
- Requires a combined deposit balance of at least £25,000, with up to £100,000 in this account
- No withdrawals or closure during the term (except within 14 days of opening)
- The product page states that it is not a crypto asset
How it works, and the Japan angle
According to Midnight’s announcement, the system has three layers: the customer app, the bank’s core systems, and Midnight. On the Midnight layer, shielded smart contracts mirror each deposit one-to-one in sterling and show that it is backed without revealing balances or customer identities.
In an interview published by NADA NEWS on November 19, Midnight Foundation’s Fahmi Syed said the Foundation had signed a memorandum of understanding (MOU) with a major Japanese payments company. The company was not named, and no service has started in Japan. The article reports that Japanese financial institutions are watching how Monument’s operation goes as they make their own decisions (Midnight Foundation head reveals MOU with a major Japanese payments company).
7. Midnight’s Infrastructure
Proof generation on confidential computing
In a Google Cloud case study, the Midnight Foundation disclosed that it has moved the computation that produces zero-knowledge proofs to Google Cloud’s Confidential Space and GKE Confidential Nodes and runs it in production. The case study notes that generating proofs on a user’s own device takes from several seconds to tens of seconds, and quotes chief technology advisor Ben Beckmann:
“Confidential Space gives us provable hardware confidentiality that unblocks mobile and enterprise adoption.”
Midnight’s official account described it as joint work with Google Cloud and BCW Group (Midnight’s proof generation goes live on Google Cloud confidential computing). On the side of making local proving faster, Hoskinson said on November 20 that he had implemented GPU support in the program that produces Midnight proofs, asking “if anyone wants to test it and benchmark.” The change is still a draft that has not been merged.
Advisories and client-side fixes
- midnight-node advisory (published 10:17 a.m. JST on November 14, severity High): an unauthenticated transaction submission could trigger heavy deserialization before any limit check, exhausting a node’s memory and stopping it. The advisory says “The transaction never enters a block (death precedes admission) — a direct service kill, not a chain halt,” and lists 1.0.4 as affected and 2.1.101 as patched. Version 2.1.101 was released on November 8 and is the version running on all three networks today.
- Indexer 4.3.800 (November 14): a release on the Ledger 8 line. Its notes say it “fixes two security issues” and that a reindex from genesis is required. It includes the fix for the availability advisory reported last week.
- Ledger 9.1.0.2 (November 16): the notes describe it as “a client-side patch release” that “does not change transaction validation, state hashes or anything a node computes,” fixing two ways in which wallets and DApps built transactions that the node then rejected. Midnight.js 5.0.1 also moved the Ledger 9 stack to final releases.
- Node 2.1.200: still at release candidate rc.2 as of the morning of November 21.
Standards and post-quantum work
Midnight improvement proposal MIP-0018, “On-Chain Token Metadata Emission,” was accepted after an editors’ vote on November 17 (10 in favour, 0 against). It is a shared format for a token-issuing contract to publish its own name, ticker and number of decimals as on-chain events (Midnight’s MIP-0018 accepted, a standard for showing token names on chain).
On November 18 (UTC), two post-quantum documents were merged: MPS-0050 (protecting the contents of shielded Zswap transfers) and MPS-0051 (signatures that authorise spending of unshielded outputs). Both define what must be protected before deciding on solutions (Midnight splits its post-quantum problems into two MPS documents on confidentiality and signatures). On November 19, an MIP for the ML-DSA-65 signature scheme and three more draft post-quantum MPS documents were also opened.
The draft for staking NIGHT with Cardano pools
The “NIGHT Staking on Cardano” draft we reported last week had its original PR closed on November 16, and the same author reopened it as PR #421 with the same title. The text says “A holder locks NIGHT on Cardano (cNIGHT) for a pool, and Midnight counts it with the pool’s ADA stake when it selects each epoch’s committee.” The four-Cardano-epoch wait to unlock and the fact that locked cNIGHT generates no DUST are unchanged. It has been neither merged nor accepted.
Disclosure: SIPO is a Cardano SPO and a member of Midnight’s Nightforce ambassador programme. This draft directly affects how SIPO’s pools could be selected to produce Midnight blocks.
8. Around Midnight
- North Star: North Star, a DEX on Midnight, announced on November 17 (UTC) that it is “officially live on Midnight mainnet.” The announcement does not say whether anyone can now create pools or whether audits are complete (Midnight DEX North Star officially goes live on mainnet).
- Pulse Pump: on November 20, the Midnight Foundation highlighted Pulse Pump, which Pulse built to let users issue and trade tokens on Midnight.
- LIGHTSOUT: a developer at ODATANO published code for a bridge between NEAR and Midnight with no operator and no special hardware. It is a prototype running on the NEAR testnet and Midnight’s preview network (ODATANO releases a test bridge between NEAR and Midnight).
- The CTO’s explainer: part two of a series by Midnight Foundation CTO Sebastien Guillemot explains how four components (note commitments, zero-knowledge proofs, nullifiers and viewing keys) protect shielded assets (Midnight CTO explains the four cryptographic components behind shielded assets).
- Cardano DEXs: according to DefiLlama, Cardano DEX volume on November 14 (UTC) was about $3.14 million, about 2.3 times the previous day. DexHunter, a DEX aggregator, said by its own count that more than 10 million ADA of the day’s trading was NIGHT (NIGHT trading lifts Cardano DEX volume to 2.3 times the previous day).
- December 15: in a November 17 video, Hoskinson said he would present a review of Midnight’s year and its 2027 plans on December 15, and on November 20 he posted: “Everyone ready for December 15th” (Hoskinson to present Midnight’s 2027 plans on December 15). Midnight’s official account has announced a special edition of its “After Midnight” broadcast at 17:00 UTC on November 24.
9. cardano-node 11.2.x; 11.1.3 Still Recommended
11.2.1 is still a pre-release
Last week we wrote that 11.2.1 remained a pre-release while mainnet approval was expected “by the end of the week.” As of 7 a.m. JST on November 21, 11.2.1 on GitHub still carries the pre-release label, and its text still says it is “not yet recommended for use on mainnet.” The latest version marked as recommended on GitHub is 11.1.3 from September 29.
Intersect’s weekly update #137 (November 15) says “Mainnet approval is expected shortly” and reports that with 11.2.1, LSM, which keeps the UTxO set on disk, is approved for use on block-producing nodes on all networks (Node 11.2.1 brings memory fixes and LSM approval for block producers).
11.2.2 and 11.2.3 exist only as tags
On GitHub, a tag for 11.2.2 was created at 7:24 p.m. on November 17 and one for 11.2.3 at 10:09 p.m. on November 19, but neither has a release page yet. The Hard Fork Working Group minutes of November 17 say:
“11.2.2 was delayed a bit due to the conformance issue discovered at the Node diversity workshop”
“11.2.3, that will address conformance issue fix, is expected to be pre-released soon and made mainnet ready by the end of this week”
The release change for 11.2.3 bumps the protocol version the node advertises in block headers from 11.4 to 11.5 and picks up a component that decodes headers from before protocol version 12 with the legacy decoder. The minutes also say of 11.2.x: “These versions are not capable of surviving the hard fork.” Upgrade Bulletin #43 (9:03 p.m. on November 20) expects “<1 week: Cardano Node 11.2.3 release,” and the mainnet row of its compatibility table still lists 11.1.3.
Neither the release notes for 11.2.1 nor the descriptions of the release changes for 11.2.2 and 11.2.3 mention security.
Disclosure: SIPO is an SPO running three pools; updating to 11.2.x and registering BLS voting keys for Dijkstra are SIPO’s own tasks.
10. Dijkstra and Leios, and Version 6 of the Constitution
The constitution timeline
As of the morning of November 21, version 6 of CAP-12 has not appeared on the CAP portal. The latest is version 5 from October 30, and there have been no comments since November 14. Bulletin #43 expects “~1-2 weeks: v6 of CAP-12 published to Constitutional Amendment Portal” and “~1 month: Update Constitution governance action on-chain.” The November 17 minutes say the new constitution and guardrails action should preferably be submitted before the hard fork, and that the “Earliest possible date of submission would be on 25th November, beginning of epoch 670.” Epoch 670 begins at 6:44:51 a.m. JST on November 26.
The TSC review of whether to restore the procedure for switching Leios off to the constitution, which we reported last week, was scheduled for November 18. As of the morning of November 21, the TSC minutes page has only a heading, and the outcome has not been published (CAP-12’s Leios off switch goes to TSC review on November 18). The working group minutes record that an updated Leios impact assessment was sent out for feedback and that the TSC will give the Leios team a baseline for hardware requirements.
11.3, and moving Preview to Dijkstra
Bulletin #43 expects the 11.3 pre-release in “~2-3 weeks.” The minutes describe 11.3 as “the first candidate that has a chance to be promoted to 12.0 provided successful testing without any showstopper issues,” set a goal of forking the Preview testnet to the Dijkstra era “before the holidays given the right conditions are met,” and note that this will “Need to be well coordinated to respect Midnight needs.”
Implementation progress
- Consensus: three Leios changes, including aggregating votes into certificates, were merged into ouroboros-consensus main on November 14–15. They are not yet part of a release (Leios consensus implementation: three changes including vote certificates merged into main).
- Leios release candidates: rc-2026w46 (November 16) and rc-2026w47 (November 20) were published. The latter describes itself as a “Hotfix to mitigate vote storms.”
- Babel fees: weekly update #137 reports a first working version of Babel fees, which let users pay transaction fees with tokens they hold instead of ADA (First working version of Babel fees lets users pay fees with tokens they hold).
SIPO has commented in the CAP discussion. The debate over SPO costs and guardrails directly affects the conditions under which SIPO runs its three pools.
11. Node Diversity and Moving Teams
Implementations that have produced mainnet blocks
The November 17 minutes list five implementations that have produced blocks on mainnet: cardano-node, Amaru, Dingo, cardano-bean and tsunagi. Tsunagi was added to the four listed in the previous week’s minutes.
Blink Labs, which develops the Go-based Dingo, announced at 8:42 p.m. JST on November 17 that Dingo had produced its 100th mainnet block. When SIPO counted on Koios the blocks whose headers carry Dingo’s identifier, there were 103 from the first on September 16 up to just before the announcement. The identifier is a value written by the block producer itself (Go node Dingo produces its 100th mainnet block). In the same week Dingo released v0.94.0 through v0.94.2, making a new Genesis sync method the default.
Amaru, written in Rust, released v10.11.20261119 on November 20, adding commands such as one that generates pool keys offline. Its “Minimum Viable Block producer” milestone did not close on November 19, and its due date has moved to November 26.
Hydra moves to BlockPQR
At 12:05 a.m. JST on November 19, Input Output announced on its official X account: “Hydra engineering is moving to @blcokpqr on Dec. 1, 2026.” It explained that Hydra uses Cardano’s ledger rules off-chain and that BlockPQR already works on that ledger (Hydra development moves from IOG to BlockPQR on December 1).
In his November 17 video, Hoskinson explained that the final stage of handing over Input Output’s roadmap runs up to the Leios hard fork, and that developers working on each part are moving to new companies every two to four weeks.
12. Who Holds Your Voice
EMURGO and Yoroi DReps: end of December
At 11:36 a.m. JST on November 20, EMURGO announced on its official X account that it would postpone the de-registration of its two DReps, EMURGO and Yoroi, from November 30 to the end of December 2026.
“Following requests from our delegators for additional transition time, we are extending the de-registration timeline for both the EMURGO and Yoroi DReps”
It says the exact date will follow. In SIPO’s check on Koios, about 599.89 million ADA from 15,658 delegations remained with the two DReps as of November 20 (EMURGO and Yoroi DRep de-registration postponed to end of December). If the DRep you delegate to de-registers, withdrawals of staking rewards stop. The rewards themselves do not stop.
On November 18, Intersect’s Civics committee again reminded holders: “Changing your DRep takes a few minutes, and your ADA stays in your wallet.”
Disclosure: SIPO is a DRep and has a direct interest in delegators reviewing their choice. As of the morning of November 21 it has about 120.02 million ADA delegated from 438 delegators (versus about 117.26 million ADA from 431 on November 14, as reported last week).
13. SIPO’s Three Pools
This is SIPO’s own record.
The three pools produced 108 blocks in Epoch 667 (SIPO 58, SIPO2 30, SIPO3 20) and 123 blocks in Epoch 668 (SIPO 51, SIPO2 41, SIPO3 31).
| Pool | Live stake at end of Epoch 668 | Delegators | Ratio to k=1000 saturation |
|---|---|---|---|
| SIPO | 54,765,829 ada | 1,095 | 1.487x |
| SIPO2 | 35,668,638 ada | 477 | 0.969 |
| SIPO3 | 23,946,840 ada | 538 | 0.650 |
As a simple calculation dividing Epoch 669’s circulating supply of 36,824,575,797 ada by k, the saturation point is about 73,649,152 ada at k=500 (current) and about 36,824,576 ada at k=1000. All three pools have a 3.9% margin and a fixed cost of 340 ada, and have produced 48,894 blocks in total.
14. Network: Transactions Back to Pre-Epoch-666 Levels
| Epoch | Period (JST) | Blocks | Transactions | Per block | Fees |
|---|---|---|---|---|---|
| 666 | 11/6 6:44 – 11/11 6:44 | 21,161 | 253,993 | 12.00 | 60,379.81 ada |
| 667 | 11/11 6:44 – 11/16 6:44 | 21,517 | 144,274 | 6.71 | 47,546.95 ada |
| 668 | 11/16 6:44 – 11/21 6:44 | 21,093 | 137,728 | 6.53 | 46,663.72 ada |
The jump in transactions in Epoch 666 that we reported last week reversed in Epoch 667, falling 43.20% to near the Epoch 665 level (142,991). We have not identified why they rose or why they fell back.
15. Tools, DeFi and Market Structure
- Daedalus 11.6.3 (November 20): on Windows, fixes an issue where the wallet backend exited when communication with the node was cut off mid-read, so it now reconnects on its own. It also repairs wallets that older versions had left unopenable, and requires macOS 13 or later (Daedalus 11.6.3 reconnects to the node on Windows after a communication break).
- Lace 2.5.2: Input Output’s November 20 weekly development report says the team prepared 2.5.2 for the browser extension and for iOS and Android, and that the browser version integrates Midnight Wallet SDK 2.0.0. As of the morning of November 21 there is no GitHub release for the browser version yet.
- DJED and SHEN: COTI announced that services for the ADA-backed stablecoin DJED and its reserve token SHEN will wind down at 11:59 p.m. UTC on December 31, 2026, which is 8:59 a.m. JST on January 1, 2027. DJED’s official X account says “All redemptions are subject to the reserve ratio.” (COTI to wind down Cardano stablecoin DJED and SHEN at year end).
- FluidTokens V4: launched a campaign adding 10% APR until the end of the year for supplying USDM, USDCx or USDrf, capped at $1 million (FluidTokens V4 adds 10% APR for supplying three stablecoins).
- CME ADA futures: on November 19 the Cardano Foundation announced that GSR is providing continuous two-sided quotes in CME’s ADA and Micro ADA futures (GSR provides two-sided quotes in CME ADA futures).
- Hackathon: applications opened for the Developer Experience Hackathon, which invites developers from other chains to try Cardano’s new development tools, with $20,000 in prizes and a start date of December 10 (Hackathon to test Cardano’s new developer tools offers $20,000 in prizes).
Within the main DeFi and wallet official accounts we checked, there were no reports of new incidents this week.
SIPO operates a SundaeSwap v4 scooper.
16. Key and Wallet Safety
- Emails claiming to be from Eternl: at 2:27 p.m. JST on November 20, Eternl warned that an official-looking email carrying its branding is “NOT from us. It’s a scam email, don’t click any links.” The email in the screenshot was framed as a “2027 VAT Tax Compliance Update” (Fake emails claiming to be Eternl; wallet warns “not from us”).
- Switching DReps: with the EMURGO and Yoroi date change, be careful of messages offering to “help with the transition” that ask for your recovery phrase. Changing delegation never requires a recovery phrase.
- DJED redemptions: the safest course is to check any notice about the wind-down against official announcements from DJED and COTI.
17. Risk Dimensions
- Treasury (next requests). Global Events 2027 and Mesh SDK close on December 21. Global Events is budgeted at an assumed 1 ada = $0.20, with a quarterly review that scales back later events. CEBP has not been submitted, and about 42.6 million ADA remains under the Net Change Limit.
- Treasury (metadata). The committee’s No votes on AURORA cited a metadata URL that can be edited. Discussion continues on CAP-9, which would remove that requirement.
- Operations (11.2.x). 11.2.3 was expected to be “mainnet ready by the end of this week,” but as of the morning of November 21 it has no release page. 11.1.3 remains the recommended version.
- The Dijkstra schedule. Version 6 of CAP-12, the outcome of the TSC review, the 11.3 pre-release and the submission of the constitution update action are all due over the coming weeks.
- Midnight (operations). The midnight-node advisory is fixed in 2.1.101, but 2.1.200 remains a release candidate and requires a federated authority vote to switch over.
- Delegation. Stake still delegated to the EMURGO and Yoroi DReps will be unable to withdraw rewards after the end-of-December de-registration.
- DeFi. DJED and SHEN end at 8:59 a.m. JST on January 1. Amounts deposited in pools or lending markets need to be withdrawn first.
- Keys. Be careful of emails claiming to be from wallets and of messages that piggyback on date changes.
18. What to Watch Next Week
- cardano-node 11.2.3 — whether a release page appears and whether it is marked for mainnet. Check the
IntersectMBO/cardano-nodereleases page. - Intersect weekly update #138 — not published as of the morning of the 21st. Check Intersect’s news page.
- Hard Fork Working Group — the meeting on November 24. Check the minutes on Intersect’s Cardano Upgrades site.
- TSC minutes for November 18 — how the procedure for switching Leios off is handled. Check the TSC minutes page.
- Midnight’s After Midnight — 17:00 UTC on November 24, 2:00 a.m. JST on the 25th. Check @MidnightNtwrk.
- The Epoch 670 boundary — 6:44:51 a.m. JST on November 26. It coincides with the “earliest possible date of submission” for the constitution update action, and final figures for Epoch 669 will be available. Check gov.tools and Koios epoch data.
- Amaru’s milestone — “Minimum Viable Block producer” is due November 26. Check the milestones list for
pragma-org/amaru. - Version 6 of CAP-12 — check CAP-12 on the CAP portal.
- Developer survey info action deadline — 6:44:51 a.m. JST on December 1.
- Hydra’s move to BlockPQR — December 1. Check official announcements from @IOGroup and BlockPQR.
- The draft for staking NIGHT — check PR #421 in
midnightntwrk/midnight-improvement-proposals. - Midnight node 2.1.200 — whether it moves from release candidate to final. Check the
midnightntwrk/midnight-nodereleases page. - Global Events 2027 and Mesh SDK deadlines — 6:44:51 a.m. JST on December 21. Check each action’s page on gov.tools.
- The date of EMURGO and Yoroi DRep de-registration — check @emurgo_io on X.
Summary
All three treasury actions we followed last week have expired. On PFMS, the committee’s fifth vote arrived a few hours before the deadline, and by delegated stake Yes finished ahead of voted No, but 41.59% of DReps remained far from 67%. On AURORA, committee No votes cited where the metadata was stored.
In the same week, the Foundation’s 25 million ADA request and Mesh’s 600,000 ADA request went to a vote. With the debate over the Foundation’s accountability continuing, DRep votes are where that debate turns into treasury decisions. We corrected one point in last week’s treasury breakdown based on Intersect’s announcement.
On Midnight, a regulated bank’s deposits began moving on chain for the first time, proof generation moved to confidential computing, and standards advanced to token names. On Cardano, 11.2.x remained a pre-release and tags, and the week was spent waiting for version 6 of the constitution and for 11.3.
Next week, ahead of the Epoch 670 boundary at 6:44:51 a.m. JST on November 26, the first thing we will check is whether 11.2.3 appears on the cardano-node releases page.
References and Sources
Links to SIPO’s own articles are placed in the text where they are mentioned. Primary sources are listed below.
- Koios REST API (epoch data, treasury, action status, vote timestamps, circulating supply, DRep delegation): https://api.koios.rest/api/v1
- Cardano governance actions: https://gov.tools/governance_actions
- PFMS action: https://gov.tools/governance_actions/72491608dc1a500d38613214069a2bd3b7e9a0e670d5abd7d6374e6bb54fc0e8#0
- AURORA action: https://gov.tools/governance_actions/14d6a48df8b9099a3e727e1bf6a9ac6c911341a9601e91c7d3ac799bfd89b01b#0
- Copper action: https://gov.tools/governance_actions/6eddf4f1dbad06f329aa69743559c4930b7b689f16c073061d228d9c6613d19c#0
- Global Events 2027 action: https://gov.tools/governance_actions/3815fd9e916c8fdeb0dfde556860f4600bdd981f11a76b0bfb6b30edf9a5e947#0
- Mesh SDK action: https://gov.tools/governance_actions/6b40978780eb15f44786329b39c947f5ff37162464ec4947dcffb55d9139adc7#0
- Cardano Foundation’s Global Events 2027 submission announcement: https://x.com/Cardano_CF/status/2122354225346937104
- Mesh’s submission announcement: https://x.com/meshsdk
- Cardano Foundation’s PFMS post (November 18): https://x.com/Cardano_CF/status/2123027517887885439
- Intersect weekly update #137: https://www.intersectmbo.org/news/intersect-weekly-update-137-nov-15-2026
- Intersect’s treasury return announcement: https://x.com/IntersectMBO/status/2123073566455296437
- Intersect Upgrade Bulletin #43: https://x.com/IntersectMBO/status/2123749035538313351
- Hard Fork Working Group minutes (November 17): https://cardanoupgrades.docs.intersectmbo.org/general/hard-fork-working-group-meeting-minutes/17th-november-2026
- TSC minutes (November 18): https://technicalsteeringcommittee.docs.intersectmbo.org/meeting-minutes/2026-tsc-meeting-minutes/meeting-minutes-november-18-2026
- CAP-12 (CAP portal): https://cap-portal-api.onrender.com/proposals/12
- cardano-node 11.2.1: https://github.com/IntersectMBO/cardano-node/releases/tag/11.2.1
- Release change for cardano-node 11.2.3: https://github.com/IntersectMBO/cardano-node/pull/6777
- Input Output weekly development report (November 20): https://www.essentialcardano.io/development-update/weekly-development-report-2026-11-20
- Input Output’s Hydra move announcement: https://x.com/IOGroup/status/2123070074906894637
- Leios release candidate rc-2026w47: https://github.com/input-output-hk/ouroboros-leios/releases/tag/rc-2026w47
- Amaru v10.11.20261119: https://github.com/pragma-org/amaru/releases/tag/v10.11.20261119
- Amaru milestones: https://github.com/pragma-org/amaru/milestone/25
- Blink Labs’ 100-block announcement for Dingo: https://x.com/blinklabs_io
- Cardano Foundation CEO’s long post: https://x.com/F_Gregaard
- Hoskinson’s post on the AMA: https://x.com/IOHK_Charles/status/2123474649774489822
- Hoskinson’s GPU support post: https://x.com/IOHK_Charles/status/2123621915164377502
- Hoskinson’s December 15 post: https://x.com/IOHK_Charles/status/2123538522598683047
- Midnight’s Monument Bank blog: https://midnight.network/blog
- Midnight Foundation’s Monument Bank post: https://x.com/midnightfdn/status/2122739979075870729
- midnight-node advisory (November 14): https://github.com/midnightntwrk/midnight-node/security/advisories/GHSA-f46h-wx5g-q2v7
- Midnight indexer 4.3.800: https://github.com/midnightntwrk/midnight-indexer/releases/tag/v4.3.800
- Midnight ledger 9.1.0.2: https://github.com/midnightntwrk/midnight-ledger/releases/tag/ledger-9.1.0.2
- Midnight node 2.1.200-rc.2: https://github.com/midnightntwrk/midnight-node/releases/tag/node-2.1.200-rc.2
- NIGHT Staking on Cardano draft (PR #421): https://github.com/midnightntwrk/midnight-improvement-proposals/pull/421
- Midnight improvement proposals repository (MIP-0018, MPS-0050, MPS-0051): https://github.com/midnightntwrk/midnight-improvement-proposals
- Midnight’s After Midnight announcement: https://x.com/MidnightNtwrk/status/2123777219575087603
- Midnight Foundation’s Pulse Pump post: https://x.com/midnightfdn/status/2123781033438953751
- EMURGO’s DRep postponement announcement: https://x.com/emurgo_io/status/2123606389763563783
- Intersect Civics’ Check your DRep: https://x.com/IntersectCIVICS/status/2122710291481788465
- Daedalus 11.6.3: https://github.com/input-output-hk/daedalus/releases/tag/11.6.3
- DJED wind-down announcement: https://x.com/DjedStablecoin
- Cardano Foundation’s GSR post: https://x.com/Cardano_CF/status/2123397900076011933
- Eternl’s warning: https://x.com/eternlwallet
- Cardano DEX volume: https://defillama.com/chain/Cardano
- Morning fixed-point readings (ADA / BTC / ETH are Hyperliquid perpetual futures prices): https://app.hyperliquid.xyz
- ADA at epoch boundaries: https://www.coingecko.com
- Weekly Brief #32: https://sipo.tokyo/language/en/weekly-brief-32-en/
Transparency Notes
- Treasury action votes: retrieved from Koios at 7:15 a.m. JST on November 21. Figures for PFMS, AURORA, the two new actions and the developer survey are calculated by Koios on Epoch 669 delegation; Copper on Epoch 668 delegation. The denominator is explicit Yes plus the stake that counts as No (voted No, non-voters and always-no-confidence): 4,353,613,724 ada for PFMS, 3,496,666,328 ada for AURORA and 3,978,517,864 ada for Copper. The Yes rate is Yes ÷ denominator, and the voted-No share is voted No ÷ denominator (PFMS 1,810,497,678 ÷ 4,353,613,724 = 41.59% and 1,747,156,046 ÷ 4,353,613,724 = 40.13%; AURORA 2,191,446,521 ÷ 3,496,666,328 = 62.67%; Copper 2,858,324,982 ÷ 3,978,517,864 = 71.84%). The No rate returned by the public API includes non-voters and always-no-confidence, so we do not use it. Abstentions are excluded from the denominator.
- Difference in Copper figures: SIPO’s November 16 article, based mainly on AdaStat’s post-expiry tally, reported 0.51% Yes and 72.31% voted No. This article uses Koios’s tally: 0.50% and 71.84%. The difference reflects timing and source.
- PFMS ceiling with non-voters: (1,810,497,678 + 664,927,616) ÷ 4,353,613,724 = 56.86%. The increase in Yes was 1,810,497,678 − 1,397,618,954 = 412,878,724 ada.
- Committee votes and rationales: based on Koios records and each member’s rationale. Committee members are not named. Quotations from rationales and DRep vote rationales are from the English originals. DRep names and delegated stake are each DRep’s registered display name and Koios values.
- Global Events 2027 conversion: 24,995,775 × $0.14068 = about $3,516,406, or 70.3% of the assumed $4,999,155. The Net Change Limit remainder is 500,000,000 − 457,395,629 = 42,604,371 ada.
- Correction to last week: subtracting the Catalyst returns of 23,063,600 ada from the Epoch 667 treasury increase of 26,688,995 ada leaves 3,625,395 ada. The time of the second return was confirmed from on-chain records in SIPO’s November 20 article.
- SIPO DRep delegation: retrieved from Koios at 7:18 a.m. JST on November 21 (120,022,516 ada, 438 delegators). Its share of PFMS’s denominator is 120,022,516 ÷ 4,353,613,724 = 2.76%.
- cardano-node: checked against GitHub release and tag data in the 7 a.m. hour JST on November 21. Because neither the 11.2.1 release notes nor the descriptions of the 11.2.2 and 11.2.3 release changes mention security, we do not describe any of them as a “security fix.” Since 11.2.2 and 11.2.3 have no release pages, their release notes themselves could not be checked.
- Midnight advisories and releases: translated from the English originals of the GitHub advisories and release notes. For indexer 4.3.800, the release notes themselves use the words “security issues.”
- Dingo block count: based on Blink Labs’ announcement and the Koios check (103 blocks) in SIPO’s November 18 article. The identifier is written by the block producer.
- EMURGO and Yoroi DRep delegation: values checked against Koios in SIPO’s November 20 article.
- Saturation estimate: a simple calculation dividing Epoch 669’s on-chain circulating supply of 36,824,575,797 ada by k. SIPO’s three pool figures are live stake retrieved just after the end of Epoch 668.
- Staking ratio: the value at the start of Epoch 669. We could not obtain the boundary value at the start of Epoch 668, so we do not report the change.
- Market reading times: the November 14 values are from the 6:35:09 a.m. morning reading and the November 21 values from 6:35:03 a.m. The epoch-boundary ADA figure (−7.41%) uses CoinGecko values at the boundary times.
- SIPO’s interests: in the text we disclose that SIPO voted No on Copper, Yes on PFMS and Abstain on AURORA; that it has not yet voted on Global Events 2027, Mesh SDK or the developer survey; that on Midnight it is a member of the Nightforce ambassador programme and an SPO whose pool selection would be affected by the NIGHT staking draft; that for node 11.2.x and Dijkstra, updating and registering BLS voting keys are SIPO’s own tasks; that on CAP it has posted public comments; that on delegation it is a DRep with about 120.02 million ADA from 438 delegators; that its three pools run at a 3.9% margin with a 340 ada fixed cost, and pool 1 is above the k=1000 saturation point; and that it operates a SundaeSwap v4 scooper.
- What we did not write: forecasts for any action, guesses at why DReps and committee members voted as they did, the name of the Japanese payments company, the content of Hoskinson’s December 15 presentation (his own post does not describe it), figures from the Foundation’s AMA (we have not verified a primary record from the Foundation), GPU speed-up figures (they are testers’ reports, not official measurements), Midnight transaction counts, the name of Monument’s token and the amount issued so far, the cause of the rise and fall in Epoch 666 transactions, and the outcome of the TSC review (not published).
- Prices and events: not linked.
This is not investment advice. For information and research purposes only.
