【ANN】◢◣ Swipp ◢◣ Modern cryptocurrency ● X11 ● POW/POS ● Masternodes

[acemibtc]

Why only 10 out of 25 working masternodes receive a reward? Check in the explorer - many nodes do not get the reward after 140,000 blocks.

Since yesterday, awards for masternodes have ceased. I put my masternode again from the very beginning with a new address, but I have not received a single award. But at the same time my masternode is working.

v.2.1.0.0 Yggdrasil
Windows 7

[awano1125]

after 24 hours ,my updated mn finally got reward.
still same as before ,1.2SWP.
this update not change anything???

[Imaha486]

after 24 hours ,my updated mn finally got reward.
still same as before ,1.2SWP.
this update not change anything???

same.
all 1.2swp rewards.

[stalin2517]

what is the minimum amount needed to go into business

[canonical]

Why only 10 out of 25 working masternodes receive a reward? Check in the explorer - many nodes do not get the reward after 140,000 blocks.

Since yesterday, awards for masternodes have ceased. I put my masternode again from the very beginning with a new address, but I have not received a single award. But at the same time my masternode is working.

v.2.1.0.0 Yggdrasil
Windows 7

I can confirm this. After 140,000 my masternode stopped receiving any rewards. I also tried to fix this by starting again from scratch with a new address but, so far, it has not made any difference. Rewards have simply stopped.

[teamswipp]

The reason you are not seeing PoW rewards to your masternode yet has been explained. The payment is in the block, but the pools are not sending the reward. Swipp is, as far as we know, is the first peercoin derivate to include PoW masternode payments, so you need to give everybody some time to fix everything. Swipp is not just another stale copy - we are actually doing a lot of new development.

We are working together with the pool operators to fix the issue. Again, read the earlier post regarding this.

On the note of non-working masternodes - nothing has changed in this regard since last release. The masternode code is exactly the same. The difference lies in the miner part and block validation. If you are not receiving payments, you most likely need to wait. The first payment can take a while. If it's still not working, you should look into firewall rules and make sure that you are not closed to the outside world.

Whatever you do, do not keep restarting the masternode. When you do, you are instantly pushed down in priority.

If it's up and it's active - be patient. The payouts will start to come in. Just like last time.

Yours, team swipp

[teamswipp]

what is the minimum amount needed to go into business

For now, you need 30 000 Swipp for a masternode.

Yours, team swipp

[teamswipp]

Hello everybody!

We have been working with the pool operator for our biggest pool (lpool) to fix the issue with the masternode payments. We can report that it is now working properly and that the first masternodes have now received rewards;

http://explorer.swippcoin.com/tx/0542a3557efd92e0a360f591bc6dbef8b5b2057b3e4d3ddee0f47776dfcf55f0
http://explorer.swippcoin.com/tx/802b48b8c58db29831f345e46b9e32bae0625652bffbd3219a15c5838ac02743
http://explorer.swippcoin.com/tx/ed27c41fbf0e31819aa0b2fffd6c43488cb87525889d64a8ee2e277ac0070021

Thanks to lpool for helping out and assisting us to work out this issue .

We will also contact the operator for Altcoinix and get it sorted there as well. Once this is done, we can enforce the payments in the block chain!

We can also report that all masternodes have started to receive payments except these ones;

ScWVC1uMD1QndgC1Y2SukFMUqLf9SGZTuf (firewall closed, rejecting connections)
SMaQo9DtZ42xCfLwDCfHjXAuE2aE1G6Hh1 (connects, but then instantly drops our connection)
SgNw1v7nxNEgUUwUThpsirfADgRDLx2vhL (unknown issue, we recommend changing port to 24055)
SbJkMr56p1jrNyw2bE4pouXisqqAVzaQ8k (connects, but then instantly drops our connection)
SToJDfws4nLMXHz1EKB9GssK5kuEmiUzTM (firewall closed, rejecting connections)
SjE9MpK8Kk17RhNpnZEjdwH7aSHFicajJJ (firewall closed, rejecting connections)
SiPsK8tSQPU8dfvqW38QxGDKTdkCBDXrRy (unknown issue, this one has us stumped)
SWzBtL4ntuUj4CiBWb6CE5Vda5TKK4g14H (unknown issue, this one has us stumped)
SQD4ByPU9UDrs1bXYDZKFTcqNxU67ycarS (firewall closed, rejecting connections)
SVM1NsL9L383tJX2VDKEQVPxny16uLLVL8 (firewall closed, rejecting connections)
SPgewyvbgCvY8Qz3wmQbvBLcq1rXNgJQqW (firewall closed, rejecting connections)

