Unipad FAQ

Unipad is a builder funding protocol and launch surface. It pairs fair-launch builder tokens with Uniswap v4 funding hooks so market activity can fund public builder treasuries, while the 3% UNIPAD fee backs extra support for the strongest Unipad-launched tokens. The broader repeatable launch system is still being built.

For a Unipad-enabled pool, swaps are meant to route a configured share of fees through a funding hook to the builder treasury. For the original UNIPAD pool, the 3% fee routes to the Unipad treasury first, then treasury support is used to reinforce top launches on Unipad.

That is the goal: a repeatable launchpad where builders can create a token, configure a funding hook, and publish a transparent profile. The production permissionless launch flow is not live yet. Real launches should appear only after their token, hook, treasury, and project details are ready to verify.

The Unipad builder launch template is designed around fair launches without hidden team allocations. If a future launch uses any reserved allocation, lockup, or special distribution, it should be disclosed clearly on that launch before users trade.

The UNIPAD 3% fee still goes to the Unipad treasury address. The stated use for that treasury flow is automatic extra support for the strongest tokens launched through Unipad. Builder-token fees go to each launched project treasury, and every live project should show fee revenue, support allocation, and relevant contract addresses.

A Uniswap v4 hook is a smart contract attached to a pool that can run custom logic around pool actions such as swaps or liquidity changes. Unipad uses the hook concept to make funding behavior part of the pool mechanics instead of an off-chain promise.

Builder tokens can be volatile and illiquid. Smart contracts, hooks, launch configuration, treasury routing, and support allocation can contain bugs or mistakes. Fee revenue may be small or inconsistent, and public GitHub activity does not guarantee a project will ship. Unipad is not a guarantee of returns.

The funding mechanism does not technically need GitHub to move fees. The Unipad product uses GitHub data as public proof of builder activity, so the live launch directory is expected to require a connected public repo before a project is presented as a verified builder launch.

Live now: the public Unipad site, launch drafting surface, builder directory structure, and preview builder profile. Coming later: production builder token launches, automated hook and pool deployment, verified fee dashboards for real launches, and GitHub-backed activity views for live builder projects.