- Jul 22, 2014
- Dash Address
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!
Should be fixed now https://github.com/dashpay/dash/pull/1092My 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
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 188.8.131.52:19999 2016-10-24 14:19:11 CDarksendPool::DoAutomaticDenominating -- connected, addr=184.108.40.206: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...
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?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:
Latest builds (v0.12.1.0-b9bd116) of v0.12.1.x branch
- Update dashd
- Update sentinel
- Restart masternode
- Make sure to enable crontab (described below)
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/
We’re currently using nmarley’s repository for Sentinel, we will merge this to dashpay/sentinel soon:
*/2 * * * * cd /home/YOURUSERNAME/.dashcore/sentinel && venv/bin/python scripts/crontab.py >/dev/null 2>&1
Full Installation Instructions:
Github Bug Tracker Links
Find a bug, issue or think we should improve something specific? Please use the issue tracker from Github here:
It’s well worth creating a github account if you don’t have one. 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.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.
Your frustrations with the software are based on your own mis-understanding of how it works -- don't blame the developers for that.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/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)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?
So do I just leave that line the way it is? I don't understand it :/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.
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.What does "WATCHDOG_EXPIRED" in my masternodes tab / status column in the wallet mean?
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.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.
To put it simply - "DS MultiSession" is 1+ year old (omg , 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 defaultSo 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
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.edit : does this mean what i think it means ? (version v0.12.1.0-b3f14b3 btw)