EDPoS Vote Guide

1. ready For EDPOS vote

NOTE:

1. BigBang Core use the CPoW + EDPoS consensus model, and there is no pre-excavation and pre-projection, it is necessary to dig out enough Token through the CPoW before Token can be used to vote

2. Download address of executable program (please select the latest version):

https://github.com/bigbangcore/BigBang/releases  

3. In the windows operating system,when executing the program in your current directory, please change the ". /bigbang" command to "bigbang". Same below.

2. Run the executable program to generate two groups of standby keys

NOTE:

1. Use to create DPOS template and Wallet

2. Use the command "bigbang makekeypair" to generate two groups of public-private key pairs, and use the command "bigbang getpubkeyaddress $pubkey" to obtain the public key address

First key pairs (for spending):
{
    "privkey" : "e7382046309d5a623bd87a75b666b088f53b8f86fa87a27d1aaafb5b174ca9f1",
    "pubkey" : "8e0594f219d5ffa30cc938fa9c26c76e0bfa3655fe91b67ee1b1891bee5dbb7f",
    "pubkeyaddress" : "1fyxnvvgvh6ry2znpj7z5adqt1dqce9mwz8wcj353zzahkwmm0p74y0t4"
}

Second key pairs (for mining):
{
    "privkey" : "57bdb88a874facd3c1e5dada6b6ce4d7d271a101236523b9f0fd314576c96b4d",
    "pubkey" : "928aa9ac6e67b094024ca2a59a228eb6fd45a26bc3ee02d53b7689903f6a7941"
}

3. Modify the configuration file (.bigbang/bigbang.conf)

# Start P2P listening (IPv4)
listen4   

connect=18.182.192.156:9955(Test Net)
connect=112.126.60.134:19901(Test Net)

# Public key address for DPOS(spending address/wallet address)
mpvssaddress=1fyxnvvgvh6ry2znpj7z5adqt1dqce9mwz8wcj353zzahkwmm0p74y0t4

# Private key for DPOS(Private key for signing)
mpvsskey=57bdb88a874facd3c1e5dada6b6ce4d7d271a101236523b9f0fd314576c96b4d

NOTE:

If multiple DPOS nodes are configured on the same host,the port and rpcport parameters of each node should be different.

4. After the configuration is completed, restart the program, and the data starts to be synchronized automatically

command: bigbang -daemon -debug

5. Import DPOS mining template into Wallet

command:
bigbang addnewtemplate delegate '{"delegate": "Public key for signing", "owner": "spending address/wallet address"}'

example:
bigbang addnewtemplate delegate '{"delegate": "928aa9ac6e67b094024ca2a59a228eb6fd45a26bc3ee02d53b7689903f6a7941", "owner": "1fyxnvvgvh6ry2znpj7z5adqt1dqce9mwz8wcj353zzahkwmm0p74y0t4"}'
20m0bk8tjwt73gtjb4jv8r6sa04fe22r3ns2era8zbnn20qfv8sz38vg6 //template address

6. Vote

NOTE: EDPoS voting consists of voting by oneself and voting by other address

6.1 Voting by the DPoS template address owner

command:
bigbang sendfrom <DPoS spending address>  <DPOS template address>  <$TOKEN>

example:
bigbang sendfrom 1fyxnvvgvh6ry2znpj7z5adqt1dqce9mwz8wcj353zzahkwmm0p74y0t4 20m0bk8tjwt73gtjb4jv8r6sa04fe22r3ns2era8zbnn20qfv8sz38vg6 1000

6.2 Voting for others

NOTE: You need to generate a vote template address to be voted for based on the other's EDPoS template address and your wallet address,and then vote for the newly generated vote address.This voting method is redeemable. Direct voting for DPOS mining template addresses is non-redeemable.

1) Generate a vote template address
command:
bigbang addnewtemplate vote '{"delegate": "The other's DPOS template address", "owner": "Your spending address/Your wallet address"}'

example:
bigbang addnewtemplate vote '{"delegate": "20m0bk8tjwt73gtjb4jv8r6sa04fe22r3ns2era8zbnn20qfv8sz38vg6", "owner": "1tefq9nem7mdkr14gx3man2sr1bvvvfhey0evvctp3tdj6r4d279sr9p7"}'
--- 20w0629r20911rwy0mfkqmcp8qqsghp1m4v8e3998s04xmcd6qb1dj9er  --- vote address

2) Voting
command:
bigbang sendfrom {$Your spending address/Your wallet address} {$vote address} {$amount}

example:
bigbang sendfrom 1tefq9nem7mdkr14gx3man2sr1bvvvfhey0evvctp3tdj6r4d279sr9p7  20w0629r20911rwy0mfkqmcp8qqsghp1m4v8e3998s04xmcd6qb1dj9er 1000

6.3 Voting for others (No need to import the voice template address)

NOTE: Because the whole chain of transactions needs to be loaded when importing the voice template address, it takes time. If you do not need to import the voice template address, you can use the following methods:

1) Generate a vote template address
command:
bigbang maketemplate vote '{"delegate": "The other's DPOS template address", "owner": "Your spending address/Your wallet address"}'

example:
bigbang maketemplate vote '{"delegate": "20m0bk8tjwt73gtjb4jv8r6sa04fe22r3ns2era8zbnn20qfv8sz38vg6", "owner": "1tefq9nem7mdkr14gx3man2sr1bvvvfhey0evvctp3tdj6r4d279sr9p7"}'
--- "address" : "20w0629r20911rwy0mfkqmcp8qqsghp1m4v8e3998s04xmcd6qb1dj9er", --- This is the address of the vote template. Transfer to this address to vote;
---"hex" : "0700020500b9a352e68e386a4b24b68c1b2a011ee10b03ae44ec291f5d6a205dfb467e01d39f74d5d43d1b3c0490e8e8aa8b380af7bdbe2ef01dbdb3561e9b23608d11d3"    ---This is the data of the address of the voice template, which is used for the - TD parameter in the sendfromcommand;

2) Voting
command:
bigbang sendfrom {$Your spending address/Your wallet address} {$vote address} {$amount} -td={template address data}

NOTE: -td=This parameter is the hex data generated by the maketemplate command, that is, the template address data;

example:
bigbang sendfrom 1tefq9nem7mdkr14gx3man2sr1bvvvfhey0evvctp3tdj6r4d279sr9p7  20w0629r20911rwy0mfkqmcp8qqsghp1m4v8e3998s04xmcd6qb1dj9er 1000 -td=0700020500b9a352e68e386a4b24b68c1b2a011ee10b03ae44ec291f5d6a205dfb467e01d39f74d5d43d1b3c0490e8e8aa8b380af7bdbe2ef01dbdb3561e9b23608d11d3

7. Clients who voted cancel the vote and retrieve token

NOTE: Redemption can only be done by the voting address and the corresponding wallet needs to be unlocked

command: 
bigbang sendfrom {$vote address} {$Your spending address/Your wallet address} {$amount} 1

example：
bigbang sendfrom 20w0629r20911rwy0mfkqmcp8qqsghp1m4v8e3998s04xmcd6qb1dj9er  1tefq9nem7mdkr14gx3man2sr1bvvvfhey0evvctp3tdj6r4d279sr9p7 1000 1

NOTE:

1) The node needs to configure dpos mining parameters,**"mpvssaddress"** and **"mpvsskey"**. For security, these two parameters should come from different key pairs.  

2) There are two ways to vote, vote for oneself and vote for others. The template for accepting the vote is two different templates.  

3) The number of tokens transferred in determines the weight of the address. The ratio of the number of tokens owned by the template address to the total number of tokens is the weight. If the weight is larger, the probability of the address generates block is higher. If the weight is small, the probability of the address generates block is lower.  

4) The total number of tokens issued by BigBang is called **“Total Tokens"**, which increases with the increase of block height. We can calculate the total number of tokens at a certain block height according to the release rules of token.
  

Q&A

1) What is the height of the pow generates block reached can the DPOS start to generate block? What principle is this based on?    
A:In the initial stage, blocks are generated in POW mode. After that, if the DPOS miner gets the vote, DPOS will have the opportunity to generate the block. However, whether DPOS blocks are generated depends on POW, voting, and the random number of the whole network. In the first phase, the height is hard coded into the program. When the current height is lower than this height, POW blocks will be generated. When the current height is higher than this height, whether POW blocks or DPOS blocks are determined by voting and random number.

2) How many tickets do DPOS node needs to get to get the right of block generate?  
A: DPOS nodes need to obtain at least 2% of the total number of token to have the chance to participate in DPOS out block node competition. Finally, according to the voting situation, select the top 23 nodes to participate in the random number selection. As for how many votes need to be obtained in order to get the block right, it needs to be determined according to the voting situation of the whole network. The more votes a node gets, the higher the chance to get the block right.

3) What is the relationship between permissions and weights for DPOS generates block?  
A:The weight of DPOS node is calculated by taking the number of token and the total number of token obtained by the node as parameters. The more votes the node gets, the higher the weight and the higher the chance to get the block weight.

4) Why do we need two groups of keys when adding mining templates?  
A: when adding a mining template, two parameters need to be added. One is the private key used for mining, which is used for the signature of blocks generate. The other is the token spending address. Only when you have the private key of the address, you can spend the token owned by the mining template address. For security reasons, the two groups of keys cannot be the same. The mining private key needs to be saved in the mining node and may be disclosed, so this private key is not secure. The other parameter is the spend address, which does not need to give the private key. As long as the private key is saved, the token in the template address is secure. Therefore, in our BigBang system, using two groups of key pairs can improve the security.