BCIP-21: Governance-Gated Oracle Script & Data Source Approach

Context

This is a signaling proposal to gauge community sentiment on gating the creation and editing of oracle scripts and data sources behind on-chain governance on BandChain.

What We're Proposing

Currently, anyone can create an oracle script or data source, and the stored owner can edit it directly. We propose to restrict this — requiring a passed governance proposal for any creation or edit, regardless of who the stored owner is.

Concretely:

• CreateOracleScript / EditOracleScript will require the governance module account as signer.
• CreateDataSource / EditDataSource will require the governance module account as signer. The owner field remains intact — it is not removed. However, being the owner no longer grants the ability to create or edit directly.

Purpose

Routing oracle script and data source management through governance ensures every creation and edit is reviewed in the open, decided by the community, and permanently on the record — closing off a path that could become an attack surface.

This is a text proposal. No code changes are activated by passing it. A YES vote signals agreement with the direction, after which a formal upgrade proposal will be submitted to implement the change.

Voting Guidance

• YES → Support the direction; proceed with a formal upgrade proposal
• NO → Do not support; adjustments needed
• ABSTAIN → No strong opinion

Discussion

• Forum: https://forum.bandprotocol.com/t/text-proposal-governance-gated-oracle-script-data-source-management/386