Home/DeFi/@hyperbook_ely
63
Score · promising
Scored 5d ago

@hyperbook_ely

Hyperbook

Hyperbook bridges Hyperliquid's order book data to Elysium (EVM L2) via signed snapshots every ~100ms, enabling dynamic-fee Uniswap v4 hooks and USDC perps that price off live HyperCore depth. The project has shipped mainnet contracts including WHYPE/USDC and KNTQ/USDC pools, launched $HBOOK token on their own hook with forever-locked LP, and published a self-review audit. Small following (~113) and 5-month-old account signal genuine early-stage status, though reliance on centralized signers and Elysium's nascent ecosystem introduce execution risk.

AI Analysispromising

Confidence
72%

Hyperbook bridges Hyperliquid's order book data to Elysium (EVM L2) via signed snapshots every ~100ms, enabling dynamic-fee Uniswap v4 hooks and USDC perps that price off live HyperCore depth.

The project has shipped mainnet contracts including WHYPE/USDC and KNTQ/USDC pools, launched $HBOOK token on their own hook with forever-locked LP, and published a self-review audit.

Small following (~113) and 5-month-old account signal genuine early-stage status, though reliance on centralized signers and Elysium's nascent ecosystem introduce execution risk.

Green flags: Working mainnet product — live pools and perps on Elysium with verifiable on-chain activity · Technical differentiation: brings Hyperliquid's 200-level order book into EVM contracts via signed EIP-712 snapshots · Team eats own cooking — launched $HBOOK on their own Uniswap v4 hook with永久锁仓 LP, 100% protocol revenue to burn · Published audit/review of contracts publicly, transparent about trust assumptions · Small footprint (113 followers, 5mo old account) with substance — real infra shipped

Red flags: Centralized trust model — snapshots signed by off-chain signers, not purely decentralized oracle · Elysium is itself an early/unproven L2 — ecosystem risk if chain fails to gain traction · All tweets from same day (2026-11-11) suggest coordinated launch push, limited organic growth signal yet · No VC/team disclosure, anonymous builders (common in DeFi but adds trust surface)

Token
$HBOOK · announced
Chain
Elysium
Stage
mainnet+live
Category
oracle/liquidity infra

Recent tweetsSee all on 𝕏 →

