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

[mikegi]

Went through the same procedure as setting up my other masternodes.

Using the latest version...
    "version" : 2010203,
    "protocolversion" : 70701,
    "walletversion" : 61000,

Sent 10000 to the address, made the private key... updated masternode.conf, restarted wallet.

The transaction does show up in this list "darknet-cli listlockunspent"

But is not in in the list "darknet-cli  masternode outputs"

Unsurprisingly, trying to start the masternode shows...

"errorMessage" : "Could not allocate vin ...... for masternode ........onion:51472"

Any ideas what went wrong here?

I'm going to try a fresh install and regenerate my wallet from a dump.

Any ideas about how to disable staking?  This is a feature request.

I wouldn't want the wallet to stake transactions from my running masternode before I can lock the transactions

EDIT: From the logs, it looks like the TXs from masternode.conf are parsed

Some ideas.
- start with "maxconnections=0"

EDIT: this does not disable p2p connections

I guess "darknet-cli setstakesplitthreshold" would not be useful.

EDIT: Well at least the wallet conflicts are fixed.

[jakiman]

hmm i guess more than 50% of my masternodes dropped out of payment ....

something has happend on saturday, if i check the nodes not getting payments anymore they are all in sync,  "status" : "Masternode successfully started" and controller wallet says "status" : "ENABLED" and tx shows up in masternode list.

not sure what to do but something is wrong ..

Luckily I only had about 4 masternodes that had its sync stuck over the last few days.
I just stopped/started the darknetd and it caught right back up. No biggie really.

Also, I just got back from work and checked my masternode that couldn't start up.
It's back up! I guess i didn't wait long enough for it to update its masternode list.

[borris123]

hmm i guess more than 50% of my masternodes dropped out of payment ....

something has happend on saturday, if i check the nodes not getting payments anymore they are all in sync,  "status" : "Masternode successfully started" and controller wallet says "status" : "ENABLED" and tx shows up in masternode list.

not sure what to do but something is wrong ..

Luckily I only had about 4 masternodes that had its sync stuck over the last few days.
I just stopped/started the darknetd and it caught right back up. No biggie really.

Also, I just got back from work and checked my masternode that couldn't start up.
It's back up! I guess i didn't wait long enough for it to update its masternode list.

how do you know they dropped out? mine show enabled? that mean they all still working?

[DRPD]

hmm i guess more than 50% of my masternodes dropped out of payment ....

something has happend on saturday, if i check the nodes not getting payments anymore they are all in sync,  "status" : "Masternode successfully started" and controller wallet says "status" : "ENABLED" and tx shows up in masternode list.

not sure what to do but something is wrong ..

Luckily I only had about 4 masternodes that had its sync stuck over the last few days.
I just stopped/started the darknetd and it caught right back up. No biggie really.

Also, I just got back from work and checked my masternode that couldn't start up.
It's back up! I guess i didn't wait long enough for it to update its masternode list.

how do you know they dropped out? mine show enabled? that mean they all still working?

because i got no payments for more than 48 hrs for 30+ of my mn's even if they are in sync, enabled and successfully started ...
edit: ofc all running with newest version  ...

[jakiman]

how do you know they dropped out? mine show enabled? that mean they all still working?

Just some of the things to check are in this post: https://bitcointalk.org/index.php?topic=1262920.msg16132899#msg16132899
I also sometimes check the transactions tab and go through each masternode alias (e.g. MN01) to see if it's getting paid daily.

[NotMyFarm]

how do you know they dropped out? mine show enabled? that mean they all still working?

Just some of the things to check are in this post: https://bitcointalk.org/index.php?topic=1262920.msg16132899#msg16132899
I also sometimes check the transactions tab and go through each masternode alias (e.g. MN01) to see if it's getting paid daily.

mine look all good (enabled) but no payments in the last 12 hours

[mikegi]

Went through the same procedure as setting up my other masternodes.

Using the latest version...
    "version" : 2010203,
    "protocolversion" : 70701,
    "walletversion" : 61000,

Sent 10000 to the address, made the private key... updated masternode.conf, restarted wallet.

The transaction does show up in this list "darknet-cli listlockunspent"

But is not in in the list "darknet-cli  masternode outputs"

Unsurprisingly, trying to start the masternode shows...

"errorMessage" : "Could not allocate vin ...... for masternode ........onion:51472"

Any ideas what went wrong here?

I'm going to try a fresh install and regenerate my wallet from a dump.

Any ideas about how to disable staking?  This is a feature request.

I wouldn't want the wallet to stake transactions from my running masternode before I can lock the transactions

EDIT: From the logs, it looks like the TXs from masternode.conf are parsed

Some ideas.
- start with "maxconnections=0"

EDIT: this does not disable p2p connections

I guess "darknet-cli setstakesplitthreshold" would not be useful.

EDIT: Well at least the wallet conflicts are fixed.

Turns out that the 10000 DNET was used to pay a 40 DNET fee in the same block.... perhaps to do with having obfuscation enabled.

So what have I learned...

Transactions shown by "darknet-cli listlockunspent" might already be spent or might not even exist
(Try putting a fictional txid into masternode.conf )

Transactions listed in masternode.conf will be locked when starting the node.

"darknet-cli masternode list-conf" does exactly what it says... Print's the contents of masternode.com at the time dartknetd was rund in JSON format  as well as printing the status of the node.

[StakeBox]

Went through the same procedure as setting up my other masternodes.

Using the latest version...
    "version" : 2010203,
    "protocolversion" : 70701,
    "walletversion" : 61000,

Sent 10000 to the address, made the private key... updated masternode.conf, restarted wallet.

The transaction does show up in this list "darknet-cli listlockunspent"

But is not in in the list "darknet-cli  masternode outputs"

Unsurprisingly, trying to start the masternode shows...

"errorMessage" : "Could not allocate vin ...... for masternode ........onion:51472"

Any ideas what went wrong here?

I'm going to try a fresh install and regenerate my wallet from a dump.

Any ideas about how to disable staking?  This is a feature request.

I wouldn't want the wallet to stake transactions from my running masternode before I can lock the transactions

EDIT: From the logs, it looks like the TXs from masternode.conf are parsed

Some ideas.
- start with "maxconnections=0"

EDIT: this does not disable p2p connections

I guess "darknet-cli setstakesplitthreshold" would not be useful.

EDIT: Well at least the wallet conflicts are fixed.

Turns out that the 10000 DNET was used to pay a 40 DNET fee in the same block.... perhaps to do with having obfuscation enabled.

So what have I learned...

Transactions shown by "darknet-cli listlockunspent" might already be spent or might not even exist
(Try putting a fictional txid into masternode.conf )

Transactions listed in masternode.conf will be locked when starting the node.

"darknet-cli masternode list-conf" does exactly what it says... Print's the contents of masternode.com at the time dartknetd was rund in JSON format  as well as printing the status of the node.

Glad to see that you found the issue. Yeah, the 40 DNET is the collateral fee for obfuscation. It is actually still in your wallet, and can be found with coin control. My guess is that when you created the 10K transaction you spent the collateral, and it was created again. In the future use coin control when creating your masternode vins to avoid similar issues.

Also, there are 2 ways to stop staking, You can enter "reservebalance true 9999999" in the console to temporarily disable it while setting up a new masternode then enter "reservebalance false" when you are finished. A more permanent solution is to add "staking=0" to your darknet.conf, although there is not much point in using that method, we had to add that for bittrex, when you have more than 9999999 coins the reserve balance command is useless.

On a side note, I haven't had any issues with my masternodes, and would be interested in some debug.logs the next time anyone has issues like the past several posts have mentioned.

[mikegi]

......

Glad to see that you found the issue. Yeah, the 40 DNET is the collateral fee for obfuscation. It is actually still in your wallet, and can be found with coin control. My guess is that when you created the 10K transaction you spent the collateral, and it was created again. In the future use coin control when creating your masternode vins to avoid similar issues.

Also, there are 2 ways to stop staking, You can enter "reservebalance true 9999999" in the console to temporarily disable it while setting up a new masternode then enter "reservebalance false" when you are finished. A more permanent solution is to add "staking=0" to your darknet.conf, although there is not much point in using that method, we had to add that for bittrex, when you have more than 9999999 coins the reserve balance command is useless.

