Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.149.82 as permitted sender)
	client-ip=62.13.149.82; envelope-from=pete@petertodd.org;
	helo=outmail149082.authsmtp.co.uk; 
Date: Fri, 14 Jun 2013 15:20:58 -0400
From: Peter Todd <pete@petertodd.org>
To: Adam Back <adam@cypherspace.org>
Message-ID: <20130614192058.GA11509@petertodd.org>
References: <20130519132359.GA12366@netbook.cypherspace.org>
	<20130613133932.GA13028@netbook.cypherspace.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU"
Content-Disposition: inline
In-Reply-To: <20130613133932.GA13028@netbook.cypherspace.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Bitcoin-Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] is there a way to do bitcoin-staging?
Precedence: list


--azLHFNyN32YCQGCU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 13, 2013 at 03:39:32PM +0200, Adam Back wrote:
> I had one thought towards this which is a different kind of merged mining.
>=20
> I think a "fair" merged mining aiming for price parity would be done by t=
he
> miner having to choose the altcoin or btc at mine time, and altcoin chain
> considering btc mine unspendable and bitcoin considering ac unspendable.

One way to look at what you are describing is to say you want to prove
your sacrifice of potential BTC earnings. That goes back to the PoW
hashcash stuff I mentioned earlier, and is accomplished by simply mining
shares with an unspendable coinbase to prove you did work that could
have resulted in Bitcoins, but didn't.

--=20
'peter'[:-1]@petertodd.org
00000000000000b7dc90d34b08218b76687c0cd8a00878fea13d4ce98b0f4df0

--azLHFNyN32YCQGCU
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAlG7bRkACgkQpEFN739thowEbQCfbwXIEzFD6X7OdOoU7d/vzIHd
KFUAn12CRaHJY1MBNcnt3tclDyj5dqAy
=M8ph
-----END PGP SIGNATURE-----

--azLHFNyN32YCQGCU--