Configuration

Structure Description:

Enum:

A directory of enumerations, allowing you to call specific values by their names.

InfoReg:

A registry for storing periodic values. For example, if you need to store two dimensions and their value on a certain date (e.g., exchange rates). You can store new values for the currency dimension with a specific date, and by providing a date snapshot, retrieve the value as it was on any of the stored dates. (Example needed here.)

Dictionary:

A standard value directory containing various fields for data storage, similar to tables in databases like MySQL or PostgreSQL.

Operation:

An object representing a document, which has a header and (optionally) tabular parts. For instance, when recording a money deposit to a bank account, you only need the document header with details like sender and date. However, if recording a product shipment, you’ll need a table listing the products. This allows for creating and storing diverse data structures for operational accounting.

Const:

A list of constants that can be used in queries to avoid repeatedly writing the same value.

Ledger:

A registry for tracking balances. For example, if you have an account and funds, this object allows you to record transactions that either increase or decrease the account balance.

Contract:

An object for storing Ethereum network contract data such as ABI, contract address, and additional fields. Otherwise, you can write and read data from it just like any other directory.

Ethereum:

An external connected data set containing transaction and log journals from the Ethereum blockchain. This object is read-only, but data can be stored in other objects within your structure.