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
  • Requirements for Candidate Masternode:
  • Apply to become a Masternode
  1. Masternode

Apply For SliceLedger Masternode

Apply for SliceLedger Chain Masternode with Node created before

PreviousRun a Full SliceLedger NodeNextResign as Masternode

Last updated 2 years ago

SliceLedger Chain Masternodes receive a significant amount of rewards, which exceeds the cost for running the node infrastructure. However, in order to become validator, node operator need to stake certain amount of IGT as deposit. It is required to stake 50,000 IGT to become candidate Masternode.

When the node operator stake initial deposit, it is separated as Candidate Masternode. It will not be promoted directly as Masternode status except it is in the list of top 251 Masternodes. All the Candidates need support from voters to increase their capacity to rank higher among 251 masternodes on SliceLedger Chain network. Masternodes with high capacity get higher chances of validating blocks, thus it is needed to have more voters to rank higher.

Requirements for Candidate Masternode:

Following conditions must be matched to become Candidate Masternode:

  • Up and running node.

  • The node must stake required amount of IGT Coins (50,000). These staked coins are deposited to the Validator Smart Contract.

  • It needs to be in top 251 most voted Masternode Candidates on the SliceLedger Chain network.

Apply to become a Masternode

Go to node operator dashboard, click on "" and follow the instructions. If node meets all conditions, it will be promoted to Candidate Masternode.

Become a Masternode