Guide

Get a node online,
publish a site.

This is the shortest useful path from a fresh checkout to a reachable .loom site served by your own node.

// Install

Choose the install path that fits your machine

Most people should use the packaged install path for their platform and only fall back to a source build if they want to hack on Lattice itself.

Arch Linux

Use the AUR package

The fastest way to get a working node on Arch is the maintained AUR package.

yay -S lattice-net-git
lattice up
Windows

Use the MSI

Install the Windows MSI from the latest GitHub release. It puts lattice on PATH, installs the daemon service, and adds setup shortcuts.

Download:
github.com/fordz0/lattice/releases/latest

Preferred asset:
lattice-windows-x86_64.msi
macOS

Use the release tarball

Grab the tarball that matches your Mac, extract it, and run lattice up. Apple Silicon and Intel builds are both published.

Apple Silicon:
lattice-macos-aarch64.tar.gz

Intel:
lattice-macos-x86_64.tar.gz
Source

Build it yourself

Use this path if you want to work on the code, test local changes, or run straight from a checkout.

git clone https://github.com/fordz0/lattice
cd lattice
cargo build --release -p lattice-daemon -p lattice
// Build

Compile the pieces

At minimum you need the daemon and the CLI. The browser extension is loaded separately and talks to the daemon over localhost.

git clone https://github.com/fordz0/lattice
cd lattice
cargo build --release -p lattice-daemon -p lattice
// Run

Start the daemon

The daemon owns your node key, joins the network, stores records locally, and answers the CLI and extension. Keep it running while you publish or browse.

lattice up
lattice doctor

On first start it will create local state and begin connecting to bootstrap peers. lattice doctor is the fastest way to confirm the daemon, RPC endpoint, and local setup all line up.

// Browser

Load the Firefox extension

The extension intercepts .loom requests and forwards them to the local daemon. No remote gateway is involved.

  1. Open the public AMO listing: addons.mozilla.org/en-US/firefox/addon/lattice/
  2. Install the extension in Firefox.
  3. Keep the daemon running with lattice up before testing any .loom site.
  4. Open a .loom address and confirm the extension badge turns green on the docs site.
// Publish

Claim and publish

Publishing a directory claims the name if needed, signs the manifest, and stores content-addressed blocks for the network to replicate.

lattice publish --dir ./my-site --name mysite

You can inspect the result with:

lattice name info mysite
lattice status

To refresh installed Lattice apps later, run:

lattice update --all
// Verify

Check the full path

  • Open mysite.loom in Firefox with the extension enabled.
  • Confirm the daemon logs a fetch or local serve event.
  • Run lattice doctor or lattice status to confirm the CLI can talk to your daemon.
  • If browsing fails, check daemon port bindings and extension setup before debugging the protocol itself.