Great video, thanks! Very informative.
Right around 1:35:20, there’s discussion of (AIUI) preserving edges between nodes which are being updated. This reminds me of the notion of branches in git, where we refer to a mutable pointer to the tip of a hash chain, rather than any specific hash (which for git would be a commit). Could the issue you encountered in Acorn be solved by mapping, metaphorically, edges between “branches” rather than “commits”? This might be implemented by storing a “branches table”, which maps branch names to the latest entry, and then defining the “edges table” over branches. Then when an entry gets updated, the “branches table” gets updated to point to the new latest entry. The “edges table” wouldn’t need to be updated, because it now refers to the stable branch pointer.
Hopefully I’ve understood the issue right - I am still new to Holochain.