 Thanks for joining today. My name is Renata. I am one of the key maintainers of Hyperledger Indie for the fourth year now. I'm glad to work on Indie and today I will tell you why. Hyperledger Indie is a digital identity project that represents a whole ecosystem of products ranging from a distributed blockchain ledger to a client libraries for issuing verifiable credentials. The main idea of this system is a public permission blockchain network that allows you to identify people without sharing too much personal data. The system allows credentials to be issued to an identity holder and then the holder can provide a proof of those credentials to a verifier. The verifier can then trust the holder so I see that you can hear me. It's wonderful that I can continue. So this slide explains some things that distinguish Indie from other distributed ledgers. Custom privacy is Indie's top priority. It's possible because the ledger doesn't store private user data instead it is stored by the holder. To be consensus, Indie nodes use the RBFT protocol which allows quick detection of performance degradation at the primary node. The primary node can then be changed keeping the system efficient. Each requester for getting a transaction contains a state proof which significantly speeds up read operations but allowing us to trust the response from only one node. In addition to the identity transactions most of the network configuration operations are also saved in the ledger. Those we can change some parameters of the network through consensus of all nodes. And the history of these changes is public and easily tricky. We develop the system using test driving development so the code is well covered with tests more than 5000 units and integration tests more than 10,000 parameterized tests and system tests which are equivalent to testing a real distributed pool. So the following slide shows how credentials work. Holders own their permission personal data and they can present to their verify. And there. Thanks to Indie's use of zero knowledge proofs only a part of the personal data can be provided for verification. At the same time, Verifier will not be able to use the information to impersonate the holder. The Indie ledger can communicate with agents that speak the areas protocol application which are compatible with this protocol can connect and exchange credentials with each other. Agents connect to the ledger to verify keys but it's not common to write to the ledger. Those agent communication is only limited by the speed of the network through operations which happens really quickly thanks to the use of state proofs. The network is a set of nodes that contains the sorry site of Indie. Indie node is responsible this part. Indie node is responsible for the business logic like the definition of identity transactions. Plenum includes the consensus protocol and local data storage that ensure safe reboot of the nodes even in emergency situation. Let's take a closer look at the products that provide the work of this business logic. Ursa is responsible for cryptography, nodes and client libraries use it to work with BLS signatures, elliptic curve encryption and other operations. Plenum and nodes are services that run on the site of the validators. There are two products currently on the client side. Indie SDK which includes a Rust library for ledger communication, interfaces in fact for adding a payment system and wrappers in different languages for using the library on the any platform. RS provides an alternative approach with the Indie VDR verifiable data registry to connect to one or more Indie node ledger pools. RS SQL provides secure storage and cryptography support and Charlotte Rust libraries V6 provides a high-level credential exchange protocol and frameworks for simplifying the creation of agent application. There are a variety of agents built on the Indie SDK or the RS libraries which allow the end users to have a convenient and understandable way to work with the whole infrastructure. So let's take a look at a set of key features. These key features make this project unique from my point of view. The authorable transaction dynamically determines the permission for recording transactions and other activities. Rules can require multi signatures. Authorals allow changes in network configuration without rebooting the nodes and all changes are tracked of course. In addition, plugins can be added to Indie nodes expanding the standard functionality. The audit ledger keeps rack of records of each transaction in each sub ledger. This ensures consistency which solved a key issue in distributed networks. The transaction loss agreement is a user agreement required to write to the ledger. This allows customer governments rules for meeting legal requirements. Freshness is an internal ledger mechanism that ensures a network with a few write operations reminds consistent and available. Flexible network monitoring allows users with appropriate role to receive full information about the hardware state and the internal state of the Indie services running on the nodes. In addition, in recent years, we improved the mechanisms for recovering nodes after logging, changing primary malicious nodes and communication between nodes. On some questions, we contacted the author of the RBFT protocol to work out more efficient and more effective solutions. In my opinion, we managed to move forward the signs of distributed consensus. In this presentation, I have outlined only the main advantages of Indie. In fact, this is an amazing world with a diverse community, and I will be happy to discuss it with everyone after the presentation. We have communicals. They are regularly held to synchronize our efforts and develop a single direction of movement. We will be glad to have a question in the Hyperledger RocketChats channel used by the project. So thanks for your attention. I can share my email for your questions and I can read your questions in this chat. You'll be glad to answer for them. Do you have any questions? No, really, guys. Oh, we have a question from Michael. Michael, sorry. Does Indie support BBS plus signature? No. Right now, we don't support BBS plus signature. In fact, one of the reasons that just maybe one month ago, we had a final specs about BBS plus. So this Indie doesn't support BBS plus signatures. But we think in this direction. Thank you for your question. I hope you will have another question. And I think I can tell something about our next plans in IndieNode because we have a few minutes more. Now we are working on new releases because we create new interesting features and we changed our release process a bit and want to improve and test it. Do you have any question? How can we add new validators node to existing network? Now we had 25 validator nodes and it's some kind of sovereign government idea that we have a few validators. And if we want to add a new one, we need to send a node transaction to adding this node. But firstly, to have these permissions to send this transaction, you need to contact with sovereign foundation. And after this, I don't see any problem why you can't join this validators pool. Thanks for your question. Because I think it's interesting question in all PBFT protocols because the count of nodes limited. So do you have more questions? I have two minutes to tell you something interesting in another topics. So as I said before, we... Oh, I can't. Sorry if I pronounced it wrong. Sonec was talking about separating the network and more than an indie functionality. Not a basic... Firstly, I think sovereign, it's not a basic network. It's another organization. And about adding a new separate indie network. In fact, you just need to start pool with specific scripts. That creates a pool through using a genesis file with a genesis transaction. It contains a few start nodes. And after this, if you want to add new nodes, you can send specific transaction, node transaction to adding nodes and to make it validator. Yes, I think we're out of time. Thanks for your question. If you have more questions, please send them to me in email or in rocket charts and hope to see you in community calls or online. Thanks for your question and for your attention. Thank you.