From: 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 15:29:33 -0700 [thread overview]
Message-ID: <53583ECD.5000105@thinlink.com> (raw)
In-Reply-To: <1533579.cuHiT41BQ7@crushinator>
On 4/22/2014 9:03 PM, Matt Whitlock wrote:
> 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.
The rational miner works hard digging hashes out of the ether, and wants
the reward to be great. How much more valuable would his reward be if
he were paid in something that is spendable like cash on a 1-minute
network for coffee and other innumerable real-time transactions, versus
something that is only spendable on a 15-minute network?
There is a prisoner's dilemma, to be sure, but do the fees from helping
people successfully double-spend their coffee supplier really outweigh
the increased value to the entire network - including himself - of
ensuring that digital cash actually works like cash?
next prev parent reply other threads:[~2014-04-23 22:30 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
2014-04-23 22:29 ` Tom Harding [this message]
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=53583ECD.5000105@thinlink.com \
--to=tomh@thinlink$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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