The README currently documents a public, unauthenticated plain-gRPC endpoint and explicitly says it has no TLS. That is fine for a demo, but it is not suitable for regulated or sovereign deployments.
Please define a production profile with:
- TLS 1.3 and endpoint/certificate configuration;
- mutual authentication or an equivalent client identity model;
- authorization for Put, Get, metadata/proof reads, and Delete;
- replay/rate/abuse protections and quotas;
- safe key storage/rotation/recovery guidance; and
- a documented metadata-leakage model (object IDs, filenames, transaction records, size, timing).
In particular, content hashes should not be treated as the only access control mechanism, and application filenames must be considered sensitive metadata.
The README currently documents a public, unauthenticated plain-gRPC endpoint and explicitly says it has no TLS. That is fine for a demo, but it is not suitable for regulated or sovereign deployments.
Please define a production profile with:
In particular, content hashes should not be treated as the only access control mechanism, and application filenames must be considered sensitive metadata.