Skip to content

Latest commit

 

History

History
105 lines (76 loc) · 6.62 KB

CHANGELOG.md

File metadata and controls

105 lines (76 loc) · 6.62 KB

CHANGELOG

Unreleased

v0.4.2

May 19th, 2024

Improvements

  • multisig is able to process BaseAccount types from SDK v0.50.*
  • refactor account type processing to improve readability and remove hardcoded version from type URL

v0.4.1

April 16th, 2024

BUG FIXES

  • localname settings in the config were not being applied properly, and would result in errors when running multisig broadcast (#85)

FEATURES

  • multisig can now handle DelayedVestingAccount vesting account types (commit)

v0.4.0

December 20th, 2022

Highlights

This major release implements a couple new transaction commands and adds additional flags to improve the flexibility when adding new transactions such as ability to specify gas and fees.

FEATURES

  • Changed the way EthAccount account types are checked (#63)
  • Added a new command to generate a withdraw-rewards transaction to claim validators' rewards and commission (#65)
  • Added a new command to create a delegate transaction (#66)
  • Allow fees and gas flags to be specified when creating a new transaction (#70)
  • Added support for '/stride.vesting.StridePeriodicVestingAccount' (#73)
  • Upgraded Cosmos SDK version (v0.45.9) and Golang version (v1.18) (#80)
  • Implemented logic to add a --node flag to the multisig broadcast command (#82)
  • Added logic to allow a user to specify a --key flag to the multisig broadcast command (#83)

BUG FIXES

  • Refactored the logic to delete files from S3. Now when pushing (--force) tx files, all existing files in the path will be deleted first (#74)

v0.3.0

September 8th, 2022

Highlights

This major release has a few improvements such as new commands, a new config file handling, ability to use an S3 provider other than AWS (e.g. minio), an end-to-end basic test suite that leverages containers and several important bug fixes that were identified during regular use of the tool.

FEATURES

  • New configuration file handling (#51)
    • By default, the config file $HOME/.multisig/config.toml is used
    • Config file now may be customized via --config flag
    • If the file is not specified with the --config flag or the file is in the $HOME/.multisig folder, then it will look for it in the current folder
  • AWS S3 address can be modified to support S3-compatible self-hosted solutions (#41)
  • Basic end-to-end test suite (#40)
  • New multisig delete command that allows the deletion of files in the S3 bucket for a specific chain and key name (#29)
  • Added a new --description flag to multisig tx commands to allow additional metadata to be added to the signdata.json file, e.g a short description about the tx (#37)
  • Implemented logic to use the default values for gas and fees from the configuration file. This replaces the old way where these values were only hard-coded. If values are not specified in the config the hard-coded values will still be used (#44)
  • New tx authz revoke command that allows multisig to submit a tx to revoke an authz permission previously granted for a particular message type (e.g. vote) (#18)

BUG FIXES

  • Fixed issue that prevented a tx withdraw to be pushed to S3 (#34)
  • Handle different account types that were returned when querying an account to find the account number and the sequence number. This bug prevented signing txs in Regen and Evmos for examples
    • Support for different account types such as BaseAccount and PeriodicVestingAccount (#21)
    • Support for the /ethermint.types.v1.EthAccount account type (Evmos use it) (#54)
    • Support for the /cosmos.vesting.v1beta1.ContinuousVestingAccount account type (#47)

v0.2.1 (May 10, 2022)

Thi minor release includes some minor bug fixes identified after the previous release

  • Fix the raw cat command (#17)
  • Fix the multisig list --all command (#23)
  • Avoid panic when executing a tx push command (#32) (#26)
  • Better handling of messages and warnings (#19) (#28)

v0.2.0 (May 3, 2022)

  • Allow multiple txs to be submited for a single (chain, key) pair using the --additional or -x flag. Paths now include a "txIndex" value, starting from 0. The txIndex is automatically added to the sequence number fetched from the node. This allows multiple sequential txs to be pushed and signed asynchronously. sign and broadcast commands now take a --index or -i value to specify the tx to sign or broadcast. Txs must be broadcast in order but can be signed in any order.
  • Don't overwrite a tx without specifying --force or -f.
  • Removed generate command, the new tx push command has the same effect but a better name.
  • Added tx vote and tx withdraw commands that generate the unsigned transaction.
  • Added --denom flag for fees. Denom can also be set in the configuration, under [[chains]]. For example denom=uatom. If denom is not set anywhere, it will be queried from the chain registry.
  • Added tx authz grant command to create transactions for granting authz persmissions.

v0.1.0 (Mar 8, 2022)

Basic functionality for managing multisig txs with an AWS bucket! Only allows one tx per (chain, key) pair at a time.