Creator fee routing

This is the feature Hoodl is built around. Most launchpads let a creator send fees to one wallet. Hoodl lets you split a token’s fees across up to two recipients, address them by X handle, and tag people who haven’t joined yet — their share waits in escrow until they claim it.

Live on mainnet

The routing and escrow logic runs in the FeeSplitterEscrow contract, now deployed and verified on Robinhood Chain mainnet (4663). The app surfaces that drive it (setting recipients at launch, claiming) are still rolling out.

How a split works

At launch you set the 70% creator pool (see Fees) as up to two recipients:

• Each recipient is an X handle or a wallet address.
• Each gets a percentage, and the percentages sum to 100% of the creator pool.
• A recipient’s share accrues continuously as the token trades, paid in the quote asset (ETH/USDG).

Examples

• Solo: you → 100%. All creator fees go to your wallet.
• Collab: you → 50%, a collaborator’s wallet → 50%.
• Shout-out: you → 70%, @someCreator (X handle) → 30%. If that handle hasn’t joined Hoodl, their 30% accrues to escrow until they claim it.
• Tribute: you → 0%, @someCreator → 100%. Launch a token for someone and route the entire creator pool to them.

Launch a coin for someone to claim later

Because a recipient can be an X handle with no wallet, you can launch a token that routes fees to a creator who has never heard of Hoodl. When they show up, verify their handle, and link a wallet, everything that accrued in their name is waiting.

The identity problem

Binding an X handle to a payout wallet can’t be done trustlessly — there’s no on-chain oracle for “who owns @handle.” Every production system that does this (across the industry) relies on a centralized sign-in to verify control of the account. Hoodl is transparent about the trade-off:

• Verification uses Privy’s “Sign in with X” — the standard OAuth flow. Hoodl does not use a paid X API.
• On-chain, the split contract only ever knows addresses. After you prove control of the handle, a protocol linker writes the handle → wallet binding on-chain (the escrow’s linkHandle) — the single, auditable trust point. From then on the wallet can claim, and future fees for that handle credit it directly.
• Until a handle is linked, its share sits in escrow keyed to the handle — safe, and claimable later.
• If someone changes their X handle or a link is made in error, a protocol multisig has narrow dispute tools to correct it; the blast radius is limited to future deposits and still-escrowed balances.

How it compares

	Typical launchpad	Hoodl
Recipients	One wallet	Up to two, split by basis points
Address by X handle	No	Yes
Tag someone with no wallet yet	No	Yes — escrow keyed to the handle
”Launch for someone else”	No	Yes

The on-chain splitting idea is well-trodden (social fee-sharing has precedents on other chains). Hoodl’s contribution is making multi-recipient, X-addressable routing with escrow the centerpiece on an EVM launchpad — something typical launchpads don’t offer.

Limits today

The recipient cap is two in the first version. The underlying contract is written to support more recipients (the cap is a configurable maximum), so it can be raised later without a redesign.