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:13.629 align:start position:0%
 
[Music]

00:00:13.629 --> 00:00:13.639 align:start position:0%
 
 

00:00:13.639 --> 00:00:16.310 align:start position:0%
 
and<00:00:14.639><c> during</c><00:00:14.880><c> the</c><00:00:15.179><c> last</c><00:00:15.299><c> two</c><00:00:15.540><c> years</c><00:00:15.719><c> I've</c><00:00:16.139><c> been</c>

00:00:16.310 --> 00:00:16.320 align:start position:0%
and during the last two years I've been
 

00:00:16.320 --> 00:00:18.109 align:start position:0%
and during the last two years I've been
contributing<00:00:16.859><c> to</c><00:00:17.039><c> the</c><00:00:17.220><c> Sunderland</c><00:00:17.580><c> and</c><00:00:17.940><c> today</c>

00:00:18.109 --> 00:00:18.119 align:start position:0%
contributing to the Sunderland and today
 

00:00:18.119 --> 00:00:20.150 align:start position:0%
contributing to the Sunderland and today
I'm<00:00:18.240><c> going</c><00:00:18.420><c> to</c><00:00:18.539><c> talk</c><00:00:18.720><c> about</c><00:00:18.840><c> using</c><00:00:19.380><c> ibps</c><00:00:19.859><c> to</c>

00:00:20.150 --> 00:00:20.160 align:start position:0%
I'm going to talk about using ibps to
 

00:00:20.160 --> 00:00:22.490 align:start position:0%
I'm going to talk about using ibps to
create<00:00:20.279><c> the</c><00:00:20.520><c> metaverse</c><00:00:21.119><c> so</c><00:00:21.420><c> let's</c><00:00:21.779><c> first</c><00:00:22.260><c> talk</c>

00:00:22.490 --> 00:00:22.500 align:start position:0%
create the metaverse so let's first talk
 

00:00:22.500 --> 00:00:26.630 align:start position:0%
create the metaverse so let's first talk
about<00:00:22.760><c> what</c><00:00:23.760><c> the</c><00:00:23.939><c> meters</c><00:00:24.300><c> is</c><00:00:24.980><c> well</c><00:00:25.980><c> it's</c><00:00:26.400><c> a</c>

00:00:26.630 --> 00:00:26.640 align:start position:0%
about what the meters is well it's a
 

00:00:26.640 --> 00:00:28.370 align:start position:0%
about what the meters is well it's a
social<00:00:26.820><c> network</c><00:00:27.180><c> where</c><00:00:27.660><c> you</c><00:00:27.840><c> interact</c><00:00:28.140><c> with</c>

00:00:28.370 --> 00:00:28.380 align:start position:0%
social network where you interact with
 

00:00:28.380 --> 00:00:31.189 align:start position:0%
social network where you interact with
friends<00:00:29.039><c> people</c><00:00:29.519><c> that</c><00:00:29.820><c> you</c><00:00:29.939><c> meet</c><00:00:30.119><c> there</c><00:00:30.359><c> in</c><00:00:31.019><c> a</c>

00:00:31.189 --> 00:00:31.199 align:start position:0%
friends people that you meet there in a
 

00:00:31.199 --> 00:00:33.830 align:start position:0%
friends people that you meet there in a
three-dimensional<00:00:31.800><c> way</c><00:00:32.120><c> and</c><00:00:33.120><c> also</c><00:00:33.360><c> there</c><00:00:33.600><c> you</c>

00:00:33.830 --> 00:00:33.840 align:start position:0%
three-dimensional way and also there you
 

00:00:33.840 --> 00:00:35.590 align:start position:0%
three-dimensional way and also there you
have<00:00:34.020><c> a</c><00:00:34.200><c> digital</c><00:00:34.500><c> identity</c>

00:00:35.590 --> 00:00:35.600 align:start position:0%
have a digital identity
 

00:00:35.600 --> 00:00:39.830 align:start position:0%
have a digital identity
which<00:00:36.600><c> is</c><00:00:37.260><c> customized</c><00:00:37.980><c> custom</c><00:00:38.520><c> is</c><00:00:39.120><c> custom</c><00:00:39.420><c> for</c>

00:00:39.830 --> 00:00:39.840 align:start position:0%
which is customized custom is custom for
 

00:00:39.840 --> 00:00:42.290 align:start position:0%
which is customized custom is custom for
you<00:00:39.960><c> and</c><00:00:40.440><c> it's</c><00:00:41.040><c> your</c><00:00:41.460><c> the</c><00:00:41.760><c> way</c><00:00:41.940><c> that</c><00:00:42.180><c> people</c>

00:00:42.290 --> 00:00:42.300 align:start position:0%
you and it's your the way that people
 

00:00:42.300 --> 00:00:44.990 align:start position:0%
you and it's your the way that people
recognizes<00:00:43.079><c> you</c>

00:00:44.990 --> 00:00:45.000 align:start position:0%
recognizes you
 

00:00:45.000 --> 00:00:47.690 align:start position:0%
recognizes you
um<00:00:45.420><c> what</c><00:00:46.079><c> distinguished</c><00:00:46.739><c> the</c><00:00:46.860><c> central</c><00:00:47.100><c> from</c>

00:00:47.690 --> 00:00:47.700 align:start position:0%
um what distinguished the central from
 

00:00:47.700 --> 00:00:50.029 align:start position:0%
um what distinguished the central from
other<00:00:47.820><c> metaverses</c><00:00:48.539><c> is</c><00:00:48.840><c> that</c><00:00:49.200><c> the</c><00:00:49.500><c> users</c><00:00:49.860><c> are</c>

00:00:50.029 --> 00:00:50.039 align:start position:0%
other metaverses is that the users are
 

00:00:50.039 --> 00:00:53.750 align:start position:0%
other metaverses is that the users are
the<00:00:50.219><c> ones</c><00:00:50.399><c> who</c><00:00:50.700><c> owns</c><00:00:51.120><c> the</c><00:00:51.899><c> platform</c><00:00:52.440><c> right</c><00:00:52.800><c> so</c>

00:00:53.750 --> 00:00:53.760 align:start position:0%
the ones who owns the platform right so
 

00:00:53.760 --> 00:00:56.510 align:start position:0%
the ones who owns the platform right so
how<00:00:54.059><c> do</c><00:00:54.180><c> we</c><00:00:54.300><c> do</c><00:00:54.480><c> that</c><00:00:54.660><c> well</c><00:00:55.320><c> the</c><00:00:55.920><c> world</c><00:00:56.219><c> is</c>

00:00:56.510 --> 00:00:56.520 align:start position:0%
how do we do that well the world is
 

00:00:56.520 --> 00:00:59.029 align:start position:0%
how do we do that well the world is
divided<00:00:56.879><c> into</c><00:00:57.000><c> parcels</c><00:00:57.600><c> and</c><00:00:58.020><c> each</c><00:00:58.199><c> parcel</c><00:00:58.680><c> has</c>

00:00:59.029 --> 00:00:59.039 align:start position:0%
divided into parcels and each parcel has
 

00:00:59.039 --> 00:01:01.850 align:start position:0%
divided into parcels and each parcel has
an<00:00:59.460><c> owner</c><00:00:59.879><c> and</c><00:01:00.480><c> is</c><00:01:00.600><c> the</c><00:01:00.840><c> owner</c><00:01:01.079><c> who</c><00:01:01.260><c> decides</c>

00:01:01.850 --> 00:01:01.860 align:start position:0%
an owner and is the owner who decides
 

00:01:01.860 --> 00:01:04.789 align:start position:0%
an owner and is the owner who decides
what<00:01:02.340><c> to</c><00:01:02.520><c> show</c><00:01:02.760><c> on</c><00:01:03.120><c> the</c><00:01:03.239><c> on</c><00:01:03.480><c> the</c><00:01:03.660><c> world</c><00:01:03.799><c> they</c>

00:01:04.789 --> 00:01:04.799 align:start position:0%
what to show on the on the world they
 

00:01:04.799 --> 00:01:07.670 align:start position:0%
what to show on the on the world they
could<00:01:05.100><c> chose</c><00:01:05.519><c> to</c><00:01:06.000><c> set</c><00:01:06.720><c> up</c><00:01:06.900><c> an</c><00:01:07.080><c> essene</c><00:01:07.500><c> for</c>

00:01:07.670 --> 00:01:07.680 align:start position:0%
could chose to set up an essene for
 

00:01:07.680 --> 00:01:11.090 align:start position:0%
could chose to set up an essene for
example<00:01:07.920><c> for</c><00:01:08.280><c> a</c><00:01:08.400><c> casino</c><00:01:08.720><c> for</c><00:01:09.720><c> a</c><00:01:09.900><c> bar</c><00:01:10.140><c> or</c><00:01:10.560><c> even</c><00:01:10.740><c> a</c>

00:01:11.090 --> 00:01:11.100 align:start position:0%
example for a casino for a bar or even a
 

00:01:11.100 --> 00:01:12.230 align:start position:0%
example for a casino for a bar or even a
music<00:01:11.280><c> festival</c>

00:01:12.230 --> 00:01:12.240 align:start position:0%
music festival
 

00:01:12.240 --> 00:01:17.530 align:start position:0%
music festival
and<00:01:12.900><c> how</c><00:01:13.200><c> we</c><00:01:13.380><c> do</c><00:01:13.560><c> that</c><00:01:14.060><c> we</c><00:01:15.060><c> have</c><00:01:15.860><c> deployed</c>

00:01:17.530 --> 00:01:17.540 align:start position:0%
and how we do that we have deployed
 

00:01:17.540 --> 00:01:20.749 align:start position:0%
and how we do that we have deployed
contracts<00:01:18.540><c> in</c><00:01:18.659><c> ethereum</c><00:01:19.260><c> to</c><00:01:20.040><c> check</c><00:01:20.520><c> the</c>

00:01:20.749 --> 00:01:20.759 align:start position:0%
contracts in ethereum to check the
 

00:01:20.759 --> 00:01:23.109 align:start position:0%
contracts in ethereum to check the
ownership<00:01:21.060><c> of</c><00:01:21.540><c> those</c><00:01:21.720><c> lands</c><00:01:22.259><c> on</c><00:01:22.439><c> the</c><00:01:22.619><c> worlds</c>

00:01:23.109 --> 00:01:23.119 align:start position:0%
ownership of those lands on the worlds
 

00:01:23.119 --> 00:01:26.030 align:start position:0%
ownership of those lands on the worlds
and<00:01:24.119><c> to</c><00:01:24.720><c> check</c><00:01:25.020><c> the</c><00:01:25.200><c> ownership</c><00:01:25.439><c> we</c><00:01:25.740><c> use</c><00:01:25.920><c> the</c>

00:01:26.030 --> 00:01:26.040 align:start position:0%
and to check the ownership we use the
 

00:01:26.040 --> 00:01:29.090 align:start position:0%
and to check the ownership we use the
graph<00:01:26.280><c> in</c><00:01:26.640><c> the</c><00:01:26.820><c> backend</c><00:01:27.240><c> services</c>

00:01:29.090 --> 00:01:29.100 align:start position:0%
graph in the backend services
 

00:01:29.100 --> 00:01:33.410 align:start position:0%
graph in the backend services
um so<00:01:29.460><c> we</c><00:01:29.820><c> have</c><00:01:30.060><c> the</c><00:01:30.960><c> the</c><00:01:31.680><c> contract</c><00:01:32.640><c> for</c><00:01:32.880><c> lands</c>

00:01:33.410 --> 00:01:33.420 align:start position:0%
um so we have the the contract for lands
 

00:01:33.420 --> 00:01:35.749 align:start position:0%
um so we have the the contract for lands
which<00:01:33.780><c> where</c><00:01:34.380><c> you</c><00:01:34.740><c> can</c>

00:01:35.749 --> 00:01:35.759 align:start position:0%
which where you can
 

00:01:35.759 --> 00:01:38.810 align:start position:0%
which where you can
own<00:01:36.299><c> a</c><00:01:36.479><c> Land</c><00:01:36.659><c> and</c><00:01:37.020><c> then</c><00:01:37.220><c> let</c><00:01:38.220><c> others</c><00:01:38.640><c> have</c>

00:01:38.810 --> 00:01:38.820 align:start position:0%
own a Land and then let others have
 

00:01:38.820 --> 00:01:41.030 align:start position:0%
own a Land and then let others have
permissions<00:01:39.240><c> to</c><00:01:39.479><c> deploy</c><00:01:39.840><c> some</c><00:01:40.079><c> scene</c><00:01:40.500><c> on</c><00:01:40.860><c> the</c>

00:01:41.030 --> 00:01:41.040 align:start position:0%
permissions to deploy some scene on the
 

00:01:41.040 --> 00:01:44.569 align:start position:0%
permissions to deploy some scene on the
world<00:01:41.280><c> we</c><00:01:42.119><c> also</c><00:01:42.479><c> have</c><00:01:42.900><c> nft</c><00:01:43.560><c> collections</c><00:01:44.280><c> as</c>

00:01:44.569 --> 00:01:44.579 align:start position:0%
world we also have nft collections as
 

00:01:44.579 --> 00:01:48.050 align:start position:0%
world we also have nft collections as
well<00:01:44.900><c> where</c><00:01:45.900><c> the</c><00:01:46.200><c> wearables</c><00:01:46.860><c> creators</c><00:01:47.460><c> can</c>

00:01:48.050 --> 00:01:48.060 align:start position:0%
well where the wearables creators can
 

00:01:48.060 --> 00:01:50.630 align:start position:0%
well where the wearables creators can
meet<00:01:48.540><c> a</c><00:01:48.780><c> collection</c><00:01:49.079><c> and</c><00:01:49.619><c> then</c><00:01:49.799><c> sell</c><00:01:50.100><c> them</c><00:01:50.280><c> in</c>

00:01:50.630 --> 00:01:50.640 align:start position:0%
meet a collection and then sell them in
 

00:01:50.640 --> 00:01:52.450 align:start position:0%
meet a collection and then sell them in
the<00:01:50.759><c> marketplace</c>

00:01:52.450 --> 00:01:52.460 align:start position:0%
the marketplace
 

00:01:52.460 --> 00:01:55.370 align:start position:0%
the marketplace
and<00:01:53.460><c> then</c><00:01:53.640><c> you</c><00:01:54.240><c> as</c><00:01:54.479><c> a</c><00:01:54.659><c> user</c><00:01:54.899><c> you</c><00:01:55.079><c> can</c><00:01:55.200><c> choose</c>

00:01:55.370 --> 00:01:55.380 align:start position:0%
and then you as a user you can choose
 

00:01:55.380 --> 00:01:57.770 align:start position:0%
and then you as a user you can choose
those<00:01:55.680><c> wearables</c><00:01:56.220><c> buy</c><00:01:56.520><c> them</c><00:01:56.759><c> and</c><00:01:57.180><c> then</c><00:01:57.299><c> set</c><00:01:57.600><c> up</c>

00:01:57.770 --> 00:01:57.780 align:start position:0%
those wearables buy them and then set up
 

00:01:57.780 --> 00:02:02.690 align:start position:0%
those wearables buy them and then set up
your<00:01:58.259><c> uh</c><00:01:58.560><c> your</c><00:01:58.979><c> avatar</c><00:01:59.479><c> and</c><00:02:00.479><c> that's</c><00:02:01.439><c> where</c><00:02:01.920><c> we</c>

00:02:02.690 --> 00:02:02.700 align:start position:0%
your uh your avatar and that's where we
 

00:02:02.700 --> 00:02:06.770 align:start position:0%
your uh your avatar and that's where we
store<00:02:03.000><c> them</c><00:02:03.240><c> in</c><00:02:03.720><c> the</c><00:02:03.840><c> users</c><00:02:04.140><c> profiles</c><00:02:05.000><c> and</c><00:02:06.000><c> we</c>

00:02:06.770 --> 00:02:06.780 align:start position:0%
store them in the users profiles and we
 

00:02:06.780 --> 00:02:10.010 align:start position:0%
store them in the users profiles and we
you<00:02:07.200><c> can</c><00:02:07.740><c> also</c><00:02:07.979><c> have</c><00:02:08.099><c> a</c><00:02:08.280><c> name</c><00:02:08.459><c> in</c><00:02:08.940><c> the</c><00:02:09.060><c> sand</c><00:02:09.239><c> run</c>

00:02:10.010 --> 00:02:10.020 align:start position:0%
you can also have a name in the sand run
 

00:02:10.020 --> 00:02:13.369 align:start position:0%
you can also have a name in the sand run
and<00:02:10.679><c> that's</c><00:02:10.920><c> like</c><00:02:11.220><c> the</c><00:02:11.580><c> identity</c><00:02:12.200><c> that</c><00:02:13.200><c> you</c>

00:02:13.369 --> 00:02:13.379 align:start position:0%
and that's like the identity that you
 

00:02:13.379 --> 00:02:16.550 align:start position:0%
and that's like the identity that you
own<00:02:13.560><c> right</c><00:02:14.400><c> what</c><00:02:15.000><c> happened</c><00:02:15.540><c> with</c><00:02:15.840><c> that</c><00:02:16.080><c> there</c>

00:02:16.550 --> 00:02:16.560 align:start position:0%
own right what happened with that there
 

00:02:16.560 --> 00:02:19.550 align:start position:0%
own right what happened with that there
are<00:02:16.680><c> a</c><00:02:16.739><c> lot</c><00:02:16.860><c> of</c><00:02:17.040><c> files</c><00:02:17.700><c> and</c><00:02:18.060><c> it's</c><00:02:18.599><c> a</c><00:02:18.900><c> it's</c><00:02:19.319><c> too</c>

00:02:19.550 --> 00:02:19.560 align:start position:0%
are a lot of files and it's a it's too
 

00:02:19.560 --> 00:02:22.430 align:start position:0%
are a lot of files and it's a it's too
many<00:02:19.680><c> assets</c><00:02:20.099><c> to</c><00:02:20.340><c> store</c><00:02:20.700><c> scenes</c><00:02:21.660><c> and</c><00:02:22.020><c> free</c>

00:02:22.430 --> 00:02:22.440 align:start position:0%
many assets to store scenes and free
 

00:02:22.440 --> 00:02:25.610 align:start position:0%
many assets to store scenes and free
models<00:02:22.980><c> and</c><00:02:23.280><c> well</c><00:02:23.580><c> some</c><00:02:24.000><c> pictures</c><00:02:24.200><c> so</c><00:02:25.200><c> we</c><00:02:25.500><c> need</c>

00:02:25.610 --> 00:02:25.620 align:start position:0%
models and well some pictures so we need
 

00:02:25.620 --> 00:02:29.030 align:start position:0%
models and well some pictures so we need
to<00:02:25.860><c> store</c><00:02:26.099><c> them</c><00:02:26.540><c> in</c><00:02:27.540><c> somewhere</c><00:02:28.379><c> and</c><00:02:28.739><c> we</c><00:02:28.920><c> have</c>

00:02:29.030 --> 00:02:29.040 align:start position:0%
to store them in somewhere and we have
 

00:02:29.040 --> 00:02:31.910 align:start position:0%
to store them in somewhere and we have
to<00:02:29.160><c> delete</c><00:02:29.280><c> that</c><00:02:29.760><c> the</c><00:02:30.300><c> centralized</c><00:02:30.840><c> right</c><00:02:31.140><c> so</c>

00:02:31.910 --> 00:02:31.920 align:start position:0%
to delete that the centralized right so
 

00:02:31.920 --> 00:02:34.550 align:start position:0%
to delete that the centralized right so
what<00:02:32.280><c> we</c><00:02:32.520><c> have</c><00:02:33.120><c> are</c><00:02:33.480><c> the</c><00:02:33.660><c> centralized</c><00:02:34.200><c> servers</c>

00:02:34.550 --> 00:02:34.560 align:start position:0%
what we have are the centralized servers
 

00:02:34.560 --> 00:02:36.589 align:start position:0%
what we have are the centralized servers
we<00:02:35.040><c> just</c><00:02:35.220><c> store</c><00:02:35.400><c> all</c><00:02:35.640><c> the</c><00:02:35.819><c> data</c><00:02:36.120><c> that</c><00:02:36.420><c> the</c>

00:02:36.589 --> 00:02:36.599 align:start position:0%
we just store all the data that the
 

00:02:36.599 --> 00:02:38.809 align:start position:0%
we just store all the data that the
client<00:02:36.840><c> needs</c><00:02:37.260><c> to</c><00:02:37.319><c> to</c><00:02:37.620><c> run</c><00:02:37.860><c> right</c><00:02:38.280><c> the</c>

00:02:38.809 --> 00:02:38.819 align:start position:0%
client needs to to run right the
 

00:02:38.819 --> 00:02:41.270 align:start position:0%
client needs to to run right the
community<00:02:39.120><c> owns</c><00:02:39.900><c> the</c><00:02:40.200><c> the</c><00:02:40.440><c> servers</c><00:02:40.980><c> which</c>

00:02:41.270 --> 00:02:41.280 align:start position:0%
community owns the the servers which
 

00:02:41.280 --> 00:02:43.850 align:start position:0%
community owns the the servers which
means<00:02:41.640><c> that</c><00:02:42.000><c> there</c><00:02:42.360><c> is</c><00:02:42.540><c> a</c><00:02:43.019><c> there</c><00:02:43.379><c> isn't</c><00:02:43.739><c> around</c>

00:02:43.850 --> 00:02:43.860 align:start position:0%
means that there is a there isn't around
 

00:02:43.860 --> 00:02:49.089 align:start position:0%
means that there is a there isn't around
Dio<00:02:44.840><c> which</c><00:02:46.160><c> is</c><00:02:47.160><c> a</c><00:02:47.340><c> responsible</c><00:02:47.700><c> of</c>

00:02:49.089 --> 00:02:49.099 align:start position:0%
Dio which is a responsible of
 

00:02:49.099 --> 00:02:52.610 align:start position:0%
Dio which is a responsible of
approving<00:02:50.099><c> the</c><00:02:50.400><c> list</c><00:02:51.060><c> of</c><00:02:51.239><c> servers</c><00:02:51.720><c> that</c><00:02:52.140><c> that</c>

00:02:52.610 --> 00:02:52.620 align:start position:0%
approving the list of servers that that
 

00:02:52.620 --> 00:02:54.589 align:start position:0%
approving the list of servers that that
are<00:02:52.980><c> in</c><00:02:53.160><c> the</c><00:02:53.400><c> Dao</c>

00:02:54.589 --> 00:02:54.599 align:start position:0%
are in the Dao
 

00:02:54.599 --> 00:02:57.530 align:start position:0%
are in the Dao
so<00:02:55.260><c> they</c><00:02:55.860><c> they</c><00:02:56.340><c> have</c><00:02:56.640><c> to</c><00:02:56.760><c> synchronize</c><00:02:57.239><c> between</c>

00:02:57.530 --> 00:02:57.540 align:start position:0%
so they they have to synchronize between
 

00:02:57.540 --> 00:02:59.570 align:start position:0%
so they they have to synchronize between
them<00:02:57.840><c> because</c><00:02:58.080><c> we</c><00:02:58.680><c> have</c><00:02:58.860><c> all</c><00:02:59.160><c> the</c><00:02:59.340><c> content</c>

00:02:59.570 --> 00:02:59.580 align:start position:0%
them because we have all the content
 

00:02:59.580 --> 00:03:02.089 align:start position:0%
them because we have all the content
replicated<00:03:00.060><c> on</c><00:03:00.420><c> each</c><00:03:00.540><c> of</c><00:03:00.720><c> them</c><00:03:00.840><c> so</c><00:03:01.620><c> the</c><00:03:01.800><c> client</c>

00:03:02.089 --> 00:03:02.099 align:start position:0%
replicated on each of them so the client
 

00:03:02.099 --> 00:03:04.729 align:start position:0%
replicated on each of them so the client
can<00:03:02.340><c> connect</c><00:03:02.519><c> to</c><00:03:02.760><c> any</c><00:03:03.000><c> of</c><00:03:03.180><c> them</c><00:03:03.840><c> and</c><00:03:04.319><c> we'll</c><00:03:04.500><c> get</c>

00:03:04.729 --> 00:03:04.739 align:start position:0%
can connect to any of them and we'll get
 

00:03:04.739 --> 00:03:06.949 align:start position:0%
can connect to any of them and we'll get
the<00:03:04.920><c> same</c><00:03:05.099><c> information</c><00:03:05.340><c> right</c>

00:03:06.949 --> 00:03:06.959 align:start position:0%
the same information right
 

00:03:06.959 --> 00:03:09.530 align:start position:0%
the same information right
um the<00:03:07.200><c> way</c><00:03:07.319><c> we</c><00:03:07.500><c> do</c><00:03:07.680><c> that</c><00:03:07.860><c> is</c><00:03:08.340><c> every</c><00:03:09.000><c> every</c>

00:03:09.530 --> 00:03:09.540 align:start position:0%
um the way we do that is every every
 

00:03:09.540 --> 00:03:12.949 align:start position:0%
um the way we do that is every every
server<00:03:10.019><c> which</c><00:03:10.319><c> we</c><00:03:10.560><c> name</c><00:03:10.739><c> catalyst</c><00:03:11.400><c> is</c><00:03:12.300><c> doing</c><00:03:12.720><c> a</c>

00:03:12.949 --> 00:03:12.959 align:start position:0%
server which we name catalyst is doing a
 

00:03:12.959 --> 00:03:15.470 align:start position:0%
server which we name catalyst is doing a
polling<00:03:13.319><c> mechanism</c><00:03:13.739><c> to</c><00:03:13.980><c> all</c><00:03:14.280><c> the</c><00:03:14.459><c> others</c><00:03:14.819><c> to</c>

00:03:15.470 --> 00:03:15.480 align:start position:0%
polling mechanism to all the others to
 

00:03:15.480 --> 00:03:18.589 align:start position:0%
polling mechanism to all the others to
retrieve<00:03:15.900><c> the</c><00:03:16.019><c> files</c><00:03:16.379><c> and</c><00:03:17.099><c> the</c><00:03:17.519><c> entities</c><00:03:17.760><c> and</c>

00:03:18.589 --> 00:03:18.599 align:start position:0%
retrieve the files and the entities and
 

00:03:18.599 --> 00:03:21.410 align:start position:0%
retrieve the files and the entities and
this<00:03:19.019><c> works</c><00:03:19.319><c> okay</c><00:03:19.500><c> but</c><00:03:20.040><c> we</c><00:03:20.280><c> wanted</c><00:03:20.400><c> to</c><00:03:20.760><c> go</c><00:03:21.180><c> a</c>

00:03:21.410 --> 00:03:21.420 align:start position:0%
this works okay but we wanted to go a
 

00:03:21.420 --> 00:03:24.710 align:start position:0%
this works okay but we wanted to go a
little<00:03:21.599><c> bit</c><00:03:21.780><c> further</c><00:03:22.200><c> and</c><00:03:23.180><c> test</c><00:03:24.180><c> two</c><00:03:24.480><c> things</c>

00:03:24.710 --> 00:03:24.720 align:start position:0%
little bit further and test two things
 

00:03:24.720 --> 00:03:26.930 align:start position:0%
little bit further and test two things
the<00:03:25.379><c> first</c><00:03:25.500><c> thing</c><00:03:25.739><c> is</c><00:03:26.040><c> that</c>

00:03:26.930 --> 00:03:26.940 align:start position:0%
the first thing is that
 

00:03:26.940 --> 00:03:29.570 align:start position:0%
the first thing is that
as<00:03:27.540><c> you</c><00:03:27.780><c> may</c><00:03:27.900><c> assume</c><00:03:28.440><c> we</c><00:03:28.680><c> have</c><00:03:28.800><c> lots</c><00:03:29.159><c> of</c><00:03:29.280><c> data</c>

00:03:29.570 --> 00:03:29.580 align:start position:0%
as you may assume we have lots of data
 

00:03:29.580 --> 00:03:31.250 align:start position:0%
as you may assume we have lots of data
and<00:03:29.760><c> we</c><00:03:30.000><c> have</c><00:03:30.120><c> like</c><00:03:30.300><c> the</c><00:03:30.480><c> only</c><00:03:30.720><c> historical</c>

00:03:31.250 --> 00:03:31.260 align:start position:0%
and we have like the only historical
 

00:03:31.260 --> 00:03:33.649 align:start position:0%
and we have like the only historical
data<00:03:31.800><c> like</c><00:03:32.340><c> all</c><00:03:32.519><c> the</c><00:03:32.700><c> changes</c><00:03:33.060><c> that</c><00:03:33.360><c> have</c>

00:03:33.649 --> 00:03:33.659 align:start position:0%
data like all the changes that have
 

00:03:33.659 --> 00:03:36.589 align:start position:0%
data like all the changes that have
happened<00:03:34.019><c> on</c><00:03:34.379><c> unseen</c><00:03:34.800><c> and</c><00:03:35.580><c> also</c><00:03:35.819><c> the</c><00:03:36.239><c> way</c><00:03:36.420><c> that</c>

00:03:36.589 --> 00:03:36.599 align:start position:0%
happened on unseen and also the way that
 

00:03:36.599 --> 00:03:38.690 align:start position:0%
happened on unseen and also the way that
the<00:03:36.900><c> files</c><00:03:37.200><c> are</c><00:03:37.319><c> replicated</c><00:03:37.739><c> together</c><00:03:38.099><c> well</c>

00:03:38.690 --> 00:03:38.700 align:start position:0%
the files are replicated together well
 

00:03:38.700 --> 00:03:40.250 align:start position:0%
the files are replicated together well
let's<00:03:38.940><c> first</c><00:03:39.180><c> talk</c><00:03:39.360><c> about</c><00:03:39.540><c> the</c><00:03:39.840><c> historical</c>

00:03:40.250 --> 00:03:40.260 align:start position:0%
let's first talk about the historical
 

00:03:40.260 --> 00:03:41.570 align:start position:0%
let's first talk about the historical
data

00:03:41.570 --> 00:03:41.580 align:start position:0%
data
 

00:03:41.580 --> 00:03:43.670 align:start position:0%
data
what<00:03:42.060><c> happens</c><00:03:42.180><c> for</c><00:03:42.659><c> example</c><00:03:42.959><c> this</c><00:03:43.379><c> is</c><00:03:43.500><c> the</c>

00:03:43.670 --> 00:03:43.680 align:start position:0%
what happens for example this is the
 

00:03:43.680 --> 00:03:47.350 align:start position:0%
what happens for example this is the
Genesis<00:03:44.040><c> Plaza</c><00:03:44.519><c> for</c><00:03:44.640><c> the</c><00:03:44.819><c> sandran</c><00:03:45.299><c> which</c><00:03:45.959><c> was</c>

00:03:47.350 --> 00:03:47.360 align:start position:0%
Genesis Plaza for the sandran which was
 

00:03:47.360 --> 00:03:50.630 align:start position:0%
Genesis Plaza for the sandran which was
away<00:03:48.360><c> in</c><00:03:48.720><c> 2020</c><00:03:49.260><c> and</c><00:03:49.680><c> there</c><00:03:50.040><c> was</c><00:03:50.220><c> a</c><00:03:50.340><c> change</c><00:03:50.459><c> in</c>

00:03:50.630 --> 00:03:50.640 align:start position:0%
away in 2020 and there was a change in
 

00:03:50.640 --> 00:03:54.949 align:start position:0%
away in 2020 and there was a change in
2021<00:03:51.299><c> so</c><00:03:52.140><c> the</c><00:03:53.040><c> servers</c><00:03:53.519><c> need</c><00:03:53.940><c> to</c><00:03:54.120><c> retrieve</c><00:03:54.720><c> the</c>

00:03:54.949 --> 00:03:54.959 align:start position:0%
2021 so the servers need to retrieve the
 

00:03:54.959 --> 00:03:56.509 align:start position:0%
2021 so the servers need to retrieve the
content<00:03:55.319><c> the</c><00:03:55.500><c> latest</c><00:03:55.739><c> content</c><00:03:56.159><c> they</c><00:03:56.340><c> don't</c>

00:03:56.509 --> 00:03:56.519 align:start position:0%
content the latest content they don't
 

00:03:56.519 --> 00:03:58.550 align:start position:0%
content the latest content they don't
need<00:03:56.700><c> to</c><00:03:56.819><c> serve</c><00:03:57.120><c> the</c><00:03:57.239><c> how</c><00:03:57.540><c> was</c><00:03:57.840><c> the</c><00:03:58.080><c> sundran</c>

00:03:58.550 --> 00:03:58.560 align:start position:0%
need to serve the how was the sundran
 

00:03:58.560 --> 00:04:00.530 align:start position:0%
need to serve the how was the sundran
two<00:03:59.099><c> years</c><00:03:59.280><c> before</c><00:03:59.580><c> right</c>

00:04:00.530 --> 00:04:00.540 align:start position:0%
two years before right
 

00:04:00.540 --> 00:04:03.229 align:start position:0%
two years before right
but<00:04:01.319><c> we</c><00:04:01.680><c> want</c><00:04:01.860><c> to</c><00:04:01.980><c> store</c><00:04:02.159><c> that</c><00:04:02.400><c> data</c><00:04:02.819><c> as</c><00:04:03.000><c> a</c>

00:04:03.229 --> 00:04:03.239 align:start position:0%
but we want to store that data as a
 

