v0.10.13.x RC5 Testing

kryptofoo · Sep 13, 2014

Also, is it possible there are too few masternodes on the testnet? I see 15 running v08. If my coins have already been run through one masternode, I assume they would not be processed another round in the same masternode(?). Maybe our coins have to match not only denomiations but also match on a current masternode that neither of us has mixed with previously. Is that how this works?

Stealth923 · Sep 13, 2014

vertoe said:
Denomination slowed down on test net, come on people, get your wallets up!

Getting mine going as we speak

qwizzie · Sep 13, 2014

i think Darksend+ should be restricted into only merging amounts when the output can be easily paired / is equal to the splitting methode amounts.

or

let it try to pair for a fixed number of times and if then still not paired force it to split into a more easily paired amount.

moli · Sep 13, 2014

Yesterday I tried to anonymize 5000 tdrk, about 1000 tdrk got thru 6 rounds, then I had to stop. Last night, I started the wallet again, tried to pair with Oblox (25 tdrk, 8 rounds for a while, got 0 anon tdrk.) I then changed the configurations to 15000 tdrk to keep anonymized, 8 round. Overnight I've got only 995 tdrk anonymized.

oblox · Sep 13, 2014

moli said:
Yesterday I tried to anonymize 5000 tdrk, about 1000 tdrk got thru 6 rounds, then I had to stop. Last night, I started the wallet again, tried to pair with Oblox (25 tdrk, 8 rounds for a while, got 0 anon tdrk.) I then changed the configurations to 15000 tdrk to keep anonymized, 8 round. Overnight I've got only 995 tdrk anonymized.

I'm still stuck, no pairs or anything. Not sure if this is a bug in which case I should be submitting a jira report or an error due to lack of pairs (now needing 3). I'm going to give it until noon to do something, then I am filing a bug report and attaching the wallet file and logs.

moli · Sep 13, 2014

oblox said:
I'm still stuck, no pairs or anything. Not sure if this is a bug in which case I should be submitting a jira report or an error due to lack of pairs (now needing 3). I'm going to give it until noon to do something, then I am filing a bug report and attaching the wallet file and logs.

I think the handful testers we have right now are testing large amounts. That's why we get stuck in trying to anonymize small amounts. When I paired with you, I kept seeing my wallet say "Submitted to masternode, Waiting for more entries (2/3)" and later it said "Submitted to masternode, Waiting for more entries (1/3)", I thought maybe you dropped out.

qwizzie · Sep 13, 2014

kryptofoo said:
My submits are for 930 tDRK. I find it hard to believe it has to match the total amount. That would be really inefficient!

I opened up a second wallet on a VM. We need more peeps to run darksend!

You can try the following to get it started again :

Stop anonymization

Send 430 tDRK to the test faucet .. make sure you select the following amounts through coin control :

3x 100 (incl last cent) on round 2
1x 100 (incl last cent) on round 3
3x 10 (incl last cent) on round 2 and 3

set methode of transaction on : no preference

make sure you dont pay any fees for this bundle transaction to the faucet (set in yr option transaction fees to 0)

After the transaction to the faucet set the transaction fees back to 0.001 to get certain transactions prioritized again.

Start anonymization again

moli · Sep 13, 2014

kryptofoo said:
Been trying to anonymize 5000 tDRK 4 rounds for last 16 hours or so. First 1000 went really fast then nothing for a seemingly long time. Isn't there anybody I can mix with? Sniff sniff

I sent all my anon tdrk to the faucet. Just set my wallet to pair with you, 5000 tdrk to keep anonymized, 4 rounds. I think we need a 3rd client to pair also.

oblox · Sep 13, 2014

moli said:
I think the handful testers we have right now are testing large amounts. That's why we get stuck in trying to anonymize small amounts. When I paired with you, I kept seeing my wallet say "Submitted to masternode, Waiting for more entries (2/3)" and later it said "Submitted to masternode, Waiting for more entries (1/3)", I thought maybe you dropped out.

