Allowing a "no-RBF" flag serves only to fool new users into believing that
0-conf is more secure than it is. There is already too much confusion about
this point.
In Bitcoin was assume that miners are profit-maximizing agents, and so we
must assume that (flag or not) miners will replace transactio
While the usability of non-RBF transactions tends to be quite poor, there are
some legitimate risk-analysis-based reasons why people use them (eg to sell BTC
based on a incoming transaction which you will need to convert to fiat, which
has low cost if the transaction doesn't confirm), and if peo
On Tue, Dec 05, 2017 at 07:39:32PM +, Luke Dashjr via bitcoin-dev wrote:
> On Tuesday 05 December 2017 7:24:04 PM Sjors Provoost wrote:
> > I recently submitted a pull request that would turn on RBF by default,
> > which triggered some discussion [2]. To ease the transition for merchants
> > wh
On Dec 5, 2017 12:00 PM, "Sjors Provoost" wrote:
...
I don't think all BIPs lend themselves to this pattern. Can you think of
another example?
Not right now, just seemed like a good idea to consider making it useful
for more than one thing (maybe CT or something else could use it in the
future
CryptAxe wrote:
> 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?
I don't think all BIPs lend themselves to this pattern
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.
On Tuesday 05 December 2017 7:24:04 PM Sjors Provoost wrote:
> 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
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
