Architecture Decision Records (ADR)

This is a location to record all high-level architecture decisions in the Interchain Security 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 is or should be.

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.

To suggest an ADR, please make use of the ADR template provided.

Table of Contents

ADR #	Description	Status
001	Consumer chain key assignment	Accepted, Implemented
002	Jail Throttling	Accepted, Implemented
003	Equivocation governance proposal	Accepted, Implemented
004	Denom DOS fixes	Accepted, Implemented
005	Cryptographic verification of equivocation evidence	Accepted, In-progress
007	Pause validator unbonding during equivocation proposal	Proposed
008	Throttle with retries	Accepted, In-progress
009	Soft Opt-out	Accepted, Implemented
010	Standalone to Consumer Changeover	Accepted, Implemented
011	Improving testing and increasing confidence	Proposed
012	Separate Releasing	Proposed
013	Slashing on the provider for consumer equivocation	Proposed