Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 3E675C0032 for ; Thu, 2 Mar 2023 21:05:35 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 1953060BAC for ; Thu, 2 Mar 2023 21:05:35 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 1953060BAC 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=fm1 header.b=DasSG/Ls 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 smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A8tTRasE35D8 for ; Thu, 2 Mar 2023 21:05:31 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org BD50560BAE Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by smtp3.osuosl.org (Postfix) with ESMTPS id BD50560BAE for ; Thu, 2 Mar 2023 21:05:31 +0000 (UTC) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id E0F025C0186; Thu, 2 Mar 2023 16:05:28 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Thu, 02 Mar 2023 16:05:28 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=fm1; t=1677791128; x= 1677877528; bh=KOWP9kn1kD2ovtCth2k6Dxy4K322gO+IMi8Hx4+Bz4s=; b=D asSG/LsLaXoHRJuP3dpNwDRw5m6EJxKk43F1PDmAn9o6hXHkS3/gOn7/cXFiKCJU MfO7OqyiKa/QlRX38l0kFcxhdIUqthnlBT61/FFd9bMPVbwUoMcmMbjllWdx5/9x eSgNwucbAhPd5dnK2QDchTgTKFHHasUTKvTYiqWymjyFEFSUMOzkdIVYMIPki6f6 98iZpWWDM6eKEcclrq0YVoMQx/fsA36HyY2mLDTNd1yhEnMEhvUQUiiZk/EFJxqY D2OGalvt2hEn+e37AaZBSTJe75PoxpxISRexCdRUiOeBPbKhMf8+AhD71mQqwtw+ ChU9arwpW2Pqllz68ijmw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudeljedgudegfecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvufgfjghfkfggtgfgsehtqhhmtddtreejnecuhfhrohhmpefrvght vghrucfvohguugcuoehpvghtvgesphgvthgvrhhtohguugdrohhrgheqnecuggftrfgrth htvghrnhepgfeuledvudfflefhvdeufffgveehveejffefkeetleeugfeihfdujefggfeu ffffnecuffhomhgrihhnpehgihhthhhusgdrtghomhdplhhinhhugihfohhunhgurghtih honhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhr ohhmpehpvghtvgesphgvthgvrhhtohguugdrohhrgh X-ME-Proxy: Feedback-ID: i525146e8:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 2 Mar 2023 16:05:27 -0500 (EST) Date: Thu, 02 Mar 2023 21:05:26 +0000 From: Peter Todd To: Luke Dashjr , Bitcoin Protocol Discussion , Luke Dashjr via bitcoin-dev , kcalvinalvin User-Agent: K-9 Mail for Android In-Reply-To: References: Message-ID: <121124D0-060B-4093-98A4-7D96E7A41E8D@petertodd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [bitcoin-dev] Using service bit 24 for utreexo signaling in testnet and signet 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: Thu, 02 Mar 2023 21:05:35 -0000 On March 2, 2023 6:20:35 PM GMT, Luke Dashjr via bitcoin-dev wrote: >This sounds like something that should be written up as a BIP and use a n= ormal service bit assignment=2E=2E=2E? The purpose of the experimental service bits is experiments=2E If the deta= ils of utreexo aren't nailed down and may change, an experimental service b= it makes sense=2E Bit 24 is fine and AFAIK unused at the moment; full-rbf is using bit 26: h= ttps://github=2Ecom/petertodd/bitcoin/commit/c15b8d70778238abfa751e4216a971= 40be6369af#diff-8e2ffc8fe0e0847a6aac311a93b2faeebd2d76ddb2c81741bb8cf744828= 7807eR297 >Luke > > >On 3/2/23 01:55, kcalvinalvin via bitcoin-dev wrote: >> Hello all, >>=20 >> Wanted to tell the mailing list that I'll be using service bit 24 (1 <<= 24) to signal that nodes are Utreexo capable nodes on testnet and signet a= s requested by the comment in protocol=2Eh=C2=A0in bitcoind=C2=A0(https://g= ithub=2Ecom/bitcoin/bitcoin/blob/74981aa02d2b14ad1c0b82d1eb09cf3169eaa8ae/s= rc/protocol=2Eh#L295-L301)=2E There are plans to release binaries for the u= treexo node (github=2Ecom/utreexo/utreexod)=C2=A0in the next few months so = that power users can try it out=2E=C2=A0I have no=C2=A0plans to release bin= aries for mainnet yet=2E >>=20 >> Do let me know if someone else is using the same bit to signal for some= thing else and we can coordinate accordingly=2E >>=20 >> Best, >> Calvin >>=20 >> _______________________________________________ >> bitcoin-dev mailing list >> bitcoin-dev@lists=2Elinuxfoundation=2Eorg >> https://lists=2Elinuxfoundation=2Eorg/mailman/listinfo/bitcoin-dev >_______________________________________________ >bitcoin-dev mailing list >bitcoin-dev@lists=2Elinuxfoundation=2Eorg >https://lists=2Elinuxfoundation=2Eorg/mailman/listinfo/bitcoin-dev