laconicd/docs/architecture
yihuang 7f70429ac2
docs: ADR-002 EVM hooks (#429)
* 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
..
adr-001-state.md evm, rpc: fix parameters and block gas limit in getBlockByHeight and getBlockByHash (#312) 2021-07-19 01:52:44 +00:00
adr-002-evm-hooks.md docs: ADR-002 EVM hooks (#429) 2021-09-01 06:11:52 -04:00
adr-template.md ADR 001: State (#26) 2021-05-17 18:36:41 -04:00
README.md docs: ADR-002 EVM hooks (#429) 2021-09-01 06:11:52 -04:00

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:

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