v0.34.3

What changed

• Security. nmts wallet swap on Bluefin now calls only the contract package pinned in this
  release. Before, it read the "current" package from a public Sui node and preferred that answer,
  so a node giving a false answer could have sent the swap into someone else's code with your coin
  as the argument. The pinned package is still checked against the chain before a quote is shown;
  if that check refuses it, the Bluefin venue is unavailable until a release bumps the pin. DeepBook
  was never affected. No such node was observed and no loss is known.

Install

From the registry:

npm install -g @needmoretruth/nmts-cli@0.34.3

Or straight from this repository, without the registry:

npm install -g github:needmoretruth/nmts-cli#v0.34.3

Or, without a clone, from the tarball attached below:

npm install -g https://github.com/needmoretruth/nmts-cli/releases/latest/download/nmts.tgz

Node 22 or newer. Nothing is compiled by a C compiler and there is no native build
step; the encryption engine is a WebAssembly module carried in the package.

v0.34.2

What changed

• The README and the agent document open with what the name stands for — NMTS is
  NeedMoreTruthStorage — who builds it, and the site, https://nmts.me; the package description
  says the same. No behaviour changed.

Install

From the registry:

npm install -g @needmoretruth/nmts-cli@0.34.2

Or straight from this repository, without the registry:

npm install -g github:needmoretruth/nmts-cli#v0.34.2

Or, without a clone, from the tarball attached below:

npm install -g https://github.com/needmoretruth/nmts-cli/releases/latest/download/nmts.tgz

Node 22 or newer. Nothing is compiled by a C compiler and there is no native build
step; the encryption engine is a WebAssembly module carried in the package.

v0.34.1

What changed

• The advice printed for MANIFEST_TOO_LARGE no longer tells a program to ask the operator for a
  higher ceiling. The file list is stored in chunks and the room an account has for it grows with
  the files the storage network has confirmed; nobody raises it by hand. The advice now says to
  save once more so an old single-piece list becomes chunks, after which the ceiling is that
  allowance (details.allowed on MANIFEST_CHUNKS_EXCEEDED).

Install

From the registry:

npm install -g @needmoretruth/nmts-cli@0.34.1

Or straight from this repository, without the registry:

npm install -g github:needmoretruth/nmts-cli#v0.34.1

Or, without a clone, from the tarball attached below:

npm install -g https://github.com/needmoretruth/nmts-cli/releases/latest/download/nmts.tgz

Node 22 or newer. Nothing is compiled by a C compiler and there is no native build
step; the encryption engine is a WebAssembly module carried in the package.

v0.34.0

What changed

• nmts credits transfer --to <account identifier> <credits> moves credits from this account to
  another account of the same family — the account a person made, and every account made under it.
  Nothing reaches anyone else: a recipient outside the family and an account that does not exist
  are refused in the same words. The free trial's one place a week belongs to the whole family, so
  this is how the credits get to the account that needs them. Both balances come back, --json
  carries them, and there is an nmts_credits_transfer MCP tool. It is a medium act and needs the
  account's human check, like the trial; the credits keep the expiry they already had.

• nmts balance opens with AI account (not the main account) when the account it is signed in
  to was made under somebody else's for an AI to work in. Such an account has its own NMTS key,
  its own wallet and its own drive, and nothing said which kind you were holding. --json and the
  nmts_balance MCP tool carry the same fact as ai_account; an ordinary account sees nothing.

Install

From the registry:

npm install -g @needmoretruth/nmts-cli@0.34.0

Or straight from this repository, without the registry:

npm install -g github:needmoretruth/nmts-cli#v0.34.0

Or, without a clone, from the tarball attached below:

npm install -g https://github.com/needmoretruth/nmts-cli/releases/latest/download/nmts.tgz

Node 22 or newer. Nothing is compiled by a C compiler and there is no native build
step; the encryption engine is a WebAssembly module carried in the package.

v0.33.0

What changed

• The secret that opens an account is now called your NMTS key. It was the account code; only
  the word changed, and the wallet it derives is the NMTS key wallet. Help text, error
  messages, the MCP tool descriptions and the documentation say the new name.
• Nothing you have scripted breaks. The flags, the environment variables
  (NMTS_ACCOUNT_CODE, NMTS_ACCOUNT_CODE_FILE), the config keys, the MCP tool and argument
  names, the error codes and every file format keep the names they already had.

Install

From the registry:

npm install -g @needmoretruth/nmts-cli@0.33.0

Or straight from this repository, without the registry:

npm install -g github:needmoretruth/nmts-cli#v0.33.0

Or, without a clone, from the tarball attached below:

npm install -g https://github.com/needmoretruth/nmts-cli/releases/latest/download/nmts.tgz

Node 22 or newer. Nothing is compiled by a C compiler and there is no native build
step; the encryption engine is a WebAssembly module carried in the package.

v0.32.0

What changed

• The file list is saved in pieces. Editing one file now uploads the piece it is in instead of the
  whole list, so a rename costs the same on a drive of ten files and a drive of fifty thousand.
  Nothing about the drive changes and there is nothing to do: the first save after this version
  converts the account, and the pieces are kept on this machine by name so a later read fetches
  only what changed. nmts listfile writes the index and its pieces out as one file, as before.
• Node 22.15.0 or newer is now required (it was 22). That is the release where Node's own zlib
  learned zstd, which is what the pieces are compressed with.

Install

From the registry:

npm install -g @needmoretruth/nmts-cli@0.32.0

Or straight from this repository, without the registry:

npm install -g github:needmoretruth/nmts-cli#v0.32.0

Or, without a clone, from the tarball attached below:

npm install -g https://github.com/needmoretruth/nmts-cli/releases/latest/download/nmts.tgz

Node 22 or newer. Nothing is compiled by a C compiler and there is no native build
step; the encryption engine is a WebAssembly module carried in the package.

v0.31.0

What changed

• The credit deposit is now a choice: nmts deposit [credits] reads and sets what this account
  sets aside per credit-paid file (0 to 64, default 64), and put --deposit <n> / push --deposit <n> set it for one run. 0 sets nothing aside, and a release of that file costs twice the fee
  from the balance instead.
• nmts balance names the default and the ceiling the server states, and what each file with a
  deposit set aside and has spent; nmts erase --release-storage says what the release cost and
  whether it came out of the deposit, and refuses with both numbers when the balance cannot cover
  a doubled fee.

Install

From the registry:

npm install -g @needmoretruth/nmts-cli@0.31.0

Or straight from this repository, without the registry:

npm install -g github:needmoretruth/nmts-cli#v0.31.0

Or, without a clone, from the tarball attached below:

npm install -g https://github.com/needmoretruth/nmts-cli/releases/latest/download/nmts.tgz

Node 22 or newer. Nothing is compiled by a C compiler and there is no native build
step; the encryption engine is a WebAssembly module carried in the package.

v0.30.0

What changed

• The package now declares its MCP server for the official registry (server.json, mcpName),
  so nmts mcp can be listed there once the package is on npm.
• homepage points at https://nmts.me; this changelog appears on every release page.

Install

From the registry:

npm install -g @needmoretruth/nmts-cli@0.30.0

Or straight from this repository, without the registry:

npm install -g github:needmoretruth/nmts-cli#v0.30.0

Or, without a clone, from the tarball attached below:

npm install -g https://github.com/needmoretruth/nmts-cli/releases/latest/download/nmts.tgz

Node 22 or newer. Nothing is compiled by a C compiler and there is no native build
step; the encryption engine is a WebAssembly module carried in the package.

v0.29.0

From the registry:

npm install -g @needmoretruth/nmts-cli@0.29.0

Or straight from this repository, without the registry:

npm install -g github:needmoretruth/nmts-cli#v0.29.0

Or, without a clone, from the tarball attached below:

npm install -g https://github.com/needmoretruth/nmts-cli/releases/latest/download/nmts.tgz

Node 22 or newer. Nothing is compiled by a C compiler and there is no native build
step; the encryption engine is a WebAssembly module carried in the package.

v0.28.0

From the registry:

npm install -g @needmoretruth/nmts-cli@0.28.0

Or straight from this repository, without the registry:

npm install -g github:needmoretruth/nmts-cli#v0.28.0

Or, without a clone, from the tarball attached below:

npm install -g https://github.com/needmoretruth/nmts-cli/releases/latest/download/nmts.tgz

Node 22 or newer. Nothing is compiled by a C compiler and there is no native build
step; the encryption engine is a WebAssembly module carried in the package.