Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 11D9AC0032 for ; Wed, 2 Aug 2023 01:28:15 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 9604140445 for ; Wed, 2 Aug 2023 01:28:14 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 9604140445 Authentication-Results: smtp2.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=G+kPdK2e X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TAjWEcSBbP4o for ; Wed, 2 Aug 2023 01:28:13 +0000 (UTC) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by smtp2.osuosl.org (Postfix) with ESMTPS id C408040376 for ; Wed, 2 Aug 2023 01:28:12 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org C408040376 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 2C4FE5C00D6; Tue, 1 Aug 2023 21:28:10 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Tue, 01 Aug 2023 21:28:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type: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=1690939690; x=1691026090; bh=1cJFg2ILJvThM ntcHTPn+/FRV1WCV/GZ9q862n1H4eM=; b=G+kPdK2ezXK/yUbwvupOv5/JCz2rH IShX+Lj0eaQ0lzoPVBrNDZaHFLI74L0HrNNFkC14LYYGYS1laGNP4VCc2ZJAqtIG y5/DGzYagfMfxWh4k0bzoOq+zqyZuhng6HZcd+ori6KdvzAYXizzekjdGKA3o73G 2o5Ly5lAsxrvUrtanCikQe9QUZdiC5dCCzrvXvz5zkbzfC2LnTp3KQEdonsEk507 MTB/XI11NP/COyYAWSlfz4hF4cvf2F/fGDwcZwCJ/vmKRKC8bugt/VOnN3PQyR+Z COad7F5NJqed/s1cinldZZ5qJw1e0EijyclJDV7LVzaDZpuXmzPY7JQLA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrjeejgdegiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvvefukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefrvghtvghr ucfvohguugcuoehpvghtvgesphgvthgvrhhtohguugdrohhrgheqnecuggftrfgrthhtvg hrnheptdfhfefgieffteetuddtgeekjefhvddttedtkeffudeileejleektdfglefgieev necuffhomhgrihhnpehlihhnuhigfhhouhhnuggrthhiohhnrdhorhhgpdhpvghtvghrth houggurdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhf rhhomhepphgvthgvsehpvghtvghrthhouggurdhorhhg X-ME-Proxy: Feedback-ID: i525146e8:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 1 Aug 2023 21:28:09 -0400 (EDT) Received: by localhost (Postfix, from userid 1000) id D49B85F830; Wed, 2 Aug 2023 01:28:06 +0000 (UTC) Date: Wed, 2 Aug 2023 01:28:06 +0000 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="P40TQ96qqG+j+U/4" Content-Disposition: inline In-Reply-To: Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Pull-req to enable Full-RBF by default 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: Wed, 02 Aug 2023 01:28:15 -0000 --P40TQ96qqG+j+U/4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 02, 2023 at 01:27:24AM +0300, Daniel Lipshitz wrote: > Your research is not thorough and reaches an incorrect conclusion. >=20 > As stated many times - we service payment processors and some merchants > directly - Coinspaid services multiple merchants and process a > significant amount of BTC they are a well known and active in the space - > as I provided back in December 2022 a email from Max the CEO of Coinspaid > confirming their use of 0-conf as well as providing there cluster address= es > to validate there deposit flows see here again - > https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-December/021= 239.html > - if this is not sufficient then please email support@coinspaid.com and a= sk > to be connected to Max or someone from the team who can confirm Conspaid = is > clients of GAP600. Max also at the time was open to do a call, I can check > again now and see if this is still the case and connect you. >=20 > That on its own is enough of a sample to validate our statistics. Why don't you just give me an example of some merchants using Coinspaid, and another example using Coinpayments, who rely on unconfirmed transactions? If those merchants actually exist it should be very easy to give me some names= of them. Without actual concrete examples for everyone to see for themselves, why sh= ould we believe you? > I have also spoken to Changelly earlier today and they offered to email p= ro > @ changelly.com and they will be able to confirm GAP600 as a service Emailed; waiting on a reply. > provider. Also please send me the 1 trx hash you tested and I can see if = it > was queried to our system and if so offer some info as to why it wasnt > approved. Also if you can elaborate how you integrated with Changelly - I > can check with them if that area is not integrated with GAP600. Why don't you just tell me exactly what service Changelly offers that relie= s on unconfirmed transactions, and what characteristics would meet GAP600's risk criteria? I and others on this mailing list could easily do test transactio= ns if you told us what we can actually test. If your service actually works, t= hen you can safely provide that information. I'm not going to give you any exact tx hashes of transactions I've already done, as I don't want to cause any problems for the owners of the accounts I borrowed for testing. Given your lack of honesty so far I have every reason= to believe they might be retalliated against in some way. > As the architect of such a major change to the status of 0-conf > transactions I would think you would welcome the opportunity to speak to > business and users who actual activities will be impacted by full RBF > becoming dominant. Funny how you say this, without actually giving any concrete examples of businesses that will be affected. Who exactly are these businesses? Payment processors obviously don't count. =20 > Are you able to provide the same i.e emails and contacts of people at > the mining pools who can confirm they have adopted FULL RBF ? I've already had multiple mining pools complain to me that they and their employees have been harassed over full-rbf, so obviously I'm not going to provide you with any private contact information I have. There's no need to expose them to further harassment. If you actually offered an unconfirmed transaction guarantee service, with = real customers getting an actual benefit, you'd be doing test transactions frequently and would already have a very good idea of what pools do full-rb= f. Why don't you already have this data? --=20 https://petertodd.org 'peter'[:-1]@petertodd.org --P40TQ96qqG+j+U/4 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmTJsSMACgkQLly11TVR LzefSxAAprUW+PiRM4oUhssZF6V6AWooUtokyvzAPpijV2/tbO7Xg/o4pNiMLGhH fSzkTDh6cOMTmUacX126BfKPCw07aRsSBAgH8J9YeNFL/vaNB6STWR9ntGZz8dJY SIcw7XNmWvdj1gTRpXd5zEvBOn9sL5T7YHZ/vk7CkjAeejhLbwoLd4OGlY5iM+hI fjXwJ3FzXsOYO1kqa588GWx4e82BQ1EYslqmGIGIiQ1U1aK61UZA7Q77aLFxhUsJ sTXyuwcKFlHiW7u77T2WgUcEi1otIgqjmdljpFu/tJ6HjzYrqe+SwN8SCcrQ7DlM wUqal5J8SzJlLNesJwtYDXGowlhZ8Q6vmuTU4Ews1S50FonwbIwKbtV4NpzLaHjr UkNprOcwLoMF0I3uZEvqij0Ukz/S/GMo1YLhzwk2JFGF5SLmfs9L+xePoFwI5Gz6 /6FqyJQcjdMl/8qCl8ABNGPNdNgt0S0yG5udTqtDMv6/EUpZbnKWlwRZKNY8bODh O2aBcE5EUHKCPhqEkGOiFLYWDSwX7Fhc3ZRErG+J4VAKOA9Yb6IUifI8O1bGptOK cdZH1U7UJfsHYusDUs4yFNmaQzO1Gk+eQ3cXw7oLJ5kgX/N4pk7micpw8Kq1IU8A sz2Nf9XtvsqW6eIRvYpjcywhDOSZSHV4aQ4zrXcwGiXA+lZajrg= =80Vf -----END PGP SIGNATURE----- --P40TQ96qqG+j+U/4--