Through this endpoint, users can manage TRX staking: freezing, unfreezing, and withdrawing TRX. Stake an amount of TRX to obtain bandwidth or energy and optimize blockchain resource usage. Additionally, users can delegate bandwidth or energy resources to other accounts for efficient transaction processing.
Specifies the blockchain network involved in the transaction (eg. tron).
Represents the originating address from which the transaction is initiated.
Specifies the network used (eg. mainnet , nile).
Represents the sender's specific and unique Vault ID of the sender.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context
is specified by the user.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context
is specified by the user.
The amount of TRX which will be freeze/unfreeze/delegate/undelegate. When type of request is withdraw-resource the amount is not required.
Boolean if we want to lock the delegated amount. Whether to lock the resource delegation, true means locked the delegation, the delegating cannot be canceled within the period specified by lockPeriod, false means non-locked, the resource delegating can be canceled at any time.
Only when lock is true, this field is valid. If the delegate lock period is 1 day, the lock_period is: 28800. The minimum value of lockPeriod is the remaining lock period of this type of resource that was delegated last time, and the maximum value is 864000 (30 days). If lock is true and lock_period is not set or set to 0, lockPeriod will be set to the default value 86400 (3 days) automatically.
Transaction note with additional details.
Resource staking for (e.g. Bandwidth, Energy).
Address receiving the delegated amount or from which we undelegate. It is used when type of the request is delegate/undelagate.
Type of the request (e.g. freeze, unfreeze, withdraw-resource)
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId
is generated by Vaultody and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context
is specified by the user.
Specifies the blockchain network involved in the transaction. (eg. tron).
Destination of the transaction
Address of the destination that will receive the resources.
The amount of TRX being staked/unfrozen.
The unit of currency used in the transaction.
A unique identifier for the transaction.
Specifies the network used (eg. mainnet, nile).
Specifies the type of the resource being managed(eg. bandwidth, energy).
Details about the sender
The address of the sender.
Defines the status of the transaction request, (e.g. created).
The type of staking operation being performed (eg. freeze, unfreeze, withdraw-resource)
Identifies the vault id linked to the transaction.
cb233681a8ee35665296c1824c1f67bc46691788
PSqeqRLap8rBc/wogNU1DeGGUPb2VyVtg6GiBOaBnYQ=
1681885776
zYgKeueoOq
{
"context": "yourExampleString",
"data": {
"item": {
"amount": "3",
"lock": "true",
"lockPeriod": "28800",
"note": "Your note",
"resource": "bandwidth",
"toAddress": "TJgba7p9nFz6vMgVBJUxTaRR8WbpaG6ifi",
"type": "freeze"
}
}
}
{
"apiVersion": "2024-05-09",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"item": {
"blockchain": "tron",
"destination": [
{
"address": "TMLmaAS4GfshG6PfToD5YYRm5G8giauYc4",
"amount": "3",
"amountUnit": "TRX"
}
],
"id": "67a336950ca2f4fd25fb0deb",
"network": "mainnet",
"resource": "energy",
"source": {
"address": "TMLmaAS4GfshG6PfToD5YYRm5G8giauYc4"
},
"status": "created",
"type": "freeze",
"vaultId": "66d9b73a9f455b085ed9de39"
}
}
}