DeFi Analytics Setup: DefiLlama TVL, Subgraph, Dune

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%.

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.

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

1. Protocol architecture analysis: contracts, chains, factory.
2. Adapter writing with modular tests.
3. Local run on historical data (minimum 100 blocks).
4. PR submission and addressing DefiLlama feedback.
5. Parallel subgraph deployment.
6. 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.

DeFi Protocol Development

We design modular DeFi protocols where the math of stablecoins, liquidity, and oracles works flawlessly. Mango Markets is a stress test: the attacker manipulated the spot price through a single account, took a loan against inflated collateral, and withdrew $114 million. The oracle took the price from a single source without TWAP. Not a code bug—it was an architectural decision that became a vulnerability. Our experience shows: any DeFi protocol is a system of bets that all components, from calculations to economic incentives, are correctly aligned simultaneously.

We don't write code under the 'if it works, don't touch it' mindset. We model stress scenarios: cascading liquidations, depegs, flash loans. Only then do we build events that won't break the protocol.

Why are oracles a critical component of DeFi?

Most major DeFi hacks started with oracle manipulation. Let's break down the three layers we use in every project.

Spot price as oracle—not an option. Uniswap v2 spot price can be shifted by a flash loan in one transaction. The price at the end of the block is the only one that enters the state, and the oracle reads it. Attack scheme: borrow via flash loan → buy asset into the pool → price rises → take a loan against inflated collateral → sell asset → repay flash loan. One transaction.

TWAP as protection. Uniswap v3 observe() averages the price over a period (30 minutes). Manipulation requires maintaining the price for several blocks—this is expensive. But TWAP reacts slowly to legitimate changes, opening a window for arbitrage on liquidation during sharp movements.

Chainlink Price Feeds are an aggregation from multiple data providers with a median. Standard for lending. Problem: heartbeat 1–24 hours and deviation threshold 0.5%. If the price doesn't move, the feed may not update for a day. In volatile markets—lag.

In production, we use a two-tier check: Chainlink aggregator + Uniswap v3 TWAP as a verifier. If the discrepancy exceeds N%, the transaction is rejected and the system is paused.

How to protect a DeFi protocol from flash loan attacks?

Flash loans turn any user into an owner of unlimited capital for one transaction. Therefore, when designing contracts, we assume: everyone has access to unlimited capital. This completely changes the threat model.

Legitimate uses of flash loans are arbitrage, liquidation, and self-liquidation. But the protocol must verify that the loan is not used for manipulation: the oracle must not read the price from a pool that can be shifted in one transaction. We add checks on block.timestamp and minimum liquidity depth.

Key Components of DeFi Architecture

AMM: From x*y=k to Concentrated Liquidity

Uniswap v2 uses x * y = k. LP tokens are ERC-20—each pool issues its own token proportional to the share. Problem: liquidity is spread across the entire curve, most of it unused.

Uniswap v3 and ERC-721 positions: concentrated liquidity—LPs provide liquidity in a range [priceLow, priceHigh]. Capital efficiency up to 4000x for stable pairs. But ERC-721 breaks vault strategies built for ERC-20. Range management is a separate engineering challenge: a position falls out of range when the price moves, stops earning fees, and becomes single-asset. Protocols like Arrakis Finance automatically rebalance. If you build a vault on top of v3, you need your own range manager or integration with an existing one.

Slippage in v3 is calculated via sqrtPriceX96—96-bit fixed-point math. Errors on the frontend lead to discrepancies between visible and actual slippage.

Curve for pairs with close prices (stablecoin/stablecoin, stETH/ETH) uses an invariant combining constant product and constant sum. Lower slippage within the peg range. Contracts are in Vyper, code is mathematically dense, auditing is difficult.

Lending Protocols: Collateral, Liquidation, Bad Debt

LTV defines the maximum loan against collateral. Liquidation threshold is the level for liquidation. The difference is the buffer for the liquidator. Typical example: LTV 75%, liquidation threshold 80%, bonus 5%. If the price drops 20%+, the position is open for liquidation.

Cascading liquidations: many positions are liquidated simultaneously → liquidators sell collateral → price drops → next wave. LUNA/UST 2022 is a classic cascade.

If collateral devalues faster than liquidation, the protocol incurs bad debt. Aave uses a Safety Module (staked AAVE), Compound uses reserves. Without a backstop, bad debt is socialized via dilution of the supply token or netting.

Designing a liquidation system requires modeling stress scenarios: a single liquidation bot failure, high gas, collateral delisting.

Yield Farming and Incentive Mechanics

Liquidity mining distributes governance tokens to LP providers. Problem: mercenary capital—farmers come, sell tokens, leave. TVL is illusory.

Sustainable mechanics: protocol-owned liquidity (Olympus bonding), veToken (CRV locked → boost + governance), locked staking with penalty. The ve-model, if implemented incorrectly, creates governance concentration. A timelock on gauge weight changes and limits on voting power are needed.

What Our DeFi Protocol Development Includes

• Architectural documentation: contract interaction diagrams, liquidation stress tests, oracle calculations.
• Implementation in Solidity 0.8.x with OpenZeppelin 5.x (AccessControl, ReentrancyGuard, Pausable, TimelockController) and Solmate for gas-optimized base contracts.
• Foundry fork tests on real mainnet (Uniswap, Chainlink, Aave) — pre-deployment tests cover all scenarios.
• Audit: at least two independent auditors for TVL over $1M. Code4rena or Sherlock for bug bounty.
• Deployment with Gnosis Safe 3/5 multisig + timelock 48–72 hours.
• Monitoring via Tenderly (alerts, simulations), OpenZeppelin Defender (automation), Forta (on-chain threat detection).
• Post-launch support: updates, patches, upgrades via proxy.

Our Expertise and Experience

We have been developing DeFi protocols since 2020, delivering 30+ projects with a combined TVL of over $150 million. Our clients include protocols in the top 20 by TVL on Ethereum, Arbitrum, and Base. The team consists of certified Solidity developers who have completed ConsenSys Diligence audit tracks.

DeFi basic principles that we apply in practice.

Timelines

• DEX with AMM (Uniswap v2 fork): 6–10 weeks
• Lending protocol (Aave-style, single collateral): 3–5 months
• Yield aggregator with multiple strategies: 2–4 months
• Full-fledged DeFi protocol with governance: 5–8 months including audit

Cost is calculated individually—contact us for a project estimate.

Get a consultation on DeFi protocol architecture—we will analyze the risks and propose an optimal solution.