-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Mon, Jun 10, 2013 at 5:43 PM, Peter Todd <p...@petertodd.org> wrote: > On Mon, Jun 10, 2013 at 01:25:05PM -0400, Alan Reiner wrote: >> to sign votes. Not only that, but it would require them to reveal their >> public key, which while isn't technically so terrible, large amounts of >> money intended to be kept in storage for 10+ years will prefer to avoid >> any exposure at all, in the oft-chance that QCs come around a lot >> earlier than we expected. Sure, the actual risk should be pretty much >> non-existent, but some of the most paranoid folks are probably the same >> ones who have a lot of funds and want 100.00% of the security that is >> possible. They will see this as wildly inconvenient. > > Solving that problem is pretty easy actually: just add a voting only > public key to your outputs. Specifically you would have an opcode called > something like "OP_VOTE" and put a code-path in your script that only > executes for that specific key.
Rather than "OP_VOTE" all you really need is the "spending tx matches a template" functionality that has been proposed for many other things. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBCAAGBQJRvLIoAAoJEEWCsU4mNhiPdtoIAKOeEwtWXw6fNKbSN0miGmcQ rHxgoEh5EAPsbs0hkCRpsVF7OjvmAftOn0Z0K0X/a4UFVHI64bvvGUg0brmAMnh3 ha4Mu/o7UwxwVJmmd6vpUw4smjbQrKbRzheXXQKUsDG2HOmRzMabFjJG1F20mPdg RobwYG49fKLcjAfqqTjOwSQE5KBjrugAUo32OUJWHZyNR5E3JYUXRHseHCfQ+1Fd VOQ8rWA4OaqwiX7PXdrNMWXc7Ab1dK7j9U7n4FgzCGIJjAek2dGbYLdrjftGKI+z Vje7o/RCJFLkJW5cC/wDoB/58XyJuvsvGOBAjvz01UrengUiapkhLRjKQwbveEo= =P0Hm -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
