Bitcoin Forum
November 14, 2024, 10:59:03 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Poll
Question: .
.
.

Pages: « 1 2 3 4 5 6 7 [8] 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 ... 541 »
  Print  
Author Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN  (Read 782372 times)
donnyespo
Hero Member
*****
Offline Offline

Activity: 827
Merit: 1000


Twitter: @bitcoin_dad


View Profile
February 01, 2016, 03:33:19 AM
 #141

whats the max coin amount?

            ▄▄████▄▄
        ▄▄██████████████▄▄
      ███████████████████████▄▄
      ▀▀█████████████████████████
██▄▄       ▀▀█████████████████████
██████▄▄        ▀█████████████████
███████████▄▄       ▀▀████████████
███████████████▄▄        ▀████████
████████████████████▄▄       ▀▀███
 ▀▀██████████████████████▄▄
     ▀▀██████████████████████▄▄
▄▄        ▀██████████████████████▄
████▄▄        ▀▀██████████████████
█████████▄▄        ▀▀█████████████
█████████████▄▄        ▀▀█████████
██████████████████▄▄        ▀▀████
▀██████████████████████▄▄
  ▀▀████████████████████████
      ▀▀█████████████████▀▀
           ▀▀███████▀▀



.SEMUX
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
  Semux uses .100% original codebase.
  Superfast with .30 seconds instant finality.
  Tested .5000 tx per block. on open network
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
Belligerent Fool
Legendary
*
Offline Offline

Activity: 1218
Merit: 1001



View Profile
February 01, 2016, 04:07:00 AM
 #142

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.
4x13 (OP)
Legendary
*
Offline Offline

Activity: 1078
Merit: 1011


View Profile
February 01, 2016, 04:14:35 AM
 #143

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.
4x13 (OP)
Legendary
*
Offline Offline

Activity: 1078
Merit: 1011


View Profile
February 01, 2016, 04:17:06 AM
 #144

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.
SushiNoTomato
Hero Member
*****
Offline Offline

Activity: 756
Merit: 500


View Profile
February 01, 2016, 04:19:48 AM
 #145

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.
4x13 (OP)
Legendary
*
Offline Offline

Activity: 1078
Merit: 1011


View Profile
February 01, 2016, 04:44:58 AM
 #146

it will always be 10k, and there is an active exchange with sell orders as I write this.. Smiley

btcpool.exchange
glen123
Legendary
*
Offline Offline

Activity: 1028
Merit: 1000



View Profile
February 01, 2016, 03:28:30 PM
Last edit: February 01, 2016, 05:36:55 PM by glen123
 #147

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+
StakeBox
Full Member
***
Offline Offline

Activity: 226
Merit: 100


View Profile WWW
February 01, 2016, 05:29:06 PM
 #148

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.

Low power dedicated staking hardware, learn more at StakeBox.com
Raspberry Pi wallets at github.com/StakeBox
StakeBox
Full Member
***
Offline Offline

Activity: 226
Merit: 100


View Profile WWW
February 01, 2016, 05:31:53 PM
Last edit: February 01, 2016, 08:01:32 PM by StakeBox
 #149

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"
        }
}

Low power dedicated staking hardware, learn more at StakeBox.com
Raspberry Pi wallets at github.com/StakeBox
trader19
Legendary
*
Offline Offline

Activity: 1232
Merit: 1001



View Profile WWW
February 01, 2016, 07:42:20 PM
 #150

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

Join the Elastic revolution!  Elastic - The Decentralized Supercomputer
ELASTIC WEBSITE | NEW ANNOUNCEMENT THREAD | ELASTIC SLACK | ELASTIC FORUM
samspaces
Legendary
*
Offline Offline

Activity: 1453
Merit: 1030


View Profile
February 01, 2016, 07:49:17 PM
 #151

How exactly is this a POS coin, if there is no stake notify and no POS difficulty in the 'getinfo' ?
trader19
Legendary
*
Offline Offline

Activity: 1232
Merit: 1001



View Profile WWW
February 01, 2016, 07:53:41 PM
 #152

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

Join the Elastic revolution!  Elastic - The Decentralized Supercomputer
ELASTIC WEBSITE | NEW ANNOUNCEMENT THREAD | ELASTIC SLACK | ELASTIC FORUM
trader19
Legendary
*
Offline Offline

Activity: 1232
Merit: 1001



View Profile WWW
February 01, 2016, 07:55:08 PM
 #153

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

Join the Elastic revolution!  Elastic - The Decentralized Supercomputer
ELASTIC WEBSITE | NEW ANNOUNCEMENT THREAD | ELASTIC SLACK | ELASTIC FORUM
userpacman1
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
February 01, 2016, 08:07:56 PM
Last edit: February 01, 2016, 08:34:37 PM by userpacman1
 #154

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.
samspaces
Legendary
*
Offline Offline

Activity: 1453
Merit: 1030


View Profile
February 01, 2016, 08:43:06 PM
 #155

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 ?
userpacman1
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
February 01, 2016, 09:20:13 PM
 #156

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
incognitoworker
Hero Member
*****
Offline Offline

Activity: 736
Merit: 500


View Profile
February 01, 2016, 09:35:34 PM
 #157

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

Quotient- Closed loop economy enviroment experiment
https://bitcointalk.org/index.php?topic=1195335.0
StakeBox
Full Member
***
Offline Offline

Activity: 226
Merit: 100


View Profile WWW
February 01, 2016, 10:10:50 PM
 #158

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

The port has to be 51472, not 9998. So, MN1 xxx.xx.xx.xx:51472 MASTERNODEPRIVKEY 1

Low power dedicated staking hardware, learn more at StakeBox.com
Raspberry Pi wallets at github.com/StakeBox
4x13 (OP)
Legendary
*
Offline Offline

Activity: 1078
Merit: 1011


View Profile
February 01, 2016, 10:11:52 PM
 #159

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

Wrong port numbers
glen123
Legendary
*
Offline Offline

Activity: 1028
Merit: 1000



View Profile
February 01, 2016, 10:13:48 PM
 #160

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+

@Dev : pls add to OP
Pages: « 1 2 3 4 5 6 7 [8] 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 ... 541 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!