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

NorthPixel

sr. member

Activity: 314

Merit: 250

News from PosWallet should not significantly lower the price, but rather create a more distributed network.

coinwider

full member

Activity: 184

Merit: 101

Put the fun back into banking!

Quote from: borris123 on April 25, 2017, 03:12:57 AM

Quote from: coinwider on April 25, 2017, 03:01:43 AM

Quote from: coinwider on April 25, 2017, 02:24:21 AM

Quote from: DRPD on April 25, 2017, 02:11:10 AM

Quote from: coinwider on April 25, 2017, 01:31:33 AM

till yet i have used the 2.1.3.0 wallet version on LinuxMint 64bit Kernel 4.8.0-49-generic without any probs

updated yesterday to Pivx 2.2.0 wallet + sync from Scratch but now i always get the same error when starting pivx 2.2:

pivx-qt: main.cpp:2300: bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `hashPrevBlock == view.GetBestBlock()' failed.
Aborted

any advice what I can do? sync from Scratch did complete well...

edit: to be more clear, i've downloaded the correct linux version x86_64

no problem on ubunt 16.04 here with version 2.2.0. i would go to slack and ask for help there. i guess it has to do with mint?

nope i don't think it has to do with Mint - maybe it relies to the new 4.8 Kernel Version 49 which i just upgraded...
trying 4.8 46 now instead and will post progress

restarted with Kernel 4.8 Version 46 but the same error

pivx-qt: main.cpp:2300: bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `hashPrevBlock == view.GetBestBlock()' failed.
Aborted

i don't want to open a slack account, i'll gonna post it via an github issue..

The 2.2.0 qt has a memory leak problem. Presstab thinks he knows the prob. If you build from master source it may have been fixed as alot of new commits are on there.

The Daemon works fine no probs. You have to delete all block data and resync from scratch.

ah okay, thx for info. but i already resynced from scratch with the new wallet; but still have the problem

i wrote an issue on github https://github.com/PIVX-Project/PIVX/issues/148

borris123

hero member

Activity: 728

Merit: 500

Quote from: coinwider on April 25, 2017, 03:01:43 AM

Quote from: coinwider on April 25, 2017, 02:24:21 AM

Quote from: DRPD on April 25, 2017, 02:11:10 AM

Quote from: coinwider on April 25, 2017, 01:31:33 AM

till yet i have used the 2.1.3.0 wallet version on LinuxMint 64bit Kernel 4.8.0-49-generic without any probs

updated yesterday to Pivx 2.2.0 wallet + sync from Scratch but now i always get the same error when starting pivx 2.2:

pivx-qt: main.cpp:2300: bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `hashPrevBlock == view.GetBestBlock()' failed.
Aborted

any advice what I can do? sync from Scratch did complete well...

edit: to be more clear, i've downloaded the correct linux version x86_64

no problem on ubunt 16.04 here with version 2.2.0. i would go to slack and ask for help there. i guess it has to do with mint?

nope i don't think it has to do with Mint - maybe it relies to the new 4.8 Kernel Version 49 which i just upgraded...
trying 4.8 46 now instead and will post progress

restarted with Kernel 4.8 Version 46 but the same error

pivx-qt: main.cpp:2300: bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `hashPrevBlock == view.GetBestBlock()' failed.
Aborted

i don't want to open a slack account, i'll gonna post it via an github issue..

The 2.2.0 qt has a memory leak problem. Presstab thinks he knows the prob. If you build from master source it may have been fixed as alot of new commits are on there.

The Daemon works fine no probs. You have to delete all block data and resync from scratch.

coinwider

full member

Activity: 184

Merit: 101

Put the fun back into banking!

Quote from: coinwider on April 25, 2017, 02:24:21 AM

Quote from: DRPD on April 25, 2017, 02:11:10 AM

Quote from: coinwider on April 25, 2017, 01:31:33 AM

till yet i have used the 2.1.3.0 wallet version on LinuxMint 64bit Kernel 4.8.0-49-generic without any probs

updated yesterday to Pivx 2.2.0 wallet + sync from Scratch but now i always get the same error when starting pivx 2.2:

pivx-qt: main.cpp:2300: bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `hashPrevBlock == view.GetBestBlock()' failed.
Aborted

any advice what I can do? sync from Scratch did complete well...

edit: to be more clear, i've downloaded the correct linux version x86_64

no problem on ubunt 16.04 here with version 2.2.0. i would go to slack and ask for help there. i guess it has to do with mint?

nope i don't think it has to do with Mint - maybe it relies to the new 4.8 Kernel Version 49 which i just upgraded...
trying 4.8 46 now instead and will post progress

restarted with Kernel 4.8 Version 46 but the same error

pivx-qt: main.cpp:2300: bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `hashPrevBlock == view.GetBestBlock()' failed.
Aborted

i don't want to open a slack account, i'll gonna post it via an github issue..

coinwider

full member

Activity: 184

Merit: 101

Put the fun back into banking!

Quote from: DRPD on April 25, 2017, 02:11:10 AM

Quote from: coinwider on April 25, 2017, 01:31:33 AM

till yet i have used the 2.1.3.0 wallet version on LinuxMint 64bit Kernel 4.8.0-49-generic without any probs

updated yesterday to Pivx 2.2.0 wallet + sync from Scratch but now i always get the same error when starting pivx 2.2:

pivx-qt: main.cpp:2300: bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `hashPrevBlock == view.GetBestBlock()' failed.
Aborted

any advice what I can do? sync from Scratch did complete well...

edit: to be more clear, i've downloaded the correct linux version x86_64

no problem on ubunt 16.04 here with version 2.2.0. i would go to slack and ask for help there. i guess it has to do with mint?

nope i don't think it has to do with Mint - maybe it relies to the new 4.8 Kernel Version 49 which i just upgraded...
trying 4.8 46 now instead and will post progress

DRPD

legendary

Activity: 1148

Merit: 1001

Quote from: coinwider on April 25, 2017, 01:31:33 AM

till yet i have used the 2.1.3.0 wallet version on LinuxMint 64bit Kernel 4.8.0-49-generic without any probs

updated yesterday to Pivx 2.2.0 wallet + sync from Scratch but now i always get the same error when starting pivx 2.2:

pivx-qt: main.cpp:2300: bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `hashPrevBlock == view.GetBestBlock()' failed.
Aborted

any advice what I can do? sync from Scratch did complete well...

edit: to be more clear, i've downloaded the correct linux version x86_64

no problem on ubunt 16.04 here with version 2.2.0. i would go to slack and ask for help there. i guess it has to do with mint?

coinwider

full member

Activity: 184

Merit: 101

Put the fun back into banking!

till yet i have used the 2.1.3.0 wallet version on LinuxMint 64bit Kernel 4.8.0-49-generic without any probs

updated yesterday to Pivx 2.2.0 wallet + sync from Scratch but now i always get the same error when starting pivx 2.2:

