12.1 Testnet Testing Phase Two Ignition

Status
Not open for further replies.

UdjinM6

Official Dash Dev
Core Developer
Dash Core Group
May 20, 2014
3,639
3,537
1,183
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...
Should be fixed now https://github.com/dashpay/dash/pull/1092
 
  • Like
Reactions: Balych

halso

Active Member
Apr 27, 2016
439
237
113
Sydney, Australia
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!
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.
 

UdjinM6

Official Dash Dev
Core Developer
Dash Core Group
May 20, 2014
3,639
3,537
1,183
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.
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.
 

splawik21

Yeah, it's me....
Dash Core Group
Foundation Member
Dash Support Group
Apr 8, 2014
1,957
1,316
1,283
@halso put testnet=1 in your dash.conf :) the binaries are the same.
 

halso

Active Member
Apr 27, 2016
439
237
113
Sydney, Australia
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?
 

nmarley

Administrator
Core Developer
Dash Core Group
Jun 28, 2014
369
427
133
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?
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.
 
  • Like
Reactions: JGCMiner and David

UdjinM6

Official Dash Dev
Core Developer
Dash Core Group
May 20, 2014
3,639
3,537
1,183
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?
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.
 
  • Like
Reactions: halso and studioz

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,876
1,867
1,283
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?)
 

splawik21

Yeah, it's me....
Dash Core Group
Foundation Member
Dash Support Group
Apr 8, 2014
1,957
1,316
1,283
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.
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,876
1,867
1,283
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?
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)
 
  • Like
Reactions: halso

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,876
1,867
1,283
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.
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?
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,876
1,867
1,283
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:

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,876
1,867
1,283
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:
[email protected]:~/.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:

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,876
1,867
1,283
OK, I think I got it fixed. Apparently, we need to remove the step where you put in masternodeaddr=whatever because that fucks it up. I started my MN, apparently successfully on both ends, by removing that line from my remote (non-funded) MN.

Unless I'm wrong here, that should be removed from the instructions :)

https://gist.github.com/moocowmoo/66049a781f8eaa1021306072f19363d4

It would save a lot on frustration and questions :)
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,876
1,867
1,283
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 :)
 

italx

Well-known Member
Foundation Member
Jul 31, 2014
65
52
158
California
What does "WATCHDOG_EXPIRED" in my masternodes tab / status column in the wallet mean?
 

fuzzyduck

Active Member
Feb 19, 2015
137
113
93
I fixed it by iinstalling ssentinel as wwel. Or iis it a ccoincidence

SSorr pphoneffreakingout. AAlwaysthis forum.
 

stan.distortion

Well-known Member
Oct 30, 2014
928
547
163
What does "WATCHDOG_EXPIRED" in my masternodes tab / status column in the wallet mean?
On a newly started masternode? That message comes up on the first run and should change as soon as Sentinel runs (to pre-enabled iirc), not really a bug but apparently it'll be changed to something less confusing before release.
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,876
1,867
1,283
So it looks like multi-session is an option that is turned off by default. Why is that? Is it less secure?

Unless it is MUCH less secure, this is a feature everyone would benefit from, so I don't understand why 1- we have the option of turning it on / off and 2- why it's not on by default.

Frankly, Dash is getting a bit too complex with it's choices. In open source projects, this becomes the norm - but at the price of losing your users to the dumbed down easier to use options out there. Take my android phone vs my daughter's iphone. Hers functions cleanly and is super easy to understand. Mine has had quite a learning curve, which I'm still on.

What am I saying? Well, we kind of have covered this by making it so you have to turn these extra tabs and options on in the wallet to access them, but it seems that all the useful features are defaulted to off. I think we should make the most useful / fast /easy options the default, and if you want to change those to "more safe" vs "faster", you then have to poke around in the wallet. Because most people in the future will not be so concerned about extreme privacy (the sort you are worried about because you're doing something highly illegal) but rather want general, quick and cheap privacy and ease of use to buy groceries, etc... So make the default settings for those people (whom we'd rather associate with anyway) and leave the obfuscation to those who are motivated by fear to figure out.

Dash has long taken the approach to be for general use. Privacy was always for personal privacy and personal protection against unreasonable search and seizure, etc... So I think keeping the default wallet in line with ease of use for best/fastest/safest against theft and loss features trumps those for ultra anon uses.

Take Crowning's backup feature. The wallet makes a backup each time it's shut down (or is it backed up when started??) anyway, this is priceless for a regular "normal" person. But because I am paranoid and don't want to leave my wallet, though well encrypted, on my computer, I pack up my MN when I have to expose them on the internet, and delete the wallet.dat files in the backup folder each time. But I like the feature, because it still keeps me safe in case I screw something up until I delete it :)
 
  • Like
