Choose the evidence
The 2-track settlement model
For institutional partners with commercial revenue-sharing agreements, reporting follows a strict 2-track separation:- Track 1: On-Chain Data API (Gross Yield):
- Reflects pure, unadulterated on-chain vault operations.
- Provides canonical Gross PnL, holdings, and time-weighted returns.
- Serves as the immutable single source of truth for corporate balance sheet valuation and financial audits.
- Track 2: Commercial Settlement Statement (Net Payout):
- Off-chain commercial calculation applied to the API Gross PnL.
- Applies agreed contractual terms: performance fee sharing (e.g. 10% fee with 50~70% partner share) and deductions for off-chain expenses (such as monthly Rhino bridge invoices).
- Produced as a monthly settlement statement for cash disbursement.
Strategy NAV estimate
By default, SuperEarn usesvaluation=pps (the on-chain share value). However, when underlying strategies (such as Morpho lending markets, Pendle PT discount accretion, or tokenized RWA yield) accumulate interest between root harvest transactions, partners can inspect real-time venue accruals by setting valuation=estimated_nav.
- Same-block reads: NAV estimation uses exact same-block queries across all underlying venue adapters.
- Availability with flows: True TWR under estimated NAV supports periods without external cash flows. If an external flow occurs during the period, NAV return rates are returned as
nullwithtwr_nav_flow_state_unavailable, while monetary cash flows and estimated PnL remain available. - Cost basis preservation: Setting
valuation=estimated_navrevaluespositionValueandunrealizedPnl, but retains the exact same historicalcostBasis.
Harvest to investor earnings
To understand how underlying protocol yields translate into investor earnings, follow the lifecycle across smart contract layers:Two realization measures
Cooldown principal and settlement
Example across three periods
Consider a wallet starting with 100 shares and cost 100 in a vault with 1,000 root assets and 1,000 supply (1:1 conversion, no external flows):- When the harvest occurs, profit is fully locked; investor PnL is 0.
- Over the 7-day degradation window, profit unlocks; investor recognizes +10 in unrealized PnL.
- When shares are redeemed, the +10 unrealized gain shifts into +10 realized PnL; net PnL is 0.
Why legacy harvestReport is retired in v1
In earlier prototypes (kaia-usdt-miniapp and legacy /external/v2/...), an experimental accountedBy=harvestReport parameter existed. It attributed keeper report gains immediately to holders at the harvest block, under the assumption that locked profit would eventually unlock to current holders.
This mode was deliberately retired in v1 for three strict accounting reasons:
-
No Legal Entitlement or Liquidity at Report Time (IFRS Asset Recognition Failure):
- Under smart contract mechanics, profit reported by a harvest is locked in a degradation buffer and released linearly over 7 days.
- If an investor redeems shares immediately after harvest, the contract settles strictly at
pricePerShare(usingfreeFunds), completely excluding unreleased locked profit. - Recording an unredeemable locked amount as current holder balance or PnL violates the IFRS definition of an asset (present economic control and expected realizable inflow).
-
Shareholding Dilution and Flow Mismatch:
- Assuming locked profit belongs to current holders requires assuming zero subsequent deposits or withdrawals over the next 7 days.
- If new depositors enter the vault on day 2, they acquire shares at the current PPS, and the remaining locked profit unlocks across the enlarged share supply. Current holders are diluted.
- Recognizing 100% of the locked profit on day 1 produces phantom gains that change retrospectively when other participants transact.
-
Breakage of the Lifetime Ledger Invariant:
- Any compliant accounting ledger must satisfy:
- Because all deposits and redemptions execute in real tokens at PPS, booking locked profit in balance/earnings causes a sharp artificial disposal loss when an investor exits at actual PPS.
- Any compliant accounting ledger must satisfy:
How to query the information you need
Rather than blending hypothetical future releases into canonical balance and PnL, v1 separates the information into dedicated, audit-grade endpoints:Boundary valuation equation
For supported SuperVault roots (apiVersion: "0.4.6"), the boundary valuation is computed in three precise stages:
1. Linear profit release
include=reconciliation)
- Allocated Locked Profit:
floor(Held Shares * Effective Locked Profit / Total Supply) (converted). - Rounding Adjustment: Integer floor difference between the converted reported allocation (
floor(Held Shares * Reported Total Assets / Total Supply) (converted)) and the sum of active position value and allocated locked profit.
[!NOTE] Valuation mode vs reconciliation evidence: The Data API supports exactly two valuation modes:valuation=pps(default canonical share value) andvaluation=estimated_nav(real-time underlying venue accruals).include=reconciliationis not an independent valuation mode; it is an enrichment parameter available exclusively withvaluation=ppsthat supplies audit evidence reconciling the difference between canonical PPS valuation and total reported assets (including the locked profit buffer and integer rounding differences).
Harvest allocation
For each harvest report, optional wallet allocation uses end-of-report-block ownership:- Net report gain: Gross report gain minus gross report loss in underlying token atoms (signed integer division truncates toward zero before conversion).
- Report-block ownership: Wallet shares and total supply measured after all transactions in the report block.
- Assessed fees: Fees equal
min(Gross Gain, Management Fee + Performance Fee + Strategist Fee); zero gain charges zero.
Period-close workflow
To perform an audit-grade monthly or annual financial close:[!TIP] Practical Walkthrough: For an end-to-end walkthrough with live curl requests, actual response payloads, and ledger journal entries, see the Partner Reconciliation Walkthrough.
Additional recognition and measurement
When applying a separately supported carrying adjustment without altering underlying on-chain cash flows, adjust the book as follows: