[ANN] MemoryCoin

[Sondey10mg]

I'm trying to update but I get this error while starting up

Linux noob so please help


root@Memorycoin:~/memorycoinupdate/memorycoin/src# ./bitcoind --daemon
root@Memorycoin:~/memorycoinupdate/memorycoin/src# Bitcoin server starting
*** Error in `./bitcoind': munmap_chunk(): invalid pointer: 0x00000000024f169a ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x7f576)[0x7f3249e63576]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZNSs6assignERKSs+0x86)[0x7f324a784666]
./bitcoind[0x47d639]
./bitcoind[0x5d5dbb]
./bitcoind[0x497822]
./bitcoind[0x4982c5]
./bitcoind[0x4540b8]
./bitcoind[0x4727f5]
./bitcoind[0x41ac11]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f3249e05ea5]
./bitcoind[0x41e8f1]
======= Memory map: ========
00400000-00772000 r-xp 00000000 fd:00 264725                             /root/memorycoinupdate/memorycoin/src/bitcoind
00971000-00973000 r--p 00371000 fd:00 264725                             /root/memorycoinupdate/memorycoin/src/bitcoind
00973000-00974000 rw-p 00373000 fd:00 264725                             /root/memorycoinupdate/memorycoin/src/bitcoind
00974000-00978000 rw-p 00000000 00:00 0
023f8000-02559000 rw-p 00000000 00:00 0                                  [heap]
7f3240000000-7f3240021000 rw-p 00000000 00:00 0
7f3240021000-7f3244000000 ---p 00000000 00:00 0
7f3244a3c000-7f3244cfd000 rw-p 00000000 00:00 0
7f3244cfd000-7f3244cfe000 ---p 00000000 00:00 0
7f3244cfe000-7f32454fe000 rw-p 00000000 00:00 0                          [stack:14061]
7f32454fe000-7f32457c7000 r--p 00000000 fd:00 921502                     /usr/lib/locale/locale-archive
7f32457c7000-7f32499c9000 rw-p 00000000 00:00 0
7f32499c9000-7f32499df000 r-xp 00000000 fd:00 1049547                    /lib/x86_64-linux-gnu/libz.so.1.2.7
7f32499df000-7f3249bde000 ---p 00016000 fd:00 1049547                    /lib/x86_64-linux-gnu/libz.so.1.2.7
7f3249bde000-7f3249bdf000 r--p 00015000 fd:00 1049547                    /lib/x86_64-linux-gnu/libz.so.1.2.7
7f3249bdf000-7f3249be0000 rw-p 00016000 fd:00 1049547                    /lib/x86_64-linux-gnu/libz.so.1.2.7
7f3249be0000-7f3249be3000 r-xp 00000000 fd:00 1049502                    /lib/x86_64-linux-gnu/libdl-2.17.so
7f3249be3000-7f3249de2000 ---p 00003000 fd:00 1049502                    /lib/x86_64-linux-gnu/libdl-2.17.so
7f3249de2000-7f3249de3000 r--p 00002000 fd:00 1049502                    /lib/x86_64-linux-gnu/libdl-2.17.so
7f3249de3000-7f3249de4000 rw-p 00003000 fd:00 1049502                    /lib/x86_64-linux-gnu/libdl-2.17.so
7f3249de4000-7f3249fa2000 r-xp 00000000 fd:00 1049550                    /lib/x86_64-linux-gnu/libc-2.17.so
7f3249fa2000-7f324a1a1000 ---p 001be000 fd:00 1049550                    /lib/x86_64-linux-gnu/libc-2.17.so
7f324a1a1000-7f324a1a5000 r--p 001bd000 fd:00 1049550                    /lib/x86_64-linux-gnu/libc-2.17.so
7f324a1a5000-7f324a1a7000 rw-p 001c1000 fd:00 1049550                    /lib/x86_64-linux-gnu/libc-2.17.so
7f324a1a7000-7f324a1ac000 rw-p 00000000 00:00 0
7f324a1ac000-7f324a1c0000 r-xp 00000000 fd:00 1049598                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f324a1c0000-7f324a3c0000 ---p 00014000 fd:00 1049598                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f324a3c0000-7f324a3c1000 r--p 00014000 fd:00 1049598                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f324a3c1000-7f324a3c2000 rw-p 00015000 fd:00 1049598                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f324a3c2000-7f324a4c5000 r-xp 00000000 fd:00 1049496                    /lib/x86_64-linux-gnu/libm-2.17.so
7f324a4c5000-7f324a6c5000 ---p 00103000 fd:00 1049496                    /lib/x86_64-linux-gnu/libm-2.17.so
7f324a6c5000-7f324a6c6000 r--p 00103000 fd:00 1049496                    /lib/x86_64-linux-gnu/libm-2.17.so
7f324a6c6000-7f324a6c7000 rw-p 00104000 fd:00 1049496                    /lib/x86_64-linux-gnu/libm-2.17.so
7f324a6c7000-7f324a7ac000 r-xp 00000000 fd:00 918072                     /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.17
7f324a7ac000-7f324a9ab000 ---p 000e5000 fd:00 918072                     /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.17
7f324a9ab000-7f324a9b3000 r--p 000e4000 fd:00 918072                     /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.17
7f324a9b3000-7f324a9b5000 rw-p 000ec000 fd:00 918072                     /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.17
7f324a9b5000-7f324a9ca000 rw-p 00000000 00:00 0
7f324a9ca000-7f324a9e2000 r-xp 00000000 fd:00 1049600                    /lib/x86_64-linux-gnu/libpthread-2.17.so
7f324a9e2000-7f324abe1000 ---p 00018000 fd:00 1049600                    /lib/x86_64-linux-gnu/libpthread-2.17.so
7f324abe1000-7f324abe2000 r--p 00017000 fd:00 1049600                    /lib/x86_64-linux-gnu/libpthread-2.17.so
7f324abe2000-7f324abe3000 rw-p 00018000 fd:00 1049600                    /lib/x86_64-linux-gnu/libpthread-2.17.so
7f324abe3000-7f324abe7000 rw-p 00000000 00:00 0
7f324abe7000-7f324ad98000 r-xp 00000000 fd:00 1049544                    /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
7f324ad98000-7f324af98000 ---p 001b1000 fd:00 1049544                    /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
7f324af98000-7f324afb3000 r--p 001b1000 fd:00 1049544                    /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
7f324afb3000-7f324afbe000 rw-p 001cc000 fd:00 1049544                    /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
7f324afbe000-7f324afc2000 rw-p 00000000 00:00 0
7f324afc2000-7f324b015000 r-xp 00000000 fd:00 1049549                    /lib/x86_64-linux-gnu/libssl.so.1.0.0
7f324b015000-7f324b215000 ---p 00053000 fd:00 1049549                    /lib/x86_64-linux-gnu/libssl.so.1.0.0
7f324b215000-7f324b218000 r--p 00053000 fd:00 1049549                    /lib/x86_64-linux-gnu/libssl.so.1.0.0
7f324b218000-7f324b21e000 rw-p 00056000 fd:00 1049549                    /lib/x86_64-linux-gnu/libssl.so.1.0.0
7f324b21e000-7f324b21f000 rw-p 00000000 00:00 0
7f324b21f000-7f324b3dc000 r-xp 00000000 fd:00 928411                     /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so
7f324b3dc000-7f324b5dc000 ---p 001bd000 fd:00 928411                     /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so
7f324b5dc000-7f324b5e4000 r--p 001bd000 fd:00 928411                     /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so
7f324b5e4000-7f324b5e5000 rw-p 001c5000 fd:00 928411                     /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so
7f324b5e5000-7f324b5fe000 r-xp 00000000 fd:00 930974                     /usr/lib/libboost_thread.so.1.49.0
7f324b5fe000-7f324b7fe000 ---p 00019000 fd:00 930974                     /usr/lib/libboost_thread.so.1.49.0
7f324b7fe000-7f324b800000 r--p 00019000 fd:00 930974                     /usr/lib/libboost_thread.so.1.49.0
7f324b800000-7f324b801000 rw-p 0001b000 fd:00 930974                     /usr/lib/libboost_thread.so.1.49.0
7f324b801000-7f324b85d000 r-xp 00000000 fd:00 931205                     /usr/lib/libboost_program_options.so.1.49.0
7f324b85d000-7f324ba5d000 ---p 0005c000 fd:00 931205                     /usr/lib/libboost_program_options.so.1.49.0
7f324ba5d000-7f324ba60000 r--p 0005c000 fd:00 931205                     /usr/lib/libboost_program_options.so.1.49.0
7f324ba60000-7f324ba61000 rw-p 0005f000 fd:00 931205                     /usr/lib/libboost_program_options.so.1.49.0
7f324ba61000-7f324ba7f000 r-xp 00000000 fd:00 930714                     /usr/lib/libboost_filesystem.so.1.49.0
7f324ba7f000-7f324bc7f000 ---p 0001e000 fd:00 930714                     /usr/lib/libboost_filesystem.so.1.49.0
7f324bc7f000-7f324bc80000 r--p 0001e000 fd:00 930714                     /usr/lib/libboost_filesystem.so.1.49.0
7f324bc80000-7f324bc81000 rw-p 0001f000 fd:00 930714                     /usr/lib/libboost_filesystem.so.1.49.0
7f324bc81000-7f324bc84000 r-xp 00000000 fd:00 930693                     /usr/lib/libboost_system.so.1.49.0
7f324bc84000-7f324be83000 ---p 00003000 fd:00 930693                     /usr/lib/libboost_system.so.1.49.0
7f324be83000-7f324be84000 r--p 00002000 fd:00 930693                     /usr/lib/libboost_system.so.1.49.0
7f324be84000-7f324be85000 rw-p 00003000 fd:00 930693                     /usr/lib/libboost_system.so.1.49.0
7f324be85000-7f324bea8000 r-xp 00000000 fd:00 1049594                    /lib/x86_64-linux-gnu/ld-2.17.so
7f324c01e000-7f324c01f000 rw-p 00000000 00:00 0
7f324c01f000-7f324c04f000 r--s 00000000 fd:00 264747                     /root/.memorycoin/blocks/index/000005.sst
7f324c04f000-7f324c05f000 rw-s 00000000 fd:00 264746                     /root/.memorycoin/chainstate/MANIFEST-000012
7f324c05f000-7f324c060000 rw-p 00000000 00:00 0
7f324c060000-7f324c070000 rw-s 00000000 fd:00 264751                     /root/.memorycoin/blocks/index/MANIFEST-000011
7f324c070000-7f324c09b000 rw-p 00000000 00:00 0
7f324c09b000-7f324c09e000 rw-p 00000000 00:00 0
7f324c09e000-7f324c0a5000 r--s 00000000 fd:00 917816                     /usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache
7f324c0a5000-7f324c0a7000 rw-p 00000000 00:00 0
7f324c0a7000-7f324c0a8000 r--p 00022000 fd:00 1049594                    /lib/x86_64-linux-gnu/ld-2.17.so
7f324c0a8000-7f324c0aa000 rw-p 00023000 fd:00 1049594                    /lib/x86_64-linux-gnu/ld-2.17.so
7fff84b3d000-7fff84b72000 rw-p 00000000 00:00 0                          [stack]
7fff84bfe000-7fff84c00000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]

[stas]

Mr Wax,

Not sure if you noticed, but I'm concerned the coin is dying a slow death in its present form and radical surgery is needed to save it. I've proposed a fork.
https://asktom.cf/index.php?topic=285232.0

Interested to hear your thoughts on it as your fund has clearly shown that you have a good understanding of the grants and votes - although I'm sure you'll be conflicted as it aims to kill your fund along with the other interest payment grants.

Also, logo competition is over. A decent logo should help the coin's image.

@ FreeTrade:
I don't think that coin is dying. We do need a pool and a better exchange (criptsy)
The trading value of MEG is much better than many other coins, so is the price.
Considering the fact that not many people know/use BTER exchange, I would say the coin is doing OK. 

Stas

[stas]

today's value on BTER is ~16000 MEG
It's more than 10% of all current supply
So things are not that bad.
Once again, the priority would be the pool and a better exchange than making voting system better:)

[mercSuey]

Come on Quantplus,

the thing that is interesting with this coin is the voting system.
If you want to mine a clone coin with no innovation, there is plenty out there.

The fact that FreeTrade get one of the 5 grant is perfectly normal since he didn't premine.
But yet we can chose at any-time to remove this grant from him.
And that's what happened once already, and he has the right to whine about it.

This is far better than premine, because he can't dump it all at once, and he need to keep on with the support of the coin, otherwise we can remove the grant from him.

As far as the market, I think FT is not the kind of vocal man, who shout everywhere to promote the coin, and it's ok since he is a developer, not a salesman or public relation.
So what memorycoin lack is some kind of promotion.
And I guess as a collective we have to take that in charge.

So if you want more byers, then move your ass and promote the coin !

Well, there's a irony about cpu-only coins...and more so when it's designed to hit L2 memory.  The cpu is an 'all-purpose' chip, and yet, when the MemoryCoin client is run on a personal computer in a household, the computer becomes basically paralyzed.  Performance degrades a lot when constantly accessing L2 memory and cpu resource usage is at 100%.  So you want to promote this, but to who?  And for what?  To paralyze your personal computer and not allow you to do anything else?  No, unfortunately, cpu-only coins are botnet canon fodder until they are no longer profitable.  And so far, the price action of cpu-only coins depicts this to be the case.

While getting my graduate degree in Mathematics, the main thing that was constantly pounded into my head by professors was don't try to 'reinvent the wheel'.  In other words, just use the work of someone else who worked on the problem before me and try to add to it.  In the art world, Picasso says something similar, "Good artists copy.  Great artists steal." 

Every development project starts somewhere.  And in time, the successful projects add to their origins and evolve.

-Merc

[stas]

Come on Quantplus,

the thing that is interesting with this coin is the voting system.
If you want to mine a clone coin with no innovation, there is plenty out there.

The fact that FreeTrade get one of the 5 grant is perfectly normal since he didn't premine.
But yet we can chose at any-time to remove this grant from him.
And that's what happened once already, and he has the right to whine about it.

This is far better than premine, because he can't dump it all at once, and he need to keep on with the support of the coin, otherwise we can remove the grant from him.

As far as the market, I think FT is not the kind of vocal man, who shout everywhere to promote the coin, and it's ok since he is a developer, not a salesman or public relation.
So what memorycoin lack is some kind of promotion.
And I guess as a collective we have to take that in charge.

So if you want more byers, then move your ass and promote the coin !

Well, there's a irony about cpu-only coins...and more so when it's designed to hit L2 memory.  The cpu is an 'all-purpose' chip, and yet, when the MemoryCoin client is run on a personal computer in a household, the computer becomes basically paralyzed.  Performance degrades a lot when constantly accessing L2 memory and cpu resource usage is at 100%.  So you want to promote this, but to who?  And for what?  To paralyze your personal computer and not allow you to do anything else?  No, unfortunately, cpu-only coins are botnet canon fodder until they are no longer profitable.  And so far, the price action of cpu-only coins depicts this to be the case.

While getting my graduate degree in Mathematics, the main thing that was constantly pounded into my head by professors was don't try to 'reinvent the wheel'.  In other words, just use the work of someone else who worked on the problem before me and try to add to it.  In the art world, Picasso says something similar, "Good artists copy.  Great artists steal." 

Every development project starts somewhere.  And in time, the successful projects add to their origins and evolve.

-Merc

Have You actually used Memory Coin client?
Because it runs on my PC at work and does not disturb to work I do during the usual working day.
Especially the latest client which only uses half of the PC's power.

[stas]

today's value on BTER is ~16000 MEG
It's more than 10% of all current supply
So things are not that bad.
Once again, the priority would be the pool and a better exchange than making voting system better:)

The market is working...
But volume is deceptive because price crashed 75% from 0.0004 to 0.0001...
And Q+ was not responsible for the Crash...
It was a buggy Client... and all the bullshit with the 20% Mining Tax = Grant System...
Even bter has told me they are having problems with Client and network.

Stas, ask yourself a serious question:

Do you really expect the idiot who designed the current "Voting System"...
And buried it as cryptic text in the "debug.log" file...
While creative people are building fabulous $10 million BTC Casinos...
To "make it better" after > one month of not making it "better"?

It's nothing more than a Smokescreen for grabbing 20% of the Coins.

I don't know why you are seeing all in such a negative and an incorrect way.
You keep saying that he is getting 20%, but he is not. You are wrong here, that's a fact. look at the voting longs there is a proof.
he gets something. and if you ask me it's not a lot, considering the fact that he is working constantly on improving the client and the whole concept + he does spend the money he gets on bounties.
So i do not agree with you completely.

Stas

[SlyWax]

Come on Quantplus,

the thing that is interesting with this coin is the voting system.
If you want to mine a clone coin with no innovation, there is plenty out there.

The fact that FreeTrade get one of the 5 grant is perfectly normal since he didn't premine.
But yet we can chose at any-time to remove this grant from him.
And that's what happened once already, and he has the right to whine about it.

This is far better than premine, because he can't dump it all at once, and he need to keep on with the support of the coin, otherwise we can remove the grant from him.

As far as the market, I think FT is not the kind of vocal man, who shout everywhere to promote the coin, and it's ok since he is a developer, not a salesman or public relation.
So what memorycoin lack is some kind of promotion.
And I guess as a collective we have to take that in charge.

So if you want more byers, then move your ass and promote the coin !

Well, there's a irony about cpu-only coins...and more so when it's designed to hit L2 memory.  The cpu is an 'all-purpose' chip, and yet, when the MemoryCoin client is run on a personal computer in a household, the computer becomes basically paralyzed.  Performance degrades a lot when constantly accessing L2 memory and cpu resource usage is at 100%.  So you want to promote this, but to who?  And for what?  To paralyze your personal computer and not allow you to do anything else?  No, unfortunately, cpu-only coins are botnet canon fodder until they are no longer profitable.  And so far, the price action of cpu-only coins depicts this to be the case.

You are contradicting yourself, because if the client where to paralyse your system, then the botnet couldn't use it, since if an infected computer is paralysed, the user just reformat and reinstall the OS. So botnet have to be stealth and not consuming all the cpu of it's minion.

If you want to work at the same time, just set the priority of the mining process low.

While getting my graduate degree in Mathematics, the main thing that was constantly pounded into my head by professors was don't try to 'reinvent the wheel'.  In other words, just use the work of someone else who worked on the problem before me and try to add to it.  In the art world, Picasso says something similar, "Good artists copy.  Great artists steal." 

I don't see where you are going there ?
But what your teacher has failed to tell you yet, is that once you have stooped studying and if you what to become a great mathematician, you will have to find your own way.

Every development project starts somewhere.  And in time, the successful projects add to their origins and evolve.

-Merc

Sure, but mostly in computer development, if you want to make a big step ahead, you have to "trash everything and start from a clean well thought state" (with the knowledge you have acquired with the previous version).

Sly.

[xchrix]

this looks very interesting! reserved for watching

[FreeTrade]

Ok there's hard fork on block 8710. That's 1 week from now, and should give everybody enough time to get the updated code.

I've uploaded a new client here -
http://memorycoin.org/downloads/memorycoin-qt-latest.zip

and Github is updated with the new source.

From block 8710 onwards, only 1 large grant rather than 5 small ones will be awarded in the block chain. This change has been made to ensure that awards are only made to grants that enjoy broad community support. The total amount of awards won't change so the inflation rate will remain unaffected.

[superresistant]

Hi,

I cannot open the linux build. The xz archive won't decompress on linux.
On windows, with 7zip, there is no name on any file.

Can someone upload a normal archive please ?

Or just describe me the content of the archive so I can put name and format on all files ?

Thanks

EDIT : work great on windows but still can't open the archive on linux. Can someone create a zip file for me ?

Forget it, I found a solution :

 a)     git clone https://github.com/memorycoin/memorycoin.git
     b)     cd memorycoin
     c)     sudo apt-get install qt4-qmake libqt4-dev build-essential libboost-dev libboost-system-dev \
             libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev \
             libssl-dev libdb++-dev libminiupnpc-dev libjpeg62
     d)     qmake
     e)     make

[Zalfrin]

Downloaded new client, found that I've been mining on a fork for the past 3 days... Grrr....

Can't get any peers with the new client. I used the addnodes from post 1, which had worked before, but no connections showing up any more.

[FreeTrade]

Hmm - give these IPs a try -

"addr" : "192.241.163.164:8555",
"addr" : "110.190.247.14:8555",
"addr" : "178.33.191.150:8555",
"addr" : "79.113.223.83:8555",
"addr" : "182.130.181.127:8555",

[Zalfrin]

Hmm - give these IPs a try -

"addr" : "192.241.163.164:8555",
"addr" : "110.190.247.14:8555",
"addr" : "178.33.191.150:8555",
"addr" : "79.113.223.83:8555",
"addr" : "182.130.181.127:8555",

Thanks. Got a connection out of those.

I still had connections to other peers while I was forked, but I don't see any evidence of my debug log of anyone else generating blocks but me. 9/2 06:54 (CST) was my last accepted block, first orphan on 9/3 06:32. FYI.

So now my client is hung on block 6439. Guess I will restart again.

EDIT: Still stuck on 6439, but now getting an orange banner on QT: "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade." Nice. Time to delete blockchain I suppose.

[Zalfrin]

Something odd since switching to the new client: My hashespersec has dropped quite a bit. From 12-13 to 8-9. Looking at core utilization, core 2 is never used more than ~30%. The other cores seem to average around 70%.

[FreeTrade]

Something odd since switching to the new client: My hashespersec has dropped quite a bit. From 12-13 to 8-9. Looking at core utilization, core 2 is never used more than ~30%. The other cores seem to average around 70%.

MemoryCoin only uses half of available cores by default now - you can explicitly set the number of cores using

setgenerate true <numberofcores>

The rationale is that the MC client is being designed for ease of use - so we don't want newbies machines grinding to a halt when they start using it. For more advanced users, they can set the number of cores explicitly.

[Zalfrin]

Something odd since switching to the new client: My hashespersec has dropped quite a bit. From 12-13 to 8-9. Looking at core utilization, core 2 is never used more than ~30%. The other cores seem to average around 70%.

MemoryCoin only uses half of available cores by default now - you can explicitly set the number of cores using

setgenerate true <numberofcores>

The rationale is that the MC client is being designed for ease of use - so we don't want newbies machines grinding to a halt when they start using it. For more advanced users, they can set the number of cores explicitly.

Thanks. Makes sense, though even with all cores pegged on my PC, I don't have any usability concerns. I'm just used to the -1 meaning all cores.

[Zalfrin]

Well, I mined one block successfully yesterday, then my client forked again. There's another 7 orphans... I may be done mining this coin since my client can't stay connected to the current block chain.

Sequence was:
mined block 7155.
saw block 7156 from a peer.
forked.

debug log:
received getdata for: block 0000251d3f0d81c65b9fbbaafdb6058115b1a6ab0d5591f7928ac40ffeeebad2
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
Flushed 2225 addresses to peers.dat  11ms
socket recv error 10054
disconnecting node [2001:0:5ef5:79fb:1c61:44a:2bbf:5a6e]:8555
trying connection 216.218.196.43:8555 lastseen=941.4hrs
connection timeout

followed by tons and tons of these trying connection... timeout... disconnecting... messages. Then I start generating orphans.

[superresistant]

What is the calculation for the time to find a block from the current difficulty and the hash per second please ?

[FreeTrade]

Well, I mined one block successfully yesterday, then my client forked again. There's another 7 orphans... I may be done mining this coin since my client can't stay connected to the current block chain.

What OS are you using? And are you downloading or compiling your own client?

You might find opening port 8555 keeps you better connected - that might reduce problems, but I'm not sure what's going on with your client yet.

[FreeTrade]

What is the calculation for the time to find a block from the current difficulty and the hash per second please ?

Someone posted a formula for this - I think in this thread. Let us all know if it seems to be accurate based on your experiences.