pivx-qt: main.cpp:2300: bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `hashPrevBlock == view.GetBestBlock()' failed.
Aborted

any advice what I can do? sync from Scratch did complete well...

edit: to be more clear, i've downloaded the correct linux version x86_64

jordan coins

full member

Activity: 208

Merit: 100

The price will be back to $1

berron

hero member

Activity: 727

Merit: 501

Quote from: DRPD on April 24, 2017, 12:52:48 PM

Quote from: berron on April 24, 2017, 12:06:49 PM

Someone has updated the IPv6 multiple node arragement? I'm getting crazy trying to know what, where and haow decompress to update them... Huh

vultr 5 instance?

if yes shutdown all instances:

systemctl stop pivx_n1
systemctl stop pivx_n2
systemctl stop pivx_n3
systemctl stop pivx_n4
systemctl stop pivx_n5
sleep 15

download and extract the new binaries to a temp folder like this:

cd ~
wget https://github.com/PIVX-Project/PIVX/releases/download/v2.2.0/pivx-2.2.0-x86_64-linux-gnu.tar.gz
mkdir ~/ctempClient
tar -vxzf ~/pivx-2.2.0-x86_64-linux-gnu.tar.gz -C ~/ctempClient

optional save the old binaries:

mv /usr/local/bin/pivxd /usr/local/bin/pivxd_o
mv /usr/local/bin/pivx-cli /usr/local/bin/pivx-cli_o
mv /usr/local/bin/pivx-tx /usr/local/bin/pivx-tx_o
mv /usr/local/bin/pivx-qt /usr/local/bin/pivx-qt_o

copy the binaries to /usr/local/bin/ like this:

cp ~/ctempClient/pivx-2.2.0/bin/pivx* /usr/local/bin/

not sure if optional or not but i did it and would recommend to do it: delete the chain and load it from a 2.2.0 client for every instance

restart the deamons:

systemctl restart pivx_n1
sleep 5
systemctl restart pivx_n2
sleep 5
systemctl restart pivx_n3
sleep 5
systemctl restart pivx_n4
sleep 5
systemctl restart pivx_n5
sleep 5

remove archive and temp folder:

rm -R ~/ctempClient
rm pivx-2.2.0-x86_64-linux-gnu.tar.gz

restrat all nodes with controller wallet, after that you need to activate all nodes on vps too like this
pivx-cli -rpcport=444[xy] -rpcuser=[username] -rpcpassword=[pw] masternode start

xy is the instance number ofc

Thnaks a lot, DRPD.

bathrobehero

legendary

Activity: 2002

Merit: 1051

ICO? Not even once.

Quote from: endchat on April 24, 2017, 05:48:18 PM

Quote from: bitcoinsay on April 24, 2017, 04:35:42 PM

I think that with Gnosis PIVX has been given less chance of entering poloniex.

https://www.facebook.com/photo.php?fbid=613862918819876&set=p.613862918819876&type=3&theater

https://ibb.co/kiCg35

Poor level 2 fud.

mfgex

member

Activity: 68

Merit: 10

Quote from: aqzu on April 24, 2017, 08:01:29 PM

Quote from: endchat on April 24, 2017, 05:48:18 PM

Quote from: bitcoinsay on April 24, 2017, 04:35:42 PM

I think that with Gnosis PIVX has been given less chance of entering poloniex.

https://www.facebook.com/photo.php?fbid=613862918819876&set=p.613862918819876&type=3&theater

https://ibb.co/kiCg35

it is more like not official by poloniex that post that. look at that logo on write your comment. which means it is your id that published that comment, not polo.

lol caught him

aqzu

full member

Activity: 227

Merit: 100

Quote from: endchat on April 24, 2017, 05:48:18 PM

Quote from: bitcoinsay on April 24, 2017, 04:35:42 PM

I think that with Gnosis PIVX has been given less chance of entering poloniex.

https://www.facebook.com/photo.php?fbid=613862918819876&set=p.613862918819876&type=3&theater

https://ibb.co/kiCg35

it is more like not official by poloniex that post that. look at that logo on write your comment. which means it is your id that published that comment, not polo.

endchat

sr. member

Activity: 269

Merit: 250

Quote from: bitcoinsay on April 24, 2017, 04:35:42 PM

I think that with Gnosis PIVX has been given less chance of entering poloniex.

https://www.facebook.com/photo.php?fbid=613862918819876&set=p.613862918819876&type=3&theater

https://ibb.co/kiCg35

bitcoinsay

sr. member

Activity: 434

Merit: 255

Presale starts on 28th of April!

I think that with Gnosis PIVX has been given less chance of entering poloniex.

luka4x

member

Activity: 101

Merit: 10

Quote from: bathrobehero on April 24, 2017, 02:57:04 PM

Quote from: Redni on April 24, 2017, 01:33:34 PM

Bad news – PoSWallet:

"With the PIVX rewards system, it is more profitable for users to have PIVX in their own staking wallet, especially with > 10,000 as a masternode. Because of this, we are going to delist PIVX from POSWallet.com. Please start withdrawing your PIVX now - we will make sure all users have the ability to withdraw all of their coins. If you need a larger daily withdrawal amount, please open a support ticket. We apologize for the inconvenience this may cause, but think it is more important for the community as a whole to earn as much as they possible can staking."

I'd say it's good news. More home staking operation = more nodes and decentralization of funds instead of holding all coins at the mercy of a centralized service that is PoSwallet...

It's not ideal for people who don't run their computers 0-24 though. In that case pick up a cheap old laptop, format it, install OS, firewall, antivirus, PIVX and stake with the added benefit of the battery acting as a UPS for uninterrupted staking.

Or use a Raspberry Pi.

maybe is one of that reason why the price drop a bit, if i´m not mistaken dash had some no good news with masternodes reward...both coin with high hype...

bathrobehero

legendary

Activity: 2002

Merit: 1051

ICO? Not even once.

Quote from: Redni on April 24, 2017, 01:33:34 PM

Bad news – PoSWallet:

"With the PIVX rewards system, it is more profitable for users to have PIVX in their own staking wallet, especially with > 10,000 as a masternode. Because of this, we are going to delist PIVX from POSWallet.com. Please start withdrawing your PIVX now - we will make sure all users have the ability to withdraw all of their coins. If you need a larger daily withdrawal amount, please open a support ticket. We apologize for the inconvenience this may cause, but think it is more important for the community as a whole to earn as much as they possible can staking."

I'd say it's good news. More home staking operation = more nodes and decentralization of funds instead of holding all coins at the mercy of a centralized service that is PoSwallet...

It's not ideal for people who don't run their computers 0-24 though. In that case pick up a cheap old laptop, format it, install OS, firewall, antivirus, PIVX and stake with the added benefit of the battery acting as a UPS for uninterrupted staking.

Or use a Raspberry Pi.

Redni

sr. member

Activity: 370

Merit: 255

Bad news – PoSWallet:

"With the PIVX rewards system, it is more profitable for users to have PIVX in their own staking wallet, especially with > 10,000 as a masternode. Because of this, we are going to delist PIVX from POSWallet.com. Please start withdrawing your PIVX now - we will make sure all users have the ability to withdraw all of their coins. If you need a larger daily withdrawal amount, please open a support ticket. We apologize for the inconvenience this may cause, but think it is more important for the community as a whole to earn as much as they possible can staking."

shintosai

hero member

Activity: 756

Merit: 500

Quote from: The Crypto Baron on April 24, 2017, 08:13:42 AM

Quote from: bobitza202 on April 24, 2017, 07:52:06 AM

It's quite difficult to predict the price of a coin, but i know for sure there are lots of people trying to grab some cheap PIVX Grin

And one of those people is named "Poloneix" Wink

might possible being added if Polo have enough numbers of holdings, as they really making good earnings from adding new coins and pumped it inside their exchange its been a long time business and those who really understand the drill will continue buying this coin and wait for its rebound.

Fundamentals Of

sr. member

Activity: 2380

Merit: 366

Was there an ICO on PIVX? Damn too much noise on this coin and it's just getting noisier each day especially when many are predicting this will be added to Poloniex in few days. Too much volume and platform doesn't have big problems right now? I'll take a risk and ride the train.

DRPD

legendary

Activity: 1148

Merit: 1001

Quote from: berron on April 24, 2017, 12:06:49 PM

Someone has updated the IPv6 multiple node arragement? I'm getting crazy trying to know what, where and haow decompress to update them... Huh

vultr 5 instance?

if yes shutdown all instances:

systemctl stop pivx_n1
systemctl stop pivx_n2
systemctl stop pivx_n3
systemctl stop pivx_n4
systemctl stop pivx_n5
sleep 15

download and extract the new binaries to a temp folder like this:

cd ~
wget https://github.com/PIVX-Project/PIVX/releases/download/v2.2.0/pivx-2.2.0-x86_64-linux-gnu.tar.gz
mkdir ~/ctempClient
tar -vxzf ~/pivx-2.2.0-x86_64-linux-gnu.tar.gz -C ~/ctempClient

optional save the old binaries:

mv /usr/local/bin/pivxd /usr/local/bin/pivxd_o
mv /usr/local/bin/pivx-cli /usr/local/bin/pivx-cli_o
mv /usr/local/bin/pivx-tx /usr/local/bin/pivx-tx_o
mv /usr/local/bin/pivx-qt /usr/local/bin/pivx-qt_o

copy the binaries to /usr/local/bin/ like this:

cp ~/ctempClient/pivx-2.2.0/bin/pivx* /usr/local/bin/

not sure if optional or not but i did it and would recommend to do it: delete the chain and load it from a 2.2.0 client for every instance

restart the deamons:

systemctl restart pivx_n1
sleep 5
systemctl restart pivx_n2
sleep 5
systemctl restart pivx_n3
sleep 5
systemctl restart pivx_n4
sleep 5
systemctl restart pivx_n5
sleep 5

remove archive and temp folder:

rm -R ~/ctempClient
rm pivx-2.2.0-x86_64-linux-gnu.tar.gz

restrat all nodes with controller wallet, after that you need to activate all nodes on vps too like this
pivx-cli -rpcport=444[xy] -rpcuser=[username] -rpcpassword=[pw] masternode start

xy is the instance number ofc

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