Eskimo Coder

#ShowYourStripes

[Eskimo Coder @tuxkimo]

@ruggedpikachu The classic, how to say: "I have not the faintest idea on how Polkadot works, without actually saying it..." Come on, it is really not hard to diss Polkadot with arguments that make sense. No transactions on the relay chain ... wow, that's a shock. 🤦

[Eskimo Coder @tuxkimo]

@LayerZero_Core **Nothing here that a Polkadot architect wouldn't have considered.** The presentation is polished and the component-level engineering sounds ambitious, but the "multi-core world computer" framing is Polkadot's thesis with a fresh coat of paint and ZK underneath.

[Eskimo Coder @tuxkimo]

@LayerZero_Core I let this summarize for someone having worked on Polkadot parachain consensus for the last 5 years by Claude, its honest assessment section:

The architecture is **Polkadot's heterogeneous sharding model + ZK proofs instead of optimistic/dispute-based validation**.

[Eskimo Coder @tuxkimo]

@LayerZero_Core The main bet they're making that differs from Polkadot: ZK proving will become so fast/cheap that it's strictly better than Polkadot's "execute a subset + disputes" model. That's a reasonable bet for 2027+, but it's an engineering scaling bet, not an architectural innovation.

[Eskimo Coder @tuxkimo]

@LayerZero_Core The individual component engineering claims (QMDB, FAFO, Jolt Pro, SVID) are interesting if they deliver, but the overall system design is not novel — it's the parachain model where you trade Polkadot's lightweight validity mechanism for heavyweight ZK proving.

[Eskimo Coder @tuxkimo]

@seunlanlege Working on it. Not SASSAFRAS (which would not go far enough), but being resistant to relay chain forks (among other things) for perfect block confidence: https://t.co/xS6jSZ0e7V

[Parity Technologies @paritytech]

We’re pushing the limits of on-chain performance.

Join us for a live demo of a classic Web3 game running fully on-chain, powered by 12 @Polkadot cores and 500 ms block times.

No off-chain shortcuts. Just real throughput and real user experience.

🎥 Watch the demo ↓
👏 @sandreim_ , @remyGFLeBerre

[Dónal Murray @domuiri]

Today's the day! We're migrating all balances as well as governance and staking functionality (+more) from the Polkadot Relay Chain to Asset Hub. This is the beginning of the end of over a year of work

[RegionX @RegionXLabs]

Today, the first-ever purchase on a secondary Coretime marketplace was made on @kusamanetwork 🚀

Our marketplace—with full UI support—is now officially live on Kusama. This is a big milestone for us.

We’re the first—and the only—team to deliver a secondary Coretime marketplace!

[Bastian Köcher @bkchr]

I finally finished my smol block article about 500ms blocks: https://t.co/bhOsEkqP6p

[Nova Wallet @NovaWalletApp]

Nova Wallet 10.3 just dropped 🔥
What’s inside:
— Multisig push notifications (Polkadot, Kusama, PAH, KAH, Hydration & more)
— Swap GIGADOT, GIGAETH & aDOT
— Unique NFTs
— Upgraded staking, governance, proxies features
— Added cross-chain transaction safety checks
— Improved Mercuryo on-ramp

🎥 Full breakdown in the video — watch now!

[Alice und Bob @alice_und_bob]

Things I wish L2 teams understood ✌️

– zk over fraud proofs = unneccessary, just rent a Polkadot core
– 7d exit window = unneccessary, just rent a Polkadot core
– blobs or altDA bridge = unneccessary, just rent a Polkadot core

All these problems are already solved. Just switch to Polkadot. Your devs will thank you.

Focus on building the code that really matters, not reinventing the wheel.

[RegionX @RegionXLabs]

Big news — the RegionX Kusama parachain is live! We have purchased a core in the current sale cycle, which will be usable from the start of the next cycle

Until then, we’ll be using on-demand to test things out and have the first trustless resale of Coretime on @kusamanetwork 👀

[Eskimo Coder @tuxkimo]

@bkchr @dotlake_xyz @rphmeier @pierreaubert @99 Makes it even more questionable to include them in the metric. Would the data be "wrong" if we only included ready and if so, why?

[Eskimo Coder @tuxkimo]

@dotlake_xyz @rphmeier @pierreaubert @99 Questions:

1. Why future + ready ... shouldn't future become ready eventually? Thus aren't we double counting?
2. Why is it that bad, compared to block confidence?

[Eskimo Coder @tuxkimo]

@dotlake_xyz @rphmeier @pierreaubert @99 block confidence seems to be finalized/produced blocks. For validated it is: finalized/(ready tx + future tx). So it is not confidence of tx getting into block, but confidence of tx getting finalized. Which has to be lower than just block confidence.

[Eskimo Coder @tuxkimo]

@dotlake_xyz @rphmeier @pierreaubert @99 Do we know why validated confidence is that bad? High-level I would expect this to be much better than block confidence. Studying the metrics a bit, it looks like "validated" is ratio of finalized vs ready/future.

[Eskimo Coder @tuxkimo]

@IamDavidBrain The 1 DOT requirement is only on the relay chain. Luckily it is being worked hard to move everything to asset hub, where the existential deposit is only 0.01 DOT.

[Eskimo Coder @tuxkimo]

@csaint02 @Polkadot Those low TPS numbers is just chainspect not doing their job properly ... real numbers much higher. Fix already in the works.

[Eskimo Coder @tuxkimo]

@yuboruan @AcalaNetwork @DefiLlama @Polkadot Great to see numbers fixed that quickly! Hydration still missing?