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

[c0in_junkie]

Where can i find instructions about installing and securing pivx wallet?

[1714104289]

1714104289

[1714104289]

1714104289

[jazen777]

Where can i find instructions about installing and securing pivx wallet?

Quickest response time - pivx.slack.com

Other -https://forum.pivx.org/c/pivx-guides


Goodluck! :-) -jazen

[c0in_junkie]

Thank you.

[mxnsch]

devs you need for hard work to fix some shits erorrs in pivx daemon
after its once killed (why?) and after manual restart the blockchain is corrupted:

[root@xxxx ~]# : Corrupted block database detected.
 
Do you want to rebuild the block database now?

2017-03-23 07:08:46 ERROR: ProcessNewBlock : AcceptBlock FAILED
2017-03-23 07:08:46 block time=1490233275 adjusted time=1490252926 is proof of stake=1
2017-03-23 07:08:46 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large
2017-03-23 07:08:46 ERROR: CheckProofOfStake() : INFO: read txPrev failed
2017-03-23 07:08:46 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d
2017-03-23 07:08:46 ERROR: ProcessNewBlock : AcceptBlock FAILED
2017-03-23 07:08:47 block time=1490233275 adjusted time=1490252927 is proof of stake=1
2017-03-23 07:08:47 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large
2017-03-23 07:08:47 ERROR: CheckProofOfStake() : INFO: read txPrev failed
2017-03-23 07:08:47 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d
2017-03-23 07:08:47 ERROR: ProcessNewBlock : AcceptBlock FAILED
2017-03-23 07:09:00 block time=1490233275 adjusted time=1490252940 is proof of stake=1
2017-03-23 07:09:00 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large
2017-03-23 07:09:00 ERROR: CheckProofOfStake() : INFO: read txPrev failed
2017-03-23 07:09:00 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d

Never had that issue. Why did you kill the process? How did you install PIVX and what version? Feel free to hit #support in slack.

Ps.: It's obviously a known issue when you try _really_ hard to kill the process multiple times and only happening to installations on a SSD ;-)
Fix in the works here: https://github.com/PIVX-Project/PIVX/issues/69 Stay calm, coins are safe.

[linux_master]

devs you need for hard work to fix some shits erorrs in pivx daemon
after its once killed (why?) and after manual restart the blockchain is corrupted:

[root@xxxx ~]# : Corrupted block database detected.
 
Do you want to rebuild the block database now?

2017-03-23 07:08:46 ERROR: ProcessNewBlock : AcceptBlock FAILED
2017-03-23 07:08:46 block time=1490233275 adjusted time=1490252926 is proof of stake=1
2017-03-23 07:08:46 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large
2017-03-23 07:08:46 ERROR: CheckProofOfStake() : INFO: read txPrev failed
2017-03-23 07:08:46 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d
2017-03-23 07:08:46 ERROR: ProcessNewBlock : AcceptBlock FAILED
2017-03-23 07:08:47 block time=1490233275 adjusted time=1490252927 is proof of stake=1
2017-03-23 07:08:47 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large
2017-03-23 07:08:47 ERROR: CheckProofOfStake() : INFO: read txPrev failed
2017-03-23 07:08:47 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d
2017-03-23 07:08:47 ERROR: ProcessNewBlock : AcceptBlock FAILED
2017-03-23 07:09:00 block time=1490233275 adjusted time=1490252940 is proof of stake=1
2017-03-23 07:09:00 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large
2017-03-23 07:09:00 ERROR: CheckProofOfStake() : INFO: read txPrev failed
2017-03-23 07:09:00 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d

Never had that issue. Why did you kill the process? How did you install PIVX and what version? Feel free to hit #support in slack.

Ps.: It's obviously a known issue when you try _really_ hard to kill the process multiple times and only happening to installations on a SSD ;-)
Fix in the works here: https://github.com/PIVX-Project/PIVX/issues/69 Stay calm, coins are safe.

Its killed not by me, it was crash, now I am experementing with maxconnection parameter,  looks like decreasing this paramater more stable for daemon

But it is a fact that some daemon crashing corrupts local blockchain and it is a bug need for fix it

and yes it is SSD VPS, thanks for link

[mxnsch]

devs you need for hard work to fix some shits erorrs in pivx daemon
after its once killed (why?) and after manual restart the blockchain is corrupted:

[root@xxxx ~]# : Corrupted block database detected.
 
Do you want to rebuild the block database now?

2017-03-23 07:08:46 ERROR: ProcessNewBlock : AcceptBlock FAILED
2017-03-23 07:08:46 block time=1490233275 adjusted time=1490252926 is proof of stake=1
2017-03-23 07:08:46 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large
2017-03-23 07:08:46 ERROR: CheckProofOfStake() : INFO: read txPrev failed
2017-03-23 07:08:46 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d
2017-03-23 07:08:46 ERROR: ProcessNewBlock : AcceptBlock FAILED
2017-03-23 07:08:47 block time=1490233275 adjusted time=1490252927 is proof of stake=1
2017-03-23 07:08:47 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large
2017-03-23 07:08:47 ERROR: CheckProofOfStake() : INFO: read txPrev failed
2017-03-23 07:08:47 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d
2017-03-23 07:08:47 ERROR: ProcessNewBlock : AcceptBlock FAILED
2017-03-23 07:09:00 block time=1490233275 adjusted time=1490252940 is proof of stake=1
2017-03-23 07:09:00 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large
2017-03-23 07:09:00 ERROR: CheckProofOfStake() : INFO: read txPrev failed
2017-03-23 07:09:00 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d

Never had that issue. Why did you kill the process? How did you install PIVX and what version? Feel free to hit #support in slack.

Ps.: It's obviously a known issue when you try _really_ hard to kill the process multiple times and only happening to installations on a SSD ;-)
Fix in the works here: https://github.com/PIVX-Project/PIVX/issues/69 Stay calm, coins are safe.

Its killed not by me, it was crash, now I am experementing with maxconnection parameter,  looks like decreasing this paramater more stable for daemon on VPS

But it is a fact that some daemon crashing corrupts local blockchain and it is a bug need for fix it

and yes it is SSD VPS, thanks for link

Be assured it's being worked on. Is your ram limited by any chance? When you don't have enough, the process get's killed by the linux kernel.

Never had that issue myself, but i can replicate it by killing as stated in the github issue.

[bitmaster1x]

Not even heard about this until a few days ago and this was around since 2015. Interesting.

[ciro1]

Alot of people are gonna hear about pivx after it hit $2. I can't believe I didn't buy in when it was 0.18 few days ago

[linux_master]

When you don't have enough, the process get's killed by the linux kernel.

of course I know it

Is your ram limited by any chance?

of course, 512 Mb now, but how to determine which of config parameteres influences to the ram?

pivx daemon like dash may be and bitcoin I think very gluttonous for ram

but dash daemon more and more stable now, a lot of work has been done there

and ok this discussion can be moved to pivx forum

[lordzc]

How long will this ascension continue?

[bitmaster1x]

I just realized that this is just a re-branding of DNET. LoL

[misterbones]

DUMP INCOMING SOON 

[coinwider]

How long will this ascension continue?

a Mars journey takes  6 months   

[ooom]

Where can you use PIVX?

Circulating supply:
 7,181,585 DASH  
52,537,624 PIVX

Supply is a way to huge to reach an amazing price.

I think anything above 5 dollar mark per PIVX will be highly over payed.

Looking at today status of the project it's still needs a ton of development in various directions.

[LemonAndFriesOne]

Can't wait until the next part of PIVx is released. Should be good 

[BitcoinFX]

When you don't have enough, the process get's killed by the linux kernel.

of course I know it

Is your ram limited by any chance?

of course, 512 Mb now, but how to determine which of config parameteres influences to the ram?

pivx daemon like dash may be and bitcoin I think very gluttonous for ram

but dash daemon more and more stable now, a lot of work has been done there

