Skip to documentation
BINK / DOCUMENTATION PROTOCOL V4

Bink protocol documentation

Launch it. Share it. Bink it.

Bink is a permissionless token launch protocol built on Robinhood Chain and Uniswap v4. It creates a standard ERC-20, initializes its market, permanently locks the launch liquidity, and applies a venue policy before the market becomes fully permissionless.

NetworkRobinhood Chain
MarketUniswap v4
TradingImmediate
Graduation5 ETH-equivalent
Launch fee0.001 ETH
LiquidityPermanently locked

Introduction

A new way to launch

Bink separates market infrastructure from launch policy. Liquidity and execution remain in Robinhood Chain’s official Uniswap v4 PoolManager; the Bink hook enforces the pre-graduation venue rule, accounts for fees, and records graduation.

Real v4 liquidity

The launch pool is a standard Uniswap v4 pool. Indexers and compatible interfaces can observe its liquidity, price, volume, and swaps.

Permanent by construction

The single-sided LP position is owned by BinkPoolDeployer, which deliberately has no liquidity-removal function.

Ordinary token behavior

Launched tokens have no transfer tax, blacklist, whitelist, pause control, owner mint, or sell restriction.

Immutable launch economics

The quote asset, creator tax, holder-reward rate, supply, launch model, and optional metadata binding are fixed per launch.

Open exits

Sells are permissionless from the beginning. The temporary venue policy applies only to buys into Bink’s launch pool.

No liquidity migration

Graduation changes who may buy; it does not move assets, replace the pool, or introduce a second market.

Introduction

Launch lifecycle

Every launch progresses through the same onchain sequence. Starting price and FDV affect the curve, but not the graduation target.

  1. 1

    Configure

    The creator selects identity, fixed supply, launch model, quote asset, starting price, creator tax, holder rewards, and optional metadata.

  2. 2

    Deploy atomically

    The factory deploys the token and reward vault, optionally deploys a vesting vault, initializes the v4 pool, installs locked liquidity, and registers the hook configuration.

  3. 3

    Trade immediately

    The market opens as soon as the launch transaction confirms. Approved execution venues may buy, and sells remain open.

  4. 4

    Graduate in place

    At five ETH-equivalents of net quote raised, the buy allowlist is removed. The same pool and locked position continue without migration.

Using Bink

Launch a token

The launch form prepares the entire market before requesting a transaction. A launch costs exactly 0.001 ETH plus gas; creators do not deposit quote assets or separately seed liquidity.

Before you begin

  • Connect an EVM wallet and select the configured Robinhood Chain network.
  • Choose a permanent token name, symbol, and fixed total supply.
  • Decide whether the launch is Fair or Builder.
  • Select WETH, USDG, or an approved Robinhood Stock Token as the quote and reward asset.
  • Review the starting price, immutable fees, and first-hour wallet limit before signing.

Fair and Builder launches

ModelMarket supplyCreator allocationVesting
FairAll supply, except unavoidable rounding dustNoneNot applicable
BuilderAt least 90% of supplyUp to 10%30-day cliff, then linear release over one year

The Builder allocation is deposited into a non-revocable BinkVestingVault during launch. The beneficiary may release vested tokens but cannot shorten, revoke, or reconfigure the schedule.

What becomes immutable

Token
Name, symbol, 18-decimal fixed supply, and ERC-2612 permit support.
Market
Quote asset, starting tick, 0.20% LP fee, curve, and permanently held position.
Economics
Creator tax and holder-reward rate, each independently selectable from 0% to 10%.
Distribution
Fair or Builder model and, when applicable, the allocation and vesting vault.
Metadata
The IPFS URI plus SHA-256 digests of the exact JSON and original image, when supplied.

Using Bink

Trading

Bink supports native-ETH routing for WETH markets, direct quote-token routing for every approved quote asset, and automatic ETH conversion for supported USDG or Stock Token routes. The interface requests a quote before submission and enforces the user’s minimum output.

Market phaseBuysSells
Pre-graduationBink or an allowlisted Relay solverPermissionless
Post-graduationAny compatible Uniswap v4 routerPermissionless

Allowance and permit behavior

New Bink tokens implement ERC-2612. A compatible wallet can sign a maximum router allowance off-chain and submit it atomically with the first sell, removing the separate approval transaction and the delay between approval and execution. Legacy tokens use a conventional maximum approval.

Price protection

Quotes are estimates at a specific state. The transaction’s minimum-output value is the onchain protection against price movement and route deterioration. A failed minimum-output check reverts the entire trade.

Using Bink

Creator tools

The creator dashboard is an operational view, not an administrative control plane. A creator can inspect their launch, vesting, accrued creator fees, holder-reward activity, graduation progress, and market links. They cannot change launch economics or withdraw the locked LP.

  • Creator fees: fees accrue in the immutable quote asset and are claimed from BinkHook.
  • Vested allocation: Builder beneficiaries release only the amount available under the fixed schedule.
  • Holder rewards: the dashboard exposes vault activity and pending distribution state.
  • Metadata: displayed from the immutable token URI and verified content hashes.

Open the creator dashboard

Protocol

Markets and liquidity

Bink represents its launch curve as a boundary-to-extreme, single-sided Uniswap v4 position. The position begins with token inventory and virtual quote reserves; real quote assets enter the pool through buys.

constant-product reserve modelx · y = kFor the configured one-sided curve, price rises approximately with 1 ÷ remaining-supply².

Permanent liquidity

BinkPoolDeployer creates and owns the position. It exposes pool creation and settlement logic but no withdrawal path. LP fees therefore remain associated with the locked position rather than becoming a creator-controlled balance.

Graduation accounting

Graduation uses net real quote raised. Starting virtual liquidity does not count, buys increase progress, and sells decrease it. WETH markets graduate at exactly 5 WETH; other markets use five times the quote asset’s snapshotted one-ETH equivalent.

Protocol

Fees

Trading fees are measured against executed quote value. The creator and holder components are independent, immutable launch settings.

ComponentRateAppliesDestination
Native v4 LP fee0.20%SwapsPermanently locked LP position
Bink infrastructure0.10%SwapsProtocol treasury
Creator tax0–10%SwapsLaunch creator
Holder rewards0–10%SwapsPer-launch reward vault
Originating venue0.15%Approved pre-graduation buysRecipient fixed to the approved executor

Ordinary all-in fees range from 0.30% to 20.30%. An approved pre-graduation buy adds the 0.15% venue fee, producing a maximum of 20.45%. The one-time 0.001 ETH launch fee is separate from trading fees.

Protocol

Holder rewards

Each launch receives its own BinkRewardVault. Rewards accrue in the same asset used to quote the market: WETH, USDG, or the selected Stock Token.

Per-share accounting

The vault uses O(1) cumulative accounting. Token transfers update holder checkpoints without taxing or rebasing the token.

Automatic delivery

Every Bink-routed stock trade attempts to pay four rotating holders. A permissionless sweep can process up to 64 holders.

Failure isolation

A recipient that cannot receive a restricted asset does not block trading or payouts to other eligible holders.

System accounts—including the factory, PoolManager, reward vault, and vesting vault—are excluded from holder rewards. Users do not sign reward claims or pay claim gas for the automatic path.

Protocol

Quote assets

The quote asset defines the market denomination, trade settlement asset, creator-fee asset, holder-reward asset, and graduation unit. It is selected once and cannot change for an existing launch.

KindTypical assetOperational notes
CryptoWETHNative ETH entry and exit through wrapping and unwrapping.
StableUSDGDollar-denominated market and rewards; ETH may route through available Uniswap liquidity.
StockApproved Robinhood Stock TokenStock-denominated market and rewards; availability can depend on issuer, jurisdiction, oracle, route liquidity, and wallet eligibility.

BinkQuoteRegistry controls which assets future launches may select. Every launch snapshots the asset’s decimals, kind, and standard one-ETH trade amount. A later registry update cannot change an existing pool or block its sells.

Protocol

Token and vesting model

Standard token surface

BinkToken is an 18-decimal fixed-supply ERC-20 with ERC-2612 permit and immutable metadata fields. It has no owner, mint function, blacklist, pause switch, or transfer tax.

First-hour wallet limit

For one hour after deployment, a non-exempt recipient cannot hold more than 2% of total supply. Protocol system addresses are exempt so pool initialization, rewards, and vesting can function. After the hour, ordinary transfers have no wallet cap.

Builder vesting

The optional allocation remains locked for 30 days. It then vests linearly over 365 days from launch. Released tokens become ordinary ERC-20 balances and remain subject to the same market conditions as every other token.

Protocol

Metadata

Metadata is optional. A launch without artwork remains fully functional. When artwork is supplied, Bink stores the original bytes and deterministic ERC-1046-style JSON in content-addressed storage, then binds three values to the token:

tokenURI
An immutable ipfs:// URI for the metadata document.
metadataHash
The SHA-256 digest of the exact JSON bytes.
imageHash
The SHA-256 digest of the exact uploaded artwork bytes.

Artwork requirements

  • PNG, JPG, WEBP, or GIF.
  • Maximum file size of 5 MB.
  • Each dimension from 256 to 2048 pixels.
  • Square artwork is recommended for consistent display.

The launch interface handles content-addressed storage and binds the resulting URI and hashes in the same launch transaction.

Developers

Architecture

The protocol is non-upgradeable and decomposed by responsibility. The hook does not custody the LP position, and the router does not own launch configuration.

Factory child contracts are deployed through the stateless BinkLaunchDeployer, keeping factory runtime code safely below EVM deployment limits without introducing an upgrade authority.

Developers

Networks and contracts

Robinhood Chain mainnet runs the reviewed v0.0.3 release, finalized at block 50,951,840. This table reads from the same public runtime configuration as the application; the complete release commit, child contracts, and runtime code hashes are recorded in the canonical deployment manifest.

Selected networkLoading…
Chain ID
Environment
ContractCurrent address
Uniswap v4 PoolManagerLoading…
WETHLoading…
USDGLoading…
BinkFactoryLoading…
BinkHookLoading…
BinkQuoteRegistryLoading…
BinkRouterLoading…
BinkLensLoading…

Developers

Reading protocol state

BinkLens.getBinkTokenState is the preferred aggregate read for a token page. It returns launch provenance, current v4 state, fee configuration, quote and reward assets, wallet limits, graduation state, and Builder vesting information.

TypeScript · viem
const state = await publicClient.readContract({
  address: lensAddress,
  abi: binkLensAbi,
  functionName: "getBinkTokenState",
  args: [tokenAddress],
});

console.log({
  poolId: state.poolId,
  quoteAsset: state.quoteAsset,
  netQuoteRaised: state.netQuoteRaised,
  graduationThreshold: state.graduationThresholdQuote,
  graduated: state.graduated,
});

Reconstructing the pool key

Currency ordering follows address order. Read the quote asset and tick spacing from BinkFactory, use the immutable 0.20% LP fee, and set the hook to BinkHook. Do not assume the launched token is always currency0.

PoolKey
PoolKey({
  currency0: min(token, quoteAsset),
  currency1: max(token, quoteAsset),
  fee: 2000,
  tickSpacing: factory.tickSpacingForToken(token),
  hooks: binkHook
})

Developers

Trading integration

Use BinkRouter when integrating Bink-native execution. It validates deadlines and minimum output, settles against PoolManager, handles native wrapping, and attempts bounded automatic reward delivery after trades.

IntentRouter entry pointInput
Quote a direct tradequoteBinkExactInputToken, direction, exact input
Buy a WETH marketbuyBinkExactInputNative ETH
Buy a token-quote marketbuyBinkExactInputTokenUSDG or approved Stock Token
Buy a token-quote market from ETHbuyBinkExactInputEthRoutedNative ETH routed through USDG liquidity
Sell to WETHsellBinkExactInputLaunched token
Sell to the quote tokensellBinkExactInputTokenLaunched token
Sell a token-quote market to ETHsellBinkExactInputEthRoutedLaunched token routed through USDG liquidity

Pre-graduation access

Trading starts immediately after launch. Before graduation, only Bink traders and Relay solvers loaded from Relay's current Robinhood Chain registry are allowlisted to buy. There is no timed opening, batch settlement, Bink signature, or authorization API.

Relay fills can route through different destination aggregators. Relay's entry contracts and downstream DEX routers are therefore not treated as proof that a transaction came from Relay.

Developers

Core events

ContractEventUse
BinkFactoryBinkTokenLaunchedLaunch discovery and immutable market configuration.
BinkFactoryBinkTokenMetadataBoundMetadata URI and content-hash provenance.
BinkFactoryBinkLaunchEnabledUpdatedPublic token creation opened or closed.
BinkFactoryBinkWhitelistedLauncherUpdatedLauncher access granted or revoked.
BinkHookBinkGraduationProgressNet quote raised relative to the fixed target.
BinkHookBinkPoolGraduatedPermanent removal of the pre-graduation buy allowlist.
BinkHookBinkFeesCollectedProtocol, creator, holder, and venue fee accounting.
BinkRouterBinkRoutedSwapBink-routed volume and trader activity.

Applications should discover launches from factory events and verify the factory’s one-based launchIndexPlusOne mapping. A token symbol or metadata document is not proof of Bink provenance.

Developers

Public runtime configuration

Network identity, the default public RPC endpoint, and deployed contract addresses are delivered through /api/runtime-config. Users may override the RPC for all browser-side onchain activity from Settings; the per-network preference stays in their browser.

FieldPurpose
chainId / chainNameWallet network identity
rpcUrlPublic RPC used by the application
poolManagerAddressOfficial Uniswap v4 singleton
factoryAddressBink launch factory
hookAddressLaunch-policy and fee hook
routerAddressPrimary Bink execution router
lensAddressAggregate read contract

Integrations should read the active configuration and verify bytecode rather than copying addresses from screenshots, cached pages, or examples.

Reference

Security model

Immutable contracts

Core contracts are non-upgradeable. Each launch snapshots its economic and quote configuration.

Locked liquidity

The LP owner contract exposes no removal function. Review deployed bytecode rather than relying on interface claims.

Direct venue enforcement

Before graduation, the hook accepts buys only when the contract calling PoolManager is approved onchain.

Venue attribution

The immediate PoolManager caller determines the approved venue and fixed fee recipient.

Open token transfers

The token avoids owner-controlled transfer restrictions. Holders can create independent secondary pools outside Bink’s launch liquidity.

External dependencies

Uniswap v4, quote-token behavior, Robinhood Chain, RPC providers, wallet software, IPFS gateways, and Stock Token restrictions remain external risks.

Reference

Contract directory

BinkFactory

Validates launch parameters, deploys launch components, initializes the market, installs liquidity, and records provenance.

BinkLaunchDeployer

Stateless child deployer used to keep the factory within EVM production code-size limits.

BinkToken

Fixed-supply ERC-20 with permit, the first-hour wallet limit, reward checkpoints, and optional metadata commitments.

BinkPoolDeployer

Creates and permanently owns each single-sided Uniswap v4 position.

BinkHook

Enforces launch-phase buy policy, accounts for fees, tracks net quote raised, and records graduation.

BinkRouter

Quotes and executes native, token-quote, and ETH-auto-routed exact-input trades.

BinkRewardVault

Accounts for holder rewards and pays bounded rotating batches in the launch quote asset.

BinkVestingVault

Holds the optional Builder allocation under its fixed cliff and linear release schedule.

BinkQuoteRegistry

Approves quote assets for future launches and records their kind, decimals, and one-ETH reference amount.

BinkLens

Aggregates factory, hook, token, quote, and live PoolManager state for applications.

BinkV2CurveCalculator

Derives tick boundaries, liquidity, and virtual reserve calibration for the one-sided curve.

Reference

Glossary

Launch price
Quote asset per launched token, independent of PoolManager currency ordering.
Graduation
The permanent transition from approved-venue buys to permissionless buys in the same pool.
Market supply
Total supply deposited into launch liquidity after subtracting an optional Builder allocation.
Net quote raised
Real quote value deposited through buys minus quote value removed through sells.
Partner executor
An approved contract that directly calls PoolManager for pre-graduation buys.
Quote asset
The asset paired with the launched token and used for pricing, fees, rewards, and graduation accounting.
Virtual reserves
Curve-calibration values that shape starting price without counting as real graduation liquidity.