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

[4x13]

dnet.presstab.pw is running the newest version

Awesome!! Thank You Presstab!!

[1715606676]

1715606676

[1715606676]

1715606676

[1715606676]

1715606676

[killerjoegreece]

what is the current coin supply?

[DRPD]

no offense jakiman but i'm waiting for ann correction which is necessary anyway if you're right (and i guess you are ) ....

No offense taken. I know I'm right. I agree that ANN needs to be corrected.

exactly because of the ann. infos my opinion was that i have about 3 weeks left to buy cheap coins

in fact i guess only 8 days left to reach my goal, damn i must stay calm

don't panic buy, don't panic buy, don't panic buy, stay frosty .... ...

Hopefully we will see one more dip around 450 before moooooooooooooon

Don't wait for the dump bro. You could miss the train.  The cool kids are marketbuying  

true already hard to get a decent amount below 600

@killerjoegreece i guess ~34 mio (8-9 mio to go until pow ends)

[jakiman]

what is the current coin supply?

Best to check yourself via block explorer.
http://presstab.pw/phpexplorer/DNET/

[berron]

no offense jakiman but i'm waiting for ann correction which is necessary anyway if you're right (and i guess you are ) ....

No offense taken. I know I'm right. I agree that ANN needs to be corrected.

exactly because of the ann. infos my opinion was that i have about 3 weeks left to buy cheap coins

in fact i guess only 8 days left to reach my goal, damn i must stay calm

don't panic buy, don't panic buy, don't panic buy, stay frosty .... ...

Hopefully we will see one more dip around 450 before moooooooooooooon

Don't wait for the dump bro. You could miss the train.  The cool kids are marketbuying  

true already hard to get a decent amount below 600

@killerjoegreece i guess ~34 mio (8-9 mio to go until pow ends)

Taking into account dev and community activity (high), the capitalization seems absurd, and if truly anonymous transaction is finally implemented, totally ridiculous. Lot of people holding (big wallets in Bittrex continue increasing)

[kokokoin]

Is there way to check how many nodes switched to version 1.1.0?

[SwedishGirl]

no offense jakiman but i'm waiting for ann correction which is necessary anyway if you're right (and i guess you are ) ....

No offense taken. I know I'm right. I agree that ANN needs to be corrected.

exactly because of the ann. infos my opinion was that i have about 3 weeks left to buy cheap coins

in fact i guess only 8 days left to reach my goal, damn i must stay calm

don't panic buy, don't panic buy, don't panic buy, stay frosty .... ...

Hopefully we will see one more dip around 450 before moooooooooooooon

Don't wait for the dump bro. You could miss the train.  The cool kids are marketbuying  

true already hard to get a decent amount below 600

@killerjoegreece i guess ~34 mio (8-9 mio to go until pow ends)

7 days is a lot of time in crypto. People get impatient all the time. I already own a lot, so if the price does not drop again, it's still OK for me.

[borris123]

no offense jakiman but i'm waiting for ann correction which is necessary anyway if you're right (and i guess you are ) ....

No offense taken. I know I'm right. I agree that ANN needs to be corrected.

exactly because of the ann. infos my opinion was that i have about 3 weeks left to buy cheap coins

in fact i guess only 8 days left to reach my goal, damn i must stay calm

don't panic buy, don't panic buy, don't panic buy, stay frosty .... ...

Hopefully we will see one more dip around 450 before moooooooooooooon

Don't wait for the dump bro. You could miss the train.  The cool kids are marketbuying  

true already hard to get a decent amount below 600

@killerjoegreece i guess ~34 mio (8-9 mio to go until pow ends)

Taking into account dev and community activity (high), the capitalization seems absurd, and if truly anonymous transaction is finally implemented, totally ridiculous. Lot of people holding (big wallets in Bittrex continue increasing)

alot of big wallets on bittrex but is that because not many players are in the game? got to think as well all the 9 mil locked in masternodes. How many people are actually running these? is it just a 18 people with 50 masternodes? I dont think there is many people involved atm. IF truly anonymous does get implemented and works we in for good ride

[StakeBox]

well dev team can you please clarify this and please correct if wrong in ann. post.
specs from official  ann. post are decisively for me and i guess for a lot of other people too.
thanks

Block number 151200 for PoW Block Reward drop was already confirmed by dev StakeBox. See this post:
https://bitcointalk.org/index.php?topic=1262920.msg14747320#msg14747320

<snip>
This is a mandatory update, everyone needs to be on the new version, 1.1.0.0, by block 151200, about 2 weeks from now, that is when the new block rewards will go into effect. Notices will be sent to all service providers shortly. Thanks for your patience, I know I said this would be done last night or this morning. Sorry for the delay guys.

Also, block number 151200 is stated as the block when 250 will drop to 50 on the OP already.
Second line of Coin Specs on the OP states: "PoW Block Reward: (block# 2-151200) 250 DNET (block# 151201-259200) 50 DNET"

Edit:
And for true proof, here's the source code snippet from 1.1.0.0.
https://github.com/Darknet-Crypto/Darknet/blob/master/src/main.cpp#L1550
It clearly shows PoW reduction at block # >=151200. Also, the numeric value "172800" doesn't even exist in the source code.
So yeah, s3v3n should correct the "PoW Rewards Breakdown" portion of the OP.

int64_t GetBlockValue(int nBits, int nHeight, const CAmount& nFees)
{
    int64_t nSubsidy = 0;
    if(nHeight == 0) {
        nSubsidy = 60001 * COIN;
    }
    else if(nHeight < 86400 && nHeight > 0) {
        nSubsidy = 250 * COIN;
    }
    else if(nHeight < 151200 && nHeight >= 86400) {
        nSubsidy = 225 * COIN;
    }
    else if(nHeight < 259200 && nHeight >= 151200) {
        nSubsidy = 45 * COIN;
    }
    else {
        nSubsidy = 0 * COIN;
    }      
        
    return nSubsidy + nFees;
}

int64_t GetMasternodePayment(int nHeight, int64_t blockValue)
{
    int64_t ret = 0;
    if(nHeight <= 43200) {
        ret = blockValue/5;
    }
    else if(nHeight < 86400 && nHeight > 43200) {
        ret = blockValue/(100/30);
    }
    else if(nHeight < 259200 && nHeight >= 86400) {
        ret = 50 * COIN;
    }
    else if(nHeight < 259200 && nHeight >= 151200) {
        ret = blockValue/2;
    }
    else {
        ret = 0 * COIN;
    }
    return ret;
}

Man, thank you jakiman for posting the relevant section of the code. I hate to do this, but upon looking at that post realized there was an error in the code. It is fixed now, and we just released a new version of the wallet with the fix. Line 1569 should have been else if(nHeight < 151200 && nHeight >= 86400) {, not else if(nHeight < 259200 && nHeight >= 86400) {. I actually noticed the problem when I was testing, I made the change locally, but it never got pushed. That would have caused some serious issues. I apologize to everyone, but you are going to need to update to the newer version, 1.1.0.1 before block 151200, which is in about 7.5 days. This is totally my fault, I feel like an ass, I hope you can all forgive me. Also, a big thanks again to jakiman for that post, without it the error probably would have gone unnoticed until it was too late. The new wallets are up on github, I think s3v3n has updated the OP to reflect the change.

[presstab]

Man, thank you jakiman for posting the relevant section of the code. I hate to do this, but upon looking at that post realized there was an error in the code. It is fixed now, and we just released a new version of the wallet with the fix. Line 1569 should have been else if(nHeight < 151200 && nHeight >= 86400) {, not else if(nHeight < 259200 && nHeight >= 86400) {. I actually noticed the problem when I was testing, I made the change locally, but it never got pushed. That would have caused some serious issues. I apologize to everyone, but you are going to need to update to the newer version, 1.1.0.1 before block 151200, which is in about 7.5 days. This is totally my fault, I feel like an ass, I hope you can all forgive me. Also, a big thanks again to jakiman for that post, without it the error probably would have gone unnoticed until it was too late. The new wallets are up on github, I think s3v3n has updated the OP to reflect the change.

Mistakes happen. Happy that someone found it before it got ugly.

[4x13]

Bittrex and Presstab have already updated to v1.1.0.1 Thank You guys!!

[trincaxt]

already updated

thanks !!

[IBGigglin]

Nice catch.

[jakiman]

Man, thank you jakiman for posting the relevant section of the code. I hate to do this, but upon looking at that post realized there was an error in the code. It is fixed now, and we just released a new version of the wallet with the fix. Line 1569 should have been else if(nHeight < 151200 && nHeight >= 86400) {, not else if(nHeight < 259200 && nHeight >= 86400) {. I actually noticed the problem when I was testing, I made the change locally, but it never got pushed. That would have caused some serious issues. I apologize to everyone, but you are going to need to update to the newer version, 1.1.0.1 before block 151200, which is in about 7.5 days. This is totally my fault, I feel like an ass, I hope you can all forgive me. Also, a big thanks again to jakiman for that post, without it the error probably would have gone unnoticed until it was too late. The new wallets are up on github, I think s3v3n has updated the OP to reflect the change.

Ah. I just noticed it now also. I didn't really check the masternode portion.
I just bolded 151200 without thinking much else to show the switch block.
Anyways, glad I helped(?) but really glad you noticed it as I didn't!

[mikegi]

Is there way to check how many nodes switched to version 1.1.0?

If it corresponds to the protocol version shown in masternode list, I suppose it is.

Code:

$ darknet-cli masternodelist full |grep 70106 |wc -l 
857

Code:

$ darknet-cli masternodelist full |grep 70107 |wc -l 
48

If the masternode's uptime affects one's payments. I suppose the most profitable strategy for one still running the older version is to wait until one gets the last expected higher reward from their masternode before upgrading. So waiting for a payout of 50 within about ~850 blocks from the change to smaller rewards. Not a big difference.

[4x13]

I know its a pain.. No one likes to update their masternodes and wallets, but it has to be done. Please.. Everyone start updating their masternodes. it will be a bumpy ride for everyone until at least 65% have updated... then things will smooth out.. so the quicker everyone updates the better.

here is what I use, takes about 10 seconds to do the update per masternode..

./darknet-cli stop && sudo rm -R darknetd && sudo rm -R darknet-cli && wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.1.0.1/darknetd && wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.1.0.1/darknet-cli && sudo chmod +x darknetd && sudo chmod +x darknet-cli && ./darknetd

put this entire string in your terminal windows when you are in the folder where the binaries are located..

[DRPD]

I know its a pain.. No one likes to update their masternodes and wallets, but it has to be done. Please.. Everyone start updating their masternodes. it will be a bumpy ride for everyone until at least 65% have updated... then things will smooth out.. so the quicker everyone updates the better.

here is what I use, takes about 10 seconds to do the update per masternode..

./darknet-cli stop && sudo rm -R darknetd && sudo rm -R darknet-cli && wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.1.0.1/darknetd && wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.1.0.1/darknet-cli && sudo chmod +x darknetd && sudo chmod +x darknet-cli && ./darknetd && ./darknetd

put this entire string in your terminal windows when you are in the folder where the binaries are located..

ok thanks already updating my 50mn's (almost done  )

i guess you have a little error at the end of the line ./darknetd && ./darknetd 2 times.
you maybe also want to check if the upgrade was successful after starting darknetd again so here is my update string (you can lower the 20 second sleep if you like):

./darknet-cli stop && sudo rm -R darknetd && sudo rm -R darknet-cli && wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.1.0.1/darknetd && wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.1.0.1/darknet-cli && sudo chmod +x darknetd && sudo chmod +x darknet-cli && ./darknetd && sleep 20 && ./darknet-cli getinfo

the upgrade was successful if you see:
"version" : 1010001, ....

Cheers and happy upgrading all  

[jakiman]

Thanks for those scripts.

I had to add extra sleep 60 after "./darknet-cli stop" as sometimes it would take a long time to stop.
Also, does darknet-tx need to be updated also?

[DRPD]

Thanks for those scripts.

I had to add extra sleep 60 after "./darknet-cli stop" as sometimes it would take a long time to stop.
Also, does darknet-tx need to be updated also?

good idea i noticed that too on some slow servers.

it was not necessary to update darknet-tx for the last update so i guess it is not necessary for the new update
i guess dev team will clarify this soon 

[DRPD]

ok i just noticed that i had to run masternode start-missing from controller wallet after upgrading my mn's

some are started successful the first time some are reporting an error the first time:
"result" : "failed",
 "errorMessage" : "Could not allocate vin

if i run masternode start-missing again it works and the error is gone

not sure if we have a problem here?

will check my mn's for the next 2  hrs  (have to leave office afterwards for a while) and run masternode start-missing regularly and report here if i notice more probs