Docs

Every token launched on this chain locks its liquidity permanently and charges a fee on every swap. Most of that fee belongs to whoever deployed the token. It does not arrive in a wallet — it accrues inside the locked position and stays there until somebody calls a function to move it.

HoodVault reads any wallet and shows exactly what each of its tokens is holding, then gives you three ways to get it out. Reading and claiming are free. We charge only for automating the claim.

• ›Read any address — no wallet, no signup, no signature
• ›Claim it yourself at 0%, always
• ›Or let it drain itself on your schedule for 3% of what moves
• ›Non-custodial: we never hold your funds between transactions
• ›One transaction in, one transaction out, from your own wallet

The launchpad's locker already keeps a list of every token per deployer and per fee recipient. That means finding your tokens is a plain contract read — there is no indexer between you and the chain, and no server that could show you a stale number.

Where the amount comes from

The claim function is permissioned, but a simulated call costs nothing and sends nothing. We simulate the claim from your own address and read back the exact pair of amounts a real claim would move at this block. It is not an estimate and not a reconstruction of fee-growth maths — it is the number the contract itself would produce.

Why each token shows a different split

The creator/protocol split is snapshotted per token when it launches. The platform default has already changed once, so older tokens and newer tokens genuinely pay different rates. We read the value for each token individually. Anything that used the current global figure would misreport older tokens by twenty percentage points.

Connect your wallet and press claim. You sign one transaction per token, the fees land in your wallet, and we take nothing. There is no tier, no minimum and no catch on this path — the button says 0% because it is 0%.

We keep it free because the read and the claim are how people find out we exist. What we sell is never having to remember again.

Opting in points your fee wallet at our splitter with one transaction sent from your own wallet. From then on our keeper triggers the claim on your schedule, pays the gas, and the splitter forwards your share in the same transaction.

When it fires

• ›Threshold — once the pile crosses an amount you set
• ›Schedule — every N days regardless of size
• ›Both — whichever comes first
• ›Manual — wired but only when you press it

The trigger condition lives in the contract, not in our server. The keeper cannot fire early to book a fee on a pile that has not met your own condition.

What the contract guarantees

• ›The splitter's balance is zero at the end of every transaction
• ›Your share transfers before ours, in the same transaction
• ›The fee is capped at 3% by a constant that cannot be raised
• ›No function can send funds to an address you did not set
• ›No owner withdrawal path exists over creator funds
• ›Immutable — no proxy, no upgrade key, no admin pause

Point your fee wallet back at yourself. It is one transaction, sent from your own wallet, and it needs no permission, no notice period and no conversation with us. We cannot block it, delay it or charge for it.

This is deliberate. A product that has to trap its users to keep them has already lost the argument it is making about custody.

What holding changes

Holding lowers the rate we charge for our own automated drain — 3% at open, down to 2%, 1%, and 0% by tier — and unlocks our own tooling: more watched wallets, the buy-back and deepen routes, and a read API key.

What it may never do

• ›Buy a bigger share of anyone's fees
• ›Buy a faster drain or preferential ordering
• ›Pay a rate of return, in any form
• ›Gate access to somebody else's fee flow

Where our revenue goes

Paid API spend is burned. Operations are funded from our own creator position on the token rather than from the cut, which keeps the cut going entirely to buyback and keeps the two flows separable in public accounting.

At this chain's current size the automated cut is a small business — a few hundred dollars a day at realistic adoption. The larger revenue line is our own creator position on the token. We publish both.

A protocol that asks creators to route fee income through its contract cannot be coy about its own fee income. Disclosure here is not a courtesy, it is the product's core claim.

What could kill this

• ›The launchpad could ship a claim button of its own any week — the largest risk, not a footnote
• ›Everything depends on this chain staying alive; a major launchpad on it has already gone dark once
• ›Redirecting fee income is a real act of trust and nobody should do it without a published audit
• ›Fee splits are set by a third party, already moved from 90/10 to 70/30, and can reach 50/50

Do I have to connect a wallet to see my number?

No. Reading is a public call. You can check your own address, a friend's, or the deployer of anything you bought this morning.

Can you take my fees?

No. Payouts always go to the recipient the creator set, never to whoever triggered the call. Our keeper can start a claim; it can never receive one.

Do the fees expire if I never claim?

No. They do not decay, expire or become unclaimable. Anyone telling you otherwise is inventing urgency. The pile simply sits there.

Why is my split 90/10 when the docs say 70/30?

Because the split is fixed for each token when it launches. Tokens launched before the platform changed its default kept the older, better terms. We read the real value for each token rather than assuming.

What happens if you disappear?

Point your fee wallet back at yourself and claim manually as before. The splitter holds nothing between transactions, so there is no balance of yours to strand.

Is there a token yet?

Not at the time of writing. Any contract claiming to be it is fake. The product ships first; the token launches into something that already works.