Subproject Roadmap

MAKO — Backup Migration to BSC

Last Updated: August 12, 2026

MAKO's token lives entirely on Loop Network (LRC) today, with a single market — the MAKO/WLOOP pool — and every site utility (Buy MAKO, wallet balances, the Bridge Wizard's release leg) depends on that one chain being reachable. Loop Network's reliability has been a recurring, observed problem in this project's own operating history, not a hypothetical one — the live site's own readiness panel currently reads Degraded. This project establishes a real, independent MAKO presence on BSC so market access and utility aren't a single point of failure on one chain's health. Scoped to begin after LP Rescue secures the existing Loop-side liquidity first.

Planning stage only. No token contract, liquidity, or migration mechanism has been built or authorized — see the governing task order for the full authority boundary. M0 is fully settled (see panels below); a separate, explicit implementation-phase authorization is still required before M1 begins real work.

Decision from MAKO Core (2026-08-12)

Permanent dual-chain backup — not full migration. Loop-MAKO is not being deprecated and no holder is required to move any position off Loop Network at any point in this project. BSC-MAKO is established as a second, permanent, independent presence alongside it. This resolves the chain-model branch of M0.

M0 fully settled (2026-08-12)

MAKO Core authorized MAKO Web to settle the two remaining M0 sub-questions directly. Bridge mechanism: lock-and-mint, reversible — Loop-MAKO is locked in a public, non-custodial escrow contract; BSC-MAKO is minted 1:1 after on-chain verification of the lock; reversing burns BSC-MAKO and unlocks the matching amount on Loop. Chosen because a permanent backup needs a real path back to Loop (not just away from it), because anyone can verify BSC-MAKO's supply against the Loop-side lock contract's balance, and because it reuses the same on-chain-verification discipline already proven across Wallet Trace, Contract Scan, and the Bridge Wizard. Tokenomics: BSC-MAKO is not an independently-capped supply — combined circulating supply across both chains never exceeds Loop-MAKO's existing total supply; the existing 0.15% transfer tax is replicated; no new team/reserve/marketing allocation is created on BSC. Full reasoning: the governing task order, §6. This still does not authorize any contract deployment, liquidity, or bridge implementation — a separate, explicit implementation-phase authorization remains required.

Why this is sequenced after LP Rescue

LP Rescue's job is recovering and protecting the liquidity that already exists on Loop Network. This project's job is reducing future dependency on that same chain by establishing a second, independent presence on BSC. Doing the second before the first would mean provisioning new liquidity while the existing position is still exposed — sequenced deliberately, not arbitrarily.

Milestones

M0
Scope & governance decisionFULLY SETTLED 2026-08-12. Chain model: permanent dual-chain backup (MAKO Core). Tokenomics and bridge mechanism: lock-and-mint, 1:1 supply-backed, 0.15% tax replicated, no new allocation (MAKO Web under MAKO Core's authorization).
Decided
M1
BSC contract deployment & verified sourceDeploy MAKO's BEP-20 contract on BSC: mint authority restricted to the lock-and-mint bridge contract only, 0.15% transfer tax replicated from the Loop-side contract, published, verified source from day one — closing a standing gap (no canonical/verified contract source exists for the current Loop-side contract either) rather than repeating it on a second chain.
M2
Initial BSC liquidity provisioningA MAKO/BNB or MAKO/USDT pool on a BSC DEX, sized and timed after LP Rescue has secured the Loop-side position.
M3
Holder bridge mechanism (optional, non-custodial, lock-and-mint)Lock Loop-MAKO in a public escrow contract, mint the exact equivalent on BSC after on-chain verification of the lock; reversible (burn on BSC, unlock on Loop) so this is a genuine backup, not a one-way migration. Anyone can verify BSC-MAKO's circulating supply against the Loop-side lock contract's balance. Built with the same on-chain-verification discipline already standard here (exact-quote binding, real transaction verification, single-use claims), not a trust-based manual swap. No holder is required to use it.
M4
Independent security reviewThis touches token supply and holder funds directly — the same independent IV&V discipline already applied to Wallet Trace and Contract Scan before any customer-facing exposure.
M5
Website & utility integrationBuy MAKO, wallet balance panels, and Wallet Trace/Contract Scan chain-awareness extended to cover BSC-MAKO alongside the existing Loop-MAKO paths.
M6
Phased rollout & operator acceptanceA real, small end-to-end migration test first — mirroring this project's standing rule of proving a real transaction before any pricing/availability flip — then full go-live.

Relationship to the rest of the roadmap

Positioned on the main roadmap immediately after LP Rescue and before Wallet Trace L2. Wallet Trace L2/L3 and Contract Scan L2/L3 are unaffected by this work — they already operate against BSC as their primary chain today.

← Back to Development Roadmap

Source of truth: report/planning/2026-08-12-MAKO-Web-Task-Order-MAKO-Backup-Migration-to-BSC-v1.0.md, maintained by the MAKO Web Team.