<oembed><type>rich</type><version>1.0</version><author_name>npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2</author_name><author_url>https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-06-19&#xA;📝 Original message:On Fri, Jun 19, 2015 at 03:00:57PM +0000, justusranvier at riseup.net wrote:&#xA;&gt; On 2015-06-19 10:39, Peter Todd wrote:&#xA;&gt; &#xA;&gt;      Yesterday F2Pool, currently the largest pool with 21% of the hashing&#xA;&gt;      power, enabled full replace-by-fee (RBF) support after discussions &#xA;&gt; with&#xA;&gt;      me. This means that transactions that F2Pool has will be replaced if &#xA;&gt; a&#xA;&gt;      conflicting transaction pays a higher fee. There are no requirements &#xA;&gt; for&#xA;&gt;      the replacement transaction to pay addresses that were paid by the&#xA;&gt;      previous transaction.&#xA;&gt; &#xA;&gt; &#xA;&gt; Intentional fraud is a bad thing to add to a financial protocol.&#xA;&gt; &#xA;&gt; A user who creates conflicting transactions, one that pays someone else &#xA;&gt; and another which does not pay them, and broadcasts both of them, has &#xA;&gt; just self-incriminated themselves by producing prima facie evidence of &#xA;&gt; fraud.&#xA;&#xA;Depends.&#xA;&#xA;If you ask me to pay you 1BTC at address A and I create tx1 that pays&#xA;1BTC to A1 and 2BTC of chain to C, what&#39;s wrong with me creating tx2&#xA;that still pays 1BTC to A, but now only pays 1.999BTC to C? I&#39;m not&#xA;defrauding you, I&#39;m just reducing the value of my change address to pay&#xA;a higher fee. Similarly if I now need to pay Bob 0.5BTC, I can create&#xA;tx3 paying 1BTC to A, 0.5BTC to B, and 1.498BTC to C.&#xA;&#xA;Yet from the point of view of an external observer they have no idea why&#xA;the transaction outputs reduced in size, nor any way of knowing if fraud&#xA;did or did not occur.&#xA;&#xA;Equally, maybe you tell me &#34;Actually, just give me 0.5BTC to cancel out&#xA;that debt&#34;, in which case I&#39;m not breaking any contract at all by giving&#xA;you less money than I first promised - the contract has changed.&#xA;&#xA;Again, none of this can or should be observable to anyone other than the&#xA;parties directly involved.&#xA;&#xA;&gt; It may be the case that since Bitcoin spans multiple legal jurisdictions &#xA;&gt; and can be use anonymously that the victims of such fraud can not rely &#xA;&gt; on legal recourse, and it may also be the case that proof of work is how &#xA;&gt; Bitcoin deals with the aforementioned factors, but regardless &#xA;&gt; un-prosecutable fraud is still fraud and anyone who encourages it should &#xA;&gt; be recognied as a bad actors.&#xA;&gt; &#xA;&gt; Committing vandalism and encouraging fraud to prove a point may be &#xA;&gt; something the network can&#39;t stop on a technical level, but there&#39;s no &#xA;&gt; reason not to call it out for what it is.&#xA;&#xA;What do you think of Bitcoin XT then? It relays double-spends, which&#xA;makes it much easier to get double-spends to miners than before. In&#xA;particular you see a lot of zero-fee transactions being replaced by&#xA;fee-paying transactions, relayed through Bitcoin XT nodes and then&#xA;mined. Is that encouraging fraud?&#xA;&#xA;-- &#xA;&#39;peter&#39;[:-1]@petertodd.org&#xA;000000000000000003932458055c68d4ee2b6d68441c4764efbdf6b0b1683717&#xA;-------------- next part --------------&#xA;A non-text attachment was scrubbed...&#xA;Name: signature.asc&#xA;Type: application/pgp-signature&#xA;Size: 650 bytes&#xA;Desc: Digital signature&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150619/8664ea09/attachment.sig&gt;</html></oembed>