LIVE ADA-- MCAP-- TVL-- STAKE-- EPOCH-- Cardano & Midnight 総合情報ポータル
SIPO
HOME › Weekly Brief EN › Weekly Brief #31 | Midnight Takes Ledger 9 to Mainnet Without a Preprod Run
Weekly Brief EN

Weekly Brief #31 | Midnight Takes Ledger 9 to Mainnet Without a Preprod Run

2026-11-07SIPO

Midnight announced at 6:41 a.m. JST on November 7 that it had finished the hard fork moving its mainnet ledger from Ledger 8 to Ledger 9. The upgrade skipped the usual Preprod deployment and soak period. The official explanation is that this approach is used “when security fixes require a more controlled release path,” and no specific vulnerability is named.

In the same week, DijkstraNet, the network testing Cardano’s next hard fork, moved to protocol version 12. It did so without Leios and CIP-23, and cardano-node 11.2.1, the version intended for mainnet, had not been released as of the morning of November 7. IOG announced that its consensus and developer experience teams will move to independent companies.

Two things moved on the on-chain record for the treasury. At 4:57 a.m. JST on November 7, 21 million ADA from a cancelled Catalyst milestone was recorded in a transaction returning it to the treasury. Copper and AURORA received a third “unconstitutional” vote from the Constitutional Committee, while PFMS stands at 24.88% DRep Yes against 26.86% voted No.

SIPO is a member of Midnight’s Nightforce ambassadors, and voted on all three treasury actions as a DRep on November 5: No on Copper, Yes on PFMS and Abstain on AURORA. Full disclosures are in Chapters 2 and 7.

Executive Summary

  • Midnight moves to Ledger 9: the upgrade went directly to mainnet, skipping Preprod and the soak period. Existing balances and contracts migrated automatically, and the project says NIGHT holders need do nothing. Developers must update to Midnight.js 5. Preprod remains on Ledger 8.
  • DijkstraNet reaches protocol version 12: Intersect’s announcement gives 9:00 a.m. JST on November 2, without Linear Leios or CIP-23. Upgrade Bulletin #41 describes BLS voting key registration as what can be tried at this stage.
  • cardano-node 11.2.1 is not out yet: it is meant for mainnet and will include a fix for a memory usage regression. It was expected “later this week,” but no tag existed as of 9 a.m. JST on November 7. The known-issues section of 11.2.0 is still empty.
  • The schedule for Leios and the constitution: 11.3 is “at least 2–3 weeks away,” and the target for submitting the new constitution and guardrails is by November 25. A TSC proposal on how to switch Leios off will be reviewed on November 18.
  • IOG moves two teams: consensus to Serokell and developer experience to AlwaysTrue. The moves run until early 2027.
  • Catalyst’s 21 million ADA: funds moved to a treasury reserve contract in July were returned on November 7 as a donation to the treasury. They will appear in the balance only after the November 11 boundary.
  • Three treasury actions: voted No on Copper stands at 55.88%. On Copper and AURORA, the Committee cannot reach two-thirds even if the remaining four members all vote Yes. PFMS has 24.88% DRep Yes and two Committee Yes votes.
  • SIPO’s three votes: No on Copper, Yes with expectations on PFMS, Abstain on AURORA. SIPO holds about 118.88 million ADA from 430 delegations.
  • The budget debate: Intersect’s CEBP info action (target: November 10) and the Cardano Foundation’s Global Events 2027 (a proposal of 24,995,775 ada) are not on chain yet. The DRep Council is collecting comments on a draft standard for treasury proposals.
  • Network: Epoch 665 had 142,991 transactions, the second consecutive increase.
  • SPO work: SIPO applied a fix for Linux kernel vulnerability CVE-2026-98432 across all of its nodes.
  • Binance’s initial report: about USD 6.34 billion was impacted, and 98% has been replenished. This is not the final report.
  • Markets: ADA −4.63%, BTC −1.39%, ETH −0.57%, NIGHT −3.59%.

1. Market Pulse

These are morning fixed-point readings from October 31 to November 7. ADA, BTC and ETH are Hyperliquid perpetual futures prices.

Asset10/3111/7Week
ADA$0.19425$0.18525−4.63%
BTC$76,820.0$75,750.8−1.39%
ETH$2,238.70$2,225.90−0.57%
NIGHT$0.040036$0.038599−3.59%

All four fell, with ADA falling the most. NIGHT at both ends is calculated from Cardano DEX prices, so the source is consistent. Priced in ADA, NIGHT moved from 0.206105 ADA to 0.208361 ADA, or +1.09%.

At epoch boundaries, ADA went from $0.19339963 (¥30.48) at 6:45 a.m. on November 1, when Epoch 665 began, to $0.18313272 (¥28.87) at 6:45 a.m. on November 6, when Epoch 666 began: −5.31%. The sampling times differ, so this does not match the weekly −4.63%.

We do not link price moves to the events covered in this article.

The remaining network figures: at the boundary from Epoch 664 to 665, the staking ratio rose from 56.29% to 56.77%, and delegators fell by 6,036 to 1,326,283. The treasury stands at 1,396,473,702 ada in Epoch 666.

2. Midnight’s Ledger 9 Goes Straight to Mainnet

What the project said

Midnight’s official account said the following in a series of posts at 6:41 a.m. JST on November 7.

“Midnight has completed its upgrade from Ledger 8 to Ledger 9, bringing new capabilities for developers alongside security, compatibility and performance improvements across the network.”

“Unlike previous upgrades, Ledger 9 has been deployed directly to mainnet, bypassing the standard Preprod deployment and soak period. This approach is used when security fixes require a more controlled release path to protect the network.”

The official blog says the same and that “the Midnight network has just executed a hard fork.” The announcement gives neither the exact time of the fork nor the vulnerability addressed. The release notes for Ledger 9.1.0.0, published on November 5, say it carries forward security fixes released to mainnet as 8.1.2 and 8.1.3, listing “contract call transcripts must embed canonical field values” and “hardening of low-level deserialization.” How these relate to this decision cannot be determined from the official material. No new security advisories were published in Midnight’s repositories this week (Ledger 9 flash report).

Who needs to do what

RoleOfficial guidance
NIGHT holdersNo action needed. Balances and deployed contracts migrated automatically
dApp developersExisting contracts carry over, but apps must update to Midnight.js 5
Developers on Preview and PreprodtNIGHT must be re-registered to resume DUST generation

The Midnight.js 5.0.0 migration guide rates the difficulty as High and says to expect several days of work. It warns that builds still on 4.1.1 at the fork can no longer read the network or call contracts they deployed. That version was published the day before the announcement, which left developers a short preparation window (Midnight.js 5.0.0). On the wallet side, the SDK documentation explains that balances can look empty after the fork until the first sync completes.

The usual order of versions is reversed

Midnight’s official support matrix showed the following on the morning of November 7.

NetworkLedgerNodeMidnight.js
Mainnet92.1.1015.0.0
Preview92.1.1015.0.0
Preprod81.0.4004.1.1

Preprod, which normally comes before production, now sits one ledger behind it. Documentation updates “will roll out over the coming weeks.” The public releases of midnight-node on GitHub still end at node-1.0.400 from October 6, and no tag matching Node 2.1.101 was visible at this time.

What changes with Ledger 9

The new items are native support for the widely used cryptographic standards ECDSA and Keccak-256, wider wallet and custody compatibility, and contract-to-contract calls. The proving foundation moved to zk-stdlib v2, and fees gained an explicit price floor. As of Ledger 9.1.0.0, two known issues were public, including one where a contract call paying its fee with a single DUST spend can be rejected (Ledger 9.1.0.0).

The official wording on contract calls varies. The November 6 notice says the “upcoming upgrade will introduce” them, the Ledger 9 post says the upgrade “enables contracts to interact directly with one another,” and the roadmap says that in Q1 2027 contracts “will be able to call one another while each keeps its own data private.”

Around Midnight

  • Ascend: the Midnight exchange Ascend opened “prediction perps,” leveraged trading on the probability of events, to private participants on mainnet (Ascend).
  • Nightmode: Sig Network still wrote “Live on Midnight stagenet” on November 3, and no mainnet support has been announced.
  • Roadmap: block production rewards for stake pool operators are listed for Q4 2026, and participation by Cardano SPOs and NIGHT delegation for Q1 2027. No dates are given.

Disclosure: SIPO is a member of Midnight’s Nightforce ambassadors and, as a Cardano SPO, could be eligible for the opening of block production in the roadmap.

3. DijkstraNet Moves to Protocol Version 12

What the switch contains

In Upgrade Bulletin #41, Intersect wrote that the node 11.2 pre-release moved DijkstraNet into the Dijkstra era on November 2 at 00:00 UTC (9:00 a.m. JST).

“The release includes the Dijkstra hard fork feature set except Linear Leios and the Fair Min Fees implementation (CIP-23).”

The same entry in the Cardano Operations Book says “November 1st,” so the dates differ. We follow the Bulletin and the Hard Fork Working Group minutes here. Mainnet remains on protocol version 11, and no switch date has been given (DijkstraNet moves to protocol 12).

Last week we reported that the CIP-23 change using minimum values in reward calculation had been merged into the ledger. That is a statement about the code: DijkstraNet running on 11.2 does not include it yet. The minutes’ action items also still include adding the full CIP-23 implementation to the Dijkstra overview page. For Leios, what can be tried on 11.2 today stops at BLS voting key registration.

In the minutes, SPO Martin (ATADA) expressed concern about confusion over which features are available on which testnet and version, and work on a compatibility matrix was assigned. On hardware wallets, BLS support for the Cardano app on Ledger has been developed and is waiting for the next release.

11.2.1 has not arrived

Intersect’s Weekly Update #136 (published at 5:22 a.m. JST on November 7) lays out the versions as follows.

VersionPosition
11.1.3The current recommended release for Preview, Preprod and mainnet
11.2 pre-releaseFor DijkstraNet. Not yet cleared for mainnet
11.2.1Soon to be released with mainnet clearance, with a fix for a memory usage regression seen in the 11.1.x line
11.3Target release candidate for the full Dijkstra era including Linear Leios. “At least 2-3 weeks away”

Bulletin #41 said 11.2.1 was expected “later this week,” but no tag existed on GitHub as of 9 a.m. JST on November 7. A changelog update was merged into release/11.2.x at 5:53 a.m. the same morning. The 11.2.0 release notes were edited on November 5, yet the known-issues, benchmark and system-test sections are still waiting to be filled in. The check we listed last week was not resolved this week.

The memory regression is said to extend to the 11.1 line, and #136 explains that the fix returns usage “to levels comparable with Node 11.0.” No figures have been published.

DB Sync 13.8.0.0 (early November 5) is a release “advised for all operators.” Logging configuration changed, and old keys are ignored without stopping startup, so monitoring can quietly detach (DB Sync 13.8.0.0). cardano-cli 11.7.0.0 (November 6) adds a command that replaces only the BLS key in a pool registration certificate.

Disclosure: SIPO is an SPO running three pools, and upgrading to 11.2.1 and registering BLS voting keys are SIPO’s own work.

4. The Schedule for Leios and the Constitution

Into the main development branch

Input Output’s weekly development report (November 6) says endorser block production, certificate checks during chain selection and vote relaying were added on the main development branch, and adds that these “remain development work, not a mainnet release.” In the prototypes, rc-2026w44 added shrinking endorser blocks when votes fall short, and rc-2026w45 adjusts that. The notes call it “still experimental and off by default” (Leios prototype).

How to stop it is not settled

Version 5 of constitutional amendment proposal CAP-12 said Leios parameters cannot be set to zero. An editor’s note on November 3 says this means “the off switch has been removed rather than moved,” and points out that the CAP, its exhibit and the TSC are now out of step.

On November 6, Kevin Hammond of the TSC posted a proposed position. It supports setting maxEndorserBlockTxsSize to 0 as the official network-wide way to deactivate Leios, conditional on written confirmation from the Leios team, measured switching on Preview and Preprod, conformance tests across all node implementations, and a guardrail change. It will be reviewed on November 18 and is not yet a decision. It runs in the opposite direction to version 5’s “cannot be zero.”

He also wrote that reference script guardrails “need to be treated carefully since there are security implications (including possible Denial-of-Service for Linear Leios),” that a detailed review has been passed to the Security Council for final sign-off, and that the Parameter Committee has not yet seen the pending values.

The November 25 target

According to the November 3 Hard Fork Working Group minutes, the aim is to submit the new constitution and guardrails “no later than 25th November (or between epochs 667 and 669).” #136 reports that around thirty values are still pending and a sixth version is expected. The next CAP review session is at 4 p.m. JST on November 12.

SIPO contributes comments to the CAP discussion. On CAP-10, which would require SPO approval for pool economic parameters, SIPO commented while stating its interest as a DRep that also runs three pools.

5. IOG Moves Consensus and Developer Experience

In a blog post on November 5, “Independent teams. Shared foundations.,” IOG announced that two teams are moving from IO Labs to independent organizations.

“Two Cardano engineering teams are moving from IO Labs to independent organizations: consensus to Serokell and developer experience (DevX) to AlwaysTrue.”

“Each team moves on its own schedule between now and early 2027.”

The code stays in public repositories: consensus remains in the IntersectMBO organization on GitHub, and the developer tools AlwaysTrue maintains remain under Apache 2.0.

