Subproject Roadmap

MAKO PayFlow V2 — Buy LOOP

Last Updated: October 21, 2026 at 08:55 PM EDT

Source POA&M last reviewed (docs/MAKO-PAYFLOW-V2-BUY-LOOP-POAM-V1.md): 2026-10-21 20:30 EDT

A swap feature: a user buys BSC-native LOOP with BNB, instantly or through dollar-cost averaging (DCA), and the purchased LOOP goes to the user's own wallet; the DCA path uses a narrowly scoped per-user holding contract and a relayer. On 2026-10-05 the scope was widened to also cover selling LOOP for BNB on BSC and swaps between MAKO and LOOP on Loop Network, with a minimum 1% fee to the deployer on every swap.

The BSC BNB-to-LOOP part is built and tested locally; nothing is deployed and nothing handles real money. It has passed an internal, non-independent pre-review. The project is parked by MAKO Core (YELLOW), and it is not ready for an independent review request. The new parts added on 2026-10-05 are demo-only so far and still wait on three open operator decisions (see below). Real-money operation needs a separate, later authorization (M11).

Milestones

M1
Requirements documentWritten and confirmed. Done 2026-10-01.
Done
M2
POA&MThe V2 plan of action and milestones. Done 2026-10-01.
Done
M3
Open questions resolvedPurchase caps, slippage, gas reserve, stuck-run timeout, alerting thresholds, relayer liveness approach and refund handling for a stalled DCA run were decided. Done 2026-10-01.
Done
M4
Live re-verification of LOOP/WBNB pool depthDone 2026-10-04. The pool is the only real venue and is shallow (about $59k total value); LOOP's 10% transfer tax was not re-confirmed because the public RPC rejected the log queries.
Done
M5
Design: per-user DCA holding contract (BSC)Cap enforcement, withdrawal and failure path, and the relayer interface. Done 2026-10-04.
Done
M6
Design: BSC-side relayerCron-driven, with permissionless slice execution; the hosting question is resolved as a 15-minute cron. Done 2026-10-04.
Done
M7
User interfaceFirst walkable version built 2026-10-05 in demo mode, with a simulated wallet, pool and contract. The MAKO side (M19) now implements its own buy/sell flow rather than linking out. As of 2026-10-14 the page (version 2.5.1) covered all three legs in one page and was verified by the operator in a click-through. On 2026-10-16 the page (now version 2.7.0) was frozen together with all three contracts and the stage cards; the operator gave written approval for both the card set and the page build. The independent review authority has acknowledged a second, corrected freeze pin. All six planned test windows on the operator's own machine are now complete. The counting test run on the automated runner has reported all three test groups counted (final, pending MAKO Core's reading): the two legs that ran cleanly passed their proofs, and the third — after running out of memory on the runner and being split into one slice per check — is now counted as a whole, with a single check left undecided (timed out, not proved false) under the review authority's own reading. A separate, longer tooling/mutation test run is also under way: its first of two parts is complete, with several results not yet confirmed safe to disregard; the second part is scheduled for the morning of October 21. Not connected to any real contract.
Frozen — all six test windows done; Halmos counting reported final on all three legs, awaiting MAKO Core's reading; tooling/mutation run in progress (1 of 2 parts done)
M8
1% fee collection and routingBuilt into each contract: 1% of the BNB/LOOP input (rounded down on buys, rounded up on sells and swaps) routed to the deployer wallet read from the register. Not deployed.
Built — not deployed
M9
Holding contract and relayer builtBuilt and tested locally 2026-10-04 (contract tests, real-pool fork tests and relayer tests passing). Nothing is deployed; a dry run on the real hosting runtime, alert delivery, and an operator-supplied submission endpoint are still open.
Built locally — not deployed
M10
Internal pre-review of the holding contractDone 2026-10-05; the reviewed candidate is frozen (the freeze was reissued 2026-10-10 with identical contract and tests). No review request is filed until the operator's written approval of the build exists. This review is internal and not independent.
Done
M10a
MAKO Core written spec acceptanceRequested 2026-10-05. Returned as out of date by MAKO Core on 2026-10-14; acceptance not granted. One request per leg (A BSC buy, B Loop swap, C BSC sell) will be refiled when PayFlow un-parks.
Returned — refile per leg
M10d
BSC deploy scriptDone 2026-10-05: built outside the frozen code, 82 tests, mutation 82 of 83 killed (1 justified equivalent), and a local fork rehearsal. A read-only plan against real BSC passes 27 checks and fails 1: the owner is not set. Not deployed.
Done
M10b
Blind pre-IV&V reviewA fresh session reviews through MAKO Core, then the readiness notice; the user interface is built and walked through first.
M10c
Independent IV&VA pass from the reviewer of record, issued and graded by MAKO Core; a gate PayFlow cannot close itself.
M11
Real-money authorization gateA separate, later operator authorization is required before any real-money action; this plan does not request it.
M12
Real, small-value end-to-end testInstant path first, then DCA. Go-live gate: the operator's own explicit words, not an inferred pass.
M13
Requirements and SDK documents finalizedFinalized against the real, built feature.
M14
Scope amendmentRecorded 2026-10-05: V2 now also adds BNB-to-LOOP selling on BSC and MAKO-to-LOOP swaps on Loop Network, with a minimum 1% fee to the deployer on every swap; the already-live LOOP-to-MAKO swap on Loop Network is the baseline.
Done
M15
Design and build: BSC LOOP-to-BNB (sell)Design approved 2026-10-10 (the contract pulls LOOP straight from the seller into the pool rather than routing through an intermediate hop); fork-tested against the real pair (16 of 16 across three runs) and formally verified (19 proofs, 8 controls). Contract (PayFlowSellLoop) written and tested 2026-10-10 (57 unit tests, 14 fork tests); a security baseline run passed (63 unit and 30 fork tests); mutation testing completed (120 mutants, 119 killed, 1 documented equivalent) and a claims ledger written (35 claims checked, ten findings recorded for follow-up). The operator approved the sell page build in writing on 2026-10-13 and approved the contract's flow card on 2026-10-14. Not frozen yet; nothing deployed.
In progress — design and contract built, not frozen
M16
Design and build: Loop Network swap contractBoth directions, 1% fee, pair-generic (pool read at time of use). Design approved; security baseline and a mutation-testing round complete as of 2026-10-05 (105 of 108 mutants killed, 3 justified equivalents; 65-test suite). A deploy script is also now built and tested (64 tests, 54 of 55 mutants killed), enforcing the registered fee receiver and signer and refusing to deploy without a MAKOv2 pool on Loop Network. The operator approved this contract's flow card on 2026-10-14. Not frozen; a full mutation run and baseline are still owed. Not deployable today — no pool exists yet (M17), and the Loop-side owner is not yet confirmed; which MAKO token to use and whether DCA applies remain open operator decisions.
In progress — design, tests and deploy script built, not deployed
M17
MAKO/LOOP pool depth on Loop NetworkNo MAKOv2 pool exists on Loop Network (2026-10-05). Owned by MAKO Liquidity Pools, MAKO-V2 and Bridge; PayFlow sets no depth requirement and deals with whatever is delivered. Waiting on other teams and on MAKO Core's response.
Waiting on other teams
M18
Route the live swap through PayFlow's Loop contractSo the live widget pays the fee (a MAKO Web change; PayFlow supplies the contract and an integration document). Blocked on an operator decision and on M16.
Blocked — operator decision
M19
One page for each pair and direction, both chainsFirst walkable version of the Loop Network (MAKO) side built 2026-10-05, in demo mode: buy, and sell with one signature; add/switch network; pool presets and a no-pool state. The old link-out to the live Buy/Sell MAKO widget has been removed in favor of this real flow. Still open: the operator's walkthrough of this side, a real wallet connected to a deployed contract and pool (the demo pool is made up), and a chain switch for Loop Network.
In progress — demo built, link-out removed
M20
Amended spec request to MAKO CoreCovers the whole expanded item and redraws the IV&V scope (several contracts, two chains); the first request is on hold. As of 2026-10-14 this is superseded: MAKO Core asks for one request per leg instead (M10a).
STD-1012
Verification and validation evidence package (IEEE 1012-2016)The evidence package that shows how this project's work meets the IEEE 1012-2016 standard for verification and validation. MAKO Core checks it is complete; it is not an independent verdict.
IN PROGRESS
STD-SCSVS
Smart contract security evidence package (OWASP SCSVS)The evidence package that shows how this project's contracts and page meet the OWASP Smart Contract Security Verification Standard, version 0.0.1. MAKO Core checks it is complete; it is not an independent verdict.
IN PROGRESS

