Docs - SliceLedger
  • What is Slice Ledger?
  • SliceLedger Key Features
  • SliceLedger Wallet
    • SliceLedger Crypto Wallet
      • Slice Web Extension
    • SliceLedger Explorer
    • SliceLedger DEX
    • SliceLedger NFT Market
  • Sliceledger Chain Network
    • Sliceledger Chain Mainnet
    • Sliceledger Chain Testnet
    • CLI Commands
    • Audit
    • Slice Faucet
  • Integrating Metamask
    • Add SliceLedger Chain Network to Metamask
    • Config Custom Token
    • How to Reset Metamask Wallet
  • Slice Ledger Protocols
    • SLICE Game
    • SLICE Reward
    • SLICE Privacy
  • SliceLedger Exclusive Products
    • Bharat NFT Marketplace
    • Bharat Token
    • Slice Crypto Wallet
    • Slice Wallet Extension
    • Bouquet NFT Collection
  • Enterprise Blockchain
    • Diamond Industry
  • SLICE Token
    • Technical
    • Utility
    • Coin Distribution
  • Developer Guide
    • Token Standards
      • SLICE-20 Tokens
      • SLICE-721 Tokens
    • Verify Smart Contract
  • Masternode
    • Masternode Requirements
    • Masternode Setup Guide
    • Run a Full SliceLedger Node
    • Apply For SliceLedger Masternode
    • Resign as Masternode
  • API
    • accounts
    • blockNumber
    • call
    • chainId
    • estimateGas
    • gasPrice
    • getBalance
    • getBlockByHash
    • getBlockByNumber
    • getBlockTransactionCountByHash
    • getBlockTransactionCountByNumber
    • getCode
    • getLogs
    • getStorageAt
    • getTransactionByBlockHashAndIndex
    • getTransactionByBlockNumberAndIndex
    • getTransactionByHash
    • getTransactionCount
    • getTransactionReceipt
    • getUncleByBlockHashAndIndex
    • getUncleByBlockNumberAndIndex
    • getUncleCountByBlockHash
    • getUncleCountByBlockNumber
    • getWork
    • hashrate
    • mining
    • protocolVersion
    • sendRawTransaction
    • submitWork
    • syncing
    • net_listening
    • net_peerCount
    • net_version
    • web3_clientVersion
    • parity_nextNonce
    • Filter methods
    • newFilter
    • newBlockFilter
    • getFilterChanges
    • uninstallFilter
  • Deploying on SliceLedger Chain
    • Using Remix
    • Using Truffle
    • Using Hardhat
Powered by GitBook
On this page
  • Hardware requirements to run SliceLedger Masternode:
  • Knowledge Required
  • Maintenance
  1. Masternode

Masternode Requirements

Requirements to run SliceLedger Masternode

Hardware requirements to run SliceLedger Masternode:

The process of signing blockchain transactions requires highly efficient hardware and processing power which are more reliable for running a Masternode.

· Directly facing internet (public IP, no NAT)

Using popular cloud providers are recommended as it is more reliable with uptime close to 100%. These servers would be a good starting point:

  • DigitalOcean: CPU optimized droplet 32GB/16CPU

  • Amazon EC2: C5 instance

  • Google Cloud Engine: n1-highcpu-16

Choosing weaker machine for running Masternode operations might result in poor performances, significantly impacting owner's rewards and chain performance.

Knowledge Required

  • VPS Setup - Ability to setup a cloud-hosted virtual private server (VPS)

  • Linux familiarity - A basic knowledge of how to SSH-into (ex: putty or terminal) and operate the Linux command-line.

Maintenance

Maintenance is necessary for every Masternode. It is node operator's responsibility to ensure regular maintenance. Make sure:

  • To have enough disk space to update and store latest data

  • It has ample processing power to keep the chain operating at optimal speed

  • System is secure and using latest version of security applications and OS

PreviousMasternodeNextMasternode Setup Guide

Last updated 2 years ago