Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UyfRD-0000Tz-BK for bitcoin-development@lists.sourceforge.net; Mon, 15 Jul 2013 09:51:23 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of petertodd.org designates 62.13.148.112 as permitted sender) client-ip=62.13.148.112; envelope-from=pete@petertodd.org; helo=outmail148112.authsmtp.co.uk; Received: from outmail148112.authsmtp.co.uk ([62.13.148.112]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1UyfRB-000721-Dd for bitcoin-development@lists.sourceforge.net; Mon, 15 Jul 2013 09:51:23 +0000 Received: from mail-c232.authsmtp.com (mail-c232.authsmtp.com [62.13.128.232]) by punt9.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id r6F9pE1F055611; Mon, 15 Jul 2013 10:51:14 +0100 (BST) Received: from savin (76-10-178-109.dsl.teksavvy.com [76.10.178.109]) (authenticated bits=128) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id r6F9p8FL001482 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 15 Jul 2013 10:51:11 +0100 (BST) Date: Mon, 15 Jul 2013 05:51:07 -0400 From: Peter Todd To: Peter Vessenes Message-ID: <20130715095107.GA8828@savin> References: <20130705140140.GA23949@netbook.cypherspace.org> <20130712131815.GA18716@petertodd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Server-Quench: 14b7653e-ed34-11e2-b10b-0025903375e2 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aQdMdwcUEkAYAgsB AmUbWlReVVx7WGI7 bAxPbAVDY01GQQRq WVdMSlVNFUsqB2oI RhZoLhlydgFOejBx ZUJkXj5aWBZ9c0N+ F1MBQW4CeGZhPWIC AkFYJR5UcAFPdx9G aVd6AXFDAzANdhES HhM4ODE3eDlSNilR RRkIIFQOdA4PHzQu SgoFFjIuGwUfSiE+ JgcrJhpUA0YYLg07 O1w8RRoRUVcABxdZ FEZMBmpeIV0QDyMv EUZRWk8YWCJcXScU Dxw0IhJSRztIEi9Z AkpDRHkA X-Authentic-SMTP: 61633532353630.1019:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 76.10.178.109/587 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Score: -1.5 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1UyfRB-000721-Dd Cc: Bitcoin-Dev Subject: Re: [Bitcoin-development] libzerocoin released, what about a zerocoin-only alt-coin with either-or mining 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: Mon, 15 Jul 2013 09:51:23 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 13, 2013 at 11:32:39AM -0700, Peter Vessenes wrote: > One very real issue for alt-currencies that don't peg to Bitcoin is that > market liquidity is a bitch. By almost all standards current global Bitco= in > liquidity is already very, very low. Too low for many transactions that > come across my desk at least. >=20 > There are a lot of reasons for that low liquidity, but to try and float a > new pair for which the likely initial counter-asset is going to be Bitcoin > means minuscule liquidity. Being able to have automated Bitcoin<->Zerocoin P2P trading without an exchange is also significantly more desirable from a privacy standpoint. Basically it reduces the privacy risks of doing the exchange to spending the Zerocoins in the first place. --=20 'peter'[:-1]@petertodd.org 00000000000000878c30a45104c48fd4e8037cb5b3ba1e14dc4d8bef72eff1be --envbJBWh7q8WU6mo Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBCAAGBQJR48YLAAoJECSBQD2l8JH74ksIAJzpJn3/aVn6+A4PYdVad61m cOAp1wgCMc7GRTbHOATmL+E7WIfD/lldSyLnokY7YC0smhGVKfWeqWcPXhxgzysZ Eb5ghSYePaf7O4wIVoedWorAVHTbZtJgfaY3s8QntiOKEPnvhSTPOrXOVu1vmfge ybOFR9YTonabqKyVkhmA3jGaPKrLATD3SaeaW+33nTdcXY9DXuPPrF5LndjwjDHg H0YOTLAk1dJrk+2+teY0RsFaYRkcVTNA7r4ZDDU7rUJWda4oEnids1iZgiE7PlXN gAQyg8xMnd/vJeKsFX9VSG0JqMbYxqYJO+wln/D3ekcFos+MFCwZm2o8HQdxxzY= =nIWO -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo--