SatoshiChain
  • What is SatoshiChain?
    • 1.1 Phases
    • 1.2 Connect To SatoshiChain
    • 1.3 Solutions
    • 1.4 Characteristics
  • Main Features
    • 2.1 'Clique' Proof-of-Authority (PoA) Consensus
    • 2.2 EVM-compatible
    • 2.3 Decentralized Governance
    • 2.4 Cross-chain Compatibility
  • Background
    • 3.1 Cryptographic Hash Functions
    • 3.2 Digital Signatures
      • 3.2.1 Secp256k1 Curve
      • 3.2.2 ECDSA Signature Algorithm
    • 3.3 Ethereum Virtual Machine (EVM)
    • 3.4 Consensus Protocols
      • 3.4.1 Proof-of-Work (PoW) - Nakamoto Consensus
      • 3.4.2 Istanbul Byzantine Fault Tolerant (IBFT)
      • 3.4.3 IBFT Proof of Authority (PoA)
      • 3.4.4 IBFT Proof-of-Stake (PoS)
      • 3.4.5 RAFT
      • 3.4.6 'Clique' Proof-of-Authority (PoA)
      • 3.4.7 Comparison and Selection
  • Developers
    • 4.1 SatoshiChain Layering Architecture
    • 4.2 SatoshiChain Cross-Chain Protocol
    • 4.3 SatoshiChain Design
    • 4.4 Native Currency of SatoshiChain: The $SC Token
    • 4.5 SatoshiChain Configurations
  • VE Model for SatoshiChain
    • 5.1 Voting Power
    • 5.2 How to Use $veSC
  • Smart Contracts of SatoshiChain
    • 6.1 Validator Set Contract
    • 6.2 Slashing Contract
    • 6.3 Staking Contract
    • 6.4 Governance Contract
    • 6.5 Vault Contract
    • 6.6 Bridge Contract
  • SatoshiChain Staking
  • SatoshiX Decentralized Exchange (DEX)
  • Potential Applications
    • 9.1 NFT
    • 9.2 DeFi
    • 9.3 GameFi
  • Become a Validator Node Operator
Powered by GitBook
On this page
  1. Smart Contracts of SatoshiChain

6.2 Slashing Contract

SatoshiChain adopts a slashing methodology similar to the one used by the Binance Smart Chain. In addition to enhancing the security of the SatoshiChain chain, slashing is used to safeguard its on-chain governance mechanisms from malicious or dishonest behavior via disciplinary actions. SatoshiChain slash evidence can be submitted by anyone. It’s worth noting that each transaction submission demands a slashing proof and is subject to fees. That said, it also produces a higher reward if it is successful. Two types of slashing behaviors are considered below:

  • Double-Signing: Let us assume that two different block headers have the same height and the same parent block hash. If these two block headers are sealed by the same validator and different signatures are created, then this validator will be slashed and banned permanently.

  • Unavailable: If a validator misses 48 blocks per 24 hours, it will be unable to receive rewards from the block fees. If a validator misses more than 96 blocks for 24 hours, the validator will be punished for 10,000 $SC tokens and will be jailed for 3 days. During jail time, it will still be able to produce or validate blocks.

Previous6.1 Validator Set ContractNext6.3 Staking Contract

Last updated 2 years ago