From: Gregory Maxwell <gmaxwell@gmail•com>
To: Tom Harding <tomh@thinlink•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] First-Seen-Safe Replace-by-Fee
Date: Tue, 26 May 2015 23:11:17 +0000 [thread overview]
Message-ID: <CAAS2fgRDF-p3-4CruCXkNtV3tDTQLUx3x+Dq7WN7WnQJdBtu3A@mail.gmail.com> (raw)
In-Reply-To: <5564FAF1.1050907@thinlink.com>
On Tue, May 26, 2015 at 11:00 PM, Tom Harding <tomh@thinlink•com> wrote:
> The bitcoin transaction is part of a real-world "deal" with unknown
> connections to the other parts
I'm having a hard time parsing this. You might as well say that its
part of a weeblix for how informative it is, since you've not defined
it.
> not the case if paying parties are kicked out of the deal, and possibly
> don't learn about it right away.
The signatures of a transaction can always be changed any any time,
including by the miner, as they're not signed.
> A subset of parties to an Armory simulfunding transaction (an actual
> multi-input use case) could replace one signer's input after they broadcast
> it.
They can already do this.
> Maybe the
> receiver cares where he is paid from or is basing a subsequent decision on
> it. Maybe a new output is being added, whose presence makes the transaction
> less likely to be confirmed quickly, with that speed affecting the business.
The RBF behavior always moves in the direction of more prefered or
otherwise the node would not switch to the replacement. Petertodd
should perhaps make that more clear.
But your "maybe"s are what I was asking you to clarify. You said it
wasn't hard to imagine; so I was asking for specific clarification.
> With Kalle's Proof of Payment proposed standard, one payer in a two-input
> transaction could decide to boot the other, and claim the concert tickets
> all for himself. The fact that he pays is not the only consideration in the
> real world -- what if these are the last 2 tickets?
They can already do that.
> I'd argue that changing how an input is signed doesn't change the deal. For
> example if a different 2 of 3 multisig participants sign, those 3 people
> gave up that level of control when they created the multisig.
Then why do you not argue that changing the input set does not change
the weeblix?
Why is one case of writing out a participant different that the other
case of writing out a participant?
> Replacement is new - we have a choice what kind of warnings we need to give
> to signers of multi-input transactions. IMHO we should avoid needing a
> stronger warning than is already needed for 0-conf.
How could a _stronger_ warning be required?
next prev parent reply other threads:[~2015-05-26 23:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 5:13 Peter Todd
2015-05-26 17:54 ` Tom Harding
2015-05-26 19:10 ` Gregory Maxwell
2015-05-26 23:00 ` Tom Harding
2015-05-26 23:11 ` Gregory Maxwell [this message]
2015-05-26 23:42 ` Tom Harding
2015-05-26 21:20 ` Danny Thorpe
2015-05-26 21:27 ` Pieter Wuille
2015-05-26 22:09 ` Danny Thorpe
2015-05-26 22:18 ` Adam Back
2015-05-27 7:30 ` Peter Todd
2015-06-10 9:10 ` [Bitcoin-development] First-Seen-Safe Replace-by-Fee patch against Bitcoin Core v0.10.2 Peter Todd
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=CAAS2fgRDF-p3-4CruCXkNtV3tDTQLUx3x+Dq7WN7WnQJdBtu3A@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=tomh@thinlink$(echo .)com \
/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