POST
/
4f8d8f4040bdacd1577bff8058438274
/
info
info (userToMultiSigSigners)
curl --request POST \
  --url https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/info \
  --header 'Content-Type: application/json' \
  --data '{
  "type": "userToMultiSigSigners",
  "user": "0x3710f20c8a8b2781D878105Fbd61CC0c20fE0411"
}'
[
  "<string>"
]
The info endpoint with type: "userToMultiSigSigners" retrieves the list of multi-signature signers associated with a specific user on the Hyperliquid network. This endpoint is essential for understanding the multi-signature setup and authorized signers for a user’s account.
Get your own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

​
Request body

  • type (string, required) — The request type. Must be "userToMultiSigSigners" to retrieve multi-signature signers.
  • user (string, required) — User address in 42-character hexadecimal format (e.g., 0x3710f20c8a8b2781D878105Fbd61CC0c20fE0411).

​
Response

The response is an array of signer addresses associated with the user’s multi-signature setup:
  • Signers array (array of strings) — List of authorized signer addresses
    • Each element is a hexadecimal address string
    • Represents accounts that can participate in multi-signature operations
    • Empty array indicates no multi-signature setup or no authorized signers

​
Understanding multi-signature signers

Multi-signature functionality:
  • Allows multiple parties to control a single account or execute transactions
  • Enhances security by requiring multiple approvals for sensitive operations
  • Commonly used for institutional accounts, DAOs, and shared custody arrangements
  • Signers are pre-authorized addresses that can participate in multi-sig operations
Signer management:
  • Users can add or remove signers through governance or administrative functions
  • Each signer has equal authority unless specified otherwise in the multi-sig contract
  • Threshold requirements may apply (e.g., 2-of-3, 3-of-5 signatures required)
  • Signer changes typically require existing signer approval
Security considerations:
  • Multi-signature setups reduce single points of failure
  • Distributed control among trusted parties or devices
  • Protection against key compromise or loss
  • Enhanced compliance for institutional requirements

​
Example request

Shell
curl -X POST \
  -H "Content-Type: application/json" \
  -d '{"type": "userToMultiSigSigners", "user": "0x3710f20c8a8b2781D878105Fbd61CC0c20fE0411"}' \
  https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/info

​
Use case

The info endpoint with type: "userToMultiSigSigners" is essential for applications that need to:
  • Account management: Display authorized signers for multi-signature accounts
  • Security auditing: Verify current signer configurations and permissions
  • Transaction preparation: Identify required signers before initiating multi-sig transactions
  • Compliance monitoring: Track authorized parties for regulatory requirements
  • Access control: Validate signer permissions for administrative operations
  • Multi-sig wallets: Show users their current signer setup and configurations
  • Institutional dashboards: Monitor multi-signature arrangements across accounts
  • Risk management: Assess security posture through signer distribution
  • Governance systems: Identify voting participants in multi-sig governance
  • Backup verification: Ensure proper backup signer arrangements
  • Onboarding flows: Guide new users through multi-signature setup
  • Permission management: Track and manage signer roles and responsibilities
  • Emergency procedures: Identify available signers for urgent operations
  • Audit trails: Document signer changes and account modifications
This endpoint is particularly valuable for institutional users managing complex multi-signature arrangements, security-conscious traders using multi-sig wallets, compliance teams tracking authorized signers, and applications providing comprehensive account security management on the Hyperliquid network.

Body

application/json
​
type
enum<string>
default:userToMultiSigSigners
required

Request type to retrieve multi-signature signers for a user

Available options:
userToMultiSigSigners
​
user
string
default:0x3710f20c8a8b2781D878105Fbd61CC0c20fE0411
required

User address in 42-character hexadecimal format

Response

200 - application/json

Multi-signature signers associated with the user

List of signer addresses associated with the user's multi-signature setup