From a0cfa89b8205f3f1ac24eb7938b4148fd484426b Mon Sep 17 00:00:00 2001 From: Orie Steele Date: Mon, 11 Dec 2023 09:26:15 -0600 Subject: [PATCH] Update draft-birkholz-scitt-scrapi.md Co-authored-by: robinbryce --- draft-birkholz-scitt-scrapi.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-birkholz-scitt-scrapi.md b/draft-birkholz-scitt-scrapi.md index c7a5a44..a0d3a5a 100644 --- a/draft-birkholz-scitt-scrapi.md +++ b/draft-birkholz-scitt-scrapi.md @@ -75,7 +75,7 @@ In order to avoid interactivity and improve interoperability, document describes a non-exclusive, but mandatory to support, confirmation scheme In this scheme the verifier's challenge is a recent unix timestamp, -and the registering party need no request this information from the transparency service. +party need not Here is an example key binding token that can be paired with the confirmation claim in a signed statement: