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
I think we can remove the logic of checking and just set the record. The checking was done to avoid spending more GAS than needed, but in on-prem installations this is not a problem. Also, the code should become much simpler.
In case we already have the record and it is invalid, we should
overwrite it instead of having several conflicting records.
Signed-off-by: Evgenii Stratonikov <evgeniy@morphbits.ru>
aprasolova
pushed a commit
to aprasolova/neofs-node
that referenced
this issue
Oct 19, 2022
NNS proposal describes string N3 address format, however we must also
have hex-string for backwards compatibility.
Signed-off-by: Evgenii Stratonikov <evgeniy@morphbits.ru>
If contract hashes are not equal to the expected ones we just call
AddRecord
that seems like not expected action in our deploys but anyway.neofs-node/cmd/neofs-adm/internal/modules/morph/initialize_nns.go
Lines 168 to 179 in 17059b3
The text was updated successfully, but these errors were encountered: