Logos Control

Small Basecamp plugin for operating local Logos node modules. It keeps node controls separate from application UIs such as Logos Palace.

The plugin exposes only explicit user actions:

• report whether an LEZ wallet client is available;
• start or stop Delivery from user-provided JSON;
• start or stop Storage from user-provided JSON;
• refresh observed module state.

It does not handle wallet secrets, start a remote sequencer, invent network credentials, or configure an application room.

Use

Add the 3esmit release catalog to Basecamp's package manager, then install logos_control_ui with its catalog-resolved lez_core, delivery_module, and storage_module dependencies. The catalog is:

https://raw.githubusercontent.com/3esmit/logos-3esmit-release/main/logos-repo.json

Open Logos Control from Basecamp after installation. The catalog points to the source-owned releases from the 3esmit forks; this repository does not ship copies of those dependencies.

The controller accepts a JSON object only when a node is uninitialized. The node module keeps its initialized configuration; subsequent starts do not need the JSON entered again. The field clears after a successful request. Configuration is never embedded in this plugin.

Delivery uses the Delivery module's flat Waku configuration object. Storage expects the Storage module configuration object; choose an absolute data directory and log location appropriate for the local user.

Build

nix build .#lgx-portable

The resulting directory contains an installable .lgx package.

Validation

nix build
nix build .#lgx-portable

For a local Basecamp run, install the four compatible LGX packages into an isolated Basecamp user directory, then use the visible node controls. Do not place test configuration, wallet material, or generated screenshots in Git.

License

MIT.