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

[borris123]

If your only using 1 node this guide on the main page is spot on. cant see how you can make it any simpler.


Step 1: First, open the console of your wallet and create an address for your masternode, do this by entering
"getaccountaddress MN". You can replace "MN" with whatever you would like to name your masternode.

Step 2: Send 10000DNET to the address you just created. It must be exactly 10000, in one transaction.

Step 3: Execute "masternode genkey" in your wallet's console.

Step 4: Open the darknet.conf folder in the data directory for your wallet

This is located as deafult C:\Users\YOUR NAME\AppData\Roaming\DarkNet

, edit it like so:

rpcuser=long random username
rpcpassword=longer random password
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
masternode=1
masternodeprivkey=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Replace the Xs with the key generated when you ran "masternode genkey" in step 3.

Step 5: Save the darknet.conf file, close, and restart your wallet.

Step 6: In the console of your wallet enter "masternode start", assuming everything went well you should see a
message letting you know your masternode has been started successfully.

If you are running multiple wallets you need to get a VPS.


From the very begining, on your laptop in the console enter "masternode genkey" twice for 2 masternodes, and enter
"getaccountaddress MN1" and "getaccountaddress MN2", the MN1 and MN2 could be substituted with any name
you would like to call the masternode addresses. Recommend just make a load of addresses for later deployment of more nodes without having to backup wallet all the time when you add new address.

Make a note of the priv keys in a word document in order you executed the command. When using getaccountaddress MN* copy this address and paste it next to the priv key so not to confuse them all.

e.g. This would be the first priv key generated followed by the address you are using for this priv key which would be MN1 address

88dkgjsooxf2nZbpNHXukjda03JySp9QG3fD1s586jdkjsgSFLhqYbd    DCgDbyXpfr49dj3Vtf4ddgJ4awSgroosAaA

Send 10k DNET to each of the addresses generated in step 1, making sure to send exactly 10k, in
one transaction to each. I purchased them from bittrex but if you already have coins in a wallet I would recommend sending them to there so you can transfer 10k exactly.

Once it is confirmed with bittrex it will have your transaction ID wen you click the + on the withdrawn coins that you need for your masternode conf. Whichever Address you have sent it to paste this next to the address of the word document so not to confuse which address is which transcaction.

e.g. for the first one MN1

88dkgjsooxf2nZbpNHXukjda03JySp9QG3fD1s586jdkjsgSFLhqYbd    DCgDbyXpfr49dj3Vtf4ddgJ4awSgroosAaA     6b80fc205c2551d2e0d1af9c2861afa705d6433jhdsojgsog94093cd25d88ac

Once it has been confirmed a couple of times, execute "masternode outputs" in the console of your laptop wallets.

Look for the transaction ID and see which number is next to it whether that is a 1 or a 0. so if this was a 0 the eg would now look like this once you press space and 0.

88dkgjsooxf2nZbpNHXukjda03JySp9QG3fD1s586jdkjsgSFLhqYbd    DCgDbyXpfr49dj3Vtf4ddgJ4awSgroosAaA     6b80fc205c2551d2e0d1af9c2861afa705d6433jhdsojgsog94093cd25d88ac 0

You now have everything you need and will need to setup a VPS to get the IP. To do this go to the following link and register for a darknet masternode. It is not automatic so its when Paul the owner sees it and activates it.

http://my.mp-hosting.co.uk/aff.php?aff=004

Once activated login with the details on the node with Putty http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

Once you are logged in type in

root (press enter)
password (press enter)
nano ~/.darknet/darknet.conf (press enter)

Either change the details already supplied in the document or delete all in the screen and then have this copied with your details inserted on a note pad

rpcuser=*****RANDOM
rpcpassword=*****RANDOM
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
masternode=1
masternodeprivkey=*****whichever priv node it is

addnode=31.6.30.115
addnode=217.240.107.120
addnode=109.172.55.170
addnode=68.104.0.118
addnode=24.104.248.48
addnode=67.3.92.178
addnode=86.122.138.192
addnode=76.105.204.52
addnode=74.132.6.75
addnode=173.30.131.78
addnode=68.7.186.217
addnode=188.230.158.70
addnode=162.213.154.31
addnode=173.245.148.70
addnode=151.80.206.104
addnode=24.254.142.135
addnode=74.132.6.75
addnode=67.225.110.88
addnode=104.200.151.6

now Press ctrl - x

press Y to confirm save

Now go back to your desktop pc.

Open the masternode.conf file in the data directory of your laptop's wallet and edit it. In one
line for each masternode follow this format: ALIAS VPSIP:51472 MASTERNODEPRIVKEY TRANSACTIONHASH INDEX​. The
ALIAS can be anything you want it to be, but for simplicities sake it may be best to use the name you used
for the wallet addresses, MN1 and MN2 in this example. The IP is the IP where the masternode wallet can be
found. the MASTERNODEPRIVKEY is the output from the command "masternode genkey" you entered earlier.
The TRANSACTIONHASH and INDEX are the output you received when you executed "masternode outputs" earlier.

eg for MN 1 shown here would be

mn1 VPSIP:51472 88dkgjsooxf2nZbpNHXukjda03JySp9QG3fD1s586jdkjsgSFLhqYbd 6b80fc205c2551d2e0d1af9c2861afa705d6433jhdsojgsog94093cd25d88ac 0

you then would continue this on with other priv keys and transaction ids for the different nodes eg.


mn2 VPS IP:51472 88dkgjsooxf2nZbpNHXukjda03JySp9QG3fD1s586jdkjsgSFLhqYbd 6b80fc205c2551d2e0d1af9c2861afa705d6433jhdsojgsog94093cd25d88ac 0


mn3 VPS IP:51472 88dkgjsooxf2nZbpNHXukjda03JySp9QG3fD1s586jdkjsgSFLhqYbd 6b80fc205c2551d2e0d1af9c2861afa705d6433jhdsojgsog94093cd25d88ac 0

Then save this file and restart the desktop wallet.

Go back to your VPS Putty and type the following command:

./darknetd

Should now have a message saying it starting.

Now go back to your desktop, unlock the wallet and go into debug command and type masternode start-many

You should then have messages saying they enabled.

That is it. Well done!

If you want to check if nodes are running. On your desktop wallet in debug command type

masternode list-conf


this will show you if they are enabled. If some are not enabled and say some missing because you have restarted the VPS/restarted the node/crashed make sure the masternode is running and then go back to the debug command and type

Also a really good way to check if its running is to go in the the send folder on coin controls and the addresses should be locked if they are running.

masternode start-missing

DO NOT START MANY else it will reset your time or summit like that and you have to wait ages for another transaction...well it did for me anyway.


That should help some people

[kokokoin]

I want to remind you about this proposal. Even if you don't like it, please vote 'no' to show number of atcive masternode owners. But i think DNET POW should be decreased to keep the coin attractive to new investors.

I am a miner and masternodes owner. I think constant supply during POW phase is bad for cryptocurrency. It leads to constant inflation and therefore fading of interest of investors.

My proposal for supply reduction during POW phase. It will decrease inflation, leaving enough coins for fair distribution. We will have total of 45 360 000 coins at the end of the POW phase instead of 64 800 000 coins (-19 440 000 coins).

Blocks 1 - 86 400 (56 days)
POW reward: 250 DNET
Total supply: 21 600 000

Blocks 86 401 - 172 800 (56 days)
POW reward: 175 DNET
Total supply: 36 720 000

Blocks 172 801 - 259 200 (56 days)
POW reward: 100 DNET
Total supply: 45 360 000

Blocks 259 200 +
POS

To vote in favor = "mnbudget vote eb800b00add41c506738592d8cc7de53c17bbfec4ca572b77c778632c57e2c3c yes"
To vote against = "mnbudget vote eb800b00add41c506738592d8cc7de53c17bbfec4ca572b77c778632c57e2c3c no"
(use 'vote-many' instead of 'vote' to vote using all your MN at once via controller wallet).

Just setup my MN last night - Voted on this now.  Is there a list of proposals?

Type mnbudget show in console.

[Zeraful]

-snip-

Yeah, the basics are simple and nicely written, also nice guide for multiple nodes. My point was for troubleshooting when things don't actually work as intended. As is case for me, apparently not qualified. Could someone explain what does it mean that a node is not qualified exactly? I had it running for 30 hours, it said masternode started succesfully but I checked today and no transactions have occurred and checked out that it is in fact unqualified... so yeah if anyone could shed some light on that..

Thanks for the write-up, appreciated by many i'm sure.

[Darkoth89]

