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

[DRPD]

Since masternode owners (including me) will most probably not receive anything until a fix is available, we should compensate them for the lost profits. What do you guys think?

@berron you need to wait for the new wallet

the last payouts for my 50+ masternodes are from august 5, but i'm not asking for any compensation...
thats my risk and the dev's are working hard for this coin without any premine or compensation afaik

just my 2 cents.

[1715013379]

1715013379

[1715013379]

1715013379

[1715013379]

1715013379

[pjcltd]

Since masternode owners (including me) will most probably not receive anything until a fix is available, we should compensate them for the lost profits. What do you guys think?

@berron you need to wait for the new wallet

the last payouts for my 50+ masternodes are from august 5, but i'm not asking for any compensation...
thats my risk and the dev's are working hard for this coin without any premine or compensation afaik

just my 2 cents.

Spot on
we all know the risks in the coin
this issue will get sorted out.


thanks
Paul

[mxnsch]

i think you misquoted that one. I agree with the risk part. There is also the risk that people switch off masternodes and thats pretty high imho.

EDIT:

Spot on
we all know the risks in the coin
this issue will get sorted out.

I am not talking about a couple of days but compensation in case it takes longer.

You should know how people handle this otherwise since you switched off 100+ masternodes at least because people were not paying.

[tylerderden]

Compensation is pretty much the only way you will get anything since block 290200 or whenever the switch was, there are many forks so when a fix comes it will most likely start at the block where pos occurred, everything after will probly be invalid but who knows, we have awesome devs so I'm sure nobody is going to lose out much. And the good thing is nobody else will either so it should kick off with everyone on an even playing field.

[pjcltd]

i think you misquoted that one. I agree with the risk part. There is also the risk that people switch off masternodes and thats pretty high imho.

EDIT:

Spot on
we all know the risks in the coin
this issue will get sorted out.

I am not talking about a couple of days but compensation in case it takes longer.

You should know how people handle this otherwise since you switched off 100+ masternodes at least because people were not paying.

dont think thats the same really
if you dont pay for a service then you will get turned off
this is differant thay have a isse in the code lets let them sort it out.


thanks
Paul

[jakiman]

Last time something like this happen was during March where MN payments were higher than normal.
It was fixed but nothing was invalidated. It's all part of the fun. Code is open for all to see on github.

[presstab]

I am working with the DNET team to implement a fix to the node communication issue. We worked late into the night and got quite a bit done. Now we are in the testing phase. Hope to have some better information for you all soon. As of now, I would expect to consider anything after 259200 as not valid. I think best route going forward will be for us to make sure this fix works, then mint 10-20 PoS blocks and then hard checkpoint it into the wallet, then distribute the new version.

I feel bad, this is my error in the code. Sorry to let you all down.

[pjcltd]

I am working with the DNET team to implement a fix to the node communication issue. We worked late into the night and got quite a bit done. Now we are in the testing phase. Hope to have some better information for you all soon. As of now, I would expect to consider anything after 259200 as not valid. I think best route going forward will be for us to make sure this fix works, then mint 10-20 PoS blocks and then hard checkpoint it into the wallet, then distribute the new version.

I feel bad, this is my error in the code. Sorry to let you all down.

Hay
no problem these things happen
if you need any help from any of us just let sus know on here 

and thanks for taking the time to keep us informed 

thanks
Paul

[tylerderden]

I am working with the DNET team to implement a fix to the node communication issue. We worked late into the night and got quite a bit done. Now we are in the testing phase. Hope to have some better information for you all soon. As of now, I would expect to consider anything after 259200 as not valid. I think best route going forward will be for us to make sure this fix works, then mint 10-20 PoS blocks and then hard checkpoint it into the wallet, then distribute the new version.

I feel bad, this is my error in the code. Sorry to let you all down.

Allgood brother, I doubt anyone here is upset in the slightest. Masternodes with PoS shit this is a first, going OK under the circumstances. Except Nobody is panic selling goddamnit!!

[DRPD]

I am working with the DNET team to implement a fix to the node communication issue. We worked late into the night and got quite a bit done. Now we are in the testing phase. Hope to have some better information for you all soon. As of now, I would expect to consider anything after 259200 as not valid. I think best route going forward will be for us to make sure this fix works, then mint 10-20 PoS blocks and then hard checkpoint it into the wallet, then distribute the new version.

I feel bad, this is my error in the code. Sorry to let you all down.

thanks for your honest information and no problem man, we are all humans, and humans make mistakes ....
just take the time you need to fix the error and test the new version.

[berron]

I am working with the DNET team to implement a fix to the node communication issue. We worked late into the night and got quite a bit done. Now we are in the testing phase. Hope to have some better information for you all soon. As of now, I would expect to consider anything after 259200 as not valid. I think best route going forward will be for us to make sure this fix works, then mint 10-20 PoS blocks and then hard checkpoint it into the wallet, then distribute the new version.

I feel bad, this is my error in the code. Sorry to let you all down.

The only way to not fail it's not try it. I think that everyone involved in this coin from its early stage know that you were trying to get a new high to the Dashcoin scheme, and it would have its risk (first in something is always a risk, being this to land a rocket or to make the first POS wallet in the last bitcoin protocol). Big wallets in Bitrex are (unfortunately) not dumping so it's clear that almost everyone knows your honestity, professionality and work. Let's hope we can have that wallet working as soon as possible, if any testnet windows version can be run to help, don't hesitate to ask.

[jakiman]

I am working with the DNET team to implement a fix to the node communication issue. We worked late into the night and got quite a bit done. Now we are in the testing phase. Hope to have some better information for you all soon. As of now, I would expect to consider anything after 259200 as not valid. I think best route going forward will be for us to make sure this fix works, then mint 10-20 PoS blocks and then hard checkpoint it into the wallet, then distribute the new version.

I feel bad, this is my error in the code. Sorry to let you all down.

What happens to the coins that i withdrew from bittrex after block 259200?
It came through without issue .will i lose that?

[kbhutto]

I am working with the DNET team to implement a fix to the node communication issue. We worked late into the night and got quite a bit done. Now we are in the testing phase. Hope to have some better information for you all soon. As of now, I would expect to consider anything after 259200 as not valid. I think best route going forward will be for us to make sure this fix works, then mint 10-20 PoS blocks and then hard checkpoint it into the wallet, then distribute the new version.

I feel bad, this is my error in the code. Sorry to let you all down.

What happens to the coins that i withdrew from bittrex after block 259200?
It came through without issue .will i lose that?

That would be an issue.......I also did a couple of small transfers.

[presstab]

I am working with the DNET team to implement a fix to the node communication issue. We worked late into the night and got quite a bit done. Now we are in the testing phase. Hope to have some better information for you all soon. As of now, I would expect to consider anything after 259200 as not valid. I think best route going forward will be for us to make sure this fix works, then mint 10-20 PoS blocks and then hard checkpoint it into the wallet, then distribute the new version.

I feel bad, this is my error in the code. Sorry to let you all down.

What happens to the coins that i withdrew from bittrex after block 259200?
It came through without issue .will i lose that?

That would be an issue.......I also did a couple of small transfers.

I am not sure how you could have something go through after 259200. My guess is that you minted it into a transaction yourself and that it will be in the mempool waiting to get into a block once the update is ready.

Initial testing has gone well, I have a few nodes synced up to a PoS chain. Should have more details to you folks soon. I am more than happy to give up any staking rewards I have received in the process.

[kbhutto]

I am working with the DNET team to implement a fix to the node communication issue. We worked late into the night and got quite a bit done. Now we are in the testing phase. Hope to have some better information for you all soon. As of now, I would expect to consider anything after 259200 as not valid. I think best route going forward will be for us to make sure this fix works, then mint 10-20 PoS blocks and then hard checkpoint it into the wallet, then distribute the new version.

I feel bad, this is my error in the code. Sorry to let you all down.

What happens to the coins that i withdrew from bittrex after block 259200?
It came through without issue .will i lose that?

That would be an issue.......I also did a couple of small transfers.

I am not sure how you could have something go through after 259200. My guess is that you minted it into a transaction yourself and that it will be in the mempool waiting to get into a block once the update is ready.


Initial testing has gone well, I have a few nodes synced up to a PoS chain. Should have more details to you folks soon. I am more than happy to give up any staking rewards I have received in the process.

No.......I did two very small transfers from trex (both were successful). I am not worried about my coins as transactions are small........but what about transactions done by other users?

Don't make it another ETH please!

[presstab]

I am working with the DNET team to implement a fix to the node communication issue. We worked late into the night and got quite a bit done. Now we are in the testing phase. Hope to have some better information for you all soon. As of now, I would expect to consider anything after 259200 as not valid. I think best route going forward will be for us to make sure this fix works, then mint 10-20 PoS blocks and then hard checkpoint it into the wallet, then distribute the new version.

I feel bad, this is my error in the code. Sorry to let you all down.

What happens to the coins that i withdrew from bittrex after block 259200?
It came through without issue .will i lose that?

That would be an issue.......I also did a couple of small transfers.

I am not sure how you could have something go through after 259200. My guess is that you minted it into a transaction yourself and that it will be in the mempool waiting to get into a block once the update is ready.


Initial testing has gone well, I have a few nodes synced up to a PoS chain. Should have more details to you folks soon. I am more than happy to give up any staking rewards I have received in the process.

No.......I did two very small transfers from trex (both were successful). I am not worried about my coins as transactions are small........but what about transactions done by other users?

Don't make it another ETH please!

And the transactions were confirmed into a block?

There is no need for a reversal of transactions. Transactions are not dependent on the block. Bittrex, if they need to, can just prompt their wallet to rebroadcast the transactions.

[kbhutto]

I am working with the DNET team to implement a fix to the node communication issue. We worked late into the night and got quite a bit done. Now we are in the testing phase. Hope to have some better information for you all soon. As of now, I would expect to consider anything after 259200 as not valid. I think best route going forward will be for us to make sure this fix works, then mint 10-20 PoS blocks and then hard checkpoint it into the wallet, then distribute the new version.

I feel bad, this is my error in the code. Sorry to let you all down.

What happens to the coins that i withdrew from bittrex after block 259200?
It came through without issue .will i lose that?

That would be an issue.......I also did a couple of small transfers.

I am not sure how you could have something go through after 259200. My guess is that you minted it into a transaction yourself and that it will be in the mempool waiting to get into a block once the update is ready.


Initial testing has gone well, I have a few nodes synced up to a PoS chain. Should have more details to you folks soon. I am more than happy to give up any staking rewards I have received in the process.

No.......I did two very small transfers from trex (both were successful). I am not worried about my coins as transactions are small........but what about transactions done by other users?

Don't make it another ETH please!

And the transactions were confirmed into a block?

There is no need for a reversal of transactions. Transactions are not dependent on the block. Bittrex, if they need to, can just prompt their wallet to rebroadcast the transactions.

presstab explorer is not showing records for both transactions. However, I received both in my wallet and balance on trex was deducted accordingly. Could it be that presstab was on a different chain........but how come trex and my wallet were on same chain?

PS: I was on v2 wallet.....

[jakiman]

I am working with the DNET team to implement a fix to the node communication issue. We worked late into the night and got quite a bit done. Now we are in the testing phase. Hope to have some better information for you all soon. As of now, I would expect to consider anything after 259200 as not valid. I think best route going forward will be for us to make sure this fix works, then mint 10-20 PoS blocks and then hard checkpoint it into the wallet, then distribute the new version.

I feel bad, this is my error in the code. Sorry to let you all down.

What happens to the coins that i withdrew from bittrex after block 259200?
It came through without issue .will i lose that?

That would be an issue.......I also did a couple of small transfers.

I am not sure how you could have something go through after 259200. My guess is that you minted it into a transaction yourself and that it will be in the mempool waiting to get into a block once the update is ready.

Initial testing has gone well, I have a few nodes synced up to a PoS chain. Should have more details to you folks soon. I am more than happy to give up any staking rewards I have received in the process.

I did 1 small and 1 large withdraw from bittrex after block 259200 using v2 wallet.
It was done during the time when i was getting stake rewards. (minted) (still am)
It has over 1000 confirms so yeah, it would be an issue if i just lose it...  

Surely there must have been others who also withdrew after block 259200. (but maybe not on this forum)
That would mean they will also lose their coins. Hmm.

[kbhutto]

I am working with the DNET team to implement a fix to the node communication issue. We worked late into the night and got quite a bit done. Now we are in the testing phase. Hope to have some better information for you all soon. As of now, I would expect to consider anything after 259200 as not valid. I think best route going forward will be for us to make sure this fix works, then mint 10-20 PoS blocks and then hard checkpoint it into the wallet, then distribute the new version.

I feel bad, this is my error in the code. Sorry to let you all down.

What happens to the coins that i withdrew from bittrex after block 259200?
It came through without issue .will i lose that?

That would be an issue.......I also did a couple of small transfers.

I am not sure how you could have something go through after 259200. My guess is that you minted it into a transaction yourself and that it will be in the mempool waiting to get into a block once the update is ready.

Initial testing has gone well, I have a few nodes synced up to a PoS chain. Should have more details to you folks soon. I am more than happy to give up any staking rewards I have received in the process.

I did 1 small and 1 large withdraw from bittrex after block 259200 using v2 wallet.
It was done during the time when i was getting stake rewards. (minted) (still am)
It has over 1000 confirms so yeah, it would be an issue if i just lose it...  

Surely there must have been others who also withdrew after block 259200. (but maybe not on this forum)
That would mean they will also lose their coins. Hmm.

Yeah. We cannot just discard blocks after 259200 height. It may not be good for the coin. Don't repeat ETH mistakes.

[mikegi]

My wallet node was up to block 259390... on whatever chain...

My masternodes seem to be happily waiting at 259200 with
 "status" : "Masternode successfully started".

Any suggestions from the devs about what to do with currently running masternodes or what will be likely necessary steps one should take when the fix is ready?

Anyway, it is nice to see some action in github indicating a solution is in the works.