If you would like to try my build of xptminer used for ypool, the code is compiling for linux or windows here: https://github.com/clintar/xptMiner
x86_64 binary here: https://dl.dropboxusercontent.com/u/105316582/xptclintar.zip


If you compile it for linux, you can try to get a speed increase using llvm/clang by running
instead of just make

Notes about speed:
I'm getting mixed feedback about speed. Some the windows binary is faster than jh00's linked at ypool's howto page, a few said it was slower. On my machine, the windows build runs faster in wine than compiling it native, but my coworker's machine runs much faster native, and even faster after compiling with llvm/clang. Almost double from wine or even running the windows version in native windows (he dual boots).

So try multiple ways if you can and please let me know if it runs better for you or not, either way, and what cpu type, distro, and compiler version if you compile it.

Disclosure:
It's got a 1% fee by default, which you can set the amount with -d.

waht device you're using!?

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.

Hey guys,

What is going on with Bter? Is it normal that they are updating servers this long. I have some coins there so I am worried.

Hmm...I have Intel i7-3820 @ 3.6 GHZ
24GB RAM

{
"blocks" : 565,
"currentblocksize" : 1193,
"currentblocktx" : 1,
"difficulty" : 0.00003196,
"errors" : "",
"genproclimit" : 8,
"hashespermin" : 2.09299892,
"pooledtx" : 1,
"testnet" : false
}

Does this seem right?  Compared to the laptop?  Anything I can do to bump up the h/min?  I tried to setgenerate true 32 but all that does is heat up my CPU, no hash speed increase.  I can overclock, does that help?

Cheers!

Possible botnet controller?
I would like to know how someone could get 300 mcc when most people are getting 1-1.5 rewards.
Unless we've ramped up to 280 rewards now. In which case, we seriously need a pool.

WTB 20 MMC.  Post your offer!

WTB 5 MMC for 0.15BTC (@0.03BTC/MEM)