Download Latest Version v0.4.1-rc1 source code.zip (2.2 MB)
Home / v0.4.0-rc2
Name Modified Size InfoDownloads / Week
Parent folder
README.md 2026-11-13 4.8 kB
v0.4.0-rc2 source code.tar.gz 2026-11-13 2.2 MB
v0.4.0-rc2 source code.zip 2026-11-13 2.2 MB
Totals: 3 Items   4.4 MB 0

Note: Every download is signed. The macOS builds carry an Apple Developer ID signature and Apple notarization, so they install with no Gatekeeper warning and no Terminal command. The Windows builds carry an Authenticode signature issued to HADAMARD GATE INCORPORATED. Each release also publishes SHA256SUMS and an OpenPGP signature over that file. See Verify Your Download.

Quick Install

macOS / Linux:

:::sh
curl -fsSL https://gitlab.com/quip.network/quip-node-manager/-/raw/v0.4.0-rc2/scripts/install.sh | sh

Windows (PowerShell):

:::powershell
irm https://gitlab.com/quip.network/quip-node-manager/-/raw/v0.4.0-rc2/scripts/install.ps1 | iex

Manual Install

macOS

Download the .dmg, open it, and drag the app to /Applications.

Linux

The recommended format is AppImage (works on any distro):

:::sh
chmod +x quip-node-manager-linux-x86_64.AppImage
./quip-node-manager-linux-x86_64.AppImage

A .deb package is also available for Debian/Ubuntu:

:::sh
sudo dpkg -i quip-node-manager-linux-x86_64.deb

A signed .rpm package is available for Fedora, RHEL and openSUSE:

:::sh
sudo rpm --import https://gitlab.com/quip.network/quip-node-manager/-/raw/v0.4.0-rc2/.gitlab/release-signing-key.asc
sudo rpm -i quip-node-manager-linux-x86_64.rpm

Windows

Download the .exe and run it. Windows names HADAMARD GATE INCORPORATED as the publisher. SmartScreen may still warn until the certificate builds reputation across enough downloads. Click More info, then Run anyway.

Verify Your Download

scripts/install.sh checks the checksum on every run, and checks the signature as well when gpg is installed. scripts/install.ps1 checks the checksum and the Authenticode signature on every run, and the OpenPGP signature as well when gpg is installed. To check a download by hand instead, expand the section below.

Manual verification steps ### Checksums, every platform Download `SHA256SUMS` and `SHA256SUMS.asc` from this release, then import the release key and check both the signature and the checksum: :::sh curl -fsSLO https://gitlab.com/quip.network/quip-node-manager/-/raw/v0.4.0-rc2/.gitlab/release-signing-key.asc gpg --import release-signing-key.asc gpg --verify SHA256SUMS.asc SHA256SUMS sha256sum --check --ignore-missing SHA256SUMS On macOS, use `shasum -a 256 --check --ignore-missing SHA256SUMS` for the last step. `gpg --verify` must report a good signature from this key: | Item | Value | |------|-------| | Key | `Quip Node Manager Release Signing <rick@postquant.xyz>` | | Fingerprint | `A63860E21E7070C2C26FDA5DC85BEAB01AD9FEE3` | | Type | RSA 4096, expires 2029-09-16 | GnuPG reports the key as untrusted until you sign it yourself. That warning is expected. Compare the fingerprint in the output against the value above. ### macOS :::sh xcrun stapler validate quip-node-manager-macos-universal.dmg spctl --assess --type open --context context:primary-signature -v quip-node-manager-macos-universal.dmg `stapler` must report `The validate action worked`. `spctl` must report `accepted` and `source=Notarized Developer ID`. ### Windows :::powershell Get-AuthenticodeSignature .\quip-node-manager-windows-x86_64.exe | Format-List `Status` must read `Valid`, and `SignerCertificate.Subject` must name `HADAMARD GATE INCORPORATED`. ### Linux RPM :::sh sudo rpm --import release-signing-key.asc rpm --checksig quip-node-manager-linux-x86_64.rpm The output must read `digests signatures OK`. An unsigned package reports `digests OK` and still exits 0, so read the words, not the exit status. The `.deb` and the AppImage carry no embedded signature. Check those two against `SHA256SUMS` as shown above.

v0.4.0-rc2

The stack joins the Aglais relaunch on runtime 120

Aglais restarted from a fresh genesis on runtime specification 120. The chain name, chain ID, bootnodes, and faucet do not change.

  • The manager ships the new chain specification and requires validator v0.5.0-rc2 or later. The validator has no stable release at that version or later, so both channels resolve to v0.5.0-rc2 today.
  • The validator keeps its database in data/aglais-120-chain-db and the dashboard keeps its index in dashboard-data-120. The old chain cannot serve the new genesis, so the next Start syncs the validator and rebuilds the dashboard index from block 0.
  • The manager does not delete data/aglais-119-chain-db or dashboard-data-119. Delete them yourself to recover the disk space.
  • The miner funds and registers its account again on the new chain, through the faucet, on its first start.

Source: README.md, updated 2026-11-13