[ANN] RHINOHORNS [CPU/GPU HYBRID] SAVE THE RHINO! LAUNCHED!

[rhinotakeover]

"No block source available..."

Have you put the nodes into a rhinohorn.conf file?

addnode=132.199.72.221:6999
addnode=67.11.25.199:6999

[djm34]

not working better than before... (Got one confirmation in my 1 roh tranfer... I will be dead before it got confirmed...)

no blocksource available, right after I added the two new nodes too...

[enerbyte]

"No block source available..."

Have you put the nodes into a rhinohorn.conf file?

addnode=132.199.72.221:6999
addnode=67.11.25.199:6999

Yes, I did!

[peterlustig]

Indeed stuck at 14877

Connected to these two nodes:
67.11.25.199:6999
90.57.167.142:6999

[monoxide]

now it started syncin for me. i don't know if it helped but i had windows updates pending for restart and after i did wallet synced..

[enerbyte]

this is rather strange, I remember when vertcoin implements KGW, there was no incompatibility issues with wallet.dat file, in the case of Rhinohorns is quite confusing, this is due to? (sorry for the english)

[rhinotakeover]

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;

addnode=54.186.150.238

[djm34]

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;

addnode=54.186.150.238

Yes installing windows 95 is the solution  
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...)

[enerbyte]

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;

addnode=54.186.150.238

thanks dev, everything right!  

[rhinotakeover]

thanks dev, everything right!  

Fantastic

[peterlustig]

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?

[djm34]

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;

addnode=54.186.150.238

thanks dev, everything right!  

well not here, transfering 1roh was ok... more seems to not show up.
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.  

[kraftcheesy]

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;

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?

[monoxide]

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;

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.

[rhinotakeover]

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.

[djm34]

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 !!!
(I guess I am out of that coin, I guess in takeover, that include other people coins)

[Malayko]

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 ...

[eddo51]

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 !!!
(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.

[djm34]

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 !!!
(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.

ninja forking, with untested new wallet is something new. Nice takeover
(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)

[rhinotakeover]

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.