public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: K Calvin <ccychc@gmail.com>
To: Javier Mateos <javierpmateos@gmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: [BIP Proposal] Utreexo Nodes
Date: Wed, 30 Jul 2025 23:20:27 +0900	[thread overview]
Message-ID: <CAGYLYJQPi34eACgJ-7wY+CcdaF-UOrWc9Cs0D89U0+gYt8SwZg@mail.gmail.com> (raw)
In-Reply-To: <e007ba14-c66d-4e8c-9b9e-adb2c4025be5n@googlegroups.com>

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

Hey Javier,

Thanks for taking the time to do the conceptual analysis.

As for the missing detail you mentioned, I think this section in the
validation BIP has that covered:
https://github.com/utreexo/biptreexo/blob/main/utreexo-validation-bip.md#order-of-operations

We wanted the accumulator BIP free from any Bitcoin related operations.
Thus anything that has to do with validation of Bitcoin blocks will be
found in the validation BIP.

Best,
Calvin

On Wed, Jul 30, 2025 at 6:22 PM Javier Mateos <javierpmateos@gmail.com>
wrote:

> 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
> <https://groups.google.com/d/msgid/bitcoindev/e007ba14-c66d-4e8c-9b9e-adb2c4025be5n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CAGYLYJQPi34eACgJ-7wY%2BCcdaF-UOrWc9Cs0D89U0%2BgYt8SwZg%40mail.gmail.com.

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

      reply	other threads:[~2025-07-30 16:06 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 ` [bitcoindev] " Javier Mateos
2025-07-30 14:20   ` K Calvin [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=CAGYLYJQPi34eACgJ-7wY+CcdaF-UOrWc9Cs0D89U0+gYt8SwZg@mail.gmail.com \
    --to=ccychc@gmail.com \
    --cc=bitcoindev@googlegroups.com \
    --cc=javierpmateos@gmail.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