Innergy I had this once in normal mode as well when I was sending multiple payments, switched label to switch again on Send and was good view later.Guys, I'm using the wallet in lite mode (litemode=1 in dash.conf file) and look what I get when I tried to send some funds:
Then I tried the same in normal mode with checked "Darksend" and got the same strange fee (maybe it's normal, I don't know, I haven't any anonymized funds):
In normal mode, with unchecked "Darksend" all looks good:
Is it possible that the lite mode doesn't switch off correctly the Darksend and InstantX options?
Im not at a non MN Dash wallet at the moment but I will try this in a couple of hours. One thing that is something I hope we can add as a feature is perma lock for MN wallets so funds aren't spent from those. Its really annoying when you lock it....close and re-open that if you use DASH for buying something it will pull the DASH from MN wallets because they are now unlocked again...arrrgghhTried to mix 100 DASH (2 rounds). It is running since 9 hours and only got 53 DASH completed. Running on version 11.2.22. This version is described to bring DS performance improvements, but mainnet results do not look promising.
Is current darksend code/implementation the problem or do we have too low general DASH mixing volume? 75% of MNs are on version 11.2.22, so that should not be the problem.
What is your darksend mixing speed experience with 11.2.22?
Best,
Rango
Im not at a non MN Dash wallet at the moment but I will try this in a couple of hours. One thing that is something I hope we can add as a feature is perma lock for MN wallets so funds aren't spent from those. Its really annoying when you lock it....close and re-open that if you use DASH for buying something it will pull the DASH from MN wallets because they are now unlocked again...arrrgghh
Yes, I also encounter this, but not every time.I'm not sure if anybody else is having this problem, but everytime I start dash-qt.exe on my Windows PC, it gets almost to the point of loading and then crashes with no error messages. When I run it again, it comes up without any problems.
I didn't have a problem with this version yetI'm not sure if anybody else is having this problem, but everytime I start dash-qt.exe on my Windows PC, it gets almost to the point of loading and then crashes with no error messages. When I run it again, it comes up without any problems.
I'm not sure if anybody else is having this problem, but everytime I start dash-qt.exe on my Windows PC, it gets almost to the point of loading and then crashes with no error messages. When I run it again, it comes up without any problems.
Yes, I also encounter this, but not every time.
I think something is wrong with masternode payment frequency since enforcement was last activated. Looking at the masternode count for the last days, one would expect about 4 days between payments, but if you look at https://dashninja.pl/masternodes.html and sort by last payment, there are hundreds of active MN's not getting paid for over 5 days. I can confirm this with my own MN's. Most of them running perfectly for over 8 weeks but receive payments about every 5,5 days now.
Does someone have an explanation for this? Could the MN count be wrong?
The payments take longer
but are bigger as expected
So all good here
Not agree.. MN count / Blocks per day - 2312/576 = expected payment per MN - every 4 days
I have three MNs that haven't got paid more than 5 days..
And one question: does "start-many" throws you out of the payment queue?
There is no way to even out masternode payment values since the block rewards are based on difficulty. It's based on frequency since last block paid.I haven't look at the code but my understanding is that it's not the payment frequency that's evenly distributed (ie. round robin) but the payment value.
Can a dev confirm or correct this?
There is no way to even out masternode payment values since the block rewards are based on difficulty. It's based on frequency since last block paid.