kaber2
kaber2
I discovered the history.logs.disable option and enabled it, and speed is back up to around 5k blocks/sec.
One final note, in both cases I'm using cache.blocklogs=2560 to make sure the 2k block ranges fit into the log cache.
So can we expect an update in the release announcement for 1.3.0?
Thank you!
Thank you for the information. This leaves a few questions though. Is this new fork compatible with opera, and will it be running on the same chain or a new...
Thanks for your response, I will give that a try. > keyd monitor -t +3448 ms Apple Inc. Apple Internal Keyboard / Trackpad 05ac:027f ] down +0 ms Apple Inc....
``` [main] ] = timeout(noop, 100, ]) ``` Seems to mostly solve the issue. No idea why ] is displayed as a plus sign, but except for some occasional plus-signs...
I have a few weird new effects since running keyd, the "ä" key (german umlaut) now also inserts a carriage return, the other umlauts behave normally. The arrow down key...
Great, I'll (slowly) get working on that.
> @kaber2 [OffchainLabs/nitro#2231 (comment)](https://github.com/OffchainLabs/nitro/issues/2231#issuecomment-2058603798) Taking the conversation here. Backfilling blocks and blobs are separate concerns. Every full node should have all the historical blocks, but there is no guarantee that...