<oembed><type>rich</type><version>1.0</version><author_name>npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2</author_name><author_url>https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2013-06-01&#xA;📝 Original message:Currently the most compact way (proof-size) to sacrifice Bitcoins that&#xA;does not involve making them unspendable is to create a anyone-can-spend&#xA;output as the last txout in the coinbase of a block:&#xA;&#xA;scriptPubKey: &lt;data&gt; OP_TRUE&#xA;&#xA;The proof is then the SHA256 midstate, the txout, and the merkle path to&#xA;the block header. However this mechanism needs miner support, and it is&#xA;not possible to pay for such a sacrifice securely, or create an&#xA;assurance contract to create one.&#xA;&#xA;A anyone-can-spend in a regular txout is another option, but there is no&#xA;way to prevent a miner from including a transaction spending that txout&#xA;in the same block. Once that happens, there is no way to prove the miner&#xA;didn&#39;t create both, thus invalidating the sacrifice. The announce-commit&#xA;protocol solves that problem, but at the cost of a much larger proof,&#xA;especially if multiple parties want to get together to pay the cost of&#xA;the sacrifice. (the proof must include the entire tx used to make the&#xA;sacrifice)&#xA;&#xA;However if we add a rule where txouts ending in OP_TRUE are unspendable&#xA;for 100 blocks, similar to coinbases, we fix these problems. The rule&#xA;can be done as a soft-fork with 95% support in the same way the&#xA;blockheight rule was implemented. Along with that change&#xA;anyone-can-spend outputs should be make IsStandard() so they will be&#xA;relayed.&#xA;&#xA;The alternative is sacrifices to unspendable outputs, which is very&#xA;undesirable compared to sending the money to miners to further&#xA;strengthen the security of the network.&#xA;&#xA;We should always make it easy for people to write code that does what is&#xA;best for Bitcoin.&#xA;&#xA;-- &#xA;&#39;peter&#39;[:-1]@petertodd.org&#xA;00000000000000ce3427502ee6a254fed27e1cd21a656a335cd2ada79b7b5293&#xA;-------------- next part --------------&#xA;A non-text attachment was scrubbed...&#xA;Name: signature.asc&#xA;Type: application/pgp-signature&#xA;Size: 490 bytes&#xA;Desc: Digital signature&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130601/9a4fd0e7/attachment.sig&gt;</html></oembed>