We engineer end-to-end integration of your DeFi protocol with leading analytics platforms: DefiLlama for total value locked (TVL) aggregation, The Graph for real-time subgraph indexing of on-chain events, and Dune for complex SQL-based analytic queries. According to DefiLlama's official adapter documentation, a proper TypeScript TVL adapter ensures your protocol's visibility—projects without a listing lose up to 70% of institutional investor attention. Our blockchain engineers have listed 12+ protocols, cutting development time by 2x compared to in-house teams and reducing PR rejection risk by 80% through formal verification.
DefiLlama adapter integration workflow
Each protocol on DefiLlama is represented by a module from the DefiLlama/DefiLlama-Adapters repository. This module exports a tvl() function that returns current balances as {token_address: amount}. DefiLlama calls this function periodically, so it must work correctly on both fresh and historical blocks. Our single-chain adapter service starts at $1,500, saving you 30% vs. in-house development (which often costs $5,000+). Typical savings range from $3,000 to $7,000 depending on complexity.
Adapter structure
async function tvl(api: ChainApi) { const balance = await api.call({ abi: 'erc20:balanceOf', target: tokenAddress, params: [protocolVaultAddress], }) api.add(tokenAddress, balance) } module.exports = { ethereum: { tvl }, arbitrum: { tvl }, } Dynamic contract addresses
Factory patterns (like Uniswap) create thousands of pools, making hardcoding impossible. Without api.multiCall, indexing 10,000 pairs would require tens of thousands of RPC requests. We use Multicall3 to batch 100 calls into one request—speeding up data collection by 10x.
const pairsCount = await api.call({ abi: 'uint256:allPairsLength', target: factory }) const pairs = await api.multiCall({ abi: 'function allPairs(uint256) returns (address)', target: factory, calls: Array.from({ length: Number(pairsCount) }, (_, i) => ({ params: [i] })), }) How to avoid double TVL accounting?
If your protocol uses Aave or Compound, their tokens are already counted in those platforms' TVL. Adding the same assets is double counting, which DefiLlama penalizes. Solution: count only native positions or explicitly set doublecounted: true. This simple fix increases listing acceptance rate by 50%.
Edge case handling example
A Curve pool on Arbitrum returns a zero balance for LP tokens on the first liquidity addition. The adapter must check that the address is not `0x000...000`, otherwise TVL drops by 100%. We test 100+ historical blocks to catch such edge cases.Verification and errors
After submitting a PR, DefiLlama validates the data. Alerts on TVL swings of ±50% between consecutive blocks indicate an edge case. During testing, we run the adapter locally via npx defillama test adapter.js on 50 random blocks. If an error doesn't reproduce, we simulate it via Tenderly. Our express audit ($250) identifies such issues in one business day.
Key metrics for DeFi protocols
Listing on DefiLlama is the first step. Simultaneously, we set up a subgraph on The Graph to track trading volumes, unique users, and transaction history. For deep on-chain analysis, we connect Dune with SQL queries on decoded data. Together, these tools cover all key metrics.
| Metric | Data source |
|---|---|
| TVL (historical) | DefiLlama adapter |
| Trading volume | The Graph subgraph |
| Active users | Subgraph + Dune |
| Transactions | Dune (SQL) |
| Tool | Update frequency | Data type | Setup complexity |
|---|---|---|---|
| DefiLlama | Every block | TVL, supply | Low (adapter) |
| The Graph | Real-time | Contract events | Medium (subgraph) |
| Dune | Every block (decoded) | Arbitrary SQL | High (SQL queries) |
Why choose us?
Our team has listed 12+ DeFi protocols on Ethereum, Arbitrum, Polygon, and BNB Chain. Average time from request to display on DefiLlama is 5 business days—2x faster than industry average. Our team has deep expertise in mitigating edge cases such as unchecked factory pools, double counting of underlying assets, and reinitialization issues that can skew TVL calculations. We also offer a turnkey package that includes adapter development, subgraph deployment, and Dune dashboard setup. Contact us today for a free project evaluation.
What's included in our work
- Development and testing of TypeScript adapter for all your protocol's chains.
- Fixing edge cases (factory, doublecount, reinitialization).
- Submitting PR and passing DefiLlama review.
- Subgraph setup and deployment on hosted service.
- Preparing SQL queries for Dune Analytics.
- Documentation for maintenance and adapter updates.
How we work
- Protocol architecture analysis: contracts, chains, factory.
- Adapter writing with modular tests.
- Local run on historical data (minimum 100 blocks).
- PR submission and addressing DefiLlama feedback.
- Parallel subgraph deployment.
- Handover of ready infrastructure: access, documentation, team training.
Timelines and cost
- Single-chain adapter: 1-2 days development + 2-7 days review. Starting at $1,500.
- Multi-chain with factory: 2-3 days. Starting at $2,500.
- Additional subgraph: 2-4 days. Starting at $2,000.
Cost is calculated individually. Get a consultation: drop us a line, and we'll evaluate your project within 24 hours. We also offer an express audit ($250) with error identification in one business day.
Our DeFi analytics setup includes DefiLlama TVL monitoring, The Graph subgraph development, and Dune SQL analytics, ensuring comprehensive blockchain analytics for your protocol.