Add expiration epoch to object's meta information that goes through the chain #191

Open
opened 2025-12-28 18:08:49 +00:00 by sami · 1 comment
Owner

Originally created by @carpawell on GitHub (Feb 14, 2025).

I'm always frustrated when we need to have expiration epoch in our meta-services but we dont.

Describe the solution you'd like

Extend meta information to have expiration epoch too.

Describe alternatives you've considered

No.

Additional context

https://github.com/nspcc-dev/neofs-contract/pull/448
https://github.com/nspcc-dev/neofs-contract/pull/457

Originally created by @carpawell on GitHub (Feb 14, 2025). ## Is your feature request related to a problem? Please describe. I'm always frustrated when we need to have expiration epoch in our meta-services but we dont. ## Describe the solution you'd like Extend meta information to have expiration epoch too. ## Describe alternatives you've considered No. ## Additional context https://github.com/nspcc-dev/neofs-contract/pull/448 https://github.com/nspcc-dev/neofs-contract/pull/457
Author
Owner

@roman-khimov commented on GitHub (Nov 5, 2025):

On hold. Meta is being reworked into a separate chain.

@roman-khimov commented on GitHub (Nov 5, 2025): On hold. Meta is being reworked into a separate chain.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-contract#191
No description provided.