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 don't see how a node can synchronize state root signatures over P2P in the current state validation implementation. Node can calculate local state root, node can catch broadcasted stateroot messages and add signatures this way, but if it misses them (or it's synchronizing from the genesis) there is nothing like getroots/roots pair of Neo 2 protocol to get validated state roots. So node can't ensure that its state is correct and can't provide state root signatures for its RPC clients, signatures are kinda "locked" into nodes that received them during initial stateroot broadcast. Is this intentional? How can we synchronize state roots?
The text was updated successfully, but these errors were encountered:
I don't see how a node can synchronize state root signatures over P2P in the current state validation implementation. Node can calculate local state root, node can catch broadcasted stateroot messages and add signatures this way, but if it misses them (or it's synchronizing from the genesis) there is nothing like
getroots
/roots
pair of Neo 2 protocol to get validated state roots. So node can't ensure that its state is correct and can't provide state root signatures for its RPC clients, signatures are kinda "locked" into nodes that received them during initial stateroot broadcast. Is this intentional? How can we synchronize state roots?The text was updated successfully, but these errors were encountered: