From ac3d0702e879af370632a8afc851b15c3eba8bdc Mon Sep 17 00:00:00 2001 From: Ilaria <43253244+ilariae@users.noreply.github.com> Date: Thu, 1 Aug 2024 18:52:09 +0200 Subject: [PATCH] Update learn/infrastructure/relayer.md Co-authored-by: Erin Shaben --- learn/infrastructure/relayer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/learn/infrastructure/relayer.md b/learn/infrastructure/relayer.md index 5276d250..89f7689c 100644 --- a/learn/infrastructure/relayer.md +++ b/learn/infrastructure/relayer.md @@ -13,7 +13,7 @@ There are three primary types of relayers discussed: - **Client-side relaying** - a cost-efficient, no-backend-infrastructure approach relying on user-facing front ends. It provides a simple solution, although it can complicate the user experience due to the manual steps involved - **Specialized relayers** - backend components that handle parts of the cross-chain process, offering a smoother user experience and allowing off-chain calculations to reduce gas costs. These relayers could operate through direct listening to the Guardian Network (Spy relaying) or by providing a REST endpoint to accept VAAs to be relayed (REST relaying) -- **Standard Relayers** - a decentralized relayer network that can deliver arbitrary VAAs, reducing the developer's need to develop, host, or maintain relayers. However, they require all calculations to be done on-chain and might be less gas-efficient +- **Standard relayers** - a decentralized relayer network that can deliver arbitrary VAAs, reducing the developer's need to develop, host, or maintain relayers. However, they require all calculations to be done on-chain and might be less gas-efficient ## Fundamentals