You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But I think this would be a good improvement. Is there any use case for having plugins using a different network to the node itself? Can they not just use the same one as set in the node config?
IIRC in C# implementation that's what NeoFS plugin will do to be able to communicate with the NeoFS sidechain (#630).
Good example. I still think it would still be an improvement to remove the field and use the config file network number in other plugins. Modules that need to connect to other networks, like the NeoFS plugin, can still include overrides (or additional values) in their own configs.
When installing a plugin, to manually modify the network number in the config file, I do not know the meaning of the existence of the network number.
The
plugins
command lists plugins that may not work because of different network numbers, should they be improved.The text was updated successfully, but these errors were encountered: