Anybody is willing to answer? Only 100's denoms left in a wallet. What if I darksend few drk?What if I have spent all 0.1 1.0 10 denoms and only 100 left and I darksend 1 drk? Do I lose 99 drk change? Because change goes to miners.
I don't want to be that generous. Am I missing something?
You'll get your change, not miners.Anybody is willing to answer? Only 100's denoms left in a wallet. What if I darksend few drk?
Bump.... Anybody have an answer?Will this version work with p2pool by changing the version number in the code?
Thanks!
But I don't want to reveal any info. Simply I will have to mix them again.You'll get your change, not miners.
Yes, change needs to be remixed.But I don't want to reveal any info. Simply I will have to mix them again.
So after shopping madness I will have to check coincontrol to see what size of denoms left
Yikes, that's really weird.Local wallet got stuck after 7/8 rounds with two conflicting '!' txes, restarted with -zapwallettxes and now being hit with a string of charges and no DS progress:
![]()
Might just be bad luck. I left if for another hour and got a PTY 0.00 but it stayed stuck on 'Found unconfirmed... waiting...'Yikes, that's really weird.
On Win 7, I had 1 conflict tx stuck at 39%(for 16 hrs).Had saved a wallet from the start of version 11.0.6 before mixing and did the standard copy and paste thing, re ran same version and everything tickety boo now.Local wallet got stuck after 7/8 rounds with two conflicting '!' txes, restarted with -zapwallettxes and now being hit with a string of charges and no DS progress:
![]()
I had the same problem on everything up to 0.11.0.4 - I skipped 0.11.0.5 - Have had this happen only one time since 0.11.0.6 and by pure coincidence, I was looking right at it when it happened. No output of any kind. I roll the command to execute like this in the same terminal so that any STDOUT or STDERR will hit the same screen session: ~/.darkcoin/darkcoind & tail -f ~/.darkcoin/debug.log - but nuthin'. No SEGFAULT, no stacktrace, just poof. The good news is that it is improved in it's occurrence by orders of magnitude in 0.11.0.6 - now over 40 nodes and it only happened once in 24 hours.I've had 3 MNs just stop (daemon on server just quit, nothing odd in debug.log, no obvious signs in logs of RAM/CPU overuse) since updating to v11. They have all had to be restarted from the local wallet.
Well, Darkcoil doesn't have DS (and masternode support iirc). Not sure where the optimizations lie.Latest version is unresponsive and crashes often with "dust" transactions.
Windows 7 64 bit
Why can't we get the same performance as in Darkcoil wallet??
Problem is with very small payments from P2Pool. I'm talking about 15 "dust" payments per day.Well, Darkcoil doesn't have DS (and masternode support iirc). Not sure where the optimizations lie.
Yeah, I hear you. You're left at the moment with either using with daemon to group and send dust and micro payments or Darkcoil.Problem is with very small payments from P2Pool. I'm talking about 15 "dust" payments per day.
DS and MN should not cause it. These are incoming transactions.
flare , I just built v0.11.0.6 with OpenSSL 1.0.1j , all 3 operating systems built without problems and Win and Linux clients also run without problems.Just got a link to https://bitcointalk.org/index.php?topic=919373.0
According to deps-linux.yml we ARE building with Openssl-1.0.1k.
eduffield , shouldn't we temporarily use Openssl-1.0.1j ?
Backup wallet and run once with -upgradewallet -zapwallettxesI found that this version of the wallet was completely unresponsive & locked up every time I went to do something with it on win7 64bit - unusable, so I went back to using darkcoil again.
I too use p2pool, so maybe this has something to do with it, but I also saw a post on bitcointalk from someone who couldn't use the daemon with p2pool at all - it wouldn't connect:
https://bitcointalk.org/index.php?topic=421615.msg10178011#msg10178011
Peace![]()
working on it.Latest version is unresponsive and crashes often with "dust" transactions.
Windows 7 64 bit
Why can't we get the same performance as in Darkcoil wallet??
what's wrong with 1.0.1k?Just got a link to https://bitcointalk.org/index.php?topic=919373.0
According to deps-linux.yml we ARE building with Openssl-1.0.1k.
eduffield , shouldn't we temporarily use Openssl-1.0.1j ?
I was thinking about this one : http://sourceforge.net/p/bitcoin/mailman/message/33221963/what's wrong with 1.0.1k?
yeah it does, darkcoin is so freakin up-to-date since v11I was thinking about this one : http://sourceforge.net/p/bitcoin/mailman/message/33221963/
...but if v0.11.0.6 already includes Bitcoins workaround-commit (didn't check) than you can just ignore my post...
Edit: I checked...forget my post![]()
I had the 64bit Linux client freeze on me once, which has never happened before. It's a fairly bare-bones Xubuntu installation with nothing else I've installed running.I found that this version of the wallet was completely unresponsive & locked up every time I went to do something with it on win7 64bit - unusable, so I went back to using darkcoil again.
I too use p2pool, so maybe this has something to do with it, but I also saw a post on bitcointalk from someone who couldn't use the daemon with p2pool at all - it wouldn't connect:
https://bitcointalk.org/index.php?topic=421615.msg10178011#msg10178011
Peace![]()
No, those are not "funky" messages.. lol... Those messages are letting you know what the mixing is doing.I had the 64bit Linux client freeze on me once, which has never happened before. It's a fairly bare-bones Xubuntu installation with nothing else I've installed running.
Mixing seems to have hit a wall. I'm getting all sorts of funky messages above the Darksend mixing buttons. It would be great if it were possible to select the text and copy it, because it changes quite often. Some of the messages I have seen are:
Submitted to masternode, waiting in queue .
Darksend is idle.
Darksend request incomplete: transaction not valid. Will retry
Masternode: transaction not valid
Masternode: not compatible with existing transactions
Submitted to masternode, entries 2/3
Submitted to masternode, Waiting for more entries (2/3)..
... collateral not valid
Masternode: collateral not valid
I imagine that a lot of these have to do with the fact that only about 35% of Masternodes have updated to the latest version.
What does collateral not valid mean? Is there some way I can make my collateral valid?No, those are not "funky" messages.. lol... Those messages are letting you know what the mixing is doing.