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
  1. SLICE Token

Utility

Secure the Network:

The primary utility of SLICE token is to secure the SliceLedger Chain network with using Proof-of-Stake system. In order to run SliceLedger Node and participate in securing the network, validator must hold 50,000 SLICE and voters have to lock up their SLICE to any validator node to increase node capacity. In exchange for participation, validator and voter both receive rewards in SLICE after every transaction.

Network fees:

SLICE is used to pay for network fees such as transaction fees, smart contract deployment and other networks activities. The fees on SliceLedger Chain network is extremely cheap compared to other blockchain networks. However, lower fees does not compromise network states as it sets limitations to suspicious activities via SLICE privacy protocol.

Payments

SLICE is ideal for crypto currency payments to enterprises and businesses all around the world. It offers very quick and low-cost transactions compared to other crypto payment options. As the network eligible to process 100,000 transactions per second (TPS), depending on the number of validator nodes, SliceLedger Chain is high throughput and affordable blockchain network to every user.

Governance

As being native token, SLICE is used in SliceLedger on-chain governance. SliceLedger Chain is a fully decentralized network, hence any decision on the network is carried out by on-chain governance process. SLICE holders can propose and vote for changes and improvements by staking their tokens.

PreviousTechnicalNextCoin Distribution

Last updated 2 years ago