From 128d79ed93d507ef6554b8b9d399af58a4ed41a6 Mon Sep 17 00:00:00 2001 From: LHerskind Date: Mon, 4 Mar 2024 14:21:36 +0000 Subject: [PATCH] chore: address comment --- yellow-paper/docs/data-publication-and-availability/index.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/yellow-paper/docs/data-publication-and-availability/index.md b/yellow-paper/docs/data-publication-and-availability/index.md index 7cd820d5c291..4342a4ee1b42 100644 --- a/yellow-paper/docs/data-publication-and-availability/index.md +++ b/yellow-paper/docs/data-publication-and-availability/index.md @@ -95,7 +95,8 @@ You could say that the transactions are pre-confirmed until they convince the va If there is no explicit consensus for the Rollup, staking can still be utilized for leader selection, picking a distinct sequencer which will have a period to propose a block and convince the validating light-client. The user can as earlier define his own confirmation rules and could decide that if the sequencer acknowledge his transaction, then he sees it as confirmed. -This can be done fully on trust, of with some signed message the user could take to the host and "slash" the sequencer for not upholding his part of the deal. +This have a weaker guarantees than the consensus based as the sequencer could be malicious and not uphold his part of the deal. +Nevertheless, the user could always do an out of protocol agreement with the sequencer, where the sequencer guarantees that he will include the transaction or the user will be able to slash him and get compensated. :::info Fernet Fernet lives in this category if you have a single sequencer active from the proposal to proof inclusion stage.