public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Dave Scotese <dscotese@litmocracy•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] OP_CHECKWILDCARDSIGVERIFY or "Wildcard Inputs" or "Coalescing Transactions"
Date: Tue, 24 Nov 2015 15:28:33 -0800	[thread overview]
Message-ID: <CAGLBAhd-6NbxppFdqNVSQ5ot_GX12eL8P2-qVe7_dZcUfHYv6w@mail.gmail.com> (raw)
In-Reply-To: <CABaSBaxKJjEd2e9hrnzyS57-YHspqCv9PiSH4XccqSZJMQG6qg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1946 bytes --]

What is required to spend bitcoin is that input be provided to the UTXO
script that causes it to return true.  What Chris is proposing breaks the
programmatic nature of the requirement, replacing it with a requirement
that the secret be known.  Granted, the secret is the only requirement in
most cases, but there is no built-in assumption that the script always
requires only that secret.

This idea could be applied by having the wildcard signature apply to all
UTXOs that are of a standard form and paid to a particular address, and be
a signature of some kind of message to that effect.  I imagine the cost of
re-scanning the UTXO set to find them all would justify a special extra
mining fee for any transaction that used this opcode.

Please be blunt about any of my own misunderstandings that this email makes
clear.

On Tue, Nov 24, 2015 at 1:51 PM, Bryan Bishop via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:

> On Tue, Nov 24, 2015 at 11:34 AM, Chris Priest via bitcoin-dev <
> bitcoin-dev@lists•linuxfoundation.org> wrote:
>
>> **OP_CHECKWILDCARDSIGVERIFY**
>
>
> Some (minor) discussion of this idea in -wizards earlier today starting
> near near "09:50" (apologies for having no anchor links):
> http://gnusha.org/bitcoin-wizards/2015-11-24.log
>
> - Bryan
> http://heybryan.org/
> 1 512 203 0507
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>


-- 
I like to provide some work at no charge to prove my value. Do you need a
techie?
I own Litmocracy <http://www.litmocracy.com> and Meme Racing
<http://www.memeracing.net> (in alpha).
I'm the webmaster for The Voluntaryist <http://www.voluntaryist.com> which
now accepts Bitcoin.
I also code for The Dollar Vigilante <http://dollarvigilante.com/>.
"He ought to find it more profitable to play by the rules" - Satoshi
Nakamoto

[-- Attachment #2: Type: text/html, Size: 3299 bytes --]

  reply	other threads:[~2015-11-24 23:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 17:34 Chris Priest
2015-11-24 20:32 ` Gavin Andresen
2015-11-24 21:01   ` Chris Priest
2015-11-24 21:51 ` Bryan Bishop
2015-11-24 23:28   ` Dave Scotese [this message]
2015-11-24 23:48     ` Chris Priest
2015-11-25  0:38       ` Jannes Faber
2015-11-25  1:26         ` Chris Priest
2015-11-25 14:16           ` Erik
2015-11-25 15:41             ` Trevin Hofmann
2015-11-25 17:03             ` Dave Scotese

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=CAGLBAhd-6NbxppFdqNVSQ5ot_GX12eL8P2-qVe7_dZcUfHYv6w@mail.gmail.com \
    --to=dscotese@litmocracy$(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