Multisig UI Development Update 1

Abel
Confio
Published in
3 min readOct 10, 2023

The cosmos-multisig-ui has been actively maintained by Confio for some time now, so we thought an article showing the improvements to the app was due.

Testnets can now be connected to

The invaluable chain-registry repo provides data for both mainnets and testnets of the Cosmos ecosystem, but only mainnets were supported until now on the Multisig UI.

Multiple messages and asset selection

While the previous version of the app did a good job of providing the necessary form for each type of message it supported, only one could be added per transaction.

Also, any denom from the chain registry can now be selected, whereas before, only the fee token could be sent.

Support for Staking messages

Since only MsgDelegate was supported, a user could stake some tokens to a validator but wasn’t able to then withdraw them.

Now, both MsgUndelegate and MsgBeginRedelegate messages can be sent.

Support for Distribution messages

Both MsgWithdrawDelegatorReward and MsgSetWithdrawAddress are now available to be sent, enabling the claiming of rewards and the setting of a withdraw address different from the delegator, respectively.

Support creating a Vesting account

A MsgCreateVestingAccount form is now available to add this kind of message to a transaction.

Support sending IBC tokens

The new MsgTransfer message can be selected when creating a transaction in order to send IBC tokens.

Support CosmWasm messages

MsgInstantiateContract, MsgInstantiateContract2, MsgExecuteContract, and MsgMigrateContract are now available, too:

Other development tasks

Much of the work has been centered around refactoring the code to enable the changes above, like decoupling the transaction and message components so that several messages could be included or improving the state management of the networks, so it’s now easier than ever to add new functionalities.

Other improvements have been focused on bugfixes and on small UX tweaks, like:

  • Show all the holdings of a multisig, not only the fee token.
  • Add loading spinners to buttons when the forms are submitted.
  • Add a link to see the current multisig in an explorer.
  • Warn and redirect to the home screen when connecting to another chain.
  • Change the user of the app when changing the user in Keplr.
  • Add some missing back buttons for better navigation.
  • Show error when creating a transaction besides logging to console.

What’s next?

The upcoming features we’re currently planning to release include:

  • A layout tweak for the “Add Msg” buttons.
  • User login to display offchain data like list of multisigs.
  • A redesign of the UI.

That’s it for the first Multisig UI Development Update; we’re looking forward to the next one!

--

--