# IBC Application Developer Introduction
Remember the separation of concerns in the Inter-Blockchain Communication Protocol (IBC) between the transport layer (IBC/TAO) and the application layer (IBC/APP). The transport layer provides the basic infrastructure layer to transport, authenticate, and order arbitrary packets of data. The encoding, decoding, and interpretation of the data to trigger the custom application logic is then up to the application layer. The examples of token transfer sent over IBC implicitly used the ICS-20 or transfer IBC application module provided by the ibc-go SDK module (which also provides the core transport layer functionality).
In the following sections, you will learn how to develop your custom IBC application modules, either by upgrading an existing module or starting from scratch using Ignite CLI.
In the integration (opens new window) section of the IBC documentation, the necessary steps to integrate IBC in a Cosmos SDK chain are outlined.
Note that this does not mean that the main application modules turn into IBC modules, it only means IBC is enabled for the chain. The IBC module has come out-of-the-box in Cosmos SDK chains since the 0.40.x version of the SDK, so it is unlikely you will have to implement these steps manually when developing a chain.
For example, the checkers blockchain you developed in the previous section is IBC-enabled. This is revealed when trying to send IBC denoms from other chains in order to set a wager. However, this does not make the
x/checkers module an IBC-enabled module. You will investigate all the additions required to make the module IBC-enabled in what follows.
# Structure of the sections to come
In this part of the chapter, you will first investigate the code you have to add to make a module IBC-enabled. For this conceptual example, you will build a simple chain from scratch with Ignite CLI. Ignite CLI provides the option to scaffold an IBC module, which does all of the hard work in terms of boilerplate code. Still, it makes sense to take a look at what exactly has changed. Therefore, you will compare the code with a git diff when scaffolding a chain with a regular module and when you scaffold an IBC module.
A similar approach will be taken to check what Ignite CLI implements when scaffolding an IBC packet.
After finishing the conceptual part, you are going to expand the checkers blockchain you created to include an IBC module in it, and will create an additional leaderboard blockchain to act as a separate appchain that can interact via IBC with the checkers blockchain.
Let's dive into it!