# Reduce Maximum Block Size to 1mb

**URL:** <https://forum.osmosis.zone/t/reduce-maximum-block-size-to-1mb/417>\
**Category:** Proposal Discussion\
**Tags:** rejected\
**Created:** [September 30, 2023, 8:36am UTC](https://forum.osmosis.zone/t/reduce-maximum-block-size-to-1mb/417 "2023-09-30T08:36:25Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![faddat](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/faddat/32/2098_2.png) [@faddat](https://forum.osmosis.zone/u/faddat)\
**Post date:** [September 30, 2023, 8:36am UTC](https://forum.osmosis.zone/t/reduce-maximum-block-size-to-1mb/417/1 "2023-09-30T08:36:25Z")

</div>

## Change log

- 2023-09-30: initial post
- 2023-10-1: proposal live [Mintscan](https://www.mintscan.io/osmosis/proposals/645)

## Summary

> **[ASA-2023-002: Default for \`BlockParams.MaxBytes\` consensus parameter may...](https://github.com/cometbft/cometbft/security/advisories/GHSA-hq58-p9mv-338c)**
>
> \## Amulet Security Advisory for CometBFT: ASA-2023-002
> 
> \*\*Component\*\*: CometBFT
> \*\*Criticality:\*\* Low
> \*\*Affected versions:\*\* All
> \*\*Affected users:\*\* Validators, Chain Builders + Maintainers
> 
> ...

## Details

> **[ASA-2023-002: Default for \`BlockParams.MaxBytes\` consensus parameter may...](https://github.com/cometbft/cometbft/security/advisories/GHSA-hq58-p9mv-338c)**
>
> \## Amulet Security Advisory for CometBFT: ASA-2023-002
> 
> \*\*Component\*\*: CometBFT
> \*\*Criticality:\*\* Low
> \*\*Affected versions:\*\* All
> \*\*Affected users:\*\* Validators, Chain Builders + Maintainers
> 
> ...

## Parameter and new value

```json
{
    "title": "Reduce Maximum Block Size",
    "description": "This Proposal reduces the maximum block size pursuant to: https://github.com/cometbft/cometbft/security/advisories/GHSA-hq58-p9mv-338c",
    "changes": [
        {
            "subspace": "baseapp",
            "key": "BlockParams",
            "value": {
                "max_bytes": "1048576"
            }
        }
    ],
    "deposit": "100000000uosmo"
}

```

## Forum post link

> <https://x.com/gadikian/status/1707895413821370592?s=20>

## IPFS link

## Governance votes

The following items summarize the voting options and what it means for this proposal:

YES - reduce maximum block size on the cosmos hub  
NO - keep Gaia’s maximum block size the same  
NO WITH VETO - A ‘NoWithVeto’ vote indicates a proposal either (1) is deemed to be spam, i.e., irrelevant to Cosmos Hub, (2) disproportionately infringes on minority interests, or (3) violates or encourages violation of the rules of engagement as currently set out by Cosmos Hub governance. If the number of ‘NoWithVeto’ votes is greater than a third of total votes, the proposal is rejected and the deposits are burned.  
ABSTAIN - You wish to contribute to quorum but you formally decline to vote either for or against the proposal.

---

<div class="post-metadata">

**Author:** ![luisqa](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/luisqa/32/1759_2.png) [@luisqa](https://forum.osmosis.zone/u/luisqa)\
**Post date:** [September 30, 2023, 1:01pm UTC](https://forum.osmosis.zone/t/reduce-maximum-block-size-to-1mb/417/2 "2023-09-30T13:01:17Z")

</div>

I see no mention of 1MB being the recommended amount besides a comparison between 21mb and 1mb block size.

What size is appropriate? What is the current average block size in Osmosis?

---

<div class="post-metadata">

**Author:** ![faddat](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/faddat/32/2098_2.png) [@faddat](https://forum.osmosis.zone/u/faddat)\
**Post date:** [September 30, 2023, 2:32pm UTC](https://forum.osmosis.zone/t/reduce-maximum-block-size-to-1mb/417/3 "2023-09-30T14:32:16Z")

</div>

Overall Average Size of block range 11591000 - 11593151 is: 74.61 KB

Thanks to @nostradamus

1mb still allows for \>10x the average size.

So I’m good with 1mb.

---

<div class="post-metadata">

**Author:** ![faddat](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/faddat/32/2098_2.png) [@faddat](https://forum.osmosis.zone/u/faddat)\
**Post date:** [October 1, 2023, 9:51am UTC](https://forum.osmosis.zone/t/reduce-maximum-block-size-to-1mb/417/4 "2023-10-01T09:51:28Z")

</div>

> **[Mintscan](https://www.mintscan.io/osmosis/proposals/645)**
>
> Interchain explorer and analytics powered by Cosmostation.

---

<div class="post-metadata">

**Author:** ![LeonoorsCryptoman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/leonoorscryptoman/32/208_2.png) [@LeonoorsCryptoman](https://forum.osmosis.zone/u/LeonoorsCryptoman)\
**Post date:** [October 1, 2023, 6:37pm UTC](https://forum.osmosis.zone/t/reduce-maximum-block-size-to-1mb/417/5 "2023-10-01T18:37:59Z")

</div>

@faddat How do the concerns from Valardragon fit into this?

> <https://twitter.com/valardragon/status/1708487646111015282>

If I read it correctly the risk is deemed low. An expedited proposal is therefore unnecessary imo.  
It also says that chains are advised to start an analysis. Going on chain without ever mentioning it is a grave gap as well. So this proposal should not pass imo since it leaves out enormous parts of information required to make an educated vote.

---

<div class="post-metadata">

**Author:** ![faddat](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/faddat/32/2098_2.png) [@faddat](https://forum.osmosis.zone/u/faddat)\
**Post date:** [October 1, 2023, 10:07pm UTC](https://forum.osmosis.zone/t/reduce-maximum-block-size-to-1mb/417/6 "2023-10-01T22:07:48Z")

</div>

Hey @LeonoorsCryptoman – @valardragon and I talked a bit after his tweet. Basically, when planning this prop, I missed some factors that could be uniquie to osmosis and/or CosmWasm enabled chains, so we’re going to turn around on this one.

---

<div class="post-metadata">

**Author:** ![luisqa](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/luisqa/32/1759_2.png) [@luisqa](https://forum.osmosis.zone/u/luisqa)\
**Post date:** [October 2, 2023, 5:08am UTC](https://forum.osmosis.zone/t/reduce-maximum-block-size-to-1mb/417/7 "2023-10-02T05:08:43Z")

</div>

Might want to reach out to other validators, seems this is passing. Shame you only listened when Valardragon got involved.

---

<div class="post-metadata">

**Author:** ![LeonoorsCryptoman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/leonoorscryptoman/32/208_2.png) [@LeonoorsCryptoman](https://forum.osmosis.zone/u/LeonoorsCryptoman)\
**Post date:** [October 3, 2023, 6:28pm UTC](https://forum.osmosis.zone/t/reduce-maximum-block-size-to-1mb/417/8 "2023-10-03T18:28:41Z")

</div>

I mainly deem is a bummer that using the forum as intended could have caused this proposal to not hit on-chain governance…

Like using the forum is intended to do. We switched from Commonwealth to the forum, also to facilitate one of the main people (@faddat) who had issues to get on Commonwealth to be able to be here and discuss again…

---

<div class="post-metadata">

**Author:** ![whitemarlin](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/whitemarlin/32/776_2.png) [@whitemarlin](https://forum.osmosis.zone/u/whitemarlin)\
**Post date:** [October 4, 2023, 1:27am UTC](https://forum.osmosis.zone/t/reduce-maximum-block-size-to-1mb/417/9 "2023-10-04T01:27:39Z")

</div>

Will developers be able to upload smart contract updates with this? Why is 1MB appropriate?

---

<div class="post-metadata">

**Author:** ![LeonoorsCryptoman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/leonoorscryptoman/32/208_2.png) [@LeonoorsCryptoman](https://forum.osmosis.zone/u/LeonoorsCryptoman)\
**Post date:** [October 4, 2023, 6:10pm UTC](https://forum.osmosis.zone/t/reduce-maximum-block-size-to-1mb/417/10 "2023-10-04T18:10:51Z")

</div>

Nobody knows, no research has been done…

---

<div class="post-metadata">

**Author:** ![faddat](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/faddat/32/2098_2.png) [@faddat](https://forum.osmosis.zone/u/faddat)\
**Post date:** [October 20, 2023, 11:24am UTC](https://forum.osmosis.zone/t/reduce-maximum-block-size-to-1mb/417/11 "2023-10-20T11:24:55Z")

</div>

No there’s about 30 pages of research at this point

And about 10 when this post was made.

But I likely would have broken contract uploads.

Please don’t assume stuff.

Part of me feeling should just release report.

---

<div class="post-metadata">

**Author:** ![faddat](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/faddat/32/2098_2.png) [@faddat](https://forum.osmosis.zone/u/faddat)\
**Post date:** [December 28, 2023, 12:11pm UTC](https://forum.osmosis.zone/t/reduce-maximum-block-size-to-1mb/417/12 "2023-12-28T12:11:17Z")

</div>

In the end I did just release the report, here is a tweet containing every bit of detail that we put together on P2P storms:

> [@Proposal for Doubling the Max Gas Block Parameter from 120,000,000 to 240,000,000](https://forum.osmosis.zone/t/proposal-for-doubling-the-max-gas-block-parameter-from-120-000-000-to-240-000-000/1072/11):
>
> I support this proposal, along with another proposal that I’m about to write that reduces block size but not as much as the one I wrote earlier, here: @JohnnyWyles are you saying that currently we cannot adjust baseapp parameters? Because I would like to do well a proposal that does exactly that. @czarcas7ic I’m in support of increasing block gas because indeed, we can put more txns in em. At the same time I would like to reduce the maximum block size to 4mb, not the 1mb I proposed earlier. …

I can say conclusively that this is what was used recently to exploit @madcapslaugh’s Levana.

At Osmosis we love dragons.

Informal won’t protect them, we have to do it ourselves.

I just spoke with @JohnnyWyles, he mentioned that @ValarDragon is suggesting five megabytes as a decent block size and I agree – 5mb sounds great.
