DeFi Portfolio Dashboard Development: Aggregation, P&L, Multi-Chain

We build turnkey DeFi portfolio dashboards. Imagine a user holding USDC in Aave, an ETH-USDC LP in Uniswap V3, wstETH in Lido, and an open perpetual position on GMX. Four different protocols, four different ways to represent positions, four different APIs or subgraphs. The dashboard's job is to aggregate everything into a single screen with real P&L numbers. Our experience shows that 80% of the effort goes into the data layer: normalizing data from different sources and correctly computing stale versus live balances. We guarantee block-level accuracy and minimal latency. Contact us to evaluate your project stack.

How is P&L and impermanent loss calculated?

The hardest part is correctly calculating unrealized P&L for LP positions. For Uniswap V3, a position is an NFT with specific tickLower, tickUpper, and liquidity. Current token0 and token1 amounts depend on the pool's current sqrtPriceX96. The formula is nontrivial:

function getAmountsFromLiquidity(
  sqrtPriceX96: bigint,
  sqrtRatioAX96: bigint,
  sqrtRatioBX96: bigint,
  liquidity: bigint
): [bigint, bigint] {
  if (sqrtPriceX96 <= sqrtRatioAX96) {
    const amount0 = (liquidity * (sqrtRatioBX96 - sqrtRatioAX96) * Q96) 
                    / (sqrtRatioBX96 * sqrtRatioAX96)
    return [amount0, 0n]
  } else if (sqrtPriceX96 < sqrtRatioBX96) {
    const amount0 = (liquidity * (sqrtRatioBX96 - sqrtPriceX96) * Q96) 
                    / (sqrtRatioBX96 * sqrtPriceX96)
    const amount1 = (liquidity * (sqrtPriceX96 - sqrtRatioAX96)) / Q96
    return [amount0, amount1]
  } else {
    const amount1 = (liquidity * (sqrtRatioBX96 - sqrtRatioAX96)) / Q96
    return [0n, amount1]
  }
}

Impermanent loss is calculated as the difference between the current position value and the value if the same assets were simply held since entry. The dashboard must store entry price and initial amounts at position opening.

What data sources do we use?

We combine on-chain direct calls and indexers. The most accurate way to get a balance is a direct eth_call to the contract. For token balance — balanceOf(). For an Aave position — getUserAccountData(). This is always current but slow: each protocol requires separate calls, and latency grows linearly with dozens of protocols. The solution is Multicall3 (contract 0xC...A11, deployed on all major EVM chains): batching 50+ calls into one transaction. Response time is like one RPC call instead of 50. Comparison: Multicall3 is 20x faster than sequential calls.

import { multicall } from 'viem'

const results = await multicall(client, {
  contracts: [
    { address: AAVE_POOL, abi: aavePoolAbi, functionName: 'getUserAccountData', args: [userAddress] },
    { address: USDC_TOKEN, abi: erc20Abi, functionName: 'balanceOf', args: [userAddress] },
    { address: UNISWAP_POSITION_MANAGER, abi: nftAbi, functionName: 'balanceOf', args: [userAddress] },
  ]
})

For historical data (transaction history, PnL over time) direct calls don't work — we need indexers.

We use The Graph for historical data. Uniswap, Aave, Compound, Curve, Balancer all have official subgraphs on The Graph Network. A subgraph provides a GraphQL API to query historical events: deposits, withdrawals, swaps, liquidations.

query UserPositions($user: String!) {
  aaveV3_deposits(where: { user: $user }, orderBy: timestamp, orderDirection: desc) {
    amount
    reserve { symbol, decimals, priceInUSD }
    timestamp
  }
  aaveV3_borrows(where: { user: $user }) {
    amount
    reserve { symbol }
    currentVariableBorrowRate
  }
}

Problem: different protocol versions have different subgraphs. Aave V2 on Ethereum, Aave V3 on Polygon, Aave V3 on Arbitrum — three different subgraphs with different schemas. Normalization is the main engineering task of the dashboard. We use a unified abstraction layer that maps all schemas into a single data model.

Alchemy and Moralis as API-over-RPC. Alchemy API provides ready-made methods: getTokenBalances() returns all ERC-20 balances of an address without iterating contracts. getAssetTransfers() provides transfer history. This significantly simplifies initial implementation, but costs money at high load. Moralis additionally aggregates NFT positions and DeFi protocol positions via their DeFi API — paid, but saves months of custom data layer development. For an MVP, Alchemy + The Graph for key protocols is justified. For production with tens of thousands of users, we recommend a custom indexer.

Multi-Chain Aggregation

A typical user is active on Ethereum mainnet, Arbitrum, Polygon, and Base. The dashboard must show the total portfolio across chains. Our approach: parallel requests to each chain's RPC via Promise.all(), normalizing balances into USD with a unified price oracle. We use the Coingecko API or DefiLlama Price API to fetch current prices by token address and chain ID. The cross-chain identity problem: the user address is the same on all EVM chains (ECDSA), but a smart contract wallet (Safe, Argent) may have different addresses on different chains if deploy was not synchronized. We support multi-address mode: the user can add multiple addresses to one profile.

How We Ensure Performance

Backend: Node.js + TypeScript with viem for RPC. Redis for caching balances (TTL 30 seconds for live data, 5 minutes for historical). PostgreSQL for storing historical portfolio snapshots (to build equity curves).

Frontend: React + wagmi v2 for wallet connection, Recharts or TradingView Lightweight Charts for graphs, Tanstack Query for data fetching with automatic refetch every 30 seconds.

WebSocket for real-time updates: subscribing to eth_subscribe("newHeads") triggers balance updates on each new block — providing liveliness without wasteful polling.

const transport = http('https://mainnet.infura.io/v3/YOUR_KEY')
const client = createPublicClient({ transport })

What Is Included

• Data layer documentation (data schemas, normalization description).
• Full dashboard code repository access.
• 2 hours of online team training.
• 2 weeks of free post-deployment support.
• Optional SLA for ongoing maintenance.

Our track record: 5 years in blockchain development, 20+ successful DeFi projects. We guarantee the dashboard will run without downtime and with block-level accuracy.

Process

1. Analysis (1–2 days). List target protocols and chains, prioritize by popular audience use cases.
2. Data layer (5–7 days). Build Multicall aggregator, integrate The Graph for key protocols, normalize into a unified position schema.
3. Backend API (3–5 days). Deliver REST/GraphQL API for frontend, caching, portfolio history.
4. Frontend (5–7 days). Implement wallet connection, total balance view, per-protocol details, charts.

Timeline Estimates

Get a consultation for your project — we will assess complexity and timelines for free.

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.