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


_______________________________________________
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 and Meme Racing (in alpha).
I'm the webmaster for The Voluntaryist which now accepts Bitcoin.
I also code for The Dollar Vigilante.
"He ought to find it more profitable to play by the rules" - Satoshi Nakamoto