From 612d8a66ef28b0b603a7b049f08e04cb85016695 Mon Sep 17 00:00:00 2001 From: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> Date: Tue, 11 Dec 2018 10:12:52 +0000 Subject: [PATCH] Update proposals/1442-state-resolution.md Co-Authored-By: erikjohnston --- proposals/1442-state-resolution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/1442-state-resolution.md b/proposals/1442-state-resolution.md index 891b11fc..8eca1c9f 100644 --- a/proposals/1442-state-resolution.md +++ b/proposals/1442-state-resolution.md @@ -473,7 +473,7 @@ Intuitively using rejected events feels dangerous, however: duplicated event would then pass the auth checks. Ignoring rejected events would therefore not eliminate any potential attack vectors. -We specifically don't use rejected auth events in the iterative auth checks, as +Rejected auth events are deliberately excluded from use in the iterative auth checks, as in that case the auth events aren't re-authed like the rest of the events in the list.