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

[ronald0cz]

Hi, guys, newbie in this thread I have 2 questions. What is the difference between e.g. Dash and DNET? Where does DNET trade?

DASH is PoW and does not have a fully untraceable transaction.
DNET is PoS and goal is to achieve fully untraceable transactions.
Both utilizes masternodes. Currently trades mainly on Bittrex.

Thank you for answer!

[1715175790]

1715175790

[1715175790]

1715175790

[1715175790]

1715175790

[1715175790]

1715175790

[1715175790]

1715175790

[1715175790]

1715175790

[jakiman]

Hi, guys, newbie in this thread I have 2 questions. What is the difference between e.g. Dash and DNET? Where does DNET trade?

DASH is PoW and does not have a fully untraceable transaction.
DNET is PoS and goal is to achieve fully untraceable transactions.
Both utilizes masternodes. Currently trades mainly on Bittrex.

Thank you for answer!

Np. There is a much better answer by the devs that was posted few days ago on slack.

But yeah, it's essentially that and it has had active development since its launch.

Devs did warn us that it may be a rough ride but yeah, those who persevere may reap the benefit later.

[mikegi]

i also have a backup from a node in sync with info page from about a hour ago
just send me a pm if you need the link for download, maybe this will help

I've just restarted my other 10 masternodes which I've left untouched since it got stuck today.
5 out of 10 came match the MN info page. The other 5 do not. So I got a good copy now.
But yeah, this is with assumption that MN info page is indeed the correct chain. (I hope it is!)

lol we all hope so *fingers crossed*

A problem with peer connectivity I suppose. I am not up to the same height as the hash Jakiman
posted but I suppose we are forked again.

[hagie]

Restart of the 3 Masternodes and the controller wallet solve the stuck issue .. maybe because I still have the addnode from the last version change with the right chain ?!

regards

[DRPD]

restart of the wallet on nodes solved the problem only temporary

a lot of my nodes stuck again (there are more every minute) on different blocks: 325608, 325332, 325563, 325582 and so on ... once stuck the chain is not moving anymore even if i have 10+ connections.

maybe another restart will solve the problem again for some time, but i will now wait instead of wasting time  

jakiman are you in contact with the devs?
don't want to stress you but i like to know if somebody is working on the problem already - thanks

edit: windows wallet just stuck again too @325611

[jakiman]

I've posted the issue on slack so I'm sure when they wake up, they'll see and start working on it.

I don't have any special access to the devs more than anyone else here do unfortunately.

But yeah, timing is bad as issue happened while it was (and still is) very early morning in US where both devs are located.

P.S. I'm going to bed myself now. Hopefully I wake up to good news.

[jakiman]

I just tried syncing from my backup blockchain again and it matches the MN info page's hash! (although, still not sure if this is a good thing lol)

getblockhash 325702
3be928dce46d73cb04c5bf65cd248246865c10186682b55042cb5ef86b0785d4

getblockhash 325715
71f9da03b949742820b373dc94db5ee154bc790ad8d03d8679fe47b6e04e23fb

I just left my conf file as previously recommended: (although bantime is not needed anymore afaik)

Code:

addnode=108.61.151.69
addnode=173.245.158.8
bantime=50

Anyways, best to wait until we hear something more official from the devs.

[borris123]

I just tried syncing from my backup blockchain again and it matches the MN info page's hash! (although, still not sure if this is a good thing lol)

getblockhash 325702
3be928dce46d73cb04c5bf65cd248246865c10186682b55042cb5ef86b0785d4

getblockhash 325715
71f9da03b949742820b373dc94db5ee154bc790ad8d03d8679fe47b6e04e23fb

I just left my conf file as previously recommended: (although bantime is not needed anymore afaik)

Code:

addnode=108.61.151.69
addnode=173.245.158.8
bantime=50

Anyways, best to wait until we hear something more official from the devs.

thats the chain i aiming for although when going through my masternodes i sometimes go on this chain which is wrong i assume and start again



****************do not go off this chain***************************
 ./darknet-cli getblockhash 325553
6d2dc289f33089149e8de4cca71f77e1847cc8ed3829c5cf5b862f692a332d81
****************do not go off this chain***************************

[DRPD]

I just tried syncing from my backup blockchain again and it matches the MN info page's hash! (although, still not sure if this is a good thing lol)

getblockhash 325702
3be928dce46d73cb04c5bf65cd248246865c10186682b55042cb5ef86b0785d4

getblockhash 325715
71f9da03b949742820b373dc94db5ee154bc790ad8d03d8679fe47b6e04e23fb

I just left my conf file as previously recommended: (although bantime is not needed anymore afaik)

Code:

addnode=108.61.151.69
addnode=173.245.158.8
bantime=50

Anyways, best to wait until we hear something more official from the devs.

i use the same conf.
nevertheless more than 50% of my nodes are stuck again (at least not forking again) after working fine and in sync with info page for a few hrs after the restart.

only the devs can give us a proper solution. i guess you have not heard from them yet?

just not sure if i should wait a bit more or leaving the office now for today ....

[cryptohunter]

Shame this coin was not more stable I'm sure the market cap would be way higher if it was

