Berylpad, the Base network, the Beryl upgrade and the B20 token standard — explained.
Berylpad is a launchpad and explorer ("screener") for B20 tokens on Base. It discovers every B20, folds its on-chain policy-state from genesis, prices it against on-chain liquidity, and lets creators launch new B20 tokens.
Browsing and screening tokens is free. Launching a token and trading pay normal Base gas in ETH; the launchpad protocol fee is taken on-chain by the launch contracts, not by Berylpad off-chain.
No. Berylpad is non-custodial. You connect a wallet and sign every transaction yourself; token deploys and swaps are client-side. Berylpad never holds your keys or funds.
On-chain policy-state is a first-class column: allowlist/blocklist membership, frozen accounts, paused features (transfer/mint/burn), supply cap and rebase multiplier. Trust signals come from real on-chain state; the gem/rarity visual is decorative.
Base mainnet (chain id 8453). Base Sepolia (chain id 84532) is used for testing.
Yes — the launchpad contracts are public at github.com/BerylPad/v1-contracts (a fork of Clanker v4 adapted to the B20 standard). The web app is operated by the Berylpad team.
Base is an Ethereum Layer-2 network built on the OP Stack. Its mainnet chain id is 8453 and it uses ETH for gas.
Click Connect and approve in your wallet (WalletConnect or an injected wallet like MetaMask/Coinbase Wallet). During early access a private-beta password may be required before connecting or deploying.
ETH on Base. Launch, trade and airdrop-claim transactions all pay gas in ETH.
Beryl is the Base network upgrade (hardfork) that introduces the native B20 token standard at the protocol level, via precompiles — a token factory and a policy registry built into the chain.
The mainnet activation target was 2026-06-25 18:00 UTC. Berylpad indexes B20 activity from the Beryl genesis block forward.
It added the B20 precompiles: a factory that mints B20 tokens and a policy registry that enforces compliance and token controls in-protocol, rather than in deployed contract bytecode.
B20 is Base's native, protocol-level token standard introduced by the Beryl upgrade. Unlike a normal ERC-20 deployed as EVM bytecode, a B20 lives in a precompile and carries built-in policy-state: allowlist/blocklist, freeze, pause, supply cap, rebase and memo.
A B20 is enforced by the protocol (a precompile), not by contract bytecode, and ships native compliance controls. It exposes an ERC-20-compatible surface (balanceOf, transfer) while adding on-chain policy enforcement.
Policy-state is the compliance state folded from on-chain events: allowlist/blocklist membership, frozen accounts, paused features (TRANSFER/MINT/BURN), supply cap and rebase multiplier. Berylpad reconstructs it from genesis for every token.
On an allowlist token only listed accounts may transact (listed = allowed). On a blocklist token, listed accounts are denied (listed = denied). Authorization is the policy mode applied to membership.
A frozen account cannot move the token. Freezing is a compliance/admin action recorded on-chain; Berylpad surfaces it so you can see it before trading.
A B20 can pause specific features independently — TRANSFER, MINT or BURN. Paused TRANSFER means holders cannot move the token until it is unpaused.
A supply cap bounds total supply; rebase applies a multiplier to balances. On-chain balanceOf and totalSupply return RAW amounts — the rebase multiplier is a view-layer scaling, not a change to the underlying ledger.
If the token's policy grants those roles, an admin can freeze accounts or change compliance. Berylpad surfaces a token's roles and policy mode so you can judge how much control the creator retains before you trade.
Not enumerable: the policy registry only answers point queries (isAuthorized for a given account). Berylpad reconstructs full membership by event-sourcing allow/blocklist updates from the Beryl genesis block forward.
Open Launch (Forge), pick a template or a custom configuration — compliance mode, MEV protection, vault, airdrop and dev-buy — then deploy from your wallet. The configuration is permanent at deploy time.
Sign in and open My Tokens (shown when authenticated). Each token you created has a manage panel: rebase, update metadata (name/symbol/contract URI), pause/unpause TRANSFER/MINT/BURN, and grant/revoke roles — for as long as you hold the relevant admin role.
The launch configuration — supply, extensions (vault/airdrop/dev-buy), compliance mode and MEV settings — is permanent at deploy. If you hold the roles, you can still rebase, edit metadata, pause/unpause features and manage roles from My Tokens.
On a token's page, if your connected wallet has an allocation, a claim panel appears. Claiming is trustless — the contract verifies your merkle proof against the airdrop root committed on-chain.
Berylpad indexes Base on-chain events live (discovery, policy/membership fold, swaps, pricing). The figures shown are the latest indexed on-chain state, not a third-party price feed.
Yes. At launch you set an LP-fee reward split — recipient addresses and their shares (the default recipient is your wallet). As the token trades, LP fees accrue on-chain to those recipients via the launch's fee locker.
Open My Tokens, pick your token and use the Rewards tab to claim the LP fees that have accrued to your wallet from the on-chain fee locker. You can only claim rewards for addresses you control.
FDV (fully-diluted valuation) = price × total supply; market cap ≈ price × circulating supply. Both are derived from the token's live indexed price.
Liquidity shows “—” when on-chain pool liquidity for that token isn't available to the indexer yet. Price, volume, holders and policy-state are still shown from indexed on-chain state.
The Trust score is a breakdown of real on-chain signals, not market hype: admin renounced (rug-proof), capped supply, mint paused, holder distribution, organic holder base, and any frozen/allowlist policy. Risk flags call out paused transfers, whale concentration (top-10 ≥ 90%), or an active blocklist. It's the same score that drives the gem rarity, shown factor-by-factor.
The Roles panel on the token page folds RoleGranted/RoleRevoked events into the current holders of each role and flags “live powers” — addresses that can still mint (dilute), seize via burnBlocked (claw back) or pause transfers. “Admin renounced” comes from the on-chain LastAdminRenounced signal; once renounced, those powers can never return.