Phase 1
Smart contract development
-
The deposit and yield contract written and deployed to BNB Smart Chain.
The contract exists at a public address with verified source on BscScan.
TurboLoop publishes its roadmap as phases, six of which are marked complete. Some of those completions leave permanent on-chain evidence. Others are claims about activity that no one outside the team can confirm. This page keeps the two apart.
Verifiable means you can confirm it yourself on BscScan or in a published report, not that we vouch for it. Stated means it is plausible and undocumented outside the operator’s own pages.
Phase 1
The deposit and yield contract written and deployed to BNB Smart Chain.
The contract exists at a public address with verified source on BscScan.
Phase 2
Independent audits completed and published.
HazeCrypto published a full report. SolidityScan scored 99.99 with zero critical, high, medium or low findings.
Phase 3
Contract ownership permanently renounced.
owner() returns the zero address. Irreversible, and checkable in seconds.
Liquidity pool tokens locked on-chain.
The pool address and its balances are public and readable at any time.
Phase 4
The protocol opened to deposits.
Deposit and payout transactions against the contract are public from launch onward.
Phase 5
Telegram, Discord and X channels established.
Multilingual onboarding and support material produced.
Phase 6
Regional presence across fourteen countries: local-language hosts, Telegram groups and paid creators.
A standing $100,000 bounty for anyone demonstrating centralisation, an admin backdoor or an upgrade path. Zero claims paid to date.
The absence of a successful claim is not proof of safety, only that no one has publicly succeeded.
Creator Star programme paying approved creators per video.
Content library past 28 videos across roughly twelve languages.
Phase 7
Improved Turbo Swap routing: multi-hop paths, better fills, tighter slippage.
Research into additional plan variants, in separate contracts alongside the existing four.
Early cross-chain research, framed by the operator as exploration rather than commitment.
Referral and leadership reporting tools, dashboards, downline trees, exports.
A mobile app, per the other roadmap article.
Phase 8
Deeper language coverage beyond the current twelve.
Richer Telegram tooling.
User-facing on-chain analytics.
Cross-chain expansion, per the other roadmap article.
Phase 9
Community governance over the ecosystem layer.
The operator publishes more than one roadmap post, and they do not match. One assigns the mobile app to Phase 7 and cross-chain expansion to Phase 8; another describes Phase 7 as swap routing, plan variants and cross-chain research, with Phase 8 covering languages, Telegram tooling and analytics. Both are listed above rather than picking a winner. Treat phase numbering past 6 as a theme, not a schedule.
Phases 1 to 4 leave permanent evidence. The contract is deployed and verified, the audits are published, ownership is renounced, the launch happened. You can confirm all of it without asking anyone, and that is a stronger position than most protocols in this category can offer.
Phases 5 and 6 are activity claims: country counts, video counts, an unclaimed bounty. They are plausible and mostly unverifiable from outside. Nothing here depends on them being exact.
Phases 7 to 9 are intentions. Cross-chain, a mobile app, a DAO, these appear on nearly every roadmap in the sector and most never ship. Give them no weight in a deposit decision.
One thing the operator states repeatedly and that does hold up: everything planned is additive. The deposit contract is immutable and ownership is renounced, so no future phase can change the terms of a loop that is already running.