Band Protocol Oracle Integration

Band Protocol Integration (Oracles)

Band Protocol — cross-chain oracle on top of BandChain — specialized blockchain on Cosmos SDK optimized for oracle data. Unlike Chainlink and Pyth, Band not just provides price data — allows creating custom oracle scripts in Owanscript (OWasm) for any verifiable data.

Band Protocol Architecture

BandChain: separate blockchain where validators execute data requests. Validators fetch data from external API, aggregate, publish on-chain.

Oracle Scripts: Owanscript programs on BandChain defining how to aggregate data. Analog of Chainlink custom jobs.

Data Sources: verified data sources on BandChain (CoinGecko, Binance, CryptoCompare).

IBC + Bridges: oracle results transmitted to other chains via IBC (Cosmos) or Bridge contracts (EVM).

EVM Integration

Standard Reference Data

For standard prices (BTC/USD, ETH/USD, etc.):

interface IStdReference {
    struct ReferenceData {
        uint256 rate;
        uint256 lastUpdatedBase;
        uint256 lastUpdatedQuote;
    }
    
    function getReferenceData(string memory _base, string memory _quote)
        external view returns (ReferenceData memory);
}

contract BandConsumer {
    IStdReference ref;
    
    function getPrice(string memory symbol) external view returns (uint256) {
        IStdReference.ReferenceData memory data = ref.getReferenceData(symbol, "USD");
        require(block.timestamp - data.lastUpdatedBase < 3600, "Stale price");
        return data.rate; // 18 decimals
    }
}

Custom Oracle Script

Band's advantage — custom data requests via oracle scripts.

Cosmos Integration via IBC

If protocol on Cosmos-compatible chain (Osmosis, Juno, Terra 2.0) — native IBC integration.

Comparison with Chainlink

Band Protocol — good choice for Cosmos ecosystem and custom data feeds. For Ethereum mainnet DeFi — Chainlink remains standard.

Band integration — several hours for standard feeds. Custom oracle script — 1-2 weeks.