Multi-sig

Advanced Feature (Testnet-only)

The Hyperliquid L1 supports native multi-sig actions in addition to normal L1 actions. The main use case for multi-sig is user-based actions, e.g. treasuries, additional security for funds, and/or any other situation where extra security is desired.

A MultiSig action wraps around any normal action and includes the minimum required number of signatures from authorized users. A normal user can be converted to and from a multi-sig user. While the user is a multi-sig user, all actions applied to it must be wrapped in a MultiSig action.

The multi-sig workflow is described below:

  • To convert a user to a multi-sig user, the desired user needs to send a ConvertToMultiSigUser action with the authorized users and the minimum required number of authorized users needed to sign.

  • Each authorized user must convert their user or an agent into a multi-sig "signer". As a "signer", you are only allowed to provide signatures as part of a MultiSig message. The recommendation is to create a new user and deposit the required fee (10 USDC) to register that user as a multi-sig signer.

  • Each multi-sig signer signs the same inner action to produce a signature. One of the signers can then take a set of signatures and form the MultiSig action to send. The outer signer of the MultiSig action must be one of the authorized signers.

  • To convert a multi-sig user back to a normal user, a MultiSig action is required by definition. In this case, the set of authorized users can be set to empty and conversion to normal user will be performed.

See the Python SDK for code examples.

Last updated