Topic: [ANN] MemoryCoin - page 37. (Read 100338 times)
Seems like I've processed all the blocks but still getting 0 hashespersec on my linux VM.
anyone get multi-threading in linux to work? I can compile/run, but then cannot connect to the server via the daemon command. Very odd
ok it seems like deleting my .memorycoin folder fixed this. However, only 1 CPU core is being used ?
Are you using the multithread branch from github?
Yes - this coin keeps barfing on me. Just got a seg-fault when running it with multi-thread. Can't connect to server... blah blah blah. More work is needed here
i use
memorycoinQTMT.zip
windows xp 32bit
can sync
when i type setgenerate true
the hashespersec is always =0
is it right?
memorycoinQTMT.zip
windows xp 32bit
can sync
when i type setgenerate true
the hashespersec is always =0
is it right?
I'm using the multithread branch (downloaded the zip from github), it takes a long time to sync or rather verify (15mins), using 1 core at 100%, and during that time commands might return "can't connect to server". gen=0 in the conf.
When it's done (current block count is 476), cpu is idle, can start mining (i'm using 7 threads out of 8 cores I've got), it's been 1h and didn't find a block.
1 block is found like every 10 or 15 minutes by the network (I haven't timed it, I could be off).
When it's done (current block count is 476), cpu is idle, can start mining (i'm using 7 threads out of 8 cores I've got), it's been 1h and didn't find a block.
1 block is found like every 10 or 15 minutes by the network (I haven't timed it, I could be off).
anyone get multi-threading in linux to work? I can compile/run, but then cannot connect to the server via the daemon command. Very odd
ok it seems like deleting my .memorycoin folder fixed this. However, only 1 CPU core is being used ?
Are you using the multithread branch from github?
anyone get multi-threading in linux to work? I can compile/run, but then cannot connect to the server via the daemon command. Very odd
ok it seems like deleting my .memorycoin folder fixed this. However, only 1 CPU core is being used ?
anyone get multi-threading in linux to work? I can compile/run, but then cannot connect to the server via the daemon command. Very odd
I have a following problem: it dowloads all the data, starts mining and mines for few blocks then it stops downloading new blocks. It looks like it loses connection, but there is always 4 connections in the debug window. When restarted everything is OK, but looks I can't live it overnight.
why the hashespersec = 0?
Here is a small patch for this.
Immediately after line 4873 of main.cpp, add this line:
nHashesDone++;
Re-run the make file and you should now have a non-zero hashespersec.
What's you hashespersec, what cpu, how many blocks did you find?
This coin is really hard to mine. It takes literally hours to load the bitcoind and download the blockchain..
I think he made the hashing algorithm so hard that even verifying work takes forever....
This coin is really hard to mine. It takes literally hours to load the bitcoind and download the blockchain..
I think he made the hashing algorithm so hard that even verifying work takes forever....
Quite quick after launching the mining I found a block
Date: 5-8-2013 22:56
But after this one no new blocks were found.
Quite hard to mine, and quite some trouble setting it all up.
Will come back in a day or so and see how it all evolved.
Verifying is slow endeed.
I got sync and verifying faster putting these nodes.
addnode 180.183.205.59 add
addnode 71.187.248.95 add
addnode 97.89.174.206 add
addnode 211.75.183.176 add
addnode 209.190.27.90 add
addnode 46.229.50.42 add
addnode 65.61.116.102 add
addnode 46.98.142.139 add
addnode 142.55.148.72 add
addnode 180.183.156.19 add
Don't know which one works, but I have 5 connections to the network.
I got sync and verifying faster putting these nodes.
addnode 180.183.205.59 add
addnode 71.187.248.95 add
addnode 97.89.174.206 add
addnode 211.75.183.176 add
addnode 209.190.27.90 add
addnode 46.229.50.42 add
addnode 65.61.116.102 add
addnode 46.98.142.139 add
addnode 142.55.148.72 add
addnode 180.183.156.19 add
Don't know which one works, but I have 5 connections to the network.
This coin is really hard to mine. It takes literally hours to load the bitcoind and download the blockchain..
I think he made the hashing algorithm so hard that even verifying work takes forever....
This coin is really hard to mine. It takes literally hours to load the bitcoind and download the blockchain..
rl3 Looks better. I have mined about 10 blocks 
Is it typical for "bitcoind" to take 100% cpu of a single core while downloading the blockchain?
This is on linux btw... whats the current block count?
This is on linux btw... whats the current block count?
having it start mining (by default) before loading the wallet is a bad idea, not only if you just want to send funds and the time it takes to startup but any blocks found will be orphaned when the client finally syncs (happened to me)
so what do you suggest on doing?
i never started it with the bat
so what do you suggest on doing?
You could try starting up by clicking directly on the .exe file rather than the start.bat file.
Once it's synchronized, on the debug window, type
setgenerate true
why the hashespersec = 0?
Here is a small patch for this.
Immediately after line 4873 of main.cpp, add this line:
nHashesDone++;
Re-run the make file and you should now have a non-zero hashespersec.
Jump to: