@needmoretruth/nmts-cli 0.35.0 → 0.36.2

package/dist/walrus.d.ts

@@ -28,22 +28,7 @@ export declare const RELAY_HOSTS: Readonly<Record<string, readonly string[]>>;
 export declare const SUI_RPC_HOSTS: Readonly<Record<string, readonly string[]>>;
 /** How long one host gets before the next is tried. A read that stalls is a read that failed. */
 export declare const READ_TIMEOUT_MS = 60000;
-/**
- * Point reads at somebody else's aggregator, or at a development stack.
- *
- * ⚠ It replaces the list rather than adding to it, and that is deliberate: a run should read from
- *   where it was told to read, not from there AND the public hosts. Comma-separated for more
- *   than one, tried in the order given.
- */
-export declare const AGGREGATOR_ENV_VAR = "NMTS_AGGREGATOR";
-/**
- * Push writes through somebody else's relay, or through a development stack.
- *
- * ⚠ ONE host, not a list. Unlike reads there is nothing to fail over to — see `RELAY_HOSTS`.
- */
-export declare const RELAY_ENV_VAR = "NMTS_RELAY";
-/** Ask a different Sui JSON-RPC node the shard-count question. */
-export declare const SUI_RPC_ENV_VAR = "NMTS_SUI_RPC";
+export { AGGREGATOR_ENV_VAR, RELAY_ENV_VAR, SUI_RPC_ENV_VAR } from "./env-vars.ts";
 /** The relay this run writes through: the environment's if it named one, else the network's. */
 export declare function relayHost(network: string): string;
 /**

package/dist/walrus.js

@@ -10,7 +10,9 @@
 //    them: here, the browser build, and the standalone recovery tool. One copy going stale shows
 //    up as "file not found", which reads as "the file is gone" — so the machine holds them level
 //    rather than a person remembering to.
+import { AGGREGATOR_ENV_VAR, RELAY_ENV_VAR, SUI_RPC_ENV_VAR } from "./env-vars.js";
 import { NmtsError } from "./errors.js";
+import { host as runtime } from "./host.js";
 /** Curated Walrus aggregator (read) endpoints per network, preference order. */
 export const AGGREGATOR_HOSTS = {
     testnet: ["https://aggregator.walrus-testnet.walrus.space"],
@@ -50,34 +52,21 @@ export const SUI_RPC_HOSTS = {
 };
 /** How long one host gets before the next is tried. A read that stalls is a read that failed. */
 export const READ_TIMEOUT_MS = 60_000;
-/**
- * Point reads at somebody else's aggregator, or at a development stack.
- *
- * ⚠ It replaces the list rather than adding to it, and that is deliberate: a run should read from
- *   where it was told to read, not from there AND the public hosts. Comma-separated for more
- *   than one, tried in the order given.
- */
-export const AGGREGATOR_ENV_VAR = "NMTS_AGGREGATOR";
-/**
- * Push writes through somebody else's relay, or through a development stack.
- *
- * ⚠ ONE host, not a list. Unlike reads there is nothing to fail over to — see `RELAY_HOSTS`.
- */
-export const RELAY_ENV_VAR = "NMTS_RELAY";
-/** Ask a different Sui JSON-RPC node the shard-count question. */
-export const SUI_RPC_ENV_VAR = "NMTS_SUI_RPC";
+// Re-exported so every caller still finds them here; the names themselves live in a module with no
+// imports, because `nmts --help` prints them (`env-vars.ts`).
+export { AGGREGATOR_ENV_VAR, RELAY_ENV_VAR, SUI_RPC_ENV_VAR } from "./env-vars.js";
 /** The relay this run writes through: the environment's if it named one, else the network's. */
 export function relayHost(network) {
-    const named = process.env[RELAY_ENV_VAR]?.trim();
+    const named = runtime().env(RELAY_ENV_VAR)?.trim();
     if (named)
         return named;
-    const host = RELAY_HOSTS[network]?.[0];
-    if (host === undefined) {
+    const known = RELAY_HOSTS[network]?.[0];
+    if (known === undefined) {
         throw new NmtsError(`No upload relay is known for the ${network} storage network.`, {
             nextStep: `Name one in ${RELAY_ENV_VAR} to upload anyway.`,
         });
     }
-    return host;
+    return known;
 }
 /**
  * Every Sui JSON-RPC node this run may ask, in order.
@@ -88,7 +77,7 @@ export function relayHost(network) {
  *    they did not choose.
  */
 export function suiRpcHosts(network) {
-    const named = process.env[SUI_RPC_ENV_VAR]?.trim();
+    const named = runtime().env(SUI_RPC_ENV_VAR)?.trim();
     if (named)
         return [named];
     const hosts = SUI_RPC_HOSTS[network];
@@ -104,7 +93,7 @@ export function suiRpcHost(network) {
     return suiRpcHosts(network)[0] ?? "";
 }
 function fromEnvironment() {
-    const raw = process.env[AGGREGATOR_ENV_VAR];
+    const raw = runtime().env(AGGREGATOR_ENV_VAR);
     if (raw === undefined)
         return null;
     const hosts = raw.split(",").map((h) => h.trim()).filter((h) => h !== "");

package/docs/commands/credits.md

@@ -27,7 +27,7 @@ is spent by moving credits, and running the same command the other way puts them
 The credits keep the expiry they already had. The move drains the soonest-expiring lots first, so
 sending 100 may arrive as several grants with different dates, and moving them never renews them.
 
-Four refusals, four different remedies, and none of them is a retry:
+Four refusals, none of them worth retrying:
 `CREDIT_TRANSFER_OUTSIDE_FAMILY` (name an account of your own) · `CREDIT_TRANSFER_SELF` (that is
 the account sending) · `CREDIT_TRANSFER_INSUFFICIENT` (send less — the refusal carries what was
 needed and what the account can spend) · `CREDIT_TRANSFER_ZERO` (send some). Nothing is moved and

package/docs/commands/platform.md

@@ -0,0 +1,15 @@
+# nmts platform — the key pair a business signs with
+
+Commands: platform
+Tiers: platform=none · platform.keygen=medium
+
+`platform keygen` makes an Ed25519 key pair and writes both halves to `nmts-business-key.json`, or
+to `--out <file>`, with mode 0600 (on Windows, where no file mode applies, it removes the inherited
+permissions with `icacls` and leaves your account alone on the file, and says so if that fails). It
+refuses a name that already exists, whatever `--force` says, and prints only the public half.
+`platform register` cannot register it: that needs a signed-in browser session at nmts.me, under
+Settings › Developer › Platform, and the command prints that path and exits 2.
+
+The private half is what signs every request a business makes and every delegation token it mints
+for one of its users. Nothing can derive it again, and replacing the registered key invalidates every
+token the old one signed.

package/docs/commands/support.md

@@ -13,4 +13,4 @@ English. One report per problem.
 
 In the default mode it prints what it would send and asks (or takes `--yes`); in an auto mode it
 sends after printing. Replies arrive in the thread: `support list`, `support show <code>`,
-`support reply <code> --message`. If the CLI itself cannot run, the second door is nmts@nmts.me.
+`support reply <code> --message`. If the CLI itself cannot run, write to nmts@nmts.me.

package/docs/commands/trash.md

@@ -1,4 +1,4 @@
-# nmts rm, restore, sweep, erase — the trash, and the one way past it
+# nmts rm, restore, sweep, erase — the trash, and erasing for good
 
 Commands: rm, restore, sweep, erase
 Tiers: rm=low · restore=low · sweep=medium · erase=ultra-high · erase.release=ultra-high(release-storage)

package/docs/commands/wallet.md

@@ -17,9 +17,11 @@ kept inside your sealed file list, so the browser, this tool and every other dev
 Numbers come from the key, so a wallet cannot be deleted, and a wallet you leave keeps whatever is
 in it.
 
-`put`, `push`, `extend`, `wallet send` and `wallet donate` all pay from that wallet, and each takes
-`--wallet <number>` to pay from a different one for that run only, without changing the setting.
-⛔ If the file list cannot be read, they refuse rather than falling back to wallet 0 — paying from
+`put`, `push`, `extend`, `wallet send` and `wallet donate` all pay from that wallet. The same
+number decides the rest: `wallet swap` swaps its coins, `wallet storage split|merge|transfer`
+reshapes the resources it holds, and `wallet hall --name` signs as its address. Each takes
+`--wallet <number>` to use a different one for that run only, without changing the setting.
+⛔ If the file list cannot be read, they refuse rather than falling back to wallet 0 — signing with
 a wallet nobody chose is not a thing to guess at.
 
 ## Where SUI comes from, and why it is SUI
@@ -28,8 +30,8 @@ You can store without any coin here: credits pay the network for you (the weekly
 nmts.me, or credits somebody gave you), and `nmts balance` shows them. The wallet matters only when
 you pay the network yourself.
 
-The files live on Walrus, and Walrus is paid on the Sui chain in WAL, with gas in SUI. That is why
-this wallet holds SUI and WAL and nothing else — not a preference, the chain the storage runs on.
+The files live on Walrus, and Walrus is paid on the Sui chain in WAL, with gas in SUI, so
+this wallet holds SUI and WAL and nothing else.
 Fiat is not taken because taking it would make NMTS hold your money, which it never does.
 
 Getting SUI (as of 2026-09-06): buy it on an exchange that lists it (Binance and Upbit did on that
@@ -77,5 +79,7 @@ One more reads the gifts back, and one flag on it publishes a name:
 - `wallet hall` prints the gift hall of fame — the developer, then the ten largest senders as read
   from the public chain, with the rest of the list at nmts.me/hall; reading it signs nothing and
   needs no NMTS key. `--name <name>` (1 to 24 characters, no links, not an address) signs a
-  short message with this account's wallet so the server shows that name beside the address, and
-  `--remove` puts the entry back to a shortened address.
+  short message with the wallet this account pays from — the wallet a gift left from — so the
+  server shows that name beside its address, and `--remove` puts the entry back to a shortened
+  address. Reading which wallet that is opens the file list, so naming yourself needs an API key
+  where reading the hall needs none.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@needmoretruth/nmts-cli",
-  "version": "0.35.0",
+  "version": "0.36.2",
   "description": "Command-line and MCP access to NMTS (NeedMoreTruthStorage, https://nmts.me): open-source, end-to-end encrypted storage on the Walrus network. No fee to NMTS; you pay the network from your own wallet. For people and for their agents.",
   "license": "Apache-2.0",
   "publishConfig": {
@@ -41,6 +41,14 @@
       "types": "./dist/index.d.ts",
       "default": "./dist/index.js"
     },
+    "./portable": {
+      "types": "./dist/portable.d.ts",
+      "default": "./dist/portable.js"
+    },
+    "./host": {
+      "types": "./dist/host.d.ts",
+      "default": "./dist/host.js"
+    },
     "./api": {
       "types": "./dist/api.d.ts",
       "default": "./dist/api.js"
@@ -81,6 +89,7 @@
       "types": "./dist/wallet-sign.d.ts",
       "default": "./dist/wallet-sign.js"
     },
+    "./vendor/nmts-crypto/*": "./vendor/nmts-crypto/*",
     "./package.json": "./package.json"
   },
   "engines": {
@@ -100,7 +109,7 @@
   "scripts": {
     "compile": "tsc -p tsconfig.json",
     "typecheck": "tsc -p tsconfig.json --noEmit",
-    "test": "node --test \"test/**/*.test.ts\""
+    "test": "node --import ./test/host.ts --test \"test/**/*.test.ts\""
   },
   "devDependencies": {
     "@types/node": "^24.3.0",
@@ -109,6 +118,8 @@
   "dependencies": {
     "@mysten/sui": "^2.20.1",
     "@mysten/walrus": "^1.2.3",
+    "@noble/curves": "^2.3.0",
+    "@noble/hashes": "^2.2.0",
     "uqr": "^0.1.3"
   },
   "mcpName": "io.github.needmoretruth/nmts"