1. 2017/09/23 - Decred v1.1.0 released! → Release Notes  → Downloads
  1. Kandiru

    Kandiru Member

    Feb 21, 2016
    202
    85
    Yeah, I would also like to be able to change these parameters while the wallet is running. I'm still using the --enablestakemining option as it lets me use dcrctl to change the maxprice and ticket fee while the wallet is running.

    A dcrctl --wallet reloadticketbuyerconfig RPC call would be good, which would make it re-parse it's config file and alter the parameters accordingly. Or a command to change each option, but that's probably a bit excessive.
     
  2. jcv

    jcv Full Member
    Developer

    We do need to add the ticketbuying options to the rpc server for sure. I don't think we would want to add a reload config rpc call since that has too many strange cases with no good solution (e.g., you change the rpc password in the config file). But adding the individual ticketbuyer knobs to rpc is definitely something that should be done.
     
    zero and Kandiru like this.
  3. zero

    zero Full Member

    Jan 1, 2016
    288
    121
    Male
    #23 zero, Feb 28, 2017
    Last edited: Feb 28, 2017
    Good to know it's planned for the future releases, I mean it's not urgent but it will be a very useful addition. The new ticket buyer seems to work very well and it gives better feedback of what is going on with ticket buying.

    I'd like to ask something else, do I have to use --reuseaddresses? I haven't use it so far and I didn't have any problem. Is there a point - number of dcrwallet addresses, that it might cause problems? Does paymetheus works with --reuseaddresses enabled or with --reuseaddresses behavior in general on buying tickets?
     
  4. Shadowlance

    Shadowlance Full Member

    Jan 9, 2016
    218
    154
    Male
    You don't have to and from a privacy standpoint it makes it harder to track transactions if you don't. Historically, people (myself included) used that switch as the wallet had trouble buying tickets if the funds were spread over multiple addresses. Not sure if that's a problem anymore.
     
    zero likes this.
  5. zero

    zero Full Member

    Jan 1, 2016
    288
    121
    Male
    Yeah I remember I've consolidate 2 or 3 times on the very early releases due to spending issues, but after a release and over (I don't remember the version) I didn't have such an issue again so I didn't use --reuseaddresses. That's why I asked if this issue is completely fixed now because dcrwallet keeps creating many new addresses just for buying tickets and I don't know if I should start using --reuseaddresses because of it.

    Anyway I'll continue without --reuseaddresses and if I'll have spending issues I'll just consolidate and start using --reuseaddresses flag.

    Thanks.
     
  6. jrick

    jrick Member
    Developer

    Jan 4, 2016
    88
    81
    Male
    just to clarify this (because i understand how it may be confusing) --reuseaddresses and consolidate have nothing to do with each other. Even if you reuse addresses, you will still create the same number of outputs, and if the wallet becomes too dusty you may still want to use consolidate to "fix" it.
     
    zero likes this.
  7. zero

    zero Full Member

    Jan 1, 2016
    288
    121
    Male
    Sorry for the confusion. So I was wrong thinking that with reuse addresses I could eliminate these "dust" issues. Anyway I didn't have such issues for months now but maybe others with higher balance than me that make more transactions in general may still have problems but they can consolidate to fix them.
     

Share This Page