Vlad Frolov

> hmm, aren't our typings generated from TypeScript source code in nearlib? I guess the point was that our nearlib types are not accurate enough in the first place.

@dunmatt interestingly enough, two out of two issues about this crate suggest fixing this :) (ref #3) I am happy to receive PRs! You are very welcome!

I assigned L1 implying that initial items should not be huge and Clippy + Rust compiler should guide us through, but if a bigger refactoring is necessary, we should decouple...

> So I suggest we do the following renaming The suggested renaming sounds reasonable to me. I will apply the suggestion (update my post) tomorrow.

The first steps in this direction are #2511 and #2520. @SkidanovAlex @nearmax @ilblackdragon Do you have any objections against project refactoring? The code is not going to change, it should...

@fckt Given the project is nearcore, it implies that everything in the repository is related to near. Thus, "near" as a folder name does not introduce any clarity (the same...

Let me list all the crates we have: ``` genesis-csv-to-json genesis-populate keypair-generator loadtester neard near-actix-utils near-chain near-chain-configs near-chunks near-client near-crypto near-epoch-manager near-jsonrpc near-jsonrpc-client near-logger-utils near-metrics near-network near-pool near-primitives near-rpc-error-core near-rpc-error-macro...

I propose keeping neard in the root folder since it is the main entry point to the project. "utils" was just recently introduced (#2511) and it has the only crate...

Yeah, we slowly move in this direction: * #4292 * #4621 * #4651

I would say that monitoring and anomaly detection are crucial for any product. I have limited experience in this area, and it seems to be quite a bit of work...