--- Day changed Mon Jan 11 2016 00:04 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-ndpfypiptaokzedm] has joined #bitcoin-core-dev 00:08 -!- trippysalmon [rob@2001:984:6466:0:51d:b5ab:ab61:bed8] has quit [Read error: Connection reset by peer] 00:22 -!- Arnavion2 [arnavion@arnavion.cloudapp.net] has joined #bitcoin-core-dev 00:24 < jonasschnelli> call for final review: https://github.com/bitcoin/bitcoin/pull/6480 00:24 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Quit: Arnavion] 00:24 -!- Arnavion2 is now known as Arnavion 00:28 -!- Arnavion [arnavion@arnavion.cloudapp.net] has quit [Changing host] 00:28 -!- Arnavion [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev 00:31 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Quit: ZNC 1.6.2 - http://znc.in] 00:46 -!- Arnavion [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev 00:55 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Quit: ZNC 1.6.2 - http://znc.in] 00:55 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has joined #bitcoin-core-dev 00:55 -!- Arnavion [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev 01:08 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has quit [Remote host closed the connection] 01:16 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Quit: -] 01:18 -!- Arnavion [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev 01:30 < jonasschnelli> morcos: ping 01:42 -!- AtashiCon [arnavion@unaffiliated/arnavion] has quit [Remote host closed the connection] 01:42 -!- AtashiCon [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev 01:53 -!- rubensayshi [~ruben@c89225.upc-c.chello.nl] has joined #bitcoin-core-dev 02:05 -!- arowser [~quassel@106.120.101.38] has quit [Quit: No Ping reply in 180 seconds.] 02:06 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev 02:11 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 03:12 -!- btccharm [~02@107.150.94.2] has joined #bitcoin-core-dev 03:21 -!- btccharm [~02@107.150.94.2] has quit [Ping timeout: 272 seconds] 03:53 -!- JackH [~Jack@host-80-43-143-228.as13285.net] has joined #bitcoin-core-dev 04:23 -!- adam3us [~Adium@63.138.18.50] has quit [Quit: Leaving.] 04:26 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev 04:37 -!- xiangfu [~xiangfu@111.198.29.54] has quit [Ping timeout: 272 seconds] 04:49 -!- rubensayshi [~ruben@c89225.upc-c.chello.nl] has quit [Ping timeout: 256 seconds] 04:57 -!- Thireus [~Thireus@vps-92.197.170.217.stwvps.net] has joined #bitcoin-core-dev 05:01 -!- rubensayshi [~ruben@212.187.89.225] has joined #bitcoin-core-dev 05:08 -!- adam3us [~Adium@63.138.18.50] has joined #bitcoin-core-dev 05:36 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Quit: laurentmt] 05:38 -!- btccharm [~02@107.150.94.2] has joined #bitcoin-core-dev 05:52 -!- brg444 [18257df2@gateway/web/freenode/ip.24.37.125.242] has joined #bitcoin-core-dev 05:56 -!- Yoghur114 [~Yoghurt11@131.224.198.111] has quit [Ping timeout: 260 seconds] 05:59 -!- Chris_Stewart_5 [~Chris_Ste@173-26-115-141.client.mchsi.com] has joined #bitcoin-core-dev 05:59 -!- Yoghur114 [~Yoghurt11@131.224.198.111] has joined #bitcoin-core-dev 06:02 -!- Yoghur114 [~Yoghurt11@131.224.198.111] has quit [Read error: Connection reset by peer] 06:02 -!- Yoghur114 [~Yoghurt11@131.224.198.111] has joined #bitcoin-core-dev 06:31 -!- zookolaptop [~user@2601:281:8001:26aa:3497:5ba3:9f3c:cb4e] has quit [Ping timeout: 240 seconds] 06:34 -!- zookolaptop [~user@50.141.117.128] has joined #bitcoin-core-dev 06:35 -!- zookolaptop is now known as zooko 06:38 -!- paveljanik [~paveljani@79-98-72-216.sys-data.com] has joined #bitcoin-core-dev 06:38 -!- paveljanik [~paveljani@79-98-72-216.sys-data.com] has quit [Changing host] 06:38 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-core-dev 06:39 < Luke-Jr> what's up with https://github.com/bitcoin/bitcoin/pull/7213 ? seems to me this is a bugfix post-softfork activation, and ought to be in 0.12.. 06:39 -!- zooko` [~user@2601:281:8001:26aa:2570:26be:1433:31b8] has joined #bitcoin-core-dev 06:40 -!- zooko [~user@50.141.117.128] has quit [Ping timeout: 245 seconds] 06:44 -!- zooko` is now known as zooko 06:53 < jonasschnelli> Luke-Jr: Yes. We should backport the OP_NOP2 rename. 06:57 < morcos> Luke-Jr: Can you point out where you think the priority calculation is broken (other than not including not in chain at time of acceptance inputs. I'm pretty sure it doesn't have an off by one error. but if so, it shoudl be fixed 06:58 < Luke-Jr> morcos: immediately after an input is confirmed, its value is multiplied by 0 toward its dependent's priority, rather than 1 06:59 < Luke-Jr> morcos: I discovered this while writing unit tests for your bugfix in 7149 07:00 < Luke-Jr> although thinking about it today, I'm not entirely sure the fix needs to be as complicated as I made it 07:00 < morcos> Luke-Jr: you're saying the supposedly correct dynamic priority is wrong, not that there is a "bug" in the calculation in master? 07:00 < Luke-Jr> morcos: both 07:00 < morcos> i'm sure that the calculation in 7149 is the same as the old calculaiton 07:00 < morcos> its checked in mempool.check isn't it 07:01 < Luke-Jr> morcos: for given height X, it is correct, but for block X+1, it uses height X 07:01 < morcos> can you point me to a line # that you think gives a wrong result (in master) i'm having trouble following what you mean 07:02 < morcos> but this was checked by comparing the new calculation to the old calculation and they were the same to within double precision 07:02 < morcos> (for 7149 version that is) 07:02 < Luke-Jr> this is how I fixed it http://codepad.org/5il1jH1K 07:03 < Luke-Jr> but I'm not sure even that fix is correct now 07:03 < Luke-Jr> probably just the rpcblockchain and mining *calls* need a +1 07:03 < Luke-Jr> oh, and AcceptToMemoryPool's usage probably ought to have a +1, but it hasn't worked right since it was added there 07:04 < morcos> Luke-Jr: I htink you are mistaken 07:04 -!- adam3us [~Adium@63.138.18.50] has quit [Quit: Leaving.] 07:04 < Luke-Jr> morcos: well, then explain why the unit test I wrote doesn't pass on it? :P 07:05 < Luke-Jr> s/unit/rpc/ 07:05 < morcos> So if a new input is included in the block chain at block X. that input adds 0 to the priority of the tx at block X. 07:05 < morcos> but now the inchainINput value will be increased by new input, and the cached height will = X 07:05 < morcos> so if you ask for priority at (X+1) then it will include that newly inchain input in the aging 07:06 < morcos> but this is only relevant to 7149 and not master anyway 07:06 -!- rubensayshi [~ruben@212.187.89.225] has quit [Ping timeout: 272 seconds] 07:06 -!- adam3us [~Adium@63.138.18.50] has joined #bitcoin-core-dev 07:06 < morcos> Luke-Jr: which line in your test fails? 07:06 < Luke-Jr> the main problem is you're asking for priority X when it should be X+1 07:07 < Luke-Jr> morcos: literally every non-zero comparison 07:07 < Luke-Jr> they're always off by one block 07:07 < Luke-Jr> once block X is mined, the current priority for all practical purposes is X+1 07:07 < Luke-Jr> because miners are mining X+1, not X 07:08 < morcos> yes i agree, and that is what is evaluated for mempool acceptance and mining 07:08 < Luke-Jr> mempool acceptance at least uses chainTip.height() 07:08 < morcos> i'm not sure what is returned in getrawmempool, maybe that is wrong 07:09 < Luke-Jr> mining appears to use the correct height, you're right 07:10 < morcos> oh, interesting, perhaps there is a bug in the mempool acceptance code. 07:10 < morcos> i dont think there is a bug in the calculation though.. i'll try to find some time today to look at it 07:10 < morcos> can you point me to the branch with your rpc test so i can try it out 07:12 -!- btccharm [~02@107.150.94.2] has quit [Ping timeout: 272 seconds] 07:12 < Luke-Jr> I haven't committed it yet, because the pruning rpc test fails with it, and I need to confirm it isn't because of my changes 07:12 < Luke-Jr> it's in that patch I linked though 07:19 < morcos> Luke-Jr: nope, no bug in ATMP 07:19 < morcos> The dpriority that is calculated and stored as the starting priority is the priority of the tx at block X (chain tip) 07:20 < morcos> but then when it is evaluated for acceptance to the mempool there is a separate call to GetPriority which feeds in chainActive.height + 1 07:20 < morcos> see line 972 07:21 < morcos> so if your concern is that startingriority represents a priority that is never actual used for anything, i suppose thats true, but thats the way its always been 07:22 < morcos> i believe priority used in any calculations are always correct 07:23 < morcos> the priority value returned by getrawmempool has always been incorrect for currentpriority anyway 07:23 < Luke-Jr> [15:19:58] The dpriority that is calculated and stored as the starting priority is the priority of the tx at block X (chain tip) <-- that's not what it ought to be 07:23 < Luke-Jr> oh 07:23 < Luke-Jr> I see 07:24 < Luke-Jr> morcos: yes, seems the bugs are entirely in getrawmempool then 07:24 < Luke-Jr> which as you note, has never worked right in that regard 07:25 < Luke-Jr> still would be good to fix it though 07:25 < Luke-Jr> if for no reason other than to have working rpc tests 07:25 * Luke-Jr ponders adding priority to the GBT output so we can test that as well 07:26 < morcos> i don't understand what you want to "fix" 07:26 < morcos> startingpriority can be defined to be anything we want 07:26 < morcos> its a meaningless number only used in getrawmempool rpc call 07:26 < morcos> why change the definition of it? 07:27 < Luke-Jr> "currentpriority" at the very least 07:27 < Luke-Jr> with regard to startingpriority, why change it => so it has some meaningful purpose 07:27 < morcos> by fix currentpriority you mean make it evaluate at X+1 ? 07:27 < Luke-Jr> morcos: yes 07:28 < morcos> ehh.. not worth it in my opinion. 07:28 < Luke-Jr> … 07:33 -!- Chris_Stewart_5 [~Chris_Ste@173-26-115-141.client.mchsi.com] has quit [Ping timeout: 276 seconds] 07:43 -!- arubi [~ese168@unaffiliated/arubi] has quit [Ping timeout: 255 seconds] 07:45 -!- Chris_Stewart_5 [~Chris_Ste@104.156.228.69] has joined #bitcoin-core-dev 07:53 -!- arubi [~ese168@unaffiliated/arubi] has joined #bitcoin-core-dev 07:58 -!- rubensayshi [~ruben@c89225.upc-c.chello.nl] has joined #bitcoin-core-dev 08:00 -!- arubi [~ese168@unaffiliated/arubi] has quit [Ping timeout: 255 seconds] 08:01 < morcos> jonasschnelli: ping? 08:01 < morcos> your comments about NotifyTransaction on the abandontransaction PR 08:01 < morcos> i'm concerned that that would be needed in MarkConflicted as well 08:01 < morcos> I just copied the code from there. 08:03 < morcos> I'm not very familiar with how the wallet/gui works, but NotifyTransaction is used to update the GUI I guess? What notifications do we have to worry about? Do other things like the available balance know to get updated if you just do that notification? 08:04 < morcos> your other commits are also things that I think are good ideas, but I'm still holding out hope for abandontransaction to make it in 0.12, so not sure if it helps to add those now or not 08:05 < morcos> again the tx categories are something I have no familiarity with, but it seems to me that you can mark txs you receive as abandoned as well (although i don't think this would have any practical effect now, it might if we in the future sort such txs differently) 08:08 -!- tripleslash_q [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev 08:09 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Ping timeout: 250 seconds] 08:09 -!- arubi [~ese168@unaffiliated/arubi] has joined #bitcoin-core-dev 08:10 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev 08:12 < jonasschnelli> morcos: still here? 08:12 < morcos> yep 08:12 -!- tripleslash_q [~triplesla@unaffiliated/imsaguy] has quit [Ping timeout: 245 seconds] 08:12 * jonasschnelli reading backlog 08:14 < jonasschnelli> morcos: I guess MarkConflicted() is always used together with the NotifyTransaction signal. 08:15 < jonasschnelli> AddToWallet() calls the signal. 08:15 < jonasschnelli> morcos: and sure, ... feel free to keep the informative PRs (listtransactions and new GUI tx state) out for 0.12. 08:15 < morcos> jonasschnelli: oh. interesting. 08:15 < morcos> thats what copy-paste coding gets you! 08:16 < jonasschnelli> abandon use a own db write,... so there it's necesarry. 08:18 < morcos> sorry, i didn't understand that? 08:18 < morcos> but maybe you are trying to say what i was just going to ask about 08:19 < jonasschnelli> hah... 08:19 < morcos> it looks like markconflicted does things like write the tx to the database and mark it dirty on its own, when those same things happen in AddToWallet 08:19 < jonasschnelli> Your new setAbandoned() call creates its own instance of CWalletDB()... 08:19 < jonasschnelli> it's a rare case... because rest is adding keys or adding wtx. 08:20 < jonasschnelli> in terms os wtx,.. everything goes over AddToWallet 08:20 < jonasschnelli> not important at all, .. but you need to call the NotifyTransaction signal then 08:20 < morcos> seems like i also might need to call the -walletnotify script 08:20 < jonasschnelli> (which takes care for balance update, etc. in the GUI) 08:21 < jonasschnelli> morcos: yes. Could be possible... also keep ZMQ in mind (maybe same interfae) 08:21 < jonasschnelli> *interface 08:21 < morcos> i think those same thigns are missing from MarkConflicted in the case it gets called from AddToWalletIfInvolvingMe right? 08:22 < morcos> because it can cause txs to be marked as conflicted , but AddToWallet doesn't get called 08:22 < morcos> because the tx we are considering is the double spend 08:22 < jonasschnelli> yes... could be necessary there. Agreed. But out of scope four your abandoned PR? 08:22 < morcos> perhaps, but i think a necessary bugfix for 0.12 08:23 < jonasschnelli> Yes. Agreed. 08:23 < morcos> ok.. i have to do interview soon, but will work on this this afternoon 08:24 < jonasschnelli> -walletnotify needs also a refactor... your right. 08:25 < jonasschnelli> But can be done later... happy interview. 08:26 -!- zooko [~user@2601:281:8001:26aa:2570:26be:1433:31b8] has quit [Ping timeout: 240 seconds] 08:42 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Ping timeout: 272 seconds] 08:50 < btcdrak> Is there a way to prevent travis from running on a PR? 08:51 < phantomcircuit> btcdrak, dont think so 08:52 < btcdrak> phantomcircuit: TIL https://docs.travis-ci.com/user/customizing-the-build/#Skipping-a-build 09:12 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev 09:13 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Client Quit] 09:46 -!- fkhan_ [weechat@gateway/vpn/mullvad/x-ddpmxlvmbypqyten] has quit [Ping timeout: 245 seconds] 10:04 -!- fkhan_ [weechat@gateway/vpn/mullvad/x-bkbszwdodgvizjkv] has joined #bitcoin-core-dev 10:09 -!- zookolaptop [~user@2601:281:8001:26aa:2570:26be:1433:31b8] has joined #bitcoin-core-dev 10:18 -!- adam3us [~Adium@63.138.18.50] has quit [Quit: Leaving.] 10:21 -!- adam3us [~Adium@63.138.18.50] has joined #bitcoin-core-dev 10:24 -!- droark [~droark@c-24-22-36-12.hsd1.or.comcast.net] has joined #bitcoin-core-dev 10:29 -!- p15 [~p15@101.91.145.64.client.static.strong-tk2.bringover.net] has quit [Ping timeout: 264 seconds] 10:35 -!- adam3us [~Adium@63.138.18.50] has quit [Quit: Leaving.] 11:01 -!- fkhan_ [weechat@gateway/vpn/mullvad/x-bkbszwdodgvizjkv] has quit [Ping timeout: 260 seconds] 11:07 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev 11:08 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Client Quit] 11:13 -!- fkhan_ [weechat@gateway/vpn/mullvad/x-fpbetoxdefhmqdsy] has joined #bitcoin-core-dev 11:14 < Taek> do verion numbers get updated when changes are backported? 11:15 < btcdrak> Taek: what do you mean? 11:15 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev 11:15 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Client Quit] 11:16 < btcdrak> Taek: if something get backported to 0.10 for example it will eventually make it into a 0.10.x maintenance release, if that's what you mean. 11:16 < Taek> say you have v0.10.3, and then you backport a change (e.g. https://github.com/bitcoin/bitcoin/pull/7217#issuecomment-170642993) -> 0.10.4 11:16 < Taek> ok 11:32 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 11:34 < morcos> jonasschnelli: wumpus: actually i took jonas's commit for #7312, but I'm not sure I understand well enough to know whether both additions he added are needed 11:35 < morcos> I'm not sure how the GUI notifications work 11:35 < morcos> but why would it be necessary to call NotifyTransactionChanged there for each of the txs that had an input being spent 11:36 < morcos> But it isn't necessary to do that in SyncTransaction when we are marking those prevtxs dirty b/c their inputs are being spent in the first place? 11:40 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev 11:56 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev 11:58 -!- benjyz1 [~benjyz1@ip-109-47-2-224.web.vodafone.de] has joined #bitcoin-core-dev 12:12 -!- benjyz1 [~benjyz1@ip-109-47-2-224.web.vodafone.de] has quit [Remote host closed the connection] 12:18 -!- zookolaptop [~user@2601:281:8001:26aa:2570:26be:1433:31b8] has quit [Ping timeout: 260 seconds] 12:21 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Quit: laurentmt] 12:27 -!- morcos [~morcos@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Remote host closed the connection] 12:30 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev 12:33 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Client Quit] 12:39 -!- bsm117532 [~mcelrath@38.121.165.30] has quit [Ping timeout: 240 seconds] 13:08 -!- brg444 [18257df2@gateway/web/freenode/ip.24.37.125.242] has quit [Quit: Page closed] 13:11 -!- morcos [~morcos@static-100-38-11-146.nycmny.fios.verizon.net] has joined #bitcoin-core-dev 13:20 -!- jtimon [~quassel@126.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 13:32 < jonasschnelli> morcos: I guess it's necessary. 13:33 < morcos> jonasschnelli: it was hard for me to tell what that Notify call actually does 13:33 < morcos> but it seems to me the two function are determine whether the balance needs to be updated and determine whethehr the transaction record should be shown 13:34 < jonasschnelli> morcos: I think from the wallet perspective it's easy: notify every changed transaction. 13:35 < jonasschnelli> What if a signal listener relays on a info when a child-tx gets abandoned? 13:35 < morcos> jonasschnelli: its not done anywhere else that the only relevant update is whether the txs outputs are spent or not 13:35 < morcos> for instance look at SyncTransaction 13:35 < morcos> it marks all the prevouts as dirty so we can recalculate balances 13:35 < jonasschnelli> (Phone typing)... 13:35 < morcos> but it doesn't notify anything 13:37 < morcos> well take a look tomorrow at your computer, but i think its unnecessary and isn't in keeping with the other places we call NotifyTransaction 13:37 < jonasschnelli> Yes. Maybe we remove the second line. But I think we should look at it from a signal/future-feature perspective. 13:37 < morcos> but I wasn't comfortable enough with the GUI code to change your commit 13:37 < morcos> jonasschnelli: but we have to define what the signals are for 13:37 < jonasschnelli> Okay. I'll have a closer look tmr. 13:37 < jonasschnelli> morcos: not really. :-) 13:38 < morcos> and if we want them to be for letting you know that some previously spent inputs are now unspent, then we need it to be the case for everytime that status changes 13:38 < jonasschnelli> But IMO call whenever a transaction changes. 13:38 < morcos> its very confusing to someone trying to understand the code, if sometimes you call it and sometimes yo udont 13:38 < morcos> this would be literally the only case of calling it for a change like this i think 13:38 < jonasschnelli> Yes. It should follow the same concept everywhere in the code. Agree. 13:39 < jonasschnelli> Yes. 13:39 < jonasschnelli> Remove the seconds line / signal call 13:39 < morcos> ok, great, i'll wait for your thoughts tomorrow. i see your point. someone in the future might want to hide txs that have been completely spent or mark them differently or something. 13:39 < morcos> but then we shoudl be consistent everywhere 13:39 < morcos> ok 13:40 < jonasschnelli> Right. 13:40 < morcos> i'll remove it for now in the hopes that wumpus will merge this if its done changing 13:40 < morcos> thanks! 13:40 < jonasschnelli> Yes. We need to get this in asap. 13:40 < jonasschnelli> Thanks and nite 13:53 -!- gijensen [~gijensen@gijensen.xyz] has quit [Ping timeout: 246 seconds] 13:53 -!- gijensen [~gijensen@gijensen.xyz] has joined #bitcoin-core-dev 13:57 -!- bsm117532 [~mcelrath@38.121.165.30] has joined #bitcoin-core-dev 13:59 < GitHub186> [bitcoin] crowning- opened pull request #7327: [Wallet] Transaction View: LastMonth calculation fixed (master...patch-2) https://github.com/bitcoin/bitcoin/pull/7327 14:06 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has joined #bitcoin-core-dev 14:16 -!- murch [~murch@p4FDB73DB.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 14:39 -!- zookolaptop [~user@50.141.118.160] has joined #bitcoin-core-dev 14:44 -!- zookolaptop [~user@50.141.118.160] has quit [Ping timeout: 265 seconds] 14:44 -!- zookolap` [~user@2601:281:8001:26aa:2570:26be:1433:31b8] has joined #bitcoin-core-dev 15:09 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has quit [Quit: Leaving.] 15:11 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has joined #bitcoin-core-dev 15:13 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has quit [Client Quit] 15:13 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has joined #bitcoin-core-dev 15:17 -!- fkhan_ [weechat@gateway/vpn/mullvad/x-fpbetoxdefhmqdsy] has quit [Ping timeout: 245 seconds] 15:18 -!- Thireus [~Thireus@vps-92.197.170.217.stwvps.net] has quit [Ping timeout: 246 seconds] 15:21 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev 15:21 -!- fkhan_ [weechat@gateway/vpn/mullvad/x-gfanfzttnlduggox] has joined #bitcoin-core-dev 15:28 -!- brg444 [415ce066@gateway/web/freenode/ip.65.92.224.102] has joined #bitcoin-core-dev 15:29 -!- adam3us [~Adium@63.138.18.50] has joined #bitcoin-core-dev 15:41 -!- murch [~murch@p4FDB73DB.dip0.t-ipconnect.de] has quit [Quit: Leaving.] 15:42 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.] 15:45 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)] 16:00 -!- jgarzik [~jgarzik@unaffiliated/jgarzik] has quit [Quit: This computer has gone to sleep] 16:03 -!- jgarzik [~jgarzik@104-178-201-106.lightspeed.tukrga.sbcglobal.net] has joined #bitcoin-core-dev 16:03 -!- jgarzik [~jgarzik@104-178-201-106.lightspeed.tukrga.sbcglobal.net] has quit [Changing host] 16:03 -!- jgarzik [~jgarzik@unaffiliated/jgarzik] has joined #bitcoin-core-dev 16:19 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev 16:20 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Client Quit] 16:30 -!- jgarzik [~jgarzik@unaffiliated/jgarzik] has quit [Quit: This computer has gone to sleep] 16:33 -!- jtimon [~quassel@126.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 255 seconds] 16:40 -!- brg444 [415ce066@gateway/web/freenode/ip.65.92.224.102] has quit [Ping timeout: 252 seconds] 17:03 -!- brg444 [415ce066@gateway/web/freenode/ip.65.92.224.102] has joined #bitcoin-core-dev 17:06 -!- xiangfu [~xiangfu@111.198.29.53] has joined #bitcoin-core-dev 17:07 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev 17:08 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Client Quit] 17:14 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has quit [Read error: Connection reset by peer] 17:20 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has joined #bitcoin-core-dev 17:27 -!- arowser [~quassel@106.120.101.38] has quit [Quit: No Ping reply in 180 seconds.] 17:27 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev 17:38 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-ndpfypiptaokzedm] has quit [Quit: Connection closed for inactivity] 18:10 -!- jgarzik [~jgarzik@unaffiliated/jgarzik] has joined #bitcoin-core-dev 18:10 -!- jgarzik [~jgarzik@unaffiliated/jgarzik] has quit [Client Quit] 18:16 -!- wallet42 [~wallet42@p4249133-ipngn24701marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 18:27 -!- Jimmy16 [~jimmy16@76-9-70-13-rt-broadband-00.broadband.oakhurst.sti.net] has quit [Quit: Leaving] 18:35 -!- p15 [~p15@49.91.145.64.client.static.strong-tk2.bringover.net] has joined #bitcoin-core-dev 19:05 -!- wallet42 [~wallet42@p4249133-ipngn24701marunouchi.tokyo.ocn.ne.jp] has quit [Quit: Leaving.] 19:16 -!- belcher [~user@unaffiliated/belcher] has quit [Quit: Leaving] 19:17 -!- SmiteMeSmith [~SmiteMeSm@WLLDON1606W-LP140-01-2925330739.dsl.bell.ca] has quit [Ping timeout: 256 seconds] 19:18 -!- SmiteMeSmith [~SmiteMeSm@WLLDON1606W-LP140-02-1279535220.dsl.bell.ca] has joined #bitcoin-core-dev 19:33 -!- guest21333 [~02@107.150.94.2] has joined #bitcoin-core-dev 20:21 -!- tripleslash_v [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev 21:09 -!- guest21333 [~02@107.150.94.2] has quit [Quit: Bye] 21:12 -!- brg444 [415ce066@gateway/web/freenode/ip.65.92.224.102] has quit [Ping timeout: 252 seconds] 21:17 -!- maaku [~quassel@botbot.xen.prgmr.com] has left #bitcoin-core-dev ["http://quassel-irc.org - Chat comfortably. Anywhere."] 22:24 -!- zookolap` [~user@2601:281:8001:26aa:2570:26be:1433:31b8] has quit [Ping timeout: 240 seconds] 22:32 < GitHub113> [bitcoin] btcdrak opened pull request #7328: Update README.md website link (master...website) https://github.com/bitcoin/bitcoin/pull/7328 22:38 < Quent> the bitcoin-core website will be copyrighted? 22:45 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-dkbxwcodzgkqnisq] has joined #bitcoin-core-dev 23:07 < btcdrak> Quent #bitcoin 23:13 -!- Squidicuz [~squid@pool-173-48-117-206.bstnma.fios.verizon.net] has quit [Quit: Oh no, not again] 23:28 -!- wallet42 [~wallet42@210.164.9.11] has joined #bitcoin-core-dev 23:47 -!- wallet42 [~wallet42@210.164.9.11] has quit [Quit: Leaving.]