From: CryptAxe <cryptaxe@gmail•com>
To: Sjors Provoost <sjors@sprovoost•nl>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Cc: Matt Corallo <matt@chaincode•com>
Subject: Re: [bitcoin-dev] BIP-21 amendment proposal: -no125
Date: Tue, 5 Dec 2017 11:40:42 -0800 [thread overview]
Message-ID: <CAF5CFkhwj5BHPndasvX5zYzmVwOF09XxzZo8hQO_f_1L3Vc+cg@mail.gmail.com> (raw)
In-Reply-To: <AE14915B-37DF-4D94-A0B1-E32A26903807@sprovoost.nl>
[-- Attachment #1: Type: text/plain, Size: 1927 bytes --]
Perhaps instead of a flag that can be used to disable a specific operation,
there should be a "-ignoredflags=x,y,z" section of the URI that can be used
to ignore whatever BIP this might also be useful for in the future?
On Dec 5, 2017 11:34 AM, "Sjors Provoost via bitcoin-dev" <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> One way to reduce fees is to encourage usage of Replace-By-Fee, BIP 125
> [0]. It allows wallets to recommend lower fees, because if a transaction
> gets stuck due to underestimation, the fee can easily be bumped.
>
> Bitcoin Core has had support for RBF for a while, and as of v0.15.0
> recommends lower fees [1] when the user chooses to use RBF.
>
> I recently submitted a pull request that would turn on RBF by default,
> which triggered some discussion [2]. To ease the transition for merchants
> who are reluctant to see their customers use RBF, Matt Corallo suggested
> that wallets honor a no125=1 flag.
>
> So a BIP-21 URI would look like this: bitcoin:175t...45W?amount=20.
> 3&no125=1
>
> When this flag is set, wallets should not use RBF, regardless of their
> default, unless the user explicitly overrides the merchant's preference.
>
> Afaik adding this flag won't break existing BIP-21 support. It doesn't use
> the req- prefix, because it's optional. I'm also not aware of any ad hoc
> standards that use no125 in BIP-21-ish URIs.
>
> - Sjors
>
> P.S. I'd similarly suggest adding a bech32 param, but that's for another
> discussion
>
> [0] https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki
> [1] https://bitcoincore.org/en/2017/09/01/release-0.15.0/#
> better-fee-estimates
> [2] https://github.com/bitcoin/bitcoin/pull/11605
> [3] https://github.com/bitcoin/bitcoin/issues/11828
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
[-- Attachment #2: Type: text/html, Size: 3013 bytes --]
prev parent reply other threads:[~2017-12-05 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 19:24 Sjors Provoost
2017-12-05 19:39 ` Luke Dashjr
2017-12-05 20:00 ` Sjors Provoost
2017-12-05 20:06 ` CryptAxe
2017-12-11 18:19 ` Peter Todd
2017-12-23 16:25 ` Matt Corallo
2017-12-23 18:33 ` Paul Iverson
2017-12-05 19:40 ` CryptAxe [this message]
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=CAF5CFkhwj5BHPndasvX5zYzmVwOF09XxzZo8hQO_f_1L3Vc+cg@mail.gmail.com \
--to=cryptaxe@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=matt@chaincode$(echo .)com \
--cc=sjors@sprovoost$(echo .)nl \
/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