Topic: [ANN] [MΣC] Megacoin.co.nz - Forum, Github, Website Now in 18 Languages - page 135. (Read 330769 times)
September 13, 2013, 01:26:39 PM
11 blocks to go!
September 13, 2013, 01:16:34 PM
15 more blocks 
September 13, 2013, 01:08:48 PM
Dr. Kimoto Kun! I've noticed megacoin.co.nz hasn't updated the clients in its downloads section
September 13, 2013, 12:58:33 PM
Mining has been amazing so far today. I solo mined 6 blocks in 1.5 hours this morning with my 1800 K/hash.
September 13, 2013, 12:04:36 PM
Pool Hashrate 33 Mh/s vs. Network Hashrate 4,71 mh/s. Diff now 0.52.
...strange, if this is just a lag, its maybe its maybe ok and we just have to wait.
...strange, if this is just a lag, its maybe its maybe ok and we just have to wait.
Yes, a little bit concerning.. Want to see that network hashrate and difficulty stabilise pretty soon.
But in the meantime the blocks are coming in thick and fast
Could be after effect / lag from when mining was temporarily stopped - there was something like 6 blocks mined in 6 hours before the new client was released..
I have a possible theory. Not sure what time the fix went in, but I was mining all night. I noticed my wallet had a ton of unconfirmed payments. As soon as I installed the new client they caught up. Maybe this has something to do with the reported lag? Could be quite a few miners that haven't updated yet. In fact, I know half the people in your pool, and none of them have the new client yet.
Looks like it has stabilised - network hashrate and difficulty have risen...
Yep, starting to look good. Should be quite a day for Megacoin. Only about 50 blocks to go before we hit the reduction.
Info on coinchoose and coinwarz is still old. I suspect as soon as it updates we are going to get our smoke test from the multipool.
September 13, 2013, 11:54:03 AM
Pool Hashrate 33 Mh/s vs. Network Hashrate 4,71 mh/s. Diff now 0.52.
...strange, if this is just a lag, its maybe its maybe ok and we just have to wait.
...strange, if this is just a lag, its maybe its maybe ok and we just have to wait.
Yes, a little bit concerning.. Want to see that network hashrate and difficulty stabilise pretty soon.
But in the meantime the blocks are coming in thick and fast
Could be after effect / lag from when mining was temporarily stopped - there was something like 6 blocks mined in 6 hours before the new client was released..
I have a possible theory. Not sure what time the fix went in, but I was mining all night. I noticed my wallet had a ton of unconfirmed payments. As soon as I installed the new client they caught up. Maybe this has something to do with the reported lag? Could be quite a few miners that haven't updated yet. In fact, I know half the people in your pool, and none of them have the new client yet.
Looks like it has stabilised - network hashrate and difficulty have risen...
September 13, 2013, 11:50:06 AM
I will just repost some of my findings from the multipool thread from yesterday.
As I understand it, the algorithm works like this:
Next Diff = (Average Diff over the last N blocks) * (150 seconds) * N / (Actual Seconds for last N blocks)
where N is a number between 144 and 4032.
The "clever" part is that N gets smaller when the diff changes quickly and N gets larger when the diff is stable. The idea would be that when there is a quick change in hash rate, it reacts quickly. When the hash rate is stable, it reacts slowly.
The problem is the first part of the algorithm has momentum. This is one of the things that caused so much trouble with the transition at block 42,000. Even after the MP switched off around block 42130, the difficulty kept climbing for about 70 more blocks (which took 2 days).
For example, if N is 144 and the coin-hoppers mine a fast 50 coins and switch off the coin, those coins will still be counted in the average used for the next difficulty while the faithful have to grind on 94 coins themselves.
The change in direction will also increase N, causing the permitted change to be smaller, and allowing those 50 fast-mined coins to linger even longer, forcing the faithful miners to spend even more time trying to create even more blocks necessary to bring difficulty back down.
The idea was clever, but not practically applied. If instead of using block counts for PastBlockMin and PastBlockMax, he had used Time (i.e. PastSecondsMin and PastSecondsMax), then used blocks/hour instead of hours (seconds) per block for the calculation. That way if the coin slows down to 2-4 blocks per hour, it doesn't take days of grinding to get the 50-100 blocks needed to push the fast blocks out of the window of consideration.
Hopefully, I am wrong and it stays profitable to mine for the faithful and keeps producing blocks. Unfortunately, I think that every time it gets marginally profitable to mine, MP, MC and CC will slap it down and create problem like it had with block 42,000 where transactions don't confirm and 2 guys are stuck mining it for days waiting for it to recover, only to get slapped down and have to repeat the cycle.
To give some real numbers, last night, when middlecoin, multipool, and coinchoose were off mec, it took 16 hours to generate 60 blocks, about half of what would be required to push fast block out of the minimum 144 block consideration window. That was with a descent profitability. If profitability drops to a very undesirable level, like around block 42159-42219, mining 60 blocks took 3.5 days.Next Diff = (Average Diff over the last N blocks) * (150 seconds) * N / (Actual Seconds for last N blocks)
where N is a number between 144 and 4032.
The "clever" part is that N gets smaller when the diff changes quickly and N gets larger when the diff is stable. The idea would be that when there is a quick change in hash rate, it reacts quickly. When the hash rate is stable, it reacts slowly.
The problem is the first part of the algorithm has momentum. This is one of the things that caused so much trouble with the transition at block 42,000. Even after the MP switched off around block 42130, the difficulty kept climbing for about 70 more blocks (which took 2 days).
For example, if N is 144 and the coin-hoppers mine a fast 50 coins and switch off the coin, those coins will still be counted in the average used for the next difficulty while the faithful have to grind on 94 coins themselves.
The change in direction will also increase N, causing the permitted change to be smaller, and allowing those 50 fast-mined coins to linger even longer, forcing the faithful miners to spend even more time trying to create even more blocks necessary to bring difficulty back down.
The idea was clever, but not practically applied. If instead of using block counts for PastBlockMin and PastBlockMax, he had used Time (i.e. PastSecondsMin and PastSecondsMax), then used blocks/hour instead of hours (seconds) per block for the calculation. That way if the coin slows down to 2-4 blocks per hour, it doesn't take days of grinding to get the 50-100 blocks needed to push the fast blocks out of the window of consideration.
Hopefully, I am wrong and it stays profitable to mine for the faithful and keeps producing blocks. Unfortunately, I think that every time it gets marginally profitable to mine, MP, MC and CC will slap it down and create problem like it had with block 42,000 where transactions don't confirm and 2 guys are stuck mining it for days waiting for it to recover, only to get slapped down and have to repeat the cycle.
Your math is off if that's the conclusion you are coming to. Obviously we'll see how it plays out in production...but to me it seems like a smart formula that will adapt well while also keeping things more consistent and under control. There might be some slow blocks still in there...but as soon as they're found the difficulty will start to plunge rapidly.
Anyway, the die is cast, and we will all start finding out tomorrow. Hopefully, Friday the 13th is not unlucky for MEC.
Not trying to rub any salt here, but I predicted this long ago. Here is that train wreck I was talking about... http://forum.feathercoin.com/index.php?topic=3673.0
September 13, 2013, 11:37:22 AM
Pool Hashrate 33 Mh/s vs. Network Hashrate 4,71 mh/s. Diff now 0.52.
...strange, if this is just a lag, its maybe its maybe ok and we just have to wait.
...strange, if this is just a lag, its maybe its maybe ok and we just have to wait.
Yes, a little bit concerning.. Want to see that network hashrate and difficulty stabilise pretty soon.
But in the meantime the blocks are coming in thick and fast
Could be after effect / lag from when mining was temporarily stopped - there was something like 6 blocks mined in 6 hours before the new client was released..
I have a possible theory. Not sure what time the fix went in, but I was mining all night. I noticed my wallet had a ton of unconfirmed payments. As soon as I installed the new client they caught up. Maybe this has something to do with the reported lag? Could be quite a few miners that haven't updated yet. In fact, I know half the people in your pool, and none of them have the new client yet.
September 13, 2013, 11:25:17 AM
Pool Hashrate 33 Mh/s vs. Network Hashrate 4,71 mh/s. Diff now 0.52.
...strange, if this is just a lag, its maybe its maybe ok and we just have to wait.
...strange, if this is just a lag, its maybe its maybe ok and we just have to wait.
Yes, a little bit concerning.. Want to see that network hashrate and difficulty stabilise pretty soon.
But in the meantime the blocks are coming in thick and fast
Could be after effect / lag from when mining was temporarily stopped - there was something like 6 blocks mined in 6 hours before the new client was released..
September 13, 2013, 11:21:07 AM
Proposal to MEC community... never again do we let MEC price fall below 1 penny/MEC (its currently at .009 usd). Today we pass DGC in current market cap!
But let me demonstrate how undervalued MEC is:
MEC future forward marketcap = 42M X .009 = $378,000
DGC future forwward market cap = 200M X .019 = $3,800,000
Do you understand what this means?
OKIEs prediction DGC adds a decimal place and MEC loses a decimal place in the very near future!
http://coinmarketcap.com/
But let me demonstrate how undervalued MEC is:
MEC future forward marketcap = 42M X .009 = $378,000
DGC future forwward market cap = 200M X .019 = $3,800,000
Do you understand what this means?
OKIEs prediction DGC adds a decimal place and MEC loses a decimal place in the very near future!
http://coinmarketcap.com/
September 13, 2013, 11:14:14 AM
Lets get mec back on cryptsy, this sucks big time
It sucks big time? Now isn't a great time to sell - the price will steadily move up if you wait. Or, if all you want to do is look at it, just be patient, man -- I promise Cryptsy didn't steal your MEC and skip town. It will be back soon and attacked hard by the multi-miners right away.
It's not because I want to sell, i just need a market price for calculations and I only have half the amount of MEC that I want. We need block explorer fixed to BTW
September 13, 2013, 11:10:42 AM
Pool Hashrate 33 Mh/s vs. Network Hashrate 4,71 mh/s. Diff now 0.52.
...strange, if this is just a lag, its maybe its maybe ok and we just have to wait.
...strange, if this is just a lag, its maybe its maybe ok and we just have to wait.
September 13, 2013, 11:09:55 AM
Diff down to 0.63 here. ist that a little low?
My thoughts as well, been watching it fall, reported network hashrate is quite low.
The lag in the client reported network hash rate, which I have commented on many times in the past, I agree is the culprit. The new diff adjustment must be based on the reported hash rate which could be an issue.
Code:
Pool Hashrate 33.647 MH/s
Network Hashrate 4.71 MH/s
Network Hashrate 4.71 MH/s
September 13, 2013, 11:07:21 AM
Diff down to 0.63 here. ist that a little low?
My thoughts as well, been watching it fall, reported network hashrate is quite low.
September 13, 2013, 11:06:48 AM
Just uploaded these, upped the version. Good to start mining again with 996. Let me know if they download and install fine.
http://sourceforge.net/projects/megacoin/files/megacoin-0.8.996-win32-setup.exe/download
http://sourceforge.net/projects/megacoin/files/megacoin-0.8.996-source.zip/download
Better if you (re)move peers.dat before first run.
Any way you could put the source in github?
September 13, 2013, 11:01:59 AM
Diff down to 0.63 here. isn't that a little low?
September 13, 2013, 10:59:06 AM
Lets get mec back on cryptsy, this sucks big time
It sucks big time? Now isn't a great time to sell - the price will steadily move up if you wait. Or, if all you want to do is look at it, just be patient, man -- I promise Cryptsy didn't steal your MEC and skip town. It will be back soon and attacked hard by the multi-miners right away.
September 13, 2013, 10:45:24 AM
Lets get mec back on cryptsy, this sucks big time
September 13, 2013, 10:15:24 AM
no price update = no multipool! I say shhhh until after the reward reduction. Mining is very good right now.
September 13, 2013, 09:41:22 AM
Has Kimoto talked with cryptsy yet, i miss my precious MEC, I have big time anxiety until all my coin come back!
Jump to: