YieldFi yUSD
In recovery . ethereum . 0x19ebd191f7a24ece672ba13a302212b5ef7f35cb
What this vault advertises, against what it actually paid, measured from its own share price on chain over a 30 day window. Everything below is recomputed hourly and every figure on this page comes from the snapshot named at the bottom. Nothing here is typed by hand.
Advertised
none published
Realized
0.00%
30 day window
Gap
no claim to compare
this protocol advertises no yield figure.
What YieldFi published.
YieldFi publishes no yield figure we can record for yUSD on a first-party surface, so this row carries a realized reading and no comparison. That is a description of what is published, not an accusation.
Recompute it yourself.
The realized figure is two calls and one exponent. Both calls are pinned to a block height, so they return the same values for you as they did for us, forever. Use any archive endpoint. We deliberately do not name one: a reproduction that runs on our RPC is not a reproduction.
The call
Chain
ethereum
Contract
0x19ebd191f7a24ece672ba13a302212b5ef7f35cb
Method
convertToAssets(uint256)
Argument
1000000000000000000 (one whole yUSD share, 18 decimals)
eth_call data
0x07a2d13a0000000000000000000000000000000000000000000000000de0b6b3a7640000
Returns
USDC, 6 decimals
The argument is one whole share in the SHARE token's own decimals, which is not always eighteen. Kerne's own skUSD reports twenty four, so calling it with 1e18 returns a millionth of the right answer. Ask the vault for its decimals rather than assuming, exactly as our collector does.
At the start of the window
Block
25539888 (0x185b530)
Timestamp
1784140607 (2026-07-15 18:36 UTC)
Share price returned
0.998453
At the end of the window
Block
25755112 (0x188fde8)
Timestamp
1786732607 (2026-08-14 18:36 UTC)
Share price returned
0.998453
Start of window, cast
RPC_URL=... cast call 0x19ebd191f7a24ece672ba13a302212b5ef7f35cb "convertToAssets(uint256)(uint256)" 1000000000000000000 --block 25539888 --rpc-url "$RPC_URL"End of window, cast
RPC_URL=... cast call 0x19ebd191f7a24ece672ba13a302212b5ef7f35cb "convertToAssets(uint256)(uint256)" 1000000000000000000 --block 25755112 --rpc-url "$RPC_URL"Start of window, raw JSON-RPC
{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x19ebd191f7a24ece672ba13a302212b5ef7f35cb","data":"0x07a2d13a0000000000000000000000000000000000000000000000000de0b6b3a7640000"},"0x185b530"]}End of window, raw JSON-RPC
{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x19ebd191f7a24ece672ba13a302212b5ef7f35cb","data":"0x07a2d13a0000000000000000000000000000000000000000000000000de0b6b3a7640000"},"0x188fde8"]}Both calls return an integer in the smallest unit of USDC. Divide by 10 ** 6 to get the share price printed above. Set RPC_URL to any archive endpoint you trust.
The arithmetic
growth = 0.998453 / 0.998453
elapsed = 1786732607 - 1784140607 = 2592000 seconds
annualized = (growth ^ (31536000 / 2592000) - 1) * 100
= 0% (0% over the window)
Simple compounding at the observed rate, on a 365 day year. No fee assumption, no reinvestment assumption, no smoothing. If your arithmetic lands somewhere else, that disagreement is the finding and we want it: liam@kerne.fi.
Context for this row.
Paused and publishing no yield figure. YieldFi's own site carries a notice at the top of the page stating that mint and redeem operations for yUSD are paused until it seeks remediation from a named counterparty under a contractual agreement, and its APY widget renders no loaded figure. The share price has not moved for months and over the trailing year it FELL rather than rose, which is unusual on this board and is the reason this row was held back when the vault was first measured on 2026-07-29: a decline has a cause, and we said at the time that we would not publish the number until the cause could be stated. It now can be, from the issuer's own surface, so the row is here. Read it as a paused protocol rather than as a verdict. A vault that stops accruing while its operator says publicly that it is pausing and seeking remediation is disclosing, which is more than a silent one does. The dollar itself traded within a fraction of a cent of par when this row was added, so the fall is in the vault's share price rather than in the peg of the asset it is denominated in.
This page measures one axis and one only: advertised yield against realized yield. It is not a rating, not an audit, and it says nothing about whether YieldFi is safe or whether its reserves are what it says they are. A protocol in an announced wind down paying nothing is behaving correctly. The reserve axis is a different page, at the reserve transparency scorecard.
Take this row with you.
This page
https://kerne.fi/honesty-index/yieldfi-yusdCitation
Kerne Honesty Index, 2026-08-14: YieldFi (yUSD) advertised none published, realized 0.00% from on-chain share-price growth, gap no claim to compare (this protocol advertises no yield figure). Source: https://kerne.fi/honesty-index#row-yieldfi-yusdBadge, markdown
[](https://kerne.fi/honesty-index#row-yieldfi-yusd)Badge, HTML
<a href="https://kerne.fi/honesty-index#row-yieldfi-yusd"><img src="https://kerne.fi/honesty-badge.svg?row=yieldfi-yusd" width="360" height="112" loading="lazy" alt="Kerne Honesty Index: advertised versus realized yield"></a>Row in the API
https://kerne.fi/api/honesty-index/row/yieldfi-yusd
Where these numbers came from.
Snapshot generated
2026-08-14 18:37 UTC
Snapshot source
live store
Signature
verified, signer 0x84949170e0ad0f9bd8686a4aa4922c10f5fdc4ea
Row key
yieldfi-yusd
The signature is checked on every render rather than assumed from the presence of a field. A snapshot that does not verify is served with that said plainly instead of borrowing the word.
Board last read 2026-08-14. Every figure on this page is regenerated from https://kerne.fi/honesty-index and none of them is stored in this file.