From: Javier Mateos <javierpmateos@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Re: [BIP Proposal] Utreexo Nodes
Date: Tue, 29 Jul 2025 19:33:37 -0700 (PDT) [thread overview]
Message-ID: <e007ba14-c66d-4e8c-9b9e-adb2c4025be5n@googlegroups.com> (raw)
In-Reply-To: <3452b63c-ff2b-4dd9-90ee-83fd9cedcf4an@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1800 bytes --]
Hi Calvin, Tadge, Davidson,
Thanks for sharing this important work ...it's exciting to see Utreexo
maturing into a full BIP proposal. The modular split into accumulator,
validation, and P2P layers is very clean and helpful for review.
After a quick conceptual and implementation-level analysis, I believe
there's a critical detail missing from the current accumulator spec: a
deterministic order for processing UTXO deletions and additions per block.
Aside from that, the spec is well written and shows deep consideration.
Best regards,
El martes, 29 de julio de 2025 a las 20:26:42 UTC-3, Calvin Kim escribió:
> Hello all,
>
> Tadge Dryja, Davidson Souza, and I would like to propose 3 BIPs describing
> Utreexo, a consensus-compatible (non-soft fork) way to send and verify
> transactions without storing the full UTXO set.
>
> The 3 BIPs are for:
>
> 1. The specification of the Utreexo accumulator.
> 2. The specification of Bitcoin block and tx validation using the
> Utreexo accumulator.
> 3. The peer to peer networking changes required to enable Utreexo
> nodes.
>
>
> We are currently looking for conceptual review. Do note that the documents
> are not final, and they will be updated.
>
> All of the BIPs can be found here: https://github.com/utreexo/biptreexo
>
> We thank you in advance for your time and consideration.
>
> Best,
> Calvin
>
--
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 visit https://groups.google.com/d/msgid/bitcoindev/e007ba14-c66d-4e8c-9b9e-adb2c4025be5n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 5185 bytes --]
next prev parent reply other threads:[~2025-07-30 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 23:20 [bitcoindev] [BIP Proposal] Utreexo Nodes Calvin Kim
2025-07-30 2:33 ` Javier Mateos [this message]
2025-07-30 14:20 ` [bitcoindev] " K Calvin
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=e007ba14-c66d-4e8c-9b9e-adb2c4025be5n@googlegroups.com \
--to=javierpmateos@gmail.com \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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