Show Posts
|
Pages: [1]
|
Oh, yes. Of course. It slipped my mind that all mined coins are sent to separate addresses in the wallet.dat So getting the privatekey for the main wallet address won't actually move the coins. Ha, my bad. If you can reply to my private message we can try and fix your problem.
|
|
|
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" 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.
|
|
|
thanks dev, everything right! ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) Fantastic ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
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
|
|
|
"No block source available..." ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) Have you put the nodes into a rhinohorn.conf file? addnode=132.199.72.221:6999 addnode=67.11.25.199:6999
|
|
|
Important postHere are some nodes. addnode=132.199.72.221:6999 addnode=67.11.25.199:6999 addnode=54.186.150.238 Here is a new wallet [WINDOWS] And for those wanting a git Hope everything works for you! Once everything is fixed up we will make the new ANN. EDIT: In response to those wanting to know some more information about us. There are currently 3 in our team with a few more close to the project. We all have different levels of experience, enough to save a near death coin? Let's see. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Hope everyone has got their wallets working.
Anyone that is still having problems should send us a PM. We will try to help you.
|
|
|
Edit: this seems to work just fine as it is, but if i try copy/paste my old wallet.dat (where all my coins are) it says wallet.dat corrupt, salvage stopped. I try to send some of my coins in old client to new address in new client and see if it works..
Have you got this working? ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) All our private testing has allowed us to use our old wallet.dat files. You might want to try exporting the .dat from inside the old rhino wallet, rather than copy and pasting it from the application files. As many of you have suggested, we will be creating a new ANN but only once we have ironed out all the bugs and it has a new name etc. Patience ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
We apologise for the problems you are having. Please try this (it has worked in all our testing); [WINDOWS] http://www.sendspace.com/file/3dnxoqAlso, we will take suggestions for a name change and put that into place at a later date. Our main priorities were to make the coin functional again. We will make a new ANN when this has been accepted by the community as the current fork and once we have changed the name etc.
|
|
|
So this will be on Crypto Altex, or is that a no?
I think the problem with getting it listed was KGW and the absent dev. Hopefully now that it has been solved we can be listed. I suggest you mine before it starts to get too hard.
|
|
|
It isn't a good idea... we won't reach block 24000 before 3 or 4 months, single computer can't get a coin within a sensible time, there is no pool. the coin will be dead before it reach block 24k. (understand that we want to dump the cpu mine coin, before the gpu arrive... but three month it is still very long)
Once KGW kicks in soon then it will be no problem for CPUs to mine this coin.
|
|
|
The source is on the Dropbox link.
|
|
|
Here is the new code, a compiled qt wallet for windows and source for Linux etc; https://www.dropbox.com/sh/zw8t7sgfe1yp3v1/pSxecwP50H We have fixed the KGW exploit and it will start 200 blocks from now (block 14750). That should solve the extremely slow re targeting we're getting at the moment. It is still only CPU mineable in line with the original plan. We felt it was a unique element to the coin and also didn't want to change it too much from the original developers plan. If the original dev decides that he wants to retake control that is perfectly fine by us, just let us know if you plan on doing so ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Please all update your wallets to continue on with this fork. I think we can all agree that it is not going anywhere fast in its current state.
|
|
|
Hey guys!
We are going to take over this coin by the end of the day if there are no objections. A coin that is listed on an exchange needs some sort of active development.
We have been looking through the past posts on this thread and have seen a few good ideas such as starting a charitable fund and possibly changing the name. If we successfully take over ownership then we will make sure to put these questions to the public through polls etc.
There are a few of us and are willing to put some coins in the kitty for bounties etc. More will be revealed later, including how you can help if you wish.
The first things we will do is patch up the KGW code to fix the exploit and sort out this terribly slow retargeting.
|
|
|
|