Topic: [ANN] [MΣC] Megacoin.co.nz - Forum, Github, Website Now in 18 Languages - page 178. (Read 330783 times)
August 02, 2013, 01:51:01 PM
Wow diff going down! Good!
August 02, 2013, 12:18:23 PM
Ugh - setting up bitcoin-abe filled up the drives - Moved to another drive with more space to take care of space concerns
August 02, 2013, 12:09:31 PM
9.6!
Looks like something is happening. I started receiving MEGA coins this morning, and the pace seems to be picking up. First incoming coins I've seen in 5 days. I don't see any new blocks confirmed (that I was involved in mining). I take that back, we just had one confirmed (mega.minepool.net). Hope we get some good news today.
August 02, 2013, 12:08:40 PM
Only a few more blocks till the next difficulty drop! Slowly getting there!
Any updates Kimoto?
Any updates Kimoto?
August 02, 2013, 10:41:09 AM
9.6!
August 02, 2013, 08:46:34 AM
having lots of different pools has no bearing on anything other than payouts (and perhaps public perception). The network is still going to find blocks at the same rate. Perhaps I pulled mine too early, though it hadn't found a block in days, nor had active miners. Personally, I always try to support pools that are supporting the coin...being here in the thread, active, discussing with miners ect. (And I try and be this kind of pool op for the coins I host).
I hope MEC can turn it around, whether I end up re-opening a pool for it or not. Good luck to those mining it. Its refreshing to see people standing behind a coin for the long term. Wish more did the same (whether mec or not)
I hope MEC can turn it around, whether I end up re-opening a pool for it or not. Good luck to those mining it. Its refreshing to see people standing behind a coin for the long term. Wish more did the same (whether mec or not)
August 02, 2013, 08:35:23 AM
I am having the same issue as MobGod during compiles - Ubuntu as well...but he's tested on multiple distros including Mint (I've been reading 
)
g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -I/home/gr33k/megacoin-0.8.994-source/src -I/home/gr33k/megacoin-0.8.994-source/src/obj -DUSE_IPV6=1 -I/home/gr33k/megacoin-0.8.994-source/src/leveldb/include -I/home/gr33k/megacoin-0.8.994-source/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2 -MMD -MF obj/newsmessage.d -o obj/newsmessage.o newsmessage.cpp
g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -I/home/gr33k/megacoin-0.8.994-source/src -I/home/gr33k/megacoin-0.8.994-source/src/obj -DUSE_IPV6=1 -I/home/gr33k/megacoin-0.8.994-source/src/leveldb/include -I/home/gr33k/megacoin-0.8.994-source/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2 -MMD -MF obj/sendalert.d -o obj/sendalert.o sendalert.cpp
sendalert.cpp: In member function ‘void CSendAlert::Test(std::string, std::string)’:
sendalert.cpp:63:18: error: ‘Sleep’ was not declared in this scope
make: *** [obj/sendalert.o] Error 1
make: *** Waiting for unfinished jobs...
**
I also see that we've been asking for fixed source code for a while - Any news or ETA?
Thank you - I really like MEC and have the most coins mined for this one - I'd love to see it working. Trying to setup a mining pool with mmcfe-ng
i had fixed that for myself opening that file and changing "Sleep" to "sleep" on that line. that will happen with several files )g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -I/home/gr33k/megacoin-0.8.994-source/src -I/home/gr33k/megacoin-0.8.994-source/src/obj -DUSE_IPV6=1 -I/home/gr33k/megacoin-0.8.994-source/src/leveldb/include -I/home/gr33k/megacoin-0.8.994-source/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2 -MMD -MF obj/newsmessage.d -o obj/newsmessage.o newsmessage.cpp
g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -I/home/gr33k/megacoin-0.8.994-source/src -I/home/gr33k/megacoin-0.8.994-source/src/obj -DUSE_IPV6=1 -I/home/gr33k/megacoin-0.8.994-source/src/leveldb/include -I/home/gr33k/megacoin-0.8.994-source/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2 -MMD -MF obj/sendalert.d -o obj/sendalert.o sendalert.cpp
sendalert.cpp: In member function ‘void CSendAlert::Test(std::string, std::string)’:
sendalert.cpp:63:18: error: ‘Sleep’ was not declared in this scope
make: *** [obj/sendalert.o] Error 1
make: *** Waiting for unfinished jobs...
**
I also see that we've been asking for fixed source code for a while - Any news or ETA?
Thank you - I really like MEC and have the most coins mined for this one - I'd love to see it working. Trying to setup a mining pool with mmcfe-ng
ZOMG case sensitive OS FTW -
Did this for sendalert.cpp and sendnews.cpp -
Change Sleep(500); to sleep(500);
Silly typo
Good catch - Thank you! It compiled finally - MobGod (and others) here is the likely fix for your compiling issue 
August 02, 2013, 05:13:58 AM
slowly to 10.154...
August 02, 2013, 03:21:41 AM
New MegaCoin mining pool up
http://gr33k.gotdns.org
Stratum, 1% pool fee, and just starting - Got one worker so far - Me
more details:
https://bitcointalksearch.org/topic/ann-new-megacoin-mining-pool-gr33kgotdnsorg-266577
http://gr33k.gotdns.org
Stratum, 1% pool fee, and just starting - Got one worker so far - Me
more details:
https://bitcointalksearch.org/topic/ann-new-megacoin-mining-pool-gr33kgotdnsorg-266577
My account is locked because I put in a fake email and apparently you need to activate through email. If you unlock my account and disable the email stuff I would put some hash there.
For those that weren't here earlier (or don't read all the posts) a few of us move from multipool to meg.smalltimeminer.com
I don't want to sound unappreciative of gr33k's efforts, but I think one problem this coin has is too many pools, and not enough hashing power. As it is, we have found quite a few blocks that may never be confirmed. I can't see moving to another pool and ending up in this situation again. I'm not trying to be pessimistic, and will do my best to help if we can come up with a plan to get this coin moving again.
This is incorrect, actually. There were plenty of people mining this coin before the reward was halved and the bottom fell out of it. A big part of the problem was that the only big pool that was up-and-running right before the crash was at multipool...and a lot of people who were mining MegaCoin over there decided to just switch to the multi port instead. As a result, when things hit the cliff, everybody instantly switched to mining something else. We're still recovering from this rollercoaster hash rate (which created the problem.)
Perhaps you weren't around before this issue, but network speed was over 1 GH/s at points. The slow network speed now is due to the fact that it's taking forever to get the difficulty down to a reasonable level. It's getting there slowly...but the addition of dedicated MegaCoin pools will help for sure. Also, an adjustment to the formula is still a requirement in my opinion. We're still not out of the woods yet...but we're getting there. I really don't want to deal with this again in 30 days (and I guarantee the exact same thing will happen if the formula stays the same.)
As Shellbunner will tell you, I was mining MEGA from day 1. I understand what you're saying about pre-block 42000 mining. The reward change at block 21k didn't cause any problems, so hopefully this is a fixable glitch. Yes the hash rate was growing bigger and bigger. I celebrated each peak with my friends, and we watched the tremendous growth in value. I believe the highest peak was 1.2 Gh/s and a market cap of almost $240k. What I meant was, I don't think we want our hashing power spread too thin. The pool I was in with half a dozen of my friends now solves 1 block about every 5 hours. There only 2 miners left in that pool, VR4mines, and Captn62, because I asked them to stay. We need fewer, and larger pools to get this thing kick-started again (my 2 cents, or should I say 2% of a MEGA). Once I recover some of the blocks I worked on in that pool, I would be happy to join gr33k's pool. Actually if we can come up with a plan to get us going, I'll join in now. I just hate to leave all those unfinished blocks behind, and I hope that pool survives. I feel pretty sure Kimoto will get the issue resolved, but I agree with your earlier post that this is a serious situation. I look at myself as a Crypto coin collector. I'm not in this to jump from pool to pool, and just mining the most profitable coins. I want to see more strong alternatives like Litecoin. Up until this brick wall of difficulty, I was pretty certain MEGA was going to be next major player.
V12AMG
Right -- I'm talking about after this issue is resolved and things are rolling again. Obviously a ton of pools right now is pointless unless there are people to fill them -- more pools isn't going to get us out of the situation. My top concern now is preventing this from happening again...as it would almost certainly be the end.
I'm not opting for people to go to TONS of pools
Come to mine 
- Also posting here to show the crypto-community that MegaCoin is still live and kicking!I'm confident that the good Doctor will update us in the near future with his updates
August 02, 2013, 02:57:11 AM
New MegaCoin mining pool up
http://gr33k.gotdns.org
Stratum, 1% pool fee, and just starting - Got one worker so far - Me
more details:
https://bitcointalksearch.org/topic/ann-new-megacoin-mining-pool-gr33kgotdnsorg-266577
http://gr33k.gotdns.org
Stratum, 1% pool fee, and just starting - Got one worker so far - Me
more details:
https://bitcointalksearch.org/topic/ann-new-megacoin-mining-pool-gr33kgotdnsorg-266577
My account is locked because I put in a fake email and apparently you need to activate through email. If you unlock my account and disable the email stuff I would put some hash there.
For those that weren't here earlier (or don't read all the posts) a few of us move from multipool to meg.smalltimeminer.com
I don't want to sound unappreciative of gr33k's efforts, but I think one problem this coin has is too many pools, and not enough hashing power. As it is, we have found quite a few blocks that may never be confirmed. I can't see moving to another pool and ending up in this situation again. I'm not trying to be pessimistic, and will do my best to help if we can come up with a plan to get this coin moving again.
This is incorrect, actually. There were plenty of people mining this coin before the reward was halved and the bottom fell out of it. A big part of the problem was that the only big pool that was up-and-running right before the crash was at multipool...and a lot of people who were mining MegaCoin over there decided to just switch to the multi port instead. As a result, when things hit the cliff, everybody instantly switched to mining something else. We're still recovering from this rollercoaster hash rate (which created the problem.)
Perhaps you weren't around before this issue, but network speed was over 1 GH/s at points. The slow network speed now is due to the fact that it's taking forever to get the difficulty down to a reasonable level. It's getting there slowly...but the addition of dedicated MegaCoin pools will help for sure. Also, an adjustment to the formula is still a requirement in my opinion. We're still not out of the woods yet...but we're getting there. I really don't want to deal with this again in 30 days (and I guarantee the exact same thing will happen if the formula stays the same.)
As Shellbunner will tell you, I was mining MEGA from day 1. I understand what you're saying about pre-block 42000 mining. The reward change at block 21k didn't cause any problems, so hopefully this is a fixable glitch. Yes the hash rate was growing bigger and bigger. I celebrated each peak with my friends, and we watched the tremendous growth in value. I believe the highest peak was 1.2 Gh/s and a market cap of almost $240k. What I meant was, I don't think we want our hashing power spread too thin. The pool I was in with half a dozen of my friends now solves 1 block about every 5 hours. There only 2 miners left in that pool, VR4mines, and Captn62, because I asked them to stay. We need fewer, and larger pools to get this thing kick-started again (my 2 cents, or should I say 2% of a MEGA). Once I recover some of the blocks I worked on in that pool, I would be happy to join gr33k's pool. Actually if we can come up with a plan to get us going, I'll join in now. I just hate to leave all those unfinished blocks behind, and I hope that pool survives. I feel pretty sure Kimoto will get the issue resolved, but I agree with your earlier post that this is a serious situation. I look at myself as a Crypto coin collector. I'm not in this to jump from pool to pool, and just mining the most profitable coins. I want to see more strong alternatives like Litecoin. Up until this brick wall of difficulty, I was pretty certain MEGA was going to be next major player.
V12AMG
Right -- I'm talking about after this issue is resolved and things are rolling again. Obviously a ton of pools right now is pointless unless there are people to fill them -- more pools isn't going to get us out of the situation. My top concern now is preventing this from happening again...as it would almost certainly be the end.
August 02, 2013, 02:49:46 AM
Ok - I've fixed the mail server, and set the blocks from 50 to 125 since that's the going block reward. Everything appears to be running smoothly.
My block stats right now are:
Next Network Block 42271 (Current: 42270)
(12:49 AM - PST)
Port 3333 is open and external connections have been confirmed to be working by both myself and ALIEN (thanx bro!)
I'm working on a blockexplorer using bitcoin-abe for Megacoin and Cosmoscoin.
If you experience a bit of sluggishness - That's the block index populating MySQL. It will be over...well it's taking forever so far (4+ hours)...but hopefully soon!
Suggestions and/or recommendations are appreciated
My block stats right now are:
Next Network Block 42271 (Current: 42270)
(12:49 AM - PST)
Port 3333 is open and external connections have been confirmed to be working by both myself and ALIEN (thanx bro!)
I'm working on a blockexplorer using bitcoin-abe for Megacoin and Cosmoscoin.
If you experience a bit of sluggishness - That's the block index populating MySQL. It will be over...well it's taking forever so far (4+ hours)...but hopefully soon!
Suggestions and/or recommendations are appreciated
August 02, 2013, 02:03:46 AM
New MegaCoin mining pool up
http://gr33k.gotdns.org
Stratum, 1% pool fee, and just starting - Got one worker so far - Me
more details:
https://bitcointalksearch.org/topic/ann-new-megacoin-mining-pool-gr33kgotdnsorg-266577
http://gr33k.gotdns.org
Stratum, 1% pool fee, and just starting - Got one worker so far - Me
more details:
https://bitcointalksearch.org/topic/ann-new-megacoin-mining-pool-gr33kgotdnsorg-266577
My account is locked because I put in a fake email and apparently you need to activate through email. If you unlock my account and disable the email stuff I would put some hash there.
For those that weren't here earlier (or don't read all the posts) a few of us move from multipool to meg.smalltimeminer.com
I don't want to sound unappreciative of gr33k's efforts, but I think one problem this coin has is too many pools, and not enough hashing power. As it is, we have found quite a few blocks that may never be confirmed. I can't see moving to another pool and ending up in this situation again. I'm not trying to be pessimistic, and will do my best to help if we can come up with a plan to get this coin moving again.
This is incorrect, actually. There were plenty of people mining this coin before the reward was halved and the bottom fell out of it. A big part of the problem was that the only big pool that was up-and-running right before the crash was at multipool...and a lot of people who were mining MegaCoin over there decided to just switch to the multi port instead. As a result, when things hit the cliff, everybody instantly switched to mining something else. We're still recovering from this rollercoaster hash rate (which created the problem.)
Perhaps you weren't around before this issue, but network speed was over 1 GH/s at points. The slow network speed now is due to the fact that it's taking forever to get the difficulty down to a reasonable level. It's getting there slowly...but the addition of dedicated MegaCoin pools will help for sure. Also, an adjustment to the formula is still a requirement in my opinion. We're still not out of the woods yet...but we're getting there. I really don't want to deal with this again in 30 days (and I guarantee the exact same thing will happen if the formula stays the same.)
As Shellbunner will tell you, I was mining MEGA from day 1. I understand what you're saying about pre-block 42000 mining. The reward change at block 21k didn't cause any problems, so hopefully this is a fixable glitch. Yes the hash rate was growing bigger and bigger. I celebrated each peak with my friends, and we watched the tremendous growth in value. I believe the highest peak was 1.2 Gh/s and a market cap of almost $240k. What I meant was, I don't think we want our hashing power spread too thin. The pool I was in with half a dozen of my friends now solves 1 block about every 5 hours. There only 2 miners left in that pool, VR4mines, and Captn62, because I asked them to stay. We need fewer, and larger pools to get this thing kick-started again (my 2 cents, or should I say 2% of a MEGA). Once I recover some of the blocks I worked on in that pool, I would be happy to join gr33k's pool. Actually if we can come up with a plan to get us going, I'll join in now. I just hate to leave all those unfinished blocks behind, and I hope that pool survives. I feel pretty sure Kimoto will get the issue resolved, but I agree with your earlier post that this is a serious situation. I look at myself as a Crypto coin collector. I'm not in this to jump from pool to pool, and just mining the most profitable coins. I want to see more strong alternatives like Litecoin. Up until this brick wall of difficulty, I was pretty certain MEGA was going to be next major player.
V12AMG
August 02, 2013, 01:39:52 AM
August 02, 2013, 01:39:41 AM
Hmm i checked some other pools and they are on the same block as I am it seems right now 
I also noticed that the block reward is still at 50 - working on setting that to the current block reward of 125 - hopefully
I also noticed that the block reward is still at 50 - working on setting that to the current block reward of 125 - hopefully
August 02, 2013, 01:15:57 AM
diff: down to 10.712
August 02, 2013, 12:43:55 AM
I am building bitcoin-abe on a screen in the background - I wonder if this is causing the delay?
Hmm - Other than deleting the block index and having megacoind rebuild it - anything else I can do to catch up? there a rebuild index command too. Though it's unclear to me WHY i'm actually behind
Hmm - Other than deleting the block index and having megacoind rebuild it - anything else I can do to catch up? there a rebuild index command too. Though it's unclear to me WHY i'm actually behind
August 02, 2013, 12:39:54 AM
MEC is now back over BTC in profitability at least!
by a hair..
Code:
100.69%
by a hair..
August 02, 2013, 12:36:56 AM
ALIEN - I see you're on there tearing it up with almost about 850KH/s 
Nice man Hope this pool takes off! Thank you very much for helping test this bad boy out
Nice man
Hope this pool takes off! Thank you very much for helping test this bad boy out I moved that hash off because it says you are on block 42262 but the network is on 42264
August 02, 2013, 12:35:23 AM
ALIEN - I see you're on there tearing it up with almost about 850KH/s
Nice man Hope this pool takes off! Thank you very much for helping test this bad boy out
Nice man
Hope this pool takes off! Thank you very much for helping test this bad boy out August 02, 2013, 12:14:17 AM
Doh - Firewall issue - Changed port to 3333 at some point during testing but hadn't updated firewall rules. Sorry! Fixed
Jump to: