Enable concurrent read/write operations in oZKS
eozturk1 opened this issue · comments
During a sequencing operation a node might get updated. This means if a client requests a proof during sequencing, we might return an inconsistent proof (a mix of states from the current and next epochs). A solution to this is to keep duplicate information about a node but this can be improved further.
I'll work on this @Jasleen1 after the micro benchmark tests.