Transactions¶

Tx¶

Field		Type	Description
Hash		bytes	Hash of body
Body	Nonce	uint64	Increasing number used only once per sender account
	Account	bytes	Decoded sender account address
	Recipient	bytes	Decoded receiver account address
	Amount	bytes	Amount of transfer
	Payload	bytes	Smart contract data
	Limit	uint64	Maximum limit of gas to be used (0 = no limit)
	Price	bytes	Reserved
	Type	int	See below
	ChainIDHash	bytes	Hash of chain ID
	Sign	bytes	ECDSA signature with secp256k1

Payload¶

A payload can be any kind of binary data, but is most often used with JSON strings for smart contract calls.

Transaction types¶

There are several kinds of transactions.

Normal type (0)¶

Normal transactions are used to transfer tokens and calling smart contracts. Since version 2.0, there are more precise transaction types that should be used instead.

Governance type (1)¶

Governance transactions are used for calling system contracts, such as staking and voting. Transactions of this type have a special payload format and recipient. See below for details.

Transfer type (4)¶

Transactions that only transfer value. For backwards compatability, the Normal type can also be used.

Call type (5)¶

Smart contract calls should be denoted using the Call transaction type. For backwards compatability, the Normal type can also be used.

FeeDelegation type (3)¶

FeeDelegation transactions are used for calling smart contract while charging fees to the contract. This only works if the contract supports the fee delegation interface.

Deploy type (6)¶

Used to deploy contracts. For backwards compatability, the Normal type can also be used.

Redeploy type (2)¶

Used to re-deploy a contract.

Governance transaction details¶

The following table shows the specification for each field of the transaction body of a governance transaction.

Action	Recipient	Amount	Payload
staking	`aergo.system`	amount to stake	`{"Name":"v1stake"}`
unstaking	`aergo.system`	amount to unstake	`{"Name":"v1unstake"}`
voting	`aergo.system`	0	`{"Name":"v1voteBP","Args":[<peer IDs>]}`
voting DAO	`aergo.system`	0	`{"Name":"v1voteDAO","Args":[<DAO ID>,<candidate>]}`
create name	`aergo.name`	20 aergo *	`{"Name":"v1createName","Args":[<a name string>]}`
update name	`aergo.name`	20 aergo *	`{"Name":"v1updateName","Args":[<a name string>, <new owner address>]}`
add admin	`aergo.enterprise`	0 aergo	`{"Name":"appendAdmin","Args":[<new admin address>]}`
remove admin	`aergo.enterprise`	0 aergo	`{"Name":"removeAdmin","Args":[<admin address>]}`
change raft cluster	`aergo.enterprise`	0 aergo	`{"Name":"changeCluster","Args":[{"command":"add","name":"[node name]","address":"[peer address]","peerid":"[peer id]"}]}`
add config	`aergo.enterprise`	0 aergo	`{"Name":"appendConf","Args":[<config key>,<config value>]}`
enable config	`aergo.enterprise`	0 aergo	`{"Name":"enableConf","Args":[<config key>,<true\|false>]}`
remove config	`aergo.enterprise`	0 aergo	`{"Name":"removeConf","Args":[<config key>,<config value>]}`

* The amount needed for name transactions is determiend by the NAMEPRICE vote. It is currently 20 aergo on Mainnet. You can retrieve this information by accessing the network’s ChainInfo.

The aergo.system transactions, including staking, unstaking and voting, can be sent once per 24 hours per account. The only exception is when you first vote. For staking and unstaking, there is a limit to the amount of requests. It must be over 10000 aergo based on the amount of staked. Therefore, the first staking request should exceed 10000 aergo, and in the case of the unstaking request, more than 10000 must be left or withdrawn altogether.

When voting for DAO, there are IDs by paramter. It will be changed to the new value when the first place gets 2/3 of the staking total.

DAO ID	Value	Description
BPCOUNT	1 to 100	The number of block producer
STAKINGMIN	1 to 500000000000000000000000000	The amount of staking minimum
GASPRICE	1 to 500000000000000000000000000	The price of gas
NAMEPRICE	1 to 500000000000000000000000000	The price of name transactions

The aergo.enterprise transactions are only for the private blockchain network. if you want to enable aergo.enterprise, you should make the genesis block with "public":"false"