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.

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

Should IR requirements be reflected in the contract docs? #323

Open
cthulhu-rider opened this issue Feb 10, 2023 · 1 comment
Open

Should IR requirements be reflected in the contract docs? #323

cthulhu-rider opened this issue Feb 10, 2023 · 1 comment
Labels
discussion Open discussion of some problem documentation Improvements or additions to documentation I3 Minimal impact S3 Minimally significant U4 Nothing urgent

Comments

@cthulhu-rider
Copy link
Contributor

One of the Inner Ring activities in NeoFS architecture is listening to Sidechain contracts and validating incoming events. The Inner Ring imposes arequirements for some operations.

For example, to switch storage node to MAINTENANCE mode it should be allowed by the network configuration. Contract docs does not mention this restriction. Maybe it should?

Even if contract does not verify such cases, docs could prevent some pre-failed transactions.

@cthulhu-rider cthulhu-rider added documentation Improvements or additions to documentation question Further information is requested discussion Open discussion of some problem labels Feb 10, 2023
@roman-khimov
Copy link
Member

if contract does not verify such cases

This is the main problem in many of such cases. See #314 also.

@roman-khimov roman-khimov added U4 Nothing urgent S3 Minimally significant I3 Minimal impact and removed question Further information is requested labels Dec 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Open discussion of some problem documentation Improvements or additions to documentation I3 Minimal impact S3 Minimally significant U4 Nothing urgent
Projects
None yet
Development

No branches or pull requests

2 participants