If we were able to identify the problem, we have listed it above. As you can se, most of them have a valid explanation. Currently, we have 11 masternodes misbehaving in one way or another. If it's incorrectly set up, you will obviously not receive payments.

If you are on that list with "unknown issue" and manage to work out what is causing your problems, please let everybody in the thread know.

Yours, team swipp

[awano1125]

Hello everybody!

We have been working with the pool operator for our biggest pool (lpool) to fix the issue with the masternode payments. We can report that it is now working properly and that the first masternodes have now received rewards;

http://explorer.swippcoin.com/tx/0542a3557efd92e0a360f591bc6dbef8b5b2057b3e4d3ddee0f47776dfcf55f0
http://explorer.swippcoin.com/tx/802b48b8c58db29831f345e46b9e32bae0625652bffbd3219a15c5838ac02743
http://explorer.swippcoin.com/tx/ed27c41fbf0e31819aa0b2fffd6c43488cb87525889d64a8ee2e277ac0070021

Thanks to lpool for helping out and assisting us to work out this issue .

We will also contact the operator for Altcoinix and get it sorted there as well. Once this is done, we can enforce the payments in the block chain!

We can also report that all masternodes have started to receive payments except these ones;

ScWVC1uMD1QndgC1Y2SukFMUqLf9SGZTuf (firewall closed, rejecting connections)
SMaQo9DtZ42xCfLwDCfHjXAuE2aE1G6Hh1 (connects, but then instantly drops our connection)
SgNw1v7nxNEgUUwUThpsirfADgRDLx2vhL (unknown issue, we recommend changing port to 24055)
SbJkMr56p1jrNyw2bE4pouXisqqAVzaQ8k (connects, but then instantly drops our connection)
SToJDfws4nLMXHz1EKB9GssK5kuEmiUzTM (firewall closed, rejecting connections)
SjE9MpK8Kk17RhNpnZEjdwH7aSHFicajJJ (firewall closed, rejecting connections)
SiPsK8tSQPU8dfvqW38QxGDKTdkCBDXrRy
SWzBtL4ntuUj4CiBWb6CE5Vda5TKK4g14H
SQD4ByPU9UDrs1bXYDZKFTcqNxU67ycarS
SVM1NsL9L383tJX2VDKEQVPxny16uLLVL8
SPgewyvbgCvY8Qz3wmQbvBLcq1rXNgJQqW

If we were able to identify the problem, we have listed it above. Currently, we have 11 masternodes misbehaving in one way or another. If you are on that list and manage to work out what is causing your problems, please let everybody in the thread now.

Yours, team swipp

my mn not on listed above and i just got reward few min ago,still 1.2 SWP .

[teamswipp]

my mn not on listed above and i just got reward few min ago,still 1.2 SWP.

The PoW rewards (~4.8 Swipp) will come as well. It takes a little time for the network to normalize. If you got a reward it is working as intended. Remember, it's a random payout, so exactly what you get and how much varies slightly.

Yours, team swipp

[Imaha486]

http://explorer.swippcoin.com/tx/adaace65575b4300695940b5cbac95b31d0ffccd124ef6e1205b9133e97b165f

my first 4.8swp reward!  

[teamswipp]

http://explorer.swippcoin.com/tx/adaace65575b4300695940b5cbac95b31d0ffccd124ef6e1205b9133e97b165f

my first 4.8swp reward!  

Congrats

Yours, team swipp

[fusionfoto]

Hello everybody!

We have been working with the pool operator for our biggest pool (lpool) to fix the issue with the masternode payments. We can report that it is now working properly and that the first masternodes have now received rewards;

http://explorer.swippcoin.com/tx/0542a3557efd92e0a360f591bc6dbef8b5b2057b3e4d3ddee0f47776dfcf55f0
http://explorer.swippcoin.com/tx/802b48b8c58db29831f345e46b9e32bae0625652bffbd3219a15c5838ac02743
http://explorer.swippcoin.com/tx/ed27c41fbf0e31819aa0b2fffd6c43488cb87525889d64a8ee2e277ac0070021

