VeThor (VTHO)

VeThor (VTHO): The Fee Token Powering VeChainThor

VeThor is the transaction and smart-contract fee asset of VeChainThor. Its role is closely tied to network activity, validator incentives, staking design, and VeChain’s governance process rather than to independent application features.

What VTHO does

VeThor, identified by the symbol VTHO, is the secondary token of the VeChainThor blockchain. It pays for transfers, smart-contract execution, and other state-changing operations. Reading blockchain data is free, but writing data requires gas, and VeChain’s developer documentation identifies VTHO as the gas asset used to pay that cost. VTHO is implemented as a built-in VIP180 fungible token rather than as a conventional contract deployed by an application developer.

The token’s practical demand therefore depends on activity on VeChainThor. A simple transfer, a contract call, or a transaction containing several clauses consumes gas according to the work required. The network’s transaction model allows one transaction to carry multiple instructions, which can make VTHO usage depend on both the number and complexity of tasks included in a transaction.

The two-token economy

VeChain separates the asset used for value transfer and staking from the asset used for network fees. VET is the primary ecosystem token, while VTHO represents the cost of using VeChainThor. The intended benefit is that application users and businesses do not need to expose every transaction directly to the market price of the primary token. This separation does not make fees fixed: the amount of VTHO required still depends on gas consumption and the protocol’s fee market.

VTHO does not have a fixed maximum supply in the current documentation. Its issuance is linked to the network’s staking and block-reward rules, while transaction fees use a base-fee and priority-fee structure. The base fee is burned and the priority fee goes to the validator that proposes the block. This creates two opposing flows: VTHO is created through protocol rewards and destroyed through fee payment, so the supply outcome depends on issuance, staking participation, transaction demand, and fee parameters.

Issuance, staking, and validators

VeChain’s current documentation describes VTHO generation as a function of VET locked by validators and delegators. The published formula uses a square-root relationship to total staked VET, meaning that additional staking increases aggregate issuance but produces diminishing incremental issuance as the staking base grows. The documentation says that delegators can participate through StarGate, while validators operate infrastructure and are required to stake VET as collateral.

This model makes VTHO partly dependent on VeChainThor’s security system. The network documentation describes 101 active validators, with validators receiving VTHO associated with their stake, a share associated with delegations, and priority fees from blocks they produce. That creates a direct connection between VTHO economics and the availability, concentration, and operating quality of the validator set.

Architecture for application users

VeChainThor is an Ethereum-compatible layer 1 implemented through the open-source Thor client. The repository describes the client as the official Go implementation and supports smart-contract development through familiar Ethereum tooling, while retaining VeChain-specific transaction features. These include multiple clauses in one transaction, transaction expiration and block references, dependency ordering, and native fee delegation.

Fee delegation is particularly relevant to applications that want to hide the initial need to acquire VTHO from end users. Under the documented mechanisms, a sponsor can pay a transaction fee on behalf of the sender through either native multi-party payment or the VIP-191 designated gas-payer approach. The dependency remains practical rather than automatic: an application still needs a sponsor, wallet or service integration, and a budget for the VTHO it pays.

Governance and upgrade control

VTHO’s rules are not immutable from the perspective of users. VeChain’s governance documentation says proposals can change network upgrades, token-emission parameters, gas rules, block rewards, and other technical or economic mechanics. The described process includes discussion, authorization by whitelisted accounts, voting, and a final on-chain execution record. Voting power is assigned to validators and StarGate node holders or managers rather than uniformly to every VTHO holder.

The system therefore combines public blockchain settlement with a defined governance and validator structure. The official consensus documentation describes known, identity-disclosed validators and a proof-of-authority design, while newer governance and tokenomics materials describe broader staking participation. For VTHO users, this means protocol upgrades, validator eligibility, staking rules, and fee parameters are material dependencies that should be reviewed when assessing the token’s long-term role.

Who the asset is designed to serve

VTHO is primarily designed for users of VeChainThor: application developers, businesses operating blockchain-backed workflows, validators, delegators, and end users whose transactions are sponsored by applications. VeChain’s official developer material emphasizes EVM-compatible development and enterprise-oriented infrastructure, while the network’s transaction features target applications that need multiple operations, controlled transaction lifecycles, and sponsored fees.

That positioning also defines the main limitation of VTHO’s utility: it is not a general-purpose governance or application token by itself. Its core function is to pay for computation and network actions on VeChainThor. Its economic relevance therefore depends on actual use of the chain, the amount of VTHO generated by staking, the fee market, the validator system, and the continued adoption of applications that require on-chain execution.

Key takeaways

• VTHO is VeChainThor’s gas and transaction-fee token, not the network’s primary staking asset.
• Its supply has no fixed maximum in the current documentation and is shaped by staking-linked issuance, fee burning, and validator rewards.
• VeChainThor supports fee delegation, allowing applications or sponsors to pay VTHO fees for users.
• The token’s demand depends on real transaction and smart-contract activity on VeChainThor.
• Governance can change emission, gas, reward, and upgrade parameters, with voting power concentrated among defined validator and node-holder groups.

Risks and open questions

• VTHO demand depends on sustained application activity; network growth does not automatically guarantee sufficient fee demand to offset issuance.
• The supply balance can change as staking participation, validator rewards, fee parameters, and transaction volume change.
• Validator and governance participation is structured around defined node and staking groups, which may create concentration and centralization risks.
• Fee delegation improves user onboarding but shifts VTHO costs to application operators or sponsors, creating a dependency on their budgets and continued operation.
• Protocol upgrades and tokenomics changes can alter VTHO generation, fee burning, validator incentives, or governance control.
• The exact economic outcome of future upgrades should be checked against the final activated protocol rules rather than draft proposals alone.