VeChain Docs
  • Welcome to VeChain
  • Blockchain Basics
    • Introduction to blockchain
    • Introduction to digital property
    • The evolution of the internet
  • Introduction to VeChain
    • About the VeChain blockchain
      • Consensus Deep Dive
      • Governance
    • Dual-Token Economic Model
      • VeChain (VET)
      • VeThor (VTHO)
    • Acquire VeChain Assets
    • Sustainability
  • Core Concepts
    • Networks
      • Thor Solo Node
      • Testnet
      • Mainnet
    • Nodes
      • Node Rewards Programme
    • Blocks
      • Block Model
    • Transactions
      • Transaction Model
      • Transaction Fees
      • Transaction Calculation
      • Meta Transaction Features
        • Transaction Uniqueness
        • Controllable Transaction Lifecycle
        • Clauses (Multi-Task Transaction)
        • Fee Delegation
          • Multi-Party Payment (MPP)
          • Designated Gas Payer (VIP-191)
        • Transaction Dependency
    • Block Explorers
    • Wallets
      • VeWorld
        • User Guide
          • Setup
          • Wallet
          • Signing
          • Activities
          • Settings
        • FAQ
      • Sync2
        • User Guide
          • Setup
          • Wallet
          • Signing
          • Activities
          • Settings
        • FAQ
      • Sync
        • User Guide
          • Wallet
          • Ledger Device
          • Browser dApps and web
          • Interact with dApps
          • Activities
          • Settings
          • Report an Issue
          • Contributing
        • FAQ
    • EVM Compatibility
      • VeChain Modifications
      • Methodology
      • Test Coverage
        • Gas model
        • Raw transaction
        • hardhat specific
          • Ganache failures
          • evm_increaseTime
        • Failures in constructor
        • eth_sign
        • Contract address prediction
        • BadBeacon proxy address at 0x1
      • How to Recreate
      • Additional Information
        • Using Governance Contracts
        • ERC1820/ERC777 Testnet
        • Delegate Options
    • Account Abstraction
      • UserOperation
      • Bundler
      • EntryPoint Contract
      • Account Factory Contract
      • Paymaster Contract
    • Token Bound Accounts
  • How to run a node
    • Nodes
    • How to run a Thor Solo Node
    • Custom Network
    • Connect Sync2 to a Thor Solo Node
  • Developer Resources
    • Getting Started
    • How to build on VeChain
      • Connect to the Network
      • Read Data
        • Read Blocks
        • Read Transactions
        • Read Accounts
        • States & Views
        • Events & Logs
        • VET Transfers
      • Write Data
        • Transactions
        • Fee Delegation
      • Listen to Changes
        • Events
        • VET Transfers
        • Transactions
        • Blocks
        • Beats
      • Build with Hardhat
      • Utilities
        • BigInt and Unit-Handling
        • Name Service Lookups
    • Example dApps
      • Buy me a Coffee
      • Token Bound Accounts
      • PWA with Privy and Account Abstraction
    • EVM Compatibility for Developers
      • Key Architectural Differences and Optimizations
      • Practical Implications for Developers: Key Considerations
      • RPC Methods (Detailed Breakdown)
      • Frequently Asked Questions (FAQs)
      • VeChain Blockchain Specifications
      • Key Differences Between VeChain and Ethereum (Summary)
      • Best Practices for Developing on VeChainThor
    • How to verify Address-Ownership
      • Next.js Session Verification
    • Debug Reverted Transactions
    • Account Abstraction
    • VIP-191: Designated Gas Payer
      • How to Integrate VIP-191 (I)
      • How to Integrate VIP-191 (II)
      • How to Integrate VIP-191 (III)
    • Index with Graph Node
      • Setup with Docker
      • Index with OpenZeppelin
        • Create Subgraph Project
        • Configure Contracts
        • Deploy Subgraph and start Indexing
        • Track Subgraph Indexing
        • Access Subgraph
        • Update Subgraph
    • SDKs & Providers
      • SDK
        • Architecture
        • Accounts
        • Bloom Filter
        • Certificates
        • Contracts
        • Cryptography
        • Debug
        • Encoding
        • Polls
        • Subscriptions
        • Thor Client
        • Transactions
      • Thor DevKit
        • Installation
        • Usage
          • Cryptography
          • Accounts
          • Encoding
          • Transactions
          • Certificates
          • Bloom Filter
      • DApp Kit
        • v2
          • Installation
          • React
            • Installation
            • Usage
          • Vanilla JS
            • Installation
            • Usage
          • Core
            • Installation
            • Usage
          • Theme Variables
          • i18n
        • v1
          • Installation
          • React
            • Installation
            • Usage
          • Vanilla JS
            • Installation
            • Usage
          • Core
            • Installation
            • Usage
          • Theme Variables
          • i18n
          • Node Polyfills
          • V0 to V1
        • v0
          • Installation
          • Usage
          • React
            • Installation
            • Usage
          • Vanilla (UI)
            • Installation
            • Usage
          • Styles (UI)
          • i18n
      • DevPal
      • Web3-Providers-Connex
        • Installation
        • Usage
      • Connex
        • Installation
        • API Specification
    • Frameworks & IDEs
      • Hardhat
      • Remix
    • Built-in Contracts
    • VORJ
    • Useful Links
  • How to contribute
Powered by GitBook
On this page
  • What are nodes in blockchain networks?
  • What are the different types of nodes that support the VeChainThor blockchain?
  • Authority Masternode (AM)
  • Economic & X-Nodes
  • Full Nodes

Was this helpful?

  1. Core Concepts

Nodes

Defining the different types of nodes who support the VeChain ecosystem.

What are nodes in blockchain networks?

In blockchain networks, nodes are individual computers or devices that participate in maintaining the blockchain's network by

  • validating

  • storing

  • relaying

transactions and blocks.

As with any peer-to-peer network, nodes play a crucial role in the overall functioning and security of the network. The more nodes who contribute to the network, generally the more robust and secure the network will be.

What are the different types of nodes that support the VeChainThor blockchain?

The VeChainThor network is supported by various different types of nodes, who all contribute to the ecosystem in a particular way.

Authority Masternode (AM)

AMs are responsible for keeping operational both consensus and block production on the VeChain network. There are 101 AMs who are authorised, via an on-chain whitelist, to validate and propose blocks on the VeChainThor blockchain. As a reward, the AM who has proposed a block receives 30% of all VTHO used for the transactions (gas fees) in a block, with the other 70% being burned.

There's a rigorous process implemented in order for a person/entity to run an AM:

  • Be vetted to ensure they have a legitimate identity;

  • Hold 25M VETs as collateral; and,

  • Run and manage the node with a certain guaranteed level of performance and availability.

Economic & X-Nodes

With only 101 nodes being responsible for the network, both VeChain Economic and X-Node programs aims to increase stability in the VeChain ecosystem and act as a distribution of power and privilege within the blockchain’s economy.

Both nodes are governance tokens and are tight to a minimum requirement of VET soft-locked in the wallet, and the two node types but have slightly different requirements.

Economic Nodes
X-Nodes

Rewards

--

VTHO generated from 5bln VET X-Node pool.

Application

Applied for based on minimum VET required or purchased on secondary market.

X-Node non-fungible tokens (NFTs) were distributed upon mainnet launch but can be purchased on secondary market.

Upgrade

Upgradeable, minimum threshold of next tier applies.

Upgradeable, minimum threshold of next tier applies.

Revoke

VET drops below current level minimum threshold then node level gets downgraded.

Unclaimed VTHO can be claimed.

VET drops below current level minimum threshold then Node token loses X status and becomes an Economic Node. VeThorX node in this case gets destroyed as lowest X level node Unclaimed VTHO can be claimed.

Node
Requirement
Staking Bonus
Maturity Period
Voting Tier

1,000,000 VET

10 days

1 EN Votes

5,000,000 VET

20 days

5 EN Votes

15,000,000 VET

30 days

15 EN Votes

600,000 VET

25%

-

1 XN Votes

1,600,000 VET

100%

30 days

3 XN Votes

5,600,000 VET

150%

60 days

10 XN Votes

15,600,000 VET

200%

90 days

26 XN Votes

Full Nodes

Full nodes can be deployed by anybody by running an instance of the VeChainThor node software, and they support the network in a few fundamental ways. Full nodes, once fully synced, can relay new transactions into the network for AMs to build into blocks. Full nodes also enable people to query the VeChainThor blockchain and get the blockchain data from the chain to other systems to be processed. They also increase resiliency as they have a complete copy of the blockchain history stored.

See a full list of the publicly available VeChainThor nodes in the Developer Resource article Nodes

PreviousMainnetNextNode Rewards Programme

Last updated 1 month ago

Was this helpful?

Strength

Thunder

Mjolnir

VeThor X

Strength X

Thunder X

Mjolnir X

Interested in operating a public Thor node, here's a link to the public repo , and a link to a tutorial on how to run a local Thor node How to run a Thor Solo Node.

https://github.com/vechain/thor