00:04:03.239 --> 00:04:05.930 align:start position:0%
but we want to store that data as a
backup<00:04:03.659><c> and</c><00:04:04.200><c> for</c><00:04:04.860><c> for</c><00:04:05.159><c> example</c><00:04:05.400><c> if</c><00:04:05.640><c> you</c><00:04:05.760><c> want</c>

00:04:05.930 --> 00:04:05.940 align:start position:0%
backup and for for example if you want
 

00:04:05.940 --> 00:04:08.390 align:start position:0%
backup and for for example if you want
to<00:04:06.060><c> run</c><00:04:06.239><c> the</c><00:04:06.659><c> world</c><00:04:06.959><c> how</c><00:04:07.319><c> it</c><00:04:07.680><c> looked</c><00:04:07.980><c> a</c><00:04:08.159><c> year</c>

00:04:08.390 --> 00:04:08.400 align:start position:0%
to run the world how it looked a year
 

00:04:08.400 --> 00:04:10.970 align:start position:0%
to run the world how it looked a year
before<00:04:08.580><c> if</c><00:04:09.299><c> you</c><00:04:09.420><c> run</c><00:04:09.599><c> a</c><00:04:10.019><c> full</c><00:04:10.200><c> node</c><00:04:10.560><c> which</c>

00:04:10.970 --> 00:04:10.980 align:start position:0%
before if you run a full node which
 

00:04:10.980 --> 00:04:12.470 align:start position:0%
before if you run a full node which
means<00:04:11.280><c> that</c><00:04:11.400><c> you</c><00:04:11.580><c> have</c><00:04:11.700><c> all</c><00:04:11.879><c> the</c><00:04:12.060><c> historical</c>

00:04:12.470 --> 00:04:12.480 align:start position:0%
means that you have all the historical
 

00:04:12.480 --> 00:04:14.990 align:start position:0%
means that you have all the historical
data<00:04:12.900><c> all</c><00:04:13.439><c> you</c><00:04:13.560><c> need</c><00:04:13.680><c> to</c><00:04:13.799><c> do</c><00:04:13.980><c> is</c><00:04:14.340><c> enlarge</c><00:04:14.879><c> your</c>

00:04:14.990 --> 00:04:15.000 align:start position:0%
data all you need to do is enlarge your
 

00:04:15.000 --> 00:04:18.229 align:start position:0%
data all you need to do is enlarge your
disk<00:04:15.420><c> and</c><00:04:16.260><c> everything</c><00:04:16.560><c> will</c><00:04:16.859><c> work</c><00:04:17.100><c> okay</c><00:04:17.340><c> the</c>

00:04:18.229 --> 00:04:18.239 align:start position:0%
disk and everything will work okay the
 

00:04:18.239 --> 00:04:19.490 align:start position:0%
disk and everything will work okay the
only<00:04:18.359><c> thing</c><00:04:18.600><c> is</c><00:04:18.720><c> that</c><00:04:18.840><c> you</c><00:04:18.959><c> will</c><00:04:19.139><c> need</c><00:04:19.260><c> two</c>

00:04:19.490 --> 00:04:19.500 align:start position:0%
only thing is that you will need two
 

00:04:19.500 --> 00:04:22.790 align:start position:0%
only thing is that you will need two
terabytes<00:04:20.040><c> of</c><00:04:20.400><c> of</c><00:04:20.820><c> disk</c><00:04:21.959><c> but</c><00:04:22.320><c> if</c><00:04:22.500><c> you</c><00:04:22.560><c> want</c><00:04:22.680><c> to</c>

00:04:22.790 --> 00:04:22.800 align:start position:0%
terabytes of of disk but if you want to
 

00:04:22.800 --> 00:04:24.110 align:start position:0%
terabytes of of disk but if you want to
run<00:04:22.919><c> a</c><00:04:23.100><c> light</c><00:04:23.220><c> note</c>

00:04:24.110 --> 00:04:24.120 align:start position:0%
run a light note
 

00:04:24.120 --> 00:04:26.150 align:start position:0%
run a light note
then<00:04:24.600><c> we</c><00:04:24.780><c> you</c><00:04:24.960><c> can</c><00:04:25.139><c> enable</c><00:04:25.440><c> the</c><00:04:25.919><c> garage</c>

00:04:26.150 --> 00:04:26.160 align:start position:0%
then we you can enable the garage
 

00:04:26.160 --> 00:04:28.969 align:start position:0%
then we you can enable the garage
collection<00:04:26.699><c> which</c><00:04:27.360><c> is</c><00:04:28.080><c> a</c><00:04:28.380><c> mechanism</c><00:04:28.740><c> that</c>

00:04:28.969 --> 00:04:28.979 align:start position:0%
collection which is a mechanism that
 

00:04:28.979 --> 00:04:31.670 align:start position:0%
collection which is a mechanism that
deletes<00:04:29.400><c> all</c><00:04:29.699><c> the</c><00:04:29.940><c> all</c><00:04:30.419><c> the</c><00:04:30.600><c> files</c><00:04:31.020><c> from</c><00:04:31.560><c> the</c>

00:04:31.670 --> 00:04:31.680 align:start position:0%
deletes all the all the files from the
 

00:04:31.680 --> 00:04:34.610 align:start position:0%
deletes all the all the files from the
entities<00:04:31.979><c> that</c><00:04:32.400><c> were</c><00:04:33.060><c> written</c><00:04:33.720><c> by</c><00:04:34.020><c> new</c><00:04:34.259><c> ones</c>

00:04:34.610 --> 00:04:34.620 align:start position:0%
entities that were written by new ones
 

00:04:34.620 --> 00:04:35.629 align:start position:0%
entities that were written by new ones
right

00:04:35.629 --> 00:04:35.639 align:start position:0%
right
 

00:04:35.639 --> 00:04:38.090 align:start position:0%
right
okay<00:04:36.180><c> but</c><00:04:36.479><c> what</c><00:04:36.720><c> happens</c><00:04:36.960><c> if</c><00:04:37.440><c> all</c><00:04:37.680><c> servers</c>

00:04:38.090 --> 00:04:38.100 align:start position:0%
okay but what happens if all servers
 

00:04:38.100 --> 00:04:40.370 align:start position:0%
okay but what happens if all servers
then<00:04:38.340><c> enable</c><00:04:38.699><c> garage</c><00:04:38.940><c> collection</c><00:04:39.479><c> then</c><00:04:40.139><c> we</c>

00:04:40.370 --> 00:04:40.380 align:start position:0%
then enable garage collection then we
 

00:04:40.380 --> 00:04:42.350 align:start position:0%
then enable garage collection then we
may<00:04:40.560><c> lose</c><00:04:40.800><c> those</c><00:04:41.100><c> data</c><00:04:41.580><c> and</c><00:04:41.759><c> we</c><00:04:42.000><c> don't</c><00:04:42.120><c> want</c>

00:04:42.350 --> 00:04:42.360 align:start position:0%
may lose those data and we don't want
 

00:04:42.360 --> 00:04:45.230 align:start position:0%
may lose those data and we don't want
that<00:04:42.660><c> so</c><00:04:43.380><c> our</c><00:04:43.620><c> idea</c><00:04:43.919><c> was</c><00:04:44.100><c> to</c><00:04:44.280><c> set</c><00:04:44.460><c> up</c><00:04:44.580><c> a</c><00:04:44.759><c> node</c><00:04:44.940><c> an</c>

00:04:45.230 --> 00:04:45.240 align:start position:0%
that so our idea was to set up a node an
 

00:04:45.240 --> 00:04:47.050 align:start position:0%
that so our idea was to set up a node an
ebfs<00:04:45.840><c> node</c>

00:04:47.050 --> 00:04:47.060 align:start position:0%
ebfs node
 

00:04:47.060 --> 00:04:50.450 align:start position:0%
ebfs node
connected<00:04:48.060><c> to</c><00:04:48.360><c> a</c><00:04:48.840><c> server</c><00:04:49.320><c> which</c><00:04:49.800><c> listens</c><00:04:50.340><c> all</c>

00:04:50.450 --> 00:04:50.460 align:start position:0%
connected to a server which listens all
 

00:04:50.460 --> 00:04:52.550 align:start position:0%
connected to a server which listens all
the<00:04:50.580><c> network</c><00:04:50.759><c> and</c><00:04:51.479><c> listens</c><00:04:51.900><c> all</c><00:04:52.020><c> the</c><00:04:52.199><c> changes</c>

00:04:52.550 --> 00:04:52.560 align:start position:0%
the network and listens all the changes
 

