[ANN][MOON] Mooncoin: You know where it's headed! KGW exploit FIXED 4/3/2014

[gjhiggins]

According to gjhiggins, it is a ported version of Litecoin with the latest updates (OpenSSL-fix etc.). We would have to ask him for details. Btw: you can then change back the coin-icon to the original one immediately as you like, since the other one is only a suggestion by Graham and he already stated, that he is out of the project, regarding active work on the code. He just wanted to provide a good new starting point for the community, after deaconboogie seemed to be so unreliable.

Precisely so.

There has been an unfortunate tendency for (forked/cloned) altcoins to be released with a code repository that (for some unfathomable reason) discards all the prior commit history, i.e. all the sequential detailed changes made to the parent coin, back from its inception right up to the point when it is forked to create the new altcoin. One extremely important consequence of this decision to excise the commit history is that it effectively prevents the newly-forked code from benefiting from any enhancements or bug fixes made to the parent after it was forked.

With “normal” git (revision control) practice, you create a fork of the original repository code. The technically accurate term is “fork” but the actual command borrows misleadingly and uselessly from genetics:
git clone <repos_url>
You can then work completely separately on the forked code (say, making a few improvements or correcting a typo). At the end of the effort, you have a complete copy of the original, plus your changes. Assuming you have write access to the git repository from which you forked the code, you can simply commit the lot to the repos and that's the job done. Typically, unless you're a member of the development team, you won't have write access to a repository, instead you can submit a “pull request” to the repos admin, indicating that you have made specific changes. If your PR is acceptable, git allows the devs to integrate it very, very simply by merging your acceptably-changed copy of the code into the master.

But what happens if the original repos content is changed while you're still working? Your copy is now out of date and your PR will be rejected. The standard means of keeping your working copy up to date with changes to the master repository is to pull the changes from the repos and merge them into your copy with
git pull; git merge.

This is exactly how it could work with, say, Dogecoin and Mooncoin (the latter being a fork of the former). Bugs discovered and fixed in the parent Dogecoin repos could be merged into the Mooncoin code, enhancements and improvements to the Dogecoin code could be propagated to the Mooncoin code fairly simply (with thanks and due consideration) by merging. So, releasing a coin with a repos that cannot be used to merge bugfixes and improvements from the parent coin is a seriously retrograde step and will create a strong reliance on a capable dev who can migrate desirable changes in the Dogecoin code to the Mooncoin code.

I'll just vary the binding in the above para:

This is exactly how it could work with, say, Litecoin and Mooncoin (the latter being an indirect fork of the former). Bugs discovered and fixed in the parent Litecoin repos could be merged into the Mooncoin code, enhancements and improvements to the Litecoin code could be propagated to the Mooncoin code fairly simply (with thanks and due consideration) by merging. So, releasing a coin with a repos that cannot be used to merge bugfixes and improvements from the parent coin is a seriously retrograde step and will create a strong reliance on a capable dev who can migrate desirable changes in the Litecoin code to the Mooncoin code.

Mooncoin was launched as a fork of Litecoin 0.6.3 (as was Dogecoin). In late Feb, the extant Mooncoin 0.6.3 repos was overwritten completely with an upgrade of Mooncoin code to match code in the Litecoin 0.8.6 repos.

I took this code-dump and integrated it back in to a fork of Litecoin 0.8.6 with a full commit history:

https://github.com/mooncoin-project/mooncoin-landann/commits/mooncoin?page=2

The commit history now records in faithful detail, step-by-step, the process of going from recent Litecoin to latest Mooncoin and allows Litecoin upgrades (e.g. 0.8.6 -> 0.8.7) to be straightforwardly merged in to the Mooncoin code.

If Mooncoin follows Dogecoin to Bitcoin 0.9.2 (I strongly recommend this), then the above code is irrelevant, it all needs to be done again because there is no straightforward merge path from Litecoin 0.8.x to Bitcoin 0.9.X. However, the 0.8.6 commit history contains all the details of the path that was trodden previously.

I considered that to be the most effective contribution I could achieve without actually supplanting the official dev.

Cheers

Graham

[secbul]

There is a dev here : soopy452000

I saw that he RE-SURRECT GRW coin. (GRW coin was near dead)
As read the post, he/she knows what to do. This is an example of course.

https://bitcointalk.org/index.php?topic=469464.0

[coinflow]

There is a dev here : soopy452000

I saw that he RE-SURRECT GRW coin. (GRW coin was near dead)
As read the post, he/she knows what to do. This is an example of course.

https://bitcointalk.org/index.php?topic=469464.0

