# Transfer middleware

## Definitions
Middleware: A self-contained module that sits between core IBC and an underlying IBC application during packet execution. All messages between core IBC and underlying application must flow through middleware, which may perform its own custom logic.

In this case, the IBC application is `transfer` module in ibc-go.

## How is it working
As we want a shared total supply between Banksy and Picasso, token transfers from Picasso to Banksy via IBC will not have the `ibc/` denom prefix. Instead, the native token in Picasso, PICA, should be used.

We have introduced an IBC middleware module to lock `ibc/` tokens and mint native tokens. This module handles middleware processes when executing the ICS26 implementation of IBC transfer, including SendPacket, OnRecvPacket, OnAcknowledgementPacket, and OnTimeoutPacket.

#### Transfer and SendPacket

Scope:
- Coverage source zone, sink zone logic in IBC transfer. (about this : https://github.com/cosmos/ibc-go/blob/main/modules/apps/transfer/keeper/relay.go#L22)
- Ensure all native and ibced token will be burned when receive successful ack packet.

Current process : https://github.com/notional-labs/composable-testnet/pull/25

#### OnRecvPacket

Scope:
- Coverage source zone, sink zone logic in IBC transfer. (about this : https://github.com/cosmos/ibc-go/blob/main/modules/apps/transfer/keeper/relay.go#L22)

#### OnAcknowledgementPacket
Same with OnRecvPacket. I'll write more description for this

#### OnTimeoutPacket
Same with OnRecvPacket. I'll write more description for this