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

New issue

Open

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

sami commented

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

Owner

Originally created by @cthulhu-rider on GitHub (Feb 10, 2023).

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.

Originally created by @cthulhu-rider on GitHub (Feb 10, 2023). 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.

sami added the

documentation

discussion

labels

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

sami commented

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

Author

Owner

@roman-khimov commented on GitHub (Feb 10, 2023):

if contract does not verify such cases

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

@roman-khimov commented on GitHub (Feb 10, 2023): > if contract does not verify such cases This is the main problem in many of such cases. See #314 also.