Skip to content

stake-v1-legacy.md

Latest commit

 

History

History
71 lines (45 loc) · 3.47 KB

stake-v1-legacy.md

File metadata and controls

71 lines (45 loc) · 3.47 KB
Raw

Staking (Stake 1.0, legacy)

⚠️ Legacy. These are the pre–Stake 2.0 freeze commands, kept for reference. New usage should prefer Stake 2.0. For the difference between the two models, see concepts/staking-models.

Legacy freeze/unfreeze and resource delegation (v1). Bandwidth mechanics are explained in concepts/resources.

How to freeze/unfreeze balance

After the funds are frozen, the corresponding number of shares and bandwidth will be obtained. Shares can be used for voting and bandwidth can be used for trading. The rules for the use and calculation of share and bandwidth are described in concepts/resources.

Freeze operation is as follows:

> freezeBalance [OwnerAddress] frozen_balance frozen_duration [ResourceCode:0 BANDWIDTH, 1 ENERGY] [receiverAddress]
  • OwnerAddress — the address of the account that initiated the transaction, optional, default is the address of the login account.
  • frozen_balance — the amount of frozen funds, the unit is Sun. The minimum value is 1000000 Sun (1 TRX).
  • frozen_duration — freeze time, this value is currently only allowed for 3 days.

For example:

> freezeBalance 100000000 3 1 address

After the freeze operation, frozen funds will be transferred from Account Balance to Frozen. You can view frozen funds from your account information. After being unfrozen, it is transferred back to Balance from Frozen, and the frozen funds cannot be used for trading.

When more share or bandwidth is needed temporarily, additional funds may be frozen to obtain additional share and bandwidth. The unfrozen time is postponed until 3 days after the last freeze operation.

After the freezing time expires, funds can be unfrozen.

Unfreeze operation is as follows:

> unfreezeBalance [OwnerAddress] ResourceCode(0 BANDWIDTH, 1 CPU) [receiverAddress]

How to delegate resource

FreezeBalance (delegate)

> freezeBalance [OwnerAddress] frozen_balance frozen_duration [ResourceCode:0 BANDWIDTH, 1 ENERGY] [receiverAddress]

The latter two parameters are optional. If not set, the TRX is frozen to obtain resources for its own use; if not empty, the acquired resources are used by receiverAddress.

  • OwnerAddress — the address of the account that initiated the transaction, optional, default is the address of the login account.
  • frozen_balance — the amount of frozen TRX, the unit is the smallest unit (Sun), the minimum is 1000000 sun.
  • frozen_duration — frozen duration, 3 days.
  • ResourceCode — 0 BANDWIDTH; 1 ENERGY.
  • receiverAddress — target account address.

UnfreezeBalance (undelegate)

> unfreezeBalance [OwnerAddress] ResourceCode(0 BANDWIDTH, 1 CPU) [receiverAddress]

The latter two parameters are optional. If they are not set, the BANDWIDTH resource is unfrozen by default; when the receiverAddress is set, the delegated resources are unfrozen.

Get resource delegation information

  • getDelegatedResource fromAddress toAddress — get the information from the fromAddress to the toAddress resource delegate.
  • getDelegatedResourceAccountIndex address — get the information that address is delegated to other accounts' resources.

See also