TrueBit's Silent Relaunch Sparked a $130M Bonding-Curve Scramble and Scam Rumors

The reappearance of the TrueBit protocol was surrounded by enough uncertainty that many in the community openly wondered whether it was a scam. No official announcement accompanied the launch, and no current media presence backed it up, leaving much of the community to piece together what had actually happened.

A Substack post from April 20th described TrueBit's goal as enabling smart contracts to run complex computations in standard programming languages at lower gas cost — a genuinely useful idea if it held up, which is part of why the murky rollout drew so much attention.

01Why the launch looked suspicious

Several factors fed the skepticism:

1. Development activity appeared to have gone quiet even as the protocol suddenly went live — though it later emerged the project maintained two separate GitHub accounts, TruebitProtocol and the more actively maintained TrueBitFoundation.
2. TrueBit's official Medium page did not clearly list a token contract address, prompting fears that the live contract might be an impersonator. The correct address was, in fact, listed in the FAQ section of the project's website.
3. The team's most recent public update was confirmation that mainnet had gone live on April 26th; before that, there had been no Twitter activity since January 25th.
4. There was no official Telegram or Discord channel for the project at all.

Combined with intense hype and promotion around the token sale, these gaps were enough to make people suspicious.

As Banteg described it on Twitter, the protocol had effectively soft-launched with limited access to its codebase, and only a handful of people worked out how to arbitrage the bonding curve contract — funneling around $130 million into the curve, which only bought back at one-eighth of the sale price.

That dynamic produced sharp price swings once users realized the token's price was not one-directional.

02The Vitalik connection, examined

Much of the hype rested on claims that the project had been "co-authored by Vitalik" Buterin. In reality, the TrueBit whitepaper, published in 2017, was written by Jason Teutsch and Christian Reitwießner. Vitalik is credited in an acknowledgment, not as a co-author — the "co-author" claim appears to have originated from confusion with a separate 2017 paper on ICOs that Vitalik did co-write with Teutsch. A TrueBit mention by Vitalik on ethresear.ch likely added further fuel to the hype cycle.

03Stealth launch, or something else

The founders had reportedly always intended a stealth rollout, but days after the token went live, significant uncertainty persisted. Comparisons were drawn to the earlier $CRV rogue deployment, raising the question of whether someone deployed the contract on the team's behalf, or gained unauthorized access to a private repository and forced the team to treat the launch as official after the fact. The only word from TrueBit at that point was a tweet promising a future Q&A session.

Confusion also surrounded the sale mechanics themselves. Many assumed a bonding curve had failed to hold its price, but the team never described the sale that way — the actual mechanism was TrueOS's mint/burn process. Users mint new TRU by supplying ETH to the TrueOS contract, with minting cost rising as more tokens enter circulation. TRU can also be sold back to TrueOS, which repurchases at 12.5% of the highest recorded minting price before burning the tokens.

04The May 2nd crash

Optimism held for roughly 24 hours of consecutive gains before turning to panic on May 2nd. One large TRU holder pulled their liquidity and sold roughly $465,000 of TRU on the open market. The market couldn't absorb the volume, triggering a cascade of panic selling that took the price from $1.40 down to $0.20 within about two hours. (Credit for this account of events goes to talleyrand.)

05Left unanswered

Without a direct explanation from the TrueBit team, it remains impossible to say with certainty whether the launch unfolded as intended. It's plausible the team's quiet approach was deliberate, consistent with a stated preference for building over promoting. But that silence appears to have amplified speculation rather than contained it, and a single clarifying statement early on might have prevented much of the confusion — even though the team bears no responsibility for how the market subsequently behaved. Whether the episode reflects simple miscommunication or something more deliberate remains an open question.