12017-11-04T00:08:32  *** Cogito_Ergo_Sum has quit IRC
  22017-11-04T00:15:03  <achow101> why were there no commit messages in IRC?
  32017-11-04T00:19:23  <gmaxwell> they don't show up on other branches?
  42017-11-04T00:24:26  <sipa> i assume that's it
  52017-11-04T00:28:58  *** CubicEar_ has quit IRC
  62017-11-04T00:31:42  <bitcoin-git> [bitcoin] TheBlueMatt opened pull request #11604: [net] Remove ForNode/ForEachNode (master...2017-11-no-foreachnode) https://github.com/bitcoin/bitcoin/pull/11604
  72017-11-04T00:31:51  <bitcoin-git> [bitcoin] TheBlueMatt closed pull request #10697: Do not hold cs_vNodes when making ForEachNode Callbacks (master...2017-06-cnodestateaccessors-5) https://github.com/bitcoin/bitcoin/pull/10697
  82017-11-04T00:36:38  *** StopAndDecrypt has quit IRC
  92017-11-04T00:45:34  *** EL_CARTERO has quit IRC
 102017-11-04T00:45:51  *** StopAndDecrypt has joined #bitcoin-core-dev
 112017-11-04T00:45:51  *** LumberCartel has quit IRC
 122017-11-04T01:04:39  *** grio has joined #bitcoin-core-dev
 132017-11-04T01:16:30  *** vicenteH has quit IRC
 142017-11-04T01:21:09  *** vicenteH has joined #bitcoin-core-dev
 152017-11-04T01:23:29  *** jtimon has quit IRC
 162017-11-04T01:41:45  *** promag has joined #bitcoin-core-dev
 172017-11-04T01:44:38  *** quantbot has joined #bitcoin-core-dev
 182017-11-04T01:45:53  *** quantbot_ has joined #bitcoin-core-dev
 192017-11-04T01:45:53  *** quantbot has quit IRC
 202017-11-04T02:05:15  *** promag has quit IRC
 212017-11-04T02:08:54  *** twistedline has left #bitcoin-core-dev
 222017-11-04T02:09:04  *** d9b4bef9 has quit IRC
 232017-11-04T02:10:24  *** d9b4bef9 has joined #bitcoin-core-dev
 242017-11-04T02:21:00  *** ghost43 has quit IRC
 252017-11-04T02:21:52  *** ghost43 has joined #bitcoin-core-dev
 262017-11-04T02:27:16  *** cheese_ has quit IRC
 272017-11-04T03:00:51  *** xinxi has quit IRC
 282017-11-04T03:01:27  *** xinxi has joined #bitcoin-core-dev
 292017-11-04T03:04:37  *** LumberCartel has joined #bitcoin-core-dev
 302017-11-04T03:50:55  *** quantbot_ has quit IRC
 312017-11-04T04:02:11  *** quantbot has joined #bitcoin-core-dev
 322017-11-04T04:45:15  *** xinxi has quit IRC
 332017-11-04T04:45:48  *** xinxi has joined #bitcoin-core-dev
 342017-11-04T04:49:02  *** arubi has quit IRC
 352017-11-04T04:50:00  *** arubi has joined #bitcoin-core-dev
 362017-11-04T04:57:04  *** xinxi has quit IRC
 372017-11-04T04:57:39  *** xinxi has joined #bitcoin-core-dev
 382017-11-04T05:12:04  *** kkode has quit IRC
 392017-11-04T05:12:44  *** quantbot has quit IRC
 402017-11-04T05:18:06  <ossifrage> Should linearize-data.py still work? It fails sometime after 486000 with "Invalid magic: 00000000", from blk01005.dat (dated Sept 22, 2017)
 412017-11-04T05:19:01  <ossifrage> The resulting .dat file then fails to load with --loadblock
 422017-11-04T05:26:13  <gmaxwell> ossifrage: you need to go add segwit support to it, would be my guess.
 432017-11-04T05:34:34  *** murr4y has quit IRC
 442017-11-04T06:11:04  *** d9b4bef9 has quit IRC
 452017-11-04T06:12:11  *** d9b4bef9 has joined #bitcoin-core-dev
 462017-11-04T06:50:20  *** Lauda has quit IRC
 472017-11-04T06:50:51  *** Lauda has joined #bitcoin-core-dev
 482017-11-04T07:13:19  *** quantbot has joined #bitcoin-core-dev
 492017-11-04T07:17:35  *** quantbot has quit IRC
 502017-11-04T07:32:27  *** SopaXorzTaker has quit IRC
 512017-11-04T07:33:39  *** SopaXorzTaker has joined #bitcoin-core-dev
 522017-11-04T08:19:17  *** ula|2 has quit IRC
 532017-11-04T08:19:52  <wumpus>  * [new tag]         v0.15.1rc1 -> v0.15.1rc1
 542017-11-04T08:24:52  <meshcollider> \o/
 552017-11-04T08:26:22  *** SopaXorzTaker has quit IRC
 562017-11-04T08:26:26  <meshcollider> will start gitian building now then
 572017-11-04T08:26:59  *** SopaXorzTaker has joined #bitcoin-core-dev
 582017-11-04T08:28:40  *** justan0theruser has quit IRC
 592017-11-04T08:33:07  *** grio has quit IRC
 602017-11-04T08:41:20  *** ula has joined #bitcoin-core-dev
 612017-11-04T08:48:32  *** promag has joined #bitcoin-core-dev
 622017-11-04T08:51:29  *** fanquake has joined #bitcoin-core-dev
 632017-11-04T09:02:46  *** promag has quit IRC
 642017-11-04T10:09:18  *** btcdrak has quit IRC
 652017-11-04T10:10:37  <fanquake> I've PR some sigs if anyone wants to compare.
 662017-11-04T10:12:36  <meshcollider> linux looks good, still building windows and mac atm
 672017-11-04T10:15:51  *** NielsvG has quit IRC
 682017-11-04T10:16:26  *** jouke has quit IRC
 692017-11-04T10:21:11  *** NielsvG has joined #bitcoin-core-dev
 702017-11-04T10:21:13  *** NielsvG has joined #bitcoin-core-dev
 712017-11-04T10:58:32  *** cheese_ has joined #bitcoin-core-dev
 722017-11-04T11:05:01  *** murr4y has joined #bitcoin-core-dev
 732017-11-04T11:05:56  <Lauda> ping wumpus
 742017-11-04T11:23:42  *** laurentmt has joined #bitcoin-core-dev
 752017-11-04T11:54:30  *** xinxi has quit IRC
 762017-11-04T11:54:52  *** dermoth has quit IRC
 772017-11-04T11:55:04  *** xinxi has joined #bitcoin-core-dev
 782017-11-04T12:00:43  *** Provoostenator has joined #bitcoin-core-dev
 792017-11-04T12:02:30  *** quantbot has joined #bitcoin-core-dev
 802017-11-04T12:04:50  *** jtimon has joined #bitcoin-core-dev
 812017-11-04T12:07:36  *** dermoth has joined #bitcoin-core-dev
 822017-11-04T12:16:38  *** cheese_ has quit IRC
 832017-11-04T12:18:04  *** quantbot has quit IRC
 842017-11-04T12:18:40  *** quantbot has joined #bitcoin-core-dev
 852017-11-04T12:22:57  *** quantbot has quit IRC
 862017-11-04T12:34:22  <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?
 872017-11-04T12:35:00  <Provoostenator> And also, is it useful if I run Gitian on this?
 882017-11-04T12:37:10  *** joemphilips_ has joined #bitcoin-core-dev
 892017-11-04T12:42:10  <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
 902017-11-04T12:42:43  <Provoostenator> @wxss thanks
 912017-11-04T13:01:09  <bitcoin-git> [bitcoin] Sjors opened pull request #11605: [Qt] Enable RBF by default (master...rbf-default) https://github.com/bitcoin/bitcoin/pull/11605
 922017-11-04T13:07:36  <Provoostenator> ^ that was me
 932017-11-04T13:11:05  *** g_ has joined #bitcoin-core-dev
 942017-11-04T13:18:07  *** ekrion has joined #bitcoin-core-dev
 952017-11-04T13:27:28  *** voilk has joined #bitcoin-core-dev
 962017-11-04T13:34:49  *** warxhead has quit IRC
 972017-11-04T14:42:27  *** AaronvanW has joined #bitcoin-core-dev
 982017-11-04T14:51:44  *** mlz has quit IRC
 992017-11-04T14:53:40  <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
