summaryrefslogtreecommitdiff
path: root/bip-0070.mediawiki
diff options
context:
space:
mode:
Diffstat (limited to 'bip-0070.mediawiki')
-rw-r--r--bip-0070.mediawiki15
1 files changed, 8 insertions, 7 deletions
diff --git a/bip-0070.mediawiki b/bip-0070.mediawiki
index 4666ff6..692d7f0 100644
--- a/bip-0070.mediawiki
+++ b/bip-0070.mediawiki
@@ -222,10 +222,11 @@ used.
Each certificate is a DER [ITU.X690.1994] PKIX certificate value. The
certificate containing the public key of the entity that digitally
-signed the PaymentRequest must be the first certificate. This MAY be
+signed the PaymentRequest must be the first certificate. This MUST be
followed by additional certificates, with each subsequent certificate
-being the one used to certify the previous one, up to a trusted root
-authority. The recipient must verify the certificate chain according to
+being the one used to certify the previous one, up to (but not
+including) a trusted root authority. The trusted root authority MAY be
+included. The recipient must verify the certificate chain according to
[RFC5280] and reject the PaymentRequest if any validation failure
occurs.
@@ -253,10 +254,10 @@ message with version=2. Old implementations should let the user know
that they need to upgrade their software when they get an up-version
PaymentDetails message.
-Implementations that need to extend messages in this specification
-shall use tags starting at 1000, and shall update the wiki page at
-https://en.bitcoin.it/wiki/Payment_Request to avoid conflicts with
-other extensions.
+Implementations that need to extend messages in this specification shall use
+tags starting at 1000, and shall update the
+[[bip-0070/extensions.mediawiki|extensions page]] via pull-req to avoid
+conflicts with other extensions.
==References==