packet-forward-middleware v4.1.2

Note

This release includes the patch for the Mandrake vulnerability

We recommend that you upgrade to the patched version, create a new release for your chain binary, and coordinate an upgrade with validators as soon as reasonable.

In addition to patching packet-forward-middleware, it is imperative that you check the balances of each escrow account against the total supply of each asset on the associated counterparty chain. Failure to verify parity between the escrow accounts and the counterparty total supply can result in a type of Denial-of-Service where users may not be able to unwind their assets through your chain. You can use our escrow checker tool or whatever means you deem fit to validate these balances against the counterparty total supply. If a discrepancy is found, you will need to build an upgrade handler that mints and transfers assets to the escrow account(s) with the discrepancy. Strangelove has provided an example upgrade handler or you can see the upgrade handler used by the Cosmos Hub.

What's Changed

• [BP: release/v4 <- #88] test: use non-deprecated gomock package & fix unit tests by @mergify in #113
• [BP: release/v4 <- #118] rename: router -> packetforward by @mergify in #119
• [BP: release/v4 <- #70] Add warning to ibc-hooks docs by @mergify in #123
• [BP: release/v4 <- #132] chore: export the GetReceiver function by @mergify in #133
• [BP: release/v4 <- #86] fix!: queries that panic should return ack-err by @mergify in #137
• fix: mint and transfer funds back to escrow account on timeout or ack error by @jtieri in #174

Full Changelog: middleware/packet-forward-middleware/v4.1.1...middleware/packet-forward-middleware/v4.1.2