summaryrefslogtreecommitdiff
path: root/bip-0075
diff options
context:
space:
mode:
authorMatt David <matt@netki.com>2016-07-28 09:26:36 -0700
committerMatt David <matt@netki.com>2016-07-28 09:26:36 -0700
commitf7e08aa1a7979cc97d4d45f9ca5d98fd6467291e (patch)
treea3de1bb55c415e14c74b94f21382eff02080dd4f /bip-0075
parent95df420895879920114c48771b6473aedf9837da (diff)
downloadbips-f7e08aa1a7979cc97d4d45f9ca5d98fd6467291e.tar.xz
- 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.
Diffstat (limited to 'bip-0075')
-rw-r--r--bip-0075/paymentrequest.proto9
1 files changed, 5 insertions, 4 deletions
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 {