[jakiman]

I think the issue may have started as a result of a code bug related to the updated seesaw mechanism which is supposed to start at block 325000. Although I'm no coder, from what I can see,  I think the operator was incorrectly set as there's no set logic for block 32500 when looking at the seesaw switch logic. I guess this caused us to all get stuck at block 324999.

https://github.com/Darknet-Crypto/Darknet/commit/6700079eed972831bd55179c029f0a2481e255f1#diff-7ec3c68a81efff79b6ca22ac1f1eabbaR1741

Code:

else if (nHeight < 325000) {
else if (nHeight > 325000) {

should be

Code:

else if (nHeight < 325000) {
else if (nHeight >= 325000) {

Feel free to correct me if I'm wrong. It's past midnight and my eyelids are becoming very heavy.

[StakeBox]

OK, guys. I haven't read back through the past few pages yet, I thought I should just throw a post up quick to let everyone know what's going on. Here is a direct quote of myself on slack:

Yeah, I am just getting to the bottom of the issue. As jakiman pointed out the seesaw change didn't account for block 325500, that was a really stupid mistake on my part. We were able to get around that by having everyone restart their wallets, I made a fix locally and ran it, and then everyone else could sync past that problem. Now the problem is that everyone is banning each other because they are not accepting one another's blocks. If we see a different masternode count then we will calculate a different valid masternode reward and refuse blocks from people who don't agree on the masternode count. I have disabled masternode reward enforcement for now, that will allow us to get back on the same chain. The main problem is determining which chain to consider valid. I am resyncing right now to see where I get, I would advise everyone to do the same, I think that should put us all on the same chain. So, load up a blockchain backup if you have one and resync from there.

If you have removed the bantime line from your darknet.conf, or naver added it, please add "bantime=50" in there. That will allow for a quick unbanning of the peers you have recently banned unjustly, and help us all get back on the same page.

[borris123]

OK, guys. I haven't read back through the past few pages yet, I thought I should just throw a post up quick to let everyone know what's going on. Here is a direct quote of myself on slack:

Yeah, I am just getting to the bottom of the issue. As jakiman pointed out the seesaw change didn't account for block 325500, that was a really stupid mistake on my part. We were able to get around that by having everyone restart their wallets, I made a fix locally and ran it, and then everyone else could sync past that problem. Now the problem is that everyone is banning each other because they are not accepting one another's blocks. If we see a different masternode count then we will calculate a different valid masternode reward and refuse blocks from people who don't agree on the masternode count. I have disabled masternode reward enforcement for now, that will allow us to get back on the same chain. The main problem is determining which chain to consider valid. I am resyncing right now to see where I get, I would advise everyone to do the same, I think that should put us all on the same chain. So, load up a blockchain backup if you have one and resync from there.

If you have removed the bantime line from your darknet.conf, or naver added it, please add "bantime=50" in there. That will allow for a quick unbanning of the peers you have recently banned unjustly, and help us all get back on the same page.

the chains we have been going off is the masternode info page. i have resynced them all to that. although from what i have seen there are a couple of others going but the

./darknet-cli getblockhash 325553

fca8b0fd86b80b6c5e966a0542f760c38b0752ad9b515f08f35f605530d754df

seems to be the one they sync into mostly which is the masternode info page sync



can we get confirmation that bittrex on the same chain before start moving stuff.

just done a test and bittrex on the same chain as well. we going off that one then ye?

[coinwider]

16:57:40

getblockhash 325925

6123bcf945e4aa11d63404d5360acaa96f452b8ee5cff64494f89b1f47bf49d9


same as MN payments hash

[StakeBox]

Yeah, seems the masternode info page is good, I am still resyncing, but s3v3n has resynced to that chain, seems to be the winner.

[B1tUnl0ck3r]

Same here (6123bcf945e4aa11d63404d5360acaa96f452b8ee5cff64494f89b1f47bf49d9)

and

getblockhash 326029

8878bcd2af42565858c5b7fc53dd479c58aba52e4bbef0d9a23ead5560f62cfe

more than 1000 MN !!!

[berron]

Yeah, seems the masternode info page is good, I am still resyncing, but s3v3n has resynced to that chain, seems to be the winner.

All my nodes and my controller wallet are in that chain, but some second ago something strage has happened in my controller wallet:

I have minted this:
Status: 6 confirmations
Date: 04/10/2016 18:26
From: unknown
To:
Credit: 40.49998960 DNET
Net amount: +40.49998960 DNET
Transaction ID: 82a5e2620fba30719661f5e1a177b5d695ef6ba71f2510c2b3d08e64690b4536-000

As suddenly there was no MN's competing for the reward 

EDIT: I'm in the same fork than bitunlocker

[kbhutto]

Mine is stuck

[coinwider]

Mine is stuck

the last 3 hours have been stable - but now my linux 64 wallet was on a fork or just some orphans (?) ; immediatley shut down and restarted without staking; waited a while till it completed to get the right MNs, blocks and budgets;

working again       (relying to MN payout page)

edit:  Stakebox or s3v3nh4cks, if you need the log files just tell me

[ccminer.net]

How long is the maturing time folks?