From: Gregory Maxwell <gmaxwell@gmail•com>
To: Sergio Lerner <sergiolerner@certimix•com>
Cc: bitcoin-development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP: Voluntary deposit bonds
Date: Tue, 30 Dec 2014 18:28:54 +0000 [thread overview]
Message-ID: <CAAS2fgRxysRqkSxqbF8Y9u2ptfVjX0PU6W85jD-RjSn9hUqNBA@mail.gmail.com> (raw)
In-Reply-To: <54A2D1F4.9050306@certimix.com>
On Tue, Dec 30, 2014 at 4:25 PM, Sergio Lerner
<sergiolerner@certimix•com> wrote:
> Slight off-topic:
> That looks like an abuse of the VM. Even P2SH is an abuse of the VM.
> Gavin's OP_EVAL (hard-fork) should had been chosen. I'm taking about a
> simple change that goes along the lines of Satoshi's original design.
> Bitcoin was a beautiful design, and extra complexity is making it ugly.
> We need Bitcoin to be simple to understand for new programmers so they
> can keep the project going. It doesn't help the project that one needs
> to be a guru to code for Bitcoin.
Sergio there is no "abuse" there, OP_NOP3 in that case would be
redefined to OP_COINBASE_FOO_CONSISTENCY.
(I say FOO because it's not clear what rule you actually hope to apply there.)
What you suggested has no purpose by itself: it would need an
additional change which overlays functionality in order to actually do
something. Such a change would likely be "ugly"-- it's easy to be
elegant when you do nothing.
next prev parent reply other threads:[~2014-12-30 18:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 19:21 Sergio Lerner
2014-12-29 21:10 ` Mike Hearn
2014-12-29 21:34 ` Justus Ranvier
2014-12-30 10:47 ` Jorge Timón
2014-12-30 13:16 ` Justus Ranvier
2014-12-29 22:36 ` Luke Dashjr
2014-12-29 22:35 ` Luke Dashjr
2014-12-30 4:51 ` Gregory Maxwell
2014-12-30 16:25 ` Sergio Lerner
2014-12-30 18:28 ` Gregory Maxwell [this message]
2014-12-31 18:25 ` Stephen Morse
2015-01-03 3:48 ` Peter Todd
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=CAAS2fgRxysRqkSxqbF8Y9u2ptfVjX0PU6W85jD-RjSn9hUqNBA@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=sergiolerner@certimix$(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