Variational On-chain Verification
Variational intends to use 100% of treasury-directed revenue for VAR buy-and-burn after TGE. perpdex.io uses positive daily treasury USDC balance changes as an experimental reference, without treating balance changes as confirmed revenue or executed buybacks.
On-chain Verification Overview
Compare Variational official data with Arbitrum Settlement Pool snapshots while separating on-chain facts, official data, derived metrics and experimental research.
On-chain and Official Settlement Pool TVL, plus Core OLP Vault
On-chain and API TVL both use the Settlement Pools scope. The Core OLP Vault is shown separately and excluded from both
Independent On-chain Verification
On-chain Settlement Pool TVL is only native USDC held by all Settlement Pools at one Arbitrum block; the Core OLP Vault is shown separately.
Official Public Data
The Variational public stats API provides TVL, OI and 24H volume. TVL is verified on the same scope as the on-chain USDC balance sum across Settlement Pools and excludes the Core OLP Vault.
Deterministic Derivation
Net user exposure, implied OLP exposure, the like-for-like TVL difference, external net inflow and Core OLP net deployment to Pools use explicitly separated scopes.
Experimental Research Layer
Inferences are never described as actual positions, equity, solvency or hedge completion.
External inflows/outflows include only native USDC transfers between the official Core OLP address and non-Settlement-Pool addresses. Verified user deposits include only ordinary funding in the previous complete UTC day where a successful depositUSDC call names a sender registered as that Pool's user-side participant and the same transaction contains one exact native-USDC transfer. tx.from may be a relayer and is not used as user identity. Atomic and other channels are not yet included.
Omni Settlement Pools are bilateral User ↔ OLP relationships, so PoolCreated.otherAddresses are shown as user-side settlement addresses. Current public on-chain events still do not directly expose instrument, side, quantity or entry price.
To control database, CPU and RPC load, core events and compact Core OLP external-flow evidence each retain at most 100,000 rows. Ordinary user-deposit evidence is retained for 35 days and daily snapshots for 30 complete UTC days. Page requests never call the RPC.
The OLPToPoolTransfer event name does not prove that its source is the official Core OLP; Pool balance is not OLP equity; ordinary user deposits do not represent every funding channel; implied OLP exposure is not an actual external hedge; and vault / exposure is not a solvency ratio.