 All right, I apologize for the delay. Let's see. All right, it looks like the areas working group met yesterday was anyone able to attend this call. I did. The, we talked about how to cool demo of a native iOS like areas library and Swift, which appears to be on the way to donation to hyperledger as part of the areas project, which is really cool. We also talked about did come be to interrupt credit goes to Lance from roots ID who has done a lot of work in this area. And it starts to feel a lot like we're going to start defining AIP version three with did come be to as a foundational basis for that. So that is in the beginning stages the very beginning stages, not at the end of conclusion or anything but But that that appears to be moving forward in the community. All right, very cool. Thank you, Sam. Looks like areas bifold met last week was anyone able to attend the bifold user group. Looks like they're working on some OCA stuff and some bugs anyone wants to dive into that. And then freeze cloud agent met a couple days ago. Was anyone able to attend the cloud agent Python users group. Yep, the, the traction demo and occupy plugins architecture was put forward so some of the things we'll hear about today. And, and then presentation from ID Union on how to use or an idea for using interacting between an open ID connect relying party and, and a did come, you know, occupy holder for providing proofs so so using out of band to connect between them or at least to share a credential. So interesting approach. The other topics will will carry on next week. But there was good, good discussion on this idea of getting started on on combining open ID and occupy. And this built on another presentation down a few weeks before. Also on on the same topic. All right, sounds good. Thank you, Stephen. See, looks like areas go met last week was anyone able to attain to the framework go planning meeting. All right, it looks like they were discussing some did calm be to stuff. I'm not sure if anybody's framework JavaScript met today. I'm not sure if anyone was able to attend this meeting was anyone there. They were talking about some credential delay and did come be to support. See, looks like ursa's next meeting was set for November 23 was anyone able to attend the hyper ledger Ursa meeting. You can find their meeting recordings here, if you're interested in following up on that one. Trist over IP has not met very recently. It looks like the technology stack working group met on the 28th was anyone able to attend this to IP meeting. Hey, yeah, the center here, I was there. And finally, I think was, I'm just going to collect. There was, like I said, because the holidays, not too much attendance, but it was mainly driven. And I think Daniel, I think maybe was there. And we kind of went over the, you know, summarization of what happened at the IRW seminar in California. And that was primarily it and there were fewer things, but nothing more specific. All right, sounds good. Thank you, Sandy. And by the way, they're supposed to be a itf meeting, I think in fact supposed to be at noon today. So, for the AI and medibus technology framework from the technology stack. It's supposed to be a technology stack meeting this morning at 10, which I couldn't because I had a conflict with my work. So I don't know how to get this one there, but I do plan to attend the one at noon. All right, sounds good. Appreciate you. We're back to us. Yep, thank you. So the concepts and technology meeting on the 21st, was anyone able to attend this TOIP meeting? Okay, looks like they were discussing some terminology for toolbox 2.0. This week was a users group. We talked about some of the compatibility concerns, but one of the things that came out of that was that it would be really useful to have some test agents stood up. And so one of them that was brought up was the adjustability to do a trust ping, which is a very crazy simple protocol. But if you can successfully execute a trust ping with another agent, then there's a, then a lot of things work. And so, which is, which is really useful. And so I volunteered to work on that. And so I'm working on a very simple trust ping only did come be to agent for that purpose. All right, sounds good. Thank you, Sam. Looks like the interoperability group is canceled for IW and has not met since. Actually, the interoperability group met Wednesday. I have not heard the recording yet, but Paul Knowles reported on overlays, concept overlays, OCA, the overlays architecture. So that might be an interesting one to have heard what the latest update is on that. I'm going to catch up on it when I get a chance. All right. Good to know. Thank you, Stephen. I will make sure this section gets updated. Awesome. I believe that is it for our community updates then. We'll pass over to you, Kyle, if you'd like to start share. Tim, there's one other year missing, which is the non credits work that's going on. So we met on Monday and had a really interesting conversation for those not aware of this that from like a lot of who talked about some new work he has done and and what could be the foundation of a non credits next generation with a number of really interesting features and so on that we implemented with different cryptography primitives. So interesting presentation. All right. So you're suggesting to add that at the bottom. There's none. I want to add an on credits. I think that's more active than some of the other things that are that are structured there in there. All right. Sounds good. I can definitely do that. Stephen, do you have a wiki link and on credits. Yes. Yeah, I can share that it's hyper ledger non credits is now a project and so it's on the hyper ledger wiki and I'll shoot it over to you. Great. Thank you. Awesome. Well, I think yeah with that we'll pass it over to you Kyle if you want to start sharing. Great thanks. Organized here. All right, you can see my screen. Yeah, we can. Okay. I'm going to go through this presentation. Feel free to ask questions as we go. And maybe if Tim you can keep an eye on the chat for questions that might come in chat. Just let me know. So I'm Kyle Robinson I'm the senior strategic advisor for the energy and minds digital trust project as being run with the government of British Columbia. In this presentation we're going to talk about digital credentials for organizational identities in the natural resource sector. So energy and minds digital trust is really working on the BC government digital trust ecosystems. There's also work going on with the Ministry of Citizen Services with different project, but we are working very closely together on an overall BC government digital trust ecosystem. There's a number of different use cases involved. One of the uses that the energy and minds spaces looking at is around sharing sustainability data certifications and credentials, particularly between businesses and government entities, not so much in the personal identity space. But there's three sort of opportunities that we're looking at for using this type of technology self sovereign identity verifiable credentials in the context of sustainability reporting. One of them is more efficient processes for reporting. And so the technology stack actually allows for better efficiency. For sending data around because at the end of the day really the SSI or verifiable credential technology stack allows for data transport between different parties in a structured manner. Current processes are often unstructured. So their emails or PDF reports or things like that that are just emailed around. But this allows us to have more structured processes and data standardization. The next piece for that is increased trust and security. So there's a lot of third party verification that's often done in this space of sustainability reporting. And so an end receiving party for information really wants to know that they trust the data they're receiving, which has been audited by third party. And again, this technology allows for that, you know, digital signature to be baked into the credential itself, which that end party can examine and understand where it comes from to see the trust. The other important thing is actually selective disclosure. So we're looking at we're reusing hyper ledger non creds to enable selective disclosure. And one of the primary reasons there is there's a lot of data that is handled between businesses that's, you know, reviewed and audited, but not all of it is shareable to all different parties. So what we want back to the efficient processes is we want to reuse data sets that have been trusted, rather than recreating multiple data sets with different subsets for different parties. So using selective disclosure, you can have one credential, let's say, with like 100 attributes of information, which covers many, many use cases for who all the different parties are that you want to share with for regulatory reporting, voluntary reporting, adding to an ESG report, sending to investors sending to a bank, all these different things you want to use the same set of data. So you don't have to constantly get it new credentials in different formats with different subsets of data, which is again what's happening today in the form PDFs and that kind of thing, or recrafting data sets. So selective disclosure for those not familiar is a mechanism where you can have 100 attributes of information, and then you can pick only the subset of information that receiving party needs. So the receiving party might want 10 different attributes of that information. Well, they can specifically ask for those 10 and you can use the 10 values from that specific credential to fulfill that request. You can use the same digital signature as if you were to share 15 different attributes of information. So, a little bit more on the credentials. We talked about efficiency of reporting. There's increased accuracy. So right now there's often a lot of data manipulation that's done in Excel. Somebody will, you know, copy and paste data from this source to that source, reframe it. Copy it somewhere else. Again, this is all this reformatting and subsets of data. So increased accuracy is important. So that you can actually have the data all the way from the root source, and it's just passed all the way through using these data standards and the technology. We talked about improved trust and being tamper proof for transmission privacy preserving this so they're only sharing what they want. Maximized markets is so where the natural resource companies allows them to compete in these global markets. So what we're seeing right now in the market is particularly in Europe is there's a requirement for responsibly sourced products. And then to get that to that responsibly sourced product, there needs to be a digital signature on the product and verifiable credentials allows that to happen. There's a couple other potential technologies that are being looked at, but there are sort of verifiers in the trust triangle sense in the market space that are looking for those credentials. So we want proof that the data is or that the product is sustainably sourced. And this also dovetails into the supply chain solutions. And, you know, we're just innovative technology so this is all very cutting edge technology and positioning British Columbia as a actor in the natural resource international trade space. We want to enable our companies in British Columbia to do this kind of thing. So the, so energy and minds digital trust as a as a project as a bit of a program are enabling these companies to participate in this space. Okay, so in EMDT, we have two teams, we have one team that is working on our pilots that are use cases working with different stakeholders. And we have another team, which is our developers and so our development team is working on a thing called traction, which was mentioned earlier in the call. It's open source software and we're being built on top of Akapai and in the, it's right now it's architected so that the we're building plugins on top of Akapai, very similar to the plugins that in this year has been building. We're using that Akapai plugin architecture, so that you can have an existing Akapai, and then add those plugins to get the additional features and functions. For the most part, the plugins that we're building are user interface, and to a certain degree data storage, like tables that would get added into Akapai. There's one that we're working on which is basic messaging, one that is a tenant UI, so it's a user interface on top of Akapai to manage the tenant and all the different things that you can do with it. And then the third main one is the innkeeper UI or the innkeeper plugin. And so that's for managing multi tenant solutions for Akapai. Yeah, it's probably good there. So, so that's our technology team that's they've been working on to support all our pilots. And so this is our updated ecosystem graphic. And what we've got on here. This is actually new this graphic. So this is the first the first group to see this updated version. The on the left hand side on the legend. We see there are these different credentials, all these different shield icons, their indication of the credentials that are being issued. And then the second part here is the digital wallet technology that's being used in a pilot sense. The digital wallet technologies have these orange, like the orange border for traction. So we'll see that around something like this energy mines and low carbon innovation entity. So they'll be using traction. We in our pilots we're using or partnered with northern block. And so we have some actors in the ecosystem using northern block technology interoperable. It's also based, it's Akapai based using hyper ledger areas. So that's interoperable there. And you can also see this green one which is on open earth. So they're using a base Akapai integration. So we have talked with spherity. You don't know if we actually have them marked in here, not yet. But that is a partner that we're working with spherity that also interoperable. That's more into the supply chain. They're a company based in Germany. So what we see here in overall in this ecosystem is on the left hand side, generally these are issuers of credentials. And you can see the different types of credentials that they would issue. In the middle, we would have to our holders. So these are companies, these are natural resource companies based in British Columbia, so copper mountain mining corporation, their mining company. They have a facility in the middle and interior British Columbia tech. They have eight different mine sites, I believe, throughout Canada, I can't remember all the locations, tourmaline and Pacific Cambrian. Those are natural gas producers. So they have pipelines, they extract natural gas and send natural gas through pipelines to be sold. So far right hand side, we have our verifiers and so what we see is open earth, they're a voluntary reporting mechanism or reporting warehouse for greenhouse gas emissions and pledges for climate change. The mining association of Canada. They are doing a, it's called TSM, which is towards sustainable mining, which is essentially a ESG type of a report. The Lennon metal exchange is the LME. That's one of those European markets. And then we have the British Columbia Climate Action Secretariat and the BC oil and gas commission, those are both regulatory bodies in British Columbia. And then at the bottom we have going city, which is the actual city in South Korea. They're a consumer of natural gas from British Columbia and expansive. They're a market for natural gas for greenhouse gas emissions. So there's a lot going on in our ecosystem. We've talked with all of these different parties. They're all at different stages of involvement with our pilots. Our primary group that we started out with is Pricewaterhouse Coopers, Copper Mountain and open earth right at the top there. So on to our next slide. We pause there if there's any questions. Actually, the next slide I'm going to show video. This is our demonstration. Oh, good. Okay. Energy in Minds Digital Trust is enabling a global digital ecosystem to make it easier and more secure for natural resource companies in British Columbia to share sustainability data. This demonstration builds upon existing regulatory emissions reporting processes. Because this is a pilot, it does not satisfy or replace regulatory reporting obligations. In this demonstration, we will show how Copper Mountain Mining Corporation uses a digital credential issued by Pricewaterhouse Coopers to share with the government of British Columbia's Climate Action Secretariat. Annually, Pricewaterhouse Coopers verifies Copper Mountain Mining Corporation's legislatively required greenhouse gas emissions data. Having verified Copper Mountain's data, PWC uses Northern Block Orbit to create a digital credential. PWC inputs the data into each field and issues the digital credential containing GHG data to Copper Mountain. Copper Mountain sees a new notification from PWC. Copper Mountain logs into Northern Block Orbit to view the credential. Copper Mountain selects the new credential, inspects the data, and accepts the credential. They now own their verification statement as a digital credential and can use it to fulfill requests for information. Copper Mountain begins by sending a presentation proposal in order to share GHG data with the government of British Columbia's Climate Action Secretariat, CAS. CAS's traction wallet auto accepts the proposal and triggers a request. Copper Mountain then reviews the necessary information, selects the digital credential, and sends to CAS. CAS requires mining companies that emit above 25,000 tons of CO2E a year to verify their GHG emissions annually, adhering to the Greenhouse Gas Industrial Reporting and Control Act. Using traction, the Climate Action Secretariat can see how Copper Mountain has sent their digital credential. CAS has the ability to see that Price Waterhouse Coopers verified this data and issued the digital credential. CAS still reserves the right to check emissions reports for accuracy. This demonstration is one of several EMDT pilots. Exploring how sustainability reporting can be made more efficient in the natural resource sector. Contact Energy and Mines Digital Trust to learn more and to watch a live demonstration of a credential exchange. This demonstration uses traction and northern block technology. All right, so that's the video. If you want to connect and talk more about the work that we're doing, there's my contact information. That's a QR code that goes to LinkedIn. And so now, Tim, we can open it up for some Q&A. Thanks for the presentation, Kyle. What's next from the pilot? What are some of the main things that have been learned? Oh, boy. Well, on the technology front, we're actually working even more closely with the Citizen Services Group to align our technologies. Because the traction components that you see could be used for any of the different use cases. So we're working on doing some alignment with just the government as a whole and what that's going to look like. So that's our development side of the fence. For our pilots, we're actually working more on the natural gas space. And so there's a couple of things that are very late breaking that we're working through. The natural gas companies that we're working with is interested in, well, they're actually setting up IoT sensors to detect fugitive emissions, which is basically gases that come off of facilities that are producing natural gas. And so those sensors are IoT devices. And so one of the ideas that we're looking at is to have those IoT sensors be issuers. Either there's software built into them or there's a centralized system that would be integrated with to have them actually issuing very regular credentials of the emissions. Weekly, for example, so you'd be able to get weekly emissions from an IoT devices credentials. And then those credentials can be used to basically add up and fulfill the needs for, you know, weekly monthly yearly requirements in a trusted manner. Again, that's very early. But that's some of the things that are being explored with the natural resource space is the integration with IoT device systems. Oh, that sounds really interesting. Maybe I'll just pop back to our ecosystem side for a second. This one. So yeah, there's a lot, there's a lot going on in our pilots over here. And again, all at different stages. A lot of the work that we've been doing on our pilot team has been with these credentials and looking at the actual data structures for them. Some of them don't really already exist. Some of them do. Some of them have existing governance, what we would call governance information. For example, towards sustainable mining. They have pretty good data, or sorry, governance structure for what a TSM credential is, and the way that it's used. So, from a governance perspective, we're looking at how we can leverage the existing work that's been done and how what, you know, gap we need to fill for governance for the actual verifiable credential form of towards sustainable mining potential. The other thing with with some of these other credentials is how we're filling the gaps on the governance. Thanks for the presentation. So I think that my company is working on a similar project from the other side of it for carbon sequestration or solar panel capture. And I guess the major differences that lead back to me is like, probably, I think what you mentioned before like we're capturing more data at the sensor level so actually at the raw source. So it's a double credential so it's a, I would say it's a, it's probably a little bit more robust audit trail right back to the sensor itself. And then I think like, and then it eventually it does tie into carbon credit ecosystems that are fully like third party auditable which I think you know you have a lot of those elements here but I wondered if you see that tying into like the purchase of carbon credits or into the sensor ecosystems and then how far back to into the, like, into the source of the data, you think this system would go. That's a good question. So, what we've talked about, if you're not involved there's a greenhouse gas emission task force that's just been started up with, I think it's trust over IP. Everybody can can correct me on that but, or we can chat after. And one of the things that we talked about in that group is looking at it from a bottom up or a top down perspective. And when I what I mean there is the bottom up would be going to the very, very source of the tiniest little report, like, if it's an invoice of diesel fuel, you know, from last month or something. Maybe as far back as they can go to actually get the data that contributes to the higher level yearly amount. So that's the bottom up approach or IoT sensors on certain pieces of equipment, even just a gas gauge on a dump truck or something. The other way to look at it is to go from the very top and just say, you know, we're just going to deal with the total for now, and get that moving through the ecosystem. And we will figure out how to take all the different pieces of data underneath to get to that total. There's a need for verifiable credentials for all of it and how it all gets kind of chained together and added up. And for our pilot word, we're starting from the top. And so there's an existing process where it's a regulatory reporting process that was shown in the video, where it's just sort of a total number. There's a lot of work that's done outside of the system to get to that number. But it's still at the end of the day is a trusted number because an audited by third party in this case. So price water has Cooper's. So the trust is that PWC is the testing to that number, based on the work that they had done prior to it to creating that number really. Sorry, they get the number from Copper Mountain, but they verify it. They do a site visits and all these other processes to make sure that that is accurate. So that there's so that's the top down or the top down and bottom up approach. So the other thing to answer your question on the carbon credits or the carbon markets is this is one side of the equation of a net zero sort of result. And so to do a net zero report, you have to first, you know, document and report on all of your actual emissions to say, yes, we are meeting, you know, 97,000 tons of CO2 a year. That's your starting number. Then you need to look at your carbon markets to be like, okay, well, we need to figure out how we can get, you know, 97,000 offsets or credits, so that we can report that we're net zero. So I definitely see there to be a linkage here. It's unclear at this point how that linkage happens, but it's something that needs to be done at least by the company in the middle. So Copper Mountain, for example, if they wanted to report net zero, they would be able to use kind of what we're building in this ecosystem to have verifiable, you know, credentials that speak to that 97,000 tons of emissions. So we need to use maybe a related system or a connected system, or, or some other mechanism, maybe it's just a carbon credit thing. And then Copper Mountain can bring those two numbers together and trust the banner to say this is our offsets. Does that answer your question. Yeah, I guess my thought would be, I think, like, using verifiable credentials makes a lot of sense to me for the bottoms up approach. I'm just curious on the tops down approach because like, it seems like what you mentioned like PWC already does onsite inspection like they're the auditor, they've already been the one on the site counting the number of dump trucks and the amount of fuel. What value does the PWC get from receiving a verifiable credential, which I guess is just kind of reasserting the data that they've already audit or maybe I'm missing something. Yeah, so, so in this case PWC is not getting the credential, they're issuing the credential. So they are actually taking data from Copper Mountain there's a bit of a process to, you know, for where Copper Mountain actually like, you know, sends all their invoices and all that fun stuff. They also have a process where they do a site visit. This is actually from a regulatory reporting perspective, a requirement to do a site visit and have a plan and these kinds of things. It needs to be third party audited. So PricewaterhouseCoopers is actually the issuer. They're the ones that are issuing or testing to the numbers. So Copper Mountain gets to hold that number, and then they can do what they want with it they can share and they can put it in the ESG report, those kinds of things that help answer that. Yeah, so I was reading your diagram backwards so I thought I thought that I thought the data was coming from the right side to the left. No, it goes from left to right. Yeah. So yeah, issuers are on the left here. For the most part, holders in the middle and verifiers on the right. So these people on the left side are the ones attesting to information creating creating information. And then the middle group is holding it. The group on the right is consuming that information. Great. Great questions. Any other questions from the group. Okay, well, if you have follow up questions or want to get connected, you can email me or check me out on LinkedIn. But for now, I'll pass it back to you, Tim or Shar. Sounds good. Thank you, Kyle. I believe that was pretty much all for today. Be sure to join us next time. We will be hearing from shoot, let me pull up his name. And then we'll be hearing from Dominic is a scout ski. Yes, I believe so. To that presentation. Yes, thank you, Shar. The next meeting will be on December 15th, and we will send out discord reminders as well. So thank you all for coming and the recording will be up soon. Have a good one. Thank you.