WEBVTT
Kind: captions
Language: en

00:00:00.000 --> 00:00:04.350 align:start position:0%
 
foreign

00:00:04.350 --> 00:00:04.360 align:start position:0%
 
 

00:00:04.360 --> 00:00:15.189 align:start position:0%
 
[Music]

00:00:15.189 --> 00:00:15.199 align:start position:0%
 
 

00:00:15.199 --> 00:00:17.750 align:start position:0%
 
I'm<00:00:16.199><c> the</c><00:00:16.260><c> founder</c><00:00:16.560><c> of</c><00:00:16.680><c> Easter</c><00:00:17.160><c> storage</c><00:00:17.340><c> today</c>

00:00:17.750 --> 00:00:17.760 align:start position:0%
I'm the founder of Easter storage today
 

00:00:17.760 --> 00:00:19.790 align:start position:0%
I'm the founder of Easter storage today
I<00:00:18.060><c> will</c><00:00:18.180><c> going</c><00:00:18.359><c> to</c><00:00:18.480><c> present</c><00:00:18.900><c> our</c><00:00:19.140><c> talk</c><00:00:19.380><c> on</c><00:00:19.619><c> the</c>

00:00:19.790 --> 00:00:19.800 align:start position:0%
I will going to present our talk on the
 

00:00:19.800 --> 00:00:22.189 align:start position:0%
I will going to present our talk on the
future<00:00:19.920><c> of</c><00:00:20.160><c> battery</c><00:00:20.539><c> Paving</c><00:00:21.539><c> the</c><00:00:21.660><c> way</c><00:00:21.840><c> to</c><00:00:22.020><c> the</c>

00:00:22.189 --> 00:00:22.199 align:start position:0%
future of battery Paving the way to the
 

00:00:22.199 --> 00:00:24.050 align:start position:0%
future of battery Paving the way to the
fully<00:00:22.560><c> Android</c><00:00:22.980><c> and</c><00:00:23.279><c> fully</c><00:00:23.460><c> decentral</c><00:00:23.880><c> as</c>

00:00:24.050 --> 00:00:24.060 align:start position:0%
fully Android and fully decentral as
 

00:00:24.060 --> 00:00:24.830 align:start position:0%
fully Android and fully decentral as
well

00:00:24.830 --> 00:00:24.840 align:start position:0%
well
 

00:00:24.840 --> 00:00:26.929 align:start position:0%
well
so<00:00:25.380><c> what</c><00:00:25.740><c> is</c><00:00:25.920><c> the</c><00:00:26.039><c> current</c><00:00:26.220><c> status</c><00:00:26.460><c> of</c><00:00:26.820><c> the</c>

00:00:26.929 --> 00:00:26.939 align:start position:0%
so what is the current status of the
 

00:00:26.939 --> 00:00:28.790 align:start position:0%
so what is the current status of the
central<00:00:27.180><c> as</c><00:00:27.480><c> well</c><00:00:27.660><c> so</c><00:00:28.260><c> we</c><00:00:28.439><c> have</c><00:00:28.619><c> a</c>

00:00:28.790 --> 00:00:28.800 align:start position:0%
central as well so we have a
 

00:00:28.800 --> 00:00:30.950 align:start position:0%
central as well so we have a
decentralized<00:00:29.279><c> access</c><00:00:29.519><c> protocol</c><00:00:30.060><c> like</c><00:00:30.359><c> ipfs</c>

00:00:30.950 --> 00:00:30.960 align:start position:0%
decentralized access protocol like ipfs
 

00:00:30.960 --> 00:00:33.470 align:start position:0%
decentralized access protocol like ipfs
and<00:00:31.560><c> we</c><00:00:31.679><c> also</c><00:00:31.980><c> have</c><00:00:32.099><c> a</c><00:00:32.279><c> mature</c><00:00:32.579><c> P2P</c><00:00:33.120><c> Network</c>

00:00:33.470 --> 00:00:33.480 align:start position:0%
and we also have a mature P2P Network
 

00:00:33.480 --> 00:00:35.930 align:start position:0%
and we also have a mature P2P Network
layer<00:00:33.960><c> and</c><00:00:34.320><c> which</c><00:00:34.620><c> we</c><00:00:34.800><c> are</c><00:00:35.100><c> able</c><00:00:35.280><c> to</c><00:00:35.340><c> retrieve</c>

00:00:35.930 --> 00:00:35.940 align:start position:0%
layer and which we are able to retrieve
 

00:00:35.940 --> 00:00:37.790 align:start position:0%
layer and which we are able to retrieve
the<00:00:36.059><c> data</c><00:00:36.360><c> and</c><00:00:36.899><c> we</c><00:00:37.079><c> also</c><00:00:37.320><c> have</c><00:00:37.559><c> the</c>

00:00:37.790 --> 00:00:37.800 align:start position:0%
the data and we also have the
 

00:00:37.800 --> 00:00:40.369 align:start position:0%
the data and we also have the
incentivized<00:00:38.579><c> storage</c><00:00:38.760><c> layer</c><00:00:39.300><c> that</c><00:00:39.660><c> helps</c><00:00:40.260><c> to</c>

00:00:40.369 --> 00:00:40.379 align:start position:0%
incentivized storage layer that helps to
 

00:00:40.379 --> 00:00:44.090 align:start position:0%
incentivized storage layer that helps to
keep<00:00:40.800><c> the</c><00:00:41.040><c> data</c><00:00:41.340><c> consistency</c>

00:00:44.090 --> 00:00:44.100 align:start position:0%
keep the data consistency
 

00:00:44.100 --> 00:00:46.190 align:start position:0%
keep the data consistency
however<00:00:44.879><c> there</c><00:00:45.120><c> are</c><00:00:45.300><c> still</c><00:00:45.360><c> great</c><00:00:45.600><c> limitation</c>

00:00:46.190 --> 00:00:46.200 align:start position:0%
however there are still great limitation
 

00:00:46.200 --> 00:00:48.229 align:start position:0%
however there are still great limitation
of<00:00:46.500><c> current</c><00:00:46.800><c> uh</c><00:00:47.219><c> decentralized</c><00:00:47.820><c> Storage</c>

00:00:48.229 --> 00:00:48.239 align:start position:0%
of current uh decentralized Storage
 

00:00:48.239 --> 00:00:51.290 align:start position:0%
of current uh decentralized Storage
Solutions<00:00:48.660><c> first</c><00:00:49.559><c> those</c><00:00:50.520><c> storage</c><00:00:50.820><c> solution</c>

00:00:51.290 --> 00:00:51.300 align:start position:0%
Solutions first those storage solution
 

00:00:51.300 --> 00:00:55.010 align:start position:0%
Solutions first those storage solution
has<00:00:51.660><c> a</c><00:00:52.379><c> great</c><00:00:52.620><c> limits</c><00:00:53.280><c> on</c><00:00:53.579><c> the</c><00:00:53.940><c> semantics</c><00:00:54.420><c> in</c>

00:00:55.010 --> 00:00:55.020 align:start position:0%
has a great limits on the semantics in
 

00:00:55.020 --> 00:00:57.470 align:start position:0%
has a great limits on the semantics in
many<00:00:55.199><c> Workforce</c><00:00:56.039><c> static</c><00:00:56.280><c> files</c><00:00:56.640><c> which</c><00:00:57.239><c> means</c>

00:00:57.470 --> 00:00:57.480 align:start position:0%
many Workforce static files which means
 

00:00:57.480 --> 00:01:00.049 align:start position:0%
many Workforce static files which means
that<00:00:57.660><c> it's</c><00:00:57.840><c> very</c><00:00:58.079><c> inefficient</c><00:00:58.739><c> to</c><00:00:59.219><c> update</c><00:00:59.879><c> and</c>

00:01:00.049 --> 00:01:00.059 align:start position:0%
that it's very inefficient to update and
 

00:01:00.059 --> 00:01:02.630 align:start position:0%
that it's very inefficient to update and
delete<00:01:00.239><c> those</c><00:01:00.780><c> existing</c><00:01:01.260><c> files</c><00:01:01.680><c> even</c><00:01:02.039><c> just</c><00:01:02.399><c> a</c>

00:01:02.630 --> 00:01:02.640 align:start position:0%
delete those existing files even just a
 

00:01:02.640 --> 00:01:04.969 align:start position:0%
delete those existing files even just a
single<00:01:02.879><c> bias</c><00:01:03.180><c> that</c><00:01:03.300><c> is</c><00:01:03.420><c> changed</c><00:01:03.840><c> and</c><00:01:04.559><c> further</c>

00:01:04.969 --> 00:01:04.979 align:start position:0%
single bias that is changed and further
 

00:01:04.979 --> 00:01:08.270 align:start position:0%
single bias that is changed and further
there's<00:01:05.760><c> no</c><00:01:06.060><c> way</c><00:01:06.240><c> to</c><00:01:06.479><c> compose</c><00:01:07.020><c> this</c><00:01:07.740><c> data</c><00:01:07.979><c> in</c><00:01:08.100><c> a</c>

00:01:08.270 --> 00:01:08.280 align:start position:0%
there's no way to compose this data in a
 

00:01:08.280 --> 00:01:10.250 align:start position:0%
there's no way to compose this data in a
centralized<00:01:08.580><c> a</c><00:01:08.880><c> decentralized</c><00:01:09.420><c> way</c><00:01:09.600><c> so</c>

00:01:10.250 --> 00:01:10.260 align:start position:0%
centralized a decentralized way so
 

00:01:10.260 --> 00:01:12.350 align:start position:0%
centralized a decentralized way so
sometimes<00:01:10.619><c> we</c><00:01:10.799><c> have</c><00:01:10.920><c> to</c><00:01:11.100><c> rely</c><00:01:11.700><c> on</c><00:01:11.880><c> centralized</c>

00:01:12.350 --> 00:01:12.360 align:start position:0%
sometimes we have to rely on centralized
 

00:01:12.360 --> 00:01:15.230 align:start position:0%
sometimes we have to rely on centralized
server<00:01:13.020><c> second</c><00:01:13.680><c> is</c><00:01:14.340><c> that</c><00:01:14.460><c> all</c><00:01:14.700><c> these</c><00:01:14.939><c> projects</c>

00:01:15.230 --> 00:01:15.240 align:start position:0%
server second is that all these projects
 

00:01:15.240 --> 00:01:17.090 align:start position:0%
server second is that all these projects
they<00:01:15.479><c> have</c><00:01:15.659><c> their</c><00:01:15.840><c> ecosystem</c><00:01:16.380><c> which</c><00:01:16.860><c> means</c>

00:01:17.090 --> 00:01:17.100 align:start position:0%
they have their ecosystem which means
 

00:01:17.100 --> 00:01:19.010 align:start position:0%
they have their ecosystem which means
that<00:01:17.280><c> users</c><00:01:17.700><c> has</c><00:01:17.939><c> to</c><00:01:18.119><c> use</c><00:01:18.360><c> their</c><00:01:18.600><c> wallets</c>

00:01:19.010 --> 00:01:19.020 align:start position:0%
that users has to use their wallets
 

00:01:19.020 --> 00:01:21.890 align:start position:0%
that users has to use their wallets
tokens<00:01:19.920><c> and</c><00:01:20.220><c> addresses</c><00:01:20.640><c> in</c><00:01:21.240><c> order</c><00:01:21.360><c> to</c><00:01:21.600><c> be</c><00:01:21.780><c> able</c>

00:01:21.890 --> 00:01:21.900 align:start position:0%
tokens and addresses in order to be able
 

00:01:21.900 --> 00:01:25.010 align:start position:0%
tokens and addresses in order to be able
to<00:01:22.080><c> upload</c><00:01:22.500><c> those</c><00:01:22.619><c> files</c><00:01:23.040><c> to</c><00:01:23.280><c> their</c><00:01:23.460><c> systems</c>

00:01:25.010 --> 00:01:25.020 align:start position:0%
to upload those files to their systems
 

00:01:25.020 --> 00:01:27.710 align:start position:0%
to upload those files to their systems
so<00:01:25.979><c> with</c><00:01:26.280><c> these</c><00:01:26.520><c> problems</c><00:01:26.939><c> we</c><00:01:27.180><c> are</c><00:01:27.299><c> projecting</c>

00:01:27.710 --> 00:01:27.720 align:start position:0%
so with these problems we are projecting
 

00:01:27.720 --> 00:01:29.810 align:start position:0%
so with these problems we are projecting
what<00:01:28.140><c> the</c><00:01:28.320><c> features</c><00:01:28.740><c> that</c><00:01:28.920><c> we</c><00:01:29.100><c> need</c><00:01:29.340><c> in</c><00:01:29.700><c> the</c>

00:01:29.810 --> 00:01:29.820 align:start position:0%
what the features that we need in the
 

00:01:29.820 --> 00:01:32.749 align:start position:0%
what the features that we need in the
future<00:01:29.939><c> but</c><00:01:30.240><c> three</c><00:01:30.540><c> first</c><00:01:31.380><c> we</c><00:01:31.860><c> need</c><00:01:32.100><c> a</c><00:01:32.460><c> Rich</c>

00:01:32.749 --> 00:01:32.759 align:start position:0%
future but three first we need a Rich
 

00:01:32.759 --> 00:01:34.789 align:start position:0%
future but three first we need a Rich
Storage<00:01:33.180><c> semantics</c><00:01:33.780><c> in</c><00:01:34.080><c> a</c><00:01:34.259><c> decentralized</c>

00:01:34.789 --> 00:01:34.799 align:start position:0%
Storage semantics in a decentralized
 

00:01:34.799 --> 00:01:38.149 align:start position:0%
Storage semantics in a decentralized
storage<00:01:35.220><c> which</c><00:01:36.180><c> can</c><00:01:36.420><c> support</c><00:01:37.079><c> great</c><00:01:37.560><c> update</c>

00:01:38.149 --> 00:01:38.159 align:start position:0%
storage which can support great update
 

00:01:38.159 --> 00:01:41.390 align:start position:0%
storage which can support great update
delete<00:01:38.659><c> blobs</c><00:01:39.659><c> for</c><00:01:40.020><c> very</c><00:01:40.320><c> large</c><00:01:40.619><c> large</c><00:01:40.979><c> amount</c>

00:01:41.390 --> 00:01:41.400 align:start position:0%
delete blobs for very large large amount
 

00:01:41.400 --> 00:01:43.550 align:start position:0%
delete blobs for very large large amount
potentially<00:01:42.119><c> petabytes</c>

00:01:43.550 --> 00:01:43.560 align:start position:0%
potentially petabytes
 

00:01:43.560 --> 00:01:45.590 align:start position:0%
potentially petabytes
further<00:01:44.159><c> it</c><00:01:44.340><c> can</c><00:01:44.520><c> be</c><00:01:44.640><c> programmable</c><00:01:45.060><c> by</c><00:01:45.360><c> smart</c>

00:01:45.590 --> 00:01:45.600 align:start position:0%
further it can be programmable by smart
 

00:01:45.600 --> 00:01:47.630 align:start position:0%
further it can be programmable by smart
conscious<00:01:46.079><c> so</c><00:01:46.320><c> that</c><00:01:46.500><c> can</c><00:01:46.680><c> easily</c><00:01:47.040><c> compose</c><00:01:47.400><c> us</c>

00:01:47.630 --> 00:01:47.640 align:start position:0%
conscious so that can easily compose us
 

00:01:47.640 --> 00:01:50.929 align:start position:0%
conscious so that can easily compose us
data<00:01:48.380><c> with</c><00:01:49.380><c> the</c><00:01:49.560><c> larger</c><00:01:49.860><c> on</c><00:01:50.220><c> of</c><00:01:50.579><c> the</c><00:01:50.759><c> smart</c>

00:01:50.929 --> 00:01:50.939 align:start position:0%
data with the larger on of the smart
 

00:01:50.939 --> 00:01:53.210 align:start position:0%
data with the larger on of the smart
contracts<00:01:51.479><c> running</c><00:01:51.659><c> on</c><00:01:51.840><c> ethereum</c><00:01:52.320><c> and</c><00:01:53.040><c> second</c>

00:01:53.210 --> 00:01:53.220 align:start position:0%
contracts running on ethereum and second
 

00:01:53.220 --> 00:01:55.429 align:start position:0%
contracts running on ethereum and second
is<00:01:53.460><c> that</c><00:01:53.640><c> we</c><00:01:53.820><c> want</c><00:01:54.000><c> to</c><00:01:54.119><c> simplify</c><00:01:54.780><c> the</c><00:01:54.960><c> user</c><00:01:55.259><c> or</c>

00:01:55.429 --> 00:01:55.439 align:start position:0%
is that we want to simplify the user or
 

00:01:55.439 --> 00:01:57.469 align:start position:0%
is that we want to simplify the user or
body<00:01:55.619><c> which</c><00:01:56.340><c> means</c><00:01:56.579><c> that</c><00:01:56.700><c> the</c><00:01:56.939><c> user</c><00:01:57.240><c> just</c>

00:01:57.469 --> 00:01:57.479 align:start position:0%
body which means that the user just
 

00:01:57.479 --> 00:01:59.929 align:start position:0%
body which means that the user just
using<00:01:57.840><c> the</c><00:01:57.960><c> user</c><00:01:58.259><c> wallet</c><00:01:58.680><c> pay</c><00:01:59.100><c> ethereum</c><00:01:59.700><c> and</c>

00:01:59.929 --> 00:01:59.939 align:start position:0%
using the user wallet pay ethereum and
 

00:01:59.939 --> 00:02:03.530 align:start position:0%
using the user wallet pay ethereum and
is<00:02:00.119><c> able</c><00:02:00.479><c> to</c><00:02:00.659><c> upload</c><00:02:01.619><c> and</c><00:02:02.100><c> basically</c><00:02:02.700><c> store</c><00:02:03.299><c> a</c>

00:02:03.530 --> 00:02:03.540 align:start position:0%
is able to upload and basically store a
 

00:02:03.540 --> 00:02:05.690 align:start position:0%
is able to upload and basically store a
large<00:02:03.659><c> amount</c><00:02:03.899><c> of</c><00:02:04.079><c> data</c><00:02:04.320><c> on</c><00:02:04.619><c> top</c><00:02:04.799><c> of</c><00:02:04.920><c> the</c><00:02:05.159><c> who</c>

00:02:05.690 --> 00:02:05.700 align:start position:0%
large amount of data on top of the who
 

00:02:05.700 --> 00:02:08.449 align:start position:0%
large amount of data on top of the who
is<00:02:05.939><c> your</c><00:02:06.119><c> network</c><00:02:06.360><c> and</c><00:02:07.320><c> lastly</c><00:02:07.619><c> we</c><00:02:08.160><c> need</c><00:02:08.340><c> to</c>

00:02:08.449 --> 00:02:08.459 align:start position:0%
is your network and lastly we need to
 

00:02:08.459 --> 00:02:10.910 align:start position:0%
is your network and lastly we need to
have<00:02:08.640><c> a</c><00:02:08.880><c> nil</c><00:02:09.179><c> access</c><00:02:09.660><c> particle</c><00:02:10.380><c> that</c><00:02:10.560><c> is</c><00:02:10.679><c> able</c>

00:02:10.910 --> 00:02:10.920 align:start position:0%
have a nil access particle that is able
 

00:02:10.920 --> 00:02:14.809 align:start position:0%
have a nil access particle that is able
to<00:02:11.099><c> render</c><00:02:11.580><c> those</c><00:02:12.300><c> Dynamic</c><00:02:12.780><c> data</c><00:02:13.340><c> from</c><00:02:14.340><c> uh</c>

00:02:14.809 --> 00:02:14.819 align:start position:0%
to render those Dynamic data from uh
 

00:02:14.819 --> 00:02:16.570 align:start position:0%
to render those Dynamic data from uh
front<00:02:15.120><c> end</c><00:02:15.360><c> to</c><00:02:15.540><c> the</c><00:02:15.660><c> blockchain</c><00:02:16.020><c> and</c><00:02:16.260><c> storage</c>

00:02:16.570 --> 00:02:16.580 align:start position:0%
front end to the blockchain and storage
 

00:02:16.580 --> 00:02:20.030 align:start position:0%
front end to the blockchain and storage
without<00:02:17.580><c> any</c><00:02:17.819><c> centralized</c><00:02:18.300><c> identity</c>

00:02:20.030 --> 00:02:20.040 align:start position:0%
without any centralized identity
 

00:02:20.040 --> 00:02:22.190 align:start position:0%
without any centralized identity
so<00:02:20.580><c> what's</c><00:02:20.700><c> the</c><00:02:20.940><c> solution</c>

00:02:22.190 --> 00:02:22.200 align:start position:0%
so what's the solution
 

00:02:22.200 --> 00:02:23.690 align:start position:0%
so what's the solution
um thanks<00:02:22.440><c> to</c><00:02:22.680><c> the</c><00:02:22.860><c> latest</c><00:02:22.980><c> development</c><00:02:23.459><c> of</c>

00:02:23.690 --> 00:02:23.700 align:start position:0%
um thanks to the latest development of
 

00:02:23.700 --> 00:02:25.369 align:start position:0%
um thanks to the latest development of
the<00:02:23.819><c> ethernet</c><00:02:24.120><c> Technologies</c><00:02:24.660><c> we</c><00:02:25.200><c> believe</c>

00:02:25.369 --> 00:02:25.379 align:start position:0%
the ethernet Technologies we believe
 

00:02:25.379 --> 00:02:27.890 align:start position:0%
the ethernet Technologies we believe
that<00:02:25.680><c> we</c><00:02:25.920><c> are</c><00:02:26.099><c> now</c><00:02:26.280><c> at</c><00:02:26.640><c> a</c><00:02:26.819><c> position</c><00:02:26.940><c> that</c><00:02:27.360><c> we</c>

00:02:27.890 --> 00:02:27.900 align:start position:0%
that we are now at a position that we
 

00:02:27.900 --> 00:02:29.390 align:start position:0%
that we are now at a position that we
can<00:02:28.020><c> achieve</c><00:02:28.379><c> these</c><00:02:28.620><c> goals</c><00:02:28.920><c> in</c><00:02:29.099><c> the</c><00:02:29.220><c> near</c>

00:02:29.390 --> 00:02:29.400 align:start position:0%
can achieve these goals in the near
 

00:02:29.400 --> 00:02:32.089 align:start position:0%
can achieve these goals in the near
future<00:02:29.640><c> first</c><00:02:30.540><c> of</c><00:02:30.780><c> all</c><00:02:30.900><c> we</c><00:02:31.560><c> have</c><00:02:31.739><c> data</c>

00:02:32.089 --> 00:02:32.099 align:start position:0%
future first of all we have data
 

00:02:32.099 --> 00:02:33.830 align:start position:0%
future first of all we have data
availability<00:02:32.520><c> disability</c><00:02:33.120><c> thanks</c><00:02:33.599><c> to</c>

00:02:33.830 --> 00:02:33.840 align:start position:0%
availability disability thanks to
 

00:02:33.840 --> 00:02:36.650 align:start position:0%
availability disability thanks to
Thanksgiving<00:02:34.459><c> which</c><00:02:35.459><c> greatly</c><00:02:35.940><c> increase</c><00:02:36.239><c> the</c>

00:02:36.650 --> 00:02:36.660 align:start position:0%
Thanksgiving which greatly increase the
 

00:02:36.660 --> 00:02:39.229 align:start position:0%
Thanksgiving which greatly increase the
data<00:02:37.319><c> upload</c><00:02:37.739><c> speed</c><00:02:37.920><c> using</c><00:02:38.700><c> Advanced</c>

00:02:39.229 --> 00:02:39.239 align:start position:0%
data upload speed using Advanced
 

00:02:39.239 --> 00:02:41.509 align:start position:0%
data upload speed using Advanced
cryptography<00:02:40.020><c> Primitives</c>

00:02:41.509 --> 00:02:41.519 align:start position:0%
cryptography Primitives
 

00:02:41.519 --> 00:02:44.410 align:start position:0%
cryptography Primitives
and<00:02:42.060><c> second</c><00:02:42.300><c> is</c><00:02:42.959><c> that</c><00:02:43.200><c> we</c><00:02:43.440><c> are</c><00:02:43.560><c> able</c><00:02:43.739><c> to</c><00:02:43.920><c> build</c>

00:02:44.410 --> 00:02:44.420 align:start position:0%
and second is that we are able to build
 

00:02:44.420 --> 00:02:46.910 align:start position:0%
and second is that we are able to build
external<00:02:45.420><c> data</c><00:02:45.720><c> retention</c><00:02:46.019><c> Network</c><00:02:46.260><c> so</c><00:02:46.739><c> that</c>

00:02:46.910 --> 00:02:46.920 align:start position:0%
external data retention Network so that
 

00:02:46.920 --> 00:02:49.309 align:start position:0%
external data retention Network so that
we<00:02:47.099><c> only</c><00:02:47.220><c> store</c><00:02:47.580><c> corresponding</c><00:02:48.300><c> metadata</c><00:02:48.720><c> on</c>

00:02:49.309 --> 00:02:49.319 align:start position:0%
we only store corresponding metadata on
 

00:02:49.319 --> 00:02:51.470 align:start position:0%
we only store corresponding metadata on
ethereum<00:02:49.800><c> and</c><00:02:50.459><c> be</c><00:02:50.640><c> able</c><00:02:50.760><c> to</c><00:02:50.879><c> store</c><00:02:51.180><c> large</c>

00:02:51.470 --> 00:02:51.480 align:start position:0%
ethereum and be able to store large
 

00:02:51.480 --> 00:02:53.949 align:start position:0%
ethereum and be able to store large
amount<00:02:51.660><c> of</c><00:02:51.959><c> data</c><00:02:52.260><c> in</c><00:02:52.739><c> this</c><00:02:52.980><c> layer</c><00:02:53.400><c> 2</c><00:02:53.519><c> Network</c>

00:02:53.949 --> 00:02:53.959 align:start position:0%
amount of data in this layer 2 Network
 

00:02:53.959 --> 00:02:57.170 align:start position:0%
amount of data in this layer 2 Network
and<00:02:54.959><c> we</c><00:02:55.140><c> just</c><00:02:55.319><c> periodically</c><00:02:56.040><c> submit</c><00:02:56.940><c> the</c>

00:02:57.170 --> 00:02:57.180 align:start position:0%
and we just periodically submit the
 

00:02:57.180 --> 00:03:00.650 align:start position:0%
and we just periodically submit the
proof<00:02:57.599><c> of</c><00:02:57.840><c> storage</c><00:02:58.140><c> into</c><00:02:59.099><c> the</c><00:02:59.340><c> ethernet</c><00:02:59.760><c> so</c><00:03:00.480><c> it</c>

00:03:00.650 --> 00:03:00.660 align:start position:0%
proof of storage into the ethernet so it
 

00:03:00.660 --> 00:03:02.930 align:start position:0%
proof of storage into the ethernet so it
tells<00:03:01.019><c> that</c><00:03:01.140><c> everybody</c><00:03:01.379><c> can</c><00:03:01.860><c> check</c><00:03:02.160><c> the</c>

00:03:02.930 --> 00:03:02.940 align:start position:0%
tells that everybody can check the
 

00:03:02.940 --> 00:03:05.390 align:start position:0%
tells that everybody can check the
actual<00:03:03.180><c> data</c><00:03:03.599><c> the</c><00:03:04.019><c> latest</c><00:03:04.200><c> data</c><00:03:04.680><c> is</c><00:03:04.920><c> keep</c><00:03:05.099><c> in</c>

00:03:05.390 --> 00:03:05.400 align:start position:0%
actual data the latest data is keep in
 

00:03:05.400 --> 00:03:08.570 align:start position:0%
actual data the latest data is keep in
the<00:03:05.519><c> network</c><00:03:05.780><c> with</c><00:03:06.780><c> high</c><00:03:07.019><c> replication</c>

00:03:08.570 --> 00:03:08.580 align:start position:0%
the network with high replication
 

00:03:08.580 --> 00:03:11.210 align:start position:0%
the network with high replication
and<00:03:09.180><c> lastly</c><00:03:09.540><c> we</c><00:03:10.019><c> also</c><00:03:10.260><c> developed</c><00:03:10.680><c> our</c><00:03:10.739><c> website</c>

00:03:11.210 --> 00:03:11.220 align:start position:0%
and lastly we also developed our website
 

00:03:11.220 --> 00:03:13.390 align:start position:0%
and lastly we also developed our website
access<00:03:11.400><c> protocol</c><00:03:11.940><c> which</c><00:03:12.480><c> is</c><00:03:12.599><c> able</c><00:03:12.959><c> to</c>

00:03:13.390 --> 00:03:13.400 align:start position:0%
access protocol which is able to
 

00:03:13.400 --> 00:03:16.190 align:start position:0%
access protocol which is able to
decentralizedly<00:03:14.400><c> access</c><00:03:14.700><c> those</c><00:03:15.360><c> web</c><00:03:15.599><c> objects</c>

00:03:16.190 --> 00:03:16.200 align:start position:0%
decentralizedly access those web objects
 

00:03:16.200 --> 00:03:19.550 align:start position:0%
decentralizedly access those web objects
caused<00:03:16.860><c> by</c><00:03:17.040><c> smart</c><00:03:17.400><c> contracts</c><00:03:18.360><c> so</c><00:03:18.900><c> this</c><00:03:19.140><c> is</c><00:03:19.319><c> a</c>

00:03:19.550 --> 00:03:19.560 align:start position:0%
caused by smart contracts so this is a
 

00:03:19.560 --> 00:03:21.589 align:start position:0%
caused by smart contracts so this is a
website<00:03:20.040><c> access</c><00:03:20.280><c> protocol</c><00:03:20.760><c> which</c><00:03:21.180><c> is</c><00:03:21.300><c> defined</c>

00:03:21.589 --> 00:03:21.599 align:start position:0%
website access protocol which is defined
 

00:03:21.599 --> 00:03:25.550 align:start position:0%
website access protocol which is defined
by<00:03:22.099><c> erc4804</c><00:03:23.099><c> which</c><00:03:24.000><c> is</c><00:03:24.180><c> a</c><00:03:24.480><c> way</c><00:03:25.140><c> to</c><00:03:25.319><c> render</c>

00:03:25.550 --> 00:03:25.560 align:start position:0%
by erc4804 which is a way to render
 

00:03:25.560 --> 00:03:28.309 align:start position:0%
by erc4804 which is a way to render
rapid<00:03:25.860><c> objects</c><00:03:26.340><c> hosted</c><00:03:26.700><c> by</c><00:03:26.819><c> smart</c><00:03:27.000><c> contra</c><00:03:27.840><c> is</c>

00:03:28.309 --> 00:03:28.319 align:start position:0%
rapid objects hosted by smart contra is
 

00:03:28.319 --> 00:03:30.470 align:start position:0%
rapid objects hosted by smart contra is
very<00:03:28.560><c> similar</c><00:03:28.980><c> to</c><00:03:29.099><c> http</c><00:03:29.640><c> so</c><00:03:30.000><c> that</c><00:03:30.180><c> it</c><00:03:30.300><c> can</c>

00:03:30.470 --> 00:03:30.480 align:start position:0%
very similar to http so that it can
 

00:03:30.480 --> 00:03:33.530 align:start position:0%
very similar to http so that it can
inherit<00:03:30.959><c> all</c><00:03:31.200><c> the</c><00:03:31.379><c> good</c><00:03:31.800><c> benefits</c><00:03:32.280><c> of</c><00:03:32.700><c> HTTP</c>

00:03:33.530 --> 00:03:33.540 align:start position:0%
inherit all the good benefits of HTTP
 

00:03:33.540 --> 00:03:36.949 align:start position:0%
inherit all the good benefits of HTTP
while<00:03:34.440><c> we</c><00:03:34.680><c> are</c><00:03:34.800><c> able</c><00:03:34.980><c> to</c><00:03:35.180><c> identify</c><00:03:36.180><c> a</c><00:03:36.540><c> resource</c>

00:03:36.949 --> 00:03:36.959 align:start position:0%
while we are able to identify a resource
 

00:03:36.959 --> 00:03:38.869 align:start position:0%
while we are able to identify a resource
that<00:03:37.140><c> hosts</c><00:03:37.500><c> by</c><00:03:37.620><c> smart</c><00:03:37.800><c> culture</c><00:03:38.280><c> and</c><00:03:38.519><c> further</c>

00:03:38.869 --> 00:03:38.879 align:start position:0%
that hosts by smart culture and further
 

00:03:38.879 --> 00:03:41.690 align:start position:0%
that hosts by smart culture and further
access<00:03:39.840><c> the</c><00:03:40.200><c> underlying</c><00:03:40.799><c> storage</c><00:03:41.040><c> layer</c><00:03:41.519><c> that</c>

00:03:41.690 --> 00:03:41.700 align:start position:0%
access the underlying storage layer that
 

00:03:41.700 --> 00:03:43.190 align:start position:0%
access the underlying storage layer that
we<00:03:41.879><c> built</c>

00:03:43.190 --> 00:03:43.200 align:start position:0%
we built
 

00:03:43.200 --> 00:03:45.649 align:start position:0%
we built
and<00:03:43.920><c> the</c><00:03:44.099><c> user</c><00:03:44.459><c> storage</c><00:03:44.640><c> is</c><00:03:45.120><c> a</c><00:03:45.239><c> layer</c><00:03:45.540><c> 2</c>

00:03:45.649 --> 00:03:45.659 align:start position:0%
and the user storage is a layer 2
 

00:03:45.659 --> 00:03:48.649 align:start position:0%
and the user storage is a layer 2
solutions<00:03:46.140><c> that</c><00:03:46.980><c> aims</c><00:03:47.340><c> to</c><00:03:47.459><c> scale</c><00:03:47.760><c> ethereum</c>

00:03:48.649 --> 00:03:48.659 align:start position:0%
solutions that aims to scale ethereum
 

00:03:48.659 --> 00:03:50.990 align:start position:0%
solutions that aims to scale ethereum
storage<00:03:48.840><c> rather</c><00:03:49.440><c> than</c><00:03:49.620><c> computation</c><00:03:50.159><c> and</c><00:03:50.879><c> so</c>

00:03:50.990 --> 00:03:51.000 align:start position:0%
storage rather than computation and so
 

00:03:51.000 --> 00:03:53.330 align:start position:0%
storage rather than computation and so
here<00:03:51.180><c> is</c><00:03:51.360><c> a</c><00:03:51.599><c> quick</c><00:03:51.720><c> comparison</c><00:03:52.260><c> of</c><00:03:52.799><c> what</c><00:03:53.099><c> is</c>

00:03:53.330 --> 00:03:53.340 align:start position:0%
here is a quick comparison of what is
 

00:03:53.340 --> 00:03:56.869 align:start position:0%
here is a quick comparison of what is
storage<00:03:53.580><c> can</c><00:03:54.239><c> do</c><00:03:54.480><c> versus</c><00:03:55.080><c> biocoin</c><00:03:55.860><c> orig</c><00:03:56.040><c> and</c>

00:03:56.869 --> 00:03:56.879 align:start position:0%
storage can do versus biocoin orig and
 

00:03:56.879 --> 00:03:58.729 align:start position:0%
storage can do versus biocoin orig and
the<00:03:57.060><c> default</c><00:03:57.360><c> storage</c><00:03:57.599><c> solutions</c><00:03:58.200><c> of</c>

00:03:58.729 --> 00:03:58.739 align:start position:0%
the default storage solutions of
 

00:03:58.739 --> 00:04:02.149 align:start position:0%
the default storage solutions of
ethereum<00:03:59.700><c> and</c><00:04:00.299><c> with</c><00:04:00.599><c> this</c><00:04:00.959><c> infrastructure</c><00:04:01.860><c> we</c>

00:04:02.149 --> 00:04:02.159 align:start position:0%
ethereum and with this infrastructure we
 

00:04:02.159 --> 00:04:04.250 align:start position:0%
ethereum and with this infrastructure we
believe<00:04:02.340><c> that</c><00:04:02.640><c> we</c><00:04:02.879><c> are</c><00:04:03.000><c> able</c><00:04:03.180><c> to</c><00:04:03.239><c> enable</c><00:04:03.780><c> a</c><00:04:04.140><c> lot</c>

00:04:04.250 --> 00:04:04.260 align:start position:0%
believe that we are able to enable a lot
 

00:04:04.260 --> 00:04:06.949 align:start position:0%
believe that we are able to enable a lot
of<00:04:04.379><c> new</c><00:04:04.620><c> applications</c><00:04:05.220><c> for</c><00:04:06.000><c> example</c><00:04:06.299><c> just</c><00:04:06.659><c> the</c>

00:04:06.949 --> 00:04:06.959 align:start position:0%
of new applications for example just the
 

00:04:06.959 --> 00:04:09.530 align:start position:0%
of new applications for example just the
website<00:04:07.200><c> hosting</c><00:04:07.560><c> like</c><00:04:07.739><c> unit</c><00:04:07.980><c> swap</c><00:04:08.459><c> curve</c><00:04:08.819><c> or</c>

00:04:09.530 --> 00:04:09.540 align:start position:0%
website hosting like unit swap curve or
 

00:04:09.540 --> 00:04:12.789 align:start position:0%
website hosting like unit swap curve or
dynamic<00:04:10.200><c> nft</c><00:04:10.560><c> which</c><00:04:11.040><c> we</c><00:04:11.220><c> are</c><00:04:11.459><c> able</c><00:04:11.760><c> to</c><00:04:12.360><c> change</c>

00:04:12.789 --> 00:04:12.799 align:start position:0%
dynamic nft which we are able to change
 

00:04:12.799 --> 00:04:15.770 align:start position:0%
dynamic nft which we are able to change
the<00:04:13.799><c> presentation</c><00:04:14.459><c> of</c><00:04:14.700><c> image</c><00:04:15.060><c> dynamically</c>

00:04:15.770 --> 00:04:15.780 align:start position:0%
the presentation of image dynamically
 

00:04:15.780 --> 00:04:17.990 align:start position:0%
the presentation of image dynamically
and<00:04:16.560><c> we</c><00:04:16.739><c> also</c><00:04:17.040><c> be</c><00:04:17.220><c> able</c><00:04:17.400><c> to</c><00:04:17.459><c> build</c>

00:04:17.990 --> 00:04:18.000 align:start position:0%
and we also be able to build
 

00:04:18.000 --> 00:04:19.909 align:start position:0%
and we also be able to build
decentralized<00:04:18.720><c> social</c><00:04:18.959><c> networks</c><00:04:19.440><c> such</c><00:04:19.739><c> as</c>

00:04:19.909 --> 00:04:19.919 align:start position:0%
decentralized social networks such as
 

00:04:19.919 --> 00:04:22.610 align:start position:0%
decentralized social networks such as
essential<00:04:20.400><c> Twitter</c><00:04:20.720><c> Media</c><00:04:21.720><c> or</c><00:04:22.440><c> even</c>

00:04:22.610 --> 00:04:22.620 align:start position:0%
essential Twitter Media or even
 

00:04:22.620 --> 00:04:25.310 align:start position:0%
essential Twitter Media or even
decentralized<00:04:23.160><c> Dropbox</c>

00:04:25.310 --> 00:04:25.320 align:start position:0%
decentralized Dropbox
 

00:04:25.320 --> 00:04:27.950 align:start position:0%
decentralized Dropbox
so<00:04:25.919><c> here</c><00:04:26.100><c> I</c><00:04:26.280><c> will</c><00:04:26.400><c> give</c><00:04:26.520><c> a</c><00:04:26.759><c> demo</c>

00:04:27.950 --> 00:04:27.960 align:start position:0%
so here I will give a demo
 

00:04:27.960 --> 00:04:29.749 align:start position:0%
so here I will give a demo
um<00:04:28.080><c> let</c><00:04:28.320><c> me</c><00:04:28.500><c> see</c><00:04:28.620><c> okay</c>

00:04:29.749 --> 00:04:29.759 align:start position:0%
um let me see okay
 

00:04:29.759 --> 00:04:32.270 align:start position:0%
um let me see okay
this<00:04:30.120><c> is</c><00:04:30.240><c> my</c><00:04:30.479><c> Firefox</c><00:04:31.080><c> browser</c><00:04:31.560><c> that</c><00:04:31.860><c> supports</c>

00:04:32.270 --> 00:04:32.280 align:start position:0%
this is my Firefox browser that supports
 

00:04:32.280 --> 00:04:35.710 align:start position:0%
this is my Firefox browser that supports
the<00:04:32.400><c> 3vml</c><00:04:33.060><c> so</c><00:04:33.360><c> now</c><00:04:33.540><c> it's</c><00:04:33.720><c> time</c><00:04:33.780><c> to</c><00:04:33.960><c> go</c><00:04:34.080><c> to</c><00:04:34.259><c> URL</c>

00:04:35.710 --> 00:04:35.720 align:start position:0%
the 3vml so now it's time to go to URL
 

00:04:35.720 --> 00:04:39.530 align:start position:0%
the 3vml so now it's time to go to URL
uh<00:04:36.720><c> that</c><00:04:37.440><c> may</c><00:04:37.680><c> register</c><00:04:38.040><c> a</c><00:04:38.340><c> UNS</c><00:04:38.759><c> standpoints</c>

00:04:39.530 --> 00:04:39.540 align:start position:0%
uh that may register a UNS standpoints
 

00:04:39.540 --> 00:04:41.930 align:start position:0%
uh that may register a UNS standpoints
channel<00:04:39.780><c> uh</c><00:04:40.680><c> the</c><00:04:40.800><c> smart</c><00:04:40.979><c> contract</c><00:04:41.460><c> that</c><00:04:41.580><c> holds</c>

00:04:41.930 --> 00:04:41.940 align:start position:0%
channel uh the smart contract that holds
 

00:04:41.940 --> 00:04:45.969 align:start position:0%
channel uh the smart contract that holds
our<00:04:42.180><c> performance</c><00:04:43.080><c> so</c><00:04:43.620><c> all</c><00:04:43.860><c> the</c><00:04:44.100><c> images</c><00:04:44.660><c> HTML</c>

00:04:45.969 --> 00:04:45.979 align:start position:0%
our performance so all the images HTML
 

00:04:45.979 --> 00:04:49.430 align:start position:0%
our performance so all the images HTML
CSS<00:04:46.979><c> JavaScript</c><00:04:47.520><c> now</c><00:04:48.060><c> uh</c><00:04:48.780><c> hosting</c><00:04:49.139><c> by</c><00:04:49.320><c> the</c>

00:04:49.430 --> 00:04:49.440 align:start position:0%
CSS JavaScript now uh hosting by the
 

00:04:49.440 --> 00:04:51.050 align:start position:0%
CSS JavaScript now uh hosting by the
smart<00:04:49.620><c> contract</c><00:04:49.979><c> are</c><00:04:50.220><c> returned</c><00:04:50.520><c> by</c><00:04:50.759><c> this</c>

00:04:51.050 --> 00:04:51.060 align:start position:0%
smart contract are returned by this
 

00:04:51.060 --> 00:04:53.689 align:start position:0%
smart contract are returned by this
website<00:04:51.960><c> access</c><00:04:52.080><c> support</c><00:04:52.380><c> code</c><00:04:52.740><c> so</c><00:04:53.400><c> there</c><00:04:53.580><c> are</c>

00:04:53.689 --> 00:04:53.699 align:start position:0%
website access support code so there are
 

00:04:53.699 --> 00:04:55.850 align:start position:0%
website access support code so there are
also<00:04:53.940><c> a</c><00:04:54.060><c> couple</c><00:04:54.120><c> of</c><00:04:54.300><c> uh</c><00:04:54.720><c> interesting</c><00:04:55.320><c> examples</c>

00:04:55.850 --> 00:04:55.860 align:start position:0%
also a couple of uh interesting examples
 

00:04:55.860 --> 00:04:58.310 align:start position:0%
also a couple of uh interesting examples
for<00:04:56.100><c> example</c><00:04:56.400><c> design</c><00:04:56.699><c> trans</c><00:04:57.060><c> Dropbox</c>

00:04:58.310 --> 00:04:58.320 align:start position:0%
for example design trans Dropbox
 

00:04:58.320 --> 00:05:00.290 align:start position:0%
for example design trans Dropbox
so<00:04:58.800><c> this</c><00:04:59.040><c> is</c><00:04:59.220><c> also</c><00:04:59.520><c> a</c><00:04:59.580><c> whole</c><00:04:59.699><c> digital</c><00:05:00.060><c> return</c>

00:05:00.290 --> 00:05:00.300 align:start position:0%
so this is also a whole digital return
 

00:05:00.300 --> 00:05:02.350 align:start position:0%
so this is also a whole digital return
on<00:05:00.600><c> Smart</c><00:05:00.840><c> contract</c><00:05:01.320><c> another</c><00:05:01.620><c> small</c><00:05:01.919><c> culture</c>

00:05:02.350 --> 00:05:02.360 align:start position:0%
on Smart contract another small culture
 

00:05:02.360 --> 00:05:05.510 align:start position:0%
on Smart contract another small culture
and<00:05:03.360><c> we</c><00:05:03.720><c> can</c><00:05:04.020><c> see</c><00:05:04.320><c> I</c><00:05:04.620><c> can</c><00:05:04.800><c> see</c><00:05:04.919><c> them</c><00:05:05.100><c> all</c><00:05:05.280><c> the</c>

00:05:05.510 --> 00:05:05.520 align:start position:0%
and we can see I can see them all the
 

00:05:05.520 --> 00:05:07.670 align:start position:0%
and we can see I can see them all the
list<00:05:05.820><c> like</c><00:05:06.360><c> all</c><00:05:06.600><c> the</c><00:05:06.660><c> print</c><00:05:06.780><c> files</c><00:05:07.259><c> have</c><00:05:07.440><c> been</c>

00:05:07.670 --> 00:05:07.680 align:start position:0%
list like all the print files have been
 

00:05:07.680 --> 00:05:10.550 align:start position:0%
list like all the print files have been
uploaded<00:05:08.340><c> before</c><00:05:08.460><c> and</c><00:05:09.419><c> in</c><00:05:09.720><c> order</c><00:05:09.840><c> to</c><00:05:10.080><c> upload</c><00:05:10.440><c> a</c>

00:05:10.550 --> 00:05:10.560 align:start position:0%
uploaded before and in order to upload a
 

00:05:10.560 --> 00:05:13.730 align:start position:0%
uploaded before and in order to upload a
new<00:05:10.680><c> file</c><00:05:10.979><c> what</c><00:05:11.820><c> I</c><00:05:12.120><c> should</c><00:05:12.419><c> do</c><00:05:12.720><c> is</c><00:05:13.259><c> just</c><00:05:13.500><c> check</c>

00:05:13.730 --> 00:05:13.740 align:start position:0%
new file what I should do is just check
 

00:05:13.740 --> 00:05:14.870 align:start position:0%
new file what I should do is just check
the<00:05:13.979><c> file</c>

00:05:14.870 --> 00:05:14.880 align:start position:0%
the file
 

00:05:14.880 --> 00:05:17.990 align:start position:0%
the file
and<00:05:15.600><c> then</c><00:05:15.840><c> it</c><00:05:16.080><c> will</c><00:05:16.259><c> ask</c><00:05:16.560><c> me</c><00:05:17.160><c> to</c><00:05:17.460><c> sign</c><00:05:17.759><c> a</c>

00:05:17.990 --> 00:05:18.000 align:start position:0%
and then it will ask me to sign a
 

00:05:18.000 --> 00:05:20.450 align:start position:0%
and then it will ask me to sign a
transaction<00:05:18.479><c> via</c><00:05:19.380><c> mask</c>

00:05:20.450 --> 00:05:20.460 align:start position:0%
transaction via mask
 

00:05:20.460 --> 00:05:22.790 align:start position:0%
transaction via mask
so<00:05:20.880><c> during</c><00:05:21.120><c> the</c><00:05:21.300><c> whole</c><00:05:21.479><c> procedure</c>

00:05:22.790 --> 00:05:22.800 align:start position:0%
so during the whole procedure
 

00:05:22.800 --> 00:05:24.650 align:start position:0%
so during the whole procedure
you<00:05:23.220><c> do</c><00:05:23.400><c> not</c><00:05:23.580><c> need</c><00:05:23.759><c> to</c><00:05:23.820><c> require</c><00:05:24.180><c> any</c>

00:05:24.650 --> 00:05:24.660 align:start position:0%
you do not need to require any
 

00:05:24.660 --> 00:05:29.930 align:start position:0%
you do not need to require any
additional<00:05:25.460><c> uh</c><00:05:26.460><c> two</c><00:05:27.000><c> such</c><00:05:27.419><c> as</c><00:05:27.600><c> Cellar</c><00:05:28.199><c> CLI</c>

00:05:29.930 --> 00:05:29.940 align:start position:0%
additional uh two such as Cellar CLI
 

00:05:29.940 --> 00:05:33.529 align:start position:0%
additional uh two such as Cellar CLI
and<00:05:30.780><c> once</c><00:05:31.139><c> the</c><00:05:31.320><c> transaction</c><00:05:31.800><c> is</c><00:05:32.699><c> confirmed</c><00:05:33.240><c> a</c>

00:05:33.529 --> 00:05:33.539 align:start position:0%
and once the transaction is confirmed a
 

00:05:33.539 --> 00:05:37.430 align:start position:0%
and once the transaction is confirmed a
network<00:05:33.800><c> I</c><00:05:34.800><c> can</c><00:05:35.039><c> access</c><00:05:35.280><c> the</c><00:05:35.820><c> file</c><00:05:36.080><c> also</c><00:05:37.080><c> via</c>

00:05:37.430 --> 00:05:37.440 align:start position:0%
network I can access the file also via
 

00:05:37.440 --> 00:05:40.430 align:start position:0%
network I can access the file also via
web3<00:05:38.039><c> access</c><00:05:38.280><c> protocol</c>

00:05:40.430 --> 00:05:40.440 align:start position:0%
web3 access protocol
 

00:05:40.440 --> 00:05:43.010 align:start position:0%
web3 access protocol
um<00:05:40.560><c> so</c><00:05:40.800><c> has</c><00:05:41.580><c> been</c><00:05:41.759><c> uploaded</c><00:05:42.240><c> so</c><00:05:42.539><c> we</c><00:05:42.720><c> are</c><00:05:42.840><c> able</c>

00:05:43.010 --> 00:05:43.020 align:start position:0%
um so has been uploaded so we are able
 

00:05:43.020 --> 00:05:45.290 align:start position:0%
um so has been uploaded so we are able
to<00:05:43.139><c> access</c><00:05:43.380><c> so</c><00:05:43.740><c> it's</c><00:05:43.979><c> still</c><00:05:44.280><c> giving</c><00:05:44.580><c> but</c><00:05:45.000><c> we</c>

00:05:45.290 --> 00:05:45.300 align:start position:0%
to access so it's still giving but we
 

00:05:45.300 --> 00:05:47.650 align:start position:0%
to access so it's still giving but we
can<00:05:45.660><c> still</c><00:05:45.780><c> using</c><00:05:46.139><c> website</c><00:05:46.560><c> access</c><00:05:46.979><c> protocol</c>

00:05:47.650 --> 00:05:47.660 align:start position:0%
can still using website access protocol
 

00:05:47.660 --> 00:05:51.409 align:start position:0%
can still using website access protocol
and<00:05:48.660><c> the</c><00:05:48.900><c> corresponding</c><00:05:49.940><c> violence</c><00:05:50.940><c> is</c><00:05:51.180><c> also</c>

00:05:51.409 --> 00:05:51.419 align:start position:0%
and the corresponding violence is also
 

00:05:51.419 --> 00:05:53.749 align:start position:0%
and the corresponding violence is also
updated<00:05:51.840><c> according</c><00:05:52.500><c> to</c><00:05:52.800><c> it</c><00:05:52.979><c> thanks</c><00:05:53.160><c> to</c><00:05:53.400><c> Smart</c>

00:05:53.749 --> 00:05:53.759 align:start position:0%
updated according to it thanks to Smart
 

00:05:53.759 --> 00:05:54.830 align:start position:0%
updated according to it thanks to Smart
contract

00:05:54.830 --> 00:05:54.840 align:start position:0%
contract
 

00:05:54.840 --> 00:05:56.810 align:start position:0%
contract
so<00:05:55.620><c> this</c><00:05:55.800><c> is</c><00:05:55.979><c> an</c><00:05:56.160><c> example</c><00:05:56.340><c> for</c><00:05:56.699><c> this</c>

00:05:56.810 --> 00:05:56.820 align:start position:0%
so this is an example for this
 

00:05:56.820 --> 00:05:58.070 align:start position:0%
so this is an example for this
centralized

00:05:58.070 --> 00:05:58.080 align:start position:0%
centralized
 

00:05:58.080 --> 00:06:00.050 align:start position:0%
centralized
Dropbox<00:05:58.620><c> there</c><00:05:58.919><c> are</c><00:05:59.039><c> also</c><00:05:59.160><c> a</c><00:05:59.280><c> couple</c><00:05:59.400><c> of</c><00:05:59.580><c> other</c>

00:06:00.050 --> 00:06:00.060 align:start position:0%
Dropbox there are also a couple of other
 

00:06:00.060 --> 00:06:02.390 align:start position:0%
Dropbox there are also a couple of other
examples<00:06:00.780><c> like</c><00:06:01.080><c> web</c><00:06:01.380><c> streaming</c><00:06:01.860><c> deception</c>

00:06:02.390 --> 00:06:02.400 align:start position:0%
examples like web streaming deception
 

00:06:02.400 --> 00:06:05.810 align:start position:0%
examples like web streaming deception
report<00:06:02.960><c> Dynamic</c><00:06:03.960><c> guarantee</c><00:06:05.100><c> Etc</c><00:06:05.220><c> so</c><00:06:05.639><c> welcome</c>

00:06:05.810 --> 00:06:05.820 align:start position:0%
report Dynamic guarantee Etc so welcome
 

00:06:05.820 --> 00:06:09.170 align:start position:0%
report Dynamic guarantee Etc so welcome
to<00:06:06.120><c> play</c><00:06:06.539><c> to</c><00:06:07.080><c> yeah</c><00:06:07.560><c> yeah</c><00:06:08.460><c> um</c><00:06:08.520><c> so</c><00:06:08.759><c> there</c><00:06:08.940><c> are</c><00:06:09.120><c> a</c>

00:06:09.170 --> 00:06:09.180 align:start position:0%
to play to yeah yeah um so there are a
 

00:06:09.180 --> 00:06:11.629 align:start position:0%
to play to yeah yeah um so there are a
lot<00:06:09.300><c> of</c><00:06:09.360><c> more</c><00:06:09.600><c> details</c><00:06:10.020><c> of</c><00:06:10.259><c> our</c><00:06:10.639><c> technology</c>

00:06:11.629 --> 00:06:11.639 align:start position:0%
lot of more details of our technology
 

00:06:11.639 --> 00:06:14.450 align:start position:0%
lot of more details of our technology
that<00:06:11.940><c> are</c><00:06:12.120><c> built</c><00:06:12.479><c> so</c><00:06:13.020><c> we</c><00:06:13.199><c> have</c><00:06:13.380><c> after</c><00:06:13.740><c> party</c><00:06:14.100><c> in</c>

00:06:14.450 --> 00:06:14.460 align:start position:0%
that are built so we have after party in
 

00:06:14.460 --> 00:06:17.150 align:start position:0%
that are built so we have after party in
this<00:06:14.699><c> afternoon</c><00:06:15.060><c> and</c><00:06:15.720><c> in</c><00:06:16.080><c> the</c><00:06:16.259><c> nearby</c><00:06:16.560><c> Hilton</c>

00:06:17.150 --> 00:06:17.160 align:start position:0%
this afternoon and in the nearby Hilton
 

00:06:17.160 --> 00:06:20.210 align:start position:0%
this afternoon and in the nearby Hilton
Hotel<00:06:17.400><c> and</c><00:06:18.060><c> 550</c><00:06:18.539><c> Camp</c><00:06:18.780><c> I'm</c><00:06:19.680><c> happy</c><00:06:19.860><c> to</c><00:06:20.039><c> answer</c>

00:06:20.210 --> 00:06:20.220 align:start position:0%
Hotel and 550 Camp I'm happy to answer
 

00:06:20.220 --> 00:06:23.150 align:start position:0%
Hotel and 550 Camp I'm happy to answer
any<00:06:20.460><c> questions</c><00:06:20.759><c> yes</c><00:06:21.479><c> you</c><00:06:21.900><c> you</c><00:06:22.319><c> listed</c><00:06:22.740><c> four</c>

00:06:23.150 --> 00:06:23.160 align:start position:0%
any questions yes you you listed four
 

00:06:23.160 --> 00:06:26.270 align:start position:0%
any questions yes you you listed four
you've<00:06:23.880><c> made</c><00:06:24.000><c> comparison</c><00:06:24.660><c> with</c><00:06:25.139><c> four</c><00:06:25.860><c> systems</c>

00:06:26.270 --> 00:06:26.280 align:start position:0%
you've made comparison with four systems
 

