How much DRK do you have anonymized?![]()
I got the same error (Unable to locate enough darksend) from using normal transaction on the same platform on v5...
How much DRK do you have anonymized?![]()
I got the same error (Unable to locate enough darksend) from using normal transaction on the same platform on v5...
Ok, dont forget JIRA's 30 todo issues.Anything pre-existing I'll deal with next release, I'm just looking to fix Darksend right now. With that said, I'm going to go ahead and release. Thanks everyone!
Same here, none mixed when stopped mixing and trying to send funds to faucet.At that point, none.
This may be testnet related but three of my wallets stuck at the same block ~63137 had to close them and restart for it to move on.Evan : how do you feel about waiting a day (or night, depending where you live) so we can run the wallets a bit longer and decide tomorrow
if there needs more fixing or not ? From my point of view it looks solid but a bit more testing could not hurt either...
"Create Normal Transaction" will only take non-denom inputs that have nothing to do with Darksend. So if you've even started denominating, that setting won't work. You'd have to use no-pref to spend the denominated rounds that haven't met the rounds minimum.At that point, none.
I'm for removing it. I justed wanted to see if I could duplicate his issue. If I am sending anything, I either use from darksend transaction or no preference so the normal seems out of place, especially if it will go bust the second the DS process is started."Create Normal Transaction" will only take non-denom inputs that have nothing to do with Darksend. So if you've even started denominating, that setting won't work. You'd have to use no-pref to spend the denominated rounds that haven't met the rounds minimum.
So yeah, this is confusing and needs to be removed. Someone suggested just removing it entirely and spending inputs by prioritizing anonymity, then it'll popup and say HOW anonymous the transaction is going to be and ask you if you want to continue. That's prob the best bet.
Being in a hurry is rarely a good thing.Anything pre-existing I'll deal with next release, I'm just looking to fix Darksend right now. With that said, I'm going to go ahead and release. Thanks everyone!
I agree with darkwing. Always good to have an option for anonymous or public transactions. Maybe by having a prompt come up just after you send coins asking which coins you would like to use.."Create Normal Transaction" will only take non-denom inputs that have nothing to do with Darksend. So if you've even started denominating, that setting won't work. You'd have to use no-pref to spend the denominated rounds that haven't met the rounds minimum.
So yeah, this is confusing and needs to be removed. Someone suggested just removing it entirely and spending inputs by prioritizing anonymity, then it'll popup and say HOW anonymous the transaction is going to be and ask you if you want to continue. That's prob the best bet.
It's hard to trust anything daemons report at the moment, my local QT (which I used to start the remote MN) still sees my MN on the list, but the MN itself doesn't see itself at all any more... and different people are all seeing different counts... I'm just going to wait 24hrs and see what happens.Can anyone help? I updated darkcoind for my masternodes both remotely and locally. I started it as I always do, with darkcoind -daemon on the server and ./darkcoind -masternodeaddr=54.ipaddress:9999 -daemon, ./darkcoind walletpassphrase, ./darkcoind masternode start
The local works and says masternode started remotely, plus if I do ./darkcoind masternode list, I see my server's IP address.
But the remote, after waiting over half an hour, says not capable masternode
What's up?
Edit: I used my QT wallet and it worked. Perhaps starting with the remote ip address no longer works? It used to not work for me when I left it out.... go figure, LOL
Same, half my masternodes grepped 1 on the remote masternode list, the others, nothing. Then loading up my primary wallet (not a masternode wallet) and getting the list, the same ones don't show.It's hard to trust anything daemons report at the moment, my local QT (which I used to start the remote MN) still sees my MN on the list, but the MN itself doesn't see itself at all any more... and different people are all seeing different counts... I'm just going to wait 24hrs and see what happens.
Maybe Evan has worked in IP obfuscation already? :tongue:Hum, ok then, we'll see tomorrow
Mine no longer sees their ip address but still report that the masternode was started successfully. Hopefully that's good ;P
I guess masternode list will show the address then...LOL, yes, and I guess this is a taste of what is to come. We may not be able to check our masternodes so easily in the future! Well, one of mine got a payment, so I'm guessing everything is OK.
Cant you wait untill its fixed?we cant enforce while not all updated yet.... today I start pool police....
Your computer can't resolve the hostname to an IP, this has nothing to do with the port....try to use the IP directly.if I do the command telnet host 9999 I get "could not resolve host/9999 no address associated with host name." Why? I have no idea!
telnet <your_IP> 9999You mean like this?
[email protected]:/usr/bin$ telnet host myip
telnet: could not resolve host/myip: Servname not supported for ai_socktype