Uninstall

Remove Dassie from a server you installed it on with the installer. The node's data stays until you delete it yourself, so you can change your mind.

Before you start

If you mean to delete the node for good, move its money out while it still runs. It is test money, but you may want it on another node.

• Withdraw what the node holds in its settlement hubs to its XRP Ledger account, in the wallet's Hubs page or with dassie hub withdraw.
• Keep your recovery phrase. The keys of the node's XRP Ledger accounts derive from it, so the phrase brings them back on a new node. Your recovery phrase says what else it brings back.

If you're moving the node to another server instead, see Back up and move a node.

Remove Dassie

Run the installer with uninstall:

$curl --proto =https --tlsv1.2 -sSf https://sh.dassie.land | sh -s -- uninstall

It asks for sudo where it needs root, and shows each command it runs as root. It:

1. checks that no update is running: if one is, it stops and changes nothing, so run it again once the update is done;
2. stops and disables the node and its units: dassie.service, its sockets (dassie-http.socket, dassie-https.socket, dassie-ipc.socket, dassie-quic.socket, dassie-feed.socket) and the updater (dassie-update.service, dassie-update.timer);
3. removes those unit files from /etc/systemd/system;
4. removes /opt/dassie, with every installed version, and the dassie command in /usr/local/bin.

When it is done, it says what it left behind:

▶ Dassie is uninstalled
  The node's data stays in /var/lib/private/dassie, and the group dassie-users stays too.

The same command removes an install made with --no-service, which has no units to stop. It still asks systemd to reload its units, though, so on a machine without systemd, such as a container, it stops with an error before it removes anything. There, remove the files yourself:

$sudo rm -rf /opt/dassie /usr/local/bin/dassie

What stays

Delete the data

Once Dassie is uninstalled, delete the data and the link to it:

$sudo rm -rf /var/lib/private/dassie /var/lib/dassie

Then the drop-ins, if you made any:

$sudo rm -rf /etc/systemd/system/dassie.service.d /etc/systemd/system/dassie-update.timer.d
$sudo systemctl daemon-reload

And the group:

$sudo groupdel dassie-users

Installing again

If you kept the data, install as before (Quick Start). The installer puts the newest release in place and starts the node, which finds its database and carries on with the same identity, books and settings. There's no need to run dassie init or set it up again.

A node that was down for a while may have missed releases. The installer installs the newest, which reads a database from 0.3.0 or any later release; Keeping up with the network says what a node that was away misses.

Data left by a release before 0.3.0 (0.1 or 0.2) doesn't carry over. Those releases ran the early test network, and the node refuses their database and doesn't start. Move that data aside and set the node up again with a new phrase; it starts with empty books (A node from the 0.2 releases).

On NixOS and in the desktop app

On NixOS, the installer isn't involved: turn the module off in your configuration and rebuild. Dassie on NixOS shows how. The node's data stays there too, in /var/lib/private/dassie.

The desktop app keeps its node's data in your home directory, in ~/.local/share/dassie (or $XDG_DATA_HOME/dassie, if you set it), and the installer doesn't touch it. Install the desktop app covers the app.