Repository navigation
v0.4.0-rc2
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
SHA256SUMSand an OpenPGP signature over that file. See
Verify Your Download.
Quick Install
macOS / Linux:
curl -fsSL https://gitlab.com/quip.network/quip-node-manager/-/raw/v0.4.0-rc2/scripts/install.sh | shWindows (PowerShell):
irm https://gitlab.com/quip.network/quip-node-manager/-/raw/v0.4.0-rc2/scripts/install.ps1 | iexManual Install
macOS
Download the .dmg, open it, and drag the app to /Applications.
Linux
The recommended format is AppImage (works on any distro):
chmod +x quip-node-manager-linux-x86_64.AppImage
./quip-node-manager-linux-x86_64.AppImageA .deb package is also available for Debian/Ubuntu:
sudo dpkg -i quip-node-manager-linux-x86_64.debA signed .rpm package is available for Fedora, RHEL and openSUSE:
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.rpmWindows
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:
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 SHA256SUMSOn 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
xcrun stapler validate quip-node-manager-macos-universal.dmg
spctl --assess --type open --context context:primary-signature -v quip-node-manager-macos-universal.dmgstapler must report The validate action worked. spctl must report
accepted and source=Notarized Developer ID.
Windows
Get-AuthenticodeSignature .\quip-node-manager-windows-x86_64.exe | Format-ListStatus must read Valid, and SignerCertificate.Subject must name
HADAMARD GATE INCORPORATED.
Linux RPM
sudo rpm --import release-signing-key.asc
rpm --checksig quip-node-manager-linux-x86_64.rpmThe 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-rc2or later. The validator has no stable release at that version
or later, so both channels resolve tov0.5.0-rc2today. - The validator keeps its database in
data/aglais-120-chain-dband the
dashboard keeps its index indashboard-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-dbor
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.