GitHood

The first-ever GitHub Repo Launchpad. Fair-launch tokens for verified GitHub builders. Every trade funds the maintainer & $GHOOD. Built on Robinhood Chain.

[GitHood @GitHoodapp]

Introducing GitHood - the first GitHub-native launchpad purpose-built from the ground up for Robinhood Chain.

CA: 0xa08c0c768661c66d282e149ce0f77f4f5bcf119a

GitHood connects real development, community ownership, and on-chain funding.

Builders connect through our tested GitHub App, verify their repositories, and launch tokens tied directly to real projects and public work. GitHood provides the complete on-chain infrastructure for attestations, fair bonding-curve launches, automated funding, and transparent graduation.

Instead of launching around anonymous promises, GitHood starts with something verifiable: shipped code.

Communities can discover builders earlier, support the projects they believe in, and follow their progress directly through GitHub. Builders gain a new way to fund development while continuing to build in public.

The protocol is live.
The GitHub App is ready for all users.

Website: https://t.co/TBIoFXrd9q
GitHub App: https://t.co/wx7l5A3AuD

[GitHood @GitHoodapp]

The first GitHood Launchpad competition is coming soon. 🏆

$500 grand prize.

We’re starting by rewarding the builders who move first - the early creators launching tokens for their GitHub repos through GitHood Launchpad.

Your repo. Your token. Your launch.

Full details soon.

[GitHood @GitHoodapp]

GitHood's optional launch curve is a virtual-reserve constant-product market rather than an order book.

Each token receives `virtualEth` and `virtualTokens`, which shape its starting price without pretending those virtual reserves are withdrawable assets.

At any moment, the pricing invariant uses `k = (virtualEth + ethCollected) * (virtualTokens - tokensSold)`. For a buy, the contract adds the incoming ETH to the effective ETH reserve and solves for the new token reserve. The difference between the old and new token reserve becomes `tokensOut`. The calculation uses `Math.ceilDiv` for the new token reserve, rounding against over-distributing tokens when integer division cannot represent the exact curve.

For a sell, returned tokens increase the effective token reserve and the contract solves for the lower ETH reserve. The ETH difference becomes `ethOut`, but it can never exceed the real `ethCollected` balance. `minTokensOut` and `minEthOut` protect both paths from slippage between quoting and execution. `tokensSold` cannot exceed `curveSupplyCap`, and selling more than the outstanding sold amount is rejected.

All state updates happen before external transfers, while `nonReentrant` protects the ETH and token movement. When real collected ETH reaches `graduationEthTarget`, the curve stops being only a pricing function and begins the transition into permanent Uniswap v4 liquidity.

[GitHood @GitHoodapp]

On GitHood, connecting GitHub to a wallet is not a single login step; it is a bridge between two unrelated trust systems.

GitHood starts with a GitHub App installation because repository access must come from permissions that GitHub can actually verify. The `installation_id` returned by GitHub is still treated as untrusted browser input, because knowing an installation number does not prove control over it. GitHood binds that value to a pending server-side flow, creates OAuth `state` and PKCE values, and encrypts the verifier before persistence.

After the OAuth callback, the server checks the state, exchanges the one-time code, and asks GitHub which account authenticated. It then verifies that the user can access the pending installation. For a personal installation, the authenticated user ID must match the installation owner ID. For an organization, GitHood requires an administrator role rather than accepting ordinary membership.

The temporary GitHub user token is discarded after this proof, and the browser receives only a random `Secure`, `HttpOnly`, `SameSite=Lax` session cookie. Repository listing and verification are scoped to the same installation, so a valid session cannot silently reach unrelated repositories.

The wallet is connected only after this GitHub-side authorization is complete, using a separate signed challenge rather than treating OAuth as wallet proof.

The result is an explicit trust bridge: GitHub proves repository authority, the wallet proves key control, and GitHood links the two without trusting a URL parameter as identity.

[GitHood @GitHoodapp]

GitHub usernames change, but numeric GitHub user IDs remain stable. GitHood uses that distinction to turn a verified GitHub account into an on-chain builder identity without storing a mutable username in the contract.

