Subproject Roadmap

MAKO Harvester V2

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

Harvester is a self-hosted automated farming and liquidity-pool harvesting tool for LoopSwap. V2 expands to staking-pool support, adds scheduled harvest-readiness checks, enables Binance-relay off-ramp to Coinbase for multi-exchange users, and introduces a symmetric add-funds flow alongside harvest automation. Built by the MAKO Posse Team; fully production-authorized for V1 end-to-end, with V2 phases phased under security isolation and verification gating.

Milestones

P0.0
Development isolationAll V2 work on dedicated git branch with separate Vercel Preview Deployment and Upstash Redis database, protecting production users before any Phase 1+ code lands.
P0.1
Re-verify interruption recoveryConfirm Send stage's two-transaction shape has no silent-duplicate path remaining, protects money already live today.
Done
P0.2
BscScan source verificationVerify MasterBuilder's pid-0 harvest functions enterStaking/leaveStaking or actual implementation against deployed source.
Done
P0.3
Binance LTC network selectionConfirm via Binance API docs whether LTC withdrawal can specify native-network distinct from BEP-20 arrival network.
Done
P0.4
Notification channel decisionDecide channel for scheduled harvest-readiness checks (email/push/SMS/in-app). Decided: Email via transactional service.
Done
P0.5
Full Farm Exit verificationMasterBuilder withdraw mechanics, every LP pair, liquidity-removal methods, LOOP/BUSD-to-BNB paths, transfer-fee behavior verification.
M1
Manual LSWAP staking pool detection and harvestDetect and harvest Loopsyrup Manual LSWAP (pid 0) alongside existing farm pools via enterStaking(0). Same contract already trusted.
Planned
M2
Add funds to staking poolsApprove and stake symmetric to existing harvest flow. Simpler case before M10 LP farm deposits requiring swap/add-liquidity.
Planned
M3
Consolidate duplicate BNB-price fetchingRefactor to reduce redundant on-chain price calls before M5 (scheduled checks) increases call frequency.
Planned
M4
Binance-relay to CoinbaseDestination-aware Convert, new Binance crypto-withdrawal for LTC (native network), fee-peel-off design. Core V2 feature for multi-exchange users.
Planned
M5
Scheduled harvest-readiness checksEmail notifications on monthly cadence or USD-threshold basis. Cron-triggered API route, email provider selected, email field added to settings.
Planned
M6
Binance error health-checkPeriodic monitoring and alerting for the intermittent Binance -2015 error surface. Sequenced with M4's Binance API work.
Planned
M7
Generalize pool discoveryReplace hardcoded POOL_NAMES and pid exclusions with dynamic on-chain metadata reads so new pools appear automatically.
Planned
M8
Persisted harvest historyLog past harvests for trend visibility. Reuses existing Upstash store. Pairs naturally with M5 (readiness checks).
Planned
M9
Multicall batching for on-chain readsReduce call count and latency by batching reads. More valuable once M1/M2 grow read diversity.
Planned
M10
Add funds to LP farmsSwap-and-add-liquidity then deposit into farms. More complex than M2 (requires slippage handling, two-asset balancing).
Planned
M11
Custom domain cutoverDNS + Vercel domain configuration for harvester.makoinu.com. Eliminates *.vercel.app phishing-heuristic warnings.
Done (2026-08-24)
M12
Onboarding personalizationCapture user name at onboarding, greet with time-of-day (Good morning/afternoon/evening) and timezone fallback.
Planned
E1
Full Farm Exit / BailoutDiscover all nonzero LP farm positions, unstake all, remove all liquidity, convert to BNB, reuse existing fee/reserve/Binance path. Includes testing-only fractional canary.
Scope settled, implementation not authorized

Relationship to MAKO Web

This roadmap covers the MAKO Posse Team's own V2 expansion work. Harvester V1 is already live in production with real users and real money. V2 development proceeds under full development isolation (dedicated branch, separate Preview environment, separate Upstash database) to protect V1 users until each phase is verified and independently reviewed. Once each phase is proven, the code lands on main and reaches production. The MAKO Web Team does not integrate Harvester — it is a standalone operator tool, not a public site feature.

← Back to Development Roadmap

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