From e41b4a6b7e41307864547cb18aeac5e55b9e5ea3 Mon Sep 17 00:00:00 2001 From: Kevin Griffin Date: Tue, 9 Apr 2024 14:39:40 -0400 Subject: [PATCH] Update spec.md (#97) --- spec/spec.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/spec/spec.md b/spec/spec.md index f8c7572..1ea8ed3 100644 --- a/spec/spec.md +++ b/spec/spec.md @@ -3108,8 +3108,6 @@ The associated expanded Attribute block is as follows: Notice that the value of the attribute, `a` field in the transaction event, matches the value of the SAID, `d` field in the expanded attribute block. Further notice that the UUID, `u` field is missing. This makes the attribute block unblinded. The Issuer may provide an API that allows a Validator to query the attributed block for any given transaction event in the registry, or knowing that it is unblinded, a Validator can try the two different state value possibilities to discover which one generates a SAID, `d` field value that matches the attribute, `a` field value in the event. -Notice that the value of the Attribute, `a` field in the transaction event, matches the value of the SAID, `d` field in the expanded Attribute block. Further notice that the UUID, `u` field is missing. This makes the Attribute block unblinded. The Issuer may provide an API that allows a Validator to query the attributed block for any given transaction event in the Registry, or knowing that its unblinded, a Validator can try the two different state value possibilities to discover which one generates a SAID, `d` field value that matches the Attribute, `a` field value in the event. - Sometime later the ACDC is revoked with the publication by the Issuer of the following event: