How Aumo actually works

You put in USDT0 and get aumoUSDT0 shares back. It is a standard ERC-4626 vault, which is a fancy way of saying: your shares are a claim on the whole pot, and yield shows up as your share getting more valuable, not as a separate reward you have to claim.

What the pool is worth at any moment:

Each venue's balance is read live and wrapped in a try/catch, so one flaky venue can never brick the whole number. First-depositor inflation (the classic 4626 attack) is neutralized with a decimals offset of 6. Ownership is two-step and cannot be renounced, so the pool is never left ownerless. And redemptions are never pausable, so you can always get out.

The agent is smart but not trusted. Every limit is enforced by the pool itself, so the worst a buggy or hijacked agent can do is get a transaction reverted.

• A cap on how much moves per transaction, per venue, and in total.
• An allowlist: funds can only reach approved venues, never some random address.
• A rolling loss budget: every swap spread it burns is metered, and once the window's budget is spent, further lossy moves revert.
• A deploy budget that rate-limits how fast it can churn capital.

Caps check real exposure, not just booked principal:

It never chases the biggest APY. It breaks each venue into risk pieces, blends them with fixed weights, and haircuts the yield by the result. The blend:

Then it adds a trend penalty if the venue is getting worse, plus two RWA-specific alarms: a hit if the venue's live data went stale, and a bigger hit if you could not actually exit it right now (a lending market borrowed to the hilt, or a position bigger than the exit door). Concentration is correlation-aware, so stacking two similar venues does not count as diversifying. What it ranks on is never the raw APY:

It rotates capital only when the move pays for itself. Two things usually say "don't bother": the best venue is already at its concentration cap (it cannot legally add more), or the edge is real but cannot beat the round-trip swap cost before the position matures.

For a fixed-maturity venue like a Pendle PT, only the yield capturable before it matures counts. So a juicy headline edge on something maturing in two months often does not justify the ~100bps it costs to get in and out. Holding, in that case, is the agent being disciplined, not idle.

Aave v3. Supplies USDT0, holds the interest-bearing aToken. Simple.

USDG. Swaps USDT0 to USDG behind a slippage floor, then supplies it to Aave for real-world-asset yield.

Pendle PT-USDG. Buys the Principal Token for a fixed rate to maturity. Valued off a TWAP oracle (never a spot price you could yank around) and clamped at par.

USDG/USDT0 LP. The liquidity venue from the walkthrough above. It vendors Uniswap's own math exactly, values the position through a peg-band-clamped price so a manipulated spot cannot fake a gain, and reads its live fee APY from the pool's fee growth:

annualized by the elapsed time, in full-precision integer math.

Every cycle writes a receipt: what it saw, the risk scores, the plan and why, the transaction hashes, and a fingerprint of the exact guardrails in force. So any change in behavior traces back to a change in policy. Performance is measured as honestly as it gets: the growth of your share price.

Idle money keeps that flat; the agent's job is to grow it, net of every cost. A fresh deposit dips it briefly by the one-time cost of deploying, which is earned back, so the number only gets reported once there is a fair window behind it. The whole trail exports as CSV.

The agent signs with an ordinary key, and the design assumes that key could be compromised at any moment. That is the point: the safety does not come from hiding the key, it comes from the contract. Even holding the signing key, the only moves it permits are allocating to an allowlisted venue and pulling funds back to the pool. No function sends money to an outside address, so a stolen signer still cannot drain a cent. Deposits can start on Ethereum, Arbitrum, Optimism, or Polygon and land on X Layer through USDT0's native bridge, no wrapped-asset detour.

The thing Aumo removes is trusting the agent: it cannot exceed the on-chain caps and cannot send funds to an outside address, so a rogue agent cannot steal. What you still trust is the venues themselves, the correctness of the contracts, and the owner key that sets policy. The pool and adapters have a unit suite plus a stateful invariant suite, every adapter is fork-proven against live contracts, and new money-code gets a multi-pass adversarial review. Aumo is experimental and has not had a formal third-party audit yet. That is the truth, plainly.