# \[2601 Grant\] SwaptoX Aggregator – Milestone 1

**URL:** https://gov.rootstockcollective.xyz/t/2601-grant-swaptox-aggregator-milestone-1/700
**Category:** Grants & Incentives
**Created:** [January 8, 2026, 7:42pm UTC](https://gov.rootstockcollective.xyz/t/2601-grant-swaptox-aggregator-milestone-1/700 "2026-01-08T19:42:33Z")
**Posts on this page:** 1
**Showing post:** 86

<div class="post-metadata">

### Author: ![Tane](https://yyz2.discourse-cdn.com/flex030/user_avatar/gov.rootstockcollective.xyz/tane/32/223_2.png) [@Tane](https://gov.rootstockcollective.xyz/u/Tane)
#### Post date: [June 16, 2026, 2:28pm UTC](https://gov.rootstockcollective.xyz/t/2601-grant-swaptox-aggregator-milestone-1/700/86 "2026-06-16T14:28:53Z")

</div>

Thanks for the detailed update, @SwaptoX. Tree-based recursive splitting is a genuinely harder problem than splitting across independent routes, and @SEEDGov is right that the reasons hold up: no objection to the 15-day extension, and moving the UI work into the M3 widget phase is sensible.

One item for M2 delivery. When we [flagged audit planning](https://gov.rootstockcollective.xyz/t/2601-grant-swaptox-aggregator-milestone-1/700/65), the M2 deliverable became a concrete audit plan with a selected provider, locked scope, cost, and timeline, plus the third-party grant applications, not just quotations. Contacting around ten firms is progress, but the finalized plan is the deliverable.

So at delivery, could you share three things: the finalized audit plan; the deployed multisig and timelock addresses, so the governance upgrade can be verified on-chain; and the public split-routing comparison page against OpenOcean that the scope set as the validation mechanism?

---

_[View the full topic](https://gov.rootstockcollective.xyz/t/2601-grant-swaptox-aggregator-milestone-1/700)._