 Using blockchain on logistics and business animation and our presentation today, business automation in the new economy of movement. I'm going to stop sharing now and give the meeting over to Tram. I believe you have a deck, so excellent. You're able to share. Welcome. Thank you. I came from an art background, so I always have to have something visual. So thank you for having me here. A slight correction. I haven't spoke to supply chain before. I spoke to the social impact group, but not supply. That's right. Not yet. Today is the first. So good to see everyone. My, I think my colleague did. Rajat spoke with. Yes, so he was here. I think you maybe. Hello everyone. So during my talk, it's very informal. If you have questions, stop me anytime and you can answer or you can wait until they are entirely up to you. My name is Tram Bo. I am CEO and co-founder of Moby. Full disclaimer, as you can tell, I'm not a technologist. So this talk is not very techy at all, but it's more like the high level overview of what we're trying to do and what we've done so far. I started out in chemistry and then I went on to art conservation. And for a couple decades, work on heritage preservation and conservation projects around the world for organization like UNESCO and the Getty here, based in Los Angeles. And in May of 2018, along with Chris Ballinger, my co-founder, we launched Moby. We are also married, so that was a lot of togetherness during the pandemic shutdown. So a little bit of history about Moby. We launched in 2018, but our history went back a couple of years before that. Many of our Moby members were very excited about blockchain and experimented with many proof of concepts. They all found that putting a vehicle, data or service onto a chain, that was easy, but these applications weren't able to scale. And there were a couple of reasons for that. One, the industry needs standards, standards on like how to identify a vehicle, people, things, trips. One does a trip begin, one does it end, how to connect the whole trip, how to transfer and share data and how to settle transactions. All those needs standards so that we can communicate at the same level. And then two companies were using decentralized technologies, blockchain, but they were building centralized blockchain platforms and were not able to get others to go onto them. For example, we have one OEM that built a mass multimodal platform, but couldn't convince others to go on to the mass multimodal platform. We have another OEM, spent a lot of money building a supply chain platform. But again, it was their platform and couldn't convince other automakers to go on to them. We have a logistic company. When I spent $54 million building a logistic platform, again, couldn't convince others to go on to them. So what we learn, of course, is that centralized platforms don't scale. And this is why Moby was launched in 2018. Longer numbers, we are creating standards and building web-free infrastructure for industry-wide business automation. So why is industry-wide business automation important? Most of the productivity that we have gained within the last 50 years or so came from business automation enabled by digitization of internal processes only. Very little was from the automation of extended value chain involving unrelated untrusted parties. And even when those attempts happen, they tend to be with a couple or a very small group of organizations. So they're not really scalable to industry-wide. And from the beginning, the big picture for Moby has been this, and it's still the same, is that the convergence of all the technologies that you see here will permit any connected entity, a person, a vehicle, a device, a piece of infrastructure to have a trusted identity that can directly communicate and securely transact with another connected entity. And in doing so, not having to go through someone else's centralized platform. And once you have a trusted identity that you can link with location into a verifiable trip, then you have the pay-per-use economy, which we call the new economy of movement. So when it's trusted identity important for business automation, 60 to 65 percent of internet traffic is from bots, and 40 percent of total internet traffic is from malicious bots. And we have 15 billion connected things today. That number will double every three years. So how do you do business with something if you don't know who or what it is? And then the arrival of genitive AI will make this problem dramatically more important. And this cartoon was from 1997, I think. I can't remember now. And I think many of you have seen it. But I think the problem is still true today. So across any connected ecosystem, mobility, telecom, insurance, and we're working with those as well, including semiconductor chips and all that, they have hundreds, if not thousands of connected stakeholders. And they all have not just private but public as well. And they all have unique databases. They all have unique processes. They all have regulation on how to handle business and customer data. And these databases don't talk to each other. They do. It's a risk for the business. So currently, it is impossible to automate business processes without opening up your own databases. So for industry-wide business automation to happen, the solution needs to have the five things that you see here on the screen. One is zero trust authentication. So that means every entity must be identified and authenticated for every transaction. And then all the data or the claims must be non-repeatable. The second thing is data privacy. That is regulatory compliant. Of course, GDPR and non-interstate, I think we have four or five states that have similar regulations as well. And the ability to limit access to intended recipients only. And the third thing is data security and selective disclosure. So instead of connecting to databases and doing business, we want to be able to push the data to the edge and do the transaction at the edge. And the ability to selectively disclose and verify information at the moment of transaction without having to store the data before, during, or after the transaction is extremely important. And then the solution has to be affordable, interoperable, scalable, and extensible. So that means the solution has to be standard-based, platform-agnostic, and that would have to work with any legacy system so that the mom and pop shop can do it in the supply chain. And there's no costly new infrastructure that they have to build. They don't have to pay for integration and they don't have to pay for maintenance every couple of years or so. And last but not least, of course, is that we have to have a solution that is not a centralized platform that is owned by one. It has to be community-owned and operated and open-source. Trian, can I ask a question? Yes, please. Back on the standards item that you mentioned there. How did you decide what standards to use to leverage there and when do you need new ones there? And if that's something later on, great. It just seems to be an eternal problem within blockchain. Yes. So we are, well, there's a couple of things. I'm going to, the next couple of slides, I can talk about them. Is that okay? Sure thing. Yep. So I do have one question around. Oh, sorry. Back to the slide again. Apologize. And the decentralization. Can you expand on that just a tiny bit? Are you talking about the node operators, the validators of a blockchain would own, those are what you meant by owned infrastructure. So if they used, if their node somehow was on Microsoft Cloud, you're not talking about that, are you? A little bit of that, but mainly for here is about centralized platforms. We all know about centralized platform like Google, Google, Facebook, and all that. And then the three example I gave earlier, I didn't give name, but one of the major OEM built a mass multimodal platform. It is a centralized platform. And so the automakers, why would we go on to that? It belongs to you. It's behind your firewall. And then another one built a supply chain platform using blockchain. And also it is a centralized platform. They control it. It's behind a firewall. And so nobody else would go into it. And this is really important message to our members is that you can't build a platform and say that this is yours and then what are those to go on to it? Any other questions on this? Okay. Okay. So keeping all these requirements in mind, we come up with a solution that we call self-solving digital twins or SSDTs in the U.S. I've seen a comedian recently that made fun of the fact that there's so many acronyms on everything. And he did a whole segment on it, which is true because I see a lot of acronyms on my slide there. So self-solving digital twins, the concept of digital twins was generated by NASA back in the 1960s. Essentially, it is a digital representation of an object or a system that captures static and near real-time data throughout the host lifecycle of the object. And for us, self-solving digital twins are digital twins that can self-generate verifiable credentials so that they can identify, they have the ability to authenticate identity and selectively disclose pertinent information at the moment of transaction and ability to verify the data that's given to them. So that means, again, they don't have to connect to centralized databases. They can do transaction at the edge. They are universal translated and encrypted log data. Well, so this is really important. Only the controller or the owner of the SSDTs, self-solving digital twins, has access to it and nobody else does. And the SSDTs are standard-based. This is the first standard that we are talking about for the ecosystem. We use W3C standards, the World Wide Web Consortium, which produce standards for the Internet. And the standards we've been using here are the DIT and the VC standard, decentralized identifiers and verifiable credentials. So the VC standard was approved a few years ago. The DIT standard was approved last year in August, I think. And it's been worked on for many, many years. And actually, Moby's first standard ever in 2019 was the ID, Moby vehicle identity. And that standard was based on using decentralized identifiers. So we were using W3C DIT standard before it became a formal standard. We were working with them to understand. And I think many of you know this already, but it took a while. When it was first voted on, everybody voted yes for the standard. There were three organizations that didn't like the standard and objected to it. And of course, I think you can take a wild guess as who they are. They were Google, Apple and Mozilla. So these are the two standards that we use for the ecosystem on identity. So if you look at these things that are listed here for the self-sorbent digital twins, they fulfill most of these requirements. They are essentially zero trust authentication. They use, they enable data privacy, security and selectively disclose information. They are standard based for interoperability, scalability and extendability. They are affordable because users don't have to build new infrastructure. SSDTs can be an app that you download to the device of your choice. And it can be stored in the cloud of your choice, of course. And the last thing we need to address is how do we make sure that it's not one entity that owns the infrastructure? So to do that, this is, I think you've seen, many of you probably have seen this DIT and VC and this whole verifiable credential ecosystem. So Mobi is a technology agnostic. So we don't endorse any specific blockchain. Ten years from now, we don't know which blockchains we'll still be around. So that's not our job. Our job is to work with blockchain because we see the potential of blockchain and we love all the capabilities of blockchain. But we leave it to the expert to build out that. So what we instead, we are building a layer two, which is think of it as a trust layer that is enable us to anchor the DIT to decentralize, identify onto blockchain. So and then the third layer on top is Cetopia, which is where the self-sustained digital twins reside. And this is where they transact with each other. So the POC of 2016 and 17 that I mentioned has proven to our ecosystem that blockchain works. That's not that important. What is important is how blockchain is being used. I've always said there's the 200 ways of cooking chicken and rice. If you look up on the internet, every culture has a chicken and rice dish. It's how you make it that's important. So within Mobi, how we use blockchain is very specific and we only use it doing it to have DIT registry and that's it. We're not storing any data or any PII one chain. We don't recommend it and our members in this ecosystem does not do that. And right now, the two blockchains that we anchoring to is fabric and Ideria. So every DIT that we create is deposit onto the 15 nodes that we have so far in fabric and then also onto Ideria as well. So I think I do I need to go into this whole ecosystem at all what's going on here or should I skip that? Well, you can spend like an hour on it. I think it could be interesting just to hear a couple of minutes on it. Okay. All right. So come on. Thank you. Really in simple term, the way I describe the IT and integrated just network here is like a phone book. It's been a while since many of us have seen a phone book. I'm old enough to remember when they dropped the white pages and the yellow pages at the front porch. And so now Google has become the de facto phone book. We Google everything. But we're trying, this ecosystem is going to try to get us away from that. So this is the public communication channel. You deposit the DIT and then once you look up the services of a business like in the yellow pages, you can usually see an ad, you see a business and they list all the services that they do. And then there's a phone number that you can pick up the phone and contact them. So essentially, this is the same thing is a public publication. You can look up services. And then once you find a business you want to do a business with, you pick up the phone and call them. And when you pick up the phone and call them, you communicate in a private communication channel. And that's up here and we use verifiable potential to do that. And usually when you see this whole ecosystem is being built by one organization, one company, and we think that is way too much power for one organization to have because you have the agreement, the transaction, and then you have the DIT, the signature that's in them. So that's way too many things that one company have. So we actually even split this up to two and these are two legal entities that we register and they are separate companies. All Movi members in good standing have a little bit of shares in both of these companies, but we will soon also reach out to VC, all of our members and external to invest in it because we can't do this based on just membership fees alone. We are a non-profit startup, so it's like a double whammy, no money and no money. So the next, I have I think two more slides of something to this, which explain exactly how we do the verifiable corrential and you don't need to read this, please. I'm just gonna walk through it really quick. So this is a battery birth certificate verification. I think some of you might have heard of the battery passport, correct? So the EU Commission has written a regulation, it hasn't been signed yet, but it's been drafted and the second draft was earlier this year released. Essentially it requires that if anybody produce a battery greater than two, and I think you have to have a battery passport, which means pretty much every battery except for the little ones. And the battery password, you don't have it, you cannot sell it in Europe. So that is really a big worry for auto manufacture and the battery manufacturers in our ecosystem. So this is an example of how a verifiable corrential works in our ecosystem. Let's say we have battery manufacturers, we have OEM, which is stand for just vehicle manufacturers, and we have let's say a couple here, and they all have their own legacy system and databases, and none of them are connected or want to connect each other to do transactions. So how do we make it so that they interoperable and can send messages that everybody can understand? So that means everybody would self-create a self-solving digital twin. And then once they generate that, they can do this kind of messaging. So the battery manufacturer creates a battery and then also create a battery self-solving digital twin. Then the manufacturer will send a message to its own SSDT and say, hey, can you get a DIT, a decentralized identifier created for this battery, please? Then that message gets translated into a accepted protocol and send that message to a Cytopia node. Cytopia node then send a message to the ITN, and the ITN's job again is only to create DIT and anchor them onto blockchain. So then ask the ITN, please create a DIT for this battery. The ITN creates it, deposit it onto blockchain, then sending the message back to the Cytopia node and say, hey, this is the DIT you requested. Cytopia then send that message back to the battery manufacturer SSDT and give it to it. Then the manufacturer SSDT will send the DIT to the battery SSDT and now the battery has that store in the battery. The second thing is the battery birth certificate. The battery birth certificate is just like yours and my birth certificate is static information. It's kind of boring, you know. Where were you born? Which hospital? How big were you? Who were your parents? But those are all needed to be able to trace back to the manufacturer. It's the whole lifetime of it. How many auto credentials that they received as the important thing. So then they create the battery birth certificate with all the data scheme items required. And this is a Moby standard. So earlier, I forgot, I'm sorry, who asked me about which standard you decide. So we use W3C standard for this implementation of the ecosystem. But within the business processes, we have members sit down and walk through what would a battery birth certificate look like, what kind of information should be in there. And so this is that standard, a Moby standard that we use. So once the battery birth certificate as a verifiable credential has been created, then it gets sent to the battery SSDT and deposit in there as well. So now the battery has the DIT and the battery birth certificate. Let's say an OEM come along, let's say BMW comes along and say, I need to install this battery in my vehicle. How do I verify that this battery has that history and the passport that's required? And how do I authenticate it? So then BMW will send a message to the battery SSDT and say, hey, can you give me your credentials so I can verify you? The battery present the DIT, the battery birth certificate, instead of trusting the battery, you need to verify and validate it in this zero trust ecosystem. Then BMW will send a message to Zootopia and say, hey, can you verify this for me, please? Zootopia send a message to the ITN to verify it. Make sure the digits and signatures are correct. The ITN said, yep, you save, you can proceed. Zootopia node then send a message back to BMW and say, you can proceed, battery saved, install it. And then let's say we in a shared economy and a couple of automakers have agreement to use the same battery and let's say Daimler came along and used the same battery and they need to install it now. They can do the same authentication messaging again. And so in our ecosystem, this is how we verify and validate all the transaction without having to really pass messages, I mean, passing data, you pass a verification. Any questions on this before I move on to the next or the last slide? Is this already being used and so by how many companies and approximately how many BBCs have been issued and have any of the companies given feedback on the impacts it's had to their operations? So we are in the pilot trial right now. It's recently we've had two major OEM major vehicle manufacturers that did this pilot. And this is pretty historic because usually they don't speak to each other. And for them to be able to sit down and do this pilot and finish this, it was pretty fantastic. And now we are having more of our members joining this pilot. So it's going to take a little time. But as you know, R&D takes a little while. We can't use it right away yet. So any other questions on this? One question I had was, this follows along, I just keep the hyperlinker thing, but when you ask for verification, it just gives back a, it doesn't give back data does, it just gives back a verifier, I don't know if it's a hash signature. It doesn't really, it doesn't have to give out all this information just gives an okay. Correct. And the next slide I have another example with some code in it as well, which I don't know how to code, but I can show it to you. Any other questions on this slide? Daniela, I see a hand up. I don't know this old or new. I think that's been up for a while. I'm not sure. Yeah, I think that's been up for a little while. Okay. All right. Let me go to the next slide. So this is an example of a zero knowledge proof that we've been looking on. So one another pilot which is recently completed is called the dealer floor plan audit. For those of you who don't know, there are dealerships that sells vehicles, right? And those dealerships, they don't buy the vehicles with their own money. Maybe the little ones do, but the really big ones that have hundreds of vehicles, they have a bank that they work with and the bank lend them money to pay the auto manufacturer to purchase these these cars. So then the bank wants to make sure the cars are still on the lot and not sold yet because under the agreement, when you sell a vehicle, you have to return the money immediately so the bank can use that money for something else and make more money. But there are a few dealerships that don't disclose right away that they have sold the vehicle so that they can keep the money in their book in the bank and do some something else with it. So the lenders need to go physically right now onto the dealership lot. Somebody with a paperclip and they hand and check out the vehicle. And it's a really labor-intensive process and it's a slow process and you can't do it, you know, all the time, right? So according to Accenture, if you can automate this process within the U.S. alone, you can save four to five hundred million dollars a year. So it's a big problem. We did the pilot on how do you verify that the vehicles are on the lot when we know that location is PIR. You can't store location. So what we did for this pilot was that we used zero knowledge proof service offered by Zootopia inside a verifiable credential. So let's say you are the lender, the bank. You have an SSDT and then you ping the vehicle SSDT to ask the vehicle, are you in this geofence location? And the geofence location is the dealership. And then the vehicle then would answer back, would approve, let's say yes or no in this location or not. And if they say yes, fantastic. If the vehicle say no, I'm not in that geofence location, that means it's out, it's been driven around, it could be driven around by a customer and you don't want to know. That's PII. So let's say you ping, the lender ping the vehicle once an hour for 24 hours straight for three days straight or continuously all the time while the vehicle is not being sold yet. And if the answer is mostly yes, unless once in a while it goes out for a test drive or in the service department, then that's fine. But if it's saying no a lot, especially 3 a.m. in the morning and if it's 3 a.m. in the morning, everybody's sleeping if the vehicle is not in the maybe there's an issue. So then the lender needs to have a procedure on how to follow up on this. So as I mentioned, VIN number is PII, location is PII, how do you do this proof without storing that? So the proof that the vehicle sent back first, the input into the zero-knowledge proof, you have the VIN number here, you have the latitude, you have the longitude, and this is the approved latitude and longitude, which means this is the geofence location of the dealership. And then it goes through the zero-knowledge proof. And as you can see, when it sent back a verifiable credential would approve, there's no clear text of the VIN number or the location. And that's how we also do data privacy in a verifiable credential as well. Any questions on that? Yeah, just one. So that JSON file you've got over here, is that format coming off of some standard or is there some way that another system can retrieve that format to understand what they need to, but JSON format they need to send over to the credential, the verification? So let me see if I got your question correctly, because I'm not a technologist, so you might have to send a question later, and I send it to our tech team. So this will be a somewhat of a standard for Mobi members. And then we also, this is a service of Cetopia, so the zero-knowledge proof services is a service that Cetopia will offer to members so that they can do the extra layer of data privacy as well. Okay. Any other questions? Okay. And this is my last slide. We are doing many pilots with our members and these pilots, we are not building these products. This is just to demonstrate the infrastructure, Cetopia and the ITN to our members so that they see it, they see how to use it, and then they need to go in and run a node on the ITN, they need to run a node in Cetopia, and then they need to build the application on top of Cetopia. So we have been tracked, essentially they are Cetopia, they all track and trace and either track a vehicle. And then once you do registration and titling a vehicle, you can do other things like floor plan audit, which I just mentioned. You can use road usage charge, which is a big conversation right now going on. And vehicle repair maintenance tracking and mission tracking, we did that pilot with the EU Commission, JRC, last year. They want to see the vehicle can self-report a mission. And then you have usage-based insurance you can build on top and many, many more use cases. These are just the ones that our members said are important and we're working on them. And of course, the battery passport, we're working with our members on the standards for that and how to report it out using a decentralized method. And next week, we're pushing out a standard actually on the guideline on how to create a battery, global battery passport in a decentralized implementation ecosystem. And then we have one that's mass multimodal so that the user can plan, reserve and pay for a multimodal trip on one place, instead of having many apps and platforms. So I will stop here, seeing any questions. Thank you, Tram. This has been great. For that last, if you could go back to that last slide, the pilot you mentioned with the EU on emissions tracking, have there been any results on that yet? Yes, we have a report. Let me see. I can go on to a website and deposit this here. Great. Yes, let me see. Too many screen now, let me. And the pilot is, so if you go to this link, here's where's the report? Let me link it real quick. Okay, here is the page for it. And then go directly to the report, if you scroll down on the page, you can see the icon for the report. I see it. Perfect. Thank you so much. And this is a report written by JRC. Okay. Oh, excellent. Thank you. This looks like a really good resource. A lot of details. Yeah. Including hyperledger fabric. I see hyperledger fabric down under section four. Any other questions? Yeah, Tram, this is Tom Klein. Thank you very much for sharing the overall picture of Moby. Good stuff. And I got the picture of standards plus web three infrastructures where you guys are focusing. So the question is around governance. And how does it work? What do you get for your money if you join? Right? And how do you get to have your influence or decisions made? Those kind of things. Since one of my intentions is blockchain, one of the reasons why things have not taken up quite as fast is how do you get people to work together? Right? So it'd be interesting to hear your experiences on, you know, here's some things that we tried that didn't work and here's some things that have worked here. Here's what we're not sure about still. Yes. So let me see if I can like think of everything. It doesn't need to be everything. Yeah, in the past five years, but essentially moving Moby, we are a democracy, we have a voting system, but it's only a democracy if you actually show up and vote, right? If you don't show up and vote, then you can't complain. And so that's how we choose, you know, the use cases and all that. And then if you decide to run a node on the ITN as a topia, which we recommend, so don't just use the service, you actually run the node, then you can make money later on when we're in production. So within them, we would have two types of shareholders. The class A shares are the node operators and they are the governance body of the networks, the two networks. And they get to vote, they get to decide, they get to do all that. And they also have a board of directors and be able to hire an executive team. And then the B shares are the ones that get dividends. If there is, of course, any revenue, any gains, the B shares will get dividends. And those don't get to participate in the governance unless they also run a node. And the one major vote that they get to do is if all the class A shares decided to say that, okay, we're just going to give only ourself all the money and the B shares forget about it, then they can rise up and revolt and say, no, you can't do that. So within Mobi membership, you can run a node and have an A share. And then you can also get incentive to come in early as an early adopter, you get a little bit of the B share as well. And that your VC arm decide to also invest more than you get more of the B share. And then outside investor gets it as well. Okay, good. Yes, what you're saying here is democracy is basically a voting system modeled on democracy here, I have class A and class B shares here, one, you got to be a node operator to be a class A, and then you can participate in the governance and be your kind of a passive party here, if you're class B. Okay, got it. Yeah. And then education I find is extremely important. So essentially, this is a new way of doing things. And you need to learn the language. So before you can write poetry, all that, you need to learn the alphabet. And we see that at first, we say, okay, here is the direction and how to run a node. And we heard crickets, maybe one or two companies and get it. So now this year has been about education to our members, about what did VCR and then walk through the code. And even like walk through the dip diagram and explain if you are the battery, then you're the subject, who's the bit controller, how you pass it on, how do you change things. So all that needs a lot of education to be able to explain this whole new way of doing things. And I think that's really important in any consortium is education to be able to produce these kind of classes so our members get it. And then the tech team can get it. And then you need the business people and the tech people to have the same language. Because the business people can get excited. And then they go back to their team and say to the tech team, oh, can you do this? And the tech team will be what? And vice versa. So you can teach the tech team the language as well. Then they consult the business people, hey, you want to do this. There's a way to do this now that we couldn't do before. So they really do need to be on the same page as well. How incentivize are people to, actually, like you said, you need to show up to vote, right? Are you finding that I need to give them extra incentives or just by them paying, hey, they're motivated enough or I mean, there's always the politics, somebody might sponsor it and say, you know, they got moved on to a different part of the organization and then some of the momentum gets lost there. So interested in what you've done about that. Yes, I totally agree. Moby's been around for five years. We launched in May. And so there were the early adopters and now there's a current adopter, which is later than them. And how do you keep them all engaged? That is the hard part, I agree. Because early adopter might get frustrated and say, doesn't get too slow. And then later adopters don't know the language yet. So this is like we constantly having to educate and having to get the ecosystem come in and do pilots. Recently, as I mentioned, there's two auto manufacturers that did a pilot and it was exciting for the ecosystem to see. So now more people want to do it. And so it's constant. It's a little bit exhausting, to be honest. But, you know, I have to say, as long as I feel like I'm learning something new every day, which I do, then I can wake up the next day, even though the day before I was exhausted and say, forget it. So it's a constant thing. And I'm seeing the light at the end of the tunnel. I'm hoping it won't take five more years. But it's a slow process to move all the industry players along. And I think the reason why crypto, you know, it moved fast is because they're not really industry, right? They individual organization that can make decisions really fast. They all started a startup not too long ago. Industry are much slower. They're much more conservative. They have rules, regulation, the const department can stop anything. The legal department can stop anything if they don't understand it. So it takes a lot of education to move them. But the most important thing is government buy-in. From the beginning, I've always said if we can think of what we're doing so cool, government doesn't buy in on it. It's not going to go very far. And there's a reason why crypto is still in the billion dollar industry. And then other organization within Moby coming together is a multi trillion dollar industry. It's because you need standards, you need government buy-in, you need structure on how to do things. And then everybody need to agree on that before we can move forward. Good. Thank you. It's very, very helpful. So you have just one question on your business model. So if I'm a Moby customer, do I pay a license over some time or do I pay for transactions, some small fraction? So they're not going to be Moby customer because Cytopia and ITN are separate. I'm hoping in a year or so, they will become their own entities. And then Moby will continue to do the data standard for other use cases. And then Cytopia and ITN business model is really simple. API call charges and that's it. Okay. Does anyone else here have any other questions right now? I want to be mindful of time. It is 1258. So I don't hear in eastern time zone. Tram, this has been very illuminating. You have grown so much as a company since the last time I saw you present. The amount of work you've gotten done is really impressive. And so many different pilots. It seems so slow, but thank you for saying that. Because I think the last time when you came in to speak to the social impact stick, I believe that was summer of 2020. Oh, okay. And what I remember from that mainly was the battery passport. And now talking about the Vintrack and the different pilots there and Cytopia Mass, you have gotten so much done on this time. And it's really exciting to see the amount of partnerships you've been able to create and the standards you're developing. So I want to really thank you for coming and sharing this with us. Yes, it was excellent. Thank you. That's it. Does anyone have any last minute questions? Okay. Tram, will you be able to share your deck with the group? Let me look through it. Is that okay? And then I can put watermark or something on it and then send it to you. If you send it to me and let me know if I can share it, then I can share it. Then I can send it out with the group and also post it to the agenda for this meeting. Thank you. Great. Thank you so much. With that said, I'm going to let everybody go. Our next meeting is on June 29th. Same time, same place. And we'll be doing more work on the e-book. Bye. That was good. Thank you so much, Tram. And to everybody else. Hey, everybody. Thank you, Tram. Have a great day. Bye-bye.