Bitcoin Forum

Dear coin devs:
please always mention VERSION and DATE of your wallet

Maintaining many wallets can be made much easier for us ... please, devs.

At the moment it's always the same riddles:
Which version am I running? Which one is the newest available? When was it published? Am I still fine, or is the update mandatory? How can I find out without actually starting the wallet client? ...

Please help us:

OP of your ANN thread, right beside the wallet downloads:
mention the newest version number
AND release date
AND the reason for this update (e.g. heartbleed bug)

Your website
mention the newest version number AND release date AND the reason for this update

In the filename
include the version number into the download-filename, e.g.  MyUniqueCoin-v0.8.6.2.zip

(Windows/Mac) In the file properties of the .exe
e.g. file properties for the "v0.9.4.4-unk-beta" version: https://i.imgur.com/Xn0zedw.png

In the archive which I unpack,
provide a readme-v0.8.6.2.txt or  history-v0.8.6.2.txt  or version-v0.8.6.2.txt or MyUniqueCoin-v0.8.6.2.txt


Then two quick visits,
into the install folder, and onto the ANN thread
will tell me:   It's time to act!

A big plus is also to link to a www.virustotal.com result for each binary, and give sha1 / sha256 codes



Actually, I just had an idea, a useful tiny program - anyone wants to program that?  A small download which iterates through all the (usually used) wallet folders, and (1) compiles a list of version numbers of installed wallets; and then (2) compares to a list which is kept updated on a server; where (3) admins register if they have released a new version.  And you can build it step by step: (1) would already be useful, (2) would be great, and (3) really cool :-)  And all that could become the starting point for a fancy (4) wallet software distribution system (e.g. s.th. like http://portableapps.com/download ). And (5) a wallet.dat backup suite.




EDIT:  use the ALERT SERVICE when hardforking ! ! ! ! !
--> https://bitcointalk.org/index.php?topic=566164.msg6822654#msg6822654

It's in the wallet under debug so if any of the devs knew what they were doing it would be available in all coins consoles. Generator crap coins and bad devs have no idea

I know, but that is a far way. Some coin wallets need ages to start.

Much easier if I can see the version number in the folder - and on the ANN thread, most importantly.

.

Bumping this one because I just had a hard time finding a Litecoin wallet from an official source which says the heartbleed bug is fixed [1]

Litecoin.org: no info
Litecoin.info/Wiki: no info
Github: nothing checked-in / mentioned

I'm sorry to say this, but from a version management/communicating this to the enduser point of view you dev guys suck.

Why is it SOOO hart to change the download link to "Litecoin-Qt-0.8.6.2-SSL-fixed" on the official download page?

[1]: of course I could build linking it against my own fixed version of openssl, but that's not the point.

yes, exactly.  But I'd rather say "... SOME OF you dev guys suck."  :-)


I actually see this problem improving in the past weeks - perhaps even since my posting?

(and always post some working nodes in your OP… or take care node-infos are always up to date…)

good point. Most of my recent wallets didn't need any .conf file anymore, so I guess it works by hardcoded addresses? So make sure the wallets on those addresses are running.

!

If you plan an obligatory hardfork for your coin, please

use the ALERT SERVICE  -  https://en.bitcoin.it/wiki/Alerts (https://en.bitcoin.it/wiki/Alerts)

to inform old wallet users to upgrade immediately.


Don't loose the coins of your users by unprofessional hardforks.

in case of hardfork, you (as the upgrade demanding dev) should also ask the major exchanges
to mention one sentence on their deposit pages (https://www.mintpal.com/deposit/DRK) to warn not to use older wallets: