goku
@0xgoku_ • 4,922 subscribers
Shorts
Videos
12 years ago a guy comes up on stage at a small meetup to casually explain to maybe 40 people how they’re about to build systems that make nation states irrelevant over time (not in the sense that govs would collapse, but that for many economic and coordination functions, states would no longer be needed as the default authority) all while nursing a beer bottle throughout his talk the audience is shouting out answers, someone’s heckling about spelling, he’s mentioning about white powder and accidentally almost describes drug dealing, all laughs, then changes analogy to being a farmer in turkey and his wheat biz talk is generally about freedom, forces of nature, rethinking what law even means many projections made that year happened in some form actually: smart contracts/escrow, defi, daos, ens/did, oracles in 2026 tho, this is like watching early internet people talk about how the web would democratize knowledge and flatten hierarchies, and technically they are not wrong, but the version we got was facebook, twitter, tiktok, amazon and many other successful bizs
goku128,545 görüntüleme • 3 ay önce
Polkadot ran a major stress test, Spammening, in December 2024 to prove its infra can handle extreme txn loads in a live environment with real economic stakes. The result was 143K TPS, using just 23% of the network’s capacity. But the elephant in the room—does anyone outside of Polkadot even care. TPS is a tricky metric, especially today. Polkadot is a heterogeneous sharded blockchain and was used to be referred as layer 0. Essentially designed to orchestrate multiple chains in parallel, not maximize base layer txns. Therefore fundamentally it isn’t built for single-chain TPS races, but for very high throughput across multiple chains. So Polkadot’s TPS doesn’t compare neatly to monolithic chains, and that led to it staying out of TPS-focused optics in the past. As a result, it’s often misunderstood or seen as slow by this metric. And today, Polkadot has shifted from a chain-centric approach to a blockspace-centric one. It’s no longer about chains but about blockspace and cores—operating much like your multi-core computer. Aka, a chain can eat multiple cores if it needs more throughput. This is called Elastic scaling. With JAM and Elastic scaling, blocks can actually be split into chunks and validated in parallel, allowing the network’s parallel processing to directly impact single-state throughput. Reminder that this Elastic scaling is already live on Kusama and will be coming to Polkadot next quarter. Now, Justin Bons and @0xBreadguy argue that any sharded system can claim millions of TPS, but that doesn’t mean anything as it doesn’t happen within a single state—not equivalent to atomic composability. So, for this time, I’m tossing it to the gigabrains. Do they have a point, or is there more to consider. Shawn Tabrizi Gavin Wood rphmeier
goku16,687 görüntüleme • 1 yıl önce
Daha fazla içerik yok.