The flow begins with a GitHub App installation, and the `installation_id` returned to the browser is treated as untrusted input. The server binds it to an OAuth flow, validates state and PKCE, and confirms that the authenticated user owns the installation or is an administrator of its organization.

Once authenticated, GitHood creates a five-minute wallet challenge containing `https://t.co/TBIoFXrd9q`, Robinhood Chain ID `4663`, the normalized wallet, GitHub user and installation IDs, the installation owner, a nonce, and timestamps. The server reconstructs this canonical message before recovering the signer instead of trusting arbitrary message text supplied by the browser. The nonce is stored only as a hash and consumed atomically, preventing the same challenge from authorizing another attestation.

After signature verification, GitHood derives the onchain key as `keccak256("githood.attestation.v1:github:" + numericUserId)`. The prefix domain-separates GitHood’s identity namespace, while the numeric ID keeps the binding stable across username changes. This hash is not encryption: numeric account IDs have a searchable input space, so it should be understood as a pseudonymous identifier rather than a privacy guarantee.

GitBondAttestation then enforces one active wallet per GitHub hash and one active GitHub hash per wallet, while restricting writes and revocations to an authorized attestor. When a builder launches a token, BuilderTokenLauncher checks isAttested(creator) and links the deployed token back to that identity, creating verifiable provenance from GitHub account to wallet to builder token.

[GitHood @GitHoodapp]

GitHood Roadmap v1.0 - Next 2 Weeks

The launch was only the beginning. Over the next two weeks, we’re expanding GitHood with new features while improving the core experience across the entire platform.

WEEK 1 — Better tracking, transparency & usability

→ Portfolio dashboard
View your builder-token positions, recent activity and projects you support from one dashboard.

→ Watchlists
Save tokens and builders you want to follow without needing to hold their tokens.

→ Token Pages v2
Clearer market information, project details, GitHub activity and treasury data on every token page.

→ Advanced market charts
Improved price charts, volume history, liquidity data and selectable timeframes.

→ Builder roadmaps
Builders can publish upcoming goals, development priorities and planned releases directly on their profiles.

→ Project update posts
Teams can share product updates, completed milestones and important announcements with their communities.

→ GitHub activity timeline
Follow commits, releases and repository activity alongside each project’s market data.

→ Treasury transparency upgrades
Clearer treasury balances, fee inflows, allocations, spending updates and transaction links.

→ Builder Profile v2
Improved project descriptions, team links, milestones, contracts and key ecosystem information.

→ Launch flow improvements
A clearer step-by-step launch experience with better previews, explanations and transaction status updates.

→ Shareable project cards
Generate clean cards for builder profiles, token pages and milestones that can be shared across social platforms.

→ Improved mobile experience
Faster navigation, cleaner layouts and easier trading, tracking and discovery on mobile devices.

→ Performance upgrades
Faster page loads, improved data refreshes and a smoother experience across the platform.

WEEK 2 — Smarter discovery, community & notifications

→ Live ecosystem activity feed
Follow new launches, builder updates, GitHub activity, milestones and treasury events as they happen.

→ Leaderboard v2
New rankings based on shipping activity, market activity, treasury growth and community momentum.

→ Advanced leaderboard filters
Filter projects by category, activity, launch date, token performance and development progress.

→ Trending builders & tokens
Discover projects gaining attention through real ecosystem activity.

→ Personalized alerts
Receive notifications for price movements, new launches, roadmap updates and milestones.

→ Follow builders
Follow specific projects and receive their latest updates in one personalized feed.

→ Smarter ecosystem search
Find builders, tokens, repositories and wallet addresses faster from one search experience.

→ Project categories & tags
Explore projects by ecosystem, product type, development stage and builder focus.

→ Verified builder signals
Clearer indicators for connected GitHub accounts, verified repositories, contracts and public project information.

→ Community reactions
Support and react to builder updates, milestones and roadmap announcements.

→ Project comparison
Compare selected builders across market activity, GitHub progress, treasury data and milestones.

→ Recently updated section
Quickly find projects that have shipped new releases, published updates or completed roadmap goals.

→ Ecosystem analytics
Track platform-wide launches, active builders, treasury flows and development activity.

→ Weekly GitHood recap
A simple summary highlighting new launches, active builders, completed milestones and major ecosystem updates.

→ Better sharing tools
Share tokens, builder profiles, rankings and updates directly to X with automatically formatted posts.

This is a living roadmap. We’ll continue adding new features, platform improvements and community-requested updates as development progresses.

More items will be added to the roadmap throughout the next two weeks.

The launch was only step one. Now we build GitHood together.

[GitHood @GitHoodapp]

What makes GitHood different from a traditional launchpad on Robinhood Chain?

Most launchpads start with a token.

GitHood starts with something real: a GitHub project.

Before launching, the builder connects their GitHub account, verifies the repository and links it to their wallet. This gives every GitHood launch a visible project, an identifiable builder and a public development history behind it.

But the difference does not end at verification.

GitHood is designed to fund continued development. Every trade routes 3% directly to the project’s builder, while the 1% GitHood protocol fee flows entirely back to the $GHOOD ecosystem.

When the project reaches its funding target, liquidity is automatically moved to Uniswap for open trading.

Traditional launchpads help people create tokens.

GitHood helps verified builders turn real projects into onchain communities, access continuous funding and keep building after the launch.

A token is easy to create.

A real project is harder to build.

GitHood is built for the builders.

[GitHood @GitHoodapp]

How does a GitHub project become an on-chain project?

The code never leaves GitHub.

First, the developer connects GitHood and verifies that they own or maintain the project. Their GitHub identity, repository, and wallet are then securely linked.

The developer can now launch a token for the project on Robinhood Chain.

People can discover the project, follow its progress, and trade its token. Every trade helps fund the ecosystem: 3% goes directly to the project’s builder, while GitHood’s 1% protocol fee flows entirely back to the $GHOOD ecosystem.

When the project reaches its funding target, its liquidity is automatically moved to Uniswap for open trading.

The result is simple:

A real GitHub project becomes a verified on-chain community with its own token, public liquidity, and continuous funding for development.

[GitHood @GitHoodapp]

GitHood explained in plain English, for everyone, not just developers.

GitHood helps developers turn real GitHub projects into on-chain communities.

A developer connects their GitHub account, verifies their project, and launches a token for it on Robinhood Chain.

People can then discover the project, trade its token, and support the builder from an early stage.

Every trade includes two simple fees:

3% goes directly to the project’s builder, creating continuous funding for development.

1% is the GitHood protocol fee. 100% of it is directed back to the $GHOOD ecosystem to support the token and its community.

When a project reaches its funding target, liquidity is automatically moved to Uniswap for open trading.

In simple terms:

Real GitHub project.
Verified developer.
Fair token launch.
Automatic liquidity.
Continuous funding for builders.
100% of GitHood’s protocol fees flow back to $GHOOD.

[GitHood @GitHoodapp]

GitHood is also available in Chinese! All Chinese-speaking users can now enjoy the full GitHood experience in their own language.

GitHood 现已支持中文！所有中文用户现在都可以使用自己的语言，畅享完整的 GitHood 体验。

[GitHood @GitHoodapp]

How does GitHood actually work?

GitHood turns a verified GitHub builder and their project into an on-chain token economy on Robinhood Chain.

Here is the complete process from start to finish:

1. Install the GitHood GitHub App

The builder installs GitHood on a personal GitHub account or organization and chooses which repositories the App can access.

GitHood uses read-only permissions. It cannot edit code, push commits or modify repositories.

2. Prove control of the GitHub account

GitHood verifies that the user controls the selected installation.

For personal accounts, the authenticated GitHub user must own the installation. For organizations, the user must have the required administrator role.

Temporary authorization credentials are discarded after verification and are not stored as permanent user access tokens.

3. Connect and verify a wallet

The builder connects a wallet on Robinhood Chain and signs a short-lived verification message.

The message is bound to:

• https://t.co/TBIoFXrd9q
• Robinhood Chain ID 4663
• The connected wallet
• The verified GitHub installation
• A one-time nonce
• A short expiration time

