Viction
  • Getting Started
  • General
    • Overview
    • Viction Blockchain
      • PoSV Consensus
      • Comparison
    • Staking
      • Staking Requirements
      • Staking Rewards
      • How to stake on Viction Wallet
    • Network Information
      • Viction Mainnet
      • Viction Testnet
    • Viction RPC API
  • Smart Contract Development
    • Solidity
      • A Simple Smart Contract
      • Solidity by Example
    • Standards & Specification
      • VRC25 Specification
      • VRC725 Specification
    • IDEs and Tools
      • Remix
      • Ethers.js
      • web3.js
      • thirdweb CLI
    • Deployment & Verification
      • Hardhat
      • Foundry
  • DApp Development
    • Integration
      • Exchange/Wallet integration
      • VRC25 Exchange/Wallet integration
      • Viction Staking Governance
      • VIC ZeroGas
      • VRRF
    • Data and analytics
    • Embedded Wallet (MPC)
    • Walkthrough: Build a Dapp on Viction
      • Setup Environment
      • Write the Smart Contract
      • Interacting with the Dapp in a browser
  • Masternode
    • Requirements
    • Run a Full Node
      • Binary
      • Create a Viction Masternode
      • Tmn
      • Docker
    • Apply Your Node
    • Slashing Mechanism
    • Chain Data Snapshots
    • Troubleshooting
  • Viction Wallet
    • User Guide
      • Authentication
      • How to create a new wallet
      • How to restore a wallet?
      • Wallet settings
      • Send & Receive Tokens
      • Add custom token
      • Manage Tokens
      • Send NFT
      • General settings
    • Developer Guide
    • Privacy Policy
    • Term and Services
  • Viction Bridge
    • Spacegate
    • Arken Bridge
    • Hyperlane
  • Viction Data Availability
    • Viction DA RPC API
    • DA Integration Use cases
      • Simple Guide for Integrating OP Stack Rollup with Viction DA Layer
  • How to
    • How to Connect to Viction Blockchain
      • Coin98 Super Wallet
      • Metamask
      • Ledger
    • How to troubleshoot when the node is up but couldn't begin to sync block
    • How to Vote for Viction Saigon Network Upgrade Proposal
    • How to issue a token via VICIssuer
    • How to verify if a contract has been issued via VICIssuer
    • How to deploy the VRC725 contract
    • How to apply ZeroGas for VRC725 contract
    • How to Migrate Dapps from Ethereum
    • How to register Token or NFT logo on Vicscan
    • How to verify a contract on Vicscan
    • How to confirm a project on Vicscan
    • How to check if a token is gas sponsored on Viction
    • How to verify gas sponsored transactions
    • How to create Telegram Mini Apps
    • How to use VictionSafe (Multisig)
  • FAQ
    • APIs
    • General
      • Viction
      • Ecosystem
      • VIC - Economics
      • Contact & Support
    • Masternodes and Voting
      • Masternodes
      • Voter
    • Products
      • VicScan (Explorer)
      • VicMaster
      • VicStats
      • VicIssuer
        • How to Verify & Publish Contract Source Code on VicScan
      • Viction Wallet
      • Viction Data Availability Network
  • Legal
    • Terms of Use
    • Privacy Policy
  • Whitepaper and Research
  • Archive
    • TOMOE
    • How to Deploy a VRC25 Token on Viction
    • How to deploy an ICO smart contract on Viction
    • How to deploy an NFT token
    • An Example of Building a Dapp on Viction
    • Migrate Ethereum Dapp to Viction
    • TomoMasterDAO
      • Introduction
      • Governance model
        • On-Chain vs Off-Chain Voting
        • Board
        • Proposals
        • Voting and Outcome
      • Tokenomics
      • How to utilize and trade tDAO
      • Proposal guidelines for TomoMasterDAO
    • Old Viction Testnet
    • Deploy on Viction
      • CLI Commands
      • Viction Private Testnet Setup
Powered by GitBook
On this page
  • General System Specs
  • Recommendation
  • Maintenance
  1. Masternode

Requirements

Hardware specification for running a Viction Mainnet node.

General System Specs

Minimum requirements

  • CPU: 2 cores

  • RAM: 8 GB

  • SSD: 1 TB

  • Network: 10 Mb/s

Full node requirements

  • CPU: 4 cores

  • RAM: 16 GB

  • SSD: 1 TB

  • Network: 25 Mb/s

Masternode requirements

  • CPU: 8 cores

  • RAM: 16 GB

  • SSD: 1 TB

  • Network: 25 Mb/s

Archive node requirements

  • CPU: 16-64 cores

  • RAM: 32 GB

  • SSD: 4 TB

  • Network: 25 Mb/s

The requirements above are for typical workload and cannot cover all workloads. These are good starting points to adjust node specifications to fit with your workload.

As of December 2024, the size of blockchain data is:

  • Full node: 900 GB

  • Archive node: 3743 GB

Recommendation

We recommend using popular cloud providers as their reliability and uptime are close to 100%. These servers would be a good starting point:

  • Amazon EC2: C5 instance

  • DigitalOcean: CPU optimized droplet 16GB/8vCPU

  • Google Cloud Engine: n2d-standard-8

Setting up a Masternode Candidate on a low specs machine might result in poor performances, significantly impacting owner's rewards and the chain performance.

Notice

A Masternode has a certain number of tasks to process (validations, block creations, etc.) over time. Your Masternode should be able to process all the tasks that are designated to it, or the rewards will be negatively impacted. However, overpowered technical specifications of the Masternode will not result in greater rewards.

Maintenance

All IT systems require maintenance.

It is of the owner's responsibility to ensure regular maintenance, and that the node has enough:

  • Disk space to store the new blockchain data.

  • Processing power to keep the chain operating at optimal speed.

  • Monitoring to be able to react quickly in case of a problem occurring.

  • Security measures like firewalling, OS security patching, SSH via keypairs, etc.

This is a non-exhaustive list.

PreviousMasternodeNextRun a Full Node

Last updated 3 months ago