LeL
_Originally posted in https://github.com/nspcc-dev/neofs-node/pull/2674#discussion_r1542662972_ crypto helpers can be added to the SDK and pulled into the node code. Such refactoring is expected to simplify server implementation
Object placement is build using `netmap.Source` and `container.Source` in most scenarios. Also there are some similar cases when we use same placement approach, e.g. shard evacuation introduced [here](https://github.com/nspcc-dev/neofs-node/pull/1800/) and remote...
see https://github.com/nspcc-dev/neofs-node/pull/2733#discussion_r1504938815
* https://github.com/grpc/grpc-go/blob/master/Documentation/compression.md we've never used it. In theory, should reduce amount of node-to-node transmission data and boost system performance overall requires in-depth research and analysis, in the current situation it...
## Is your feature request related to a problem? Please describe. NeoFS API server sometimes wastes large amounts of memory. For example, to verify request signatures, the server decodes messages...
being executed over multi-node container, object `SEARCH` op can have partial success by design. Current server behavior could be buggy ## Steps to reproduce having NeoFS with at least 2...
## Is your feature request related to a problem? Please describe. `ObjectService.Put` devours a lot of memory for data buffers, sometimes excessively. Current scheme: client ---> `server OS` |---> `gRPC`...
## Is your feature request related to a problem? Please describe. object [`SEARCH`](https://github.com/nspcc-dev/neofs-api/blob/d95228c40283cf6e188073a87a802af7e5dc0a7d/object/service.proto#L156) operations are executed additively on all container nodes. Currently, server writes one response message to the stream...
currently IR [validates](https://github.com/nspcc-dev/neofs-node/blob/c93822827c37c4cace4c86d8861595eff5243102/pkg/innerring/config.go#L28) blockchain config by itself as @AnnaShaleva mentioned in [comment](https://github.com/nspcc-dev/neofs-node/pull/2652#discussion_r1413419752), Neo Go lib provides https://pkg.go.dev/github.com/nspcc-dev/[email protected]/pkg/config#ProtocolConfiguration.Validate that performs similar checks we cannot reuse this checker easily cuz its errors...
## Is your feature request related to a problem? Please describe. I'm always frustrated when user sees contract/transaction hash in the log and can only ask "what the endianness?". And...