Merge branch 'main' into tamjid/pfm-homecoming

Author: DeshErBojhaa

docs/audits/IBC-v2/IBC-v2-April-2025-Collaborative-Audit-Report.pdf

@@ -17,7 +17,9 @@ Since ibc-go v10, there are two versions of the protocol in the same release: IB
 
 ## High-level overview of IBC v2
 
-For a high level overview of IBC v2, please refer to [this blog post.](https://ibcprotocol.dev/blog/ibc-v2-announcement) For a more detailed understanding of the IBC v2 protocol, please refer to the [IBC v2 protocol specification.](https://github.com/cosmos/ibc/pull/1143)
+For a high level overview of IBC v2, please refer to [this blog post.](https://ibcprotocol.dev/blog/ibc-v2-announcement) For a more detailed understanding of the IBC v2 protocol, please refer to the [IBC v2 protocol specification.](https://github.com/cosmos/ibc/tree/main/spec/IBC_V2)
+
+If you are interested in using the cannonical deployment of IBC v2, connecting Cosmos chains and Ethereum, take a look at the [IBC Eureka](https://docs.skip.build/go/eureka/eureka-overview) documentation to get started.
 
 ## High-level overview of IBC Classic
 

docs/docs/00-intro.md

@@ -10,6 +10,20 @@ slug: /ibc/middleware/develop
 
 IBC middleware will wrap over an underlying IBC application (a base application or downstream middleware) and sits between core IBC and the base application.
 
+:::warning
+middleware developers must use the same serialization and deserialization method as in ibc-go's codec: transfertypes.ModuleCdc.[Must]MarshalJSON
+:::
+
+For middleware builders this means:
+
+```go
+import transfertypes "github.com/cosmos/ibc-go/v10/modules/apps/transfer/types"
+transfertypes.ModuleCdc.[Must]MarshalJSON
+func MarshalAsIBCDoes(ack channeltypes.Acknowledgement) ([]byte, error) {
+	return transfertypes.ModuleCdc.MarshalJSON(&ack)
+}
+```
+
 The interfaces a middleware must implement are found [here](https://github.com/cosmos/ibc-go/blob/v7.0.0/modules/core/05-port/types/module.go).
 
 ```go

docs/docs/01-ibc/04-middleware/02-develop.md

@@ -18,6 +18,20 @@ slug: /ibc/middleware/developIBCv2
 
 IBC middleware will wrap over an underlying IBC application (a base application or downstream middleware) and sits between core IBC and the base application.
 
+:::warning
+middleware developers must use the same serialization and deserialization method as in ibc-go's codec: transfertypes.ModuleCdc.[Must]MarshalJSON
+:::
+
+For middleware builders this means:
+
+```go
+import transfertypes "github.com/cosmos/ibc-go/v10/modules/apps/transfer/types"
+transfertypes.ModuleCdc.[Must]MarshalJSON
+func MarshalAsIBCDoes(ack channeltypes.Acknowledgement) ([]byte, error) {
+	return transfertypes.ModuleCdc.MarshalJSON(&ack)
+}
+```
+
 The interfaces a middleware must implement are found in [core/api](https://github.com/cosmos/ibc-go/blob/main/modules/core/api/module.go#L11). Note that this interface has changed from IBC classic. 
 
 An `IBCMiddleware` struct implementing the `Middleware` interface, can be defined with its constructor as follows:

docs/docs/01-ibc/04-middleware/02-developIBCv2.md

@@ -41,6 +41,20 @@ Middleware allows developers to define the extensions as separate modules that c
 
 IBC middleware will wrap over an underlying IBC application and sits between core IBC and the application. It has complete control in modifying any message coming from IBC to the application, and any message coming from the application to core IBC. Thus, middleware must be completely trusted by chain developers who wish to integrate them, however this gives them complete flexibility in modifying the application(s) they wrap.
 
+:::warning
+middleware developers must use the same serialization and deserialization method as in ibc-go's codec: transfertypes.ModuleCdc.[Must]MarshalJSON
+:::
+
+For middleware builders this means:
+
+```go
+import transfertypes "github.com/cosmos/ibc-go/v10/modules/apps/transfer/types"
+transfertypes.ModuleCdc.[Must]MarshalJSON
+func MarshalAsIBCDoes(ack channeltypes.Acknowledgement) ([]byte, error) {
+	return transfertypes.ModuleCdc.MarshalJSON(&ack)
+}
+```
+
 ### Interfaces
 
 ```go

docs/versioned_docs/version-v7.8.x/01-ibc/04-middleware/01-develop.md

@@ -10,6 +10,20 @@ slug: /ibc/middleware/develop
 
 IBC middleware will wrap over an underlying IBC application (a base application or downstream middleware) and sits between core IBC and the base application.
 
+:::warning
+middleware developers must use the same serialization and deserialization method as in ibc-go's codec: transfertypes.ModuleCdc.[Must]MarshalJSON
+:::
+
+For middleware builders this means:
+
+```go
+import transfertypes "github.com/cosmos/ibc-go/v10/modules/apps/transfer/types"
+transfertypes.ModuleCdc.[Must]MarshalJSON
+func MarshalAsIBCDoes(ack channeltypes.Acknowledgement) ([]byte, error) {
+	return transfertypes.ModuleCdc.MarshalJSON(&ack)
+}
+```
+
 The interfaces a middleware must implement are found [here](https://github.com/cosmos/ibc-go/blob/v7.0.0/modules/core/05-port/types/module.go).
 
 ```go