orama network

orama maint network

orama maint network announce [flags]

Write networks/<name>/ (release-root.json and, last, manifest.json) for a
network whose chain has not been created: its name, the chain id it will have, the
channel, the release repository and the release root its releases are verified
against, whether it has a faucet, and its seeds. The manifest pins no genesis, so
the network is listed but cannot be joined: 'orama setup --network <name>' says it
has not been created yet.

The person who creates the network then runs 'orama setup --create-network <name>'
with no --release-root: the chain id, the release repository, the channel and the
release root come from the announcement (a flag overrides). When the chain exists
the creation publishes the full manifest, with the genesis, over the announcement.

An announcement can be written again until the network is created. A network that
is already created is refused: a reset needs a new chain id from the creation.

Afterwards run 'make -C core sync-networks' so the binary embeds the manifest, and
commit networks/ and core/pkg/netregistry/embedded/ together.

orama maint network publish [flags]

Write networks/<name>/ (genesis.json, release-root.json, tor-network.json when the
network has one and, last, manifest.json) from the genesis a deploy built, for
the chain id it was built under. The manifest carries the SHA-256 of the genesis,
of the release root and of the Tor network file, so what a joining operator
fetches can be checked. --tor-network pins the network's Tor network file
(tor-network.json, the private Orama Tor network its relays join), which
'orama setup' then gives to every relay it installs; the Tor network is a
different thing from the chain, so a reset of the chain keeps the file.

An unset field keeps its value from the manifest already published; the first
publish of a network sets --seeds, --channel, --min-version, --release-repo and
--release-root. A chain id that is already published keeps its genesis: a reset
of the network needs a new chain id (orama-stagenet-5 becomes orama-stagenet-6),
and publishing the old id with another genesis is refused.

Afterwards run 'make -C core sync-networks' so the binary embeds the new manifest,
and commit networks/ and core/pkg/netregistry/embedded/ together.

orama network

List, choose, add and remove the networks the CLI knows.

A network is a name for something you can reach: a cluster, through its
gateway, and, for a network of the registry such as stagenet, the chain it runs,
the seeds to join through and the release root its software is verified against.
Every other command talks to the active network, or to the one --env names.

  orama network list                          every network and where it comes from
  orama network use <name>                    make one active
  orama network add <name> <gateway-url>      reach a cluster by its gateway
  orama network add <manifest-url>            trust a network that publishes a manifest
  orama network current                       the active network
  orama network remove <name>                 forget one

orama network add <manifest-url> | <name> <gateway-url> [description] [flags]

Add a network, one of two ways.

With one argument, a manifest URL: https://<host>/<path>/manifest.json. The
manifest names the chain id, the genesis digest, the seeds, the release channel
and the digest of the release root the network's software is verified against.
The command fetches it (https only, size-bounded) and the release-root.json
beside it, checks the root against the digest, shows the chain id and the digest,
and asks you to type yes. Nothing is stored before that. --yes confirms for a
script; the digest is then the only thing you trust, so a script should pass the
URL of a manifest it already checked.

With a name and a gateway URL, a cluster you reach through that gateway (and an
optional description). The URL must be https:// with a host (http:// only for a
gateway on this machine: localhost or a loopback address), because every command
sends its credential there. --ca-file trusts a PEM bundle for this gateway's
domain and every name under it, in addition to the system roots: a cluster on
Let's Encrypt's staging CA, or on a private CA. It is not trusted for any other
host. --network records which registry network the cluster runs on.

orama network current

orama network list

List the networks of the registry (built into this binary or added by URL) and the
gateways you configured, one row each. A name that is both shows both. The active
network is marked with *.

orama network remove <name>

Forget the network of that name: the one you added by URL and the gateway you
configured, whichever exist. A network built into this binary stays in the list.
A name that is neither is not an error.

orama network use <name>