hi everybody Charles Hoskinson here broadcasting live from warm sunny Colorado I just returned from my long trip all around the world I final trip was in Scotland I was in Edinburgh for Plutus fest and that was a great degree of fun I had a chance to finally sit down with the Plutus and Marlowe team and I got the whole team together it's very diverse international team so it was quite a bit of fun to see everybody in the same room at the same time I also had a chance to shave so the beard was getting pretty long and now the the fear the beard Charles is is over I did want to give you guys a quick and brief update about where we have gone throughout this year and some things to look forward to towards the end of the year so let's get to it so it's been a very long year it's been a year where we as a company I which Kay and the broader Cardno ecosystem has definitely learned quite a bit and through this process we have done a lot in particular we've written over 40 papers 20 of which have been peer reviewed and the other 20 are in some various stages of review or their technical reports we've learned how to do what Duncan Koontz likes to call evidence-based engineering but it's more typically called specification driven engineering where we write a formal specification the specification looks like some provenance of logic and mathematics from that specification you extract code and then you're able to prove that your implementation is equivalent to that extracted code and therefore you follow the spec so come December 18th will be the very first time we've shipped anything in the history of Cardno that remotely connects to a specification and that's going to be the one point for release it took quite a bit of time for us to get to the one point for release there were variety of reasons for that some were structural reasons some were scope creep some were just we didn't fully anticipate the state of complexity of these things or the where the code base was at but overall we finally got in there it took seven release candidates it was quite a bit of quite a bit of effort but I'm very happy to see how things have evolved I'm very happy to see where we're at entering into 2019 now some lessons learned we learned a completely new way of doing QA a completely new way of running a helpdesk our helpdesk has serviced well over 10,000 tickets throughout its history our QA system has managed to dramatically decrease the QA cycle massively improved the test coverage that we have for a product and overall they've just managed to aggregate together about nine months worth of lessons over four major releases and so going into 2019 we'll see better tests and smaller releases less ha fixes and certainly a much higher quote quality so while 2018 was very difficult especially for us on the engineering side 2019 will be much more manageable and easier for us furthermore we've begun a systematic decoupling of things that are in our stack starting with the wallet back-end the very next version of it will actually be completely decoupled and we'll be able to connect the formally verified wallet back-end from just the Haskell client to also connect it with our rest client as well so that decoupling should be finished sometime January and actually as a result of that we're gonna have a very fast development time for wallet back-end features this includes things like multi-sig now this includes things like manuals collection of the TXO manual transaction creation offline transactions so we'll take a lot of the things that we've now seen with the RUS client we'll be able to move these things that's general Dedalus so sometime during early 2019 within the first quarter likely devilís will get a command line and you'll be able to interface directly with the wallet back-end through that command line just through normal everyday Dedalus and hopefully we'll be able to take that whole wallet scripting idea that we had with Cardinal rust and pour that over into the main client so that there will be no difference between those two we've had a huge amount of success here with your pours program I think this is one of the crown jewels there's really two major crown jewels of cardano's portfolio the other being Plutus in Marlowe and our work with yella and K and Ora Boris is the other crown jewel we've had a huge amount of success with it starting with orb or Sprouse earlier this year going to Israel to War Horse Genesis where we went to Canada to CCS - or Boers BFT and all this surrounding infrastructure around it works we now have multiple implementations of warhorse BFT we actually have five separate implementations for varying degrees of uses from our enterprise Ledger's offering to stuff involving Cardno and things on the scholar side we also have several prototypes and limitations of or board's Genesis in fact the Haskell implementation of warhorse is so elegant you can Reaper ammeter eyes the same code base to run and be if T mode Prowse motor Genesis mode and you can even put in different network stacks so it's pretty cool pretty interesting really excited to see how that evolved materialized and how much we learned and it's also really cool to see that we're now also having a really deep involved conversation with how we intend on writing our ledger spec and how we intend on handing delegation so we're going to be doing a workshop for HK and some of our third-party partners come early January in Berlin specifically about the delegation specification and to finalize that specification much like Plutus fest kind of forced us to finalize the specification for pluto's 1.0 and marlowe 1.0 will be doing the exact same with the with the delegation specification which will also be made publicly available just like the wallet back in spec was made publicly available what's really nice is we've actually managed to take the ledger spec which defines all the rules for validating what is legitimate and ledger and what is not legitimate and leisure and create almost like a DSL to describe different ledger rules and so it's very easy for us to describe the old ledger which is the byron ledger and what the new Shelley leisure is going to look like and hope is over a series of iterations to not only be able to do this easily but also to massively simplify some of the rules where and when we can so that we have overall simpler code base and we've eschewed unnecessary complexity particularly around the update system and validation of whether an update is correct or not so what's really exciting though is that because the ledger spec now lives as it does and the network spec now lives as it does and other parts of the system now live as they do overall the Cardinal codebase I'd say is considerably higher quality once jelly's released then it's ever been in its history and it's going to probably be the highest quality codebase I would argue of any cryptocurrency ever made and will have an enormous amount of evidence for that statement because we'll have great property based testing it'll be a very concise codebase wonderful in to end testing and and so forth and you know any third party can take a look at it and you see that there's definitely a lot of thought that went into this and have a very clear understanding of why the code behaves the way it does and how the code works and how to maintain an upgraded so long year a lot of hard fought battles just ton of science ton of engineering very difficult to deal with all the exchanges especially given that there were language barriers and cultural barriers and different sets of structures and we had to deal with all of this while having a product and market that just couldn't work for certain people given that that was the case early this year i authorized the work of the icarus program and that was really one of our fastest pieces of engineering we started in early March gathering business requirements and technical requirements then we built an entire engineering team in less than two months and that team over a period of just three months was able to actually build and wallet from scratch involving both a rust component and a JavaScript component and have that go through a full security on it and in short order Merkel was able to take that reference codebase icarus and turn it into the arroyo wallet since the time of launch they've already done several major updates and they've already a very large user base constituting 11 percent of the entire Cardinal population and they have some great statistics on uses and and so forth so that was a great win and we're real excited and happy to see how fast that was able to materialize and come along and we're also excited and happy to see that it's in tracted some third party participation like vacuum labs and others to start having conversations with us now one of the most commonly requested integrations in our ecosystem has been ledger and I feel I should talk about ledger a little bit why there was some difficulty there there was really three factors that came together that made it very difficult for us to get ledger support right when we launched first we were using a different type of cryptography and a different type of HD wallet than what the ledger team was normally used to encountering so usually people have some variant of ECDSA we were using at 255 19 and our HD wallet involved a non-deterministic non-standard scheme this was because of design decisions that Sarah Kell made now while this was not didn't suffer a security issue it was secure it was quite difficult for people just to take something off the shelf and make this work easily so that was one dimension second there was a middleman involved on creating support on the ledger side principally that was called meta Legend meta layer and they were working with the Cardinal foundation and we've historically had some issues there and unfortunately because of that tripartite arrangement where there was a ohk the Cardinal foundation and a third-party developer given the history and other things it dramatically slowed down support integration and then finally on our end we had just simply other priorities and really the thing that was holding his back was to move to a better more standard way of handling the cryptographic side namely deterministic addresses which people see with Icarus style wallets and also to have a new wallet back-end so with the shipping of one point for half of the is done and then the other half the icarus tell address support because we've already done this once before with Icarus it'll be very easy for us to roll that into the wallet back-end so come January we anticipate Icarus style addresses coming to the wallet back-end and the very next update of Cardinal 1.5 will have support for this now the good news is that now that the foundation issues have been resolved and a Mirko has really started scaling up development with the EROEI we've had a lot of discussions about bringing in a third party firm principally vacuum labs to work with both of us to rapidly accelerate ledger support and get ledger support first in a row and then very shortly thereafter into Daedalus with either the next most immediate update or the following update so that you'll be able to use it with both a full node as well as a browser-based interface now the first step was to have vacuum lamps write a report and they did it was I think a 15 16 page report but what is the state of the work that was done previously and their estimate is there's about thirty to fifty man days of engineering that needs to be done to clean up the work that's been done and make sure that the work that's been done is secure so that's not too much and for our moderately sized team two to three people working with a Mirko it probably can be done in short order but that requires a little bit more negotiation and a little bit more effort so so basically we hear you we understand you there were factors that came into play that kind of pushed ledger to the side a little bit but now as an ecosystem we're in a position where we can move much more quickly and we have some great third-party support to allow us to move much more quickly and I personally am allows a user it's been a bit of a frustration for me not to have that in our ecosystem the other factor it's kind of a silent fourth factor was it was never clear until the second half of our year exactly how we would handle cold staking with a hardware wallet device there were many different ways we could do this but we need some sort of basically offline or cold key management system built into Daedalus and this was always anticipated to be something that we handled once we had released Shelly and we had a very clear crystallized ui/ux planned out for the delegation center I've been getting gooey scamp's and mock-ups for the delegation center the registration process and a litany of other things that are Shelley related on a pretty regular basis and we're converging to a final user experience for that now as a subset of that that will be the cold staking component and there are two sites that one is the paper wallet side so one person has a paper wallet there needs to be some mechanism for them to import a credential that allows them to delegate from that paper wallet without having the spending keys go live and hot and live within a computer second there needs to be some sort of mechanism on the ledge aside to permit that for heaven or other hardware wallets now our Marco is also keen on having treszura support in addition to last year and I think there's been some good progress made there as well so these things are coming and now that we have a decoupled wallet back-end we're converging in that direction and that development team seeing a great acceleration and we have low technical that very beautiful code to work with these things will happen fast as for the rest of the components of the system you know the the great advantage of the pain we've gone through the lessons we've learned is that month by month we continue to see much better metrics we see faster development time faster PRS better testing better code quality more turnaround time and when incidents happen we're much even more easily able to resolve those incidents so I'm happy with the direction we still need to do a lot of work we have some divergent teams right now we actually have a rust team and a Haskell team and both of them are building independent full clients for Shelley and they're in a sudden death of whichever one finishes first and our hope is that one of them can get to a test net quickly so that we can start building up the state pool population a few more things a big component of the Shelly release isn't just having the technology ready and the science ready we're converging to that it's also having the commune ready and a big impediment throughout this entire year was the Cardinal foundation not making meaningful investments in community management so there were a lot of programs that came up but we're just never funded or initiated for example one program was called a card oh no Ambassador Program and the basic idea would be creating some mechanism to acknowledge people who have already made substantive contributions to the Cardinal community and to try to create a structured way of communicating with them and potentially even funding their interest long term and then the other concept is the Cardinal hub idea where there are certain people who want to go beyond above and beyond just making occasional or in some cases part two full-time contributions and actually creating an organization and that organization would do Cardinal related things within a jurisdiction in scope now both of these ideas were working you know pretty hand-in-hand and there were a lot of really good idea really good discussions and attempts to create momentum but the prior chairman of the Cardinal foundation always killed them and refused to fund them now that he's gone and he's been replaced with more reasonable Minds it's going to be a very big priority to make sure that these programs get launched as quickly as we can because there's we need to start building up a bottom-up community all across the world and to augment the community we've already had grown it's not to say that we don't have some structure there's already a lot of meetup groups some surprisingly large and subscribing lis diverse locations for example there are some people in Iran there's a surprisingly large group in Colombia Bogota Colombia there's us a great group of people in Eastern Europe in places like Bulgaria and places like Romania good group of people in Ukraine a great group of people in South Korea and Japan all throughout the countries it's just we need to do a better job as an ecosystem providing resources to those who have taken the time to become evangelists in our community and to say good and positive things and teach people about what we're doing so now that the foundation is back very soon statement we'll be made efforts will be made to to try to scale these programs get them out as quickly as possible now as an output of good community management and as an output of an ambassador program and meetup groups will naturally be lots of people wanting to run stink fools and the way that we've decentralized the protocol we anticipate having it roughly a thousand or more participating in the system and our hope is to get to that number as quickly as we can so we ran a pilot just to see what was interest back earlier this year around April and the registration did get far more than a thousand people who expressed interest in running a stinking pool so our hope is to reconstitute that soon within the next 60 days and then try to convert that list as soon as we can when a Shelly test net is operational to get as many people as we can to play around with that chili test then and to learn how staking works and to get ready for the centralization of the entire system we've seen a lot of fun this year some of it was just because of common misunderstandings or applying things that other cryptocurrencies are dealing with us and in some cases they were just baseless lies and attempts to just make people really worried about things they ought not to be one thing for example was this concept of well because shelly is delayed or whatever this means that everything else is delay the reality is that the smart contract work was following a different path than the consensus work the delegation work and the rewriting of the entire code base the smart contract stuff was done by a Scala team and done by a language designing team the language designing team was led by Phil Wadler and well chavarri and they're based out of University of Edinburgh and they had their own group their own resources and they were following a two-year track and that Plutus track and Marlowe track have now come to a research end and we've been moving into actual implementation so none of the Shelly delays from the or war side and the delegation side cascaded into the language side they've been along in a pretty good pace and we're quite happy with the progress made furthermore the work with yella was done with a fork of the mantas client and we ran two tests notes them they've been operational since the summer and we've learned a huge amount about that model run time verifications learned a lot about from that model and in short order we should be able to productize that so we're on target and on schedule for smart contracts and what's going to end up happening is that the Shelly release is going to come out a little later than anticipated so originally we wanted to come out this year now we'd like it to come out as close to human as possible unless there's some major event where it makes sense the slide in a week or two for that event and the smart contracts side was always anticipate to come out somewhere around the late 1st half early second half of 2019 so that timeframe for smart contracts is still quite reasonable in our view and there's no reason why it wouldn't be rather straightforward to roll quickly into that so there's still a lot more to do there's still a lot more testing to do but the concepts like extended UTX so hopefully this works how to integrate Plutus how to integrate side-chains how to run a side chain with the mantas Network and roll that over into production code these things are very well understood and it basically puts us in a good position to quickly move in that direction so I'm happy with that and I'm glad to see there's no slowdown there's been some other fun I some recent fun I guess some how out of the EOS community is saying something like all the Japanese who purchased ADA years ago are apparently locked and when ADA was launched on the exchanges new ADA was issued to to somehow create liquidity and that the Japanese are still locked up let me be exceedingly clear 100% of the people who bought ADA have access to it or were given access to it and can redeem and have redeemed and if you look at the Genesis block you can see the vast majority of the Genesis ada has moved in a lot of people have sold it traded still holding it but everyone has liquidity there are no special groups of people there were no tears where you know certain people got sweetheart deals or shares in a company or something like that it was sold at a very straightforward way and it's just unbelievable to me that these these lies are spreading and it just shows you the character of that community and it just shows you who these people are when they have to just say things that are not only false but provably so you can just look at the distribution of ADA in the Genesis block and see the transactions that have flown there is no group of people that's locked my ADA is locked because I chose that but there there's no one who participated in the sale who's is locked this is insane it's a bizarre statement and it's something that should not spread in when you see somebody saying it they are lying but I've come to expect that from this community they just lie repeatedly even when they're faced with overwhelming evidence that the things they say are wrong they then turn it back into you as they prove us wrong and then you show them the evidence and they just ignore it so this is just where we're at in the cryptocurrency space concepts like maybe if you say scientific claims you should have them go through peer review maybe if you claim you've implemented software in a certain way you should have some evidence that the software behaves that way that's the concept of using specification driven development considering these protocols have to be around a long time people just for some bizarre reason tend to ignore these things or say these things are irrelevant or unnecessary I don't understand why I don't really want to hazard a guess it's just when it comes up my job to say that it's not true so anyway it's been a long year we've had a lot of ups and downs and you know it's been hard in the markets it's been hard for the community as a whole I've been to 30 countries I I think more than almost 60 events and I've had a chance to meet a heck of a lot of good people and see a lot of great passion from people who have gotten tattoos with our logo on it people have planted trees for us people name their kids after us in South Korea and there's no evidence at all that the communities slowing down there's no evidence at all that we're losing momentum it's actually quite the contrary I see month by month more people join in the community more people downloading the wallet we can track those statistics and I see a lot of people extremely excited about the future and given that decentralisation and smart contracts and a lot of our good features which have been in long arc Rd are now coming out in 2019 we have a resurrected card out on foundation a merkel is starting to really get things going and our pan-african strategy is really starting to show some fruit and our enterprise framework is going to start rolling out in 2019 throughout africa which will bring lots of people into our ecosystem is kind of transitively I think that our best days are ahead of us there's still going to be a lot of hard days and there's going to be a lot of events that you know hit us from unexpected angles but we seem to be very resilient and the other thing that's really exciting is this is a self-healing ecosystem when there were issues with the foundation the first to bring these issues to the public we're not treasured insiders but it was the guardians of card on oh and third party entities and card on oh really is already very decentralized there are so many people around who keep us accountable who create podcasts who set up meetup groups who are doing interesting development work building their own explorers building their own wallets sometimes good ones sometimes not so good funds now because flute is playgrounds out and yellows out people are using these things to write interesting scripts and anticipation for the network launching and sending hundreds of emails with advice and well wishes and sometimes constructive criticism that's the sign of a healthy vibrant community and it's one that I've only seen once before not with aetherium but with Bitcoin itself so I believe very firmly that our best days are ahead of us and I believe very firmly that Cardno is definitely going to be a big big big deal in 2019 as it has already been in 2018 and at its launch in 2017 so some other housekeeping items real briefly first off aetherium classic this one has been a pretty difficult topic for me personally because you know aetherium Pat of a classic was the unintended product the unintended project there was no plan to create a theorem classic it came as a result of an event and back when I joined the community it was unclear whether the community was going to go anywhere the project was going to go anywhere it was unclear if a theorem classic was going to survive but it was mostly a protest coin we said we don't know where we're going we don't know what's going to happen but you know we feel that this this issue with the Dow hack has been handled very poorly and that many people invested in who got involved in etherium believing that code is law even languages made a legality and a lot of people cared a lot about basically preserving the original intent as they saw it of the etherium blockchain which had then be violated by this hard fork so as a consequence we felt it was absolutely necessary to give people a choice and say maybe it's the minority chain maybe it's the majority chain but you can't just go ahead and do something like this and then say well you're forced to do this there needs to be some sort of dissent and that dissent needs to be encouraged to survive and thrive and hopefully grow and become its own thing so I put my money where my mouth was opened up my wallet and spent my own money to build a client from scratch now lots happened since that event we've seen mantas grow from a concept to an actual production system that now works both with aetherium can aetherium classic and members of the etherium foundation have even reached out to us asking us to find a way to change the saw for license which we will do from MIT to Apache and try to make it a hyper ledger project so that people in the etherion ecosystem can use our code base for their products and projects and it can be under good governance we've also seen now two major summits for aetherium one was in South Korea the other was in Hong Kong and we've seen a formation of a reasonable governance group within the ecosystem so there's an open question now of well what should I which case participation be with the etherium classic and does this participation in any way compromise our ability to work on cardano's slow it down or in some way compete with the mission goal and vision of Cardinal well in a way there's been a great degree of synergy the work on a theorem classic has definitely helped us have a production system that we could very quickly repurpose to test etherium interoperability for smart contracts on our system so just by having mantis we were very easily able to be plug in the ke VM and plug in yella and run solidity code in our system it would have been much harder to do that and more expensive to run these tests had we not done what we did with the theorem classic second building that client trained our developers to understand how the theorem ecosystem worked they literally started from nothing just from the yellow paper and from the documentation and wrote a hundred percent new code and Scala so that exercise was incredibly valuable creating a knowledge transfer and bridging the skill gap so that we understood where a theorem sat and all the things that could do and all the things it couldn't do it's easy to be overly academic or to kind of throw the baby out with the bathwater it does not an entirely new model it's a lot harder to be pragmatic and learn from your competitors of where they sit and what they're doing and where they're going and we gained that benefit as a consequence of creating that client so it really did help us in a certain respect and it really did enrich our company the challenge for me is that I'm spending my own money on building this and we've never gotten a revenue source from the construction of this class to the date we haven't received any money from digital asset foundation or digital asset Holdings or whatever the heck bury a digital asset group or digital currency group I can't remember the name right now a Barry's group or etc' lab or any development grants so at the moment we've made nothing from participating in etc' and at some point as a CEO of a company I do have to make a decision of well what when and where do we stop spending money when and where do we stop contributing resources for something that doesn't contribute back one of the most difficult parts for our participation was that we predicted that there would be funding issues with aetherium we wrote several blog posts and lectured on a pretty regular basis about the need for something like a Treasury in aetherium classic making the argument that if we existed solely on a donation model that the people who didn't have the luxury of pre-existing wealth or a business model to subsidize these things would frankly be unable to long-term maintain and innovate and compete especially given people who had quite a bit of funding unfortunately e TC dev and others were very much against the funding of the Treasury some incredibly harsh statements were written in those statements were endorsed or casually accepted by people from HEA TC dev ironically TC dev apparently is shutting its doors because it hasn't been able to pay its bills as predicted so now we're left in a situation where we're not getting any value as a company for contributing to a theorem classic and we're in left in a situation where the community's been very resistant historically to attempting to create mechanisms such as a Treasury system to give us some certainty that if we participate as a company in the effort we can recoup our losses recoup our bills and continue to contribute and that we've already gained as much value as a company as we can from etherion classic at the moment there's nothing innovative in the roadmap unless we propose something and we do have many great things we have NEPA powells we have a DAC protocol called parallel change which works very well for proof of work we have considerable improvements we've made to the etherium virtual machine and all of these things could be put into a theorem classic they take time effort and money and a great degree of coordination and to me it doesn't feel like it's worth the effort to put these things in given the current structure of things so we'll talk to the existing members of the etherium classic community and see if there's some way that our continued participation can be subsidized if we can't come to that arrangement what we're going to do is retire the mantas client for a theorem classic we'll continue to support the hyper ledger version if we can get it into the hyper ledger group for aetherium support because there is commercial value in that and we'll move that team to other projects it's unfortunate it's come to this but these are the realities of the markets were in the realities of the resources that were in and also I feel that a two-year commitment off of a moral victory moral statement is enough you cannot make an unlimited infinite commitment to something you have to at some point say that there has to be something that comes back and we've delivered at the moment you could run 100 percent of the etherium classic network on mantas it is still the only client that was built from the ground up specifically for theorem classic and it was built in Scala and it was built with great engineering practices and it was built by great engineers and it was built in a very transparent way if you go to our YouTube page and you I which ka YouTube you can see the weekly stand-up meetings that we did for mantas and I think there's damn near a hundred of them and we didn't miss a single one every week we showed up and we even if there was a little progress or a lot of progress we showed it off and people could watch us go from an idea to a fully constructed client and they can see the commits in the repository is that I'm very proud of that and I think it was a great effort so moving into 2019 we'll see what we do but at the moment unless a funding source comes in for a theorem classic we're going to retire that team we learned a lot we love the community we love the people there and we think it was worth the effort worth the time that was put in but like all good things must come to an end at some point and we're gonna move in a different direction unless there's funding to stay in this current course in this direction another announcement is that the Cardinal foundation recently appointed three new members Nathan Kaiser Donna Berkey and Manmeet Singh and these members are interim members their purpose is to clean up the foundation build systems that have been lacking over the last two years startup programs like the hub program the Ambassador Program and other things and then to appoint a new board a large diverse board that represents the community so a statement will be made at a later date about the specifics of this arrangement and those members after they have a chance to dig deeper into the organization and finally see certain records and finally be able to get the foundation to be a bit more proactive and getting things handled its affairs handled will then look outward and talk to how they're going to provide value and benefit for the community but it's a great achievement it's something that took quite a bit of time and effort and negotiations and hard work and we're very happy to see that outcome so anyway those are the announcements there and in closing about all of this cardano's doing well and it's been an adult year you know 2017 was kind of the the kids here everybody was excited and happy didn't matter if he'd actually done real work or not it didn't matter if he made progress or not you could be a copy of a copy of a copy and still have a billion dollar market cap and still get funded and still be able to go to any conference and everybody thought you were great 20:18 what's happened is we've seen a lot of projects winnow out products collapse teams fall apart infighting occur funding dry up and it separated the real things from the fake things and I believe that we've passed the test and we're still here we're still going strong unlike certain competitors we're not laying people off in our company we're growing and still hiring and we're quite well-funded and our people are moving in the right direction furthermore I like to believe the approach that we've taken the peer-review approach and the specification driven development approach while horrifically expensive in the short term is paying dividends it's given us a lingua franca as an organization to speak about complicated concepts like delegation like ledger validation like smart contracts like how a wallet functions and to have this language be utilized amongst engineers business professional scientists lawyers and other entities and as a consequence of that we have organizational clarity on how these things are put together and if these things are actually going to work at scale this is not something we feel our competitors have and not something we feel our competitors fully understand and as we get into more complicated systems if we get into systems that behave with millions of users tens of millions of users that require regular upgrades I think we're really going to start seeing that Delta grow so while it's been hard I think it's been worthwhile and what's really made a most worthwhile has been the Kuran Cardno community as a whole it's been really phenomenal and exciting to see just how many people have wished us well participated with us given us helpful handy suggestions introduced us to new cool ideas and to see how quickly our vision and message has spread if there was anything to take away from 2018 is that card on o is made by you the community and as long as the community strong I honestly do believe that this will become the financial operating system of the developing world so thank you all for listening I do appreciate it and I look forward to seeing everybody in 2019 it's going to be a really good year and it's going to be a lot more fun giving an update then than it is now and I think that everything is going to be okay Cheers
