Crypto Gloss

Band Protocol: Decentralized Data Oracle

Authors Sorasit, Paul; Lertjitbanjong, Sorawit; Rangsitratkul, Prin; et al. (Band Protocol)
Year 2020
Project Band Protocol
License Apache 2.0
Official Source https://whitepaper.bandprotocol.com/

This page is an educational summary and analysis of an official whitepaper or technical paper, written for reference purposes. It is not a verbatim reproduction. CryptoGloss does not claim authorship of the original work. All intellectual property rights remain with the original author(s). The official document is linked above.

“Band Protocol: Decentralized Data Oracle” is the whitepaper by Band Protocol (co-founded by Paul Sorasit, Sorawit Lertjitbanjong, and Prin Rangsitratkul in Thailand, 2017) describing a cross-chain oracle network built as a sovereign Cosmos SDK blockchain (BandChain). Band makes oracle services a first-class blockchain primitive: data requests are transactions, data aggregation is computed by WebAssembly programs (“oracle scripts”) on-chain, and results are delivered to destination chains via IBC or bridge adapters.

> Whitepaper: Available at whitepaper.bandprotocol.com.

Publication and Context

In 2019, Chainlink was the dominant oracle (Ethereum-centric, push-based, committee voting). Band Protocol’s differentiation: rather than securing oracles via a committee of data providers on Ethereum, Band built an entire Cosmos blockchain dedicated to oracle computation — enabling oracle logic to run as on-chain code with blockchain-level finality, and then relay results to any connected chain.

Band v1 (2019) was an Ethereum-based token-curated oracle. Band v2 (2020, BandChain) rebuilt the system as a Cosmos SDK chain, which is the design described in the main whitepaper.

BandChain Architecture

BandChain is a Cosmos SDK Tendermint-BFT blockchain with:

  • Its own validator set (secured by delegated staking of BAND tokens)
  • A specialized transaction type: Data Request transactions
  • Tendermint finality (~3 seconds): oracle results have BFT-final guarantees, not just probabilistic confirmation
  • IBC compatibility: any Cosmos chain can consume BandChain data via IBC channels

Workflow:

  1. A consumer (dApp on Ethereum, BSC, Avalanche, etc.) submits a data request (or has it relayed automatically)
  2. BandChain validators receive the request and call data sources
  3. Validators aggregate responses using an oracle script (WebAssembly program)
  4. The result is included in a BandChain block with BFT finality
  5. A relayer observes the result and submits a transaction to the consumer chain with a BandChain proof

Oracle Scripts

Oracle scripts are WebAssembly programs stored on-chain that define how a data request is processed:

A script defines:

  • Prepare phase: Which data sources to call, with what parameters
  • Aggregate phase: How to combine multiple data source responses (median, mean, custom logic)

Example oracle script for ETH/USD price:

  • Call 5 data sources: CoinGecko, CoinMarketCap, Binance, Kraken, OKX
  • Aggregate by median of returned prices
  • Return the result as a uint64 (price × 10⁸)

Data sources are simpler scripts that define how to call an external API and parse the response. Both oracle scripts and data sources are stored on BandChain and can be composed.

Validator Responsibilities

BandChain validators perform two duties:

  1. Block validation: Standard Tendermint BFT consensus on BandChain blocks
  2. Data provision: When assigned to a data request, call the relevant external APIs, run the oracle script’s prepare phase, and submit their response before the request timeout

Validators who fail to respond to assigned requests are penalized (slashed) proportionally to missed responses. This creates economic pressure to maintain reliable data source connections.

Cross-Chain Delivery

Band delivers oracle results to connected chains in two ways:

Via IBC (Cosmos chains): Direct cross-chain packet relay using the IBC protocol. Any Cosmos chain with an IBC connection to BandChain can query oracle results with cryptographic proof.

Via Bridge contracts (EVM chains): A smart contract bridge on Ethereum (and other EVM chains) verifies BandChain validator signatures (using BLS aggregation) to confirm that a given oracle result was included in a BandChain block with sufficient validator support. The bridge maintains the current BandChain validator set and updates it on epoch changes.

BAND Token Economics

  • BAND tokens are staked by validators and delegators
  • Delegators earn staking rewards (+oracle data fees)
  • Fees are paid in BAND by requesters for oracle data (fee per data request)
  • Validators can set their own oracle data fees; market competition determines effective pricing

Reality Check

Band Protocol is a fully operational oracle network with live price feeds serving multiple chains (Ethereum, BSC, Avalanche, Cosmos ecosystem). Its Cosmos SDK design is technically coherent and benefits from IBC for direct chain connectivity.

Caveats:

  • Market share: Chainlink dominates the oracle market by usage. Band has been more popular in the Cosmos ecosystem and Southeast Asian DeFi markets than globally.
  • Data provider centralization: Despite the decentralized validator set, the data sources called by oracle scripts are typically centralized APIs (CoinGecko, CoinMarketCap). The validators are decentralized; the underlying data sources often are not.
  • Cross-chain latency: The two-step process (BandChain block → relayer → destination chain) adds latency. For high-frequency trading applications, this can be a constraint.

Legacy

Band Protocol demonstrated that a purpose-built oracle blockchain using Cosmos SDK could provide IBC-native oracle services to the entire Cosmos ecosystem — something Chainlink’s Ethereum-centric design struggled with. The oracle script / data source composability model influenced later oracle designs. Band’s BAND v2 relaunch on BandChain pioneered the “oracle as a blockchain” model.

Related Terms

Research

  • Sorasit, P., Lertjitbanjong, S., Rangsitratkul, P., et al. (2020). Band Protocol: Decentralized Data Oracle. Band Protocol.

— Primary whitepaper. Section 3 defines oracle scripts; Section 5 covers cross-chain delivery via IBC and bridge contracts.

  • Breidenbach, L., et al. (2021). Chainlink 2.0: Next Steps in the Evolution of Decentralized Oracle Networks. Chainlink Labs.

— The competing oracle design; useful for comparing Band’s custom-blockchain approach to Chainlink’s committee-on-Ethereum design.

  • Kwon, J., & Buchman, E. (2016). Cosmos: A Network of Distributed Ledgers. Cosmos whitepaper.

— The foundational Cosmos SDK and IBC paper; Band Protocol inherits Tendermint BFT consensus and IBC interoperability from this architecture.