From 1b16f851c9d9cec82ce813b729be8b4f4953fb4d Mon Sep 17 00:00:00 2001 From: John Hilliard Date: Mon, 25 Nov 2024 13:59:34 -0500 Subject: [PATCH] Update architecture.mdx Updating broken proxyd link --- pages/builders/chain-operators/architecture.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/builders/chain-operators/architecture.mdx b/pages/builders/chain-operators/architecture.mdx index 36fe57400..2b8b5ef5e 100644 --- a/pages/builders/chain-operators/architecture.mdx +++ b/pages/builders/chain-operators/architecture.mdx @@ -56,7 +56,7 @@ requests from your users. The Sequencer node has the important job of working wi the batcher to handle block creation. To allow the Sequencer to focus on that job, you can peer replica nodes to handle the rest of the work. -An example of this would be to configure [proxyd](https://github.com/ethereum-optimism/optimism/tree/develop/proxyd) +An example of this would be to configure [proxyd](https://github.com/ethereum-optimism/infra/tree/main/proxyd) to route RPC methods, retry failed requests, load balance, etc. Users sending `eth_sendRawTransaction` requests can have their requests forwarded directly to the Sequencer. All other RPC requests can be forwarded to replica nodes.