From: Luke Dashjr <luke@dashjr•org>
To: kcalvinalvin <calvin@kcalvinalvin•info>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Using service bit 24 for utreexo signaling in testnet and signet
Date: Thu, 2 Mar 2023 13:20:35 -0500 [thread overview]
Message-ID: <a9357869-2eb0-0e7d-f0c4-536404930e48@dashjr.org> (raw)
In-Reply-To: <vymiNsSrjFPbfpdd3z6BMnIqqJ2cC_3J224jD7Rv_7I7bPt0HHufyisjCe67tSGBiluouQoj5wuNVKA12KSmC3pS9Q6NjBSH4OmUbI8U7wQ=@kcalvinalvin.info>
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
next prev parent reply other threads:[~2023-03-02 18:29 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 [this message]
2023-03-02 21:05 ` Peter Todd
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=a9357869-2eb0-0e7d-f0c4-536404930e48@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=calvin@kcalvinalvin$(echo .)info \
/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