본문으로 건너뛰기

RPC 제공자

선택할 수 있는 여러 RPC 공급자가 있습니다. 이러한 공급자는 NEAR 네트워크와 상호 작용하는 데 도움이 되는 중개자 역할을 합니다. 이중화(redundancy) 및 균형 조정을 위해 잠재적으로 여러 공급자를 사용할 수 있습니다. You'll experience different latency levels depending on the provider's location.

If you want to use a custom RPC provider with NEAR Wallet Selector, check this example.

Mainnet

공급자엔드포인트 루트
NEARhttps://rpc.mainnet.near.org
Pagodahttps://rpc.mainnet.pagoda.co
1RPChttps://1rpc.io/near
All That Nodehttps://near-mainnet-rpc.allthatnode.com:3030
ankr.comhttps://rpc.ankr.com/near
BlockPihttps://public-rpc.blockpi.io/http/near
dRPChttps://near.drpc.org
fast-near web4https://rpc.web4.near.page
FASTNEARhttps://free.rpc.fastnear.com
Gateway.fmhttps://rpc.near.gateway.fm/
GetBlockhttps://getblock.io/nodes/near/
Lava Networkhttps://near.lava.build
Lavender.Five Nodeshttps://near.lavenderfive.com/
NodeRealhttps://nodereal.io/api-marketplace/near-rpc
NOWNodeshttps://near.nownodes.io/
OMNIAhttps://endpoints.omniatech.io/v1/near/mainnet/public
QuickNode-
Seraclehttps://api.seracle.com/saas/baas/rpc/near/mainnet/public/
Zeeve-

Testnet

ProviderEndpoint Root
NEARhttps://rpc.testnet.near.org
Pagodahttps://rpc.testnet.pagoda.co
FASTNEARhttps://test.rpc.fastnear.com

RPC Failover

In near-api-js you can use FailoverRpcProvider to automatically switch RPC providers when one provider is experiencing downtime, or implement an RPC selection widget that allows users to add their own RPC provider.

As a user, if a dApp or wallet doesn't support RPC failover and the primary provider is down, you can use an RPC Selector browser extension to redirect all requests to an RPC provider of your choice.

Was this page helpful?