Preparing your documentation...
Prebuilt binaries for the matrix CLI and the matrixd node. Every archive is published as a GitHub release asset with a SHA256SUMS file generated over the artifacts themselves.
Each archive contains both matrix and matrixd, plus the licence and README. Sizes are reported by GitHub for the exact file you are downloading.
The release ships a SHA256SUMS file generated over the published archives. Check your download against it:
curl -fsSLO https://github.com/its-janghoon/matrix-os/releases/download/v0.5.4/SHA256SUMS
sha256sum -c SHA256SUMS --ignore-missingThis is the supported path today, and it is what the release workflow runs. You need Go (the version in services/core/go.mod) and buf, which generates the Protocol Buffers stubs the CLI imports.
git clone https://github.com/savagemanage/matrix-os.git
cd matrix-os
# Generate the Protocol Buffers stubs, then build both binaries.
make proto
cd services/core
go build -o matrix ./cmd/matrix
go build -o matrixd ./cmd/matrixd./matrix init # write a dev config to ~/.matrix
./matrixd & # start the node
./matrix quickstart # genesis -> fund -> provider -> first jobTargets the release workflow builds: linux/amd64, linux/arm64, darwin/amd64, darwin/arm64, windows/amd64, windows/arm64.