Search results

300k is a long way from 5k but I see the issue. However, if something that serious is going to happen then a hard limit should be set and the user should not be able to override it. In one wallet (spread over many addresses) I'd imagine a few hundred people would have 5000DRK. Thus I think...

I guess if it can be disabled by the user than any limit is OK, but ... whats' the problem with letting it run for any amount( i.e without the troublesome target setting as is the case now)? Fees? Time required? Bloat?

Got it. Thanks. :smile:

I am probably just confused, but does this mean that regardless of the current number of available masternodes only the best 20 are used for anonymization?

Because it is a 0.001 DRK fee per round. Currently that is about 0.5 cents (and it can be lowered in the future if DRK's price really blows up). Small price to pay to avoid DOS and bloat attacks.

I think the UI improvements are very important even if it means the launch is delayed a bit. It would be a problem if a lack of clarity led to a panic once the less technical start using the software. Also, "smart" denomination was mentioned above where after a send only the required amount is...

Is issue also the reason for the collateral fees? Also this is a crosspost from Camosoul on bitcointalk.... Seems plausible. Has this been considered?

As I said, the denominate fee is normal (and it will happen on mainnet) and the collateral fee is a bug needing to be fixed.

I am not sure if he still needs it, but you might want to send your log file to Evan.

Denominate fees are normal and they should be 0.001 DRK per round. This is so someone can't DOS the network or bloat up the blockchain for free by purposely causing a large number of pointless denomination transactions. As for the collateral fee, so long as you didn't close the client or have...

Rather than rolling back -- wouldn't a testnet2 set up for just launch simulations be easier? Plus, if a date is set and the community is informed then for a short time we could probably get a lot more miners/masternodes making it that much closer to mainnet.

Looking forward to the windows version. Haven't found the time to get linux set up, but I have been itching to see autoDenom in action. :grin:

Sorry for derailing. I didn't think that was off topic (as my points had nothing to do with speculation but how to handle things when the latest test version goes live) but I will apologize anyway. Carry on. :smile:

How the market behaves should be of nobody's concern. If there is a pump then so be it -- if there is not then who cares. My point is that this release is just like a hardfork for masternodes (whether they recieve payment is dependent on them updating) and it is really bad form to launch...

If masternodes are going to get kicked then I think a date for RC4's release should be announced in advance and the binaries available at least a couple days before said date. Otherwise people are going to claim their nodes got ninja banned and accuse insiders of scooping up tons of payments...

Yes with RC4 you will be able to Darksend any amount. However, currently Darksend enabled wallets are linux only on testnet. So you can try to get linux set up or wait for RC4 on mainnet. It is not expected to be a long wait.

I agree as well... at the very least the fess must be much lower. Someone said a few pages back that for 3000 DRK in 10 hours he paid 0.3 DRK in fees. Assuming that there are no rouge collateral charges in that amount (as that is bug currently being fixed) then that is far too expensive for an...

Hmm, on mainnet I figure that most will have their wallets protected -- which is in conflict with the fact that the more wallets participating in the autoDeom the better. Also it would mean that a requirement for anonymity would be leaving the wallet unprotected, a condition most would find...

Excellent post babygiraffe! I hope Evan considers this optimization.

This is a very good point. Let the user select from a set of ranges. For example -- Basic anonymity: 2-4, moderate anonymity: 3-6, and high anonymity: 6-8. Then the client decides the mixing depth in a random fashion based on the selected range.