Correct `EXPIRATION_EPOCH` expectations #147

New issue

Closed

opened 2025-12-28 18:15:09 +00:00 by sami · 1 comment

sami commented

2025-12-28 18:15:09 +00:00

Owner

Originally created by @carpawell on GitHub (Dec 21, 2022).

Originally assigned to: @abereziny on GitHub.

It was clarified that the expiration epoch is the last epoch for any entity to be valid. See https://github.com/nspcc-dev/neofs-sdk-go/issues/370 and https://github.com/nspcc-dev/neofs-api/issues/253.

Related to https://github.com/nspcc-dev/neofs-node/issues/2097 and https://github.com/nspcc-dev/neofs-node/issues/2099. neofs-cli
flags description clarification is in progress.

Originally created by @carpawell on GitHub (Dec 21, 2022). Originally assigned to: @abereziny on GitHub. It was clarified that the expiration epoch is the _last epoch_ for any entity to be valid. See https://github.com/nspcc-dev/neofs-sdk-go/issues/370 and https://github.com/nspcc-dev/neofs-api/issues/253. Related to https://github.com/nspcc-dev/neofs-node/issues/2097 and https://github.com/nspcc-dev/neofs-node/issues/2099. `neofs-cli` flags description clarification is in [progress](https://github.com/nspcc-dev/neofs-node/pull/2169).

sami

2025-12-28 18:15:09 +00:00

closed this issue
added the
U0
label

sami commented

2025-12-28 18:15:09 +00:00

Author

Owner

@carpawell commented on GitHub (Dec 21, 2022):

lifetime flags should mean the following: specified --lifetime 10, made 10 epoch ticks, got the last valid epoch for an entity.

expire-at flags should mean the following: specified --expire-at 10, wait until currEpoch == 10, got the last valid epoch for an entity.

@carpawell commented on GitHub (Dec 21, 2022): `lifetime` flags should mean the following: specified `--lifetime 10`, made 10 epoch ticks, got the last _valid_ epoch for an entity. `expire-at` flags should mean the following: specified `--expire-at 10`, wait until `currEpoch == 10`, got the last _valid_ epoch for an entity.