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
The migration to the new node key format is tricky. To avoid stopping the network, it introduces a lazy set. We will accept the existence of both new and old format nodes in the tree.
Proposal
Refactor the Node structure to accept both old and new nodes, like this
// Node represents a node in a Tree.typeNodestruct {
key []bytevalue []bytehash []bytenodeKey*NodeKeyleftNodeKey []byte// it can be a node hash for the old node and be a node key serialization for the new node.rightNodeKey []bytesizeint64leftNode*NoderightNode*NodesubtreeHeightint8
}
Setting new nodes will store the node as a new node key format. It will refactor them to the new format for old nodes that face while updating the tree.
The text was updated successfully, but these errors were encountered:
Context
The migration to the new node key format is tricky. To avoid stopping the network, it introduces a
lazy set
. We will accept the existence of both new and old format nodes in the tree.Proposal
Node
structure to accept both old and new nodes, like thisThe text was updated successfully, but these errors were encountered: