From 4d4f9578995a29c2719540062630f4921ec78b46 Mon Sep 17 00:00:00 2001 From: Fraser Hutchison Date: Tue, 28 May 2024 22:36:07 +0100 Subject: [PATCH] minor update to relayer description --- docs/overview/components/relayer.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/overview/components/relayer.md b/docs/overview/components/relayer.md index 0470e86..e37a49f 100644 --- a/docs/overview/components/relayer.md +++ b/docs/overview/components/relayer.md @@ -1,12 +1,12 @@ # Relayer -The Relayer's responsibility is to take validated blocks from the sequencer and -pass them along to both the Conductor and the DA layer. Because the sequencer's -block times are much faster than those of the DA, the relayer also collects a -queue of ordered sequencer blocks before wrapping them for submission to DA. +The relayer's responsibility is to fetch validated blocks from the sequencer and +pass them along to the DA layer. Because the sequencer's block times are much +faster than those of the DA, the relayer batches the ordered data from multiple +sequencer blocks before compressing it and submitting it to the DA. -The individual sequencer blocks are sent immediately to the Conductor to enable -fast finality for an improved UX and also act as soft commits for the execution -layer. The collections of blocks sent to the DA layer are used as a source of -truth and are ultimately pulled from the DA to be used as firm commits for -finality in the rolllups. +The individual sequencer blocks can also be fetched by the Conductor before the +relayer has submitted them to the DA. This enables fast finality for an improved +UX, acting as soft commits for the execution layer. The collections of data sent +to the DA layer by the relayer are used as a source of truth and are ultimately +pulled from the DA to be used as firm commits for finality in the rollups.