< jabd>
i'm just getting into bitcoin now... where is the canoncial source? I'm getting a bit confused with all of the fork discussions from the past couple of weeks... maybe another way I should put this is - who is canonical upstream? Is github official, should I only pull from https://bitcoin.org/en/download or bitcoinclassic.com?
< jabd>
also, where can I get the latest info for where everyone is headed e.g XT vs 2mb etc
< Luke-Jr>
jabd: Bitcoin has no canonical/official anything.
< Luke-Jr>
jabd: http://bitcoincore.org for stuff by the Core dev team, including scaling plans for Bitcoin
< jabd>
ok thanks
< jabd>
Luke-Jr: on bitcoin.org, I can see lots of mentions of "Bitcoin Core", but I can't see anywhere it links to bitcoincore.org?
< Luke-Jr>
jabd: bitcoin.org is neither official for Bitcoin *nor* for Bitcoin Core
< p15>
those are created by separate people / entities
< p15>
bitcoin.org has more info on wallets etc
< jabd>
so when if people are running Bitcoin code from different places, are they possibly running on the same blockchain or different blockchains? Is there an "official" Bitcoin blockchain, or are these "forks" all running on their own networks? So confused
< jabd>
How's best to educate myself on this more?
< p15>
ask in #bitcoin maybe
< btcdrak>
sort of OT question, sorry, but how many devs here use Macbooks for their coding work?
< gmaxwell>
what what OS?
< gmaxwell>
e.g. bluematt has a macbook but it runs linux.
< michagogo>
cfields: if you want, you can watch as I retry
< michagogo>
ssh ro-thYmcEyGTTIm0RPJm3h2bJmCp@am2.tmate.io to see the build script, and ssh ro-me6PDf23hOTHOloQFCzphFCPj@fk2.tmate.io to see a tailf of the install/build logs
< cfields>
michagogo: i'm hacking on a few things atm, but ping me when it's done :)
< michagogo>
cfields: Okay, I'm not sure I'll still be awake when that happens, but I'll ping you if I see it
< michagogo>
The tmates should stay up, though
< michagogo>
cfields: so if all goes well, you should see a PR from me with the gitian sigs
< cfields>
michagogo: great, thanks
< michagogo>
If it fails again, those tmate sessions will let you see what's happening
< michagogo>
If that happens hopefully I'll be able to work on it via teamviewer from the bus
< michagogo>
cfields: it's breaking again
< michagogo>
Again during the Qt build, something about files not being found
< michagogo>
No, never mind
< michagogo>
Looks like those were errors while it was detecting what's available
< michagogo>
cfields: looks like the same bizarre log, too
< michagogo>
File not starting at the beginning even though I know it started properly from the tailf, and a ton of nulls
< michagogo>
Ending at "creating qmake"
< wangchun>
Lightsword: this channel ok?
< Lightsword>
sure
< Lightsword>
the issue with headers only mining is that poor propagation creates accidental selfish mining attacks
< Luke-Jr>
what? no, it's because you make invalid blocks O.o
< instagibbs>
i think it amplifies selfish mining once fees become larger fraction of reward
< Lightsword>
Luke-Jr, it’s antpool’s fault mainly they have really bad propagation on one of their nodes
< Lightsword>
Block 393554 in particular
< michagogo>
Luke-Jr: I don't suppose you have any idea what might be causing my OS X gitian build to fail catastrophically?
< michagogo>
The really weird thing is that somehow the build.log is breaking retroactively.
< michagogo>
Tailf-ing it, I see the depends building normally. I walk away while it's doing Qt, and then come back to find it failed, and then when I check the log file again it's a few weird lines, then a ton of null bytes, and then the log resumes at "creating qmake"...
< Luke-Jr>
michagogo: try less to view it maybe?
< Luke-Jr>
Shift-F in less acts as tail
< michagogo>
Luke-Jr: when I lessed it I got the "may be binary" warning
< michagogo>
And then when I said yes, it was what I just described
< michagogo>
A couple lines that were definitely not what should have been the beginning of the log, a whole lot of ^@, and then "creating qmake"