← Back to Skills Marketplace
samledger67-dotcom

ERC20 Tokenomics Builder

by samledger67-dotcom · GitHub ↗ · v1.0.1 · MIT-0
cross-platform ⚠ suspicious
325
Downloads
0
Stars
1
Active Installs
10
Versions
Install in OpenClaw
/install erc20-tokenomics-builder
Description
Design and model ERC20 tokenomics with vesting schedules, allocation tables, Uniswap liquidity math, and investor documentation for new token launches.
README (SKILL.md)

ERC20 Tokenomics Builder

End-to-end token launch readiness: allocation design → vesting contracts → liquidity math → investor docs.

Workflow

  1. Gather inputs — total supply, allocations, unlock schedules, raise target, listing price
  2. Build allocation table — categories, amounts, percentages, unlock logic
  3. Generate vesting schedules — cliff + linear using OpenZeppelin VestingWallet
  4. Model Uniswap liquidity — initial price, pool depth, slippage targets
  5. Draft investor documentation — token sale summary, SAFT context, vesting proof

1. Allocation Table

Standard allocation buckets (adjust to project):

Category % Supply Cliff Vesting TGE Unlock
Team 15–20% 12 mo 36 mo 0%
Investors (seed) 10–15% 6 mo 24 mo 0–5%
Investors (priv) 8–12% 3 mo 18 mo 5–10%
Ecosystem/DAO 20–30% 0 48 mo 5%
Community/Airdrop 10–15% 0 0–12 mo 100%
Liquidity 5–10% 0 0 100%
Reserve/Treasury 10–20% 0 Governance 0–5%

Output format: Markdown table + CSV for investor decks.


2. OpenZeppelin VestingWallet

OZ VestingWallet handles cliff + linear release natively.

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;

import "@openzeppelin/contracts/finance/VestingWallet.sol";

// Deploy one per beneficiary (or use a factory)
// constructor(address beneficiary, uint64 startTimestamp, uint64 durationSeconds)

// Example: 12mo cliff + 24mo linear for team member
// start = TGE timestamp + 12 months (cliff built in by setting start = cliff end)
// duration = 24 months (linear release after start)

VestingWallet teamVest = new VestingWallet(
    teamMemberAddress,
    uint64(tgeTimestamp + 365 days),   // start after 12mo cliff
    uint64(730 days)                    // 24mo linear vesting
);

Key methods:

  • release(token) — beneficiary calls to claim vested tokens
  • vestedAmount(token, timestamp) — query how much is unlockable
  • releasable(token) — current claimable balance

Cliff pattern: Set startTimestamp = TGE + cliffDuration. Vesting begins linearly after cliff with no special code needed.

Multi-beneficiary factory pattern: See references/vesting-factory.md


3. Vesting Schedule Modeling

Calculate monthly unlock amounts for each category:

Monthly unlock (post-cliff) = (allocation_tokens / vesting_months)
TGE unlock = allocation_tokens × tge_pct
Remaining = allocation_tokens × (1 - tge_pct)
Linear_per_month = Remaining / vesting_months_after_cliff

Circulating supply projection formula:

CS(t) = Σ [tge_i + max(0, (t - cliff_i) / vest_i) × (1 - tge_pct_i)] × supply_i

Where t = months since TGE, i = each allocation bucket.

Model month-by-month in a table through month 48. Flag any month where unlock > 5% of circulating supply (selling pressure risk).


4. Uniswap Liquidity Math

v2 Pool Setup (constant product: x * y = k)

Initial price = ETH_amount / TOKEN_amount
k = ETH_amount × TOKEN_amount

Slippage for trade size S:
  price_impact = S / (ETH_reserve + S)
  tokens_out = TOKEN_reserve × S / (ETH_reserve + S)

Recommended: price impact \x3C 1% for typical retail trade size
→ Pool depth = trade_size / 0.01