00:04:52.560 --> 00:04:56.330 align:start position:0%
the network and listens all the changes
and<00:04:52.860><c> stores</c><00:04:53.160><c> well</c><00:04:54.060><c> pins</c><00:04:54.479><c> to</c><00:04:54.720><c> ibps</c><00:04:55.199><c> all</c><00:04:56.160><c> the</c>

00:04:56.330 --> 00:04:56.340 align:start position:0%
and stores well pins to ibps all the
 

00:04:56.340 --> 00:04:59.830 align:start position:0%
and stores well pins to ibps all the
files<00:04:56.759><c> that</c><00:04:57.360><c> are</c><00:04:57.600><c> synchronized</c><00:04:58.259><c> so</c><00:04:59.040><c> first</c><00:04:59.280><c> we</c>

00:04:59.830 --> 00:04:59.840 align:start position:0%
files that are synchronized so first we
 

00:04:59.840 --> 00:05:03.230 align:start position:0%
files that are synchronized so first we
uploaded<00:05:00.840><c> all</c><00:05:01.259><c> the</c><00:05:01.500><c> all</c><00:05:01.800><c> the</c><00:05:01.979><c> files</c>

00:05:03.230 --> 00:05:03.240 align:start position:0%
uploaded all the all the files
 

00:05:03.240 --> 00:05:05.810 align:start position:0%
uploaded all the all the files
and<00:05:04.020><c> now</c><00:05:04.259><c> and</c><00:05:04.979><c> then</c>

00:05:05.810 --> 00:05:05.820 align:start position:0%
and now and then
 

00:05:05.820 --> 00:05:08.150 align:start position:0%
and now and then
um<00:05:05.880><c> we</c><00:05:06.180><c> set</c><00:05:06.419><c> up</c><00:05:06.540><c> the</c><00:05:06.780><c> server</c><00:05:07.320><c> to</c><00:05:07.620><c> listen</c><00:05:07.860><c> all</c>

00:05:08.150 --> 00:05:08.160 align:start position:0%
um we set up the server to listen all
 

00:05:08.160 --> 00:05:10.450 align:start position:0%
um we set up the server to listen all
the<00:05:08.220><c> changes</c><00:05:08.520><c> and</c><00:05:08.759><c> automatically</c>

00:05:10.450 --> 00:05:10.460 align:start position:0%
the changes and automatically
 

00:05:10.460 --> 00:05:13.850 align:start position:0%
the changes and automatically
pins<00:05:11.460><c> the</c><00:05:11.759><c> new</c><00:05:12.060><c> files</c><00:05:12.540><c> and</c><00:05:13.199><c> the</c><00:05:13.440><c> other</c><00:05:13.560><c> thing</c>

00:05:13.850 --> 00:05:13.860 align:start position:0%
pins the new files and the other thing
 

00:05:13.860 --> 00:05:16.550 align:start position:0%
pins the new files and the other thing
is<00:05:14.280><c> the</c><00:05:14.580><c> files</c><00:05:15.000><c> replication</c><00:05:15.479><c> which</c><00:05:16.020><c> we</c><00:05:16.259><c> what</c>

00:05:16.550 --> 00:05:16.560 align:start position:0%
is the files replication which we what
 

00:05:16.560 --> 00:05:19.490 align:start position:0%
is the files replication which we what
is<00:05:16.740><c> that</c><00:05:16.860><c> well</c><00:05:17.280><c> the</c><00:05:17.880><c> way</c><00:05:18.000><c> that</c><00:05:18.240><c> we</c><00:05:18.600><c> share</c><00:05:19.259><c> those</c>

00:05:19.490 --> 00:05:19.500 align:start position:0%
is that well the way that we share those
 

00:05:19.500 --> 00:05:21.530 align:start position:0%
is that well the way that we share those
files<00:05:19.860><c> between</c><00:05:19.979><c> the</c><00:05:20.280><c> servers</c><00:05:20.699><c> we</c><00:05:21.300><c> are</c><00:05:21.419><c> doing</c>

00:05:21.530 --> 00:05:21.540 align:start position:0%
files between the servers we are doing
 

00:05:21.540 --> 00:05:25.490 align:start position:0%
files between the servers we are doing
it<00:05:21.840><c> by</c><00:05:22.320><c> HTTP</c><00:05:23.280><c> request</c><00:05:23.759><c> and</c><00:05:24.720><c> it's</c><00:05:25.020><c> a</c><00:05:25.199><c> full</c><00:05:25.320><c> match</c>

00:05:25.490 --> 00:05:25.500 align:start position:0%
it by HTTP request and it's a full match
 

00:05:25.500 --> 00:05:27.770 align:start position:0%
it by HTTP request and it's a full match
topology<00:05:25.919><c> right</c><00:05:26.340><c> because</c><00:05:26.639><c> every</c><00:05:27.180><c> node</c><00:05:27.600><c> is</c>

00:05:27.770 --> 00:05:27.780 align:start position:0%
topology right because every node is
 

00:05:27.780 --> 00:05:30.890 align:start position:0%
topology right because every node is
talking<00:05:28.560><c> to</c><00:05:28.860><c> every</c><00:05:29.039><c> other</c><00:05:29.220><c> node</c>

00:05:30.890 --> 00:05:30.900 align:start position:0%
talking to every other node
 

00:05:30.900 --> 00:05:33.110 align:start position:0%
talking to every other node
um oh<00:05:31.139><c> I</c><00:05:31.440><c> think</c><00:05:31.560><c> I</c><00:05:31.740><c> was</c><00:05:31.860><c> well</c>

00:05:33.110 --> 00:05:33.120 align:start position:0%
um oh I think I was well
 

00:05:33.120 --> 00:05:37.610 align:start position:0%
um oh I think I was well
what<00:05:33.840><c> what</c><00:05:33.840><c> happens</c><00:05:34.680><c> if</c><00:05:35.220><c> we</c><00:05:35.520><c> use</c><00:05:36.300><c> ibps</c><00:05:36.840><c> and</c><00:05:37.500><c> we</c>

00:05:37.610 --> 00:05:37.620 align:start position:0%
what what happens if we use ibps and we
 

00:05:37.620 --> 00:05:40.370 align:start position:0%
what what happens if we use ibps and we
leverage<00:05:37.919><c> that</c><00:05:38.759><c> so</c><00:05:39.479><c> we</c><00:05:39.780><c> don't</c><00:05:39.900><c> have</c><00:05:40.080><c> to</c><00:05:40.199><c> care</c>

00:05:40.370 --> 00:05:40.380 align:start position:0%
leverage that so we don't have to care
 

00:05:40.380 --> 00:05:42.050 align:start position:0%
leverage that so we don't have to care
about<00:05:40.620><c> synchronizing</c><00:05:41.340><c> files</c><00:05:41.639><c> we</c><00:05:41.699><c> only</c><00:05:41.880><c> have</c>

00:05:42.050 --> 00:05:42.060 align:start position:0%
about synchronizing files we only have
 

00:05:42.060 --> 00:05:44.990 align:start position:0%
about synchronizing files we only have
to<00:05:42.240><c> care</c><00:05:42.419><c> about</c><00:05:43.080><c> the</c><00:05:43.800><c> evaluations</c><00:05:44.520><c> that</c><00:05:44.820><c> we</c>

00:05:44.990 --> 00:05:45.000 align:start position:0%
to care about the evaluations that we
 

00:05:45.000 --> 00:05:47.150 align:start position:0%
to care about the evaluations that we
need<00:05:45.060><c> to</c><00:05:45.180><c> do</c><00:05:45.300><c> to</c><00:05:45.660><c> the</c><00:05:45.720><c> blockchain</c><00:05:46.199><c> and</c><00:05:46.919><c> the</c>

00:05:47.150 --> 00:05:47.160 align:start position:0%
need to do to the blockchain and the
 

00:05:47.160 --> 00:05:49.850 align:start position:0%
need to do to the blockchain and the
entities<00:05:47.460><c> and</c><00:05:48.000><c> the</c><00:05:48.180><c> way</c><00:05:48.360><c> that</c><00:05:49.199><c> we</c><00:05:49.440><c> need</c><00:05:49.620><c> to</c>

00:05:49.850 --> 00:05:49.860 align:start position:0%
entities and the way that we need to
 

00:05:49.860 --> 00:05:52.249 align:start position:0%
entities and the way that we need to
retrieve<00:05:50.220><c> those</c><00:05:50.400><c> files</c><00:05:50.820><c> but</c>

00:05:52.249 --> 00:05:52.259 align:start position:0%
retrieve those files but
 

00:05:52.259 --> 00:05:55.670 align:start position:0%
retrieve those files but
we<00:05:52.919><c> con</c><00:05:53.280><c> we</c><00:05:54.000><c> only</c><00:05:54.300><c> would</c><00:05:54.900><c> need</c><00:05:55.139><c> to</c><00:05:55.320><c> know</c><00:05:55.440><c> the</c>

00:05:55.670 --> 00:05:55.680 align:start position:0%
we con we only would need to know the
 

00:05:55.680 --> 00:05:59.770 align:start position:0%
we con we only would need to know the
hashes<00:05:56.039><c> that</c><00:05:56.220><c> we</c><00:05:56.340><c> need</c><00:05:56.460><c> to</c><00:05:56.520><c> pin</c><00:05:56.820><c> and</c><00:05:57.180><c> then</c>

00:05:59.770 --> 00:05:59.780 align:start position:0%
 
 

00:05:59.780 --> 00:06:03.890 align:start position:0%
 
all<00:06:00.800><c> of</c><00:06:01.800><c> that</c><00:06:02.100><c> part</c><00:06:02.280><c> themselves</c><00:06:03.000><c> so</c><00:06:03.660><c> that's</c>

00:06:03.890 --> 00:06:03.900 align:start position:0%
all of that part themselves so that's
 

00:06:03.900 --> 00:06:07.550 align:start position:0%
all of that part themselves so that's
our<00:06:04.199><c> idea</c><00:06:04.740><c> on</c><00:06:05.340><c> a</c><00:06:05.520><c> trial</c><00:06:06.120><c> to</c><00:06:06.419><c> to</c><00:06:06.780><c> make</c><00:06:07.020><c> something</c>

00:06:07.550 --> 00:06:07.560 align:start position:0%
our idea on a trial to to make something
 

00:06:07.560 --> 00:06:08.810 align:start position:0%
our idea on a trial to to make something
different

00:06:08.810 --> 00:06:08.820 align:start position:0%
different
 

00:06:08.820 --> 00:06:12.050 align:start position:0%
different
um test<00:06:09.360><c> if</c><00:06:09.780><c> we</c><00:06:10.320><c> can</c><00:06:10.440><c> Leverage</c><00:06:10.919><c> The</c><00:06:11.100><c> ipvs</c><00:06:11.759><c> to</c>

00:06:12.050 --> 00:06:12.060 align:start position:0%
um test if we can Leverage The ipvs to
 

00:06:12.060 --> 00:06:13.850 align:start position:0%
um test if we can Leverage The ipvs to
work<00:06:12.300><c> that</c>

00:06:13.850 --> 00:06:13.860 align:start position:0%
work that
 

00:06:13.860 --> 00:06:15.710 align:start position:0%
work that
um that's<00:06:14.220><c> all</c><00:06:14.520><c> thank</c><00:06:14.820><c> you</c><00:06:15.060><c> I</c><00:06:15.539><c> was</c><00:06:15.660><c> just</c>

00:06:15.710 --> 00:06:15.720 align:start position:0%
um that's all thank you I was just
 

00:06:15.720 --> 00:06:16.909 align:start position:0%
um that's all thank you I was just
wondering<00:06:16.020><c> could</c><00:06:16.259><c> you</c><00:06:16.380><c> speak</c><00:06:16.560><c> a</c><00:06:16.740><c> little</c><00:06:16.800><c> bit</c>

00:06:16.909 --> 00:06:16.919 align:start position:0%
wondering could you speak a little bit
 

00:06:16.919 --> 00:06:19.730 align:start position:0%
wondering could you speak a little bit
about<00:06:17.100><c> your</c><00:06:17.400><c> decision</c><00:06:17.759><c> to</c><00:06:18.360><c> use</c><00:06:18.539><c> ipfs</c><00:06:19.320><c> instead</c>

00:06:19.730 --> 00:06:19.740 align:start position:0%
about your decision to use ipfs instead
 

00:06:19.740 --> 00:06:22.010 align:start position:0%
about your decision to use ipfs instead
of<00:06:19.860><c> RV</c><00:06:20.340><c> for</c><00:06:20.759><c> storing</c><00:06:21.180><c> historical</c><00:06:21.600><c> data</c>

00:06:22.010 --> 00:06:22.020 align:start position:0%
of RV for storing historical data
 

00:06:22.020 --> 00:06:24.529 align:start position:0%
of RV for storing historical data
instead<00:06:22.500><c> of</c><00:06:22.560><c> our</c><00:06:23.400><c> weave</c><00:06:23.759><c> for</c><00:06:24.000><c> like</c><00:06:24.180><c> permanent</c>

00:06:24.529 --> 00:06:24.539 align:start position:0%
instead of our weave for like permanent
 

00:06:24.539 --> 00:06:27.550 align:start position:0%
instead of our weave for like permanent
data<00:06:24.960><c> to</c><00:06:25.080><c> store</c><00:06:25.319><c> like</c><00:06:25.560><c> historical</c><00:06:25.919><c> data</c><00:06:26.419><c> we</c><00:06:27.419><c> we</c>

00:06:27.550 --> 00:06:27.560 align:start position:0%
data to store like historical data we we
 

00:06:27.560 --> 00:06:30.710 align:start position:0%
data to store like historical data we we
currently<00:06:28.560><c> have</c><00:06:29.100><c> the</c><00:06:29.460><c> the</c><00:06:29.759><c> data</c><00:06:30.240><c> stored</c>

00:06:30.710 --> 00:06:30.720 align:start position:0%
currently have the the data stored
 

00:06:30.720 --> 00:06:33.590 align:start position:0%
currently have the the data stored
locally<00:06:30.960><c> like</c><00:06:31.319><c> in</c><00:06:31.440><c> the</c><00:06:31.620><c> file</c><00:06:31.800><c> system</c><00:06:32.100><c> and</c><00:06:33.060><c> we</c>

00:06:33.590 --> 00:06:33.600 align:start position:0%
locally like in the file system and we
 

00:06:33.600 --> 00:06:37.430 align:start position:0%
locally like in the file system and we
have<00:06:34.020><c> the</c><00:06:34.680><c> the</c><00:06:35.240><c> way</c><00:06:36.240><c> to</c><00:06:36.479><c> configure</c><00:06:36.960><c> that</c><00:06:37.199><c> and</c>

00:06:37.430 --> 00:06:37.440 align:start position:0%
have the the way to configure that and
 

00:06:37.440 --> 00:06:39.290 align:start position:0%
have the the way to configure that and
store<00:06:37.800><c> if</c><00:06:38.220><c> you</c><00:06:38.340><c> were</c><00:06:38.520><c> running</c><00:06:38.699><c> out</c><00:06:38.940><c> and</c><00:06:39.120><c> want</c>

00:06:39.290 --> 00:06:39.300 align:start position:0%
store if you were running out and want
 

00:06:39.300 --> 00:06:41.990 align:start position:0%
store if you were running out and want
to<00:06:39.360><c> store</c><00:06:39.539><c> them</c><00:06:39.780><c> on</c><00:06:40.259><c> as</c><00:06:40.380><c> free</c><00:06:40.740><c> you</c><00:06:41.039><c> can</c><00:06:41.160><c> we</c><00:06:41.880><c> have</c>

00:06:41.990 --> 00:06:42.000 align:start position:0%
to store them on as free you can we have
 

00:06:42.000 --> 00:06:44.090 align:start position:0%
to store them on as free you can we have
been<00:06:42.180><c> thinking</c><00:06:42.539><c> a</c><00:06:42.720><c> lot</c><00:06:42.840><c> about</c><00:06:43.080><c> the</c><00:06:43.680><c> way</c><00:06:43.860><c> that</c>

00:06:44.090 --> 00:06:44.100 align:start position:0%
been thinking a lot about the way that
 

00:06:44.100 --> 00:06:46.610 align:start position:0%
been thinking a lot about the way that
the<00:06:44.280><c> catalysts</c><00:06:44.940><c> sing</c><00:06:45.240><c> each</c><00:06:45.419><c> other</c><00:06:45.600><c> and</c><00:06:46.319><c> we've</c>

00:06:46.610 --> 00:06:46.620 align:start position:0%
the catalysts sing each other and we've
 

00:06:46.620 --> 00:06:49.129 align:start position:0%
the catalysts sing each other and we've
been<00:06:46.680><c> assigned</c><00:06:47.039><c> a</c><00:06:47.160><c> lot</c><00:06:47.220><c> how</c><00:06:47.520><c> ipvs</c><00:06:48.240><c> does</c><00:06:48.600><c> that</c>