AreaMoved to
ConsensusSerokell (this announcement)
Developer experienceAlwaysTrue (this announcement)
MithrilTeragone
DaedalusSe7en Labs
Ledger, indexer, formal methods, high availabilityBlockPQR
PlutusMidgard Labs
Platform, quality assurance, cryptography, performanceICAN Group

Serokell worked on Cardano’s early node, and IOG describes this as consensus returning to Serokell. The consensus layer also carries the mechanism that executes hard forks. Because the moves overlap with Dijkstra preparation, their order matters to SPOs too. The announcement does not cover post-transfer funding or contract terms (IOG team moves).

6. Catalyst’s 21 Million ADA Goes to the Treasury

Two transactions on the record

This is what SIPO.TOKYO’s editors confirmed from on-chain records. Koios’s total for Epoch 666 showed a treasury donation of 21,000,000 ada, so we checked the epoch’s 67,016 transactions and found one that matched.

Time (JST)Transaction
July 2, 2026, 4:58 p.m.Moved 21,000,000 ada from one contract to another. Event type modify
November 7, 2026, 4:57 a.m.Sent that 21,000,000 ada as a donation to the treasury. Event type sweep

Both transactions carry the same reason in their metadata.

“With administration of Catalyst FC transferring from Input Output to the Cardano Foundation, Fund 15 will no longer go ahead under the scope of the existing ‘Catalyst 2025 Proposal by Input Output: Advancing Decentralised Community Innovation Funding & Infrastructure’ SoW. The corresponding Milestone payment for Fund 15 shall therefore be cancelled and returned to the treasury.”

The July transaction’s description says “This project is being cancelled and funds returned to the treasury reserve contract,” and the November transaction names milestone MS-4 of project EMI-0001a-25. Funds moved to the reserve contract in July reached the treasury itself about four months later.

Background and what can be checked

Cardano’s official glossary says Input Output and the Cardano Foundation agreed in February 2026 that the Foundation takes over stewardship of Project Catalyst. It adds that “Fund15 and Fund16 did not go ahead in their planned form, the ada earmarked for them went back to the treasury,” and that grantees from Fund14 and earlier continue to be paid per milestone.

Treasury donations are added to the balance at the epoch boundary. The Epoch 666 balance of 1,396,473,702 ada does not include this amount, and it can be checked in Koios’s Epoch 667 value after the boundary at 6:44:51 a.m. JST on November 11. It is about 1.5% of the balance, and these are previously withdrawn funds coming back rather than newly created money. We could not find an official announcement of this transaction. We have not written about how it is treated in the Net Change Limit calculation.

7. Three Treasury Actions

Where the votes stand

These are DRep votes taken at 9:30 a.m. JST on November 7. The denominator is explicit Yes plus voted No, not voted and always-no-confidence.

ActionAmountDRep YesVoted NoCommittee (Yes−No)Deadline
Copper22,000,000 ADA5 votes, 0.41%107 votes, 55.88%0−3Nov 16, 6:44:51 a.m.
AURORA940,000 ADA14 votes, 3.63%63 votes, 36.43%0−3Nov 21, 6:44:51 a.m.
PFMS9,600,000 ADA37 votes, 24.88%43 votes, 26.86%2−0Nov 21, 6:44:51 a.m.

Since last week, PFMS Yes rose from 26 votes (20.39%) to 37, and voted No from 27 votes (13.30%) to 43. Each needs 67% of DReps and two-thirds “constitutional” from the Constitutional Committee.

If delegations stay as they are, the ceiling if every non-voter voted Yes would be 41.1% for Copper and 60.4% for AURORA, neither reaching 67%. PFMS’s ceiling is 70.5%, reaching 67% if 92% of non-voters vote Yes.

The third Committee vote

One Constitutional Committee member voted “unconstitutional” on Copper and AURORA early on November 3. The rationale summary is “off-chain content is not immutable,” citing Article II, Section 6.1 of the constitution and recording that Copper is hosted on the proposer’s website URL and AURORA on a GitHub branch URL. The same member voted Yes on PFMS and the developer survey, with a rationale reading in full “LGTM.”

There are seven members, so on Copper and AURORA four more Yes votes would give four-sevenths, short of two-thirds. CAP-9, a constitutional amendment that addresses the same clause by removing the immutable storage requirement for metadata, reached version 3 on November 3.

DRep rationales

The Cardano Foundation voted No on AURORA on the evening of November 5, writing:

“this proposal does not show that a lack of this infrastructure is what holds institutional credit back. […] The proposal names no lending protocol, originator or capital provider committed to the standard”

On PFMS, DRep rationales sit on both sides. Phil UPLC, voting No, wrote that “the proposal has not demonstrated enough value to Cardano to justify the treasury funding the full development cost.” Rodrigo, voting Yes, wrote “I consider the existing delivery record, the proposed milestone controls and the potential benefit to Cardano sufficient grounds to support this proposal.” Governance Hour #13 aired as scheduled early on November 6, and the PFMS proposer is answering rationales directly on DRep Talk (DRep Talk).

SIPO’s three votes

These are SIPO’s own votes, recorded here as a party to them. The full rationales are in each article and on chain.

  • No on Copper (Nov 5, 10:05 a.m.): four points: fund control concentrated in the recipient, a receiving account that contradicts the proposal’s own commitment, the allocation of price risk and profit, and a size above half of the remaining headroom. SIPO states this is not opposition to real-world asset tokenization (SIPO on Copper).
  • Yes with expectations on PFMS (Nov 5, 11:22 a.m.): SIPO weighed usage and demand already on mainnet and payments conditional on usage. It also asks for a correction of the “multisig” description and public confirmation from the deploying state government, among other items (SIPO on PFMS).
  • Abstain on AURORA (Nov 5, 11:41 a.m.): SIPO supports the direction and fund controls, but cited a proposal record that is not fixed, no evidence of users, and a design in which funds can leave before final acceptance, and set out conditions for a Yes (SIPO on AURORA).

SIPO’s DRep has not yet voted on the developer survey info action.

8. Who Holds Your Voice

The EMURGO and Yoroi DReps

EMURGO’s latest post remains the one from October 28, and no change to the November 30 deregistration date has been announced. According to Intersect’s Weekly Update #136, the Civics Committee begins a “Check your DRep” campaign on Monday (November 9). As we wrote last week, what stops is the withdrawal of rewards, not the rewards themselves.

Retired pools and reasons to choose again

Cexplorer warned on November 3 that 131.65 million ADA remains delegated to retired stake pools, with 59,025 accounts earning no rewards (retired pools). As with DRep delegation, this continues until holders choose again. As a way to check, Cardanoscan rebuilt its pool list so that pool governance votes appear on the same page (Cardanoscan).

Disclosure: SIPO is one of the five DReps named as examples in EMURGO’s announcement, and at Epoch 666 holds about 118.88 million ADA from 430 delegations (about 104.63 million ADA and 417 as of October 28 last week). SIPO has a direct interest in the choice of where to move.

9. Deciding Budgets: Three Proposals

CEBP and November 10

Intersect’s 2027 budget proposal, CEBP, targets November 10 for its first info action. As of the morning of November 7 nothing has been submitted on chain, and the text of #136 does not mention CEBP. No new governance actions were submitted this week.

Global Events 2027

Early on November 5, the Cardano Foundation published on its forum a proposal for a shared booth at industry conferences in 12 cities in 2027. The request is US$4,999,155, or 24,995,775 ada at an assumed US$0.20 per ada, with submission planned for November. Tokyo’s TEAMZ Summit (April) is included. The Foundation says that if approved it would fall under CEBP’s Marketing, Analysis & Events domain, and it has also put itself forward as that domain’s steward. DRep sessions are at 6 p.m. JST on November 9 and 1 a.m. JST on November 10 (Global Events 2027).

The DRep Council’s proposal standard

On November 5, the DRep Council began collecting comments on a draft standard listing the questions a treasury proposal should answer. It drew on 158 governance actions and rationales from 19 DReps, and states that it does not bind votes. Comments run for seven days (DRep Council standard). A trial tool that scores proposals with an LLM has also been released (LLM scoring).

SIPO posted a public comment on this draft as a DRep outside the Council, proposing wording on the items asking for full names and LinkedIn that takes account of regional differences and pseudonymous contributors.

10. SIPO’s Three Pools and the Kernel Update

This is SIPO’s own record.

CVE-2026-98432

In Weekly Update #135, Intersect asked SPOs to prepare for the critical Linux kernel vulnerability CVE-2026-98432 (CVSS 9.8). Ubuntu’s CVE page still showed each version as “work in progress” on the morning of November 7. Ubuntu’s November 2 blog post said fixed kernels had been placed in its testing pocket ahead of general release. On November 3, SIPO installed the fix on all of its nodes and rebooted them. Whether to install a testing-stage build or wait for general release is a matter of operating philosophy (SIPO’s kernel update). Even after installation, the old kernel keeps running until reboot.

Pool figures

In Epoch 665, the three pools produced 142 blocks: SIPO 61, SIPO2 46 and SIPO3 35 (119 in Epoch 664).

PoolLive stake at end of Epoch 665DelegatorsRatio to k=1000 saturation
SIPO55,044,927 ada1,0981.495x
SIPO235,483,618 ada4770.963
SIPO323,962,184 ada5430.651

As a mechanical estimate, dividing the November 7 circulating supply of 36,828,375,236 ada by k gives saturation of about 73,656,750 ada at k=500 (current) and about 36,828,375 ada at k=1000. SIPO’s first pool fell by about 1.2 million ada in one epoch. All three pools have a 3.9% margin and a 340 ada fixed cost.

11. Network: 142,991 Transactions in Epoch 665

EpochPeriod (JST)BlocksTransactionsPer blockFees
66310/22 6:44 – 10/27 6:4421,471126,7115.9040,210.07 ada
66410/27 6:44 – 11/1 6:4421,225138,1476.5142,320.14 ada
66511/1 6:44 – 11/6 6:4421,565142,9916.6341,673.49 ada

Transactions in Epoch 665 rose 3.51% from the previous epoch, and fees fell 1.53%. On rewards, the Epoch 664 total settled at 6,146,940 ada, down 1.38% from 6,232,906 ada in Epoch 663. The treasury balance rose by +3,576,727 ada at the boundary into Epoch 666. This arithmetic is as far as we can go.

12. Tools and Node Diversity

  • Amaru (Nov 6): v10.11.20261105 of the Rust node Amaru states “Block forging is no longer limited to test networks.” CIP-0203 tags are on by default. There is no record of it actually producing a block on mainnet, and its “Minimum Viable Block producer” milestone remains open with a November 12 target (Amaru).
  • Mithril: Teragone’s milestones M1.1 and M1.2 (658,718 ADA in total) were approved, confirming a prototype for distributing data over IPFS (Mithril).
  • Wallets: GeroWallet published all of its browser extension code under Apache 2.0 (GeroWallet), and Daedalus released 11.6.1 early on November 7.
  • Dolos v1.6.3: a maintenance release addressing five security advisories in dependencies, recommended by TxPipe for all v1 users (Dolos).
  • Post-quantum signatures: a CIP pull request proposes Plutus builtins to verify ML-DSA and SLH-DSA (post-quantum proposal).

There was no full Hydra release this week.

13. DeFi

  • ATLAS: the perpetuals venue ATLAS opened its mainnet beta to the public on the morning of November 2, with up to 5x leverage (ATLAS).
  • Surf: about two months after its late-August incident, it restored leverage and liquidation (Surf).
  • Indigo: it published the contents of Indigo Prime, funded through PRIME, and says the first INDY cashback payout goes out this week (Indigo).
  • Strike: it announced that more than 7,000 people have traded on it in total (Strike).
  • USDrf: according to Cexplorer, RealFi’s USDrf is Cardano’s third-largest stablecoin at 8.63% (USDrf).
  • Liqwid: wanUSDC reimbursements were announced as claimable from November 2, but we could not find a follow-up confirming they started.

SIPO runs a scooper for SundaeSwap v4. On November 7 it published an explainer from the perspective of processing orders (SundaeSwap v4 guide).

14. Keys and Exchanges

Binance’s initial report

On November 3, Binance published its initial report on the October 29 (UTC) theft. About USD 6.34 billion was impacted and about USD 2.85 billion frozen or intercepted, and the attacker “exploited unauthorized access to an internal wallet signing service.” The report traces a path starting from a developer’s device in June, and says the latest FBI information indicates North Korea is responsible. Binance says it will absorb the loss, and its update early on November 5 reported about 98% replenished.

The investigation continues, and an independent third-party review is planned. Withdrawals have been resuming in phases since November 1, and a November 6 post says Binance aims to reopen all tokens on restored networks by the end of next week. The treatment of ADA and NIGHT does not appear in announcements we could confirm in text. SIPO has an article on what can and cannot be prevented (Binance).

Wallet warnings

  • SecondFi: on November 6, it warned that “SecondFi will never email you.” Any contact asking for a recovery phrase is a scam (SecondFi).
  • Keystone: it explained that the web authentication key used to verify devices reached attackers and sent its 3 Pro stock for disposal (Keystone stock). On November 6, it said some Nexus App services were hit by a cyberattack and asked users to update to v1.3.7 (Nexus App).

15. Organizations and Adoption

  • Petrobras: the Cardano Foundation said on November 4 that Brazil’s Petrobras is tokenizing sustainable aviation fuel certificates on Cardano (Daily Intel 11/5).
  • Cardano Accelerator: eight ventures in the fall cohort kicked off in Dublin, with Demo Day on February 3 (Accelerator).
  • Reeve 1.8: the new version of the Foundation’s financial reporting base makes items tied to already published funds uneditable (Reeve).

16. Risk Dimensions

  • Midnight (information asymmetry). Because the content of the fix is not public, neither users nor developers have material to judge what was affected. Whether details are published is the next check.
  • Midnight (gap with test environments). While Preprod sits on an older ledger than production, testing under identical conditions is not possible. The timing of the Preprod update and documentation revisions directly affects developers.
  • Operations (11.2.1 ordering). The new 11.2 configuration files cannot be read by nodes older than 11.2. Even after 11.2.1 is out, the node itself must be upgraded first.
  • Dijkstra schedule. Testing proceeds without CIP-23 and Leios, while 11.3 and the constitution submission target fall close together. If 11.3 moves, later steps move too.
  • Development structure. The consensus team responsible for hard forks changes organizations during Dijkstra preparation.
  • Treasury. On Copper and AURORA, Committee arithmetic falls short of two-thirds. PFMS has Yes and No side by side and depends on non-voters. The proposals on how to decide budgets have not been submitted yet.
  • Delegation. Wallets still delegated to the EMURGO and Yoroi DReps will be unable to withdraw rewards after the deadline.
  • Keys. In the SecondFi and Keystone cases, beware of scams posing as support. The kernel fix is ahead of Ubuntu’s general release, so SPOs will differ on when to install it.

17. What to Watch Next Week

  1. cardano-node 11.2.1 — the release for mainnet, and whether the known-issues section is filled in. Check the IntersectMBO/cardano-node releases page.
  2. Midnight follow-ups — publication of what was fixed, and Preprod’s update to Ledger 9. Check Midnight’s official blog and the documentation’s support matrix.
  3. Global Events 2027 DRep sessions — 6 p.m. JST on Nov 9 and 1 a.m. JST on Nov 10. Check @Cardano_CF on X.
  4. Check your DRep — begins Monday, Nov 9. Check Intersect’s weekly update.
  5. CEBP info action — target submission Nov 10. Check GovTool and DRepTalk.
  6. Epoch 667 boundary — Nov 11, 6:44:51 a.m. JST. Whether Catalyst’s 21 million ADA appears in the treasury balance, and final Epoch 666 transaction counts and block counts for the three pools. Check Koios epoch information.
  7. CAP review — Nov 12, 4 p.m. JST. Version 6 and the pending values. Check CAP-12 on the CAP portal.
  8. Node Diversity Workshop — Nov 12–13, London. Amaru’s milestone target is also Nov 12. Check the pragma-org/amaru releases page.
  9. Copper deadline — Nov 16, 6:44:51 a.m. Check the action’s page on gov.tools.
  10. TSC review — Nov 18. How to switch Leios off. Check the comments on CAP-12.
  11. PFMS and AURORA deadlines — Nov 21, 6:44:51 a.m.
  12. New constitution and guardrails submission — target by Nov 25. Check the Hard Fork Working Group minutes.
  13. EMURGO and Yoroi DRep deregistration — Nov 30. Any postponement can be checked on @emurgo_io on X.

Summary

This week, Midnight updated production by a different procedure than before. The reason for skipping Preprod stops at the words “security fixes,” and the content has yet to be explained. The project says balances and contracts migrated automatically, and developers were asked to move to Midnight.js 5 on a short timeline.

On Cardano, DijkstraNet began running on protocol version 12, while 11.2.1 for mainnet and 11.3 with Leios are still to come. As development teams change homes, the target for submitting the constitution sits at November 25.

In the treasury, Catalyst’s cancelled 21 million ADA came back on chain, and Committee votes changed the arithmetic on Copper and AURORA. PFMS heads to its deadline with Yes and No side by side. The proposals that will decide 2027 spending have yet to reach the chain.

Next week, after the Epoch 667 boundary, we will first check in Koios whether the 21 million ADA appears in the treasury balance.

References and Sources

Mentions of SIPO’s own articles are linked in place. The following are primary sources.

Transparency Notes

  • Votes on the three treasury actions: values from Koios at 9:30 a.m. JST on November 7. The denominator is explicit Yes plus amounts that act as No (voted No, not voted, always no confidence): Copper 4,358,252,259 ada, AURORA 4,094,269,311 ada, PFMS 5,065,397,759 ada. The Yes rate is Yes ÷ denominator, and the voted-No share is voted No ÷ denominator (Copper 2,435,272,253 ÷ 4,358,252,259 = 55.88%, AURORA 1,491,402,366 ÷ 4,094,269,311 = 36.43%, PFMS 1,360,454,436 ÷ 5,065,397,759 = 26.86%). The No rate returned by the public API includes not voted and always no confidence, so it is not used here. Abstain is excluded from the denominator.
  • Ceiling if non-voters vote Yes: arithmetic assuming delegations stay constant. Copper (17,976,508 + 1,773,436,735) ÷ 4,358,252,259 = 41.1%, AURORA (148,418,134 + 2,322,882,047) ÷ 4,094,269,311 = 60.4%, PFMS (1,260,493,755 + 2,312,882,804) ÷ 5,065,397,759 = 70.5%. This is not a forecast.
  • Committee votes: from Koios records. PFMS’s notation in Intersect Weekly Update #136 (1-0-0-5) differs from the on-chain record (2 Yes), and we use the on-chain record. Committee member names are not given in the text.
  • Ledger 9: from the announcement posts, the blog and the official support matrix. The announcement gives neither vulnerability names nor the time of the fork. We could not confirm a GitHub tag matching Node 2.1.101 in the matrix.
  • DijkstraNet date: Upgrade Bulletin #41, Weekly Update #136 and the Hard Fork Working Group minutes say November 2; the Cardano Operations Book says November 1.
  • CIP-23: the 11.2 entry in Weekly Update #136 names only Linear Leios as excluded, while Bulletin #41 and the minutes also exclude CIP-23. We follow the latter.
  • Catalyst’s 21,000,000 ada: from Koios transaction data (treasury_donation = 21,000,000,000,000 lovelace, 2026-11-07 04:57:07 JST, block 14,166,907) and the transaction metadata verbatim. Of 67,016 transactions in Epoch 666, this was the only one containing a donation. Reflection in the treasury balance remains to be confirmed.
  • cardano-node 11.2.1: checked against GitHub’s tag list at 9 a.m. JST on November 7. We do not call anything a “security fix” unless the release notes use the word security.
  • Rewards and treasury: the reward total is Koios’s epoch information value. The treasury increase is the difference between epoch balances (1,396,473,702.51 − 1,392,896,975.26).
  • Saturation estimate: a mechanical estimate dividing the on-chain circulating supply of 36,828,375,236 ada on November 7 by k. The three pool values are live stake taken just after the end of Epoch 665.
  • Market sampling times: October 31 at 6:35:08 a.m. and November 7 at 6:35:02 a.m. morning readings. ADA at the epoch boundary (−5.31%) is CoinGecko’s value at the boundary time.
  • SIPO’s interests: disclosed in the text are membership of the Nightforce ambassadors and possible eligibility for the opening of block production on Midnight; upgrades and BLS voting key registration being SIPO’s own work on node 11.2.1 and Dijkstra; having voted No on Copper, Yes on PFMS and Abstain on AURORA on the treasury actions; being one of five DReps named as examples and holding about 118.88 million ADA from 430 delegations in EMURGO’s announcement; having posted public comments on CAP-10 and the DRep Council draft; a 3.9% margin and 340 ada fixed cost across three pools, with the first pool above k=1000 saturation; and running a SundaeSwap v4 scooper.
  • What we did not write: speculation on what vulnerability Ledger 9 addressed, any claim that Amaru produced a block on mainnet (no such record), new cumulative Midnight transaction figures (no official announcement), Binance’s withdrawal status for ADA and NIGHT (could not be confirmed in text), press figures for the theft, forecasts on any action, and speculation on why any DRep voted as it did.
  • Prices and events: not linked.

This is not investment advice. For information and research purposes only.

Delegate to SIPO · 委任ガイド

ADA を手元に置いたまま、
SIPO に委任する

SIPO は Cardano ステークプール 3 基 (SIPO / SIPO2 / SIPO3) を運用しています。Midnight のバリデータ運用は開始後に参加予定です。

  • 預けない・ロックなし
  • 約 5 日ごとに報酬
  • DRep も SIPO に
ステーキングをはじめる → はじめての方は、この 3 本を順に読むと迷いません。
  1. 1
    📘 Learning ステーキングとは、ADA を手元に置いたまま報酬を受け取る仕組み 仕組みを知る →
  2. 2
    📘 Learning DRep への委任とは、13.7 億 ADA の国庫の使い道に一票を託す仕組み ガバナンスに参加する →
  3. 3
    📘 Learning 委任マニュアル 2026 年版、Lace と Daedalus でプールと DRep を選ぶ手順 手順どおりに委任する →