From: Greg Sanders <gsanders87@gmail•com>
To: Peter Todd <pete@petertodd•org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Relaxing minimum non-witness transaction size policy restriction
Date: Wed, 26 Oct 2022 15:09:38 -0400 [thread overview]
Message-ID: <CAB3F3Dtr79W55Fdt73B-VvgN4WJVGKMGgGch-tEkZMoH9+SqgQ@mail.gmail.com> (raw)
In-Reply-To: <Y1HkG/ai+241I11S@petertodd.org>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
As there has been some feedback to the same effect, I've opened a competing
PR for separate evaluation here:
https://github.com/bitcoin/bitcoin/pull/26398
Please give feedback if anyone has any.
On Thu, Oct 20, 2022 at 8:13 PM Peter Todd <pete@petertodd•org> wrote:
> On Thu, Oct 20, 2022 at 08:07:54PM -0400, Greg Sanders wrote:
> > I don't doubt the use case(it's why I opened the issue!). I didn't want
> the
> > proposal to die in case people found it odd that 61, 62, 63, but not 64
> > bytes ended up being broadcast able.
> >
> > Perhaps this is not an issue, especially since this isn't a consensus
> > change like the Great Consensus Cleanup. Willing to change my proposal
> and
> > PR if people have no strong objections.
>
> I think it's fine if we only restrict 64 bytes. We have a specific reason
> to do
> that and it's ok if we just tell people that. Only fairly-technical
> use-cases
> are affected anyway.
>
> --
> https://petertodd.org 'peter'[:-1]@petertodd.org
>
[-- Attachment #2: Type: text/html, Size: 1582 bytes --]
prev parent reply other threads:[~2022-10-26 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 12:50 Greg Sanders
[not found] ` <PS2P216MB1089C3131115B700C840BEFB9D239@PS2P216MB1089.KORP216.PROD.OUTLOOK.COM>
2022-10-11 13:14 ` Greg Sanders
2022-10-20 23:21 ` Peter Todd
2022-10-21 0:07 ` Greg Sanders
2022-10-21 0:13 ` Peter Todd
2022-10-26 19:09 ` Greg Sanders [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=CAB3F3Dtr79W55Fdt73B-VvgN4WJVGKMGgGch-tEkZMoH9+SqgQ@mail.gmail.com \
--to=gsanders87@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=pete@petertodd$(echo .)org \
/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