From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 9C1CA87A for ; Tue, 4 Aug 2015 21:46:57 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail149055.authsmtp.co.uk (outmail149055.authsmtp.co.uk [62.13.149.55]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 067ACEA for ; Tue, 4 Aug 2015 21:46:56 +0000 (UTC) Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235]) by punt17.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t74LkpDa094577; Tue, 4 Aug 2015 22:46:51 +0100 (BST) Received: from [25.114.14.211] ([24.114.75.173]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t74Lkkdx006386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Aug 2015 22:46:48 +0100 (BST) In-Reply-To: References: <1438640036.2828.0.camel@auspira.com> <3162BC78-EC0B-4DAA-A472-D143389DDD8A@hashingit.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 From: Peter Todd Date: Tue, 04 Aug 2015 21:46:22 +0000 To: Gavin Andresen , Gavin Andresen via bitcoin-dev , Dave Hudson Message-ID: <3E3C6C76-DF1F-4F06-A01F-4E126B70C8F2@petertodd.org> X-Server-Quench: 501f67b7-3af2-11e5-b398-002590a15da7 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR bgdMdgYUGUATAgsB AmMbWVZeVFt7XGM7 aQ5PbARZfE1LQQRt U1dNRFdNFUssBhh9 XUVKGhlycQZOfjBx YERiWz5eXEUsc0Ev RVNXRDsEeGZhPWUC AkNRfx5UcAFPdx8U a1UrBXRDAzANdhEy HhM4ODE3eDlSNhEd CChFEUgbR10CFSI9 QBZKMzgiVWgMXSY+ M1QLOl8HAF1ZDUQu MVw8RRoRezUWDQZd V3pMEiIRA1gERjZh SEZcUFFWCjBGTC5G CR1gOhZQDyYaQTdX C0ZeVwpn X-Authentic-SMTP: 61633532353630.1023:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 24.114.75.173/465 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] "A Transaction Fee Market Exists Without a Block Size Limit"--new research paper suggests X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2015 21:46:57 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 4 August 2015 17:30:28 GMT-04:00, Gavin Andresen via bitcoin-dev wrote: >On Tue, Aug 4, 2015 at 2:41 PM, Dave Hudson via bitcoin-dev < >bitcoin-dev@lists.linuxfoundation.org> wrote: > >> Fundamentally a block maker (pool or aggregation of pools) does not >orphan >> its own blocks. > > >Unless the block maker has an infinitely fast connection to it's >hashpower >OR it's hashpower is not parallelized at all, that's not strictly true >-- >it WILL orphan its own blocks because two hashing units will find >solutions >in the time it takes to communicate that solution to the block maker >and to >the rest of the hashing units. > >That's getting into "how many miners can dance on the head of a pin" >territory, though. I don't think we know whether the communication >advantages of putting lots of hashing power physically close together >will >outweigh the extra cooling costs of doing that (or maybe some other >tradeoff I haven't thought of). That would be a fine topic for another >paper.... I'd suggest you do more research into how Bitcoin and mining works as the above has a number of serious misunderstandings. Or, I could just point out the obvious rather than try to be polite: you know exactly why the above makes no sense as a reply to this thread and are deliberately lying. If the situation is the latter, your conduct is toxic to the development mailing list discussion, not to mention a waste of all our time, and you should leave. -----BEGIN PGP SIGNATURE----- iQE9BAEBCAAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJVwTKi AAoJEMCF8hzn9Lnc47AH/0txNyw9dLdsfQOsNE14jLEcQifxOkaKLqTJV1O4gn6O L4+T6rPo9pVLTBuVWcsm2A24R/gBL+pYaWgaIyk/3fbSRpg4GfVau0xxh54vQU6m U4L7FPHsdZ2y67frv/+5ExJ2xrVuedhpTciTi2SqSE6C0fioO+YarH0Dvd8I5Wjx f9GnmxLdKytoj2kUaoriSSxsUzMNzxVzq78jEmhMR85TGy73ApeLdgBC/pdNgxZa oAQ0CXCMYgsE59HUOO05xFLazGxNh2epPADTbTTgoNQ9py38evlW254okhRmk9p9 v4i1yTzuv/Y6C0qw2RZcEiT/GTdvajkMKCidLEm3LbY= =W/Ke -----END PGP SIGNATURE-----