/tres-asset-balance-validation

name: tres-asset-balance-validation
description: >
  Validate wallet balances in TRES Finance against DeBank and generate a discrepancy
  report. Use this skill whenever the user asks to validate, verify, cross-check, or
  audit their TRES balances against on-chain data or DeBank. Also trigger when the
  user asks if their balances are correct or wants to see discrepancies. Only
  EVM-compatible wallets are supported.

Tres Finance — Asset Balance Validation

Overview

This skill validates wallet balances in **Tres Finance** against **DeBank**, providing a clear discrepancy report as both an interactive HTML file and a PDF. It compares per-asset token amounts (including DeFi position underlying tokens) for each EVM wallet and flags matches, minor differences, major discrepancies, missing assets, untracked tokens, and unmatched positions.

> **Scope:** Only EVM-compatible wallets are supported (DeBank limitation). Exchange accounts, non-EVM chains, and empty wallets are skipped.

---

When to Use

Trigger this skill whenever a user asks to:

• Validate or verify their TRES balances
• Cross-check or audit wallets against external on-chain data
• Compare TRES data to DeBank
• Check if their balances are correct

**Example phrases:**

• *"Validate my balances"*
• *"Check my wallets against DeBank"*
• *"Are my TRES balances correct?"*
• *"Show me any discrepancies between TRES and on-chain data"*

---

Prerequisites

| Requirement | Details | |---|---| | TRES Finance access | Must be authenticated via `get_viewer` | | DeBank API key | Free key available at [cloud.debank.com](https://cloud.debank.com) | | EVM wallets | At least one `0x...` wallet tracked in TRES |

---

Process Overview

Step 1 — Authenticate with TRES

Call `get_viewer` to confirm the organization name.

Step 2 — Fetch wallets and balances from TRES

**IMPORTANT — Timeout handling:** The `internalAccount` query with both `balances` and `positions` will timeout for large orgs. Split into two separate queries:

**Query 1: Wallets + Balances only (no positions)**

query {
  internalAccount {
    results {
      id
      name
      identifier
      isExchange
      platforms
      balances {
        amount
        asset {
          symbol
          contract { identifier }
        }
        fiatValue { value unitPrice fiatCurrency }
      }
    }
  }
}

> **Note:** The `amount` field is returned as a **string**, not a number. Always `float()` it before arithmetic.

**Wallet classification:**

| Type | Condition | Validated? | |---|---|---| | EVM | `0x...` address + EVM platform + `isExchange: false` | ✅ Yes | | Exchange | `isExchange: true` | ❌ No | | Non-EVM | Bitcoin, Tezos, Tron, etc. | ❌ No | | Empty | No asset balances | ❌ No |

**Supported EVM platforms:** Ethereum, Arbitrum, Optimism, Polygon, Base, Avalanche, Binance, Gnosis Chain, zkSync, Fantom, Celo, Berachain, Linea, Scroll, Sonic, HyperEVM.

Step 3 — Fetch DeFi positions from TRES

**Do NOT use the `positions` sub-field on `internalAccount`** — it returns all historical snapshots (can be 3000+ entries per wallet) and will timeout or exceed token limits.

Instead, use the dedicated `getStatelessWalletsPositions` query which returns **current** positions only:

query {
  getStatelessWalletsPositions(
    walletIdentifiers: ["0x..."],
    platform: ETHEREUM,
    application: "aave-v3"
  ) {
    walletIdentifier
    displayName
    positionType
    platform
    children {
      symbol
      amount
      assetIdentifier
      fiatValue
    }
    fiatValue
    id
  }
}

**Required parameters:**

• `walletIdentifiers`: array of wallet addresses
• `platform`: must be an enum value like `ETHEREUM`, `POLYGON`, `ARBITRUM`, etc.

**Optional but recommended:**

• `application`: filter by protocol (e.g. `"aave-v3"`, `"verse"`, `"lido"`, `"merkl"`, `"uniswap-v4"`, `"sablier"`, `"ethena"`, `"stakewise"`, `"quickswap"`, `"steer"`, `"yieldnest"`, `"morphoblue"`)

**IMPORTANT:** Without the `application` filter, the query returns empty results. Always specify the application.

**Batching strategy:** 1. First, fetch DeBank `all_complex_protocol_list` for each wallet to discover which protocols have positions 2. Map DeBank protocol names to TRES application names (lowercase, hyphenated) 3. Use GraphQL aliases to batch multiple wallet+platform+application combos into a single query:

query {
  a1: getStatelessWalletsPositions(walletIdentifiers: ["0x..."], platform: ETHEREUM, application: "aave-v3") {
    walletIdentifier displayName positionType platform id
    children { symbol amount assetIdentifier fiatValue }
  }
  a2: getStatelessWalletsPositions(walletIdentifiers: ["0x..."], platform: ETHEREUM, application: "verse") {
    walletIdentifier displayName positionType platform id
    children { symbol amount assetIdentifier fiatValue }
  }
}

Keep each batched query to ~6 aliases max to avoid timeouts.

Step 4 — Retrieve DeBank API key

Read `DEBANK_API_KEY` from plugin user config — do **not** ask the user to paste it in chat. If the key is absent or empty, stop and display:

> "DEBANK_API_KEY is not configured. Please add it via the plugin settings (obtain your key at https://cloud.debank.com)."

Step 5 — Fetch DeBank data via bash

For each EVM wallet, fetch **two** endpoints:

1. **Token balances:** `all_token_list` — covers all chains without requiring a `chain_id` 2. **DeFi protocol positions:** `all_complex_protocol_list` — returns LP, staking, lending positions with underlying token amounts

Use `--data-urlencode` with `-G` so the wallet address is never shell-interpolated into the URL string:

# Token balances
curl -s -G \
  -H "AccessKey: ${user_config.DEBANK_API_KEY}" \
  --data-urlencode "id=$WALLET_ADDR" \
  "https://pro-openapi.debank.com/v1/user/all_token_list"

# DeFi positions
curl -s -G \
  -H "AccessKey: ${user_config.DEBANK_API_KEY}" \
  --data-urlencode "id=$WALLET_ADDR" \
  "ht