From: Andy Parkins <andyparkins@gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] ASIC-proof mining
Date: Fri, 04 Jul 2014 13:01:33 +0100 [thread overview]
Message-ID: <5408721.UFIVL0MiXs@momentum> (raw)
In-Reply-To: <CAAS2fgRrAOgEv7Hq4BofS5UoDPsJy3hEt34od54pY6vtEq0Agw@mail.gmail.com>
On Friday 04 July 2014 04:37:26 Gregory Maxwell wrote:
[excellent explanation removed for brevity]
> > Apologies in advance if this is a stupid idea.
>
> No need to be sorry— talking about these things is how people learn.
> While I don't think this idea is good, and I'm even skeptical about
> fixed versions— I promise you many other people were thinking similar
> or even less useful things and will find the discussion interesting.
Thank you for the very thorough and courteous response. I'm sorry that I
suggested something that had been thought of before (seems to be the case on
every great idea I have for Bitcoin) and was not practical; but I'm glad to
have had your response which was certainly educational for me.
Andy
--
Dr Andy Parkins
andyparkins@gmail.com
next prev parent reply other threads:[~2014-07-04 12:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 10:27 [Bitcoin-development] ASIC-proof mining Andy Parkins
2014-07-04 10:53 ` Alan Reiner
2014-07-04 11:08 ` Eugen Leitl
2014-07-04 11:15 ` Andy Parkins
2014-07-04 11:22 ` Alan Reiner
2014-07-04 11:28 ` Andy Parkins
2014-07-04 11:37 ` Gregory Maxwell
2014-07-04 12:01 ` Andy Parkins [this message]
2014-07-04 15:20 ` Mike Hearn
2014-07-04 16:50 ` kjj
2014-07-04 18:39 ` Ron Elliott
2014-07-04 19:54 ` Aaron Voisine
2014-07-04 20:21 ` Jorge Timón
2014-07-04 20:38 ` Luke Dashjr
2014-07-04 20:55 ` Randi Joseph
2014-07-05 8:43 ` Mike Hearn
2014-07-07 0:20 ` Randi Joseph
2014-07-07 6:12 ` Odinn Cyberguerrilla
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=5408721.UFIVL0MiXs@momentum \
--to=andyparkins@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gmaxwell@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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