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

[boy2k]

Few of my masternodes are at wrong chains again. I hope it will end soon.

same...

[Rumhurius]

its ram related they said...
 

[mikegi]

For those who are having trouble... did you try this?

My masternodes and wallet have been fine since doing this.

Dev Update Snippet

New wallet is currently in the works that will implement some changes to prevent such exploit that caused much havoc yesterday.
Bittrex wallet is currently in maintenance mode. It will be back online in a day or so after the new wallet has been tested by devs.

In the meantime, make sure your wallet is at or just ahead of the MN info page's shown block and that the block hash matches.
If not, you need to resync with a backed up chain or from scratch with following lines in the darknet.conf. (no other addnodes)

Code:

addnode=173.245.158.8
addnode=68.108.10.35
bantime=50

MN Info Page = http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

[kokokoin]

For those who are having trouble... did you try this?

My masternodes and wallet have been fine since doing this.

Dev Update Snippet

New wallet is currently in the works that will implement some changes to prevent such exploit that caused much havoc yesterday.
Bittrex wallet is currently in maintenance mode. It will be back online in a day or so after the new wallet has been tested by devs.

In the meantime, make sure your wallet is at or just ahead of the MN info page's shown block and that the block hash matches.
If not, you need to resync with a backed up chain or from scratch with following lines in the darknet.conf. (no other addnodes)

Code:

addnode=173.245.158.8
addnode=68.108.10.35
bantime=50

MN Info Page = http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

Doing it now on my forked nodes.

[gulachov]

I am still seeing a bunch of wallets/nodes running on the bad chain. please check your block height and hash against either Presstabs BE, or the Stats page. The difficulty is also been lower than usual, so i assume many are not staking. feel free to stake away, and Obfuscate..

There will be a mandatory update coming shortly.. Keep an Eye out for our announcement.

Mine forked too. Waiting for the update.

[StakeBox]

Hey guys. The update is more or less ready to roll out. I would be interested in the debug.logs from you guys who are still forking just to make sure that it is caused by the issue that is fixed in this new release. I would rather hold off another day or say and make sure that the problems are solved than have to have another release soon after because something got missed. Thanks.

[jakiman]

Few of my masternodes are at wrong chains again. I hope it will end soon.

Mine forked too. Waiting for the update.

When was the last time you confirmed that you were on the correct chain?
Also, how are you confirming that you have really forked?

If you haven't resynced since last week with bantime of 50, your nodes would have forked last week when we had a network issue..
I have many wallets & masternodes and none of them has had any issues since the resync few days ago using bantime=50 in conf..

Just to be clear, being few blocks behind is OK and isn't due to a fork.
(it can take some time to catch up but it will eventually)

[NotMyFarm]

all good here
MN payout steady
staking
.... 

[jakiman]

Me too!

Meanwhile, devs are still testing the upcoming wallet on testnet.

[FogHorn_LegHorn]

I don't understand why there are so many forks? Never have I a coin with so many forks. fix ur shit man. jeez.

[tomahawkeer]

So what is the deal with exchanges all being under maintenance Is there still that many blockchain / wallet issues with this coin?

[DRPD]

So what is the deal with exchanges all being under maintenance Is there still that many blockchain / wallet issues with this coin?

i guess the exchanges are waiting for the new wallet release (testing atm afaik)

if you have the following 3 lines in conf file, forking should not be a issue:

addnode=173.245.158.8
addnode=68.108.10.35
bantime=50

[loveapple]

I am interested in this coin, please provide more details...

[berron]

I don't understand why there are so many forks? Never have I a coin with so many forks. fix ur shit man. jeez.

Maybe because this is really a new cryptoproject based in Dash but with new features and working mechanism and it's not the 500th clone of the same wallet with exactly the same functionalities?

You always can sell your share and try with other thing, man...

[4x13]

There will be a New Mandatory Release Shortly to address the issues we have experienced over the past week. We have been holding off on the release as we waited for the debug files for some people still having issues. We need everyones help when issues arise so we can diagnose and fix the issue. It's is really difficult to fix something we are not experiencing, so PM's us your debug.log files is a great help in that.

Again this release is mandatory, We will be pushing a protocol bump, so all masternodes will need to be restarted, and be on the same release.

fixes in this release;

- Addressed the Attack Vector for the Bloom Filters
- Tweaked the Seesaw Mechanism (The changes won't take effect until Block 325000)
    > Added more levels to smooth out the transition from one level to another.
- Working TestNet
- Some backend Tweaks


As soon as it is ready, I will build all the wallets and post them as usual.

Thanks for your help and understanding.

The exchanges will be back up after they update to this release.

s3v3n

[q327K091]

no problem, took out all master nodes from the circulation but sold nothing, also notice zcash is just around the corner, and anon tech will be back in a big way, always nice to see

thanks for the work on this, wonder if dash could be subject to a similar attack, but if so they can patch code based on dnet code, while dnet continues to be a bargain  

[borris123]

There will be a New Mandatory Release Shortly to address the issues we have experienced over the past week. We have been holding off on the release as we waited for the debug files for some people still having issues. We need everyones help when issues arise so we can diagnose and fix the issue. It's is really difficult to fix something we are not experiencing, so PM's us your debug.log files is a great help in that.

Again this release is mandatory, We will be pushing a protocol bump, so all masternodes will need to be restarted, and be on the same release.

fixes in this release;

- Addressed the Attack Vector for the Bloom Filters
- Tweaked the Seesaw Mechanism (The changes won't take effect until Block 325000)
    > Added more levels to smooth out the transition from one level to another.
- Working TestNet
- Some backend Tweaks


As soon as it is ready, I will build all the wallets and post them as usual.

Thanks for your help and understanding.

The exchanges will be back up after they update to this release.

s3v3n

Hope the mandatary update has not got a deadline for week. Going Vegas tomoz for 5 days and won't have access to change me nodes over

[dsutil]

The wallet on bittrex has been offline from a few days ago.

Any idea when will be online again?

Thanks.

[4x13]

All exchanges have been notified to update their wallets, so you should see them come online shortly.

[kokokoin]

I would be interested in the debug.logs from you guys who are still forking

Sorry, didn't keep debug files. The issue was with masternodes which didn't forked first day or two, they did it few days later. Now i resynced all my MN's and they are working ok for 2 days.