VeThor

vtho
Rank #526•
CoinYQ Dossier

VTHO: why VeChain replaced passive rewards with staking

VTHO was created so VeChainThor could spend one asset without consuming the other. For seven years, every VET balance quietly produced fuel. Then two 2025 upgrades rewrote the bargain: one changed what transaction fees destroy, and the other decided that only people locking VET for security should receive new issuance. The result is a gas token whose users, earners and governors are three overlapping but different groups.

A second token let VET remain intact while applications paid

VeChainThor began at midnight UTC on 30 June 2018 with a deliberate split. VET represented the scarce network asset; VeThor, recorded in the client as “energy,” began at zero and accumulated separately. A transfer or contract call spent VTHO instead of shaving value from the VET balance that supported the wider economy.

The split also made invisible payment possible. VeChainThor’s fee-delegation machinery lets a contract sponsor a user. A warehouse worker or customer can trigger an on-chain action while the application pays the fuel bill. That design made VTHO operationally important without requiring every end user to own it.

The token was not launched through its own sale. It is a built-in VIP-180 asset at a readable system address ending in the ASCII word “Energy.” Its familiar transfer and allowance methods make it wallet-compatible, but its creation and destruction happen inside chain rules.

The first engine rewarded ownership, not security work

The original formula treated every VET alike. Each unit produced 0.000432 VTHO per day, whether held by an authority node, an application treasury or an idle wallet. As all VET already existed, this made VTHO issuance steady and easy to forecast. It also detached new fuel from the work of producing blocks.

Fees supplied the counterweight. The early system burned 70% of a transaction fee and paid 30% to the producer. Supply could grow through universal VET generation and shrink through use. The model separated enterprise gas budgets from VET’s market price, but network activity and passive issuance did not have to move together.

Galactica rewrote destruction; Hayabusa rewrote creation

Galactica reached mainnet block 22,084,200 on 1 July 2025. Its EIP-1559-style market burns the dynamic base fee and sends any priority fee to the proposer. That was the first half of the monetary rewrite: the amount destroyed now responds to block demand, while users can tip for priority.

Hayabusa began at block 23,414,400 on 2 December. At that boundary the client stopped balance-based growth. The protocol then held a seven-day, 60,480-block transition in which neither the old mechanism nor the new staking rewards generated VTHO. The post-transition boundary arrived on 9 December, after which accepted blocks under DPoS became the source of new supply.

The replacement formula looks at actively staked VET and applies diminishing returns. A validator with delegators keeps 30% of its block reward and sends 70% to their pool; one without delegators keeps the block reward. Passive VET earns nothing. The change connected inflation to security, but it also concentrated new VTHO among those who meet staking, delegation and validator-performance conditions.

The people who spend VTHO do not control its rulebook

VTHO has no fixed cap. At mainnet block 25,804,268, live native counters showed about 107.57 billion VTHO in gross cumulative issuance and 4.07 billion burned. The client does not subtract burned units from its totalSupply counter, so calling that number circulating supply would be wrong. Later blocks change both counters.

There is no normal deployer account with a public mint or freeze method on the Energy interface. That does not make the economics immutable. Thor client releases install built-in code at hard-fork heights, protocol parameters shape reward calculations, approved proposals need implementation, and validators must run the adopted software.

The split ends with an asymmetry. VTHO holders pay for the network but receive no VTHO-based vote. Governance weight sits with validators and eligible VET-backed StarGate positions. The Foundation’s MiCAR paper also rejects issuer redemption, dividends, profits and proprietary claims. The fuel works when the chain accepts it; it is not a claim on the organization that maintains the chain.

How the project changed

  1. 2018-06-30
    VeChainThor starts with empty fuel tanks

    The genesis block establishes VET and the zero-initial-supply Energy asset that wallets know as VTHO.

  2. 2018–2025
    Every VET balance produces gas

    The fixed rule generates 0.000432 VTHO per VET each day, regardless of staking activity.

  3. 2025-07-01
    Galactica makes the base fee the burn target

    At block 22,084,200, a dynamic fee market replaces the old fixed 70/30 transaction-fee split.

  4. 2025-07-28
    Engineers publish the DPoS tokenomics specifications

    VIP-253 and VIP-254 document the transition window, active-stake issuance and validator-delegator split.

  5. 2025-12-02
    Hayabusa stops passive generation

    Block 23,414,400 begins the 60,480-block transition; no VTHO rewards are generated during the window.

  6. 2025-12-09
    Block rewards replace wallet accrual

    The transition boundary arrives at block 23,474,880 and the active-stake reward economy follows.

Evidence and primary sources

Last evidence review: 2026-09-05

What is VeThor?

VeThor (VTHO) is the gas asset of VeChainThor, not a smaller denomination of VET. It is an 18-decimal VIP-180 token implemented as the chain’s built-in Energy contract at 0x0000000000000000000000000000456E65726779. Sending assets, calling a contract or sponsoring another user’s transaction consumes VTHO. VET has a different job: validators and delegators lock it for security and voting weight.

VTHO has no fixed maximum. The network creates it as block rewards and destroys the base-fee portion spent on transactions. That balance was redesigned in 2025. Galactica introduced a dynamic base fee and validator tip; Hayabusa ended automatic generation by liquid VET balances and made active stake the source of new VTHO.

This separation matters to rights as well as mechanics. A VTHO balance can be transferred or spent as gas, but it does not stake the chain or vote on the policy that governs future issuance.

What problem does VeThor solve?

VeChain wanted applications to budget computation without spending their scarce staking asset every time they wrote data. A separate fuel token allowed a business or sponsor to buy transaction capacity while VET stayed locked or held. The built-in sponsorship system can even let the application pay, so an end user need not see VTHO at all.

The first design solved access but created a distribution problem. Every VET balance generated VTHO at the same fixed rate, whether its owner operated infrastructure or did nothing. Supply growth followed the amount of VET in existence rather than the amount securing the network, while actual demand depended on applications using gas.

The 2025 changes tied creation to work. They did not make price or supply predictable: issuance now varies with active stake, burning varies with transaction demand, and the people who hold VTHO are different from the VET-backed voters who can approve later policy changes.

How does VeThor work?

A transaction states a gas limit and pays VTHO. Since Galactica, the dynamic base fee is burned and an optional priority fee goes to the validator that proposed the block. The old 70% burn and 30% producer-share rule belongs to the pre-Galactica history.

New VTHO now comes from accepted blocks under Hayabusa. Total issuance is proportional to the square root of actively staked VET, so adding stake raises total issuance less than proportionally while yield per staked VET falls with the inverse square root. When a proposer has active delegations, 30% of its block reward goes to the validator and 70% to the delegator pool; without delegations, the proposer receives all of that reward.

VTHO’s ERC-20-like surface handles balances, transfers and allowances. Its supply is nevertheless protocol state, not a conventional token contract controlled by a deployer’s mint button. The Thor client stops the old balance-growth mechanism, calculates block rewards and installs changed built-in code at named fork heights. Governance, maintainers and validator adoption therefore matter even though the token interface has no ordinary owner or freeze switch.

Key facts

  • Identity: VTHO is VeChainThor’s 18-decimal VIP-180 gas asset at the built-in Energy address; it is separate from VET.
  • Origin: VeChainThor genesis is dated 30 June 2018, and the original built-in documentation says VTHO began with zero supply.
  • Old issuance: until Hayabusa, each VET generated 0.000432 VTHO per day whether or not it was staked.
  • Fee rewrite: Galactica activated at block 22,084,200 on 1 July 2025; current base fees are burned and priority fees go to block proposers.
  • Issuance rewrite: Hayabusa started a no-reward transition at block 23,414,400 on 2 December 2025; DPoS rewards followed after the 60,480-block window ending 9 December.
  • Current rewards: total VTHO issuance rises with the square root of active VET stake, while yield per staked VET falls with the inverse square root; the standard split with delegations is 30% validator and 70% delegator pool.
  • Supply: there is no fixed maximum. At block 25,804,268, gross issuance was 107,570,473,331.845068656163212212 VTHO and cumulative burns were 4,074,605,249.112071781026431409; neither counter is circulating supply.
  • Voting boundary: VTHO does not vote. Validators and eligible VET-backed StarGate positions participate in current governance.
  • Control boundary: there is no ordinary VTHO owner mint or freeze method, but fork code, protocol parameters and governance can alter issuance and fee policy.
  • Legal boundary: the MiCAR paper gives VTHO no issuer redemption, refund, dividend, profit, proprietary or governance right.
  • Account-master boundary: Energy.move lets a contract account or that account’s protocol master move its VTHO; it is not a global Foundation seizure function.

Official links

Frequently asked questions

Are VET and VTHO the same asset?

No. VET is the fixed-supply asset locked for validation, delegation and voting weight. VTHO is the variable-supply fuel spent on VeChainThor transactions. Markets may exchange them, but the protocol sets no fixed conversion or redemption rate.

Does simply holding VET still generate VTHO?

No. That fixed-rate system stopped when the Hayabusa transition began on 2 December 2025. New protocol rewards go to eligible VET actively staked by validators and StarGate delegators after the transition.

Can VTHO be staked to earn more VTHO?

VTHO itself is not the consensus collateral. Validators and delegators lock VET; the protocol pays their rewards in VTHO. A third-party product may offer a VTHO deposit, but that would be a separate counterparty arrangement.

Is all VTHO spent on gas burned?

Under the current fee market, the base-fee portion is burned and the priority fee is paid to the proposer. Older material describing a 70% burn and 30% producer reward refers to the pre-Galactica rule.

Does VTHO have a maximum supply?

No fixed cap is published. Block rewards increase supply while base-fee burning reduces it. The total therefore changes with active VET stake, block production and network use.

Who can change VTHO monetary policy?

VTHO holders do not vote by holding VTHO. Current governance uses validators and eligible VET-backed StarGate positions, while proposal authorization, code implementation and validator adoption remain distinct steps.

Can an issuer redeem VTHO for money?

The current MiCAR paper says holders are not entitled to issuer reimbursement, withdrawal or refund. VTHO’s embedded entitlement is its network function: transfer it and spend it for gas.

Why can an application user avoid holding VTHO?

VeChainThor supports fee sponsorship. A contract or sponsor can pay transaction costs for an approved user, so the application may consume VTHO behind the interface even when the user never buys it.

Can the Foundation freeze any VTHO balance?

No global pause, blacklist or owner-freeze method appears in the Energy ABI. A narrower built-in rule lets a contract account or that account’s protocol master move its VTHO, while protocol upgrades can change system behavior.

External trackers

Choose a tracking site for VeThor: