 We're kind of a diverse team people from you know all around and I speak for mist itself and that and the ethereum community as a whole So let's you know move with the web3 ecosystem and let's talk a little bit about The current landscape of it. So we've got mist which is a concept browser. I can tell you more about this later, of course We've got the amazing metamask, which is a It's not only an extension. They are much more than that more they they'll talk more about Some other new projects on the second the same room We also have a brave browser that joined this ecosystem You know two years ago Opera which recently launched the beta which has web3 access You know opera is still the fifth major browser worldwide and this is actually pretty big so We have wallet and some mobile Experience as well mobile trust browser cypher status, of course coin base And the list is growing. Can I have this? Alright, maybe that's too far. Oh, yeah So let's talk about miss history and updates. Actually, actually, this is our fifth Davcon we've heard Here since the start Alex, which is there he presented the vision and Alex presented the vision and then Inspired lots of developers All around the community to build other things on it and around it We got oh Yeah, so that's Gavin and Alex, you know several years ago That's on zero and then they've gone one Can we have it? Oh, yeah, they've gone one and then while miss was a Better, you know structured concept we got, you know, lots of wireframes and all and then came the theme wallet. Oh Yeah, they've gone two three that's me and for so I like to, you know, make a little bit of Advertising here. There are some interesting talks from our Former and current team members. So there's universal logins by Alex later today this room introducing formality by Victor Maya browser web 3.0 how to be secure web 3 clients. That's actually a missed thing and Here's our current team we got Philip myself Mark Alex and Ryan we managed to grow the team actually we were you know some dark You know times where we had you know two developers now. We're thanks to the theorem foundation. We've got plenty of them Let's talk about things that we've done this year. So there comes a time where a user Executes a transaction. So that's actually One thing that should be really carefully thought about so We put lots of thought into that Because executing transactions is actually the biggest Emotional pick in the user experience Picture that you're you know transferring 100,000 ether Well, I'm pretty sure that your hands will be sweaty You know you're deploying a multi-seg wallet that can be dangerous sometimes So in order to in order to design and oh thank you guys in order to design a pretty and useful and Transaction we know we had to you know the user has to know At a glance what's happening. It has to be a well crafted interface with pretty clear instructions This is not it This is how it used to be But we were pretty You know by the time we did that we were pretty happy with that but now we are changing this Just something you know more clear more, you know straightforward But it doesn't end that of course you can transfer, you know tokens you can execute functions And we are you know going a bit further than that well the user types of password execute transaction Then we can have you know this kind of Description thanks to an aspect or ad spec also, you know, thanks to ENS we can have these kind of More description descriptive information about addresses So yeah, this is our new transaction window we gather and mix Lots of information together. So we've got gas estimation price sequence feet functional ABI signatures That's back and in yet you know as look up for address look up Well thinking that's a major issue Back back in time back then we one could Sync the blockchain in a matter of minutes So we know how it is the state of its of this nowadays And we used to have these loading screen It was actually needed because otherwise all the depth that subscribe it to block new blocks that would be bombarded by You know events from from the node So in order to cope with that and to meet user expectations we could have you know Make the best load the screen in the world But I'm pretty sure that no one would stare at it for you know more than five minutes so we had to be creative and we devised a mechanism to to have two sinking mechanisms one with a remote node as you can see in food over there and A background sync using go Ethereum like client or fast sync and when This node was up to date it would take over the connection as a main one so ideally the user will wait a little time to See in an interact with the blockchain When the node takes over you'll be you know in a totally secure environment Totally centralized fashion. Oh, yeah Hi Peter That's the responsible for the like line and to go with you So we've got this which we call layer nodes instantly connected to the blockchain via remote provider Like line sinking in the background and well when it up to date it just takes over the connection We implemented a transaction history window Which will gather all transactions made In the browser Which is pretty convenient for depth developers because they wouldn't have to implement that themselves within the their websites using our web 3 1.0 with web sockets implemented and There are some breaking changes to how we connect with the websites. Actually, this is Coordinated effort so misuse it to inject web 3js within the DOM So we don't do that anymore. That's up to the dev developers to to choose which versions they will use And then we would only provide the web 3.0 current provider This is now changing to window dot ethereum only for simplicity sake. So here we can have The method that will request accounts and then in mist This window will pop up Which we can you can you know have Or create a new account or select one or multiple accounts you want to provide to the to the website Yeah, so in order to implement the change will be simple. You have to instantiate to make web 3 with this kind of connection pretty simple change and This is a convenient way to access blockchain resources. This is actually a Collaboration effort metamask and lots of other players are on this same boat You guys can point your devices to this QR code to see more, you know in depth Documentation we are about to roll out in the next weeks and well, of course, there's a PR for that We're also making some deep architecture changes This This is how miss looks at the moment. Okay, we've got a browser shell Which we use electron we've got the back end made in Node.js and the front end Meteor Those are all tightly coupled that makes quite difficult for us to to experiment new technologies to you know Especially when there are you know some security concerns, which in our industry is fairly common So we're changing to this kind of model so we have Totally isolated a breath really thin browser shell still using electron at this moment but the main process would be separated and the front end would be in react and That will allow us to make such changes We can have lots of updates Frequent ones just like continuous delivery mechanisms in the web development So you can have you know lots of updates the user will can subscribe to those kind of updates and of course With the user consent we will It will be as simple as a browser reload, but you're using a desktop application Then we can update only the main process and eventually when we've got new browser shell versions You'll update only that again But hey, why are you still using electron if you're building a browser? That is so true. We agree with that And this is a tweet from young from brave browser. They just got rid of electron all together And we're playing to do so as well, but We came, you know with a different solution We'll be using chromium embedded framework in a project called how Which I highly recommend you guys to watch a Philip talk would be on day Which day and time you guys hear that tomorrow at two I Think we'll be here in that same room, right? Okay, so regarding these deep architecture changes. I think In practice what can bring us to Instead of a 80 megabyte update at least you'd be like, you know less than five megabyte updates for the UI You know, that's less than a wide image And you can do that, you know frequently we can put our continuous delivery server to to work for you So increase it cross OS testing effort today is actually a pain for us So we can get rid of this all together making those frequent releases for the interface and Today we put the security burden of validating the checksums To the users. I think that is not really fair because you know, sometimes it requires some tooling additional tooling, you know Command line instructions and we can make it better with automatic checksum validation at module level a bit more about Transparency we got some feedback saying that well our roadmap wasn't quite public People sometimes wouldn't know exactly what we were working on. So Yeah, we now have medium publications. We've got just one public post there, but we've got three more You know just about to be public. So if you guys can follow us there, you'll see our roadmap would moved from Closet application to GitHub projects and Well, today I created you see your message on Twitter. So, you know Good that it was available. So he has it has zero followers, but you can Can be the first No formal guys So how to contribute to this project and to this web ecosystem Well, we have Such an amazing community where we can see from from protocol design Studies research and how they interact with each other merely using I guess if the research website and some forums and chats But here about the web protocols and changes in discussions We mainly use the easy theory magicians.org website and the EIPs, which you're probably familiar with already Also, we have well Poor requests are pretty welcome. We can guide you in your own adventure and I have you know This is something that Should be, you know exposed A tweet from AFRI Oh, yeah Yeah, that's it. If we don't stop relying on put any Centralized service not just in for it because we love him for that, but you know, that's I think that's too much on their shoulders Division of Ethereum failed just like we're defeating the purpose So I think we should you know, give more attention and and to those new projects like line incentivization Incubed that node VIP node denote There's metamask project which I can't pronounce babies was tecala, baby Well, of course universal logins and meta transactions, which you know can remove the burden off of the user interfaces All together So remember guys these things for distance relies So that that's you know for your own website where you you know about is about to To publish it is about to which kind of services you connect to This is exactly what we're here for You know So, you know just a bit a bit more about our features Mist really wants you to have any real with your node in your computer Even if it's a like client or ultra like client in a possible feature Use of swarm communication layer in and yes, we can read ENS content hosted on swarm So That's pretty much it guys. So the Web3 progress is so exciting and this is so proud to be part of it So, thank you so much