[Bitcoin-development] replace-by-fee v0.10.0rc4
jgarzik at bitpay.com
Sun Feb 22 04:06:18 UTC 2015
On Sat, Feb 21, 2015 at 10:25 PM, Jorge Timón <jtimon at jtimon.cc> wrote:
> On Sat, Feb 21, 2015 at 11:47 PM, Jeff Garzik <jgarzik at bitpay.com> wrote:
>> This isn't some theoretical exercise. Like it or not many use
>> insecure 0-conf transactions for rapid payments. Deploying something
>> that makes 0-conf transactions unusable would have a wide, negative
>> impact on present day bitcoin payments, thus "scorched earth"
> And maybe by maintaining first seen policies we're harming the system
> in the long term by encouraging people to widely deploy systems based
> on extremely weak assumptions.
Lacking a coded, reviewed alternative, that's only a platitude.
Widely used 0-conf payments are where we're at today. Simply ceasing
the "maintaining [of] first seen policies" alone is simply not a
realistic option. The negative impact to today's userbase would be
Instant payments need a security upgrade, yes.
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
More information about the bitcoin-dev