• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

v0.10.17.x Testing

Status
Not open for further replies.
eduffield

I found a lot of colleteral fees (0.1 fees) with 1 specific wallet, i think i also know with which wallet it was pairing with so i will sent you debug.logs of both
wallets. On both wallets i saw a lot of messages about ''transaction not valid''.

0Z3zNGq.jpg
 
TanteStefana said:
On my windows machine, I have denominated funds, and I tried to send 13.54 drk to the Ubuntu address using 2 X 10 coin denominated coins. But I get the error " Unable to locate enough Darksend denominated funds for this transaction.

Back when I denominated these funds, a while ago... can't remember, I had it set for 8 rounds. It stopped around 6 rounds, and I never tried for more as there was a release. Now, I've re-set the rounds to 3. It may not like the change, or may not use higher denominated funds when you've set it lower? I don't know.
Click to expand...
I tried it as well. I have denominated funds 8 rounds, some of them have 9 btw. When I tick darksend I can send every amount, but if I choose 2x10 in coin-control and try to send 10<amount<20 then It doesn't work. It says "unable to locate enough darksend denominated funds for this TX".

edit: I get it now. Interim Solution. It suppose to choose 10+1+1+0.1+...whatever to have the smallest amount of change. Choosing 2x10 I was able to send 19.91 and 0.09 change went to miners/MN

edit 2: Evan's quote "using . 10DRK+1DRK+0.1DRK, when paying for something users will just over pay to the nearest denomination ($0.1 average)"
 
Last edited by a moderator:
its weird but a lot of my newer transactions only get confirmed if i use the -zapwallettxes, it just wont confirm out of itself.

Example :

Status: 0/unconfirmed
Transaction ID: 2c3528f37ae31dc4cab29df3e173407bfb82558f047f00c7122b07d7a6b9ca5c

update : seems to be going better now, block are getting confirmed faster.

Also when getting colleteral fees / 0.1 fees (who always do get confirmed without me having to use -zapwallettxes) it always show as follows :

mjQNoxy.jpg


It seems to withdraw 0.1 and puts 0.4125 in unconfirmed status at the same time. The next block then confirms the 0.1
 
Last edited by a moderator:
I denomed 2000/2 and got 2x 0.1DRK colateral (and yes, got denoms going up to 4, 6, 7, 8 rounds) , but average was 2.8 rounds total.
I also got one of these

Status: 533 confirmations
Date: 11/29/14 03:47
Debit: 0.00 DRK
Credit: 0.00 DRK
Transaction fee: -0.008 DRK
Net amount: -0.008 DRK
Transaction ID: 03ffab60519cd61540496b9f3385dfdcd77f27361f8365323397bea7c8227845
Click to expand...


I've up'ed to 3 rounds this morning, and got zero collateral so far

gyf9mKK.png



EDIT: Finished, zero fees. Moving onto 4 rounds.
 
Last edited by a moderator:
Hi ya'all
I'm still confused. Are we testing the version of "change" that destroys the change? Either way, how do I see where the change goes please? :)
 
Last edited by a moderator:
Finished 4 rounds.

2014-11-30 18:44:13 DoAutomaticDenominating : No funds detected in need of denominating (2)
Click to expand...

Took 3 hours and zero fees. Will crank up to 8 rounds now.
 
Last edited by a moderator:
TanteStefana said:
Hi ya'all
I'm still confused. Are we testing the version of "change" that destroys the change? Either way, how do I see where the change goes please? :)
Click to expand...

quoting Evan with latest update :

- Disabled InstantX

17.x includes fixes to the dead change issue, masternode backwards compatibility, a simplier send coins interface and other improvements. It seems like everything is working really well except for InstantX (which is hit and miss), so I'd really like to make sure this release is solid as it stands and push it out to the network.
After we're sure these improvements work, we'll push out the changes and then jump right back into testing InstantX. For InstantX to work properly I need implement proof-of-service and have the masternode network passively scan itself and remove nodes that aren't online (which is causing most of our issues currently).
So let me know if there's anything else that needs to get fixed before release!
Click to expand...

I'm just testing the mixing which is finally getting a bit more fluid lately (got stuck last night with not-confirming transactions). Only the darksend rounds still
have a bug (they dont keep the set rounds)
 
i had 6 wallets set for 970 / 4 rounds and they all stopped (constant idle status) around 83-86%
Once i'm back from work i will try to use coin control, bundle all n/a amounts and see if i cant
get a bit higher with the %.
 
qwizzie said:
i had 6 wallets set for 970 / 4 rounds and they all stopped (constant idle status) around 83-86%
Once i'm back from work i will try to use coin control, bundle all n/a amounts and see if i cant
get a bit higher with the %.
Click to expand...

I had mine stall for a few hours, then picked up again nicely. Just letting it do it thing...

2000/4 to 8 rounds, its now 75% done. Got 1 collateral so far.
 
Alrighty then... QT says this;

014-12-01 13:23:18 DoAutomaticDenominating : No funds detected in need of denominating (2)
2014-12-01 13:23:27 ResendWalletTransactions()
2014-12-01 13:23:43 CDarkSendPool::UpdateState() == 3 | 3
2014-12-01 13:24:08 dstx: Got Masternode transaction b53dd31431a17aa7a3594c12bb059ab6f8f2850545cd76956043777d48496caa
2014-12-01 13:24:08 AcceptToMemoryPool: 95.85.48.49:19999 /Satoshi:0.10.17.4/ : accepted b53dd31431a17aa7a3594c12bb059ab6f8f2850545cd76956043777d48496caa (poolsz 14)
2014-12-01 13:24:20 DoAutomaticDenominating : No funds detected in need of denominating (2)
2014-12-01 13:25:21 DoAutomaticDenominating : No funds detected in need of denominating (2)
Click to expand...

But in reality;

uYG3F5O.png


bhm8hoo.png


and lots of 3, 4, 5 6 & 7's ...

So I'll stop for now until next update, and move onto OpenBaazar. Picking up some python in hopes to be able to read the code and help dev DRK integration/fork
 
crowning said:
At least yours does something....mine say "DoAutomaticDenominating : No funds detected in need of denominating (2)" but never start...
Click to expand...

Happens to me too. Thats the thing... For some reason it does not find funds to denominate, hence it wont start. Try sending out a few anonymised coins away, it may/will kickstart the process I believe.
 
My testnet MN is crashing regularly, I think because it's running out of RAM and I didn't bother to set up any swap space. Peaks about 540MB according to the stats (on a 512MB instance.) Are other people seeing similar RAM usage?

My v16 mainnet MNs are steady about 250MB.

Stats since I restarted it about an hour ago:
mn3.png
 
Last edited by a moderator:
Windows wallet v101704 - Got almost 2000 tdrk anonymized:

upload_2014-12-1_12-51-5.png


Some of the denoms got 9 rounds instead of 8. And it seems now we have a lot of "change" amounts as results of the small anonymized denoms?

upload_2014-12-1_12-53-2.png


Also got some collateral fees:

upload_2014-12-1_12-54-47.png
 
Thoughts on getting rid of being able to select the rounds? In an ideal situation, the fees for usage are hit randomly, no longer per round. I full anon phase should be 8 full rounds with those that want further anonymity having the option of going another round of 8. People should no longer be allowed to mix coins less than 8 rounds. Thoughts on replacing rounds with periods (each period being 8 rounds)? Else, just remove the option completely with 100% meaning all the coins went through 8 rounds.
 
Status
Not open for further replies.
Back
Top