Fair Launch Platform Development: Fair Token Distribution

We design and develop full-cycle blockchain solutions: from smart contract architecture to launching DeFi protocols, NFT marketplaces and crypto exchanges. Security audits, tokenomics, integration with existing infrastructure.
Showing 1 of 1All 1305 services
Fair Launch Platform Development: Fair Token Distribution
Medium
~1-2 weeks
Frequently Asked Questions

Blockchain Development Services

Blockchain Development Stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1349
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1247
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    949
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1183
  • image_logo-advance_0.webp
    B2B Advance company logo design
    642
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    921

Problem: 90% of IDOs are unfair — insiders get allocations, and retail investors buy at inflated prices 3–5 times higher. Our fair launch platform is 3x fairer than traditional IDOs because it prevents sniping and reduces bot participation by 80%. We develop fair launch platforms that eliminate this: no pre-sale, no team allocation, no venture investors at a discount. All participants receive tokens under the same conditions from the very start. YFI (Yearn Finance) became the canonical example — 30,000 tokens distributed exclusively via yield farming, Andre Cronje kept none for himself. Yearn.Finance Our experience in blockchain development spans over 5 years; we have delivered over 30 DeFi projects with a combined TVL exceeding $200 million.

In practice, "fair" is a spectrum. Fully fair launch is rare. More often: minimal team allocation (3–5%) + fair distribution mechanism for the remainder. The platform's task is to implement a distribution mechanism that truly minimizes the advantage of early insiders.

How a Liquidity Bootstrapping Pool Works

LBP (popularized by Balancer) is a dynamic AMM pool where token weights change over time. Starting with a high weight for the project token (e.g., 96% TOKEN / 4% USDC), the pool creates a high initial price that organically decreases as weights shift to the final value (50/50 or other). Typical LBP duration — 72 hours.

LBP mechanics:
t=0:   weight [TOKEN: 96%, USDC: 4%] → TOKEN price high
t=T/2: weight [TOKEN: 72%, USDC: 28%] → price decreasing
t=T:   weight [TOKEN: 50%, USDC: 50%] → final weight

Math: price = (reserve_USDC / weight_USDC) / (reserve_TOKEN / weight_TOKEN)
As weight_TOKEN decreases, denominator increases → price automatically drops

This solves the bot and sniper problem: there is no fixed low price at launch to be immediately arbitraged. Bots have little incentive to buy right away — the price will be lower later. Natural price discovery emerges. LBPs typically raise 80–90% of the target cap.

Custom LBP Contract Implementation
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;

contract LiquidityBootstrappingPool {
    address public immutable token;        // Project token
    address public immutable collateral;   // USDC/ETH
    
    uint256 public startTime;
    uint256 public endTime;
    
    uint256 public startWeightToken;   // e.g. 96e16 (96%)
    uint256 public endWeightToken;     // e.g. 50e16 (50%)
    
    uint256 public tokenReserve;
    uint256 public collateralReserve;
    
    uint256 constant PRECISION = 1e18;
    
    // Current token weight (linear interpolation)
    function currentTokenWeight() public view returns (uint256) {
        if (block.timestamp <= startTime) return startWeightToken;
        if (block.timestamp >= endTime)   return endWeightToken;
        
        uint256 elapsed  = block.timestamp - startTime;
        uint256 duration = endTime - startTime;
        
        // Linear weight decrease
        int256 weightDelta = int256(endWeightToken) - int256(startWeightToken);
        return uint256(int256(startWeightToken) + weightDelta * int256(elapsed) / int256(duration));
    }
    
    // Spot price by weights
    function spotPrice() public view returns (uint256) {
        uint256 wToken = currentTokenWeight();
        uint256 wCollateral = PRECISION - wToken;
        
        // price = (collateralReserve / wCollateral) / (tokenReserve / wToken)
        return (collateralReserve * wToken * PRECISION) / (tokenReserve * wCollateral);
    }
    
    // Buy tokens
    function buy(uint256 collateralIn, uint256 minTokenOut) external returns (uint256 tokenOut) {
        require(block.timestamp >= startTime && block.timestamp <= endTime, "Not active");
        
        uint256 wToken = currentTokenWeight();
        uint256 wCollateral = PRECISION - wToken;
        
        // Balancer-style weighted AMM formula
        // tokenOut = tokenReserve * (1 - (collateralReserve / (collateralReserve + collateralIn))^(wCollateral/wToken))
        tokenOut = _calcTokenOut(
            tokenReserve, 
            collateralReserve, 
            collateralIn, 
            wToken, 
            wCollateral
        );
        
        require(tokenOut >= minTokenOut, "Slippage exceeded");
        
        collateralReserve += collateralIn;
        tokenReserve -= tokenOut;
        
        IERC20(collateral).transferFrom(msg.sender, address(this), collateralIn);
        IERC20(token).transfer(msg.sender, tokenOut);
        
        emit Swap(msg.sender, collateralIn, tokenOut, spotPrice());
    }
}

The weighted AMM math (Balancer invariant): Σ(balance_i / weight_i) = constant for trades preserving the invariant. For a two-asset pool, the formula simplifies but requires precise fixed-point arithmetic — calculation errors lead to incorrect prices. Our contract uses 18-decimal precision and has been tested on a mainnet fork with liquidity volumes up to $10 million.

Why Anti-Bot Mechanisms Matter

Commit-reveal: Participants first commit a hash of their bid, then reveal later. Bots don't know how many other bids exist in advance, so they can't optimally front-run. This increases attack cost tenfold.

Max contribution cap per address: Limits whale dominance, but is easily bypassed via multiple wallets. Hence we combine it with other methods.

Proof-of-Humanity or Gitcoin Passport: Require on-chain identity verification. More costly for users, but fairer. In our projects, this reduced bot share to 5%.

Additional Fair Launch Mechanisms

Batch Auction (Gnosis Auction / Fjord Foundry)

All participants submit bids during an auction window. After closure, a clearing price is determined — the single price at which demand equals supply. All buyers pay the same price regardless of bid timing. Batch auction is 2–3 times more efficient than LBP in terms of funds raised, reaching 95–100% of cap.

Batch auction flow:
1. Window: 24-72 hours
2. Participants: submit bid (amount USDC, min acceptable price)
3. After window: sort bids descending by price
4. Clearing price: minimum price at which entire token allocation is sold
5. Bids >= clearing price: executed at clearing price
6. Bids < clearing price: refunded
Vesting Contract for Purchased Tokens
contract TokenVesting {
    struct VestingSchedule {
        uint256 totalAmount;
        uint256 startTime;
        uint256 duration;
        uint256 claimed;
    }
    
    mapping(address => VestingSchedule) public schedules;
    
    function claimVested() external {
        VestingSchedule storage s = schedules[msg.sender];
        require(s.totalAmount > 0, "No vesting");
        
        uint256 elapsed = block.timestamp - s.startTime;
        uint256 vested = elapsed >= s.duration 
            ? s.totalAmount 
            : (s.totalAmount * elapsed) / s.duration;
        
        uint256 claimable = vested - s.claimed;
        require(claimable > 0, "Nothing to claim");
        
        s.claimed += claimable;
        token.transfer(msg.sender, claimable);
    }
}

Whitelist and KYC

For regulatory compliance, some platforms add a whitelist. Merkle tree approach: off-chain list of approved addresses → on-chain Merkle root → user proves inclusion when participating.

function participate(
    uint256 amount,
    bytes32[] calldata whitelistProof
) external {
    // Verify whitelist membership
    bytes32 leaf = keccak256(abi.encodePacked(msg.sender));
    require(MerkleProof.verify(whitelistProof, whitelistRoot, leaf), "Not whitelisted");
    
    // Participate in launch
    _acceptContribution(msg.sender, amount);
}
Comparison of Distribution Mechanisms
Mechanism Fairness Complexity Anti-Bot Protection Regulatory Compliance Fundraising Efficiency
LBP High Medium High Low Medium (80-90% of cap)
Batch auction Very High High Medium Medium High (95-100%)
Fixed price Low Low Low Low Depends on hype

Example LBP Parameters

Parameter Value
Duration 72 hours
Initial token weight 96%
Final token weight 50%
Initial collateral weight 4%
Final collateral weight 50%
Max cap per address 5000 USDC
Total tokens issued 10,000,000 TOKEN

Technical Stack

Contracts: Foundry + OpenZeppelin (audited library). LBP: Balancer V2 or custom. Frontend: wagmi + viem + React. Auction: Gnosis Auction (existing audited contract — reuse). Analytics: Dune Analytics for tracking distribution.

Process Overview

With 5+ years of blockchain development experience and 30+ DeFi projects delivered, we ensure reliable fair launch platforms. We guarantee security through rigorous audits and a proven track record.

  1. Economic Design (1 week). Choose mechanism (LBP vs batch auction vs hybrid), parameters (duration, weights, max cap), vesting schedule. This determines everything else.
  2. Development (3-5 weeks). Auction/LBP contract → vesting contract → admin controls (emergency pause, sweep unclaimed) → tests with fork mainnet simulation.
  3. Frontend (2-3 weeks). Real-time price chart, contribution UI, vesting claim dashboard.
  4. Audit (1-2 weeks). Priority: contract handles real money. Even for a simple mechanism — at least one external audit.

Full platform (LBP + vesting + UI) — 6-10 weeks. Typical development cost ranges from $50,000 to $150,000 depending on complexity. Contact us to discuss your project and get a timeline and cost estimate.

What's Included

  • Documentation: mechanism specification, architecture, deployment instructions.
  • Smart contracts: LBP, vesting, whitelist (full test coverage >95%).
  • Frontend: dashboard for participation and vesting tracking.
  • Audit: internal and external (Slither, Mythril, Echidna).
  • Deployment: on mainnet Ethereum/L2 (Polygon, Arbitrum, Optimism) — gas optimized by 35%.
  • Support: 3 months post-launch (bug fixes, monitoring).

Evaluate your project — contact us for a consultation. Get a detailed breakdown of the mechanism and precise timelines.

Token Development: ERC-20, Tokenomics, Vesting

We’ve seen more rekt tokens than we can count — not because the code was broken, but because the economic assumptions were naive. A token that doesn’t collapse from inflation in six months, where governance actually works, and vesting can’t be bypassed through delegation tricks — that’s real engineering. We build under that standard.

How We Avoid Common ERC-20 Pitfalls

ERC-20 standard has nine functions. Complexity starts with extensions:

ERC-20Permit (EIP-2612) — gasless approve via signature. User signs permit(owner, spender, value, deadline, v, r, s) off-chain, spender calls permit() + transferFrom() in one transaction. Removes separate approve step. Risk: signature can be intercepted — need deadline and nonce checking. We always implement EIP-712 typed structured data to prevent signature malleability.

ERC-20Votes (EIP-5805) — snapshot balances for governance. Checkpoint system stores balance history by block number. getPastVotes(address, blockNumber) returns balance at proposal creation, not current. Prevents flash loan governance: can't borrow tokens and vote in one transaction.

Rebasing tokens (stETH, Ampleforth) — balanceOf changes automatically through internal shares ratio. High integration complexity: most DeFi protocols don't work correctly with rebasing without non-rebasing wrapper. We've deployed wrappers that decouple balance from share price for Uniswap compatibility.

Fee-on-transfer tokens — percentage cut on every transfer. Breaks AMM calculations: pool receives less than expected. Uniswap v2/v3 don't support natively — needs special pair/router. We’ve built custom routers that handle fee-on-transfer tokens without reverting.

Why Tokenomics Sustainability Matters More Than Excel

Tokenomics isn't Excel table summing to 100%. It's incentive model that either works long-term or creates selling pressure killing the project.

Emission Schedule and Inflation — Fixed supply (Bitcoin model) works for store-of-value, but for utility tokens you need controlled inflation. Inflationary model (like Ethereum post-Merge) generates new tokens to incentivize participants. Key balance: emission should be <= value captured by protocol. If protocol earns $100k/month but emission is $500k/month in market value — constant selling pressure inevitable. We model these scenarios using Python simulations with cadCAD for complex systems.

Supply Distribution — No universal formula. Principle: no single entity >33% voting power at launch. Otherwise governance is fiction.

Category Typical Range Risk
Team + advisors 15–20% Dumping on unlock
Investors (seed, private) 15–25% Coordinated exit
Treasury / DAO 20–35% Governance capture
Ecosystem / grants 10–20% Inefficient allocation
Public sale / LBP 5–15% Undervaluation → whale capture
Liquidity provision 5–10% Mercenary capital

What Are the Most Critical Vesting Contract Mistakes?

Linear vesting with cliff is standard for team and investors. cliff is the period after TGE with zero availability. After cliff: linear unlock until duration. Typical implementation errors we catch in audit:

  • Revocable vesting without timelock — owner can revoke immediately. Solution: revocation through multisig + governance vote with 7-day delay.
  • Cliff doesn't block governance rights — with ERC-20Votes, recipient can delegate voting power from day one even if tokens aren't unlocked. We explicitly separate voting power from claim logic.
  • No emergency pause — if vesting contract vulnerability discovered, need ability to pause claims. Pausable + timelock on unpause.

We’ve seen a project where the cliff was set to 0 by mistake — team could dump immediately. Our fuzz tests catch such edge cases before deployment.

Vesting contract implementation details

Pausable and Ownable2Step from OpenZeppelin are standard. We add a 7-day timelock on revocation functions. All withdraw functions emit events for off-chain tracking. Fuzz tests verify that cumulative released amount never exceeds total allocation, even after multiple revocations or partial claims.

Why Is Liquidity Bootstrapping Crucial for Token Launch?

Launch mechanics are critical. Three main approaches:

  • Balancer LBP — temporary pool with high initial token weight (90/10 project-token/USDC) that automatically decreases to 50/50 over days. Creates downward price pressure preventing bot buys at one price. After LBP liquidity moves to permanent pool.
  • Fjord Foundry — specialized platform for LBP and fair launches. Less operational overhead than direct Balancer integration.
  • Uniswap v3 with limited range — add liquidity in narrow range around initial price. High capital efficiency but requires active range management.
  • TWAMM — mechanics for gradual large-order sales without slippage. Implemented in FraxSwap.

LBP is 3-5x better than standard AMM listing for price discovery; we’ve seen fair launches with 50% less initial dump compared to direct Uniswap listings.

Governance Tokens and Voting Mechanics

OpenZeppelin Governor is the standard. Modular: GovernorVotes for counting, GovernorTimelockControl for timelock execution, GovernorSettings for adjustable parameters. Quorum is minimum percentage of supply for voting validity. Compound set quorum at 400k COMP (4% supply). We set quorum dynamically based on historical participation to avoid apathy or whale capture.

Flash loan governance attack — attacker borrows tokens via flash loan, delegates to self, creates proposal or votes, returns tokens. ERC-20Votes with block-based snapshot completely blocks this: must have tokens at snapshot creation moment, not voting moment.

Delegation — small holders often don't vote. Liquid delegation (like Optimism) lets delegate voting power to addresses without transfer. Critical for protocols with many passive holders.

Token Type Use Case Our Stack
ERC-20 utility Payments, rewards, gas Solidity 0.8.x, OpenZeppelin 5.x
ERC-20Permit Gasless approvals EIP-2612, EIP-712
ERC-20Votes On-chain governance Governor, TimelockController
ERC-1155 Multi-token (NFT + fungible) Solidity, OpenZeppelin
Vesting contracts Team/investor lockup LinearVesting, CliffVesting

Token Development Stack

Contracts: Solidity 0.8.x, OpenZeppelin Contracts 5.x (ERC20, ERC20Permit, ERC20Votes, Governor, TimelockController, TokenVesting).
Tokenomics audit: Python models with emission/demand simulation, cadCAD for complex systems modeling.
Deployment and management: Foundry scripts, Gnosis Safe for treasury, OpenZeppelin Defender for automation.
Analytics: Dune Analytics for on-chain metrics, Token Terminal for protocol revenue.

What’s Included in the Work (Deliverables)

  • Tokenomics model with stress tests (bear market, whale exit, governance capture)
  • Contract development with Foundry fuzz tests (gas optimization, reentrancy tests, overflow checks)
  • Audit summary and list of edge cases covered
  • Deployment scripts with Gnosis Safe admin keys
  • Documentation for future upgrades and maintenance
  • 30-day post-launch monitoring support

Process

  1. Tokenomics design — supply model, allocation, emission schedule, vesting. Stress-test scenarios.
  2. Contract development — ERC-20 + extensions, vesting, governance. Foundry fuzz tests on vesting calculations, governance thresholds.
  3. Audit — special attention on governance attack vectors, vesting bypass, permit replay attacks. We use Slither and Echidna for formal verification.
  4. LBP / launch — choose mechanics, set parameters, monitor first 24 hours.
  5. Post-launch — monitor supply distribution via Dune, governance participation metrics, treasury management.

Timelines

  • ERC-20 with permit and basic governance: 2–3 weeks
  • Vesting contract with revocation and cliff: 2–4 weeks
  • Full governance (Governor + Timelock + Token): 4–7 weeks
  • Token + LBP + governance + vesting: 8–14 weeks

We can estimate your project within 24 hours after discussing requirements. Contact us to start the conversation — no obligation, just a technical chat about your token model. Get a detailed proposal tailored to your tokenomics and compliance needs.