Charge for metadata attribute #188

New issue

Open

opened 2025-12-28 18:08:49 +00:00 by sami · 2 comments

sami commented

2025-12-28 18:08:49 +00:00

Owner

Originally created by @roman-khimov on GitHub (Oct 18, 2024).

I'm always frustrated when additional workload is not payed for in NeoFS. https://github.com/nspcc-dev/neofs-api/pull/309 should be a paid for attribute, just like NNS names.

Describe the solution you'd like

Add a configuration option and charge for this attribute.

Originally created by @roman-khimov on GitHub (Oct 18, 2024). ## Is your feature request related to a problem? Please describe. I'm always frustrated when additional workload is not payed for in NeoFS. https://github.com/nspcc-dev/neofs-api/pull/309 should be a paid for attribute, just like NNS names. ## Describe the solution you'd like Add a configuration option and charge for this attribute.

sami added the

enhancement

labels

2025-12-28 18:08:49 +00:00

sami commented

2025-12-28 18:08:49 +00:00

Author

Owner

@roman-khimov commented on GitHub (Nov 14, 2024):

The problem is, we don't see attributes at the contract level (at least not until we refactor the container structure).

@roman-khimov commented on GitHub (Nov 14, 2024): The problem is, we don't see attributes at the contract level (at least not until we refactor the container structure).

sami commented

2025-12-28 18:08:49 +00:00

Author

Owner

@roman-khimov commented on GitHub (Nov 14, 2024):

We can have a different price for meta-enabled containers though. And it'd be even more fair since the overhead increases per-object.

@roman-khimov commented on GitHub (Nov 14, 2024): We can have a different price for meta-enabled containers though. And it'd be even more fair since the overhead increases per-object.