The hard fork initiation action was ratified at the epoch boundary on July 13, 2026 at 21:45 UTC.
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.
AI on Cardano Update
Last week we had our first ever "AI on Cardano" call for everyone interested in this topic.
The goal of this forum is to
- Establish a platform to talk about AI developments, discuss standards, form working groups and present work
- Establish Cardano as the Nr. 1 Blockchain when it comes to AI development
- Foster more collaboration
In the first call we mostly went over whats currently happening on other chains, what this forum should be used for and a brief introduction.
@masatoalexander I'm serious and sincere. I think I'm missing something. Indexers seem to be the obvious answer here. Pretty sure Cardano has a bunch of them. Some easier to extend than others. Whats missing?
3/3
Trying to ratify the affected proposals before the HF is an option. Sorting them out after the HF applies is also.
Sure it will be cumbersome post HF but we need to keep in mind that WE, DReps, SPOs, governance action authors and everybody holding ADA now make the calls!
> Treat the submission date as part of the proposal itself, not as an administrative detail added at the end.
True. We are learning a lot of things with this hard fork. But this is not a blocker (1/3)
2/3
This is a critical moment for all the proposers of the affected actions, no question. What needs to be done is also in their hands and Cardano as a Community can help.
GM. We are preparing the launch of the Masumi Payment Service version 2, which will include:
- V2 Smart Contract, with better batching - Hydra Integration
- x402 aggregation across multiple chains
- Cardano Registry update to support different agent standards
- Agent Identity
Huge update incoming.
> we have secured approximately 129 million ADA as part of our broader containment and asset protection response.
Can somebody knowledgeable with secondfi's wallet architecture explain to me how a Blockchain Wallet author can do that? Are they just bruteforcing the exploit?
🧵1/3 Calling all single pool SPOs. @realfi_co is preparing its launch in Cardano and we are exploring a Single Pool Accelerator with selected single pool operators.
This may be the help you’ve been looking for. For anyone new to it, RealFi connects on-chain capital to real-world markets through a stablecoin designed to be backed by US Treasuries, money market funds, and private credit.
If you’re a single pool operator with roughly 1M to 12M ADA delegated, please register an expression of interest via the form I’ll link in the thread below. This is research, not an offer.
If you think single pool SPOs should help shape the RealFi launch in Cardano, please RT and share.
@txpipe_tools > the block we want: a (slot, header hash) point
How come it always is a slot+hash combination in most cardano libs I see. Isn't the hash enough?
@FurkanCCTV@sunnydecree Wir haben super viele deutsche Cardano Startups, darüber habt ihr noch nie geschrieben. Statt dessen wenn's mal Drama gibt direkt aus den Löchern kriechen. Unglaublich echt.
🚨 Service announcement! 🚨
Diffusion holders have until the end of this week to cast their vote on the Diffusion delegation strategy governance proposal!
This is a critical vote deciding future staking yield, so time to participate!
All info can be found in the post below 👇
Great news!
We updated our Diffusion Staking Basket UI to also reflect additional NIGHT and ATMA token rewards!
If you hover over the APY, you'll get a breakdown of the full APY details.
Based on current token valuations, you're earning around 4% staking APY with Diffusion! 🔥
Yaci Store 2.0.0 is now live.
Get reliable access to Cardano blockchain data, with improved ledger and governance state derivation, a new plugin framework, and production-grade performance improvements.
Built to support resilient Cardano DApps.
https://t.co/Nj9zx5IbxR
@MicheleHarmonic Sure, UTXOs don't lock each other out but in the context of a validator I can imagine the case where you would want existing UTXOs to be interacted with in a specific order. What's wrong with business or legal reasons being encoded in a smart contract? Isn't that what they exist?