if u dont set a changeaddress ur wallet will create a new address for everytime a transaction create a change returned to u
the change addresses only visible in coin control

when u add it to diamond.conf
changeaddress=youraddress
its always active if u use there ur mainadress u will get the change always back there

if u want to use it only for actual session u can set it at wallet gui

Great. It seems my hashrate in last 1000 blocks is 7.5%, and 8% in last 100 blocks  

hmmm seems people get  "token expired" when try to register at
http://dmdeu.miningfield.com/

luis is sleeping already he will look at it tomorrow

Thanks, but I like the anonymity.

This parameter is needed, that not to increase quantity of the hidden addresses and not to increase the "weight" of the wallet?
if so, then why this feature is not enabled by default?

because we did take that part unchanged from our bitcoin anchestor

same as all coins who build up on bitcoin code base

but if demand is bog enought we can think about it

that we added the changeaddress= option for diamond.conf seems to me a acceptable solution

because how we know automated what addres people wana use as change address

the risc that no changeaddress setting make wallet heave only exist after a lot years for a normal useage

in that timeframe we can expect code changes that will take care about long term optimization of wallets

so short answer:

yes all kind of stuff to wallet dust optimisations this is on todo list but at low priority because for 99% of users feelable effects are multiple years away

cryptonit

I am interested in more safety of the file a wallet.dat, therefore I am interested parameter changeaddress=
example, hypothetical situation:
I posted a few coins in the outgoing transaction.
at this time the wallet creates additional hidden addresses...
and at this time for any reasons there is a failure of an operating system, turned off electricity and other.
under such circumstances the wallet can not manage to create the necessary hidden addresses and the file wallet.dat, will be damaged.
this leads to the loss of coins that have appeared in the wallet after the last backup file wallet.dat.
as example: was 1000 coins (I have a backup wallet.dat 1000 coins). I got 100 coins and sent 50. total wallet should remain in 1050 coins.
system crash (for any reason). wallet.dat damaged.
as a result I have only 1000 coins (backup wallet.dat 1000 coins), but not 1050.
you understand that I want to tell?
Even if such a situation may occur once every 10 years, this could lead to loss of all the coins. I understand that there is still a lot of other options damage wallet.dat, but I'm talking about a parameter changeaddress=  in diamond.conf.
If do not create hidden addresses the probability of damage is much lower.
Correct me if I'm wrong.

If I have 3 addresses in wallet the fact that in this case I need to write in diamond.conf?

no matter how fast i try it always bring token expired even after delete all cache stuff and restart browser....

there must be a issue

lets say im pretty impressed how stable price is after all that troubles we had

that make me very optimistic for the future when issues solved
and stability is again a word u can connect with dmd network