Hi @warz,
Thank you for the post.
Looks like this may be the same or related to the problem in this thread.
It looks like step 1 may be redundant, because Peruse-v0.7.0-win-x64-dev\Peruse.exe
CRUD’s against a MockVault
file that is created in your temp_dir.
But that’s great that you’re experimenting with running your own local network.
Devs seems to be observing a corrupted MockVault
more often now, so we’re pushing up the task in priority to understand why.
Have you tried connecting a non-dev SAFE Browser release to your local test network?