HyperCore Native Multisig: Signers, Thresholds, and Transaction Flow
Summary
HyperCore provides native multisig account control, allowing several existing users to authorize actions for one account. A user converts an account by specifying its authorized signers and the minimum number of signatures required. After conversion, actions must be wrapped in a multisig action containing signatures over the same payload and nonce.
One authorized signer acts as the transaction leader and submits the completed action; that signer may use an API wallet. The leader’s nonce is the one validated and updated. Signer lists and thresholds can be changed through a multisig action, and the account can return to normal control by setting the signer list to empty. The document describes account mechanics rather than trading methods or performance evidence. It notes a limit of ten authorized users and warns that HyperEVM control remains with the original wallet after conversion, while CoreWriter does not support multisig users; it advises against HyperEVM interaction for these accounts.
Key ideas
- HyperCore multisig requires a configured signer set and a minimum signature threshold.
- Every multisig action must include signatures over matching transaction information.
- An authorized signer submits the action as leader, and that signer’s nonce is validated.
- Signer configuration can be changed or cleared through a multisig action.
- HyperEVM control remains with the original wallet, and CoreWriter does not support multisig users.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.