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

Enterprise Blockchain

PreviousBouquet NFT CollectionNextDiamond Industry

Last updated 2 years ago

A permissioned blockchain known as a "enterprise blockchain" can be used to scale up commercial procedures like tracking supplies or settling international payments.

How is an enterprise blockchain different from other types?

Enterprise blockchains differ in the following areas:

  • Level of decentralization

  • Security

1. Private (Permissioned) Blockchain

Private blockchains are closed networks accessible only to users the central authority has authorised. Private blockchains, in contrast to public blockchains, depend on a central node to verify transactions. Who can participate in the system and what data is allowed may also be decided by this node.

2. Hybrid Blockchain

Blockchain networks that integrate private and public chains have hybrid properties. The end result is a solution that fixes the issues that both blockchain systems have while keeping their advantages.

On a hybrid blockchain, data integrity is higher because the owner cannot change data without other nodes' consent. Additionally, hybrid networks are more secure due to the distributed consensus among all network nodes.

3. Consortium Blockchain

Consortium blockchains are similar to public blockchains in that they have a decentralised, peer-to-peer structure. Every member of the network has a copy of the distributed ledger, and no one entity has exclusive control over the system.

How is an enterprise blockchain different from other types?

A vast majority of enterprise blockchains are "," meaning companies have direct control over them. For instance, they can block transactions that do not comply with their rules, or if law enforcement asks them to do so.

Some of the main characteristics of enterprise blockchains include:

  • Accountability: Each node in the network – which each holds a copy of the transaction history – is known and can be held accountable for its actions. For example, often enterprise blockchains are shared by a few companies or financial entities in a cooperative format.

  • Permissioned: Only users who have permission can use the blockchain. The network owner(s) can choose who's allowed to use it and who's not.

  • Mutable: If all entities managing the network agree, the data can be changed.

  • Scalability: Because enterprise blockchains are typically not as decentralized as Bitcoin, they can easily support more transactions at the base layer.

permissioned blockchains