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.
Initial Commit of http-address-service BIP draftfd249cb305
Cleanup Response titles and bold HTTP response codes8905c7436d
Add links for RFCsa62ba93990
Add links for RFCs61674ca008
Removing Justin and adding Frank as co-authorfaec02cd97
- Removing bolding on next word "header"66e2d91754
Merge remote-tracking branch 'upstream/master'
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
cd9d2d37b5
Merge remote-tracking branch 'upstream/master'
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
95df420895
- 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.
f7e08aa1a7
- Replace UNKNOWN_TYPE with UNKNOWN_MESSAGE_TYPE6559767e03
Added additional pki_type valuesc7fdd9d428
Merge pull request #18 from jmacwhyte/master
Added additional pki_type values
8516e47a5e
Added versioning, cancelingac8a5f4df6
Merge pull request #19 from jmacwhyte/proofread
Added versioning, canceling
4d1949d707
- Remove working copy of http address service bip7ba8e5813a
Merge remote-tracking branch 'upstream/master'
Added:
- Versioning
- Cancellation
- 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/)
Updated:
- Additional pki_type values
- Updated status_code 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.
This is a metadata mirror of the GitHub repository
bitcoin/bips.
This site is not affiliated with GitHub.
Content is generated from a GitHub metadata backup.
generated: 2026-05-01 20:10 UTC
This site is hosted by @0xB10C More mirrored repositories can be found on mirror.b10c.me