If I read it correctly, soopy452000 was the original dev who handed the coin over to unick. See their new thread here:
https://bitcointalk.org/index.php?topic=641241.0

Something like that would be ideal. Deaconboogie should do the same, if he doesn't want or cannot care for MOON in a reasonable manner.
We could then include an information here in the first posting and on reddit, that a new developer or development-team took over, so everyone who is interested (and/or does not read the whole thread nor even the latest postings) immediately knows, what's going on and will be forwarded to the right place to get correct information, Edit: instead of being confronted with incorrect/outdated and or missing data, like it is now here in the first posting and on reddit.

[redjedievolution]

big buys on cryptsy, jumped to 5 litoshi 
and yes... im not... 

[peme]

big buys on cryptsy, jumped to 5 litoshi 
and yes... im not... 

  nice.

Secure Mooncoin web wallet, also for mobile devices at:
http://www.coinspot.com.au now added at mooncoin.rocks :  http://mooncoin.rocks/web-wallet/

[redjedievolution]

another 400millions bought at 6 litoshi.


DEFINITIVELY THIS IS THE BEST MOMENT TO BUY IN... LAST OPORTUNITY WAS 2 WEEKS AGO WHICH WE WAS AT 4-5 LITOSHI, RIGHT NOW YOU ONLY CAN BUY AT 6 AND THE ASK IS GETTING BURNED FAST!!!!!


YIIIHAAAAAAAAAAAAAAAAAAAAA


TO THE MOOOOOONNNNNNNN

[agswinner]

Thank you Peme for add coinspot web wallet on mooncoin.rocks! This mobile multi wallet is Super sicure (2FA).
https://www.coinspot.com.au/

I asked to set an option to scan  qr code.

[peme]

I have finished the Mooncoin section.  It will be in the book called Cryptocurrency "The Alt-ernative" (A historical reference book).  Here is the preliminary cover (a better cover is currently being worked on):



The plan is to get the book published before Christmas 2014.  

Here is the Mooncoin preview section:

https://i.imgur.com/rjAp96D.png

Any donations towards this future publication are highly welcome.  I would love to see this book become a reality.  

2THQ74iskgoTXSWEEZZ9R1tkFa9575aDhu


Main Book Bitcointalk.org Thread is:

https://bitcointalk.org/index.php?topic=483187.0

Any further points which the community would like to be included in the MOON section need to be messaged to me ASAP.

Thanks for the Mooncoin section in your book.
It would be great if you could remove the coinex-exchange, that doesn't exist anymore and also coined up, they seem to give up.
Please have a look at http://mooncoin.rocks/about-mooncoin/. There you can find actual details about exchanges (please add SwissCex and Cryptoine), mining pools etc.
It would be very nice if you could also mention the mooncoin special facts (block number based on the lunar cycle will be awarded a 2x payout bonus, apollo 11 phase, ...also mentioned at mooncoin.rocks)

Thanks a lot. 

[peme]

I finished compiling the original mooncoin-GUI-wallet from source code with integration of the qrcode-library. Everything works fine.  
But I had really no chance to get a new fresh wallet connecting to the mooncoin-network with a completely empty blockchain. The wallet all the time tries to connect to 192.210.146.176:44664 without success and ignores all the online IPs within the mooncoin.conf I added.    

So I took the peers.dat file from my synchronized always fast connecting mooncoin wallet with all the blockchain and copied this peers.dat only in the folder of the mooncoin.conf (c:/users/appdata/roaming/mooncoin) to overwrite the empty peers.dat of the new created mooncoin wallet that has no blockchain. ---> after that the new wallet connected ultra-fast.  

I would like to put this actual peers.dat with a what-to-do-guide if connection problems in the download section of mooncoin.rocks. So new users can use the wallet fast and aren't frustrated because of no connection. What do you think? A good idea?

[agswinner]

I think it's a good idea to have available a wallet ultra fast !
Great work Peme

[Tyke]

I have finished the Mooncoin section.  It will be in the book called Cryptocurrency "The Alt-ernative" (A historical reference book).  Here is the preliminary cover (a better cover is currently being worked on):



The plan is to get the book published before Christmas 2014.  

Here is the Mooncoin preview section:

https://i.imgur.com/rjAp96D.png

Any donations towards this future publication are highly welcome.  I would love to see this book become a reality.  

2THQ74iskgoTXSWEEZZ9R1tkFa9575aDhu


Main Book Bitcointalk.org Thread is:

https://bitcointalk.org/index.php?topic=483187.0

Any further points which the community would like to be included in the MOON section need to be messaged to me ASAP.

Thanks for the Mooncoin section in your book.
It would be great if you could remove the coinex-exchange, that doesn't exist anymore and also coined up, they seem to give up.
Please have a look at http://mooncoin.rocks/about-mooncoin/. There you can find actual details about exchanges (please add SwissCex and Cryptoine), mining pools etc.
It would be very nice if you could also mention the mooncoin special facts (block number based on the lunar cycle will be awarded a 2x payout bonus, apollo 11 phase, ...also mentioned at mooncoin.rocks)

Thanks a lot. 

OK I will take all your comments into account

[coinflow]

I finished compiling the original mooncoin-GUI-wallet from source code with integration of the qrcode-library. Everything works fine.  
But I had really no chance to get a new fresh wallet connecting to the mooncoin-network with a completely empty blockchain. The wallet all the time tries to connect to 192.210.146.176:44664 without success and ignores all the online IPs within the mooncoin.conf I added.    

So I took the peers.dat file from my synchronized always fast connecting mooncoin wallet with all the blockchain and copied this peers.dat only in the folder of the mooncoin.conf (c:/users/appdata/roaming/mooncoin) to overwrite the empty peers.dat of the new created mooncoin wallet that has no blockchain. ---> after that the new wallet connected ultra-fast.  

I would like to put this actual peers.dat with a what-to-do-guide if connection problems in the download section of mooncoin.rocks. So new users can use the wallet fast and aren't frustrated because of no connection. What do you think? A good idea?

Most probably the information in peers.dat is outdated in a few hrs or days again, so it is questionable, whether posting it would be of great help.
I don't know the code of the wallet exactly, but it could be that a now missing seed-node, that deaconboogie coded, prevents the wallet from finding new peers immediately.
So if the wallet is installed from scratch, it does not find an active seed-node (maybe it is simply the mooncoin.info-server, which is offline now, as we know).
So the only real solution would then be, to issue an updated wallet with a new seed-node, which is always on.

Advising to use a mooncoin.conf like this:

addnode=5.45.105.66
addnode=37.120.168.233
addnode=multipool.us
addnode=moon.bitember.com

... could be the better idea meanwhile (until the new wallet with one or more updated seed-nodes is available) ...
(The first IP of the above list is from the P2Pool-node and the second one is the IP-address of the now working blockchain-explorer, so all of these addresses should be online most of the time)

Could you check, whether your compiled wallet is connecting, using a mooncoin.conf of that kind?
Otherwise just check the result of the command getpeerinfo in your working wallet's console, to see the current peers of your wallet. --> Help/Debug/Console

Check out http://devtome.com/doku.php?id=scrypt_altcoin_cloning_guide to find this:
--
 You can also set an initial “seed node” or always on system that the new coin wallets coming online will check for additional addresses:

src/net.cpp:
 LINE 1000  {"some website name", "somewebsite.org or ip x.x.x.x"},
--

which translates to this in the code of the Mooncoin-wallet:

https://github.com/realmooncoin/mooncoin/blob/master/src/net.cpp#L1198

... and because of mooncoin.info being down, the newly installed wallet without addnodes is not finding anything ...

[peme]

I finished compiling the original mooncoin-GUI-wallet from source code with integration of the qrcode-library. Everything works fine.  
But I had really no chance to get a new fresh wallet connecting to the mooncoin-network with a completely empty blockchain. The wallet all the time tries to connect to 192.210.146.176:44664 without success and ignores all the online IPs within the mooncoin.conf I added.    

So I took the peers.dat file from my synchronized always fast connecting mooncoin wallet with all the blockchain and copied this peers.dat only in the folder of the mooncoin.conf (c:/users/appdata/roaming/mooncoin) to overwrite the empty peers.dat of the new created mooncoin wallet that has no blockchain. ---> after that the new wallet connected ultra-fast.  

I would like to put this actual peers.dat with a what-to-do-guide if connection problems in the download section of mooncoin.rocks. So new users can use the wallet fast and aren't frustrated because of no connection. What do you think? A good idea?

Most probably the information in peers.dat is outdated in a few hrs or days again, so it is questionable, whether posting it would be of great help.
I don't know the code of the wallet exactly, but it could be that a now missing seed-node, that deaconboogie coded, prevents the wallet from finding new peers immediately.
So if the wallet is installed from scratch, it does not find an active seed-node (maybe it is simply the mooncoin.info-server, which is offline now, as we know).
So the only real solution would then be, to issue an updated wallet with a new seed-node, which is always on.

Advising to use a mooncoin.conf like this:

addnode=5.45.105.66
addnode=37.120.168.233
addnode=multipool.us
addnode=moon.bitember.com

