Just got a message saying: "Warning: Displayed transactions may not be correct! You may need to upgrade or other nods may need to upgrade."
I am using the latest release....any Idear what that could mean?
Topic: [ANN] MemoryCoin - page 27. (Read 100338 times)
I can't connect. Any nodes?
Been mining two i7 HP laptops for 24 hours with ZERO ISSUES = 14 hash/sec = 4 blocks mined.
If the 14 hash/sec is for the 2 machines combined then it's normal to have no issues (7 hash per machine).
I have one 2-core celeron 2.6Ghz mining at 4.5 hash/sec and it hardly ever crashes or hangs.
On the other hand, my 6-core i7 extreme at 4.5Ghz does 26 hash/sec but hangs or crashes every few blocks
(no, it's not the overclocking)I have found that any of my > 4 core machines that if I limit the hash on them to half of the physical cores (I have some 8 core Xeons E5's that I run just on 4 cores) I run stable 24x7, it's when I go over half of their cores that they start to hang on blocks. Just an FYI.
Been mining two i7 HP laptops for 24 hours with ZERO ISSUES = 14 hash/sec = 4 blocks mined.
If the 14 hash/sec is for the 2 machines combined then it's normal to have no issues (7 hash per machine).
I have one 2-core celeron 2.6Ghz mining at 4.5 hash/sec and it hardly ever crashes or hangs.
On the other hand, my 6-core i7 extreme at 4.5Ghz does 26 hash/sec but hangs or crashes every few blocks
(no, it's not the overclocking) Did you read my post on the previous page about some cores that keep on mining while another core is changing the data to move to the next block? I honestly think this is where things go wrong.
Thanks, yes. Gradually working my way through a number of different possibilities.
I seem to be stuck updating at block 1744
Any help?
Any help?
Delete your blockchain and start again. This worked for me on one machine that was stuck on block 1745.
Be careful not to delete your wallet.dat !!!
Try a simple restart first. If that doesn't work, try a re-index start, if that doesn't work, delete your blockchain and restart.
I seem to be stuck updating at block 1744
Any help?
Any help?
Delete your blockchain and start again. This worked for me on one machine that was stuck on block 1745.
Be careful not to delete your wallet.dat !!!
I seem to be stuck updating at block 1744
Any help?
Any help?
Update - should offer improved stability -
https://docs.google.com/file/d/0B-5Ax5kejTpMdzVES0ZPSDVna2c/edit?usp=sharing
There are two sources of instability -
a) one in the grant award code which I think is a subtle memory corruption issue, and might cause program crashes. This error is likely to manifest around blocks divisible by 20.
b) the other is related to the hashing code. This might be related to hardware - MemoryCoin is trying to push the L2, L3 and main memory bus to the max, any weakness there could be reflected in a hard system crash requiring restart. This error is likely to manifest when mining.
This update addresses the first issue. It should offer a significant improvement, but not a complete fix.
https://docs.google.com/file/d/0B-5Ax5kejTpMdzVES0ZPSDVna2c/edit?usp=sharing
There are two sources of instability -
a) one in the grant award code which I think is a subtle memory corruption issue, and might cause program crashes. This error is likely to manifest around blocks divisible by 20.
b) the other is related to the hashing code. This might be related to hardware - MemoryCoin is trying to push the L2, L3 and main memory bus to the max, any weakness there could be reflected in a hard system crash requiring restart. This error is likely to manifest when mining.
This update addresses the first issue. It should offer a significant improvement, but not a complete fix.
One of my machines got stuck on block 1770 with this version so there are still some bugs te be worked out. (as you mentioned yourself).
Did you read my post on the previous page about some cores that keep on mining while another core is changing the data to move to the next block? I honestly think this is where things go wrong.
for solo mining , i only have to full sync my client and type setgenerate rate true,
Yes, that's all you need to do. - command is
setgenerate true
and after a few minutes, you can check your hashespersec by typing
getmininginfo
for solo mining , i only have to full sync my client and type setgenerate rate true, or i have to setup a .conf file ?
This coin only CPU mining ？
This coin is designed to be GPU resistant. Once we get onto an exchange and the coin has some value, The MemoryCoin Foundation might look at offering a (Bitcoin) prize to anyone who can create a more efficient GPU miner.
Update - should offer improved stability -
https://docs.google.com/file/d/0B-5Ax5kejTpMdzVES0ZPSDVna2c/edit?usp=sharing
There are two sources of instability -
a) one in the grant award code which I think is a subtle memory corruption issue, and might cause program crashes. This error is likely to manifest around blocks divisible by 20.
b) the other is related to the hashing code. This might be related to hardware - MemoryCoin is trying to push the L2, L3 and main memory bus to the max, any weakness there could be reflected in a hard system crash requiring restart. This error is likely to manifest when mining.
This update addresses the first issue. It should offer a significant improvement, but not a complete fix.
https://docs.google.com/file/d/0B-5Ax5kejTpMdzVES0ZPSDVna2c/edit?usp=sharing
There are two sources of instability -
a) one in the grant award code which I think is a subtle memory corruption issue, and might cause program crashes. This error is likely to manifest around blocks divisible by 20.
b) the other is related to the hashing code. This might be related to hardware - MemoryCoin is trying to push the L2, L3 and main memory bus to the max, any weakness there could be reflected in a hard system crash requiring restart. This error is likely to manifest when mining.
This update addresses the first issue. It should offer a significant improvement, but not a complete fix.
Is there any way to get an estimate of network hashrate?
The apparent network hashrate for block 1725 was ~1.996 KH/s.
(2^32 * d) / s
d is block difficulty
s is number of seconds it took to find the block
CPU
this coin for cpu or gpu? or both?
block reward became 22.8 MEG
Thanks to everybody who's supported the coin so far, and especially to those who have helped to see it through this fork.
I'd like to see a period of stability for the coin, and I'll be giving priority to issues to do with network and client stability for now.
I've also set up a voting address to receive funds to directly support my development efforts. It is separate from the MC Foundation address whose funds I'll direct to support other developers and projects.
So please consider voting for the following addresses to best support the coin.
1. MVTEoEo5LgYAMVh95oBBfGPj2eCDzkuJC3 (FreeTrade Dev)
2. MVTEoEomFfe7WuSEepMLsorgYzCQGBVw1z (21st Century, Network and Clients)
3. MVTEoEoXmYzFydRfg5uNJRewt9tZ329fAN (MemoryCoin Foundation)
4. MVTEoEoJ1vP6NHHcCTTBPy4bXfejbAqV5N (EFF - Charity)
5. MVTEoEorLyJKdtGFXfFTt3Joevk7PeRvzh (Amnesty International - Charity)
I'd like to see a period of stability for the coin, and I'll be giving priority to issues to do with network and client stability for now.
I've also set up a voting address to receive funds to directly support my development efforts. It is separate from the MC Foundation address whose funds I'll direct to support other developers and projects.
So please consider voting for the following addresses to best support the coin.
1. MVTEoEo5LgYAMVh95oBBfGPj2eCDzkuJC3 (FreeTrade Dev)
2. MVTEoEomFfe7WuSEepMLsorgYzCQGBVw1z (21st Century, Network and Clients)
3. MVTEoEoXmYzFydRfg5uNJRewt9tZ329fAN (MemoryCoin Foundation)
4. MVTEoEoJ1vP6NHHcCTTBPy4bXfejbAqV5N (EFF - Charity)
5. MVTEoEorLyJKdtGFXfFTt3Joevk7PeRvzh (Amnesty International - Charity)
Here's the current balances and voting preferences -
http://21stcenturymoneytalk.org/index.php/topic,32.0.html
http://21stcenturymoneytalk.org/index.php/topic,32.0.html
Jump to: