Dedicated tMN updated to v0.12.1.0-0199027 and synced nmarley sentinel. Don't have time to help more than that right now. Hopefully Wednesday. Good luck all! 
12.1 Testnet Testing Phase Two Ignition
- Thread starter eduffield
- Start date
- Status
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.
Test Build 00676 (v0.12.1.0-g77852d9) RPMs for Fedora, CentOS, RHEL
https://drive.google.com/open?id=18qwFkDKfyZhvecuR5kxiIKmPsjPZjFhRY0EsfHYbD7I
Source package repository and how to build them is linked within. Stable Dash Core (v0.12.0) available from there as well. Happy testing.
UPDATE (on Thu Oct 27): Build 679 or v0.12.1.0-g1a81c34
https://drive.google.com/open?id=18qwFkDKfyZhvecuR5kxiIKmPsjPZjFhRY0EsfHYbD7I
Source package repository and how to build them is linked within. Stable Dash Core (v0.12.0) available from there as well. Happy testing.
UPDATE (on Thu Oct 27): Build 679 or v0.12.1.0-g1a81c34
Last edited:
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?
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.
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?)
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?)
- Apr 8, 2014
- 1,953
- 1,315
- 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.
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)
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?
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:
[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
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:
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
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
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
OK, so now I have my MNs up and running, next I'll try mixing
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 OK, so now I have my MNs up and running, next I'll try mixing
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.
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
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
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.
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.
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.
To put it simply - "DS MultiSession" is 1+ year old (omgSo 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
, 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 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
If I include the line 'createwalletbackups=0' in dash.conf, it causes mixing to be 'Disabled'... is this by design?
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)
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:
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.
- Status