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 ...
