decred / decred-binaries Goto Github PK

View Code? Open in Web Editor NEW

56.0 25.0 40.0 1001 KB

Binary archives for Decred releases.

decred-binaries's Introduction

decred-binaries

Decred Binary Releases

This repository contains release notes and binaries released for Decred.

Available Releases

This repository contains releases for the following software:

Release notes

Notes for the current and previous releases can be found in the Release Notes document.

Verifying Binaries

For your security, we recommend that you verify binaries before running them. Each release contains a manifest file with SHA-256 hashes for each released binary. To ensure your downloads are authentic, you should verify that the manifest file is signed by [email protected], and that your hashed binary matches the manifest.

Detailed instructions can be found in the Decred Documentation: Verifying Binaries. New users should start there.

If you've already done this before and you still have the Decred Release keys on your GnuPG keyring, the following shorthand instructions are provided as a quick refresher:

Download:
- The zip/tarball for your specific OS / architecture
- The file manifest and hashes, ending in -manifest.txt
- The signature for the manifest, ending in -manifest.txt.asc

Verify that the manifest was directly signed by the Decred project:

$ gpg --verify <your manifest.txt.asc file>

Example output:

gpg: assuming signed data in 'decred-v1.5.1-manifest.txt'
gpg: Signature made 01/29/20 15:17:58 Eastern Standard Time
gpg:                using RSA key F516ADB7A069852C7C28A02D6D897EDF518A031D
gpg: Good signature from "Decred Release <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: FD13 B683 5E24 8FAF 4BD1  838D 6DF6 34AA 7608 AF04
   Subkey fingerprint: F516 ADB7 A069 852C 7C28  A02D 6D89 7EDF 518A 031D

If you see Good signature from "Decred Release <[email protected]>", then you're successful! You can trust that the manifest.txt came directly from the Decred project.

Verify that the hash of your downloaded zip/tarball matches the manifest hash:
- Windows:
  - If you have 7-Zip installed, simply open up Windows Explorer, right click on the file, mouseover CRC SHA, then click SHA-256.
  - $ certutil -hashfile <your file> SHA256
- macOS
  - $ shasum -a 256 <your file>
- Linux
  - $ sha256sum <your file>
Example output:
```
0c43caffa428cebb8a4d3c8efb2a341220fd1c232640ff3b4403ff67e1873e1a  decred-linux-amd64-v1.5.1.tar.gz
```

If your output hash matches the hash from the manifest, you're done! The binary for your platform is now verified and you can be confident it was generated by the Decred Project. It's safe to install the software.

Source code

This repo only contains build archives, build scripts, and similar content. For the source code, please see the individual repositories at: https://github.com/decred/

decred-binaries's People

Contributors

Stargazers

Watchers

decred-binaries's Issues

v1.3.1 release notes do not mention a new tool politeiavoter

Does this new distribution item deserve a mention?

Validate Paymetheus v1.0.0

Validate paymetheus on x86 and x64:

Windows 7 x64
Windows 10 x64

Make sure both icons launch paymetheus correctly.

In the comments note which OS you tested and the results.

Wrong year for 1.2.0

2017 -> 2018

https://github.com/decred/decred-binaries/blob/master/release-notes.md
https://github.com/decred/decred-binaries/releases/tag/v1.2.0

1.6RC4 (linux/kubuntu) Is mixer running or not?

Had mixer running. The circular mixing icon is spinning. Everything just works. ;)

Thinking of shutting down decrediton to do some computer updates.

However, turning "off" the mixer in the privacy panel results in the notification that the mixer is not running, however the circular mixing icon remains spinning. Hovering over the spinning icon reveals the tool tip that the mixer is still running, which is conflicting information.

Is the mixer running or not? Is it safe to close decrediton?

No manifest for Decrediton 1.1.3

The github repo only contains manifest for up to 1.1.2.

manifest-decrediton-v1.3.0.txt contains a hash of itself

Is it possible?

Validate dcrinstall v1.0.0 on all OSes

Validate dcrinstall upgrades on the following platforms:

Linux
Bitrig/OpenBSD
Windows
OSX

Validate dcrinstall clean install on the following platforms:

Linux
Bitrig/OpenBSD
Windows
OSX

Drop 32bit OSX builds.

Broken link for "decrediton Linux"

When visiting https://github.com/decred/decred-binaries/releases the link for the newest version of decrediton for linux, called "decrediton Linux" is broken. It is currently:
https://github.com/decred/decred-binaries/releases/download/v1.4.0/decrediton-1.4.0.tar.gz

It is missing a "v" in front of "1.4.0.tar.gz". Should be:
https://github.com/decred/decred-binaries/releases/download/v1.4.0/decrediton-v1.4.0.tar.gz

White Background on every panel

There is a white background (complete with drop shadow) obscuring every single pane in the 1.3.1 release of decrediton. (see screenshot)

macOS 10.14.

CUDA runtime libraries should be packaged with binaries

These shared libraries are required to run gominer (or anything using the CUDA runtime). They are only available with the CUDA toolkit, not the drivers, as they are intended for packaging with the binaries. They are redistrubutable royalty-free.

See Section 1.8 of the EULA : http://docs.nvidia.com/cuda/eula/index.html#attachment-a

The relevant part:

Component : CUDA Runtime
Windows : cudart.dll, cudart_static.lib, cudadevrt.lib
Mac OSX : libcudart.dylib, libcudart_static.a, libcudadevrt.a
Linux : libcudart.so, libcudart_static.a, libcudadevrt.a
Android : libcudart.so, libcudart_static.a, libcudadevrt.a

Visual Enhancement: Overview page

I'd recommend changing this color to something a bit darker. It's barely visible on the white background. Perhaps into what we use for the date.
https://d.pr/i/3TIWCU

resolve difference in packaging of sample configurations

Currently the sample files for dcrctl and dcrwallet are included with the release files but the sample file for dcrd is not. dcrd goes about it a different way, generating its own default sample configuration when creating the initial .dcrd directory.

The expected behavior is for the decred project to have a single agreed way to deliver the sample files to the users.

https://github.com/decred/dcrd/blob/master/sampleconfig/sampleconfig.go

https://github.com/decred/dcrd/blob/master/cmd/dcrctl/sample-dcrctl.conf

https://github.com/decred/dcrwallet/blob/master/sample-dcrwallet.conf

Add v1.5.0 rc1 manifests

README for v1.5.0 rc1 was committed but not the manifests.

https://github.com/decred/decred-binaries/releases/tag/v1.5.0-rc1

dont recommend the installer

"To install the command line tools, please see dcrinstaller."

This is the binaries repo. It shouldnt say that. Should probably say there is an installer or that binaries are available to alleviate user confusion.

validate v0.8.2 release

The upcoming v0.8.2 release needs some sanity checking/validating. Tests needed:

Please comment with what you tested (linux distro, etc).

Manifest does not have v1.1.2 file

Manifest files are missing the decrediton v1.1.2

Bad link on latest release page

On the releases page: https://github.com/decred/decred-binaries/releases

...the links to download the latest version (v1.1.0) of Paymetheus are broken. They point to:

https://github.com/decred/decred-binaries/releases/download/v1.0.8/decred_1.1.0-release_x64.msi

...instead of:

https://github.com/decred/decred-binaries/releases/download/v1.1.0/decred_1.1.0-release_x64.msi

(Note that the first version has "v1.0.8" in the path instead of "v1.1.0".)

People trying to download the latest version will therefore have trouble unless they realize the mistake and manually edit the URL to go to the right location.

Just wanted to let someone know that could fix it. Thanks.

Manifest for 1.21

Is it just me or is it missing?

Statistics: Stake Pools can't switch

Drop down menu for pools list work fine, but when you try to select a different pool it stays on what was selected by default.

https://d.pr/i/gQkOl5

required feature: decrediton support for raspberrypi arm64 linux

raspberrypi has released linux arm64. will decrediton release binary support it ? thanks alot

Validate dcrinstall v1.0.1

Validate dcrinstall upgrades on the following platforms:

Linux
Windows
OSX

Validate dcrinstall clean install on the following platforms:

Linux
Windows
OSX

ccminer default config file not updated for decred

The ccminer.conf in the win64 zip is not updated for Decred, still specifying vanilla algo and old vnl.suprnova.cc pool url, etc. Needs automatic build script that can be called by minersbuild.sh.

Remove links to old wiki

Old wiki is going away, use point links to other places.

Use -ldflags to set +release on release builds

improve manifest filenames

manifest filenames are currently of following form:

manifest-vX.Y.Z.txt is for the command line tools
manifest--vX.Y.Z.txt is for all other repos (dcrinstall, decrediton, paymetheus, etc)

to improve the ease with which these files can be found in file browsers and to avoid filename conflicts with other projects, i propose changing the format to roughly:

decredcli-manifest-vX.Y.Z.txt for command line tools
-manifest-vX.Y.Z.txt for other repos

RC-1 Build?

Will there be RC1 binaries?

Add promptsecret to builds

Once decred/dcrd#649 goes in, it needs to be added to the builds.

readme has wrong decrediton links

Where it says

To install decrediton download, uncompress, and run
decrediton Linux
or
decrediton OSX

Validate decrediton v1.0.0

Basic testing of the release build needs to be done on supported OSes

OSX x64
Linux x64

Testing more than one Linux disto is a good idea so please mention distro or version you tested in comments.

Confirm wallet seeds: Create New Seed, receive funds, send funds then recreate with dcrwallet and make sure they are the same.

If there are any other obvious things we need to add here, please add to the issue.

All this testing MUST be done on release builds which will be provided soon.

Insufficient balance error when balance appears to be sufficient

1.6rc4
Purchasing mixed tickets (164DCR), receive insufficient balance error despite having adequate balance (210DCR)
--screenshot attached

2020-12-13 08:13:20.554 [INF] WLLT: Reserved credits for 1 tickets: total fee: 0.00799484 DCR
2020-12-13 08:13:20.554 [INF] WLLT: Returning address (account=2 branch=1 child=62)
2020-12-13 08:13:20.578 [ERR] GRPC: Unary method /walletrpc.WalletService/PurchaseTickets invoked by 127.0.0.1:37164 errored: wallet.PurchaseTicketsWithResponse: insufficient balance:: txauthor.NewUnsignedTransaction

I can't confirm seed

in my case, with ubuntu 16.04, Decrediton 1.1.1

see https://forum.decred.org/threads/cant-confirm-seed-in-decredition-windows-64.5762/

Pascal

Icon on the taskbar (Windows 10)

If I pin Decred to the taskbar it shows a weird looking icon.

Compared to the one for the wallet running it is very different.

v1.5 rc1 Release Notes feedback

I submitted smaller fixes in #118. Below are things I couldn't figure out on my own.

dcrwallet v1.5.0-rc1

Arbitrary extended pubkeys can now be imported as a watching-only account,
even on wallets which do store private keys for other accounts.

decred/dcrwallet#1471 had "Addresses of imported xpub accounts are not watched and transactions are not saved.". If this is still the case, "watching-only" will cause confusion. Also, if it is still the case, I suggest adding this limitation to the release notes.

A --disablecointypeupgrades flag and config setting is added to prevent the
wallet from ever upgrading the coin type on a seed restored wallet, even when
there is no observed transactions for the seed.

Add a hint when this can be useful.

Deprecated config flags from the v1.4.0 release have been removed.

Please list them to save reader's time and quickly see if they need to update their config.

* A panic caused by out-of-bounds array access in the SPV syncer was identified
  and corrected.
dfdfdes zero confirmation
  transactions and corrects the `last_block` behavior to match bitcoind.

Buggy text.

decrediton v1.5.0-rc1

It also includes a preliminary Lightning Network implementation by matheusd. Most of the other work was completed by vctt and a new member of the team, bgptr. Many thanks to them for their hard work on this release.

I suggest to move credits to its own section at the end, similar to dcrd's Code Contributors. This is the first time I see credits in the intro.

Update Politeia proposal fetching to reduce amount of data that is consistantly
requested. Previously, every load of decrediton would cause an unnecessary
amount of data to be requested.

This is really a bug fix of an epic bug, should be under Bug fixes.

Update lockedByTickets balance to accomodate dcrwallet balance updates staking.

"balance updates staking" is hard to read, please reword.

General

inconsistent capitalization of Decrediton (vs decrediton) throughout the release notes

manifest-decrediton-v1.3.1.txt was not properly signed

I got the following error message while verifying it:

$ gpg --verify manifest-decrediton-v1.3.1.txt.asc 
gpg: assuming signed data in 'manifest-decrediton-v1.3.1.txt'
gpg: Signature made Mon Oct 15 13:58:50 2018 PDT using RSA key ID 518A031D
gpg: BAD signature from "Decred Release <[email protected]>" [unknown]

For sanity check, I verified the previous version (v1.3.0) immediately and the process worked for this specific version:

$ gpg --verify manifest-decrediton-v1.3.0.txt.asc 
gpg: assuming signed data in 'manifest-decrediton-v1.3.0.txt'
gpg: Signature made Wed Sep 19 13:14:24 2018 PDT using RSA key ID 518A031D
gpg: Good signature from "Decred Release <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: FD13 B683 5E24 8FAF 4BD1  838D 6DF6 34AA 7608 AF04
     Subkey fingerprint: F516 ADB7 A069 852C 7C28  A02D 6D89 7EDF 518A 031D

Steps to reproduce:

Checkout the github repo
Run the aforementioned commands

wallet cannol be opened after upgrade

Hi, I cannot open wallet after upgrade. I have this error.

[img]http://i.imgur.com/jdv1OqE.jpg[/img]

add gencerts to package

When building from source there are additional utilities that get built during the process. It was assumed that these utilities would be included in the packages found in this repo.

Example utilities

-rwxr-xr-x    1 decred   decred    10191247 Aug 23 22:30 addblock
-rwxr-xr-x    1 decred   decred    11210318 Aug 23 22:30 dcrctl
-rwxr-xr-x    1 decred   decred    18829982 Aug 23 22:31 dcrd
-rwxr-xr-x    1 decred   decred     9961906 Aug 23 22:30 findcheckpoint
-rwxr-xr-x    1 decred   decred     4697431 Aug 23 22:30 gencerts
-rwxr-xr-x    1 decred   decred     1979881 Aug 23 22:30 promptsecret

We should ensure that all the utilities are included with the packages hosted here, especially certgen.

Missing file for /rpc.cert

cloudy:decred bilalghalib$ ./dcrctl --wallet getnewaddress
open /........./Library/Application Support/Dcrwallet/rpc.cert: no such file or directory

Installed CMD line tools, connected using the seed text, can't create new wallet...
Ideas?

Help link goes to v1.2.1 "What's new"

When you click on "Help" and then "About" then "What's New" it takes you to https://github.com/decred/decred-binaries/releases/tag/v1.2.1

Add new build of politeiavoter

Some important issues have been fixed with politeiavoter since v1.3. A new binary should be included with the v1.4 release that just got cut.

manifest-decrediton-v1.4.0.txt.asc is borked

It has the same content as manifest-decrediton-v1.4.0.txt

manifests $ pwd
/home/user/bin/decred-binaries/manifests
manifests $ diff -u manifest-decrediton-v1.4.0.txt*
manifests $ echo $?
0

Decredition v1.3.1 (and 1.3.0) blockchain sync on startup stalls / stuck

Upon startup the 1.3.0 version would get stuck at Blockchain Syncing 342913/366181
I upgraded to 1.3.1 and the same result occurred.

v1.5 rc1 tag does not contain v1.5 release notes

The v1.5.0-rc1 tag points to commit e5ddf0b3 which does not have the v1.5 release notes. They are available in master though.

Scrolling not working on Governance Panels

1.4.0-RC1/macOS 10.14.2

Governance Tab
Scrolling through longer governance proposals is broken -does not work with scroll wheel or 'clicking and dragging down'. Additionally no scroll bars are displayed.

Your account has been flagged.

My account has been flagged. Can you change it, please?

Validate Paymetheus v1.0.1

Validate paymetheus on:

Windows 7 x64
Windows 10 x64

Make sure both icons launch paymetheus correctly.

Validate decrediton v1.0.1

Basic testing of the release build needs to be done on supported OSes:

OSX x64
Linux x64

Testing more than one Linux disto is a good idea so please mention distro or version you tested in comments.

Purchaseonly ticket buyer wallet option

Problem:

When doing solo mining, even when using a dual wallet hot/cold with a voting-only wallet, the hot wallet which does the ticket purchase has to remained unlocked and is at risk of moving funds if someone is able to access the system with login privileges.

The same problem would apply for someone doing mining with a pool and wants to use the automated ticket buyer. The remaining balance in the wallet remains at risk even if the majority of the funds are held in tickets, or when proceeds for voting are returned to the wallet and the ticket price is too high, the funds would sit in the wallet for a period of time being at risk of being transferred out.

Solution:

dcrwallet should have an option to start the process in "ticket-purchase-only" mode where even if the wallet is unlocked it can only be used to buy tickets or receive funds but funds cannot be transferred out without unlocking again in "full" mode or restarting the process.

Workaround:

The only current safe option is to have the ticket buying wallet be cold wallet but it cannot automatically purchase tickets in this case and requires a manual process every few days to unlock the wallet for purchasing tickets.

Cannot verify file for v1.5.1

I tried to verify the setup file for Mac OS but got the following error:

gpg --verify decrediton-v1.5.1-manifest.txt.asc decrediton-v1.5.1.dmg
gpg: Signature made Thu Jan 30 07:38:58 2020 JST
gpg:                using RSA key F516ADB7A069852C7C28A02D6D897EDF518A031D
gpg: BAD signature from "Decred Release <[email protected]>" [unknown]