mirror of
https://github.com/tendermint/tendermint.git
synced 2026-01-03 03:35:19 +00:00
e30b125725
Implementation spec of Double Signing Risk Reduction [ADR-51](https://github.com/tendermint/tendermint/blob/master/docs/architecture/adr-051-double-signing-risk-reduction.md) by B-Harvest - Add `DoubleSignCheckHeight` config variable to ConsensusConfig for "How many blocks looks back to check existence of the node's consensus votes when before joining consensus" - Add `consensus.double_sign_check_height` to `config.toml` and `tendermint node` as flag for set `DoubleSignCheckHeight` - Set default `consensus.double_sign_check_height` to `0` ( it could be adjustable in this PR, disable when 0 ) Refs - [ADR-51](https://github.com/tendermint/tendermint/blob/master/docs/architecture/adr-051-double-signing-risk-reduction.md) - [https://github.com/tendermint/tendermint/issues/4059](https://github.com/tendermint/tendermint/issues/4059) - [https://github.com/tendermint/tendermint/pull/4262](https://github.com/tendermint/tendermint/pull/4262)
order, parent
| order | parent | ||
|---|---|---|---|
| 1 |
|
Architecture Decision Records (ADR)
This is a location to record all high-level architecture decisions in the tendermint project.
You can read more about the ADR concept in this blog post.
An ADR should provide:
- Context on the relevant goals and the current state
- Proposed changes to achieve the goals
- Summary of pros and cons
- References
- Changelog
Note the distinction between an ADR and a spec. The ADR provides the context, intuition, reasoning, and justification for a change in architecture, or for the architecture of something new. The spec is much more compressed and streamlined summary of everything as it stands today.
If recorded decisions turned out to be lacking, convene a discussion, record the new decisions here, and then modify the code to match.
Note the context/background should be written in the present tense.
Table of Contents:
- ADR-001-Logging
- ADR-002-Event-Subscription
- ADR-003-ABCI-APP-RPC
- ADR-004-Historical-Validators
- ADR-005-Consensus-Params
- ADR-006-Trust-Metric
- ADR-007-Trust-Metric-Usage
- ADR-008-Priv-Validator
- ADR-009-ABCI-Design
- ADR-010-Crypto-Changes
- ADR-011-Monitoring
- ADR-012-Peer-Transport
- ADR-013-Symmetric-Crypto
- ADR-014-Secp-Malleability
- ADR-015-Crypto-Encoding
- ADR-016-Protocol-Versions
- ADR-017-Chain-Versions
- ADR-018-ABCI-Validators
- ADR-019-Multisigs
- ADR-020-Block-Size
- ADR-021-ABCI-Events
- ADR-022-ABCI-Errors
- ADR-023-ABCI-Propose-tx
- ADR-024-Sign-Bytes
- ADR-025-Commit
- ADR-026-General-Merkle-Proof
- ADR-028-libp2p
- ADR-029-Check-Tx-Consensus
- ADR-030-Consensus-Refactor
- ADR-030-Changelog-structure
- ADR-033-Pubsub
- ADR-034-Priv-Validator-File-Structure
- ADR-035-Documentation
- ADR-037-Deliver-Block
- ADR-038-non-zero-start-height
- ADR-039-Peer-Behaviour
- ADR-041-Proposer-Selection-via-ABCI
- ADR-043-Blockchain-RiRi-Org
- ADR-044-Lite-Client-With-Weak-Subjectivity
- ADR-045-ABCI-Evidence
- ADR-046-Light-Client-Implementation
- ADR-047-Handling-Evidence-From-Light-Client
- ADR-051-Double-Signing-Risk-Reduction
- ADR-052-Tendermint-Mode
- ADR-053-State-Sync-Prototype
- ADR-054-crypto-encoding-2
- ADR-055-protobuf-design
- ADR-056-proving-amnesia-attacks
- ADR-057-RPC
- ADR-058-event-hashing