Skip to content
View hoodvault's full-sized avatar
🎯
Focusing
🎯
Focusing

Block or report hoodvault

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
hoodvault/README.md
HoodVault

Every token you launched is still collecting fees you never took out.

Unclaimed creator fees on Robinhood Chain.

Site X Telegram Chain 4663 Free reads 0% claim No custody


Every token launched on this chain locks its liquidity permanently and charges a fee on every swap. Seventy percent of that fee belongs to whoever deployed the token — and it never arrives in a wallet. It accrues inside the locked position and waits for someone to call a function most creators have never called, and many don't know exists.

There was no screen anywhere that answered the only question that matters: how much is in there right now?

Paste an address, get a number

The read path

No wallet, no signup, no cost — and no backend. The locker already indexes tokens per deployer, so the whole read is a handful of contract calls made straight from the browser.

Why the number is exact, not an estimate

The claim itself is permissioned, but eth_call will simulate it from the creator's own address — no signature, no gas, no transaction. What comes back is the exact pair of amounts a real claim would move at that block, rather than a reconstruction of fee-growth maths that drifts from reality.

One detail that is easy to get wrong, and wrong silently:

// The creator/protocol split is snapshotted PER TOKEN at launch.
// The global value has already moved once — 90/10 to 70/30.
protocolPct = locker.tokenProtocolFeeShares(token);   // not the global figure

Read the global value instead and every older token is misreported by twenty percentage points.

What it costs

Layer What it does Price
The Mirror Paste any address — see every token it launched and what's owed Free, forever
The Pull Connect, claim, fees land in your wallet 0% — we're a button
The Drain Point your fee wallet at our splitter; the pile empties itself on your schedule 3% of what we move

Never on principal. Nothing if nothing moves. The read and the claim are the marketing — we charge for plumbing, and only for plumbing.

How the drain works, and how you leave it

The drain

Opting in is one transaction from your own wallet. Leaving is the same transaction, reversed. Payouts always go to the recipient the creator set — never to whoever triggered the call — so the keeper moves the money without ever being able to hold it.

The trigger condition lives in the contract, not on our server: the splitter reverts a drain below the creator's own threshold, so the keeper cannot fire early to book a fee.

Status

A fee-routing protocol that rounds up its own progress has already lost the argument it is making. So:

State
Mirror — read any wallet Live on mainnet
Pull — connect and claim Live on mainnet
Launch — one-transaction token launch Live on mainnet
Drain — the auto-drain splitter Not deployed. Contract unwritten, unaudited
$VAULT token Live0x92E43FD417A12f9633446FB40C8Aa5265c2659b3

The splitter will not be promoted until an independent audit is published in full. That is a launch gate, not a phase-two item.

On chain 4663

We deploy nothing yet. Everything below belongs to the chain's launchpad — we only read it.

Contract Address What it does
Locker v1 0x736D…7F35 Indexes tokens per deployer and per fee recipient
Locker v2 0x31ca…54B5 Same, newer factory — no fee-recipient index
Factory 0x7eD5…EC7e One-transaction launch, pairs against native ETH
WETH 0x0Bd7…AD73 What fees accrue in
HoodVaultSplitter not deployed Immutable, no proxy, no admin key over creator funds
$VAULT 0x92E4…59b3 Ours. This is the only address — check it here before you trust one

What we deliberately don't build

  • No shared vault. No pooled deposit, no receipt token, no TVL number to inflate.
  • No custody. The splitter's balance is zero at rest, by design.
  • No lockup, no exit penalty, no withdrawal fee.
  • No fee on principal, ever. Only on fees we actually move.
  • No paywall on the read. Free for any address, including ones that will never pay us.
  • No fake urgency. We never imply fees expire, decay, or are at risk. They don't.

Stack

Next.js · React · TypeScript · Tailwind · viem · Solidity

The frontend reads the chain directly from the browser. No API routes, no database in the read path, no server secrets — the only environment variables are public by design.


$VAULT is a utility token, not a security or a claim on revenue. Holding it lowers the rate we charge for our own service and unlocks our own tooling. Nothing more is promised.
Smart contracts carry risk, including total loss, even after audit. Nothing here is financial advice.

We watch the pile so you don't have to.

hoodvault.app · @hoodvaultRH · Telegram

Pinned Loading

  1. hoodvault hoodvault Public

    Profile README for HoodVault — unclaimed creator fees on Robinhood Chain. Read any wallet free, claim at 0%, no custody.

  2. hoodvault-api hoodvault-api Public

    Read-only HTTP API for Robinhood Chain creator fees. Returns unsigned launch transactions and holds no private keys.

    TypeScript

  3. hoodvault-docs hoodvault-docs Public

    How HoodVault reads Robinhood Chain, plus locker and factory quirks verified against deployed bytecode.