We value your privacy
We use cookies to improve your browsing experience. By clicking “Accept,” you consent to our use of cookies. You can change your choice at any time via “Cookie settings” in the footer. Read our Privacy policy.

Band · Validator and data operator

Blocksize on Band

Crypto prices from 9,000+ pairs across 70+ exchanges, tested against Band's consensus with every update.

  • 9,000+pairs
  • 99.99%node uptime
  • 0slashing events

What we run on Band

  • Validator
  • Oracle reporter
  • Governance votes

Band at a glance · from today's FAQ

The network

What is the Band Network?

Band is a decentralized oracle built on its own blockchain, BandChain. Applications request data through programmable scripts, and BandChain's validators fetch that data from external sources, report it, and aggregate the results into a single verified value that can be delivered to any blockchain. Built on the Cosmos SDK, it reaches fast finality through validator consensus.

hover to read
Its model

Why Band's model is different

On most oracle networks, fetching data and securing the chain are separate jobs. Band combines them: the same validators that produce blocks are the ones that retrieve and report the requested data. That means the parties securing the network are directly accountable for the data it delivers: data integrity and chain security are enforced by the same set of operators.

hover to read
Our role

Blocksize on Band

Blocksize runs a validator on BandChain. That means we take part in the network's consensus and, as part of that role, fetch and report real-time crypto market data when applications request it. We help secure the network and contribute the data it serves, backed by the same aggregated market data we deliver to our customers off-chain.
You can see our validator here.

hover to read

01 Created

Built from the whole market.

  • Real-time aggregationLiquidity is scattered. Prices are aggregated between 70+ exchanges live.
  • Outlier detectionIndividual trades are filtered using confidence intervals.
  • Dynamic sourceMarkets that show sustained drift, staleness, or unreliable volume are dynamically excluded.
  • Contingency logicWe have clearly defined rules in place to address rare situations where data is delayed or missing.
  • Governance by designAll methodology rules are overseen by the Blocksize Data Committee.

02 Pushed

Our node, our endpoints.

Blocksize validator → oracle report on BandChain → relayed to the target chain.

03 Checked · Ask count, min count

Tested by consensus, every update.

A request asks a stake-weighted set of validators; the result is aggregated once the minimum count has reported.

Our accuracy is not a claim we make. Band measures it each time we submit.

5 layers, trade to chain

From a trade on 70+ exchanges to Band's consensus.

01 · Exchanges

Trades and quotes from 70+ venues. Liquidity is scattered; no venue alone is the market.

02 · Aggregation

9,000+ pairs, outliers filtered, drifting venues down-weighted, rules under the Data Committee.

03 · Oracle reporter

Fetches and reports our price when a request asks our validator.

04 · Validator

Produces and signs BandChain blocks.

05 · BandChain aggregation

Results are aggregated once the minimum count has reported.

Why it matters to Band

What vertical integration gives a network.

Accuracy

No hand-offs between trade and chain

The price leaves our aggregation and reaches the network through our own nodes. Nothing in between can round, delay or replace it.

Tested in public

Every update meets consensus

Each submission is compared with the other sources before it counts. Our accuracy is measured by the network, update after update, not by us.

Security

Fewer parties in the path

Own publisher nodes, own RPC endpoints, own keys. A shorter path has fewer places to attack and fewer parties to trust.

Liveness

One team watches every layer

Exchange outages are absorbed in aggregation; node and RPC failover is ours. The status log shows every minute.

Accountability

One name on every layer

If a value is wrong, it is ours at every step, and networks penalise bad data. Incentives point one way.

Diversity

An independent operator

A first-party source with its own aggregation and infrastructure adds an independent voice to each network's consensus.

Behind the Network

Frequently Asked Questions

If any part of your portfolio touches DeFi, on-chain derivatives or lending protocols, the prices behind those positions are set by oracle consensus. Liquidations, settlements and margin calls on-chain follow the oracle price, whatever one exchange shows. Blocksize delivers those oracle-grade prices off-chain into your systems, so your risk models match what smart contracts act on. Download our Whitepaper to learn more.

Group 36(2)

Our feeds are validated across eight leading oracle networks, which together secure around 75% of all value secured by oracles, and delivered off-chain to institutional systems. Compliance, risk and trading teams receive the same oracle-grade prices that govern DeFi smart contracts.

Group 36(1)

A single exchange only shows its own order book, which can drift from the real market: on even the most liquid pair, only about 25% of a top exchange's quotes sit within the true multi-venue fair value, and during stress a venue can diverge by 10 basis points or more. Listing sites like CoinGecko show a reference average, not a real-time, validated feed you can build on. We aggregate across 70+ venues in real time, filter outliers, and down-weight drifting sources, so you get the consensus price the whole market agrees on, not one venue's version of it.

Building Illustration

As a first-party oracle data publisher, every price update we produce is independently verified by multiple node operators across decentralized oracle networks like Chainlink, Pyth, and RedStone. Submissions that deviate from consensus are rejected, and operators providing inaccurate data face financial penalties. This creates continuous, real-time quality enforcement in every single block.

Computer Illustration

For Band teams

Add Blocksize as a source.