From ce8b888cd45ccb99d8b1e3c00c7e5984491e9117 Mon Sep 17 00:00:00 2001 From: Lucas Tortora <85233773+lucas-tortora@users.noreply.github.com> Date: Fri, 1 Mar 2024 10:10:10 -0300 Subject: [PATCH] Update docs/build/wasp-evm/v1.0.0-rc.6/docs/how-tos/integrate-your-exchange.mdx Co-authored-by: Jeroen van den Hout --- .../v1.0.0-rc.6/docs/how-tos/integrate-your-exchange.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/build/wasp-evm/v1.0.0-rc.6/docs/how-tos/integrate-your-exchange.mdx b/docs/build/wasp-evm/v1.0.0-rc.6/docs/how-tos/integrate-your-exchange.mdx index 18a2451874b..1c8ccff570f 100644 --- a/docs/build/wasp-evm/v1.0.0-rc.6/docs/how-tos/integrate-your-exchange.mdx +++ b/docs/build/wasp-evm/v1.0.0-rc.6/docs/how-tos/integrate-your-exchange.mdx @@ -9,7 +9,7 @@ import { ChainId } from '@theme/ChainId'; # ShimmerEVM Exchange Integration If you already support EVM, then you probably are already familiar with what you'll need to integrate ShimmerEVM. As -with most networks, you should be able to use the same API as [go-ethereum](https://geth.ethereum.org/) taking into account the +with most networks, you should be able to use the same [JSON RPC API](https://wiki.iota.org/wasp-evm/reference/json-rpc-spec/) or clients, like [go-ethereum](https://geth.ethereum.org/), taking into account the [compatibility and limitations](../getting-started/compatibility.md), use the ShimmerEVM RPC URL (https://json-rpc.evm.shimmer.network) and ChainId (), and run our [Hornet](/hornet/welcome/) node with the [Wasp](/wasp/running-a-node/) INX-plugin.