The full Hyperliquid order book is now a free primitive on Elysium. 200 levels. Signed every ~100 ms. Verified by one call from any contract. What you can build on it today: · lending that liquidates at the real book, not a TWAP · options marked to live HyperCore vol · launchpads anchored to exchange price from block 1 · vaults that hedge spot LP with a perp in the same tx · bots that arb our pools — the hook charges you, LPs keep it No key. No contract to sign. No permission. And the day Elysium ships native HyperCore reads, every one of these flips to the precompile automatically. Same interface, zero latency, no vendor in the loop. You build once — the rails upgrade under you. https://t.co/Xp4cIdiWX8
5d ago♥ 19💬 5🔁 1
Thanks for the support and for letting more people know, our product will change the game for elysium.
5d ago♥ 24💬 18🔁 3
Why we launched $HBOOK on a hook, not a plain pool We build hooks for a living. AnchorHook is a Uniswap v4 hook. Of course we launched our own token on one. Forge on Elysium gave us things a plain pool can't: 1. LP is locked forever. Not "locked for 6 months", not "team promises". Burned at the contract level. The oldest rug in crypto is physically impossible. 2. Snipers eat a wall. Max 1 KNTQ per block at launch. No bot could load up in block one and dump on you in block two. Every early holder bought at roughly the same price — including us. Our dev buy was 1 KNTQ. 3. Dumps pay for the holders. The pool fee is dynamic: calm market = 1%, someone slams price inside a 60-second window = fee climbs to 6%. Panic sellers and volatility bots get taxed; the fee goes to LPs. Rapid-dump cascades that kill 99% of launches are mechanically dampened here. 4. Fees fund the project, not a wallet. Creator share → protocol buyback → $HBOOK bought and sent to 0xdead. Launch revenue burns supply. 5. No admin keys. Hook logic is on-chain and immutable. We can't change the fee, can't pause, can't pull liquidity. You don't have to trust the team because the team can't do anything. 6. It's native v4. The same PoolManager, the same hook architecture our AnchorHook pools run on. Any v4 router, aggregator, or integration on Elysium picks $HBOOK up for free. Plain pool: trust the deployer. Hook pool: read the code. This is the thesis of Hyperbook in one launch — market structure should be enforced by hooks, not promises. We wouldn't ship it to you if we didn't launch on it ourselves. https://t.co/KXmdNlUQEk
5d ago♥ 15💬 6🔁 4
Builders on Elysium: Hyperliquid's order book is now a free primitive. Here's what you can do with it today. THE API (free, no key) · GET /v1/snapshot/{coin} — mid, bid/ask, 25 bps depth, imbalance, volatility, slippage, from the full 200-level book, signed, ~100 ms fresh · WebSocket /ws — the same stream pushed every 100 ms · /v1/hook/quote, /v1/pool/quote — exact fee and output for any swap before you send it · IBookOracle on-chain — one call, verified by BookAttestor, no trust in us required BUILD · Lending that liquidates at the real book, not a stale TWAP · Options / structured products marked to live HyperCore vol · Launchpads where the pool is anchored to exchange price from block one · Vaults that hedge spot LP with a BookPerp position in the same tx · Bots that arb our pools vs HyperCore — go ahead, the hook charges you the deviation and LPs keep it · Anything that needs a price that can't be manipulated by a thin on-chain pool LP · WHYPE/USDC and KNTQ/USDC AnchorHook pools. Dynamic fee: traders pulling price toward HyperCore pay 0.03%+; anyone trying to arb the gap pays the full deviation. The LVR leak — the reason most AMM LPs lose to arbs — goes to the LP instead of the bot. · Protocol share of every swap → buys $HBOOK → 0xdead · Perp LP vault: counterparty to BookPerp, earns open/close fees + funding + liquidation share · Add from the site, remove any time, no lockups SAFE Every contract reviewed line by line, Slither on every build, 37 tests, every finding and its status published at https://t.co/MLxDom9CDT. Owner can't touch user funds. Route to burn is locked on-chain. And when Elysium ships native HyperCore reads, all of this switches to the precompile automatically — your integration doesn't change. https://t.co/KXmdNlUiOM
5d ago♥ 10💬 3🔁 1
We already built this. Live on Elysium today. Hyperbook = v4 hooks that read Hyperliquid's full order book — 200 levels, signed every 100 ms, verified on-chain by contract. What's shipped: · AnchorHook pools (WHYPE/USDC, KNTQ/USDC) that price off HyperCore's real book. Arbs pay the deviation, LPs stop bleeding LVR. · BookPerp — USDC perps that open, close and liquidate at Hyperliquid's marked price. No oracle lag. · Signed snapshots free over REST/WS — any contract gets the book in one call. · All revenue → buys $HBOOK → 0xdead. Locked on-chain. Your wishlist: launches with built-in market making, hooks reacting to perps, auto-hedging vaults, spot+perp products — every one of them is a Hyperbook integration, not a research project. The data layer is done. And the second half of your sentence is the roadmap: the moment Elysium ships native HyperCore reads in the EVM, Hyperbook switches to it automatically — IBookOracle was designed for the precompile from day one, zero changes for pools, perps or integrators. Then hooks that don't just read HyperCore but execute on it. 100 ms blocks. The real book. Hooks that use it. Now. https://t.co/KXmdNlUQEk
5d ago♥ 20💬 17🔁 2

Signal Timeline

CR
@crypto_peet followed
AFirst discovered·5d ago

Score breakdown0–100

🎯Scout conviction
+21.7 / 35
📚Scout consensus
0 / 10
🪪Profile & earliness
+16 / 20
✍️Substance
+10 / 20
🤖AI verdict
+21.3 / 30
⚠️Penalties
-6 / 40
63
Below threshold (74)
Watching for additional signals.
Followers
113
Account age
2.4y
Scouts
1
First seen
5d ago