 Good morning, everyone. Thanks to the Hyperledger community for having invited us to share our vision and thoughts about social identity and the future of digital identity. Before start just a few words about us. I'm Emiliano Vernini. I've been working for post-Italian over the last 14 years. Currently, I'm the head of the innovation strategy whose mission and goal is to bring new technology inside our organization and support business innovation. Here with me today, Rosario Zeghiara, hi Rosario, please introduce yourself. Hello. My main interests are computer programming, especially Commodore 64. This is the most important part of my CV. Please, Emiliano. For those who are not familiar with post-Italian, as you can imagine from the name post-Italian is the largest postal and logistic operator in Italy, but is also a bank, is also an insurance, is a mobile virtual operator and with its over 12,000 postal offices spread all over the Italy, is for sure the biggest proximity network in Italy. When I say proximity, I mean that daily we meet face to face our customer. We have over one million and a half visitors per day in our postal offices. You can imagine from these huge numbers how big is our company. Probably you're asking why post-Italian and digital identity is well because post-Italian is also the biggest digital identity provider in Italy. Post-Italian issued over 16 million digital identities. Post-Italian solution that is named post-D is AIDA certified and so post-Italian plays a really crucial role in the digitalization process of the Italian country. Before going deeper in our solution and what we have developed so far, just to set a common ground of knowledge, I will go briefly through the evolution of digital identity model during the time. So started from the centralized identity, seal of the identity in which one operator holds all the information related to the digital identity of the user. Through this identity provider, the user can gain such as to online services. This model has several problems. First of all, the user is disintermediated let me say as not the full control over his data. There is a third party that can track all the user digital interaction but also the user experience is really fragmented due to proliferation of the digital identities for the same user. The federated model solves this last problem, this last issue but the user is not still in full control over its data. There is always an identity provider who disintermediates the user from the service provider. And so the evolution is the social identity whose main goal is to bring back the user, the citizen at the center of the digital identity ecosystem and give the user the full possession and control over its digital identity information. And so the user is now able to with social identity is able to gain access to online services without relying to a third party. If we look at what happened in the physical world, we all know that a citizen, a user can ask to some attestation or identity document to a public registry. And then he can collect the identity document, the attestation and store it in his wallet and use whenever he wants, whenever he needs to access a public service. The verifier can, of course, check for the validity of the document just looking at the document. Well said, social identity aims to replicate exactly these flows also in the digital world. And so using the blockchain as a trusted registry for anchoring the digital credential and for verifying the validity of the digital credential so that an older user, a citizen can in every moment independently and again without relying on a third party on a trusted issuer gain access to online services. And the verifier can in every moment check against the blockchain for the validity of the credential provided by the user. Social identity is not a new and exploratory topic. There are a lot of different implementation and projects that are running U-Port, ION, Sovereign, Alastria, but also a project within the boundaries of the European blockchain partnership that is named as if European social identity framework that aims to create a common framework for the development of a European digital identity. So when we first started exploring social identity, we decided to not reinvent the wheel, but to start from one of the implementation, the implementation that best fits our need and our vision. And so we decided to start from the Alastria implementation because Alastria model, Alastria SSI model is in line with the S framework because Alastria is built on top of the European blockchain services infrastructure. And in Italy, post-Italian is part of a project that is named Italian blockchain services infrastructure that is in line and aims to be interoperable with the HEBS infrastructure. And moreover, because Alastria is built on top of Quorum that is an Ethereum implementation. And it is really important for post-Italian because we want to use a general purpose blockchain instead of a dedicated vertical blockchain for development for digital identity application. Now I leave the stage to Rosario who will go deeper in the technical details of our project. And then I will be back at the end of the presentation just to share with you some consideration about the possible business model. Okay, let's start from the mandatory slide with the hyperledger ecosystem. We have very emphasized in this slide in red the components we studied and analyzed in these last few months. And in green what we what actually made into the current version of our solution. Next slide. Let's check how these red components have been analyzed and how we took the decision. Of course, we are talking about the surface of an identity solution. So the mandatory first step was starting studying hyperledger indie. Then we took a glimpse that lasted for at least three, four months studying fabric. The final decision also driven by what Emilia the strategic ideas Emilia not talked about was to go for Bezu because Bezu is of course an Ethereum virtual machine and perfectly matched our technological requirements. Also we dedicated some of our brain power in studying hyperledger artists. But still the final decision was to go for Veramo as the agent framework. Then we have a caliper caliper is something we use to benchmark our infrastructure. Next slide. This is how our solution currently is framed between the other competitors. On the far right you see hyperledger indie. From our point of view it was some sort of full stack solution that not really was suitable for the multi-purpose ecosystem blockchain we were designing. For these reasons we didn't use it. On the left you see Alassia. Emilia said that was the first solution that really had a range of functionalities that matched our functional requirements. For this reason we went into the deep of code of Alassia and started customizing it. Please next slide. Once again post ID will be just one of the systems of the solutions deployed on the hyperledger based infrastructure nodes you see in the lower part of these slides that will be named IBSI EBSI in Italian that is Italian blockchain services infrastructure. It will be just one of the users cases we are going to work on. Let's get into the decision on moving away from Aris. Aris from our point of view is absolutely the most advanced agent framework available on market. Still the funny the nice thing that the useful thing is that it is out of the box able to accommodate the range of different agents deployment model we intend to use so there is a dotnet version that can be used for mobile app. Still the same version can be used for the server and so on. The real problem is that our current stack and our guidelines software development guidelines we adopted internally are mainly based on Node.js TypeScript and hyperledger is even if is available for Node.js in Node.js TypeScript the flavor it doesn't have the same maturity level of the dotnet version and customizing it would not match with our plans. So for these reasons we moved to Veramo that is one of the projects in the U-port effort. Veramo is a clear plugin-based architecture that allowed us to clearly fully plan a customization of such plugins in order to there too on one side get to the smart contractor of our SSI implementation and on the other end be deployed both on the mobile phones and in the government public services web services. Okay let's get to the next slide. This is something that going to Veramo is something we planned for the next iteration of our app. Current iteration has been designed and developed by taking some shortcuts. For instance we used a non-grown agent framework which just allowed us to have a synchronous communication among agents that in the simple words just allowed us to interact by using the wallet app with the issuer, the verifier and so on just by scanning QR code and sending a credential for instance taking them and sending them to a call back this was a real movement that still has been functional to getting to an MVP that we finalized just yesterday evening for the first time. Next slide is depicts what we are planning. We are planning to replace the mid-layers that we call on the left part post-ID library and post-ID wallet API to something named the public post-ID agent that will allow as you can see from the sides of the block in the upper layer on the right part post-ID that is the wallet the issuer the verifier and so on will be developed in the same way just relying on the lower part that is the agent framework customized for each of the different deployment model. This is a quite interesting step we are currently designing it. Next slide we give a glimpse to the current version of the smart contracts which as I said already said were just to take inspiration from Alastria. In the upper part we see the function separated for each of the possible identity taken by each of actors in the ecosystem so we will have an identity for smart contract that test the functionalities for every actor in the system service provider functions for just the service provider, the issuer and so on. Then at the very core of the system there is the identity manager smart contract that also collects the four registries that are the very core of every SSI solution where the credential registry, presentation registry, public registry and the brand new credential schema registry which that is something we designed and implemented because it was not available in Alastria. Each of the registry of course take care of keeping just the smallest part, a bit of information needed for the functions of the system so we just keep the ashes of the credential, the presentation and so this is also to be compliant with the GDPR. And in the lowest part of the the schema you can see the identity proxy each of the actor will have his own copy of the identity proxy at the address of the identity proxy will be part of the DAD schema you can see on the right in yellow. In the next slide there is another small detail on the technological strengthening effort we had with the smart contract that we added from Dom and Zeppelin an upgradability smart contract that allowed us to fix bugs and scale functionalities in future without losing the state of each smart contract. And we also added a rule-based access control to have a fine-graded administrative tasks control on each of the registry of the DDD of the our SSI solution. Finally in the last in the next slide you can see Evianno please start the video. You can see the current version of the post ID app as you may expect it is a big yellow app with the standard with our enterprise logo colors and it is the as I said the MVP1 we are planning MVP2 for next September that the two main additions will be one of course is the agent I talked about hopefully enough in the previous slides and the next big step will be a system to allow user to get back in to recover the credential here she may have lost during the daily using of the system. Okay this is the end of my part please Emiliano. Okay just to share with you some consideration about the model for sure for post-italian which is now an identity provided in Italy it will be a great shift from a custodian from to be a custodian of the customer data to we are now trying to test a different model we are now trying to support our customer the Italian citizens in managing their own data autonomously but for sure we think that not all the customer have enough digital knowledge to go by themselves so we are planning to use a premium model because as you probably know digital identity now is free and will be free forever but as post-italian we think we could offer premium services in order to help our customer managing their data. An example of premium services could be for sure keys recovery in case of wallet loss or key confirmation by an hacker but also we can offer a online repository to back up a store an encrypted version of the credential and also offer ancillary services like transaction document signing trusted communication and so on so we are trying to shift our model we are trying to understand if this model is sustainable or not shifting from a custodian model to a different business model okay now I think it's time for some question if you have I can say there are at least three questions one is from party costas do you do you think there is possibility you would leverage the public ethereum blockchain in the future please I think it is a great question and we are working with diver ledger bezu because it is as you probably know it is an ethereum client that could be used to access also the ethereum public network it depends on the regulation okay I think the regulation will be very important because we need to to define what is our what will be defined by the regulation but we think yes we technically we could also use the we are ready to go okay the other question from Patrick who will be running the meso nodes in the initial project phases will this be public to read write okay we are we are we are using right now the the test net of the ebsi project ebsi as said before during the presentation stands for italian blockchain services infrastructure and is an experimental project that aims to build a public blockchain ecosystem for the public administration right now the the the blockchain is permissioned but we are moving towards a public permissioned model so everyone can read from the blockchain but just uh known organization and so uh just validators can write on the on the blockchain but everyone can submit transaction okay there is another question from pasquale could you tell us the information of the very valuable credential you are storing in the blockchain how do you avoid the privacy issues I guess I can answer this one that we just may keep on blockchain just a careful crafted hash in this way you can check once you have a credential you can check its validity by calculating this hash still you cannot correlate use this hash to correlate the activities of an actor across the blockchain another question from catarina reis is that italian infrastructure aligned or apart of ebsi yeah ebsi is the is the correct name is the right name right now ebsi is aligned with ebsi meaning that we share the same technological infrastructure but we are also looking at the at the technical governance of ebsi in order to stay aligned in the future I don't know probably uh what I what I expect is that the ebsi will be full interoperable with ebsi whatever it uh it means uh rickardo basso seems to duplicate the question about going on mainnet uh we are not using the the ethereum testnet the public ethereum testnet right now we are using uh a private blockchain uh that is the ebsi testnet in the case to switch to the ethereum uh public yeah yeah there's a there's a matter of transaction costs that we need to take into account there's another question more on the technical side dark creation proofs implemented as a zero knowledge proofs uh as in everlair gerindy this is something we have on the timeline for sure we are not putting it for the next mvp we hope to be able to put our dirty ends on this solution based on on bls maybe for mvp yeah mvp 3 i guess i hope actually yeah yeah uh we hope uh within this year before the end of this year we will have an implementation of uh of the revitalization with uh with the support for zero knowledge proof uh okay it seems there are another question uh no no it seems that we tried uh uh is there a reason i should choose you as provider of revival credentials versus a ministry for instance actually accommodate the credentials for army uh for our ministry yeah yeah yeah we we provide the credentials for the public administration right now in italy uh so we are certified let me say certified digital identity provider so there's not a huge difference between us and the uh between the credential provided by poise italiana and the credential provided by a ministry for sure for sure we can offer right now more services compared to the one uh offered by by a ministry but right now in italy uh a public ministry do not offer uh digital credentials uh i'm not really sure when this session should end seems there are no more uh questions okay if you have any other question please connect with us using uh linked in our twitter and you can see the answer okay it's a wrap we have just one minute left thank you everybody for training us and for the uh useful feedbacks bye bye have a nice day enjoy iver ledger global forum