00:06:26.280 --> 00:06:28.730 align:start position:0%
you've made comparison with four systems
but<00:06:26.520><c> you</c><00:06:26.699><c> forgot</c><00:06:27.060><c> to</c><00:06:27.300><c> mention</c><00:06:27.479><c> swarm</c><00:06:28.259><c> yeah</c>

00:06:28.730 --> 00:06:28.740 align:start position:0%
but you forgot to mention swarm yeah
 

00:06:28.740 --> 00:06:31.010 align:start position:0%
but you forgot to mention swarm yeah
actually<00:06:29.340><c> I</c><00:06:29.580><c> talked</c><00:06:29.940><c> to</c><00:06:30.000><c> Swan</c><00:06:30.300><c> people</c><00:06:30.479><c> a</c><00:06:30.900><c> few</c>

00:06:31.010 --> 00:06:31.020 align:start position:0%
actually I talked to Swan people a few
 

00:06:31.020 --> 00:06:33.650 align:start position:0%
actually I talked to Swan people a few
days<00:06:31.199><c> ago</c><00:06:31.500><c> so</c><00:06:32.280><c> Swan</c><00:06:32.699><c> actually</c><00:06:32.940><c> has</c><00:06:33.240><c> a</c><00:06:33.419><c> similar</c>

00:06:33.650 --> 00:06:33.660 align:start position:0%
days ago so Swan actually has a similar
 

00:06:33.660 --> 00:06:36.409 align:start position:0%
days ago so Swan actually has a similar
architecture<00:06:34.199><c> as</c><00:06:34.380><c> ffs</c><00:06:34.979><c> which</c><00:06:35.639><c> is</c><00:06:35.759><c> using</c><00:06:36.240><c> a</c>

00:06:36.409 --> 00:06:36.419 align:start position:0%
architecture as ffs which is using a
 

00:06:36.419 --> 00:06:39.050 align:start position:0%
architecture as ffs which is using a
Content<00:06:36.780><c> addressing</c><00:06:37.259><c> to</c><00:06:37.620><c> basically</c><00:06:38.580><c> a</c>

00:06:39.050 --> 00:06:39.060 align:start position:0%
Content addressing to basically a
 

00:06:39.060 --> 00:06:41.629 align:start position:0%
Content addressing to basically a
locating<00:06:39.479><c> a</c><00:06:39.660><c> file</c><00:06:39.840><c> and</c><00:06:40.319><c> also</c><00:06:40.560><c> it</c><00:06:40.740><c> has</c><00:06:40.979><c> a</c><00:06:41.280><c> way</c><00:06:41.400><c> to</c>

00:06:41.629 --> 00:06:41.639 align:start position:0%
locating a file and also it has a way to
 

00:06:41.639 --> 00:06:43.550 align:start position:0%
locating a file and also it has a way to
basically<00:06:42.000><c> call</c><00:06:42.240><c> Dynamic</c><00:06:42.660><c> hash</c><00:06:42.900><c> to</c><00:06:43.139><c> able</c><00:06:43.440><c> to</c>

00:06:43.550 --> 00:06:43.560 align:start position:0%
basically call Dynamic hash to able to
 

00:06:43.560 --> 00:06:46.010 align:start position:0%
basically call Dynamic hash to able to
locate<00:06:44.100><c> the</c><00:06:44.220><c> latest</c><00:06:44.460><c> version</c><00:06:44.819><c> of</c><00:06:45.000><c> file</c><00:06:45.300><c> but</c><00:06:45.840><c> at</c>

00:06:46.010 --> 00:06:46.020 align:start position:0%
locate the latest version of file but at
 

00:06:46.020 --> 00:06:47.570 align:start position:0%
locate the latest version of file but at
the<00:06:46.139><c> same</c><00:06:46.259><c> time</c><00:06:46.380><c> right</c><00:06:46.680><c> now</c><00:06:46.800><c> I</c><00:06:47.160><c> don't</c><00:06:47.220><c> think</c><00:06:47.400><c> it</c>

00:06:47.570 --> 00:06:47.580 align:start position:0%
the same time right now I don't think it
 

00:06:47.580 --> 00:06:49.309 align:start position:0%
the same time right now I don't think it
has<00:06:47.759><c> the</c><00:06:47.880><c> programmability</c><00:06:48.419><c> with</c><00:06:48.900><c> the</c><00:06:49.139><c> Smart</c>

00:06:49.309 --> 00:06:49.319 align:start position:0%
has the programmability with the Smart
 

00:06:49.319 --> 00:06:51.890 align:start position:0%
has the programmability with the Smart
Launcher<00:06:49.800><c> which</c><00:06:50.280><c> is</c><00:06:50.520><c> able</c><00:06:51.000><c> to</c><00:06:51.120><c> modify</c><00:06:51.660><c> and</c>

00:06:51.890 --> 00:06:51.900 align:start position:0%
Launcher which is able to modify and
 

00:06:51.900 --> 00:06:54.290 align:start position:0%
Launcher which is able to modify and
able<00:06:52.199><c> to</c><00:06:52.319><c> compose</c><00:06:52.680><c> all</c><00:06:52.860><c> the</c><00:06:53.039><c> data</c><00:06:53.280><c> purely</c><00:06:54.060><c> on</c>

00:06:54.290 --> 00:06:54.300 align:start position:0%
able to compose all the data purely on
 

00:06:54.300 --> 00:06:55.909 align:start position:0%
able to compose all the data purely on
chain<00:06:54.479><c> and</c><00:06:55.139><c> there's</c><00:06:55.319><c> something</c><00:06:55.560><c> we</c><00:06:55.740><c> really</c>

00:06:55.909 --> 00:06:55.919 align:start position:0%
chain and there's something we really
 

00:06:55.919 --> 00:06:58.010 align:start position:0%
chain and there's something we really
want<00:06:56.100><c> to</c><00:06:56.220><c> enable</c><00:06:56.580><c> and</c><00:06:56.940><c> second</c><00:06:57.120><c> is</c><00:06:57.360><c> that</c><00:06:57.539><c> or</c><00:06:57.780><c> who</c>

00:06:58.010 --> 00:06:58.020 align:start position:0%
want to enable and second is that or who
 

00:06:58.020 --> 00:07:00.230 align:start position:0%
want to enable and second is that or who
the<00:06:58.259><c> design</c><00:06:58.560><c> is</c><00:06:58.860><c> using</c><00:06:59.220><c> easier</c><00:06:59.580><c> so</c><00:06:59.940><c> basically</c>

00:07:00.230 --> 00:07:00.240 align:start position:0%
the design is using easier so basically
 

00:07:00.240 --> 00:07:02.629 align:start position:0%
the design is using easier so basically
the<00:07:00.539><c> data</c><00:07:00.780><c> providers</c><00:07:01.199><c> will</c><00:07:01.500><c> be</c><00:07:01.680><c> paid</c><00:07:02.160><c> by</c><00:07:02.400><c> the</c>

00:07:02.629 --> 00:07:02.639 align:start position:0%
the data providers will be paid by the
 

00:07:02.639 --> 00:07:04.909 align:start position:0%
the data providers will be paid by the
user<00:07:03.180><c> and</c><00:07:03.600><c> also</c><00:07:03.840><c> the</c><00:07:04.020><c> users</c><00:07:04.380><c> will</c><00:07:04.560><c> pay</c><00:07:04.740><c> the</c>

00:07:04.909 --> 00:07:04.919 align:start position:0%
user and also the users will pay the
 

00:07:04.919 --> 00:07:07.550 align:start position:0%
user and also the users will pay the
user<00:07:05.220><c> to</c><00:07:05.340><c> storage</c><00:07:05.580><c> those</c><00:07:06.000><c> content</c><00:07:06.660><c> so</c><00:07:07.139><c> it's</c><00:07:07.319><c> a</c>

00:07:07.550 --> 00:07:07.560 align:start position:0%
user to storage those content so it's a
 

00:07:07.560 --> 00:07:09.290 align:start position:0%
user to storage those content so it's a
highly<00:07:07.860><c> coupled</c><00:07:08.160><c> with</c><00:07:08.280><c> the</c><00:07:08.400><c> ethereum</c><00:07:08.759><c> with</c>

00:07:09.290 --> 00:07:09.300 align:start position:0%
highly coupled with the ethereum with
 

00:07:09.300 --> 00:07:13.460 align:start position:0%
highly coupled with the ethereum with
the<00:07:09.539><c> basically</c><00:07:10.319><c> native</c><00:07:11.160><c> support</c>