order |
---|
1 |
Lastest update: Dec 22, 2021
This document endeavours to inform the wider IBC community about plans and priorities for work on ibc-go byt the team at Interchain GmbH. It is intended to broadly inform all users of ibc-go, including developers and operators of IBC, relayer, chain and wallet applications.
This roadmap should be read as a high-level guide, rather than a commitment to schedules and deliverables. The degree of specificity is inversely proportional to the timeline. We will update this document periodically to reflect the status and plans.
The release tags and timelines are educated guesses based on the information at hand at the moment of updating this document. Since predicting the final version number (specially for minor and patch numbers) can be challenging (since we might need to release unforeseen security vulnerability patches or urgent bug fixes), we are using alphabet letters as placeholders. Once we get closer to the release date, the placeholder will be replaced with the right number. An example for clarification...
Let's assume that the planned release schedule looks like the following:
- At time
t0
:- The first planned patch release for the
v2.0.x
release series with release tagv2.0.a
. The placeholder isa
since this is the first patch release in the given quarter. - The first planned minor release for the
v2.x
release series with release tagv2.a.0
. The placeholder isa
since this is the first minor release in the given quarter.
- The first planned patch release for the
- At time
t0 + delta
:- The second planned patch release for the
v2.0.x
release series with release tagv2.0.b
. The placehoder isb
since this is the next patch release of this release series afterv2.0.a
in the given quarter. - The first planned patch release for the new
v2.a.x
release series with release tagv2.a.a
. The patch version placeholder isa
because this is the first planned patch release of the series in the given quarter.
- The second planned patch release for the
- Work on any issues that may come out of the two external audits.
- Create beta, release candidate and final releases.
- Work on issues that may arise from internal audit.
- External audit (issues may arise that we need to work on before release).
- Create alpha, beta, release candidate and final release.
There is an open PR that implements support for Wasm-based light clients, but it needs to be updated after the finalization of the ICS28 specification. The PR will also need a final review from ibc-go core team members.
- Testnet testing of V1.
- #545: Remove the
GetTransferAccount
function, since we never use the ICS20 transfer module account (every escrow address is created as a regular account). - #559: Changes needed to support the migration to SMT storage. This is basically adding a new proof spec that will be used during connection handshake with a chain that has migrated to SMT to verify that the light client of the counterparty chain uses the correct proof specs to be able to verify proofs for that chain.
- And more to be added later!
v3.0.0-beta
: Beta release ofv3.0.0
including Interchain Accounts, an update of Golang fromv1.15
tov1.17
, and some core improvements. This is a Go-API breaking change because of #472.
v2.0.a
v3.0.0-rc0
: Release candidate 0 ofv3.0.0
including Interchain Accounts, an update of Golang fromv1.15
tov1.17
, and some core improvements. This is a Go-API breaking change because of #472.v4.0.0-alpha
: Alpha release ofv4.0.0
including Relayer Incentivisation and the issues to bring ibc-go implementation in line with ICS02 (which are Go-API breaking changes). This release will include fixes to issues that surfaced during internal audit.
v3.0.0
: Final release ofv3.0.0
including Interchain Accounts, an update of Golang fromv1.15
tov1.17
, and some core improvements. This is a Go-API breaking change because of #472.
v4.0.0-beta
: Beta release ofv4.0.0
including Relayer Incentivisation and the issues to bring ibc-go implementation in line with ICS02 (which are Go-API breaking changes). This release will include fixes to issues that surfaced during external audit.
v4.0.0-rc0
: Release candidate 0 ofv4.0.0
including Relayer Incentivisation and the issues to bring ibc-go implementation in line with ICS02 (which are Go-API breaking changes).
v4.0.0
: Final release ofv4.0.0
including Relayer Incentivisation and the issues to bring ibc-go implementation in line with ICS02 (which are Go-API breaking changes).v1.a.0
: Minor release inv1.x
seires including the update of Cosmos SDK tov0.46
and Tendermint tov0.35
.v2.a.0
: Minor release inv2.x
series including the update of Cosmos SDK tov0.46
and Tendermint tov0.35
.v3.a.0
: Minor release inv3.x
series including the update of Cosmos SDK tov0.46
and Tendermint tov0.35
.v4.a.0
: Minor release inv4.x
series including the update of Cosmos SDK tov0.46
and Tendermint tov0.35
.
Scope is still TBD.
v5.0.0-rc0
: Release candidate that includes the update of Cosmos SDK fromv0.46
tov1.0
and that will support the migration to SMT storage.