2.17BTC ($267USD) pledged to the SHA1 reward to date.
It's amusing that the Bitcoin scripting language lets you pull off
stunts like this; annoying that the scripting language is too limited to
pull off much more than this. In any case I'd love to see proof of a
SHA1 or RIPEMD160 collision previou
On 09/15/2013 03:12 AM, Peter Todd wrote:
> It's amusing that the Bitcoin scripting language lets you pull off
> stunts like this; annoying that the scripting language is too limited to
> pull off much more than this.
You have seen the "CoinWitness" proposal?
https://bitcointalk.org/index.php?to
1) We advise mining the block in which you collect your bounty yourself;
scriptSigs satisfying the above scriptPubKeys do not cryptographically
sign
the transaction's outputs. If the bounty value is sufficiently large
other miners may find it profitable to reorganize the chain to kill
y
Mining power policy abuse (deciding which transactions prevail based on
compute power advantage for theft reasons, or political reasons, or taint
reasons) is what committed coins protect against:
https://bitcointalk.org/index.php?topic=206303.0
(Its just a proposal, its not implemented).
Adam