Thanks to lpool for helping out and assisting us to work out this issue .

We will also contact the operator for Altcoinix and get it sorted there as well. Once this is done, we can enforce the payments in the block chain!

We can also report that all masternodes have started to receive payments except these ones;

ScWVC1uMD1QndgC1Y2SukFMUqLf9SGZTuf (firewall closed, rejecting connections)
SMaQo9DtZ42xCfLwDCfHjXAuE2aE1G6Hh1 (connects, but then instantly drops our connection)
SgNw1v7nxNEgUUwUThpsirfADgRDLx2vhL (unknown issue, we recommend changing port to 24055)
SbJkMr56p1jrNyw2bE4pouXisqqAVzaQ8k (connects, but then instantly drops our connection)
SToJDfws4nLMXHz1EKB9GssK5kuEmiUzTM (firewall closed, rejecting connections)
SjE9MpK8Kk17RhNpnZEjdwH7aSHFicajJJ (firewall closed, rejecting connections)
SiPsK8tSQPU8dfvqW38QxGDKTdkCBDXrRy (unknown issue, this one has us stumped)
SWzBtL4ntuUj4CiBWb6CE5Vda5TKK4g14H (unknown issue, this one has us stumped)
SQD4ByPU9UDrs1bXYDZKFTcqNxU67ycarS (firewall closed, rejecting connections)
SVM1NsL9L383tJX2VDKEQVPxny16uLLVL8 (firewall closed, rejecting connections)
SPgewyvbgCvY8Qz3wmQbvBLcq1rXNgJQqW (firewall closed, rejecting connections)

If we were able to identify the problem, we have listed it above. As you can se, most of them have a valid explanation. Currently, we have 11 masternodes misbehaving in one way or another. If it's incorrectly set up, you will obviously not receive payments.

If you are on that list with "unknown issue" and manage to work out what is causing your problems, please let everybody in the thread know.

Yours, team swipp

My MN is on the list as "connects, but then instantly drops our connection".

My debug.log looks like this:

2017-12-19 15:01:00 connect() to 31.148.219.41:24055 failed after select(): Conn
ection refused
2017-12-19 15:01:06 connect() to 78.46.142.25:24055 failed after select(): Conne
ction refused
2017-12-19 15:01:07 Misbehaving: 115.78.128.102:24055 (0 -> 1)
2017-12-19 15:01:07 ProcessMessage(ping, 8 bytes) FAILED
2017-12-19 15:01:19 connect() to 63.142.252.38:24055 failed after select(): Conn
ection refused
2017-12-19 15:01:25 Misbehaving: 104.251.218.157:24055 (0 -> 1)
2017-12-19 15:01:25 ProcessMessage(ping, 8 bytes) FAILED
2017-12-19 15:01:31 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused
2017-12-19 15:01:40 CDarkSendPool::UpdateState() == 3 | 3
2017-12-19 15:01:40 CActiveMasternode::Dseep() - SendDarkSendElectionEntryPing v
in = CTxIn(COutPoint(8af5718190, 1), scriptSig=)
2017-12-19 15:03:32 connect() to 183.181.170.69:24055 failed after select(): Con
2017-12-19 15:03:40 CDarkSendPool::UpdateState() == 3 | 3
2017-12-19 15:03:44 connect() to 88.117.5.39:24055 failed after select(): Connec
tion refused
2017-12-19 15:03:45 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused
2017-12-19 15:03:46 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused
2017-12-19 15:03:47 SetBestChain: new best=00000000000e8e2ba467a6cf9d182a2ee366a
69f9e5871f5d52eefbc2b49dd61  height=141585  trust=56142781818565511163  blocktru
st=15754019755107  date=12/19/17 15:03:25
2017-12-19 15:03:47 ProcessBlock: ACCEPTED
+2017-12-19 15:03:52 connect() to 31.148.219.41:24055 failed after select(): Con
nection refused
2017-12-19 15:03:58 connect() to 78.46.142.25:24055 failed after select(): Conne
ction refused
2017-12-19 15:04:10 CActiveMasternode::Dseep() - SendDarkSendElectionEntryPing v
in = CTxIn(COutPoint(8af5718190, 1), scriptSig=)
2017-12-19 15:04:11 connect() to 63.142.252.38:24055 failed after select(): Conn
ection refused
2017-12-19 15:04:23 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused

It thinks all of the incoming connections are misbehaving for some reason.

[teamswipp]

My MN is on the list as "connects, but then instantly drops our connection".

It thinks all of the incoming connections are misbehaving for some reason.

Hi. Actually, most of the "connection refused" messages you are seeing are caused by nodes/wallets that are closed and do not accept connections. This is completely normal.

To troubleshoot this via terminal, you can telnet to your node from the outside with;

telnet <ip> <port>

If it holds the connection and lets you enter some characters, it's behaving correctly. If it instantly disconnects  you, something is wrong and most likely caused by a firewall issue.

Yours, team swipp

[altcoinix]

We updated our pool wallet

http://s1.altcoinix.com/swipp/public

[anupans]

The old version runs MN, i see my IP on http://explorer.swippcoin.com/masternodes. Version 2.1.1.0 does not work

I doubt it's the wallet. No code in the part that registers the wallet has changed. Also, many masternodes are running 2.1.1.0 already.

It's probably the collateral that is wrong in some way...  Remember, it has to be exactly 30k swipp.

Also, check the debug.log... If it's not starting you can usually get some tips there.

Yours, team swipp

Hi you
After 12h run, nothing is progressing, although at http://explorer.swippcoin.com/masternodes still see my IP.
I use the wallet v2.1.1.0: Yggdrasil. 
How do I run MN?
https://imgur.com/a/SWkpq
https://imgur.com/a/ddC1q
https://imgur.com/a/w7YtN

Hi.

Open an issue on GitHub.

If it's not the collateral, it might be that the port for the masternode is not open in your firewall, that could also result in a -1 rank that doesn't change.

Yours, team swipp

I opened the port, I let the wallet run for hours, but still nothing progressed. Even in the tap SwipNodeNetwork only see each of my MN.
I do not know what to do now. My wallet is the latest version 2.1.1.0
https://imgur.com/a/brz5z
https://imgur.com/a/nq84C
https://imgur.com/a/X4kDL

Same for me

Me too

anybody can solve this problem?

[adorid]

Coin added to pool:

http://hashpool.eu

Code:

-o stratum+tcp://pool.hashpool.eu:3533 -u <WALLET_ADDRESS> -p c=SWP

[fusionfoto]

Hello everybody!

We have been working with the pool operator for our biggest pool (lpool) to fix the issue with the masternode payments. We can report that it is now working properly and that the first masternodes have now received rewards;

http://explorer.swippcoin.com/tx/0542a3557efd92e0a360f591bc6dbef8b5b2057b3e4d3ddee0f47776dfcf55f0
http://explorer.swippcoin.com/tx/802b48b8c58db29831f345e46b9e32bae0625652bffbd3219a15c5838ac02743
http://explorer.swippcoin.com/tx/ed27c41fbf0e31819aa0b2fffd6c43488cb87525889d64a8ee2e277ac0070021

Thanks to lpool for helping out and assisting us to work out this issue .

We will also contact the operator for Altcoinix and get it sorted there as well. Once this is done, we can enforce the payments in the block chain!

We can also report that all masternodes have started to receive payments except these ones;

ScWVC1uMD1QndgC1Y2SukFMUqLf9SGZTuf (firewall closed, rejecting connections)
SMaQo9DtZ42xCfLwDCfHjXAuE2aE1G6Hh1 (connects, but then instantly drops our connection)
SgNw1v7nxNEgUUwUThpsirfADgRDLx2vhL (unknown issue, we recommend changing port to 24055)
SbJkMr56p1jrNyw2bE4pouXisqqAVzaQ8k (connects, but then instantly drops our connection)
SToJDfws4nLMXHz1EKB9GssK5kuEmiUzTM (firewall closed, rejecting connections)
SjE9MpK8Kk17RhNpnZEjdwH7aSHFicajJJ (firewall closed, rejecting connections)
SiPsK8tSQPU8dfvqW38QxGDKTdkCBDXrRy (unknown issue, this one has us stumped)
SWzBtL4ntuUj4CiBWb6CE5Vda5TKK4g14H (unknown issue, this one has us stumped)
SQD4ByPU9UDrs1bXYDZKFTcqNxU67ycarS (firewall closed, rejecting connections)
SVM1NsL9L383tJX2VDKEQVPxny16uLLVL8 (firewall closed, rejecting connections)
SPgewyvbgCvY8Qz3wmQbvBLcq1rXNgJQqW (firewall closed, rejecting connections)

If we were able to identify the problem, we have listed it above. As you can se, most of them have a valid explanation. Currently, we have 11 masternodes misbehaving in one way or another. If it's incorrectly set up, you will obviously not receive payments.

If you are on that list with "unknown issue" and manage to work out what is causing your problems, please let everybody in the thread know.

Yours, team swipp

My MN is on the list as "connects, but then instantly drops our connection".

My debug.log looks like this:

2017-12-19 15:01:00 connect() to 31.148.219.41:24055 failed after select(): Conn
ection refused
2017-12-19 15:01:06 connect() to 78.46.142.25:24055 failed after select(): Conne
ction refused
2017-12-19 15:01:07 Misbehaving: 115.78.128.102:24055 (0 -> 1)
2017-12-19 15:01:07 ProcessMessage(ping, 8 bytes) FAILED
2017-12-19 15:01:19 connect() to 63.142.252.38:24055 failed after select(): Conn
ection refused
2017-12-19 15:01:25 Misbehaving: 104.251.218.157:24055 (0 -> 1)
2017-12-19 15:01:25 ProcessMessage(ping, 8 bytes) FAILED
2017-12-19 15:01:31 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused
2017-12-19 15:01:40 CDarkSendPool::UpdateState() == 3 | 3
2017-12-19 15:01:40 CActiveMasternode::Dseep() - SendDarkSendElectionEntryPing v
in = CTxIn(COutPoint(8af5718190, 1), scriptSig=)
2017-12-19 15:03:32 connect() to 183.181.170.69:24055 failed after select(): Con
2017-12-19 15:03:40 CDarkSendPool::UpdateState() == 3 | 3
2017-12-19 15:03:44 connect() to 88.117.5.39:24055 failed after select(): Connec
tion refused
2017-12-19 15:03:45 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused
2017-12-19 15:03:46 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused
2017-12-19 15:03:47 SetBestChain: new best=00000000000e8e2ba467a6cf9d182a2ee366a
69f9e5871f5d52eefbc2b49dd61  height=141585  trust=56142781818565511163  blocktru
st=15754019755107  date=12/19/17 15:03:25
2017-12-19 15:03:47 ProcessBlock: ACCEPTED
+2017-12-19 15:03:52 connect() to 31.148.219.41:24055 failed after select(): Con
nection refused
2017-12-19 15:03:58 connect() to 78.46.142.25:24055 failed after select(): Conne
ction refused
2017-12-19 15:04:10 CActiveMasternode::Dseep() - SendDarkSendElectionEntryPing v
in = CTxIn(COutPoint(8af5718190, 1), scriptSig=)
2017-12-19 15:04:11 connect() to 63.142.252.38:24055 failed after select(): Conn
ection refused
2017-12-19 15:04:23 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused

It thinks all of the incoming connections are misbehaving for some reason.

[teamswipp]

Hello everybody!

We have been working with the pool operator for our biggest pool (lpool) to fix the issue with the masternode payments. We can report that it is now working properly and that the first masternodes have now received rewards;

http://explorer.swippcoin.com/tx/0542a3557efd92e0a360f591bc6dbef8b5b2057b3e4d3ddee0f47776dfcf55f0
http://explorer.swippcoin.com/tx/802b48b8c58db29831f345e46b9e32bae0625652bffbd3219a15c5838ac02743
http://explorer.swippcoin.com/tx/ed27c41fbf0e31819aa0b2fffd6c43488cb87525889d64a8ee2e277ac0070021

Thanks to lpool for helping out and assisting us to work out this issue .

We will also contact the operator for Altcoinix and get it sorted there as well. Once this is done, we can enforce the payments in the block chain!

We can also report that all masternodes have started to receive payments except these ones;

