WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:12.730 align:start position:0% [Music] 00:00:12.730 --> 00:00:12.740 align:start position:0% 00:00:12.740 --> 00:00:15.650 align:start position:0% my<00:00:13.740> talk<00:00:13.860> today<00:00:14.099> is<00:00:14.280> going<00:00:14.460> to<00:00:14.519> be<00:00:14.639> about<00:00:14.880> Fast 00:00:15.650 --> 00:00:15.660 align:start position:0% my talk today is going to be about Fast 00:00:15.660 --> 00:00:17.689 align:start position:0% my talk today is going to be about Fast and<00:00:15.900> Furious<00:00:16.199> withdrawals<00:00:16.920> from<00:00:17.100> optimistic 00:00:17.689 --> 00:00:17.699 align:start position:0% and Furious withdrawals from optimistic 00:00:17.699 --> 00:00:20.570 align:start position:0% and Furious withdrawals from optimistic Roll-Ups<00:00:18.240> so<00:00:18.600> a<00:00:19.199> little<00:00:19.320> bit<00:00:19.440> about<00:00:19.500> myself<00:00:19.859> my 00:00:20.570 --> 00:00:20.580 align:start position:0% Roll-Ups so a little bit about myself my 00:00:20.580 --> 00:00:23.150 align:start position:0% Roll-Ups so a little bit about myself my name<00:00:20.640> is<00:00:20.760> Masa<00:00:21.240> and<00:00:21.480> I'm<00:00:21.900> a<00:00:22.140> PhD<00:00:22.560> candidate<00:00:22.980> I'm 00:00:23.150 --> 00:00:23.160 align:start position:0% name is Masa and I'm a PhD candidate I'm 00:00:23.160 --> 00:00:25.490 align:start position:0% name is Masa and I'm a PhD candidate I'm doing<00:00:23.340> PhD<00:00:23.760> at<00:00:23.880> Concordia<00:00:24.359> University<00:00:24.600> with 00:00:25.490 --> 00:00:25.500 align:start position:0% doing PhD at Concordia University with 00:00:25.500 --> 00:00:28.070 align:start position:0% doing PhD at Concordia University with Jeremy<00:00:25.920> Clark<00:00:26.100> and<00:00:26.580> Montreal<00:00:27.119> and<00:00:27.660> I'm<00:00:27.779> also 00:00:28.070 --> 00:00:28.080 align:start position:0% Jeremy Clark and Montreal and I'm also 00:00:28.080 --> 00:00:32.030 align:start position:0% Jeremy Clark and Montreal and I'm also integration<00:00:28.800> engineer<00:00:29.279> at<00:00:29.580> the<00:00:29.699> often<00:00:30.060> labs 00:00:32.030 --> 00:00:32.040 align:start position:0% integration engineer at the often labs 00:00:32.040 --> 00:00:34.250 align:start position:0% integration engineer at the often labs all<00:00:32.640> right<00:00:32.820> so<00:00:33.120> what<00:00:33.600> I'm<00:00:33.780> going<00:00:33.960> to<00:00:34.079> talk 00:00:34.250 --> 00:00:34.260 align:start position:0% all right so what I'm going to talk 00:00:34.260 --> 00:00:36.470 align:start position:0% all right so what I'm going to talk about<00:00:34.380> today<00:00:34.739> is<00:00:35.219> uh<00:00:35.640> research<00:00:36.059> that<00:00:36.239> I<00:00:36.360> was 00:00:36.470 --> 00:00:36.480 align:start position:0% about today is uh research that I was 00:00:36.480 --> 00:00:38.450 align:start position:0% about today is uh research that I was doing<00:00:36.600> during<00:00:36.780> the<00:00:36.960> PHD<00:00:37.380> and<00:00:38.040> it<00:00:38.219> kind<00:00:38.340> of 00:00:38.450 --> 00:00:38.460 align:start position:0% doing during the PHD and it kind of 00:00:38.460 --> 00:00:40.190 align:start position:0% doing during the PHD and it kind of co-located<00:00:39.000> with<00:00:39.360> the<00:00:39.540> time<00:00:39.719> that<00:00:39.899> I<00:00:40.079> was 00:00:40.190 --> 00:00:40.200 align:start position:0% co-located with the time that I was 00:00:40.200 --> 00:00:43.069 align:start position:0% co-located with the time that I was doing<00:00:40.379> uh<00:00:41.040> the<00:00:41.520> job<00:00:41.700> at<00:00:41.940> the<00:00:42.059> off<00:00:42.300> chain<00:00:42.600> so 00:00:43.069 --> 00:00:43.079 align:start position:0% doing uh the job at the off chain so 00:00:43.079 --> 00:00:44.690 align:start position:0% doing uh the job at the off chain so it's<00:00:43.200> kind<00:00:43.440> of<00:00:43.559> a<00:00:43.680> collaboration<00:00:44.100> between<00:00:44.399> the 00:00:44.690 --> 00:00:44.700 align:start position:0% it's kind of a collaboration between the 00:00:44.700 --> 00:00:48.470 align:start position:0% it's kind of a collaboration between the folks<00:00:44.940> at<00:00:45.059> FJ<00:00:45.480> and<00:00:45.719> Korea<00:00:46.379> so<00:00:47.100> it's<00:00:47.879> a<00:00:48.059> research 00:00:48.470 --> 00:00:48.480 align:start position:0% folks at FJ and Korea so it's a research 00:00:48.480 --> 00:00:51.290 align:start position:0% folks at FJ and Korea so it's a research we<00:00:48.840> are<00:00:49.160> particularly<00:00:50.180> interested<00:00:51.180> in 00:00:51.290 --> 00:00:51.300 align:start position:0% we are particularly interested in 00:00:51.300 --> 00:00:53.630 align:start position:0% we are particularly interested in solving<00:00:51.660> a<00:00:51.840> research<00:00:52.140> problem<00:00:52.379> but<00:00:53.160> before<00:00:53.340> I 00:00:53.630 --> 00:00:53.640 align:start position:0% solving a research problem but before I 00:00:53.640 --> 00:00:55.430 align:start position:0% solving a research problem but before I dive<00:00:53.820> into<00:00:54.059> the<00:00:54.300> details<00:00:54.719> of<00:00:54.840> the<00:00:54.960> problem<00:00:55.140> I 00:00:55.430 --> 00:00:55.440 align:start position:0% dive into the details of the problem I 00:00:55.440 --> 00:00:57.229 align:start position:0% dive into the details of the problem I want<00:00:55.620> to<00:00:55.739> take<00:00:55.860> some<00:00:56.039> time<00:00:56.280> and<00:00:56.879> talk<00:00:57.059> about 00:00:57.229 --> 00:00:57.239 align:start position:0% want to take some time and talk about 00:00:57.239 --> 00:01:00.229 align:start position:0% want to take some time and talk about how<00:00:57.899> Roll-Ups<00:00:58.620> work<00:00:58.800> in<00:00:59.160> general<00:00:59.340> and<00:01:00.059> how 00:01:00.229 --> 00:01:00.239 align:start position:0% how Roll-Ups work in general and how 00:01:00.239 --> 00:01:02.630 align:start position:0% how Roll-Ups work in general and how optimistic<00:01:00.780> Roll-Ups<00:01:01.320> work<00:01:01.440> so<00:01:02.160> you<00:01:02.520> might 00:01:02.630 --> 00:01:02.640 align:start position:0% optimistic Roll-Ups work so you might 00:01:02.640 --> 00:01:04.250 align:start position:0% optimistic Roll-Ups work so you might have<00:01:02.879> already<00:01:03.120> heard<00:01:03.420> from<00:01:03.660> other<00:01:03.840> folks 00:01:04.250 --> 00:01:04.260 align:start position:0% have already heard from other folks 00:01:04.260 --> 00:01:05.630 align:start position:0% have already heard from other folks during<00:01:04.440> the<00:01:04.680> conference<00:01:04.979> but<00:01:05.280> it's<00:01:05.460> always 00:01:05.630 --> 00:01:05.640 align:start position:0% during the conference but it's always 00:01:05.640 --> 00:01:07.550 align:start position:0% during the conference but it's always good<00:01:05.880> to<00:01:06.000> keep<00:01:06.119> refreshing<00:01:06.659> and<00:01:06.900> make<00:01:07.380> sure 00:01:07.550 --> 00:01:07.560 align:start position:0% good to keep refreshing and make sure 00:01:07.560 --> 00:01:09.050 align:start position:0% good to keep refreshing and make sure everybody<00:01:07.860> is<00:01:08.159> on<00:01:08.340> board 00:01:09.050 --> 00:01:09.060 align:start position:0% everybody is on board 00:01:09.060 --> 00:01:11.690 align:start position:0% everybody is on board so<00:01:09.600> let's<00:01:09.780> start<00:01:10.020> with<00:01:10.320> the<00:01:10.500> question<00:01:10.740> of<00:01:11.100> why 00:01:11.690 --> 00:01:11.700 align:start position:0% so let's start with the question of why 00:01:11.700 --> 00:01:13.550 align:start position:0% so let's start with the question of why is<00:01:11.880> the<00:01:11.939> term<00:01:12.060> slow<00:01:12.360> and<00:01:12.540> expensive 00:01:13.550 --> 00:01:13.560 align:start position:0% is the term slow and expensive 00:01:13.560 --> 00:01:16.429 align:start position:0% is the term slow and expensive so<00:01:13.920> we<00:01:14.100> know<00:01:14.280> ethereum<00:01:14.700> is<00:01:15.360> slow<00:01:15.659> uh<00:01:16.200> there's 00:01:16.429 --> 00:01:16.439 align:start position:0% so we know ethereum is slow uh there's 00:01:16.439 --> 00:01:18.830 align:start position:0% so we know ethereum is slow uh there's unscalability<00:01:17.220> problem<00:01:17.820> with<00:01:18.180> ethereum<00:01:18.600> and 00:01:18.830 --> 00:01:18.840 align:start position:0% unscalability problem with ethereum and 00:01:18.840 --> 00:01:21.109 align:start position:0% unscalability problem with ethereum and it's<00:01:18.960> really<00:01:19.200> a<00:01:19.439> fundamental<00:01:19.860> issue<00:01:20.220> and<00:01:20.700> why 00:01:21.109 --> 00:01:21.119 align:start position:0% it's really a fundamental issue and why 00:01:21.119 --> 00:01:23.270 align:start position:0% it's really a fundamental issue and why there<00:01:21.540> is<00:01:21.659> a<00:01:21.780> problem<00:01:21.960> is<00:01:22.680> that<00:01:22.799> let's<00:01:22.979> say<00:01:23.100> you 00:01:23.270 --> 00:01:23.280 align:start position:0% there is a problem is that let's say you 00:01:23.280 --> 00:01:24.590 align:start position:0% there is a problem is that let's say you have<00:01:23.400> a<00:01:23.580> function<00:01:23.820> that<00:01:24.060> you<00:01:24.180> want<00:01:24.360> to<00:01:24.479> get 00:01:24.590 --> 00:01:24.600 align:start position:0% have a function that you want to get 00:01:24.600 --> 00:01:27.530 align:start position:0% have a function that you want to get executed<00:01:25.200> on<00:01:25.380> an<00:01:25.500> input<00:01:25.740> X<00:01:25.979> and<00:01:26.759> if<00:01:26.939> it<00:01:27.119> was<00:01:27.299> a 00:01:27.530 --> 00:01:27.540 align:start position:0% executed on an input X and if it was a 00:01:27.540 --> 00:01:29.690 align:start position:0% executed on an input X and if it was a cloud<00:01:27.720> environment<00:01:28.380> the<00:01:29.159> cloud<00:01:29.340> service 00:01:29.690 --> 00:01:29.700 align:start position:0% cloud environment the cloud service 00:01:29.700 --> 00:01:31.850 align:start position:0% cloud environment the cloud service provider<00:01:30.360> would<00:01:30.540> give<00:01:30.780> you<00:01:30.900> the<00:01:31.200> closest<00:01:31.380> node 00:01:31.850 --> 00:01:31.860 align:start position:0% provider would give you the closest node 00:01:31.860 --> 00:01:33.230 align:start position:0% provider would give you the closest node in<00:01:31.979> the<00:01:32.159> network 00:01:33.230 --> 00:01:33.240 align:start position:0% in the network 00:01:33.240 --> 00:01:35.030 align:start position:0% in the network and<00:01:33.600> then<00:01:33.659> what<00:01:33.900> happened<00:01:34.080> is<00:01:34.380> you<00:01:34.619> send<00:01:34.920> the 00:01:35.030 --> 00:01:35.040 align:start position:0% and then what happened is you send the 00:01:35.040 --> 00:01:37.069 align:start position:0% and then what happened is you send the function<00:01:35.280> to<00:01:35.460> the<00:01:35.640> node<00:01:35.820> it<00:01:36.299> would<00:01:36.479> execute 00:01:37.069 --> 00:01:37.079 align:start position:0% function to the node it would execute 00:01:37.079 --> 00:01:39.469 align:start position:0% function to the node it would execute the<00:01:37.740> function<00:01:38.040> for<00:01:38.280> you<00:01:38.460> and<00:01:39.000> it<00:01:39.119> would<00:01:39.240> give 00:01:39.469 --> 00:01:39.479 align:start position:0% the function for you and it would give 00:01:39.479 --> 00:01:41.510 align:start position:0% the function for you and it would give back<00:01:39.780> the<00:01:40.079> results<00:01:40.320> and<00:01:40.740> you<00:01:40.860> learn<00:01:41.040> what<00:01:41.340> the 00:01:41.510 --> 00:01:41.520 align:start position:0% back the results and you learn what the 00:01:41.520 --> 00:01:44.210 align:start position:0% back the results and you learn what the result<00:01:41.640> is<00:01:42.000> but<00:01:42.600> on<00:01:42.780> a<00:01:42.960> blockchain<00:01:43.380> because<00:01:43.860> we 00:01:44.210 --> 00:01:44.220 align:start position:0% result is but on a blockchain because we 00:01:44.220 --> 00:01:46.670 align:start position:0% result is but on a blockchain because we care<00:01:44.400> about<00:01:44.579> trust<00:01:45.119> and<00:01:45.420> integrity<00:01:45.840> we<00:01:46.439> can't 00:01:46.670 --> 00:01:46.680 align:start position:0% care about trust and integrity we can't 00:01:46.680 --> 00:01:48.469 align:start position:0% care about trust and integrity we can't really<00:01:46.860> rely<00:01:47.340> on<00:01:47.520> one<00:01:47.700> node<00:01:47.939> to<00:01:48.119> execute 00:01:48.469 --> 00:01:48.479 align:start position:0% really rely on one node to execute 00:01:48.479 --> 00:01:49.850 align:start position:0% really rely on one node to execute everything<00:01:48.720> for<00:01:49.079> us 00:01:49.850 --> 00:01:49.860 align:start position:0% everything for us 00:01:49.860 --> 00:01:52.190 align:start position:0% everything for us so<00:01:50.340> what<00:01:50.579> happens<00:01:50.700> on<00:01:51.000> a<00:01:51.119> blockchain<00:01:51.479> is<00:01:51.720> you 00:01:52.190 --> 00:01:52.200 align:start position:0% so what happens on a blockchain is you 00:01:52.200 --> 00:01:54.710 align:start position:0% so what happens on a blockchain is you send<00:01:52.380> your<00:01:52.560> function<00:01:52.860> to<00:01:53.100> a<00:01:53.280> node<00:01:53.939> and<00:01:54.540> one 00:01:54.710 --> 00:01:54.720 align:start position:0% send your function to a node and one 00:01:54.720 --> 00:01:56.630 align:start position:0% send your function to a node and one note<00:01:54.899> what<00:01:55.200> that<00:01:55.380> node<00:01:55.680> does<00:01:55.920> is<00:01:56.280> actually 00:01:56.630 --> 00:01:56.640 align:start position:0% note what that node does is actually 00:01:56.640 --> 00:01:59.630 align:start position:0% note what that node does is actually relays<00:01:57.600> your<00:01:58.380> function<00:01:58.920> together<00:01:59.159> with<00:01:59.520> the 00:01:59.630 --> 00:01:59.640 align:start position:0% relays your function together with the 00:01:59.640 --> 00:02:01.130 align:start position:0% relays your function together with the input<00:01:59.880> to<00:02:00.060> all<00:02:00.299> the<00:02:00.420> nodes<00:02:00.600> in<00:02:00.840> the<00:02:00.960> network 00:02:01.130 --> 00:02:01.140 align:start position:0% input to all the nodes in the network 00:02:01.140 --> 00:02:03.649 align:start position:0% input to all the nodes in the network and<00:02:01.680> what<00:02:01.860> happens<00:02:02.040> is<00:02:02.340> then<00:02:02.759> all<00:02:03.299> the<00:02:03.420> nodes 00:02:03.649 --> 00:02:03.659 align:start position:0% and what happens is then all the nodes 00:02:03.659 --> 00:02:06.410 align:start position:0% and what happens is then all the nodes in<00:02:03.840> a<00:02:04.020> network<00:02:04.159> execute<00:02:05.159> your<00:02:05.340> function<00:02:05.700> so 00:02:06.410 --> 00:02:06.420 align:start position:0% in a network execute your function so 00:02:06.420 --> 00:02:08.029 align:start position:0% in a network execute your function so it's<00:02:06.600> literally<00:02:06.899> like<00:02:07.140> you<00:02:07.320> have<00:02:07.500> to<00:02:07.619> pay<00:02:07.799> for 00:02:08.029 --> 00:02:08.039 align:start position:0% it's literally like you have to pay for 00:02:08.039 --> 00:02:09.650 align:start position:0% it's literally like you have to pay for each<00:02:08.340> and<00:02:08.520> every<00:02:08.700> node<00:02:09.000> executing<00:02:09.539> the 00:02:09.650 --> 00:02:09.660 align:start position:0% each and every node executing the 00:02:09.660 --> 00:02:11.690 align:start position:0% each and every node executing the function<00:02:09.959> for<00:02:10.259> you<00:02:10.440> and<00:02:10.920> then<00:02:11.099> it<00:02:11.400> takes<00:02:11.520> some 00:02:11.690 --> 00:02:11.700 align:start position:0% function for you and then it takes some 00:02:11.700 --> 00:02:13.309 align:start position:0% function for you and then it takes some time<00:02:11.879> because<00:02:12.060> they<00:02:12.360> have<00:02:12.540> to<00:02:12.780> run<00:02:13.020> a 00:02:13.309 --> 00:02:13.319 align:start position:0% time because they have to run a 00:02:13.319 --> 00:02:15.589 align:start position:0% time because they have to run a consensus<00:02:13.739> algorithm<00:02:14.280> among<00:02:14.700> each<00:02:14.819> other<00:02:15.060> so 00:02:15.589 --> 00:02:15.599 align:start position:0% consensus algorithm among each other so 00:02:15.599 --> 00:02:17.210 align:start position:0% consensus algorithm among each other so that<00:02:15.780> they<00:02:15.900> could<00:02:16.080> all<00:02:16.319> agree<00:02:16.680> on<00:02:16.860> the<00:02:17.040> same 00:02:17.210 --> 00:02:17.220 align:start position:0% that they could all agree on the same 00:02:17.220 --> 00:02:19.490 align:start position:0% that they could all agree on the same output<00:02:17.580> and<00:02:18.120> it's<00:02:18.300> only<00:02:18.540> that<00:02:18.959> moment<00:02:19.260> that 00:02:19.490 --> 00:02:19.500 align:start position:0% output and it's only that moment that 00:02:19.500 --> 00:02:21.410 align:start position:0% output and it's only that moment that you<00:02:19.680> can<00:02:19.800> learn<00:02:19.980> the<00:02:20.220> result<00:02:20.459> so<00:02:21.239> that's 00:02:21.410 --> 00:02:21.420 align:start position:0% you can learn the result so that's 00:02:21.420 --> 00:02:23.809 align:start position:0% you can learn the result so that's that's<00:02:21.780> uh<00:02:22.200> that's<00:02:22.680> really<00:02:22.860> why<00:02:23.340> it's<00:02:23.580> so 00:02:23.809 --> 00:02:23.819 align:start position:0% that's uh that's really why it's so 00:02:23.819 --> 00:02:25.309 align:start position:0% that's uh that's really why it's so inexpensive 00:02:25.309 --> 00:02:25.319 align:start position:0% inexpensive 00:02:25.319 --> 00:02:28.610 align:start position:0% inexpensive okay<00:02:25.920> so<00:02:26.220> but<00:02:26.580> why<00:02:27.420> is<00:02:27.599> it<00:02:27.780> that<00:02:28.080> every<00:02:28.379> node 00:02:28.610 --> 00:02:28.620 align:start position:0% okay so but why is it that every node 00:02:28.620 --> 00:02:30.650 align:start position:0% okay so but why is it that every node has<00:02:28.920> to<00:02:29.040> compute<00:02:29.459> everything<00:02:29.700> so<00:02:30.360> the<00:02:30.540> answer 00:02:30.650 --> 00:02:30.660 align:start position:0% has to compute everything so the answer 00:02:30.660 --> 00:02:32.210 align:start position:0% has to compute everything so the answer is<00:02:30.900> because<00:02:31.140> they<00:02:31.440> have<00:02:31.560> to<00:02:31.739> make<00:02:31.860> sure<00:02:32.040> that 00:02:32.210 --> 00:02:32.220 align:start position:0% is because they have to make sure that 00:02:32.220 --> 00:02:34.070 align:start position:0% is because they have to make sure that it's<00:02:32.400> the<00:02:32.580> correct<00:02:32.879> thing<00:02:33.060> so<00:02:33.540> let's<00:02:33.660> say<00:02:33.840> I 00:02:34.070 --> 00:02:34.080 align:start position:0% it's the correct thing so let's say I 00:02:34.080 --> 00:02:35.809 align:start position:0% it's the correct thing so let's say I have<00:02:34.200> a<00:02:34.319> function<00:02:34.560> I<00:02:34.800> execute<00:02:35.220> it<00:02:35.340> for<00:02:35.459> you<00:02:35.580> and 00:02:35.809 --> 00:02:35.819 align:start position:0% have a function I execute it for you and 00:02:35.819 --> 00:02:37.250 align:start position:0% have a function I execute it for you and then<00:02:35.940> I<00:02:36.120> come<00:02:36.180> to<00:02:36.300> you<00:02:36.480> and<00:02:36.540> I'm<00:02:36.660> like<00:02:36.840> here's 00:02:37.250 --> 00:02:37.260 align:start position:0% then I come to you and I'm like here's 00:02:37.260 --> 00:02:39.110 align:start position:0% then I come to you and I'm like here's the<00:02:37.379> output<00:02:37.739> so<00:02:38.340> what<00:02:38.520> is<00:02:38.700> the<00:02:38.940> most 00:02:39.110 --> 00:02:39.120 align:start position:0% the output so what is the most 00:02:39.120 --> 00:02:41.509 align:start position:0% the output so what is the most straightforward<00:02:39.840> way<00:02:40.080> to<00:02:40.319> for<00:02:40.680> you<00:02:40.920> to 00:02:41.509 --> 00:02:41.519 align:start position:0% straightforward way to for you to 00:02:41.519 --> 00:02:43.369 align:start position:0% straightforward way to for you to actually<00:02:41.700> verify<00:02:42.360> if<00:02:42.599> I'm<00:02:42.780> saying<00:02:43.200> the 00:02:43.369 --> 00:02:43.379 align:start position:0% actually verify if I'm saying the 00:02:43.379 --> 00:02:45.530 align:start position:0% actually verify if I'm saying the correct<00:02:43.739> thing<00:02:43.920> so<00:02:44.819> you<00:02:45.000> have<00:02:45.120> to<00:02:45.239> go<00:02:45.360> and 00:02:45.530 --> 00:02:45.540 align:start position:0% correct thing so you have to go and 00:02:45.540 --> 00:02:48.110 align:start position:0% correct thing so you have to go and compute<00:02:46.080> the<00:02:46.200> function<00:02:46.560> yourself<00:02:46.800> right<00:02:47.220> so 00:02:48.110 --> 00:02:48.120 align:start position:0% compute the function yourself right so 00:02:48.120 --> 00:02:50.690 align:start position:0% compute the function yourself right so the<00:02:48.660> question<00:02:48.900> people<00:02:49.319> have<00:02:49.680> been<00:02:49.860> asking<00:02:50.340> in 00:02:50.690 --> 00:02:50.700 align:start position:0% the question people have been asking in 00:02:50.700 --> 00:02:52.910 align:start position:0% the question people have been asking in terms<00:02:50.879> of<00:02:51.000> scalability<00:02:51.660> of<00:02:52.019> ethereum<00:02:52.440> is<00:02:52.680> that 00:02:52.910 --> 00:02:52.920 align:start position:0% terms of scalability of ethereum is that 00:02:52.920 --> 00:02:55.790 align:start position:0% terms of scalability of ethereum is that is<00:02:53.340> there<00:02:53.519> any<00:02:53.819> way<00:02:54.120> I<00:02:54.660> can<00:02:54.780> convince<00:02:55.260> you<00:02:55.379> that 00:02:55.790 --> 00:02:55.800 align:start position:0% is there any way I can convince you that 00:02:55.800 --> 00:02:58.130 align:start position:0% is there any way I can convince you that I've<00:02:56.099> done<00:02:56.340> the<00:02:56.580> execution<00:02:57.120> correct<00:02:57.660> without 00:02:58.130 --> 00:02:58.140 align:start position:0% I've done the execution correct without 00:02:58.140 --> 00:03:00.589 align:start position:0% I've done the execution correct without you<00:02:58.620> having<00:02:58.860> to<00:02:59.160> go<00:02:59.400> and<00:02:59.879> execute<00:03:00.300> everything 00:03:00.589 --> 00:03:00.599 align:start position:0% you having to go and execute everything 00:03:00.599 --> 00:03:03.530 align:start position:0% you having to go and execute everything yourself 00:03:03.530 --> 00:03:03.540 align:start position:0% 00:03:03.540 --> 00:03:05.630 align:start position:0% so<00:03:04.140> there<00:03:04.440> are<00:03:04.620> two<00:03:04.800> main<00:03:04.980> approaches<00:03:05.459> to 00:03:05.630 --> 00:03:05.640 align:start position:0% so there are two main approaches to 00:03:05.640 --> 00:03:07.729 align:start position:0% so there are two main approaches to tackle<00:03:06.000> this<00:03:06.180> problem<00:03:06.420> the<00:03:07.019> first<00:03:07.140> one<00:03:07.319> is<00:03:07.500> you 00:03:07.729 --> 00:03:07.739 align:start position:0% tackle this problem the first one is you 00:03:07.739 --> 00:03:09.470 align:start position:0% tackle this problem the first one is you can<00:03:07.860> actually<00:03:08.040> throw<00:03:08.459> some<00:03:08.700> math<00:03:08.940> at<00:03:09.360> a 00:03:09.470 --> 00:03:09.480 align:start position:0% can actually throw some math at a 00:03:09.480 --> 00:03:11.449 align:start position:0% can actually throw some math at a problem<00:03:09.660> and<00:03:10.379> you<00:03:10.560> create<00:03:10.739> kind<00:03:11.099> of<00:03:11.220> a 00:03:11.449 --> 00:03:11.459 align:start position:0% problem and you create kind of a 00:03:11.459 --> 00:03:13.790 align:start position:0% problem and you create kind of a mathematical<00:03:12.000> proof<00:03:12.480> so<00:03:13.019> you<00:03:13.200> run<00:03:13.379> a<00:03:13.560> function 00:03:13.790 --> 00:03:13.800 align:start position:0% mathematical proof so you run a function 00:03:13.800 --> 00:03:16.309 align:start position:0% mathematical proof so you run a function you<00:03:13.980> get<00:03:14.159> the<00:03:14.280> output<00:03:14.580> and<00:03:14.940> you<00:03:15.120> then<00:03:15.540> you<00:03:15.900> kind 00:03:16.309 --> 00:03:16.319 align:start position:0% you get the output and you then you kind 00:03:16.319 --> 00:03:18.589 align:start position:0% you get the output and you then you kind of<00:03:16.440> create<00:03:16.680> a<00:03:17.040> cryptography<00:03:17.640> proof<00:03:18.000> you<00:03:18.420> hand 00:03:18.589 --> 00:03:18.599 align:start position:0% of create a cryptography proof you hand 00:03:18.599 --> 00:03:21.470 align:start position:0% of create a cryptography proof you hand it<00:03:18.780> to<00:03:18.959> me<00:03:19.140> and<00:03:19.319> then<00:03:19.620> I<00:03:20.580> can<00:03:20.700> actually<00:03:20.940> verify 00:03:21.470 --> 00:03:21.480 align:start position:0% it to me and then I can actually verify 00:03:21.480 --> 00:03:22.729 align:start position:0% it to me and then I can actually verify the<00:03:21.599> proof<00:03:21.900> and<00:03:22.019> see<00:03:22.200> if<00:03:22.319> it's<00:03:22.440> a<00:03:22.620> correct 00:03:22.729 --> 00:03:22.739 align:start position:0% the proof and see if it's a correct 00:03:22.739 --> 00:03:25.729 align:start position:0% the proof and see if it's a correct thing<00:03:22.920> or<00:03:23.099> not<00:03:23.220> so<00:03:23.760> very<00:03:24.540> if<00:03:24.780> like<00:03:25.140> verifying 00:03:25.729 --> 00:03:25.739 align:start position:0% thing or not so very if like verifying 00:03:25.739 --> 00:03:27.830 align:start position:0% thing or not so very if like verifying the<00:03:25.800> proof<00:03:26.159> is<00:03:26.519> less<00:03:26.819> work<00:03:27.120> than<00:03:27.540> actually 00:03:27.830 --> 00:03:27.840 align:start position:0% the proof is less work than actually 00:03:27.840 --> 00:03:30.229 align:start position:0% the proof is less work than actually having<00:03:28.140> to<00:03:28.379> execute<00:03:28.800> everything<00:03:29.099> then<00:03:29.940> I 00:03:30.229 --> 00:03:30.239 align:start position:0% having to execute everything then I 00:03:30.239 --> 00:03:32.449 align:start position:0% having to execute everything then I actually<00:03:30.599> save<00:03:31.019> some<00:03:31.620> money<00:03:31.800> and<00:03:32.040> time<00:03:32.220> right 00:03:32.449 --> 00:03:32.459 align:start position:0% actually save some money and time right 00:03:32.459 --> 00:03:35.030 align:start position:0% actually save some money and time right so<00:03:32.879> this<00:03:33.060> is<00:03:33.180> how<00:03:33.360> ZK<00:03:33.780> Roll-Ups<00:03:34.260> work<00:03:34.500> on<00:03:34.920> a 00:03:35.030 --> 00:03:35.040 align:start position:0% so this is how ZK Roll-Ups work on a 00:03:35.040 --> 00:03:35.930 align:start position:0% so this is how ZK Roll-Ups work on a high<00:03:35.159> level 00:03:35.930 --> 00:03:35.940 align:start position:0% high level 00:03:35.940 --> 00:03:38.809 align:start position:0% high level so<00:03:36.480> the<00:03:36.659> way<00:03:36.840> SDK<00:03:37.319> roll-up<00:03:37.680> work<00:03:37.860> is 00:03:38.809 --> 00:03:38.819 align:start position:0% so the way SDK roll-up work is 00:03:38.819 --> 00:03:40.789 align:start position:0% so the way SDK roll-up work is he<00:03:39.360> actually<00:03:39.540> sent<00:03:39.840> a<00:03:39.959> function<00:03:40.200> to<00:03:40.379> a<00:03:40.560> node 00:03:40.789 --> 00:03:40.799 align:start position:0% he actually sent a function to a node 00:03:40.799 --> 00:03:42.710 align:start position:0% he actually sent a function to a node the<00:03:41.159> node<00:03:41.340> would<00:03:41.580> execute<00:03:41.940> it<00:03:42.120> for<00:03:42.239> you<00:03:42.420> and 00:03:42.710 --> 00:03:42.720 align:start position:0% the node would execute it for you and 00:03:42.720 --> 00:03:45.530 align:start position:0% the node would execute it for you and then<00:03:42.900> they<00:03:43.680> create<00:03:43.920> a<00:03:44.400> cryptographic<00:03:45.120> proof 00:03:45.530 --> 00:03:45.540 align:start position:0% then they create a cryptographic proof 00:03:45.540 --> 00:03:48.110 align:start position:0% then they create a cryptographic proof saying<00:03:45.959> that<00:03:46.140> this<00:03:46.379> is<00:03:46.500> a<00:03:46.680> correct<00:03:46.860> output<00:03:47.280> now 00:03:48.110 --> 00:03:48.120 align:start position:0% saying that this is a correct output now 00:03:48.120 --> 00:03:50.089 align:start position:0% saying that this is a correct output now generation<00:03:48.659> of<00:03:49.019> this<00:03:49.200> proof<00:03:49.560> takes<00:03:49.799> a<00:03:49.920> long 00:03:50.089 --> 00:03:50.099 align:start position:0% generation of this proof takes a long 00:03:50.099 --> 00:03:52.490 align:start position:0% generation of this proof takes a long time<00:03:50.280> it<00:03:50.879> even<00:03:51.000> takes<00:03:51.299> like<00:03:51.540> 1000<00:03:52.019> times<00:03:52.200> or 00:03:52.490 --> 00:03:52.500 align:start position:0% time it even takes like 1000 times or 00:03:52.500 --> 00:03:54.589 align:start position:0% time it even takes like 1000 times or even<00:03:52.620> million<00:03:53.099> times<00:03:53.280> longer<00:03:53.760> than<00:03:54.000> when<00:03:54.360> you 00:03:54.589 --> 00:03:54.599 align:start position:0% even million times longer than when you 00:03:54.599 --> 00:03:56.149 align:start position:0% even million times longer than when you have<00:03:54.780> to<00:03:55.019> like<00:03:55.200> compute<00:03:55.560> a<00:03:55.680> function<00:03:55.920> yourself 00:03:56.149 --> 00:03:56.159 align:start position:0% have to like compute a function yourself 00:03:56.159 --> 00:03:59.390 align:start position:0% have to like compute a function yourself so<00:03:57.060> that's<00:03:57.180> kind<00:03:57.480> of<00:03:57.540> a<00:03:57.659> hidden<00:03:57.959> cost<00:03:58.080> but<00:03:59.040> if 00:03:59.390 --> 00:03:59.400 align:start position:0% so that's kind of a hidden cost but if 00:03:59.400 --> 00:04:01.970 align:start position:0% so that's kind of a hidden cost but if like<00:03:59.640> once<00:04:00.060> you<00:04:00.239> have<00:04:00.420> the<00:04:00.780> the<00:04:01.260> proof<00:04:01.680> in<00:04:01.799> hand 00:04:01.970 --> 00:04:01.980 align:start position:0% like once you have the the proof in hand 00:04:01.980 --> 00:04:04.070 align:start position:0% like once you have the the proof in hand you<00:04:02.459> can<00:04:02.580> actually<00:04:02.700> go<00:04:03.120> and<00:04:03.299> send<00:04:03.540> it<00:04:03.720> to<00:04:03.900> the 00:04:04.070 --> 00:04:04.080 align:start position:0% you can actually go and send it to the 00:04:04.080 --> 00:04:06.410 align:start position:0% you can actually go and send it to the network<00:04:04.260> and<00:04:04.799> then<00:04:05.040> verifying<00:04:05.879> the<00:04:06.060> proof<00:04:06.299> is 00:04:06.410 --> 00:04:06.420 align:start position:0% network and then verifying the proof is 00:04:06.420 --> 00:04:09.649 align:start position:0% network and then verifying the proof is really<00:04:06.659> nothing<00:04:07.099> so<00:04:08.099> it's<00:04:08.400> really<00:04:09.060> a<00:04:09.480> cost 00:04:09.649 --> 00:04:09.659 align:start position:0% really nothing so it's really a cost 00:04:09.659 --> 00:04:11.929 align:start position:0% really nothing so it's really a cost effective<00:04:10.260> solution<00:04:10.680> especially<00:04:11.519> if<00:04:11.760> you're 00:04:11.929 --> 00:04:11.939 align:start position:0% effective solution especially if you're 00:04:11.939 --> 00:04:14.809 align:start position:0% effective solution especially if you're one<00:04:12.180> of<00:04:12.360> those<00:04:12.659> nodes<00:04:12.959> that<00:04:13.379> have<00:04:13.620> to<00:04:13.920> verify 00:04:14.809 --> 00:04:14.819 align:start position:0% one of those nodes that have to verify 00:04:14.819 --> 00:04:17.150 align:start position:0% one of those nodes that have to verify those<00:04:15.360> proof 00:04:17.150 --> 00:04:17.160 align:start position:0% those proof 00:04:17.160 --> 00:04:20.210 align:start position:0% those proof and<00:04:18.060> the<00:04:18.600> second<00:04:18.720> solution<00:04:19.139> is<00:04:19.500> to<00:04:19.799> use<00:04:19.979> kind 00:04:20.210 --> 00:04:20.220 align:start position:0% and the second solution is to use kind 00:04:20.220 --> 00:04:22.850 align:start position:0% and the second solution is to use kind of<00:04:20.340> like<00:04:20.400> economics<00:04:21.120> so<00:04:21.600> I'm<00:04:21.840> like<00:04:22.079> I<00:04:22.500> execute 00:04:22.850 --> 00:04:22.860 align:start position:0% of like economics so I'm like I execute 00:04:22.860 --> 00:04:24.710 align:start position:0% of like economics so I'm like I execute this<00:04:23.040> function<00:04:23.400> and<00:04:23.759> here's<00:04:24.000> the<00:04:24.120> output<00:04:24.419> and 00:04:24.710 --> 00:04:24.720 align:start position:0% this function and here's the output and 00:04:24.720 --> 00:04:26.770 align:start position:0% this function and here's the output and here's<00:04:25.080> a<00:04:25.199> million<00:04:25.620> dollar<00:04:25.740> worth<00:04:26.160> of<00:04:26.400> eth 00:04:26.770 --> 00:04:26.780 align:start position:0% here's a million dollar worth of eth 00:04:26.780 --> 00:04:30.110 align:start position:0% here's a million dollar worth of eth packing<00:04:27.780> uh<00:04:28.320> my<00:04:28.560> assertion<00:04:29.040> and<00:04:29.699> it's<00:04:29.940> open 00:04:30.110 --> 00:04:30.120 align:start position:0% packing uh my assertion and it's open 00:04:30.120 --> 00:04:32.090 align:start position:0% packing uh my assertion and it's open for<00:04:30.419> you<00:04:30.540> to<00:04:30.720> dispute<00:04:31.199> anybody<00:04:31.680> can<00:04:31.919> come 00:04:32.090 --> 00:04:32.100 align:start position:0% for you to dispute anybody can come 00:04:32.100 --> 00:04:33.890 align:start position:0% for you to dispute anybody can come along<00:04:32.280> and<00:04:32.639> they<00:04:32.820> can<00:04:33.000> prove<00:04:33.300> that<00:04:33.479> it's<00:04:33.660> the 00:04:33.890 --> 00:04:33.900 align:start position:0% along and they can prove that it's the 00:04:33.900 --> 00:04:35.930 align:start position:0% along and they can prove that it's the wrong<00:04:34.020> output<00:04:34.500> but<00:04:35.100> they<00:04:35.400> have<00:04:35.520> to<00:04:35.639> stake 00:04:35.930 --> 00:04:35.940 align:start position:0% wrong output but they have to stake 00:04:35.940 --> 00:04:38.030 align:start position:0% wrong output but they have to stake money<00:04:36.120> as<00:04:36.360> well<00:04:36.540> so<00:04:37.320> the<00:04:37.440> way<00:04:37.620> it<00:04:37.740> works<00:04:37.979> is 00:04:38.030 --> 00:04:38.040 align:start position:0% money as well so the way it works is 00:04:38.040 --> 00:04:39.050 align:start position:0% money as well so the way it works is let's<00:04:38.280> say 00:04:39.050 --> 00:04:39.060 align:start position:0% let's say 00:04:39.060 --> 00:04:41.629 align:start position:0% let's say Alice<00:04:39.660> is<00:04:39.780> saying<00:04:40.020> what<00:04:40.139> apple<00:04:40.380> is<00:04:40.740> right<00:04:40.860> uh 00:04:41.629 --> 00:04:41.639 align:start position:0% Alice is saying what apple is right uh 00:04:41.639 --> 00:04:44.150 align:start position:0% Alice is saying what apple is right uh Bob<00:04:42.479> is<00:04:42.600> saying<00:04:42.840> the<00:04:42.960> other<00:04:43.080> output<00:04:43.620> is<00:04:43.860> right 00:04:44.150 --> 00:04:44.160 align:start position:0% Bob is saying the other output is right 00:04:44.160 --> 00:04:47.330 align:start position:0% Bob is saying the other output is right and<00:04:44.699> then<00:04:44.880> uh<00:04:45.840> there's<00:04:46.560> a<00:04:46.740> dispute<00:04:47.100> and 00:04:47.330 --> 00:04:47.340 align:start position:0% and then uh there's a dispute and 00:04:47.340 --> 00:04:49.430 align:start position:0% and then uh there's a dispute and disagreement<00:04:47.820> right<00:04:48.060> and<00:04:48.600> it's<00:04:48.720> only<00:04:48.960> in<00:04:49.259> that 00:04:49.430 --> 00:04:49.440 align:start position:0% disagreement right and it's only in that 00:04:49.440 --> 00:04:51.650 align:start position:0% disagreement right and it's only in that point<00:04:49.620> that<00:04:49.979> ethereum<00:04:50.520> goes<00:04:50.940> back<00:04:51.120> to<00:04:51.479> a 00:04:51.650 --> 00:04:51.660 align:start position:0% point that ethereum goes back to a 00:04:51.660 --> 00:04:54.290 align:start position:0% point that ethereum goes back to a normal<00:04:51.900> blockchain<00:04:52.560> mode<00:04:52.979> where<00:04:53.759> every<00:04:54.000> node 00:04:54.290 --> 00:04:54.300 align:start position:0% normal blockchain mode where every node 00:04:54.300 --> 00:04:58.189 align:start position:0% normal blockchain mode where every node has<00:04:54.540> to<00:04:54.720> execute<00:04:55.320> everything<00:04:55.620> so<00:04:56.660> uh<00:04:57.660> this<00:04:58.080> is 00:04:58.189 --> 00:04:58.199 align:start position:0% has to execute everything so uh this is 00:04:58.199 --> 00:05:00.530 align:start position:0% has to execute everything so uh this is how<00:04:58.320> optimistic<00:04:58.860> rollups<00:04:59.340> work<00:04:59.520> and<00:05:00.060> we<00:05:00.360> call 00:05:00.530 --> 00:05:00.540 align:start position:0% how optimistic rollups work and we call 00:05:00.540 --> 00:05:02.170 align:start position:0% how optimistic rollups work and we call it<00:05:00.660> optimistic<00:05:01.199> because 00:05:02.170 --> 00:05:02.180 align:start position:0% it optimistic because 00:05:02.180 --> 00:05:05.870 align:start position:0% it optimistic because because<00:05:03.199> we're<00:05:04.199> really<00:05:04.380> optimistic<00:05:04.919> that<00:05:05.220> not 00:05:05.870 --> 00:05:05.880 align:start position:0% because we're really optimistic that not 00:05:05.880 --> 00:05:08.150 align:start position:0% because we're really optimistic that not every<00:05:06.060> node<00:05:06.419> has<00:05:06.660> to<00:05:06.919> compute<00:05:07.919> everything 00:05:08.150 --> 00:05:08.160 align:start position:0% every node has to compute everything 00:05:08.160 --> 00:05:10.129 align:start position:0% every node has to compute everything because 00:05:10.129 --> 00:05:10.139 align:start position:0% because 00:05:10.139 --> 00:05:12.530 align:start position:0% because it<00:05:10.680> really<00:05:10.919> notes<00:05:11.460> always<00:05:11.639> assert<00:05:12.240> the<00:05:12.419> right 00:05:12.530 --> 00:05:12.540 align:start position:0% it really notes always assert the right 00:05:12.540 --> 00:05:15.590 align:start position:0% it really notes always assert the right output<00:05:12.900> and<00:05:13.139> you<00:05:13.320> see<00:05:13.620> why 00:05:15.590 --> 00:05:15.600 align:start position:0% output and you see why 00:05:15.600 --> 00:05:18.170 align:start position:0% output and you see why so<00:05:16.199> the<00:05:16.320> way<00:05:16.500> an<00:05:16.740> optimistic<00:05:17.220> rollups<00:05:17.699> work<00:05:17.820> is 00:05:18.170 --> 00:05:18.180 align:start position:0% so the way an optimistic rollups work is 00:05:18.180 --> 00:05:19.850 align:start position:0% so the way an optimistic rollups work is that<00:05:18.540> uh 00:05:19.850 --> 00:05:19.860 align:start position:0% that uh 00:05:19.860 --> 00:05:22.430 align:start position:0% that uh I<00:05:20.460> I<00:05:20.460> execute<00:05:21.120> a<00:05:21.240> function<00:05:21.540> and<00:05:21.900> I<00:05:22.139> put<00:05:22.259> an 00:05:22.430 --> 00:05:22.440 align:start position:0% I I execute a function and I put an 00:05:22.440 --> 00:05:24.950 align:start position:0% I I execute a function and I put an assertion<00:05:22.919> I<00:05:23.340> stick<00:05:23.639> on<00:05:23.940> that<00:05:24.060> and<00:05:24.660> let's<00:05:24.780> say 00:05:24.950 --> 00:05:24.960 align:start position:0% assertion I stick on that and let's say 00:05:24.960 --> 00:05:27.170 align:start position:0% assertion I stick on that and let's say Bobby's<00:05:25.560> come<00:05:25.740> coming<00:05:25.979> and<00:05:26.460> he<00:05:26.580> says<00:05:26.820> this<00:05:27.120> is 00:05:27.170 --> 00:05:27.180 align:start position:0% Bobby's come coming and he says this is 00:05:27.180 --> 00:05:29.270 align:start position:0% Bobby's come coming and he says this is the<00:05:27.360> wrong<00:05:27.539> output<00:05:27.960> so<00:05:28.320> he<00:05:28.500> finds<00:05:28.860> a<00:05:28.919> dispute 00:05:29.270 --> 00:05:29.280 align:start position:0% the wrong output so he finds a dispute 00:05:29.280 --> 00:05:31.370 align:start position:0% the wrong output so he finds a dispute so<00:05:29.940> what<00:05:30.060> happens<00:05:30.240> is<00:05:30.539> ethereum<00:05:31.080> would<00:05:31.199> be 00:05:31.370 --> 00:05:31.380 align:start position:0% so what happens is ethereum would be 00:05:31.380 --> 00:05:34.010 align:start position:0% so what happens is ethereum would be like<00:05:31.560> hey<00:05:32.160> I<00:05:32.520> know<00:05:32.699> you<00:05:32.940> guys<00:05:33.180> are<00:05:33.360> disagreeing 00:05:34.010 --> 00:05:34.020 align:start position:0% like hey I know you guys are disagreeing 00:05:34.020 --> 00:05:36.890 align:start position:0% like hey I know you guys are disagreeing on<00:05:34.259> this<00:05:34.440> output<00:05:34.800> I<00:05:35.639> want<00:05:35.820> you<00:05:36.000> to<00:05:36.240> pinpoint<00:05:36.660> me 00:05:36.890 --> 00:05:36.900 align:start position:0% on this output I want you to pinpoint me 00:05:36.900 --> 00:05:39.290 align:start position:0% on this output I want you to pinpoint me to<00:05:37.259> the<00:05:37.500> exact<00:05:37.919> step<00:05:38.280> inside<00:05:38.639> the<00:05:38.880> computation 00:05:39.290 --> 00:05:39.300 align:start position:0% to the exact step inside the computation 00:05:39.300 --> 00:05:41.510 align:start position:0% to the exact step inside the computation where<00:05:39.660> you<00:05:39.840> started<00:05:40.139> to<00:05:40.259> disagree<00:05:40.680> so<00:05:41.340> maybe 00:05:41.510 --> 00:05:41.520 align:start position:0% where you started to disagree so maybe 00:05:41.520 --> 00:05:44.450 align:start position:0% where you started to disagree so maybe you<00:05:42.120> were<00:05:42.300> fine<00:05:42.720> for<00:05:43.199> the<00:05:43.380> first<00:05:43.500> 30<00:05:43.740> of<00:05:44.340> the 00:05:44.450 --> 00:05:44.460 align:start position:0% you were fine for the first 30 of the 00:05:44.460 --> 00:05:46.310 align:start position:0% you were fine for the first 30 of the computation<00:05:44.940> and<00:05:45.419> it's<00:05:45.600> only<00:05:45.780> this<00:05:46.139> little 00:05:46.310 --> 00:05:46.320 align:start position:0% computation and it's only this little 00:05:46.320 --> 00:05:48.770 align:start position:0% computation and it's only this little step<00:05:46.680> where<00:05:47.160> you<00:05:47.340> started<00:05:47.699> to<00:05:47.820> disagree<00:05:48.300> so 00:05:48.770 --> 00:05:48.780 align:start position:0% step where you started to disagree so 00:05:48.780 --> 00:05:50.510 align:start position:0% step where you started to disagree so it's<00:05:48.960> actually<00:05:49.199> going<00:05:49.560> to<00:05:49.800> verify<00:05:50.280> that 00:05:50.510 --> 00:05:50.520 align:start position:0% it's actually going to verify that 00:05:50.520 --> 00:05:52.310 align:start position:0% it's actually going to verify that little<00:05:50.759> step<00:05:51.120> so<00:05:51.360> it<00:05:51.539> ends<00:05:51.780> up<00:05:51.840> being<00:05:52.020> very 00:05:52.310 --> 00:05:52.320 align:start position:0% little step so it ends up being very 00:05:52.320 --> 00:05:54.710 align:start position:0% little step so it ends up being very cost<00:05:52.500> effective<00:05:53.039> even<00:05:53.820> if<00:05:54.000> ethereum<00:05:54.419> has<00:05:54.600> to 00:05:54.710 --> 00:05:54.720 align:start position:0% cost effective even if ethereum has to 00:05:54.720 --> 00:05:55.670 align:start position:0% cost effective even if ethereum has to step<00:05:54.900> in 00:05:55.670 --> 00:05:55.680 align:start position:0% step in 00:05:55.680 --> 00:05:58.790 align:start position:0% step in and<00:05:56.400> that's<00:05:56.759> why<00:05:56.940> actually<00:05:57.180> it's<00:05:57.960> near<00:05:58.199> really 00:05:58.790 --> 00:05:58.800 align:start position:0% and that's why actually it's near really 00:05:58.800 --> 00:06:01.070 align:start position:0% and that's why actually it's near really not<00:05:59.160> easy<00:05:59.400> to<00:05:59.820> get<00:06:00.000> away<00:06:00.479> with<00:06:00.780> the<00:06:00.960> wrong 00:06:01.070 --> 00:06:01.080 align:start position:0% not easy to get away with the wrong 00:06:01.080 --> 00:06:03.170 align:start position:0% not easy to get away with the wrong output<00:06:01.500> because<00:06:01.979> everybody<00:06:02.340> knows<00:06:02.880> that<00:06:03.000> at 00:06:03.170 --> 00:06:03.180 align:start position:0% output because everybody knows that at 00:06:03.180 --> 00:06:05.029 align:start position:0% output because everybody knows that at the<00:06:03.300> end<00:06:03.419> of<00:06:03.539> the<00:06:03.660> day<00:06:03.780> a<00:06:04.259> term<00:06:04.440> can<00:06:04.740> come<00:06:04.860> along 00:06:05.029 --> 00:06:05.039 align:start position:0% the end of the day a term can come along 00:06:05.039 --> 00:06:06.770 align:start position:0% the end of the day a term can come along and<00:06:05.280> it<00:06:05.400> can<00:06:05.520> settle<00:06:05.880> things<00:06:06.060> and<00:06:06.539> you<00:06:06.720> can 00:06:06.770 --> 00:06:06.780 align:start position:0% and it can settle things and you can 00:06:06.780 --> 00:06:10.570 align:start position:0% and it can settle things and you can lose<00:06:07.020> money<00:06:07.320> and<00:06:08.100> then<00:06:08.340> uh<00:06:09.240> yeah<00:06:09.660> and<00:06:10.440> then 00:06:10.570 --> 00:06:10.580 align:start position:0% lose money and then uh yeah and then 00:06:10.580 --> 00:06:13.610 align:start position:0% lose money and then uh yeah and then that's<00:06:11.580> why<00:06:11.820> actually<00:06:12.120> the<00:06:12.840> only<00:06:12.960> way<00:06:13.259> you<00:06:13.500> can 00:06:13.610 --> 00:06:13.620 align:start position:0% that's why actually the only way you can 00:06:13.620 --> 00:06:15.529 align:start position:0% that's why actually the only way you can get<00:06:13.800> away<00:06:14.039> with<00:06:14.340> the<00:06:14.520> wrong<00:06:14.699> output<00:06:15.120> is<00:06:15.360> that 00:06:15.529 --> 00:06:15.539 align:start position:0% get away with the wrong output is that 00:06:15.539 --> 00:06:17.570 align:start position:0% get away with the wrong output is that nobody<00:06:15.780> is<00:06:15.960> watching<00:06:16.199> the<00:06:16.320> protocol<00:06:16.620> so<00:06:17.340> at 00:06:17.570 --> 00:06:17.580 align:start position:0% nobody is watching the protocol so at 00:06:17.580 --> 00:06:19.730 align:start position:0% nobody is watching the protocol so at least<00:06:17.699> what<00:06:18.060> honest<00:06:18.479> party<00:06:18.720> watches<00:06:19.620> the 00:06:19.730 --> 00:06:19.740 align:start position:0% least what honest party watches the 00:06:19.740 --> 00:06:22.850 align:start position:0% least what honest party watches the protocol<00:06:20.039> then<00:06:20.639> you<00:06:21.000> you<00:06:21.180> can<00:06:21.780> never<00:06:22.139> get<00:06:22.680> out 00:06:22.850 --> 00:06:22.860 align:start position:0% protocol then you you can never get out 00:06:22.860 --> 00:06:24.529 align:start position:0% protocol then you you can never get out of<00:06:23.039> it<00:06:23.160> yeah 00:06:24.529 --> 00:06:24.539 align:start position:0% of it yeah 00:06:24.539 --> 00:06:27.050 align:start position:0% of it yeah and<00:06:25.259> yeah<00:06:25.380> this<00:06:25.680> is<00:06:25.800> how<00:06:26.039> optimistic<00:06:26.580> rollups 00:06:27.050 --> 00:06:27.060 align:start position:0% and yeah this is how optimistic rollups 00:06:27.060 --> 00:06:30.650 align:start position:0% and yeah this is how optimistic rollups work<00:06:27.180> and<00:06:27.960> like<00:06:28.680> um<00:06:28.680> in<00:06:28.979> in<00:06:29.220> real<00:06:29.520> world<00:06:29.759> it 00:06:30.650 --> 00:06:30.660 align:start position:0% work and like um in in real world it 00:06:30.660 --> 00:06:33.529 align:start position:0% work and like um in in real world it never<00:06:30.780> happens<00:06:31.139> and<00:06:31.919> they're<00:06:32.340> dispute<00:06:32.759> like 00:06:33.529 --> 00:06:33.539 align:start position:0% never happens and they're dispute like 00:06:33.539 --> 00:06:35.390 align:start position:0% never happens and they're dispute like an<00:06:34.020> arbitrum<00:06:34.500> there's<00:06:34.620> never<00:06:34.800> been<00:06:34.979> a<00:06:35.100> dispute 00:06:35.390 --> 00:06:35.400 align:start position:0% an arbitrum there's never been a dispute 00:06:35.400 --> 00:06:36.110 align:start position:0% an arbitrum there's never been a dispute before 00:06:36.110 --> 00:06:36.120 align:start position:0% before 00:06:36.120 --> 00:06:38.450 align:start position:0% before so<00:06:36.660> let's<00:06:36.840> say<00:06:37.080> let's<00:06:37.440> see<00:06:37.800> how<00:06:37.919> it<00:06:38.100> works<00:06:38.340> on 00:06:38.450 --> 00:06:38.460 align:start position:0% so let's say let's see how it works on 00:06:38.460 --> 00:06:40.670 align:start position:0% so let's say let's see how it works on arbitrom<00:06:38.940> on<00:06:39.180> a<00:06:39.300> smart<00:06:39.360> contract<00:06:39.720> level<00:06:39.960> so 00:06:40.670 --> 00:06:40.680 align:start position:0% arbitrom on a smart contract level so 00:06:40.680 --> 00:06:42.230 align:start position:0% arbitrom on a smart contract level so what<00:06:40.800> happens<00:06:40.979> with<00:06:41.160> Arbitron<00:06:41.639> puts<00:06:42.060> two 00:06:42.230 --> 00:06:42.240 align:start position:0% what happens with Arbitron puts two 00:06:42.240 --> 00:06:44.510 align:start position:0% what happens with Arbitron puts two smart<00:06:42.419> contracts<00:06:42.960> on<00:06:43.380> the<00:06:43.620> L1<00:06:43.860> inbox<00:06:44.340> and 00:06:44.510 --> 00:06:44.520 align:start position:0% smart contracts on the L1 inbox and 00:06:44.520 --> 00:06:47.210 align:start position:0% smart contracts on the L1 inbox and outbox<00:06:44.880> and<00:06:45.479> uh<00:06:45.720> what<00:06:45.960> Alice's<00:06:46.380> Alice<00:06:46.740> does<00:06:46.919> is 00:06:47.210 --> 00:06:47.220 align:start position:0% outbox and uh what Alice's Alice does is 00:06:47.220 --> 00:06:49.070 align:start position:0% outbox and uh what Alice's Alice does is she<00:06:47.580> wants<00:06:47.819> to<00:06:47.940> execute<00:06:48.300> some<00:06:48.479> function<00:06:48.780> right 00:06:49.070 --> 00:06:49.080 align:start position:0% she wants to execute some function right 00:06:49.080 --> 00:06:51.350 align:start position:0% she wants to execute some function right so<00:06:49.620> what<00:06:49.919> she<00:06:50.100> does<00:06:50.280> is<00:06:50.460> instead<00:06:50.880> of<00:06:51.000> putting 00:06:51.350 --> 00:06:51.360 align:start position:0% so what she does is instead of putting 00:06:51.360 --> 00:06:53.749 align:start position:0% so what she does is instead of putting the<00:06:51.539> function<00:06:51.840> on<00:06:52.080> L1<00:06:52.440> and<00:06:52.860> having<00:06:53.039> the<00:06:53.280> L1<00:06:53.580> to 00:06:53.749 --> 00:06:53.759 align:start position:0% the function on L1 and having the L1 to 00:06:53.759 --> 00:06:55.670 align:start position:0% the function on L1 and having the L1 to execute<00:06:54.120> everything<00:06:54.360> she<00:06:54.960> puts<00:06:55.319> a<00:06:55.500> message 00:06:55.670 --> 00:06:55.680 align:start position:0% execute everything she puts a message 00:06:55.680 --> 00:06:57.469 align:start position:0% execute everything she puts a message saying<00:06:56.160> that<00:06:56.340> I<00:06:56.580> want<00:06:56.699> this<00:06:56.880> function<00:06:57.180> to<00:06:57.360> be 00:06:57.469 --> 00:06:57.479 align:start position:0% saying that I want this function to be 00:06:57.479 --> 00:07:00.230 align:start position:0% saying that I want this function to be executed<00:06:58.020> on<00:06:58.199> layer<00:06:58.440> one<00:06:58.560> and<00:06:59.039> it's<00:06:59.280> only<00:06:59.460> the 00:07:00.230 --> 00:07:00.240 align:start position:0% executed on layer one and it's only the 00:07:00.240 --> 00:07:02.510 align:start position:0% executed on layer one and it's only the inbox<00:07:00.660> contract<00:07:01.139> is<00:07:01.440> going<00:07:01.620> to<00:07:01.740> record<00:07:02.100> the 00:07:02.510 --> 00:07:02.520 align:start position:0% inbox contract is going to record the 00:07:02.520 --> 00:07:04.850 align:start position:0% inbox contract is going to record the fact<00:07:02.759> that<00:07:03.360> Alice<00:07:03.780> wants<00:07:04.199> this<00:07:04.319> function<00:07:04.620> to 00:07:04.850 --> 00:07:04.860 align:start position:0% fact that Alice wants this function to 00:07:04.860 --> 00:07:06.590 align:start position:0% fact that Alice wants this function to be<00:07:04.979> executed 00:07:06.590 --> 00:07:06.600 align:start position:0% be executed 00:07:06.600 --> 00:07:08.990 align:start position:0% be executed so<00:07:07.080> what<00:07:07.259> happens<00:07:07.380> is<00:07:07.680> somebody<00:07:07.979> outside<00:07:08.460> L1 00:07:08.990 --> 00:07:09.000 align:start position:0% so what happens is somebody outside L1 00:07:09.000 --> 00:07:12.170 align:start position:0% so what happens is somebody outside L1 comes<00:07:09.360> along<00:07:09.479> they<00:07:10.380> dump<00:07:10.740> the<00:07:11.400> contents<00:07:12.060> of 00:07:12.170 --> 00:07:12.180 align:start position:0% comes along they dump the contents of 00:07:12.180 --> 00:07:16.070 align:start position:0% comes along they dump the contents of the<00:07:12.300> inbox<00:07:12.600> smart<00:07:12.840> contract<00:07:13.319> on<00:07:13.680> L2<00:07:14.120> and<00:07:15.120> then 00:07:16.070 --> 00:07:16.080 align:start position:0% the inbox smart contract on L2 and then 00:07:16.080 --> 00:07:17.450 align:start position:0% the inbox smart contract on L2 and then they're<00:07:16.319> going<00:07:16.500> to<00:07:16.620> execute<00:07:16.919> everything<00:07:17.160> on 00:07:17.450 --> 00:07:17.460 align:start position:0% they're going to execute everything on 00:07:17.460 --> 00:07:20.990 align:start position:0% they're going to execute everything on the<00:07:17.580> arbos<00:07:18.000> and<00:07:18.720> it's<00:07:19.199> really<00:07:19.440> based<00:07:19.919> on<00:07:20.099> like 00:07:20.990 --> 00:07:21.000 align:start position:0% the arbos and it's really based on like 00:07:21.000 --> 00:07:23.689 align:start position:0% the arbos and it's really based on like the<00:07:21.300> the<00:07:21.900> how<00:07:22.860> they<00:07:23.039> were<00:07:23.160> sorted<00:07:23.520> inside 00:07:23.689 --> 00:07:23.699 align:start position:0% the the how they were sorted inside 00:07:23.699 --> 00:07:25.730 align:start position:0% the the how they were sorted inside inbox<00:07:24.120> smart<00:07:24.479> contract<00:07:24.960> and<00:07:25.440> then<00:07:25.560> they're 00:07:25.730 --> 00:07:25.740 align:start position:0% inbox smart contract and then they're 00:07:25.740 --> 00:07:27.589 align:start position:0% inbox smart contract and then they're gonna<00:07:25.919> update<00:07:26.400> everybody's<00:07:26.940> account<00:07:27.180> on<00:07:27.479> the 00:07:27.589 --> 00:07:27.599 align:start position:0% gonna update everybody's account on the 00:07:27.599 --> 00:07:29.150 align:start position:0% gonna update everybody's account on the arbos 00:07:29.150 --> 00:07:29.160 align:start position:0% arbos 00:07:29.160 --> 00:07:31.309 align:start position:0% arbos and<00:07:29.580> then<00:07:29.699> they<00:07:29.880> put<00:07:30.120> the<00:07:30.300> uh<00:07:30.539> like<00:07:30.900> the<00:07:31.080> output 00:07:31.309 --> 00:07:31.319 align:start position:0% and then they put the uh like the output 00:07:31.319 --> 00:07:34.129 align:start position:0% and then they put the uh like the output of<00:07:31.560> this<00:07:31.680> execution<00:07:32.220> inside<00:07:33.000> the<00:07:33.360> outbox<00:07:33.840> more 00:07:34.129 --> 00:07:34.139 align:start position:0% of this execution inside the outbox more 00:07:34.139 --> 00:07:36.170 align:start position:0% of this execution inside the outbox more contract<00:07:34.440> in<00:07:34.680> the<00:07:34.800> form<00:07:34.919> of<00:07:35.099> an<00:07:35.280> assertion<00:07:35.759> so 00:07:36.170 --> 00:07:36.180 align:start position:0% contract in the form of an assertion so 00:07:36.180 --> 00:07:38.629 align:start position:0% contract in the form of an assertion so an<00:07:36.419> assertion<00:07:36.900> is<00:07:37.080> basically<00:07:37.500> a<00:07:37.979> fingerprint 00:07:38.629 --> 00:07:38.639 align:start position:0% an assertion is basically a fingerprint 00:07:38.639 --> 00:07:42.050 align:start position:0% an assertion is basically a fingerprint of<00:07:39.419> the<00:07:39.720> latest<00:07:39.900> state<00:07:40.380> of<00:07:40.680> the<00:07:40.800> arbos 00:07:42.050 --> 00:07:42.060 align:start position:0% of the latest state of the arbos 00:07:42.060 --> 00:07:44.990 align:start position:0% of the latest state of the arbos so<00:07:42.479> a<00:07:42.599> term<00:07:42.780> doesn't<00:07:43.020> care<00:07:43.319> what<00:07:43.860> is<00:07:44.039> our<00:07:44.160> Os<00:07:44.639> or 00:07:44.990 --> 00:07:45.000 align:start position:0% so a term doesn't care what is our Os or 00:07:45.000 --> 00:07:47.809 align:start position:0% so a term doesn't care what is our Os or how<00:07:45.360> our<00:07:45.599> OS<00:07:46.020> works<00:07:46.380> it<00:07:46.860> actually<00:07:47.039> works<00:07:47.520> a<00:07:47.699> lot 00:07:47.809 --> 00:07:47.819 align:start position:0% how our OS works it actually works a lot 00:07:47.819 --> 00:07:50.749 align:start position:0% how our OS works it actually works a lot like<00:07:48.060> ethereum<00:07:48.660> it<00:07:49.020> runs<00:07:49.380> a<00:07:49.560> blockchain<00:07:50.039> it 00:07:50.749 --> 00:07:50.759 align:start position:0% like ethereum it runs a blockchain it 00:07:50.759 --> 00:07:52.969 align:start position:0% like ethereum it runs a blockchain it has<00:07:50.940> blocks<00:07:51.479> it<00:07:51.780> has<00:07:51.900> miners<00:07:52.380> we<00:07:52.680> call<00:07:52.860> them 00:07:52.969 --> 00:07:52.979 align:start position:0% has blocks it has miners we call them 00:07:52.979 --> 00:07:56.089 align:start position:0% has blocks it has miners we call them validators<00:07:53.580> it<00:07:54.419> has<00:07:54.599> block<00:07:54.840> explorers<00:07:55.500> but<00:07:55.919> a 00:07:56.089 --> 00:07:56.099 align:start position:0% validators it has block explorers but a 00:07:56.099 --> 00:07:57.890 align:start position:0% validators it has block explorers but a term<00:07:56.280> doesn't<00:07:56.520> care<00:07:56.759> about<00:07:56.880> anything<00:07:57.240> about 00:07:57.890 --> 00:07:57.900 align:start position:0% term doesn't care about anything about 00:07:57.900 --> 00:08:00.350 align:start position:0% term doesn't care about anything about that<00:07:58.199> it<00:07:58.680> only<00:07:58.800> cares<00:07:59.220> about<00:07:59.340> like<00:07:59.759> here's<00:08:00.240> the 00:08:00.350 --> 00:08:00.360 align:start position:0% that it only cares about like here's the 00:08:00.360 --> 00:08:02.629 align:start position:0% that it only cares about like here's the list<00:08:00.599> of<00:08:00.780> function<00:08:01.139> that<00:08:01.919> I'm<00:08:02.099> seeing<00:08:02.340> that 00:08:02.629 --> 00:08:02.639 align:start position:0% list of function that I'm seeing that 00:08:02.639 --> 00:08:04.969 align:start position:0% list of function that I'm seeing that are<00:08:02.759> going<00:08:02.940> to<00:08:03.060> be<00:08:03.180> executed<00:08:03.599> on<00:08:03.780> Layer<00:08:04.080> Two<00:08:04.259> I 00:08:04.969 --> 00:08:04.979 align:start position:0% are going to be executed on Layer Two I 00:08:04.979 --> 00:08:07.070 align:start position:0% are going to be executed on Layer Two I want<00:08:05.220> to<00:08:05.400> see<00:08:05.639> the<00:08:05.940> the<00:08:06.240> output<00:08:06.660> of<00:08:06.900> this 00:08:07.070 --> 00:08:07.080 align:start position:0% want to see the the output of this 00:08:07.080 --> 00:08:10.070 align:start position:0% want to see the the output of this execution<00:08:07.560> that's<00:08:07.919> all<00:08:08.099> it<00:08:08.280> cares<00:08:08.580> about 00:08:10.070 --> 00:08:10.080 align:start position:0% execution that's all it cares about 00:08:10.080 --> 00:08:12.170 align:start position:0% execution that's all it cares about so<00:08:10.680> we<00:08:10.979> have<00:08:11.160> to<00:08:11.280> wait<00:08:11.460> for<00:08:11.699> seven<00:08:11.940> days 00:08:12.170 --> 00:08:12.180 align:start position:0% so we have to wait for seven days 00:08:12.180 --> 00:08:13.990 align:start position:0% so we have to wait for seven days because<00:08:12.479> we<00:08:12.840> want<00:08:13.020> to<00:08:13.139> make<00:08:13.319> sure<00:08:13.560> that 00:08:13.990 --> 00:08:14.000 align:start position:0% because we want to make sure that 00:08:14.000 --> 00:08:16.850 align:start position:0% because we want to make sure that everybody<00:08:15.000> have<00:08:15.419> time<00:08:15.720> to<00:08:16.080> come<00:08:16.259> along<00:08:16.500> and 00:08:16.850 --> 00:08:16.860 align:start position:0% everybody have time to come along and 00:08:16.860 --> 00:08:18.650 align:start position:0% everybody have time to come along and they<00:08:17.099> react<00:08:17.460> to<00:08:17.580> it<00:08:17.699> if<00:08:17.880> there's<00:08:18.000> any<00:08:18.180> dispute 00:08:18.650 --> 00:08:18.660 align:start position:0% they react to it if there's any dispute 00:08:18.660 --> 00:08:21.170 align:start position:0% they react to it if there's any dispute and<00:08:19.139> if<00:08:19.500> there's<00:08:19.740> not<00:08:20.039> no<00:08:20.280> dispute<00:08:20.639> it's<00:08:21.000> going 00:08:21.170 --> 00:08:21.180 align:start position:0% and if there's not no dispute it's going 00:08:21.180 --> 00:08:22.969 align:start position:0% and if there's not no dispute it's going to<00:08:21.300> be<00:08:21.419> finalized 00:08:22.969 --> 00:08:22.979 align:start position:0% to be finalized 00:08:22.979 --> 00:08:25.070 align:start position:0% to be finalized so<00:08:23.520> let's<00:08:23.699> say<00:08:23.819> Alice<00:08:24.240> wants<00:08:24.599> to<00:08:24.660> do<00:08:24.780> something 00:08:25.070 --> 00:08:25.080 align:start position:0% so let's say Alice wants to do something 00:08:25.080 --> 00:08:27.290 align:start position:0% so let's say Alice wants to do something slightly<00:08:25.740> different<00:08:25.979> this<00:08:26.400> time<00:08:26.580> she<00:08:27.000> wants 00:08:27.290 --> 00:08:27.300 align:start position:0% slightly different this time she wants 00:08:27.300 --> 00:08:30.529 align:start position:0% slightly different this time she wants to<00:08:27.419> withdraw<00:08:27.840> 100<00:08:28.020> eth<00:08:28.500> from<00:08:28.740> L2<00:08:29.099> and<00:08:29.879> to<00:08:30.360> make 00:08:30.529 --> 00:08:30.539 align:start position:0% to withdraw 100 eth from L2 and to make 00:08:30.539 --> 00:08:32.990 align:start position:0% to withdraw 100 eth from L2 and to make that<00:08:30.660> happen<00:08:30.900> arbitrom<00:08:31.620> has<00:08:31.860> to<00:08:32.039> introduce<00:08:32.520> a 00:08:32.990 --> 00:08:33.000 align:start position:0% that happen arbitrom has to introduce a 00:08:33.000 --> 00:08:35.570 align:start position:0% that happen arbitrom has to introduce a smart<00:08:33.300> contract<00:08:33.719> which<00:08:34.440> is<00:08:34.620> called<00:08:34.800> Bridge<00:08:35.039> so 00:08:35.570 --> 00:08:35.580 align:start position:0% smart contract which is called Bridge so 00:08:35.580 --> 00:08:38.690 align:start position:0% smart contract which is called Bridge so Bridge's<00:08:36.419> job<00:08:36.659> is<00:08:36.899> basically<00:08:37.200> to<00:08:37.700> Escrow 00:08:38.690 --> 00:08:38.700 align:start position:0% Bridge's job is basically to Escrow 00:08:38.700 --> 00:08:41.269 align:start position:0% Bridge's job is basically to Escrow whatever<00:08:39.180> tokens<00:08:39.959> or<00:08:40.200> ethers<00:08:40.740> people<00:08:40.860> want<00:08:41.159> to 00:08:41.269 --> 00:08:41.279 align:start position:0% whatever tokens or ethers people want to 00:08:41.279 --> 00:08:43.670 align:start position:0% whatever tokens or ethers people want to move<00:08:41.399> to<00:08:41.580> the<00:08:41.760> L2<00:08:42.120> so<00:08:42.839> if<00:08:43.080> Alice<00:08:43.380> wants<00:08:43.680> to 00:08:43.670 --> 00:08:43.680 align:start position:0% move to the L2 so if Alice wants to 00:08:43.680 --> 00:08:45.829 align:start position:0% move to the L2 so if Alice wants to withdraw<00:08:44.039> 100<00:08:44.219> ether<00:08:44.640> from<00:08:44.880> L2<00:08:45.300> it<00:08:45.540> means<00:08:45.720> that 00:08:45.829 --> 00:08:45.839 align:start position:0% withdraw 100 ether from L2 it means that 00:08:45.839 --> 00:08:48.710 align:start position:0% withdraw 100 ether from L2 it means that she<00:08:46.080> has<00:08:46.320> previously<00:08:46.980> moved<00:08:47.820> 100<00:08:47.880> ether<00:08:48.420> to 00:08:48.710 --> 00:08:48.720 align:start position:0% she has previously moved 100 ether to 00:08:48.720 --> 00:08:51.290 align:start position:0% she has previously moved 100 ether to the<00:08:49.080> rbos<00:08:49.620> so<00:08:50.220> what<00:08:50.399> bridge<00:08:50.580> does<00:08:50.880> is<00:08:51.060> hey 00:08:51.290 --> 00:08:51.300 align:start position:0% the rbos so what bridge does is hey 00:08:51.300 --> 00:08:53.210 align:start position:0% the rbos so what bridge does is hey Alice<00:08:51.660> I<00:08:51.839> know<00:08:51.959> you're<00:08:52.140> moving<00:08:52.380> 100<00:08:52.620> East<00:08:52.980> to 00:08:53.210 --> 00:08:53.220 align:start position:0% Alice I know you're moving 100 East to 00:08:53.220 --> 00:08:55.670 align:start position:0% Alice I know you're moving 100 East to the<00:08:53.399> L2<00:08:53.700> that's<00:08:54.300> fine<00:08:54.540> just<00:08:54.779> give<00:08:54.959> me<00:08:55.140> 100<00:08:55.320> each 00:08:55.670 --> 00:08:55.680 align:start position:0% the L2 that's fine just give me 100 each 00:08:55.680 --> 00:08:57.650 align:start position:0% the L2 that's fine just give me 100 each I'm<00:08:55.920> gonna<00:08:56.040> score<00:08:56.399> it<00:08:56.640> for<00:08:56.820> you<00:08:56.940> and<00:08:57.360> then<00:08:57.480> I'm 00:08:57.650 --> 00:08:57.660 align:start position:0% I'm gonna score it for you and then I'm 00:08:57.660 --> 00:09:00.170 align:start position:0% I'm gonna score it for you and then I'm gonna<00:08:57.839> mint<00:08:58.260> 100<00:08:58.440> is<00:08:58.860> on<00:08:59.100> L2<00:08:59.399> out<00:08:59.580> of<00:08:59.760> thin<00:09:00.000> air 00:09:00.170 --> 00:09:00.180 align:start position:0% gonna mint 100 is on L2 out of thin air 00:09:00.180 --> 00:09:02.150 align:start position:0% gonna mint 100 is on L2 out of thin air you'll<00:09:00.660> be<00:09:00.839> the<00:09:00.959> owner<00:09:01.260> do<00:09:01.500> whatever<00:09:01.680> you<00:09:02.040> want 00:09:02.150 --> 00:09:02.160 align:start position:0% you'll be the owner do whatever you want 00:09:02.160 --> 00:09:04.490 align:start position:0% you'll be the owner do whatever you want go<00:09:02.459> ahead<00:09:02.760> transfer<00:09:03.120> it<00:09:03.240> to<00:09:03.360> Bob<00:09:03.540> and<00:09:04.200> the<00:09:04.380> end 00:09:04.490 --> 00:09:04.500 align:start position:0% go ahead transfer it to Bob and the end 00:09:04.500 --> 00:09:06.710 align:start position:0% go ahead transfer it to Bob and the end of<00:09:04.680> the<00:09:04.860> day<00:09:05.040> what<00:09:05.519> I<00:09:05.760> care<00:09:05.880> about<00:09:06.060> is<00:09:06.420> somebody 00:09:06.710 --> 00:09:06.720 align:start position:0% of the day what I care about is somebody 00:09:06.720 --> 00:09:08.449 align:start position:0% of the day what I care about is somebody comes<00:09:07.200> along<00:09:07.320> and<00:09:07.620> they<00:09:07.800> want<00:09:07.980> their<00:09:08.160> ether 00:09:08.449 --> 00:09:08.459 align:start position:0% comes along and they want their ether 00:09:08.459 --> 00:09:10.370 align:start position:0% comes along and they want their ether back<00:09:08.700> from<00:09:08.880> me<00:09:09.120> and<00:09:09.779> that's<00:09:09.959> called<00:09:10.140> a 00:09:10.370 --> 00:09:10.380 align:start position:0% back from me and that's called a 00:09:10.380 --> 00:09:13.310 align:start position:0% back from me and that's called a withdraw<00:09:10.860> transaction<00:09:11.339> so<00:09:12.240> yeah<00:09:12.420> so<00:09:12.839> like<00:09:13.080> any 00:09:13.310 --> 00:09:13.320 align:start position:0% withdraw transaction so yeah so like any 00:09:13.320 --> 00:09:15.710 align:start position:0% withdraw transaction so yeah so like any other<00:09:13.560> transaction<00:09:13.980> I<00:09:14.339> just<00:09:14.519> described<00:09:15.000> Alice 00:09:15.710 --> 00:09:15.720 align:start position:0% other transaction I just described Alice 00:09:15.720 --> 00:09:17.509 align:start position:0% other transaction I just described Alice puts<00:09:16.080> a<00:09:16.260> message<00:09:16.440> for<00:09:16.920> the<00:09:17.040> withdrawal 00:09:17.509 --> 00:09:17.519 align:start position:0% puts a message for the withdrawal 00:09:17.519 --> 00:09:19.310 align:start position:0% puts a message for the withdrawal transaction<00:09:17.760> inside<00:09:18.120> the<00:09:18.420> Inbox<00:09:18.720> and 00:09:19.310 --> 00:09:19.320 align:start position:0% transaction inside the Inbox and 00:09:19.320 --> 00:09:22.009 align:start position:0% transaction inside the Inbox and arbitrum<00:09:19.980> does<00:09:20.160> it<00:09:20.399> things 00:09:22.009 --> 00:09:22.019 align:start position:0% arbitrum does it things 00:09:22.019 --> 00:09:25.310 align:start position:0% arbitrum does it things so<00:09:22.560> yeah<00:09:22.740> somebody<00:09:22.980> dumps<00:09:23.880> the<00:09:24.660> contents<00:09:25.200> of 00:09:25.310 --> 00:09:25.320 align:start position:0% so yeah somebody dumps the contents of 00:09:25.320 --> 00:09:27.530 align:start position:0% so yeah somebody dumps the contents of the<00:09:25.440> Inbox<00:09:25.680> and<00:09:25.980> the<00:09:26.100> arbos<00:09:26.459> it<00:09:26.820> gets<00:09:27.060> executed 00:09:27.530 --> 00:09:27.540 align:start position:0% the Inbox and the arbos it gets executed 00:09:27.540 --> 00:09:29.990 align:start position:0% the Inbox and the arbos it gets executed and<00:09:28.260> then<00:09:28.380> the<00:09:28.620> assertion<00:09:29.040> would<00:09:29.279> be<00:09:29.399> placed 00:09:29.990 --> 00:09:30.000 align:start position:0% and then the assertion would be placed 00:09:30.000 --> 00:09:31.970 align:start position:0% and then the assertion would be placed inside<00:09:30.180> the<00:09:30.480> outbox<00:09:30.839> now<00:09:31.380> we<00:09:31.560> have<00:09:31.740> to<00:09:31.800> wait 00:09:31.970 --> 00:09:31.980 align:start position:0% inside the outbox now we have to wait 00:09:31.980 --> 00:09:34.370 align:start position:0% inside the outbox now we have to wait for<00:09:32.220> seven<00:09:32.459> days<00:09:32.700> so<00:09:33.240> that<00:09:33.420> we<00:09:33.600> make<00:09:33.779> sure<00:09:34.019> that 00:09:34.370 --> 00:09:34.380 align:start position:0% for seven days so that we make sure that 00:09:34.380 --> 00:09:35.870 align:start position:0% for seven days so that we make sure that the<00:09:34.560> assertion<00:09:34.980> is<00:09:35.160> finalized<00:09:35.519> and<00:09:35.760> our 00:09:35.870 --> 00:09:35.880 align:start position:0% the assertion is finalized and our 00:09:35.880 --> 00:09:39.769 align:start position:0% the assertion is finalized and our withdraw<00:09:36.360> transaction<00:09:36.660> can<00:09:37.080> go<00:09:37.200> through 00:09:39.769 --> 00:09:39.779 align:start position:0% 00:09:39.779 --> 00:09:41.690 align:start position:0% and<00:09:40.320> only<00:09:40.560> in<00:09:40.800> that<00:09:40.980> case<00:09:41.160> when<00:09:41.399> it<00:09:41.580> is 00:09:41.690 --> 00:09:41.700 align:start position:0% and only in that case when it is 00:09:41.700 --> 00:09:43.610 align:start position:0% and only in that case when it is finalized<00:09:42.180> Alice<00:09:42.720> knows<00:09:43.140> that<00:09:43.380> her 00:09:43.610 --> 00:09:43.620 align:start position:0% finalized Alice knows that her 00:09:43.620 --> 00:09:45.769 align:start position:0% finalized Alice knows that her transaction<00:09:44.040> is<00:09:44.399> in<00:09:44.580> assertion<00:09:45.000> number<00:09:45.180> 20. 00:09:45.769 --> 00:09:45.779 align:start position:0% transaction is in assertion number 20. 00:09:45.779 --> 00:09:47.750 align:start position:0% transaction is in assertion number 20. she<00:09:46.140> can<00:09:46.380> go<00:09:46.500> to<00:09:46.680> the<00:09:46.800> outbox<00:09:47.100> and<00:09:47.399> she'll<00:09:47.580> be 00:09:47.750 --> 00:09:47.760 align:start position:0% she can go to the outbox and she'll be 00:09:47.760 --> 00:09:49.850 align:start position:0% she can go to the outbox and she'll be like<00:09:47.880> hey<00:09:48.120> upbox<00:09:48.600> this<00:09:49.200> is<00:09:49.320> the<00:09:49.440> assertion 00:09:49.850 --> 00:09:49.860 align:start position:0% like hey upbox this is the assertion 00:09:49.860 --> 00:09:51.889 align:start position:0% like hey upbox this is the assertion it's<00:09:50.399> just<00:09:50.519> finalized<00:09:51.060> it's<00:09:51.300> sitting<00:09:51.660> there 00:09:51.889 --> 00:09:51.899 align:start position:0% it's just finalized it's sitting there 00:09:51.899 --> 00:09:54.350 align:start position:0% it's just finalized it's sitting there for<00:09:52.140> you<00:09:52.320> to<00:09:52.560> go<00:09:52.740> and<00:09:52.920> see<00:09:53.160> go<00:09:53.760> check<00:09:54.000> it<00:09:54.180> please 00:09:54.350 --> 00:09:54.360 align:start position:0% for you to go and see go check it please 00:09:54.360 --> 00:09:56.810 align:start position:0% for you to go and see go check it please and<00:09:54.660> then<00:09:54.899> if<00:09:55.320> you're<00:09:55.560> happy<00:09:55.740> with<00:09:55.980> that<00:09:56.160> I<00:09:56.580> won 00:09:56.810 --> 00:09:56.820 align:start position:0% and then if you're happy with that I won 00:09:56.820 --> 00:09:59.329 align:start position:0% and then if you're happy with that I won my<00:09:57.000> 100<00:09:57.120> East<00:09:57.540> back<00:09:57.779> from<00:09:58.019> the<00:09:58.140> bridge 00:09:59.329 --> 00:09:59.339 align:start position:0% my 100 East back from the bridge 00:09:59.339 --> 00:10:01.490 align:start position:0% my 100 East back from the bridge so<00:09:59.820> outbox<00:10:00.180> is<00:10:00.480> Happy<00:10:00.660> Bridge<00:10:01.019> would<00:10:01.320> give 00:10:01.490 --> 00:10:01.500 align:start position:0% so outbox is Happy Bridge would give 00:10:01.500 --> 00:10:03.530 align:start position:0% so outbox is Happy Bridge would give back<00:10:01.680> The<00:10:01.920> Ether<00:10:02.160> to<00:10:02.640> Alice<00:10:02.940> and<00:10:03.180> then<00:10:03.360> it's 00:10:03.530 --> 00:10:03.540 align:start position:0% back The Ether to Alice and then it's 00:10:03.540 --> 00:10:06.530 align:start position:0% back The Ether to Alice and then it's gonna<00:10:03.779> burn<00:10:04.440> those<00:10:04.800> on<00:10:05.100> the<00:10:05.339> L2 00:10:06.530 --> 00:10:06.540 align:start position:0% gonna burn those on the L2 00:10:06.540 --> 00:10:08.449 align:start position:0% gonna burn those on the L2 so<00:10:06.899> here's<00:10:07.140> the<00:10:07.260> problem<00:10:07.440> I'm<00:10:07.800> sure<00:10:08.160> you've 00:10:08.449 --> 00:10:08.459 align:start position:0% so here's the problem I'm sure you've 00:10:08.459 --> 00:10:11.810 align:start position:0% so here's the problem I'm sure you've noticed<00:10:09.019> withdrawals<00:10:10.019> take<00:10:10.320> seven<00:10:10.620> days<00:10:10.980> to 00:10:11.810 --> 00:10:11.820 align:start position:0% noticed withdrawals take seven days to 00:10:11.820 --> 00:10:14.030 align:start position:0% noticed withdrawals take seven days to be<00:10:12.300> to<00:10:12.600> be<00:10:12.660> finalized<00:10:13.200> and<00:10:13.380> it<00:10:13.560> could<00:10:13.680> be<00:10:13.860> even 00:10:14.030 --> 00:10:14.040 align:start position:0% be to be finalized and it could be even 00:10:14.040 --> 00:10:17.389 align:start position:0% be to be finalized and it could be even longer<00:10:14.519> if<00:10:15.180> there's<00:10:15.300> any<00:10:15.540> dispute<00:10:16.019> and<00:10:16.980> uh 00:10:17.389 --> 00:10:17.399 align:start position:0% longer if there's any dispute and uh 00:10:17.399 --> 00:10:18.889 align:start position:0% longer if there's any dispute and uh although<00:10:17.760> there's<00:10:18.000> never<00:10:18.180> been<00:10:18.420> a<00:10:18.600> dispute 00:10:18.889 --> 00:10:18.899 align:start position:0% although there's never been a dispute 00:10:18.899 --> 00:10:21.530 align:start position:0% although there's never been a dispute before<00:10:19.140> but<00:10:19.380> there<00:10:19.500> could<00:10:19.740> be<00:10:19.920> and<00:10:20.640> people 00:10:21.530 --> 00:10:21.540 align:start position:0% before but there could be and people 00:10:21.540 --> 00:10:23.030 align:start position:0% before but there could be and people really<00:10:21.779> don't<00:10:21.959> want<00:10:22.140> to<00:10:22.260> wait<00:10:22.380> for<00:10:22.560> seven<00:10:22.740> days 00:10:23.030 --> 00:10:23.040 align:start position:0% really don't want to wait for seven days 00:10:23.040 --> 00:10:24.650 align:start position:0% really don't want to wait for seven days sometimes<00:10:23.700> they<00:10:23.880> have<00:10:24.060> a<00:10:24.180> pressing<00:10:24.480> reason 00:10:24.650 --> 00:10:24.660 align:start position:0% sometimes they have a pressing reason 00:10:24.660 --> 00:10:26.389 align:start position:0% sometimes they have a pressing reason they<00:10:25.019> want<00:10:25.200> to<00:10:25.320> really<00:10:25.440> do<00:10:25.800> something<00:10:26.040> with 00:10:26.389 --> 00:10:26.399 align:start position:0% they want to really do something with 00:10:26.399 --> 00:10:28.970 align:start position:0% they want to really do something with their<00:10:26.580> ether<00:10:26.880> but<00:10:27.740> intrinsically<00:10:28.740> you<00:10:28.920> don't 00:10:28.970 --> 00:10:28.980 align:start position:0% their ether but intrinsically you don't 00:10:28.980 --> 00:10:31.370 align:start position:0% their ether but intrinsically you don't want<00:10:29.100> to<00:10:29.279> wait<00:10:29.399> and<00:10:29.940> then<00:10:30.120> seven<00:10:30.600> days<00:10:30.839> is<00:10:31.140> just 00:10:31.370 --> 00:10:31.380 align:start position:0% want to wait and then seven days is just 00:10:31.380 --> 00:10:33.410 align:start position:0% want to wait and then seven days is just really<00:10:31.620> an<00:10:31.860> arbitrary<00:10:32.220> number<00:10:32.519> but<00:10:33.000> there 00:10:33.410 --> 00:10:33.420 align:start position:0% really an arbitrary number but there 00:10:33.420 --> 00:10:35.389 align:start position:0% really an arbitrary number but there should<00:10:33.600> be<00:10:33.720> some<00:10:33.899> time<00:10:34.080> window<00:10:34.320> for<00:10:34.740> people<00:10:34.920> to 00:10:35.389 --> 00:10:35.399 align:start position:0% should be some time window for people to 00:10:35.399 --> 00:10:38.090 align:start position:0% should be some time window for people to pay<00:10:36.180> attention<00:10:36.480> to<00:10:36.720> the<00:10:36.839> protocol<00:10:37.140> and<00:10:37.680> react 00:10:38.090 --> 00:10:38.100 align:start position:0% pay attention to the protocol and react 00:10:38.100 --> 00:10:41.570 align:start position:0% pay attention to the protocol and react to<00:10:38.279> it<00:10:38.399> if<00:10:38.519> something<00:10:38.760> happens 00:10:41.570 --> 00:10:41.580 align:start position:0% 00:10:41.580 --> 00:10:44.030 align:start position:0% but<00:10:42.120> something<00:10:42.360> interesting<00:10:43.019> that<00:10:43.560> we<00:10:43.680> notice 00:10:44.030 --> 00:10:44.040 align:start position:0% but something interesting that we notice 00:10:44.040 --> 00:10:46.550 align:start position:0% but something interesting that we notice is<00:10:44.399> on<00:10:44.880> arbit's<00:10:45.360> room<00:10:45.480> let's<00:10:45.720> say<00:10:45.839> there's<00:10:46.380> an 00:10:46.550 --> 00:10:46.560 align:start position:0% is on arbit's room let's say there's an 00:10:46.560 --> 00:10:48.590 align:start position:0% is on arbit's room let's say there's an assertion<00:10:47.040> that<00:10:47.459> you're<00:10:47.880> just<00:10:48.060> looking<00:10:48.180> at<00:10:48.480> it 00:10:48.590 --> 00:10:48.600 align:start position:0% assertion that you're just looking at it 00:10:48.600 --> 00:10:50.030 align:start position:0% assertion that you're just looking at it for<00:10:48.839> the<00:10:48.959> first<00:10:49.079> time<00:10:49.260> and<00:10:49.620> you're<00:10:49.740> trying<00:10:49.920> to 00:10:50.030 --> 00:10:50.040 align:start position:0% for the first time and you're trying to 00:10:50.040 --> 00:10:51.769 align:start position:0% for the first time and you're trying to figure<00:10:50.220> out<00:10:50.459> if<00:10:50.640> it's<00:10:50.820> going<00:10:51.000> to<00:10:51.060> be<00:10:51.240> finalized 00:10:51.769 --> 00:10:51.779 align:start position:0% figure out if it's going to be finalized 00:10:51.779 --> 00:10:54.650 align:start position:0% figure out if it's going to be finalized or<00:10:51.959> not<00:10:52.560> so<00:10:53.100> if<00:10:53.399> it<00:10:53.700> ha<00:10:53.880> it<00:10:54.240> actually<00:10:54.360> happens 00:10:54.650 --> 00:10:54.660 align:start position:0% or not so if it ha it actually happens 00:10:54.660 --> 00:10:58.190 align:start position:0% or not so if it ha it actually happens if<00:10:55.200> you<00:10:55.380> run<00:10:55.620> an<00:10:56.040> validator<00:10:56.579> on<00:10:56.940> arbitrol<00:10:57.660> what 00:10:58.190 --> 00:10:58.200 align:start position:0% if you run an validator on arbitrol what 00:10:58.200 --> 00:11:00.350 align:start position:0% if you run an validator on arbitrol what happens<00:10:58.320> is<00:10:58.680> what<00:10:59.279> is<00:10:59.459> validator<00:10:59.820> is<00:11:00.060> just<00:11:00.240> a 00:11:00.350 --> 00:11:00.360 align:start position:0% happens is what is validator is just a 00:11:00.360 --> 00:11:01.810 align:start position:0% happens is what is validator is just a software<00:11:00.720> that<00:11:00.839> goes<00:11:01.140> through<00:11:01.200> the<00:11:01.380> inbox 00:11:01.810 --> 00:11:01.820 align:start position:0% software that goes through the inbox 00:11:01.820 --> 00:11:04.190 align:start position:0% software that goes through the inbox transactions<00:11:02.820> one<00:11:03.000> by<00:11:03.180> one<00:11:03.360> it's<00:11:03.899> going<00:11:04.079> to 00:11:04.190 --> 00:11:04.200 align:start position:0% transactions one by one it's going to 00:11:04.200 --> 00:11:05.690 align:start position:0% transactions one by one it's going to execute<00:11:04.500> those<00:11:04.740> and<00:11:04.980> at<00:11:05.220> the<00:11:05.339> end<00:11:05.399> of<00:11:05.519> the<00:11:05.579> day 00:11:05.690 --> 00:11:05.700 align:start position:0% execute those and at the end of the day 00:11:05.700 --> 00:11:08.509 align:start position:0% execute those and at the end of the day it's<00:11:05.880> just<00:11:06.060> gonna<00:11:06.360> compare<00:11:06.899> the<00:11:07.860> output<00:11:08.220> of 00:11:08.509 --> 00:11:08.519 align:start position:0% it's just gonna compare the output of 00:11:08.519 --> 00:11:10.130 align:start position:0% it's just gonna compare the output of this<00:11:08.700> execution<00:11:09.120> with<00:11:09.420> the<00:11:09.660> state<00:11:09.839> that<00:11:10.019> is 00:11:10.130 --> 00:11:10.140 align:start position:0% this execution with the state that is 00:11:10.140 --> 00:11:12.949 align:start position:0% this execution with the state that is being<00:11:10.320> asserted<00:11:10.860> so<00:11:11.339> if<00:11:11.640> you<00:11:11.820> run<00:11:12.120> an<00:11:12.540> orbits 00:11:12.949 --> 00:11:12.959 align:start position:0% being asserted so if you run an orbits 00:11:12.959 --> 00:11:15.590 align:start position:0% being asserted so if you run an orbits from<00:11:13.079> validator<00:11:13.500> you<00:11:14.100> can<00:11:14.220> be<00:11:14.399> 100<00:11:14.579> sure<00:11:15.240> that 00:11:15.590 --> 00:11:15.600 align:start position:0% from validator you can be 100 sure that 00:11:15.600 --> 00:11:16.970 align:start position:0% from validator you can be 100 sure that this<00:11:15.839> transaction<00:11:16.200> is<00:11:16.380> really<00:11:16.620> going<00:11:16.800> to<00:11:16.920> be 00:11:16.970 --> 00:11:16.980 align:start position:0% this transaction is really going to be 00:11:16.980 --> 00:11:18.410 align:start position:0% this transaction is really going to be finalized<00:11:17.459> the<00:11:17.640> assertion<00:11:18.060> is<00:11:18.180> going<00:11:18.300> to<00:11:18.360> be 00:11:18.410 --> 00:11:18.420 align:start position:0% finalized the assertion is going to be 00:11:18.420 --> 00:11:20.930 align:start position:0% finalized the assertion is going to be finalized<00:11:19.019> so<00:11:19.620> we<00:11:19.860> found<00:11:20.040> that<00:11:20.279> this<00:11:20.459> this<00:11:20.700> is 00:11:20.930 --> 00:11:20.940 align:start position:0% finalized so we found that this this is 00:11:20.940 --> 00:11:23.210 align:start position:0% finalized so we found that this this is really<00:11:21.180> interesting<00:11:22.079> that<00:11:22.440> we<00:11:22.680> can<00:11:22.860> leverage 00:11:23.210 --> 00:11:23.220 align:start position:0% really interesting that we can leverage 00:11:23.220 --> 00:11:26.389 align:start position:0% really interesting that we can leverage to<00:11:23.820> get<00:11:24.060> a<00:11:24.300> relief<00:11:24.660> of<00:11:25.320> this<00:11:25.680> pain<00:11:25.860> point<00:11:26.100> of 00:11:26.389 --> 00:11:26.399 align:start position:0% to get a relief of this pain point of 00:11:26.399 --> 00:11:29.630 align:start position:0% to get a relief of this pain point of having<00:11:26.579> to<00:11:26.820> wait<00:11:27.000> for<00:11:27.240> seven<00:11:27.420> days 00:11:29.630 --> 00:11:29.640 align:start position:0% having to wait for seven days 00:11:29.640 --> 00:11:32.389 align:start position:0% having to wait for seven days so<00:11:30.540> the<00:11:30.899> question<00:11:31.079> we<00:11:31.440> were<00:11:31.620> asking<00:11:31.980> in<00:11:32.220> this 00:11:32.389 --> 00:11:32.399 align:start position:0% so the question we were asking in this 00:11:32.399 --> 00:11:35.150 align:start position:0% so the question we were asking in this research<00:11:32.760> is<00:11:33.120> can<00:11:33.480> Alice<00:11:33.899> withdraw<00:11:34.380> 100<00:11:34.560> eth 00:11:35.150 --> 00:11:35.160 align:start position:0% research is can Alice withdraw 100 eth 00:11:35.160 --> 00:11:38.090 align:start position:0% research is can Alice withdraw 100 eth from<00:11:35.459> L2<00:11:35.880> back<00:11:36.660> to<00:11:36.839> L1<00:11:37.200> without<00:11:37.620> having<00:11:37.920> to 00:11:38.090 --> 00:11:38.100 align:start position:0% from L2 back to L1 without having to 00:11:38.100 --> 00:11:40.670 align:start position:0% from L2 back to L1 without having to wait<00:11:38.339> for<00:11:38.579> seven<00:11:38.760> days<00:11:39.060> so<00:11:39.720> we<00:11:39.959> we<00:11:40.260> have<00:11:40.500> come 00:11:40.670 --> 00:11:40.680 align:start position:0% wait for seven days so we we have come 00:11:40.680 --> 00:11:43.069 align:start position:0% wait for seven days so we we have come up<00:11:40.860> with<00:11:41.040> four<00:11:41.339> different<00:11:41.579> solutions<00:11:42.120> in<00:11:42.839> his 00:11:43.069 --> 00:11:43.079 align:start position:0% up with four different solutions in his 00:11:43.079 --> 00:11:45.230 align:start position:0% up with four different solutions in his work<00:11:43.260> and<00:11:43.740> I'm<00:11:44.040> gonna<00:11:44.220> go<00:11:44.519> through<00:11:44.760> them<00:11:45.000> one 00:11:45.230 --> 00:11:45.240 align:start position:0% work and I'm gonna go through them one 00:11:45.240 --> 00:11:47.150 align:start position:0% work and I'm gonna go through them one by<00:11:45.360> one<00:11:45.540> and<00:11:46.079> they<00:11:46.260> actually<00:11:46.440> get<00:11:46.680> better<00:11:46.860> as 00:11:47.150 --> 00:11:47.160 align:start position:0% by one and they actually get better as 00:11:47.160 --> 00:11:48.230 align:start position:0% by one and they actually get better as we<00:11:47.339> go<00:11:47.459> through 00:11:48.230 --> 00:11:48.240 align:start position:0% we go through 00:11:48.240 --> 00:11:50.750 align:start position:0% we go through okay<00:11:48.600> so<00:11:49.140> the<00:11:49.320> first<00:11:49.440> solution<00:11:49.740> is<00:11:50.040> Alice<00:11:50.519> can 00:11:50.750 --> 00:11:50.760 align:start position:0% okay so the first solution is Alice can 00:11:50.760 --> 00:11:53.210 align:start position:0% okay so the first solution is Alice can actually<00:11:50.940> use<00:11:51.420> a<00:11:51.839> centralized<00:11:52.440> exchange<00:11:52.860> like 00:11:53.210 --> 00:11:53.220 align:start position:0% actually use a centralized exchange like 00:11:53.220 --> 00:11:55.970 align:start position:0% actually use a centralized exchange like hop<00:11:53.519> right<00:11:53.940> so<00:11:54.480> what<00:11:54.899> you<00:11:55.079> can<00:11:55.200> do<00:11:55.440> is<00:11:55.680> you<00:11:55.860> can 00:11:55.970 --> 00:11:55.980 align:start position:0% hop right so what you can do is you can 00:11:55.980 --> 00:11:58.190 align:start position:0% hop right so what you can do is you can go<00:11:56.160> to<00:11:56.279> The<00:11:56.459> Exchange<00:11:56.820> she<00:11:57.120> can<00:11:57.300> trade<00:11:57.660> uh<00:11:58.019> her 00:11:58.190 --> 00:11:58.200 align:start position:0% go to The Exchange she can trade uh her 00:11:58.200 --> 00:12:00.769 align:start position:0% go to The Exchange she can trade uh her hundred<00:11:58.560> each<00:11:59.040> on<00:11:59.339> a<00:11:59.459> two<00:11:59.640> with<00:11:59.880> the<00:12:00.000> one<00:12:00.120> on<00:12:00.360> L1 00:12:00.769 --> 00:12:00.779 align:start position:0% hundred each on a two with the one on L1 00:12:00.779 --> 00:12:03.590 align:start position:0% hundred each on a two with the one on L1 and<00:12:01.560> it's<00:12:01.860> really<00:12:02.100> easy<00:12:02.399> so<00:12:03.000> these 00:12:03.590 --> 00:12:03.600 align:start position:0% and it's really easy so these 00:12:03.600 --> 00:12:05.750 align:start position:0% and it's really easy so these centralized<00:12:04.079> exchanges<00:12:04.620> they<00:12:04.860> have<00:12:05.040> piles<00:12:05.519> of 00:12:05.750 --> 00:12:05.760 align:start position:0% centralized exchanges they have piles of 00:12:05.760 --> 00:12:08.269 align:start position:0% centralized exchanges they have piles of eth<00:12:06.480> on<00:12:06.720> both<00:12:06.899> L2<00:12:07.320> and<00:12:07.440> L1<00:12:07.740> and<00:12:07.980> you<00:12:08.160> can 00:12:08.269 --> 00:12:08.279 align:start position:0% eth on both L2 and L1 and you can 00:12:08.279 --> 00:12:09.949 align:start position:0% eth on both L2 and L1 and you can actually<00:12:08.459> trade<00:12:08.760> with<00:12:08.940> them<00:12:09.180> so<00:12:09.779> this 00:12:09.949 --> 00:12:09.959 align:start position:0% actually trade with them so this 00:12:09.959 --> 00:12:11.569 align:start position:0% actually trade with them so this solution<00:12:10.200> works<00:12:10.620> a<00:12:10.860> lot<00:12:10.920> of<00:12:11.040> people<00:12:11.160> have<00:12:11.459> been 00:12:11.569 --> 00:12:11.579 align:start position:0% solution works a lot of people have been 00:12:11.579 --> 00:12:13.490 align:start position:0% solution works a lot of people have been using<00:12:11.940> it<00:12:12.060> but<00:12:12.360> the<00:12:12.600> problem<00:12:12.720> with<00:12:13.019> that<00:12:13.200> is 00:12:13.490 --> 00:12:13.500 align:start position:0% using it but the problem with that is 00:12:13.500 --> 00:12:17.389 align:start position:0% using it but the problem with that is it's<00:12:13.980> centralized<00:12:14.779> so<00:12:15.779> now<00:12:16.260> we<00:12:16.620> ask<00:12:16.860> ourselves 00:12:17.389 --> 00:12:17.399 align:start position:0% it's centralized so now we ask ourselves 00:12:17.399 --> 00:12:19.430 align:start position:0% it's centralized so now we ask ourselves is<00:12:17.700> there<00:12:17.880> any<00:12:18.120> way<00:12:18.360> we<00:12:18.600> can<00:12:18.779> do<00:12:18.899> it<00:12:19.019> in<00:12:19.320> a 00:12:19.430 --> 00:12:19.440 align:start position:0% is there any way we can do it in a 00:12:19.440 --> 00:12:22.069 align:start position:0% is there any way we can do it in a decentralized<00:12:20.160> way 00:12:22.069 --> 00:12:22.079 align:start position:0% decentralized way 00:12:22.079 --> 00:12:25.310 align:start position:0% decentralized way and<00:12:23.040> uh<00:12:23.459> so<00:12:23.760> that's<00:12:24.120> where<00:12:24.480> we<00:12:24.720> go<00:12:24.959> to<00:12:25.140> the 00:12:25.310 --> 00:12:25.320 align:start position:0% and uh so that's where we go to the 00:12:25.320 --> 00:12:27.650 align:start position:0% and uh so that's where we go to the second<00:12:25.440> solution<00:12:25.920> so<00:12:26.339> the<00:12:26.579> story<00:12:26.820> is<00:12:27.060> Alice<00:12:27.540> is 00:12:27.650 --> 00:12:27.660 align:start position:0% second solution so the story is Alice is 00:12:27.660 --> 00:12:30.050 align:start position:0% second solution so the story is Alice is holding<00:12:28.019> 100<00:12:28.140> East<00:12:28.500> on<00:12:28.740> L2<00:12:29.040> right 00:12:30.050 --> 00:12:30.060 align:start position:0% holding 100 East on L2 right 00:12:30.060 --> 00:12:33.250 align:start position:0% holding 100 East on L2 right so<00:12:30.779> if<00:12:31.380> it<00:12:31.560> happens<00:12:31.740> to<00:12:32.100> be<00:12:32.279> some<00:12:32.820> somebody 00:12:33.250 --> 00:12:33.260 align:start position:0% so if it happens to be some somebody 00:12:33.260 --> 00:12:36.230 align:start position:0% so if it happens to be some somebody somewhere<00:12:34.260> that<00:12:34.680> that<00:12:34.980> has<00:12:35.399> the<00:12:35.640> exact<00:12:35.940> same 00:12:36.230 --> 00:12:36.240 align:start position:0% somewhere that that has the exact same 00:12:36.240 --> 00:12:39.170 align:start position:0% somewhere that that has the exact same amount<00:12:36.540> of<00:12:36.779> if<00:12:37.019> on<00:12:37.680> L1<00:12:38.040> and<00:12:38.579> is<00:12:38.760> willing<00:12:39.060> to 00:12:39.170 --> 00:12:39.180 align:start position:0% amount of if on L1 and is willing to 00:12:39.180 --> 00:12:41.210 align:start position:0% amount of if on L1 and is willing to trade<00:12:39.420> that<00:12:39.600> with<00:12:39.779> Alice<00:12:40.260> then<00:12:40.740> they<00:12:40.920> can<00:12:41.040> do 00:12:41.210 --> 00:12:41.220 align:start position:0% trade that with Alice then they can do 00:12:41.220 --> 00:12:43.550 align:start position:0% trade that with Alice then they can do something<00:12:41.519> called<00:12:41.880> Atomic<00:12:42.420> swap<00:12:42.779> so<00:12:43.260> I'm<00:12:43.380> not 00:12:43.550 --> 00:12:43.560 align:start position:0% something called Atomic swap so I'm not 00:12:43.560 --> 00:12:45.170 align:start position:0% something called Atomic swap so I'm not gonna<00:12:43.740> go<00:12:44.040> through<00:12:44.220> the<00:12:44.459> details<00:12:44.820> of<00:12:45.000> what 00:12:45.170 --> 00:12:45.180 align:start position:0% gonna go through the details of what 00:12:45.180 --> 00:12:48.290 align:start position:0% gonna go through the details of what Atomic<00:12:45.600> swap<00:12:45.899> is<00:12:46.139> but<00:12:46.740> it's<00:12:46.980> basically<00:12:47.339> like<00:12:47.760> a 00:12:48.290 --> 00:12:48.300 align:start position:0% Atomic swap is but it's basically like a 00:12:48.300 --> 00:12:49.870 align:start position:0% Atomic swap is but it's basically like a little<00:12:48.480> of<00:12:48.779> crypto 00:12:49.870 --> 00:12:49.880 align:start position:0% little of crypto 00:12:49.880 --> 00:12:52.550 align:start position:0% little of crypto combined<00:12:50.880> with<00:12:51.000> smart<00:12:51.240> contract<00:12:51.720> that<00:12:52.079> allows 00:12:52.550 --> 00:12:52.560 align:start position:0% combined with smart contract that allows 00:12:52.560 --> 00:12:55.310 align:start position:0% combined with smart contract that allows you<00:12:52.740> to<00:12:53.220> basically<00:12:53.639> do<00:12:54.120> transactions<00:12:54.839> on<00:12:55.139> two 00:12:55.310 --> 00:12:55.320 align:start position:0% you to basically do transactions on two 00:12:55.320 --> 00:12:57.590 align:start position:0% you to basically do transactions on two different<00:12:55.500> chains<00:12:56.040> at<00:12:56.279> the<00:12:56.339> same<00:12:56.519> time<00:12:56.760> so 00:12:57.590 --> 00:12:57.600 align:start position:0% different chains at the same time so 00:12:57.600 --> 00:12:59.090 align:start position:0% different chains at the same time so it's<00:12:57.720> like<00:12:57.959> arbits<00:12:58.620> from<00:12:58.680> here<00:12:58.800> is<00:12:58.980> a 00:12:59.090 --> 00:12:59.100 align:start position:0% it's like arbits from here is a 00:12:59.100 --> 00:13:01.310 align:start position:0% it's like arbits from here is a different<00:12:59.160> chain<00:12:59.399> than<00:12:59.639> a<00:13:00.240> term<00:13:00.420> right 00:13:01.310 --> 00:13:01.320 align:start position:0% different chain than a term right 00:13:01.320 --> 00:13:04.490 align:start position:0% different chain than a term right so<00:13:01.860> it's<00:13:01.980> like<00:13:02.279> uh<00:13:03.180> both<00:13:03.360> Alice<00:13:03.779> and<00:13:03.899> Bob<00:13:04.079> they 00:13:04.490 --> 00:13:04.500 align:start position:0% so it's like uh both Alice and Bob they 00:13:04.500 --> 00:13:07.190 align:start position:0% so it's like uh both Alice and Bob they agree<00:13:04.920> on<00:13:05.399> Atomic<00:13:06.000> swap<00:13:06.360> so<00:13:06.720> they<00:13:06.899> have<00:13:07.019> to 00:13:07.190 --> 00:13:07.200 align:start position:0% agree on Atomic swap so they have to 00:13:07.200 --> 00:13:09.590 align:start position:0% agree on Atomic swap so they have to lock<00:13:07.380> up<00:13:07.740> some<00:13:07.980> money<00:13:08.220> and<00:13:08.940> then<00:13:09.060> there<00:13:09.360> is<00:13:09.480> a 00:13:09.590 --> 00:13:09.600 align:start position:0% lock up some money and then there is a 00:13:09.600 --> 00:13:12.230 align:start position:0% lock up some money and then there is a secret<00:13:09.779> somewhere<00:13:10.320> that<00:13:10.680> uh<00:13:11.279> if<00:13:11.459> it's<00:13:11.639> if<00:13:12.000> it's 00:13:12.230 --> 00:13:12.240 align:start position:0% secret somewhere that uh if it's if it's 00:13:12.240 --> 00:13:14.150 align:start position:0% secret somewhere that uh if it's if it's revealed<00:13:12.839> on<00:13:13.079> one<00:13:13.200> chain<00:13:13.380> then<00:13:13.740> you<00:13:13.920> can<00:13:13.980> use 00:13:14.150 --> 00:13:14.160 align:start position:0% revealed on one chain then you can use 00:13:14.160 --> 00:13:15.590 align:start position:0% revealed on one chain then you can use it<00:13:14.279> to<00:13:14.459> send<00:13:14.639> a<00:13:14.820> transaction<00:13:15.120> on<00:13:15.480> another 00:13:15.590 --> 00:13:15.600 align:start position:0% it to send a transaction on another 00:13:15.600 --> 00:13:17.930 align:start position:0% it to send a transaction on another chain<00:13:15.899> so<00:13:16.139> it's<00:13:16.260> either<00:13:16.500> like<00:13:16.860> either<00:13:17.459> both 00:13:17.930 --> 00:13:17.940 align:start position:0% chain so it's either like either both 00:13:17.940 --> 00:13:20.150 align:start position:0% chain so it's either like either both transaction<00:13:18.480> goes<00:13:19.320> through<00:13:19.500> at<00:13:19.860> the<00:13:20.040> same 00:13:20.150 --> 00:13:20.160 align:start position:0% transaction goes through at the same 00:13:20.160 --> 00:13:22.370 align:start position:0% transaction goes through at the same time<00:13:20.339> or<00:13:20.700> they<00:13:20.820> don't<00:13:21.000> go<00:13:21.180> through<00:13:21.360> at<00:13:21.600> all<00:13:21.779> so 00:13:22.370 --> 00:13:22.380 align:start position:0% time or they don't go through at all so 00:13:22.380 --> 00:13:24.410 align:start position:0% time or they don't go through at all so this<00:13:22.560> is<00:13:22.620> the<00:13:22.800> beauty<00:13:22.920> of<00:13:23.160> atomic<00:13:23.579> swap<00:13:23.880> so 00:13:24.410 --> 00:13:24.420 align:start position:0% this is the beauty of atomic swap so 00:13:24.420 --> 00:13:26.750 align:start position:0% this is the beauty of atomic swap so it's<00:13:24.540> perfect<00:13:24.839> it<00:13:25.440> works<00:13:25.860> but<00:13:26.160> the<00:13:26.579> problem 00:13:26.750 --> 00:13:26.760 align:start position:0% it's perfect it works but the problem 00:13:26.760 --> 00:13:28.790 align:start position:0% it's perfect it works but the problem with<00:13:27.060> that<00:13:27.240> that<00:13:27.540> you<00:13:27.779> might<00:13:27.959> have<00:13:28.079> noticed<00:13:28.500> is 00:13:28.790 --> 00:13:28.800 align:start position:0% with that that you might have noticed is 00:13:28.800 --> 00:13:32.210 align:start position:0% with that that you might have noticed is that<00:13:29.100> Bob<00:13:29.940> can<00:13:30.240> agree<00:13:30.720> to<00:13:31.200> do<00:13:31.320> the<00:13:31.500> atomic<00:13:31.860> swap 00:13:32.210 --> 00:13:32.220 align:start position:0% that Bob can agree to do the atomic swap 00:13:32.220 --> 00:13:34.009 align:start position:0% that Bob can agree to do the atomic swap but<00:13:32.459> then<00:13:32.639> he<00:13:32.880> can<00:13:33.060> just<00:13:33.240> disappear<00:13:33.720> in<00:13:33.899> the 00:13:34.009 --> 00:13:34.019 align:start position:0% but then he can just disappear in the 00:13:34.019 --> 00:13:36.110 align:start position:0% but then he can just disappear in the middle<00:13:34.139> of<00:13:34.320> the<00:13:34.500> protocol<00:13:34.740> so<00:13:35.639> there's<00:13:35.880> some 00:13:36.110 --> 00:13:36.120 align:start position:0% middle of the protocol so there's some 00:13:36.120 --> 00:13:38.569 align:start position:0% middle of the protocol so there's some time<00:13:36.300> window<00:13:36.540> for<00:13:36.899> Alice<00:13:37.200> to<00:13:37.440> go<00:13:37.620> back<00:13:37.860> and<00:13:38.339> get 00:13:38.569 --> 00:13:38.579 align:start position:0% time window for Alice to go back and get 00:13:38.579 --> 00:13:40.670 align:start position:0% time window for Alice to go back and get whatever<00:13:38.820> she<00:13:39.120> has<00:13:39.300> locked<00:13:39.660> up<00:13:39.720> before<00:13:39.899> but 00:13:40.670 --> 00:13:40.680 align:start position:0% whatever she has locked up before but 00:13:40.680 --> 00:13:42.350 align:start position:0% whatever she has locked up before but it's<00:13:40.860> actually<00:13:41.100> very<00:13:41.399> awkward<00:13:41.760> because<00:13:42.240> she's 00:13:42.350 --> 00:13:42.360 align:start position:0% it's actually very awkward because she's 00:13:42.360 --> 00:13:44.150 align:start position:0% it's actually very awkward because she's not<00:13:42.600> getting<00:13:42.720> what<00:13:42.959> she<00:13:43.200> wants<00:13:43.500> and<00:13:43.980> she's 00:13:44.150 --> 00:13:44.160 align:start position:0% not getting what she wants and she's 00:13:44.160 --> 00:13:46.190 align:start position:0% not getting what she wants and she's actually<00:13:44.459> losing<00:13:45.000> some<00:13:45.180> time<00:13:45.360> here 00:13:46.190 --> 00:13:46.200 align:start position:0% actually losing some time here 00:13:46.200 --> 00:13:48.889 align:start position:0% actually losing some time here so<00:13:46.680> we<00:13:46.860> go<00:13:47.040> to<00:13:47.160> the<00:13:47.279> third<00:13:47.459> solution<00:13:47.880> so<00:13:48.660> we're 00:13:48.889 --> 00:13:48.899 align:start position:0% so we go to the third solution so we're 00:13:48.899 --> 00:13:51.170 align:start position:0% so we go to the third solution so we're like<00:13:49.079> hey<00:13:49.920> Alice<00:13:50.279> we<00:13:50.639> know<00:13:50.760> that<00:13:51.000> you 00:13:51.170 --> 00:13:51.180 align:start position:0% like hey Alice we know that you 00:13:51.180 --> 00:13:53.090 align:start position:0% like hey Alice we know that you initiated<00:13:51.600> your<00:13:51.839> withdraw<00:13:52.380> transaction<00:13:52.740> on 00:13:53.090 --> 00:13:53.100 align:start position:0% initiated your withdraw transaction on 00:13:53.100 --> 00:13:56.329 align:start position:0% initiated your withdraw transaction on L2<00:13:53.519> and<00:13:54.420> uh<00:13:54.959> from<00:13:55.200> L2<00:13:55.560> and<00:13:55.860> then<00:13:55.980> now<00:13:56.160> you're 00:13:56.329 --> 00:13:56.339 align:start position:0% L2 and uh from L2 and then now you're 00:13:56.339 --> 00:13:57.769 align:start position:0% L2 and uh from L2 and then now you're waiting<00:13:56.820> for<00:13:56.940> your<00:13:57.120> assertion<00:13:57.480> to<00:13:57.660> be 00:13:57.769 --> 00:13:57.779 align:start position:0% waiting for your assertion to be 00:13:57.779 --> 00:14:00.470 align:start position:0% waiting for your assertion to be finalized<00:13:58.320> what<00:13:58.920> we<00:13:59.100> can<00:13:59.279> do<00:13:59.399> is<00:13:59.700> we<00:14:00.180> can<00:14:00.300> give 00:14:00.470 --> 00:14:00.480 align:start position:0% finalized what we can do is we can give 00:14:00.480 --> 00:14:03.410 align:start position:0% finalized what we can do is we can give you<00:14:00.600> a<00:14:00.779> ticket<00:14:00.959> actually<00:14:01.500> that<00:14:02.459> says<00:14:02.820> you<00:14:03.300> are 00:14:03.410 --> 00:14:03.420 align:start position:0% you a ticket actually that says you are 00:14:03.420 --> 00:14:05.389 align:start position:0% you a ticket actually that says you are actually<00:14:03.720> the<00:14:04.079> owner<00:14:04.380> of<00:14:04.620> this<00:14:04.740> hundred<00:14:05.100> each 00:14:05.389 --> 00:14:05.399 align:start position:0% actually the owner of this hundred each 00:14:05.399 --> 00:14:07.250 align:start position:0% actually the owner of this hundred each and<00:14:05.940> then<00:14:06.120> you<00:14:06.420> can<00:14:06.540> do<00:14:06.660> whatever<00:14:06.779> you<00:14:07.139> want 00:14:07.250 --> 00:14:07.260 align:start position:0% and then you can do whatever you want 00:14:07.260 --> 00:14:09.290 align:start position:0% and then you can do whatever you want with<00:14:07.440> the<00:14:07.620> ticket<00:14:07.800> you<00:14:08.339> can<00:14:08.459> go<00:14:08.639> ahead<00:14:08.880> you<00:14:09.180> can 00:14:09.290 --> 00:14:09.300 align:start position:0% with the ticket you can go ahead you can 00:14:09.300 --> 00:14:11.569 align:start position:0% with the ticket you can go ahead you can transfer<00:14:09.959> it<00:14:10.079> to<00:14:10.260> Bob<00:14:10.440> that's<00:14:11.040> fine<00:14:11.279> even 00:14:11.569 --> 00:14:11.579 align:start position:0% transfer it to Bob that's fine even 00:14:11.579 --> 00:14:14.389 align:start position:0% transfer it to Bob that's fine even though<00:14:11.820> the<00:14:12.060> seven<00:14:12.180> day<00:14:12.420> has<00:14:12.660> not<00:14:12.839> passed<00:14:13.560> so 00:14:14.389 --> 00:14:14.399 align:start position:0% though the seven day has not passed so 00:14:14.399 --> 00:14:15.350 align:start position:0% though the seven day has not passed so uh 00:14:15.350 --> 00:14:15.360 align:start position:0% uh 00:14:15.360 --> 00:14:17.449 align:start position:0% uh so<00:14:15.839> it's<00:14:15.899> basically<00:14:16.200> like<00:14:16.440> we're<00:14:16.680> giving<00:14:16.980> a 00:14:17.449 --> 00:14:17.459 align:start position:0% so it's basically like we're giving a 00:14:17.459 --> 00:14:20.509 align:start position:0% so it's basically like we're giving a tradable<00:14:17.880> ticket<00:14:18.420> or<00:14:19.139> a<00:14:19.320> claim<00:14:19.620> of<00:14:20.279> whatever 00:14:20.509 --> 00:14:20.519 align:start position:0% tradable ticket or a claim of whatever 00:14:20.519 --> 00:14:22.850 align:start position:0% tradable ticket or a claim of whatever is<00:14:20.940> going<00:14:21.180> to<00:14:21.360> go<00:14:21.600> out<00:14:21.959> of<00:14:22.079> the<00:14:22.260> bridge<00:14:22.380> after 00:14:22.850 --> 00:14:22.860 align:start position:0% is going to go out of the bridge after 00:14:22.860 --> 00:14:24.949 align:start position:0% is going to go out of the bridge after the<00:14:23.100> seven<00:14:23.279> days<00:14:23.519> and<00:14:24.000> as<00:14:24.180> I<00:14:24.300> said<00:14:24.480> these<00:14:24.899> are 00:14:24.949 --> 00:14:24.959 align:start position:0% the seven days and as I said these are 00:14:24.959 --> 00:14:26.990 align:start position:0% the seven days and as I said these are tradable<00:14:25.380> they<00:14:25.620> can<00:14:25.800> transfer<00:14:26.220> it 00:14:26.990 --> 00:14:27.000 align:start position:0% tradable they can transfer it 00:14:27.000 --> 00:14:29.750 align:start position:0% tradable they can transfer it so<00:14:27.660> if<00:14:27.959> Bob<00:14:28.200> happens<00:14:28.560> to<00:14:28.860> be<00:14:28.980> an<00:14:29.160> Orbitz<00:14:29.519> from 00:14:29.750 --> 00:14:29.760 align:start position:0% so if Bob happens to be an Orbitz from 00:14:29.760 --> 00:14:32.269 align:start position:0% so if Bob happens to be an Orbitz from validator<00:14:30.240> it<00:14:30.660> means<00:14:30.899> that<00:14:31.139> he<00:14:31.500> can<00:14:31.740> be<00:14:32.100> sure 00:14:32.269 --> 00:14:32.279 align:start position:0% validator it means that he can be sure 00:14:32.279 --> 00:14:33.710 align:start position:0% validator it means that he can be sure if<00:14:32.700> the<00:14:32.820> assertion<00:14:33.180> is<00:14:33.300> going<00:14:33.480> to<00:14:33.600> go 00:14:33.710 --> 00:14:33.720 align:start position:0% if the assertion is going to go 00:14:33.720 --> 00:14:36.110 align:start position:0% if the assertion is going to go finalized<00:14:34.500> or<00:14:34.620> not<00:14:34.800> so<00:14:35.220> what<00:14:35.459> she<00:14:35.700> does<00:14:35.880> is 00:14:36.110 --> 00:14:36.120 align:start position:0% finalized or not so what she does is 00:14:36.120 --> 00:14:38.090 align:start position:0% finalized or not so what she does is what<00:14:36.360> Alice<00:14:36.660> does<00:14:36.839> is<00:14:37.079> that<00:14:37.380> she<00:14:37.800> can<00:14:37.980> actually 00:14:38.090 --> 00:14:38.100 align:start position:0% what Alice does is that she can actually 00:14:38.100 --> 00:14:40.730 align:start position:0% what Alice does is that she can actually go<00:14:38.399> to<00:14:38.579> Bob<00:14:38.880> and<00:14:39.420> she'll<00:14:39.540> be<00:14:39.720> like<00:14:39.839> hey<00:14:40.079> Bob<00:14:40.260> I 00:14:40.730 --> 00:14:40.740 align:start position:0% go to Bob and she'll be like hey Bob I 00:14:40.740 --> 00:14:42.170 align:start position:0% go to Bob and she'll be like hey Bob I know<00:14:40.860> that<00:14:41.100> you're<00:14:41.399> you're<00:14:41.820> actually 00:14:42.170 --> 00:14:42.180 align:start position:0% know that you're you're actually 00:14:42.180 --> 00:14:44.210 align:start position:0% know that you're you're actually validating<00:14:42.779> everything<00:14:43.139> and<00:14:43.740> you<00:14:43.920> might<00:14:44.040> not 00:14:44.210 --> 00:14:44.220 align:start position:0% validating everything and you might not 00:14:44.220 --> 00:14:46.610 align:start position:0% validating everything and you might not even<00:14:44.339> care<00:14:44.639> about<00:14:44.760> my<00:14:45.000> withdrawal<00:14:45.600> but<00:14:46.199> what<00:14:46.440> I 00:14:46.610 --> 00:14:46.620 align:start position:0% even care about my withdrawal but what I 00:14:46.620 --> 00:14:47.810 align:start position:0% even care about my withdrawal but what I can<00:14:46.740> offer<00:14:47.040> you 00:14:47.810 --> 00:14:47.820 align:start position:0% can offer you 00:14:47.820 --> 00:14:49.490 align:start position:0% can offer you is<00:14:48.180> that<00:14:48.360> I<00:14:48.480> have<00:14:48.600> this<00:14:48.720> ticket<00:14:48.959> that<00:14:49.260> worth 00:14:49.490 --> 00:14:49.500 align:start position:0% is that I have this ticket that worth 00:14:49.500 --> 00:14:52.310 align:start position:0% is that I have this ticket that worth 100<00:14:49.740> ether<00:14:50.399> in<00:14:50.880> seven<00:14:51.060> days<00:14:51.360> so<00:14:51.839> what<00:14:52.019> you<00:14:52.199> can 00:14:52.310 --> 00:14:52.320 align:start position:0% 100 ether in seven days so what you can 00:14:52.320 --> 00:14:54.290 align:start position:0% 100 ether in seven days so what you can do<00:14:52.500> is<00:14:52.680> I<00:14:52.920> give<00:14:53.040> you<00:14:53.160> a<00:14:53.339> discount<00:14:53.459> or<00:14:53.820> a<00:14:54.000> bonus 00:14:54.290 --> 00:14:54.300 align:start position:0% do is I give you a discount or a bonus 00:14:54.300 --> 00:14:57.050 align:start position:0% do is I give you a discount or a bonus you<00:14:55.079> can<00:14:55.199> buy<00:14:55.680> my<00:14:55.980> ticket<00:14:56.100> because<00:14:56.639> you<00:14:56.880> know 00:14:57.050 --> 00:14:57.060 align:start position:0% you can buy my ticket because you know 00:14:57.060 --> 00:14:58.250 align:start position:0% you can buy my ticket because you know that<00:14:57.240> this<00:14:57.420> assertion<00:14:57.839> is<00:14:57.959> going<00:14:58.079> to<00:14:58.139> be 00:14:58.250 --> 00:14:58.260 align:start position:0% that this assertion is going to be 00:14:58.260 --> 00:15:01.550 align:start position:0% that this assertion is going to be finalized<00:14:58.920> and<00:14:59.639> then<00:14:59.940> uh<00:15:00.600> you<00:15:01.079> get<00:15:01.260> the<00:15:01.380> ticket 00:15:01.550 --> 00:15:01.560 align:start position:0% finalized and then uh you get the ticket 00:15:01.560 --> 00:15:03.769 align:start position:0% finalized and then uh you get the ticket you<00:15:01.920> get<00:15:02.220> the<00:15:02.339> ticket<00:15:02.459> you<00:15:02.760> get<00:15:02.880> the<00:15:02.940> bonus<00:15:03.300> and 00:15:03.769 --> 00:15:03.779 align:start position:0% you get the ticket you get the bonus and 00:15:03.779 --> 00:15:05.090 align:start position:0% you get the ticket you get the bonus and then<00:15:03.899> at<00:15:04.019> the<00:15:04.199> end<00:15:04.260> of<00:15:04.380> the<00:15:04.440> day<00:15:04.620> you<00:15:04.980> have 00:15:05.090 --> 00:15:05.100 align:start position:0% then at the end of the day you have 00:15:05.100 --> 00:15:08.569 align:start position:0% then at the end of the day you have profit<00:15:05.579> so<00:15:06.240> Bob<00:15:06.420> can<00:15:06.660> do<00:15:06.839> that<00:15:06.959> it's<00:15:07.139> great<00:15:07.579> but 00:15:08.569 --> 00:15:08.579 align:start position:0% profit so Bob can do that it's great but 00:15:08.579 --> 00:15:11.750 align:start position:0% profit so Bob can do that it's great but as<00:15:09.000> you<00:15:09.120> may<00:15:09.240> have<00:15:09.420> noticed<00:15:09.839> Bob<00:15:10.500> here 00:15:11.750 --> 00:15:11.760 align:start position:0% as you may have noticed Bob here 00:15:11.760 --> 00:15:14.990 align:start position:0% as you may have noticed Bob here is<00:15:12.420> having<00:15:12.779> two<00:15:13.139> roles<00:15:13.500> so<00:15:14.100> first<00:15:14.279> off<00:15:14.459> he<00:15:14.820> has 00:15:14.990 --> 00:15:15.000 align:start position:0% is having two roles so first off he has 00:15:15.000 --> 00:15:17.269 align:start position:0% is having two roles so first off he has to<00:15:15.180> have<00:15:15.300> the<00:15:15.480> liquidity<00:15:16.019> meaning<00:15:16.740> that<00:15:17.040> he 00:15:17.269 --> 00:15:17.279 align:start position:0% to have the liquidity meaning that he 00:15:17.279 --> 00:15:20.150 align:start position:0% to have the liquidity meaning that he has<00:15:17.459> to<00:15:17.579> be<00:15:17.760> sitting<00:15:18.120> on<00:15:18.480> a<00:15:18.720> pile<00:15:18.839> of<00:15:19.019> East<00:15:19.260> and 00:15:20.150 --> 00:15:20.160 align:start position:0% has to be sitting on a pile of East and 00:15:20.160 --> 00:15:21.829 align:start position:0% has to be sitting on a pile of East and his<00:15:20.399> he<00:15:20.760> has<00:15:20.940> to<00:15:21.000> be<00:15:21.120> willing<00:15:21.420> to<00:15:21.540> trade<00:15:21.720> it 00:15:21.829 --> 00:15:21.839 align:start position:0% his he has to be willing to trade it 00:15:21.839 --> 00:15:24.410 align:start position:0% his he has to be willing to trade it with<00:15:22.019> Alice<00:15:22.380> the<00:15:23.040> other<00:15:23.100> thing<00:15:23.339> is<00:15:23.519> Bob<00:15:23.880> needs 00:15:24.410 --> 00:15:24.420 align:start position:0% with Alice the other thing is Bob needs 00:15:24.420 --> 00:15:27.949 align:start position:0% with Alice the other thing is Bob needs to<00:15:24.540> run<00:15:24.899> an<00:15:25.500> evalidator<00:15:26.160> on<00:15:26.459> arbitrom<00:15:27.120> so<00:15:27.720> he 00:15:27.949 --> 00:15:27.959 align:start position:0% to run an evalidator on arbitrom so he 00:15:27.959 --> 00:15:29.689 align:start position:0% to run an evalidator on arbitrom so he needs<00:15:28.199> some<00:15:28.380> Assurance<00:15:28.680> he<00:15:29.100> needs<00:15:29.279> to<00:15:29.399> know 00:15:29.689 --> 00:15:29.699 align:start position:0% needs some Assurance he needs to know 00:15:29.699 --> 00:15:32.030 align:start position:0% needs some Assurance he needs to know that<00:15:30.180> this<00:15:30.360> assertion<00:15:30.839> is<00:15:31.019> gonna<00:15:31.199> go<00:15:31.440> finalize 00:15:32.030 --> 00:15:32.040 align:start position:0% that this assertion is gonna go finalize 00:15:32.040 --> 00:15:33.290 align:start position:0% that this assertion is gonna go finalize someday<00:15:32.459> otherwise<00:15:32.820> he's<00:15:33.000> not<00:15:33.180> really 00:15:33.290 --> 00:15:33.300 align:start position:0% someday otherwise he's not really 00:15:33.300 --> 00:15:35.569 align:start position:0% someday otherwise he's not really willing<00:15:33.660> to<00:15:33.779> trade<00:15:34.019> with<00:15:34.199> Alice<00:15:34.620> so<00:15:35.399> the 00:15:35.569 --> 00:15:35.579 align:start position:0% willing to trade with Alice so the 00:15:35.579 --> 00:15:36.949 align:start position:0% willing to trade with Alice so the problem<00:15:35.760> this<00:15:36.060> solution<00:15:36.360> is<00:15:36.480> really<00:15:36.660> great 00:15:36.949 --> 00:15:36.959 align:start position:0% problem this solution is really great 00:15:36.959 --> 00:15:39.949 align:start position:0% problem this solution is really great but<00:15:37.620> the<00:15:37.860> problem<00:15:37.980> with<00:15:38.279> that<00:15:38.459> is<00:15:38.699> uh<00:15:39.600> there's 00:15:39.949 --> 00:15:39.959 align:start position:0% but the problem with that is uh there's 00:15:39.959 --> 00:15:42.110 align:start position:0% but the problem with that is uh there's not<00:15:40.320> probably<00:15:40.740> a<00:15:41.040> lot<00:15:41.100> of<00:15:41.220> Bobs<00:15:41.579> in<00:15:41.760> this<00:15:41.940> world 00:15:42.110 --> 00:15:42.120 align:start position:0% not probably a lot of Bobs in this world 00:15:42.120 --> 00:15:44.030 align:start position:0% not probably a lot of Bobs in this world so<00:15:42.660> there<00:15:42.839> could<00:15:42.959> be<00:15:43.079> some<00:15:43.260> people<00:15:43.440> they<00:15:43.860> have 00:15:44.030 --> 00:15:44.040 align:start position:0% so there could be some people they have 00:15:44.040 --> 00:15:46.250 align:start position:0% so there could be some people they have the<00:15:44.220> liquidity<00:15:44.760> and<00:15:45.480> so<00:15:45.660> they<00:15:45.839> have<00:15:45.959> a<00:15:46.019> lot<00:15:46.139> of 00:15:46.250 --> 00:15:46.260 align:start position:0% the liquidity and so they have a lot of 00:15:46.260 --> 00:15:49.790 align:start position:0% the liquidity and so they have a lot of it<00:15:46.440> but<00:15:47.040> they're<00:15:47.639> not<00:15:47.880> necessarily<00:15:48.800> arbitrary 00:15:49.790 --> 00:15:49.800 align:start position:0% it but they're not necessarily arbitrary 00:15:49.800 --> 00:15:51.769 align:start position:0% it but they're not necessarily arbitrary validators<00:15:50.279> or<00:15:50.820> there<00:15:51.000> could<00:15:51.180> be<00:15:51.300> some<00:15:51.420> arbits 00:15:51.769 --> 00:15:51.779 align:start position:0% validators or there could be some arbits 00:15:51.779 --> 00:15:54.050 align:start position:0% validators or there could be some arbits from<00:15:51.839> validators<00:15:52.320> but<00:15:53.040> they're<00:15:53.220> not<00:15:53.519> sitting 00:15:54.050 --> 00:15:54.060 align:start position:0% from validators but they're not sitting 00:15:54.060 --> 00:15:55.850 align:start position:0% from validators but they're not sitting on<00:15:54.180> a<00:15:54.300> pile<00:15:54.420> of<00:15:54.600> eth<00:15:54.959> or<00:15:55.380> they're<00:15:55.560> not<00:15:55.740> even 00:15:55.850 --> 00:15:55.860 align:start position:0% on a pile of eth or they're not even 00:15:55.860 --> 00:15:58.250 align:start position:0% on a pile of eth or they're not even interested<00:15:56.399> in<00:15:56.760> participating<00:15:57.300> in<00:15:57.839> this<00:15:58.079> kind 00:15:58.250 --> 00:15:58.260 align:start position:0% interested in participating in this kind 00:15:58.260 --> 00:16:01.250 align:start position:0% interested in participating in this kind of<00:15:58.380> like<00:15:58.620> markets<00:15:59.399> they're<00:16:00.000> just<00:16:00.240> but<00:16:00.660> doing 00:16:01.250 --> 00:16:01.260 align:start position:0% of like markets they're just but doing 00:16:01.260 --> 00:16:02.990 align:start position:0% of like markets they're just but doing that<00:16:01.500> because<00:16:01.680> they<00:16:01.920> want<00:16:02.100> to<00:16:02.220> be<00:16:02.339> part<00:16:02.579> of<00:16:02.760> the 00:16:02.990 --> 00:16:03.000 align:start position:0% that because they want to be part of the 00:16:03.000 --> 00:16:04.910 align:start position:0% that because they want to be part of the arbitrary<00:16:03.720> ecosystem 00:16:04.910 --> 00:16:04.920 align:start position:0% arbitrary ecosystem 00:16:04.920 --> 00:16:07.490 align:start position:0% arbitrary ecosystem so<00:16:05.399> that's<00:16:05.699> the<00:16:06.000> problem<00:16:06.199> finding<00:16:07.199> these 00:16:07.490 --> 00:16:07.500 align:start position:0% so that's the problem finding these 00:16:07.500 --> 00:16:09.290 align:start position:0% so that's the problem finding these bulbs<00:16:07.860> that<00:16:08.040> work<00:16:08.279> for<00:16:08.519> the<00:16:08.699> both<00:16:08.880> side<00:16:09.060> of 00:16:09.290 --> 00:16:09.300 align:start position:0% bulbs that work for the both side of 00:16:09.300 --> 00:16:12.829 align:start position:0% bulbs that work for the both side of equations<00:16:09.660> is<00:16:10.139> not<00:16:10.320> really<00:16:10.560> easy<00:16:10.800> okay<00:16:11.399> so<00:16:12.000> we 00:16:12.829 --> 00:16:12.839 align:start position:0% equations is not really easy okay so we 00:16:12.839 --> 00:16:17.269 align:start position:0% equations is not really easy okay so we are<00:16:13.199> at<00:16:13.500> a<00:16:13.740> last<00:16:13.980> solution<00:16:14.459> we<00:16:15.120> so<00:16:15.720> uh<00:16:16.620> we<00:16:17.100> were 00:16:17.269 --> 00:16:17.279 align:start position:0% are at a last solution we so uh we were 00:16:17.279 --> 00:16:19.370 align:start position:0% are at a last solution we so uh we were like<00:16:17.459> is<00:16:18.060> there<00:16:18.180> any<00:16:18.360> way<00:16:18.540> we<00:16:18.720> can<00:16:18.899> split<00:16:19.199> Bob 00:16:19.370 --> 00:16:19.380 align:start position:0% like is there any way we can split Bob 00:16:19.380 --> 00:16:22.430 align:start position:0% like is there any way we can split Bob so<00:16:20.279> is<00:16:20.459> there<00:16:20.579> any<00:16:20.820> way<00:16:21.000> we<00:16:21.600> can<00:16:21.779> have<00:16:21.959> Alice 00:16:22.430 --> 00:16:22.440 align:start position:0% so is there any way we can have Alice 00:16:22.440 --> 00:16:24.710 align:start position:0% so is there any way we can have Alice she<00:16:22.800> wants<00:16:23.100> to<00:16:23.160> withdraw<00:16:23.579> 100<00:16:23.699> East<00:16:24.000> from<00:16:24.300> L2 00:16:24.710 --> 00:16:24.720 align:start position:0% she wants to withdraw 100 East from L2 00:16:24.720 --> 00:16:28.310 align:start position:0% she wants to withdraw 100 East from L2 then<00:16:25.440> we<00:16:25.620> have<00:16:25.800> David<00:16:26.279> who<00:16:27.120> is<00:16:27.300> the<00:16:27.899> arbits 00:16:28.310 --> 00:16:28.320 align:start position:0% then we have David who is the arbits 00:16:28.320 --> 00:16:29.810 align:start position:0% then we have David who is the arbits from<00:16:28.380> validator<00:16:28.800> but<00:16:29.100> he<00:16:29.279> doesn't<00:16:29.399> have<00:16:29.639> the 00:16:29.810 --> 00:16:29.820 align:start position:0% from validator but he doesn't have the 00:16:29.820 --> 00:16:32.389 align:start position:0% from validator but he doesn't have the liquidity<00:16:30.300> and<00:16:30.779> we<00:16:30.959> have<00:16:31.079> Carol<00:16:31.620> who<00:16:31.980> has<00:16:32.160> the 00:16:32.389 --> 00:16:32.399 align:start position:0% liquidity and we have Carol who has the 00:16:32.399 --> 00:16:34.910 align:start position:0% liquidity and we have Carol who has the liquidity<00:16:32.820> but<00:16:33.120> she's<00:16:33.300> not<00:16:33.480> a<00:16:33.660> validator<00:16:34.019> so 00:16:34.910 --> 00:16:34.920 align:start position:0% liquidity but she's not a validator so 00:16:34.920 --> 00:16:37.490 align:start position:0% liquidity but she's not a validator so is<00:16:35.100> there<00:16:35.279> any<00:16:35.519> way<00:16:35.760> these<00:16:36.660> three<00:16:36.779> can<00:16:37.139> arrange 00:16:37.490 --> 00:16:37.500 align:start position:0% is there any way these three can arrange 00:16:37.500 --> 00:16:40.249 align:start position:0% is there any way these three can arrange something<00:16:37.920> that<00:16:38.820> can<00:16:39.000> give<00:16:39.300> Alice<00:16:39.779> what<00:16:40.079> she 00:16:40.249 --> 00:16:40.259 align:start position:0% something that can give Alice what she 00:16:40.259 --> 00:16:42.710 align:start position:0% something that can give Alice what she wants<00:16:40.560> at<00:16:40.800> the<00:16:40.920> end<00:16:41.040> of<00:16:41.160> the<00:16:41.279> day<00:16:41.459> and<00:16:42.240> it<00:16:42.420> turns 00:16:42.710 --> 00:16:42.720 align:start position:0% wants at the end of the day and it turns 00:16:42.720 --> 00:16:44.389 align:start position:0% wants at the end of the day and it turns out<00:16:42.779> that<00:16:43.079> yes<00:16:43.259> there<00:16:43.560> is<00:16:43.740> a<00:16:43.860> solution<00:16:44.100> for 00:16:44.389 --> 00:16:44.399 align:start position:0% out that yes there is a solution for 00:16:44.399 --> 00:16:46.310 align:start position:0% out that yes there is a solution for that<00:16:44.519> we<00:16:44.820> have<00:16:45.000> this<00:16:45.180> solution<00:16:45.540> and<00:16:46.199> our 00:16:46.310 --> 00:16:46.320 align:start position:0% that we have this solution and our 00:16:46.320 --> 00:16:48.189 align:start position:0% that we have this solution and our solution<00:16:46.620> is<00:16:46.920> not<00:16:47.100> necessarily<00:16:47.519> the<00:16:47.759> only<00:16:47.940> one 00:16:48.189 --> 00:16:48.199 align:start position:0% solution is not necessarily the only one 00:16:48.199 --> 00:16:53.689 align:start position:0% solution is not necessarily the only one but<00:16:49.339> but<00:16:50.339> we<00:16:50.699> think<00:16:51.560> it<00:16:52.560> works<00:16:52.740> great 00:16:53.689 --> 00:16:53.699 align:start position:0% but but we think it works great 00:16:53.699 --> 00:16:55.850 align:start position:0% but but we think it works great so<00:16:54.360> the<00:16:54.660> solution<00:16:54.959> is<00:16:55.139> to<00:16:55.320> set<00:16:55.440> up<00:16:55.620> something 00:16:55.850 --> 00:16:55.860 align:start position:0% so the solution is to set up something 00:16:55.860 --> 00:16:58.790 align:start position:0% so the solution is to set up something called<00:16:56.279> a<00:16:56.759> prediction<00:16:57.120> market<00:16:57.420> so<00:16:58.199> what<00:16:58.440> is<00:16:58.620> a 00:16:58.790 --> 00:16:58.800 align:start position:0% called a prediction market so what is a 00:16:58.800 --> 00:17:01.129 align:start position:0% called a prediction market so what is a prediction<00:16:59.160> market<00:16:59.420> so<00:17:00.420> a<00:17:00.600> prediction<00:17:00.899> Market 00:17:01.129 --> 00:17:01.139 align:start position:0% prediction market so a prediction Market 00:17:01.139 --> 00:17:04.370 align:start position:0% prediction market so a prediction Market is<00:17:01.440> basically<00:17:01.920> a<00:17:02.519> betting<00:17:02.880> Market<00:17:03.060> but<00:17:04.020> with<00:17:04.199> a 00:17:04.370 --> 00:17:04.380 align:start position:0% is basically a betting Market but with a 00:17:04.380 --> 00:17:06.470 align:start position:0% is basically a betting Market but with a difference<00:17:04.500> that<00:17:04.980> you<00:17:05.400> can<00:17:05.520> get<00:17:05.760> inside<00:17:06.059> and 00:17:06.470 --> 00:17:06.480 align:start position:0% difference that you can get inside and 00:17:06.480 --> 00:17:08.150 align:start position:0% difference that you can get inside and outside<00:17:06.660> of<00:17:06.959> your<00:17:07.140> position 00:17:08.150 --> 00:17:08.160 align:start position:0% outside of your position 00:17:08.160 --> 00:17:09.949 align:start position:0% outside of your position so<00:17:08.280> in<00:17:08.520> a<00:17:08.699> betting<00:17:08.939> Market<00:17:09.059> what<00:17:09.419> happens<00:17:09.660> is 00:17:09.949 --> 00:17:09.959 align:start position:0% so in a betting Market what happens is 00:17:09.959 --> 00:17:12.470 align:start position:0% so in a betting Market what happens is you'll<00:17:10.740> have<00:17:10.860> you<00:17:11.160> can<00:17:11.220> place<00:17:11.400> a<00:17:11.579> bet<00:17:11.760> but<00:17:12.299> then 00:17:12.470 --> 00:17:12.480 align:start position:0% you'll have you can place a bet but then 00:17:12.480 --> 00:17:14.210 align:start position:0% you'll have you can place a bet but then you<00:17:12.660> cannot<00:17:12.900> transfer<00:17:13.380> it<00:17:13.500> or<00:17:13.679> you<00:17:13.860> can<00:17:13.980> you 00:17:14.210 --> 00:17:14.220 align:start position:0% you cannot transfer it or you can you 00:17:14.220 --> 00:17:15.650 align:start position:0% you cannot transfer it or you can you cannot<00:17:14.459> get<00:17:14.699> out<00:17:14.819> of<00:17:14.939> your<00:17:15.059> position<00:17:15.240> you<00:17:15.480> have 00:17:15.650 --> 00:17:15.660 align:start position:0% cannot get out of your position you have 00:17:15.660 --> 00:17:17.510 align:start position:0% cannot get out of your position you have to<00:17:15.720> sit<00:17:15.900> on<00:17:16.140> it<00:17:16.319> and<00:17:16.740> then<00:17:16.860> you<00:17:17.040> have<00:17:17.160> to<00:17:17.339> wait 00:17:17.510 --> 00:17:17.520 align:start position:0% to sit on it and then you have to wait 00:17:17.520 --> 00:17:20.210 align:start position:0% to sit on it and then you have to wait for<00:17:17.819> the<00:17:18.000> event<00:17:18.360> to<00:17:18.660> happen<00:17:18.900> but<00:17:19.679> on<00:17:20.040> the 00:17:20.210 --> 00:17:20.220 align:start position:0% for the event to happen but on the 00:17:20.220 --> 00:17:21.949 align:start position:0% for the event to happen but on the prediction<00:17:20.459> Market<00:17:20.760> on<00:17:21.240> the<00:17:21.360> other<00:17:21.480> side<00:17:21.660> what 00:17:21.949 --> 00:17:21.959 align:start position:0% prediction Market on the other side what 00:17:21.959 --> 00:17:24.650 align:start position:0% prediction Market on the other side what happens<00:17:22.140> is<00:17:22.380> let's<00:17:22.620> say<00:17:22.799> you<00:17:23.579> think<00:17:23.880> the<00:17:24.299> odds 00:17:24.650 --> 00:17:24.660 align:start position:0% happens is let's say you think the odds 00:17:24.660 --> 00:17:27.409 align:start position:0% happens is let's say you think the odds of<00:17:24.839> Joe<00:17:25.140> Biden<00:17:25.620> being<00:17:26.160> the<00:17:26.520> next<00:17:26.640> president<00:17:26.939> of 00:17:27.409 --> 00:17:27.419 align:start position:0% of Joe Biden being the next president of 00:17:27.419 --> 00:17:29.630 align:start position:0% of Joe Biden being the next president of the<00:17:27.600> United<00:17:27.660> States<00:17:28.079> is<00:17:28.439> so<00:17:28.679> high<00:17:28.860> so<00:17:29.340> what<00:17:29.460> you 00:17:29.630 --> 00:17:29.640 align:start position:0% the United States is so high so what you 00:17:29.640 --> 00:17:31.190 align:start position:0% the United States is so high so what you do<00:17:29.820> is<00:17:29.940> You're<00:17:30.120> Gonna<00:17:30.240> Go<00:17:30.540> place<00:17:30.780> a<00:17:31.020> bet 00:17:31.190 --> 00:17:31.200 align:start position:0% do is You're Gonna Go place a bet 00:17:31.200 --> 00:17:33.770 align:start position:0% do is You're Gonna Go place a bet against<00:17:31.440> it<00:17:31.740> in<00:17:32.400> three<00:17:32.580> months<00:17:32.940> the<00:17:33.360> odds<00:17:33.660> are 00:17:33.770 --> 00:17:33.780 align:start position:0% against it in three months the odds are 00:17:33.780 --> 00:17:35.750 align:start position:0% against it in three months the odds are actually<00:17:33.960> going<00:17:34.320> down<00:17:34.620> so<00:17:35.160> what<00:17:35.340> you<00:17:35.460> do<00:17:35.640> is 00:17:35.750 --> 00:17:35.760 align:start position:0% actually going down so what you do is 00:17:35.760 --> 00:17:37.789 align:start position:0% actually going down so what you do is you<00:17:36.000> can<00:17:36.120> actually<00:17:36.299> sell<00:17:36.660> your<00:17:36.900> position 00:17:37.789 --> 00:17:37.799 align:start position:0% you can actually sell your position 00:17:37.799 --> 00:17:39.890 align:start position:0% you can actually sell your position and<00:17:38.280> can<00:17:38.460> get<00:17:38.640> out<00:17:38.820> of<00:17:38.940> your<00:17:39.120> position<00:17:39.299> so<00:17:39.660> this 00:17:39.890 --> 00:17:39.900 align:start position:0% and can get out of your position so this 00:17:39.900 --> 00:17:41.690 align:start position:0% and can get out of your position so this is<00:17:40.020> the<00:17:40.140> difference<00:17:40.320> with<00:17:40.799> a<00:17:41.160> betting<00:17:41.520> market 00:17:41.690 --> 00:17:41.700 align:start position:0% is the difference with a betting market 00:17:41.700 --> 00:17:43.730 align:start position:0% is the difference with a betting market and<00:17:42.360> then<00:17:42.539> it's<00:17:42.960> really<00:17:43.140> like<00:17:43.320> a<00:17:43.440> betting 00:17:43.730 --> 00:17:43.740 align:start position:0% and then it's really like a betting 00:17:43.740 --> 00:17:46.070 align:start position:0% and then it's really like a betting Market<00:17:43.860> but<00:17:44.340> it<00:17:44.520> designed<00:17:44.940> more<00:17:45.120> kind<00:17:45.480> of<00:17:45.720> like 00:17:46.070 --> 00:17:46.080 align:start position:0% Market but it designed more kind of like 00:17:46.080 --> 00:17:48.289 align:start position:0% Market but it designed more kind of like stocks<00:17:46.860> I'd<00:17:47.100> say 00:17:48.289 --> 00:17:48.299 align:start position:0% stocks I'd say 00:17:48.299 --> 00:17:49.850 align:start position:0% stocks I'd say so<00:17:48.720> okay<00:17:48.840> so<00:17:49.140> we<00:17:49.320> have<00:17:49.440> this<00:17:49.559> prediction 00:17:49.850 --> 00:17:49.860 align:start position:0% so okay so we have this prediction 00:17:49.860 --> 00:17:52.070 align:start position:0% so okay so we have this prediction Market<00:17:50.100> the<00:17:50.400> way<00:17:50.580> we<00:17:50.760> set<00:17:50.940> up<00:17:51.120> it<00:17:51.299> is<00:17:51.480> we<00:17:51.900> put 00:17:52.070 --> 00:17:52.080 align:start position:0% Market the way we set up it is we put 00:17:52.080 --> 00:17:54.230 align:start position:0% Market the way we set up it is we put the<00:17:52.200> market<00:17:52.380> it's<00:17:53.160> really<00:17:53.340> like<00:17:53.640> a<00:17:53.820> vending 00:17:54.230 --> 00:17:54.240 align:start position:0% the market it's really like a vending 00:17:54.240 --> 00:17:56.270 align:start position:0% the market it's really like a vending machine<00:17:54.480> it's<00:17:55.080> there's<00:17:55.320> no<00:17:55.500> bookkeeping<00:17:56.100> or 00:17:56.270 --> 00:17:56.280 align:start position:0% machine it's there's no bookkeeping or 00:17:56.280 --> 00:17:58.070 align:start position:0% machine it's there's no bookkeeping or anything<00:17:56.520> it's<00:17:56.940> autonomous<00:17:57.480> smart<00:17:57.720> contract 00:17:58.070 --> 00:17:58.080 align:start position:0% anything it's autonomous smart contract 00:17:58.080 --> 00:18:01.730 align:start position:0% anything it's autonomous smart contract we<00:17:58.320> put<00:17:58.500> it<00:17:58.559> on<00:17:58.740> L1<00:17:59.120> and<00:18:00.120> uh<00:18:00.780> so<00:18:01.140> a<00:18:01.260> user<00:18:01.559> would 00:18:01.730 --> 00:18:01.740 align:start position:0% we put it on L1 and uh so a user would 00:18:01.740 --> 00:18:04.669 align:start position:0% we put it on L1 and uh so a user would go<00:18:01.919> to<00:18:02.039> it<00:18:02.280> I<00:18:02.580> can<00:18:02.700> go<00:18:02.880> to<00:18:03.000> it<00:18:03.240> I<00:18:03.720> deposit<00:18:04.320> one 00:18:04.669 --> 00:18:04.679 align:start position:0% go to it I can go to it I deposit one 00:18:04.679 --> 00:18:06.890 align:start position:0% go to it I can go to it I deposit one ether<00:18:05.039> inside<00:18:05.340> the<00:18:05.700> market<00:18:05.880> and<00:18:06.600> it<00:18:06.780> would 00:18:06.890 --> 00:18:06.900 align:start position:0% ether inside the market and it would 00:18:06.900 --> 00:18:11.210 align:start position:0% ether inside the market and it would give<00:18:07.140> me<00:18:07.320> two<00:18:07.799> shares<00:18:08.299> one<00:18:09.299> yester<00:18:10.260> and<00:18:10.679> one<00:18:10.919> no 00:18:11.210 --> 00:18:11.220 align:start position:0% give me two shares one yester and one no 00:18:11.220 --> 00:18:13.549 align:start position:0% give me two shares one yester and one no share<00:18:11.520> so<00:18:12.179> and<00:18:12.539> these<00:18:12.780> Shares<00:18:13.020> are<00:18:13.140> betting 00:18:13.549 --> 00:18:13.559 align:start position:0% share so and these Shares are betting 00:18:13.559 --> 00:18:15.049 align:start position:0% share so and these Shares are betting against<00:18:13.740> if<00:18:14.100> this<00:18:14.340> session<00:18:14.580> is<00:18:14.760> going<00:18:14.880> to<00:18:15.000> be 00:18:15.049 --> 00:18:15.059 align:start position:0% against if this session is going to be 00:18:15.059 --> 00:18:16.909 align:start position:0% against if this session is going to be finalized<00:18:15.539> or<00:18:15.720> not<00:18:15.900> so<00:18:16.500> at<00:18:16.679> the<00:18:16.799> very 00:18:16.909 --> 00:18:16.919 align:start position:0% finalized or not so at the very 00:18:16.919 --> 00:18:18.770 align:start position:0% finalized or not so at the very beginning<00:18:17.160> I'm<00:18:17.700> actually<00:18:17.880> covered<00:18:18.299> for<00:18:18.539> both 00:18:18.770 --> 00:18:18.780 align:start position:0% beginning I'm actually covered for both 00:18:18.780 --> 00:18:21.409 align:start position:0% beginning I'm actually covered for both cases<00:18:19.260> so<00:18:19.919> if<00:18:20.100> the<00:18:20.220> assertion<00:18:20.640> is<00:18:20.820> finalized 00:18:21.409 --> 00:18:21.419 align:start position:0% cases so if the assertion is finalized 00:18:21.419 --> 00:18:23.630 align:start position:0% cases so if the assertion is finalized my<00:18:21.840> yester<00:18:22.140> is<00:18:22.440> going<00:18:22.559> to<00:18:22.679> be<00:18:22.799> worth<00:18:22.980> one<00:18:23.220> ether 00:18:23.630 --> 00:18:23.640 align:start position:0% my yester is going to be worth one ether 00:18:23.640 --> 00:18:26.029 align:start position:0% my yester is going to be worth one ether and<00:18:24.240> my<00:18:24.419> no<00:18:24.539> shares<00:18:24.960> actually<00:18:25.320> worth<00:18:25.740> nothing 00:18:26.029 --> 00:18:26.039 align:start position:0% and my no shares actually worth nothing 00:18:26.039 --> 00:18:28.970 align:start position:0% and my no shares actually worth nothing and<00:18:27.000> on<00:18:27.720> the<00:18:27.900> other<00:18:27.960> side<00:18:28.140> if<00:18:28.380> the<00:18:28.559> assertion 00:18:28.970 --> 00:18:28.980 align:start position:0% and on the other side if the assertion 00:18:28.980 --> 00:18:31.430 align:start position:0% and on the other side if the assertion fails<00:18:29.340> there's<00:18:29.460> a<00:18:29.700> dispute<00:18:30.059> and<00:18:30.840> then<00:18:31.020> my<00:18:31.260> no 00:18:31.430 --> 00:18:31.440 align:start position:0% fails there's a dispute and then my no 00:18:31.440 --> 00:18:33.950 align:start position:0% fails there's a dispute and then my no share<00:18:31.799> is<00:18:31.919> going<00:18:32.100> to<00:18:32.280> be<00:18:32.400> worth<00:18:33.059> one<00:18:33.360> ether<00:18:33.720> and 00:18:33.950 --> 00:18:33.960 align:start position:0% share is going to be worth one ether and 00:18:33.960 --> 00:18:36.350 align:start position:0% share is going to be worth one ether and the<00:18:34.080> gestures<00:18:34.440> are<00:18:34.799> actually<00:18:34.980> nothing<00:18:35.460> so<00:18:36.179> in 00:18:36.350 --> 00:18:36.360 align:start position:0% the gestures are actually nothing so in 00:18:36.360 --> 00:18:37.909 align:start position:0% the gestures are actually nothing so in any<00:18:36.480> case<00:18:36.720> I<00:18:36.960> can<00:18:37.020> go<00:18:37.200> and<00:18:37.320> redeem<00:18:37.679> my<00:18:37.799> one 00:18:37.909 --> 00:18:37.919 align:start position:0% any case I can go and redeem my one 00:18:37.919 --> 00:18:40.730 align:start position:0% any case I can go and redeem my one ether<00:18:38.280> back<00:18:38.520> okay<00:18:39.120> so<00:18:39.539> how<00:18:40.020> does<00:18:40.140> it<00:18:40.260> work<00:18:40.500> so 00:18:40.730 --> 00:18:40.740 align:start position:0% ether back okay so how does it work so 00:18:40.740 --> 00:18:42.650 align:start position:0% ether back okay so how does it work so let's<00:18:40.919> say<00:18:41.100> Alice<00:18:41.460> wants<00:18:41.820> Alice<00:18:42.179> is<00:18:42.360> the<00:18:42.539> one 00:18:42.650 --> 00:18:42.660 align:start position:0% let's say Alice wants Alice is the one 00:18:42.660 --> 00:18:44.990 align:start position:0% let's say Alice wants Alice is the one who<00:18:42.900> wants<00:18:43.260> to<00:18:43.320> do<00:18:43.860> this<00:18:44.039> withdrawal<00:18:44.580> right<00:18:44.700> so 00:18:44.990 --> 00:18:45.000 align:start position:0% who wants to do this withdrawal right so 00:18:45.000 --> 00:18:46.669 align:start position:0% who wants to do this withdrawal right so she<00:18:45.360> initiates<00:18:45.840> the<00:18:46.020> withdrawal<00:18:46.440> and<00:18:46.559> she's 00:18:46.669 --> 00:18:46.679 align:start position:0% she initiates the withdrawal and she's 00:18:46.679 --> 00:18:49.549 align:start position:0% she initiates the withdrawal and she's like<00:18:46.860> okay<00:18:47.039> I<00:18:47.580> want<00:18:47.700> my<00:18:48.179> there<00:18:48.780> now<00:18:49.020> I<00:18:49.500> don't 00:18:49.549 --> 00:18:49.559 align:start position:0% like okay I want my there now I don't 00:18:49.559 --> 00:18:51.590 align:start position:0% like okay I want my there now I don't want<00:18:49.679> to<00:18:49.799> wait<00:18:49.919> for<00:18:50.160> seven<00:18:50.340> days<00:18:50.580> so<00:18:51.059> what<00:18:51.240> I<00:18:51.419> do 00:18:51.590 --> 00:18:51.600 align:start position:0% want to wait for seven days so what I do 00:18:51.600 --> 00:18:54.169 align:start position:0% want to wait for seven days so what I do is<00:18:51.720> I<00:18:51.960> come<00:18:52.140> along<00:18:52.320> I<00:18:52.559> go<00:18:52.740> to<00:18:52.860> this<00:18:53.039> market<00:18:53.220> and 00:18:54.169 --> 00:18:54.179 align:start position:0% is I come along I go to this market and 00:18:54.179 --> 00:18:56.750 align:start position:0% is I come along I go to this market and I<00:18:54.419> I<00:18:54.780> and<00:18:55.320> pay<00:18:55.860> attention<00:18:56.160> to<00:18:56.340> this<00:18:56.460> that<00:18:56.580> she 00:18:56.750 --> 00:18:56.760 align:start position:0% I I and pay attention to this that she 00:18:56.760 --> 00:18:58.850 align:start position:0% I I and pay attention to this that she wants<00:18:56.940> to<00:18:57.000> withdraw<00:18:57.299> 100<00:18:57.480> ether<00:18:57.900> so<00:18:58.500> what<00:18:58.679> she 00:18:58.850 --> 00:18:58.860 align:start position:0% wants to withdraw 100 ether so what she 00:18:58.860 --> 00:19:01.490 align:start position:0% wants to withdraw 100 ether so what she does<00:18:59.039> is<00:18:59.340> she<00:18:59.580> deposits<00:19:00.240> 100<00:19:00.419> if<00:19:00.840> inside<00:19:01.200> the 00:19:01.490 --> 00:19:01.500 align:start position:0% does is she deposits 100 if inside the 00:19:01.500 --> 00:19:03.470 align:start position:0% does is she deposits 100 if inside the smart<00:19:01.679> contract<00:19:02.039> the<00:19:02.280> market<00:19:02.520> and<00:19:03.179> what 00:19:03.470 --> 00:19:03.480 align:start position:0% smart contract the market and what 00:19:03.480 --> 00:19:05.630 align:start position:0% smart contract the market and what Market<00:19:03.720> does<00:19:04.080> it<00:19:04.559> actually<00:19:04.740> gives<00:19:05.160> Alice 00:19:05.630 --> 00:19:05.640 align:start position:0% Market does it actually gives Alice 00:19:05.640 --> 00:19:08.870 align:start position:0% Market does it actually gives Alice hundred<00:19:06.179> shares<00:19:06.720> of<00:19:07.200> yes<00:19:07.440> and<00:19:07.980> 100<00:19:08.220> shares<00:19:08.700> of 00:19:08.870 --> 00:19:08.880 align:start position:0% hundred shares of yes and 100 shares of 00:19:08.880 --> 00:19:12.470 align:start position:0% hundred shares of yes and 100 shares of no<00:19:09.080> so<00:19:10.080> if<00:19:10.919> Alice<00:19:11.400> actually<00:19:11.640> believes<00:19:12.179> that 00:19:12.470 --> 00:19:12.480 align:start position:0% no so if Alice actually believes that 00:19:12.480 --> 00:19:14.270 align:start position:0% no so if Alice actually believes that this<00:19:12.660> assertion<00:19:13.140> is<00:19:13.260> going<00:19:13.440> to<00:19:13.500> be<00:19:13.620> finalized 00:19:14.270 --> 00:19:14.280 align:start position:0% this assertion is going to be finalized 00:19:14.280 --> 00:19:16.130 align:start position:0% this assertion is going to be finalized and<00:19:14.580> at<00:19:14.700> the<00:19:14.880> end<00:19:14.940> of<00:19:15.059> the<00:19:15.240> day<00:19:15.360> her<00:19:15.600> ether<00:19:15.960> is 00:19:16.130 --> 00:19:16.140 align:start position:0% and at the end of the day her ether is 00:19:16.140 --> 00:19:18.169 align:start position:0% and at the end of the day her ether is going<00:19:16.320> to<00:19:16.440> get<00:19:16.559> out<00:19:16.799> of<00:19:16.919> the<00:19:17.100> bridge<00:19:17.280> but<00:19:18.000> she 00:19:18.169 --> 00:19:18.179 align:start position:0% going to get out of the bridge but she 00:19:18.179 --> 00:19:19.250 align:start position:0% going to get out of the bridge but she would<00:19:18.299> do 00:19:19.250 --> 00:19:19.260 align:start position:0% would do 00:19:19.260 --> 00:19:21.289 align:start position:0% would do so<00:19:19.740> she<00:19:19.980> would<00:19:20.220> keep<00:19:20.460> the<00:19:20.640> gestures<00:19:21.000> for 00:19:21.289 --> 00:19:21.299 align:start position:0% so she would keep the gestures for 00:19:21.299 --> 00:19:23.870 align:start position:0% so she would keep the gestures for herself<00:19:21.720> because<00:19:22.260> it's<00:19:22.559> a<00:19:22.740> bet<00:19:22.860> against<00:19:23.280> the 00:19:23.870 --> 00:19:23.880 align:start position:0% herself because it's a bet against the 00:19:23.880 --> 00:19:25.909 align:start position:0% herself because it's a bet against the assertions<00:19:24.360> being<00:19:24.600> finalized<00:19:25.200> and<00:19:25.559> she<00:19:25.740> would 00:19:25.909 --> 00:19:25.919 align:start position:0% assertions being finalized and she would 00:19:25.919 --> 00:19:27.110 align:start position:0% assertions being finalized and she would get<00:19:26.100> away 00:19:27.110 --> 00:19:27.120 align:start position:0% get away 00:19:27.120 --> 00:19:28.909 align:start position:0% get away there<00:19:27.600> are<00:19:27.720> no<00:19:27.780> shares<00:19:28.140> right<00:19:28.260> out<00:19:28.559> of<00:19:28.679> the<00:19:28.799> no 00:19:28.909 --> 00:19:28.919 align:start position:0% there are no shares right out of the no 00:19:28.919 --> 00:19:30.650 align:start position:0% there are no shares right out of the no shares<00:19:29.280> but<00:19:29.760> she's<00:19:29.940> not<00:19:30.120> going<00:19:30.240> to<00:19:30.360> do<00:19:30.480> that 00:19:30.650 --> 00:19:30.660 align:start position:0% shares but she's not going to do that 00:19:30.660 --> 00:19:33.470 align:start position:0% shares but she's not going to do that and<00:19:31.020> I<00:19:31.200> tell<00:19:31.440> you<00:19:31.559> why<00:19:31.799> what<00:19:32.460> she<00:19:32.700> does<00:19:32.880> is<00:19:33.120> she 00:19:33.470 --> 00:19:33.480 align:start position:0% and I tell you why what she does is she 00:19:33.480 --> 00:19:36.230 align:start position:0% and I tell you why what she does is she actually<00:19:33.919> keeps<00:19:34.919> uh<00:19:35.280> the<00:19:35.580> gestures<00:19:35.940> for 00:19:36.230 --> 00:19:36.240 align:start position:0% actually keeps uh the gestures for 00:19:36.240 --> 00:19:38.390 align:start position:0% actually keeps uh the gestures for herself<00:19:36.539> at<00:19:36.840> the<00:19:37.020> Notions<00:19:37.260> for<00:19:37.500> herself<00:19:37.799> and 00:19:38.390 --> 00:19:38.400 align:start position:0% herself at the Notions for herself and 00:19:38.400 --> 00:19:41.510 align:start position:0% herself at the Notions for herself and she's<00:19:38.580> gonna<00:19:38.820> give<00:19:39.299> the<00:19:40.140> yes<00:19:40.440> shares<00:19:40.919> to<00:19:41.280> David 00:19:41.510 --> 00:19:41.520 align:start position:0% she's gonna give the yes shares to David 00:19:41.520 --> 00:19:43.310 align:start position:0% she's gonna give the yes shares to David who's<00:19:42.000> running<00:19:42.240> the<00:19:42.480> orbits<00:19:42.840> from<00:19:42.960> validator 00:19:43.310 --> 00:19:43.320 align:start position:0% who's running the orbits from validator 00:19:43.320 --> 00:19:45.950 align:start position:0% who's running the orbits from validator so<00:19:43.980> she<00:19:44.160> goes<00:19:44.460> to<00:19:44.520> David<00:19:44.760> and<00:19:45.179> she's<00:19:45.299> like<00:19:45.539> hey 00:19:45.950 --> 00:19:45.960 align:start position:0% so she goes to David and she's like hey 00:19:45.960 --> 00:19:48.169 align:start position:0% so she goes to David and she's like hey I<00:19:46.679> know<00:19:46.799> that<00:19:47.039> you're<00:19:47.340> already<00:19:47.520> validating 00:19:48.169 --> 00:19:48.179 align:start position:0% I know that you're already validating 00:19:48.179 --> 00:19:50.510 align:start position:0% I know that you're already validating the<00:19:48.480> orbits<00:19:48.900> from<00:19:49.020> chain<00:19:49.260> and<00:19:49.980> David<00:19:50.160> doesn't 00:19:50.510 --> 00:19:50.520 align:start position:0% the orbits from chain and David doesn't 00:19:50.520 --> 00:19:52.490 align:start position:0% the orbits from chain and David doesn't care<00:19:50.760> about<00:19:51.059> this<00:19:51.360> withdrawal<00:19:51.900> at<00:19:52.140> all<00:19:52.260> she 00:19:52.490 --> 00:19:52.500 align:start position:0% care about this withdrawal at all she 00:19:52.500 --> 00:19:53.750 align:start position:0% care about this withdrawal at all she doesn't<00:19:52.620> even<00:19:52.799> he<00:19:53.100> doesn't<00:19:53.220> even<00:19:53.400> know<00:19:53.640> what 00:19:53.750 --> 00:19:53.760 align:start position:0% doesn't even he doesn't even know what 00:19:53.760 --> 00:19:56.210 align:start position:0% doesn't even he doesn't even know what that<00:19:53.940> is<00:19:54.120> so<00:19:54.539> Alice<00:19:54.900> is<00:19:55.080> like<00:19:55.260> I<00:19:55.559> am<00:19:55.799> giving<00:19:56.039> you 00:19:56.210 --> 00:19:56.220 align:start position:0% that is so Alice is like I am giving you 00:19:56.220 --> 00:19:58.010 align:start position:0% that is so Alice is like I am giving you these<00:19:56.580> hundred<00:19:56.820> no<00:19:57.059> shares 00:19:58.010 --> 00:19:58.020 align:start position:0% these hundred no shares 00:19:58.020 --> 00:20:00.230 align:start position:0% these hundred no shares is<00:19:58.620> a<00:19:58.799> bet<00:19:58.919> against<00:19:59.220> this<00:19:59.580> assertion<00:20:00.000> number 00:20:00.230 --> 00:20:00.240 align:start position:0% is a bet against this assertion number 00:20:00.240 --> 00:20:02.750 align:start position:0% is a bet against this assertion number 10<00:20:00.539> is<00:20:00.720> going<00:20:00.840> to<00:20:01.020> be<00:20:01.080> finalized<00:20:01.559> or<00:20:01.740> not<00:20:01.860> and 00:20:02.750 --> 00:20:02.760 align:start position:0% 10 is going to be finalized or not and 00:20:02.760 --> 00:20:05.450 align:start position:0% 10 is going to be finalized or not and I'm<00:20:03.240> giving<00:20:03.419> it<00:20:03.720> to<00:20:03.960> you<00:20:04.200> for<00:20:04.679> a<00:20:04.860> discount<00:20:05.039> or 00:20:05.450 --> 00:20:05.460 align:start position:0% I'm giving it to you for a discount or 00:20:05.460 --> 00:20:09.470 align:start position:0% I'm giving it to you for a discount or bonus<00:20:05.940> so<00:20:06.539> you<00:20:06.780> can<00:20:06.900> give<00:20:07.080> me<00:20:07.320> 99<00:20:08.039> cents<00:20:08.820> per 00:20:09.470 --> 00:20:09.480 align:start position:0% bonus so you can give me 99 cents per 00:20:09.480 --> 00:20:11.930 align:start position:0% bonus so you can give me 99 cents per shares<00:20:09.960> so<00:20:10.260> at<00:20:10.440> the<00:20:10.620> end<00:20:10.679> of<00:20:10.799> the<00:20:10.919> day<00:20:11.100> you<00:20:11.760> pay 00:20:11.930 --> 00:20:11.940 align:start position:0% shares so at the end of the day you pay 00:20:11.940 --> 00:20:14.690 align:start position:0% shares so at the end of the day you pay 99<00:20:12.200> ether<00:20:13.200> and<00:20:13.740> if<00:20:14.160> it's<00:20:14.340> going<00:20:14.520> to<00:20:14.640> be 00:20:14.690 --> 00:20:14.700 align:start position:0% 99 ether and if it's going to be 00:20:14.700 --> 00:20:16.970 align:start position:0% 99 ether and if it's going to be finalized<00:20:15.299> you<00:20:15.780> can<00:20:15.900> always<00:20:16.020> go<00:20:16.380> back<00:20:16.559> to<00:20:16.799> the 00:20:16.970 --> 00:20:16.980 align:start position:0% finalized you can always go back to the 00:20:16.980 --> 00:20:19.730 align:start position:0% finalized you can always go back to the market<00:20:17.100> and<00:20:17.460> you<00:20:17.580> can<00:20:17.640> redeem<00:20:18.000> it<00:20:18.179> 400<00:20:18.600> East<00:20:19.320> so 00:20:19.730 --> 00:20:19.740 align:start position:0% market and you can redeem it 400 East so 00:20:19.740 --> 00:20:21.650 align:start position:0% market and you can redeem it 400 East so Bob's<00:20:20.100> gonna<00:20:20.280> profit<00:20:20.760> right 00:20:21.650 --> 00:20:21.660 align:start position:0% Bob's gonna profit right 00:20:21.660 --> 00:20:24.169 align:start position:0% Bob's gonna profit right so<00:20:22.080> yeah<00:20:22.620> um<00:20:22.620> sorry<00:20:22.799> Dave<00:20:23.160> is<00:20:23.340> going<00:20:23.520> to<00:20:23.580> pray<00:20:23.760> I 00:20:24.169 --> 00:20:24.179 align:start position:0% so yeah um sorry Dave is going to pray I 00:20:24.179 --> 00:20:25.909 align:start position:0% so yeah um sorry Dave is going to pray I was<00:20:24.299> keeping<00:20:24.539> saying<00:20:24.900> Bob<00:20:25.140> right<00:20:25.440> sorry<00:20:25.799> about 00:20:25.909 --> 00:20:25.919 align:start position:0% was keeping saying Bob right sorry about 00:20:25.919 --> 00:20:29.150 align:start position:0% was keeping saying Bob right sorry about that<00:20:26.160> so<00:20:26.460> I'm<00:20:26.580> in<00:20:26.880> debut<00:20:27.299> yeah<00:20:27.720> so<00:20:28.500> so<00:20:28.679> Dave<00:20:28.980> is 00:20:29.150 --> 00:20:29.160 align:start position:0% that so I'm in debut yeah so so Dave is 00:20:29.160 --> 00:20:31.250 align:start position:0% that so I'm in debut yeah so so Dave is going<00:20:29.340> to<00:20:29.400> profit<00:20:29.760> right<00:20:30.000> so<00:20:30.360> he's<00:20:30.600> willing<00:20:31.140> to 00:20:31.250 --> 00:20:31.260 align:start position:0% going to profit right so he's willing to 00:20:31.260 --> 00:20:32.930 align:start position:0% going to profit right so he's willing to do<00:20:31.380> that<00:20:31.559> that's<00:20:31.740> fine<00:20:31.980> so<00:20:32.400> what<00:20:32.580> she<00:20:32.760> does 00:20:32.930 --> 00:20:32.940 align:start position:0% do that that's fine so what she does 00:20:32.940 --> 00:20:34.549 align:start position:0% do that that's fine so what she does with<00:20:33.179> the<00:20:33.360> no<00:20:33.480> shares<00:20:33.840> that<00:20:34.020> she<00:20:34.200> kept<00:20:34.440> for 00:20:34.549 --> 00:20:34.559 align:start position:0% with the no shares that she kept for 00:20:34.559 --> 00:20:37.270 align:start position:0% with the no shares that she kept for herself<00:20:34.980> now<00:20:35.640> she<00:20:35.880> can<00:20:36.059> actually<00:20:36.240> go<00:20:36.539> to<00:20:36.720> Cairo 00:20:37.270 --> 00:20:37.280 align:start position:0% herself now she can actually go to Cairo 00:20:37.280 --> 00:20:40.130 align:start position:0% herself now she can actually go to Cairo who<00:20:38.280> has<00:20:38.400> the<00:20:38.580> liquidity<00:20:39.059> but<00:20:39.660> she<00:20:39.960> doesn't 00:20:40.130 --> 00:20:40.140 align:start position:0% who has the liquidity but she doesn't 00:20:40.140 --> 00:20:42.470 align:start position:0% who has the liquidity but she doesn't know<00:20:40.740> what's<00:20:41.039> going<00:20:41.280> on<00:20:41.460> on<00:20:41.700> arbitrome<00:20:42.240> chain 00:20:42.470 --> 00:20:42.480 align:start position:0% know what's going on on arbitrome chain 00:20:42.480 --> 00:20:45.830 align:start position:0% know what's going on on arbitrome chain and<00:20:43.260> Alice<00:20:43.919> would<00:20:44.100> be<00:20:44.220> like<00:20:44.400> hi<00:20:44.880> I'm<00:20:45.419> willing 00:20:45.830 --> 00:20:45.840 align:start position:0% and Alice would be like hi I'm willing 00:20:45.840 --> 00:20:47.810 align:start position:0% and Alice would be like hi I'm willing to<00:20:45.960> trade<00:20:46.200> my<00:20:46.440> ticket<00:20:46.679> with<00:20:46.980> you<00:20:47.100> this<00:20:47.520> is<00:20:47.640> a 00:20:47.810 --> 00:20:47.820 align:start position:0% to trade my ticket with you this is a 00:20:47.820 --> 00:20:50.630 align:start position:0% to trade my ticket with you this is a ticket<00:20:47.940> it's<00:20:48.480> worth<00:20:48.840> 100<00:20:49.260> if<00:20:49.740> it<00:20:50.280> belongs<00:20:50.520> to 00:20:50.630 --> 00:20:50.640 align:start position:0% ticket it's worth 100 if it belongs to 00:20:50.640 --> 00:20:53.090 align:start position:0% ticket it's worth 100 if it belongs to me<00:20:50.760> now<00:20:50.940> but<00:20:51.120> I<00:20:51.299> can<00:20:51.419> sell<00:20:51.600> it<00:20:51.780> to<00:20:51.900> you<00:20:52.080> and<00:20:52.860> I 00:20:53.090 --> 00:20:53.100 align:start position:0% me now but I can sell it to you and I 00:20:53.100 --> 00:20:55.370 align:start position:0% me now but I can sell it to you and I know<00:20:53.280> that<00:20:53.640> you<00:20:53.880> don't<00:20:54.179> have<00:20:54.660> any<00:20:54.840> idea<00:20:55.200> about 00:20:55.370 --> 00:20:55.380 align:start position:0% know that you don't have any idea about 00:20:55.380 --> 00:20:57.350 align:start position:0% know that you don't have any idea about this<00:20:55.679> assertion<00:20:56.100> number<00:20:56.280> 10<00:20:56.580> you<00:20:57.120> don't<00:20:57.240> know 00:20:57.350 --> 00:20:57.360 align:start position:0% this assertion number 10 you don't know 00:20:57.360 --> 00:20:58.850 align:start position:0% this assertion number 10 you don't know if<00:20:57.480> it's<00:20:57.600> going<00:20:57.780> to<00:20:57.840> be<00:20:57.960> finalized<00:20:58.559> or<00:20:58.679> not 00:20:58.850 --> 00:20:58.860 align:start position:0% if it's going to be finalized or not 00:20:58.860 --> 00:21:00.950 align:start position:0% if it's going to be finalized or not that's<00:20:59.400> fine<00:20:59.700> you<00:21:00.120> don't<00:21:00.240> have<00:21:00.419> to<00:21:00.660> do 00:21:00.950 --> 00:21:00.960 align:start position:0% that's fine you don't have to do 00:21:00.960 --> 00:21:03.770 align:start position:0% that's fine you don't have to do anything<00:21:01.200> I<00:21:01.740> provide<00:21:02.100> insurance<00:21:02.460> so<00:21:03.419> what<00:21:03.600> I 00:21:03.770 --> 00:21:03.780 align:start position:0% anything I provide insurance so what I 00:21:03.780 --> 00:21:06.110 align:start position:0% anything I provide insurance so what I do<00:21:03.960> is<00:21:04.140> I'm<00:21:04.380> gonna<00:21:04.559> give<00:21:04.919> hundred<00:21:05.400> no<00:21:05.760> shares 00:21:06.110 --> 00:21:06.120 align:start position:0% do is I'm gonna give hundred no shares 00:21:06.120 --> 00:21:09.770 align:start position:0% do is I'm gonna give hundred no shares to<00:21:06.840> you<00:21:06.960> for<00:21:07.320> free<00:21:07.500> so<00:21:08.220> in<00:21:08.520> any<00:21:08.640> case<00:21:08.880> if<00:21:09.539> the 00:21:09.770 --> 00:21:09.780 align:start position:0% to you for free so in any case if the 00:21:09.780 --> 00:21:11.630 align:start position:0% to you for free so in any case if the assertion<00:21:10.260> is<00:21:10.380> going<00:21:10.559> to<00:21:10.679> be<00:21:10.799> finalized<00:21:11.400> and 00:21:11.630 --> 00:21:11.640 align:start position:0% assertion is going to be finalized and 00:21:11.640 --> 00:21:14.450 align:start position:0% assertion is going to be finalized and my<00:21:11.880> withdraw<00:21:12.480> is<00:21:12.600> actually<00:21:12.840> confirm<00:21:13.500> what<00:21:14.220> I 00:21:14.450 --> 00:21:14.460 align:start position:0% my withdraw is actually confirm what I 00:21:14.460 --> 00:21:16.549 align:start position:0% my withdraw is actually confirm what I do<00:21:14.580> is<00:21:14.880> what<00:21:15.299> you<00:21:15.480> can<00:21:15.600> do<00:21:15.720> is<00:21:15.900> you<00:21:16.140> can<00:21:16.260> go<00:21:16.440> to 00:21:16.549 --> 00:21:16.559 align:start position:0% do is what you can do is you can go to 00:21:16.559 --> 00:21:17.630 align:start position:0% do is what you can do is you can go to the<00:21:16.799> market 00:21:17.630 --> 00:21:17.640 align:start position:0% the market 00:21:17.640 --> 00:21:19.789 align:start position:0% the market and<00:21:18.179> you<00:21:18.419> can<00:21:18.480> redeem<00:21:18.840> your<00:21:19.140> you<00:21:19.380> can<00:21:19.559> go<00:21:19.679> to 00:21:19.789 --> 00:21:19.799 align:start position:0% and you can redeem your you can go to 00:21:19.799 --> 00:21:21.529 align:start position:0% and you can redeem your you can go to the<00:21:19.919> outbox<00:21:20.220> and<00:21:20.520> then<00:21:20.640> you<00:21:20.760> can<00:21:20.880> redeem<00:21:21.240> your 00:21:21.529 --> 00:21:21.539 align:start position:0% the outbox and then you can redeem your 00:21:21.539 --> 00:21:23.330 align:start position:0% the outbox and then you can redeem your ticket<00:21:21.960> for<00:21:22.260> 100<00:21:22.440> East 00:21:23.330 --> 00:21:23.340 align:start position:0% ticket for 100 East 00:21:23.340 --> 00:21:25.549 align:start position:0% ticket for 100 East and<00:21:23.940> if<00:21:24.120> no<00:21:24.299> if<00:21:24.600> there's<00:21:24.720> a<00:21:24.960> dispute<00:21:25.260> happen 00:21:25.549 --> 00:21:25.559 align:start position:0% and if no if there's a dispute happen 00:21:25.559 --> 00:21:28.250 align:start position:0% and if no if there's a dispute happen and<00:21:25.919> these<00:21:26.100> assertions<00:21:26.640> happens<00:21:27.179> to<00:21:27.539> be<00:21:27.720> like 00:21:28.250 --> 00:21:28.260 align:start position:0% and these assertions happens to be like 00:21:28.260 --> 00:21:30.770 align:start position:0% and these assertions happens to be like uh<00:21:29.039> not<00:21:29.280> finalized<00:21:29.880> what<00:21:30.059> you<00:21:30.240> can<00:21:30.360> do<00:21:30.480> is<00:21:30.600> you 00:21:30.770 --> 00:21:30.780 align:start position:0% uh not finalized what you can do is you 00:21:30.780 --> 00:21:32.810 align:start position:0% uh not finalized what you can do is you can<00:21:30.900> go<00:21:31.080> to<00:21:31.200> the<00:21:31.380> market<00:21:31.559> and<00:21:32.039> you<00:21:32.280> can<00:21:32.340> redeem 00:21:32.810 --> 00:21:32.820 align:start position:0% can go to the market and you can redeem 00:21:32.820 --> 00:21:35.390 align:start position:0% can go to the market and you can redeem your<00:21:33.120> no<00:21:33.299> shares<00:21:33.720> for<00:21:33.840> 100<00:21:34.020> each<00:21:34.440> so<00:21:34.860> in<00:21:35.220> any 00:21:35.390 --> 00:21:35.400 align:start position:0% your no shares for 100 each so in any 00:21:35.400 --> 00:21:38.990 align:start position:0% your no shares for 100 each so in any case<00:21:35.700> Alice<00:21:36.480> is<00:21:36.659> ensuring<00:21:37.400> Carol<00:21:38.400> so<00:21:38.640> Carol 00:21:38.990 --> 00:21:39.000 align:start position:0% case Alice is ensuring Carol so Carol 00:21:39.000 --> 00:21:40.610 align:start position:0% case Alice is ensuring Carol so Carol would<00:21:39.179> be<00:21:39.360> able<00:21:39.539> to<00:21:39.659> do<00:21:39.840> the<00:21:40.020> trade<00:21:40.260> with<00:21:40.440> her 00:21:40.610 --> 00:21:40.620 align:start position:0% would be able to do the trade with her 00:21:40.620 --> 00:21:42.890 align:start position:0% would be able to do the trade with her there's<00:21:40.860> no<00:21:41.039> risk<00:21:41.340> for<00:21:41.460> her 00:21:42.890 --> 00:21:42.900 align:start position:0% there's no risk for her 00:21:42.900 --> 00:21:44.330 align:start position:0% there's no risk for her so<00:21:43.320> this<00:21:43.500> is<00:21:43.620> great<00:21:43.740> this<00:21:44.039> is<00:21:44.100> the<00:21:44.220> best 00:21:44.330 --> 00:21:44.340 align:start position:0% so this is great this is the best 00:21:44.340 --> 00:21:46.430 align:start position:0% so this is great this is the best solution<00:21:44.700> that<00:21:45.000> I<00:21:45.179> I<00:21:45.299> guess<00:21:45.600> we<00:21:45.780> have<00:21:46.020> come<00:21:46.260> up 00:21:46.430 --> 00:21:46.440 align:start position:0% solution that I I guess we have come up 00:21:46.440 --> 00:21:48.590 align:start position:0% solution that I I guess we have come up with<00:21:46.559> and<00:21:47.100> for<00:21:47.280> the<00:21:47.400> implementation<00:21:47.940> this<00:21:48.419> is 00:21:48.590 --> 00:21:48.600 align:start position:0% with and for the implementation this is 00:21:48.600 --> 00:21:51.470 align:start position:0% with and for the implementation this is a<00:21:48.840> work<00:21:49.080> uh<00:21:49.559> under<00:21:49.740> progress<00:21:50.220> so<00:21:50.760> what<00:21:51.000> we<00:21:51.299> did 00:21:51.470 --> 00:21:51.480 align:start position:0% a work uh under progress so what we did 00:21:51.480 --> 00:21:53.810 align:start position:0% a work uh under progress so what we did so<00:21:51.659> far<00:21:51.840> is<00:21:52.140> we<00:21:52.380> modified<00:21:52.740> arbits<00:21:53.340> from<00:21:53.460> Nitro 00:21:53.810 --> 00:21:53.820 align:start position:0% so far is we modified arbits from Nitro 00:21:53.820 --> 00:21:55.970 align:start position:0% so far is we modified arbits from Nitro to<00:21:54.360> support<00:21:54.539> our<00:21:54.840> Solutions<00:21:55.200> and<00:21:55.559> we<00:21:55.679> provide 00:21:55.970 --> 00:21:55.980 align:start position:0% to support our Solutions and we provide 00:21:55.980 --> 00:21:58.310 align:start position:0% to support our Solutions and we provide measurements<00:21:56.640> we<00:21:57.360> fully<00:21:57.780> implemented 00:21:58.310 --> 00:21:58.320 align:start position:0% measurements we fully implemented 00:21:58.320 --> 00:22:00.350 align:start position:0% measurements we fully implemented solution<00:21:58.679> three<00:21:58.919> so<00:21:59.220> far<00:21:59.400> it's<00:21:59.880> a<00:22:00.059> proof<00:22:00.299> of 00:22:00.350 --> 00:22:00.360 align:start position:0% solution three so far it's a proof of 00:22:00.360 --> 00:22:02.810 align:start position:0% solution three so far it's a proof of concept<00:22:00.720> so<00:22:01.260> what<00:22:01.440> I<00:22:01.559> did<00:22:01.679> was<00:22:01.860> I<00:22:02.280> implemented 00:22:02.810 --> 00:22:02.820 align:start position:0% concept so what I did was I implemented 00:22:02.820 --> 00:22:05.090 align:start position:0% concept so what I did was I implemented an<00:22:03.000> L1<00:22:03.299> Market<00:22:03.600> it's<00:22:04.080> really<00:22:04.380> like<00:22:04.620> a<00:22:04.799> vending 00:22:05.090 --> 00:22:05.100 align:start position:0% an L1 Market it's really like a vending 00:22:05.100 --> 00:22:06.710 align:start position:0% an L1 Market it's really like a vending machine<00:22:05.220> as<00:22:05.460> I<00:22:05.640> said<00:22:05.760> so<00:22:06.360> there's<00:22:06.600> no 00:22:06.710 --> 00:22:06.720 align:start position:0% machine as I said so there's no 00:22:06.720 --> 00:22:09.110 align:start position:0% machine as I said so there's no bookkeeping<00:22:07.200> or<00:22:07.380> anything<00:22:07.620> and<00:22:08.520> we<00:22:08.760> modified 00:22:09.110 --> 00:22:09.120 align:start position:0% bookkeeping or anything and we modified 00:22:09.120 --> 00:22:11.510 align:start position:0% bookkeeping or anything and we modified the<00:22:09.360> outbox<00:22:09.659> so<00:22:09.900> that<00:22:10.080> it<00:22:10.260> would<00:22:10.440> support<00:22:11.159> our 00:22:11.510 --> 00:22:11.520 align:start position:0% the outbox so that it would support our 00:22:11.520 --> 00:22:12.409 align:start position:0% the outbox so that it would support our Market 00:22:12.409 --> 00:22:12.419 align:start position:0% Market 00:22:12.419 --> 00:22:14.330 align:start position:0% Market and<00:22:12.960> for<00:22:13.140> the<00:22:13.260> solution<00:22:13.559> for<00:22:13.799> the<00:22:13.980> prediction 00:22:14.330 --> 00:22:14.340 align:start position:0% and for the solution for the prediction 00:22:14.340 --> 00:22:17.090 align:start position:0% and for the solution for the prediction Market<00:22:14.580> one<00:22:14.940> it's<00:22:15.900> still<00:22:16.080> under<00:22:16.260> progress<00:22:16.740> but 00:22:17.090 --> 00:22:17.100 align:start position:0% Market one it's still under progress but 00:22:17.100 --> 00:22:19.010 align:start position:0% Market one it's still under progress but we<00:22:17.340> modified<00:22:17.640> the<00:22:17.880> roll<00:22:18.059> up<00:22:18.240> and<00:22:18.419> outbox<00:22:18.720> more 00:22:19.010 --> 00:22:19.020 align:start position:0% we modified the roll up and outbox more 00:22:19.020 --> 00:22:21.649 align:start position:0% we modified the roll up and outbox more contracts<00:22:19.500> uh<00:22:20.400> so<00:22:20.700> uh<00:22:21.120> there<00:22:21.419> could<00:22:21.539> be 00:22:21.649 --> 00:22:21.659 align:start position:0% contracts uh so uh there could be 00:22:21.659 --> 00:22:23.630 align:start position:0% contracts uh so uh there could be prediction<00:22:22.020> Market<00:22:22.260> friendly<00:22:22.799> okay<00:22:23.159> so<00:22:23.460> I'm 00:22:23.630 --> 00:22:23.640 align:start position:0% prediction Market friendly okay so I'm 00:22:23.640 --> 00:22:25.610 align:start position:0% prediction Market friendly okay so I'm gonna<00:22:23.820> walk<00:22:24.120> you<00:22:24.360> through<00:22:24.659> the<00:22:25.020> the<00:22:25.200> protocol 00:22:25.610 --> 00:22:25.620 align:start position:0% gonna walk you through the the protocol 00:22:25.620 --> 00:22:27.470 align:start position:0% gonna walk you through the the protocol of<00:22:25.980> solution<00:22:26.280> three<00:22:26.520> how<00:22:26.760> it<00:22:26.880> works<00:22:27.120> and<00:22:27.299> how 00:22:27.470 --> 00:22:27.480 align:start position:0% of solution three how it works and how 00:22:27.480 --> 00:22:28.970 align:start position:0% of solution three how it works and how what<00:22:27.720> what<00:22:27.960> are<00:22:28.200> the<00:22:28.320> functions<00:22:28.620> that<00:22:28.860> we 00:22:28.970 --> 00:22:28.980 align:start position:0% what what are the functions that we 00:22:28.980 --> 00:22:30.830 align:start position:0% what what are the functions that we added<00:22:29.280> to<00:22:29.460> the<00:22:29.700> product<00:22:30.059> the<00:22:30.419> Arbitron 00:22:30.830 --> 00:22:30.840 align:start position:0% added to the product the Arbitron 00:22:30.840 --> 00:22:33.350 align:start position:0% added to the product the Arbitron protocols<00:22:31.380> so<00:22:31.620> let's<00:22:31.860> say<00:22:31.980> Alice<00:22:32.400> wants<00:22:32.820> to<00:22:32.940> do 00:22:33.350 --> 00:22:33.360 align:start position:0% protocols so let's say Alice wants to do 00:22:33.360 --> 00:22:35.750 align:start position:0% protocols so let's say Alice wants to do a<00:22:33.539> withdraw<00:22:33.960> so<00:22:34.260> she<00:22:34.500> puts<00:22:34.799> her<00:22:34.919> a<00:22:35.159> withdrawal 00:22:35.750 --> 00:22:35.760 align:start position:0% a withdraw so she puts her a withdrawal 00:22:35.760 --> 00:22:37.970 align:start position:0% a withdraw so she puts her a withdrawal transaction<00:22:36.059> inside<00:22:36.480> the<00:22:36.720> Inbox<00:22:37.080> and<00:22:37.860> then 00:22:37.970 --> 00:22:37.980 align:start position:0% transaction inside the Inbox and then 00:22:37.980 --> 00:22:39.590 align:start position:0% transaction inside the Inbox and then what<00:22:38.280> she<00:22:38.460> does<00:22:38.700> this<00:22:38.880> is<00:22:39.000> the<00:22:39.120> function<00:22:39.360> that 00:22:39.590 --> 00:22:39.600 align:start position:0% what she does this is the function that 00:22:39.600 --> 00:22:41.750 align:start position:0% what she does this is the function that we<00:22:39.720> added<00:22:39.960> to<00:22:40.140> the<00:22:40.200> outbox<00:22:40.559> she<00:22:41.340> wants<00:22:41.700> to 00:22:41.750 --> 00:22:41.760 align:start position:0% we added to the outbox she wants to 00:22:41.760 --> 00:22:43.610 align:start position:0% we added to the outbox she wants to participate<00:22:42.240> inside<00:22:42.480> the<00:22:42.780> market<00:22:42.960> so<00:22:43.380> Market 00:22:43.610 --> 00:22:43.620 align:start position:0% participate inside the market so Market 00:22:43.620 --> 00:22:46.610 align:start position:0% participate inside the market so Market needs<00:22:44.100> to<00:22:44.220> know<00:22:44.520> that<00:22:45.179> she<00:22:45.419> actually<00:22:45.780> locked 00:22:46.610 --> 00:22:46.620 align:start position:0% needs to know that she actually locked 00:22:46.620 --> 00:22:49.250 align:start position:0% needs to know that she actually locked up<00:22:46.919> her<00:22:47.400> her<00:22:47.700> ether<00:22:48.059> inside<00:22:48.299> the<00:22:48.539> market<00:22:48.720> so 00:22:49.250 --> 00:22:49.260 align:start position:0% up her her ether inside the market so 00:22:49.260 --> 00:22:51.230 align:start position:0% up her her ether inside the market so what<00:22:49.380> Alice<00:22:49.740> needs<00:22:50.039> to<00:22:50.100> do<00:22:50.280> first<00:22:50.460> is<00:22:50.820> she<00:22:51.059> has 00:22:51.230 --> 00:22:51.240 align:start position:0% what Alice needs to do first is she has 00:22:51.240 --> 00:22:53.690 align:start position:0% what Alice needs to do first is she has to<00:22:51.360> go<00:22:51.539> to<00:22:51.659> the<00:22:51.780> outbox<00:22:52.200> and<00:22:53.039> cause<00:22:53.280> the 00:22:53.690 --> 00:22:53.700 align:start position:0% to go to the outbox and cause the 00:22:53.700 --> 00:22:55.789 align:start position:0% to go to the outbox and cause the transfer<00:22:54.059> spender<00:22:54.419> function<00:22:54.840> with<00:22:55.559> what 00:22:55.789 --> 00:22:55.799 align:start position:0% transfer spender function with what 00:22:55.799 --> 00:22:59.029 align:start position:0% transfer spender function with what basically<00:22:56.400> it<00:22:56.580> does<00:22:56.760> is<00:22:57.059> it<00:22:57.480> it<00:22:57.720> transfer<00:22:58.559> her 00:22:59.029 --> 00:22:59.039 align:start position:0% basically it does is it it transfer her 00:22:59.039 --> 00:23:02.570 align:start position:0% basically it does is it it transfer her exit<00:22:59.820> her<00:23:00.600> withdrawal<00:23:01.320> to<00:23:01.799> the<00:23:02.100> market<00:23:02.220> smart 00:23:02.570 --> 00:23:02.580 align:start position:0% exit her withdrawal to the market smart 00:23:02.580 --> 00:23:03.950 align:start position:0% exit her withdrawal to the market smart contract<00:23:03.000> so<00:23:03.419> it's<00:23:03.539> like<00:23:03.720> it's 00:23:03.950 --> 00:23:03.960 align:start position:0% contract so it's like it's 00:23:03.960 --> 00:23:06.590 align:start position:0% contract so it's like it's collateralizing<00:23:04.860> her<00:23:05.039> exit 00:23:06.590 --> 00:23:06.600 align:start position:0% collateralizing her exit 00:23:06.600 --> 00:23:08.870 align:start position:0% collateralizing her exit and<00:23:07.140> then<00:23:07.320> once<00:23:07.559> that's<00:23:07.740> done<00:23:08.039> she<00:23:08.520> can<00:23:08.700> go<00:23:08.820> to 00:23:08.870 --> 00:23:08.880 align:start position:0% and then once that's done she can go to 00:23:08.880 --> 00:23:10.909 align:start position:0% and then once that's done she can go to the<00:23:09.059> market<00:23:09.240> and<00:23:09.840> she<00:23:09.960> can<00:23:10.140> actually<00:23:10.260> open<00:23:10.679> a 00:23:10.909 --> 00:23:10.919 align:start position:0% the market and she can actually open a 00:23:10.919 --> 00:23:13.190 align:start position:0% the market and she can actually open a market<00:23:11.100> on<00:23:11.400> her<00:23:11.520> exit<00:23:11.880> and<00:23:12.600> Market<00:23:12.840> would 00:23:13.190 --> 00:23:13.200 align:start position:0% market on her exit and Market would 00:23:13.200 --> 00:23:16.070 align:start position:0% market on her exit and Market would check<00:23:13.440> if<00:23:13.799> Alice<00:23:14.220> has<00:23:14.460> really<00:23:14.720> deposited<00:23:15.720> her 00:23:16.070 --> 00:23:16.080 align:start position:0% check if Alice has really deposited her 00:23:16.080 --> 00:23:18.529 align:start position:0% check if Alice has really deposited her exit<00:23:16.500> inside<00:23:16.679> the<00:23:16.980> market<00:23:17.100> or<00:23:17.400> not<00:23:17.520> and<00:23:18.059> if<00:23:18.299> yes 00:23:18.529 --> 00:23:18.539 align:start position:0% exit inside the market or not and if yes 00:23:18.539 --> 00:23:21.110 align:start position:0% exit inside the market or not and if yes that's<00:23:19.140> fine<00:23:19.320> she<00:23:19.620> can<00:23:19.799> open<00:23:19.919> a<00:23:20.159> market<00:23:20.340> then 00:23:21.110 --> 00:23:21.120 align:start position:0% that's fine she can open a market then 00:23:21.120 --> 00:23:22.970 align:start position:0% that's fine she can open a market then the<00:23:21.299> market<00:23:21.419> is<00:23:21.659> open<00:23:21.840> for<00:23:22.140> some<00:23:22.320> time<00:23:22.559> until 00:23:22.970 --> 00:23:22.980 align:start position:0% the market is open for some time until 00:23:22.980 --> 00:23:25.549 align:start position:0% the market is open for some time until there's<00:23:23.280> a<00:23:23.460> trade<00:23:23.760> Bob<00:23:24.419> comes<00:23:24.840> along<00:23:24.960> he's<00:23:25.320> a 00:23:25.549 --> 00:23:25.559 align:start position:0% there's a trade Bob comes along he's a 00:23:25.559 --> 00:23:26.930 align:start position:0% there's a trade Bob comes along he's a Trader<00:23:25.919> he<00:23:25.980> is<00:23:26.159> willing<00:23:26.400> to<00:23:26.520> trade<00:23:26.640> it<00:23:26.820> with 00:23:26.930 --> 00:23:26.940 align:start position:0% Trader he is willing to trade it with 00:23:26.940 --> 00:23:29.630 align:start position:0% Trader he is willing to trade it with Alice<00:23:27.299> what<00:23:27.720> he<00:23:27.960> does<00:23:28.140> is<00:23:28.320> uh<00:23:28.919> he<00:23:29.159> submits<00:23:29.580> a 00:23:29.630 --> 00:23:29.640 align:start position:0% Alice what he does is uh he submits a 00:23:29.640 --> 00:23:32.390 align:start position:0% Alice what he does is uh he submits a bid<00:23:29.880> that<00:23:30.480> actually<00:23:30.780> is<00:23:31.559> greater<00:23:31.919> than<00:23:31.980> what 00:23:32.390 --> 00:23:32.400 align:start position:0% bid that actually is greater than what 00:23:32.400 --> 00:23:35.810 align:start position:0% bid that actually is greater than what is<00:23:32.640> Alice<00:23:33.059> as<00:23:33.299> Alice<00:23:33.840> is<00:23:34.020> asking<00:23:34.440> for<00:23:34.620> and<00:23:35.400> that 00:23:35.810 --> 00:23:35.820 align:start position:0% is Alice as Alice is asking for and that 00:23:35.820 --> 00:23:37.789 align:start position:0% is Alice as Alice is asking for and that that's<00:23:36.120> when<00:23:36.419> the<00:23:36.600> trade<00:23:36.840> occurs<00:23:37.260> so<00:23:37.620> the 00:23:37.789 --> 00:23:37.799 align:start position:0% that's when the trade occurs so the 00:23:37.799 --> 00:23:39.529 align:start position:0% that's when the trade occurs so the trade<00:23:38.159> happens<00:23:38.340> everything<00:23:38.820> gets<00:23:39.240> settled 00:23:39.529 --> 00:23:39.539 align:start position:0% trade happens everything gets settled 00:23:39.539 --> 00:23:42.350 align:start position:0% trade happens everything gets settled down<00:23:39.659> but<00:23:40.260> Market<00:23:40.500> does<00:23:40.919> it<00:23:41.340> first<00:23:41.760> gonna 00:23:42.350 --> 00:23:42.360 align:start position:0% down but Market does it first gonna 00:23:42.360 --> 00:23:44.630 align:start position:0% down but Market does it first gonna first<00:23:42.900> is<00:23:43.140> gonna<00:23:43.440> send<00:23:43.740> the<00:23:43.919> East<00:23:44.220> back<00:23:44.460> to 00:23:44.630 --> 00:23:44.640 align:start position:0% first is gonna send the East back to 00:23:44.640 --> 00:23:46.430 align:start position:0% first is gonna send the East back to Alice<00:23:45.000> so<00:23:45.120> Alice<00:23:45.419> is<00:23:45.600> happy<00:23:45.780> she<00:23:46.140> got<00:23:46.260> her 00:23:46.430 --> 00:23:46.440 align:start position:0% Alice so Alice is happy she got her 00:23:46.440 --> 00:23:48.770 align:start position:0% Alice so Alice is happy she got her ether<00:23:46.740> and<00:23:47.460> then<00:23:47.580> what<00:23:47.820> it<00:23:48.000> does<00:23:48.179> is<00:23:48.419> because 00:23:48.770 --> 00:23:48.780 align:start position:0% ether and then what it does is because 00:23:48.780 --> 00:23:52.010 align:start position:0% ether and then what it does is because it's<00:23:49.320> owning<00:23:49.860> the<00:23:50.520> exit<00:23:50.880> now<00:23:51.059> what<00:23:51.600> it<00:23:51.720> can<00:23:51.900> do 00:23:52.010 --> 00:23:52.020 align:start position:0% it's owning the exit now what it can do 00:23:52.020 --> 00:23:54.049 align:start position:0% it's owning the exit now what it can do is<00:23:52.260> it<00:23:52.620> it<00:23:52.740> can<00:23:53.039> actually<00:23:53.159> go<00:23:53.520> inside<00:23:53.820> the 00:23:54.049 --> 00:23:54.059 align:start position:0% is it it can actually go inside the 00:23:54.059 --> 00:23:57.230 align:start position:0% is it it can actually go inside the outbox<00:23:54.419> and<00:23:54.900> change<00:23:55.200> the<00:23:55.679> owner<00:23:56.460> of<00:23:56.760> this<00:23:56.880> exit 00:23:57.230 --> 00:23:57.240 align:start position:0% outbox and change the owner of this exit 00:23:57.240 --> 00:23:59.510 align:start position:0% outbox and change the owner of this exit so<00:23:57.720> it<00:23:57.840> reached<00:23:58.260> inside<00:23:58.380> the<00:23:58.679> outbox<00:23:59.039> and<00:23:59.400> it 00:23:59.510 --> 00:23:59.520 align:start position:0% so it reached inside the outbox and it 00:23:59.520 --> 00:24:01.610 align:start position:0% so it reached inside the outbox and it changes<00:23:59.820> the<00:23:59.940> owner<00:24:00.240> to<00:24:00.360> the<00:24:00.659> ball 00:24:01.610 --> 00:24:01.620 align:start position:0% changes the owner to the ball 00:24:01.620 --> 00:24:04.370 align:start position:0% changes the owner to the ball so<00:24:02.100> now<00:24:02.220> Bob<00:24:02.460> owns<00:24:02.880> the<00:24:03.000> exit<00:24:03.299> we<00:24:03.900> wait<00:24:04.200> for 00:24:04.370 --> 00:24:04.380 align:start position:0% so now Bob owns the exit we wait for 00:24:04.380 --> 00:24:06.590 align:start position:0% so now Bob owns the exit we wait for seven<00:24:04.559> days<00:24:04.860> and<00:24:05.580> then<00:24:05.700> what<00:24:05.880> happens<00:24:06.059> is<00:24:06.360> he 00:24:06.590 --> 00:24:06.600 align:start position:0% seven days and then what happens is he 00:24:06.600 --> 00:24:08.390 align:start position:0% seven days and then what happens is he can<00:24:06.840> now<00:24:07.020> go<00:24:07.200> to<00:24:07.320> the<00:24:07.500> outbox<00:24:07.740> smart<00:24:08.039> contract 00:24:08.390 --> 00:24:08.400 align:start position:0% can now go to the outbox smart contract 00:24:08.400 --> 00:24:10.789 align:start position:0% can now go to the outbox smart contract execute<00:24:08.940> his<00:24:09.120> withdrawal<00:24:09.600> transaction<00:24:09.960> and 00:24:10.789 --> 00:24:10.799 align:start position:0% execute his withdrawal transaction and 00:24:10.799 --> 00:24:13.370 align:start position:0% execute his withdrawal transaction and then<00:24:10.919> because<00:24:11.280> he's<00:24:11.640> the<00:24:11.820> owner<00:24:12.140> the<00:24:13.140> bridge 00:24:13.370 --> 00:24:13.380 align:start position:0% then because he's the owner the bridge 00:24:13.380 --> 00:24:16.669 align:start position:0% then because he's the owner the bridge would<00:24:13.740> send<00:24:13.919> 100<00:24:14.220> East<00:24:14.700> back<00:24:15.120> to<00:24:15.419> him<00:24:15.600> so<00:24:16.380> easy 00:24:16.669 --> 00:24:16.679 align:start position:0% would send 100 East back to him so easy 00:24:16.679 --> 00:24:18.830 align:start position:0% would send 100 East back to him so easy peasy<00:24:17.400> everyone's<00:24:18.059> happy 00:24:18.830 --> 00:24:18.840 align:start position:0% peasy everyone's happy 00:24:18.840 --> 00:24:21.470 align:start position:0% peasy everyone's happy and<00:24:19.320> then<00:24:19.440> we<00:24:19.919> run<00:24:20.100> some<00:24:20.340> measurements<00:24:20.880> too<00:24:21.120> to 00:24:21.470 --> 00:24:21.480 align:start position:0% and then we run some measurements too to 00:24:21.480 --> 00:24:24.049 align:start position:0% and then we run some measurements too to find<00:24:21.720> out<00:24:21.960> how<00:24:22.440> much<00:24:22.559> at<00:24:22.919> one<00:24:23.159> gas<00:24:23.460> it<00:24:23.940> would 00:24:24.049 --> 00:24:24.059 align:start position:0% find out how much at one gas it would 00:24:24.059 --> 00:24:26.570 align:start position:0% find out how much at one gas it would cost<00:24:24.240> us<00:24:24.480> to<00:24:24.780> run<00:24:24.900> this<00:24:25.200> function<00:24:25.500> so<00:24:26.220> it<00:24:26.340> turns 00:24:26.570 --> 00:24:26.580 align:start position:0% cost us to run this function so it turns 00:24:26.580 --> 00:24:28.730 align:start position:0% cost us to run this function so it turns out<00:24:26.700> it's<00:24:26.880> really<00:24:27.120> cheap<00:24:27.360> so<00:24:28.080> for 00:24:28.730 --> 00:24:28.740 align:start position:0% out it's really cheap so for 00:24:28.740 --> 00:24:30.529 align:start position:0% out it's really cheap so for transferring<00:24:29.280> the<00:24:29.580> spender<00:24:29.940> inside<00:24:30.240> the 00:24:30.529 --> 00:24:30.539 align:start position:0% transferring the spender inside the 00:24:30.539 --> 00:24:33.770 align:start position:0% transferring the spender inside the output<00:24:30.900> smart<00:24:31.080> contract<00:24:31.440> it's<00:24:31.799> around<00:24:32.100> 80<00:24:32.780> uh 00:24:33.770 --> 00:24:33.780 align:start position:0% output smart contract it's around 80 uh 00:24:33.780 --> 00:24:36.590 align:start position:0% output smart contract it's around 80 uh six<00:24:34.320> K<00:24:34.799> and<00:24:35.220> it's<00:24:35.760> really<00:24:35.940> like<00:24:36.240> the<00:24:36.419> most 00:24:36.590 --> 00:24:36.600 align:start position:0% six K and it's really like the most 00:24:36.600 --> 00:24:39.289 align:start position:0% six K and it's really like the most expensive<00:24:37.080> one<00:24:37.320> because<00:24:37.620> it's<00:24:38.460> the<00:24:38.700> like<00:24:39.059> the 00:24:39.289 --> 00:24:39.299 align:start position:0% expensive one because it's the like the 00:24:39.299 --> 00:24:41.690 align:start position:0% expensive one because it's the like the it's<00:24:39.659> the<00:24:39.900> first<00:24:40.140> transferring<00:24:40.980> of<00:24:41.220> spender 00:24:41.690 --> 00:24:41.700 align:start position:0% it's the first transferring of spender 00:24:41.700 --> 00:24:43.490 align:start position:0% it's the first transferring of spender so<00:24:42.419> it's<00:24:42.600> actually<00:24:42.780> you're<00:24:43.020> paying<00:24:43.380> for 00:24:43.490 --> 00:24:43.500 align:start position:0% so it's actually you're paying for 00:24:43.500 --> 00:24:46.310 align:start position:0% so it's actually you're paying for creation<00:24:43.919> of<00:24:44.100> a<00:24:44.340> mapping<00:24:44.700> so<00:24:45.600> the<00:24:45.960> because 00:24:46.310 --> 00:24:46.320 align:start position:0% creation of a mapping so the because 00:24:46.320 --> 00:24:47.810 align:start position:0% creation of a mapping so the because there's<00:24:46.620> a<00:24:46.799> mapping<00:24:47.100> that<00:24:47.280> keeps<00:24:47.520> track<00:24:47.640> of 00:24:47.810 --> 00:24:47.820 align:start position:0% there's a mapping that keeps track of 00:24:47.820 --> 00:24:50.390 align:start position:0% there's a mapping that keeps track of all<00:24:48.059> the<00:24:48.179> owners<00:24:48.419> of<00:24:48.659> an<00:24:48.780> exit<00:24:49.140> so<00:24:49.860> this<00:24:50.280> is 00:24:50.390 --> 00:24:50.400 align:start position:0% all the owners of an exit so this is 00:24:50.400 --> 00:24:51.710 align:start position:0% all the owners of an exit so this is really<00:24:50.580> expensive<00:24:51.000> the<00:24:51.120> first<00:24:51.299> one<00:24:51.419> is<00:24:51.539> really 00:24:51.710 --> 00:24:51.720 align:start position:0% really expensive the first one is really 00:24:51.720 --> 00:24:53.450 align:start position:0% really expensive the first one is really expensive<00:24:52.140> but<00:24:52.320> the<00:24:52.500> LA<00:24:52.679> the<00:24:52.860> second<00:24:53.039> one<00:24:53.280> and 00:24:53.450 --> 00:24:53.460 align:start position:0% expensive but the LA the second one and 00:24:53.460 --> 00:24:55.370 align:start position:0% expensive but the LA the second one and the<00:24:53.580> third<00:24:53.700> one<00:24:53.880> I<00:24:54.419> guess<00:24:54.539> they<00:24:55.020> were<00:24:55.140> around 00:24:55.370 --> 00:24:55.380 align:start position:0% the third one I guess they were around 00:24:55.380 --> 00:24:59.570 align:start position:0% the third one I guess they were around like<00:24:55.620> 40K<00:24:56.280> away<00:24:57.120> which<00:24:57.600> was<00:24:57.840> really<00:24:58.140> great 00:24:59.570 --> 00:24:59.580 align:start position:0% like 40K away which was really great 00:24:59.580 --> 00:25:02.210 align:start position:0% like 40K away which was really great and<00:25:00.120> for<00:25:00.240> opening<00:25:00.659> the<00:25:00.780> market<00:25:00.960> we<00:25:01.740> had<00:25:01.919> to<00:25:02.100> pay 00:25:02.210 --> 00:25:02.220 align:start position:0% and for opening the market we had to pay 00:25:02.220 --> 00:25:05.270 align:start position:0% and for opening the market we had to pay around<00:25:02.580> 300K 00:25:05.270 --> 00:25:05.280 align:start position:0% around 300K 00:25:05.280 --> 00:25:09.169 align:start position:0% around 300K and<00:25:06.120> for<00:25:06.900> for<00:25:07.200> submitting<00:25:07.799> the<00:25:07.860> bid<00:25:08.159> uh<00:25:08.820> I<00:25:09.059> had 00:25:09.169 --> 00:25:09.179 align:start position:0% and for for submitting the bid uh I had 00:25:09.179 --> 00:25:12.409 align:start position:0% and for for submitting the bid uh I had to<00:25:09.360> pay<00:25:09.480> around<00:25:09.720> 100K<00:25:10.500> and<00:25:11.460> then<00:25:11.760> for 00:25:12.409 --> 00:25:12.419 align:start position:0% to pay around 100K and then for 00:25:12.419 --> 00:25:16.010 align:start position:0% to pay around 100K and then for executing<00:25:12.900> the<00:25:13.080> transaction<00:25:13.500> it<00:25:14.100> cost<00:25:14.280> 90k 00:25:16.010 --> 00:25:16.020 align:start position:0% executing the transaction it cost 90k 00:25:16.020 --> 00:25:19.549 align:start position:0% executing the transaction it cost 90k and<00:25:16.559> that<00:25:16.799> sums<00:25:17.280> up<00:25:17.400> the<00:25:17.700> talk<00:25:17.880> uh<00:25:18.840> I<00:25:19.080> I<00:25:19.080> hope 00:25:19.549 --> 00:25:19.559 align:start position:0% and that sums up the talk uh I I hope 00:25:19.559 --> 00:25:21.350 align:start position:0% and that sums up the talk uh I I hope you<00:25:19.679> enjoyed<00:25:19.980> it<00:25:20.159> it's<00:25:20.520> really<00:25:20.760> a<00:25:20.940> work<00:25:21.120> under 00:25:21.350 --> 00:25:21.360 align:start position:0% you enjoyed it it's really a work under 00:25:21.360 --> 00:25:24.470 align:start position:0% you enjoyed it it's really a work under progress<00:25:21.900> so<00:25:22.440> uh<00:25:23.039> the<00:25:23.700> repo<00:25:24.059> is<00:25:24.179> not<00:25:24.360> really 00:25:24.470 --> 00:25:24.480 align:start position:0% progress so uh the repo is not really 00:25:24.480 --> 00:25:27.529 align:start position:0% progress so uh the repo is not really public<00:25:24.840> yet<00:25:25.200> but<00:25:25.860> I<00:25:26.279> urge<00:25:26.880> you<00:25:26.940> to<00:25:27.179> reach<00:25:27.419> out 00:25:27.529 --> 00:25:27.539 align:start position:0% public yet but I urge you to reach out 00:25:27.539 --> 00:25:29.630 align:start position:0% public yet but I urge you to reach out to<00:25:27.779> me<00:25:27.900> on<00:25:28.140> Twitter<00:25:28.320> if<00:25:29.039> you<00:25:29.159> need<00:25:29.279> to<00:25:29.400> learn 00:25:29.630 --> 00:25:29.640 align:start position:0% to me on Twitter if you need to learn 00:25:29.640 --> 00:25:31.610 align:start position:0% to me on Twitter if you need to learn more<00:25:29.940> we're<00:25:30.539> gonna<00:25:30.720> submit<00:25:31.080> it<00:25:31.200> somewhere 00:25:31.610 --> 00:25:31.620 align:start position:0% more we're gonna submit it somewhere 00:25:31.620 --> 00:25:35.360 align:start position:0% more we're gonna submit it somewhere soon<00:25:31.799> and<00:25:32.340> the<00:25:32.460> repo<00:25:32.820> will<00:25:32.940> be<00:25:33.120> public