yeah, I also thought this is weird, but this will be updated in adr-001 imp. It allows having one child nodekey, even zero nodekey.
IMO, we will keep them at this moment.

yeah, I also thought this is weird, but this will be updated in adr-001 imp. It allows having one child nodekey, even zero nodekey. IMO, we will keep them at this moment.

"It allows having one child nodekey", can you elaborate on that? do you mean one child branch node?

no, what I mean is it is possible to have one or zero node-key, since we are using the version + path as the node key, we can remove the child node keys for the same versions from the node structure, right?
because we can determine the child path like this left child path = node path + '0', right child path = node path + '1'

I know this is a bit far from this topic, but it will be updated in new imp, so I'd like to keep it at this time. tbh I am facing conflicts in my open PRs so frequently.

no, what I mean is it is possible to have one or zero node-key, since we are using the version + path as the node key, we can remove the child node keys for the same versions from the node structure, right? because we can determine the child path like this left child path = node path + '0', right child path = node path + '1'

I know this is a bit far from this topic, but it will be updated in new imp, so I'd like to keep it at this time. tbh I am facing conflicts in my open PRs so frequently.

BTW, we have some new ideas regarding iavl storage recently.

we can close this one, @yihuang @tac0turtle ?