From f7e08aa1a7979cc97d4d45f9ca5d98fd6467291e Mon Sep 17 00:00:00 2001 From: Matt David Date: Thu, 28 Jul 2016 09:26:36 -0700 Subject: - Add UNKNOWN_TYPE to ProtocolMessageType enum in paymentrequest.proto and BIP75 text (based on suggestions from http://androiddevblog.com/protocol-buffers-pitfall-adding-enum-values/) - Update BIP75 Motivation and use cases to provide more color around reasoning and use of BIP75 NOTE: The BIP75 language no longer contains a description of the KYC compliance use case, as it is a single, very specific use-case that does not have any bearing on the technical specifications herein. BIP75 extends the original BIP70 Payment Protocol to become a two-way, encrypted messaging process, which can be used for a variety of reasons one of which is regulatory compliance. --- bip-0075/paymentrequest.proto | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'bip-0075') diff --git a/bip-0075/paymentrequest.proto b/bip-0075/paymentrequest.proto index 3c1ef40..caab02a 100644 --- a/bip-0075/paymentrequest.proto +++ b/bip-0075/paymentrequest.proto @@ -57,10 +57,11 @@ message InvoiceRequest { } enum ProtocolMessageType { - INVOICE_REQUEST = 0; - PAYMENT_REQUEST = 1; - PAYMENT = 2; - PAYMENT_ACK = 3; + UNKNOWN_TYPE = 0; + INVOICE_REQUEST = 1; + PAYMENT_REQUEST = 2; + PAYMENT = 3; + PAYMENT_ACK = 4; } message ProtocolMessage { -- cgit v1.2.3