## Mempool Fee Market Integrator Guide The Osmosis team recently introduced an EIP-1559 style fee market in order to mitigate blocks from being filled with invalid txs. This mechanism calculates a transaction fee each block (named `base_fee`), which is dynamic based on volume of transactions. If the blocks are consistently full, the transaction fee grows at a pre-defined rate, making invalid transaction spam less desirable from the viewpoint of the sending party. This increases until a maximum base fee is reached. Inversely, if the blocks are empty, the base fee decreases to a minium value. There are parameters for the min, max base fee, and the max rate of change. Integrators should update their fee estimation algorithm to account for this change. ### Client Side Integration As a client, to determine the transaction fee to set, query the endpoint below. ```bash curl https://lcd.osmosis.zone/osmosis/txfees/v1beta1/cur_eip_base_fee ``` Multiply the returned value by 3 for the final result to use in your application. Note, that this integration would make clients overpay txfees frequently. With the base fee multiplication by 3, we expect to have sufficient buffer to account for the times of instability. However, this is a temporary solution until a more stable implementation of the fee market is integrated into consensus. ### References Please see [this file](https://github.com/osmosis-labs/osmosis/blob/3d199dbf7eb6df019944fed3384c3a5679eae11f/x/txfees/keeper/mempool-1559/code.go#L13-L40) for more details about the current implementation.
Last changed by  
 
Roman Akhtariev
213

Read more

SQS: Separate Write and Read

Initial Architecture In the initial SQS architecture, we combined the SQS web server (the read side) together with the node logic (the write side) in-process. While this proved to be an attractive architecture for the initial iteration speed, it has also caused impediments stemming from chain repository merge, branch and release processes. Currently, each SQS change is low-risk. However, it has to go through the same expensive processes as the chain repository. Current Release Process During a chain release process, an SQS change has to be backported to multiple release branches. The process entails:

12/15/2023
Docker Build Logs

Docker Build Logs

12/11/2023
Sidecar Query Server (SQS): Integrator Guide

An off-chain server that is used for performing expensive query tasks.

12/6/2023
Server Notes

https://eminetto.medium.com/clean-architecture-using-golang-b63587aa5e3f

10/23/2023
Read more from Roman Akhtariev
Published on HackMD