OUSG vs SyrupUSDC

OUSG leads on the only live benchmark. OUSG wins on Which tokenized T-bill or yield fund actually pays what it promises (0.13% vs 0.010%).

Read methodology Last measured Window: rolling 24h1 shared benchmark
OUSG logo
OUSG

Ondo OUSG is a tokenized short-term U.S. Treasury fund. NAV appreciation model: the share price grows daily as yield accrues. Delivered yield on bench 089 is read from Ondo's on-chain oracle (Aave IPriceOracle interface).

SyrupUSDC logo
SyrupUSDC

Maple SyrupUSDC is an ERC-4626 vault whose underlying is a book of institutional USDC loans. Not a T-bill wrapper. Yield reflects loan-book performance. Delivered yield on bench 089 reads convertToAssets(1 share) at latest and t-30d blocks and compares to the pool's base APY (excludes SYRUP token rewards).

Side by side measurements

Frequently asked questions

OUSG vs SyrupUSDC: which one is better?

OUSG and SyrupUSDC are compared on 1 shared OpenChainBench benchmarks. OUSG leads on Which tokenized T-bill or yield fund actually pays what it promises. See the live table on this page for every metric.

Which is cheaper, OUSG or SyrupUSDC?

On the Which tokenized T-bill or yield fund actually pays what it promises benchmark, OUSG leads at 0.13% versus SyrupUSDC at 0.010%. Live measurement is updated continuously by the OpenChainBench harness.

How is the OUSG vs SyrupUSDC comparison measured?

Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.

How this pair was selected

Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing — panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.