This development dispatch covers work completed since the Decred v0.1.0 release from April 18th, 2016. Since then, developers have merged 18 pull requests of code into 3 software repositories. During this period, a total of 18 commits occurred in these repositories and represent modifications to the effect of 848 lines of code added to and 275 lines removed from the codebase. A series of RFP milestones were achieved and paid for from the development subsidy. Milestones paid for include (See: Status and Expenditures): RFP-3: Port has been completed (limited milestones) (6ae7950) RFP-6: Pool has been successfully tested for 1 week on testnet and configuration verified (x4) (e5bcf90, f9ea04d, e94c540, fc58177) Binaries: https://github.com/decred/decred-release/releases/tag/v0.1.1 dcrd Added a check to disallow by default transactions to be broadcast if the fee per kilobyte is 100x above the minimum (0.01 DCR). This check does not affect other incoming transactions to the node, it only checks transactions going out of the node (124-b7e88f4) Added a new RPC command called ticketfeeinfo to provide statistical information about ticket fees per kilobyte for the mempool, recent blocks, and recent difficulty windows (132-41abd20) Updated fee calculation (125-a5ca12f), error handling (127-82a0e17), documentation (128-fd40243), and versioning (136-4f8ad73) Credits: @ay-p, @ceejep, @jcv, @jolan dcrwallet Fixed the build when using newer versions of the gRPC packages (189-3f411f0) Isolated the address pool to prevent excessive address creation (192-4e689d6) Fixed an issue where the purchaseticket RPC command would fail if the ticket address or pool address was undeclared, not allowing the user to set the ticket expiry if either was absent (198-0740964) Added ability to change the ticket autopurchase frequency and changed the frequency to a default of 1 (can be changed with the command-line argument --ticketbuyfreq=) (201-823bddb) Fixed an issue that prevented Paymetheus from starting properly (203-b28ae9a) Updated dust calculation (193-df0af6e), fee calculation (194-5d77ddb), documentation (195-2a1e04c, 208-0bcc487), index scan length (196-38cdae0), user prompts (202-8ed9a8c), and versioning (209-c5e47fb) Credits: @ay-p, @ceejep, @jcv, @jrick dcrrpcclient Updated documentation (13-c69fe51) Credits: @jolan
how i put manual the fees at 0.08 at last version because that command does not work -- wallet setticketfee 0.08
I'm really liking the ticketfeeinfo addition. Great work guys. On another note, are there any plans to include the time of when a transaction is sent vs when it is confirmed? It looks like listtransactions in dcrctl has always been setup that way but I'm not sure if it's even implemented into (what I would call - pardon me if this is not the correct term) the transaction header. It would be interesting to see how long some of these transactions are sitting in the mempool compared to the fees users are setting.
@_ingsoc @ceejep So if we won't start dcrwallet with "--ticketbuyfreq=x" flag it will always be 1? Is there any command to setticketbuyfreq afterwards or there is going to be in the future? I've checked dcrctl -l and I didn't find any, a setticketbuyfreq command will be useful so as we won't need to restart dcrwallet to change it. Also it will be good if we'll can check ticketbuyfreq value through walletinfo command or at least with a getticketbuyfreq command.
Legacy ticket purchasing is going to be removed relatively soon in favor of the dedicated program that is being developed for it. https://github.com/cjepson/dcrticketbuyer Whether or not that needs its own interactive RPC is another question, but the hope is that it will be feature rich enough to be set it and forget it.
Why is the wallet trying to insert a transaction all on its own? Ticket price is well above my max price. 22:07:29 2016-04-29 [INF] TMGR: Inserting unconfirmed transaction 8d0fbb4a21d7c2 03d4ba9011076c94f6a05b46c89e32efbb64e575d2f1be8066