00:06:49.129 --> 00:06:49.139 align:start position:0%
been assigned a lot how ipvs does that
 

00:06:49.139 --> 00:06:51.950 align:start position:0%
been assigned a lot how ipvs does that
so<00:06:49.860><c> that's</c><00:06:50.039><c> why</c><00:06:50.220><c> I</c><00:06:50.400><c> think</c><00:06:50.520><c> we</c><00:06:50.759><c> chose</c><00:06:51.000><c> ibps</c><00:06:51.539><c> to</c>

00:06:51.950 --> 00:06:51.960 align:start position:0%
so that's why I think we chose ibps to
 

00:06:51.960 --> 00:06:53.749 align:start position:0%
so that's why I think we chose ibps to
test<00:06:52.199><c> this</c>

00:06:53.749 --> 00:06:53.759 align:start position:0%
test this
 

00:06:53.759 --> 00:06:55.850 align:start position:0%
test this
um<00:06:53.819><c> but</c><00:06:54.300><c> we</c><00:06:54.479><c> have</c><00:06:54.720><c> done</c><00:06:54.900><c> so</c><00:06:55.080><c> far</c><00:06:55.199><c> it's</c><00:06:55.380><c> only</c><00:06:55.560><c> the</c>

00:06:55.850 --> 00:06:55.860 align:start position:0%
um but we have done so far it's only the
 

00:06:55.860 --> 00:06:58.309 align:start position:0%
um but we have done so far it's only the
historical<00:06:56.580><c> data</c><00:06:57.360><c> right</c><00:06:57.479><c> we</c><00:06:57.780><c> haven't</c><00:06:57.960><c> done</c>

00:06:58.309 --> 00:06:58.319 align:start position:0%
historical data right we haven't done
 

00:06:58.319 --> 00:07:01.490 align:start position:0%
historical data right we haven't done
used<00:06:58.860><c> the</c><00:06:59.160><c> ipvs</c><00:06:59.759><c> to</c><00:07:00.000><c> run</c><00:07:00.300><c> the</c><00:07:00.479><c> sync</c>

00:07:01.490 --> 00:07:01.500 align:start position:0%
used the ipvs to run the sync
 

00:07:01.500 --> 00:07:04.490 align:start position:0%
used the ipvs to run the sync
how<00:07:02.039><c> do</c><00:07:02.160><c> you</c><00:07:02.280><c> handle</c><00:07:02.639><c> content</c><00:07:03.479><c> moderation</c><00:07:03.960><c> or</c>

00:07:04.490 --> 00:07:04.500 align:start position:0%
how do you handle content moderation or
 

00:07:04.500 --> 00:07:06.469 align:start position:0%
how do you handle content moderation or
cases<00:07:04.860><c> where</c><00:07:05.220><c> like</c><00:07:05.580><c> certain</c><00:07:05.940><c> content</c><00:07:06.360><c> or</c>

00:07:06.469 --> 00:07:06.479 align:start position:0%
cases where like certain content or
 

00:07:06.479 --> 00:07:08.270 align:start position:0%
cases where like certain content or
files<00:07:06.900><c> might</c><00:07:07.199><c> be</c><00:07:07.440><c> illegal</c><00:07:07.919><c> in</c><00:07:08.100><c> certain</c>

00:07:08.270 --> 00:07:08.280 align:start position:0%
files might be illegal in certain
 

00:07:08.280 --> 00:07:09.950 align:start position:0%
files might be illegal in certain
countries<00:07:08.699><c> but</c><00:07:09.060><c> would</c><00:07:09.240><c> be</c><00:07:09.360><c> valid</c><00:07:09.660><c> in</c><00:07:09.780><c> other</c>

00:07:09.950 --> 00:07:09.960 align:start position:0%
countries but would be valid in other
 

00:07:09.960 --> 00:07:10.850 align:start position:0%
countries but would be valid in other
ones

00:07:10.850 --> 00:07:10.860 align:start position:0%
ones
 

00:07:10.860 --> 00:07:13.010 align:start position:0%
ones
well<00:07:11.400><c> the</c><00:07:11.580><c> way</c><00:07:11.699><c> that</c>

00:07:13.010 --> 00:07:13.020 align:start position:0%
well the way that
 

00:07:13.020 --> 00:07:16.610 align:start position:0%
well the way that
way now<00:07:13.380><c> is</c><00:07:14.060><c> each</c><00:07:15.060><c> of</c><00:07:15.300><c> the</c><00:07:15.419><c> servers</c><00:07:15.900><c> has</c><00:07:16.319><c> an</c>

00:07:16.610 --> 00:07:16.620 align:start position:0%
way now is each of the servers has an
 

00:07:16.620 --> 00:07:19.610 align:start position:0%
way now is each of the servers has an
owner<00:07:16.979><c> and</c><00:07:17.940><c> it's</c><00:07:18.539><c> there's</c><00:07:18.720><c> a</c><00:07:19.020><c> responsibility</c>

00:07:19.610 --> 00:07:19.620 align:start position:0%
owner and it's there's a responsibility
 

00:07:19.620 --> 00:07:23.870 align:start position:0%
owner and it's there's a responsibility
to<00:07:20.520><c> deny</c><00:07:21.060><c> list</c><00:07:21.240><c> some</c><00:07:21.660><c> entities</c><00:07:22.380><c> or</c><00:07:22.800><c> files</c><00:07:23.340><c> or</c>

00:07:23.870 --> 00:07:23.880 align:start position:0%
to deny list some entities or files or
 

00:07:23.880 --> 00:07:26.990 align:start position:0%
to deny list some entities or files or
they<00:07:24.539><c> think</c><00:07:24.780><c> that</c><00:07:25.080><c> they</c><00:07:25.259><c> need</c><00:07:25.500><c> to</c><00:07:25.680><c> moderate</c><00:07:26.099><c> so</c>

00:07:26.990 --> 00:07:27.000 align:start position:0%
they think that they need to moderate so
 

00:07:27.000 --> 00:07:30.110 align:start position:0%
they think that they need to moderate so
we<00:07:27.240><c> I</c><00:07:27.419><c> we</c><00:07:27.840><c> are</c><00:07:27.960><c> we</c><00:07:28.380><c> are</c><00:07:28.560><c> not</c><00:07:28.740><c> taking</c><00:07:29.280><c> care</c><00:07:30.000><c> of</c>

00:07:30.110 --> 00:07:30.120 align:start position:0%
we I we are we are not taking care of
 

00:07:30.120 --> 00:07:31.969 align:start position:0%
we I we are we are not taking care of
the<00:07:30.300><c> moderation</c><00:07:30.660><c> ourselves</c><00:07:31.199><c> we're</c><00:07:31.500><c> letting</c>

00:07:31.969 --> 00:07:31.979 align:start position:0%
the moderation ourselves we're letting
 

00:07:31.979 --> 00:07:34.070 align:start position:0%
the moderation ourselves we're letting
the<00:07:32.220><c> owners</c><00:07:32.580><c> of</c><00:07:32.759><c> the</c><00:07:32.940><c> Catalyst</c><00:07:33.419><c> do</c><00:07:33.660><c> themselves</c>

00:07:34.070 --> 00:07:34.080 align:start position:0%
the owners of the Catalyst do themselves
 

00:07:34.080 --> 00:07:35.870 align:start position:0%
the owners of the Catalyst do themselves
we<00:07:34.440><c> we</c><00:07:34.680><c> only</c><00:07:34.860><c> provide</c><00:07:35.220><c> the</c><00:07:35.340><c> mechanism</c><00:07:35.639><c> for</c>

00:07:35.870 --> 00:07:35.880 align:start position:0%
we we only provide the mechanism for
 

00:07:35.880 --> 00:07:38.510 align:start position:0%
we we only provide the mechanism for
them<00:07:36.000><c> to</c><00:07:36.360><c> to</c><00:07:36.660><c> remove</c><00:07:37.080><c> to</c><00:07:37.680><c> remove</c><00:07:37.860><c> those</c><00:07:38.220><c> files</c>

00:07:38.510 --> 00:07:38.520 align:start position:0%
them to to remove to remove those files
 

00:07:38.520 --> 00:07:42.560 align:start position:0%
them to to remove to remove those files
and<00:07:38.699><c> don't</c><00:07:38.880><c> serve</c><00:07:39.300><c> them</c><00:07:39.900><c> thank</c><00:07:40.440><c> you</c>