From 31b1cde376a5cf2464cb7cd52272f2ab44c71d9e Mon Sep 17 00:00:00 2001 From: Zsomething Date: Tue, 21 Apr 2026 13:44:20 -0600 Subject: [PATCH 1/2] edit --- book/src/design/security-properties.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/book/src/design/security-properties.md b/book/src/design/security-properties.md index a8fe77090ec..e27c2c4048e 100644 --- a/book/src/design/security-properties.md +++ b/book/src/design/security-properties.md @@ -6,7 +6,9 @@ Crosslink is designed and can be analyzed with respect to the following security Transactions enter a finalized state, and finalized transactions cannot be rolled back. Failure of this security property is called “rollback attack”. -Importantly, all participants who are sufficiently in sync with the consensus agree on finality status, or if there is a failure by the protocol to provide finality, all of those participants agree that this failure occurred. This contrasts with Proof-of-Work which provides “probabilistic finality”, which means every participant must select their own rollback threshold at which point they consider a protocol failure event to have occurred (including malicious rollback attacks). Because these thresholds vary among users, rollbacks naturally fragment users into groups with competing interests in the event of protocol failures. +Irreversible finality cannot be provided by unalloyed Proof-of-Work, which provides only “probabilistic finality“. In probabilistic finality, the protocol provides no detection or prevention of rollback attack, so detection and prevention (and remediation) are left up to the users ("the social layer"). + +Importantly, with irreversible finality, all users who are sufficiently in sync with the consensus agree on finality status, so if there is a failure by the protocol to provide finality, all of those participants agree that this failure occurred. This contrasts with probabilistic finality—in that model, every user must select their own rollback threshold at which point they consider a protocol failure event to have occurred. Because these thresholds vary among users, rollbacks fragment the users into groups with competing interests. ## _Liveness/Availability_ From ac0df239a8dec0b19062bef79d7c2a6595d6863e Mon Sep 17 00:00:00 2001 From: zookoatshieldedlabs Date: Tue, 21 Apr 2026 13:51:35 -0600 Subject: [PATCH 2/2] Update book/src/design/security-properties.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- book/src/design/security-properties.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/src/design/security-properties.md b/book/src/design/security-properties.md index e27c2c4048e..cedc1cbcaf1 100644 --- a/book/src/design/security-properties.md +++ b/book/src/design/security-properties.md @@ -6,7 +6,7 @@ Crosslink is designed and can be analyzed with respect to the following security Transactions enter a finalized state, and finalized transactions cannot be rolled back. Failure of this security property is called “rollback attack”. -Irreversible finality cannot be provided by unalloyed Proof-of-Work, which provides only “probabilistic finality“. In probabilistic finality, the protocol provides no detection or prevention of rollback attack, so detection and prevention (and remediation) are left up to the users ("the social layer"). +Irreversible finality cannot be provided by unalloyed Proof-of-Work, which provides only “probabilistic finality”. In probabilistic finality, the protocol provides no detection or prevention of rollback attacks, so detection and prevention (and remediation) are left up to the users ("the social layer"). Importantly, with irreversible finality, all users who are sufficiently in sync with the consensus agree on finality status, so if there is a failure by the protocol to provide finality, all of those participants agree that this failure occurred. This contrasts with probabilistic finality—in that model, every user must select their own rollback threshold at which point they consider a protocol failure event to have occurred. Because these thresholds vary among users, rollbacks fragment the users into groups with competing interests.