uGit FAQ

uGit 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. The app already shows the core uGit surface, launch drafting, and builder previews; the broader repeatable launch system is still being built.

For a uGit-enabled pool, swaps are meant to route a configured share of fees through a funding hook to the builder treasury. That only applies to pools deployed with the uGit hook and treasury configuration. Builder-specific fee routing is upcoming until those real pools are live.

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 uGit 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.

Fees are intended to go to the configured builder treasury for that launched project. Each live builder token should show its treasury destination, fee revenue, and relevant contract addresses so users can inspect where funds move.

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. uGit 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, and treasury routing can contain bugs or mistakes. Fee revenue may be small or inconsistent, and public GitHub activity does not guarantee a project will ship. uGit is not a guarantee of returns.

The funding mechanism does not technically need GitHub to move fees. The uGit 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 uGit 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.