1 2017-09-08 03:32:12 <ossifrage> dviola, that error is exactly as it sounds, the other side of the connection hung up. Happens all the time (4965 times in 10 days on my node)
 2 2017-09-08 11:06:32 <jtfidje_> Hi. Quick question. How does this technology mitigate if "Bad guys" decide to flood miner network with millions of fake transactions?
 3 2017-09-08 11:33:53 <Emcy> quick rundown: fees
 4 2017-09-08 13:49:12 <ilkmccr> We have created our altcoin, genesis block for educational purposes, but we couldn't start the mining process. Because of internal miner has been removed from bitcoin, we can't mine. We have tried with cgminer, but because of cgminer asks getblocktemplate and gets response LEARNcoin is downloading blocks...
 5 2017-09-08 13:49:33 <ilkmccr> Could someone help me please ?
 6 2017-09-08 13:58:17 <r251d> ilkmccr: instead of making a new chain, just have your students use existing testnet chain to learn.
 7 2017-09-08 14:00:11 <ilkmccr> r251d: that does not help, could you please see my question again ?
 8 2017-09-08 14:01:42 <r251d> Nobody here is going to help you make a fork. Use testnet to learn, or please move your question to #bitcoin-forks
 9 2017-09-08 15:14:29 <stevenroose> Are block timestamps enforced to be incremental?
10 2017-09-08 15:16:38 <Chris_Stewart_5> stevenroose: Sort of. See BIP113 https://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki
11 2017-09-08 15:16:54 <Chris_Stewart_5> "The median of the last 11 blocks is used instead of the block's timestamp, ensuring that it increases monotonically with each block. "
12 2017-09-08 15:28:05 <stevenroose> "Since the consensus rules do not mandate strict ordering of block timestamps," so no
13 2017-09-08 15:28:06 <stevenroose> :p
14 2017-09-08 15:28:21 <stevenroose> That's kinda weird though
15 2017-09-08 15:28:38 <stevenroose> Could be softforked though
16 2017-09-08 15:37:34 <Chris_Stewart_5> stevenroose: I feel like if it was pratical they would have
17 2017-09-08 15:37:47 <Chris_Stewart_5> instead of doing this median past time thing
18 2017-09-08 19:54:27 <esotericnonsense> without a mechanism to push them back, timestamps would be pushed to the limit forwards
19 2017-09-08 20:06:30 <dviola> hi
20 2017-09-08 20:06:45 <dviola> I see this in the debug.log: warning='16 of last 100 blocks have unexpected version'
21 2017-09-08 20:06:47 <dviola> what does it mean?
22 2017-09-08 20:21:21 <dviola> my node has already finished syncing :)
23 2017-09-08 20:21:36 <dviola> I'm curious what that message means though
24 2017-09-08 20:22:38 <CryptAxe> dviola you can ignore that message, it means that miners have created blocks with an unknown version number
25 2017-09-08 20:22:48 <CryptAxe> That could be signalling for a incompatible softfork etc
26 2017-09-08 20:23:42 <dviola> I see, thanks
27 2017-09-08 20:24:15 <CryptAxe> No problem :) It's a scary message, maybe it should be more clear. You only saw it because you looked at the debug log though?
28 2017-09-08 20:24:37 <CryptAxe> I think if it is in the debug log it's okay to be a bit technical, but not if it is shown on the GUI
29 2017-09-08 20:24:59 <dviola> yeah, I didn't find it scary, just curious what it meant... I've been looking at the debug.log most of the time, with tail -f
30 2017-09-08 20:25:29 <dviola> yeah, it is ok
31 2017-09-08 20:25:32 <CryptAxe> Good practice, you'll actually learn a lot about Bitcoin just by following that file
32 2017-09-08 20:26:06 <dviola> I see, nice
33 2017-09-08 20:26:16 <dviola> 2017-09-06 12:31:18 socket recv error Connection reset by peer (104)
34 2017-09-08 20:26:17 <dviola> 2017-09-06 12:31:19 connect() to 193.25.7.64:8333 failed after select(): Connection refused (111)
35 2017-09-08 20:26:22 <dviola> those messages are normal too, right?
36 2017-09-08 20:26:41 <dviola> 2017-09-07 17:24:52 ProcessMessages(version, 113 bytes) FAILED peer=71
37 2017-09-08 20:28:39 <CryptAxe> Yeah it seems like the peer you were connected to went offline
38 2017-09-08 20:29:12 <dviola> I see
39 2017-09-08 20:29:54 <dviola> I'm surprised how light bitcoind is on resources, I'm using a 10 years old computer and I can't barely feel bitcoind is running (after the IBD sync is done)
40 2017-09-08 20:30:00 <dviola> many thanks
41 2017-09-08 20:31:02 <dviola> I've finished syncing today, after 7 days... was waiting for this day for a long time
42 2017-09-08 20:31:27 <CryptAxe> It is programmed in C++ by some very talented people (not me ;) ) so it runs great
43 2017-09-08 20:31:36 <CryptAxe> the initial block download is really the only bad part
44 2017-09-08 20:32:34 <dviola> I see, I actually felt that it wasn't too bad after I updated to 0.15.0-rc3, that really helped a lot :)
45 2017-09-08 20:32:49 <CryptAxe> And the core developers have REALLY improved IBD, I remember it taking significantly longer than it does now, even back when the blockchain was much smaller
46 2017-09-08 20:32:53 <dviola> I'll definitely do it again if I have to
47 2017-09-08 20:33:01 <CryptAxe> dviola yeah it keeps getting better.
48 2017-09-08 20:33:06 <dviola> neat
49 2017-09-08 20:33:08 <dviola> :)
50 2017-09-08 20:33:22 <CryptAxe> dviola I usually update my own node around once every 6 months or so, so it isn't on the newest version all the time
51 2017-09-08 20:33:29 <CryptAxe> that has worked out pretty well for me
52 2017-09-08 20:33:56 <CryptAxe> I really want to start running some fullnodes to support the network again
53 2017-09-08 20:34:09 <dviola> CryptAxe: cool
54 2017-09-08 20:35:13 <dviola> I'm from brazil and our internet connection isn't that great, so I'm surprised it only took me a week to sync given these constraints
55 2017-09-08 20:35:19 <dviola> I think most people use electrum here for those reasons
56 2017-09-08 20:35:30 <dviola> but I'm def moving to core after this, to use it as a wallet :)
57 2017-09-08 20:41:00 <CryptAxe> It's the best wallet because you are verifying everything yourself and not trusting anyone so good choice
58 2017-09-08 20:41:06 <CryptAxe> Just start it up and sync it every once in a while
59 2017-09-08 20:41:51 <dviola> yep :)