[ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN

[cryptomaxsun]

How to correctly start masternode?
what is the problem? The address did not change.

[1714190229]

1714190229

[1714190229]

1714190229

[btct22]

How to correctly start masternode?
what is the problem? The address did not change.

This is a weird error message that comes up for me as well.  The answer is to use the command line to start the node.

try: masternode start-alias "masternode=1"   from the debug console? 

[cryptomaxsun]

How to correctly start masternode?
what is the problem? The address did not change.

This is a weird error message that comes up for me as well.  The answer is to use the command line to start the node.

try: masternode start-alias "masternode=1"   from the debug console? 

I'm with the console running : masternode start-many
 
Does not help, status enabled, then a missing.
Help!

[EleanorZ]

How to correctly start masternode?
what is the problem? The address did not change.

This is a weird error message that comes up for me as well.  The answer is to use the command line to start the node.

try: masternode start-alias "masternode=1"   from the debug console?  

I'm with the console running : masternode start-many
 
Does not help, status enabled, then a missing.
Help!

If possible, avoid using 'start-many'. Use 'start-missing' or, even better, as btct22 suggested, use 'start-alias MN-NAME' and, if that still isn't working, do it from the console rather than via the GUI (to be fair, the GUI has been quite reliable for the last few wallet releases).

If your problem is still the 'invalid IP' error, first try waiting a day. I have had the 'invalid IP' three times that I can remember (in 1.5 years), and twice it went away on its own. The third time, it didn't go away after a few days so I created a new MN address, did the process over again, and everything was fine. So that is also an option.

If, however, your MN is showing up as being enabled and then an hour later it is missing, then the more likely answer is that you entered information wrong somewhere. First, did you activate the remote node (pivx-cli masternode start), and did you make sure that your remote pivx.conf (assuming you're using a VPS) is updated? You have to activate remotely first and then locally. Of course, that also means that your remote node has to be fully synced. Also, make sure you have the correct tx id, '1' or '0' etc. in your local masternode.conf and that the relevant info in the remote pivx.conf matches the local masternode.conf. Worst case, you might also try deleting everything on the remote server (again assuming you're using a VPS) and reinstalling.

I also wonder if actually naming your MN 'masternode=1' like you've done might screw something up, if the name somehow gets read as part of the code. Or if the fact that your MN is apparently named 'masternode=1' is in fact a sign that you've messed something up in your code.

[LEILO]

PIVX is going moon soon................😂😂😂😂😂😂😂😂😂

[theskillzdatklls]

how many pivx masternodes does it take to become rich?

[hexoli]

only 1, pivx has a bright future =)

[endchat]

Still SEVERELY underVALUED in my honest opinion...

[cryptomaxsun]

How to correctly start masternode?
what is the problem? The address did not change.

This is a weird error message that comes up for me as well.  The answer is to use the command line to start the node.

try: masternode start-alias "masternode=1"   from the debug console?  

I'm with the console running : masternode start-many
 
Does not help, status enabled, then a missing.
Help!

If possible, avoid using 'start-many'. Use 'start-missing' or, even better, as btct22 suggested, use 'start-alias MN-NAME' and, if that still isn't working, do it from the console rather than via the GUI (to be fair, the GUI has been quite reliable for the last few wallet releases).

If your problem is still the 'invalid IP' error, first try waiting a day. I have had the 'invalid IP' three times that I can remember (in 1.5 years), and twice it went away on its own. The third time, it didn't go away after a few days so I created a new MN address, did the process over again, and everything was fine. So that is also an option.

If, however, your MN is showing up as being enabled and then an hour later it is missing, then the more likely answer is that you entered information wrong somewhere. First, did you activate the remote node (pivx-cli masternode start), and did you make sure that your remote pivx.conf (assuming you're using a VPS) is updated? You have to activate remotely first and then locally. Of course, that also means that your remote node has to be fully synced. Also, make sure you have the correct tx id, '1' or '0' etc. in your local masternode.conf and that the relevant info in the remote pivx.conf matches the local masternode.conf. Worst case, you might also try deleting everything on the remote server (again assuming you're using a VPS) and reinstalling.

I also wonder if actually naming your MN 'masternode=1' like you've done might screw something up, if the name somehow gets read as part of the code. Or if the fact that your MN is apparently named 'masternode=1' is in fact a sign that you've messed something up in your code.

name masternode mn=1

Code:

07:45:53

start-missing


07:45:53

Method not found (code -32601)


07:46:20

start-alias mn=1


07:46:20

Method not found (code -32601)


07:46:39

start-missing mn=1


07:46:39

Method not found (code -32601)

How the problem?
Fix?

UP.
VPS PIVX.conf

Code:

rpcuser=(any username)
rpcpassword=(any password)
server=1
daemon=1
listen=1
staking=0                                                                               
logtimestamps=1                                                                         
maxconnections=256          
port=51472                                                                              
masternode=1                                                                            
externalip=185.51.247.44                                                                
bind=185.51.247.44                                                                      
masternodeaddr=185.51.247.44                                                            
masternodeprivkey=***************

Local masternode.conf

Code:

mn=1 185.51.247.44:51472 masternode privkey ID transaction 1

[EleanorZ]

How the problem?
Fix?

Your local masternode.conf looks fine, assuming the info is correct. You have a bunch of extra stuff in your remote conf, though. I don't know if it's causing issues, but I can say that I don't have it and I rarely have problems. This is mine:

Code:

rpcuser=blahblahblah
rpcpassword=blahblahblah
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
bantime=50
maxconnections=64
masternode=1
masternodeprivkey=blahblahblah

So, I don't have the port=, externalip=, bind=, or masternodeaddr= lines, and I would definitely try removing those. bantime= used to be necessary and honestly I'm not sure if it still is, but it's still in there and it works fine! Also, I used to have 256 connections but I have been playing with lower numbers recently since I was having some bandwidth issues on my VPSs. 256 should be fine though.

[cryptomaxsun]

How the problem?
Fix?

Your local masternode.conf looks fine, assuming the info is correct. You have a bunch of extra stuff in your remote conf, though. I don't know if it's causing issues, but I can say that I don't have it and I rarely have problems. This is mine:

Code:

rpcuser=blahblahblah
rpcpassword=blahblahblah
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
bantime=50
maxconnections=64
masternode=1
masternodeprivkey=blahblahblah

So, I don't have the port=, externalip=, bind=, or masternodeaddr= lines, and I would definitely try removing those. bantime= used to be necessary and honestly I'm not sure if it still is, but it's still in there and it works fine! Also, I used to have 256 connections but I have been playing with lower numbers recently since I was having some bandwidth issues on my VPSs. 256 should be fine though.

Code:

09:50:17

masternode start-alias "mn=1"


09:50:17

{
    "alias" : "mn=1",
    "result" : "successful"
}

Status Enabled,
Active 00m00s

does not change, and the last contact is also unchanged.

[gdrules]

Why is PIVX mooning so hard right now - any new updates?

[endchat]

Why is PIVX mooning so hard right now - any new updates?

because the team is working hard and making great improvements...

but more so, because it severely undervalued!!!

[cryptomaxsun]

How fix?

[FermatMX]

Why is PIVX mooning so hard right now - any new updates?

because the team is working hard and making great improvements...

but more so, because it severely undervalued!!!

Totally agree with your opinion, great team doing stuff but the first top price is over 150,000 sts

[free-bit.co.in]

Why is PIVX mooning so hard right now - any new updates?

because the team is working hard and making great improvements...

but more so, because it severely undervalued!!!

Totally agree with your opinion, great team doing stuff but the first top price is over 150,000 sts

Yep, we are still far away from the ATH price of 150k satoshi BTC, but we reached a higher price in $ as Bitcoin got expensive.  

It's definitely undervalued!

[bluedude]

Why is PIVX mooning so hard right now - any new updates?

because the team is working hard and making great improvements...

but more so, because it severely undervalued!!!

Totally agree with your opinion, great team doing stuff but the first top price is over 150,000 sts

Yep, we are still far away from the ATH price of 150k satoshi BTC, but we reached a higher price in $ as Bitcoin got expensive.  

It's definitely undervalued!

Price will soon reach 100K+ with the new mainnet release. So its a great time to buy and accumulate for the greener future.

[cryptomaxsun]

started the masternode on another server:


Code:

masternode start-all


08:30:36

{
    "overall" : "Successfully started 1 masternodes, failed to start 0, total 1",
    "detail" : {
        "status" : {
            "alias" : "mn1",
            "result" : "successful"
        }
    }
}

Code:

masternode status


08:31:12

This is not a masternode
 (code -1)

the work timer does not change, when starting with the purse it gives out the same error as in the screenshot above.
Help, what's the problem?

[blester]

When was the release date of PIVX's masternode?

[rebal15]

PIVX is going moon soon................😂😂😂😂😂😂😂😂😂

yeah, everything with PIVX is soon. PIVX is soon.