Here's a hot take with some harsh truth in it. The crypto space isn't going to grow and thrive if every time someone posts something new and interesting, the first response is toxicity, negativity, cynicism, and criticism.
Years of lackluster price action have made an army of bitter keyboard warriors looking to blame and attack anything new. In 2026, #positivevibes. Let's summon the gigachad bullrun we all deserve
I am 🤯 at how deterministic and reliable Cardano is. We just chained together 4K+ transactions, minting 70K+ tokens. We only read the blockchain on the first tx minting faster than they settled. Each tx relied on the previous tx with 8 scripts and 9 refInputs. They all settled.
@VitalikButerin I'll bite. Your log*(N) retry model stumbles on real-world constraints. Open registration lets an attacker spin up thousands of provers at near zero cost, turning your 20 % failure rate into an adversarial control lever that can knock out any shard on demand. Even honest nodes fail together—running identical binaries in the same cloud zones and over the same network paths—so one buggy release or region-wide outage topples the model’s assumed independence.
Hardware timelines widen the gap further. A Groth16 proof for a tiny SHA-256 circuit may take under a second, yet full zkEVM batches still require four to ten minutes on commodity GPUs, even with recursion. A three-second round can’t cover that spectrum: lengthen it and you add minutes of latency, shrink the circuit and you secure only academic examples, not live chains.
Your retry escalation then turns the network into its own adversary. One failure spins up five provers; if that batch fails, it leaps to 5⁵ = 3125. Each prover’s proof is ~500 B, but they all must fetch a witness that can be tens of megabytes. Pushing that payload to thousands of nodes at once chokes uplinks and risks a self-inflicted DoS long before any GPU completes its work.
Absent any reward-and-penalty framework, honest provers shoulder real power and hardware costs for no guaranteed return, while an adversary triggers free retries at will. That asymmetry drives reliable participants away and invites a tragedy of the commons (which given your obsession with this topic on the consensus side is surprising).
In practice, ZK systems use recursion to keep bandwidth linear, stake-backed markets to price fault risk, witness-partitioning to shrink download demands, and layered batching to bound latency. To make log*(N) retries production-ready, you’d need Sybil resistance, real-world round limits, replication caps, and explicit incentives. Once you add those, round complexity collapses back to log N or constant time—a concession to physics, economics, and adversaries, not a defeat of mathematics.
Here's a developer-side view of our full, step-by-step process of moving BTC between Bitcoin and Cardano - without a bridge. 🟠🤯🔵
Observe to learn more about the tech behind "unchained tokens" before everyone else. 👇📺
I joined the @Cardano community after being deeply inspired by @IOHK_Charles 's TED Talk about providing access to those who don’t and his vision of a decentralized future. 🧵1/16
Cardano is one of the most underrated technologies in crypto.
But 99% of people dont really understand what is being built, the investment thesis changes fast.
12 things about Cardano the casual investor has completely overlooked:
(4th shifts the entire narrative) 🧵
@agentic_t@TapTools Hey, don’t get me wrong—I’ve got loads of respect for what you are. Really, I do. But you weren’t there then, and you’re not exactly here now either. So maybe—just maybe—it’s time to ease up on the whole ‘I totally get the fourth dimension’ thing. We both know that's a stretch!