The Anoma Umbrella, its status and plans, were discussed and diagrammed.
-
anoma_node
This is the node application, containing processes which run and implement various engines and pieces of functionality; it owns theAnoma.Node
namespace. -
anoma_lib
This holds modules with functions, in no particular namespace though theAnoma
namespace is available for data structures and the like which are pieces of Anoma. -
event_broker
See the dedicated thread! Owns theEventBroker
namespace. -
anoma_proto
Data type definitions which are anoma_lib material, but they’re protobuf definitions generated with protoc, so it’s easiest to organize them here and have the protoc done as part of its build process. Owns, probably, theAnoma.Proto
namespace. -
anoma_client
Offline client code; also processes which run, but not part of the node. This has e.g. the prover. -
Others
In future, there will be others; see the diagram for examples like anoma_web or anoma_observer or nock_vm.