[ANN] MemoryCoin | CPU Coin | Paid Dev Team | Limited Supply [MMC] - page 62.

montecristo83

member

Activity: 112

Merit: 10

Quote from: giveBTCpls on December 18, 2013, 11:38:48 AM

Quote from: montecristo83 on December 18, 2013, 11:11:02 AM

Quote from: giveBTCpls on December 18, 2013, 11:06:48 AM

Is this still as useless to mine as it was when it launched? any pools yet? or any place to buy some?? This seems like yet again another 1% scenareo where only people with NASA tier computers are getting coins.

A recent fork sorted out the excessive difficulty fluctuations.

You can buy/sell in this thread: https://bitcointalksearch.org/topic/btcmmc-google-spreadsheet-exchange-373396

So how many NMC per day can I make mining at 0.4??

Namecoin? 0. Cheesy

In all seriousness, I have no idea. But what I do know is that 0.4 hpm is very low, so unless you wanna roll the dice and try to get lucky; wait for a pool.

radiumsoup

sr. member

Activity: 356

Merit: 255

Quote from: FreeTrade on December 18, 2013, 11:00:13 AM

Quote from: radiumsoup on December 18, 2013, 10:42:41 AM

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?)

Okay, thanks - so if you're just running 1 thread, on each iteration, it's adding 32mb?
and if you're running 32 threads, it's adding 32x32mb = 1GB each iteration?

correct.

radiumsoup

sr. member

Activity: 356

Merit: 255

Quote from: radiumsoup on December 18, 2013, 10:42:41 AM

Quote from: FreeTrade on December 18, 2013, 09:44:03 AM

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?)

actually, this sometimes (!?) breaks ssl with "context: unable to load ssl2 md5 routines". reverting to commented.

skwinx

member

Activity: 100

Merit: 10

Quote from: FreeTrade on December 18, 2013, 11:31:57 AM

Quote from: skwinx on December 18, 2013, 11:20:14 AM

bitcoind: db/version_set.cc:715: leveldb::VersionSet::~VersionSet(): Assertion `dummy_versions_.next_ == &dummy_versions_' failed.

I have experienced this many times...........

https://bitsharestalk.org/index.php?topic=1449.new#new

yes, I hava rm the .memorycoin can be OK, but wait a period of time, will go wrong.

giveBTCpls

sr. member

Activity: 322

Merit: 250

Quote from: montecristo83 on December 18, 2013, 11:11:02 AM

Quote from: giveBTCpls on December 18, 2013, 11:06:48 AM

Is this still as useless to mine as it was when it launched? any pools yet? or any place to buy some?? This seems like yet again another 1% scenareo where only people with NASA tier computers are getting coins.

A recent fork sorted out the excessive difficulty fluctuations.

You can buy/sell in this thread: https://bitcointalksearch.org/topic/btcmmc-google-spreadsheet-exchange-373396

So how many NMC per day can I make mining at 0.4??

FreeTrade

legendary

Activity: 1428

Merit: 1030

Quote from: skwinx on December 18, 2013, 11:20:14 AM

bitcoind: db/version_set.cc:715: leveldb::VersionSet::~VersionSet(): Assertion `dummy_versions_.next_ == &dummy_versions_' failed.

I have experienced this many times...........

https://bitsharestalk.org/index.php?topic=1449.new#new

Rubick

newbie

Activity: 9

Merit: 0

Quote from: Snard on December 18, 2013, 11:13:18 AM

Is the block stuck at 612?

You'll have to delete your blockchain, update your Client and redownload the Blockchain.

jeroenn13

hero member

Activity: 644

Merit: 500

Yay. Block found =)

280 MMC for sale, PM your offers.

skwinx

member

Activity: 100

Merit: 10

bitcoind: db/version_set.cc:715: leveldb::VersionSet::~VersionSet(): Assertion `dummy_versions_.next_ == &dummy_versions_' failed.

I have experienced this many times...........

ryen123

sr. member

Activity: 292

Merit: 250

Quote from: Snard on December 18, 2013, 11:13:18 AM

Is the block stuck at 612?

It is currently block 639

Snard

full member

Activity: 140

Merit: 100

Is the block stuck at 612?

montecristo83

member

Activity: 112

Merit: 10

Quote from: giveBTCpls on December 18, 2013, 11:06:48 AM

Is this still as useless to mine as it was when it launched? any pools yet? or any place to buy some?? This seems like yet again another 1% scenareo where only people with NASA tier computers are getting coins.

A recent fork sorted out the excessive difficulty fluctuations.

You can buy/sell in this thread: https://bitcointalksearch.org/topic/btcmmc-google-spreadsheet-exchange-373396

giveBTCpls

sr. member

Activity: 322

Merit: 250

Is this still as useless to mine as it was when it launched? any pools yet? or any place to buy some?? This seems like yet again another 1% scenareo where only people with NASA tier computers are getting coins.

montecristo83

member

Activity: 112

Merit: 10

Quote from: Riseman on December 18, 2013, 10:43:04 AM

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?

This coin has better features than a lot of the (cloned) coins already listed on the various exchanges. I don't see why it shouldn't get added to an exchange.

Quote from: Rubick on December 18, 2013, 10:44:19 AM

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.

I think the sooner the better. That's just my personal opinion though.

He announced the fork yesterday, and pushed it forward since it seemed like we were gonna be stuck for a very long time at a certain block. Surely the same would happen with more than one of about 150 blocks.

FreeTrade

legendary

Activity: 1428

Merit: 1030

Quote from: radiumsoup on December 18, 2013, 10:42:41 AM

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?)

Okay, thanks - so if you're just running 1 thread, on each iteration, it's adding 32mb?
and if you're running 32 threads, it's adding 32x32mb = 1GB each iteration?

Rubick

newbie

Activity: 9

Merit: 0

Quote from: montecristo83 on December 18, 2013, 10:38:44 AM

Quote from: FreeTrade on December 18, 2013, 10:33:16 AM

Quote from: radiumsoup on December 18, 2013, 10:01:14 AM

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.

Riseman

hero member

Activity: 690

Merit: 500

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?

radiumsoup

sr. member

Activity: 356

Merit: 255

Quote from: FreeTrade on December 18, 2013, 09:44:03 AM

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?)

truckythin

hero member

Activity: 781

Merit: 501

Quote from: montecristo83 on December 18, 2013, 10:38:44 AM

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 Undecided

montecristo83

member

Activity: 112

Merit: 10

Quote from: FreeTrade on December 18, 2013, 10:33:16 AM

Quote from: radiumsoup on December 18, 2013, 10:01:14 AM

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.

Topic: [ANN] MemoryCoin | CPU Coin | Paid Dev Team | Limited Supply [MMC] - page 62. (Read 281382 times)