ScWVC1uMD1QndgC1Y2SukFMUqLf9SGZTuf (firewall closed, rejecting connections)
SMaQo9DtZ42xCfLwDCfHjXAuE2aE1G6Hh1 (connects, but then instantly drops our connection)
SgNw1v7nxNEgUUwUThpsirfADgRDLx2vhL (unknown issue, we recommend changing port to 24055)
SbJkMr56p1jrNyw2bE4pouXisqqAVzaQ8k (connects, but then instantly drops our connection)
SToJDfws4nLMXHz1EKB9GssK5kuEmiUzTM (firewall closed, rejecting connections)
SjE9MpK8Kk17RhNpnZEjdwH7aSHFicajJJ (firewall closed, rejecting connections)
SiPsK8tSQPU8dfvqW38QxGDKTdkCBDXrRy (unknown issue, this one has us stumped)
SWzBtL4ntuUj4CiBWb6CE5Vda5TKK4g14H (unknown issue, this one has us stumped)
SQD4ByPU9UDrs1bXYDZKFTcqNxU67ycarS (firewall closed, rejecting connections)
SVM1NsL9L383tJX2VDKEQVPxny16uLLVL8 (firewall closed, rejecting connections)
SPgewyvbgCvY8Qz3wmQbvBLcq1rXNgJQqW (firewall closed, rejecting connections)

If we were able to identify the problem, we have listed it above. As you can se, most of them have a valid explanation. Currently, we have 11 masternodes misbehaving in one way or another. If it's incorrectly set up, you will obviously not receive payments.

If you are on that list with "unknown issue" and manage to work out what is causing your problems, please let everybody in the thread know.

Yours, team swipp

My MN is on the list as "connects, but then instantly drops our connection".

My debug.log looks like this:

2017-12-19 15:01:00 connect() to 31.148.219.41:24055 failed after select(): Conn
ection refused
2017-12-19 15:01:06 connect() to 78.46.142.25:24055 failed after select(): Conne
ction refused
2017-12-19 15:01:07 Misbehaving: 115.78.128.102:24055 (0 -> 1)
2017-12-19 15:01:07 ProcessMessage(ping, 8 bytes) FAILED
2017-12-19 15:01:19 connect() to 63.142.252.38:24055 failed after select(): Conn
ection refused
2017-12-19 15:01:25 Misbehaving: 104.251.218.157:24055 (0 -> 1)
2017-12-19 15:01:25 ProcessMessage(ping, 8 bytes) FAILED
2017-12-19 15:01:31 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused
2017-12-19 15:01:40 CDarkSendPool::UpdateState() == 3 | 3
2017-12-19 15:01:40 CActiveMasternode::Dseep() - SendDarkSendElectionEntryPing v
in = CTxIn(COutPoint(8af5718190, 1), scriptSig=)
2017-12-19 15:03:32 connect() to 183.181.170.69:24055 failed after select(): Con
2017-12-19 15:03:40 CDarkSendPool::UpdateState() == 3 | 3
2017-12-19 15:03:44 connect() to 88.117.5.39:24055 failed after select(): Connec
tion refused
2017-12-19 15:03:45 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused
2017-12-19 15:03:46 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused
2017-12-19 15:03:47 SetBestChain: new best=00000000000e8e2ba467a6cf9d182a2ee366a
69f9e5871f5d52eefbc2b49dd61  height=141585  trust=56142781818565511163  blocktru
st=15754019755107  date=12/19/17 15:03:25
2017-12-19 15:03:47 ProcessBlock: ACCEPTED
+2017-12-19 15:03:52 connect() to 31.148.219.41:24055 failed after select(): Con
nection refused
2017-12-19 15:03:58 connect() to 78.46.142.25:24055 failed after select(): Conne
ction refused
2017-12-19 15:04:10 CActiveMasternode::Dseep() - SendDarkSendElectionEntryPing v
in = CTxIn(COutPoint(8af5718190, 1), scriptSig=)
2017-12-19 15:04:11 connect() to 63.142.252.38:24055 failed after select(): Conn
ection refused
2017-12-19 15:04:23 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused

It thinks all of the incoming connections are misbehaving for some reason.

Please do not spam the thread and double-post the same thing twice. I already answered this here;

https://bitcointalk.org/index.php?topic=2375296.msg26611707#msg26611707

Yours, team swipp

[teamswipp]

anybody can solve this problem?

We already went through and troubleshot all the masternodes that in one way or another are not receiving payments. Please see our post concerning this. Most masternodes not receiving payment have a firewall that is incorrectly configured.

Yours, team swipp