WEBVTT Kind: captions Language: en 00:00:14.289 --> 00:00:16.750 align:start position:0% alright<00:00:15.289> that<00:00:16.190> works 00:00:16.750 --> 00:00:16.760 align:start position:0% alright that works 00:00:16.760 --> 00:00:21.280 align:start position:0% alright that works hello<00:00:17.030> everyone<00:00:17.470> it's<00:00:18.470> me<00:00:18.530> here<00:00:19.030> so<00:00:20.030> where<00:00:20.990> I'm 00:00:21.280 --> 00:00:21.290 align:start position:0% hello everyone it's me here so where I'm 00:00:21.290 --> 00:00:21.940 align:start position:0% hello everyone it's me here so where I'm for<00:00:21.500> Mackenzie 00:00:21.940 --> 00:00:21.950 align:start position:0% for Mackenzie 00:00:21.950 --> 00:00:24.040 align:start position:0% for Mackenzie I'm<00:00:22.130> from<00:00:22.550> Jack<00:00:22.850> if<00:00:23.120> anyone<00:00:23.390> knows<00:00:23.540> us<00:00:23.750> we<00:00:23.930> are 00:00:24.040 --> 00:00:24.050 align:start position:0% I'm from Jack if anyone knows us we are 00:00:24.050 --> 00:00:26.770 align:start position:0% I'm from Jack if anyone knows us we are in<00:00:24.380> the<00:00:24.530> music<00:00:24.890> and<00:00:25.040> media<00:00:25.220> space<00:00:25.610> the<00:00:26.300> name<00:00:26.690> of 00:00:26.770 --> 00:00:26.780 align:start position:0% in the music and media space the name of 00:00:26.780 --> 00:00:29.170 align:start position:0% in the music and media space the name of the<00:00:27.010> presentation<00:00:28.010> today<00:00:28.310> is<00:00:28.550> a<00:00:28.580> new<00:00:28.790> engine 00:00:29.170 --> 00:00:29.180 align:start position:0% the presentation today is a new engine 00:00:29.180 --> 00:00:31.630 align:start position:0% the presentation today is a new engine to<00:00:29.210> power<00:00:29.450> the<00:00:29.510> web<00:00:29.960> of<00:00:30.110> content<00:00:30.560> and<00:00:30.770> I<00:00:31.460> just 00:00:31.630 --> 00:00:31.640 align:start position:0% to power the web of content and I just 00:00:31.640 --> 00:00:33.549 align:start position:0% to power the web of content and I just really<00:00:31.789> wanted<00:00:31.940> to<00:00:32.059> start<00:00:32.270> first<00:00:32.480> by<00:00:32.719> by<00:00:33.379> kind 00:00:33.549 --> 00:00:33.559 align:start position:0% really wanted to start first by by kind 00:00:33.559 --> 00:00:35.260 align:start position:0% really wanted to start first by by kind of<00:00:33.590> acknowledging<00:00:34.040> that<00:00:34.190> you<00:00:34.550> know<00:00:34.640> in<00:00:35.060> terms 00:00:35.260 --> 00:00:35.270 align:start position:0% of acknowledging that you know in terms 00:00:35.270 --> 00:00:37.150 align:start position:0% of acknowledging that you know in terms of<00:00:35.360> music<00:00:35.570> there<00:00:35.960> are<00:00:35.990> a<00:00:36.140> lot<00:00:36.410> of<00:00:36.440> music 00:00:37.150 --> 00:00:37.160 align:start position:0% of music there are a lot of music 00:00:37.160 --> 00:00:39.100 align:start position:0% of music there are a lot of music blockchain<00:00:37.520> startups<00:00:37.910> in<00:00:38.000> the<00:00:38.030> space<00:00:38.300> so<00:00:39.020> it 00:00:39.100 --> 00:00:39.110 align:start position:0% blockchain startups in the space so it 00:00:39.110 --> 00:00:40.330 align:start position:0% blockchain startups in the space so it be<00:00:39.200> a<00:00:39.230> good<00:00:39.350> idea<00:00:39.440> really<00:00:39.739> to<00:00:39.950> just<00:00:40.130> kind<00:00:40.280> of 00:00:40.330 --> 00:00:40.340 align:start position:0% be a good idea really to just kind of 00:00:40.340 --> 00:00:42.280 align:start position:0% be a good idea really to just kind of recap<00:00:40.700> why<00:00:41.000> we're<00:00:41.360> in<00:00:41.480> the<00:00:41.570> space<00:00:41.810> and<00:00:42.020> why<00:00:42.140> we 00:00:42.280 --> 00:00:42.290 align:start position:0% recap why we're in the space and why we 00:00:42.290 --> 00:00:43.360 align:start position:0% recap why we're in the space and why we really<00:00:42.440> think<00:00:42.739> that<00:00:42.770> music<00:00:43.100> and<00:00:43.190> blockchain 00:00:43.360 --> 00:00:43.370 align:start position:0% really think that music and blockchain 00:00:43.370 --> 00:00:46.120 align:start position:0% really think that music and blockchain really<00:00:43.790> do<00:00:44.000> make<00:00:44.390> sense<00:00:44.660> and<00:00:45.050> yep<00:00:45.680> take<00:00:45.920> a<00:00:45.950> word 00:00:46.120 --> 00:00:46.130 align:start position:0% really do make sense and yep take a word 00:00:46.130 --> 00:00:49.389 align:start position:0% really do make sense and yep take a word so<00:00:46.460> first<00:00:47.450> of<00:00:47.540> all<00:00:47.570> what<00:00:47.780> is<00:00:47.960> the<00:00:48.170> problem<00:00:48.530> and 00:00:49.389 --> 00:00:49.399 align:start position:0% so first of all what is the problem and 00:00:49.399 --> 00:00:52.300 align:start position:0% so first of all what is the problem and I<00:00:49.489> think<00:00:49.520> that<00:00:49.840> the<00:00:50.840> way<00:00:50.930> that<00:00:51.079> most<00:00:51.649> people<00:00:52.130> as 00:00:52.300 --> 00:00:52.310 align:start position:0% I think that the way that most people as 00:00:52.310 --> 00:00:54.430 align:start position:0% I think that the way that most people as consumers<00:00:52.880> experience<00:00:53.120> music<00:00:53.420> is<00:00:53.840> that<00:00:54.320> we 00:00:54.430 --> 00:00:54.440 align:start position:0% consumers experience music is that we 00:00:54.440 --> 00:00:56.680 align:start position:0% consumers experience music is that we just<00:00:54.470> think<00:00:54.770> of<00:00:54.860> a<00:00:54.920> song<00:00:55.160> as<00:00:55.280> an<00:00:55.370> mp3<00:00:55.610> so<00:00:56.059> when 00:00:56.680 --> 00:00:56.690 align:start position:0% just think of a song as an mp3 so when 00:00:56.690 --> 00:00:58.299 align:start position:0% just think of a song as an mp3 so when we<00:00:56.809> play<00:00:57.079> a<00:00:57.110> song<00:00:57.410> or<00:00:57.559> we<00:00:57.649> hear<00:00:57.860> a<00:00:57.890> song<00:00:58.100> playing 00:00:58.299 --> 00:00:58.309 align:start position:0% we play a song or we hear a song playing 00:00:58.309 --> 00:01:00.190 align:start position:0% we play a song or we hear a song playing we<00:00:58.460> just<00:00:58.489> think<00:00:58.820> that's<00:00:59.090> a<00:00:59.239> song<00:00:59.480> play<00:01:00.079> the 00:01:00.190 --> 00:01:00.200 align:start position:0% we just think that's a song play the 00:01:00.200 --> 00:01:01.389 align:start position:0% we just think that's a song play the song<00:01:00.410> that's<00:01:00.770> what<00:01:00.950> I<00:01:01.010> need<00:01:01.160> to<00:01:01.190> worry<00:01:01.340> about 00:01:01.389 --> 00:01:01.399 align:start position:0% song that's what I need to worry about 00:01:01.399 --> 00:01:04.030 align:start position:0% song that's what I need to worry about the<00:01:01.940> problem<00:01:02.300> with<00:01:02.390> music<00:01:02.750> is<00:01:02.960> very<00:01:03.230> hard<00:01:03.950> to 00:01:04.030 --> 00:01:04.040 align:start position:0% the problem with music is very hard to 00:01:04.040 --> 00:01:05.770 align:start position:0% the problem with music is very hard to figure<00:01:04.159> out<00:01:04.250> who<00:01:04.339> to<00:01:04.519> pay<00:01:04.699> and<00:01:05.390> that's<00:01:05.479> because 00:01:05.770 --> 00:01:05.780 align:start position:0% figure out who to pay and that's because 00:01:05.780 --> 00:01:09.640 align:start position:0% figure out who to pay and that's because a<00:01:05.900> song<00:01:06.380> is<00:01:06.680> actually<00:01:07.570> kind<00:01:08.570> of<00:01:08.600> complex<00:01:08.930> so 00:01:09.640 --> 00:01:09.650 align:start position:0% a song is actually kind of complex so 00:01:09.650 --> 00:01:11.920 align:start position:0% a song is actually kind of complex so let's<00:01:10.549> say<00:01:10.729> that<00:01:10.940> a<00:01:10.970> few<00:01:11.360> people<00:01:11.390> get<00:01:11.780> in<00:01:11.870> the 00:01:11.920 --> 00:01:11.930 align:start position:0% let's say that a few people get in the 00:01:11.930 --> 00:01:13.300 align:start position:0% let's say that a few people get in the studio<00:01:12.170> and<00:01:12.350> they<00:01:12.470> start<00:01:12.680> working<00:01:12.860> on<00:01:13.130> some 00:01:13.300 --> 00:01:13.310 align:start position:0% studio and they start working on some 00:01:13.310 --> 00:01:15.010 align:start position:0% studio and they start working on some music<00:01:13.460> you<00:01:13.850> actually<00:01:14.420> are<00:01:14.510> creating<00:01:14.810> a<00:01:14.870> very 00:01:15.010 --> 00:01:15.020 align:start position:0% music you actually are creating a very 00:01:15.020 --> 00:01:17.140 align:start position:0% music you actually are creating a very complex<00:01:15.440> ownership<00:01:15.890> structure<00:01:16.280> the<00:01:16.909> reason 00:01:17.140 --> 00:01:17.150 align:start position:0% complex ownership structure the reason 00:01:17.150 --> 00:01:18.969 align:start position:0% complex ownership structure the reason why<00:01:17.240> is<00:01:17.299> a<00:01:17.510> song<00:01:17.780> which<00:01:18.110> actually<00:01:18.409> is<00:01:18.619> not 00:01:18.969 --> 00:01:18.979 align:start position:0% why is a song which actually is not 00:01:18.979 --> 00:01:20.680 align:start position:0% why is a song which actually is not represented<00:01:19.640> in<00:01:19.820> the<00:01:19.909> music<00:01:20.270> industry<00:01:20.390> don't 00:01:20.680 --> 00:01:20.690 align:start position:0% represented in the music industry don't 00:01:20.690 --> 00:01:21.640 align:start position:0% represented in the music industry don't really<00:01:20.930> think<00:01:21.049> of<00:01:21.260> songs<00:01:21.470> they<00:01:21.619> have 00:01:21.640 --> 00:01:21.650 align:start position:0% really think of songs they have 00:01:21.650 --> 00:01:22.930 align:start position:0% really think of songs they have completely<00:01:22.250> other<00:01:22.400> terms<00:01:22.700> to<00:01:22.790> describe 00:01:22.930 --> 00:01:22.940 align:start position:0% completely other terms to describe 00:01:22.940 --> 00:01:25.060 align:start position:0% completely other terms to describe things<00:01:23.330> songs<00:01:23.630> are<00:01:23.780> just<00:01:23.900> for<00:01:24.020> consumers<00:01:24.409> but 00:01:25.060 --> 00:01:25.070 align:start position:0% things songs are just for consumers but 00:01:25.070 --> 00:01:26.560 align:start position:0% things songs are just for consumers but you<00:01:25.159> have<00:01:25.250> this<00:01:25.340> thing<00:01:25.640> called<00:01:26.090> a<00:01:26.180> recording 00:01:26.560 --> 00:01:26.570 align:start position:0% you have this thing called a recording 00:01:26.570 --> 00:01:28.300 align:start position:0% you have this thing called a recording there's<00:01:26.869> a<00:01:26.990> copy<00:01:27.200> right<00:01:27.440> now<00:01:27.740> and<00:01:28.010> that 00:01:28.300 --> 00:01:28.310 align:start position:0% there's a copy right now and that 00:01:28.310 --> 00:01:29.800 align:start position:0% there's a copy right now and that copyright<00:01:28.610> is<00:01:28.820> normally<00:01:29.119> created<00:01:29.600> when<00:01:29.720> an 00:01:29.800 --> 00:01:29.810 align:start position:0% copyright is normally created when an 00:01:29.810 --> 00:01:32.530 align:start position:0% copyright is normally created when an artist<00:01:30.140> makes<00:01:30.500> a<00:01:30.680> recording<00:01:31.130> so<00:01:31.670> if<00:01:32.060> I<00:01:32.240> go<00:01:32.390> in<00:01:32.479> a 00:01:32.530 --> 00:01:32.540 align:start position:0% artist makes a recording so if I go in a 00:01:32.540 --> 00:01:34.330 align:start position:0% artist makes a recording so if I go in a street<00:01:32.689> and<00:01:32.780> I<00:01:32.930> record<00:01:33.200> something<00:01:33.380> I'm<00:01:33.740> now<00:01:34.040> I 00:01:34.330 --> 00:01:34.340 align:start position:0% street and I record something I'm now I 00:01:34.340 --> 00:01:35.950 align:start position:0% street and I record something I'm now I create<00:01:34.939> this<00:01:35.000> thing<00:01:35.180> called<00:01:35.240> a<00:01:35.450> recording<00:01:35.810> and 00:01:35.950 --> 00:01:35.960 align:start position:0% create this thing called a recording and 00:01:35.960 --> 00:01:38.440 align:start position:0% create this thing called a recording and that<00:01:35.990> is<00:01:36.110> not<00:01:36.260> only<00:01:36.320> owned<00:01:36.530> by<00:01:36.740> a<00:01:36.770> label<00:01:37.450> labels 00:01:38.440 --> 00:01:38.450 align:start position:0% that is not only owned by a label labels 00:01:38.450 --> 00:01:40.000 align:start position:0% that is not only owned by a label labels aren't<00:01:38.570> recordings<00:01:38.990> and<00:01:39.380> in<00:01:39.530> compositions 00:01:40.000 --> 00:01:40.010 align:start position:0% aren't recordings and in compositions 00:01:40.010 --> 00:01:41.620 align:start position:0% aren't recordings and in compositions you<00:01:40.159> can<00:01:40.250> think<00:01:40.369> about<00:01:40.430> recordings<00:01:41.330> being<00:01:41.510> the 00:01:41.620 --> 00:01:41.630 align:start position:0% you can think about recordings being the 00:01:41.630 --> 00:01:43.990 align:start position:0% you can think about recordings being the implementation<00:01:42.590> of<00:01:42.830> a<00:01:42.920> composition<00:01:43.220> so<00:01:43.760> a 00:01:43.990 --> 00:01:44.000 align:start position:0% implementation of a composition so a 00:01:44.000 --> 00:01:45.940 align:start position:0% implementation of a composition so a composition<00:01:44.570> or<00:01:44.780> as<00:01:45.020> according<00:01:45.350> the<00:01:45.560> us<00:01:45.770> of 00:01:45.940 --> 00:01:45.950 align:start position:0% composition or as according the us of 00:01:45.950 --> 00:01:48.039 align:start position:0% composition or as according the us of work<00:01:46.159> is<00:01:46.460> really<00:01:47.030> just<00:01:47.210> the<00:01:47.360> the<00:01:47.600> nuts<00:01:47.840> and 00:01:48.039 --> 00:01:48.049 align:start position:0% work is really just the the nuts and 00:01:48.049 --> 00:01:49.990 align:start position:0% work is really just the the nuts and bolts<00:01:48.290> the<00:01:48.320> mechanics<00:01:48.860> of<00:01:49.009> how<00:01:49.070> this<00:01:49.640> song<00:01:49.880> was 00:01:49.990 --> 00:01:50.000 align:start position:0% bolts the mechanics of how this song was 00:01:50.000 --> 00:01:51.940 align:start position:0% bolts the mechanics of how this song was made<00:01:50.150> the<00:01:50.330> lyrics<00:01:50.720> the<00:01:50.990> melodies<00:01:51.470> and<00:01:51.680> so<00:01:51.830> on 00:01:51.940 --> 00:01:51.950 align:start position:0% made the lyrics the melodies and so on 00:01:51.950 --> 00:01:53.800 align:start position:0% made the lyrics the melodies and so on and<00:01:52.369> that's<00:01:52.460> made<00:01:52.729> by<00:01:52.880> writers<00:01:53.270> so<00:01:53.450> producers 00:01:53.800 --> 00:01:53.810 align:start position:0% and that's made by writers so producers 00:01:53.810 --> 00:01:55.719 align:start position:0% and that's made by writers so producers you<00:01:54.140> make<00:01:54.259> the<00:01:54.380> instrumentals<00:01:54.920> or<00:01:55.460> obviously 00:01:55.719 --> 00:01:55.729 align:start position:0% you make the instrumentals or obviously 00:01:55.729 --> 00:01:56.920 align:start position:0% you make the instrumentals or obviously the<00:01:55.790> people<00:01:56.030> who<00:01:56.090> just<00:01:56.210> write<00:01:56.360> the<00:01:56.479> lyrics<00:01:56.570> and 00:01:56.920 --> 00:01:56.930 align:start position:0% the people who just write the lyrics and 00:01:56.930 --> 00:01:58.719 align:start position:0% the people who just write the lyrics and that's<00:01:57.500> normally<00:01:57.799> owned<00:01:57.979> or<00:01:58.189> represented<00:01:58.640> by 00:01:58.719 --> 00:01:58.729 align:start position:0% that's normally owned or represented by 00:01:58.729 --> 00:02:00.640 align:start position:0% that's normally owned or represented by publishers<00:01:59.210> and<00:01:59.869> every<00:02:00.110> single<00:02:00.380> time<00:02:00.500> when 00:02:00.640 --> 00:02:00.650 align:start position:0% publishers and every single time when 00:02:00.650 --> 00:02:02.590 align:start position:0% publishers and every single time when you<00:02:00.770> publish<00:02:01.520> our<00:02:01.700> writer<00:02:02.000> comes<00:02:02.329> into<00:02:02.570> a 00:02:02.590 --> 00:02:02.600 align:start position:0% you publish our writer comes into a 00:02:02.600 --> 00:02:04.120 align:start position:0% you publish our writer comes into a tracks<00:02:02.840> you<00:02:02.960> can<00:02:03.049> have<00:02:03.140> five<00:02:03.439> producers<00:02:03.740> ten 00:02:04.120 --> 00:02:04.130 align:start position:0% tracks you can have five producers ten 00:02:04.130 --> 00:02:06.249 align:start position:0% tracks you can have five producers ten producers<00:02:04.610> five<00:02:04.909> samples<00:02:05.570> all<00:02:05.990> of<00:02:06.170> those 00:02:06.249 --> 00:02:06.259 align:start position:0% producers five samples all of those 00:02:06.259 --> 00:02:07.420 align:start position:0% producers five samples all of those things<00:02:06.530> have<00:02:06.710> their<00:02:06.860> own<00:02:07.009> ownership 00:02:07.420 --> 00:02:07.430 align:start position:0% things have their own ownership 00:02:07.430 --> 00:02:09.249 align:start position:0% things have their own ownership structure<00:02:07.820> these<00:02:08.329> are<00:02:08.450> like<00:02:08.689> micro 00:02:09.249 --> 00:02:09.259 align:start position:0% structure these are like micro 00:02:09.259 --> 00:02:10.870 align:start position:0% structure these are like micro businesses<00:02:09.679> everything<00:02:10.250> one<00:02:10.369> of<00:02:10.399> these<00:02:10.580> are 00:02:10.870 --> 00:02:10.880 align:start position:0% businesses everything one of these are 00:02:10.880 --> 00:02:14.559 align:start position:0% businesses everything one of these are there<00:02:11.330> they're<00:02:11.599> argued<00:02:12.500> in<00:02:12.650> in<00:02:12.950> in<00:02:13.520> by<00:02:14.360> lawyers 00:02:14.559 --> 00:02:14.569 align:start position:0% there they're argued in in in by lawyers 00:02:14.569 --> 00:02:15.370 align:start position:0% there they're argued in in in by lawyers and<00:02:14.989> figured<00:02:15.260> out 00:02:15.370 --> 00:02:15.380 align:start position:0% and figured out 00:02:15.380 --> 00:02:16.900 align:start position:0% and figured out my<00:02:15.440> managers<00:02:15.830> and<00:02:15.950> accountants<00:02:16.340> to<00:02:16.670> try<00:02:16.820> and 00:02:16.900 --> 00:02:16.910 align:start position:0% my managers and accountants to try and 00:02:16.910 --> 00:02:18.640 align:start position:0% my managers and accountants to try and create<00:02:17.030> this<00:02:17.150> structure<00:02:17.390> and<00:02:17.720> nobody<00:02:18.380> has<00:02:18.620> a 00:02:18.640 --> 00:02:18.650 align:start position:0% create this structure and nobody has a 00:02:18.650 --> 00:02:20.560 align:start position:0% create this structure and nobody has a real<00:02:18.920> picture<00:02:19.310> how<00:02:19.700> this<00:02:19.730> works<00:02:20.090> now<00:02:20.330> this<00:02:20.450> is 00:02:20.560 --> 00:02:20.570 align:start position:0% real picture how this works now this is 00:02:20.570 --> 00:02:23.620 align:start position:0% real picture how this works now this is one<00:02:20.810> song<00:02:21.460> on<00:02:22.460> Spotify<00:02:22.730> there<00:02:23.090> are<00:02:23.150> over<00:02:23.330> 30 00:02:23.620 --> 00:02:23.630 align:start position:0% one song on Spotify there are over 30 00:02:23.630 --> 00:02:26.650 align:start position:0% one song on Spotify there are over 30 over<00:02:24.440> 30<00:02:24.650> million<00:02:24.920> songs<00:02:25.360> so<00:02:26.360> you<00:02:26.420> can<00:02:26.540> imagine 00:02:26.650 --> 00:02:26.660 align:start position:0% over 30 million songs so you can imagine 00:02:26.660 --> 00:02:28.840 align:start position:0% over 30 million songs so you can imagine how<00:02:26.900> complex<00:02:27.200> that<00:02:27.410> is<00:02:27.530> to<00:02:27.920> try<00:02:28.130> and<00:02:28.190> keep 00:02:28.840 --> 00:02:28.850 align:start position:0% how complex that is to try and keep 00:02:28.850 --> 00:02:30.670 align:start position:0% how complex that is to try and keep track<00:02:29.090> of<00:02:29.150> and<00:02:29.660> the<00:02:29.900> way<00:02:30.110> we<00:02:30.290> keep<00:02:30.470> track<00:02:30.620> of 00:02:30.670 --> 00:02:30.680 align:start position:0% track of and the way we keep track of 00:02:30.680 --> 00:02:32.350 align:start position:0% track of and the way we keep track of that<00:02:30.860> is<00:02:31.040> with<00:02:31.250> proprietary<00:02:31.700> databases 00:02:32.350 --> 00:02:32.360 align:start position:0% that is with proprietary databases 00:02:32.360 --> 00:02:35.980 align:start position:0% that is with proprietary databases now<00:02:33.320> this<00:02:33.830> tries<00:02:34.250> to<00:02:34.430> explain<00:02:34.730> how<00:02:34.940> when<00:02:35.900> we 00:02:35.980 --> 00:02:35.990 align:start position:0% now this tries to explain how when we 00:02:35.990 --> 00:02:38.050 align:start position:0% now this tries to explain how when we think<00:02:36.080> about<00:02:36.200> how<00:02:36.410> music<00:02:36.560> goes<00:02:36.980> from<00:02:37.340> people 00:02:38.050 --> 00:02:38.060 align:start position:0% think about how music goes from people 00:02:38.060 --> 00:02:39.310 align:start position:0% think about how music goes from people in<00:02:38.150> a<00:02:38.210> shoe<00:02:38.330> you're<00:02:38.450> crazy<00:02:38.690> all<00:02:39.110> the<00:02:39.230> way 00:02:39.310 --> 00:02:39.320 align:start position:0% in a shoe you're crazy all the way 00:02:39.320 --> 00:02:41.650 align:start position:0% in a shoe you're crazy all the way through<00:02:39.650> to<00:02:39.800> a<00:02:40.090> consumer<00:02:41.090> listening<00:02:41.450> to<00:02:41.570> on 00:02:41.650 --> 00:02:41.660 align:start position:0% through to a consumer listening to on 00:02:41.660 --> 00:02:42.910 align:start position:0% through to a consumer listening to on the<00:02:41.750> other<00:02:41.810> side<00:02:42.080> it's<00:02:42.530> actually<00:02:42.620> quite 00:02:42.910 --> 00:02:42.920 align:start position:0% the other side it's actually quite 00:02:42.920 --> 00:02:44.560 align:start position:0% the other side it's actually quite complex<00:02:43.250> because<00:02:43.520> the<00:02:43.700> song<00:02:44.000> itself<00:02:44.360> is<00:02:44.540> a 00:02:44.560 --> 00:02:44.570 align:start position:0% complex because the song itself is a 00:02:44.570 --> 00:02:45.400 align:start position:0% complex because the song itself is a collaboration 00:02:45.400 --> 00:02:45.410 align:start position:0% collaboration 00:02:45.410 --> 00:02:47.260 align:start position:0% collaboration it's<00:02:45.740> then<00:02:45.950> pushed<00:02:46.280> in<00:02:46.400> the<00:02:46.490> metadata<00:02:46.910> and<00:02:47.180> the 00:02:47.260 --> 00:02:47.270 align:start position:0% it's then pushed in the metadata and the 00:02:47.270 --> 00:02:48.910 align:start position:0% it's then pushed in the metadata and the music<00:02:47.660> becomes<00:02:47.900> separate<00:02:48.350> as<00:02:48.500> they<00:02:48.770> always 00:02:48.910 --> 00:02:48.920 align:start position:0% music becomes separate as they always 00:02:48.920 --> 00:02:50.620 align:start position:0% music becomes separate as they always are<00:02:49.130> and<00:02:49.310> then<00:02:49.820> they<00:02:49.910> move<00:02:50.120> down<00:02:50.270> the<00:02:50.330> supply 00:02:50.620 --> 00:02:50.630 align:start position:0% are and then they move down the supply 00:02:50.630 --> 00:02:52.300 align:start position:0% are and then they move down the supply chain<00:02:50.660> in<00:02:50.930> different<00:02:51.170> ways<00:02:51.320> now<00:02:51.980> on<00:02:52.070> the<00:02:52.160> work 00:02:52.300 --> 00:02:52.310 align:start position:0% chain in different ways now on the work 00:02:52.310 --> 00:02:54.100 align:start position:0% chain in different ways now on the work side<00:02:52.580> there<00:02:52.820> is<00:02:52.850> a<00:02:52.970> standard<00:02:53.600> identifier 00:02:54.100 --> 00:02:54.110 align:start position:0% side there is a standard identifier 00:02:54.110 --> 00:02:55.270 align:start position:0% side there is a standard identifier called<00:02:54.260> a<00:02:54.380> nice<00:02:54.500> that<00:02:54.710> we<00:02:54.800> see<00:02:54.980> it<00:02:55.100> on<00:02:55.190> the 00:02:55.270 --> 00:02:55.280 align:start position:0% called a nice that we see it on the 00:02:55.280 --> 00:02:56.590 align:start position:0% called a nice that we see it on the recording<00:02:55.580> side<00:02:55.760> a<00:02:55.820> standard<00:02:56.180> identify 00:02:56.590 --> 00:02:56.600 align:start position:0% recording side a standard identify 00:02:56.600 --> 00:02:59.020 align:start position:0% recording side a standard identify clitoris<00:02:57.050> is<00:02:57.440> our<00:02:57.620> see<00:02:57.800> people<00:02:58.580> like<00:02:58.670> to<00:02:58.790> apply 00:02:59.020 --> 00:02:59.030 align:start position:0% clitoris is our see people like to apply 00:02:59.030 --> 00:03:00.100 align:start position:0% clitoris is our see people like to apply these<00:02:59.090> things<00:02:59.300> willy-nilly<00:02:59.600> they<00:02:59.930> just 00:03:00.100 --> 00:03:00.110 align:start position:0% these things willy-nilly they just 00:03:00.110 --> 00:03:02.080 align:start position:0% these things willy-nilly they just applied<00:03:00.410> all<00:03:00.560> over<00:03:00.650> the<00:03:00.830> place<00:03:01.040> and<00:03:01.520> it<00:03:01.640> really 00:03:02.080 --> 00:03:02.090 align:start position:0% applied all over the place and it really 00:03:02.090 --> 00:03:03.970 align:start position:0% applied all over the place and it really mapped<00:03:02.480> down<00:03:02.690> to<00:03:02.840> the<00:03:02.930> actual<00:03:03.320> unit<00:03:03.860> we're 00:03:03.970 --> 00:03:03.980 align:start position:0% mapped down to the actual unit we're 00:03:03.980 --> 00:03:06.220 align:start position:0% mapped down to the actual unit we're trying<00:03:04.190> to<00:03:04.280> describe<00:03:04.610> and<00:03:04.910> as<00:03:05.480> we<00:03:05.840> want<00:03:06.080> to 00:03:06.220 --> 00:03:06.230 align:start position:0% trying to describe and as we want to 00:03:06.230 --> 00:03:07.900 align:start position:0% trying to describe and as we want to keep<00:03:06.500> sync<00:03:06.860> between<00:03:06.980> these<00:03:07.250> databases<00:03:07.640> we 00:03:07.900 --> 00:03:07.910 align:start position:0% keep sync between these databases we 00:03:07.910 --> 00:03:09.610 align:start position:0% keep sync between these databases we create<00:03:08.240> these<00:03:08.360> exports<00:03:08.990> and<00:03:09.080> we<00:03:09.200> just<00:03:09.350> send 00:03:09.610 --> 00:03:09.620 align:start position:0% create these exports and we just send 00:03:09.620 --> 00:03:11.320 align:start position:0% create these exports and we just send them<00:03:09.680> around<00:03:09.920> so<00:03:10.160> this<00:03:10.280> is<00:03:10.430> flat<00:03:10.730> files<00:03:10.970> flying 00:03:11.320 --> 00:03:11.330 align:start position:0% them around so this is flat files flying 00:03:11.330 --> 00:03:13.030 align:start position:0% them around so this is flat files flying all<00:03:11.480> around<00:03:11.510> the<00:03:11.780> industry<00:03:11.990> and<00:03:12.350> this<00:03:12.770> is<00:03:12.920> what 00:03:13.030 --> 00:03:13.040 align:start position:0% all around the industry and this is what 00:03:13.040 --> 00:03:16.660 align:start position:0% all around the industry and this is what we're<00:03:13.160> kind<00:03:13.430> of<00:03:13.520> using<00:03:13.790> to<00:03:14.180> sync<00:03:14.510> right<00:03:15.670> we're 00:03:16.660 --> 00:03:16.670 align:start position:0% we're kind of using to sync right we're 00:03:16.670 --> 00:03:21.670 align:start position:0% we're kind of using to sync right we're just<00:03:16.790> using<00:03:16.940> these<00:03:17.180> flat<00:03:17.450> files<00:03:17.920> now<00:03:20.020> as<00:03:21.020> we 00:03:21.670 --> 00:03:21.680 align:start position:0% just using these flat files now as we 00:03:21.680 --> 00:03:23.560 align:start position:0% just using these flat files now as we were<00:03:21.770> saying<00:03:21.920> before<00:03:22.040> the<00:03:22.940> problem<00:03:23.270> here<00:03:23.420> is 00:03:23.560 --> 00:03:23.570 align:start position:0% were saying before the problem here is 00:03:23.570 --> 00:03:25.150 align:start position:0% were saying before the problem here is that<00:03:23.600> we<00:03:23.840> end<00:03:23.960> up<00:03:24.050> with<00:03:24.110> complete<00:03:24.590> information 00:03:25.150 --> 00:03:25.160 align:start position:0% that we end up with complete information 00:03:25.160 --> 00:03:27.250 align:start position:0% that we end up with complete information asymmetry<00:03:25.700> one<00:03:26.300> person<00:03:26.690> saying<00:03:26.840> one<00:03:27.020> thing 00:03:27.250 --> 00:03:27.260 align:start position:0% asymmetry one person saying one thing 00:03:27.260 --> 00:03:28.360 align:start position:0% asymmetry one person saying one thing another<00:03:27.560> person<00:03:27.920> saying<00:03:28.040> another<00:03:28.250> thing 00:03:28.360 --> 00:03:28.370 align:start position:0% another person saying another thing 00:03:28.370 --> 00:03:29.980 align:start position:0% another person saying another thing anyway<00:03:29.090> to<00:03:29.150> keep<00:03:29.360> those<00:03:29.450> two<00:03:29.660> things<00:03:29.810> together 00:03:29.980 --> 00:03:29.990 align:start position:0% anyway to keep those two things together 00:03:29.990 --> 00:03:33.850 align:start position:0% anyway to keep those two things together is<00:03:30.430> to<00:03:31.430> send<00:03:31.970> this<00:03:32.090> flat<00:03:32.270> file<00:03:32.620> and<00:03:33.620> that<00:03:33.710> means 00:03:33.850 --> 00:03:33.860 align:start position:0% is to send this flat file and that means 00:03:33.860 --> 00:03:35.140 align:start position:0% is to send this flat file and that means this<00:03:33.920> fragmented<00:03:34.340> content<00:03:34.820> rights<00:03:34.970> across 00:03:35.140 --> 00:03:35.150 align:start position:0% this fragmented content rights across 00:03:35.150 --> 00:03:37.240 align:start position:0% this fragmented content rights across all<00:03:35.390> these<00:03:35.540> databases<00:03:35.990> and<00:03:36.710> that<00:03:36.950> means<00:03:37.100> that 00:03:37.240 --> 00:03:37.250 align:start position:0% all these databases and that means that 00:03:37.250 --> 00:03:39.160 align:start position:0% all these databases and that means that even<00:03:37.460> inside<00:03:37.880> one<00:03:38.180> organization<00:03:38.840> which<00:03:38.990> could 00:03:39.160 --> 00:03:39.170 align:start position:0% even inside one organization which could 00:03:39.170 --> 00:03:40.150 align:start position:0% even inside one organization which could be<00:03:39.260> global<00:03:39.440> and<00:03:39.680> owned<00:03:39.920> and<00:03:40.130> controlled 00:03:40.150 --> 00:03:40.160 align:start position:0% be global and owned and controlled 00:03:40.160 --> 00:03:41.890 align:start position:0% be global and owned and controlled different<00:03:40.730> things<00:03:41.030> and<00:03:41.180> assets<00:03:41.510> in<00:03:41.630> different 00:03:41.890 --> 00:03:41.900 align:start position:0% different things and assets in different 00:03:41.900 --> 00:03:43.690 align:start position:0% different things and assets in different territories<00:03:42.380> it's<00:03:42.770> quite<00:03:42.920> hard<00:03:43.070> to<00:03:43.100> keep<00:03:43.340> an 00:03:43.690 --> 00:03:43.700 align:start position:0% territories it's quite hard to keep an 00:03:43.700 --> 00:03:45.990 align:start position:0% territories it's quite hard to keep an internal<00:03:44.240> consensus<00:03:44.690> in<00:03:44.780> that<00:03:44.900> company<00:03:45.260> and 00:03:45.990 --> 00:03:46.000 align:start position:0% internal consensus in that company and 00:03:46.000 --> 00:03:48.010 align:start position:0% internal consensus in that company and really<00:03:47.000> the<00:03:47.120> only<00:03:47.150> way<00:03:47.300> the<00:03:47.450> music<00:03:47.690> industry 00:03:48.010 --> 00:03:48.020 align:start position:0% really the only way the music industry 00:03:48.020 --> 00:03:49.570 align:start position:0% really the only way the music industry has<00:03:48.140> known<00:03:48.530> how<00:03:48.650> to<00:03:48.680> solve<00:03:48.980> this<00:03:49.100> is<00:03:49.280> just<00:03:49.490> to 00:03:49.570 --> 00:03:49.580 align:start position:0% has known how to solve this is just to 00:03:49.580 --> 00:03:51.340 align:start position:0% has known how to solve this is just to create<00:03:49.880> a<00:03:50.000> new<00:03:50.270> database<00:03:50.420> so<00:03:50.930> we<00:03:51.020> end<00:03:51.140> up<00:03:51.230> with 00:03:51.340 --> 00:03:51.350 align:start position:0% create a new database so we end up with 00:03:51.350 --> 00:03:53.170 align:start position:0% create a new database so we end up with more<00:03:51.590> and<00:03:51.860> more<00:03:51.920> and<00:03:52.190> more<00:03:52.340> fragmentation<00:03:52.820> and 00:03:53.170 --> 00:03:53.180 align:start position:0% more and more and more fragmentation and 00:03:53.180 --> 00:03:54.880 align:start position:0% more and more and more fragmentation and really<00:03:53.959> we<00:03:54.080> ended<00:03:54.320> up<00:03:54.380> with<00:03:54.560> more<00:03:54.740> and<00:03:54.860> more 00:03:54.880 --> 00:03:54.890 align:start position:0% really we ended up with more and more 00:03:54.890 --> 00:03:56.620 align:start position:0% really we ended up with more and more databases<00:03:55.240> and<00:03:56.240> then<00:03:56.330> we<00:03:56.390> end<00:03:56.480> up<00:03:56.510> with 00:03:56.620 --> 00:03:56.630 align:start position:0% databases and then we end up with 00:03:56.630 --> 00:03:58.300 align:start position:0% databases and then we end up with parallel<00:03:56.959> data<00:03:57.110> reconciliation<00:03:57.830> so<00:03:58.040> again 00:03:58.300 --> 00:03:58.310 align:start position:0% parallel data reconciliation so again 00:03:58.310 --> 00:04:00.130 align:start position:0% parallel data reconciliation so again most<00:03:58.610> things<00:03:58.820> are<00:03:58.940> traveling<00:03:59.240> around<00:03:59.300> via<00:03:59.570> XML 00:04:00.130 --> 00:04:00.140 align:start position:0% most things are traveling around via XML 00:04:00.140 --> 00:04:01.900 align:start position:0% most things are traveling around via XML and<00:04:00.290> spreadsheets<00:04:00.920> and<00:04:01.280> getting<00:04:01.580> delivered 00:04:01.900 --> 00:04:01.910 align:start position:0% and spreadsheets and getting delivered 00:04:01.910 --> 00:04:05.230 align:start position:0% and spreadsheets and getting delivered to<00:04:02.000> FTPS<00:04:02.600> there's<00:04:03.590> not<00:04:04.070> very<00:04:04.100> many<00:04:04.670> API<00:04:05.120> is 00:04:05.230 --> 00:04:05.240 align:start position:0% to FTPS there's not very many API is 00:04:05.240 --> 00:04:05.710 align:start position:0% to FTPS there's not very many API is either 00:04:05.710 --> 00:04:05.720 align:start position:0% either 00:04:05.720 --> 00:04:07.810 align:start position:0% either so<00:04:05.810> actually<00:04:06.170> syncing<00:04:06.709> is<00:04:06.860> very<00:04:07.220> much<00:04:07.400> manual 00:04:07.810 --> 00:04:07.820 align:start position:0% so actually syncing is very much manual 00:04:07.820 --> 00:04:10.360 align:start position:0% so actually syncing is very much manual and<00:04:08.000> that's<00:04:08.450> problematic<00:04:08.870> because<00:04:09.290> we<00:04:10.250> are 00:04:10.360 --> 00:04:10.370 align:start position:0% and that's problematic because we are 00:04:10.370 --> 00:04:12.130 align:start position:0% and that's problematic because we are using<00:04:10.580> proprietary<00:04:10.880> databases<00:04:11.450> and<00:04:11.780> access 00:04:12.130 --> 00:04:12.140 align:start position:0% using proprietary databases and access 00:04:12.140 --> 00:04:13.720 align:start position:0% using proprietary databases and access is<00:04:12.320> ownership<00:04:12.800> if<00:04:12.920> I<00:04:12.980> want<00:04:13.130> to<00:04:13.190> tell<00:04:13.430> you<00:04:13.580> what 00:04:13.720 --> 00:04:13.730 align:start position:0% is ownership if I want to tell you what 00:04:13.730 --> 00:04:15.160 align:start position:0% is ownership if I want to tell you what I<00:04:13.850> own<00:04:13.970> I<00:04:14.000> have<00:04:14.120> to<00:04:14.240> give<00:04:14.450> you<00:04:14.570> the<00:04:14.690> data<00:04:14.840> so 00:04:15.160 --> 00:04:15.170 align:start position:0% I own I have to give you the data so 00:04:15.170 --> 00:04:16.990 align:start position:0% I own I have to give you the data so it's<00:04:15.290> quite<00:04:15.410> hard<00:04:15.650> to<00:04:15.770> build<00:04:15.920> out<00:04:16.160> kind<00:04:16.670> of<00:04:16.760> one 00:04:16.990 --> 00:04:17.000 align:start position:0% it's quite hard to build out kind of one 00:04:17.000 --> 00:04:19.180 align:start position:0% it's quite hard to build out kind of one single<00:04:17.299> database<00:04:17.660> however<00:04:18.440> one<00:04:18.980> day<00:04:19.100> the 00:04:19.180 --> 00:04:19.190 align:start position:0% single database however one day the 00:04:19.190 --> 00:04:20.560 align:start position:0% single database however one day the music<00:04:19.400> initially<00:04:19.489> did<00:04:19.850> try<00:04:20.030> to<00:04:20.090> do<00:04:20.270> that 00:04:20.560 --> 00:04:20.570 align:start position:0% music initially did try to do that 00:04:20.570 --> 00:04:22.840 align:start position:0% music initially did try to do that there<00:04:20.750> was<00:04:20.840> one<00:04:21.049> big<00:04:21.350> global<00:04:21.590> database<00:04:22.010> and<00:04:22.400> it 00:04:22.840 --> 00:04:22.850 align:start position:0% there was one big global database and it 00:04:22.850 --> 00:04:24.070 align:start position:0% there was one big global database and it didn't<00:04:23.090> really<00:04:23.180> work<00:04:23.270> for<00:04:23.450> reasons<00:04:23.900> we<00:04:23.960> won't 00:04:24.070 --> 00:04:24.080 align:start position:0% didn't really work for reasons we won't 00:04:24.080 --> 00:04:25.990 align:start position:0% didn't really work for reasons we won't go<00:04:24.140> into<00:04:24.260> but<00:04:24.740> centralized<00:04:25.460> governance<00:04:25.790> is 00:04:25.990 --> 00:04:26.000 align:start position:0% go into but centralized governance is 00:04:26.000 --> 00:04:28.450 align:start position:0% go into but centralized governance is problematic<00:04:26.720> if<00:04:27.290> I<00:04:27.380> have<00:04:27.560> ownership<00:04:28.160> I<00:04:28.280> have 00:04:28.450 --> 00:04:28.460 align:start position:0% problematic if I have ownership I have 00:04:28.460 --> 00:04:29.080 align:start position:0% problematic if I have ownership I have control 00:04:29.080 --> 00:04:29.090 align:start position:0% control 00:04:29.090 --> 00:04:30.990 align:start position:0% control and<00:04:29.690> really<00:04:29.870> that's<00:04:29.960> why<00:04:30.169> blockchains<00:04:30.740> are 00:04:30.990 --> 00:04:31.000 align:start position:0% and really that's why blockchains are 00:04:31.000 --> 00:04:33.070 align:start position:0% and really that's why blockchains are great<00:04:32.000> solution<00:04:32.360> to<00:04:32.389> this<00:04:32.480> problem<00:04:32.630> they<00:04:32.930> help 00:04:33.070 --> 00:04:33.080 align:start position:0% great solution to this problem they help 00:04:33.080 --> 00:04:34.540 align:start position:0% great solution to this problem they help us<00:04:33.200> avoid<00:04:33.620> it<00:04:33.770> we<00:04:33.919> have<00:04:34.040> a<00:04:34.070> network<00:04:34.340> of 00:04:34.540 --> 00:04:34.550 align:start position:0% us avoid it we have a network of 00:04:34.550 --> 00:04:36.700 align:start position:0% us avoid it we have a network of unbounded<00:04:35.330> parties<00:04:35.720> we<00:04:36.200> have<00:04:36.320> the<00:04:36.410> need<00:04:36.590> to 00:04:36.700 --> 00:04:36.710 align:start position:0% unbounded parties we have the need to 00:04:36.710 --> 00:04:38.350 align:start position:0% unbounded parties we have the need to collaboratively<00:04:37.280> maintain<00:04:37.820> a<00:04:37.850> single 00:04:38.350 --> 00:04:38.360 align:start position:0% collaboratively maintain a single 00:04:38.360 --> 00:04:40.300 align:start position:0% collaboratively maintain a single dataset<00:04:38.960> and<00:04:39.350> we<00:04:39.740> want<00:04:39.950> to<00:04:40.010> do<00:04:40.100> it<00:04:40.190> without 00:04:40.300 --> 00:04:40.310 align:start position:0% dataset and we want to do it without 00:04:40.310 --> 00:04:43.360 align:start position:0% dataset and we want to do it without putting<00:04:41.030> in<00:04:41.330> a<00:04:41.450> central<00:04:41.660> authority<00:04:42.220> this<00:04:43.220> is 00:04:43.360 --> 00:04:43.370 align:start position:0% putting in a central authority this is 00:04:43.370 --> 00:04:44.500 align:start position:0% putting in a central authority this is why<00:04:43.490> block<00:04:43.639> chains<00:04:43.850> are<00:04:43.940> great<00:04:44.090> fit 00:04:44.500 --> 00:04:44.510 align:start position:0% why block chains are great fit 00:04:44.510 --> 00:04:47.740 align:start position:0% why block chains are great fit so<00:04:45.580> what<00:04:46.580> Jack<00:04:46.790> what<00:04:46.940> we're<00:04:47.060> building<00:04:47.120> is<00:04:47.419> an 00:04:47.740 --> 00:04:47.750 align:start position:0% so what Jack what we're building is an 00:04:47.750 --> 00:04:49.659 align:start position:0% so what Jack what we're building is an open<00:04:48.110> data<00:04:48.290> network<00:04:48.680> and<00:04:49.220> we've<00:04:49.370> kind<00:04:49.610> of 00:04:49.659 --> 00:04:49.669 align:start position:0% open data network and we've kind of 00:04:49.669 --> 00:04:50.890 align:start position:0% open data network and we've kind of start<00:04:49.880> to<00:04:49.910> coalesce<00:04:50.120> around<00:04:50.330> inside<00:04:50.660> there<00:04:50.810> of 00:04:50.890 --> 00:04:50.900 align:start position:0% start to coalesce around inside there of 00:04:50.900 --> 00:04:52.810 align:start position:0% start to coalesce around inside there of a<00:04:50.960> single<00:04:51.350> source<00:04:51.590> of<00:04:51.710> truth<00:04:52.010> and<00:04:52.280> think<00:04:52.639> about 00:04:52.810 --> 00:04:52.820 align:start position:0% a single source of truth and think about 00:04:52.820 --> 00:04:54.520 align:start position:0% a single source of truth and think about block<00:04:53.030> chains<00:04:53.270> as<00:04:53.480> single<00:04:54.080> source<00:04:54.290> of<00:04:54.410> true 00:04:54.520 --> 00:04:54.530 align:start position:0% block chains as single source of true 00:04:54.530 --> 00:04:56.590 align:start position:0% block chains as single source of true systems<00:04:54.919> and<00:04:55.460> actually<00:04:55.700> thanks<00:04:56.090> to<00:04:56.180> incentive 00:04:56.590 --> 00:04:56.600 align:start position:0% systems and actually thanks to incentive 00:04:56.600 --> 00:04:57.850 align:start position:0% systems and actually thanks to incentive structures<00:04:56.960> block<00:04:57.139> chains<00:04:57.320> a<00:04:57.440> highly 00:04:57.850 --> 00:04:57.860 align:start position:0% structures block chains a highly 00:04:57.860 --> 00:04:59.500 align:start position:0% structures block chains a highly effective<00:04:58.220> single<00:04:58.760> single<00:04:59.060> source<00:04:59.270> of<00:04:59.330> true 00:04:59.500 --> 00:04:59.510 align:start position:0% effective single single source of true 00:04:59.510 --> 00:05:01.210 align:start position:0% effective single single source of true systems<00:04:59.870> and<00:05:00.139> a<00:05:00.410> great<00:05:00.590> our<00:05:00.800> highly<00:05:01.160> effective 00:05:01.210 --> 00:05:01.220 align:start position:0% systems and a great our highly effective 00:05:01.220 --> 00:05:03.909 align:start position:0% systems and a great our highly effective knowledge<00:05:01.639> production<00:05:02.060> systems<00:05:02.630> so<00:05:03.229> when<00:05:03.830> we 00:05:03.909 --> 00:05:03.919 align:start position:0% knowledge production systems so when we 00:05:03.919 --> 00:05:05.740 align:start position:0% knowledge production systems so when we think<00:05:04.040> about<00:05:04.130> single<00:05:04.520> source<00:05:04.669> of<00:05:04.790> truth<00:05:04.970> we 00:05:05.740 --> 00:05:05.750 align:start position:0% think about single source of truth we 00:05:05.750 --> 00:05:07.270 align:start position:0% think about single source of truth we try<00:05:06.410> to<00:05:06.470> think<00:05:06.620> about<00:05:06.800> it<00:05:06.889> in<00:05:06.979> the<00:05:07.040> way<00:05:07.130> that 00:05:07.270 --> 00:05:07.280 align:start position:0% try to think about it in the way that 00:05:07.280 --> 00:05:08.830 align:start position:0% try to think about it in the way that it's<00:05:07.400> always<00:05:07.610> been<00:05:07.940> defined<00:05:08.330> in<00:05:08.419> enterprise 00:05:08.830 --> 00:05:08.840 align:start position:0% it's always been defined in enterprise 00:05:08.840 --> 00:05:11.140 align:start position:0% it's always been defined in enterprise and<00:05:09.020> that<00:05:09.080> is<00:05:09.350> say<00:05:09.860> if<00:05:10.010> any<00:05:10.280> one<00:05:10.669> of<00:05:10.700> us<00:05:10.850> are 00:05:11.140 --> 00:05:11.150 align:start position:0% and that is say if any one of us are 00:05:11.150 --> 00:05:12.790 align:start position:0% and that is say if any one of us are working<00:05:11.389> with<00:05:11.690> an<00:05:11.780> enterprise<00:05:12.110> or<00:05:12.139> a<00:05:12.320> consumer 00:05:12.790 --> 00:05:12.800 align:start position:0% working with an enterprise or a consumer 00:05:12.800 --> 00:05:14.680 align:start position:0% working with an enterprise or a consumer we're<00:05:13.160> known<00:05:13.400> in<00:05:13.820> the<00:05:13.940> enterprise<00:05:14.300> to<00:05:14.360> one 00:05:14.680 --> 00:05:14.690 align:start position:0% we're known in the enterprise to one 00:05:14.690 --> 00:05:16.990 align:start position:0% we're known in the enterprise to one department<00:05:14.840> as<00:05:15.290> say<00:05:15.979> a<00:05:16.010> customer<00:05:16.310> and<00:05:16.760> a 00:05:16.990 --> 00:05:17.000 align:start position:0% department as say a customer and a 00:05:17.000 --> 00:05:18.430 align:start position:0% department as say a customer and a different<00:05:17.330> person<00:05:17.600> in<00:05:17.690> a<00:05:17.720> CRM<00:05:18.169> and<00:05:18.380> a 00:05:18.430 --> 00:05:18.440 align:start position:0% different person in a CRM and a 00:05:18.440 --> 00:05:20.190 align:start position:0% different person in a CRM and a different<00:05:18.740> person<00:05:18.979> to<00:05:19.040> cells<00:05:19.310> and<00:05:19.460> so<00:05:19.760> on<00:05:19.880> and 00:05:20.190 --> 00:05:20.200 align:start position:0% different person to cells and so on and 00:05:20.200 --> 00:05:22.180 align:start position:0% different person to cells and so on and enterprise<00:05:21.200> service<00:05:21.500> bus<00:05:21.530> is<00:05:21.830> helping<00:05:22.070> us<00:05:22.160> to 00:05:22.180 --> 00:05:22.190 align:start position:0% enterprise service bus is helping us to 00:05:22.190 --> 00:05:23.409 align:start position:0% enterprise service bus is helping us to try<00:05:22.400> to<00:05:22.460> create<00:05:22.760> a<00:05:22.820> single<00:05:23.060> source<00:05:23.300> of<00:05:23.360> truth 00:05:23.409 --> 00:05:23.419 align:start position:0% try to create a single source of truth 00:05:23.419 --> 00:05:25.120 align:start position:0% try to create a single source of truth about<00:05:23.600> who<00:05:23.810> that<00:05:23.900> customer<00:05:24.110> is<00:05:24.470> that's<00:05:25.010> what 00:05:25.120 --> 00:05:25.130 align:start position:0% about who that customer is that's what 00:05:25.130 --> 00:05:26.469 align:start position:0% about who that customer is that's what we<00:05:25.160> believe<00:05:25.280> block<00:05:25.669> chains<00:05:25.850> can<00:05:26.000> help<00:05:26.150> us<00:05:26.270> do 00:05:26.469 --> 00:05:26.479 align:start position:0% we believe block chains can help us do 00:05:26.479 --> 00:05:29.050 align:start position:0% we believe block chains can help us do around<00:05:27.080> rights<00:05:27.380> so<00:05:28.220> using<00:05:28.669> the<00:05:28.760> theorem 00:05:29.050 --> 00:05:29.060 align:start position:0% around rights so using the theorem 00:05:29.060 --> 00:05:31.030 align:start position:0% around rights so using the theorem ecosystem<00:05:29.630> and<00:05:29.780> web<00:05:30.260> the<00:05:30.410> infrastructure<00:05:30.919> we 00:05:31.030 --> 00:05:31.040 align:start position:0% ecosystem and web the infrastructure we 00:05:31.040 --> 00:05:32.800 align:start position:0% ecosystem and web the infrastructure we can<00:05:31.070> power<00:05:31.340> a<00:05:31.460> new<00:05:31.700> paradigm<00:05:32.120> for<00:05:32.150> content<00:05:32.690> on 00:05:32.800 --> 00:05:32.810 align:start position:0% can power a new paradigm for content on 00:05:32.810 --> 00:05:34.750 align:start position:0% can power a new paradigm for content on the<00:05:32.930> web<00:05:33.140> a<00:05:33.440> single<00:05:34.160> source<00:05:34.340> of<00:05:34.400> truth<00:05:34.460> for 00:05:34.750 --> 00:05:34.760 align:start position:0% the web a single source of truth for 00:05:34.760 --> 00:05:36.460 align:start position:0% the web a single source of truth for content<00:05:35.180> rights<00:05:35.360> built<00:05:35.690> on<00:05:35.750> top<00:05:35.840> of<00:05:35.900> an<00:05:36.110> open 00:05:36.460 --> 00:05:36.470 align:start position:0% content rights built on top of an open 00:05:36.470 --> 00:05:37.090 align:start position:0% content rights built on top of an open inclusive 00:05:37.090 --> 00:05:37.100 align:start position:0% inclusive 00:05:37.100 --> 00:05:40.830 align:start position:0% inclusive baiser<00:05:37.310> network<00:05:37.700> which<00:05:38.419> you<00:05:38.510> call<00:05:38.660> meta<00:05:38.840> now 00:05:40.830 --> 00:05:40.840 align:start position:0% baiser network which you call meta now 00:05:40.840 --> 00:05:42.940 align:start position:0% baiser network which you call meta now when<00:05:41.840> we<00:05:41.960> were<00:05:42.020> coming<00:05:42.260> up<00:05:42.320> with<00:05:42.380> this<00:05:42.560> we<00:05:42.800> ran 00:05:42.940 --> 00:05:42.950 align:start position:0% when we were coming up with this we ran 00:05:42.950 --> 00:05:44.560 align:start position:0% when we were coming up with this we ran into<00:05:43.070> a<00:05:43.160> few<00:05:43.190> problems<00:05:43.340> the<00:05:43.970> first<00:05:44.150> is<00:05:44.419> a 00:05:44.560 --> 00:05:44.570 align:start position:0% into a few problems the first is a 00:05:44.570 --> 00:05:47.050 align:start position:0% into a few problems the first is a single<00:05:45.560> source<00:05:45.680> of<00:05:45.890> truth<00:05:46.160> we<00:05:46.460> have<00:05:46.580> to<00:05:46.789> define 00:05:47.050 --> 00:05:47.060 align:start position:0% single source of truth we have to define 00:05:47.060 --> 00:05:50.080 align:start position:0% single source of truth we have to define truth<00:05:47.419> and<00:05:48.110> truth<00:05:48.289> is<00:05:48.620> pretty<00:05:49.430> subjective<00:05:49.729> in 00:05:50.080 --> 00:05:50.090 align:start position:0% truth and truth is pretty subjective in 00:05:50.090 --> 00:05:51.820 align:start position:0% truth and truth is pretty subjective in the<00:05:50.150> music<00:05:50.390> industry<00:05:50.510> because<00:05:51.050> data<00:05:51.320> changes 00:05:51.820 --> 00:05:51.830 align:start position:0% the music industry because data changes 00:05:51.830 --> 00:05:53.590 align:start position:0% the music industry because data changes all<00:05:51.979> the<00:05:52.160> time<00:05:52.400> and<00:05:52.820> no<00:05:53.030> one<00:05:53.060> actually<00:05:53.270> really 00:05:53.590 --> 00:05:53.600 align:start position:0% all the time and no one actually really 00:05:53.600 --> 00:05:55.870 align:start position:0% all the time and no one actually really knows<00:05:53.780> if<00:05:53.990> anyone<00:05:54.229> is<00:05:55.130> right<00:05:55.310> he<00:05:55.550> was<00:05:55.700> on<00:05:55.850> that 00:05:55.870 --> 00:05:55.880 align:start position:0% knows if anyone is right he was on that 00:05:55.880 --> 00:05:57.640 align:start position:0% knows if anyone is right he was on that song<00:05:56.180> I<00:05:56.390> wasn't<00:05:56.720> in<00:05:56.780> the<00:05:56.870> studio<00:05:57.169> how<00:05:57.470> do<00:05:57.530> I 00:05:57.640 --> 00:05:57.650 align:start position:0% song I wasn't in the studio how do I 00:05:57.650 --> 00:05:59.980 align:start position:0% song I wasn't in the studio how do I know<00:05:57.880> that<00:05:58.880> creates<00:05:59.150> a<00:05:59.210> problem<00:05:59.389> and<00:05:59.720> what 00:05:59.980 --> 00:05:59.990 align:start position:0% know that creates a problem and what 00:05:59.990 --> 00:06:01.420 align:start position:0% know that creates a problem and what we've<00:06:00.110> tried<00:06:00.139> to<00:06:00.410> do<00:06:00.590> is<00:06:00.710> kind<00:06:00.950> of<00:06:01.010> a<00:06:01.130> kind<00:06:01.310> of<00:06:01.340> a 00:06:01.420 --> 00:06:01.430 align:start position:0% we've tried to do is kind of a kind of a 00:06:01.430 --> 00:06:03.129 align:start position:0% we've tried to do is kind of a kind of a proxy<00:06:01.729> for<00:06:02.120> truth<00:06:02.360> and<00:06:02.539> what<00:06:02.630> we've<00:06:02.780> kind<00:06:03.110> of 00:06:03.129 --> 00:06:03.139 align:start position:0% proxy for truth and what we've kind of 00:06:03.139 --> 00:06:04.120 align:start position:0% proxy for truth and what we've kind of moved<00:06:03.320> to<00:06:03.500> his<00:06:03.590> authority 00:06:04.120 --> 00:06:04.130 align:start position:0% moved to his authority 00:06:04.130 --> 00:06:07.659 align:start position:0% moved to his authority so<00:06:04.930> Authority<00:06:05.930> requires<00:06:06.470> really<00:06:07.220> robust 00:06:07.659 --> 00:06:07.669 align:start position:0% so Authority requires really robust 00:06:07.669 --> 00:06:09.610 align:start position:0% so Authority requires really robust identity<00:06:08.210> structure<00:06:08.570> which<00:06:08.780> kind<00:06:09.380> of<00:06:09.410> led<00:06:09.590> us 00:06:09.610 --> 00:06:09.620 align:start position:0% identity structure which kind of led us 00:06:09.620 --> 00:06:10.930 align:start position:0% identity structure which kind of led us to<00:06:09.830> building<00:06:10.100> out<00:06:10.190> this<00:06:10.280> thing<00:06:10.430> we<00:06:10.580> call<00:06:10.700> meta 00:06:10.930 --> 00:06:10.940 align:start position:0% to building out this thing we call meta 00:06:10.940 --> 00:06:13.029 align:start position:0% to building out this thing we call meta ID<00:06:11.210> so<00:06:11.630> you'll<00:06:11.780> see<00:06:11.930> here<00:06:12.050> on<00:06:12.139> the<00:06:12.229> Left<00:06:12.410> we 00:06:13.029 --> 00:06:13.039 align:start position:0% ID so you'll see here on the Left we 00:06:13.039 --> 00:06:14.620 align:start position:0% ID so you'll see here on the Left we have<00:06:13.190> this<00:06:13.340> thing<00:06:13.490> called<00:06:13.550> meta<00:06:13.820> ID<00:06:14.000> and 00:06:14.620 --> 00:06:14.630 align:start position:0% have this thing called meta ID and 00:06:14.630 --> 00:06:17.110 align:start position:0% have this thing called meta ID and message<00:06:15.350> basically<00:06:15.560> an<00:06:15.770> open<00:06:16.070> beta<00:06:16.729> network 00:06:17.110 --> 00:06:17.120 align:start position:0% message basically an open beta network 00:06:17.120 --> 00:06:18.570 align:start position:0% message basically an open beta network that<00:06:17.539> can<00:06:17.690> be<00:06:17.780> used<00:06:18.020> to<00:06:18.139> build<00:06:18.260> decentralized 00:06:18.570 --> 00:06:18.580 align:start position:0% that can be used to build decentralized 00:06:18.580 --> 00:06:20.980 align:start position:0% that can be used to build decentralized databases<00:06:19.580> based<00:06:20.030> on<00:06:20.270> mass<00:06:20.419> IDs 00:06:20.980 --> 00:06:20.990 align:start position:0% databases based on mass IDs 00:06:20.990 --> 00:06:22.570 align:start position:0% databases based on mass IDs where<00:06:21.380> participants<00:06:21.800> are<00:06:21.979> incentivized<00:06:22.460> to 00:06:22.570 --> 00:06:22.580 align:start position:0% where participants are incentivized to 00:06:22.580 --> 00:06:24.129 align:start position:0% where participants are incentivized to provide<00:06:22.880> trustless<00:06:23.389> services<00:06:23.870> to<00:06:24.050> the 00:06:24.129 --> 00:06:24.139 align:start position:0% provide trustless services to the 00:06:24.139 --> 00:06:25.450 align:start position:0% provide trustless services to the network<00:06:24.260> such<00:06:25.100> that<00:06:25.250> they<00:06:25.310> can<00:06:25.430> be 00:06:25.450 --> 00:06:25.460 align:start position:0% network such that they can be 00:06:25.460 --> 00:06:27.940 align:start position:0% network such that they can be automatically<00:06:26.300> penalized<00:06:26.990> by<00:06:27.650> providing 00:06:27.940 --> 00:06:27.950 align:start position:0% automatically penalized by providing 00:06:27.950 --> 00:06:29.620 align:start position:0% automatically penalized by providing proof<00:06:28.220> to<00:06:28.340> a<00:06:28.400> small<00:06:28.639> contract<00:06:28.970> if<00:06:29.120> the<00:06:29.240> surface 00:06:29.620 --> 00:06:29.630 align:start position:0% proof to a small contract if the surface 00:06:29.630 --> 00:06:31.390 align:start position:0% proof to a small contract if the surface hasn't<00:06:30.020> been<00:06:30.139> provided<00:06:30.620> if<00:06:30.800> any<00:06:31.039> of<00:06:31.160> you<00:06:31.250> are 00:06:31.390 --> 00:06:31.400 align:start position:0% hasn't been provided if any of you are 00:06:31.400 --> 00:06:32.890 align:start position:0% hasn't been provided if any of you are in<00:06:31.490> the<00:06:31.610> swamp<00:06:32.000> talked<00:06:32.210> earlier<00:06:32.539> on<00:06:32.660> or<00:06:32.840> the 00:06:32.890 --> 00:06:32.900 align:start position:0% in the swamp talked earlier on or the 00:06:32.900 --> 00:06:34.540 align:start position:0% in the swamp talked earlier on or the one<00:06:33.020> earlier<00:06:33.200> in<00:06:33.590> a<00:06:33.680> week<00:06:33.800> you've<00:06:34.160> heard<00:06:34.370> week 00:06:34.540 --> 00:06:34.550 align:start position:0% one earlier in a week you've heard week 00:06:34.550 --> 00:06:36.340 align:start position:0% one earlier in a week you've heard week two<00:06:34.639> talking<00:06:34.880> about<00:06:35.030> sort<00:06:35.240> of<00:06:35.300> swindle<00:06:35.780> and<00:06:36.020> a 00:06:36.340 --> 00:06:36.350 align:start position:0% two talking about sort of swindle and a 00:06:36.350 --> 00:06:37.750 align:start position:0% two talking about sort of swindle and a service<00:06:36.889> layer<00:06:37.039> of<00:06:37.190> a<00:06:37.280> structure<00:06:37.580> that's 00:06:37.750 --> 00:06:37.760 align:start position:0% service layer of a structure that's 00:06:37.760 --> 00:06:39.040 align:start position:0% service layer of a structure that's exactly<00:06:38.180> what<00:06:38.300> we're<00:06:38.450> we're<00:06:38.630> implementing 00:06:39.040 --> 00:06:39.050 align:start position:0% exactly what we're we're implementing 00:06:39.050 --> 00:06:42.010 align:start position:0% exactly what we're we're implementing here<00:06:39.289> so<00:06:40.360> with<00:06:41.360> the<00:06:41.419> mess<00:06:41.510> hiding<00:06:41.810> the 00:06:42.010 --> 00:06:42.020 align:start position:0% here so with the mess hiding the 00:06:42.020 --> 00:06:42.959 align:start position:0% here so with the mess hiding the provider<00:06:42.260> can<00:06:42.409> convert 00:06:42.959 --> 00:06:42.969 align:start position:0% provider can convert 00:06:42.969 --> 00:06:45.239 align:start position:0% provider can convert face<00:06:43.119> into<00:06:44.049> metal<00:06:44.439> objects<00:06:44.829> and<00:06:44.889> push<00:06:45.099> them 00:06:45.239 --> 00:06:45.249 align:start position:0% face into metal objects and push them 00:06:45.249 --> 00:06:47.819 align:start position:0% face into metal objects and push them into<00:06:45.369> the<00:06:45.489> networkers<00:06:45.879> meta<00:06:46.059> streams<00:06:46.829> then 00:06:47.819 --> 00:06:47.829 align:start position:0% into the networkers meta streams then 00:06:47.829 --> 00:06:49.529 align:start position:0% into the networkers meta streams then anyone<00:06:48.189> can<00:06:48.309> provide<00:06:48.549> generic<00:06:48.939> indexing 00:06:49.529 --> 00:06:49.539 align:start position:0% anyone can provide generic indexing 00:06:49.539 --> 00:06:50.939 align:start position:0% anyone can provide generic indexing services<00:06:49.929> that's<00:06:50.199> what<00:06:50.319> the<00:06:50.379> validations<00:06:50.860> are 00:06:50.939 --> 00:06:50.949 align:start position:0% services that's what the validations are 00:06:50.949 --> 00:06:51.419 align:start position:0% services that's what the validations are doing<00:06:51.129> here 00:06:51.419 --> 00:06:51.429 align:start position:0% doing here 00:06:51.429 --> 00:06:53.069 align:start position:0% doing here they<00:06:51.610> basically<00:06:51.789> enter<00:06:52.479> into<00:06:52.629> a<00:06:52.719> service 00:06:53.069 --> 00:06:53.079 align:start position:0% they basically enter into a service 00:06:53.079 --> 00:06:55.379 align:start position:0% they basically enter into a service contract<00:06:53.229> with<00:06:53.949> a<00:06:53.979> smart<00:06:54.279> contract<00:06:54.610> and<00:06:54.849> they 00:06:55.379 --> 00:06:55.389 align:start position:0% contract with a smart contract and they 00:06:55.389 --> 00:06:56.759 align:start position:0% contract with a smart contract and they provide<00:06:55.689> service<00:06:55.959> in<00:06:56.019> the<00:06:56.110> network<00:06:56.349> and<00:06:56.529> using 00:06:56.759 --> 00:06:56.769 align:start position:0% provide service in the network and using 00:06:56.769 --> 00:06:58.559 align:start position:0% provide service in the network and using Merkel<00:06:57.099> proofs<00:06:57.339> a<00:06:57.459> node<00:06:57.610> can<00:06:57.759> just<00:06:57.999> check<00:06:58.239> that 00:06:58.559 --> 00:06:58.569 align:start position:0% Merkel proofs a node can just check that 00:06:58.569 --> 00:07:00.059 align:start position:0% Merkel proofs a node can just check that the<00:06:58.629> actual<00:06:58.989> information<00:06:59.259> they<00:06:59.589> provide<00:06:59.889> as<00:07:00.039> a 00:07:00.059 --> 00:07:00.069 align:start position:0% the actual information they provide as a 00:07:00.069 --> 00:07:01.999 align:start position:0% the actual information they provide as a meta<00:07:00.309> stream<00:07:00.549> is<00:07:00.699> included<00:07:01.239> in<00:07:01.360> that<00:07:01.389> index 00:07:01.999 --> 00:07:02.009 align:start position:0% meta stream is included in that index 00:07:02.009 --> 00:07:04.769 align:start position:0% meta stream is included in that index therefore<00:07:03.009> without<00:07:03.579> graphical<00:07:04.059> API<00:07:04.329> we<00:07:04.629> can 00:07:04.769 --> 00:07:04.779 align:start position:0% therefore without graphical API we can 00:07:04.779 --> 00:07:06.509 align:start position:0% therefore without graphical API we can basically<00:07:05.139> query<00:07:05.619> that<00:07:05.769> graph<00:07:06.039> of<00:07:06.189> objects 00:07:06.509 --> 00:07:06.519 align:start position:0% basically query that graph of objects 00:07:06.519 --> 00:07:10.259 align:start position:0% basically query that graph of objects and<00:07:06.759> serve<00:07:07.239> it<00:07:07.329> up<00:07:07.389> to<00:07:07.539> adapt<00:07:08.819> now<00:07:09.879> the 00:07:10.259 --> 00:07:10.269 align:start position:0% and serve it up to adapt now the 00:07:10.269 --> 00:07:11.759 align:start position:0% and serve it up to adapt now the interactions<00:07:10.749> between<00:07:10.779> contributors<00:07:11.439> to<00:07:11.649> the 00:07:11.759 --> 00:07:11.769 align:start position:0% interactions between contributors to the 00:07:11.769 --> 00:07:14.009 align:start position:0% interactions between contributors to the media<00:07:12.069> graph<00:07:12.309> DB<00:07:12.819> so<00:07:13.089> moving<00:07:13.749> ahead<00:07:13.809> a<00:07:13.899> bit 00:07:14.009 --> 00:07:14.019 align:start position:0% media graph DB so moving ahead a bit 00:07:14.019 --> 00:07:17.100 align:start position:0% media graph DB so moving ahead a bit quick<00:07:14.549> in<00:07:15.549> respect<00:07:15.909> to<00:07:15.969> music<00:07:16.659> media<00:07:16.869> rights 00:07:17.100 --> 00:07:17.110 align:start position:0% quick in respect to music media rights 00:07:17.110 --> 00:07:18.719 align:start position:0% quick in respect to music media rights information<00:07:17.349> we<00:07:18.129> can<00:07:18.279> use<00:07:18.459> the<00:07:18.610> method 00:07:18.719 --> 00:07:18.729 align:start position:0% information we can use the method 00:07:18.729 --> 00:07:20.219 align:start position:0% information we can use the method network<00:07:19.119> to<00:07:19.209> implement<00:07:19.539> a<00:07:19.569> decentralized 00:07:20.219 --> 00:07:20.229 align:start position:0% network to implement a decentralized 00:07:20.229 --> 00:07:22.469 align:start position:0% network to implement a decentralized database<00:07:20.679> which<00:07:21.009> has<00:07:21.219> a<00:07:21.249> defined<00:07:21.729> schema<00:07:22.269> and 00:07:22.469 --> 00:07:22.479 align:start position:0% database which has a defined schema and 00:07:22.479 --> 00:07:25.859 align:start position:0% database which has a defined schema and it's<00:07:23.019> maintained<00:07:23.499> by<00:07:23.679> validators<00:07:24.869> the 00:07:25.859 --> 00:07:25.869 align:start position:0% it's maintained by validators the 00:07:25.869 --> 00:07:28.889 align:start position:0% it's maintained by validators the integrity<00:07:26.289> of<00:07:26.409> this<00:07:26.769> specific<00:07:27.549> database<00:07:27.939> the 00:07:28.889 --> 00:07:28.899 align:start position:0% integrity of this specific database the 00:07:28.899 --> 00:07:30.539 align:start position:0% integrity of this specific database the interactions<00:07:29.289> between<00:07:29.319> contributors<00:07:30.129> to<00:07:30.309> the 00:07:30.539 --> 00:07:30.549 align:start position:0% interactions between contributors to the 00:07:30.549 --> 00:07:33.869 align:start position:0% interactions between contributors to the what<00:07:30.849> we<00:07:30.939> call<00:07:31.119> media<00:07:31.389> graph<00:07:31.799> DB<00:07:32.799> here<00:07:33.099> which 00:07:33.869 --> 00:07:33.879 align:start position:0% what we call media graph DB here which 00:07:33.879 --> 00:07:35.339 align:start position:0% what we call media graph DB here which is<00:07:33.999> basically<00:07:34.179> participial<00:07:34.809> to<00:07:34.899> insert<00:07:35.229> or 00:07:35.339 --> 00:07:35.349 align:start position:0% is basically participial to insert or 00:07:35.349 --> 00:07:37.529 align:start position:0% is basically participial to insert or update<00:07:35.379> data<00:07:35.799> into<00:07:36.309> this<00:07:36.429> database<00:07:36.729> and 00:07:37.529 --> 00:07:37.539 align:start position:0% update data into this database and 00:07:37.539 --> 00:07:39.179 align:start position:0% update data into this database and validators<00:07:38.169> is<00:07:38.349> governed<00:07:38.769> by<00:07:38.799> a<00:07:38.860> swaps 00:07:39.179 --> 00:07:39.189 align:start position:0% validators is governed by a swaps 00:07:39.189 --> 00:07:42.899 align:start position:0% validators is governed by a swaps western<00:07:39.579> game<00:07:41.099> rather<00:07:42.099> they<00:07:42.219> just<00:07:42.249> put<00:07:42.639> up<00:07:42.789> a 00:07:42.899 --> 00:07:42.909 align:start position:0% western game rather they just put up a 00:07:42.909 --> 00:07:45.209 align:start position:0% western game rather they just put up a stake<00:07:43.149> which<00:07:43.329> can<00:07:43.539> be<00:07:43.659> claimed<00:07:44.049> or<00:07:44.739> burnt<00:07:45.039> if 00:07:45.209 --> 00:07:45.219 align:start position:0% stake which can be claimed or burnt if 00:07:45.219 --> 00:07:47.249 align:start position:0% stake which can be claimed or burnt if they<00:07:45.399> fail<00:07:45.610> to<00:07:45.639> perform<00:07:45.879> their<00:07:46.179> duties<00:07:46.259> much 00:07:47.249 --> 00:07:47.259 align:start position:0% they fail to perform their duties much 00:07:47.259 --> 00:07:51.509 align:start position:0% they fail to perform their duties much like<00:07:47.439> proof<00:07:47.649> of<00:07:47.769> stake<00:07:48.899> now<00:07:50.219> what<00:07:51.219> that<00:07:51.339> allows 00:07:51.509 --> 00:07:51.519 align:start position:0% like proof of stake now what that allows 00:07:51.519 --> 00:07:53.639 align:start position:0% like proof of stake now what that allows us<00:07:51.550> to<00:07:51.699> do<00:07:51.909> is<00:07:52.179> build<00:07:52.419> out<00:07:52.569> this<00:07:52.659> object<00:07:53.139> which 00:07:53.639 --> 00:07:53.649 align:start position:0% us to do is build out this object which 00:07:53.649 --> 00:07:56.819 align:start position:0% us to do is build out this object which we<00:07:53.800> call<00:07:53.949> smart<00:07:54.189> content<00:07:54.959> using<00:07:55.959> message 00:07:56.819 --> 00:07:56.829 align:start position:0% we call smart content using message 00:07:56.829 --> 00:07:58.499 align:start position:0% we call smart content using message media<00:07:56.979> graph<00:07:57.279> we<00:07:57.489> basically<00:07:57.699> create<00:07:58.239> a<00:07:58.329> new 00:07:58.499 --> 00:07:58.509 align:start position:0% media graph we basically create a new 00:07:58.509 --> 00:08:00.119 align:start position:0% media graph we basically create a new index<00:07:58.809> which<00:07:59.019> is<00:07:59.139> called<00:07:59.349> smart<00:07:59.619> content<00:07:59.949> and 00:08:00.119 --> 00:08:00.129 align:start position:0% index which is called smart content and 00:08:00.129 --> 00:08:01.859 align:start position:0% index which is called smart content and the<00:08:00.219> validators<00:08:00.669> work<00:08:00.879> to<00:08:01.119> basically<00:08:01.629> make 00:08:01.859 --> 00:08:01.869 align:start position:0% the validators work to basically make 00:08:01.869 --> 00:08:02.969 align:start position:0% the validators work to basically make sure<00:08:01.899> that<00:08:02.139> everyone<00:08:02.379> conforms<00:08:02.860> to<00:08:02.919> that 00:08:02.969 --> 00:08:02.979 align:start position:0% sure that everyone conforms to that 00:08:02.979 --> 00:08:05.129 align:start position:0% sure that everyone conforms to that schema<00:08:03.459> and<00:08:03.639> it<00:08:04.179> extends<00:08:04.659> the<00:08:04.689> media<00:08:04.959> graph 00:08:05.129 --> 00:08:05.139 align:start position:0% schema and it extends the media graph 00:08:05.139 --> 00:08:07.529 align:start position:0% schema and it extends the media graph schema<00:08:05.469> to<00:08:05.589> include<00:08:05.860> assets<00:08:06.539> licenses 00:08:07.529 --> 00:08:07.539 align:start position:0% schema to include assets licenses 00:08:07.539 --> 00:08:09.869 align:start position:0% schema to include assets licenses metadata<00:08:08.409> and<00:08:08.739> anything<00:08:09.099> else<00:08:09.129> required<00:08:09.699> to 00:08:09.869 --> 00:08:09.879 align:start position:0% metadata and anything else required to 00:08:09.879 --> 00:08:11.429 align:start position:0% metadata and anything else required to facilitate<00:08:10.329> a<00:08:10.419> commercial<00:08:10.809> transaction<00:08:11.019> so 00:08:11.429 --> 00:08:11.439 align:start position:0% facilitate a commercial transaction so 00:08:11.439 --> 00:08:13.439 align:start position:0% facilitate a commercial transaction so you<00:08:11.529> can<00:08:11.649> see<00:08:11.829> here<00:08:12.039> we<00:08:12.489> have<00:08:12.519> our<00:08:12.819> graph<00:08:13.209> and 00:08:13.439 --> 00:08:13.449 align:start position:0% you can see here we have our graph and 00:08:13.449 --> 00:08:15.299 align:start position:0% you can see here we have our graph and basically<00:08:14.049> this<00:08:14.169> is<00:08:14.229> a<00:08:14.349> swarm<00:08:14.739> manifest<00:08:15.159> and 00:08:15.299 --> 00:08:15.309 align:start position:0% basically this is a swarm manifest and 00:08:15.309 --> 00:08:18.119 align:start position:0% basically this is a swarm manifest and it<00:08:15.369> has<00:08:15.519> a<00:08:15.759> kind<00:08:16.569> of<00:08:16.599> a<00:08:16.749> Content<00:08:17.679> address<00:08:17.860> link 00:08:18.119 --> 00:08:18.129 align:start position:0% it has a kind of a Content address link 00:08:18.129 --> 00:08:19.919 align:start position:0% it has a kind of a Content address link that<00:08:18.279> we<00:08:18.339> can<00:08:18.459> just<00:08:18.610> find<00:08:18.879> it<00:08:19.029> and<00:08:19.329> it<00:08:19.629> returns 00:08:19.919 --> 00:08:19.929 align:start position:0% that we can just find it and it returns 00:08:19.929 --> 00:08:22.079 align:start position:0% that we can just find it and it returns the<00:08:20.139> rice<00:08:20.349> information<00:08:20.919> the<00:08:21.159> type<00:08:21.429> of<00:08:21.459> right 00:08:22.079 --> 00:08:22.089 align:start position:0% the rice information the type of right 00:08:22.089 --> 00:08:23.999 align:start position:0% the rice information the type of right the<00:08:22.299> percentage<00:08:22.809> the<00:08:23.139> actual<00:08:23.409> owner<00:08:23.739> which<00:08:23.919> is 00:08:23.999 --> 00:08:24.009 align:start position:0% the percentage the actual owner which is 00:08:24.009 --> 00:08:25.679 align:start position:0% the percentage the actual owner which is a<00:08:24.039> Messer<00:08:24.369> ID<00:08:24.489> and<00:08:24.849> you'll<00:08:25.239> see<00:08:25.360> that<00:08:25.449> we<00:08:25.569> have 00:08:25.679 --> 00:08:25.689 align:start position:0% a Messer ID and you'll see that we have 00:08:25.689 --> 00:08:27.299 align:start position:0% a Messer ID and you'll see that we have these<00:08:25.839> checks<00:08:26.139> here<00:08:26.379> and<00:08:26.529> checks<00:08:26.739> basically 00:08:27.299 --> 00:08:27.309 align:start position:0% these checks here and checks basically 00:08:27.309 --> 00:08:29.309 align:start position:0% these checks here and checks basically just<00:08:27.549> to<00:08:27.639> show<00:08:27.879> us<00:08:27.999> that<00:08:28.179> the<00:08:28.809> person<00:08:29.049> who 00:08:29.309 --> 00:08:29.319 align:start position:0% just to show us that the person who 00:08:29.319 --> 00:08:31.169 align:start position:0% just to show us that the person who actually<00:08:29.439> owns<00:08:30.009> this<00:08:30.309> thing<00:08:30.489> has<00:08:30.699> signed<00:08:31.029> it 00:08:31.169 --> 00:08:31.179 align:start position:0% actually owns this thing has signed it 00:08:31.179 --> 00:08:33.089 align:start position:0% actually owns this thing has signed it or<00:08:31.329> some<00:08:31.719> delegate<00:08:32.139> thereof<00:08:32.439> and<00:08:32.979> that's 00:08:33.089 --> 00:08:33.099 align:start position:0% or some delegate thereof and that's 00:08:33.099 --> 00:08:34.589 align:start position:0% or some delegate thereof and that's really<00:08:33.339> what<00:08:33.490> the<00:08:33.579> indexes<00:08:34.059> or<00:08:34.180> validators 00:08:34.589 --> 00:08:34.599 align:start position:0% really what the indexes or validators 00:08:34.599 --> 00:08:36.569 align:start position:0% really what the indexes or validators Herat<00:08:34.930> do<00:08:35.469> working<00:08:35.860> to<00:08:35.949> maintain<00:08:36.099> to<00:08:36.430> make 00:08:36.569 --> 00:08:36.579 align:start position:0% Herat do working to maintain to make 00:08:36.579 --> 00:08:39.499 align:start position:0% Herat do working to maintain to make sure<00:08:36.669> that<00:08:36.759> this<00:08:36.879> thing<00:08:37.059> is<00:08:37.149> adhere<00:08:37.419> to<00:08:38.099> so 00:08:39.499 --> 00:08:39.509 align:start position:0% sure that this thing is adhere to so 00:08:39.509 --> 00:08:41.879 align:start position:0% sure that this thing is adhere to so this<00:08:40.509> structure<00:08:40.750> facilitates<00:08:40.959> trustless 00:08:41.879 --> 00:08:41.889 align:start position:0% this structure facilitates trustless 00:08:41.889 --> 00:08:43.649 align:start position:0% this structure facilitates trustless kickthrough<00:08:42.250> license<00:08:42.699> licensing<00:08:43.329> using 00:08:43.649 --> 00:08:43.659 align:start position:0% kickthrough license licensing using 00:08:43.659 --> 00:08:45.210 align:start position:0% kickthrough license licensing using small<00:08:43.930> contracts<00:08:44.290> and<00:08:44.470> service<00:08:44.860> guarantees 00:08:45.210 --> 00:08:45.220 align:start position:0% small contracts and service guarantees 00:08:45.220 --> 00:08:47.189 align:start position:0% small contracts and service guarantees using<00:08:46.029> swearin<00:08:46.300> Swindell<00:08:46.600> contracts<00:08:46.930> where 00:08:47.189 --> 00:08:47.199 align:start position:0% using swearin Swindell contracts where 00:08:47.199 --> 00:08:49.470 align:start position:0% using swearin Swindell contracts where we<00:08:47.259> get<00:08:47.379> usage<00:08:47.709> analytics<00:08:47.829> and<00:08:48.480> automated 00:08:49.470 --> 00:08:49.480 align:start position:0% we get usage analytics and automated 00:08:49.480 --> 00:08:54.210 align:start position:0% we get usage analytics and automated real-time<00:08:49.870> payments<00:08:50.350> for<00:08:51.009> free<00:08:52.529> so<00:08:53.529> what<00:08:54.100> are 00:08:54.210 --> 00:08:54.220 align:start position:0% real-time payments for free so what are 00:08:54.220 --> 00:08:56.429 align:start position:0% real-time payments for free so what are we<00:08:54.279> working<00:08:54.429> on<00:08:54.579> at<00:08:54.670> the<00:08:54.730> moment<00:08:54.850> a<00:08:55.240> few<00:08:56.199> things 00:08:56.429 --> 00:08:56.439 align:start position:0% we working on at the moment a few things 00:08:56.439 --> 00:08:57.030 align:start position:0% we working on at the moment a few things so 00:08:57.030 --> 00:08:57.040 align:start position:0% so 00:08:57.040 --> 00:08:59.130 align:start position:0% so if<00:08:57.190> you'd<00:08:57.340> heard<00:08:57.490> before<00:08:57.660> the<00:08:58.660> j-team<00:08:59.020> has 00:08:59.130 --> 00:08:59.140 align:start position:0% if you'd heard before the j-team has 00:08:59.140 --> 00:09:00.870 align:start position:0% if you'd heard before the j-team has been<00:08:59.260> contributing<00:08:59.770> quite<00:09:00.010> heavily<00:09:00.220> to<00:09:00.550> swarm 00:09:00.870 --> 00:09:00.880 align:start position:0% been contributing quite heavily to swarm 00:09:00.880 --> 00:09:04.140 align:start position:0% been contributing quite heavily to swarm and<00:09:01.290> we<00:09:02.290> started<00:09:02.560> off<00:09:02.620> by<00:09:02.680> working<00:09:02.920> on<00:09:03.190> PSS 00:09:04.140 --> 00:09:04.150 align:start position:0% and we started off by working on PSS 00:09:04.150 --> 00:09:06.570 align:start position:0% and we started off by working on PSS slide<00:09:04.840> earlier<00:09:05.110> in<00:09:05.200> the<00:09:05.290> year<00:09:05.470> PSS<00:09:06.220> being<00:09:06.460> a 00:09:06.570 --> 00:09:06.580 align:start position:0% slide earlier in the year PSS being a 00:09:06.580 --> 00:09:09.690 align:start position:0% slide earlier in the year PSS being a routing<00:09:06.970> protocol<00:09:07.890> which<00:09:08.890> again<00:09:09.100> is<00:09:09.340> being 00:09:09.690 --> 00:09:09.700 align:start position:0% routing protocol which again is being 00:09:09.700 --> 00:09:11.640 align:start position:0% routing protocol which again is being spoken<00:09:09.880> about<00:09:10.090> just<00:09:10.570> off<00:09:10.720> this<00:09:10.840> talk<00:09:11.110> in<00:09:11.350> the 00:09:11.640 --> 00:09:11.650 align:start position:0% spoken about just off this talk in the 00:09:11.650 --> 00:09:14.700 align:start position:0% spoken about just off this talk in the breakout<00:09:11.920> hall<00:09:12.100> and<00:09:12.310> PSS<00:09:13.150> is<00:09:13.630> a<00:09:13.900> routing 00:09:14.700 --> 00:09:14.710 align:start position:0% breakout hall and PSS is a routing 00:09:14.710 --> 00:09:15.960 align:start position:0% breakout hall and PSS is a routing protocol<00:09:15.040> so<00:09:15.220> meta<00:09:15.550> nodes<00:09:15.790> can<00:09:15.940> communicate 00:09:15.960 --> 00:09:15.970 align:start position:0% protocol so meta nodes can communicate 00:09:15.970 --> 00:09:17.700 align:start position:0% protocol so meta nodes can communicate to<00:09:16.480> each<00:09:16.540> other<00:09:16.750> and<00:09:16.900> broadcast<00:09:17.320> updates 00:09:17.700 --> 00:09:17.710 align:start position:0% to each other and broadcast updates 00:09:17.710 --> 00:09:20.310 align:start position:0% to each other and broadcast updates across<00:09:17.980> the<00:09:18.160> network<00:09:18.970> we<00:09:19.780> also<00:09:19.930> worked<00:09:20.170> on<00:09:20.290> a 00:09:20.310 --> 00:09:20.320 align:start position:0% across the network we also worked on a 00:09:20.320 --> 00:09:22.080 align:start position:0% across the network we also worked on a network<00:09:20.530> simulation<00:09:21.130> simulation<00:09:21.430> framework 00:09:22.080 --> 00:09:22.090 align:start position:0% network simulation simulation framework 00:09:22.090 --> 00:09:24.120 align:start position:0% network simulation simulation framework which<00:09:22.270> allows<00:09:22.300> you<00:09:22.690> to<00:09:22.840> view<00:09:23.650> the<00:09:23.710> nodes<00:09:24.040> that 00:09:24.120 --> 00:09:24.130 align:start position:0% which allows you to view the nodes that 00:09:24.130 --> 00:09:26.490 align:start position:0% which allows you to view the nodes that are<00:09:24.220> in<00:09:24.310> a<00:09:24.370> swarm<00:09:24.760> and<00:09:25.690> then<00:09:25.930> we've<00:09:26.050> also<00:09:26.230> begun 00:09:26.490 --> 00:09:26.500 align:start position:0% are in a swarm and then we've also begun 00:09:26.500 --> 00:09:29.150 align:start position:0% are in a swarm and then we've also begun work<00:09:26.740> on<00:09:26.890> pot<00:09:27.160> and<00:09:27.430> pot<00:09:27.610> is<00:09:27.700> basically<00:09:28.060> the 00:09:29.150 --> 00:09:29.160 align:start position:0% work on pot and pot is basically the 00:09:29.160 --> 00:09:31.050 align:start position:0% work on pot and pot is basically the infrastructure<00:09:30.160> or<00:09:30.400> technology<00:09:30.880> that<00:09:30.910> will 00:09:31.050 --> 00:09:31.060 align:start position:0% infrastructure or technology that will 00:09:31.060 --> 00:09:33.020 align:start position:0% infrastructure or technology that will be<00:09:31.150> behind<00:09:31.330> swarm<00:09:31.780> databases<00:09:32.350> or<00:09:32.470> swarm<00:09:32.710> DB 00:09:33.020 --> 00:09:33.030 align:start position:0% be behind swarm databases or swarm DB 00:09:33.030 --> 00:09:35.190 align:start position:0% be behind swarm databases or swarm DB and<00:09:34.030> we'll<00:09:34.240> be<00:09:34.330> working<00:09:34.570> on<00:09:34.600> that<00:09:34.750> alongside<00:09:35.020> a 00:09:35.190 --> 00:09:35.200 align:start position:0% and we'll be working on that alongside a 00:09:35.200 --> 00:09:36.180 align:start position:0% and we'll be working on that alongside a few<00:09:35.380> of<00:09:35.440> the<00:09:35.500> other<00:09:35.590> projects<00:09:35.920> who<00:09:36.040> are 00:09:36.180 --> 00:09:36.190 align:start position:0% few of the other projects who are 00:09:36.190 --> 00:09:38.130 align:start position:0% few of the other projects who are engaged<00:09:36.550> as<00:09:36.730> a<00:09:36.850> swarm<00:09:37.060> team<00:09:37.240> over<00:09:37.900> the<00:09:37.990> coming 00:09:38.130 --> 00:09:38.140 align:start position:0% engaged as a swarm team over the coming 00:09:38.140 --> 00:09:42.780 align:start position:0% engaged as a swarm team over the coming months<00:09:41.100> we've<00:09:42.100> also<00:09:42.250> been<00:09:42.460> working<00:09:42.580> on 00:09:42.780 --> 00:09:42.790 align:start position:0% months we've also been working on 00:09:42.790 --> 00:09:44.760 align:start position:0% months we've also been working on Phillippi<00:09:43.150> centralized<00:09:43.510> applications<00:09:44.050> what 00:09:44.760 --> 00:09:44.770 align:start position:0% Phillippi centralized applications what 00:09:44.770 --> 00:09:45.870 align:start position:0% Phillippi centralized applications what you're<00:09:44.890> seeing<00:09:45.070> here<00:09:45.130> is<00:09:45.310> an<00:09:45.520> application 00:09:45.870 --> 00:09:45.880 align:start position:0% you're seeing here is an application 00:09:45.880 --> 00:09:48.390 align:start position:0% you're seeing here is an application that<00:09:46.290> we<00:09:47.290> were<00:09:47.440> calling<00:09:47.650> Jack<00:09:47.950> for<00:09:48.160> reciting 00:09:48.390 --> 00:09:48.400 align:start position:0% that we were calling Jack for reciting 00:09:48.400 --> 00:09:49.800 align:start position:0% that we were calling Jack for reciting naat<00:09:48.640> it's<00:09:49.060> really<00:09:49.270> called<00:09:49.450> the<00:09:49.480> smart 00:09:49.800 --> 00:09:49.810 align:start position:0% naat it's really called the smart 00:09:49.810 --> 00:09:52.500 align:start position:0% naat it's really called the smart content<00:09:50.200> app<00:09:50.410> it's<00:09:50.710> basically<00:09:51.330> adapt<00:09:52.330> that 00:09:52.500 --> 00:09:52.510 align:start position:0% content app it's basically adapt that 00:09:52.510 --> 00:09:54.210 align:start position:0% content app it's basically adapt that allows<00:09:52.720> you<00:09:52.900> to<00:09:53.050> build<00:09:53.350> a<00:09:53.500> smart<00:09:53.740> content<00:09:54.070> and 00:09:54.210 --> 00:09:54.220 align:start position:0% allows you to build a smart content and 00:09:54.220 --> 00:09:56.760 align:start position:0% allows you to build a smart content and manage<00:09:54.340> it<00:09:54.610> so<00:09:55.180> theory<00:09:56.020> would<00:09:56.110> be<00:09:56.230> you<00:09:56.410> enter 00:09:56.760 --> 00:09:56.770 align:start position:0% manage it so theory would be you enter 00:09:56.770 --> 00:09:58.200 align:start position:0% manage it so theory would be you enter into<00:09:56.890> the<00:09:57.070> network<00:09:57.340> with<00:09:57.520> your<00:09:57.670> master<00:09:57.880> ID<00:09:58.090> and 00:09:58.200 --> 00:09:58.210 align:start position:0% into the network with your master ID and 00:09:58.210 --> 00:09:59.640 align:start position:0% into the network with your master ID and you're<00:09:58.300> able<00:09:58.540> to<00:09:58.570> load<00:09:59.020> up<00:09:59.230> any<00:09:59.350> of<00:09:59.440> the<00:09:59.530> assets 00:09:59.640 --> 00:09:59.650 align:start position:0% you're able to load up any of the assets 00:09:59.650 --> 00:10:01.350 align:start position:0% you're able to load up any of the assets you<00:09:59.890> actually<00:10:00.250> have<00:10:00.400> already<00:10:00.550> built<00:10:00.910> in<00:10:01.150> and 00:10:01.350 --> 00:10:01.360 align:start position:0% you actually have already built in and 00:10:01.360 --> 00:10:03.750 align:start position:0% you actually have already built in and then<00:10:02.170> you<00:10:02.290> can<00:10:02.440> customize<00:10:02.980> them<00:10:03.130> add<00:10:03.280> licenses 00:10:03.750 --> 00:10:03.760 align:start position:0% then you can customize them add licenses 00:10:03.760 --> 00:10:05.490 align:start position:0% then you can customize them add licenses at<00:10:03.910> assets<00:10:04.300> so<00:10:04.450> on<00:10:04.570> and<00:10:04.720> push<00:10:04.990> them<00:10:05.200> into<00:10:05.350> the 00:10:05.490 --> 00:10:05.500 align:start position:0% at assets so on and push them into the 00:10:05.500 --> 00:10:08.400 align:start position:0% at assets so on and push them into the jack<00:10:05.710> network<00:10:06.040> and<00:10:06.850> it<00:10:07.390> uses<00:10:07.810> pretty<00:10:08.290> much 00:10:08.400 --> 00:10:08.410 align:start position:0% jack network and it uses pretty much 00:10:08.410 --> 00:10:09.420 align:start position:0% jack network and it uses pretty much many<00:10:08.680> of<00:10:08.770> the<00:10:08.830> components<00:10:09.010> we've<00:10:09.280> really 00:10:09.420 --> 00:10:09.430 align:start position:0% many of the components we've really 00:10:09.430 --> 00:10:11.970 align:start position:0% many of the components we've really discussed<00:10:09.580> small<00:10:10.450> content<00:10:10.780> indexing<00:10:11.260> media 00:10:11.970 --> 00:10:11.980 align:start position:0% discussed small content indexing media 00:10:11.980 --> 00:10:15.000 align:start position:0% discussed small content indexing media graph<00:10:12.130> index<00:10:12.460> Messer<00:10:13.180> swarm<00:10:14.080> ENS<00:10:14.770> and 00:10:15.000 --> 00:10:15.010 align:start position:0% graph index Messer swarm ENS and 00:10:15.010 --> 00:10:17.490 align:start position:0% graph index Messer swarm ENS and aetherium<00:10:15.910> just<00:10:16.720> kind<00:10:16.870> of<00:10:16.900> trying<00:10:17.200> to<00:10:17.260> use<00:10:17.380> the 00:10:17.490 --> 00:10:17.500 align:start position:0% aetherium just kind of trying to use the 00:10:17.500 --> 00:10:23.460 align:start position:0% aetherium just kind of trying to use the entire<00:10:17.800> stack<00:10:20.400> so<00:10:21.400> Lisa's<00:10:22.270> first<00:10:23.230> thing<00:10:23.380> is 00:10:23.460 --> 00:10:23.470 align:start position:0% entire stack so Lisa's first thing is 00:10:23.470 --> 00:10:24.570 align:start position:0% entire stack so Lisa's first thing is the<00:10:23.530> Mentawai<00:10:23.800> paper<00:10:24.040> we've<00:10:24.220> been<00:10:24.310> working<00:10:24.490> on 00:10:24.570 --> 00:10:24.580 align:start position:0% the Mentawai paper we've been working on 00:10:24.580 --> 00:10:26.820 align:start position:0% the Mentawai paper we've been working on it<00:10:24.670> for<00:10:24.700> a<00:10:24.820> while<00:10:24.940> now<00:10:25.120> some<00:10:26.020> people<00:10:26.650> may<00:10:26.770> have 00:10:26.820 --> 00:10:26.830 align:start position:0% it for a while now some people may have 00:10:26.830 --> 00:10:28.170 align:start position:0% it for a while now some people may have really<00:10:27.010> seen<00:10:27.190> her<00:10:27.250> first<00:10:27.460> draft<00:10:27.610> already<00:10:27.940> and 00:10:28.170 --> 00:10:28.180 align:start position:0% really seen her first draft already and 00:10:28.180 --> 00:10:29.790 align:start position:0% really seen her first draft already and that<00:10:28.690> really<00:10:28.840> defines<00:10:29.230> the<00:10:29.380> structure<00:10:29.770> that 00:10:29.790 --> 00:10:29.800 align:start position:0% that really defines the structure that 00:10:29.800 --> 00:10:30.990 align:start position:0% that really defines the structure that we're<00:10:29.980> talking<00:10:30.040> about<00:10:30.220> here<00:10:30.520> in<00:10:30.610> terms<00:10:30.640> of<00:10:30.940> the 00:10:30.990 --> 00:10:31.000 align:start position:0% we're talking about here in terms of the 00:10:31.000 --> 00:10:32.460 align:start position:0% we're talking about here in terms of the service<00:10:31.300> level<00:10:31.540> agreements<00:10:31.930> between<00:10:32.050> nodes 00:10:32.460 --> 00:10:32.470 align:start position:0% service level agreements between nodes 00:10:32.470 --> 00:10:34.950 align:start position:0% service level agreements between nodes which<00:10:33.010> which<00:10:33.910> is<00:10:34.030> quite<00:10:34.240> powerful<00:10:34.420> because<00:10:34.810> it 00:10:34.950 --> 00:10:34.960 align:start position:0% which which is quite powerful because it 00:10:34.960 --> 00:10:36.450 align:start position:0% which which is quite powerful because it would<00:10:35.110> allow<00:10:35.200> things<00:10:35.470> like<00:10:35.620> licensing<00:10:36.310> where 00:10:36.450 --> 00:10:36.460 align:start position:0% would allow things like licensing where 00:10:36.460 --> 00:10:37.860 align:start position:0% would allow things like licensing where you<00:10:36.520> just<00:10:36.670> enter<00:10:36.940> into<00:10:37.090> a<00:10:37.180> contact<00:10:37.540> with<00:10:37.780> the 00:10:37.860 --> 00:10:37.870 align:start position:0% you just enter into a contact with the 00:10:37.870 --> 00:10:39.930 align:start position:0% you just enter into a contact with the license<00:10:38.260> and<00:10:38.500> can<00:10:38.800> provide<00:10:39.490> all<00:10:39.640> kinds<00:10:39.670> of 00:10:39.930 --> 00:10:39.940 align:start position:0% license and can provide all kinds of 00:10:39.940 --> 00:10:41.280 align:start position:0% license and can provide all kinds of services<00:10:40.120> including<00:10:40.450> the<00:10:40.720> actual<00:10:40.870> storage 00:10:41.280 --> 00:10:41.290 align:start position:0% services including the actual storage 00:10:41.290 --> 00:10:43.230 align:start position:0% services including the actual storage serving<00:10:42.040> up<00:10:42.160> the<00:10:42.280> streaming<00:10:42.730> of<00:10:42.820> the<00:10:42.910> assets 00:10:43.230 --> 00:10:43.240 align:start position:0% serving up the streaming of the assets 00:10:43.240 --> 00:10:44.940 align:start position:0% serving up the streaming of the assets again<00:10:43.540> I<00:10:43.750> use<00:10:44.050> a<00:10:44.080> little<00:10:44.290> live<00:10:44.380> peer<00:10:44.650> people 00:10:44.940 --> 00:10:44.950 align:start position:0% again I use a little live peer people 00:10:44.950 --> 00:10:46.350 align:start position:0% again I use a little live peer people talking<00:10:45.190> about<00:10:45.370> that<00:10:45.520> as<00:10:45.610> well 00:10:46.350 --> 00:10:46.360 align:start position:0% talking about that as well 00:10:46.360 --> 00:10:47.790 align:start position:0% talking about that as well and<00:10:46.660> this<00:10:46.810> kind<00:10:47.140> of<00:10:47.230> framework<00:10:47.410> really<00:10:47.770> I 00:10:47.790 --> 00:10:47.800 align:start position:0% and this kind of framework really I 00:10:47.800 --> 00:10:49.560 align:start position:0% and this kind of framework really I think<00:10:48.070> will<00:10:48.250> drive<00:10:48.520> out<00:10:48.670> all<00:10:48.700> the<00:10:49.030> next 00:10:49.560 --> 00:10:49.570 align:start position:0% think will drive out all the next 00:10:49.570 --> 00:10:51.360 align:start position:0% think will drive out all the next generation<00:10:49.960> of<00:10:50.080> that<00:10:50.200> development<00:10:50.620> the 00:10:51.360 --> 00:10:51.370 align:start position:0% generation of that development the 00:10:51.370 --> 00:10:53.160 align:start position:0% generation of that development the second<00:10:51.610> part<00:10:51.790> is<00:10:51.820> the<00:10:51.910> method<00:10:52.300> up<00:10:52.660> and<00:10:52.960> the 00:10:53.160 --> 00:10:53.170 align:start position:0% second part is the method up and the 00:10:53.170 --> 00:10:55.170 align:start position:0% second part is the method up and the metal<00:10:53.410> ID<00:10:53.530> really<00:10:54.070> allows<00:10:54.430> you<00:10:54.580> to<00:10:54.610> create<00:10:55.000> a 00:10:55.170 --> 00:10:55.180 align:start position:0% metal ID really allows you to create a 00:10:55.180 --> 00:10:56.850 align:start position:0% metal ID really allows you to create a public<00:10:55.420> address<00:10:55.690> and<00:10:56.020> then<00:10:56.110> connect<00:10:56.440> all 00:10:56.850 --> 00:10:56.860 align:start position:0% public address and then connect all 00:10:56.860 --> 00:10:58.710 align:start position:0% public address and then connect all these<00:10:57.040> other<00:10:57.220> authorized<00:10:57.790> providers<00:10:58.450> to<00:10:58.600> it 00:10:58.710 --> 00:10:58.720 align:start position:0% these other authorized providers to it 00:10:58.720 --> 00:10:59.430 align:start position:0% these other authorized providers to it so<00:10:58.900> you<00:10:58.990> can<00:10:59.110> imagine 00:10:59.430 --> 00:10:59.440 align:start position:0% so you can imagine 00:10:59.440 --> 00:11:01.230 align:start position:0% so you can imagine signing<00:11:00.130> up<00:11:00.250> as<00:11:00.370> an<00:11:00.460> artist<00:11:00.790> with<00:11:00.910> a<00:11:00.940> mess<00:11:01.120> or 00:11:01.230 --> 00:11:01.240 align:start position:0% signing up as an artist with a mess or 00:11:01.240 --> 00:11:02.790 align:start position:0% signing up as an artist with a mess or ID<00:11:01.330> and<00:11:01.570> then<00:11:01.660> being<00:11:01.810> able<00:11:01.900> to<00:11:02.020> connect<00:11:02.350> any<00:11:02.680> of 00:11:02.790 --> 00:11:02.800 align:start position:0% ID and then being able to connect any of 00:11:02.800 --> 00:11:04.110 align:start position:0% ID and then being able to connect any of the<00:11:02.890> other<00:11:03.040> trusty<00:11:03.400> providers<00:11:03.820> like<00:11:03.940> your 00:11:04.110 --> 00:11:04.120 align:start position:0% the other trusty providers like your 00:11:04.120 --> 00:11:06.450 align:start position:0% the other trusty providers like your label<00:11:04.480> or<00:11:04.660> your<00:11:04.750> publisher<00:11:05.260> or<00:11:05.470> you<00:11:05.830> know<00:11:05.920> your 00:11:06.450 --> 00:11:06.460 align:start position:0% label or your publisher or you know your 00:11:06.460 --> 00:11:07.860 align:start position:0% label or your publisher or you know your Instagram<00:11:06.940> anything<00:11:07.330> where<00:11:07.480> you<00:11:07.570> like<00:11:07.750> to 00:11:07.860 --> 00:11:07.870 align:start position:0% Instagram anything where you like to 00:11:07.870 --> 00:11:09.900 align:start position:0% Instagram anything where you like to dock<00:11:08.080> your<00:11:08.230> identity<00:11:08.710> and<00:11:08.950> then<00:11:09.670> the<00:11:09.760> meta 00:11:09.900 --> 00:11:09.910 align:start position:0% dock your identity and then the meta 00:11:09.910 --> 00:11:10.620 align:start position:0% dock your identity and then the meta test<00:11:10.180> net<00:11:10.360> which 00:11:10.620 --> 00:11:10.630 align:start position:0% test net which 00:11:10.630 --> 00:11:11.700 align:start position:0% test net which allow<00:11:10.840> you<00:11:10.900> to<00:11:11.050> start<00:11:11.260> building<00:11:11.440> these 00:11:11.700 --> 00:11:11.710 align:start position:0% allow you to start building these 00:11:11.710 --> 00:11:14.370 align:start position:0% allow you to start building these decentralized<00:11:12.370> databases<00:11:12.970> we<00:11:13.810> plan<00:11:14.140> to<00:11:14.260> push 00:11:14.370 --> 00:11:14.380 align:start position:0% decentralized databases we plan to push 00:11:14.380 --> 00:11:16.140 align:start position:0% decentralized databases we plan to push that<00:11:14.530> in<00:11:14.650> early<00:11:14.920> 18<00:11:15.340> so<00:11:15.670> you'll<00:11:15.820> actually<00:11:15.970> be 00:11:16.140 --> 00:11:16.150 align:start position:0% that in early 18 so you'll actually be 00:11:16.150 --> 00:11:20.070 align:start position:0% that in early 18 so you'll actually be able<00:11:16.210> to<00:11:16.360> try<00:11:16.540> this<00:11:16.600> stuff<00:11:16.750> out<00:11:16.990> a<00:11:18.990> final<00:11:19.990> hat 00:11:20.070 --> 00:11:20.080 align:start position:0% able to try this stuff out a final hat 00:11:20.080 --> 00:11:22.680 align:start position:0% able to try this stuff out a final hat tip<00:11:20.290> Tom<00:11:20.650> see<00:11:20.800> on<00:11:21.100> the<00:11:21.250> CEO<00:11:21.490> I'm<00:11:21.730> building 00:11:22.680 --> 00:11:22.690 align:start position:0% tip Tom see on the CEO I'm building 00:11:22.690 --> 00:11:23.850 align:start position:0% tip Tom see on the CEO I'm building other<00:11:22.810> stuff<00:11:23.020> so<00:11:23.140> I<00:11:23.200> once<00:11:23.320> wanted<00:11:23.440> to<00:11:23.620> let<00:11:23.770> you 00:11:23.850 --> 00:11:23.860 align:start position:0% other stuff so I once wanted to let you 00:11:23.860 --> 00:11:25.560 align:start position:0% other stuff so I once wanted to let you know<00:11:23.890> the<00:11:24.280> people<00:11:24.640> who<00:11:24.910> you<00:11:24.970> can<00:11:25.090> speak<00:11:25.330> to<00:11:25.450> if 00:11:25.560 --> 00:11:25.570 align:start position:0% know the people who you can speak to if 00:11:25.570 --> 00:11:27.080 align:start position:0% know the people who you can speak to if you're<00:11:25.690> interested<00:11:26.020> in<00:11:26.080> learning<00:11:26.380> a<00:11:26.560> bit<00:11:26.650> more 00:11:27.080 --> 00:11:27.090 align:start position:0% you're interested in learning a bit more 00:11:27.090 --> 00:11:29.580 align:start position:0% you're interested in learning a bit more fred<00:11:28.090> and<00:11:28.420> victor<00:11:28.690> obviously<00:11:28.960> my<00:11:29.080> co-founders 00:11:29.580 --> 00:11:29.590 align:start position:0% fred and victor obviously my co-founders 00:11:29.590 --> 00:11:31.260 align:start position:0% fred and victor obviously my co-founders for<00:11:30.010> his<00:11:30.100> lead<00:11:30.250> application<00:11:30.730> engineer<00:11:31.090> on 00:11:31.260 --> 00:11:31.270 align:start position:0% for his lead application engineer on 00:11:31.270 --> 00:11:31.860 align:start position:0% for his lead application engineer on jack 00:11:31.860 --> 00:11:31.870 align:start position:0% jack 00:11:31.870 --> 00:11:34.080 align:start position:0% jack victor<00:11:32.470> obviously<00:11:32.770> the<00:11:32.950> architect<00:11:33.610> working 00:11:34.080 --> 00:11:34.090 align:start position:0% victor obviously the architect working 00:11:34.090 --> 00:11:36.420 align:start position:0% victor obviously the architect working on<00:11:34.180> Jack<00:11:34.390> and<00:11:34.570> Messer<00:11:34.830> who<00:11:35.830> is<00:11:35.950> Marshall<00:11:36.280> who's 00:11:36.420 --> 00:11:36.430 align:start position:0% on Jack and Messer who is Marshall who's 00:11:36.430 --> 00:11:38.490 align:start position:0% on Jack and Messer who is Marshall who's heading<00:11:36.760> up<00:11:36.880> Messer<00:11:37.270> he's<00:11:38.080> the<00:11:38.140> best<00:11:38.290> person 00:11:38.490 --> 00:11:38.500 align:start position:0% heading up Messer he's the best person 00:11:38.500 --> 00:11:39.570 align:start position:0% heading up Messer he's the best person to<00:11:38.530> speak<00:11:38.710> to<00:11:38.860> about<00:11:38.950> all<00:11:39.160> the<00:11:39.250> stuff<00:11:39.400> I<00:11:39.550> just 00:11:39.570 --> 00:11:39.580 align:start position:0% to speak to about all the stuff I just 00:11:39.580 --> 00:11:41.610 align:start position:0% to speak to about all the stuff I just described<00:11:40.120> and<00:11:40.300> Oren<00:11:40.870> as<00:11:40.960> well<00:11:41.140> he's<00:11:41.440> also 00:11:41.610 --> 00:11:41.620 align:start position:0% described and Oren as well he's also 00:11:41.620 --> 00:11:42.360 align:start position:0% described and Oren as well he's also working<00:11:41.890> on<00:11:42.040> Messer 00:11:42.360 --> 00:11:42.370 align:start position:0% working on Messer 00:11:42.370 --> 00:11:45.450 align:start position:0% working on Messer let<00:11:43.300> me<00:11:43.360> have<00:11:43.450> Lewis<00:11:43.690> who<00:11:44.050> sees<00:11:44.800> the<00:11:45.010> developer 00:11:45.450 --> 00:11:45.460 align:start position:0% let me have Lewis who sees the developer 00:11:45.460 --> 00:11:47.550 align:start position:0% let me have Lewis who sees the developer working<00:11:45.610> on<00:11:45.790> PSS<00:11:46.240> and<00:11:46.540> Luke<00:11:46.870> who's<00:11:47.170> who's 00:11:47.550 --> 00:11:47.560 align:start position:0% working on PSS and Luke who's who's 00:11:47.560 --> 00:11:49.560 align:start position:0% working on PSS and Luke who's who's heading<00:11:47.800> up<00:11:47.890> meta<00:11:48.100> ID<00:11:48.340> so<00:11:49.090> again<00:11:49.270> if<00:11:49.420> you<00:11:49.480> do 00:11:49.560 --> 00:11:49.570 align:start position:0% heading up meta ID so again if you do 00:11:49.570 --> 00:11:50.730 align:start position:0% heading up meta ID so again if you do have<00:11:49.600> any<00:11:49.810> questions<00:11:49.840> and<00:11:50.350> you<00:11:50.440> do<00:11:50.620> wanna 00:11:50.730 --> 00:11:50.740 align:start position:0% have any questions and you do wanna 00:11:50.740 --> 00:11:51.930 align:start position:0% have any questions and you do wanna reach<00:11:50.860> out<00:11:50.980> those<00:11:51.130> guys<00:11:51.250> please<00:11:51.550> you<00:11:51.670> just<00:11:51.850> go 00:11:51.930 --> 00:11:51.940 align:start position:0% reach out those guys please you just go 00:11:51.940 --> 00:11:55.830 align:start position:0% reach out those guys please you just go and<00:11:52.240> reach<00:11:52.540> out<00:11:52.690> to<00:11:52.750> them<00:11:52.900> and<00:11:54.390> you<00:11:55.390> can<00:11:55.540> find 00:11:55.830 --> 00:11:55.840 align:start position:0% and reach out to them and you can find 00:11:55.840 --> 00:11:59.310 align:start position:0% and reach out to them and you can find us<00:11:55.990> on<00:11:56.260> we<00:11:56.740> do<00:11:56.890> have<00:11:56.920> a<00:11:57.250> github<00:11:57.790> github.com<00:11:58.720> / 00:11:59.310 --> 00:11:59.320 align:start position:0% us on we do have a github github.com / 00:11:59.320 --> 00:12:01.740 align:start position:0% us on we do have a github github.com / meta<00:11:59.530> -<00:12:00.160> network<00:12:00.370> there<00:12:01.120> we<00:12:01.210> have<00:12:01.360> most<00:12:01.600> these 00:12:01.740 --> 00:12:01.750 align:start position:0% meta - network there we have most these 00:12:01.750 --> 00:12:03.450 align:start position:0% meta - network there we have most these things<00:12:02.020> defined<00:12:02.470> conceptually<00:12:03.220> we<00:12:03.340> have 00:12:03.450 --> 00:12:03.460 align:start position:0% things defined conceptually we have 00:12:03.460 --> 00:12:05.310 align:start position:0% things defined conceptually we have documents<00:12:04.000> we<00:12:04.480> also<00:12:04.600> have<00:12:04.780> the<00:12:04.900> mess<00:12:05.050> ID 00:12:05.310 --> 00:12:05.320 align:start position:0% documents we also have the mess ID 00:12:05.320 --> 00:12:06.600 align:start position:0% documents we also have the mess ID framework<00:12:05.830> the<00:12:05.950> first<00:12:06.130> version<00:12:06.400> of<00:12:06.460> that 00:12:06.600 --> 00:12:06.610 align:start position:0% framework the first version of that 00:12:06.610 --> 00:12:08.400 align:start position:0% framework the first version of that which<00:12:06.760> is<00:12:06.850> open<00:12:07.120> source<00:12:07.330> we<00:12:08.080> plan<00:12:08.260> to<00:12:08.380> open 00:12:08.400 --> 00:12:08.410 align:start position:0% which is open source we plan to open 00:12:08.410 --> 00:12:09.930 align:start position:0% which is open source we plan to open source<00:12:08.710> more<00:12:08.950> things<00:12:09.130> over<00:12:09.460> the<00:12:09.550> coming<00:12:09.730> month 00:12:09.930 --> 00:12:09.940 align:start position:0% source more things over the coming month 00:12:09.940 --> 00:12:11.190 align:start position:0% source more things over the coming month so<00:12:10.090> please<00:12:10.120> do<00:12:10.360> check<00:12:10.450> it<00:12:10.600> out<00:12:10.780> we<00:12:11.020> obviously 00:12:11.190 --> 00:12:11.200 align:start position:0% so please do check it out we obviously 00:12:11.200 --> 00:12:13.350 align:start position:0% so please do check it out we obviously are<00:12:11.470> on<00:12:11.590> git<00:12:11.770> er<00:12:11.800> so<00:12:12.130> again<00:12:12.700> just<00:12:12.910> get<00:12:13.120> er<00:12:13.150> with 00:12:13.350 --> 00:12:13.360 align:start position:0% are on git er so again just get er with 00:12:13.360 --> 00:12:15.570 align:start position:0% are on git er so again just get er with the<00:12:13.450> same<00:12:13.660> thing<00:12:13.930> slash<00:12:14.200> lobby<00:12:14.410> and<00:12:14.680> then<00:12:15.220> if 00:12:15.570 --> 00:12:15.580 align:start position:0% the same thing slash lobby and then if 00:12:15.580 --> 00:12:16.830 align:start position:0% the same thing slash lobby and then if you<00:12:15.700> do<00:12:15.790> want<00:12:15.910> to<00:12:15.970> join<00:12:16.090> us<00:12:16.180> on<00:12:16.270> slack<00:12:16.540> and<00:12:16.750> talk 00:12:16.830 --> 00:12:16.840 align:start position:0% you do want to join us on slack and talk 00:12:16.840 --> 00:12:18.030 align:start position:0% you do want to join us on slack and talk about<00:12:17.020> things<00:12:17.200> that<00:12:17.260> may<00:12:17.410> be<00:12:17.470> less<00:12:17.650> technical 00:12:18.030 --> 00:12:18.040 align:start position:0% about things that may be less technical 00:12:18.040 --> 00:12:20.250 align:start position:0% about things that may be less technical community<00:12:18.880> don't<00:12:19.030> metal<00:12:19.330> -<00:12:19.600> network<00:12:19.750> dot<00:12:20.080> IO 00:12:20.250 --> 00:12:20.260 align:start position:0% community don't metal - network dot IO 00:12:20.260 --> 00:12:21.720 align:start position:0% community don't metal - network dot IO and<00:12:20.800> you<00:12:20.980> can<00:12:21.070> just<00:12:21.190> jump<00:12:21.310> into<00:12:21.460> the<00:12:21.580> sack 00:12:21.720 --> 00:12:21.730 align:start position:0% and you can just jump into the sack 00:12:21.730 --> 00:12:23.270 align:start position:0% and you can just jump into the sack there<00:12:21.970> and<00:12:22.150> it's<00:12:22.660> because<00:12:22.840> any<00:12:22.960> other<00:12:23.050> guys 00:12:23.270 --> 00:12:23.280 align:start position:0% there and it's because any other guys 00:12:23.280 --> 00:12:25.710 align:start position:0% there and it's because any other guys yeah<00:12:24.280> that's<00:12:25.030> the<00:12:25.240> end<00:12:25.330> of<00:12:25.390> my<00:12:25.480> presentation 00:12:25.710 --> 00:12:25.720 align:start position:0% yeah that's the end of my presentation 00:12:25.720 --> 00:12:32.200 align:start position:0% yeah that's the end of my presentation and<00:12:26.170> thank<00:12:26.500> you<00:12:26.590> very<00:12:26.770> much 00:12:32.200 --> 00:12:32.210 align:start position:0% 00:12:32.210 --> 00:12:39.690 align:start position:0% [Music]