Fee pressure becomes exposure
Hood3 treats usage as fuel: fees flow to margin, margin creates HOOD exposure, and the position is published back to the token layer.
Current positionNO POSITIONwallet not connected
Size$00 HOOD
Total SOL bridged0 SOLclaim rail idle
HOODX price$0.0000not trading yet
Total burnt0HOODX retired
Current positionNO POSITIONwallet not connected
Size$00 HOOD
Total SOL bridged0 SOLclaim rail idle
HOODX price$0.0000not trading yet
Total burnt0HOODX retired
Hood3 automation terminal
Hood3
Hood3 turns protocol flow into a transparent NLT flywheel: claim fees, route SOL, fund Hyperliquid, expand a HOOD long, burn HOODX, and publish the receipts like a professional onchain desk.
Desk modeAutomation rail readyZeroed until live Supabase events arrive
Fee run-rate$0awaiting live flow
NLT backing$0.0000per token
Burn route0%not active yet
Why Hood3 exists
A cleaner surface for an aggressive thesis.
The homepage stays focused on the visual identity and live desk snapshot. The dashboard holds the automation rail, transaction terminal, and NLT backing logic; the HOOD bull case has its own dedicated page.
Burns stay visible
HOODX burn data sits in the header instead of being buried in a modal, making supply reduction part of the product surface.
Automation with receipts
The execution rail keeps private keys server-side while the site publishes every claim, transfer, swap, order, and burn event.
Dashboard moved to its own page.
Account linking, NLT backing, bridge metrics, and the “how it works” flow are grouped into the desk page.
Burns and position size stay in the top header on every route.
Execution is server-side only, with browser keys kept out of the product surface.