ChaosDAO, in efforts to bolster transparency within the community, has offered the below rationale for its decision to vote Aye on Referendum 173.
 
Referendum 173: remove_code_size has been voted Aye by ChaosDAO.

This was voted Aye by the DAO. A majority of the DAO voters abstained from voting but those who did voted aye. ChaosDAO’s unique position as a social governance DAO means that there is diversity amongst its constituents where some governance votes require them to cede voting to the other members where there is a situation that may cause conflict-of-interest, they feel unqualified to evaluate, or they don’t understand the technical details or implications.

Overall vote:
75% Abstain
25% Aye

(Sorry cannot edit above due to signer restrictions)

# Fix HostConfiguration (maxCodeSize to 3 MiB)

The current Kusama `HostConfiguration` does not fulfill all assumptions about its consistency. This proposal aims at correcting that by modifying the on-chain config.

## Problem

 The `HostConfiguration::consistency_check` function asserts that the on-chain [`max_code_size`](https://github.com/paritytech/polkadot/blob/v0.9.41/runtime/parachains/src/configuration.rs#L376) is never larger than `MAX_CODE_SIZE`. This is violated on Kusama since the concrete `max_code_size` on-chain is 10 MiB and `MAX_CODE_SIZE` is only [3 MiB](https://github.com/paritytech/polkadot/blob/v0.9.41/primitives/src/v2/mod.rs#L331).  
 You can verify this by querying [PolkadotJS](https://polkadot.js.org/apps/#/js):
 
```js
let config = await api.query.configuration.activeConfig();
console.log(config.maxCodeSize / (1024*1024), "MiB");
// Prints 10 MiB
```

It is neccecary to correct this since otherwise the `consistency_check` will stay a No-OP with the [assumption](https://github.com/paritytech/polkadot/blob/v0.9.41/runtime/parachains/src/configuration.rs#L1324): "You cannot break something that is already broken".


## Proposal

Set the on-chain `max_code_size` back to a sane value of 3 MiB. A larger value is not expected to work due to networking restrictions. Related discussions about this are in [polkadot/#7108](https://github.com/paritytech/polkadot/issues/7108) and [polkadot/#7105](https://github.com/paritytech/polkadot/issues/7105).

## Impact on Para*s

Parachain/Parathread teams should check that all queued runtime upgrade have a size of at most 3 MiB (the `Runtime Size` as reported by `srtool`). A sweep across [all parachains](https://github.com/paritytech/polkadot/issues/7108#issuecomment-1516220831) showed that the largest is currently 1.7 MiB, that is about 57% of the new limit. So no problem here.

## Impact on Developers

\-

(Sorry cannot edit above due to signer restrictions)

# Fix `HostConfiguration` (`maxCodeSize` to 3 MiB)

The current Kusama `HostConfiguration` does not fulfill all assumptions about its consistency. This proposal aims at correcting that by modifying the on-chain config.

## Problem

 The `HostConfiguration::consistency_check` function asserts that the on-chain [`max_code_size`](https://github.com/paritytech/polkadot/blob/v0.9.41/runtime/parachains/src/configuration.rs#L376) is never larger than `MAX_CODE_SIZE`. This is violated on Kusama since the concrete `max_code_size` on-chain is 10 MiB and `MAX_CODE_SIZE` is only [3 MiB](https://github.com/paritytech/polkadot/blob/v0.9.41/primitives/src/v2/mod.rs#L331).  
 You can verify this by querying [PolkadotJS](https://polkadot.js.org/apps/#/js):
 
```js
let config = await api.query.configuration.activeConfig();
console.log(config.maxCodeSize / (1024*1024), "MiB");
// Prints 10 MiB
```

It is neccecary to correct this since otherwise the `consistency_check` will stay a No-OP with the [assumption](https://github.com/paritytech/polkadot/blob/v0.9.41/runtime/parachains/src/configuration.rs#L1324): "You cannot break something that is already broken".


## Proposal

Set the on-chain `max_code_size` back to a sane value of 3 MiB. A larger value is not expected to work due to networking restrictions. Related discussions about this are in [polkadot/#7108](https://github.com/paritytech/polkadot/issues/7108) and [polkadot/#7105](https://github.com/paritytech/polkadot/issues/7105).

## Impact on Para*s

Parachain/Parathread teams should check that all queued runtime upgrade have a size of at most 3 MiB (the `Runtime Size` as reported by `srtool`). A sweep across [all parachains](https://github.com/paritytech/polkadot/issues/7108#issuecomment-1516220831) showed that the largest is currently 1.7 MiB, that is about 57% of the new limit. So no problem here.

## Impact on Developers

\-

This is a referendumV2 whose proposer address (Ea6jhP5gF4r7NqhkEoAXJDgSgYpNQNaTYU6gPsrEGfctaKR) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Set the max validation code size for incoming upgrades.

#173 Untitled