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

Wallets online: https://github.com/Darknet-Crypto/Darknet/releases/tag/v2.0.3.0

For linux command line linux ;


+ https://bitcointalksearch.org/topic/m.15829838 with v2.0.3.0 + ALWAYS BACKUP YOUR WALLET.DAT

Cheers!

Thanks. Once the 2 files in github are put up for the scripts, I'll start updating my MNs.

Thanks for your hard work, s3v3nh4cks! It would be great if you could also share new chaindata and blocks data for the newcomers.

Everyone really needs to get on the same page with all this, even after we just released this an hour ago, people are already trying to use old chains... if you don't know if you have a good chain to start with, start from scratch...

I will be posting the latest wallets shortly, then off to bed for me..

New source is up, building wallets now, v2.0.3.0

Bring all your wallets, lets see if we can break it again.

delete the chain you have...

use the same nodes in your config file as before

connect=72.49.184.206
connect=68.227.30.210
connect=74.118.192.18
connect=138.68.50.249
connect=173.245.157.244
connect=173.245.158.8
connect=coin-server.com
connect=24.119.187.242
connect=178.254.23.111

delete your peers file just in case..

Do Not use any other chain than this one...

https://www.dropbox.com/s/njdjxmsvhwh6njf/.darknet.zip?dl=0

Restart your wallet, and sync up before enabling staking..


Note to everyone, if you enter getblockhash 259280 and don't get d363a8592e5391df7b9a9b2c62012724f3c22c0bebfdf3dae27a34f997f7ab66 you are on the wrong chain. sync from scratch.

I've been making mad MN & PoS rewards every update also lol.

Definitely good that trex has been stopped. Makes it easier to roll back.

All masternodes nodes and peers down, let the remaining masternodes continue into a hundred forks of Darknet PoS Classic 1 to n.

Just do it, don't look at the balance and and transactions,  erase those old blockchains.

Looking forward to PoS at 259200 again... maybe keeping the PoS  and Masternode reward low for a month would  help. For example 10 for proposals and 5 DNET divided between MN and PoS.

thanks for the info.
i think this is the only good solution. we wait ....

oh boy, switching to pos seems to have caused a shit show. As i am on the correct chain but my MN is getting mad rewards. would be a shame if the roll back killed them... good job on stopping trex deposits/withdraws

agree
switched everything off (not to confuse this any more than nessacery)
waiting for next version

Edit
we should get onto that soon 
http://bitcoinist.net/new-research-suggests-dark-net-markets-are-still-growing/

Yeah. Apparently the MN info page is on the wrong chain also as the devs. So it's still a mess right now.

Devs are looking at ways to ensure the next new wallet will only connect and/or download from a certain chain via hash verification.
Anyways, after the last 3 updates, last thing we want is for another round of multi-forks. So we'll just have to wait more this time.

That's correct. You just need some unlocked DNET in wallet & have the wallet unlocked to stake.
(Settings->Unlock Wallet->check "for anonymization only"->Enter passphrase->OK)

AFAIK, the PoS is based on BC PoS v2. Not sure about the stake times.

Guys, I have seen some of you saying that you're minting AND doing MN, how do we mint from wallet..? Is it just keeping the dnet in wallet and unlock it for minting? how long does minting takes?

cool , np at all, solid update.. suspending all master nodes even though they by a miracle  are staking, although I can't send em back to the mother ship

Yeah. I'm no linux guy nor a coder but having 10+ masternode consoles on screen synchronized made me feel like an uber geek. lol

Had to google ClusterSHISH.... thought it was a misspelling... good that there is something like clusterssh for Windows users. :-)

same here

The problems syncing could be due to problems with checking the proof of stake, or verifying blocks.

I set up one node to sync using "connect=" from 5 masternodes that are on the same chain.
I assume the masternode would all send the same block updates and there should be no differing headers)
The syncing got stuck about 100 blocks from where the masternodes were. (stuck on block 261687... 9278bbfb89902faee60e0b1a44d6b53616915168aae893b7d8c2ef4e1268aa60 )

If one is not able to sync from 0 blocks (without downloading a blockfile), reliably, then something is seriously broken.

It would be interesting to know if master nodes are paying on the chain that the are on only, or both chains. I haven't looked into how masternodes work in detail,I suppose they check, sign and send transactions based on the fork that they are on, and these are verified by other masternodes based on their version of the chain. Also, it's possible that a masternode can exist on one fork and not the other if it's transaction has been spent on one chain and not on the other or if the masternode transaction only exists on one fork (created after forking). 
So we end up with masternodes disagreeing.

DarkCoin / Dash has had at least this fork:
https://www.dash.org/forum/threads/issues-with-masternode-payments-fork.858/

I noticed that these messages stop appearing in the logs when the syncing freezes:


My  guess is that at some point there are too many orphan blocks to sort out and it becomes impossible to proceed.  


Good to hear! I think a roll back to 259200 would be fair. (At least, it would prevent having to choose a chain and associated disappointments)

I'll stop digging through git and sleep.

Yeah, I spent hours and hours for past few days with v2.0.0.0, v2.0.1.0 and v2.0.2.0.
Each time updating all my wallets and masternode multiple times. Wasn't fun.

But I did learn a few things to do it quicker using scripts, clustershish etc.
So yeah, new skill earned at least. Now I'm ready for next update.