I've watched this exact mismatch kill the narrative on more than one solid project, and Babylon is living through it right now in real time.
David Tse's academic background is information theory and cryptographic security, the kind of discipline that models adversarial behavior over decade long time horizons, not quarterly vibes. That pedigree shows up directly in Babylon's slashing design and its remote staking security proofs, work built to survive a multi cycle adversary, not to pump a token chart in week one.
Then TGE happened and CT did what CT does. Instead of evaluating whether the cryptoeconomic security model holds under stress, the timeline filled with people doing back of envelope math on six month BTC staking yielding something like 0.6 percent annualized in early epochs, and airdrop allocations getting compared unfavorably to a random NFT floor price from three months prior. The complaint was never about game theory soundness. It was about number not going up fast enough for a degen holding period measured in days.
This is the actual tension worth sitting with. A protocol engineered for BTC's decade plus security horizon is getting graded on a weekly PnL screenshot standard, and those two timeframes are not the same instrument at all. Slashing conditions, covenant committee thresholds, and finality gadget robustness matter more at year three than at week one, but week one is when the loudest reviews get written.
The market that eventually rewards this kind of design is not the one screenshotting APY on day seven. It is the one still checking delegation health and BSN uptime in 2027. BABY's value accrual thesis depends entirely on which crowd sticks around long enough to find out which timeline was right.
@BabylonLabs_io $BABY #baby