# Provenance stamped 2026-10-07 (roadmap#943): written by an API Evangelist sweep (dated 2026-06-13 by the file itself), not
# harvested from the provider. `method: generated` so the economics campaign may replace it with a
# dated, verbatim transcription; every figure below is unverified until it does.
method: generated
generated: '2026-06-13'
specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
provider: Band Protocol
providerId: band-protocol
created: '2026-06-13'
modified: '2026-06-13'
reconciled: true
tags:
  - FinOps
  - Cost Management
  - Blockchain
  - Oracle
  - BAND Token
description: >-
  FOCUS-aligned FinOps for Band Protocol: costs arise from on-chain BAND token gas fees for
  data requests and transactions, plus optional infrastructure costs for running validator or
  full-node hardware. Read-only API access is free.
sources:
  - https://docs.bandchain.org/develop/api-endpoints
  - https://docs.bandchain.org/introduction/how-bandchain-works
  - https://docs.bandchain.org/node-validators/overview
alignedWith:
  framework: FinOps Foundation Framework
  frameworkUrl: https://www.finops.org/framework/
  dataSpec: FOCUS
  dataSpecVersion: '1.3'
  dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/
publisherName: Band Protocol Foundation
serviceCategory: Blockchain / Data Oracle
billingModel:
  pricingCategory: Gas Fees + Infrastructure
  billingFrequency: Per Transaction (on-chain, immediate)
  billingCurrency: BAND / uband
  chargeCategories:
    - Usage
    - Infrastructure
focusColumns:
  ServiceName: BandChain
  ServiceCategory: Blockchain / Oracle
  ProviderName: Band Protocol
  PublisherName: Band Protocol Foundation
  InvoiceIssuerName: Decentralized (no centralized invoice)
  BillingCurrency: BAND (uband)
meters:
  - name: data_requests
    unit: transaction
    aggregation: sum
    dimensions:
      - oracle_script_id
      - ask_count
      - min_count
      - validator_count
  - name: gas_consumed
    unit: uband
    aggregation: sum
    dimensions:
      - transaction_type
      - oracle_script_id
  - name: data_source_fees
    unit: uband
    aggregation: sum
    dimensions:
      - data_source_id
      - oracle_script_id
  - name: validator_infrastructure
    unit: USD
    aggregation: sum
    dimensions:
      - cloud_provider
      - region
      - instance_type
  - name: band_token_stake
    unit: BAND
    aggregation: point_in_time
    dimensions:
      - validator_address
principles:
  - name: Visibility
    description: >-
      Monitor on-chain transaction costs via the BandChain block explorer (cosmoscan.io) or
      by indexing MsgRequestData events. Track gas consumption and data source fees per
      oracle script to understand cost drivers.
  - name: Allocation
    description: >-
      Tag data requests with meaningful client IDs and oracle script IDs to allocate oracle
      query costs across teams, products, or use cases. Use separate BandChain addresses
      per cost center.
  - name: Optimization
    description: >-
      Optimize oracle request costs by tuning ask_count and min_count parameters — fewer
      validators reduce fees. Batch price lookups and cache results where data freshness
      allows. Use the free REST API for historical queries rather than triggering new
      on-chain requests.
  - name: Accountability
    description: >-
      Reconcile monthly BAND token expenditure against budget by exporting transaction
      history from cosmoscan.io. For validator operators, track block reward income against
      infrastructure costs to assess node profitability.