add batch transfer doc (#82)

Author: b00f

.gitignore

@@ -4,3 +4,5 @@ public/
 resources
 *.lock
 hugo_stats.json
+
+TODO

content/get-started/become-a-validator.md

@@ -20,9 +20,9 @@ By staking their own coins, validators contribute to the network's security and
 ## Validator Rewards
 
 When a validator successfully proposes a block that is accepted by the network,
-they receive a block reward in the form of one coin.
+they receive a block reward.
 This reward serves as an [incentive](/protocol/blockchain/incentive)
-for validators to continue supporting the network.
+for validators to continue supporting the network while ensuring the long-term sustainability of the Pactus ecosystem.
 
 ## Minimum requirement
 

content/protocol/transaction/batch_transfer.md

@@ -0,0 +1,34 @@
+---
+title: Batch Transfer Transaction
+weight: 8
+math: false
+---
+
+Batch transfer transaction is used to transfer coins to multiple recipients in a single transaction.
+This is more efficient than creating multiple individual transfer transactions.
+It follows a one-to-many pattern, allowing a single sender to transfer coins to multiple recipients in one transaction.
+
+If any receiver account does not exist, it will be created automatically.
+
+The [Payload Type](/protocol/transaction/format/#payload-type) for Batch Transfer is 6.
+
+## Payload Structure
+
+The batch transfer transaction has a payload that consists of the following fields:
+
+| Field                | Size     |
+| -------------------- | -------- |
+| Sender address       | 21 bytes |
+| Number of Recipients | Variant  |
+| Recipients Address 1 | 21 bytes |
+| Recipients Amount 1  | Variant  |
+| ...                  | ...      |
+| Recipients Address N | 21 bytes |
+| Recipients Amount N  | Variant  |
+
+- **Sender address** is the account address that transfers the amounts
+- **Number of Recipients** specifies how many recipients will receive funds in this transaction (maximum 8 recipients)
+- **Recipients Address 1 to N** are the account addresses that receive the amounts
+- **Recipients Amount 1 to N** are the amounts of coins that should be transferred to each corresponding recipient
+
+The payload structure allows for up to 8 recipients, with each recipient having a corresponding address and amount pair.

content/protocol/transaction/bond.md

@@ -13,6 +13,8 @@ This is called the "bond interval" and is defined in the
 Validators within the committee cannot increase their stake.
 Therefore, bond transactions will be processed only when the validators are not in the committee.
 
+The [Payload Type](/protocol/transaction/format/#payload-type) for Bond is 2.
+
 ## Payload Structure
 
 The bond transaction has a payload consists the following fields:

content/protocol/transaction/format.md

@@ -15,8 +15,8 @@ Transactions in the Pactus consist of the following fields:
 | Memo         | Variant  |
 | Payload Type | 1 byte   |
 | Payload Data | Variant  |
-| Signature    | 48 bytes |
-| Public Key   | 96 bytes |
+| Signature    | Variant  |
+| Public Key   | Variant  |
 
 - **Flags** A flag is a bitfield that indicates how to decode the transaction data.
 - **Version** is the version of the transaction format. Different versions may have different fields or
@@ -48,11 +48,13 @@ The following are the supported transactions in the Pactus blockchain:
 3. [Sortition transaction](/protocol/transaction/sortition)
 4. [Unbond transaction](/protocol/transaction/unbond)
 5. [Withdraw transaction](/protocol/transaction/withdraw)
+6. [Batch Transfer transaction](/protocol/transaction/batch_transfer)
 
 ## Flags
 
-- **0x1** Indicates that the [public key is known](https://pips.pactus.org/PIPs/pip-4)
+- **0x01** Indicates that the [public key is known](https://pips.pactus.org/PIPs/pip-4)
   and excluded from the transaction.
+- **0x02** Indicates that the transaction is not signed yet.
 
 ## Transaction ID
 

content/protocol/transaction/sortition.md

@@ -11,6 +11,8 @@ Sortition transactions are valid for 7 blocks, which is defined as "sortition in
 [consensus parameters](/protocol/consensus/parameters/).
 Sortition is free. This means there are no fees associated with the process of sortition transaction.
 
+The [Payload Type](/protocol/transaction/format/#payload-type) for Sortition is 3.
+
 ## Payload Structure
 
 The sortition transaction has a payload consists the following fields:

content/protocol/transaction/transfer.md

@@ -7,6 +7,8 @@ math: false
 Transfer transaction is used to transfer coins between the [accounts](/protocol/blockchain/account/).
 If the receiver account does not exist, it will be created.
 
+The [Payload Type](/protocol/transaction/format/#payload-type) for Transfer is 1.
+
 ## Payload Structure
 
 The transfer transaction has a payload consists the following fields:

content/protocol/transaction/unbond.md

@@ -10,6 +10,8 @@ After 21 days, the stake can be withdrawn.
 This period is called the "unbond interval" and is defined in the [consensus parameter](/protocol/consensus/parameters/).
 Unbonding is free. This means there are no fees associated with the process of unbond transaction.
 
+The [Payload Type](/protocol/transaction/format/#payload-type) for Unbond is 4.
+
 ## Payload Structure
 
 The unbond transaction has a payload consists the following field:

content/protocol/transaction/withdraw.md

@@ -9,6 +9,8 @@ A withdraw transaction is used to retrieve the staked coins from an unbonded
 If the validator is still in the unbond period, the transaction will be rejected.
 The unbond period is a 21-day interval during which the validator is inactive, but their stake cannot yet be withdrawn.
 
+The [Payload Type](/protocol/transaction/format/#payload-type) for Withdraw is 5.
+
 ## Payload Structure
 
 The withdraw transaction has a payload consists the following fields: