Docs

validatorL1Votes - HyperCore Info Endpoint

Get validator voting information for L1 operations on Hyperliquid. Monitor consensus, voting patterns, and validator participation.

Get validator voting information for L1 operations on Hyperliquid, including consensus data and validator participation.

Authenticate HyperCore Info requests by sending your Dwellir API key in the x-api-key header to https://api-hyperliquid-mainnet-info.n.dwellir.com/info.

When to Use This Endpoint

The validatorL1Votes endpoint is essential for:

  • Validator Monitoring — Track validator voting activity and participation
  • Consensus Analysis — Analyze voting patterns and consensus formation
  • Network Health — Monitor validator coordination on L1 operations
  • Staking Insights — Understand validator behavior for staking decisions

Common Use Cases

1. Monitor Validator Participation

Track validator activity on L1 operations:

JavaScript
async function monitorValidatorActivity() {
  const data = await getValidatorL1Votes();

  console.log('=== Validator L1 Voting Activity ===\n');
  console.log(`Total vote records: ${data.votes.length}`);

  if (data.votes.length === 0) {
    console.log('No recent L1 voting activity');
  }
}

2. Analyze Consensus Patterns

Analyze voting patterns and consensus formation:

JavaScript
async function analyzeConsensus() {
  const data = await getValidatorL1Votes();

  return {
    totalVotes: data.votes.length,
    timestamp: Date.now(),
    hasActivity: data.votes.length > 0
  };
}

// Usage
const analysis = await analyzeConsensus();
console.log(`Consensus analysis:`, analysis);

3. Build Validator Dashboard

Create a monitoring dashboard for validators:

JavaScript
async function getValidatorDashboard() {
  try {
    const votes = await getValidatorL1Votes();

    return {
      status: 'operational',
      voteCount: votes.votes.length,
      lastUpdated: new Date().toISOString()
    };
  } catch (error) {
    return {
      status: 'error',
      error: error.message
    };
  }
}

Best Practices

  1. Poll regularly — Monitor validator activity at consistent intervals
  2. Cache appropriately — Cache results for several minutes to reduce load
  3. Handle empty responses — Account for periods with no L1 voting activity
  4. Implement timeouts — Use reasonable timeout values (10-30 seconds)
  5. Monitor trends — Track voting patterns over time for insights

Access real-time Hyperliquid validator information with Dwellir's HyperCore Info Endpoint. Get your API key →