hive-defi-research

hive-defi-research — DeFi Protocol Analysis

Answer protocol, TVL, fee, revenue, yield, stablecoin, bridge, and chain-level DeFi questions with like-for-like, timestamped metrics.

Task toolset and identifiers

Toolset: defi_protocol_analysis. Read hive://toolsets/defi_protocol_analysis before execution; it is authoritative for the current output schema, material-call budget, phases, fallback condition, and stop conditions.

• Required: protocol name/slug or chain.
• Optional: time window, metric type, yield pool, stablecoin, bridge.

Ask for a protocol slug, or choose a provider-supported slug only when the user clearly named the protocol.

Before choosing endpoints, select exactly one matching entry from the exact workflow's routes[]. Follow its ordered steps, use a fallback only under that step's published condition, stop at four material calls, and preserve the selected route_id in the typed result. The broad coverageCatalog is discovery coverage, not an execution plan.

Procedure

1. Resolve the protocol slug or chain name.
2. Call search_tools for protocol, TVL, fee/revenue, yield, stablecoin, bridge, or chain-metric capabilities.
3. Call get_api_endpoint_schema for each endpoint before calling it.
4. Pull only the metrics the question needs.
5. Compare protocols only with like-for-like metrics and timestamps, and state when a metric is unavailable or stale.

Bounded calls

• Limit protocol lists and yield pools.
• Avoid comparing TVL snapshots from different dates without a caveat.
• Mark missing fee/yield/stablecoin metrics instead of omitting them.

Worked example

User: "Compare Aave and Compound — TVL and fees, which one actually earns more?"

1. search_tools → {"query": "protocol tvl fees revenue defi", "limit": 5}
2. get_api_endpoint_schema for the protocol-metric endpoints returned, then invoke_api_endpoint once per protocol slug with schema-valid arguments.
3. Normalize: same metric definitions, same window, same timestamps.
4. Summarize the comparison in a table, with provider and fetched_at per metric, using the report template.