Specification does not clarify that object expires after NEOFSEXPIRATION_EPOCH occurs #31

New issue

Open

opened 2025-12-28 18:14:26 +00:00 by sami · 0 comments

sami commented

2025-12-28 18:14:26 +00:00

Owner

Originally created by @vdomnich-yadro on GitHub (Aug 9, 2022).

There's a paragraph in specification that explains expiration behavior.

This paragraph does not elaborate that object becomes expired after epoch __NEOFS__EXPIRATION_EPOCH (which is the actual logic in accordance with the code). Ideally we would want this to be clearly stated in specification.

Originally created by @vdomnich-yadro on GitHub (Aug 9, 2022). There's a [paragraph](https://github.com/nspcc-dev/neofs-spec/blob/323a28f30b119e1c38ef738ca532c07dfea2623b/03-storage/10-expiration.md?plain=1#L3) in specification that explains expiration behavior. This paragraph does not elaborate that object becomes expired after epoch `__NEOFS__EXPIRATION_EPOCH` (which is the actual logic in accordance with [the code](https://github.com/nspcc-dev/neofs-api/blob/master/object/types.proto#L123)). Ideally we would want this to be clearly stated in specification.