Gridcoin

For Gridcoin binaries, see the GitHub releases page. For more information, see Run ./build targets.sh --help for all options, including Qt5/Qt6 selection, ccache, build type, and more. Developers work in their own trees, then submit pull requests to the development branch when they think their feature or bug fix is ready. The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if they don't match the project's coding conventions (see developer-notes.md) or are controversial. The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are regularly created to indicate new stable release versions of Gridcoin. Feature branches are created when there are major new features being worked on by several people. Gridcoin uses five branches to ensure stability without slowing down the pace of the daily development activities - development , testnet , staging , master and hotfix . When development is ready for broader testing, it is merged to testnet where tagged testnet pre-releases are published. This branch is used extensively for integration testing of consensus changes, hard fork activation, and new features on the Gridcoin test network before any production release. For general questions, please visit our Discord server, Matrix room, or Libera Chat in gridcoin-help.