7Block Labs
Blockchain

ByAUJay

Concise summary: A decision-maker’s, zero-fluff roadmap for Afreta Token—from ERC‑20 launch to Afreta mainnet—covering testnet gates, audit/bounty budgets, LBP parameters, liquidity bootstrapping on Uniswap/Balancer, governance and vesting communications, validator economics, and mainnet readiness SLOs with concrete dates, owners, and acceptance criteria grounded in 2024–2026 best practice.

Afreta Token Roadmap Breakdown: Key Milestones From Launch Date to Mainnet

Afreta is a practitioner-grade token design and program plan we use at 7Block Labs to ship production networks. Because public documentation for a real-world “Afreta” is sparse, we treat it as a realistic composite and tie every recommendation to what actually worked for leading protocols in 2024–2026. That lets you copy a concrete, auditable path from Token Generation Event (TGE) to mainnet without guesswork. (7blocklabs.com)

Below is a turnkey plan you can paste into your internal tracker. It assumes:

  • Token initially launches as ERC‑20 on Ethereum with EIP‑2612 permit and Permit2 support.
  • Liquidity is bootstrapped via a Balancer LBP plus canonical Uniswap v3 pools.
  • Testnets run in two public phases; mainnet genesis is a strict, SLO‑gated event.
  • Governance is minimized pre‑mainnet; security is layered via audits + bounty.

Where we cite, we link to the exact precedent or spec so your team can verify quickly.


Executive timeline (example dates you can shift ±2–4 weeks)

  • TGE (ERC‑20): April 21, 2026
  • Public Testnet Alpha: May 12, 2026
  • Public Testnet Beta (incentivized): July 6, 2026
  • Mainnet Candidate RC: September 7, 2026
  • Mainnet Genesis: September 30, 2026

Why this pacing works:

  • Two audit passes with fix review and a live bounty window fit cleanly.
  • LBP, Uniswap pool seeding, and bribe/incentive setup have room to settle.
  • Community and partners get vesting dashboards and unlock comms in place before high‑visibility milestones.

Security, testnet gating, and launch hygiene mirror what we’ve seen across recent mainnets and DeFi protocols that launched successfully in 2024–2025. (openzeppelin.com)


Phase 0 — Pre‑TGE hardening (now → April 20, 2026)

Security and token standards

  • Contracts: ERC‑20 with EIP‑2612 Permit and Uniswap Permit2 integration to reduce approval friction and unify UX across dapps. Acceptance: 100% unit/fuzz coverage for permit flows; replay‑protected signatures; no unlimited approvals required in dapps integrating Permit2. (eips.ethereum.org)
  • Codebase audit wave 1: book a top‑tier audit that includes architecture review, fuzzing, and fix‑review cycle; aim to lock scope 6–8 weeks pre‑TGE. Use auditors’ published process as the baseline for how you run pre‑audit readiness and fix review. (openzeppelin.com)
  • Bounty program: open an evergreen bug bounty before TGE; do not wait for mainnet. Benchmarks: Immunefi programs paying $100k–$1.5m for criticals are commonplace; set your critical payout floor at five figures and cap at 10% of funds at risk or a fixed max. (theblock.co)

Liquidity bootstrapping design

  • Primary sale: Balancer Liquidity Bootstrapping Pool (LBP) with time‑dependent weights; pair AFRE with a stable (DAI/USDC). Start at a deliberately high price; linearly shift from 90/10 (AFRE/stable) to 30/70 over 72–96 hours to achieve fair price discovery and capital efficiency. Use Balancer’s documented LBP settings and migration router to roll proceeds into a weighted or composable stable pool post‑sale. (docs.balancer.fi)
  • Secondary liquidity: Canonical Uniswap v3 pools at 0.3% (AFRE/WETH) and 0.05% (AFRE/stable). Configure liquidity mining with Uniswap v3 Staker and publish reward schedules up front. (docs.uniswap.org)
  • Deployment ops: Follow Uniswap DAO’s deployment guidance if requesting DAO‑recognized deployments or incentives/frontends like Oku; budget integration costs and timelines accordingly. (gov.uniswap.org)

Vesting transparency and comms

  • Publish a vesting dashboard with on‑chain schedules for team/investor/airdrop tranches, and a public unlock calendar. Do not cluster large unlocks shortly after TGE; the 2024 STRK unlock backlash is a case study in why gradual, clearly communicated unlocks matter. Acceptance: on‑chain schedule + public dashboard live before the LBP starts. (coindesk.com)
  • Consider linear monthly unlocks with smaller, more frequent events; pair with market‑making lines sized to cover expected unlock‑day flow.

Governance posture

  • Governance‑minimized pre‑mainnet: timelocked councils for budget/security/listings; tokenholders ratify high‑level parameters; all operational changes run behind a timelock and emergency pause reviewed by a Security Council.

Phase 1 — TGE day plan (April 21, 2026)

What ships, hour by hour

  • 09:00 UTC — Publish final token contract addresses, Merkle roots (if any), and LBP parameters; deploy Uniswap v3 pools; publish Etherscan‑verified source. Acceptance: addresses verified; pool init tx hashes posted; v3 Staker incentives queued for T+48h. (docs.uniswap.org)
  • 12:00 UTC — LBP opens with anti‑snipe configuration (trusted router + block project‑token swaps in); live price bands posted; Discord/Twitter comms with specific schedule and caps. (docs.balancer.fi)
  • 16:00 UTC — Risk window: market making goes live; circuit‑breaker thresholds published (spread, depth, and daily net flow), with escalation playbook to pause incentives but keep trading if needed.

Liquidity examples you can lift

  • LBP parameters: start 90/10 AFRE/DAI at $1.20 implied, end 30/70 at $0.60; min raise $2.5m; hard cap $10m; 96 hours; automatic 40% migration to 80/20 AFRE/DAI weighted pool at close. All parameters are supported in Balancer docs and tooling. (docs.balancer.fi)
  • Uniswap v3: seed $1m in AFRE/WETH at 0.3% and $1m in AFRE/USDC at 0.05%; concentrate initial ranges ±5% around LBP mid; begin a 90‑day, linearly declining reward schedule via v3 Staker. (docs.uniswap.org)

Security posture on TGE

  • Audit sign‑off: publish wave‑1 report + fix review link; open public bounty with clearly posted tiers and scope before LBP opens. Benchmarks indicate credible programs surpass $100m paid cumulatively; aim to be meaningfully competitive. (openzeppelin.com)

Phase 2 — First 60 days post‑TGE (April 22 → June 20, 2026)

Developer and ecosystem activation

  • Grants v0.1: small‑ticket, milestone‑based grants for ERP/TMS adapters, shipping/oracle bots, and data pipelines. Keep the program offchain with weekly triage; move to onchain votes post‑mainnet.
  • SDKs and standards: release TypeScript and Solidity kits that assume Permit2 and EIP‑2612; if you need multi‑asset internal accounting (credits, points, fee coupons), standardize on ERC‑6909 over ERC‑1155 for lower gas and simpler allowances. (eips.ethereum.org)

Liquidity and growth

  • Migrate a portion of LBP proceeds into a deep, sticky pool (Balancer or Uniswap v3 narrow bands) and formalize an incentives cadence. If you seek Uniswap DAO co‑incentives or canonicalization on new L2s, follow DAO process and timeline. (gov.uniswap.org)
  • Track pool health using Uniswap’s active liquidity metrics; expand or shift ranges weekly based on realized volume corridors. (docs.uniswap.org)

Security wave 2 and bounties

  • Code freeze for testnet Alpha; run audit wave‑2 and extend the bounty program to cover new modules (vesting, safety, router). Publish fix review diffs before Alpha opens. (openzeppelin.com)
  • Bug bounty budget: set a $250k–$1m ceiling for criticals, pegged to TVL at risk; align with Immunefi norms that pay a % of impact, with explicit floors and scope. (immunefi.com)

Phase 3 — Public testnets (Alpha → Beta)

Alpha (May 12 → June 14, 2026)

  • Scope: core settlement paths, oracle attestations, fee routing, vesting read‑only views, and governance timelocks.
  • Gates to pass:
    • Liveness ≥99.5% and time‑to‑finality under your target; median oracle lag under target.
    • No criticals open; bounty live with triage SLA ≤48h.
  • UX: ship Chainlist entries for testnet so wallets add networks in one click; publish RPC endpoints and chain IDs. Chainlist is the standard way most users add EVM networks today. (chainlist.app)

Beta, incentivized (July 6 → August 16, 2026)

  • Scope: stress rollups/bridges, safety module, ve‑style locks, incentive accounting, and council operations.
  • Precedent to learn from: recent mainnets pair launches with governance dashboards, cross‑chain bridges, and 50+ projects at go‑live; replicate this choreography to prime ecosystem momentum. (theblockbeats.info)

Phase 4 — Mainnet readiness review (August 18 → September 6, 2026)

SLOs (service level objectives) you must hit for 14 consecutive days

  • Liveness: 99.95% (no epoch halts; sequencer fallback tested if applicable).
  • Time to inclusion: ≤2 blocks median; ≤5 blocks p95.
  • Oracle median lag: ≤1s p50, ≤3s p95 on your target feeds.
  • Safety module: funded to target coverage; emissions and buybacks parameterized to phase down inflation and favor cash‑flow funded coverage, echoing what Aave iterated through in 2025. (governance.aave.com)
  • Governance: timelocks, emergency‑pause runbooks, and signer rotations documented; dry‑run emergency with postmortem.

Security checklist

  • All audits published with fix reviews; open issues severity ≤“medium” with documented compensating controls. Use the auditor’s documented process language to frame acceptance. (openzeppelin.com)
  • Bounty: criticals paid promptly; triage pipeline demonstrated; scope includes chain, bridges, vesting, DEX integrations. Benchmarks: programs on Immunefi for L1/L2 and blue‑chip DeFi regularly advertise six‑ to seven‑figure maxima. (theblock.co)

Liquidity and distribution hygiene

  • Pools: balanced depth across AFRE/USDC (0.05%) and AFRE/WETH (0.3%), and one Balancer pool for treasury diversification. If deploying Uniswap v3 to new L2s with DAO support, ensure canonical frontends like Oku are live or alternatives arranged. (gov.uniswap.org)
  • Unlocks: next 6‑month unlock calendar bannered; no “cliff bombs.” The Starknet episode is your cautionary tale—use gradual schedules and over‑communicate. (coindesk.com)

Phase 5 — Mainnet genesis (September 30, 2026)

What happens during the week of launch

  • Wallet and tooling: publish mainnet chain ID, RPCs, and explorers; submit to Chainlist so users can one‑click add the network in MetaMask and other wallets. (chainlist.app)
  • Bridge: bring up a production, audited bridge and/or partner with a proven provider; annotate routes and fees in docs. Example: recent L1s launched with governance dashboards and official bridges day‑one to reduce friction. (theblockbeats.info)
  • DEX strategy:
    • Keep Uniswap v3 pools on Ethereum as primary liquidity for the first 60–90 days to avoid fragmenting depth; add a mirrored pool on Afreta mainnet once wallets, explorers, and gas‑sponsor UX are stable.
    • If you want DAO‑recognized Uniswap deployments on new chains, follow the UAC process and timeline. (gov.uniswap.org)
  • Account abstraction: ship optional ERC‑4337 onboarding with a paymaster so enterprises can sponsor gas or let users pay fees in stablecoins. Publish EntryPoint, bundler, and paymaster addresses in docs. (eips.ethereum.org)
  • Governance turn‑up: seat Budget, Security/Risk, and Ecosystem councils; activate fee‑switches, emissions, and treasury policies via time‑locked proposals.

Run‑of‑day checklist

  • 08:00 UTC: soft‑open RPC gateways; observe CPU/mem/network for 2 hours.
  • 10:00 UTC: unpause sequencer/validators; enable bridge; announce Chainlist entry.
  • 12:00 UTC: open governance UI; publish the first three routine proposals (treasury spend cap, safety budget, emissions epoch 0) with 48h delay.
  • 16:00 UTC: liquidity checks; expand Uniswap v3 ranges as volume migrates.

Phase 6 — First 90 days post‑genesis (October → December 2026)

Stability and performance

  • SRE SLOs: maintain 99.95% liveness; p95 inclusion ≤5 blocks; post weekly SLO dashboards.
  • Incident practice: run two chaos exercises (sequencer halt; oracle stall); publish postmortems.

Security

  • Keep bounty running indefinitely; adjust tiers when TVL crosses thresholds. Compare your payouts to active, public programs so they remain attractive. (theblock.co)
  • Commission a post‑deployment “adversarial review” of the most‑used contracts after real traffic emerges.

Liquidity and listings

  • Incentives: taper emissions every epoch; favor revenue‑backed fee sharing over inflation, in line with 2025 governance shifts at major protocols. (governance.aave.com)
  • CEX engagement: share a clean “data room” (audit reports, bounty stats, unlock calendars, treasury policies, MM relationships, proof of reserves for team/treasury multisigs, council rosters and charters).

Token, liquidity, and governance details to copy as‑is

Standards and integrations

  • ERC‑20 + EIP‑2612 permit; Uniswap Permit2 for unified approvals. This slashes wallet pop‑ups and improves security, even for tokens without native permit support. (eips.ethereum.org)
  • If you need a multi‑asset internal ledger (credits/points/coupons), adopt ERC‑6909 for lower gas and granular allowances versus ERC‑1155. (eips.ethereum.org)
  • Optional ERC‑4337 onboarding with a paymaster allows stablecoin gas and sponsored transactions for enterprise pilots. (eips.ethereum.org)

Balancer LBP parameters (reference)

  • Duration: 96h
  • Weights: 90/10 → 30/70 (AFRE/stable)
  • Caps: min $2.5m; hard $10m
  • Router: LBPMigrationRouter; migrate 40% to an 80/20 weighted pool at close
  • Rationale: documented to produce fairer price discovery and lower capital needs up front. (docs.balancer.fi)

Uniswap pools and incentives

  • Canonical pools at TGE: AFRE/USDC 0.05%, AFRE/WETH 0.3%
  • Incentivization: Uniswap v3 Staker campaign with startTime/endTime posted onchain; publish pool addresses and ranges; share weekly “active liquidity” snapshots. (docs.uniswap.org)

Vesting transparency

  • On‑chain vesting + public dashboard with unlock calendars and beneficiary classes; avoid large, clustered unlocks within 60–120 days post‑TGE and communicate changes early—learn from STRK’s revised schedule. (coindesk.com)

Security program

  • Two audit waves with fix reviews, then continuous bounty. Public benchmarks show robust programs paying six‑ to seven‑figure bounties for criticals, which is the right order of magnitude if you’re serious about safety. (openzeppelin.com)

Emerging practices you should not skip in 2026

  • DAO‑recognized deployments and frontends: If you deploy Uniswap to new L2s or appchains, coordinate with the Uniswap Accountability Committee for canonicalization, incentives, and frontends (e.g., Oku). This shortens your path to real usage. (gov.uniswap.org)
  • Hooks era AMMs: Uniswap v4 went live in 2025 with hooks, and Balancer v3 shipped hooks and 100% boosted pools—use them for programmatic fee policies once your base liquidity is stable. (blog.uniswap.org)
  • Governance‑minimized risk budgets: Follow the arc major DAOs took in 2025—fewer inflationary emissions, more buybacks/fee redirection, and simpler safety modules with explicit coverage targets. (governance.aave.com)
  • One‑click network add: Ship Chainlist entries on day one (testnets and mainnet) to compress support load and improve wallet UX. (chainlist.app)

Why this roadmap is resilient

  • It borrows what worked: decentralized sequencing/mainnet choreography and day‑one governance tooling seen at recent L1 launches; price‑discovery sales that reduce bot games; DAO‑recognized DEX deployments to avoid liquidity dead ends. (astria.org)
  • It de‑risks public perception: vesting dashboards and gradual unlocks prevent “sell‑wall” narratives; this lesson was paid for in 2024—no reason to repeat it. (coindesk.com)
  • It treats security as a program, not a moment: audits with fix reviews plus ongoing bounties that match industry payout norms are what reduce tail risk, not a single PDF. (openzeppelin.com)

Owner’s checklist (copy/paste into your tracker)

  • T‑60d: freeze token contracts; pass audit wave‑1 and integrate Permit2. (github.com)
  • T‑45d: publish vesting dashboard and unlock calendar; open bounty. (coindesk.com)
  • T‑21d: announce LBP parameters; schedule Uniswap v3 pools and incentive windows. (docs.balancer.fi)
  • TGE day: LBP live; Uniswap pools live; audit + bounty links pinned; market‑maker standing instructions active.
  • T+7: migrate part of LBP to weighted pool; publish first liquidity and safety report with pool health and bounty stats. (docs.balancer.fi)
  • T+21: spin up Alpha testnet; publish Chainlist entry and RPC. (chainlist.app)
  • T+75: Beta testnet with incentives; publish SLO dashboards; pass all gates.
  • T+140: freeze for mainnet RC; publish mainnet docs, Chainlist entry, and governance proposal set; ship genesis.

Closing note

You can compress or extend dates, but keep the sequence: vesting transparency before fundraising, audits before TGE and again before mainnet, LBP then canonical Uniswap pools, Alpha then incentivized Beta, governance minimized until genesis, and SLO‑gated mainnet. Ship those, and you’ll launch Afreta the way top networks and protocols shipped in 2024–2026—measurable, defensible, and enterprise‑ready. (openzeppelin.com)


7Block Labs helps teams implement exactly this program; if you want this converted into a Gantt + risk register + comms calendar for your dates and jurisdictions, we can spin it up in a week.

Like what you're reading? Let's build together.

Get a free 30‑minute consultation with our engineering team.

Related Posts

7BlockLabs

Full-stack blockchain product studio: DeFi, dApps, audits, integrations.

7Block Labs is a trading name of JAYANTH TECHNOLOGIES LIMITED.

Registered in England and Wales (Company No. 16589283).

Registered Office address: Office 13536, 182-184 High Street North, East Ham, London, E6 2JA.

© 2025 7BlockLabs. All rights reserved.