Dd-11: V0.1.4 (05/27/16)

Discussion in 'Development Dispatches' started by tacotime, May 27, 2016.

  1. 2017/12/15 - Decred v1.1.2 released! → Release Notes  → Downloads
  1. gravityz3r0

    gravityz3r0 New Member

    Feb 28, 2016
    83
    13
    #21 gravityz3r0, May 29, 2016
    Last edited: May 29, 2016
    Thanks for the quick response guys, seems to be up and running now, however, it doesn't seems to be purchasing ticket just as yet. Any idea why? This is my current setting :


    maxperblock=10
    maxinmempool=2000
    maxpriceabsolute=18
    balancetomaintain=0
    expirydelta=16
    min/maxpricescale disabled. Commented out.
    pricetarget=0.0
    maxfee=0.2
    minfee=0.01
    feesource=mean
    feetargetscaling=1.07
    txfee=0.01
    blockstoavg=11

    Is there a minimum amount of blocks required after launch before the ticketbuyer is able to compute and purchase the ticket effectively?

    Additionally, what can i expect to see when i run "walletinfo" now that's i've started using the ticketbuyer?

    Do i need to omit the --balancetomaintaiin and --ticketmaxprice flag from dcrwallet now that i have ticketbuyer to handle it?
     
  2. chappjc

    chappjc Full Member
    Developer Pool Operator (PoS)

    It needed to have a new block come in.

    I'm not sure what the default min ticket fee is, but consider raising it.
     
  3. gravityz3r0

    gravityz3r0 New Member

    Feb 28, 2016
    83
    13
    Ok! WIll do! Thanks!

    One more thing, do i need to omit the --balancetomaintain and --ticketmaxprice flag from dcrwallet now that i have ticketbuyer to handle it?

    In another word, i will only launch my dcrwallet with "-u xxx -P xxx --enablestakemining" and nothing else.
     
  4. gravityz3r0

    gravityz3r0 New Member

    Feb 28, 2016
    83
    13
    Nothing is happening even after 12 blocks, no purchase whatsoever, even my web UI is empty.

    Untitled.png
     
  5. ceejep

    ceejep Sr. Member
    Developer

    Dec 14, 2015
    192
    220
    Add this line to your run command to see trace output. You may have something configured wrong.
    Code:
    dcrticketbuyer -C ticketbuyer.conf -d TKBY=trace
    Also, if you are running the HTTP server, please make sure you bind it to localhost in your configuration file.

    Code:
    httpsvrbind=localhost
    By default it opens on all interfaces right now. The default was changed in a pull request:

    https://github.com/decred/dcrticketbuyer/pull/3
     
    zero likes this.
  6. ceejep

    ceejep Sr. Member
    Developer

    Dec 14, 2015
    192
    220
    dcrticketbuyer is pretty new code and bugs are still emerging. It will eventually be the replacement for the previous ticket buying code, which is still possible to use in wallet. That's partially why we haven't updated the docs yet, we're still waiting for people to try it out and urging very large amounts of caution if they're using it on mainnet.

    To answer your parameters with questions:
    Code:
    httpsvrport=7770
    Make sure to bind the server to localhost unless you want it to be externally accessible:
    Code:
    httpsvrbind=localhost
    Code:
    testnet=false !Can we totally remove this for mainnet?!
    Yes

    Code:
    poolfees=5.00 !If the pool fee is 5%!
    Yes

    Code:
    #maxpricescale=2.0 !#disabled? Or better remove it if we don’t want it?!
    #minpricescale=0.7  !#disabled? Or better remove it if we don’t want it?!
    Either is fine (comment out or remove)

    Code:
    pricetarget=0.0         !0.0 = disabled? Or better remove it if we don’t want it?!
    I would leave disabled, chappjc changes his. It's basically the target price to buy tickets at. If it's unset it'll target a combination of the 10-day VWAP and ticket pool price. Above that price, it applies an exponential penalty to the number of tickets purchased that difficulty round.

    Code:
    expirydelta=140
    This means your tickets won't expire for 140 blocks once purchased, if they don't get into a block because fees are too low. This should be smaller (5-20 blocks).

    Code:
    feesource=mean  !median isn’t stable right now! 
    Yes, should be fixed this week

    Code:
    txfee=0.01  !lower than 0.01 can cause problems?!
    Yes, do not set this lower than 0.01

    Code:
    maxpriceabsolute=14.0
    That price is too low, as the current average is ~18. You will probably want to set this higher or it will never buy tickets.

    Code:
    feetargetscaling=1.01
    May want to set this higher to ensure tickets get into block

    Code:
    blockstoavg=22  !If it hasn’t any previous values to check, where it will scan them from?!
    It's supposed to use the fees in the closest ticket price of the last 10 difficulty periods, but chappjc says there might be a bug that prevents this from working properly. I'm looking into it

    Hope this helps
     
    zero likes this.
  7. Nimrod

    Nimrod New Member

    Mar 4, 2016
    102
    18
    Male
    I've had two crashes of dcrd.exe in two days on two separate machines with v0.1.4. Never had any crashes before.
    No time yet to check any further details but this version appears less stable. Replace binaries as usual from v0.1.3.
     
  8. zero

    zero Full Member

    Jan 1, 2016
    288
    121
    Male
    #28 zero, May 30, 2016
    Last edited: May 30, 2016
    @ceejep @chappjc Thanks for the info, suggestions and for your time explaining things about dcrticketbuyer. I think I am going to update to v0.1.4 soon but I'll might leave dcrticketbuyer for later. I am sure that dcrticketbuyer is a huge improvement.

    My example values were very low in purpose so it will not cause any problem to someone that might want to try them out since I wasn't very sure in general about dcrticketbuyer.

    In ticketbuyer-example.conf, httpsvrbind parameter is only mentioned as optional in comments over httpsvrport. I think httpsvrbind=localhost should be included even commented out or disabled after httpsvrport with the appropriate comments and explanations about it.
     
  9. davecgh

    davecgh Hero Member
    Developer Organizer

    Dec 31, 2015
    642
    788
    Male
    United States
    On my recommendation, @ceejep changed the default in https://github.com/decred/dcrticketbuyer/pull/3 to be locahost, so if you don't specify anything in the conf with the latest code, it will only bind to locahost.
     
    zero likes this.
  10. root

    root Member

    Feb 3, 2016
    381
    76
    I saw hundreds of "[ERR] PEER: Can't read message ..." with version 0.1.4 dcrd, around 50 with version 0.1.3, but zero with 0.1.2 and before.
    Is there any problem with network code ?
     
  11. gravityz3r0

    gravityz3r0 New Member

    Feb 28, 2016
    83
    13
    Can someone please post a screenshot output of a "dcrticketbuyer" window assuming everything is working as it should?

    I have a feeling that mine is not working correctly although it says the connection to dcrd and dcrwallet client is successful and "beginning to purchase ticket". All I see I my dcrticketbuyer window is just a bunch of connected block and nothing else. No fee information, no purchase attempt.
     
  12. root

    root Member

    Feb 3, 2016
    381
    76
    12:34:33 2016-05-17 [TRC] RPCC: Sending command [ticketvwap] with id 4669
    12:34:33 2016-05-17 [TRC] RPCC: Received response for id 4669 (result 5.7552594)
    12:34:33 2016-05-17 [TRC] TKBY: Calculated average ticket price: 5.92433192 Coin
    12:34:33 2016-05-17 [TRC] RPCC: Sending command [getstakedifficulty] with id 3300
    12:34:33 2016-05-17 [TRC] RPCC: Received response for id 3300 (result {"current":4.65645465,"next":4.65645465})
    12:34:33 2016-05-17 [TRC] RPCC: Sending command [estimatestakediff] with id 4670
    12:34:33 2016-05-17 [TRC] RPCC: Received response for id 4670 (result {"min":2.69633361,"max":9.26698489,"expected":7.56458887
    })
    12:34:33 2016-05-17 [TRC] RPCC: Sending command [getbalance] with id 3301
    12:34:33 2016-05-17 [TRC] RPCC: Received response for id 3301 (result 1997.62291389)
    12:34:33 2016-05-17 [DBG] TKBY: Current spendable balance at height 77206 for account 'default': 1997.62291389 Coin
    12:34:33 2016-05-17 [TRC] RPCC: Sending command [ticketfeeinfo] with id 4671
    12:34:33 2016-05-17 [TRC] RPCC: Received response for id 4671 (result {"feeinfomempool":{"number":23,"min":1.01e-05,"max":1.11
    1e-05,"mean":1.016e-05,"median":1.01e-05,"stddev":2.1e-07},"feeinfoblocks":[{"height":77206,"number":13,"min":1.01e-05,"max":1
    .022e-05,"mean":1.012e-05,"median":1.013e-05,"stddev":3e-08},{"height":77205,"number":15,"min":1.01e-05,"max":1.018e-05,"mean"
    :1.011e-05,"median":1.01e-05,"stddev":2e-08},{"height":77204,"number":14,"min":1.01e-05,"max":1.022e-05,"mean":1.012e-05,"medi
    an":1.013e-05,"stddev":3e-08},{"height":77203,"number":17,"min":1.01e-05,"max":1.114e-05,"mean":1.018e-05,"median":1.013e-05,"
    stddev":2.5e-07},{"height":77202,"number":14,"min":1.01e-05,"max":1.022e-05,"mean":1.011e-05,"median":1.01e-05,"stddev":3e-08}
    ],"feeinfowindows":null})
    12:34:33 2016-05-17 [TRC] RPCC: Sending command [setticketfee] with id 3302
    12:34:33 2016-05-17 [TRC] RPCC: Received response for id 3302 (result true)
    12:34:33 2016-05-17 [DBG] TKBY: Mean fee for the last blocks or window period was 1.0118e-05; this was scaled to 1.10286200000
    00001e-05
    12:34:33 2016-05-17 [TRC] RPCC: Sending command [getrawchangeaddress] with id 3303
    12:34:33 2016-05-17 [TRC] RPCC: Received response for id 3303 (result "TsoaEkGscjaWLc2zxM3SUXWNdNwjy9mQhNo")
    12:34:33 2016-05-17 [TRC] RPCC: Sending command [purchaseticket] with id 3304
    12:34:33 2016-05-17 [TRC] RPCC: Received response for id 3304 (result ["1aa32fe9946b97293d26f4bc825546294705d30946f5d755aee126
    f24607e86a","3ca87a84b5aa041f1eb7ba22b387d01d21d2c5a6d6e3f2287b8366d22046a2be"])
    12:34:33 2016-05-17 [INF] TKBY: Purchased ticket 1aa32fe9946b97293d26f4bc825546294705d30946f5d755aee126f24607e86a at stake dif
    ficulty 4.65645465 (1.103e-05 fees per KB used)
    12:34:33 2016-05-17 [INF] TKBY: Purchased ticket 3ca87a84b5aa041f1eb7ba22b387d01d21d2c5a6d6e3f2287b8366d22046a2be at stake dif
    ficulty 4.65645465 (1.103e-05 fees per KB used)
    12:34:33 2016-05-17 [DBG] TKBY: Tickets purchased so far in this window: 18
    12:34:33 2016-05-17 [DBG] TKBY: Tickets remaining to be purchased in this window: 408
    12:34:33 2016-05-17 [TRC] RPCC: Sending command [getbalance] with id 3305
    12:34:33 2016-05-17 [TRC] RPCC: Received response for id 3305 (result 1988.30937699)
    12:34:33 2016-05-17 [DBG] TKBY: Final spendable balance at height 77206 for account 'default' after ticket purchases: 1988.309
    37699 Coin
    12:35:24 2016-05-17 [TRC] RPCC: Received notification [blockconnected]
    12:35:24 2016-05-17 [INF] DCRD: Block height 77207 connected
    12:35:24 2016-05-17 [TRC] RPCC: Sending command [walletinfo] with id 3306
    12:35:24 2016-05-17 [TRC] RPCC: Received response for id 3306 (result {"daemonconnected":true,"unlocked":true,"txfee":0.001,"t
    icketfee":1.103e-05,"ticketmaxprice":50,"balancetomaintain":9.9999999e+07,"stakemining":true})
    12:35:24 2016-05-17 [TRC] RPCC: Sending command [getticketpoolvalue] with id 4672
    12:35:24 2016-05-17 [TRC] RPCC: Received response for id 4672 (result 29748.66616074)
    12:35:24 2016-05-17 [TRC] RPCC: Sending command [getbestblockhash] with id 4673
    12:35:24 2016-05-17 [TRC] RPCC: Received response for id 4673 (result "00000000016415881e3e2c7b2a56bdcd97dcfd509ee5efec094d456
    0ec16a0ae")
    12:35:24 2016-05-17 [TRC] RPCC: Sending command [getblock] with id 4674
    12:35:24 2016-05-17 [TRC] RPCC: Received response for id 4674 (result "00000000586183a801ca546729d9d6b00189fe03aaafd239420d2d2
    9fba2bd04000000006a403f35bfe235465b63be0a1b5d37ed4afeb1602aba22ee1df442b046397b7ab839fc40e084fed580f98f382d53916216ad9932bd659
    a98d5aea87908af582f0100acf1c1d3a2ea05000f0015130000ecbb061c992fc11b00000000972d0100ed310000eaf33a57223ecafc811fbe8d001cfc2b000
    000000000000000000000000000000000000000000000000000001201000000010000000000000000000000000000000000000000000000000000000000000
    000ffffffff00ffffffff0307ca4f0a00000000000017a9144fa6cbd0dbe5ec407fe4c8ad374e667771fa0d448700000000000000000000266a24972d01000
    0000000000000000000000000000000000000000000000096c4ce226e060acb92d6df3d0000000000001976a9144a7738e64d6ca33fa9ac65ddcf39b9f5a41
    ef54288ac00000000000000000135862e480000000000000000ffffffff0800002f646372642f0100000003badd6a36ccf3d9faf4c4c7022a2bf6f678f988a
    e48e45141717e42d93d10a8940100000000ffffffffbaf80f611e8e40d9c80a85d80b22633cb468466a7c945073c .....
    .....
    .....
    .....
     
  13. gravityz3r0

    gravityz3r0 New Member

    Feb 28, 2016
    83
    13
    Thank you @root

    Any idea why my webUI is showing empty graphs? Untitled22.png Untitled11.png
     
  14. root

    root Member

    Feb 3, 2016
    381
    76
    you need to copy the whole
    webui directory from git (just download ZIP and unpack),
    place it along with dcrticketbuyer.
    CSV data are stored there.
     
  15. gravityz3r0

    gravityz3r0 New Member

    Feb 28, 2016
    83
    13
    #35 gravityz3r0, May 31, 2016
    Last edited: May 31, 2016
    1. I have already all the CSV files as far as i can see in the webui folder. The webUI folder is placed in the root directory containing binaries dcrd, dcrwallet, etc. (which is by default). However, the graph are still empty.

    Edit- The CSV is being updated to the latest block properly, as evident from opening the individual CSV files with Notepad. However, this is not being translated to the UI.

    2. Does it has anything to do with the browser that i used? I tried on Chrome. IE is giving me some script error and unable to load the UI completely. (crappy as usual). Firefox is also giving me blank graphs. I check the page source and it seems like all the .js and .csv file is where it's supposed to be. I'm suspecting that the script isn't loaded properly.

    3. Another thing that i noticed is that, dcrticketbuyer only perform the calculation and the decision to purchase ticket approximately 45sec-1min after each block is connected. Will this delay prevent it from purchasing ticket in the event that 2 or 3 blocks is mined in rapid succession that the dcrticketbuyer does not have the chance to calculate in time?
     
  16. root

    root Member

    Feb 3, 2016
    381
    76
    1/ so the problem is possibly with permissions ? Using Windows ?
    2/ no JAva needed, just binaries, maybe default settings disable javascript from reading local CSV files ?
    3/ as per your description, probably yes, I have not looked thoroughly yet. See the thread about dcrticketbuyer
     
  17. gravityz3r0

    gravityz3r0 New Member

    Feb 28, 2016
    83
    13
    #37 gravityz3r0, May 31, 2016
    Last edited: May 31, 2016
    1. Yes using Windows. Chrome, IE, Firefox with no joy. Not sure what do you mean by permission. Can't find any such option in the browser settings.

    EDIT- It's not working in mobile phone browser neither. Same result.

    2. Java is enabled. I even downloaded the Java application and verified it with another java-enabled website just to be sure.

    3. If that's the case, we may risk missing some blocks and therefore miss the chance to get our ticket mined. Perhaps its a better idea not to use ticketbuyer until the response time is improved.
     
  18. ceejep

    ceejep Sr. Member
    Developer

    Dec 14, 2015
    192
    220
    1/2. Only tested on firefox. Make sure you have the lib folder and all the contents of the lib folder, since they contain the JS libraries needed to make the graphs.
    https://github.com/decred/dcrticketbuyer/tree/master/webui

    3. Are you connecting to a remote daemon? That will make it slower. You can connect a local daemon to your remote daemon with "--connect=123.45.67.89:12345" and then connect your wallet and ticketbuyer to that. If the connect flag is passed into daemon, it will ONLY connect to that node, meaning your IP isn't otherwise leaked.
     
  19. zero

    zero Full Member

    Jan 1, 2016
    288
    121
    Male
    Good to know. I think it would be better that way.

    @ceejep A minpriceabsolute parameter will be useful in dcrticketbuyer, to help someone easily choose the price range he wants to make ticket purchases.
     
  20. David

    David Sr. Member

    Jan 22, 2016
    364
    207
    Male
    USA
    I've got a small issue here... I am getting getting tons of "Lost peer x.x.x.x" outputs on 2 separate machines on two separate networks, and also a few errors. However, it does seem to keep the number of connections at 8 by immediately replacing a lost peer.

    17:30:13 2016-06-01 [INF] BMGR: New valid peer 81.169.187.209:9108 (outbound) (/dcrwire:0.0.1/dcrd:0.1.3/)
    17:30:26 2016-06-01 [INF] BMGR: Lost peer 162.243.226.209:9108 (outbound)
    17:31:11 2016-06-01 [INF] BMGR: New valid peer 166.78.62.30:9108 (outbound) (/dcrwire:0.1.0/dcrd:0.1.4/)
    17:32:33 2016-06-01 [INF] BMGR: New valid peer 178.63.29.108:9108 (outbound) (/dcrwire:0.0.1/dcrd:0.1.3/)
    17:36:37 2016-06-01 [INF] BMGR: Processed 1 block in the last 6m43.01s (7 transactions, height 33296, 2016-06-01 17:36:09 -0700 PDT)
    17:37:19 2016-06-01 [INF] BMGR: Lost peer 45.35.251.48:9108 (outbound)
    17:37:19 2016-06-01 [INF] BMGR: New valid peer 67.169.35.31:9108 (outbound) (/dcrwire:0.0.1/dcrd:0.1.3/)
    17:40:29 2016-06-01 [INF] BMGR: Processed 1 block in the last 3m52s (3 transactions, height 33297, 2016-06-01 17:39:33 -0700 PDT)
    17:41:04 2016-06-01 [INF] BMGR: Lost peer 67.169.35.31:9108 (outbound)
    17:41:13 2016-06-01 [INF] BMGR: Lost peer 81.169.187.209:9108 (outbound)
    17:41:13 2016-06-01 [INF] BMGR: New valid peer 212.83.146.45:9108 (outbound) (/dcrwire:0.1.0/dcrd:0.1.4/)
    17:41:13 2016-06-01 [INF] BMGR: New valid peer 158.69.196.59:9108 (outbound) (/dcrwire:0.1.0/dcrd:0.1.4/)
    17:51:47 2016-06-01 [INF] BMGR: Processed 1 block in the last 11m17.88s (4 transactions, height 33298, 2016-06-01 17:50:50 -0700 PDT)
    17:52:18 2016-06-01 [INF] BMGR: Lost peer 178.63.29.108:9108 (outbound)
    17:52:18 2016-06-01 [INF] BMGR: New valid peer 178.150.207.53:9108 (outbound) (/dcrwire:0.1.0/dcrd:0.1.4/)
    17:52:19 2016-06-01 [INF] BMGR: Lost peer 176.9.98.88:9108 (outbound)
    17:52:28 2016-06-01 [INF] BMGR: Lost peer 158.69.196.59:9108 (outbound)
    17:52:28 2016-06-01 [INF] BMGR: New valid peer 67.169.35.31:9108 (outbound) (/dcrwire:0.0.1/dcrd:0.1.3/)
    17:54:26 2016-06-01 [ERR] PEER: Can't read message from 188.213.166.128:9108 (outbound): read tcp 172.31.50.148:42766->188.213.166.128:9108: read: connection reset by peer
    17:54:26 2016-06-01 [INF] BMGR: New valid peer 178.63.29.108:9108 (outbound) (/dcrwire:0.0.1/dcrd:0.1.3/)
    17:55:37 2016-06-01 [INF] BMGR: Processed 1 block in the last 3m49.54s (1 transaction, height 33299, 2016-06-01 17:55:01 -0700 PDT)
    17:56:11 2016-06-01 [INF] BMGR: Lost peer 166.78.62.30:9108 (outbound)
    17:56:11 2016-06-01 [INF] BMGR: New valid peer 163.172.27.11:9108 (outbound) (/dcrwire:0.1.0/dcrd:0.1.4/)
    17:56:13 2016-06-01 [INF] BMGR: Lost peer 212.83.146.45:9108 (outbound)
    17:56:19 2016-06-01 [INF] BMGR: Lost peer 104.255.231.169:9108 (outbound)
    17:56:19 2016-06-01 [INF] BMGR: New valid peer 75.9.96.199:9108 (outbound) (/dcrwire:0.0.1/dcrd:0.1.0/)
    17:56:19 2016-06-01 [INF] BMGR: New valid peer 5.249.147.90:9108 (outbound) (/dcrwire:0.0.1/dcrd:0.0.10/)
    17:57:39 2016-06-01 [INF] BMGR: Processed 1 block in the last 2m2.48s (7 transactions, height 33300, 2016-06-01 17:57:24 -0700 PDT)
    17:58:00 2016-06-01 [INF] BMGR: Processed 1 block in the last 21.12s (1 transaction, height 33301, 2016-06-01 17:57:33 -0700 PDT)
     

Share This Page