From 6bed6e7aa1a71695ed9cfce993bccf5ccf0f9476 Mon Sep 17 00:00:00 2001 From: Zsomething Date: Tue, 21 Apr 2026 13:23:45 -0600 Subject: [PATCH] trivial edit --- 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 69f4f5223e7..a8fe77090ec 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”. -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. +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. ## _Liveness/Availability_