certusone
/
cosmos-sdk
mirror of https://github.com/certusone/cosmos-sdk.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: change abci++ -> abci 1.0 (#13322) 

* change abci++ -> abci 1.0

* file change
This commit is contained in:
Marko 2022-09-16 17:35:23 +02:00 committed by GitHub
parent d04392c5e2
commit 73debf46d9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/architecture/README.md
View File

@ -82,7 +82,7 @@ When writing ADRs, follow the same best practices for writing RFCs. When writing
* [ADR 046: Module Params](./adr-046-module-params.md) * [ADR 046: Module Params](./adr-046-module-params.md)
* [ADR 057: App Wiring Part I](./adr-057-app-wiring-1.md) * [ADR 057: App Wiring Part I](./adr-057-app-wiring-1.md)
* [ADR 059: Test Scopes](./adr-059-test-scopes.md) * [ADR 059: Test Scopes](./adr-059-test-scopes.md)
* [ADR 060: ABCI++ (Phase I)](./adr-060-abci%2B%2B-phase-i.md) * [ADR 060: ABCI 1.0](adr-060-abci-1.0.md)
### Draft ### Draft

22
docs/architecture/adr-060-abci++-phase-i.md → docs/architecture/adr-060-abci-1.0.md
View File

@ -1,4 +1,4 @@
# ADR 60: ABCI++ (Phase I) # ADR 60: ABCI 1.0 Integration
## Changelog ## Changelog
@ -10,15 +10,15 @@ PROPOSED
## Abstract ## Abstract
This ADR describes the initial adoption of [ABCI++](https://github.com/tendermint/tendermint/blob/master/spec/abci%2B%2B/README.md), This ADR describes the initial adoption of [ABCI 1.0](https://github.com/tendermint/tendermint/blob/master/spec/abci%2B%2B/README.md),
the next evolution of ABCI, within the Cosmos SDK. ABCI++ aims to provide the next evolution of ABCI, within the Cosmos SDK. ABCI 1.0 aims to provide
application developers with more flexibility and control over application and application developers with more flexibility and control over application and
consensus semantics, e.g. in-application mempools, in-process oracles, and consensus semantics, e.g. in-application mempools, in-process oracles, and
order-book style matching engines. order-book style matching engines.
## Context ## Context
Tendermint will release ABCI++ in phases. Notably, at the time of this writing, Tendermint will release ABCI 1.0. Notably, at the time of this writing,
Tendermint is releasing v0.37.0 which will include `PrepareProposal` and `ProcessProposal`. Tendermint is releasing v0.37.0 which will include `PrepareProposal` and `ProcessProposal`.
The `PrepareProposal` ABCI method is concerned with a block proposer requesting The `PrepareProposal` ABCI method is concerned with a block proposer requesting
@ -35,16 +35,16 @@ The second ABCI method, `ProcessProposal`, is used to process the block proposer
proposal as defined by `PrepareProposal`. This ABCI method requests that the proposal as defined by `PrepareProposal`. This ABCI method requests that the
application evaluate the entire proposed block for validity. application evaluate the entire proposed block for validity.
It is important to note that in this phase of ABCI++ integration, the application It is important to note that in ABCI 1.0 integration, the application
is NOT responsible for locking semantics -- Tendermint will still be responsible is NOT responsible for locking semantics -- Tendermint will still be responsible
for that. In the future, however, the application will be responsible for locking, for that. In the future, however, the application will be responsible for locking,
which allows for parallel execution possibilities. which allows for parallel execution possibilities.
## Decision ## Decision
We will integrate the first phase of ABCI++, which will be introduced in Tendermint We will integrate ABCI 1.0, which will be introduced in Tendermint
v0.37.0, in the next major release of the Cosmos SDK. We will integrate the two v0.37.0, in the next major release of the Cosmos SDK. We will integrate ABCI 1.0
aforementioned ABCI++ methods on the `BaseApp` type. We describe the implementations methods on the `BaseApp` type. We describe the implementations
of the two methods individually below. of the two methods individually below.
Prior to describing the implementation of the two new methods, it is important to Prior to describing the implementation of the two new methods, it is important to
@ -210,9 +210,9 @@ case `ProcessProposal` fails.
### Backwards Compatibility ### Backwards Compatibility
ABCI++ is naturally not backwards compatible with prior versions of the Cosmos SDK ABCI 1.0 is naturally not backwards compatible with prior versions of the Cosmos SDK
and Tendermint. For example, an application that requests `RequestPrepareProposal` and Tendermint. For example, an application that requests `RequestPrepareProposal`
to the same application that does not speak ABCI++ will naturally fail. to the same application that does not speak ABCI 1.0 will naturally fail.
However, in the first phase of the integration, the existing ABCI methods as we However, in the first phase of the integration, the existing ABCI methods as we
know them today will still exist and function as they currently do. know them today will still exist and function as they currently do.
@ -220,7 +220,7 @@ know them today will still exist and function as they currently do.
### Positive ### Positive
* Applications now have full control over transaction ordering and priority. * Applications now have full control over transaction ordering and priority.
* Lays the groundwork for the full integration of ABCI++, which will unlock more * Lays the groundwork for the full integration of ABCI 1.0, which will unlock more
app-side use cases around block construction and integration with the Tendermint app-side use cases around block construction and integration with the Tendermint
consensus engine. consensus engine.