public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Roy Badami <roy@gnomon•org.uk>
To: Jeff Garzik <jgarzik@bitpay•com>
Cc: Bitcoin-Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: soft-fork to make anyone-can-spend outputs unspendable for 100 blocks
Date: Tue, 4 Jun 2013 19:36:53 +0100	[thread overview]
Message-ID: <20130604183652.GI45035@giles.gnomon.org.uk> (raw)
In-Reply-To: <CAJHLa0PRNxS7K3YeCx_eXkZQdO8vOCefuGyXMXD7ESq0QEhr+g@mail.gmail.com>

> Sure they are paying themselves, but given bitcoin network
> difficulty is uso high, simply obtaining payments-go-myself-as-miner
> transactions is itself difficult.

Not for pool operators it isn't.  Nor for people buying hashing power
from a GPUMAX-type service, if such services still exist (or should
they exist again in future).



  reply	other threads:[~2013-06-04 18:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-01 19:30 Peter Todd
     [not found] ` <201306012034.31543.luke@dashjr.org>
2013-06-01 20:58   ` Peter Todd
     [not found] ` <38A06794-B6B4-45F3-99C1-24B08434536D@gmail.com>
2013-06-02  6:13   ` Peter Todd
2013-06-02 17:35     ` Jeff Garzik
2013-06-02 18:41       ` Peter Todd
2013-06-04  0:22     ` Mark Friedenbach
2013-06-02 21:45 ` Adam Back
2013-06-04 14:12   ` Jeff Garzik
2013-06-04 14:55     ` John Dillon
2013-06-04 17:42       ` Jeff Garzik
2013-06-04 18:36         ` Roy Badami [this message]
2013-06-04 18:49           ` Jeff Garzik
2013-06-04 20:25             ` Peter Todd
2013-06-03 23:43 ` Melvin Carvalho
2013-06-04  2:26   ` Michael Hendricks
2013-06-06 19:14 Luke-Jr
2013-06-06 19:59 ` Andreas M. Antonopoulos
2013-06-06 20:07   ` Luke-Jr
2013-06-06 20:16     ` Andreas M. Antonopoulos
2013-06-06 21:48       ` Luke-Jr
2013-06-06 22:10         ` Melvin Carvalho
2013-06-06 20:25   ` Melvin Carvalho

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=20130604183652.GI45035@giles.gnomon.org.uk \
    --to=roy@gnomon$(echo .)org.uk \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=jgarzik@bitpay$(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