→ faq

GitHood FAQ

Plain answers about the protocol idea, the launch surface, fee routing, GitHub proof, support allocation, and which parts are live now versus upcoming.

live now

Public GitHood pages, the FAQ, launch drafting, and preview builder surfaces.

upcoming

Permissionless production launches, real hook-backed builder pools, and live fee dashboards.

verify

Every real launch should expose contracts, treasury destinations, repo links, fee flow, and support allocation.

01

live + upcoming

What is GitHood?

GitHood is a builder funding protocol and launch surface. Its Uniswap v4 hooks split a 4% funding fee: 3% to the builder treasury and 1% to the shared GitHood treasury for extra support. The broader repeatable launch system is still being built.

02

hook-based

How does every trade fund builders?

For a GitHood-enabled pool, the funding hook routes 3% of each exact-input trade to the builder treasury and 1% to the shared GitHood treasury. The split is enforced in the pool path and can be inspected on-chain.

03

upcoming

Can anyone launch a builder token?

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.

04

fair-launch template

Are there team allocations?

The GitHood 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.

05

transparent by design

Where do fees go?

The 4% funding fee is split on-chain: 3% goes to the launched project treasury and 1% goes to the shared GitHood treasury. Every live project should show fee revenue, support allocation, and the relevant contract addresses.

06

protocol primitive

What is a Uniswap v4 hook?

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. GitHood uses the hook concept to make funding behavior part of the pool mechanics instead of an off-chain promise.

07

important

What are the risks?

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. GitHood is not a guarantee of returns.

08

required for proof

Is the GitHub repo connection required?

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

09

roadmap clarity

What is live now and what is coming later?

Live now: the public GitHood 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.