Building a Weighting System for Your Crypto Index

Developing a crypto index without a thoughtful asset weighting system is not an index—it's an arbitrary basket. We've encountered projects where BTC and ETH dominance in a market cap index reached 80%, defeating the purpose of diversification. In one real case, an MCW index on Ethereum mainnet required daily rebalancing with gas costs of $50–200 per operation, eating up to 30% of annual returns. We replaced the methodology with SQRT and moved to Arbitrum: gas dropped to $2, diversification improved, and rebalances became infrequent. Our approach is to select a methodology aligned with portfolio goals and implement it in Solidity with minimal gas and maximum reliability. We have 10+ years of experience in DeFi and have developed over 15 weighting systems for various indices.

How to Choose an Asset Weighting System for a Crypto Index?

Market Cap Weighting (MCW)

Classic approach: weight proportional to market cap. BTC + ETH occupy 70–80% of any MCW index—resulting in low diversification and mega-cap bias. Solidity implementation: fetch prices via Chainlink, multiply by circulating supply (stored off-chain, updated via multisig). Issue: supply data cannot be reliably obtained on-chain—manipulation via multisig.

Square Root Market Cap (SQRT MCW)

Apply sqrt to market cap: weight = sqrt(mcap_i) / sum(sqrt(mcap_j)). ETH drops from 65% to ~40%, small-caps gain noticeable weight. Index Coop uses a variant in DPI. On-chain sqrt—no built-in Solidity function; use Babylonian method or Solmate library. Example code:

function sqrt(uint256 x) internal pure returns (uint256) {
    if (x == 0) return 0;
    uint256 z = (x + 1) / 2;
    uint256 y = x;
    while (z < y) { y = z; z = (x / z + z) / 2; }
    return y;
}

Equal Weight (EW)

All assets have equal weight—maximum diversification, but rebalancing costs high: with 20 assets, every price move creates drift. Daily rebalancing on Ethereum mainnet—guaranteed loss to gas. Realistic only on L2s (Arbitrum, Base) with gas in cents.

Volatility-Adjusted Weighting

Weight inversely proportional to volatility—less volatile assets weigh more. Goal: minimize overall portfolio volatility. On-chain calculation: historical prices for realized volatility via Chainlink (expensive) or a custom rolling window. For 20 assets with a 30-day window—600 storage entries, updated once a day—moderate load.

How to Implement Weighting in Solidity Without Losing Precision?

Fixed-Point Arithmetic for Precision

All calculations in integers with 18 decimal precision (WAD = 1e18). Normalization example:

uint256 totalWeight = 0;
for (uint i = 0; i < n; i++) {
    totalWeight += rawWeights[i];
}
for (uint i = 0; i < n; i++) {
    normalizedWeights[i] = rawWeights[i] * 1e18 / totalWeight;
}

Check for overflow with large rawWeights and ensure normalizedWeights sum to 1e18 within ±1.

Rebalancing Trigger

Two approaches: time-based (every N blocks) and drift-based (deviation from target weight > threshold, e.g., 5%). Drift-based is more efficient: in stable markets, few rebalances. Implement via Chainlink Automation: checkUpkeep returns true if |currentWeight - targetWeight| > threshold for any asset. A 5% threshold reduces rebalances by 3–5 times, saving up to 40% in gas.

Trigger Comparison

Integration with Swaps

During rebalance, sell overweight assets and buy underweight ones. Optimal route: via a DEX aggregator (1inch, Paraswap) or directly Uniswap v3 Universal Router. Atomic rebalancing is critical: all swaps in a single transaction via multicall or try/catch with revert. If the transaction reverts mid-way, the index becomes stuck.

What the Process Includes

1. Requirements analysis—select methodology, data sources, rebalancing trigger.
2. Architecture design—smart contract specification, oracle layout.
3. Development—WeightCalculator, Rebalancer, integration with external protocols.
4. Testing—unit tests for weight calculations, fork tests with real prices and rebalance simulation.
5. Deployment and documentation—deployment instructions, contract addresses, ongoing support.

Timeline and Cost

Timeline depends on complexity: for a single methodology—3 to 5 days; for a multi-methodology system with governance switching—1–2 weeks. Cost is calculated individually after discussing your index.

Contact us for a consultation—we'll help you choose a methodology and evaluate the project. Get a free analysis of your index and launch weighting with minimal risk.

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.