laconicd/docs/architecture
Justin Thompson 3ed790b8cd
docs: fix JSON-RPC links (#558)
* RPC method docs

* forgot readme

* cleanup

* add table and fill in missing details

* update table

* fix tip block

* add the rest of the eth methods

* added the rest of the namespaces

* get rid of extra space

* doc bug fixes

* Update docs/.vuepress/config.js

* fix adr md comment

Co-authored-by: Federico Kunze <federico.kunze94@gmail.com>
Co-authored-by: Federico Kunze <31522760+fedekunze@users.noreply.github.com>
2020-10-01 03:53:42 -03:00
..
adr-template.md docs: ADR template (#536) 2020-09-24 12:36:29 -03:00
README.md docs: fix JSON-RPC links (#558) 2020-10-01 03:53:42 -03: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