From: Anthony Towns <aj@erisian•com.au>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] [BIP Proposal] Block template sharing
Date: Wed, 13 Aug 2025 10:18:09 +1000 [thread overview]
Message-ID: <aJvZwR_bPeT4LaH6@erisian.com.au> (raw)
Hi all,
I did a write up with a proof of concept of the idea of sharing
block templates with peers, particularly in order to improve compact
block relay when miners and nodes have differing mempool policies. It's
at:
https://delvingbitcoin.org/t/sharing-block-templates/1906
I've now also written up a draft BIP specifying the p2p messages that
uses, which can be found here:
https://github.com/ajtowns/bips/blob/202508-sendtemplate/bip-ajtowns-sendtemplate.md
Review welcome! If you prefer to make comments via a github review
rather than here or on delving, I've opened a PR on my own repo at
https://github.com/ajtowns/bips/pull/7 which you could use.
Cheers,
aj
--
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/aJvZwR_bPeT4LaH6%40erisian.com.au.
reply other threads:[~2025-08-18 14:44 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=aJvZwR_bPeT4LaH6@erisian.com.au \
--to=aj@erisian$(echo .)com.au \
--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