congrats on the @tempo testnet launch. i want to point out one issue in the readme. it says that tempo is “the most performant evm execution client.” this is not correct when we compare it with real benchmark data. i don't get why @paradigm insist with this meme that reth is fast when it isn't. nethermind and go ethereum are both faster in normal tests that can be run independently by anyone. nethermind is usually about 50 percent faster. this is important because both clients use programming languages with garbage collectors, which should make them slower than rust. but today, they still run faster since they have superior architectures and better written codebases. @ethrex_client, our own execution client, is also a bit faster than reth, but the difference is not very big. in any case, the numbers do not support the claim that tempo is the fastest client. after the fusaka update, reth has also been using very high amounts of memory. on our servers, it stays around 80 gb of ram. in the last few months it also had several OOM crashes because of problems with concurrency and how tokio is used. my criticism has nothing to do with the @ethereum versus tempo debate. it's related with keeping objective engineering measurements in a technical subject. it's not ok to keep repeating things that are not true. one last note, commoware’s codebase is very well written and performs strongly. congrats for choosing it.