From: Matt Whitlock <bip@mattwhitlock•name>
To: Tom Harding <tomh@thinlink•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Double-spending unconfirmed transactions is a lot easier than most people realise
Date: Wed, 23 Apr 2014 00:03:17 -0400 [thread overview]
Message-ID: <1533579.cuHiT41BQ7@crushinator> (raw)
In-Reply-To: <53574581.3040004@thinlink.com>
On Tuesday, 22 April 2014, at 8:45 pm, Tom Harding wrote:
> A network where transaction submitters consider their (final)
> transactions to be unchangeable the moment they are transmitted, and
> where the network's goal is to confirm only transactions all of whose
> UTXO's have not yet been seen in a final transaction's input, has a
> chance to be such a network.
Respectfully, this is not the goal of miners. The goal of miners is to maximize profits. Always will be. If they can do that by enabling replace-by-fee (and they can), then they will. Altruism does not factor into business.
next prev parent reply other threads:[~2014-04-23 4:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 21:31 Peter Todd
2014-04-23 4:29 ` Jan Møller
2014-04-23 6:35 ` Mark Friedenbach
2014-04-23 4:45 ` Tom Harding
2014-04-23 4:03 ` Matt Whitlock [this message]
2014-04-23 22:29 ` Tom Harding
2014-04-24 0:42 ` Simon Barber
2014-04-23 4:22 ` Jeff Garzik
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=1533579.cuHiT41BQ7@crushinator \
--to=bip@mattwhitlock$(echo .)name \
--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