This has been fixed for a while, miners don't seem to want to upgrade and get more money. https://github.com/decred/dcrd/commit/2ba4225eb7496c817eb0e3ac0c08c45420d960b1
I use --reuseaddresses option and set ticketfee to 0.05 when purchase ticket, but both of them is not work in v0.1.0. ticket purchase transaction fee is lower than 0.05. and it sometimes happens SStx purchase transaction was not found in the explorer. Do I need to recreate my wallet from seed? edit: ticket purchase transaction showed up after a while.
@ceejep wrote that median txfee is .16 in last $8/SStx rounds. That does not seem to be a random pick from mempool. That suggests that half of successful tickets were pricing fees above .16DCR. Why do people raise setxfee if it does not help? Is that a waste of DCR?
Also @Dyrk shows .025DCR as average fees in this current $8DCR/SStx round. This would suggest very small percent of fees above .16DCR. This suggests a high concentration of high-fee SStxs picked from mempool. (assuming this round is similar to last $8/SStx round)
This may be harsh, but I started disconnecting versions that are older. All my peers are now v0.1.0 as of now. Looking to automate this, but for now: Code: dcrctl -u YourUserName -P YourPassword getpeerinfo dcrctl -u YourUserName -P YourPassword node disconnect (id)
That is because most need 140 characters or less in order to comprehend a message. Someone needs to get on this (sticky, shortened summary) in the Announcements section and on social media outlets. Major benefits of each update should be summarized in this way. Social media part would have a secondary effect of helping additionally with awareness.
Does anyone know when tickets move from ownmempooltix to immature? Or as it happened before, get's returned to me.
ownmempooltix are sstx transactions waiting to be confirmed. As soon as a miner includes your transaction in a block, it will move to immature (I believe it happens in the following block immediately after confirmation). From there it sits as an immature ticket for 256 blocks until it joins the pool with the rest of the tickets waiting to be selected.
Oh yeah, don't write, "Can now adjust ticket price"; rather write, "allows you to stake more tickets by adjusting fees up when SStx price is low." When a developer lists upgrades, it doesn't mean much to regular users. Write about the ultimate use of feature or improvement and write it in plain language.
I think the Release Notes need to be a little more verbose. These issue needed to be spelled out, restated, reiterated and put in boldface type. Oh, and cgminer had a lot of room for improvement, to put it mildly. I'm hoping for gominer to become the standard soon.
I haven't had any trouble understanding the list of improvements with each release. That's probably attributed to my interest in the subject which drives me to investigate and do my own research on things I don't understand. When this project started, I knew very little of the back end measures and technicalities that drive a cryptocurrency. The users that are interested will take it upon themselves to learn what they don't understand. The code is already incredibly well documented for our general viewing; I don't think anything else needs to be spoon fed here. I would leave room for exceptions, of course. However, IMO, part of the fun of the project is figuring stuff out on my own. I think the best way to learn about things is through critical thinking, analysis, and the desire to learn.
I would agree with this.. Especially for the issue with the miners and ticket fees. I must have missed the release notes because I was still under the impression that it was not fixed until I saw ceejep's post this morning: 50% of the current network hashrate is coming from suprnova and coinmine. Ensuring that these guys stay updated would probably dramatically help the ticket purchase fee situation. I know @ocminer runs suprnova but I'm not sure if the operator of coinmine is on this forum.
Critical thinking sure. So I'm nuts thinking setting the ticket transaction fee to 0.5 would equal a ticket transaction fee of 0.5 for each ticket. Silly me.
OK I see no luck with ~ 8.40 ticket price as well, I believe none of my ownmempooltix will go to immature. I really don't like the new ticketfee calculation, I would prefer the total fee to be the fixed value I set. I also don't like the new auto-consolidation to ticket price feature since consolidation fees spend unreturned all the time for no reason most of the times. But I guess I am the only one who don't like these new things. @ceejep Is there going to be a way to set a lower ticket price value as well with max ticket price value so as to be able to choose a ticket price range for auto buying tickets in the future? That way we can leave the lower ticket price ranges for those willing to give in fees almost half of the vote reward.
True, this distinction has not always been clear. But I see where David is coming from, myself being similarly obsessive w.r.t. this project. @zero I'm also a little disappointed with my staking situation this round, as I have 20 tickets in the mempool that are not likely to get mined. My fees were 0.08ish (per kB as we now know). I wish I could pull them out without penalty and buy again.
That's great! It is interesting stuff, for sure. Now, if the ultimate success depended on the few dozen people who want to spend months of their lives learning the backend of Decred, then we would be all set doing it the same way. We do not want to do things so that you can understand it all; rather, we want to do it to enable understanding in the least of us. One day, we can just push these updates to GUI, automated wallets with easy operation controls/voting. For now, we want the largest userbase with the tools we have. The upside of participating in the Decred project, tutorials, and simple explanations of update benefits blasted across social media will accomplish that.
Well, the new automated buyer should work much better after the bugs are shaken out of it, and dcrd, and dcrwallet. It has a scaling penalty for higher difficulties and has a maximum fees to spend per ticket at lower difficulties. I could add a cutoff to stop buying tickets if the fee is too high too, good idea. Here's a repo if you want to be guinea pigs. Once I have it working well I'll get an official repo for it, but right now it's WIP. https://github.com/cjepson/dcrticketbuyer It should be trivial after to hack in your own personal rules. It's also designed to be highly tuneable.
FYI, it is not luck. I got 149 SStx out of ownmempool to immature with a setticketfee of .165 in this round. That is steep but 1.80/.165 (or even 3(kb) * .165) DCR is a pretty good return on investment.