That would be really great.
LW6Bqqk74D4t7WHTD2URAAFdRmYKYYk2mF
Thank you very much Matt
|
|
|
eWPt99NZT5mNR5QSiGj8sz48r35KWfS2pv
aw, too late :-(
|
|
|
is someone elses windows wallet not synchronizing? for good measure 7RPcjBoGKcYs2rTR7DA2EpVvzMUNfYr9iP Mine is working fine. Here's my conf: rpcuser=dimecoinrpc rpcpassword=2596a6a36d42416b5486386c rpcallowip=127.0.0.1 rpcport=11930 port=11931 daemon=1 server=1 gen=0 addnode=108.53.178.39 addnode=115.28.16.229 addnode=109.65.166.87 addnode=99.99.203.102 addnode=86.184.213.156 addnode=115.28.16.229 addnode=115.28.11.226 addnode=37.146.68.215 addnode=23.88.164.18 addnode=24.131.171.33 addnode=77.47.170.101
|
|
|
74aiNcN18Lmg2ACVuzhkd39n96L7CTa9vx
thanks. And once you have created a petition at the the other Exchanges, please let us know. We will "like" it like we did on Cryptsy :-)
|
|
|
Hi there,
I would like to test if my QT v1.4 actually works. Could someone send me a few RVD to RN9pjTPc6GcBduyWrdUTVYUxvCMit3vuD7
Thank you very much Matt
|
|
|
LziV9CKA2gTDgo4qU4qepLKyAWfd8UqYmV
thanks
P.S. I posted this address on the facebook page, liked your facebook page and also shared it
|
|
|
MNEJJ8a7vEDyMwr9yVcgVPLjacJgM7aMC9
thanks
|
|
|
thanks, this time it worked. :-)
|
|
|
74aiNcN18Lmg2ACVuzhkd39n96L7CTa9vx
thanks
|
|
|
OK, but how can we make that happen? What would be the first step? :-)
|
|
|
74aiNcN18Lmg2ACVuzhkd39n96L7CTa9vx
thanks
|
|
|
eWPt99NZT5mNR5QSiGj8sz48r35KWfS2pv
thanks
|
|
|
EWXT5Tds3zWcmETwgNketJuMBpzc36QvYH
thanks
|
|
|
Hi there,
I would like to ask how version management of Altcoin wallets is currently being handled?
In the last 4 weeks (aka the time I have spent with Altcoins) I have noticed 3 major challenges:
1. New Wallet versions being introduced without everyone upgrading 2. New Wallet versions are sometimes incompatible to the old wallets => people lose their coins 3. Every new altcoin requires its own wallet software (=> issues (1) and (2) get even worse with every wallet installed)
Re 1) Not everyone is as active as you guys. Not everyone knows when his QT wallet must be upgraded. I would like to propose that all QT wallets have an "autoupdate" feature which checks at least once a day if a new version is released. Pretty much like an iPad/iPhone-App or an Adobe/Microsoft/Apple/PrettyMuchEveryOtherSoftwareVendor-application. They all check for updates all the time. Some even allow automatic updates so the user is never bothered with such admin tasks. I think, every wallet should have that feature and it should be activated by default. Advanced user can - of course - switch it off (e.g. by a command like "autoupdate false" or so).
Re 2) Take a look at QBT (or others): when v3 was released, the blockchain of v2 was abandoned. As I said before: not everyone is as active as you. I am sure that there are people out there that invested hard cash into buying v2 QBT, did not realize that they must switch over to v3 within days, and now lost all their money because their v2 coins are useless. Not really sure how to handle this. One way could be a mandatory escrow service accessing the frozen old blockchain to payout to new versions. But I am not sure how that could be enfored in reality.
Re 3) I think one way to solve this is by building a plugin-mechanism with version control for Meta-Wallets. What do I mean by this? Well, instead of installing a completely new wallet software for each altcoin, there should only be 1 single Meta-Wallet that can handle all altcoins (even those that have just been released seconds ago). In my opinion, the best way to deal with this is by means of a plugin-system. So the standard source-code does not only generate the QT and the XXXd file but also the XXXd-plugin (implementing the entire QT minus the GUI, but plus the plugin-interface). This plugin should result in 1 file that is published in the Meta-Wallet-repository. Seconds after this has been done, all Meta-Wallets around the globe can download and install the plugin and handle the new currency. Since that plugin is essentially a QT without a GUI, it can implment all features of the native QT and consequently be part of the network of the respective currency. The same way, if a new version has to be introduced, the Meta-Wallet-Repo makes sure that it updates automatically. All the devs have to do is to make sure they update the Metawallet-repo whenever they release something new. I am sure they will do that in their own interest because after all, they want everyone to update.
Any thoughs from you? Do you think that makes sense / is needed / is doable?
Thanks Matt
|
|
|
Just a little confused here. I have QT v1.0.0.0-unk-boss Does that still work or do I have to upgrade?
Just to test: could someone send me some BSS/BOS to bD5SfBJvvu3aK97SzFYYMX4Y2eEXcysUKE ?
Thanks
|
|
|
Turns out I used my v2 address in the old thread. My v2 wallet never synchronized so the 50 QBT you sent never showed up. I am not too happy with the fact that wallets can actually expire and be rendered useless if the devs decide to issue a new, incompatible software version.
Anyways, I just created a v3 address and the wallet is currently syncing. Hopefully, that will work...
CVVUsZaNLPgTWooSgm1N6GmLg7G6FzkS9E
Thanks Matt
|
|
|
Turns out I used my v2 address in the thread above. My v2 wallet never synchronized so the 50 QBT you sent never showed up. I am not too happy with the fact that wallets can actually expire and be rendered useless if the devs decide to issue a new, incompatible software version.
Anyways, I just created a v3 address and the wallet is currently syncing. Hopefully, that will work...
CVVUsZaNLPgTWooSgm1N6GmLg7G6FzkS9E
Thanks Matt
|
|
|
LziV9CKA2gTDgo4qU4qepLKyAWfd8UqYmV
thanks
|
|
|
LziV9CKA2gTDgo4qU4qepLKyAWfd8UqYmV
thanks
|
|
|
LziV9CKA2gTDgo4qU4qepLKyAWfd8UqYmV
thanks
P.S. I posted this address on the facebook page, liked your facebook page and also shared it
|
|
|
|