1 2018-06-13 01:09:50	0|bitcoin-git|[13bitcoin] 15edsgerlin closed pull request #13444: depends: bump openssl to 1.0.2o (06master...06patch-1) 02https://github.com/bitcoin/bitcoin/pull/13444
  2 2018-06-13 01:22:35	0|gmaxwell|man I dred reviewing openssl patches.
  3 2018-06-13 01:22:39	0|gmaxwell|dread*
  4 2018-06-13 01:23:15	0|gmaxwell|lol I see other people complaining on the PR.
  5 2018-06-13 05:54:28	0|bitcoin-git|[13bitcoin] 15practicalswift opened pull request #13454: Add linter: Make sure LC_ALL=C is set when using grep range expressions (06master...06avoid-locale-dependent-range-expressions) 02https://github.com/bitcoin/bitcoin/pull/13454
  6 2018-06-13 08:00:29	0|fanquake|wumpus I can create that backport if you aren't already doing it
  7 2018-06-13 08:04:57	0|wumpus|sure! thanks, though no real hurry, I've tegged it 0.16.2, don't think it should hold up 0.16.1
  8 2018-06-13 08:05:53	0|fanquake|np, I'll do that and the other outstanding backport. Hadn't noticed the Windows one until now..
  9 2018-06-13 08:11:33	0|bitcoin-git|[13bitcoin] 15fanquake opened pull request #13455: [0.16.2] Backports (060.16...060-16-2-backports) 02https://github.com/bitcoin/bitcoin/pull/13455
 10 2018-06-13 08:13:58	0|fanquake|Any further thought on #13091? Agree that it's only useful if you branch has already been found. Maybe we need to put a notice in the master readme.md?
 11 2018-06-13 08:14:01	0|gribble|https://github.com/bitcoin/bitcoin/issues/13091 | [0.15] doc: Add compilation note to README.md by fanquake · Pull Request #13091 · bitcoin/bitcoin · GitHub
 12 2018-06-13 08:14:10	0|fanquake|^ wumpus
 13 2018-06-13 08:14:27	0|fanquake|If we don't want to do that I'll close the PR and the 0.15.2 milestone.
 14 2018-06-13 08:16:39	0|wumpus|fanquake: yes, as I commented there, I don't think it's very useful in current form, most people are bound to look at README.md in master, but it probably also needs opinions by other people
 15 2018-06-13 08:17:37	0|fanquake|wumpus meh, I think I'll close for now, and might do something against master
 16 2018-06-13 08:18:15	0|bitcoin-git|[13bitcoin] 15fanquake closed pull request #13091: [0.15] doc: Add compilation note to README.md (060.15...060-15-0-readme) 02https://github.com/bitcoin/bitcoin/pull/13091
 17 2018-06-13 08:25:22	0|wumpus|fanquake: okay
 18 2018-06-13 09:21:50	0|jonasschnelli|sipa: thanks for the new BCH code...
 19 2018-06-13 09:22:18	0|jonasschnelli|You set "randomly" picked... out of what set?
 20 2018-06-13 09:54:39	0|jonasschnelli|wumpus: for your scantxoutset issue, the problem is, that P2PK and P2PKH leads to the same address, and decoding the script from that address always decodes in a P2PKH script
 21 2018-06-13 09:55:34	0|jonasschnelli|wumpus: scanning for the P2PK script equivalent by "hashing" the script in the txoutset (form a P2PK script) would probably be a large overhead
 22 2018-06-13 09:56:45	0|jonasschnelli|I don't know how to best deal with that... if a warning the P2PK scripts are not covered by providing addresses is enought
 23 2018-06-13 10:02:04	0|marcoagner|hi! is the process of documenting changes in behavior (including adding release notes) documented anywhere? thanks
 24 2018-06-13 10:05:41	0|marcoagner|I'd like to know if I introduce a small behavior change, should I just write a release-notes-prXXX.md or is there anywhere else to document? asking here so I don't clutter the PR with notifications for simple q's :)
 25 2018-06-13 10:05:52	0|fanquake|marcoagner: The main place changes in behaviour are documented is in release notes. With some changes having a deprecation period for a release or two. i.e RPC changes.
 26 2018-06-13 10:07:25	0|fanquake|A release-notes.md PR sounds ok.
 27 2018-06-13 10:07:58	0|wumpus|if it's a significant behavior change, it needs to be mentioned explicitly in the release notes, it's preferable to add a .md for your PR because it has the least chance of conflict (these will be assembled into one text before the release)
 28 2018-06-13 10:08:12	0|wumpus|jonasschnelli: I understand. Maybe it's not a problem at all.
 29 2018-06-13 10:09:06	0|wumpus|jonasschnelli: depending on the use-case
 30 2018-06-13 10:09:31	0|wumpus|agree it would add overhead to scan for those as well
 31 2018-06-13 10:09:49	0|wumpus|on the other hand, if people rely on this to output the spendable outputs to an address, this needs to work
 32 2018-06-13 10:10:07	0|marcoagner|fanquake: wumpus: thank you, I think I got it. it's not a major change but Luke advised to document it and I agree since it changes behavior (the PR in question just in case: https://github.com/bitcoin/bitcoin/pull/13381#issuecomment-396744773)
 33 2018-06-13 10:16:55	0|provoostenator|What's a simple way to generate a reasonably random UInt256 for in src/benchmark?
 34 2018-06-13 10:20:52	0|jonasschnelli|provoostenator: what do you want to benchmark?
 35 2018-06-13 10:21:34	0|provoostenator|CCoinsView(Cache) writes / reads with and without disk access.
 36 2018-06-13 10:21:54	0|provoostenator|So I need unique tx hashes, but they can be garbage.
 37 2018-06-13 10:30:48	0|jonasschnelli|provoostenator: use FastRandomContext() and eventually make sure you pre-generate random hashes before entering the benchmark timecycle?
 38 2018-06-13 10:32:30	0|provoostenator|Thanks. Yes, I'm making sure to keep that sort of stuff away from the benchmark itself.
 39 2018-06-13 10:33:49	0|provoostenator|There's already sa FastRandom_32bit helper function in the becnh dir I just notice, so can just reuse that pattern.
 40 2018-06-13 10:34:49	0|provoostenator|(no actually that's different, but I'll figure it out)
 41 2018-06-13 11:46:38	0|SpYoGsee|hallo
 42 2018-06-13 12:31:33	0|bitcoin-git|13bitcoin/060.16 14dac5d68 15Wladimir J. van der Laan: doc: Last-minute edits to 0.16.1 release notes...
 43 2018-06-13 12:31:33	0|bitcoin-git|[13bitcoin] 15laanwj pushed 1 new commit to 060.16: 02https://github.com/bitcoin/bitcoin/commit/dac5d68fc6cf136e0d7b21b9ed4fa053d54e6059
 44 2018-06-13 12:35:48	0|fanquake|Looks like a 0.16.1 tag is imminent :o
 45 2018-06-13 12:37:36	0|wumpus|feeling the tension in the air
 46 2018-06-13 12:44:13	0|wumpus|* [new tag]                                                                           v0.16.1 -> v0.16.1
 47 2018-06-13 12:45:47	0|fanquake|Wew
 48 2018-06-13 12:46:20	0|fanquake|\o/
 49 2018-06-13 12:52:45	0|wumpus|\o//
 50 2018-06-13 13:26:29	0|bitcoin-git|13bitcoin/06master 1451ed05a 15Chun Kuan Lee: travis: Increase travis_wait time while verifying commits...
 51 2018-06-13 13:26:29	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/a607d23ae82e...4b1edd318514
 52 2018-06-13 13:26:30	0|bitcoin-git|13bitcoin/06master 144b1edd3 15MarcoFalke: Merge #13447: travis: Increase travis_wait time while verifying commits...
 53 2018-06-13 13:27:30	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #13447: travis: Increase travis_wait time while verifying commits (06master...06patch-1) 02https://github.com/bitcoin/bitcoin/pull/13447
 54 2018-06-13 13:41:44	0|bitcoin-git|13bitcoin/06master 14f6f8026 15Karl-Johan Alm: validation: check the specified number of blocks (off-by-one)
 55 2018-06-13 13:41:44	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/4b1edd318514...caabdea627cf
 56 2018-06-13 13:41:45	0|bitcoin-git|13bitcoin/06master 14caabdea 15Wladimir J. van der Laan: Merge #13428: validation: check the specified number of blocks (off-by-one)...
 57 2018-06-13 13:42:35	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #13428: validation: check the specified number of blocks (off-by-one) (06master...06validation-off-by-one) 02https://github.com/bitcoin/bitcoin/pull/13428
 58 2018-06-13 13:44:15	0|bitcoin-git|13bitcoin/06master 1451cd508 15Ben Woosley: When build fails due to lib missing, indicate which one...
 59 2018-06-13 13:44:15	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/caabdea627cf...cf7ca609234d
 60 2018-06-13 13:44:16	0|bitcoin-git|13bitcoin/06master 14cf7ca60 15Wladimir J. van der Laan: Merge #13435: When build fails due to lib missing, indicate which one...
 61 2018-06-13 13:45:10	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #13435: When build fails due to lib missing, indicate which one (06master...06lib-missing) 02https://github.com/bitcoin/bitcoin/pull/13435
 62 2018-06-13 13:48:21	0|bitcoin-git|13bitcoin/06master 149882d1f 15Chun Kuan Lee: Reset default -g -O2 flags when enable debug
 63 2018-06-13 13:48:21	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/cf7ca609234d...8eb76f3958e3
 64 2018-06-13 13:48:22	0|bitcoin-git|13bitcoin/06master 148eb76f3 15Wladimir J. van der Laan: Merge #13445: build: Reset default -g -O2 flags when enable debug...
 65 2018-06-13 13:49:14	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #13445: build: Reset default -g -O2 flags when enable debug (06master...06debug_cflags) 02https://github.com/bitcoin/bitcoin/pull/13445
 66 2018-06-13 13:53:54	0|bitcoin-git|[13bitcoin] 15MarcoFalke opened pull request #13457: tests: Drop variadic macro (06master...06Mf1806-qaVariadicMacro) 02https://github.com/bitcoin/bitcoin/pull/13457
 67 2018-06-13 14:08:40	0|jonasschnelli|wumpus: added detection of P2PK scripts in scantxoutset: https://github.com/bitcoin/bitcoin/pull/12196#issuecomment-396950856
 68 2018-06-13 14:29:26	0|instagibbs|I'd like a backport tag for #13451 if possible
 69 2018-06-13 14:29:28	0|gribble|https://github.com/bitcoin/bitcoin/issues/13451 | rpc: expose CBlockIndex::nTx in getblock(header) by instagibbs · Pull Request #13451 · bitcoin/bitcoin · GitHub
 70 2018-06-13 14:39:05	0|fanquake|instagibbs I can add it to 13455
 71 2018-06-13 14:39:52	0|fanquake|eh, still needs to be merged
 72 2018-06-13 14:40:28	0|instagibbs|yes, working on that. It's a super easy change at least.
 73 2018-06-13 14:41:18	0|bitcoin-git|13bitcoin/06master 142ce8186 15Lowell Manners: [tests] Add logging to provide anchor points when debugging failures....
 74 2018-06-13 14:41:18	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/8eb76f3958e3...f532d52d3965
 75 2018-06-13 14:41:19	0|bitcoin-git|13bitcoin/06master 14f532d52 15MarcoFalke: Merge #13350: [tests] Add logging to provide anchor points when debugging p2p_sendheaders...
 76 2018-06-13 14:42:03	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #13350: [tests] Add logging to provide anchor points when debugging p2p_sendheaders (06master...06testlogging) 02https://github.com/bitcoin/bitcoin/pull/13350
 77 2018-06-13 14:50:27	0|sipa|jonasschnelli: there are some free parameters for the code
 78 2018-06-13 14:50:35	0|sipa|jonasschnelli: i picked one at random
 79 2018-06-13 14:51:35	0|sipa|jonasschnelli, wumpus: i think it's a very bad idea to continue the pubkey/address confusion, for a number of reasons
 80 2018-06-13 14:52:29	0|sipa|one is that it's not compatible with bip158 based rescanning where you must know the exact scriptPubKeys you're looking for)
 81 2018-06-13 14:56:48	0|jonasschnelli|sipa: P2PK: I think either...
 82 2018-06-13 14:57:20	0|jonasschnelli|But,... what should we do with address bases scanning,... drop it completely?
 83 2018-06-13 14:58:51	0|jonasschnelli|Not looking for P2PK equivalents when providing address is probably dangerous
 84 2018-06-13 14:59:10	0|jonasschnelli|Also, just mentioning in the docs somewhere that P2PK scripts are not covered seems also fragile.
 85 2018-06-13 14:59:22	0|sipa|jonasschnelli: why? it's not that anyone in practice is paid using P2PK
 86 2018-06-13 15:00:27	0|jonasschnelli|Yes. Perhaps...
 87 2018-06-13 15:00:41	0|sipa|yes, i would just document it loudly
 88 2018-06-13 15:01:09	0|jonasschnelli|Okay. Makes sense... let me do that
 89 2018-06-13 15:01:42	0|sipa|so still want to include support for hd chaina etc?
 90 2018-06-13 15:01:53	0|sipa|in scantxoutset?
 91 2018-06-13 15:10:00	0|bitcoin-git|[13bitcoin] 15laanwj opened pull request #13458: gui: Drop qt5 support (06master...062018_06_remove_qt4_support) 02https://github.com/bitcoin/bitcoin/pull/13458
 92 2018-06-13 15:12:07	0|jonasschnelli|sipa: support for hd chain?
 93 2018-06-13 15:12:11	0|jonasschnelli|You mean flexible keypath?
 94 2018-06-13 15:12:30	0|sipa|jonasschnelli: support for xpub derivation etc
 95 2018-06-13 15:12:42	0|jonasschnelli|It's supported in the current PR
 96 2018-06-13 15:12:49	0|sipa|i know
 97 2018-06-13 15:13:01	0|promag|> gui: Drop qt5 support < uff
 98 2018-06-13 15:13:05	0|jonasschnelli|sipa: Just not with a text base script type descriptor as we once discussed
 99 2018-06-13 15:13:12	0|sipa|jonasschnelli: okay
100 2018-06-13 15:13:38	0|jonasschnelli|sipa: But I changed the API to have n elements of various types
101 2018-06-13 15:13:53	0|jonasschnelli|(as you suggested)
102 2018-06-13 15:17:25	0|wumpus|promag: lol...
103 2018-06-13 15:18:18	0|sipa|wumpus: straight to qt6?
104 2018-06-13 15:20:54	0|fanquake|sipa bundle that with c++17
105 2018-06-13 15:21:37	0|sipa|fanquake: that seems weird; c++17 actually exists :)
106 2018-06-13 15:21:43	0|sipa|go for c++20 at least
107 2018-06-13 15:22:51	0|wumpus|sipa: we're migrating to electron *runs very fast*
108 2018-06-13 15:23:24	0|sipa|haha
109 2018-06-13 15:23:43	0|fanquake|heh
110 2018-06-13 15:55:20	0|jonasschnelli|sipa: any preferences for a name for the Base32 based 27 checksum BCH code? BechSeven32? Bech32Priv? Priv32?
111 2018-06-13 15:56:04	0|jonasschnelli|And I guess I can use the HRP checksum integration 1:1 from Bech32?
112 2018-06-13 15:56:36	0|sipa|yeah
113 2018-06-13 15:56:56	0|sipa|Bech32X
114 2018-06-13 15:56:59	0|sipa|:)
115 2018-06-13 16:03:10	0|jonasschnelli|Okay. Bech32X shall it be
116 2018-06-13 16:06:05	0|fanquake|jonasschnelli: I'm just retesting, but be good to get your ack/nack on #12783. Not sure if you wanted to test a 10.8 VM, but I think we'll be moving to 10.10+ "soonish".
117 2018-06-13 16:06:07	0|gribble|https://github.com/bitcoin/bitcoin/issues/12783 | macOS: Disable AppNap by krab · Pull Request #12783 · bitcoin/bitcoin · GitHub
118 2018-06-13 16:06:25	0|jonasschnelli|fanquake: okay. Will have a look soon.
119 2018-06-13 17:21:04	0|bitcoin-git|13bitcoin/06master 143d69853 15Chun Kuan Lee: travis: Change Mac goal to all deploy so that travis can build all executables for Mac.
120 2018-06-13 17:21:04	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/f532d52d3965...4382f192e5ce
121 2018-06-13 17:21:05	0|bitcoin-git|13bitcoin/06master 144382f19 15MarcoFalke: Merge #13406: travis: Change Mac goal to all deploy...
122 2018-06-13 17:21:54	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #13406: travis: Change Mac goal to all deploy (06master...06travis_make_mac) 02https://github.com/bitcoin/bitcoin/pull/13406
123 2018-06-13 17:24:55	0|bitcoin-git|13bitcoin/06master 14faf52f9 15MarcoFalke: tests: Drop variadic macro
124 2018-06-13 17:24:55	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/4382f192e5ce...b2221381e787
125 2018-06-13 17:24:56	0|bitcoin-git|13bitcoin/06master 14b222138 15Wladimir J. van der Laan: Merge #13457: tests: Drop variadic macro...
126 2018-06-13 17:25:49	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #13457: tests: Drop variadic macro (06master...06Mf1806-qaVariadicMacro) 02https://github.com/bitcoin/bitcoin/pull/13457
127 2018-06-13 17:49:08	0|bitcoin-git|13bitcoin/06master 14c2dfbb4 15Andrew Chow: Add unavailable options to hidden options category...
128 2018-06-13 17:49:08	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/b2221381e787...4a7e64fc8546
129 2018-06-13 17:49:09	0|bitcoin-git|13bitcoin/06master 144a7e64f 15MarcoFalke: Merge #13441: Prevent shared conf files from failing with different available options in different binaries...
130 2018-06-13 17:50:02	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #13441: Prevent shared conf files from failing with different available options in different binaries (06master...06gargs-disabled-options) 02https://github.com/bitcoin/bitcoin/pull/13441
131 2018-06-13 18:55:40	0|Chris_Stewart_5|I have a question about using `addmultisigaddress` in conjunction with decodescript. I am not getting the same address field output
132 2018-06-13 18:55:49	0|Chris_Stewart_5|https://pastebin.com/q7yNWAJM
133 2018-06-13 18:56:16	0|Chris_Stewart_5|if I take the `redeemScript` from addmultisigaddress pass that into `decodescript` I get a different address encoding, why is that?
134 2018-06-13 18:56:55	0|sipa|i'm confused
135 2018-06-13 18:57:04	0|sipa|what exactly is not what you expect
136 2018-06-13 18:58:09	0|Chris_Stewart_5|is the address being returned from `addmultisigaddress` suppose to be an encoding of the redeem script?
137 2018-06-13 18:58:24	0|sipa|no, it's the P2SH address
138 2018-06-13 18:58:41	0|Chris_Stewart_5|yes, so p2sh(redeemscript) right?
139 2018-06-13 18:58:43	0|sipa|yes
140 2018-06-13 18:59:05	0|Chris_Stewart_5|So why would decodescript give a different address?
141 2018-06-13 18:59:33	0|sipa|ah!
142 2018-06-13 18:59:43	0|sipa|sorry, i had no idea what i was supposed to see that was weird
143 2018-06-13 19:00:05	0|sipa|can you run getaddressinfo or validateaddress on both?
144 2018-06-13 19:00:15	0|Chris_Stewart_5|np. We checked it against bitcoin-s and it appears to be the second address from decode script that is correct
145 2018-06-13 19:00:48	0|Chris_Stewart_5|Yes we can do that. Just a sec
146 2018-06-13 19:01:09	0|sipa|oh, it may be that addmultisigaddress returns an P2SH-P2WSH address
147 2018-06-13 19:02:38	0|Chris_Stewart_5|is getaddressinfo only on master?
148 2018-06-13 19:02:48	0|sipa|possibly
149 2018-06-13 19:04:32	0|nkohen|sipa, I think you're right, here's my session https://pastebin.com/YdPgi88U
150 2018-06-13 19:05:15	0|sipa|nkohen: yup
151 2018-06-13 19:05:52	0|satwo|b) a multi-file solution for bitcoind's debug logging to allow for truncating and archiving debug.log
152 2018-06-13 19:05:52	0|satwo|b) a multi-file solution for bitcoind's debug logging to allow for truncating and archiving debug.log
153 2018-06-13 19:05:52	0|satwo|Hello all. Been thinking about a couple of features I'd like to see in Bitcoin Core and am curious what others think and whether these features already been discussed (or even implemented somewhere). a) Exposing SigOps count in getrawtransaction and getblock
154 2018-06-13 19:06:20	0|sipa|nkohen: use addresstype=legacy if you want p2sh-multisig
155 2018-06-13 19:08:29	0|Chris_Stewart_5|sipa: Is this an issue that there isn't consistentcy in the address being returned by these? I.e. one of thos rpcs isn't reading what your configuration is?
156 2018-06-13 19:09:39	0|Chris_Stewart_5|if we submitted a PR to do this would that be accepted?
157 2018-06-13 19:12:27	0|jonasschnelli|Why is "include_watchonly" in getbalance depracated?
158 2018-06-13 19:13:44	0|bitcoin-git|[13bitcoin] 15MarcoFalke opened pull request #13460: doc: Remove note to install all boost dev packages (06master...06Mf1806-docBuildUbuntu) 02https://github.com/bitcoin/bitcoin/pull/13460
159 2018-06-13 19:14:09	0|sipa|Chris_Stewart_5: what would you change?
160 2018-06-13 19:14:15	0|sipa|all the returned information is correct
161 2018-06-13 19:14:27	0|sipa|Chris_Stewart_5: decodescript is not a wallet RPC
162 2018-06-13 19:14:34	0|sipa|it just decodes the script
163 2018-06-13 19:15:25	0|sipa|validateaddress/getaddressinfo will return the wallet related information
164 2018-06-13 19:19:49	0|sipa|i guess decodescript could get an extra "p2sh-p2wsh" field
165 2018-06-13 19:20:04	0|sipa|which gives the p2sh-p2wsh address for that script
166 2018-06-13 19:20:39	0|sipa|actually, no
167 2018-06-13 19:21:13	0|sipa|if it's already a witness program it can't do that, etc
168 2018-06-13 19:26:34	0|gmaxwell|satwo: you can handle the logs like standard unix daemon logs. Mv the file, then HUP the process and it'll make a new file and stop writing to the old one.
169 2018-06-13 19:32:27	0|satwo|gmaxwell: Wouldn't there be data loss (albeit small) with that approach?
170 2018-06-13 19:33:07	0|satwo|Or does bitcoind immediately make a new debug.log if it doesn't see one where it's expecting to?
171 2018-06-13 19:49:36	0|Chris_Stewart_5|sipa: If you provide a 'raw' (non witness) redeem script it would make sense to have multiple address encodings no?
172 2018-06-13 19:50:29	0|sipa|Chris_Stewart_5: iguess
173 2018-06-13 19:50:49	0|sipa|but generally decodescript doesn't know
174 2018-06-13 19:51:35	0|sipa|though things that look like witness programs aren't useful as scripts directly
175 2018-06-13 19:51:41	0|Chris_Stewart_5|Yeah I understand, I didn't realize it was an rpc that doesn't have any context into your wallet. Not even configuration settings
176 2018-06-13 19:52:09	0|sipa|oh it does have configuration info
177 2018-06-13 19:52:37	0|sipa|but the field is called "p2sh", not "address", so i guess it's expected to produce a p2sh address
178 2018-06-13 19:53:08	0|sipa|still, i think it wouldn't make sense to make its output depend on what type of addresses you have configured
179 2018-06-13 19:53:21	0|sipa|it's an rpc designed to examine things, not to construct addresses
180 2018-06-13 19:54:16	0|Chris_Stewart_5|really? I would disagree. But to each and his own. Thanks you for the help
181 2018-06-13 19:55:20	0|sipa|but adding other fields for p2wsh addresses there sounds oretty useful to me
182 2018-06-13 19:56:03	0|sipa|Chris_Stewart_5: generally nobody but the receiver wallet should be constructing addresses (as only he and his software can determine exactly which outputs tjey will consider valid payments)
183 2018-06-13 19:56:31	0|sipa|so i think it doesn't make sense to have an RPC that is designed to analyse other's addresses be dependent on your own settings for what addresses to genrrate
184 2018-06-13 19:57:50	0|sipa|i've seen some confusion from people who want to "convert" an existing p2pkh address into segwit versions, which you should never do, as you don't know the receiver wallet will support it
185 2018-06-13 20:21:28	0|cfields|sipa: it occurs to me that for for SHA256D64, duplicated leaves have some redundant sigma0 calculations during message expansion.
186 2018-06-13 20:21:39	0|cfields|not enough redundancy to be useful, just thought it was interesting
187 2018-06-13 20:28:46	0|luke-jr|IIRC, the new code is doing 8-way if there's >=8 things left, and 4-way if 4-7 things left.. is there a reason not to do 8-way for >4 things? wouldn't that be faster than doing 4-way + 2-way + 1-way ?
188 2018-06-13 20:29:26	0|luke-jr|sipa: ^
189 2018-06-13 20:29:44	0|bitcoin-git|[13bitcoin] 15jonasschnelli opened pull request #13461: Wallet: correctly deprecate accounts in getbalance, re-add minconf / include-watch-only (06master...062018/06/watch_only_balance) 02https://github.com/bitcoin/bitcoin/pull/13461
190 2018-06-13 20:32:46	0|sipa|luke-jr: yes, i've thought about that- but it also doesn't matter all that much
191 2018-06-13 20:32:55	0|sipa|it affects at most 3 entries per level
192 2018-06-13 20:41:44	0|bitcoin-git|[13bitcoin] 15Empact opened pull request #13462: scripted-diff: Simplify common case of CHashWriter and drop SER_GETHASH (06master...06serialize-hash-type) 02https://github.com/bitcoin/bitcoin/pull/13462
193 2018-06-13 21:14:46	0|christos88|hi, my bit core client says since a few hours ago as i started it that its "checking again the blocks..." "Blöcke werden nochmal neu verarbeitet...", its says 0%, the client is working but i dont know what its doing, i want to complete the download of the blockchain, its possible that the program wasnt shut down properly but how long can the work process take?
194 2018-06-13 21:17:47	0|sipa|christos88: yes, unclean shutdown
195 2018-06-13 21:18:41	0|sipa|it can take a long time; it needs to go through all blocks since the last succesful flush
196 2018-06-13 21:18:48	0|sipa|with large dbcache that can be a lot
197 2018-06-13 21:21:16	0|bitcoin-git|[13bitcoin] 15spyder46n2 opened pull request #13463: Merge change from BitCoin #11013 - Fix automake warnings when running autogen.sh (Ubuntu and others) (06master...06develop) 02https://github.com/bitcoin/bitcoin/pull/13463
198 2018-06-13 21:23:46	0|christos88|@sipa thank you, i had already over 80%, it took me a few weeks, do i have to wait again that long?
199 2018-06-13 21:34:27	0|sipa|christos88: weeks?!
200 2018-06-13 21:34:29	0|sipa|what hardware?
201 2018-06-13 21:52:51	0|midnightmagic|gah, what's up with ken's signature
202 2018-06-13 21:55:42	0|achow101|what's wrong with it?
203 2018-06-13 21:58:54	0|christos88|sipa: its old hardware, intel dual core, 4gb ram, geforce 9400
204 2018-06-13 22:01:57	0|achow101|midnightmagic: he uses ECDSA instead of RSA, perhaps that's the problem?
205 2018-06-13 22:11:32	0|midnightmagic|hrm
206 2018-06-13 22:15:29	0|midnightmagic|he must be using gpg2 as gpg
207 2018-06-13 22:15:35	0|booyah|christos88: it shouldn't take so long. is computer running almost 24/2?
208 2018-06-13 22:15:36	0|booyah|christos88: it shouldn't take so long. is computer running almost 24/24?
209 2018-06-13 22:16:03	0|achow101|midnightmagic: probably. in some systems, gpg2 is the default gpg
210 2018-06-13 22:16:54	0|midnightmagic|rad
211 2018-06-13 22:21:13	0|christos88|booyah: yes, right now 24 hours, percentage per hour was o,XX, depended on how much i was using browsers to surf, right now bitcore is checking at 0% since 4 hours
212 2018-06-13 22:34:51	0|bitcoin-git|[13bitcoin] 15spyder46n2 closed pull request #13463: Merge change from BitCoin #11013 - Fix automake warnings when running autogen.sh (Ubuntu and others) (06master...06develop) 02https://github.com/bitcoin/bitcoin/pull/13463
213 2018-06-13 23:26:02	0|bitcoin-git|[13bitcoin] 15kristapsk opened pull request #13464: RPC: Allow to specify rescan start timestamp for importaddress, importprivkey and importpubkey (06master...06rescan-from) 02https://github.com/bitcoin/bitcoin/pull/13464