From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UedQI-0001pz-2S for bitcoin-development@lists.sourceforge.net; Tue, 21 May 2013 03:39:38 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of robbak.com designates 209.85.128.181 as permitted sender) client-ip=209.85.128.181; envelope-from=robbak@robbak.com; helo=mail-ve0-f181.google.com; Received: from mail-ve0-f181.google.com ([209.85.128.181]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UedQG-0003ku-RK for bitcoin-development@lists.sourceforge.net; Tue, 21 May 2013 03:39:38 +0000 Received: by mail-ve0-f181.google.com with SMTP id pb11so88549veb.26 for ; Mon, 20 May 2013 20:39:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=LtFpI/gVy1CS7vV5IjWmM/lyCzRbUFaVZZy87bWUsyw=; b=KKPnAHBjcTA6IVq+I2oLkS1gpzGhkl8Ttk9LskegmgUSpTRMWPaqWdcrvSllx2zdSH 684JMYxVKSSdlmei+Ue69MkdR68K9oP5ZX8zKKqnv9D9pk9XDd/v+aCksYHBbbYkDPdx yyiOeXYR+BmQ1A0cnSBw15t5MNXk3HwXqz5jObUYJS5rv/V+cRrQGXJrca9NVeZxhOkO EEJLa1W/g+eCyiwvzH39cWBQtNf3ycnHcO2RUjR4vxxWlKDmMAE+RnP0PZl4mOu4PjZI TlXQZV8xz7Xp0eOoyQqqoJNWwy+xJXN/AwMsMOWOns/eLxXQueaGnX244ULL2zjOImip DI0g== MIME-Version: 1.0 X-Received: by 10.58.75.46 with SMTP id z14mr144267vev.52.1369107571058; Mon, 20 May 2013 20:39:31 -0700 (PDT) Received: by 10.52.88.172 with HTTP; Mon, 20 May 2013 20:39:30 -0700 (PDT) In-Reply-To: References: <519AC3A8.1020306@quinnharris.me> Date: Tue, 21 May 2013 13:39:30 +1000 Message-ID: From: Robert Backhaus To: Bitcoin Dev Content-Type: multipart/alternative; boundary=089e01228e426eebe904dd32325a X-Gm-Message-State: ALoCoQn6T+/ryEQjBipIKbyoqW5kAtULSiJBeqUGFYnHHRuedpvkDKi/LsUy+Q4zVT++/hItm+ZL X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1UedQG-0003ku-RK Subject: Re: [Bitcoin-development] Double Spend Notification 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: Tue, 21 May 2013 03:39:38 -0000 --089e01228e426eebe904dd32325a Content-Type: text/plain; charset=ISO-8859-1 That's good - what I had taken away from the replace-by-fee discussions was that it was finally decided. My opinion is that we should be doing what we can to make 0-confs as reliable as possible - which will always be 'not very', but a solid system to notify on attempted double-spends is a good start. I'd like to know how Peter Todd's experiment with the 2BTC reward has gone. On 21 May 2013 13:27, Mike Hearn wrote: > Indeed, that has been proposed but it's a dumb idea and I'm very sceptical > it will go anywhere. Certainly no decision was made. The arguments for it > are based on some quite faulty thinking about economics. Double spend > notifications have been proposed a long time ago, I believe Matt has > indicated some interest in implementing them and that is the right way to > go. > On 20 May 2013 18:57, "Pieter Wuille" wrote: > >> On Tue, May 21, 2013 at 3:24 AM, Robert Backhaus >> wrote: >> > So the decision has been made to make 0-conf double spends trivial, so >> no >> > one will ever trust 0-confs. If a later transaction appears with a >> larger >> > fee, it will be considered to be the valid one, and the first one >> dropped, >> > as long as the first one has not been confirmed. This makes undoing a >> > mistaken transaction possible. >> >> This has been suggested, but I know of no such decision having been made. >> >> -- >> Pieter >> >> >> ------------------------------------------------------------------------------ >> Try New Relic Now & We'll Send You this Cool Shirt >> New Relic is the only SaaS-based application performance monitoring >> service >> that delivers powerful full stack analytics. Optimize and monitor your >> browser, app, & servers with just a few lines of code. Try New Relic >> and get this awesome Nerd Life shirt! >> http://p.sf.net/sfu/newrelic_d2d_may >> _______________________________________________ >> Bitcoin-development mailing list >> Bitcoin-development@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bitcoin-development >> > --089e01228e426eebe904dd32325a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
That's good - what I had taken away from the replace-b= y-fee discussions was that it was finally decided.

My op= inion is that we should be doing what we can to make 0-confs as reliable as= possible - which will always be 'not very', but a solid system to = notify on attempted double-spends is a good start.

I'd like to know how Peter Todd's experim= ent with the 2BTC reward has gone.


On 21 May 201= 3 13:27, Mike Hearn <mike@plan99.net> wrote:

Indeed, that has been proposed but it's a dumb idea and = I'm very sceptical it will go anywhere.=A0 Certainly no decision was ma= de. The arguments for it are based on some quite faulty thinking about econ= omics. Double spend notifications have been proposed a long time ago, I bel= ieve Matt has indicated some interest in implementing them and that is the = right way to go.

On 20 May 2013 18:57, "Pieter Wui= lle" <= pieter.wuille@gmail.com> wrote:
On Tue, May 21, 2013 at 3:24 AM, Robert Backhaus <robbak@robbak.com> wrote:
> So the decision has been made to make 0-conf double spends trivial, so= no
> one will ever trust 0-confs. If a later transaction appears with a lar= ger
> fee, it will be considered to be the valid one, and the first one drop= ped,
> as long as the first one has not been confirmed. This makes undoing a<= br> > mistaken transaction possible.

This has been suggested, but I know of no such decision having been made.
--
Pieter

---------------------------------------------------------------------------= ---
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service=
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--089e01228e426eebe904dd32325a--