docs: IBCv2 documentation structure

Author: kulikthebird

src/pages/_meta.jsx

@@ -5,6 +5,7 @@ export default {
   core: "CosmWasm Core",
   wasmd: "Wasmd",
   ibc: "IBC",
+  ibc2: "IBCv2",
   sylvia: "Sylvia",
   storey: "Storey",
   "cw-storage-plus": "StoragePlus",

src/pages/ibc2/_meta.js

@@ -0,0 +1,6 @@
+export default {
+  "getting-started": "Getting started",
+  "entrypoints": "Entry points",
+  "message-passing": "Message passing",
+  "example": "Example contract",
+};

src/pages/ibc2/entrypoints.mdx

@@ -0,0 +1,66 @@
+---
+tags: ["ibc"]
+---
+
+# Entry points in IBCv2
+
+There are 4 entry points specified in the IBCv2 protocol.
+
+## Receive entry point
+```rust template="core"
+#[cfg_attr(not(feature = "library"), entry_point)]
+pub fn ibc2_packet_receive(
+    deps: DepsMut,
+    env: Env,
+    msg: Ibc2PacketReceiveMsg,
+) -> StdResult<IbcReceiveResponse> {
+    // [...]
+}
+```
+
+ * TODO tkulik: Describe `Ibc2PacketReceiveMsg`
+
+## Time out entry point
+
+```rust template="core"
+#[cfg_attr(not(feature = "library"), entry_point)]
+pub fn ibc2_packet_timeout(
+    deps: DepsMut,
+    env: Env,
+    msg: Ibc2PacketTimeoutMsg,
+) -> StdResult<IbcBasicResponse> {
+    // [...]
+```
+
+* TODO tkulik: Describe `Ibc2PacketTimeoutMsg`
+
+## Acknowledgement receive entry point
+
+```rust template="core"
+#[cfg_attr(not(feature = "library"), entry_point)]
+pub fn ibc2_acknowledge_receive(
+    deps: DepsMut,
+    env: Env,
+    msg: Ibc2AcknowledgeMsg,
+) -> StdResult<IbcBasicResponse> {
+    // [...]
+}
+```
+
+* TODO tkulik: Describe `Ibc2AcknowledgeMsg`
+
+
+## Sent entry point
+
+```rust template="core"
+#[cfg_attr(not(feature = "library"), entry_point)]
+pub fn ibc2_packet_sent(
+    deps: DepsMut,
+    env: Env,
+    msg: Ibc2PacketSentMsg,
+) -> StdResult<IbcBasicResponse> {
+    // [...]
+}
+```
+
+* TODO tkulik: Describe `Ibc2SentMsg`

src/pages/ibc2/example.mdx

@@ -0,0 +1,7 @@
+---
+tags: ["ibc"]
+---
+
+# Example contract
+
+* TODO tkulik: Example implementation of the ibc2 entry points 

src/pages/ibc2/getting-started.mdx

@@ -0,0 +1,21 @@
+---
+tags: ["ibc"]
+---
+
+import { Callout } from "nextra/components";
+
+# Getting started
+
+CosmWasm module uses [ibc-go](https://ibc.cosmos.network/main/) implementation to interact with other blockchains via IBC protocol.
+Along with ibc-go version 10 a new protocol version was announced - [IBCv2](https://ibcprotocol.dev/blog/ibc-v2-announcement).
+The new version allows interaction between Cosmos and non-Cosmos blockchains. To achieve this goal,
+the protocol team decided to simplify the flow and reduce number of entry points.
+Thanks to this update, now it's feasible to implement appropriate endpoints on chains like for e.g. Ethereum.
+Side effect for the contract developers is the fact, that there are only few entry points to implement in smart contracts
+in order to take full advantage of the blockchain interconnections.
+
+<Callout>
+This section of a documentation provides a basic information on how to set up contracts to use IBCv2 entry points and how
+to communicate with services and contracts on different chains. To learn more about the IBC architecture we recommend
+to visit the [official ibc-go documentation page](https://ibc.cosmos.network/main/).
+</Callout>

src/pages/ibc2/message-passing.mdx

@@ -0,0 +1,18 @@
+---
+tags: ["ibc"]
+---
+
+# Message passing
+
+Smart contract can send IBCv2 messages from entry points  we Message
+
+## Send IBCv2 messages
+
+
+
+## Entry point usage for sent messages
+
+The special entry point `ibc2_packet_sent` is called
+
+* TODO tkulik: How to send ibcv2 message
+* TODO tkulik: How to send acknowledgement asynchronously