# Our understanding of the Cosmos Hub mempool issues

**URL:** <https://forum.cosmos.network/t/our-understanding-of-the-cosmos-hub-mempool-issues/12040>\
**Category:** Conversation\
**Created:** [November 7, 2023, 10:59pm UTC](https://forum.cosmos.network/t/our-understanding-of-the-cosmos-hub-mempool-issues/12040 "2023-11-07T22:59:59Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ebuchman](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.cosmos.network/ebuchman/32/6645_2.png) [@ebuchman](https://forum.cosmos.network/u/ebuchman)\
**Post date:** [November 7, 2023, 11:23pm UTC](https://forum.cosmos.network/t/our-understanding-of-the-cosmos-hub-mempool-issues/12040/2 "2023-11-07T23:23:03Z")

</div>

To underscore, there are architectural and design problems in the Cosmos fee system and mempool. These are well known and being worked on through a variety of efforts. Validators are expected to respond to S.P.A.M by adjusting their fee and mempool settings. The Comet team has been working all year on ways to reduce bandwidth usage and have some patches that should help (as I summarized [here](https://forum.cosmos.network/t/proposal-cosmos-hub-adopt-the-skip-block-sdk/11641/35)). Ultimately Cosmos needs a more sustainable fee system and mechanisms for building blocks and gossiping txs in app-specific ways.

---

_[View the full topic](https://forum.cosmos.network/t/our-understanding-of-the-cosmos-hub-mempool-issues/12040)._