The intelligence layer for onchain hooks
Hookline organizes live contract evidence around one chain-aware identity, then makes the record useful through watchlists, comparisons, monitoring, and developer access.
Read deployed bytecode, fingerprint the runtime, probe conventional ownership, decode permissions, and retain the observed block.
Save named local watchlists, refresh evidence intentionally, preserve successful history, and surface failures without erasing prior state.
Consume the same evidence through constrained JSON-RPC and a machine-payable x402 capacity route.
Current boundary: The board uses a timestamped community-indexer snapshot for discovery and aggregate counts. Live inspection remains direct RPC evidence. Time-series analytics, alerts, and long-range event history are planned work.
Evidence before interpretation
Contract identity is always chain ID + normalized address. Each successful observation retains chain, address, block, timestamp, bytecode size, runtime fingerprint, permission state, owner-probe result, and latency.
A failed refresh remains a failure. It never becomes empty successful evidence and never overwrites the most recent valid observation.
One evidence surface for people and agents
Hookline methods
hookline_chainssupported networks and upstreamshookline_decodePermissionscanonical low-14-bit permission statehookline_chainStatusidentity, height, status, and latencyhookline_getHooklive evidence for one chain and address
{
"jsonrpc": "2.0",
"method": "hookline_getHook",
"params": [8453, "0xb082…6888"],
"id": 1
}The free route is rate limited. POST /rpc/paid requests 0.01 USDC on Base through x402. The proxy rejects transaction submission, account access, administrative, debug, trace, and batch requests.
An evidence and coordination layer for hooks
Programmable-liquidity hooks create a discovery problem. Deployments, permissions, code versions, owners, pool relationships, activity, and project claims live across tools that do not treat the hook as a first-class research object.
Hookline’s job is to make it easy to answer what a hook is, where it is deployed, what it can do, what depends on it, what changed, and where the evidence came from.
The board now supplies broad cross-chain discovery and aggregate activity. The next data layer indexes official PoolManager initialization, swap, liquidity, and donation events into a rebuildable first-party graph. Every metric keeps its chain, block range, generated time, and derivation version.
Read the complete whitepaper on GitHub ↗Build usefulness before surface area
- NOW
Dependable evidence desk
Live inspection, permission decoding, watchlists, comparisons, telemetry, free RPC, and x402 capacity.
- NEXT
Hook registry and pool graph
PoolManager event ingestion, canonical identities, raw-log retention, verified-source metadata, and searchable profiles.
- THEN
Activity and change intelligence
Swap and liquidity history, code and owner change detection, dependency timelines, alerts, and reproducible exports.
- LATER
Professional and ecosystem layers
Team workspaces, webhooks, longer retention, signed manifests, contributed research, and additional programmable-liquidity systems.
Frequently asked questions
Where does Hookline data come from?
The hook board uses a timestamped v4.xyz community-indexer snapshot for discovery and aggregate pool and swap counts. Names and descriptions are community-curated or project-submitted. Live contract evidence comes directly from configured Ethereum, Base, Arbitrum One, and Robinhood Chain RPC endpoints.
Is Hookline already indexing volume and liquidity?
The board exposes indexed pool and swap aggregates, not price, market cap, dollar volume, or liquidity claims. First-party event-backed pool discovery, time-series activity, and historical analytics are the next data layer.
What do the 14 permission flags prove?
They identify which Uniswap v4 callback permissions are encoded in the hook address. They do not explain the complete runtime behavior and do not establish that a contract is safe.
Is this a smart-contract audit?
No. Hookline is an evidence and monitoring product, not an audit, legal opinion, or trading recommendation.
Why can’t I compare live state across chains?
An address is not a complete identity, and block heights on separate chains do not share state or time semantics. Hookline limits direct comparisons to one chain.
Are watchlists uploaded?
Not currently. Lists and observations are stored in the browser and can be exported or imported as JSON.
Does the RPC submit transactions?
No. Transaction submission and account-access methods are rejected by the public service.
What is the x402 route?
It is a machine-payable capacity path. A valid unpaid request receives an HTTP 402 challenge for 0.01 USDC on Base.
What is HKLN?
HKLN is Hookline’s service-alignment asset on Base. Current product access does not require holding it. Future holder features are inactive until implemented and documented.
Does market cap generate Hookline revenue?
No. Market cap itself does not create creator fees. Venue fees require trading activity, and product revenue requires useful paid services.
Is Hookline affiliated with Uniswap or Robinhood?
No. Hookline is independent and is not endorsed by Uniswap Labs, Robinhood, Flaunch, PayAI, or its RPC providers.
How can I contribute?
Use the public GitHub repository. Include chain, exact address, block range, expected result, and reproduction steps in evidence-related issues.