EVM/SVM/TVM `/v2` endpoints

[DenisCarriere]

The following endpoints will be subject to breaking changes, endpoints will be scoped as /v2.

1. DEX /pools (evm|tvm|svm)

✅ NEW

• Pool Metadata
  • tokens Array (Symbol/Name/Decimals)
    • Query filter by token
  • factory_name
  • pool_name
• Pool Statistics
  • uaw (unique active wallets, using uniq_tx_from or new MV table)
    • Depends on Compute UAW using dedicated MV table substreams-evm#69
  • transactions (total transactions per pool)
  • last_activity (last swap activity inside this particular pool)
• Pool Creation
  • transaction_id
  • datetime
  • timestamp (UTC seconds)

❗ DEPRECATE

• Pool Metadata
  • input_token
  • output_token

2. DEX /dexes (evm|tvm|svm)

✅ NEW

• Factory Metadata
  • factory_name
• Factory Statistics
  • pools (total count of pools)
  • last_activity (last swap activity inside this particular pool)
  • is_aggregator (true/false) (in case of Jupiter)

🏎️ 🌬️ PERFORMANCE

• uaw (unique active wallets per factory)
  • Depends on: Compute UAW using dedicated MV table substreams-evm#69

3. DEX /swaps (evm|tvm|svm)

✅ NEW

• Swap Metadata
  • ordinal (Log event Ordinal, unique per swap within a single block)
  • transaction_from (The wallet that initiated the transaction that contains the swap)
    • This field is used to compute uaw (Unique Active Wallets)
  • user (new standard for emitting the user that performed the swap)

🔖 INFO

• Native token (ETH/BNB, etc..) are defined as 0x0000000000000000000000000000000000000000 token contract

❗ DEPRECATE (removed)

• caller (not all chains support extracting Log events by calls, RPC poller chains would be blank for this field)
• legacy Uniswap V2 fields (no longer supported in DEXs, replaced by user field)
  • recipient
  • sender

❗ DEPRECATE (moved to SDK)
https://github.com/pinax-network/token-api-sdk

• Move fields to Token API SDK (since they are all "derived" fields, reduces payload footprint)
  • input_value
  • output_value
  • price
  • price_inf
  • summary (Allow users to provide their own Summary format via SDK)

4. DEX /pools/ohlc

• ❓ SUPPORT for multi-token handling
  • Currently Tri-pools have mixed results in OHLC data
• ❓ How to handle volume field when stable token is either token?
  • Should symbol be provided to Volume? (ex: 4428564.077931 WTRX)

[matthewdarwin]

Related: #294