[Bitcoin-development] An initial replace-by-fee implementation is now available
adam at cypherspace.org
Thu May 9 12:07:23 UTC 2013
I have to say I do not think you want to have it be random as to who gets
paid (by having conflicting double spends floating around with different
payee & change addresses all from the same sending address.)
About current defacto no replacement: it is the best bitcoin currently has,
and it has value, with it you need to do a net-split to attack eg
1-confirmation, and this proposal weakens it. Net-splits are possible but
not trivial. This proposal moves them into spec - ie free.
About privacy: I think you are going to inherently disclose which is the
change address, because you will decrease the change when you increase the
fee. There is no coin management in the client, and as far as I saw so far,
no privacy management of which coins to reduce coin cross linking. Who's to
say the client has 100s of times as many coins as the payment.
If people dont want to reveal which is change and which payment, they need
to put a big enough fee up front based on a margin over prevailing fee
It would also be better to try to get the fee right first time than to create
more traffic revising it due to experience. Though the ability to revise
the fee IFF the best effort fee doesnt work empirically after a couple of
blocks seems like a good feature. (But not with revised recipient/change
Also if the bids are too flexibly different how do you stop both bids being
processed (eg one in a block, the next in the next block).
On Thu, May 09, 2013 at 07:46:05AM -0400, Peter Todd wrote:
>On Thu, May 09, 2013 at 01:19:13PM +0200, Adam Back wrote:
>> In this thread discussing this idea
>> it is suggested that the approach risks making 0-confirm double-spends
>The patch makes the concept of a 0-confirm double-spend obsolete
>basically. The model is rather than having some vague, insecure, easily
>broken, de-facto no-replacement rule it replaces it with something very
>easy to reason about: you are bidding for blockchain space, and you can
>adjust your bid after the fact.
>The reality is zero-conf double-spends aren't that big of a problem
>because the vast majority of payments have other mechanisms they can use
>instead of relying on the defacto behavior of dozens of major miners and
>Long story short, we're better off if we don't give people a false sense
>> I dont see why this should be. Cant part of the validation of accepting a
>> fee revision be that every aspct of the revision except the reward must be
>> unchanged, otherwise the revision is considered invalid and discarded?
>A node has no idea which transaction output is change and which one
>isn't; if nodes could distinguish change from payment your privacy would
>be badly violated.
>By allowing simple replacement without further rules the fee adjustment
>process can go on as long as required, without you running out of
>additional transaction inputs and without causing the transaction to get
>bigger and bigger each time.
>It also allows more interesting use cases, like adding additional
>outputs to a transaction after the fact as more payees become known, or
>if two unrelated parties decide to combine their transactions to save on
>blockchain space and preserve their privacy.
>Eventually the P2P protocol can have delta compression support, so the
>network bandwidth required to merge two transactions into one will be
More information about the bitcoin-dev