WEBVTT
Kind: captions
Language: en

00:00:01.160 --> 00:00:06.690 align:start position:0%
 
[Music]

00:00:06.690 --> 00:00:06.700 align:start position:0%
 
 

00:00:06.700 --> 00:00:09.190 align:start position:0%
 
[Music]

00:00:09.190 --> 00:00:09.200 align:start position:0%
[Music]
 

00:00:09.200 --> 00:00:11.830 align:start position:0%
[Music]
and<00:00:09.400><c> so</c><00:00:09.679><c> glad</c><00:00:09.960><c> to</c><00:00:10.080><c> be</c><00:00:10.360><c> here</c><00:00:11.080><c> and</c><00:00:11.240><c> today</c><00:00:11.639><c> I</c><00:00:11.719><c> would</c>

00:00:11.830 --> 00:00:11.840 align:start position:0%
and so glad to be here and today I would
 

00:00:11.840 --> 00:00:14.110 align:start position:0%
and so glad to be here and today I would
like<00:00:12.000><c> to</c><00:00:12.160><c> share</c><00:00:12.599><c> about</c><00:00:12.840><c> our</c><00:00:13.040><c> current</c><00:00:13.400><c> work</c>

00:00:14.110 --> 00:00:14.120 align:start position:0%
like to share about our current work
 

00:00:14.120 --> 00:00:16.950 align:start position:0%
like to share about our current work
named<00:00:14.599><c> Mobi</c><00:00:15.240><c> a</c><00:00:15.400><c> mobile</c><00:00:15.759><c> based</c><00:00:16.160><c> like</c><00:00:16.359><c> client</c>

00:00:16.950 --> 00:00:16.960 align:start position:0%
named Mobi a mobile based like client
 

00:00:16.960 --> 00:00:19.750 align:start position:0%
named Mobi a mobile based like client
I'm<00:00:17.119><c> s</c><00:00:17.480><c> hun</c><00:00:17.760><c> and</c><00:00:18.000><c> partner</c><00:00:18.320><c> of</c><00:00:18.480><c> the</c><00:00:18.600><c> ABC</c><00:00:18.960><c> Labs</c><00:00:19.560><c> so</c>

00:00:19.750 --> 00:00:19.760 align:start position:0%
I'm s hun and partner of the ABC Labs so
 

00:00:19.760 --> 00:00:23.109 align:start position:0%
I'm s hun and partner of the ABC Labs so
ABC<00:00:20.279><c> is</c><00:00:20.439><c> not</c><00:00:20.640><c> just</c><00:00:20.840><c> a</c><00:00:21.119><c> ventur</c><00:00:21.840><c> capital</c><00:00:22.320><c> we</c><00:00:22.480><c> are</c>

00:00:23.109 --> 00:00:23.119 align:start position:0%
ABC is not just a ventur capital we are
 

00:00:23.119 --> 00:00:24.870 align:start position:0%
ABC is not just a ventur capital we are
always<00:00:23.400><c> make</c><00:00:23.640><c> our</c><00:00:23.840><c> hand</c><00:00:24.080><c> dirty</c><00:00:24.439><c> before</c><00:00:24.720><c> we</c>

00:00:24.870 --> 00:00:24.880 align:start position:0%
always make our hand dirty before we
 

00:00:24.880 --> 00:00:27.070 align:start position:0%
always make our hand dirty before we
make<00:00:25.080><c> the</c><00:00:25.240><c> investment</c><00:00:26.160><c> so</c><00:00:26.439><c> that's</c><00:00:26.720><c> part</c><00:00:26.920><c> of</c>

00:00:27.070 --> 00:00:27.080 align:start position:0%
make the investment so that's part of
 

00:00:27.080 --> 00:00:30.029 align:start position:0%
make the investment so that's part of
the<00:00:27.400><c> investment</c><00:00:28.119><c> strategy</c><00:00:29.119><c> so</c><00:00:29.359><c> this</c><00:00:29.519><c> work</c><00:00:29.759><c> is</c>

00:00:30.029 --> 00:00:30.039 align:start position:0%
the investment strategy so this work is
 

00:00:30.039 --> 00:00:32.870 align:start position:0%
the investment strategy so this work is
powered<00:00:30.320><c> by</c><00:00:30.560><c> ABC</c><00:00:31.119><c> and</c><00:00:31.320><c> cisc</c><00:00:31.800><c> CC</c><00:00:32.239><c> is</c><00:00:32.360><c> another</c>

00:00:32.870 --> 00:00:32.880 align:start position:0%
powered by ABC and cisc CC is another
 

00:00:32.880 --> 00:00:34.790 align:start position:0%
powered by ABC and cisc CC is another
company<00:00:33.320><c> which</c><00:00:33.480><c> are</c><00:00:33.640><c> doing</c><00:00:33.960><c> really</c><00:00:34.320><c> good</c><00:00:34.559><c> job</c>

00:00:34.790 --> 00:00:34.800 align:start position:0%
company which are doing really good job
 

00:00:34.800 --> 00:00:36.950 align:start position:0%
company which are doing really good job
on<00:00:35.239><c> ZK</c><00:00:35.600><c> Hardware</c><00:00:35.960><c> acceleration</c><00:00:36.640><c> they</c><00:00:36.760><c> will</c>

00:00:36.950 --> 00:00:36.960 align:start position:0%
on ZK Hardware acceleration they will
 

00:00:36.960 --> 00:00:38.910 align:start position:0%
on ZK Hardware acceleration they will
help<00:00:37.200><c> us</c><00:00:37.399><c> to</c><00:00:37.559><c> build</c><00:00:37.960><c> more</c><00:00:38.239><c> efficient</c>

00:00:38.910 --> 00:00:38.920 align:start position:0%
help us to build more efficient
 

00:00:38.920 --> 00:00:43.510 align:start position:0%
help us to build more efficient
stateless<00:00:39.480><c> light</c><00:00:40.000><c> client</c><00:00:41.360><c> so</c><00:00:42.360><c> so</c><00:00:42.960><c> the</c><00:00:43.160><c> entire</c>

00:00:43.510 --> 00:00:43.520 align:start position:0%
stateless light client so so the entire
 

00:00:43.520 --> 00:00:46.069 align:start position:0%
stateless light client so so the entire
blockchain<00:00:43.960><c> Community</c><00:00:44.640><c> is</c><00:00:44.800><c> founded</c><00:00:45.239><c> on</c><00:00:45.640><c> One</c>

00:00:46.069 --> 00:00:46.079 align:start position:0%
blockchain Community is founded on One
 

00:00:46.079 --> 00:00:49.830 align:start position:0%
blockchain Community is founded on One
Core<00:00:46.680><c> principle</c><00:00:47.680><c> don't</c><00:00:47.920><c> trust</c><00:00:48.640><c> verify</c><00:00:49.600><c> this</c>

00:00:49.830 --> 00:00:49.840 align:start position:0%
Core principle don't trust verify this
 

00:00:49.840 --> 00:00:52.430 align:start position:0%
Core principle don't trust verify this
principle<00:00:50.399><c> served</c><00:00:50.840><c> as</c><00:00:50.960><c> a</c><00:00:51.199><c> foundation</c><00:00:51.920><c> payLo</c>

00:00:52.430 --> 00:00:52.440 align:start position:0%
principle served as a foundation payLo
 

00:00:52.440 --> 00:00:54.830 align:start position:0%
principle served as a foundation payLo
for<00:00:52.680><c> the</c><00:00:53.440><c> architecture</c><00:00:54.079><c> of</c><00:00:54.199><c> the</c><00:00:54.320><c> blockchain</c>

00:00:54.830 --> 00:00:54.840 align:start position:0%
for the architecture of the blockchain
 

00:00:54.840 --> 00:00:59.029 align:start position:0%
for the architecture of the blockchain
networks<00:00:55.840><c> so</c><00:00:56.199><c> after</c><00:00:56.480><c> the</c><00:00:56.960><c> POS</c><00:00:57.920><c> so</c><00:00:58.239><c> the</c><00:00:58.480><c> etherum</c>

00:00:59.029 --> 00:00:59.039 align:start position:0%
networks so after the POS so the etherum
 

00:00:59.039 --> 00:01:02.549 align:start position:0%
networks so after the POS so the etherum
officially<00:00:59.640><c> po</c><00:01:00.199><c> the</c><00:01:00.399><c> light</c><00:01:00.640><c> client</c><00:01:01.280><c> works</c><00:01:02.160><c> but</c>

00:01:02.549 --> 00:01:02.559 align:start position:0%
officially po the light client works but
 

00:01:02.559 --> 00:01:04.829 align:start position:0%
officially po the light client works but
fortunately<00:01:03.280><c> several</c><00:01:03.600><c> third</c><00:01:03.920><c> party</c><00:01:04.199><c> teams</c>

00:01:04.829 --> 00:01:04.839 align:start position:0%
fortunately several third party teams
 

00:01:04.839 --> 00:01:07.429 align:start position:0%
fortunately several third party teams
are<00:01:05.080><c> initial</c><00:01:05.600><c> their</c><00:01:05.799><c> own</c><00:01:06.439><c> implementations</c>

00:01:07.429 --> 00:01:07.439 align:start position:0%
are initial their own implementations
 

00:01:07.439 --> 00:01:11.030 align:start position:0%
are initial their own implementations
such<00:01:07.680><c> as</c><00:01:07.960><c> NBAs</c><00:01:08.560><c> based</c><00:01:08.799><c> on</c><00:01:08.920><c> name</c><00:01:09.640><c> and</c><00:01:10.119><c> lar</c><00:01:10.799><c> based</c>

00:01:11.030 --> 00:01:11.040 align:start position:0%
such as NBAs based on name and lar based
 

00:01:11.040 --> 00:01:13.390 align:start position:0%
such as NBAs based on name and lar based
on<00:01:11.159><c> the</c><00:01:11.240><c> tab</c><00:01:11.479><c> scrap</c><00:01:12.119><c> and</c><00:01:12.320><c> Hiers</c><00:01:12.960><c> based</c><00:01:13.200><c> on</c><00:01:13.280><c> the</c>

00:01:13.390 --> 00:01:13.400 align:start position:0%
on the tab scrap and Hiers based on the
 

00:01:13.400 --> 00:01:16.830 align:start position:0%
on the tab scrap and Hiers based on the
rust<00:01:14.200><c> so</c><00:01:14.720><c> however</c><00:01:15.200><c> none</c><00:01:15.479><c> of</c><00:01:15.680><c> the</c><00:01:16.159><c> L</c><00:01:16.439><c> CL</c>

00:01:16.830 --> 00:01:16.840 align:start position:0%
rust so however none of the L CL
 

00:01:16.840 --> 00:01:20.030 align:start position:0%
rust so however none of the L CL
Solutions<00:01:17.840><c> con</c><00:01:18.119><c> natively</c><00:01:18.640><c> run</c><00:01:19.200><c> on</c><00:01:19.400><c> the</c><00:01:19.600><c> most</c>

00:01:20.030 --> 00:01:20.040 align:start position:0%
Solutions con natively run on the most
 

00:01:20.040 --> 00:01:23.069 align:start position:0%
Solutions con natively run on the most
ubiquitous<00:01:21.040><c> devices</c><00:01:21.920><c> the</c><00:01:22.119><c> mobile</c><00:01:22.439><c> phone</c>

00:01:23.069 --> 00:01:23.079 align:start position:0%
ubiquitous devices the mobile phone
 

00:01:23.079 --> 00:01:27.069 align:start position:0%
ubiquitous devices the mobile phone
right<00:01:23.840><c> and</c><00:01:24.159><c> so</c><00:01:24.640><c> our</c><00:01:24.880><c> goal</c><00:01:25.119><c> is</c><00:01:25.280><c> quite</c><00:01:25.520><c> simple</c><00:01:26.479><c> we</c>

00:01:27.069 --> 00:01:27.079 align:start position:0%
right and so our goal is quite simple we
 

00:01:27.079 --> 00:01:30.469 align:start position:0%
right and so our goal is quite simple we
we<00:01:27.200><c> are</c><00:01:27.439><c> working</c><00:01:27.759><c> on</c><00:01:28.000><c> to</c><00:01:28.200><c> offer</c><00:01:28.840><c> and</c><00:01:29.640><c> our</c><00:01:29.960><c> to</c><00:01:30.159><c> e</c>

00:01:30.469 --> 00:01:30.479 align:start position:0%
we are working on to offer and our to e
 

00:01:30.479 --> 00:01:33.350 align:start position:0%
we are working on to offer and our to e
room<00:01:30.640><c> Community</c><00:01:31.600><c> a</c><00:01:31.880><c> alternative</c><00:01:32.840><c> a</c><00:01:33.040><c> light</c>

00:01:33.350 --> 00:01:33.360 align:start position:0%
room Community a alternative a light
 

00:01:33.360 --> 00:01:36.910 align:start position:0%
room Community a alternative a light
client<00:01:34.079><c> can</c><00:01:34.240><c> run</c><00:01:35.240><c> any</c><00:01:35.880><c> mobile</c>

00:01:36.910 --> 00:01:36.920 align:start position:0%
client can run any mobile
 

00:01:36.920 --> 00:01:41.190 align:start position:0%
client can run any mobile
devices<00:01:37.920><c> so</c><00:01:38.360><c> the</c><00:01:38.520><c> motivation</c><00:01:39.439><c> so</c><00:01:40.320><c> why</c><00:01:40.759><c> this</c><00:01:41.000><c> is</c>

00:01:41.190 --> 00:01:41.200 align:start position:0%
devices so the motivation so why this is
 

00:01:41.200 --> 00:01:43.870 align:start position:0%
devices so the motivation so why this is
is<00:01:41.439><c> technically</c><00:01:41.960><c> feasible</c><00:01:42.720><c> so</c><00:01:43.000><c> as</c>

00:01:43.870 --> 00:01:43.880 align:start position:0%
is technically feasible so as
 

00:01:43.880 --> 00:01:47.550 align:start position:0%
is technically feasible so as
2024<00:01:44.880><c> the</c><00:01:45.040><c> performance</c><00:01:45.600><c> of</c><00:01:45.880><c> edge</c><00:01:46.320><c> devices</c><00:01:47.320><c> uh</c>

00:01:47.550 --> 00:01:47.560 align:start position:0%
2024 the performance of edge devices uh
 

00:01:47.560 --> 00:01:50.069 align:start position:0%
2024 the performance of edge devices uh
has<00:01:47.920><c> advanced</c><00:01:48.759><c> significantly</c><00:01:49.759><c> we</c><00:01:49.880><c> are</c>

00:01:50.069 --> 00:01:50.079 align:start position:0%
has advanced significantly we are
 

00:01:50.079 --> 00:01:51.990 align:start position:0%
has advanced significantly we are
already<00:01:50.399><c> seeing</c><00:01:50.799><c> some</c><00:01:51.040><c> developers</c><00:01:51.600><c> running</c>

00:01:51.990 --> 00:01:52.000 align:start position:0%
already seeing some developers running
 

00:01:52.000 --> 00:01:54.990 align:start position:0%
already seeing some developers running
local<00:01:52.280><c> RM</c><00:01:52.840><c> on</c><00:01:52.960><c> your</c><00:01:53.320><c> mobiles</c><00:01:54.320><c> and</c><00:01:54.560><c> running</c>

00:01:54.990 --> 00:01:55.000 align:start position:0%
local RM on your mobiles and running
 

00:01:55.000 --> 00:01:57.069 align:start position:0%
local RM on your mobiles and running
light<00:01:55.240><c> clients</c><00:01:55.640><c> on</c><00:01:55.759><c> the</c><00:01:55.920><c> mobiles</c><00:01:56.719><c> only</c>

00:01:57.069 --> 00:01:57.079 align:start position:0%
light clients on the mobiles only
 

00:01:57.079 --> 00:01:59.069 align:start position:0%
light clients on the mobiles only
require<00:01:57.600><c> a</c><00:01:57.799><c> periodically</c><00:01:58.560><c> network</c>

00:01:59.069 --> 00:01:59.079 align:start position:0%
require a periodically network
 

00:01:59.079 --> 00:02:02.029 align:start position:0%
require a periodically network
communication<00:02:00.000><c> and</c><00:02:00.200><c> some</c><00:02:00.759><c> storage</c><00:02:01.759><c> so</c>

00:02:02.029 --> 00:02:02.039 align:start position:0%
communication and some storage so
 

00:02:02.039 --> 00:02:04.510 align:start position:0%
communication and some storage so
therefore<00:02:02.680><c> running</c><00:02:03.039><c> a</c><00:02:03.280><c> eim</c><00:02:03.719><c> light</c><00:02:03.960><c> client</c><00:02:04.320><c> on</c>

00:02:04.510 --> 00:02:04.520 align:start position:0%
therefore running a eim light client on
 

00:02:04.520 --> 00:02:06.870 align:start position:0%
therefore running a eim light client on
the<00:02:04.680><c> mobile</c><00:02:05.200><c> is</c><00:02:05.520><c> entirely</c>

00:02:06.870 --> 00:02:06.880 align:start position:0%
the mobile is entirely
 

00:02:06.880 --> 00:02:10.510 align:start position:0%
the mobile is entirely
feasible<00:02:07.880><c> so</c><00:02:08.560><c> how</c><00:02:08.720><c> to</c><00:02:08.879><c> make</c><00:02:09.000><c> it</c><00:02:09.239><c> happen</c><00:02:10.039><c> so</c><00:02:10.280><c> our</c>

00:02:10.510 --> 00:02:10.520 align:start position:0%
feasible so how to make it happen so our
 

00:02:10.520 --> 00:02:13.270 align:start position:0%
feasible so how to make it happen so our
goal<00:02:10.800><c> is</c><00:02:11.280><c> is</c><00:02:11.400><c> not</c><00:02:11.640><c> build</c><00:02:11.959><c> something</c><00:02:12.280><c> new</c><00:02:12.879><c> and</c>

00:02:13.270 --> 00:02:13.280 align:start position:0%
goal is is not build something new and
 

00:02:13.280 --> 00:02:15.229 align:start position:0%
goal is is not build something new and
uh<00:02:13.560><c> we</c><00:02:13.800><c> want</c><00:02:14.040><c> to</c><00:02:14.280><c> build</c>

00:02:15.229 --> 00:02:15.239 align:start position:0%
uh we want to build
 

00:02:15.239 --> 00:02:18.070 align:start position:0%
uh we want to build
SDK<00:02:16.239><c> for</c><00:02:16.440><c> the</c><00:02:16.680><c> native</c><00:02:17.040><c> running</c><00:02:17.440><c> L</c><00:02:17.680><c> kind</c><00:02:17.959><c> for</c>

00:02:18.070 --> 00:02:18.080 align:start position:0%
SDK for the native running L kind for
 

00:02:18.080 --> 00:02:19.910 align:start position:0%
SDK for the native running L kind for
the<00:02:18.200><c> mobile</c><00:02:18.760><c> for</c><00:02:18.920><c> the</c><00:02:19.080><c> mobile</c><00:02:19.440><c> platform</c>

00:02:19.910 --> 00:02:19.920 align:start position:0%
the mobile for the mobile platform
 

00:02:19.920 --> 00:02:22.390 align:start position:0%
the mobile for the mobile platform
especially<00:02:20.239><c> for</c><00:02:20.319><c> the</c><00:02:20.440><c> Androids</c><00:02:21.200><c> so</c><00:02:21.400><c> the</c><00:02:21.640><c> whole</c>

00:02:22.390 --> 00:02:22.400 align:start position:0%
especially for the Androids so the whole
 

00:02:22.400 --> 00:02:24.790 align:start position:0%
especially for the Androids so the whole
we<00:02:22.480><c> don't</c><00:02:22.680><c> want</c><00:02:22.840><c> to</c><00:02:23.000><c> build</c><00:02:23.440><c> something</c><00:02:24.440><c> uh</c>

00:02:24.790 --> 00:02:24.800 align:start position:0%
we don't want to build something uh
 

00:02:24.800 --> 00:02:27.390 align:start position:0%
we don't want to build something uh
already<00:02:25.200><c> happened</c><00:02:25.800><c> so</c><00:02:26.400><c> the</c><00:02:26.840><c> the</c><00:02:27.200><c> whole</c>

00:02:27.390 --> 00:02:27.400 align:start position:0%
already happened so the the whole
 

00:02:27.400 --> 00:02:28.990 align:start position:0%
already happened so the the whole
architecture<00:02:27.920><c> is</c><00:02:28.160><c> about</c><00:02:28.360><c> based</c><00:02:28.599><c> on</c><00:02:28.760><c> their</c>

00:02:28.990 --> 00:02:29.000 align:start position:0%
architecture is about based on their
 

00:02:29.000 --> 00:02:31.350 align:start position:0%
architecture is about based on their
very<00:02:29.319><c> efficient</c><00:02:29.959><c> Library</c><00:02:30.319><c> called</c><00:02:30.560><c> Hiers</c>

00:02:31.350 --> 00:02:31.360 align:start position:0%
very efficient Library called Hiers
 

00:02:31.360 --> 00:02:34.990 align:start position:0%
very efficient Library called Hiers
created<00:02:31.800><c> by</c><00:02:32.120><c> xxd</c><00:02:33.120><c> and</c><00:02:33.519><c> Hiers</c><00:02:33.959><c> is</c><00:02:34.120><c> based</c><00:02:34.319><c> on</c><00:02:34.480><c> R</c>

00:02:34.990 --> 00:02:35.000 align:start position:0%
created by xxd and Hiers is based on R
 

00:02:35.000 --> 00:02:36.990 align:start position:0%
created by xxd and Hiers is based on R
and<00:02:35.239><c> what</c><00:02:35.360><c> we</c><00:02:35.440><c> are</c><00:02:35.599><c> doing</c><00:02:35.959><c> here</c><00:02:36.280><c> is</c><00:02:36.400><c> to</c><00:02:36.599><c> make</c><00:02:36.760><c> a</c>

00:02:36.990 --> 00:02:37.000 align:start position:0%
and what we are doing here is to make a
 

00:02:37.000 --> 00:02:40.390 align:start position:0%
and what we are doing here is to make a
cing<00:02:37.519><c> WP</c><00:02:38.360><c> and</c><00:02:38.599><c> to</c><00:02:38.760><c> make</c><00:02:39.000><c> it</c><00:02:39.280><c> as</c><00:02:39.480><c> a</c><00:02:39.800><c> library</c><00:02:40.200><c> for</c>

00:02:40.390 --> 00:02:40.400 align:start position:0%
cing WP and to make it as a library for
 

00:02:40.400 --> 00:02:43.149 align:start position:0%
cing WP and to make it as a library for
the<00:02:40.519><c> Android</c><00:02:41.480><c> so</c><00:02:41.959><c> our</c><00:02:42.280><c> secondary</c><00:02:42.720><c> goal</c><00:02:42.959><c> is</c>

00:02:43.149 --> 00:02:43.159 align:start position:0%
the Android so our secondary goal is
 

00:02:43.159 --> 00:02:45.630 align:start position:0%
the Android so our secondary goal is
after<00:02:43.480><c> achieving</c><00:02:43.920><c> the</c><00:02:44.360><c> compatible</c><00:02:45.360><c> with</c><00:02:45.519><c> the</c>

00:02:45.630 --> 00:02:45.640 align:start position:0%
after achieving the compatible with the
 

00:02:45.640 --> 00:02:49.110 align:start position:0%
after achieving the compatible with the
E<00:02:46.080><c> midnight</c><00:02:47.080><c> and</c><00:02:47.360><c> is</c><00:02:47.519><c> to</c><00:02:48.000><c> make</c><00:02:48.200><c> a</c><00:02:48.360><c> h</c><00:02:48.640><c> function</c>

00:02:49.110 --> 00:02:49.120 align:start position:0%
E midnight and is to make a h function
 

00:02:49.120 --> 00:02:51.149 align:start position:0%
E midnight and is to make a h function
like<00:02:49.280><c> to</c><00:02:49.440><c> offer</c><00:02:49.720><c> light</c><00:02:50.000><c> client</c><00:02:50.319><c> services</c><00:02:50.879><c> for</c>

00:02:51.149 --> 00:02:51.159 align:start position:0%
like to offer light client services for
 

00:02:51.159 --> 00:02:53.589 align:start position:0%
like to offer light client services for
E<00:02:51.519><c> all</c><00:02:51.720><c> e</c><00:02:52.159><c> layer</c><00:02:52.360><c> tools</c><00:02:52.720><c> if</c><00:02:52.879><c> they</c><00:02:53.080><c> provided</c>

00:02:53.589 --> 00:02:53.599 align:start position:0%
E all e layer tools if they provided
 

00:02:53.599 --> 00:02:54.790 align:start position:0%
E all e layer tools if they provided
light<00:02:53.800><c> CL</c>

00:02:54.790 --> 00:02:54.800 align:start position:0%
light CL
 

00:02:54.800 --> 00:02:57.110 align:start position:0%
light CL
protocol<00:02:55.800><c> and</c><00:02:56.080><c> so</c><00:02:56.280><c> because</c><00:02:56.519><c> their</c><00:02:56.760><c> time</c><00:02:56.959><c> is</c>

00:02:57.110 --> 00:02:57.120 align:start position:0%
protocol and so because their time is
 

00:02:57.120 --> 00:02:59.550 align:start position:0%
protocol and so because their time is
limited<00:02:57.640><c> and</c><00:02:57.840><c> we'll</c><00:02:58.360><c> share</c><00:02:58.680><c> some</c><00:02:59.040><c> experience</c>

00:02:59.550 --> 00:02:59.560 align:start position:0%
limited and we'll share some experience
 

00:02:59.560 --> 00:03:02.070 align:start position:0%
limited and we'll share some experience
to<00:02:59.879><c> make</c><00:03:00.080><c> it</c><00:03:00.280><c> happen</c><00:03:01.000><c> so</c><00:03:01.239><c> as</c><00:03:01.400><c> we</c><00:03:01.599><c> know</c><00:03:01.920><c> the</c>

00:03:02.070 --> 00:03:02.080 align:start position:0%
to make it happen so as we know the
 

00:03:02.080 --> 00:03:04.949 align:start position:0%
to make it happen so as we know the
heers<00:03:02.519><c> is</c><00:03:02.720><c> code</c><00:03:02.920><c> based</c><00:03:03.200><c> rtin</c><00:03:03.519><c> in</c><00:03:03.640><c> the</c><00:03:03.760><c> rest</c><00:03:04.640><c> so</c>

00:03:04.949 --> 00:03:04.959 align:start position:0%
heers is code based rtin in the rest so
 

00:03:04.959 --> 00:03:06.750 align:start position:0%
heers is code based rtin in the rest so
they're<00:03:05.239><c> containing</c><00:03:05.680><c> a</c><00:03:05.879><c> significant</c><00:03:06.440><c> amount</c>

00:03:06.750 --> 00:03:06.760 align:start position:0%
they're containing a significant amount
 

00:03:06.760 --> 00:03:09.509 align:start position:0%
they're containing a significant amount
of<00:03:07.000><c> their</c><00:03:07.480><c> synchronized</c><00:03:08.120><c> thre</c><00:03:09.120><c> and</c><00:03:09.280><c> but</c>

00:03:09.509 --> 00:03:09.519 align:start position:0%
of their synchronized thre and but
 

00:03:09.519 --> 00:03:12.869 align:start position:0%
of their synchronized thre and but
Android<00:03:10.200><c> is</c><00:03:10.360><c> on</c><00:03:10.519><c> the</c><00:03:10.760><c> hand</c><00:03:11.159><c> on</c><00:03:11.400><c> that</c><00:03:11.640><c> hand</c><00:03:12.040><c> is</c><00:03:12.200><c> a</c>

00:03:12.869 --> 00:03:12.879 align:start position:0%
Android is on the hand on that hand is a
 

00:03:12.879 --> 00:03:15.309 align:start position:0%
Android is on the hand on that hand is a
build<00:03:13.440><c> right</c><00:03:13.599><c> build</c><00:03:13.879><c> on</c><00:03:14.080><c> the</c><00:03:14.239><c> cing</c><00:03:14.799><c> and</c><00:03:15.040><c> which</c>

00:03:15.309 --> 00:03:15.319 align:start position:0%
build right build on the cing and which
 

00:03:15.319 --> 00:03:18.589 align:start position:0%
build right build on the cing and which
running<00:03:15.640><c> on</c><00:03:15.799><c> the</c><00:03:15.959><c> gvm</c><00:03:16.959><c> so</c><00:03:17.599><c> the</c><00:03:17.799><c> rust</c><00:03:18.239><c> do</c><00:03:18.360><c> not</c>

00:03:18.589 --> 00:03:18.599 align:start position:0%
running on the gvm so the rust do not
 

00:03:18.599 --> 00:03:21.070 align:start position:0%
running on the gvm so the rust do not
have<00:03:18.760><c> their</c><00:03:18.959><c> garbage</c><00:03:19.280><c> collection</c><00:03:20.080><c> mechanisms</c>

00:03:21.070 --> 00:03:21.080 align:start position:0%
have their garbage collection mechanisms
 

00:03:21.080 --> 00:03:23.589 align:start position:0%
have their garbage collection mechanisms
whereas<00:03:21.400><c> the</c><00:03:21.599><c> gvm</c><00:03:22.040><c> has</c><00:03:22.159><c> the</c><00:03:22.319><c> GC</c><00:03:23.080><c> so</c><00:03:23.319><c> this</c>

00:03:23.589 --> 00:03:23.599 align:start position:0%
whereas the gvm has the GC so this
 

00:03:23.599 --> 00:03:25.630 align:start position:0%
whereas the gvm has the GC so this
happen<00:03:23.879><c> a</c><00:03:23.959><c> lot</c><00:03:24.159><c> of</c><00:03:24.319><c> times</c><00:03:24.640><c> that</c><00:03:25.080><c> results</c><00:03:25.480><c> in</c>

00:03:25.630 --> 00:03:25.640 align:start position:0%
happen a lot of times that results in
 

00:03:25.640 --> 00:03:27.390 align:start position:0%
happen a lot of times that results in
the<00:03:25.840><c> synchronized</c><00:03:26.440><c> threat</c><00:03:27.000><c> has</c><00:03:27.159><c> been</c>

00:03:27.390 --> 00:03:27.400 align:start position:0%
the synchronized threat has been
 

00:03:27.400 --> 00:03:30.030 align:start position:0%
the synchronized threat has been
incorrectly<00:03:28.080><c> garbage</c><00:03:28.439><c> collected</c><00:03:28.920><c> by</c><00:03:29.040><c> the</c><00:03:29.120><c> gvm</c>

00:03:30.030 --> 00:03:30.040 align:start position:0%
incorrectly garbage collected by the gvm
 

00:03:30.040 --> 00:03:34.309 align:start position:0%
incorrectly garbage collected by the gvm
so<00:03:30.239><c> it's</c><00:03:30.560><c> really</c><00:03:30.879><c> painful</c><00:03:31.680><c> and</c><00:03:31.920><c> more</c><00:03:32.519><c> moreover</c>

00:03:34.309 --> 00:03:34.319 align:start position:0%
so it's really painful and more moreover
 

00:03:34.319 --> 00:03:37.309 align:start position:0%
so it's really painful and more moreover
Android<00:03:35.319><c> you</c><00:03:35.720><c> have</c><00:03:35.959><c> some</c><00:03:36.239><c> unique</c><00:03:36.680><c> permission</c>

00:03:37.309 --> 00:03:37.319 align:start position:0%
Android you have some unique permission
 

00:03:37.319 --> 00:03:39.990 align:start position:0%
Android you have some unique permission
protection<00:03:37.959><c> mechanisms</c><00:03:38.760><c> includes</c><00:03:39.280><c> the</c><00:03:39.519><c> where</c>

00:03:39.990 --> 00:03:40.000 align:start position:0%
protection mechanisms includes the where
 

00:03:40.000 --> 00:03:42.949 align:start position:0%
protection mechanisms includes the where
various<00:03:40.640><c> permission</c><00:03:41.200><c> Crosser</c><00:03:41.799><c> arrows</c><00:03:42.599><c> when</c>

00:03:42.949 --> 00:03:42.959 align:start position:0%
various permission Crosser arrows when
 

00:03:42.959 --> 00:03:46.509 align:start position:0%
various permission Crosser arrows when
when<00:03:43.200><c> directly</c><00:03:43.879><c> invoking</c><00:03:44.879><c> involve</c><00:03:45.519><c> some</c>

00:03:46.509 --> 00:03:46.519 align:start position:0%
when directly invoking involve some
 

00:03:46.519 --> 00:03:50.550 align:start position:0%
when directly invoking involve some
Hiers<00:03:47.280><c> code</c><00:03:47.799><c> base</c><00:03:48.799><c> and</c><00:03:49.280><c> uh</c><00:03:49.920><c> eventually</c><00:03:50.400><c> we</c>

00:03:50.550 --> 00:03:50.560 align:start position:0%
Hiers code base and uh eventually we
 

00:03:50.560 --> 00:03:52.990 align:start position:0%
Hiers code base and uh eventually we
have<00:03:50.760><c> some</c><00:03:51.200><c> long</c><00:03:51.599><c> additions</c><00:03:52.239><c> so</c><00:03:52.480><c> apart</c><00:03:52.760><c> from</c>

00:03:52.990 --> 00:03:53.000 align:start position:0%
have some long additions so apart from
 

00:03:53.000 --> 00:03:55.670 align:start position:0%
have some long additions so apart from
the<00:03:53.239><c> basic</c><00:03:53.799><c> functionality</c><00:03:54.799><c> we</c><00:03:55.040><c> have</c><00:03:55.239><c> further</c>

00:03:55.670 --> 00:03:55.680 align:start position:0%
the basic functionality we have further
 

00:03:55.680 --> 00:03:57.949 align:start position:0%
the basic functionality we have further
expectation<00:03:56.319><c> for</c><00:03:56.480><c> the</c><00:03:56.640><c> mobile</c><00:03:56.959><c> light</c><00:03:57.200><c> client</c>

00:03:57.949 --> 00:03:57.959 align:start position:0%
expectation for the mobile light client
 

00:03:57.959 --> 00:03:59.949 align:start position:0%
expectation for the mobile light client
including<00:03:58.640><c> but</c><00:03:58.840><c> not</c><00:03:59.040><c> limited</c><00:03:59.400><c> to</c><00:03:59.480><c> the</c><00:03:59.760><c> to</c><00:03:59.879><c> the</c>

00:03:59.949 --> 00:03:59.959 align:start position:0%
including but not limited to the to the
 

00:03:59.959 --> 00:04:01.830 align:start position:0%
including but not limited to the to the
following<00:04:00.319><c> two</c><00:04:00.560><c> directions</c><00:04:01.319><c> the</c><00:04:01.480><c> first</c><00:04:01.680><c> one</c>

00:04:01.830 --> 00:04:01.840 align:start position:0%
following two directions the first one
 

00:04:01.840 --> 00:04:04.229 align:start position:0%
following two directions the first one
is<00:04:02.239><c> functionality</c><00:04:03.239><c> the</c><00:04:03.480><c> core</c><00:04:03.799><c> function</c><00:04:04.120><c> of</c>

00:04:04.229 --> 00:04:04.239 align:start position:0%
is functionality the core function of
 

00:04:04.239 --> 00:04:06.830 align:start position:0%
is functionality the core function of
the<00:04:04.360><c> light</c><00:04:04.599><c> client</c><00:04:05.000><c> is</c><00:04:05.200><c> verification</c><00:04:06.200><c> right</c>

00:04:06.830 --> 00:04:06.840 align:start position:0%
the light client is verification right
 

00:04:06.840 --> 00:04:09.710 align:start position:0%
the light client is verification right
but<00:04:07.319><c> however</c><00:04:07.760><c> given</c><00:04:08.079><c> the</c><00:04:08.599><c> sto</c><00:04:09.200><c> storage</c>

00:04:09.710 --> 00:04:09.720 align:start position:0%
but however given the sto storage
 

00:04:09.720 --> 00:04:12.110 align:start position:0%
but however given the sto storage
performance<00:04:10.360><c> of</c><00:04:10.480><c> the</c><00:04:10.599><c> modern</c><00:04:11.000><c> devices</c><00:04:11.680><c> we</c><00:04:11.840><c> aim</c>

00:04:12.110 --> 00:04:12.120 align:start position:0%
performance of the modern devices we aim
 

00:04:12.120 --> 00:04:14.750 align:start position:0%
performance of the modern devices we aim
to<00:04:12.280><c> build</c><00:04:12.599><c> something</c><00:04:13.000><c> called</c><00:04:13.319><c> light</c><00:04:13.640><c> Cent</c><00:04:14.000><c> PL</c>

00:04:14.750 --> 00:04:14.760 align:start position:0%
to build something called light Cent PL
 

00:04:14.760 --> 00:04:16.629 align:start position:0%
to build something called light Cent PL
so<00:04:14.959><c> beyond</c><00:04:15.239><c> the</c><00:04:15.360><c> simple</c><00:04:15.640><c> verification</c><00:04:16.440><c> we</c>

00:04:16.629 --> 00:04:16.639 align:start position:0%
so beyond the simple verification we
 

00:04:16.639 --> 00:04:19.069 align:start position:0%
so beyond the simple verification we
intended<00:04:17.120><c> to</c><00:04:17.519><c> add</c><00:04:17.759><c> some</c><00:04:17.959><c> storage</c><00:04:18.519><c> compability</c>

00:04:19.069 --> 00:04:19.079 align:start position:0%
intended to add some storage compability
 

00:04:19.079 --> 00:04:22.189 align:start position:0%
intended to add some storage compability
for<00:04:19.919><c> example</c><00:04:20.359><c> users</c><00:04:20.880><c> could</c><00:04:21.560><c> selectively</c>

00:04:22.189 --> 00:04:22.199 align:start position:0%
for example users could selectively
 

00:04:22.199 --> 00:04:24.830 align:start position:0%
for example users could selectively
store<00:04:22.560><c> some</c><00:04:23.120><c> State</c><00:04:23.639><c> and</c><00:04:23.880><c> histor</c><00:04:24.440><c> data</c><00:04:24.680><c> of</c>

00:04:24.830 --> 00:04:24.840 align:start position:0%
store some State and histor data of
 

00:04:24.840 --> 00:04:28.270 align:start position:0%
store some State and histor data of
their<00:04:25.120><c> s</c><00:04:25.880><c> and</c><00:04:26.520><c> then</c><00:04:26.680><c> you</c><00:04:26.880><c> can</c><00:04:27.199><c> they</c><00:04:27.360><c> can</c><00:04:27.919><c> uh</c>

00:04:28.270 --> 00:04:28.280 align:start position:0%
their s and then you can they can uh
 

00:04:28.280 --> 00:04:30.590 align:start position:0%
their s and then you can they can uh
carry<00:04:28.600><c> them</c><00:04:28.800><c> locally</c><00:04:29.520><c> and</c><00:04:29.840><c> additionally</c><00:04:30.440><c> we</c>

00:04:30.590 --> 00:04:30.600 align:start position:0%
carry them locally and additionally we
 

00:04:30.600 --> 00:04:32.870 align:start position:0%
carry them locally and additionally we
want<00:04:30.759><c> to</c><00:04:30.960><c> build</c><00:04:31.240><c> some</c><00:04:31.440><c> rpcs</c><00:04:32.320><c> functionality</c>

00:04:32.870 --> 00:04:32.880 align:start position:0%
want to build some rpcs functionality
 

00:04:32.880 --> 00:04:36.150 align:start position:0%
want to build some rpcs functionality
for<00:04:33.080><c> use</c><00:04:33.600><c> for</c><00:04:33.960><c> other</c><00:04:34.240><c> use</c><00:04:34.840><c> l</c><00:04:35.160><c> client</c><00:04:35.520><c> knowes</c>

00:04:36.150 --> 00:04:36.160 align:start position:0%
for use for other use l client knowes
 

00:04:36.160 --> 00:04:39.390 align:start position:0%
for use for other use l client knowes
this<00:04:36.520><c> it's</c><00:04:36.919><c> kind</c><00:04:37.120><c> of</c><00:04:37.320><c> the</c><00:04:37.680><c> portal</c><00:04:38.000><c> Network</c><00:04:39.000><c> and</c>

00:04:39.390 --> 00:04:39.400 align:start position:0%
this it's kind of the portal Network and
 

00:04:39.400 --> 00:04:41.469 align:start position:0%
this it's kind of the portal Network and
another<00:04:39.720><c> part</c><00:04:40.000><c> is</c><00:04:40.479><c> the</c><00:04:40.639><c> entertainment</c><00:04:41.320><c> or</c>

00:04:41.469 --> 00:04:41.479 align:start position:0%
another part is the entertainment or
 

00:04:41.479 --> 00:04:44.110 align:start position:0%
another part is the entertainment or
make<00:04:41.680><c> it</c><00:04:41.880><c> more</c><00:04:42.080><c> smart</c><00:04:42.840><c> as</c><00:04:43.000><c> we</c><00:04:43.199><c> mentioned</c><00:04:43.720><c> so</c><00:04:43.960><c> in</c>

00:04:44.110 --> 00:04:44.120 align:start position:0%
make it more smart as we mentioned so in
 

00:04:44.120 --> 00:04:45.990 align:start position:0%
make it more smart as we mentioned so in
addition<00:04:44.400><c> to</c><00:04:44.560><c> the</c><00:04:44.680><c> light</c><00:04:44.919><c> client</c><00:04:45.440><c> so</c><00:04:45.680><c> mobile</c>

00:04:45.990 --> 00:04:46.000 align:start position:0%
addition to the light client so mobile
 

00:04:46.000 --> 00:04:47.790 align:start position:0%
addition to the light client so mobile
devices<00:04:46.479><c> now</c><00:04:46.680><c> have</c><00:04:46.840><c> the</c><00:04:47.000><c> ability</c><00:04:47.360><c> to</c><00:04:47.520><c> run</c>

00:04:47.790 --> 00:04:47.800 align:start position:0%
devices now have the ability to run
 

00:04:47.800 --> 00:04:50.350 align:start position:0%
devices now have the ability to run
local<00:04:48.039><c> RM</c><00:04:48.520><c> inference</c><00:04:49.199><c> so</c><00:04:49.400><c> for</c><00:04:49.759><c> for</c><00:04:49.960><c> example</c>

00:04:50.350 --> 00:04:50.360 align:start position:0%
local RM inference so for for example
 

00:04:50.360 --> 00:04:53.390 align:start position:0%
local RM inference so for for example
Android<00:04:51.280><c> private</c><00:04:51.840><c> local</c><00:04:52.479><c> Gemini</c><00:04:52.919><c> inference</c>

00:04:53.390 --> 00:04:53.400 align:start position:0%
Android private local Gemini inference
 

00:04:53.400 --> 00:04:57.590 align:start position:0%
Android private local Gemini inference
apis<00:04:54.400><c> and</c><00:04:54.800><c> we</c><00:04:55.000><c> want</c><00:04:55.280><c> to</c><00:04:55.600><c> explore</c><00:04:56.560><c> where</c><00:04:56.960><c> we</c><00:04:57.160><c> can</c>

00:04:57.590 --> 00:04:57.600 align:start position:0%
apis and we want to explore where we can
 

00:04:57.600 --> 00:05:00.430 align:start position:0%
apis and we want to explore where we can
combine<00:04:58.000><c> the</c><00:04:58.400><c> local</c><00:04:58.720><c> node</c><00:04:59.039><c> and</c><00:04:59.240><c> local</c><00:04:59.800><c> M</c>

00:05:00.430 --> 00:05:00.440 align:start position:0%
combine the local node and local M
 

00:05:00.440 --> 00:05:05.270 align:start position:0%
combine the local node and local M
together<00:05:01.440><c> to</c><00:05:01.840><c> conduct</c><00:05:02.400><c> some</c><00:05:03.400><c> uh</c><00:05:03.560><c> something</c><00:05:04.560><c> uh</c>

00:05:05.270 --> 00:05:05.280 align:start position:0%
together to conduct some uh something uh
 

00:05:05.280 --> 00:05:08.350 align:start position:0%
together to conduct some uh something uh
interesting<00:05:06.280><c> and</c><00:05:06.400><c> so</c><00:05:06.680><c> here</c><00:05:06.840><c> is</c><00:05:07.120><c> a</c><00:05:07.280><c> demo</c><00:05:08.000><c> and</c><00:05:08.199><c> I</c>

00:05:08.350 --> 00:05:08.360 align:start position:0%
interesting and so here is a demo and I
 

00:05:08.360 --> 00:05:12.230 align:start position:0%
interesting and so here is a demo and I
bring<00:05:08.720><c> my</c><00:05:09.000><c> phone</c><00:05:09.400><c> here</c><00:05:09.880><c> but</c><00:05:10.560><c> due</c><00:05:10.800><c> to</c><00:05:11.240><c> their</c>

00:05:12.230 --> 00:05:12.240 align:start position:0%
bring my phone here but due to their
 

00:05:12.240 --> 00:05:13.469 align:start position:0%
bring my phone here but due to their
time

00:05:13.469 --> 00:05:13.479 align:start position:0%
time
 

00:05:13.479 --> 00:05:15.710 align:start position:0%
time
liation<00:05:14.479><c> if</c><00:05:14.600><c> you</c><00:05:14.759><c> got</c><00:05:15.039><c> interesting</c><00:05:15.440><c> I</c><00:05:15.520><c> can</c>

00:05:15.710 --> 00:05:15.720 align:start position:0%
liation if you got interesting I can
 

00:05:15.720 --> 00:05:17.870 align:start position:0%
liation if you got interesting I can
show<00:05:15.919><c> you</c><00:05:16.160><c> after</c><00:05:16.680><c> after</c><00:05:17.000><c> this</c><00:05:17.199><c> talk</c><00:05:17.639><c> and</c>

00:05:17.870 --> 00:05:17.880 align:start position:0%
show you after after this talk and
 

00:05:17.880 --> 00:05:20.749 align:start position:0%
show you after after this talk and
another<00:05:18.120><c> demo</c><00:05:18.440><c> is</c><00:05:18.800><c> called</c><00:05:19.120><c> local</c><00:05:19.840><c> RM</c><00:05:20.440><c> and</c><00:05:20.600><c> I</c>

00:05:20.749 --> 00:05:20.759 align:start position:0%
another demo is called local RM and I
 

00:05:20.759 --> 00:05:24.029 align:start position:0%
another demo is called local RM and I
bring<00:05:21.039><c> the</c><00:05:21.199><c> Lama</c><00:05:21.520><c> 3</c><00:05:22.199><c> three</c><00:05:22.560><c> billion</c><00:05:22.919><c> to</c><00:05:23.160><c> the</c><00:05:23.680><c> to</c>

00:05:24.029 --> 00:05:24.039 align:start position:0%
bring the Lama 3 three billion to the to
 

00:05:24.039 --> 00:05:26.189 align:start position:0%
bring the Lama 3 three billion to the to
to<00:05:24.240><c> to</c><00:05:24.400><c> to</c><00:05:24.560><c> the</c><00:05:24.639><c> phones</c><00:05:25.039><c> and</c><00:05:25.240><c> I</c><00:05:25.360><c> can</c><00:05:25.520><c> show</c><00:05:25.840><c> it</c>

00:05:26.189 --> 00:05:26.199 align:start position:0%
to to to the phones and I can show it
 

00:05:26.199 --> 00:05:28.950 align:start position:0%
to to to the phones and I can show it
after<00:05:26.440><c> the</c><00:05:26.639><c> talk</c><00:05:27.199><c> so</c><00:05:27.960><c> that's</c><00:05:28.120><c> all</c><00:05:28.440><c> and</c><00:05:28.720><c> about</c>

00:05:28.950 --> 00:05:28.960 align:start position:0%
after the talk so that's all and about
 

00:05:28.960 --> 00:05:31.070 align:start position:0%
after the talk so that's all and about
myself<00:05:29.319><c> I'm</c><00:05:29.720><c> partner</c><00:05:30.039><c> of</c><00:05:30.160><c> the</c><00:05:30.319><c> VC</c><00:05:30.639><c> labs</c><00:05:30.880><c> and</c>

00:05:31.070 --> 00:05:31.080 align:start position:0%
myself I'm partner of the VC labs and
 

00:05:31.080 --> 00:05:34.189 align:start position:0%
myself I'm partner of the VC labs and
fin<00:05:31.319><c> year</c><00:05:31.440><c> PhD</c><00:05:31.800><c> at</c><00:05:32.639><c> and</c><00:05:32.840><c> my</c><00:05:32.960><c> us</c><00:05:33.440><c> about</c><00:05:33.880><c> their</c>

00:05:34.189 --> 00:05:34.199 align:start position:0%
fin year PhD at and my us about their
 

00:05:34.199 --> 00:05:38.749 align:start position:0%
fin year PhD at and my us about their
database<00:05:34.600><c> SS</c><00:05:35.600><c> thank</c><00:05:35.880><c> you</c><00:05:36.880><c> thank</c><00:05:37.039><c> you</c><00:05:37.479><c> uh</c><00:05:37.680><c> s</c><00:05:38.560><c> uh</c>

00:05:38.749 --> 00:05:38.759 align:start position:0%
database SS thank you thank you uh s uh
 

00:05:38.759 --> 00:05:41.710 align:start position:0%
database SS thank you thank you uh s uh
do<00:05:38.880><c> we</c><00:05:39.039><c> have</c><00:05:39.280><c> questions</c><00:05:39.600><c> for</c><00:05:40.319><c> our</c><00:05:40.720><c> friend</c>

00:05:41.710 --> 00:05:41.720 align:start position:0%
do we have questions for our friend
 

00:05:41.720 --> 00:05:43.990 align:start position:0%
do we have questions for our friend
amazing<00:05:42.120><c> speaker</c>

00:05:43.990 --> 00:05:44.000 align:start position:0%
amazing speaker
 

00:05:44.000 --> 00:05:46.230 align:start position:0%
amazing speaker
here

00:05:46.230 --> 00:05:46.240 align:start position:0%
here
 

00:05:46.240 --> 00:05:48.189 align:start position:0%
here
okay<00:05:47.240><c> he</c><00:05:47.400><c> there</c><00:05:47.520><c> thank</c><00:05:47.680><c> you</c><00:05:47.800><c> this</c><00:05:47.880><c> is</c><00:05:48.000><c> great</c>

00:05:48.189 --> 00:05:48.199 align:start position:0%
okay he there thank you this is great
 

00:05:48.199 --> 00:05:49.670 align:start position:0%
okay he there thank you this is great
that<00:05:48.280><c> you're</c><00:05:48.440><c> working</c><00:05:48.680><c> on</c><00:05:48.919><c> like</c><00:05:49.160><c> clients</c><00:05:49.520><c> in</c>

00:05:49.670 --> 00:05:49.680 align:start position:0%
that you're working on like clients in
 

00:05:49.680 --> 00:05:52.110 align:start position:0%
that you're working on like clients in
the<00:05:49.919><c> the</c><00:05:50.080><c> ecosystem</c><00:05:50.880><c> yeah</c><00:05:51.240><c> um</c><00:05:51.720><c> how</c><00:05:51.840><c> long</c><00:05:52.000><c> does</c>

00:05:52.110 --> 00:05:52.120 align:start position:0%
the the ecosystem yeah um how long does
 

00:05:52.120 --> 00:05:53.550 align:start position:0%
the the ecosystem yeah um how long does
it<00:05:52.240><c> take</c><00:05:52.400><c> for</c><00:05:52.560><c> the</c><00:05:52.639><c> client</c><00:05:52.919><c> to</c><00:05:53.000><c> be</c><00:05:53.160><c> connected</c>

00:05:53.550 --> 00:05:53.560 align:start position:0%
it take for the client to be connected
 

00:05:53.560 --> 00:05:55.510 align:start position:0%
it take for the client to be connected
to<00:05:53.720><c> the</c><00:05:53.880><c> network</c><00:05:54.440><c> and</c><00:05:54.560><c> then</c><00:05:54.759><c> how</c><00:05:55.000><c> quick</c><00:05:55.319><c> can</c>

00:05:55.510 --> 00:05:55.520 align:start position:0%
to the network and then how quick can
 

00:05:55.520 --> 00:05:57.469 align:start position:0%
to the network and then how quick can
you<00:05:55.919><c> for</c><00:05:56.080><c> example</c><00:05:56.360><c> do</c><00:05:56.520><c> an</c><00:05:56.680><c> eth</c><00:05:57.000><c> call</c><00:05:57.280><c> and</c>

00:05:57.469 --> 00:05:57.479 align:start position:0%
you for example do an eth call and
 

00:05:57.479 --> 00:05:59.670 align:start position:0%
you for example do an eth call and
validate<00:05:58.039><c> that</c><00:05:58.560><c> if</c><00:05:58.680><c> you</c><00:05:58.800><c> build</c><00:05:59.000><c> a</c><00:05:59.280><c> mobile</c>

00:05:59.670 --> 00:05:59.680 align:start position:0%
validate that if you build a mobile
 

00:05:59.680 --> 00:06:01.749 align:start position:0%
validate that if you build a mobile
application<00:06:00.120><c> on</c><00:06:00.319><c> top</c><00:06:00.759><c> and</c><00:06:00.960><c> and</c><00:06:01.120><c> how</c><00:06:01.319><c> secure</c><00:06:01.639><c> is</c>

00:06:01.749 --> 00:06:01.759 align:start position:0%
application on top and and how secure is
 

00:06:01.759 --> 00:06:04.270 align:start position:0%
application on top and and how secure is
it<00:06:01.919><c> at</c><00:06:02.039><c> the</c><00:06:02.120><c> end</c><00:06:02.319><c> maybe</c><00:06:02.600><c> you</c><00:06:02.680><c> can</c><00:06:02.840><c> talk</c><00:06:03.000><c> to</c><00:06:03.280><c> that</c>

00:06:04.270 --> 00:06:04.280 align:start position:0%
it at the end maybe you can talk to that
 

00:06:04.280 --> 00:06:06.270 align:start position:0%
it at the end maybe you can talk to that
so<00:06:04.600><c> actually</c><00:06:04.919><c> is</c><00:06:05.000><c> there</c><00:06:05.199><c> ISM</c><00:06:05.720><c> protocol</c>

00:06:06.270 --> 00:06:06.280 align:start position:0%
so actually is there ISM protocol
 

00:06:06.280 --> 00:06:09.230 align:start position:0%
so actually is there ISM protocol
provided<00:06:07.000><c> a</c><00:06:07.599><c> a</c><00:06:07.800><c> native</c><00:06:08.240><c> function</c><00:06:08.639><c> called</c><00:06:08.919><c> G</c>

00:06:09.230 --> 00:06:09.240 align:start position:0%
provided a a native function called G
 

00:06:09.240 --> 00:06:11.790 align:start position:0%
provided a a native function called G
proof<00:06:10.000><c> and</c><00:06:10.160><c> you</c><00:06:10.319><c> can</c><00:06:10.560><c> use</c><00:06:10.800><c> this</c><00:06:11.039><c> G</c><00:06:11.280><c> proof</c><00:06:11.599><c> to</c>

00:06:11.790 --> 00:06:11.800 align:start position:0%
proof and you can use this G proof to
 

00:06:11.800 --> 00:06:14.230 align:start position:0%
proof and you can use this G proof to
verify<00:06:12.240><c> the</c><00:06:12.400><c> data</c><00:06:12.720><c> from</c><00:06:12.919><c> the</c><00:06:13.039><c> other</c><00:06:13.319><c> client</c><00:06:14.039><c> so</c>

00:06:14.230 --> 00:06:14.240 align:start position:0%
verify the data from the other client so
 

00:06:14.240 --> 00:06:16.350 align:start position:0%
verify the data from the other client so
the<00:06:14.360><c> heers</c><00:06:14.919><c> basically</c><00:06:15.280><c> the</c><00:06:15.400><c> heers</c><00:06:15.800><c> work</c><00:06:16.120><c> that</c>

00:06:16.350 --> 00:06:16.360 align:start position:0%
the heers basically the heers work that
 

00:06:16.360 --> 00:06:19.150 align:start position:0%
the heers basically the heers work that
you<00:06:16.440><c> can</c><00:06:16.599><c> verify</c><00:06:17.560><c> any</c><00:06:17.919><c> data</c><00:06:18.240><c> from</c><00:06:18.599><c> untrusted</c>

00:06:19.150 --> 00:06:19.160 align:start position:0%
you can verify any data from untrusted
 

00:06:19.160 --> 00:06:21.790 align:start position:0%
you can verify any data from untrusted
rpcs<00:06:20.120><c> in</c><00:06:20.240><c> a</c><00:06:20.360><c> local</c><00:06:20.680><c> way</c><00:06:20.880><c> because</c><00:06:21.240><c> the</c><00:06:21.400><c> protocol</c>

00:06:21.790 --> 00:06:21.800 align:start position:0%
rpcs in a local way because the protocol
 

00:06:21.800 --> 00:06:23.909 align:start position:0%
rpcs in a local way because the protocol
cannot<00:06:22.039><c> be</c><00:06:22.160><c> changed</c><00:06:22.840><c> so</c><00:06:23.080><c> that's</c><00:06:23.400><c> really</c><00:06:23.759><c> how</c>

00:06:23.909 --> 00:06:23.919 align:start position:0%
cannot be changed so that's really how
 

00:06:23.919 --> 00:06:27.909 align:start position:0%
cannot be changed so that's really how
to<00:06:24.160><c> guarantee</c><00:06:24.520><c> the</c><00:06:25.199><c> security</c><00:06:26.199><c> yeah</c><00:06:26.400><c> no</c><00:06:26.680><c> I</c><00:06:27.000><c> um</c><00:06:27.479><c> I</c>

00:06:27.909 --> 00:06:27.919 align:start position:0%
to guarantee the security yeah no I um I
 

00:06:27.919 --> 00:06:29.830 align:start position:0%
to guarantee the security yeah no I um I
understand<00:06:28.120><c> that</c><00:06:28.319><c> I've</c><00:06:28.960><c> I'm</c><00:06:29.080><c> in</c><00:06:29.199><c> the</c><00:06:29.319><c> same</c><00:06:29.639><c> v</c>

00:06:29.830 --> 00:06:29.840 align:start position:0%
understand that I've I'm in the same v
 

00:06:29.840 --> 00:06:31.830 align:start position:0%
understand that I've I'm in the same v
as<00:06:29.960><c> you</c><00:06:30.160><c> but</c><00:06:30.360><c> if</c><00:06:30.440><c> you</c><00:06:30.560><c> do</c><00:06:30.720><c> an</c><00:06:30.880><c> eth</c><00:06:31.240><c> call</c><00:06:31.680><c> right</c>

00:06:31.830 --> 00:06:31.840 align:start position:0%
as you but if you do an eth call right
 

00:06:31.840 --> 00:06:32.909 align:start position:0%
as you but if you do an eth call right
which<00:06:31.960><c> you</c><00:06:32.039><c> want</c><00:06:32.160><c> to</c><00:06:32.280><c> do</c><00:06:32.440><c> you</c><00:06:32.520><c> want</c><00:06:32.599><c> to</c><00:06:32.720><c> do</c>

00:06:32.909 --> 00:06:32.919 align:start position:0%
which you want to do you want to do
 

00:06:32.919 --> 00:06:35.510 align:start position:0%
which you want to do you want to do
method<00:06:33.280><c> call</c><00:06:34.039><c> you</c><00:06:34.160><c> don't</c><00:06:34.319><c> know</c><00:06:34.520><c> if</c><00:06:34.680><c> the</c><00:06:34.919><c> VM</c>

00:06:35.510 --> 00:06:35.520 align:start position:0%
method call you don't know if the VM
 

00:06:35.520 --> 00:06:37.909 align:start position:0%
method call you don't know if the VM
that<00:06:35.680><c> is</c><00:06:35.840><c> on</c><00:06:36.000><c> the</c><00:06:36.199><c> remote</c><00:06:36.599><c> side</c><00:06:36.840><c> is</c><00:06:37.039><c> executing</c>

00:06:37.909 --> 00:06:37.919 align:start position:0%
that is on the remote side is executing
 

00:06:37.919 --> 00:06:39.670 align:start position:0%
that is on the remote side is executing
correctly<00:06:38.360><c> so</c><00:06:38.560><c> do</c><00:06:38.639><c> you</c><00:06:38.720><c> have</c><00:06:38.800><c> a</c><00:06:38.919><c> local</c><00:06:39.199><c> VM</c><00:06:39.560><c> or</c>

00:06:39.670 --> 00:06:39.680 align:start position:0%
correctly so do you have a local VM or
 

00:06:39.680 --> 00:06:41.350 align:start position:0%
correctly so do you have a local VM or
like<00:06:39.840><c> how</c><00:06:39.919><c> do</c><00:06:40.039><c> you</c><00:06:40.160><c> solve</c><00:06:40.400><c> that</c>

00:06:41.350 --> 00:06:41.360 align:start position:0%
like how do you solve that
 

00:06:41.360 --> 00:06:44.070 align:start position:0%
like how do you solve that
problem<00:06:42.360><c> wait</c><00:06:42.800><c> I</c><00:06:42.880><c> think</c><00:06:43.080><c> the</c><00:06:43.280><c> L</c><00:06:43.520><c> client</c><00:06:43.759><c> do</c><00:06:43.880><c> not</c>

00:06:44.070 --> 00:06:44.080 align:start position:0%
problem wait I think the L client do not
 

00:06:44.080 --> 00:06:45.830 align:start position:0%
problem wait I think the L client do not
have<00:06:44.240><c> the</c><00:06:44.400><c> local</c><00:06:44.720><c> VM</c><00:06:45.120><c> they</c><00:06:45.280><c> just</c><00:06:45.440><c> the</c><00:06:45.599><c> use</c>

00:06:45.830 --> 00:06:45.840 align:start position:0%
have the local VM they just the use
 

00:06:45.840 --> 00:06:48.710 align:start position:0%
have the local VM they just the use
their<00:06:46.840><c> just</c><00:06:47.160><c> use</c><00:06:47.319><c> their</c><00:06:47.520><c> get</c><00:06:47.759><c> proof</c><00:06:48.039><c> to</c><00:06:48.240><c> verify</c>

00:06:48.710 --> 00:06:48.720 align:start position:0%
their just use their get proof to verify
 

00:06:48.720 --> 00:06:51.390 align:start position:0%
their just use their get proof to verify
their<00:06:49.000><c> correctness</c><00:06:49.599><c> of</c><00:06:49.800><c> their</c><00:06:50.360><c> mot</c>

00:06:51.390 --> 00:06:51.400 align:start position:0%
their correctness of their mot
 

00:06:51.400 --> 00:06:53.830 align:start position:0%
their correctness of their mot
tree<00:06:52.400><c> yeah</c><00:06:52.560><c> but</c><00:06:52.759><c> with</c><00:06:52.919><c> the</c><00:06:53.080><c> get</c><00:06:53.319><c> proof</c><00:06:53.560><c> you</c><00:06:53.680><c> can</c>

00:06:53.830 --> 00:06:53.840 align:start position:0%
tree yeah but with the get proof you can
 

00:06:53.840 --> 00:06:56.629 align:start position:0%
tree yeah but with the get proof you can
only<00:06:54.720><c> prove</c><00:06:55.080><c> the</c><00:06:55.240><c> storage</c><00:06:55.919><c> not</c><00:06:56.120><c> the</c><00:06:56.280><c> result</c><00:06:56.520><c> of</c>

00:06:56.629 --> 00:06:56.639 align:start position:0%
only prove the storage not the result of
 

00:06:56.639 --> 00:06:59.869 align:start position:0%
only prove the storage not the result of
a<00:06:56.800><c> call</c><00:06:57.520><c> yes</c><00:06:57.879><c> yes</c><00:06:58.240><c> oh</c><00:06:58.479><c> that</c><00:06:58.680><c> part</c><00:06:58.960><c> is</c><00:06:59.240><c> that</c><00:06:59.720><c> want</c>

00:06:59.869 --> 00:06:59.879 align:start position:0%
a call yes yes oh that part is that want
 

00:06:59.879 --> 00:07:03.189 align:start position:0%
a call yes yes oh that part is that want
to<00:07:00.319><c> you</c><00:07:00.639><c> to</c><00:07:01.120><c> to</c><00:07:01.360><c> to</c><00:07:01.639><c> introduce</c><00:07:02.160><c> their</c><00:07:02.520><c> AI</c><00:07:02.840><c> agent</c>

00:07:03.189 --> 00:07:03.199 align:start position:0%
to you to to to introduce their AI agent
 

00:07:03.199 --> 00:07:06.270 align:start position:0%
to you to to to introduce their AI agent
part<00:07:03.520><c> like</c><00:07:03.680><c> we</c><00:07:03.840><c> use</c><00:07:04.120><c> RM</c><00:07:04.960><c> to</c><00:07:05.199><c> detect</c><00:07:05.919><c> whether</c>

00:07:06.270 --> 00:07:06.280 align:start position:0%
part like we use RM to detect whether
 

00:07:06.280 --> 00:07:09.230 align:start position:0%
part like we use RM to detect whether
the<00:07:06.639><c> core</c><00:07:06.879><c> is</c><00:07:07.360><c> malicious</c><00:07:07.840><c> or</c><00:07:08.000><c> not</c><00:07:08.599><c> to</c><00:07:08.840><c> help</c>

00:07:09.230 --> 00:07:09.240 align:start position:0%
the core is malicious or not to help
 

00:07:09.240 --> 00:07:10.710 align:start position:0%
the core is malicious or not to help
because<00:07:09.479><c> the</c><00:07:09.639><c> light</c><00:07:10.240><c> actually</c><00:07:10.560><c> the</c>

00:07:10.710 --> 00:07:10.720 align:start position:0%
because the light actually the
 

00:07:10.720 --> 00:07:12.350 align:start position:0%
because the light actually the
functionality<00:07:11.280><c> of</c><00:07:11.360><c> the</c><00:07:11.479><c> light</c><00:07:11.960><c> is</c><00:07:12.080><c> very</c>

00:07:12.350 --> 00:07:12.360 align:start position:0%
functionality of the light is very
 

00:07:12.360 --> 00:07:14.790 align:start position:0%
functionality of the light is very
limited<00:07:13.039><c> so</c><00:07:13.280><c> far</c><00:07:13.720><c> so</c><00:07:13.879><c> we</c><00:07:14.000><c> want</c><00:07:14.120><c> to</c><00:07:14.319><c> extend</c>

00:07:14.790 --> 00:07:14.800 align:start position:0%
limited so far so we want to extend
 

00:07:14.800 --> 00:07:16.790 align:start position:0%
limited so far so we want to extend
something<00:07:15.240><c> new</c><00:07:15.639><c> that's</c><00:07:15.879><c> was</c><00:07:16.080><c> this</c><00:07:16.400><c> Mission</c>

00:07:16.790 --> 00:07:16.800 align:start position:0%
something new that's was this Mission
 

00:07:16.800 --> 00:07:21.309 align:start position:0%
something new that's was this Mission
yeah<00:07:17.800><c> next</c>

00:07:21.309 --> 00:07:21.319 align:start position:0%
 
 

00:07:21.319 --> 00:07:25.550 align:start position:0%
 
question<00:07:22.479><c> um</c><00:07:23.479><c> okay</c><00:07:24.080><c> so</c><00:07:25.080><c> since</c><00:07:25.280><c> you</c><00:07:25.400><c> are</c>

00:07:25.550 --> 00:07:25.560 align:start position:0%
question um okay so since you are
 

00:07:25.560 --> 00:07:27.350 align:start position:0%
question um okay so since you are
working<00:07:25.800><c> on</c><00:07:26.000><c> mobile</c><00:07:26.479><c> right</c><00:07:26.680><c> there's</c><00:07:27.039><c> another</c>

00:07:27.350 --> 00:07:27.360 align:start position:0%
working on mobile right there's another
 

00:07:27.360 --> 00:07:29.909 align:start position:0%
working on mobile right there's another
constraint<00:07:27.800><c> which</c><00:07:28.000><c> is</c><00:07:28.199><c> power</c><00:07:28.960><c> so</c><00:07:29.160><c> like</c><00:07:29.639><c> um</c>

00:07:29.909 --> 00:07:29.919 align:start position:0%
constraint which is power so like um
 

00:07:29.919 --> 00:07:32.309 align:start position:0%
constraint which is power so like um
have<00:07:30.360><c> like</c><00:07:30.599><c> how's</c><00:07:30.960><c> the</c><00:07:31.280><c> power</c><00:07:31.560><c> consumption</c><00:07:32.080><c> on</c>

00:07:32.309 --> 00:07:32.319 align:start position:0%
have like how's the power consumption on
 

00:07:32.319 --> 00:07:35.110 align:start position:0%
have like how's the power consumption on
phones<00:07:33.199><c> running</c><00:07:33.759><c> on</c>

00:07:35.110 --> 00:07:35.120 align:start position:0%
phones running on
 

00:07:35.120 --> 00:07:38.390 align:start position:0%
phones running on
us<00:07:36.120><c> you</c><00:07:36.280><c> mean</c><00:07:36.840><c> the</c><00:07:37.080><c> the</c><00:07:37.280><c> like</c><00:07:37.479><c> battery</c><00:07:37.879><c> life</c>

00:07:38.390 --> 00:07:38.400 align:start position:0%
us you mean the the like battery life
 

00:07:38.400 --> 00:07:40.790 align:start position:0%
us you mean the the like battery life
like<00:07:38.720><c> how</c><00:07:39.199><c> oh</c><00:07:39.479><c> did</c><00:07:39.639><c> you</c><00:07:39.800><c> optimize</c><00:07:40.280><c> for</c><00:07:40.440><c> it</c><00:07:40.560><c> or</c>

00:07:40.790 --> 00:07:40.800 align:start position:0%
like how oh did you optimize for it or
 

00:07:40.800 --> 00:07:41.990 align:start position:0%
like how oh did you optimize for it or
so<00:07:40.960><c> actually</c><00:07:41.199><c> we</c><00:07:41.319><c> are</c><00:07:41.440><c> working</c><00:07:41.680><c> on</c><00:07:41.840><c> a</c>

00:07:41.990 --> 00:07:42.000 align:start position:0%
so actually we are working on a
 

00:07:42.000 --> 00:07:45.869 align:start position:0%
so actually we are working on a
benchmark<00:07:42.639><c> like</c><00:07:43.039><c> how</c><00:07:43.199><c> many</c><00:07:44.039><c> um</c><00:07:44.440><c> CS</c><00:07:45.240><c> Bas</c><00:07:45.639><c> can</c>

00:07:45.869 --> 00:07:45.879 align:start position:0%
benchmark like how many um CS Bas can
 

00:07:45.879 --> 00:07:50.110 align:start position:0%
benchmark like how many um CS Bas can
call<00:07:46.400><c> on</c><00:07:46.759><c> current</c><00:07:47.199><c> mobile</c><00:07:47.520><c> devices</c><00:07:48.520><c> yeah</c>

00:07:50.110 --> 00:07:50.120 align:start position:0%
call on current mobile devices yeah
 

00:07:50.120 --> 00:07:53.990 align:start position:0%
call on current mobile devices yeah
okay<00:07:51.120><c> um</c><00:07:51.479><c> a</c><00:07:51.680><c> followup</c><00:07:52.400><c> to</c><00:07:52.680><c> the</c><00:07:53.479><c> previous</c>

