--- Day changed Fri Sep 15 2017 00:09 -!- pbase [~pbase@unaffiliated/pbase] has quit [Remote host closed the connection] 00:15 -!- pbase [~pbase@unaffiliated/pbase] has joined #bitcoin-core-dev 00:44 -!- harrymm [~wayne@85.203.47.86] has joined #bitcoin-core-dev 00:47 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 00:48 -!- drizztbsd [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 00:49 -!- laurentmt [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev 00:50 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Client Quit] 00:52 -!- laurentmt [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev 00:52 -!- timothy [~tredaelli@redhat/timothy] has quit [Ping timeout: 260 seconds] 00:53 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/0f399a9ff227...ae233c4ec3d1 00:53 < bitcoin-git> bitcoin/master dc2f737 danra: Trivial: Fix comments for DEFAULT_WHITELIST[FORCE]RELAY 00:53 < bitcoin-git> bitcoin/master ae233c4 MarcoFalke: Merge #11330: Trivial: Fix comments for DEFAULT_WHITELIST[FORCE]RELAY... 00:53 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #11330: Trivial: Fix comments for DEFAULT_WHITELIST[FORCE]RELAY (master...patch-10) https://github.com/bitcoin/bitcoin/pull/11330 00:53 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 252 seconds] 00:55 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/ae233c4ec3d1...09627b1dd41d 00:55 < bitcoin-git> bitcoin/master cdaf3a1 Matt Corallo: Fix Qt 0.14.2->0.15.0 segfault if "total at least" is selected... 00:55 < bitcoin-git> bitcoin/master 09627b1 Wladimir J. van der Laan: Merge #11332: Fix possible crash with invalid nCustomFeeRadio in QSettings (achow101, TheBlueMatt)... 00:56 < bitcoin-git> [bitcoin] laanwj closed pull request #11332: Fix possible crash with invalid nCustomFeeRadio in QSettings (achow101, TheBlueMatt) (master...2017/09/qsettings_1) https://github.com/bitcoin/bitcoin/pull/11332 00:57 < bitcoin-git> [bitcoin] laanwj pushed 1 new commit to 0.15: https://github.com/bitcoin/bitcoin/commit/46c8d23dad216d990564014f4c8000b79fd36f4e 00:57 < bitcoin-git> bitcoin/0.15 46c8d23 Matt Corallo: Fix Qt 0.14.2->0.15.0 segfault if "total at least" is selected... 00:58 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 01:15 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 01:16 -!- drizztbsd [~tredaelli@redhat/timothy] has quit [Ping timeout: 240 seconds] 01:18 < bitcoin-git> [bitcoin] danra opened pull request #11337: Fix code constness in CBlockIndex::GetAncestor() overloads (master...fix/const-get-ancestor) https://github.com/bitcoin/bitcoin/pull/11337 01:44 < bitcoin-git> [bitcoin] laanwj closed pull request #11208: Fixing offscreen GUI issue (master...201709_offscreen_fix) https://github.com/bitcoin/bitcoin/pull/11208 01:52 < wumpus> meshcollider: "mhm but if we rely on Qt restore and save, its not really fixable by us" <- well, as we never managed t oget it right in years of trying, please don't be angry at me for thinking maybe the qt devs know more about handling this and can do this better? :) 01:52 < meshcollider> wumpus: yeah im not saying we should do it, I'm just saying its their problem now :) 01:52 < wumpus> we can try this, give it one try, if it's flaky as well, I'd say we remove the functionality 01:53 < meshcollider> their restore and save function have a lot more benefits than ours anyway, like the maximisation issue I mentioned in my PR 01:53 < wumpus> it's not worth spending too much cycles on 01:53 < wumpus> but I'd bet quite a lot that their function received significantly more testing than us 01:53 < wumpus> ours* 01:55 < wumpus> I don't understand why this triggers yet another qt 4 discussion though, the function has existed for about forever 01:55 < wumpus> or is there some subtlety there? 01:56 -!- promag [~promag@62.28.141.66] has joined #bitcoin-core-dev 02:00 < promag> what does the "n" prefix means in nRPCConsoleWindow ? 02:01 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-eymzzvwlnncbxacb] has quit [Quit: Connection closed for inactivity] 02:01 -!- rjak [~rjak@gateway/vpn/privateinternetaccess/rjak] has joined #bitcoin-core-dev 02:08 < wumpus> "number" I guess 02:09 < wumpus> all of the qt settings have weird names, AFAIK it's based on satoshi's naming scheme for settings when they were still in the wallet 02:10 < wumpus> anyhow it doesn't really matter what the names are, as long as the names are unique within bitcoin-qt 02:10 < wumpus> for new settings I'd say use a plainer scheme 02:11 < meshcollider> its a perfect time to change the nRPCConsoleWindow and nWindow ones if you want to because theyre both new to this PR 02:11 < meshcollider> nRPCConsoleWindowGeometry and nWindowGeometry 02:11 < wumpus> but I don't care, no one is supposed to see them 02:11 < wumpus> right 02:12 < promag> yeah, I would rename since they hold a different value/type 02:13 < promag> the suffix "Geometry" sounds enough 02:14 < wumpus> yes, it's enough 02:14 < meshcollider> so just get rid of the 'n' at the front? 02:14 < meshcollider> RPCConsoleWindowGeometry and WindowGeometry ? 02:14 < wumpus> sounds good to me 02:14 < wumpus> maybe MainWindowGeometry 02:15 < promag> was going to say the same 02:16 < meshcollider> sweet done 馃憤 02:19 < promag> so the old settings will stay? 02:20 < meshcollider> the old settings weren't called Geometry anyway, they saved position and size seperately in nWindowPos and nWindowSize 02:21 < meshcollider> But yeah those Pos and Size will stay in there unused 02:22 < wumpus> adding upgrade handling code just to remove them sounds like overkill 02:35 < promag> and for some reason the user can keep 2 versions installed 02:36 -!- promag [~promag@62.28.141.66] has quit [Remote host closed the connection] 02:37 -!- promag [~promag@62.28.141.66] has joined #bitcoin-core-dev 02:37 -!- promag [~promag@62.28.141.66] has quit [Remote host closed the connection] 02:38 -!- promag [~promag@62.28.141.66] has joined #bitcoin-core-dev 02:38 -!- promag [~promag@62.28.141.66] has quit [Remote host closed the connection] 02:43 < wumpus> right, or some sinister altcoin that uses the same settings directory :-) 02:43 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has joined #bitcoin-core-dev 02:43 -!- Dummbatz [~dummy@89.126.196.178.dynamic.wline.res.cust.swisscom.ch] has left #bitcoin-core-dev [] 02:45 -!- promag [~promag@62.28.141.66] has joined #bitcoin-core-dev 02:47 -!- promag [~promag@62.28.141.66] has quit [Read error: Connection reset by peer] 02:49 -!- ula [~kvirc@b2b-78-94-11-194.unitymedia.biz] has joined #bitcoin-core-dev 02:57 < bitcoin-git> [bitcoin] laanwj opened pull request #11338: qt: Backup former GUI settings on `-resetguisettings` (master...2017_10_backup_resetguisettings) https://github.com/bitcoin/bitcoin/pull/11338 03:11 < meshcollider> Are there any other goals for 0.15.1 other than the segwit wallet support sipa is working on? 03:15 < bitcoin-git> [bitcoin] danra opened pull request #11339: Minor improvements to checkpoints code (master...refactor/checkpoints) https://github.com/bitcoin/bitcoin/pull/11339 03:16 -!- supay [6a334193@gateway/web/freenode/ip.106.51.65.147] has joined #bitcoin-core-dev 03:16 < supay> i was wondering if it would be possible to create a contact system where individuals grant access to another individuals contact information on top of the blockchain 03:16 < supay> i believe a peer-to-peer ledger recording the level of access granted or revoked could enable an open social graph 03:16 < supay> once there is a clean method to grant and update contact information across users, there is also now a social graph with information tiering, allowing a user-controlled and defined connection level between individuals. 03:17 < meshcollider> supay: wrong channel, try #bitcoin 03:17 < supay> meshcollider: tried :( 03:18 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 03:20 < venzen> supay: Namecoin provides namespaces for ID information 03:21 < supay> venzen: but no open social graph! 03:22 < supay> on #bitcoin ali1234 mentioned that there are still analog holes 03:22 < meshcollider> supay venzen: this channel is only for discussion of bitcoin core, please take this discussion to another channel 03:22 < supay> but i see this as a powerful p2p contact exchange and/or social graph 03:22 < venzen> supay: we shouldn't really discuss that here, it's off-topic for this dev channel 03:22 < supay> venzen: can i pm? 03:23 < venzen> sure 03:34 -!- RubenSomsen [~RubenSoms@1.217.138.142] has joined #bitcoin-core-dev 03:36 < wumpus> meshcollider: no other features at least, bugfixes are always good of course 03:44 < bitcoin-git> [bitcoin] danra opened pull request #11340: Trivial: Fix validation.cpp comment, BIP113 already deployed (master...patch-12) https://github.com/bitcoin/bitcoin/pull/11340 04:15 < bitcoin-git> [bitcoin] danra closed pull request #11331: Trivial: Update outdated comment in validation.h (master...patch-11) https://github.com/bitcoin/bitcoin/pull/11331 04:15 < bitcoin-git> [bitcoin] danra closed pull request #11328: Move comment about transaction/block weight calculation (master...fix/weight-comment) https://github.com/bitcoin/bitcoin/pull/11328 04:27 < aj> wumpus: hey, now 0.15 is out, should i ping back about #10996 (network.conf) ? we were worrying about qt/bitcoind initialisation diverging and generally making that stuff harder to understand, and potentially tests and such 04:27 < gribble> https://github.com/bitcoin/bitcoin/issues/10996 | [WIP] Add per-network config file network.conf by ajtowns 路 Pull Request #10996 路 bitcoin/bitcoin 路 GitHub 04:48 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 05:16 < wumpus> aj: yes, agreed 05:17 -!- dabura667_ [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 05:20 < wumpus> so, do a 0.15.0.1 with just #11332 or merge #11335 and maybe #11338 as well? 05:20 < gribble> https://github.com/bitcoin/bitcoin/issues/11332 | Fix possible crash with invalid nCustomFeeRadio in QSettings (achow101, TheBlueMatt) by jonasschnelli 路 Pull Request #11332 路 bitcoin/bitcoin 路 GitHub 05:20 < gribble> https://github.com/bitcoin/bitcoin/issues/11335 | Replace save|restoreWindowGeometry with Qt functions by MeshCollider 路 Pull Request #11335 路 bitcoin/bitcoin 路 GitHub 05:20 < gribble> https://github.com/bitcoin/bitcoin/issues/11338 | qt: Backup former GUI settings on `-resetguisettings` by laanwj 路 Pull Request #11338 路 bitcoin/bitcoin 路 GitHub 05:21 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds] 05:21 < wumpus> all are necessary qt gui changes, though only the former is a crash issue 05:24 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 05:29 -!- pit [~pit@178.168.58.59] has joined #bitcoin-core-dev 05:34 -!- pit [~pit@178.168.58.59] has quit [Quit: Leaving] 05:44 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 05:53 < MarcoFalke> What is the deadline for 0.15.0.1? 05:53 < MarcoFalke> I might prepare some qa backports, so that people won't run into the intermittent errors we saw on travis 05:54 -!- jtimon [~quassel@199.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 05:54 < wumpus> I don't know - would be nice to have something as soon as possible to recommend to people experiencing crashes, though 05:54 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 05:54 < wumpus> that's the motivation for it 05:55 < MarcoFalke> hmm, in which case it should be tagged today. To give some time for builders 05:56 < wumpus> if we only include 11338 do we even need a RC phase? 05:57 < wumpus> I guess it would be better to do one anyway, a very short one 05:58 < wumpus> ok, will do the version bump, update translations and tag rc1 06:00 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #11341: [0.15.0] Bump manpages (0.15...Mf1709-docMan15) https://github.com/bitcoin/bitcoin/pull/11341 06:00 < MarcoFalke> wumpus: Someone complained about the manpages ^ 06:02 < wumpus> ah yes, was just about to do that 06:02 < wumpus> but need after the 0.15.0.1 bump 06:05 < MarcoFalke> Maybe we don't need an rc phase for this 1 LOC change... 06:05 < wumpus> yes, maybe not 06:05 < MarcoFalke> If it is broken (despite testing) don't push the binaries. 06:06 < wumpus> and make a 0.15.0.2? :) 06:07 < MarcoFalke> ja :) 06:09 < promag> wumpus: do you think the backup filename should have the datetime? 06:11 < promag> also, if the file already exists it is appended, not really a backup imo 06:11 < wumpus> no need for a datetime, it's a one-time thing 06:11 < promag> *appended as in the settings are added or updated 06:11 -!- pbase [~pbase@unaffiliated/pbase] has quit [Quit: Leaving] 06:11 < wumpus> oh, good point, it should be cleared first 06:12 < promag> thats why I thought about the timestamp 06:12 < wumpus> I'll just add a dst.clear() 06:14 < wumpus> I prefer a fixed name as I don't want people to end up with zillions of files in their datadir 06:16 < promag> allright 06:16 < promag> nit: backupSettings(filename, src) swap: backupSettings(const QSettings &src, const fs::path &filename)? :P 06:16 < wumpus> why? 06:17 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev 06:17 < promag> ah I see you prefer dst, src 06:17 < wumpus> yes 06:17 < promag> why? :P 06:17 < wumpus> don't feel like arguing this 06:19 < wumpus> both options are equally valid and it really doesn't matter here, it's an internal function not an official API 06:19 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #11339: Minor improvements to checkpoints code (master...refactor/checkpoints) https://github.com/bitcoin/bitcoin/pull/11339 06:22 < warren> Does bitcoin-cli have any tool that will tell you the feerate of a rawtx? 06:22 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to 0.15: https://github.com/bitcoin/bitcoin/compare/46c8d23dad21...7123b95bea5b 06:22 < bitcoin-git> bitcoin/0.15 8432332 Wladimir J. van der Laan: build: Bump version to 0.15.0.1... 06:22 < bitcoin-git> bitcoin/0.15 7123b95 Wladimir J. van der Laan: doc: Bump manpages to 0.15.0.1... 06:24 < wumpus> warren: no, as that information is not in a raw transaction, it'd need the parent transactions (which aren't available without txindex) 06:25 < promag> unless the transaction is in your wallet 06:28 < promag> wumpus: in #11338 `T &x` should be `T& x` 06:28 < gribble> https://github.com/bitcoin/bitcoin/issues/11338 | qt: Backup former GUI settings on `-resetguisettings` by laanwj 路 Pull Request #11338 路 bitcoin/bitcoin 路 GitHub 06:28 < wumpus> sure, but in that case you don't need a call that works on raw transactions, but would just use the wallet api... 06:29 < wumpus> promag: can you please do minor nits the issue instead of IRC, otherwise I'm bound to forget about them 06:30 < bitcoin-git> [bitcoin] laanwj closed pull request #11341: [0.15.0] Bump manpages (0.15...Mf1709-docMan15) https://github.com/bitcoin/bitcoin/pull/11341 06:37 < promag> wumpus: sure, done 06:37 < wumpus> thanks 06:40 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 06:42 -!- supay [6a334193@gateway/web/freenode/ip.106.51.65.147] has quit [Quit: Page closed] 06:43 -!- BashCo_ [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 246 seconds] 06:49 < bitcoin-git> [bitcoin] laanwj pushed 1 new commit to 0.15: https://github.com/bitcoin/bitcoin/commit/f266f2668bf8fd73015bf8265f0d00f5e858b577 06:49 < bitcoin-git> bitcoin/0.15 f266f26 Wladimir J. van der Laan: qt: Translations update pre-0.15.0.1... 06:51 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev 06:55 < achow101> so is 0.15.0.1 just #11332? 06:55 < gribble> https://github.com/bitcoin/bitcoin/issues/11332 | Fix possible crash with invalid nCustomFeeRadio in QSettings (achow101, TheBlueMatt) by jonasschnelli 路 Pull Request #11332 路 bitcoin/bitcoin 路 GitHub 06:55 < wumpus> yes 06:57 < promag> Why #11332 removes nCustomFeeRadio usage? achow101 06:57 < gribble> https://github.com/bitcoin/bitcoin/issues/11332 | Fix possible crash with invalid nCustomFeeRadio in QSettings (achow101, TheBlueMatt) by jonasschnelli 路 Pull Request #11332 路 bitcoin/bitcoin 路 GitHub 06:57 < achow101> promag: no need for it 06:58 < wumpus> promag: see https://github.com/bitcoin/bitcoin/pull/11334 06:58 < promag> no need for the checkbox? 06:58 < achow101> it was only to store which of the custom fee radio buttons were selected, but now there is only one option, so no need for it 06:59 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 06:59 < achow101> the checkbox is unrelated to that 07:00 < promag> ops, meant radio button 07:01 < bitcoin-git> [bitcoin] laanwj pushed 1 new commit to 0.15: https://github.com/bitcoin/bitcoin/commit/fb7b5293844ea6adc5dcf5ad0a0c5890b4495939 07:01 < bitcoin-git> bitcoin/0.15 fb7b529 Wladimir J. van der Laan: doc: Release notes for 0.15.0.1... 07:02 < promag> achow101: remove ui->labelCustomPerKilobyte->setEnable? 07:02 < promag> IIRC setEnabled on labels does nothing 07:02 < achow101> promag: no, that's required to make that row grayed out if checkBoxMinimumFee is checked 07:02 < achow101> I think 07:06 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 255 seconds] 07:07 < wumpus> yes the proper fix needs more review, which is why we went with the minimal fix that avoids the crash in 0.15.0.1 07:07 < wumpus> * [new tag] v0.15.0.1 -> v0.15.0.1 07:15 -!- DrOlmer [~DrOlmer@unaffiliated/drolmer] has quit [Quit: Leaving] 07:15 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 07:18 -!- pbase [~pbase@unaffiliated/pbase] has joined #bitcoin-core-dev 07:22 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 248 seconds] 07:23 < promag> wumpus: do you think Copy/BackupSettings should be in src/qt/guiutil.cpp since they are "general function" 07:24 < wumpus> not as long as they're only used in one place IMO 07:24 < wumpus> guiutil is a grab-bag for common shared stuff 07:24 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 07:24 < wumpus> if something is used in only one compilation unit, better to have it static and local 07:24 < wumpus> can always be moved later 07:25 < wumpus> let's not try to overdesign this anyhow 07:25 < wumpus> another case of both choices being valid, it doesn't really matter 07:27 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 07:31 < meshcollider> sipa: why didn't you choose a 2 character HRP for bech32 regtest addresses if testnet and mainnet are both 2 characters? 'rb' or something? 07:36 < wumpus> probably because he didn't want to 'burn' a 2 character code on regtest, which is only meant for local testing 07:37 < wumpus> unlike testnet3 and mainnet it's not an 'official' network 07:47 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 07:48 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 07:48 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds] 07:53 -!- zxzzt [~prod@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Ping timeout: 240 seconds] 07:53 -!- sdaftuar [~sdaftuar@unaffiliated/sdaftuar] has quit [Ping timeout: 255 seconds] 07:54 -!- jnewbery [~john@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Ping timeout: 260 seconds] 07:54 -!- zxzzt [~prod@static-100-38-11-146.nycmny.fios.verizon.net] has joined #bitcoin-core-dev 07:55 -!- jnewbery [~john@static-100-38-11-146.nycmny.fios.verizon.net] has joined #bitcoin-core-dev 07:55 -!- sdaftuar [~sdaftuar@static-100-38-11-146.nycmny.fios.verizon.net] has joined #bitcoin-core-dev 07:55 -!- sdaftuar [~sdaftuar@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Changing host] 07:55 -!- sdaftuar [~sdaftuar@unaffiliated/sdaftuar] has joined #bitcoin-core-dev 08:00 < morcos> achow101: while you're playing around in the QT code, i think we want to eliminate the checkbox for "Pay only the required fee ..." 08:00 < morcos> maybe separate PR in case we want to back port 11334 08:01 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 08:02 < achow101> why? 08:03 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds] 08:06 < morcos> sorry, why what? 08:09 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 08:10 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 08:12 < achow101> morcos: why remove that checkbox? It just means that you will be paying the minrelayfee 08:12 < achow101> (although the wording on it probably needs to be changed) 08:13 < morcos> achow101: because you can just select the minrelayfee in the custom box if you want to pay that 08:13 < morcos> it doesn't seem like selecting it as a stand alone option really sends the right message 08:13 < achow101> morcos: the user may not know what the minrelayfee is 08:14 < achow101> also, doesn't it change if the mempool is full? 08:14 < morcos> that number does not change 08:14 < morcos> but regardless of getting rid of that checkbox 08:14 < morcos> i am realizing that it's a bit annoying that you don't know what the minimum is you need to put on your transaction if you are selecting current fee 08:15 < morcos> perhaps we want to output a : minimum to currently be accepted in the mempool fee 08:15 < morcos> but i would suggest people be forced to type that into the box 08:15 < morcos> making it too easy to select that implies it could could be a good idea 08:15 < morcos> unless you're seeing that returned in fee estimation 08:15 < morcos> it's proably not a good idea 08:16 < achow101> we could change it to update the custom fee box with the fee rate that it would be using 08:17 < morcos> not sure i follow 08:17 < morcos> it uses the fee rate you give it 08:17 < morcos> if you're using custom fee (as opposed to recommended) 08:18 < morcos> even if such fee would not get you accepted to the mempool 08:19 < achow101> I meant that if you check the box to use minrelayfee, it can display the fee rate that it is using in the custom fee rate box right above it 08:19 < morcos> i just don't think we should give users an option to use the minimum 08:20 < morcos> it has very limited benefit... the options should be.. recommended (for a given target) or you specify 08:20 < morcos> we discussed in SF, and i thought there was other agreement with this idea 08:22 < bitcoin-git> [bitcoin] danra opened pull request #11342: Add sanity assert in CheckSequenceLocks (master...patch-13) https://github.com/bitcoin/bitcoin/pull/11342 08:22 < achow101> I'm afraid that if someone wants to use the minimum that they will accidentally enter 1 sat/kB (not 1000 sat/kB) in the box if they don't have the option to use the minimum 08:22 < morcos> well, in that case it'll be changed to 1000 for them 08:22 < achow101> although I suppose that can be fixed by lower bounding the box to the minrelayfee 08:22 -!- Dizzle [~dizzle@108.171.182.16] has joined #bitcoin-core-dev 08:23 < morcos> it already lower bounds.. but it doesn't really tell you it's going to 08:24 < morcos> in any case, i suppose there are a lot of options for how to improve this area... so maybe its not critical right now 08:28 < gmaxwell> you could also put 0 in the custom box and get clamped to min relay fee. no 08:28 < gmaxwell> oh nevermind 08:29 < luke-jr> another reason I thought of, that people might want to keep it: this way you can check the min fee checkbox, while retaining the current saved value for the manual fee 08:29 < luke-jr> but that use case might be better served by allowing users to define pre-set values 08:30 < morcos> gmaxwell: yes that does work 08:31 < gmaxwell> the nevermind was because on the line before mine you pointe dthat out. :) 08:32 < morcos> i'm not sure of the QT mojo to do this easily, but seems like the best outcome might be to replace the checkbox with a display of what the mempool min fee is, and have a way to click that and have it populated into the custom box 08:32 < morcos> then we're missing informing people of what the min relay fee is in case they actually wanted to do a tx that wouldn't yet be accepted into the mempool, but that seems pretty advanced, and maybe people will know that if they want to do it 08:33 < morcos> submitting these super low fee txs does have the use case for manually managed rbf bumping 08:37 -!- jtimon [~quassel@199.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 260 seconds] 08:39 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has quit [Quit: .] 08:41 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has joined #bitcoin-core-dev 08:51 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 255 seconds] 08:55 -!- fengling [~fengling@2400:8901::f03c:91ff:fe61:b65c] has quit [Ping timeout: 246 seconds] 08:55 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 08:55 -!- fengling_ [~fengling@2400:8901::f03c:91ff:fe61:b65c] has joined #bitcoin-core-dev 08:58 -!- riemann [~riemann@ip-222-88.ists.pl] has joined #bitcoin-core-dev 09:04 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 09:12 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 09:18 -!- JackH [~laptop@46.231.18.66] has quit [Quit: Leaving] 09:37 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-rkvowqyvcztbilar] has quit [Quit: Connection closed for inactivity] 09:43 < bitcoin-git> [bitcoin] isghe opened pull request #11343: added `-walletallowsymboliclink` (default false) (0.15...wallet-allow-symbolic-link) https://github.com/bitcoin/bitcoin/pull/11343 09:48 -!- riemann [~riemann@ip-222-88.ists.pl] has quit [Ping timeout: 248 seconds] 10:05 -!- timothy [~tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!] 10:07 -!- Lauda [~quassel@unaffiliated/lauda] has quit [Remote host closed the connection] 10:07 -!- Lauda [~quassel@unaffiliated/lauda] has joined #bitcoin-core-dev 10:10 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 10:12 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-uuuqpcquxyefnngt] has joined #bitcoin-core-dev 10:12 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 264 seconds] 10:13 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:14 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 10:14 -!- atroxes [~atroxes@unaffiliated/atroxes] has quit [Quit: bye] 10:15 -!- atroxes [~atroxes@unaffiliated/atroxes] has joined #bitcoin-core-dev 10:17 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 240 seconds] 10:18 -!- pergaminho [~Cleber@201.47.91.172] has joined #bitcoin-core-dev 10:21 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 252 seconds] 10:29 -!- atroxes [~atroxes@unaffiliated/atroxes] has quit [Quit: bye] 10:30 < warren> Yikes. I had been using my wallet as a symbolic link for years now. 10:31 < sipa> i wasn't even aware that could work... 10:31 -!- atroxes [~atroxes@unaffiliated/atroxes] has joined #bitcoin-core-dev 10:31 < warren> It worked just fine. 10:33 -!- RubenSomsen [~RubenSoms@1.217.138.142] has quit [Ping timeout: 260 seconds] 10:35 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 10:39 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Quit: laurentmt] 10:41 < luke-jr> it shouldn't..? 10:41 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Killed (Sigyn (Spam is off topic on freenode.))] 10:44 < warren> It worked for me for years. #10885 sounds like it got more complicated with the possibility of the same wallet being opened multiple times after multi wallet was added 10:44 < gribble> https://github.com/bitcoin/bitcoin/issues/10885 | Reject invalid wallets by promag 路 Pull Request #10885 路 bitcoin/bitcoin 路 GitHub 10:44 < warren> was there concern about single wallet being broken with a symlink? that worked for me for years 10:47 < luke-jr> warren: the concern is situations like your own: it doesn't work in a way that is useful 10:47 < gmaxwell> wallets being on different media than the /database directory will result in corruption. 10:47 < luke-jr> warren: wallet.dat being on an encrypted fs doesn't provide you any security 10:49 * BlueMatt also got someone on IRC asking why the PPA broke his wallet-symlink 10:49 < BlueMatt> I was like "oh, please dont do that...I mean will usually work, but if your system crashes, you may get fucked" 10:51 < warren> OK, maybe I was lucky to never run into problems. 10:52 < BlueMatt> well we have a loop that compacts wallet like every 100ms, and (usually) if you crash post-compact pre-writing-new-stuff you're ok, but bdb makes no guarantees there, and certainly you can get screwed if you miss the time window there 10:54 -!- RubenSomsen [~RubenSoms@1.217.138.142] has joined #bitcoin-core-dev 10:55 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:58 < luke-jr> and I'd expect the wallet data to be written to the unencrypted database/ dir before getting into wallet.dat 10:58 < BlueMatt> i believe it does, yes 10:58 < BlueMatt> or the .log file 10:58 < gmaxwell> everything written to wallet.dat first goes through the database/ dir. IIRC 10:59 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 11:01 -!- delinquentme [~delinquen@108-235-112-153.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev 11:01 -!- Dizzle [~dizzle@108.171.182.16] has quit [Quit: Leaving...] 11:01 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 11:03 < delinquentme> running bitcoind w the option --assumevalid= but Im not seeing an update in the "verificationprogress" ... If i've given it a block that is only hours old ... shouldnt that verification shoot up? 11:04 < gmaxwell> Nope. 11:05 < gmaxwell> assume valid means skipping script processing, it doesn't (and cannot) avoid having to process blocks. 11:06 < gmaxwell> also, setting an assumevalid right now won't do much, as the default is a fairly recent. 11:07 < delinquentme> so if I've got a low compute node that I want this on, my best option for speeding up the verification is side loading it? 11:08 -!- adiabat [~adiabat@45.63.20.152] has quit [Quit: WeeChat 1.4] 11:08 -!- adiabat [~adiabat@45.63.20.152] has joined #bitcoin-core-dev 11:09 < gmaxwell> delinquentme: yes, or just be patient, if your system is fast enough to keep up it will catch up. 11:09 -!- Dizzle [~dizzle@108.171.182.16] has joined #bitcoin-core-dev 11:11 < BlueMatt> also -dbcache 11:12 < gmaxwell> BlueMatt: I didn't suggest that because most cpu starved things don't have ram. 11:13 < BlueMatt> ah, well sure, just saying crank it if possible 11:17 < delinquentme> yeah I've got that specd at 8 gigs on the machine doing the sideloading 11:17 < delinquentme> I've got a total of 16 ... any reason I shouldn't make it 12g? 11:22 < sipa> it won't use that much 11:22 < sipa> i believe it maxes out at around dbcache=6000 11:22 < sipa> but setting it higher won't hurt 11:26 < BlueMatt> ha! https://github.com/bitcoin/bitcoin/pull/11226#issuecomment-329289991 <-- fuck yea, I add locks 11:29 < sdaftuar> everyone needs a hobby! :) 11:29 < StopAndDecrypt_> gmaxwell, how do you measure your sync time data? 11:30 -!- singhj [290d8c5a@gateway/web/freenode/ip.41.13.140.90] has joined #bitcoin-core-dev 11:30 < StopAndDecrypt_> pen and pencil or do you monitor with a tool? 11:30 < BlueMatt> sdaftuar: considering my current push is refactoring the world to remove lockorder dependancies that may actually be true........ 11:30 < StopAndDecrypt_> im gonna be setting up 0.15 on a rapberry pi3 in the next few weeks if you want i can try and share the info 11:30 < StopAndDecrypt_> if it would be useful 11:32 -!- singhj [290d8c5a@gateway/web/freenode/ip.41.13.140.90] has quit [Client Quit] 11:34 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 11:35 < gmaxwell> StopAndDecrypt_: debug log timestamp differences. 11:35 < gmaxwell> you can make the logs have microsecond precision too. 11:36 < achow101> StopAndDecrypt_: Look at the debug.log file and check the timestamps for when you start the sync and when IsInitialBlockDownload is finished 11:37 < StopAndDecrypt_> makes sense, just curious if that info would be useful. 11:40 < bitcoin-git> [bitcoin] jnewbery opened pull request #11345: [tests] Check connectivity before sending in assumevalid.py (master...assume_valid_improvement) https://github.com/bitcoin/bitcoin/pull/11345 11:46 -!- RubenSomsen [~RubenSoms@1.217.138.142] has quit [Ping timeout: 260 seconds] 11:59 < BlueMatt> jonasschnelli: do you believe the latest qt only fixed the offscreen issue, or did you also intend to imply that it also fixed the setSortingEnabled thing? 12:03 -!- rpifan [~rpifan@136.55.8.76] has joined #bitcoin-core-dev 12:07 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has quit [Ping timeout: 248 seconds] 12:08 -!- jtimon [~quassel@199.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 12:08 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 246 seconds] 12:09 -!- Alina-malina [~Alina-mal@37.157.223.81] has joined #bitcoin-core-dev 12:09 -!- Alina-malina [~Alina-mal@37.157.223.81] has quit [Changing host] 12:09 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has joined #bitcoin-core-dev 12:13 -!- Austindoggie [~austindog@96-64-238-65-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 12:15 -!- Austindoggie [~austindog@96-64-238-65-static.hfc.comcastbusiness.net] has quit [Client Quit] 12:22 -!- tErik_mc [~tErik@unaffiliated/terik] has quit [Ping timeout: 240 seconds] 12:22 -!- pbase [~pbase@unaffiliated/pbase] has quit [Quit: Leaving] 12:24 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev 12:31 -!- riemann [~riemann@ip-222-88.ists.pl] has joined #bitcoin-core-dev 12:33 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has quit [Ping timeout: 248 seconds] 12:33 -!- Cheeseo [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev 12:34 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Read error: Connection reset by peer] 12:38 -!- Alina-malina [~Alina-mal@37.157.223.81] has joined #bitcoin-core-dev 12:39 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 12:40 -!- Alina-malina [~Alina-mal@37.157.223.81] has quit [Changing host] 12:40 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has joined #bitcoin-core-dev 12:41 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 12:57 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 12:58 -!- Cheeseo [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Ping timeout: 240 seconds] 12:59 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 13:00 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 13:02 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 13:05 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 13:06 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 248 seconds] 13:19 -!- brianhoffman_ [~brianhoff@pool-96-231-163-68.washdc.fios.verizon.net] has quit [Quit: brianhoffman_] 13:22 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 13:23 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit] 13:25 -!- pergaminho [~Cleber@201.47.91.172] has quit [Quit: Saindo] 13:38 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 14:09 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-qcwfnqnvyndrivqc] has joined #bitcoin-core-dev 14:11 -!- RoyceX [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev 14:14 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has quit [Ping timeout: 240 seconds] 14:20 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 14:21 -!- brianhoffman_ [~brianhoff@pool-96-231-163-68.washdc.fios.verizon.net] has joined #bitcoin-core-dev 14:47 -!- rpifan [~rpifan@136.55.8.76] has quit [Ping timeout: 240 seconds] 14:52 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 15:08 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 15:11 -!- riemann_ [~riemann@ip-222-88.ists.pl] has joined #bitcoin-core-dev 15:13 -!- Dizzle [~dizzle@108.171.182.16] has quit [Quit: Leaving...] 15:13 -!- delinquentme [~delinquen@108-235-112-153.lightspeed.sntcca.sbcglobal.net] has quit [Ping timeout: 248 seconds] 15:14 -!- riemann [~riemann@ip-222-88.ists.pl] has quit [Ping timeout: 240 seconds] 15:15 -!- tknp [~tknp@unaffiliated/tknp] has joined #bitcoin-core-dev 15:24 -!- delinquentme [~delinquen@c-73-71-127-234.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 15:26 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 260 seconds] 15:39 -!- riemann_ [~riemann@ip-222-88.ists.pl] has quit [Remote host closed the connection] 15:58 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 16:07 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 16:19 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-qcwfnqnvyndrivqc] has quit [Quit: Connection closed for inactivity] 16:24 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 16:26 -!- cdodd [~cdodd@host109-153-135-26.range109-153.btcentralplus.com] has joined #bitcoin-core-dev 16:30 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-ihohsnnsnyutmyxm] has joined #bitcoin-core-dev 16:33 < jonasschnelli> BlueMatt: I don't think setSortingEnabled is fixed in newer Qt versions 16:39 -!- cdodd [~cdodd@host109-153-135-26.range109-153.btcentralplus.com] has quit [Quit: Konversation terminated!] 16:46 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has quit [Quit: Page closed] 16:55 -!- tknp [~tknp@unaffiliated/tknp] has quit [Quit: tknp] 16:57 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Textual IRC Client: www.textualapp.com] 17:00 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 17:05 -!- blznblzn2 [~blzn@2605:6001:f28d:e600:cf36:4af4:2baf:900a] has quit [Remote host closed the connection] 17:20 -!- brianhoffman_ is now known as brianhoffman 17:26 -!- eenoch [~eenoch@unaffiliated/eenoch] has quit [Quit: leaving] 17:31 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Read error: Connection reset by peer] 17:32 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev 17:37 < luke-jr> jonasschnelli: I don't see any reason to think it's broken..? 17:37 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 17:46 -!- eenoch [~eenoch@unaffiliated/eenoch] has joined #bitcoin-core-dev 17:47 -!- eenoch [~eenoch@unaffiliated/eenoch] has quit [Client Quit] 17:47 -!- eenoch [~eenoch@unaffiliated/eenoch] has joined #bitcoin-core-dev 18:06 -!- rpifan [~rpifan@136.55.8.76] has joined #bitcoin-core-dev 18:08 -!- rpifan [~rpifan@136.55.8.76] has quit [Remote host closed the connection] 18:09 -!- delinquentme [~delinquen@c-73-71-127-234.hsd1.ca.comcast.net] has quit [Quit: Leaving] 18:14 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Ping timeout: 248 seconds] 18:14 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 248 seconds] 18:14 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 248 seconds] 18:14 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 248 seconds] 18:17 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 18:20 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 18:20 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 18:21 < meshcollider> Latest report by dooglus was that it was broken in rc2 with Qt5.7.1 18:21 < meshcollider> https://github.com/bitcoin/bitcoin/issues/9883#issuecomment-325217617 18:26 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev 18:33 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 240 seconds] 18:39 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 18:52 -!- RubenSomsen [~RubenSoms@1.217.138.142] has joined #bitcoin-core-dev 19:10 < luke-jr> wasn't that implicated in the radio button thing? 19:17 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-uuuqpcquxyefnngt] has quit [Quit: Connection closed for inactivity] 19:31 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 20:09 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 255 seconds] 20:29 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-ihohsnnsnyutmyxm] has quit [Quit: Connection closed for inactivity] 20:38 -!- cyzeria [~user@c-73-192-153-254.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 20:39 -!- rjak [~rjak@gateway/vpn/privateinternetaccess/rjak] has quit [Quit: rjak] 20:40 < cyzeria> l 20:41 < cyzeria> Oh, this is cool. 20:41 < cyzeria> I type words on one screen, and they pop out on another. 20:58 -!- cyzeria [~user@c-73-192-153-254.hsd1.ca.comcast.net] has quit [Quit: leaving] 21:02 < bitcoin-git> [bitcoin] aijs opened pull request #11346: Merge pull request #1 from bitcoin/master (master...master) https://github.com/bitcoin/bitcoin/pull/11346 21:02 < bitcoin-git> [bitcoin] fanquake closed pull request #11346: Merge pull request #1 from bitcoin/master (master...master) https://github.com/bitcoin/bitcoin/pull/11346 21:05 < bitcoin-git> [bitcoin] aijs opened pull request #11347: 0.15 (master...0.15) https://github.com/bitcoin/bitcoin/pull/11347 21:05 < bitcoin-git> [bitcoin] fanquake closed pull request #11347: 0.15 (master...0.15) https://github.com/bitcoin/bitcoin/pull/11347 21:21 -!- RubenSomsen [~RubenSoms@1.217.138.142] has quit [Ping timeout: 248 seconds] 21:21 -!- jimpo [~jimpo@ec2-52-42-179-84.us-west-2.compute.amazonaws.com] has quit [Ping timeout: 264 seconds] 21:21 -!- c40d9b0743a91f40 [~2c232c25c@unaffiliated/c40d9b0743a91f40] has quit [Ping timeout: 264 seconds] 21:21 -!- thrasher` [~thrasher@unaffiliated/thrasher/x-7291870] has quit [Ping timeout: 264 seconds] 21:22 -!- jimpo [~jimpo@ec2-52-42-179-84.us-west-2.compute.amazonaws.com] has joined #bitcoin-core-dev 21:22 -!- arowser [~quassel@106.120.101.38] has quit [Ping timeout: 264 seconds] 21:22 -!- cysm [cysm@gateway/shell/elitebnc/x-fkmljjvhepnlkukc] has quit [Ping timeout: 264 seconds] 21:22 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Ping timeout: 264 seconds] 21:22 -!- newbie [~irc@mirk.info] has quit [Ping timeout: 264 seconds] 21:22 -!- waxwing [~waxwing@unaffiliated/waxwing] has quit [Ping timeout: 264 seconds] 21:23 -!- bitbee [~bitbee@138.197.209.248] has quit [Ping timeout: 264 seconds] 21:23 -!- comboy [~quassel@tesuji.pl] has quit [Ping timeout: 264 seconds] 21:23 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev 21:23 -!- c40d9b0743a91f40 [~2c232c25c@unaffiliated/c40d9b0743a91f40] has joined #bitcoin-core-dev 21:23 -!- newbie [~irc@mirk.info] has joined #bitcoin-core-dev 21:24 -!- comboy [~quassel@tesuji.pl] has joined #bitcoin-core-dev 21:26 -!- bitbee [~bitbee@138.197.209.248] has joined #bitcoin-core-dev 21:27 -!- waxwing [~waxwing@91.216.245.111] has joined #bitcoin-core-dev 21:28 -!- thrasher` [~thrasher@unaffiliated/thrasher/x-7291870] has joined #bitcoin-core-dev 21:29 -!- cysm [cysm@gateway/shell/elitebnc/x-dsgarvabbgruuvat] has joined #bitcoin-core-dev 21:30 -!- achow101 [~achow101@unaffiliated/achow101] has joined #bitcoin-core-dev 21:35 -!- tknp [~tknp@unaffiliated/tknp] has joined #bitcoin-core-dev 21:37 -!- waxwing [~waxwing@91.216.245.111] has quit [Changing host] 21:37 -!- waxwing [~waxwing@unaffiliated/waxwing] has joined #bitcoin-core-dev 21:46 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 21:49 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 21:50 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 240 seconds] 21:54 -!- alxlu [~alxlu@138.68.58.104] has quit [Quit: ZNC 1.6.5 - http://znc.in] 22:00 -!- alxlu [~alxlu@138.68.58.104] has joined #bitcoin-core-dev 22:18 -!- Orion3k [~Orion3k@47-51-33-228.static.mtpk.ca.charter.com] has quit [Quit: Leaving] 22:26 -!- tErik_mc [~tErik@unaffiliated/terik] has joined #bitcoin-core-dev 22:41 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/09627b1dd41d...e278f86c5369 22:41 < bitcoin-git> bitcoin/master 1444c2e Adam Langley: Switch memory_cleanse implementation to BoringSSL's to ensure memory clearing even with link-time optimization.... 22:41 < bitcoin-git> bitcoin/master e278f86 Wladimir J. van der Laan: Merge #11196: Switch memory_cleanse implementation to BoringSSL's to ensure memory clearing even with -lto... 22:41 < bitcoin-git> [bitcoin] laanwj closed pull request #11196: Switch memory_cleanse implementation to BoringSSL's to ensure memory clearing even with -lto (master...fix-memory-clense) https://github.com/bitcoin/bitcoin/pull/11196 22:42 -!- jtimon [~quassel@199.31.134.37.dynamic.jazztel.es] has quit [Remote host closed the connection] 22:53 -!- pbase [~pbase@unaffiliated/pbase] has joined #bitcoin-core-dev 22:58 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 23:02 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 264 seconds] 23:08 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 248 seconds] 23:20 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-cecmcltdnjdtzhwj] has joined #bitcoin-core-dev 23:49 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 23:51 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 23:51 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 23:58 -!- tknp [~tknp@unaffiliated/tknp] has quit [Quit: tknp]