The next sections are all about creating a decentralized game of checkers (see the rules here (opens new window)) using Ignite CLI and the Cosmos SDK. Each section progressively advances the project. To learn the most efficiently, you should treat each section as a solution to the questions raised at the start of the section.
These exercises help you prepare a conceptual framework for the information that follows. You are not tested on them, but it is in your best interest to complete each one before moving on to the associated section.
Although the guided coding exercises use Cosmos SDK v0.45.4, the current release is at v0.47.2. In addition, v0.50 is imminent, and will feature the following:
EndBlock
disappears as a module function and is replaced by another while keeping the same conceptual capability.bech32
removal: currently bech32 prefixes are a global in the Cosmos SDK and for applications as well. The objective is to remove most if not all globals within the SDK.GetSigners
: as GetSigners
is now automated, it can be removed from msg.go; an extension interface will be added for users that still need it.ValidateBasic
: with the use of ValidateBasic
considered optional, the Cosmos SDK will remove its usage in favor of having all validation happen on msg
server. The SDK will still support an extension interface for those that would like to continue using it.For a sense of the scale of the Cosmos SDK's ongoing development, you can review all the changes that have been implemented to date at this link (opens new window).