TurboUSD
LIVE
₸USD$0.000005184·24h-3.51%·MCAP$502.5K·Burned1.05B ₸·Bought back2.08B ₸·Staked29.02B ₸·Wallets246,886·AMI managed$14.4K·Last AMI opStake ·USD printed+$39,616/s·M2 YoY+5.7%·₸USD$0.000005184·24h-3.51%·MCAP$502.5K·Burned1.05B ₸·Bought back2.08B ₸·Staked29.02B ₸·Wallets246,886·AMI managed$14.4K·Last AMI opStake ·USD printed+$39,616/s·M2 YoY+5.7%·

AMI · Treasury Manager

Autonomy inside
immutable boundaries.

The smart contract that executes every treasury operation. AMI defines what should be done; this contract defines what can be done. Every function has hard limits encoded onchain, whatever the agent decides.

Treasury Manager · Base

0xAF8b3FEBA3411430FAc757968Ac1c9FB25b84107
Source on GitHubTreasury dashboard
Managed funds
$14,351

updated recently

₸USD burned
1.05B ₸

32 burns · $6.9K

₸USD bought back
2.08B ₸

12 buys · $10.6K

₸USD held for good
2B ₸

Can only be staked or burned

No function in the contract can sell or withdraw ₸USD. It only locks, buys and burns it.

0₸USD sold, ever

Controlled actions

Five capabilities.
Every one capped.

Instead of open-ended control, the contract exposes a short list of functions, each bounded by per-action and daily caps over a rolling 24-hour window. Treasury intervention stays measurable, constrained and predictable.

buybackWETH · buybackUSDC()

Market purchase of ₸USD with treasury assets, through Uniswap

  • 0.5 ETH per action · 2 ETH per day
  • 1,000 USDC per action · 5,000 per day

burnTUSD()

Permanent removal of ₸USD, sent to 0xdead

  • 100M ₸USD per action
  • 500M ₸USD per day

stakeTUSD()

Locks treasury ₸USD into staking

  • 100M ₸USD per action
  • 500M ₸USD per day

buyStrategicToken()

WETH into a registered strategic token, with its own caps

  • Registered tokens only
  • Independent caps per token

rebalanceStrategicToken()

Sells a strategic token: 75% becomes ₸USD, 25% USDC

  • 0.5 ETH per action
  • 2 ETH per day

Not on the list

sellTUSD()

There is no way to sell or withdraw ₸USD. Flows are one-directional: in, never out.

Caps as configured at the time of writing; the contract enforces whatever is set onchain.

Execution constraints

Hard limits and
rate control.

Beyond the caps, the contract regulates how and when actions happen: no rapid repetition, no exposure to manipulated prices, and an operator that can execute but never rewrite the rules.

Cooldown

60 min

Between two operator actions, so no burst of repeated moves.

Price oracle

TWAP

30-minute average on liquid pools, 2 hours on the ₸USD pool: flash loans can't move it.

Operator role

Restricted

AMI can call approved functions. It can't change limits, logic or its own permissions.

Ownership

2-step

Ownable2Step and ReentrancyGuard, on OpenZeppelin 5.

One-way safe

No escape hatches. The only withdrawal path is the 25% USDC share of a rebalance, hardcoded and immutable.

sweep()rescue()emergencyWithdraw()selfdestructdelegatecallproxy upgrade

Permissionless fallback

If the owner and the operator both go quiet, anyone can keep the treasury running: buying, staking and burning ₸USD in perpetuity. No funds can ever be stuck.

180 days

initial lockout

+14 days

of owner & operator inactivity

Strategic token registry

What the treasury
may buy besides ₸USD.

Treasury strategic tokens are registered in the contract, each with its own Uniswap V3 or V4 route and its own caps. When they rise, rebalancing turns the gains into ₸USD buybacks. Live value held, from the dashboard:

BNKRV3

$1,091

DRBV3

$2,053

CLANKERV3

Not held

KELLYV4

$337

CLAWDV4

$266

JUNOV4

Not held

FELIXV4

Not held

Onchain log

Don't trust,
verify.

AMI 9000

AMI 9000

onchain execution log

LIVE
  1. connecting to treasury

Treasury Manager

0xAF8b3FEBA3411430FAc757968Ac1c9FB25b84107

BurnEngine

0x022688aDcDc24c648F4efBa76e42CD16BD0863AB

Legacy fee claimer

0x2c857A891338fe17D86651B7B78C59c96e274246

F.A.Q.

Who can call the contract?
The owner and the operator (AMI). The operator is bound by every cap, cooldown and slippage check; after long inactivity anyone can trigger rebalances.
What if the owner key were compromised?
Damage is capped by the same rolling limits, around 2 ETH a day of sub-optimal swaps, and 75% of any rebalance still ends up as ₸USD in the treasury.
Where did the treasury's ₸USD come from?
Buybacks, trading fees and, since April 20, 2026, the 2B ₸USD that Clanker set aside for the team at launch. The founder bought the other team members' share of it OTC with his own money and, once it unlocked, gave the whole 2B to the Treasury Manager instead of selling it: a buyback paid out of pocket. It can't leave the contract, so it is locked for good and will end up burned.
Has it been audited?
Yes, two audit rounds (v2 and v3). The reports are in the repository, next to the source.
AMI overviewOnchain log