Scope and exclusions

In scope: plain swaps with the purchased asset delivered to the user's own wallet; a minimum 1% fee to the deployer wallet on every swap; DCA with sign-once, autonomous multi-slice execution through a per-user holding contract and a relayer. BNB-to-LOOP on BSC is built locally; LOOP-to-BNB on BSC and MAKO/LOOP swaps on Loop Network are designed and built (not frozen, nothing deployed; see M15 and M16).

Not in scope: any liquidity-provision work (that belongs to the MAKO Liquidity Pools project); any real-money authorization (M11 is a real gate, not a formality).

Open operator decisions

Still open: how the already-live swap begins paying the fee.

Answered by the operator (2026-10-05 and 2026-10-10): no DCA on Loop Network; the fee is 1% of the amount in on buys and of the amount out on sells; the Loop Network MAKO-side swap uses MAKOv2 only, once a MAKOv2/WLOOP pool exists (the live original-MAKO swap stays up until that cutover); the existing price-impact limit is kept; this feature will live on PayFlow's own page, with MAKO Web pointing its Buy/Sell button at it at cutover; the BSC sell contract pulls LOOP straight into the pool rather than routing through an intermediate hop; and the unbuilt payment-collection design (PayFlow Collect) is shelved until a MAKO utility asks to use it.

Relationship to PayFlow V1 and MAKO Web

V2 is a separate document on the same project; V1's own milestones and blockers are unaffected by V2's status either way. Like V1, it is built and owned by the MAKO Posse Team as a standalone project and is not integrated into any MAKO Web utility by this team.

← Back to MAKO PayFlow

MAKO Posse Team is responsible for keeping this POA&M and all milestone status current.