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

Router

Multi-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.
HomepageContracts source

DeFindex

Yield vault

Yield-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.
Homepage

Coming next

Routed-via attribution (what fraction of each underlying pair volume came in via a router or aggregator) is in the database schema — see migration 0025_create_routers_and_aggregator_exposures.sql — but needs the routers registry seeded on r1 before the attribution endpoint goes live.