01
What it is
A token without a market maker looks dead: a wide spread, an empty book, and any modest buy moves the price by tens of percent. TONMM keeps the market alive: it counter-trades against other people’s swaps, holds price inside a configured corridor, and rebalances inventory when the position skews to one side.
In a system like this, the important part is not making money — it is knowing how to stop.
There are three independent safeties: a kill switch, a circuit breaker and an auto-stop on reconciliation drift. On thin-liquidity tokens we deliberately raised the minimum slippage tolerance, because otherwise the system honestly refused to trade — which is correct behaviour, not a bug.
02
capabilities
What it does
01
Market-making strategies
Counter-trading against incoming swaps, price-corridor holding, and templated trade series ranging from gentle to aggressive.
02
Inventory rebalancing
The dollar position is tracked continuously; past a skew threshold the system levels the token and TON balance on its own.
03
Managed wallet pool
V5R1 and V4R2 wallets with encrypted mnemonics, plus address rotation so activity does not read as a single participant.
04
Execution protection
A slippage cap and a quote-drift check before send — if price moved more than a percent, the trade aborts.
05
Three ways to stop
Kill switch, circuit breaker and reconciliation auto-stop — independent circuits, not one button.
06
Observability
Prometheus, Grafana and Loki from day one: every trade, every rejection and every position skew is visible.
03
architecture
How it works
01
DEX swap flow
02
Strategy and decision
03
Execution via STON.fi
04
Inventory rebalance
05
Reconciliation and safeties
Under the hood
- A FastAPI backend with 24 routers; a React console with trade charts and pool state.
- MongoDB for operational state, SQLite for strategy state — a deliberate split by the nature of the data.
- Execution through the STON.fi aggregator, with a separate path for DEX sells on low-liquidity pairs.
- Mnemonics are symmetrically encrypted; the key never sits in the repository.
- FunC smart contracts ship as part of the project.
- A standby instance on a separate server: if the primary node dies, trading does not stop forever.
04
scale
Numbers
3
independent stop mechanisms
24
API routers
2
stores by purpose
1%
quote drift threshold