edit#281
Merged
3 commits merged intoApr 21, 2026
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the Crosslink security properties documentation to clarify the distinction between irreversible finality and Proof-of-Work’s probabilistic finality.
Changes:
- Rewrote the “Irreversible Finality” section to explicitly contrast irreversible vs probabilistic finality and the role of the “social layer”.
- Split the prior long paragraph into shorter paragraphs for readability.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+9
to
+11
| 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. |
There was a problem hiding this comment.
The PR title/description are still the unfilled template (title is just "edit"), which makes it hard to validate the intent/scope of this documentation change. Please update the PR title and fill in Motivation/Solution (and Tests if applicable).
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
judah-caruso
approved these changes
Apr 21, 2026
github-merge-queue
Bot
closed this pull request by merging all changes
into
main
in
6d02a1b
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Solution
Tests
Specifications & References
Follow-up Work
PR Checklist