arubi: gevs, that is the exact redeemscript : 522102109c754588a5e6de512a68b0e82fa8ed6520f5fd57f6b41315e3d3c2b8f92ac2210318e0167d697e9366f17c2e83ac21c7e66ecc9427884d083887c8d3b6aa3857d8210350bc7cb1f4632c42ad092b1b825beea81ad4a663fa1c365c95d09ff44a11f30353ae

i just found out, when i try to *sign only* the raw transaction payload provided by shmali in the btt thread - i come back to an error i have had before, the library cant sign my OP_RETURN output and it says "scriptPubKey not supported"

uho ok i may have done wrong sending some money of this account earlier haha - my input contains 200000 satoshis but i have spent some, so im going to add a new input (i think im geting this right, lets hope im back here with a big smile in an hour or so :P)

hi, i thought i saw somewhere there is an bitcoind option which allows to not verify the chain up to a certain block height. This is to speed up the initial download. Am I mistaken? is there any other option to achieve the same goal? I dont want to spend CPU cycles unnecessarily.

arubi, :( i changed input... and the newer input i use also specifies a new hash :( "665ea557807d7114aeee2f049d2a54b79e59a9e4", its not the 666 anymore, does it mean i have to reproduce that one instead of the 666 hash? because the 666 was maybe linked to that other input?

because now i get error: RuntimeException : Redeem script fails to solve pay-to-script-hash - which comes from the bitcoin php wrapper and seems to be clear about im failing to provide the right solution

the forum post says: mandatory-script-verify-flag-failed comes from missing signatures though and i have also seen that this error is replace by "64: scriptpubkey" whenever i add a OP_EQUAL to the OP_RETURN output..

you've set your tx to redeem an input sent to 3B2JEDkAB9nSnvAj7ehPRCY1s13APLKnnd, which has hash160 665EA557807D7114AEEE2F049D2A54B79E59A9E4, with the redeemscript for 3B2d4gAe51A6yEPG9qAxRfKxdVA1Zfpq9R which hash hash160 666E5E7041CD7A9DF7075D2F3FC79B6D53DF7963

yep, bad i havent seen that 665 reproduced since im working on it :P might be a key i havent discovered yet haha probably something like 0/3 or so because it the next address, ill come back amazing answers thank you lots :)

you did that spend using the copay wallet. I just did `bitcoin-cli decodescript 522102109c754588a5e6de512a68b0e82fa8ed6520f5fd57f6b41315e3d3c2b8f92ac2210318e0167d697e9366f17c2e83ac21c7e66ecc9427884d083887c8d3b6aa3857d8210350bc7cb1f4632c42ad092b1b825beea81ad4a663fa1c365c95d09ff44a11f30353ae`

they're right there encoded in hex. 522102109c754588a5e6de512a68b0e82fa8ed6520f5fd57f6b41315e3d3c2b8f92ac2210318e0167d697e9366f17c2e83ac21c7e66ecc9427884d083887c8d3b6aa3857d8210350bc7cb1f4632c42ad092b1b825beea81ad4a663fa1c365c95d09ff44a11f30353ae`