 Excellent. Go ahead and get started right away then I thought I'd be able to hear people but I guess all the conversation is going to happen in the chat. Hopefully it's not a problem with my audio here. Okay thanks Chris. Welcome everybody. Today this session is about how to set up a hyperledger indie network and it's kind of specific to hyperledger indie and very much a niche thing so I appreciate everybody is able to attend and hope I can be of some help. A lot of the session today will be covering a lot of the slides today we'll have links to places where you can get a lot more information because they didn't give me enough time to go into the detail that I had promised in the explanation or description of this session so apologies in advance but it should be all the information is in those documents so my name is Lynn Bendixon I work for Indicio they're a public benefit corporation and get to the right slide here. What we do is we help people, anyone who wants to get into the decentralized identity space and provide services and start all the way at the beginning from just consulting on standards maybe to governance and then all the way to the stuff I'm talking about today. For example last week I gave a training session on exactly what we'll be talking about today is a 12-hour training session where we actually went through, installed the nodes and built a network and we were done so it was a test network but it was everything we'll be talking about today so to begin with this is a slide that talks about the whole picture of what you need to do to create a public utility network. This is from the utility foundry working group link is at the bottom there we have some more details out on that site but we're not going to talk very much about the first couple things in here except that you'll need to do some governance. You see the two things about governance in these first couple of sections here but most of what we'll talk about is some of the create a lot of the implement and some of the maintenance that needs to happen for a network once you get to that thing going. So that is the big picture we'll be going through. We'll jump right into it here. We're in the interest of time. Feel free to put your questions in the Q&A and I'll cover those at the end. So first thing you got to do you got to find some organizations and some people it's best to get some that are committed and to start a network I recommend that you have four organizations or stewards or node operators that are the people that will be creating your Genesis nodes. You want these people to be long-term as much as possible because it's difficult to change your Genesis files once they're out in public it's not an easy thing to change those and those original nodes the four original nodes are the ones that will go into your Genesis file. So the trustees that you get they need to be people that can respond within 24 hours for example to a request to help administer your network. So you want organizations that can make sure they are able to fund the node longer term so you don't run into issues down the road. Later on you can add more right these initial node operators I don't like to have a designation that calls them Genesis stewards or anything like that. Call your initial group of people founding stewards or founding node operators if you want to but the Genesis ones are just the first ones to get in and do stuff there's not really any special designation on the network for them once the nester is all instantiated all the nodes look the same to anybody trying to get into it. The last part here though it's pretty good idea if you're doing especially a public network to be to have people from different locations or sorry organizations from different locations and to do different hosting providers if all of your people are from now using AWS for example then that's not as diversified as it should be AWS decides that they don't want to allow people to run nodes anymore and then your whole network is gone if everyone's on AWS for example. So after you've got the people together the organizations have all signed up give them the specifications you know from your governance of how you want to set up your servers there are a whole bunch of documents in this technical ongoing documents link that I put here all of these documents are open source documents that are available for you to use one of the documents inside of there for sorry three or four of the documents in there for helping to set up your server are specifically for different hosting platforms like AWS or Azure or GCP are all in there and then there's one that's not quite as detailed as those ones or if you want to set it up in your own data center so the other ones are fairly detailed step by step and take you through every step of the process of you know one by one it's not very visual none of the documents I have are very visual they're all very much word-oriented text-oriented but that's what we have right now to share with everybody and they're pretty detailed and a novice can go in and set up an Azure instance for example and if you've never used Azure using the steps if I can the once you've got the initial document set up then you'll need to use the validator preparation guide to go through and set up the indie node on the server install the software and two things I suggest on that is make it your own take the validation preparation validator preparation guide change the links and the other things in there that are the values of say this last thing there the network directory name that you've chosen since all nodes have to have the same putting that inside of your validator preparation guide is a big help for those that are copying the instruction I'm sorry copying the commands from in there into their servers part of the setup so and then the other suggestion slash I guess thing to note about the validator preparation guide is if it's set up for adding a node to a network and then off to the side there are sometimes a comment that says you don't have to do this if you're setting up a new network because now just think about it as you're walking through the guide it's obvious if you're building a new network that a pool doesn't exist yet right you don't have a network that you can connect to a pool on as an example so there are a few things like that in there just to be aware of so you don't get lost trying to do things that don't exist yet it'll be taken care of later when you build the Genesis file and speak in the Genesis file that's the next step well as you have your stewards have finished building their nodes then they have been fill out all of the information from the output of one of the commands in the spreadsheet there's an example spreadsheet it has all the items that are needed in there for you to fill out every trustee is needing to add their did and burr key and I think I forgot to mention three trustees is a good thing to have to start out with here and we'll talk about why three is a good number at least three on a different slide just a minute here but you have two different sheets in the spreadsheet and using those two different sheets you download see files from Matt and copy those to one of the nodes on your network and also get the Genesis creation script on that one node and then one node creates the Genesis files and then you copy those Genesis files to the other notes all those instruction all those things I mentioned plus other instructions there's about 10 steps or so are in this treat Genesis files instruction sheet and that has pretty good detail and that's it for Genesis files once those Genesis files are created and copied all the nodes in the right directories with the right permissions then you want to do some you want to get together with all your and Genesis stewards and have a meeting so what I usually do is get a zoom chat going where we have everyone together and then we start checking the configurations checking configurations networking everything to make sure it's all set up before you try and start the network saves a ton of debugging time in the long run a detailed check of a just a couple of config files networking in 10 minutes or so at the beginning of the meeting maybe 15 to make sure everyone's on the same page and that's the same stuff saves hours of debugging either so that's one of the big things I would recommend here just do that with a couple little checks and then once everything looks right on everybody's machine and everyone will run this system patrol start indie node and your network is up and running and once it's up and running you can run the pseudo validator info on each node to see whether everyone's connected and working together and I can share that if we have some more time at the end of the meeting in order you during the question answer time okay once it's up and running a couple of configuration steps that you'll probably want to perform the first one is the off rules that default off rules that come with the indie node are a little bit weak even for a test net so I recommend going through this off rules walk through looking at what you want your authentication rules to be up for those of you don't know off rules or what determines how many signatures each transaction needs to be put on to the network and who can write to the network etc so this is a lot of the off rules had to do with the administrative tasks so it's how many trustees are needed to add a new steward or to remove a steward or to add a node etc all those kinds of administrative tasks are or covered here and if you're running a public network with trustees from multiple companies you don't want one trustee to have enough power to bring down your home network for example so that's what the off rules help to do is set up the security and then the this other thing on a on all the public networks I've set up it's we've wanted to have a transaction off the agreement it's kind of a legal thing to help out with the covering yourself in case someone writes something bad to your network in this often author agreement is something that you can set up so that everyone when they write to the network they have to agree to that before they write to it so and then this is said or as there are a few other plugins like tokens and stuff that you can configure a few would like to at this time and like again this is after the network is up and running then you go in and on the commands to configure a few more things maintenance is a big deal so we'll cover this briefly here some of the things you'll need to do once you get your four initial eyes up and running is to add some new node operators the validator preparation guy and we talked about customizing for yourself earlier you can use that and send that to the new stewards they can use that to set up their nodes that the validator preparation guy in conjunction with some of the other documents I send about setting up the server beforehand will help and then plus a list of your specifications from your governance it's an important part as well upgrades is it says here that it's automated the next big upgrade coming up from it's going to be an upgrade from we're going to 1604 to 20.04 that one we won't be able to automate that will be a manual upgrade and it's coming soon and so you may if you're thinking about building a network soon here you may want to wait just a little bit so everyone doesn't have to do the rip and replace of their server to 20.04 but over time that once everyone's on 2004 most of the upgrades will be automated and there's a command here this can give you an idea of what happens to the automated and then the last thing here is a couple of tools the indie scan tool written by Patrick Stoss was created to help developers see what's exactly on the network and not just developers but anybody who wants to see what has been written to one of the networks there oh and these links here just to the source code for creating this I don't have links for the examples but you can send me an email I think it'd be some examples if he seems in practice movie and then Indie node monitor is a project that's been worked on to make a node monitoring a little bit easier there's a couple different people contributing to that and producing different monitoring situations that you can choose from there and then the self-serve app is one that that I wrote for sovereign so that we're getting a lot of emails asking for endorsers on our test nets the endorsers on the main net they have to pay for sovereign and for in DCO to be able to use it but endorsers on the test nets are free and we didn't want to so we made this portal here that makes it so that people can go and add it on their own so we don't have to wait for us those are just a couple tools there that help you get started and those are all open source if you need any more help the stuff there's a link to the full document of everything that talked about here created a new Indian network there's a chat channel like the ledger Indie node for most of the stuff I talked about today and ask questions there and several people are willing to respond some of the people on this call if I'm not mistaken thanks for joining us and then a little seamless plug here at the end I guess we have some training I can mentioned earlier we have a node operator training course and a few other training packages from DCO that you can take advantage of to get some more help and that is all I had time to present today I'm gonna go over to the Q&A part here and see if anyone's asking questions feel free to speak up and ask if you're able to unmute yourself and have any questions I'm not seeing any questions I'm gonna see if I can I think I mentioned earlier I might show a little bit of the results of the get validator info I'm still watching the chat in my other screen here so if you have a question do I type it in but really quickly here the results of the command pseudo validator info look like this and as you're setting up a method the first thing or a network the first thing you'll look at is this thing here where it says unreachable hosts but there's hosts that can't be seen there's either a configuration or network problem on either those hosts or yourself and make it so that that is unable to happen and what happens when you're adding a node to a network is that is that you'll communicate with the primary node and start downloading the transactions for your subletters right so and but and to see who with the primary node is that's what these long numbers are here the primary node for this network I'm showing is uphold and then these other numbers inside the parentheses are going to be the next ones if this one for some reason isn't able to communicate with it they switch it around to the next and the next right so it's ordering which will be changing those and the primary node but this just prints out from a file the validator info is inside of a file and that just prints out from that file so it wouldn't and that file is updated every minute so it doesn't do any good when this repeatedly once a minute is all the out more often that it's updated and you can get more info by doing a verbose version of that let's see says the main chat monitoring slash auditing tools we just ran out of time I can show you really quick the monitoring tool that I have I don't have an auditing tool but the monitoring tool I wrote looks like this and we're able to see the admin type information that you're interested in here there are auditing and other tools available thanks everybody for coming so I see a question in the chat from Shane if anyone's still around here is India private network I believe that the stuff I've been describing today is how to set it up as a public network so hyperledger and you can be a public network with nodes from around the world included in it you can set it up to be private and it's just how how you want to set it up but most indie networks that I've worked with are public networks okay I'm in the closest session and I get off to your next place thank you