WEBVTT Kind: captions Language: en 00:00:03.890 --> 00:00:09.080 align:start position:0% hi<00:00:04.890> I'm<00:00:05.220> beyond<00:00:05.879> and<00:00:07.519> when<00:00:08.519> it<00:00:08.639> comes<00:00:08.880> to 00:00:09.080 --> 00:00:09.090 align:start position:0% hi I'm beyond and when it comes to 00:00:09.090 --> 00:00:11.930 align:start position:0% hi I'm beyond and when it comes to bridging<00:00:09.900> that<00:00:10.110> AB<00:00:10.290> talk<00:00:10.740> contracts<00:00:11.490> talking 00:00:11.930 --> 00:00:11.940 align:start position:0% bridging that AB talk contracts talking 00:00:11.940 --> 00:00:14.509 align:start position:0% bridging that AB talk contracts talking across<00:00:12.179> chains<00:00:12.599> so<00:00:13.590> I<00:00:13.620> will<00:00:13.889> use<00:00:14.099> the<00:00:14.250> next 00:00:14.509 --> 00:00:14.519 align:start position:0% across chains so I will use the next 00:00:14.519 --> 00:00:16.099 align:start position:0% across chains so I will use the next half<00:00:14.730> hour<00:00:14.880> to<00:00:15.150> tell<00:00:15.330> you<00:00:15.420> a<00:00:15.450> bit<00:00:15.599> about<00:00:15.630> a 00:00:16.099 --> 00:00:16.109 align:start position:0% half hour to tell you a bit about a 00:00:16.109 --> 00:00:18.529 align:start position:0% half hour to tell you a bit about a project<00:00:16.619> if<00:00:16.980> you<00:00:17.010> know<00:00:17.340> vajay<00:00:17.760> overview<00:00:18.390> on<00:00:18.510> a 00:00:18.529 --> 00:00:18.539 align:start position:0% project if you know vajay overview on a 00:00:18.539 --> 00:00:20.689 align:start position:0% project if you know vajay overview on a project<00:00:19.080> that<00:00:19.170> we<00:00:19.410> kicked<00:00:19.680> off<00:00:19.830> roughly<00:00:20.369> one 00:00:20.689 --> 00:00:20.699 align:start position:0% project that we kicked off roughly one 00:00:20.699 --> 00:00:22.849 align:start position:0% project that we kicked off roughly one and<00:00:20.880> a<00:00:20.910> half<00:00:21.060> years<00:00:21.359> ago<00:00:21.420> in<00:00:21.810> the<00:00:22.439> larger 00:00:22.849 --> 00:00:22.859 align:start position:0% and a half years ago in the larger 00:00:22.859 --> 00:00:25.730 align:start position:0% and a half years ago in the larger context<00:00:23.460> of<00:00:23.490> another<00:00:23.939> poem<00:00:24.600> project<00:00:25.199> which<00:00:25.560> we 00:00:25.730 --> 00:00:25.740 align:start position:0% context of another poem project which we 00:00:25.740 --> 00:00:30.500 align:start position:0% context of another poem project which we call<00:00:25.949> polka<00:00:26.400> dot<00:00:28.730> to<00:00:29.730> really<00:00:29.970> understand<00:00:30.390> what 00:00:30.500 --> 00:00:30.510 align:start position:0% call polka dot to really understand what 00:00:30.510 --> 00:00:31.970 align:start position:0% call polka dot to really understand what we're<00:00:30.689> trying<00:00:30.929> to<00:00:31.109> do<00:00:31.260> I<00:00:31.289> want<00:00:31.590> to<00:00:31.679> give<00:00:31.800> you 00:00:31.970 --> 00:00:31.980 align:start position:0% we're trying to do I want to give you 00:00:31.980 --> 00:00:35.840 align:start position:0% we're trying to do I want to give you just<00:00:32.610> a<00:00:32.790> brief<00:00:33.030> brief<00:00:33.480> gist<00:00:34.110> of<00:00:34.380> polka<00:00:34.770> dot<00:00:34.950> so 00:00:35.840 --> 00:00:35.850 align:start position:0% just a brief brief gist of polka dot so 00:00:35.850 --> 00:00:38.240 align:start position:0% just a brief brief gist of polka dot so polka<00:00:36.719> dot<00:00:36.960> is<00:00:37.140> our<00:00:37.620> take<00:00:37.980> on<00:00:38.219> a 00:00:38.240 --> 00:00:38.250 align:start position:0% polka dot is our take on a 00:00:38.250 --> 00:00:41.930 align:start position:0% polka dot is our take on a next-generation<00:00:39.410> blockchain<00:00:40.410> protocol<00:00:40.940> with 00:00:41.930 --> 00:00:41.940 align:start position:0% next-generation blockchain protocol with 00:00:41.940 --> 00:00:44.020 align:start position:0% next-generation blockchain protocol with key<00:00:42.210> tenants<00:00:42.660> being<00:00:42.920> scalability 00:00:44.020 --> 00:00:44.030 align:start position:0% key tenants being scalability 00:00:44.030 --> 00:00:47.270 align:start position:0% key tenants being scalability interoperability<00:00:45.030> and<00:00:45.510> governments<00:00:46.280> it 00:00:47.270 --> 00:00:47.280 align:start position:0% interoperability and governments it 00:00:47.280 --> 00:00:48.830 align:start position:0% interoperability and governments it really<00:00:47.789> is 00:00:48.830 --> 00:00:48.840 align:start position:0% really is 00:00:48.840 --> 00:00:51.139 align:start position:0% really is heterogeneous<00:00:49.500> multi<00:00:50.190> chain<00:00:50.399> proposal<00:00:51.059> a 00:00:51.139 --> 00:00:51.149 align:start position:0% heterogeneous multi chain proposal a 00:00:51.149 --> 00:00:54.310 align:start position:0% heterogeneous multi chain proposal a framework<00:00:51.710> that<00:00:52.710> is<00:00:52.770> set<00:00:53.190> to<00:00:53.430> enable 00:00:54.310 --> 00:00:54.320 align:start position:0% framework that is set to enable 00:00:54.320 --> 00:00:56.930 align:start position:0% framework that is set to enable independent<00:00:55.320> blockchains<00:00:55.829> to<00:00:56.640> exchange 00:00:56.930 --> 00:00:56.940 align:start position:0% independent blockchains to exchange 00:00:56.940 --> 00:01:00.439 align:start position:0% independent blockchains to exchange information<00:00:57.899> and<00:00:58.680> value<00:00:59.460> in<00:00:59.670> a<00:00:59.850> trust<00:01:00.180> free 00:01:00.439 --> 00:01:00.449 align:start position:0% information and value in a trust free 00:01:00.449 --> 00:01:04.609 align:start position:0% information and value in a trust free manner<00:01:01.280> now<00:01:02.390> for<00:01:03.390> this<00:01:03.510> larger<00:01:03.960> vision<00:01:04.140> to 00:01:04.609 --> 00:01:04.619 align:start position:0% manner now for this larger vision to 00:01:04.619 --> 00:01:07.820 align:start position:0% manner now for this larger vision to become<00:01:04.799> a<00:01:05.280> success<00:01:05.990> we<00:01:06.990> need<00:01:07.020> a<00:01:07.229> component 00:01:07.820 --> 00:01:07.830 align:start position:0% become a success we need a component 00:01:07.830 --> 00:01:11.690 align:start position:0% become a success we need a component that<00:01:07.950> we<00:01:08.100> call<00:01:08.340> the<00:01:09.119> birch<00:01:09.330> and<00:01:10.250> the<00:01:11.250> bridge<00:01:11.460> in 00:01:11.690 --> 00:01:11.700 align:start position:0% that we call the birch and the bridge in 00:01:11.700 --> 00:01:14.840 align:start position:0% that we call the birch and the bridge in that<00:01:11.820> context<00:01:12.740> it's<00:01:13.740> supposed<00:01:14.159> to<00:01:14.369> enable 00:01:14.840 --> 00:01:14.850 align:start position:0% that context it's supposed to enable 00:01:14.850 --> 00:01:19.160 align:start position:0% that context it's supposed to enable block<00:01:15.780> chains<00:01:16.140> that<00:01:16.790> ourself<00:01:17.790> secure<00:01:18.450> that 00:01:19.160 --> 00:01:19.170 align:start position:0% block chains that ourself secure that 00:01:19.170 --> 00:01:21.679 align:start position:0% block chains that ourself secure that means<00:01:19.500> that<00:01:20.310> provide<00:01:20.700> their<00:01:20.939> own<00:01:21.060> means<00:01:21.390> to 00:01:21.679 --> 00:01:21.689 align:start position:0% means that provide their own means to 00:01:21.689 --> 00:01:25.370 align:start position:0% means that provide their own means to come<00:01:21.900> to<00:01:21.930> consensus<00:01:23.000> to<00:01:24.170> really<00:01:25.170> communicate 00:01:25.370 --> 00:01:25.380 align:start position:0% come to consensus to really communicate 00:01:25.380 --> 00:01:30.080 align:start position:0% come to consensus to really communicate with<00:01:25.890> each<00:01:26.009> other<00:01:26.750> now<00:01:28.189> when<00:01:29.189> we<00:01:29.340> started<00:01:30.000> with 00:01:30.080 --> 00:01:30.090 align:start position:0% with each other now when we started with 00:01:30.090 --> 00:01:32.450 align:start position:0% with each other now when we started with that<00:01:30.270> project<00:01:30.479> we<00:01:30.930> realized<00:01:31.799> that<00:01:31.950> we<00:01:32.430> really 00:01:32.450 --> 00:01:32.460 align:start position:0% that project we realized that we really 00:01:32.460 --> 00:01:37.060 align:start position:0% that project we realized that we really got<00:01:32.820> an<00:01:32.970> opportunity<00:01:33.720> to<00:01:34.380> create<00:01:35.369> value<00:01:35.520> for 00:01:37.060 --> 00:01:37.070 align:start position:0% got an opportunity to create value for 00:01:37.070 --> 00:01:39.590 align:start position:0% got an opportunity to create value for existing<00:01:38.070> aetherium<00:01:38.549> developers<00:01:39.090> rather 00:01:39.590 --> 00:01:39.600 align:start position:0% existing aetherium developers rather 00:01:39.600 --> 00:01:41.960 align:start position:0% existing aetherium developers rather than<00:01:39.930> shooting<00:01:40.500> for<00:01:40.829> the<00:01:40.950> moon<00:01:40.979> in<00:01:41.340> a<00:01:41.759> few 00:01:41.960 --> 00:01:41.970 align:start position:0% than shooting for the moon in a few 00:01:41.970 --> 00:01:47.840 align:start position:0% than shooting for the moon in a few years<00:01:42.180> and<00:01:45.079> in<00:01:46.079> order<00:01:46.380> to<00:01:46.409> understand<00:01:47.040> in<00:01:47.310> what 00:01:47.840 --> 00:01:47.850 align:start position:0% years and in order to understand in what 00:01:47.850 --> 00:01:50.090 align:start position:0% years and in order to understand in what way<00:01:48.119> this<00:01:48.180> can<00:01:48.720> help<00:01:49.049> a<00:01:49.259> serum<00:01:49.619> developers 00:01:50.090 --> 00:01:50.100 align:start position:0% way this can help a serum developers 00:01:50.100 --> 00:01:52.100 align:start position:0% way this can help a serum developers today<00:01:50.460> it's<00:01:51.060> important<00:01:51.540> to<00:01:51.600> understand<00:01:52.020> the 00:01:52.100 --> 00:01:52.110 align:start position:0% today it's important to understand the 00:01:52.110 --> 00:01:54.260 align:start position:0% today it's important to understand the problem<00:01:52.530> that<00:01:52.680> we<00:01:52.860> are<00:01:52.890> facing<00:01:53.159> today<00:01:53.430> those 00:01:54.260 --> 00:01:54.270 align:start position:0% problem that we are facing today those 00:01:54.270 --> 00:01:57.530 align:start position:0% problem that we are facing today those teams<00:01:54.720> that<00:01:54.840> building<00:01:55.350> dabs<00:01:55.560> today<00:01:55.920> and<00:01:56.729> I 00:01:57.530 --> 00:01:57.540 align:start position:0% teams that building dabs today and I 00:01:57.540 --> 00:02:00.080 align:start position:0% teams that building dabs today and I mean<00:01:57.990> most<00:01:58.170> of<00:01:58.350> you<00:01:58.619> are<00:01:58.890> aware<00:01:59.100> that<00:01:59.549> the<00:01:59.939> name 00:02:00.080 --> 00:02:00.090 align:start position:0% mean most of you are aware that the name 00:02:00.090 --> 00:02:02.990 align:start position:0% mean most of you are aware that the name of<00:02:00.240> the<00:02:00.360> game<00:02:00.540> is<00:02:01.170> scaling<00:02:01.710> right<00:02:02.040> we<00:02:02.700> still 00:02:02.990 --> 00:02:03.000 align:start position:0% of the game is scaling right we still 00:02:03.000 --> 00:02:05.090 align:start position:0% of the game is scaling right we still haven't<00:02:03.390> figured<00:02:03.570> out<00:02:03.840> how<00:02:04.079> easy<00:02:04.619> remain<00:02:04.920> that 00:02:05.090 --> 00:02:05.100 align:start position:0% haven't figured out how easy remain that 00:02:05.100 --> 00:02:10.999 align:start position:0% haven't figured out how easy remain that can<00:02:05.310> scale<00:02:05.610> and<00:02:06.380> I<00:02:09.140> personally<00:02:10.140> at<00:02:10.470> least<00:02:10.709> am 00:02:10.999 --> 00:02:11.009 align:start position:0% can scale and I personally at least am 00:02:11.009 --> 00:02:13.640 align:start position:0% can scale and I personally at least am very<00:02:11.629> skeptical 00:02:13.640 --> 00:02:13.650 align:start position:0% very skeptical 00:02:13.650 --> 00:02:16.670 align:start position:0% very skeptical saspa<00:02:14.310> will<00:02:15.180> arrive<00:02:15.659> within<00:02:15.959> the<00:02:16.110> next<00:02:16.349> 12 00:02:16.670 --> 00:02:16.680 align:start position:0% saspa will arrive within the next 12 00:02:16.680 --> 00:02:18.830 align:start position:0% saspa will arrive within the next 12 month<00:02:16.890> and<00:02:17.129> I<00:02:17.370> think<00:02:17.640> Edward<00:02:17.939> rather<00:02:18.209> take<00:02:18.810> a 00:02:18.830 --> 00:02:18.840 align:start position:0% month and I think Edward rather take a 00:02:18.840 --> 00:02:21.940 align:start position:0% month and I think Edward rather take a few<00:02:19.170> years<00:02:19.349> until<00:02:19.620> we<00:02:19.920> really<00:02:20.189> get<00:02:20.340> them<00:02:20.579> and 00:02:21.940 --> 00:02:21.950 align:start position:0% few years until we really get them and 00:02:21.950 --> 00:02:24.500 align:start position:0% few years until we really get them and what<00:02:22.950> we've<00:02:23.129> seen<00:02:23.400> over<00:02:23.459> the<00:02:23.790> last<00:02:23.879> years<00:02:24.299> is 00:02:24.500 --> 00:02:24.510 align:start position:0% what we've seen over the last years is 00:02:24.510 --> 00:02:27.380 align:start position:0% what we've seen over the last years is that<00:02:24.689> we<00:02:25.230> have<00:02:25.409> this<00:02:25.590> amazing<00:02:26.370> ecosystem<00:02:26.760> like 00:02:27.380 --> 00:02:27.390 align:start position:0% that we have this amazing ecosystem like 00:02:27.390 --> 00:02:29.690 align:start position:0% that we have this amazing ecosystem like hundreds<00:02:27.959> of<00:02:28.200> projects<00:02:28.980> that<00:02:29.069> have<00:02:29.129> been 00:02:29.690 --> 00:02:29.700 align:start position:0% hundreds of projects that have been 00:02:29.700 --> 00:02:31.580 align:start position:0% hundreds of projects that have been working<00:02:29.909> hard<00:02:30.329> on<00:02:30.540> implementing<00:02:31.230> certain 00:02:31.580 --> 00:02:31.590 align:start position:0% working hard on implementing certain 00:02:31.590 --> 00:02:33.589 align:start position:0% working hard on implementing certain depths<00:02:32.129> right<00:02:32.430> certain<00:02:33.120> depth<00:02:33.299> with<00:02:33.569> a 00:02:33.589 --> 00:02:33.599 align:start position:0% depths right certain depth with a 00:02:33.599 --> 00:02:38.289 align:start position:0% depths right certain depth with a certain<00:02:34.140> smart<00:02:34.709> contract<00:02:35.099> architecture<00:02:35.790> and 00:02:38.289 --> 00:02:38.299 align:start position:0% 00:02:38.299 --> 00:02:41.179 align:start position:0% it's<00:02:39.299> sad<00:02:39.659> but<00:02:40.019> the<00:02:40.170> reality<00:02:40.650> is<00:02:40.680> that<00:02:41.010> a<00:02:41.069> lot 00:02:41.179 --> 00:02:41.189 align:start position:0% it's sad but the reality is that a lot 00:02:41.189 --> 00:02:43.280 align:start position:0% it's sad but the reality is that a lot of<00:02:41.579> them<00:02:41.730> can't<00:02:42.060> go<00:02:42.239> live<00:02:42.450> today<00:02:42.780> on<00:02:42.900> maenette 00:02:43.280 --> 00:02:43.290 align:start position:0% of them can't go live today on maenette 00:02:43.290 --> 00:02:46.429 align:start position:0% of them can't go live today on maenette because<00:02:45.019> transaction<00:02:46.019> fees<00:02:46.200> are 00:02:46.429 --> 00:02:46.439 align:start position:0% because transaction fees are 00:02:46.439 --> 00:02:50.059 align:start position:0% because transaction fees are prohibitively<00:02:47.280> low<00:02:47.900> prohibitively<00:02:48.900> high<00:02:49.069> so 00:02:50.059 --> 00:02:50.069 align:start position:0% prohibitively low prohibitively high so 00:02:50.069 --> 00:02:54.050 align:start position:0% prohibitively low prohibitively high so the<00:02:51.709> depths<00:02:52.709> are<00:02:52.859> economically<00:02:53.519> not<00:02:53.730> feasible 00:02:54.050 --> 00:02:54.060 align:start position:0% the depths are economically not feasible 00:02:54.060 --> 00:02:56.839 align:start position:0% the depths are economically not feasible and<00:02:54.450> second<00:02:55.379> we<00:02:55.950> get<00:02:56.099> into<00:02:56.430> these<00:02:56.579> situations 00:02:56.839 --> 00:02:56.849 align:start position:0% and second we get into these situations 00:02:56.849 --> 00:02:59.179 align:start position:0% and second we get into these situations where<00:02:57.659> the<00:02:57.959> network<00:02:58.260> is<00:02:58.379> just<00:02:58.590> congested 00:02:59.179 --> 00:02:59.189 align:start position:0% where the network is just congested 00:02:59.189 --> 00:03:04.520 align:start position:0% where the network is just congested right<00:02:59.730> the<00:03:00.359> blocks<00:03:00.599> are<00:03:00.780> full<00:03:01.069> and<00:03:03.530> some 00:03:04.520 --> 00:03:04.530 align:start position:0% right the blocks are full and some 00:03:04.530 --> 00:03:07.099 align:start position:0% right the blocks are full and some people<00:03:04.829> may<00:03:04.950> say<00:03:05.189> right<00:03:05.609> but<00:03:06.480> you<00:03:06.840> know<00:03:06.930> we 00:03:07.099 --> 00:03:07.109 align:start position:0% people may say right but you know we 00:03:07.109 --> 00:03:08.929 align:start position:0% people may say right but you know we have<00:03:07.230> all<00:03:07.349> these<00:03:07.530> other<00:03:07.709> EVM<00:03:08.459> scaling 00:03:08.929 --> 00:03:08.939 align:start position:0% have all these other EVM scaling 00:03:08.939 --> 00:03:10.729 align:start position:0% have all these other EVM scaling approaches<00:03:09.450> right<00:03:09.629> that<00:03:09.959> can<00:03:10.470> potentially 00:03:10.729 --> 00:03:10.739 align:start position:0% approaches right that can potentially 00:03:10.739 --> 00:03:12.920 align:start position:0% approaches right that can potentially help<00:03:11.010> us<00:03:11.159> today<00:03:11.519> or<00:03:11.849> rather<00:03:12.060> in<00:03:12.329> a<00:03:12.389> few<00:03:12.599> months 00:03:12.920 --> 00:03:12.930 align:start position:0% help us today or rather in a few months 00:03:12.930 --> 00:03:16.099 align:start position:0% help us today or rather in a few months when<00:03:13.079> they're<00:03:13.260> done<00:03:13.500> and<00:03:13.769> a<00:03:14.459> lot<00:03:14.639> of<00:03:14.730> them<00:03:15.109> we 00:03:16.099 --> 00:03:16.109 align:start position:0% when they're done and a lot of them we 00:03:16.109 --> 00:03:18.740 align:start position:0% when they're done and a lot of them we we<00:03:16.530> call<00:03:16.799> Lea<00:03:17.189> do<00:03:17.519> scaling<00:03:18.000> solutions<00:03:18.510> right 00:03:18.740 --> 00:03:18.750 align:start position:0% we call Lea do scaling solutions right 00:03:18.750 --> 00:03:21.379 align:start position:0% we call Lea do scaling solutions right so<00:03:19.229> we<00:03:19.379> have<00:03:19.560> one<00:03:20.099> to<00:03:20.579> run<00:03:20.699> micropayment 00:03:21.379 --> 00:03:21.389 align:start position:0% so we have one to run micropayment 00:03:21.389 --> 00:03:25.550 align:start position:0% so we have one to run micropayment chairman<00:03:21.930> it's<00:03:22.139> such<00:03:22.440> as<00:03:22.819> micro<00:03:23.819> Radin<00:03:24.209> or<00:03:24.560> we 00:03:25.550 --> 00:03:25.560 align:start position:0% chairman it's such as micro Radin or we 00:03:25.560 --> 00:03:29.259 align:start position:0% chairman it's such as micro Radin or we have<00:03:25.790> state<00:03:26.790> channel<00:03:27.090> approaches<00:03:27.599> from<00:03:27.810> the 00:03:29.259 --> 00:03:29.269 align:start position:0% have state channel approaches from the 00:03:29.269 --> 00:03:32.539 align:start position:0% have state channel approaches from the wonderful<00:03:30.269> team<00:03:30.479> from<00:03:31.019> fanfare<00:03:31.650> the<00:03:32.129> january 00:03:32.539 --> 00:03:32.549 align:start position:0% wonderful team from fanfare the january 00:03:32.549 --> 00:03:35.539 align:start position:0% wonderful team from fanfare the january state<00:03:33.120> Senate<00:03:33.479> from<00:03:33.629> counterfactual<00:03:34.560> or<00:03:34.739> the 00:03:35.539 --> 00:03:35.549 align:start position:0% state Senate from counterfactual or the 00:03:35.549 --> 00:03:38.000 align:start position:0% state Senate from counterfactual or the great<00:03:35.819> work<00:03:36.090> that<00:03:36.620> spank<00:03:37.620> chain<00:03:37.829> has<00:03:37.979> been 00:03:38.000 --> 00:03:38.010 align:start position:0% great work that spank chain has been 00:03:38.010 --> 00:03:40.849 align:start position:0% great work that spank chain has been doing<00:03:38.449> and<00:03:39.449> last<00:03:39.690> but<00:03:39.810> not<00:03:39.959> least<00:03:40.199> just<00:03:40.290> plasma 00:03:40.849 --> 00:03:40.859 align:start position:0% doing and last but not least just plasma 00:03:40.859 --> 00:03:44.629 align:start position:0% doing and last but not least just plasma right<00:03:41.449> but<00:03:42.449> what<00:03:43.260> a<00:03:43.290> lot<00:03:43.530> of<00:03:43.560> people<00:03:43.859> forget<00:03:44.370> is 00:03:44.629 --> 00:03:44.639 align:start position:0% right but what a lot of people forget is 00:03:44.639 --> 00:03:48.080 align:start position:0% right but what a lot of people forget is that<00:03:45.680> those<00:03:46.680> approaches<00:03:47.310> are<00:03:47.430> not<00:03:47.699> applicable 00:03:48.080 --> 00:03:48.090 align:start position:0% that those approaches are not applicable 00:03:48.090 --> 00:03:51.409 align:start position:0% that those approaches are not applicable to<00:03:48.840> most<00:03:49.019> dab<00:03:49.349> architectures<00:03:50.129> that<00:03:50.419> exist 00:03:51.409 --> 00:03:51.419 align:start position:0% to most dab architectures that exist 00:03:51.419 --> 00:03:54.379 align:start position:0% to most dab architectures that exist today<00:03:51.599> so<00:03:52.319> these<00:03:52.859> teams<00:03:53.159> that<00:03:53.370> have<00:03:53.970> set<00:03:54.239> out 00:03:54.379 --> 00:03:54.389 align:start position:0% today so these teams that have set out 00:03:54.389 --> 00:03:56.179 align:start position:0% today so these teams that have set out like<00:03:54.629> a<00:03:54.659> few<00:03:54.900> years<00:03:54.930> ago<00:03:55.319> when<00:03:55.560> these<00:03:55.709> ideas 00:03:56.179 --> 00:03:56.189 align:start position:0% like a few years ago when these ideas 00:03:56.189 --> 00:03:57.649 align:start position:0% like a few years ago when these ideas weren't<00:03:56.489> around<00:03:56.760> yet<00:03:57.060> right<00:03:57.299> and<00:03:57.329> have 00:03:57.649 --> 00:03:57.659 align:start position:0% weren't around yet right and have 00:03:57.659 --> 00:03:59.689 align:start position:0% weren't around yet right and have written<00:03:57.900> like<00:03:58.139> hundreds<00:03:58.919> and<00:03:59.099> thousands<00:03:59.639> of 00:03:59.689 --> 00:03:59.699 align:start position:0% written like hundreds and thousands of 00:03:59.699 --> 00:04:01.759 align:start position:0% written like hundreds and thousands of lines<00:03:59.909> of<00:04:00.120> code<00:04:00.180> right<00:04:00.659> I<00:04:00.930> in<00:04:01.049> a<00:04:01.169> situation 00:04:01.759 --> 00:04:01.769 align:start position:0% lines of code right I in a situation 00:04:01.769 --> 00:04:03.649 align:start position:0% lines of code right I in a situation where<00:04:01.919> they're<00:04:02.069> like<00:04:02.220> if<00:04:02.669> we<00:04:03.000> want<00:04:03.299> to<00:04:03.389> use 00:04:03.649 --> 00:04:03.659 align:start position:0% where they're like if we want to use 00:04:03.659 --> 00:04:06.050 align:start position:0% where they're like if we want to use these<00:04:03.959> approaches<00:04:04.739> these<00:04:05.129> layer<00:04:05.400> to<00:04:05.699> scaling 00:04:06.050 --> 00:04:06.060 align:start position:0% these approaches these layer to scaling 00:04:06.060 --> 00:04:08.210 align:start position:0% these approaches these layer to scaling approaches<00:04:06.659> that<00:04:07.139> really<00:04:07.530> means<00:04:07.739> they<00:04:08.069> have 00:04:08.210 --> 00:04:08.220 align:start position:0% approaches that really means they have 00:04:08.220 --> 00:04:09.530 align:start position:0% approaches that really means they have to<00:04:08.400> start<00:04:08.669> from<00:04:08.909> ground<00:04:09.209> zero 00:04:09.530 --> 00:04:09.540 align:start position:0% to start from ground zero 00:04:09.540 --> 00:04:13.240 align:start position:0% to start from ground zero they<00:04:09.959> have<00:04:10.079> to<00:04:10.229> react<00:04:10.590> attack<00:04:10.949> their<00:04:11.340> hold<00:04:11.579> up 00:04:13.240 --> 00:04:13.250 align:start position:0% they have to react attack their hold up 00:04:13.250 --> 00:04:16.969 align:start position:0% they have to react attack their hold up so<00:04:14.250> and<00:04:14.579> that<00:04:15.359> is<00:04:15.479> what<00:04:15.750> I<00:04:15.780> believe<00:04:15.979> parity 00:04:16.969 --> 00:04:16.979 align:start position:0% so and that is what I believe parity 00:04:16.979 --> 00:04:19.550 align:start position:0% so and that is what I believe parity bridge<00:04:17.220> can<00:04:17.639> at<00:04:17.940> least<00:04:18.269> help<00:04:18.570> until<00:04:19.109> in<00:04:19.380> the 00:04:19.550 --> 00:04:19.560 align:start position:0% bridge can at least help until in the 00:04:19.560 --> 00:04:22.399 align:start position:0% bridge can at least help until in the intermediate<00:04:20.220> time<00:04:20.519> until<00:04:21.169> chess<00:04:22.169> pass 00:04:22.399 --> 00:04:22.409 align:start position:0% intermediate time until chess pass 00:04:22.409 --> 00:04:25.219 align:start position:0% intermediate time until chess pass around<00:04:22.590> right<00:04:23.250> so<00:04:23.969> let<00:04:24.150> me<00:04:24.270> introduce<00:04:24.690> you<00:04:25.080> to 00:04:25.219 --> 00:04:25.229 align:start position:0% around right so let me introduce you to 00:04:25.229 --> 00:04:26.090 align:start position:0% around right so let me introduce you to what<00:04:25.710> that 00:04:26.090 --> 00:04:26.100 align:start position:0% what that 00:04:26.100 --> 00:04:30.650 align:start position:0% what that paraty<00:04:26.640> bridge<00:04:28.490> basically<00:04:29.490> it's<00:04:30.120> a<00:04:30.240> federated 00:04:30.650 --> 00:04:30.660 align:start position:0% paraty bridge basically it's a federated 00:04:30.660 --> 00:04:35.240 align:start position:0% paraty bridge basically it's a federated system<00:04:31.370> that<00:04:32.370> allows<00:04:32.930> to<00:04:33.930> relay<00:04:34.320> arbitrary 00:04:35.240 --> 00:04:35.250 align:start position:0% system that allows to relay arbitrary 00:04:35.250 --> 00:04:37.370 align:start position:0% system that allows to relay arbitrary messages<00:04:35.460> any<00:04:36.090> kind<00:04:36.510> of<00:04:36.570> messages<00:04:37.140> between 00:04:37.370 --> 00:04:37.380 align:start position:0% messages any kind of messages between 00:04:37.380 --> 00:04:42.250 align:start position:0% messages any kind of messages between two<00:04:38.100> evm<00:04:38.700> networks<00:04:39.390> between<00:04:39.750> two<00:04:40.170> EVM<00:04:40.530> chains 00:04:42.250 --> 00:04:42.260 align:start position:0% two evm networks between two EVM chains 00:04:42.260 --> 00:04:45.590 align:start position:0% two evm networks between two EVM chains for<00:04:43.260> the<00:04:43.350> sake<00:04:43.560> of<00:04:43.590> this<00:04:44.300> presentation<00:04:45.300> here 00:04:45.590 --> 00:04:45.600 align:start position:0% for the sake of this presentation here 00:04:45.600 --> 00:04:47.570 align:start position:0% for the sake of this presentation here let<00:04:45.810> them<00:04:45.930> call<00:04:46.140> the<00:04:46.290> main<00:04:46.560> and<00:04:46.890> side<00:04:47.250> chain 00:04:47.570 --> 00:04:47.580 align:start position:0% let them call the main and side chain 00:04:47.580 --> 00:04:51.170 align:start position:0% let them call the main and side chain right<00:04:48.060> so<00:04:48.540> we<00:04:48.660> have<00:04:48.750> two<00:04:49.760> there<00:04:50.760> are<00:04:50.850> three 00:04:51.170 --> 00:04:51.180 align:start position:0% right so we have two there are three 00:04:51.180 --> 00:04:53.720 align:start position:0% right so we have two there are three critical<00:04:52.080> parts<00:04:52.620> of<00:04:52.680> that<00:04:52.860> verge<00:04:53.100> that<00:04:53.370> exist 00:04:53.720 --> 00:04:53.730 align:start position:0% critical parts of that verge that exist 00:04:53.730 --> 00:04:57.890 align:start position:0% critical parts of that verge that exist today<00:04:54.230> one<00:04:55.230> is<00:04:55.500> rust<00:04:55.950> software<00:04:56.610> that<00:04:57.180> connects 00:04:57.890 --> 00:04:57.900 align:start position:0% today one is rust software that connects 00:04:57.900 --> 00:05:01.640 align:start position:0% today one is rust software that connects to<00:04:58.200> two<00:04:58.410> aetherium<00:04:59.040> nodes<00:04:59.330> via<00:05:00.330> RPC<00:05:00.930> or<00:05:01.140> IPC 00:05:01.640 --> 00:05:01.650 align:start position:0% to two aetherium nodes via RPC or IPC 00:05:01.650 --> 00:05:04.340 align:start position:0% to two aetherium nodes via RPC or IPC you<00:05:01.860> can<00:05:02.010> choose<00:05:02.280> and<00:05:02.580> really<00:05:03.300> just<00:05:03.750> watches 00:05:04.340 --> 00:05:04.350 align:start position:0% you can choose and really just watches 00:05:04.350 --> 00:05:06.560 align:start position:0% you can choose and really just watches the<00:05:04.500> chain<00:05:04.950> for<00:05:05.250> certain<00:05:05.580> events<00:05:05.850> to<00:05:06.420> be 00:05:06.560 --> 00:05:06.570 align:start position:0% the chain for certain events to be 00:05:06.570 --> 00:05:09.680 align:start position:0% the chain for certain events to be triggered<00:05:07.400> then<00:05:08.400> second<00:05:08.940> there<00:05:09.510> are 00:05:09.680 --> 00:05:09.690 align:start position:0% triggered then second there are 00:05:09.690 --> 00:05:13.790 align:start position:0% triggered then second there are mid-space<00:05:10.500> entities<00:05:11.240> persons<00:05:12.240> that<00:05:13.050> run<00:05:13.590> the 00:05:13.790 --> 00:05:13.800 align:start position:0% mid-space entities persons that run the 00:05:13.800 --> 00:05:16.490 align:start position:0% mid-space entities persons that run the aforementioned<00:05:14.070> software<00:05:14.940> and<00:05:15.150> they<00:05:15.930> are<00:05:16.230> the 00:05:16.490 --> 00:05:16.500 align:start position:0% aforementioned software and they are the 00:05:16.500 --> 00:05:19.130 align:start position:0% aforementioned software and they are the authorities<00:05:17.190> that<00:05:17.520> validate<00:05:18.330> and<00:05:18.630> eventually 00:05:19.130 --> 00:05:19.140 align:start position:0% authorities that validate and eventually 00:05:19.140 --> 00:05:20.960 align:start position:0% authorities that validate and eventually relay<00:05:19.590> the<00:05:19.650> messages<00:05:20.220> from<00:05:20.400> one<00:05:20.550> chain<00:05:20.790> to 00:05:20.960 --> 00:05:20.970 align:start position:0% relay the messages from one chain to 00:05:20.970 --> 00:05:24.200 align:start position:0% relay the messages from one chain to another<00:05:21.210> and<00:05:21.980> last<00:05:22.980> but<00:05:23.190> not<00:05:23.310> least<00:05:23.550> we<00:05:24.180> have 00:05:24.200 --> 00:05:24.210 align:start position:0% another and last but not least we have 00:05:24.210 --> 00:05:26.870 align:start position:0% another and last but not least we have smart<00:05:25.050> contracts<00:05:25.590> on<00:05:25.710> both<00:05:25.860> chains<00:05:26.280> that 00:05:26.870 --> 00:05:26.880 align:start position:0% smart contracts on both chains that 00:05:26.880 --> 00:05:29.690 align:start position:0% smart contracts on both chains that coordinate<00:05:27.690> between<00:05:28.350> validate<00:05:29.190> between 00:05:29.690 --> 00:05:29.700 align:start position:0% coordinate between validate between 00:05:29.700 --> 00:05:32.360 align:start position:0% coordinate between validate between these<00:05:29.850> authorities<00:05:30.540> the<00:05:31.050> validation<00:05:31.770> the 00:05:32.360 --> 00:05:32.370 align:start position:0% these authorities the validation the 00:05:32.370 --> 00:05:34.850 align:start position:0% these authorities the validation the relay<00:05:32.880> and<00:05:33.120> eventual<00:05:33.930> delivery<00:05:34.530> of<00:05:34.710> the 00:05:34.850 --> 00:05:34.860 align:start position:0% relay and eventual delivery of the 00:05:34.860 --> 00:05:39.200 align:start position:0% relay and eventual delivery of the messages<00:05:36.440> now<00:05:37.520> what<00:05:38.520> can<00:05:38.640> you<00:05:38.700> do<00:05:38.910> with<00:05:39.060> them 00:05:39.200 --> 00:05:39.210 align:start position:0% messages now what can you do with them 00:05:39.210 --> 00:05:42.400 align:start position:0% messages now what can you do with them right<00:05:39.770> that's<00:05:40.770> that's<00:05:41.280> the<00:05:41.490> biggest<00:05:41.640> question 00:05:42.400 --> 00:05:42.410 align:start position:0% right that's that's the biggest question 00:05:42.410 --> 00:05:45.890 align:start position:0% right that's that's the biggest question well<00:05:43.410> the<00:05:44.370> nice<00:05:44.580> thing<00:05:44.610> about<00:05:44.940> that<00:05:45.210> is<00:05:45.450> this 00:05:45.890 --> 00:05:45.900 align:start position:0% well the nice thing about that is this 00:05:45.900 --> 00:05:48.190 align:start position:0% well the nice thing about that is this general<00:05:46.350> approaches<00:05:46.950> that<00:05:47.280> you<00:05:47.490> can<00:05:47.700> have 00:05:48.190 --> 00:05:48.200 align:start position:0% general approaches that you can have 00:05:48.200 --> 00:05:50.780 align:start position:0% general approaches that you can have adapt<00:05:49.200> that<00:05:49.500> has<00:05:49.680> a<00:05:49.710> smart<00:05:50.040> contract<00:05:50.250> on<00:05:50.610> one 00:05:50.780 --> 00:05:50.790 align:start position:0% adapt that has a smart contract on one 00:05:50.790 --> 00:05:54.770 align:start position:0% adapt that has a smart contract on one chain<00:05:51.030> that<00:05:51.960> suddenly<00:05:52.380> calls<00:05:53.310> a<00:05:53.670> function<00:05:54.180> on 00:05:54.770 --> 00:05:54.780 align:start position:0% chain that suddenly calls a function on 00:05:54.780 --> 00:05:59.030 align:start position:0% chain that suddenly calls a function on a<00:05:54.980> any<00:05:55.980> contract<00:05:56.940> with<00:05:57.810> any<00:05:58.050> parameters<00:05:58.860> on 00:05:59.030 --> 00:05:59.040 align:start position:0% a any contract with any parameters on 00:05:59.040 --> 00:06:03.850 align:start position:0% a any contract with any parameters on another<00:05:59.580> chain<00:05:59.870> it's<00:06:00.870> that<00:06:01.080> simple<00:06:01.430> and 00:06:03.850 --> 00:06:03.860 align:start position:0% another chain it's that simple and 00:06:03.860 --> 00:06:06.410 align:start position:0% another chain it's that simple and security<00:06:04.860> of<00:06:05.130> that<00:06:05.340> message<00:06:05.850> relay<00:06:06.090> is 00:06:06.410 --> 00:06:06.420 align:start position:0% security of that message relay is 00:06:06.420 --> 00:06:10.430 align:start position:0% security of that message relay is guaranteed<00:06:06.960> by<00:06:07.110> trustworthy<00:06:08.120> authorities<00:06:09.440> so 00:06:10.430 --> 00:06:10.440 align:start position:0% guaranteed by trustworthy authorities so 00:06:10.440 --> 00:06:13.220 align:start position:0% guaranteed by trustworthy authorities so for<00:06:11.370> every<00:06:11.700> and<00:06:11.940> each<00:06:12.210> message<00:06:12.600> that's<00:06:13.020> being 00:06:13.220 --> 00:06:13.230 align:start position:0% for every and each message that's being 00:06:13.230 --> 00:06:16.160 align:start position:0% for every and each message that's being relayed<00:06:13.680> it's<00:06:13.950> required<00:06:14.520> there's<00:06:14.940> a<00:06:15.060> that<00:06:15.450> a 00:06:16.160 --> 00:06:16.170 align:start position:0% relayed it's required there's a that a 00:06:16.170 --> 00:06:18.020 align:start position:0% relayed it's required there's a that a certain<00:06:16.890> number<00:06:16.920> of<00:06:17.280> authorities<00:06:17.400> have 00:06:18.020 --> 00:06:18.030 align:start position:0% certain number of authorities have 00:06:18.030 --> 00:06:21.820 align:start position:0% certain number of authorities have signed<00:06:18.360> off<00:06:18.540> of<00:06:18.810> that<00:06:18.990> message<00:06:19.950> relay<00:06:20.250> and 00:06:21.820 --> 00:06:21.830 align:start position:0% signed off of that message relay and 00:06:21.830 --> 00:06:24.380 align:start position:0% signed off of that message relay and overall<00:06:22.830> we<00:06:23.040> try<00:06:23.340> to<00:06:23.400> keep<00:06:23.700> the<00:06:23.880> system<00:06:24.090> as 00:06:24.380 --> 00:06:24.390 align:start position:0% overall we try to keep the system as 00:06:24.390 --> 00:06:29.920 align:start position:0% overall we try to keep the system as simple<00:06:25.140> in<00:06:25.320> general<00:06:26.010> as<00:06:26.160> possible<00:06:26.760> right<00:06:28.700> now 00:06:29.920 --> 00:06:29.930 align:start position:0% simple in general as possible right now 00:06:29.930 --> 00:06:33.020 align:start position:0% simple in general as possible right now how<00:06:30.930> can<00:06:31.320> that<00:06:31.380> help<00:06:31.770> mitigate<00:06:32.310> these<00:06:32.760> scaling 00:06:33.020 --> 00:06:33.030 align:start position:0% how can that help mitigate these scaling 00:06:33.030 --> 00:06:36.800 align:start position:0% how can that help mitigate these scaling issues<00:06:33.450> that<00:06:33.660> we<00:06:33.780> run<00:06:33.960> into<00:06:34.669> well<00:06:35.669> if<00:06:36.060> you<00:06:36.540> can 00:06:36.800 --> 00:06:36.810 align:start position:0% issues that we run into well if you can 00:06:36.810 --> 00:06:39.590 align:start position:0% issues that we run into well if you can offload<00:06:37.500> a<00:06:37.950> large<00:06:38.580> amount<00:06:38.940> of<00:06:39.030> transaction 00:06:39.590 --> 00:06:39.600 align:start position:0% offload a large amount of transaction 00:06:39.600 --> 00:06:42.650 align:start position:0% offload a large amount of transaction from<00:06:39.810> one<00:06:39.960> chain<00:06:40.230> to<00:06:40.380> another<00:06:40.710> right<00:06:41.660> that 00:06:42.650 --> 00:06:42.660 align:start position:0% from one chain to another right that 00:06:42.660 --> 00:06:46.210 align:start position:0% from one chain to another right that that<00:06:43.110> is<00:06:43.170> an<00:06:43.410> approach<00:06:43.710> you<00:06:43.740> can<00:06:44.040> choose<00:06:44.310> and 00:06:46.210 --> 00:06:46.220 align:start position:0% that is an approach you can choose and 00:06:46.220 --> 00:06:48.680 align:start position:0% that is an approach you can choose and really<00:06:47.220> what<00:06:47.370> you<00:06:47.490> can<00:06:47.700> do<00:06:47.880> there<00:06:48.120> now<00:06:48.270> because 00:06:48.680 --> 00:06:48.690 align:start position:0% really what you can do there now because 00:06:48.690 --> 00:06:51.980 align:start position:0% really what you can do there now because of<00:06:49.290> this<00:06:49.680> arbitrary<00:06:50.400> message<00:06:51.090> relay<00:06:51.420> approach 00:06:51.980 --> 00:06:51.990 align:start position:0% of this arbitrary message relay approach 00:06:51.990 --> 00:06:55.460 align:start position:0% of this arbitrary message relay approach is<00:06:52.260> you<00:06:52.920> can<00:06:53.210> spread<00:06:54.210> out<00:06:54.480> you<00:06:54.960> dab<00:06:55.200> between 00:06:55.460 --> 00:06:55.470 align:start position:0% is you can spread out you dab between 00:06:55.470 --> 00:06:58.760 align:start position:0% is you can spread out you dab between those<00:06:56.070> multiple<00:06:56.550> chains<00:06:56.790> so<00:06:57.390> you<00:06:57.450> have<00:06:57.810> the 00:06:58.760 --> 00:06:58.770 align:start position:0% those multiple chains so you have the 00:06:58.770 --> 00:07:00.710 align:start position:0% those multiple chains so you have the assets<00:06:59.220> that<00:06:59.340> need<00:06:59.640> to<00:06:59.880> live<00:07:00.060> on<00:07:00.240> main<00:07:00.480> that 00:07:00.710 --> 00:07:00.720 align:start position:0% assets that need to live on main that 00:07:00.720 --> 00:07:02.480 align:start position:0% assets that need to live on main that right<00:07:01.050> on<00:07:01.200> the<00:07:01.320> assumed<00:07:01.620> name<00:07:01.710> that<00:07:02.040> may<00:07:02.430> be 00:07:02.480 --> 00:07:02.490 align:start position:0% right on the assumed name that may be 00:07:02.490 --> 00:07:04.820 align:start position:0% right on the assumed name that may be those<00:07:02.790> that<00:07:03.060> have<00:07:03.240> to<00:07:03.450> be<00:07:03.680> interact<00:07:04.680> with 00:07:04.820 --> 00:07:04.830 align:start position:0% those that have to be interact with 00:07:04.830 --> 00:07:07.430 align:start position:0% those that have to be interact with exchanges<00:07:05.640> or<00:07:05.790> maybe<00:07:06.300> some<00:07:06.600> identity<00:07:07.170> of<00:07:07.260> the 00:07:07.430 --> 00:07:07.440 align:start position:0% exchanges or maybe some identity of the 00:07:07.440 --> 00:07:11.200 align:start position:0% exchanges or maybe some identity of the user<00:07:07.590> that<00:07:07.950> can<00:07:08.490> stay<00:07:08.730> with<00:07:08.970> us<00:07:09.180> right<00:07:09.570> but 00:07:11.200 --> 00:07:11.210 align:start position:0% user that can stay with us right but 00:07:11.210 --> 00:07:13.850 align:start position:0% user that can stay with us right but those<00:07:12.210> interactions<00:07:12.780> within<00:07:13.230> the<00:07:13.500> apps<00:07:13.650> that 00:07:13.850 --> 00:07:13.860 align:start position:0% those interactions within the apps that 00:07:13.860 --> 00:07:17.320 align:start position:0% those interactions within the apps that happens<00:07:14.280> on<00:07:14.460> chain<00:07:14.790> right<00:07:15.060> that<00:07:15.300> are<00:07:15.420> really 00:07:17.320 --> 00:07:17.330 align:start position:0% happens on chain right that are really 00:07:17.330 --> 00:07:19.580 align:start position:0% happens on chain right that are really computationally<00:07:18.330> expensive<00:07:18.480> or<00:07:19.050> we<00:07:19.200> try<00:07:19.470> a 00:07:19.580 --> 00:07:19.590 align:start position:0% computationally expensive or we try a 00:07:19.590 --> 00:07:22.040 align:start position:0% computationally expensive or we try a lot<00:07:20.160> of<00:07:20.190> transactions<00:07:20.940> those<00:07:21.480> you<00:07:21.750> try<00:07:21.990> to 00:07:22.040 --> 00:07:22.050 align:start position:0% lot of transactions those you try to 00:07:22.050 --> 00:07:26.630 align:start position:0% lot of transactions those you try to outsource<00:07:22.650> to<00:07:23.310> another<00:07:23.820> app<00:07:25.220> so<00:07:26.220> that's<00:07:26.460> one 00:07:26.630 --> 00:07:26.640 align:start position:0% outsource to another app so that's one 00:07:26.640 --> 00:07:28.700 align:start position:0% outsource to another app so that's one part<00:07:26.850> the<00:07:27.210> other<00:07:27.360> exciting<00:07:27.990> part<00:07:28.230> about<00:07:28.350> that 00:07:28.700 --> 00:07:28.710 align:start position:0% part the other exciting part about that 00:07:28.710 --> 00:07:31.220 align:start position:0% part the other exciting part about that approach<00:07:29.040> is<00:07:29.340> in<00:07:30.060> my<00:07:30.300> opinion<00:07:30.720> that<00:07:30.750> you<00:07:31.020> can 00:07:31.220 --> 00:07:31.230 align:start position:0% approach is in my opinion that you can 00:07:31.230 --> 00:07:33.430 align:start position:0% approach is in my opinion that you can really<00:07:31.620> get<00:07:31.860> early<00:07:32.250> access<00:07:32.280> to<00:07:32.820> new<00:07:33.000> features 00:07:33.430 --> 00:07:33.440 align:start position:0% really get early access to new features 00:07:33.440 --> 00:07:35.990 align:start position:0% really get early access to new features features<00:07:34.440> that<00:07:34.620> are<00:07:34.800> have<00:07:35.310> yet<00:07:35.640> to<00:07:35.670> become 00:07:35.990 --> 00:07:36.000 align:start position:0% features that are have yet to become 00:07:36.000 --> 00:07:39.230 align:start position:0% features that are have yet to become available<00:07:36.330> on<00:07:36.900> the<00:07:37.050> main<00:07:37.170> net<00:07:37.410> so<00:07:38.160> if<00:07:38.610> you<00:07:39.000> take 00:07:39.230 --> 00:07:39.240 align:start position:0% available on the main net so if you take 00:07:39.240 --> 00:07:41.180 align:start position:0% available on the main net so if you take as<00:07:39.510> an<00:07:39.780> example<00:07:39.870> that<00:07:40.320> the<00:07:40.500> sidechain<00:07:41.040> is 00:07:41.180 --> 00:07:41.190 align:start position:0% as an example that the sidechain is 00:07:41.190 --> 00:07:43.250 align:start position:0% as an example that the sidechain is being<00:07:41.400> run<00:07:41.640> by<00:07:41.670> parity<00:07:42.240> theory<00:07:42.720> nodes<00:07:42.930> right 00:07:43.250 --> 00:07:43.260 align:start position:0% being run by parity theory nodes right 00:07:43.260 --> 00:07:46.310 align:start position:0% being run by parity theory nodes right in<00:07:43.470> a<00:07:43.560> pure<00:07:44.250> network<00:07:44.700> you<00:07:45.420> could<00:07:45.600> have<00:07:45.900> today 00:07:46.310 --> 00:07:46.320 align:start position:0% in a pure network you could have today 00:07:46.320 --> 00:07:48.830 align:start position:0% in a pure network you could have today wasn't<00:07:47.190> smart<00:07:47.580> contracts<00:07:48.060> being<00:07:48.390> run<00:07:48.600> down 00:07:48.830 --> 00:07:48.840 align:start position:0% wasn't smart contracts being run down 00:07:48.840 --> 00:07:52.840 align:start position:0% wasn't smart contracts being run down you<00:07:49.320> could<00:07:49.530> use<00:07:49.830> private<00:07:50.640> transactions<00:07:51.740> or 00:07:52.840 --> 00:07:52.850 align:start position:0% you could use private transactions or 00:07:52.850 --> 00:07:56.660 align:start position:0% you could use private transactions or you<00:07:53.850> could<00:07:54.030> try<00:07:54.330> out<00:07:54.620> constantinople<00:07:55.670> opcodes 00:07:56.660 --> 00:07:56.670 align:start position:0% you could try out constantinople opcodes 00:07:56.670 --> 00:07:58.580 align:start position:0% you could try out constantinople opcodes that<00:07:56.880> will<00:07:57.030> only<00:07:57.240> become<00:07:57.480> available<00:07:57.780> in<00:07:58.350> half 00:07:58.580 --> 00:07:58.590 align:start position:0% that will only become available in half 00:07:58.590 --> 00:08:01.010 align:start position:0% that will only become available in half a<00:07:58.710> year<00:07:58.920> in<00:07:58.950> general<00:07:59.190> when<00:07:59.670> you<00:08:00.020> Maynard 00:08:01.010 --> 00:08:01.020 align:start position:0% a year in general when you Maynard 00:08:01.020 --> 00:08:06.020 align:start position:0% a year in general when you Maynard upgrades<00:08:03.560> there's<00:08:04.560> one<00:08:05.040> note<00:08:05.310> of<00:08:05.340> caution<00:08:05.520> I 00:08:06.020 --> 00:08:06.030 align:start position:0% upgrades there's one note of caution I 00:08:06.030 --> 00:08:08.300 align:start position:0% upgrades there's one note of caution I wanna<00:08:06.270> I<00:08:06.570> want<00:08:06.930> to<00:08:07.020> add<00:08:07.140> here<00:08:07.170> and<00:08:07.590> that's<00:08:08.040> very 00:08:08.300 --> 00:08:08.310 align:start position:0% wanna I want to add here and that's very 00:08:08.310 --> 00:08:11.510 align:start position:0% wanna I want to add here and that's very important<00:08:08.820> to<00:08:08.850> me<00:08:09.470> why<00:08:10.470> this<00:08:10.530> is<00:08:10.860> really<00:08:11.280> great 00:08:11.510 --> 00:08:11.520 align:start position:0% important to me why this is really great 00:08:11.520 --> 00:08:14.180 align:start position:0% important to me why this is really great for<00:08:11.580> the<00:08:11.850> moment<00:08:12.300> in<00:08:12.540> the<00:08:13.350> long<00:08:13.590> run 00:08:14.180 --> 00:08:14.190 align:start position:0% for the moment in the long run 00:08:14.190 --> 00:08:17.270 align:start position:0% for the moment in the long run this<00:08:14.640> isn't<00:08:15.270> gonna<00:08:15.480> solve<00:08:15.930> the<00:08:16.530> scaling<00:08:17.010> issue 00:08:17.270 --> 00:08:17.280 align:start position:0% this isn't gonna solve the scaling issue 00:08:17.280 --> 00:08:20.990 align:start position:0% this isn't gonna solve the scaling issue in<00:08:17.880> in<00:08:18.390> in<00:08:18.810> the<00:08:18.960> hole<00:08:19.110> right<00:08:19.470> that's<00:08:20.430> why<00:08:20.640> the 00:08:20.990 --> 00:08:21.000 align:start position:0% in in in the hole right that's why the 00:08:21.000 --> 00:08:23.360 align:start position:0% in in in the hole right that's why the slide<00:08:21.270> says<00:08:21.540> mitigating<00:08:22.200> scaling<00:08:22.590> issues<00:08:23.130> and 00:08:23.360 --> 00:08:23.370 align:start position:0% slide says mitigating scaling issues and 00:08:23.370 --> 00:08:26.330 align:start position:0% slide says mitigating scaling issues and not<00:08:23.730> solving<00:08:24.270> them<00:08:24.420> because<00:08:25.200> what<00:08:25.890> that<00:08:25.920> means 00:08:26.330 --> 00:08:26.340 align:start position:0% not solving them because what that means 00:08:26.340 --> 00:08:30.530 align:start position:0% not solving them because what that means here<00:08:26.730> is<00:08:26.880> that<00:08:27.920> you<00:08:28.920> know<00:08:29.070> if<00:08:29.580> you<00:08:29.880> spin<00:08:30.330> up<00:08:30.360> a 00:08:30.530 --> 00:08:30.540 align:start position:0% here is that you know if you spin up a 00:08:30.540 --> 00:08:32.600 align:start position:0% here is that you know if you spin up a new<00:08:30.570> side<00:08:31.020> chain<00:08:31.410> that<00:08:31.440> means<00:08:31.920> you<00:08:32.160> also<00:08:32.310> have 00:08:32.600 --> 00:08:32.610 align:start position:0% new side chain that means you also have 00:08:32.610 --> 00:08:34.700 align:start position:0% new side chain that means you also have to<00:08:32.729> secure<00:08:33.090> that<00:08:33.330> chance<00:08:33.599> I<00:08:33.780> chain<00:08:34.080> and<00:08:34.289> as 00:08:34.700 --> 00:08:34.710 align:start position:0% to secure that chance I chain and as 00:08:34.710 --> 00:08:37.550 align:start position:0% to secure that chance I chain and as more<00:08:35.010> side<00:08:35.370> chains<00:08:35.700> are<00:08:35.880> as<00:08:36.210> more<00:08:36.900> resources 00:08:37.550 --> 00:08:37.560 align:start position:0% more side chains are as more resources 00:08:37.560 --> 00:08:39.860 align:start position:0% more side chains are as more resources you<00:08:37.830> need<00:08:38.039> to<00:08:38.219> secure<00:08:38.700> these<00:08:38.910> individual<00:08:39.630> side 00:08:39.860 --> 00:08:39.870 align:start position:0% you need to secure these individual side 00:08:39.870 --> 00:08:43.279 align:start position:0% you need to secure these individual side chains<00:08:40.169> and<00:08:40.910> we<00:08:41.910> all<00:08:42.090> believe<00:08:42.479> that<00:08:42.510> that 00:08:43.279 --> 00:08:43.289 align:start position:0% chains and we all believe that that 00:08:43.289 --> 00:08:47.120 align:start position:0% chains and we all believe that that can't<00:08:43.680> skate<00:08:44.070> securely<00:08:44.610> nonetheless<00:08:45.570> in<00:08:46.260> the 00:08:47.120 --> 00:08:47.130 align:start position:0% can't skate securely nonetheless in the 00:08:47.130 --> 00:08:49.430 align:start position:0% can't skate securely nonetheless in the meantime<00:08:47.370> this<00:08:48.300> is<00:08:48.450> a<00:08:48.480> way<00:08:48.750> to<00:08:48.810> get<00:08:49.170> your 00:08:49.430 --> 00:08:49.440 align:start position:0% meantime this is a way to get your 00:08:49.440 --> 00:08:52.620 align:start position:0% meantime this is a way to get your application<00:08:49.920> life 00:08:52.620 --> 00:08:52.630 align:start position:0% 00:08:52.630 --> 00:08:55.470 align:start position:0% so<00:08:53.440> for<00:08:53.949> the<00:08:54.069> sign<00:08:54.279> change<00:08:54.579> what<00:08:54.910> options<00:08:55.329> do 00:08:55.470 --> 00:08:55.480 align:start position:0% so for the sign change what options do 00:08:55.480 --> 00:08:56.040 align:start position:0% so for the sign change what options do we<00:08:55.540> have 00:08:56.040 --> 00:08:56.050 align:start position:0% we have 00:08:56.050 --> 00:08:59.400 align:start position:0% we have I<00:08:57.180> believe<00:08:58.180> you<00:08:58.300> can<00:08:58.509> choose<00:08:58.779> between<00:08:59.170> three 00:08:59.400 --> 00:08:59.410 align:start position:0% I believe you can choose between three 00:08:59.410 --> 00:09:02.670 align:start position:0% I believe you can choose between three flavors<00:08:59.980> right<00:09:00.160> now<00:09:00.310> either<00:09:01.029> you<00:09:01.389> say<00:09:01.630> hey<00:09:02.259> you 00:09:02.670 --> 00:09:02.680 align:start position:0% flavors right now either you say hey you 00:09:02.680 --> 00:09:06.090 align:start position:0% flavors right now either you say hey you know<00:09:02.800> I<00:09:03.040> need<00:09:03.610> the<00:09:03.880> the<00:09:05.100> transaction 00:09:06.090 --> 00:09:06.100 align:start position:0% know I need the the transaction 00:09:06.100 --> 00:09:07.860 align:start position:0% know I need the the transaction throughput<00:09:06.730> that's<00:09:06.940> available<00:09:07.480> on<00:09:07.600> a<00:09:07.630> new 00:09:07.860 --> 00:09:07.870 align:start position:0% throughput that's available on a new 00:09:07.870 --> 00:09:11.340 align:start position:0% throughput that's available on a new change<00:09:08.170> for<00:09:08.230> myself<00:09:08.500> for<00:09:08.889> my<00:09:08.980> own<00:09:09.009> app<00:09:09.370> in<00:09:10.350> Pepe 00:09:11.340 --> 00:09:11.350 align:start position:0% change for myself for my own app in Pepe 00:09:11.350 --> 00:09:13.939 align:start position:0% change for myself for my own app in Pepe or<00:09:11.500> a<00:09:11.589> parity<00:09:12.100> theorem<00:09:12.519> you<00:09:12.670> can<00:09:12.699> get<00:09:13.089> up<00:09:13.360> to 00:09:13.939 --> 00:09:13.949 align:start position:0% or a parity theorem you can get up to 00:09:13.949 --> 00:09:17.639 align:start position:0% or a parity theorem you can get up to maybe<00:09:14.949> 500<00:09:15.279> maybe<00:09:15.850> one<00:09:16.690> to<00:09:16.870> two<00:09:17.019> thousand 00:09:17.639 --> 00:09:17.649 align:start position:0% maybe 500 maybe one to two thousand 00:09:17.649 --> 00:09:19.769 align:start position:0% maybe 500 maybe one to two thousand transactions<00:09:18.370> per<00:09:18.490> second<00:09:18.850> and<00:09:19.060> then<00:09:19.630> you 00:09:19.769 --> 00:09:19.779 align:start position:0% transactions per second and then you 00:09:19.779 --> 00:09:22.290 align:start position:0% transactions per second and then you just<00:09:19.990> say<00:09:20.170> like<00:09:20.380> hey<00:09:20.589> I<00:09:20.800> spin<00:09:21.310> up<00:09:21.459> my<00:09:21.670> own<00:09:21.850> def 00:09:22.290 --> 00:09:22.300 align:start position:0% just say like hey I spin up my own def 00:09:22.300 --> 00:09:24.930 align:start position:0% just say like hey I spin up my own def specific<00:09:22.899> chain<00:09:23.170> you<00:09:23.680> get<00:09:23.800> a<00:09:23.860> few<00:09:24.250> different 00:09:24.930 --> 00:09:24.940 align:start position:0% specific chain you get a few different 00:09:24.940 --> 00:09:27.360 align:start position:0% specific chain you get a few different projects<00:09:25.899> to<00:09:26.079> run<00:09:26.259> an<00:09:26.410> authority<00:09:26.980> note<00:09:27.190> and 00:09:27.360 --> 00:09:27.370 align:start position:0% projects to run an authority note and 00:09:27.370 --> 00:09:31.319 align:start position:0% projects to run an authority note and thereby<00:09:27.910> secure<00:09:28.300> your<00:09:28.449> chain<00:09:28.660> or<00:09:29.459> you<00:09:30.459> say<00:09:30.730> no 00:09:31.319 --> 00:09:31.329 align:start position:0% thereby secure your chain or you say no 00:09:31.329 --> 00:09:34.110 align:start position:0% thereby secure your chain or you say no actually<00:09:32.139> you<00:09:32.620> know<00:09:32.769> this<00:09:33.190> is<00:09:33.399> as<00:09:33.550> a<00:09:33.579> team<00:09:33.910> and 00:09:34.110 --> 00:09:34.120 align:start position:0% actually you know this is as a team and 00:09:34.120 --> 00:09:37.110 align:start position:0% actually you know this is as a team and we<00:09:34.540> have<00:09:34.750> like<00:09:35.220> applications<00:09:36.220> that<00:09:36.459> interface 00:09:37.110 --> 00:09:37.120 align:start position:0% we have like applications that interface 00:09:37.120 --> 00:09:39.090 align:start position:0% we have like applications that interface with<00:09:37.149> each<00:09:37.509> other<00:09:37.750> that<00:09:38.110> are<00:09:38.139> reliant<00:09:38.680> on<00:09:38.889> each 00:09:39.090 --> 00:09:39.100 align:start position:0% with each other that are reliant on each 00:09:39.100 --> 00:09:42.480 align:start position:0% with each other that are reliant on each other<00:09:39.339> and<00:09:39.579> we<00:09:39.639> both<00:09:40.269> make<00:09:40.930> a<00:09:41.130> consortium<00:09:42.130> and 00:09:42.480 --> 00:09:42.490 align:start position:0% other and we both make a consortium and 00:09:42.490 --> 00:09:46.499 align:start position:0% other and we both make a consortium and we<00:09:42.819> spin<00:09:43.120> up<00:09:43.149> our<00:09:43.509> our<00:09:44.170> kind<00:09:45.100> of<00:09:45.220> deaf<00:09:45.910> friends 00:09:46.499 --> 00:09:46.509 align:start position:0% we spin up our our kind of deaf friends 00:09:46.509 --> 00:09:50.610 align:start position:0% we spin up our our kind of deaf friends of<00:09:46.630> dabs<00:09:46.870> chain<00:09:47.579> or<00:09:48.579> last<00:09:49.300> but<00:09:49.509> not<00:09:49.630> least<00:09:49.899> you 00:09:50.610 --> 00:09:50.620 align:start position:0% of dabs chain or last but not least you 00:09:50.620 --> 00:09:53.900 align:start position:0% of dabs chain or last but not least you use<00:09:51.579> an<00:09:51.730> existing<00:09:51.850> bridge<00:09:52.569> that<00:09:53.380> verges 00:09:53.900 --> 00:09:53.910 align:start position:0% use an existing bridge that verges 00:09:53.910 --> 00:09:56.670 align:start position:0% use an existing bridge that verges existing<00:09:54.910> networks<00:09:55.360> for<00:09:55.779> example<00:09:56.259> the<00:09:56.410> easier 00:09:56.670 --> 00:09:56.680 align:start position:0% existing networks for example the easier 00:09:56.680 --> 00:10:01.670 align:start position:0% existing networks for example the easier main<00:09:56.949> network<00:09:57.339> with<00:09:57.639> the<00:09:57.759> cove<00:09:57.970> intestine<00:10:00.240> now 00:10:01.670 --> 00:10:01.680 align:start position:0% main network with the cove intestine now 00:10:01.680 --> 00:10:04.650 align:start position:0% main network with the cove intestine now let's<00:10:02.680> take<00:10:03.040> a<00:10:03.069> look<00:10:03.310> how<00:10:03.610> parity<00:10:04.420> bridge 00:10:04.650 --> 00:10:04.660 align:start position:0% let's take a look how parity bridge 00:10:04.660 --> 00:10:09.569 align:start position:0% let's take a look how parity bridge actually<00:10:05.019> works<00:10:05.620> the<00:10:07.709> next<00:10:08.709> few<00:10:09.040> slides<00:10:09.160> will 00:10:09.569 --> 00:10:09.579 align:start position:0% actually works the next few slides will 00:10:09.579 --> 00:10:12.960 align:start position:0% actually works the next few slides will show<00:10:09.910> you<00:10:10.689> what<00:10:10.930> a<00:10:10.959> walkthrough<00:10:11.550> for<00:10:12.550> message 00:10:12.960 --> 00:10:12.970 align:start position:0% show you what a walkthrough for message 00:10:12.970 --> 00:10:17.429 align:start position:0% show you what a walkthrough for message being<00:10:13.269> sent<00:10:13.360> from<00:10:14.050> main<00:10:14.620> tree<00:10:15.220> send<00:10:16.410> what<00:10:17.410> you 00:10:17.429 --> 00:10:17.439 align:start position:0% being sent from main tree send what you 00:10:17.439 --> 00:10:20.850 align:start position:0% being sent from main tree send what you can<00:10:17.740> see<00:10:18.040> in<00:10:18.490> these<00:10:18.880> diagrams<00:10:19.180> is<00:10:19.779> on<00:10:20.170> the<00:10:20.649> left 00:10:20.850 --> 00:10:20.860 align:start position:0% can see in these diagrams is on the left 00:10:20.860 --> 00:10:22.379 align:start position:0% can see in these diagrams is on the left side<00:10:21.069> there's<00:10:21.519> a<00:10:21.579> main<00:10:21.819> chain<00:10:22.060> on<00:10:22.240> the<00:10:22.360> right 00:10:22.379 --> 00:10:22.389 align:start position:0% side there's a main chain on the right 00:10:22.389 --> 00:10:25.530 align:start position:0% side there's a main chain on the right side<00:10:22.720> there's<00:10:22.959> a<00:10:23.079> side<00:10:23.259> chain<00:10:23.790> on<00:10:24.790> the<00:10:25.360> main 00:10:25.530 --> 00:10:25.540 align:start position:0% side there's a side chain on the main 00:10:25.540 --> 00:10:27.960 align:start position:0% side there's a side chain on the main chain<00:10:25.810> you<00:10:26.050> have<00:10:26.079> a<00:10:26.800> contract<00:10:27.639> deployed 00:10:27.960 --> 00:10:27.970 align:start position:0% chain you have a contract deployed 00:10:27.970 --> 00:10:29.460 align:start position:0% chain you have a contract deployed that's<00:10:28.240> called<00:10:28.600> which<00:10:28.839> contract<00:10:29.290> right<00:10:29.439> now 00:10:29.460 --> 00:10:29.470 align:start position:0% that's called which contract right now 00:10:29.470 --> 00:10:32.910 align:start position:0% that's called which contract right now it<00:10:30.100> has<00:10:30.310> one<00:10:31.300> function<00:10:31.480> that's<00:10:32.079> called<00:10:32.319> relay 00:10:32.910 --> 00:10:32.920 align:start position:0% it has one function that's called relay 00:10:32.920 --> 00:10:36.240 align:start position:0% it has one function that's called relay message<00:10:33.339> on<00:10:34.110> the<00:10:35.110> side<00:10:35.319> chain<00:10:35.350> you<00:10:35.860> have<00:10:36.220> a 00:10:36.240 --> 00:10:36.250 align:start position:0% message on the side chain you have a 00:10:36.250 --> 00:10:37.319 align:start position:0% message on the side chain you have a bridge<00:10:36.550> contract<00:10:36.939> as<00:10:37.089> well 00:10:37.319 --> 00:10:37.329 align:start position:0% bridge contract as well 00:10:37.329 --> 00:10:39.629 align:start position:0% bridge contract as well right<00:10:37.720> and<00:10:37.959> it's<00:10:38.439> called<00:10:38.769> it<00:10:39.160> has<00:10:39.370> a<00:10:39.399> function 00:10:39.629 --> 00:10:39.639 align:start position:0% right and it's called it has a function 00:10:39.639 --> 00:10:44.579 align:start position:0% right and it's called it has a function called<00:10:39.819> confirm<00:10:40.449> message<00:10:41.459> now<00:10:43.410> some<00:10:44.410> app 00:10:44.579 --> 00:10:44.589 align:start position:0% called confirm message now some app 00:10:44.589 --> 00:10:47.730 align:start position:0% called confirm message now some app wants<00:10:45.009> to<00:10:45.130> use<00:10:45.339> this<00:10:46.000> bridge<00:10:46.350> what<00:10:47.350> the<00:10:47.529> Deaf 00:10:47.730 --> 00:10:47.740 align:start position:0% wants to use this bridge what the Deaf 00:10:47.740 --> 00:10:51.269 align:start position:0% wants to use this bridge what the Deaf does<00:10:48.009> it<00:10:48.399> deploy<00:10:49.149> is<00:10:49.470> extension<00:10:50.470> contracts<00:10:50.980> so 00:10:51.269 --> 00:10:51.279 align:start position:0% does it deploy is extension contracts so 00:10:51.279 --> 00:10:54.030 align:start position:0% does it deploy is extension contracts so contracts<00:10:52.089> that<00:10:52.689> know<00:10:52.959> how<00:10:53.199> to<00:10:53.259> interact<00:10:53.740> with 00:10:54.030 --> 00:10:54.040 align:start position:0% contracts that know how to interact with 00:10:54.040 --> 00:10:56.879 align:start position:0% contracts that know how to interact with these<00:10:54.189> bridge<00:10:54.459> contracts<00:10:55.319> so<00:10:56.319> we<00:10:56.500> have<00:10:56.620> on<00:10:56.740> the 00:10:56.879 --> 00:10:56.889 align:start position:0% these bridge contracts so we have on the 00:10:56.889 --> 00:10:58.079 align:start position:0% these bridge contracts so we have on the left<00:10:57.069> side 00:10:58.079 --> 00:10:58.089 align:start position:0% left side 00:10:58.089 --> 00:10:59.879 align:start position:0% left side sending<00:10:58.720> contract<00:10:59.199> which<00:10:59.350> is<00:10:59.500> part<00:10:59.740> of<00:10:59.829> your 00:10:59.879 --> 00:10:59.889 align:start position:0% sending contract which is part of your 00:10:59.889 --> 00:11:04.170 align:start position:0% sending contract which is part of your DAP<00:11:00.189> it<00:11:01.180> has<00:11:01.389> some<00:11:01.689> function<00:11:02.230> and<00:11:02.639> on<00:11:03.639> the 00:11:04.170 --> 00:11:04.180 align:start position:0% DAP it has some function and on the 00:11:04.180 --> 00:11:05.600 align:start position:0% DAP it has some function and on the right<00:11:04.360> side<00:11:04.600> we<00:11:04.839> have 00:11:05.600 --> 00:11:05.610 align:start position:0% right side we have 00:11:05.610 --> 00:11:07.819 align:start position:0% right side we have on<00:11:05.670> the<00:11:05.970> sidechain<00:11:06.209> a<00:11:06.540> receiving<00:11:07.380> contract 00:11:07.819 --> 00:11:07.829 align:start position:0% on the sidechain a receiving contract 00:11:07.829 --> 00:11:10.120 align:start position:0% on the sidechain a receiving contract which<00:11:07.950> is<00:11:07.980> also<00:11:08.490> part<00:11:08.730> of<00:11:08.880> your<00:11:08.940> application 00:11:10.120 --> 00:11:10.130 align:start position:0% which is also part of your application 00:11:10.130 --> 00:11:13.449 align:start position:0% which is also part of your application and<00:11:11.130> which<00:11:11.310> has<00:11:11.459> a<00:11:11.490> function<00:11:11.940> accept<00:11:12.269> message 00:11:13.449 --> 00:11:13.459 align:start position:0% and which has a function accept message 00:11:13.459 --> 00:11:16.699 align:start position:0% and which has a function accept message now<00:11:14.459> we<00:11:15.209> also<00:11:15.360> have<00:11:15.839> bridge<00:11:16.079> authorities 00:11:16.699 --> 00:11:16.709 align:start position:0% now we also have bridge authorities 00:11:16.709 --> 00:11:19.130 align:start position:0% now we also have bridge authorities write<00:11:16.980> these<00:11:17.430> in<00:11:17.820> take<00:11:18.120> this<00:11:18.329> integral<00:11:18.690> part 00:11:19.130 --> 00:11:19.140 align:start position:0% write these in take this integral part 00:11:19.140 --> 00:11:21.259 align:start position:0% write these in take this integral part of<00:11:19.320> the<00:11:19.470> system<00:11:19.920> that<00:11:20.250> actually<00:11:20.310> facilitates 00:11:21.259 --> 00:11:21.269 align:start position:0% of the system that actually facilitates 00:11:21.269 --> 00:11:23.449 align:start position:0% of the system that actually facilitates the<00:11:21.779> message<00:11:22.200> relay<00:11:22.529> between<00:11:22.800> the<00:11:23.010> two<00:11:23.160> chains 00:11:23.449 --> 00:11:23.459 align:start position:0% the message relay between the two chains 00:11:23.459 --> 00:11:28.250 align:start position:0% the message relay between the two chains and<00:11:23.579> that<00:11:24.120> watches<00:11:24.750> both<00:11:24.990> chains<00:11:26.839> now<00:11:27.839> let's 00:11:28.250 --> 00:11:28.260 align:start position:0% and that watches both chains now let's 00:11:28.260 --> 00:11:31.699 align:start position:0% and that watches both chains now let's say<00:11:28.500> a<00:11:28.920> user<00:11:29.430> kicks<00:11:29.880> of<00:11:30.089> a<00:11:30.720> transaction<00:11:31.589> with 00:11:31.699 --> 00:11:31.709 align:start position:0% say a user kicks of a transaction with 00:11:31.709 --> 00:11:34.130 align:start position:0% say a user kicks of a transaction with your<00:11:31.860> application<00:11:32.550> it<00:11:33.029> called<00:11:33.360> some<00:11:33.660> function 00:11:34.130 --> 00:11:34.140 align:start position:0% your application it called some function 00:11:34.140 --> 00:11:36.590 align:start position:0% your application it called some function and<00:11:34.230> some<00:11:34.500> function<00:11:34.950> again<00:11:35.220> called<00:11:35.820> relay 00:11:36.590 --> 00:11:36.600 align:start position:0% and some function again called relay 00:11:36.600 --> 00:11:38.569 align:start position:0% and some function again called relay message<00:11:36.959> because<00:11:37.320> I<00:11:37.350> wants<00:11:37.769> to<00:11:37.860> send<00:11:38.100> over<00:11:38.279> a 00:11:38.569 --> 00:11:38.579 align:start position:0% message because I wants to send over a 00:11:38.579 --> 00:11:43.130 align:start position:0% message because I wants to send over a message<00:11:39.240> to<00:11:39.450> the<00:11:39.570> other<00:11:39.720> chain<00:11:41.810> that<00:11:42.810> again 00:11:43.130 --> 00:11:43.140 align:start position:0% message to the other chain that again 00:11:43.140 --> 00:11:45.410 align:start position:0% message to the other chain that again kicks<00:11:43.440> off<00:11:43.649> it<00:11:44.370> triggers<00:11:44.760> an<00:11:44.880> event<00:11:45.149> called 00:11:45.410 --> 00:11:45.420 align:start position:0% kicks off it triggers an event called 00:11:45.420 --> 00:11:47.960 align:start position:0% kicks off it triggers an event called relay<00:11:45.750> message<00:11:46.110> the<00:11:46.709> Bridge<00:11:46.920> Authority<00:11:46.970> see 00:11:47.960 --> 00:11:47.970 align:start position:0% relay message the Bridge Authority see 00:11:47.970 --> 00:11:51.199 align:start position:0% relay message the Bridge Authority see that<00:11:48.149> event<00:11:48.990> being<00:11:49.230> triggered<00:11:49.529> they<00:11:50.310> wait<00:11:51.180> a 00:11:51.199 --> 00:11:51.209 align:start position:0% that event being triggered they wait a 00:11:51.209 --> 00:11:53.720 align:start position:0% that event being triggered they wait a few<00:11:51.570> confirmations<00:11:52.350> because<00:11:53.220> they<00:11:53.430> want<00:11:53.640> to 00:11:53.720 --> 00:11:53.730 align:start position:0% few confirmations because they want to 00:11:53.730 --> 00:11:55.340 align:start position:0% few confirmations because they want to wait<00:11:53.910> until<00:11:54.329> they<00:11:54.480> have<00:11:54.600> a<00:11:54.630> higher<00:11:54.899> degree<00:11:55.110> of 00:11:55.340 --> 00:11:55.350 align:start position:0% wait until they have a higher degree of 00:11:55.350 --> 00:11:59.210 align:start position:0% wait until they have a higher degree of finality<00:11:56.480> right<00:11:57.480> because<00:11:57.990> the<00:11:58.380> main<00:11:58.649> ad<00:11:58.890> it 00:11:59.210 --> 00:11:59.220 align:start position:0% finality right because the main ad it 00:11:59.220 --> 00:12:01.280 align:start position:0% finality right because the main ad it has<00:11:59.490> only<00:11:59.640> probabilistic<00:12:00.209> finality<00:12:00.750> and<00:12:01.170> you 00:12:01.280 --> 00:12:01.290 align:start position:0% has only probabilistic finality and you 00:12:01.290 --> 00:12:03.680 align:start position:0% has only probabilistic finality and you really<00:12:01.649> don't<00:12:01.829> want<00:12:02.040> to<00:12:02.510> relay<00:12:03.510> a<00:12:03.540> message 00:12:03.680 --> 00:12:03.690 align:start position:0% really don't want to relay a message 00:12:03.690 --> 00:12:06.350 align:start position:0% really don't want to relay a message that<00:12:04.350> might<00:12:04.649> be<00:12:04.920> reverted<00:12:05.610> after<00:12:06.000> the<00:12:06.120> fact 00:12:06.350 --> 00:12:06.360 align:start position:0% that might be reverted after the fact 00:12:06.360 --> 00:12:10.400 align:start position:0% that might be reverted after the fact right<00:12:07.490> so<00:12:08.490> after<00:12:08.790> a<00:12:09.060> few<00:12:09.089> block<00:12:09.600> confirmations 00:12:10.400 --> 00:12:10.410 align:start position:0% right so after a few block confirmations 00:12:10.410 --> 00:12:13.850 align:start position:0% right so after a few block confirmations the<00:12:11.010> authorities<00:12:11.990> confirm<00:12:12.990> the<00:12:13.230> message<00:12:13.589> one 00:12:13.850 --> 00:12:13.860 align:start position:0% the authorities confirm the message one 00:12:13.860 --> 00:12:17.150 align:start position:0% the authorities confirm the message one by<00:12:14.040> one<00:12:14.310> on<00:12:14.579> the<00:12:15.269> other<00:12:15.390> chain<00:12:15.779> once<00:12:16.500> a<00:12:16.769> certain 00:12:17.150 --> 00:12:17.160 align:start position:0% by one on the other chain once a certain 00:12:17.160 --> 00:12:19.689 align:start position:0% by one on the other chain once a certain threshold<00:12:17.490> which<00:12:18.089> is<00:12:18.120> configurable<00:12:18.870> has<00:12:19.260> been 00:12:19.689 --> 00:12:19.699 align:start position:0% threshold which is configurable has been 00:12:19.699 --> 00:12:23.000 align:start position:0% threshold which is configurable has been achieved<00:12:21.170> another<00:12:22.170> event<00:12:22.709> is<00:12:22.829> triggered 00:12:23.000 --> 00:12:23.010 align:start position:0% achieved another event is triggered 00:12:23.010 --> 00:12:25.790 align:start position:0% achieved another event is triggered which<00:12:23.339> is<00:12:23.519> receive<00:12:23.880> message<00:12:24.300> and<00:12:24.540> then<00:12:25.110> this 00:12:25.790 --> 00:12:25.800 align:start position:0% which is receive message and then this 00:12:25.800 --> 00:12:27.939 align:start position:0% which is receive message and then this contract<00:12:26.339> the<00:12:26.820> bridge<00:12:27.000> contract<00:12:27.510> on-site 00:12:27.939 --> 00:12:27.949 align:start position:0% contract the bridge contract on-site 00:12:27.949 --> 00:12:31.519 align:start position:0% contract the bridge contract on-site chords<00:12:28.949> whatever<00:12:29.430> the<00:12:30.300> recipient<00:12:30.959> contract 00:12:31.519 --> 00:12:31.529 align:start position:0% chords whatever the recipient contract 00:12:31.529 --> 00:12:34.040 align:start position:0% chords whatever the recipient contract is<00:12:31.730> and<00:12:32.730> calls<00:12:33.060> a<00:12:33.180> function<00:12:33.540> called<00:12:33.720> accept 00:12:34.040 --> 00:12:34.050 align:start position:0% is and calls a function called accept 00:12:34.050 --> 00:12:37.550 align:start position:0% is and calls a function called accept message<00:12:34.410> there<00:12:34.649> that's<00:12:35.610> a<00:12:35.810> message<00:12:36.810> delivered 00:12:37.550 --> 00:12:37.560 align:start position:0% message there that's a message delivered 00:12:37.560 --> 00:12:43.970 align:start position:0% message there that's a message delivered and<00:12:37.800> it<00:12:38.490> there<00:12:39.269> can<00:12:39.449> be<00:12:42.110> whatever<00:12:43.110> transaction 00:12:43.970 --> 00:12:43.980 align:start position:0% and it there can be whatever transaction 00:12:43.980 --> 00:12:46.759 align:start position:0% and it there can be whatever transaction should<00:12:44.459> be<00:12:44.610> kicked<00:12:44.940> off<00:12:45.180> by<00:12:46.019> by<00:12:46.560> this 00:12:46.759 --> 00:12:46.769 align:start position:0% should be kicked off by by this 00:12:46.769 --> 00:12:48.829 align:start position:0% should be kicked off by by this interaction<00:12:47.190> can<00:12:47.459> be<00:12:47.640> kicked<00:12:47.850> off<00:12:48.029> by<00:12:48.420> accept 00:12:48.829 --> 00:12:48.839 align:start position:0% interaction can be kicked off by accept 00:12:48.839 --> 00:12:58.100 align:start position:0% interaction can be kicked off by accept message<00:12:49.140> sign<00:12:50.329> so<00:12:53.000> that's<00:12:54.000> add<00:12:55.490> the<00:12:57.110> message 00:12:58.100 --> 00:12:58.110 align:start position:0% message sign so that's add the message 00:12:58.110 --> 00:13:00.439 align:start position:0% message sign so that's add the message relay<00:12:58.350> the<00:12:58.949> other<00:12:59.100> way<00:12:59.310> around<00:12:59.370> from<00:12:59.970> site<00:13:00.240> or 00:13:00.439 --> 00:13:00.449 align:start position:0% relay the other way around from site or 00:13:00.449 --> 00:13:04.220 align:start position:0% relay the other way around from site or main<00:13:00.839> is<00:13:01.760> not<00:13:02.760> identical<00:13:03.540> to<00:13:03.570> this 00:13:04.220 --> 00:13:04.230 align:start position:0% main is not identical to this 00:13:04.230 --> 00:13:06.680 align:start position:0% main is not identical to this interaction<00:13:04.649> and<00:13:05.190> that<00:13:05.880> is<00:13:06.000> mainly<00:13:06.329> due<00:13:06.660> to 00:13:06.680 --> 00:13:06.690 align:start position:0% interaction and that is mainly due to 00:13:06.690 --> 00:13:09.019 align:start position:0% interaction and that is mainly due to the<00:13:06.959> reason<00:13:07.290> that<00:13:07.320> we<00:13:07.800> build<00:13:08.699> on<00:13:08.910> the 00:13:09.019 --> 00:13:09.029 align:start position:0% the reason that we build on the 00:13:09.029 --> 00:13:12.230 align:start position:0% the reason that we build on the assumption<00:13:09.660> that<00:13:10.760> transaction<00:13:11.760> costs<00:13:12.089> are 00:13:12.230 --> 00:13:12.240 align:start position:0% assumption that transaction costs are 00:13:12.240 --> 00:13:14.600 align:start position:0% assumption that transaction costs are significantly<00:13:13.170> higher<00:13:13.500> on<00:13:13.860> the<00:13:14.130> main<00:13:14.339> side 00:13:14.600 --> 00:13:14.610 align:start position:0% significantly higher on the main side 00:13:14.610 --> 00:13:18.079 align:start position:0% significantly higher on the main side than<00:13:15.449> the<00:13:15.930> side<00:13:16.170> side<00:13:16.470> and<00:13:16.709> that<00:13:17.160> means<00:13:17.459> you 00:13:18.079 --> 00:13:18.089 align:start position:0% than the side side and that means you 00:13:18.089 --> 00:13:19.430 align:start position:0% than the side side and that means you know<00:13:18.209> bridge<00:13:18.449> outside<00:13:18.690> is<00:13:19.110> real 00:13:19.430 --> 00:13:19.440 align:start position:0% know bridge outside is real 00:13:19.440 --> 00:13:21.260 align:start position:0% know bridge outside is real we<00:13:19.500> want<00:13:19.710> to<00:13:19.830> interact<00:13:20.190> as<00:13:20.490> little<00:13:21.120> as 00:13:21.260 --> 00:13:21.270 align:start position:0% we want to interact as little as 00:13:21.270 --> 00:13:24.100 align:start position:0% we want to interact as little as possible<00:13:21.870> with<00:13:22.230> the<00:13:22.710> main<00:13:22.920> blockchain<00:13:23.850> and 00:13:24.100 --> 00:13:24.110 align:start position:0% possible with the main blockchain and 00:13:24.110 --> 00:13:26.840 align:start position:0% possible with the main blockchain and like<00:13:25.110> gather<00:13:25.440> signatures<00:13:25.860> gather<00:13:26.550> these 00:13:26.840 --> 00:13:26.850 align:start position:0% like gather signatures gather these 00:13:26.850 --> 00:13:33.050 align:start position:0% like gather signatures gather these confirmations<00:13:27.600> on<00:13:28.560> the<00:13:28.860> side<00:13:29.070> chain<00:13:30.920> so<00:13:32.060> how 00:13:33.050 --> 00:13:33.060 align:start position:0% confirmations on the side chain so how 00:13:33.060 --> 00:13:36.830 align:start position:0% confirmations on the side chain so how can<00:13:33.690> you<00:13:34.050> utilize<00:13:34.440> it<00:13:34.950> as<00:13:35.300> the<00:13:36.300> app<00:13:36.360> developer 00:13:36.830 --> 00:13:36.840 align:start position:0% can you utilize it as the app developer 00:13:36.840 --> 00:13:40.210 align:start position:0% can you utilize it as the app developer like<00:13:37.620> what<00:13:37.950> do<00:13:38.040> you<00:13:38.160> have<00:13:38.370> change<00:13:38.610> them<00:13:38.820> and 00:13:40.210 --> 00:13:40.220 align:start position:0% like what do you have change them and 00:13:40.220 --> 00:13:43.460 align:start position:0% like what do you have change them and critically<00:13:41.220> there<00:13:41.580> are<00:13:41.760> two<00:13:42.150> interfaces<00:13:42.750> that 00:13:43.460 --> 00:13:43.470 align:start position:0% critically there are two interfaces that 00:13:43.470 --> 00:13:47.210 align:start position:0% critically there are two interfaces that you<00:13:43.650> need<00:13:43.830> to<00:13:43.920> be<00:13:44.040> aware<00:13:44.280> of<00:13:45.710> you<00:13:46.710> can<00:13:46.890> see<00:13:47.100> both 00:13:47.210 --> 00:13:47.220 align:start position:0% you need to be aware of you can see both 00:13:47.220 --> 00:13:49.850 align:start position:0% you need to be aware of you can see both here<00:13:47.520> one<00:13:48.270> allows<00:13:48.720> you<00:13:48.750> to<00:13:49.170> relay<00:13:49.710> a<00:13:49.740> message 00:13:49.850 --> 00:13:49.860 align:start position:0% here one allows you to relay a message 00:13:49.860 --> 00:13:52.850 align:start position:0% here one allows you to relay a message it<00:13:50.520> only<00:13:51.090> has<00:13:51.330> two<00:13:51.540> parameters<00:13:52.260> it's<00:13:52.470> a<00:13:52.650> data 00:13:52.850 --> 00:13:52.860 align:start position:0% it only has two parameters it's a data 00:13:52.860 --> 00:13:56.740 align:start position:0% it only has two parameters it's a data whatever<00:13:53.400> your<00:13:53.580> messages<00:13:54.440> as<00:13:55.440> well<00:13:56.040> as<00:13:56.250> a 00:13:56.740 --> 00:13:56.750 align:start position:0% whatever your messages as well as a 00:13:56.750 --> 00:13:59.900 align:start position:0% whatever your messages as well as a address<00:13:57.750> which<00:13:58.020> is<00:13:58.280> recipient<00:13:59.280> address<00:13:59.700> on 00:13:59.900 --> 00:13:59.910 align:start position:0% address which is recipient address on 00:13:59.910 --> 00:14:04.730 align:start position:0% address which is recipient address on the<00:14:00.060> other<00:14:00.210> chain<00:14:00.920> also<00:14:02.420> you<00:14:03.420> have<00:14:03.690> a<00:14:04.080> function 00:14:04.730 --> 00:14:04.740 align:start position:0% the other chain also you have a function 00:14:04.740 --> 00:14:07.130 align:start position:0% the other chain also you have a function called<00:14:04.770> accept<00:14:05.580> message<00:14:06.000> which<00:14:06.630> your 00:14:07.130 --> 00:14:07.140 align:start position:0% called accept message which your 00:14:07.140 --> 00:14:09.200 align:start position:0% called accept message which your recipient<00:14:07.830> contract<00:14:08.280> has<00:14:08.520> to<00:14:08.550> implement 00:14:09.200 --> 00:14:09.210 align:start position:0% recipient contract has to implement 00:14:09.210 --> 00:14:14.420 align:start position:0% recipient contract has to implement right<00:14:10.050> and<00:14:10.260> that's<00:14:11.250> it<00:14:12.650> one<00:14:13.650> thing<00:14:14.010> is<00:14:14.160> to<00:14:14.310> be 00:14:14.420 --> 00:14:14.430 align:start position:0% right and that's it one thing is to be 00:14:14.430 --> 00:14:16.730 align:start position:0% right and that's it one thing is to be noted<00:14:14.760> here<00:14:14.940> all<00:14:15.570> information<00:14:16.560> obviously 00:14:16.730 --> 00:14:16.740 align:start position:0% noted here all information obviously 00:14:16.740 --> 00:14:19.130 align:start position:0% noted here all information obviously needs<00:14:17.550> to<00:14:17.730> be<00:14:17.850> encoded<00:14:18.270> in<00:14:18.660> the<00:14:18.900> data 00:14:19.130 --> 00:14:19.140 align:start position:0% needs to be encoded in the data 00:14:19.140 --> 00:14:21.530 align:start position:0% needs to be encoded in the data parameter<00:14:19.830> and<00:14:20.040> the<00:14:20.490> recipient<00:14:21.060> contract 00:14:21.530 --> 00:14:21.540 align:start position:0% parameter and the recipient contract 00:14:21.540 --> 00:14:23.390 align:start position:0% parameter and the recipient contract needs<00:14:21.900> to<00:14:22.110> be<00:14:22.200> able<00:14:22.470> to<00:14:22.560> decode<00:14:23.070> that<00:14:23.130> message 00:14:23.390 --> 00:14:23.400 align:start position:0% needs to be able to decode that message 00:14:23.400 --> 00:14:26.300 align:start position:0% needs to be able to decode that message and<00:14:23.960> do<00:14:24.960> certain<00:14:25.350> actions<00:14:25.470> based<00:14:25.860> on<00:14:26.160> this 00:14:26.300 --> 00:14:26.310 align:start position:0% and do certain actions based on this 00:14:26.310 --> 00:14:31.700 align:start position:0% and do certain actions based on this degradation<00:14:28.430> now<00:14:29.430> I<00:14:30.200> brought<00:14:31.200> you<00:14:31.410> a<00:14:31.440> few 00:14:31.700 --> 00:14:31.710 align:start position:0% degradation now I brought you a few 00:14:31.710 --> 00:14:34.490 align:start position:0% degradation now I brought you a few examples<00:14:32.280> of<00:14:32.520> what<00:14:33.030> you<00:14:33.240> can<00:14:33.390> do<00:14:33.540> with<00:14:33.660> them<00:14:33.810> so 00:14:34.490 --> 00:14:34.500 align:start position:0% examples of what you can do with them so 00:14:34.500 --> 00:14:37.070 align:start position:0% examples of what you can do with them so for<00:14:34.920> example<00:14:35.340> you<00:14:35.490> can<00:14:35.640> use<00:14:35.910> to<00:14:36.390> build<00:14:36.540> an<00:14:36.810> ELC 00:14:37.070 --> 00:14:37.080 align:start position:0% for example you can use to build an ELC 00:14:37.080 --> 00:14:42.320 align:start position:0% for example you can use to build an ELC 22<00:14:37.650> s<00:14:37.770> and<00:14:38.130> C<00:14:38.430> 20<00:14:38.790> bridge<00:14:39.000> you<00:14:39.870> look<00:14:40.110> up<00:14:41.330> you 00:14:42.320 --> 00:14:42.330 align:start position:0% 22 s and C 20 bridge you look up you 00:14:42.330 --> 00:14:44.180 align:start position:0% 22 s and C 20 bridge you look up you build<00:14:42.510> for<00:14:42.990> example<00:14:43.020> let's<00:14:43.410> take<00:14:43.560> organ<00:14:43.980> as<00:14:44.070> an 00:14:44.180 --> 00:14:44.190 align:start position:0% build for example let's take organ as an 00:14:44.190 --> 00:14:48.080 align:start position:0% build for example let's take organ as an example<00:14:45.980> you<00:14:46.980> build<00:14:47.190> a<00:14:47.250> contract<00:14:47.700> that<00:14:47.820> allows 00:14:48.080 --> 00:14:48.090 align:start position:0% example you build a contract that allows 00:14:48.090 --> 00:14:52.010 align:start position:0% example you build a contract that allows you<00:14:48.390> to<00:14:48.510> lock<00:14:49.110> up<00:14:49.260> orca<00:14:49.620> on<00:14:49.910> IEP<00:14:50.910> on<00:14:51.120> the<00:14:51.840> main 00:14:52.010 --> 00:14:52.020 align:start position:0% you to lock up orca on IEP on the main 00:14:52.020 --> 00:14:55.250 align:start position:0% you to lock up orca on IEP on the main net<00:14:52.550> that<00:14:53.550> contract<00:14:54.420> sends<00:14:54.810> a<00:14:54.870> message 00:14:55.250 --> 00:14:55.260 align:start position:0% net that contract sends a message 00:14:55.260 --> 00:14:57.710 align:start position:0% net that contract sends a message through<00:14:55.920> the<00:14:55.980> purge<00:14:56.250> to<00:14:56.550> another<00:14:57.030> contract<00:14:57.570> on 00:14:57.710 --> 00:14:57.720 align:start position:0% through the purge to another contract on 00:14:57.720 --> 00:14:59.840 align:start position:0% through the purge to another contract on the<00:14:57.870> side<00:14:58.080> network<00:14:58.500> and<00:14:58.710> says<00:14:58.920> hey<00:14:59.190> you<00:14:59.430> know<00:14:59.640> a 00:14:59.840 --> 00:14:59.850 align:start position:0% the side network and says hey you know a 00:14:59.850 --> 00:15:03.320 align:start position:0% the side network and says hey you know a sign<00:15:00.390> that<00:15:00.690> many<00:15:01.140> or<00:15:01.500> got<00:15:01.770> oaken's<00:15:02.160> that<00:15:03.120> only 00:15:03.320 --> 00:15:03.330 align:start position:0% sign that many or got oaken's that only 00:15:03.330 --> 00:15:05.390 align:start position:0% sign that many or got oaken's that only live<00:15:03.600> on<00:15:03.780> the<00:15:03.900> side<00:15:04.080> network<00:15:04.440> to<00:15:04.800> this<00:15:04.950> person 00:15:05.390 --> 00:15:05.400 align:start position:0% live on the side network to this person 00:15:05.400 --> 00:15:06.650 align:start position:0% live on the side network to this person and<00:15:05.610> vice<00:15:06.180> versa 00:15:06.650 --> 00:15:06.660 align:start position:0% and vice versa 00:15:06.660 --> 00:15:08.960 align:start position:0% and vice versa pretty<00:15:06.990> straightforward<00:15:07.589> as<00:15:08.100> well<00:15:08.430> you<00:15:08.760> can 00:15:08.960 --> 00:15:08.970 align:start position:0% pretty straightforward as well you can 00:15:08.970 --> 00:15:11.510 align:start position:0% pretty straightforward as well you can do<00:15:09.089> that<00:15:09.120> with<00:15:09.540> native<00:15:09.900> currency<00:15:10.140> so<00:15:10.890> on<00:15:11.160> the 00:15:11.510 --> 00:15:11.520 align:start position:0% do that with native currency so on the 00:15:11.520 --> 00:15:14.030 align:start position:0% do that with native currency so on the manor<00:15:11.700> you<00:15:12.150> could<00:15:12.390> look<00:15:12.690> up<00:15:12.750> ether<00:15:13.500> on<00:15:13.740> one 00:15:14.030 --> 00:15:14.040 align:start position:0% manor you could look up ether on one 00:15:14.040 --> 00:15:17.090 align:start position:0% manor you could look up ether on one side<00:15:14.280> and<00:15:14.520> create<00:15:15.510> rapt<00:15:15.870> ether<00:15:16.140> on<00:15:16.560> the<00:15:16.950> other 00:15:17.090 --> 00:15:17.100 align:start position:0% side and create rapt ether on the other 00:15:17.100 --> 00:15:21.410 align:start position:0% side and create rapt ether on the other side<00:15:17.430> which<00:15:18.089> is<00:15:18.270> really<00:15:18.300> an<00:15:19.400> ESC<00:15:20.400> 20<00:15:20.970> token 00:15:21.410 --> 00:15:21.420 align:start position:0% side which is really an ESC 20 token 00:15:21.420 --> 00:15:23.960 align:start position:0% side which is really an ESC 20 token that<00:15:21.600> is<00:15:22.020> redeemable<00:15:22.710> for<00:15:23.160> one<00:15:23.370> ether<00:15:23.760> on<00:15:23.850> the 00:15:23.960 --> 00:15:23.970 align:start position:0% that is redeemable for one ether on the 00:15:23.970 --> 00:15:27.410 align:start position:0% that is redeemable for one ether on the main<00:15:24.120> network<00:15:24.510> and<00:15:25.610> the<00:15:26.610> last<00:15:26.820> example<00:15:27.060> I 00:15:27.410 --> 00:15:27.420 align:start position:0% main network and the last example I 00:15:27.420 --> 00:15:29.540 align:start position:0% main network and the last example I brought<00:15:27.690> here<00:15:27.930> and<00:15:28.110> that's<00:15:28.320> the<00:15:28.710> one<00:15:28.860> I'm<00:15:29.070> most 00:15:29.540 --> 00:15:29.550 align:start position:0% brought here and that's the one I'm most 00:15:29.550 --> 00:15:31.780 align:start position:0% brought here and that's the one I'm most excited<00:15:29.820> about<00:15:30.240> probably<00:15:31.080> in<00:15:31.260> the 00:15:31.780 --> 00:15:31.790 align:start position:0% excited about probably in the 00:15:31.790 --> 00:15:36.849 align:start position:0% excited about probably in the in<00:15:31.939> this<00:15:32.799> combination<00:15:33.799> here<00:15:34.429> is<00:15:34.629> that<00:15:35.649> you<00:15:36.649> can 00:15:36.849 --> 00:15:36.859 align:start position:0% in this combination here is that you can 00:15:36.859 --> 00:15:40.769 align:start position:0% in this combination here is that you can have<00:15:37.040> an<00:15:37.160> ESC<00:15:37.489> 20<00:15:37.970> token<00:15:38.389> on<00:15:38.569> the<00:15:39.019> main<00:15:39.199> network 00:15:40.769 --> 00:15:40.779 align:start position:0% have an ESC 20 token on the main network 00:15:40.779 --> 00:15:45.489 align:start position:0% have an ESC 20 token on the main network lock<00:15:41.779> it<00:15:41.929> up<00:15:42.079> and<00:15:42.319> then<00:15:43.569> if<00:15:44.569> the<00:15:44.839> user<00:15:44.869> whoever 00:15:45.489 --> 00:15:45.499 align:start position:0% lock it up and then if the user whoever 00:15:45.499 --> 00:15:48.909 align:start position:0% lock it up and then if the user whoever locked<00:15:45.739> it<00:15:45.980> up<00:15:46.149> native<00:15:47.149> currency<00:15:47.449> on<00:15:47.989> the<00:15:48.709> side 00:15:48.909 --> 00:15:48.919 align:start position:0% locked it up native currency on the side 00:15:48.919 --> 00:15:51.189 align:start position:0% locked it up native currency on the side network<00:15:49.309> and<00:15:49.549> that<00:15:50.119> really<00:15:50.509> means<00:15:50.779> you 00:15:51.189 --> 00:15:51.199 align:start position:0% network and that really means you 00:15:51.199 --> 00:15:53.919 align:start position:0% network and that really means you suddenly<00:15:51.589> can<00:15:51.889> have<00:15:52.129> a<00:15:52.329> stable<00:15:53.329> coin<00:15:53.660> peck 00:15:53.919 --> 00:15:53.929 align:start position:0% suddenly can have a stable coin peck 00:15:53.929 --> 00:15:56.409 align:start position:0% suddenly can have a stable coin peck native<00:15:54.319> currency<00:15:54.559> on<00:15:54.949> the<00:15:54.980> sidechain<00:15:55.419> right 00:15:56.409 --> 00:15:56.419 align:start position:0% native currency on the sidechain right 00:15:56.419 --> 00:16:00.789 align:start position:0% native currency on the sidechain right you<00:15:56.660> can<00:15:56.899> have<00:15:57.859> died<00:15:58.549> being<00:15:59.419> essentially<00:16:00.199> the 00:16:00.789 --> 00:16:00.799 align:start position:0% you can have died being essentially the 00:16:00.799 --> 00:16:03.009 align:start position:0% you can have died being essentially the currency<00:16:01.309> that<00:16:01.339> you<00:16:01.549> used<00:16:01.910> to<00:16:02.059> pay<00:16:02.239> for<00:16:02.480> gas<00:16:02.629> on 00:16:03.009 --> 00:16:03.019 align:start position:0% currency that you used to pay for gas on 00:16:03.019 --> 00:16:06.340 align:start position:0% currency that you used to pay for gas on your<00:16:03.769> side<00:16:03.980> network<00:16:04.399> and<00:16:04.660> if<00:16:05.660> you<00:16:05.929> combine 00:16:06.340 --> 00:16:06.350 align:start position:0% your side network and if you combine 00:16:06.350 --> 00:16:08.979 align:start position:0% your side network and if you combine that<00:16:06.379> for<00:16:06.949> example<00:16:07.220> R<00:16:07.399> is<00:16:07.609> fixed<00:16:07.999> gas<00:16:08.389> prices 00:16:08.979 --> 00:16:08.989 align:start position:0% that for example R is fixed gas prices 00:16:08.989 --> 00:16:11.849 align:start position:0% that for example R is fixed gas prices you<00:16:09.199> suddenly<00:16:09.889> have<00:16:10.429> a<00:16:10.459> situation<00:16:10.790> where 00:16:11.849 --> 00:16:11.859 align:start position:0% you suddenly have a situation where 00:16:11.859 --> 00:16:14.319 align:start position:0% you suddenly have a situation where those<00:16:12.859> people<00:16:13.279> that<00:16:13.399> run<00:16:13.639> dabs<00:16:13.939> are<00:16:14.149> those 00:16:14.319 --> 00:16:14.329 align:start position:0% those people that run dabs are those 00:16:14.329 --> 00:16:15.879 align:start position:0% those people that run dabs are those people<00:16:14.600> that<00:16:14.749> interact<00:16:14.989> with<00:16:15.350> stamps<00:16:15.739> on<00:16:15.859> your 00:16:15.879 --> 00:16:15.889 align:start position:0% people that interact with stamps on your 00:16:15.889 --> 00:16:19.419 align:start position:0% people that interact with stamps on your side<00:16:16.220> network<00:16:16.669> have<00:16:17.179> full<00:16:18.049> control<00:16:19.009> and<00:16:19.129> full 00:16:19.419 --> 00:16:19.429 align:start position:0% side network have full control and full 00:16:19.429 --> 00:16:21.939 align:start position:0% side network have full control and full understanding<00:16:20.059> of<00:16:20.179> what<00:16:20.239> their<00:16:21.199> transaction 00:16:21.939 --> 00:16:21.949 align:start position:0% understanding of what their transaction 00:16:21.949 --> 00:16:23.379 align:start position:0% understanding of what their transaction and<00:16:22.069> their<00:16:22.220> interactions<00:16:22.790> will<00:16:22.970> cost 00:16:23.379 --> 00:16:23.389 align:start position:0% and their interactions will cost 00:16:23.389 --> 00:16:27.280 align:start position:0% and their interactions will cost there<00:16:23.929> will<00:16:24.079> be<00:16:24.109> no<00:16:24.379> volatility<00:16:25.069> and<00:16:26.290> this 00:16:27.280 --> 00:16:27.290 align:start position:0% there will be no volatility and this 00:16:27.290 --> 00:16:29.879 align:start position:0% there will be no volatility and this last<00:16:27.529> part<00:16:27.679> really<00:16:28.279> was<00:16:28.459> made<00:16:28.669> possible<00:16:29.149> by 00:16:29.879 --> 00:16:29.889 align:start position:0% last part really was made possible by 00:16:29.889 --> 00:16:33.659 align:start position:0% last part really was made possible by something<00:16:30.889> we<00:16:31.730> called<00:16:32.029> la<00:16:32.299> cravat<00:16:32.689> contract 00:16:33.659 --> 00:16:33.669 align:start position:0% something we called la cravat contract 00:16:33.669 --> 00:16:37.840 align:start position:0% something we called la cravat contract which<00:16:34.669> allows<00:16:35.509> a<00:16:35.899> smart<00:16:36.470> contract<00:16:36.769> to<00:16:37.249> inform 00:16:37.840 --> 00:16:37.850 align:start position:0% which allows a smart contract to inform 00:16:37.850 --> 00:16:40.720 align:start position:0% which allows a smart contract to inform the<00:16:38.089> consensus<00:16:38.749> engine<00:16:39.230> how<00:16:39.709> many<00:16:39.980> new<00:16:40.249> tokens 00:16:40.720 --> 00:16:40.730 align:start position:0% the consensus engine how many new tokens 00:16:40.730 --> 00:16:42.369 align:start position:0% the consensus engine how many new tokens should<00:16:40.939> be<00:16:41.089> minted<00:16:41.449> and<00:16:41.660> who<00:16:41.809> they<00:16:42.019> should<00:16:42.079> be 00:16:42.369 --> 00:16:42.379 align:start position:0% should be minted and who they should be 00:16:42.379 --> 00:16:47.529 align:start position:0% should be minted and who they should be assigned<00:16:42.619> to<00:16:43.749> but<00:16:44.749> basically<00:16:45.619> the<00:16:46.539> options 00:16:47.529 --> 00:16:47.539 align:start position:0% assigned to but basically the options 00:16:47.539 --> 00:16:49.269 align:start position:0% assigned to but basically the options are<00:16:47.720> pretty<00:16:47.989> much<00:16:48.230> unlimited<00:16:48.559> of<00:16:48.949> what<00:16:49.160> you 00:16:49.269 --> 00:16:49.279 align:start position:0% are pretty much unlimited of what you 00:16:49.279 --> 00:16:50.979 align:start position:0% are pretty much unlimited of what you can<00:16:49.489> do<00:16:49.579> everything<00:16:49.970> you<00:16:50.179> can<00:16:50.480> write<00:16:50.720> in<00:16:50.899> a 00:16:50.979 --> 00:16:50.989 align:start position:0% can do everything you can write in a 00:16:50.989 --> 00:16:56.499 align:start position:0% can do everything you can write in a smart<00:16:51.230> contract<00:16:51.439> you<00:16:51.799> can<00:16:51.980> do<00:16:52.100> them<00:16:53.799> now<00:16:55.509> here 00:16:56.499 --> 00:16:56.509 align:start position:0% smart contract you can do them now here 00:16:56.509 --> 00:16:59.289 align:start position:0% smart contract you can do them now here a<00:16:56.539> few<00:16:56.899> of<00:16:57.079> the<00:16:57.199> projects<00:16:57.709> I've<00:16:58.299> personally 00:16:59.289 --> 00:16:59.299 align:start position:0% a few of the projects I've personally 00:16:59.299 --> 00:17:02.229 align:start position:0% a few of the projects I've personally talked<00:16:59.569> to<00:16:59.799> that<00:17:00.799> have<00:17:01.009> either<00:17:01.279> been<00:17:01.669> using 00:17:02.229 --> 00:17:02.239 align:start position:0% talked to that have either been using 00:17:02.239 --> 00:17:05.889 align:start position:0% talked to that have either been using the<00:17:02.329> parity<00:17:02.720> bridge<00:17:02.929> or<00:17:03.199> that<00:17:04.039> have<00:17:04.899> been 00:17:05.889 --> 00:17:05.899 align:start position:0% the parity bridge or that have been 00:17:05.899 --> 00:17:07.389 align:start position:0% the parity bridge or that have been waiting<00:17:06.289> for<00:17:06.319> the<00:17:06.620> arbitrary<00:17:07.069> message 00:17:07.389 --> 00:17:07.399 align:start position:0% waiting for the arbitrary message 00:17:07.399 --> 00:17:10.689 align:start position:0% waiting for the arbitrary message passing<00:17:07.699> in<00:17:08.000> order<00:17:08.389> to<00:17:08.569> you<00:17:09.049> know<00:17:09.459> split<00:17:10.459> up 00:17:10.689 --> 00:17:10.699 align:start position:0% passing in order to you know split up 00:17:10.699 --> 00:17:14.819 align:start position:0% passing in order to you know split up they're<00:17:10.880> there<00:17:11.059> between<00:17:11.240> multiple<00:17:11.779> chains 00:17:14.819 --> 00:17:14.829 align:start position:0% 00:17:14.829 --> 00:17:18.659 align:start position:0% now<00:17:15.829> as<00:17:16.220> always<00:17:17.120> there<00:17:17.600> are<00:17:17.720> certain<00:17:18.230> caveats 00:17:18.659 --> 00:17:18.669 align:start position:0% now as always there are certain caveats 00:17:18.669 --> 00:17:21.159 align:start position:0% now as always there are certain caveats with<00:17:19.669> this<00:17:19.850> approach<00:17:20.149> and<00:17:20.419> they<00:17:20.870> occurred 00:17:21.159 --> 00:17:21.169 align:start position:0% with this approach and they occurred 00:17:21.169 --> 00:17:22.689 align:start position:0% with this approach and they occurred certain<00:17:21.529> cave<00:17:21.709> reads<00:17:22.010> with<00:17:22.189> our<00:17:22.339> current 00:17:22.689 --> 00:17:22.699 align:start position:0% certain cave reads with our current 00:17:22.699 --> 00:17:25.059 align:start position:0% certain cave reads with our current implementation<00:17:22.939> that<00:17:23.569> I<00:17:23.630> don't<00:17:23.899> want<00:17:24.110> to<00:17:24.230> not 00:17:25.059 --> 00:17:25.069 align:start position:0% implementation that I don't want to not 00:17:25.069 --> 00:17:28.360 align:start position:0% implementation that I don't want to not talk<00:17:25.309> about<00:17:25.510> so<00:17:26.510> number<00:17:27.139> one<00:17:27.319> currently<00:17:28.069> all 00:17:28.360 --> 00:17:28.370 align:start position:0% talk about so number one currently all 00:17:28.370 --> 00:17:30.639 align:start position:0% talk about so number one currently all of<00:17:28.399> the<00:17:28.639> bridge<00:17:28.970> authorities<00:17:29.750> right<00:17:30.350> these 00:17:30.639 --> 00:17:30.649 align:start position:0% of the bridge authorities right these 00:17:30.649 --> 00:17:33.100 align:start position:0% of the bridge authorities right these authorities<00:17:31.279> that<00:17:31.519> relay<00:17:31.850> messages<00:17:32.110> should 00:17:33.100 --> 00:17:33.110 align:start position:0% authorities that relay messages should 00:17:33.110 --> 00:17:36.519 align:start position:0% authorities that relay messages should also<00:17:33.380> be<00:17:33.820> authorities<00:17:34.820> on<00:17:35.120> the<00:17:35.840> site<00:17:36.080> network 00:17:36.519 --> 00:17:36.529 align:start position:0% also be authorities on the site network 00:17:36.529 --> 00:17:38.529 align:start position:0% also be authorities on the site network so<00:17:36.860> they<00:17:37.250> should<00:17:37.580> be<00:17:37.610> the<00:17:37.909> validate<00:17:38.389> as<00:17:38.510> a 00:17:38.529 --> 00:17:38.539 align:start position:0% so they should be the validate as a 00:17:38.539 --> 00:17:41.289 align:start position:0% so they should be the validate as a block<00:17:38.899> producers<00:17:39.620> of<00:17:39.740> new<00:17:40.220> blocks<00:17:40.610> on<00:17:40.850> the 00:17:41.289 --> 00:17:41.299 align:start position:0% block producers of new blocks on the 00:17:41.299 --> 00:17:44.560 align:start position:0% block producers of new blocks on the side<00:17:41.510> chain<00:17:41.740> that<00:17:42.740> is<00:17:42.980> because 00:17:44.560 --> 00:17:44.570 align:start position:0% side chain that is because 00:17:44.570 --> 00:17:47.080 align:start position:0% side chain that is because currently<00:17:45.559> the<00:17:45.889> system<00:17:46.070> is<00:17:46.370> designed<00:17:46.759> so<00:17:47.059> that 00:17:47.080 --> 00:17:47.090 align:start position:0% currently the system is designed so that 00:17:47.090 --> 00:17:49.299 align:start position:0% currently the system is designed so that most<00:17:47.600> transactions<00:17:48.470> that<00:17:48.590> happen<00:17:48.919> on<00:17:49.039> chain 00:17:49.299 --> 00:17:49.309 align:start position:0% most transactions that happen on chain 00:17:49.309 --> 00:17:51.850 align:start position:0% most transactions that happen on chain happen<00:17:49.759> on<00:17:50.000> the<00:17:50.389> site<00:17:50.600> network<00:17:51.019> and<00:17:51.230> you<00:17:51.649> don't 00:17:51.850 --> 00:17:51.860 align:start position:0% happen on the site network and you don't 00:17:51.860 --> 00:17:53.740 align:start position:0% happen on the site network and you don't want<00:17:52.130> the<00:17:52.250> authorities<00:17:52.370> to<00:17:53.059> have<00:17:53.179> to<00:17:53.330> pay<00:17:53.509> for 00:17:53.740 --> 00:17:53.750 align:start position:0% want the authorities to have to pay for 00:17:53.750 --> 00:17:56.049 align:start position:0% want the authorities to have to pay for these<00:17:54.019> transactions<00:17:54.679> right<00:17:55.190> for<00:17:55.940> both 00:17:56.049 --> 00:17:56.059 align:start position:0% these transactions right for both 00:17:56.059 --> 00:17:59.249 align:start position:0% these transactions right for both reasons<00:17:56.330> spam<00:17:56.750> protection<00:17:57.409> as<00:17:57.529> well<00:17:57.980> as<00:17:58.070> cost 00:17:59.249 --> 00:17:59.259 align:start position:0% reasons spam protection as well as cost 00:17:59.259 --> 00:18:02.740 align:start position:0% reasons spam protection as well as cost but<00:18:00.259> if<00:18:01.159> the<00:18:01.639> British<00:18:01.789> authorities<00:18:02.000> happened 00:18:02.740 --> 00:18:02.750 align:start position:0% but if the British authorities happened 00:18:02.750 --> 00:18:04.690 align:start position:0% but if the British authorities happened to<00:18:02.840> be<00:18:02.990> the<00:18:03.139> POA<00:18:03.440> or<00:18:03.740> authorities<00:18:04.190> on<00:18:04.370> the<00:18:04.490> site 00:18:04.690 --> 00:18:04.700 align:start position:0% to be the POA or authorities on the site 00:18:04.700 --> 00:18:06.759 align:start position:0% to be the POA or authorities on the site network<00:18:05.149> they<00:18:05.720> don't<00:18:05.929> have<00:18:06.139> to<00:18:06.320> pay<00:18:06.470> for<00:18:06.529> the 00:18:06.759 --> 00:18:06.769 align:start position:0% network they don't have to pay for the 00:18:06.769 --> 00:18:08.019 align:start position:0% network they don't have to pay for the transaction<00:18:07.340> that<00:18:07.429> they<00:18:07.549> put<00:18:07.730> in<00:18:07.880> their 00:18:08.019 --> 00:18:08.029 align:start position:0% transaction that they put in their 00:18:08.029 --> 00:18:11.409 align:start position:0% transaction that they put in their blocks<00:18:08.330> so<00:18:09.200> that<00:18:09.679> works<00:18:09.919> pretty<00:18:10.130> well<00:18:10.250> in<00:18:10.700> my 00:18:11.409 --> 00:18:11.419 align:start position:0% blocks so that works pretty well in my 00:18:11.419 --> 00:18:14.049 align:start position:0% blocks so that works pretty well in my opinion<00:18:11.990> it<00:18:12.289> also<00:18:12.649> works<00:18:13.130> pretty<00:18:13.429> well<00:18:13.580> with 00:18:14.049 --> 00:18:14.059 align:start position:0% opinion it also works pretty well with 00:18:14.059 --> 00:18:16.149 align:start position:0% opinion it also works pretty well with the<00:18:14.240> trust<00:18:14.570> model<00:18:14.899> that<00:18:15.259> you<00:18:15.440> have<00:18:15.649> to<00:18:15.830> assume 00:18:16.149 --> 00:18:16.159 align:start position:0% the trust model that you have to assume 00:18:16.159 --> 00:18:19.600 align:start position:0% the trust model that you have to assume around<00:18:17.059> this<00:18:17.960> application<00:18:18.590> because<00:18:19.279> you<00:18:19.309> know 00:18:19.600 --> 00:18:19.610 align:start position:0% around this application because you know 00:18:19.610 --> 00:18:22.389 align:start position:0% around this application because you know after<00:18:20.240> all<00:18:20.269> if<00:18:20.570> you<00:18:20.720> don't<00:18:20.929> trust<00:18:21.769> the 00:18:22.389 --> 00:18:22.399 align:start position:0% after all if you don't trust the 00:18:22.399 --> 00:18:25.240 align:start position:0% after all if you don't trust the authorities<00:18:23.059> on<00:18:23.330> your<00:18:23.870> site<00:18:24.169> network<00:18:24.649> you 00:18:25.240 --> 00:18:25.250 align:start position:0% authorities on your site network you 00:18:25.250 --> 00:18:29.470 align:start position:0% authorities on your site network you know<00:18:25.870> truthfully<00:18:26.870> maintain<00:18:27.909> integrity<00:18:28.909> of 00:18:29.470 --> 00:18:29.480 align:start position:0% know truthfully maintain integrity of 00:18:29.480 --> 00:18:32.639 align:start position:0% know truthfully maintain integrity of this<00:18:29.960> side<00:18:30.590> chain<00:18:30.889> right<00:18:31.190> then<00:18:31.759> you<00:18:32.029> also 00:18:32.639 --> 00:18:32.649 align:start position:0% this side chain right then you also 00:18:32.649 --> 00:18:35.560 align:start position:0% this side chain right then you also wouldn't<00:18:33.649> want<00:18:33.889> to<00:18:33.980> trust<00:18:34.250> a<00:18:34.879> bridge<00:18:35.539> that 00:18:35.560 --> 00:18:35.570 align:start position:0% wouldn't want to trust a bridge that 00:18:35.570 --> 00:18:39.450 align:start position:0% wouldn't want to trust a bridge that relays<00:18:36.500> messages<00:18:37.070> through<00:18:37.279> this<00:18:37.399> chain<00:18:38.379> right 00:18:39.450 --> 00:18:39.460 align:start position:0% relays messages through this chain right 00:18:39.460 --> 00:18:41.950 align:start position:0% relays messages through this chain right another<00:18:40.460> one<00:18:40.700> currently<00:18:41.240> the<00:18:41.480> spiritual 00:18:41.950 --> 00:18:41.960 align:start position:0% another one currently the spiritual 00:18:41.960 --> 00:18:44.320 align:start position:0% another one currently the spiritual authority<00:18:42.019> set<00:18:42.559> is<00:18:42.799> immutable<00:18:43.279> right<00:18:43.789> it's 00:18:44.320 --> 00:18:44.330 align:start position:0% authority set is immutable right it's 00:18:44.330 --> 00:18:48.279 align:start position:0% authority set is immutable right it's very<00:18:44.539> trivial<00:18:45.440> to<00:18:45.649> change<00:18:45.980> that<00:18:46.840> we<00:18:47.840> can<00:18:48.049> just 00:18:48.279 --> 00:18:48.289 align:start position:0% very trivial to change that we can just 00:18:48.289 --> 00:18:50.649 align:start position:0% very trivial to change that we can just add<00:18:48.529> another<00:18:49.190> contract<00:18:50.120> logic<00:18:50.480> that<00:18:50.600> allows 00:18:50.649 --> 00:18:50.659 align:start position:0% add another contract logic that allows 00:18:50.659 --> 00:18:53.200 align:start position:0% add another contract logic that allows you<00:18:51.230> to<00:18:51.679> have<00:18:51.860> a<00:18:51.889> majority<00:18:52.279> vote<00:18:52.700> and<00:18:53.029> vote<00:18:53.179> a 00:18:53.200 --> 00:18:53.210 align:start position:0% you to have a majority vote and vote a 00:18:53.210 --> 00:18:56.019 align:start position:0% you to have a majority vote and vote a bridge<00:18:53.600> authority<00:18:53.840> in<00:18:54.350> or<00:18:54.529> out<00:18:54.700> however<00:18:55.700> you 00:18:56.019 --> 00:18:56.029 align:start position:0% bridge authority in or out however you 00:18:56.029 --> 00:18:58.119 align:start position:0% bridge authority in or out however you want<00:18:56.299> or<00:18:56.539> add<00:18:56.960> whatever<00:18:57.259> it's<00:18:57.649> governance 00:18:58.119 --> 00:18:58.129 align:start position:0% want or add whatever it's governance 00:18:58.129 --> 00:19:02.230 align:start position:0% want or add whatever it's governance mechanism<00:18:58.669> you<00:18:58.759> want<00:18:59.500> last<00:19:00.500> but<00:19:00.710> not<00:19:00.860> least<00:19:01.240> if 00:19:02.230 --> 00:19:02.240 align:start position:0% mechanism you want last but not least if 00:19:02.240 --> 00:19:05.499 align:start position:0% mechanism you want last but not least if you<00:19:03.279> connect<00:19:04.279> two<00:19:04.549> chains<00:19:04.909> and<00:19:05.120> one<00:19:05.299> of<00:19:05.389> the 00:19:05.499 --> 00:19:05.509 align:start position:0% you connect two chains and one of the 00:19:05.509 --> 00:19:08.730 align:start position:0% you connect two chains and one of the chains<00:19:05.809> is<00:19:06.049> a<00:19:06.080> proof-of-work<00:19:06.710> network<00:19:07.610> then 00:19:08.730 --> 00:19:08.740 align:start position:0% chains is a proof-of-work network then 00:19:08.740 --> 00:19:12.639 align:start position:0% chains is a proof-of-work network then unfortunately<00:19:09.740> you<00:19:10.490> are<00:19:10.940> facing<00:19:11.870> the<00:19:12.500> problem 00:19:12.639 --> 00:19:12.649 align:start position:0% unfortunately you are facing the problem 00:19:12.649 --> 00:19:14.320 align:start position:0% unfortunately you are facing the problem that<00:19:13.009> you<00:19:13.129> don't<00:19:13.279> have<00:19:13.549> deterministic 00:19:14.320 --> 00:19:14.330 align:start position:0% that you don't have deterministic 00:19:14.330 --> 00:19:17.399 align:start position:0% that you don't have deterministic finality<00:19:14.659> which<00:19:15.440> means<00:19:15.769> if<00:19:16.039> you<00:19:16.850> want<00:19:16.879> to<00:19:17.149> be 00:19:17.399 --> 00:19:17.409 align:start position:0% finality which means if you want to be 00:19:17.409 --> 00:19:20.200 align:start position:0% finality which means if you want to be fairly<00:19:18.409> sure<00:19:18.860> that<00:19:19.250> nothing<00:19:20.059> is<00:19:20.179> being 00:19:20.200 --> 00:19:20.210 align:start position:0% fairly sure that nothing is being 00:19:20.210 --> 00:19:22.389 align:start position:0% fairly sure that nothing is being reverted<00:19:20.960> you<00:19:20.990> want<00:19:21.350> a<00:19:21.440> very<00:19:21.590> weight<00:19:21.889> of<00:19:22.129> huge 00:19:22.389 --> 00:19:22.399 align:start position:0% reverted you want a very weight of huge 00:19:22.399 --> 00:19:25.389 align:start position:0% reverted you want a very weight of huge transactions<00:19:23.059> and<00:19:23.240> that<00:19:23.929> introduces<00:19:24.379> lesson 00:19:25.389 --> 00:19:25.399 align:start position:0% transactions and that introduces lesson 00:19:25.399 --> 00:19:27.970 align:start position:0% transactions and that introduces lesson let<00:19:25.789> and<00:19:25.940> see<00:19:26.120> that<00:19:26.330> we<00:19:26.480> don't<00:19:26.659> want<00:19:26.899> that<00:19:27.529> sad 00:19:27.970 --> 00:19:27.980 align:start position:0% let and see that we don't want that sad 00:19:27.980 --> 00:19:31.049 align:start position:0% let and see that we don't want that sad if<00:19:28.750> you've<00:19:29.750> got<00:19:29.990> two<00:19:30.259> networks<00:19:30.710> that<00:19:30.860> have 00:19:31.049 --> 00:19:31.059 align:start position:0% if you've got two networks that have 00:19:31.059 --> 00:19:33.930 align:start position:0% if you've got two networks that have deterministic<00:19:32.059> finality<00:19:32.419> there's<00:19:33.200> really<00:19:33.440> no 00:19:33.930 --> 00:19:33.940 align:start position:0% deterministic finality there's really no 00:19:33.940 --> 00:19:37.749 align:start position:0% deterministic finality there's really no no<00:19:35.200> reason<00:19:36.200> to<00:19:36.350> wait<00:19:36.529> longer<00:19:36.830> than<00:19:36.980> ones 00:19:37.749 --> 00:19:37.759 align:start position:0% no reason to wait longer than ones 00:19:37.759 --> 00:19:41.730 align:start position:0% no reason to wait longer than ones finality<00:19:38.629> has<00:19:38.779> been<00:19:39.080> achieved<00:19:39.500> on<00:19:39.710> any<00:19:39.950> block 00:19:41.730 --> 00:19:41.740 align:start position:0% finality has been achieved on any block 00:19:41.740 --> 00:19:45.759 align:start position:0% finality has been achieved on any block last<00:19:42.740> but<00:19:42.919> not<00:19:43.039> least<00:19:44.379> there's<00:19:45.379> a<00:19:45.470> very 00:19:45.759 --> 00:19:45.769 align:start position:0% last but not least there's a very 00:19:45.769 --> 00:19:48.639 align:start position:0% last but not least there's a very important<00:19:46.460> note<00:19:46.909> of<00:19:46.940> caution<00:19:47.360> here<00:19:47.840> the 00:19:48.639 --> 00:19:48.649 align:start position:0% important note of caution here the 00:19:48.649 --> 00:19:50.980 align:start position:0% important note of caution here the contracts<00:19:49.309> I've<00:19:49.700> been<00:19:49.940> talking<00:19:50.269> about<00:19:50.389> here 00:19:50.980 --> 00:19:50.990 align:start position:0% contracts I've been talking about here 00:19:50.990 --> 00:19:54.340 align:start position:0% contracts I've been talking about here they<00:19:51.470> haven't<00:19:51.649> been<00:19:51.860> audited<00:19:52.340> yet<00:19:52.570> so<00:19:53.570> please 00:19:54.340 --> 00:19:54.350 align:start position:0% they haven't been audited yet so please 00:19:54.350 --> 00:19:56.680 align:start position:0% they haven't been audited yet so please use<00:19:54.679> with<00:19:54.889> caution<00:19:55.129> they<00:19:55.789> in<00:19:55.940> an<00:19:56.120> alpha<00:19:56.510> phase 00:19:56.680 --> 00:19:56.690 align:start position:0% use with caution they in an alpha phase 00:19:56.690 --> 00:19:59.860 align:start position:0% use with caution they in an alpha phase right 00:19:59.860 --> 00:19:59.870 align:start position:0% 00:19:59.870 --> 00:20:05.900 align:start position:0% so<00:20:00.870> further<00:20:01.380> challenges<00:20:04.460> transactions<00:20:05.460> on 00:20:05.900 --> 00:20:05.910 align:start position:0% so further challenges transactions on 00:20:05.910 --> 00:20:09.560 align:start position:0% so further challenges transactions on Maynard<00:20:06.390> are<00:20:06.690> very<00:20:06.960> expensive<00:20:07.320> right<00:20:07.940> so<00:20:08.940> if 00:20:09.560 --> 00:20:09.570 align:start position:0% Maynard are very expensive right so if 00:20:09.570 --> 00:20:11.870 align:start position:0% Maynard are very expensive right so if you<00:20:09.840> relay<00:20:10.200> a<00:20:10.230> transaction<00:20:10.980> from<00:20:11.520> the<00:20:11.670> side 00:20:11.870 --> 00:20:11.880 align:start position:0% you relay a transaction from the side 00:20:11.880 --> 00:20:14.000 align:start position:0% you relay a transaction from the side network<00:20:12.300> back<00:20:12.630> to<00:20:12.810> the<00:20:12.930> main<00:20:13.080> network<00:20:13.440> then 00:20:14.000 --> 00:20:14.010 align:start position:0% network back to the main network then 00:20:14.010 --> 00:20:17.120 align:start position:0% network back to the main network then you<00:20:14.580> need<00:20:14.730> at<00:20:14.910> least<00:20:14.940> one<00:20:15.900> transaction<00:20:16.410> to<00:20:16.980> be 00:20:17.120 --> 00:20:17.130 align:start position:0% you need at least one transaction to be 00:20:17.130 --> 00:20:19.220 align:start position:0% you need at least one transaction to be made<00:20:17.280> by<00:20:17.490> authorities<00:20:18.060> and<00:20:18.240> that's<00:20:18.840> the 00:20:19.220 --> 00:20:19.230 align:start position:0% made by authorities and that's the 00:20:19.230 --> 00:20:20.750 align:start position:0% made by authorities and that's the transaction<00:20:19.830> that<00:20:20.010> actually<00:20:20.370> relays<00:20:20.730> a 00:20:20.750 --> 00:20:20.760 align:start position:0% transaction that actually relays a 00:20:20.760 --> 00:20:24.470 align:start position:0% transaction that actually relays a message<00:20:21.240> right<00:20:21.540> so<00:20:22.320> now<00:20:22.980> who<00:20:23.610> should<00:20:23.910> pay<00:20:24.120> for 00:20:24.470 --> 00:20:24.480 align:start position:0% message right so now who should pay for 00:20:24.480 --> 00:20:27.170 align:start position:0% message right so now who should pay for that<00:20:24.570> transaction<00:20:25.130> that's<00:20:26.130> still<00:20:26.520> a<00:20:26.790> problem 00:20:27.170 --> 00:20:27.180 align:start position:0% that transaction that's still a problem 00:20:27.180 --> 00:20:31.790 align:start position:0% that transaction that's still a problem we<00:20:27.450> are<00:20:27.480> facing<00:20:27.750> I<00:20:28.400> believe<00:20:29.400> in<00:20:29.700> most<00:20:29.940> cases<00:20:30.800> it 00:20:31.790 --> 00:20:31.800 align:start position:0% we are facing I believe in most cases it 00:20:31.800 --> 00:20:33.020 align:start position:0% we are facing I believe in most cases it won't<00:20:31.980> be<00:20:32.190> a<00:20:32.220> big<00:20:32.460> problem 00:20:33.020 --> 00:20:33.030 align:start position:0% won't be a big problem 00:20:33.030 --> 00:20:36.650 align:start position:0% won't be a big problem because<00:20:33.420> the<00:20:34.640> application<00:20:35.640> that<00:20:35.910> decides<00:20:36.360> to 00:20:36.650 --> 00:20:36.660 align:start position:0% because the application that decides to 00:20:36.660 --> 00:20:38.240 align:start position:0% because the application that decides to implement<00:20:36.810> the<00:20:37.290> site<00:20:37.530> network<00:20:37.950> and<00:20:38.100> to 00:20:38.240 --> 00:20:38.250 align:start position:0% implement the site network and to 00:20:38.250 --> 00:20:40.490 align:start position:0% implement the site network and to utilize<00:20:38.460> the<00:20:38.910> bridge<00:20:39.150> has<00:20:39.690> an<00:20:39.870> intrinsic 00:20:40.490 --> 00:20:40.500 align:start position:0% utilize the bridge has an intrinsic 00:20:40.500 --> 00:20:44.800 align:start position:0% utilize the bridge has an intrinsic motivation<00:20:41.430> to<00:20:41.820> pay<00:20:42.000> for<00:20:42.360> these<00:20:42.510> transactions 00:20:44.800 --> 00:20:44.810 align:start position:0% motivation to pay for these transactions 00:20:44.810 --> 00:20:48.170 align:start position:0% motivation to pay for these transactions because<00:20:45.810> it<00:20:46.200> obviously<00:20:46.820> increases<00:20:47.820> the<00:20:47.880> value 00:20:48.170 --> 00:20:48.180 align:start position:0% because it obviously increases the value 00:20:48.180 --> 00:20:50.030 align:start position:0% because it obviously increases the value of<00:20:48.270> the<00:20:48.420> network<00:20:48.600> the<00:20:49.170> overall<00:20:49.530> network<00:20:49.890> and 00:20:50.030 --> 00:20:50.040 align:start position:0% of the network the overall network and 00:20:50.040 --> 00:20:56.350 align:start position:0% of the network the overall network and its<00:20:51.170> application<00:20:53.210> second<00:20:54.410> what<00:20:55.410> happens<00:20:55.800> when 00:20:56.350 --> 00:20:56.360 align:start position:0% its application second what happens when 00:20:56.360 --> 00:20:59.450 align:start position:0% its application second what happens when relay<00:20:57.360> message<00:20:57.780> kicks<00:20:58.410> off<00:20:58.590> a<00:20:58.800> transaction 00:20:59.450 --> 00:20:59.460 align:start position:0% relay message kicks off a transaction 00:20:59.460 --> 00:21:02.180 align:start position:0% relay message kicks off a transaction that<00:20:59.640> actually<00:20:59.970> runs<00:21:00.210> out<00:21:00.360> of<00:21:00.390> gas<00:21:00.720> right<00:21:01.230> like 00:21:02.180 --> 00:21:02.190 align:start position:0% that actually runs out of gas right like 00:21:02.190 --> 00:21:05.360 align:start position:0% that actually runs out of gas right like we<00:21:02.400> are<00:21:02.520> facing<00:21:02.730> a<00:21:03.180> more<00:21:03.540> acing<00:21:04.370> situation 00:21:05.360 --> 00:21:05.370 align:start position:0% we are facing a more acing situation 00:21:05.370 --> 00:21:08.320 align:start position:0% we are facing a more acing situation here<00:21:05.580> and<00:21:05.730> that's<00:21:06.300> not<00:21:06.720> trivial<00:21:07.020> at<00:21:07.290> all<00:21:07.410> to<00:21:07.770> to 00:21:08.320 --> 00:21:08.330 align:start position:0% here and that's not trivial at all to to 00:21:08.330 --> 00:21:12.740 align:start position:0% here and that's not trivial at all to to mitigate<00:21:09.890> another<00:21:10.890> thing<00:21:11.640> that<00:21:11.910> shouldn't<00:21:12.600> be 00:21:12.740 --> 00:21:12.750 align:start position:0% mitigate another thing that shouldn't be 00:21:12.750 --> 00:21:15.920 align:start position:0% mitigate another thing that shouldn't be unnoted<00:21:13.560> is<00:21:13.830> that<00:21:14.640> there<00:21:15.330> is<00:21:15.450> still<00:21:15.660> missing 00:21:15.920 --> 00:21:15.930 align:start position:0% unnoted is that there is still missing 00:21:15.930 --> 00:21:18.380 align:start position:0% unnoted is that there is still missing tooling<00:21:16.470> for<00:21:16.500> side-chains<00:21:17.130> right<00:21:17.610> even 00:21:18.380 --> 00:21:18.390 align:start position:0% tooling for side-chains right even 00:21:18.390 --> 00:21:20.780 align:start position:0% tooling for side-chains right even though<00:21:18.570> we<00:21:18.870> finally<00:21:19.770> have<00:21:19.980> an<00:21:20.160> open-source 00:21:20.780 --> 00:21:20.790 align:start position:0% though we finally have an open-source 00:21:20.790 --> 00:21:22.670 align:start position:0% though we finally have an open-source blockchain<00:21:21.270> Explorer<00:21:21.660> which<00:21:21.990> is<00:21:22.020> absolutely 00:21:22.670 --> 00:21:22.680 align:start position:0% blockchain Explorer which is absolutely 00:21:22.680 --> 00:21:24.710 align:start position:0% blockchain Explorer which is absolutely fantastic<00:21:22.890> right<00:21:23.580> which<00:21:24.030> you<00:21:24.060> can<00:21:24.330> spin<00:21:24.570> up 00:21:24.710 --> 00:21:24.720 align:start position:0% fantastic right which you can spin up 00:21:24.720 --> 00:21:27.500 align:start position:0% fantastic right which you can spin up for<00:21:24.930> your<00:21:25.050> site<00:21:25.290> Network<00:21:25.940> we've<00:21:26.940> still<00:21:27.240> met 00:21:27.500 --> 00:21:27.510 align:start position:0% for your site Network we've still met 00:21:27.510 --> 00:21:30.650 align:start position:0% for your site Network we've still met miss<00:21:28.290> madam<00:21:28.800> asked<00:21:29.010> and<00:21:29.460> if<00:21:29.580> here<00:21:29.940> and<00:21:30.480> other 00:21:30.650 --> 00:21:30.660 align:start position:0% miss madam asked and if here and other 00:21:30.660 --> 00:21:33.170 align:start position:0% miss madam asked and if here and other kind<00:21:30.960> of<00:21:31.080> things<00:21:31.350> that<00:21:31.440> we<00:21:31.710> usually<00:21:32.160> want<00:21:32.760> in 00:21:33.170 --> 00:21:33.180 align:start position:0% kind of things that we usually want in 00:21:33.180 --> 00:21:39.550 align:start position:0% kind of things that we usually want in order<00:21:33.600> to<00:21:33.810> effectively<00:21:34.770> build<00:21:35.130> on<00:21:35.310> a<00:21:35.340> network 00:21:39.550 --> 00:21:39.560 align:start position:0% 00:21:39.560 --> 00:21:41.930 align:start position:0% last<00:21:40.560> but<00:21:40.740> not<00:21:40.860> least<00:21:41.100> there<00:21:41.550> are<00:21:41.610> UX 00:21:41.930 --> 00:21:41.940 align:start position:0% last but not least there are UX 00:21:41.940 --> 00:21:43.730 align:start position:0% last but not least there are UX considerations<00:21:42.810> that<00:21:43.140> you<00:21:43.260> have<00:21:43.410> to<00:21:43.560> take 00:21:43.730 --> 00:21:43.740 align:start position:0% considerations that you have to take 00:21:43.740 --> 00:21:45.290 align:start position:0% considerations that you have to take into<00:21:43.920> account<00:21:44.010> when<00:21:44.460> you<00:21:44.580> follow<00:21:45.120> this 00:21:45.290 --> 00:21:45.300 align:start position:0% into account when you follow this 00:21:45.300 --> 00:21:48.500 align:start position:0% into account when you follow this approach<00:21:45.860> for<00:21:46.860> example<00:21:47.010> you<00:21:47.850> might<00:21:48.030> end<00:21:48.270> up<00:21:48.360> in 00:21:48.500 --> 00:21:48.510 align:start position:0% approach for example you might end up in 00:21:48.510 --> 00:21:50.720 align:start position:0% approach for example you might end up in a<00:21:48.600> situation<00:21:48.840> where<00:21:49.320> the<00:21:49.920> user<00:21:50.220> that 00:21:50.720 --> 00:21:50.730 align:start position:0% a situation where the user that 00:21:50.730 --> 00:21:52.400 align:start position:0% a situation where the user that interacts<00:21:51.210> with<00:21:51.240> adapt<00:21:51.630> has<00:21:51.840> to<00:21:52.140> switch 00:21:52.400 --> 00:21:52.410 align:start position:0% interacts with adapt has to switch 00:21:52.410 --> 00:21:54.760 align:start position:0% interacts with adapt has to switch between<00:21:52.590> networks<00:21:53.250> which<00:21:53.700> is<00:21:53.730> not<00:21:54.090> quite<00:21:54.360> nice 00:21:54.760 --> 00:21:54.770 align:start position:0% between networks which is not quite nice 00:21:54.770 --> 00:21:58.430 align:start position:0% between networks which is not quite nice also<00:21:55.770> the<00:21:56.670> user<00:21:56.880> might<00:21:57.210> have<00:21:57.420> to<00:21:57.600> own<00:21:57.780> native 00:21:58.430 --> 00:21:58.440 align:start position:0% also the user might have to own native 00:21:58.440 --> 00:22:02.780 align:start position:0% also the user might have to own native currencies<00:21:59.100> on<00:21:59.280> both<00:21:59.430> networks<00:22:00.680> so<00:22:01.790> last 00:22:02.780 --> 00:22:02.790 align:start position:0% currencies on both networks so last 00:22:02.790 --> 00:22:04.940 align:start position:0% currencies on both networks so last thing<00:22:02.940> a<00:22:03.240> bit<00:22:03.480> about<00:22:03.690> the<00:22:03.930> roadmap<00:22:04.350> that<00:22:04.590> we 00:22:04.940 --> 00:22:04.950 align:start position:0% thing a bit about the roadmap that we 00:22:04.950 --> 00:22:08.120 align:start position:0% thing a bit about the roadmap that we are<00:22:05.010> looking<00:22:05.220> at<00:22:06.080> next<00:22:07.080> things<00:22:07.470> we<00:22:07.680> want<00:22:07.920> to<00:22:07.980> do 00:22:08.120 --> 00:22:08.130 align:start position:0% are looking at next things we want to do 00:22:08.130 --> 00:22:11.140 align:start position:0% are looking at next things we want to do include<00:22:08.850> we<00:22:09.120> not<00:22:09.840> want<00:22:10.350> to<00:22:10.440> enable 00:22:11.140 --> 00:22:11.150 align:start position:0% include we not want to enable 00:22:11.150 --> 00:22:13.060 align:start position:0% include we not want to enable which<00:22:11.390> authorities<00:22:12.020> to<00:22:12.230> vote<00:22:12.530> on<00:22:12.800> a<00:22:12.830> new 00:22:13.060 --> 00:22:13.070 align:start position:0% which authorities to vote on a new 00:22:13.070 --> 00:22:15.640 align:start position:0% which authorities to vote on a new bridge<00:22:13.309> authority<00:22:13.550> set<00:22:14.150> what<00:22:14.930> I<00:22:14.960> just<00:22:15.230> said 00:22:15.640 --> 00:22:15.650 align:start position:0% bridge authority set what I just said 00:22:15.650 --> 00:22:19.780 align:start position:0% bridge authority set what I just said dynamic<00:22:16.280> bridge<00:22:16.670> authority<00:22:16.910> sense<00:22:17.920> ii<00:22:18.920> what 00:22:19.780 --> 00:22:19.790 align:start position:0% dynamic bridge authority sense ii what 00:22:19.790 --> 00:22:22.450 align:start position:0% dynamic bridge authority sense ii what we<00:22:19.940> really<00:22:20.300> want<00:22:20.540> is<00:22:20.870> that<00:22:21.220> the<00:22:22.220> bridge 00:22:22.450 --> 00:22:22.460 align:start position:0% we really want is that the bridge 00:22:22.460 --> 00:22:25.960 align:start position:0% we really want is that the bridge authorities<00:22:23.240> are<00:22:23.710> tracking<00:22:24.710> whoever<00:22:25.550> is<00:22:25.790> an 00:22:25.960 --> 00:22:25.970 align:start position:0% authorities are tracking whoever is an 00:22:25.970 --> 00:22:30.190 align:start position:0% authorities are tracking whoever is an authority<00:22:26.600> on<00:22:26.809> the<00:22:27.970> on<00:22:28.970> the<00:22:29.570> site<00:22:29.809> networks 00:22:30.190 --> 00:22:30.200 align:start position:0% authority on the on the site networks 00:22:30.200 --> 00:22:32.650 align:start position:0% authority on the on the site networks and<00:22:30.410> that<00:22:30.890> these<00:22:31.160> set<00:22:31.460> are<00:22:32.090> pretty<00:22:32.510> much 00:22:32.650 --> 00:22:32.660 align:start position:0% and that these set are pretty much 00:22:32.660 --> 00:22:37.890 align:start position:0% and that these set are pretty much identical<00:22:34.420> further<00:22:35.559> we<00:22:36.559> are<00:22:36.590> exploring 00:22:37.890 --> 00:22:37.900 align:start position:0% identical further we are exploring 00:22:37.900 --> 00:22:40.480 align:start position:0% identical further we are exploring methods<00:22:38.900> how<00:22:39.320> the<00:22:39.380> site<00:22:39.740> network<00:22:40.220> can<00:22:40.460> be 00:22:40.480 --> 00:22:40.490 align:start position:0% methods how the site network can be 00:22:40.490 --> 00:22:42.900 align:start position:0% methods how the site network can be proof<00:22:41.000> of<00:22:41.180> stake<00:22:41.450> and<00:22:41.720> the<00:22:42.470> sidechain 00:22:42.900 --> 00:22:42.910 align:start position:0% proof of stake and the sidechain 00:22:42.910 --> 00:22:45.610 align:start position:0% proof of stake and the sidechain validate<00:22:43.910> us<00:22:43.940> you<00:22:44.600> know<00:22:44.720> the<00:22:44.900> validators<00:22:45.470> of 00:22:45.610 --> 00:22:45.620 align:start position:0% validate us you know the validators of 00:22:45.620 --> 00:22:47.890 align:start position:0% validate us you know the validators of that<00:22:45.770> chain<00:22:46.010> actually<00:22:46.640> state<00:22:46.940> is<00:22:47.179> on<00:22:47.480> the<00:22:47.720> main 00:22:47.890 --> 00:22:47.900 align:start position:0% that chain actually state is on the main 00:22:47.900 --> 00:22:49.840 align:start position:0% that chain actually state is on the main net<00:22:48.080> which<00:22:49.010> is<00:22:49.160> a<00:22:49.190> fairly<00:22:49.580> interesting 00:22:49.840 --> 00:22:49.850 align:start position:0% net which is a fairly interesting 00:22:49.850 --> 00:22:54.549 align:start position:0% net which is a fairly interesting approach<00:22:52.600> furthermore<00:22:53.600> we<00:22:54.020> are<00:22:54.050> interested 00:22:54.549 --> 00:22:54.559 align:start position:0% approach furthermore we are interested 00:22:54.559 --> 00:22:57.250 align:start position:0% approach furthermore we are interested in<00:22:54.679> finding<00:22:55.220> more<00:22:55.780> interesting<00:22:56.780> use<00:22:56.960> cases 00:22:57.250 --> 00:22:57.260 align:start position:0% in finding more interesting use cases 00:22:57.260 --> 00:22:59.140 align:start position:0% in finding more interesting use cases writing<00:22:57.770> more<00:22:57.890> extension<00:22:58.429> contracts<00:22:59.000> and 00:22:59.140 --> 00:22:59.150 align:start position:0% writing more extension contracts and 00:22:59.150 --> 00:23:01.120 align:start position:0% writing more extension contracts and last<00:22:59.630> but<00:22:59.840> not<00:22:59.960> least<00:23:00.170> they<00:23:00.740> are<00:23:00.800> still 00:23:01.120 --> 00:23:01.130 align:start position:0% last but not least they are still 00:23:01.130 --> 00:23:03.760 align:start position:0% last but not least they are still chilling<00:23:01.640> that<00:23:02.120> should<00:23:02.330> be<00:23:02.480> in<00:23:02.570> place<00:23:02.809> for 00:23:03.760 --> 00:23:03.770 align:start position:0% chilling that should be in place for 00:23:03.770 --> 00:23:05.799 align:start position:0% chilling that should be in place for example<00:23:04.090> monitoring<00:23:05.090> tooling<00:23:05.420> that<00:23:05.450> allows 00:23:05.799 --> 00:23:05.809 align:start position:0% example monitoring tooling that allows 00:23:05.809 --> 00:23:08.890 align:start position:0% example monitoring tooling that allows us<00:23:05.840> really<00:23:06.440> to<00:23:06.860> inspect<00:23:07.670> and<00:23:07.910> see<00:23:08.270> what<00:23:08.780> is 00:23:08.890 --> 00:23:08.900 align:start position:0% us really to inspect and see what is 00:23:08.900 --> 00:23:10.570 align:start position:0% us really to inspect and see what is happening<00:23:09.380> in<00:23:09.559> the<00:23:09.770> bridge<00:23:09.980> and<00:23:10.340> what 00:23:10.570 --> 00:23:10.580 align:start position:0% happening in the bridge and what 00:23:10.580 --> 00:23:13.750 align:start position:0% happening in the bridge and what messages<00:23:11.240> are<00:23:11.450> being<00:23:11.480> relayed<00:23:12.080> and<00:23:12.760> debug 00:23:13.750 --> 00:23:13.760 align:start position:0% messages are being relayed and debug 00:23:13.760 --> 00:23:18.960 align:start position:0% messages are being relayed and debug problems<00:23:14.240> if<00:23:14.420> there<00:23:14.660> are<00:23:14.720> any<00:23:14.929> problems<00:23:15.170> I 00:23:18.960 --> 00:23:18.970 align:start position:0% 00:23:18.970 --> 00:23:22.180 align:start position:0% invite<00:23:19.970> all<00:23:20.179> of<00:23:20.210> you<00:23:20.540> to<00:23:20.840> please<00:23:21.350> have<00:23:21.950> a<00:23:21.980> look 00:23:22.180 --> 00:23:22.190 align:start position:0% invite all of you to please have a look 00:23:22.190 --> 00:23:25.600 align:start position:0% invite all of you to please have a look at<00:23:22.250> our<00:23:22.580> Vicki<00:23:23.000> Reid<00:23:23.800> contribute<00:23:24.800> shared<00:23:25.400> with 00:23:25.600 --> 00:23:25.610 align:start position:0% at our Vicki Reid contribute shared with 00:23:25.610 --> 00:23:28.900 align:start position:0% at our Vicki Reid contribute shared with us<00:23:25.820> I<00:23:26.120> can't<00:23:26.840> wait<00:23:27.080> to<00:23:27.260> hear<00:23:27.590> what<00:23:27.800> you<00:23:28.670> want<00:23:28.850> to 00:23:28.900 --> 00:23:28.910 align:start position:0% us I can't wait to hear what you want to 00:23:28.910 --> 00:23:31.510 align:start position:0% us I can't wait to hear what you want to build<00:23:29.090> with<00:23:29.240> that<00:23:29.420> and<00:23:29.660> on<00:23:30.500> what<00:23:31.040> network<00:23:31.400> you 00:23:31.510 --> 00:23:31.520 align:start position:0% build with that and on what network you 00:23:31.520 --> 00:23:33.610 align:start position:0% build with that and on what network you want<00:23:31.700> to<00:23:31.790> build<00:23:31.910> it<00:23:32.059> is<00:23:32.179> it<00:23:32.660> coven<00:23:33.080> is<00:23:33.260> that 00:23:33.610 --> 00:23:33.620 align:start position:0% want to build it is it coven is that 00:23:33.620 --> 00:23:35.500 align:start position:0% want to build it is it coven is that your<00:23:33.770> own<00:23:33.860> app<00:23:34.160> for<00:23:34.429> specific<00:23:34.910> chains<00:23:35.179> are<00:23:35.360> you 00:23:35.500 --> 00:23:35.510 align:start position:0% your own app for specific chains are you 00:23:35.510 --> 00:23:38.230 align:start position:0% your own app for specific chains are you going<00:23:35.690> to<00:23:35.780> team<00:23:35.960> up<00:23:35.990> with<00:23:36.380> giveth<00:23:37.100> or<00:23:37.460> some 00:23:38.230 --> 00:23:38.240 align:start position:0% going to team up with giveth or some 00:23:38.240 --> 00:23:40.510 align:start position:0% going to team up with giveth or some other<00:23:38.390> teams<00:23:38.720> to<00:23:39.110> build<00:23:39.260> a<00:23:39.410> new<00:23:39.590> chain<00:23:39.890> in<00:23:40.250> the 00:23:40.510 --> 00:23:40.520 align:start position:0% other teams to build a new chain in the 00:23:40.520 --> 00:23:42.520 align:start position:0% other teams to build a new chain in the meantime<00:23:40.700> as<00:23:41.120> long<00:23:41.450> as<00:23:41.630> the<00:23:41.840> manor<00:23:42.020> doesn't 00:23:42.520 --> 00:23:42.530 align:start position:0% meantime as long as the manor doesn't 00:23:42.530 --> 00:23:49.480 align:start position:0% meantime as long as the manor doesn't scale<00:23:42.770> thank<00:23:43.580> you<00:23:43.700> so<00:23:43.850> much 00:23:49.480 --> 00:23:49.490 align:start position:0% 00:23:49.490 --> 00:23:52.730 align:start position:0% so<00:23:50.490> I've<00:23:50.670> got<00:23:50.850> another<00:23:51.120> five<00:23:51.930> minutes<00:23:52.230> for 00:23:52.730 --> 00:23:52.740 align:start position:0% so I've got another five minutes for 00:23:52.740 --> 00:24:00.280 align:start position:0% so I've got another five minutes for questions<00:23:53.370> I<00:23:57.080> can<00:23:58.080> repeat<00:23:58.350> it<00:23:58.500> to<00:23:58.620> you<00:23:58.710> them<00:23:58.860> on 00:24:00.280 --> 00:24:00.290 align:start position:0% questions I can repeat it to you them on 00:24:00.290 --> 00:24:02.630 align:start position:0% questions I can repeat it to you them on the<00:24:01.290> roadmap<00:24:01.470> I<00:24:01.800> noticed<00:24:02.130> you<00:24:02.220> guys<00:24:02.370> had<00:24:02.610> no 00:24:02.630 --> 00:24:02.640 align:start position:0% the roadmap I noticed you guys had no 00:24:02.640 --> 00:24:05.210 align:start position:0% the roadmap I noticed you guys had no intention<00:24:03.180> to<00:24:03.210> audit<00:24:03.660> your<00:24:03.810> contracts<00:24:04.260> is 00:24:05.210 --> 00:24:05.220 align:start position:0% intention to audit your contracts is 00:24:05.220 --> 00:24:06.440 align:start position:0% intention to audit your contracts is that<00:24:05.430> something<00:24:05.730> that<00:24:05.880> you<00:24:06.060> know<00:24:06.180> you're 00:24:06.440 --> 00:24:06.450 align:start position:0% that something that you know you're 00:24:06.450 --> 00:24:09.800 align:start position:0% that something that you know you're going<00:24:06.600> to<00:24:06.750> do<00:24:06.920> I'm<00:24:07.920> sorry<00:24:08.190> on<00:24:08.700> the<00:24:08.970> roadmap<00:24:09.480> you 00:24:09.800 --> 00:24:09.810 align:start position:0% going to do I'm sorry on the roadmap you 00:24:09.810 --> 00:24:11.930 align:start position:0% going to do I'm sorry on the roadmap you guys<00:24:09.960> didn't<00:24:10.260> list<00:24:10.770> any<00:24:10.920> intention<00:24:11.460> to<00:24:11.490> audit 00:24:11.930 --> 00:24:11.940 align:start position:0% guys didn't list any intention to audit 00:24:11.940 --> 00:24:13.880 align:start position:0% guys didn't list any intention to audit your<00:24:12.060> contracts<00:24:12.660> is<00:24:13.320> that<00:24:13.380> something<00:24:13.860> that 00:24:13.880 --> 00:24:13.890 align:start position:0% your contracts is that something that 00:24:13.890 --> 00:24:15.170 align:start position:0% your contracts is that something that you<00:24:14.310> guys<00:24:14.460> are<00:24:14.610> going<00:24:14.730> to<00:24:14.850> do<00:24:14.940> because<00:24:15.150> that 00:24:15.170 --> 00:24:15.180 align:start position:0% you guys are going to do because that 00:24:15.180 --> 00:24:16.790 align:start position:0% you guys are going to do because that hasn't<00:24:15.570> really<00:24:15.750> worked<00:24:16.110> out<00:24:16.470> well<00:24:16.650> in<00:24:16.680> the 00:24:16.790 --> 00:24:16.800 align:start position:0% hasn't really worked out well in the 00:24:16.800 --> 00:24:21.170 align:start position:0% hasn't really worked out well in the past<00:24:17.010> yeah<00:24:17.670> most<00:24:17.880> definitely<00:24:18.120> so<00:24:19.820> what<00:24:20.820> I<00:24:20.850> want 00:24:21.170 --> 00:24:21.180 align:start position:0% past yeah most definitely so what I want 00:24:21.180 --> 00:24:22.280 align:start position:0% past yeah most definitely so what I want to<00:24:21.300> see<00:24:21.420> first<00:24:21.630> is<00:24:21.870> a<00:24:21.900> bit<00:24:22.110> more 00:24:22.280 --> 00:24:22.290 align:start position:0% to see first is a bit more 00:24:22.290 --> 00:24:25.550 align:start position:0% to see first is a bit more experimentation<00:24:23.010> right<00:24:23.370> we<00:24:23.820> were<00:24:24.030> we<00:24:25.020> were<00:24:25.230> we 00:24:25.550 --> 00:24:25.560 align:start position:0% experimentation right we were we were we 00:24:25.560 --> 00:24:27.200 align:start position:0% experimentation right we were we were we haven't<00:24:25.920> actually<00:24:26.160> released<00:24:26.700> arbitrary 00:24:27.200 --> 00:24:27.210 align:start position:0% haven't actually released arbitrary 00:24:27.210 --> 00:24:30.410 align:start position:0% haven't actually released arbitrary message-passing<00:24:27.540> Burchette<00:24:28.910> it's<00:24:29.910> already 00:24:30.410 --> 00:24:30.420 align:start position:0% message-passing Burchette it's already 00:24:30.420 --> 00:24:32.180 align:start position:0% message-passing Burchette it's already in<00:24:30.750> github<00:24:31.050> yeah<00:24:31.380> you<00:24:31.590> know<00:24:31.680> you<00:24:31.740> can<00:24:31.980> play 00:24:32.180 --> 00:24:32.190 align:start position:0% in github yeah you know you can play 00:24:32.190 --> 00:24:35.240 align:start position:0% in github yeah you know you can play around<00:24:32.340> with<00:24:32.550> it<00:24:32.640> it<00:24:32.910> works<00:24:33.560> but<00:24:34.560> you<00:24:34.620> know<00:24:34.830> we 00:24:35.240 --> 00:24:35.250 align:start position:0% around with it it works but you know we 00:24:35.250 --> 00:24:36.890 align:start position:0% around with it it works but you know we want<00:24:35.460> to<00:24:35.550> write<00:24:35.910> a<00:24:35.940> few<00:24:36.210> more<00:24:36.270> integration 00:24:36.890 --> 00:24:36.900 align:start position:0% want to write a few more integration 00:24:36.900 --> 00:24:39.080 align:start position:0% want to write a few more integration tests<00:24:37.290> and<00:24:38.010> then<00:24:38.190> I<00:24:38.310> expect<00:24:38.640> us<00:24:38.820> in<00:24:39.000> the 00:24:39.080 --> 00:24:39.090 align:start position:0% tests and then I expect us in the 00:24:39.090 --> 00:24:41.510 align:start position:0% tests and then I expect us in the following<00:24:39.240> weeks<00:24:39.660> to<00:24:39.930> release<00:24:40.230> it<00:24:40.520> then 00:24:41.510 --> 00:24:41.520 align:start position:0% following weeks to release it then 00:24:41.520 --> 00:24:44.060 align:start position:0% following weeks to release it then deploy<00:24:41.940> a<00:24:42.210> test<00:24:42.420> version<00:24:42.690> between<00:24:43.380> Colvin<00:24:43.830> and 00:24:44.060 --> 00:24:44.070 align:start position:0% deploy a test version between Colvin and 00:24:44.070 --> 00:24:46.250 align:start position:0% deploy a test version between Colvin and maybe<00:24:44.220> Robson<00:24:44.820> right<00:24:45.060> play<00:24:45.630> around<00:24:45.870> with<00:24:46.080> it 00:24:46.250 --> 00:24:46.260 align:start position:0% maybe Robson right play around with it 00:24:46.260 --> 00:24:47.780 align:start position:0% maybe Robson right play around with it invite<00:24:46.620> more<00:24:46.800> people<00:24:46.860> to<00:24:47.220> play<00:24:47.340> around<00:24:47.610> with 00:24:47.780 --> 00:24:47.790 align:start position:0% invite more people to play around with 00:24:47.790 --> 00:24:50.960 align:start position:0% invite more people to play around with it<00:24:48.000> see<00:24:48.510> if<00:24:48.870> it<00:24:49.080> really<00:24:49.490> you<00:24:50.490> know<00:24:50.550> fulfill 00:24:50.960 --> 00:24:50.970 align:start position:0% it see if it really you know fulfill 00:24:50.970 --> 00:24:53.600 align:start position:0% it see if it really you know fulfill these<00:24:51.330> requirements<00:24:51.390> and<00:24:52.380> meets<00:24:53.340> these<00:24:53.550> needs 00:24:53.600 --> 00:24:53.610 align:start position:0% these requirements and meets these needs 00:24:53.610 --> 00:24:56.150 align:start position:0% these requirements and meets these needs that<00:24:54.210> people<00:24:54.420> have<00:24:54.600> and<00:24:54.960> then<00:24:55.470> once<00:24:55.890> we<00:24:56.040> got 00:24:56.150 --> 00:24:56.160 align:start position:0% that people have and then once we got 00:24:56.160 --> 00:24:59.180 align:start position:0% that people have and then once we got there<00:24:56.460> sure<00:24:56.760> like<00:24:57.210> definitely<00:24:57.740> either<00:24:58.740> we<00:24:58.980> do 00:24:59.180 --> 00:24:59.190 align:start position:0% there sure like definitely either we do 00:24:59.190 --> 00:25:00.890 align:start position:0% there sure like definitely either we do it<00:24:59.220> or<00:24:59.430> we<00:24:59.580> team<00:24:59.820> up<00:24:59.850> with<00:25:00.150> a<00:25:00.210> few<00:25:00.480> teams<00:25:00.660> to 00:25:00.890 --> 00:25:00.900 align:start position:0% it or we team up with a few teams to 00:25:00.900 --> 00:25:02.690 align:start position:0% it or we team up with a few teams to audit<00:25:01.200> these<00:25:01.320> contracts<00:25:01.830> thank<00:25:02.280> you<00:25:02.370> yeah 00:25:02.690 --> 00:25:02.700 align:start position:0% audit these contracts thank you yeah 00:25:02.700 --> 00:25:06.770 align:start position:0% audit these contracts thank you yeah thank<00:25:03.150> you<00:25:03.240> for<00:25:03.390> the<00:25:03.450> question<00:25:05.180> hey<00:25:06.180> hey 00:25:06.770 --> 00:25:06.780 align:start position:0% thank you for the question hey hey 00:25:06.780 --> 00:25:08.900 align:start position:0% thank you for the question hey hey thanks<00:25:07.020> for<00:25:07.140> that<00:25:07.320> Bjorn<00:25:07.710> and<00:25:07.770> thanks<00:25:08.070> it 00:25:08.900 --> 00:25:08.910 align:start position:0% thanks for that Bjorn and thanks it 00:25:08.910 --> 00:25:11.240 align:start position:0% thanks for that Bjorn and thanks it looks<00:25:09.150> looks<00:25:09.570> really<00:25:09.810> exciting<00:25:10.050> and<00:25:10.410> what 00:25:11.240 --> 00:25:11.250 align:start position:0% looks looks really exciting and what 00:25:11.250 --> 00:25:12.530 align:start position:0% looks looks really exciting and what question<00:25:11.520> I<00:25:11.580> had<00:25:11.700> was<00:25:11.880> with<00:25:12.120> the<00:25:12.180> bridge 00:25:12.530 --> 00:25:12.540 align:start position:0% question I had was with the bridge 00:25:12.540 --> 00:25:16.010 align:start position:0% question I had was with the bridge authorities<00:25:13.970> who<00:25:14.970> do<00:25:15.270> you<00:25:15.390> envision<00:25:15.720> those 00:25:16.010 --> 00:25:16.020 align:start position:0% authorities who do you envision those 00:25:16.020 --> 00:25:17.990 align:start position:0% authorities who do you envision those would<00:25:16.200> be<00:25:16.350> like<00:25:16.680> what<00:25:16.950> are<00:25:17.040> their<00:25:17.130> incentives 00:25:17.990 --> 00:25:18.000 align:start position:0% would be like what are their incentives 00:25:18.000 --> 00:25:19.850 align:start position:0% would be like what are their incentives for<00:25:18.270> actually<00:25:18.840> securing<00:25:19.320> those<00:25:19.500> relay 00:25:19.850 --> 00:25:19.860 align:start position:0% for actually securing those relay 00:25:19.860 --> 00:25:23.170 align:start position:0% for actually securing those relay messages<00:25:20.010> across<00:25:20.610> screens<00:25:21.240> across<00:25:21.930> chains 00:25:23.170 --> 00:25:23.180 align:start position:0% messages across screens across chains 00:25:23.180 --> 00:25:26.690 align:start position:0% messages across screens across chains again<00:25:24.180> how<00:25:24.450> to<00:25:24.510> panic<00:25:24.930> punish<00:25:25.340> bad<00:25:26.340> actors 00:25:26.690 --> 00:25:26.700 align:start position:0% again how to panic punish bad actors 00:25:26.700 --> 00:25:31.190 align:start position:0% again how to panic punish bad actors that<00:25:26.730> might<00:25:27.060> seep<00:25:27.480> in<00:25:27.680> right<00:25:28.680> I<00:25:29.960> can<00:25:30.960> envision 00:25:31.190 --> 00:25:31.200 align:start position:0% that might seep in right I can envision 00:25:31.200 --> 00:25:33.710 align:start position:0% that might seep in right I can envision multiple<00:25:32.040> scenarios<00:25:32.280> right<00:25:32.700> number<00:25:33.120> one<00:25:33.300> the 00:25:33.710 --> 00:25:33.720 align:start position:0% multiple scenarios right number one the 00:25:33.720 --> 00:25:37.160 align:start position:0% multiple scenarios right number one the most<00:25:33.840> obvious<00:25:34.380> one<00:25:34.620> is<00:25:34.650> the<00:25:35.370> DAP<00:25:35.960> that<00:25:36.960> needs 00:25:37.160 --> 00:25:37.170 align:start position:0% most obvious one is the DAP that needs 00:25:37.170 --> 00:25:38.900 align:start position:0% most obvious one is the DAP that needs to<00:25:37.350> utilize<00:25:37.770> the<00:25:37.950> chain<00:25:38.190> right<00:25:38.520> being<00:25:38.760> at 00:25:38.900 --> 00:25:38.910 align:start position:0% to utilize the chain right being at 00:25:38.910 --> 00:25:41.030 align:start position:0% to utilize the chain right being at their<00:25:39.090> own<00:25:39.240> chain<00:25:39.600> or<00:25:39.780> the<00:25:39.840> multiple<00:25:40.680> depths 00:25:41.030 --> 00:25:41.040 align:start position:0% their own chain or the multiple depths 00:25:41.040 --> 00:25:42.710 align:start position:0% their own chain or the multiple depths that<00:25:41.070> want<00:25:41.340> to<00:25:41.460> spin<00:25:42.060> up<00:25:42.150> their<00:25:42.330> own<00:25:42.450> chains 00:25:42.710 --> 00:25:42.720 align:start position:0% that want to spin up their own chains 00:25:42.720 --> 00:25:45.560 align:start position:0% that want to spin up their own chains they<00:25:42.900> have<00:25:43.050> an<00:25:43.170> intrinsic<00:25:43.710> motivation<00:25:44.640> to<00:25:45.240> you 00:25:45.560 --> 00:25:45.570 align:start position:0% they have an intrinsic motivation to you 00:25:45.570 --> 00:25:48.020 align:start position:0% they have an intrinsic motivation to you know<00:25:45.690> facilitate<00:25:46.560> this<00:25:46.740> transfer<00:25:47.160> and<00:25:47.520> after 00:25:48.020 --> 00:25:48.030 align:start position:0% know facilitate this transfer and after 00:25:48.030 --> 00:25:50.630 align:start position:0% know facilitate this transfer and after all<00:25:48.180> the<00:25:49.170> price<00:25:49.560> isn't<00:25:49.950> really<00:25:50.370> the<00:25:50.490> problem 00:25:50.630 --> 00:25:50.640 align:start position:0% all the price isn't really the problem 00:25:50.640 --> 00:25:53.420 align:start position:0% all the price isn't really the problem the<00:25:51.000> cost<00:25:51.240> the<00:25:51.450> expenses<00:25:52.050> to<00:25:52.560> spin<00:25:53.010> up<00:25:53.130> a<00:25:53.220> node 00:25:53.420 --> 00:25:53.430 align:start position:0% the cost the expenses to spin up a node 00:25:53.430 --> 00:25:55.520 align:start position:0% the cost the expenses to spin up a node today<00:25:53.820> I<00:25:53.850> believe<00:25:54.330> for<00:25:54.720> its<00:25:54.960> nearing<00:25:55.230> may<00:25:55.320> not 00:25:55.520 --> 00:25:55.530 align:start position:0% today I believe for its nearing may not 00:25:55.530 --> 00:25:58.580 align:start position:0% today I believe for its nearing may not cost<00:25:55.770> like<00:25:55.950> what<00:25:56.960> $150<00:25:57.960> a<00:25:58.140> month 00:25:58.580 --> 00:25:58.590 align:start position:0% cost like what $150 a month 00:25:58.590 --> 00:26:00.220 align:start position:0% cost like what $150 a month geronimo<00:25:59.220> note<00:25:59.370> so 00:26:00.220 --> 00:26:00.230 align:start position:0% geronimo note so 00:26:00.230 --> 00:26:03.190 align:start position:0% geronimo note so that<00:26:00.500> isn't<00:26:00.679> really<00:26:00.980> the<00:26:01.280> point<00:26:01.460> and<00:26:02.080> to<00:26:03.080> my 00:26:03.190 --> 00:26:03.200 align:start position:0% that isn't really the point and to my 00:26:03.200 --> 00:26:04.930 align:start position:0% that isn't really the point and to my knowledge<00:26:03.350> I<00:26:03.650> think<00:26:03.679> POA<00:26:04.280> network<00:26:04.700> has<00:26:04.910> been 00:26:04.930 --> 00:26:04.940 align:start position:0% knowledge I think POA network has been 00:26:04.940 --> 00:26:08.770 align:start position:0% knowledge I think POA network has been running<00:26:05.830> the<00:26:06.830> bridge<00:26:07.460> for<00:26:08.150> over<00:26:08.450> half<00:26:08.660> a<00:26:08.750> year 00:26:08.770 --> 00:26:08.780 align:start position:0% running the bridge for over half a year 00:26:08.780 --> 00:26:14.409 align:start position:0% running the bridge for over half a year now<00:26:09.010> and<00:26:10.780> I<00:26:11.919> think<00:26:12.919> the<00:26:13.370> cost<00:26:13.610> were<00:26:13.820> negligible 00:26:14.409 --> 00:26:14.419 align:start position:0% now and I think the cost were negligible 00:26:14.419 --> 00:26:18.159 align:start position:0% now and I think the cost were negligible so<00:26:16.059> reason<00:26:17.059> I<00:26:17.150> ask<00:26:17.299> is<00:26:17.510> one<00:26:17.900> of<00:26:17.990> the<00:26:18.049> most 00:26:18.159 --> 00:26:18.169 align:start position:0% so reason I ask is one of the most 00:26:18.169 --> 00:26:19.900 align:start position:0% so reason I ask is one of the most exciting<00:26:18.470> use<00:26:18.740> cases<00:26:18.980> which<00:26:19.400> I've<00:26:19.549> thought<00:26:19.730> of 00:26:19.900 --> 00:26:19.910 align:start position:0% exciting use cases which I've thought of 00:26:19.910 --> 00:26:21.460 align:start position:0% exciting use cases which I've thought of with<00:26:20.540> something<00:26:20.809> like<00:26:20.960> thunder<00:26:21.290> core 00:26:21.460 --> 00:26:21.470 align:start position:0% with something like thunder core 00:26:21.470 --> 00:26:22.810 align:start position:0% with something like thunder core something<00:26:21.860> like<00:26:22.010> that<00:26:22.160> being<00:26:22.340> able<00:26:22.460> to<00:26:22.610> use 00:26:22.810 --> 00:26:22.820 align:start position:0% something like that being able to use 00:26:22.820 --> 00:26:25.480 align:start position:0% something like that being able to use die<00:26:23.150> sound<00:26:24.110> one<00:26:24.260> side<00:26:24.559> chain<00:26:24.860> and<00:26:25.130> move<00:26:25.370> it 00:26:25.480 --> 00:26:25.490 align:start position:0% die sound one side chain and move it 00:26:25.490 --> 00:26:27.520 align:start position:0% die sound one side chain and move it over<00:26:25.610> you<00:26:26.330> know<00:26:26.390> you<00:26:26.840> can<00:26:26.990> end<00:26:27.110> up<00:26:27.230> if<00:26:27.350> some 00:26:27.520 --> 00:26:27.530 align:start position:0% over you know you can end up if some 00:26:27.530 --> 00:26:29.470 align:start position:0% over you know you can end up if some application<00:26:28.309> becomes<00:26:28.580> really<00:26:28.760> valuable<00:26:29.240> or 00:26:29.470 --> 00:26:29.480 align:start position:0% application becomes really valuable or 00:26:29.480 --> 00:26:31.330 align:start position:0% application becomes really valuable or really<00:26:29.720> of<00:26:29.929> hot<00:26:30.320> use<00:26:30.530> right<00:26:30.830> these<00:26:31.040> bridge 00:26:31.330 --> 00:26:31.340 align:start position:0% really of hot use right these bridge 00:26:31.340 --> 00:26:32.620 align:start position:0% really of hot use right these bridge authority<00:26:31.490> czar<00:26:31.880> going<00:26:32.000> to<00:26:32.059> be<00:26:32.120> presumably 00:26:32.620 --> 00:26:32.630 align:start position:0% authority czar going to be presumably 00:26:32.630 --> 00:26:34.240 align:start position:0% authority czar going to be presumably taking<00:26:33.049> and<00:26:33.169> Diet<00:26:33.380> and<00:26:33.650> being<00:26:33.830> able<00:26:33.919> to<00:26:34.040> direct 00:26:34.240 --> 00:26:34.250 align:start position:0% taking and Diet and being able to direct 00:26:34.250 --> 00:26:36.909 align:start position:0% taking and Diet and being able to direct it<00:26:34.610> in<00:26:34.760> the<00:26:35.030> main<00:26:35.179> chain<00:26:35.710> you<00:26:36.710> know<00:26:36.799> there 00:26:36.909 --> 00:26:36.919 align:start position:0% it in the main chain you know there 00:26:36.919 --> 00:26:38.500 align:start position:0% it in the main chain you know there might<00:26:37.010> be<00:26:37.070> a<00:26:37.190> lot<00:26:37.370> of<00:26:37.400> valley<00:26:37.640> moving<00:26:38.120> from<00:26:38.330> one 00:26:38.500 --> 00:26:38.510 align:start position:0% might be a lot of valley moving from one 00:26:38.510 --> 00:26:41.940 align:start position:0% might be a lot of valley moving from one chain<00:26:38.750> to<00:26:38.960> another<00:26:39.260> that's<00:26:40.190> it<00:26:40.429> right 00:26:41.940 --> 00:26:41.950 align:start position:0% chain to another that's it right 00:26:41.950 --> 00:26:44.409 align:start position:0% chain to another that's it right and<00:26:42.950> so<00:26:43.160> obviously<00:26:43.700> there's<00:26:44.059> an<00:26:44.179> incentive 00:26:44.409 --> 00:26:44.419 align:start position:0% and so obviously there's an incentive 00:26:44.419 --> 00:26:46.360 align:start position:0% and so obviously there's an incentive might<00:26:44.960> be<00:26:45.110> an<00:26:45.169> incentive<00:26:45.440> there<00:26:45.799> right<00:26:46.070> for 00:26:46.360 --> 00:26:46.370 align:start position:0% might be an incentive there right for 00:26:46.370 --> 00:26:48.370 align:start position:0% might be an incentive there right for you<00:26:47.030> know<00:26:47.120> then<00:26:47.330> to<00:26:47.480> direct<00:26:47.720> die<00:26:47.929> to<00:26:47.990> some 00:26:48.370 --> 00:26:48.380 align:start position:0% you know then to direct die to some 00:26:48.380 --> 00:26:50.020 align:start position:0% you know then to direct die to some other<00:26:48.530> contract<00:26:48.919> that's<00:26:49.070> not<00:26:49.250> the<00:26:49.429> intended 00:26:50.020 --> 00:26:50.030 align:start position:0% other contract that's not the intended 00:26:50.030 --> 00:27:00.610 align:start position:0% other contract that's not the intended intended<00:26:50.540> contract<00:26:51.290> right<00:26:52.150> I<00:26:58.540> can<00:26:59.620> sum 00:27:00.610 --> 00:27:00.620 align:start position:0% intended contract right I can sum 00:27:00.620 --> 00:27:04.180 align:start position:0% intended contract right I can sum multiple<00:27:01.490> aspects<00:27:01.850> right<00:27:02.090> I<00:27:02.679> still<00:27:03.679> think 00:27:04.180 --> 00:27:04.190 align:start position:0% multiple aspects right I still think 00:27:04.190 --> 00:27:06.039 align:start position:0% multiple aspects right I still think this<00:27:04.340> is<00:27:04.400> only<00:27:04.700> an<00:27:04.910> intermediary<00:27:05.390> solutions 00:27:06.039 --> 00:27:06.049 align:start position:0% this is only an intermediary solutions 00:27:06.049 --> 00:27:08.230 align:start position:0% this is only an intermediary solutions as<00:27:06.230> I<00:27:06.290> said<00:27:06.650> because<00:27:07.040> I<00:27:07.070> think<00:27:07.220> we<00:27:07.820> need<00:27:08.030> to 00:27:08.230 --> 00:27:08.240 align:start position:0% as I said because I think we need to 00:27:08.240 --> 00:27:09.940 align:start position:0% as I said because I think we need to come<00:27:08.450> to<00:27:08.630> a<00:27:08.660> point<00:27:09.140> where<00:27:09.380> we<00:27:09.500> pull<00:27:09.740> security 00:27:09.940 --> 00:27:09.950 align:start position:0% come to a point where we pull security 00:27:09.950 --> 00:27:12.640 align:start position:0% come to a point where we pull security for<00:27:10.520> all<00:27:10.640> these<00:27:10.790> chains<00:27:11.120> right<00:27:11.480> this<00:27:12.020> booty 00:27:12.640 --> 00:27:12.650 align:start position:0% for all these chains right this booty 00:27:12.650 --> 00:27:14.560 align:start position:0% for all these chains right this booty chain<00:27:12.950> future<00:27:13.880> where<00:27:14.179> you<00:27:14.270> have<00:27:14.390> like 00:27:14.560 --> 00:27:14.570 align:start position:0% chain future where you have like 00:27:14.570 --> 00:27:16.330 align:start position:0% chain future where you have like thousands<00:27:15.169> of<00:27:15.260> chains<00:27:15.590> that<00:27:15.679> all<00:27:15.890> secure 00:27:16.330 --> 00:27:16.340 align:start position:0% thousands of chains that all secure 00:27:16.340 --> 00:27:19.450 align:start position:0% thousands of chains that all secure themselves<00:27:16.549> bid<00:27:17.120> in<00:27:17.390> in<00:27:18.380> in<00:27:18.679> this<00:27:18.890> model<00:27:19.280> right 00:27:19.450 --> 00:27:19.460 align:start position:0% themselves bid in in in this model right 00:27:19.460 --> 00:27:21.159 align:start position:0% themselves bid in in in this model right well<00:27:19.820> you<00:27:19.910> have<00:27:19.940> IBM<00:27:20.419> chains<00:27:20.720> being<00:27:20.960> bridged 00:27:21.159 --> 00:27:21.169 align:start position:0% well you have IBM chains being bridged 00:27:21.169 --> 00:27:23.470 align:start position:0% well you have IBM chains being bridged by<00:27:21.410> parity<00:27:21.679> bridge<00:27:21.950> or<00:27:22.130> in<00:27:22.160> the<00:27:22.700> cosmos<00:27:23.120> model 00:27:23.470 --> 00:27:23.480 align:start position:0% by parity bridge or in the cosmos model 00:27:23.480 --> 00:27:24.850 align:start position:0% by parity bridge or in the cosmos model where<00:27:23.660> you<00:27:23.750> have<00:27:23.900> all<00:27:24.020> these<00:27:24.200> zones<00:27:24.470> that<00:27:24.650> have 00:27:24.850 --> 00:27:24.860 align:start position:0% where you have all these zones that have 00:27:24.860 --> 00:27:26.680 align:start position:0% where you have all these zones that have to<00:27:25.040> secure<00:27:25.370> themselves<00:27:25.549> I<00:27:25.940> don't<00:27:26.450> I<00:27:26.630> don't 00:27:26.680 --> 00:27:26.690 align:start position:0% to secure themselves I don't I don't 00:27:26.690 --> 00:27:28.210 align:start position:0% to secure themselves I don't I don't think<00:27:27.020> that's<00:27:27.169> feasible<00:27:27.380> in<00:27:27.740> the<00:27:27.860> long<00:27:28.010> run 00:27:28.210 --> 00:27:28.220 align:start position:0% think that's feasible in the long run 00:27:28.220 --> 00:27:33.250 align:start position:0% think that's feasible in the long run right<00:27:30.580> for<00:27:31.580> me<00:27:31.730> this<00:27:32.000> is<00:27:32.150> really<00:27:32.179> an<00:27:32.809> approach 00:27:33.250 --> 00:27:33.260 align:start position:0% right for me this is really an approach 00:27:33.260 --> 00:27:35.650 align:start position:0% right for me this is really an approach for<00:27:33.590> all<00:27:33.830> these<00:27:34.330> applications<00:27:35.330> right<00:27:35.510> now 00:27:35.650 --> 00:27:35.660 align:start position:0% for all these applications right now 00:27:35.660 --> 00:27:38.919 align:start position:0% for all these applications right now that<00:27:36.200> are<00:27:36.320> facing<00:27:36.559> these<00:27:37.220> issues<00:27:37.690> that<00:27:38.690> they 00:27:38.919 --> 00:27:38.929 align:start position:0% that are facing these issues that they 00:27:38.929 --> 00:27:40.810 align:start position:0% that are facing these issues that they have<00:27:39.169> been<00:27:39.380> working<00:27:39.530> on<00:27:39.890> all<00:27:39.950> that<00:27:40.309> code<00:27:40.549> for 00:27:40.810 --> 00:27:40.820 align:start position:0% have been working on all that code for 00:27:40.820 --> 00:27:42.430 align:start position:0% have been working on all that code for like<00:27:40.940> multiple<00:27:41.390> years<00:27:41.690> and<00:27:41.840> they<00:27:42.169> are<00:27:42.290> facing 00:27:42.430 --> 00:27:42.440 align:start position:0% like multiple years and they are facing 00:27:42.440 --> 00:27:44.980 align:start position:0% like multiple years and they are facing the<00:27:42.770> situation<00:27:43.340> a<00:27:43.460> either<00:27:44.030> you<00:27:44.510> wait<00:27:44.720> another 00:27:44.980 --> 00:27:44.990 align:start position:0% the situation a either you wait another 00:27:44.990 --> 00:27:49.030 align:start position:0% the situation a either you wait another three<00:27:45.350> years<00:27:45.380> and<00:27:46.630> Jasper's<00:27:47.630> here<00:27:47.900> or<00:27:48.080> you 00:27:49.030 --> 00:27:49.040 align:start position:0% three years and Jasper's here or you 00:27:49.040 --> 00:27:51.310 align:start position:0% three years and Jasper's here or you restart<00:27:49.610> from<00:27:49.790> scratch<00:27:50.179> and<00:27:50.540> try<00:27:51.260> to 00:27:51.310 --> 00:27:51.320 align:start position:0% restart from scratch and try to 00:27:51.320 --> 00:27:53.590 align:start position:0% restart from scratch and try to implement<00:27:51.740> it<00:27:51.950> with<00:27:52.130> layer<00:27:52.640> 2<00:27:52.910> solutions<00:27:53.419> such 00:27:53.590 --> 00:27:53.600 align:start position:0% implement it with layer 2 solutions such 00:27:53.600 --> 00:27:59.200 align:start position:0% implement it with layer 2 solutions such as<00:27:53.630> state<00:27:54.470> channels<00:27:54.799> right<00:27:56.049> that<00:27:57.049> said<00:27:58.210> I'm 00:27:59.200 --> 00:27:59.210 align:start position:0% as state channels right that said I'm 00:27:59.210 --> 00:28:03.190 align:start position:0% as state channels right that said I'm not<00:27:59.240> quite<00:27:59.660> sure<00:27:59.690> if<00:28:00.520> that<00:28:01.630> click<00:28:02.630> are<00:28:02.809> you<00:28:02.990> are 00:28:03.190 --> 00:28:03.200 align:start position:0% not quite sure if that click are you are 00:28:03.200 --> 00:28:08.680 align:start position:0% not quite sure if that click are you are you<00:28:03.350> asking<00:28:04.160> about<00:28:04.370> the<00:28:06.850> the<00:28:07.850> danger<00:28:08.480> of 00:28:08.680 --> 00:28:08.690 align:start position:0% you asking about the the danger of 00:28:08.690 --> 00:28:11.980 align:start position:0% you asking about the the danger of having<00:28:09.080> too<00:28:09.290> much<00:28:09.440> there<00:28:09.770> you<00:28:09.799> locked<00:28:10.250> up<00:28:10.460> in<00:28:11.120> a 00:28:11.980 --> 00:28:11.990 align:start position:0% having too much there you locked up in a 00:28:11.990 --> 00:28:13.330 align:start position:0% having too much there you locked up in a POA<00:28:12.320> chain 00:28:13.330 --> 00:28:13.340 align:start position:0% POA chain 00:28:13.340 --> 00:28:16.600 align:start position:0% POA chain well<00:28:14.120> it's<00:28:14.539> well<00:28:15.289> maybe<00:28:15.769> not<00:28:15.919> necessarily<00:28:16.039> POA 00:28:16.600 --> 00:28:16.610 align:start position:0% well it's well maybe not necessarily POA 00:28:16.610 --> 00:28:19.899 align:start position:0% well it's well maybe not necessarily POA but<00:28:16.940> for<00:28:17.149> instance<00:28:17.419> like<00:28:17.600> you<00:28:18.320> could<00:28:18.639> mint<00:28:19.639> dye 00:28:19.899 --> 00:28:19.909 align:start position:0% but for instance like you could mint dye 00:28:19.909 --> 00:28:22.299 align:start position:0% but for instance like you could mint dye on<00:28:20.240> the<00:28:20.870> main<00:28:21.049> net<00:28:21.289> right<00:28:21.710> and<00:28:21.950> then<00:28:22.129> there's 00:28:22.299 --> 00:28:22.309 align:start position:0% on the main net right and then there's 00:28:22.309 --> 00:28:24.549 align:start position:0% on the main net right and then there's some<00:28:22.490> application<00:28:23.269> that<00:28:23.389> uses<00:28:23.539> dye<00:28:23.929> say<00:28:24.440> on 00:28:24.549 --> 00:28:24.559 align:start position:0% some application that uses dye say on 00:28:24.559 --> 00:28:26.200 align:start position:0% some application that uses dye say on another<00:28:24.830> chain<00:28:25.249> maybe<00:28:25.909> it's<00:28:26.059> like<00:28:26.179> a 00:28:26.200 --> 00:28:26.210 align:start position:0% another chain maybe it's like a 00:28:26.210 --> 00:28:27.519 align:start position:0% another chain maybe it's like a proof-of-work<00:28:26.629> saying<00:28:27.019> or<00:28:27.139> a<00:28:27.169> peewee<00:28:27.350> powder 00:28:27.519 --> 00:28:27.529 align:start position:0% proof-of-work saying or a peewee powder 00:28:27.529 --> 00:28:29.590 align:start position:0% proof-of-work saying or a peewee powder or<00:28:27.710> something<00:28:28.039> right<00:28:28.220> and<00:28:28.759> you<00:28:28.879> send<00:28:29.179> you<00:28:29.480> know 00:28:29.590 --> 00:28:29.600 align:start position:0% or something right and you send you know 00:28:29.600 --> 00:28:31.930 align:start position:0% or something right and you send you know I<00:28:29.629> don't<00:28:30.049> know<00:28:30.110> a<00:28:30.259> million<00:28:30.499> dollars<00:28:30.620> into<00:28:31.279> the 00:28:31.930 --> 00:28:31.940 align:start position:0% I don't know a million dollars into the 00:28:31.940 --> 00:28:35.100 align:start position:0% I don't know a million dollars into the other<00:28:32.450> chain<00:28:32.779> right<00:28:33.409> through<00:28:33.799> the<00:28:33.889> bridge 00:28:35.100 --> 00:28:35.110 align:start position:0% other chain right through the bridge 00:28:35.110 --> 00:28:37.180 align:start position:0% other chain right through the bridge value<00:28:36.110> gets<00:28:36.289> generated<00:28:36.440> there<00:28:36.889> or<00:28:37.039> whatever 00:28:37.180 --> 00:28:37.190 align:start position:0% value gets generated there or whatever 00:28:37.190 --> 00:28:39.489 align:start position:0% value gets generated there or whatever then<00:28:38.090> you<00:28:38.360> want<00:28:38.509> to<00:28:38.629> secure<00:28:38.960> it<00:28:39.019> back<00:28:39.200> on<00:28:39.409> the 00:28:39.489 --> 00:28:39.499 align:start position:0% then you want to secure it back on the 00:28:39.499 --> 00:28:42.220 align:start position:0% then you want to secure it back on the main<00:28:39.649> net 00:28:42.220 --> 00:28:42.230 align:start position:0% 00:28:42.230 --> 00:28:43.840 align:start position:0% you<00:28:42.350> know<00:28:42.470> destroyed<00:28:42.919> or<00:28:43.039> properly<00:28:43.340> accounted 00:28:43.840 --> 00:28:43.850 align:start position:0% you know destroyed or properly accounted 00:28:43.850 --> 00:28:45.669 align:start position:0% you know destroyed or properly accounted on<00:28:43.940> the<00:28:44.029> main<00:28:44.179> net<00:28:44.389> but<00:28:44.929> maybe<00:28:45.139> it's<00:28:45.320> just<00:28:45.470> not 00:28:45.669 --> 00:28:45.679 align:start position:0% on the main net but maybe it's just not 00:28:45.679 --> 00:28:47.200 align:start position:0% on the main net but maybe it's just not the<00:28:45.860> youth<00:28:46.039> the<00:28:46.249> right<00:28:46.429> use<00:28:46.639> case<00:28:46.879> for<00:28:46.909> this 00:28:47.200 --> 00:28:47.210 align:start position:0% the youth the right use case for this 00:28:47.210 --> 00:28:50.649 align:start position:0% the youth the right use case for this kind<00:28:47.480> of<00:28:48.129> okay<00:28:49.129> I<00:28:49.159> get<00:28:49.340> so<00:28:49.580> so<00:28:49.999> you're<00:28:50.450> asking 00:28:50.649 --> 00:28:50.659 align:start position:0% kind of okay I get so so you're asking 00:28:50.659 --> 00:28:53.399 align:start position:0% kind of okay I get so so you're asking how<00:28:51.499> can<00:28:51.559> I<00:28:51.740> trust<00:28:52.070> these<00:28:52.369> authorities 00:28:53.399 --> 00:28:53.409 align:start position:0% how can I trust these authorities 00:28:53.409 --> 00:28:55.180 align:start position:0% how can I trust these authorities effectively<00:28:54.409> because<00:28:54.559> they<00:28:54.649> can<00:28:54.799> send<00:28:55.070> the 00:28:55.180 --> 00:28:55.190 align:start position:0% effectively because they can send the 00:28:55.190 --> 00:28:56.710 align:start position:0% effectively because they can send the diet<00:28:55.429> you<00:28:55.610> know<00:28:55.789> wherever<00:28:55.970> right<00:28:56.299> that's 00:28:56.710 --> 00:28:56.720 align:start position:0% diet you know wherever right that's 00:28:56.720 --> 00:28:58.450 align:start position:0% diet you know wherever right that's always<00:28:56.869> the<00:28:57.139> case<00:28:57.350> right<00:28:57.590> like<00:28:57.769> it's<00:28:58.039> it's<00:28:58.340> the 00:28:58.450 --> 00:28:58.460 align:start position:0% always the case right like it's it's the 00:28:58.460 --> 00:29:01.239 align:start position:0% always the case right like it's it's the same<00:28:58.669> thing<00:28:58.970> as<00:28:59.210> in<00:28:59.509> in<00:28:59.960> any<00:29:00.320> theorem<00:29:00.889> proof<00:29:01.100> of 00:29:01.239 --> 00:29:01.249 align:start position:0% same thing as in in any theorem proof of 00:29:01.249 --> 00:29:02.889 align:start position:0% same thing as in in any theorem proof of work<00:29:01.549> or<00:29:01.759> in<00:29:01.879> any<00:29:02.029> kind<00:29:02.240> of<00:29:02.299> proof<00:29:02.509> of<00:29:02.659> state 00:29:02.889 --> 00:29:02.899 align:start position:0% work or in any kind of proof of state 00:29:02.899 --> 00:29:06.489 align:start position:0% work or in any kind of proof of state system<00:29:03.289> how<00:29:03.440> can<00:29:03.649> i<00:29:03.740> sir<00:29:04.039> I<00:29:04.309> I<00:29:05.210> trust<00:29:06.169> that<00:29:06.289> the 00:29:06.489 --> 00:29:06.499 align:start position:0% system how can i sir I I trust that the 00:29:06.499 --> 00:29:08.379 align:start position:0% system how can i sir I I trust that the validators<00:29:07.070> who<00:29:07.249> validate<00:29:07.639> my<00:29:07.759> chain<00:29:08.029> be<00:29:08.149> the 00:29:08.379 --> 00:29:08.389 align:start position:0% validators who validate my chain be the 00:29:08.389 --> 00:29:11.560 align:start position:0% validators who validate my chain be the chain<00:29:08.720> or<00:29:09.139> or<00:29:09.860> the<00:29:10.460> bridge<00:29:10.669> doesn't<00:29:11.299> really 00:29:11.560 --> 00:29:11.570 align:start position:0% chain or or the bridge doesn't really 00:29:11.570 --> 00:29:13.299 align:start position:0% chain or or the bridge doesn't really matter<00:29:11.779> in<00:29:11.929> that<00:29:11.960> sense<00:29:12.320> right<00:29:12.619> like<00:29:13.100> don't 00:29:13.299 --> 00:29:13.309 align:start position:0% matter in that sense right like don't 00:29:13.309 --> 00:29:16.450 align:start position:0% matter in that sense right like don't collude<00:29:13.999> right<00:29:14.600> don't<00:29:15.110> build<00:29:15.440> a<00:29:15.559> cartel<00:29:16.249> and 00:29:16.450 --> 00:29:16.460 align:start position:0% collude right don't build a cartel and 00:29:16.460 --> 00:29:18.009 align:start position:0% collude right don't build a cartel and say<00:29:16.639> like<00:29:16.789> oh<00:29:16.909> I'm<00:29:17.119> actually<00:29:17.360> gonna<00:29:17.600> take<00:29:17.869> all 00:29:18.009 --> 00:29:18.019 align:start position:0% say like oh I'm actually gonna take all 00:29:18.019 --> 00:29:21.489 align:start position:0% say like oh I'm actually gonna take all the<00:29:18.200> value<00:29:18.470> out<00:29:18.679> of<00:29:18.710> that<00:29:19.159> bridge<00:29:20.259> very<00:29:21.259> good 00:29:21.489 --> 00:29:21.499 align:start position:0% the value out of that bridge very good 00:29:21.499 --> 00:29:27.159 align:start position:0% the value out of that bridge very good question<00:29:22.249> I<00:29:25.059> think<00:29:26.059> like<00:29:26.509> as<00:29:26.659> a<00:29:26.690> user<00:29:26.960> you've 00:29:27.159 --> 00:29:27.169 align:start position:0% question I think like as a user you've 00:29:27.169 --> 00:29:29.590 align:start position:0% question I think like as a user you've got<00:29:27.289> to<00:29:27.379> be<00:29:27.440> really<00:29:27.710> cautious<00:29:27.919> to<00:29:28.730> interact 00:29:29.590 --> 00:29:29.600 align:start position:0% got to be really cautious to interact 00:29:29.600 --> 00:29:31.659 align:start position:0% got to be really cautious to interact with<00:29:29.929> certain<00:29:30.110> chains<00:29:30.470> with<00:29:30.769> too<00:29:31.309> much<00:29:31.490> value 00:29:31.659 --> 00:29:31.669 align:start position:0% with certain chains with too much value 00:29:31.669 --> 00:29:33.820 align:start position:0% with certain chains with too much value right<00:29:32.090> I<00:29:32.299> wouldn't<00:29:32.869> want<00:29:33.049> to<00:29:33.139> transfer<00:29:33.710> a 00:29:33.820 --> 00:29:33.830 align:start position:0% right I wouldn't want to transfer a 00:29:33.830 --> 00:29:36.700 align:start position:0% right I wouldn't want to transfer a million<00:29:34.580> died<00:29:34.970> over<00:29:35.509> to<00:29:35.720> a<00:29:35.749> chain<00:29:36.110> that<00:29:36.499> I<00:29:36.559> know 00:29:36.700 --> 00:29:36.710 align:start position:0% million died over to a chain that I know 00:29:36.710 --> 00:29:39.220 align:start position:0% million died over to a chain that I know is<00:29:37.009> rarely<00:29:37.909> being<00:29:38.240> used<00:29:38.509> where<00:29:38.840> there<00:29:38.990> may<00:29:39.200> be 00:29:39.220 --> 00:29:39.230 align:start position:0% is rarely being used where there may be 00:29:39.230 --> 00:29:43.359 align:start position:0% is rarely being used where there may be two<00:29:40.809> to<00:29:41.809> authorities<00:29:42.440> only<00:29:42.649> that<00:29:43.190> have 00:29:43.359 --> 00:29:43.369 align:start position:0% two to authorities only that have 00:29:43.369 --> 00:29:46.450 align:start position:0% two to authorities only that have aligned<00:29:44.090> incentives<00:29:44.509> to<00:29:45.169> actually<00:29:45.590> collude 00:29:46.450 --> 00:29:46.460 align:start position:0% aligned incentives to actually collude 00:29:46.460 --> 00:29:51.580 align:start position:0% aligned incentives to actually collude and<00:29:46.639> steal<00:29:47.179> your<00:29:47.330> money<00:29:47.480> right<00:29:49.029> yeah<00:29:50.590> thanks 00:29:51.580 --> 00:29:51.590 align:start position:0% and steal your money right yeah thanks 00:29:51.590 --> 00:29:57.580 align:start position:0% and steal your money right yeah thanks for<00:29:51.649> that<00:29:51.740> appreciate<00:29:52.190> it<00:29:52.309> thank<00:29:52.490> you<00:29:56.590> thank 00:29:57.580 --> 00:29:57.590 align:start position:0% for that appreciate it thank you thank 00:29:57.590 --> 00:30:02.080 align:start position:0% for that appreciate it thank you thank you<00:29:58.749> so<00:29:59.980> how<00:30:00.980> is<00:30:01.340> the<00:30:01.549> fault<00:30:01.909> tolerance 00:30:02.080 --> 00:30:02.090 align:start position:0% you so how is the fault tolerance 00:30:02.090 --> 00:30:05.619 align:start position:0% you so how is the fault tolerance maintained<00:30:02.990> at<00:30:03.440> the<00:30:03.499> delivery<00:30:04.159> of<00:30:04.249> the<00:30:04.700> accept 00:30:05.619 --> 00:30:05.629 align:start position:0% maintained at the delivery of the accept 00:30:05.629 --> 00:30:07.450 align:start position:0% maintained at the delivery of the accept message<00:30:06.019> is<00:30:06.289> there<00:30:06.499> a<00:30:06.529> ring<00:30:06.830> signature<00:30:07.340> or 00:30:07.450 --> 00:30:07.460 align:start position:0% message is there a ring signature or 00:30:07.460 --> 00:30:10.509 align:start position:0% message is there a ring signature or something<00:30:07.820> of<00:30:07.970> the<00:30:08.119> validators<00:30:08.710> no<00:30:09.710> so<00:30:09.980> what 00:30:10.509 --> 00:30:10.519 align:start position:0% something of the validators no so what 00:30:10.519 --> 00:30:14.649 align:start position:0% something of the validators no so what is<00:30:10.639> happening<00:30:12.639> the<00:30:13.639> Bridge<00:30:13.820> Authority<00:30:13.850> is<00:30:14.480> do 00:30:14.649 --> 00:30:14.659 align:start position:0% is happening the Bridge Authority is do 00:30:14.659 --> 00:30:18.789 align:start position:0% is happening the Bridge Authority is do two<00:30:14.840> things<00:30:15.019> right<00:30:15.549> when<00:30:16.549> they<00:30:16.730> watch<00:30:17.799> message 00:30:18.789 --> 00:30:18.799 align:start position:0% two things right when they watch message 00:30:18.799 --> 00:30:21.009 align:start position:0% two things right when they watch message coming<00:30:19.100> from<00:30:19.129> me<00:30:19.399> into<00:30:19.490> a<00:30:19.610> site<00:30:19.789> on<00:30:19.999> the<00:30:20.840> site 00:30:21.009 --> 00:30:21.019 align:start position:0% coming from me into a site on the site 00:30:21.019 --> 00:30:24.129 align:start position:0% coming from me into a site on the site matches<00:30:21.230> they<00:30:21.529> all<00:30:21.710> have<00:30:22.669> to<00:30:22.940> call<00:30:23.869> a<00:30:23.899> function 00:30:24.129 --> 00:30:24.139 align:start position:0% matches they all have to call a function 00:30:24.139 --> 00:30:25.149 align:start position:0% matches they all have to call a function on 00:30:25.149 --> 00:30:25.159 align:start position:0% on 00:30:25.159 --> 00:30:27.549 align:start position:0% on sight<00:30:25.519> network<00:30:26.119> right<00:30:26.330> and<00:30:26.599> you<00:30:27.409> have<00:30:27.529> a 00:30:27.549 --> 00:30:27.559 align:start position:0% sight network right and you have a 00:30:27.559 --> 00:30:29.320 align:start position:0% sight network right and you have a configurable<00:30:28.099> section<00:30:28.700> and<00:30:28.909> if<00:30:28.999> you<00:30:29.119> say 00:30:29.320 --> 00:30:29.330 align:start position:0% configurable section and if you say 00:30:29.330 --> 00:30:31.899 align:start position:0% configurable section and if you say seven<00:30:29.720> out<00:30:29.840> of<00:30:29.869> ten<00:30:30.460> authorities<00:30:31.460> have<00:30:31.700> to 00:30:31.899 --> 00:30:31.909 align:start position:0% seven out of ten authorities have to 00:30:31.909 --> 00:30:33.969 align:start position:0% seven out of ten authorities have to sign<00:30:32.179> off<00:30:32.359> on<00:30:32.389> the<00:30:32.659> message<00:30:32.960> only<00:30:33.109> then<00:30:33.710> the 00:30:33.969 --> 00:30:33.979 align:start position:0% sign off on the message only then the 00:30:33.979 --> 00:30:35.349 align:start position:0% sign off on the message only then the message<00:30:34.309> is<00:30:34.460> actually<00:30:34.609> being<00:30:34.970> relayed 00:30:35.349 --> 00:30:35.359 align:start position:0% message is actually being relayed 00:30:35.359 --> 00:30:37.389 align:start position:0% message is actually being relayed otherwise<00:30:35.749> not<00:30:35.989> right<00:30:36.320> and<00:30:36.499> in<00:30:36.919> the<00:30:37.070> other<00:30:37.190> way 00:30:37.389 --> 00:30:37.399 align:start position:0% otherwise not right and in the other way 00:30:37.399 --> 00:30:37.839 align:start position:0% otherwise not right and in the other way around 00:30:37.839 --> 00:30:37.849 align:start position:0% around 00:30:37.849 --> 00:30:41.019 align:start position:0% around you<00:30:38.269> gather<00:30:38.809> signatures<00:30:39.259> before<00:30:39.919> right 00:30:41.019 --> 00:30:41.029 align:start position:0% you gather signatures before right 00:30:41.029 --> 00:30:43.269 align:start position:0% you gather signatures before right they<00:30:41.450> gather<00:30:42.169> signatures<00:30:42.440> on<00:30:42.950> the<00:30:43.070> side 00:30:43.269 --> 00:30:43.279 align:start position:0% they gather signatures on the side 00:30:43.279 --> 00:30:45.279 align:start position:0% they gather signatures on the side network<00:30:43.669> and<00:30:43.849> then<00:30:44.119> the<00:30:44.450> last<00:30:44.599> or<00:30:45.049> ''tis 00:30:45.279 --> 00:30:45.289 align:start position:0% network and then the last or ''tis 00:30:45.289 --> 00:30:47.349 align:start position:0% network and then the last or ''tis submits<00:30:45.979> one<00:30:46.070> transaction<00:30:46.849> on<00:30:46.970> the<00:30:47.149> main 00:30:47.349 --> 00:30:47.359 align:start position:0% submits one transaction on the main 00:30:47.359 --> 00:30:50.680 align:start position:0% submits one transaction on the main network<00:30:47.840> that<00:30:48.999> accumulates<00:30:49.999> on<00:30:50.090> all<00:30:50.479> these 00:30:50.680 --> 00:30:50.690 align:start position:0% network that accumulates on all these 00:30:50.690 --> 00:30:52.389 align:start position:0% network that accumulates on all these signatures<00:30:51.049> and<00:30:51.349> the<00:30:51.470> contract<00:30:51.919> checks<00:30:52.159> that 00:30:52.389 --> 00:30:52.399 align:start position:0% signatures and the contract checks that 00:30:52.399 --> 00:30:54.729 align:start position:0% signatures and the contract checks that all<00:30:52.609> the<00:30:52.789> signatures<00:30:53.269> are<00:30:53.450> there<00:30:53.629> in<00:30:54.289> that<00:30:54.529> way 00:30:54.729 --> 00:30:54.739 align:start position:0% all the signatures are there in that way 00:30:54.739 --> 00:30:57.489 align:start position:0% all the signatures are there in that way you<00:30:54.799> have<00:30:55.159> like<00:30:55.489> for<00:30:55.729> tolerance<00:30:56.229> okay<00:30:57.229> is 00:30:57.489 --> 00:30:57.499 align:start position:0% you have like for tolerance okay is 00:30:57.499 --> 00:31:00.009 align:start position:0% you have like for tolerance okay is there<00:30:57.739> is<00:30:58.070> there<00:30:58.309> like<00:30:58.759> like<00:30:59.539> on<00:30:59.720> state 00:31:00.009 --> 00:31:00.019 align:start position:0% there is there like like on state 00:31:00.019 --> 00:31:01.899 align:start position:0% there is there like like on state channels<00:31:00.409> where<00:31:00.649> there's<00:31:00.830> kind<00:31:01.039> of<00:31:01.099> this<00:31:01.249> like 00:31:01.899 --> 00:31:01.909 align:start position:0% channels where there's kind of this like 00:31:01.909 --> 00:31:04.810 align:start position:0% channels where there's kind of this like the<00:31:02.119> waiting<00:31:02.869> period<00:31:03.349> after<00:31:03.769> message<00:31:04.700> has 00:31:04.810 --> 00:31:04.820 align:start position:0% the waiting period after message has 00:31:04.820 --> 00:31:07.089 align:start position:0% the waiting period after message has been<00:31:04.849> relayed<00:31:05.409> is<00:31:06.409> there<00:31:06.649> something<00:31:06.950> like 00:31:07.089 --> 00:31:07.099 align:start position:0% been relayed is there something like 00:31:07.099 --> 00:31:08.830 align:start position:0% been relayed is there something like that<00:31:07.279> so<00:31:07.519> that<00:31:07.639> maybe<00:31:08.090> somebody<00:31:08.450> can<00:31:08.570> bring<00:31:08.690> in 00:31:08.830 --> 00:31:08.840 align:start position:0% that so that maybe somebody can bring in 00:31:08.840 --> 00:31:11.799 align:start position:0% that so that maybe somebody can bring in attestation<00:31:09.349> saying<00:31:09.799> that<00:31:10.009> actually<00:31:10.809> that's 00:31:11.799 --> 00:31:11.809 align:start position:0% attestation saying that actually that's 00:31:11.809 --> 00:31:14.070 align:start position:0% attestation saying that actually that's not<00:31:11.899> what<00:31:12.139> happened<00:31:12.499> on<00:31:12.739> the<00:31:13.039> opposing<00:31:13.580> chain 00:31:14.070 --> 00:31:14.080 align:start position:0% not what happened on the opposing chain 00:31:14.080 --> 00:31:17.979 align:start position:0% not what happened on the opposing chain currently<00:31:15.080> not<00:31:15.259> because<00:31:16.570> really<00:31:17.570> you<00:31:17.809> take 00:31:17.979 --> 00:31:17.989 align:start position:0% currently not because really you take 00:31:17.989 --> 00:31:20.139 align:start position:0% currently not because really you take these<00:31:18.200> the<00:31:18.739> set<00:31:19.009> of<00:31:19.159> which<00:31:19.369> our<00:31:19.549> sorties<00:31:19.970> as 00:31:20.139 --> 00:31:20.149 align:start position:0% these the set of which our sorties as 00:31:20.149 --> 00:31:21.969 align:start position:0% these the set of which our sorties as you<00:31:20.419> are<00:31:20.570> you<00:31:21.019> know<00:31:21.169> your<00:31:21.409> point<00:31:21.679> of<00:31:21.739> reference 00:31:21.969 --> 00:31:21.979 align:start position:0% you are you know your point of reference 00:31:21.979 --> 00:31:25.629 align:start position:0% you are you know your point of reference if<00:31:22.369> they<00:31:22.929> say<00:31:23.929> hey<00:31:24.679> that<00:31:24.889> message<00:31:25.249> was<00:31:25.429> real 00:31:25.629 --> 00:31:25.639 align:start position:0% if they say hey that message was real 00:31:25.639 --> 00:31:28.180 align:start position:0% if they say hey that message was real that<00:31:25.700> is<00:31:25.879> actually<00:31:26.210> relayed<00:31:26.539> and<00:31:26.720> in<00:31:27.289> order<00:31:27.679> to 00:31:28.180 --> 00:31:28.190 align:start position:0% that is actually relayed and in order to 00:31:28.190 --> 00:31:30.009 align:start position:0% that is actually relayed and in order to make<00:31:28.399> sure<00:31:28.429> there's<00:31:28.970> no<00:31:29.119> reorganization<00:31:29.899> they 00:31:30.009 --> 00:31:30.019 align:start position:0% make sure there's no reorganization they 00:31:30.019 --> 00:31:32.019 align:start position:0% make sure there's no reorganization they wait<00:31:30.229> a<00:31:30.259> few<00:31:30.789> confirmation<00:31:31.789> block 00:31:32.019 --> 00:31:32.029 align:start position:0% wait a few confirmation block 00:31:32.029 --> 00:31:34.539 align:start position:0% wait a few confirmation block confirmations<00:31:32.659> in<00:31:32.779> order<00:31:33.109> you<00:31:33.409> know<00:31:33.529> to<00:31:34.429> be 00:31:34.539 --> 00:31:34.549 align:start position:0% confirmations in order you know to be 00:31:34.549 --> 00:31:36.940 align:start position:0% confirmations in order you know to be sure<00:31:34.759> that<00:31:35.210> actually<00:31:35.929> whatever<00:31:36.379> kicked<00:31:36.769> off 00:31:36.940 --> 00:31:36.950 align:start position:0% sure that actually whatever kicked off 00:31:36.950 --> 00:31:39.609 align:start position:0% sure that actually whatever kicked off this<00:31:37.190> relay<00:31:37.609> happened<00:31:38.330> on<00:31:38.479> the<00:31:38.869> one<00:31:39.320> side<00:31:39.470> of 00:31:39.609 --> 00:31:39.619 align:start position:0% this relay happened on the one side of 00:31:39.619 --> 00:31:41.589 align:start position:0% this relay happened on the one side of the<00:31:39.739> chain<00:31:39.889> thank<00:31:40.639> you<00:31:40.789> thank<00:31:41.299> you<00:31:41.359> for<00:31:41.479> the 00:31:41.589 --> 00:31:41.599 align:start position:0% the chain thank you thank you for the 00:31:41.599 --> 00:31:45.630 align:start position:0% the chain thank you thank you for the question<00:31:41.929> I<00:31:42.440> got<00:31:42.799> a<00:31:42.830> head<00:31:43.070> off<00:31:43.690> thank<00:31:44.690> you 00:31:45.630 --> 00:31:45.640 align:start position:0% question I got a head off thank you 00:31:45.640 --> 00:31:57.650 align:start position:0% question I got a head off thank you [Applause] 00:31:57.650 --> 00:31:57.660 align:start position:0% 00:31:57.660 --> 00:31:59.720 align:start position:0% you