1 2018-02-28 07:21:59 <FraJah> moinings
2 2018-02-28 07:44:53 <rav3nn> I have a btc node inside docker deployed, got properly mounted volume. But after restart is syncing from the beginning. What I'm doing wrong ?
3 2018-02-28 07:48:39 <eklitzke> have you tried looking at the log files
4 2018-02-28 07:50:15 <rav3nn> yep, got enabled txindex, reindex ... and got reindexing in logs from files
5 2018-02-28 07:56:12 <eklitzke> it sounds like to me you have either -reindex in the command line, or reindex=1 in the bitcoinf.conf file
6 2018-02-28 07:58:33 <luke-jr> or docker resets the data
7 2018-02-28 07:58:47 <rav3nn> I got both of them
8 2018-02-28 07:58:53 <rav3nn> is it bad ?
9 2018-02-28 07:59:34 <rav3nn> it reindexing mounted files and old data exist there, so docker dont remove it
10 2018-02-28 07:59:59 <luke-jr> rav3nn: it does what it says
11 2018-02-28 08:00:06 <luke-jr> reindex = start from the beginning
12 2018-02-28 08:02:15 <rav3nn> ok... so I missed something
13 2018-02-28 08:05:36 <rav3nn> -reindex Rebuild chain state and block index from the blk*.dat files on disk
14 2018-02-28 09:09:44 <CubicEarths>
15 2018-02-28 09:09:44 <CubicEarths>
16 2018-02-28 09:09:44 <CubicEarths>
17 2018-02-28 09:09:46 <CubicEarths>
18 2018-02-28 09:09:48 <CubicEarths>
19 2018-02-28 09:09:50 <CubicEarths>
20 2018-02-28 09:09:52 <CubicEarths>
21 2018-02-28 09:09:54 <CubicEarths>
22 2018-02-28 09:09:56 <CubicEarths>
23 2018-02-28 09:09:58 <CubicEarths>
24 2018-02-28 09:10:00 <CubicEarths>
25 2018-02-28 09:10:02 <CubicEarths>
26 2018-02-28 09:10:04 <CubicEarths>
27 2018-02-28 09:10:06 <CubicEarths>
28 2018-02-28 09:10:08 <CubicEarths>
29 2018-02-28 09:10:10 <CubicEarths>
30 2018-02-28 09:10:12 <CubicEarths>
31 2018-02-28 09:10:14 <CubicEarths>
32 2018-02-28 09:10:16 <CubicEarths>
33 2018-02-28 09:10:18 <CubicEarths>
34 2018-02-28 09:10:20 <CubicEarths>
35 2018-02-28 09:10:22 <CubicEarths>
36 2018-02-28 09:10:24 <CubicEarths>
37 2018-02-28 09:10:26 <CubicEarths>
38 2018-02-28 09:10:28 <CubicEarths>
39 2018-02-28 09:10:30 <CubicEarths>
40 2018-02-28 09:10:32 <CubicEarths>
41 2018-02-28 09:10:34 <CubicEarths>
42 2018-02-28 09:10:36 <CubicEarths>
43 2018-02-28 09:10:38 <CubicEarths>
44 2018-02-28 09:10:40 <CubicEarths>
45 2018-02-28 09:10:40 <dongcarl> Am I the only one seeing this?
46 2018-02-28 09:10:42 <CubicEarths>
47 2018-02-28 09:10:44 <CubicEarths>
48 2018-02-28 09:10:46 <CubicEarths>
49 2018-02-28 09:10:48 <CubicEarths>
50 2018-02-28 09:10:50 <CubicEarths>
51 2018-02-28 09:10:52 <CubicEarths>
52 2018-02-28 09:10:53 <FraJah> !kb CubicEarths
53 2018-02-28 09:10:53 <gribble> Error: "kb" is not a valid command.
54 2018-02-28 09:10:54 <CubicEarths> Shit
55 2018-02-28 09:10:59 <CubicEarths> No. Sorry
56 2018-02-28 09:11:00 <FraJah> !ban CubicEarths
57 2018-02-28 09:11:00 <gribble> Error: "ban" is not a valid command.
58 2018-02-28 09:11:03 <FraJah> grrr
59 2018-02-28 09:13:04 <CubicEarths> So when a block is solved, is it true that the hash value itself isn't transmitted? The miner just sends the block, and everyone can compute the hash for themselves?
60 2018-02-28 09:19:12 <CubicEarths> I had just always visualized the miner proudly broadcasting the block + hash, but looking at the header strucutre, I am seeing there is no room for the current hash...
61 2018-02-28 09:19:16 <CubicEarths> I feel silly
62 2018-02-28 09:23:44 <mmgen> CubicEarths: yes, the hash is not included; each node calculates it itself
63 2018-02-28 09:25:32 <CubicEarths> well, that makes bitcoin just a little bit cooler than I always thought it was
64 2018-02-28 09:26:52 <mmgen> mmgen: the header must be kept as small as possible; including the hash just wastes space
65 2018-02-28 09:27:07 <CubicEarths> of course!
66 2018-02-28 09:27:28 <mmgen> CubicEarths: that's why the nonce is only 4 bytes, for example
67 2018-02-28 09:28:19 <mmgen> CubicEarths: even though that complicates things for miners a bit
68 2018-02-28 09:28:31 <CubicEarths> mmgen: yeah. I know other parts are varied since the nonce isn't big enough
69 2018-02-28 22:14:35 <FraJah> nite nite ^_^