Bugfix: Atomically commit trace and worldstate storage in single transaction #126
Description
Shomei commits trace and worldstate in two separate consecutive transactions.
RocksDB will correctly recover from being killed, but only in the context of the current commit.
If shomei is killed between the commit for the first transaction and the second transaction, there is a chance that the second commit will be lost, leaving the application state in a half/commited state. The result is that shomei will start up normally and proceed, but the trace (from the second consecutive transaction) is missing.
acceptance criteria:
- wrap the trace and worldstate commits in a single atomic commit