[MOJO] MOJOv3 has been taken over by new devs

[dsutil]

I got a third seed node up now, should be:
108.61.172.245 or mojonode03.mojocoin.org

You shouldn't have to put it in the mojocoin.conf as it's in the code and I have checked the DNS settings and it should all be good:



If anyone is having problems, then try to delete the peers.dat and restart, you should have 3 seed nodes hard coded

I have restarted, and now the wallet is syncing, but with the mojonode03:

Code:

mojocoind getpeerinfo
[
    {
        "addr" : "108.61.172.245:22255",
        "services" : "00000001",
        "lastsend" : 1473193019,
        "lastrecv" : 1473193019,
        "bytessent" : 180545,
        "bytesrecv" : 1187107,
        "conntime" : 1473193018,
        "pingtime" : 0.13114600,
        "version" : 90000,
        "subver" : "/Mojocore:2.3.0/",
        "inbound" : false,
        "startingheight" : 113720,
        "banscore" : 0,
        "syncnode" : true

I'll try to restart the 01 and 02 nodes

Now I'm syncing also with mojonode01:

Code:

mojocoind getpeerinfo
[
    {
        "addr" : "108.61.172.245:22255",
        "addrlocal" : ":59726",
        "services" : "00000001",
        "lastsend" : 1473193317,
        "lastrecv" : 1473193345,
        "bytessent" : 181281,
        "bytesrecv" : 1200692,
        "conntime" : 1473193317,
        "pingtime" : 0.17381500,
        "version" : 90000,
        "subver" : "/Mojocore:2.3.0/",
        "inbound" : false,
        "startingheight" : 113847,
        "banscore" : 0,
        "syncnode" : true
    },
    {
        "addr" : "45.63.43.114:22255",
        "addrlocal" : ":60394",
        "services" : "00000001",
        "lastsend" : 1473193319,
        "lastrecv" : 1473193319,
        "bytessent" : 1344,
        "bytesrecv" : 2702,
        "conntime" : 1473193318,
        "pingtime" : 0.23672600,
        "version" : 90000,
        "subver" : "/Mojocore:2.3.0/",
        "inbound" : false,
        "startingheight" : 113847,
        "banscore" : 0,
        "syncnode" : false

[1714296434]

1714296434

[1714296434]

1714296434

[1714296434]

1714296434

[1714296434]

1714296434

[1714296434]

1714296434

[1714296434]

1714296434

[EBK1000]

I think there was a fork, what block are you on?

CryptoID - https://chainz.cryptoid.info/mojo/ - is ahead and stuck

MegaCrypton - http://blockchain.megacrypton.com/mojo/ is on the right block

The nodes and my wallet are at block 113700

[dsutil]

I think there was a fork, what block are you on?

CryptoID - https://chainz.cryptoid.info/mojo/ - is ahead and stuck

MegaCrypton - http://blockchain.megacrypton.com/mojo/ is on the right block

The nodes and my wallet are at block 113700

After resync i'm on megacrypton chain.

[Jack Liver]

same problem i've delete peers.dat and blockchain but i have zero connection, for me http://blockchain.megacrypton.com/mojo/ is down, about the fork can be related to the guy with ASIC ? generally isn't a good thing have all hashing power in the hand of a single user i don't know if it's the same for a ( temporary ) hybrid PoS coin.

[hagie]

at a side note and I dunno if it's related to the actual problem, but almost 50% masternodes running on a single hardware isn't decentralisation.

the network should check double IP's and ban them.

regards


P.S. Still not able to get my controller wallet in sync. Was there really a fork ? Looks like both explorers are at the same high and the hash of the blocks is the same ... so no fork there .

[CryptoHobo]

...
I have deleted peers.dat, blockchain and I have added on the .conf:

addnode=mojonode01.mojocoin.org
addnode=mojonode02.mojocoin.org
addnode=45.63.43.114
addnode=45.32.234.45

With no success. I'm getting on the log a lot of:

Code:

socket recv error 104

and

Code:

connect() to 212.159.88.206:22255 failed after select(): Connection refused

I don't find that node in the explorer network. Very strange. :-O

I was getting the same errors on window qt build, after checking my router it turns out upnp isn't working correctly. Create a rule on your routers firewall and you'll get connections, I did.

[hagie]

...
I have deleted peers.dat, blockchain and I have added on the .conf:

addnode=mojonode01.mojocoin.org
addnode=mojonode02.mojocoin.org
addnode=45.63.43.114
addnode=45.32.234.45

With no success. I'm getting on the log a lot of:

Code:

socket recv error 104

and

Code:

connect() to 212.159.88.206:22255 failed after select(): Connection refused

I don't find that node in the explorer network. Very strange. :-O

I was getting the same errors on window qt build, after checking my router it turns out upnp isn't working correctly. Create a rule on your routers firewall and you'll get connections, I did.

The wallet works fine until the restart. I don't use UPNP and don't allow incoming connections to the windows server. Outgoing (nat) connections are working of course.

There must be another issue ..

regards

[dsutil]

at a side note and I dunno if it's related to the actual problem, but almost 50% masternodes running on a single hardware isn't decentralisation.

the network should check double IP's and ban them.

regards


P.S. Still not able to get my controller wallet in sync. Was there really a fork ? Looks like both explorers are at the same high and the hash of the blocks is the same ... so no fork there .

Last night there was a fork, but after some time, chainz synchronized with the "new" chain. My wallet also.....

[dsutil]

...
I have deleted peers.dat, blockchain and I have added on the .conf:

addnode=mojonode01.mojocoin.org
addnode=mojonode02.mojocoin.org
addnode=45.63.43.114
addnode=45.32.234.45

With no success. I'm getting on the log a lot of:

Code:

socket recv error 104

and

Code:

connect() to 212.159.88.206:22255 failed after select(): Connection refused

I don't find that node in the explorer network. Very strange. :-O

I was getting the same errors on window qt build, after checking my router it turns out upnp isn't working correctly. Create a rule on your routers firewall and you'll get connections, I did.

The wallet works fine until the restart. I don't use UPNP and don't allow incoming connections to the windows server. Outgoing (nat) connections are working of course.

There must be another issue ..

regards

I think also that the problem must be related with what CryptoHobo says because I have the same configuration as you hagie (with linux, but only outgoing connections) and usually I'm getting few connections or none, but If I open the firewall and/or reboot my router, I get more connections....

[dsutil]

...
I have deleted peers.dat, blockchain and I have added on the .conf:

addnode=mojonode01.mojocoin.org
addnode=mojonode02.mojocoin.org
addnode=45.63.43.114
addnode=45.32.234.45

With no success. I'm getting on the log a lot of:

Code:

socket recv error 104

and

Code:

connect() to 212.159.88.206:22255 failed after select(): Connection refused

I don't find that node in the explorer network. Very strange. :-O

I was getting the same errors on window qt build, after checking my router it turns out upnp isn't working correctly. Create a rule on your routers firewall and you'll get connections, I did.

The wallet works fine until the restart. I don't use UPNP and don't allow incoming connections to the windows server. Outgoing (nat) connections are working of course.

There must be another issue ..

regards

I think also that the problem must be related with what CryptoHobo says because I have the same configuration as you hagie (with linux, but only outgoing connections) and usually I'm getting few connections or none, but If I open the firewall and/or reboot my router, I get more connections....

I'm thinking that I'm compiling with UPNP=- Maybe thats the problem........ 

[EBK1000]

I don't think the fork was a big problem, the checkpoints works and so it should resolve itself.
If you find specific issues can you please use the GitHub issues section. I opened it up and I will try to document all the issues there for the next update.

[megacryptonstatus]

Trade MOJOCOIN with Megacrypton.com

BTC/MOJO[Current Rate: 0.00000015]: https://live.megacrypton.com/market/66
LTC/MOJO[Current Rate: 0.00000022]: https://live.megacrypton.com/market/67

[FogHorn_LegHorn]

I am having connectivity issues now. What can I put in my .config file? Thanks

[CryptoHobo]

...

I'm thinking that I'm compiling with UPNP=- Maybe thats the problem........ 

yea that'll compile without upnp.
The windows build has upnp enabled as the checkbox is selected and not grayed out however it doesn't actually seem to do anything.

[GoldenEye]

I am having connectivity issues now. What can I put in my .config file? Thanks

Code:

addnode=mojonode01.mojocoin.org
addnode=mojonode02.mojocoin.org

additionally you can add the peers from here:
https://www.coinexchange.io/network/peers/MOJO

[FogHorn_LegHorn]

I am having connectivity issues now. What can I put in my .config file? Thanks

Code:

addnode=mojonode01.mojocoin.org
addnode=mojonode02.mojocoin.org

additionally you can add the peers from here:
https://www.coinexchange.io/network/peers/MOJO

Damn, WTF is going on? This is my Mojocoin.config file:

addnode=mojonode01.mojocoin.org
addnode=mojonode02.mojocoin.org
addnode=2605:e980:3ea:4::4237
addnode=212.24.103.88
addnode=192.161.53.47
addnode=2002:55d6:444b::55d6:444b
addnode=194.135.92.172
addnode=66.11.122.218
addnode=213.136.94.226
addnode=2a02:c207:3001:4147::1
addnode=93.104.209.17
addnode=85.214.68.75
addnode=66.11.122.218
addnode=2a02:c207:3001:3444::1
addnode=45.63.43.105
addnode=2001:0:5ef5:79fb:2860:641a:2b60:a732
addnode=184.69.47.155
addnode=45.32.234.45
addnode=184.69.47.155
addnode=184.69.47.155
addnode=2600:3c03::f03c:91ff:fe9b:253e
addnode=96.44.156.214
addnode=84.200.32.238
addnode=184.69.47.155
addnode=184.69.47.155
addnode=184.69.47.155
addnode=184.69.47.155
addnode=184.69.47.155
addnode=184.69.47.155
addnode=192.161.53.47
addnode=167.114.103.43

I have zero connections. I have tried to do a total resync and still nothing. WTF is going on? I was totally good till like yesterday then all went to shit. Please help. Thanks.

I reset everything (modem, computer, etc.)

[GoldenEye]

I am having connectivity issues now. What can I put in my .config file? Thanks

Code:

addnode=mojonode01.mojocoin.org
addnode=mojonode02.mojocoin.org

additionally you can add the peers from here:
https://www.coinexchange.io/network/peers/MOJO

Damn, WTF is going on? This is my Mojocoin.config file:

addnode=mojonode01.mojocoin.org
addnode=mojonode02.mojocoin.org
...
I have zero connections. I have tried to do a total resync and still nothing. WTF is going on? I was totally good till like yesterday then all went to shit. Please help. Thanks.

I reset everything (modem, computer, etc.)

I had the same problem 3 days ago. I had constant 17 connections, but after a client restart: nothing.
The explanation here was that there was a fork, but I can't believe this.
For me a resync from the beginning was successful, now I have some connections, but not 17 as before.
I deleted all chain data (probably not necessary) and the peers.dat. Backup your wallet.dat before !!!
Then I started with a clean conf with only the three seed nodes:
https://bitcointalk.org/index.php?topic=1366963.msg16168997#msg16168997

I had never opened ports in the firewall, so that cannot be the reason

[EBK1000]

We have three seed nodes running now:
108.61.172.245
45.63.43.114
45.32.234.45

They are all hardcoded into mojonode01,02,03

I know there was a fork but it resolved itself as it should as the checkpoints are in place. I don't know why there seems to be an issue with peer connections. I will investigate this.

[GoldenEye]

Sorry, I meant:
The explanation here was, that there was a fork, but I can't believe that this was the reason for connection problems.

[hagie]

Sorry, I meant:
The explanation here was, that there was a fork, but I can't believe that this was the reason for connection problems.

I don't believe this either ...

I compile ALL wallets with use_upnp=-  under linux and create the port forwarding by hand in iptables. I never open incoming ports on my windows machine (for obvlious reasons) and of course don't use UPNP and have it disabled on the router.
I hardly get one connection to the network now with my controller wallet and it takes forever to establish something.
There must be another problem.

Regards