This article was first published on null
This new post lays out the elements of New Golem’s reference architecture, and illustrates how they interact to form a working ecosystem. This is an important base knowledge to have, before delving into the details of low-level Golem APIs (Application Programming Interfaces - acronym for software intermediaries that allow two applications to talk to each other).
Daemon & CLI (Command Line Interface)
To participate in the Golem network, a machine must host a component called Daemon. The Daemon is a piece of software which runs in the background and implements all the fundamental mechanics of the Golem ecosystem. It is responsible for:
- Node identity, account and key management
- Communication with other nodes in the Golem network
- Implementation of the low-level APIs
- Management of payments and integration with payment platforms (yes, the new Golem architecture allows various payment platforms, like plain Ethereum, or Layer-2 solutions)
So the Daemon will be the first component which must be up on a Golem node. It implements both Requestor and Provider APIs and features.
The reference architecture includes a CLI to control the state of the Daemon and a number of its administrative functions. So, you’ve used a CLI to setup the Daemon instance, and now you are ready to run the Agent apps...
In order to advertise resources onto the Golem Market, the Offers need to be published and the incoming Demands processed, so that the Agreements with the Requestors can be negotiated. Then, the activity execution needs to be controlled, and finally, payment notes must be issued in order to receive payments for services. All these responsibilities are ...
To keep reading, please go to the original article at: