Good News
Full Transcript
hi everybody I just wanted to go live here for just a little bit to talk about some things that have come up the news of the hour is that one of our partners amber go earlier this more they went ahead and pushed an update to your ROI and that update for the first time ever gives Cardinal support for our Hardware walk treasure wallet it's pretty cool and what's really exciting to me and why I think this is such mummy mental news and why I'm making a big deal out of it is this is the first time in the history of the Chordata project where something of this magnitude has been done without any effort coordination or input from IO HK the treasurer integration that emerge o is done is 100% them it's a hundred percent their efforts and they've done a real great job with it and they'll make an announcement shortly soon I suspect today or early tomorrow and they have some videos and other cool things but from our perspective on the average-case side this is a major milestone because it's a resilient smile stop it's basically saying that third-party developers are building things in our ecosystem and they're just going ahead and doing it they're not asking permission they're not asking for input they're just working real hard to get these types of things done the other thing that's exciting is that ledger support is the number one request to feature we get from everybody in the forum's and treasure support legislature treasure came a little sooner because there was some great work that was done there by banking labs and others but Ledger's not too far behind so given that we have support their support on Ledger's should probably come in the next month or two at the latest on the ROI side now on our side on the cardio side 2018 was all about learning about how to rule out a crypto currency for the exchanges for the users how to build a help desk how to do a QA process and what does it mean to actually have a crypto currency wallet in production and people barking and yelling at you every day about various things that they'd like or things that aren't working well now as we move into 2019 we an organization have gained an enormous amount of knowledge and experience and capability and we're going to start rolling that knowledge expertise and capability into our product portfolio so in particular in the next few quarters you're going to see card on a wallet the reference wallet up the system transform quite a bit first we'd like to have two implementations of card on a wallets back at so we right now have a rest implementation because excuse me a Haskell implementation but we're also going to be rolling out of rust implementation and then the user can choose which code base that they want to use for the back hat second we're going to really double down on this whole concept of having an advanced user mode with a card on a wallet so we're going to have a terminal and that terminals don't allow you to do things like manually construct a transaction manually do you TXO selection run scripts that you can write kind of a shell script within the wallet to automate a lot of wallet tasks as well as to directly interface with things the database and directly interface with the wallet itself and eventually that terminal will be used to deploy smart contracts as well so for the users of our test net if you've used mallet to deploy smart contracts the KVM in ante yella a lot of those concepts and ideas that we have there will be taken and put into card on wallet or flutists as well as eventually the side chain connections that we have for yella and for the cave yeah so it's going to be an advanced user mode it's a high priority and now that we have a new wallet back-end it's something that we're going to be building our way towards a very systematic effort and there's a whole dedicated team another thing is that our wallet back end is getting decoupled so we've actually built it so that it's going to be in its own repo and it's going to be a standalone product and that conceivably means that you can take that Haskell wallet back in and connect it to a different core our first experiment with that is going to be with the rust Cardinal client so we'll take the new wallet layer well connect it to the rest client and it should be able to connect to the Haskell client the Russ client but if ultimately other people can take that back-end and they can use it for other products and because it's been built in a very particular way it may be abstracted to a point where you can use it for any you TXO wallet if you certain parameterization meaning that you could conceivably in the long arc use this as a Bitcoin wallet system or a light coin wallet system in addition to being useful for Cardno and so forth we're also going to start putting a lot of resources into improving Haskell's portability right now haskell works great for certain infrastructure if you're in the linux world huzzah but if you're in the windows world or the mac world things are a little harder if you live in the browser things are non-existent there's things like GA CJ s but unfortunately it's not really good experience compared to things like reason ml or close your scrip so given that Plutus is embedded within haskell if we're going to have a good experience with people deploying Plutus scripts and running those using template haskell on the client side in addition to the blockchain on the server we need to have a way of getting us into a browser and there's two routes we can take we can either go down the web assembly road and get a Haskell to web assembly compiler ready to go and make that a good experience similar to how we can do that with rust or we can put more money and get GA CGAs to reach equivalency with things like reason ml or other platforms that do that so we're having a big internal discussion with our team we're going to conduct a series of experiments one of our partners tweak already has been doing pretty heavy lifting with web assembly and we think within four to six months if it's given some tender love and Kari can reach parity with what it needs to to be able to compile our Haskell code to run in the browser now what does this mean for smart contracts and what does this need for card no it means all the Haskell code that we've written could conceivably be ported into a browser application similar to what we've done with Icarus with rust and JavaScript it also means that when you write a flu two styles of our contract your development tools your build environment and even the DAP deployment environment could conceivably be 100% inside the browser or within Daedalus because Daedalus is built on top of electron so that's a high priority in addition to getting the terminal where it needs to go thanks so much so we're going to be hiring three full-time engineers to do nothing but work on either GHC j/s or on web assembling we're having an internal debate of the most efficient allocation resources there the good news is those projects are within half a year worth of effort and so they should conclude right around the same time we start upgrading our system to include smart contracts another thing that was put on the back burner last year because we decided to completely rewrite core and completely rewrite the wallet back end is multi-sig and multi-sig is making a comeback our partners keep requesting it and we keep saying there's no good reason not to pursue it so we already have one pull request that was from I think April to May of last year where there was a pretty good design for multi-sig but we chose not to pursue it because we were in the process of rebuilding everything now that major components have been reconstructed we're going to go ahead and restart the multi-sig project so right after we start seeing led your support and treasurer supports already now here with a Roy very short thereafter we should have a standard for multi-sig and we're going to work with a mergo to make sure that that gets implemented properly they have some more announcements that they're going to make about their roadmap for 2019 I've seen it it's great roadmap there's some really impressive cool things the other nice part about you Roy is the development team keeps growing we're going to start making contributions to it we were trying to figure out whether it made sense to keep maintaining the icarus codebase or to retire that and move our contributions to you Roy but we're so impressed with what Sebastien and Nico and Mirko have been doing that IO HK is going to start making code commits to you Roy so we can hopefully double the size of that development team and we can very rapidly get wallet features out but not just multi sitting and hardware support these are fun but also features a delegation center from your oiseau you can stake your coins right within the browser and other such things so that's going to be a nice open road map and that's going to be exciting certainly the good news it's not super significant but it is a major milestone to repeat is the launch of treasure support with Roy and what's so exciting about it to me again is this concept that it was done a percent without i which k engineers iowa which can input it was just done by our partner the other thing is it's getting considerably easier day by day week by week for third parties to start integrating Cardno support so as we move out of q1 o as we move through it will expect to see lakhs of third parties like shape-shift and jacks and others start picking up card on o and supporting card on oh because the implementation kind and effort for that is quite quite low compared to what it was in 2018 as for me one final thing we're going to set up a workshop internally to discuss like clients for Daedalus and one of the things we'd like to move the car Donald Wallet platform to is to start instead of as a full note to start as a light note so basically what would happen is that we download a small amount of data get the UT EXO and then you would instantly be able to use Daedalus as opposed to having to wait for devil is to download the entire blockchain there are some discussions about given how we transmit our blockchain given how our network stack works and given how warhorse works what's the most optimal way of doing a light client but this is not an insurmountable challenge and the advantage would be that when you download that you just click it it boots up very quickly kind of like how you really boots up quickly and then in the background if it's left on and will gradually upgrade itself to a full node but it should not stop you from using the wallet there's been a lot of other requests accounting requests whitelisting requests for addresses and we've received them and hurt them and the big bottleneck for new features was just getting the new wallet back-end done it made no sense to try to build new wallet features on top of the old back-end it was like building extensions to your home while the foundations built on quicksand made no sense but now we're on a solid granite base we're working our way through getting everybody I've created to that solid base it's pretty challenging for some but we're moving through it and there's going to be a bunch of little utilities that we probably will end up deploying as well especially once we have a terminal things a blockchain integrity checker so you can run a script can check the blockchain make sure that your database is not corrupt you teak so Defragmenter so if you have some fragmentation or you need to consolidate down so you don't have all these dust inputs there are ways to do that and their scripts you can run to do that we give them to exchanges it'd be nice to see that in Daedalus but basically these types of things are coming we have a dedicated team just for this it's the wallet back-end team is led by Matthias he's a nice French guy I and now that they're decoupled they're in their own github repo there and have their own route roadmap their own deadline and it's a very well-trained team that's very smart team so features should come rolling out we also have competition now you're always looking great these guys are moving super fast and they're just doing wonderful work code quality is quite high and we expect to see them making phenomenal progress as well so anyway good news is hardware supporters come that's treszura Mirko will make an announcement they have lots of cool stuff to get people excited about it and they have some other things that are coming down the pipe very soon that are super exciting but I can't spill the beans yet on those I and all of that's happening without direct I which K input so we're real proud to see how well that they've come together and how quickly they're moving and their commitment to open source and their commitment to building a great great wallet ecosystem and on our end we're gonna try to ride with them so multiple backends rest back in the haskell back and terminals coming multi-sig is coming we shouldn't be too far behind on hardware wallet support there's just some things we have to do to get that to happen and takes a little bit of time for that and it's a little bit easier for the guys over at Margo to do that because they're on the bit for you for compliant Icarus style addresses and we're migrating our way to that so we have to do that first card on a 1.5 should be dropping soon it's going to be a singular update it's a movement from the old or forest or horse BFT it's going to come out nothing's going to change it'll just download it they'll say hey great minor update but actually buried within it is a fork and we just flip a switch and it changes consensus from the old model to the new model and we'll probably fork some around March for that so we'll give people a nice window of time to ensure that the upgrade in particular for infrastructure providers so people who run backends I the wallet backends and we see with your ROI or people who run exchange notes DSL notes so we'll have a nice window of time to build upgrade there and also make sure they're interoperable with the new v1 API is so gonna be a busy year guys and thank you so much for all the patients and if you're having trouble upgrading to 1.4 do file a bug report take to the forums talk to the technical support people there also is a telegram technical support Channel speaking of telegram I mentioned this on Twitter recently and I'd like to mention it again there are two major Twitter excuse me telegram channels one channel is Cardinal General and the other is channel called Cardinal community now there's a legacy here what happened was Cardinal community was created first Cardinal foundation have not invested any money at all or effort community management they just simply didn't care under Michael Parsons and what ended up happening is that channel was basically led by a group of people who have become bad actors and if you join the channel instantly you're told Cardinal is a scam it's a horrible product we're all bad human beings any news that comes out is obviously a lie or bad news it's just not a good place for people to count and I would posit that a large chunk of the people there are not even real accounts but anyway it's a legacy channel and no one should join it in fact the people who run it tried to sell it to us and when we refused to buy it from them they decided to just continuously attack us and say we're horrible human beings so if you want good moderated Cardinal news and just communication in a channel I happen to be in myself Cardinal general is the correct channel which is around five thousand five hundred or something like that people so my hope is we can retire the Cardinal community and over time scale up the Cardinal general channel and there's moderators there and there's dedicated technical support channels as well if you're having some issues but anyway for one point or just bear with us and get through it if you're having trouble upgrading it could be that you have a corrupted block database easiest way of resolving that is to delete the old database and to download a new one takes more time to do it but if you're not able to migrate that's probably the most likely cause but do file a helpdesk report and once everybody's on that foundation and we're on to 1.
Found an error in the transcript?
Help improve this transcript by reporting an error.