> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# userToMultiSigSigners | Hyperliquid info

> The info endpoint with type: "userToMultiSigSigners" retrieves the list of multi-signature signers associated with a specific user on the Hyperliquid network.

<Info>
  This method is available on Chainstack. Not all Hyperliquid methods are available on Chainstack, as the open-source node implementation does not support them yet — see [Hyperliquid methods](/docs/hyperliquid-methods) for the full availability breakdown.
</Info>

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.

## 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

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

  ```python Python (hyperliquid-python-sdk) theme={"system"}
  from hyperliquid.info import Info

  info = Info("YOUR_CHAINSTACK_ENDPOINT", skip_ws=True)

  signers = info.query_user_to_multi_sig_signers("0x3710f20c8a8b2781D878105Fbd61CC0c20fE0411")
  print(signers)
  ```

  ```typescript TypeScript (@nktkas/hyperliquid) theme={"system"}
  import { HttpTransport, InfoClient } from "@nktkas/hyperliquid";

  const transport = new HttpTransport({ apiUrl: "YOUR_CHAINSTACK_ENDPOINT" });
  const info = new InfoClient({ transport });

  const signers = await info.userToMultiSigSigners({
    user: "0x3710f20c8a8b2781D878105Fbd61CC0c20fE0411",
  });
  console.log(signers);
  ```
</CodeGroup>

<Note>
  **Use your own endpoint in your code.** The code examples use a placeholder Chainstack endpoint (YOUR\_CHAINSTACK\_ENDPOINT) — replace it with your own Hyperliquid node endpoint from the [Chainstack console](https://console.chainstack.com/). The curl above uses a shared public endpoint for quick checks only; do not use it in production.
</Note>

## 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.


## OpenAPI

````yaml openapi/hyperliquid_node_api/hypercore_info/info_user_to_multi_sig_signers.json post /4f8d8f4040bdacd1577bff8058438274/info
openapi: 3.0.0
info:
  title: Hyperliquid Node API
  version: 1.0.0
  description: This is an API for interacting with Chainstack Hyperliquid node.
servers:
  - url: https://hyperliquid-mainnet.core.chainstack.com
security: []
paths:
  /4f8d8f4040bdacd1577bff8058438274/info:
    post:
      tags:
        - hyperliquid operations
      summary: info (userToMultiSigSigners)
      operationId: infoUserToMultiSigSigners
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                type:
                  type: string
                  default: userToMultiSigSigners
                  enum:
                    - userToMultiSigSigners
                  description: Request type to retrieve multi-signature signers for a user
                user:
                  type: string
                  default: '0x3710f20c8a8b2781D878105Fbd61CC0c20fE0411'
                  description: User address in 42-character hexadecimal format
              required:
                - type
                - user
      responses:
        '200':
          description: Multi-signature signers associated with the user
          content:
            application/json:
              schema:
                type: array
                description: >-
                  List of signer addresses associated with the user's
                  multi-signature setup
                items:
                  type: string
                  description: Signer address in hexadecimal format

````