[ANN] MemoryCoin | CPU Coin | Paid Dev Team | Limited Supply [MMC]

[FreeTrade]

Are there updated binaries for Windows? Mine still says 0.8.52.0.  I jsut redownloaded from links on first post.

Yes - you might be getting a cached version. Try the Google link.

I'll change the file name too - that should help. Try -

http://www.memorycoin.org/downloads/memorycoin854.zip

[1714032244]

1714032244

[1714032244]

1714032244

[1714032244]

1714032244

[1714032244]

1714032244

[Chida]

hi,
When do you believe it is possible the minning every 6 minutes?

I think we're on a pretty good course for that. 10 blocks over the past 50 minutes or so. Difficulty around the 170/180 mark.

Right now our diff is 0008d86c2464a8c536fe1a8c536fe1a8c536fe1a8c536fe1a8c536fe1a8c5387

You'd expect to need 16x16x16x2 hashes per block . .

8192 per block

At 4 hashes per minute, that's about 34 hours.

Good

[Rubick]

My wallet gets stuck at block 614... So, I stop mining, waiting for a pool and external miner.

Probably old branch.

Is there some forking going on here? I'm at block 615 at the moment, the last block was generated only a couple of minutes ago. Version 0.8.53.0.

I'll try with 0.8.54.0.

[ig0tik3d]

 0.8.54.0


getblockhash 619


0002396ed633e456fd9764c7c9dfc7b5480e35984005d77edb45cf3f14f49b79

[nomullet]

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

[radiumsoup]

Okay. Flash Fork at 607 - github updated. Binaries available shortly.

Not cool, man - you just effectively cut off those who took the time to upgrade due to the carefully and considerately planned announcement, in favor of those who happened to catch the thread just when you posted. :\

[Rubick]

I'm using client version 0.8.54.0 now, still stuck at block 615. According to the debug log, the client is connected to several nodes that report they have 620 blocks but my client makes no effort to catch up on the missing blocks!

I'm possibly on a fork because my block 615 differs from this one: http://www.chainbrowser.com/memorycoin/block/00017a2988f88953776c084b8010cbd74fd6c98e08d5cd834df786aed13acd09/
How can I get my client to load the correct chain?

edit: Seems like my client is on the wrong side of the fork at block 607, how can I fix this?

[Orrechorre]

any pool coming out? seems to difficult to solo mine

[montecristo83]

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

This post solved my issues: https://bitcointalk.org/index.php?topic=370806.msg4024975#msg4024975

I ran these commands on my linux instances (I'm a linux newbie. Use at your own risk):

Code:

cd

cd .memorycoin

rm peers.dat

rm db.log

rm debug.log

rm memorycoin.conf

rm -r blocks

rm -r chainstate

I'm using client version 0.8.54.0 now, still stuck at block 615. According to the debug log, the client is connected to several nodes that report they have 620 blocks but my client makes no effort to catch up on the missing blocks!

I'm possibly on a fork because my block 615 differs from this one: http://www.chainbrowser.com/memorycoin/block/00017a2988f88953776c084b8010cbd74fd6c98e08d5cd834df786aed13acd09/
How can I get my client to load the correct chain?

edit: Seems like my client is on the wrong side of the fork at block 607, how can I fix this?

This post solved my issues: https://bitcointalk.org/index.php?topic=370806.msg4024975#msg4024975

This post solved my issues: https://bitcointalk.org/index.php?topic=370806.msg4024975#msg4024975

Re-downloading the blockchain, sounds fun ...

More fun than being on the wrong fork.

[Snard]

Yes - you might be getting a cached version. Try the Google link.

I'll change the file name too - that should help. Try -

http://www.memorycoin.org/downloads/memorycoin854.zip

You may want to consider changing the version number on the executable as well.  Still says 0.8.52.0

[Rubick]

This post solved my issues: https://bitcointalk.org/index.php?topic=370806.msg4024975#msg4024975

Re-downloading the blockchain, sounds fun ... Guess I better waste my cpu cycles on some other useless stuff.
I don't get how one could think that doing a fork at 607 was a good idea when the chain was at 605 or something? So many ppl are cought in that fork because they trusted it would happen at 750 and they would be on the safe side since they updated already today...

[Tamis]

I've lost 10% of my hpm !

Is this normal ?

[mmx888]

I need node pls give me ..

THX!!!

[FreeTrade]

Not cool, man - you just effectively cut off those who took the time to upgrade due to the carefully and considerately planned announcement, in favor of those who happened to catch the thread just when you posted. :\

I hear you. It was a difficult call. It looked to me that the blockchain had effectively halted and I was concerned that we'd never reach block 750. I had to act quickly in the interests of the coin. I think we're in a much better place now than if we had waited.

[jabbaah]

"version" : 85400

getblockhash 629

00011254d00b698574d16a9c3c82d95fdfc14b40eee9229ee5bb8695703a2a04

[montecristo83]

Not cool, man - you just effectively cut off those who took the time to upgrade due to the carefully and considerately planned announcement, in favor of those who happened to catch the thread just when you posted. :\

I hear you. It was a difficult call. It looked to me that the blockchain had effectively halted and I was concerned that we'd never reach block 750. I had to act quickly in the interests of the coin. I think we're in a much better place now than if we had waited.

For what it's worth, I think you made the right call. A lot of people were complaining about the excessive jumps in difficulty, and I believe many of us would simply stop mining because of that.

It would probably take more than 24 hours to get to block 750; with more and more people simply giving up on mining before reaching this block.

[truckythin]

It would probably take more than 24 hours to get to block 750; with more and more people simply giving up on mining before reaching this block.

give up! cannot play with luck since i have to pay the bill too 

[radiumsoup]

Okay, can you try uncommenting (latest source) lines 136, 137

      //CRYPTO_cleanup_all_ex_data();
      //EVP_cleanup();

and  271, 272

      //CRYPTO_cleanup_all_ex_data();
      //EVP_cleanup();

Let me know if that helps please.

Thanks for addressing this.

Tired on source posted as of 30 minutes ago, I still get the same thing... 32mb per thread added to vmem every time the CPU dips (not exactly sure what's happening, probably finished with old work and starting new work?)

[Riseman]

Maybe a stupid question... Will this coin be listed on any cryptocurrency exchange someday? Is there any info or assumption on when will it happen and what the price might be?

[Rubick]

Not cool, man - you just effectively cut off those who took the time to upgrade due to the carefully and considerately planned announcement, in favor of those who happened to catch the thread just when you posted. :\

I hear you. It was a difficult call. It looked to me that the blockchain had effectively halted and I was concerned that we'd never reach block 750. I had to act quickly in the interests of the coin. I think we're in a much better place now than if we had waited.

For what it's worth, I think you made the right call. A lot of people were complaining about the excessive jumps in difficulty, and I believe many of us would simply stop mining because of that.

It would probably take more than 24 hours to get to block 750; with more and more people simply giving up on mining before reaching this block.

It sure was the right choice to re-adjust the fork. But block 607? A higher block number would have given everyone a bit more time to react.