From: Calvin Kim <ccychc@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Utreexod beta release
Date: Tue, 7 May 2024 03:33:10 -0700 (PDT) [thread overview]
Message-ID: <d5f47120-3397-4f56-93ca-dd310d845f3cn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2411 bytes --]
Hi all,
Utreexod, a full node implementation with Utreexo accumulator support, is
now
available for general testing by the public. Notable features are:
- Implementation of efficient Utreexo accumulators with an improved deletion
algorithm from the Utreexo paper.
- Efficient P2P transaction relay with support for caching utreexo proofs
for
mempool transactions.
- Quick sync to the tip of the blockchain with AssumeUtreexo.
- Built in wallet support (with BDK wallet).
- Electrum personal server support for usage with other wallets.
It’s important to note that the code and protocol is not peer reviewed.
Using
the node for production usage or for non-negligible amounts of Bitcoin is
not
recommended. There will also be breaking changes requiring frequent updates
as
well. Utreexod is also based off of btcd
(https://github.com/btcsuite/btcd), a
bitcoin node implementation in Go. Because of this, there may be consensus
incompatibilities either as a result of a btcd bug or a Bitcoin Core bug.
Also note that there are not many Utreexo nodes on the network. It may take
a
while for the node to find a Utreexo node it can sync off of. To help
bootstrap
the network, consider running an archival node or a bridge node. Refer to
the
readme on the github (https://github.com/utreexo/utreexod) page for
instructions
on how to run a bridge node or an archival utreexo node.
Prebuilt static binaries for Linux, MacOS, and Windows are available at
(https://github.com/utreexo/utreexod/releases/)
Huge thanks to HRF for funding my work for this release. Without the
support I
wouldn’t have been able to focus on Utreexo.
Also thanks to all the folks that directly contributed to the release:
Aaron Chew
Aarush Bhat
Dan Cline
Davidson Souza
devrandom
Dipto Chakrabarty
Evan Lin
Janus Troelsen
João Dias
Matt Drollette
Neha Narula
Niklas Goëgge
Rueben DeLeon
Sebastian Falbesoner
Tadge Dryja
Thebora Kompanioni
tnakagawa
yyforyongyu
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/d5f47120-3397-4f56-93ca-dd310d845f3cn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2864 bytes --]
reply other threads:[~2024-05-07 10:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d5f47120-3397-4f56-93ca-dd310d845f3cn@googlegroups.com \
--to=ccychc@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
/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