AdaStat.net 💎 Cardano Explorer • SPO • DRep

JUST IN: Kraken registered 12 Cardano stake pools in June, reportedly holding around $1B worth of $ADA. 🤯 That's not a small move. More eyes are turning to Cardano, and the ecosystem is getting harder to ignore. Something is brewing. 👀

van Rossem hard fork update 🍴 The hard fork initiation action was ratified at the epoch boundary on July 13, 2026 at 21:45 UTC. Voting Result: ✅️ DReps: 77.63% / 60% ✅️ SPOs: 52.7% / 51% ✅️ CC: 6 constitutional, 1 did not vote Following ratification, enactment will now take place on July 18, 2026 at 21:45 UTC. This is a final call to action for anyone yet to update their infrastructure to a hard fork compatible version to do so as soon as possible. Thank you to all DReps, SPOs and CC members who voted. 🗳️ *no other governance actions were harmed during this ratification

⚠️ Following ratification, enactment will now take place on July 18, 2026 at 21:45 UTC. This is a final call to action for anyone yet to update their infrastructure to a hard fork compatible version to do so as soon as possible. ⚠️ NORTH v10.6 ₳312.53M @nordicpool BLOOM v10.6 ₳144.91M @bloompool_io PILOT v10.6 ₳90.53M @ada_pilot PPTG1 v10.6 ₳89.99M @Tangem P2P/PPCX1/P2P2/PPCX2 v10.6 ₳78.32M @p2pvalidator DARK v10.6 ₳70.85M @AdaDarkpool ADAST v10.6 ₳36.96M @adastrongpool LOVE v10.3 ₳22.72M @PooltoolI MORH v10.3 ₳18.29M @MorhPool PSB v10.6 ₳17.69M @PSILOBLOX RSNG v10.6 ₳13.91M @InfinityRisingX BREAK v10.2 ₳13.04M @breakingada DCONE v10.6 ₳9.19M @DCOneCrypto YOON v10.3 ₳8.80M @youradamoon SNEK v10.6 ₳8.75M @snek FARM v10.2 ₳8.34M @ADAFarmio CLAY v10.6 ₳8.06M @claymates BLOCK v10.2 ₳7.32M @KBlocks_ADA ZEIT v10.2 ₳6.56M @zeitgeistpool ASTRA v10.2 ₳6.14M @AstraStake PXLZ v10.2 ₳5.67M @pxlzNFT BRADA v10.7 ₳5.25M @bradapool WRM01 v10.8 ₳4.92M @wingriderscom MYB v10.2 ₳4.81M @Miyabi_Kyoto_ CANUK v10.2 ₳4.18M @CanadaCardano 1112 v10.3 ₳3.49M @6ietbl6fnlnny1s 4GOOD v10.6 ₳3.36M @4GOODStakePool EPOCH v10.7 ₳3.17M @EpochPool KSP v10.6 ₳2.55M @ksp144927 ALDIA v10.2 ₳2.18M @cardanoaldia 307 v10.2 ₳2.02M @ShoshoniTony ALLEY v10.6 ₳1.96M @AlleycatMining KAPY v10.6 ₳1.81M @kapypool MUGGY v10.6 ₳1.80M @muggy_pool OMNI v10.6 ₳1.80M @omnidevops APP v10.6 ₳1.67M @Ada_Point_Pool A3C v10.2 ₳1.61M @A3Cpool_shawn PEPE v10.6 ₳1.51M @official_coder TREK v10.2 ₳1.47M @stakeTREK IAMX v10.2 ₳1.32M @IAM_X_IDENTITY VICE v10.6 ₳1.25M @vicestakepool AMINT v10.7 ₳1.21M @CardanoMint NIGHT v10.2 ₳1.07M @MidnightNtwrk AZTEC v10.2 ₳1.06M @AztecStaking GERO2 v10.3 ₳1.04M @GeroWallet adatool.net/spo-versions

Cardano peeps, the van Rossem hard fork has met all threshold approvals and will execute! Congratulations 🥳 Fully on-chain, decentralized governance, in action.

Got it. The reason I was confused is that whenever I hear "federated nodes," I immediately think about block production, not governance. That's how it worked during the Byron era, up until 2021, when block production was centralized and stake pools didn't exist yet. I think what you actually mean is centralized governance keys - the Shelley era after Byron, before CIP-1694 introduced decentralized governance with DReps, the Constitutional Committee, and everything that came with it. Personally, I don't think we need to go back to federated governance. In my opinion, that would actually make things worse than they are today, because it would create even more uncertainty. That said, I completely agree with your broader point that some degree of centralization is necessary. Not everything can/should be decentralized. For example, the goal should be unified: something the community broadly agrees on, with proposals serving as different ways of achieving that shared objective. Without that, everyone ends up pulling in their own direction, and the result is very little real progress. That's the part I believe we still need to figure out together.

Fair question. I'm not chanting “centralization forever.” It’s just that when governance becomes captured, slow, and unaccountable, pretending the current structure is sacred can do more damage than a temporary reset. Federated nodes under IO guidance would not magically fix governance by itself, but it would create a stabilization period where technical execution, treasury controls, and ecosystem priorities can be cleaned up without every decision getting dragged into political theatre. In other words: pause the dysfunction, restore clear accountability, audit spending, tighten leadership, then decentralize again from a healthier base. Decentralization only works when the incentives and institutions around it are strong enough to support it. If they are broken, you don’t get freedom. You get a bad system.

Cardano’s governance experiment is broken. Not “imperfect.” Broken. And to be clear, the tech is astounding. Cardano’s research, engineering, security model, and long-term design are still some of the best in the industry. But everything around the tech needs work. I have a lot of respect for many people in #Cardano. Some of the smartest, most principled people I’ve worked with are still in this ecosystem. But, that being said, I also have the exact opposite view of many others who have treated governance like a game, a gravy train, or a personal brand exercise. The only era where Cardano clearly excelled was under the old model, with tighter technical leadership and proper direction. Since the handoff, governance has become slow, political, sloppy, and too easy for insiders and loud voices to influence. The market sees it. The community sees it. Confidence has been bleeding out in public. Great projects have fallen to this exact problem before: incredible tech, poor incentives, captured governance, and no real accountability. Others survived because they made the hard calls early enough. Cardano still can. But the answer is not another round of committees, town halls, budget games, or decentralization cosplay. Cardano needs a reset. Bring back federated nodes under proper IO guidance until the chain and ecosystem are stabilized. Audit every major treasury spend from the last 3–5 years. Show who got paid, what they promised, what they delivered, and what remains. Any funds taken without real delivery should be returned. Prune the founding entities where needed. Clean up the conflicts. Stop pretending every legacy structure deserves to survive just because it has been around for years. Put adult treasury controls in place before spending another ADA. And put focus back on traders. Traders are not the enemy. They are liquidity, attention, distribution, price discovery, and market signal. Ignore them long enough and you do not get a purer ecosystem. You get an irrelevant one. Stop building in hostile or Trojan horse environments that clearly do not serve Cardano’s long-term interest. IO carrying Cardano and Midnight is a lot. No question. But Cardano needs accountable leadership more than it needs more governance theatre. Hard calls are overdue. I understand that this probably won't be a popular opinion on here, but it's honestly how I feel. #Cardano #Governance #Community #Growth

updating CML to support the latest hardfork (alternative for people wanting to move off of EMURGO's CSL library) Spent 3 subscriptions to Fable improving the testing framework around CBOR/CDDL/codegen to ensure the upgrade doesn't introduce a bug Want to contribute? DM me!

@CoinMarketCap So far, so good. The Musashi Dojo opened its doors. That's the Leios public testnet: years of peer-reviewed research on scaling Cardano, now live and open for anyone to test. leios.cardano-scaling.org

In my opinion, EMURGO did not have to leave Pentad because of the unfortunate SecondFi incident. Instead, they could have announced the sunsetting of the Yoroi/SecondFi wallet and retired as DRep. EMURGO + Yoroi together are the strongest DReps with huge voting power. Retiring Yoroi DRep would be a much more responsible approach from an accountability and decentralization perspective than giving up Pentad duties. Pentad is not transparent, so I cannot assess how EMURGO contributed. I expect the remaining Pentad members to comment on this. DReps approved the budget for Pentad, so the community deserves to know what the consequences of EMURGO leaving will be. I see no connection between Pentad duties and the SecondFi incident, so I don't really understand EMURGO's reaction. I am all the more curious about the next announcement. What is your opinion on this?

Funny fact: "Reduce the committeeMinSize parameter from 7 to 5" proposal might become Invalidated for the third time ever, and the second time in this voting round alone.

I'd say that's perfectly normal, and exactly what we expected. That's why we didn't simply replace the old UI with the new one. Instead, we decided to keep both and let users choose which one they prefer. Right now, our goal is to make sure that everything users are used to in the Classic UI is also available in the Modern UI. Once we get there, the Modern UI will become the default, while the Classic UI will still remain available as an option. Then, after some time (I expect quite a long time), the Classic UI will gradually be phased out, leaving only the Modern UI.

When I first saw the new @ada_stat design, I hated it, but now I'm used to it and I like it more than the old one. Still miss some of the functionalities of the old one though, but don't want to miss out on new functionality of the new design too.

Omg... Thank you for letting me know @HephyPool I genuinely don't understand why this sometimes doesn't work. I've tried every combination with Wants/BindsTo/After/etc. Most of the time it behaves exactly as expected. But every now and then, something goes wrong and the service just doesn't restart. At this point, I think it's time to call a shaman :)

If you've upgraded recently, remember to restart your Mithril Signers when you restart your nodes 🫡 @NordicPool @ada_stat @CryptoJoe101

ZK Verification Technical Workshop Join Input Output Research (IOR) for a deep dive session into zero knowledge (ZK) verification infrastructure for Cardano, covering: 🧠 Proof-system design 📐 SNARK standardization 🛡️ Hydra Tail security 📍 Google Meet 🎟️ Register: luma.com/l0lc5mx5

We’re LIVE again! Come join us! x.com/i/broadcasts/1…

We need SPOs. We need builders. We need DApps on the Leios testnet. You're the ones who'll tell us how it performs, where it breaks, and what to refine. Every round of feedback brings the end-of-year mainnet upgrade closer. Enter the Dojo: musashi.network

@JaromirTesar Unpopular opinion: we don't need NCL

We need to have a strategy and be able to prioritize before approving the next NCL. ADA allocations should be planned in advance. Without this, approving the NCL will just be another raid on the Treasury. Now is the time to talk about it.

@NFTbyND @niang_whale @strikeperps @StatsAda Yeah, that seems likely. But in any case, it's probably worth checking.

@ada_stat @niang_whale @strikeperps @StatsAda Yeah its probably just a cache bug on his end

DO YOUR HOMEWORK!!! DO YOUR HOMEWORK!!! DO YOUR HOMEWORK!!! If you trust @strikeperps you can still delegate your $ADA to other drep if your delegated drep voted no or abstain! Link: adastat.net/governances/87…

van Rossem hard fork update ⚙️ As we approach the final 12 hours of epoch 640, a look at the current hard fork status - 89% block production on node version 11 - 80.21% exchange readiness by liquidity - Hard fork working group has voted to formally recommend ratification Voting Status: ✅️ DReps: 66.57% / 60% ⏳️ SPOs: 43.75% / 51% ⏳️ CC: 1 constitutional , 6 yet to vote ⚠️ SPOs must explicitly vote yes/no/abstain on hard forks. Auto-abstain will count as a NO vote otherwise. SPO voting guide: developers.cardano.org/docs/operators…

@Cointelegraph Leios. Years of peer-reviewed research on scaling Cardano, now live on public testnet. leios.cardano-scaling.org

@NFTbyND @niang_whale @strikeperps @StatsAda Hmm, that's very strange... For me, it looks like this:

@niang_whale @strikeperps @StatsAda I meant @ada_stat , check this out please