Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 367E7C002B for ; Sat, 4 Feb 2023 16:28:04 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id EFE3360AC9 for ; Sat, 4 Feb 2023 16:28:03 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org EFE3360AC9 Authentication-Results: smtp3.osuosl.org; dkim=pass (2048-bit key, unprotected) header.d=messagingengine.com header.i=@messagingengine.com header.a=rsa-sha256 header.s=fm3 header.b=ZYW3UP+q X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.602 X-Spam-Level: X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NoRQ6C_Wnlvb for ; Sat, 4 Feb 2023 16:28:03 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org E096F60881 Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by smtp3.osuosl.org (Postfix) with ESMTPS id E096F60881 for ; Sat, 4 Feb 2023 16:28:02 +0000 (UTC) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id E16DC3200708; Sat, 4 Feb 2023 11:28:00 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sat, 04 Feb 2023 11:28:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1675528080; x=1675614480; bh=p8A4ZIr+3UnRAm/8TRFcXR78a9SN sMfpOyNjQM/fpEo=; b=ZYW3UP+qpJgEeIZnqAj2hBhCph8YDXINoKxLTJD16l+4 juGWwjhnTfs0gZHopSkqr+lN8KPDGc+iP2bbxcj+8cBPZ++eR75qBY9sKUAP8UBv 4ik30QZHqDRAGfo3vRura4PRUbd3qb+bvN79B+dWa9UIzcLSdORByaqHNZnejykN PFlfz5QD8/SfJnLYBaNxrzzibvgZ3TD1fWt/iTCs087Yh1ocnSFLlE3AQ+O1bc+x j8WhemQZ+YfjLt4Q4KJlOblhcCDL5h6u43c4EBOFNjf2fv1uWRbIqjyJrOyYxmjz cYPJEJa8s2oUBclRiwNp42WDj3Q1GaIuoTH9gfw6pA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudegvddgkeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggujgesghdtreertddtvdenucfhrhhomheprfgvthgv rhcuvfhougguuceophgvthgvsehpvghtvghrthhouggurdhorhhgqeenucggtffrrghtth gvrhhnpeelvdellefftddukeduffejgfefjeeuheeileeftdfgteduteeggeevueethfej tdenucffohhmrghinhepphgvthgvrhhtohguugdrohhrghenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvgesphgvthgvrhhtohguugdr ohhrgh X-ME-Proxy: Feedback-ID: i525146e8:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 4 Feb 2023 11:27:59 -0500 (EST) Received: by localhost (Postfix, from userid 1000) id 268AC5F879; Sat, 4 Feb 2023 11:27:47 -0500 (EST) Date: Sat, 4 Feb 2023 11:27:47 -0500 From: Peter Todd To: Daniel Lipshitz Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="XBrXsSEEO5hxpEuH" Content-Disposition: inline In-Reply-To: Cc: bitcoin-dev , John Carvalho Subject: Re: [bitcoin-dev] A proposal for Full RBF to not exclude Zero Conf use case X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Feb 2023 16:28:04 -0000 --XBrXsSEEO5hxpEuH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 14, 2023 at 10:15:30PM +0200, Daniel Lipshitz wrote: > We have standard commercial information about the payment processors, non > custodial liquidity providers and merchants which become our clients - we > do not have any kyc/aml information or telephone number on who is sending > our clients the bitcoin for deposit. For us these are just bitcoin Trx > which our clients choose to benefit from 0-conf deposit recognition. Our > service is provided via API with the only information our clients share > with us, regarding a specific bitcoin transaction, being public bitcoin > information like trx hash and output address. You know who your clients are, and thus every request for information on a transaction is reasonably likely to be a deposit associated with the client= who requested it. Learning what addresses are associated with what entity is a significant benefit to Chainalysis operations, and there's every reason to expect that the data you learn will either be sold or leaked to Chainalysis companies. --=20 https://petertodd.org 'peter'[:-1]@petertodd.org --XBrXsSEEO5hxpEuH Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmPeh4AACgkQLly11TVR LzeDTxAAuATzimWJq8Fmqc+VAVN2KeKSr9Nvc+uASlQD1X581e7FrzCp/rv17XUW 4CrnKT0JGARA2SQkc9+QL983Opk8cpeTQQdF23p/aUTLfMHz1lagosVKLoL362yJ IpCfms7XiJYemSLVpovZDKEyj3CP8SRBdIrh5g2eD6qjhNbYujvrOGajvA4JsKdC DPU82OENxVuzGhQCYyB19bRVp6xcnD3J9MkXt+KHEPGhZgspgGFfNUiA3zEI0YjA MSUJPNzd2L4lr3cv6O+V17hgHLd7eOJKE7IfnzGFSkxPL00elEJLgrNE/YJgLHbi c3UZt6nA6ssWRKcEHm2wS9s7/c2B7hl1diilhXJRDfqqK0LGI47iU3/JhxHpy5Gc PaFA8r1iKIvD5UX5gXhRyy9aQjX7kZMXR4EJUvz8Q+PO4GLBtxhXFcWtmEhE0w8I CoqiEhzeUFaw3DjpXklnM7G8OTlY4A+yR/VqKfEPwp3hkDtI1oZ6WstxcbC33BEv jp/pq/o/oBcpkhoMnJvhroOXXEw90Wu3JEt1zOg8GJe89wgKw7OMBX6vpkUiq1UT yuow3xPmmytY3thGV1p2CEyHGZmshhg2cWCUR467OEUT9ts+5SPe70yWWokwSfI9 ncHZMWLRsWYtxGYsUVmf+mpCUpq+vxQQowaSRogrlvkWudzoQ+I= =sWKK -----END PGP SIGNATURE----- --XBrXsSEEO5hxpEuH--