So I had download the update for a fork at 7xx(can't remember what it was) and thought everything was fine. Didn't notice that you had decided to emergency fork it at 607.

Came home yesterday and was excited to have finally found a block. It wasn't real, though.

How was I supposed to know that you would decide to fork it 100 blocks earlier......

I'm really disappointed in this coin. I've been mining since the release and I'm done.

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.

ThreadRPCServer method=getmininginfo
testHash ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff, 0
Start Search
ThreadRPCServer method=getinfo
keypool reserve 3
keypool return 3
ThreadRPCServer method=getmininginfo
ThreadRPCServer method=getinfo
keypool reserve 3
keypool return 3
ThreadRPCServer method=getmininginfo
ThreadRPCServer method=getinfo
keypool reserve 3
keypool return 3
ThreadRPCServer method=getmininginfo
found solution - 814 / 1968 / 239863267
ThreadRPCServer method=getinfo
keypool reserve 3
keypool return 3
ThreadRPCServer method=getmininginfo
ThreadRPCServer method=getinfo
keypool reserve 3
keypool return 3
ThreadRPCServer method=getmininginfo
testHash 8483376418dfb5403da6e6eff6d4f11215dbb1cc1eb6e16028d276a5494597b8, 1
Start Search
ThreadRPCServer method=getinfo
keypool reserve 3
keypool return 3
ThreadRPCServer method=getmininginfo



MemoryCoin version v0.8.5-59-g2806f95-beta (2013-12-18 17:42:32 +0700)
Using OpenSSL version OpenSSL 1.0.1e 11 Feb 2013
Startup time: 2013-12-19 13:29:28
Default data directory /root/.memorycoin
Using data directory /root/.memorycoin
Using at most 125 connections (1024 file descriptors available)
Using 16 threads for script verification
init message: Verifying wallet...
dbenv.open LogDir=/root/.memorycoin/database ErrorFile=/root/.memorycoin/db.log
Bound to [::]:1968
Bound to 0.0.0.0:1968
init message: Loading block index...
Opening LevelDB in /root/.memorycoin/blocks/index
Opened LevelDB successfully
Opening LevelDB in /root/.memorycoin/chainstate
Opened LevelDB successfully
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: LoadBlockIndex() : CheckIndex failed: CBlockIndex(pprev=0x7f2d88810960, pnext=(nil), nHeight=860, merkle=5673807da71bc8de6f7f9d5e618e3dd05bbf901b088742cd2383596eb7a8332f, hashBlock=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff)
: Error loading block database.
Do you want to rebuild the block database now?
Flush(false)
DBFlush(false) ended               0ms
StopNode()
Flushed 0 addresses to peers.dat  2ms
Committing 0 changed transactions to coin database...

There's always someone bitching about what's fair and what's not fair. Surely not everyone has access to an ASIC miner due to price and availability, but a cloud server? Come on... They're not that expensive and anyone with a few extra bucks can get one. May I remind you that Amazon isn't the only cloud server provider out there? Do some research and find a good host.

I've been running 5 12-core cloud server on one provider and 12 12-core (on and off) on another. 5 blocks found so far.

Also, there have been several people in this thread that has found blocks using their LAPTOPS. Hence the 'anyone' can mine this coin.

That's it, I'm not going to smell this coin again. It stinks badly! Not that it all started poorly with all the premined coins, 6% of mined coins going to developers, software crashing, blockchain not syncing correctly, had fubar difficulty targeting,... Well, now it's official that (most likely) one of existent protoshares pools started mining, if not one of developers. I wouldn't be surprised if they (PTS pools and developers) are tightly connected.

http://www.chainbrowser.com/memorycoin/address/MAWa8jwrpvg87dZCv9KAajCmMY62xJfrKY

I think we can all say bye bye to this crypto. It sucks.


From now on, developers should consider 3 things before releasing anything. 1. Working pool, 2. working miner and 3. working wallet. This is fiasco.

PS. I'm sure damage control will make pool available in 12 hours or so. Well, I'm out anyway.

hi all,

does anyone know what is current exchange rate for each MMC?

tks

Are you paying for the AWS server or using free credit?  I just got 100 bucks free credit, and started c3.4xlarge, so I am wondering how many days it will last? BTW, the max price I set is 2.2$ . Thanks.

I used to get the .. c3.xlarge (l8 cores, 10GB RAM?... the "budget" CPU server).. I guess maybe I shouldn't say this if it's ever profitable again, but you could always get those @ spot price for .07c in US East (I had 100 running on multiple occasions).

Haven't tried them with this (& they arent worth it anymore with any other coins at current prices)

ed: oh, did you get a promo at wholesaleinternet or just regular prices?  i have about 30 servers, but a lot of them i keep, like the $39 e3-1230's that online.net stuck on oneprovider

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?

aws c3.8xlarge

Ok so the windows build has now crashed on both my machines, and crashed again when trying to restart it.

or he wrote a pool miner + botnet

Who's this: MAWa8jwrpvg87dZCv9KAajCmMY62xJfrKY
And how did he hit 17 blocks...?
http://www.chainbrowser.com/memorycoin/address/MAWa8jwrpvg87dZCv9KAajCmMY62xJfrKY/

You are making a very big assumption... That Bitcoin itself can be considered stable ground with a stable value that will reflect in changing price as fiat currencies are debased.
That's a pretty large leap of faith.

The best way to make money mining is to make your own coin
https://bitcointalk.org/index.php?topic=364076.msg4021727#msg4021727