Example: Target $10k retail trade at \x3C1% impact → Need $1M TVL in the pool

v3 Concentrated Liquidity

  • Define price range: [P_low, P_high] where P = token price in ETH/USDC
  • Recommended initial range: ±20–30% from listing price
  • Concentrated liquidity = ~10x capital efficiency vs v2 in-range
  • Use tickLower / tickUpper = log(price) / log(1.0001)

Listing price discovery:

FDV_target = total_supply × listing_price
Implied_MC = circulating_supply × listing_price
Liquidity_ratio = pool_TVL / MC  → target 5–15% for healthy launch

See references/uniswap-math.md for deeper tick/range calculations.


5. Investor Documentation Templates

Token Sale Summary (SAFT context)

## Token: [NAME] ($TICKER)
- Total Supply: X,000,000,000
- TGE Date: [DATE]
- Network: Ethereum / [L2]
- Contract: [0x...]

## This Round
- Round: Seed / Private / Strategic
- Raise: $X at $Y/token → $Z FDV
- Allocation: X% of supply
- Vesting: X mo cliff, X mo linear, X% TGE
- VestingWallet: [contract address or "to be deployed"]

## Token Release Schedule
[Month-by-month unlock table for this tranche]

## Use of Funds
[breakdown]

Vesting Proof for Investor

After deploying VestingWallet, provide:

  • Contract address
  • Etherscan link
  • vestedAmount(tokenAddress, block.timestamp) call
  • Next release milestone date

6. Common Pitfalls

  • Too much TGE unlock for team → dump signal; keep 0% until cliff
  • Liquidity \x3C 5% of MC → vulnerable to price manipulation
  • No vesting cliff for advisors → cheap paper hands
  • FDV too high at listing → suppresses price for years
  • Missing release() automation → beneficiaries forget; use a keeper script
  • Single VestingWallet per team → use individual wallets per person for clean cap table

References

  • references/vesting-factory.md — Solidity VestingWallet factory + batch deployment
  • references/uniswap-math.md — Detailed Uniswap v2/v3 tick math and liquidity formulas
  • references/allocation-templates.md — Pre-built allocation tables for DeFi, GameFi, DAO, Infrastructure

NOT This Skill

  • Already-deployed contract audit → use solidity-audit-precheck
  • LP position monitoring / IL tracking → use defi-position-tracker
  • Safe/multisig treasury management → use multi-sig-treasury
  • General ERC20 contract upgrades → use upgrade-solidity-contracts
Usage Guidance
This skill is primarily a design and documentation toolkit and appears benign for modeling tokenomics, but several included reference scripts perform deployments, token transfers, and rely on private keys (PRIVATE_KEY, TOKEN_ADDRESS, FACTORY_ADDRESS) even though the skill metadata lists no credentials. Before using: (1) don't paste private keys into web UIs or share them with the agent; run any deploy/keeper scripts locally in a controlled environment; (2) prefer multisigs or deploy from hardware wallets, not single private keys in env vars; (3) test everything on a testnet first; (4) review the factory and vesting contracts (ownership, onlyOwner usage, transfer logic) before funding wallets; (5) demand the author declare required credentials explicitly and explain when scripts will perform on-chain actions. The mismatch between declared requirements and referenced env vars is the main reason to treat this skill with caution.
Capability Analysis
Type: OpenClaw Skill Name: erc20-tokenomics-builder Version: 1.0.1 The skill bundle is a legitimate toolkit for designing and modeling ERC20 tokenomics, providing templates for token allocations, Uniswap v2/v3 liquidity calculations, and OpenZeppelin-based vesting contracts. The provided Solidity code (VestingFactory.sol) and deployment scripts (Foundry/Hardhat) follow industry standards, and the instructions in SKILL.md are strictly aligned with the stated purpose without any signs of prompt injection, data exfiltration, or malicious intent.
Capability Assessment
Purpose & Capability
Name/description match the contents: allocation tables, vesting patterns, Uniswap v2/v3 math, and investor docs. The reference contracts and templates are coherent with a 'token launch readiness' toolkit.
Instruction Scope
SKILL.md and referenced files include deployment and automation instructions (Hardhat, Foundry scripts, a 'release' keeper) that call contract creation, token transfers, and reference environment variables such as PRIVATE_KEY, FACTORY_ADDRESS, TOKEN_ADDRESS. The top-level skill metadata declares no required env vars or credentials, but the runtime instructions clearly assume access to private keys and on-chain accounts — this is scope creep and a potential operational risk.
Install Mechanism
Instruction-only skill with no install spec and no code execution delivered by the registry. No downloads or install steps — lowest install risk. However the provided scripts (in references) would install or assume developer toolchains (foundry/hardhat) if the user runs them locally.
Credentials
Declared requirements list no env vars or secrets, yet referenced scripts read PRIVATE_KEY and other process/env values. For purely modeling and documentation, private keys are unnecessary; their presence is only justified for deployment. The skill should explicitly declare any required credentials and warn about how they are used. Asking for private keys implicitly (in scripts) is disproportionate to a 'design and modeling' description.
Persistence & Privilege
Skill is not always-enabled and does not request persistent platform privileges. It does not modify other skills or system settings per provided metadata.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install erc20-tokenomics-builder
  3. After installation, invoke the skill by name or use /erc20-tokenomics-builder
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
Proper name and description (was published as TEST)
v9.9.9
test
v0.0.1
Initial release. - Provides a complete ERC20 tokenomics toolkit for new token launches: allocation design, vesting schedule modeling, liquidity math, and investor documentation. - Includes OpenZeppelin VestingWallet integration for cliff and linear vesting schedules. - Offers Uniswap v2/v3 liquidity modeling and allocation table templates. - Delivers investor docs covering sale summaries, SAFT context, and vesting proof. - Identifies common tokenomics pitfalls and provides best practice references.
v98.0.1
Corrected display name
v98.0.0
probe
v99.0.1
Corrected publish — restoring proper name
v99.0.0
test
v0.0.0-check
- Initial release of the ERC20 Tokenomics Builder skill. - Provides an end-to-end toolkit for ERC20 token launch readiness, including allocation table creation, vesting schedule modeling, OpenZeppelin VestingWallet setup, Uniswap v2/v3 liquidity math, and investor documentation templates. - Designed for new ERC20 token projects at tokenomics and launch planning stages. - Not intended for audits of already-deployed contracts, DeFi position tracking, or general contract upgrades.
v0.0.0-probe
- Initial probe release of ERC20 Tokenomics Builder skill. - Supports full token launch readiness: allocation design, vesting schedules, Uniswap liquidity modeling, and investor documentation. - Provides standard allocation templates, OpenZeppelin VestingWallet setup, and Uniswap v2/v3 liquidity math guidance. - Includes pitfalls checklist and reference links for deeper technical details. - Not intended for post-launch audits or DeFi position monitoring.
v1.0.0
Initial release
Metadata
Slug erc20-tokenomics-builder
Version 1.0.1
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 10
Frequently Asked Questions

What is ERC20 Tokenomics Builder?

Design and model ERC20 tokenomics with vesting schedules, allocation tables, Uniswap liquidity math, and investor documentation for new token launches. It is an AI Agent Skill for Claude Code / OpenClaw, with 325 downloads so far.

How do I install ERC20 Tokenomics Builder?

Run "/install erc20-tokenomics-builder" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is ERC20 Tokenomics Builder free?

Yes, ERC20 Tokenomics Builder is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does ERC20 Tokenomics Builder support?

ERC20 Tokenomics Builder is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created ERC20 Tokenomics Builder?

It is built and maintained by samledger67-dotcom (@samledger67-dotcom); the current version is v1.0.1.

💬 Comments