diff options
| author | Luke Dashjr <luke@dashjr.org> | 2015-06-20 03:48:05 +0000 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2015-06-20 03:48:49 +0000 |
| commit | 87d8d5afd50efcdc02e60f1ec978de856c5f903b (patch) | |
| tree | 74bc1ee2f38351a9ce38bf408212e493ef711c53 | |
| parent | c1eb3e1073fef765476e4db26c6bf8a113669578 (diff) | |
| download | pi-bitcoindev-87d8d5afd50efcdc02e60f1ec978de856c5f903b.tar.gz pi-bitcoindev-87d8d5afd50efcdc02e60f1ec978de856c5f903b.zip | |
Re: [Bitcoin-development] F2Pool has enabled full replace-by-fee
| -rw-r--r-- | 78/c6fb298548b43cde8ba0ae2c29171ffffc94ea | 76 |
1 files changed, 76 insertions, 0 deletions
diff --git a/78/c6fb298548b43cde8ba0ae2c29171ffffc94ea b/78/c6fb298548b43cde8ba0ae2c29171ffffc94ea new file mode 100644 index 000000000..3cdd1a602 --- /dev/null +++ b/78/c6fb298548b43cde8ba0ae2c29171ffffc94ea @@ -0,0 +1,76 @@ +Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] + helo=mx.sourceforge.net) + by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <luke@dashjr.org>) id 1Z69lx-0004wY-9E + for bitcoin-development@lists.sourceforge.net; + Sat, 20 Jun 2015 03:48:49 +0000 +Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of dashjr.org + designates 192.3.11.21 as permitted sender) + client-ip=192.3.11.21; envelope-from=luke@dashjr.org; + helo=zinan.dashjr.org; +Received: from zinan.dashjr.org ([192.3.11.21]) + by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) + id 1Z69lv-0000nU-9x for bitcoin-development@lists.sourceforge.net; + Sat, 20 Jun 2015 03:48:49 +0000 +Received: from ishibashi.localnet (unknown + [IPv6:2001:470:5:265:61b6:56a6:b03d:28d6]) + (Authenticated sender: luke-jr) + by zinan.dashjr.org (Postfix) with ESMTPSA id C4B6A108083A; + Sat, 20 Jun 2015 03:48:07 +0000 (UTC) +X-Hashcash: 1:25:150620:bitcoin-development@lists.sourceforge.net::RgsY08PLKIIU/aJW:d0TP +X-Hashcash: 1:25:150620:voisine@gmail.com::tZkkBx0KwyFXBSLC:E2dh +X-Hashcash: 1:25:150620:mark@friedenbach.org::LT2up1kkBym65F4j:aIBAz +From: Luke Dashjr <luke@dashjr.org> +To: bitcoin-development@lists.sourceforge.net +Date: Sat, 20 Jun 2015 03:48:05 +0000 +User-Agent: KMail/1.13.7 (Linux/3.14.41-gentoo; KDE/4.14.3; x86_64; ; ) +References: <20150619103959.GA32315@savin.petertodd.org> + <CAOG=w-u6fmpnojpQmrFEMRK56WDsfhZgm406C3tVax5hsX2sOA@mail.gmail.com> + <CACq0ZD5VDJRuKiq2NaPyoJdDVMPd+9YWtEr3pauS5ZNzxXXEig@mail.gmail.com> +In-Reply-To: <CACq0ZD5VDJRuKiq2NaPyoJdDVMPd+9YWtEr3pauS5ZNzxXXEig@mail.gmail.com> +X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F +X-PGP-Key-ID: BD02942421F4889F +X-PGP-Keyserver: hkp://pgp.mit.edu +MIME-Version: 1.0 +Content-Type: Text/Plain; + charset="iso-8859-15" +Content-Transfer-Encoding: 7bit +Message-Id: <201506200348.06564.luke@dashjr.org> +X-Spam-Score: -1.9 (-) +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 + -0.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay + domain + -0.1 AWL AWL: Adjusted score from AWL reputation of From: address +X-Headers-End: 1Z69lv-0000nU-9x +Subject: Re: [Bitcoin-development] F2Pool has enabled full replace-by-fee +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Sat, 20 Jun 2015 03:48:49 -0000 + +On Saturday, June 20, 2015 1:23:03 AM Aaron Voisine wrote: +> They don't need to be made cryptographically safe, they just have to be +> safer than, for instance, credit card payments that can be charged back. As +> long as it's reasonably good in practice, that's fine. + +They never will be. You can get a decent rate of success merely by making one +transaction propagate fast (eg, 1 input, 1 output) and the other slow (eg, +1000 inputs, 1000 outputs) and choosing your peers carefully. The only reason +unconfirmed transactions aren't double spent today is because nobody is +seriously *trying*. + +Luke + + |