Subproject Roadmap

Bridge Wizard — Cross-Chain Market-Swap Bridge

Last Updated: August 15, 2026

A non-custodial market-swap bridge: the operator sends BNB or LOOP on BSC, it is locked, released as WLOOP on Loop Network (LRC), swapped for MAKO through the MAKO/WLOOP pool (0xba8AcEe49eA398b813CEd49A547c70077956934B), and delivered to the operator's wallet — no pooled reserve, no LP custody, no held inventory. Built by the MAKO Posse Team; feeds stages 2 and 3 on the main roadmap (BNB entry and LOOP entry are two doors into the same engine), but tracks separately.

The core swap engine was built and proven live on-chain in March 2026 (a real 5-slice run, 100 confirmed executions, real MAKO delivered). It was subsequently taken offline during an anti-custody governance pass in April/May 2026 and has not yet been restored to production. Restoration, plus the gaps identified alongside it, is scoped under Bridge Wizard POA&M V6 (2026-08-09).

Update from MAKO Posse (2026-08-09)

A full review of this subproject's history found the underlying bridge engine had already been built and proven — real on-chain execution, real MAKO delivered, in March 2026 — before two governance-driven changes took the execution path offline in April and May 2026 while hardening custody safety rules. The capability was never lost technically; it was intentionally disabled and never re-enabled. Alongside that, three further gaps were confirmed: a revenue-split ("toll") mechanism was built but never connected to live execution; a live price-impact calculator was built but never connected to the slice-sizing step (runs always used a fixed size instead); and the wizard has never supported starting from BNB, only from LOOP directly. A corrected plan (POA&M V6) now governs closing all four gaps together before this goes back into production, plus new work to keep runs going through Loop Network RPC outages rather than failing on them.

Update from MAKO Posse (2026-08-15)

Both M1 contracts are now live and connected on Loop Network mainnet. The swap-execution contract's deployment (paused yesterday by a temporary RPC outage) completed, and the two contracts have been wired together for real — a one-time, irreversible on-chain step, independently re-verified afterward. The wizard's configuration now points at both live contracts. What remains before this milestone is proven: a real, small-amount end-to-end run through the actual wizard interface, watched start to finish.

Update from MAKO Posse (2026-08-14)

Real build progress across four of the milestones below, all still ahead of deployment. The M1 contract now has a full local test suite passing (24/24) and a ready deployment runbook. A gap was found in the live wizard: it was actually asking the operator to sign three separate transactions, not the one or two the design calls for — the fix is built (an automated relayer that removes the two unnecessary signatures, and a rebuilt wizard interface down to two buttons total, with automatic progress after the single lock signature). The RPC-outage-resilience design (M5) is also built. Deployment has now started for real: the relay contract is live on Loop Network mainnet as of today. The second contract is mid-deployment, currently paused by a temporary RPC outage on Loop Network's public endpoint (not a code issue) — resuming once that clears.

Milestones

M0
Baseline reconciliationCorrected the project record: confirmed what was proven live, exactly when and why it was disabled, and locked the milestone list below.
Done
M1
Restore execution path — redesigned, not reconnectedThe disabled worker required a private key with standing, unattended authority — rejected as unacceptable. New design: a permissionless contract where safety comes from on-chain checks (live price-impact floor, minimum-interval cooldown, immutable recipient), not from trusting whoever calls it. Both contracts are now live on Loop Network mainnet and wired together for real. What remains: a real end-to-end proof run through the actual wizard interface.
In progress
M2
Dynamic price-impact sizingNow enforced directly inside the M1 contract — each slice is checked against the live pool reserves before it can execute, not a separate wiring step.
In progress (part of M1)
M3
Toll enforcement wiringNow implemented directly inside the M1 contract — every delivery splits treasury/LP builder fees before paying the operator's net amount, matching the pattern already proven for the release leg.
In progress (part of M1)
M4
BNB entry legAdd the BNB→LOOP conversion step so an operator holding only BNB can complete the full journey to delivered MAKO without acquiring LOOP separately.
M5
RPC-resilient executionEach delivery step waits out a Loop Network RPC outage rather than failing — it resumes automatically once RPC is live again and continues until the full amount is delivered. Design and implementation done (a liveness guard that holds and resumes rather than failing). Not yet proven against a live deployment.
In progress
M6
Minimum-signature verificationConfirm the operator signs only what moves their own funds (the BNB→LOOP swap, if used, and the BSC lock) — nothing further is signed for release, swap, or delivery. A review found the live wizard actually required 3 signatures, not the intended 1-2 — built the fix: an automated relayer that removes the 2 unnecessary ones, and rebuilt the wizard to a 2-button flow with automatic progress after the one lock signature. Not yet exercised with a real wallet.
In progress
M7
End-to-end acceptance testA fresh, dated, pass/fail acceptance report covering the complete BNB→MAKO path with every milestone above in place, to the same evidence standard already proven for the basic lock/release leg.
M8
MAKO Web handoff packagePackage the Wizard as a clean utility interface — not the internal operator dashboard — for the MAKO Web Team to integrate into the live site.

Relationship to MAKO Web

This roadmap covers the MAKO Posse Team's own build/restoration work. Once M0 through M8 are complete and independently verified, the Bridge Wizard will be handed to the MAKO Web Team for integration into the live site, following the same request/answer/POA&M handoff pattern already used for Contract Scan. It does not yet appear on the live site — this page tracks the work required before that handoff can happen.

← Back to Development Roadmap

Source of truth: Bridge Wizard POA&M V6 (2026-08-09), maintained by the MAKO Posse Team.