Hmm...Now my wallet has been getting hit with blank type transactions and "Unconfirmed 9.77499906 DRK" Why do we keep getting these blank transactions? And it seems some of them might be stuck on the block chain again. Edit: All blank transactions got confirmed.
some more wallets finished with the input amounts exactly 8 rounds (not exceeding them) and reaching 100 % : nr 1 : Darksend Balance : 554 Amount set : 990 nr 2 : Darksend Balance : 454 Amount set : 990 nr 3 : Darksend Balance : 744 Amount set : 990 I found no further collateral fees and also no blank transactions (transactions without ''type'')
I am really excited about this code and where it is at. I sometimes get frustrated when things on testnet don't go as planned but then I realize I need to step back and realize this is what testnet is for. Figuring out the things we need to and tweaking all the things that needs tweaking. I am excited at how robust the ds+ code base has become after all the people looking it over. Thanks to everyone for all their hardwork testing and hardening the code! May the dark be with you!
Nice - darksend is working again and is fast in v101717. No longer getting any blank transactions or strange error messages in v101717. Just a few nuisance items perhaps: When I am anonymizing 2000 tdrk 4 rounds, I still have a lot of denoms going through 5 or 6 rounds. My completion bar reads 100% completion too early because of this. In the 32bit windows-qt client starting with early versions of 1017xx and continuing in v101717, anytime a transaction is being created (darksend mixing or just sending funds) the CPU gets pegged and the client becomes unresponsive for maybe 15-20 seconds. This happened sporadically in my v1016xx clients but now it happens every time, even during darksend mixing. I have a decent PC (i5, 8gb) so not a huge problem but folks with crappy machines may have more of an issue with this.
Wallet run for the complete night without crash, but there's still this "DoAutomaticDenominating -- Found unconfirmed denominated outputs, will wait till they confirm to continue." bug. In other words, it's not possible to denominate with this wallet for me.
I'd just start a fresh. Send your coins to me and ill send them back once you have got a new wallet myy263emYeyaFTZYSKWDS4sRKPWUezDzfb
Its a bug from previous test updates, mainnet users shouldn't have this problem. Only testneter's Edit: Had four denominations in an hour, will post a pic of 8 Rounds.
v17 working much better for me than recent previous builds. Only issue I've noticed is the progress bar getting to 100% way too soon, but the process carries on and pretty close to your specified amount end up anon'd. Had two 0.1 charges in the course of anon'ing 1700DRK.
My 2000/4 denom finished, but exceeded the requested anon funds. Also it seems (and I'm just guessing) that once it finished, pty got stuck. Sending the funds to the faucet and starting fresh, this was a previous version wallet. deleting the entire testnet3 folder but keeping debug.log just in case requested. A few 5 rounds, but the rest very nice and tidy all 4's, no less.
On another note, left my tMN shell open, and got this message, never seen this happen before. Checked MN status Which is not true, this is a hot wallet, and got the message straight after
You get the 'masternode started remotely' when it starts itself, not just when you start it yourself from a remote wallet. Other thing I have no idea, I grepped for it but didn't find any such string in the debug.log of mine.
Thats the thing, the daemon did not crash. When I updated, debug said "no problems found" so I "masternode start" locally. .
Oops now I'm getting a bunch of blank transactions and collateral charges. Actually it seems darksend mixing should be completed, I have already reached the target rounds and amount, but it keeps on going with these blank TXs and collateral charges.
My wallet completed denom. I have coins at 8 and 9 rounds. Also, the denom is 100% but i keep getting ---payment to yourself--- 0.10.
My wallet finished up fine, so I sent 1000 back to the faucet, stuck the remaining 700 in a new address, and so far (3 hrs) it hasn't denominated the new 700 lump at all, I just get a periodic 'submitted to mn / waiting in queue' which never gets accepted. Tried restarting the wallet, same behaviour. May just be lack of participants, but it shouldn't need anyone else to denominate? edit: finally denominated after 4 hrs!
I have two wallets. One tMN and one denoms. The moment I turned third on for denoms I get few blank tx and several colateral. Maybe coincidence. Can two denominating wallets cause this sometimes? I know people here have 5-6 denominating wallets and they get hit by collateral. Will send debug to Evan edit: I get hit by these from 2h now. No denoms at all. First wallet. Second one denominating like hell
Finished 2000/4 ...damn, that WAS fast! But I got more 5 rounds than 4. 1x collateral fee. says 100% --- 1952.2/2000 DRKs average 4.67742 or 4 rounds
I'm curious why DS is now going over in rounds vs before it wasn't. If it's capped at 8 rounds, we definitely shouldn't be seeing 9's. Likewise, if you specify 4 rounds and end up with 5 or 6s, it's not following your inputs. EDIT: I do see two more commits today on the instantx branch for stopping and max rounds, although the max rounds set to 2 seems odd, unless this is strictly to test whether people are going over in a shorter period of time before reverting.
************** Please update to v0.10.17.18 *********************************** - Later rounds now REQUIRE only denominated funds to be in the pool (moli's transaction) - Darksend will properly shut off when it gets complete now (in some cases it was splitting forever) Instructions 1.) restart with -zapwallettxes 2.) mix some inputs 8 rounds 3.) post anonymous transactions and lets try to trace them -- Source: https://github.com/darkcoin/darkcoin/tree/instantx Windows 32bit: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/windows/darkcoind.exe https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/windows/darkcoin-qt.exe Mac OS X: https://github.com/darkcoinproject/...ster/instantx/mac/darkcoin-0.10.17.18-osx.dmg Linux 32bit: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/linux/32/darkcoin-qt https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/linux/32/darkcoind Linux 64bit: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/linux/64/darkcoin-qt https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/linux/64/darkcoind
There's two "modes" of the darksend pool now, 1.) Rounds 0 to 1 - where it allows change and new denominations to be created 2.) Rounds 2 to 8 - where ONLY denominations should go in and come out.
Did you find why some 9s were appearing? EDIT: And the overages (setting rounds 5 but getting 6s on some denominations instead of stopping)
I also have a question about tx sizes and tx fees being prompted. How does DS know where to pull the tx fee on the prompt and does it do any rounding to again prevent the dead change issue from breaking up denominations for those microfees?
I'm trying to understand how random collateral fees, especially such low fees, deter bad actors from spamming the system? Also, when spending your funds, can we still mix darksend funds with unmixed funds? If so, won't that expose the other people you mixed with previously as well as yourself?
Possible bug. Brand new wallet. Before receiving any tDRK, I tried to click the Stop Darkesend Mixing to disable it until the funds were cleared and got this.
