Milestone Adjustment
Thanks to @Tane for highlighting three key issues:
-
Excessive standalone privileges of the Router
-
Priority of split routing
-
Formal audit planning
I agree that these are critical concerns. Below are the adjustments and clarifications.
Milestone 2 (Updated)
-
(Estimated 20–30 days)
Develop split routing algorithms and core routing logic. -
(Estimated 7 days)
Upgrade token USD pricing logic to split-based quoting, ensuring displayed prices better reflect actual swap execution prices. -
(Estimated 5 days)
Fully migrate API to Redis caching and integrate Cloudflare global acceleration.
Current quote latency: 3–4 seconds → Target: 1–3 seconds. -
(Estimated 7 days) UI improvements:
-
Display transaction history
-
Support permit-based approvals
-
Redesign routing display module (to support split routing visualization; current display only reflects single-path routes)
-
-
(Estimated 7 days) Router contract governance upgrades:
-
The Entered contract becomes upgradeable only (e.g., v2, v3), and deployed versions cannot be overwritten
-
Introduce a 3-wallet multisig, requiring 2-of-3 signatures for any admin operation
-
Implement a 72-hour timelock for all admin functions (“request + confirm” pattern; confirmation must be executed by a different signer to mitigate single key compromise risk)
-
Extend the protocol fee timelock on Rootstock: no protocol fee changes allowed before 2028 (based on current timeline, all milestones are expected to complete by September 2026)
-
-
Audit planning (to be delivered in Milestone 3):
-
Engage multiple audit firms to obtain quotations
-
Apply for third-party audit grants (e.g., https://atlas.optimism.io/missions/audit-grants)
Outcome: determine audit scope, cost, availability of external funding, and finalize the audit plan.
Milestone 2 will define and establish a concrete audit plan (scope, provider, and timeline), which will be a prerequisite for execution in Milestone 3.
-
This milestone addresses the priority of split routing and significantly mitigates the risks associated with Router administrative control. It also delivers a concrete audit plan for Milestone 3.
The multisig structure will initially be managed by the core team, with additional signers introduced over time to reduce unilateral control risk.
Split Routing Validation
The main challenge of this milestone lies in the split routing algorithm, as there is no standard solution and it requires extensive computation to determine optimal path allocation and proportions.
To validate the implementation:
-
A public comparison page will be built using both SwaptoX API and OpenOcean API
-
Identical inputs (token pair and amount) will be used for fair comparison
-
At least 30 different test scenarios will be included, covering:
-
Various trade sizes (e.g., 0.1 BTC, 0.5 BTC, 1 BTC, 2 BTC, etc.)
-
Multiple token pairs (e.g., BTC → USDC, BTC → USDT, USDT → BTC, etc.)
-
-
Each page refresh triggers a new round of live quotes
-
Tests will be conducted across multiple blocks and time intervals to reduce the impact of short-term market fluctuations
Success Criteria
SwaptoX demonstrates competitive routing performance compared to leading aggregators across multiple trade sizes.
This includes:
-
Comparable or better average output
-
Positive or near-neutral median performance
-
A meaningful share of scenarios (across varying trade sizes and token pairs) where SwaptoX achieves equal or better results
-
No significant negative deviation in large trades
The comparison page will be publicly accessible for anyone to verify results.
Milestone 2 Timeline: 45–60 days
Requested Funding: $6,000
Milestone 3
Aligned with Milestone 2 from “Redefined Milestones: V2.1”, now redefined as Milestone 3.
Additionally:
We will build a dedicated interface using the Mini-SDK:
mini.swaptox.com (currently not live)
This interface will:
-
Provide a simplified and complete swap experience
-
Be optimized for mobile usage
-
Serve as the primary entry point for:
-
Telegram bots
-
Farcaster Mini Apps
-
Native DEX aggregator app integrations
-
For growth in Milestone 4, distribution will prioritize Telegram bots alongside SDK adoption.
Timeline: 30–40 days
Requested Funding: $4,000
Milestone 4
Aligned with Milestone 3 from “Redefined Milestones: V2.1”, now redefined as Milestone 4.
Budget Adjustment Explanation
This revision increases the total funding request by $3,000 compared to the original proposal.
The expanded scope introduces additional engineering complexity, particularly in:
-
Split routing implementation (multi-path optimization and allocation logic)
-
Router contract security enhancements (multisig, timelock, and stricter upgrade constraints)
These components were not part of the original implementation.
The changes significantly improve execution quality and protocol security, and therefore require additional development effort and time.
This updated proposal will enter a 7-day discussion period before proceeding to on-chain voting.