1002017-11-04T14:53:55  <Provoostenator> (VirtualBox running on OSX)
1012017-11-04T14:54:03  <Provoostenator> bitcoin/contrib/gitian-build.sh --setup --lxc -b signer v0.15.1rc1
1022017-11-04T14:54:22  <Provoostenator> (or with 0.15.1 instead of v0.15.1rc1)
1032017-11-04T14:54:57  <MarcoFalke> What is the issue?
1042017-11-04T14:55:16  *** mlz has joined #bitcoin-core-dev
1052017-11-04T14:55:52  <Provoostenator> It starts with a bunch of errors:
1062017-11-04T14:55:52  <Provoostenator> Cannot build for OSX, SDK does not exist. Will build for other OSes
1072017-11-04T14:55:54  <Provoostenator> v-b
1082017-11-04T14:55:54  <Provoostenator> Reading package lists... Done
1092017-11-04T14:55:56  <Provoostenator> Building dependency tree
1102017-11-04T14:55:56  <Provoostenator> Reading state information... Done
1112017-11-04T14:55:58  <Provoostenator> E: Unable to locate package python-vm-builder
1122017-11-04T14:55:58  <Provoostenator> fatal: destination path 'gitian.sigs' already exists and is not an empty directory.
1132017-11-04T14:56:00  <Provoostenator> fatal: destination path 'bitcoin-detached-sigs' already exists and is not an empty directory.
1142017-11-04T14:56:00  <Provoostenator> fatal: destination path 'gitian-builder' already exists and is not an empty directory.
1152017-11-04T14:56:02  <Provoostenator> ~/gitian-builder ~ ~
1162017-11-04T14:56:02  <Provoostenator> Then it seems to move along happily, e.g.:
1172017-11-04T14:56:04  <Provoostenator> I: Configuring initramfs-tools...
1182017-11-04T14:56:04  <Provoostenator> I: Configuring ureadahead...
1192017-11-04T14:56:06  <Provoostenator> I: Base system installed successfully.
1202017-11-04T14:56:06  <Provoostenator> 1+0 records in
1212017-11-04T14:56:08  <Provoostenator> 1+0 records out
1222017-11-04T14:56:08  <Provoostenator> 1048576 bytes (1.0 MB) copied, 0.00145623 s, 720 MB/s
1232017-11-04T14:56:10  <Provoostenator> mke2fs 1.42.12 (29-Aug-2014)
1242017-11-04T14:56:10  <Provoostenator> Discarding device blocks: done
1252017-11-04T14:56:12  <Provoostenator> Creating filesystem with 2621440 4k blocks and 656640 inodes
1262017-11-04T14:56:12  <Provoostenator> Filesystem UUID: 7b433e1a-b962-473d-8192-3c78d20ec64a
1272017-11-04T14:56:14  <Provoostenator> Superblock backups stored on blocks:
1282017-11-04T14:56:14  <Provoostenator> 	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
1292017-11-04T14:56:16  <Provoostenator> Allocating group tables: done
1302017-11-04T14:56:16  <Provoostenator> Writing inode tables: done
1312017-11-04T14:56:18  <Provoostenator> Creating journal (32768 blocks): done
1322017-11-04T14:56:18  <Provoostenator> Writing superblocks and filesystem accounting information: done
1332017-11-04T14:56:20  <Provoostenator> And then it fails:
1342017-11-04T14:56:20  <eck> plz
1352017-11-04T14:56:20  <Provoostenator> ~ ~
1362017-11-04T14:56:22  <eck> no flooding
1372017-11-04T14:56:22  <Provoostenator> ~/bitcoin ~ ~
1382017-11-04T14:56:22  <Provoostenator> error: pathspec 'v-b' did not match any file(s) known to git.
1392017-11-04T14:56:23  <Apocalyptic> have you heard of pastebin ?
1402017-11-04T14:56:24  <Provoostenator> Oops, I'll use a gist
1412017-11-04T14:56:41  <MarcoFalke> You'd need to fetch the osx sdk somewhere
1422017-11-04T14:56:41  <Provoostenator> My IRC client split the message up in 100 parts, that wasn't the plan.
1432017-11-04T14:56:53  <eck> yes, that is how IRC works
1442017-11-04T14:57:07  <MarcoFalke> I think they are hosted on some apple developer website
1452017-11-04T14:57:24  <MarcoFalke> Also, random people might have uploaded them to GitHub somewhere
1462017-11-04T14:57:46  <MarcoFalke> You can also skip the osx build for now
1472017-11-04T14:57:54  <Provoostenator> I have an Apple developer account, so that should be doable. Do I need to get the old MaxOSX10.11 stuff?
1482017-11-04T14:58:35  <Provoostenator> Skipping it is probably better for now, I'd like to see ifI can get the other builds to work.
1492017-11-04T14:58:53  *** meshcollider has quit IRC
1502017-11-04T15:02:03  <MarcoFalke> Refer to https://github.com/bitcoin/bitcoin/blob/master/doc/README_osx.md for instructions to download the apple sdk
1512017-11-04T15:03:17  <Provoostenator> I've seen those instructions; they're not really clear, but I'll give it a shot.
1522017-11-04T15:03:50  <Provoostenator> (I'll make some PR's to improve them once I manage to do a succesfull build)
1532017-11-04T15:18:24  *** AaronvanW has quit IRC
1542017-11-04T15:18:59  *** AaronvanW has joined #bitcoin-core-dev
1552017-11-04T15:19:30  *** justanotheruser has joined #bitcoin-core-dev
1562017-11-04T15:19:50  *** justanotheruser has joined #bitcoin-core-dev
1572017-11-04T15:23:17  *** AaronvanW has quit IRC
1582017-11-04T15:23:35  <achow101> Provoostenator: it should be 0.15.1rc1 not v0.15.1rc1
1592017-11-04T15:26:02  <achow101> Provoostenator: there's no --lxc option
1602017-11-04T15:26:15  <achow101> lxc is what it uses by default
1612017-11-04T15:26:39  <Provoostenator> Ok and "signer" needs to be my email (for the PGP key)?
1622017-11-04T15:26:48  <achow101> yes
1632017-11-04T15:27:33  <achow101> does not necessarily need to be your email, could just be your username or some name that GPG recognizes
1642017-11-04T15:28:10  <Provoostenator> Github username?
1652017-11-04T15:28:15  <achow101> yeah
1662017-11-04T15:29:28  <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
1672017-11-04T15:30:21  <Provoostenator> So I should either move my GPG key onto the VM, or just do the actual signing on my machine?
1682017-11-04T15:31:05  <achow101> yes
1692017-11-04T15:31:15  <achow101> I suggest signing on your machine
1702017-11-04T15:33:54  <Provoostenator> debian@debian:~$ bitcoin/contrib/gitian-build.sh -b sjors 0.15.1rc1 --detached-sign
1712017-11-04T15:33:55  <Provoostenator> lxcbr0: ERROR while getting interface flags: No such device
1722017-11-04T15:33:56  <Provoostenator> SIOCSIFADDR: No such device
1732017-11-04T15:34:09  <sipa> you don't have lxc
1742017-11-04T15:34:54  <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
1752017-11-04T15:36:10  *** Chris_Stewart_5 has joined #bitcoin-core-dev
1762017-11-04T15:47:24  *** cheese_ has joined #bitcoin-core-dev
1772017-11-04T15:51:55  <Provoostenator> Switching bitcoin repo to master first did the trick. This might be related: https://github.com/bitcoin/bitcoin/pull/11391
1782017-11-04T15:59:58  *** RoyceX has joined #bitcoin-core-dev
1792017-11-04T16:02:47  *** cheese_ has quit IRC
1802017-11-04T16:04:45  *** joemphilips_ has quit IRC
1812017-11-04T16:05:35  *** dabura667 has joined #bitcoin-core-dev
1822017-11-04T16:06:20  *** fanquake has quit IRC
1832017-11-04T16:15:16  *** jouke has joined #bitcoin-core-dev
1842017-11-04T16:15:35  *** RoyceX has quit IRC
1852017-11-04T16:17:59  *** cheese_ has joined #bitcoin-core-dev
1862017-11-04T16:19:27  *** neha has joined #bitcoin-core-dev
1872017-11-04T16:23:32  *** cheese_ has quit IRC
1882017-11-04T16:27:01  *** AaronvanW has joined #bitcoin-core-dev
1892017-11-04T16:30:03  *** cheese_ has joined #bitcoin-core-dev
1902017-11-04T16:30:40  *** dabura667 has quit IRC
1912017-11-04T16:33:42  *** donaloconnor has joined #bitcoin-core-dev
1922017-11-04T16:33:47  *** jouke_ has joined #bitcoin-core-dev
1932017-11-04T16:34:02  <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
1942017-11-04T16:34:21  <sipa> what does that mean?
1952017-11-04T16:34:22  <donaloconnor> (FYI - I'm learning the protocol and stepping through the code)
1962017-11-04T16:34:33  <sipa> as in, what do you mean by valid?
1972017-11-04T16:35:02  *** quantbot has joined #bitcoin-core-dev
1982017-11-04T16:35:03  <donaloconnor> the hash the miners generate for a block
1992017-11-04T16:35:29  <sipa> which validity rule, i mean? difficulty, pow, merkle root commitment, ...?
2002017-11-04T16:37:48  <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
2012017-11-04T16:37:57  <sipa> by definition the hash itself is always valid
2022017-11-04T16:38:07  *** cheese_ has quit IRC
2032017-11-04T16:38:13  <sipa> of course, there are many rules that the block has to satisfy
2042017-11-04T16:38:32  <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)
2052017-11-04T16:38:49  <sipa> it does not verify that anywhere
2062017-11-04T16:38:55  <sipa> nobody claims a block has a certain hash
2072017-11-04T16:39:16  <sipa> the block itself is propagated
2082017-11-04T16:39:28  <sipa> and to be valid, its hash has to satisfy PoW
2092017-11-04T16:39:47  <sipa> (but that's only one out of dozens of validity criteria)
2102017-11-04T16:42:00  *** kkode has joined #bitcoin-core-dev
2112017-11-04T16:44:49  <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?
2122017-11-04T16:45:01  <donaloconnor> I guess i'm missing something here, sorry if I'm sounding silly ;)
2132017-11-04T16:45:14  <sipa> well then the block will be invalid
2142017-11-04T16:45:27  <donaloconnor> well that's what I mean... where does it check that
2152017-11-04T16:45:34  <sipa> perhaps we're arguing semantics
2162017-11-04T16:45:58  <sipa> but there is no need to check whether the block matches its claimed hash - nobody ever claims it has a particular hash
2172017-11-04T16:46:07  <sipa> the hash is computed from the block
2182017-11-04T16:46:26  <sipa> the rule is _for a block to be valid_ that its hash is below the target implied by the difficulty
2192017-11-04T16:46:38  <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.
2202017-11-04T16:46:38  <sipa> and you've already found where that is checked
2212017-11-04T16:46:48  <aj> donaloconnor: nodes don't communicate the hashes directly, the communicate the headers (and blocks) and then work out what the hash is
2222017-11-04T16:46:52  <sipa> the hash is always the hash of the block contents
2232017-11-04T16:46:56  <donaloconnor> ahhh
2242017-11-04T16:46:57  <sipa> it is defined as such
2252017-11-04T16:47:00  <donaloconnor> maybe that's it
2262017-11-04T16:47:02  <donaloconnor> sorry
2272017-11-04T16:47:18  <donaloconnor> now I understand...
2282017-11-04T16:48:06  <donaloconnor> uint256 hash = block.GetHash(); << this is calculated by the nodes and not transmitted over the wire
2292017-11-04T16:49:55  <sipa> exactly
2302017-11-04T16:50:19  <donaloconnor> sipa/aj - thanks for the information.
2312017-11-04T16:59:37  *** fobban has joined #bitcoin-core-dev
2322017-11-04T17:03:28  <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.
2332017-11-04T17:03:50  <sipa> sounds like your CPU is overheating
2342017-11-04T17:03:57  <fobban> I've got a i7-6700k. Never got these hardware errors before and I only get them once I start bitcoin core again
2352017-11-04T17:04:24  <sipa> bitcoin core tends to stress CPUs far more than usual desktop software
2362017-11-04T17:06:48  <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
2372017-11-04T17:07:05  *** kkode has quit IRC
2382017-11-04T17:09:11  <fobban> is v0.15 much harder on the cpu than 0.14 was?
2392017-11-04T17:13:47  <sipa> yes, it needs to wait much less on memory
2402017-11-04T17:14:29  *** spudowiar has joined #bitcoin-core-dev
2412017-11-04T17:16:12  <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.
2422017-11-04T17:17:02  <donaloconnor> could be PSU not providing enough power for CPU
2432017-11-04T17:18:41  *** Chris_Stewart_5 has quit IRC
2442017-11-04T17:22:29  <fobban> Hm, might be temp after all, started to spike to 75C now o_O
2452017-11-04T17:24:23  <donaloconnor> maybe, though 75 is not uncommon under high load
2462017-11-04T17:31:30  *** PaulCapestany has quit IRC
2472017-11-04T17:33:24  *** PaulCape_ has joined #bitcoin-core-dev
2482017-11-04T17:35:04  *** aqquadro has joined #bitcoin-core-dev
2492017-11-04T17:35:04  *** aqquadro has joined #bitcoin-core-dev
2502017-11-04T17:40:43  *** dabura667 has joined #bitcoin-core-dev
2512017-11-04T17:43:55  *** AaronvanW has quit IRC
2522017-11-04T17:47:12  <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?
2532017-11-04T17:48:18  *** PaulCape_ has quit IRC
2542017-11-04T17:49:18  *** spudowiar has left #bitcoin-core-dev
2552017-11-04T17:50:03  *** PaulCapestany has joined #bitcoin-core-dev
2562017-11-04T17:54:25  *** donaloconnor has quit IRC
2572017-11-04T17:57:57  *** LumberCartel has quit IRC
2582017-11-04T18:01:23  *** xinxi has quit IRC
2592017-11-04T18:01:57  *** xinxi has joined #bitcoin-core-dev
2602017-11-04T18:02:22  *** dabura667 has quit IRC
2612017-11-04T18:07:44  <jouke> w/win 14
2622017-11-04T18:08:49  <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
2632017-11-04T18:09:29  <Provoostenator> Hopefully this isn't a problem:
2642017-11-04T18:09:29  <Provoostenator> ./bin/gsign:52:in `<main>': invalid option: --detach-sign (OptionParser::InvalidOption)
2652017-11-04T18:10:02  *** Chris_Stewart_5 has joined #bitcoin-core-dev
2662017-11-04T18:10:48  *** Deacyde has quit IRC
2672017-11-04T18:15:09  *** AaronvanW has joined #bitcoin-core-dev
2682017-11-04T18:24:49  *** AaronvanW has quit IRC
2692017-11-04T18:25:28  *** AaronvanW has joined #bitcoin-core-dev
2702017-11-04T18:27:07  *** dabura667 has joined #bitcoin-core-dev
2712017-11-04T18:32:32  *** AaronvanW has quit IRC
2722017-11-04T18:33:01  *** AaronvanW has joined #bitcoin-core-dev
2732017-11-04T18:33:10  *** LumberCartel has joined #bitcoin-core-dev
2742017-11-04T18:38:14  *** grio has joined #bitcoin-core-dev
2752017-11-04T18:55:05  *** dabura667 has quit IRC
2762017-11-04T18:56:57  *** LumberCartel has quit IRC
2772017-11-04T18:58:02  *** dabura667 has joined #bitcoin-core-dev
2782017-11-04T19:00:40  *** LumberCartel has joined #bitcoin-core-dev
2792017-11-04T19:02:18  *** dabura667 has quit IRC
2802017-11-04T19:03:35  *** meshcollider has joined #bitcoin-core-dev
2812017-11-04T19:09:52  *** LumberCartel has quit IRC
2822017-11-04T19:09:59  *** uneeb has joined #bitcoin-core-dev
2832017-11-04T19:11:39  <meshcollider> Provoostenator: you can also look at the build logs as it's building, to see how it's going
2842017-11-04T19:12:00  <meshcollider> And check for errors
2852017-11-04T19:16:05  *** uneeb has quit IRC
2862017-11-04T19:22:38  <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?
2872017-11-04T19:30:44  <meshcollider> Provoostenator: hmm I don't think it checks the hashes, just checks the signatures are valid
2882017-11-04T19:31:34  *** jtimon has quit IRC
2892017-11-04T19:31:53  <Provoostenator> So how do I check that my hashes match what others found? I compared a few manually and they match.
2902017-11-04T19:34:35  *** LumberCartel has joined #bitcoin-core-dev
2912017-11-04T19:38:41  *** laurentmt has quit IRC
2922017-11-04T19:38:45  <bitcoin-git> [bitcoin] Sjors opened pull request #11607: Add Gitian PGP key: Sjors (master...gitian-sjors) https://github.com/bitcoin/bitcoin/pull/11607
2932017-11-04T19:40:47  *** AaronvanW has quit IRC
2942017-11-04T19:41:01  *** Chris_Stewart_5 has quit IRC
2952017-11-04T19:51:36  *** cheese_ has joined #bitcoin-core-dev
2962017-11-04T19:53:57  *** LumberCartel has quit IRC
2972017-11-04T19:58:22  *** zshlyk has quit IRC
2982017-11-04T19:59:40  *** cheese_ has quit IRC
2992017-11-04T19:59:41  *** zshlyk has joined #bitcoin-core-dev
3002017-11-04T20:00:24  *** aqquadro has quit IRC
3012017-11-04T20:22:49  <ossifrage> :-( ./libtool: line 1720: 10983 Segmentation fault      (core dumped) /usr/bin/gcc-ar cru .libs/libsecp256k1.a src/libsecp256k1_la-secp256k1.o
3022017-11-04T20:28:58  *** Evel-Knievel has quit IRC
3032017-11-04T20:34:02  *** jtimon has joined #bitcoin-core-dev
3042017-11-04T20:35:45  *** owowo has quit IRC
3052017-11-04T20:40:38  *** owowo has joined #bitcoin-core-dev
3062017-11-04T20:40:38  *** owowo has joined #bitcoin-core-dev
3072017-11-04T20:58:11  *** Chris_Stewart_5 has joined #bitcoin-core-dev
3082017-11-04T20:58:23  *** AaronvanW has joined #bitcoin-core-dev
3092017-11-04T21:01:34  *** Aaronvan_ has joined #bitcoin-core-dev
3102017-11-04T21:03:01  *** AaronvanW has quit IRC
3112017-11-04T21:09:36  *** LumberCartel has joined #bitcoin-core-dev
3122017-11-04T21:10:53  *** Provoostenator has quit IRC
3132017-11-04T21:11:34  *** Aaronvan_ has quit IRC
3142017-11-04T21:12:12  *** AaronvanW has joined #bitcoin-core-dev
3152017-11-04T21:13:23  *** AaronvanW has quit IRC
3162017-11-04T21:13:40  *** AaronvanW has joined #bitcoin-core-dev
3172017-11-04T21:16:21  <gmaxwell> ossifrage: hurray compiler bug.. or cpu overheating
3182017-11-04T21:18:10  <ossifrage> I was trying (again) to get a flto compile with the current tree. I'm assuming it is a toolchain bug
3192017-11-04T21:18:35  <ossifrage> ./libtool: line 1720:  1040 Segmentation fault      (core dumped) /usr/bin/gcc-ranlib .libs/libsecp256k1.a
3202017-11-04T21:19:05  <gmaxwell> which gcc version
3212017-11-04T21:20:23  <ossifrage> gcc is 7.2.1, gcc-ar is 2.27-24
3222017-11-04T21:21:50  <ossifrage> Initially I was getting "plugin needed to handle lto object" from /usr/bin/ranlib, so I switched to gcc-{ranlib,ar,nm}
3232017-11-04T21:23:36  <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)
3242017-11-04T21:25:42  <ossifrage> gmaxwell, I'm compiling the entire tree with lto, it just happened to go boom on libsecp256k1
3252017-11-04T21:28:16  <gmaxwell> ossifrage: in any case, I'm jealous, not that often that you get to report a GCC bug. :P
3262017-11-04T21:31:40  *** shesek has quit IRC
3272017-11-04T21:38:44  <esotericnonsense> ossifrage: ryzen gcc segfault bug ?
3282017-11-04T21:42:44  <ossifrage> esotericnonsense, this is an old xeon (with ecc) and it is repeatable (so not some thermal silliness)
3292017-11-04T21:42:53  <esotericnonsense> ah
3302017-11-04T21:43:22  *** meshcollider has quit IRC
3312017-11-04T21:46:37  *** Chris_Stewart_5 has quit IRC
3322017-11-04T21:48:26  *** promag has joined #bitcoin-core-dev
3332017-11-04T21:49:05  *** fobban has quit IRC
3342017-11-04T21:59:28  *** LumberCartel has quit IRC
3352017-11-04T22:19:18  *** spinza has quit IRC
3362017-11-04T22:25:45  *** Chris_Stewart_5 has joined #bitcoin-core-dev
3372017-11-04T22:32:58  *** spinza has joined #bitcoin-core-dev
3382017-11-04T22:43:22  <cfields> gitian builders: v0.15.1rc1 codesigs are _finally_ pushed
3392017-11-04T22:44:29  *** AaronvanW has quit IRC
3402017-11-04T22:44:44  *** promag has quit IRC
3412017-11-04T22:45:07  *** AaronvanW has joined #bitcoin-core-dev
3422017-11-04T22:47:13  *** sava_ has joined #bitcoin-core-dev
3432017-11-04T22:47:16  <sava_> hello,
3442017-11-04T22:47:38  <sava_> can anyone tell me command to create new wallet address in linux please
3452017-11-04T22:48:45  <sipa> sava_: #bitcoin
3462017-11-04T22:49:23  *** AaronvanW has quit IRC
3472017-11-04T22:51:02  <sava_> its BTCGPU for bitcoin gold i installed
3482017-11-04T22:52:10  *** Emcy_ has joined #bitcoin-core-dev
3492017-11-04T22:53:00  <sipa> sava_: not here, #bitcoin
3502017-11-04T22:53:23  <sipa> oh, it's for an altcoin - in that case, no idea
3512017-11-04T22:53:27  *** Emcy has quit IRC
3522017-11-04T22:53:50  <sava_> cheers
3532017-11-04T22:53:53  *** sava_ has quit IRC
3542017-11-04T22:55:05  <windsok> #bitcoin-forks
3552017-11-04T23:01:06  *** AaronvanW has joined #bitcoin-core-dev
3562017-11-04T23:11:12  *** AaronvanW has quit IRC
3572017-11-04T23:24:13  *** AaronvanW has joined #bitcoin-core-dev
3582017-11-04T23:26:36  *** AaronvanW has quit IRC
3592017-11-04T23:42:35  *** Chris_Stewart_5 has quit IRC
3602017-11-04T23:44:28  *** kkode has joined #bitcoin-core-dev
3612017-11-04T23:48:39  *** fanquake has joined #bitcoin-core-dev
3622017-11-04T23:48:49  *** dermoth has quit IRC
3632017-11-04T23:49:15  *** dermoth has joined #bitcoin-core-dev
3642017-11-04T23:49:17  *** kkode has quit IRC
3652017-11-04T23:49:23  <fanquake> cfields lagging as per usual :p
3662017-11-04T23:52:18  <fanquake> Have pushed some signed sigs up.