@kokokoin, Excellent, thanks!

[kokokoin]

Why this proposal suddenly disappeared from mnbudget show list?

I am a miner and masternodes owner. I think constant supply during POW phase is bad for cryptocurrency. It leads to constant inflation and therefore fading of interest of investors.

My proposal for supply reduction during POW phase. It will decrease inflation, leaving enough coins for fair distribution. We will have total of 45 360 000 coins at the end of the POW phase instead of 64 800 000 coins (-19 440 000 coins).

Blocks 1 - 86 400 (56 days)
POW reward: 250 DNET
Total supply: 21 600 000

Blocks 86 401 - 172 800 (56 days)
POW reward: 175 DNET
Total supply: 36 720 000

Blocks 172 801 - 259 200 (56 days)
POW reward: 100 DNET
Total supply: 45 360 000

Blocks 259 200 +
POS

To vote in favor = "mnbudget vote eb800b00add41c506738592d8cc7de53c17bbfec4ca572b77c778632c57e2c3c yes"
To vote against = "mnbudget vote eb800b00add41c506738592d8cc7de53c17bbfec4ca572b77c778632c57e2c3c no"
(use 'vote-many' instead of 'vote' to vote using all your MN at once via controller wallet).

[StakeBox]

-snip-

Yeah, the basics are simple and nicely written, also nice guide for multiple nodes. My point was for troubleshooting when things don't actually work as intended. As is case for me, apparently not qualified. Could someone explain what does it mean that a node is not qualified exactly? I had it running for 30 hours, it said masternode started succesfully but I checked today and no transactions have occurred and checked out that it is in fact unqualified... so yeah if anyone could shed some light on that..

Thanks for the write-up, appreciated by many i'm sure.

Not qualified is not a state I have seen, nor can I find any reference to in the source. What is the exact error you are seeing? If you run "masternode list does it show up there? Is this a local Masternode, or remote Masternode? Did you follow the instructions in the OP to set it up? Are you sure that you have a confirmed transaction of exactly 10000 DNET in your wallet, if it is a remote Masternode, the coins are in your local wallet, right? Again, without more information it is really near impossible to help you.

[StakeBox]

Why this proposal suddenly disappeared from mnbudget show list?

I am a miner and masternodes owner. I think constant supply during POW phase is bad for cryptocurrency. It leads to constant inflation and therefore fading of interest of investors.

My proposal for supply reduction during POW phase. It will decrease inflation, leaving enough coins for fair distribution. We will have total of 45 360 000 coins at the end of the POW phase instead of 64 800 000 coins (-19 440 000 coins).

Blocks 1 - 86 400 (56 days)
POW reward: 250 DNET
Total supply: 21 600 000

Blocks 86 401 - 172 800 (56 days)
POW reward: 175 DNET
Total supply: 36 720 000

Blocks 172 801 - 259 200 (56 days)
POW reward: 100 DNET
Total supply: 45 360 000

Blocks 259 200 +
POS

To vote in favor = "mnbudget vote eb800b00add41c506738592d8cc7de53c17bbfec4ca572b77c778632c57e2c3c yes"
To vote against = "mnbudget vote eb800b00add41c506738592d8cc7de53c17bbfec4ca572b77c778632c57e2c3c no"
(use 'vote-many' instead of 'vote' to vote using all your MN at once via controller wallet).

It looks like someone took you up on your request to vote on your proposal. If you run "mnbudget getinfo POSSupplyReduction" you can still see it, but it looks like the number of no votes is why it got removed from the main list.

[StakeBox]

I'm getting error: could not allocate vin when starting remote masternodes.

Sorry you are having issues. Is this a local Masternode, or a remote Masternode? Are you following the instructions in the OP? If it is a remote Masternode which wallet are you using to start it, and what is the command you are using? Are you sure that you have a confirmed transaction of exactly 10000 DNET in your wallet, if it is a remote Masternode, the coins are in your local wallet, right? More information is needed to troubleshoot your problem. There are quite a few places things could go wrong in the setup procedure, and without all of the relevant info it won't be possible to remotely solve.

Followed, cut & pasted this https://bitcointalk.org/index.php?topic=1262920.msg14138827#msg14138827 for remote .conf and OP for local .confs.

Using local wallet to start 6 remote MNs. Transactions sent 6 x 10000. Command: masternode start-many.

