Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Brad implementers guide revisions 2 #6239

Merged
eskimor merged 5 commits into from
Nov 11, 2022
+33 −29
Merged

Brad implementers guide revisions 2 #6239

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
07f413b
Add disputes subsystems fix
BradleyOlson64 Oct 18, 2022
6d28b3c
Updated dispute approval vote import reasoning
BradleyOlson64 Nov 6, 2022
e325f1d
Improved wording of my changes
BradleyOlson64 Nov 6, 2022
00eb4d0
Resolving issues brought up in comments
BradleyOlson64 Nov 11, 2022
ee4787b
Merge branch 'master' of https://github.com/paritytech/polkadot into …
BradleyOlson64 Nov 11, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Improved wording of my changes
  • Loading branch information
@BradleyOlson64
BradleyOlson64 committed Nov 6, 2022
commit e325f1d28637cd474789cd6bdfa033f45deadba0
2 changes: 1 addition & 1 deletion roadmap/implementers-guide/src/node/disputes/dispute-coordinator.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ section.
While there is no need to record approval votes in the dispute coordinator
preemptively, we do need to make sure they are recorded when a dispute
actually happens. This is because only votes recorded by the dispute
coordinator will be considered for slashing. It was decided sufficient to our
coordinator will be considered for slashing. It is sufficient for our
threat model that malicious backers are slashed as opposed to both backers and
approval checkers. However, we still must import approval votes from the approvals
process into the disputes process to ensure that lazy approval checkers
Expand Down