Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Verification function for container-level thing #413

Open
roman-khimov opened this issue Jun 27, 2024 · 0 comments
Open

Verification function for container-level thing #413

roman-khimov opened this issue Jun 27, 2024 · 0 comments
Assignees
@carpawell
Labels
blocked Can't be done because of something feature Completely new functionality I2 Regular impact S2 Regular significance U2 Seriously planned

Comments

@roman-khimov
Copy link
Member

Is your feature request related to a problem? Please describe.

I'm always frustrated when we can't check something container-level.

Describe the solution you'd like

Smth. like VerifySignature(cid interop.Hash256, msg []byte, sigs []Signature, curveHash NamedCurveHash) bool, we need to:

This can be used both in contracts and verification scripts (with CID fixed). A set of signatures like this can prove object existence (refs. nspcc-dev/neofs-api#299).
@roman-khimov roman-khimov added U2 Seriously planned blocked Can't be done because of something S2 Regular significance I2 Regular impact feature Completely new functionality labels Jun 27, 2024
@roman-khimov roman-khimov mentioned this issue Jun 27, 2024
Open
@carpawell carpawell self-assigned this Aug 26, 2024
@carpawell carpawell mentioned this issue Sep 6, 2024
Merged
carpawell added a commit to nspcc-dev/neofs-node that referenced this issue Sep 6, 2024
@carpawell
node/object/put: exchange meta signatures during replication
c13f5f4 
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
@carpawell
node/object/put: exchange meta signatures during replication
e63289a 
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
@carpawell
node/object/put: exchange meta signatures during replication
b724d14 
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
Assignees

@carpawell carpawell

Labels
blocked Can't be done because of something feature Completely new functionality I2 Regular impact S2 Regular significance U2 Seriously planned
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@roman-khimov @carpawell