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

12.1 Testnet Testing Phase Two Ignition

Status
Not open for further replies.
Balych said:
My mixing stuck at 22% with PrivateSend request incomplete: Collateral not valid.
but continue to use keys (already 3k used) and not create any TXs for 16+ hours
Code: 
2016-10-24 14:19:11 CDarksendPool::DoAutomaticDenominating -- invalid collateral, recreating...
2016-10-24 14:19:11 keypool added key 15603, size=1001
2016-10-24 14:19:11 init message: Loading wallet... (1558.74 %)
2016-10-24 14:19:11 keypool reserve 14603
2016-10-24 14:19:11 keypool keep 14603
2016-10-24 14:19:11 CMasternodeMan::FindRandomNotInVec -- 5 enabled masternodes, 3 masternodes to choose from
2016-10-24 14:19:11 CDarksendPool::DoAutomaticDenominating -- attempt 0 connection to Masternode 45.55.31.68:19999
2016-10-24 14:19:11 CDarksendPool::DoAutomaticDenominating -- connected, addr=45.55.31.68:19999
2016-10-24 14:19:11 CDarksendPool::DoAutomaticDenominating -- connected, sending DSACCEPT, nSessionDenom: 1 (100.001)
2016-10-24 14:19:12 OverviewPage::privateSendStatus -- Last PrivateSend message: Mixing in progress...
2016-10-24 14:19:12 CDarksendPool::SetState -- nState: 3, nStateNew: 1
2016-10-24 14:19:12 CDarksendPool::SetState -- nState: 1, nStateNew: 7
2016-10-24 14:19:13 OverviewPage::privateSendStatus -- Last PrivateSend message: PrivateSend request incomplete: Collateral not valid. Will retry...
Click to expand...

Should be fixed now https://github.com/dashpay/dash/pull/1092
 
eduffield said:
Happy Monday!

We are looking to move onto the next stage of testnet, but we need some active participation from the masternodes operators currently running active testnet daemons in order to test the code we are working on. Our test network is currently about 5% upgraded, we need at least 65% to force the upgrade. To do the update we will fork testnet and don’t want to leave clients broken on the wrong fork.

To smoothly update the network, we ask anyone running an active masternode to follow the steps below. If you have a masternode, please update, this would greatly help our efforts!

How to upgrade:
  • Update dashd
  • Update sentinel
  • Restart masternode
  • Make sure to enable crontab (described below)
Latest builds (v0.12.1.0-b9bd116) of v0.12.1.x branch
Linux --> https://dashpay.atlassian.net/build...ccessful/artifact/JOB1/gitian-linux-dash-dist
Windows --> https://dashpay.atlassian.net/build...uccessful/artifact/JOB1/gitian-win-dash-dist/
MacOS X --> https://dashpay.atlassian.net/build...uccessful/artifact/JOB1/gitian-osx-dash-dist/
Raspberry --> https://dashpay.atlassian.net/build...build-latestSuccessful/gitian-RPi2-dash-dist/

Sentinel Code
We’re currently using nmarley’s repository for Sentinel, we will merge this to dashpay/sentinel soon:
https://github.com/nmarley/sentinel.git

Crontab Entry
*/2 * * * * cd /home/YOURUSERNAME/.dashcore/sentinel && venv/bin/python scripts/crontab.py >/dev/null 2>&1

Full Installation Instructions:
https://gist.github.com/moocowmoo/66049a781f8eaa1021306072f19363d4

Github Bug Tracker Links
Find a bug, issue or think we should improve something specific? Please use the issue tracker from Github here:

https://github.com/dashpay/dash/issues
https://github.com/nmarley/sentinel/issues

It’s well worth creating a github account if you don’t have one. Thanks!
Click to expand...
Quick question - i downloaded the windows version of 12.1 (as above), but the masternode tab is missing. Also there is no t before the dash address. It looks like a mainnet client. Is that possible?

If i have downloaded the test net client, can someone please send me some tDash to Xm8ovg466chDg54AYXFHLkAgDnR5AWqh9B.

Thanks.
 
halso said:
Quick question - i downloaded the windows version of 12.1 (as above), but the masternode tab is missing. Also there is no t before the dash address. It looks like a mainnet client. Is that possible?

If i have downloaded the test net client, can someone please send me some tDash to Xm8ovg466chDg54AYXFHLkAgDnR5AWqh9B.

Thanks.
Click to expand...
There is no testnet specific binaries, to start wallet in testnet mode you need to specify "-testnet" cmd-line option. Testnet addresses start with "y", the one you specified is mainnet address.
 
I've tried but i can't make it work. To be honest, this is a little disappointing. This release was promised in July. It's nearly November, and the link to testnet doesn't even work. Can someone please release a windows testnet link that i can download and test?
 
halso said:
I've tried but i can't make it work. To be honest, this is a little disappointing. This release was promised in July. It's nearly November, and the link to testnet doesn't even work. Can someone please release a windows testnet link that i can download and test?
Click to expand...

Your frustrations with the software are based on your own mis-understanding of how it works -- don't blame the developers for that.

As others have said, there is no "testnet download" -- there's only one download, and it works for both testnet and mainnet. You have to specify which one to use, and it defaults to mainnet. Both @UdjinM6 and @splawik21 have instructed you how to do that.
 
halso said:
I've tried but i can't make it work. To be honest, this is a little disappointing. This release was promised in July. It's nearly November, and the link to testnet doesn't even work. Can someone please release a windows testnet link that i can download and test?
Click to expand...
Latest successful windows build is there https://dashpay.atlassian.net/build...uccessful/artifact/JOB1/gitian-win-dash-dist/
(binaries update automatically there once new build is completed)
You need to either configure dash.conf with testnet=1 or supply -tesnet in cmd-line to connect to testnet. If you don't specify this wallet starts in mainnet mode by default with your mainnet wallet i.e. with your real funds which should be more or less ok but it is not recommended until "official" release/announcement.
 
Two questions:

1. what is this? :
#masternodeaddr=' >> dash.conf
and should I remove ' >> dash.conf and replace it with my MN address?

2. Is this instead where I put the earnings deposit address? (do we have a way to deposit earnings into another address now?)
 
No TS, with budgeting the forwarding of the MN earnings is not possible anymore in this stage and probably later but I have to say it was cool to send the MN earnings on the other address.
 
halso said:
I've tried but i can't make it work. To be honest, this is a little disappointing. This release was promised in July. It's nearly November, and the link to testnet doesn't even work. Can someone please release a windows testnet link that i can download and test?
Click to expand...
The dash.conf that you must put testnet=1 inside is the one residing in the AppData/Roaming/dashcore folder (not the subfolder called testnet3 or whatever)
 
splawik21 said:
No TS, with budgeting the forwarding of the MN earnings is not possible anymore in this stage and probably later but I have to say it was cool to send the MN earnings on the other address.
Click to expand...
So do I just leave that line the way it is? I don't understand it :/

Also, my windows wallet is using the old /AppData/Roaming/Dash folder. I'm wondering what I did wrong?? I did use the link at the first page of this thread, but I believe updates are always pushed to the same download link, no?
 
I didn't use capital letters, I can do that. However, why would the wallet hook up to the old Dash folder?

Ok, I renamed my dash directory, and now it's asking me if I want to use a custom directory or default. I'm going to see what default does.... OK, default opens a new DashCore directory.

I wonder why my windows wallet wanted to use the old dash directory?? Is this the behavior you expected? Perhaps only the MNs need to use the dashcore directory?
 
Last edited:
my dash.conf file looks like this:

echo 'daemon=1
server=1
listen=1
testnet=1
rpcuser=Ingie
rpcpassword=anythingyoulikeUIHOYRpuih23reh2p

masternode=1
masternodeprivkey=932PH26R9HDvCTEaZn5A6WmFmZBcrxDEg7a7oGoQYQpT651WsE3
masternodeaddr=216.45.55.232:19999


And, after putting my ip address and the port and undoing the # (mark off ?) in dash.conf, I get this when I try to start my remote (non-funded) MN:
TS@Dash1:~/.dashcore$ Error: masternodeaddr option is deprecated. Please use masternode.conf to manage your remote masterndodes.

Please tell me what I'm doing wrong, thanks :)
 
Last edited:
Just kill me - I found Evan's comment at the bottom of the page:

With recent updates to 12.1, masternodeaddr=ADDR should be updated to externalip=ADDR.

If anyone can update the instructions and fix it, it will save people a lot of grief when they're forced to update to 12.1 :) Thanks :D

OK, so now I have my MNs up and running, next I'll try mixing :)
 
What does "WATCHDOG_EXPIRED" in my masternodes tab / status column in the wallet mean?
 
Status
Not open for further replies.
Back
Top