Many stakepool users didn't succeed to buy any ticket with the ticketfee = 0.20 DCR / KB (stakepool ticket transaction size is ~ 540 bytes) The maximum fee was 0.40 DCR per kb, and average mined somewhere in the range 0.21 - 0.36 dcr
Yeah, non-stakepool users have a large advantage when the price is now. I got some tickets with a 0.21 fee, which works out at only 0.063DCR/ticket which isn't much worse than the starting ticket fees.
Yeah, I think stakepools should start to control the market and never allow price go below 25 DCR. The best combo is Stakepool + ticket with the 0.003 DCR fee. In this case, you also protected from the costs of missed tickets. Because if you paid 0.20 DCR fee for the ticket and it didn't cast a vote, you lose your money (high fee + no reward)
Indeed. My prediction was definitely an informed one based on watching the behavior of ticket prices over the past several weeks and an understanding of how the ticket buyer works in relation to minimum and maximum target windows based on the VWAP, the default price scales which most users won't (and really probably shouldn't) change, expiration windows, etc. I don't think you're implying that original dev funds control all the tickets by this statement since I've seen several of your other posts and know you're well informed, however to clarify for others reading since it would be easy to misinterpret, the original devs do not have more coins locked than their proportion of the coins to the total supply and won't for the initial year as was posted back near launch. That is to say, that the origdev+c0 portion of the total supply is 29.8% right now which means origdevs+c0 do not control more than 29.8% of the total tickets in the pool. Or in other words, since there are currently ~41637 tickets in the live ticket pool, at most ~12407 of those tickets are staked by origdevs+c0. In fact, it is pretty easy to see it is much lower than that in reality by looking at the number of coins in block 1 that have never been moved and dividing it back out by the average ticket purchase price.
@davecgh Oh yes, I wasn't implying that all the tickets were from the dev funds, merely that the PoS locked funds approaching that value was a milestone of sorts of the currency The same applies to the airdrop funds!
It may be a good idea to put something on dcrstats like "Next price given n many tickets enter the blockchain in the remaining period", where n is the 'user' field from the results of Code: estimatestakediff n For example, with current difficulty, Code: n next ticket difficulty 100 10.67179739 200 12.18077499 300 13.68975260 400 15.19873021 500 16.70770782 etc You can also plug in the number of tickets currently in the mempool to help inform the user of what the next ticket difficulty might be. Right now, the way the users behave is strange. The majority of users are willing to forego a weeks worth of potential reward to wait until the difficulty is below the weighted average price. Someone with a lot of coins, in the meantime, can keep the difficulty above the average and reap almost all the tickets and reward. Users also have no problem competing and getting reduced reward above the loss of their funds to fees in competitive periods.
That's consumer behavior for you! People are not always logical... but they (the customer) are always right.