1 2017-06-26 06:57:44	0|jtimon|maybe we should add stack exchange to the where botbot link is?
 2 2017-06-26 10:20:33	0|wumpus|you mean in the channel topic? currently we suggest #bitcoin for usage questions, that seems ok
 3 2017-06-26 11:41:06	0|bitcoin-git|13bitcoin/06master 145a9b508 15practicalswift: [trivial] Add end of namespace comments
 4 2017-06-26 11:41:06	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/d609fd85ca41...f3f1e2e7d380
 5 2017-06-26 11:41:07	0|bitcoin-git|13bitcoin/06master 14f3f1e2e 15Wladimir J. van der Laan: Merge #9544: [trivial] Add end of namespace comments. Improve consistency....
 6 2017-06-26 11:41:16	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #9544: [trivial] Add end of namespace comments. Improve consistency. (06master...06consistent-use-of-end-of-namespace-comments) 02https://github.com/bitcoin/bitcoin/pull/9544
 7 2017-06-26 13:05:28	0|bitcoin-git|[13bitcoin] 15laanwj pushed 3 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/f3f1e2e7d380...22a0aca32974
 8 2017-06-26 13:05:29	0|bitcoin-git|13bitcoin/06master 1407b2afe 15Marko Bencun: add Binds, WhiteBinds to CConnman::Options...
 9 2017-06-26 13:05:29	0|bitcoin-git|13bitcoin/06master 14ce79f32 15Marko Bencun: add WhitelistedRange to CConnman::Options...
10 2017-06-26 13:05:30	0|bitcoin-git|13bitcoin/06master 1422a0aca 15Wladimir J. van der Laan: Merge #10496: Add Binds, WhiteBinds, Whitelistedrange to CConnman::Options...
11 2017-06-26 13:05:54	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10496: Add Binds, WhiteBinds, Whitelistedrange to CConnman::Options (06master...06connman_options) 02https://github.com/bitcoin/bitcoin/pull/10496
12 2017-06-26 14:09:26	0|bitcoin-git|[13bitcoin] 15practicalswift opened pull request #10672: Avoid division by zero in the case of a corrupt estimates file (06master...06division-by-zero) 02https://github.com/bitcoin/bitcoin/pull/10672
13 2017-06-26 15:13:39	0|bitcoin-git|13bitcoin/06master 145257698 15Alex Morcos: Change semantics of HaveCoinInCache to match HaveCoin...
14 2017-06-26 15:13:39	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/22a0aca32974...234ffc677ee5
15 2017-06-26 15:13:40	0|bitcoin-git|13bitcoin/06master 14234ffc6 15Wladimir J. van der Laan: Merge #10559: Change semantics of HaveCoinInCache to match HaveCoin...
16 2017-06-26 15:14:34	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10559: Change semantics of HaveCoinInCache to match HaveCoin (06master...06haveunspentincache) 02https://github.com/bitcoin/bitcoin/pull/10559
17 2017-06-26 20:08:11	0|bitcoin-git|[13bitcoin] 15practicalswift opened pull request #10673: [qt] Avoid potential null pointer dereference in TransactionView::exportClicked() (06master...06null-pointer-dereference) 02https://github.com/bitcoin/bitcoin/pull/10673
18 2017-06-26 20:17:04	0|instagibbs|addmultisigaddress seems of quite dubious value. Lost a couple hours thinking it was supposed to add the script to watchonly :/ why shouldn't people just createmultisig->importaddress with redeemscript
19 2017-06-26 20:17:37	0|sipa|instagibbs: because addmultisigaddress is older than watchonly
20 2017-06-26 20:17:54	0|instagibbs|"legacy" somehow I could have guessed :)
21 2017-06-26 20:18:15	0|sipa|and the wallet integration never made it past 'proof of concept'... namely it only treats coins sent to multisig as yours if 1) you know the redeemscript and 2) you have access to all the keys
22 2017-06-26 20:18:22	0|sipa|which i think should be deprecated
23 2017-06-26 20:18:39	0|sipa|the wallet shouldn't try to infer what is yours - we have watchonly now to deal with that
24 2017-06-26 20:18:45	0|bitcoin-git|[13bitcoin] 15jnewbery closed pull request #9569: Setting -blocksonly sets -maxmempool to zero. (06master...06blocksonlynomempoolsharing) 02https://github.com/bitcoin/bitcoin/pull/9569
25 2017-06-26 20:19:21	0|instagibbs|sipa, ok, that makes a bit more sense why there are these two competing systems
26 2017-06-26 20:21:25	0|instagibbs|should addmultisig be marked as deprecated?
27 2017-06-26 20:22:17	0|sipa|unsure; but perhaps this behaviour should at least be documenting in the help
28 2017-06-26 20:22:25	0|instagibbs|yes I am surely going to do that
29 2017-06-26 20:22:33	0|sipa|thanks!
30 2017-06-26 20:47:16	0|instagibbs|hmm as-is you cannot use importaddress to import a non-watchonly address. I guess that's where addmultisig has to be used... that's not straight forward at all
31 2017-06-26 20:47:47	0|sipa|?
32 2017-06-26 20:47:53	0|instagibbs|meaning, cannot use it to import a p2sh multisig you control
33 2017-06-26 20:48:00	0|sipa|really?
34 2017-06-26 20:48:18	0|instagibbs|well, using the redeemscript, lemme check otherwise
35 2017-06-26 20:48:20	0|sipa|even if you only have some of the keys?
36 2017-06-26 20:48:31	0|instagibbs|i believe if you have all of them
37 2017-06-26 20:52:00	0|instagibbs|right, so you can't import the redeemscript, but you can import the p2sh address itself, provided the wallet doesn't know the redeemscript
38 2017-06-26 20:52:14	0|instagibbs|via addmultisig or some other method
39 2017-06-26 21:08:36	0|sipa|there is also importscript
40 2017-06-26 21:11:28	0|instagibbs|i think that's just importaddress with a script arg?
41 2017-06-26 21:12:09	0|sipa|right
42 2017-06-26 21:12:16	0|sipa|isn't that enough?
43 2017-06-26 21:12:54	0|instagibbs|was just noting if you try that with a redeemscript you own the keys to it rejects it
44 2017-06-26 21:13:54	0|instagibbs|so importmultisig appears to be the only place to tell your wallet about something it controls
45 2017-06-26 21:19:00	0|sipa|importmultisig? does that exist
46 2017-06-26 21:19:30	0|instagibbs|importmultisigaddress*
47 2017-06-26 21:19:47	0|instagibbs|can never remember which one has *address at the end
48 2017-06-26 21:19:57	0|instagibbs|create/add
49 2017-06-26 21:20:17	0|sipa|there is addmultisig and createmultisig, no?
50 2017-06-26 21:20:22	0|sipa|no import
51 2017-06-26 21:20:29	0|instagibbs|oh, yes, sorry