• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Running a test network

mikeybd

New member
I would like to explore and experiment with dash by creating a test network of my own. It is a bit too much of an investment for me to run a real masternode. I would like to be able to do so on a practice network of my own.

I haven't been able to find any instructions yet on how this might be accomplished. Can anyone point me in the right direction?
 
@chaeplin
is there a place to download debian binaries? or do I have to build from source to use 12.2.x?
 
thank you, I am up and running with 0.12.2.x on testnet. I've gotten 2000 dash from the faucet. Working on setting up a masternode now... Tao's guide is geared toward using an already setup VPS in combination with a local install? I am attempting to do this all locally so it is a bit of a struggle following those instructions. Should I set up a second server? Do I need two installs in order to set up the masternode? I am using virtual machines to play around so I can set up a second one if necessary. I am using ubuntu server 16 for an OS, but I can switch to any OS that is recommended.
 
I'm still struggling to put all the pieces together, but have made some progress...

I'm thinking I can do all this with one instance of dash-qt, someone please let me know if this is incorrect!

I start it with dash-qt -testnet=1

I have port 19999 forwarded from my router to my dash vm running ubuntu 16

I followed Tao's masternode guide as best I could, generated the key, send 1000 dash to the address

I set up dash.conf and masternode.conf

I set up sentinel

dash-qt shows my masternode in the masternodes tab, but the status is "MISSING" and the protocol is "-1"

I hit start alias, and it says masternode started successfully

status changes to "OUTPOINT SPENT"
protocol changes to "70207"
and a payee address gets filled in

after a minute or so the masternode appears to stop and switches back to status is "MISSING" and the protocol is "-1"

I can start the alias again with the same result

sentinel output:
venv/bin/python bin/sentinel.py
[Errno 111] Connection refused
Cannot connect to dashd. Please ensure dashd is running and the JSONRPC port is open to Sentinel.

I am wondering if this is because it is attempting to connect to port 9999 instead of 19999? How do I tell sentinel that I am on the testnet?

I can confirm port 19999 is open with nmap...
 
Last edited:
I also do not see the 1000 dash I sent to generated masternode address in my transactions...

I do see a "payment to yourself" but the amount is -0.00007480 tDash, and it remains unconfirmed....
 
@mikeybd
Do you want to run a masternode with Dash-QT ?

Sentinel needs rpc connection to dashd.

Setup your node to accept rpc connection from local.

You need at least following at dash.conf
rpcuser=XXXXXXXXXXXXX
rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXX
rpcallowip=127.0.0.1
server=1
listen=1
daemon=1
maxconnections=24
masternode=1
masternodeprivkey=XXXXXXXXXXXXXXXXXXXXXXX
externalip=XXX.XXX.XXX.XXX

https://dashpay.atlassian.net/wiki/spaces/DOC/pages/1146943/Masternode
 
yes, I already have that in my dash.conf

I could run dashd instead of dash-qt if that will simplify things, I just thought it would be a little easier with the GUI

dash-qt created a .dashcore folder in my home directory, that is where I created my dash.conf, masternode.conf is in the testnet3 subdirectory

I'm guessing something went wrong with the 1000 tDash deposit? Because when I start the alias in the masternodes tab the status changes to "OUTPOINT SPENT".

How does sentinel know what port to connect to? Do I have to make it aware of the rpuuser and rpcpassword that I chose in dash.conf?

@mikeybd
Do you want to run a masternode with Dash-QT ?

Sentinel needs rpc connection to dashd.

Setup your node to accept rpc connection from local.

You need at least following at dash.conf


https://dashpay.atlassian.net/wiki/spaces/DOC/pages/1146943/Masternode
 
yes, I already have that in my dash.conf

I could run dashd instead of dash-qt if that will simplify things, I just thought it would be a little easier with the GUI

dash-qt created a .dashcore folder in my home directory, that is where I created my dash.conf, masternode.conf is in the testnet3 subdirectory

I'm guessing something went wrong with the 1000 tDash deposit? Because when I start the alias in the masternodes tab the status changes to "OUTPOINT SPENT".

How does sentinel know what port to connect to? Do I have to make it aware of the rpuuser and rpcpassword that I chose in dash.conf?


change sentinel/sentinel.conf
https://github.com/dashpay/sentinel/blob/master/sentinel.conf#L6-L7

network=mainnet to network=testnet

Use https://test.explorer.dash.org/chain/tDash to find txid and index_number
 
change sentinel/sentinel.conf
https://github.com/dashpay/sentinel/blob/master/sentinel.conf#L6-L7

network=mainnet to network=testnet

Use https://test.explorer.dash.org/chain/tDash to find txid and index_number


my address is: ySgrDzxvn8kGYpo8cN1CQNwEW9xqkLwhaV
found this:
https://test.explorer.dash.org/tx/5...85afe0925a837a33a2f648dc428c1f46839d1a5f28#o1

I'm not sure why there is 1900 and change in the transaction, but it does say the say the address balance is 1000...

