Its 2017...and if asked when I started this project if I'd be making this particular post I'd have laughed! The quest for a true mass market capable solution has surely been a long one and despite everything I'm glad that our resolve hasn't wavered and I'm very proud about what has been achieved. Say what you will about the development timescales and delays, but we enter 2017 in the very unique and powerful position of being the only game in town that has real workable solutions to not one, but a number of critical problems that everyone in this space is facing. I'm talking about scalability, efficiency, node incentives, near seamless infrastructure integration and of course an economic model that has the possibility to forge the future of monetary policies. At the risk of sounding brash, a solution to just one of those would be justification for enthusiastic chest banging....we have them all and as far as I'm aware no one is even close to being on our tail. Each and every one of you involved in the project, even the critical among us have played a part in molding and crafting the path that has led us to where we are today. I'm more confident now than ever that we are going to disrupt not just finance, but a number of industries more than we could possibly imagine. 2016, while being quiet on the front lines, served to answer all of the remaining question marks surrounding the possibility of achieving the end goal. Finalizing the EVEI consensus and it passing the "death test" was key to removing a number of said question marks for a number of our goals and allowing us to enter 2017 with confidence. In fact, such was the level of progress on that front in 2016, that there are no major question marks remaining which could stand in our way to a launch this coming year. The only major component still requiring significant development is the economics, which is itself in the final stages of code cutting and will be completed (save for heavy testing) within the next 4-6 weeks. Aside from development, a large amount of progress was made in other areas of the project that will contribute significantly to our success. Key relationships have been forged with a number of parties, both at a personal and professional level, which will also serve us well throughout 2017. The most significant of these will come into effect post launch, as behind the scenes we have been actively engaged in securing merchant and retailer participation to allow the purchase of millions of everyday items using our currency very soon after launch. Exciting times I'm sure you'll agree! Without further ado, here is the schedule as it currently stands for 2017. I've spent a lot of time putting together the following plan over the past few months, honing it to be as efficient and realistic as possible. I do not expect there to be any major deviation even when considering "Dan Time" January First on the agenda is my yearly holiday. 2016 was quite simply hell and I'll save you the details. Simply, I need one! I'm leaving tomorrow and return on Monday the 9th all refreshed As soon as I'm home I have a meetings in London on the 10th and 11th which will focus on our debit card solution. Hopefully these meetings will provide some clarity on how to enable the millions of devices globally to accept our cards with minimal fuss and give a clearer picture what we need to do and how long it is going to take. From the 12th - 23rd I'll be concentrating solely on code with a view to wrap up the remaining refactoring work and polishing I spent most of December doing so that I can drop a beta soon after. We should also have agreed and committed to the technology branding by this point and the various branding requirements such as logos, websites etc should be well under way, perhaps even nearing completion. I have a marketing design team standing by to get moving on this ASAP. 23rd-25th London again for Blockchain Expo, either myself or Rob will be presenting at this event. Remainder of January will consist of finishing up the refactoring if not already done, continue with economics and drop a succession of betas for you guys to test. Also during the course of Jan there are articles covering the project going to print in 2 major financial and business journals. I'll drop references to them on the forum as they are published. February February is pedal to the metal month in terms of development. By this point we should have had a few good rounds of beta testing and economics will be nearing the point where it can also be tested hard. The first 3rd party project using our technology should be well underway and is an application targeting the insurance industry. I'll provide more concrete detail on this as and when I can due to me being under NDA and the project is as yet unannounced. Development will consist of much of the same, refactoring, cleaning code, fixing minor issues, but also adding APIs and other functions to support 3rd party projects such as the one above. It is my intention to bring February to an close and have a V0.99 client ready to go to open beta. To achieve that most of the month will be focused on development while keeping various "irons in the fire" at the required temperature. March Following on from February, I'd like to kick off March with a bang and run an open beta under the guise of the newly created tech brand. Having a V0.99 client will be a huge benefit as I also want to get moving on fundraising that will see us through launch and mass market roll out. I don't think there has been a fundraising campaign previously where the tech is all but complete due to development of the idea being privately funded. I expect that fact alone will attract a lot of investment interest as the risk is massively reduced. An ICO will play a part in our fund raising efforts, but will not be the only campaign that we will operate. More on those later. By March end I also would like to have expanded the London team in order to handle more business development, and have in place a development team of maybe 5-10 people located near to where I live in a dedicated office. That team will be tasked with bringing the V0.99 client to a V1.0 and also the creation of mobile clients and supporting 3rd party developers. April Successive drops of the open beta and nearing that elusive v1.0 A code audit and security review is on the cards at this stage, unfortunately this is expensive and the only real option is to use raised funds to pay for it. Other than the development team itself, this will likely be the largest single expense directly associated with finalizing V1.0 development. I expect by April end to be able to set an accurate launch window, and upon the completion of the audit, set one in stone. As of today, I would consider a loose "end Q2/start Q3" to be realistic and sensible considering the remaining development and preparations required.