Data

Index

1. Toc
2. User
   1. Data
3. Contributing
   1. Understanding Any Module
   2. Style Guide
   3. Writing Documents
   4. Examples Over Testing
   5. Git
   6. Hoon
   7. Iex
   8. Mnesia Vs Actor State
   9. Observer
   10. Testing
       1. Running Tests
       2. Writing Tests
4. Visualization
   1. Actors
5. Hoon
   1. Calling
   2. Dumping
   3. Setting Up
6. Analysis
   1. Fema Analysis Pinger
7. Logging
8. Vm_interface

Where Anoma saves State

Anoma follows XDG conventions for state stored on the operating system:

1. Database dumps and Database tables are stored in $XDG_DATA_HOME/anoma_env
2. Configuration files are stored in $XDG_CONFIG_HOME/anoma_env

Configuration Files

Currently Anoma stores a file config.toml with minimal settings for your Anoma node.

Configuration Format

TODO write about each field or link to a relavent section

Sending in a custom configuration file

TODO explain how to do this

Data Files

Anoma stores a few different files in the $XDG_DATA_HOME

1. Mnesia tables backed by RocksDB
2. Anoma dump files.

The dump file contains all information necessary to restore Anoma to the time when the dump command was used on Anoma.

Beware this will overwrite the local Mnesia tables.

The Mnesia tables are created every time one runs Anoma.

These Mnesia tables contain chain information that the Anoma execution environment can query.

To learn more about our data format, please checkout the developer’s section on Mnesia Vs Actor State.

Launching with a given dump file

TODO write how to send in the CLI arguments to restore a dump