|
I was very excited and eager to get into cloud mining, but after reading this thread I'm full of dread.
Is there a cloud mining service you'd recommend that can accept credit cards?
Hashnest looks profitable but only accepts bitcoin which I'm very low on these days.
AMHash is sold out it seems, but they also look good.
Genesis Mining takes cards, but from their fees and pricing looks like it would be a bad deal compared to the rest.
KnC may be a good choice, but not sure if they take cards or not.
Any recommendations?
|
|
|
|
|
On Linux I'm getting:
Can't load blockchain storage from file, generating genesis block.
When starting the daemon, and it never seems to finish or use any resources.
I deleted everything but my wallet and keys from the folder I keep the daemon and wallet in, nothing in .bitmonero
|
|
|
|
|
What miner do you use for Windows 64bit, E3-1240v3 (AES support etc)
What about an older Nehalem based processor?
|
|
|
|
|
Is there a calculator for XMG to see about how many coins will be mined per day given a processor or hash rate?
|
|
|
|
|
How do you compile the wallet from source on Linux command line?
I'm unable to get this to compile from github.
|
|
|
|
Thanks, what about Staking? Do I need to run just one wallet? Or is it beneficial to run a wallet on each desktop? Can they all use the same address, or do they all need to be unique? |
|
|
|
|
Now that PoS-II is active, and I'm still a bit confused with PoM, what is the best mining method for Windows desktop computers?
I have some that are X3470 and some that are E3-1240v3 that support newer AES stuff.
I have a few idle, should I be running the wallet on each one of them + a optimized CPU miner to a pool, or just mine from the wallet to a pool etc?
Doubt I would stand a chance solo mining at all.
|
|
|
|
Out of no where my wallet.bin stopped working with this error:
Error: failed to load wallet: failed to read file "wallet.bin"
I have all the files including the keys file, how can I rebuild my wallet.bin without losing my balance?
Backup all the files first, then move everything except the keys file to a different directory. Restart the wallet with just the keys file and it will rescan the blockchain and create a new bin file (which will take some time) Thanks, I believe this worked and I kept my original address. That was simple. |
|
|
|
|
Out of no where my wallet.bin stopped working with this error:
Error: failed to load wallet: failed to read file "wallet.bin"
I have all the files including the keys file, how can I rebuild my wallet.bin without losing my balance?
|
|
|
|
|
I'm looking at investing a few thousand into Scrypt ASICS.
I noticed most of the sites selling them are saying they are sold out, but have a lot of new pre-orders which have very nice profitability.
I assume by the time it is shipped however, this profitability will be much lower.
What ASICs that are currently available do you recommend? Or should I wait a month or two for the next generation to come out?
|
|
|
|
|
I've been away since around 2 weeks after launch.
Do I need to update my wallet, and if I stake on more than 1 computer with the same wallet, is there any benefit?
|
|
|
|
|
I downloaded the latest blockchain and daemon/wallet, but when I start it, it crashes saying it can't load the blockchain from storage file, generating genesis block, then crashes.
I downloaded the blockchain again, same issue.
I deleted the blockchain file and its running and synchronizing, but at the current rate will take days, it's stuck on block 801 for half an hour now, but is still using a lot of network.
Modern PC with 8GB of RAM and 16GB virtual ram, 3770 processor, 64bit Windows 7.
|
|
|
|
That is very strange. It seems you may have created a new wallet instead of restoring the old one.
Hopefully you have safe backup copies of your wallet.bin.keys file that are separate from whatever you are using to try to restore. When working with wallet files always make sure you have good backups stored somewhere else so you can't mess them up.
That being the case, move all of the new wallet files somewhere else, make a new copy of your safely-stored wallet.bin.keys making sure there are no other wallet files there at all. Load into simplewallet.
If you don't get the same address at that point, you have gotten your wallet.bin.keys files mixed up.
I backed up the right roaming folder, but wrong wallet.bin perhaps. I have the correct viewkey though, is there a way to recover with that and the original address? If not, at least I emptied it out a month ago, so not too much pain. |
|
|
|
|
I upgraded to a new machine and copied over my wallet.bin wallet.bin.keys and then started the new version I just downloaded today, but my address has changed in simplewallet.
I made sure to load the proper old wallet.bin file.
Is there something else special I can do?
Any way to get my old address back? I have the viewkey as well.
|
|
|
|
This one? https://github.com/tpruvot/ccminerIs there a pre-compiled one for Linux? Or how to fix this as my device can't run CUDA 6+ nvcc -gencode=arch=compute_50,code=\"sm_50,compute_50\" -I . -I/usr/local/cuda/include -I./compat/jansson --maxrregcount=128 -o cuda_fugue256.o -c cuda_fugue256.cu nvcc fatal : Unsupported gpu architecture 'compute_50' make[2]: *** [cuda_fugue256.o] Error 255 make[2]: *** Waiting for unfinished jobs.... Version D7b should work I just see Windows binaries in that download, and no source to compile for Linux. Thanks for the help! |
|
|
|
|
Other than Tsiv's Nvidia Monero miner, are there any others for the Nvidia crowd?
|
|
|
|
|
Thanks! Keep me in the loop, or is there a master thread somewhere?
|
|
|
|
|
Anything new going on with this? Love the concept.
|
|
|
|
Is there a way to set something on the remote miners running this to report back to the master miner that oversees them all?
Finding exactly what IP each one actually finds to can be troublesome, but I'm being picky/lazy.
I could, and I was thinking about something like this, but I too was lazy when trying to roll out the miner  . The question I have for the group is what style of auto discovery would we want? i.e. do most people run their miners on networks that have multicast enabled across all the switches and hubs etc? or would we just want to instead of listing all the nodes on the masters start-up command, just list the master node on every other nodes start-up command? Perhaps a config file or command line argument on each remote node that would cause it to connect to a certain master node. Same way it currently works where the master lists each remote node, but reversed  each remote node lists the master it connects to. |
|
|
|
|
Is there a way to set something on the remote miners running this to report back to the master miner that oversees them all?
Finding exactly what IP each one actually finds to can be troublesome, but I'm being picky/lazy.
|
|
|
|
|
Show Posts
