From: Peter Todd <pete@petertodd•org>
To: Luke Dashjr <luke@dashjr•org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Luke Dashjr via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org>,
kcalvinalvin <calvin@kcalvinalvin•info>
Subject: Re: [bitcoin-dev] Using service bit 24 for utreexo signaling in testnet and signet
Date: Thu, 02 Mar 2023 21:05:26 +0000 [thread overview]
Message-ID: <121124D0-060B-4093-98A4-7D96E7A41E8D@petertodd.org> (raw)
In-Reply-To: <a9357869-2eb0-0e7d-f0c4-536404930e48@dashjr.org>
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
prev parent reply other threads:[~2023-03-02 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 6:55 kcalvinalvin
2023-03-02 18:20 ` Luke Dashjr
2023-03-02 21:05 ` Peter Todd [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=121124D0-060B-4093-98A4-7D96E7A41E8D@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=calvin@kcalvinalvin$(echo .)info \
--cc=luke@dashjr$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox