release: tag-triggered binaries and a README that states the measured rates #28
Reference in New Issue
Block a user
Delete Branch "release/binaries-and-readme"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For independent miners (quantus/miner#27). The repository is public but had no on-ramp: no releases, and a README that still opened with upstream's build instructions.
release.yaml: pushing av<version>-lair.<n>tag buildsquantus-minerandquantus-benchon the cuda-13.0 runner (Fedora 43, nvcc, so the binary carries sm_86/sm_89/sm_120 cubins plus PTX) with the tag's commit in--version, and publishes a Gitea release with the tarball, its sha256 and a BUILD.txt (commit, toolchain, glibc). Excluded from deploy triggers; a release changes nothing on the fleet.--cuda-gpuengine and the two closed pool binaries; where the binaries are and what they need; the exactquantus-benchcommands for the hashrate and the 2000-job parity check; the interleaved-rounds method; and the statement that there is no dev fee, licence server or telemetry.LAIR_MINBLOCKSknob commit (c1cac91, no default change) so the redeploy this merge triggers is not for nothing.First tag after merge:
v4.0.2-lair.1.🤖 Generated with Claude Code
https://claude.ai/code/session_01Ue5ZZm1Hiv5zPnucykKKuF
quantus-bench
7831323362on benjy.hanzalova.internaltotal median: 708.54 MH/s (batch 1000000, 5 x 30s, engine gpu-cuda)
--- resume miner ---
active