Merge branch 'main' into feat/ibc_v2

Author: kulikthebird

CHANGELOG.md

@@ -2,10 +2,21 @@
 
 ## [Unreleased](https://github.com/CosmWasm/wasmd/tree/HEAD)
 
-Register IBC v2 route and store the IBC v2 port in ContractInfo [\#2122](https://github.com/CosmWasm/wasmd/issues/2122)
-Add IBC v2 SendPacket message encoding [\#2110](https://github.com/CosmWasm/wasmd/issues/2110)
+[Full Changelog](https://github.com/CosmWasm/wasmd/compare/v0.55.0...HEAD)
 
-[Full Changelog](https://github.com/CosmWasm/wasmd/compare/v0.54.0...HEAD)
+ - Register IBC v2 route and store the IBC v2 port in ContractInfo [\#2122](https://github.com/CosmWasm/wasmd/issues/2122)
+ - Add IBC v2 SendPacket message encoding [\#2110](https://github.com/CosmWasm/wasmd/issues/2110)
+
+
+## [v0.55.0](https://github.com/CosmWasm/wasmd/tree/v0.55.0) (2025-03-11)
+
+[Full Changelog](https://github.com/CosmWasm/wasmd/compare/v0.54.0...v0.55.0)
+
+- Bump ibc-go to v10.0.0 which removes IBC fees and capabilities [\#2157](https://github.com/CosmWasm/wasmd/pull/2157)
+- Add gas cost for UnpackAny [\#2115](https://github.com/CosmWasm/wasmd/pull/2115)
+- Make ContractAddrLen variable [\#2111](https://github.com/CosmWasm/wasmd/pull/2111)
+- Adjust SmartContractState query gas limit [\#2103](https://github.com/CosmWasm/wasmd/pull/2103)
+- Refactor build address command [\#2101](https://github.com/CosmWasm/wasmd/pull/2101)
 
 ## [v0.54.0](https://github.com/CosmWasm/wasmd/tree/v0.54.0) (2025-01-08)
 
@@ -287,7 +298,7 @@ below to learn more!
 ### Notable changes:
 
 - If you are not coming from v0.32.0, please see the "Notables changes" below, first. Especially about CometBFT.
-- IBC-Go is a new major version including the "hucklebery" security fix. See [v7.0.1](https://github.com/cosmos/ibc-go/releases/tag/v7.0.1).
+- IBC-Go is a new major version including the "huckleberry" security fix. See [v7.0.1](https://github.com/cosmos/ibc-go/releases/tag/v7.0.1).
 - SDK 47 support is a big step from the SDK 45 version supported before. Make sure to read the upgrade guide for the SDK
   before applying any changes. Links below.
 - Some advice from working with SDK 47 that may affect you, too:

CODE_OF_CONDUCT.md

@@ -40,7 +40,7 @@ Project maintainers who do not follow or enforce the Code of Conduct in good fai
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [Contributor Covenant 1.4][version]
 
 [homepage]: http://contributor-covenant.org
 [version]: http://contributor-covenant.org/version/1/4/

CODING_GUIDELINES.md

@@ -7,7 +7,7 @@ This document is an extension to [CONTRIBUTING](./CONTRIBUTING.md) and provides
 * Code must be well structured:
     * packages must have a limited responsibility (different concerns can go to different packages),
     * types must be easy to compose,
-    * think about maintainbility and testability.
+    * think about maintainability and testability.
 * "Depend upon abstractions, [not] concretions".
 * Try to limit the number of methods you are exposing. It's easier to expose something later than to hide it.
 * Follow agreed-upon design patterns and naming conventions.

Dockerfile

@@ -15,10 +15,10 @@ RUN apk add git
 WORKDIR /code
 COPY . /code/
 # See https://github.com/CosmWasm/wasmvm/releases
-ADD https://github.com/CosmWasm/wasmvm/releases/download/v2.2.1/libwasmvm_muslc.aarch64.a /lib/libwasmvm_muslc.aarch64.a
-ADD https://github.com/CosmWasm/wasmvm/releases/download/v2.2.1/libwasmvm_muslc.x86_64.a /lib/libwasmvm_muslc.x86_64.a
-RUN sha256sum /lib/libwasmvm_muslc.aarch64.a | grep ba6cb5db6b14a265c8556326c045880908db9b1d2ffb5d4aa9f09ac09b24cecc
-RUN sha256sum /lib/libwasmvm_muslc.x86_64.a | grep b3bd755efac0ff39c01b59b8110f961c48aa3eb93588071d7a628270cc1f2326
+ADD https://github.com/CosmWasm/wasmvm/releases/download/v2.2.3/libwasmvm_muslc.aarch64.a /lib/libwasmvm_muslc.aarch64.a
+ADD https://github.com/CosmWasm/wasmvm/releases/download/v2.2.3/libwasmvm_muslc.x86_64.a /lib/libwasmvm_muslc.x86_64.a
+RUN sha256sum /lib/libwasmvm_muslc.aarch64.a | grep 6641730781bb1adc4bdf04a1e0f822b9ad4fb8ed57dcbbf575527e63b791ae41
+RUN sha256sum /lib/libwasmvm_muslc.x86_64.a | grep 32503fe35a7be202c5f7c3051497d6e4b3cd83079a61f5a0bf72a2a455b6d820
 
 # force it to use static lib (from above) not standard libgo_cosmwasm.so file
 RUN LEDGER_ENABLED=false BUILD_TAGS=muslc LINK_STATICALLY=true make build

EVENTS.md

@@ -240,7 +240,7 @@ If the response contains a non-empty list of `attributes`, `x/wasm` will emit a
 always be tagged with `_contract_address` by the Go module, so this is trust-worthy. The contract itself cannot overwrite
 this field. Beyond this, the `attributes` returned by the contract, these are appended to the same event.
 
-A contact may also return custom `events`. These are multiple events, each with their own type as well as attributes.
+A contract may also return custom `events`. These are multiple events, each with their own type as well as attributes.
 When they are received, `x/wasm` prepends `wasm-` to the event type returned by the contact to avoid them trying to fake
 an eg. `transfer` event from the bank module. The output here may look like:
 
@@ -312,7 +312,7 @@ consistent way possible.
 ### Combining Events from Sub-Messages
 
 Each time a contract is executed, it not only returns the `message` event from its call, the `execute` event for the
-contact and the `wasm` event with any custom fields from the contract itself. It will also return the same set of information
+contract and the `wasm` event with any custom fields from the contract itself. It will also return the same set of information
 for all messages that it returned, which were later dispatched. The event system was really designed for one main
 action emitting events, so we define a structure to flatten this event tree:
 
@@ -346,7 +346,7 @@ sdk.NewEvent(
     sdk.NewAttribute("custom", "from contract"),
 ),
 
-// instantiating contract (first dipatched message)
+// instantiating contract (first dispatched message)
 sdk.NewEvent(
     "instantiate",
     sdk.NewAttribute("code_id", fmt.Sprintf("%d", msg.CodeID)),
@@ -382,7 +382,7 @@ sdk.NewEvent(
 
 When the `reply` clause in a contract is called, it will receive the data returned from the message it
 applies to, as well as all events from that message. In the above case, when the `reply` function was called
-on `contractAddr` in response to initializing a contact, it would get the binary-encoded `initData` in the `data`
+on `contractAddr` in response to initializing a contract, it would get the binary-encoded `initData` in the `data`
 field, and the following in the `events` field:
 
 ```go

INTEGRATION.md

@@ -6,14 +6,14 @@ If you want to use Wasm in your own app, here is how you can get this working
 quickly and easily. 
 First start with this [article](https://medium.com/cosmwasm/cosmwasm-for-ctos-iv-native-integrations-713140bf75fc) 
 in the "CosmWasm for CTOs" series that gives you a high level view. 
-Then check to make sure you fit the pre-requisites,
+Then check to make sure you fit the prerequisites,
 then integrate the `x/wasm` module as described below, and finally, you
 can add custom messages and queries to your custom Go/SDK modules, exposing
 them to any chain-specific contract.
 
 ## Prerequisites
 
-The pre-requisites of integrating `x/wasm` into your custom app is to be using 
+The prerequisites of integrating `x/wasm` into your custom app are to be using 
 a compatible version of the Cosmos SDK, and to accept some limits to the
 hardware it runs on.
 

README.md

@@ -28,16 +28,18 @@ Also CosmWasm 2.0 contracts remain compatible at the Wasm interface level.
 To extend the feature set over time, contracts can specify required [capabilities](https://github.com/CosmWasm/cosmwasm/blob/main/docs/CAPABILITIES.md) through cargo features in cosmwasm-std.
 The following table shows which of the [latest capabilities](https://github.com/CosmWasm/cosmwasm/blob/main/docs/CAPABILITIES-BUILT-IN.md) are supported by certain wasmd versions.
 
-| capability   | >= 0.51 | >= 0.42 | >= 0.41 | >= 0.31 | >= 0.29 | 0.28 |
-| ------------ | ------- | ------- | ------- | ------- | ------- | ---- |
-| iterator     | x       | x       | x       | x       | x       | x    |
-| stargate     | x       | x       | x       | x       | x       | x    |
-| staking      | x       | x       | x       | x       | x       | x    |
-| cosmwasm_1_1 | x       | x       | x       | x       | x       |      |
-| cosmwasm_1_2 | x       | x       | x       | x       |         |      |
-| cosmwasm_1_3 | x       | x       | x       |         |         |      |
-| cosmwasm_1_4 | x       | x       |         |         |         |      |
-| cosmwasm_2_0 | x       |         |         |         |         |      |
+| capability   | >= 0.54 | >= 0.52 | >= 0.51 | >= 0.42 | >= 0.41 | >= 0.31 | >= 0.29 | 0.28 |
+| ------------ | ------- | ------- | ------- | ------- | ------- | ------- | ------- | ---- |
+| iterator     | x       | x       | x       | x       | x       | x       | x       | x    |
+| stargate     | x       | x       | x       | x       | x       | x       | x       | x    |
+| staking      | x       | x       | x       | x       | x       | x       | x       | x    |
+| cosmwasm_1_1 | x       | x       | x       | x       | x       | x       | x       |      |
+| cosmwasm_1_2 | x       | x       | x       | x       | x       | x       |         |      |
+| cosmwasm_1_3 | x       | x       | x       | x       | x       |         |         |      |
+| cosmwasm_1_4 | x       | x       | x       | x       |         |         |         |      |
+| cosmwasm_2_0 | x       | x       | x       |         |         |         |         |      |
+| cosmwasm_2_1 | x       | x       |         |         |         |         |         |      |
+| cosmwasm_2_2 | x       |         |         |         |         |         |         |      |
 
 ### For node developers
 
@@ -53,6 +55,12 @@ The following table shows
 
 | wasmd  | compatible | specified                                                         |
 | ------ | ---------- | ----------------------------------------------------------------- |
+| 0.55.0 | 2.2.x      | [2.2.1](https://github.com/CosmWasm/wasmd/blob/v0.55.0/go.mod#L6) |
+| 0.54.0 | 2.2.x      | [2.2.1](https://github.com/CosmWasm/wasmd/blob/v0.54.0/go.mod#L6) |
+| 0.53.2 | 2.1.x      | [2.1.4](https://github.com/CosmWasm/wasmd/blob/v0.53.2/go.mod#L6) |
+| 0.53.1 | 2.1.x      | [2.1.4](https://github.com/CosmWasm/wasmd/blob/v0.53.1/go.mod#L6) |
+| 0.53.0 | 2.1.x      | [2.1.2](https://github.com/CosmWasm/wasmd/blob/v0.53.0/go.mod#L6) |
+| 0.52.0 | 2.1.x      | [2.1.0](https://github.com/CosmWasm/wasmd/blob/v0.52.0/go.mod#L6) |
 | 0.51.0 | 2.0.x      | [2.0.0](https://github.com/CosmWasm/wasmd/blob/v0.51.0/go.mod#L6) |
 | 0.50.0 | 1.5.x      | [1.5.0](https://github.com/CosmWasm/wasmd/blob/v0.50.0/go.mod#L6) |
 | 0.45.0 | 1.5.x      | [1.5.0](https://github.com/CosmWasm/wasmd/blob/v0.45.0/go.mod#L6) |
@@ -236,7 +244,7 @@ We strongly suggest **to limit the max block gas in the genesis** and not use th
       "max_gas": "SET_YOUR_MAX_VALUE",
 ```
 
-Tip: if you want to lock this down to a permisisoned network, the following script can edit the genesis file
+Tip: if you want to lock this down to a permissioned network, the following script can edit the genesis file
 to only allow permissioned use of code upload or instantiating:
 
 `sed -i 's/permission": "Everybody"/permission": "Nobody"/'  .../config/genesis.json`
@@ -257,7 +265,6 @@ Or even testing the app and bringing up critical issues. The following have help
 - Shane Vitarana [shanev](https://github.com/shanev)
 - Billy Rennekamp [okwme](https://github.com/okwme)
 - Westaking [westaking](https://github.com/westaking)
-- Marko [marbar3778](https://github.com/marbar3778)
 - JayB [kogisin](https://github.com/kogisin)
 - Rick Dudley [AFDudley](https://github.com/AFDudley)
 - KamiD [KamiD](https://github.com/KamiD)

UPGRADING.md

@@ -2,7 +2,7 @@
 
 With stargate, we have access to the `x/upgrade` module, which we can use to perform
 inline upgrades. Please first read both the basic 
-[x/upgrade spec](https://github.com/cosmos/cosmos-sdk/blob/master/x/upgrade/spec/01_concepts.md)
+[x/upgrade spec](https://github.com/cosmos/cosmos-sdk/blob/31fdee0228bd6f3e787489c8e4434aabc8facb7d/x/upgrade/spec/01_concepts.md)
 and [go docs](https://godoc.org/github.com/cosmos/cosmos-sdk/x/upgrade#hdr-Performing_Upgrades)
 for the background on the module.
 

app/app.go

@@ -4,6 +4,7 @@ import (
 	"encoding/json"
 	"fmt"
 	"io"
+	"maps"
 	"os"
 	"path/filepath"
 	"sort"
@@ -1092,12 +1093,7 @@ func (app *WasmApp) RegisterNodeService(clientCtx client.Context, cfg config.Con
 //
 // NOTE: This is solely to be used for testing purposes.
 func GetMaccPerms() map[string][]string {
-	dupMaccPerms := make(map[string][]string)
-	for k, v := range maccPerms {
-		dupMaccPerms[k] = v
-	}
-
-	return dupMaccPerms
+	return maps.Clone(maccPerms)
 }
 
 // BlockedAddresses returns all the app's blocked account addresses.

docs/proto/proto-docs.md

@@ -961,7 +961,7 @@ the x/gov module via a v1 governance proposal.
 | ----- | ---- | ----- | ----------- |
 | `title` | [string](#string) |  | Title is a short summary |
 | `description` | [string](#string) |  | Description is a human readable text |
-| `access_config_updates` | [AccessConfigUpdate](#cosmwasm.wasm.v1.AccessConfigUpdate) | repeated | AccessConfigUpdate contains the list of code ids and the access config to be applied. |
+| `access_config_updates` | [AccessConfigUpdate](#cosmwasm.wasm.v1.AccessConfigUpdate) | repeated | AccessConfigUpdates contains the list of code ids and the access config to be applied. |