What is a Bulletin Subnet RPC?
An RPC endpoint connects wallets and applications to Bulletin Subnet. Use the endpoints above for JSON-RPC requests, and keep alternatives available for regional endpoint failures or rate limits.
Public RPC endpoints and wallet configuration for Bulletin Subnet.
An RPC endpoint connects wallets and applications to Bulletin Subnet. Use the endpoints above for JSON-RPC requests, and keep alternatives available for regional endpoint failures or rate limits.
Use “Add to wallet” to request the network configuration. Always verify chain ID 78431, currency BLT, and the selected RPC before approving.
Public endpoints are third-party infrastructure. They may log requests, enforce limits, or become unavailable. Never place private keys, seed phrases, or secrets in an RPC request.
Rate limits, browser CORS rules, network mismatch, and temporary provider failures are common. Try another listed endpoint and verify the returned chain ID.
https://subnets.avax.network/bulletin/testnet/rpc is the recommended endpoint in this directory. Multiple alternatives are listed above in case an endpoint is unavailable from your region.
Bulletin Subnet uses chain ID 78431 (0x1325f in hexadecimal).
Use the Add to wallet button above. Your wallet will ask you to review and approve the network details.
Treat public RPCs as infrastructure operated by third parties. They can observe requests, rate-limit traffic, or be unavailable. Never send private keys or seed phrases to an RPC.
Help keep network data current through a community contribution.