Per-container event feed #414
Assignees
Labels
Milestone
Comments
roman-khimov
added
U2
This was referenced Jun 27, 2024
|
There is a question of updates. Updating 1000 contracts at once is very much different from updating 10 contracts. |
carpawell
added a commit
to nspcc-dev/neofs-node
that referenced
this issue
Sep 6, 2024
Initial replication requires nodes to sign object's main meta information and respond with it. Meta information is not sent on wire and treated as a fixed ordered NEO's map. Signatures are verified, not stored/send anywhere yet. It follows the recent API extension: nspcc-dev/neofs-api#299. Further, this extension is planned to have a contract adoption: nspcc-dev/neofs-contract#413 and nspcc-dev/neofs-contract#414. Closes #2876. Signed-off-by: Pavel Karpy <[email protected]>
carpawell
added a commit
to nspcc-dev/neofs-node
that referenced
this issue
Sep 10, 2024
Initial replication requires nodes to sign object's main meta information and respond with it. Meta information is not sent on wire and treated as a fixed ordered NEO's map. Signatures are verified, not stored/send anywhere yet. It follows the recent API extension: nspcc-dev/neofs-api#299. Further, this extension is planned to have a contract adoption: nspcc-dev/neofs-contract#413 and nspcc-dev/neofs-contract#414. Closes #2876. Signed-off-by: Pavel Karpy <[email protected]>
carpawell
added a commit
to nspcc-dev/neofs-node
that referenced
this issue
Sep 10, 2024
Initial replication requires nodes to sign object's main meta information and respond with it. Meta information is not sent on wire and treated as a fixed ordered NEO's map. Signatures are verified, not stored/send anywhere yet. It follows the recent API extension: nspcc-dev/neofs-api#299. Further, this extension is planned to have a contract adoption: nspcc-dev/neofs-contract#413 and nspcc-dev/neofs-contract#414. Closes #2876. Signed-off-by: Pavel Karpy <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 (nspcc-dev/neofs-api#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.
The text was updated successfully, but these errors were encountered: