kaber2

> We already process blocks fully and then emit logs, but since those get filtered and only the matches returned, it's not trivial to signal the end. It gets a...

I have a patch to send block logs. I'm currently on vacation traveling, but I'll send it over end of the month.

> * Use the new `parse_into_document()` and create a new document for every parse. This is potentially both slow and very wasteful with memory, but would let us keep a...

> Hello, we doubled the server resources and still we have problem in syncing and transactions broadcasting, some of TX is done and some not. Really there is BUG in...

More fine work brought to you by the good people of Binance Shit Chain. Despite the obvious mess ups like silently halting the chain etc, why the hell the "fix"...

Thank you for the hint, I will give this is try and report back.

PS: regarding Repro, unfortunately no and I can't share this specific contract. I'll see if your suggestions makes a difference and will then see if I can quickly whip up...

Ok I used the default options from OptimiserSettings.h and removed F, and indeed that massively reduced my contract size. I also tried adding an intermediate function to remove constant parameters...

[test.txt](https://github.com/ethereum/solidity/files/14438227/test.txt) I think I managed to create a reproducer. It has one big lnonsense function, and two external entry points, calling the function with constant arguments. It gets specialized for...

I'm not sure how practical that would be, but just an idea. I personally don't care too much about a bit of bloat in the contract and prefer lower execution...