Topic: [ANN] MemoryCoin | CPU Coin | Paid Dev Team | Limited Supply [MMC] - page 70. (Read 281389 times)
December 17, 2013, 09:39:07 PM
never mind, just re-download from the .org one, it has 8.5.3 verison.
December 17, 2013, 09:37:07 PM
hi guys,
where can i get the windows build for verson 8.5.3? the file on memorycoin.info and on google drive at page still 8.5.2
Thanks
where can i get the windows build for verson 8.5.3? the file on memorycoin.info and on google drive at page still 8.5.2
Thanks
December 17, 2013, 09:31:47 PM
Still mining since the start, now with 2.3 HPM on i7 2600 ....... still no block.
Just about download and update the client hope it brings some luck!!!
check out the source code changes on github (as you should always do to prevent yourself from downloading a bicoind wallet stealer ^^), it only adds changes to block >750 difficulty and disallows inefficient thread numbers. wont make you fastere or luckier. Just about download and update the client hope it brings some luck!!!
December 17, 2013, 09:21:34 PM
Still mining since the start, now with 2.3 HPM on i7 2600 ....... still no block.
Just about download and update the client hope it brings some luck!!!
Just about download and update the client hope it brings some luck!!!
December 17, 2013, 09:12:34 PM
I'm not sure I agree with you yet.
Albeit, writing yourself "payments" into the code for 6 officers, with two people filling two positions (twice the payments) is pretty sketchy.
Giving the right to vote on "job positions" to only a select few who already hold memorycoins from the previous coin is also sketchy. How can we be sure the devs didn't buy up all the old coins with the intention of holding the majority vote on the new coin? Why even hold a vote?
Writing a premine to "benefit previous memorycoin and protoshares holders" without outlining exactly how many coins would go to those people. We know the amount 1:10 memory coins. Does that mean there is 7,800,000 memory coins from 1.0? (nope, max 1 mill). So why the 780,000 MMC2 premine?
Let's say there was 500,000 memorycoins from 1.0
Shouldn't the premine be only 50,000 then?
What happens to all the MMC2 coins that aren't redeemed from MMC1 coins?
These questions need to be addressed going forward.
Of course we know that only two people had MMC1 coins.
Problem solved...
or they could have bought them on exchanges without anyone knowing who bought what.
Obviously that is just speculation, but I am just pointing out we don't know what happened.
December 17, 2013, 09:08:05 PM
i just followed the cloud mining guide last night to start mine memory coin, so what do i need to do to get the update? has the source been released that we just do a new download and recompile?
December 17, 2013, 08:55:24 PM
Let me get this straight...to activate the new fork mining all I need to do is just reinstall everything like I did in the beginning because the new files are posted at the same address?
December 17, 2013, 08:47:39 PM
that's unnecessary. I've found that the problem is exacerbated by the number of threads being used; perhaps he's only using 2 or 4 cores and therefore hasn't hit a hard limit yet?
I ended up just writing a script to restart the daemon if (when) cpu drops below a certain threshold, indicating the process has crashed... hacky, but good enough for now.
I ended up just writing a script to restart the daemon if (when) cpu drops below a certain threshold, indicating the process has crashed... hacky, but good enough for now.
radiumsoup, can you share that script? appriciate
December 17, 2013, 08:44:04 PM
Delete the "rpcthreads" setting and use only the "genproclimit". It's the onlyone solution for now
try both last night, still got crash
, now will try only genproclimit. Any other suggestions?
I still to look the source code, but I've not find nothing yet.
Without rpcthreads my server was still up for three days without problems. Try and give a me a feedback. Now it's my time to sleep :-)
Good luck
FaSan
BULL. Post a pic of htop and i will believe you.
I ended up just writing a script to restart the daemon if (when) cpu drops below a certain threshold, indicating the process has crashed... hacky, but good enough for now.
December 17, 2013, 08:18:37 PM
Delete the "rpcthreads" setting and use only the "genproclimit". It's the onlyone solution for now
try both last night, still got crash
, now will try only genproclimit. Any other suggestions?
I still to look the source code, but I've not find nothing yet.
Without rpcthreads my server was still up for three days without problems. Try and give a me a feedback. Now it's my time to sleep :-)
Good luck
FaSan
BULL. Post a pic of htop and i will believe you.
December 17, 2013, 08:18:07 PM
Delete the "rpcthreads" setting and use only the "genproclimit". It's the onlyone solution for now
This does not fix the problem. stop telling people this fixes the problem. you are filling this thread with FUD!
December 17, 2013, 08:17:24 PM
Delete the "rpcthreads" setting and use only the "genproclimit". It's the onlyone solution for now
try both last night, still got crash
, now will try only genproclimit. Any other suggestions?
I still to look the source code, but I've not find nothing yet.
Without rpcthreads my server was still up for three days without problems. Try and give a me a feedback. Now it's my time to sleep :-)
Good luck
FaSan
December 17, 2013, 08:13:10 PM
Delete the "rpcthreads" setting and use only the "genproclimit". It's the onlyone solution for now
try both last night, still got crash
, now will try only genproclimit. Any other suggestions?
December 17, 2013, 08:11:43 PM
Delete the "rpcthreads" setting and use only the "genproclimit". It's the onlyone solution for now
December 17, 2013, 08:00:27 PM
Thought I would come home from work to find my linux box crashed again- was still running and I scored a block!
http://theanalogoustruth.files.wordpress.com/2011/10/gollum_20100219_aatheory1.jpg
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:~$
http://theanalogoustruth.files.wordpress.com/2011/10/gollum_20100219_aatheory1.jpg
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:~$
December 17, 2013, 07:30:13 PM
maybe off-topic but relevant. FaSan after looking at your constant help to other users I think you could be a good candidate to apply for the CSO position of memorycoin https://bitcointalksearch.org/topic/the-memorycoin-blockchain-is-hiring-369487.
Thank you for suggest. Here my introduction :
https://bitsharestalk.org/index.php?topic=1460.0
FaSan
December 17, 2013, 07:14:53 PM
Now its on block 530. Can we mine but the difficulty will just be worse? Because i have a feeling that this will take a few hours to reach 750 or am i wrong?...
December 17, 2013, 07:05:20 PM
Sounds like a case of gambler's fallacy - if you don't win for a while you think the next time your odds will be higher when, in fact, they are exactly the same.
December 17, 2013, 06:57:51 PM
i don't want to stop now for updating the client.. i mine since 22 hours without any block, i am sure i find a block soon and if i start from new then i have to mine another 3 months 
Thats not how probability works.
yea but thats how my mind works
December 17, 2013, 06:55:35 PM
i don't want to stop now for updating the client.. i mine since 22 hours without any block, i am sure i find a block soon and if i start from new then i have to mine another 3 months
Thats not how probability works.
Jump to: