It’s been a wild ride, but as @Cardano moves into a new era, we have to recognize what no longer fits its future.
Milkomeda will shut down in four months. Please withdraw your funds before September 1 (00:00 EST).
Any funds left after that deadline will be frozen.
1/2
It’s been a wild ride, but as @Cardano moves into a new era, we have to recognize what no longer fits its future.
Milkomeda will shut down in four months. Please withdraw your funds before September 1 (00:00 EST).
Any funds left after that deadline will be frozen.
1/2
Totally agree, and I’m not trying to be that guy—we're just trying to clarify a few things.
Nomad was an optimistic bridge, so it wasn’t actually centralized. We wouldn't have considered it Tier 1 if it were. When a bridge gets hacked, it’s not necessarily because it’s centralized or decentralized.
In Nomad’s case specifically, the issue arose when their team patched what was originally flagged by the auditor as a minor, non-critical bug—but that patch ended up introducing a critical vulnerability.
We wanted to clear up two misunderstandings once and for all:
1) Was Cardano the problem for Milkomeda?
2) Did Milkomeda ever have product–market fit (PMF) or even a chance at it?
Quick thread 🧵
1/3
2) I don't get Milkomeda. Did it ever had PMF (Product Market Fit) or even a chance of it?
It’s a common misunderstanding to treat Milkomeda as a front-facing user product. It never was.
You might hear, “I never used Milkomeda" or "I’d never had use it,” and that’s perfectly fine. Why? Because putting Milkomeda in front of end-users was mostly a marketing play to stay top-of-mind. So if that wasn’t the real product, what was?
Think of blockchains as countries. At the time, Cardano was a fast-growing nation with cool new projects but almost no connections to other “countries.” Milkomeda acted as the adapter—bridges, oracles, and other infrastructure —that linked EVM and Cardano’s eUTXO world.
That two-way link mattered. Milkomeda let Cardano projects trade with external chains and, just as important, let outside assets—especially stablecoins—flow into Cardano.
Some people checked DeFiLlama and thought, “Milkomeda flopped!” We looked at the raw asset flow through Milkomeda and saw those numbers climbing; our reaction was, “Wow, it’s actually working!”
- Ethereum users were getting exposure to Cardano tokens.
- Cardano users were finally accessing stablecoins on Cardano DEXes (not Milkomeda DEXes).
We felt things were on track, but crypto is risky.
The Nomad partnership
We partnered with the best Tier-1 bridge willing to work with us: Nomad.
Context: Many projects, VCs, etc., would shut us down the moment they heard “Cardano.” They’d decline before even opening our deck. That frustration wasn’t aimed at Milkomeda; it was blanket resistance to anything Cardano. We spent countless hours correcting misconceptions (“Cardano has no smart contracts,” etc.) and gradually made progress which made us pretty exciting about showing people something that they were not spotting.
Back to Nomad: everything looked great. Roughly $25–30 million in assets sat on Cardano, powering users who didn’t even realize Milkomeda was underneath. Cardano projects enjoyed extra liquidity from Ethereum traders buying their tokens. Then Nomad got hacked; most assets were never recovered, and there was no path back after that.
Milkomeda had multiple security audits—including full formal verification, the first Cardano project to do so—but that couldn’t protect us from a partner’s exploit.
With hindsight, we shouldn’t have partnered with Nomad, but at the time it felt like the strongest option. Nomad was leading Circle’s USDC CCTP, collaborating with Avail for data availability, strong team with proven experience, you name it—you can see why we chose them. Unfortunately, it didn’t pan out, and we’re truly sorry.
We share this context so it’s clear there’s more to the story than first meets the eye.
We had plans to add new VMs to Cardano and move beyond EVM and create a model where UTXOs could connect smart contracts from different VMs; Cardano is, after all, a multi-VM blockchain—but that’s a thread for another day.
End
3/3
1) Was Cardano the problem for Milkomeda?
No. If we could turn back the clock, we’d still build and deploy on Cardano. Developing on it was genuinely fun, and finding creative ways to use UTXOs was a blast—highly recommended.
2/3
It’s been a wild ride, but as @Cardano moves into a new era, we have to recognize what no longer fits its future.
Milkomeda will shut down in four months. Please withdraw your funds before September 1 (00:00 EST).
Any funds left after that deadline will be frozen.
1/2
Check out this beginner's guide to DeFi at https://t.co/Mr5W2c93of! 👈
Crypto-degens, join the referral program to teach your non-crypto friends and share a $4k prize pool 🍯 by Cardano Startup Index with @Blueshiftfi, @projectnewm, @TangleSwap & @DJEDalliance
This tutorial will show you how to use Yield Pool on Blueshift DEX! 🔗 Full guide here: https://t.co/U3VDxn5Y7F. Make sure to follow our YouTube channel. We post a lot of educational content around #DeFi there! ✏️
🎵 Breaking into the #Cardano Startup Index, NEWM sets a new rhythm with its music streaming marketplace. Stay tuned for the launch, as blockchain meets innovative tunes! 🚀 #NEWM#Cardano
Some C1 Bridge unwraps and wraps were stuck while the new added VOID token was pending liquidity
Once the liquidity was given everything started processing as expected
Please let us know if you have any problems. The bridge page shows everything processed 🫡
We have a release candidate for the frontend library fix.
We are coordinating with the @TangleSwap team to verify it and hopefully everything will be resolved soon.
Since yesterday, the indexer and the bridge have been up and running.
We still have some users reporting an error related to the calculation of 'upfront fees'. The team is working on updating the calculations in the frontend library used by DApps.
@coolwaves_22 They have been very helpful providing information to address the issue. We just released a candidate fix for them to try it out and hopefully later today it may be fixed.
Since yesterday, the indexer and the bridge have been up and running.
We still have some users reporting an error related to the calculation of 'upfront fees'. The team is working on updating the calculations in the frontend library used by DApps.