Difference between revisions of "Release process"

From Bitcoin Wiki
Jump to: navigation, search
(External Links: Add entry for Bitcoin Core Release Process on Github.)
(Verifying The Download: replace incorrect and misleading information with links to proper resources)
Line 14: Line 14:
 
==Verifying The Download==
 
==Verifying The Download==
  
To verify the checksum for a binary download, first ensure the checksum file is secure by decrypting the SHA256SUMS.asc file:
+
See the verification instructions [https://bitcoincore.org/en/download/ on the Bitcoin Core download page].
$ gpg --decrypt SHA256SUMS.asc
 
  
Then verify the file checksum:
+
Or try the [https://github.com/bitcoin/bitcoin/tree/master/contrib/verifybinaries script in the Bitcoin Core repository].
$ openssl dgst -sha256 [binary release archive]
 
 
 
Verify that the checksum matches the one in SHA256SUMS.asc
 
 
 
A [https://github.com/bitcoin/bitcoin/pull/1935 script to verify the binaries] was contributed to the Bitcoin.org project.
 
  
 
==External Links==
 
==External Links==

Revision as of 12:06, 9 August 2019

Bitcoin Core Open Source Release Process

Releases to the Bitcoin Core client and 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 distribution (Bitcoin.org/bin, and Launchpad.net for the Ubuntu PPA)
  • Blog post on Bitcoin.org
  • Forum post (sticky) on BitcoinTalk.org

Verifying The Download

See the verification instructions on the Bitcoin Core download page.

Or try the script in the Bitcoin Core repository.

External Links

See Also