Reactions: halso

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,876
1,867
1,283
One more thing. I tried to consolidate a bunch of inputs, but they were too big (I suppose over the 1 or 2 mb allowed per block). This got me thinking. Lets say you're buying something big and expensive, like a house. But you can't send the funds in one chunk, which makes the transaction messy and multiplies the risks to both parties (you can't just hand over the deed/money instantly (ok, escrow would normally be used BUT)

I was wondering if there could be a feature where the user could prepare for a large purchase by having all their inputs pre-consolidated into one input. So when it's time to pay, they know they can do it in one simple step with minimum inputs.

You could do this manually, but it'd be so much easier if the wallet could do this for you. Especially if there were an algorithm that could determine which inputs to combine to maintain the most privacy for people you've previously mixed with.

Just a thought.
 

italx

Well-known Member
Foundation Member
Jul 31, 2014
65
52
158
California
On a newly started masternode? That message comes up on the first run and should change as soon as Sentinel runs (to pre-enabled iirc), not really a bug but apparently it'll be changed to something less confusing before release.
Thanks for the info. Checking back today one has changed to say "ENABLED" and the other two now say "POSE_BAN". No idea what that means. I had reinstalled and setup them all yesterday with newly downloaded versions of dash and sentinel. I'll have to do more investigation when I have some time.
 

UdjinM6

Official Dash Dev
Core Developer
Dash Core Group
May 20, 2014
3,639
3,537
1,183
So it looks like multi-session is an option that is turned off by default. Why is that? Is it less secure?

Unless it is MUCH less secure, this is a feature everyone would benefit from, so I don't understand why 1- we have the option of turning it on / off and 2- why it's not on by default.

Frankly, Dash is getting a bit too complex with it's choices. In open source projects, this becomes the norm - but at the price of losing your users to the dumbed down easier to use options out there. Take my android phone vs my daughter's iphone. Hers functions cleanly and is super easy to understand. Mine has had quite a learning curve, which I'm still on.

What am I saying? Well, we kind of have covered this by making it so you have to turn these extra tabs and options on in the wallet to access them, but it seems that all the useful features are defaulted to off. I think we should make the most useful / fast /easy options the default, and if you want to change those to "more safe" vs "faster", you then have to poke around in the wallet. Because most people in the future will not be so concerned about extreme privacy (the sort you are worried about because you're doing something highly illegal) but rather want general, quick and cheap privacy and ease of use to buy groceries, etc... So make the default settings for those people (whom we'd rather associate with anyway) and leave the obfuscation to those who are motivated by fear to figure out.

Dash has long taken the approach to be for general use. Privacy was always for personal privacy and personal protection against unreasonable search and seizure, etc... So I think keeping the default wallet in line with ease of use for best/fastest/safest against theft and loss features trumps those for ultra anon uses.

Take Crowning's backup feature. The wallet makes a backup each time it's shut down (or is it backed up when started??) anyway, this is priceless for a regular "normal" person. But because I am paranoid and don't want to leave my wallet, though well encrypted, on my computer, I pack up my MN when I have to expose them on the internet, and delete the wallet.dat files in the backup folder each time. But I like the feature, because it still keeps me safe in case I screw something up until I delete it :)
To put it simply - "DS MultiSession" is 1+ year old (omg :eek:, I didn't realize that), here is the PR - https://github.com/dashpay/dash/pull/615 (don't be confused by such a small amount of changes in this specific PR, all actual work to clean the code to be able to finally do this was done before it, that one was "the final switch" ;)). It was an experimental and unproved feature back then and could consume all your keypool in few seconds if anything gone wrong. I know, I had these o_O moments few times myself. Obviously, I wouldn't advise any general user to use it back then. I've been using it for mixing all this year (including my mainnet funds) and since then few edge cases/bugs were fixed, few additional safety checks implemented etc. Finally, this https://github.com/dashpay/dash/pull/882 was implemented, so eventually multi-session feature became both proven and quite safe (hopefully). If massive testing of multi-session mixing on testnet won't bring any surprises like rapid keypool depletion or stuck txes or smth like that AND everyone agree it's safe enough I think we can turn it on by default :)
 
  • Like
Reactions: TanteStefana

bertlebbert

Active Member
Jul 17, 2014
670
289
133
If I include the line 'createwalletbackups=0' in dash.conf, it causes mixing to be 'Disabled'... is this by design?
 

bertlebbert

Active Member
Jul 17, 2014
670
289
133
Yep, that's the screen I get - I had to investigate a bit to determine it's caused by 'createwalletbackups=0' - not sure how those two are related... that's why I figured best check that it's by design. Cool, thanks Udjin :)
 
  • Like
Reactions: qwizzie

qwizzie

Well-known Member
Aug 6, 2014
1,831
991
183
Open pull requests = 0 :)

I will test commits 4894345 once it gets available for download (meaning i will do some mixing / IS / PS) . Call me optimistic but i get the feeling we are entering a new phase on testnet but i do have a question though :
is there a status update about the superblocks on Testnet ? did you guys manage to have a superblock created on Testnet or do more masternodes need to upgrade ?

edit : does this mean what i think it means ? (version v0.12.1.0-b3f14b3 btw)

 
Last edited:

nmarley

Administrator
Core Developer
Dash Core Group
Jun 28, 2014
369
427
133
edit : does this mean what i think it means ? (version v0.12.1.0-b3f14b3 btw)
Not sure if this is what you're asking, but superblocks will still be monthly on mainnet. We needed a quicker way to test them on testnet, so testnet superblocks are hourly.

We still need to get testnet stable for now (e.g. no forks and "gobject list" shouldn't take more than a few seconds) before asking lots of people to upgrade at this point. But with the latest commit it's looking a lot better. There are still some governance optimizations coming down the pike that should help a lot. I don't believe we've had an automated superblock yet, but network stability concerns have taken priority ATM.
 
  • Like
Reactions: qwizzie
Status
Not open for further replies.