Dd-22: V1.0.0 (04/25/17)

Discussion in 'Development Dispatches' started by jy-p, Apr 26, 2017.

  1. 2017/08/25 - Decred v1.0.8 released! → Release Notes  → Downloads
  1. zero

    zero Full Member

    Jan 1, 2016
    #21 zero, May 3, 2017
    Last edited: May 5, 2017
    @jy-p @davecgh @moo1337 My dcrwallet reads (ticket) max price wrong. I start dcrwallet with (among the rest flags):

    --ticketbuyer.maxpriceabsolute=56.1 --ticketbuyer.balancetomaintainabsolute=0 --ticketbuyer.balancetomaintainrelative=0 and I get this message:
    [INF] TKBY: Not buying because max price exceeded: (max price: 53.13271588 DCR, ticket price: 54.08115247 DCR)

    Then I start it with:
    --ticketbuyer.maxpriceabsolute=60.1 --ticketbuyer.balancetomaintainabsolute=0 --ticketbuyer.balancetomaintainrelative=0 and I get this message:
    [INF] TKBY: Not buying because max price exceeded: (max price: 53.13xxxxxx DCR, ticket price: 54.08115247 DCR) - xxxxxx: a little different value than the previous one.

    Do I miss something or there is a problem with dcrwallet?

    I am running v1.0.1 on Windows 10 x64. A couple days ago I didn't have such problem with the same setup and version. (max price: = was the exact --ticketbuyer.maxpriceabsolute I set).
  2. gravityz3r0

    gravityz3r0 New Member

    Feb 28, 2016
    Have you got your issue fixed? If not try slack channel, they are very active there.
  3. adam2312

    adam2312 Jr. Member

    Jan 11, 2016
    Same issues here. Please post if resolved.
  4. ClokworkGremlin

    ClokworkGremlin Sr. Member

    Jan 10, 2016
    Whatever I want.
    Similar problem. Set max ticket price over 100, wallet reads it as just over 50DCR.
  5. Johnshpon3

    Johnshpon3 Member

    Dec 25, 2015
    You need to set parameter ticketbuyer.maxpricerelative=1.6 or higher. I set it to 2, by default is 1.25. This factor is scaling factor for setting the maximum price, multiplies by the average price so usually need to be over default.

    But when the maxpricescaling will be adequate you will stumble upon fee problems. I found out that at least ticketbuyer.feetargetscaling and ticketbuyer.minfee need to be seted.
    If ticketbuyer.minfee stays default 0.01, ticketbuyer will begin to buy new tickets in the first next block when price drops and it was no tickets in mempool before so avareage ticket fee is 0, but it will buy with minfee, that mean tickets would not be mined and they expire after 16 blocks (default value).
    I useed to buy tickets manualy now since v1.0.1 because ticketbuyer is real PITA and I was not able to tweak it enough to buy tickets automaticaly.
    adam2312 likes this.

Share This Page