Hyperliquid 노드를 운영 중이신가요?Hyperliquid 피어링을 통해 블록 및 전체 멥풀에 대한 직접 경로를 활성화합니다.
자세히 알아보기SOC 2 Type II 인증 · ISO 27001
Connect to Mantle mainnet and every active testnet with low-latency RPC, full archive data, debug and trace APIs, and real-time Streams. The complete Mantle data stack, managed from a single Quicknode dashboard.
Mantle builders need more than basic RPC. Quicknode runs the full surface: low-latency JSON-RPC, full archive with debug and trace, and real-time Streams, all from one dashboard.
Query, subscribe, and stream Mantle data with low latency. From a single eth_call to billions of rows of historical logs, you get the right interface for the job.
Six ways to access Mantle data, from a single eth_call to billions of rows of queryable history. Pick the interface, ship faster.
Standard JSON-RPC over HTTPS and WSS on Mantle mainnet and Mantle Sepolia. Every EVM method supported, including eth_call, eth_getLogs, eth_getBalance, eth_sendRawTransaction, and eth_subscribe, with predictable rate limits.
Full historical Mantle state with no pruning. Run debug_traceTransaction and debug_traceBlockByNumber against archive nodes for indexing and simulation.
Backfill and real-time Mantle blocks, logs, and traces delivered to your datastore with guaranteed reliability. Filter upstream, receive only the data you actually need.
전달 보장, 재시도 기능, 내장된 재구성 처리 기능을 갖춘 이벤트 기반 알림입니다. 특정 주소, 계약 이벤트 또는 온체인 조건에 구독하여 실시간으로 대응할 수 있습니다.
Read rollup sync status and L2 output roots with optimism_syncStatus and optimism_outputAtBlock. This is the data bridges and withdrawal-proving flows use to verify Mantle state against Ethereum L1.
Subscribe to new Mantle blocks and logs over a persistent WSS connection with eth_subscribe. Push updates the moment they land, with no polling.
Mantle is a modular Ethereum layer 2, so the tooling you already know works unchanged. ethers.js, web3.js, viem, and web3.py all hit a Quicknode Mantle endpoint the same way they hit Ethereum. Same methods, same SDK, just a different RPC URL.
Point your existing Ethereum codebase at a Quicknode Mantle endpoint and deploy. Contracts, libraries, and tooling carry over.
eth_call, eth_getLogs, eth_sendRawTransaction, and eth_subscribe all behave exactly as they do on Ethereum.
// Your Ethereum code, pointed at Mantleimport { createPublicClient, http } from "viem";const client = createPublicClient({// Mantle mainnet, chain ID 5000chain: { id: 5000, name: "Mantle" },transport: http(QUICKNODE_MANTLE_URL)});const block = await client.getBlockNumber();// Same methods, same SDK. Mantle is a modular Ethereum layer 2.
Open MetaMask, go to Settings, Networks, Add Network, and enter your Quicknode Mantle RPC URL with the details on the right. Save, and MetaMask routes through your private Quicknode endpoint instead of a rate-limited public RPC.
Docs, guides, and runnable sample apps for every Mantle workload. Clone, customize, and ship.
Full reference for every Mantle JSON-RPC method, WebSocket subscription, and the debug and trace namespaces. Code examples for @quicknode/sdk, ethers.js, web3.js, and viem.
Indexes token transfers on an EVM chain using Quicknode Streams and delivers them to your own datastore and API. Works unchanged on Mantle.
Runnable sample apps and starter kits across Quicknode-supported chains, including Mantle. Clone one and ship.
From your first Mantle endpoint to mission-critical production workloads, Quicknode scales with you. Get started in minutes.
Spin up your Mantle endpoint and ship. The free tier covers prototyping and small production loads, no credit card required.
Dedicated Mantle infrastructure, contractual SLAs, priority support, and procurement-ready terms for wallets, exchanges, trading firms, and high-volume protocols.
"Quicknode became our primary provider because the consistency held. At 200 million API responses a day, it still does."Jonathan Skrzypek, VP of Engineering @ Dune
자주 묻는 질문
아직도 궁금한 점이 있으신가요? 고객 지원팀에 문의하시거나, ‘ Quicknode ’equipe 을 통해 답변을 찾으실 수 있습니다.
The Ethereum toolchain you already know works unchanged on Mantle. Deploy contracts, manage endpoints, and ship from one Quicknode account.