00:07:53.990 --> 00:07:54.000 align:start position:0%
okay um a followup to the previous
 

00:07:54.000 --> 00:07:56.909 align:start position:0%
okay um a followup to the previous
question<00:07:54.520><c> about</c><00:07:54.960><c> how</c><00:07:55.479><c> e</c><00:07:55.919><c> call</c>

00:07:56.909 --> 00:07:56.919 align:start position:0%
question about how e call
 

00:07:56.919 --> 00:08:00.029 align:start position:0%
question about how e call
Works<00:07:57.919><c> um</c><00:07:58.879><c> I</c>

00:08:00.029 --> 00:08:00.039 align:start position:0%
Works um I
 

00:08:00.039 --> 00:08:02.869 align:start position:0%
Works um I
so<00:08:00.759><c> the</c><00:08:00.919><c> way</c><00:08:01.120><c> how</c><00:08:01.280><c> it</c><00:08:01.400><c> works</c><00:08:01.759><c> is</c><00:08:01.960><c> you</c><00:08:02.199><c> have</c><00:08:02.440><c> a</c>

00:08:02.869 --> 00:08:02.879 align:start position:0%
so the way how it works is you have a
 

00:08:02.879 --> 00:08:07.670 align:start position:0%
so the way how it works is you have a
local<00:08:03.560><c> evm</c><00:08:04.360><c> inside</c><00:08:05.080><c> helos</c><00:08:06.080><c> they</c><00:08:06.240><c> used</c><00:08:06.800><c> the</c><00:08:07.199><c> red</c>

00:08:07.670 --> 00:08:07.680 align:start position:0%
local evm inside helos they used the red
 

00:08:07.680 --> 00:08:13.430 align:start position:0%
local evm inside helos they used the red
evm<00:08:08.360><c> revm</c><00:08:09.199><c> yeah</c><00:08:10.120><c> and</c><00:08:11.120><c> it</c><00:08:11.720><c> uh</c><00:08:11.879><c> uses</c><00:08:12.319><c> e</c><00:08:12.720><c> get</c><00:08:13.000><c> proof</c>

00:08:13.430 --> 00:08:13.440 align:start position:0%
evm revm yeah and it uh uses e get proof
 

00:08:13.440 --> 00:08:15.869 align:start position:0%
evm revm yeah and it uh uses e get proof
to<00:08:13.680><c> fetch</c><00:08:14.039><c> the</c><00:08:14.199><c> code</c><00:08:14.840><c> yes</c><00:08:15.039><c> you</c><00:08:15.159><c> can</c><00:08:15.520><c> get</c><00:08:15.720><c> the</c>

00:08:15.869 --> 00:08:15.879 align:start position:0%
to fetch the code yes you can get the
 

00:08:15.879 --> 00:08:18.950 align:start position:0%
to fetch the code yes you can get the
code<00:08:16.199><c> from</c><00:08:16.440><c> the</c><00:08:16.680><c> state</c><00:08:17.080><c> tree</c><00:08:17.680><c> yes</c><00:08:17.960><c> puts</c><00:08:18.199><c> it</c><00:08:18.400><c> in</c>

00:08:18.950 --> 00:08:18.960 align:start position:0%
code from the state tree yes puts it in
 

00:08:18.960 --> 00:08:22.029 align:start position:0%
code from the state tree yes puts it in
and<00:08:19.199><c> whenever</c><00:08:20.120><c> the</c><00:08:20.280><c> evm</c><00:08:20.759><c> needs</c><00:08:21.000><c> some</c><00:08:21.280><c> storage</c>

00:08:22.029 --> 00:08:22.039 align:start position:0%
and whenever the evm needs some storage
 

00:08:22.039 --> 00:08:24.589 align:start position:0%
and whenever the evm needs some storage
that<00:08:23.000><c> um</c><00:08:23.360><c> it</c><00:08:23.560><c> doesn't</c><00:08:23.919><c> have</c><00:08:24.159><c> available</c>

00:08:24.589 --> 00:08:24.599 align:start position:0%
that um it doesn't have available
 

00:08:24.599 --> 00:08:26.710 align:start position:0%
that um it doesn't have available
locally<00:08:24.960><c> it</c><00:08:25.080><c> is</c><00:08:25.240><c> another</c><00:08:25.560><c> E</c><00:08:25.879><c> get</c><00:08:26.080><c> proof</c><00:08:26.520><c> like</c>

00:08:26.710 --> 00:08:26.720 align:start position:0%
locally it is another E get proof like
 

00:08:26.720 --> 00:08:28.510 align:start position:0%
locally it is another E get proof like
it's<00:08:26.879><c> a</c><00:08:27.000><c> lot</c><00:08:27.159><c> of</c><00:08:27.280><c> round</c><00:08:27.599><c> trips</c><00:08:28.039><c> there</c><00:08:28.159><c> is</c><00:08:28.280><c> a</c><00:08:28.400><c> lot</c>

00:08:28.510 --> 00:08:28.520 align:start position:0%
it's a lot of round trips there is a lot
 

00:08:28.520 --> 00:08:30.029 align:start position:0%
it's a lot of round trips there is a lot
of<00:08:28.680><c> latency</c>

00:08:30.029 --> 00:08:30.039 align:start position:0%
of latency
 

00:08:30.039 --> 00:08:34.269 align:start position:0%
of latency
um<00:08:30.400><c> there</c><00:08:30.560><c> are</c><00:08:31.279><c> some</c><00:08:32.279><c> uh</c><00:08:33.080><c> efforts</c><00:08:33.640><c> on</c><00:08:33.800><c> the</c><00:08:34.000><c> way</c>

00:08:34.269 --> 00:08:34.279 align:start position:0%
um there are some uh efforts on the way
 

00:08:34.279 --> 00:08:37.990 align:start position:0%
um there are some uh efforts on the way
to<00:08:35.000><c> improve</c><00:08:35.640><c> that</c><00:08:36.360><c> to</c><00:08:36.560><c> make</c><00:08:36.680><c> it</c><00:08:36.839><c> more</c><00:08:37.120><c> compact</c>

00:08:37.990 --> 00:08:38.000 align:start position:0%
to improve that to make it more compact
 

00:08:38.000 --> 00:08:42.310 align:start position:0%
to improve that to make it more compact
but<00:08:38.680><c> if</c><00:08:38.959><c> because</c><00:08:39.479><c> the</c><00:08:39.959><c> Revan</c><00:08:40.519><c> runs</c><00:08:41.159><c> locally</c><00:08:42.159><c> it</c>

00:08:42.310 --> 00:08:42.320 align:start position:0%
but if because the Revan runs locally it
 

00:08:42.320 --> 00:08:44.550 align:start position:0%
but if because the Revan runs locally it
means<00:08:42.959><c> that</c><00:08:43.320><c> you</c><00:08:43.479><c> can</c><00:08:43.680><c> trust</c><00:08:43.959><c> the</c><00:08:44.120><c> local</c>

00:08:44.550 --> 00:08:44.560 align:start position:0%
means that you can trust the local
 

00:08:44.560 --> 00:08:47.470 align:start position:0%
means that you can trust the local
execution<00:08:45.560><c> and</c><00:08:45.800><c> later</c><00:08:46.120><c> on</c><00:08:46.480><c> if</c><00:08:46.600><c> you</c><00:08:46.800><c> have</c><00:08:47.000><c> seen</c>

00:08:47.470 --> 00:08:47.480 align:start position:0%
execution and later on if you have seen
 

00:08:47.480 --> 00:08:50.430 align:start position:0%
execution and later on if you have seen
yesterday's<00:08:48.440><c> talk</c><00:08:48.800><c> from</c><00:08:49.279><c> Justin</c><00:08:49.760><c> breake</c><00:08:50.240><c> with</c>

00:08:50.430 --> 00:08:50.440 align:start position:0%
yesterday's talk from Justin breake with
 

00:08:50.440 --> 00:08:53.190 align:start position:0%
yesterday's talk from Justin breake with
like<00:08:50.600><c> the</c><00:08:50.720><c> redacted</c><00:08:51.360><c> title</c><00:08:52.360><c> um</c><00:08:52.600><c> in</c><00:08:52.720><c> the</c><00:08:52.880><c> future</c>

00:08:53.190 --> 00:08:53.200 align:start position:0%
like the redacted title um in the future
 

00:08:53.200 --> 00:08:56.310 align:start position:0%
like the redacted title um in the future
once<00:08:53.560><c> we</c><00:08:53.800><c> have</c><00:08:54.200><c> CK</c><00:08:54.959><c> snarks</c><00:08:55.680><c> that</c><00:08:55.839><c> prove</c><00:08:56.160><c> the</c>

00:08:56.310 --> 00:08:56.320 align:start position:0%
once we have CK snarks that prove the
 

00:08:56.320 --> 00:08:58.190 align:start position:0%
once we have CK snarks that prove the
execution<00:08:56.920><c> and</c><00:08:57.040><c> the</c><00:08:57.200><c> server</c><00:08:57.560><c> can</c><00:08:57.720><c> also</c><00:08:58.000><c> do</c>

00:08:58.190 --> 00:08:58.200 align:start position:0%
execution and the server can also do
 

00:08:58.200 --> 00:09:01.590 align:start position:0%
execution and the server can also do
that<00:08:58.399><c> and</c><00:08:58.560><c> we</c><00:08:58.640><c> don't</c><00:08:58.800><c> need</c><00:08:58.959><c> the</c><00:08:59.120><c> local</c>

00:09:01.590 --> 00:09:01.600 align:start position:0%
 
 

00:09:01.600 --> 00:09:03.430 align:start position:0%
 
um<00:09:01.839><c> guys</c><00:09:02.079><c> thank</c><00:09:02.240><c> you</c><00:09:02.399><c> so</c><00:09:02.640><c> much</c><00:09:03.079><c> uh</c><00:09:03.200><c> we'll</c>

00:09:03.430 --> 00:09:03.440 align:start position:0%
um guys thank you so much uh we'll
 

00:09:03.440 --> 00:09:06.590 align:start position:0%
um guys thank you so much uh we'll
continue<00:09:03.920><c> this</c><00:09:04.160><c> conversation</c><00:09:05.600><c> meet</c>

00:09:06.590 --> 00:09:06.600 align:start position:0%
continue this conversation meet
 

00:09:06.600 --> 00:09:09.440 align:start position:0%
continue this conversation meet
backstage<00:09:07.160><c> and</c>