Docs · Reference
Contracts and security
The contracts Moa uses on GIWA Sepolia, and what their owner can and cannot do.
| Contract | Address | Purpose |
|---|---|---|
| MoaRouter | 0x1ce8f956a66806625c7e8e368e6e9ab3263081370x1ce8f9…308137 | Entry point for trades: takes the fee, enforces the minimum received |
| MoaLimitOrders | 0xabde40ed0be10d832a46c3888c5ba64a3d1f8f060xabde40…1f8f06 | Holds limit orders until they fill or are cancelled |
| MoaCopyVault | 0xbb0c999fde019db3eb2207e9843aa8d8ad00996a0xbb0c99…00996a | Followers’ deposits and copied positions |
| MoaLaunchFees | 0x8e8799a8f8e59ab0c98d2795f6aee78f827d843a0x8e8799…7d843a | Collects Moa’s share of launched tokens |
How trades are kept safe
- You approve only the router. The swap itself is made by a separate executor contract that holds no approvals and no funds between trades, so a pool cannot reach your approvals or anyone else’s funds.
- What you receive is measured from your balance, not taken from what a pool reports, and the trade is cancelled if it is below your minimum.
Owner permissions
| The owner can | The owner cannot |
|---|---|
| Lower fees, or set them up to the 1% cap | Set any fee above 1% |
| Change referral terms up to 50% | Withdraw referral earnings or users’ funds |
| Pause new trades and copies | Stop cancellations, withdrawals or referral claims |
| Add copy trading keepers and venues, usable after a waiting period | Make one usable without waiting, or spend past a follower’s limits |
| Allow launchers and lower the launch share | Raise the launch share above 1% or send it anywhere but the treasury |
Limit orders have no owner at all. None of the contracts can be upgraded.
Testing and audits
The contracts are covered by automated tests that run against a copy of the live chain, including attempts to copy trades that never happened, fake pools and attempts to take other users’ funds.
They were also reviewed by independent automated reviewers working from the code alone; the issues found were fixed and the contracts redeployed. Tokens whose balances change on their own (rebasing tokens) are not supported in limit orders or the copy vault.
Not audited. The contracts have not yet been reviewed by an external audit firm. They are deployed on a test network only.