Pythonideus (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 07:39:02 PM |
|
Today I, like many other pool owners, was quite excited for MoonCoin. It looked promising with its active IRC channel and populated thread. I was a bit annoyed by their announcement that multipool would be the only pool to receive early source, but figured it would only result in our pool being a little behind by compiling the source and we would be on a more or less even footing with the other pools. Instead, this happened: 12:30 : Developer locks chat, promotes multipool.us pool until launch 1 PM (original launch time) : Multipool.us is down, developer says he is delaying the launch for unrelated reasons (lol, k). 1:02 PM : Multipool.us back up, developer says launch is nearly ready. Seconds later multipool goes back down, developer says new launch is 1:10. Developer goes offline. 1:12 PM : Developer back online, multipool.us back up, developer says he left and delayed the launch because his home computer got DDOSed (lol, k). He says they are "working on it". 1:15 - 1:18 : Developers and pool owners spam the chat with such comments as "The coin is not being premined!" and "Still at block 0!" 1:19 : Developer says "It is up!" - referring to multipool.us 1:29 : Developers say multipool.us is undergoing a DDOS attack 1:30 PM : Developer announce source code 1:47 PM : Source actually released This is hilarious guys, wanna know why? http://moon.hackshard.com/BlockCrawler/index.php?block_hash=df6b464acdb02b1691fe664e0716dae50cbf9ae14539483c116c06df183e6be3This machine is an hour behind, but as you can see, the coin was clearly mined during the time that the developers were saying that no mining was occurring. There are other reasons that this ScamCoin is hilarious but I'll leave that for more eloquent posters than myself.
|
|
|
|
digicoin
Legendary
Offline
Activity: 1106
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 07:40:22 PM |
|
Yes, it is premined. The dev lies to us
|
|
|
|
|
iGotSpots
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 07:44:15 PM |
|
Even if it's not premined, you're still getting like 8% of the total coins EVER in the first 100k blocks
|
|
|
|
hsz
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 07:44:33 PM |
|
waitting....................
|
|
|
|
Pythonideus (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 07:44:40 PM |
|
Proof of timing ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2Fq1XQWij.png&t=665&c=TDZkMMaS_aOlcQ)
|
|
|
|
deaconboogie
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 07:44:50 PM |
|
Complete rubbish.
12:45 we locked the channel.
1PM we opened the port but the daemon kept crashing under the load.
1:12PM I got online again using another method because my cable modem was getting DDOS'd
1:15-1:19 - Yes, I got back on and from what I could see we were still at block 0. It was my understanding that the pool was still down.
1:29PM - Multipool still down/up with daemon finally getting stable.
1:30PM - We released the code because it was safe.
Not sure where the 1:47 thing came from... The source was released shortly after announcement was made.
If someone was able to mine a block before you in the middle of the bedlam, then that's the way it goes. With services crashing left and right, what do you expect?
|
Mooncoin: 2F4E859vh1ezhpdDnMZdcR4hS1gLn54ytf BTC: 18S8XiKvFVhw6avx9tB21EHd3gNgomBFCK
|
|
|
Dacm4n
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 07:47:17 PM |
|
Today I, like many other pool owners, was quite excited for MoonCoin. It looked promising with its active IRC channel and populated thread. I was a bit annoyed by their announcement that multipool would be the only pool to receive early source, but figured it would only result in our pool being a little behind by compiling the source and we would be on a more or less even footing with the other pools. Instead, this happened: 12:30 : Developer locks chat, promotes multipool.us pool until launch 1 PM (original launch time) : Multipool.us is down, developer says he is delaying the launch for unrelated reasons (lol, k). 1:02 PM : Multipool.us back up, developer says launch is nearly ready. Seconds later multipool goes back down, developer says new launch is 1:10. Developer goes offline. 1:12 PM : Developer back online, multipool.us back up, developer says he left and delayed the launch because his home computer got DDOSed (lol, k). He says they are "working on it". 1:15 - 1:18 : Developers and pool owners spam the chat with such comments as "The coin is not being premined!" and "Still at block 0!" 1:19 : Developer says "It is up!" - referring to multipool.us 1:29 : Developers say multipool.us is undergoing a DDOS attack 1:30 PM : Developer announce source code 1:47 PM : Source actually released This is hilarious guys, wanna know why? http://moon.hackshard.com/BlockCrawler/index.php?block_hash=df6b464acdb02b1691fe664e0716dae50cbf9ae14539483c116c06df183e6be3This machine is an hour behind, but as you can see, the coin was clearly mined during the time that the developers were saying that no mining was occurring. There are other reasons that this ScamCoin is hilarious but I'll leave that for more eloquent posters than myself. Almost all new coins created in the last year are scam coins.
|
|
|
|
Pythonideus (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 07:49:54 PM |
|
Complete rubbish.
12:45 we locked the channel.
1PM we opened the port but the daemon kept crashing under the load.
1:12PM I got online again using another method because my cable modem was getting DDOS'd
1:15-1:19 - Yes, I got back on and from what I could see we were still at block 0. It was my understanding that the pool was still down.
1:29PM - Multipool still down/up with daemon finally getting stable.
1:30PM - We released the code because it was safe.
Not sure where the 1:47 thing came from... The source was released shortly after announcement was made.
If someone was able to mine a block before you in the middle of the bedlam, then that's the way it goes. With services crashing left and right, what do you expect?
Explain this please ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2Fizvncgj.png&t=665&c=dOo0cu4LPyxQPQ)
|
|
|
|
BrewCrewFan
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 07:50:53 PM |
|
no windows -qt leaving many at the mercy of pools who all seem to have issues.
|
|
|
|
BrewCrewFan
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 07:52:42 PM |
|
Complete rubbish.
12:45 we locked the channel.
1PM we opened the port but the daemon kept crashing under the load.
1:12PM I got online again using another method because my cable modem was getting DDOS'd
1:15-1:19 - Yes, I got back on and from what I could see we were still at block 0. It was my understanding that the pool was still down.
1:29PM - Multipool still down/up with daemon finally getting stable.
1:30PM - We released the code because it was safe.
Not sure where the 1:47 thing came from... The source was released shortly after announcement was made.
If someone was able to mine a block before you in the middle of the bedlam, then that's the way it goes. With services crashing left and right, what do you expect?
I expect the option of being able to solo mine... but you did not give people that option by leaving out the other options in particular the windows -qt
|
|
|
|
Pythonideus (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 07:54:33 PM |
|
First block after source release ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2F8as9YUo.png&t=665&c=oEIUy8rOvhxrxQ)
|
|
|
|
|
Pythonideus (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 08:09:02 PM |
|
Well A. the time in both pictures is the same timezone, so it's irrelevant and B. it doesn't matter if he pre-announced it, that's still a scammy thing to do.
|
|
|
|
Pythonideus (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 08:11:08 PM |
|
Developer kicking people who call the coin a scam from IRC ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FxuL5FnI.png&t=665&c=J1ges9QFWRGBbA)
|
|
|
|
xocel
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 08:14:56 PM |
|
I was mining this on multipool before the source was up, as were many others. It was made clear multipool was going live as first part of launch, followed by the source. I also compiled mooncoin-qt the moment the source was available, without any hassle. (although it does need its branding fixed up).
Also, multipool didnt go live until after the announced launch time. I really don't see why everyone is complaining. The times everyone is looking at is in CST not EST, add an hour..
|
|
|
|
metalphreak
Newbie
Offline
Activity: 6
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 08:22:42 PM |
|
In Summary:
Multipool had the source code before 1pm. They had issues getting it going. The source code was delayed (I wonder why?)
~1:15 to ~1:45 the only mining going on was at multipool IF you could even connect. Approx 900 blocks mined in this period (multipool also guaranteed their fees from this...)
1:45pm source code finally available, other pools scramble to get it to compile (some have issues because the coding/mods to forked source is terribad)
By the time anyone else has a change, the difficulty jumps to 16.
I wonder why everyone is pissed off?
Want to launch a coin properly? Get the code working, ONLINE, before you set the launch date. Actually release it on time to everyone. The password protected zip/rar idea an hour or two before launch is a good one.
Also, the CST vs EST thing. Really? Is it that hard to understand? The screen shot shows CST ie 12:14pm. EST that is 1:14pm. This is still before the source code is released.
|
|
|
|
MisO69
Legendary
Offline
Activity: 1946
Merit: 1005
My mule don't like people laughing
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 08:24:44 PM |
|
Even if it's not premined, you're still getting like 8% of the total coins EVER in the first 100k blocks
That is a scam unto itself. New coins should payout crap for the first 10,000 blocks or so. Giving everyone ample time to get on and then start mining the real reward blocks. There is a new one coming out called Darkcoin that is going to take that approach. I just think the dev is relatively new to the scene and that one will be a flop as well.
|
|
|
|
Pythonideus (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 30, 2013, 08:26:12 PM |
|
I was mining this on multipool before the source was up, as were many others. It was made clear multipool was going live as first part of launch, followed by the source. I also compiled mooncoin-qt the moment the source was available, without any hassle. (although it does need its branding fixed up).
Also, multipool didnt go live until after the announced launch time. I really don't see why everyone is complaining. The times everyone is looking at is in CST not EST, add an hour..
Look. At. The. Minutes.
|
|
|
|
|
|