Get the error message for 1st 5 MNs, 6th says successful. 

Thanks

I am going to look a bit deeper into this, but the first thing that comes to mind is, did you use coin control when sending the 6 transactions? It is possible that you sent 10k to the first address, and then when you sent 10k to the second address, since the initial 10k transaction wouldn't have been locked, it was combined with another input and used to send the second one, and so on down the line, until you sent the last one, which would be the only remaining full 10k input in your wallet. That would explain why only the last one started successfully. If you haven't already go to settings->options->wallet in your local wallet and enable coin control. Then, go to the sending page of the wallet and click on inputs. The screen that opens should show 6 10k inputs, if not, then that is what happened. I will try to figure out some other way you could be getting that error in the meantime, but I bet that is what happened.

Coin control wasn't enabled.  Inputs shows 6x locked 10k transactions.  Thanks a lot.

When you run "masternode outputs" it shows you 6 TXids, right? And do those match the ones in your darknet.conf? At this point it be just be best to start over, removing the 5 Masternodes that won't start from your darknet.conf, and set them up one at a time to eliminate some simple error that I am just not imagining.

[Zeraful]

-snip-

Yeah, the basics are simple and nicely written, also nice guide for multiple nodes. My point was for troubleshooting when things don't actually work as intended. As is case for me, apparently not qualified. Could someone explain what does it mean that a node is not qualified exactly? I had it running for 30 hours, it said masternode started succesfully but I checked today and no transactions have occurred and checked out that it is in fact unqualified... so yeah if anyone could shed some light on that..

Thanks for the write-up, appreciated by many i'm sure.

Not qualified is not a state I have seen, nor can I find any reference to in the source. What is the exact error you are seeing? If you run "masternode list does it show up there? Is this a local Masternode, or remote Masternode? Did you follow the instructions in the OP to set it up? Are you sure that you have a confirmed transaction of exactly 10000 DNET in your wallet, if it is a remote Masternode, the coins are in your local wallet, right? Again, without more information it is really near impossible to help you.

I'm referencing that, before I shut down I checked the qualify amounts, It indeed didn't drop by one as I shut mine down, all I can think of is if it just hasn't been online long enough, thought 30 hours would be though. And it's a local masternode, did follow op. Checked with coin control that it's exactly 10k. And it does say its enabled, no idea what that qualify means.

Total: 287 (DS Compatible: 287 / Enabled: 287 / Qualify: 279)

[borris123]

how is it going with getting dnet added to poloniex?

[Zeraful]

how is it going with getting dnet added to poloniex?

Poloniex hasn't added coins lately besides RADS right? So wouldn't expect anything in a long while.. Did send that coin suggestion submission to them just now tho for what its worth. Does anyone even know poloniex's requirements to get added? I'm curious.

[ipsec]

DNET RIP...... end of story.. Now dump to 1 sato
Maybe i will buy for 2 sato

[DRPD]

is there an official twitter account for dnet?

TY

[StakeBox]

-snip-

Yeah, the basics are simple and nicely written, also nice guide for multiple nodes. My point was for troubleshooting when things don't actually work as intended. As is case for me, apparently not qualified. Could someone explain what does it mean that a node is not qualified exactly? I had it running for 30 hours, it said masternode started succesfully but I checked today and no transactions have occurred and checked out that it is in fact unqualified... so yeah if anyone could shed some light on that..

Thanks for the write-up, appreciated by many i'm sure.

Not qualified is not a state I have seen, nor can I find any reference to in the source. What is the exact error you are seeing? If you run "masternode list does it show up there? Is this a local Masternode, or remote Masternode? Did you follow the instructions in the OP to set it up? Are you sure that you have a confirmed transaction of exactly 10000 DNET in your wallet, if it is a remote Masternode, the coins are in your local wallet, right? Again, without more information it is really near impossible to help you.

I'm referencing that, before I shut down

There is your problem.. In order to get paid a Masternode must be running and online. You will not receive payments for it if it is shut down. It needs to be accessible by the network in order for it to provide the services that Masternodes are getting paid to provide. It is of no use if it is shut down.

[q327K091]

What about masternode payouts?

Not changing, like in the firs post of ANN:

PoW Rewards Breakdown: [0000002-0043200] 20% MNODE / 80% MINER
PoW Rewards Breakdown: [0043201-0259201] 20% MNODE / 70% MINER / 10% PROPOSALS

