what about other exchanges?
i do not want to register to an other one.
Bittrex is a great exchange, I use this for over a year now. Never complaints. Suggest you have a look. I also use Cryptsy for other coins but everything is more slow (trading) and deposid/withdrawal takes a lot of time. ok, mhh. i use poloniex and yobit. i will have a look at bitter then. If you want Gulden on other exchanges then as a user of those exchanges you should request it from them, it is ultimately the exchanges and the users of those exchanges that decide which coins to add, it is not something that the Gulden devs can control (well not without bribery and that isn't going to happen) |
|
|
|
Just in case it might be useful for anyone in future, I found and modified a basic python script that can search for private keys in an (unencrypted) wallet.dat and print them out in a way that you can import into the wallet. Tested it with a few valid wallet.dat files and it worked. As a last resort (if you have a lot of time) you could probably run this using a linux bootdisk against the entire partition. (expect some false positives - not everything it spits out is going to be a valid address) Unfortunately after this point it becomes a trade off of cost to pursue further etc.  http://www.pxdojo.net/2013/12/bitcoin-private-key-necromancy.html is also a worthwhile read - this is where I got the script from. #!/usr/bin/python
import binascii
import os
import hashlib
import sys
# bytes to read at a time from file (10meg)
readlength=1*1024
if len(sys.argv)!=2:
print "./keyhunter.py <filename>"
exit()
filename = sys.argv[1]
f = open(filename)
magic = '\x01\x01\x04\x20'
magiclen = len(magic)
##### start code from pywallet.py #############
__b58chars = '123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz'
__b58base = len(__b58chars)
def b58encode(v):
""" encode v, which is a string of bytes, to base58.
"""
long_value = 0L
for (i, c) in enumerate(v[::-1]):
long_value += (256**i) * ord(c)
result = ''
while long_value >= __b58base:
div, mod = divmod(long_value, __b58base)
result = __b58chars[mod] + result
long_value = div
result = __b58chars[long_value] + result
# Bitcoin does a little leading-zero-compression:
# leading 0-bytes in the input become leading-1s
nPad = 0
for c in v:
if c == '\0': nPad += 1
else: break
return (__b58chars[0]*nPad) + result
def Hash(data):
return hashlib.sha256(hashlib.sha256(data).digest()).digest()
def EncodeBase58Check(secret):
hash = Hash(secret)
return b58encode(secret + hash[0:4])
########## end code from pywallet.py ############
# read through target file
# one block at a time
while True:
data = f.read(readlength)
if not data:
break
# look in this block for keys
x=0
while True:
# find the magic number
pos=data.find(magic,x)
#pos=data.find('\13\02\01\01\04\20',0)
if pos==-1:
break
print EncodeBase58Check('\xA6'+data[pos+magiclen:pos+magiclen+32])
x+=(pos+1)
# are we at the end of the file?
if len(data) < readlength:
break
# make sure we didn't miss any keys at the end of the block
f.seek(f.tell()-(32+magiclen))
# code grabbed from pywallet.py
|
|
|
|
Possibly try to run your command prompt as administrator and turn off your virus scanner. Ensure you have the 64 bit version of the program installed if it is a 64 bit windows.
I'm not sure what else to suggest, but the program is at this point not even reaching the part where it tries to recover the wallet.dat (it is failing just to make a copy of the wallet.dat with a different name) and this indicates something external is wrong e.g. unable to even access the file for some reason. (The read only attribute being the most obvious thing here - you are 100% sure the read only attribute is not set?)
If you send me the full debug.log in private perhaps I can pick up some other clues from it.
Yes i am pretty sure it aint that. Running cmd in admin modes. I just recovered more then just wallet.dat (It contains 2.12 GB) and going to try it again. I will let you know. Okay, the next step then is probably to try and get the private keys directly with a hex editor - there are a few scripts around for this. Can you pm me or add me on skype? aron@shopem.nlBest would be if you can come on slack, if not PM, I won't be able to skype until later. |
|
|
|
Possibly try to run your command prompt as administrator and turn off your virus scanner. Ensure you have the 64 bit version of the program installed if it is a 64 bit windows.
I'm not sure what else to suggest, but the program is at this point not even reaching the part where it tries to recover the wallet.dat (it is failing just to make a copy of the wallet.dat with a different name) and this indicates something external is wrong e.g. unable to even access the file for some reason. (The read only attribute being the most obvious thing here - you are 100% sure the read only attribute is not set?)
If you send me the full debug.log in private perhaps I can pick up some other clues from it.
Yes i am pretty sure it aint that. Running cmd in admin modes. I just recovered more then just wallet.dat (It contains 2.12 GB) and going to try it again. I will let you know. Okay, the next step then is probably to try and get the private keys directly with a hex editor - there are a few scripts around for this. |
|
|
|
Does the file wallet.1446113146.bak exist afterwards? There is something very strange going on that a basic file rename is failing...
No Possibly try to run your command prompt as administrator and turn off your virus scanner. Ensure you have the 64 bit version of the program installed if it is a 64 bit windows. I'm not sure what else to suggest, but the program is at this point not even reaching the part where it tries to recover the wallet.dat (it is failing just to make a copy of the wallet.dat with a different name) and this indicates something external is wrong e.g. unable to even access the file for some reason. (The read only attribute being the most obvious thing here - you are 100% sure the read only attribute is not set?) If you send me the full debug.log in private perhaps I can pick up some other clues from it. |
|
|
|
Please try the following:
1) Create a new folder C:\Recover
2) Place just a single wallet.dat in the folder
3) Ensure both the folder and wallet.dat are readable and writeable
4) Run Gulden.exe -datadir=C:\Recover -salvagewallet -debug from the prompt
5) If it fails send me the debug.log
PyWallet gives me the following error Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again Same problem; 2015-10-29 10:05:46 Gulden version v1.5.2.0-f0e8ba6 (2015-10-10 12:42:24 -0400) 2015-10-29 10:05:46 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015 2015-10-29 10:05:46 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-10-29 10:05:46 Default data directory C:\Users\AKKIE\AppData\Roaming\Gulden 2015-10-29 10:05:46 Using data directory N:\Gulden 2015-10-29 10:05:46 Using config file N:\Gulden\Gulden.conf 2015-10-29 10:05:46 Using at most 125 connections (2048 file descriptors available) 2015-10-29 10:05:46 Using 8 threads for script verification 2015-10-29 10:05:46 Using wallet wallet.dat 2015-10-29 10:05:46 init message: Verifying wallet... 2015-10-29 10:05:46 CDBEnv::Open: LogDir=N:\Gulden\database ErrorFile=N:\Gulden\db.log 2015-10-29 10:05:46 Failed to rename wallet.dat to wallet.1446113146.bak 2015-10-29 10:05:46 GUI: initializeResult : Initialization result: 0 2015-10-29 10:05:46 GUI: requestShutdown : Requesting shutdown 2015-10-29 10:05:46 GUI: shutdown : Running Shutdown in thread 2015-10-29 10:05:46 Shutdown: In progress... 2015-10-29 10:05:46 StopNode() 2015-10-29 10:05:46 Shutdown: done 2015-10-29 10:05:46 GUI: shutdown : Shutdown finished 2015-10-29 10:05:46 GUI: shutdownResult : Shutdown result: 1 2015-10-29 10:05:46 GUI: ~BitcoinApplication : Stopping thread 2015-10-29 10:05:46 GUI: ~BitcoinApplication : Stopped thread Note : The wallet.dat files i recovered are much different then the one from the new wallet. I can recover all data from the new wallet.dat i created. It seems like the wallet.dat files are not right. The recovered files are build somewhere in 2014. Can it have something to do with the fact there are build in old outdated guldencoin wallets? Does the file wallet.1446113146.bak exist afterwards? There is something very strange going on that a basic file rename is failing... |
|
|
|
@Shopem, i googled a bit and saw that possibly you can retrieve the private key with a hex-program. I have no experience with that. Once you have the private key you can import that in a new wallet. I think it is wise to wait for the experts to assist on this.
Did you have only 1 backup file?
I recovered multiple wallet.dat and other files Are the files maybe marked as read only? Right click them, go into properties and ensure they are writeable. Note: this alone might be enough to make the 'corruption' disappear so try this first without the salvage wallet option even. (That bitcoin-qt reports read only wallet files as corrupted is horrific and something that we must fix - I am going to open a bug on our github for this immediately) I wish this was the problem... Unfortunly not! Please try the following: 1) Create a new folder C:\Recover 2) Place just a single wallet.dat in the folder 3) Ensure both the folder and wallet.dat are readable and writeable 4) Run Gulden.exe -datadir=C:\Recover -salvagewallet -debug from the prompt 5) If it fails send me the debug.log |
|
|
|
It is possible as a last resort. I think it is better to first try and use salvagewallet, from what I can see currently the salvage is not failing but rather it is failing to rename the file (which it does before the salvage even begins) so as a first step it would be best to figure out why this is. |
|
|
|
@Shopem, i googled a bit and saw that possibly you can retrieve the private key with a hex-program. I have no experience with that. Once you have the private key you can import that in a new wallet. I think it is wise to wait for the experts to assist on this.
Did you have only 1 backup file?
I recovered multiple wallet.dat and other files Are the files maybe marked as read only? Right click them and ensure they are writeable. Note: this alone might be enough to make the 'corruption' disappear so try this first without the salvage wallet option even. (That bitcoin-qt reports read only wallet files as corrupted is horrific and something that we must fix - I am going to open a bug on our github for this immediately) Let this also be a reminder to everyone, please make regular backups of your wallet.dat Also please report wallet bugs on our github if you find them, the more bug reports the more fixes the better the wallet  |
|
|
|
@Shopem, i googled a bit and saw that possibly you can retrieve the private key with a hex-program. I have no experience with that. Once you have the private key you can import that in a new wallet. I think it is wise to wait for the experts to assist on this.
Did you have only 1 backup file?
I recovered multiple wallet.dat and other files Are the files maybe marked as read only? Right click them, go into properties and ensure they are writeable. Note: this alone might be enough to make the 'corruption' disappear so try this first without the salvage wallet option even. (That bitcoin-qt reports read only wallet files as corrupted is horrific and something that we must fix - I am going to open a bug on our github for this immediately) |
|
|
|
Help!
I just recovered my wallet.dat file after a format but when i put it in the right folder and start guldencoin (on windows) it says the wallet.dat file is corrupt. This account holds over 800k NLG so please help!
1) Make sure you have a safe backup of this file before trying anything further as any further incorrect steps may damage it even more and remove whatever chance of recovery there is. Work only on a copy of the file from now on. 2) Open a command prompt 3) Run command "Gulden.exe -salvagewallet" |
|
|
|
If i remember correctly there is a website for Gulden with all market data stats, Mining stats etc etc but i cannot find it.
Anyone a quick link?
nlgstats.nl |
|
|
|
decisions on pos being made
No final decisions have been made in terms of changing algorithms. With all the other big changes that have occurred, new difficulty algorithm, reward change, litecoin halving etc. it is best not to rush into a bad choice here. We are carefully watching and monitoring things to see how it develops from here, once things settle a bit or it becomes apparent that something like POS remains necessary the discussion will be brought up again. |
|
|
|
Just a quick reminder that 1.5.2 is out, 1.5.0 users should try upgrade when possible Also a reminder to everyone to make regular backups of their wallets. |
|
|
|
I hope this whole unpleasantness can now remain in the past and the dev team can now focus on what we do best, developing. Despite what has been claimed we remain open to positive contributions from all no matter how small they may be. If anyone in the community has projects they want to work on or propose I (and I'm sure the others) remain more than willing to discuss them. In the interests of moving forward now and trying to gain back the positive momentum we need I invite all users to have their say on what they like/hate about the wallets and what they would like to see in them in the future over here: https://community.gulden.com/t/features-you-would-like-to-see-in-the-wallet-s/1323 |
|
|
|
When I make a mistake I usually say sorry and try to correct whatever I have done wrong. In this case the respons was slightly different (STFU and accept our way bitches) resulting in this ongoing discussion. DeVries didn't close his .zone forum because he wants to let down this community, he did so because he realized he could never do any good with it because he got backstabbed by Rijk time and time again. I want to build (or a facilitate it it least) a new forum, but not if it gets ignored and bypassed by the devteam the same way the .zone forum has.
Anyone can setup a forum around Gulden, should they wish so. Yet it cannot be expected from the devteam, to have them involved in every fora regarding Gulden with "official" questions. Those kinda questions, which would require a devteam involvement or direct answer, could be asked here, or on the official forum. Should those kind of questions be asked NOT here or NOT on the official forum, those questions should be re-directed towards; it is kinda illogical, to expect other way around...  Very true, however I would like to say that when community members pointed out questions on zone to me (or asked for assistance answering questions on zone) I did in fact help where possible, but yes I certainly can't spend all my time being active on every single different outlet, and as the community grows there will be more and more channels, slack, reddit, facebook, google+, more forums, it certainly isn't reasonable to expect the devs to actively pour energy into every single forum that pops up. These allegations that the dev team had some sort of a problem with zone or sabotaged it or whatever else certain people are trying to make it sound like are completely unfounded and have no basis in reality. |
|
|
|
Because it's not us, the community members who get to decide what forum is going to be used, that is being dictated by the ones in control of the media, being the Dev's.
Nonsense, users can post wherever they want, therefore it is impossible to dictate what forum users choose to use. They refuse to cooperate in building a community forum the community (by large majority) asks for.
If the community - Which part by the way? You keep talking as if the community is one mass but in reality any community consists of multiple different groups of people who all want, feel and think different things. You seem to for some reason think that you speak for everyone and I don't understand where you get that idea from, you speak for (from what I can tell) a very small group of people, or do you get input from every last community member before you make statements? It certainly doesn't seem that way... - wants a forum then there is absolutely nothing stopping them from building one, the devs have certainly put up no roadblocks in that respect. The gulden.zone forum was mentioned on all official pages (even our Github) alongside the existing forums, I even answered questions there on occasion when it was requested of me. What more support could you possibly want, do you mean we must actually do all the work for you? What is stopping you from advertising your own forum - there are many places including here where you could do such a thing, we have no monopoly on this either. In fact if there were an overwhelming demand for this forum it would have been built already, it is *not* hard to launch a new forum, it can be done with very little skill with less than a few hours work, the fact that it has not been done shows that: 1) There is not as much demand for it as is being claimed 2) The people who are pissing and crying about it are more interested in making a big fuss (political agenda) about the dev team and using this situation to try stir things up then they are in actually having a forum. - And this is the part that really grinds me, what utter short sightedness to constantly drag the coins name into the dirt through public crying like this over something as petty and silly as a forum, when you are free to make your own. It is really really sad that a very small group of people are still crying about a forum change months later and taking every opportunity to bring it up over and over again, causing damage to the very coin they claim to support, instead of just getting over it like grown adults and moving on whether that be by making their own forum or finding something else to do with their time. They singlesidedly changed "our" forum overnight into something very technical, without any consultation whatsoever.
A vast majority complained about that and kept asking to go back to the old one.
Actually at the time a vote was taken and the vast majority of the vote was in favour of keeping the new forums, after this vote some who *still* disagreed made a new forum, which the dev team had no problem with, after all we already have two BTC, community, a third is no problem. Please stop trying to revise history. |
|
|
|
LTEX, Biomike and some others. If you think it through it is kinda retarted that the dev-team didn't gave any trust in these people. Is it because they are loaded with Gulden? Or any other reason.
https://github.com/Gulden/gulden-dev/pull/48https://github.com/Gulden/gulden-dev/pull/49https://github.com/Gulden/gulden-dev/pull/46https://github.com/Gulden/gulden-dev/pull/45The dev team has and will continue to accept all valid positive contributions from anyone regardless of their affiliations, motives or how many coins they hold. This does not mean that we always have to agree with everyone, it is impossible to please 100% of the people 100% of the time, and if there is a small group that feels slighted that a few decisions didn't please them there is nothing we can do about that, we continue to serve the *majority* of users not a small group of people *regardless of how many coins this small group may hold* "To avoid criticism say nothing, do nothing, be nothing." |
|
|
|
Hello.
On the same subject, I have Guldencoin Core wallet version 1.5.0. It seems to be doing fine but I'm wondering if I should go to a newer version.
Thanks in advance.
1.5.0 users should ideally update, nothing bad will happen if you don't but we would appreciate it if you do |
|
|
|
|
Show Posts
