1 2017-07-16 15:17:08 <molz> mmgen, how do you set the block version to signal for bit 1?
 2 2017-07-16 15:28:34 <mmgen> molz: with the -blockversion switch
 3 2017-07-16 15:28:51 <mmgen> molz: you have to use an integer, not hex
 4 2017-07-16 15:29:13 <mmgen> molz: works only in regtest mode of course
 5 2017-07-16 15:30:07 <molz> mmgen, so you run the client with -blockversion=1 ?
 6 2017-07-16 15:30:25 <molz> sorry i have no clue, but i'm curious
 7 2017-07-16 15:33:29 <mmgen> molz: no, versionbits is a bit map. 0x20000002 is signaling on bit 1. Use the integer value of that
 8 2017-07-16 15:35:19 <mmgen> molz: versionbits is described in BIP9
 9 2017-07-16 15:35:41 <molz> right, what i'm trying to understand is how do you set the bit in regtest
10 2017-07-16 15:37:29 <molz> mmgen, how did you do this: "<mmgen> I first set the block version to signal for bit 1"
11 2017-07-16 15:37:53 <mmgen> I just told you how
12 2017-07-16 15:38:11 <mmgen> convert that hex value to an int and use that as your argument
13 2017-07-16 15:38:47 <molz> ok thanks, i'll have to ask someone else, sorry i'm such a noob
14 2017-07-16 16:11:36 <mmgen> molz: since no one's stepped up to the plate, looks like I'll have to spell it out for you:
15 2017-07-16 16:11:54 <molz> mmgen, i got it, thanks :)
16 2017-07-16 16:11:59 <molz> i'm doing it now
17 2017-07-16 16:12:13 <mmgen> Figured it out?
18 2017-07-16 16:12:47 <mmgen> Run the client with -blockversion=<integer value of the hex I gave you>
19 2017-07-16 16:13:03 <mmgen> You can convert the hex using Python
20 2017-07-16 16:17:16 <molz> so at the beginning i got "defined", and after mining 144 blocks i got "started"
21 2017-07-16 16:18:27 <molz> how many blocks does it take to get "lock-in"?
22 2017-07-16 16:19:06 <arubi> I /think/ that by block 421 it should activate
23 2017-07-16 16:19:50 <arubi> I didn't think bip9 was active on regtest right from the beginning
24 2017-07-16 16:19:50 <arubi> unless this signal from block 1 makes a difference, not sure
25 2017-07-16 16:22:34 <molz> arubi it doesn't
26 2017-07-16 16:23:31 <molz> im thinking 2016 blocks
27 2017-07-16 16:25:28 <molz> oh hm just mined 144 blocks again and segwit got 'lock-in'
28 2017-07-16 16:25:56 <arubi> bip9_softforks": {
29 2017-07-16 16:25:56 <arubi> "csv": {
30 2017-07-16 16:25:56 <arubi> molz, 432
31 2017-07-16 16:25:56 <arubi> "status": "active",
32 2017-07-16 16:25:57 <arubi> "startTime": 0,
33 2017-07-16 16:25:57 <arubi> "timeout": 999999999999,
34 2017-07-16 16:25:58 <arubi> },
35 2017-07-16 16:25:58 <arubi> "since": 432
36 2017-07-16 16:25:59 <arubi> "segwit": {
37 2017-07-16 16:25:59 <arubi> "status": "active",
38 2017-07-16 16:26:00 <arubi> "startTime": 0,
39 2017-07-16 16:26:01 <arubi> "timeout": 999999999999,
40 2017-07-16 16:26:03 <arubi> "since": 432
41 2017-07-16 16:36:45 <mmgen> You're right, it becomes active automatically around block 500
42 2017-07-16 16:36:51 <mmgen> No signaling is required
43 2017-07-16 16:38:26 <mmgen> s/500/432/
44 2017-07-16 16:39:59 <mmgen> That's too easy, in my opinion
45 2017-07-16 16:42:12 <arubi> you can set it with -bip9params=deployment:start:end
46 2017-07-16 16:42:47 <mmgen> arubi: ok
47 2017-07-16 16:43:02 <mmgen> Yes, the client is signaling on its own:
48 2017-07-16 16:43:19 <mmgen> UpdateTip: new best=5b29f39f47b89315f00b51f729c732a51c0d45409875b9bfbbc27eef5f24c570 height=300 version=0x30000003
49 2017-07-16 16:43:36 <mmgen> for csv and segwit
50 2017-07-16 16:44:03 <mmgen> but why 0x30?
51 2017-07-16 16:44:14 <arubi> it should, like it does on mainnet
52 2017-07-16 16:45:15 <arubi> not sure really.  pretty weird
53 2017-07-16 16:49:07 <mmgen> s/432/431/
54 2017-07-16 16:49:19 <arubi> mine say UpdateTip: new best=377c7964bc3c939e7e39ea6a2082917651b3bfd5cfb32ccdfa3ac7bb507a4591 height=438 version=0x20000000 log2_work=9.7780771 tx=439 date='16 20' progress=1.000000 cache=0.1MiB(438tx)
55 2017-07-16 16:49:27 <arubi> and version=0x20000004 when the MAST client generates
56 2017-07-16 16:50:29 <mmgen> UpdateTip: new best=001f59da4e7f2ece7301cec69cd8d443c7b4de803f6435448e7a0582d31d4061 height=431 version=0x30000003
57 2017-07-16 16:50:44 <mmgen> UpdateTip: new best=2af894f9a2d7bb7072bbb5ccbf239f7bbcefc66c0666453df4f7e31c780d6d11 height=432 version=0x20000000
58 2017-07-16 16:51:18 <mmgen> It stops signaling right after activation
59 2017-07-16 16:51:21 <arubi> which version is that?
60 2017-07-16 16:51:29 <mmgen> 0.14.1
61 2017-07-16 16:51:39 <arubi> ohh I think it signals for both csv and segwit at the same time
62 2017-07-16 16:52:17 <mmgen> Yes, hence the version=0x30000003
63 2017-07-16 16:53:01 <mmgen> that's bits 1 and 2
64 2017-07-16 16:53:12 <mmgen> counting from zero
65 2017-07-16 16:53:23 <arubi> right, I forgot csv is activated at the same time and only expected to see segwit's signal at bit 1
66 2017-07-16 16:53:30 <arubi> yes
67 2017-07-16 16:53:43 <arubi> hence I now realize csv is probably on bit 2 :)
68 2017-07-16 16:55:23 <mmgen> s/is/was/
69 2017-07-16 16:55:25 <arubi> now what's bip 9's 011 on MSB means
70 2017-07-16 16:56:38 <mmgen> good question. we don't see that on mainnet
71 2017-07-16 16:59:29 <arubi> so I guess bit 27 is what we see on mainnet and bit 28 is the testdummy bit
72 2017-07-16 17:00:30 <arubi> consensus.BIP66Height = 1251; // BIP66 activated on regtest (Used in rpc activation tests)
73 2017-07-16 17:00:30 <arubi> oof: consensus.BIP65Height = 1351; // BIP65 activated on regtest (Used in rpc activation tests)
74 2017-07-16 17:00:31 <arubi> I did not know these were so far off bip9 activations
75 2017-07-16 17:02:32 <arubi> yep, it actually takes so many :)