What is Band Protocol?
👋 New to this? Just start reading at the top — it begins in plain English and gets more detailed as you scroll. Jump to any level:
🟢 The simple version
Plain English — no jargon. Start here.
Band Protocol is a cross-chain oracle network — it brings real-world data (prices, sports results, weather, any verifiable information) onto blockchains, competing with Chainlink by using its own purpose-built blockchain (BandChain) to aggregate and validate oracle data before delivering it to any connected chain.
What oracles do and why they matter
Blockchains are isolated systems — a smart contract on Ethereum cannot natively read the current price of ETH/USD, the result of a sports match, or the weather in Mumbai. Oracles are the bridges that bring external data onto chains. Without reliable oracles, DeFi protocols cannot price assets, insurance contracts cannot trigger on real-world events, and prediction markets cannot resolve.
Band Protocol provides this oracle layer. It differs from Chainlink in a key architectural choice: Band built its own blockchain (BandChain, on Cosmos SDK) specifically for oracle operations. Data requests are processed on BandChain — validators fetch data from external sources, reach consensus on the value, and then deliver the validated result to any connected chain (Ethereum, BNB Chain, Solana, and others via BandChain's IBC and bridge connections).
Band vs Chainlink — the key differences
Chainlink operates directly on destination chains — Chainlink nodes submit data directly to Ethereum contracts, with no intermediate chain. Band routes requests through BandChain first. Band's architecture is faster for cross-chain use cases (one BandChain request can supply multiple destination chains simultaneously), while Chainlink's architecture is more deeply integrated with Ethereum's security model. Both have extensive real-world deployments; neither has "won" the oracle market.
What BAND token does
BAND is staked by BandChain validators. Validators with more BAND stake have more influence on oracle data aggregation. BAND stakers earn fees from oracle data requests. BAND is used for governance. Total supply: 100 million BAND.
Is it legal in India?
Yes. BAND is a VDA under Indian law. 30% tax and 1% TDS apply. See India regulation.
🟡 A bit more detail
For when you want to go a little deeper.
BandChain — the oracle-specific blockchain
BandChain is built on Cosmos SDK and uses Tendermint BFT consensus. It is designed specifically for oracle operations: processing data requests, aggregating validator responses, and producing proofs that can be verified on destination chains. A data request on BandChain follows this flow: a smart contract on Ethereum (or another chain) requests a price. BandChain validators each independently query the specified data sources (price APIs, sports data feeds, etc.). Validators submit their results to BandChain. BandChain reaches consensus on the median value. The result and a merkle proof are relayed back to the Ethereum contract.
Band Protocol provides price feeds for DeFi protocols across multiple blockchains. Alpha Finance Lab and Venus Protocol (BNB Chain DeFi) use Band oracles. Band is particularly strong in non-Ethereum chains where Chainlink has less coverage. Several prediction market platforms use Band for sports and event data resolution. WazirX (Indian crypto exchange) has used Band for price feeds. Band's cross-chain oracle capability makes it the preferred choice for Cosmos-ecosystem chains connected via IBC.
Oracle Script and Data Sources
Band Protocol uses a two-layer data specification. Data Sources are scripts that fetch data from specific external APIs — each Data Source specifies the endpoint, parsing logic, and expected data format. Oracle Scripts aggregate multiple Data Sources into a single oracle request — for example, an ETH/USD Oracle Script might call CoinGecko, Binance, and Kraken Data Sources and return the median price. This separation allows flexible composition: the same Data Sources can be mixed into different Oracle Scripts for different use cases.
Key Band metrics: number of oracle requests per day, number of chains served, validator count and stake distribution (decentralisation indicator), and BAND staking yield. Band competes directly with Chainlink — the primary comparison is coverage breadth (Chainlink wins on Ethereum ecosystem depth; Band wins on Cosmos/cross-chain coverage), response time, and decentralisation. Live data: CoinGecko · CosmoScan (BandChain).
🟣 The full technical picture
For the technically curious.
Band Protocol whitepaper and proof of validity
The Band Protocol whitepaper describes "Proof of Validity" — the cryptographic mechanism by which BandChain results are verified on destination chains. Each oracle result from BandChain includes a merkle proof of the result's inclusion in a BandChain block. The destination chain maintains a light client of BandChain — a compact record of recent BandChain block headers updated by relayers. To verify an oracle result, the destination chain smart contract checks the merkle proof against the stored BandChain block header. This allows any EVM chain to trustlessly verify BandChain data without running a full BandChain node.
Source: Band Protocol documentation. docs.bandchain.org · Band Protocol whitepaper: whitepaper.bandprotocol.com
VRF — verifiable random function
Beyond price feeds, Band Protocol provides a Verifiable Random Function (VRF) service — on-chain random number generation that can be verified as genuinely random and not manipulable by the requester, the oracle, or any single party. VRF is used by blockchain games (random loot drops, NFT trait generation), prediction markets (random draw mechanics), and DeFi protocols requiring unmanipulable randomness. Band's VRF uses a multi-party computation among BandChain validators to generate random values that no single validator can predict or influence — the randomness is provably fair.
BandChain's IBC integration allows Cosmos-ecosystem chains to request oracle data natively via the Inter-Blockchain Communication protocol, without any bridge contracts or relayer trust assumptions. An IBC oracle request is a standard IBC packet: the requesting chain sends a packet specifying the Oracle Script ID and parameters; BandChain processes the request, computes the result using its validators, and sends an IBC acknowledgement back with the data. The requesting chain's IBC module verifies the acknowledgement cryptographically using BandChain's IBC light client. This native IBC integration eliminates the relayer trust assumption present in Band's EVM bridge deployments — the security model is purely IBC cryptography.
Key facts
- Function: Cross-chain oracle network + VRF
- Own chain: BandChain (Cosmos SDK, Tendermint BFT)
- Data flow: Request → BandChain validators → consensus → proof → destination chain
- Proof mechanism: Merkle proof + BandChain light client
- IBC native: Yes (Cosmos ecosystem)
- BAND supply: 100 million
- Founded: 2017 (Soravis Srinawakoon, Paul Nattapatsiri)