Per-container event feed #177

New issue

Closed

opened 2025-12-28 18:08:46 +00:00 by sami · 1 comment

sami commented

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

Owner

Originally created by @roman-khimov on GitHub (Jun 27, 2024).

Originally assigned to: @carpawell on GitHub.

I'm always frustrated when I don't know what's up with the container contents. And we want to filter events per-container.

Describe the solution you'd like

The solution is to deploy a contract for containers that use meta (https://github.com/nspcc-dev/neofs-api/issues/300, container contract would need to know it's enabled). This contract needs to accept event data from SNs and push them into notifications. It does not need to process/store these events. This gives a natural event feed for container.

Originally created by @roman-khimov on GitHub (Jun 27, 2024). Originally assigned to: @carpawell on GitHub. ## Is your feature request related to a problem? Please describe. I'm always frustrated when I don't know what's up with the container contents. And we want to filter events per-container. ## Describe the solution you'd like The solution is to deploy a contract for containers that use meta (https://github.com/nspcc-dev/neofs-api/issues/300, container contract would need to know it's enabled). This contract needs to accept event data from SNs and push them into notifications. It does not need to process/store these events. This gives a natural event feed for container.

sami

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

closed this issue
added the
S2

feature

U2

I1
labels

sami commented

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

Author

Owner

@roman-khimov commented on GitHub (Sep 3, 2024):

There is a question of updates. Updating 1000 contracts at once is very much different from updating 10 contracts.

@roman-khimov commented on GitHub (Sep 3, 2024): There is a question of updates. Updating 1000 contracts at once is very much different from updating 10 contracts.