Perhaps, that's why I am hoping eduffield could clarify if it is in fact the issue of lack of small amount testers or not. The wallet has been running since the 11th with the only stoppage due to upgrading to the latest test version.

moli · Sep 13, 2014

oblox said:
Perhaps, that's why I am hoping eduffield could clarify if it is in fact the issue of lack of small amount testers or not. The wallet has been running since the 11th with the only stoppage due to upgrading to the latest test version.

If you submit this to JIRA, make sure also send your debug.log file and the wallet.dat.

qwizzie · Sep 13, 2014

Ppl who got stuck with denominations (hours and hours since last denomination) check your debug.log and see which amount Darksend+ is trying to pair with.
Watch for this line : Submiting Darksend for ......

If the amount is a rare amount then stop darksend+ and calculate which amount would make it easily pairable again .. the rest of the amount will
need to go outside yr wallet. This needs to be done through coin control by selecting those amounts with the lesser rounds then start Darksend+ again.
note : so only select those amounts with lesser rounds that make it a rare amount... normal amounts are 1-10-100-500-1024-4096
lets say for example darksend+ is trying to pair 550 then only 50 of those lesser rounds needs to go out.

My own wallet is now happily denominating again after having stuck for 15 hours trying to pair a 600 amount which is rather rare. I sent 100 out and it worked again.

Stealth923 · Sep 13, 2014

got my 3 wallets going - denominated 3 wallets with 1000 DRK 8 rounds in 30 min...insanely fast!!! will keep them topped up and constantly denominating so other people can benefit

status bar looks like its working accurately too!!

I can feel it - open source is close!

DrkMiner · Sep 13, 2014

Anyone trying small amounts? 10, 20 DRK?

Darksend is idle for hours. Trying 10 DRK/2 rounds.

moli · Sep 13, 2014

I'm testing 5000 tdrk, 4 rounds. Just got another tester to join us testing the same amount. So far my wallet got 4 DS denominate fees, but 0 anon tdrk.

eduffield · Sep 13, 2014

****** PLEASE UPDATE TO v9.13.9 (Stable) OR 10.13.9 (RC) *******

There's good reason why we don't use three participants for DS on testnet, there's just not enough wallets to combine with to keep the network going all of the time. I really just wanted to make sure 3 worked, so we could use it on mainnet.

- Testnet merges use two, while mainnet merges will use 3 participants
- Fixed the endless splitting issue causes by splitting 1000DRK and not making a DS compatible input

(waiting for flare's excellent compiling service)

DrkMiner · Sep 13, 2014

Great!
Kept getting "Payment to yourself".
Could we change that message to "Denominate"?

We could have tried 3 participants on the testnet.

We just have to setup time that ALL tester will try any amount with max of 20 DRK.

Than different time for 100 DRK etc...

jpr · Sep 13, 2014

Now when I just installed 10.13.8

JGCMiner · Sep 13, 2014

DrkMiner said:
Great!
Kept getting "Payment to yourself".
Could we change that message to "Denominate"?

There is already a message called "Darksend Denominate"... Maybe splitting inputs? Dunno

DrkMiner · Sep 13, 2014

JGCMiner said:
There is already a message called "Darksend Denominate"... Maybe splitting inputs? Dunno

In the Transaction tab, have a better "type" description

flare · Sep 13, 2014

eduffield said:
****** PLEASE UPDATE TO v9.13.9 (Stable) OR 10.13.9 (RC) *******

There's good reason why we don't use three participants for DS on testnet, there's just not enough wallets to combine with to keep the network going all of the time. I really just wanted to make sure 3 worked, so we could use it on mainnet.

- Testnet merges use two, while mainnet merges will use 3 participants
- Fixed the endless splitting issue causes by splitting 1000DRK and not making a DS compatible input

(waiting for flare's excellent compiling service)

v0.10.13.x RC5 Testing

Active member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Active member

Well-known member

Core Developer

Active member

Well-known member

Active member

Active member

Well-known member