Building a Fee Distribution System for Your Protocol

Building a Fee Distribution System for Your Protocol

Imagine: your DeFi protocol generates $100k in fees daily, but token holders receive nothing. Uniswap V3 faced this before enabling the fee switch — governance redirected some fees to the treasury, requiring a reliable system for collection, accumulation, and distribution. We build such systems turnkey with gas optimization and security in mind. Synthetix StakingRewards — the benchmark pattern we adapt to your architecture.

Two Distribution Patterns: Push vs Pull

Why Pull Distribution Is Better Than Push?

Push distribution — send to everyone. The contract accumulates fees and periodically calls distribute(), which iterates over the staker list and transfers each their share. Simple to understand, complex to implement: an unbounded loop is a classic gas griefing vector. With 10,000 stakers, the transaction exceeds the block gas limit (requiring ~3 million gas instead of typical 150k).

Acceptable only for systems with an explicit cap on participants and batch processing (pagination). In most cases, it's the wrong choice. Pull distribution reduces gas costs for claims by 4x, critical when scaling to thousands of stakers.

Pull distribution — users claim themselves. The contract maintains rewardPerTokenStored — accumulated reward per unit of stake since launch. On each deposit/withdraw/claim, it updates userRewardPerTokenPaid for the specific user. Reward = (rewardPerTokenStored - userRewardPerTokenPaid) * balance.

This is the math from Synthetix StakingRewards — one of the most copied patterns in DeFi. Key property: Gas-complexity O(1) for claim, independent of staker count.

function earned(address account) public view returns (uint256) {
    return (
        (balanceOf[account] * (rewardPerToken() - userRewardPerTokenPaid[account])) / 1e18
    ) + rewards[account];
}

We use this pattern as the foundation for most fee distribution systems.

Fee Collection and Conversion

How to Convert Fees Without Loss?

Protocols generate fees in various tokens — swap fees in traded tokens, lending fees in debt tokens. Before distributing to stakers, you need to convert into a single target token (usually protocol token or USDC).

FeeCollector contract — aggregates fees from all source contracts. Periodically called by a keeper (Chainlink Automation, Gelato) or any user.

Conversion via DEX — swap accumulated fees into the target token through Uniswap V3. Important: converting a large volume at once creates price impact and MEV opportunities. Solution: convert in small batches using TWAP-oriented swaps or use Cow Protocol for MEV-protected swaps. This reduces slippage by 20-30%.

Distribution in multiple tokens — sometimes it's better not to convert but distribute in original fee tokens. Curve distributes 3CRV LP tokens (a stablecoin basket) instead of converting. This is more expensive to implement (multi-reward staking) but preserves value without slippage.

Multi-Channel Distribution

Rarely does the entire fee go only to stakers. Typical scheme:

Proportions set via governance-controlled parameters with timelock. FeeDistributor contract reads current proportions on each distribute() call.

veToken Model (Vote-Escrowed)

Curve introduced a model where to receive fees, you must lock CRV for up to 4 years. The longer the lock, the more veCRV, and the larger the fee share. This aligns interests: long-term holders get more. Implementation is more complex than basic staking — requires decay calculation of voting power, periodic checkpoints, integration with gauge voting.

If you need a veToken mechanism, that is a separate scope on top of basic fee distribution.

What Is Included

• Audit of existing architecture and selection of optimal pattern (pull/push/hybrid).
• Development of smart contracts: FeeCollector, FeeDistributor, Staking (with reentrancy protection, OpenZeppelin checks).
• Integration with DEX for conversion (Uniswap V3, Cow Protocol).
• Test writing (Foundry, fuzz, fork tests) covering edge cases.
• Deployment and verification of contracts on Etherscan.
• Documentation for governance and auditors.
• Post-launch support (monitoring, hotfixes).

We guarantee no reentrancy or frontrunning vulnerabilities. Team experience: 7+ years in blockchain, 50+ smart contracts, 5 years on the market. Contact us for an architecture audit — we'll assess your project in 1 day. Order a fee distribution system development – get architecture consultation.

Process and Timeline Estimates

Design (2-3 days). Determine source contracts, target token, distribution proportions, keeper mechanism for periodic conversion.

Development (5-8 days). FeeCollector + FeeDistributor + Staking contract. Tests with Foundry: correct calculation of earned() under changing total supply, correct handling of deposit/withdraw in the same block as distribute().

Integration tests. Fork test with a real Uniswap V3 pool to verify fee conversion. Fuzz tests on distribution math — edge cases with very small or very large balances.

Basic system (pull-distribution, one reward token, periodic collect) — 1 week. With DEX conversion and multi-reward — 1.5-2 weeks. veToken mechanism — additional 2-3 weeks. Cost is calculated individually based on complexity and required audit.

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.