From 373b4f0423d00716505b47a6ea4486b9416fa58a Mon Sep 17 00:00:00 2001 From: trbouma Date: Wed, 24 Apr 2024 16:38:12 -0400 Subject: [PATCH] typo --- 05-signed-metadata.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/05-signed-metadata.md b/05-signed-metadata.md index 2f5e66b6..637c68dc 100644 --- a/05-signed-metadata.md +++ b/05-signed-metadata.md @@ -12,7 +12,7 @@ This NIP proposes the addtion of ```"metadata"``` to the nip-05 response to prov ## Rationale -The value of this NIP is that it extends the capability of a NIP-05 identifier to present unsigned or signed (verifiable) credentials about itself, or about the controller of the identifier. For example, a NIP-05 identifier such as ```bob@example.com``` can express a signed statement that Bob is indeed a professional engineer. This capability enables a NIP-05 identifier express trusted (signed) statements that can be presented as such in a client, where indication is required. +The value of this NIP is that it extends the capability of a NIP-05 identifier to present unsigned or signed (verifiable) credentials about itself, or about the controller of the identifier. For example, a NIP-05 identifier such as ```bob@example.com``` can express a signed statement that Bob is indeed a professional engineer. This capability enables a NIP-05 identifier to express trusted (signed) statements that can be presented as such in a client, where indication is required. ## Theory and Approach