I had that salvage error too, but just fixed everything by sending my coins in to new wallet/address.
quess i was lucky that my coins were saved.
And calling dev team as scammer is straigth up bullshit.
They use their time and skills to keep this coin alive. no one should call em that, especially when most of us (including myself) didn't know nothing but that there was something that needed to do for this coin to save it and we didn't know how.
So to the dev team: i apologize on behalf of my fellow forum member for all those accusations.
Hope you still want to carry on with this coin.
Thanks.
Topic: [ANN] RHINOHORNS [CPU/GPU HYBRID] SAVE THE RHINO! LAUNCHED! - page 4. (Read 28930 times)
Sending your coins from the old wallet to the new one will not work as the blockchain has forked, due to the takeover.
All your coins will be safe in the old wallet.dat file which should work perfectly with the new wallet qt.
Anyone still having problems should send us a PM. We will help you fix your problems.
oh... thank you for telling this now !!!All your coins will be safe in the old wallet.dat file which should work perfectly with the new wallet qt.
Anyone still having problems should send us a PM. We will help you fix your problems.
(I guess I am out of that coin, I guess in takeover, that include other people coins)
Yep, about the same for me. Old wallet.dat doesn't work with the newest fixed qt-wallet (Still this corrupt error, old qt-wallet however working with the "corrupt" wallet.dat).
As I would understand it the forking would mean that if we get the old wallet.dat's to work in the new wallet then we should be able to recover the coins that were sent (with the old qt-wallet) after the forked block.
(was able to transfer 1 roh, but "strangely" the other 15k got lost in the fork).
rhinotakeover expert dev (who post as newbie as usual...) for me expert scammer (wow, I am the one saying it
)edit: apparently using a old back up of the wallet seems to have restored its content. (however I still get corrupt wallet, if i try to use the
new one)
You guys crack me up.... You wanted it fixed so these guys went in and turned on KGW sooner... Patched KGW for the timewarp bug.. and you still bitch and moan.
Hate to tell u but you saying shit is crashing etc is not helping anybody to include yourself. Post some screen shots of the errors, This was a hard fork all that had to be done is replace old qt file with the new one and it woulda been fine.
I posted the exact comment with the error (wont post an image, but I can describe it to you:
a window pop up with the message "wallet.dat corrupt salvage failed" then close
Ha, you make me laugh. Expert scammer? We haven't taken any coins. Once you get the old wallet.dat to work in the new QT all your coins will still be there, because of the forked blockchain.
A new idea has just popped into my head.
With the old wallet-qt go into
Help > Debug Window > Console
and type "dumpprivkey WALLETADDRESS"
with WALLETADDRESS being your rhino address
Now, copy that key.
If you have a passphrase on the wallet you must type this first;
"walletpassphrase PASSPHRASE 600"
Then, load up the new wallet qt, go to the console and type
"importprivkey PRIVATEKEY"
This should work perfectly fine.
did that, nothing happen (the command was aknowledge) but nothing happenedA new idea has just popped into my head.
With the old wallet-qt go into
Help > Debug Window > Console
and type "dumpprivkey WALLETADDRESS"
with WALLETADDRESS being your rhino address
Now, copy that key.
If you have a passphrase on the wallet you must type this first;
"walletpassphrase PASSPHRASE 600"
Then, load up the new wallet qt, go to the console and type
"importprivkey PRIVATEKEY"
This should work perfectly fine.
Ok now just close your wallet
To be safe this time around delete everything in your %appdata%/rhinohorn folder EXCEPT wallet.dat and your rhinohorn.conf file
and start the wallet back up with the -rescan / -salvagewallet
did that, nothing happen (the command was aknowledge) but nothing happened
The command was acknowledged, where? You did all the steps?
Ha, you make me laugh. Expert scammer? We haven't taken any coins. Once you get the old wallet.dat to work in the new QT all your coins will still be there, because of the forked blockchain.
A new idea has just popped into my head.
With the old wallet-qt go into
Help > Debug Window > Console
and type "dumpprivkey WALLETADDRESS"
with WALLETADDRESS being your rhino address
Now, copy that key.
If you have a passphrase on the wallet you must type this first;
"walletpassphrase PASSPHRASE 600"
Then, load up the new wallet qt, go to the console and type
"importprivkey PRIVATEKEY"
This should work perfectly fine.
did that, nothing happen (the command was aknowledge) but nothing happened A new idea has just popped into my head.
With the old wallet-qt go into
Help > Debug Window > Console
and type "dumpprivkey WALLETADDRESS"
with WALLETADDRESS being your rhino address
Now, copy that key.
If you have a passphrase on the wallet you must type this first;
"walletpassphrase PASSPHRASE 600"
Then, load up the new wallet qt, go to the console and type
"importprivkey PRIVATEKEY"
This should work perfectly fine.
Sending your coins from the old wallet to the new one will not work as the blockchain has forked, due to the takeover.
All your coins will be safe in the old wallet.dat file which should work perfectly with the new wallet qt.
Anyone still having problems should send us a PM. We will help you fix your problems.
oh... thank you for telling this now !!!All your coins will be safe in the old wallet.dat file which should work perfectly with the new wallet qt.
Anyone still having problems should send us a PM. We will help you fix your problems.
(I guess I am out of that coin, I guess in takeover, that include other people coins)
Yep, about the same for me. Old wallet.dat doesn't work with the newest fixed qt-wallet (Still this corrupt error, old qt-wallet however working with the "corrupt" wallet.dat).
As I would understand it the forking would mean that if we get the old wallet.dat's to work in the new wallet then we should be able to recover the coins that were sent (with the old qt-wallet) after the forked block.
(was able to transfer 1 roh, but "strangely" the other 15k got lost in the fork).
rhinotakeover expert dev (who post as newbie as usual...) for me expert scammer (wow, I am the one saying it
)edit: apparently using a old back up of the wallet seems to have restored its content. (however I still get corrupt wallet, if i try to use the
new one)
You guys crack me up.... You wanted it fixed so these guys went in and turned on KGW sooner... Patched KGW for the timewarp bug.. and you still bitch and moan.
Hate to tell u but you saying shit is crashing etc is not helping anybody to include yourself. Post some screen shots of the errors, This was a hard fork all that had to be done is replace old qt file with the new one and it woulda been fine.
I have done this across 8 machines just to try and get some indication of any problems and they all work just fine.
Ha, you make me laugh. Expert scammer? We haven't taken any coins. Once you get the old wallet.dat to work in the new QT all your coins will still be there, because of the forked blockchain.
A new idea has just popped into my head.
With the old wallet-qt go into
Help > Debug Window > Console
and type "dumpprivkey WALLETADDRESS"
with WALLETADDRESS being your rhino address
Now, copy that key.
If you have a passphrase on the wallet you must type this first;
"walletpassphrase PASSPHRASE 600"
Then, load up the new wallet qt, go to the console and type
"importprivkey PRIVATEKEY"
with PRIVATKEY being the key you copied.
This should work perfectly fine.
A new idea has just popped into my head.
With the old wallet-qt go into
Help > Debug Window > Console
and type "dumpprivkey WALLETADDRESS"
with WALLETADDRESS being your rhino address
Now, copy that key.
If you have a passphrase on the wallet you must type this first;
"walletpassphrase PASSPHRASE 600"
Then, load up the new wallet qt, go to the console and type
"importprivkey PRIVATEKEY"
with PRIVATKEY being the key you copied.
This should work perfectly fine.
Sending your coins from the old wallet to the new one will not work as the blockchain has forked, due to the takeover.
All your coins will be safe in the old wallet.dat file which should work perfectly with the new wallet qt.
Anyone still having problems should send us a PM. We will help you fix your problems.
oh... thank you for telling this now !!!All your coins will be safe in the old wallet.dat file which should work perfectly with the new wallet qt.
Anyone still having problems should send us a PM. We will help you fix your problems.
(I guess I am out of that coin, I guess in takeover, that include other people coins)
Yep, about the same for me. Old wallet.dat doesn't work with the newest fixed qt-wallet (Still this corrupt error, old qt-wallet however working with the "corrupt" wallet.dat).
As I would understand it the forking would mean that if we get the old wallet.dat's to work in the new wallet then we should be able to recover the coins that were sent (with the old qt-wallet) after the forked block.
(was able to transfer 1 roh, but the other 15k got lost in the fork).
edit: apparently using a old back up of the wallet seems to have restored its content. (however I still get corrupt wallet, if i try to use the
new one)
Sending your coins from the old wallet to the new one will not work as the blockchain has forked, due to the takeover.
All your coins will be safe in the old wallet.dat file which should work perfectly with the new wallet qt.
Anyone still having problems should send us a PM. We will help you fix your problems.
oh... thank you for telling this now !!!All your coins will be safe in the old wallet.dat file which should work perfectly with the new wallet qt.
Anyone still having problems should send us a PM. We will help you fix your problems.
(I guess I am out of that coin, I guess in takeover, that include other people coins)
Yep, about the same for me. Old wallet.dat doesn't work with the newest fixed qt-wallet (Still this corrupt error, old qt-wallet however working with the "corrupt" wallet.dat).
As I would understand it the forking would mean that if we get the old wallet.dat's to work in the new wallet then we should be able to recover the coins that were sent (with the old qt-wallet) after the forked block.
All that should have been done is stop current qt, copy new .exe qt from the download links to where your "old" one is and start it back up.
That is all no moving wallet files (its always safe bet to back it up) no transfering coins no nothing just replace the QT.exe and start and done.
If you attempt to send coins from the "old" wallet to the "new" one the coins will never show up as the 2 wallets are now off on their own "chains".
So for those of u still having issues... I would recommend shutting your wallet down, downloading the "fixed" qt. replace your .exe with the fixed one, and than start it back up with the -rescan and or -salvagewallet ...
That is all no moving wallet files (its always safe bet to back it up) no transfering coins no nothing just replace the QT.exe and start and done.
If you attempt to send coins from the "old" wallet to the "new" one the coins will never show up as the 2 wallets are now off on their own "chains".
So for those of u still having issues... I would recommend shutting your wallet down, downloading the "fixed" qt. replace your .exe with the fixed one, and than start it back up with the -rescan and or -salvagewallet ...
Sending your coins from the old wallet to the new one will not work as the blockchain has forked, due to the takeover.
All your coins will be safe in the old wallet.dat file which should work perfectly with the new wallet qt.
Anyone still having problems should send us a PM. We will help you fix your problems.
oh... thank you for telling this now !!!All your coins will be safe in the old wallet.dat file which should work perfectly with the new wallet qt.
Anyone still having problems should send us a PM. We will help you fix your problems.
(I guess I am out of that coin, I guess in takeover, that include other people coins)
Sending your coins from the old wallet to the new one will not work as the blockchain has forked, due to the takeover.
All your coins will be safe in the old wallet.dat file which should work perfectly with the new wallet qt.
Anyone still having problems should send us a PM. We will help you fix your problems.
All your coins will be safe in the old wallet.dat file which should work perfectly with the new wallet qt.
Anyone still having problems should send us a PM. We will help you fix your problems.
I don't think the wallet problem is due to KGW.
Unfortunately, we are unable to reproduce the problems everyone is having.
I don't really know what else to suggest. Are you moving the wallet.dat from a different operating system?
I would quite happily try your wallet file on my QT and see if it works, then send the coins to another address for you?
Obviously, this is not ideal because you would have to trust me with your wallet file, but the offer is there.
Here is another node;
Unfortunately, we are unable to reproduce the problems everyone is having.
I don't really know what else to suggest. Are you moving the wallet.dat from a different operating system?
I would quite happily try your wallet file on my QT and see if it works, then send the coins to another address for you?
Obviously, this is not ideal because you would have to trust me with your wallet file, but the offer is there.
Here is another node;
Quote
addnode=54.186.150.238
...I just overwrote my old rhinowallet file and now it won't open. Is there a downloadable V0.3 wallet I can actually download for Windows?
I found this from my computer: https://www.dropbox.com/s/r3a37euoto9frkv/Rhinohorn-WindowsWallet.zip
Hope it works.
I tried that old wallet and it got stuck on block 14782 while the nw wallet syncs just fine.
Also here are all the nodes i have in my new rhinohorns.conf:
addnode=199.127.226.163
addnode=220.239.233.14
addnode=132.199.72.221:6999
addnode=67.11.25.199:6999
addnode=67.11.25.199:6999
addnode=90.57.167.142:6999
addnode=54.186.150.238
Also, i noticed that old client roaming dir was named rhinohorn when the new is named rhinohorns
I don't know if it matters or is correct, but everyone who have problems with syncin should try to rename .conf file with or without s as the last letter.
I don't think the wallet problem is due to KGW.
Unfortunately, we are unable to reproduce the problems everyone is having.
I don't really know what else to suggest. Are you moving the wallet.dat from a different operating system?
I would quite happily try your wallet file on my QT and see if it works, then send the coins to another address for you?
Obviously, this is not ideal because you would have to trust me with your wallet file, but the offer is there.
Here is another node;
Unfortunately, we are unable to reproduce the problems everyone is having.
I don't really know what else to suggest. Are you moving the wallet.dat from a different operating system?
I would quite happily try your wallet file on my QT and see if it works, then send the coins to another address for you?
Obviously, this is not ideal because you would have to trust me with your wallet file, but the offer is there.
Here is another node;
Quote
addnode=54.186.150.238
...I just overwrote my old rhinowallet file and now it won't open. Is there a downloadable V0.3 wallet I can actually download for Windows?
I don't think the wallet problem is due to KGW.
Unfortunately, we are unable to reproduce the problems everyone is having.
I don't really know what else to suggest. Are you moving the wallet.dat from a different operating system?
I would quite happily try your wallet file on my QT and see if it works, then send the coins to another address for you?
Obviously, this is not ideal because you would have to trust me with your wallet file, but the offer is there.
Here is another node;
thanks dev, everything right! Unfortunately, we are unable to reproduce the problems everyone is having.
I don't really know what else to suggest. Are you moving the wallet.dat from a different operating system?
I would quite happily try your wallet file on my QT and see if it works, then send the coins to another address for you?
Obviously, this is not ideal because you would have to trust me with your wallet file, but the offer is there.
Here is another node;
Quote
addnode=54.186.150.238
7 confirmations on the old wallet which now is stuck at block 14778 (while the new is at 15142)
not yet arrived on the new wallet.
Yeah synced now, probably the connections were maxed out. Add maxconnections=24 or so to the .conf file of the nodes maybe if you haven't yet?
I don't think the wallet problem is due to KGW.
Unfortunately, we are unable to reproduce the problems everyone is having.
I don't really know what else to suggest. Are you moving the wallet.dat from a different operating system?
I would quite happily try your wallet file on my QT and see if it works, then send the coins to another address for you?
Obviously, this is not ideal because you would have to trust me with your wallet file, but the offer is there.
Here is another node;
thanks dev, everything right! Unfortunately, we are unable to reproduce the problems everyone is having.
I don't really know what else to suggest. Are you moving the wallet.dat from a different operating system?
I would quite happily try your wallet file on my QT and see if it works, then send the coins to another address for you?
Obviously, this is not ideal because you would have to trust me with your wallet file, but the offer is there.
Here is another node;
Quote
addnode=54.186.150.238
I don't think the wallet problem is due to KGW.
Unfortunately, we are unable to reproduce the problems everyone is having.
I don't really know what else to suggest. Are you moving the wallet.dat from a different operating system?
I would quite happily try your wallet file on my QT and see if it works, then send the coins to another address for you?
Obviously, this is not ideal because you would have to trust me with your wallet file, but the offer is there.
Here is another node;
Yes installing windows 95 is the solution Unfortunately, we are unable to reproduce the problems everyone is having.
I don't really know what else to suggest. Are you moving the wallet.dat from a different operating system?
I would quite happily try your wallet file on my QT and see if it works, then send the coins to another address for you?
Obviously, this is not ideal because you would have to trust me with your wallet file, but the offer is there.
Here is another node;
Quote
addnode=54.186.150.238
lol Am I on BCX thread ? Should I post my hash somewhere ?
I was finally able to transfer my 1 roh, it just took 4 to 5 hours... (the rest is transfering...)
still wondering why the block doesn't have the same number in the old and in the new wallet (most likely the problem is there...)
I don't think the wallet problem is due to KGW.
Unfortunately, we are unable to reproduce the problems everyone is having.
I don't really know what else to suggest. Are you moving the wallet.dat from a different operating system?
I would quite happily try your wallet file on my QT and see if it works, then send the coins to another address for you?
Obviously, this is not ideal because you would have to trust me with your wallet file, but the offer is there.
Here is another node;
Unfortunately, we are unable to reproduce the problems everyone is having.
I don't really know what else to suggest. Are you moving the wallet.dat from a different operating system?
I would quite happily try your wallet file on my QT and see if it works, then send the coins to another address for you?
Obviously, this is not ideal because you would have to trust me with your wallet file, but the offer is there.
Here is another node;
Quote
addnode=54.186.150.238
Jump to: