From: "Sjors Provoost" <sjors@sprovoost•nl>
To: eric@voskuil•org, 'jeremy' <jeremy.l.rubin@gmail•com>,
"'Bitcoin Development Mailing List'"
<bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Consensus Cleanup BIP draft
Date: Sat, 29 Mar 2025 12:02:32 +0100 [thread overview]
Message-ID: <19f6a854-674a-4e4d-9497-363af306e3a0@app.fastmail.com> (raw)
In-Reply-To: <065901dba01b$2164fff0$642effd0$@voskuil.org>
On Fri, Mar 28, 2025, at 20:53, eric@voskuil•org wrote:
> Hi Jeremy,
>
>> I'm also personally strongly against removing 64-byte transactions. It's a wart
[...]
> But more to the point, it does not solve any of the problems that were
> originally provided as justification, apart from making it slightly
> simpler to implement an SPV wallet (no need to get the coinbase tx).
It's important to keep in mind that "SPV wallet" also includes any kind of automated bridge that requires knowledge of Bitcoin transaction inclusion. What's simple to implement in a rust-bitcoin wallet may be extremely hard in a smart contract. Or maybe it's indeed trivial.
It could be a useful illustration if someone implements such a bridge using any of the proposed covenant op codes, and shows the difference in complexity between having the 64 byte limit and not having it.
I do agree that people should read these other threads to form an opinion on the topic. And the BIP should point to these threads if it doesn't already.
- Sjors
--
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/19f6a854-674a-4e4d-9497-363af306e3a0%40app.fastmail.com.
next prev parent reply other threads:[~2025-03-31 9:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 17:14 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-03-27 10:46 ` Chris Stewart
2025-03-27 17:54 ` /dev /fd0
2025-03-27 19:05 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-03-27 20:45 ` jeremy
2025-03-27 21:38 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-03-28 9:23 ` Sjors Provoost
2025-03-28 11:02 ` Chris Stewart
2025-03-28 12:48 ` Sjors Provoost
2025-03-28 13:54 ` Chris Stewart
2025-03-28 14:07 ` Sjors Provoost
2025-03-28 19:53 ` eric
2025-03-29 11:02 ` Sjors Provoost [this message]
2025-03-31 11:00 ` Anthony Towns
2025-03-31 15:29 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-03-31 20:09 ` eric
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=19f6a854-674a-4e4d-9497-363af306e3a0@app.fastmail.com \
--to=sjors@sprovoost$(echo .)nl \
--cc=bitcoindev@googlegroups.com \
--cc=eric@voskuil$(echo .)org \
--cc=jeremy.l.rubin@gmail$(echo .)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