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

# Data consensus

> Verify response accuracy by cross-checking data across multiple providers.

# What is data consensus?

Data consensus verifies API response data by querying multiple blockchain providers and comparing their responses. This ensures the data you receive is accurate, consistent, and free from provider-specific errors or anomalies.

**Use data consensus when you need:**

* Guaranteed data accuracy for critical operations
* Protection against provider data errors
* Verification of financial data (prices, balances)
* Confidence in high-stakes transactions

<Note>Data consensus is automatically enabled for all Uniblock users.</Note>

***

## How it works

When data consensus is enabled, Uniblock follows this process:

1. **Primary request** - Query your primary provider
2. **Parallel verification** - Simultaneously query 2-3 additional providers
3. **Compare responses** - Analyze data from all providers
4. **Detect outliers** - Identify responses that deviate significantly
5. **Return consensus** - Provide verified data based on majority agreement

<Frame caption="Data consensus verification across multiple providers">
  <img src="https://mintcdn.com/uniblock/ce6MWTwGsgFUjX8w/images/docs/a803dd3-data_consensus_image.png?fit=max&auto=format&n=ce6MWTwGsgFUjX8w&q=85&s=56a391feda6643ac23cafd70a26548e8" width="5760" height="4096" data-path="images/docs/a803dd3-data_consensus_image.png" />
</Frame>

***

## Why data consensus matters

### Without data consensus

A single provider error can cause critical issues:

```json Provider returns incorrect price theme={null}
{
  "tokenAddress": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
  "symbol": "USDC",
  "price": 25.0 // ❌ Should be $1.00
}
```

**Consequences:**

* Incorrect portfolio valuations
* Failed trading decisions
* User trust issues
* Financial losses

### With data consensus

Errors are detected and filtered:

```
Provider A: $1.00 ✅
Provider B: $1.01 ✅
Provider C: $25.00 ❌ (outlier detected)

Consensus result: $1.00
```

**Benefits:**

* Accurate data guaranteed
* Outliers automatically filtered
* Confidence in critical operations
* Protection against provider bugs

***

## Supported endpoints

Data consensus works with these endpoint categories:

### Token endpoints

* ✅ Token prices
* ✅ Token balances
* ✅ Token transfers
* ✅ Token allowances

### NFT endpoints

* ✅ NFT floor prices
* ✅ NFT metadata
* ✅ NFT ownership
* ✅ Collection stats

### Transaction endpoints

* ✅ Transaction receipts
* ✅ Gas prices
* ✅ Block data

### Market data endpoints

* ✅ Token prices
* ✅ Trading volume
* ✅ Market cap

<Info>
  Data consensus is not available for JSON-RPC endpoints or provider-specific
  features.
</Info>

***

## Performance impact

Data consensus adds latency as it queries multiple providers:

| Providers queried | Added latency | Use case              |
| ----------------- | ------------- | --------------------- |
| **2 providers**   | \~50-100ms    | Low-latency needs     |
| **3 providers**   | \~100-200ms   | Standard verification |
| **4 providers**   | \~150-300ms   | Maximum accuracy      |

**Optimization tips:**

* Enable only for critical endpoints
* Use lower provider counts for time-sensitive operations
* Cache consensus results when appropriate
* Disable for non-critical data

***

## Key benefits

<CardGroup cols={2}>
  <Card title="Enhanced accuracy" icon="bullseye">
    Cross-verify data across multiple sources for guaranteed accuracy.
  </Card>

  <Card title="Error detection" icon="triangle-exclamation">
    Automatically detect and filter provider errors and anomalies.
  </Card>

  <Card title="Reduced risk" icon="shield-check">
    Minimize impact of incorrect data on critical operations.
  </Card>

  <Card title="Confidence" icon="check-double">
    Make decisions based on verified, consensus-based data.
  </Card>
</CardGroup>

{/* ---

## Best practices

<Check>
**Enable for critical data only** - Use data consensus for financial data, not
all endpoints. Reduces latency and costs.
</Check>

<Check>
**Monitor outlier rates** - High outlier rates from a specific provider
indicate reliability issues. Consider removing that provider.
</Check>

<Check>
**Use appropriate thresholds** - Strict thresholds for prices, lenient for
metadata. Match sensitivity to data criticality.
</Check>

<Check>
**Cache consensus results** - Cache verified data to avoid repeated consensus
queries for the same data.
</Check> */}

***

## When to use data consensus

### ✅ Use data consensus for:

* **Token prices** - Critical for trading, swaps, portfolio valuation
* **Token balances** - Important for transaction validation
* **NFT floor prices** - Essential for marketplace accuracy
* **Gas prices** - Affects transaction cost calculations
* **Financial calculations** - Any data affecting money

***

## Next steps

<CardGroup cols={2}>
  <Card title="Auto-retry" icon="rotate" href="/guides/uniblock/autorouting/uniblock-auto-retry">
    Learn how auto-retry works with data consensus.
  </Card>

  <Card title="Backup providers" icon="life-ring" href="/guides/uniblock/autorouting/uniblock-backup">
    Configure provider fallback lists for consensus queries.
  </Card>

  <Card title="Routing optimization" icon="gauge-high" href="/guides/uniblock/autorouting/uniblock-routing-optimization">
    Optimize provider selection for consensus queries.
  </Card>

  <Card title="Dashboard" icon="chart-line" href="https://dashboard.uniblock.dev">
    Configure consensus settings and monitor metrics.
  </Card>
</CardGroup>

***

## Common pitfalls

<Warning>
  **Using for all endpoints** - Data consensus adds latency and cost. Only
  enable for critical data.
</Warning>

<Warning>
  **Too strict thresholds** - Overly strict outlier detection may flag valid
  variations. Use moderate settings.
</Warning>

<Warning>
  **Ignoring outlier patterns** - Frequent outliers from one provider indicate
  reliability issues. Investigate and adjust.
</Warning>

<Warning>
  **Not accounting for latency** - Consensus adds 100-300ms. Factor this into
  timeout and UX design.
</Warning>

***

<Card title="Ready to get started with Uniblock?" icon="rocket" href="https://dashboard.uniblock.dev">
  Create your free account and start building with unified blockchain infrastructure across 100+ chains.
</Card>

<CardGroup cols={2}>
  <Card title="View API reference" icon="book" href="/reference/unified-api-reference-overview">
    Explore all available endpoints and interactive playgrounds
  </Card>

  <Card title="Join our community" icon="discord" href="https://discord.gg/uniblock">
    Get help from our team and connect with other developers
  </Card>
</CardGroup>