1 2017-07-09 11:18:17	0|bitcoin-git|[13bitcoin] 15flack opened pull request #10779: Create dependencies.md (06master...06patch-2) 02https://github.com/bitcoin/bitcoin/pull/10779
 2 2017-07-09 11:41:22	0|bitcoin-git|[13bitcoin] 15practicalswift opened pull request #10780: Simplify `!foo || (foo && bar)` as `!foo || bar` (06master...06redundant-condition) 02https://github.com/bitcoin/bitcoin/pull/10780
 3 2017-07-09 15:35:25	0|spudowiar|Not sure about this
 4 2017-07-09 15:35:34	0|spudowiar|Basically, if you do validateaddress on a hardware wallet address
 5 2017-07-09 15:35:41	0|spudowiar|It will say "ismine": true and "iswatchonly": false
 6 2017-07-09 15:35:59	0|spudowiar|Which is technically a lie, but might be useful for compatibility
 7 2017-07-09 15:45:12	0|luke-jr|spudowiar: is it a lie?
 8 2017-07-09 15:45:36	0|luke-jr|I would think it would say the same as if it was a locked encrypted wallet file
 9 2017-07-09 16:18:36	0|spudowiar|If I use addmultisig, do I then use zapwallettxes to scan for UTXOs for that multisig address?
10 2017-07-09 16:21:08	0|spudowiar|I've tried -rescan and that didn't work, so I'm trying -zapwallettxes now
11 2017-07-09 16:21:21	0|spudowiar|Doubt that'll work though
12 2017-07-09 16:23:53	0|sipa|spudowiar: you need to addaddress as well
13 2017-07-09 16:24:09	0|sipa|spudowiar: addmultisig just informs the wallet about a possible redeemscript
14 2017-07-09 16:24:15	0|sipa|you still need to actually watch for it
15 2017-07-09 16:24:21	0|spudowiar|Thanks :)
16 2017-07-09 16:24:38	0|spudowiar|Wait
17 2017-07-09 16:24:43	0|spudowiar|There's no addaddress RPC method
18 2017-07-09 16:24:47	0|spudowiar|(I remember looking for it :)
19 2017-07-09 16:25:23	0|spudowiar|sipa: It's showing the address as a "Sending address"
20 2017-07-09 16:27:54	0|sipa|importaddress, soory
21 2017-07-09 16:28:55	0|spudowiar|Thanks :)
22 2017-07-09 16:33:17	0|spudowiar|Now, it's seeing it as TX_SCRIPTHASH, not TX_MULTISIG
23 2017-07-09 16:33:27	0|spudowiar|How do I fix this?
24 2017-07-09 16:34:36	0|spudowiar|validateaddress is showing it as multisig
25 2017-07-09 16:34:42	0|sipa|P2SH outputs are TX_SCRIPTHASH yes
26 2017-07-09 16:34:59	0|spudowiar|Yep, but it should be able to detect the scriptPubKey is multisig because it has the redeemScript, right?
27 2017-07-09 16:35:21	0|sipa|where?
28 2017-07-09 16:35:35	0|sipa|you're saying "it's seeing it as TX_SCRIPTHASH", what is 'it'?
29 2017-07-09 16:36:23	0|spudowiar|It's a scriptPubKey that pays to a multisig address
30 2017-07-09 16:36:41	0|sipa|you haven't answered my question
31 2017-07-09 16:36:47	0|spudowiar|The scriptPubKey is a914b7f06dc2f7e39ad712c75633247ac3e33238367387
32 2017-07-09 16:36:51	0|spudowiar|The redeemScript is 5221030e669acac1f280d1ddf441cd2ba5e97417bf2689e4bbec86df4f831bf9f7ffd02103f94638530818d14d7d2ae9b77aa387a6ab26bd01cbc11cf966a64f13d903910452ae
33 2017-07-09 16:37:00	0|spudowiar|sipa: What were you asking in particular?
34 2017-07-09 16:37:16	0|sipa|something is telling you it's a TX_SCRIPTHASH output
35 2017-07-09 16:37:19	0|sipa|what is that something
36 2017-07-09 16:37:23	0|spudowiar|decodescript <scriptPubKey>
37 2017-07-09 16:37:36	0|sipa|decodescript is a utility RPC, not a wallet RPC
38 2017-07-09 16:37:42	0|sipa|it doesn't know about redeemscripts
39 2017-07-09 21:16:34	0|bitcoin-git|[13bitcoin] 15practicalswift opened pull request #10781: Python cleanups (06master...06python-cleanups) 02https://github.com/bitcoin/bitcoin/pull/10781