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 planning. - 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 planning.
- 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 planning. - 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 thev2.a.x
release series.
- 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.
- 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!
Release | Milestone | Date |
---|---|---|
v3.0.0-alpha2 |
Jan 07, 2021 |
During this quarter we will also probably release versions that bump the Cosmos SDK to v0.45
and Tendermint to v0.35
, but at the moment of writing it is difficult to estimate when. Check our roadmap regularly for updates.
v2.0.a
v3.0.0-beta1
: Beta 1 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 release because of #472 and #675.
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 release because of #472 and #675.
v3.a.0-alpha1
: Alpha release ofv3.a.0
including Relayer Incentivisation. This release will include fixes to issues that surfaced during the 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 release because of #472 and #675.v3.a.0-beta1
: Beta release ofv3.a.0
including Relayer Incentivisation. This release will include fixes to issues that surfaced during the external audit.
v3.a.0-rc0
: Release candiate 0v3.1.0
including Relayer Incentivisation.
Full scope still TBD.
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 need thorough review, more tests and potentially implementation changes.
During this quarter we will also probably release versions that bump the Cosmos SDK to v0.46
and to v1.0
, but at the moment of writing it is difficult to estimate when. Check our roadmap regularly for updates.
v3.a.0
: Final release ofv3.a.0
including Relayer Incentivisation.v4.0.0-rc0
: Release candidate 0 ofv4.0.0
including the work for the issues to bring ibc-go implementation in line with ICS02 (which are Go-API breaking changes).
v4.0.0
: Release candidate 0 ofv4.0.0
including the work for the issues to bring ibc-go implementation in line with ICS02 (which are Go-API breaking changes).