{"proposals":[{"id":"22","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-169","substitute_client_id":"07-tendermint-397","signer":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"68326565343891","abstain_count":"0","no_count":"9863694","no_with_veto_count":"0"},"submit_time":"2026-09-30T13:22:56.173539219Z","deposit_end_time":"2026-10-05T13:22:56.173539219Z","total_deposit":[{"denom":"uband","amount":"1010000000"}],"voting_start_time":"2026-10-01T06:09:14.291320546Z","voting_end_time":"2026-10-06T06:09:14.291320546Z","metadata":"Stride light client recovery on BandChain (07-tendermint-169 -\u003e 07-tendermint-397)","title":"Recover expired Stride light client 07-tendermint-169","summary":"The Stride light client 07-tendermint-169 on BandChain expired on 2026-08-17 (last consensus state 2026-08-05; 11.9-day trusting period lapsed). This client backs connection-150, the counterparty of Stride's connection-146, which carries every interchain account Stride uses to liquid stake BAND (delegation, withdrawal, fee, redemption and community-pool ICAs) and the transfer channel pair channel-258 (Stride) / channel-161 (Band). With the client expired, Stride cannot operate the BAND host zone at all: ~1,060 BAND of completed unbondings are stranded in the delegation ICA (band1r9sw8tc4z8sgzy8nvkzes4t7qset9seqwr7854phphlp9wkxs3vqlnj5g3) waiting to be swept back to redeeming users, two further redemption batches (~126.6 BAND) cannot begin unbonding, ~44 BAND of accrued rewards sit unclaimed in the withdrawal ICA, and ~513,000 BAND of delegations cannot be rebalanced or compounded. This proposal substitutes the expired client with 07-tendermint-397, a freshly created and actively maintained Stride client with identical parameters (chain-id stride-1, 1/3 trust level, 1026000s trusting period, 1209600s unbonding period, 600s max clock drift, same upgrade path). Client recovery via governance is the standard IBC procedure (ibc-go ADR-026 / MsgRecoverClient): it only refreshes the existing connection's light client, moves no funds, and grants no privileges to anyone.","proposer":"band19yqk6z9easklkzej7w5gxasy5fnqe5wgz08upw","expedited":false,"failed_reason":""},{"id":"21","messages":[],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"69290119455544","abstain_count":"0","no_count":"0","no_with_veto_count":"0"},"submit_time":"2026-08-06T07:56:24.001457936Z","deposit_end_time":"2026-08-11T07:56:24.001457936Z","total_deposit":[{"denom":"uband","amount":"1010000000"}],"voting_start_time":"2026-08-06T08:42:28.105036666Z","voting_end_time":"2026-08-11T08:42:28.105036666Z","metadata":"ipfs://CID","title":"BCIP-21: Governance-Gated Oracle Script \u0026 Data Source Approach","summary":"## Context \nThis 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.\n### What We're Proposing\nCurrently, 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.\n### Concretely:\n- CreateOracleScript / EditOracleScript will require the governance module account as signer.\n- CreateDataSource / EditDataSource will require the governance module account as signer.\nThe owner field remains intact — it is not removed. However, being the owner no longer grants the ability to create or edit directly.\n### Purpose\nRouting 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.\n\nThis 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.\n## Voting Guidance\n- YES → Support the direction; proceed with a formal upgrade proposal\n- NO → Do not support; adjustments needed\n- ABSTAIN → No strong opinion\n\n## Discussion\n- Forum: https://forum.bandprotocol.com/t/text-proposal-governance-gated-oracle-script-data-source-management/386","proposer":"band1xz5zcr3c97u99lxgr5u54uhx43t62fpzedevhq","expedited":false,"failed_reason":""},{"id":"20","messages":[],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"71433698796579","abstain_count":"0","no_count":"186999999","no_with_veto_count":"0"},"submit_time":"2026-04-23T07:27:56.528304298Z","deposit_end_time":"2026-04-28T07:27:56.528304298Z","total_deposit":[{"denom":"uband","amount":"1010000000"}],"voting_start_time":"2026-04-23T08:33:44.625096901Z","voting_end_time":"2026-04-28T08:33:44.625096901Z","metadata":"ipfs://CID","title":"BCIP-20: Upgrade to v3.1.3 - Height Deadline Confirmation","summary":"## Context \nFollowing the approval of BCIP-19 (https://www.cosmoscan.io/proposal/19), this proposal confirms the upgrade height deadline for v3.1.3 on mainnet.\n\nThe upgrade will follow a soft upgrade approach:\n-  The chain continues using the current logic until the specified block height\n-  New logic is activated automatically after that height\n\nValidators are required to upgrade their node to v3.1.3 before the deadline below.\n## Upgrade Schedule\n- Upgrade deadline: Height 64214000 (estimated time: 07 May 2026 08:00 UTC Time)\n- Network: Mainnet\n\nAll validators should complete the upgrade before this height to ensure a smooth transition.\n## Voting Guidance\n- YES → Agree with the proposed upgrade deadline\n- NO → Disagree with the deadline or request adjustments\n- ABSTAIN → No strong opinion on the proposed deadline","proposer":"band1xz5zcr3c97u99lxgr5u54uhx43t62fpzedevhq","expedited":false,"failed_reason":""},{"id":"19","messages":[],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"63591400129290","abstain_count":"0","no_count":"186999999","no_with_veto_count":"0"},"submit_time":"2026-04-03T08:48:18.667029918Z","deposit_end_time":"2026-04-08T08:48:18.667029918Z","total_deposit":[{"denom":"uband","amount":"1010000000"}],"voting_start_time":"2026-04-03T10:18:58.457848954Z","voting_end_time":"2026-04-08T10:18:58.457848954Z","metadata":"ipfs://CID","title":"BCIP-19: BandChain Upgrade v3.1.3 Approach","summary":"## Context \nThis proposal introduces an upgrade to BandChain including:\n- Dependency updates\n- A change in tunnel behavior to allow soft deviation to no longer be restricted by parameters, meaning:\n   - No minimum restriction for soft deviation\n   - Soft deviation must still be ≤ hard deviation\n   - Supports use cases where all signal prices must be included in every update packet\n\nThe upgrade follows a soft upgrade approach:\n- Current logic is used until a specified block height\n- New logic activates automatically after that height\n\n## Voting\nPlease vote on the governance proposal using:\n- YES → Support this upgrade and approach\n- NO → Do not support or think changes are needed\n- ABSTAIN → No strong opinion on the proposal, but still participate in voting to support quorum\n\n## Discussion\nFor more detailed information, rationale, and implementation approach, please refer to the forum discussion below.\n\nFeedback, concerns, or alternative suggestions are encouraged to be shared there during the voting period.\n- Forum: https://forum.bandprotocol.com/t/proposal-bandchain-upgrade-v3-1-3/368","proposer":"band1xz5zcr3c97u99lxgr5u54uhx43t62fpzedevhq","expedited":false,"failed_reason":""},{"id":"18","messages":[{"@type":"/ibc.core.client.v1.MsgRecoverClient","subject_client_id":"07-tendermint-169","substitute_client_id":"07-tendermint-380","signer":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"69429861765720","abstain_count":"0","no_count":"0","no_with_veto_count":"0"},"submit_time":"2026-01-16T11:05:31.976343762Z","deposit_end_time":"2026-01-21T11:05:31.976343762Z","total_deposit":[{"denom":"uband","amount":"1000000000"}],"voting_start_time":"2026-01-16T11:05:31.976343762Z","voting_end_time":"2026-01-21T11:05:31.976343762Z","metadata":"","title":"Recover IBC light client for Stride","summary":"This proposal updates the expired IBC light client `07-tendermint-169` for counterparty chain `stride-1` with the state of the newly created substitute client `07-tendermint-380`","proposer":"band1705swa2kgn9pvancafzl254f63a3jda928d3qk","expedited":false,"failed_reason":""},{"id":"17","messages":[{"@type":"/cosmos.staking.v1beta1.MsgUpdateParams","authority":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm","params":{"unbonding_time":"1814400s","max_validators":53,"max_entries":7,"historical_entries":10000,"bond_denom":"uband","min_commission_rate":"0.000000000000000000"}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"80831763593432","abstain_count":"314420806686","no_count":"0","no_with_veto_count":"17910827159"},"submit_time":"2025-10-01T08:34:24.667534867Z","deposit_end_time":"2025-10-06T08:34:24.667534867Z","total_deposit":[{"denom":"uband","amount":"1010000000"}],"voting_start_time":"2025-10-01T08:49:58.889759740Z","voting_end_time":"2025-10-06T08:49:58.889759740Z","metadata":"ipfs://CID","title":"BCIP-17: Strengthening Validator Operations for Band v3","summary":"## Overview\nWe recently launched Band v3, an upgraded version of BandChain that is faster, cheaper, and capable of handling much higher throughput. This marks a significant step forward in the performance and scalability of the network.\n\n## Importance of Validators\nValidators are essential to BandChain’s stability and efficiency. They:\n - Fetch price data directly from key sources, including CEXs, DEXs, and aggregators.\n - Maintain high uptime to ensure uninterrupted block production and secure network operations.\n\nWith BandChain’s reduced block time of ~1 second, downtime or delays are more critical than ever. Validators must maintain over 99% uptime to prevent missed blocks and keep the chain running smoothly.\n\n## Upgrade-Driven Changes\nAs part of the Band v3 upgrade, we have reduced the number of active validators from 100 to 53. This strategic change delivers several key benefits:\n 1. Closer Collaboration\n - Enables more direct communication between the Band Foundation and active validators.\n 2. Faster Coordination\n - Simplifies upgrades and allows quicker responses during both minor and major network updates.\n 3. Stronger Alignment and Incentives\n - With fewer active validators, each carries greater responsibility and stronger incentives to maintain high performance and align with the network’s long-term goals.\n\n## Conclusion\nBy reducing the validator set and emphasizing operational excellence, Band v3 creates a tighter, more efficient, and better-coordinated validator ecosystem, ensuring the network continues to grow securely and reliably.","proposer":"band1xz5zcr3c97u99lxgr5u54uhx43t62fpzedevhq","expedited":false,"failed_reason":""},{"id":"16","messages":[{"@type":"/band.bandtss.v1beta1.MsgTransitionGroup","members":["band1r00x80djyu6wkxpceegmvn5w9nx65prgvpz48t","band1f6htx23e4xfu0dkpa2ck2kk63la2ej94jwyvt7","band1wja9nds8klxcjurvxerdsun4t52zfjvqdy7837","band1m88fha4982ev7smptzu8a7wvt8wkxdvf4cnf7x","band128dkddh98pfwdxg07t36fxedczthg0p2hmunsp","band1ycs4g7xu8wmf7n4vwwtfsvhtfm7tekvw683qrf","band17d3uhcjlh4jyqcep82jfsrg8avsngklx2thhwr","band1c9ye54e3pzwm3e0zpdlel6pnavrj9qqvlrnumc","band1q894x7p4ugl3q5l47e8ksll5k5lmx74f2kap30","band14kn0kk33szpwus9nh8n87fjel8djx0y0z5sv0f","band1p26kdh5fx24qz9xa5jtjje8ha8ee9q44l45mzn","band1nqmeykpnqdccxf2kfqnwszy748ll3qlzsen6pq"],"threshold":"8","exec_time":"2025-08-07T07:00:00Z","authority":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"67262215305884","abstain_count":"1555050061549","no_count":"0","no_with_veto_count":"0"},"submit_time":"2025-07-31T06:17:06.193244236Z","deposit_end_time":"2025-08-05T06:17:06.193244236Z","total_deposit":[{"denom":"uband","amount":"1010000000"}],"voting_start_time":"2025-07-31T07:18:55.325203537Z","voting_end_time":"2025-08-05T07:18:55.325203537Z","metadata":"ipfs://CID","title":"BCIP-16: Launching the First TSS Group on BandChain","summary":"This proposal aims to launch the first Threshold Signature Scheme (TSS) group on BandChain, using the bandtss module. The group will consist of 12 validators, and any message will require at least 8 signatures to be considered valid.\n\nAs this is the first TSS group, we are selecting validators who have worked closely with the Band Protocol team during the development and testing phases. Their familiarity with the system and continued collaboration make them well-qualified to help ensure a successful launch.\n\n**Initial validator set for the first TSS group:**\n\n| Validator Name   | Address                                      |\n|------------------|----------------------------------------------|\n| Dijkstra         | band1r00x80djyu6wkxpceegmvn5w9nx65prgvpz48t  |\n| Kruskal          | band1f6htx23e4xfu0dkpa2ck2kk63la2ej94jwyvt7  |\n| Knuth            | band1wja9nds8klxcjurvxerdsun4t52zfjvqdy7837  |\n| Tarjan           | band1m88fha4982ev7smptzu8a7wvt8wkxdvf4cnf7x  |\n| Hamming          | band128dkddh98pfwdxg07t36fxedczthg0p2hmunsp  |\n| Sorawit          | band1ycs4g7xu8wmf7n4vwwtfsvhtfm7tekvw683qrf  |\n| Cosmostation     | band17d3uhcjlh4jyqcep82jfsrg8avsngklx2thhwr  |\n| Nansen           | band1c9ye54e3pzwm3e0zpdlel6pnavrj9qqvlrnumc  |\n| B-Harvest        | band1q894x7p4ugl3q5l47e8ksll5k5lmx74f2kap30  |\n| Forbole          | band14kn0kk33szpwus9nh8n87fjel8djx0y0z5sv0f  |\n| Stakecito        | band1p26kdh5fx24qz9xa5jtjje8ha8ee9q44l45mzn  |\n| Active Nodes     | band1nqmeykpnqdccxf2kfqnwszy748ll3qlzsen6pq  |\n\n\u0026nbsp;\n\nWe sincerely appreciate the continued contributions of all validators in the BandChain community. Your support is essential to the growth and success of the network.","proposer":"band1xz5zcr3c97u99lxgr5u54uhx43t62fpzedevhq","expedited":false,"failed_reason":""},{"id":"15","messages":[{"@type":"/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade","authority":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm","plan":{"name":"v3_1","time":"0001-01-01T00:00:00Z","height":"42450000","info":"","upgraded_client_state":null}}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"69360664499400","abstain_count":"1029212905675","no_count":"0","no_with_veto_count":"0"},"submit_time":"2025-07-12T03:49:42.553870285Z","deposit_end_time":"2025-07-17T03:49:42.553870285Z","total_deposit":[{"denom":"uband","amount":"1010000000"}],"voting_start_time":"2025-07-12T04:21:34.334028944Z","voting_end_time":"2025-07-17T04:21:34.334028944Z","metadata":"ipfs://CID","title":"BCIP-15: Upgrade to v3.1","summary":"## Context \nThe purpose of this proposal is to upgrade BandChain to v3.1. This upgrade will roll-out these features on BandChain.\n\n- Bump cosmos-sdk version to v0.50.14. \n\n## Upgrade block and date: \nThis upgrade is expected to occur at block 42450000. (Estimate date is July 17, 2025 at 12:00 UTC)","proposer":"band1xz5zcr3c97u99lxgr5u54uhx43t62fpzedevhq","expedited":false,"failed_reason":""},{"id":"14","messages":[{"@type":"/cosmos.gov.v1.MsgExecLegacyContent","content":{"@type":"/cosmos.upgrade.v1beta1.SoftwareUpgradeProposal","title":"BCIP-14: Upgrade to v3","description":"## Context\nThe purpose of this proposal is to upgrade BandChain to v3. This upgrade will roll-out these features on BandChain.\n\n- Bump Go to v1.24.2, Cosmos SDK to v0.50.13, CometBFT to v0.38.17, IBC-Go to v8.7.0, go-owasm to v0.3.1\n- Add new modules: tss, bandtss, feeds, tunnel, restake, rollingseed, and globalfee.\n- Introduce new mempool with transaction lanes and prioritization\n- Add Grogu and Cylinder programs to support feed price submission and TSS operations\n\n## Upgrade block and date\nThis upgrade is expected to occur at block 42051400. (Estimated date: July 8, 2025 at 12:00 UTC)\n\n## On-Chain Upgrade Process\nWhen the network reaches the halt height, the BandChain state machine will stop. Validators and node operators must replace the binary with the v3 version. We recommend using Cosmovisor to handle the upgrade automatically. The chain will resume from the same height with full history.\n","plan":{"name":"v3","time":"0001-01-01T00:00:00Z","height":"42051400","info":"","upgraded_client_state":null}},"authority":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"66206566899873","abstain_count":"552827910987","no_count":"0","no_with_veto_count":"0"},"submit_time":"2025-06-23T10:52:23.371799546Z","deposit_end_time":"2025-07-07T10:52:23.371799546Z","total_deposit":[{"denom":"uband","amount":"1000000000"}],"voting_start_time":"2025-06-23T16:28:23.120087960Z","voting_end_time":"2025-07-07T16:28:23.120087960Z","metadata":"","title":"BCIP-14: Upgrade to v3","summary":"## Context\nThe purpose of this proposal is to upgrade BandChain to v3. This upgrade will roll-out these features on BandChain.\n\n- Bump Go to v1.24.2, Cosmos SDK to v0.50.13, CometBFT to v0.38.17, IBC-Go to v8.7.0, go-owasm to v0.3.1\n- Add new modules: tss, bandtss, feeds, tunnel, restake, rollingseed, and globalfee.\n- Introduce new mempool with transaction lanes and prioritization\n- Add Grogu and Cylinder programs to support feed price submission and TSS operations\n\n## Upgrade block and date\nThis upgrade is expected to occur at block 42051400. (Estimated date: July 8, 2025 at 12:00 UTC)\n\n## On-Chain Upgrade Process\nWhen the network reaches the halt height, the BandChain state machine will stop. Validators and node operators must replace the binary with the v3 version. We recommend using Cosmovisor to handle the upgrade automatically. The chain will resume from the same height with full history.\n","proposer":"","expedited":false,"failed_reason":""},{"id":"13","messages":[{"@type":"/cosmos.gov.v1.MsgExecLegacyContent","content":{"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"BCIP-12: Increase the maximum data size for oracle module","description":"## Context\nThe purpose of this proposal is to adjust two parameters, specifically `MAX_CALLDATA_SIZE` and `MAX_REPORT_DATA_SIZE`, in order to expand the new use-cases of the Band Oracle. This expansion is particularly needed for oracle data generated by generative AI which requires larger input and output sizes.\n\nThe proposed changes are as follows:\n- Increasing `MAX_CALLDATA_SIZE` from 256 to 4096 to allow for a larger maximum byte size of calldata.\n- Increasing `MAX_REPORT_DATA_SIZE` from 512 to 4096 to enable a larger maximum byte size for reports from validators.\n\n## Effects\n**For All Validators:** All validators providing oracle data will need to adjust `MAX_DATA_SIZE` in the data source executor to 4096.\n\n**For Users/Developers:** They will be able to create DS/OS with larger input and output.","changes":[{"subspace":"oracle","key":"MaxCalldataSize","value":"\"4096\""},{"subspace":"oracle","key":"MaxReportDataSize","value":"\"4096\""}]},"authority":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"39966022610798","abstain_count":"42720551391023","no_count":"64568353","no_with_veto_count":"0"},"submit_time":"2024-03-12T08:51:21.404932912Z","deposit_end_time":"2024-03-26T08:51:21.404932912Z","total_deposit":[{"denom":"uband","amount":"1000001000"}],"voting_start_time":"2024-03-12T13:47:34.182097992Z","voting_end_time":"2024-03-26T13:47:34.182097992Z","metadata":"","title":"BCIP-12: Increase the maximum data size for oracle module","summary":"## Context\nThe purpose of this proposal is to adjust two parameters, specifically `MAX_CALLDATA_SIZE` and `MAX_REPORT_DATA_SIZE`, in order to expand the new use-cases of the Band Oracle. This expansion is particularly needed for oracle data generated by generative AI which requires larger input and output sizes.\n\nThe proposed changes are as follows:\n- Increasing `MAX_CALLDATA_SIZE` from 256 to 4096 to allow for a larger maximum byte size of calldata.\n- Increasing `MAX_REPORT_DATA_SIZE` from 512 to 4096 to enable a larger maximum byte size for reports from validators.\n\n## Effects\n**For All Validators:** All validators providing oracle data will need to adjust `MAX_DATA_SIZE` in the data source executor to 4096.\n\n**For Users/Developers:** They will be able to create DS/OS with larger input and output.","proposer":"","expedited":false,"failed_reason":""},{"id":"12","messages":[{"@type":"/cosmos.gov.v1.MsgExecLegacyContent","content":{"@type":"/cosmos.distribution.v1beta1.CommunityPoolSpendProposal","title":"Band Protocol Grants Program","description":"## Summary\n\n- As part of our overall decentralization roadmap, this proposal aims to establish the official Band Protocol Grants Program for the Band community.\n- The purpose of this proposal is to secure funding from the community pool of Band Protocol in order to support the official Band Protocol Grants Program and advance the growth of the Band Protocol community\n- As of the date of submission, we are seeking approximately 20% (or 150k BAND) of the total funds available in the community pool, which currently stands at ~800,000 BAND. This pool, derived from 2% of block rewards and network fee, has remained untouched thus far.\n- The requested funds will be allocated to support contributors in the first wave of the grant program. The grant program operates on a four-wave per year basis, with a maximum funding limit of 150,000 BAND per wave. To reinforce the decentralization of the network, the proposed grant program will be governed by the existing Band token holders.\n- All BandChain Grants Proposals (BCGPs) will undergo a review process led by the grants team lead and will be reviewed by three supported reviewers using the BCGPs process\n- The grants program will commence once the proposal has been approved.\n\n\n## Purpose\n\nTo successfully achieve decentralization, Band Protocol recognizes the importance of building a robust and active community. As part of our ongoing efforts to further decentralize the network, we are introducing a grant program that will be governed by the existing Band token holders.\n\nThe primary objective of Grants program is to enhance the Band community and increase the long-term effectiveness of BandChain by rewarding individuals who contribute values that support BandChain. \n\n\nThe grants program aims to:\n\n- Expand the Band ecosystem, funds will be provided for development activities aimed at adding value and ensuring the long-term success of BandChain.\n- Support and fund innovative ideas that enhance the Band ecosystem.\n- Provide funding for value-added projects, ideas, and community events to encourage more active participation from contributors. The growth of the Band ecosystem depends on the community, and this will benefit it while attracting new members to the Band community.\n\nFrom onset, BandChain has maintained Band tokens in its community pool, which steadily increases by around 19,000 BAND per month through the allocation of 2% of block rewards and network fee. And so far this has accumulated 800,000 BAND which have not been utilized before and it is essential to actively utilize these funds to add value to the protocol and its ecosystem. As part of an effort to further decentralize the network, we are proposing a grant program governed by the current Band token holders.\n\nThe grants program will establish a maximum funding limit of 150,000 BAND per wave, and the program will operate on a quarterly basis, with four waves per year.\n\nThe BCGP was established with the aforementioned goal in mind, and contributors can apply for and obtain $1,000 to $50,000 worth of BAND under the funding conditions, which is a sum that would not be viable for governance funding via on-chain voting every single time. We recognize that having funding for operations and development is crucial for contributors, which is why we encourage them to be active and grow the ecosystem in the long run.\n\n## Scope of work\n\nDuring the initial phase, Band core team will help to create all the essential procedures and resources for the program, including the Grants website, Band forum, and application process. If the program operates efficiently on its own, it will slowly shift to the community, enhancing its long-term sustainability.\n\nThe program’s scope extends beyond providing funding to individual contributors, as it also encompasses talented teams that are developing value-added projects. Our objective is to support the Band Ecosystem by allocating grants to projects that generate significant benefits for the community.\n\nThere are 4 categories to support Band Ecosystem:\n\n1. **Development Grants:** Grants for developers building blockchain-based applications and services on top of a particular platform.\n2. **Research Grants:** Grants for academic or industry researchers studying various aspects of blockchain technology, such as scalability, security, privacy, and interoperability.\n3. **Community Grants:** Grants for projects that promote the adoption and growth of a particular blockchain ecosystem, such as meetups, hackathons, educational initiatives, and marketing campaigns.\n4. **Infrastructure Grants:** Grants for projects that improve the underlying infrastructure of a particular blockchain ecosystem, such as improvements to consensus algorithms, network scalability, or storage efficiency.\n\n\n\n\n## Grants Team\n\nThe initial introduction of the grants team by the core team of Band will include individuals who have been working closely with Band for over three years. These team members possess diverse skill sets, extensive experience, and share a common goal of ensuring the long-term success of BandChain.\n\nHere are the proposed initial members of the grants team:\n\n1. Grants Team Lead:\n    - Shine - Head of Operations, Band Protocol\n2. Reviewers:\n    - Swit - CTO, Band Protocol\n    - Paul - CPO, Band Protocol\n    - Queue - Senior Software Engineer, Band Protocol\n\nSince the grants team is affiliated with Band Protocol and are pre-selected for an initial starting period, they will not be compensated using the requested grants fund. Therefore, the entirety of the funds in the community pool will be dedicated solely to contributors.\n\nThe grants team will remain operational until the program achieves self-sufficiency, with a planned experimentation period of one year. Furthermore, community members will be able to volunteer and garner votes from Band token holders and the community, opening up possibilities for them to join the grants team down the line.\n\n\nThe team will have the following responsibilities:\n\n- **Operations**: As soon as the applications for the BCGP are received, the grants team will establish an efficient operational process.\n- **Review BCGP**: The team will review all applications bi-weekly.\n- **Feasibility Testing**: The team will interview contributors to clarify information, agree on funding terms and amounts, and discuss with the Band core team and advisors to ensure that the grants are valuable.\n- **BCGP Approval**: The team will approve BCGPs that meet the criteria.\n- **Provision of Funds**: The team will provide the funds as per the agreed terms of the contributor and grant team’s agreement.\n- **Follow-Up**: The team will hold a follow-up meeting with the grantee to ensure that they achieve any milestones and generate a final report for the community.\n\n## Granting Process and Timeline\n\nAfter the approval of this proposal, the grants program will initiate, comprising of four cycles annually, with each cycle spanning three months. Community members are encouraged to submit their applications through the Band forum within the designated grants program timeframe. Evaluations of the approved applications will be conducted using the BCGP processes approximately one month prior to the conclusion of each cycle. Any proposals submitted during this timeframe will be considered for the subsequent cycle.\n\nThe grants team will source and discuss potential BCGP with the Band core team and advisors to ensure that it benefits the Band ecosystem. If everyone agrees on the BCGP, the grants team will interview the contributor to clarify information, agree on milestones, funding terms, and grant amounts. The grantee will then apply for the BCGP on the grants website and prepare for the final approval.\n\nUpon submission of the BCGP on the website, the grant team will review all the information and give the final approval. After the reviewing status of BCGP changes to the implementing status, the grant team will fund the grantee within seven days following the terms of the agreement. And the fund will be paid in BAND for worldwide applicants, except for those located in the United States, who will be paid in USDC instead.","recipient":"band1y0jp7je72qr9pwkrjy4ks3zl2em6zstjmns5qh","amount":[{"denom":"uband","amount":"150000000000"}]},"authority":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"19790413643489","abstain_count":"47682210564841","no_count":"0","no_with_veto_count":"0"},"submit_time":"2023-05-30T08:13:52.399462320Z","deposit_end_time":"2023-06-13T08:13:52.399462320Z","total_deposit":[{"denom":"uband","amount":"1000000000"}],"voting_start_time":"2023-05-30T08:28:26.028941715Z","voting_end_time":"2023-06-13T08:28:26.028941715Z","metadata":"","title":"Band Protocol Grants Program","summary":"## Summary\n\n- As part of our overall decentralization roadmap, this proposal aims to establish the official Band Protocol Grants Program for the Band community.\n- The purpose of this proposal is to secure funding from the community pool of Band Protocol in order to support the official Band Protocol Grants Program and advance the growth of the Band Protocol community\n- As of the date of submission, we are seeking approximately 20% (or 150k BAND) of the total funds available in the community pool, which currently stands at ~800,000 BAND. This pool, derived from 2% of block rewards and network fee, has remained untouched thus far.\n- The requested funds will be allocated to support contributors in the first wave of the grant program. The grant program operates on a four-wave per year basis, with a maximum funding limit of 150,000 BAND per wave. To reinforce the decentralization of the network, the proposed grant program will be governed by the existing Band token holders.\n- All BandChain Grants Proposals (BCGPs) will undergo a review process led by the grants team lead and will be reviewed by three supported reviewers using the BCGPs process\n- The grants program will commence once the proposal has been approved.\n\n\n## Purpose\n\nTo successfully achieve decentralization, Band Protocol recognizes the importance of building a robust and active community. As part of our ongoing efforts to further decentralize the network, we are introducing a grant program that will be governed by the existing Band token holders.\n\nThe primary objective of Grants program is to enhance the Band community and increase the long-term effectiveness of BandChain by rewarding individuals who contribute values that support BandChain. \n\n\nThe grants program aims to:\n\n- Expand the Band ecosystem, funds will be provided for development activities aimed at adding value and ensuring the long-term success of BandChain.\n- Support and fund innovative ideas that enhance the Band ecosystem.\n- Provide funding for value-added projects, ideas, and community events to encourage more active participation from contributors. The growth of the Band ecosystem depends on the community, and this will benefit it while attracting new members to the Band community.\n\nFrom onset, BandChain has maintained Band tokens in its community pool, which steadily increases by around 19,000 BAND per month through the allocation of 2% of block rewards and network fee. And so far this has accumulated 800,000 BAND which have not been utilized before and it is essential to actively utilize these funds to add value to the protocol and its ecosystem. As part of an effort to further decentralize the network, we are proposing a grant program governed by the current Band token holders.\n\nThe grants program will establish a maximum funding limit of 150,000 BAND per wave, and the program will operate on a quarterly basis, with four waves per year.\n\nThe BCGP was established with the aforementioned goal in mind, and contributors can apply for and obtain $1,000 to $50,000 worth of BAND under the funding conditions, which is a sum that would not be viable for governance funding via on-chain voting every single time. We recognize that having funding for operations and development is crucial for contributors, which is why we encourage them to be active and grow the ecosystem in the long run.\n\n## Scope of work\n\nDuring the initial phase, Band core team will help to create all the essential procedures and resources for the program, including the Grants website, Band forum, and application process. If the program operates efficiently on its own, it will slowly shift to the community, enhancing its long-term sustainability.\n\nThe program’s scope extends beyond providing funding to individual contributors, as it also encompasses talented teams that are developing value-added projects. Our objective is to support the Band Ecosystem by allocating grants to projects that generate significant benefits for the community.\n\nThere are 4 categories to support Band Ecosystem:\n\n1. **Development Grants:** Grants for developers building blockchain-based applications and services on top of a particular platform.\n2. **Research Grants:** Grants for academic or industry researchers studying various aspects of blockchain technology, such as scalability, security, privacy, and interoperability.\n3. **Community Grants:** Grants for projects that promote the adoption and growth of a particular blockchain ecosystem, such as meetups, hackathons, educational initiatives, and marketing campaigns.\n4. **Infrastructure Grants:** Grants for projects that improve the underlying infrastructure of a particular blockchain ecosystem, such as improvements to consensus algorithms, network scalability, or storage efficiency.\n\n\n\n\n## Grants Team\n\nThe initial introduction of the grants team by the core team of Band will include individuals who have been working closely with Band for over three years. These team members possess diverse skill sets, extensive experience, and share a common goal of ensuring the long-term success of BandChain.\n\nHere are the proposed initial members of the grants team:\n\n1. Grants Team Lead:\n    - Shine - Head of Operations, Band Protocol\n2. Reviewers:\n    - Swit - CTO, Band Protocol\n    - Paul - CPO, Band Protocol\n    - Queue - Senior Software Engineer, Band Protocol\n\nSince the grants team is affiliated with Band Protocol and are pre-selected for an initial starting period, they will not be compensated using the requested grants fund. Therefore, the entirety of the funds in the community pool will be dedicated solely to contributors.\n\nThe grants team will remain operational until the program achieves self-sufficiency, with a planned experimentation period of one year. Furthermore, community members will be able to volunteer and garner votes from Band token holders and the community, opening up possibilities for them to join the grants team down the line.\n\n\nThe team will have the following responsibilities:\n\n- **Operations**: As soon as the applications for the BCGP are received, the grants team will establish an efficient operational process.\n- **Review BCGP**: The team will review all applications bi-weekly.\n- **Feasibility Testing**: The team will interview contributors to clarify information, agree on funding terms and amounts, and discuss with the Band core team and advisors to ensure that the grants are valuable.\n- **BCGP Approval**: The team will approve BCGPs that meet the criteria.\n- **Provision of Funds**: The team will provide the funds as per the agreed terms of the contributor and grant team’s agreement.\n- **Follow-Up**: The team will hold a follow-up meeting with the grantee to ensure that they achieve any milestones and generate a final report for the community.\n\n## Granting Process and Timeline\n\nAfter the approval of this proposal, the grants program will initiate, comprising of four cycles annually, with each cycle spanning three months. Community members are encouraged to submit their applications through the Band forum within the designated grants program timeframe. Evaluations of the approved applications will be conducted using the BCGP processes approximately one month prior to the conclusion of each cycle. Any proposals submitted during this timeframe will be considered for the subsequent cycle.\n\nThe grants team will source and discuss potential BCGP with the Band core team and advisors to ensure that it benefits the Band ecosystem. If everyone agrees on the BCGP, the grants team will interview the contributor to clarify information, agree on milestones, funding terms, and grant amounts. The grantee will then apply for the BCGP on the grants website and prepare for the final approval.\n\nUpon submission of the BCGP on the website, the grant team will review all the information and give the final approval. After the reviewing status of BCGP changes to the implementing status, the grant team will fund the grantee within seven days following the terms of the agreement. And the fund will be paid in BAND for worldwide applicants, except for those located in the United States, who will be paid in USDC instead.","proposer":"","expedited":false,"failed_reason":""},{"id":"11","messages":[{"@type":"/cosmos.gov.v1.MsgExecLegacyContent","content":{"@type":"/cosmos.upgrade.v1beta1.SoftwareUpgradeProposal","title":"BCIP-11: Upgrade to v2.5","description":"## Context\nThe purpose of this proposal is to upgrade the BandChain to v2.5. This upgrade will roll-out these features on BandChain\n\n- Bump ibc-go to v4.3.0 due to v3 has reached the end of life and requires coordinating upgrade\n- Bump cosmos-sdk to v0.45.15, tendermint (cometbft) to v0.34.27, and go-owasm v0.2.3\n- Support statically linked binary for bandd\n\n## Upgrade block and date\nThis upgrade is expected to occur at block 16562500. (Estimate date is April 27, 2023 at 14:00 UTC)\n\n## On-Chain Upgrade Process\nWhen the network reaches the halt height, the state machine program of the BandChain will be halted. This classic method for upgrading requires all validators and node operators to manually substitute the existing state machine binary with the new binary. We recommend validators to use Cosmovisor to swap the binaries automatically. Because it is an on-chain upgrade process, the blockchain will be continued with all the accumulated history with continuous block height.\n\nInstruction to prepare v2.5 binary: https://github.com/bandprotocol/launch/blob/master/laozi-mainnet/docs/prepare-for-upgrade-v2.5.md\n","plan":{"name":"v2_5","time":"0001-01-01T00:00:00Z","height":"16562500","info":"","upgraded_client_state":null}},"authority":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"70733404495946","abstain_count":"53167359112","no_count":"0","no_with_veto_count":"0"},"submit_time":"2023-04-11T06:25:38.713235637Z","deposit_end_time":"2023-04-25T06:25:38.713235637Z","total_deposit":[{"denom":"uband","amount":"1000000000"}],"voting_start_time":"2023-04-11T06:29:18.641565835Z","voting_end_time":"2023-04-25T06:29:18.641565835Z","metadata":"","title":"BCIP-11: Upgrade to v2.5","summary":"## Context\nThe purpose of this proposal is to upgrade the BandChain to v2.5. This upgrade will roll-out these features on BandChain\n\n- Bump ibc-go to v4.3.0 due to v3 has reached the end of life and requires coordinating upgrade\n- Bump cosmos-sdk to v0.45.15, tendermint (cometbft) to v0.34.27, and go-owasm v0.2.3\n- Support statically linked binary for bandd\n\n## Upgrade block and date\nThis upgrade is expected to occur at block 16562500. (Estimate date is April 27, 2023 at 14:00 UTC)\n\n## On-Chain Upgrade Process\nWhen the network reaches the halt height, the state machine program of the BandChain will be halted. This classic method for upgrading requires all validators and node operators to manually substitute the existing state machine binary with the new binary. We recommend validators to use Cosmovisor to swap the binaries automatically. Because it is an on-chain upgrade process, the blockchain will be continued with all the accumulated history with continuous block height.\n\nInstruction to prepare v2.5 binary: https://github.com/bandprotocol/launch/blob/master/laozi-mainnet/docs/prepare-for-upgrade-v2.5.md\n","proposer":"","expedited":false,"failed_reason":""},{"id":"10","messages":[{"@type":"/cosmos.gov.v1.MsgExecLegacyContent","content":{"@type":"/cosmos.gov.v1beta1.TextProposal","title":"BCIP-10: Introduce minimum gas price of 0.0025 uband","description":"## Context\nThe purpose of this proposal is to introduce network fees on the BandChain mainnet. The team strongly suggest validators to set the **minimum gas price** to **0.0025 uband** to achieve the below objectives:  \n\n- Prevent spam events on the BandChain\n- Provide incentive for actors to be good actors within the Band community (e.g. validators and data providers to be rewarded for completed work)\n- Progress towards a self-sustainable decentralized ecosystem\n\n## Gas price\n\nThe minimum gas price will be set to 0.0025 uband to achieve the objectives stated above. This number came as a result of experimentation and testing to strike a balance and set the gas price to discourage attacks and network spams, derived from associated costs required to perform such malicious attacks, without creating a hindrance to the services.\n\n## Decisions\n\n### Yes\n\n1. Foundation nodes will set minimum gas price on each node to 0.0025 uband on the 1st of February 2023\n2. All validators are strongly encouraged and recommended to update minimum gas price to 0.0025 uband on the 1st of February 2023\n3. The core team will prioritize implementation of minimum gas price at protocol level, which will be detailed in subsequent upgrade proposal\n\n### No\n\nA “No” result would signify that the Foundation nodes will not update minimum gas price and would force a reconsideration for the team on security\n\n## Effective date\n\nThe minimum-gas-price is to be set on the 1st of February 2023\n\n## Effects\n\nBuilders and developers of the BandChain ecosystem\n\n- Validators must update `minimum-gas-prices` in `$HOME/.band/config/app.toml`to “0.0025uband” and restart your node *on the* effective date.\n- BandChain users must update their gas_prices in transactions *before* the effective date.\n"},"authority":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"17504224442471","abstain_count":"32147784232584","no_count":"14125970","no_with_veto_count":"0"},"submit_time":"2023-01-13T11:41:26.736472477Z","deposit_end_time":"2023-01-27T11:41:26.736472477Z","total_deposit":[{"denom":"uband","amount":"1000000000"}],"voting_start_time":"2023-01-13T11:44:21.399708470Z","voting_end_time":"2023-01-27T11:44:21.399708470Z","metadata":"","title":"BCIP-10: Introduce minimum gas price of 0.0025 uband","summary":"## Context\nThe purpose of this proposal is to introduce network fees on the BandChain mainnet. The team strongly suggest validators to set the **minimum gas price** to **0.0025 uband** to achieve the below objectives:  \n\n- Prevent spam events on the BandChain\n- Provide incentive for actors to be good actors within the Band community (e.g. validators and data providers to be rewarded for completed work)\n- Progress towards a self-sustainable decentralized ecosystem\n\n## Gas price\n\nThe minimum gas price will be set to 0.0025 uband to achieve the objectives stated above. This number came as a result of experimentation and testing to strike a balance and set the gas price to discourage attacks and network spams, derived from associated costs required to perform such malicious attacks, without creating a hindrance to the services.\n\n## Decisions\n\n### Yes\n\n1. Foundation nodes will set minimum gas price on each node to 0.0025 uband on the 1st of February 2023\n2. All validators are strongly encouraged and recommended to update minimum gas price to 0.0025 uband on the 1st of February 2023\n3. The core team will prioritize implementation of minimum gas price at protocol level, which will be detailed in subsequent upgrade proposal\n\n### No\n\nA “No” result would signify that the Foundation nodes will not update minimum gas price and would force a reconsideration for the team on security\n\n## Effective date\n\nThe minimum-gas-price is to be set on the 1st of February 2023\n\n## Effects\n\nBuilders and developers of the BandChain ecosystem\n\n- Validators must update `minimum-gas-prices` in `$HOME/.band/config/app.toml`to “0.0025uband” and restart your node *on the* effective date.\n- BandChain users must update their gas_prices in transactions *before* the effective date.\n","proposer":"","expedited":false,"failed_reason":""},{"id":"9","messages":[{"@type":"/cosmos.gov.v1.MsgExecLegacyContent","content":{"@type":"/cosmos.upgrade.v1beta1.SoftwareUpgradeProposal","title":"BCIP-9: Upgrade to v2.4","description":"## Context\nThe purpose of this proposal is to upgrade the BandChain to v2.4. This upgrade will roll-out these features on Bandchain\n\n- Bump cosmos-sdk to v0.45.10 and ibc-go to v3.3.1 to fully support state sync and ICA-host\n- Increase the throughput for oracle module by ~10X from optimizing owasm runtime\n- Increase the MaxGas per block to 50M Gas\n\n## Upgrade block and date\nThis upgrade is expected to occur at block 11525000. (Estimate date is November 21, 2022 at 14:00 UTC)\n\n## On-Chain Upgrade Process\nWhen the network reaches the halt height, the state machine program of the BandChain will be halted. This classic method for upgrading requires all validators and node operators to manually substitute the existing state machine binary with the new binary. We recommend validators to use Cosmovisor to swap the binaries automatically. Because it is an on-chain upgrade process, the blockchain will be continued with all the accumulated history with continuous block height.\n\nInstruction to migrate to use cosmovisor: https://github.com/bandprotocol/launch/blob/master/laozi-mainnet/docs/migrate-bandd-binary-to-cosmovisor.md\n\nInstruction to prepare v2.4 binary: https://github.com/bandprotocol/launch/blob/master/laozi-mainnet/docs/prepare-for-upgrade-v2.4.md\n\n## Effects \n\n- Users/Developers: After the upgrade, you will need and are advised to redeploy your oracle scripts to reduce used gas for oracle requests\n\nFor full details of upgrade please see this article: https://medium.com/bandprotocol/bandchain-v2-4-upgrade-70dbb896618c\n","plan":{"name":"v2_4","time":"0001-01-01T00:00:00Z","height":"11525000","info":"","upgraded_client_state":null}},"authority":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"76973831418618","abstain_count":"0","no_count":"0","no_with_veto_count":"0"},"submit_time":"2022-11-03T09:30:05.782172574Z","deposit_end_time":"2022-11-17T09:30:05.782172574Z","total_deposit":[{"denom":"uband","amount":"1001000000"}],"voting_start_time":"2022-11-03T10:06:37.799874318Z","voting_end_time":"2022-11-17T10:06:37.799874318Z","metadata":"","title":"BCIP-9: Upgrade to v2.4","summary":"## Context\nThe purpose of this proposal is to upgrade the BandChain to v2.4. This upgrade will roll-out these features on Bandchain\n\n- Bump cosmos-sdk to v0.45.10 and ibc-go to v3.3.1 to fully support state sync and ICA-host\n- Increase the throughput for oracle module by ~10X from optimizing owasm runtime\n- Increase the MaxGas per block to 50M Gas\n\n## Upgrade block and date\nThis upgrade is expected to occur at block 11525000. (Estimate date is November 21, 2022 at 14:00 UTC)\n\n## On-Chain Upgrade Process\nWhen the network reaches the halt height, the state machine program of the BandChain will be halted. This classic method for upgrading requires all validators and node operators to manually substitute the existing state machine binary with the new binary. We recommend validators to use Cosmovisor to swap the binaries automatically. Because it is an on-chain upgrade process, the blockchain will be continued with all the accumulated history with continuous block height.\n\nInstruction to migrate to use cosmovisor: https://github.com/bandprotocol/launch/blob/master/laozi-mainnet/docs/migrate-bandd-binary-to-cosmovisor.md\n\nInstruction to prepare v2.4 binary: https://github.com/bandprotocol/launch/blob/master/laozi-mainnet/docs/prepare-for-upgrade-v2.4.md\n\n## Effects \n\n- Users/Developers: After the upgrade, you will need and are advised to redeploy your oracle scripts to reduce used gas for oracle requests\n\nFor full details of upgrade please see this article: https://medium.com/bandprotocol/bandchain-v2-4-upgrade-70dbb896618c\n","proposer":"","expedited":false,"failed_reason":""},{"id":"7","messages":[{"@type":"/cosmos.gov.v1.MsgExecLegacyContent","content":{"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"BCIP-7: Increase max_raw_request_count from 12 to 16","description":"### Context\nThe parameter max_raw_request_count sets the upper limit of how many external calls to datasource can a request make, limiting the number of sources that one request can include.\n\nThe Bandchain data ecosystems now have more data sources which can all be used to aggregate data results to secure a stronger integrity of the data request. But with the limit of `max_raw_request_count` a request can only currently call out to 12 sources.\n\nThe Band Protocol team proposes to increase the limit from 12 to 16 external calls per request. We think 16 is the number of sources that can strengthen the current requests without spamming data source execution on the validator's side.\n\t\t\n### Effects\nUsers/Developers: Able to create script and request more data sources to aggregate result.\n","changes":[{"subspace":"oracle","key":"MaxRawRequestCount","value":"\"16\""}]},"authority":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"67752085842959","abstain_count":"1541206307","no_count":"1","no_with_veto_count":"0"},"submit_time":"2022-03-11T06:30:04.307480195Z","deposit_end_time":"2022-03-25T06:30:04.307480195Z","total_deposit":[{"denom":"uband","amount":"1001000000"}],"voting_start_time":"2022-03-11T06:40:24.643109784Z","voting_end_time":"2022-03-25T06:40:24.643109784Z","metadata":"","title":"BCIP-7: Increase max_raw_request_count from 12 to 16","summary":"### Context\nThe parameter max_raw_request_count sets the upper limit of how many external calls to datasource can a request make, limiting the number of sources that one request can include.\n\nThe Bandchain data ecosystems now have more data sources which can all be used to aggregate data results to secure a stronger integrity of the data request. But with the limit of `max_raw_request_count` a request can only currently call out to 12 sources.\n\nThe Band Protocol team proposes to increase the limit from 12 to 16 external calls per request. We think 16 is the number of sources that can strengthen the current requests without spamming data source execution on the validator's side.\n\t\t\n### Effects\nUsers/Developers: Able to create script and request more data sources to aggregate result.\n","proposer":"","expedited":false,"failed_reason":""},{"id":"6","messages":[{"@type":"/cosmos.gov.v1.MsgExecLegacyContent","content":{"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"BCIP-6: Increase Block Capacity through Request Gas Parameter","description":"### Context\nWith the recent growth of usage from our partners (i.e. Mirror, Injective), there is an increase in requests that fills upto 80-90% of block’ capacity during peak periods. The proposed parameter `per_validator_request_gas` specifies the amount of gas required to process a request on BandChain per each validator that needs to report data. The parameter was originally initiated to the previous value to prevent spamming of requests to all validators. Now, with datasource fee activated on datasource ends, the parameter renders less necessary in preventing spamming and the protocol can take advantage of this to increase block capacity.\n\nThis proposal reduces `per_validator_request_gas` from 30000 to 0, decreasing the overall gas used per each request.\n\nWith each request using less gas, a block which has a gas limit of 8 million can take in more requests, allowing BandChain to process more requests in one block and increase capacity to serve growing data demand of partners. Specifically, this will increase BandChain capacity to process requests by approximately 25%.\n\n### Effects\nUsers: Faster requests and transactions on-chain.With less request size (by gas used), a block has more free capacity to process more requests and other types of transactions.\n","changes":[{"subspace":"oracle","key":"PerValidatorRequestGas","value":"\"0\""}]},"authority":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"74682907122905","abstain_count":"200000000","no_count":"0","no_with_veto_count":"0"},"submit_time":"2022-02-11T04:55:10.943189468Z","deposit_end_time":"2022-02-25T04:55:10.943189468Z","total_deposit":[{"denom":"uband","amount":"1001000000"}],"voting_start_time":"2022-02-11T04:57:45.234728553Z","voting_end_time":"2022-02-25T04:57:45.234728553Z","metadata":"","title":"BCIP-6: Increase Block Capacity through Request Gas Parameter","summary":"### Context\nWith the recent growth of usage from our partners (i.e. Mirror, Injective), there is an increase in requests that fills upto 80-90% of block’ capacity during peak periods. The proposed parameter `per_validator_request_gas` specifies the amount of gas required to process a request on BandChain per each validator that needs to report data. The parameter was originally initiated to the previous value to prevent spamming of requests to all validators. Now, with datasource fee activated on datasource ends, the parameter renders less necessary in preventing spamming and the protocol can take advantage of this to increase block capacity.\n\nThis proposal reduces `per_validator_request_gas` from 30000 to 0, decreasing the overall gas used per each request.\n\nWith each request using less gas, a block which has a gas limit of 8 million can take in more requests, allowing BandChain to process more requests in one block and increase capacity to serve growing data demand of partners. Specifically, this will increase BandChain capacity to process requests by approximately 25%.\n\n### Effects\nUsers: Faster requests and transactions on-chain.With less request size (by gas used), a block has more free capacity to process more requests and other types of transactions.\n","proposer":"","expedited":false,"failed_reason":""},{"id":"5","messages":[{"@type":"/cosmos.gov.v1.MsgExecLegacyContent","content":{"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"BCIP-5: Enable IBC Transfer","description":"The proposal enables IBC-Transfer on BandChain. If this proposal passes, IBC Transfer params will be set to true, and the historical_entries param in the staking module will be changed to 10,000 for header verification in IBC connections. BAND holders can transfer their token to our partner chains with IBC-capability and perform activity on those chains with BAND tokens. The ease of transferring enabled by this feature creates more seamless use cases of Band token which raises the value and liquidity of the token.\n\n\t","changes":[{"subspace":"staking","key":"HistoricalEntries","value":"10000"},{"subspace":"transfer","key":"SendEnabled","value":"true"},{"subspace":"transfer","key":"ReceiveEnabled","value":"true"}]},"authority":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"60161828259064","abstain_count":"0","no_count":"0","no_with_veto_count":"0"},"submit_time":"2021-10-28T12:23:00.008182224Z","deposit_end_time":"2021-11-11T12:23:00.008182224Z","total_deposit":[{"denom":"uband","amount":"1001000000"}],"voting_start_time":"2021-10-28T12:25:55.336662201Z","voting_end_time":"2021-11-11T12:25:55.336662201Z","metadata":"","title":"BCIP-5: Enable IBC Transfer","summary":"The proposal enables IBC-Transfer on BandChain. If this proposal passes, IBC Transfer params will be set to true, and the historical_entries param in the staking module will be changed to 10,000 for header verification in IBC connections. BAND holders can transfer their token to our partner chains with IBC-capability and perform activity on those chains with BAND tokens. The ease of transferring enabled by this feature creates more seamless use cases of Band token which raises the value and liquidity of the token.\n\n\t","proposer":"","expedited":false,"failed_reason":""},{"id":"4","messages":[{"@type":"/cosmos.gov.v1.MsgExecLegacyContent","content":{"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"BCIP-4: Enable IBC Oracle","description":"The proposal enables requesting an oracle data on BandChain via IBC. If this proposal passes, IBC Oracle feature on BandChain will be enabled. This means IBC-compatible chains can request oracle data, and receive the oracle results which are proved to exist on BandChain by the IBC  procedure. This will not only increase the usage of BandChain's oracle data, but also provide a secure and decentralized method for other chains to access oracle data.\n\n\t","changes":[{"subspace":"oracle","key":"IBCRequestEnabled","value":"true"}]},"authority":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"73802515005187","abstain_count":"0","no_count":"0","no_with_veto_count":"0"},"submit_time":"2021-10-01T12:57:59.998191655Z","deposit_end_time":"2021-10-15T12:57:59.998191655Z","total_deposit":[{"denom":"uband","amount":"1001000000"}],"voting_start_time":"2021-10-01T13:02:38.789629666Z","voting_end_time":"2021-10-15T13:02:38.789629666Z","metadata":"","title":"BCIP-4: Enable IBC Oracle","summary":"The proposal enables requesting an oracle data on BandChain via IBC. If this proposal passes, IBC Oracle feature on BandChain will be enabled. This means IBC-compatible chains can request oracle data, and receive the oracle results which are proved to exist on BandChain by the IBC  procedure. This will not only increase the usage of BandChain's oracle data, but also provide a secure and decentralized method for other chains to access oracle data.\n\n\t","proposer":"","expedited":false,"failed_reason":""},{"id":"3","messages":[{"@type":"/cosmos.gov.v1.MsgExecLegacyContent","content":{"@type":"/cosmos.gov.v1beta1.TextProposal","title":"BCIP-3: Laozi Upgrade Proposal B","description":"This proposal is intended to signal acceptance/rejection of the precise software release that contains changes included in the BandChain Laozi upgrade.\n\nIn this upgrade, the following code version will be used to upgrade BandChain: https://github.com/bandprotocol/chain/releases/tag/v2.3.0. We are proposing to halt band-guanyu-mainnet on September 23, 2021, 09:00:00 UTC and launching the new laozi-mainnet with the genesis time of 3 hours after the halt time of Guanyu, September 23, 2021, 12:00:00 UTC.\n\t\t\nFull proposal: https://ipfs.io/ipfs/QmSNhfzg6jUR9aBRLdpD78JQTKmnDJ9WaypTdsBmq1oVun\n\t\t\n"},"authority":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"68172490148583","abstain_count":"0","no_count":"0","no_with_veto_count":"0"},"submit_time":"2021-09-07T11:39:37.528084395Z","deposit_end_time":"2021-09-21T11:39:37.528084395Z","total_deposit":[{"denom":"uband","amount":"1001000000"}],"voting_start_time":"2021-09-07T11:41:40.697550883Z","voting_end_time":"2021-09-21T11:41:40.697550883Z","metadata":"","title":"BCIP-3: Laozi Upgrade Proposal B","summary":"This proposal is intended to signal acceptance/rejection of the precise software release that contains changes included in the BandChain Laozi upgrade.\n\nIn this upgrade, the following code version will be used to upgrade BandChain: https://github.com/bandprotocol/chain/releases/tag/v2.3.0. We are proposing to halt band-guanyu-mainnet on September 23, 2021, 09:00:00 UTC and launching the new laozi-mainnet with the genesis time of 3 hours after the halt time of Guanyu, September 23, 2021, 12:00:00 UTC.\n\t\t\nFull proposal: https://ipfs.io/ipfs/QmSNhfzg6jUR9aBRLdpD78JQTKmnDJ9WaypTdsBmq1oVun\n\t\t\n","proposer":"","expedited":false,"failed_reason":""},{"id":"2","messages":[{"@type":"/cosmos.gov.v1.MsgExecLegacyContent","content":{"@type":"/cosmos.gov.v1beta1.TextProposal","title":"BCIP-2: Laozi Upgrade Proposal","description":"This proposal is intended to signal acceptance/rejection of the precise software release that will contain the changes to be included in the BandChain Laozi upgrade.\n\nWe are proposing to use this code https://github.com/bandprotocol/chain/releases/tag/v2.0.3 to upgrade BandChain. We are proposing to export the state at block height 7486289, which we expect to occur approximately on July 13, 2021, 11:00:00 UTC. We are proposing to launch Laozi mainnet using genesis time 6 hours after the timestamp of block height 7486289.\n\t\t\nFull proposal: https://ipfs.io/ipfs/QmX3PSxcWgBfCqLkXdVq9evVYcx9bT3fNLQ9cJtFwPHzKg\n\t\t\n"},"authority":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"74265857671497","abstain_count":"0","no_count":"0","no_with_veto_count":"0"},"submit_time":"2021-06-28T12:16:30.125523469Z","deposit_end_time":"2021-07-12T12:16:30.125523469Z","total_deposit":[{"denom":"uband","amount":"1001000000"}],"voting_start_time":"2021-06-28T14:28:47.543027370Z","voting_end_time":"2021-07-12T14:28:47.543027370Z","metadata":"","title":"BCIP-2: Laozi Upgrade Proposal","summary":"This proposal is intended to signal acceptance/rejection of the precise software release that will contain the changes to be included in the BandChain Laozi upgrade.\n\nWe are proposing to use this code https://github.com/bandprotocol/chain/releases/tag/v2.0.3 to upgrade BandChain. We are proposing to export the state at block height 7486289, which we expect to occur approximately on July 13, 2021, 11:00:00 UTC. We are proposing to launch Laozi mainnet using genesis time 6 hours after the timestamp of block height 7486289.\n\t\t\nFull proposal: https://ipfs.io/ipfs/QmX3PSxcWgBfCqLkXdVq9evVYcx9bT3fNLQ9cJtFwPHzKg\n\t\t\n","proposer":"","expedited":false,"failed_reason":""},{"id":"1","messages":[{"@type":"/cosmos.gov.v1.MsgExecLegacyContent","content":{"@type":"/cosmos.gov.v1beta1.TextProposal","title":"GuanYu Upgrade Proposal","description":"This proposal is intended to signal acceptance/rejection of the precise software release that will contain the changes to be included in the GuanYu upgrade.\n\nWe are proposing to use this code https://github.com/bandprotocol/bandchain/releases/tag/v1.2.6 to upgrade the BandChain. We are proposing to export the state at block height 4172935, which we expect to occur on Wednesday, October 14, 2020 at or around 2:00 pm UTC. We are proposing to launch GuanYu mainnet using genesis time 60 minutes after the timestamp of block height 4172935.\n\nFull proposal: https://ipfs.io/ipfs/QmWTkr9sJCs6BR5z9nevAemJxhnpSZnuxQJmkThPKpekLk\n\n"},"authority":"band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"}],"status":"PROPOSAL_STATUS_PASSED","final_tally_result":{"yes_count":"61509712685441","abstain_count":"515217133","no_count":"0","no_with_veto_count":"0"},"submit_time":"2020-09-29T07:10:35.976738552Z","deposit_end_time":"2020-10-13T07:10:35.976738552Z","total_deposit":[{"denom":"uband","amount":"1000000000"}],"voting_start_time":"2020-09-29T07:12:16.762050013Z","voting_end_time":"2020-10-13T07:12:16.762050013Z","metadata":"","title":"GuanYu Upgrade Proposal","summary":"This proposal is intended to signal acceptance/rejection of the precise software release that will contain the changes to be included in the GuanYu upgrade.\n\nWe are proposing to use this code https://github.com/bandprotocol/bandchain/releases/tag/v1.2.6 to upgrade the BandChain. We are proposing to export the state at block height 4172935, which we expect to occur on Wednesday, October 14, 2020 at or around 2:00 pm UTC. We are proposing to launch GuanYu mainnet using genesis time 60 minutes after the timestamp of block height 4172935.\n\nFull proposal: https://ipfs.io/ipfs/QmWTkr9sJCs6BR5z9nevAemJxhnpSZnuxQJmkThPKpekLk\n\n","proposer":"","expedited":false,"failed_reason":""}],"pagination":{"next_key":null,"total":"21"}}