Dd-7: V0.1.0 (04/18/16)

Hello,

I'm trying to figure out what to do after this upgrade to version 0.1.0. Basically from what I understand from this thread and my own upgrade:

• I cannot reliably purchase tickets.
• Or if I can purchase tickets, it's because the price is higher and not many tickets attempts have been made for the block.

A little history (as I understand it):

• All my ~6 DCR ticket purchases have not made it into the block chain.
• The DCR that I attempted to purchase tickets with have been returned to me minus the consolidation fee.

So how do I handle this?

• Do I downgrade to the previous version?
• If I have to downgrade, should I re-create wallet?
• Is there an emergency fix for this in the works? (I'm sure there is)

Please let me know how to proceed.

Thank you.

 

Ok, so I think I understand what's going on. Please correct me if I'm wrong.

Transaction fees have been defaulted to 0.01 so all those tickets that were waiting to be purchased by previous versions of the wallet were set to 0.05 as default, thus rendering my attempted purchase of the cheap tickets to go to the back of the line.

At ticket price of ~16 DCR just now, I was able to purchase some tickets at the tx fee of 0.01 because there were less than 50 in the total mem pool for that block.

So, if I want to compete with older versions of the DCR wallet, I have to settxfee to 0.05+ when the price goes lower again.

 

Not exactly, even with 0.01 fees, you might be able to purchase tickets even with 0.05 fees in line.

 

Thank you devs, for me everything works correctly and it has been running for some days now

 

I set fee to 0.1 and not single ticket of 47 in line was mined. Happened now and also last time when price was under 10. When price rise there were no problem even with 0.01 fee, ticket was mined inside 2-3 blocks time.

 

Well, I set my fee to 0.015 and gotten 43 tickets and another 15 not in time to be mined. So yea, if that answers you.. Luck I guess..

 

I was on version 0.0.10 and I purchase 4 tickets in one block. with the dcrctl command.
And 2 in another. Didn't face any issue. And don't worry in a few days time (my guess is two days. Guessing from the previous trend.) Value will fall again. Buy then.

 

Even with my SStx PoS crash from the upgrade, I was able to purchase 24 SStx that just matured today; guess that makes them the 6.5DCR tickets. I had to restore from seed and missed 6 votes. I then purchased at 16DCR just fine. I guess restoring from seed fixed it. Wonder why some did not need to restore.

 

Higher tx fees are supposed to put you higher in the mem pool. When prices are low, the mem pool gets filled up to capacity. It doesn't matter what the tx fees are when the mem pool has space for your tickets.

 

So far this upgrade is good, except I had to learn the lesson of keeping an eye on the tx fee since I used to keep it at default, I have to do this manually now.

settxfee lower when prices are higher, settxfee higher (or back to old default) when there is a rush to buy cheap tickets.

I like the auto consolidate that is happening now so it's one less thing to worry about.

 

I never worried about that before and had no problems; it is good to know that I don't have to start worrying, though.

 

Ticket fees were very high at the last 6.5 DCR round. About 8000 tickets did not get in.

You can see the fees using "ticketfeeinfo", which gives stats about fees for different window periods and previous blocks, plus mempool.

Code:

    {
      "startheight": 21168,
      "endheight": 21312,
      "number": 2880,
      "min": 0.01,
      "max": 0.375,
      "mean": 0.13400829,
      "median": 0.16891891,
      "stddev": 0.06412928
    }

To get a ticket in that round probably required in the range of 0.10-0.30 DCR/KB.

 

@ceejep, What exactly is the command to run this, I tried with and without the --wallet flag.

Code:

dcrctl -u YourUserName -P YourPassword --wallet ticketfeeinfo
Unrecognized command 'ticketfeeinfo'
Specify -l to list available commands

dcrctl -u YourUserName -P YourPassword ticketfeeinfo
Unrecognized command 'ticketfeeinfo'
Specify -l to list available commands

 

Yes, tx fees doesn't matter on the mem pool part. What I meant was that in the mem pool, there are various number of tx fees. And I believe that they are chosen at random, instead of yours being 0.05 fee and you got selected instead of my 0.015. Which is proven as of now.

 

@davecgh, I'm running v0.1.0 from the 18th, is the ticketfeeinfo command there?

 

This seems like a bug but I think I read somewhere they are trying to fix it.

 

yea, issues were raised regarding that and I'm sure they are resolving it. Its been like that since PoS started btw.

 

Command is in master, it will be in an official build next week.