Author

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

hero member
Activity: 736
Merit: 500
OK, here is how to setup multiple DarkNet masternodes. I am going to use RPis as the masternodes in this example,
with a wallet on your laptop acting as the controller, I am also going to write this for 2 masternodes,
but the directions could be expanded to as many as you want. The concept could also be changed around as
you please using VPSs or other computers as your masternodes, as well as something else for the controller.
If using a VPS, or darknetd as opposed to the Qt wallet, all of the commands that are to be entered in the
console should be entered on the command line preceded by "./darknet-cli",for example "./darknet-cli masternode
genkey". This should go without saying, but don't enter the quotation marks when entering commands.

Step 1: From the very begining, on your laptop in the console enter "masternode genkey" twice, 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.

Step 2: Send 10k DNET to each of the addresses generated in step 1, making sure to send exactly 10k, in
one transaction to each. Now, execute "masternode outputs" in the console of your laptop wallets.

Step 3: 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 IP: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.

Step 4: Open the darknet.conf file in the data directory of the controller wallet, again, on the laptop in
this example, Modify the contents to match this:
rpcuser=long random username
rpcpassword=longer random password
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
maxconnections=256

Step 5: Close the wallet and restart it.

Step 6: Open the darknet.conf file in the data directory of one of your masternode wallets, on a RPi in this
example. modify the contents of the file to look like this:
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
Replacing the username and password with your own, and replacing the Xs with the masternode private key that
corresponds to the masternode alias you would like for this masternode.

Step 7: Close and restart that wallet.

Step 8: repeat steps 5 and 6 for the other masternode wallet, the other RPi in this example.

Final step: Now, both of your masternodes are setup, you just need to start them, you will do this with the
controlling wallet on your laptop. Open the console of the controlling wallet and enter "masternode start-many"
you should get an output something like this:
{
    "overall" : "Successfully started 2 masternodes, failed to start 0, total 2",
    "detail" : {
        "status" : {
            "alias" : "mn1",
            "result" : "successful"
        },
        "status" : {
            "alias" : "mn2",
            "result" : "successful"
        }
}
Thank you for very Nice tutorial, however i still have a issue.
Can you post an exact example of this line: ALIAS IP:51472 MASTERNODEPRIVKEY TRANSACTIONHASH INDEX​ ?

Have tried this, and wallet gets Runtime error:
MN1 xxx.xx.xx.xx:9998 MASTERNODEPRIVKEY TRANSACTIONHASH 1(index)

MN1 xxx.xx.xx.xx:9998 MASTERNODEPRIVKEY
"TRANSACTIONHASH" : "1"

Where is my error/s?
Thank you,

IW
full member
Activity: 238
Merit: 100
How exactly is this a POS coin, if there is no stake notify and no POS difficulty in the 'getinfo' ?
its all in OP, check it

Quote
PoS Phase 1: PoS [0259201-0518400] Approx. 180 DAYS

Yes, I've seen that. So where is the POS part in the daemon commands ?

- Your coins will not gain weight right now as PoS has not been implemented yet.

That's what OP said on page 7
legendary
Activity: 1453
Merit: 1030
How exactly is this a POS coin, if there is no stake notify and no POS difficulty in the 'getinfo' ?
its all in OP, check it

Quote
PoS Phase 1: PoS [0259201-0518400] Approx. 180 DAYS

Yes, I've seen that. So where is the POS part in the daemon commands ?
full member
Activity: 238
Merit: 100
Hey guys, remember you can mine for FREE!!! 0% fees!!!




Is everything fine? Over 60 mins with no payments, but everything was working great till that.

UPDATE: Nevermind, a bigger payment was on its way, all seems good.
legendary
Activity: 1232
Merit: 1001
How exactly is this a POS coin, if there is no stake notify and no POS difficulty in the 'getinfo' ?
its all in OP, check it

Quote
PoS Phase 1: PoS [0259201-0518400] Approx. 180 DAYS
legendary
Activity: 1232
Merit: 1001
OK, here is how to setup multiple DarkNet masternodes. I am going to use RPis as the masternodes in this example,
with a wallet on your laptop acting as the controller, I am also going to write this for 2 masternodes,
but the directions could be expanded to as many as you want. The concept could also be changed around as
you please using VPSs or other computers as your masternodes, as well as something else for the controller.
If using a VPS, or darknetd as opposed to the Qt wallet, all of the commands that are to be entered in the
console should be entered on the command line preceded by "./darknet-cli",for example "./darknet-cli masternode
genkey". This should go without saying, but don't enter the quotation marks when entering commands.

Step 1: From the very begining, on your laptop in the console enter "masternode genkey" twice, 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.

Step 2: Send 10k DNET to each of the addresses generated in step 1, making sure to send exactly 10k, in
one transaction to each. Now, execute "masternode outputs" in the console of your laptop wallets.

Step 3: 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 IP: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. To get
the TRANSACTIONHASH and INDEX are the output you received when you executed "masternode outputs" earlier.

Step 4: Open the darknet.conf file in the data directory of the controller wallet, again, on the laptop in
this example, Modify the contents to match this:
rpcuser=long random username
rpcpassword=longer random password
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
maxconnections=256

Step 5: Close the wallet and restart it.

Step 6: Open the darknet.conf file in the data directory of one of your masternode wallets, on a RPi in this
example. modify the contents of the file to look like this:
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
Replacing the username and password with your own, and replacing the Xs with the masternode private key that
corresponds to the masternode alias you would like for this masternode.

Step 7: Close and restart that wallet.

Step 8: repeat steps 5 and 6 for the other masternode wallet, the other RPi in this example.

Final step: Now, both of your masternodes are setup, you just need to start them, you will do this with the
controlling wallet on your laptop. Open the console of the controlling wallet and enter "masternode start-many"
you should get an output something like this:
{
    "overall" : "Successfully started 2 masternodes, failed to start 0, total 2",
    "detail" : {
        "status" : {
            "alias" : "mn1",
            "result" : "successful"
        },
        "status" : {
            "alias" : "mn2",
            "result" : "successful"
        }
}
very very good tutorial, thanks
legendary
Activity: 1453
Merit: 1030
How exactly is this a POS coin, if there is no stake notify and no POS difficulty in the 'getinfo' ?
legendary
Activity: 1232
Merit: 1001
dnet.gcpool.eu

Have Fun

Port 3352 for Vardiff
Port 3452 for Fixed Diff ( 0.1 ) 20Mhs+

Port 3552 for Fixed Diff ( 0.5 ) 200Mhs+
ty for pool, looks great  Cool
full member
Activity: 226
Merit: 100
OK, here is how to setup multiple DarkNet masternodes. I am going to use RPis as the masternodes in this example,
with a wallet on your laptop acting as the controller, I am also going to write this for 2 masternodes,
but the directions could be expanded to as many as you want. The concept could also be changed around as
you please using VPSs or other computers as your masternodes, as well as something else for the controller.
If using a VPS, or darknetd as opposed to the Qt wallet, all of the commands that are to be entered in the
console should be entered on the command line preceded by "./darknet-cli",for example "./darknet-cli masternode
genkey". This should go without saying, but don't enter the quotation marks when entering commands.

Step 1: From the very begining, on your laptop in the console enter "masternode genkey" twice, 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.

Step 2: Send 10k DNET to each of the addresses generated in step 1, making sure to send exactly 10k, in
one transaction to each. Now, execute "masternode outputs" in the console of your laptop wallets.

Step 3: 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 IP: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.

Step 4: Open the darknet.conf file in the data directory of the controller wallet, again, on the laptop in
this example, Modify the contents to match this:
rpcuser=long random username
rpcpassword=longer random password
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
maxconnections=256

Step 5: Close the wallet and restart it.

Step 6: Open the darknet.conf file in the data directory of one of your masternode wallets, on a RPi in this
example. modify the contents of the file to look like this:
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
Replacing the username and password with your own, and replacing the Xs with the masternode private key that
corresponds to the masternode alias you would like for this masternode.

Step 7: Close and restart that wallet.

Step 8: repeat steps 5 and 6 for the other masternode wallet, the other RPi in this example.

Final step: Now, both of your masternodes are setup, you just need to start them, you will do this with the
controlling wallet on your laptop. Open the console of the controlling wallet and enter "masternode start-many"
you should get an output something like this:
{
    "overall" : "Successfully started 2 masternodes, failed to start 0, total 2",
    "detail" : {
        "status" : {
            "alias" : "mn1",
            "result" : "successful"
        },
        "status" : {
            "alias" : "mn2",
            "result" : "successful"
        }
}
full member
Activity: 226
Merit: 100
OK, so you want to start a DarkNet masternode, here's how to do it. Note, these instuctions are intended for
those running the Qt DarkNet wallet. If you are using darknetd the same steps apply, but, whenever a command is
to be entered in the console you would enter the command on the command line preceded by "./darnet-cli",
for example, to generate the masternode private key you would enter "./darknet-cli masternode genkey".
This should go without saying, but don't enter the quotation marks when entering commands.

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, 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.
legendary
Activity: 1028
Merit: 1000
dnet.gcpool.eu

Have Fun

Port 3352 for Vardiff
Port 3452 for Fixed Diff ( 0.1 ) 20Mhs+

Port 3552 for Fixed Diff ( 0.5 ) 200Mhs+
legendary
Activity: 1078
Merit: 1011
it will always be 10k, and there is an active exchange with sell orders as I write this.. Smiley

btcpool.exchange
hero member
Activity: 756
Merit: 500
This coin seems ok, could be used for a lot more things, mining is decent but ATM it is hard to get the 10K for a Obfuscation Masternode.

Will 10K always be the limit or will it go down ?

I agree it is hard to set up an ON "Obfuscation Node" while there is no exchange to buy some.
legendary
Activity: 1078
Merit: 1011
This coin seems ok, could be used for a lot more things, mining is decent but ATM it is hard to get the 10K for a Obfuscation Masternode.

The increased difficulty of obtaining the required DNET to build a Masternode is what will help keep this coin moving in the right direction.
legendary
Activity: 1078
Merit: 1011
whats the max coin amount?

In the PoW phase, the max possible coins will be 64800000

We are still working the numbers to see what the following PoS phases will be. The numbers that have been proposed are just suggestions at this point.
legendary
Activity: 1218
Merit: 1001
This coin seems ok, could be used for a lot more things, mining is decent but ATM it is hard to get the 10K for a Obfuscation Masternode.
hero member
Activity: 827
Merit: 1000
Twitter: @bitcoin_dad
whats the max coin amount?
legendary
Activity: 1078
Merit: 1011
Here are the daemon files, I have also included a script to just install the required deps etc. make sure you

chmod +x Install-Darknet-Deps

then

./Install-Darknet-Deps

https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.0.0/Darknet-Daemons-v1.0.0.0.zip

legendary
Activity: 1517
Merit: 1042
@notsofast
I will make available the daemon files for your server shortly, as long as you have run the install script to install the deps, the binaries will work.

Though for various reasons providing statically linked binaries is a bad idea, we will provide these shortly.

Please be aware that running Masternodes on low cost VPS's may work now, but as the network grows, the resources that the Masternodes will use will increase and you will start having issues.



Awesome-- much appreciated, thank you.

I'd like to get the masternode running, prove the concept to myself, and add resources to the VPS when I need to. It seems like it's really easy to simply upgrade the allocation of memory to the VPS when it's needed, without changing the installation.
legendary
Activity: 1517
Merit: 1042
@notsofast
There is now a Script available to install the Darknet wallet on you RPi2.

This has been tested on the Latest Jesse Raspbian Build and the Wheezy Raspbian Build available from the Raspberry Website Now. To avoid any issues, please use a clean fresh Raspbian Image.

Just download the script through the RPi itself then;

chmod +x Install-Darknet-RPi2

then to start the installation

./Install-Darknet-RPi2

The script will download, install all the necessary deps and git source as well as compile the binary and move it to your home directory.

When completed,

./darknet-qt

Nice!

I got an insufficient memory error installing Darknet onto a linux VPS with 768Mb memory... what could have caused this problem? It was a completely fresh instance of the VPS.

Building software on Linux requires memory.  With the base OS using somewhere around 256MB that leaves you with only 512MB to play with.  To do the build, I would recommend no less than 2GB of Ram on the VPS.  To get around this, you could just download the pre-compiled binary that they have available.

You could also just create a swap file.  You can build coin daemons from source on vps's with 768MB ram and a 2GB swap file.



Hm, good call. Since I only need darknetd and darknet-cli I can just build it anywhere, and upload only those two files to the VPS, no?

I would have just used a pre-compiled linux binary, but s3v3n purposely didn't build one.
Jump to: