--- Day changed Sat Nov 04 2017 00:13 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has joined #bitcoin-core-dev 00:17 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has quit [Ping timeout: 240 seconds] 00:32 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 00:33 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 01:19 -!- ula|2 [~kvirc@b2b-78-94-11-194.unitymedia.biz] has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/] 01:19 < wumpus> * [new tag] v0.15.1rc1 -> v0.15.1rc1 01:24 < meshcollider> \o/ 01:26 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 01:26 < meshcollider> will start gitian building now then 01:26 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 01:28 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 1.7.1] 01:33 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has quit [Ping timeout: 258 seconds] 01:41 -!- ula [~kvirc@b2b-78-94-11-194.unitymedia.biz] has joined #bitcoin-core-dev 01:48 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 01:51 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 02:02 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 03:09 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-qdsxsqgjcrzzmffx] has quit [Quit: Connection closed for inactivity] 03:10 < fanquake> I've PR some sigs if anyone wants to compare. 03:12 < meshcollider> linux looks good, still building windows and mac atm 03:15 -!- NielsvG [~Necrathex@unaffiliated/necrathex] has quit [Ping timeout: 258 seconds] 03:16 -!- jouke [~jouke@a80-100-203-151.adsl.xs4all.nl] has quit [Ping timeout: 252 seconds] 03:21 -!- NielsvG [~Necrathex@2001:982:aa8:1:76d4:35ff:fe12:58d6] has joined #bitcoin-core-dev 03:21 -!- NielsvG [~Necrathex@2001:982:aa8:1:76d4:35ff:fe12:58d6] has quit [Changing host] 03:21 -!- NielsvG [~Necrathex@unaffiliated/necrathex] has joined #bitcoin-core-dev 03:58 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 04:05 -!- murr4y [ali@100.94.211.130.bc.googleusercontent.com] has joined #bitcoin-core-dev 04:05 < Lauda> ping wumpus 04:23 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 04:54 -!- xinxi [~xinxi@39.109.214.22] has quit [Remote host closed the connection] 04:54 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Ping timeout: 248 seconds] 04:55 -!- xinxi [~xinxi@39.109.214.22] has joined #bitcoin-core-dev 05:00 -!- Provoostenator [~textual@54693D0F.cm-12-2a.dynamic.ziggo.nl] has joined #bitcoin-core-dev 05:02 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has joined #bitcoin-core-dev 05:04 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 05:07 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev 05:16 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has quit [Ping timeout: 248 seconds] 05:18 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has quit [Remote host closed the connection] 05:18 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has joined #bitcoin-core-dev 05:22 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has quit [Ping timeout: 248 seconds] 05:34 < Provoostenator> Is v0.15.1 simply what was called v0.15.0.2 before? I.e. some tweaks to deal with the upcoming fork, but not full SegWit support? 05:35 < Provoostenator> And also, is it useful if I run Gitian on this? 05:37 -!- joemphilips_ [276ed47d@gateway/web/freenode/ip.39.110.212.125] has joined #bitcoin-core-dev 05:42 < wxss> Provoostenator: to your first question, v0.15.1 (previously called v0.15.0.2) is the extra release to better deal with the 2X shitshow. Segwit support had to be delayed because of this to the next release, likely to be called v0.15.2 05:42 < Provoostenator> @wxss thanks 06:01 < bitcoin-git> [bitcoin] Sjors opened pull request #11605: [Qt] Enable RBF by default (master...rbf-default) https://github.com/bitcoin/bitcoin/pull/11605 06:07 < Provoostenator> ^ that was me 06:11 -!- g_ [5e017693@gateway/web/freenode/ip.94.1.118.147] has joined #bitcoin-core-dev 06:11 -!- g_ [5e017693@gateway/web/freenode/ip.94.1.118.147] has quit [Client Quit] 06:18 -!- ekrion [~ff@adsl201-232-238-252.epm.net.co] has joined #bitcoin-core-dev 06:27 -!- voilk [b9302498@gateway/web/freenode/ip.185.48.36.152] has joined #bitcoin-core-dev 06:27 -!- voilk [b9302498@gateway/web/freenode/ip.185.48.36.152] has quit [Client Quit] 06:34 -!- warxhead [warxhead@c-73-243-180-191.hsd1.co.comcast.net] has quit [] 07:42 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 07:51 -!- mlz [~IRCIdent@unaffiliated/molly] has quit [Quit: ZNC 1.6.5 - http://znc.in] 07:53 < Provoostenator> I'm trying to make a Gitian build. Installing Virtual Box and Debian was easy, but this part of the instructions is confusing: https://github.com/bitcoin-core/docs/blob/master/gitian-building.md 07:53 < Provoostenator> (VirtualBox running on OSX) 07:54 < Provoostenator> bitcoin/contrib/gitian-build.sh --setup --lxc -b signer v0.15.1rc1 07:54 < Provoostenator> (or with 0.15.1 instead of v0.15.1rc1) 07:54 < MarcoFalke> What is the issue? 07:55 -!- mlz [~IRCIdent@unaffiliated/molly] has joined #bitcoin-core-dev 07:55 < Provoostenator> It starts with a bunch of errors: 07:55 < Provoostenator> Cannot build for OSX, SDK does not exist. Will build for other OSes 07:55 < Provoostenator> v-b 07:55 < Provoostenator> Reading package lists... Done 07:55 < Provoostenator> Building dependency tree 07:55 < Provoostenator> Reading state information... Done 07:55 < Provoostenator> E: Unable to locate package python-vm-builder 07:55 < Provoostenator> fatal: destination path 'gitian.sigs' already exists and is not an empty directory. 07:56 < Provoostenator> fatal: destination path 'bitcoin-detached-sigs' already exists and is not an empty directory. 07:56 < Provoostenator> fatal: destination path 'gitian-builder' already exists and is not an empty directory. 07:56 < Provoostenator> ~/gitian-builder ~ ~ 07:56 < Provoostenator> Then it seems to move along happily, e.g.: 07:56 < Provoostenator> I: Configuring initramfs-tools... 07:56 < Provoostenator> I: Configuring ureadahead... 07:56 < Provoostenator> I: Base system installed successfully. 07:56 < Provoostenator> 1+0 records in 07:56 < Provoostenator> 1+0 records out 07:56 < Provoostenator> 1048576 bytes (1.0 MB) copied, 0.00145623 s, 720 MB/s 07:56 < Provoostenator> mke2fs 1.42.12 (29-Aug-2014) 07:56 < Provoostenator> Discarding device blocks: done 07:56 < Provoostenator> Creating filesystem with 2621440 4k blocks and 656640 inodes 07:56 < Provoostenator> Filesystem UUID: 7b433e1a-b962-473d-8192-3c78d20ec64a 07:56 < Provoostenator> Superblock backups stored on blocks: 07:56 < Provoostenator> 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 07:56 < Provoostenator> Allocating group tables: done 07:56 < Provoostenator> Writing inode tables: done 07:56 < Provoostenator> Creating journal (32768 blocks): done 07:56 < Provoostenator> Writing superblocks and filesystem accounting information: done 07:56 < Provoostenator> And then it fails: 07:56 < eck> plz 07:56 < Provoostenator> ~ ~ 07:56 < eck> no flooding 07:56 < Provoostenator> ~/bitcoin ~ ~ 07:56 < Provoostenator> error: pathspec 'v-b' did not match any file(s) known to git. 07:56 < Apocalyptic> have you heard of pastebin ? 07:56 < Provoostenator> Oops, I'll use a gist 07:56 < MarcoFalke> You'd need to fetch the osx sdk somewhere 07:56 < Provoostenator> My IRC client split the message up in 100 parts, that wasn't the plan. 07:56 < eck> yes, that is how IRC works 07:57 < MarcoFalke> I think they are hosted on some apple developer website 07:57 < MarcoFalke> Also, random people might have uploaded them to GitHub somewhere 07:57 < MarcoFalke> You can also skip the osx build for now 07:57 < Provoostenator> I have an Apple developer account, so that should be doable. Do I need to get the old MaxOSX10.11 stuff? 07:58 < Provoostenator> Skipping it is probably better for now, I'd like to see ifI can get the other builds to work. 07:58 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-bbqiakxbjcufrebq] has quit [Quit: Connection closed for inactivity] 08:02 < MarcoFalke> Refer to https://github.com/bitcoin/bitcoin/blob/master/doc/README_osx.md for instructions to download the apple sdk 08:03 < Provoostenator> I've seen those instructions; they're not really clear, but I'll give it a shot. 08:03 < Provoostenator> (I'll make some PR's to improve them once I manage to do a succesfull build) 08:18 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 08:18 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 08:19 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 08:19 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Client Quit] 08:19 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 08:23 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 258 seconds] 08:23 < achow101> Provoostenator: it should be 0.15.1rc1 not v0.15.1rc1 08:26 < achow101> Provoostenator: there's no --lxc option 08:26 < achow101> lxc is what it uses by default 08:26 < Provoostenator> Ok and "signer" needs to be my email (for the PGP key)? 08:26 < achow101> yes 08:27 < achow101> does not necessarily need to be your email, could just be your username or some name that GPG recognizes 08:28 < Provoostenator> Github username? 08:28 < achow101> yeah 08:29 < achow101> if that doesn't match your PGP key, you can use --detach-sign and sign it later. the signer name is used to organize the sigs into folders with each signer's name so having something like github username for that is better 08:30 < Provoostenator> So I should either move my GPG key onto the VM, or just do the actual signing on my machine? 08:31 < achow101> yes 08:31 < achow101> I suggest signing on your machine 08:33 < Provoostenator> debian@debian:~$ bitcoin/contrib/gitian-build.sh -b sjors 0.15.1rc1 --detached-sign 08:33 < Provoostenator> lxcbr0: ERROR while getting interface flags: No such device 08:33 < Provoostenator> SIOCSIFADDR: No such device 08:34 < sipa> you don't have lxc 08:34 < Provoostenator> I didn't see any obvious errors while doing this: https://github.com/bitcoin-core/docs/blob/master/gitian-building/gitian-building-setup-gitian-debian.md#setting-up-debian-for-gitian-building 08:36 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 08:47 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 08:51 < Provoostenator> Switching bitcoin repo to master first did the trick. This might be related: https://github.com/bitcoin/bitcoin/pull/11391 08:59 -!- RoyceX [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev 09:02 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has quit [Ping timeout: 248 seconds] 09:04 -!- joemphilips_ [276ed47d@gateway/web/freenode/ip.39.110.212.125] has quit [Ping timeout: 260 seconds] 09:05 -!- dabura667 [~dabura667@172.56.38.178] has joined #bitcoin-core-dev 09:06 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Quit: Leaving.] 09:15 -!- jouke [~jouke@a80-100-203-151.adsl.xs4all.nl] has joined #bitcoin-core-dev 09:15 -!- RoyceX [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Ping timeout: 248 seconds] 09:17 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 09:19 -!- neha [~narula@tbilisi.csail.mit.edu] has joined #bitcoin-core-dev 09:23 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has quit [Ping timeout: 240 seconds] 09:27 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 09:30 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 09:30 -!- dabura667 [~dabura667@172.56.38.178] has quit [Ping timeout: 255 seconds] 09:33 -!- donaloconnor [506fff1e@gateway/web/freenode/ip.80.111.255.30] has joined #bitcoin-core-dev 09:33 -!- jouke_ [~quassel@2a01:7c8:aab2:c6:5054:ff:fee1:44f5] has joined #bitcoin-core-dev 09:34 < donaloconnor> Can anyone point to me where in the code bitcoin core checks if the block hash is valid? - I can see it checks POW in CheckBlockHeader 09:34 < sipa> what does that mean? 09:34 < donaloconnor> (FYI - I'm learning the protocol and stepping through the code) 09:34 < sipa> as in, what do you mean by valid? 09:35 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has joined #bitcoin-core-dev 09:35 < donaloconnor> the hash the miners generate for a block 09:35 < sipa> which validity rule, i mean? difficulty, pow, merkle root commitment, ...? 09:37 < sipa> and i can be a bit pedantic: the hash is computed - it's not that miners "claim" it has a certain hash; it's just how we identify blocks 09:37 < sipa> by definition the hash itself is always valid 09:38 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has quit [Ping timeout: 252 seconds] 09:38 < sipa> of course, there are many rules that the block has to satisfy 09:38 < donaloconnor> I guess it's pow? - I'm not entirely sure... apologies I'm learning. Miners generate the block hash to find one that satisfies the difficulty. I mean, where does bitcoin core check that this hash is actually valid (ie: hashing the block again results int he same hash) 09:38 < sipa> it does not verify that anywhere 09:38 < sipa> nobody claims a block has a certain hash 09:39 < sipa> the block itself is propagated 09:39 < sipa> and to be valid, its hash has to satisfy PoW 09:39 < sipa> (but that's only one out of dozens of validity criteria) 09:42 -!- kkode [~eliasc@ool-18bfd89e.dyn.optonline.net] has joined #bitcoin-core-dev 09:44 < donaloconnor> my understanding was miners modified parts of the coinbase text + nonce in order to find something that will result in a hash that satisfies pow/difficulty (blocks start with 0000000000000000003) now. I guess i'm asking, what's stopping someone generating a hash that begins with enough zeros that isn't actually the hash of the block header? 09:45 < donaloconnor> I guess i'm missing something here, sorry if I'm sounding silly ;) 09:45 < sipa> well then the block will be invalid 09:45 < donaloconnor> well that's what I mean... where does it check that 09:45 < sipa> perhaps we're arguing semantics 09:45 < sipa> but there is no need to check whether the block matches its claimed hash - nobody ever claims it has a particular hash 09:46 < sipa> the hash is computed from the block 09:46 < sipa> the rule is _for a block to be valid_ that its hash is below the target implied by the difficulty 09:46 < donaloconnor> maybe. I'm looking at ProcessNewBlock and trying to find out where it validates that the hash is infact a valid hash of the block contents. 09:46 < sipa> and you've already found where that is checked 09:46 < aj> donaloconnor: nodes don't communicate the hashes directly, the communicate the headers (and blocks) and then work out what the hash is 09:46 < sipa> the hash is always the hash of the block contents 09:46 < donaloconnor> ahhh 09:46 < sipa> it is defined as such 09:47 < donaloconnor> maybe that's it 09:47 < donaloconnor> sorry 09:47 < donaloconnor> now I understand... 09:48 < donaloconnor> uint256 hash = block.GetHash(); << this is calculated by the nodes and not transmitted over the wire 09:49 < sipa> exactly 09:50 < donaloconnor> sipa/aj - thanks for the information. 09:59 -!- fobban [~martin@h-90-223.A463.priv.bahnhof.se] has joined #bitcoin-core-dev 10:03 < fobban> I'm running (or trying to run) bitcoin-core on arch linux but ever since v0.15 I get a CPU hardware error after a few minutes which causes the computer to reboot. I redownloaded the blockchain but a few seconds after it was complete I got the error again. 10:03 < sipa> sounds like your CPU is overheating 10:03 < fobban> I've got a i7-6700k. Never got these hardware errors before and I only get them once I start bitcoin core again 10:04 < sipa> bitcoin core tends to stress CPUs far more than usual desktop software 10:06 < fobban> ok, let me monitor the temp. I don't think it has to do with that though cause the fans don't really spin up more than usual, but hang on, will probably time out soon :P 10:07 -!- kkode [~eliasc@ool-18bfd89e.dyn.optonline.net] has quit [Quit: kkode] 10:09 < fobban> is v0.15 much harder on the cpu than 0.14 was? 10:13 < sipa> yes, it needs to wait much less on memory 10:14 -!- spudowiar [~spudowiar@unaffiliated/saleemrashid] has joined #bitcoin-core-dev 10:16 < fobban> I see now that I didn't get the crash when the blockchain was complete, I managed to download 91% before it crashed. But temp is steady between 23-30C on all cores. 10:17 < donaloconnor> could be PSU not providing enough power for CPU 10:18 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds] 10:22 < fobban> Hm, might be temp after all, started to spike to 75C now o_O 10:24 < donaloconnor> maybe, though 75 is not uncommon under high load 10:31 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has quit [Read error: Connection reset by peer] 10:33 -!- PaulCape_ [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has joined #bitcoin-core-dev 10:35 -!- aqquadro [~name@2-230-231-230.ip204.fastwebnet.it] has joined #bitcoin-core-dev 10:35 -!- aqquadro [~name@2-230-231-230.ip204.fastwebnet.it] has quit [Changing host] 10:35 -!- aqquadro [~name@unaffiliated/aqquadro] has joined #bitcoin-core-dev 10:40 -!- dabura667 [~dabura667@172.56.38.177] has joined #bitcoin-core-dev 10:43 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [] 10:47 < Provoostenator> Gitian has been diligently working for the past few hours... Is there any way to spot check if the work in progress is correct? 10:48 -!- PaulCape_ [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has quit [Quit: .] 10:49 -!- spudowiar [~spudowiar@unaffiliated/saleemrashid] has left #bitcoin-core-dev ["WeeChat 1.9.1"] 10:50 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has joined #bitcoin-core-dev 10:54 -!- donaloconnor [506fff1e@gateway/web/freenode/ip.80.111.255.30] has quit [Ping timeout: 260 seconds] 10:57 -!- LumberCartel [~randolf@96.53.47.42] has quit [Ping timeout: 240 seconds] 11:01 -!- xinxi [~xinxi@39.109.214.22] has quit [Remote host closed the connection] 11:01 -!- xinxi [~xinxi@39.109.214.22] has joined #bitcoin-core-dev 11:02 -!- dabura667 [~dabura667@172.56.38.177] has quit [Ping timeout: 258 seconds] 11:07 < jouke> w/win 14 11:08 < Provoostenator> To answer my own q: once all linux versions finish building, it spits out a summary with hashes. You can compare that with e.g. gitian.sigs/0.15.1rc1-linux/laanwj/bitcoin-linux-0.15-build.assert 11:09 < Provoostenator> Hopefully this isn't a problem: 11:09 < Provoostenator> ./bin/gsign:52:in `
': invalid option: --detach-sign (OptionParser::InvalidOption) 11:10 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 11:10 -!- Deacyde [~Deacyde@unaffiliated/deacyde] has quit [Ping timeout: 258 seconds] 11:15 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 11:24 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 11:25 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 11:27 -!- dabura667 [~dabura667@172.56.38.177] has joined #bitcoin-core-dev 11:32 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds] 11:33 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 11:33 -!- LumberCartel [~randolf@S01060024369fd648.vc.shawcable.net] has joined #bitcoin-core-dev 11:38 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has joined #bitcoin-core-dev 11:55 -!- dabura667 [~dabura667@172.56.38.177] has quit [Ping timeout: 240 seconds] 11:56 -!- LumberCartel [~randolf@S01060024369fd648.vc.shawcable.net] has quit [Ping timeout: 240 seconds] 11:58 -!- dabura667 [~dabura667@172.56.38.177] has joined #bitcoin-core-dev 12:00 -!- LumberCartel [~randolf@S01060024369fd648.vc.shawcable.net] has joined #bitcoin-core-dev 12:02 -!- dabura667 [~dabura667@172.56.38.177] has quit [Remote host closed the connection] 12:03 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-knrdtkevlkquboci] has joined #bitcoin-core-dev 12:09 -!- LumberCartel [~randolf@S01060024369fd648.vc.shawcable.net] has quit [Ping timeout: 260 seconds] 12:09 -!- uneeb [~uneeb@c-73-162-26-32.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 12:11 < meshcollider> Provoostenator: you can also look at the build logs as it's building, to see how it's going 12:12 < meshcollider> And check for errors 12:16 -!- uneeb [~uneeb@c-73-162-26-32.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds] 12:22 < Provoostenator> @meshcollider those are fun to watch. When I run ./bin/gverify, I assume it checks both the signatures of the other signers as well as that they have the same hashes in their assert files? 12:30 < meshcollider> Provoostenator: hmm I don't think it checks the hashes, just checks the signatures are valid 12:31 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 264 seconds] 12:31 < Provoostenator> So how do I check that my hashes match what others found? I compared a few manually and they match. 12:34 -!- LumberCartel [~randolf@96.53.47.42] has joined #bitcoin-core-dev 12:38 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 12:38 < bitcoin-git> [bitcoin] Sjors opened pull request #11607: Add Gitian PGP key: Sjors (master...gitian-sjors) https://github.com/bitcoin/bitcoin/pull/11607 12:40 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds] 12:41 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 255 seconds] 12:51 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 12:53 -!- LumberCartel [~randolf@96.53.47.42] has quit [Ping timeout: 240 seconds] 12:58 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 12:59 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has quit [Ping timeout: 258 seconds] 12:59 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 13:00 -!- aqquadro [~name@unaffiliated/aqquadro] has quit [Quit: Leaving] 13:22 < ossifrage> :-( ./libtool: line 1720: 10983 Segmentation fault (core dumped) /usr/bin/gcc-ar cru .libs/libsecp256k1.a src/libsecp256k1_la-secp256k1.o 13:28 -!- Evel-Knievel [~Evel-Knie@178-119-237-211.access.telenet.be] has quit [] 13:34 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 13:35 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 248 seconds] 13:40 -!- owowo [~ovovo@185.212.170.51] has joined #bitcoin-core-dev 13:40 -!- owowo [~ovovo@185.212.170.51] has quit [Changing host] 13:40 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 13:58 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 13:58 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 14:01 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 14:03 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 14:09 -!- LumberCartel [~randolf@96.53.47.42] has joined #bitcoin-core-dev 14:10 -!- Provoostenator [~textual@54693D0F.cm-12-2a.dynamic.ziggo.nl] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 14:11 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 14:12 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 14:13 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 14:13 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 14:16 < gmaxwell> ossifrage: hurray compiler bug.. or cpu overheating 14:18 < ossifrage> I was trying (again) to get a flto compile with the current tree. I'm assuming it is a toolchain bug 14:18 < ossifrage> ./libtool: line 1720: 1040 Segmentation fault (core dumped) /usr/bin/gcc-ranlib .libs/libsecp256k1.a 14:19 < gmaxwell> which gcc version 14:20 < ossifrage> gcc is 7.2.1, gcc-ar is 2.27-24 14:21 < ossifrage> Initially I was getting "plugin needed to handle lto object" from /usr/bin/ranlib, so I switched to gcc-{ranlib,ar,nm} 14:23 < gmaxwell> fwiw, there should be no LTO benefit from libsecp256k1 itself, it's a single .c file. (the modules are all in seperate header files, specifically so it gets all the inlining gains possible, without using LTO) 14:25 < ossifrage> gmaxwell, I'm compiling the entire tree with lto, it just happened to go boom on libsecp256k1 14:28 < gmaxwell> ossifrage: in any case, I'm jealous, not that often that you get to report a GCC bug. :P 14:31 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 258 seconds] 14:38 < esotericnonsense> ossifrage: ryzen gcc segfault bug ? 14:42 < ossifrage> esotericnonsense, this is an old xeon (with ecc) and it is repeatable (so not some thermal silliness) 14:42 < esotericnonsense> ah 14:43 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-knrdtkevlkquboci] has quit [Quit: Connection closed for inactivity] 14:46 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 258 seconds] 14:48 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 14:49 -!- fobban [~martin@h-90-223.A463.priv.bahnhof.se] has quit [Quit: Lost terminal] 14:59 -!- LumberCartel [~randolf@96.53.47.42] has quit [Ping timeout: 248 seconds] 15:19 -!- spinza [~spin@196.212.164.26] has quit [Quit: Coyote finally caught up with me...] 15:25 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 15:32 -!- spinza [~spin@196.212.164.26] has joined #bitcoin-core-dev 15:43 < cfields> gitian builders: v0.15.1rc1 codesigs are _finally_ pushed 15:44 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 15:44 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 15:45 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 15:47 -!- sava_ [3e2d71ac@gateway/web/freenode/ip.62.45.113.172] has joined #bitcoin-core-dev 15:47 < sava_> hello, 15:47 < sava_> can anyone tell me command to create new wallet address in linux please 15:48 < sipa> sava_: #bitcoin 15:49 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 252 seconds] 15:51 < sava_> its BTCGPU for bitcoin gold i installed 15:52 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 15:53 < sipa> sava_: not here, #bitcoin 15:53 < sipa> oh, it's for an altcoin - in that case, no idea 15:53 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 15:53 < sava_> cheers 15:53 -!- sava_ [3e2d71ac@gateway/web/freenode/ip.62.45.113.172] has quit [Quit: Page closed] 15:55 < windsok> #bitcoin-forks 16:01 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 16:11 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [] 16:24 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 16:26 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 16:42 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds] 16:44 -!- kkode [~eliasc@ool-18bfd89e.dyn.optonline.net] has joined #bitcoin-core-dev 16:48 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 16:48 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 16:49 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev 16:49 -!- kkode [~eliasc@ool-18bfd89e.dyn.optonline.net] has quit [Ping timeout: 260 seconds] 16:49 < fanquake> cfields lagging as per usual :p 16:52 < fanquake> Have pushed some signed sigs up. 17:05 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 17:17 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 17:20 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 17:22 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [] 17:37 -!- justanotheruser is now known as xustanotheruser 18:07 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 18:14 -!- LumberCartel [~randolf@96.53.47.42] has joined #bitcoin-core-dev 18:31 -!- wunpunch [~Alli@2a02:c7d:49ce:da00:601f:52a0:fa8d:fc64] has joined #bitcoin-core-dev 18:35 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 19:02 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has quit [Remote host closed the connection] 19:04 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-vanyjhpubhfpskvf] has joined #bitcoin-core-dev 19:12 < meshcollider> cfields: yeah about time, whats that, nearly 14.5 hours since wumpus tagged the release ;) 19:14 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has quit [Read error: Connection reset by peer] 19:15 < meshcollider> PRed my sigs too 19:18 -!- ula [~kvirc@b2b-78-94-11-194.unitymedia.biz] has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/] 19:20 -!- PaulCape_ [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has joined #bitcoin-core-dev 19:28 -!- wunpunch [~Alli@2a02:c7d:49ce:da00:601f:52a0:fa8d:fc64] has quit [Read error: Connection reset by peer] 19:31 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has joined #bitcoin-core-dev 19:35 -!- str4d [~str4d@187.153.90.28] has joined #bitcoin-core-dev 19:38 -!- xustanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 258 seconds] 19:39 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [] 19:41 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 19:42 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Client Quit] 19:42 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 19:45 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has quit [Remote host closed the connection] 19:47 -!- Haaggis [~Mutter@2.220.30.18] has joined #bitcoin-core-dev 19:50 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds] 19:54 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-wbniywgmcwfwxbmc] has quit [Quit: Connection closed for inactivity] 19:59 -!- str4d [~str4d@187.153.90.28] has quit [Ping timeout: 252 seconds] 19:59 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 20:00 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev 20:01 -!- Haaggis [~Mutter@2.220.30.18] has quit [Remote host closed the connection] 20:09 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-ynflvbxvyppwbxti] has joined #bitcoin-core-dev 20:19 < achow101> Updated my sigs PR with the codesigned ones 21:18 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 21:24 -!- darkprofet [~darkprofe@gateway/tor-sasl/darkprofet] has joined #bitcoin-core-dev 21:26 < bitcoin-git> [bitcoin] MeshCollider opened pull request #11610: Update release notes for 0.15.1 (0.15...201711_releasenotes0151) https://github.com/bitcoin/bitcoin/pull/11610 21:37 < meshcollider> ryanofsky: you should add the script from https://github.com/bitcoin/bitcoin/pull/11592#pullrequestreview-73922693 to contrib/devtools/ IMO 21:49 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 21:51 -!- xinxi [~xinxi@39.109.214.22] has quit [Remote host closed the connection] 21:51 -!- xinxi [~xinxi@39.109.214.22] has joined #bitcoin-core-dev 21:56 -!- Provoostenator [~textual@54693D0F.cm-12-2a.dynamic.ziggo.nl] has joined #bitcoin-core-dev 22:13 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 248 seconds] 22:17 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 252 seconds] 22:48 -!- darkprofet [~darkprofe@gateway/tor-sasl/darkprofet] has quit [Remote host closed the connection] 23:01 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 23:06 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 258 seconds] 23:16 -!- jouke [~jouke@a80-100-203-151.adsl.xs4all.nl] has quit [Ping timeout: 248 seconds] 23:19 < bitcoin-git> [bitcoin] fanquake opened pull request #11611: [build] Don't fail when passed --disable-lcov and lcov isn't available (master...dontfaillcov) https://github.com/bitcoin/bitcoin/pull/11611 23:32 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 23:33 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 23:47 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has joined #bitcoin-core-dev 23:51 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has quit [Ping timeout: 240 seconds]