pressure to purchase coins to erect master nodes is why master nodes should pay out, it would be so much better if people would not sell at low prices but propagate network of master nodes (the more the better)

selling at less then 10 million market cap is not worth your time! unless you buying chewing gum from the profits at less which some of you do sadly  

a beauty to my eyes (one of em), granted I could be unloading shaving off 10K anything above and pushing onto an exchange and sell it aint doing that , my strong believe is dev(s) will be adding on the top of dash and continue


./darknet-cli getbalance
10167.99937202

what also happens with the master nodes is that wallets consume low % of CPU/memory (and none GPU of course) freeing machines to do other "stuff", while the master nodes quietly collect

what I really need to do is to have cron jobs to dispatch anything above 10K to master main wallet and cold store so I dont have to think about it

[Zeraful]

There is your problem.. In order to get paid a Masternode must be running and online. You will not receive payments for it if it is shut down. It needs to be accessible by the network in order for it to provide the services that Masternodes are getting paid to provide. It is of no use if it is shut down.

Guess so, I just read from this thread that you should get first payment after like 24 hours, I had it up for more than 30 hours. Is there any estimate how long it should be up before seeing some payments then? Also I'd still like to know what that qualify thing is? Curious

[Selsonblue]

Yeah, it took about 24 hours for my first masternode payment to come in. Over the last week I have had about 3 or 4 come in at around 80dnet each... HELLZ YEAH ILL TAKE DEM SATOSHIS BRA

[Darkoth89]

Set my masternode up last night, had two payments so far, roughly 8 hours apart of 83.3333333 DNET each. Pretty happy with that so far!

[danonthehill]

I'm getting error: could not allocate vin when starting remote masternodes.

Sorry you are having issues. Is this a local Masternode, or a remote Masternode? Are you following the instructions in the OP? If it is a remote Masternode which wallet are you using to start it, and what is the command you are using? Are you sure that you have a confirmed transaction of exactly 10000 DNET in your wallet, if it is a remote Masternode, the coins are in your local wallet, right? More information is needed to troubleshoot your problem. There are quite a few places things could go wrong in the setup procedure, and without all of the relevant info it won't be possible to remotely solve.

Followed, cut & pasted this https://bitcointalk.org/index.php?topic=1262920.msg14138827#msg14138827 for remote .conf and OP for local .confs.

Using local wallet to start 6 remote MNs. Transactions sent 6 x 10000. Command: masternode start-many.

Get the error message for 1st 5 MNs, 6th says successful. 

Thanks

I am going to look a bit deeper into this, but the first thing that comes to mind is, did you use coin control when sending the 6 transactions? It is possible that you sent 10k to the first address, and then when you sent 10k to the second address, since the initial 10k transaction wouldn't have been locked, it was combined with another input and used to send the second one, and so on down the line, until you sent the last one, which would be the only remaining full 10k input in your wallet. That would explain why only the last one started successfully. If you haven't already go to settings->options->wallet in your local wallet and enable coin control. Then, go to the sending page of the wallet and click on inputs. The screen that opens should show 6 10k inputs, if not, then that is what happened. I will try to figure out some other way you could be getting that error in the meantime, but I bet that is what happened.

Coin control wasn't enabled.  Inputs shows 6x locked 10k transactions.  Thanks a lot.

When you run "masternode outputs" it shows you 6 TXids, right? And do those match the ones in your darknet.conf? At this point it be just be best to start over, removing the 5 Masternodes that won't start from your darknet.conf, and set them up one at a time to eliminate some simple error that I am just not imagining.

Yeah they all matched.  I've set them individually and they are all running now.  Only thing I can think of is that I messed up the order of starting the server, restarting the wallet, starting masternodes.  Anyway, THANKS GUYS!

[jakiman]

Considering Darknet is all about being "Community Driven via MN voting".....
Anything that could increase community/investor involvement is key....

So I think a new Darknet website with ability to view current Proposals & Votes in "real time" should be right up there in priority. (more than untraceable tx)
This will really allow the community & investors to see what's going on without needing to see it via CLI.
Also would be cool to have it auto-tweet new proposals & end-results via Twitter. (like an automated alert/notification)

Including what I've said above, I really would like to see an easier in-wallet GUI for voting & submitting new proposals instead of requiring the use of CLI.