12 bytes more for each script pair to provide same bruteforce security as it was for old pay-to-pubkey outputs or pay-to-pubkey and 20 bytes less for each script pair (OP_HASH160
Topic: Are there any OP_DUP OP_HASH256 <hash> OP_EQUALVERIFY OP_CHECKSIG on blockchain? (Read 405 times)
October 13, 2016, 11:21:46 AM
Usual script comes in form OP_DUP OP_HASH160 OP_EQUALVERIFY OP_CHECKSIG. Are there any real scripts in blockchain where OP_HASH160 is replaced with OP_HASH256? Some guys bruteforced four old and already empty addresses. Maybe it is a time to switch to 256 bit secured outputs? For reference private keys are 256 bits long and there are about 2^256/2^160 = 2^96 256 bit long private keys for any 160 bit hash output.
12 bytes more for each script pair to provide same bruteforce security as it was for old pay-to-pubkey outputs or pay-to-pubkey and 20 bytes less for each script pair (OP_HASH160 is not needed).
12 bytes more for each script pair to provide same bruteforce security as it was for old pay-to-pubkey outputs or pay-to-pubkey and 20 bytes less for each script pair (OP_HASH160
Jump to: