Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WfDUl-0007eT-K4 for bitcoin-development@lists.sourceforge.net; Tue, 29 Apr 2014 19:15:11 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([192.3.11.21]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1WfDUk-0007UO-EZ for bitcoin-development@lists.sourceforge.net; Tue, 29 Apr 2014 19:15:11 +0000 Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265:be5f:f4ff:febf:4f76]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id EF39F10803A1; Tue, 29 Apr 2014 19:15:40 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Tue, 29 Apr 2014 19:14:59 +0000 User-Agent: KMail/1.13.7 (Linux/3.12.6-gentoo; KDE/4.11.5; x86_64; ; ) X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201404291915.00239.luke@dashjr.org> X-Spam-Score: -0.7 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1WfDUk-0007UO-EZ Cc: poolowners@list.pfoe.be, sirahlst@gmail.com, kinlo@triplemining.com, Con Kolivas Subject: [Bitcoin-development] GBT 2.0 wishlist X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2014 19:15:11 -0000 Let's try to get GBT 2.0 off the ground finally.. :) Here's some wishlist items/ideas: - Extremely low bandwidth use (binary protocol, with compression support) - UDP-based transport protocol? (so message order need not be preserved at the expense of latency) - Ability to instruct miners to insert (username,hash-of-username,hash-of- options-array,hash-of-both,etc) in coinbase at a given position (this enables cheaper proof-of-work auditing of a pool's rewards; it can just save/publish shares meeting higher targets and anyone can verify the shares were found by a given username/hash) - Always encrypted (once by the server), with optional authentication via CA/namecoin/URI - Incrementing "precommit id" so miners can precommit to settings without needing a new/custom coinbase - Multiple clients should share bandwidth on a LAN (similar to slush's stratum proxy) - Convey prevblock as block header so we can follow blockchains securely. - Fee logic: pools can claim as much coinbase distribution as they require (with hint from miner); miners are expected to ensure subsidy + transaction fees tally up to the required total; any fees beyond requires total may be distributed as the miner wishes. Potentially, pools could allow 50% (or similar) participation allowing a miner to use multiple pools at the same time. Rather than polluting the main development mailing list with what is sure to have quite a bit of discussion, I have asked kinlo (who hosts the poolowners mailing list) to provide a dedicated list for this purpose. Interested parties should please subscribe via http://list.pfoe.be/mailman/listinfo/gbt2 and send replies to gbt2@list.pfoe.be (once a draft BIP is ready, the main dev mailing list will be once again CC'd). Luke