Repository inventory

hydric-org/skills

Skills indexed from this repository, with install-style signals scoped to the repo.
2 skills0 GitHub stars0 weekly installsGitHubOwner profile

Overview

This skill is a practical guide for interacting with the Hydric Liquidity Pools Indexer (Envio/HyperIndex). It explains how to query real-time and historical liquidity pool metrics, fetch cross-chain token metadata and prices, and understand tracked vs untracked safety rules. Use it to build dashboards, analytics pipelines, or programmatic alerts against unified DeFi data across multiple chains.

How this skill works

The indexer exposes a Hasura-style GraphQL API backed by a unified Postgres schema that aggregates liquidity data from supported chains. Core entities include Pool, SingleChainToken, and PoolHistoricalData; numeric financial fields are returned as strings to preserve precision. Queries support polymorphic pool types (V3, V4, Algebra, Slipstream) and pre-calculated rolling stats for 24h/7d/30d/90d windows.

When to use it

  • Fetch live TVL, swap volume, fees, or APY/yield for pools across supported chains.
  • Retrieve token metadata, tracked USD price, and aggregated liquidity per token.
  • Build historical charts or time-series analytics using PoolHistoricalData.
  • Search tokens or pools with robust fuzzy matching using normalizedSymbol/normalizedName.
  • Validate safety-sensitive values by preferring tracked fields over raw computations.

Best practices

  • Always use trackedTotalValueLockedUsd and trackedUsdPrice for safety-critical calculations; untracked values are vulnerable to manipulation.
  • Lowercase addresses and follow the global ID format <chainId>-<lowercase_address> when constructing IDs.
  • Query normalizedSymbol and normalizedName (not only symbol) for reliable fuzzy search across variants and special characters.
  • Parse numeric strings into BigInt/Decimal types in your client to preserve precision; do not assume native numbers.
  • Request specific nested pool type objects (v3PoolData, v4PoolData, algebraPoolData) when you need type-specific fields.

Example use cases

  • Leaderboard: query top pools by tracked TVL with protocol metadata and 24h stats for a frontend dashboard.
  • Token lookup: fuzzy-search tokens across chains and return tracked price + total pooled liquidity for token comparison.
  • Time-series analytics: pull DAILY PoolHistoricalData for 90 days to compute rolling yields or volume trends.
  • Security checks: compare totalValueLockedUsd vs trackedTotalValueLockedUsd to detect potentially untrusted liquidity.
  • Cross-chain aggregation: aggregate trackedTotalValuePooledUsd for a token across chainIds to measure multi-chain exposure.

FAQ

Financial fields are strings to preserve BigInt/Decimal precision. Parse them to the appropriate numeric type in your client.

Which TVL field should I use for production?

Always prefer trackedTotalValueLockedUsd; it applies price filters and whitelists to reduce spoofing risks.

2 skills

More from this maintainer
Other repositories and skills published under the same GitHub owner.
Skills library
Jump back to the full directory or explore grouped topics.
Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational