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

[FreeTrade]

only the version number is wrong? just that its a waste of 20mins to do them all again

Yes - search the debug for

Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.804799
Before: 1e77a0cc 000077a0cc000000000000000000000000000000000000000000000000000000
After: 1f081de4 00081de44f5f0f11b95b4ce37454da5a299e0ccb2e8c398bd874b5f17cacd76c

If you've got that - it's the right version

And you'll notice the 10x drop in diff

[1713490518]

1713490518

[stas]

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

Binaries available. The Kimoto Gravity Well has us now.

No updated client available yet.

i think is that
http://www.memorycoin.org/downloads/memorycoin.zip

yes. sorry. it's there.

[x0rcist]

My miner is not working anymore with newest code. I get:

Code:

EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_6system12system_errorEEEEE      
context: unable to load ssl2 md5 routines      
memorycoin in AppInit()

Anyone else seeing this?

Are you getting this error when you start the wallet, or only when you start mining?

I added some more memory cleanup code a short time ago - might be related.

This is happening when starting ./bitcoind. I might be an exception here since I am on Manjaro/Arch Linux. The previous version worked though (at least it started).

+1, same error on Ubuntu 12.04 LTS.

build with: make -f makefile.unix

so dont use the USE_PNP=- flag, should solve this error.

[voteformeg]

0.8.54 works fine for me it is synced and absolutely mining

[Sharky444]

build with: make -f makefile.unix

so dont use the USE_PNP=- flag, should solve this error.

Thanks! Works again, for 1 hour at least, then the usual crash.

Syncing very slow.

[Chida]

in debug.log i find a lot of "found solution - 13312 / 1968 / 4254976766".
What is it?

[montecristo83]

I pulled the updated version from github on Ubuntu 13.04 64-bit (VPS). Now I'm getting:

Code:

Error loading block database.
Do you want to rebuild the block database now?
bitcoind: db/version_set.cc:715: leveldb::VersionSet::~VersionSet(): Assertion `dummy_versions_.next_ == &dummy_versions_' failed.

How can I tell it to rebuild the block database?

Edit: I tried "./bitcoind --rebuild" and it resulted in:

Code:

: Error loading block database.
Do you want to rebuild the block database now?
bitcoind: db/version_set.cc:715: leveldb::VersionSet::~VersionSet(): Assertion `dummy_versions_.next_ == &dummy_versions_' failed.
Aborted (core dumped)

[Nagath]

Can't sync from block 607 to 608  

[FreeTrade]

Can't sync from block 607 to 608  

That's okay - the old fork is ahead by one or two blocks, and the new fork is rejecting those blocks.

[voteformeg]

Can't sync from block 607 to 608  

it was ok but by restart it cant sync from 608 to 609

[stas]

Can't sync from block 607 to 608  

not yet 608, that's why

[stas]

Can't sync from block 607 to 608 

not yet 608, that's why

hm.. there is, but no synch

[padre999]

same here, one machine on 607, the other at 608 while block 609 is already out.

[FreeTrade]

same here, one machine on 607, the other at 608 while 609 is already out.

try

addnode 180.183.155.90 add

[Chida]

same here, one machine on 607, the other at 608 while 609 is already out.

try

addnode 180.183.155.90 add

is possible to have a node on 8080 port?

[stuartcharles]

same here, one machine on 607, the other at 608 while 609 is already out.

try

addnode 180.183.155.90 add

tryed that? still on 607

[ryen123]

same here, one machine on 607, the other at 608 while 609 is already out.

try

addnode 180.183.155.90 add

tryed that? still on 607

Try my node 103.11.49.151

[padre999]

same here, one machine on 607, the other at 608 while 609 is already out.

try

addnode 180.183.155.90 add

tryed that? still on 607

Try my node 103.11.49.151

tried addnode 180.183.155.90 add, didn't help so far.

[FreeTrade]

tryed that? still on 607

Okay, our new fork should be up to 608 now -and difficulty is now -"difficulty" : 0.00000188,

[Chida]

addnode 103.11.49.151 add
solved me