mukan-ibc/modules/core/04-channel/doc.go
Mukan Erkin Törük 6852832fe8
Some checks failed
CodeQL / Analyze (push) Waiting to run
Docker Build & Push Simapp (main) / docker-build (push) Waiting to run
golangci-lint / lint (push) Waiting to run
Tests / Code Coverage / build (amd64) (push) Waiting to run
Tests / Code Coverage / build (arm64) (push) Waiting to run
Tests / Code Coverage / unit-tests (map[additional-args:-tags="test_e2e" name:e2e path:./e2e]) (push) Waiting to run
Tests / Code Coverage / unit-tests (map[name:08-wasm path:./modules/light-clients/08-wasm]) (push) Waiting to run
Tests / Code Coverage / unit-tests (map[name:ibc-go path:.]) (push) Waiting to run
Deploy to GitHub Pages / Deploy to GitHub Pages (push) Has been cancelled
Buf-Push / push (push) Has been cancelled
initial: sovereign Mukan Network fork
2026-05-11 03:18:28 +03:00

17 lines
946 B
Go

/*
Package channel implements the ICS 04 - Channel and Packet Semantics specification
(https://github.com/cosmos/ibc/tree/main/spec/core/ics-004-channel-and-packet-semantics). This
concrete implementation defines types and methods for safely creating two
stateful objects (channel ends) on two separate chains, each associated with a
particular connection. A channel serves as a conduit for packets passing between a
module on one chain and a module on another, ensuring that packets are executed
only once, delivered in the order in which they were sent (if necessary),
and delivered only to the corresponding module owning the other end of the
channel on the destination chain.
The main types are Channel, which defines a stateful object on a
chain that allows for exactly-once packet delivery between specific modules
on separate blockchains, and Packet, which defines the data carried
across different chains through IBC.
*/
package channel