On a side note, I haven't had any issues with my masternodes, and would be interested in some debug.logs the next time anyone has issues like the past several posts have mentioned.

Thanks,with the exception of those 2 weeks in August and my first masternode,  I haven't had a problem until now.
(
I'm using the CLI only...have thought about using the GUI wallet but I prefer to keep things lightweight. Coin control could be handy. I haven't felt a need for it yet.

I found the coins, with the help of listunspent and grep... and the blockexplorer. The unspent 9959.9something instead of unspent 10000 put me on the right track.

Perhaps you could clear up one thing about (remote) masternodes and controller wallets. I have had mixed luck with being able to restart a masternode without having to start it from the controller wallet.

When the the controller has not been restarted since the last time I have reactivated the masternode. The state changes as follows ( output from darknet-cli masternode status)

- error: {"code":-28,"message":"Loading block index..."}
- "status" : "Node just started, not yet activated"
- "status" : "Masternode successfully started"

When the controller has been restarted, at that masternode has not been activated. So, miss some mn payments and need to restart.

- error: {"code":-28,"message":"Loading block index..."}
- "status" : "Node just started, not yet activated"
- "status" : "Not capable masternode: Hot node, waiting for remote activation."

I guess there is some information in the controller about the masternode that is not stored persistently or does the controller need to sync with the network?  I have normally kept the controller running... and sometimes held off upgrading the controller in order to keeps the masternodes up.

[4x13]

Glad we did the 1st POS Superblock very well!  Our coins are now cut to stone - err - written to the blockchain.


Looking forward to do more obfuscation -  500/2 best option still?



And maybe some of you know www.distrowatch.com - as a good resource of open source - operating systems. There is a new sister project out now, which covers cryptocoinz and -surprise-  DNET is yet listed their.


Please check it out - www.cryptocoin.cc



 

You can set it to any amount, I would say 500/2 would be a minimum. I have mine set at 10k/8. When that is able to complete, we have a decent amount of people participating.

[coinwider]

Glad we did the 1st POS Superblock very well!  Our coins are now cut to stone - err - written to the blockchain.


Looking forward to do more obfuscation -  500/2 best option still?



And maybe some of you know www.distrowatch.com - as a good resource of open source - operating systems. There is a new sister project out now, which covers cryptocoinz and -surprise-  DNET is yet listed their.


Please check it out - www.cryptocoin.cc



 

You can set it to any amount, I would say 500/2 would be a minimum. I have mine set at 10k/8. When that is able to complete, we have a decent amount of people participating.

TY, will increase the amount in the wallets.


BTW - Linux PPA updates work like a charm.

[berron]

What wallet version were you using?

DarkNet Core version v2.1.2.3-cb528cd (64-bit)

I think about block 298830 I forked and during more than one hour my wallet saw no new blocks was not able to mint a block neither. In that moment, first forked block was minted and I started to have a new minted block every few minutes, seconds, till I discover the issue. I erased everything except wallet.conf and masternode.conf and things were back to normal. Now I have the wallet working normally, minting and receiving MN payments at the expected frequency.
Salute

After analysing my "fork" a bit more, thing start to seem more interesting. Look at this image:



When my wallet started to stack like crazy two of the transactions were accepted. Very strange

Salute

hi berron,

watching yours wallet data doesn't look well.

You should clean your wallet.dat of that orphans, as s3v3nh4cks adviced to .cryptic.



First of all - backup your wallet.dat!!!

Go to - TOOLS - WALLET-REPAIR   and  then choose   3rd option called   "zapwallettxes=1"
It checks the whole blockchain for vaild transactions and keeps your personalized data - e.g. named wallet addresses

That should do it.



With the Windows wallet version 2.1.2.1 I had some stake problems, but after zapwallettxes=1 function and loading the snapshot from www.cryptochainer.com  (http://108.61.216.160/cryptochainer.chains/chains/DarkNet_blockchain.zip) it was done.

The important part was to show that orphans just in case the devs having interest in the issue, after that I zapped my wallet to get rid of them. Seems that it's not very important, but you know, after the POS transition problems i preferred to do my best to notice it to the devs.

Thanks and salute.

[coinwider]

What wallet version were you using?

DarkNet Core version v2.1.2.3-cb528cd (64-bit)

I think about block 298830 I forked and during more than one hour my wallet saw no new blocks was not able to mint a block neither. In that moment, first forked block was minted and I started to have a new minted block every few minutes, seconds, till I discover the issue. I erased everything except wallet.conf and masternode.conf and things were back to normal. Now I have the wallet working normally, minting and receiving MN payments at the expected frequency.
Salute

After analysing my "fork" a bit more, thing start to seem more interesting. Look at this image:



When my wallet started to stack like crazy two of the transactions were accepted. Very strange

Salute

hi berron,

watching yours wallet data doesn't look well.

You should clean your wallet.dat of that orphans, as s3v3nh4cks adviced to .cryptic.



First of all - backup your wallet.dat!!!

Go to - TOOLS - WALLET-REPAIR   and  then choose   3rd option called   "zapwallettxes=1"
It checks the whole blockchain for vaild transactions and keeps your personalized data - e.g. named wallet addresses

That should do it.



With the Windows wallet version 2.1.2.1 I had some stake problems, but after zapwallettxes=1 function and loading the snapshot from www.cryptochainer.com  (http://108.61.216.160/cryptochainer.chains/chains/DarkNet_blockchain.zip) it was done.

The important part was to show that orphans just in case the devs having interest in the issue, after that I zapped my wallet to get rid of them. Seems that it's not very important, but you know, after the POS transition problems i preferred to do my best to notice it to the devs.

Thanks and salute.

allright, got you berron
keep the Node running

[NotMyFarm]

checked my Debug Logs
and have a couple of no payment MN's with

2016-09-19 23:26:25 mnb - Got bad Masternode address signature
2016-09-19 23:26:25 Misbehaving: 142.4.193.108:51472 (0 -> 100) BAN THRESHOLD EXCEEDED
2016-09-19 23:26:25 connect() to [2001:470:1f11:1d4:6438:30ff:fe38:6561]:51472 failed: No route to host (65)
2016-09-19 23:26:27 receive version message: /DarkNet Core:2.1.2.3/: version 70701, blocks=305792,

??
what to do with these naughty boys  

Send Debug Log to Stakebox.

[jakiman]

Official Bounty List

This list was posted on slack by StakeBox. I'm posting it here again for visibility.

[20k DNET] Port Bittrex trading (In Wallet) from Transfercoin to Darknet
[20k DNET] Port Masternode Tracking (In Wallet) from Transfercoin to Darknet
[20k DNET] Port Encrypted Chat (In wallet) from Transfercoin to Darknet
[20k DNET] Port an Announcements Page (In Wallet) from SDC Wallet to Darknet. Include the php form to send the announcements fromo ur servers
[20k DNET] Port ability to use external Themes into Darknet Wallet from HYPERSTAKE

All that is needed to get the bounty is to create a new branch on the official Github, do the coding and submit your pull request.
Then once the devs test & merges it, they will send you your DNET! 20K DNET is enough for 2 masternodes or can just trade it.

If you have something different that you can provide to DNET devs or community, feel free to PM s3v3nh4cks or Stakebox.
If it's a bigger job that's potentially worth a lot more, create a budget proposal and let the masternode holders vote!

P.S. These will be listed on the OP along with any new ones. So please check the OP from time to time!

[NotMyFarm]

mixing like crazy
6k - 2 Rounds done

updating to
6k - 4 Rounds next

[kokokoin]

If i lock coins in obfuscation, they will not stake?

[borris123]

If i lock coins in obfuscation, they will not stake?

dev said it doesnt affect it. you will not be able to transfer coins when they locked in that tho i believe.

[coinwider]

mixing like crazy
6k - 2 Rounds done

updating to
6k - 4 Rounds next

me 4k - 4 Rounds --- and 50% already mixed in 12 hours --- mixing is now miles faster than my inital 500/2 with a duration of 2 days

[NotMyFarm]

mixing like crazy
6k - 2 Rounds done

updating to
6k - 4 Rounds next

me 4k - 4 Rounds --- and 50% already mixed in 12 hours --- mixing is now miles faster than my inital 500/2 with a duration of 2 days

 
81% done here
race me/you ?!