How Hoodium works
Hoodium is three products that share one ledger: a manager for concentrated-liquidity positions, a fixed-supply launchpad, and the token that earns from both. Everything here is non-custodial: you sign, your wallet holds, and Hoodium never takes possession of a position or a token.
Chains and venues
Hoodium reads and signs on two chains. A position is identified by its chain, its position manager and its token id, and nothing in the system assumes the same address means the same contract on both.
| Chain | Venues | What runs there |
|---|---|---|
| BNB Chainchain id 56 | PancakeSwap v3Uniswap v3 | Position management, automation, one-signature claim, zap |
| Robinhood Chainchain id 4663 | Uniswap v4Uniswap v3 | The same, plus the launchpad |
Uniswap v4 is a first-class venue, not an afterthought: v4 has a single PositionManager fronting every pool and no IncreaseLiquidity event, so its positions are read, priced and ranked through their own code path rather than squeezed through the v3 shape.
Quick start
- Open pools.hoodium.app and connect a wallet. Connecting is a signature, not a transaction, and it grants nothing. Any wallet that speaks WalletConnect or an injected provider works.
- Look before you sign. The board and every position page are readable with no wallet at all. The numbers are derived from public chain data, not from your session.
- Act on a position. Claim, compound, rebalance, zap in and zap out are single flows that build the transaction and show you what it will do before your wallet asks.
- Arm automation only when you want it. A rule watches in shadow mode for seven days first, and no rule can fire until you review what it would have done and confirm.
You need the chain's native token for gas (BNB on 56, ETH on 4663) and nothing else. There is no Hoodium account, no deposit and no sign-up.
Where the numbers come from
Every figure Hoodium shows is derived, not quoted from an oracle:
- Position state is read from the venue's own position manager and the pool's
slot0, live. - Fee and PnL history is rebuilt from the venues' own events (mints, burns, collects, and each pool's swaps) and stored as a per-position ledger with a cost basis.
- Pool volume and fee income are summed from
Swaplogs on chain rather than bought from a data provider, so a pool nobody indexes still has real numbers. - Prices come from the chain's own pools. Most tokens on Robinhood Chain have no external price feed, so a token is valued by routing it through the pools that actually trade it, and is marked unpriceable when none do rather than being given a made-up number.
Value charts start when indexing started. Snapshots are forward-only telemetry: re-indexing recovers history for fees and PnL, but a chart of position value can only fill in from the point Hoodium began sampling. A short chart on an old position is that, not a gap in the data.
What Hoodium never does
- It never holds your private key, and it never asks for a seed phrase. There is no session key, no custodial wallet and no deposit address.
- It never moves a position you did not sign for. Automation acts on an order carrying your signature, against limits in that signature, and pays every proceed to the position's owner.
- It cannot take a position away. The approvals it uses are operator rights on your position NFT, revocable by you at any time from your wallet, and the contracts have no path that sends a position anywhere but back to its owner.
The long version, including which keys exist and what a stolen one could do, is on Security and risk.
Questions
Write to hello@hoodium.app or @HoodiumHQ. Live service health for every product is at status.hoodium.app. If a question is about a specific charge or execution, start from the transaction hash. Every automated action emits an event beside the action it was taken from.