Using service bit 24 for utreexo signaling in testnet and signet

Using service bit 24 for utreexo signaling in testnet and signet
2023-03-02 18:20 ` Luke Dashjr
  
From: kcalvinalvin @ 2023-03-02  6:55 UTC (permalink / raw)
  To: bitcoin-dev

[-- Attachment #1: Type: text/plain, Size: 650 bytes --]

Hello all,

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 as requested by the comment in protocol.h in bitcoind (https://github.com/bitcoin/bitcoin/blob/74981aa02d2b14ad1c0b82d1eb09cf3169eaa8ae/src/protocol.h#L295-L301). There are plans to release binaries for the utreexo node (github.com/utreexo/utreexod) in the next few months so that power users can try it out. I have no plans to release binaries for mainnet yet.

Do let me know if someone else is using the same bit to signal for something else and we can coordinate accordingly.

Best,
Calvin

[-- Attachment #2: Type: text/html, Size: 1004 bytes --]

 permalink raw reply	[|nested]
2023-03-02  6:55 [bitcoin-dev] Using service bit 24 for utreexo signaling in testnet and signet kcalvinalvin

  2023-03-02 21:05   ` Peter Todd
  
From: Luke Dashjr @ 2023-03-02 18:20 UTC (permalink / raw)
  To: kcalvinalvin, Bitcoin Protocol Discussion

This sounds like something that should be written up as a BIP and use a 
normal service bit assignment...?

Luke


On 3/2/23 01:55, kcalvinalvin via bitcoin-dev wrote:
> Hello all,
>
> 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 as requested by the comment in protocol.h in 
> bitcoind (https://github.com/bitcoin/bitcoin/blob/74981aa02d2b14ad1c0b82d1eb09cf3169eaa8ae/src/protocol.h#L295-L301). 
> There are plans to release binaries for the utreexo node 
> (github.com/utreexo/utreexod) in the next few months so that power 
> users can try it out. I have no plans to release binaries for mainnet 
> yet.
>
> Do let me know if someone else is using the same bit to signal for 
> something else and we can coordinate accordingly.
>
> Best,
> Calvin
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


 permalink raw reply	[|nested]
2023-03-02 18:20 ` Luke Dashjr

  
From: Peter Todd @ 2023-03-02 21:05 UTC (permalink / raw)
  To: Luke Dashjr, Bitcoin Protocol Discussion,
	Luke Dashjr via bitcoin-dev, kcalvinalvin



On March 2, 2023 6:20:35 PM GMT, Luke Dashjr via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>This sounds like something that should be written up as a BIP and use a normal service bit assignment...?

The purpose of the experimental service bits is experiments. If the details of utreexo aren't nailed down and may change, an experimental service bit makes sense.

Bit 24 is fine and AFAIK unused at the moment; full-rbf is using bit 26: https://github.com/petertodd/bitcoin/commit/c15b8d70778238abfa751e4216a97140be6369af#diff-8e2ffc8fe0e0847a6aac311a93b2faeebd2d76ddb2c81741bb8cf7448287807eR297

>Luke
>
>
>On 3/2/23 01:55, kcalvinalvin via bitcoin-dev wrote:
>> Hello all,
>> 
>> 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 as requested by the comment in protocol.h in bitcoind (https://github.com/bitcoin/bitcoin/blob/74981aa02d2b14ad1c0b82d1eb09cf3169eaa8ae/src/protocol.h#L295-L301). There are plans to release binaries for the utreexo node (github.com/utreexo/utreexod) in the next few months so that power users can try it out. I have no plans to release binaries for mainnet yet.
>> 
>> Do let me know if someone else is using the same bit to signal for something else and we can coordinate accordingly.
>> 
>> Best,
>> Calvin
>> 
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists•linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>_______________________________________________
>bitcoin-dev mailing list
>bitcoin-dev@lists•linuxfoundation.org
>https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


 permalink raw reply	[|nested]