Dmitry Murzin

> Gist is the following: > > 1. Leader pop transactions from the queue and they are removed temporarily (either entirely or just hashes) > 2. If block was committed...

The reason of tps degradation over time in case of single peer is that `Sumeragi::try_create_block()` method becomes slower as block height increases. Here is analysis of that method (~90 minutes...

Update on single peer tps profiling. WASM code for transaction validation takes >60% of all sumeragi thread:  Hot places inside WASM code: * 41% `SignedTransaction::decode` * 14% `AccountId::decode` *...

> is this the case even after #4995? Yes, this is 02479ce598854c35c106831e30f7223964703db3 > Is it the act of decoding that is slow or the act of copying bytes into linear...

> So if we still have to use genesis account afaik what benefits do we gain by now also checking hash of genesis block? As I see `kagami genesis sign`...

Discussed with @mversic and decided that currently it is not worth to implement #4555. Originally it was expected that it will simplify things, but looks like there is no good...

> @dima74 will #5117 take care of this? If all peer public keys are also changed, then no. Since we establish connection only with peers which public keys our peer...

From the issue description: > After some height peer set A is replaced with peer set B (A intersection B = empty set) I mean if there is no such...

How things currently work: * Topology of the peers (public keys and addresses) are stored on-chain. * There are (Un)RegisterPeer instructions for changing topology. * Initial topology is provided in...

> > Note that peer internal port is already in config - torii.address > > Do we still need this in the config? Yes, internal port is needed to listen...