contracts/factory/src/lib.rs defines pub const MAX_BATCH_SIZE: u32 = 100;, used by both create_batch_streams and cancel_batch_streams to cap batch sizes. Every other protocol-wide numeric bound in the system — fee_bps, min_duration_seconds, max_duration_seconds, max_rate_per_second — lives in DripGovernor and is adjustable by a role-gated setter without a contract upgrade. MAX_BATCH_SIZE is the one remaining bound that can only be changed by uploading new factory WASM via upgrade_stream_wasm (which, per the earlier issue on that function, doesn't even upgrade the factory's own code) or a fresh deploy. Worth considering whether batch-size limits belong in DripGovernor::GovernorConfig alongside the other tunables.
contracts/factory/src/lib.rsdefinespub const MAX_BATCH_SIZE: u32 = 100;, used by bothcreate_batch_streamsandcancel_batch_streamsto cap batch sizes. Every other protocol-wide numeric bound in the system —fee_bps,min_duration_seconds,max_duration_seconds,max_rate_per_second— lives inDripGovernorand is adjustable by a role-gated setter without a contract upgrade.MAX_BATCH_SIZEis the one remaining bound that can only be changed by uploading new factory WASM viaupgrade_stream_wasm(which, per the earlier issue on that function, doesn't even upgrade the factory's own code) or a fresh deploy. Worth considering whether batch-size limits belong inDripGovernor::GovernorConfigalongside the other tunables.