BCIP-12: Increase the maximum data size for oracle module

1. Parameter change cosmos.params.v1beta1

   {
       "@type": "/cosmos.gov.v1.MsgExecLegacyContent",
       "content": {
           "@type": "/cosmos.params.v1beta1.ParameterChangeProposal",
           "title": "BCIP-12: Increase the maximum data size for oracle module",
           "changes": [
               {
                   "key": "MaxCalldataSize",
                   "value": "\"4096\"",
                   "subspace": "oracle"
               },
               {
                   "key": "MaxReportDataSize",
                   "value": "\"4096\"",
                   "subspace": "oracle"
               }
           ],
           "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."
       },
       "authority": "band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"
   }

Voting ended before BitBasic started recording Band votes on Oct 29, 2026, and the chain deletes votes when voting ends.