public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
To: Mike Brooks <m@ib.tc>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Smaller Transactions with PubRef
Date: Sun, 02 Aug 2020 00:36:08 +0000	[thread overview]
Message-ID: <1cxOISncF4dES_Ijm5FJUhwUAzBupnLPiv3qnU20as76zMMhVyggkg1hphq4ehuqEFK_H88TBbfI2pKbLWzzx7E6kOUXeC-yOcfrOkg3uAY=@protonmail.com> (raw)
In-Reply-To: <CALFqKjTDcsD4xpc-TryTRCNnCJivyqkU9dv0ff2emP5kxZF1bA@mail.gmail.com>

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


  reply	other threads:[~2020-08-02  0:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-01  5:09 [bitcoin-dev] Smaller Transactions with PubRef Mike Brooks
2020-08-02  0:36 ` ZmnSCPxj [this message]
2020-08-02  1:12   ` Mike Brooks
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='1cxOISncF4dES_Ijm5FJUhwUAzBupnLPiv3qnU20as76zMMhVyggkg1hphq4ehuqEFK_H88TBbfI2pKbLWzzx7E6kOUXeC-yOcfrOkg3uAY=@protonmail.com' \
    --to=zmnscpxj@protonmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=m@ib.tc \
    /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