The experimental "X" architecture introduces sharding. However, sharding a TBSE-based state root is risky. Cross-shard transactions currently rely on a centralized notary pool (Phase 1). This reintroduces trust assumptions that the original TBSE was designed to eliminate.
Watch the v0.9.2 commit on GitHub. If they open the validator set to permissionless entry by Q3, this is a game changer. If not, "X" is just marketing. tbse-x
🔐 Security: They say "quantum resistant." I checked the signing algo. It’s still ECDSA on a twisted curve. No post-quantum signatures in the binary yet. That’s a lie by omission. The experimental "X" architecture introduces sharding
I’ve been tracking the development of over the last few weeks. While the marketing materials push the "next-gen" narrative, the technical architecture tells a more interesting—and nuanced—story. This reintroduces trust assumptions that the original TBSE
I ran a node for 72 hours. Here are the raw metrics vs. the whitepaper claims. 🧵👇
Here is what I found looking under the hood:
Looking into TBSE-X: Why is nobody talking about the "Validator Gap"?