Step 1 of the split daily-TVL chain. Discovers every (blockchain, owner, token, pricing_token, balance_type) that TermMax holds on-chain across V1, V1Plus, V2 and V2.01 vaults, markets, ERC4626 wrappers (Aave / Customize / For4626 variants), and GearingToken collateral. Step 2 (query 7443043) consumes this set to compute daily balances.

OUTPUT
- blockchain      varchar  ethereum / arbitrum / base / bnb / berachain / hyperevm
- owner           bytes    contract address holding the token
- token           bytes    token contract whose Transfer events feed the balance
- pricing_token   bytes    token to price the balance against (= `token` for raw rows; = the underlying asset for Aave aTokens)
- balance_type    varchar  'raw' for plain ERC20 holdings; 'aave_scaled' for Aave aTokens (so step 3 can rebase by liquidityIndex)

Materialized as `dune.termmax.result_termmax_tvl_daily_owner_tokens` (cron `0 0 * * *` UTC).

DISCOVERY METHODOLOGY
- Vaults: `initialParams.asset` from `evt_vaultcreated` (V1/V1Plus/V2/V2.01).
- Markets: `debtToken` from `evt_marketcreated` / `evt_createmarket`.
- ERC4626 wrappers come from three families:
    * `StableErc4626ForAave` / `VariableErc4626ForAave` — decoded via the
      `_call_initialize` table; the corresponding aToken is then looked up
      against `aave_v3_multichain.poolconfigurator_evt_reserveinitialized`
      to yield (vault, aToken, pricing=underlying).
    * `StableErc4626For4626` — decoded from the `ERC4626For4626Initialized`
      event (topic0 0x580b944c...) read directly from each chain's `*.logs`.
      This exposes both the `thirdPool` share AND the `underlying` so the
      wrapper's idle underlying buffer is registered as a separate row.
      The event-based path is required because Dune's `_call_*` tables only
      decode wrappers from the V1 4626 factory; later factories (V2 b/c)
      don't have decoded call tables, and call tables also don't carry
      `underlying`.
    * `StableErc4626ForCustomize` — decoded via `_call_*` and the
      `ERC4626ForCustomizeInitialized` event (topic0 0xb9be6a74...).
      For Customize wrappers we additionally register `(thirdPool, underlying)`
      to cover the case where the thirdPool itself holds the underlying.
- Market collateral (gearing-token-owned): MarketInitialized event
  (topic0 0x923c07a7...) decoded from raw chain logs. V2 markets use the
  same topic0 as V1 but a different data layout — `gt` is at slot 3
  (data offset 109) instead of slot 1 (offset 45). V1 (ethereum,
  arbitrum) is also covered via the decoded `_evt_marketinitialized`
  table. Raw-log decode is the only path for V2 markets across all
  five chains where it ships.

CALL- vs EVENT-TABLE ASYMMETRY
Pure RPC view-call getters (e.g. off-chain `vault.aToken()`) leave no
Dune trace. Affected wrappers were missed before the event-based path
was added. Workarounds — in order of robustness — are: decoded
`_call_initialize` on the proxy → raw-log decode of the initialization
event → submitting factory ABIs to Dune for new factory generations.

EXCLUDED CHAINS
bsquared (chain not on Dune), xlayer (decoder pipeline empty),
pharos (chain not on Dune), hyperliquid (no TermMax positions yet).
