From: James MacWhyte <macwhyte@gmail.com>
To: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] BIP75 update & PR - Simplification
Date: Fri, 06 May 2016 23:51:58 +0000 [thread overview]
Message-ID: <CAH+Axy5Ga9twXP7ORqOHHtdejxs1CGuo1u-7TaDd_fcOfBXixQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
Hi all,
We've made some significant changes to BIP75 which we think simplify things
greatly:
Instead of introducing encrypted versions of all BIP70 messages
(EncryptedPaymentRequest, EncryptedPayment, etc), we have defined a generic
EncryptedProtocolMessage type which is essentially a wrapper that enables
encryption for all existing BIP70 messages. This reduces the number of new
messages we are defining and makes it easier to add new message types in
the future.
We've also decided to use AES-GCM instead of AES-CBC, which eliminates the
need for the verification hash.
A pull request has been submitted, which can be seen here:
https://github.com/bitcoin/bips/pull/385
All comments are welcome. Thank you!
James
[-- Attachment #2: Type: text/html, Size: 863 bytes --]
reply other threads:[~2016-05-06 23:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH+Axy5Ga9twXP7ORqOHHtdejxs1CGuo1u-7TaDd_fcOfBXixQ@mail.gmail.com \
--to=macwhyte@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox