{"type":"rich","version":"1.0","author_name":"npub15z6e9t07ugx267aj3s3c487pln852ydytzlgu0vkkqxfznyvx4jq4kn0zr","author_url":"https://nostr.ae/npub15z6e9t07ugx267aj3s3c487pln852ydytzlgu0vkkqxfznyvx4jq4kn0zr","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2013-06-04\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n\n\u003e I'm one of the people experimenting in this area.  I've long argued\n\u003e that a zero-output transaction should be permitted -- 100% miner fee\n\u003e -- as an elegant proof of sacrifice.  Unfortunately that requires a\n\u003e hard fork.  Also, for most people, it seems likely that a change\n\u003e transaction would be generated.  That, then, would generate an\n\u003e already-standard transaction, where inputs \u003e outputs.\n\n100% miner fee is not a proof of anything because the miner could have created\nthat transaction for themselves. You must have proof that all miners had an\nequal opportunity at collecting the fee, and the only way to do that is by\nPeter's announce-commit protocol, or his unspendable until after n blocks\nproposal.\n\nAlso the idea of a zero-output transaction is silly. In almost all cases you\nare making the sarifice to link that act to an identity, and linking that act\nto arbitrary data is far more flexible than any scheme relying on the pubkeys\nthat paid for the transaction. With a arbitrary data you can slice up the\nsacrifice for instance with a merkle-sum-tree, as well as hide what the\nsacrifice was for to preserve anonymity. The extra cost in size of the provably\nunspendable OP_RETURN scriptPubKey is minimal for the rare time when it isn't\nrequired.\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.11 (GNU/Linux)\n\niQEcBAEBCAAGBQJRrf/BAAoJEEWCsU4mNhiP7+MH/RGfo2k+Zd0VoGzv3KSTzBrM\nauK9Do2fYp2YvMnT/JFYbz2MgbTcCiKGyZfxjaH+zrqdTFgkgAE53midIv/Rd5/w\nkjjifJuqw5AyIN6ANA1TuLQ64elPOXXymsaMqWO8ou0angG6DBI/LZZEG7SXM7+I\nJwk3MXLhFswvvuRif4G2C9v29WqSj4XRxxl3o63ziSYvZPPCHLYHAL9BJaMpDhaw\nLxebM088RofzJAoGL1QIeQhDS3aAK4jKSZtJ/6+fwYZQB2Qc3sa1v9IAcCQHE+M3\n6oQY0tzEEFg9+xdnSM7J6pW7qW28nFS8Fdr6UkUUlwhI5c4KnIKCtQa3o1mYDFE=\n=SHWS\n-----END PGP SIGNATURE-----"}