The four per-platform CLI install commands in src/getting-started/requirements.md (lines 65, 75, 85, 95) all return 404. The same broken URLs are duplicated in src/getting-started/dev-environment-setup.md and src/getting-started/validator-staking.md.
Each command points at https://github.com/Arch-Network/arch-node/releases/latest/download/cli-<platform>. The /releases/latest/download/ redirect resolves fine to the current release (v0.8.8), but no asset named cli-<platform> exists in it. Two separate problems are stacked here.
1. Asset names have gained an arch-cli- prefix. For the two platforms that are still built, the documented name is just missing the prefix:
| Documented (404) |
Actual asset in v0.8.8 |
cli-aarch64-apple-darwin |
arch-cli-aarch64-apple-darwin |
cli-x86_64-unknown-linux-gnu |
arch-cli-x86_64-unknown-linux-gnu |
2. The other two platforms have no asset at all in v0.8.8. x86_64-apple-darwin (macOS Intel) and aarch64-unknown-linux-gnu (Linux ARM64) are documented with download commands, but v0.8.8 publishes no release asset of any kind for either target, not the CLI and not the validator or plugin binaries either. The full asset list for v0.8.8 is:
arch-cli-aarch64-apple-darwin
arch-cli-x86_64-unknown-linux-gnu
libarch_plugin_kafka-aarch64-apple-darwin.dylib
libarch_plugin_kafka-x86_64-unknown-linux-gnu.so
local_validator-aarch64-apple-darwin
local_validator-x86_64-unknown-linux-gnu
v0.8.8.json
validator-aarch64-apple-darwin
validator-x86_64-unknown-linux-gnu
So a new user on macOS Intel or Linux ARM64 who follows the getting-started guide hits a dead command with no working alternative on the page. requirements.md is the first install page the Prerequisites flow routes to, so this is day-one onboarding.
For the two built platforms the fix is just the corrected filename. For macOS Intel and Linux ARM64 I did not want to guess: is dropping those targets intentional, or a gap in the release build matrix? That changes whether the docs should point at corrected URLs or instead say those platforms are not currently prebuilt (with build-from-source as the path). Happy to open a PR for the two filename corrections once the intended direction on the other two is clear.
Reproduction (checked 2026-08-30):
curl -sL -o /dev/null -w "%{http_code}\n" https://github.com/Arch-Network/arch-node/releases/latest/download/cli-aarch64-apple-darwin
# 404
curl -sL -o /dev/null -w "%{http_code}\n" https://github.com/Arch-Network/arch-node/releases/latest/download/arch-cli-aarch64-apple-darwin
# 200
Not a duplicate of #37 (2025, a book-hosted install.sh link, since fixed via #38); this is the current arch-node release-asset naming and platform coverage.
The four per-platform CLI install commands in
src/getting-started/requirements.md(lines 65, 75, 85, 95) all return 404. The same broken URLs are duplicated insrc/getting-started/dev-environment-setup.mdandsrc/getting-started/validator-staking.md.Each command points at
https://github.com/Arch-Network/arch-node/releases/latest/download/cli-<platform>. The/releases/latest/download/redirect resolves fine to the current release (v0.8.8), but no asset namedcli-<platform>exists in it. Two separate problems are stacked here.1. Asset names have gained an
arch-cli-prefix. For the two platforms that are still built, the documented name is just missing the prefix:cli-aarch64-apple-darwinarch-cli-aarch64-apple-darwincli-x86_64-unknown-linux-gnuarch-cli-x86_64-unknown-linux-gnu2. The other two platforms have no asset at all in v0.8.8.
x86_64-apple-darwin(macOS Intel) andaarch64-unknown-linux-gnu(Linux ARM64) are documented with download commands, but v0.8.8 publishes no release asset of any kind for either target, not the CLI and not the validator or plugin binaries either. The full asset list for v0.8.8 is:So a new user on macOS Intel or Linux ARM64 who follows the getting-started guide hits a dead command with no working alternative on the page.
requirements.mdis the first install page the Prerequisites flow routes to, so this is day-one onboarding.For the two built platforms the fix is just the corrected filename. For macOS Intel and Linux ARM64 I did not want to guess: is dropping those targets intentional, or a gap in the release build matrix? That changes whether the docs should point at corrected URLs or instead say those platforms are not currently prebuilt (with build-from-source as the path). Happy to open a PR for the two filename corrections once the intended direction on the other two is clear.
Reproduction (checked 2026-08-30):
Not a duplicate of #37 (2025, a
book-hostedinstall.shlink, since fixed via #38); this is the currentarch-noderelease-asset naming and platform coverage.