How Vaults Use Syncrone to track performance

Key takeaways

• APY, TVL, and a public chart are not a performance record. LPs need NAV from the first deposit, not from the day a dashboard was connected.

• Vault yield rarely arrives as a transaction. Interest, fees, and share-price accretion must be read from protocol state, then valued.

• Compare vaults only after the methodology is the same: same look-through, same price source, same day-count.

• What you publish and what you keep internal can differ. The internal book still has to produce the public number.

Why advertised APY is not a record

A vault page that shows 12% APY answers a sales question. It does not answer the questions an allocator, a curator, or a risk committee will ask.

What was NAV on day one? What is NAV today? How much of the change is income the vault earned, and how much is the underlying asset moving? What share of the book is idle? When did the strategy change, and did the published series stay continuous?

APY compresses all of that into one rate. Two vaults can print the same APY and have completely different books: one earning stable lending income, the other riding a token price, the third looping the same collateral until gross exposure is several times net assets.

If those three look identical on a marketing page, the page is not a reporting system.

What a vault performance record must contain

A usable record starts at inception, not at the day the team connected a tracker.

It needs a daily NAV series. Each point is a snapshot of vault state at a documented time, priced with a documented source. The series must survive share issuance, redemptions, fee accruals, and strategy migrations without a silent reset.

It needs a return that is not distorted by flows. Time-weighted return isolates the strategy. Money-weighted return (XIRR) shows what a specific depositor earned. Publishing one number as if it were both is how vaults lose credibility with professional LPs.

It needs a decomposition. Income that accrued as balance growth or share-price accretion is not the same thing as mark-to-market on the underlying. LPs allocating for yield care which one they are buying.

It needs look-through. A vault share is a claim on whatever the vault holds. Pricing the share on a thin DEX while the vault can redeem through the protocol is a different number. The record should show the economic claim, not only the receipt ticker.

How vault state becomes those figures

Most vault yield does not emit a clean transfer. Aave-style receipts rise with an index. Many ERC-4626 vaults accrete value into the share price. AMM fees change pool composition. Pendle PTs pull toward par along a curve. None of that looks like a coupon payment in a transaction list.

A NAV engine therefore has to read protocol state at each snapshot: exchange rates, share prices, pending rewards, debt, and the underlying balances those receipts represent. Then it prices the unwrapped claim.

That is also why a subgraph that misses a market, or a dashboard that starts on onboarding day, produces a record that cannot be shown to an auditor. The gap is not cosmetic. The first weeks of a vault are often the most important part of the track record.

Comparing vaults on a common methodology

Curators and DAO treasuries compare vaults. The comparison is only valid if the methodology matches.

Same valuation policy: look-through versus receipt-token spot. Same price source and snapshot time. Same treatment of rewards that are earned but unclaimed. Same day-count when a rate is annualized. Same rule for idle stablecoins sitting in the vault wallet.

Without that, a “peer APY” table is a design element, not an analysis. A vault that looks cheaper on fees can be more expensive once idle capital and looped gross exposure are visible.

Internal dashboards can still show many vaults side by side. The requirement is that each series is computed the same way, and that the public page does not switch methodology when the number gets harder to explain.

What to publish, and what to keep internal

Public vault pages should be narrower than the internal book. NAV, time-weighted return, income versus price, composition, and a period statement are enough for most LPs.

The internal book should go further: position-level PnL, idle versus deployed capital, concentration through look-through, and a frozen period close that does not rewrite itself when an oracle is later corrected.

The two views must reconcile. If the public APY cannot be produced from the internal series, the public number is the one that will fail due diligence.

A vault that can show that reconciliation, from the first deposit, is operating as a product. A vault that can only show a live yield badge is still operating as a campaign.