Release process

From Bitcoin Wiki
Revision as of 22:22, 15 October 2012 by Sgornick (talk | contribs) (→‎Verifying The Download: Add mention of script to verify the binaries.)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Bitcoin Open Source Release Process

Releases to the Bitcoin.org client project are built and released using this process:

  • Labeled in github
  • Binaries are created for the platforms affected (usually all, Windows, Mac and Linux).
  • Binary file checksum(s) is(are) calculated and a message with those are signed by a core developer.
    • sha256 checksum
  • Files used to build are checksummed and submitted to the Gitian.sigs project on github.
  • Uploaded to sourceforge
  • Blog post on Bitcoin.org
  • Forum post on BitcoinTalk.org

Verifying The Download

To verify the checksum for a binary download, first ensure the checksum file is secure by decrypting the SHA256SUMS.asc file:

$ gpg --decrypt SHA256SUMS.asc

Then verify the file checksum:

$ openssl dgst -sha256 [binary release archive]

Verify that the checksum matches the one in SHA256SUMS.asc

A script to verify the binaries was contributed to the Bitcoin.org project.

External Links

See Also