add rpc requirements to docs

polytope-labs · Dec 21, 2024 · 66b3ad3 · 66b3ad3
1 parent fd2f1fe
commit 66b3ad3
Showing 1 changed file with 9 additions and 0 deletions.
diff --git a/docs/pages/developers/network/relayer.mdx b/docs/pages/developers/network/relayer.mdx
@@ -306,6 +306,15 @@ It is optional to provide the configuration option for any of the connected chai
 
 You can obtain the required etherscan API key by following [this guide](https://docs.etherscan.io/getting-started/viewing-api-usage-statistics) for the appropriate network. Do note that since Ethereum and its L2s all use Ether as the gas token. They can all share the same etherscan API key.
 
+### RPC Endpoint Requirements
+
+The tesseract relayer makes use of rpc methods that may not be exposed for the different chains it support. For evm chains, ensure that the RPC API supports the following namespaces:
+
+ - [`debug`](https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-debug)
+ - [`eth`](https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-eth)
+
+For substrate chains, ensure the RPC [enables unsafe rpc methods](https://docs.substrate.io/build/remote-procedure-calls/#safe-and-unsafe-rpc-methods).
+
 ### Contract addresses
 
 You can find the addresses for the `IsmpHost` contracts for [mainnet](/developers/evm/contracts/mainnet) and [testnet](/developers/evm/contracts/testnet)