Skip to main content

Install

Download the binary for your platform from the GitHub releases page. To run it as dpm trace, register it with DPM.

Download the binary​

The binary has no dependencies, so after you unpack it, you can run ./dpm-trace right away. Builds exist for Linux, macOS, and Windows, on amd64 and arm64.

tar xzf dpm-trace_<version>_<os>_<arch>.tar.gz
./dpm-trace --version

The output is:

dpm-trace <version> (<commit>, built <date>)

On Windows, unpack the .zip and run dpm-trace.exe.

Build from source​

If you prefer to build it yourself, you need Go 1.25 or newer.

git clone https://github.com/walnuthq/dpm-trace.git
cd dpm-trace
go build -o dpm-trace ./cmd/trace
./dpm-trace --version
dpm-trace dev (none, built unknown)

Register with DPM​

Registering the binary lets you run it as dpm trace. This needs DPM and a Daml SDK installed. All commands in these docs use dpm trace, and dpm-trace <args> works the same way.

If you do not have DPM, install it with:

curl https://get.digitalasset.com/install/install.sh | sh
export PATH="$HOME/.dpm/bin:$PATH"
dpm install latest

The install script puts dpm in ~/.dpm/bin, which is not on your PATH by default. Add the export line to your shell profile so new shells find dpm.

Then register the binary:

./dpm-trace install-plugin
Registered dpm-trace <version> as a DPM plugin (SDK <sdk-version>) in <dpm-home>.
Run with: dpm trace --help

Register for each SDK version​

Registration applies to one SDK version: the one active in the current directory, or the highest installed. A project whose daml.yaml pins a different sdk-version does not see the plugin, and dpm trace fails there with unknown command "trace" for "dpm".

To fix it, register again for that version, either from inside the project or by naming the version:

cd <path-to-daml-project>
<path-to>/dpm-trace install-plugin
# or, from anywhere:
<path-to>/dpm-trace install-plugin --sdk-version <sdk-version>
note

dpm build and the local Canton also need a Java runtime version 17 or newer.