🐛 The Bug: The consensus engine stalls when block height hits an odd number (Bug #TBSE-404). Devs patched it 6 hours ago, but the patch introduces a memory leak.
🚀 The Pitch: "Infinite scalability." The Reality: Max TPS topped at 4,200 before latency spiked. Good, but not "infinite." tbse-x
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. 🐛 The Bug: The consensus engine stalls when
Looking into TBSE-X: Why is nobody talking about the "Validator Gap"? Good, but not "infinite
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.
📉 Verdict: TBSE-X is an experimental fork (the X stands for eXperimental, not 10x). Don't bridge mainnet assets to it yet.
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.