I have the following at the end of my masternode.conf configuration line:
595148e4d149d2f991787585afe0925a837a33a2f648dc428c1f46839d1a5f28 1

I changed sentinel.conf and now my output is:
michael@ubuntuserver16:~/.dashcore/sentinel$ venv/bin/python bin/sentinel.py
Invalid Masternode Status, cannot continue.

does sentinel need to restarted after the configuration file change? I get different output now, so I'm guessing it saw the change...
 
595148e4d149d2f991787585afe0925a837a33a2f648dc428c1f46839d1a5f28 1 is ok.
when masternode status is ok, sentinel will work(with a cron).
 
595148e4d149d2f991787585afe0925a837a33a2f648dc428c1f46839d1a5f28 1 is ok.
when masternode status is ok, sentinel will work(with a cron).

so where do I go from here? sentinel says masternode status is invalid. could it be the transaction doesn't have enough confirmations? it has been over 24 hours...

when I go into the masternodes tab of dash-qt I see my masternode

and from a previous post in this thread:

the status is "MISSING" and the protocol is "-1"

I hit start alias, and it says "masternode started successfully!"

status changes to "OUTPOINT SPENT"
protocol changes to "70207"
payee address to "ySgrDzxvn8kGYpo8cN1CQNwEW9xqkLwhaV"

after a minute or so the masternode appears to stop and switches back to status is "MISSING", the protocol back to "-1", and the payee back to blank

I can start the alias again with the same results
 
start your mn. current status.

"595148e4d149d2f991787585afe0925a837a33a2f648dc428c1f46839d1a5f28-1": "NEW_START_REQUIRED 70207 ySgrDzxvn8kGYpo8cN1CQNwEW9xqkLwhaV 1503587364

Is your node synced fully ?

check, AssetID should be 999.
dash-cli mnsync status

{

"AssetID": 999,

"AssetName": "MASTERNODE_SYNC_FINISHED",

"AssetStartTime": 1503537375,

"Attempt": 0,

"IsBlockchainSynced": true,

"IsMasternodeListSynced": true,

"IsWinnersListSynced": true,

"IsSynced": true,

"IsFailed": false

}

dash-cli getinfo

{

"version": 120200,

"protocolversion": 70207,

"walletversion": 61000,

"balance": 4999.89382520,

"privatesend_balance": 4999.67999630,

"blocks": 256135,

"timeoffset": 0,

"connections": 24,

"proxy": "",

"difficulty": 22.12893031157587,

"testnet": true,

"keypoololdest": 1503505879,

"keypoolsize": 1999,

"paytxfee": 0.00000000,

"relayfee": 0.00010000,

"errors": ""

}
 
start your mn. current status.



Is your node synced fully ?

check, AssetID should be 999.

when I try to start the alias in dash-qt masternodes tab it seems to be working briefly, then it stops again, I described the output in earlier posts...

status says "OUTPOINT SPENT" while it is running, then it goes back to "MISSING"

what does "OUTPOINT SPENT" mean?

michael@ubuntuserver16:~/.dashcore/sentinel$ dash-cli -testnet mnsync status
{
"AssetID": 999,
"AssetName": "MASTERNODE_SYNC_FINISHED",
"AssetStartTime": 1503586615,
"Attempt": 0,
"IsBlockchainSynced": true,
"IsMasternodeListSynced": true,
"IsWinnersListSynced": true,
"IsSynced": true,
"IsFailed": false
}
michael@ubuntuserver16:~/.dashcore/sentinel$ dash-cli getinfo
error: couldn't connect to server
michael@ubuntuserver16:~/.dashcore/sentinel$ dash-cli -testnet getinfo
{
"version": 120200,
"protocolversion": 70207,
"walletversion": 61000,
"balance": 2999.99585080,
"privatesend_balance": 74.70074700,
"blocks": 255191,
"timeoffset": 0,
"connections": 8,
"proxy": "",
"difficulty": 21.69138096217026,
"testnet": true,
"keypoololdest": 1503358053,
"keypoolsize": 1999,
"unlocked_until": 0,
"paytxfee": 0.00000000,
"relayfee": 0.00010000,
"errors": ""
}
 
looks like wallet stuck at 255192.
'OUTPOINT SPENT' means your tx was made at block height 255440, and your dashd is at 255192, so it could't find any tx.

Use -reindex to get sorted.

stop dashd.
run dashd -reindex
 
looks like wallet stuck at 255192.
'OUTPOINT SPENT' means your tx was made at block height 255440, and your dashd is at 255192, so it could't find any tx.

Use -reindex to get sorted.

stop dashd.
run dashd -reindex

ok, that helped

now when I start the alias, the status changed to ENABLED for a couple seconds

then it changed to WATCHDOG_EXPIRED

active is "-7m: -26s"

not sure what that means...

sentinel still returns:
michael@ubuntuserver16:~/.dashcore/sentinel$ venv/bin/python bin/sentinel.py
Invalid Masternode Status, cannot continue.
 
use a cmd at `michael@ubuntuserver16`

dash-cli masternode status

to check masternode status which sentinel checks.
 
Back
Top