public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Murch <murch@murch.one>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] [BIP Proposal] Utreexo Nodes
Date: Wed, 6 Aug 2025 15:36:33 -0700	[thread overview]
Message-ID: <a713fdee-f8d3-443a-ad16-8884ffa9abe5@murch.one> (raw)
In-Reply-To: <3452b63c-ff2b-4dd9-90ee-83fd9cedcf4an@googlegroups.com>

Hello Calvin and all,

Thank you for sharing your drafts. I skimmed your proposals and found 
them to be shaping up nicely. I didn’t notice anything worth conceptual 
feedback at this time, but will have plenty comments later in the 
process when they are more fitting. Obviously, utreexo has had a lot of 
discussion in the past already and these proposals are fairly close to 
the editorial requirements, so please feel free to open pull requests 
for the proposals whenever you feel ready to do so.

Cheers,
Murch

On 2025-07-29 16:20, Calvin Kim wrote:
> 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/3452b63c-ff2b-4dd9-90ee-83fd9cedcf4an%40googlegroups.com 
> <https://groups.google.com/d/msgid/bitcoindev/3452b63c-ff2b-4dd9-90ee-83fd9cedcf4an%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/a713fdee-f8d3-443a-ad16-8884ffa9abe5%40murch.one.


  parent reply	other threads:[~2025-08-06 23:24 UTC|newest]

Thread overview: 5+ 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
2025-08-06 22:36 ` Murch [this message]
2025-08-10  6:58   ` [bitcoindev] " Calvin Kim

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=a713fdee-f8d3-443a-ad16-8884ffa9abe5@murch.one \
    --to=murch@murch.one \
    --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