laconicd-deprecated/docs/architecture/README.md
yihuang 7f70429ac2
docs: ADR-002 EVM hooks ()
* Add adr-002 evm hooks proposal

* add bank send hook example

* fix typo

* add more details to the adr

* polishes

* add comments and missing sections

* explain the error translation

* update working, add consequences

* add reference to staking module hooks

* add ApplyTransaction snippet
2021-09-01 06:11:52 -04:00

39 lines
1.3 KiB
Markdown

<!--
order: false
parent:
order: 0
-->
# Architecture Decision Records (ADR)
This is a location to record all high-level architecture decisions in Ethermint.
You can read more about the ADR concept in this blog posts:
- [GitHub - Why Write ADRs](https://github.blog/2020-08-13-why-write-adrs/)
- [Reverb - Documenting architecture decisions, the Reverb way](https://product.reverb.com/documenting-architecture-decisions-the-reverb-way-a3563bb24bd0#.78xhdix6t)
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.
Please add a entry below in your Pull Request for an ADR.
## ADR Table of Contents
- [ADR 001: State](adr-001-state.md)
- [ADR 002: EVM Hooks](adr-002-evm-hooks.md)