Proposal for a restart -
http://21stcenturymoneytalk.org/index.php/topic,30.0.html
Topic: [ANN] MemoryCoin - page 31. (Read 100338 times)
It seems the blockchain takes ages to synchronize and the coin is only some days old.
Yes, the hash takes a long time to run - say 0.5 seconds or so . . . at a block height of only 1,200 . . . that's 600 seconds, 10 minutes. We're going to need a hash-lookup table distributed with the executable at a minimum for new nodes.
It seems the blockchain takes ages to synchronize and the coin is only some days old.
I have installed the latest version on two PC's. So far works fine.
Latest build is not working. Failed while synchronizing the blockchain.
Runtime error.
Runtime error.
Are you starting with the mining switched off?
Mining while synchronizing reliably causes crashes.
Difficultly has doubled in the past few hours, and I'm seeing a lot more connected peers. I think this is down to the latest client performing better on multi-core machines.
I think the last 1680-version-3 is less stable than the first 1680 version. I can't get my 6-core intel to mine more than a few blocks before getting stuck on a block with the last release. (it eventually gets stuck with the first 1680 version as well, but I have a feeling it lasts longer)
Have you identified why the program hangs while syncing and mining? As mentioned before, I think there is a big chance you will fix the hanging on blocks while mining if you fix this syncing issue.
Latest build is not working. Failed while synchronizing the blockchain.
Runtime error.
Runtime error.
Are you starting with the mining switched off?
Mining while synchronizing reliably causes crashes.
Difficultly has doubled in the past few hours, and I'm seeing a lot more connected peers. I think this is down to the latest client performing better on multi-core machines.
This thread is interesting. Watching
This coin network will simply not work without UPnP support in the compiled release, it should be your priority.
if you could list the date next to the client link each time its updated that would be helpful
Latest build is not working. Failed while synchronizing the blockchain.
Runtime error.
Latest lines of the debug.log :
Runtime error.
Latest lines of the debug.log :
Code:
processNextBlockIntoGrantDatabase 13
processNextBlockIntoGrantDatabase 14
processNextBlockIntoGrantDatabase 15
processNextBlockIntoGrantDatabase 16
processNextBlockIntoGrantDatabase 17
processNextBlockIntoGrantDatabase 18
processNextBlockIntoGrantDatabase 19
processNextBlockIntoGrantDatabase 20
getGrantAwardsFromDatabase 40
-------------:
Vote Count:
-------------:
--------Grant Voting--------
---Current Balances------
5 addresses with balances. Printing Top 20
->Balance:264 - MLdZXb6PTZ1Pz9iSsUF2UGtkTJ28Ek4GTS
->Balance:144 - MVkBCWGjgFk93w7VkZhrftoLWrPyztGGJv
->Balance:48 - MNsqNybJLJfntPwT1mocU7C6R763y3uRao
->Balance:24 - MQ4T6yAJBpQLUbSbYw2QEsUJTAhHa4v52A
->Balance:24 - MGv9cSYnaRSTZNzYaN7bhbgmozoGkKBvCn
---End Balances------
Total coin issued: 504
Total of Voters' Balances: 0
Percentage of total issued coin voting: 0 percent
Droop Quota: 0
-------------:
Award Round:0
I'm getting a segfault with the latest code.
Allright then, let's give this one a try.
It's running and I will try to keep an eye on it for some time, but actually it's time for my beautysleep
Fingers crossd.
It's running and I will try to keep an eye on it for some time, but actually it's time for my beautysleep
Fingers crossd.
Sorry to break the bad news but my 6-core machine got stuck on block 1227 just now
Thanks yes - that was a train wreck. Here's the new one.
https://docs.google.com/file/d/0B-5Ax5kejTpMMDlBYTdkbllDbzQ/edit?usp=sharing
https://docs.google.com/file/d/0B-5Ax5kejTpMMDlBYTdkbllDbzQ/edit?usp=sharing
Allright then, let's give this one a try.
It's running and I will try to keep an eye on it for some time, but actually it's time for my beautysleep
Fingers crossd.
No need to wait until tomorrow, both machines went down already.
One got stuck on block 1218 and the other crashed with a runtime error.
I'm back to the previous version for now.
One got stuck on block 1218 and the other crashed with a runtime error.
I'm back to the previous version for now.
Thanks yes - that was a train wreck. Here's the new one.
https://docs.google.com/file/d/0B-5Ax5kejTpMMDlBYTdkbllDbzQ/edit?usp=sharing
I just installed it on both my multi-core machines so let's see if it survives the night without hanging (and hopefully solving some blocks).
I will report back tomorrow.
I will report back tomorrow.
No need to wait until tomorrow, both machines went down already.
One got stuck on block 1218 and the other crashed with a runtime error.
I'm back to the previous version for now.
Installed the new version an hour ago (as soon as it got released) and it worked fine until now when it just gave me a C++ runtime error.
The old versions nerer crached on me, so that is realy strange that the new one crached
Well I switched back to the version that I used befor this one....just wanted to let you know^^
The old versions nerer crached on me, so that is realy strange that the new one crached
Well I switched back to the version that I used befor this one....just wanted to let you know^^
Okay, got a new version -
This should improve stabilty, but there will still be some glitches,
https://docs.google.com/file/d/0B-5Ax5kejTpMWGkxaFoxT19SWVk/edit?usp=sharing
It should also do improve multithreaded performance a good deal. The hash rate won't improve, but it cuts down on redundant hashing, so you should see a more blocks for multi-core mining.
This should improve stabilty, but there will still be some glitches,
https://docs.google.com/file/d/0B-5Ax5kejTpMWGkxaFoxT19SWVk/edit?usp=sharing
It should also do improve multithreaded performance a good deal. The hash rate won't improve, but it cuts down on redundant hashing, so you should see a more blocks for multi-core mining.
Great, thanks for your hard work.
I just installed it on both my multi-core machines so let's see if it survives the night without hanging (and hopefully solving some blocks).
I will report back tomorrow.
Whatever git pull pulls, which hopefully should be latest code unless someone is messing up the github repo as seems to have happened with litecoin. (Litecoin repo maintainer seems not to have made into main line some branch or other that the daemons are already saying they want used, fucked up situation...)
Basically with billions of coins out there the only way to know which ones have new code available is git pull in each source directory and see which pulls result in getting new code...
-MarkM-
Basically with billions of coins out there the only way to know which ones have new code available is git pull in each source directory and see which pulls result in getting new code...
-MarkM-
Ah okay - early on I had the latest source on a tree, so you were just getting a bitcoin 0.8.3 build.
I have been trying to find out what ports this thing uses but as far as I can tell it is unchanged bitcoin code?
It connects to the bitcoin network, on the bitcoin port, and maybe even uses the bitcoin network handshake to identify itself so it can pretend to be a bitcoin node and try to poison the bitcoin network with its hopefully incompatible blocks and in turn get all mucked up by being given bitcoin blocks by bitcoin nodes?
Or has the code been hacked in some nonstandard place to fix some of that that seems in the chain info stuff to be plain old bitcoin settings?
-MarkM-
It connects to the bitcoin network, on the bitcoin port, and maybe even uses the bitcoin network handshake to identify itself so it can pretend to be a bitcoin node and try to poison the bitcoin network with its hopefully incompatible blocks and in turn get all mucked up by being given bitcoin blocks by bitcoin nodes?
Or has the code been hacked in some nonstandard place to fix some of that that seems in the chain info stuff to be plain old bitcoin settings?
-MarkM-
Hi Mark,
Port 8555 - some of the old builds had some old bitcoin stuff left in accidentally, but that should all be cleared out now. Which build or source are you using?
Whatever git pull pulls, which hopefully should be latest code unless someone is messing up the github repo as seems to have happened with litecoin. (Litecoin repo maintainer seems not to have made into main line some branch or other that the daemons are already saying they want used, fucked up situation...)
Basically with billions of coins out there the only way to know which ones have new code available is git pull in each source directory and see which pulls result in getting new code...
-MarkM-
Today I have mined 4 blocks already (while in the past week I only mined 2)....could it be that I am on a forked chain? If so, what could I do to get on the right chain again and how would I save my mined MEG?
Thanks!!!
Thanks!!!
Dose any one have an idea how I could check if I am still on the right chain?
My miners are at block 1207 right now.
You can also use the blockchainexplorer posted a few post above this to see at what block your chain should be.
EDIT: Let's make it easy, here's the link: http://memorycoin.21stcenturymoneytalk.org/
Hey thanks a million!
Yes that is the same block I am on, so I guss every thing I mined today is for real! Wow that would be awsom
I have mined 144 coins today and have a total of 192
Can´t belive my luck 
Jump to: