Author

Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 107. (Read 782359 times)

hero member
Activity: 714
Merit: 500
y²=x3+ax+b, a=0,b=7
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.  Wink

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.
hero member
Activity: 1088
Merit: 531
Free Crypto in Stake.com Telegram t.me/StakeCasino
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.  Wink

It's definitely undervalued!
sr. member
Activity: 306
Merit: 251
Working for a better world
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
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
sr. member
Activity: 269
Merit: 250
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!!!
member
Activity: 68
Merit: 10
Why is PIVX mooning so hard right now - any new updates?
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
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.
sr. member
Activity: 359
Merit: 270
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.
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
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
sr. member
Activity: 269
Merit: 250
Still SEVERELY underVALUED in my honest opinion...
full member
Activity: 151
Merit: 100
only 1, pivx has a bright future =)
hero member
Activity: 1328
Merit: 563
MintDice.com | TG: t.me/MintDice
how many pivx masternodes does it take to become rich?
sr. member
Activity: 336
Merit: 250
PIVX is going moon soon................😂😂😂😂😂😂😂😂😂
sr. member
Activity: 359
Merit: 270
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.
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
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!
hero member
Activity: 615
Merit: 502
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? 

legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
How to correctly start masternode?
what is the problem? The address did not change.
full member
Activity: 151
Merit: 100
What are the future plans of pivx?
hero member
Activity: 2156
Merit: 521
Are there problems with the blockchain at the moment?

At height 793881 the blockchain stalled for a while, and when I look at the cryptoid block-explorer the height is totally off.
Atm. cryptoid shows height 794093 and my wallets show height 794041, it looks like a fork.


this can happen when a significant amount of masternodes are offline (see posts above)
you just need to resync

cheers


Well, I don't understand why this could happen when there are some master-nodes offline, there were still ~1100 MN online which should be more than enough. My guess is that it has something to do with some people or master-nodes still using the old wallet, probably cryptoid is still using the old wallet as well. This still doesn't explain why the blockchain stalled for a while at height 793881.

the devs are aware of the problem with the mn drop. we had the same problem before.
for more information please visit slack....

Thanks, I will visit slack.


Pivx is very solid project...devs are really profesional...I wish them to keep going

The more solid project is visible from every feature and development update, and the end result is a price that is so expensive, getting people interested to buy more, including this PIVX.
legendary
Activity: 1792
Merit: 1010
code is self healing, witnessed it twice first hand, code is rock solid (super important for it to be so)
Jump to: