update

A command that downloads newer Docker images used by a Dash blockchain node.

In plain words
What is it for?
Updating one or more node configurations and viewing the results as plain text, JSON, or YAML before restarting services to use the new images.
Why use it?
It updates the node's service images and reports whether each one changed, stayed current, or failed to update.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/dashpay/platform/update
Clone the repo
git clone --depth 1 https://github.com/dashpay/platform
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 495 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00495
Opus 5 $0.00000 $0.00247
Sonnet 5 $0.00000 $0.00099
Haiku 4.5 $0.00000 $0.00049

Measured yesterday against content hash ec00c42ed6cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

update scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/dashmate/docs/commands/update.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

update

The update command updates the node's Docker images to their latest versions.

Usage

dashmate update [OPTIONS]

Options

Option Description Default
-c, --config=<name> Configuration to update Uses default config if not specified
--format=<format> Display output format (plain, json, yaml) plain

Description

This command updates the Docker images used by a Dash node to their latest versions. It pulls the latest images specified in the configuration and reports on which services were updated.

The command displays a table showing:

  • Service names
  • Docker image identifiers
  • Update status (updated, up to date, or error)

Services that were updated are highlighted in yellow, services that were already up to date are shown in green, and any errors are displayed in red.

This command only updates the Docker images; it does not automatically restart services to use the new images. After updating, you typically need to restart the node with the restart command to apply the updates.

Examples

# Update the default configuration
dashmate update

# Update a specific configuration
dashmate update --config=testnet

# Update and display results in JSON format
dashmate update --format=json

Example output:

┌─────────────────┬──────────────────────────────┬────────────┐
│ Service         │ Image                        │ Updated    │
├─────────────────┼──────────────────────────────┼────────────┤
│ Core            │ dashpay/dashd:19.2.0        │ up to date │
│ Drive ABCI      │ dashpay/drive:1.0.0         │ updated    │
│ Tenderdash      │ dashpay/tenderdash:0.10.0   │ updated    │
│ DAPI API        │ dashpay/dapi:1.0.0          │ up to date │
│ Envoy Gateway   │ dashpay/platform-gateway:1.0 │ up to date │
└─────────────────┴──────────────────────────────┴────────────┘

Read the full file on GitHub · 63 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 63 lines · 0 tokens per session scan A ec00c42ed6cc

Subscribe to this mod's changes

update is a command published in the GitHub repository dashpay/platform (92 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 495 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.