Personal Logos Basecamp module catalog by @hackyguru — browse it at modules.hackyguru.com.
Basecamp → Package Manager → Add repository:
https://modules.hackyguru.com/logos-repo.json
Then install any module below with one click — Basecamp resolves versions and dependencies for you.
| Module | Packages | Description |
|---|---|---|
| Logos Wallet | logos_wallet (core), logos_wallet_ui |
Unified Bedrock (base chain) + LEZ (execution zone) wallet — node lifecycle, base transfers/inscriptions, and private LEZ payments. |
| Lotion | lotion (core), lotion_ui |
Local-first, Notion-style writing workspace — SQLite pages with AES-256-GCM envelope crypto, optionally published to logos-storage. |
lotion_ui additionally depends on storage_module, which this catalog
does not publish — add a repository that carries it (or install it
first) or Basecamp's dependency resolution will fail.
More coming as they're polished — source lives in hackyguru/logos-workshop.
Built on logos-co/logos-modules-release-base:
GitHub Actions build each module's .lgx from its Nix flake
(.#lgx-portable), sign it (Ed25519 — the public DID is in
logos-repo.json under trustedSigners), publish it
as a <module>-v<version> release, and roll everything into the
index release
that clients read.
The release pipeline builds one module per submodule root — it reads
<module_path>/metadata.json and can't target a subdirectory. A monorepo
holding several modules therefore publishes its own signed .lgx (with
the same key, so trustedSigners still matches), and this catalog folds
those release assets into the index by URL. The sources are listed in
external-modules.txt; the Augment index
workflow runs after every Rebuild index and adds them on top.
hackyguru/lotion works this way —
lotion-core and lotion-ui live side by side in one repo.
Development happens in the
logos-workshop monorepo;
each module is mirrored to its own repo (logos-wallet-core,
logos-wallet-ui) via scripts/sync-wallet-modules.sh over there, and
those mirrors are the submodules released here.
Releases are cut from the Actions tab (Release …) or with
scripts/catalog.sh. The site at
modules.hackyguru.com is regenerated by CI from the index after every
release.