CoinYQ Dossier

The chain that changed both its coin and its gatekeepers

VeChain's history contains two migrations. The first moved value from Ethereum VEN into native VET and split gas into VTHO. The second moved block production from identified authorities to delegated stake. Each widened the system in one direction while leaving another set of gates—issuance rules, proposal authorization, software delivery and commercial contracts—fully visible.

One VEN became one hundred VET—and a second token appeared

VeChain began its market life on someone else's chain. VEN was an ERC-20 token on Ethereum, sold before VeChainThor could carry its own assets. When mainnet launched in 2018, the Foundation exchanged each VEN for 100 VET. The split changed the unit count, not the proportional ownership of the migrated pool.

The move was an administered bridge rather than a protocol teleport. By September 2018 the Foundation reported 93.5% swapped, with surrendered VEN sent to unspendable addresses before VET distribution. It kept a residual service open for years, then closed it on 10 October 2023. A forgotten VEN balance is now a legacy asset without an official conversion path.

Mainnet added an economic companion. VET became the fixed-supply value, staking and governance-weight asset. VTHO began at zero and paid for computation. The design let an application acquire or sponsor gas without spending its principal staking asset.

The gas engine stopped rewarding stillness

VET's supply is fixed at 86,712,634,466. VTHO's is not. Before Hayabusa, every VET balance generated VTHO at a linear rate, whether or not its owner helped secure the chain. That kept gas abundant, but spread issuance across passive balances and weakened the link between inflation and validation.

Hayabusa redirected issuance to active stake. Validators and StarGate delegators now generate VTHO as a function of total locked VET, with the formula scaling sub-linearly. Protocol rewards divide 30% to validators and 70% to delegator pools. Galactica's fee market burns the base fee and awards the priority fee to the proposer. VTHO policy can therefore contract through burning and expand through security rewards at the same time.

VeChain replaced known authorities with economic admission

The original network chose identity as its Sybil defense. Up to 101 Authority Masternodes passed KYC and were admitted to produce blocks. A built-in Executor started with seven approvers; after two-thirds approval it could call contracts that changed authority candidates and network parameters. Efficiency came with an explicit committee choke point.

Renaissance dismantled that exact arrangement in stages. Galactica modernized the EVM and fee market. On 2 December 2025, Hayabusa activated at block 23,414,400 and replaced KYC PoA with DPoS. Current validators post 25,000,000 VET, and holders can delegate through a StarGate NFT instead of operating infrastructure.

Permissionless candidature removes identity approval, but capital and coordination remain filters. The 25 million VET validator stake is substantial, 101 validators still carry block production, and two-thirds plus one are needed for finality. Delegators choose among that set and inherit validator performance risk.

The committee left the ballot, not the whole machine

Current governance says the Steering Committee is deprecated and decisions belong to validators and eligible StarGate node holders using VeVote. Voting weight varies by role, and the current quorum is 5% of eligible weight. That percentage is a configurable contract value, so even the participation threshold belongs to governance rather than nature.

The pipeline has gates outside the tally. Proposal creation is authorized through whitelisted accounts. Passed proposals require off-chain implementation and end with an on-chain execution record; VeVote itself is modular and upgradeable. The Foundation and maintainers can propose and write software, administrators can exercise contract permissions, and validators can accept or reject releases. Those actors overlap but are not equivalent.

Enterprise relationships sit still farther away. DNV publicly confirmed a 2018 partnership for traceability of product and supplier information. That establishes a collaboration at that time, not permanent volume on VeChainThor. It also creates no redemption, equity, product-data ownership or partner-revenue right for a VET holder. Token utility ends where the customer's commercial contract begins.

How the project changed

  1. 2017
    VEN is sold on Ethereum

    VeChain finances the pre-mainnet project with an ERC-20 token and forms the Foundation and first Steering Committee.

  2. 2018
    VeChainThor launches with PoA and dual tokens

    The mainnet introduces 101 authorized producers, converts VEN to VET at 1:100 and makes VTHO the gas asset.

  3. 2023-10-10
    The residual VEN swap closes

    After five years, the Foundation ends its official service for converting legacy Ethereum VEN into native VET.

  4. 2025-07
    Galactica changes the fee market

    The first Renaissance protocol phase adds Shanghai EVM alignment and a dynamic base-fee burn plus validator tip.

  5. 2025-12-02
    Hayabusa replaces KYC PoA

    At block 23,414,400, DPoS activates; VTHO issuance moves from passive holding to validator and delegator stake.

Evidence and primary sources

Last evidence review: 2026-09-04

What is VeChain?

VeChainThor is a public, EVM-compatible smart-contract network created by VeChain. Its current primary asset, VET, is not the Ethereum token sold under the ticker VEN. At mainnet launch in 2018, the Foundation exchanged one VEN for 100 native VET; the support service closed on 10 October 2023. VET's fixed total supply is 86,712,634,466.

VeChain separates stake and computation. VET is locked by validators and delegators and supplies governance weight. VTHO is a distinct VIP-180 token used for gas. Since the Hayabusa hard fork, only eligible actively staked VET contributes to VTHO issuance; a liquid VET balance no longer produces it automatically.

The network also changed who produces blocks. VeChainThor began with 101 KYC-identified Authority Masternodes under Proof of Authority. Hayabusa activated delegated proof of stake on 2 December 2025. Current documents describe 101 validators, a 25,000,000 VET validator stake and delegation through StarGate.

What problem does VeChain solve?

VeChain was designed for organizations that wanted to put supply-chain or assurance records on a public ledger without making customers manage blockchain fees. The dual-token model was its answer: hold and stake VET as the scarce network asset, spend VTHO for computation, and let sponsors pay a user's gas when an application needs conventional onboarding. The separation makes business costs less directly tied to VET's market price, but it creates two policies instead of one.

The original policy favored operational identity. Authority nodes passed KYC and a Foundation-era executive committee controlled the built-in path for adding or revoking producers and changing parameters. That made upgrades efficient and accountability legible, while concentrating admission and protocol discretion. Renaissance changed the bargain: Galactica installed a dynamic fee market, and Hayabusa opened validation and delegation under DPoS.

Voting is broader now, but a vote is not the whole change pipeline. Current docs retain whitelisted proposal authorization and describe execution as off-chain work ending in an on-chain record. Client developers must implement a change and validators must adopt it. VET ownership alone neither writes the release nor creates legal rights in an enterprise application.

How does VeChain work?

VET and VTHO follow different supply rules. All 86,712,634,466 VET already exist, so staking reallocates existing VET rather than minting more. VTHO has no fixed maximum. Its current issuance is a function of total VET actively locked, and protocol rewards are split 30% to validators and 70% to their delegator pools. Transaction base fees are burned and priority fees go to the proposing validator under the dynamic fee market.

A validator locks 25,000,000 VET and operates block-producing infrastructure. StarGate users lock VET into transferable staking NFTs and delegate to a validator. The current 101-validator set reaches consensus with a two-thirds-plus-one threshold. Performance and delegation therefore affect rewards, while simply leaving VET liquid does not.

VeVote gives validators and eligible StarGate NFT holders, owners or delegates voting weight. The current quorum is 5% of eligible weight and can itself be changed through smart-contract configuration. Governance covers consensus, technical upgrades, staking formulas and voting models. Proposal creation is authorized through a whitelist, and passed decisions still require implementation and execution.

That current stack replaces a historical one rather than erasing it. The old built-in Executor began with seven committee approvers and could call Authority or Params after two-thirds approval. The Steering Committee is now deprecated for protocol voting, but the Foundation, contract administrators, maintainers and validators retain different practical powers around the voter layer.

Key facts

  • Migration lineage: 1 Ethereum VEN became 100 native VET; the Foundation says the remaining swap service closed on 10 October 2023.
  • Fixed primary asset: total VET supply is 86,712,634,466 and no additional VET is scheduled to be minted by the protocol.
  • Variable gas asset: VTHO pays transaction fees, has no fixed cap and since Hayabusa is issued only through eligible active staking.
  • Historical control: PoA used 101 KYC Authority Masternodes and a seven-approver built-in Executor for authority and parameter changes.
  • Current consensus: Hayabusa activated at block 23,414,400 on 2 December 2025; current validators stake 25,000,000 VET and users may delegate through StarGate.
  • Current voters: validators and eligible StarGate NFT holders or delegates vote in VeVote; reviewed docs set quorum at a configurable 5% of eligible weight.
  • Execution boundary: the Steering Committee is deprecated for voting, but proposal creation is whitelisted and passed proposals still require off-chain implementation and an on-chain execution record.
  • Commercial-right boundary: a named partnership or application can use VeChainThor, but VET does not grant equity, guaranteed redemption, partner revenue, product ownership or passive post-Hayabusa VTHO rewards.

Official links

Categories

Related coins

Frequently asked questions

Can I still swap VEN for VET?

The Foundation's support article says no. The mainnet migration exchanged 1 Ethereum VEN for 100 native VET, and the remaining swap service officially closed on 10 October 2023. VEN and VET should be treated as different chain assets, not interchangeable tickers.

Are VET and VTHO interchangeable?

No. VET is the fixed-supply primary and staking asset. VTHO is the variable-supply VIP-180 gas token spent for transactions. Markets may offer exchange routes, but the protocol does not promise a fixed conversion or redemption rate between them.

Does every VET holder earn VTHO?

That was the pre-Hayabusa model. Current issuance rewards VET actively staked by validators or through eligible StarGate delegation. Liquid VET alone does not generate VTHO. Reward amounts vary with total stake, validator performance and protocol parameters.

Is VeChain still Proof of Authority?

Historically yes; current mainnet no. VeChainThor launched with 101 KYC Authority Masternodes. Hayabusa activated DPoS at block 23,414,400 on 2 December 2025. Current docs describe 101 validators and a 25 million VET validator stake.

Did VeVote remove Foundation or administrator control?

It deprecated the Steering Committee as the voting body and opened voting to validators and eligible StarGate nodes. Proposal authorization remains whitelisted, the governance contracts are upgradeable, and passed decisions require implementation and execution. Voting, code authorship, contract administration and validator adoption are separate powers.

Do VeChain's enterprise partnerships create rights for VET holders?

No. DNV's own announcement confirms a defined traceability collaboration, but a partnership does not give VET holders revenue, equity or ownership of product data. Each enterprise deployment has its own customer, contract, duration and legal rights, and may generate little or no token demand.

External trackers

Choose a tracking site for VeChain: