build(deps): Bump github.com/cosmos/cosmos-sdk from 0.46.0-beta2 to 0.46.0-rc1 in /cosmovisor

[dependabot]

Bumps github.com/cosmos/cosmos-sdk from 0.46.0-beta2 to 0.46.0-rc1.

Release notes

Sourced from github.com/cosmos/cosmos-sdk's releases.

v0.46.0-rc1

Cosmos SDK v0.46.0 Release Candidate 1 - Release Notes

This release introduces several new important updates to the Cosmos SDK. The release notes below provide an overview of the larger high-level changes introduced in the v0.46 release series.

That being said, this release does contain many more minor and module-level changes besides those mentioned below. For a comprehsive list of all breaking changes and improvements since the v0.45 release series, please see the CHANGELOG.

New Module: x/group

The previous v0.43 series focused on simplifying keys and fee management for SDK users, by adding x/feegrant and x/authz. v0.46 finishes this work by introducing x/group.

x/group provides functionality to define on-chain groups of people that can execute arbitrary messages based on agreed upon rules. A simple use-case of x/group is to create on-chain multisigs (with updateable members and thresholds), but x/group can also be used to create more complex DAOs.

The x/group module revolves around 3 concepts:

• A group is simply an aggregation of accounts with associated weights.
• A group policy is a group with a set of rules attached, called decision policy. The decision policy defines how voting and arbitrary message execution happens (e.g. does a proposal pass on 50% yes? 2/3 yes? is there a way to veto? etc). Each group policy has its own an on-chain account, so can hold funds. Managing group membership separately from decision policies results in the least overhead and keeps membership consistent across different policies.
• Any member of a group can submit a proposal for a group policy account to decide upon. A proposal consists of a set of messages that will be executed if the proposal passes voting.

If a proposal passes the decision policy's rules after its voting period, then any account can send a MsgExec against this proposal to execute the sdk.Msgs included in the proposal.

For more details about x/group, please refer to the SDK documentation and ADR-042.

The folder structure of x/group contains an internal folder, which holds a custom ORM used only by x/group (and which will be replaced by the new ORM) as well as a new implementation of Dec (for decimals) based on cockroachdb/apd, which serves as a proof-of-concept for the new sdk.Dec.

Msg-based Gov Proposals

In an effort to align x/gov with x/group, the SDK v0.46 release introduces a new Protobuf package: cosmos.gov.v1.

The biggest change compared to the previous cosmoss.gov.v1beta1 is in MsgSubmitProposal: instead of defining gov router proposal handlers, the v0.46 gov execution models is based on sdk.Msgs:

message MsgSubmitProposal {
-  google.protobuf.Any content                       = 1 [(cosmos_proto.accepts_interface) = "Content"];
+  repeated google.protobuf.Any messages             = 1 [(cosmos_proto.accepts_interface) = "sdk.Msg"];
  repeated cosmos.base.v1beta1.Coin initial_deposit = 2 [(gogoproto.nullable) = false];
  string                            proposer        = 3 [(cosmos_proto.scalar) = "cosmos.AddressString"];
+  // metadata is any arbitrary metadata attached to the proposal.
+  string metadata = 4;
}

For example, instead of broadcasting a v1beta1.MsgSubmitProposal with content a SoftwareUpgradeProposal, the proposer would submit a v1.MsgSubmitProposal with a /cosmos.upgrade.v1beta1.MsgSoftwareUpgrade message. When the proposal passes, the sdk.Msg will be executed by the Msg service router (instead of going through the gov proposal handlers).

The sdk.Msgs in the proposal are executed on behalf of the gov module account. This means that each of the sdk.Msg inside the proposal must have their GetSigners() method return exactly one address, which is the gov module account's address.

A metadata field has also been added to MsgSubmitProposal and MsgVote, for users to provide optional justification for their action.

From a client perspective, the new gov v1 is purely additive. All v1beta1 Protobuf defintions, queries and Msgs still work. Morever, users can also submit v1beta1 legacy proposals using the v1 Msg service, by including a MsgExecLegacyContent inside the v1.MsgSubmitProposal. It is recommended to switch to gov v1 during v0.46, as the gov v1beta1 backwards-compatibility might be removed in a future version.

... (truncated)

Changelog

Sourced from github.com/cosmos/cosmos-sdk's changelog.

v0.46.0-rc1 - 2022-05-23

Features

• (types) #11985 Add a Priority field on sdk.Context, which represents the CheckTx priority field. It is only used during CheckTx.
• (gRPC) #11889 Support custom read and write gRPC options in app.toml. See max-recv-msg-size and max-send-msg-size respectively.
• (cli) #11738 Add tx auth multi-sign as alias of tx auth multisign for consistency with multi-send.
• (cli) #11738 Add tx bank multi-send command for bulk send of coins to multiple accounts.
• (grpc) #11642 Implement ABCIQuery in the Tendermint gRPC service, which proxies ABCI Query requests directly to the application.
• (x/upgrade) #11551 Update ScheduleUpgrade for chains to schedule an automated upgrade on BeginBlock without having to go though governance.
• (cli) #11548 Add Tendermint's inspect command to the tendermint sub-command.
• (tx) #\11533 Register EIP191 as an available SignMode for chains to use.
• (x/genutil) #11500 Fix GenTx validation and adjust error messages
• #11430 Introduce a new grpc-only flag, such that when enabled, will start the node in a query-only mode. Note, gRPC MUST be enabled with this flag.
• (x/bank) #11417 Introduce a new SpendableBalances gRPC query that retrieves an account's total (paginated) spendable balances.
• #11441 Added a new method, IsLTE, for types.Coin. This method is used to check if a types.Coin is less than or equal to another types.Coin.
• (x/upgrade) #11116 MsgSoftwareUpgrade and MsgCancelUpgrade have been added to support v1beta2 msgs-based gov proposals.
• #11308 Added a mandatory metadata field to Vote in x/gov v1beta2.
• #10977 Now every cosmos message protobuf definition must be extended with a cosmos.msg.v1.signer option to signal the signer fields in a language agnostic way.
• #10710 Chain-id shouldn't be required for creating a transaction with both --generate-only and --offline flags.
• #10703 Create a new grantee account, if the grantee of an authorization does not exist.
• #10592 Add a DecApproxEq function that checks to see if |d1 - d2| < tol for some Dec d1, d2, tol.
• #9933 Introduces the notion of a Cosmos "Scalar" type, which would just be simple aliases that give human-understandable meaning to the underlying type, both in Go code and in Proto definitions.
• #9884 Provide a new gRPC query handler, /cosmos/params/v1beta1/subspaces, that allows the ability to query for all registered subspaces and their respective keys.
• #9776 Add flag staking-bond-denom to specify the staking bond denomination value when initializing a new chain.
• #9533 Added a new gRPC method, DenomOwners, in x/bank to query for all account holders of a specific denomination.
• (bank) #9618 Update bank.Metadata: add URI and URIHash attributes.
• (store) #8664 Implementation of ADR-038 file StreamingService
• #9837 --generate-only flag can be used with a keyname from the keyring.
• #10326 x/authz add all grants by granter query.
• #10944 x/authz add all grants by grantee query
• #10348 Add fee.{payer,granter} and tip fields to StdSignDoc for signing tipped transactions.
• #10208 Add TipsTxMiddleware for transferring tips.
• #10379 Add validation to x/upgrade CLI software-upgrade command --plan-info value.
• #10507 Add middleware for tx priority.
• #10311 Adds cli to use tips transactions. It adds an --aux flag to all CLI tx commands to generate the aux signer data (with optional tip), and a new tx aux-to-fee subcommand to let the fee payer gather aux signer data and broadcast the tx
• #10430 ADR-040: Add store/v2 MultiStore implementation
• #11019 Add MsgCreatePermanentLockedAccount and CLI method for creating permanent locked account
• #10947 Add AllowancesByGranter query to the feegrant module
• #10407 Add validation to x/upgrade module's BeginBlock to check accidental binary downgrades
• (gov) #11036 Add in-place migrations for 0.43->0.46. Add a migrate v0.46 CLI command for v0.43->0.46 JSON genesis migration.
• #11006 Add debug pubkey-raw command to allow inspecting of pubkeys in legacy bech32 format
• (x/authz) #10714 Add support for pruning expired authorizations
• #10015 ADR-040: ICS-23 proofs for SMT store
• #11240 Replace various modules ModuleCdc with the global legacy.Cdc
• #11179 Add state rollback command.
• #10794 ADR-040: Add State Sync to V2 Store
• #11234 Add GRPCClient field to Client Context. If GRPCClient field is set to nil, the Invoke method would use ABCI query, otherwise use gprc.
• #10962 ADR-040: Add state migration from iavl (v1Store) to smt (v2Store)
• (types) #10948 Add app-db-backend to the app.toml config to replace the compile-time types.DBbackend variable.

... (truncated)

Commits

• 3a7eac6 chore: Add v0.46.0 RC1 release notes and changelog (#12015)
• 27869a5 refactor: Add Tips decorator in simapp (#12016)
• 7d6cbbb build(deps): Bump goreleaser/goreleaser-action from 2 to 3 (#12018)
• 3c0f55c fix: index ante events for failed tx (#12013)
• d416ee8 refactor: Revert middlewares to antehandler (part 2/2: posthandler) (#11985)
• b2af716 math: derive marshalled byte length from copy, not blind assumptions (#12010)
• 4459c2a build(deps): Bump github.com/hashicorp/go-getter in /cosmovisor (#12008)
• a3a0124 chore!: tweak x/gov ModuleAccountInvariant (#11998)
• 01832e6 refactor: Revert middlewares to antehandlers (part 1/2: baseapp) (#11979)
• cf750b8 build(deps): Bump github.com/hashicorp/go-getter from 1.6.0 to 1.6.1 (#12001)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)