Subproject Roadmap

MAKOv2

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

Source POA&M last reviewed (docs/POAM.md): 2026-10-21 20:30 EDT

The next version of the MAKO token. Holders of the original MAKO will be able to move to MAKOv2 one for one, with no treasury allocation, and liquidity providers keep their share. MAKOv2 is built for BSC and Loop Network and connects to the MAKO Bridge and to the MAKO liquidity pools.

The token and its migration contracts are built and have passed independent review. Holder migration has not opened, and no MAKOv2 trading pool exists yet. Opening migration is gated on the steps below, each of which needs MAKO Core approval and, where marked, the operator's own written authorization.

Milestones

V0
Project establishmentRepository, charter, boundaries and plan of action. Done.
Done
V1
Original-token supply and ownership baselineTooling built and the first full capture of the original MAKO holder list is recorded. A regular series continues. Producing the one designated snapshot waits on independent review of the snapshot tool.
In progress
V2
Migration policy and allocation modelOne-for-one migration, no treasury allocation, liquidity-provider entitlements added on top, and direct claims retire the original MAKO. All policy decisions are made; the exact snapshot block is the one item left, set when the snapshot is designated.
In progress
V3
Token and claim contract specificationApproved by the operator and MAKO Core.
Done
V4
Local implementation and deterministic testingBuilt to the approved specification, with a full automated test suite and a reproducible build.
Done
V5
Independent review and deployment readinessFive rounds of review by an outside reviewer independent of the builders, each on an exact pinned version of the code. The fifth round passed on August 24, 2026 with no open critical or high finding.
Done
V6
Deployment and bounded claim pilotA small pilot among the operator's own wallets comes first, with verified contracts and reconciled evidence. It waits on independent review of the snapshot tool and on the operator's written authorization for the capture.
In progress
V7
Holder and liquidity-provider migrationPublished claims, the liquidity-provider process and supply reconciliation. Not started; follows the pilot.
V8
Canonical cutover and stabilizationMAKOv2 becomes the official token, deprecation notices go out, and monitoring and acceptance close the project. Not started.
V9
Utility reconfiguration and integrationReconnects the MAKO tools and partner utilities to MAKOv2 once the pilot has passed. Not started.

Scope and exclusions

In scope: the MAKOv2 token, the claim contract and snapshot tooling, the holder-facing claim page, the migration plan and its reconciliation, and the cutover from the original MAKO.

Not in scope: creating and operating the liquidity pools (MAKO Liquidity Pools), moving tokens between chains (MAKO Bridge) and the swap and payment features (MAKO PayFlow). MAKOv2 depends on each of these and tracks them, but they are separate projects with their own roadmaps.

What it waits on

Independent review of the snapshot tool before the one designated snapshot of the original MAKO holders is taken. The first MAKOv2 trading pools on BSC and Loop Network, built by MAKO Liquidity Pools and opened with a small first deposit. The operator's written authorization for the capture and for any live step.

Relationship to other projects

MAKOv2 is governed by MAKO Core. It works alongside MAKO Liquidity Pools, MAKO Bridge and MAKO PayFlow.

← Back to the Development Roadmap

MAKOv2 is responsible for keeping this plan of action and milestones current.