Updated OP text with a new section for development dispatches and documented the latest updates. Also, do remember to get your proposals in for RFP-2, RFP-3, and RFP-4. They all close at 06:00 PM UTC March 8th, 2016. If you are into miner and pool development, get a proposal in for RFP-5, which closes very soon at 06:00 PM UTC March 4th, 2016.

This development dispatch covers work completed since the initial Decred commits on February 8th, 2016. Since then, developers have merged 83 pull requests of code into 10 software repositories. During this period, a total of 139 commits occurred in these repositories and represent modifications to the effect of 5,499 lines of code added to and 1,952 lines removed from the codebase. In addition, a native Windows wallet GUI is being ported to Decred. Finally, 5 requests for proposals (RFPs) were opened to involve new developers in Decred's development.

dcrd (v0.0.5)

• Improved getwork RPC handling (13-42ae03b)
  
• Added command and result interfaces for incoming new RPC call for wallet (16-3968690)
  
• Reduced amount of fees required before a transaction is considered free (20-5d04f47)
  
• Improved the use of analysis tools in goclean.sh (24-1954bf2) and resolved issues caught (28-14769a7)
  
• Added getcoinsupply RPC call to track total coin supply (30-c77e541), cached its results (34-2edc483), and fixed issues (55-aa21c12)
  
• Added JSON handling for per ticket manipulation of the VoteBits field in wallet (31-2f9fc2d)
  
• Completed the framework to enable the address indexer for the memory pool by default (35-9740110)
  
• Modified JSON framework to enable two new RPC calls (existsliveticket, getstakeinfo) (38-3f706d2)
  
• Changed CheckpointConfirmations to 4,096 (39-0e60dff)
  
• Added an initial blockchain checkpoint (44-203be41)
  
• Increased the default number of outbound peers from 3 to 8 (46-5e0163f)
  
• Modified getrawmempool to allow for the selection of specific transaction types from the mempool (51-18acc11)
  
• Avoid possible false hits within the templatePool map (48-638fff6)
  
• Added framework handling to the new listscripts JSON RPC call for wallet (54-f001389)
  
• Fixed issues with documentation (19-7e1e205), address indexer (01e9bfd), RPC call results (36-4868ed4), btcsuite artifacts (21-1e22c04), notifications (45-1652a0d), configuration files (23-33ff72f), stack tests (12-4d5ee10), error handling (18-01e9bfd, 60-bc44bcf), and RPC help (61-4c24488)
  
• Updated versioning (62-fbede49, 22-1b42b87, 56-33ff4be)
  

dcrwallet (v0.0.5)

• Fixed a rare panic that could occur when importing multisignature scripts found in the blockchain that were unconfirmed (27-7ea5117)
  
• Allowed wallet to accept hex or words as seed (31-2a407e4)
  
• Added getwalletfee RPC call to show fee while creating transactions (32-414c03d)
  
• Added per-ticket setting of the VoteBits field so that different VoteBits settings can be user-selected at stake pools via the RPC (38-6a938f9)
  
• Corrected fee estimation for general transactions (37-4bdb6ac)
  
• Added better tracking of the address index in the wallet (41-93408e9)
  
• Fixed references to removed dcrjson results for single fields (42-b47feed)
  
• Added getstakeinfo command to the wallet to give various statistics, such as the number of tickets it has in mempool, the number of tickets it has that are mature or live, the number of votes it has cast, and the total rewards earned by the wallet (44-f2d928b)
  
• Disabled unsafe RPC calls on mainnet that allowed the removal of unencrypted private data from the wallet (dumpprivkey, getseed) and fixed extended pubkey storage (45-28b1bf0)
  
• Improved performance of the getstakeinfo RPC call (47-e875bf3)
  
• Fixed a bug in multisignature handling that would occasionally cause the inappropriate failing of transactions being added to the transaction manager (54-9d1ed9d, 55-8d41590)
  
• Fixed a panic occurring from TxResults response (49-6d8f657)
  
