Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mark@monetize.io>) id 1WxjYN-0007Ms-Sq
	for bitcoin-development@lists.sourceforge.net;
	Thu, 19 Jun 2014 21:07:27 +0000
Received: from mail-pd0-f181.google.com ([209.85.192.181])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WxjYL-0007jM-QM
	for bitcoin-development@lists.sourceforge.net;
	Thu, 19 Jun 2014 21:07:27 +0000
Received: by mail-pd0-f181.google.com with SMTP id v10so2197185pde.12
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 19 Jun 2014 14:07:20 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:message-id:date:from:organization:user-agent
	:mime-version:to:cc:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=l4JT5juzdkOLCEP+qJGb0IRB+hyhDkS5d/fxw6omVwo=;
	b=ifSnF0+joxVaefiK6vrUlaHYRV+oMGs29b0296CDKzPhUwKcEg7neTwxZ9epsKR1R8
	d8Agj1y9j2Sj/9Br+R+qlMfp/3k67GKi0NIhcgZACUwrh2dhFzRVoJSR/OmLdEBI86Ij
	YL6mDfSblp41qrGXIuwWOZVZoz5AQo1IIV10TstLqWpxBX8Rw+td0GmtKZoU8eLUvMOD
	x00WVteDk39BG7YdH4mjwPLrxuXP4lOh0m4ofoi7XW/z8R+aHi8CxrBWdQ8l2lnEJDwC
	Wwl4DRiHB8w+z1E0z7z8mm1uVpVaCk5b+mID0cPrVApsTQtSVnK8AopB6ew+1APHBsZI
	rncQ==
X-Gm-Message-State: ALoCoQnG7Wn1sIua4ZW5/CmSgFgZ+RQoVk0Gx1wWOzfz3qn9cOhlxcJaOZety8tgEAslL+y9nAlW
X-Received: by 10.66.122.36 with SMTP id lp4mr8874492pab.82.1403212039847;
	Thu, 19 Jun 2014 14:07:19 -0700 (PDT)
Received: from [192.168.127.236] (50-0-36-179.dsl.dynamic.sonic.net.
	[50.0.36.179]) by mx.google.com with ESMTPSA id
	ry10sm32080292pab.38.2014.06.19.14.07.17 for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 19 Jun 2014 14:07:19 -0700 (PDT)
Message-ID: <53A35105.3070509@monetize.io>
Date: Thu, 19 Jun 2014 14:07:17 -0700
From: Mark Friedenbach <mark@monetize.io>
Organization: Monetize.io Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: slush <slush@centrum.cz>
References: <53A316BE.5040508@certimix.com> <53A31B3E.7020906@monetize.io>
	<CANEZrP2Lq-28NuvOJR_rS3N2TZsy13xrKubcfPBrMbP7WArcKw@mail.gmail.com>
	<CAJna-HgNnwARH2AN_LJ1LFkrWL5n4X4Lo-koW0WdOWw1RUiGJA@mail.gmail.com>
	<53A34A71.2090106@monetize.io>
	<CAJna-HgP=RvbFpkdwqkoNP0fmMg6r80zDKrA-Cb2mcbmyjOTEA@mail.gmail.com>
In-Reply-To: <CAJna-HgP=RvbFpkdwqkoNP0fmMg6r80zDKrA-Cb2mcbmyjOTEA@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
	no trust [209.85.192.181 listed in list.dnswl.org]
X-Headers-End: 1WxjYL-0007jM-QM
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BlockPow: A Practical Proposal to prevent
 mining pools AND reduce payoff variance:
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 19 Jun 2014 21:07:28 -0000

It's not the pool operator's business what software the miner is running
to select transactions for his block, so long as the miner follows the
template and doesn't generate invalid blocks. We already discussed
invalid blocks, and checking the template requires parsing the coinbase
transaction and verifying the merkleroot. The most expensive operations
are the hashes in the merkleroot verification, but you have to do that
in stratum too because of the extranonce, right?

On 06/19/2014 01:55 PM, slush wrote:
> Miner issues are just one thing what came to my mind. What about
> validating transactions? How the pool can be sure that miner is running
> up to date bitcoind which do full validation of transactions? Not
> talking that if every miner takes his own set of transaction, pool need
> to calculate merkle root for every submit, to check its correctness.