Skip to main content
POST
/
4f8d8f4040bdacd1577bff8058438274
/
info
info (validatorL1Votes)
curl --request POST \
  --url https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/info \
  --header 'Content-Type: application/json' \
  --data '
{
  "type": "validatorL1Votes"
}
'
[
  {
    "validator": "<string>",
    "votingPower": "<string>",
    "l1Votes": [
      {
        "proposalId": "<string>",
        "vote": "yes",
        "timestamp": 123,
        "blockHeight": 123
      }
    ],
    "participationRate": "<string>"
  }
]
The info endpoint with type: "validatorL1Votes" retrieves information about validator participation in L1 governance voting on the Hyperliquid network. This endpoint provides data about validator voting behavior, consensus participation, and governance engagement.
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.
This request type is supported by the Hyperliquid info server and by Chainstack’s node endpoint, but it is not documented in the upstream Hyperliquid docs. The response shape may evolve.

​
Parameters

​
Request body

  • type (string, required) — The request type. Must be "validatorL1Votes" to retrieve validator L1 voting information.

​
Response

The response is an array of validator voting information, including their L1 governance participation:

​
Validator voting data

  • validator (string) — Validator address in hexadecimal format
  • votingPower (string) — Validator’s voting power in the consensus mechanism
  • l1Votes (array) — List of L1 votes cast by the validator:
    • proposalId (string) — Unique identifier for the governance proposal
    • vote (string) — Vote cast by the validator (“yes”, “no”, or “abstain”)
    • timestamp (integer) — Timestamp when the vote was cast
    • blockHeight (integer) — Block height at which the vote was recorded
  • participationRate (string) — Validator’s participation rate in L1 governance

​
Understanding L1 governance voting

L1 governance structure:
  • Validators participate in network governance through on-chain voting
  • Proposals affect protocol parameters, upgrades, and network policies
  • Voting power typically correlates with validator stake and delegation
  • Consensus mechanisms ensure democratic decision-making
Voting mechanics:
  • Validators can vote “yes”, “no”, or “abstain” on proposals
  • Voting periods have specific timeframes for participation
  • Votes are recorded on-chain for transparency and immutability
  • Participation rates indicate validator engagement in governance
Governance importance:
  • Ensures decentralized decision-making for protocol evolution
  • Validators represent delegator interests in governance decisions
  • High participation rates indicate healthy network governance
  • Voting history provides transparency for delegator selection
Consensus participation:
  • Validators with higher voting power have greater influence
  • Participation rates affect proposal outcomes and legitimacy
  • Regular voting demonstrates validator commitment to network health
  • Abstentions may indicate neutral positions or technical issues

​
Example request

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

​
Example response

[
  {
    "validator": "0x5ac9e4e1b3b8d3d8d5f1a9f7d2b1c4e5f6a7b8c9",
    "votingPower": "123456.0",
    "l1Votes": [
      {
        "proposalId": "HYP-1",
        "vote": "yes",
        "timestamp": 1732320000000,
        "blockHeight": 123456
      }
    ],
    "participationRate": "0.95"
  }
]

​
Use case

The info endpoint with type: "validatorL1Votes" is essential for applications that need to:
  • Governance dashboards: Display validator voting history and participation rates
  • Delegator tools: Help users choose validators based on governance engagement
  • Compliance monitoring: Track validator participation for regulatory requirements
  • Network analysis: Analyze governance participation patterns and trends
  • Validator research: Evaluate validator commitment to network governance
  • Proposal tracking: Monitor voting progress and validator positions
  • Transparency tools: Provide public access to governance voting records
  • Risk assessment: Evaluate network governance health and participation
  • Automated alerts: Notify stakeholders about important governance votes
  • Academic research: Study decentralized governance patterns and effectiveness
  • Audit systems: Verify validator behavior and governance participation
  • Delegation strategies: Optimize delegation based on governance alignment
  • Network health monitoring: Track overall governance participation rates
  • Validator comparison: Compare governance engagement across validators
This endpoint is particularly valuable for delegators selecting validators based on governance participation, governance researchers analyzing voting patterns, compliance systems tracking validator behavior, and applications providing comprehensive validator analytics and transparency tools on the Hyperliquid network.

Body

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

Request type to retrieve validator L1 voting information

Available options:
validatorL1Votes

Response

200 - application/json

Validator L1 voting information and consensus data

​
validator
string

Validator address in hexadecimal format

​
votingPower
string

Validator's voting power in the consensus

​
l1Votes
object[]

List of L1 votes cast by the validator

​
participationRate
string

Validator's participation rate in L1 governance

Last modified on October 19, 2025