From 73c6cc4576ef235b2f6a97f53f0643cf1c158a03 Mon Sep 17 00:00:00 2001 From: Rob Riddle Date: Thu, 1 Mar 2018 16:31:30 -0500 Subject: [PATCH 1/2] Update with information about inputs --- bip70.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/bip70.md b/bip70.md index e8642f1..477e3be 100644 --- a/bip70.md +++ b/bip70.md @@ -1,11 +1,11 @@ # BIP-70 Modifications In addition to JSON payment protocol, BitPay Bitcoin and Bitcoin Cash invoices use a mildly modified version of [BIP-70](https://github.com/bitcoin/bips/blob/master/bip-0070.mediawiki). We include -one additional field which specifies the fee rate the transaction must have in order to be accepted. Bitcoin invoices are temporarily exempt from this rule to allow wallets time to adjust. +one additional field which specifies the fee rate the transaction must have in order to be accepted. This minimum fee is required to ensure a reasonable confirmation time for payments which are sent to BitPay. +To further ensure this we also require payments be made with confirmed inputs. Payments using unconfirmed inputs, such as unconfirmed change, will be rejected. Bitcoin invoices are temporarily exempt from this rule to allow wallets time to adjust. * `required_fee_rate` - The minimum fee per byte required on your transaction. Bitcoin Cash payments will be rejected if fee rate included for the transaction is not at least this value. _May be fractional value_ ie 0.123 sat/byte - ## Application Logic Please note that you should **NOT** broadcast a payment to the P2P network if we respond with an http status code other than `200`. Broadcasting a payment before getting a success notification back from the server will -lead to a failed payment for the sender. The sender will bear the cost of paying transaction fees yet again to get their money back. \ No newline at end of file +lead to a failed payment for the sender. The sender will bear the cost of paying transaction fees yet again to get their money back. From 353210bd8a57b6e726c7d420b5657084c9dd13c9 Mon Sep 17 00:00:00 2001 From: Rob Riddle Date: Thu, 1 Mar 2018 16:34:57 -0500 Subject: [PATCH 2/2] Fix wording --- bip70.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bip70.md b/bip70.md index 477e3be..241c86c 100644 --- a/bip70.md +++ b/bip70.md @@ -2,7 +2,7 @@ In addition to JSON payment protocol, BitPay Bitcoin and Bitcoin Cash invoices use a mildly modified version of [BIP-70](https://github.com/bitcoin/bips/blob/master/bip-0070.mediawiki). We include one additional field which specifies the fee rate the transaction must have in order to be accepted. This minimum fee is required to ensure a reasonable confirmation time for payments which are sent to BitPay. -To further ensure this we also require payments be made with confirmed inputs. Payments using unconfirmed inputs, such as unconfirmed change, will be rejected. Bitcoin invoices are temporarily exempt from this rule to allow wallets time to adjust. +To further ensure this we also require payments be made with confirmed inputs. Payments using unconfirmed inputs, such as unconfirmed change, will be rejected. Bitcoin (BTC) invoices are temporarily exempt from these rules to allow wallets time to adjust. * `required_fee_rate` - The minimum fee per byte required on your transaction. Bitcoin Cash payments will be rejected if fee rate included for the transaction is not at least this value. _May be fractional value_ ie 0.123 sat/byte