Supported Networks

The following networks are supported by default. In the RPC URLs you can use either the name or the id of the chain as specified in the table.

Network	Name	Id
Ethereum Mainnet	`ethereum-mainnet`	`0x01`
Polygon Mainnet	`polygon-mainnet`	`0x89`
Polygon Amoy (Testnet)	`polygon-amoy`	`0x013882`
BSC Mainnet	`bsc-mainnet`	`0x38`
Ethereum Sepolia (Testnet)	`sepolia`	`0xaa36a7`
Arbitrum One	`arbitrum-mainnet`	`0xa4b1`
Arbitrum Sepolia (Testnet)	`arbitrum-sepolia`	`0x066eee`
Base	`base-mainnet`	`0x2105`
Base Sepolia (Testnet)	`base-sepolia`	`0x014a34`
Celo	`celo-mainnet`	`0xa4ec`
Optimism	`optimism-mainnet`	`0x0a`

HTTP Requests

URL Format - https://rpc.shield3.com/v3/[NETWORK NAME OR ID]/[API_KEY]/rpc

All standard RPC methods are supported as specified in the Ethereum JSON-RPC Spec

Shield3 Specific Methods

Simulation

The RPC API accepts a custom method eth_simulateTransacion to get the policy results of the transaction without broadcasting.

The parameters passed to eth_simulateTransaction are [serializedTx, fromAddress]

For more on simulation see Simulate Api Reference

Backfill

The RPC API accepts a custom method eth_backfillTransaction to track transaction that was broadcast and confirmed outside of Shield3's RPC to the transaction dashboard

The parameters passed to eth_backfillTransaction are [txHash]

Websocket Requests

URL Format - wss://ws-rpc.shield3.com?apiKey=[API_KEY]&networkId=[NETWORK NAME OR ID]

The websocket API can be used to subscribe to new events using the eth_subscribe and eth_unsubscribe methods.

For more on websocket request formats see Alchemy websocket docs