From: Mike Brooks <m@ib•tc>
To: ZmnSCPxj <ZmnSCPxj@protonmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Smaller Transactions with PubRef
Date: Sat, 1 Aug 2020 18:12:16 -0700 [thread overview]
Message-ID: <CALFqKjSrQ260XfYtdvd9N=ZKZvJqE2iz+reGtBNpq++br9S1ig@mail.gmail.com> (raw)
In-Reply-To: <1cxOISncF4dES_Ijm5FJUhwUAzBupnLPiv3qnU20as76zMMhVyggkg1hphq4ehuqEFK_H88TBbfI2pKbLWzzx7E6kOUXeC-yOcfrOkg3uAY=@protonmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1014 bytes --]
Hey ZmnSCPxj,
Re-orgs should be solved in a different way.
Best Regards,
Micahel
On Sat, Aug 1, 2020 at 5:36 PM ZmnSCPxj <ZmnSCPxj@protonmail•com> wrote:
> Good morning Mike,
>
> Hard NAK.
>
> The responses to the original posting already pointed out important
> problems with this:
>
> * Encourages address reuse, hurting fungibility and privacy.
> * Prevents pruning, since access to previous blocks must always be
> available in order to validate.
> * Optimized implementation requires creating yet another index to previous
> block data, increasing requirements on fullnodes.
> * Requires SCRIPT to be re-evaluated on transactions arriving in
> newblocks, to protect against reorgs of the chaintip, and in particular
> `OP_PUBREF` references to near the chaintip.
>
> None of these issues have been addressed in your current proposal.
> The proposal looks at clients only, without considering what validators
> have to implement in order to validate new blocks with this opcode.
>
> Regards,
> ZmnSCPxj
>
[-- Attachment #1.2: Type: text/html, Size: 1403 bytes --]
[-- Attachment #2: Floating-Point Nakamoto Consensus.pdf --]
[-- Type: application/pdf, Size: 70769 bytes --]
next prev parent reply other threads:[~2020-08-02 1:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 5:09 Mike Brooks
2020-08-02 0:36 ` ZmnSCPxj
2020-08-02 1:12 ` Mike Brooks [this message]
2020-08-02 14:22 ` ZmnSCPxj
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='CALFqKjSrQ260XfYtdvd9N=ZKZvJqE2iz+reGtBNpq++br9S1ig@mail.gmail.com' \
--to=m@ib$(echo .)tc \
--cc=ZmnSCPxj@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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