 Okay, welcome to the session on Estanium to NetZero with verifiable credentials. It's an interesting combination of two topics, a verifiable credential, I think it's a pretty known concept in this kind of community, in the hyperledge areas are the sort of known stacks in this space and NetZero refers to carbon emission sustainability. So let's see, I want to tell the story actually from a Siemens side. I work for Siemens and what you see here is a factory, a Siemens factory. It's one of the sort of factories in a global network that was actually called the Lighthouse Network of Global Factories by the World Economic Forum. It's a factory that produces roughly one product per second, so it has a very high and for many, many years factories of this kind of scale, this kind of automation had always the challenge of being efficient, of optimizing, of being more and more automated and there's now a new kind of challenge and it's actually a big challenge, it's a huge challenge around carbon pricing. Carbon pricing is a concept that tries to move to shift the burden from global warming to those who can actually change it, to those who cause it also and this goes to factories like these, of course not only Siemens factories, but many other factories in the world too. So for us it's a key product like this, it's a program which is produced there as I said every second and the key question is really what is the carbon footprint of this device? How is it composed and how potentially can I change as a manufacturer also on the actual footprint and then of course the price because if we really go into an area where carbon is priced much more heavily than today, the price or the cost of the product will be affected by this footprint and this kind of question came up inside of Siemens but it applies in the same way to a manufacturer of an iPhone or of a phone, a mobile phone, to a manufacturer of some sneakers or to a car manufacturer and all these cases is always the same question what is the carbon footprint and to make it a bit more specific there are actually different scopes when computing a product carbon footprint. There's the scope one which relates to the emissions that are locally happening in a factory so this is normally quite known to a manufacturer also scope two is quite known it's the electricity bill sort of very sort of straightforward the bill that that a factory receives but actually the challenge is to map the values that people or the data that people and manufacturers have on that site scale down to the actual products that's not straightforward because you have variations in the type in the kind of energy consumption you have periods where there is a higher consumption of energy maybe in the summer when you have the air condition more running and how do you then map it actually in a way to your product that it's also understandable you have to average in a certain way you have to aggregate but much more difficult is actually the scope three upstream so the part of the aggregation of scope one and scope two from all the suppliers and that's complicated because we live in an area where supply chains are very complex they are typically global so the sourcing happens not just locally but it happens really across the world and it changes quite frequently so knowing for one particular product with multiple sourcing channels for a single component exactly what is now the product carbon footprint of a component is not really involves a tight connection to the suppliers key question is also how can you request this data in a trustful manner so how can you basically when you receive a product carbon footprint about the components that go into a product such that you can actually trust it and then shift potentially to a different sourcing and then the very right hand side how you then share your own kind of product carbon footprint with the next manufacturer in the chain or basically with your customer so these are the key questions and we believe verifiable credentials can play a role here it's a little bit different role than traditionally where verifiable credentials are used with individuals to use a selected set of identity attributes share them in a privacy preserving and sort of self-serving manner here in the context we talk about products we talk about companies so it's a slight different angle and the scope three what I mentioned before is actually very important because 80% of the co2 emissions of products in general come from the upstream scope three so that's where the biggest problem is within the open within the the own context of the manufacturing that's possible to handle that's in the domain of a manufacturer it's not straightforward but it's much easier because it doesn't involve so many other parties so in this context in this chart here you see the the footprint of a typical product it goes quite some steps and there is confidentiality involved so the way the logistics setup by the the suppliers is confidential to the suppliers they would not want to share it because it's also their differentiation the same about the components of the parts that the manufacturers manufacture this is also confidential and should not be disclosed in the same way as the manufacturer doesn't want to disclose the suppliers and the components that that the manufacturer itself uses so there's there are confidentiality requirements with people you would say privacy requirements here we talk about companies so it's it's more like around confidentiality and an important part is also to integrate the aspect of recycling and the aspect of offsetting you might have heard in co2 decarbonization efforts it's very often that companies try to not really reduce their emissions or their energy consumption or change their sourcing but they're basically try to offset by buying co2 certificates and this could be related to helping to grow forest to do some other means of co2 negative efforts but unfortunately there's a lot of dodgy things happen so this kind of integration of things important thing to bring in here and in all these cases it has to do with trust and the concept of verifiable credentials is exactly for doing this you typically have this these three roles of an issuer a holder and a verifier sometimes the subject is the holder itself but in our case the subject is actually a product in our case it's what is called a zimatic s7 1500 an issuer in our setup here is a technical inspection company here in Germany you have them typically referred as tÜV I think even outside of Germany this term is quite known but in every country you have these technical inspection companies that are quite familiar with certain domains so for ease as they will be used for certain certification of processes in any kind of industry they are used and we believe they can play an important role here for bringing the trust into the system the system cannot work by simply self declaring that a manufacturer says okay my product has this kind of protocol and footprint or what is also very typical today that a so-called lifecycle assessment databases are used where for a product you basically go into a database you look it up and you you get a protocol and footprint value this is a generalization it doesn't really help to move forward with decolonization because it's always the same value it won't change if anything in the supply chain is changed so the idea is here to use the role of the technical inspection companies as the issuer of verifiable credentials that the issuer has inside into the factory it knows about the specific way of measuring energy maybe even on the factory floor it knows about the emissions as well and it knows also about the bill of material the bill of processes that are being used with a product and it can reach out to the supplier or it can get the data that the holder would request from a supplier in this case it's always a direct relationship so the holder the direct relationship with a supplier and would expect to receive some information preferably in the format of a presentation of a verifiable presentation of again verifiable credentials that have been issued with a supplier in the step before such that the issuer can then really have the trust not only based on assumptions with respect to the supplier but information coming in a verifiable way through credentials and this requires again an issuer of course it has to be a different or it's very typically then a different issuer otherwise there could be collusion such that we believe there's a chain of issuers holders and verifiers verifiers that can stretch across the supply chain so underlying is the typical verifiable data registry that helps to give everybody access to the public DIDs the the identities basically of the holder would not be registered here because for the next step the holder should be not known by the real identity for the end verifier so this is exactly the confidentiality the direct relationship also exists between the holder and the verifier typically the customer that would request for a particular product to to issue information in the data registry important is also to have the credential schema and the revocation list by no means there should be any real PCF data so that's also important we have these one-to-one relationships typically established through pairways pseudonyms that help to potentially also anonymize the the the identity of some of the parties with every tool we have claims associated there would be two different types of claims so for the verifiable credential that is issued by the certifier so the the issuer in this so the certifier that plays the issuer role or is the technical inspection company the claim would relate to a product in this case it's the s7 1500 there would be two values for scope one scope two you could think of it also as one value for both scope one and scope two and there would be more information related to the components here just shown as one component as an example which has a manufacturer and a unit it's important to specify the unit the amount of these components within the product as well because the multiplication has to done has to be done based on the information coming then with a presentation from the supplier and here we see already that there is potentially the need for bringing in an anonymized information with respect to the component that is part of the component one so the component to this part of component one also the name of the supplier should not necessarily be revealed so that's the claim that is passed on to the supplier there may be different kind of variations how this can be exactly implemented it depends on the trust assumptions between the different parties but the basic flow would be that a customer would would send a request to a manufacturer expecting there is either already information available or the manufacturer would have to send out likewise a request to a supplier a tier one supplier and the respective tier one supplier if necessary would send again a request to the next supplier in certain cases and you will see it in the short demo that I have also here this won't go to the very end of the supply chain there could be cases where a supplier has not the means to reach out to the next level in this case it would be possible to do some form of self declaration again being potentially certified by a technical inspection company and the actual value that the aggregate value that goes back then to the customer would have a different quality than if everything would be really based on the certification so just this just to let you know that this is considered in the system that we have different of authenticity and different levels of quality in the system but the actual flow is then coming from the left hand side of the supply chain from the tier two tier one and the towards the manufacturer and the customer always in in pair so there's a there's a issuing of a verified the credential former certified to a supplier to a supplier there's again of course a manufacturer then a presentation of selected information that didn't doesn't necessarily have to be or can be the full information that this the certifier issued in the in the credential and indy provides this or the concept of verifiable credential provides this where multiple credentials can be combined in a presentation can be combined in ways of selectively taking information also taking also only a range of the values so there's the crypto scheme of zero knowledge proofs also available so that not the full information that is issued through the verified credential it has to be presented to the next to the next player in the supply chain and then again from tier one supplier there would be a presentation to the manufacturer again an issuing from the certifier that is in the same trust domain as a manufacturer and then eventually a presentation to the end customer there's optional extension here that the suppliers it's anonymously presents certain information also to the end customer think about an auditing kind of situation where you might want to have at the customer in quotes here so talking about the the auditor as a customer would have the need to see more information directly coming from the parties in this in the supply chain we think it's the entire concept has two two sides to it so there's a part where we have the actual network with it this must be an open network where other people can join in there's need for agreeing on standards on things like the quality what I mentioned it's not enough just to point to the greenhouse gas protocol it is still too broad there's there's need also to agree on how you exactly map values down to the the actual product level and then there will be connectors to the network and here you see an example of such a connector where we believe different industries would come up with their own kind of connectors with different kind of requirements okay so I wanted to give very briefly a demo I had believe I have to do it very quickly because we're almost at the end of the time so let me just jump to a very I think it's it's not more than 30 seconds to to show you how this looks like so this is this is an instance of such a such a connector where there's a dashboard you lock in as in this case as a manufacturer you have your overview of the factory you could see all kinds of statistics with your emissions and then you have requests coming in from from a supplier to share data and this relates to a base housing where we seem to have enough data ourselves so we sent a request to our supplier called Ries so here the the view from the supplier in the same tool where the request comes in there's the possibility to enter data through an LCA database there's a possibility to type in the data manually based on the available information at hand but there could be also a possibility then to reach out to actually the next part in in the in the supply chain which yeah would be basically the same kind of request coming into the system and so on here you see the quality values as well that addresses how information is provided the base is it actually by multiple steps in the supply chain and so on so this I probably stop my presentation and and see if you have any kind of questions and I look here in the questions uh Estanium all of us is asking Estanium because of Estonia now it's the the name Estanium comes from is derived actually from the project name that we had it was called Sustainium inside of Siemens but externally we wanted to find a name that relates to sustainability and environment so that's the combination of the E and the Estanium it's a bit like an artificial name but it has nothing to do with the country Estonia any other questions okay I see two more questions coming in which other companies are participating in this network we're currently looking for interested parties to launch the association and we believe we're quite interesting initial founding members here I cannot disclose them at that point but that's important that we have a balanced mix of parties being involved here this should not be dominated by any kind of small circle or even a single company the way information is shared here how the network is run what is the agreement on the layer on top of Indian areas it should be really come up by this by this association another question are you working with Bosch on the agents in the process BC Gov is working on a similar project okay now you have to help him BC Gov Bosch we were in discussions yeah there are discussions with Bosch we were any on multiple projects actually with Bosch on yeah also on yeah very similar topics so I probably can adopt too much in this round here okay yeah yeah BC Gov there's some momentum okay thanks for the information happy to follow up on this Steven just ping me British Columbia yeah got it okay any more questions I think we're actually over time already but maybe one last one otherwise I guess we would have to close good then thanks a lot to all of you please ping me please come back to me if you're interested we have two more presentations tomorrow on the panel there's a sustainability panel on my morning it would be a different time in the in the US and other time zones of course please join and we have a presentation also on very fiber credentials for asset management quite interesting and finally on the ID Union project it's a large association European driven many use cases very exciting also on around verifiable credentials with this okay thanks a lot for your attention and take care