Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md to add zellic audit #228

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+3 −0
Open

Update README.md to add zellic audit #228

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions middleware/packet-forward-middleware/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,7 @@
# packet-forward-middleware

[Audited by Zellic on Aug 13th, 2024](https://github.com/Zellic/publications/blob/master/Celestia%20Packet%20Forward%20Middleware%20-%20Zellic%20Audit%20Report.pdf). Commit: [26d8080d](https://github.com/cosmos/ibc-apps/commit/26d8080d75662ea2f1155fce446ebda7a915d521) version with patches: [v8.1.0](https://github.com/cosmos/ibc-apps/releases/tag/middleware%2Fpacket-forward-middleware%2Fv8.1.0)

Middleware for forwarding IBC packets.

Asynchronous acknowledgements are utilized for atomic multi-hop packet flows. The acknowledgement will only be written on the chain where the user initiated the packet flow after the forward/multi-hop sequence has completed (success or failure). This means that a user (i.e. an IBC application) only needs to monitor the chain where the initial transfer was sent for the response of the entire process.
Expand Down
Loading