Re: [Bitcoin-development] Opcode whitelist for P2SH?

2013-07-29 Thread Peter Todd
On Sun, Jul 28, 2013 at 07:39:08PM +, John Dillon wrote: > Peter Todd recently came up with two related, and IMO very good, uses for > non-standard transactions to implement both oracles and one-time-password > protection of wallet funds. While the wallet fund case could be implemented as > onl

Re: [Bitcoin-development] Opcode whitelist for P2SH?

2013-07-29 Thread Peter Todd
On Mon, Jul 29, 2013 at 02:00:10AM -0400, Jeff Garzik wrote: > On Mon, Jul 29, 2013 at 1:17 AM, Luke-Jr wrote: > > On Sunday, July 28, 2013 7:39:08 PM John Dillon wrote: > >> What are your thoughts on creating a whitelist for specific opcodes that > >> would apply to scripts serialized using P2SH,

Re: [Bitcoin-development] Opcode whitelist for P2SH?

2013-07-28 Thread Jeff Garzik
On Mon, Jul 29, 2013 at 1:17 AM, Luke-Jr wrote: > On Sunday, July 28, 2013 7:39:08 PM John Dillon wrote: >> What are your thoughts on creating a whitelist for specific opcodes that >> would apply to scripts serialized using P2SH, retaining the existing >> standard whitelist for scriptPubKeys? (I w

Re: [Bitcoin-development] Opcode whitelist for P2SH?

2013-07-28 Thread Luke-Jr
On Sunday, July 28, 2013 7:39:08 PM John Dillon wrote: > What are your thoughts on creating a whitelist for specific opcodes that > would apply to scripts serialized using P2SH, retaining the existing > standard whitelist for scriptPubKeys? (I would still recommend dropping > pay-to-pubkey and pay-

[Bitcoin-development] Opcode whitelist for P2SH?

2013-07-28 Thread John Dillon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Peter Todd recently came up with two related, and IMO very good, uses for non-standard transactions to implement both oracles and one-time-password protection of wallet funds. While the wallet fund case could be implemented as only a single standard