Can have a 3rd merkle map with the leaves just being the root of the other two?
#Merging in parallel transactions that update the same merkle map
topaz lynx
trail beacon
Can have a 3rd merkle map with the leaves just being the root of the other two?
Maybe not, since this would allow for having 2 different values for the same key in each merkle map. I need the merging operation to fail in these cases. Plus this would create a large and complex data structure pretty quickly, negating the benefits of recursion, and using a more traditional blockchain architecture where we need to store every transaction, but maybe I'm missing something about your approach
topaz lynx
I mean
Root 1 hash from A merkle
Root 2 hash from B merkle
Always call a function like updateFinalRoot() whenever you change the leaf in either of those so you are sure the final root 3(hash of root1+root2) is updated too
Just thinking from the top of my head
Might not be doable
trail beacon
ORIGINAL MESSAGE: sorry, I accidentally deleted the original message. I'm basically trying to find a way to make a rollup where each transaction updates the same merkle map, with these transactions being able to be processed in parallel (instead of sequentially), and was wondering about how this could be implemented