• Added listscripts RPC call to allow a user to dump the redeem scripts contained in the wallet (56-d3ebcbb)
  
• Corrected storing of votes and revocations in the case of redundant wallets (57-9c1e89f, 58-ddb741a)
  
• Added automatic pruning of old tickets and expired transactions from the internal memory pool (59-04a75c0)
  
• Fixed issues with documentation (36-cc4956b) and rare panics (43-76bd7bd)
  
• Updated versioning (63-ee2a72a)
  

dcrrpcclient (v0.0.5)

• Added getticketvotebits and setticketvotebits to the wallet RPC client (1-17bbf91)
  
• Fixed issues with address functions (2-8ec8807)
  
• Added functionality required to support getstakeinfo and call it, and two new wrappers for daemon RPC functions (missedtickets, existsliveticket) (3-2d67a90)
  
• Added GetBalanceMinConfType to specify balance type (4-c222e4a)
  
• Added TxType flags to getrawmempool access, so that a user may specify which type of transaction they would like returned from the mempool (5-680d8ff)
  

cgminer (v0.0.5)

• Fixed difficulty on front end UI (1-d7751bb)
  
• Addressed compilation issues and allow ATI/AMD OpenCL toolkits via environment variables (2-4adc167, 3-bceed92)
  
• Added a --cert option that allows a user to supply a self-signed certificate for the RPC server (6-27fb09d)
  
• Changed Autoconf to address cross-compilation without breaking native Linux building (9-7bd2c58)
  
• Assigned a 64-bit per-work unique ID to each work order, ensuring that GPUs ran in cgminer instances will never repeat the same work (10-d701a89)
  
• Added an include in a header check for adl_sdk.h to work (12-72afa18)
  
• Reverted cgminer difficulty calculation (16-4291617)
  

Web Wallet

• Fixed issues with fee calculation (1-f80e2fe), language (5-1b50a7b)
  
• Fixed JavaScript unit tests to use PhantomJS (12-8476a19)
  
• Fixed fee to send all and make sure it does not go below min fee (13-a583538)
  

Block Explorer

• Added getcoinsupply RPC (1-e578aa9) and recognized it (1-52fc02e)
  
• Fixed block reward calculation to be more accurate for non-critical information (2-2a8e57d)
  
• Added votes and freshstake to block lists and front page (3-b3cd6da, 8-06ba621)
  
• Displayed available supply on status page (4-411d6f5)
  
• Switched from dbits to atoms as the unit choice (5-0f648f9)
  
• Hardcoded checks for block version and block 0/1 (5-6d50513)
  
• Fixed issues with Bitcoin artifacts (6-fd58b9b), block reward aesthetics (9-9576ec5), and block reward calculations (4-8a58c40)
  

RFPs

• Added RFP0001: Windows Wallet UI/UX Overhaul (1-d4f53d1, 2-02d3441)
  
• Added RFP0002: Web Wallet Ticket and Stake Pool Support (3-bdf7edf, 4-e7f95c3)
  
• Added RFP0003: Network Status Dashboard (5-cd2f31e, 6-de6a0ee)
  
• Added RFP0004: Refactor and Update Wiki Documentation (7-3aa1d0c)
  
• Added RFP0005: Mining Protocol Development And Pool Integration (10-698224f)
  

Quick update on what has been going on with the mainnet stake pool. There has been quite a bit of progress behind the scenes to make it more stable.

Basic timeline:

• Got a proof-of-concept working and released
• Added support for allowing users to control their votes or defer decision making to the pool
• Realized due to a deployment issue that the pool was not operating properly
• Added stats so the pool operator/users could see the pool's history/status
• Stats were too slow to be useful through WAN links with a large wallet
• Stats speed was improved greatly
• Lots of bug fixes and stability/reliability/debugging ability improvements in between the various steps above
• When checking the faster stats code devs found/fixed a bug that caused synchronized pool wallets to have different statistics
• More instrumentation added for verifying wallets are in sync and restoring/syncing from a live wallet/SQL

The last 2 items were just addressed late last night. Hoping today is the day for a stable pool that clearly reports its status.

Updated the OP text to reflect the latest RFP. RFP-3 deals with visualizing the Decred network. If you know data, it is to port and build a network status dashboard. The next RFP will be for documentation and user guides. Then there will be an RFP for the miner devs. These all run in parallel.

Updated the OP text to reflect proof-of-stake (PoS) mining becoming active at block 4,096. The mainnet stake pool code underwent optimization and further testing today and is coming this week. The code will be made free and open-source software as well, so it will be really good to see if the project can work with others who are interested in becoming stake pool operators. You will be able to charge a nominal fee for doing so. It would be ideal to get at least 10 stake pools up and running to help decentralize the effort.

If you use the web wallet, the DCR goes to your wallet on your computer. The web wallet is just an interface - the wallet sits on your own computer. It is a true wallet, not an account service. But yes, a GUI is crucial - it is the reason RFP0001 is about bringing that forward.

This has been raised elsewhere as well and should receive attention. The web wallet is a client that runs in your browser. The name can indeed cause confusion thinking the wallet is somehow stored server-side (which is incorrect), so this is a good point to address.

The OP text has been updated with information about RFP0002. If you are a web dev with Node.js experience, get involved and help decentralise Decred development. If your proposal is accepted, you will be paid in DCR.

Available supply is now visible on the status page of the block explorer. It updates on every block. You can also pull a feed from: https://mainnet.decred.org/api/status?q=getCoinSupply

Note: This shows available supply in atoms, to see the available supply in decred, divide by 1e8. Thus, 174987865164800÷100000000 = 1749878.651648 DCR.

No developer or project member will trade any of their bring-up DCR for 12 months and c0 will not trade any of its bring-up DCR for 24 months. These funds are therefore ineligible for trading during that time. Source: The Project's Commitment

PoW miners are reporting their hash rates in the following hardware performance thread as well. Hopefully that is of use to you!

If you are referring to buying stake tickets using the web wallet, that is not currently possible. That is part of an RFP coming this week.

Decred is looking for a UI/UX designer (or developer). This is a paid contract to help the project overhaul the current UI/UX of its wallet software. Estimated work is 40 hours/week or greater. Please see here for details. Please get in touch or post if you need more information and I will help you!

Decred is looking for a UI/UX designer (or developer). This is a paid contract to help the project overhaul the current UI/UX of its wallet software. Estimated work is 40 hours/week or greater. Please see here for details. Please get in touch or post if you need more information and I will help you!

Two big milestones today.

The first point is that RFPs have now begun (announcement). RFP-1 is for a Windows wallet UI/UX overhaul. So if you're a UI/UX whiz, show the Decred community your craft and get paid in DCR. It's your project too.

The second point is that the current Decred developers will work without taking a cent from the development organisation (DHG) for three full months. That means all money from the development subsidy will now go to any new developers that apply (and are successful) for these RFPs. Hopefully you can see from this how serious the project is about including other developers in the process.

Testnet stake pool is live! Come jump in the stake pool and help test. The hope is to iron out the rest of the code, open-source it, and transfer stake pooling to anyone serious about running their own stake pool. Announcement is here! You can sign up for the pool here: https://teststakepool.decred.org.

Remember, this is for testnet so we can all test it together and make sure it's all working nicely before we transition it to mainnet. This is for PoS mining in a way that does not require you to solo mine.

Decred is now on both Bittrex and Bleutrade. Will keep working on more as the dev keeps churning! Should have a stake pool you can join very soon as well.

For those curious about the final airdrop review process and how it was conducted, information has been released. Announcement here.

Should also state that multiple accounts were merged into one. So if you applied fraudulently using multiple accounts, only one of your accounts will work. It was felt that this was a reasonable process on dealing with attempted fraud. There will be consolidated information about this.

256.