Timeline for What does this transaction script mean?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 25, 2018 at 22:08 | history | tweeted | twitter.com/StackBitcoin/status/967883986977648640 | ||
| Feb 25, 2018 at 7:36 | answer | added | pebwindkraft | timeline score: 4 | |
| Feb 25, 2018 at 7:02 | comment | added | pebwindkraft | I put my summary in a new answer, otherwise formatting get's in the way ... | |
| Feb 25, 2018 at 0:10 | comment | added | Rod Lin | eh... but we did get the hash, that was weird. I was actually checking the next tx that's using this output. Which signature and pub key were you using? | |
| Feb 25, 2018 at 0:03 | vote | accept | Rod Lin | ||
| Feb 24, 2018 at 17:03 | comment | added | pebwindkraft | ah, I see... this is your own tx. That works with me too :-) I was trying the original tx, but couldn't get it to work. The sig/pubkey and hash didn't match. Anyhow, the structure of the original tx is clear, and I don't want to get off topic too much. Thx. | |
| Feb 24, 2018 at 15:25 | comment | added | Rod Lin | I was using a python library and did get the same hash. I tried openssl in your way, and it still seemed to be valid. These were the parameters I used. | |
| Feb 24, 2018 at 12:53 | comment | added | pebwindkraft | when I convert the sig and unsigned tx to hex, and do a double sha256 on it, I get "4eb4dccd727e81315a9ff801c205efc62635471cf8668e42c1c8aebfb51500a3" - which doesn't match somehow (I then use: openssl pkeyutl <tmp_utx_dsha256.hex -verify -pubin -inkey pubkey.pem -sigfile tmp_sig.hex). How did you check, that sig is valid? | |
| Feb 24, 2018 at 10:00 | comment | added | Rod Lin | sorry forgot to update after Andrew's reply. That's an interesting discovery. I don't know why the owner would expose part of the answer in the previous tx if he was intended to make it a practical and secure one(don't know much about lightning network though). And my raw tx for signature is this one, which seemed fine when I checked. | |
| Feb 23, 2018 at 17:28 | comment | added | pebwindkraft | what a wonderful script! I am trying to decode, but have some troubles. I am having troubles to verify the spending tx signatures with the first or second pubkey, no matter if I use the normal hash or a double hash. One observation: sha256 of the 20 bytes hash from the funding tx (0x1B1B01DC...) results in hash2 in the TX_OUTPUT of the spending tx (F531F304...). So this all makes me think that it is a multisig try. Working on it ... | |
| Feb 23, 2018 at 16:57 | answer | added | Ava Chow♦ | timeline score: 3 | |
| Feb 23, 2018 at 11:47 | review | First posts | |||
| Feb 25, 2018 at 22:37 | |||||
| Feb 23, 2018 at 11:45 | history | asked | Rod Lin | CC BY-SA 3.0 |