Band Protocol

About Band Protocol (BAND)

What Is Band Protocol (BAND)?

Band Protocol is a cross-chain oracle network that delivers real-world data, primarily asset prices, to smart contracts on other blockchains. It runs its own Cosmos SDK blockchain, BandChain, whose validators are paid to fetch, aggregate, and publish that data, and then ship it to destination chains in a form those chains can verify.

The point of putting the work on a separate chain is separation of duties. Continuously watching prices and reacting to price moves is expensive if you do it on a general-purpose smart contract platform. BandChain absorbs that load, and the same verified data points can then be reused across many networks. BAND is the chain's native staking and governance token.

Official sources:

• Band Protocol
• Band documentation
• CosmoScan explorer
• Band Protocol on GitHub

Who Founded Band Protocol? (History)

Band Protocol was founded in 2017 by Soravis Srinawakoon, Sorawit Suriyakarn, and Paul Nattapatsiri, with Srinawakoon as chief executive, Suriyakarn as chief technology officer, and Nattapatsiri as chief product officer. The project is associated with Bangkok and has been delivering price data to on-chain applications since 2018.

The first version of Band ran as an Ethereum token. In 2020 the project rebuilt itself around its own chain: BandChain, built with the Cosmos SDK, with the GuanYu mainnet launching in October 2020. The Laozi upgrade that followed introduced on-chain payment for data providers and Inter-Blockchain Communication support, so that Cosmos chains could request and receive Band data natively.

The most consequential change is more recent. With the V3 upgrade, BandChain narrowed its focus to price data specifically, trading the generality of arbitrary oracle scripts for much faster and more predictable price updates. Anyone reading older material about Band should treat the request-driven, general-purpose oracle description as the earlier design rather than the current emphasis.

How Band Protocol Works

Band's current pipeline has three stages, and understanding them explains most of the vocabulary in its documentation.

1. The community decides what gets fed The Signaling Hub is where BAND delegators vote on which price symbols BandChain should maintain. Voting power is proportional to staked BAND, and the more power a symbol accumulates, the shorter its guaranteed feeding interval becomes. Governance parameters set the floor and ceiling for that interval, the power step between tiers, and the maximum number of supported feeds.

2. Validators feed prices continuously Under Band's Price Stream service, implemented as the chain's feeds module, validators are obliged to keep submitting prices for every active signal at its assigned interval. A validator that fails to do so is deactivated and loses part of its revenue, and its delegators lose with it. Band does not prescribe where validators source raw prices, but it does require them to disclose their methods, and it publishes an open-source reference implementation for the job.

3. Data is delivered to other chains A Data Tunnel watches the price stream and produces packets whenever a delivery condition is met: either the feeding interval has elapsed, or the price has moved beyond a configured deviation. Those packets are then routed to the destination chain. The party who creates a tunnel funds it in BAND and is responsible for topping it up, since each delivery costs money and an empty tunnel is deactivated.

Key Ecosystem Components

Named parts of the system worth knowing:

• BandChain, the Cosmos SDK chain that performs the oracle work and secures it with staked BAND
• Signaling Hub, the coordination layer that decides which symbols are fed and how often
• The Price Stream service, delivered by the feeds module, which places a standing obligation on validators to publish prices rather than wait for requests
• Data Tunnel, the delivery mechanism, with route types covering Inter-Blockchain Communication, IBC hooks into WASM contracts, third-party interoperability routers, and threshold signatures
• The bandtss module, BandChain's native threshold signature scheme, which lets a group of members co-sign data so a destination chain can verify it cheaply without a multisignature scheme or a third-party bridge
• Grogu and Bothan, the reference programs validators run to query data sources and submit signed prices, using a separate feeder account so the validator key itself is not exposed on an always-on server
• Cylinder, the client run by threshold signature group members to handle key generation and signing
• Falcon, a relayer that carries signed tunnel output to a target contract and charges a relay fee
• Band VRF, a verifiable random function service for applications that need tamper-resistant randomness
• StdReferenceProxy contracts, the on-chain read interface deployed across supported destination networks

BAND Token Utility

BAND has a compact set of jobs:

• Staking and delegation, which secure BandChain and select its validator set. The top 100 candidates by stake become active validators.
• Signaling, since the same staked BAND also carries voting power in the Signaling Hub over which symbols get fed and how frequently. An address that has voted cannot undelegate below its committed signaling power without resubmitting its vote, and liquid-staked stBAND holders can participate too.
• Governance, where delegators vote on proposals with power proportional to bonded stake. If a delegator does not vote, the validator's vote applies on its behalf, and an explicit delegator vote overrides it.
• Paying for delivery, since tunnel creators fund tunnels in BAND to cover the cost of pushing data to destination chains.

