 do communications and a little bit of web development for a company called Madesafe. So I guess, yeah, I'm coming from more of the community and storytelling side of things. So the transition to Rust for Madesafe has been really exciting and sort of scary in some points, but it makes for a really great story. So that's kind of what I'm gonna be focusing on. So if you don't know what Madesafe is, we just in brief, I mean, it's kind of a big ambitious project, but we're essentially trying to replace the need for dependence on servers with a completely decentralized peer-to-peer network of nodes, so essentially users will be able to start up a node on laptops, home computers, whatever device they want, and allocate resources to this network so that other people can upload their data and make use of this. It's in addition to the main focus, I guess, at the beginning is this concept of being able to distribute storage and do distributed communications as well, but in the end, it's a development platform. So applications will be built on top of it, on top of the stack that we're building, so we are doing a lot of outreach for third-party developers, so if you have any interest in building applications which don't depend on servers and are particularly focused on security and privacy for your users, then Madesafe and the safe network is something that you want to be looking at. So I should say that we're not quite in production yet, even though this is in production. We potentially earn that title because we have completely scrapped all of our C++ code and have decided to switch completely to REST, so maybe that just kind of deserves in production because we are committed to using it for the production. At this point, we are finalizing our rewriting of the libraries and we are releasing libraries in bundles so you can kind of keep track of what we're doing and see the libraries that we've been releasing over time and we don't really have a launch date, we're not really interested in focusing on that, we just kind of want to get tools out for developers to start using and for other people to start looking at. So initially we were, the very beginning stages of Madesafe was a lot of research and development, so using Python for that and eventually switching over to C++ for the production use that C++ had been development had been going on for several years and then REST happened and I should say that it really started out from just the founder, David Irvine, playing around with rewriting one of our, one of the safe network libraries into REST and he spent three full days without much sleep but essentially rewrote an entire library in those three days to work at a minimum capacity and that was really his trigger to realizing that it was probably a good idea to try to get more developers working on these. So he pulled a few other developers aside from the core team, actually not from the core team from kind of the front end team and requested that they build a couple of the libraries themselves and it took them a couple of weeks and through that, becoming kind of more confident in the ability for particularly the front end developers to do this, we went all in on REST and deleted all of our C++ code. So it had a lot of benefits. The biggest benefit is the reduction in code. So we had also, I guess we should say that during this time we were also going through a refactoring stage, the code base was very large before. So we went from essentially almost 500,000 developers to about 100,000 lines of C++ code to about 70,000 lines of C++ code after doing a lot of refactoring and then from there we reduced it even more so we went to about 7,000 lines of REST code by switching all of our libraries into REST. It could be a little bit more because this statistic was taken from a couple months ago but we've essentially been able to be really efficient with the code and what we're building. And I read this quote at the launch party but I think it's a really awesome quote and it kind of sums up the founder's mindset of switching and this in context was a little bit of trouble running into some frustration with building and testing with REST. So he said, we cannot short circuit, alter the system of test builds, et cetera so we need to just work harder to test really otherwise we go back to the land of spaghetti and complexity where nobody knows what's happening. We are not going back there. And so additionally to kind of just the hard numbers, the clear efficiency that this platform we're building is gaining from switching to REST. We've had a lot of kind of social improvements as well so I mentioned that he had pulled aside a couple of front end developers to experiment rewriting some of the libraries into REST and it's really true that it has empowered a lot of our front end developers. Originally we had a core team of developers that was only about five people that really understood what was happening with the C++ code and it was harder for other people to pick it up but by switching to REST there's a lot of kind of empowerment of front end developers because they were able to take on this new language and learn it just as quickly as C++. So yeah, those initially hired for application development are now core developers. That's not to say that they're not also doing application development because we're also building applications which will be running on top but they're able to kind of integrate more and everyone can kind of work on both sets of things. So original core developers are also welcoming the change. I shouldn't say it's all like unicorns and rainbows when switching over to REST. We definitely had a lot of skepticism within the team and it did actually end up that we departed ways with two contractors who were just very into C++ and they really want to keep doing that and that's fine, we need expert C++ people to be working on C++ things but it wasn't really working out with going all in on REST as we had been but most of our core developers were really excited about this. It helped them gain a lot of efficiency and here's another quote. This is from one of the core developers. I'm just taking it from our forum so this is public anyway. I still remember my first week with REST which I mean that was probably a few months ago but so good thing that he remembers it but when we first started coding the Crest Library which is one of the layers in our stack, we just had one test and I was very sure that we wouldn't be able to get any library to work on the very first attempt. However, I was very happy to be proven wrong so a lot of the libraries that we were rebuilding just worked from the start. There wasn't, there was not a lot of change needed and this just made for a very happy core development team and the fact that we only really started rewriting into REST about four months ago so David started playing around with this one library in early March, late February, early March and from there we probably, I think we decided to kind of go all in early April and since then we've been rewriting all of our code so it's just been a really fast pace and really exciting. So in addition to internal motivation we're excited about the growing interest from outside contributors so similarly with internal we also had a lot of skepticism from the community. We have a pretty large community that are interested in the technology we're building but once making that switch and committing to it over time we've had a lot of excitement from the core community especially seeing how fast we're able to iterate on building. So excitement from the community and expanding core development and understanding we don't, building this kind of secondary internet we don't want to be this core group of people that are just us knowing how it works and us maintaining it we want it to be this large global effort so we are excited about the potential and just expanding of getting other sorts of developers interested in doing core development so it's not just people that know C++. And here's a quote from another core developer this was from an interview that he was doing on a podcast that's actually about MadeSafe and what we're building. I know REST has its own podcast which is really cool but someone also started up a podcast for MadeSafe and you can kind of tell the strengthening community when someone decides to start a podcast and start talking about it and getting people on their show and talking about it. So the problem is a very good C++ programmer would be able to write code which doesn't produce any conflicts when it's running on multi-threaded systems but it requires being awake and you cannot program in the very late hours of the night. It requires a lot of mental effort and the help of REST is exactly that the computer is always there watching over you and I would add the good kind of watching over you not like the NSA kind of watching over you. So this is, I guess this is where I get really excited about this stuff is the growing and mixing of communities so like any new programming language you're obviously gonna be mixing a lot of people from different interests because they're gonna be building different tools and similarly with what MadeSafe is building we are kind of bringing together different people from different interests so people that are interested in security, decentralization, networking, free open source software I should note that our code base is GPL so if you're interested in GPL stuff then, yeah, build on MadeSafe because we kind of want to push this GPL and open source discussion forward. We think it's really important for kind of this new internet precedent that we're trying to set. Additionally with growing community we have recently announced a bounty system for the core code base so if you are either just getting into Rust or just looking for something to work on within Rust I suggest looking into the Safe Network Core code base and seeing if you can contribute we're essentially going to be putting up bounties for bugs and features and depending on this point system that we've created if you create something that gets merged then you earn income based on how much work you've put in how many points the bounty was worth so we're paying all of those bounties out in Bitcoin because that's what we have to spend. But Bitcoin is money, right? So and then we're also because we're a platform we're interested in kind of doing outreach to you for having third party developers so obviously we want anyone to be able to build an application in any sort of language that they want but we're definitely interested in kind of pushing forward the Rust community and helping that grow as much as possible as well. And generally we're very appreciative of and align with a lot of what the Rust core developers and community are doing so open meetings, open discussions, open code where we align very greatly with that and we're really appreciative of the outreach that the core developers of Rust have done with us. They've done calls with a few of the companies doing production work and kind of asking, you know, being in tune with what we're building and seeing how they can help us and we can help them. So I think it's a very just open and motivating feature of like, having the way of kind of doing open development and collaborating with different communities. So just to end it, I think I'm a little over, sorry about that. So these are kind of links that you want to take note of if you're interested, our GitHub, all of our code is open, GPL. We have our kind of issue tracker at Listen. We have our crates, so you can just search crates.io for MadeSafe and see our crates on there. Communities at forum.safenetwork.io and then the company website is madesafe.net. So if you're interested in any of this, I don't have time for questions now but feel free to talk to me. Thanks.