-
Notifications
You must be signed in to change notification settings - Fork 15
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
Expand NetworkInfo information with more data #172
Comments
Signed-off-by: Leonard Lyubich <[email protected]>
Define `netmap.NetworkConfig` message which represents structure of NeoFS network config stored in Netmap contract. Signed-off-by: Leonard Lyubich <[email protected]>
Signed-off-by: Leonard Lyubich <[email protected]>
I'd also document list of keys and format of corresponding values. |
Define `netmap.NetworkConfig` message which represents structure of NeoFS network config stored in Netmap contract. Signed-off-by: Leonard Lyubich <[email protected]>
Signed-off-by: Leonard Lyubich <[email protected]>
@alexvanin are u sure that keys are hex-encoded strings? Seems like Netmap contract stores UTF-8 strings. Or we want to encode them during communication? |
You are right, they are simple UTF-8 encoded strings and should stay this way. |
Signed-off-by: Leonard Lyubich <[email protected]>
Define `netmap.NetworkConfig` message which represents structure of NeoFS network config stored in Netmap contract. Signed-off-by: Leonard Lyubich <[email protected]>
Signed-off-by: Leonard Lyubich <[email protected]>
Define `netmap.NetworkConfig` message which represents structure of NeoFS network config stored in Netmap contract. Signed-off-by: Leonard Lyubich <[email protected]>
Signed-off-by: Leonard Lyubich <[email protected]>
After nspcc-dev/neo-go#2160 we can expand
NetworkInfo
message with details about side chain:Also we can include NeoFS global configuration records as a list of key/value (both repeated bytes).
Keys are hex encoded strings and values ara raw data from netmap contract.
The text was updated successfully, but these errors were encountered: