#Vote & Unvote Transaction

A key feature of the ARK DPoS model is that each address can vote for one validator of their choosing to secure the network. A vote and unvote transaction type is therefore necessary to enable this functionality. Once an address votes for a validator, funds can enter and leave the address as needed, and vote weight adjusts automatically. Voting does not send funds to the validators’s ARK address in question - it only assigns vote weight

Holders of ARK vote through their wallets for validators who secure the network, insert blocks into the ledger, and create new ARK. The top 51 vote earners are named elected forging validators. Number of validators is related to DPOS mechanism configuration .

#Single Vote Structure

A single-vote transaction is structured and works identically in Core v3 as it did in Core v2.

In the following example, we can see the first transaction from this wallet (03415...ed192) is a Vote for the publicKey 02511...36f34.

#Signed JSON Payload

 1{
 2    "version": 3,
 3    "network": 23,
 4    "type": 3,
 5    "nonce": "1",
 6    "senderPublicKey": "034151a3ec46b5670a682b0a63394f863587d1bc97483b1b6c70eb58e7f0aed192",
 7    "fee": "100000000",
 8    "amount": "0",
 9    "asset": {
10        "votes": [
11            "+02511f16ffb7b7e9afc12f04f317a11d9644e4be9eb5a5f64673946ad0f6336f34"
12        ]
13    },
14    "signature": "582aa4650868c162516f4b2a2d872970483f5b9577014a831a6320dea3c01d5063618b5d857634497bb7683f1787e7fbb9826301066ef1cc680996acde457a03",
15    "id": "72276571deef993f297d2f4e39985d425c40dac7f5dc9dd6a268423cb105ee11"
16}

#Serialized Payload

1ff03170100000003000100000000000000034151a3ec46b5670a682b0a63394f863587d1bc97483b1b6c70eb58e7f0aed19200e1f5050000000000010102511f16ffb7b7e9afc12f04f317a11d9644e4be9eb5a5f64673946ad0f6336f34582aa4650868c162516f4b2a2d872970483f5b9577014a831a6320dea3c01d5063618b5d857634497bb7683f1787e7fbb9826301066ef1cc680996acde457a03

#Deserialized Hex Payload

#Multi-Vote Structure

A multi-vote transaction is exclusive to Core v3 and allows up 2 different votes (Vote/Unvote) to be combined into a single transaction.

key facts:

• A Multi-vote contains a max of 2 Votes.
  • A single vote is still permitted.
• Votes must not be duplicated.
  • They must be either [Vote, Unvote] or [Unvote, Vote].
  • It would not make sense to Vote–or Unvote–twice in the same transaction.
• Votes must be ordered.
  • It would not make sense to Vote THEN Unvote from a wallet that has already voted.
  • It would not make sense to Unvote THEN Vote from a wallet that has not already voted.

In the following example, we can see this wallet’s 2nd transaction is an Unvote for the publicKey 02511...36f34, and a subsequent Vote for the publicKey 0259d...cfe79.

#Signed JSON Payload

 1{
 2    "version": 3,
 3    "network": 23,
 4    "type": 3,
 5    "nonce": "2",
 6    "senderPublicKey": "034151a3ec46b5670a682b0a63394f863587d1bc97483b1b6c70eb58e7f0aed192",
 7    "fee": "100000000",
 8    "amount": "0",
 9    "asset": {
10        "votes": [
11            "-02511f16ffb7b7e9afc12f04f317a11d9644e4be9eb5a5f64673946ad0f6336f34"
12            "+0259d9ca7922c277b0e7407a88703bbb98f5da43a335b0eefa6c4642f072acfe79"
13        ]
14    },
15    "signature": "51b77240bc639e6bcbe08510e0f71a77b029faa67ea60d7c7208963a00e155cafae06e35513db0b6bea1d16c4e19f36fe15fba03fbf59e2b556edf6923e06114",
16    "id": "f1f2c81d42acf9da186c180c7c4c3646f8d60c2814e151ec216b960f58a9bfa7"
17}

#Serialized Payload

1ff03170100000003000200000000000000034151a3ec46b5670a682b0a63394f863587d1bc97483b1b6c70eb58e7f0aed19200e1f5050000000000020002511f16ffb7b7e9afc12f04f317a11d9644e4be9eb5a5f64673946ad0f6336f34010259d9ca7922c277b0e7407a88703bbb98f5da43a335b0eefa6c4642f072acfe7951b77240bc639e6bcbe08510e0f71a77b029faa67ea60d7c7208963a00e155cafae06e35513db0b6bea1d16c4e19f36fe15fba03fbf59e2b556edf6923e06114

#Deserialized Hex Payload