BitSong
  • Introduction
  • Delegators
    • Delegator FAQ
    • Delegator Security
  • Validators
    • Validator Overview
    • Validator FAQ
    • Validator Security
  • Relayer
  • FAQ
  • Glossary
  • Roadmap
  • Media Kit
  • Links
  • Blockchain
    • Install go-bitsong
    • Join the Mainnet
    • Create Validator
    • CLI Guide
    • Gas and Fees
    • Pruning of State
    • Export the state
    • Verify Mainnet
    • Upgrades
      • From v0.8.0 to v0.10.0
      • From v0.10.0 to v0.11.0
      • From v0.12.x to v0.13.0
      • From v0.13.x to v0.14.0
      • From v0.14.x to v0.15.0
      • From v0.17.0 to v0.18.0
  • Features and Modules
    • Fan Tokens
    • Merkledrop
    • NFTs
    • Marketplace
    • CosmWasm
      • Install rust
      • Deploy a Smart Contract
    • IBC
    • Auth
    • Bank
    • Crisis
    • Capability
    • Community Pool
    • Distribution
    • Evidence
    • Governance
    • Mint
    • Staking
    • Slashing
    • Upgrade
  • BTSG
    • What is BTSG ?
    • Distribution and Tokenomics
    • Wallets
    • Buy and Sell
    • Liquidity Provider
  • Developers
    • bitsongJS
  • PRODUCTS
    • Sinfonia
    • BitSong Studio
  • USEFUL GUIDES
    • How to Create a BitSong wallet
    • How to Import Your BitSong Wallet
    • How to Stake $BTSG
    • How to Add $BTSG Liquidity to Osmosis Pools
    • Sinfonia User's Guide
    • How to Report a Bug on Sinfonia
  • Global Ambassador Program
    • Who is an ambassador?
    • Program Rules
Powered by GitBook
On this page
  1. Features and Modules

Evidence

PreviousDistributionNextGovernance

Last updated 3 years ago

Evidence is an implementation of a Cosmos SDK module, per , that allows for the submission and handling of arbitrary evidence of misbehavior such as equivocation and counterfactual signing.

The evidence module differs from standard evidence handling which typically expects the underlying consensus engine, e.g. Tendermint, to automatically submit evidence when it is discovered by allowing clients and foreign chains to submit more complex evidence directly.

All concrete evidence types must implement the Evidence interface contract. Submitted Evidence is first routed through the evidence module's Router in which it attempts to find a corresponding registered Handler for that specific Evidence type. Each Evidence type must have a Handler registered with the evidence module's keeper in order for it to be successfully routed and executed.

Each corresponding handler must also fulfill the Handler interface contract. The Handler for a given Evidence type can perform any arbitrary state transitions such as slashing, jailing, and tombstoning.

ADR 009