This prevents another person from copying or replaying the verification.

4. Create an on-chain builder identity

GitHood hashes the verified GitHub account ID and binds it to the wallet through the GitHood Attestation contract.

The blockchain receives the hashed identity, not the builder’s GitHub password, OAuth token or private account information.

Once the wallet is verified, the builder does not need to repeat the entire GitHub installation process for every launch.

5. Select and check the project

The builder selects one of the repositories available through the GitHood App.

GitHood checks access to the repository and adds the project link to the launch metadata. This creates a visible connection between the token, its builder and the code being developed.

6. Configure the token

The builder chooses the token’s:

• Name and symbol
• Builder treasury
• Bonding-curve supply
• Graduation liquidity allocation
• Virtual reserves and starting price
• Graduation ETH target
• Post-graduation funding fee
• Repository and project metadata

The builder can start the launch without providing initial ETH liquidity.

7. Launch the token

The verified builder signs one Robinhood Chain transaction.

GitHood then:

• Deploys a fixed-supply ERC-20 token
• Creates the token’s bonding curve
• Records its creator and treasury
• Stores its launch configuration
• Links it to the builder’s verified GitHub identity

An unverified wallet cannot use the launcher contract.

8. Begin bonding-curve trading

Community members can buy and sell the token through its constant-product bonding curve.

The price changes according to the virtual reserves, collected ETH and tokens sold. Transactions include minimum-output protection so users can control their acceptable slippage.

The builder does not manually select buyers or distribute early positions.

9. Reach the graduation target

Each launch has a transparent ETH target.

When the curve reaches that target, the curve closes and the token graduates. The collected ETH and the tokens reserved for liquidity move into the GitHood graduation system.

Tokens already purchased remain in their holders’ wallets.

10. Create the Uniswap v4 market

GitHood registers the token’s ETH pool with its funding hook, initializes the market price and uses the collected ETH and reserved tokens to create liquidity on Uniswap v4.

The process verifies that the pool was initialized correctly and contains liquidity before graduation is marked as complete.

If finalization fails, the assets remain secured and the process can be retried instead of leaving a partially created market.

11. Activate continuous builder funding

After graduation, trading moves from the bonding curve to the token’s Uniswap v4 pool.

By default, GitHood’s hook routes:

• 3% to the project’s builder treasury
• 1% to the $GHOOD system treasury

The Uniswap v4 pool also charges its separate 1% pool fee. These fees apply at different stages of a swap rather than as one guaranteed flat deduction.

The routed fees are recorded transparently on-chain.

12. Continue building

The builder now has a permanent token market connected to:

• A verified GitHub identity
• A selected project repository
• A Robinhood Chain token contract
• A transparent launch history
• Uniswap v4 liquidity
• An automated builder treasury

Trading activity can continue funding the project after the initial launch is complete.

GitHood creates a complete path from shipped code to onchain discovery, liquidity and continuous funding.

GitHub verifies the builder.
Robinhood Chain records the launch.
The bonding curve forms the market.
Uniswap v4 provides long-term liquidity.
Trading helps fund continued development.

[GitHood @GitHoodapp]

GitHood’s public GitHub App is officially ready - tested, working, and available to every GitHub user.

The app lets builders securely connect their GitHub account and repositories to GitHood, prove the connection between their builder identity and wallet, and create a verifiable link between real development activity and on-chain token markets.

GitHood uses read-only GitHub permissions. It cannot modify your code or control your funds. Its purpose is to prevent impersonation, verify the builders behind projects, and make it easier to see who is actually shipping.

With our GitHub infrastructure complete, we’re getting closer to the official GitHood launch on Robinhood Chain.

GitHub App: https://t.co/XRIWv5LiRx

Built for builders. Verified through GitHub. Powered by Robinhood Chain.

[GitHood @GitHoodapp]

Introducing GitHood

Robinhood Chain’s first GitHub-verified builder-funding protocol.

Verify GitHub. Launch a fair builder token. Every trade funds the maintainer and the shared GitHood treasury through Uniswap v4 hooks.

Code creates value. GitHood gives it a market.