From: James MacWhyte <macwhyte@gmail•com>
To: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] BIP75 - Out of Band Address Exchange
Date: Thu, 10 Mar 2016 21:43:29 +0000 [thread overview]
Message-ID: <CAH+Axy6WVtb8Eib0aqS4Pp=zpjnsrDBbWRMmmBrJOZ3rFQAXww@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
Hi everyone,
Our BIP (officially proposed on March 1) has tentatively been assigned
number 75. Also, the title has been changed to "Out of Band Address
Exchange using Payment Protocol Encryption" to be more accurate.
We thought it would be good to take this opportunity to add some optional
fields to the BIP70 paymentDetails message. The new fields are:
subtractable fee (give permission to the sender to use some of the
requested amount towards the transaction fee), fee per kb (the minimum fee
required to be accepted as zeroconf), and replace by fee (whether or not a
transaction with the RBF flag will be accepted with zeroconf). I know it
doesn't make much sense for merchants to accept RBF with zeroconf, so that
last one might be used more to explicitly refuse RBF transactions (and
allow the automation of choosing a setting based on who you are transacting
with).
I see BIP75 as a general modernization of BIP70, so I think it should be
fine to include these extensions in the new BIP, even though these fields
are not specific to the features we are proposing. Please take a look at
the relevant section and let me know if anyone has any concerns:
https://github.com/techguy613/bips/blob/master/bip-0075.mediawiki#Extending_BIP70_PaymentDetails
The BIP70 extensions page in our fork has also been updated.
Thanks!
James
[-- Attachment #2: Type: text/html, Size: 1594 bytes --]
next reply other threads:[~2016-03-10 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 21:43 James MacWhyte [this message]
2016-03-11 11:54 ` Andreas Schildbach
2016-03-11 19:32 ` James MacWhyte
2016-03-12 14:40 ` Andreas Schildbach
2016-03-11 22:43 ` Justin Newton
2016-03-12 15:00 ` Andreas Schildbach
2016-03-17 1:23 ` James MacWhyte
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+Axy6WVtb8Eib0aqS4Pp=zpjnsrDBbWRMmmBrJOZ3rFQAXww@mail.gmail.com' \
--to=macwhyte@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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