nspcc-dev / nspcc-dev/neofs-api
MD5 hash
Open
Nobody has claimed this yet.
blocked
enhancement
I3
S2
U2
- Dominant language
- Makefile
- Stars
- 11
- Forks
- 15
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 9
Description
Is your feature request related to a problem? Please describe.
I'm always frustrated when I look at https://github.com/nspcc-dev/neofs-s3-gw/issues/1053.
Describe the solution you'd like
I see no other way to solve it but to add yet another hash field to NeoFS objects (https://github.com/nspcc-dev/neofs-s3-gw/issues/1053#issuecomment-2907792818). Yeah, that's MD5. In 2025.
Describe alternatives you've considered
Unknown.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked neofs-s3-gw issue #1053 and its referenced comment to understand the requested MD5 behavior and why a new NeoFS object hash field is needed. Done means agreeing on the API change and documenting the resulting field and compatibility requirements; no repository file or test is identified in this issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design, cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100