BAND is inflationary rather than capped. New tokens are minted at an annual rate that moves within a 7 percent to 20 percent band, adjusted to target roughly 66 percent of supply being staked, and 2 percent of block rewards are diverted to a community fund pool. An ERC-20 representation of BAND also exists on Ethereum, and bridged forms circulate on networks such as Fantom and, over IBC, Osmosis.

What Makes Band Protocol Unique?

Three things stand out. First, the oracle work happens on a dedicated chain with its own validator set and its own economics, rather than as a service layered on a general-purpose network. Second, the community, not a company, decides which assets are worth feeding: the Signaling Hub converts staked tokens directly into feed coverage and update frequency. Third, verification uses a native threshold signature scheme, so a receiving contract can check a signature rather than trust an intermediary bridge or a separate consensus system.

How Band Protocol Differs from Similar Oracles

Set against other oracle designs:

• Band operates its own sovereign chain, whereas several competitors deploy node networks directly onto each destination chain
• Feed coverage is governed by token-weighted signaling, rather than being chosen by the oracle operator or negotiated per client
• Delivery is push-based on interval and deviation triggers, which suits applications that need a value already sitting on chain
• Data verification is available natively through threshold signatures, avoiding dependence on a separate messaging network for the trust step
• Off-chain consumption of BandChain price data is published as a free public good, which is unusual among commercial oracle providers

Use Cases of Band Protocol

Applications that rely on Band data include:

• Lending markets and money markets that need collateral prices for liquidations
• Derivatives, perpetuals, and synthetic asset platforms
• Stablecoin and tokenization systems that reference external values
• Insurance and prediction products settling against real-world outcomes
• Games and lotteries that need verifiable randomness through Band VRF
• Off-chain analytics and AI systems consuming the public price stream

How Band Protocol Is Secured

BandChain uses delegated proof of stake. Validators bond BAND, delegators can add stake to a validator and share its rewards, and both are exposed to the same penalties. Validators are slashed for excessive downtime, for double signing, and for failing to respond to data requests. Feed obligations add a second layer: a validator that stops submitting signal prices at the required interval is deactivated and loses revenue, which passes through to its delegators.

Data quality itself is not enforced purely by code. Validators must disclose how they source prices for each symbol, and it is left to token holders to choose validators on the strength of those disclosures. On the delivery side, threshold signatures let a destination contract verify that a quorum of the group signed the data.

Risks and Considerations

• Data source risk remains. Band aggregates across validators, but validators can share upstream sources, so a widely used bad feed can propagate.
• Delegator responsibility is real. Because Band explicitly leaves sourcing methodology to validators, choosing a validator carelessly is a genuine quality risk.
• Inflation dilutes non-stakers. With supply expanding to target a bonded ratio, holders who do not stake lose relative share over time.
• Coverage depends on signaling. A symbol nobody votes for will not be fed, so an application must ensure its symbols attract enough power.
• Tunnels can go dark. If a tunnel creator lets its balance run out, deliveries stop, and the responsibility for monitoring sits with the creator.
• Oracles are a competitive, consolidating market, and integration wins can be won or lost quickly.
• Bridged BAND on other networks carries the risk of whichever bridge issued it.

Why Band Protocol Matters

Oracles are the point where blockchains meet reality, and a mistake there is not a minor bug: it is a bad liquidation, a mispriced loan, or a drained pool. Band matters because it has been shipping this infrastructure since 2018, has been willing to rebuild itself twice, and encodes an unusual governance idea, that the token holders who bear the risk should also decide what data is worth maintaining.

Where Can You Buy Band Protocol (BAND)?

BAND is listed on many centralized exchanges, both against stablecoins and in local currency pairs on regional venues. Bridged BAND is also tradable on decentralized exchanges. Availability and pairs vary by jurisdiction.

Major Centralized Exchanges (CEX)

BAND is commonly available on:

• Binance
• OKX
• Kraken
• HTX
• WhiteBIT

Common pairs include BAND against major stablecoins where supported.

Storage Options After Purchase

BAND can be stored:

• On an exchange, under that exchange's custody
• In a Cosmos-compatible wallet holding native BAND, which is what you need in order to delegate to a validator, signal symbols, or vote
• In an Ethereum or EVM wallet if you hold an ERC-20 or bridged representation
• Behind a hardware wallet paired with compatible wallet software

Native BAND and bridged BAND are not interchangeable without a transfer step, so confirm which form you hold and verify the network before any deposit or withdrawal. Only native BAND on BandChain can be staked.

Related Coins

You can compare BAND with related oracle and data networks on Coinrithm:

• Chainlink (LINK)
• Pyth Network (PYTH)
• API3 (API3)
• UMA (UMA)
• Tellor (TRB)