Aggregators
Routers and yield wrappers — protocols that route into the underlying DEXes and lending pools. Reported alongside but excluded from VWAP so we don't double-count the upstream price-discovery event.
Why aggregators don't price into VWAP
A trade routed through the Soroswap router still emits a SoroswapPair swap event on the underlying pair contract — that event is the one we VWAP. Counting the router-level call separately would double the same price-discovery moment.
The same logic applies to DeFindex: a vault deposit moves shares but doesn't set a price. The underlying Blend loan's collateral revaluation is what we care about, and we get that directly from Blend.
Soroswap Router
RouterMulti-hop convenience layer over Soroswap pair contracts. Trades that go through the router resolve to the same pair-level swap events we already index — the router is just the entry point.
- •No router-specific decoder needed for trades — the underlying SoroswapPair swap events fire regardless. The router contract is tracked separately for routed-via attribution (what % of pair volume arrived via the router).
- •Per the protocol-class contract, routers are in `/v1/sources` with class=aggregator and contribute zero VWAP weight by default. Including them would double-count the underlying pair trade.
- RouterCAG5LR…JDDH
- Pair factoryCA4HEQ…7AW2
DeFindex
Yield vaultYield-aggregator vaults that deposit into Blend and other lending pools. Earns the underlying borrow APY plus any incentive emissions, minus a management fee.
- •Position changes happen on the vault contract (deposit/withdraw); the actual yield-bearing legs are at Blend. We track the vault TVL but rely on Blend for the underlying yield observation.
- •Excluded from VWAP — yield-aggregator inflows are not price-discovery events.
- FactoryCDKFHF…NFKI
- USDC autocompoundCDB2WM…ZSAP
- EURC autocompoundCC5CE6…7JVI
- XLM autocompoundCDPWNU…DG2Z
Routed volume (24h)
Trades tagged routed_via — same-tx attribution of router invocations to underlying pair trades; vault entries are listed for completeness (they don't accrue per-tx tags)
| Aggregator | Kind | Protocol | Routed trades | Routed volume | Last routed |
|---|---|---|---|---|---|
| Loading attribution… | |||||
Attribution joins each router invocation to the pair-level swap trades in the same transaction (first-wins, never re-tagged). Volume is the USD valuation of the routed trades; “—” means the window's routed trades haven't received a USD valuation yet, not zero. A sub-invocation call (an aggregator wrapping the router) is attributed to that aggregator's own row when it's a registered contract; rows marked unverified or with * carry coverage caveats — hover for detail.
Reference price aggregators
Cross-check sources — never priced into our VWAP
| Source | Cost | Backfill | Role |
|---|---|---|---|
| Loading sources… | |||
Reference aggregators are excluded from VWAPby policy — they aggregate the same upstream venues we already index, so including them would double-count those underlying markets and let their methodology bleed into ours. They show up here so divergence flags can attribute “us vs CG” cleanly.