TurboUSD treasury: published totals vs Base

The burned total matches the chain exactly: 1,052,048,829.86 TUSD sit at the dead address, and the BurnEngine figure matches too. Two figures use a wider definition than market buys or staking contracts; here is how each reconciles. Of the 2.08B shown as “bought back”, 2.0B is a withdrawal of tokens allocated at launch from a ClankerVault; on-chain market buys total 77.6M. The 29.02B shown as “staked” includes the TreasuryManager’s own 2.0B unstaked balance; the staking contracts hold 27.01B. The treasury-burns figure is 441,746 lower than the chain because one old-burner burn is not counted.

Source of published figures

turbousd.com/api/live (updatedAt 12:40:08 UTC), the feed behind the turbousd.com ticker; definitions from TurboUSD/treasury-manager @ 9de97647

Block

52,855,800 · 2026-10-20 12:55:47 UTC · 0x0b223105…5ead0a

Token

TUSD 0x3d5e…DB07 on Base, 18 decimals, launch supply 100,000,000,000

Method

eth_call balances and supply at the pinned block; Blockscout transfer lists filtered to that block; read-only

Paid by

Nobody. Free record; we pitched AMI a paid version on 20 Oct.

Right of reply

Corrections or context from AMI/TurboUSD will be appended here, time-stamped.

Published vs chain

The 2.0B in “bought back”

On 20 Apr 2026, transaction Basescan ↗ 0xdb0a89e994e3fe00fc85db273e35b9b3bc66748495a8d1ce6a5dc4a6c7420408 moved exactly 2,000,000,000 TUSD from the ClankerVault 0x42a9…f09d to the TreasuryManager 0xAF8b…4107. It was a withdraw(...) call (selector 0x69328dec) sent by 0x29c3…799d. The transaction contains a single TUSD transfer, vault to TreasuryManager. No WETH or USDC moved, so nothing was paid for the tokens.

The vault received exactly 2,000,000,000 TUSD in the token’s deploy block 32,471,385 (5 Jul 2025), in transaction Basescan ↗ 0xab0182c5ecd1c07a25c5008552f2f66cc4bbdbb7881475af151e144d21c83755, from 0x2a78…7382. These are tokens allocated at launch, not bought on the market.

Market buys are counted as TUSD arriving at AMI contracts from the TUSD/WETH Uniswap V3 pool 0xd013…78F8 (the swap output):

The published figure reconciles exactly to these parts. The published buy count (12) is likewise 8 TreasuryManager + 1 old-burner + 2 BurnEngine buys + the vault withdrawal.

Under the dashboard source code, “Bought back” is a sum of rows in an off-chain Supabase operations log (op_type Buyback), not a chain query.

Who burned the 1.05B

All 70 transfers to the dead address 0x0000…dEaD up to the pinned block, grouped by sender:

Contracts operated by AMI (TreasuryManager and old burner) account for 54,486,696.91; with the BurnEngine, 150,177,425.72. Whether AMI or the team controls the Safe 0x1eaf…4ace or the EOA 0x29c3…799d is not established on chain.

BurnEngine burns:

• Basescan ↗ 0xb8df47dcd3ff0e07efa98007360dba7d0ab74058bd283163c9db397d34913f96 1,000.00
• Basescan ↗ 0xe39ab49ffd9894e21ecfd8f7eec071ffef09587b19e57503680f1a51fc297c0b 1,000.00
• Basescan ↗ 0x06532c1bebf52b494de435b18c382036a259b325833c849ca9b3d06fb0f2cb47 10,231,482.83
• Basescan ↗ 0x6b38c903a0e5edb03b31bae23df232fe09bc655f1c7e65bdd9c417bceb6159b4 76,486,816.46
• Basescan ↗ 0xb87ac6729bf226495bd4b3aed68e9e6b69d62661acb97d0b896c4a9778a32194 8,970,429.52

Old-burner burns:

• Basescan ↗ 0x8e166a43d7c7cf9be7aa48d1546f8186ad1bd708d99dc83183d14544e17ff9be 441,746.13
• Basescan ↗ 0xa590b565b381eea85b144cd39821d301fb7d23d4c13e4a147033d87491db161c 43,147,461.30

Latest TreasuryManager burn: Basescan ↗ 0x817bf0e16d45bea7bc1bb16f1efbdbd7647f3e3dd2f50784e4252efaf6f4c546 500,000.00.

What we could not check / limits

• Transfer lists come from the Blockscout Etherscan-compatible API (base.blockscout.com), filtered to blocks at or before 52,855,800. Balances and supply come from eth_call at that block on mainnet.base.org. A full-range eth_getLogs was not available on the free RPC endpoints used.
• The dead-address transfer sum equals the dead-address balance exactly, which cross-checks that list for completeness.
• Buybacks are detected only as TUSD arriving from the Uniswap V3 pool 0xd013…78F8. Buys routed through other pools into these contracts would be missed; none were seen, and every non-pool inflow is listed.
• Whether AMI or the team controls the Safe 0x1eaf…4ace and the EOA 0x29c3…799d is not established on chain.
• The code behind turbousd.com/api/live is not public. Definitions are taken from the treasury-manager repository and inferred from exact numeric matches.
• USD figures were not checked; they depend on price.
• totalSupply is 99,999,999,906.53, about 93.47 TUSD below the 100B launch supply. Those tokens were removed by supply reduction, not sent to the dead address.

How to reproduce

1. Pin the block. Base block 52,855,800 (0x32683f8), hash 0x0b223105ccc2e7235b0485248778bc32518212bef956a0110a413ca8bd5ead0a, timestamp 2026-10-20 12:55:47 UTC.
2. Supply and balances. eth_call on https://mainnet.base.org at block 0x32683f8 to the TUSD token 0x3d5e…DB07: totalSupply() (0x18160ddd) and balanceOf(address) (0x70a08231 + address padded to 32 bytes) for the dead address, Staking 0x2a70…C89A, TurboFaithStaking 0x2958…21bc, TreasuryManager 0xAF8b…4107, BurnEngine 0x0226…63AB and old burner 0x3dbF…BBd6. Divide by 10¹⁸. BurnEngine getStatus() at the same block returns totalBurned 0x4f274ccd9377547bfcc0f6 (95,690,728.81) and 5 cycles.
3. Transfer lists. https://base.blockscout.com/api?module=account&action=tokentx&contractaddress=0x3d5e487B21E0569048c4D1A60E98C36e1B09DB07&address=<address> for the dead address and each AMI contract; keep only rows with blockNumber ≤ 52,855,800. Group dead-address inflows by sender and check that their sum equals the dead balance.
4. Buyback definition used. A buyback is a TUSD transfer from the TUSD/WETH Uniswap V3 pool 0xd013…78F8 into the TreasuryManager, old burner or BurnEngine. Any other inflow (such as the ClankerVault withdrawal) is listed separately and not counted as a purchase.
5. Published figures. GET https://www.turbousd.com/api/live (read at updatedAt 2026-10-20T12:40:08Z). The ticker shows Burned = supply.burned, Bought back = ops.boughtTusd, Staked = supply.staked, per dashboard/components/tusd-chrome/live.ts in github.com/TurboUSD/treasury-manager at commit 9de97647.
6. Staking. Add the Staking and TurboFaithStaking balances, then add the TreasuryManager balance and compare each total with supply.staked.