Strategy Sleeve

Deploying capital

The Team Safe may deploy up to 95% of the Treasury's USDG into the Strategy Sleeve. The contract refuses a deployment unless liquid reserves and protocol-owned liquidity outside the sleeve still cover 1 USDG for every ROTEO on their own, so the sleeve only ever earns on capital the protocol does not need for that line.

Marking

At launch, the Team Safe is a 2-of-3 multisig and is configured as the Strategy Sleeve attestor. At least two signers approve every mark post. It also decides where capital goes. The StrategyVault takes 20% off the attested mark and the Treasury takes a further 2%, so a mark of 100 USDG counts as 78.40 USDG in Hard Reserves.

The mark follows a few rules:

• It can be posted at most once a day.
• It can rise by at most 0.5% per post, and fall at any time.
• It can never exceed 2× the capital deployed.
• After 7 days without a post it decays, halving every day, and a stale mark blocks new deployments.

A deployment can lose value or become inaccessible. The backing outside the sleeve is designed to stay intact even if deployed capital became worthless.

Transparency

Sleeve positions are visible through the protocol's disclosed Treasury wallets on DeBank and the relevant chain explorers. The StrategyVault does not move funds across chains itself: the Team Safe deploys capital and posts the mark the contracts use.

Roteo operations

Treasury Surplus may also fund the Roteo Operating Sleeve: inference capacity, reserved infrastructure and reliability buffers. These are operating items, not reserves, and none of them counts toward Hard NAV.

Roteo Serving Capacity, the current ability to route paid requests, is an operating metric reported by model and service unit. Any Maximum Routable Spend figure is an operating estimate at published prices, not asset value or revenue.

Roteo's gross routed volume is not Treasury revenue either. Only realized net contribution, after inference costs, routing and infrastructure costs, refunds and reserves for failed requests and chargebacks, becomes Hard Reserves, once it settles onchain.

Who holds the keys

A multisig Team Safe manages sleeve and Operating Sleeve deployments, and may rotate the attestor; every rotation emits a public onchain event. Capital at the Team Safe is not available to the floor bid until it returns through the StrategyVault, and every deployment and return is a public transaction.

The Team Safe can also harvest protocol-owned liquidity. ROTEO a harvest sends to it is meant for new pools and products, not for sale; that is the Team Safe's policy, not a contract restriction. Those positions are shown for reference only and never count toward Hard NAV.