From: Mike Hearn <mike@plan99•net>
To: Andy Parkins <andyparkins@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] ASIC-proof mining
Date: Fri, 4 Jul 2014 17:20:23 +0200 [thread overview]
Message-ID: <CANEZrP3tRWuoUv8Xw5OgXRsfw4WEpTWp=UEOe-Xjt8LAr_fEPw@mail.gmail.com> (raw)
In-Reply-To: <5408721.UFIVL0MiXs@momentum>
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
Yup, no need to apologise. If nothing else the conversations get archived
where other people can use them to get up to speed faster. A lot of these
discussions get spread across forums, lists and IRC so it can be hard to
know what the current state of the art thinking is.
Recall the second prong of my opening argument - if you could beat ASICs,
you'd end up with botnets. I prefer having the chain be dominated by a
single pool for a while than having one with a major botnet presence, given
their history of doing things like mining empty blocks and giving random
people enormous electricity bills.
I think we can make good head way if we just optimise a lot and finish
things off, to be honest. I'm not sure we need an algorithmic silver
bullet. Remember you can always outsource mining by just not having any
hardware at all, CEX style, so trying to prevent outsourcing using clever
hacks seems ultimately doomed.
[-- Attachment #2: Type: text/html, Size: 1054 bytes --]
next prev parent reply other threads:[~2014-07-04 15:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 10:27 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
2014-07-04 15:20 ` Mike Hearn [this message]
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='CANEZrP3tRWuoUv8Xw5OgXRsfw4WEpTWp=UEOe-Xjt8LAr_fEPw@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=andyparkins@gmail$(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