NESTS - Named Entities in Simple Tiered Spaces

NB: This is a temporary working document under continual revision as coding progresses. The documents and the initial implementation are co-evolving continually, so expect to find some duplications and occasional inconsistencies (all of which will be removed over time). (See page footer for most recent revision.)

2024-09-12: Because of the urgent need for a functional equivalent of NESTS to support open money requirements only (not the much richer requirements of a full open measure implementation), work has been suspended temporarily to focus on the much simpler SLATE software. In turn, the development of SLATE has led to a number of revisions in the NESTS design.

This page has been added while the markdown file at https://openmoney.github.io/specification/README.md is temporarily hidden. This is because the status of the repository has been changed to private pending completion of the first version of SLATE and its uploading. This has been adapted (and slightly updated) from the README.md file.

SLATE (Simple Ledger Application: a Temporary Expedient)

This is an extremely simple Flask application to support nested open money payment networks, each able to support multiple currencies.

This is a temporary system to allow networks/islands to form while NESTS is still being developed (its specification being still somewhat fluid at this stage). For this reason, the names used to identify entities (agents and currencies) in SLATE are compatible 1 with those of the fully-nested (and much more capable) NESTS software.


Entity categories

There are five categories of entity:

Agent categories

There are four categories of agent:


Internal representation

For convenience, each entity (namespace, primid, secid, currency or account) is identified internally by a unique number (its FPH) serving (among other things) as the primary key in an SQLite table. (NB, these numbers are fully compatible with the FPH () used in NESTS.

These global mappings are:

As in NESTS, each entity (namespace, currency, primid, secid or account) is identified by a human-readable name string (HRNS) placing it within a namespace.

Each namespace contains the names of namespaces, currencies, primds and secids and, as in NESTS, the names of accounts may be contained within any namespace (subject to authorization by its stewards. This provides a sufficient entry point into a network fully compatible with open money] (although notably lacking provision for the construction of the rich governance system that NESTS is intended to support).

The compatibility of the entity names (HRNS) and their equivalent FPH, will be sufficient to enable convenient and complete migration from SLATE to NESTS in due course.


Ledger files

Currency journal

Each currency has an associated journal in which all payments are recorded, listing

The currency's journal can be exported at any time (either as a CSV files or as a pretty-printed table) by one of its stewards or by a global system administrator.

Agents' ledgers

Each account has an associated journal in which all payments and receipts are recorded.

Each primd or secid (agent) has access to at least one account (generally more), and a separate ledger for each of these. The accounts' ledgers list all transaction (payments and receipts). These ledgers each comprise fields listing

For each payment made

Each primd or secid (agent) can export its own accounts' ledgers, each account being in a distinct currency.

The agent interface

The SLATE screens form a subset those used in NESTS, with minimal, if any, modification.

Primid screens