tavern
Create

tavern docs

How tavern works.

Tavern launches fixed-supply ERC-20 coins into 1% Uniswap V3 pools on Robinhood Chain. The launcher locks each position NFT in TavernLocker before the transaction finishes.

Launch a coin View launcher
ProtocolLivemainnet
1B supply Locked V3 NFT 1% pool

Start here

Overview

Tavern is a non-custodial web app. Your wallet signs transactions. Tavern contracts create the markets and hold the position NFTs. A read-only Go service indexes confirmed chain events for listings, charts, holders, and history.

One launch transaction

The launcher deploys the coin, creates its WETH pool, mints the V3 position, transfers the NFT to TavernLocker, and can make the configured initial buy. If one step fails, the whole transaction reverts.

Trading after confirmation

The pool exists when the launch confirms. There is no later migration transaction.

Position NFT in TavernLocker

The locker has no function that transfers the position NFT back out.

Wallet-signed actions

The web app cannot launch, trade, bridge, or collect fees without a wallet signature.

For creators

Launch a coin

The coin stores its name, symbol, image URL, description, and social links in the constructor. There are no metadata setters. Names do not have to be unique, so the token address is the only reliable identifier.

  1. 01

    Enter token data

    The name is limited to 32 bytes. The symbol is 1 to 10 letters or digits. The description is limited to 500 bytes.

  2. 02

    Set the initial buy and rewards

    The initial buy is optional. Creator rewards can go to the creator, one fee wallet, or as many as 10 wallets whose shares total 100%.

  3. 03

    Review the wallet request

    The value is the 0.0005 ETH launch fee plus any initial buy. The app includes a minimum output and deadline when the initial buy is not zero.

Fixed supply1 billion coins
Launch fee0.0005 ETH
Initial buyOptional ETH amount
MarketCoin / WETH, 1% fee

Markets

Trade a market

The app asks the V3 quoter for the current pool output, then submits a minimum output and deadline with the trade. The quote can change before the transaction confirms. The deployed trade zap wraps ETH for buys, scopes sell approvals to one helper, and unwraps WETH after a sale.

Price
The current pool price for one coin.
Market cap
Current price multiplied by circulating supply.
FDV
Current price multiplied by the fixed total supply.
Price impact
How much your trade moves the pool price.
Slippage
The maximum quote movement your transaction will accept.
Launch protection

On the launch block, only the initial buy inside the launch transaction can buy from a pool. During the next two blocks, each wallet is limited to a 5% balance and 5.5% in cumulative pool buys. Sells and wallet transfers are not limited.

Before it enables trading, the app checks the indexed launcher against the deployed release. It also checks the token record from the launcher and the pool address from the coin.

Funding Robinhood Chain

Bridge funds

The bridge page gets its source networks and assets from Relay. The Tavern server asks Relay for an exact-input quote and rejects any response that does not deliver native ETH on Robinhood Chain to the address you chose.

  1. 01

    Choose the source

    Pick a network, asset, amount, and Robinhood Chain recipient. Available routes depend on Relay.

  2. 02

    Check the quote

    Review the expected ETH, route impact, estimated time, and recipient before signing.

  3. 03

    Execute on the source network

    Your connected wallet signs the Relay steps. A route can require an approval and one or more source-chain transactions.

The destination is fixed

Tavern only accepts bridge quotes whose output is native ETH on chain ID 4663. Relay executes the route and may use third-party bridges or exchanges.

Open bridge

Token economics

Supply, burns, and liquidity

Supply counts coins. Liquidity counts the coin and WETH represented by the locked V3 position at the current pool price. Sending coins to 0x...dEaD changes circulating supply but does not remove principal from the position.

Total supplyAll 1 billion minted coins
Burned supplyBalance at 0x…dEaD
Circulating supplyTotal minus burned
LiquidityLocked coin/WETH position
Burns do not withdraw liquidity

TavernLocker collects earned V3 fees without decreasing liquidity in the position. It sends the protocol share of coin fees to 0x...dEaD. The NFT stays in the locker.

Sending coins to the burn address lowers circulating supply but does not change the ERC-20 totalSupply() value. Burns do not guarantee a higher price, liquidity, or demand.

Milestone

Graduation

graduationStatus(token) calculates how much WETH principal the locked position represents at the current pool price. It returns graduated when that amount is at least 4.2 WETH.

SourceLive contract read
Threshold4.2 WETH principal
Pool after graduationSame V3 pool
Position after graduationStill locked

This is a live calculation, not a stored flag or a second transaction. The result can change with the pool price. It does not rate the coin or predict future demand.

For creators

Creator rewards

V3 charges swap fees in the input asset. Buys accrue WETH fees and sells accrue coin fees. Each market stores the protocol share that applied at launch. The current split pays 70% of each asset to creator recipients. The other 30% of WETH goes to the protocol fee wallet, and the other 30% of coin goes to the burn address.

70%Creator rewards
30%WETH treasury · coin burn

The creator, a listed reward recipient, an approved collector, or the locker owner can call collectFees. TavernLocker pays creator recipients in both assets. It sends protocol WETH to the fee wallet and protocol coin fees to 0x...dEaD. The protocol fee wallet receives no launched coin.

Technical reference

Network

Tavern is deployed on Robinhood Chain mainnet. Transactions use real ETH.

Network
Robinhood Chain
Chain ID
4663
Protocol release
Tavern V9
Native asset
ETH
Pool fee
1.00%
Token supply
1,000,000,000
Launch fee
0.0005 ETH

Technical reference

Contracts

These addresses come from the same generated mainnet manifest used by the web app and indexer. Check them before signing or integrating.

Under the hood

The launch transaction

1TavernLauncherChecks the fee, reward share, deadline, slippage, config, and pinned contract code.
2Executor and V3Runs pinned executor code, deploys TavernCoin with CREATE2, creates the pool, and mints the position.
3TavernLockerReceives the position NFT and stores the creator recipients and protocol share for that coin.

The launcher runs the deployed TavernLaunchExecutor with delegatecall. The executor rejects direct calls. The launcher pins the executor, locker, WETH, and Uniswap contract code hashes and checks them before every launch.

Canonical launch event
TokenLaunched(token, deployer, dexFactory, pairToken, pool, dexId, launchConfigId, positionId, restrictionsEndBlock, initialBuyAmount)

The launcher emits TokenLaunched after the NFT reaches TavernLocker and before an optional initial buy. ProtocolTokenFeesBurned records each protocol coin-fee burn. Contract state and confirmed chain events define the result.

After a launch confirms, a Privy-authenticated request asks the web server to publish the TavernCoin source on Blockscout. The server checks the runtime bytecode, coin deployer, launch factory, and launcher record before it submits the source bundle. A verification failure does not undo the launch.

Read path

Data and indexing

Market discovery, charts, holders, and wallet history come from a read-only Go service. It starts at block 24,342,979 and scans Robinhood Chain logs through the latest block with two confirmations.

1Robinhood Chain RPCReturns launcher, pool, locker, and coin events from confirmed blocks.
2Go indexerChecks launcher records, resolves metadata and senders, and updates a checkpointed snapshot.
3Read-only APIServes tokens, charts, holders, token history, and wallet history to the web app.

The indexer checks the saved block hash before each scan. A reorg, deployment change, or snapshot version change makes it rebuild from the deployment block. It only accepts a TokenLaunched event when the launcher returns the matching token record.

Transaction notifications do not write market data

After a confirmed launch, trade, or fee collection, the authenticated web route sends only the transaction hash to the service. That wakes the scanner. The scanner still reads the events from Robinhood Chain, and its one-minute scan remains the fallback.

The indexer can lag or be offline. The app rechecks the launcher record and pool address onchain before enabling a market for trading.

Common questions

FAQ

Does liquidity move after graduation?

No. The same Uniswap V3 pool and permanently locked position continue trading.

Can the creator withdraw the locked liquidity?

No. The position NFT is held permanently by the locker. Earned trading fees can only be distributed through the locker.

Does burning coins reduce liquidity?

No. Burned fees are separate from the locked LP principal. Burning reduces circulating supply; the permanent liquidity position remains locked.

Why does total supply stay at 1 billion?

Tavern sends burned coins to 0x…dEaD. They are removed from circulation, but the ERC-20 totalSupply() value remains fixed. The site reports total, burned, and circulating supply separately.

Does tavern hold my funds?

The web app does not hold your funds. Your wallet sends transactions to the contracts or, on the bridge page, executes a Relay route. TavernLocker holds the position NFT for every market by design.

Is graduation permanent?

No flag is stored. The launcher calculates the result from the locked position and current pool price each time the app reads it.

Is this available on mainnet?

Yes. The current website is configured for Robinhood Chain mainnet and transactions use real ETH.

Before you transact

Safety and risk

Review before confirming

Mainnet transactions use real assets and cannot be undone. Verify addresses, amounts, and approvals in your wallet before signing.

  • Names, symbols, links, and images are user-provided and can be copied. Verify the token address.
  • A quote is an estimate. The transaction uses its minimum output, not the number last shown on screen.
  • The indexer can lag behind the chain. Check the contract or explorer when timing matters.
  • Wallets, RPC providers, Relay routes, the indexer, and smart contracts can fail.
  • A confirmed blockchain transaction is usually irreversible.