Downloads

Release artifacts

The repository currently ships Windows binaries in Releases/:

File	Purpose
`bootstrap-v1.0.exe`	Bootstrap node
`peer-node-v1.0.exe`	Peer CLI
`bootstrap-v1.1.exe`	Updated bootstrap node
`peer-v1.1.exe`	Updated peer CLI
`gui-v1.1.exe`	Fyne desktop client

These are the files to mirror or package when you want to distribute the current builds.

Live release panel

Loading live data from GitHub...

Repository

Name: -

Description: -

Stars: -

Language: -

Last push: -

Latest Release

Tag: -

Published: -

Assets: -

Open release notes

Open Issues

Count: -

Open Milestones

Count: -

Build from source

From Network/:

go build -o bootstrap ./cmd/bootstrap
go build -o peer ./cmd/peer
go build -o gui ./cmd/gui

The repository also has a Makefile:

make bootstrap
make peer

And a Windows build script:

powershell -File build.ps1 -OutDir ./bin -v 1.1

That script builds every package in cmd/ and names the output name-version.exe. The GUI build uses the Windows GUI subsystem flag.

What to expect from each binary

bootstrap asks for a name, prints multiaddrs, and writes bs-nodes
peer reads bs-nodes, joins the network, and runs discovery
gui opens a desktop window and wraps the same shared node package

When to use source builds

Build from source when you want to:

change the node package
test the current branch instead of a published release
produce your own platform-specific binaries

Notes on platforms

The current published artifacts are Windows executables. If you need macOS or Linux builds, compile them locally from Network/ with your target Go toolchain and build tags.

Release Notes - current release inventory
How to Use - build and run instructions
Deployment - running binaries outside local testing