 Show Posts
|
|
Pages: [1] 2 »
|
|
Cryptsy has always been quick to respond to support questions. I think the biggest risk is having the site get hacked and losing your deposit- I think the real question is which site has the best security.
|
|
|
|
|
You can undervolt the AMD 8350 quite a bit- mines @ 1.32v 4.4ghz, board says 111w. I'd test it against the plug but don't have a meter.
|
|
|
|
|
Like I said my only risk is electricity- you could cloud mine for a month, get nothing and be out of a good hunk of change. Gotten two blocks so far- odds seem okay to me.
|
|
|
|
|
Pool will just make it easier for cloud mining- my only costs risk is electricity.
|
|
|
|
Delete everything in the roaming/memorycoin folder except for memorcoin.conf (delete wallet.dat too!!) Set gen=0 in memorycoin.conf Start memorycoin When it is synced turn on mining That's what worked for me on windows. YMMV. how are y people mining this  . - 1 - it take age to sync , i am using all node i was able to find (and from fresh node topic)
2 -client often crash during sync
3- client often crash during mining
|
|
|
|
|
Was able to get it going on windows by deleting everything + wallet.dat and having mining turned off in memorycoin.config (when starting it). Fortunately there was nothing in it! Its mining on the right block now.
|
|
|
|
Mine is overclocked to 4.4ghz just drop the voltage to 1.30 and you won't make much extra heat. Isn't that CPU 5GHz? I've mined a lot of coins this is one of the worst launch i've seen... and I tried hard !
Just leave this here... I do not wish to create a whole topic regarding this comment
I must admit, I had my doubts about freetrade and his way of ensuring he makes money. But, I like some of his ideas, and even though it's struggling, I think this coin does have potential. Freetrade should of maybe tested it more, but I still think it has potential. The same way I think FT has potential. Anyway, I've given up mining this, I started at the beginning, that's why I was punished with a <5MMC block, and no other after all this time. I'm using a 8-core 8350 @ 4.2ghz And FT, in all honesty, I wish him the best of luck - and I hope I can come back and mine this coin someday. K. No, it's definitely 4ghz - I have one... (mine is OC 5%) K. |
|
|
|
Disabled watch on my linux machine... we will see- |
|
|
|
Same here- deleted the old block chain and takes forever to load the block and crashes... exact same operation on the linux box and it was up and running in a few minutes. Well, I've been running the Windows client for about 5 days and have encountered some bugs. They are all the same for all 3 released binary versions and didn't improve in any way. Just want to summarize the issues for the Windows build:
1. Sync problem
After starting the client it can't sync ("No block source available"). Reproduced behind NAT. Sometimes you simply have to wait 10-30 min. and it syncs. Sometimes it doesn't. Adding lots of nodes from this thread to the memorycoin.conf file seems to fix this issue.
Also sometimes the client appears to be synced but the block count is less than real block count. Improves after some time or after restart.
2. Program crash
Usually happens when you turn mining on and off several times or change thread count. For example: Mine 4 Processes -> Mine 2 Processes -> Switch Mining Off -> Mine 4 Processes -> crash. I noticed that you have to wait for some time for mining to actually stop before enabling it again but it doesn't prevent crashes. Sometimes the crash is followed by database corruption.
3. Database corruption
Happens after number 3. After starting the client it shows a dialog like "Do you want to rebuild index?" Then it reindexes the database.
4. Mining stops
After mining for some time it stops. Enabling mining with any number of threads doesn't work even if the blockchain is in sync and with correct block count. Restarting client fixes this.
5. The application doesn't close
Usually happens after number 4. After closing the client window memorycoin-qt.exe can still be seen in the process list.
|
|
|
|
Nodes worked for me- however I have noticed that adding the nodes in the console almost never works (win 7). Picked them up right away when I added to memorycoin.conf. None of the IPs on original post work,
try 68.232.188.226 and 198.12.127.2 (darkhosis.nogleg.com and nogleg.net)
oh, there are many ppl stuck at 554 blocks for some reason. they usually end up trying to submit some blocks to me and my client bans them?
Here are my dedi's running the latest MMC build (Should be online until Jan.) addnode 69.197.166.50:1968 add addnode 198.204.255.50:1968 add addnode 69.197.181.18:1968 add addnode 173.208.132.122:1968 add addnode 69.197.144.42:1968 add addnode 173.208.132.114:1968 add addnode 69.197.144.146:1968 add addnode 69.30.198.114:1968 add Feel free to add them to your linux conf as well: addnode=69.197.166.50:1968 addnode=198.204.255.50:1968 addnode=69.197.181.18:1968 addnode=173.208.132.122:1968 addnode=69.197.144.42:1968 addnode=173.208.132.114:1968 addnode=69.197.144.146:1968 addnode=69.30.198.114:1968
Anyone know the H/m for amazon cloud mining?
"hashespermin" : 10.21357159,
aws c3.8xlarge Is that $2.4 per hour? That translates to 722.4 hours in a month. (24 hours * 4.3 weeks * 7 days) 722.4*2.4 = $1,733.76 The 16 CPU would be $866.88 @ $1.2/hour Yeeeesh. |
|
|
|
|
Stuck on 610 on linux with latest build:
{
"version" : 85400,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 280.00080000,
"blocks" : 610,
"timeoffset" : 1,
"connections" : 8,
"proxy" : "",
"difficulty" : 0.00001890,
"testnet" : false,
"keypoololdest" : 1387122711,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}
{
"blocks" : 610,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00001890,
"errors" : "",
"genproclimit" : -1,
"hashespermin" : 3.24141026,
"pooledtx" : 0,
"testnet" : false
}
From top:
8656 nomullet 20 0 28.2g 1.1g 4860 S 797.3 14.1 525:43.86 bitcoind
|
|
|
|
Thought I would come home from work to find my linux box crashed again- was still running and I scored a block!  VIRT was up to 3g in top. nomullet@debian:~$ apt-cache policy openssl openssl: Installed: 1.0.1e-2 Candidate: 1.0.1e-2 Version table: *** 1.0.1e-2 0 500 http://ftp.us.debian.org/debian/ wheezy/main amd64 Packages 100 /var/lib/dpkg/status nomullet@debian:~$ |
|
|
|
|
Just for fun tried a 2 cpu droplet and was getting .2hpm- and 3.4 on my 8350. Waste of time if you ask me.. personally I like that the coin doesn't cloud mine well.
|
|
|
|
|
Non- aes i7 950 win 7
{
"blocks" : 72,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00000128,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespermin" : 0.96817527,
"pooledtx" : 0,
"testnet" : false
}
AMD 8350 debian wheezy
{
"blocks" : 74,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00000089,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespermin" : 3.43980344,
"pooledtx" : 0,
"testnet" : false
}
|
|
|
|
That did it... sorry for the dumb questions. |
|
|
|
Any hints on getting this running on linux? I ran make and got bitcoind running, but it doesn't seem to be doing much.
try this: watch './bitcoind getinfo && ./bitcoind getmininginfo' Thanks for the help.... getting sh: 1: ./bitcoind: not found good news is the cpus are swamped now- must be doing something. You have to run it from the folder where bitcoind is in, so do a "cd" to that folder before. I had to do a bunch of goofy stuff to get it running- it didn't seem to want to use the conf file default path so I got it running with this: ./bitcoind -datadir=/home/nomullet/memorycoin -conf=/home/nomullet/memorycoin/memorycoin.conf If I run ./bitcoind -datadir=/home/nomullet/memorycoin -conf=/home/nomullet/memorycoin/memorycoin.conf getinfo It says "can't connect to server" running watch './bitcoind getinfo && ./bitcoind getmininginfo' from src folder (same issue I was having finding conf file) Every 2.0s: ./bitcoind getinfo && ./bitcoind getmin... Sun Dec 15 10:05:17 2013 error: You must set rpcpassword=<password> in the configuration file: /home/nomullet/.memorycoin/memorycoin.conf If the file does not exist, create it with owner-readable-only file permissions. Well, as the error message says, "You must set rpcpassword=<password> in the configuration file". Have you done this? Yes, I have. I am wondering if there is some kind of issue with my rpc settings... anyone have an example for linux? |
|
|
|
Any hints on getting this running on linux? I ran make and got bitcoind running, but it doesn't seem to be doing much.
try this: watch './bitcoind getinfo && ./bitcoind getmininginfo' Thanks for the help.... getting sh: 1: ./bitcoind: not found good news is the cpus are swamped now- must be doing something. You have to run it from the folder where bitcoind is in, so do a "cd" to that folder before. I had to do a bunch of goofy stuff to get it running- it didn't seem to want to use the conf file default path so I got it running with this: ./bitcoind -datadir=/home/nomullet/memorycoin -conf=/home/nomullet/memorycoin/memorycoin.conf If I run ./bitcoind -datadir=/home/nomullet/memorycoin -conf=/home/nomullet/memorycoin/memorycoin.conf getinfo It says "can't connect to server" running watch './bitcoind getinfo && ./bitcoind getmininginfo' from src folder (same issue I was having finding conf file) Every 2.0s: ./bitcoind getinfo && ./bitcoind getmin... Sun Dec 15 10:05:17 2013 error: You must set rpcpassword=<password> in the configuration file: /home/nomullet/.memorycoin/memorycoin.conf If the file does not exist, create it with owner-readable-only file permissions. |
|
|
|
Any hints on getting this running on linux? I ran make and got bitcoind running, but it doesn't seem to be doing much.
try this: watch './bitcoind getinfo && ./bitcoind getmininginfo' Thanks for the help.... getting sh: 1: ./bitcoind: not found good news is the cpus are swamped now- must be doing something. |
|
|
|
|
Any hints on getting this running on linux? I ran make and got bitcoind running, but it doesn't seem to be doing much.
|
|
|
|
|
