📢 Today’s Update
🔥 Tracking Swap Global Orders (private group) is back to normal operation.
🔥 Cardano Wallet Alert [@DCOneCryptoBot] is now active with LV5 support.
❌ Note: From version v1.0.4, the BOT will no longer send notifications for transactions below 2 ADA.
🔥 DCOne Swap Aggregator 2.0 UI is under finalization and remains operational (not available for Vietnam IPs) https://t.co/zdfhJQfSi4
🔥 DCONE Pool Active Stake: 1.9M ADA (sincere thanks to everyone 🙏) https://t.co/s31AKJhkGV
🔥 Midnight Node is being set up to participate in operations.
🔥 Fund15: The team is not participating.
🔥 Team donation wallet (pool wallet):
addr1qxtaxx699hhcymgusgze5jrumkalk3thc92e27zkrl3gsmml7ra5wekgmhpemqk85x85cm3szsqwcxwqhlpukhe8w4ksu7c03h
or $dconenode
Thank you to all of my friends who have been standing with us and supporting us throughout this period. Your trust and encouragement are a tremendous source of motivation for our team.
A special thank you to everyone who continues to support the DCONE Pool. We truly appreciate every contribution and will continue striving to deliver the best possible value to the community.
Thank you sincerely for your support! 🙏❤️
#ada
Hydra needs real products, real users, real feedback, real benchmarks and even real failures so we can learn and improve.
That’s what we’re trying to contribute with Hydra One.
Hydra is NOT a Layer 2 for every possible use case.
Hydra is strongest when applications need:
⚡ Low latency
⚡ High-frequency transactions
⚡ Near-zero fees
⚡ Fast settlement
⚡ Verifiable state transitions
That’s why we started building real-time application experiences on Hydra One:
🐉 Hydra Fly: a real-time skill game
🌊 River Cross: a provably fair risk/reward game with cash-out & proof verification
🎁 Hydra Gacha: a reveal/drop primitive focused on transparency & auditability
👉 https://t.co/Khk0rhgq27
These are not the “final use cases” of Hydra.
They are reference implementations to test what really matters: Can users connect a wallet, deposit assets, play, cash out, verify results, and move smoothly between applications?
Hydra One is also our attempt to make managed heads easier to understand and more trustworthy.
Managed heads should mean:
🔍 Transparent operators
📊 Clear system state
🧾 Verifiable proofs
🛡️ Clear risk assumptions
🌉 A visible exit path back to L1
That’s why Hydra Hub and Hydra One Proof Explorer are core parts of the stack.
Our goal is simple:
Move Hydra from “interesting technology”➡️ into a usable ecosystem. @sharan_konerira@v0d1ch@tony_thanh_@haiph_9
@adastackio Exactly. Nowadays, not only humans can easily visualize and analyze data through graphs, but AI agents can also greatly benefit from using graph-based structures to process and understand information more effectively. 😉
How much has your DRep actually committed to spend?
DAVEGov lets you see it directly. Connect your wallet or search any DRep to view their committed spend across the current budget cycle and prior periods.
You can also inspect how they behave, their mission. Voting patterns, participation, relative rank, and overall activity are all visible in one place. This gives a clearer picture of intent, consistency, and fiscal approach over time.
If governance is about accountability, this is where it starts, enjoy!
https://t.co/shf9XrXeeT
There is a clear overlap between Midgard and work that has already received funding, and in my view that needs addressing head on.
Hey @sharan_konerira, from what I can see so far, the Midgard scope overlaps with prior allocations from both Catalyst and treasury. Catalyst covered 500k ADA, with progress only shown up to January 2026 and sitting at around 60 percent. On top of that, treasury withdrawals from last year total 2.162 million ADA.
Looking at this practically, I am struggling to see output that lines up with that level of funding. I have not come across a working end to end demonstration that shows the system running in anything close to a real environment. The Intersect milestone tracker also shows the work running more than four milestones behind, with only the first milestone having actually drawn funds.
There are also signals from the repo itself. Activity has declined sharply, roughly a two thirds drop from its early 2025 peak, and more than halved compared to the late 2025 window. There are still commits in the last couple of weeks, so it is not inactive, but the development pace is now at its lowest point in the past 16 months.
At this stage I took some time to go through the code in the Midgard repo in detail and compare it against the milestones submitted to Intersect on the previous withdrawals.
From my own assessment, I do not believe the current state is sufficient to justify sign off, which might be why the funds have never been claimed and the Milestone's are still not closed. There is clearly engineering effort in place, but I cannot see any milestone that is complete, integrated end to end, tested, and deployable. The node is still not wired to the real contracts, fraud proof logic is actively being refactored, and there are open issues raised by the team themselves that point to fund locking and payout edge cases. The SDK and offchain components are still sitting in preliminary states, and there is no clear release process, testnet deployment, or CI pipeline that would give confidence in stability.
There are also some basic signals I would expect to see by this stage that are missing. No tagged releases, no public testnet, limited automated testing, and a growing number of open branches, open issues and PRs that have not been closed out (20 at this time). Combined with the continued slowdown in repo activity, it paints a picture of work in progress rather than something nearing completion or even in my opinion ready for us to commit more funds too.
To me, that creates a gap between what has been paid out and what can be verified. Over 2.66 million ADA has already been allocated across Catalyst and treasury withdrawals, and I do not yet see delivery that matches that level of spend.
On a more practical note, I also offered to help by posting updates and keeping the community informed. Phil said he would reach out, but that never happened, which was disappoint. That does affect my confidence in the delivery of this project. Communication is part of delivery, and right now my trust in the progress is increasingly reducing.
I would also welcome a formal statement on the above to clear this up, not just for me but for other DReps and delegates who are asking the same questions.
This is based on what I have observed so far, so if I have missed something, I am open to being corrected or pointed in the right direction.
I find it difficult to support further funding decisions without clarity on what has already been delivered.
I will review the new proposal on its own merits, but this context around prior funding and delivery needs to be clearly understood first.
We are currently using:
1⃣ Koios
2⃣ Ogmios
3⃣ Blockfrost
This order also reflects our usage priority and traffic distribution. We rely more on Koios due to their responsive and supportive team, along with simple and flexible APIs that can be adapted to our needs.
For Ogmios, we primarily use it for real-time data streaming.
As for Blockfrost, it is currently used mainly as a backup solution and for load balancing purposes.
🤝@MinswapDEX Aggregator now integrates @DanoFinance .
Most routes now flow through Dano - powered by concentrated liquidity for lower slippage and better execution.
Try it now!
More integrations coming.
@CardanoRami Your idea is quite good, and I agree with it. However, from my perspective, the 5% rate might be better adjusted to a lower level, as it could potentially have negative long-term effects on the system🙂
We would like to express our sincere thanks to @ItsDave_ADA for contributing the amazing open-source toolkit OgmiosDotnet, and especially the extended version OgmiosDotnet.BlockchainEvents built on the C# platform.
Building on this foundation, our team has continued to develop and expand with several key features. Beyond chain synchronization (chain sync), we have successfully integrated parallel mempool processing while still ensuring that all rules operate accurately and reliably.
This marks an important step forward—making the system more powerful, more real-time, and opening up new possibilities for community-driven applications.
🙏 Once again, thank you to the author and the open-source community for providing the foundation that allows us to continue building and contributing.
💙 If you find this work valuable, please support Pool DCONE to help us stay motivated and continue developing new features for the community!
📌 Source:
https://t.co/Io2GfeapZq
Let’s build a stronger Cardano ecosystem together! 💪
Breaking News
Cardano (ADA) has now been formally detailed by the SEC as a digital commodity, not a security today.
It is written directly into the Commission’s latest interpretive release. (Released Today)
A digital commodity is an asset that derives its value from the programmatic operation of a functional crypto system, not from the expectation of profits driven by the efforts of others.
ADA is listed alongside Bitcoin and Ethereum under that classification.
@lilybrodi@IOGroup It seems to be faster than using the Base network, right? From what I’ve seen, transactions on Base usually take around 20–30 minutes.
Happy 4th birthday to Minswap 🎂
From an idea by a group of Vietnamese students to build a DEX on Cardano to becoming a core piece of the ecosystem’s liquidity layer.
4 years of swaps, LPs, farms, and building through every bear, bull (and cat) market 🐈
Excited to see what the next chapter brings 😼