OORT资源站

[02:19.000 -> 02:42.000] Good morning, everyone.
[02:42.000 -> 02:46.200] We're excited to have you join us in this thrilling Twitter space today.
[02:46.200 -> 02:49.800] I'm your host, Tyler, and I'm part of the BD team.
[02:49.800 -> 02:56.080] Some of you may recognize me from some of the earlier Twitter conversations we've had.
[02:56.080 -> 02:57.460] We’ve had.
[02:57.460 -> 03:00.800] Today, we have some super exciting things to share.
[03:00.800 -> 03:05.000] We're honored to have our CEO, Dr. Max Lee, with us,
[03:05.000 -> 03:12.000] who will share some groundbreaking insights and the latest innovations in our tech stack, TDS,
[03:12.000 -> 03:15.000] as well as some updates on DSS.
[03:15.000 -> 03:23.000] But before we dive into those details, let me quickly outline the agenda we've set and what you can expect.
[03:23.000 -> 03:25.600] So today, it will be filled with
[03:25.600 -> 03:30.120] a lot of information, so if you can fully focus on Dr. Lee,
[03:30.120 -> 03:35.800] we would really love to have a good Q&A session after the meeting. So first, Dr.
[03:35.800 -> 03:40.960] Lee will provide us with some customer acquisition statistics
[03:40.960 -> 03:47.760] for DSS and TDS. Then we will look at some revenue forecasts
[03:47.760 -> 03:52.880] to better understand the growth prospects
[03:52.880 -> 03:54.920] we have ahead of us, what we really are,
[03:54.920 -> 03:56.880] and take a look at our roadmap.
[03:56.880 -> 03:59.640] Finally, the highlight of the event,
[03:59.640 -> 04:03.680] Dr. Lee will introduce the revolutionary TDS product,
[04:03.680 -> 04:05.400] discuss some of its key features,
[04:05.400 -> 04:10.640] our target audience, go-to-market strategy, and more.
[04:10.640 -> 04:16.920] So before I hand the mic over to Dr. Lee, let’s not forget why we are here today.
[04:16.920 -> 04:27.300] OORT TDS is a platform designed specifically for building generative AI agents, allowing businesses to seamlessly integrate factual information,
[04:27.960 -> 04:29.840] indeed accurate information.
[04:29.840 -> 04:31.840] It is versatile and secure,
[04:32.320 -> 04:39.600] enabling their current operations in minutes rather than months, and the best part is no coding or AI
[04:39.920 -> 04:41.600] expertise is required.
[04:41.600 -> 04:46.600] So just a final reminder that after Dr. Lee's presentation, I will be
[04:46.600 -> 04:50.760] welcoming questions. If you have any pressing questions about our products,
[04:50.760 -> 04:54.920] the industry, or anything relevant, please feel free to put them in
[04:54.920 -> 04:59.800] the chat, and I will select some for Dr. Lee to answer. So Dr. Lee, if you could
[04:59.800 -> 05:06.720] quickly introduce yourself, and then we can get started.
[05:10.200 -> 05:11.200] Okay, thank you for the warm introduction, Tyler. Can you all hear me?
[05:12.400 -> 05:13.800] Yes.
[05:13.800 -> 05:14.640] Others?
[05:14.640 -> 05:15.840] Okay, perfect.
[05:15.840 -> 05:18.320] Yes, my name is Matt Lee.
[05:18.320 -> 05:20.320] I am the founder and CEO of OORT.
[05:20.320 -> 05:24.960] I am currently responsible for all product development
[05:24.960 -> 05:27.880] and technology development.
[05:27.880 -> 05:37.760] So I think we also have Mike Robinson, the chairman of the OORT Foundation, here in the
[05:37.760 -> 05:38.760] Twitter space.
[05:38.760 -> 05:47.080] If anyone has questions related to crypto,
[05:47.080 -> 05:52.120] Mike will be more than happy to answer those at the end of this Twitter space.
[05:53.400 -> 05:57.680] So I haven't had a chance to talk to the committee members for a long time,
[05:58.480 -> 06:04.520] because, you know, our crazy days have been focused on product development.
[06:04.840 -> 06:05.000] Basically, committee members, you can see that in the past few months, during our crazy days, we have been laser-focused on product development.
[06:05.000 -> 06:06.520] Basically, community members,
[06:06.520 -> 06:09.640] you can see that in the past few months,
[06:09.640 -> 06:13.200] we have developed some outstanding products in this field.
[06:14.080 -> 06:17.800] As I said, the organization is completely different
[06:17.800 -> 06:21.120] from other crypto or Web 3 projects.
[06:21.120 -> 06:24.200] We are very, very focused on technology
[06:24.200 -> 06:26.560] and product. We are a tech company
[06:26.560 -> 06:39.040] driving the project. So not. So our goal is to provide the best products in the world in the Web 3 space.
[06:39.040 -> 06:45.000] We are also very revenue-focused.
[06:45.000 -> 06:47.560] I think revenue is, you know,
[06:47.560 -> 06:51.720] when you talk about a business, of course, revenue is the way to go.
[06:51.720 -> 06:54.160] I don’t like to talk about projects
[06:54.160 -> 06:56.320] that have no revenue.
[06:57.800 -> 07:02.240] First, focusing on today’s Twitter space agenda,
[07:02.240 -> 07:08.800] I first want to share some results, I would say good results,
[07:09.360 -> 07:17.440] from our products. So currently, we have launched two key products, or what we call flagship products,
[07:18.960 -> 07:25.000] OORT. The first is DSS, which we launched in late March 2023.
[07:27.520 -> 07:31.040] DSS stands for Decentralized Storage Service,
[07:31.040 -> 07:36.040] which is an alternative solution to Amazon S3 storage.
[07:36.080 -> 07:39.540] I’m sure you all know
[07:39.540 -> 07:43.040] there are many decentralized storage projects
[07:43.040 -> 07:45.340] out there that have been around for many years,
[07:45.340 -> 07:49.440] such as Filecoin, StorageJ, Arwave,
[07:49.440 -> 07:51.820] but unfortunately, none of them can
[07:51.820 -> 07:55.200] serve as an alternative solution to Amazon S3.
[07:56.160 -> 08:00.160] So OORT is using Amazon as a benchmark,
[08:00.160 -> 08:04.240] and we are trying to provide a better solution
[08:04.240 -> 08:08.560] that surpasses Amazon AWS S3 storage solutions.
[08:08.560 -> 08:15.840] This means we can achieve the same performance as Amazon but at a much lower cost
[08:15.840 -> 08:20.560] and guarantee privacy because we are decentralized. But you know this,
[08:20.560 -> 08:28.800] you know, if we want to provide the exact same performance as Amazon Cloud S3 but all in a
[08:28.800 -> 08:31.480] decentralized manner, that’s quite challenging.
[08:31.480 -> 08:36.320] Our tech team is working day and night to achieve this.
[08:36.320 -> 08:48.000] Now, I’m excited to share with you that we have done it, and since our launch six months ago, we have secured
[08:48.000 -> 08:59.120] nearly 3,000 businesses and individual users registered and using our DSS. And they are continuously uploading
[08:59.760 -> 09:08.680] data transfers to DSS. So, we support various data types, code data, hot data, unstructured data,
[09:08.680 -> 09:12.920] structured data, or semi-structured data. We support all types of data,
[09:12.920 -> 09:21.040] just like Amazon. But if you look at all other data storage solutions,
[09:21.040 -> 09:26.080] they may only focus on one type of data. For example, just like Filecoin is good for code data,
[09:26.800 -> 09:32.000] for data archiving, but does not support hot data. Hot data means if you want to do
[09:32.000 -> 09:39.200] video streaming, or you want to run a real-time messaging application on Filecoin, it’s quite
[09:39.200 -> 09:46.780] difficult. They need to do more work to achieve that. So, we have supported all DSS.
[09:46.780 -> 09:50.220] We can host, you can host games, mini-games.
[09:50.220 -> 09:53.260] You can host, you can do video streaming,
[09:53.260 -> 09:55.420] you can upload and download photos
[09:55.420 -> 09:58.620] in real-time on demand.
[09:58.620 -> 10:01.180] Of course, you can also do archiving.
[10:01.180 -> 10:08.000] Compared to Amazon S3, we can save you up to 60% in costs.
[10:08.000 -> 10:18.000] So this is the foundation for the organization to support various applications.
[10:18.000 -> 10:28.360] The second key product we launched a few weeks ago is even more significant.
[10:28.360 -> 10:31.440] So this is a more service-related product.
[10:31.440 -> 10:35.240] We call it PDS, which stands for Call Data Service.
[10:35.240 -> 10:48.160] In fact, earlier this April, when I was giving a speech in Hong Kong, I basically showcased a demo of TDS at that time. Now we have successfully launched TDS. So the good news is
[10:55.800 -> 11:02.480] we just ensured security, you know, we just launched a few weeks ago, and we have already secured
[11:02.480 -> 11:05.640] a group of enterprise clients.
[11:06.080 -> 11:10.240] The first announcement we have made is Lenovo Image.
[11:10.600 -> 11:16.040] So Lenovo, I’m sure everyone knows this company, and they have been
[11:16.040 -> 11:24.200] using TDS to enhance their current customer service alternative solution.
[11:24.280 -> 11:26.480] Customer service system.
[11:26.480 -> 11:31.680] Now if you open the Lenovo app or their WeChat mini-program,
[11:31.680 -> 11:35.040] you will see there is a chatbot,
[11:35.040 -> 11:42.080] and the backend chatbot is powered by our TDS product,
[11:42.080 -> 11:44.480] which is our TDS service solution.
[11:44.480 -> 11:48.880] So far, it has been running well. We launched
[11:48.880 -> 12:01.760] the collaboration with Lenovo for about a week now. So far, the active users of the chatbot are increasing
[12:01.760 -> 12:11.640] every day. Now, I think Lenovo shared data with us a few days ago, and there are already
[12:11.640 -> 12:29.360] over 1,000 active users daily asking questions about customer service to help them resolve issues, and our bot has successfully helped them with many issues
[12:29.920 -> 12:34.640] using their Lenovo printers and similar things.
[12:34.640 -> 12:38.160] So every day, you have over 1,000 active users
[12:38.160 -> 12:40.340] and this number is increasing daily.
[12:41.720 -> 12:48.760] Overall, although we just launched a few weeks ago, our user base has exceeded 11 million characters
[12:48.760 -> 12:56.880] that have been trained using the organizational infrastructure in TDS.
[12:56.880 -> 13:07.640] This means customers can upload data to TDS, and then they will use our underlying
[13:07.640 -> 13:13.720] organizational cloud to train models, fine-tune models, and then, you know, just like that,
[13:13.720 -> 13:18.920] automatically. You don’t have to be an AI expert to do this. No coding is required.
[13:18.920 -> 13:34.000] This is a wonderful part of our product, and I will introduce more features of the TDS product later. So it is very easy to use. Now we have over 11 million characters
[13:34.000 -> 13:40.880] uploaded to TDS. And this data is automatically stored in DSS. You see what I
[13:40.880 -> 13:48.880] mean, right? So it’s like we provide this AI solution. And on the backend, we don’t use, like Alibaba Cloud,
[13:48.880 -> 13:51.320] Tencent Cloud, or Amazon or anything
[13:51.320 -> 13:53.600] as our cloud service provider to train models
[13:53.600 -> 13:57.000] or fine-tune models or store your uploaded data.
[13:57.000 -> 14:01.600] We use our own cloud, DSS and DCS.
[14:01.600 -> 14:04.520] DSS, storage, decentralized storage service
[14:04.520 -> 14:06.240] and DCS. DSS, decentralized storage service, DCS is coming soon,
[14:06.240 -> 14:13.200] later this year or early next year, decentralized computing service for AI
[14:13.200 -> 14:27.800] training. This is some statistics I want to share with you to showcase the success our product has achieved so far. The second thing I want to share is about ReMU.
[14:29.000 -> 14:32.440] So this is a very confidential matter, I want to say,
[14:32.440 -> 14:36.960] but I want to share with the community the ReMU projection
[14:37.960 -> 14:41.520] to let you know how well we have done so far.
[14:41.520 -> 14:44.640] I know, given the current market, it’s bad.
[14:44.640 -> 14:45.320] I mean, the market
[14:45.320 -> 14:54.480] is terrible globally, right? In the US, China, Brazil, everywhere. The market is bad.
[14:54.480 -> 15:10.640] Financial conditions are poor. But so far we have done well. We are still maintaining our revenue forecast for this year, which is 3.7 million dollars
[15:10.640 -> 15:17.280] I want to say is the revenue forecast for this year. Next year, we expect more because
[15:17.280 -> 15:23.040] our products have become, are evolving and becoming more mature. We continue to onboard
[15:26.080 -> 15:27.080] and become more mature, and we are continuously attracting a large number of new customers, paying customers.
[15:27.080 -> 15:34.040] So for next year 2024, our revenue forecast is 7.1 million dollars.
[15:34.040 -> 15:41.360] So if everything goes well, we are very confident to achieve this revenue.
[15:41.360 -> 15:50.000] So with such strong revenue, you can imagine how powerful this project will be, especially in this terrible market.
[15:50.000 -> 16:10.320] I know community members you can make money through charging
[16:10.320 -> 16:18.960] transaction fees. All other Web3 projects, I don’t know. So
[16:18.960 -> 16:25.240] so far, maybe I missed something, but as far as I know, I haven’t seen any
[16:25.240 -> 16:33.200] projects that truly protect paying customers and generate millions of dollars in revenue
every year [16:33.200 -> 16:34.200].
[16:34.200 -> 16:39.040] But the world has changed completely, and that’s basically our focus.
[16:39.040 -> 16:45.000] So far, we are working towards that line and doing well.
[16:47.720 -> 16:52.720] Okay, the last part is I want to talk more
[16:54.000 -> 16:58.040] about TDS because this is the AI solution
[16:58.040 -> 17:01.120] we are promoting these days.
[17:02.440 -> 17:09.120] I can tell you that because I work at Columbia University,
[17:09.120 -> 17:17.600] yes, so I have been working in the AI field for many, many years. This is the technology
[17:17.600 -> 17:26.800] we have been leading in this field. So while we are not a pure AI company, this AI product is already leading,
[17:27.840 -> 17:37.760] in the AI industry. We have some well-known AI solutions in the market,
[17:37.760 -> 17:49.180] such as Cloudy.ai, ChatGPT, and GPT-? So we have many, many AI projects,
[17:49.180 -> 17:51.500] but it’s easy to compare,
[17:51.500 -> 17:54.020] you can, I usually do this.
[17:55.060 -> 17:59.640] I upload the same document to cloudy.ai, for example,
[17:59.640 -> 18:01.960] and TDS.
[18:01.960 -> 18:05.400] I just ask them the same question.
[18:05.400 -> 18:09.760] TDS always gives a better response
[18:09.760 -> 18:12.680] compared to cloud AI.
[18:12.680 -> 18:15.480] So this is the very core technology at the backend.
[18:16.840 -> 18:20.960] This is our technological advantage,
[18:20.960 -> 18:22.240] technological advantage.
[18:22.240 -> 18:24.840] This is why we are becoming the leading space.
[18:24.840 -> 18:28.760] Next, I want to introduce three key features
of our TDS product [18:28.760 -> 18:30.600].
[18:31.920 -> 18:33.560] These are the differentiating factors
[18:33.560 -> 18:35.720] from all other AI solutions.
[18:35.720 -> 18:39.400] Please remember that our own AI solution is running
[18:39.400 -> 18:43.160] on our own cloud, Word Data Cloud.
[18:43.160 -> 18:45.240] This is another key distinction
[18:45.240 -> 18:47.220] from all other AI projects.
[18:47.220 -> 18:50.080] Because for all other AI projects,
[18:50.080 -> 18:52.120] they are running their AI solutions
[18:52.120 -> 18:55.720] on traditional aspects, on traditional cloud service providers.
[18:55.720 -> 18:59.840] For example, AWS, Google Cloud, or Microsoft, right?
[18:59.840 -> 19:02.980] Or Alibaba Cloud, for example.
[19:02.980 -> 19:07.960] But we are running our TDS AI solution on OORT Cloud,
[19:08.480 -> 19:10.000] our own cloud.
[19:10.000 -> 19:11.520] Why choose OORT Cloud?
[19:11.520 -> 19:16.520] Because OORT Cloud offers two key features,
[19:16.760 -> 19:19.000] one is low cost.
[19:19.000 -> 19:24.000] As I said, we can save up to 60%, 60, 60%
[19:24.380 -> 19:25.000] compared to all other
[19:25.760 -> 19:28.860] traditional cloud service providers,
[19:28.860 -> 19:33.400] and privacy, because everything here,
[19:33.400 -> 19:37.720] whether it’s data storage or data processing,
[19:37.720 -> 19:39.680] is decentralized.
[19:39.680 -> 19:43.780] It is controlled by the end user, not by us.
[19:43.780 -> 19:47.360] So we cannot change the data. We cannot delay, cancel,
[19:47.360 -> 19:57.040] or manipulate your data. Only you, as the end user, own the data.
[19:57.040 -> 20:02.240] You can do data storage, data processing, you can operate to delete your data,
[20:02.240 -> 20:06.240] add more data. This is your own power, not ours.
[20:06.240 -> 20:08.520] Okay, so this is completely different.
[20:08.520 -> 20:15.680] This is why we let this AI solution run on our own data cloud, essentially we have
[20:15.680 -> 20:19.080] these beautiful features.
[20:19.080 -> 20:27.840] Now back to the TDS AI product, we have three key features. I think these are key differentiating factors
[20:27.840 -> 20:30.100] from all other AI solutions.
[20:31.160 -> 20:34.760] Besides the underlying cloud service provider.
[20:34.760 -> 20:38.440] Okay, the first feature is factual accuracy.
[20:39.700 -> 20:41.500] What does factual accuracy mean?
[20:41.500 -> 20:44.560] It means if you want to have a conversation with Track GPT,
[20:44.560 -> 20:51.680] yes, for example, you want to get some responses that should be very accurate. This is not like
[20:52.400 -> 20:57.840] some rather random information or some false information, right? So this is a big issue
for Chat GPT [20:57.840 -> 21:12.720]. My personal experience with Chat GPT is that I asked TryGPT to tell me some recent academic achievements
about AI or IoT or papers like that.
[21:18.960 -> 21:25.960] TryGPT can give you some paper links with the paper titles and authors.
[21:25.960 -> 21:27.560] But they are all fake.
[21:27.560 -> 21:34.260] When I went to Google Scholar to check those papers, they don’t even exist.
[21:34.260 -> 21:35.920] So that’s crazy.
[21:35.920 -> 21:42.200] That’s why if you, maybe some of you have seen the news about Chat GPT daily
[21:42.200 -> 21:45.000] active users decreasing.
[21:45.700 -> 21:47.680] They are now fundraising.
[21:47.680 -> 21:49.340] If they don’t have new money,
[21:49.340 -> 21:51.680] new funding to look at this project,
[21:51.680 -> 21:53.800] OpenAI will go bankrupt
[21:53.800 -> 21:55.960] by the end of 2024.
[21:55.960 -> 22:00.080] So they can only survive for another year, right?
[22:00.080 -> 22:02.640] So now we only use TrackGPT.
[22:02.640 -> 22:04.280] What’s the reason?
[22:04.280 -> 22:07.680] Because why is TrackGPT losing users?
[22:07.680 -> 22:10.440] It’s all because of factual accuracy.
[22:10.440 -> 22:12.960] Because they cannot provide Chat GPT,
[22:12.960 -> 22:17.360] cannot give responses in a very accurate way.
[22:17.360 -> 22:22.080] So users only find Chat GPT useful
[22:22.080 -> 22:24.800] in very narrow areas.
[22:24.800 -> 22:29.040] For example, I just use ChatGPT to help me write some emails,
[22:29.040 -> 22:31.480] write some blogs, write some articles,
[22:31.480 -> 22:35.760] and then I do my own work
[22:35.760 -> 22:38.520] to ensure that every word in this email,
[22:38.520 -> 22:41.200] this article makes sense, right?
[22:41.200 -> 22:44.120] So this is the only thing ChatGPT can do right now.
[22:44.120 -> 22:54.560] So it cannot be applied to industries, manufacturing, autonomous driving, or even legal or anything else.
[22:54.560 -> 23:02.880] Because all these other industries, they need very accurate information in their responses.
[23:02.880 -> 23:05.320] But writing is no problem, right, just writing emails
[23:05.360 -> 23:09.120] if you are not accurate, it’s okay, I can still use it
[23:09.120 -> 23:12.760] because I can do a sanity check. Right. So factories
[23:12.760 -> 23:18.080] accuracy is, but TDS can provide you factory accuracy. So we will
[23:18.120 -> 23:23.440] encourage the bot models to say, sorry, I don’t know if you
[23:23.440 -> 23:25.720] don’t know, just say I don’t know. If you don’t know, just say, I don’t know.
[23:25.720 -> 23:29.640] But when you talk to GPT, GPT will never say, I don’t know.
[23:29.640 -> 23:32.840] No matter what you ask, they will give you something.
[23:32.840 -> 23:36.560] But unfortunately, this response is not accurate
[23:36.560 -> 23:39.320] or even fake, okay?
[23:39.320 -> 23:44.020] The second feature is multi-model.
[23:46.280 -> 23:49.300] Maybe some of you have tried our product.
[23:49.300 -> 23:54.960] So it can show you text and images, graphics in the responses.
[23:54.960 -> 24:00.280] Our tech and research team has tried the demo.
[24:00.280 -> 24:05.080] It’s not released yet, but internally we have also supported video.
[24:05.080 -> 24:07.640] And audio, video, and audio.
[24:08.760 -> 24:10.960] This is what’s on the roadmap.
[24:10.960 -> 24:11.920] What does this mean?
[24:11.920 -> 24:16.320] This means when you ask a question, you can
[24:16.320 -> 24:21.320] send it to TDS, and you can get responses in multiple formats.
[24:23.360 -> 24:27.600] So text, images, and videos,
[24:27.600 -> 24:31.120] basically short videos and audio.
[24:31.120 -> 24:32.360] That’s really great,
[24:32.360 -> 24:35.480] because this will open up many applications.
[24:35.480 -> 24:39.260] For example, this is why we chose Lenovo as our customer,
[24:39.260 -> 24:43.960] because Lenovo, in the current Lenovo customer support,
[24:43.960 -> 24:46.640] but when you ask some questions,
[24:46.640 -> 24:50.200] for example, hey, my printer is jammed,
[24:50.200 -> 24:51.680] this is my printer model,
[24:51.680 -> 24:53.080] what should I do?
[24:53.080 -> 24:58.120] This Lenovo bot will not only give you text,
[24:58.120 -> 25:01.120] about step-by-step instructions,
[25:01.120 -> 25:04.960] what you should do, but it also comes with
[25:04.960 -> 25:07.000] these images showing you,
[25:07.000 -> 25:10.520] hey, here’s an image, you can see this is the paper,
[25:10.520 -> 25:13.100] the location where the paper is jammed.
[25:13.100 -> 25:17.720] You should pull up the tray and go in
[25:17.720 -> 25:20.380] and see if the paper is jammed there or something else.
[25:20.380 -> 25:22.520] There are images.
[25:22.520 -> 25:29.440] The user experience in the customer support field is much better.
[25:29.440 -> 25:35.280] This is why Lenovo is very satisfied with this and wants to help us promote our TDAD solution
[25:35.280 -> 25:43.800] for many other companies as well, especially in China, because Lenovo is a leading computer
[25:43.800 -> 25:47.000] basically a Chinese manufacturer.
[25:47.000 -> 25:52.000] This is the second feature, multi-model response.
[25:52.000 -> 25:55.000] The third is data analytics.
[25:55.000 -> 26:02.000] Data analytics means you deploy the bot, you create your bot, and then you deploy your bot,
[26:02.000 -> 26:05.880] and you ask users to use the bot.
[26:05.880 -> 26:11.440] But on the backend, you want to get very insightful information from customers.
[26:11.440 -> 26:18.280] For example, Lenovo really wants to know what the top ten questions their printers are asked
[26:18.280 -> 26:25.080] by owners in a day, like today, right?
[26:30.080 -> 26:30.940] Where do these customers come from,
[26:34.400 -> 26:39.240] from different cities, different provinces, right? They want to understand the geography of these customers.
[26:39.240 -> 26:42.520] And then they might think this data is very important.
[26:42.520 -> 26:45.920] This insightful data is very important for novels
[26:45.920 -> 26:48.840] to improve their products, quality,
[26:48.840 -> 26:51.000] and their products, distribution,
[26:51.000 -> 26:52.080] and their products,
[26:53.920 -> 26:56.840] which enhances the satisfaction of their products
[26:56.840 -> 26:58.440] from their customers, right?
[26:58.440 -> 27:00.720] Because they know what their customers really care about.
[27:02.360 -> 27:06.960] So this data analytics, like Google Analytics,
[27:06.960 -> 27:09.920] helps you understand customers
[27:09.920 -> 27:12.000] who visit your website, right?
[27:12.000 -> 27:15.960] So we will provide this data analytics on the backend
[27:15.960 -> 27:20.960] to let bot owners understand their customer behavior.
[27:23.320 -> 27:26.600] This will definitely help you a lot
[27:26.600 -> 27:30.640] improve the service provided to customers.
[27:30.640 -> 27:34.320] These three key features are very important, and
[27:34.320 -> 27:37.720] the key differences between DT
[27:37.720 -> 27:43.520] TDS and all other AI solutions in the world.
[27:44.080 -> 27:51.040] To be honest, I think TDS is now somewhat leading the industry.
[27:51.040 -> 27:58.640] At least from Lenovo's case, we see it currently in a quite leading position in the industry.
[27:58.640 -> 28:05.680] Our customer service, our current target sector is the customer support sector.
[28:05.680 -> 28:10.120] So we know our AI TDS is very powerful.
[28:10.120 -> 28:13.320] It can be applied to many industries.
[28:13.920 -> 28:15.640] For example, like customer support,
[28:16.920 -> 28:22.320] like human resources and IT departments, and personal assistants.
[28:22.320 -> 28:26.320] In fact, I use TDS to create my personal assistant
[28:26.320 -> 28:29.120] that we have been using internally.
[28:29.120 -> 28:33.200] So, you can talk to my AI assistant
[28:33.200 -> 28:36.900] to schedule meetings to gather information,
[28:36.900 -> 28:40.760] my personal information, just like my public information,
[28:40.760 -> 28:43.220] my profile picture or something like that.
[28:44.960 -> 28:49.000] So it can be used in many areas,
[28:49.000 -> 28:51.840] in many industries or fields,
[28:51.840 -> 28:55.800] but we now want to focus on customer support,
[28:55.800 -> 29:01.640] because I think this is the industry or sector,
[29:02.640 -> 29:07.000] that has a strong demand for this AI solution.
[29:07.000 -> 29:09.040] We can see that from Lenovo.
[29:09.040 -> 29:13.960] Companies like Lenovo have many.
[29:13.960 -> 29:18.840] So various companies, no matter what kind of company you are,
[29:18.840 -> 29:23.120] you need customer support to help you bring in leads,
[29:23.120 -> 29:24.760] help you answer questions
[29:24.760 -> 29:25.840] from your existing
[29:25.840 -> 29:29.060] customers, pre-sales and post-sales.
[29:29.060 -> 29:32.280] So you need customer support.
[29:32.280 -> 29:38.040] We now want to target this industry and quickly acquire paying customers and
[29:38.040 -> 29:40.840] generate stronger revenue.
[29:40.840 -> 29:41.840] That’s the key.
[29:41.840 -> 29:48.000] Currently, our go-to-market strategy is dual.
[29:48.000 -> 29:51.000] I want to share with you.
[29:51.000 -> 29:54.000] First is partnerships.
[29:54.000 -> 29:57.000] So we already have strong partners and customers,
[29:57.000 -> 30:03.000] who will also be our channels to reach other companies.
[30:03.000 -> 30:07.560] For example, we have a Dell computer, right?
[30:07.560 -> 30:14.440] So we have launched a loyalty program with Dell in Canada and the US,
[30:14.440 -> 30:20.920] and they will help us promote TDS to their ecosystem
[30:20.920 -> 30:27.040] projects as well. Keep in mind, Dell has over 10 million, from small to large
[30:27.040 -> 30:35.600] medium-sized companies in their ecosystem. This AI solution will be huge for both Dell and us.
[30:35.600 -> 30:41.120] I mean, then Tencent Cloud, our partner, Tencent has a marketplace,
[30:41.120 -> 30:49.120] he will promote TDS there through their... This space is downloaded through spacedown.com. Access your space now to download.
[30:49.840 -> 30:56.240] So this will come soon. There’s also Binance, Binance BNB chain and
[30:58.400 -> 31:06.380] it’s working very closely with us, and we have other Binance projects working with us, which will be announced
[31:06.380 -> 31:14.960] soon. This is another big thing for Binance, and it’s currently a focus for Binance. So
[31:14.960 -> 31:25.120] they have been working with us for over six months, and we have provided a lot of support for their tech development.
[31:25.520 -> 31:29.120] We will announce partnerships soon,
[31:29.960 -> 31:32.320] possibly later this month.
[31:32.320 -> 31:35.120] So online, no, Binance has
[31:36.240 -> 31:40.680] the largest ecosystem, I would say, one of the largest ecosystems
[31:40.680 -> 31:43.720] in the crypto space and all crypto projects,
[31:43.720 -> 31:45.840] they also need AI solutions, right?
[31:45.840 -> 31:50.720] And this underlying decentralized data cloud.
[31:50.720 -> 31:57.520] We do have some crypto projects in our ecosystem.
[31:57.520 -> 32:02.360] And Lenovo, you know, they are our customer, Lenovo will help us
[32:02.360 -> 32:07.160] also promote the product to other companies in China.
[32:07.160 -> 32:11.120] So this is an easily achievable goal for them.
[32:11.120 -> 32:17.920] We also have four other major partners, along with Dell, Lenovo, Binance, and
[32:17.920 -> 32:24.520] Tencent, but I cannot disclose their names right now because we have this business
[32:24.520 -> 32:26.640] agreeing on their viewpoints.
[32:26.640 -> 32:29.640] But we will announce them in the coming months,
[32:29.640 -> 32:31.380] maybe after the TGE.
[32:32.240 -> 32:35.400] So later this year, one by one,
[32:35.400 -> 32:40.400] we have four other very large partnerships
[32:40.820 -> 32:43.440] who can help us promote our products
[32:43.440 -> 32:45.200] into their ecosystems as well.
[32:45.400 -> 32:50.840] This will greatly help us generate revenue.
[32:51.040 -> 32:52.760] I would say
[32:52.960 -> 32:55.600] three of them are US companies.
[32:55.800 -> 32:59.680] One of them is a large company in China.
[32:59.880 -> 33:06.600] So another channel to market is our community, which is you.
[33:08.100 -> 33:17.060] So we, you know, we have crypto elements in this project, right?
[33:17.060 -> 33:23.420] So we want to, because we are a web3 project, we want to leverage our
[33:23.420 -> 33:27.380] community to co-build this project.
[33:27.380 -> 33:34.400] So we are the founding team, but we are not, I don’t want to say we are the only owners
of the project [33:34.400 -> 33:35.780].
[33:35.780 -> 33:39.680] So ultimately, we want to hand this project over to the community.
[33:39.680 -> 33:45.960] So we are just the founding team, just like the Etheron Foundation or Vitalik.
[33:45.960 -> 33:51.240] We build these things from the ground up and then hand them over to the community.
[33:51.240 -> 33:54.600] Now we also want to do this step by step.
[33:54.600 -> 34:02.160] So the first step, we really want our community to help us promote the product to different fields
[34:02.160 -> 34:06.080] industries or help us acquire paying customers.
[34:06.080 -> 34:11.200] Of course, we are internally developing incentive programs.
[34:11.200 -> 34:17.520] We will likely offer cryptocurrency, our native token or tokens,
[34:17.520 -> 34:25.000] as a reward for helping our community members
[34:25.800 -> 34:28.200] secure these paying customers, right?
[34:28.200 -> 34:31.600] So we are working on that now,
[34:31.600 -> 34:36.600] and we will announce this soon.
[34:38.840 -> 34:41.080] I think the community is very strong
[34:41.080 -> 34:43.120] and we want to leverage our community
[34:43.120 -> 34:46.160] to help promote our products
[34:46.160 -> 34:50.320] and make OORT achieve great success in the third universe.
[34:50.320 -> 34:53.160] I would say that’s all the information
[34:53.160 -> 34:55.720] I wanted to share with you today.
[34:55.720 -> 35:00.320] At the end of the speech, I want to reiterate,
[35:01.920 -> 35:04.080] emphasize one thing, say one thing,
[35:04.080 -> 35:06.920] I’ve said it several times before, I will
[35:06.920 -> 35:12.120] say OORT is very unique.
[35:12.120 -> 35:16.640] If you want to say in the crypto space or web3 space, whatever space you put OORT into, OORT is very unique because we are indeed technology-driven.
[35:25.560 -> 35:28.120] So we are not crypto-driven, right?
[35:28.120 -> 35:30.840] So this is completely different.
[35:30.840 -> 35:34.000] We want to provide truly good products
[35:34.000 -> 35:35.760] we are very unique.
[35:35.760 -> 35:38.920] Our products are very competitive
[35:38.920 -> 35:42.440] with all the tech companies in the world,
[35:42.440 -> 35:47.000] whether it’s Web 2 or Web 3 tech companies.
[35:47.000 -> 35:53.000] I mean, ChaiGBT and Cloudy AI, all these AI companies, they are Web 2 companies.
[35:53.000 -> 35:55.000] They don’t even know about cryptocurrency, right?
[35:55.000 -> 36:09.800] They have nothing to do with cryptocurrency, but we are still competing with them. Solutions that are better than these traditional Web 2 service providers.
[36:09.800 -> 36:17.760] But by leveraging Web 3 elements, because Web 3 has its own advantages
[36:17.760 -> 36:23.760] and benefits. It is decentralized, can be built by the community,
[36:23.760 -> 36:25.840] can be operated by the community, can be operated by the community.
[36:25.840 -> 36:28.320] The community is the key to success.
[36:28.320 -> 36:29.960] That’s what we see.
[36:29.960 -> 36:36.880] That’s why we want to run this project with a Web3 mindset, rather than like another Web2
[36:36.880 -> 36:37.880] company.
[36:37.880 -> 36:44.360] For the cryptocurrency part, you know why we focus on revenue?
[36:44.360 -> 36:47.140] Because revenue is key for any business.
[36:47.140 -> 36:52.640] If you don’t want to talk about revenue, you don’t need to run a business.
[36:52.640 -> 36:59.400] And revenue will also become the core of our cryptocurrency.
[36:59.400 -> 37:08.160] If you say it’s the native token, then now we want to use tokens like ORT. So what is the basis
[37:08.160 -> 37:16.500] or the intrinsic value of cryptocurrency prices? Although Mike can share more information about cryptocurrency
[37:16.500 -> 37:21.900] on one side, but I want to say this is why we focus on revenue because revenue will
[37:21.900 -> 37:25.840] be the intrinsic value of token prices. Otherwise, your
[37:25.840 -> 37:33.360] token price comes from where, right? You say the token price is 1 dollar, 0.10 dollars, 0.01 dollars, or 100 dollars. Where does this
[37:33.360 -> 37:40.400] number come from? It comes from the revenue of real business, right? So if you don’t have
[37:40.400 -> 37:47.680] revenue, you just keep telling stories, your token price won’t go up. So that’s the fact,
[37:47.760 -> 37:51.720] right? We can’t avoid that. That’s the fact. Then
[37:51.720 -> 37:56.120] it has happened many, many times in other projects
[37:56.120 -> 38:00.560] in history. So we want to create strong revenue. And
[38:00.560 -> 38:04.760] so this will be based on our token economics, which will be real
[38:04.760 -> 38:09.720] in the long run, beneficial to support our token price.
[38:09.720 -> 38:32.040] So since our revenue is increasing and you can predict it, you can expect the token price to become stronger over time. So this is a long-term business. And, you know, because we are a US entity,
[38:32.040 -> 38:42.200] our goal is not just cryptocurrency, our goal also includes going public on NASDAQ.
[38:42.200 -> 38:46.800] We have started conversations with Wall Street people,
[38:46.800 -> 38:51.840] who are really interested in Ord, and they want to lease Ord on NASDAQ. And
[38:51.840 -> 39:00.000] the conversations have just begun. That’s our goal. I mean, we made several commitments
[39:00.000 -> 39:05.120] at the beginning of the project, and we are gradually fulfilling our commitments.
[39:13.200 -> 39:27.600] So we don’t want to miss any of the commitments we made to the community, the public, and ourselves. So yes, while I want to say life is tough, and the global market is tough, we are holding tight, and we are working hard to achieve our goals
[39:27.600 -> 39:31.560] to bring good products and technology to the world.
[39:31.560 -> 39:39.520] We are becoming more confident that we will be leading the industry
[39:39.520 -> 39:40.520] in the long run.
[39:40.520 -> 39:43.960] That’s all I wanted to share with you.
[39:43.960 -> 39:47.760] I see we have some questions.
[39:47.760 -> 39:53.840] Okay, Tyler, I will hand it over to you, and we can start the Q&A session.
[39:53.840 -> 39:56.080] Perfect.
[39:56.080 -> 39:56.560] Yes.
[39:56.560 -> 40:00.480] Thank you, Dr. Lee, for sharing all these updates.
[40:00.480 -> 40:07.520] I think you are very clear about our positioning and the development process
[40:07.520 -> 40:09.680] just like that.
[40:09.680 -> 40:16.600] I feel like we discussed a lot about partnerships and talked about the importance of the community.
[40:16.600 -> 40:21.360] This brings up one of the questions I saw in the chat.
[40:21.360 -> 40:30.400] This is from the King of the South, who inquired how long it takes
for an average user to use Orc TDS or if it is only suitable for companies? Can you clarify that for us?
[40:38.400 -> 40:46.560] Oh yes, so this is not just for companies. Basically, you just need to visit our website and go to the TDS
webpage and register, and you can start using it in a few minutes. I think it just takes you
about 30 seconds to register and then you can start using it. You upload your own data, and then
you can create your bot, and then you can start talking to it.
So feel free to use this very simple onboarding process.
[41:10.400 -> 41:12.840] Yes, thank you.
[41:12.840 -> 41:18.520] Besides that, can you further discuss how
the board is catering to businesses of different sizes, from some startups to these large enterprises,
how our technology is integrated and utilized for their
benefit? Okay, yes, for small and medium-sized enterprises, I would say, I mean
[41:40.100 -> 41:45.900] for example, the integration of all TDS services is very small.
[41:45.900 -> 41:53.120] We support all APIs and large companies, for example, like Novo, they have their own API
applications and their own WeChat mini-programs.
[41:53.120 -> 41:57.180] They just easily integrate our API into their current existing applications.
[42:03.780 -> 42:04.780] And that’s it.
[42:04.780 -> 42:06.480] Very simple.
[42:06.480 -> 42:08.560] For small and medium-sized enterprises,
[42:09.560 -> 42:12.800] but for large enterprise clients,
[42:12.800 -> 42:14.840] they may need some customization.
[42:14.840 -> 42:19.840] We do some further technical development on the backend
[42:20.560 -> 42:25.000] to meet their needs, especially the needs of customers.
[42:25.680 -> 42:28.400] But for small and medium-sized enterprise clients,
[42:28.400 -> 42:30.560] they really want to, but the gap is large.
[42:30.560 -> 42:32.760] So they really want to use AI,
[42:32.760 -> 42:37.760] but they can’t afford the costs of AI training
[42:39.120 -> 42:43.640] and fine-tuning, and they don’t even have AI experts
[42:43.640 -> 42:47.000] to help them build this stuff.
[42:47.000 -> 42:58.000] So TDS is a perfect solution because if you try to use it, you will find that you don’t need to be an engineer or an AI expert to use it.
[42:58.000 -> 43:03.000] It’s just an ordinary person with no AI knowledge, and you can still use it.
[43:03.000 -> 43:08.520] This is very welcomed by small and medium enterprises, small and medium end customers.
[43:09.480 -> 43:12.360] So because they are small, they care about costs
[43:12.800 -> 43:17.240] they may need their business may not need too much customization,
[43:17.240 -> 43:20.440] but they do care about costs and ease of use.
[43:22.440 -> 43:26.600] Yes, that’s what I saw in some conversations, is
[43:26.600 -> 43:34.640] even something as simple as a car dealership, there are many
[43:34.640 -> 43:41.840] issues in the car buying process, I really just want to get a complete information
answer. I don’t want to fill out any information. I just need the technical specifications of the car.
[43:48.480 -> 43:51.000] If I could access a website that would be great
[43:51.000 -> 43:56.000] to get it directly from something like TDS.
[43:56.000 -> 43:59.800] So I understand its real use
[43:59.800 -> 44:02.760] for many different industries.
[44:02.760 -> 44:06.340] The reason is like the factual basis.
[44:06.340 -> 44:10.380] I don’t need you to tell me who the president is
[44:10.380 -> 44:13.740] when I just need to know what the price of a car is.
[44:13.740 -> 44:14.580] Yeah, yeah.
[44:14.580 -> 44:18.140] So if you go to TDS and say, set up your bot
[44:18.140 -> 44:20.780] if you ask, or if you go to Lenovo,
[44:20.780 -> 44:23.460] a customer service bot, anyone can try.
[44:23.460 -> 44:26.080] If you say, who is the president of the United States
[44:26.080 -> 44:28.200] or who is the chairman of China?
[44:28.200 -> 44:30.200] So the bot can say, sorry, I don’t know.
[44:31.160 -> 44:32.400] Right, yes.
[44:33.900 -> 44:37.400] Yes, so this is a personal question, Dr. Lee,
[44:37.400 -> 44:40.240] I think the community will appreciate it.
[44:40.240 -> 44:43.600] So there’s a lot of discussion,
[44:43.600 -> 44:47.000] this is also something Mike has discussed
[44:47.000 -> 44:52.700] there’s a lot, but from a macro perspective, these data centers and servers,
[44:52.700 -> 45:00.500] as more and more people use generative AI, it does affect our sustainability goals for the content outlined here,
[45:00.500 -> 45:05.320] such as nations and such things, we think
[45:05.320 -> 45:10.380] are put in a secondary position, just really invested in this generative AI, we
[45:10.380 -> 45:17.400] don’t have enough capacity to sustain this model. So I see and I
[45:17.400 -> 45:21.920] feel DSS does address this issue, but we haven’t really discussed
[45:21.920 -> 45:25.200] it. Can you share more about how
[45:25.200 -> 45:30.280] DSS makes us stand out in terms of data storage locations and data storage
[45:30.280 -> 45:41.200] and how our operations are? Okay, yes, I also see one of our questions
[45:41.200 -> 45:46.440] committee members talking about this sustainability, they call it sustainable
[45:46.440 -> 45:47.440] generative AI, right?
[45:47.440 -> 45:54.360] How does it align with the goals of sustainable generative AI?
[45:54.360 -> 46:09.280] So yes, so this is a very simple thing, and I was just invited to speak at the World Climate Summit in Dubai later this year, I want to earlier
[46:09.280 -> 46:10.280] in December.
[46:10.280 -> 46:16.280] I will be speaking on this because you know, the Dubai World Climate Summit
[46:16.280 -> 46:19.480] this year, it’s a big conference, right?
[46:19.480 -> 46:25.160] So it will discuss all sustainability regarding energy, clean energy, and so on.
[46:25.160 -> 46:29.320] So ORD, as a decentralized data cloud,
[46:29.320 -> 46:34.320] aligns perfectly with this sustainability
[46:35.120 -> 46:38.880] in terms of energy, in terms of pollution,
[46:38.880 -> 46:43.880] because we see the key of decentralized infrastructure
[46:44.320 -> 46:49.640] is to leverage underutilized computing and
[46:49.640 -> 46:52.120] storage resources.
[46:52.120 -> 46:56.240] So you don’t need to build more and more data centers around the world.
[46:56.240 -> 47:02.700] So now, for any company, if they want to do so, they need more data storage
[47:02.700 -> 47:05.040] space or they need some computing power.
[47:05.040 -> 47:06.040] What do they do?
[47:06.040 -> 47:10.200] They have to hire people, they have to spend money, budget to build a new
[47:10.200 -> 47:11.200] data center.
[47:11.200 -> 47:19.040] I mean, let’s say this is a big company, they will buy GPUs, A100s, and stuff like that.
[47:19.040 -> 47:20.040] This is very expensive.
[47:20.040 -> 47:29.960] They build data centers, and data centers require a lot of noise, pollution, electricity costs, consumption, you know, all these types of things,
[47:29.960 -> 47:34.560] they are absolutely not environmentally friendly. The organization as
[47:34.560 -> 47:40.200] a decentralized data cloud, like DSS, yes, so we don’t build
[47:40.200 -> 47:49.120] any new data centers, not even a single data center. No. We just connect all the underutilized resources around the world.
[47:49.440 -> 47:58.640] And then I just had a call with Amazon this morning, basically right before
[47:58.640 -> 48:01.040] the Twitter space that Amazon launched.
[48:01.440 -> 48:09.520] So they said even Amazon, yes, so their utilization rate is only 65%.
[48:11.360 -> 48:19.440] This means 35% is idle or underutilized, right? This is Amazon. Think about other
[48:20.560 -> 48:29.800] cloud service providers. It might be lower, right? Yes, absolutely. Yes. So we also talked about another big player
[48:29.800 -> 48:35.640] in the US. So I can’t disclose the name, but they are
[48:35.640 -> 48:38.960] one of our partners that will be announced soon. But they said
[48:38.960 -> 48:45.000] they have 95% of their servers in the US not being utilized.
[48:47.880 -> 48:50.440] Wow, 95%.
[48:50.440 -> 48:52.200] So that’s a crazy number, right?
[48:52.200 -> 48:57.200] That’s why we want to use these underutilized resources
[48:58.220 -> 49:02.560] for AI training and fine-tuning and data storage.
[49:03.560 -> 49:07.840] This is what OORT can convey to the community, to the world.
[49:08.240 -> 49:09.760] We have achieved this.
[49:10.240 -> 49:17.560] That’s why you can see we save up to 60% in costs.
[49:18.320 -> 49:23.280] While we save costs, the secret is we leverage all
[49:23.280 -> 49:24.960] these underutilized resources.
The secret weapon is we use, we leverage all these underutilized resources. Yes, that’s a good answer. I think this really leads to another question raised by Ali.
[49:35.000 -> 49:40.000] What is the long-term vision for the Ortz product?
[49:40.000 -> 49:44.000] How will they impact the Web3 industry?
[49:44.000 -> 49:49.000] Maybe I can try this quickly, and then you can add.
[49:49.000 -> 50:08.240] But when we talk about TDS, I do see the long-term vision of TDS because different industries will look for fact-based bots, and we have a very unique opportunity to build the foundation for bots.
[50:13.920 -> 50:16.240] We have ample opportunities ahead of us.
[50:21.520 -> 50:25.000] Oh, Tyler, I think you’re in and out.
[50:25.000 -> 50:27.000] Can you hear me?
[50:27.000 -> 50:34.000] Hello?
[50:34.000 -> 50:35.000] Can you hear me?
[50:35.000 -> 50:37.000] Yes, I can hear you.
[50:37.000 -> 50:40.000] Oh, okay. Sorry. I’m going in and out.
[50:40.000 -> 50:46.260] But for the whole Web3 industry, I think all of us in this industry
[50:46.260 -> 50:49.200] are craving true decentralization.
[50:49.200 -> 50:57.220] I know I’ve done it, and I know I’ve been looking for who will do this first.
[50:57.220 -> 51:03.240] We still have a first-mover advantage because we can always be the infrastructure
[51:03.240 -> 51:05.000] at any given moment,
[51:05.000 -> 51:07.000] okay, let’s do this the right way.
[51:07.000 -> 51:09.000] So I’m very excited.
[51:09.000 -> 51:12.000] So I want to get back to this question, what is the long-term vision of the product,
[51:12.000 -> 51:16.000] how will these products impact?
[51:16.000 -> 51:18.000] Okay, great. That’s a great question.
[51:18.000 -> 51:30.680] So I want to say, if you know Amazon is the leader in the cloud service industry,
[51:30.680 -> 51:38.200] in the Web2 space, they started their business over 20 years ago, in the late 90s.
[51:38.200 -> 51:45.760] So our long-term vision is to become the Amazon of the Web3 space.
[51:45.760 -> 51:47.200] We are leading this field.
[51:47.200 -> 51:52.880] We are one of the earliest participants to provide this infrastructure,
[51:53.680 -> 51:59.200] decentralized infrastructure services or solutions for the entire Web3 industry.
[52:00.240 -> 52:06.640] Because the Web3 industry, they long need decentralized infrastructure.
[52:06.640 -> 52:13.200] But unfortunately now, I want to say almost all Web3 projects,
[52:13.200 -> 52:22.640] they use traditional cloud services to host their applications and data.
[52:24.000 -> 52:26.560] If you ask them, they will all use Amazon,
[52:26.560 -> 52:28.600] Alibaba Cloud, and Google Cloud.
[52:28.600 -> 52:30.000] This is ridiculous.
[52:30.000 -> 52:33.200] In my opinion, this is ridiculous because you
[52:33.200 -> 52:36.720] promote some decentralized applications.
[52:36.720 -> 52:40.400] But then under the hooks at the backend,
[52:40.400 -> 52:43.320] you put everything on a single server.
[52:43.320 -> 52:49.000] So what does this decentralization mean for the users?
[52:49.000 -> 52:51.000] But users don’t know, right?
[52