Install a Mobazha Node

Before you start

The current public release candidate requires Go 1.26.4, Git, and a supported macOS or Linux environment. Start on testnet and use a dedicated data directory. Confirm available disk space, local firewall policy, backup location, and who controls the administrator session.

Install steps

1. Clone the public Node repository and record the exact commit you intend to evaluate.
2. Build the Node module with the pure-Go crypto implementation shown below. The current main checkout's workspace declaration can lag the module's Go requirement, so the source-build command isolates the module with GOWORK=off.
3. Initialize a testnet data directory owned by the service account.
4. Start the Node on the default local-only listener and open the embedded UI.
5. Keep the terminal visible until initial startup and health checks succeed.

git clone https://github.com/mobazha/mobazha.git
cd mobazha
GOWORK=off go build -tags goolm -o mobazha .
./mobazha init --testnet
./mobazha start --testnet --open

Expected result and verification

• The first start initializes the default data directory when needed.
• The embedded Web UI and HTTP API listen on http://127.0.0.1:5102 by default.
• Versioned HTTP routes live under /v1/, WebSocket under /ws, and MCP Streamable HTTP under /v1/mcp.
• Local-only listening is the safe default; do not expose the API to the internet until authentication, TLS, firewall, and update plans are reviewed.

Run diagnostics in a second terminal:

./mobazha doctor --json
curl -fsS http://127.0.0.1:5102/v1/runtime-config | jq

Verify that diagnostics complete, the embedded UI opens, the runtime snapshot has a supported schema, and optional capabilities remain unavailable until configured and healthy.

Representative diagnostic output

doctor --json returns pass, warning, and failure counts plus named checks. Paths, capacities, versions, and optional dependency results vary by host. A healthy local Node should report zero failed checks; warnings must still be reviewed against the intended deployment.

{
  "pass": 7,
  "warn": 3,
  "fail": 0,
  "results": [
    {
      "name": "Data directory",
      "status": "PASS",
      "detail": "<data-dir> (database found: <database-path>)"
    },
    {
      "name": "Node API",
      "status": "PASS",
      "detail": "healthy"
    }
  ]
}

The list above is shortened to show the contract shape. Preserve the complete local result for operations, but redact paths and environment detail before sharing it publicly.

Optional background service

After validating an interactive start, install and inspect the supported background service.

./mobazha service install
./mobazha service status
./mobazha doctor --json

Pre-release packaging

Docker, standalone, and appliance packaging exists in the public repository, but it remains pre-release. Inspect the image tag, downloaded scripts, configuration, update behavior, and recovery path before using it outside a disposable environment.

If something fails

• If the build fails, confirm go version, the checked-out commit, platform toolchain, and available storage.
• If Go reports that go.work declares an older version than go.mod, first confirm you are on the intended public revision, then use the documented module-isolated GOWORK=off build. Do not lower the module requirement to make a release-candidate checkout compile.
• If startup fails, capture sanitized diagnostics and confirm data-directory ownership and port availability.
• If the UI does not open, test the local listener before changing DNS, TLS, or firewall configuration.
• If runtime capabilities are not ready, inspect configuration and dependencies rather than enabling frontend controls manually.
• Remove only a disposable test data directory you deliberately created; never delete the only copy of a store to retry installation.