Tx-Validation
Send transaction and simultaneously ensure they are valid
Transactions are added to a block only if they pass the node's validation test.
Use the Tx Validation utility to send transactions while, at the same time, ensure that you are constructing your transactions correctly, i.e. that they will pass the test.
Send the transaction using the request format below. The response will include:
Your request in the format that should be used when sending it to CloudAPI
Details about the transaction such as gas price and value
If an error occurred, information about the error
Tx Validation adds a layer of usability to the existing node validation utility.
When adding node_validation: true
to a transaction request you will receive an error
response only if your transaction was not valid.
Using Tx Validation you will always get a response and additional information is provided regarding errors, if and when they occur.
REQUEST
Parameters
Parameters
Name | Description | Options & Additional notes |
---|---|---|
auth_header | Allows the user to include the authentication in the URL string directly. | If the authentication is provided in both the header and the URL parameter, the one in the header will be used. |
blockchain_network | Blockchain network name. | Optional. Available options are: Mainnet, BSC-Mainnet, Polygon-Mainnet. Default: Mainnet |
nonce_monitoring | A boolean flag indicating if Tx Nonce Monitoring should be enabled for the transaction. | Optional. Default: False |
validators_only | Support for semi private transactions in all networks. | Optional. Must be false when using node validation. Default: False |
next_validator | Transaction should be sent to the next validator. | Optional. Must be false when using node validation. Default: False |
RESPONSE
Examples
for a valid transaction:
for an invalid transaction - nonce too low:
Last updated