1 2018-01-02 03:29:06 <xiedeacc> hi, output of block 0 can't be spent as this would allow Satoshi to fork the network. how could this happen ? because at first bitcoin released by Satoshi, the coinbase of block 0 cannot spendable, so if some client allow that address spend, then Satoshi can fork a new blockchain from block 0, and mine his own blockchain more longer than legal blockchain in a private way, then satoshi publish  his blockchain, made legal blcokchain cancelled?
 2 2018-01-02 04:11:17 <achow101> xiedeacc: it would be a hard fork and be completely backwards incompatible. to allow people to use older software, that output cannot be allowed to be spent from
 3 2018-01-02 04:11:33 <achow101> there is no blockchain wipeout risk. rather it is a hard fork risk
 4 2018-01-02 11:44:53 <bsdnoob> hey
 5 2018-01-02 11:45:03 <bsdnoob> can anyone help me create the genesis block?
 6 2018-01-02 12:14:51 <fluffypony> hello frenz
 7 2018-01-02 12:15:50 <fluffypony> I'm confused about the order in which inv / tx messages are sent
 8 2018-01-02 12:16:15 <fluffypony> if a node is first to broadcast a tx, it uses inv to let its peers know it has new data for them, right?
 9 2018-01-02 12:16:22 <fluffypony> because tx is only in reply to getdata?
10 2018-01-02 13:01:52 <echeveria> fluffypony: yes.
11 2018-01-02 13:02:46 <fluffypony> kk tks
12 2018-01-02 13:03:40 <echeveria> fluffypony: eventually it should probably be a protocol violation to send an unsolicited transaction message, but it's not today, though I think in debug mode it had a message about it. there's a couple of wallets that do it, and some insane software doing the same.
13 2018-01-02 13:05:04 <fluffypony> echeveria: so tx propagation through periodic requests from peers instead of broadcasting them out?
14 2018-01-02 13:06:46 <echeveria> fluffypony: that's something different. the protocol is that you send an inv for things you learn about, and the node responds with a getdata if it needs it, and you send that data in response.
15 2018-01-02 13:07:03 <fluffypony> ahhhh
16 2018-01-02 13:07:04 <fluffypony> ok
17 2018-01-02 13:07:22 <echeveria> bitcoin nodes today do transaction batching, where they will selectively delay or bundle up transaction inventory messages in an attempt to improve privacy.
18 2018-01-02 13:08:36 <echeveria> https://github.com/laanwj/bitcoin-submittx/
19 2018-01-02 13:08:55 <echeveria> this is a tool which implements the bare minimum logic needed to connect to a node, handshake, send inventory, and reply with a given transaction.
20 2018-01-02 13:09:15 <fluffypony> perfect, tks
21 2018-01-02 13:10:55 <echeveria> what do you mean by broadcast backbone?
22 2018-01-02 13:14:12 <fluffypony> echeveria: if a bunch of currencies shared a tx broadcast backbone that would be beneficial from a privacy perspective
23 2018-01-02 13:14:34 <echeveria> why?
24 2018-01-02 13:15:37 <fluffypony> BlueMatt can explain a bit more when he's around
25 2018-01-02 13:15:45 <fluffypony> got to go get food
26 2018-01-02 13:32:08 <bsdnoob> does anyone knows how to print a merkle root?
27 2018-01-02 13:33:57 <iwkse> bsdnoob: do you mean the merkle tree?
28 2018-01-02 13:34:20 <iwkse> the merkle root is written in any blocks you can easily get it
29 2018-01-02 13:34:22 <bsdnoob> iwkse, each block stores merkle root right?
30 2018-01-02 13:34:25 <iwkse> yes
31 2018-01-02 13:34:37 <bsdnoob> iwkse, I am creating my own genesis block
32 2018-01-02 13:34:37 <iwkse> blocks/blocks header
33 2018-01-02 13:34:46 <bsdnoob> and assertion fails
34 2018-01-02 13:35:49 <iwkse> I'm afraid I cannot help much with that, just jumped into that these days, but if you just want to print the merkle root, well I think you can get it from the block's header
35 2018-01-02 13:36:30 <bsdnoob> iwkse, it's in weird uint256 format
36 2018-01-02 13:36:54 <iwkse> bsdnoob: why weird?
37 2018-01-02 13:37:00 <bsdnoob> iwkse, but fear not I think it got ToString() method
38 2018-01-02 13:37:09 <bsdnoob> iwkse, first time I am seeing that type
39 2018-01-02 13:38:07 <iwkse> well the merkle root is an hash
40 2018-01-02 13:38:33 <bsdnoob> yupp
41 2018-01-02 13:38:38 <iwkse> was just checking if I can get that from bitcoin-cli
42 2018-01-02 13:38:41 <iwkse> I think it's possible
43 2018-01-02 13:40:00 <iwkse> yup
44 2018-01-02 13:40:05 <iwkse> with getblockheader
45 2018-01-02 13:40:14 <iwkse> you give the block hash and you get it all
46 2018-01-02 13:40:28 <bsdnoob> iwkse, yup got it
47 2018-01-02 13:40:38 <bsdnoob> but I ran into other problem
48 2018-01-02 13:40:48 <bsdnoob> bitcoind is crashing
49 2018-01-02 13:40:50 <bsdnoob> ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=8)
50 2018-01-02 13:41:51 <iwkse> guessing, maybe something wrong with the nonce
51 2018-01-02 13:42:02 <bsdnoob> maybe this is because I messed with hash?
52 2018-01-02 13:43:09 <iwkse> I'm not sure
53 2018-01-02 13:44:20 <bsdnoob> what does checkpoints do?
54 2018-01-02 13:46:07 <iwkse> it's something hardcoded in the client to accept transactions as valid till that point