From b1ca305b60a0fcce5c9ce6add152cb3744d96ec0 Mon Sep 17 00:00:00 2001 From: Marty <149421156+ffe9f8@users.noreply.github.com> Date: Mon, 22 Jul 2024 19:17:45 +0200 Subject: [PATCH] fix: wording of integrator options (#1059) --- .../dev/amplifier/chain-integration/integrate-a-chain.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pages/dev/amplifier/chain-integration/integrate-a-chain.mdx b/src/pages/dev/amplifier/chain-integration/integrate-a-chain.mdx index 129143f63..dfb034c07 100644 --- a/src/pages/dev/amplifier/chain-integration/integrate-a-chain.mdx +++ b/src/pages/dev/amplifier/chain-integration/integrate-a-chain.mdx @@ -203,7 +203,7 @@ Use the existing deployments for all three contracts, making note of the existin -You can also deploy a custom implementation of the gateway, verifier, and prover contracts and optimize them with the [`Cosmwasm rust-optimizer`](https://github.com/CosmWasm/optimizer). Follow the same steps as Option 2 with your own implementations of the Amplifier contracts. +You can also deploy a custom implementation of the gateway, verifier, and prover contracts and optimize them with the [`Cosmwasm rust-optimizer`](https://github.com/CosmWasm/optimizer). Follow the same steps as you would with your own implementations of the Amplifier contracts. @@ -365,4 +365,4 @@ Every new chain will need a verifier, which requires running `ampd` and `tofnd`. ## Begin routing messages -Once your chain is registered with the protocol, it will need verifiers to begin routing messages. See [Become an Amplifier Verifier (Worker)](/validator/amplifier/verifier-onboarding) for instructions to onboard a verifier. Note that chain integrators will onboard on `devnet-amplifier` and not `devnet-verifier`. \ No newline at end of file +Once your chain is registered with the protocol, it will need verifiers to begin routing messages. See [Become an Amplifier Verifier (Worker)](/validator/amplifier/verifier-onboarding) for instructions to onboard a verifier. Note that chain integrators will onboard on `devnet-amplifier` and not `devnet-verifier`.