hi @nazar-pc , is it fine if I work on this?

Sure, please

hi @nazar-pc , I am done with most of the changes, I have a question:

block_authoring_delay is u64,
https://github.com/subspace/subspace/blob/main/crates/sc-consensus-subspace-rpc/src/lib.rs#L278-L291

and schnellru support u32 for LimitedLength capacity.
https://github.com/koute/schnellru/blob/5a8927e9ed4b11fdfb0f2115aa4d2577e30d6f05/src/limiters.rs#L7

Should I cap the capacity of solution_response_senders cache to u32 max ? or do you recommed something else?

Should I cap the capacity of solution_response_senders cache to u32 max ? or do you recommed something else?

If you look carefully, you'll see that the only reason block_authoring_delay is converted into u64 is because it is originally Slot type that can be converted into u64 easily. Moreover, it is a very small number in practice (4) so you will never ever need to worry about its size, simply do this:

        let solution_response_senders_capacity =
            u32::try_from(block_authoring_delay).expect("Always a tiny constant in the protocol; qed");