Post
Topic
Board Announcements (Altcoins)
Re: ★★DigiByte|极特币★★[DGB]✔ DigiSync v6.14.2 - DigiSpeed - Segwit -DiguSign
by
M8BWNNRFMNdak68c
on 13/04/2017, 14:39:30 UTC
For those with questions about DigiByte v6.14.2 DigiSync + SegWit please read: https://digibyte.co/why-we-support-segwit-digibyte

Thanks for the blog post!

@M8BWNNRFMNdak68c
Nice! Do you run a pool or solo mine?

Well SegWit is being rolled out with a softfork (BIP9: https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki)
Which means there is a flag in the version (32 bits):
https://github.com/digibyte/digibyte/blob/6.14.2/src/chainparams.cpp#L159

Hope it helps?
ok that you! so i learned:

we take the version number ( as integer ) and convert it to binary number
536899586 ->  0010 0000 0000 0000 0111 0000 0000 0010
( some explorers print it hexadecimal: -> 20007002 )

we interpret this as a bitmask and give them numbers ( from left "B31" to "B0" on right side )
per definition is given  ( https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki#bit-flags )
B31 = 0
B30 = 0
B29 = 1

then we compare the other bits with the definition ( https://github.com/digibyte/digibyte/blob/6.14.2/src/chainparams.cpp#L154 ) and see :

B12 = 1 = DEPLOYMENT_CSV
B13 = 1 = DEPLOYMENT_SEGWIT
B14 = 1 = DEPLOYMENT_NVERSIONBIPS

so all three proposals are successfully voted for. addiitionally, there are bits for POW algorithm description:

scrypt 
0010 0000 0000 0000 0111 0000 0000 0010
sha256
0010 0000 0000 0000 0111 0010 0000 0010
skein
0010 0000 0000 0000 0111 0110 0000 0010
qubit
0010 0000 0000 0000 0111 1000 0000 0010
myr
0010 0000 0000 0000 0111 0100 0000 0010

now we only have to think about
B1 = 1
so a block is always "Version 2" ? ( in comparison to an earlier version 1 )