After signing the transaction, we may broadcast the transaction to a seed node (e.g. https://dev-api.zilliqa.com) by creating a transaction object. The correct RPC API to use is
Refer to https://apidocs.zilliqa.com/#createtransaction for more information.
The seed node performs some basic validation of the JSON payload it receives, and will attempt to verify the signature. Please note that it does not verify the correctness of the
nonce. It is at all times the developer's responsiblity to correctly increment the nonce used in the transaction.
nonce is incorrect, the transaction can silently fail. This means that the seed/lookup node will blindly forward the transaction to the correct shard, which may then reject the transaction with no error receipt.
The above applies only if we use JSON RPC API to create the transaction object. If SDKs are used to create the transaction object, then
nonce management is not an issue as SDKs would automatically handle the nonce management.
Non-Contract Transaction Object
Example of creating a non-contract transaction object:
Contract Transaction Object
The following is an example of creating a contract transaction object. The difference between contract and non-contract transaction objects is the additional contract transitions such as
setHello and its relevant params such as the
value as describe in the deployed contract.
The other significant difference is the
gasLimit field. For contract transaction objects, the recommended
gasLimit is between
Example of creating a contract transaction object: