This is a location to record all high-level architecture decisions in the Cronos implementation.
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.
| ADR # | Description | Status |
|---|---|---|
| 001 | Disable Gravity Bridge at Genesis | Accepted |
| 002 | Use a custom fork of ibc-go | Accepted |
| 003 | Add Fee Market Module | Accepted |
| 004 | Tokens conversion in Cronos | Accepted |
| 005 | Cross-chain Validation for Gravity Bridge | Rejected |
| 006 | Migrating CRC20 contract to CRC21 standard | Rejected |
| 007 | Generic event format for evm-hook actions | Accepted |
| 008 | Denom and Contract Mapping Enhancement for Bi-Directional Token Conversion | Accepted |
| 009 | Permissioned addresses in Cronos | Accepted |