... could be the better idea meanwhile (until the new wallet with one or more updated seed-nodes is available) ...
(The first IP of the above list is from the P2Pool-node and the second one is the IP-address of the now working blockchain-explorer, so all of these addresses should be online most of the time)

Could you check, whether your compiled wallet is connecting, using a mooncoin.conf of that kind?
Otherwise just check the result of the command getpeerinfo in your working wallet's console, to see the current peers of your wallet. --> Help/Debug/Console

Check out http://devtome.com/doku.php?id=scrypt_altcoin_cloning_guide to find this:
--
 You can also set an initial “seed node” or always on system that the new coin wallets coming online will check for additional addresses:

src/net.cpp:
 LINE 1000  {"some website name", "somewebsite.org or ip x.x.x.x"},
--

which translates to this in the code of the Mooncoin-wallet:

https://github.com/realmooncoin/mooncoin/blob/master/src/net.cpp#L1198

... and because of mooncoin.info being down, the newly installed wallet without addnodes is not finding anything ...

thanks for the detailed infos, coinflow...I will check all of this and will report if a changed mooncoin.conf will connect fast and how a changed wallet with a new seed node in net.cpp will work.  ... give me some time until weekend 

[coinflow]

... give me some time until weekend 

Of course. Better be safe than sorry.   

[Winner]

another 400millions bought at 6 litoshi.


DEFINITIVELY THIS IS THE BEST MOMENT TO BUY IN... LAST OPORTUNITY WAS 2 WEEKS AGO WHICH WE WAS AT 4-5 LITOSHI, RIGHT NOW YOU ONLY CAN BUY AT 6 AND THE ASK IS GETTING BURNED FAST!!!!!


YIIIHAAAAAAAAAAAAAAAAAAAAA


TO THE MOOOOOONNNNNNNN

Back at 5 litoshi, might buy in this time

[redjedievolution]

hahah i think 10 bn for me is enough  But with these ltc prices at 3-4eur, buy is very suculent. 1000 eur / 3.5€ = 285LTC

[coinflow]

This is an interesting information by the DOGE-devs:
http://www.reddit.com/r/dogecoindev/comments/2f30sb/18_contingency_planning/

It shows, what happens and has to be done, when a fork is to be made.
This will inevitably be the case for Mooncoin, too, in the not so far future. I thought, I should post the link, so you all can see and inform yourself about the procedure.

[peme]

This is an interesting information by the DOGE-devs:
http://www.reddit.com/r/dogecoindev/comments/2f30sb/18_contingency_planning/

It shows, what happens and has to be done, when a fork is to be made.
This will inevitably be the case for Mooncoin, too, in the not so far future. I thought, I should post the link, so you all can see and inform yourself about the procedure.

Interesting and very helpful....but I still do not understand the right and wrong fork stuff with releasing a new wallet. I want to understand all the technical details and have to read the bitcoin whitepaper.

[coinflow]

This is an interesting information by the DOGE-devs:
http://www.reddit.com/r/dogecoindev/comments/2f30sb/18_contingency_planning/

It shows, what happens and has to be done, when a fork is to be made.
This will inevitably be the case for Mooncoin, too, in the not so far future. I thought, I should post the link, so you all can see and inform yourself about the procedure.

Interesting and very helpful....but I still do not understand the right and wrong fork stuff with releasing a new wallet. I want to understand all the technical details and have to read the bitcoin whitepaper.

The "right" and "wrong" means the new wallet and the old wallet. We had the same problem the last time deaconboogie released a new wallet. Most of the people updated their wallet to the newest version, but some did not, because they did not know about the update. So they sent MOONs from an old wallet to the network and their Mooncoins never arrived at the wallet they were sent to, because the recipient was already on the new fork with a new wallet and vice versa.
Then they came to this thread and were complaining about the coin but simply they weren't informed about the need to update, so they lost coins.
This shows why it is crucial to have a long information-period in which we need to communicate, that an update has to be done and everybody needs to upgrade until block XY, if they don't wanna lose their Mooncoins in invalid transactions.
We also need to communicate this to the exchanges, as it would be fatal, when the coins sent to and from them will go to digital nirvana, because some are on the old wallet, and some on the new. Communication on this is everything, if we want to avoid confusion and loss of coins. It all depends on how many update to the new wallet, since if there are still a lot of old wallets in the network, we have competing blockchains leading to wallets not syncing correctly or being on different chains, hence even more confusion.

[coinflow]

As an addition to my previous posting: we should release the new wallet with a messaging system, that checks, whether the wallet is the latest version and if not, presents a warning to the user.