Hookworks
BNB SMART CHAIN / UNISWAP V4

HOOKWORKS / BNB CHAIN / 56

Build with the real network.

The verified Uniswap v4 foundation, our custom fee-aware hook, supported routes and the exact conditions for production launches.

BNB mainnet: contract launch is not enabled

Hookworks V3 Solidity, local tests and the BNB-targeted frontend are available for review, but the BNB V3 factory/launcher, hook, fee vault, router and Auto Balance policy have not been deployed, independently audited or verified together on BNB mainnet. The launch button remains disabled unless a BNB-specific deployment passes bytecode and immutable-address checks. A working website is not proof of working production contracts.

Quick start

Connect an EVM wallet on BNB Smart Chain (chain ID 56), then open the BNB studio. BNB is the native gas token. Hookworks routes its contract swaps through WBNB, the ERC-20 wrapped BNB contract. The current V3 contract requires two to eight supported quote assets and the first suggested configuration is WBNB plus USDT.

  1. Set the new token name, ticker and fixed supply.
  2. Choose quote assets from the live-validated BNB catalog, allocate supply weights totaling 100%, and set starting prices.
  3. Choose Fixed Split (default) or configure verified external feeds before enabling Auto Balance. Choose any creator fee from 0% to 4% on top of the mandatory 1% base.
  4. Inspect the exact pool routing, immutable economics and wallet simulation. Launch only after mainnet contracts are independently approved and configured.

Our custom Uniswap v4 hook

Every newly launched token has multiple independent Uniswap v4 pools governed by a custom hook. The gateway routes WBNB through weighted quote markets. The hook controls pool initialization, liquidity changes and fees, and prevents direct swaps from bypassing the launcher’s policy. The contracts are built for the official BNB Uniswap v4 PoolManager. The same contract source is not a PancakeSwap Infinity hook: those deployments and interfaces are different.

Economics enforced by the V3 contracts

  • Normal buy and sell: mandatory 1% base fee; 70% is allocated to the Hookworks treasury and 30% to the launch creator.
  • Each creator may add 0–4% of their own tax at token creation, paid entirely to that creator, with a normal all-in hook tax of 1–5%.
  • For the first 180 seconds after launch, the base fee on buys falls linearly from 50% to 1%. That declining base is split 70% to Hookworks and 30% to the creator. Creator extra is suppressed during this interval.
  • Sells during the opening window have the normal 1% base plus the creator's selected extra.
  • Uniswap v4 LP fees and any converter fee are additional to the hook tax. Beneficiaries claim their accrued share through the WBNB fee vault.

The V3 contracts implement these accounting rules, but no BNB fee revenue has been established until the contracts are actually deployed and used onchain.

One token, independent one-sided markets

A launch creates one fixed-supply token and two to eight independent token/quote pools. Only the new tokens seed the opening positions; the creator does not need the paired crypto or stablecoins to initialize them. Buyers later bring quote assets. There is no shared backing reserve and a Hookworks token is not a redeemable index or a claim on companies, ETFs, or their underlying assets.

Creators own their liquidity positions and may withdraw them. Positions are not automatically locked. Removing positions can make the weighted gateway unable to trade. Successful launch transactions and fresh pool identities do not guarantee future liquidity or a buyer.

Prices, weights and slippage

Opening price is expressed in units of each quote asset per one million new tokens, not in USD. Weights distribute the new token supply. In Fixed Split they also determine every subsequent gateway trade's WBNB allocation. Auto Balance uses independently priced reserves to favor underweight markets. A full trade reverts if a required leg, converter, oracle or minimum output fails.

Which BNB markets actually route?

The current launcher requires a hookless, initialized Uniswap v4 WBNB/asset converter with active liquidity. The catalog queries BNB PoolManager state and simulates small and larger input quotes before enabling each market. It blocks a route if a test WBNB input shows over 5% relative price impact, but a passing sample cannot guarantee an individual transaction's execution quality.

At the last direct onchain check on October 27, 2026, WBNB / USDT (500 fee, tick 10) was executable at the tested sizes. WBNB / USDC (500/10) was executable but failed the deeper-size price-impact criterion. This is a time-sensitive snapshot; the live catalog makes its own fresh determination.

Popular pairs need compatible conversion

BTCB, ETH, CAKE, USD1, and the sampled AAPL, NVDA and SPY tokenized securities did not have a qualifying hookless Uniswap v4 WBNB converter at the tested fee/tick configurations. Some trade elsewhere on BNB, particularly on PancakeSwap. Supporting them in the Hookworks gateway requires a funded compatible v4 converter or an audited cross-DEX adapter with slippage and transfer-safety protections. Custom manual addresses do not bypass these rules.

Auto Balance and oracle safety

Auto Balance is implemented in V3 Solidity and tested locally, but is off by default on the BNB studio until independent BNB/USD and asset/USD feed addresses, decimals, freshness and market-hours behavior are verified. It does not autonomously move a creator's LP positions: a separate permission with bounded price loss, turnover and cooldown is required. Fixed Split avoids unverified price-feed assumptions.

Tokenized equities and eligibility

BNB hosts Ondo, xStocks and bStocks tokens, generally routed through PancakeSwap or their issuer platforms. They are research-only in Hookworks. Token identity and market existence do not establish unrestricted transferability, collateral rights, or permission to market or sell securities. Geographic restrictions, including U.S.-person restrictions for some issuers, must be checked before enabling equity-token markets.

Wallets and networks

Use an EVM wallet configured for BNB Smart Chain ID 56, with BNB for transaction gas. The wallet flow prompts network switching. Every V3 launcher connection checks deployed bytecode, PoolManager, wrapped BNB, fee vault and creator fee recipients. Addresses stored for Robinhood Chain or earlier Hookworks beta versions are not accepted as BNB V3 deployments.

If a market or launch is unavailable

  • Market disabled: the BNB RPC or live v4 converter quote failed a liquidity, identity or price-impact check. Wait, refresh and inspect the selected venue; do not assume a PancakeSwap route is usable.
  • Launch disabled: the BNB V3 contracts have not been verified and configured; review V3 setup.
  • Auto Balance rejected: supply only independently confirmed, current BNB/USD and token/USD oracles with suitable bounds.
  • Wrong chain: switch your wallet to BNB Smart Chain 56. This does not migrate assets from Robinhood.

Official deployments and research

Uniswap v4 official deployment list · BNB mainnet network settings · PancakeSwap tokenized-stock availability.

BNB Uniswap v4 PoolManager: 0x28e2ea090877bf75740558f6bfb36a5ffee9e9df. WBNB: 0xbb4cdb9cbd36b01bd1cbaebf2de08d9173bc095c. Fee vault, hook and launcher: not yet deployed on BNB mainnet.