Chained metadata, v1 #1231

Closed
opened 2025-12-28 17:22:16 +00:00 by sami · 0 comments
Owner
Originally created by @roman-khimov on GitHub (Jun 27, 2024). Originally assigned to: @carpawell on GitHub. ## Is your epic related to a problem? Please describe. I'm always frustrated when we don't have any real solution for the metadata problem. It's naturally sharded per-container, but solving sharding problems will take a lot of time, so for v1 we can just have it centralized (which naturally limits per-network ops/s). It's processed off-chain, but ordered on-chain. ## Describe the solution you'd like * https://github.com/nspcc-dev/neofs-node/pull/2802 * https://github.com/nspcc-dev/neofs-api/issues/299 * https://github.com/nspcc-dev/neofs-sdk-go/issues/589 * https://github.com/nspcc-dev/neofs-node/issues/2876 * https://github.com/nspcc-dev/neofs-contract/issues/412 * https://github.com/nspcc-dev/neofs-contract/issues/413 * https://github.com/nspcc-dev/neofs-api/issues/300 * https://github.com/nspcc-dev/neofs-contract/issues/414 * https://github.com/nspcc-dev/neofs-node/issues/2877 * https://github.com/nspcc-dev/neo-go/issues/3493 * https://github.com/nspcc-dev/neo-go/issues/3494 * https://github.com/nspcc-dev/neo-go/issues/3496 To be continued. * #2935 * #3070 * https://github.com/nspcc-dev/neofs-node/issues/3138 * https://github.com/nspcc-dev/neofs-node/issues/3139 * https://github.com/nspcc-dev/neofs-node/issues/3140 * https://github.com/nspcc-dev/neofs-node/issues/3141 * https://github.com/nspcc-dev/neofs-node/issues/3142 * #3178 * #3189
sami 2025-12-28 17:22:16 +00:00
  • closed this issue
  • added the
    epic
    label
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-node#1231
No description provided.