Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YS9cA-0001cD-LY for bitcoin-development@lists.sourceforge.net; Sun, 01 Mar 2015 19:33:22 +0000 X-ACL-Warn: Received: from mail-ob0-f181.google.com ([209.85.214.181]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YS9c8-0008Kw-NB for bitcoin-development@lists.sourceforge.net; Sun, 01 Mar 2015 19:33:22 +0000 Received: by mail-ob0-f181.google.com with SMTP id vb8so27404748obc.12 for ; Sun, 01 Mar 2015 11:33:15 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=mCA4KjRSOn6Ta/HA/JXmEE0yBW8XK/CgsfrWBPUFBNA=; b=Xh3dz4LU97vxJYhAp0ZFW94bc9V4FE83UsdExy7AvJASn6eyNw46mGmFxSl3LO+C1J SpljQdP9I9as1Fj71TCPag09bSVS/wr9OKTmHs8IEVyfWde9YCKqlLmmAEAq1Znpy4S/ shtJPGshmO5rU8+A1AwcwAJ1KgHEgvTp2EpUs4knXUo2CfFwzQ9XlCaXyuPH7TXjk7LG e8pck7WaucQLa52djceCIneXgv13DCmxw2dyrHebs+BGYU7S2Q77lgrn8E9qeEznIi6t YubVHck8WKzbkFbdG7J/f66bWYJlCeYXLb9v6EglVoY4Pvec/M81Lh8CKvUA1wFS8e/W 9JcA== X-Gm-Message-State: ALoCoQmyLPV+Hwb4ThqXBzlevUnH3CtPAwtUjqgpMMTRJHEkakVq7oHRZeFALa0RjwYFFnFc+Hzi X-Received: by 10.202.195.68 with SMTP id t65mr15705339oif.105.1425236779813; Sun, 01 Mar 2015 11:06:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.79.137 with HTTP; Sun, 1 Mar 2015 11:05:39 -0800 (PST) X-Originating-IP: [202.56.47.34] In-Reply-To: <20150301175950.GV14804@nl.grid.coop> References: <20150215212512.GR14804@nl.grid.coop> <54E11248.6090401@gmail.com> <20150219085604.GT14804@nl.grid.coop> <20150301175950.GV14804@nl.grid.coop> From: Neil Fincham Date: Mon, 2 Mar 2015 08:05:39 +1300 Message-ID: To: Troy Benjegerdes Content-Type: multipart/alternative; boundary=001a11c17b98fb635d05103ecb84 X-Spam-Score: 2.9 (++) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.9 FUZZY_AMBIEN BODY: Attempt to obfuscate words in spam 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1YS9c8-0008Kw-NB Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] replace-by-fee v0.10.0rc4 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Mar 2015 19:33:22 -0000 --001a11c17b98fb635d05103ecb84 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > Seems like a good deal, what am I missing? The disruption caused to every other user or the bitcoin network. Transactions unconfirmed, history is rewritten, the poor Byzantine General who sent his soldiers off to battle finds out that his scouts have been paid to change their reports. Neil On 2 March 2015 at 06:59, Troy Benjegerdes wrote: > So let's play this out a little.. Let's call it "Solomon's spend[1]" > > Exchange gets hacked, bitcoins move. > > The exchange has a contract with an insurance company and miners for > 'scorched earth' theft response that creates a double-spend of the > original transaction. > > So now there's a 10,000 bitcoin incentive for miners to roll back the > chain and start (re)mining the block where the theft occurred. > > The exchange gets an insurance payout, some miner wins the lottery, and > the thief gets nothing. Seems like a good deal, what am I missing? > > [1] http://en.wikipedia.org/wiki/Judgment_of_Solomon > > On Sun, Feb 22, 2015 at 04:06:13AM -0800, Eric Lombrozo wrote: > > I should note that my proposal does require a change to the consensus > > rules...but getting bitcoin to scale will require this no matter what. > > > > - Eric Lombrozo > > On Feb 22, 2015 3:41 AM, "Eric Lombrozo" wrote: > > > > > It seems to me we're confusing two completely different motivations f= or > > > double-spending. One is the ability to replace a fee, the other is th= e > > > ability to replace outputs. > > > > > > If the double-spend were to merely add or remove inputs (but keep at > least > > > one input in common, of course), it seems fairly safe to assume it's > the > > > former, a genuine fee replacement. Even allowing for things like > coinjoin, > > > none of the payees would really care either way. > > > > > > Conversely, if at least one of the inputs were kept but none of the > > > outputs were, we can be confident it's the the latter. > > > > > > It is possible to build a wallet that always does the former when doi= ng > > > fee replacement by using another transaction to create an output with > > > exactly the additional desired fee. > > > > > > If we can clearly distinguish these two cases then the fee replacemen= t > > > case can be handled by relaying both and letting miners pick one or t= he > > > other while the output replacement case could be handled by rewarding > > > everything to a miner (essentially all outputs are voided...made > > > unredeemable...and all inputs are added to coinbase) if the miner > includes > > > the two conflicting transactions in the same block. > > > > > > Wouldn't this essentially solve the problem? > > > > > > - Eric Lombrozo > > > On Feb 21, 2015 8:09 PM, "Jeff Garzik" wrote: > > > > > >> On Sat, Feb 21, 2015 at 10:25 PM, Jorge Tim=C3=B3n > wrote: > > >> > On Sat, Feb 21, 2015 at 11:47 PM, Jeff Garzik > > >> 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, negati= ve > > >> >> 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 ceasin= g > > >> the "maintaining [of] first seen policies" alone is simply not a > > >> realistic option. The negative impact to today's userbase would be > > >> huge. > > >> > > >> Instant payments need a security upgrade, yes. > > >> > > >> -- > > >> Jeff Garzik > > >> Bitcoin core developer and open source evangelist > > >> BitPay, Inc. https://bitpay.com/ > > >> > > >> > > >> > -------------------------------------------------------------------------= ----- > > >> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > > >> from Actuate! Instantly Supercharge Your Business Reports and > Dashboards > > >> with Interactivity, Sharing, Native Excel Exports, App Integration & > more > > >> Get technology previously reserved for billion-dollar corporations, > FREE > > >> > > >> > http://pubads.g.doubleclick.net/gampad/clk?id=3D190641631&iu=3D/4140/ostg= .clktrk > > >> _______________________________________________ > > >> Bitcoin-development mailing list > > >> Bitcoin-development@lists.sourceforge.net > > >> https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > >> > > > > > > > -------------------------------------------------------------------------= ----- > > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > > from Actuate! Instantly Supercharge Your Business Reports and Dashboard= s > > with Interactivity, Sharing, Native Excel Exports, App Integration & mo= re > > Get technology previously reserved for billion-dollar corporations, FRE= E > > > http://pubads.g.doubleclick.net/gampad/clk?id=3D190641631&iu=3D/4140/ostg= .clktrk > > > _______________________________________________ > > Bitcoin-development mailing list > > Bitcoin-development@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > > -- > > -------------------------------------------------------------------------= --- > Troy Benjegerdes 'da hozer' > hozer@hozed.org > 7 elements earth::water::air::fire::mind::spirit::soul > grid.coop > > Never pick a fight with someone who buys ink by the barrel, > nor try buy a hacker who makes money by the megahash > > > > -------------------------------------------------------------------------= ----- > Dive into the World of Parallel Programming The Go Parallel Website, > sponsored > by Intel and developed in partnership with Slashdot Media, is your hub fo= r > all > things parallel software development, from weekly thought leadership blog= s > to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --001a11c17b98fb635d05103ecb84 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
>=C2=A0See= ms like a good deal, what am I missing?

The disruption caused to every other user or the bitcoin netwo= rk.=C2=A0 Transactions=C2=A0unconfirmed, history is rewritten, the poor=C2= =A0Byzantine General who sent his=C2=A0soldiers=C2=A0off to battle finds ou= t that his scouts have been paid to change their reports.
=
Neil

On 2 March 2015 at 06:59, Troy B= enjegerdes <hozer@hozed.org> wrote:
So let's play this out a little.. Let's call it "Solo= mon's spend[1]"

Exchange gets hacked, bitcoins move.

The exchange has a contract with an insurance company and miners for
'scorched earth' theft response that creates a double-spend of the<= br> original transaction.

So now there's a 10,000 bitcoin incentive for miners to roll back the chain and start (re)mining the block where the theft occurred.

The exchange gets an insurance payout, some miner wins the lottery, and
the thief gets nothing. Seems like a good deal, what am I missing?

[1] http://en.wikipedia.org/wiki/Judgment_of_Solomon

On Sun, Feb 22, 2015 at 04:06:13AM -0800, Eric Lombrozo wrote:
> I should note that my proposal does require a change to the consensus<= br> > rules...but getting bitcoin to scale will require this no matter what.=
>
> - Eric Lombrozo
> On Feb 22, 2015 3:41 AM, "Eric Lombrozo" <elombrozo@gmail.com> wrote:
>
> > It seems to me we're confusing two completely different motiv= ations for
> > double-spending. One is the ability to replace a fee, the other i= s the
> > ability to replace outputs.
> >
> > If the double-spend were to merely add or remove inputs (but keep= at least
> > one input in common, of course), it seems fairly safe to assume i= t's the
> > former, a genuine fee replacement. Even allowing for things like = coinjoin,
> > none of the payees would really care either way.
> >
> > Conversely, if at least one of the inputs were kept but none of t= he
> > outputs were, we can be confident it's the the latter.
> >
> > It is possible to build a wallet that always does the former when= doing
> > fee replacement by using another transaction to create an output = with
> > exactly the additional desired fee.
> >
> > If we can clearly distinguish these two cases then the fee replac= ement
> > case can be handled by relaying both and letting miners pick one = or the
> > other while the output replacement case could be handled by rewar= ding
> > everything to a miner (essentially all outputs are voided...made<= br> > > unredeemable...and all inputs are added to coinbase) if the miner= includes
> > the two conflicting transactions in the same block.
> >
> > Wouldn't this essentially solve the problem?
> >
> > - Eric Lombrozo
> > On Feb 21, 2015 8:09 PM, "Jeff Garzik" <jgarzik@bitpay.com> wrote:
> >
> >> On Sat, Feb 21, 2015 at 10:25 PM, Jorge Tim=C3=B3n <jtimon= @jtimon.cc> wrote:
> >> > On Sat, Feb 21, 2015 at 11:47 PM, Jeff Garzik <jgarzik@bitpay.com>
> >> wrote:
> >> >> This isn't some theoretical exercise.=C2=A0 Like= it or not many use
> >> >> insecure 0-conf transactions for rapid payments.=C2= =A0 Deploying something
> >> >> that makes 0-conf transactions unusable would have a= wide, negative
> >> >> impact on present day bitcoin payments, thus "s= corched earth"
> >>
> >> > And maybe by maintaining first seen policies we're h= arming 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 plat= itude.
> >> Widely used 0-conf payments are where we're at today.=C2= =A0 Simply ceasing
> >> the "maintaining [of] first seen policies" alone is= simply not a
> >> realistic option.=C2=A0 The negative impact to today's us= erbase would be
> >> huge.
> >>
> >> Instant payments need a security upgrade, yes.
> >>
> >> --
> >> Jeff Garzik
> >> Bitcoin core developer and open source evangelist
> >> BitPay, Inc.=C2=A0 =C2=A0 =C2=A0 https://bitpay.com/
> >>
> >>
> >> -------------------------------------------------------------= -----------------
> >> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Se= rver
> >> from Actuate! Instantly Supercharge Your Business Reports and= Dashboards
> >> with Interactivity, Sharing, Native Excel Exports, App Integr= ation & more
> >> Get technology previously reserved for billion-dollar corpora= tions, FREE
> >>
> >> http://pubads.g.doubl= eclick.net/gampad/clk?id=3D190641631&iu=3D/4140/ostg.clktrk
> >> _______________________________________________
> >> Bitcoin-development mailing list
> >> = Bitcoin-development@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listi= nfo/bitcoin-development
> >>
> >

> ----------------------------------------------------------------------= --------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboar= ds
> with Interactivity, Sharing, Native Excel Exports, App Integration &am= p; more
> Get technology previously reserved for billion-dollar corporations, FR= EE
> http://pubads.g.doubleclick.ne= t/gampad/clk?id=3D190641631&iu=3D/4140/ostg.clktrk

> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-d= evelopment@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitco= in-development


--
---------------------------------------------------------------------------= -
Troy Benjegerdes=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0'da hozer'=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 hozer@hozed.org
7 elements=C2=A0 =C2=A0 =C2=A0 earth::water::air::fire::mind::spirit::soul= =C2=A0 =C2=A0 =C2=A0 =C2=A0 = grid.coop

=C2=A0 =C2=A0 =C2=A0 Never pick a fight with someone who buys ink by the ba= rrel,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0nor try buy a hacker who makes money by t= he megahash


--------------------------------------------------------------------= ----------
Dive into the World of Parallel Programming The Go Parallel Website, sponso= red
by Intel and developed in partnership with Slashd= ot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs = to
news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
____________________________= ___________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--001a11c17b98fb635d05103ecb84--