Quicknode

Blockbook REST is now live on Quicknode. Developers can now use REST or JSON-RPC from the same Blockbook endpoint, making it easier to work with whichever interface your stack already speaks. With this launch, Blockbook on Quicknode now includes: ✅ Up to 30% faster responses ✅ Four new REST methods ✅ REST and JSON-RPC support from one endpoint ✅ A zero-code-change migration path from self-hosted Blockbook ✅ Support across six chains For teams running their own Blockbook infrastructure, this means you can move to Quicknode’s managed Blockbook add-on without rewriting your existing integration, while also getting access to REST for new workflows. Read the full launch post: https://lnkd.in/eq4hwzn3 Start building with Blockbook on Quicknode: https://lnkd.in/efiTtw46

What happens when an AI agent needs a tool it was never pre-configured to use? ERC-8257, the Agent Tool Registry, is a draft Ethereum standard from OpenSea that lets agents discover, verify, and access tools onchain, permissionlessly. Every registered tool gets a minimal onchain record: • Creator address (the publisher, bound at registration) • Metadata URI (a pointer to the tool's manifest) • Manifest hash (proves the description hasn't changed) Plus an optional access predicate that decides who can call the tool: NFT holders, subscribers, allowlists, reputation thresholds. Lightweight registry, programmable access. Think DNS for agents. Providers publish once. Everyone reads the same records. Full breakdown, including where it fits alongside ERC-8004, x402, and MCP: https://lnkd.in/eNNWcXWA

Hyperliquid just entered prediction markets, and the way it happened says a lot about where the category is heading. HIP-4 launched in May, co-authored by Kalshi's own head of crypto, and settled around $6M in outcome contracts on day one. The headline writes itself: the #1 perpetual DEX moves into a space Polymarket and Kalshi already dominate. But the more interesting question is how it's structured. Polymarket treats prediction markets as information markets on Polygon, resolved through UMA's optimistic oracle. Kalshi runs regulated event contracts under CFTC oversight with fiat rails. Both are standalone venues, which means your prediction positions sit isolated from the rest of your portfolio. Hyperliquid took a different path. HIP-4 makes outcome contracts a native instrument inside HyperCore, the same engine that powers its perps. A trader long BTC can take a position on BTC's year-end price from the same account, drawing on the same collateral pool. For builders, that composability is the real story. It opens up products that weren't possible on a standalone venue: trading bots, macro hedges, and event-driven strategies where prediction positions share margin with perpetual exposure. Read more: https://lnkd.in/etw8iqHP

Five years ago, Uniswap settled trades on one chain. Today, over $4.3 trillion has moved through Uniswap, and the trading experience feels the same no matter which chain a swap routes through. That consistency is harder than it looks from the outside. Every new network brings its own RPC requirements, failure modes, and edge cases, and the work compounds as the team adds more chains. Launch day comes down to three things: method coverage that keeps pace with protocol upgrades, latency measured at the source rather than in one region, and reliability that holds when user attention is highest. Quicknode runs production infrastructure for 80+ chains, including every chain Uniswap Labs ships to users, with a 99.99% uptime SLA. When recent launches like Linea, Tempo, and X Layer went live, the endpoints were already running. As Melody Love, Staff Software Engineer at Uniswap Labs, put it: scaling across chains takes reliable infrastructure behind the scenes so the user experience stays simple, consistent, and fast. We broke down how it works: https://lnkd.in/eY28cVpz

The World Cup markets have been live on Hyperliquid for nearly a week. Every order, fill, and price swing since kickoff is public, onchain data now. 420 HIP-4 markets across 104 fixtures, all settling in USDC, all queryable. Here's the stack to build on them: Research with SQL Explorer. One query pulls trade history, price swings, and volume across every World Cup market. No node, no indexer, just SQL. Stream with gRPC. A goal lands, and the order book shifts two blocks later. gRPC catches it first. Trade with the Exchange API. Build the order, sign with your own wallet, send in one call. Everything you need to build on them: https://lnkd.in/eNJ9Hrci

Meet qn, the Quicknode CLI. Your whole Quicknode account from the terminal: endpoints, Streams, Webhooks, Key-Value Store, usage, billing, and teams. ↳ qn endpoint list ↳ qn stream list --limit 50 ↳ qn usage summary --from 7d Built for developers. Ready for agents. Pipe it into a script or an agent and it won't dump verbose JSON. It defaults to TOON, a compact format built for LLM prompts that saves you tokens. Install is one line: brew install quicknode/tap/qn Not on Mac? Windows, Linux, and Docker are supported too. https://lnkd.in/eadnJipT

Five years ago, Uniswap settled trades on one chain. Today, over $4.3 trillion has moved through Uniswap, and the trading experience feels the same no matter which chain a swap routes through. That consistency is harder than it looks from the outside. Every new network brings its own RPC requirements, failure modes, and edge cases, and the work compounds as the team adds more chains. Launch day comes down to three things: method coverage that keeps pace with protocol upgrades, latency measured at the source rather than in one region, and reliability that holds when user attention is highest. Quicknode runs production infrastructure for 80+ chains, including every chain Uniswap Labs ships to users, with a 99.99% uptime SLA. When recent launches like Linea, Tempo, and X Layer went live, the endpoints were already running. As Melody Love, Staff Software Engineer at Uniswap Labs, put it: scaling across chains takes reliable infrastructure behind the scenes so the user experience stays simple, consistent, and fast. We broke down how it works: https://lnkd.in/eY28cVpz

In payments, 'eventually' is the same as 'failed.' That's how pay3 CEO Varun Goel thinks about latency. Not a technical metric. A product promise. pay3 replaces the 42-character wallet address with one link, pay3.so/@username. Sender picks a token, sends, receiver sees "payment received" in seconds. The catch: pay3 runs on four chains, not one. Ethereum, BNB Smart Chain, Solana, and Tron, because that's where stablecoin users actually live. Monitoring all four in real time, for a watchlist that grows with every signup, is the real problem. Polling each chain burned RPC and added exactly the latency that breaks the promise. So they built it on Quicknode Streams instead: → ~2s detection from onchain landing to webhook → 7,000+ addresses monitored across 4 chains → $500K+ in stablecoin volume to date → No in-house indexer, no per-chain polling to babysit Adding a chain is a config change, not a rebuild. Same pipeline now powers their merchant-side payments too. Full breakdown ↓ https://lnkd.in/ePfbZSEN

One readable JSON body. Four calls. A resting order on Hyperliquid. No msgpack, no EIP-712 by hand, no nonce tracking. We built the Quicknode Exchange API to handle the wire format for you. Your key never leaves your machine. Preflight → Build → Sign → Send. That's the whole API. The video shows it running against the raw API, side by side. Docs: https://lnkd.in/gnmyPVRR

The World Cup kicked off today, and every match is a market on Hyperliquid. Traders are pricing each team's shot at the trophy in public, onchain. So we built a live World Cup Dashboard that reads those markets with one SQL query, refreshed every 5 minutes. The dashboard is just the demo. Everything behind it is available to build with: 📊 SQL Explorer: one query joins five indexed Hyperliquid tables and prices all 48 teams in under a second. Volume, price history, and how every market traded before kickoff. No node setup, no indexing pipeline. Just SQL. ⚡ HyperCore gRPC: stream real-time best bid and offer, orderbook depth, and fills. Your script sees the move the second a goal goes in. 🔁 Exchange API: build and submit orders programmatically from your own code, with your own wallet. HIP-4 prediction market actions included. Watch the markets on the dashboard, then build your own version of all of it. Live dashboard: https://lnkd.in/e2gSkj9V Docs: https://lnkd.in/eBmJEUVJ