HiveSQL
Search…
Introduction
Register your HiveSQL account
Support
Technical informations
Database Diagram
Operations
TxAccountClaims
TxAccountCreates
TxAccountRecoveryChanges
TxAccountRecoveryRequests
TxAccountRecoveryConfirms
TxAccountUpdates
TxAccountUpdates2
TxAccountWitnessProxies
TxAccountWitnessVotes
TxClaimRewardBalances
TxCollateralizedConverts
TxComments
TxCommentsOptions
TxConverts
TxCustoms
TxDeclineVotingRights
TxDelegateVestingShares
TxDeleteComments
TxEscrowApproves
TxEscrowDisputes
TxEscrowReleases
TxEscrowTransfers
TxFeeds
TxLimitOrdersCancels
TxLimitOrdersCreates
TxPows
TxProposalCreates
TxProposalRemoves
TxProposalUpdates
TxProposalVoteUpdates
TxRecurrentTransfers
TxTransfers
TxVotes
TxWithdraws
TxWithdrawVestingRoutes
TxWitnessSetProperties
TxWitnessUpdates
Virtual Operations
State tables
Full Text Search
Language detection
Tutorials
HiveSQL for Python developers
HiveSQL for PHP developers
HiveSQL for Ruby developers
HiveSQL for Microsoft Excel
HiveSQL Status
Resources
Powered By GitBook
TxWithdrawVestingRoutes

Blockchain operations

  • set_withdraw_vesting_route

Columns

Name
Description
from_account
account doing the VESTS (Hive Power) to HIVE conversion (powerdown)
to_account
account who will receive HIVE assets
percent
percentage of the powerdown value received by the recipient
auto_vest
true=automatically perform a reverse conversion from HIVE to VESTS to the recipient

Description

When initiating a powerdown, the initiating account can request the blockchain to send the converted liquid HIVE to one or multiple accounts rather than the withdrawing account.
In addition, those funds can be immediately vested again, circumventing the conversion from VESTS to HIVE and back.
Previous
TxWithdraws
Next
TxWitnessSetProperties
Last modified 1yr ago
Copy link
Contents