 I don't know if people know Aragon and have used it before, so I thought I'd do a live demo of what it looks like today. So in the next 20 minutes, we're going to claim your DO name on Aragon mainnet. You can actually do this yourself, you can follow and just pick your own name if you want. I'm going to do one for something called Loricit, which is something I'm going to give you guys a sneak peek about. This is, I guess, like a component toolkit and a design system that we've been working on for Aragon specifically, but we are open sourcing it more broadly and want other people to be able to use it as well. So really briefly, I just wanted to introduce myself and my collaborator and friend, Pierre. So my name is Jonu, and we've been working on a couple of different open source projects over the last few years. So we've worked on Ubuntu, Ubuntu Phone Mobile for about four years, and then recent redesign for Riot Matrix, and most recently, I guess, last year, so we've been working very hard on Aragon, trying to make organizations on blockchain be very easy to use. So yeah, let's get into it. Let's claim your DO name. So if you want to try and follow it, you can do this yourself. It takes about two minutes. You'll get to issue your own token. You get to claim your name, so it's pretty cool. Let's go to the website. So for those of you who haven't seen or heard from Aragon before, Aragon is kind of a platform for a DAO, so it's very, very, very extensible, very broad. You can do a lot of things with it, but in this instance, I'm going to create a DO for managing Loricat, which is the design system. So in the future, we might want to be able to vote on different choices that the participants in the open source project want to go ahead with, so I think a DAO would be a great setup for that. So I'm going to do this on Mainnet, because we are live on Mainnet as of this week, after quite a lot of hard work, and I'm going to create a new organization. So you can open existing ones. If you're just trying this out, maybe try the demo first to see how the app looks like, but I'm going to create a new one. So we'll create a new org, and for this one, we want to have a democracy token project. We have a lot of people, potentially, on this project who want to decide on things, and we're going to call it Loricat, which is great. Nobody has squatted it. Next. I'm going to just kind of breeze through. This is kind of the settings for your voting that I'll just use the defaults for now, but you can change this, and I'll call it, so when you're creating a DAO with Oregon today, you also get a token, ERC20 token, so I'm going to create what could we call it, let's call it Loricoin, and give it a ticker. And then, yeah, you just confirm the transactions and get a cup of coffee, I guess, and then you've got your DAO ready. So to save some time, I'm just going to jump into a demo org to show you guys what happens next, what you get when you finish with the transactions, and it looks like something like this. So this is basically the Oregon main UI. So what you've got here on the left is a list of apps you have in your organization. So by default, you get apps like token managers, manager tokens to add people to your organization voting. You can vote in various things. You can just do random votes on anything you want, or you can do voting relating to finance if you want to make any kind of transactions from your DAO to have to pass through voting first before they accept it, then that's a good use case. Actually, I'll show you really quickly how this works. So in this demo DAO, we have two token holders. You can just add more people by just adding their, adding their Ethereum address, and hopefully NS name pretty soon. Big funds of the NS. Voting looks like this, so, yeah, you'll see what the current votes are, what's been rejected, what's been approved. You can view the details of that vote. If there's an open vote, I don't think there's any on this demo DAO that you can, you can vote on it if you hold tokens in the organization. In the finance app, you hold different tokens on your organization, so you can do various things with it. You can pay for things, you know, normal stuff, but all this stuff can be linked to the voting app. So whenever you want to make decisions, you can make sure that token holders approve those first. So, yeah, make a new transfer, so I can make a deposit. So if I wanted to deposit some Ether into this org, I could just do it through here. I can also send Ether directly, but for different tokens, it's better to do it through the app. And you can, if you want to withdraw, let's say I wanted to pay for, I don't know, two lights to ZUG, I just put in the, maybe there's an airline that accepts Ether, I just put the contract address here and then click this. And depending how you got your permission set up, it either goes through a vote or if your account has the permissions to do these things directly, then you can also do that. We have an app store that's coming up, which is going to be really cool, so people can create their own Aragon apps. These are just some examples for now, but hoping to have a lot of, and it's really quick to create this app as well, so hoping to have a lot more in the future. So yeah, that's kind of a sneak peek of Aragon 0.6, Alba. And yeah, try it out, it's very quick to use, very easy on Mainnet, so you can do real things now, which is cool. So the next thing I wanted to show you guys, wrong presentation, is Lurikid. So Lurikid is something we've been thinking about for a long time, I guess this started off as just kind of an extension of, we built something for ourselves, we thought it would be really cool if we could just expand this thing to something that anybody can go with, people can contribute it, and basically it will just enable you to create production ready, beautiful apps much quicker, because you have these good baseline components. And really you can use these for throwaway prototypes if you want, but these are, we're using all the components on Aragon itself, so these are production ready, so it's not really something that you have to worry about, like, is it just good for a prototype and have to redo the whole thing once I go to production, you can actually use these in production, we do. We've been working on these components for probably about a year now, quite a lot of pull requests, mostly thanks to PR over there, and we have 11 contributors now, but we're really hoping to get more people building stuff on top of this, and just kind of benefiting from the work we've already done, and being part of the community. So this is a sneak peek, there is a website coming pretty soon, but just to give you more of an idea of what you're hoping to achieve with this. So first and foremost, and I guess this is where we are kind of right now on the project, is we have a very modular component library of React components, we also have some specific UX patterns and components to decentralize web, a lot of these components are pretty generic like you'd imagine with a kind of React UI toolkit to find like buttons and cards and so on, but we also have some specific components to blockchain, which I'm going to show you guys a few of those in a minute. These components are pretty performant, so we've done a lot of optimization for this, so especially on mobile you'll see the difference, this should really feel like native components. And then animations is one thing that doesn't get used by a lot of projects, because maybe it's a bit daunting or people don't really know what library to use or what to do, so we're hoping to help with that as well. We have some preset motion design done here, and we're going to have a lot more kind of user guidance on that. It's easily extendable, so you can build your own, like if you don't find the component you need, you can just build your own and add it to and hopefully submit a pull request for us to set it in. And we've tried to go for a kind of a clean UI design, which you can use for your nap without every app looking like arrogant, basically. You can also theme these things pretty easily, so if you want to do something that looks very different, that's totally doable as well. And yeah, I want to highlight the fact that we really want to do this as a community efforts, because yeah, the whole ecosystem will benefit if we have good kind of baseline components, and we're hoping you're going to build your own, and it's not just for developers, really. I'd love to see more designers getting involved, so we're actually going to submit a bunch of bounties, both for Dev and design pretty soon, so if there's any designers in the room as well who want to find this interesting and want to find them more and maybe work with us on this bundle, come and talk to me after the talk, and I'll add you guys to the bundle list and product people as well, anybody basically who's interested in working on good experiences. So a couple more things about the React component specifics. So I think I've gone through most of these already, but just to reiterate, these used-styled components, which is we're styling a theme in React components, and they're very themeable, so you can really go to town on changing the look, if you like. We're targeting 60 frames per second native feel and performance, so really want to optimize how well the stuff performs. We have the documentation section coming on the website, so you'll see API docs to basically all these components. You'll also have guidance on principles for designing for decentralized systems, dealing with latency, if I'm using all that kind of stuff. I'm going to show you a quick sneak peek of the Dev docs. We've got it on ua.argon.org for now, but it will be very soon moved to the lower-key site, so just wanted to give you a quick look into what the documentation looks like. So you've got code examples here, how you use it. You have, like, always when you have a code example, we'll have the rendered React component, so you can mess around with it, just see how it performs. You can scale it, you can see how most of these components, I think actually all of them are responsive now, so I'll show you in a little bit and demo on mobile, but yeah, you can just see how everything works. So yeah, we're really hoping to make this documentation really thorough, so people can really easily start using this, and yeah, you'll see you can pick, like, oh, I like this control, this I use it, and just go straight away. So yeah, you'll see that there's a bunch of the basic controls I already built, we'll probably need some more, so hands up on this, and if you have your own ideas, yeah, please go in touch with, go to GitHub, do a pull request if you build anything, or just file an issue, we'll start from there. Cool. So I want to talk a little bit more about mobile. I think mobile is super important, like I was really curious to find, like Beltran mentioned in the talk yesterday, that everyone kind of knows in the back of their mind that, yeah, actually, most of our users probably are using mobile as well, but maybe haven't built for it yet, so I think this is nice for you guys as well. If you use the lower kit, you get mobile straight out of the box, because these components are responsive and really well optimized for more performance. I'll just show a quick demo of what that looks like. So this is our voting app, and you can see the desktop version, where you have each vote as a card, and we just stack them, and you'll see how it just, yeah, we spend a lot of time trying to think what's the best use experience for mobile as well, going from a widescreen to a smaller screen, just making sure that you can use all of this stuff for mobile too. And I think mobile is going to be really important for blockchain in general. I think we need better mobile voice and et cetera, but I think we're trying to do our part, so focusing on the components, making sure that they're really usable and mobile too, and layouts. So I want to talk a little bit about design guidelines and what we're hoping to achieve here. So actually, yeah, we're hoping to, we saw the talk yesterday, which was really great. We're hoping to collaborate with more projects that are working on this type of guidelines to just have a better documentation of what best practices are for designing, designing in general, and then also designing for Ethereum or decentralized systems. So we'll have things like do's and don'ts on the website of what you should do, what you shouldn't do. I think material design guidelines are amazing. So I think to have something like that, but more focused towards decentralized use cases. And yeah, obviously, templates and tools as well, I think is super important for designers who are jumping into the space to be able to go in and download source files for these things and start messing around. And I think it just opens up so much more for contribution. So we have components built in designer sketch right now, but we have started putting some of these over to Figma and Frameworks for interactive versions of these. So this is one area we'd be super keen on any designers in the crowd who are watching this, if you'd like to kind of get involved in putting this stuff over to Figma or Frameworks, get in touch. So yeah, a couple of examples of the more blockchain specific components. One big thing, obviously, is dealing with latency because the transactions take a very long time to mine right now. Even, I think, a year or two from now, they still take a while to mine. So we need to somehow make sure that users are aware of what's going on. They can anticipate how long it's going to take so they can do something else in the meanwhile, or they're not blocked on just waiting for things or wondering what just happened and where did this thing go. I'll just show you a quick example. This is our finance app. So just skipping through a couple of bits of signing it with me, Damascus stuff. But when you submit the transfer, for instance, we think it'd be really nice to just show kind of an optimistic US state straight away of, OK, we know it's not signed yet, but we still want to show you where you are right now. So kind of show a pending state of, right, your transactions in mind right now. You can roughly see how long it'll take. We'll get from the gas price you sent. We'll be able to estimate a rough time. You can, we'll just save you time. Like, you don't have to try and scramble around for the contract rate, so you can just see it straightly in the scanner as well, if you like. And then once it's mined, and we'll just add it to the page, and yeah, it'll just update straight away. So trying to keep users in the dark and just keep them informed of progress all the time so that they don't have to kind of switch around different apps, wonder what just happened and where we are, basically. And similarly to that, we just think there's a lot of things we could do for helping users feel more secure and more informed. So for instance, things like toasts that we could use for quick confirmations and notifications for more on-chain activity. So I'll show you an example of the toast component that we're just building right now. When you have quick interactions, you usually want to confirm to the user that, OK, what you just did has actually something's happened with it. So this is probably more, we could use this for on-chain stuff as well, but I think anything where you just need quick confirmation of, OK, we got it. Then we have something, I'll show you a quick video of our transactions or notifications panel. So all the on-chain activity would go to kind of a place where you can always see, this is stuff I've been interacting with on-chain. I can see in one place, it'll notify me if the states of the transaction changes when they get mined, when they fail. So we have different states for failure, for instance. So it's very clear that you can always go to one place and just see what's been going on with your on-chain transactions. Another thing we've been working on, I haven't done too much work on it, but I think it's worth plugging. I think it's really cool. It's more a developer thing, but human-readable transactions. So right now, I'll show you what that looks like. You're probably familiar with this kind of scenario where you have your MetaMask message, and it just doesn't make sense. So we proposed this new thing called RUDspec, where you can basically make the transactions human-readable. And we're working with MetaMask right now, I think, to get this implemented there. So right now this works in Oregon, where you can basically tell the users where they are with. So what the actions they are going to do are going to do in plain English. I think this is really going to help. Another thing for decentralized components is Ethereum addresses, the kind of these really long, ugly strings right now. So we built this address-budget component where you have a clickable thing where we can show the whole address, we can show a small version of it, especially mobile. You'll see the identifier, the blocky, and then you'll just be able to click on it and copy this directly, which is a very common use case. We just thought we'd save you a couple of clicks there, see on the other side. Same with ENS names and so on. So yeah, another kind of blockchain-specific component. Motion. We use this library called React Spring a lot. So I'm running out of time, but basically, motion, I think, is a really important thing of the user experience. People don't use enough, so we're hoping to help you with this. It should be quick and should be used for helping you focus tensions on things, not just for flash. But yeah, I've got a quick video of what this could look like, for instance. For transitions, I think it really helps to show the user where things are coming from, where you should focus on your gaze and so on. Yeah, I think we're almost getting to the end. So when can I use this? We're hoping for an early Christmas. So late November-ish, I think, depending on how busy it is. But yeah, it's nearly done. Most of the components are ready to go. We just need to work a bit more on the website. And we're good. So yeah, last plug. If you're interested in Aragon or governance on the blockchain, you should come to Berlin in January. We have this amazing conference there called Aragon. You can go to aragon.one to find out more. And that's it. Thank you very much.