and ok this discussion can be moved to pivx forum

512 MB is low RAM.

Check if you have a paging file (SWAP) set-up (if the following command returns blank then you don't have one)...

Code:

sudo swapon -s

Create a 1GB SWAP file (double the amount of physical RAM is the recommendation up to 2 GB physical RAM)

Code:

sudo dd if=/dev/zero of=/swapfile bs=64M count=16

N.B. count=16 = 1GB SWAP (count=32 would create a 2GB SWAP etc.)

Code:

sudo chmod 600 /swapfile

Code:

sudo mkswap /swapfile

Code:

sudo swapon /swapfile

You then need to make the paging file persistent on re-boot by adding the following line to the base of /etc/fstab.

Open fstab ...

Code:

sudo nano /etc/fstab

/swapfile   none    swap    sw    0   0

crtl + x (to save)

Also adding the following lines to sysctl.conf will make the SWAP file more efficient on a server.

Open sysctl.conf ...

Code:

sudo nano /etc/sysctl.conf

vm.swappiness = 60

vm.vfs_cache_pressure = 50

Again, crtl + x (to save)

Now restart the wallet daemon. Hope it helps.

[linux_master]

When you don't have enough, the process get's killed by the linux kernel.

of course I know it

Is your ram limited by any chance?

of course, 512 Mb now, but how to determine which of config parameteres influences to the ram?

pivx daemon like dash may be and bitcoin I think very gluttonous for ram

but dash daemon more and more stable now, a lot of work has been done there

and ok this discussion can be moved to pivx forum

512 MB is low RAM.

Check if you have a paging file (SWAP) set-up (if the following command returns blank then you don't have one)...

Code:

sudo swapon -s

Create a 1GB SWAP file (double the amount of physical RAM is the recommendation up to 2 GB physical RAM)

Code:

sudo dd if=/dev/zero of=/swapfile bs=64M count=16

N.B. count=16 = 1GB SWAP (count=32 would create a 2GB SWAP etc.)

Code:

sudo chmod 600 /swapfile

Code:

sudo mkswap /swapfile

Code:

sudo swapon /swapfile

You then need to make the paging file persistent on re-boot by adding the following line to the base of /etc/fstab.

Open fstab ...

Code:

sudo nano /etc/fstab

/swapfile   none    swap    sw    0   0

crtl + x (to save)

Also adding the following lines to sysctl.conf will make the SWAP file more efficient on a server.

Open sysctl.conf ...

Code:

sudo nano /etc/sysctl.conf

vm.swappiness = 60

vm.vfs_cache_pressure = 50

Again, crtl + x (to save)

Now restart the wallet daemon. Hope it helps.

yes its  blank
many thanks bro

[iosemite]

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! COMING PUMP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

                               btc-e.com
                               poloniex.com
                  /88888888888888888888888888\
                  |88888888888888888888888888/
                   |~~____~~~~~~~~~"""""""""|
                  / \_________/"""""""""""""\
                 /  |              \         \
                /   |  88    88     \         \
               /    |  88    88      \         \
              /    /                  \        |
             /     |   ________        \       |
             \     |   \______/        /       |
  /"\         \     \____________     /        |
  | |__________\_        |  |        /        /
/""""\           \_------'  '-------/       --
\____/,___________\                 -------/
------*            |                    \
  ||               |                     \
  ||               |                 ^    \
  ||               |                | \    \
  ||               |                |  \    \
  ||               |                |   \    \
  \|              /                /"""\/    /
     -------------                |    |    /
     |\--_                        \____/___/
     |   |\-_                       |
     |   |   \_                     |
     |   |     \                    |
     |   |      \_                  |
     |   |        ----___           |
     |   |               \----------|
     /   |                     |     ----------""\
/"\--"--_|                     |               |  \
|_______/                      \______________/    )
                                              \___/

[Arvydas77]

OMG, how I've missed such a great opportunity with PIVX.

[Redni]

OMG, how I've missed such a great opportunity with PIVX.

It is never too late