Unlike its predecessor (TBSE), TBSE-X appears to be moving away from a monolithic ledger. The whitepaper suggests a modular execution layer . They are attempting to separate consensus from computation. If it works, we could see transaction finality drop from ~6 seconds to sub-second.
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.
🔐 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. tbse-x
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.
📉 Verdict: TBSE-X is an experimental fork (the X stands for eXperimental, not 10x). Don't bridge mainnet assets to it yet. Unlike its predecessor (TBSE), TBSE-X appears to be
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.
Has anyone else run a node on this? What latency are you seeing? If it works, we could see transaction finality
🚀 The Pitch: "Infinite scalability." The Reality: Max TPS topped at 4,200 before latency spiked. Good, but not "infinite."
💸 Fees: "Near zero." Average tx fee = $0.004. Actually impressive. But the mempool is only 20% full. Real stress test hasn't happened.
I ran a node for 72 hours. Here are the raw metrics vs. the whitepaper claims. 🧵👇