 Show Posts
|
|
Pages: [1] 2 3 4 5 6 7 »
|
|
I ordered 6 Sapphire 280x from GPU Shack and they showed up quick. They get things out and handle things quite well, money well spent. Will be buying more too.
|
|
|
|
|
Where do I buy these FPGA's? Ready to order a few!
|
|
|
|
Just wanted to say "thanks" for all the info. Picked up used s1's and they are now voltmodded  |
|
|
|
Any reason not to just re-import priv keys instead of going back to old wallet.dat?
Yes. Most users don't know what commands to run in order to get "all" the wallet addresses. Your wallet has more addresses than shown in the "receive" tab. Those are new addresses created for "change", which means the remaining of the coins from a transaction you created. So, if you don't dump and import private keys of all the addresses, you may end up with missing coins. I had previously made a new wallet and send coins out of my old wallet because it was hard to tell what was missing in every resync. So it's just a short list on my new wallet, easy to import Which worked great. But then I tried to send a few over to bittrex:  Any ideas? Same thing happened to me when I decided to give up on maintaining a local wallet + stake and tried to move everything to Bittrex. I kind of followed what mindfox recommended while back: 1. Run checkwallet in the debug window. Given that the message is about coin mismatch, you are likely to get back a message that some amount of coins is out of sync. 2. Run repairwallet in the same window. 3. Retry transaction. It is possible that the amount you originally tried to transfer might not be available, but it should become available after waiting a little bit. If the original amount was less than 1/2 of the value of your wallet, it is likely that on the next try you will succeed (i.e. will use coins from other inputs in your wallet). If you don't have enough funds, just wait for the coins from the original transaction to be "returned" to your wallet. 4. In case 3 fails again, repeat starting from 1. You will eventually succeed. By free estimate, I had to do this 8-10 times until I moved the whole content of my wallet. You also might need to close and reopen the wallet as well for the missing amount to appear. As always, back up your wallet before attempting anything. Good luck! Yeah I was only trying to send less than 3% of my coins lol. Thanks for the info, glad I'm not only one with these problems! Any word on when the next wallet update will be out? I know Mindfox was working on it yesterday and I believe it's about ready. He is actually driving home now and then we'll be catching up. Standby for an update on version 1.7.0.3. Cool, I'll just close wallet and wait for update then. I have so many copies of wallet.dat files from bad re-sync's i'm losing track  |
|
|
|
Any reason not to just re-import priv keys instead of going back to old wallet.dat?
Yes. Most users don't know what commands to run in order to get "all" the wallet addresses. Your wallet has more addresses than shown in the "receive" tab. Those are new addresses created for "change", which means the remaining of the coins from a transaction you created. So, if you don't dump and import private keys of all the addresses, you may end up with missing coins. I had previously made a new wallet and send coins out of my old wallet because it was hard to tell what was missing in every resync. So it's just a short list on my new wallet, easy to import Which worked great. But then I tried to send a few over to bittrex: Any ideas? Same thing happened to me when I decided to give up on maintaining a local wallet + stake and tried to move everything to Bittrex. I kind of followed what mindfox recommended while back: 1. Run checkwallet in the debug window. Given that the message is about coin mismatch, you are likely to get back a message that some amount of coins is out of sync. 2. Run repairwallet in the same window. 3. Retry transaction. It is possible that the amount you originally tried to transfer might not be available, but it should become available after waiting a little bit. If the original amount was less than 1/2 of the value of your wallet, it is likely that on the next try you will succeed (i.e. will use coins from other inputs in your wallet). If you don't have enough funds, just wait for the coins from the original transaction to be "returned" to your wallet. 4. In case 3 fails again, repeat starting from 1. You will eventually succeed. By free estimate, I had to do this 8-10 times until I moved the whole content of my wallet. You also might need to close and reopen the wallet as well for the missing amount to appear. As always, back up your wallet before attempting anything. Good luck! Yeah I was only trying to send less than 3% of my coins lol. Thanks for the info, glad I'm not only one with these problems! Any word on when the next wallet update will be out? |
|
|
|
Any reason not to just re-import priv keys instead of going back to old wallet.dat?
Yes. Most users don't know what commands to run in order to get "all" the wallet addresses. Your wallet has more addresses than shown in the "receive" tab. Those are new addresses created for "change", which means the remaining of the coins from a transaction you created. So, if you don't dump and import private keys of all the addresses, you may end up with missing coins. I had previously made a new wallet and send coins out of my old wallet because it was hard to tell what was missing in every resync. So it's just a short list on my new wallet, easy to import Which worked great. But then I tried to send a few over to bittrex: Any ideas? |
|
|
|
|
Any reason not to just re-import priv keys instead of going back to old wallet.dat?
|
|
|
|
Any updates on these checkpoint errors? Sync'd 5 times, erroring...
Brian, I thought I explained in the irc channel. The error you see is normal and it's good that you see it (it means that everything works as it should). Your wallet has PoS blocks in it that are invalid. So, it broadcasts those invalid PoS blocks to the net and the net reacts to it and treats it like a threat. What you need to do is backup your wallet.dat file and remove everything (including the wallet.dat file). After your wallet syncs completely, close your wallet application, replace the backed up wallet.dat file and re-open your wallet app. Then just do the "checkwallet" and "repairwallet" if you see that you have coins missing. I did that -- the 5 times.... It syncs up, and then has the checkpoint error back after a few hours. |
|
|
|
|
Any updates on these checkpoint errors? Sync'd 5 times, erroring...
|
|
|
|
|
Checkpoint error is back on my wallet... and it sync'd with all my coins missing again. (Tried twice this morning so far...)
|
|
|
|
|
Trying to start up wallet in testnet to test my pool configuration before turning it live and I get:
Axisd: main.cpp:2573: bool LoadBlockIndex(bool): Assertion `block.GetHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)' failed.
Any ideas?
|
|
|
|
Is the wallet linked to in the op not working? I ask as I just downloaded it and it just crashes upon startup with the following error "This application has requested the Runtime to terminate it in an unusal way."
Should I just wait for the new wallet release? Don't really need to move any coins around but would be cool if they were staking.
I'm running the windows build posted on rejectmining.com -- been good for me and I know of several others using it too. |
|
|
|
Where can i get the diamond kernel miner? sph-sgminer doesn't seem to have it and groestl doesn't seem to work :/
Try updating your sph-sgminer. I had a slightly out of date version but was still mining DMD on it. https://bitcointalk.org/index.php?topic=475795I downloaded that again, but it doesn't have the "diamond" kernel in it When it solves a block, I'm finding this in my wallet debug.log 05/30/14 21:16:15 ThreadRPCServer method=submitblock
05/30/14 21:16:15 pindexBest = 411073pindexBest = 411073ERROR: CheckBlock() : hashMerkleRoot mismatch
05/30/14 21:16:15 ERROR: ProcessBlock() : CheckBlock FAILED
When you run sph-sgminer you need to specify the kernel as "groestlcoin". That should work unless something has changed with the coin since I last mined it a couple weeks back. Waiting for wallet to sync up now so I can confirm it for you... EDIT: Still works. Just picked off another solo block  Yes I can solo that way, but pool mining doesn't seem to work at all. In previous posts, there are reports of a "diamond" kernel fixing things. I believe this is the source, just need a windows binary :/ https://github.com/danbi/sph-sgminer |
|
|
|
Where can i get the diamond kernel miner? sph-sgminer doesn't seem to have it and groestl doesn't seem to work :/
Try updating your sph-sgminer. I had a slightly out of date version but was still mining DMD on it. https://bitcointalk.org/index.php?topic=475795I downloaded that again, but it doesn't have the "diamond" kernel in it When it solves a block, I'm finding this in my wallet debug.log 05/30/14 21:16:15 ThreadRPCServer method=submitblock
05/30/14 21:16:15 pindexBest = 411073pindexBest = 411073ERROR: CheckBlock() : hashMerkleRoot mismatch
05/30/14 21:16:15 ERROR: ProcessBlock() : CheckBlock FAILED
|
|
|
|
|
Where can i get the diamond kernel miner? sph-sgminer doesn't seem to have it and groestl doesn't seem to work :/
|
|
|
|
I've been trying to setup a Curecoin pool using NOMP but haven't had any luck yet, is there something out of the ordinary with block submissions? I keep seeing messages like this when submitting a block:
We thought a block was found but it was rejected by the daemon, share data: {"job":"10a2","ip":"127.0.0.1","worker":"bsom.1","height":2903,"reward":13000000,"difficulty":106.83760684,"shareDiff":"78839945.97002709","blockDiff":3675593.04712938,"blockDiffActual":3675593.04712938,"blockHash":"000000000000003679e92759a80c36f6f40d2a370bf9f03ce0567b707358369b"}
Using the latest wallet with the following coin config:
{
"name": "Curecoin",
"symbol": "CURE",
"algorithm": "sha256"
}
I have the same issues as well. I am very interested in the answer. Same issue here, too |
|
|
|
|
RejectMining.com will be in on this. But for now, I have to go finish reading your amazing web site. Love it!
|
|
|
|
So... Any idea how big of a TX works? |
|
|
|
|
