From 5b9d8a4ae73c7523f79c7cc177272b394a294cf1 Mon Sep 17 00:00:00 2001 From: trbouma Date: Wed, 24 Apr 2024 16:43:05 -0400 Subject: [PATCH] edit --- 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 0b294be0..4968fe79 100644 --- a/05-signed-metadata.md +++ b/05-signed-metadata.md @@ -27,7 +27,7 @@ The metadata element array format is depicted below: ["MANDATORY kind 0 metadata format", "OPTIONAL signature", "OPTIONAL pubkey"] ``` -* A MANDATORY first array element is MANDATORY and consists of a JSON stringified metadata consistent with ```kind 0```. `0`: **metadata**: the JSON stringified metadata content `{name: , about: , picture: }` consisting of the desired information. +* A MANDATORY first array element consists of a JSON stringified metadata consistent with ```kind 0```. `0`: **metadata**: the JSON stringified metadata content `{name: , about: , picture: }` consisting of the desired information. * An OPTIONAL second array element which is a JSON signature of the first array element. By default, the ```pubkey``` used to verify this signature is the pubkey that corresponds to value related to the ```name``` key. * An OPTIONAL third array element can be specified, if the pubkey used to verify the signature is other than the ```name```. This is for the use case where the metadata by signed by a party other than the named user - such as the NIP-05 provider, or another relevant authority.