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.910 align:start position:0% [Music] 00:00:12.910 --> 00:00:12.920 align:start position:0% 00:00:12.920 --> 00:00:16.609 align:start position:0% welcome<00:00:13.920> to<00:00:14.340> my<00:00:15.179> workshop 00:00:16.609 --> 00:00:16.619 align:start position:0% welcome to my workshop 00:00:16.619 --> 00:00:18.470 align:start position:0% welcome to my workshop um today<00:00:16.920> we<00:00:17.279> will<00:00:17.460> be<00:00:17.640> building<00:00:17.940> an<00:00:18.240> nft 00:00:18.470 --> 00:00:18.480 align:start position:0% um today we will be building an nft 00:00:18.480 --> 00:00:22.130 align:start position:0% um today we will be building an nft bridge<00:00:18.840> between<00:00:19.760> ethereum<00:00:20.760> and<00:00:21.000> arbitrum<00:00:21.600> if 00:00:22.130 --> 00:00:22.140 align:start position:0% bridge between ethereum and arbitrum if 00:00:22.140 --> 00:00:23.689 align:start position:0% bridge between ethereum and arbitrum if you<00:00:22.260> would<00:00:22.380> like<00:00:22.500> to<00:00:22.680> code<00:00:22.859> along<00:00:23.160> you<00:00:23.580> can 00:00:23.689 --> 00:00:23.699 align:start position:0% you would like to code along you can 00:00:23.699 --> 00:00:25.790 align:start position:0% you would like to code along you can clone<00:00:23.939> this<00:00:24.180> repo<00:00:24.600> here<00:00:24.840> I<00:00:25.380> don't<00:00:25.500> know<00:00:25.560> if<00:00:25.619> the 00:00:25.790 --> 00:00:25.800 align:start position:0% clone this repo here I don't know if the 00:00:25.800 --> 00:00:28.070 align:start position:0% clone this repo here I don't know if the URL<00:00:26.100> is<00:00:26.279> visible<00:00:26.580> enough<00:00:26.939> but<00:00:27.480> you<00:00:27.660> can<00:00:27.720> get<00:00:27.900> it 00:00:28.070 --> 00:00:28.080 align:start position:0% URL is visible enough but you can get it 00:00:28.080 --> 00:00:30.470 align:start position:0% URL is visible enough but you can get it from<00:00:28.380> the<00:00:28.740> off-chain<00:00:29.099> labs<00:00:29.400> GitHub<00:00:29.699> it's<00:00:30.240> the 00:00:30.470 --> 00:00:30.480 align:start position:0% from the off-chain labs GitHub it's the 00:00:30.480 --> 00:00:33.049 align:start position:0% from the off-chain labs GitHub it's the most<00:00:30.660> recently<00:00:30.960> updated<00:00:31.260> thing<00:00:31.820> or<00:00:32.820> you<00:00:32.940> can 00:00:33.049 --> 00:00:33.059 align:start position:0% most recently updated thing or you can 00:00:33.059 --> 00:00:35.209 align:start position:0% most recently updated thing or you can grab<00:00:33.239> it<00:00:33.360> from<00:00:33.480> my<00:00:33.660> Twitter<00:00:33.780> at<00:00:34.079> these<00:00:34.320> act<00:00:34.440> 23. 00:00:35.209 --> 00:00:35.219 align:start position:0% grab it from my Twitter at these act 23. 00:00:35.219 --> 00:00:37.190 align:start position:0% grab it from my Twitter at these act 23. it's<00:00:35.340> the<00:00:35.460> last<00:00:35.579> thing<00:00:35.700> I<00:00:35.820> tweeted 00:00:37.190 --> 00:00:37.200 align:start position:0% it's the last thing I tweeted 00:00:37.200 --> 00:00:38.270 align:start position:0% it's the last thing I tweeted um you're<00:00:37.380> welcome<00:00:37.559> to<00:00:37.680> code<00:00:37.800> along<00:00:38.100> you're 00:00:38.270 --> 00:00:38.280 align:start position:0% um you're welcome to code along you're 00:00:38.280 --> 00:00:40.250 align:start position:0% um you're welcome to code along you're also<00:00:38.520> welcome<00:00:38.640> to<00:00:38.880> to<00:00:39.239> listen 00:00:40.250 --> 00:00:40.260 align:start position:0% also welcome to to listen 00:00:40.260 --> 00:00:42.830 align:start position:0% also welcome to to listen um<00:00:40.460> uh<00:00:41.460> both<00:00:41.640> work<00:00:41.820> most<00:00:42.180> of<00:00:42.360> the<00:00:42.420> coding<00:00:42.719> will 00:00:42.830 --> 00:00:42.840 align:start position:0% um uh both work most of the coding will 00:00:42.840 --> 00:00:44.510 align:start position:0% um uh both work most of the coding will be<00:00:42.960> so<00:00:43.140> we<00:00:43.260> kind<00:00:43.379> of<00:00:43.500> have<00:00:43.559> the<00:00:43.800> skeleton<00:00:44.280> of 00:00:44.510 --> 00:00:44.520 align:start position:0% be so we kind of have the skeleton of 00:00:44.520 --> 00:00:45.650 align:start position:0% be so we kind of have the skeleton of the<00:00:44.579> smart<00:00:44.700> contracts<00:00:45.120> and<00:00:45.239> we'll<00:00:45.360> build<00:00:45.480> out 00:00:45.650 --> 00:00:45.660 align:start position:0% the smart contracts and we'll build out 00:00:45.660 --> 00:00:47.810 align:start position:0% the smart contracts and we'll build out some<00:00:45.840> of<00:00:45.899> the<00:00:46.020> solidity<00:00:46.379> directly 00:00:47.810 --> 00:00:47.820 align:start position:0% some of the solidity directly 00:00:47.820 --> 00:00:49.970 align:start position:0% some of the solidity directly um and<00:00:48.059> then<00:00:48.180> at<00:00:48.660> the<00:00:48.780> end<00:00:48.840> maybe<00:00:49.320> we'll<00:00:49.739> uh 00:00:49.970 --> 00:00:49.980 align:start position:0% um and then at the end maybe we'll uh 00:00:49.980 --> 00:00:52.069 align:start position:0% um and then at the end maybe we'll uh deploy<00:00:50.340> it<00:00:50.460> live<00:00:50.700> on<00:00:51.000> the<00:00:51.120> go<00:00:51.300> early<00:00:51.480> testnet 00:00:52.069 --> 00:00:52.079 align:start position:0% deploy it live on the go early testnet 00:00:52.079 --> 00:00:54.470 align:start position:0% deploy it live on the go early testnet Wi-Fi<00:00:52.739> is<00:00:52.980> a<00:00:53.160> bit<00:00:53.280> suspicious<00:00:53.820> it<00:00:54.059> seems<00:00:54.300> but 00:00:54.470 --> 00:00:54.480 align:start position:0% Wi-Fi is a bit suspicious it seems but 00:00:54.480 --> 00:00:55.850 align:start position:0% Wi-Fi is a bit suspicious it seems but uh<00:00:54.600> we'll<00:00:54.840> see 00:00:55.850 --> 00:00:55.860 align:start position:0% uh we'll see 00:00:55.860 --> 00:00:56.569 align:start position:0% uh we'll see um 00:00:56.569 --> 00:00:56.579 align:start position:0% um 00:00:56.579 --> 00:00:59.150 align:start position:0% um so<00:00:57.899> um<00:00:57.960> let<00:00:58.320> me<00:00:58.440> talk<00:00:58.559> a<00:00:58.620> bit<00:00:58.739> about<00:00:58.860> arbridge 00:00:59.150 --> 00:00:59.160 align:start position:0% so um let me talk a bit about arbridge 00:00:59.160 --> 00:01:00.770 align:start position:0% so um let me talk a bit about arbridge room<00:00:59.399> first<00:00:59.940> um<00:00:59.940> so<00:01:00.120> Arboretum<00:01:00.539> is<00:01:00.660> an 00:01:00.770 --> 00:01:00.780 align:start position:0% room first um so Arboretum is an 00:01:00.780 --> 00:01:03.049 align:start position:0% room first um so Arboretum is an ethereum<00:01:01.079> layer<00:01:01.379> too<00:01:01.559> uh<00:01:02.460> for<00:01:02.640> our<00:01:02.699> purposes 00:01:03.049 --> 00:01:03.059 align:start position:0% ethereum layer too uh for our purposes 00:01:03.059 --> 00:01:04.789 align:start position:0% ethereum layer too uh for our purposes we<00:01:03.239> can<00:01:03.359> think<00:01:03.420> of<00:01:03.539> arbitrum<00:01:04.080> as<00:01:04.320> its<00:01:04.739> own 00:01:04.789 --> 00:01:04.799 align:start position:0% we can think of arbitrum as its own 00:01:04.799 --> 00:01:06.830 align:start position:0% we can think of arbitrum as its own blockchain<00:01:05.159> because<00:01:05.400> it<00:01:05.580> is<00:01:05.700> a<00:01:05.760> blockchain 00:01:06.830 --> 00:01:06.840 align:start position:0% blockchain because it is a blockchain 00:01:06.840 --> 00:01:08.270 align:start position:0% blockchain because it is a blockchain um<00:01:06.900> runs<00:01:07.200> on<00:01:07.320> top<00:01:07.439> of<00:01:07.560> ethereum<00:01:07.979> and<00:01:08.100> kind<00:01:08.220> of 00:01:08.270 --> 00:01:08.280 align:start position:0% um runs on top of ethereum and kind of 00:01:08.280 --> 00:01:10.550 align:start position:0% um runs on top of ethereum and kind of inherits<00:01:08.700> security<00:01:08.880> from<00:01:09.119> ethereum 00:01:10.550 --> 00:01:10.560 align:start position:0% inherits security from ethereum 00:01:10.560 --> 00:01:12.830 align:start position:0% inherits security from ethereum the<00:01:11.400> uh<00:01:11.640> the<00:01:11.939> important<00:01:12.180> thing<00:01:12.360> for<00:01:12.600> for 00:01:12.830 --> 00:01:12.840 align:start position:0% the uh the important thing for for 00:01:12.840 --> 00:01:14.510 align:start position:0% the uh the important thing for for building<00:01:13.140> this<00:01:13.380> bridge<00:01:13.560> is<00:01:13.740> arbitrum<00:01:14.220> allowed 00:01:14.510 --> 00:01:14.520 align:start position:0% building this bridge is arbitrum allowed 00:01:14.520 --> 00:01:15.890 align:start position:0% building this bridge is arbitrum allowed a<00:01:14.640> sort<00:01:14.700> of<00:01:14.760> arbitrary<00:01:15.180> message<00:01:15.420> passing 00:01:15.890 --> 00:01:15.900 align:start position:0% a sort of arbitrary message passing 00:01:15.900 --> 00:01:18.230 align:start position:0% a sort of arbitrary message passing between<00:01:16.020> layers<00:01:16.560> so<00:01:17.100> we<00:01:17.220> can<00:01:17.400> send 00:01:18.230 --> 00:01:18.240 align:start position:0% between layers so we can send 00:01:18.240 --> 00:01:19.370 align:start position:0% between layers so we can send um<00:01:18.360> I'm<00:01:18.720> just<00:01:18.840> going<00:01:18.960> to<00:01:19.020> leave<00:01:19.080> the<00:01:19.200> Twitter 00:01:19.370 --> 00:01:19.380 align:start position:0% um I'm just going to leave the Twitter 00:01:19.380 --> 00:01:20.690 align:start position:0% um I'm just going to leave the Twitter there<00:01:19.619> for<00:01:19.740> a<00:01:19.860> bit<00:01:19.920> so<00:01:20.040> people<00:01:20.220> can<00:01:20.400> find<00:01:20.580> the 00:01:20.690 --> 00:01:20.700 align:start position:0% there for a bit so people can find the 00:01:20.700 --> 00:01:21.350 align:start position:0% there for a bit so people can find the link 00:01:21.350 --> 00:01:21.360 align:start position:0% link 00:01:21.360 --> 00:01:22.249 align:start position:0% link um 00:01:22.249 --> 00:01:22.259 align:start position:0% um 00:01:22.259 --> 00:01:24.050 align:start position:0% um um<00:01:22.380> we<00:01:22.680> can<00:01:22.799> send<00:01:22.920> arbitrary<00:01:23.400> messages<00:01:23.640> sort 00:01:24.050 --> 00:01:24.060 align:start position:0% um we can send arbitrary messages sort 00:01:24.060 --> 00:01:25.969 align:start position:0% um we can send arbitrary messages sort of<00:01:24.119> from<00:01:24.299> L1<00:01:24.659> from<00:01:24.900> an<00:01:25.020> L1<00:01:25.259> contract<00:01:25.619> directly 00:01:25.969 --> 00:01:25.979 align:start position:0% of from L1 from an L1 contract directly 00:01:25.979 --> 00:01:27.950 align:start position:0% of from L1 from an L1 contract directly to<00:01:26.100> Layer<00:01:26.400> Two<00:01:26.520> uh<00:01:27.240> I<00:01:27.299> shouldn't<00:01:27.600> say<00:01:27.659> directly 00:01:27.950 --> 00:01:27.960 align:start position:0% to Layer Two uh I shouldn't say directly 00:01:27.960 --> 00:01:29.450 align:start position:0% to Layer Two uh I shouldn't say directly maybe<00:01:28.140> sort<00:01:28.380> of<00:01:28.500> asynchronously<00:01:29.100> we<00:01:29.280> can<00:01:29.400> send 00:01:29.450 --> 00:01:29.460 align:start position:0% maybe sort of asynchronously we can send 00:01:29.460 --> 00:01:32.090 align:start position:0% maybe sort of asynchronously we can send messages<00:01:29.640> to<00:01:29.939> layer<00:01:30.180> two<00:01:30.360> but<00:01:30.659> arbitrarily 00:01:32.090 --> 00:01:32.100 align:start position:0% messages to layer two but arbitrarily 00:01:32.100 --> 00:01:34.130 align:start position:0% messages to layer two but arbitrarily um<00:01:32.159> and<00:01:32.759> likewise<00:01:33.180> we<00:01:33.299> can<00:01:33.420> send<00:01:33.600> arbitrary 00:01:34.130 --> 00:01:34.140 align:start position:0% um and likewise we can send arbitrary 00:01:34.140 --> 00:01:36.109 align:start position:0% um and likewise we can send arbitrary make<00:01:34.380> arbitrary<00:01:34.799> contract<00:01:35.220> calls<00:01:35.579> from<00:01:35.700> layer 00:01:36.109 --> 00:01:36.119 align:start position:0% make arbitrary contract calls from layer 00:01:36.119 --> 00:01:37.670 align:start position:0% make arbitrary contract calls from layer 2<00:01:36.240> down<00:01:36.479> to<00:01:36.600> layer<00:01:36.840> one 00:01:37.670 --> 00:01:37.680 align:start position:0% 2 down to layer one 00:01:37.680 --> 00:01:39.469 align:start position:0% 2 down to layer one and<00:01:38.340> just<00:01:38.579> sort<00:01:38.700> of<00:01:38.759> using<00:01:39.000> those<00:01:39.180> tools<00:01:39.420> that 00:01:39.469 --> 00:01:39.479 align:start position:0% and just sort of using those tools that 00:01:39.479 --> 00:01:41.149 align:start position:0% and just sort of using those tools that Arboretum<00:01:39.960> gives<00:01:40.140> we<00:01:40.380> can<00:01:40.500> build<00:01:40.680> kind<00:01:40.979> of<00:01:41.040> an 00:01:41.149 --> 00:01:41.159 align:start position:0% Arboretum gives we can build kind of an 00:01:41.159 --> 00:01:42.590 align:start position:0% Arboretum gives we can build kind of an nft<00:01:41.460> Bridge<00:01:41.759> around<00:01:42.000> them<00:01:42.180> and<00:01:42.299> that's<00:01:42.420> what 00:01:42.590 --> 00:01:42.600 align:start position:0% nft Bridge around them and that's what 00:01:42.600 --> 00:01:45.410 align:start position:0% nft Bridge around them and that's what uh<00:01:42.960> that's<00:01:43.200> what<00:01:43.320> we'll<00:01:43.439> be<00:01:43.619> doing 00:01:45.410 --> 00:01:45.420 align:start position:0% uh that's what we'll be doing 00:01:45.420 --> 00:01:46.130 align:start position:0% uh that's what we'll be doing um 00:01:46.130 --> 00:01:46.140 align:start position:0% um 00:01:46.140 --> 00:01:48.230 align:start position:0% um so<00:01:46.860> the 00:01:48.230 --> 00:01:48.240 align:start position:0% so the 00:01:48.240 --> 00:01:49.550 align:start position:0% so the um just<00:01:48.659> to<00:01:48.780> talk<00:01:48.900> a<00:01:49.020> bit<00:01:49.140> about<00:01:49.320> the 00:01:49.550 --> 00:01:49.560 align:start position:0% um just to talk a bit about the 00:01:49.560 --> 00:01:51.170 align:start position:0% um just to talk a bit about the architecture<00:01:50.159> of<00:01:50.520> the<00:01:50.640> bridge<00:01:50.700> itself 00:01:51.170 --> 00:01:51.180 align:start position:0% architecture of the bridge itself 00:01:51.180 --> 00:01:53.210 align:start position:0% architecture of the bridge itself there's<00:01:51.780> obviously<00:01:52.079> many<00:01:52.200> ways<00:01:52.500> to<00:01:52.680> build<00:01:52.860> uh 00:01:53.210 --> 00:01:53.220 align:start position:0% there's obviously many ways to build uh 00:01:53.220 --> 00:01:55.429 align:start position:0% there's obviously many ways to build uh an<00:01:53.399> area<00:01:53.579> c721<00:01:54.299> Bridge<00:01:54.540> or<00:01:54.840> something<00:01:55.020> like<00:01:55.259> it 00:01:55.429 --> 00:01:55.439 align:start position:0% an area c721 Bridge or something like it 00:01:55.439 --> 00:01:58.910 align:start position:0% an area c721 Bridge or something like it this<00:01:56.100> will<00:01:56.280> be<00:01:56.540> very<00:01:57.540> similar<00:01:58.020> to<00:01:58.560> the 00:01:58.910 --> 00:01:58.920 align:start position:0% this will be very similar to the 00:01:58.920 --> 00:02:01.429 align:start position:0% this will be very similar to the architecture<00:01:59.460> we<00:01:59.759> use<00:02:00.000> currently<00:02:00.659> on<00:02:00.899> mainnet 00:02:01.429 --> 00:02:01.439 align:start position:0% architecture we use currently on mainnet 00:02:01.439 --> 00:02:03.410 align:start position:0% architecture we use currently on mainnet speaking<00:02:02.040> of<00:02:02.100> mainnet<00:02:02.579> just<00:02:02.759> to<00:02:02.880> clarify<00:02:03.180> this 00:02:03.410 --> 00:02:03.420 align:start position:0% speaking of mainnet just to clarify this 00:02:03.420 --> 00:02:04.969 align:start position:0% speaking of mainnet just to clarify this disclaimer<00:02:03.840> here<00:02:04.020> this<00:02:04.200> is<00:02:04.320> not<00:02:04.439> tested<00:02:04.799> code 00:02:04.969 --> 00:02:04.979 align:start position:0% disclaimer here this is not tested code 00:02:04.979 --> 00:02:06.770 align:start position:0% disclaimer here this is not tested code not<00:02:05.219> audited<00:02:05.579> don't<00:02:05.700> to<00:02:05.939> playlist<00:02:06.000> on<00:02:06.299> mainnet 00:02:06.770 --> 00:02:06.780 align:start position:0% not audited don't to playlist on mainnet 00:02:06.780 --> 00:02:08.749 align:start position:0% not audited don't to playlist on mainnet not<00:02:07.140> liable<00:02:07.500> whatever<00:02:07.740> okay 00:02:08.749 --> 00:02:08.759 align:start position:0% not liable whatever okay 00:02:08.759 --> 00:02:09.589 align:start position:0% not liable whatever okay um 00:02:09.589 --> 00:02:09.599 align:start position:0% um 00:02:09.599 --> 00:02:11.270 align:start position:0% um code<00:02:10.020> that<00:02:10.259> actually<00:02:10.380> is<00:02:10.500> on<00:02:10.619> man<00:02:10.800> that<00:02:11.160> um<00:02:11.160> we 00:02:11.270 --> 00:02:11.280 align:start position:0% code that actually is on man that um we 00:02:11.280 --> 00:02:12.410 align:start position:0% code that actually is on man that um we use<00:02:11.400> similar<00:02:11.640> architecture<00:02:12.060> for<00:02:12.180> what<00:02:12.300> we 00:02:12.410 --> 00:02:12.420 align:start position:0% use similar architecture for what we 00:02:12.420 --> 00:02:13.970 align:start position:0% use similar architecture for what we call<00:02:12.540> our<00:02:12.660> custom<00:02:12.840> erc20<00:02:13.440> Bridge<00:02:13.680> you<00:02:13.860> can 00:02:13.970 --> 00:02:13.980 align:start position:0% call our custom erc20 Bridge you can 00:02:13.980 --> 00:02:15.650 align:start position:0% call our custom erc20 Bridge you can read<00:02:14.099> more<00:02:14.220> about<00:02:14.400> that<00:02:14.580> in<00:02:14.760> our<00:02:14.879> docs<00:02:15.239> this 00:02:15.650 --> 00:02:15.660 align:start position:0% read more about that in our docs this 00:02:15.660 --> 00:02:17.930 align:start position:0% read more about that in our docs this will<00:02:15.780> be<00:02:15.900> a<00:02:15.959> similar<00:02:16.260> version<00:02:16.379> of<00:02:16.620> that 00:02:17.930 --> 00:02:17.940 align:start position:0% will be a similar version of that 00:02:17.940 --> 00:02:20.630 align:start position:0% will be a similar version of that um<00:02:18.000> by<00:02:18.540> custom<00:02:18.780> what<00:02:19.140> we<00:02:19.319> mean<00:02:19.500> is<00:02:19.920> the<00:02:20.340> token 00:02:20.630 --> 00:02:20.640 align:start position:0% um by custom what we mean is the token 00:02:20.640 --> 00:02:22.610 align:start position:0% um by custom what we mean is the token contracts<00:02:21.060> themselves<00:02:21.420> on<00:02:21.720> both<00:02:21.840> L1<00:02:22.200> and<00:02:22.379> L2 00:02:22.610 --> 00:02:22.620 align:start position:0% contracts themselves on both L1 and L2 00:02:22.620 --> 00:02:24.830 align:start position:0% contracts themselves on both L1 and L2 are<00:02:22.860> sort<00:02:22.980> of<00:02:23.040> deployed<00:02:23.400> directly<00:02:23.760> by<00:02:24.420> you 00:02:24.830 --> 00:02:24.840 align:start position:0% are sort of deployed directly by you 00:02:24.840 --> 00:02:27.229 align:start position:0% are sort of deployed directly by you know<00:02:24.900> a<00:02:25.080> developer<00:02:25.379> a<00:02:25.560> user<00:02:25.860> so 00:02:27.229 --> 00:02:27.239 align:start position:0% know a developer a user so 00:02:27.239 --> 00:02:28.729 align:start position:0% know a developer a user so um<00:02:27.300> they'll<00:02:27.959> be 00:02:28.729 --> 00:02:28.739 align:start position:0% um they'll be 00:02:28.739 --> 00:02:31.970 align:start position:0% um they'll be an<00:02:28.980> ERC<00:02:29.340> 171<00:02:29.879> contract<00:02:30.239> on<00:02:30.480> L1<00:02:30.840> another<00:02:31.319> on<00:02:31.560> L2 00:02:31.970 --> 00:02:31.980 align:start position:0% an ERC 171 contract on L1 another on L2 00:02:31.980 --> 00:02:33.350 align:start position:0% an ERC 171 contract on L1 another on L2 and<00:02:32.400> as<00:02:32.580> long<00:02:32.700> as<00:02:32.760> they<00:02:32.940> have<00:02:33.120> certain 00:02:33.350 --> 00:02:33.360 align:start position:0% and as long as they have certain 00:02:33.360 --> 00:02:34.850 align:start position:0% and as long as they have certain affordances<00:02:33.900> they'll<00:02:34.200> be<00:02:34.319> able<00:02:34.440> to<00:02:34.560> sort<00:02:34.739> of 00:02:34.850 --> 00:02:34.860 align:start position:0% affordances they'll be able to sort of 00:02:34.860 --> 00:02:37.130 align:start position:0% affordances they'll be able to sort of use<00:02:35.040> this<00:02:35.220> bridge<00:02:35.459> uh<00:02:36.360> kind<00:02:36.660> of<00:02:36.780> interact<00:02:37.020> with 00:02:37.130 --> 00:02:37.140 align:start position:0% use this bridge uh kind of interact with 00:02:37.140 --> 00:02:38.990 align:start position:0% use this bridge uh kind of interact with this<00:02:37.319> bridge 00:02:38.990 --> 00:02:39.000 align:start position:0% this bridge 00:02:39.000 --> 00:02:41.270 align:start position:0% this bridge um<00:02:39.080> the<00:02:40.080> basic<00:02:40.440> functionality<00:02:40.860> that<00:02:41.099> we<00:02:41.220> want 00:02:41.270 --> 00:02:41.280 align:start position:0% um the basic functionality that we want 00:02:41.280 --> 00:02:43.009 align:start position:0% um the basic functionality that we want from<00:02:41.459> a<00:02:41.580> bridge<00:02:41.760> we<00:02:42.000> can<00:02:42.060> we<00:02:42.239> should<00:02:42.420> just<00:02:42.599> say 00:02:43.009 --> 00:02:43.019 align:start position:0% from a bridge we can we should just say 00:02:43.019 --> 00:02:45.050 align:start position:0% from a bridge we can we should just say clearly<00:02:43.440> in<00:02:43.620> case<00:02:43.739> it's<00:02:43.860> not<00:02:44.040> obvious 00:02:45.050 --> 00:02:45.060 align:start position:0% clearly in case it's not obvious 00:02:45.060 --> 00:02:46.850 align:start position:0% clearly in case it's not obvious um<00:02:45.120> is<00:02:45.660> basically<00:02:45.959> we<00:02:46.200> have<00:02:46.379> we're<00:02:46.620> sort<00:02:46.739> of 00:02:46.850 --> 00:02:46.860 align:start position:0% um is basically we have we're sort of 00:02:46.860 --> 00:02:49.070 align:start position:0% um is basically we have we're sort of going<00:02:46.980> from<00:02:47.160> L1<00:02:47.519> so<00:02:47.700> the<00:02:47.879> L1<00:02:48.120> contract<00:02:48.599> our<00:02:48.900> our 00:02:49.070 --> 00:02:49.080 align:start position:0% going from L1 so the L1 contract our our 00:02:49.080 --> 00:02:51.229 align:start position:0% going from L1 so the L1 contract our our 721<00:02:49.680> will<00:02:49.860> be<00:02:49.980> the<00:02:50.099> source<00:02:50.340> of<00:02:50.400> Truth 00:02:51.229 --> 00:02:51.239 align:start position:0% 721 will be the source of Truth 00:02:51.239 --> 00:02:53.390 align:start position:0% 721 will be the source of Truth we<00:02:51.720> want<00:02:51.840> to<00:02:51.959> be<00:02:52.080> able<00:02:52.319> to 00:02:53.390 --> 00:02:53.400 align:start position:0% we want to be able to 00:02:53.400 --> 00:02:56.750 align:start position:0% we want to be able to um<00:02:53.459> essentially<00:02:54.000> use<00:02:54.959> this<00:02:55.260> uh<00:02:55.560> the<00:02:55.739> 721<00:02:56.220> on<00:02:56.400> L1 00:02:56.750 --> 00:02:56.760 align:start position:0% um essentially use this uh the 721 on L1 00:02:56.760 --> 00:02:58.550 align:start position:0% um essentially use this uh the 721 on L1 and<00:02:56.940> get<00:02:57.120> a<00:02:57.300> representation<00:02:57.780> of<00:02:58.080> a<00:02:58.200> token<00:02:58.440> on 00:02:58.550 --> 00:02:58.560 align:start position:0% and get a representation of a token on 00:02:58.560 --> 00:03:00.890 align:start position:0% and get a representation of a token on L2<00:02:58.980> that<00:02:59.879> effectively<00:03:00.239> gives<00:03:00.420> us<00:03:00.540> rights<00:03:00.840> to 00:03:00.890 --> 00:03:00.900 align:start position:0% L2 that effectively gives us rights to 00:03:00.900 --> 00:03:02.809 align:start position:0% L2 that effectively gives us rights to the<00:03:01.019> Token<00:03:01.260> back<00:03:01.379> down<00:03:01.560> on<00:03:01.739> L1<00:03:02.040> so<00:03:02.340> you<00:03:02.640> can 00:03:02.809 --> 00:03:02.819 align:start position:0% the Token back down on L1 so you can 00:03:02.819 --> 00:03:04.490 align:start position:0% the Token back down on L1 so you can deposit<00:03:03.180> it<00:03:03.300> and<00:03:03.420> you're<00:03:03.540> guaranteed<00:03:03.840> rights 00:03:04.490 --> 00:03:04.500 align:start position:0% deposit it and you're guaranteed rights 00:03:04.500 --> 00:03:06.290 align:start position:0% deposit it and you're guaranteed rights to<00:03:04.560> withdraw<00:03:04.920> it 00:03:06.290 --> 00:03:06.300 align:start position:0% to withdraw it 00:03:06.300 --> 00:03:09.710 align:start position:0% to withdraw it um<00:03:06.560> the<00:03:07.560> the<00:03:07.800> contracts<00:03:08.400> involved<00:03:09.000> will<00:03:09.480> be 00:03:09.710 --> 00:03:09.720 align:start position:0% um the the contracts involved will be 00:03:09.720 --> 00:03:11.750 align:start position:0% um the the contracts involved will be what<00:03:10.080> we<00:03:10.200> call<00:03:10.319> our<00:03:10.440> Gateway<00:03:10.800> contract<00:03:11.280> so<00:03:11.519> one 00:03:11.750 --> 00:03:11.760 align:start position:0% what we call our Gateway contract so one 00:03:11.760 --> 00:03:14.390 align:start position:0% what we call our Gateway contract so one contract<00:03:12.120> on<00:03:12.300> L1<00:03:12.599> one<00:03:12.840> contract<00:03:13.140> on<00:03:13.319> L2<00:03:13.739> these 00:03:14.390 --> 00:03:14.400 align:start position:0% contract on L1 one contract on L2 these 00:03:14.400 --> 00:03:15.710 align:start position:0% contract on L1 one contract on L2 these are<00:03:14.459> the<00:03:14.580> sort<00:03:14.819> of<00:03:14.879> bridge<00:03:15.000> contracts<00:03:15.540> that 00:03:15.710 --> 00:03:15.720 align:start position:0% are the sort of bridge contracts that 00:03:15.720 --> 00:03:17.869 align:start position:0% are the sort of bridge contracts that are<00:03:15.840> in<00:03:15.959> charge<00:03:16.140> of<00:03:16.560> managing<00:03:17.400> the<00:03:17.580> mapping 00:03:17.869 --> 00:03:17.879 align:start position:0% are in charge of managing the mapping 00:03:17.879 --> 00:03:19.729 align:start position:0% are in charge of managing the mapping between<00:03:18.120> the<00:03:18.420> L1<00:03:18.720> token<00:03:19.080> address<00:03:19.200> and<00:03:19.440> the<00:03:19.500> L2 00:03:19.729 --> 00:03:19.739 align:start position:0% between the L1 token address and the L2 00:03:19.739 --> 00:03:22.309 align:start position:0% between the L1 token address and the L2 token<00:03:20.099> address<00:03:20.360> as<00:03:21.360> well<00:03:21.480> as<00:03:21.540> handling<00:03:22.019> the 00:03:22.309 --> 00:03:22.319 align:start position:0% token address as well as handling the 00:03:22.319 --> 00:03:23.750 align:start position:0% token address as well as handling the deposit<00:03:22.680> and<00:03:22.739> withdrawal<00:03:23.099> functionality<00:03:23.519> so 00:03:23.750 --> 00:03:23.760 align:start position:0% deposit and withdrawal functionality so 00:03:23.760 --> 00:03:25.910 align:start position:0% deposit and withdrawal functionality so I'll<00:03:23.819> just<00:03:24.000> sort<00:03:24.180> of<00:03:24.300> walk<00:03:25.019> through<00:03:25.319> the<00:03:25.800> uh 00:03:25.910 --> 00:03:25.920 align:start position:0% I'll just sort of walk through the uh 00:03:25.920 --> 00:03:27.350 align:start position:0% I'll just sort of walk through the uh the<00:03:26.220> flow<00:03:26.400> real<00:03:26.580> quick<00:03:26.760> and<00:03:26.879> then<00:03:27.060> we'll<00:03:27.180> get 00:03:27.350 --> 00:03:27.360 align:start position:0% the flow real quick and then we'll get 00:03:27.360 --> 00:03:30.710 align:start position:0% the flow real quick and then we'll get started<00:03:27.720> filling<00:03:28.680> out<00:03:28.800> the<00:03:28.920> code 00:03:30.710 --> 00:03:30.720 align:start position:0% started filling out the code 00:03:30.720 --> 00:03:33.229 align:start position:0% started filling out the code um<00:03:30.780> but<00:03:31.800> um<00:03:31.800> so<00:03:31.980> again<00:03:32.159> the<00:03:32.340> flow<00:03:32.580> is<00:03:32.760> we<00:03:33.000> we 00:03:33.229 --> 00:03:33.239 align:start position:0% um but um so again the flow is we we 00:03:33.239 --> 00:03:34.729 align:start position:0% um but um so again the flow is we we have<00:03:33.420> our<00:03:33.540> we<00:03:33.720> have<00:03:34.019> our<00:03:34.140> token<00:03:34.440> contracts 00:03:34.729 --> 00:03:34.739 align:start position:0% have our we have our token contracts 00:03:34.739 --> 00:03:37.190 align:start position:0% have our we have our token contracts deployed<00:03:35.099> on<00:03:35.220> layer<00:03:35.400> one<00:03:35.519> and<00:03:35.640> Layer<00:03:35.940> Two 00:03:37.190 --> 00:03:37.200 align:start position:0% deployed on layer one and Layer Two 00:03:37.200 --> 00:03:38.809 align:start position:0% deployed on layer one and Layer Two um<00:03:37.319> we'll<00:03:37.500> see<00:03:37.739> what<00:03:37.980> affordances<00:03:38.519> they<00:03:38.640> need 00:03:38.809 --> 00:03:38.819 align:start position:0% um we'll see what affordances they need 00:03:38.819 --> 00:03:39.890 align:start position:0% um we'll see what affordances they need as<00:03:39.000> we<00:03:39.180> go 00:03:39.890 --> 00:03:39.900 align:start position:0% as we go 00:03:39.900 --> 00:03:41.089 align:start position:0% as we go um<00:03:39.959> but<00:03:40.140> there's<00:03:40.260> kind<00:03:40.440> of<00:03:40.500> Three<00:03:40.620> cross<00:03:40.860> chain 00:03:41.089 --> 00:03:41.099 align:start position:0% um but there's kind of Three cross chain 00:03:41.099 --> 00:03:42.229 align:start position:0% um but there's kind of Three cross chain messages<00:03:41.340> that<00:03:41.700> are<00:03:41.819> going<00:03:41.940> to<00:03:42.000> have<00:03:42.120> to 00:03:42.229 --> 00:03:42.239 align:start position:0% messages that are going to have to 00:03:42.239 --> 00:03:45.589 align:start position:0% messages that are going to have to happen<00:03:42.360> here<00:03:42.659> so<00:03:43.019> one<00:03:43.560> is<00:03:43.860> we<00:03:44.040> the<00:03:44.879> um<00:03:44.940> the<00:03:45.360> L1 00:03:45.589 --> 00:03:45.599 align:start position:0% happen here so one is we the um the L1 00:03:45.599 --> 00:03:47.210 align:start position:0% happen here so one is we the um the L1 token<00:03:46.019> contract<00:03:46.260> kind<00:03:46.500> of<00:03:46.680> has<00:03:46.799> to<00:03:46.920> register 00:03:47.210 --> 00:03:47.220 align:start position:0% token contract kind of has to register 00:03:47.220 --> 00:03:49.250 align:start position:0% token contract kind of has to register itself<00:03:47.519> to<00:03:47.760> the<00:03:47.879> Gateway<00:03:48.180> which<00:03:48.900> basically 00:03:49.250 --> 00:03:49.260 align:start position:0% itself to the Gateway which basically 00:03:49.260 --> 00:03:51.830 align:start position:0% itself to the Gateway which basically just<00:03:49.500> means<00:03:49.799> it<00:03:50.099> it<00:03:50.220> kind<00:03:50.519> of<00:03:50.580> opts<00:03:51.060> in<00:03:51.120> to<00:03:51.599> what 00:03:51.830 --> 00:03:51.840 align:start position:0% just means it it kind of opts in to what 00:03:51.840 --> 00:03:53.330 align:start position:0% just means it it kind of opts in to what its<00:03:52.019> L2<00:03:52.260> address<00:03:52.440> will<00:03:52.739> be<00:03:52.920> or<00:03:53.040> what<00:03:53.159> its 00:03:53.330 --> 00:03:53.340 align:start position:0% its L2 address will be or what its 00:03:53.340 --> 00:03:54.949 align:start position:0% its L2 address will be or what its corresponding<00:03:53.640> L2<00:03:53.940> token<00:03:54.360> address<00:03:54.480> will<00:03:54.720> be 00:03:54.949 --> 00:03:54.959 align:start position:0% corresponding L2 token address will be 00:03:54.959 --> 00:03:56.690 align:start position:0% corresponding L2 token address will be and<00:03:55.739> we'll<00:03:55.920> do<00:03:56.040> that<00:03:56.159> we'll<00:03:56.340> just<00:03:56.519> sort<00:03:56.640> of 00:03:56.690 --> 00:03:56.700 align:start position:0% and we'll do that we'll just sort of 00:03:56.700 --> 00:03:58.490 align:start position:0% and we'll do that we'll just sort of store<00:03:56.879> a<00:03:57.060> mapping<00:03:57.360> on<00:03:57.599> the<00:03:57.720> L1<00:03:58.019> side<00:03:58.200> and<00:03:58.379> the 00:03:58.490 --> 00:03:58.500 align:start position:0% store a mapping on the L1 side and the 00:03:58.500 --> 00:04:00.949 align:start position:0% store a mapping on the L1 side and the L2<00:03:58.799> aside<00:03:59.099> that<00:03:59.340> Maps<00:03:59.640> L1<00:04:00.000> token<00:04:00.360> to<00:04:00.480> L<00:04:00.599> to<00:04:00.780> a 00:04:00.949 --> 00:04:00.959 align:start position:0% L2 aside that Maps L1 token to L to a 00:04:00.959 --> 00:04:02.149 align:start position:0% L2 aside that Maps L1 token to L to a token<00:04:01.200> so<00:04:01.500> that's<00:04:01.680> this<00:04:01.860> kind<00:04:02.099> of 00:04:02.149 --> 00:04:02.159 align:start position:0% token so that's this kind of 00:04:02.159 --> 00:04:03.710 align:start position:0% token so that's this kind of registration<00:04:02.640> so<00:04:03.060> it<00:04:03.180> needs<00:04:03.299> to<00:04:03.420> be<00:04:03.480> able<00:04:03.599> to 00:04:03.710 --> 00:04:03.720 align:start position:0% registration so it needs to be able to 00:04:03.720 --> 00:04:05.449 align:start position:0% registration so it needs to be able to make<00:04:03.900> that<00:04:04.080> call<00:04:04.260> and<00:04:05.040> that'll<00:04:05.280> be<00:04:05.400> a 00:04:05.449 --> 00:04:05.459 align:start position:0% make that call and that'll be a 00:04:05.459 --> 00:04:07.910 align:start position:0% make that call and that'll be a cross-chain<00:04:05.819> messages<00:04:06.060> so<00:04:06.420> both<00:04:06.659> both<00:04:07.500> layers 00:04:07.910 --> 00:04:07.920 align:start position:0% cross-chain messages so both both layers 00:04:07.920 --> 00:04:10.250 align:start position:0% cross-chain messages so both both layers sort<00:04:08.099> of<00:04:08.220> know<00:04:08.340> what<00:04:08.519> token<00:04:08.879> maps<00:04:09.120> to<00:04:09.180> wear<00:04:09.360> uh 00:04:10.250 --> 00:04:10.260 align:start position:0% sort of know what token maps to wear uh 00:04:10.260 --> 00:04:11.929 align:start position:0% sort of know what token maps to wear uh we<00:04:10.439> need<00:04:10.500> to<00:04:10.620> be<00:04:10.680> able<00:04:10.799> to<00:04:10.920> deposit<00:04:11.280> deposit<00:04:11.819> in 00:04:11.929 --> 00:04:11.939 align:start position:0% we need to be able to deposit deposit in 00:04:11.939 --> 00:04:13.610 align:start position:0% we need to be able to deposit deposit in this<00:04:12.060> case<00:04:12.180> is<00:04:12.360> going<00:04:12.540> to<00:04:12.659> mean<00:04:12.900> sort<00:04:13.560> of 00:04:13.610 --> 00:04:13.620 align:start position:0% this case is going to mean sort of 00:04:13.620 --> 00:04:15.110 align:start position:0% this case is going to mean sort of sending<00:04:13.860> the<00:04:13.920> token<00:04:14.220> to<00:04:14.280> L1<00:04:14.580> and<00:04:14.819> escrow 00:04:15.110 --> 00:04:15.120 align:start position:0% sending the token to L1 and escrow 00:04:15.120 --> 00:04:17.030 align:start position:0% sending the token to L1 and escrow sending<00:04:15.480> a<00:04:15.540> cross-train<00:04:15.900> message<00:04:16.079> to<00:04:16.320> L2<00:04:16.680> so 00:04:17.030 --> 00:04:17.040 align:start position:0% sending a cross-train message to L2 so 00:04:17.040 --> 00:04:19.370 align:start position:0% sending a cross-train message to L2 so our<00:04:17.280> corresponding<00:04:17.760> contract<00:04:18.359> mints<00:04:18.840> so 00:04:19.370 --> 00:04:19.380 align:start position:0% our corresponding contract mints so 00:04:19.380 --> 00:04:20.930 align:start position:0% our corresponding contract mints so escrow<00:04:19.799> and<00:04:19.979> mint<00:04:20.100> is<00:04:20.280> a<00:04:20.400> deposit<00:04:20.699> and<00:04:20.820> a 00:04:20.930 --> 00:04:20.940 align:start position:0% escrow and mint is a deposit and a 00:04:20.940 --> 00:04:22.790 align:start position:0% escrow and mint is a deposit and a withdraw<00:04:21.299> is<00:04:21.419> kind<00:04:21.600> of<00:04:21.660> the<00:04:21.840> opposite<00:04:22.680> um 00:04:22.790 --> 00:04:22.800 align:start position:0% withdraw is kind of the opposite um 00:04:22.800 --> 00:04:25.010 align:start position:0% withdraw is kind of the opposite um we're<00:04:22.919> going<00:04:23.100> to<00:04:23.340> burn<00:04:23.880> the<00:04:24.120> token<00:04:24.360> on<00:04:24.479> L2<00:04:24.840> send 00:04:25.010 --> 00:04:25.020 align:start position:0% we're going to burn the token on L2 send 00:04:25.020 --> 00:04:26.390 align:start position:0% we're going to burn the token on L2 send a<00:04:25.139> cross<00:04:25.259> chain<00:04:25.440> message<00:04:25.680> down<00:04:25.860> to<00:04:26.040> layer<00:04:26.280> one 00:04:26.390 --> 00:04:26.400 align:start position:0% a cross chain message down to layer one 00:04:26.400 --> 00:04:27.710 align:start position:0% a cross chain message down to layer one which<00:04:26.759> will<00:04:26.940> eventually<00:04:27.180> release<00:04:27.360> it<00:04:27.600> from 00:04:27.710 --> 00:04:27.720 align:start position:0% which will eventually release it from 00:04:27.720 --> 00:04:29.330 align:start position:0% which will eventually release it from SQL 00:04:29.330 --> 00:04:29.340 align:start position:0% SQL 00:04:29.340 --> 00:04:30.830 align:start position:0% SQL um that's<00:04:29.940> the<00:04:30.120> flow<00:04:30.240> we<00:04:30.419> need<00:04:30.540> if<00:04:30.720> you're 00:04:30.830 --> 00:04:30.840 align:start position:0% um that's the flow we need if you're 00:04:30.840 --> 00:04:32.330 align:start position:0% um that's the flow we need if you're coding<00:04:31.080> along<00:04:31.199> uh<00:04:31.560> yeah<00:04:31.680> you<00:04:31.860> can<00:04:31.919> get<00:04:32.040> clone 00:04:32.330 --> 00:04:32.340 align:start position:0% coding along uh yeah you can get clone 00:04:32.340 --> 00:04:34.550 align:start position:0% coding along uh yeah you can get clone this<00:04:32.520> and<00:04:33.300> yeah<00:04:33.479> let<00:04:33.840> me<00:04:33.960> get<00:04:34.080> to<00:04:34.199> deploying 00:04:34.550 --> 00:04:34.560 align:start position:0% this and yeah let me get to deploying 00:04:34.560 --> 00:04:35.870 align:start position:0% this and yeah let me get to deploying you<00:04:34.740> can<00:04:34.860> just<00:04:34.979> set<00:04:35.100> these<00:04:35.340> environmental 00:04:35.870 --> 00:04:35.880 align:start position:0% you can just set these environmental 00:04:35.880 --> 00:04:37.370 align:start position:0% you can just set these environmental variables 00:04:37.370 --> 00:04:37.380 align:start position:0% variables 00:04:37.380 --> 00:04:38.810 align:start position:0% variables um<00:04:37.440> you'll<00:04:37.919> need 00:04:38.810 --> 00:04:38.820 align:start position:0% um you'll need 00:04:38.820 --> 00:04:42.170 align:start position:0% um you'll need an<00:04:39.360> L1<00:04:39.780> gorilla<00:04:40.680> RPC<00:04:41.160> URL 00:04:42.170 --> 00:04:42.180 align:start position:0% an L1 gorilla RPC URL 00:04:42.180 --> 00:04:44.510 align:start position:0% an L1 gorilla RPC URL um<00:04:42.240> and<00:04:42.540> some<00:04:42.840> uh<00:04:43.380> private<00:04:43.860> key<00:04:43.979> funded<00:04:44.400> with 00:04:44.510 --> 00:04:44.520 align:start position:0% um and some uh private key funded with 00:04:44.520 --> 00:04:46.370 align:start position:0% um and some uh private key funded with Gorillaz<00:04:45.000> if<00:04:45.240> you<00:04:45.720> want<00:04:45.840> to<00:04:45.900> actually<00:04:45.960> deploy 00:04:46.370 --> 00:04:46.380 align:start position:0% Gorillaz if you want to actually deploy 00:04:46.380 --> 00:04:49.010 align:start position:0% Gorillaz if you want to actually deploy it<00:04:46.500> but<00:04:47.160> um<00:04:47.240> uh<00:04:48.240> yeah 00:04:49.010 --> 00:04:49.020 align:start position:0% it but um uh yeah 00:04:49.020 --> 00:04:52.070 align:start position:0% it but um uh yeah for<00:04:49.560> now<00:04:49.680> let's<00:04:50.220> let's<00:04:50.580> let's<00:04:50.699> dive<00:04:51.360> in<00:04:51.540> I'll 00:04:52.070 --> 00:04:52.080 align:start position:0% for now let's let's let's dive in I'll 00:04:52.080 --> 00:04:53.270 align:start position:0% for now let's let's let's dive in I'll get<00:04:52.259> rid<00:04:52.380> of 00:04:53.270 --> 00:04:53.280 align:start position:0% get rid of 00:04:53.280 --> 00:04:54.770 align:start position:0% get rid of my<00:04:53.580> Twitter 00:04:54.770 --> 00:04:54.780 align:start position:0% my Twitter 00:04:54.780 --> 00:04:56.629 align:start position:0% my Twitter um 00:04:56.629 --> 00:04:56.639 align:start position:0% um 00:04:56.639 --> 00:04:57.890 align:start position:0% um okay 00:04:57.890 --> 00:04:57.900 align:start position:0% okay 00:04:57.900 --> 00:04:59.930 align:start position:0% okay so 00:04:59.930 --> 00:04:59.940 align:start position:0% so 00:04:59.940 --> 00:05:02.210 align:start position:0% so um<00:05:00.000> to<00:05:00.419> start<00:05:00.720> we<00:05:01.199> can<00:05:01.320> sort<00:05:01.560> of<00:05:01.620> go<00:05:01.860> so<00:05:02.100> we're 00:05:02.210 --> 00:05:02.220 align:start position:0% um to start we can sort of go so we're 00:05:02.220 --> 00:05:03.290 align:start position:0% um to start we can sort of go so we're going<00:05:02.340> to<00:05:02.400> start<00:05:02.580> with<00:05:02.759> as<00:05:02.880> far<00:05:03.000> as<00:05:03.120> the<00:05:03.180> cross 00:05:03.290 --> 00:05:03.300 align:start position:0% going to start with as far as the cross 00:05:03.300 --> 00:05:04.850 align:start position:0% going to start with as far as the cross chain<00:05:03.479> messages<00:05:03.780> go<00:05:04.139> we'll<00:05:04.380> start<00:05:04.560> with<00:05:04.680> this 00:05:04.850 --> 00:05:04.860 align:start position:0% chain messages go we'll start with this 00:05:04.860 --> 00:05:06.650 align:start position:0% chain messages go we'll start with this registration<00:05:05.340> step 00:05:06.650 --> 00:05:06.660 align:start position:0% registration step 00:05:06.660 --> 00:05:10.129 align:start position:0% registration step um<00:05:06.780> so<00:05:07.020> let<00:05:07.199> me<00:05:07.440> do<00:05:07.919> this 00:05:10.129 --> 00:05:10.139 align:start position:0% um so let me do this 00:05:10.139 --> 00:05:11.570 align:start position:0% um so let me do this um<00:05:10.199> so<00:05:10.440> first<00:05:10.680> of<00:05:10.800> all<00:05:10.860> just<00:05:11.040> looking<00:05:11.220> in<00:05:11.460> our 00:05:11.570 --> 00:05:11.580 align:start position:0% um so first of all just looking in our 00:05:11.580 --> 00:05:13.370 align:start position:0% um so first of all just looking in our repo<00:05:12.000> real<00:05:12.180> quick 00:05:13.370 --> 00:05:13.380 align:start position:0% repo real quick 00:05:13.380 --> 00:05:15.650 align:start position:0% repo real quick um I'm<00:05:13.560> just<00:05:13.740> in<00:05:13.919> the<00:05:14.040> contracts<00:05:14.460> directory 00:05:15.650 --> 00:05:15.660 align:start position:0% um I'm just in the contracts directory 00:05:15.660 --> 00:05:17.030 align:start position:0% um I'm just in the contracts directory here's<00:05:16.080> our<00:05:16.199> contracts<00:05:16.440> that'll<00:05:16.680> be<00:05:16.800> deployed 00:05:17.030 --> 00:05:17.040 align:start position:0% here's our contracts that'll be deployed 00:05:17.040 --> 00:05:18.230 align:start position:0% here's our contracts that'll be deployed on<00:05:17.160> ethereum<00:05:17.460> here's<00:05:17.699> the<00:05:17.759> ones<00:05:17.880> that<00:05:18.000> will<00:05:18.120> be 00:05:18.230 --> 00:05:18.240 align:start position:0% on ethereum here's the ones that will be 00:05:18.240 --> 00:05:21.590 align:start position:0% on ethereum here's the ones that will be deployed<00:05:18.660> on<00:05:18.960> arbitrum<00:05:19.500> L2<00:05:20.400> and<00:05:21.000> basically<00:05:21.360> we 00:05:21.590 --> 00:05:21.600 align:start position:0% deployed on arbitrum L2 and basically we 00:05:21.600 --> 00:05:24.230 align:start position:0% deployed on arbitrum L2 and basically we have<00:05:21.840> the<00:05:22.560> L1<00:05:22.919> token<00:05:23.280> itself<00:05:23.460> dl2<00:05:23.880> token 00:05:24.230 --> 00:05:24.240 align:start position:0% have the L1 token itself dl2 token 00:05:24.240 --> 00:05:25.969 align:start position:0% have the L1 token itself dl2 token itself<00:05:24.479> scale<00:05:24.780> one<00:05:24.960> Gateway<00:05:25.199> the<00:05:25.440> L2<00:05:25.680> to<00:05:25.860> get 00:05:25.969 --> 00:05:25.979 align:start position:0% itself scale one Gateway the L2 to get 00:05:25.979 --> 00:05:27.770 align:start position:0% itself scale one Gateway the L2 to get where<00:05:26.280> we'll<00:05:26.639> talk<00:05:26.820> about<00:05:26.940> this<00:05:27.120> Alias<00:05:27.539> helper 00:05:27.770 --> 00:05:27.780 align:start position:0% where we'll talk about this Alias helper 00:05:27.780 --> 00:05:29.990 align:start position:0% where we'll talk about this Alias helper later<00:05:27.960> just<00:05:28.139> ignore<00:05:28.440> that<00:05:28.560> for<00:05:28.680> now 00:05:29.990 --> 00:05:30.000 align:start position:0% later just ignore that for now 00:05:30.000 --> 00:05:32.150 align:start position:0% later just ignore that for now yes 00:05:32.150 --> 00:05:32.160 align:start position:0% yes 00:05:32.160 --> 00:05:34.010 align:start position:0% yes is<00:05:32.400> that<00:05:32.580> good 00:05:34.010 --> 00:05:34.020 align:start position:0% is that good 00:05:34.020 --> 00:05:35.710 align:start position:0% is that good mark 00:05:35.710 --> 00:05:35.720 align:start position:0% mark 00:05:35.720 --> 00:05:39.409 align:start position:0% mark a<00:05:36.720> lot<00:05:36.840> more<00:05:37.020> yeah 00:05:39.409 --> 00:05:39.419 align:start position:0% a lot more yeah 00:05:39.419 --> 00:05:42.890 align:start position:0% a lot more yeah um 00:05:42.890 --> 00:05:42.900 align:start position:0% 00:05:42.900 --> 00:05:45.529 align:start position:0% so 00:05:45.529 --> 00:05:45.539 align:start position:0% so 00:05:45.539 --> 00:05:47.629 align:start position:0% so we'll<00:05:46.199> start<00:05:46.500> with 00:05:47.629 --> 00:05:47.639 align:start position:0% we'll start with 00:05:47.639 --> 00:05:50.330 align:start position:0% we'll start with so<00:05:48.240> this<00:05:48.479> is<00:05:48.660> the<00:05:49.020> token<00:05:49.500> contract<00:05:49.860> itself<00:05:50.160> or 00:05:50.330 --> 00:05:50.340 align:start position:0% so this is the token contract itself or 00:05:50.340 --> 00:05:51.950 align:start position:0% so this is the token contract itself or an<00:05:50.520> example<00:05:50.699> of<00:05:50.880> the<00:05:51.000> token<00:05:51.360> contract<00:05:51.660> itself 00:05:51.950 --> 00:05:51.960 align:start position:0% an example of the token contract itself 00:05:51.960 --> 00:05:53.629 align:start position:0% an example of the token contract itself that<00:05:52.199> we<00:05:52.320> might<00:05:52.440> want<00:05:52.680> to<00:05:52.800> use<00:05:52.919> that<00:05:53.340> we<00:05:53.520> might 00:05:53.629 --> 00:05:53.639 align:start position:0% that we might want to use that we might 00:05:53.639 --> 00:05:55.850 align:start position:0% that we might want to use that we might want<00:05:53.759> to<00:05:53.880> bridge<00:05:54.060> right<00:05:54.419> we<00:05:54.720> can<00:05:54.840> see 00:05:55.850 --> 00:05:55.860 align:start position:0% want to bridge right we can see 00:05:55.860 --> 00:05:57.230 align:start position:0% want to bridge right we can see um<00:05:55.919> this<00:05:56.280> is<00:05:56.340> already<00:05:56.460> filled<00:05:56.820> out<00:05:56.880> so<00:05:57.000> nothing 00:05:57.230 --> 00:05:57.240 align:start position:0% um this is already filled out so nothing 00:05:57.240 --> 00:05:58.790 align:start position:0% um this is already filled out so nothing to<00:05:57.419> do<00:05:57.539> here 00:05:58.790 --> 00:05:58.800 align:start position:0% to do here 00:05:58.800 --> 00:06:00.110 align:start position:0% to do here um<00:05:58.919> we<00:05:59.100> can<00:05:59.160> see<00:05:59.280> this<00:05:59.460> is<00:05:59.580> you<00:05:59.759> know<00:05:59.820> standard 00:06:00.110 --> 00:06:00.120 align:start position:0% um we can see this is you know standard 00:06:00.120 --> 00:06:02.689 align:start position:0% um we can see this is you know standard open<00:06:00.240> Zep<00:06:00.539> line<00:06:00.660> Dr<00:06:00.780> c721 00:06:02.689 --> 00:06:02.699 align:start position:0% open Zep line Dr c721 00:06:02.699 --> 00:06:04.070 align:start position:0% open Zep line Dr c721 um<00:06:02.820> we're<00:06:03.000> just<00:06:03.120> giving<00:06:03.300> ourselves<00:06:03.660> the 00:06:04.070 --> 00:06:04.080 align:start position:0% um we're just giving ourselves the 00:06:04.080 --> 00:06:05.450 align:start position:0% um we're just giving ourselves the ability<00:06:04.320> to<00:06:04.560> Minge<00:06:04.860> so<00:06:04.919> we<00:06:05.039> can<00:06:05.160> mint<00:06:05.340> stuff 00:06:05.450 --> 00:06:05.460 align:start position:0% ability to Minge so we can mint stuff 00:06:05.460 --> 00:06:06.950 align:start position:0% ability to Minge so we can mint stuff and<00:06:05.639> play<00:06:05.759> with<00:06:05.880> it 00:06:06.950 --> 00:06:06.960 align:start position:0% and play with it 00:06:06.960 --> 00:06:07.969 align:start position:0% and play with it um the<00:06:07.199> important<00:06:07.440> thing<00:06:07.560> here<00:06:07.740> the 00:06:07.969 --> 00:06:07.979 align:start position:0% um the important thing here the 00:06:07.979 --> 00:06:09.409 align:start position:0% um the important thing here the important<00:06:08.220> affordance<00:06:08.639> that<00:06:08.820> it<00:06:08.880> needs<00:06:09.120> is<00:06:09.300> it 00:06:09.409 --> 00:06:09.419 align:start position:0% important affordance that it needs is it 00:06:09.419 --> 00:06:11.090 align:start position:0% important affordance that it needs is it has<00:06:09.600> this<00:06:09.780> registration<00:06:10.259> method<00:06:10.680> so<00:06:10.919> this 00:06:11.090 --> 00:06:11.100 align:start position:0% has this registration method so this 00:06:11.100 --> 00:06:12.409 align:start position:0% has this registration method so this will<00:06:11.280> actually<00:06:11.400> make<00:06:11.580> an<00:06:11.759> external<00:06:12.120> call<00:06:12.240> to 00:06:12.409 --> 00:06:12.419 align:start position:0% will actually make an external call to 00:06:12.419 --> 00:06:14.450 align:start position:0% will actually make an external call to our<00:06:12.600> Gateway<00:06:12.960> and<00:06:13.560> again<00:06:13.680> this<00:06:13.979> will<00:06:14.100> update 00:06:14.450 --> 00:06:14.460 align:start position:0% our Gateway and again this will update 00:06:14.460 --> 00:06:16.730 align:start position:0% our Gateway and again this will update these<00:06:14.820> mappings<00:06:15.180> on<00:06:15.419> L1<00:06:15.720> and<00:06:15.900> L2<00:06:16.199> okay<00:06:16.440> so 00:06:16.730 --> 00:06:16.740 align:start position:0% these mappings on L1 and L2 okay so 00:06:16.740 --> 00:06:18.290 align:start position:0% these mappings on L1 and L2 okay so that's<00:06:16.919> already<00:06:17.100> done<00:06:17.400> the<00:06:17.639> token<00:06:18.000> has<00:06:18.120> to<00:06:18.180> be 00:06:18.290 --> 00:06:18.300 align:start position:0% that's already done the token has to be 00:06:18.300 --> 00:06:19.969 align:start position:0% that's already done the token has to be able<00:06:18.419> to<00:06:18.479> register<00:06:18.780> itself 00:06:19.969 --> 00:06:19.979 align:start position:0% able to register itself 00:06:19.979 --> 00:06:21.529 align:start position:0% able to register itself um<00:06:20.039> so<00:06:20.220> let's<00:06:20.340> start<00:06:20.520> with<00:06:20.639> that<00:06:20.880> that<00:06:21.120> actual 00:06:21.529 --> 00:06:21.539 align:start position:0% um so let's start with that that actual 00:06:21.539 --> 00:06:23.629 align:start position:0% um so let's start with that that actual registration 00:06:23.629 --> 00:06:23.639 align:start position:0% registration 00:06:23.639 --> 00:06:27.050 align:start position:0% registration um so<00:06:24.300> if<00:06:24.419> we<00:06:24.539> go<00:06:24.720> to<00:06:24.900> L1<00:06:25.380> nft<00:06:25.800> Gateway 00:06:27.050 --> 00:06:27.060 align:start position:0% um so if we go to L1 nft Gateway 00:06:27.060 --> 00:06:28.850 align:start position:0% um so if we go to L1 nft Gateway so<00:06:27.539> again<00:06:27.660> this<00:06:27.960> is<00:06:28.020> like<00:06:28.199> the<00:06:28.560> Gateway 00:06:28.850 --> 00:06:28.860 align:start position:0% so again this is like the Gateway 00:06:28.860 --> 00:06:31.070 align:start position:0% so again this is like the Gateway contract<00:06:29.220> the<00:06:29.400> bridge<00:06:29.520> contract 00:06:31.070 --> 00:06:31.080 align:start position:0% contract the bridge contract 00:06:31.080 --> 00:06:31.730 align:start position:0% contract the bridge contract um 00:06:31.730 --> 00:06:31.740 align:start position:0% um 00:06:31.740 --> 00:06:33.230 align:start position:0% um so<00:06:32.160> the<00:06:32.280> key<00:06:32.400> thing<00:06:32.520> that<00:06:32.699> we<00:06:32.819> wanna<00:06:32.940> that 00:06:33.230 --> 00:06:33.240 align:start position:0% so the key thing that we wanna that 00:06:33.240 --> 00:06:35.210 align:start position:0% so the key thing that we wanna that we're<00:06:33.360> going<00:06:33.479> to<00:06:33.539> be<00:06:33.660> sort<00:06:33.900> of<00:06:34.080> doing<00:06:34.740> here<00:06:34.979> is 00:06:35.210 --> 00:06:35.220 align:start position:0% we're going to be sort of doing here is 00:06:35.220 --> 00:06:37.430 align:start position:0% we're going to be sort of doing here is updating<00:06:35.580> this<00:06:35.759> mapping<00:06:36.120> on<00:06:36.240> the<00:06:36.360> L1<00:06:36.600> side<00:06:36.900> and 00:06:37.430 --> 00:06:37.440 align:start position:0% updating this mapping on the L1 side and 00:06:37.440 --> 00:06:38.629 align:start position:0% updating this mapping on the L1 side and then<00:06:37.500> similarly<00:06:37.919> there's<00:06:38.100> a<00:06:38.220> mapping<00:06:38.460> on<00:06:38.580> the 00:06:38.629 --> 00:06:38.639 align:start position:0% then similarly there's a mapping on the 00:06:38.639 --> 00:06:39.890 align:start position:0% then similarly there's a mapping on the L2<00:06:38.880> side<00:06:39.120> that<00:06:39.300> will<00:06:39.419> catch<00:06:39.600> with<00:06:39.720> a<00:06:39.780> cross 00:06:39.890 --> 00:06:39.900 align:start position:0% L2 side that will catch with a cross 00:06:39.900 --> 00:06:41.629 align:start position:0% L2 side that will catch with a cross chain<00:06:40.080> message 00:06:41.629 --> 00:06:41.639 align:start position:0% chain message 00:06:41.639 --> 00:06:43.249 align:start position:0% chain message um<00:06:41.699> while<00:06:42.000> we're<00:06:42.180> here<00:06:42.360> so<00:06:42.600> basically<00:06:42.900> we<00:06:43.080> just 00:06:43.249 --> 00:06:43.259 align:start position:0% um while we're here so basically we just 00:06:43.259 --> 00:06:44.809 align:start position:0% um while we're here so basically we just have<00:06:43.440> a<00:06:43.919> bunch<00:06:44.100> of<00:06:44.220> functions<00:06:44.520> we<00:06:44.580> need<00:06:44.759> to 00:06:44.809 --> 00:06:44.819 align:start position:0% have a bunch of functions we need to 00:06:44.819 --> 00:06:46.670 align:start position:0% have a bunch of functions we need to fill<00:06:44.940> out<00:06:45.120> but<00:06:46.020> we<00:06:46.139> can<00:06:46.259> just<00:06:46.319> look<00:06:46.440> at<00:06:46.560> what 00:06:46.670 --> 00:06:46.680 align:start position:0% fill out but we can just look at what 00:06:46.680 --> 00:06:48.890 align:start position:0% fill out but we can just look at what we're<00:06:46.800> initializing<00:06:47.340> it<00:06:47.460> with 00:06:48.890 --> 00:06:48.900 align:start position:0% we're initializing it with 00:06:48.900 --> 00:06:51.650 align:start position:0% we're initializing it with um<00:06:49.380> so<00:06:49.979> this<00:06:50.220> is<00:06:50.340> counterpart<00:06:50.819> L2<00:06:51.180> Gateway<00:06:51.479> the 00:06:51.650 --> 00:06:51.660 align:start position:0% um so this is counterpart L2 Gateway the 00:06:51.660 --> 00:06:54.110 align:start position:0% um so this is counterpart L2 Gateway the L2<00:06:51.900> side<00:06:52.080> of<00:06:52.259> the<00:06:52.380> actual<00:06:52.560> nft<00:06:52.919> Bridge<00:06:53.280> we're 00:06:54.110 --> 00:06:54.120 align:start position:0% L2 side of the actual nft Bridge we're 00:06:54.120 --> 00:06:56.090 align:start position:0% L2 side of the actual nft Bridge we're storing<00:06:54.479> that<00:06:54.660> and<00:06:55.139> then<00:06:55.259> inbox<00:06:55.680> and<00:06:55.919> Bridge 00:06:56.090 --> 00:06:56.100 align:start position:0% storing that and then inbox and Bridge 00:06:56.100 --> 00:06:57.710 align:start position:0% storing that and then inbox and Bridge these<00:06:56.460> are<00:06:56.520> both<00:06:56.639> arbitrum<00:06:57.240> core<00:06:57.360> protocol 00:06:57.710 --> 00:06:57.720 align:start position:0% these are both arbitrum core protocol 00:06:57.720 --> 00:06:58.969 align:start position:0% these are both arbitrum core protocol things<00:06:57.960> that<00:06:58.139> we'll<00:06:58.259> use<00:06:58.380> for<00:06:58.560> cross-chain 00:06:58.969 --> 00:06:58.979 align:start position:0% things that we'll use for cross-chain 00:06:58.979 --> 00:07:00.650 align:start position:0% things that we'll use for cross-chain messaging<00:06:59.400> uh<00:06:59.819> that<00:06:59.940> we'll<00:07:00.060> get<00:07:00.240> to<00:07:00.360> in<00:07:00.539> a 00:07:00.650 --> 00:07:00.660 align:start position:0% messaging uh that we'll get to in a 00:07:00.660 --> 00:07:02.330 align:start position:0% messaging uh that we'll get to in a second 00:07:02.330 --> 00:07:02.340 align:start position:0% second 00:07:02.340 --> 00:07:03.890 align:start position:0% second um<00:07:02.460> and<00:07:02.819> then<00:07:02.880> yeah<00:07:03.060> this<00:07:03.300> is<00:07:03.419> this<00:07:03.720> is<00:07:03.840> the 00:07:03.890 --> 00:07:03.900 align:start position:0% um and then yeah this is this is the 00:07:03.900 --> 00:07:05.210 align:start position:0% um and then yeah this is this is the mapping<00:07:04.139> we're<00:07:04.319> actually<00:07:04.440> updating<00:07:04.800> let's 00:07:05.210 --> 00:07:05.220 align:start position:0% mapping we're actually updating let's 00:07:05.220 --> 00:07:07.070 align:start position:0% mapping we're actually updating let's just<00:07:05.340> peek<00:07:05.580> at<00:07:05.639> the<00:07:05.759> L2<00:07:06.000> side<00:07:06.240> as<00:07:06.479> well<00:07:06.600> so<00:07:06.900> the 00:07:07.070 --> 00:07:07.080 align:start position:0% just peek at the L2 side as well so the 00:07:07.080 --> 00:07:08.749 align:start position:0% just peek at the L2 side as well so the L2<00:07:07.319> Gateway 00:07:08.749 --> 00:07:08.759 align:start position:0% L2 Gateway 00:07:08.759 --> 00:07:09.590 align:start position:0% L2 Gateway um 00:07:09.590 --> 00:07:09.600 align:start position:0% um 00:07:09.600 --> 00:07:11.629 align:start position:0% um similarly<00:07:10.259> we<00:07:10.500> have<00:07:10.620> an<00:07:10.680> L1<00:07:10.919> to<00:07:11.100> L2<00:07:11.340> token 00:07:11.629 --> 00:07:11.639 align:start position:0% similarly we have an L1 to L2 token 00:07:11.639 --> 00:07:13.070 align:start position:0% similarly we have an L1 to L2 token mapping<00:07:11.940> that's<00:07:12.240> what<00:07:12.419> we're<00:07:12.539> targeting<00:07:12.840> as 00:07:13.070 --> 00:07:13.080 align:start position:0% mapping that's what we're targeting as 00:07:13.080 --> 00:07:15.590 align:start position:0% mapping that's what we're targeting as we<00:07:13.500> update<00:07:13.740> and<00:07:14.460> uh<00:07:14.819> yeah<00:07:15.180> we'll<00:07:15.360> talk<00:07:15.479> about 00:07:15.590 --> 00:07:15.600 align:start position:0% we update and uh yeah we'll talk about 00:07:15.600 --> 00:07:16.909 align:start position:0% we update and uh yeah we'll talk about that<00:07:15.780> other<00:07:15.900> stuff 00:07:16.909 --> 00:07:16.919 align:start position:0% that other stuff 00:07:16.919 --> 00:07:17.749 align:start position:0% that other stuff um 00:07:17.749 --> 00:07:17.759 align:start position:0% um 00:07:17.759 --> 00:07:21.110 align:start position:0% um when<00:07:18.360> it<00:07:18.479> comes<00:07:18.780> up<00:07:18.840> okay<00:07:19.199> so<00:07:19.860> let's<00:07:20.819> um<00:07:20.880> let's 00:07:21.110 --> 00:07:21.120 align:start position:0% when it comes up okay so let's um let's 00:07:21.120 --> 00:07:23.029 align:start position:0% when it comes up okay so let's um let's start<00:07:21.240> with<00:07:21.419> this<00:07:21.539> registration<00:07:21.960> step<00:07:22.259> so<00:07:22.680> the 00:07:23.029 --> 00:07:23.039 align:start position:0% start with this registration step so the 00:07:23.039 --> 00:07:25.430 align:start position:0% start with this registration step so the token<00:07:23.280> itself<00:07:23.520> made<00:07:23.759> this<00:07:23.940> call<00:07:24.120> right 00:07:25.430 --> 00:07:25.440 align:start position:0% token itself made this call right 00:07:25.440 --> 00:07:27.650 align:start position:0% token itself made this call right um<00:07:25.500> to<00:07:26.340> register<00:07:26.699> itself<00:07:27.060> and<00:07:27.300> we<00:07:27.419> want<00:07:27.539> to 00:07:27.650 --> 00:07:27.660 align:start position:0% um to register itself and we want to 00:07:27.660 --> 00:07:30.050 align:start position:0% um to register itself and we want to update<00:07:27.840> the<00:07:27.960> mapping<00:07:28.259> basically<00:07:28.620> so<00:07:29.160> let's 00:07:30.050 --> 00:07:30.060 align:start position:0% update the mapping basically so let's 00:07:30.060 --> 00:07:32.210 align:start position:0% update the mapping basically so let's um<00:07:30.599> let's<00:07:30.599> go<00:07:31.139> for<00:07:31.259> it 00:07:32.210 --> 00:07:32.220 align:start position:0% um let's go for it 00:07:32.220 --> 00:07:34.010 align:start position:0% um let's go for it do<00:07:32.580> okay 00:07:34.010 --> 00:07:34.020 align:start position:0% do okay 00:07:34.020 --> 00:07:34.969 align:start position:0% do okay um 00:07:34.969 --> 00:07:34.979 align:start position:0% um 00:07:34.979 --> 00:07:38.570 align:start position:0% um so<00:07:35.940> we<00:07:36.539> are<00:07:36.660> going<00:07:36.900> to<00:07:37.319> kind<00:07:38.039> of<00:07:38.160> assume<00:07:38.460> that 00:07:38.570 --> 00:07:38.580 align:start position:0% so we are going to kind of assume that 00:07:38.580 --> 00:07:40.010 align:start position:0% so we are going to kind of assume that the<00:07:38.699> caller<00:07:38.940> is<00:07:39.060> a<00:07:39.180> token<00:07:39.479> if<00:07:39.599> it's<00:07:39.720> not<00:07:39.840> that's 00:07:40.010 --> 00:07:40.020 align:start position:0% the caller is a token if it's not that's 00:07:40.020 --> 00:07:42.230 align:start position:0% the caller is a token if it's not that's fine<00:07:40.259> it<00:07:40.440> won't<00:07:40.560> affect<00:07:40.740> anything<00:07:40.979> else 00:07:42.230 --> 00:07:42.240 align:start position:0% fine it won't affect anything else 00:07:42.240 --> 00:07:42.950 align:start position:0% fine it won't affect anything else um 00:07:42.950 --> 00:07:42.960 align:start position:0% um 00:07:42.960 --> 00:07:44.689 align:start position:0% um so<00:07:43.319> we'll<00:07:43.560> call<00:07:43.680> this<00:07:43.800> L1<00:07:44.099> token<00:07:44.400> then<00:07:44.580> just 00:07:44.689 --> 00:07:44.699 align:start position:0% so we'll call this L1 token then just 00:07:44.699 --> 00:07:45.710 align:start position:0% so we'll call this L1 token then just grab<00:07:44.819> the<00:07:44.940> address<00:07:45.120> because<00:07:45.360> we're<00:07:45.599> going<00:07:45.660> to 00:07:45.710 --> 00:07:45.720 align:start position:0% grab the address because we're going to 00:07:45.720 --> 00:07:47.870 align:start position:0% grab the address because we're going to use<00:07:45.840> this<00:07:45.960> in<00:07:46.139> a<00:07:46.259> few<00:07:46.319> places 00:07:47.870 --> 00:07:47.880 align:start position:0% use this in a few places 00:07:47.880 --> 00:07:49.309 align:start position:0% use this in a few places hopefully<00:07:48.240> my<00:07:48.539> hands<00:07:48.720> get<00:07:48.840> slightly<00:07:49.199> less 00:07:49.309 --> 00:07:49.319 align:start position:0% hopefully my hands get slightly less 00:07:49.319 --> 00:07:50.870 align:start position:0% hopefully my hands get slightly less shaky<00:07:49.740> in<00:07:49.860> a<00:07:49.979> second 00:07:50.870 --> 00:07:50.880 align:start position:0% shaky in a second 00:07:50.880 --> 00:07:51.529 align:start position:0% shaky in a second um 00:07:51.529 --> 00:07:51.539 align:start position:0% um 00:07:51.539 --> 00:07:52.850 align:start position:0% um so<00:07:51.840> there's<00:07:51.900> the<00:07:52.080> L1<00:07:52.319> token<00:07:52.560> address<00:07:52.680> that 00:07:52.850 --> 00:07:52.860 align:start position:0% so there's the L1 token address that 00:07:52.860 --> 00:07:54.350 align:start position:0% so there's the L1 token address that made<00:07:53.039> this<00:07:53.220> call<00:07:53.340> and<00:07:53.639> now<00:07:53.819> we<00:07:53.940> just<00:07:54.060> update 00:07:54.350 --> 00:07:54.360 align:start position:0% made this call and now we just update 00:07:54.360 --> 00:07:55.730 align:start position:0% made this call and now we just update our<00:07:54.539> mapping 00:07:55.730 --> 00:07:55.740 align:start position:0% our mapping 00:07:55.740 --> 00:07:57.409 align:start position:0% our mapping um<00:07:56.220> there'll<00:07:56.520> be<00:07:56.639> a<00:07:56.759> check<00:07:56.880> we<00:07:57.000> want<00:07:57.120> to<00:07:57.180> do<00:07:57.300> but 00:07:57.409 --> 00:07:57.419 align:start position:0% um there'll be a check we want to do but 00:07:57.419 --> 00:07:58.490 align:start position:0% um there'll be a check we want to do but let's<00:07:57.539> just<00:07:57.660> let's<00:07:57.840> just<00:07:57.960> get<00:07:58.080> this<00:07:58.139> code<00:07:58.319> in 00:07:58.490 --> 00:07:58.500 align:start position:0% let's just let's just get this code in 00:07:58.500 --> 00:07:59.390 align:start position:0% let's just let's just get this code in first 00:07:59.390 --> 00:07:59.400 align:start position:0% first 00:07:59.400 --> 00:08:02.150 align:start position:0% first L1<00:07:59.819> to<00:07:59.940> LG<00:08:00.180> token<00:08:00.599> okay<00:08:00.960> the<00:08:01.199> L1<00:08:01.500> token<00:08:01.800> mapped 00:08:02.150 --> 00:08:02.160 align:start position:0% L1 to LG token okay the L1 token mapped 00:08:02.160 --> 00:08:02.870 align:start position:0% L1 to LG token okay the L1 token mapped to 00:08:02.870 --> 00:08:02.880 align:start position:0% to 00:08:02.880 --> 00:08:06.110 align:start position:0% to the<00:08:03.240> L2<00:08:03.539> address<00:08:03.780> provided 00:08:06.110 --> 00:08:06.120 align:start position:0% the L2 address provided 00:08:06.120 --> 00:08:07.370 align:start position:0% the L2 address provided cool 00:08:07.370 --> 00:08:07.380 align:start position:0% cool 00:08:07.380 --> 00:08:08.689 align:start position:0% cool that<00:08:07.680> was<00:08:07.800> easy 00:08:08.689 --> 00:08:08.699 align:start position:0% that was easy 00:08:08.699 --> 00:08:10.670 align:start position:0% that was easy um<00:08:08.819> now 00:08:10.670 --> 00:08:10.680 align:start position:0% um now 00:08:10.680 --> 00:08:13.249 align:start position:0% um now um<00:08:10.819> one<00:08:11.819> question<00:08:12.000> we<00:08:12.240> should<00:08:12.360> ask<00:08:12.539> here<00:08:12.780> is 00:08:13.249 --> 00:08:13.259 align:start position:0% um one question we should ask here is 00:08:13.259 --> 00:08:15.050 align:start position:0% um one question we should ask here is should<00:08:13.620> you<00:08:13.800> be<00:08:13.919> able<00:08:14.220> should<00:08:14.580> the<00:08:14.699> token<00:08:14.940> be 00:08:15.050 --> 00:08:15.060 align:start position:0% should you be able should the token be 00:08:15.060 --> 00:08:16.490 align:start position:0% should you be able should the token be able<00:08:15.180> to<00:08:15.300> sort<00:08:15.479> of<00:08:15.539> re-register<00:08:16.020> to<00:08:16.199> a<00:08:16.380> new 00:08:16.490 --> 00:08:16.500 align:start position:0% able to sort of re-register to a new 00:08:16.500 --> 00:08:17.469 align:start position:0% able to sort of re-register to a new address 00:08:17.469 --> 00:08:17.479 align:start position:0% address 00:08:17.479 --> 00:08:20.089 align:start position:0% address and<00:08:18.479> we<00:08:18.660> can<00:08:18.840> decide<00:08:19.319> you<00:08:19.560> know<00:08:19.620> for<00:08:19.860> the<00:08:19.919> sake 00:08:20.089 --> 00:08:20.099 align:start position:0% and we can decide you know for the sake 00:08:20.099 --> 00:08:23.210 align:start position:0% and we can decide you know for the sake of<00:08:20.220> Simplicity<00:08:20.759> let's<00:08:21.300> say<00:08:21.539> no<00:08:21.919> this<00:08:22.919> is<00:08:23.039> kind 00:08:23.210 --> 00:08:23.220 align:start position:0% of Simplicity let's say no this is kind 00:08:23.220 --> 00:08:25.430 align:start position:0% of Simplicity let's say no this is kind of<00:08:23.340> by<00:08:23.580> the<00:08:23.759> way<00:08:23.819> this<00:08:24.259> this<00:08:25.259> whole 00:08:25.430 --> 00:08:25.440 align:start position:0% of by the way this this whole 00:08:25.440 --> 00:08:26.689 align:start position:0% of by the way this this whole architecture<00:08:25.800> is<00:08:25.919> meant<00:08:26.160> to<00:08:26.220> be<00:08:26.280> as<00:08:26.400> simple<00:08:26.520> as 00:08:26.689 --> 00:08:26.699 align:start position:0% architecture is meant to be as simple as 00:08:26.699 --> 00:08:28.189 align:start position:0% architecture is meant to be as simple as possible<00:08:27.000> kind<00:08:27.240> of<00:08:27.360> minimum<00:08:27.539> viable<00:08:27.900> token 00:08:28.189 --> 00:08:28.199 align:start position:0% possible kind of minimum viable token 00:08:28.199 --> 00:08:29.869 align:start position:0% possible kind of minimum viable token Bridge<00:08:28.319> so<00:08:28.860> we<00:08:29.160> can<00:08:29.340> kind<00:08:29.400> of<00:08:29.520> focus<00:08:29.639> on<00:08:29.819> the 00:08:29.869 --> 00:08:29.879 align:start position:0% Bridge so we can kind of focus on the 00:08:29.879 --> 00:08:30.890 align:start position:0% Bridge so we can kind of focus on the cross<00:08:30.000> chain<00:08:30.180> messaging<00:08:30.599> stuff<00:08:30.780> and 00:08:30.890 --> 00:08:30.900 align:start position:0% cross chain messaging stuff and 00:08:30.900 --> 00:08:32.990 align:start position:0% cross chain messaging stuff and understand<00:08:31.020> what's<00:08:31.319> going<00:08:31.560> on<00:08:31.680> so<00:08:32.520> if<00:08:32.880> the 00:08:32.990 --> 00:08:33.000 align:start position:0% understand what's going on so if the 00:08:33.000 --> 00:08:34.310 align:start position:0% understand what's going on so if the Gateway<00:08:33.300> you<00:08:33.539> know<00:08:33.599> if<00:08:33.659> the<00:08:33.779> token's<00:08:34.140> allowed 00:08:34.310 --> 00:08:34.320 align:start position:0% Gateway you know if the token's allowed 00:08:34.320 --> 00:08:35.930 align:start position:0% Gateway you know if the token's allowed to<00:08:34.440> sort<00:08:34.560> of<00:08:34.680> change<00:08:34.800> itself<00:08:35.159> to<00:08:35.339> address<00:08:35.580> that 00:08:35.930 --> 00:08:35.940 align:start position:0% to sort of change itself to address that 00:08:35.940 --> 00:08:38.690 align:start position:0% to sort of change itself to address that could<00:08:36.120> make<00:08:36.419> our<00:08:36.659> assumptions<00:08:37.080> kind<00:08:37.260> of<00:08:37.380> weird 00:08:38.690 --> 00:08:38.700 align:start position:0% could make our assumptions kind of weird 00:08:38.700 --> 00:08:40.850 align:start position:0% could make our assumptions kind of weird um<00:08:38.760> but<00:08:39.360> another<00:08:39.719> thing<00:08:39.959> we<00:08:40.140> might<00:08:40.380> want<00:08:40.680> to 00:08:40.850 --> 00:08:40.860 align:start position:0% um but another thing we might want to 00:08:40.860 --> 00:08:42.529 align:start position:0% um but another thing we might want to ask<00:08:40.979> is<00:08:41.159> can<00:08:41.339> it<00:08:41.459> re-register<00:08:41.880> itself<00:08:42.180> to<00:08:42.419> the 00:08:42.529 --> 00:08:42.539 align:start position:0% ask is can it re-register itself to the 00:08:42.539 --> 00:08:44.510 align:start position:0% ask is can it re-register itself to the Sam<00:08:42.659> address<00:08:42.959> and<00:08:43.560> we<00:08:43.740> actually<00:08:43.800> do<00:08:44.039> want<00:08:44.279> that 00:08:44.510 --> 00:08:44.520 align:start position:0% Sam address and we actually do want that 00:08:44.520 --> 00:08:47.030 align:start position:0% Sam address and we actually do want that and<00:08:45.240> I'll<00:08:45.360> explain<00:08:45.540> why<00:08:45.779> but<00:08:46.560> first<00:08:46.740> let<00:08:46.980> me 00:08:47.030 --> 00:08:47.040 align:start position:0% and I'll explain why but first let me 00:08:47.040 --> 00:08:49.130 align:start position:0% and I'll explain why but first let me let<00:08:47.220> me<00:08:47.339> write<00:08:47.519> this<00:08:47.640> check<00:08:47.820> so<00:08:48.480> um 00:08:49.130 --> 00:08:49.140 align:start position:0% let me write this check so um 00:08:49.140 --> 00:08:52.130 align:start position:0% let me write this check so um if<00:08:50.040> the<00:08:50.880> um 00:08:52.130 --> 00:08:52.140 align:start position:0% if the um 00:08:52.140 --> 00:08:54.650 align:start position:0% if the um so<00:08:52.500> we're<00:08:52.620> going<00:08:52.740> to<00:08:52.860> check 00:08:54.650 --> 00:08:54.660 align:start position:0% so we're going to check 00:08:54.660 --> 00:08:57.590 align:start position:0% so we're going to check um 00:08:57.590 --> 00:08:57.600 align:start position:0% 00:08:57.600 --> 00:09:00.050 align:start position:0% um<00:08:57.720> actually<00:08:57.899> let's<00:08:58.140> do<00:08:58.320> this<00:08:58.440> yeah 00:09:00.050 --> 00:09:00.060 align:start position:0% um actually let's do this yeah 00:09:00.060 --> 00:09:01.730 align:start position:0% um actually let's do this yeah so<00:09:00.420> before<00:09:00.540> we<00:09:00.720> register<00:09:01.019> it<00:09:01.260> let's<00:09:01.380> grab 00:09:01.730 --> 00:09:01.740 align:start position:0% so before we register it let's grab 00:09:01.740 --> 00:09:06.170 align:start position:0% so before we register it let's grab we'll<00:09:02.040> call<00:09:02.220> it<00:09:02.339> like<00:09:02.580> current<00:09:03.360> L2<00:09:04.080> address 00:09:06.170 --> 00:09:06.180 align:start position:0% we'll call it like current L2 address 00:09:06.180 --> 00:09:09.530 align:start position:0% we'll call it like current L2 address and<00:09:06.480> we'll<00:09:06.600> grab<00:09:06.779> it<00:09:06.899> from<00:09:07.019> the<00:09:07.140> mapping 00:09:09.530 --> 00:09:09.540 align:start position:0% 00:09:09.540 --> 00:09:10.970 align:start position:0% so<00:09:09.899> before<00:09:10.019> you<00:09:10.200> registered<00:09:10.560> it<00:09:10.680> here's<00:09:10.920> what 00:09:10.970 --> 00:09:10.980 align:start position:0% so before you registered it here's what 00:09:10.980 --> 00:09:13.850 align:start position:0% so before you registered it here's what the<00:09:11.100> address<00:09:11.220> was 00:09:13.850 --> 00:09:13.860 align:start position:0% 00:09:13.860 --> 00:09:15.769 align:start position:0% yes 00:09:15.769 --> 00:09:15.779 align:start position:0% yes 00:09:15.779 --> 00:09:17.090 align:start position:0% yes and<00:09:16.080> we're<00:09:16.260> going<00:09:16.380> to<00:09:16.440> say<00:09:16.500> if<00:09:16.680> it's<00:09:16.800> all<00:09:16.860> we're 00:09:17.090 --> 00:09:17.100 align:start position:0% and we're going to say if it's all we're 00:09:17.100 --> 00:09:17.870 align:start position:0% and we're going to say if it's all we're going<00:09:17.220> to<00:09:17.279> check<00:09:17.399> to<00:09:17.519> see<00:09:17.580> if<00:09:17.640> it's<00:09:17.760> already 00:09:17.870 --> 00:09:17.880 align:start position:0% going to check to see if it's already 00:09:17.880 --> 00:09:27.170 align:start position:0% going to check to see if it's already registered 00:09:27.170 --> 00:09:27.180 align:start position:0% 00:09:27.180 --> 00:09:32.810 align:start position:0% um 00:09:32.810 --> 00:09:32.820 align:start position:0% 00:09:32.820 --> 00:09:35.269 align:start position:0% something<00:09:33.420> I'll<00:09:33.779> figure<00:09:33.899> that<00:09:34.080> out<00:09:34.440> um<00:09:34.440> check 00:09:35.269 --> 00:09:35.279 align:start position:0% something I'll figure that out um check 00:09:35.279 --> 00:09:36.170 align:start position:0% something I'll figure that out um check and<00:09:35.399> see<00:09:35.459> if<00:09:35.519> it's<00:09:35.640> already<00:09:35.760> registered 00:09:36.170 --> 00:09:36.180 align:start position:0% and see if it's already registered 00:09:36.180 --> 00:09:38.449 align:start position:0% and see if it's already registered Excuse<00:09:36.779> me<00:09:36.899> yes<00:09:37.260> I<00:09:37.500> have<00:09:37.800> a<00:09:37.980> more<00:09:38.160> high<00:09:38.339> level 00:09:38.449 --> 00:09:38.459 align:start position:0% Excuse me yes I have a more high level 00:09:38.459 --> 00:09:41.090 align:start position:0% Excuse me yes I have a more high level abstract<00:09:39.000> question<00:09:39.300> here<00:09:39.720> but<00:09:40.100> specifically 00:09:41.090 --> 00:09:41.100 align:start position:0% abstract question here but specifically 00:09:41.100 --> 00:09:42.650 align:start position:0% abstract question here but specifically here<00:09:41.339> are<00:09:41.519> you<00:09:41.700> require<00:09:41.820> for<00:09:42.120> nft<00:09:42.360> smart 00:09:42.650 --> 00:09:42.660 align:start position:0% here are you require for nft smart 00:09:42.660 --> 00:09:45.350 align:start position:0% here are you require for nft smart contract<00:09:43.019> to<00:09:43.920> um<00:09:43.920> be<00:09:44.580> compatible<00:09:44.940> with<00:09:45.240> your 00:09:45.350 --> 00:09:45.360 align:start position:0% contract to um be compatible with your 00:09:45.360 --> 00:09:46.610 align:start position:0% contract to um be compatible with your Bridge<00:09:45.480> fundamentally<00:09:46.019> because<00:09:46.260> they<00:09:46.440> need 00:09:46.610 --> 00:09:46.620 align:start position:0% Bridge fundamentally because they need 00:09:46.620 --> 00:09:48.829 align:start position:0% Bridge fundamentally because they need to<00:09:46.680> self-register<00:09:47.100> right<00:09:47.459> yes<00:09:47.880> and<00:09:48.300> if<00:09:48.480> I'm<00:09:48.720> an 00:09:48.829 --> 00:09:48.839 align:start position:0% to self-register right yes and if I'm an 00:09:48.839 --> 00:09:51.050 align:start position:0% to self-register right yes and if I'm an nft<00:09:49.080> publisher<00:09:49.680> why<00:09:49.920> do<00:09:50.100> I<00:09:50.220> need<00:09:50.339> a<00:09:50.459> bridge<00:09:50.580> I 00:09:51.050 --> 00:09:51.060 align:start position:0% nft publisher why do I need a bridge I 00:09:51.060 --> 00:09:52.610 align:start position:0% nft publisher why do I need a bridge I can<00:09:51.180> just<00:09:51.300> click<00:09:51.600> create<00:09:51.779> a<00:09:51.959> button<00:09:52.260> on<00:09:52.440> my 00:09:52.610 --> 00:09:52.620 align:start position:0% can just click create a button on my 00:09:52.620 --> 00:09:54.350 align:start position:0% can just click create a button on my website<00:09:52.860> like<00:09:53.040> burn<00:09:53.279> photo<00:09:53.519> can<00:09:53.880> and<00:09:54.240> then 00:09:54.350 --> 00:09:54.360 align:start position:0% website like burn photo can and then 00:09:54.360 --> 00:09:55.670 align:start position:0% website like burn photo can and then give<00:09:54.480> a<00:09:54.660> tokens<00:09:54.959> when<00:09:55.140> you<00:09:55.200> buy<00:09:55.320> no<00:09:55.560> Bridge 00:09:55.670 --> 00:09:55.680 align:start position:0% give a tokens when you buy no Bridge 00:09:55.680 --> 00:09:57.769 align:start position:0% give a tokens when you buy no Bridge needed<00:09:55.980> uh<00:09:56.820> you<00:09:57.060> could<00:09:57.120> in<00:09:57.300> that<00:09:57.420> case<00:09:57.540> it'll 00:09:57.769 --> 00:09:57.779 align:start position:0% needed uh you could in that case it'll 00:09:57.779 --> 00:09:59.269 align:start position:0% needed uh you could in that case it'll be<00:09:57.839> trusted<00:09:58.140> right<00:09:58.380> so<00:09:58.500> this<00:09:58.680> we<00:09:58.860> want<00:09:58.980> it<00:09:59.100> yeah 00:09:59.269 --> 00:09:59.279 align:start position:0% be trusted right so this we want it yeah 00:09:59.279 --> 00:10:01.310 align:start position:0% be trusted right so this we want it yeah but<00:09:59.399> nft<00:09:59.700> fundamentally<00:10:00.300> our<00:10:00.660> tokenization 00:10:01.310 --> 00:10:01.320 align:start position:0% but nft fundamentally our tokenization 00:10:01.320 --> 00:10:03.050 align:start position:0% but nft fundamentally our tokenization of<00:10:01.500> Rights<00:10:01.800> so<00:10:01.980> fundamentally<00:10:02.519> nft<00:10:02.820> are 00:10:03.050 --> 00:10:03.060 align:start position:0% of Rights so fundamentally nft are 00:10:03.060 --> 00:10:04.850 align:start position:0% of Rights so fundamentally nft are trusted<00:10:03.420> well<00:10:04.019> if<00:10:04.140> we<00:10:04.260> want<00:10:04.380> the<00:10:04.500> bridging 00:10:04.850 --> 00:10:04.860 align:start position:0% trusted well if we want the bridging 00:10:04.860 --> 00:10:06.470 align:start position:0% trusted well if we want the bridging process<00:10:05.100> itself<00:10:05.459> to<00:10:05.640> be<00:10:05.700> trustless<00:10:06.120> let's<00:10:06.360> say 00:10:06.470 --> 00:10:06.480 align:start position:0% process itself to be trustless let's say 00:10:06.480 --> 00:10:08.090 align:start position:0% process itself to be trustless let's say right<00:10:06.660> so<00:10:06.899> correct<00:10:07.380> let's<00:10:07.620> put<00:10:07.800> it<00:10:07.860> that<00:10:07.980> way 00:10:08.090 --> 00:10:08.100 align:start position:0% right so correct let's put it that way 00:10:08.100 --> 00:10:09.230 align:start position:0% right so correct let's put it that way right<00:10:08.220> so<00:10:08.339> the<00:10:08.459> bridging<00:10:08.760> so<00:10:08.880> yes<00:10:09.000> whatever 00:10:09.230 --> 00:10:09.240 align:start position:0% right so the bridging so yes whatever 00:10:09.240 --> 00:10:10.850 align:start position:0% right so the bridging so yes whatever trust<00:10:09.600> assumptions<00:10:09.959> are<00:10:10.080> within<00:10:10.320> well<00:10:10.560> if 00:10:10.850 --> 00:10:10.860 align:start position:0% trust assumptions are within well if 00:10:10.860 --> 00:10:13.310 align:start position:0% trust assumptions are within well if that's<00:10:11.100> as<00:10:11.339> last<00:10:11.820> as<00:10:12.120> for<00:10:12.540> cross-pressession 00:10:13.310 --> 00:10:13.320 align:start position:0% that's as last as for cross-pressession 00:10:13.320 --> 00:10:15.110 align:start position:0% that's as last as for cross-pressession yes<00:10:13.620> exactly<00:10:14.220> so<00:10:14.339> again<00:10:14.459> we're<00:10:14.640> treating<00:10:15.000> the 00:10:15.110 --> 00:10:15.120 align:start position:0% yes exactly so again we're treating the 00:10:15.120 --> 00:10:18.490 align:start position:0% yes exactly so again we're treating the L1<00:10:15.360> contract<00:10:15.720> as<00:10:15.899> the<00:10:16.019> source<00:10:16.200> assuming<00:10:16.680> yeah 00:10:18.490 --> 00:10:18.500 align:start position:0% L1 contract as the source assuming yeah 00:10:18.500 --> 00:10:20.630 align:start position:0% L1 contract as the source assuming yeah it's<00:10:19.500> a<00:10:19.620> good<00:10:19.740> question<00:10:19.860> so<00:10:20.040> L1<00:10:20.279> contract<00:10:20.580> is 00:10:20.630 --> 00:10:20.640 align:start position:0% it's a good question so L1 contract is 00:10:20.640 --> 00:10:21.650 align:start position:0% it's a good question so L1 contract is source<00:10:20.880> of<00:10:20.940> truth<00:10:21.120> whatever<00:10:21.300> trust 00:10:21.650 --> 00:10:21.660 align:start position:0% source of truth whatever trust 00:10:21.660 --> 00:10:23.210 align:start position:0% source of truth whatever trust assumptions<00:10:21.959> it<00:10:22.140> has<00:10:22.380> we're<00:10:22.860> sticking<00:10:23.160> with 00:10:23.210 --> 00:10:23.220 align:start position:0% assumptions it has we're sticking with 00:10:23.220 --> 00:10:24.470 align:start position:0% assumptions it has we're sticking with but<00:10:23.399> the<00:10:23.519> bridge<00:10:23.640> itself<00:10:23.940> the<00:10:24.180> bridging 00:10:24.470 --> 00:10:24.480 align:start position:0% but the bridge itself the bridging 00:10:24.480 --> 00:10:27.050 align:start position:0% but the bridge itself the bridging processes<00:10:25.279> compatible<00:10:26.279> with<00:10:26.519> a<00:10:26.760> legacy 00:10:27.050 --> 00:10:27.060 align:start position:0% processes compatible with a legacy 00:10:27.060 --> 00:10:28.850 align:start position:0% processes compatible with a legacy contract<00:10:27.420> it's<00:10:27.720> only<00:10:27.899> for<00:10:28.200> upgradable 00:10:28.850 --> 00:10:28.860 align:start position:0% contract it's only for upgradable 00:10:28.860 --> 00:10:30.590 align:start position:0% contract it's only for upgradable contracts<00:10:29.339> or<00:10:29.580> new<00:10:29.820> contracts<00:10:30.240> specifically 00:10:30.590 --> 00:10:30.600 align:start position:0% contracts or new contracts specifically 00:10:30.600 --> 00:10:31.610 align:start position:0% contracts or new contracts specifically built<00:10:30.899> for<00:10:30.959> interact<00:10:31.260> with<00:10:31.380> this<00:10:31.440> bridge 00:10:31.610 --> 00:10:31.620 align:start position:0% built for interact with this bridge 00:10:31.620 --> 00:10:33.230 align:start position:0% built for interact with this bridge that's<00:10:31.920> yeah<00:10:32.279> that's<00:10:32.519> right<00:10:32.700> if<00:10:33.000> you<00:10:33.120> have<00:10:33.180> an 00:10:33.230 --> 00:10:33.240 align:start position:0% that's yeah that's right if you have an 00:10:33.240 --> 00:10:34.550 align:start position:0% that's yeah that's right if you have an old<00:10:33.300> NFTA<00:10:33.779> for<00:10:33.839> example<00:10:34.019> what<00:10:34.200> you<00:10:34.320> could<00:10:34.440> do 00:10:34.550 --> 00:10:34.560 align:start position:0% old NFTA for example what you could do 00:10:34.560 --> 00:10:36.410 align:start position:0% old NFTA for example what you could do is<00:10:34.620> deploy<00:10:34.920> a<00:10:35.100> new<00:10:35.279> contract<00:10:35.760> that's<00:10:36.060> that's 00:10:36.410 --> 00:10:36.420 align:start position:0% is deploy a new contract that's that's 00:10:36.420 --> 00:10:38.269 align:start position:0% is deploy a new contract that's that's kind<00:10:36.660> of<00:10:36.720> a<00:10:36.779> wrapper<00:10:37.080> and<00:10:37.320> use<00:10:37.500> that<00:10:37.680> one<00:10:38.100> yes 00:10:38.269 --> 00:10:38.279 align:start position:0% kind of a wrapper and use that one yes 00:10:38.279 --> 00:10:39.730 align:start position:0% kind of a wrapper and use that one yes exactly 00:10:39.730 --> 00:10:39.740 align:start position:0% exactly 00:10:39.740 --> 00:10:42.410 align:start position:0% exactly okay<00:10:40.740> so<00:10:40.980> in<00:10:41.160> in<00:10:41.459> terms<00:10:41.760> of<00:10:41.820> in<00:10:42.180> terms<00:10:42.360> of 00:10:42.410 --> 00:10:42.420 align:start position:0% okay so in in terms of in terms of 00:10:42.420 --> 00:10:43.670 align:start position:0% okay so in in terms of in terms of re-registering<00:10:43.080> so<00:10:43.200> if<00:10:43.320> it's<00:10:43.500> already 00:10:43.670 --> 00:10:43.680 align:start position:0% re-registering so if it's already 00:10:43.680 --> 00:10:45.590 align:start position:0% re-registering so if it's already registered<00:10:44.100> we're<00:10:44.279> going<00:10:44.399> to<00:10:44.519> actually<00:10:44.700> allow 00:10:45.590 --> 00:10:45.600 align:start position:0% registered we're going to actually allow 00:10:45.600 --> 00:10:46.730 align:start position:0% registered we're going to actually allow it<00:10:45.660> to<00:10:45.779> register<00:10:46.019> again<00:10:46.260> as<00:10:46.500> long<00:10:46.560> as<00:10:46.620> it's 00:10:46.730 --> 00:10:46.740 align:start position:0% it to register again as long as it's 00:10:46.740 --> 00:10:48.590 align:start position:0% it to register again as long as it's registering<00:10:47.160> to<00:10:47.339> the<00:10:47.579> same<00:10:47.760> address 00:10:48.590 --> 00:10:48.600 align:start position:0% registering to the same address 00:10:48.600 --> 00:10:51.110 align:start position:0% registering to the same address um<00:10:48.660> as<00:10:48.839> strange<00:10:49.079> as<00:10:49.200> that<00:10:49.380> might<00:10:49.620> sound 00:10:51.110 --> 00:10:51.120 align:start position:0% um as strange as that might sound 00:10:51.120 --> 00:10:52.970 align:start position:0% um as strange as that might sound um<00:10:51.240> so<00:10:51.660> we're<00:10:51.779> going<00:10:51.899> to<00:10:51.959> acquire<00:10:52.320> that<00:10:52.560> the 00:10:52.970 --> 00:10:52.980 align:start position:0% um so we're going to acquire that the 00:10:52.980 --> 00:10:56.449 align:start position:0% um so we're going to acquire that the current<00:10:53.339> address<00:10:54.079> is<00:10:55.079> equal<00:10:55.260> to<00:10:55.380> the<00:10:55.500> new<00:10:55.620> one 00:10:56.449 --> 00:10:56.459 align:start position:0% current address is equal to the new one 00:10:56.459 --> 00:10:57.889 align:start position:0% current address is equal to the new one and<00:10:56.760> the<00:10:56.880> reason<00:10:57.000> we<00:10:57.180> want<00:10:57.300> to<00:10:57.420> do<00:10:57.540> this<00:10:57.660> as 00:10:57.889 --> 00:10:57.899 align:start position:0% and the reason we want to do this as 00:10:57.899 --> 00:10:59.030 align:start position:0% and the reason we want to do this as we'll<00:10:58.079> see<00:10:58.200> is<00:10:58.260> we're<00:10:58.440> going<00:10:58.560> to<00:10:58.620> be<00:10:58.680> sending<00:10:58.980> a 00:10:59.030 --> 00:10:59.040 align:start position:0% we'll see is we're going to be sending a 00:10:59.040 --> 00:11:00.949 align:start position:0% we'll see is we're going to be sending a cross<00:10:59.160> chain<00:10:59.339> message 00:11:00.949 --> 00:11:00.959 align:start position:0% cross chain message 00:11:00.959 --> 00:11:54.889 align:start position:0% cross chain message um 00:11:54.889 --> 00:11:54.899 align:start position:0% 00:11:54.899 --> 00:11:57.530 align:start position:0% I'll<00:11:55.260> just<00:11:55.380> keep<00:11:55.560> shouting<00:11:56.339> okay<00:11:57.240> um<00:11:57.300> let<00:11:57.420> me 00:11:57.530 --> 00:11:57.540 align:start position:0% I'll just keep shouting okay um let me 00:11:57.540 --> 00:11:58.310 align:start position:0% I'll just keep shouting okay um let me know 00:11:58.310 --> 00:11:58.320 align:start position:0% know 00:11:58.320 --> 00:11:59.150 align:start position:0% know um 00:11:59.150 --> 00:11:59.160 align:start position:0% um 00:11:59.160 --> 00:12:02.030 align:start position:0% um the<00:11:59.880> okay<00:12:00.120> so<00:12:00.300> we<00:12:00.420> need<00:12:00.540> to<00:12:00.660> know<00:12:00.839> the<00:12:01.440> address 00:12:02.030 --> 00:12:02.040 align:start position:0% the okay so we need to know the address 00:12:02.040 --> 00:12:03.949 align:start position:0% the okay so we need to know the address that<00:12:02.880> um<00:12:02.880> at<00:12:03.120> which<00:12:03.240> we<00:12:03.420> want<00:12:03.540> to<00:12:03.660> trigger<00:12:03.839> a 00:12:03.949 --> 00:12:03.959 align:start position:0% that um at which we want to trigger a 00:12:03.959 --> 00:12:05.269 align:start position:0% that um at which we want to trigger a message<00:12:04.140> on<00:12:04.320> the<00:12:04.380> L2<00:12:04.680> side<00:12:04.920> which<00:12:05.100> is<00:12:05.160> going<00:12:05.279> to 00:12:05.269 --> 00:12:05.279 align:start position:0% message on the L2 side which is going to 00:12:05.279 --> 00:12:07.190 align:start position:0% message on the L2 side which is going to be<00:12:05.399> our<00:12:05.459> L2<00:12:05.760> nft<00:12:06.000> Gateway<00:12:06.420> which<00:12:06.959> we<00:12:07.140> have 00:12:07.190 --> 00:12:07.200 align:start position:0% be our L2 nft Gateway which we have 00:12:07.200 --> 00:12:09.410 align:start position:0% be our L2 nft Gateway which we have stored<00:12:07.560> as<00:12:07.800> counterpart<00:12:08.339> Gateway<00:12:08.700> and<00:12:09.360> then 00:12:09.410 --> 00:12:09.420 align:start position:0% stored as counterpart Gateway and then 00:12:09.420 --> 00:12:10.790 align:start position:0% stored as counterpart Gateway and then we<00:12:09.540> also<00:12:09.720> need<00:12:09.839> to<00:12:09.959> encode<00:12:10.320> the<00:12:10.560> actual 00:12:10.790 --> 00:12:10.800 align:start position:0% we also need to encode the actual 00:12:10.800 --> 00:12:12.829 align:start position:0% we also need to encode the actual message<00:12:10.980> we're<00:12:11.220> calling<00:12:11.640> right<00:12:12.000> so<00:12:12.240> on<00:12:12.420> the<00:12:12.540> L2 00:12:12.829 --> 00:12:12.839 align:start position:0% message we're calling right so on the L2 00:12:12.839 --> 00:12:14.810 align:start position:0% message we're calling right so on the L2 side<00:12:13.079> just<00:12:13.380> peeking<00:12:13.740> ahead<00:12:13.980> the<00:12:14.459> message<00:12:14.579> that 00:12:14.810 --> 00:12:14.820 align:start position:0% side just peeking ahead the message that 00:12:14.820 --> 00:12:16.190 align:start position:0% side just peeking ahead the message that we're<00:12:14.940> going<00:12:15.060> to<00:12:15.180> be<00:12:15.240> calling 00:12:16.190 --> 00:12:16.200 align:start position:0% we're going to be calling 00:12:16.200 --> 00:12:17.210 align:start position:0% we're going to be calling just<00:12:16.380> because<00:12:16.500> we<00:12:16.680> have<00:12:16.800> the<00:12:16.860> name<00:12:17.040> here 00:12:17.210 --> 00:12:17.220 align:start position:0% just because we have the name here 00:12:17.220 --> 00:12:20.269 align:start position:0% just because we have the name here finalize<00:12:18.000> registration<00:12:18.420> from<00:12:18.660> L2<00:12:19.079> we<00:12:20.040> need<00:12:20.160> to 00:12:20.269 --> 00:12:20.279 align:start position:0% finalize registration from L2 we need to 00:12:20.279 --> 00:12:21.829 align:start position:0% finalize registration from L2 we need to sort<00:12:20.459> of<00:12:20.519> encode<00:12:20.760> that<00:12:20.940> and<00:12:21.120> specify<00:12:21.540> that 00:12:21.829 --> 00:12:21.839 align:start position:0% sort of encode that and specify that 00:12:21.839 --> 00:12:23.509 align:start position:0% sort of encode that and specify that that's<00:12:22.019> the<00:12:22.260> that's<00:12:22.800> the<00:12:22.920> method<00:12:23.160> we<00:12:23.279> want<00:12:23.459> to 00:12:23.509 --> 00:12:23.519 align:start position:0% that's the that's the method we want to 00:12:23.519 --> 00:12:26.329 align:start position:0% that's the that's the method we want to call<00:12:23.640> so<00:12:24.540> let's<00:12:24.779> uh<00:12:25.140> let's<00:12:25.380> do<00:12:25.620> that<00:12:25.980> and 00:12:26.329 --> 00:12:26.339 align:start position:0% call so let's uh let's do that and 00:12:26.339 --> 00:12:28.009 align:start position:0% call so let's uh let's do that and encode<00:12:26.640> that<00:12:26.940> data<00:12:27.240> and<00:12:27.720> we're<00:12:27.839> going<00:12:27.959> to 00:12:28.009 --> 00:12:28.019 align:start position:0% encode that data and we're going to 00:12:28.019 --> 00:12:29.090 align:start position:0% encode that data and we're going to actually<00:12:28.079> just<00:12:28.260> do<00:12:28.380> that<00:12:28.560> in<00:12:28.740> a<00:12:28.860> separate 00:12:29.090 --> 00:12:29.100 align:start position:0% actually just do that in a separate 00:12:29.100 --> 00:12:31.250 align:start position:0% actually just do that in a separate method<00:12:29.399> here<00:12:29.579> get<00:12:30.000> register<00:12:30.360> L2<00:12:30.779> message<00:12:30.959> call 00:12:31.250 --> 00:12:31.260 align:start position:0% method here get register L2 message call 00:12:31.260 --> 00:12:33.470 align:start position:0% method here get register L2 message call data<00:12:32.040> so<00:12:32.339> here<00:12:32.519> we're<00:12:32.640> going<00:12:32.760> to<00:12:32.880> encoding<00:12:33.420> the 00:12:33.470 --> 00:12:33.480 align:start position:0% data so here we're going to encoding the 00:12:33.480 --> 00:12:34.670 align:start position:0% data so here we're going to encoding the method<00:12:33.720> of<00:12:34.019> the<00:12:34.079> call<00:12:34.200> that's<00:12:34.380> going<00:12:34.560> to<00:12:34.560> be 00:12:34.670 --> 00:12:34.680 align:start position:0% method of the call that's going to be 00:12:34.680 --> 00:12:36.590 align:start position:0% method of the call that's going to be made<00:12:34.800> on<00:12:34.980> L2 00:12:36.590 --> 00:12:36.600 align:start position:0% made on L2 00:12:36.600 --> 00:12:37.730 align:start position:0% made on L2 um 00:12:37.730 --> 00:12:37.740 align:start position:0% um 00:12:37.740 --> 00:12:39.949 align:start position:0% um so 00:12:39.949 --> 00:12:39.959 align:start position:0% so 00:12:39.959 --> 00:12:40.950 align:start position:0% so we'll<00:12:40.560> use 00:12:40.950 --> 00:12:40.960 align:start position:0% we'll use 00:12:40.960 --> 00:12:41.569 align:start position:0% we'll use [Music] 00:12:41.569 --> 00:12:41.579 align:start position:0% [Music] 00:12:41.579 --> 00:12:44.090 align:start position:0% [Music] um 00:12:44.090 --> 00:12:44.100 align:start position:0% 00:12:44.100 --> 00:12:47.090 align:start position:0% encode<00:12:44.519> with<00:12:44.760> selector 00:12:47.090 --> 00:12:47.100 align:start position:0% 00:12:47.100 --> 00:12:49.790 align:start position:0% right<00:12:47.399> so<00:12:47.579> this<00:12:47.760> is<00:12:47.820> just<00:12:47.940> this<00:12:48.120> is<00:12:48.420> you<00:12:48.600> know 00:12:49.790 --> 00:12:49.800 align:start position:0% right so this is just this is you know 00:12:49.800 --> 00:12:50.870 align:start position:0% right so this is just this is you know um 00:12:50.870 --> 00:12:50.880 align:start position:0% um 00:12:50.880 --> 00:12:52.490 align:start position:0% um um<00:12:51.120> this<00:12:51.420> is<00:12:51.480> what<00:12:51.660> the<00:12:51.720> origin<00:12:52.079> cross<00:12:52.260> chain 00:12:52.490 --> 00:12:52.500 align:start position:0% um this is what the origin cross chain 00:12:52.500 --> 00:12:55.730 align:start position:0% um this is what the origin cross chain protocol<00:12:53.279> expects<00:12:53.880> we<00:12:54.360> encode<00:12:54.779> the<00:12:54.959> actual<00:12:55.260> uh 00:12:55.730 --> 00:12:55.740 align:start position:0% protocol expects we encode the actual uh 00:12:55.740 --> 00:12:57.170 align:start position:0% protocol expects we encode the actual uh the<00:12:56.040> function<00:12:56.220> name<00:12:56.399> itself<00:12:56.700> we've<00:12:57.060> already 00:12:57.170 --> 00:12:57.180 align:start position:0% the function name itself we've already 00:12:57.180 --> 00:12:59.150 align:start position:0% the function name itself we've already imported<00:12:57.660> this<00:12:57.899> thing<00:12:58.079> so<00:12:58.260> it<00:12:58.440> should<00:12:58.560> be<00:12:58.800> yeah 00:12:59.150 --> 00:12:59.160 align:start position:0% imported this thing so it should be yeah 00:12:59.160 --> 00:13:02.449 align:start position:0% imported this thing so it should be yeah L2<00:12:59.760> then<00:12:59.940> if<00:13:00.180> T<00:13:00.420> get<00:13:00.779> away 00:13:02.449 --> 00:13:02.459 align:start position:0% L2 then if T get away 00:13:02.459 --> 00:13:04.790 align:start position:0% L2 then if T get away um 00:13:04.790 --> 00:13:04.800 align:start position:0% 00:13:04.800 --> 00:13:06.110 align:start position:0% um<00:13:04.860> what<00:13:05.100> was<00:13:05.220> it<00:13:05.339> called<00:13:05.459> finalized 00:13:06.110 --> 00:13:06.120 align:start position:0% um what was it called finalized 00:13:06.120 --> 00:13:07.310 align:start position:0% um what was it called finalized registration<00:13:06.480> from<00:13:06.600> the<00:13:06.839> one<00:13:07.019> that's<00:13:07.200> the 00:13:07.310 --> 00:13:07.320 align:start position:0% registration from the one that's the 00:13:07.320 --> 00:13:10.670 align:start position:0% registration from the one that's the method<00:13:07.560> we<00:13:07.680> want<00:13:07.800> to<00:13:07.920> call 00:13:10.670 --> 00:13:10.680 align:start position:0% 00:13:10.680 --> 00:13:13.129 align:start position:0% so<00:13:10.980> there's<00:13:11.100> our<00:13:11.279> function 00:13:13.129 --> 00:13:13.139 align:start position:0% so there's our function 00:13:13.139 --> 00:13:14.210 align:start position:0% so there's our function um 00:13:14.210 --> 00:13:14.220 align:start position:0% um 00:13:14.220 --> 00:13:16.190 align:start position:0% um and<00:13:14.760> we<00:13:14.940> pass<00:13:15.120> in<00:13:15.300> its<00:13:15.540> parameters<00:13:15.779> which<00:13:16.019> are 00:13:16.190 --> 00:13:16.200 align:start position:0% and we pass in its parameters which are 00:13:16.200 --> 00:13:17.449 align:start position:0% and we pass in its parameters which are just<00:13:16.320> going<00:13:16.440> to<00:13:16.560> be 00:13:17.449 --> 00:13:17.459 align:start position:0% just going to be 00:13:17.459 --> 00:13:19.550 align:start position:0% just going to be these<00:13:18.060> so<00:13:18.779> basically<00:13:19.079> these<00:13:19.260> are<00:13:19.320> the<00:13:19.380> things 00:13:19.550 --> 00:13:19.560 align:start position:0% these so basically these are the things 00:13:19.560 --> 00:13:21.350 align:start position:0% these so basically these are the things that<00:13:19.680> we<00:13:19.740> need<00:13:19.860> at<00:13:20.040> L2<00:13:20.399> to<00:13:20.820> do<00:13:20.940> the<00:13:21.060> second<00:13:21.180> half 00:13:21.350 --> 00:13:21.360 align:start position:0% that we need at L2 to do the second half 00:13:21.360 --> 00:13:22.730 align:start position:0% that we need at L2 to do the second half of<00:13:21.540> the<00:13:21.660> operation<00:13:21.959> which<00:13:22.139> is<00:13:22.260> updating<00:13:22.560> the 00:13:22.730 --> 00:13:22.740 align:start position:0% of the operation which is updating the 00:13:22.740 --> 00:13:24.769 align:start position:0% of the operation which is updating the mapping<00:13:22.980> at<00:13:23.100> L2 00:13:24.769 --> 00:13:24.779 align:start position:0% mapping at L2 00:13:24.779 --> 00:13:26.930 align:start position:0% mapping at L2 um<00:13:25.380> cool 00:13:26.930 --> 00:13:26.940 align:start position:0% um cool 00:13:26.940 --> 00:13:28.730 align:start position:0% um cool so<00:13:27.180> that<00:13:27.360> gets<00:13:27.720> us<00:13:27.779> the<00:13:27.959> call<00:13:28.079> data<00:13:28.440> there's<00:13:28.560> a 00:13:28.730 --> 00:13:28.740 align:start position:0% so that gets us the call data there's a 00:13:28.740 --> 00:13:29.750 align:start position:0% so that gets us the call data there's a reason<00:13:28.860> I'm<00:13:28.980> putting<00:13:29.279> this<00:13:29.399> in<00:13:29.519> its<00:13:29.700> own 00:13:29.750 --> 00:13:29.760 align:start position:0% reason I'm putting this in its own 00:13:29.760 --> 00:13:31.250 align:start position:0% reason I'm putting this in its own function<00:13:30.060> this<00:13:30.660> is<00:13:30.839> going<00:13:30.959> to<00:13:31.019> help<00:13:31.139> us 00:13:31.250 --> 00:13:31.260 align:start position:0% function this is going to help us 00:13:31.260 --> 00:13:33.350 align:start position:0% function this is going to help us estimate<00:13:31.740> gas<00:13:31.920> later<00:13:32.220> basically<00:13:32.760> but<00:13:33.060> for<00:13:33.240> now 00:13:33.350 --> 00:13:33.360 align:start position:0% estimate gas later basically but for now 00:13:33.360 --> 00:13:34.910 align:start position:0% estimate gas later basically but for now if<00:13:33.480> that's<00:13:33.660> not<00:13:33.839> satisfying<00:13:34.320> we<00:13:34.560> can<00:13:34.620> just<00:13:34.740> say 00:13:34.910 --> 00:13:34.920 align:start position:0% if that's not satisfying we can just say 00:13:34.920 --> 00:13:36.710 align:start position:0% if that's not satisfying we can just say it<00:13:35.279> looks<00:13:35.459> nice<00:13:35.519> in<00:13:35.700> its<00:13:35.880> own<00:13:35.940> function<00:13:36.180> easier 00:13:36.710 --> 00:13:36.720 align:start position:0% it looks nice in its own function easier 00:13:36.720 --> 00:13:38.150 align:start position:0% it looks nice in its own function easier to<00:13:36.899> read<00:13:37.019> okay 00:13:38.150 --> 00:13:38.160 align:start position:0% to read okay 00:13:38.160 --> 00:13:39.949 align:start position:0% to read okay um<00:13:38.220> so<00:13:38.760> that'll<00:13:39.000> be<00:13:39.180> the<00:13:39.300> call<00:13:39.420> data<00:13:39.720> for<00:13:39.839> our 00:13:39.949 --> 00:13:39.959 align:start position:0% um so that'll be the call data for our 00:13:39.959 --> 00:13:41.810 align:start position:0% um so that'll be the call data for our cross<00:13:40.079> chain<00:13:40.320> message<00:13:40.560> call<00:13:40.800> let's<00:13:41.459> grab<00:13:41.700> that 00:13:41.810 --> 00:13:41.820 align:start position:0% cross chain message call let's grab that 00:13:41.820 --> 00:13:44.210 align:start position:0% cross chain message call let's grab that in<00:13:42.000> our<00:13:42.180> registration<00:13:42.600> method 00:13:44.210 --> 00:13:44.220 align:start position:0% in our registration method 00:13:44.220 --> 00:13:44.990 align:start position:0% in our registration method um 00:13:44.990 --> 00:13:45.000 align:start position:0% um 00:13:45.000 --> 00:13:48.050 align:start position:0% um yeah 00:13:48.050 --> 00:13:48.060 align:start position:0% 00:13:48.060 --> 00:13:50.990 align:start position:0% and<00:13:48.720> uh<00:13:48.959> we<00:13:49.200> pass<00:13:49.380> in<00:13:49.620> what<00:13:50.100> did<00:13:50.279> we<00:13:50.399> call<00:13:50.519> it<00:13:50.639> L1 00:13:50.990 --> 00:13:51.000 align:start position:0% and uh we pass in what did we call it L1 00:13:51.000 --> 00:13:53.569 align:start position:0% and uh we pass in what did we call it L1 token 00:13:53.569 --> 00:13:53.579 align:start position:0% 00:13:53.579 --> 00:13:57.590 align:start position:0% L2<00:13:54.060> address 00:13:57.590 --> 00:13:57.600 align:start position:0% 00:13:57.600 --> 00:14:01.009 align:start position:0% uh<00:13:58.440> let's<00:13:58.560> call<00:13:58.800> this<00:13:58.980> something<00:13:59.540> L2<00:14:00.540> message 00:14:01.009 --> 00:14:01.019 align:start position:0% uh let's call this something L2 message 00:14:01.019 --> 00:14:02.690 align:start position:0% uh let's call this something L2 message call<00:14:01.560> data 00:14:02.690 --> 00:14:02.700 align:start position:0% call data 00:14:02.700 --> 00:14:04.490 align:start position:0% call data cool 00:14:04.490 --> 00:14:04.500 align:start position:0% cool 00:14:04.500 --> 00:14:06.710 align:start position:0% cool um 00:14:06.710 --> 00:14:06.720 align:start position:0% 00:14:06.720 --> 00:14:08.210 align:start position:0% okay<00:14:07.139> let's<00:14:07.380> just<00:14:07.560> like<00:14:07.740> see<00:14:07.920> if<00:14:08.100> this 00:14:08.210 --> 00:14:08.220 align:start position:0% okay let's just like see if this 00:14:08.220 --> 00:14:10.009 align:start position:0% okay let's just like see if this compiles 00:14:10.009 --> 00:14:10.019 align:start position:0% compiles 00:14:10.019 --> 00:14:12.050 align:start position:0% compiles um<00:14:10.139> just<00:14:10.680> to<00:14:10.860> make<00:14:11.040> sure<00:14:11.160> we<00:14:11.579> don't<00:14:11.700> go<00:14:11.820> off<00:14:11.940> the 00:14:12.050 --> 00:14:12.060 align:start position:0% um just to make sure we don't go off the 00:14:12.060 --> 00:14:13.310 align:start position:0% um just to make sure we don't go off the rails<00:14:12.240> cool<00:14:12.480> okay 00:14:13.310 --> 00:14:13.320 align:start position:0% rails cool okay 00:14:13.320 --> 00:14:14.150 align:start position:0% rails cool okay um 00:14:14.150 --> 00:14:14.160 align:start position:0% um 00:14:14.160 --> 00:14:15.829 align:start position:0% um okay<00:14:14.459> so<00:14:14.639> now<00:14:14.760> we<00:14:14.940> have<00:14:15.000> our<00:14:15.120> call<00:14:15.300> data<00:14:15.660> now 00:14:15.829 --> 00:14:15.839 align:start position:0% okay so now we have our call data now 00:14:15.839 --> 00:14:17.269 align:start position:0% okay so now we have our call data now with<00:14:16.079> that<00:14:16.260> we<00:14:16.560> can<00:14:16.680> actually<00:14:16.860> send<00:14:17.160> a 00:14:17.269 --> 00:14:17.279 align:start position:0% with that we can actually send a 00:14:17.279 --> 00:14:19.250 align:start position:0% with that we can actually send a crosstain<00:14:17.700> message<00:14:17.940> so<00:14:18.360> I'll<00:14:18.600> just<00:14:18.779> briefly 00:14:19.250 --> 00:14:19.260 align:start position:0% crosstain message so I'll just briefly 00:14:19.260 --> 00:14:21.470 align:start position:0% crosstain message so I'll just briefly show<00:14:19.800> you 00:14:21.470 --> 00:14:21.480 align:start position:0% show you 00:14:21.480 --> 00:14:23.449 align:start position:0% show you um the<00:14:21.720> interface<00:14:22.079> for<00:14:22.320> sending<00:14:22.680> L1<00:14:23.040> to<00:14:23.160> L2 00:14:23.449 --> 00:14:23.459 align:start position:0% um the interface for sending L1 to L2 00:14:23.459 --> 00:14:25.190 align:start position:0% um the interface for sending L1 to L2 messages<00:14:23.700> so<00:14:24.120> this<00:14:24.300> isn't<00:14:24.540> in<00:14:24.720> the<00:14:24.839> in<00:14:25.019> the 00:14:25.190 --> 00:14:25.200 align:start position:0% messages so this isn't in the in the 00:14:25.200 --> 00:14:28.430 align:start position:0% messages so this isn't in the in the repo<00:14:25.500> this<00:14:25.800> is<00:14:26.160> um<00:14:26.160> in<00:14:26.760> the<00:14:26.880> arbitrim<00:14:27.360> uh 00:14:28.430 --> 00:14:28.440 align:start position:0% repo this is um in the arbitrim uh 00:14:28.440 --> 00:14:30.170 align:start position:0% repo this is um in the arbitrim uh uh<00:14:28.740> the<00:14:28.980> Arboretum<00:14:29.279> core<00:14:29.459> protocol<00:14:29.760> Nitro 00:14:30.170 --> 00:14:30.180 align:start position:0% uh the Arboretum core protocol Nitro 00:14:30.180 --> 00:14:31.250 align:start position:0% uh the Arboretum core protocol Nitro Reaper<00:14:30.600> but<00:14:30.720> just<00:14:30.779> to<00:14:30.899> show<00:14:31.019> you<00:14:31.139> the 00:14:31.250 --> 00:14:31.260 align:start position:0% Reaper but just to show you the 00:14:31.260 --> 00:14:33.590 align:start position:0% Reaper but just to show you the interface<00:14:31.620> here<00:14:31.800> in<00:14:31.920> fact<00:14:32.040> let's<00:14:32.339> do<00:14:32.579> this 00:14:33.590 --> 00:14:33.600 align:start position:0% interface here in fact let's do this 00:14:33.600 --> 00:14:36.410 align:start position:0% interface here in fact let's do this that's<00:14:34.139> like<00:14:34.380> reasonably<00:14:34.860> visible<00:14:35.519> kind<00:14:35.820> of 00:14:36.410 --> 00:14:36.420 align:start position:0% that's like reasonably visible kind of 00:14:36.420 --> 00:14:38.030 align:start position:0% that's like reasonably visible kind of um 00:14:38.030 --> 00:14:38.040 align:start position:0% um 00:14:38.040 --> 00:14:39.949 align:start position:0% um um here's<00:14:38.519> all<00:14:38.579> the<00:14:38.700> things<00:14:38.820> we<00:14:39.000> need 00:14:39.949 --> 00:14:39.959 align:start position:0% um here's all the things we need 00:14:39.959 --> 00:14:41.509 align:start position:0% um here's all the things we need um create<00:14:40.260> retryable<00:14:40.860> ticket<00:14:41.100> is<00:14:41.279> how<00:14:41.399> we 00:14:41.509 --> 00:14:41.519 align:start position:0% um create retryable ticket is how we 00:14:41.519 --> 00:14:43.250 align:start position:0% um create retryable ticket is how we send<00:14:41.699> an<00:14:41.820> l12<00:14:42.240> message 00:14:43.250 --> 00:14:43.260 align:start position:0% send an l12 message 00:14:43.260 --> 00:14:44.269 align:start position:0% send an l12 message um let's<00:14:43.380> just<00:14:43.560> let's<00:14:43.680> start<00:14:43.860> filling<00:14:44.160> out 00:14:44.269 --> 00:14:44.279 align:start position:0% um let's just let's start filling out 00:14:44.279 --> 00:14:46.189 align:start position:0% um let's just let's start filling out the<00:14:44.399> fields<00:14:44.699> and<00:14:45.000> then<00:14:45.120> we'll<00:14:45.240> talk<00:14:45.360> about 00:14:46.189 --> 00:14:46.199 align:start position:0% the fields and then we'll talk about 00:14:46.199 --> 00:14:47.870 align:start position:0% the fields and then we'll talk about um all<00:14:46.560> these<00:14:46.740> new<00:14:46.920> ones 00:14:47.870 --> 00:14:47.880 align:start position:0% um all these new ones 00:14:47.880 --> 00:14:50.449 align:start position:0% um all these new ones but<00:14:48.360> for<00:14:48.480> now<00:14:48.660> okay<00:14:48.839> so<00:14:49.620> um 00:14:50.449 --> 00:14:50.459 align:start position:0% but for now okay so um 00:14:50.459 --> 00:14:52.250 align:start position:0% but for now okay so um we<00:14:50.880> have<00:14:50.940> our<00:14:51.060> inbox<00:14:51.300> address<00:14:51.540> saved<00:14:52.079> again 00:14:52.250 --> 00:14:52.260 align:start position:0% we have our inbox address saved again 00:14:52.260 --> 00:14:55.129 align:start position:0% we have our inbox address saved again this<00:14:52.440> is<00:14:52.560> just<00:14:52.680> core<00:14:52.860> protocol 00:14:55.129 --> 00:14:55.139 align:start position:0% this is just core protocol 00:14:55.139 --> 00:14:55.910 align:start position:0% this is just core protocol um 00:14:55.910 --> 00:14:55.920 align:start position:0% um 00:14:55.920 --> 00:14:58.550 align:start position:0% um create<00:14:56.519> ah<00:14:57.000> it's<00:14:57.120> Auto<00:14:57.240> filling<00:14:57.660> everything 00:14:58.550 --> 00:14:58.560 align:start position:0% create ah it's Auto filling everything 00:14:58.560 --> 00:14:59.810 align:start position:0% create ah it's Auto filling everything um 00:14:59.810 --> 00:14:59.820 align:start position:0% um 00:14:59.820 --> 00:15:02.329 align:start position:0% um I<00:15:00.779> don't<00:15:00.839> know<00:15:00.959> why<00:15:01.019> it's<00:15:01.139> doing<00:15:01.320> that 00:15:02.329 --> 00:15:02.339 align:start position:0% I don't know why it's doing that 00:15:02.339 --> 00:15:03.410 align:start position:0% I don't know why it's doing that okay 00:15:03.410 --> 00:15:03.420 align:start position:0% okay 00:15:03.420 --> 00:15:04.610 align:start position:0% okay um 00:15:04.610 --> 00:15:04.620 align:start position:0% um 00:15:04.620 --> 00:15:07.910 align:start position:0% um okay<00:15:05.100> so<00:15:05.699> two<00:15:06.060> is<00:15:06.420> uh<00:15:06.660> the<00:15:06.899> address<00:15:07.019> at<00:15:07.320> L2<00:15:07.680> at 00:15:07.910 --> 00:15:07.920 align:start position:0% okay so two is uh the address at L2 at 00:15:07.920 --> 00:15:10.189 align:start position:0% okay so two is uh the address at L2 at which<00:15:08.040> we<00:15:08.220> want<00:15:08.339> to<00:15:08.459> execute<00:15:08.760> the<00:15:08.940> L2<00:15:09.300> call<00:15:09.540> so 00:15:10.189 --> 00:15:10.199 align:start position:0% which we want to execute the L2 call so 00:15:10.199 --> 00:15:11.750 align:start position:0% which we want to execute the L2 call so this<00:15:10.320> is<00:15:10.440> our<00:15:10.620> other<00:15:10.740> Gateway<00:15:11.100> counter<00:15:11.519> Portal 00:15:11.750 --> 00:15:11.760 align:start position:0% this is our other Gateway counter Portal 00:15:11.760 --> 00:15:17.629 align:start position:0% this is our other Gateway counter Portal 2<00:15:11.940> Gateway<00:15:12.240> maybe<00:15:12.660> I<00:15:12.959> can<00:15:13.459> do<00:15:14.459> something 00:15:17.629 --> 00:15:17.639 align:start position:0% 00:15:17.639 --> 00:15:19.310 align:start position:0% as<00:15:17.940> there's<00:15:18.060> more<00:15:18.300> it<00:15:18.480> should 00:15:19.310 --> 00:15:19.320 align:start position:0% as there's more it should 00:15:19.320 --> 00:15:21.170 align:start position:0% as there's more it should um become<00:15:19.680> horizontal 00:15:21.170 --> 00:15:21.180 align:start position:0% um become horizontal 00:15:21.180 --> 00:15:23.629 align:start position:0% um become horizontal um<00:15:21.300> or<00:15:21.480> vertical<00:15:21.839> rather<00:15:22.139> the<00:15:22.680> okay<00:15:22.980> so<00:15:23.399> we 00:15:23.629 --> 00:15:23.639 align:start position:0% um or vertical rather the okay so we 00:15:23.639 --> 00:15:24.769 align:start position:0% um or vertical rather the okay so we have<00:15:23.760> that 00:15:24.769 --> 00:15:24.779 align:start position:0% have that 00:15:24.779 --> 00:15:26.210 align:start position:0% have that um again<00:15:25.079> this<00:15:25.320> key<00:15:25.440> thing<00:15:25.620> down<00:15:25.800> here<00:15:25.920> this 00:15:26.210 --> 00:15:26.220 align:start position:0% um again this key thing down here this 00:15:26.220 --> 00:15:27.769 align:start position:0% um again this key thing down here this is<00:15:26.279> the<00:15:26.399> actual<00:15:26.579> message<00:15:26.760> that<00:15:27.000> we<00:15:27.120> encoded<00:15:27.480> so 00:15:27.769 --> 00:15:27.779 align:start position:0% is the actual message that we encoded so 00:15:27.779 --> 00:15:29.689 align:start position:0% is the actual message that we encoded so we<00:15:27.899> have<00:15:28.079> that<00:15:28.260> now<00:15:28.800> everything<00:15:29.100> else<00:15:29.339> has<00:15:29.579> to 00:15:29.689 --> 00:15:29.699 align:start position:0% we have that now everything else has to 00:15:29.699 --> 00:15:31.129 align:start position:0% we have that now everything else has to do<00:15:29.820> with<00:15:29.940> kind<00:15:30.180> of<00:15:30.240> paying<00:15:30.480> for<00:15:30.600> gas<00:15:30.779> at<00:15:31.019> all 00:15:31.129 --> 00:15:31.139 align:start position:0% do with kind of paying for gas at all 00:15:31.139 --> 00:15:32.870 align:start position:0% do with kind of paying for gas at all too<00:15:31.380> so<00:15:31.800> the<00:15:31.920> way<00:15:32.040> these<00:15:32.220> retrieable<00:15:32.699> tickets 00:15:32.870 --> 00:15:32.880 align:start position:0% too so the way these retrieable tickets 00:15:32.880 --> 00:15:35.689 align:start position:0% too so the way these retrieable tickets work<00:15:33.240> is<00:15:33.779> we<00:15:34.440> not<00:15:34.620> only<00:15:34.800> specify<00:15:35.220> a<00:15:35.399> contract 00:15:35.689 --> 00:15:35.699 align:start position:0% work is we not only specify a contract 00:15:35.699 --> 00:15:37.730 align:start position:0% work is we not only specify a contract call<00:15:35.880> we<00:15:36.240> also<00:15:36.480> fund<00:15:36.839> it 00:15:37.730 --> 00:15:37.740 align:start position:0% call we also fund it 00:15:37.740 --> 00:15:39.410 align:start position:0% call we also fund it so<00:15:38.100> we<00:15:38.339> literally<00:15:38.579> you<00:15:39.000> know<00:15:39.060> we're 00:15:39.410 --> 00:15:39.420 align:start position:0% so we literally you know we're 00:15:39.420 --> 00:15:41.750 align:start position:0% so we literally you know we're effectively<00:15:39.779> depositing<00:15:40.320> ether 00:15:41.750 --> 00:15:41.760 align:start position:0% effectively depositing ether 00:15:41.760 --> 00:15:42.949 align:start position:0% effectively depositing ether um along<00:15:42.000> with<00:15:42.240> this<00:15:42.360> message<00:15:42.540> we're<00:15:42.839> going 00:15:42.949 --> 00:15:42.959 align:start position:0% um along with this message we're going 00:15:42.959 --> 00:15:44.389 align:start position:0% um along with this message we're going to<00:15:43.019> use<00:15:43.139> that<00:15:43.260> ether<00:15:43.500> at<00:15:43.680> L2<00:15:44.040> to<00:15:44.220> do<00:15:44.279> the 00:15:44.389 --> 00:15:44.399 align:start position:0% to use that ether at L2 to do the 00:15:44.399 --> 00:15:45.769 align:start position:0% to use that ether at L2 to do the execution<00:15:44.820> so<00:15:45.300> a<00:15:45.420> lot<00:15:45.480> of<00:15:45.540> these<00:15:45.660> other 00:15:45.769 --> 00:15:45.779 align:start position:0% execution so a lot of these other 00:15:45.779 --> 00:15:47.449 align:start position:0% execution so a lot of these other basically<00:15:46.199> all<00:15:46.320> these<00:15:46.500> other<00:15:46.620> fields<00:15:46.860> have<00:15:47.040> to 00:15:47.449 --> 00:15:47.459 align:start position:0% basically all these other fields have to 00:15:47.459 --> 00:15:48.889 align:start position:0% basically all these other fields have to do<00:15:47.519> with<00:15:47.699> what's<00:15:48.060> going<00:15:48.240> on<00:15:48.360> in<00:15:48.540> that<00:15:48.600> L2 00:15:48.889 --> 00:15:48.899 align:start position:0% do with what's going on in that L2 00:15:48.899 --> 00:15:50.389 align:start position:0% do with what's going on in that L2 execution 00:15:50.389 --> 00:15:50.399 align:start position:0% execution 00:15:50.399 --> 00:15:52.610 align:start position:0% execution um<00:15:50.519> so<00:15:51.300> um<00:15:51.300> L2<00:15:51.660> call<00:15:51.839> Value<00:15:52.079> that's<00:15:52.320> easier 00:15:52.610 --> 00:15:52.620 align:start position:0% um so um L2 call Value that's easier 00:15:52.620 --> 00:15:53.750 align:start position:0% um so um L2 call Value that's easier because<00:15:52.740> that's<00:15:52.860> just<00:15:53.040> zero<00:15:53.399> in<00:15:53.519> this<00:15:53.699> case 00:15:53.750 --> 00:15:53.760 align:start position:0% because that's just zero in this case 00:15:53.760 --> 00:15:55.490 align:start position:0% because that's just zero in this case we're<00:15:54.060> just<00:15:54.240> updating<00:15:54.839> a<00:15:55.019> mapping<00:15:55.320> we<00:15:55.440> don't 00:15:55.490 --> 00:15:55.500 align:start position:0% we're just updating a mapping we don't 00:15:55.500 --> 00:15:57.710 align:start position:0% we're just updating a mapping we don't need<00:15:55.620> call<00:15:55.800> Value<00:15:55.980> on<00:15:56.220> the<00:15:56.339> L2<00:15:56.579> side 00:15:57.710 --> 00:15:57.720 align:start position:0% need call Value on the L2 side 00:15:57.720 --> 00:15:58.910 align:start position:0% need call Value on the L2 side um<00:15:57.839> and<00:15:57.959> now<00:15:58.079> we<00:15:58.199> have<00:15:58.380> all<00:15:58.500> this<00:15:58.620> stuff<00:15:58.800> that 00:15:58.910 --> 00:15:58.920 align:start position:0% um and now we have all this stuff that 00:15:58.920 --> 00:16:01.129 align:start position:0% um and now we have all this stuff that has<00:15:59.040> to<00:15:59.160> do<00:15:59.220> with<00:15:59.399> gas 00:16:01.129 --> 00:16:01.139 align:start position:0% has to do with gas 00:16:01.139 --> 00:16:02.990 align:start position:0% has to do with gas um<00:16:01.260> so<00:16:01.740> I've<00:16:01.860> just<00:16:02.040> included<00:16:02.399> those<00:16:02.579> in<00:16:02.880> this 00:16:02.990 --> 00:16:03.000 align:start position:0% um so I've just included those in this 00:16:03.000 --> 00:16:04.730 align:start position:0% um so I've just included those in this L2<00:16:03.240> gas<00:16:03.420> param<00:16:03.779> struct<00:16:04.139> let's<00:16:04.380> just<00:16:04.500> look<00:16:04.620> up 00:16:04.730 --> 00:16:04.740 align:start position:0% L2 gas param struct let's just look up 00:16:04.740 --> 00:16:06.050 align:start position:0% L2 gas param struct let's just look up at<00:16:04.980> that 00:16:06.050 --> 00:16:06.060 align:start position:0% at that 00:16:06.060 --> 00:16:08.990 align:start position:0% at that but<00:16:06.540> basically<00:16:06.839> L2<00:16:07.320> execution<00:16:07.800> so<00:16:08.339> max<00:16:08.699> gas 00:16:08.990 --> 00:16:09.000 align:start position:0% but basically L2 execution so max gas 00:16:09.000 --> 00:16:11.509 align:start position:0% but basically L2 execution so max gas and<00:16:09.300> gas<00:16:09.480> price<00:16:09.720> bid<00:16:10.019> this<00:16:10.380> is<00:16:10.500> very<00:16:11.160> similar 00:16:11.509 --> 00:16:11.519 align:start position:0% and gas price bid this is very similar 00:16:11.519 --> 00:16:13.550 align:start position:0% and gas price bid this is very similar basically<00:16:11.880> the<00:16:12.060> same<00:16:12.240> idea<00:16:12.600> as<00:16:12.839> gas<00:16:13.079> price<00:16:13.320> and 00:16:13.550 --> 00:16:13.560 align:start position:0% basically the same idea as gas price and 00:16:13.560 --> 00:16:16.250 align:start position:0% basically the same idea as gas price and gas<00:16:13.740> limit<00:16:13.920> on<00:16:14.220> L1<00:16:14.579> right<00:16:15.180> works<00:16:15.959> the<00:16:16.079> same<00:16:16.199> way 00:16:16.250 --> 00:16:16.260 align:start position:0% gas limit on L1 right works the same way 00:16:16.260 --> 00:16:18.170 align:start position:0% gas limit on L1 right works the same way on<00:16:16.440> arbitrum<00:16:16.920> the<00:16:17.519> one<00:16:17.639> additional<00:16:18.000> thing 00:16:18.170 --> 00:16:18.180 align:start position:0% on arbitrum the one additional thing 00:16:18.180 --> 00:16:19.370 align:start position:0% on arbitrum the one additional thing because<00:16:18.420> this<00:16:18.600> is<00:16:18.720> a<00:16:18.779> cross<00:16:18.899> chain<00:16:19.079> messages 00:16:19.370 --> 00:16:19.380 align:start position:0% because this is a cross chain messages 00:16:19.380 --> 00:16:20.990 align:start position:0% because this is a cross chain messages there's<00:16:19.740> this<00:16:19.920> special<00:16:20.100> Max<00:16:20.399> submission<00:16:20.699> cost 00:16:20.990 --> 00:16:21.000 align:start position:0% there's this special Max submission cost 00:16:21.000 --> 00:16:22.550 align:start position:0% there's this special Max submission cost thing<00:16:21.240> an<00:16:21.480> additional<00:16:21.779> fee<00:16:22.079> for<00:16:22.199> processing 00:16:22.550 --> 00:16:22.560 align:start position:0% thing an additional fee for processing 00:16:22.560 --> 00:16:23.810 align:start position:0% thing an additional fee for processing cross<00:16:22.680> chain<00:16:22.860> messages<00:16:23.160> because<00:16:23.519> there's 00:16:23.810 --> 00:16:23.820 align:start position:0% cross chain messages because there's 00:16:23.820 --> 00:16:25.069 align:start position:0% cross chain messages because there's just<00:16:24.000> a<00:16:24.180> bit<00:16:24.300> it's<00:16:24.480> a<00:16:24.600> bit<00:16:24.660> more<00:16:24.779> resource 00:16:25.069 --> 00:16:25.079 align:start position:0% just a bit it's a bit more resource 00:16:25.079 --> 00:16:26.990 align:start position:0% just a bit it's a bit more resource intensive<00:16:25.500> so<00:16:25.980> that's<00:16:26.160> like<00:16:26.339> proportional<00:16:26.820> to 00:16:26.990 --> 00:16:27.000 align:start position:0% intensive so that's like proportional to 00:16:27.000 --> 00:16:28.610 align:start position:0% intensive so that's like proportional to the<00:16:27.120> amount<00:16:27.300> of<00:16:27.420> call<00:16:27.480> data<00:16:27.839> that<00:16:27.959> you<00:16:28.079> use<00:16:28.199> but 00:16:28.610 --> 00:16:28.620 align:start position:0% the amount of call data that you use but 00:16:28.620 --> 00:16:30.170 align:start position:0% the amount of call data that you use but for<00:16:28.800> intents<00:16:29.220> and<00:16:29.220> purposes<00:16:29.519> here<00:16:29.760> we're<00:16:30.000> just 00:16:30.170 --> 00:16:30.180 align:start position:0% for intents and purposes here we're just 00:16:30.180 --> 00:16:31.490 align:start position:0% for intents and purposes here we're just we're<00:16:30.480> asking<00:16:30.720> the<00:16:30.779> client<00:16:31.019> to<00:16:31.139> provide<00:16:31.380> all 00:16:31.490 --> 00:16:31.500 align:start position:0% we're asking the client to provide all 00:16:31.500 --> 00:16:32.449 align:start position:0% we're asking the client to provide all these<00:16:31.680> values<00:16:31.860> so<00:16:32.040> we<00:16:32.100> don't<00:16:32.220> have<00:16:32.339> to<00:16:32.399> worry 00:16:32.449 --> 00:16:32.459 align:start position:0% these values so we don't have to worry 00:16:32.459 --> 00:16:34.069 align:start position:0% these values so we don't have to worry about<00:16:32.579> where<00:16:32.820> they<00:16:32.940> came<00:16:33.120> from 00:16:34.069 --> 00:16:34.079 align:start position:0% about where they came from 00:16:34.079 --> 00:16:35.150 align:start position:0% about where they came from um<00:16:34.139> but<00:16:34.320> those<00:16:34.440> are<00:16:34.620> the<00:16:34.740> those<00:16:34.920> are<00:16:35.100> the 00:16:35.150 --> 00:16:35.160 align:start position:0% um but those are the those are the 00:16:35.160 --> 00:16:36.710 align:start position:0% um but those are the those are the fields<00:16:35.399> we'll<00:16:35.519> need<00:16:35.699> to<00:16:35.880> to<00:16:36.180> create<00:16:36.420> a<00:16:36.600> cross 00:16:36.710 --> 00:16:36.720 align:start position:0% fields we'll need to to create a cross 00:16:36.720 --> 00:16:38.389 align:start position:0% fields we'll need to to create a cross chain<00:16:36.899> message 00:16:38.389 --> 00:16:38.399 align:start position:0% chain message 00:16:38.399 --> 00:16:39.110 align:start position:0% chain message um 00:16:39.110 --> 00:16:39.120 align:start position:0% um 00:16:39.120 --> 00:16:41.810 align:start position:0% um and<00:16:39.600> I<00:16:39.899> should<00:16:39.959> just<00:16:40.079> do<00:16:40.199> this<00:16:40.320> now<00:16:40.440> as<00:16:40.620> well 00:16:41.810 --> 00:16:41.820 align:start position:0% and I should just do this now as well 00:16:41.820 --> 00:16:43.850 align:start position:0% and I should just do this now as well um<00:16:41.880> like<00:16:42.360> I<00:16:42.480> said<00:16:42.600> we're<00:16:42.839> sort<00:16:43.079> of<00:16:43.199> depositing 00:16:43.850 --> 00:16:43.860 align:start position:0% um like I said we're sort of depositing 00:16:43.860 --> 00:16:45.889 align:start position:0% um like I said we're sort of depositing The<00:16:43.920> Ether<00:16:44.160> along<00:16:44.399> with<00:16:44.639> it 00:16:45.889 --> 00:16:45.899 align:start position:0% The Ether along with it 00:16:45.899 --> 00:16:47.689 align:start position:0% The Ether along with it um 00:16:47.689 --> 00:16:47.699 align:start position:0% um 00:16:47.699 --> 00:16:51.170 align:start position:0% um so<00:16:48.060> we're<00:16:48.180> going<00:16:48.300> to<00:16:48.360> send<00:16:48.540> that<00:16:48.839> along 00:16:51.170 --> 00:16:51.180 align:start position:0% 00:16:51.180 --> 00:16:52.910 align:start position:0% um<00:16:51.240> is<00:16:51.420> that<00:16:51.540> right 00:16:52.910 --> 00:16:52.920 align:start position:0% um is that right 00:16:52.920 --> 00:16:54.110 align:start position:0% um is that right um<00:16:53.040> that<00:16:53.220> looked<00:16:53.459> weird<00:16:53.519> to<00:16:53.699> me<00:16:53.759> but<00:16:53.880> I<00:16:54.000> think 00:16:54.110 --> 00:16:54.120 align:start position:0% um that looked weird to me but I think 00:16:54.120 --> 00:16:55.970 align:start position:0% um that looked weird to me but I think that's<00:16:54.240> right<00:16:54.899> so<00:16:55.199> we<00:16:55.259> send<00:16:55.440> this<00:16:55.560> along<00:16:55.680> this 00:16:55.970 --> 00:16:55.980 align:start position:0% that's right so we send this along this 00:16:55.980 --> 00:16:57.949 align:start position:0% that's right so we send this along this will<00:16:56.100> pay<00:16:56.220> for<00:16:56.279> the<00:16:56.399> L2<00:16:56.639> execution 00:16:57.949 --> 00:16:57.959 align:start position:0% will pay for the L2 execution 00:16:57.959 --> 00:16:59.689 align:start position:0% will pay for the L2 execution the<00:16:58.139> L2<00:16:58.560> will<00:16:58.740> sort<00:16:58.860> of<00:16:58.980> automatically<00:16:59.339> try<00:16:59.519> to 00:16:59.689 --> 00:16:59.699 align:start position:0% the L2 will sort of automatically try to 00:16:59.699 --> 00:17:01.790 align:start position:0% the L2 will sort of automatically try to execute<00:17:00.060> it<00:17:00.240> if<00:17:00.600> it<00:17:00.779> fails<00:17:01.079> the<00:17:01.259> execute<00:17:01.620> on 00:17:01.790 --> 00:17:01.800 align:start position:0% execute it if it fails the execute on 00:17:01.800 --> 00:17:04.130 align:start position:0% execute it if it fails the execute on the<00:17:01.980> L2<00:17:02.279> side<00:17:02.519> it<00:17:03.060> can<00:17:03.180> be<00:17:03.240> retried<00:17:03.779> for<00:17:03.959> a<00:17:04.020> week 00:17:04.130 --> 00:17:04.140 align:start position:0% the L2 side it can be retried for a week 00:17:04.140 --> 00:17:05.210 align:start position:0% the L2 side it can be retried for a week that's<00:17:04.319> why<00:17:04.500> it's<00:17:04.620> called<00:17:04.740> a<00:17:04.799> retrievable 00:17:05.210 --> 00:17:05.220 align:start position:0% that's why it's called a retrievable 00:17:05.220 --> 00:17:06.409 align:start position:0% that's why it's called a retrievable ticket<00:17:05.400> and<00:17:05.579> this<00:17:05.699> gives<00:17:05.880> us<00:17:06.000> kind<00:17:06.179> of<00:17:06.299> an 00:17:06.409 --> 00:17:06.419 align:start position:0% ticket and this gives us kind of an 00:17:06.419 --> 00:17:08.150 align:start position:0% ticket and this gives us kind of an atomicity<00:17:06.900> guarantee 00:17:08.150 --> 00:17:08.160 align:start position:0% atomicity guarantee 00:17:08.160 --> 00:17:09.350 align:start position:0% atomicity guarantee um anyway<00:17:08.339> let's<00:17:08.579> keep<00:17:08.760> filling<00:17:09.059> these<00:17:09.179> out 00:17:09.350 --> 00:17:09.360 align:start position:0% um anyway let's keep filling these out 00:17:09.360 --> 00:17:11.210 align:start position:0% um anyway let's keep filling these out so<00:17:09.900> we<00:17:10.020> have<00:17:10.140> the<00:17:10.260> O2<00:17:10.559> counter<00:17:10.799> bracket<00:17:11.100> with 00:17:11.210 --> 00:17:11.220 align:start position:0% so we have the O2 counter bracket with 00:17:11.220 --> 00:17:13.069 align:start position:0% so we have the O2 counter bracket with no<00:17:11.459> call<00:17:11.699> Value<00:17:11.939> and<00:17:12.179> now<00:17:12.299> we<00:17:12.419> get<00:17:12.540> to<00:17:12.660> these<00:17:12.780> L2 00:17:13.069 --> 00:17:13.079 align:start position:0% no call Value and now we get to these L2 00:17:13.079 --> 00:17:14.270 align:start position:0% no call Value and now we get to these L2 gas<00:17:13.260> params 00:17:14.270 --> 00:17:14.280 align:start position:0% gas params 00:17:14.280 --> 00:17:15.829 align:start position:0% gas params um 00:17:15.829 --> 00:17:15.839 align:start position:0% um 00:17:15.839 --> 00:17:18.250 align:start position:0% um so<00:17:16.559> that<00:17:16.919> was<00:17:17.040> just<00:17:17.280> passed<00:17:17.640> in 00:17:18.250 --> 00:17:18.260 align:start position:0% so that was just passed in 00:17:18.260 --> 00:17:21.230 align:start position:0% so that was just passed in can<00:17:19.260> I<00:17:19.439> make<00:17:19.559> this 00:17:21.230 --> 00:17:21.240 align:start position:0% can I make this 00:17:21.240 --> 00:17:25.909 align:start position:0% can I make this uh 00:17:25.909 --> 00:17:25.919 align:start position:0% 00:17:25.919 --> 00:17:27.710 align:start position:0% I<00:17:26.160> feel<00:17:26.640> it's<00:17:26.819> getting<00:17:26.939> weird<00:17:27.179> I'll<00:17:27.480> just<00:17:27.600> type 00:17:27.710 --> 00:17:27.720 align:start position:0% I feel it's getting weird I'll just type 00:17:27.720 --> 00:17:28.789 align:start position:0% I feel it's getting weird I'll just type it<00:17:27.900> up 00:17:28.789 --> 00:17:28.799 align:start position:0% it up 00:17:28.799 --> 00:17:29.810 align:start position:0% it up um 00:17:29.810 --> 00:17:29.820 align:start position:0% um 00:17:29.820 --> 00:17:34.850 align:start position:0% um so<00:17:30.360> max<00:17:30.600> submission<00:17:30.900> cost<00:17:31.140> is<00:17:31.380> next 00:17:34.850 --> 00:17:34.860 align:start position:0% 00:17:34.860 --> 00:17:37.430 align:start position:0% um<00:17:34.980> okay<00:17:35.160> now<00:17:35.400> we<00:17:35.580> see<00:17:35.700> over<00:17:36.000> here<00:17:36.419> we<00:17:37.260> have 00:17:37.430 --> 00:17:37.440 align:start position:0% um okay now we see over here we have 00:17:37.440 --> 00:17:40.130 align:start position:0% um okay now we see over here we have these<00:17:37.919> refund<00:17:38.580> addresses<00:17:39.179> and<00:17:39.840> this<00:17:40.020> is 00:17:40.130 --> 00:17:40.140 align:start position:0% these refund addresses and this is 00:17:40.140 --> 00:17:42.710 align:start position:0% these refund addresses and this is basically<00:17:40.440> on<00:17:40.860> the<00:17:40.980> L2<00:17:41.340> side<00:17:41.580> if<00:17:42.299> you<00:17:42.419> provide 00:17:42.710 --> 00:17:42.720 align:start position:0% basically on the L2 side if you provide 00:17:42.720 --> 00:17:44.990 align:start position:0% basically on the L2 side if you provide excess<00:17:43.200> gas<00:17:43.559> in<00:17:43.799> your<00:17:43.919> deposit<00:17:44.340> you<00:17:44.700> specify 00:17:44.990 --> 00:17:45.000 align:start position:0% excess gas in your deposit you specify 00:17:45.000 --> 00:17:46.370 align:start position:0% excess gas in your deposit you specify which<00:17:45.240> address<00:17:45.419> you<00:17:45.720> want<00:17:45.840> that<00:17:45.960> guys<00:17:46.140> to<00:17:46.320> end 00:17:46.370 --> 00:17:46.380 align:start position:0% which address you want that guys to end 00:17:46.380 --> 00:17:48.409 align:start position:0% which address you want that guys to end up<00:17:46.559> on<00:17:46.740> and<00:17:47.340> this<00:17:47.520> is<00:17:47.640> necessary<00:17:48.000> basically 00:17:48.409 --> 00:17:48.419 align:start position:0% up on and this is necessary basically 00:17:48.419 --> 00:17:50.750 align:start position:0% up on and this is necessary basically because<00:17:48.600> it's<00:17:48.780> a<00:17:48.900> cross<00:17:49.020> chain<00:17:49.200> message<00:17:49.760> we 00:17:50.750 --> 00:17:50.760 align:start position:0% because it's a cross chain message we 00:17:50.760 --> 00:17:51.830 align:start position:0% because it's a cross chain message we need<00:17:50.880> to<00:17:51.000> sort<00:17:51.120> of<00:17:51.179> do<00:17:51.299> something<00:17:51.480> with<00:17:51.660> this 00:17:51.830 --> 00:17:51.840 align:start position:0% need to sort of do something with this 00:17:51.840 --> 00:18:01.850 align:start position:0% need to sort of do something with this excess<00:17:52.140> gas<00:17:52.380> uh<00:17:52.860> yeah<00:17:52.980> question 00:18:01.850 --> 00:18:01.860 align:start position:0% 00:18:01.860 --> 00:18:05.390 align:start position:0% they<00:18:02.280> also<00:18:02.520> call<00:18:02.700> Value 00:18:05.390 --> 00:18:05.400 align:start position:0% 00:18:05.400 --> 00:18:08.330 align:start position:0% yeah 00:18:08.330 --> 00:18:08.340 align:start position:0% 00:18:08.340 --> 00:18:10.310 align:start position:0% yeah<00:18:08.580> so<00:18:08.880> I<00:18:09.059> think<00:18:09.120> of<00:18:09.240> L2<00:18:09.480> call<00:18:09.720> Value<00:18:09.960> when 00:18:10.310 --> 00:18:10.320 align:start position:0% yeah so I think of L2 call Value when 00:18:10.320 --> 00:18:11.630 align:start position:0% yeah so I think of L2 call Value when this<00:18:10.440> cross<00:18:10.559> chain<00:18:10.860> message<00:18:11.100> we're<00:18:11.340> creating 00:18:11.630 --> 00:18:11.640 align:start position:0% this cross chain message we're creating 00:18:11.640 --> 00:18:13.070 align:start position:0% this cross chain message we're creating this<00:18:12.000> effect<00:18:12.240> something<00:18:12.600> that's<00:18:12.780> going<00:18:12.960> to 00:18:13.070 --> 00:18:13.080 align:start position:0% this effect something that's going to 00:18:13.080 --> 00:18:14.990 align:start position:0% this effect something that's going to look<00:18:13.140> a<00:18:13.260> lot<00:18:13.320> like<00:18:13.440> an<00:18:13.559> L2<00:18:13.860> transaction<00:18:14.280> it's 00:18:14.990 --> 00:18:15.000 align:start position:0% look a lot like an L2 transaction it's 00:18:15.000 --> 00:18:16.549 align:start position:0% look a lot like an L2 transaction it's just<00:18:15.179> going<00:18:15.299> to<00:18:15.360> appear<00:18:15.600> at<00:18:15.720> L2<00:18:16.020> unsigned 00:18:16.549 --> 00:18:16.559 align:start position:0% just going to appear at L2 unsigned 00:18:16.559 --> 00:18:18.830 align:start position:0% just going to appear at L2 unsigned basically<00:18:16.860> okay<00:18:17.220> so<00:18:18.059> for<00:18:18.360> that<00:18:18.480> L2 00:18:18.830 --> 00:18:18.840 align:start position:0% basically okay so for that L2 00:18:18.840 --> 00:18:20.390 align:start position:0% basically okay so for that L2 transaction<00:18:19.260> we<00:18:19.440> need<00:18:19.559> to<00:18:19.679> specify<00:18:20.039> kind<00:18:20.340> of 00:18:20.390 --> 00:18:20.400 align:start position:0% transaction we need to specify kind of 00:18:20.400 --> 00:18:23.029 align:start position:0% transaction we need to specify kind of all<00:18:20.520> the<00:18:20.700> usual<00:18:20.940> fields<00:18:21.780> okay<00:18:22.320> so<00:18:22.500> but<00:18:22.799> the 00:18:23.029 --> 00:18:23.039 align:start position:0% all the usual fields okay so but the 00:18:23.039 --> 00:18:24.650 align:start position:0% all the usual fields okay so but the we'll<00:18:23.520> we'll<00:18:23.700> sort<00:18:24.120> of<00:18:24.179> build<00:18:24.360> out<00:18:24.480> the 00:18:24.650 --> 00:18:24.660 align:start position:0% we'll we'll sort of build out the 00:18:24.660 --> 00:18:25.789 align:start position:0% we'll we'll sort of build out the contract<00:18:24.900> call<00:18:25.020> in<00:18:25.260> a<00:18:25.380> second<00:18:25.440> and<00:18:25.620> we'll<00:18:25.679> see 00:18:25.789 --> 00:18:25.799 align:start position:0% contract call in a second and we'll see 00:18:25.799 --> 00:18:27.409 align:start position:0% contract call in a second and we'll see what<00:18:25.860> the<00:18:25.919> L2<00:18:26.220> transaction<00:18:26.580> is<00:18:26.760> doing<00:18:26.940> but 00:18:27.409 --> 00:18:27.419 align:start position:0% what the L2 transaction is doing but 00:18:27.419 --> 00:18:28.730 align:start position:0% what the L2 transaction is doing but here<00:18:27.600> we're<00:18:27.780> specifying<00:18:28.140> all<00:18:28.260> the<00:18:28.440> necessary 00:18:28.730 --> 00:18:28.740 align:start position:0% here we're specifying all the necessary 00:18:28.740 --> 00:18:30.529 align:start position:0% here we're specifying all the necessary things<00:18:29.039> so<00:18:29.460> we<00:18:29.640> have<00:18:29.700> like<00:18:29.880> the<00:18:30.059> contract<00:18:30.360> call 00:18:30.529 --> 00:18:30.539 align:start position:0% things so we have like the contract call 00:18:30.539 --> 00:18:32.570 align:start position:0% things so we have like the contract call the<00:18:31.080> address<00:18:31.260> and<00:18:31.679> then<00:18:31.799> yeah<00:18:31.980> the<00:18:32.340> actual 00:18:32.570 --> 00:18:32.580 align:start position:0% the address and then yeah the actual 00:18:32.580 --> 00:18:35.450 align:start position:0% the address and then yeah the actual call<00:18:33.000> Value<00:18:33.299> just<00:18:33.539> on<00:18:33.660> the<00:18:33.780> L2<00:18:34.020> side 00:18:35.450 --> 00:18:35.460 align:start position:0% call Value just on the L2 side 00:18:35.460 --> 00:18:36.350 align:start position:0% call Value just on the L2 side um 00:18:36.350 --> 00:18:36.360 align:start position:0% um 00:18:36.360 --> 00:18:38.150 align:start position:0% um yeah<00:18:37.140> hopefully<00:18:37.500> that<00:18:37.679> makes<00:18:37.799> sense<00:18:37.919> if<00:18:38.039> not 00:18:38.150 --> 00:18:38.160 align:start position:0% yeah hopefully that makes sense if not 00:18:38.160 --> 00:18:39.169 align:start position:0% yeah hopefully that makes sense if not hopefully<00:18:38.400> it'll<00:18:38.520> become<00:18:38.700> clear<00:18:38.820> in<00:18:38.940> a<00:18:39.059> second 00:18:39.169 --> 00:18:39.179 align:start position:0% hopefully it'll become clear in a second 00:18:39.179 --> 00:18:41.450 align:start position:0% hopefully it'll become clear in a second when<00:18:39.299> we<00:18:39.419> see<00:18:39.539> the<00:18:39.660> full<00:18:39.780> the<00:18:40.020> full<00:18:40.260> flow 00:18:41.450 --> 00:18:41.460 align:start position:0% when we see the full the full flow 00:18:41.460 --> 00:18:43.010 align:start position:0% when we see the full the full flow um 00:18:43.010 --> 00:18:43.020 align:start position:0% um 00:18:43.020 --> 00:18:44.810 align:start position:0% um yeah 00:18:44.810 --> 00:18:44.820 align:start position:0% yeah 00:18:44.820 --> 00:18:46.669 align:start position:0% yeah um<00:18:44.940> okay<00:18:45.120> so<00:18:45.299> the<00:18:45.360> refund<00:18:45.660> address 00:18:46.669 --> 00:18:46.679 align:start position:0% um okay so the refund address 00:18:46.679 --> 00:18:47.270 align:start position:0% um okay so the refund address um 00:18:47.270 --> 00:18:47.280 align:start position:0% um 00:18:47.280 --> 00:18:49.250 align:start position:0% um we<00:18:47.760> can<00:18:47.820> just<00:18:48.000> we're<00:18:48.240> asking<00:18:48.840> the<00:18:48.960> client<00:18:49.080> to 00:18:49.250 --> 00:18:49.260 align:start position:0% we can just we're asking the client to 00:18:49.260 --> 00:18:50.150 align:start position:0% we can just we're asking the client to provide 00:18:50.150 --> 00:18:50.160 align:start position:0% provide 00:18:50.160 --> 00:18:52.430 align:start position:0% provide so<00:18:50.700> in<00:18:51.000> this<00:18:51.120> cross<00:18:51.240> chain<00:18:51.539> message<00:18:51.840> sort<00:18:52.320> of 00:18:52.430 --> 00:18:52.440 align:start position:0% so in this cross chain message sort of 00:18:52.440 --> 00:18:54.169 align:start position:0% so in this cross chain message sort of where<00:18:52.559> your<00:18:52.799> excess<00:18:53.039> ether<00:18:53.340> gets<00:18:53.640> refunded<00:18:54.000> at 00:18:54.169 --> 00:18:54.179 align:start position:0% where your excess ether gets refunded at 00:18:54.179 --> 00:18:55.549 align:start position:0% where your excess ether gets refunded at L2 00:18:55.549 --> 00:18:55.559 align:start position:0% L2 00:18:55.559 --> 00:18:56.930 align:start position:0% L2 um 00:18:56.930 --> 00:18:56.940 align:start position:0% um 00:18:56.940 --> 00:18:58.490 align:start position:0% um and<00:18:57.299> then<00:18:57.419> there's<00:18:57.660> a<00:18:57.780> second<00:18:57.900> refund<00:18:58.260> address 00:18:58.490 --> 00:18:58.500 align:start position:0% and then there's a second refund address 00:18:58.500 --> 00:18:59.930 align:start position:0% and then there's a second refund address which<00:18:58.740> is<00:18:58.860> if<00:18:58.980> there<00:18:59.100> is<00:18:59.220> call<00:18:59.340> Value<00:18:59.640> you 00:18:59.930 --> 00:18:59.940 align:start position:0% which is if there is call Value you 00:18:59.940 --> 00:19:02.150 align:start position:0% which is if there is call Value you specify<00:19:00.360> if<00:19:00.720> the<00:19:00.900> L2<00:19:01.200> message<00:19:01.440> never<00:19:01.679> succeeds 00:19:02.150 --> 00:19:02.160 align:start position:0% specify if the L2 message never succeeds 00:19:02.160 --> 00:19:03.590 align:start position:0% specify if the L2 message never succeeds you<00:19:02.280> specify<00:19:02.640> where<00:19:02.820> that<00:19:02.940> call<00:19:03.059> Value<00:19:03.299> gets 00:19:03.590 --> 00:19:03.600 align:start position:0% you specify where that call Value gets 00:19:03.600 --> 00:19:05.210 align:start position:0% you specify where that call Value gets refunded<00:19:03.900> at<00:19:04.020> all<00:19:04.200> too<00:19:04.380> in<00:19:04.620> this<00:19:04.740> case<00:19:04.860> doesn't 00:19:05.210 --> 00:19:05.220 align:start position:0% refunded at all too in this case doesn't 00:19:05.220 --> 00:19:06.169 align:start position:0% refunded at all too in this case doesn't really<00:19:05.400> matter<00:19:05.640> because<00:19:05.760> there's<00:19:05.940> no<00:19:06.059> call 00:19:06.169 --> 00:19:06.179 align:start position:0% really matter because there's no call 00:19:06.179 --> 00:19:07.789 align:start position:0% really matter because there's no call values<00:19:06.539> we'll<00:19:06.720> just<00:19:06.840> use<00:19:06.960> the<00:19:07.140> same<00:19:07.260> the<00:19:07.559> same 00:19:07.789 --> 00:19:07.799 align:start position:0% values we'll just use the same the same 00:19:07.799 --> 00:19:10.310 align:start position:0% values we'll just use the same the same refund<00:19:08.100> address<00:19:08.480> and<00:19:09.480> now<00:19:09.600> we<00:19:09.720> have<00:19:09.840> L2<00:19:10.140> gas 00:19:10.310 --> 00:19:10.320 align:start position:0% refund address and now we have L2 gas 00:19:10.320 --> 00:19:11.710 align:start position:0% refund address and now we have L2 gas params 00:19:11.710 --> 00:19:11.720 align:start position:0% params 00:19:11.720 --> 00:19:15.190 align:start position:0% params uh<00:19:12.720> hard<00:19:13.260> to<00:19:13.559> see 00:19:15.190 --> 00:19:15.200 align:start position:0% uh hard to see 00:19:15.200 --> 00:19:17.450 align:start position:0% uh hard to see what's<00:19:16.200> it<00:19:16.320> called<00:19:16.440> gas 00:19:17.450 --> 00:19:17.460 align:start position:0% what's it called gas 00:19:17.460 --> 00:19:19.310 align:start position:0% what's it called gas Max<00:19:17.880> gas 00:19:19.310 --> 00:19:19.320 align:start position:0% Max gas 00:19:19.320 --> 00:19:21.770 align:start position:0% Max gas so<00:19:19.620> that's<00:19:19.679> kind<00:19:19.919> of<00:19:19.980> the<00:19:20.039> gas<00:19:20.160> limit 00:19:21.770 --> 00:19:21.780 align:start position:0% so that's kind of the gas limit 00:19:21.780 --> 00:19:24.770 align:start position:0% so that's kind of the gas limit and<00:19:22.080> then<00:19:22.200> L2<00:19:22.500> gas<00:19:22.740> params 00:19:24.770 --> 00:19:24.780 align:start position:0% and then L2 gas params 00:19:24.780 --> 00:19:26.870 align:start position:0% and then L2 gas params um<00:19:24.900> it<00:19:25.020> should<00:19:25.200> be<00:19:25.320> something<00:19:25.559> like<00:19:25.919> what<00:19:26.700> do 00:19:26.870 --> 00:19:26.880 align:start position:0% um it should be something like what do 00:19:26.880 --> 00:19:29.029 align:start position:0% um it should be something like what do we<00:19:26.940> call<00:19:27.059> it 00:19:29.029 --> 00:19:29.039 align:start position:0% we call it 00:19:29.039 --> 00:19:33.230 align:start position:0% we call it Max<00:19:29.400> fee<00:19:29.880> for<00:19:29.940> gas<00:19:30.179> I<00:19:30.480> think 00:19:33.230 --> 00:19:33.240 align:start position:0% 00:19:33.240 --> 00:19:35.029 align:start position:0% for<00:19:33.419> gas<00:19:33.660> price<00:19:33.900> there<00:19:34.140> we<00:19:34.260> go<00:19:34.320> gas<00:19:34.500> price<00:19:34.740> bid 00:19:35.029 --> 00:19:35.039 align:start position:0% for gas price there we go gas price bid 00:19:35.039 --> 00:19:36.529 align:start position:0% for gas price there we go gas price bid okay 00:19:36.529 --> 00:19:36.539 align:start position:0% okay 00:19:36.539 --> 00:19:37.970 align:start position:0% okay um 00:19:37.970 --> 00:19:37.980 align:start position:0% um 00:19:37.980 --> 00:19:39.770 align:start position:0% um let's<00:19:38.340> get<00:19:38.460> rid<00:19:38.640> of<00:19:38.700> this<00:19:38.880> hoping<00:19:39.480> this<00:19:39.600> will 00:19:39.770 --> 00:19:39.780 align:start position:0% let's get rid of this hoping this will 00:19:39.780 --> 00:19:43.190 align:start position:0% let's get rid of this hoping this will just<00:19:39.900> horizontally 00:19:43.190 --> 00:19:43.200 align:start position:0% 00:19:43.200 --> 00:19:44.390 align:start position:0% um<00:19:43.260> okay<00:19:43.500> and<00:19:43.740> then<00:19:43.799> finally<00:19:44.039> the<00:19:44.220> last 00:19:44.390 --> 00:19:44.400 align:start position:0% um okay and then finally the last 00:19:44.400 --> 00:19:47.570 align:start position:0% um okay and then finally the last parameter<00:19:44.760> was<00:19:44.940> the<00:19:45.179> actual<00:19:45.419> encoded<00:19:45.960> uh 00:19:47.570 --> 00:19:47.580 align:start position:0% parameter was the actual encoded uh 00:19:47.580 --> 00:19:51.110 align:start position:0% parameter was the actual encoded uh the<00:19:48.000> encoded<00:19:48.480> call<00:19:48.600> data<00:19:48.900> of<00:19:48.960> the<00:19:49.080> L2<00:19:49.320> message 00:19:51.110 --> 00:19:51.120 align:start position:0% the encoded call data of the L2 message 00:19:51.120 --> 00:19:54.590 align:start position:0% the encoded call data of the L2 message there<00:19:51.960> we<00:19:52.140> go<00:19:52.200> okay 00:19:54.590 --> 00:19:54.600 align:start position:0% 00:19:54.600 --> 00:19:56.690 align:start position:0% um<00:19:54.720> we<00:19:55.020> are<00:19:55.260> complaining 00:19:56.690 --> 00:19:56.700 align:start position:0% um we are complaining 00:19:56.700 --> 00:20:00.289 align:start position:0% um we are complaining yes<00:19:57.360> I<00:19:57.600> did<00:19:57.780> mean<00:19:57.960> that 00:20:00.289 --> 00:20:00.299 align:start position:0% yes I did mean that 00:20:00.299 --> 00:20:02.390 align:start position:0% yes I did mean that okay<00:20:00.720> looks<00:20:01.200> good 00:20:02.390 --> 00:20:02.400 align:start position:0% okay looks good 00:20:02.400 --> 00:20:04.909 align:start position:0% okay looks good um<00:20:02.460> so<00:20:02.760> there's<00:20:02.880> a<00:20:03.000> question<00:20:03.120> message 00:20:04.909 --> 00:20:04.919 align:start position:0% um so there's a question message 00:20:04.919 --> 00:20:05.870 align:start position:0% um so there's a question message um 00:20:05.870 --> 00:20:05.880 align:start position:0% um 00:20:05.880 --> 00:20:07.610 align:start position:0% um this<00:20:06.240> gets<00:20:06.539> published<00:20:06.840> and<00:20:07.140> this<00:20:07.260> will<00:20:07.440> sort 00:20:07.610 --> 00:20:07.620 align:start position:0% this gets published and this will sort 00:20:07.620 --> 00:20:09.529 align:start position:0% this gets published and this will sort of<00:20:07.740> automatically<00:20:08.160> execute<00:20:08.700> this<00:20:09.299> method 00:20:09.529 --> 00:20:09.539 align:start position:0% of automatically execute this method 00:20:09.539 --> 00:20:11.150 align:start position:0% of automatically execute this method that<00:20:09.660> we<00:20:09.720> encoded<00:20:10.080> at<00:20:10.140> L2<00:20:10.559> so<00:20:10.799> let's<00:20:10.919> go<00:20:11.100> to 00:20:11.150 --> 00:20:11.160 align:start position:0% that we encoded at L2 so let's go to 00:20:11.160 --> 00:20:12.830 align:start position:0% that we encoded at L2 so let's go to that<00:20:11.340> now 00:20:12.830 --> 00:20:12.840 align:start position:0% that now 00:20:12.840 --> 00:20:15.770 align:start position:0% that now um<00:20:13.020> which<00:20:13.320> if<00:20:13.500> we<00:20:13.620> remember<00:20:13.799> was<00:20:14.220> this<00:20:14.580> thing 00:20:15.770 --> 00:20:15.780 align:start position:0% um which if we remember was this thing 00:20:15.780 --> 00:20:17.870 align:start position:0% um which if we remember was this thing finalized<00:20:16.440> registration<00:20:16.740> from<00:20:16.919> L1 00:20:17.870 --> 00:20:17.880 align:start position:0% finalized registration from L1 00:20:17.880 --> 00:20:19.549 align:start position:0% finalized registration from L1 so<00:20:18.240> this<00:20:18.419> gets<00:20:18.539> automatically<00:20:19.020> executed<00:20:19.440> now 00:20:19.549 --> 00:20:19.559 align:start position:0% so this gets automatically executed now 00:20:19.559 --> 00:20:20.810 align:start position:0% so this gets automatically executed now we<00:20:19.740> want<00:20:19.860> to<00:20:19.980> finalize<00:20:20.220> the<00:20:20.400> registration 00:20:20.810 --> 00:20:20.820 align:start position:0% we want to finalize the registration 00:20:20.820 --> 00:20:22.250 align:start position:0% we want to finalize the registration which<00:20:21.059> means<00:20:21.419> basically<00:20:21.660> the<00:20:21.840> same<00:20:21.960> thing<00:20:22.080> it 00:20:22.250 --> 00:20:22.260 align:start position:0% which means basically the same thing it 00:20:22.260 --> 00:20:23.630 align:start position:0% which means basically the same thing it did<00:20:22.380> before<00:20:22.559> we're<00:20:22.980> just<00:20:23.160> updating<00:20:23.460> this 00:20:23.630 --> 00:20:23.640 align:start position:0% did before we're just updating this 00:20:23.640 --> 00:20:25.789 align:start position:0% did before we're just updating this other<00:20:23.760> mapping<00:20:24.179> okay<00:20:24.600> so<00:20:25.140> that<00:20:25.320> both<00:20:25.500> sides<00:20:25.740> of 00:20:25.789 --> 00:20:25.799 align:start position:0% other mapping okay so that both sides of 00:20:25.799 --> 00:20:28.070 align:start position:0% other mapping okay so that both sides of our<00:20:25.919> Gateway<00:20:26.220> know<00:20:26.520> uh<00:20:27.179> what<00:20:27.419> token<00:20:27.780> goes<00:20:28.020> to 00:20:28.070 --> 00:20:28.080 align:start position:0% our Gateway know uh what token goes to 00:20:28.080 --> 00:20:30.409 align:start position:0% our Gateway know uh what token goes to what 00:20:30.409 --> 00:20:30.419 align:start position:0% 00:20:30.419 --> 00:20:34.549 align:start position:0% um<00:20:30.600> so<00:20:30.900> we'll<00:20:31.080> update<00:20:31.320> the<00:20:31.440> mapping<00:20:31.740> l12<00:20:32.520> token 00:20:34.549 --> 00:20:34.559 align:start position:0% um so we'll update the mapping l12 token 00:20:34.559 --> 00:20:35.930 align:start position:0% um so we'll update the mapping l12 token the<00:20:34.740> L1<00:20:35.039> address<00:20:35.220> that<00:20:35.460> I<00:20:35.580> got<00:20:35.700> from<00:20:35.760> the<00:20:35.880> cross 00:20:35.930 --> 00:20:35.940 align:start position:0% the L1 address that I got from the cross 00:20:35.940 --> 00:20:37.669 align:start position:0% the L1 address that I got from the cross chain<00:20:36.179> message<00:20:36.480> uh<00:20:36.960> gets<00:20:37.200> updated<00:20:37.380> with<00:20:37.559> this 00:20:37.669 --> 00:20:37.679 align:start position:0% chain message uh gets updated with this 00:20:37.679 --> 00:20:40.130 align:start position:0% chain message uh gets updated with this L2<00:20:37.980> address 00:20:40.130 --> 00:20:40.140 align:start position:0% L2 address 00:20:40.140 --> 00:20:41.750 align:start position:0% L2 address um<00:20:40.200> and<00:20:40.860> that's<00:20:40.980> basically<00:20:41.280> all<00:20:41.400> we<00:20:41.520> need<00:20:41.700> to 00:20:41.750 --> 00:20:41.760 align:start position:0% um and that's basically all we need to 00:20:41.760 --> 00:20:42.890 align:start position:0% um and that's basically all we need to do<00:20:41.880> there 00:20:42.890 --> 00:20:42.900 align:start position:0% do there 00:20:42.900 --> 00:20:43.669 align:start position:0% do there um 00:20:43.669 --> 00:20:43.679 align:start position:0% um 00:20:43.679 --> 00:20:45.830 align:start position:0% um now<00:20:44.400> uh<00:20:44.820> other<00:20:44.940> than<00:20:45.120> one<00:20:45.299> other<00:20:45.480> important 00:20:45.830 --> 00:20:45.840 align:start position:0% now uh other than one other important 00:20:45.840 --> 00:20:47.210 align:start position:0% now uh other than one other important thing<00:20:45.960> which<00:20:46.380> is<00:20:46.500> we<00:20:46.679> want<00:20:46.799> to<00:20:46.860> make<00:20:46.919> sure<00:20:47.100> that 00:20:47.210 --> 00:20:47.220 align:start position:0% thing which is we want to make sure that 00:20:47.220 --> 00:20:48.830 align:start position:0% thing which is we want to make sure that this<00:20:47.400> method<00:20:47.640> at<00:20:47.760> L2<00:20:48.059> can<00:20:48.299> only<00:20:48.419> be<00:20:48.539> called<00:20:48.660> as 00:20:48.830 --> 00:20:48.840 align:start position:0% this method at L2 can only be called as 00:20:48.840 --> 00:20:50.210 align:start position:0% this method at L2 can only be called as a<00:20:48.960> cross<00:20:49.080> chain<00:20:49.260> message<00:20:49.559> otherwise<00:20:50.039> this 00:20:50.210 --> 00:20:50.220 align:start position:0% a cross chain message otherwise this 00:20:50.220 --> 00:20:52.010 align:start position:0% a cross chain message otherwise this whole<00:20:50.400> thing<00:20:50.580> breaks 00:20:52.010 --> 00:20:52.020 align:start position:0% whole thing breaks 00:20:52.020 --> 00:20:53.570 align:start position:0% whole thing breaks um<00:20:52.080> so<00:20:52.380> we'll<00:20:52.500> add<00:20:52.679> this<00:20:52.860> only<00:20:53.100> counterpart 00:20:53.570 --> 00:20:53.580 align:start position:0% um so we'll add this only counterpart 00:20:53.580 --> 00:20:56.690 align:start position:0% um so we'll add this only counterpart Gateway<00:20:54.000> modifier 00:20:56.690 --> 00:20:56.700 align:start position:0% 00:20:56.700 --> 00:20:58.789 align:start position:0% and<00:20:57.059> now<00:20:57.179> we<00:20:57.360> have<00:20:57.480> to<00:20:57.600> fill<00:20:57.720> that<00:20:57.900> in 00:20:58.789 --> 00:20:58.799 align:start position:0% and now we have to fill that in 00:20:58.799 --> 00:21:01.010 align:start position:0% and now we have to fill that in I<00:20:59.160> think<00:20:59.280> I<00:20:59.460> still<00:20:59.640> have<00:20:59.880> to<00:21:00.000> do<00:21:00.059> here<00:21:00.299> no<00:21:00.840> more 00:21:01.010 --> 00:21:01.020 align:start position:0% I think I still have to do here no more 00:21:01.020 --> 00:21:02.810 align:start position:0% I think I still have to do here no more to<00:21:01.140> do<00:21:01.799> um 00:21:02.810 --> 00:21:02.820 align:start position:0% to do um 00:21:02.820 --> 00:21:05.150 align:start position:0% to do um so<00:21:03.179> only<00:21:03.299> count<00:21:03.480> up<00:21:03.660> our<00:21:03.780> Gateway<00:21:04.140> this<00:21:04.500> is 00:21:05.150 --> 00:21:05.160 align:start position:0% so only count up our Gateway this is 00:21:05.160 --> 00:21:06.049 align:start position:0% so only count up our Gateway this is um 00:21:06.049 --> 00:21:06.059 align:start position:0% um 00:21:06.059 --> 00:21:07.669 align:start position:0% um gonna<00:21:06.480> be<00:21:06.600> a<00:21:06.720> simple<00:21:06.840> required<00:21:07.320> check<00:21:07.440> just 00:21:07.669 --> 00:21:07.679 align:start position:0% gonna be a simple required check just 00:21:07.679 --> 00:21:12.169 align:start position:0% gonna be a simple required check just with<00:21:07.799> a<00:21:07.919> slight<00:21:08.160> gotcha 00:21:12.169 --> 00:21:12.179 align:start position:0% 00:21:12.179 --> 00:21:13.730 align:start position:0% so<00:21:12.480> here<00:21:12.660> we're<00:21:12.780> going<00:21:13.020> to<00:21:13.200> ensure<00:21:13.440> that<00:21:13.620> the 00:21:13.730 --> 00:21:13.740 align:start position:0% so here we're going to ensure that the 00:21:13.740 --> 00:21:15.590 align:start position:0% so here we're going to ensure that the message.cender<00:21:14.460> equals<00:21:15.000> this<00:21:15.179> thing<00:21:15.360> that 00:21:15.590 --> 00:21:15.600 align:start position:0% message.cender equals this thing that 00:21:15.600 --> 00:21:18.350 align:start position:0% message.cender equals this thing that we're<00:21:15.780> calling<00:21:16.080> counterpart<00:21:16.919> Gateway<00:21:17.280> L1<00:21:17.700> or 00:21:18.350 --> 00:21:18.360 align:start position:0% we're calling counterpart Gateway L1 or 00:21:18.360 --> 00:21:20.870 align:start position:0% we're calling counterpart Gateway L1 or counterpart<00:21:18.780> L1<00:21:19.140> Gateway<00:21:19.440> aliased 00:21:20.870 --> 00:21:20.880 align:start position:0% counterpart L1 Gateway aliased 00:21:20.880 --> 00:21:22.610 align:start position:0% counterpart L1 Gateway aliased so<00:21:21.299> notice<00:21:21.600> that<00:21:21.840> we<00:21:22.080> initialize<00:21:22.440> the 00:21:22.610 --> 00:21:22.620 align:start position:0% so notice that we initialize the 00:21:22.620 --> 00:21:24.169 align:start position:0% so notice that we initialize the contract<00:21:22.860> with<00:21:23.039> the<00:21:23.160> L1<00:21:23.400> Gateway<00:21:23.760> and<00:21:24.000> then<00:21:24.059> we 00:21:24.169 --> 00:21:24.179 align:start position:0% contract with the L1 Gateway and then we 00:21:24.179 --> 00:21:26.690 align:start position:0% contract with the L1 Gateway and then we do<00:21:24.360> this<00:21:24.539> thing<00:21:24.720> where<00:21:25.020> we<00:21:25.140> Alias<00:21:25.559> it 00:21:26.690 --> 00:21:26.700 align:start position:0% do this thing where we Alias it 00:21:26.700 --> 00:21:28.370 align:start position:0% do this thing where we Alias it um I'll<00:21:27.120> just<00:21:27.299> just<00:21:27.539> to<00:21:27.720> peek<00:21:27.960> at<00:21:28.020> this<00:21:28.200> real 00:21:28.370 --> 00:21:28.380 align:start position:0% um I'll just just to peek at this real 00:21:28.380 --> 00:21:30.110 align:start position:0% um I'll just just to peek at this real quick 00:21:30.110 --> 00:21:30.120 align:start position:0% quick 00:21:30.120 --> 00:21:32.029 align:start position:0% quick the<00:21:30.600> actual<00:21:30.840> aliasing<00:21:31.320> step<00:21:31.500> you'll<00:21:31.740> see<00:21:31.860> is 00:21:32.029 --> 00:21:32.039 align:start position:0% the actual aliasing step you'll see is 00:21:32.039 --> 00:21:34.010 align:start position:0% the actual aliasing step you'll see is just<00:21:32.220> like<00:21:32.460> adding<00:21:33.000> to<00:21:33.299> the<00:21:33.419> address<00:21:33.539> itself 00:21:34.010 --> 00:21:34.020 align:start position:0% just like adding to the address itself 00:21:34.020 --> 00:21:36.409 align:start position:0% just like adding to the address itself some<00:21:34.320> constant<00:21:34.679> offset<00:21:35.100> so<00:21:35.820> what's<00:21:36.059> going<00:21:36.240> on 00:21:36.409 --> 00:21:36.419 align:start position:0% some constant offset so what's going on 00:21:36.419 --> 00:21:37.430 align:start position:0% some constant offset so what's going on here 00:21:37.430 --> 00:21:37.440 align:start position:0% here 00:21:37.440 --> 00:21:39.649 align:start position:0% here is<00:21:38.640> um 00:21:39.649 --> 00:21:39.659 align:start position:0% is um 00:21:39.659 --> 00:21:41.090 align:start position:0% is um when<00:21:40.020> it<00:21:40.140> comes<00:21:40.260> to<00:21:40.380> cross<00:21:40.559> chain<00:21:40.740> messages 00:21:41.090 --> 00:21:41.100 align:start position:0% when it comes to cross chain messages 00:21:41.100 --> 00:21:43.250 align:start position:0% when it comes to cross chain messages the<00:21:41.940> way<00:21:42.059> that<00:21:42.179> the<00:21:42.299> sender<00:21:42.600> address<00:21:42.720> appears 00:21:43.250 --> 00:21:43.260 align:start position:0% the way that the sender address appears 00:21:43.260 --> 00:21:45.470 align:start position:0% the way that the sender address appears is<00:21:43.500> not<00:21:43.740> the<00:21:44.039> sender<00:21:44.340> of<00:21:44.460> the<00:21:44.520> L1<00:21:44.760> contract<00:21:45.240> and 00:21:45.470 --> 00:21:45.480 align:start position:0% is not the sender of the L1 contract and 00:21:45.480 --> 00:21:47.390 align:start position:0% is not the sender of the L1 contract and this<00:21:45.659> is<00:21:45.780> basically<00:21:46.080> so<00:21:46.380> that<00:21:46.620> on<00:21:47.280> the 00:21:47.390 --> 00:21:47.400 align:start position:0% this is basically so that on the 00:21:47.400 --> 00:21:48.529 align:start position:0% this is basically so that on the contract<00:21:47.640> level<00:21:47.880> we<00:21:48.179> can<00:21:48.240> easily 00:21:48.529 --> 00:21:48.539 align:start position:0% contract level we can easily 00:21:48.539 --> 00:21:50.330 align:start position:0% contract level we can easily differentiate<00:21:49.140> between<00:21:49.440> a<00:21:49.799> con<00:21:49.980> messages 00:21:50.330 --> 00:21:50.340 align:start position:0% differentiate between a con messages 00:21:50.340 --> 00:21:52.610 align:start position:0% differentiate between a con messages coming<00:21:50.640> from<00:21:50.820> L1<00:21:51.179> versus<00:21:51.780> messages<00:21:52.200> coming 00:21:52.610 --> 00:21:52.620 align:start position:0% coming from L1 versus messages coming 00:21:52.620 --> 00:21:54.590 align:start position:0% coming from L1 versus messages coming directly<00:21:52.919> from<00:21:53.100> L2<00:21:53.460> we<00:21:54.120> need<00:21:54.240> to<00:21:54.360> do<00:21:54.480> this 00:21:54.590 --> 00:21:54.600 align:start position:0% directly from L2 we need to do this 00:21:54.600 --> 00:21:57.529 align:start position:0% directly from L2 we need to do this because<00:21:54.840> arbitrim<00:21:56.000> contract<00:21:57.000> addresses<00:21:57.419> at 00:21:57.529 --> 00:21:57.539 align:start position:0% because arbitrim contract addresses at 00:21:57.539 --> 00:21:58.850 align:start position:0% because arbitrim contract addresses at Arboretum<00:21:57.960> are<00:21:58.080> computed<00:21:58.380> the<00:21:58.500> same<00:21:58.620> way<00:21:58.679> they 00:21:58.850 --> 00:21:58.860 align:start position:0% Arboretum are computed the same way they 00:21:58.860 --> 00:21:59.690 align:start position:0% Arboretum are computed the same way they are 00:21:59.690 --> 00:21:59.700 align:start position:0% are 00:21:59.700 --> 00:22:01.669 align:start position:0% are um<00:21:59.760> the<00:22:00.000> same<00:22:00.120> way<00:22:00.240> they<00:22:00.360> are<00:22:00.419> on<00:22:00.539> ethereum<00:22:00.960> so 00:22:01.669 --> 00:22:01.679 align:start position:0% um the same way they are on ethereum so 00:22:01.679 --> 00:22:03.110 align:start position:0% um the same way they are on ethereum so we<00:22:01.799> can<00:22:01.980> and<00:22:02.220> often<00:22:02.460> do<00:22:02.580> have<00:22:02.760> two<00:22:02.940> different 00:22:03.110 --> 00:22:03.120 align:start position:0% we can and often do have two different 00:22:03.120 --> 00:22:05.210 align:start position:0% we can and often do have two different contracts<00:22:03.659> you<00:22:03.960> know<00:22:04.020> one<00:22:04.140> at<00:22:04.320> L1<00:22:04.559> one<00:22:04.799> at<00:22:04.980> L2 00:22:05.210 --> 00:22:05.220 align:start position:0% contracts you know one at L1 one at L2 00:22:05.220 --> 00:22:06.830 align:start position:0% contracts you know one at L1 one at L2 that<00:22:05.460> share<00:22:05.820> the<00:22:05.940> same<00:22:06.059> address<00:22:06.299> so<00:22:06.600> if<00:22:06.720> you 00:22:06.830 --> 00:22:06.840 align:start position:0% that share the same address so if you 00:22:06.840 --> 00:22:08.330 align:start position:0% that share the same address so if you can't<00:22:06.960> differentiate<00:22:07.500> between<00:22:07.740> them<00:22:07.980> you 00:22:08.330 --> 00:22:08.340 align:start position:0% can't differentiate between them you 00:22:08.340 --> 00:22:09.470 align:start position:0% can't differentiate between them you could<00:22:08.460> get<00:22:08.580> all<00:22:08.700> sorts<00:22:08.880> of<00:22:08.940> weird<00:22:09.059> spoofing 00:22:09.470 --> 00:22:09.480 align:start position:0% could get all sorts of weird spoofing 00:22:09.480 --> 00:22:11.149 align:start position:0% could get all sorts of weird spoofing attacks<00:22:09.840> in<00:22:10.260> this<00:22:10.380> case<00:22:10.500> every<00:22:10.740> cross<00:22:10.980> chain 00:22:11.149 --> 00:22:11.159 align:start position:0% attacks in this case every cross chain 00:22:11.159 --> 00:22:12.590 align:start position:0% attacks in this case every cross chain message<00:22:11.400> kind<00:22:11.640> of<00:22:11.760> lives<00:22:11.940> in<00:22:12.059> its<00:22:12.240> own<00:22:12.299> address 00:22:12.590 --> 00:22:12.600 align:start position:0% message kind of lives in its own address 00:22:12.600 --> 00:22:15.110 align:start position:0% message kind of lives in its own address space<00:22:13.140> this<00:22:13.620> Alias<00:22:14.039> space<00:22:14.280> so<00:22:14.700> we<00:22:14.880> know<00:22:15.000> this 00:22:15.110 --> 00:22:15.120 align:start position:0% space this Alias space so we know this 00:22:15.120 --> 00:22:17.930 align:start position:0% space this Alias space so we know this is<00:22:15.299> definitely<00:22:15.480> coming<00:22:15.720> from<00:22:15.900> the<00:22:16.020> L1<00:22:16.260> Gateway 00:22:17.930 --> 00:22:17.940 align:start position:0% is definitely coming from the L1 Gateway 00:22:17.940 --> 00:22:20.570 align:start position:0% is definitely coming from the L1 Gateway um<00:22:18.000> cool<00:22:18.659> there's<00:22:18.900> our<00:22:19.080> registration<00:22:19.440> step 00:22:20.570 --> 00:22:20.580 align:start position:0% um cool there's our registration step 00:22:20.580 --> 00:22:21.649 align:start position:0% um cool there's our registration step um 00:22:21.649 --> 00:22:21.659 align:start position:0% um 00:22:21.659 --> 00:22:23.210 align:start position:0% um um yeah<00:22:22.020> any<00:22:22.260> questions<00:22:22.440> there<00:22:22.740> because 00:22:23.210 --> 00:22:23.220 align:start position:0% um yeah any questions there because 00:22:23.220 --> 00:22:28.490 align:start position:0% um yeah any questions there because that's<00:22:23.400> that's<00:22:23.640> kind<00:22:23.940> of<00:22:24.000> yeah 00:22:28.490 --> 00:22:28.500 align:start position:0% 00:22:28.500 --> 00:22:29.810 align:start position:0% if<00:22:28.860> you<00:22:28.919> didn't<00:22:29.039> yeah<00:22:29.280> so<00:22:29.460> if<00:22:29.520> we<00:22:29.640> didn't<00:22:29.700> do 00:22:29.810 --> 00:22:29.820 align:start position:0% if you didn't yeah so if we didn't do 00:22:29.820 --> 00:22:31.490 align:start position:0% if you didn't yeah so if we didn't do the<00:22:29.940> like<00:22:30.179> if<00:22:30.419> aliasing<00:22:31.020> wasn't<00:22:31.200> part<00:22:31.320> of<00:22:31.440> the 00:22:31.490 --> 00:22:31.500 align:start position:0% the like if aliasing wasn't part of the 00:22:31.500 --> 00:22:33.049 align:start position:0% the like if aliasing wasn't part of the arbitrine<00:22:31.860> protocol<00:22:32.100> for<00:22:32.400> example<00:22:32.580> if<00:22:32.880> the 00:22:33.049 --> 00:22:33.059 align:start position:0% arbitrine protocol for example if the 00:22:33.059 --> 00:22:35.029 align:start position:0% arbitrine protocol for example if the message.sender<00:22:33.659> was<00:22:33.960> just<00:22:34.260> the<00:22:34.679> address<00:22:34.799> from 00:22:35.029 --> 00:22:35.039 align:start position:0% message.sender was just the address from 00:22:35.039 --> 00:22:38.090 align:start position:0% message.sender was just the address from L1<00:22:35.460> then<00:22:36.360> the<00:22:37.080> uh<00:22:37.200> the<00:22:37.440> deployers<00:22:37.799> of<00:22:37.980> this 00:22:38.090 --> 00:22:38.100 align:start position:0% L1 then the uh the deployers of this 00:22:38.100 --> 00:22:39.110 align:start position:0% L1 then the uh the deployers of this contract<00:22:38.400> let's<00:22:38.580> say<00:22:38.700> if<00:22:38.880> they<00:22:39.000> were 00:22:39.110 --> 00:22:39.120 align:start position:0% contract let's say if they were 00:22:39.120 --> 00:22:40.549 align:start position:0% contract let's say if they were malicious<00:22:39.539> they<00:22:40.020> could<00:22:40.140> deploy<00:22:40.380> something 00:22:40.549 --> 00:22:40.559 align:start position:0% malicious they could deploy something 00:22:40.559 --> 00:22:42.649 align:start position:0% malicious they could deploy something else<00:22:40.740> at<00:22:40.860> L2<00:22:41.220> at<00:22:41.400> the<00:22:41.460> same<00:22:41.580> address 00:22:42.649 --> 00:22:42.659 align:start position:0% else at L2 at the same address 00:22:42.659 --> 00:22:44.510 align:start position:0% else at L2 at the same address that<00:22:43.140> and<00:22:43.320> then<00:22:43.500> you<00:22:43.740> know<00:22:43.860> it<00:22:44.159> becomes<00:22:44.400> very 00:22:44.510 --> 00:22:44.520 align:start position:0% that and then you know it becomes very 00:22:44.520 --> 00:22:45.710 align:start position:0% that and then you know it becomes very hard<00:22:44.700> to<00:22:44.760> reason<00:22:44.880> about<00:22:45.179> the<00:22:45.360> risks<00:22:45.659> there 00:22:45.710 --> 00:22:45.720 align:start position:0% hard to reason about the risks there 00:22:45.720 --> 00:22:46.549 align:start position:0% hard to reason about the risks there yeah 00:22:46.549 --> 00:22:46.559 align:start position:0% yeah 00:22:46.559 --> 00:22:47.930 align:start position:0% yeah um so<00:22:46.740> this<00:22:46.860> way<00:22:46.980> it's<00:22:47.159> protecting<00:22:47.700> you<00:22:47.820> from 00:22:47.930 --> 00:22:47.940 align:start position:0% um so this way it's protecting you from 00:22:47.940 --> 00:22:49.610 align:start position:0% um so this way it's protecting you from malicious<00:22:48.240> developers<00:22:48.659> basically<00:22:49.020> which<00:22:49.500> is 00:22:49.610 --> 00:22:49.620 align:start position:0% malicious developers basically which is 00:22:49.620 --> 00:22:50.570 align:start position:0% malicious developers basically which is a<00:22:49.740> good<00:22:49.860> thing<00:22:49.980> to<00:22:50.100> protect<00:22:50.340> you<00:22:50.460> from 00:22:50.570 --> 00:22:50.580 align:start position:0% a good thing to protect you from 00:22:50.580 --> 00:22:52.970 align:start position:0% a good thing to protect you from anything<00:22:50.760> else 00:22:52.970 --> 00:22:52.980 align:start position:0% anything else 00:22:52.980 --> 00:22:54.649 align:start position:0% anything else cool<00:22:53.580> okay<00:22:53.880> so<00:22:54.120> there's<00:22:54.240> our<00:22:54.360> first<00:22:54.480> there's 00:22:54.649 --> 00:22:54.659 align:start position:0% cool okay so there's our first there's 00:22:54.659 --> 00:22:55.789 align:start position:0% cool okay so there's our first there's our<00:22:54.840> first<00:22:54.900> cross<00:22:55.080> chain<00:22:55.320> message<00:22:55.559> just 00:22:55.789 --> 00:22:55.799 align:start position:0% our first cross chain message just 00:22:55.799 --> 00:22:57.890 align:start position:0% our first cross chain message just simply<00:22:56.039> doing<00:22:56.159> the<00:22:56.400> registration 00:22:57.890 --> 00:22:57.900 align:start position:0% simply doing the registration 00:22:57.900 --> 00:23:00.409 align:start position:0% simply doing the registration um<00:22:57.960> let's<00:22:58.620> do<00:22:58.980> the<00:22:59.340> deposit<00:22:59.820> so<00:23:00.179> this<00:23:00.299> will 00:23:00.409 --> 00:23:00.419 align:start position:0% um let's do the deposit so this will 00:23:00.419 --> 00:23:02.570 align:start position:0% um let's do the deposit so this will also<00:23:00.600> be<00:23:00.720> an<00:23:00.780> L1<00:23:01.020> tile<00:23:01.260> two<00:23:01.440> message 00:23:02.570 --> 00:23:02.580 align:start position:0% also be an L1 tile two message 00:23:02.580 --> 00:23:04.310 align:start position:0% also be an L1 tile two message um<00:23:02.700> and<00:23:03.120> uh<00:23:03.419> it'll<00:23:03.659> look<00:23:03.780> fairly<00:23:04.020> similar 00:23:04.310 --> 00:23:04.320 align:start position:0% um and uh it'll look fairly similar 00:23:04.320 --> 00:23:06.049 align:start position:0% um and uh it'll look fairly similar actually<00:23:04.500> let<00:23:05.039> me<00:23:05.220> just<00:23:05.340> make<00:23:05.760> sure<00:23:05.940> this 00:23:06.049 --> 00:23:06.059 align:start position:0% actually let me just make sure this 00:23:06.059 --> 00:23:07.970 align:start position:0% actually let me just make sure this compiles<00:23:06.419> again<00:23:06.539> because<00:23:06.780> I'm<00:23:07.559> not<00:23:07.740> using 00:23:07.970 --> 00:23:07.980 align:start position:0% compiles again because I'm not using 00:23:07.980 --> 00:23:10.190 align:start position:0% compiles again because I'm not using remix<00:23:08.159> and<00:23:08.520> I'm<00:23:08.640> paranoid<00:23:09.059> okay 00:23:10.190 --> 00:23:10.200 align:start position:0% remix and I'm paranoid okay 00:23:10.200 --> 00:23:12.110 align:start position:0% remix and I'm paranoid okay um<00:23:10.320> I'm<00:23:10.919> just<00:23:11.100> running<00:23:11.280> just<00:23:11.640> compiling<00:23:12.000> with 00:23:12.110 --> 00:23:12.120 align:start position:0% um I'm just running just compiling with 00:23:12.120 --> 00:23:14.570 align:start position:0% um I'm just running just compiling with hard<00:23:12.240> hat<00:23:12.960> um 00:23:14.570 --> 00:23:14.580 align:start position:0% hard hat um 00:23:14.580 --> 00:23:16.730 align:start position:0% hard hat um cool<00:23:15.000> okay<00:23:15.299> so<00:23:15.419> our<00:23:15.600> L1<00:23:15.840> token<00:23:16.140> registered<00:23:16.500> so 00:23:16.730 --> 00:23:16.740 align:start position:0% cool okay so our L1 token registered so 00:23:16.740 --> 00:23:18.049 align:start position:0% cool okay so our L1 token registered so now<00:23:16.860> we're<00:23:17.039> going<00:23:17.159> to<00:23:17.220> assume<00:23:17.580> or<00:23:17.760> we're<00:23:17.940> not 00:23:18.049 --> 00:23:18.059 align:start position:0% now we're going to assume or we're not 00:23:18.059 --> 00:23:19.789 align:start position:0% now we're going to assume or we're not going<00:23:18.179> to<00:23:18.179> assume<00:23:18.480> anything<00:23:18.539> but<00:23:18.960> if<00:23:19.679> this 00:23:19.789 --> 00:23:19.799 align:start position:0% going to assume anything but if this 00:23:19.799 --> 00:23:21.529 align:start position:0% going to assume anything but if this token<00:23:20.159> is<00:23:20.520> indeed<00:23:20.760> registered<00:23:21.059> it<00:23:21.240> can<00:23:21.299> do<00:23:21.419> a 00:23:21.529 --> 00:23:21.539 align:start position:0% token is indeed registered it can do a 00:23:21.539 --> 00:23:23.930 align:start position:0% token is indeed registered it can do a deposit 00:23:23.930 --> 00:23:23.940 align:start position:0% 00:23:23.940 --> 00:23:25.669 align:start position:0% um let<00:23:24.419> me<00:23:24.480> just 00:23:25.669 --> 00:23:25.679 align:start position:0% um let me just 00:23:25.679 --> 00:23:28.850 align:start position:0% um let me just make<00:23:26.159> sure<00:23:26.280> I<00:23:26.460> didn't<00:23:26.520> forget<00:23:26.760> anything<00:23:27.000> cool 00:23:28.850 --> 00:23:28.860 align:start position:0% make sure I didn't forget anything cool 00:23:28.860 --> 00:23:31.190 align:start position:0% make sure I didn't forget anything cool okay<00:23:29.280> so<00:23:29.820> um<00:23:29.880> now<00:23:30.000> we're<00:23:30.120> gonna<00:23:30.240> deposit<00:23:30.720> so 00:23:31.190 --> 00:23:31.200 align:start position:0% okay so um now we're gonna deposit so 00:23:31.200 --> 00:23:32.990 align:start position:0% okay so um now we're gonna deposit so you<00:23:31.320> can<00:23:31.440> see<00:23:31.559> it<00:23:31.679> as<00:23:31.919> once<00:23:32.340> again<00:23:32.400> the<00:23:32.700> L1 00:23:32.990 --> 00:23:33.000 align:start position:0% you can see it as once again the L1 00:23:33.000 --> 00:23:34.490 align:start position:0% you can see it as once again the L1 contract<00:23:33.480> is<00:23:33.659> the<00:23:33.780> source<00:23:34.020> of<00:23:34.080> truth<00:23:34.260> that's 00:23:34.490 --> 00:23:34.500 align:start position:0% contract is the source of truth that's 00:23:34.500 --> 00:23:35.810 align:start position:0% contract is the source of truth that's what<00:23:34.679> we<00:23:34.799> use<00:23:34.980> so<00:23:35.159> that's<00:23:35.340> what's<00:23:35.400> passed<00:23:35.700> in 00:23:35.810 --> 00:23:35.820 align:start position:0% what we use so that's what's passed in 00:23:35.820 --> 00:23:37.070 align:start position:0% what we use so that's what's passed in as<00:23:35.940> a<00:23:36.120> parameter 00:23:37.070 --> 00:23:37.080 align:start position:0% as a parameter 00:23:37.080 --> 00:23:38.510 align:start position:0% as a parameter um so<00:23:37.260> we'll<00:23:37.380> use<00:23:37.559> that<00:23:37.740> to<00:23:37.860> look<00:23:37.980> up<00:23:38.100> the<00:23:38.220> L2 00:23:38.510 --> 00:23:38.520 align:start position:0% um so we'll use that to look up the L2 00:23:38.520 --> 00:23:41.090 align:start position:0% um so we'll use that to look up the L2 address<00:23:38.960> uh<00:23:39.960> first 00:23:41.090 --> 00:23:41.100 align:start position:0% address uh first 00:23:41.100 --> 00:23:44.570 align:start position:0% address uh first so<00:23:41.580> let's<00:23:41.760> say<00:23:42.000> L2<00:23:42.480> address 00:23:44.570 --> 00:23:44.580 align:start position:0% so let's say L2 address 00:23:44.580 --> 00:23:46.250 align:start position:0% so let's say L2 address equals<00:23:45.360> uh<00:23:45.539> we'll<00:23:45.720> look<00:23:45.840> it<00:23:45.960> up<00:23:46.020> in<00:23:46.140> the 00:23:46.250 --> 00:23:46.260 align:start position:0% equals uh we'll look it up in the 00:23:46.260 --> 00:23:47.450 align:start position:0% equals uh we'll look it up in the mapping 00:23:47.450 --> 00:23:47.460 align:start position:0% mapping 00:23:47.460 --> 00:23:49.789 align:start position:0% mapping but<00:23:47.760> we<00:23:48.000> just<00:23:48.120> saw<00:23:48.299> the<00:23:48.539> registration<00:23:48.900> step<00:23:49.260> go 00:23:49.789 --> 00:23:49.799 align:start position:0% but we just saw the registration step go 00:23:49.799 --> 00:23:52.789 align:start position:0% but we just saw the registration step go down<00:23:49.980> and 00:23:52.789 --> 00:23:52.799 align:start position:0% 00:23:52.799 --> 00:23:54.470 align:start position:0% yes 00:23:54.470 --> 00:23:54.480 align:start position:0% yes 00:23:54.480 --> 00:23:55.430 align:start position:0% yes um<00:23:54.539> and<00:23:54.720> now<00:23:54.840> we're<00:23:54.960> just<00:23:55.080> going<00:23:55.200> to<00:23:55.200> make<00:23:55.320> sure 00:23:55.430 --> 00:23:55.440 align:start position:0% um and now we're just going to make sure 00:23:55.440 --> 00:23:56.990 align:start position:0% um and now we're just going to make sure it's<00:23:55.559> actually<00:23:55.740> registered 00:23:56.990 --> 00:23:57.000 align:start position:0% it's actually registered 00:23:57.000 --> 00:23:57.890 align:start position:0% it's actually registered um 00:23:57.890 --> 00:23:57.900 align:start position:0% um 00:23:57.900 --> 00:24:00.350 align:start position:0% um so<00:23:58.380> just<00:23:58.620> require<00:23:58.860> that<00:23:59.400> this<00:23:59.820> thing<00:24:00.059> is 00:24:00.350 --> 00:24:00.360 align:start position:0% so just require that this thing is 00:24:00.360 --> 00:24:02.930 align:start position:0% so just require that this thing is really<00:24:00.600> an<00:24:00.780> address 00:24:02.930 --> 00:24:02.940 align:start position:0% really an address 00:24:02.940 --> 00:24:05.930 align:start position:0% really an address L2<00:24:03.780> address 00:24:05.930 --> 00:24:05.940 align:start position:0% L2 address 00:24:05.940 --> 00:24:15.289 align:start position:0% L2 address um 00:24:15.289 --> 00:24:15.299 align:start position:0% 00:24:15.299 --> 00:24:18.350 align:start position:0% register<00:24:15.960> okay 00:24:18.350 --> 00:24:18.360 align:start position:0% register okay 00:24:18.360 --> 00:24:19.010 align:start position:0% register okay um 00:24:19.010 --> 00:24:19.020 align:start position:0% um 00:24:19.020 --> 00:24:21.649 align:start position:0% um so<00:24:19.679> cool<00:24:19.919> if<00:24:20.159> our<00:24:20.340> token<00:24:20.580> is<00:24:20.700> registered<00:24:21.059> our 00:24:21.649 --> 00:24:21.659 align:start position:0% so cool if our token is registered our 00:24:21.659 --> 00:24:23.630 align:start position:0% so cool if our token is registered our L1<00:24:22.020> token<00:24:22.320> opt-in<00:24:22.620> we<00:24:23.100> inherit<00:24:23.460> whatever 00:24:23.630 --> 00:24:23.640 align:start position:0% L1 token opt-in we inherit whatever 00:24:23.640 --> 00:24:26.270 align:start position:0% L1 token opt-in we inherit whatever assumptions<00:24:24.120> Helen<00:24:24.480> token<00:24:24.780> is<00:24:24.840> making<00:24:24.960> again 00:24:26.270 --> 00:24:26.280 align:start position:0% assumptions Helen token is making again 00:24:26.280 --> 00:24:28.130 align:start position:0% assumptions Helen token is making again um<00:24:26.400> now<00:24:26.760> we<00:24:26.880> can<00:24:27.000> proceed<00:24:27.299> so<00:24:27.780> we<00:24:27.900> can<00:24:28.020> actually 00:24:28.130 --> 00:24:28.140 align:start position:0% um now we can proceed so we can actually 00:24:28.140 --> 00:24:31.310 align:start position:0% um now we can proceed so we can actually do<00:24:28.440> our<00:24:28.860> our<00:24:29.640> um<00:24:29.640> our<00:24:29.880> deposit<00:24:30.299> so<00:24:30.840> deposit 00:24:31.310 --> 00:24:31.320 align:start position:0% do our our um our deposit so deposit 00:24:31.320 --> 00:24:32.510 align:start position:0% do our our um our deposit so deposit again<00:24:31.380> and<00:24:31.559> tells<00:24:31.799> these<00:24:31.919> two<00:24:32.039> things<00:24:32.220> we're 00:24:32.510 --> 00:24:32.520 align:start position:0% again and tells these two things we're 00:24:32.520 --> 00:24:34.070 align:start position:0% again and tells these two things we're going<00:24:32.640> to<00:24:32.760> Escrow<00:24:33.120> the<00:24:33.360> token<00:24:33.600> here<00:24:33.720> send<00:24:33.960> the 00:24:34.070 --> 00:24:34.080 align:start position:0% going to Escrow the token here send the 00:24:34.080 --> 00:24:36.470 align:start position:0% going to Escrow the token here send the token<00:24:34.440> to<00:24:34.740> this<00:24:35.039> contract 00:24:36.470 --> 00:24:36.480 align:start position:0% token to this contract 00:24:36.480 --> 00:24:38.210 align:start position:0% token to this contract um<00:24:36.600> yeah 00:24:38.210 --> 00:24:38.220 align:start position:0% um yeah 00:24:38.220 --> 00:24:42.350 align:start position:0% um yeah we<00:24:38.760> have<00:24:38.940> our<00:24:39.179> 721<00:24:40.020> 721<00:24:40.620> interface<00:24:41.039> imported 00:24:42.350 --> 00:24:42.360 align:start position:0% we have our 721 721 interface imported 00:24:42.360 --> 00:24:43.190 align:start position:0% we have our 721 721 interface imported um 00:24:43.190 --> 00:24:43.200 align:start position:0% um 00:24:43.200 --> 00:24:46.010 align:start position:0% um so<00:24:43.919> we'll<00:24:44.220> uh<00:24:44.640> connect<00:24:44.820> to<00:24:45.059> it<00:24:45.240> at<00:24:45.539> the<00:24:45.659> L1 00:24:46.010 --> 00:24:46.020 align:start position:0% so we'll uh connect to it at the L1 00:24:46.020 --> 00:24:51.830 align:start position:0% so we'll uh connect to it at the L1 token<00:24:46.620> address 00:24:51.830 --> 00:24:51.840 align:start position:0% 00:24:51.840 --> 00:24:55.310 align:start position:0% and<00:24:52.500> do<00:24:52.679> save<00:24:52.919> transfer<00:24:53.580> from 00:24:55.310 --> 00:24:55.320 align:start position:0% and do save transfer from 00:24:55.320 --> 00:24:58.730 align:start position:0% and do save transfer from uh<00:24:56.220> from<00:24:56.400> two<00:24:56.580> token<00:24:57.000> ID<00:24:57.120> yeah<00:24:57.419> so<00:24:57.600> from<00:24:57.840> the<00:24:58.200> uh 00:24:58.730 --> 00:24:58.740 align:start position:0% uh from two token ID yeah so from the uh 00:24:58.740 --> 00:25:00.529 align:start position:0% uh from two token ID yeah so from the uh from<00:24:59.220> the<00:24:59.400> sender 00:25:00.529 --> 00:25:00.539 align:start position:0% from the sender 00:25:00.539 --> 00:25:03.770 align:start position:0% from the sender the<00:25:00.840> caller<00:25:01.080> will<00:25:01.200> deposit 00:25:03.770 --> 00:25:03.780 align:start position:0% 00:25:03.780 --> 00:25:06.890 align:start position:0% to<00:25:04.320> this<00:25:04.559> contract<00:25:04.919> this<00:25:05.400> is<00:25:05.460> the<00:25:05.580> escrow 00:25:06.890 --> 00:25:06.900 align:start position:0% to this contract this is the escrow 00:25:06.900 --> 00:25:08.390 align:start position:0% to this contract this is the escrow so<00:25:07.320> here 00:25:08.390 --> 00:25:08.400 align:start position:0% so here 00:25:08.400 --> 00:25:10.490 align:start position:0% so here here 00:25:10.490 --> 00:25:10.500 align:start position:0% here 00:25:10.500 --> 00:25:11.330 align:start position:0% here um 00:25:11.330 --> 00:25:11.340 align:start position:0% um 00:25:11.340 --> 00:25:14.990 align:start position:0% um and<00:25:11.880> the<00:25:12.120> token<00:25:12.419> ID 00:25:14.990 --> 00:25:15.000 align:start position:0% 00:25:15.000 --> 00:25:17.029 align:start position:0% yes 00:25:17.029 --> 00:25:17.039 align:start position:0% yes 00:25:17.039 --> 00:25:18.529 align:start position:0% yes cool<00:25:17.520> so<00:25:17.760> there's<00:25:17.880> the<00:25:18.120> first<00:25:18.179> half<00:25:18.299> of<00:25:18.480> our 00:25:18.529 --> 00:25:18.539 align:start position:0% cool so there's the first half of our 00:25:18.539 --> 00:25:19.789 align:start position:0% cool so there's the first half of our deposit 00:25:19.789 --> 00:25:19.799 align:start position:0% deposit 00:25:19.799 --> 00:25:21.289 align:start position:0% deposit and<00:25:20.340> now<00:25:20.520> very<00:25:20.700> similarly<00:25:21.000> we're<00:25:21.179> going<00:25:21.299> to 00:25:21.289 --> 00:25:21.299 align:start position:0% and now very similarly we're going to 00:25:21.299 --> 00:25:23.750 align:start position:0% and now very similarly we're going to send<00:25:21.419> a<00:25:21.600> cross<00:25:21.659> train<00:25:21.840> message<00:25:22.080> to<00:25:22.320> L2 00:25:23.750 --> 00:25:23.760 align:start position:0% send a cross train message to L2 00:25:23.760 --> 00:25:26.510 align:start position:0% send a cross train message to L2 um<00:25:24.179> again<00:25:24.600> we're<00:25:25.440> going<00:25:25.620> to<00:25:25.740> need<00:25:25.919> so<00:25:26.220> we<00:25:26.400> have 00:25:26.510 --> 00:25:26.520 align:start position:0% um again we're going to need so we have 00:25:26.520 --> 00:25:28.669 align:start position:0% um again we're going to need so we have similar<00:25:27.059> parameters<00:25:27.600> here<00:25:27.840> the<00:25:28.140> gas<00:25:28.260> Brands 00:25:28.669 --> 00:25:28.679 align:start position:0% similar parameters here the gas Brands 00:25:28.679 --> 00:25:31.130 align:start position:0% similar parameters here the gas Brands the<00:25:28.740> refund<00:25:29.100> address<00:25:29.279> all<00:25:30.120> the<00:25:30.360> sort<00:25:30.600> of<00:25:30.720> gas 00:25:31.130 --> 00:25:31.140 align:start position:0% the refund address all the sort of gas 00:25:31.140 --> 00:25:33.230 align:start position:0% the refund address all the sort of gas specific<00:25:31.559> stuff<00:25:31.860> once<00:25:32.700> again<00:25:32.760> we<00:25:33.000> need<00:25:33.120> to 00:25:33.230 --> 00:25:33.240 align:start position:0% specific stuff once again we need to 00:25:33.240 --> 00:25:34.610 align:start position:0% specific stuff once again we need to encode<00:25:33.600> the<00:25:33.900> call<00:25:34.020> that<00:25:34.260> we're<00:25:34.380> going<00:25:34.500> to<00:25:34.559> make 00:25:34.610 --> 00:25:34.620 align:start position:0% encode the call that we're going to make 00:25:34.620 --> 00:25:36.649 align:start position:0% encode the call that we're going to make on<00:25:34.799> L2<00:25:35.159> which<00:25:35.700> we<00:25:35.820> will<00:25:35.940> do<00:25:36.120> in<00:25:36.240> a<00:25:36.419> function 00:25:36.649 --> 00:25:36.659 align:start position:0% on L2 which we will do in a function 00:25:36.659 --> 00:25:38.210 align:start position:0% on L2 which we will do in a function here 00:25:38.210 --> 00:25:38.220 align:start position:0% here 00:25:38.220 --> 00:25:39.830 align:start position:0% here um<00:25:38.340> so<00:25:38.580> this<00:25:38.760> is<00:25:38.820> basically<00:25:39.120> again<00:25:39.419> just<00:25:39.659> think 00:25:39.830 --> 00:25:39.840 align:start position:0% um so this is basically again just think 00:25:39.840 --> 00:25:41.269 align:start position:0% um so this is basically again just think of<00:25:39.960> this<00:25:40.080> as<00:25:40.200> like<00:25:40.380> the<00:25:40.559> information<00:25:40.740> that<00:25:41.159> we 00:25:41.269 --> 00:25:41.279 align:start position:0% of this as like the information that we 00:25:41.279 --> 00:25:44.149 align:start position:0% of this as like the information that we need<00:25:41.400> to<00:25:41.520> send<00:25:41.640> to<00:25:41.760> L2<00:25:42.500> and<00:25:43.500> the<00:25:43.799> actual 00:25:44.149 --> 00:25:44.159 align:start position:0% need to send to L2 and the actual 00:25:44.159 --> 00:25:46.490 align:start position:0% need to send to L2 and the actual function<00:25:44.580> we're<00:25:44.820> going<00:25:45.059> to<00:25:45.179> be<00:25:45.419> triggering<00:25:46.020> on 00:25:46.490 --> 00:25:46.500 align:start position:0% function we're going to be triggering on 00:25:46.500 --> 00:25:47.750 align:start position:0% function we're going to be triggering on L2 00:25:47.750 --> 00:25:47.760 align:start position:0% L2 00:25:47.760 --> 00:25:50.210 align:start position:0% L2 is<00:25:48.360> called<00:25:48.659> finalized<00:25:49.260> deposit<00:25:49.620> and<00:25:49.860> there<00:25:50.039> it 00:25:50.210 --> 00:25:50.220 align:start position:0% is called finalized deposit and there it 00:25:50.220 --> 00:25:52.490 align:start position:0% is called finalized deposit and there it is<00:25:50.340> okay<00:25:50.880> so<00:25:51.419> let's<00:25:51.539> encode<00:25:51.840> the<00:25:52.020> call<00:25:52.140> to<00:25:52.320> that 00:25:52.490 --> 00:25:52.500 align:start position:0% is okay so let's encode the call to that 00:25:52.500 --> 00:25:56.450 align:start position:0% is okay so let's encode the call to that now<00:25:52.740> again<00:25:53.460> as<00:25:53.700> a<00:25:53.880> separate<00:25:54.179> function 00:25:56.450 --> 00:25:56.460 align:start position:0% 00:25:56.460 --> 00:25:57.470 align:start position:0% um 00:25:57.470 --> 00:25:57.480 align:start position:0% um 00:25:57.480 --> 00:25:59.630 align:start position:0% um code<00:25:57.960> selector 00:25:59.630 --> 00:25:59.640 align:start position:0% code selector 00:25:59.640 --> 00:26:01.730 align:start position:0% code selector awkward<00:26:00.000> autofill 00:26:01.730 --> 00:26:01.740 align:start position:0% awkward autofill 00:26:01.740 --> 00:26:02.990 align:start position:0% awkward autofill um 00:26:02.990 --> 00:26:03.000 align:start position:0% um 00:26:03.000 --> 00:26:07.010 align:start position:0% um so<00:26:03.299> just<00:26:03.539> like<00:26:03.720> before 00:26:07.010 --> 00:26:07.020 align:start position:0% 00:26:07.020 --> 00:26:09.470 align:start position:0% awkward<00:26:07.440> autofill 00:26:09.470 --> 00:26:09.480 align:start position:0% awkward autofill 00:26:09.480 --> 00:26:11.570 align:start position:0% awkward autofill um<00:26:09.600> and<00:26:10.260> it's<00:26:10.440> the<00:26:10.679> same<00:26:10.980> parameters<00:26:11.279> in<00:26:11.460> the 00:26:11.570 --> 00:26:11.580 align:start position:0% um and it's the same parameters in the 00:26:11.580 --> 00:26:13.789 align:start position:0% um and it's the same parameters in the same<00:26:11.700> order<00:26:11.880> uh<00:26:12.419> so<00:26:12.480> yeah<00:26:12.659> function<00:26:13.080> selector 00:26:13.789 --> 00:26:13.799 align:start position:0% same order uh so yeah function selector 00:26:13.799 --> 00:26:17.870 align:start position:0% same order uh so yeah function selector here 00:26:17.870 --> 00:26:17.880 align:start position:0% 00:26:17.880 --> 00:26:22.549 align:start position:0% and<00:26:18.059> it's<00:26:18.360> just<00:26:18.480> yeah<00:26:18.720> all<00:26:19.020> these 00:26:22.549 --> 00:26:22.559 align:start position:0% 00:26:22.559 --> 00:26:27.110 align:start position:0% so<00:26:23.100> this<00:26:23.400> gets<00:26:23.700> encoded 00:26:27.110 --> 00:26:27.120 align:start position:0% 00:26:27.120 --> 00:26:29.210 align:start position:0% um 00:26:29.210 --> 00:26:29.220 align:start position:0% 00:26:29.220 --> 00:26:32.630 align:start position:0% yes 00:26:32.630 --> 00:26:32.640 align:start position:0% 00:26:32.640 --> 00:26:35.450 align:start position:0% now<00:26:33.120> let's<00:26:33.299> grab<00:26:33.840> that 00:26:35.450 --> 00:26:35.460 align:start position:0% now let's grab that 00:26:35.460 --> 00:26:38.570 align:start position:0% now let's grab that um 00:26:38.570 --> 00:26:38.580 align:start position:0% 00:26:38.580 --> 00:26:41.390 align:start position:0% so<00:26:39.059> we<00:26:39.240> have<00:26:39.419> our<00:26:39.840> uh<00:26:40.380> what<00:26:40.860> I<00:26:41.039> call<00:26:41.159> it<00:26:41.279> before 00:26:41.390 --> 00:26:41.400 align:start position:0% so we have our uh what I call it before 00:26:41.400 --> 00:26:43.669 align:start position:0% so we have our uh what I call it before a<00:26:42.179> little<00:26:42.360> two<00:26:42.720> message<00:26:42.960> call<00:26:43.200> data<00:26:43.559> or 00:26:43.669 --> 00:26:43.679 align:start position:0% a little two message call data or 00:26:43.679 --> 00:26:45.049 align:start position:0% a little two message call data or something 00:26:45.049 --> 00:26:45.059 align:start position:0% something 00:26:45.059 --> 00:26:46.549 align:start position:0% something in<00:26:45.360> fact<00:26:45.480> I<00:26:45.720> want<00:26:45.840> to<00:26:45.960> call<00:26:46.020> it<00:26:46.140> the<00:26:46.260> same<00:26:46.380> thing 00:26:46.549 --> 00:26:46.559 align:start position:0% in fact I want to call it the same thing 00:26:46.559 --> 00:26:48.590 align:start position:0% in fact I want to call it the same thing so<00:26:46.799> I<00:26:46.980> can<00:26:47.100> be<00:26:47.220> lazy<00:26:47.580> later<00:26:47.700> I'll<00:26:48.120> do<00:26:48.419> a<00:26:48.480> message 00:26:48.590 --> 00:26:48.600 align:start position:0% so I can be lazy later I'll do a message 00:26:48.600 --> 00:26:50.029 align:start position:0% so I can be lazy later I'll do a message called<00:26:48.779> Data<00:26:49.140> yes 00:26:50.029 --> 00:26:50.039 align:start position:0% called Data yes 00:26:50.039 --> 00:26:51.409 align:start position:0% called Data yes um 00:26:51.409 --> 00:26:51.419 align:start position:0% um 00:26:51.419 --> 00:26:53.390 align:start position:0% um and<00:26:51.960> we<00:26:52.140> pass<00:26:52.380> in<00:26:52.500> the<00:26:52.620> parameters<00:26:52.980> so<00:26:53.220> this 00:26:53.390 --> 00:26:53.400 align:start position:0% and we pass in the parameters so this 00:26:53.400 --> 00:26:56.570 align:start position:0% and we pass in the parameters so this was<00:26:53.520> L1<00:26:54.000> token 00:26:56.570 --> 00:26:56.580 align:start position:0% was L1 token 00:26:56.580 --> 00:26:59.630 align:start position:0% was L1 token L2<00:26:57.539> address 00:26:59.630 --> 00:26:59.640 align:start position:0% L2 address 00:26:59.640 --> 00:27:02.570 align:start position:0% L2 address token<00:27:00.480> ID 00:27:02.570 --> 00:27:02.580 align:start position:0% token ID 00:27:02.580 --> 00:27:06.169 align:start position:0% token ID and<00:27:02.880> two<00:27:03.059> two<00:27:03.299> is<00:27:03.539> the<00:27:03.659> sort<00:27:03.840> of<00:27:04.200> um 00:27:06.169 --> 00:27:06.179 align:start position:0% and two two is the sort of um 00:27:06.179 --> 00:27:08.029 align:start position:0% and two two is the sort of um the<00:27:06.600> address<00:27:06.659> at<00:27:06.960> which<00:27:07.140> we'll<00:27:07.320> be<00:27:07.500> depositing 00:27:08.029 --> 00:27:08.039 align:start position:0% the address at which we'll be depositing 00:27:08.039 --> 00:27:09.529 align:start position:0% the address at which we'll be depositing the<00:27:08.220> token<00:27:08.580> the<00:27:08.760> sort<00:27:08.880> of<00:27:09.000> receiver<00:27:09.240> of<00:27:09.419> the 00:27:09.529 --> 00:27:09.539 align:start position:0% the token the sort of receiver of the 00:27:09.539 --> 00:27:11.390 align:start position:0% the token the sort of receiver of the token<00:27:09.720> at<00:27:09.840> L2 00:27:11.390 --> 00:27:11.400 align:start position:0% token at L2 00:27:11.400 --> 00:27:12.470 align:start position:0% token at L2 um 00:27:12.470 --> 00:27:12.480 align:start position:0% um 00:27:12.480 --> 00:27:13.730 align:start position:0% um okay 00:27:13.730 --> 00:27:13.740 align:start position:0% okay 00:27:13.740 --> 00:27:16.610 align:start position:0% okay cool<00:27:14.100> so<00:27:14.580> we<00:27:14.760> have<00:27:14.880> our<00:27:14.940> call<00:27:15.120> data<00:27:15.480> and<00:27:15.779> now<00:27:16.559> um 00:27:16.610 --> 00:27:16.620 align:start position:0% cool so we have our call data and now um 00:27:16.620 --> 00:27:18.590 align:start position:0% cool so we have our call data and now um once<00:27:16.919> again<00:27:16.980> we're<00:27:17.159> going<00:27:17.279> to<00:27:17.340> send<00:27:17.520> a<00:27:17.820> sender 00:27:18.590 --> 00:27:18.600 align:start position:0% once again we're going to send a sender 00:27:18.600 --> 00:27:20.810 align:start position:0% once again we're going to send a sender a<00:27:18.720> tribal<00:27:19.200> ticket<00:27:19.380> cross-chain<00:27:19.980> message<00:27:20.220> in 00:27:20.810 --> 00:27:20.820 align:start position:0% a tribal ticket cross-chain message in 00:27:20.820 --> 00:27:23.269 align:start position:0% a tribal ticket cross-chain message in fact<00:27:21.080> in<00:27:22.080> the<00:27:22.200> interest<00:27:22.320> of<00:27:22.620> time<00:27:22.799> and<00:27:23.039> being 00:27:23.269 --> 00:27:23.279 align:start position:0% fact in the interest of time and being 00:27:23.279 --> 00:27:24.890 align:start position:0% fact in the interest of time and being lazy<00:27:23.640> I'm<00:27:23.880> just<00:27:24.000> going<00:27:24.120> to<00:27:24.240> copy<00:27:24.480> and<00:27:24.539> paste 00:27:24.890 --> 00:27:24.900 align:start position:0% lazy I'm just going to copy and paste 00:27:24.900 --> 00:27:26.269 align:start position:0% lazy I'm just going to copy and paste this<00:27:25.020> exact<00:27:25.320> thing<00:27:25.440> because<00:27:25.799> it<00:27:25.980> should<00:27:26.159> be 00:27:26.269 --> 00:27:26.279 align:start position:0% this exact thing because it should be 00:27:26.279 --> 00:27:29.390 align:start position:0% this exact thing because it should be all<00:27:26.400> the<00:27:26.580> same<00:27:26.760> parameters<00:27:27.419> I<00:27:27.720> believe 00:27:29.390 --> 00:27:29.400 align:start position:0% all the same parameters I believe 00:27:29.400 --> 00:27:35.990 align:start position:0% all the same parameters I believe I<00:27:29.820> don't<00:27:30.000> see<00:27:30.120> why<00:27:30.299> not 00:27:35.990 --> 00:27:36.000 align:start position:0% 00:27:36.000 --> 00:27:37.310 align:start position:0% um<00:27:36.120> so<00:27:36.240> we<00:27:36.419> created<00:27:36.600> a<00:27:36.720> travel<00:27:36.840> ticket<00:27:37.080> yeah 00:27:37.310 --> 00:27:37.320 align:start position:0% um so we created a travel ticket yeah 00:27:37.320 --> 00:27:39.049 align:start position:0% um so we created a travel ticket yeah Sam<00:27:37.500> browners<00:27:37.919> always<00:27:38.100> love<00:27:38.340> the<00:27:38.460> same<00:27:38.520> L2<00:27:38.880> gas 00:27:39.049 --> 00:27:39.059 align:start position:0% Sam browners always love the same L2 gas 00:27:39.059 --> 00:27:40.789 align:start position:0% Sam browners always love the same L2 gas business<00:27:39.299> once<00:27:39.900> again<00:27:39.960> the<00:27:40.140> L2<00:27:40.380> call<00:27:40.620> Value 00:27:40.789 --> 00:27:40.799 align:start position:0% business once again the L2 call Value 00:27:40.799 --> 00:27:42.769 align:start position:0% business once again the L2 call Value we're<00:27:41.100> not<00:27:41.159> sending<00:27:41.460> any<00:27:41.520> ether<00:27:41.880> uh<00:27:42.419> or<00:27:42.600> rather 00:27:42.769 --> 00:27:42.779 align:start position:0% we're not sending any ether uh or rather 00:27:42.779 --> 00:27:44.630 align:start position:0% we're not sending any ether uh or rather we're<00:27:42.960> not<00:27:43.140> you<00:27:43.380> know<00:27:43.440> using<00:27:43.980> any<00:27:44.100> ether<00:27:44.400> in 00:27:44.630 --> 00:27:44.640 align:start position:0% we're not you know using any ether in 00:27:44.640 --> 00:27:46.970 align:start position:0% we're not you know using any ether in the<00:27:45.120> um<00:27:45.179> in<00:27:45.299> the<00:27:45.360> L2<00:27:45.600> side<00:27:45.779> of<00:27:45.960> the<00:27:46.020> message<00:27:46.200> we 00:27:46.970 --> 00:27:46.980 align:start position:0% the um in the L2 side of the message we 00:27:46.980 --> 00:27:48.230 align:start position:0% the um in the L2 side of the message we could<00:27:47.100> if<00:27:47.279> we<00:27:47.460> wanted<00:27:47.520> to<00:27:47.700> have<00:27:47.820> the<00:27:47.940> option<00:27:48.120> of 00:27:48.230 --> 00:27:48.240 align:start position:0% could if we wanted to have the option of 00:27:48.240 --> 00:27:49.789 align:start position:0% could if we wanted to have the option of like<00:27:48.360> deposit<00:27:48.840> your<00:27:48.960> token<00:27:49.260> and<00:27:49.380> some<00:27:49.500> ether 00:27:49.789 --> 00:27:49.799 align:start position:0% like deposit your token and some ether 00:27:49.799 --> 00:27:51.649 align:start position:0% like deposit your token and some ether we<00:27:50.039> could<00:27:50.159> add<00:27:50.279> a<00:27:50.460> parameter<00:27:50.760> there<00:27:50.940> but<00:27:51.480> we're 00:27:51.649 --> 00:27:51.659 align:start position:0% we could add a parameter there but we're 00:27:51.659 --> 00:27:53.029 align:start position:0% we could add a parameter there but we're not 00:27:53.029 --> 00:27:53.039 align:start position:0% not 00:27:53.039 --> 00:27:53.990 align:start position:0% not um<00:27:53.100> and<00:27:53.279> then<00:27:53.400> yeah<00:27:53.520> the<00:27:53.700> only<00:27:53.820> difference 00:27:53.990 --> 00:27:54.000 align:start position:0% um and then yeah the only difference 00:27:54.000 --> 00:27:56.029 align:start position:0% um and then yeah the only difference from<00:27:54.240> before<00:27:54.360> is<00:27:54.659> we<00:27:54.779> just 00:27:56.029 --> 00:27:56.039 align:start position:0% from before is we just 00:27:56.039 --> 00:27:57.830 align:start position:0% from before is we just calling<00:27:56.460> a<00:27:56.580> different<00:27:56.700> method<00:27:57.419> um<00:27:57.480> which<00:27:57.720> we 00:27:57.830 --> 00:27:57.840 align:start position:0% calling a different method um which we 00:27:57.840 --> 00:27:59.810 align:start position:0% calling a different method um which we did<00:27:58.020> here 00:27:59.810 --> 00:27:59.820 align:start position:0% did here 00:27:59.820 --> 00:28:01.610 align:start position:0% did here um<00:27:59.880> cool<00:28:00.179> so<00:28:00.600> now<00:28:00.720> we<00:28:00.900> will<00:28:01.020> finalize<00:28:01.440> our 00:28:01.610 --> 00:28:01.620 align:start position:0% um cool so now we will finalize our 00:28:01.620 --> 00:28:03.830 align:start position:0% um cool so now we will finalize our deposit<00:28:02.100> and<00:28:02.760> finalizing<00:28:03.299> deposit<00:28:03.600> means 00:28:03.830 --> 00:28:03.840 align:start position:0% deposit and finalizing deposit means 00:28:03.840 --> 00:28:07.430 align:start position:0% deposit and finalizing deposit means minting<00:28:04.140> at<00:28:04.200> L2<00:28:04.559> so<00:28:04.860> let's<00:28:05.039> do<00:28:05.220> that 00:28:07.430 --> 00:28:07.440 align:start position:0% 00:28:07.440 --> 00:28:08.090 align:start position:0% um 00:28:08.090 --> 00:28:08.100 align:start position:0% um 00:28:08.100 --> 00:28:11.690 align:start position:0% um so<00:28:08.580> now<00:28:08.760> we're<00:28:08.940> back<00:28:09.120> on<00:28:09.419> the<00:28:09.779> L2<00:28:10.080> side 00:28:11.690 --> 00:28:11.700 align:start position:0% so now we're back on the L2 side 00:28:11.700 --> 00:28:13.730 align:start position:0% so now we're back on the L2 side um<00:28:11.820> and<00:28:12.059> cool<00:28:12.240> we<00:28:12.539> want<00:28:12.720> to<00:28:12.840> check<00:28:13.260> here<00:28:13.559> that 00:28:13.730 --> 00:28:13.740 align:start position:0% um and cool we want to check here that 00:28:13.740 --> 00:28:16.190 align:start position:0% um and cool we want to check here that it's<00:28:13.860> properly<00:28:14.220> registered 00:28:16.190 --> 00:28:16.200 align:start position:0% it's properly registered 00:28:16.200 --> 00:28:16.789 align:start position:0% it's properly registered um 00:28:16.789 --> 00:28:16.799 align:start position:0% um 00:28:16.799 --> 00:28:18.710 align:start position:0% um there<00:28:17.400> is<00:28:17.580> something<00:28:18.059> that<00:28:18.299> looks<00:28:18.480> like<00:28:18.600> an 00:28:18.710 --> 00:28:18.720 align:start position:0% there is something that looks like an 00:28:18.720 --> 00:28:20.029 align:start position:0% there is something that looks like an edge<00:28:18.840> case<00:28:19.080> which<00:28:19.260> I<00:28:19.440> can<00:28:19.500> talk<00:28:19.620> about<00:28:19.679> in<00:28:19.919> a 00:28:20.029 --> 00:28:20.039 align:start position:0% edge case which I can talk about in a 00:28:20.039 --> 00:28:21.769 align:start position:0% edge case which I can talk about in a second<00:28:20.159> why<00:28:20.640> it's<00:28:20.880> not<00:28:21.059> really<00:28:21.179> a<00:28:21.360> scary<00:28:21.480> Edge 00:28:21.769 --> 00:28:21.779 align:start position:0% second why it's not really a scary Edge 00:28:21.779 --> 00:28:23.870 align:start position:0% second why it's not really a scary Edge case<00:28:22.020> in<00:28:22.919> terms<00:28:23.159> of<00:28:23.220> the<00:28:23.400> timing<00:28:23.700> of 00:28:23.870 --> 00:28:23.880 align:start position:0% case in terms of the timing of 00:28:23.880 --> 00:28:25.909 align:start position:0% case in terms of the timing of registration<00:28:24.360> and<00:28:24.539> things<00:28:24.720> like<00:28:24.900> that 00:28:25.909 --> 00:28:25.919 align:start position:0% registration and things like that 00:28:25.919 --> 00:28:26.510 align:start position:0% registration and things like that um 00:28:26.510 --> 00:28:26.520 align:start position:0% um 00:28:26.520 --> 00:28:28.370 align:start position:0% um what<00:28:26.820> am<00:28:26.940> I<00:28:27.059> doing 00:28:28.370 --> 00:28:28.380 align:start position:0% what am I doing 00:28:28.380 --> 00:28:30.830 align:start position:0% what am I doing um<00:28:28.500> yeah<00:28:29.159> so<00:28:29.340> we're<00:28:29.460> going<00:28:29.580> to<00:28:29.700> look<00:28:29.880> up 00:28:30.830 --> 00:28:30.840 align:start position:0% um yeah so we're going to look up 00:28:30.840 --> 00:28:33.169 align:start position:0% um yeah so we're going to look up in<00:28:31.140> our<00:28:31.320> mapping 00:28:33.169 --> 00:28:33.179 align:start position:0% in our mapping 00:28:33.179 --> 00:28:35.630 align:start position:0% in our mapping uh<00:28:34.080> yes<00:28:34.320> and<00:28:34.559> see<00:28:34.740> that<00:28:34.980> that<00:28:35.159> matches<00:28:35.460> with 00:28:35.630 --> 00:28:35.640 align:start position:0% uh yes and see that that matches with 00:28:35.640 --> 00:28:38.269 align:start position:0% uh yes and see that that matches with the<00:28:35.820> token<00:28:36.120> provided 00:28:38.269 --> 00:28:38.279 align:start position:0% the token provided 00:28:38.279 --> 00:28:40.310 align:start position:0% the token provided so<00:28:38.820> this<00:28:39.120> ensures<00:28:39.539> that<00:28:39.720> it's<00:28:39.779> registered<00:28:40.140> on 00:28:40.310 --> 00:28:40.320 align:start position:0% so this ensures that it's registered on 00:28:40.320 --> 00:28:43.490 align:start position:0% so this ensures that it's registered on the<00:28:40.380> L2<00:28:40.679> side 00:28:43.490 --> 00:28:43.500 align:start position:0% 00:28:43.500 --> 00:28:46.130 align:start position:0% yep 00:28:46.130 --> 00:28:46.140 align:start position:0% 00:28:46.140 --> 00:28:47.269 align:start position:0% um 00:28:47.269 --> 00:28:47.279 align:start position:0% um 00:28:47.279 --> 00:28:49.730 align:start position:0% um and<00:28:48.059> cool<00:28:48.299> that<00:28:48.539> should<00:28:48.659> be<00:28:48.779> it<00:28:49.380> um<00:28:49.380> once<00:28:49.679> again 00:28:49.730 --> 00:28:49.740 align:start position:0% and cool that should be it um once again 00:28:49.740 --> 00:28:52.250 align:start position:0% and cool that should be it um once again we'll<00:28:50.100> add<00:28:50.460> our<00:28:50.760> only<00:28:51.360> counterpart<00:28:51.960> L1 00:28:52.250 --> 00:28:52.260 align:start position:0% we'll add our only counterpart L1 00:28:52.260 --> 00:28:53.390 align:start position:0% we'll add our only counterpart L1 Gateway<00:28:52.559> that's<00:28:52.799> kind<00:28:52.919> of<00:28:53.039> the<00:28:53.100> important 00:28:53.390 --> 00:28:53.400 align:start position:0% Gateway that's kind of the important 00:28:53.400 --> 00:28:55.549 align:start position:0% Gateway that's kind of the important thing<00:28:54.059> so<00:28:54.299> it's<00:28:54.419> gonna<00:28:54.539> only<00:28:54.720> be<00:28:54.840> called<00:28:55.020> via 00:28:55.549 --> 00:28:55.559 align:start position:0% thing so it's gonna only be called via 00:28:55.559 --> 00:28:57.590 align:start position:0% thing so it's gonna only be called via that<00:28:55.740> cross<00:28:55.860> chain<00:28:56.100> message 00:28:57.590 --> 00:28:57.600 align:start position:0% that cross chain message 00:28:57.600 --> 00:28:58.490 align:start position:0% that cross chain message um 00:28:58.490 --> 00:28:58.500 align:start position:0% um 00:28:58.500 --> 00:29:01.430 align:start position:0% um and<00:28:59.100> okay<00:28:59.340> now<00:28:59.580> we<00:28:59.700> can<00:28:59.820> do<00:28:59.880> the<00:29:00.000> L2<00:29:00.240> part 00:29:01.430 --> 00:29:01.440 align:start position:0% and okay now we can do the L2 part 00:29:01.440 --> 00:29:03.769 align:start position:0% and okay now we can do the L2 part um<00:29:01.500> the<00:29:01.620> L2<00:29:01.919> part<00:29:02.159> of<00:29:02.279> a<00:29:02.400> deposit<00:29:02.760> is<00:29:02.820> minting 00:29:03.769 --> 00:29:03.779 align:start position:0% um the L2 part of a deposit is minting 00:29:03.779 --> 00:29:05.210 align:start position:0% um the L2 part of a deposit is minting so<00:29:04.140> now<00:29:04.260> we<00:29:04.440> now<00:29:04.679> we<00:29:04.799> want<00:29:04.919> to<00:29:04.980> actually<00:29:05.100> look 00:29:05.210 --> 00:29:05.220 align:start position:0% so now we now we want to actually look 00:29:05.220 --> 00:29:06.590 align:start position:0% so now we now we want to actually look at<00:29:05.340> our<00:29:05.400> L2<00:29:05.760> token<00:29:06.059> which<00:29:06.179> we<00:29:06.299> haven't<00:29:06.419> even 00:29:06.590 --> 00:29:06.600 align:start position:0% at our L2 token which we haven't even 00:29:06.600 --> 00:29:07.970 align:start position:0% at our L2 token which we haven't even looked<00:29:06.840> at<00:29:06.900> yet 00:29:07.970 --> 00:29:07.980 align:start position:0% looked at yet 00:29:07.980 --> 00:29:09.470 align:start position:0% looked at yet um what<00:29:08.279> is<00:29:08.460> going<00:29:08.580> to<00:29:08.700> be<00:29:08.820> deployed<00:29:09.179> on<00:29:09.360> the 00:29:09.470 --> 00:29:09.480 align:start position:0% um what is going to be deployed on the 00:29:09.480 --> 00:29:11.330 align:start position:0% um what is going to be deployed on the L2<00:29:09.840> side 00:29:11.330 --> 00:29:11.340 align:start position:0% L2 side 00:29:11.340 --> 00:29:13.190 align:start position:0% L2 side so<00:29:11.820> here<00:29:12.059> I'm 00:29:13.190 --> 00:29:13.200 align:start position:0% so here I'm 00:29:13.200 --> 00:29:15.289 align:start position:0% so here I'm this<00:29:13.740> was<00:29:13.919> you<00:29:14.159> know<00:29:14.220> not<00:29:14.460> this<00:29:14.700> was<00:29:14.880> deployed 00:29:15.289 --> 00:29:15.299 align:start position:0% this was you know not this was deployed 00:29:15.299 --> 00:29:17.390 align:start position:0% this was you know not this was deployed directly<00:29:15.659> and<00:29:16.500> basically<00:29:16.799> this<00:29:17.100> is<00:29:17.220> the 00:29:17.390 --> 00:29:17.400 align:start position:0% directly and basically this is the 00:29:17.400 --> 00:29:18.830 align:start position:0% directly and basically this is the Assumption<00:29:17.760> this<00:29:17.940> is<00:29:18.059> the<00:29:18.120> assumed<00:29:18.480> interface 00:29:18.830 --> 00:29:18.840 align:start position:0% Assumption this is the assumed interface 00:29:18.840 --> 00:29:21.049 align:start position:0% Assumption this is the assumed interface it<00:29:19.080> has<00:29:19.200> to<00:29:19.320> have<00:29:19.500> these<00:29:19.860> methods<00:29:20.220> here<00:29:20.340> yes<00:29:20.820> I 00:29:21.049 --> 00:29:21.059 align:start position:0% it has to have these methods here yes I 00:29:21.059 --> 00:29:22.130 align:start position:0% it has to have these methods here yes I have<00:29:21.120> a<00:29:21.240> method<00:29:21.480> that<00:29:21.600> allows<00:29:21.779> the<00:29:21.899> bridge<00:29:22.020> to 00:29:22.130 --> 00:29:22.140 align:start position:0% have a method that allows the bridge to 00:29:22.140 --> 00:29:23.750 align:start position:0% have a method that allows the bridge to Mint<00:29:22.380> and<00:29:22.500> allows<00:29:22.740> the<00:29:22.860> bridge<00:29:22.980> to<00:29:23.159> burn<00:29:23.279> uh 00:29:23.750 --> 00:29:23.760 align:start position:0% Mint and allows the bridge to burn uh 00:29:23.760 --> 00:29:26.269 align:start position:0% Mint and allows the bridge to burn uh and<00:29:23.940> we<00:29:24.059> can<00:29:24.179> just<00:29:24.240> fill<00:29:24.480> that<00:29:24.600> out<00:29:24.840> now 00:29:26.269 --> 00:29:26.279 align:start position:0% and we can just fill that out now 00:29:26.279 --> 00:29:28.010 align:start position:0% and we can just fill that out now um<00:29:26.399> fairly<00:29:27.179> simple 00:29:28.010 --> 00:29:28.020 align:start position:0% um fairly simple 00:29:28.020 --> 00:29:30.230 align:start position:0% um fairly simple mint 00:29:30.230 --> 00:29:30.240 align:start position:0% mint 00:29:30.240 --> 00:29:32.330 align:start position:0% mint okay<00:29:30.600> so<00:29:30.779> we<00:29:30.899> expose<00:29:31.200> the<00:29:31.380> ability<00:29:31.620> for<00:29:32.039> only 00:29:32.330 --> 00:29:32.340 align:start position:0% okay so we expose the ability for only 00:29:32.340 --> 00:29:34.730 align:start position:0% okay so we expose the ability for only the<00:29:32.760> uh<00:29:32.940> only<00:29:33.179> the<00:29:33.299> Gateway<00:29:33.600> or<00:29:33.720> the<00:29:33.840> L2<00:29:34.140> the<00:29:34.500> L2 00:29:34.730 --> 00:29:34.740 align:start position:0% the uh only the Gateway or the L2 the L2 00:29:34.740 --> 00:29:36.230 align:start position:0% the uh only the Gateway or the L2 the L2 bridge<00:29:34.919> to<00:29:35.100> Mint 00:29:36.230 --> 00:29:36.240 align:start position:0% bridge to Mint 00:29:36.240 --> 00:29:37.850 align:start position:0% bridge to Mint um<00:29:36.360> I<00:29:36.600> think<00:29:36.720> it's<00:29:36.840> in<00:29:37.020> that<00:29:37.200> same<00:29:37.320> order<00:29:37.559> I'm 00:29:37.850 --> 00:29:37.860 align:start position:0% um I think it's in that same order I'm 00:29:37.860 --> 00:29:39.470 align:start position:0% um I think it's in that same order I'm not<00:29:38.100> mistaken<00:29:38.460> I<00:29:39.000> think<00:29:39.120> that's<00:29:39.240> how<00:29:39.360> that 00:29:39.470 --> 00:29:39.480 align:start position:0% not mistaken I think that's how that 00:29:39.480 --> 00:29:40.730 align:start position:0% not mistaken I think that's how that works 00:29:40.730 --> 00:29:40.740 align:start position:0% works 00:29:40.740 --> 00:29:41.510 align:start position:0% works um 00:29:41.510 --> 00:29:41.520 align:start position:0% um 00:29:41.520 --> 00:29:43.370 align:start position:0% um and<00:29:42.059> let's<00:29:42.179> add<00:29:42.419> this<00:29:42.600> only<00:29:42.840> Gateway<00:29:43.200> that 00:29:43.370 --> 00:29:43.380 align:start position:0% and let's add this only Gateway that 00:29:43.380 --> 00:29:44.750 align:start position:0% and let's add this only Gateway that should<00:29:43.559> be<00:29:43.679> probably<00:29:43.860> be<00:29:44.220> clear<00:29:44.399> if<00:29:44.520> it<00:29:44.640> was 00:29:44.750 --> 00:29:44.760 align:start position:0% should be probably be clear if it was 00:29:44.760 --> 00:29:46.250 align:start position:0% should be probably be clear if it was called<00:29:44.880> like<00:29:45.000> only<00:29:45.179> L2<00:29:45.600> Gateway<00:29:45.899> or<00:29:46.140> something 00:29:46.250 --> 00:29:46.260 align:start position:0% called like only L2 Gateway or something 00:29:46.260 --> 00:29:48.529 align:start position:0% called like only L2 Gateway or something but<00:29:46.919> when<00:29:47.159> we<00:29:47.279> initialize<00:29:47.700> our<00:29:47.820> L2<00:29:48.120> token<00:29:48.419> we 00:29:48.529 --> 00:29:48.539 align:start position:0% but when we initialize our L2 token we 00:29:48.539 --> 00:29:50.389 align:start position:0% but when we initialize our L2 token we give<00:29:48.659> it<00:29:48.779> the<00:29:48.899> address<00:29:49.020> of<00:29:49.200> the<00:29:49.320> LG<00:29:49.500> Gateway 00:29:50.389 --> 00:29:50.399 align:start position:0% give it the address of the LG Gateway 00:29:50.399 --> 00:29:52.430 align:start position:0% give it the address of the LG Gateway cool<00:29:50.760> so<00:29:50.940> now<00:29:51.059> that's<00:29:51.240> exposed<00:29:51.600> dl2<00:29:51.960> get<00:29:52.140> the 00:29:52.430 --> 00:29:52.440 align:start position:0% cool so now that's exposed dl2 get the 00:29:52.440 --> 00:29:55.370 align:start position:0% cool so now that's exposed dl2 get the L2<00:29:52.740> Gateway<00:29:53.039> can<00:29:53.399> uh<00:29:53.640> convince<00:29:54.179> so<00:29:54.659> let's<00:29:54.899> uh 00:29:55.370 --> 00:29:55.380 align:start position:0% L2 Gateway can uh convince so let's uh 00:29:55.380 --> 00:29:58.070 align:start position:0% L2 Gateway can uh convince so let's uh let's<00:29:55.679> mention 00:29:58.070 --> 00:29:58.080 align:start position:0% 00:29:58.080 --> 00:30:00.769 align:start position:0% um<00:29:58.200> where<00:29:58.380> are<00:29:58.559> we<00:29:58.679> finalize<00:29:59.039> deposit<00:29:59.520> yes 00:30:00.769 --> 00:30:00.779 align:start position:0% um where are we finalize deposit yes 00:30:00.779 --> 00:30:03.769 align:start position:0% um where are we finalize deposit yes so<00:30:01.620> let's 00:30:03.769 --> 00:30:03.779 align:start position:0% so let's 00:30:03.779 --> 00:30:07.730 align:start position:0% so let's uh<00:30:04.679> connect<00:30:04.860> to<00:30:05.039> our<00:30:05.220> L2<00:30:05.520> token 00:30:07.730 --> 00:30:07.740 align:start position:0% uh connect to our L2 token 00:30:07.740 --> 00:30:09.110 align:start position:0% uh connect to our L2 token um 00:30:09.110 --> 00:30:09.120 align:start position:0% um 00:30:09.120 --> 00:30:10.050 align:start position:0% um or<00:30:09.419> rather 00:30:10.050 --> 00:30:10.060 align:start position:0% or rather 00:30:10.060 --> 00:30:10.370 align:start position:0% or rather [Music] 00:30:10.370 --> 00:30:10.380 align:start position:0% [Music] 00:30:10.380 --> 00:30:11.450 align:start position:0% [Music] um 00:30:11.450 --> 00:30:11.460 align:start position:0% um 00:30:11.460 --> 00:30:13.789 align:start position:0% um yes<00:30:12.120> let's<00:30:12.539> connect<00:30:12.779> to<00:30:13.020> the<00:30:13.200> interface<00:30:13.500> but 00:30:13.789 --> 00:30:13.799 align:start position:0% yes let's connect to the interface but 00:30:13.799 --> 00:30:16.850 align:start position:0% yes let's connect to the interface but we'll<00:30:14.100> use<00:30:14.279> our<00:30:14.700> assumed<00:30:15.179> interface 00:30:16.850 --> 00:30:16.860 align:start position:0% we'll use our assumed interface 00:30:16.860 --> 00:30:19.190 align:start position:0% we'll use our assumed interface um<00:30:16.919> L2<00:30:17.640> our<00:30:17.820> vrc20<00:30:18.480> which<00:30:18.840> has<00:30:18.960> the<00:30:19.080> bridge 00:30:19.190 --> 00:30:19.200 align:start position:0% um L2 our vrc20 which has the bridge 00:30:19.200 --> 00:30:22.250 align:start position:0% um L2 our vrc20 which has the bridge mint<00:30:19.440> and<00:30:19.559> Bridge<00:30:19.679> burn<00:30:19.919> functionality 00:30:22.250 --> 00:30:22.260 align:start position:0% mint and Bridge burn functionality 00:30:22.260 --> 00:30:30.950 align:start position:0% mint and Bridge burn functionality uh<00:30:22.740> yes<00:30:22.919> I'm<00:30:23.100> sorry 00:30:30.950 --> 00:30:30.960 align:start position:0% 00:30:30.960 --> 00:30:33.289 align:start position:0% the<00:30:31.380> L1<00:30:31.620> and<00:30:31.799> L2<00:30:32.039> Gateway<00:30:32.399> are<00:30:32.760> they<00:30:32.940> depleted 00:30:33.289 --> 00:30:33.299 align:start position:0% the L1 and L2 Gateway are they depleted 00:30:33.299 --> 00:30:35.510 align:start position:0% the L1 and L2 Gateway are they depleted it<00:30:33.480> doesn't<00:30:33.840> matter<00:30:34.080> yeah<00:30:34.980> it<00:30:35.159> doesn't<00:30:35.340> matter 00:30:35.510 --> 00:30:35.520 align:start position:0% it doesn't matter yeah it doesn't matter 00:30:35.520 --> 00:30:37.789 align:start position:0% it doesn't matter yeah it doesn't matter they<00:30:35.700> don't<00:30:35.880> need<00:30:36.000> to<00:30:36.120> be<00:30:36.600> yeah<00:30:36.840> so<00:30:37.500> just<00:30:37.679> as 00:30:37.789 --> 00:30:37.799 align:start position:0% they don't need to be yeah so just as 00:30:37.799 --> 00:30:39.110 align:start position:0% they don't need to be yeah so just as long<00:30:37.980> as<00:30:38.039> we<00:30:38.159> as<00:30:38.279> basically<00:30:38.520> as<00:30:38.700> long<00:30:38.820> as<00:30:38.880> when 00:30:39.110 --> 00:30:39.120 align:start position:0% long as we as basically as long as when 00:30:39.120 --> 00:30:41.090 align:start position:0% long as we as basically as long as when we<00:30:39.419> like<00:30:40.080> when<00:30:40.260> we<00:30:40.440> initialize<00:30:40.799> these 00:30:41.090 --> 00:30:41.100 align:start position:0% we like when we initialize these 00:30:41.100 --> 00:30:42.590 align:start position:0% we like when we initialize these contracts<00:30:41.399> we<00:30:41.580> know<00:30:41.700> they<00:30:42.120> know<00:30:42.240> each<00:30:42.419> other's 00:30:42.590 --> 00:30:42.600 align:start position:0% contracts we know they know each other's 00:30:42.600 --> 00:30:44.269 align:start position:0% contracts we know they know each other's addresses<00:30:43.020> we're<00:30:43.260> fine<00:30:43.440> so<00:30:43.860> there's<00:30:44.039> no<00:30:44.159> need 00:30:44.269 --> 00:30:44.279 align:start position:0% addresses we're fine so there's no need 00:30:44.279 --> 00:30:46.010 align:start position:0% addresses we're fine so there's no need for<00:30:44.399> them<00:30:44.520> it's<00:30:44.700> probably<00:30:44.880> better<00:30:45.659> than<00:30:45.840> not 00:30:46.010 --> 00:30:46.020 align:start position:0% for them it's probably better than not 00:30:46.020 --> 00:30:47.210 align:start position:0% for them it's probably better than not at<00:30:46.140> the<00:30:46.260> same<00:30:46.320> address<00:30:46.500> because<00:30:46.799> that<00:30:46.919> tends 00:30:47.210 --> 00:30:47.220 align:start position:0% at the same address because that tends 00:30:47.220 --> 00:30:48.470 align:start position:0% at the same address because that tends to<00:30:47.279> confuse<00:30:47.520> people<00:30:47.760> we've<00:30:48.120> had<00:30:48.179> issues 00:30:48.470 --> 00:30:48.480 align:start position:0% to confuse people we've had issues 00:30:48.480 --> 00:30:49.250 align:start position:0% to confuse people we've had issues actually 00:30:49.250 --> 00:30:49.260 align:start position:0% actually 00:30:49.260 --> 00:30:49.970 align:start position:0% actually um 00:30:49.970 --> 00:30:49.980 align:start position:0% um 00:30:49.980 --> 00:30:52.190 align:start position:0% um um<00:30:50.100> yeah<00:30:50.279> but<00:30:51.000> um<00:30:51.120> so<00:30:51.480> they<00:30:51.600> can<00:30:51.720> be<00:30:51.840> if<00:30:52.080> you're 00:30:52.190 --> 00:30:52.200 align:start position:0% um yeah but um so they can be if you're 00:30:52.200 --> 00:30:53.810 align:start position:0% um yeah but um so they can be if you're if<00:30:52.440> you<00:30:52.559> if<00:30:52.740> you<00:30:52.860> want<00:30:52.919> to<00:30:53.039> be<00:30:53.159> fancy<00:30:53.460> with<00:30:53.640> how 00:30:53.810 --> 00:30:53.820 align:start position:0% if you if you want to be fancy with how 00:30:53.820 --> 00:30:54.950 align:start position:0% if you if you want to be fancy with how you'd<00:30:54.000> apply<00:30:54.179> them<00:30:54.360> but<00:30:54.480> they<00:30:54.600> don't<00:30:54.720> need<00:30:54.840> to 00:30:54.950 --> 00:30:54.960 align:start position:0% you'd apply them but they don't need to 00:30:54.960 --> 00:30:55.730 align:start position:0% you'd apply them but they don't need to be 00:30:55.730 --> 00:30:55.740 align:start position:0% be 00:30:55.740 --> 00:30:56.930 align:start position:0% be um 00:30:56.930 --> 00:30:56.940 align:start position:0% um 00:30:56.940 --> 00:30:58.370 align:start position:0% um okay 00:30:58.370 --> 00:30:58.380 align:start position:0% okay 00:30:58.380 --> 00:31:01.370 align:start position:0% okay um<00:30:58.440> what<00:30:58.860> are<00:30:59.039> we<00:30:59.100> doing<00:30:59.220> we're<00:30:59.580> minting 00:31:01.370 --> 00:31:01.380 align:start position:0% um what are we doing we're minting 00:31:01.380 --> 00:31:02.630 align:start position:0% um what are we doing we're minting yes 00:31:02.630 --> 00:31:02.640 align:start position:0% yes 00:31:02.640 --> 00:31:05.330 align:start position:0% yes and<00:31:03.360> my<00:31:03.600> editor<00:31:03.899> is<00:31:04.080> smart<00:31:04.260> I<00:31:04.559> think 00:31:05.330 --> 00:31:05.340 align:start position:0% and my editor is smart I think 00:31:05.340 --> 00:31:06.830 align:start position:0% and my editor is smart I think it's<00:31:05.460> not<00:31:05.700> the<00:31:05.820> right<00:31:05.940> order 00:31:06.830 --> 00:31:06.840 align:start position:0% it's not the right order 00:31:06.840 --> 00:31:08.930 align:start position:0% it's not the right order yes<00:31:07.799> cool 00:31:08.930 --> 00:31:08.940 align:start position:0% yes cool 00:31:08.940 --> 00:31:09.529 align:start position:0% yes cool um 00:31:09.529 --> 00:31:09.539 align:start position:0% um 00:31:09.539 --> 00:31:11.690 align:start position:0% um so<00:31:09.899> there's<00:31:10.020> our<00:31:10.200> actual<00:31:10.380> mint 00:31:11.690 --> 00:31:11.700 align:start position:0% so there's our actual mint 00:31:11.700 --> 00:31:12.649 align:start position:0% so there's our actual mint um 00:31:12.649 --> 00:31:12.659 align:start position:0% um 00:31:12.659 --> 00:31:15.169 align:start position:0% um and<00:31:13.140> that's<00:31:13.320> it 00:31:15.169 --> 00:31:15.179 align:start position:0% and that's it 00:31:15.179 --> 00:31:16.610 align:start position:0% and that's it right<00:31:15.360> because<00:31:15.600> again<00:31:15.779> this<00:31:16.080> this<00:31:16.320> can<00:31:16.500> only 00:31:16.610 --> 00:31:16.620 align:start position:0% right because again this this can only 00:31:16.620 --> 00:31:17.930 align:start position:0% right because again this this can only be<00:31:16.740> called<00:31:16.860> as<00:31:16.980> a<00:31:17.100> cross<00:31:17.159> chain<00:31:17.399> message<00:31:17.640> so 00:31:17.930 --> 00:31:17.940 align:start position:0% be called as a cross chain message so 00:31:17.940 --> 00:31:21.230 align:start position:0% be called as a cross chain message so there's<00:31:18.179> uh<00:31:18.659> there's<00:31:18.840> our<00:31:18.960> deposit<00:31:19.440> yeah 00:31:21.230 --> 00:31:21.240 align:start position:0% there's uh there's our deposit yeah 00:31:21.240 --> 00:31:22.909 align:start position:0% there's uh there's our deposit yeah any<00:31:21.480> other<00:31:21.659> questions<00:31:21.899> before<00:31:22.320> we<00:31:22.559> move<00:31:22.740> on<00:31:22.799> to 00:31:22.909 --> 00:31:22.919 align:start position:0% any other questions before we move on to 00:31:22.919 --> 00:31:24.529 align:start position:0% any other questions before we move on to the<00:31:23.039> last 00:31:24.529 --> 00:31:24.539 align:start position:0% the last 00:31:24.539 --> 00:31:26.210 align:start position:0% the last um<00:31:24.720> time<00:31:24.960> is<00:31:25.140> fine<00:31:25.320> so<00:31:25.620> let<00:31:25.740> me<00:31:25.860> let<00:31:26.039> me 00:31:26.210 --> 00:31:26.220 align:start position:0% um time is fine so let me let me 00:31:26.220 --> 00:31:28.909 align:start position:0% um time is fine so let me let me slightly<00:31:26.700> speed<00:31:26.880> around<00:31:27.120> this<00:31:27.299> but<00:31:27.960> um 00:31:28.909 --> 00:31:28.919 align:start position:0% slightly speed around this but um 00:31:28.919 --> 00:31:31.430 align:start position:0% slightly speed around this but um um<00:31:29.100> let's<00:31:29.940> um<00:31:30.000> let's<00:31:30.240> do<00:31:30.360> a<00:31:30.480> withdrawal 00:31:31.430 --> 00:31:31.440 align:start position:0% um let's um let's do a withdrawal 00:31:31.440 --> 00:31:32.850 align:start position:0% um let's um let's do a withdrawal so<00:31:31.980> here<00:31:32.159> we're<00:31:32.340> going<00:31:32.520> to 00:31:32.850 --> 00:31:32.860 align:start position:0% so here we're going to 00:31:32.860 --> 00:31:33.470 align:start position:0% so here we're going to [Music] 00:31:33.470 --> 00:31:33.480 align:start position:0% [Music] 00:31:33.480 --> 00:31:34.190 align:start position:0% [Music] um 00:31:34.190 --> 00:31:34.200 align:start position:0% um 00:31:34.200 --> 00:31:35.690 align:start position:0% um need<00:31:34.620> a<00:31:34.799> cross<00:31:34.919> chain<00:31:35.100> message<00:31:35.279> this<00:31:35.520> time 00:31:35.690 --> 00:31:35.700 align:start position:0% need a cross chain message this time 00:31:35.700 --> 00:31:40.010 align:start position:0% need a cross chain message this time from<00:31:35.880> L2<00:31:36.120> to<00:31:36.299> L1<00:31:36.779> I<00:31:37.500> can<00:31:37.620> just<00:31:37.799> show<00:31:38.039> you 00:31:40.010 --> 00:31:40.020 align:start position:0% from L2 to L1 I can just show you 00:31:40.020 --> 00:31:41.510 align:start position:0% from L2 to L1 I can just show you the<00:31:40.320> arbitrine<00:31:40.799> pre-compile<00:31:41.220> we're<00:31:41.399> going<00:31:41.520> to 00:31:41.510 --> 00:31:41.520 align:start position:0% the arbitrine pre-compile we're going to 00:31:41.520 --> 00:31:43.010 align:start position:0% the arbitrine pre-compile we're going to use<00:31:41.640> which<00:31:42.000> is<00:31:42.179> called<00:31:42.299> our<00:31:42.539> obsessed<00:31:42.960> so 00:31:43.010 --> 00:31:43.020 align:start position:0% use which is called our obsessed so 00:31:43.020 --> 00:31:45.470 align:start position:0% use which is called our obsessed so every<00:31:43.140> Every<00:31:43.380> arbitrum<00:31:43.919> Chain<00:31:44.360> gets<00:31:45.360> this 00:31:45.470 --> 00:31:45.480 align:start position:0% every Every arbitrum Chain gets this 00:31:45.480 --> 00:31:47.990 align:start position:0% every Every arbitrum Chain gets this pre-compile<00:31:45.960> it<00:31:46.440> lives<00:31:46.740> at<00:31:47.399> um<00:31:47.399> address<00:31:47.640> 100 00:31:47.990 --> 00:31:48.000 align:start position:0% pre-compile it lives at um address 100 00:31:48.000 --> 00:31:50.810 align:start position:0% pre-compile it lives at um address 100 or<00:31:48.779> that<00:31:49.260> hex 00:31:50.810 --> 00:31:50.820 align:start position:0% or that hex 00:31:50.820 --> 00:31:52.370 align:start position:0% or that hex um<00:31:50.940> and<00:31:51.179> this<00:31:51.240> just<00:31:51.419> exposes<00:31:51.899> all<00:31:52.080> sorts<00:31:52.320> of 00:31:52.370 --> 00:31:52.380 align:start position:0% um and this just exposes all sorts of 00:31:52.380 --> 00:31:54.409 align:start position:0% um and this just exposes all sorts of system<00:31:52.500> level<00:31:52.740> functionality<00:31:53.460> for<00:31:54.299> our 00:31:54.409 --> 00:31:54.419 align:start position:0% system level functionality for our 00:31:54.419 --> 00:31:56.149 align:start position:0% system level functionality for our purposes<00:31:54.779> we<00:31:55.200> have<00:31:55.320> this<00:31:55.559> send<00:31:55.740> transaction 00:31:56.149 --> 00:31:56.159 align:start position:0% purposes we have this send transaction 00:31:56.159 --> 00:31:58.850 align:start position:0% purposes we have this send transaction to<00:31:56.399> L1<00:31:56.760> very<00:31:57.360> similar<00:31:57.659> idea<00:31:57.899> right<00:31:58.200> we<00:31:58.440> specify 00:31:58.850 --> 00:31:58.860 align:start position:0% to L1 very similar idea right we specify 00:31:58.860 --> 00:32:00.769 align:start position:0% to L1 very similar idea right we specify the<00:31:58.980> L1<00:31:59.220> address<00:31:59.520> that<00:32:00.179> we<00:32:00.299> want<00:32:00.419> to<00:32:00.539> make<00:32:00.600> some 00:32:00.769 --> 00:32:00.779 align:start position:0% the L1 address that we want to make some 00:32:00.779 --> 00:32:03.350 align:start position:0% the L1 address that we want to make some contract<00:32:01.200> call<00:32:01.380> and<00:32:02.279> we<00:32:02.460> give<00:32:02.640> this<00:32:02.880> this<00:32:03.059> data 00:32:03.350 --> 00:32:03.360 align:start position:0% contract call and we give this this data 00:32:03.360 --> 00:32:04.730 align:start position:0% contract call and we give this this data this<00:32:03.539> call<00:32:03.720> data<00:32:04.020> which<00:32:04.140> is<00:32:04.260> the<00:32:04.380> encoded 00:32:04.730 --> 00:32:04.740 align:start position:0% this call data which is the encoded 00:32:04.740 --> 00:32:05.750 align:start position:0% this call data which is the encoded message<00:32:04.919> that<00:32:05.220> we're<00:32:05.340> actually<00:32:05.460> going<00:32:05.640> to 00:32:05.750 --> 00:32:05.760 align:start position:0% message that we're actually going to 00:32:05.760 --> 00:32:06.529 align:start position:0% message that we're actually going to call 00:32:06.529 --> 00:32:06.539 align:start position:0% call 00:32:06.539 --> 00:32:08.389 align:start position:0% call notice<00:32:07.200> in<00:32:07.380> this<00:32:07.500> case<00:32:07.559> there's<00:32:07.860> none<00:32:08.039> of<00:32:08.220> that 00:32:08.389 --> 00:32:08.399 align:start position:0% notice in this case there's none of that 00:32:08.399 --> 00:32:09.889 align:start position:0% notice in this case there's none of that gas<00:32:08.880> stuff 00:32:09.889 --> 00:32:09.899 align:start position:0% gas stuff 00:32:09.899 --> 00:32:11.510 align:start position:0% gas stuff um and<00:32:10.080> this<00:32:10.200> is<00:32:10.320> because<00:32:10.520> essentially 00:32:11.510 --> 00:32:11.520 align:start position:0% um and this is because essentially 00:32:11.520 --> 00:32:12.769 align:start position:0% um and this is because essentially there's<00:32:11.700> no<00:32:12.000> such<00:32:12.120> thing<00:32:12.240> as<00:32:12.360> automatic 00:32:12.769 --> 00:32:12.779 align:start position:0% there's no such thing as automatic 00:32:12.779 --> 00:32:14.690 align:start position:0% there's no such thing as automatic execution<00:32:13.140> on<00:32:13.440> L1<00:32:13.799> so<00:32:14.100> this<00:32:14.279> has<00:32:14.460> to<00:32:14.580> just 00:32:14.690 --> 00:32:14.700 align:start position:0% execution on L1 so this has to just 00:32:14.700 --> 00:32:16.250 align:start position:0% execution on L1 so this has to just happen<00:32:14.880> in<00:32:15.120> two<00:32:15.240> steps<00:32:15.539> right<00:32:15.720> we<00:32:15.899> initiated 00:32:16.250 --> 00:32:16.260 align:start position:0% happen in two steps right we initiated 00:32:16.260 --> 00:32:18.769 align:start position:0% happen in two steps right we initiated on<00:32:16.500> L2<00:32:16.860> and<00:32:17.340> then<00:32:17.399> sometime<00:32:17.760> later<00:32:18.000> the<00:32:18.600> client 00:32:18.769 --> 00:32:18.779 align:start position:0% on L2 and then sometime later the client 00:32:18.779 --> 00:32:20.750 align:start position:0% on L2 and then sometime later the client will<00:32:19.020> sort<00:32:19.260> of<00:32:19.320> finalize<00:32:19.620> it<00:32:19.740> on<00:32:19.919> L1<00:32:20.220> via<00:32:20.520> its 00:32:20.750 --> 00:32:20.760 align:start position:0% will sort of finalize it on L1 via its 00:32:20.760 --> 00:32:22.610 align:start position:0% will sort of finalize it on L1 via its own<00:32:20.820> transaction<00:32:21.179> so<00:32:21.539> perhaps<00:32:22.260> slightly<00:32:22.559> more 00:32:22.610 --> 00:32:22.620 align:start position:0% own transaction so perhaps slightly more 00:32:22.620 --> 00:32:24.230 align:start position:0% own transaction so perhaps slightly more inconvenient<00:32:23.100> for<00:32:23.220> the<00:32:23.340> user<00:32:23.520> but<00:32:23.760> convenient 00:32:24.230 --> 00:32:24.240 align:start position:0% inconvenient for the user but convenient 00:32:24.240 --> 00:32:25.850 align:start position:0% inconvenient for the user but convenient for<00:32:24.480> us<00:32:24.600> now<00:32:24.840> we<00:32:25.320> don't<00:32:25.440> have<00:32:25.559> to<00:32:25.620> have<00:32:25.740> those 00:32:25.850 --> 00:32:25.860 align:start position:0% for us now we don't have to have those 00:32:25.860 --> 00:32:28.669 align:start position:0% for us now we don't have to have those parameters<00:32:26.340> so<00:32:26.820> it's<00:32:26.940> a<00:32:27.179> two-step<00:32:27.539> process 00:32:28.669 --> 00:32:28.679 align:start position:0% parameters so it's a two-step process 00:32:28.679 --> 00:32:29.630 align:start position:0% parameters so it's a two-step process um<00:32:28.740> and<00:32:28.860> this<00:32:28.980> is<00:32:29.100> where<00:32:29.220> you<00:32:29.340> have<00:32:29.460> to<00:32:29.520> wait 00:32:29.630 --> 00:32:29.640 align:start position:0% um and this is where you have to wait 00:32:29.640 --> 00:32:31.490 align:start position:0% um and this is where you have to wait the<00:32:29.880> optimistic<00:32:30.299> roll-up<00:32:30.600> delay<00:32:30.899> period<00:32:31.200> if 00:32:31.490 --> 00:32:31.500 align:start position:0% the optimistic roll-up delay period if 00:32:31.500 --> 00:32:34.010 align:start position:0% the optimistic roll-up delay period if you're<00:32:31.679> familiar<00:32:32.039> with<00:32:32.340> that<00:32:32.520> stuff 00:32:34.010 --> 00:32:34.020 align:start position:0% you're familiar with that stuff 00:32:34.020 --> 00:32:36.049 align:start position:0% you're familiar with that stuff um<00:32:34.080> okay<00:32:34.440> cool 00:32:36.049 --> 00:32:36.059 align:start position:0% um okay cool 00:32:36.059 --> 00:32:37.730 align:start position:0% um okay cool um<00:32:36.179> so<00:32:36.360> let's<00:32:36.539> do<00:32:36.720> our<00:32:36.899> let's<00:32:37.080> do<00:32:37.200> a<00:32:37.320> withdrawal 00:32:37.730 --> 00:32:37.740 align:start position:0% um so let's do our let's do a withdrawal 00:32:37.740 --> 00:32:38.750 align:start position:0% um so let's do our let's do a withdrawal here 00:32:38.750 --> 00:32:38.760 align:start position:0% here 00:32:38.760 --> 00:32:40.789 align:start position:0% here um 00:32:40.789 --> 00:32:40.799 align:start position:0% um 00:32:40.799 --> 00:32:43.250 align:start position:0% um yeah<00:32:41.580> let's<00:32:42.240> go<00:32:42.419> for<00:32:42.539> it 00:32:43.250 --> 00:32:43.260 align:start position:0% yeah let's go for it 00:32:43.260 --> 00:32:45.049 align:start position:0% yeah let's go for it so<00:32:43.799> let's<00:32:44.100> see<00:32:44.220> we<00:32:44.399> have<00:32:44.460> like<00:32:44.580> 15<00:32:44.760> minutes 00:32:45.049 --> 00:32:45.059 align:start position:0% so let's see we have like 15 minutes 00:32:45.059 --> 00:32:47.570 align:start position:0% so let's see we have like 15 minutes that<00:32:45.419> should<00:32:45.600> be<00:32:45.720> fine 00:32:47.570 --> 00:32:47.580 align:start position:0% that should be fine 00:32:47.580 --> 00:32:49.010 align:start position:0% that should be fine um<00:32:47.760> let's<00:32:48.000> check<00:32:48.179> to<00:32:48.419> see<00:32:48.539> so<00:32:48.840> we're 00:32:49.010 --> 00:32:49.020 align:start position:0% um let's check to see so we're 00:32:49.020 --> 00:32:50.990 align:start position:0% um let's check to see so we're initiating<00:32:49.320> this<00:32:49.500> on<00:32:49.679> the<00:32:49.799> L2<00:32:50.159> side<00:32:50.399> once 00:32:50.990 --> 00:32:51.000 align:start position:0% initiating this on the L2 side once 00:32:51.000 --> 00:32:53.810 align:start position:0% initiating this on the L2 side once again<00:32:51.059> we<00:32:51.419> we<00:32:51.720> have<00:32:52.620> our<00:32:52.740> mapping<00:32:53.100> that<00:32:53.520> is<00:32:53.640> the 00:32:53.810 --> 00:32:53.820 align:start position:0% again we we have our mapping that is the 00:32:53.820 --> 00:32:55.669 align:start position:0% again we we have our mapping that is the source<00:32:54.120> of<00:32:54.179> truth<00:32:54.360> of<00:32:54.539> registration 00:32:55.669 --> 00:32:55.679 align:start position:0% source of truth of registration 00:32:55.679 --> 00:32:57.409 align:start position:0% source of truth of registration so<00:32:56.039> let's<00:32:56.220> uh<00:32:56.580> check<00:32:56.760> to<00:32:56.940> see<00:32:57.059> that<00:32:57.179> the<00:32:57.299> thing 00:32:57.409 --> 00:32:57.419 align:start position:0% so let's uh check to see that the thing 00:32:57.419 --> 00:32:58.610 align:start position:0% so let's uh check to see that the thing is<00:32:57.539> registered<00:32:57.840> and<00:32:58.020> also<00:32:58.200> get<00:32:58.260> the<00:32:58.380> L2 00:32:58.610 --> 00:32:58.620 align:start position:0% is registered and also get the L2 00:32:58.620 --> 00:32:59.630 align:start position:0% is registered and also get the L2 address 00:32:59.630 --> 00:32:59.640 align:start position:0% address 00:32:59.640 --> 00:33:01.250 align:start position:0% address so<00:32:59.820> again<00:33:00.059> we're<00:33:00.299> specifying<00:33:00.720> our<00:33:00.840> token<00:33:01.140> by 00:33:01.250 --> 00:33:01.260 align:start position:0% so again we're specifying our token by 00:33:01.260 --> 00:33:02.630 align:start position:0% so again we're specifying our token by the<00:33:01.380> L1<00:33:01.620> address<00:33:01.860> that's<00:33:02.100> always<00:33:02.220> the<00:33:02.399> source 00:33:02.630 --> 00:33:02.640 align:start position:0% the L1 address that's always the source 00:33:02.640 --> 00:33:04.909 align:start position:0% the L1 address that's always the source of<00:33:02.760> Truth 00:33:04.909 --> 00:33:04.919 align:start position:0% 00:33:04.919 --> 00:33:06.830 align:start position:0% um 00:33:06.830 --> 00:33:06.840 align:start position:0% um 00:33:06.840 --> 00:33:08.570 align:start position:0% um and<00:33:07.200> here<00:33:07.320> I<00:33:07.500> think<00:33:07.740> we<00:33:07.919> just<00:33:08.039> need<00:33:08.220> to<00:33:08.340> see 00:33:08.570 --> 00:33:08.580 align:start position:0% and here I think we just need to see 00:33:08.580 --> 00:33:11.330 align:start position:0% and here I think we just need to see that<00:33:08.820> it<00:33:09.059> is<00:33:09.419> registered 00:33:11.330 --> 00:33:11.340 align:start position:0% that it is registered 00:33:11.340 --> 00:33:12.889 align:start position:0% that it is registered yes 00:33:12.889 --> 00:33:12.899 align:start position:0% yes 00:33:12.899 --> 00:33:14.750 align:start position:0% yes um<00:33:12.960> just<00:33:13.140> like<00:33:13.260> before 00:33:14.750 --> 00:33:14.760 align:start position:0% um just like before 00:33:14.760 --> 00:33:16.909 align:start position:0% um just like before looking<00:33:15.299> for<00:33:15.480> how<00:33:15.600> to<00:33:15.720> address<00:33:15.960> require<00:33:16.380> that 00:33:16.909 --> 00:33:16.919 align:start position:0% looking for how to address require that 00:33:16.919 --> 00:33:22.430 align:start position:0% looking for how to address require that it<00:33:17.100> exists 00:33:22.430 --> 00:33:22.440 align:start position:0% 00:33:22.440 --> 00:33:24.350 align:start position:0% plus<00:33:22.820> autofill 00:33:24.350 --> 00:33:24.360 align:start position:0% plus autofill 00:33:24.360 --> 00:33:30.470 align:start position:0% plus autofill um 00:33:30.470 --> 00:33:30.480 align:start position:0% 00:33:30.480 --> 00:33:32.330 align:start position:0% okay 00:33:32.330 --> 00:33:32.340 align:start position:0% okay 00:33:32.340 --> 00:33:33.529 align:start position:0% okay um 00:33:33.529 --> 00:33:33.539 align:start position:0% um 00:33:33.539 --> 00:33:35.930 align:start position:0% um so<00:33:34.080> now<00:33:34.320> okay<00:33:34.559> for<00:33:34.799> a<00:33:34.980> withdrawal 00:33:35.930 --> 00:33:35.940 align:start position:0% so now okay for a withdrawal 00:33:35.940 --> 00:33:38.269 align:start position:0% so now okay for a withdrawal we<00:33:36.240> want<00:33:36.360> to<00:33:36.480> burn<00:33:36.600> first 00:33:38.269 --> 00:33:38.279 align:start position:0% we want to burn first 00:33:38.279 --> 00:33:40.250 align:start position:0% we want to burn first um<00:33:38.399> so<00:33:38.760> let's<00:33:38.880> fill<00:33:39.059> that<00:33:39.240> in<00:33:39.480> back<00:33:40.019> in<00:33:40.140> the 00:33:40.250 --> 00:33:40.260 align:start position:0% um so let's fill that in back in the 00:33:40.260 --> 00:33:41.750 align:start position:0% um so let's fill that in back in the token<00:33:40.559> we<00:33:40.679> want<00:33:40.860> to<00:33:40.919> expose<00:33:41.159> the<00:33:41.340> affordance 00:33:41.750 --> 00:33:41.760 align:start position:0% token we want to expose the affordance 00:33:41.760 --> 00:33:44.330 align:start position:0% token we want to expose the affordance for<00:33:41.940> the<00:33:42.059> gateway<00:33:42.360> to<00:33:42.480> burn 00:33:44.330 --> 00:33:44.340 align:start position:0% for the gateway to burn 00:33:44.340 --> 00:33:47.870 align:start position:0% for the gateway to burn um so<00:33:45.179> let's<00:33:45.360> do<00:33:45.779> that<00:33:46.260> in<00:33:47.100> this<00:33:47.220> case<00:33:47.340> we<00:33:47.640> also 00:33:47.870 --> 00:33:47.880 align:start position:0% um so let's do that in this case we also 00:33:47.880 --> 00:33:49.850 align:start position:0% um so let's do that in this case we also need<00:33:48.059> to<00:33:48.179> actually<00:33:48.419> verify<00:33:48.960> that<00:33:49.200> you're<00:33:49.559> uh 00:33:49.850 --> 00:33:49.860 align:start position:0% need to actually verify that you're uh 00:33:49.860 --> 00:33:51.169 align:start position:0% need to actually verify that you're uh that<00:33:50.039> you<00:33:50.279> know<00:33:50.340> this<00:33:50.519> owner<00:33:50.820> has<00:33:50.940> the<00:33:51.059> right 00:33:51.169 --> 00:33:51.179 align:start position:0% that you know this owner has the right 00:33:51.179 --> 00:33:52.370 align:start position:0% that you know this owner has the right to<00:33:51.299> burn<00:33:51.419> it<00:33:51.600> which<00:33:51.779> we<00:33:51.960> didn't<00:33:52.019> have<00:33:52.200> to<00:33:52.260> do 00:33:52.370 --> 00:33:52.380 align:start position:0% to burn it which we didn't have to do 00:33:52.380 --> 00:33:53.930 align:start position:0% to burn it which we didn't have to do for<00:33:52.500> mint 00:33:53.930 --> 00:33:53.940 align:start position:0% for mint 00:33:53.940 --> 00:33:55.610 align:start position:0% for mint um<00:33:54.000> basically<00:33:54.600> in<00:33:54.840> order<00:33:54.960> to<00:33:55.140> get<00:33:55.260> to<00:33:55.380> the<00:33:55.440> mint 00:33:55.610 --> 00:33:55.620 align:start position:0% um basically in order to get to the mint 00:33:55.620 --> 00:33:57.289 align:start position:0% um basically in order to get to the mint code<00:33:55.860> path<00:33:56.100> you<00:33:56.279> had<00:33:56.460> to<00:33:56.519> transfer<00:33:56.820> a<00:33:56.940> token<00:33:57.179> to 00:33:57.289 --> 00:33:57.299 align:start position:0% code path you had to transfer a token to 00:33:57.299 --> 00:33:58.789 align:start position:0% code path you had to transfer a token to begin<00:33:57.419> with<00:33:57.659> so<00:33:57.899> there<00:33:58.080> we<00:33:58.320> were<00:33:58.440> safe<00:33:58.620> that 00:33:58.789 --> 00:33:58.799 align:start position:0% begin with so there we were safe that 00:33:58.799 --> 00:34:00.769 align:start position:0% begin with so there we were safe that you<00:33:58.860> were<00:33:58.980> the<00:33:59.100> owner<00:33:59.399> in<00:33:59.820> this<00:33:59.940> case<00:34:00.120> you<00:34:00.659> just 00:34:00.769 --> 00:34:00.779 align:start position:0% you were the owner in this case you just 00:34:00.779 --> 00:34:03.409 align:start position:0% you were the owner in this case you just gave<00:34:00.899> me<00:34:01.019> a<00:34:01.140> token<00:34:01.380> ID<00:34:01.500> who<00:34:02.159> the<00:34:02.279> hell<00:34:02.399> are<00:34:02.519> you 00:34:03.409 --> 00:34:03.419 align:start position:0% gave me a token ID who the hell are you 00:34:03.419 --> 00:34:04.970 align:start position:0% gave me a token ID who the hell are you um<00:34:03.480> you<00:34:03.659> better<00:34:03.720> be<00:34:03.960> the<00:34:04.080> owner<00:34:04.320> so<00:34:04.679> let's<00:34:04.799> make 00:34:04.970 --> 00:34:04.980 align:start position:0% um you better be the owner so let's make 00:34:04.980 --> 00:34:06.710 align:start position:0% um you better be the owner so let's make sure<00:34:05.039> you're<00:34:05.159> the<00:34:05.340> owner 00:34:06.710 --> 00:34:06.720 align:start position:0% sure you're the owner 00:34:06.720 --> 00:34:09.230 align:start position:0% sure you're the owner um<00:34:06.980> so<00:34:07.980> the<00:34:08.280> Gateway<00:34:08.520> will<00:34:08.760> be<00:34:08.879> responsible 00:34:09.230 --> 00:34:09.240 align:start position:0% um so the Gateway will be responsible 00:34:09.240 --> 00:34:11.930 align:start position:0% um so the Gateway will be responsible for<00:34:09.480> passing<00:34:09.839> in<00:34:09.960> the<00:34:10.200> owner<00:34:10.560> address 00:34:11.930 --> 00:34:11.940 align:start position:0% for passing in the owner address 00:34:11.940 --> 00:34:15.349 align:start position:0% for passing in the owner address and<00:34:12.540> now<00:34:12.780> we<00:34:13.080> want<00:34:13.440> to<00:34:13.980> I<00:34:14.399> think<00:34:14.460> it's<00:34:14.700> owner<00:34:15.060> of 00:34:15.349 --> 00:34:15.359 align:start position:0% and now we want to I think it's owner of 00:34:15.359 --> 00:34:18.290 align:start position:0% and now we want to I think it's owner of I'm<00:34:16.020> blanking<00:34:16.440> out<00:34:16.560> that's<00:34:17.099> how<00:34:17.280> I<00:34:17.399> understand 00:34:18.290 --> 00:34:18.300 align:start position:0% I'm blanking out that's how I understand 00:34:18.300 --> 00:34:19.070 align:start position:0% I'm blanking out that's how I understand um 00:34:19.070 --> 00:34:19.080 align:start position:0% um 00:34:19.080 --> 00:34:20.570 align:start position:0% um I<00:34:19.440> think<00:34:19.560> that's<00:34:19.679> right 00:34:20.570 --> 00:34:20.580 align:start position:0% I think that's right 00:34:20.580 --> 00:34:22.369 align:start position:0% I think that's right um 00:34:22.369 --> 00:34:22.379 align:start position:0% um 00:34:22.379 --> 00:34:26.030 align:start position:0% um what's<00:34:22.740> that 00:34:26.030 --> 00:34:26.040 align:start position:0% 00:34:26.040 --> 00:34:29.089 align:start position:0% is<00:34:26.399> that<00:34:26.520> right<00:34:26.639> yeah<00:34:27.000> thank<00:34:27.780> you 00:34:29.089 --> 00:34:29.099 align:start position:0% is that right yeah thank you 00:34:29.099 --> 00:34:30.530 align:start position:0% is that right yeah thank you um 00:34:30.530 --> 00:34:30.540 align:start position:0% um 00:34:30.540 --> 00:34:32.149 align:start position:0% um so<00:34:30.899> we<00:34:30.960> want<00:34:31.080> to<00:34:31.080> acquire<00:34:31.379> require<00:34:31.740> that<00:34:32.040> it's 00:34:32.149 --> 00:34:32.159 align:start position:0% so we want to acquire require that it's 00:34:32.159 --> 00:34:33.770 align:start position:0% so we want to acquire require that it's the<00:34:32.339> owner<00:34:32.580> passed<00:34:32.940> in<00:34:33.000> let's<00:34:33.240> call<00:34:33.419> this<00:34:33.599> like 00:34:33.770 --> 00:34:33.780 align:start position:0% the owner passed in let's call this like 00:34:33.780 --> 00:34:35.750 align:start position:0% the owner passed in let's call this like whatever<00:34:34.260> it's<00:34:34.919> like<00:34:35.040> potential<00:34:35.460> owner 00:34:35.750 --> 00:34:35.760 align:start position:0% whatever it's like potential owner 00:34:35.760 --> 00:34:37.730 align:start position:0% whatever it's like potential owner should<00:34:35.879> be<00:34:36.000> owner<00:34:36.240> whatever 00:34:37.730 --> 00:34:37.740 align:start position:0% should be owner whatever 00:34:37.740 --> 00:34:39.710 align:start position:0% should be owner whatever um<00:34:37.859> yes 00:34:39.710 --> 00:34:39.720 align:start position:0% um yes 00:34:39.720 --> 00:34:41.930 align:start position:0% um yes cool<00:34:40.080> so<00:34:40.379> we<00:34:40.500> make<00:34:40.679> sure<00:34:40.859> that<00:34:41.220> this<00:34:41.520> so<00:34:41.700> yeah 00:34:41.930 --> 00:34:41.940 align:start position:0% cool so we make sure that this so yeah 00:34:41.940 --> 00:34:43.250 align:start position:0% cool so we make sure that this so yeah again<00:34:42.240> the<00:34:42.419> Gateway<00:34:42.659> is<00:34:42.780> responsible<00:34:43.139> for 00:34:43.250 --> 00:34:43.260 align:start position:0% again the Gateway is responsible for 00:34:43.260 --> 00:34:44.869 align:start position:0% again the Gateway is responsible for making<00:34:43.440> sure<00:34:43.619> that<00:34:43.800> that<00:34:43.980> owner<00:34:44.460> address<00:34:44.639> is 00:34:44.869 --> 00:34:44.879 align:start position:0% making sure that that owner address is 00:34:44.879 --> 00:34:46.490 align:start position:0% making sure that that owner address is passed<00:34:45.119> in<00:34:45.179> we<00:34:45.359> make<00:34:45.540> sure<00:34:45.599> you're<00:34:45.720> the<00:34:45.899> owner 00:34:46.490 --> 00:34:46.500 align:start position:0% passed in we make sure you're the owner 00:34:46.500 --> 00:34:48.409 align:start position:0% passed in we make sure you're the owner um<00:34:46.619> and<00:34:46.740> then<00:34:46.859> okay<00:34:46.980> once<00:34:47.280> we<00:34:47.399> are<00:34:47.520> we<00:34:47.760> can<00:34:47.879> we 00:34:48.409 --> 00:34:48.419 align:start position:0% um and then okay once we are we can we 00:34:48.419 --> 00:34:53.690 align:start position:0% um and then okay once we are we can we can<00:34:48.540> go<00:34:48.659> ahead<00:34:48.780> and<00:34:48.899> burn 00:34:53.690 --> 00:34:53.700 align:start position:0% 00:34:53.700 --> 00:34:55.250 align:start position:0% yes<00:34:54.179> maybe<00:34:54.359> that's<00:34:54.540> a<00:34:54.659> nicer<00:34:54.839> way<00:34:54.960> to<00:34:55.080> do<00:34:55.139> that 00:34:55.250 --> 00:34:55.260 align:start position:0% yes maybe that's a nicer way to do that 00:34:55.260 --> 00:34:57.349 align:start position:0% yes maybe that's a nicer way to do that but<00:34:55.679> that<00:34:56.220> works 00:34:57.349 --> 00:34:57.359 align:start position:0% but that works 00:34:57.359 --> 00:34:59.510 align:start position:0% but that works um<00:34:57.480> I<00:34:57.780> don't<00:34:57.839> think<00:34:58.080> there<00:34:58.260> is 00:34:59.510 --> 00:34:59.520 align:start position:0% um I don't think there is 00:34:59.520 --> 00:35:00.230 align:start position:0% um I don't think there is um 00:35:00.230 --> 00:35:00.240 align:start position:0% um 00:35:00.240 --> 00:35:02.810 align:start position:0% um okay<00:35:00.839> so<00:35:01.619> now<00:35:01.859> we've<00:35:02.040> exposed<00:35:02.280> Bridge<00:35:02.460> burnt 00:35:02.810 --> 00:35:02.820 align:start position:0% okay so now we've exposed Bridge burnt 00:35:02.820 --> 00:35:05.450 align:start position:0% okay so now we've exposed Bridge burnt oh<00:35:02.880> this<00:35:03.060> also<00:35:03.359> has<00:35:03.480> to<00:35:03.540> be<00:35:03.660> on<00:35:03.780> the<00:35:03.900> Gateway 00:35:05.450 --> 00:35:05.460 align:start position:0% oh this also has to be on the Gateway 00:35:05.460 --> 00:35:07.670 align:start position:0% oh this also has to be on the Gateway of<00:35:05.880> course<00:35:06.060> would<00:35:06.900> have<00:35:07.080> been<00:35:07.200> critical 00:35:07.670 --> 00:35:07.680 align:start position:0% of course would have been critical 00:35:07.680 --> 00:35:09.109 align:start position:0% of course would have been critical vulnerability 00:35:09.109 --> 00:35:09.119 align:start position:0% vulnerability 00:35:09.119 --> 00:35:10.190 align:start position:0% vulnerability um 00:35:10.190 --> 00:35:10.200 align:start position:0% um 00:35:10.200 --> 00:35:13.790 align:start position:0% um okay<00:35:10.560> so<00:35:10.980> now<00:35:11.099> we<00:35:11.280> can<00:35:11.400> burn 00:35:13.790 --> 00:35:13.800 align:start position:0% 00:35:13.800 --> 00:35:14.870 align:start position:0% um 00:35:14.870 --> 00:35:14.880 align:start position:0% um 00:35:14.880 --> 00:35:17.210 align:start position:0% um yeah 00:35:17.210 --> 00:35:17.220 align:start position:0% 00:35:17.220 --> 00:35:19.609 align:start position:0% so<00:35:17.640> we<00:35:17.940> connect<00:35:18.119> to<00:35:18.359> the<00:35:18.540> Token<00:35:18.839> on<00:35:19.200> the<00:35:19.320> L2 00:35:19.609 --> 00:35:19.619 align:start position:0% so we connect to the Token on the L2 00:35:19.619 --> 00:35:21.890 align:start position:0% so we connect to the Token on the L2 side<00:35:19.920> of<00:35:20.640> the<00:35:20.820> address<00:35:21.000> we<00:35:21.180> just<00:35:21.359> got<00:35:21.480> from<00:35:21.780> the 00:35:21.890 --> 00:35:21.900 align:start position:0% side of the address we just got from the 00:35:21.900 --> 00:35:25.370 align:start position:0% side of the address we just got from the registry<00:35:22.320> we<00:35:23.220> call<00:35:23.400> Bridge<00:35:23.640> burn<00:35:23.940> we<00:35:24.780> pass<00:35:25.079> in 00:35:25.370 --> 00:35:25.380 align:start position:0% registry we call Bridge burn we pass in 00:35:25.380 --> 00:35:27.589 align:start position:0% registry we call Bridge burn we pass in the<00:35:25.980> owner<00:35:26.280> or<00:35:26.460> claimed<00:35:26.820> owner<00:35:27.119> which<00:35:27.420> will 00:35:27.589 --> 00:35:27.599 align:start position:0% the owner or claimed owner which will 00:35:27.599 --> 00:35:31.670 align:start position:0% the owner or claimed owner which will just<00:35:27.780> be<00:35:27.900> the<00:35:28.079> caller<00:35:28.380> of<00:35:28.500> this<00:35:28.619> method 00:35:31.670 --> 00:35:31.680 align:start position:0% 00:35:31.680 --> 00:35:35.750 align:start position:0% um<00:35:31.740> and<00:35:31.920> the<00:35:32.040> token<00:35:32.400> ID 00:35:35.750 --> 00:35:35.760 align:start position:0% 00:35:35.760 --> 00:35:37.849 align:start position:0% does<00:35:36.180> that<00:35:36.300> work<00:35:36.480> yeah 00:35:37.849 --> 00:35:37.859 align:start position:0% does that work yeah 00:35:37.859 --> 00:35:39.290 align:start position:0% does that work yeah yeah 00:35:39.290 --> 00:35:39.300 align:start position:0% yeah 00:35:39.300 --> 00:35:40.490 align:start position:0% yeah okay 00:35:40.490 --> 00:35:40.500 align:start position:0% okay 00:35:40.500 --> 00:35:42.890 align:start position:0% okay um<00:35:41.040> cool<00:35:41.400> so<00:35:41.579> we<00:35:41.760> burn<00:35:41.880> on<00:35:42.000> the<00:35:42.119> L2<00:35:42.359> side<00:35:42.540> now<00:35:42.720> we 00:35:42.890 --> 00:35:42.900 align:start position:0% um cool so we burn on the L2 side now we 00:35:42.900 --> 00:35:44.150 align:start position:0% um cool so we burn on the L2 side now we want<00:35:43.020> to<00:35:43.140> send<00:35:43.320> a<00:35:43.440> cross<00:35:43.560> chain<00:35:43.800> message<00:35:43.980> down 00:35:44.150 --> 00:35:44.160 align:start position:0% want to send a cross chain message down 00:35:44.160 --> 00:35:45.290 align:start position:0% want to send a cross chain message down to<00:35:44.339> layer<00:35:44.579> one 00:35:45.290 --> 00:35:45.300 align:start position:0% to layer one 00:35:45.300 --> 00:35:46.910 align:start position:0% to layer one um<00:35:45.420> which<00:35:45.660> once<00:35:46.020> it<00:35:46.079> reaches<00:35:46.320> layer<00:35:46.619> one<00:35:46.740> we'll 00:35:46.910 --> 00:35:46.920 align:start position:0% um which once it reaches layer one we'll 00:35:46.920 --> 00:35:48.530 align:start position:0% um which once it reaches layer one we'll release<00:35:47.099> the<00:35:47.339> same<00:35:47.520> token<00:35:47.820> from<00:35:47.940> escrow<00:35:48.240> same 00:35:48.530 --> 00:35:48.540 align:start position:0% release the same token from escrow same 00:35:48.540 --> 00:35:50.390 align:start position:0% release the same token from escrow same token<00:35:48.839> we're<00:35:49.079> just<00:35:49.320> notice<00:35:49.859> I<00:35:50.040> didn't<00:35:50.160> say 00:35:50.390 --> 00:35:50.400 align:start position:0% token we're just notice I didn't say 00:35:50.400 --> 00:35:51.950 align:start position:0% token we're just notice I didn't say this<00:35:50.579> explicitly<00:35:51.300> but<00:35:51.420> we're<00:35:51.599> just<00:35:51.780> sort<00:35:51.900> of 00:35:51.950 --> 00:35:51.960 align:start position:0% this explicitly but we're just sort of 00:35:51.960 --> 00:35:53.690 align:start position:0% this explicitly but we're just sort of tracking<00:35:52.200> tokens<00:35:52.500> by<00:35:52.680> ideas<00:35:52.920> we're<00:35:53.520> just 00:35:53.690 --> 00:35:53.700 align:start position:0% tracking tokens by ideas we're just 00:35:53.700 --> 00:35:55.430 align:start position:0% tracking tokens by ideas we're just keeping<00:35:53.940> the<00:35:54.000> same<00:35:54.119> idea<00:35:54.420> two<00:35:55.020> as<00:35:55.140> it<00:35:55.260> has<00:35:55.320> on 00:35:55.430 --> 00:35:55.440 align:start position:0% keeping the same idea two as it has on 00:35:55.440 --> 00:35:58.370 align:start position:0% keeping the same idea two as it has on L1<00:35:55.800> because<00:35:56.280> why<00:35:56.640> not 00:35:58.370 --> 00:35:58.380 align:start position:0% L1 because why not 00:35:58.380 --> 00:36:00.050 align:start position:0% L1 because why not um<00:35:58.500> okay<00:35:58.740> so<00:35:59.040> we<00:35:59.220> need<00:35:59.339> the<00:35:59.640> destination 00:36:00.050 --> 00:36:00.060 align:start position:0% um okay so we need the destination 00:36:00.060 --> 00:36:02.569 align:start position:0% um okay so we need the destination address<00:36:00.359> which<00:36:00.660> we<00:36:00.900> have<00:36:01.020> the<00:36:01.800> L1<00:36:02.099> counterpart 00:36:02.569 --> 00:36:02.579 align:start position:0% address which we have the L1 counterpart 00:36:02.579 --> 00:36:03.710 align:start position:0% address which we have the L1 counterpart Gateway 00:36:03.710 --> 00:36:03.720 align:start position:0% Gateway 00:36:03.720 --> 00:36:05.810 align:start position:0% Gateway um<00:36:03.839> let's<00:36:04.079> do<00:36:04.380> what<00:36:04.859> we<00:36:04.980> did<00:36:05.099> before<00:36:05.339> and 00:36:05.810 --> 00:36:05.820 align:start position:0% um let's do what we did before and 00:36:05.820 --> 00:36:08.150 align:start position:0% um let's do what we did before and encode 00:36:08.150 --> 00:36:08.160 align:start position:0% encode 00:36:08.160 --> 00:36:09.710 align:start position:0% encode um a<00:36:08.400> function<00:36:08.579> call<00:36:08.760> here<00:36:09.240> because<00:36:09.480> we'll 00:36:09.710 --> 00:36:09.720 align:start position:0% um a function call here because we'll 00:36:09.720 --> 00:36:12.170 align:start position:0% um a function call here because we'll just<00:36:09.900> do<00:36:10.020> it<00:36:10.079> in<00:36:10.260> line<00:36:10.380> not<00:36:10.680> as<00:36:10.800> a<00:36:10.980> new<00:36:11.040> method 00:36:12.170 --> 00:36:12.180 align:start position:0% just do it in line not as a new method 00:36:12.180 --> 00:36:14.270 align:start position:0% just do it in line not as a new method okay<00:36:12.660> so<00:36:12.960> what's<00:36:13.140> our<00:36:13.500> function<00:36:13.859> and<00:36:14.040> what<00:36:14.220> do 00:36:14.270 --> 00:36:14.280 align:start position:0% okay so what's our function and what do 00:36:14.280 --> 00:36:16.910 align:start position:0% okay so what's our function and what do we<00:36:14.400> need<00:36:14.579> to<00:36:14.880> send<00:36:15.180> is<00:36:15.599> the<00:36:15.839> question<00:36:16.020> in<00:36:16.800> order 00:36:16.910 --> 00:36:16.920 align:start position:0% we need to send is the question in order 00:36:16.920 --> 00:36:19.190 align:start position:0% we need to send is the question in order to<00:36:17.280> sort<00:36:17.520> of<00:36:17.579> release<00:36:17.760> it<00:36:18.060> from<00:36:18.540> escrow<00:36:18.839> on<00:36:19.079> the 00:36:19.190 --> 00:36:19.200 align:start position:0% to sort of release it from escrow on the 00:36:19.200 --> 00:36:20.990 align:start position:0% to sort of release it from escrow on the L1<00:36:19.440> side 00:36:20.990 --> 00:36:21.000 align:start position:0% L1 side 00:36:21.000 --> 00:36:23.450 align:start position:0% L1 side um<00:36:21.119> we<00:36:21.420> can<00:36:21.660> speak 00:36:23.450 --> 00:36:23.460 align:start position:0% um we can speak 00:36:23.460 --> 00:36:25.730 align:start position:0% um we can speak so<00:36:23.880> our<00:36:24.000> method<00:36:24.540> here<00:36:24.780> is<00:36:25.079> called<00:36:25.320> finalize 00:36:25.730 --> 00:36:25.740 align:start position:0% so our method here is called finalize 00:36:25.740 --> 00:36:30.349 align:start position:0% so our method here is called finalize withdrawal<00:36:26.339> we<00:36:27.119> specify<00:36:27.599> these<00:36:28.260> things 00:36:30.349 --> 00:36:30.359 align:start position:0% withdrawal we specify these things 00:36:30.359 --> 00:36:33.470 align:start position:0% withdrawal we specify these things um<00:36:30.420> so<00:36:30.960> let's<00:36:31.140> encode<00:36:31.440> that<00:36:31.619> on<00:36:31.740> the<00:36:31.800> L2<00:36:32.099> side 00:36:33.470 --> 00:36:33.480 align:start position:0% um so let's encode that on the L2 side 00:36:33.480 --> 00:36:34.970 align:start position:0% um so let's encode that on the L2 side um<00:36:33.599> I<00:36:33.720> forgot<00:36:33.960> them<00:36:34.079> already 00:36:34.970 --> 00:36:34.980 align:start position:0% um I forgot them already 00:36:34.980 --> 00:36:37.010 align:start position:0% um I forgot them already we<00:36:35.400> specify<00:36:35.820> oh<00:36:36.060> and<00:36:36.180> token<00:36:36.420> token<00:36:36.660> ID<00:36:36.720> in<00:36:36.960> the 00:36:37.010 --> 00:36:37.020 align:start position:0% we specify oh and token token ID in the 00:36:37.020 --> 00:36:38.569 align:start position:0% we specify oh and token token ID in the two<00:36:37.140> address<00:36:37.320> okay 00:36:38.569 --> 00:36:38.579 align:start position:0% two address okay 00:36:38.579 --> 00:36:40.849 align:start position:0% two address okay and<00:36:39.119> it's<00:36:39.359> called 00:36:40.849 --> 00:36:40.859 align:start position:0% and it's called 00:36:40.859 --> 00:36:45.770 align:start position:0% and it's called finalize<00:36:41.579> withdrawal 00:36:45.770 --> 00:36:45.780 align:start position:0% 00:36:45.780 --> 00:36:51.290 align:start position:0% um 00:36:51.290 --> 00:36:51.300 align:start position:0% 00:36:51.300 --> 00:37:03.950 align:start position:0% um<00:36:51.480> yeah<00:36:52.280> uh<00:36:53.700> Owen<00:36:54.240> token 00:37:03.950 --> 00:37:03.960 align:start position:0% 00:37:03.960 --> 00:37:06.290 align:start position:0% e<00:37:04.740> oh<00:37:05.040> and<00:37:05.220> let's<00:37:05.400> call<00:37:05.579> it<00:37:05.700> something<00:37:05.880> so<00:37:06.180> this 00:37:06.290 --> 00:37:06.300 align:start position:0% e oh and let's call it something so this 00:37:06.300 --> 00:37:07.730 align:start position:0% e oh and let's call it something so this would<00:37:06.420> be<00:37:06.540> the<00:37:06.599> L1<00:37:06.839> message<00:37:07.079> call<00:37:07.260> data<00:37:07.619> in 00:37:07.730 --> 00:37:07.740 align:start position:0% would be the L1 message call data in 00:37:07.740 --> 00:37:12.109 align:start position:0% would be the L1 message call data in this<00:37:07.859> case 00:37:12.109 --> 00:37:12.119 align:start position:0% 00:37:12.119 --> 00:37:16.910 align:start position:0% um that<00:37:12.480> doesn't<00:37:12.660> oh<00:37:13.140> selector<00:37:13.980> yes 00:37:16.910 --> 00:37:16.920 align:start position:0% 00:37:16.920 --> 00:37:18.349 align:start position:0% this<00:37:17.220> will<00:37:17.460> be<00:37:17.579> encode<00:37:17.760> it<00:37:17.880> with<00:37:18.000> the<00:37:18.060> function 00:37:18.349 --> 00:37:18.359 align:start position:0% this will be encode it with the function 00:37:18.359 --> 00:37:21.530 align:start position:0% this will be encode it with the function selector<00:37:18.780> on<00:37:19.619> my<00:37:19.800> linter<00:37:20.099> just<00:37:20.339> be<00:37:20.520> nice<00:37:20.700> it 00:37:21.530 --> 00:37:21.540 align:start position:0% selector on my linter just be nice it 00:37:21.540 --> 00:37:23.030 align:start position:0% selector on my linter just be nice it will<00:37:21.660> not<00:37:21.780> oh<00:37:22.020> well 00:37:23.030 --> 00:37:23.040 align:start position:0% will not oh well 00:37:23.040 --> 00:37:24.470 align:start position:0% will not oh well um<00:37:23.099> okay<00:37:23.700> so<00:37:23.940> this<00:37:24.060> is<00:37:24.119> the<00:37:24.180> message<00:37:24.300> we're 00:37:24.470 --> 00:37:24.480 align:start position:0% um okay so this is the message we're 00:37:24.480 --> 00:37:29.030 align:start position:0% um okay so this is the message we're encoding<00:37:24.900> to<00:37:24.960> send<00:37:25.079> to<00:37:25.200> L1<00:37:25.560> and<00:37:26.099> now 00:37:29.030 --> 00:37:29.040 align:start position:0% 00:37:29.040 --> 00:37:30.349 align:start position:0% um 00:37:30.349 --> 00:37:30.359 align:start position:0% um 00:37:30.359 --> 00:37:34.130 align:start position:0% um there<00:37:30.780> we<00:37:30.900> go<00:37:31.020> is<00:37:31.680> that<00:37:31.859> compiling 00:37:34.130 --> 00:37:34.140 align:start position:0% there we go is that compiling 00:37:34.140 --> 00:37:35.450 align:start position:0% there we go is that compiling yes 00:37:35.450 --> 00:37:35.460 align:start position:0% yes 00:37:35.460 --> 00:37:36.109 align:start position:0% yes um 00:37:36.109 --> 00:37:36.119 align:start position:0% um 00:37:36.119 --> 00:37:38.390 align:start position:0% um now<00:37:36.660> we<00:37:36.839> will<00:37:37.020> uh<00:37:37.320> yeah<00:37:37.619> we'll<00:37:37.859> send<00:37:38.160> a<00:37:38.280> message 00:37:38.390 --> 00:37:38.400 align:start position:0% now we will uh yeah we'll send a message 00:37:38.400 --> 00:37:48.710 align:start position:0% now we will uh yeah we'll send a message to<00:37:38.579> L1<00:37:38.880> with<00:37:39.119> the<00:37:39.180> arbsys<00:37:39.599> pre-compile<00:37:40.140> yes 00:37:48.710 --> 00:37:48.720 align:start position:0% 00:37:48.720 --> 00:38:06.710 align:start position:0% yes 00:38:06.710 --> 00:38:06.720 align:start position:0% 00:38:06.720 --> 00:38:08.750 align:start position:0% Yeah<00:38:07.500> so<00:38:07.980> basically<00:38:08.220> that's<00:38:08.339> a<00:38:08.520> good<00:38:08.640> question 00:38:08.750 --> 00:38:08.760 align:start position:0% Yeah so basically that's a good question 00:38:08.760 --> 00:38:10.010 align:start position:0% Yeah so basically that's a good question so<00:38:09.119> the<00:38:09.240> question<00:38:09.359> between<00:38:09.540> here<00:38:09.839> was<00:38:09.960> like 00:38:10.010 --> 00:38:10.020 align:start position:0% so the question between here was like 00:38:10.020 --> 00:38:12.290 align:start position:0% so the question between here was like how<00:38:10.140> do<00:38:10.260> we<00:38:10.320> ensure<00:38:10.619> that<00:38:11.280> this<00:38:11.400> mapping<00:38:11.820> is 00:38:12.290 --> 00:38:12.300 align:start position:0% how do we ensure that this mapping is 00:38:12.300 --> 00:38:14.569 align:start position:0% how do we ensure that this mapping is legit<00:38:12.599> essentially<00:38:13.320> right<00:38:13.680> like<00:38:14.099> how<00:38:14.280> do<00:38:14.520> we 00:38:14.569 --> 00:38:14.579 align:start position:0% legit essentially right like how do we 00:38:14.579 --> 00:38:15.890 align:start position:0% legit essentially right like how do we know<00:38:14.700> this<00:38:14.820> isn't<00:38:15.060> the<00:38:15.240> actual<00:38:15.420> mapping<00:38:15.780> and 00:38:15.890 --> 00:38:15.900 align:start position:0% know this isn't the actual mapping and 00:38:15.900 --> 00:38:17.329 align:start position:0% know this isn't the actual mapping and basically<00:38:16.200> that's<00:38:16.440> the<00:38:16.680> registration<00:38:17.099> step 00:38:17.329 --> 00:38:17.339 align:start position:0% basically that's the registration step 00:38:17.339 --> 00:38:19.550 align:start position:0% basically that's the registration step ensures<00:38:17.760> that<00:38:18.000> so<00:38:18.599> we're<00:38:18.780> we're<00:38:19.020> inheriting 00:38:19.550 --> 00:38:19.560 align:start position:0% ensures that so we're we're inheriting 00:38:19.560 --> 00:38:21.290 align:start position:0% ensures that so we're we're inheriting whatever<00:38:19.920> trust<00:38:20.400> we<00:38:20.579> give<00:38:20.700> to<00:38:20.880> the<00:38:21.000> L1 00:38:21.290 --> 00:38:21.300 align:start position:0% whatever trust we give to the L1 00:38:21.300 --> 00:38:23.810 align:start position:0% whatever trust we give to the L1 contract<00:38:21.780> only<00:38:22.440> the<00:38:22.619> L1<00:38:22.920> contract<00:38:23.280> itself<00:38:23.579> can 00:38:23.810 --> 00:38:23.820 align:start position:0% contract only the L1 contract itself can 00:38:23.820 --> 00:38:24.650 align:start position:0% contract only the L1 contract itself can register 00:38:24.650 --> 00:38:24.660 align:start position:0% register 00:38:24.660 --> 00:38:26.510 align:start position:0% register so<00:38:25.020> the<00:38:25.140> L1<00:38:25.440> contract<00:38:25.859> the<00:38:26.040> token<00:38:26.280> contract 00:38:26.510 --> 00:38:26.520 align:start position:0% so the L1 contract the token contract 00:38:26.520 --> 00:38:27.589 align:start position:0% so the L1 contract the token contract itself<00:38:26.820> is<00:38:26.940> the<00:38:27.060> only<00:38:27.119> thing<00:38:27.240> that<00:38:27.420> can 00:38:27.589 --> 00:38:27.599 align:start position:0% itself is the only thing that can 00:38:27.599 --> 00:38:29.270 align:start position:0% itself is the only thing that can self-register<00:38:28.079> and<00:38:28.320> it<00:38:28.440> specifies<00:38:28.800> the<00:38:28.980> L2 00:38:29.270 --> 00:38:29.280 align:start position:0% self-register and it specifies the L2 00:38:29.280 --> 00:38:31.730 align:start position:0% self-register and it specifies the L2 contract<00:38:29.640> so<00:38:30.300> if<00:38:30.420> it<00:38:30.540> lies<00:38:30.900> it<00:38:31.079> lies<00:38:31.440> but 00:38:31.730 --> 00:38:31.740 align:start position:0% contract so if it lies it lies but 00:38:31.740 --> 00:38:32.630 align:start position:0% contract so if it lies it lies but that's 00:38:32.630 --> 00:38:32.640 align:start position:0% that's 00:38:32.640 --> 00:38:34.609 align:start position:0% that's right<00:38:32.880> then<00:38:33.540> that<00:38:33.720> means<00:38:33.839> that<00:38:34.020> the<00:38:34.079> elwind 00:38:34.609 --> 00:38:34.619 align:start position:0% right then that means that the elwind 00:38:34.619 --> 00:38:36.410 align:start position:0% right then that means that the elwind contract<00:38:34.980> was<00:38:35.099> malicious<00:38:35.520> or<00:38:36.000> if<00:38:36.119> it<00:38:36.240> gives 00:38:36.410 --> 00:38:36.420 align:start position:0% contract was malicious or if it gives 00:38:36.420 --> 00:38:38.030 align:start position:0% contract was malicious or if it gives the<00:38:36.599> wrong<00:38:36.720> address<00:38:36.900> that's<00:38:37.200> its<00:38:37.500> fault<00:38:37.680> okay 00:38:38.030 --> 00:38:38.040 align:start position:0% the wrong address that's its fault okay 00:38:38.040 --> 00:38:39.890 align:start position:0% the wrong address that's its fault okay so<00:38:38.460> we're<00:38:38.520> assuming<00:38:38.880> that<00:38:39.000> this<00:38:39.180> L1<00:38:39.480> contract 00:38:39.890 --> 00:38:39.900 align:start position:0% so we're assuming that this L1 contract 00:38:39.900 --> 00:38:41.210 align:start position:0% so we're assuming that this L1 contract over<00:38:40.140> here<00:38:40.380> when<00:38:40.800> it<00:38:40.920> makes<00:38:41.040> this 00:38:41.210 --> 00:38:41.220 align:start position:0% over here when it makes this 00:38:41.220 --> 00:38:42.589 align:start position:0% over here when it makes this registration<00:38:41.640> call 00:38:42.589 --> 00:38:42.599 align:start position:0% registration call 00:38:42.599 --> 00:38:45.650 align:start position:0% registration call picks<00:38:43.020> the<00:38:43.079> right<00:38:43.200> address<00:38:43.440> on<00:38:44.040> the<00:38:44.099> L2<00:38:44.400> side 00:38:45.650 --> 00:38:45.660 align:start position:0% picks the right address on the L2 side 00:38:45.660 --> 00:38:47.510 align:start position:0% picks the right address on the L2 side right<00:38:45.839> I<00:38:46.740> guess<00:38:46.800> yeah<00:38:47.040> I<00:38:47.160> don't<00:38:47.280> know<00:38:47.339> if<00:38:47.400> that 00:38:47.510 --> 00:38:47.520 align:start position:0% right I guess yeah I don't know if that 00:38:47.520 --> 00:38:48.589 align:start position:0% right I guess yeah I don't know if that really<00:38:47.640> answers<00:38:47.880> your<00:38:48.060> question<00:38:48.240> but<00:38:48.359> I<00:38:48.480> think 00:38:48.589 --> 00:38:48.599 align:start position:0% really answers your question but I think 00:38:48.599 --> 00:38:50.390 align:start position:0% really answers your question but I think maybe<00:38:48.720> the<00:38:48.960> key<00:38:49.079> thing<00:38:49.200> is<00:38:49.440> only<00:38:49.980> this 00:38:50.390 --> 00:38:50.400 align:start position:0% maybe the key thing is only this 00:38:50.400 --> 00:38:52.130 align:start position:0% maybe the key thing is only this register<00:38:50.760> call<00:38:51.060> it<00:38:51.300> can<00:38:51.420> update<00:38:51.720> the<00:38:51.839> mapping 00:38:52.130 --> 00:38:52.140 align:start position:0% register call it can update the mapping 00:38:52.140 --> 00:38:54.770 align:start position:0% register call it can update the mapping and<00:38:52.440> only<00:38:52.619> the<00:38:52.859> token<00:38:53.160> itself<00:38:53.339> can<00:38:53.520> affect<00:38:53.760> it 00:38:54.770 --> 00:38:54.780 align:start position:0% and only the token itself can affect it 00:38:54.780 --> 00:38:56.089 align:start position:0% and only the token itself can affect it um 00:38:56.089 --> 00:38:56.099 align:start position:0% um 00:38:56.099 --> 00:38:57.710 align:start position:0% um um<00:38:56.160> I<00:38:56.280> hope<00:38:56.339> that's<00:38:56.520> helped 00:38:57.710 --> 00:38:57.720 align:start position:0% um I hope that's helped 00:38:57.720 --> 00:38:58.550 align:start position:0% um I hope that's helped um 00:38:58.550 --> 00:38:58.560 align:start position:0% um 00:38:58.560 --> 00:39:01.069 align:start position:0% um okay<00:38:59.160> where<00:38:59.880> are<00:39:00.000> we<00:39:00.180> here<00:39:00.420> oh<00:39:00.660> yeah<00:39:00.780> now<00:39:00.960> we 00:39:01.069 --> 00:39:01.079 align:start position:0% okay where are we here oh yeah now we 00:39:01.079 --> 00:39:02.329 align:start position:0% okay where are we here oh yeah now we have<00:39:01.200> to<00:39:01.260> send<00:39:01.380> our<00:39:01.560> send<00:39:01.800> our<00:39:01.920> actual<00:39:02.160> message 00:39:02.329 --> 00:39:02.339 align:start position:0% have to send our send our actual message 00:39:02.339 --> 00:39:06.109 align:start position:0% have to send our send our actual message so<00:39:02.760> let's<00:39:03.300> do<00:39:03.660> that<00:39:03.839> here's<00:39:04.500> our<00:39:04.619> message 00:39:06.109 --> 00:39:06.119 align:start position:0% so let's do that here's our message 00:39:06.119 --> 00:39:08.569 align:start position:0% so let's do that here's our message um<00:39:06.720> we<00:39:07.140> have<00:39:07.260> this<00:39:07.440> Arab<00:39:07.740> system<00:39:07.920> by<00:39:08.400> the<00:39:08.579> way 00:39:08.569 --> 00:39:08.579 align:start position:0% um we have this Arab system by the way 00:39:08.579 --> 00:39:09.650 align:start position:0% um we have this Arab system by the way I'm<00:39:08.760> just<00:39:08.880> you<00:39:09.060> know<00:39:09.119> in<00:39:09.240> the<00:39:09.300> interest<00:39:09.420> of 00:39:09.650 --> 00:39:09.660 align:start position:0% I'm just you know in the interest of 00:39:09.660 --> 00:39:10.910 align:start position:0% I'm just you know in the interest of time<00:39:09.780> not<00:39:10.020> showing<00:39:10.320> but<00:39:10.440> all<00:39:10.560> this<00:39:10.680> stuff<00:39:10.800> is 00:39:10.910 --> 00:39:10.920 align:start position:0% time not showing but all this stuff is 00:39:10.920 --> 00:39:13.250 align:start position:0% time not showing but all this stuff is imported<00:39:11.280> these<00:39:11.640> are<00:39:11.700> some<00:39:11.940> uh<00:39:12.540> this<00:39:12.960> is<00:39:13.079> like 00:39:13.250 --> 00:39:13.260 align:start position:0% imported these are some uh this is like 00:39:13.260 --> 00:39:14.690 align:start position:0% imported these are some uh this is like our<00:39:13.500> library 00:39:14.690 --> 00:39:14.700 align:start position:0% our library 00:39:14.700 --> 00:39:17.510 align:start position:0% our library um<00:39:14.760> where<00:39:14.940> we<00:39:15.060> publish<00:39:15.420> these<00:39:15.780> interfaces<00:39:16.320> but 00:39:17.510 --> 00:39:17.520 align:start position:0% um where we publish these interfaces but 00:39:17.520 --> 00:39:19.010 align:start position:0% um where we publish these interfaces but anyway 00:39:19.010 --> 00:39:19.020 align:start position:0% anyway 00:39:19.020 --> 00:39:20.690 align:start position:0% anyway um<00:39:19.140> so<00:39:19.380> again<00:39:19.500> it's<00:39:19.740> just<00:39:19.920> a<00:39:20.099> pre-compile<00:39:20.520> at 00:39:20.690 --> 00:39:20.700 align:start position:0% um so again it's just a pre-compile at 00:39:20.700 --> 00:39:22.069 align:start position:0% um so again it's just a pre-compile at address<00:39:20.820> 100. 00:39:22.069 --> 00:39:22.079 align:start position:0% address 100. 00:39:22.079 --> 00:39:24.890 align:start position:0% address 100. and<00:39:22.980> our<00:39:23.460> method<00:39:23.760> that<00:39:23.880> we're<00:39:24.000> using<00:39:24.240> is<00:39:24.420> ntx 00:39:24.890 --> 00:39:24.900 align:start position:0% and our method that we're using is ntx 00:39:24.900 --> 00:39:27.410 align:start position:0% and our method that we're using is ntx to<00:39:25.079> layer<00:39:25.380> one 00:39:27.410 --> 00:39:27.420 align:start position:0% to layer one 00:39:27.420 --> 00:39:29.750 align:start position:0% to layer one um<00:39:27.480> the<00:39:28.079> address<00:39:28.380> is<00:39:28.800> the<00:39:29.040> Gateway<00:39:29.280> contract 00:39:29.750 --> 00:39:29.760 align:start position:0% um the address is the Gateway contract 00:39:29.760 --> 00:39:31.490 align:start position:0% um the address is the Gateway contract counterpart<00:39:30.359> Gateway<00:39:30.780> or<00:39:31.020> whatever<00:39:31.200> it's 00:39:31.490 --> 00:39:31.500 align:start position:0% counterpart Gateway or whatever it's 00:39:31.500 --> 00:39:34.310 align:start position:0% counterpart Gateway or whatever it's called<00:39:31.880> counterpart<00:39:32.880> L1<00:39:33.180> Gateway 00:39:34.310 --> 00:39:34.320 align:start position:0% called counterpart L1 Gateway 00:39:34.320 --> 00:39:35.810 align:start position:0% called counterpart L1 Gateway not<00:39:34.680> the<00:39:34.859> earliest<00:39:35.160> version<00:39:35.339> this<00:39:35.520> time<00:39:35.640> we 00:39:35.810 --> 00:39:35.820 align:start position:0% not the earliest version this time we 00:39:35.820 --> 00:39:37.730 align:start position:0% not the earliest version this time we want<00:39:35.940> the<00:39:36.060> actual<00:39:36.240> address 00:39:37.730 --> 00:39:37.740 align:start position:0% want the actual address 00:39:37.740 --> 00:39:42.589 align:start position:0% want the actual address um<00:39:37.800> and<00:39:38.460> we'll<00:39:38.700> send<00:39:39.060> the<00:39:39.300> call<00:39:39.420> data 00:39:42.589 --> 00:39:42.599 align:start position:0% 00:39:42.599 --> 00:39:47.210 align:start position:0% um 00:39:47.210 --> 00:39:47.220 align:start position:0% 00:39:47.220 --> 00:39:49.730 align:start position:0% what<00:39:47.460> am<00:39:47.520> I<00:39:47.640> doing 00:39:49.730 --> 00:39:49.740 align:start position:0% what am I doing 00:39:49.740 --> 00:39:53.150 align:start position:0% what am I doing oh<00:39:50.040> address<00:39:50.400> sorry 00:39:53.150 --> 00:39:53.160 align:start position:0% 00:39:53.160 --> 00:39:56.690 align:start position:0% there<00:39:53.460> we<00:39:53.579> go<00:39:53.700> address<00:39:54.359> 100.<00:39:55.500> and<00:39:56.040> that<00:39:56.220> looks 00:39:56.690 --> 00:39:56.700 align:start position:0% there we go address 100. and that looks 00:39:56.700 --> 00:39:58.069 align:start position:0% there we go address 100. and that looks right<00:39:56.880> to<00:39:57.119> me 00:39:58.069 --> 00:39:58.079 align:start position:0% right to me 00:39:58.079 --> 00:39:59.390 align:start position:0% right to me yes 00:39:59.390 --> 00:39:59.400 align:start position:0% yes 00:39:59.400 --> 00:40:01.069 align:start position:0% yes um I<00:39:59.520> think<00:39:59.640> that's<00:39:59.760> all<00:39:59.880> we<00:40:00.000> need<00:40:00.119> to<00:40:00.240> do<00:40:00.359> here 00:40:01.069 --> 00:40:01.079 align:start position:0% um I think that's all we need to do here 00:40:01.079 --> 00:40:02.569 align:start position:0% um I think that's all we need to do here I<00:40:01.260> think<00:40:01.440> I<00:40:01.619> missed<00:40:01.800> a<00:40:01.859> return<00:40:01.920> statement<00:40:02.339> or 00:40:02.569 --> 00:40:02.579 align:start position:0% I think I missed a return statement or 00:40:02.579 --> 00:40:04.490 align:start position:0% I think I missed a return statement or two<00:40:02.700> earlier 00:40:04.490 --> 00:40:04.500 align:start position:0% two earlier 00:40:04.500 --> 00:40:05.930 align:start position:0% two earlier um 00:40:05.930 --> 00:40:05.940 align:start position:0% um 00:40:05.940 --> 00:40:07.790 align:start position:0% um cool 00:40:07.790 --> 00:40:07.800 align:start position:0% cool 00:40:07.800 --> 00:40:09.710 align:start position:0% cool um<00:40:07.920> okay<00:40:08.160> so<00:40:08.460> let's<00:40:08.760> uh<00:40:09.060> finalize<00:40:09.540> that 00:40:09.710 --> 00:40:09.720 align:start position:0% um okay so let's uh finalize that 00:40:09.720 --> 00:40:11.030 align:start position:0% um okay so let's uh finalize that withdrawal 00:40:11.030 --> 00:40:11.040 align:start position:0% withdrawal 00:40:11.040 --> 00:40:14.630 align:start position:0% withdrawal um<00:40:11.160> this<00:40:11.820> part<00:40:12.000> should<00:40:12.240> be<00:40:12.420> fairly<00:40:12.780> simple 00:40:14.630 --> 00:40:14.640 align:start position:0% um this part should be fairly simple 00:40:14.640 --> 00:40:16.130 align:start position:0% um this part should be fairly simple um 00:40:16.130 --> 00:40:16.140 align:start position:0% um 00:40:16.140 --> 00:40:17.690 align:start position:0% um so<00:40:16.560> what<00:40:16.680> does<00:40:16.859> it<00:40:16.980> mean<00:40:17.040> to<00:40:17.160> finalize<00:40:17.579> the 00:40:17.690 --> 00:40:17.700 align:start position:0% so what does it mean to finalize the 00:40:17.700 --> 00:40:18.950 align:start position:0% so what does it mean to finalize the withdrawal<00:40:18.119> this<00:40:18.240> means<00:40:18.480> just<00:40:18.540> release<00:40:18.720> it 00:40:18.950 --> 00:40:18.960 align:start position:0% withdrawal this means just release it 00:40:18.960 --> 00:40:20.329 align:start position:0% withdrawal this means just release it from<00:40:19.079> escrow 00:40:20.329 --> 00:40:20.339 align:start position:0% from escrow 00:40:20.339 --> 00:40:21.890 align:start position:0% from escrow um<00:40:20.460> well<00:40:20.640> okay<00:40:20.940> so<00:40:21.180> the<00:40:21.300> first<00:40:21.420> part<00:40:21.540> will<00:40:21.720> be 00:40:21.890 --> 00:40:21.900 align:start position:0% um well okay so the first part will be 00:40:21.900 --> 00:40:23.690 align:start position:0% um well okay so the first part will be simple 00:40:23.690 --> 00:40:23.700 align:start position:0% simple 00:40:23.700 --> 00:40:25.370 align:start position:0% simple um<00:40:23.760> let's<00:40:24.300> release<00:40:24.540> it<00:40:24.780> from<00:40:24.839> escrow<00:40:25.200> so 00:40:25.370 --> 00:40:25.380 align:start position:0% um let's release it from escrow so 00:40:25.380 --> 00:40:27.410 align:start position:0% um let's release it from escrow so transfer<00:40:25.740> it<00:40:25.859> out<00:40:26.040> to<00:40:26.400> the 00:40:27.410 --> 00:40:27.420 align:start position:0% transfer it out to the 00:40:27.420 --> 00:40:29.990 align:start position:0% transfer it out to the uh<00:40:27.960> the<00:40:28.079> destination<00:40:28.380> address<00:40:28.680> or<00:40:28.980> the<00:40:29.220> uh<00:40:29.760> the 00:40:29.990 --> 00:40:30.000 align:start position:0% uh the destination address or the uh the 00:40:30.000 --> 00:40:31.970 align:start position:0% uh the destination address or the uh the two<00:40:30.119> address<00:40:30.359> I<00:40:30.599> should<00:40:30.780> say 00:40:31.970 --> 00:40:31.980 align:start position:0% two address I should say 00:40:31.980 --> 00:40:35.210 align:start position:0% two address I should say so<00:40:32.579> we<00:40:32.760> connect 00:40:35.210 --> 00:40:35.220 align:start position:0% 00:40:35.220 --> 00:40:35.990 align:start position:0% um 00:40:35.990 --> 00:40:36.000 align:start position:0% um 00:40:36.000 --> 00:40:40.430 align:start position:0% um and<00:40:36.480> we<00:40:36.660> transfer 00:40:40.430 --> 00:40:40.440 align:start position:0% 00:40:40.440 --> 00:40:41.690 align:start position:0% um 00:40:41.690 --> 00:40:41.700 align:start position:0% um 00:40:41.700 --> 00:40:44.930 align:start position:0% um from<00:40:42.060> two<00:40:42.240> token<00:40:42.720> ID<00:40:42.839> so<00:40:43.200> from<00:40:43.619> here 00:40:44.930 --> 00:40:44.940 align:start position:0% from two token ID so from here 00:40:44.940 --> 00:40:48.829 align:start position:0% from two token ID so from here right<00:40:45.420> it<00:40:45.960> should<00:40:46.140> already<00:40:46.320> be<00:40:46.500> escrowed 00:40:48.829 --> 00:40:48.839 align:start position:0% right it should already be escrowed 00:40:48.839 --> 00:40:50.569 align:start position:0% right it should already be escrowed sorry 00:40:50.569 --> 00:40:50.579 align:start position:0% sorry 00:40:50.579 --> 00:40:52.730 align:start position:0% sorry um<00:40:50.760> too<00:40:51.000> much<00:40:51.180> coffee<00:40:51.359> very<00:40:51.720> jittery 00:40:52.730 --> 00:40:52.740 align:start position:0% um too much coffee very jittery 00:40:52.740 --> 00:40:53.810 align:start position:0% um too much coffee very jittery to 00:40:53.810 --> 00:40:53.820 align:start position:0% to 00:40:53.820 --> 00:40:56.870 align:start position:0% to um<00:40:53.880> and<00:40:54.119> token<00:40:54.480> ID<00:40:54.660> so<00:40:55.140> there's<00:40:55.320> the<00:40:55.619> actual 00:40:56.870 --> 00:40:56.880 align:start position:0% um and token ID so there's the actual 00:40:56.880 --> 00:40:57.710 align:start position:0% um and token ID so there's the actual um 00:40:57.710 --> 00:40:57.720 align:start position:0% um 00:40:57.720 --> 00:40:59.030 align:start position:0% um there's<00:40:58.020> the<00:40:58.260> actual<00:40:58.440> method<00:40:58.680> that<00:40:58.800> gets 00:40:59.030 --> 00:40:59.040 align:start position:0% there's the actual method that gets 00:40:59.040 --> 00:41:03.589 align:start position:0% there's the actual method that gets called<00:40:59.300> now<00:41:00.300> uh<00:41:00.780> the<00:41:01.020> last<00:41:01.200> thing<00:41:01.500> to<00:41:01.859> do 00:41:03.589 --> 00:41:03.599 align:start position:0% called now uh the last thing to do 00:41:03.599 --> 00:41:06.170 align:start position:0% called now uh the last thing to do um<00:41:04.140> is 00:41:06.170 --> 00:41:06.180 align:start position:0% um is 00:41:06.180 --> 00:41:10.250 align:start position:0% um is uh<00:41:07.500> uh<00:41:08.099> fix<00:41:08.460> this<00:41:08.700> error 00:41:10.250 --> 00:41:10.260 align:start position:0% uh uh fix this error 00:41:10.260 --> 00:41:12.710 align:start position:0% uh uh fix this error oh<00:41:10.740> I<00:41:10.859> did<00:41:11.040> something<00:41:11.220> stupid 00:41:12.710 --> 00:41:12.720 align:start position:0% oh I did something stupid 00:41:12.720 --> 00:41:18.349 align:start position:0% oh I did something stupid um 00:41:18.349 --> 00:41:18.359 align:start position:0% 00:41:18.359 --> 00:41:20.450 align:start position:0% there<00:41:18.839> okay 00:41:20.450 --> 00:41:20.460 align:start position:0% there okay 00:41:20.460 --> 00:41:21.890 align:start position:0% there okay um<00:41:20.520> the<00:41:20.880> last<00:41:20.940> thing<00:41:21.060> to<00:41:21.240> do<00:41:21.359> is<00:41:21.480> to<00:41:21.599> make<00:41:21.720> sure 00:41:21.890 --> 00:41:21.900 align:start position:0% um the last thing to do is to make sure 00:41:21.900 --> 00:41:23.750 align:start position:0% um the last thing to do is to make sure that<00:41:22.079> this<00:41:22.320> actually<00:41:22.500> only<00:41:22.800> gets<00:41:23.160> executed<00:41:23.579> as 00:41:23.750 --> 00:41:23.760 align:start position:0% that this actually only gets executed as 00:41:23.760 --> 00:41:25.130 align:start position:0% that this actually only gets executed as a<00:41:23.880> cross<00:41:23.940> chain<00:41:24.180> message 00:41:25.130 --> 00:41:25.140 align:start position:0% a cross chain message 00:41:25.140 --> 00:41:26.930 align:start position:0% a cross chain message um<00:41:25.260> so<00:41:25.680> this<00:41:25.800> is<00:41:25.920> on<00:41:26.099> the<00:41:26.220> counterpart<00:41:26.579> L2 00:41:26.930 --> 00:41:26.940 align:start position:0% um so this is on the counterpart L2 00:41:26.940 --> 00:41:29.210 align:start position:0% um so this is on the counterpart L2 Gateway<00:41:27.300> this<00:41:27.660> is<00:41:27.780> a<00:41:28.020> bit<00:41:28.200> more<00:41:28.500> involved<00:41:29.040> at 00:41:29.210 --> 00:41:29.220 align:start position:0% Gateway this is a bit more involved at 00:41:29.220 --> 00:41:30.950 align:start position:0% Gateway this is a bit more involved at least<00:41:29.339> to<00:41:29.520> understand<00:41:29.640> the<00:41:30.060> pieces<00:41:30.359> of<00:41:30.540> it<00:41:30.660> and 00:41:30.950 --> 00:41:30.960 align:start position:0% least to understand the pieces of it and 00:41:30.960 --> 00:41:32.510 align:start position:0% least to understand the pieces of it and I<00:41:31.079> see<00:41:31.260> there's<00:41:31.440> eight<00:41:31.680> minutes<00:41:31.920> left<00:41:32.280> so 00:41:32.510 --> 00:41:32.520 align:start position:0% I see there's eight minutes left so 00:41:32.520 --> 00:41:33.829 align:start position:0% I see there's eight minutes left so maybe<00:41:32.700> I'd<00:41:33.000> rather<00:41:33.180> if<00:41:33.480> there's<00:41:33.540> any<00:41:33.720> other 00:41:33.829 --> 00:41:33.839 align:start position:0% maybe I'd rather if there's any other 00:41:33.839 --> 00:41:35.870 align:start position:0% maybe I'd rather if there's any other questions<00:41:34.140> feel<00:41:34.560> feel<00:41:34.859> free<00:41:35.099> I<00:41:35.520> feel<00:41:35.760> like 00:41:35.870 --> 00:41:35.880 align:start position:0% questions feel feel free I feel like 00:41:35.880 --> 00:41:37.190 align:start position:0% questions feel feel free I feel like maybe<00:41:36.060> that's<00:41:36.300> but 00:41:37.190 --> 00:41:37.200 align:start position:0% maybe that's but 00:41:37.200 --> 00:42:18.890 align:start position:0% maybe that's but if<00:41:37.560> I<00:41:37.740> don't<00:41:37.800> see<00:41:37.920> it<00:41:38.040> just<00:41:38.160> shout<00:41:38.339> yeah 00:42:18.890 --> 00:42:18.900 align:start position:0% 00:42:18.900 --> 00:42:21.290 align:start position:0% yeah<00:42:19.619> the<00:42:20.099> doodle<00:42:20.400> contract<00:42:20.700> itself<00:42:21.000> will<00:42:21.119> do 00:42:21.290 --> 00:42:21.300 align:start position:0% yeah the doodle contract itself will do 00:42:21.300 --> 00:42:22.730 align:start position:0% yeah the doodle contract itself will do the<00:42:21.420> registration<00:42:21.839> and<00:42:22.020> it<00:42:22.140> only<00:42:22.320> has<00:42:22.500> to<00:42:22.560> kind 00:42:22.730 --> 00:42:22.740 align:start position:0% the registration and it only has to kind 00:42:22.740 --> 00:42:24.109 align:start position:0% the registration and it only has to kind of<00:42:22.800> register<00:42:23.040> once<00:42:23.460> is<00:42:23.640> the<00:42:23.820> way<00:42:23.880> to<00:42:24.000> think 00:42:24.109 --> 00:42:24.119 align:start position:0% of register once is the way to think 00:42:24.119 --> 00:42:25.790 align:start position:0% of register once is the way to think about<00:42:24.240> it<00:42:24.420> right<00:42:24.660> so<00:42:25.079> that<00:42:25.260> so<00:42:25.380> once<00:42:25.680> the 00:42:25.790 --> 00:42:25.800 align:start position:0% about it right so that so once the 00:42:25.800 --> 00:42:27.230 align:start position:0% about it right so that so once the contract<00:42:26.220> itself<00:42:26.520> and<00:42:26.820> it's<00:42:26.880> not<00:42:27.000> it's<00:42:27.119> not 00:42:27.230 --> 00:42:27.240 align:start position:0% contract itself and it's not it's not 00:42:27.240 --> 00:42:28.430 align:start position:0% contract itself and it's not it's not necessarily<00:42:27.540> the<00:42:27.599> owner<00:42:27.839> of<00:42:27.960> the<00:42:28.079> contract<00:42:28.260> I 00:42:28.430 --> 00:42:28.440 align:start position:0% necessarily the owner of the contract I 00:42:28.440 --> 00:42:29.510 align:start position:0% necessarily the owner of the contract I don't think<00:42:28.619> of<00:42:28.680> it<00:42:28.800> that<00:42:28.920> way<00:42:29.040> it's<00:42:29.220> just 00:42:29.510 --> 00:42:29.520 align:start position:0% don't think of it that way it's just 00:42:29.520 --> 00:42:31.190 align:start position:0% don't think of it that way it's just however<00:42:30.240> the<00:42:30.420> contract<00:42:30.599> is<00:42:30.780> set<00:42:30.900> up<00:42:31.020> the 00:42:31.190 --> 00:42:31.200 align:start position:0% however the contract is set up the 00:42:31.200 --> 00:42:33.109 align:start position:0% however the contract is set up the contract<00:42:31.440> needs<00:42:31.680> to<00:42:31.740> be<00:42:31.859> able<00:42:32.099> to<00:42:32.220> register<00:42:32.579> so 00:42:33.109 --> 00:42:33.119 align:start position:0% contract needs to be able to register so 00:42:33.119 --> 00:42:35.030 align:start position:0% contract needs to be able to register so in<00:42:33.240> this<00:42:33.359> case<00:42:33.420> it's<00:42:33.660> not<00:42:33.900> the<00:42:34.200> owner<00:42:34.800> um<00:42:34.859> in 00:42:35.030 --> 00:42:35.040 align:start position:0% in this case it's not the owner um in 00:42:35.040 --> 00:42:36.050 align:start position:0% in this case it's not the owner um in fact<00:42:35.160> in<00:42:35.339> this<00:42:35.400> case<00:42:35.520> anyone<00:42:35.820> can<00:42:35.940> call 00:42:36.050 --> 00:42:36.060 align:start position:0% fact in this case anyone can call 00:42:36.060 --> 00:42:38.270 align:start position:0% fact in this case anyone can call register<00:42:36.359> token<00:42:36.720> Dell<00:42:36.960> to<00:42:37.200> which<00:42:37.680> means<00:42:37.980> in 00:42:38.270 --> 00:42:38.280 align:start position:0% register token Dell to which means in 00:42:38.280 --> 00:42:39.410 align:start position:0% register token Dell to which means in this<00:42:38.400> case<00:42:38.520> actually<00:42:38.700> it's<00:42:38.940> probably<00:42:39.119> not<00:42:39.300> the 00:42:39.410 --> 00:42:39.420 align:start position:0% this case actually it's probably not the 00:42:39.420 --> 00:42:40.550 align:start position:0% this case actually it's probably not the best<00:42:39.540> idea<00:42:39.780> you<00:42:40.020> have<00:42:40.200> you<00:42:40.320> should<00:42:40.440> like 00:42:40.550 --> 00:42:40.560 align:start position:0% best idea you have you should like 00:42:40.560 --> 00:42:41.630 align:start position:0% best idea you have you should like deploy<00:42:40.920> this 00:42:41.630 --> 00:42:41.640 align:start position:0% deploy this 00:42:41.640 --> 00:42:43.310 align:start position:0% deploy this contract<00:42:42.240> and<00:42:42.420> register<00:42:42.660> right<00:42:42.839> away<00:42:42.960> to<00:42:43.200> the 00:42:43.310 --> 00:42:43.320 align:start position:0% contract and register right away to the 00:42:43.320 --> 00:42:46.250 align:start position:0% contract and register right away to the right<00:42:43.440> address<00:42:43.940> but<00:42:44.940> as<00:42:45.359> long<00:42:45.540> as<00:42:45.660> some<00:42:46.020> as 00:42:46.250 --> 00:42:46.260 align:start position:0% right address but as long as some as 00:42:46.260 --> 00:42:47.329 align:start position:0% right address but as long as some as long<00:42:46.380> as<00:42:46.500> the<00:42:46.619> function<00:42:46.859> can<00:42:47.040> make<00:42:47.160> the 00:42:47.329 --> 00:42:47.339 align:start position:0% long as the function can make the 00:42:47.339 --> 00:42:49.130 align:start position:0% long as the function can make the external<00:42:47.700> call<00:42:47.820> to<00:42:48.000> register 00:42:49.130 --> 00:42:49.140 align:start position:0% external call to register 00:42:49.140 --> 00:42:51.050 align:start position:0% external call to register they<00:42:49.560> can<00:42:49.680> register<00:42:49.980> and<00:42:50.280> whether<00:42:50.460> that's<00:42:50.820> you 00:42:51.050 --> 00:42:51.060 align:start position:0% they can register and whether that's you 00:42:51.060 --> 00:42:52.069 align:start position:0% they can register and whether that's you know<00:42:51.180> whether<00:42:51.359> that's<00:42:51.540> proper<00:42:51.839> whether 00:42:52.069 --> 00:42:52.079 align:start position:0% know whether that's proper whether 00:42:52.079 --> 00:42:53.329 align:start position:0% know whether that's proper whether that's<00:42:52.200> malicious<00:42:52.619> you<00:42:52.859> should<00:42:52.980> look<00:42:53.099> at<00:42:53.220> the 00:42:53.329 --> 00:42:53.339 align:start position:0% that's malicious you should look at the 00:42:53.339 --> 00:43:00.470 align:start position:0% that's malicious you should look at the L1<00:42:53.579> token<00:42:54.000> contract<00:42:54.300> so<00:42:54.839> that's<00:42:55.020> yeah 00:43:00.470 --> 00:43:00.480 align:start position:0% 00:43:00.480 --> 00:43:02.630 align:start position:0% um<00:43:00.599> probably<00:43:00.780> the<00:43:01.020> doodle<00:43:01.380> team<00:43:01.500> right<00:43:02.220> so 00:43:02.630 --> 00:43:02.640 align:start position:0% um probably the doodle team right so 00:43:02.640 --> 00:43:05.210 align:start position:0% um probably the doodle team right so yeah<00:43:02.760> so<00:43:02.940> who<00:43:03.119> like<00:43:03.420> whoever<00:43:03.660> so<00:43:04.020> somebody 00:43:05.210 --> 00:43:05.220 align:start position:0% yeah so who like whoever so somebody 00:43:05.220 --> 00:43:07.370 align:start position:0% yeah so who like whoever so somebody basically<00:43:05.760> like<00:43:06.060> whoever<00:43:06.720> sets<00:43:07.079> this<00:43:07.200> up 00:43:07.370 --> 00:43:07.380 align:start position:0% basically like whoever sets this up 00:43:07.380 --> 00:43:08.870 align:start position:0% basically like whoever sets this up right<00:43:07.800> like<00:43:07.980> we're<00:43:08.220> probably<00:43:08.400> the<00:43:08.640> same<00:43:08.760> party 00:43:08.870 --> 00:43:08.880 align:start position:0% right like we're probably the same party 00:43:08.880 --> 00:43:10.670 align:start position:0% right like we're probably the same party that<00:43:09.060> deployed<00:43:09.359> the<00:43:09.420> L1<00:43:09.720> side 00:43:10.670 --> 00:43:10.680 align:start position:0% that deployed the L1 side 00:43:10.680 --> 00:43:12.710 align:start position:0% that deployed the L1 side um<00:43:10.800> we'll<00:43:10.980> sort<00:43:11.220> of<00:43:11.280> plan<00:43:11.400> this 00:43:12.710 --> 00:43:12.720 align:start position:0% um we'll sort of plan this 00:43:12.720 --> 00:43:14.270 align:start position:0% um we'll sort of plan this um so<00:43:12.839> they<00:43:12.960> had<00:43:13.020> to<00:43:13.140> play<00:43:13.260> both<00:43:13.500> and<00:43:13.980> you<00:43:14.160> know 00:43:14.270 --> 00:43:14.280 align:start position:0% um so they had to play both and you know 00:43:14.280 --> 00:43:15.230 align:start position:0% um so they had to play both and you know the<00:43:14.400> reason<00:43:14.520> you<00:43:14.640> want<00:43:14.760> you<00:43:14.880> wanted<00:43:15.000> to<00:43:15.119> play 00:43:15.230 --> 00:43:15.240 align:start position:0% the reason you want you wanted to play 00:43:15.240 --> 00:43:16.309 align:start position:0% the reason you want you wanted to play both<00:43:15.420> is<00:43:15.540> so<00:43:15.660> you<00:43:15.780> just<00:43:15.900> know<00:43:15.960> which<00:43:16.140> address 00:43:16.309 --> 00:43:16.319 align:start position:0% both is so you just know which address 00:43:16.319 --> 00:43:18.710 align:start position:0% both is so you just know which address to<00:43:16.680> set<00:43:16.859> okay<00:43:17.579> but<00:43:18.000> the<00:43:18.180> other<00:43:18.300> one<00:43:18.480> but<00:43:18.599> the 00:43:18.710 --> 00:43:18.720 align:start position:0% to set okay but the other one but the 00:43:18.720 --> 00:43:20.089 align:start position:0% to set okay but the other one but the other<00:43:18.780> one<00:43:18.960> contract<00:43:19.260> ultimately<00:43:19.680> has<00:43:19.859> has 00:43:20.089 --> 00:43:20.099 align:start position:0% other one contract ultimately has has 00:43:20.099 --> 00:43:22.490 align:start position:0% other one contract ultimately has has control 00:43:22.490 --> 00:43:22.500 align:start position:0% 00:43:22.500 --> 00:43:24.470 align:start position:0% we<00:43:23.040> said 00:43:24.470 --> 00:43:24.480 align:start position:0% we said 00:43:24.480 --> 00:43:31.130 align:start position:0% we said yeah 00:43:31.130 --> 00:43:31.140 align:start position:0% 00:43:31.140 --> 00:43:34.069 align:start position:0% no<00:43:31.859> so<00:43:32.040> good<00:43:32.460> question<00:43:32.760> in<00:43:33.359> the<00:43:33.480> happy<00:43:33.599> case<00:43:33.900> in 00:43:34.069 --> 00:43:34.079 align:start position:0% no so good question in the happy case in 00:43:34.079 --> 00:43:35.390 align:start position:0% no so good question in the happy case in the<00:43:34.260> common<00:43:34.319> case<00:43:34.560> no<00:43:34.740> the<00:43:34.980> question<00:43:35.040> was<00:43:35.220> when 00:43:35.390 --> 00:43:35.400 align:start position:0% the common case no the question was when 00:43:35.400 --> 00:43:37.609 align:start position:0% the common case no the question was when we<00:43:35.579> when<00:43:35.880> we<00:43:36.060> deposit<00:43:36.480> yeah 00:43:37.609 --> 00:43:37.619 align:start position:0% we when we deposit yeah 00:43:37.619 --> 00:43:38.750 align:start position:0% we when we deposit yeah um<00:43:37.740> does<00:43:37.859> anyone<00:43:38.099> need<00:43:38.280> to<00:43:38.339> call<00:43:38.460> a<00:43:38.579> function 00:43:38.750 --> 00:43:38.760 align:start position:0% um does anyone need to call a function 00:43:38.760 --> 00:43:40.790 align:start position:0% um does anyone need to call a function on<00:43:38.940> L2<00:43:39.300> so<00:43:39.720> the<00:43:39.839> way<00:43:39.960> these<00:43:40.200> retryable<00:43:40.619> tickets 00:43:40.790 --> 00:43:40.800 align:start position:0% on L2 so the way these retryable tickets 00:43:40.800 --> 00:43:41.930 align:start position:0% on L2 so the way these retryable tickets work<00:43:41.040> is<00:43:41.160> already<00:43:41.339> Richmond<00:43:41.520> cross<00:43:41.760> chain 00:43:41.930 --> 00:43:41.940 align:start position:0% work is already Richmond cross chain 00:43:41.940 --> 00:43:43.849 align:start position:0% work is already Richmond cross chain messages<00:43:42.180> is<00:43:42.480> it<00:43:42.900> should<00:43:43.140> it'll<00:43:43.500> execute 00:43:43.849 --> 00:43:43.859 align:start position:0% messages is it should it'll execute 00:43:43.859 --> 00:43:45.230 align:start position:0% messages is it should it'll execute automatically<00:43:44.339> it'll<00:43:44.640> try<00:43:44.819> to<00:43:44.940> execute 00:43:45.230 --> 00:43:45.240 align:start position:0% automatically it'll try to execute 00:43:45.240 --> 00:43:47.569 align:start position:0% automatically it'll try to execute automatically<00:43:45.780> so<00:43:46.380> we<00:43:46.619> Supply<00:43:46.800> the<00:43:47.099> gas<00:43:47.280> for 00:43:47.569 --> 00:43:47.579 align:start position:0% automatically so we Supply the gas for 00:43:47.579 --> 00:43:49.849 align:start position:0% automatically so we Supply the gas for the<00:43:47.700> L2<00:43:48.000> side<00:43:48.240> to<00:43:48.420> execute 00:43:49.849 --> 00:43:49.859 align:start position:0% the L2 side to execute 00:43:49.859 --> 00:43:51.890 align:start position:0% the L2 side to execute um<00:43:49.980> and<00:43:50.339> assuming<00:43:50.819> that<00:43:50.940> doesn't<00:43:51.060> revert<00:43:51.599> the 00:43:51.890 --> 00:43:51.900 align:start position:0% um and assuming that doesn't revert the 00:43:51.900 --> 00:43:53.390 align:start position:0% um and assuming that doesn't revert the user<00:43:52.140> doesn't<00:43:52.260> have<00:43:52.440> to<00:43:52.560> do<00:43:52.619> anything<00:43:52.800> else<00:43:53.099> so 00:43:53.390 --> 00:43:53.400 align:start position:0% user doesn't have to do anything else so 00:43:53.400 --> 00:43:55.490 align:start position:0% user doesn't have to do anything else so from<00:43:53.640> a<00:43:53.819> user<00:43:54.060> perspective<00:43:54.420> they<00:43:55.140> publish<00:43:55.380> an 00:43:55.490 --> 00:43:55.500 align:start position:0% from a user perspective they publish an 00:43:55.500 --> 00:43:58.250 align:start position:0% from a user perspective they publish an L1<00:43:55.800> transaction<00:43:56.220> they<00:43:56.700> wait<00:43:56.880> a<00:43:57.060> few<00:43:57.180> minutes 00:43:58.250 --> 00:43:58.260 align:start position:0% L1 transaction they wait a few minutes 00:43:58.260 --> 00:44:00.770 align:start position:0% L1 transaction they wait a few minutes and<00:43:58.800> then<00:43:58.980> it<00:43:59.280> just<00:43:59.400> it'll<00:43:59.940> get<00:44:00.000> minted<00:44:00.359> on<00:44:00.480> L2 00:44:00.770 --> 00:44:00.780 align:start position:0% and then it just it'll get minted on L2 00:44:00.780 --> 00:44:02.569 align:start position:0% and then it just it'll get minted on L2 now<00:44:01.260> we<00:44:01.500> can't<00:44:01.619> guarantee<00:44:02.040> the<00:44:02.220> execution 00:44:02.569 --> 00:44:02.579 align:start position:0% now we can't guarantee the execution 00:44:02.579 --> 00:44:04.309 align:start position:0% now we can't guarantee the execution will<00:44:02.819> succeed<00:44:03.060> at<00:44:03.240> L2<00:44:03.540> like<00:44:03.780> maybe<00:44:03.900> there's<00:44:04.140> a 00:44:04.309 --> 00:44:04.319 align:start position:0% will succeed at L2 like maybe there's a 00:44:04.319 --> 00:44:06.230 align:start position:0% will succeed at L2 like maybe there's a gas<00:44:04.440> spike<00:44:04.920> in<00:44:05.520> the<00:44:05.640> time<00:44:05.700> between<00:44:05.880> when<00:44:06.119> you 00:44:06.230 --> 00:44:06.240 align:start position:0% gas spike in the time between when you 00:44:06.240 --> 00:44:07.849 align:start position:0% gas spike in the time between when you deposited<00:44:06.720> and<00:44:06.900> when<00:44:07.079> there<00:44:07.440> were<00:44:07.560> tribal 00:44:07.849 --> 00:44:07.859 align:start position:0% deposited and when there were tribal 00:44:07.859 --> 00:44:10.309 align:start position:0% deposited and when there were tribal tickets<00:44:07.980> created<00:44:08.400> at<00:44:08.520> L2<00:44:08.940> if<00:44:09.720> it<00:44:09.839> fails<00:44:10.200> then 00:44:10.309 --> 00:44:10.319 align:start position:0% tickets created at L2 if it fails then 00:44:10.319 --> 00:44:11.630 align:start position:0% tickets created at L2 if it fails then someone's<00:44:10.680> gonna<00:44:10.859> have<00:44:11.040> to<00:44:11.099> kind<00:44:11.220> of<00:44:11.339> poke<00:44:11.460> it 00:44:11.630 --> 00:44:11.640 align:start position:0% someone's gonna have to kind of poke it 00:44:11.640 --> 00:44:13.490 align:start position:0% someone's gonna have to kind of poke it again<00:44:11.760> to<00:44:12.060> re<00:44:12.180> to<00:44:12.480> re<00:44:12.599> to<00:44:12.900> retry<00:44:13.200> it<00:44:13.319> to 00:44:13.490 --> 00:44:13.500 align:start position:0% again to re to re to retry it to 00:44:13.500 --> 00:44:15.170 align:start position:0% again to re to re to retry it to re-execute<00:44:13.980> it<00:44:14.099> be<00:44:14.400> able<00:44:14.579> to<00:44:14.700> wake<00:44:14.760> to<00:44:15.000> do<00:44:15.060> that 00:44:15.170 --> 00:44:15.180 align:start position:0% re-execute it be able to wake to do that 00:44:15.180 --> 00:44:16.910 align:start position:0% re-execute it be able to wake to do that but<00:44:15.420> normally<00:44:15.839> yeah<00:44:16.079> in<00:44:16.319> the<00:44:16.440> happy<00:44:16.500> case<00:44:16.740> that 00:44:16.910 --> 00:44:16.920 align:start position:0% but normally yeah in the happy case that 00:44:16.920 --> 00:44:21.109 align:start position:0% but normally yeah in the happy case that shouldn't<00:44:17.220> happen 00:44:21.109 --> 00:44:21.119 align:start position:0% 00:44:21.119 --> 00:44:22.910 align:start position:0% correct 00:44:22.910 --> 00:44:22.920 align:start position:0% correct 00:44:22.920 --> 00:44:25.790 align:start position:0% correct correct<00:44:23.460> we<00:44:23.640> Supply<00:44:23.819> it<00:44:24.180> Supply<00:44:24.780> it<00:44:25.079> here<00:44:25.260> so 00:44:25.790 --> 00:44:25.800 align:start position:0% correct we Supply it Supply it here so 00:44:25.800 --> 00:44:26.870 align:start position:0% correct we Supply it Supply it here so actually<00:44:25.980> so<00:44:26.280> when<00:44:26.400> we<00:44:26.520> do<00:44:26.640> this<00:44:26.700> create 00:44:26.870 --> 00:44:26.880 align:start position:0% actually so when we do this create 00:44:26.880 --> 00:44:28.190 align:start position:0% actually so when we do this create retrievable<00:44:27.359> what<00:44:27.540> this<00:44:27.720> is<00:44:27.780> doing<00:44:27.900> create 00:44:28.190 --> 00:44:28.200 align:start position:0% retrievable what this is doing create 00:44:28.200 --> 00:44:29.870 align:start position:0% retrievable what this is doing create retrievable<00:44:28.619> ticket<00:44:28.800> behind<00:44:29.220> the<00:44:29.280> scenes<00:44:29.579> is 00:44:29.870 --> 00:44:29.880 align:start position:0% retrievable ticket behind the scenes is 00:44:29.880 --> 00:44:31.010 align:start position:0% retrievable ticket behind the scenes is this<00:44:30.060> actually<00:44:30.300> depositing<00:44:30.900> this 00:44:31.010 --> 00:44:31.020 align:start position:0% this actually depositing this 00:44:31.020 --> 00:44:33.770 align:start position:0% this actually depositing this message.value<00:44:31.740> ether<00:44:32.040> okay 00:44:33.770 --> 00:44:33.780 align:start position:0% message.value ether okay 00:44:33.780 --> 00:44:35.150 align:start position:0% message.value ether okay so<00:44:34.200> this<00:44:34.440> is<00:44:34.560> so<00:44:34.680> that's<00:44:34.920> that's<00:44:35.099> that's 00:44:35.150 --> 00:44:35.160 align:start position:0% so this is so that's that's that's 00:44:35.160 --> 00:44:37.069 align:start position:0% so this is so that's that's that's happening<00:44:35.700> behind<00:44:35.940> the<00:44:36.060> scenes<00:44:36.300> so<00:44:36.540> this<00:44:36.720> so 00:44:37.069 --> 00:44:37.079 align:start position:0% happening behind the scenes so this so 00:44:37.079 --> 00:44:39.770 align:start position:0% happening behind the scenes so this so this<00:44:37.319> this<00:44:37.560> value<00:44:37.800> that<00:44:38.099> we<00:44:38.220> send 00:44:39.770 --> 00:44:39.780 align:start position:0% this this value that we send 00:44:39.780 --> 00:44:41.750 align:start position:0% this this value that we send is<00:44:40.140> actually<00:44:40.319> getting<00:44:40.500> deposited<00:44:41.040> to<00:44:41.160> L2<00:44:41.520> and 00:44:41.750 --> 00:44:41.760 align:start position:0% is actually getting deposited to L2 and 00:44:41.760 --> 00:44:43.370 align:start position:0% is actually getting deposited to L2 and that<00:44:41.940> has<00:44:42.060> to<00:44:42.180> cover<00:44:42.359> all<00:44:42.660> of<00:44:42.780> this<00:44:42.960> gas<00:44:43.140> cost 00:44:43.370 --> 00:44:43.380 align:start position:0% that has to cover all of this gas cost 00:44:43.380 --> 00:44:44.569 align:start position:0% that has to cover all of this gas cost that<00:44:43.619> we're<00:44:43.680> supplying<00:44:44.040> so<00:44:44.160> that<00:44:44.339> has<00:44:44.460> to 00:44:44.569 --> 00:44:44.579 align:start position:0% that we're supplying so that has to 00:44:44.579 --> 00:44:45.410 align:start position:0% that we're supplying so that has to cover 00:44:45.410 --> 00:44:45.420 align:start position:0% cover 00:44:45.420 --> 00:44:48.050 align:start position:0% cover you<00:44:45.900> know<00:44:46.020> uh<00:44:46.500> uh<00:44:46.920> you<00:44:47.040> know<00:44:47.160> gas<00:44:47.400> price<00:44:47.640> times 00:44:48.050 --> 00:44:48.060 align:start position:0% you know uh uh you know gas price times 00:44:48.060 --> 00:44:50.809 align:start position:0% you know uh uh you know gas price times gas<00:44:48.420> limit<00:44:48.599> plus<00:44:48.960> Max<00:44:49.200> emission<00:44:49.680> Cost<00:44:49.859> Plus 00:44:50.809 --> 00:44:50.819 align:start position:0% gas limit plus Max emission Cost Plus 00:44:50.819 --> 00:44:57.170 align:start position:0% gas limit plus Max emission Cost Plus call<00:44:51.060> Value 00:44:57.170 --> 00:44:57.180 align:start position:0% 00:44:57.180 --> 00:44:59.270 align:start position:0% yes 00:44:59.270 --> 00:44:59.280 align:start position:0% yes 00:44:59.280 --> 00:45:01.730 align:start position:0% yes correct<00:44:59.819> the<00:45:00.000> L1<00:45:00.359> yes<00:45:00.660> the<00:45:00.900> L1<00:45:01.140> call<00:45:01.319> supplies 00:45:01.730 --> 00:45:01.740 align:start position:0% correct the L1 yes the L1 call supplies 00:45:01.740 --> 00:45:04.130 align:start position:0% correct the L1 yes the L1 call supplies the<00:45:01.920> gas<00:45:02.099> for<00:45:02.520> L2<00:45:02.940> now<00:45:03.180> by<00:45:03.480> the<00:45:03.599> way<00:45:03.660> as<00:45:03.839> like<00:45:04.020> a 00:45:04.130 --> 00:45:04.140 align:start position:0% the gas for L2 now by the way as like a 00:45:04.140 --> 00:45:06.230 align:start position:0% the gas for L2 now by the way as like a side<00:45:04.380> note<00:45:04.500> if<00:45:04.740> you<00:45:05.040> already<00:45:05.099> do<00:45:05.339> have<00:45:05.460> gas<00:45:05.760> at 00:45:06.230 --> 00:45:06.240 align:start position:0% side note if you already do have gas at 00:45:06.240 --> 00:45:08.329 align:start position:0% side note if you already do have gas at your<00:45:06.359> L2<00:45:06.720> address<00:45:06.960> there's<00:45:07.680> ways<00:45:07.980> you<00:45:08.099> can<00:45:08.220> you 00:45:08.329 --> 00:45:08.339 align:start position:0% your L2 address there's ways you can you 00:45:08.339 --> 00:45:09.710 align:start position:0% your L2 address there's ways you can you can<00:45:08.460> use<00:45:08.579> that<00:45:08.700> but<00:45:08.880> this<00:45:09.060> is<00:45:09.180> this<00:45:09.540> is<00:45:09.599> the 00:45:09.710 --> 00:45:09.720 align:start position:0% can use that but this is this is the 00:45:09.720 --> 00:45:10.609 align:start position:0% can use that but this is this is the path<00:45:09.839> that<00:45:09.960> we<00:45:10.079> encourage<00:45:10.260> for<00:45:10.500> doing 00:45:10.609 --> 00:45:10.619 align:start position:0% path that we encourage for doing 00:45:10.619 --> 00:45:12.230 align:start position:0% path that we encourage for doing cross-chain<00:45:11.040> messages<00:45:11.220> is<00:45:11.520> just<00:45:11.700> Supply<00:45:12.000> the 00:45:12.230 --> 00:45:12.240 align:start position:0% cross-chain messages is just Supply the 00:45:12.240 --> 00:45:15.589 align:start position:0% cross-chain messages is just Supply the user<00:45:12.540> directly<00:45:12.839> for<00:45:13.319> various<00:45:13.980> reasons<00:45:14.460> yeah 00:45:15.589 --> 00:45:15.599 align:start position:0% user directly for various reasons yeah 00:45:15.599 --> 00:45:17.390 align:start position:0% user directly for various reasons yeah um 00:45:17.390 --> 00:45:17.400 align:start position:0% um 00:45:17.400 --> 00:45:18.950 align:start position:0% um um yeah<00:45:17.700> cool<00:45:17.940> then<00:45:18.180> you<00:45:18.300> can<00:45:18.420> if<00:45:18.599> you<00:45:18.720> look<00:45:18.839> at 00:45:18.950 --> 00:45:18.960 align:start position:0% um yeah cool then you can if you look at 00:45:18.960 --> 00:45:20.569 align:start position:0% um yeah cool then you can if you look at our<00:45:19.020> docs<00:45:19.319> you<00:45:19.440> know<00:45:19.500> I<00:45:19.619> I<00:45:19.680> brushed<00:45:20.280> over<00:45:20.339> some 00:45:20.569 --> 00:45:20.579 align:start position:0% our docs you know I I brushed over some 00:45:20.579 --> 00:45:21.650 align:start position:0% our docs you know I I brushed over some of<00:45:20.700> the<00:45:20.760> details<00:45:21.000> of<00:45:21.119> retrieable<00:45:21.480> tickets 00:45:21.650 --> 00:45:21.660 align:start position:0% of the details of retrieable tickets 00:45:21.660 --> 00:45:22.790 align:start position:0% of the details of retrieable tickets because 00:45:22.790 --> 00:45:22.800 align:start position:0% because 00:45:22.800 --> 00:45:24.349 align:start position:0% because um yeah<00:45:22.980> there's<00:45:23.220> a<00:45:23.400> lot<00:45:23.520> going<00:45:23.640> on<00:45:23.760> there<00:45:23.940> but 00:45:24.349 --> 00:45:24.359 align:start position:0% um yeah there's a lot going on there but 00:45:24.359 --> 00:45:26.569 align:start position:0% um yeah there's a lot going on there but that's<00:45:24.660> that<00:45:24.900> hopefully<00:45:25.260> gives<00:45:25.440> you<00:45:25.560> the<00:45:25.680> gist 00:45:26.569 --> 00:45:26.579 align:start position:0% that's that hopefully gives you the gist 00:45:26.579 --> 00:45:29.030 align:start position:0% that's that hopefully gives you the gist um<00:45:26.640> any<00:45:26.880> other<00:45:27.060> questions 00:45:29.030 --> 00:45:29.040 align:start position:0% um any other questions 00:45:29.040 --> 00:45:30.829 align:start position:0% um any other questions I'll<00:45:29.520> just<00:45:29.640> start<00:45:29.880> writing<00:45:30.300> out<00:45:30.359> how<00:45:30.540> we<00:45:30.660> do 00:45:30.829 --> 00:45:30.839 align:start position:0% I'll just start writing out how we do 00:45:30.839 --> 00:45:33.829 align:start position:0% I'll just start writing out how we do this<00:45:30.960> in<00:45:31.200> the<00:45:31.380> meantime 00:45:33.829 --> 00:45:33.839 align:start position:0% 00:45:33.839 --> 00:45:35.390 align:start position:0% okay<00:45:34.200> might<00:45:34.740> as<00:45:34.920> well<00:45:34.980> just<00:45:35.099> finish<00:45:35.220> this 00:45:35.390 --> 00:45:35.400 align:start position:0% okay might as well just finish this 00:45:35.400 --> 00:45:37.609 align:start position:0% okay might as well just finish this because<00:45:35.579> it's 00:45:37.609 --> 00:45:37.619 align:start position:0% because it's 00:45:37.619 --> 00:45:38.930 align:start position:0% because it's um<00:45:37.740> so<00:45:37.920> here's<00:45:38.280> how<00:45:38.400> we're<00:45:38.640> actually 00:45:38.930 --> 00:45:38.940 align:start position:0% um so here's how we're actually 00:45:38.940 --> 00:45:41.030 align:start position:0% um so here's how we're actually guaranteeing<00:45:39.720> that 00:45:41.030 --> 00:45:41.040 align:start position:0% guaranteeing that 00:45:41.040 --> 00:45:43.490 align:start position:0% guaranteeing that the<00:45:41.760> finalization<00:45:42.359> of<00:45:42.720> the<00:45:42.839> withdrawal<00:45:43.260> is 00:45:43.490 --> 00:45:43.500 align:start position:0% the finalization of the withdrawal is 00:45:43.500 --> 00:45:45.349 align:start position:0% the finalization of the withdrawal is really<00:45:43.619> a<00:45:43.859> cross-chain<00:45:44.220> message<00:45:44.460> and<00:45:45.119> here 00:45:45.349 --> 00:45:45.359 align:start position:0% really a cross-chain message and here 00:45:45.359 --> 00:45:46.910 align:start position:0% really a cross-chain message and here this<00:45:45.599> gets<00:45:45.839> a<00:45:45.900> bit<00:45:45.960> into<00:45:46.079> the<00:45:46.260> weeds<00:45:46.500> of<00:45:46.680> how 00:45:46.910 --> 00:45:46.920 align:start position:0% this gets a bit into the weeds of how 00:45:46.920 --> 00:45:48.170 align:start position:0% this gets a bit into the weeds of how the<00:45:47.099> sort<00:45:47.339> of<00:45:47.400> cross<00:45:47.520> chain<00:45:47.760> messaging 00:45:48.170 --> 00:45:48.180 align:start position:0% the sort of cross chain messaging 00:45:48.180 --> 00:45:50.329 align:start position:0% the sort of cross chain messaging contracts<00:45:48.660> work<00:45:48.780> in<00:45:49.020> arbitrum<00:45:49.560> but<00:45:50.099> basically 00:45:50.329 --> 00:45:50.339 align:start position:0% contracts work in arbitrum but basically 00:45:50.339 --> 00:45:52.309 align:start position:0% contracts work in arbitrum but basically cross<00:45:50.579> chain<00:45:50.819> messages<00:45:51.060> all<00:45:51.480> come<00:45:51.839> from<00:45:52.020> this 00:45:52.309 --> 00:45:52.319 align:start position:0% cross chain messages all come from this 00:45:52.319 --> 00:45:53.870 align:start position:0% cross chain messages all come from this bridge<00:45:52.500> contract<00:45:52.980> which<00:45:53.400> is<00:45:53.460> a<00:45:53.640> protocol 00:45:53.870 --> 00:45:53.880 align:start position:0% bridge contract which is a protocol 00:45:53.880 --> 00:45:55.970 align:start position:0% bridge contract which is a protocol contract 00:45:55.970 --> 00:45:55.980 align:start position:0% contract 00:45:55.980 --> 00:45:57.349 align:start position:0% contract um<00:45:56.040> I'd<00:45:56.460> like<00:45:56.579> to<00:45:56.700> show<00:45:56.819> it<00:45:56.940> to<00:45:57.000> you<00:45:57.119> if<00:45:57.240> there's 00:45:57.349 --> 00:45:57.359 align:start position:0% um I'd like to show it to you if there's 00:45:57.359 --> 00:45:58.970 align:start position:0% um I'd like to show it to you if there's time 00:45:58.970 --> 00:45:58.980 align:start position:0% time 00:45:58.980 --> 00:46:00.349 align:start position:0% time um<00:45:59.040> maybe<00:45:59.700> I'll<00:45:59.880> just<00:46:00.000> show<00:46:00.119> you<00:46:00.180> the<00:46:00.300> first 00:46:00.349 --> 00:46:00.359 align:start position:0% um maybe I'll just show you the first 00:46:00.359 --> 00:46:01.790 align:start position:0% um maybe I'll just show you the first part 00:46:01.790 --> 00:46:01.800 align:start position:0% part 00:46:01.800 --> 00:46:03.410 align:start position:0% part um<00:46:01.980> that's<00:46:02.280> that's<00:46:02.579> the<00:46:02.760> ultimate<00:46:03.060> caller<00:46:03.300> let 00:46:03.410 --> 00:46:03.420 align:start position:0% um that's that's the ultimate caller let 00:46:03.420 --> 00:46:05.089 align:start position:0% um that's that's the ultimate caller let me<00:46:03.480> show<00:46:03.599> you<00:46:03.720> the<00:46:03.780> flow<00:46:03.960> why<00:46:04.200> not 00:46:05.089 --> 00:46:05.099 align:start position:0% me show you the flow why not 00:46:05.099 --> 00:46:07.670 align:start position:0% me show you the flow why not so<00:46:05.520> crosstain<00:46:06.000> messages<00:46:06.180> just<00:46:06.480> real<00:46:06.660> quick 00:46:07.670 --> 00:46:07.680 align:start position:0% so crosstain messages just real quick 00:46:07.680 --> 00:46:09.410 align:start position:0% so crosstain messages just real quick um 00:46:09.410 --> 00:46:09.420 align:start position:0% um 00:46:09.420 --> 00:46:11.569 align:start position:0% um if<00:46:09.780> we<00:46:09.900> look<00:46:10.079> at<00:46:10.260> how<00:46:10.500> they're<00:46:10.619> executed<00:46:11.220> so 00:46:11.569 --> 00:46:11.579 align:start position:0% if we look at how they're executed so 00:46:11.579 --> 00:46:13.970 align:start position:0% if we look at how they're executed so they're<00:46:11.940> initiated<00:46:12.359> on<00:46:12.540> L2<00:46:12.900> as<00:46:13.079> we<00:46:13.260> saw<00:46:13.440> in<00:46:13.859> the 00:46:13.970 --> 00:46:13.980 align:start position:0% they're initiated on L2 as we saw in the 00:46:13.980 --> 00:46:15.109 align:start position:0% they're initiated on L2 as we saw in the case<00:46:14.099> of<00:46:14.280> you<00:46:14.579> know<00:46:14.700> you're<00:46:14.760> gonna<00:46:14.880> have<00:46:15.060> to 00:46:15.109 --> 00:46:15.119 align:start position:0% case of you know you're gonna have to 00:46:15.119 --> 00:46:16.550 align:start position:0% case of you know you're gonna have to wait<00:46:15.240> for<00:46:15.480> the<00:46:15.660> dispute<00:46:16.020> period<00:46:16.260> because<00:46:16.440> it's 00:46:16.550 --> 00:46:16.560 align:start position:0% wait for the dispute period because it's 00:46:16.560 --> 00:46:19.010 align:start position:0% wait for the dispute period because it's an<00:46:16.619> optimistic<00:46:17.040> grow<00:46:17.220> up 00:46:19.010 --> 00:46:19.020 align:start position:0% an optimistic grow up 00:46:19.020 --> 00:46:20.750 align:start position:0% an optimistic grow up um<00:46:19.200> and<00:46:19.380> then<00:46:19.500> anyone<00:46:19.859> can<00:46:20.040> call<00:46:20.160> this<00:46:20.339> execute 00:46:20.750 --> 00:46:20.760 align:start position:0% um and then anyone can call this execute 00:46:20.760 --> 00:46:22.190 align:start position:0% um and then anyone can call this execute transaction<00:46:21.119> thing<00:46:21.420> so<00:46:21.540> in<00:46:21.660> this<00:46:21.780> case<00:46:21.900> if 00:46:22.190 --> 00:46:22.200 align:start position:0% transaction thing so in this case if 00:46:22.200 --> 00:46:23.329 align:start position:0% transaction thing so in this case if that's<00:46:22.380> not<00:46:22.560> automatic<00:46:22.980> the<00:46:23.099> way<00:46:23.220> where 00:46:23.329 --> 00:46:23.339 align:start position:0% that's not automatic the way where 00:46:23.339 --> 00:46:24.710 align:start position:0% that's not automatic the way where tribal<00:46:23.640> tickets<00:46:23.760> are<00:46:24.000> there<00:46:24.240> actually<00:46:24.420> is<00:46:24.599> the 00:46:24.710 --> 00:46:24.720 align:start position:0% tribal tickets are there actually is the 00:46:24.720 --> 00:46:26.930 align:start position:0% tribal tickets are there actually is the second<00:46:24.839> L1<00:46:25.260> step 00:46:26.930 --> 00:46:26.940 align:start position:0% second L1 step 00:46:26.940 --> 00:46:29.089 align:start position:0% second L1 step um the<00:46:27.420> thing<00:46:27.540> I<00:46:27.660> want<00:46:27.839> to<00:46:27.960> show<00:46:28.140> you<00:46:28.380> in<00:46:28.920> this 00:46:29.089 --> 00:46:29.099 align:start position:0% um the thing I want to show you in this 00:46:29.099 --> 00:46:31.010 align:start position:0% um the thing I want to show you in this execution 00:46:31.010 --> 00:46:31.020 align:start position:0% execution 00:46:31.020 --> 00:46:32.690 align:start position:0% execution here 00:46:32.690 --> 00:46:32.700 align:start position:0% here 00:46:32.700 --> 00:46:35.329 align:start position:0% here here<00:46:32.819> what<00:46:33.180> we<00:46:33.300> do<00:46:33.540> is 00:46:35.329 --> 00:46:35.339 align:start position:0% here what we do is 00:46:35.339 --> 00:46:37.430 align:start position:0% here what we do is we<00:46:36.540> um 00:46:37.430 --> 00:46:37.440 align:start position:0% we um 00:46:37.440 --> 00:46:39.170 align:start position:0% we um as<00:46:37.920> we're<00:46:38.040> executing<00:46:38.579> this<00:46:38.819> cross<00:46:39.000> chain 00:46:39.170 --> 00:46:39.180 align:start position:0% as we're executing this cross chain 00:46:39.180 --> 00:46:41.809 align:start position:0% as we're executing this cross chain message<00:46:39.420> we<00:46:39.720> save<00:46:39.900> this<00:46:40.200> context<00:46:40.619> thing<00:46:41.040> so<00:46:41.640> we 00:46:41.809 --> 00:46:41.819 align:start position:0% message we save this context thing so we 00:46:41.819 --> 00:46:44.089 align:start position:0% message we save this context thing so we can<00:46:41.940> expose<00:46:42.300> all<00:46:42.540> sorts<00:46:42.839> of<00:46:42.900> data<00:46:43.200> about<00:46:43.500> this 00:46:44.089 --> 00:46:44.099 align:start position:0% can expose all sorts of data about this 00:46:44.099 --> 00:46:45.530 align:start position:0% can expose all sorts of data about this what's<00:46:44.579> happening<00:46:44.880> you<00:46:45.119> know<00:46:45.180> what<00:46:45.359> happened 00:46:45.530 --> 00:46:45.540 align:start position:0% what's happening you know what happened 00:46:45.540 --> 00:46:48.650 align:start position:0% what's happening you know what happened from<00:46:45.720> L2<00:46:46.400> notably<00:46:47.400> this<00:46:47.700> sender<00:46:48.180> data<00:46:48.420> is<00:46:48.540> what 00:46:48.650 --> 00:46:48.660 align:start position:0% from L2 notably this sender data is what 00:46:48.660 --> 00:46:50.450 align:start position:0% from L2 notably this sender data is what we're<00:46:48.780> going<00:46:48.900> to<00:46:49.020> need<00:46:49.140> so<00:46:49.619> we<00:46:49.800> expose<00:46:50.099> that<00:46:50.280> in 00:46:50.450 --> 00:46:50.460 align:start position:0% we're going to need so we expose that in 00:46:50.460 --> 00:46:52.790 align:start position:0% we're going to need so we expose that in something<00:46:50.640> like<00:46:50.819> element<00:46:50.940> L2<00:46:51.480> sender 00:46:52.790 --> 00:46:52.800 align:start position:0% something like element L2 sender 00:46:52.800 --> 00:46:54.650 align:start position:0% something like element L2 sender but<00:46:52.920> during<00:46:53.160> execution<00:46:53.760> it's<00:46:54.300> a<00:46:54.480> little<00:46:54.540> hard 00:46:54.650 --> 00:46:54.660 align:start position:0% but during execution it's a little hard 00:46:54.660 --> 00:46:56.510 align:start position:0% but during execution it's a little hard to<00:46:54.839> show<00:46:54.900> I<00:46:55.079> guess<00:46:55.140> but<00:46:55.319> during<00:46:55.440> execution<00:46:56.040> the 00:46:56.510 --> 00:46:56.520 align:start position:0% to show I guess but during execution the 00:46:56.520 --> 00:46:57.770 align:start position:0% to show I guess but during execution the point<00:46:56.700> is<00:46:56.880> as<00:46:57.060> we're<00:46:57.240> executing<00:46:57.660> a 00:46:57.770 --> 00:46:57.780 align:start position:0% point is as we're executing a 00:46:57.780 --> 00:46:59.150 align:start position:0% point is as we're executing a cross-chain<00:46:58.140> message<00:46:58.380> we<00:46:58.619> can<00:46:58.740> access<00:46:58.859> this 00:46:59.150 --> 00:46:59.160 align:start position:0% cross-chain message we can access this 00:46:59.160 --> 00:47:01.069 align:start position:0% cross-chain message we can access this context<00:46:59.520> so<00:46:59.880> we<00:47:00.060> can<00:47:00.180> do<00:47:00.300> the<00:47:00.540> checks<00:47:00.839> that<00:47:00.960> we 00:47:01.069 --> 00:47:01.079 align:start position:0% context so we can do the checks that we 00:47:01.079 --> 00:47:02.569 align:start position:0% context so we can do the checks that we need 00:47:02.569 --> 00:47:02.579 align:start position:0% need 00:47:02.579 --> 00:47:04.069 align:start position:0% need um 00:47:04.069 --> 00:47:04.079 align:start position:0% um 00:47:04.079 --> 00:47:05.690 align:start position:0% um so<00:47:04.680> that's<00:47:04.920> going<00:47:05.040> to<00:47:05.099> be<00:47:05.220> important<00:47:05.520> that's 00:47:05.690 --> 00:47:05.700 align:start position:0% so that's going to be important that's 00:47:05.700 --> 00:47:07.069 align:start position:0% so that's going to be important that's how<00:47:05.880> we'll<00:47:06.060> ensure<00:47:06.480> that<00:47:06.660> it's<00:47:06.780> really<00:47:06.900> coming 00:47:07.069 --> 00:47:07.079 align:start position:0% how we'll ensure that it's really coming 00:47:07.079 --> 00:47:08.990 align:start position:0% how we'll ensure that it's really coming from<00:47:07.319> the<00:47:07.440> L2<00:47:07.680> Gateway 00:47:08.990 --> 00:47:09.000 align:start position:0% from the L2 Gateway 00:47:09.000 --> 00:47:10.790 align:start position:0% from the L2 Gateway and<00:47:09.359> then<00:47:09.480> finally 00:47:10.790 --> 00:47:10.800 align:start position:0% and then finally 00:47:10.800 --> 00:47:11.809 align:start position:0% and then finally um the<00:47:10.980> thing<00:47:11.099> that<00:47:11.220> actually<00:47:11.400> makes<00:47:11.640> the 00:47:11.809 --> 00:47:11.819 align:start position:0% um the thing that actually makes the 00:47:11.819 --> 00:47:13.970 align:start position:0% um the thing that actually makes the call<00:47:12.000> is<00:47:12.839> going<00:47:12.960> to<00:47:13.079> be<00:47:13.200> this<00:47:13.440> other<00:47:13.619> contract 00:47:13.970 --> 00:47:13.980 align:start position:0% call is going to be this other contract 00:47:13.980 --> 00:47:15.589 align:start position:0% call is going to be this other contract that's<00:47:14.220> the<00:47:14.400> bridge<00:47:14.520> so<00:47:14.940> that's<00:47:15.060> always<00:47:15.240> how 00:47:15.589 --> 00:47:15.599 align:start position:0% that's the bridge so that's always how 00:47:15.599 --> 00:47:18.170 align:start position:0% that's the bridge so that's always how L2<00:47:16.140> to<00:47:16.319> L1<00:47:16.619> messages<00:47:16.800> work<00:47:17.160> so<00:47:17.640> we<00:47:17.700> ensure<00:47:18.000> that 00:47:18.170 --> 00:47:18.180 align:start position:0% L2 to L1 messages work so we ensure that 00:47:18.180 --> 00:47:19.849 align:start position:0% L2 to L1 messages work so we ensure that it's<00:47:18.300> really<00:47:18.480> coming<00:47:18.720> from<00:47:18.960> the<00:47:19.079> bridge<00:47:19.260> and 00:47:19.849 --> 00:47:19.859 align:start position:0% it's really coming from the bridge and 00:47:19.859 --> 00:47:21.650 align:start position:0% it's really coming from the bridge and then<00:47:19.980> we<00:47:20.099> would<00:47:20.220> also<00:47:20.520> ensure<00:47:20.940> I'm<00:47:21.300> sure<00:47:21.540> it's 00:47:21.650 --> 00:47:21.660 align:start position:0% then we would also ensure I'm sure it's 00:47:21.660 --> 00:47:23.270 align:start position:0% then we would also ensure I'm sure it's really<00:47:21.780> coming<00:47:22.020> from<00:47:22.200> the<00:47:22.319> bridge<00:47:22.440> that's 00:47:23.270 --> 00:47:23.280 align:start position:0% really coming from the bridge that's 00:47:23.280 --> 00:47:25.250 align:start position:0% really coming from the bridge that's half<00:47:23.640> the<00:47:23.880> step<00:47:24.060> half<00:47:24.359> of<00:47:24.540> the<00:47:24.599> work<00:47:24.720> the<00:47:25.079> other 00:47:25.250 --> 00:47:25.260 align:start position:0% half the step half of the work the other 00:47:25.260 --> 00:47:27.530 align:start position:0% half the step half of the work the other half<00:47:25.440> is<00:47:25.619> making<00:47:25.859> sure<00:47:26.099> that<00:47:26.400> it's<00:47:26.640> uh<00:47:26.760> we<00:47:27.000> grab 00:47:27.530 --> 00:47:27.540 align:start position:0% half is making sure that it's uh we grab 00:47:27.540 --> 00:47:28.670 align:start position:0% half is making sure that it's uh we grab that<00:47:27.720> context<00:47:28.020> and<00:47:28.200> make<00:47:28.319> sure<00:47:28.440> it's<00:47:28.560> really 00:47:28.670 --> 00:47:28.680 align:start position:0% that context and make sure it's really 00:47:28.680 --> 00:47:30.050 align:start position:0% that context and make sure it's really coming<00:47:28.920> from 00:47:30.050 --> 00:47:30.060 align:start position:0% coming from 00:47:30.060 --> 00:47:31.970 align:start position:0% coming from um<00:47:30.119> the<00:47:30.300> address<00:47:30.420> that<00:47:30.720> we<00:47:30.839> expect 00:47:31.970 --> 00:47:31.980 align:start position:0% um the address that we expect 00:47:31.980 --> 00:47:33.230 align:start position:0% um the address that we expect um<00:47:32.040> let<00:47:32.400> me<00:47:32.520> just<00:47:32.579> throw<00:47:32.760> that<00:47:32.880> in<00:47:33.000> here<00:47:33.119> I 00:47:33.230 --> 00:47:33.240 align:start position:0% um let me just throw that in here I 00:47:33.240 --> 00:47:34.250 align:start position:0% um let me just throw that in here I think<00:47:33.300> there's<00:47:33.420> time 00:47:34.250 --> 00:47:34.260 align:start position:0% think there's time 00:47:34.260 --> 00:47:37.069 align:start position:0% think there's time um so<00:47:34.440> that<00:47:34.560> this<00:47:34.740> is<00:47:34.859> at<00:47:34.980> least<00:47:35.160> complete 00:47:37.069 --> 00:47:37.079 align:start position:0% um so that this is at least complete 00:47:37.079 --> 00:47:39.370 align:start position:0% um so that this is at least complete um so<00:47:37.619> we'll<00:47:37.800> grab<00:47:38.040> that<00:47:38.280> out<00:47:38.520> box<00:47:38.700> contract 00:47:39.370 --> 00:47:39.380 align:start position:0% um so we'll grab that out box contract 00:47:39.380 --> 00:47:43.490 align:start position:0% um so we'll grab that out box contract and<00:47:40.380> this<00:47:40.680> is<00:47:41.160> uh<00:47:42.180> we<00:47:42.599> can<00:47:42.720> just<00:47:42.839> do<00:47:43.020> this<00:47:43.260> in 00:47:43.490 --> 00:47:43.500 align:start position:0% and this is uh we can just do this in 00:47:43.500 --> 00:47:46.430 align:start position:0% and this is uh we can just do this in one<00:47:43.680> line<00:47:43.859> I<00:47:44.220> guess<00:47:44.339> slightly<00:47:45.240> ugly<00:47:45.359> but<00:47:46.140> we 00:47:46.430 --> 00:47:46.440 align:start position:0% one line I guess slightly ugly but we 00:47:46.440 --> 00:47:48.950 align:start position:0% one line I guess slightly ugly but we can<00:47:46.560> instantiate<00:47:47.280> the<00:47:47.700> bridge 00:47:48.950 --> 00:47:48.960 align:start position:0% can instantiate the bridge 00:47:48.960 --> 00:47:50.870 align:start position:0% can instantiate the bridge and<00:47:49.319> then<00:47:49.380> the<00:47:49.560> bridge<00:47:49.740> gives<00:47:50.160> us<00:47:50.280> access<00:47:50.520> to 00:47:50.870 --> 00:47:50.880 align:start position:0% and then the bridge gives us access to 00:47:50.880 --> 00:47:54.109 align:start position:0% and then the bridge gives us access to the<00:47:51.000> active<00:47:51.540> outbox<00:47:51.900> this<00:47:52.440> is<00:47:52.560> just 00:47:54.109 --> 00:47:54.119 align:start position:0% the active outbox this is just 00:47:54.119 --> 00:47:56.390 align:start position:0% the active outbox this is just so<00:47:54.599> we<00:47:54.720> don't<00:47:54.780> have<00:47:54.900> to<00:47:55.020> store<00:47:55.140> another<00:47:55.400> uh 00:47:56.390 --> 00:47:56.400 align:start position:0% so we don't have to store another uh 00:47:56.400 --> 00:47:58.130 align:start position:0% so we don't have to store another uh another<00:47:56.700> address 00:47:58.130 --> 00:47:58.140 align:start position:0% another address 00:47:58.140 --> 00:48:04.130 align:start position:0% another address um 00:48:04.130 --> 00:48:04.140 align:start position:0% 00:48:04.140 --> 00:48:05.690 align:start position:0% yes 00:48:05.690 --> 00:48:05.700 align:start position:0% yes 00:48:05.700 --> 00:48:10.790 align:start position:0% yes um 00:48:10.790 --> 00:48:10.800 align:start position:0% 00:48:10.800 --> 00:48:13.250 align:start position:0% that<00:48:11.579> looks<00:48:11.940> like<00:48:12.060> something<00:48:12.359> might<00:48:12.599> be<00:48:12.780> off<00:48:12.900> I 00:48:13.250 --> 00:48:13.260 align:start position:0% that looks like something might be off I 00:48:13.260 --> 00:48:14.470 align:start position:0% that looks like something might be off I don't<00:48:13.380> answer 00:48:14.470 --> 00:48:14.480 align:start position:0% don't answer 00:48:14.480 --> 00:48:21.410 align:start position:0% don't answer uh<00:48:15.480> attention<00:48:15.960> this<00:48:16.740> is<00:48:16.859> hard<00:48:17.040> to<00:48:17.280> do<00:48:17.460> live 00:48:21.410 --> 00:48:21.420 align:start position:0% 00:48:21.420 --> 00:48:27.430 align:start position:0% um 00:48:27.430 --> 00:48:27.440 align:start position:0% 00:48:27.440 --> 00:48:31.069 align:start position:0% I<00:48:28.440> didn't<00:48:28.560> call<00:48:28.619> it<00:48:28.740> anything<00:48:28.859> yes 00:48:31.069 --> 00:48:31.079 align:start position:0% I didn't call it anything yes 00:48:31.079 --> 00:48:32.930 align:start position:0% I didn't call it anything yes thank<00:48:31.380> you 00:48:32.930 --> 00:48:32.940 align:start position:0% thank you 00:48:32.940 --> 00:48:34.069 align:start position:0% thank you and<00:48:33.180> then<00:48:33.300> I<00:48:33.359> think<00:48:33.480> that's<00:48:33.599> also<00:48:33.780> messed<00:48:34.020> it 00:48:34.069 --> 00:48:34.079 align:start position:0% and then I think that's also messed it 00:48:34.079 --> 00:48:35.809 align:start position:0% and then I think that's also messed it up 00:48:35.809 --> 00:48:35.819 align:start position:0% up 00:48:35.819 --> 00:48:39.050 align:start position:0% up um 00:48:39.050 --> 00:48:39.060 align:start position:0% 00:48:39.060 --> 00:48:40.250 align:start position:0% yeah 00:48:40.250 --> 00:48:40.260 align:start position:0% yeah 00:48:40.260 --> 00:48:42.290 align:start position:0% yeah I'm<00:48:40.680> gonna<00:48:40.920> sing<00:48:41.160> a 00:48:42.290 --> 00:48:42.300 align:start position:0% I'm gonna sing a 00:48:42.300 --> 00:48:45.290 align:start position:0% I'm gonna sing a oh<00:48:42.540> at<00:48:42.900> the<00:48:43.020> end<00:48:43.140> yeah<00:48:43.500> that<00:48:43.800> should<00:48:43.980> be 00:48:45.290 --> 00:48:45.300 align:start position:0% oh at the end yeah that should be 00:48:45.300 --> 00:48:47.630 align:start position:0% oh at the end yeah that should be yeah<00:48:45.480> we're<00:48:45.839> instantiating<00:48:46.500> after<00:48:47.220> we<00:48:47.460> call 00:48:47.630 --> 00:48:47.640 align:start position:0% yeah we're instantiating after we call 00:48:47.640 --> 00:48:49.490 align:start position:0% yeah we're instantiating after we call there<00:48:47.880> we<00:48:48.060> go<00:48:48.119> that's<00:48:48.300> the<00:48:48.480> address<00:48:48.599> okay<00:48:49.020> so 00:48:49.490 --> 00:48:49.500 align:start position:0% there we go that's the address okay so 00:48:49.500 --> 00:48:50.750 align:start position:0% there we go that's the address okay so we're<00:48:49.619> just<00:48:49.740> grabbing<00:48:49.980> the<00:48:50.160> outbox<00:48:50.460> address 00:48:50.750 --> 00:48:50.760 align:start position:0% we're just grabbing the outbox address 00:48:50.760 --> 00:48:52.069 align:start position:0% we're just grabbing the outbox address which<00:48:51.180> is<00:48:51.359> stored<00:48:51.599> in<00:48:51.720> our<00:48:51.839> protocol 00:48:52.069 --> 00:48:52.079 align:start position:0% which is stored in our protocol 00:48:52.079 --> 00:48:53.630 align:start position:0% which is stored in our protocol contracts 00:48:53.630 --> 00:48:53.640 align:start position:0% contracts 00:48:53.640 --> 00:48:57.950 align:start position:0% contracts um<00:48:53.760> and<00:48:54.000> now<00:48:54.119> uh<00:48:54.480> we<00:48:54.599> can<00:48:54.720> get<00:48:54.839> the<00:48:54.900> L2<00:48:55.140> sender 00:48:57.950 --> 00:48:57.960 align:start position:0% 00:48:57.960 --> 00:49:00.349 align:start position:0% via<00:48:58.380> this<00:48:58.560> neat<00:48:58.859> little<00:48:58.980> context<00:48:59.400> trick 00:49:00.349 --> 00:49:00.359 align:start position:0% via this neat little context trick 00:49:00.359 --> 00:49:06.470 align:start position:0% via this neat little context trick um<00:49:00.480> what<00:49:00.660> is<00:49:00.900> uh<00:49:01.140> L2<00:49:01.440> element<00:49:01.680> Center 00:49:06.470 --> 00:49:06.480 align:start position:0% 00:49:06.480 --> 00:49:10.010 align:start position:0% how<00:49:07.020> to<00:49:07.260> to<00:49:07.740> L1<00:49:08.460> sender<00:49:09.180> so<00:49:09.599> that<00:49:09.720> updates 00:49:10.010 --> 00:49:10.020 align:start position:0% how to to L1 sender so that updates 00:49:10.020 --> 00:49:12.290 align:start position:0% how to to L1 sender so that updates during<00:49:10.319> the<00:49:10.500> context<00:49:10.740> of<00:49:10.920> execution<00:49:11.400> and<00:49:12.119> now 00:49:12.290 --> 00:49:12.300 align:start position:0% during the context of execution and now 00:49:12.300 --> 00:49:15.530 align:start position:0% during the context of execution and now we<00:49:12.480> want<00:49:12.599> to<00:49:12.720> make<00:49:12.900> sure<00:49:13.079> that<00:49:13.380> that<00:49:13.619> thing 00:49:15.530 --> 00:49:15.540 align:start position:0% we want to make sure that that thing 00:49:15.540 --> 00:49:17.450 align:start position:0% we want to make sure that that thing um<00:49:15.599> is<00:49:16.020> the<00:49:16.319> counterpart<00:49:16.859> gateway<00:49:17.280> address 00:49:17.450 --> 00:49:17.460 align:start position:0% um is the counterpart gateway address 00:49:17.460 --> 00:49:21.589 align:start position:0% um is the counterpart gateway address basically 00:49:21.589 --> 00:49:21.599 align:start position:0% 00:49:21.599 --> 00:49:25.010 align:start position:0% uh 00:49:25.010 --> 00:49:25.020 align:start position:0% 00:49:25.020 --> 00:49:28.250 align:start position:0% from<00:49:25.500> Gateway 00:49:28.250 --> 00:49:28.260 align:start position:0% 00:49:28.260 --> 00:49:29.809 align:start position:0% okay 00:49:29.809 --> 00:49:29.819 align:start position:0% okay 00:49:29.819 --> 00:49:31.490 align:start position:0% okay um so<00:49:30.119> because<00:49:30.660> there's<00:49:30.900> no<00:49:31.020> automatic 00:49:31.490 --> 00:49:31.500 align:start position:0% um so because there's no automatic 00:49:31.500 --> 00:49:33.050 align:start position:0% um so because there's no automatic execution<00:49:31.920> because<00:49:32.220> this<00:49:32.520> doesn't<00:49:32.700> work<00:49:32.880> the 00:49:33.050 --> 00:49:33.060 align:start position:0% execution because this doesn't work the 00:49:33.060 --> 00:49:34.190 align:start position:0% execution because this doesn't work the way<00:49:33.180> you<00:49:33.300> know<00:49:33.420> tribal<00:49:33.780> tickets<00:49:33.900> work 00:49:34.190 --> 00:49:34.200 align:start position:0% way you know tribal tickets work 00:49:34.200 --> 00:49:35.510 align:start position:0% way you know tribal tickets work checking<00:49:34.740> out<00:49:34.800> the<00:49:34.980> sender<00:49:35.220> is<00:49:35.280> where<00:49:35.400> we 00:49:35.510 --> 00:49:35.520 align:start position:0% checking out the sender is where we 00:49:35.520 --> 00:49:37.069 align:start position:0% checking out the sender is where we expect<00:49:35.640> it<00:49:35.819> to<00:49:35.940> be<00:49:36.060> is<00:49:36.180> slightly<00:49:36.900> different 00:49:37.069 --> 00:49:37.079 align:start position:0% expect it to be is slightly different 00:49:37.079 --> 00:49:38.569 align:start position:0% expect it to be is slightly different but<00:49:37.500> this<00:49:37.619> tells<00:49:37.920> us<00:49:37.980> yeah<00:49:38.160> it's<00:49:38.339> from<00:49:38.460> the 00:49:38.569 --> 00:49:38.579 align:start position:0% but this tells us yeah it's from the 00:49:38.579 --> 00:49:39.890 align:start position:0% but this tells us yeah it's from the address<00:49:38.700> we<00:49:38.940> expect<00:49:39.119> and<00:49:39.420> it<00:49:39.540> really<00:49:39.660> is<00:49:39.839> a 00:49:39.890 --> 00:49:39.900 align:start position:0% address we expect and it really is a 00:49:39.900 --> 00:49:41.870 align:start position:0% address we expect and it really is a cross-trained<00:49:40.380> message 00:49:41.870 --> 00:49:41.880 align:start position:0% cross-trained message 00:49:41.880 --> 00:49:43.370 align:start position:0% cross-trained message um<00:49:41.940> cool<00:49:42.420> since<00:49:42.660> we're<00:49:42.839> almost<00:49:43.020> out<00:49:43.200> of<00:49:43.319> time 00:49:43.370 --> 00:49:43.380 align:start position:0% um cool since we're almost out of time 00:49:43.380 --> 00:49:45.109 align:start position:0% um cool since we're almost out of time you<00:49:43.560> know<00:49:43.680> so<00:49:43.800> there's<00:49:43.980> if<00:49:44.280> you're<00:49:44.520> coding 00:49:45.109 --> 00:49:45.119 align:start position:0% you know so there's if you're coding 00:49:45.119 --> 00:49:46.250 align:start position:0% you know so there's if you're coding along<00:49:45.240> or<00:49:45.420> if<00:49:45.540> you<00:49:45.599> want<00:49:45.660> to<00:49:45.720> grab<00:49:45.839> the<00:49:45.960> repo 00:49:46.250 --> 00:49:46.260 align:start position:0% along or if you want to grab the repo 00:49:46.260 --> 00:49:47.210 align:start position:0% along or if you want to grab the repo there's<00:49:46.440> a<00:49:46.560> branch<00:49:46.680> that<00:49:46.859> has<00:49:47.040> like<00:49:47.099> a 00:49:47.210 --> 00:49:47.220 align:start position:0% there's a branch that has like a 00:49:47.220 --> 00:49:48.650 align:start position:0% there's a branch that has like a completed<00:49:47.520> version<00:49:47.700> I<00:49:48.000> can<00:49:48.119> also<00:49:48.300> push<00:49:48.480> this 00:49:48.650 --> 00:49:48.660 align:start position:0% completed version I can also push this 00:49:48.660 --> 00:49:51.470 align:start position:0% completed version I can also push this one<00:49:48.839> but<00:49:49.380> there's<00:49:50.099> um<00:49:50.099> scripts<00:49:50.819> to<00:49:51.000> deploy<00:49:51.359> the 00:49:51.470 --> 00:49:51.480 align:start position:0% one but there's um scripts to deploy the 00:49:51.480 --> 00:49:53.270 align:start position:0% one but there's um scripts to deploy the contracts<00:49:51.900> I<00:49:52.140> can<00:49:52.319> even<00:49:52.440> just 00:49:53.270 --> 00:49:53.280 align:start position:0% contracts I can even just 00:49:53.280 --> 00:49:54.950 align:start position:0% contracts I can even just really<00:49:53.760> quickly<00:49:54.060> run<00:49:54.180> then 00:49:54.950 --> 00:49:54.960 align:start position:0% really quickly run then 00:49:54.960 --> 00:49:56.690 align:start position:0% really quickly run then um 00:49:56.690 --> 00:49:56.700 align:start position:0% um 00:49:56.700 --> 00:49:58.609 align:start position:0% um I<00:49:57.180> don't<00:49:57.240> think<00:49:57.359> there's<00:49:57.480> anything<00:49:57.720> much<00:49:58.079> to 00:49:58.609 --> 00:49:58.619 align:start position:0% I don't think there's anything much to 00:49:58.619 --> 00:50:00.109 align:start position:0% I don't think there's anything much to show<00:49:59.400> there<00:49:59.640> but<00:49:59.760> then<00:49:59.940> there's<00:50:00.000> another 00:50:00.109 --> 00:50:00.119 align:start position:0% show there but then there's another 00:50:00.119 --> 00:50:01.069 align:start position:0% show there but then there's another script<00:50:00.420> that'll<00:50:00.660> actually<00:50:00.780> do<00:50:00.960> a 00:50:01.069 --> 00:50:01.079 align:start position:0% script that'll actually do a 00:50:01.079 --> 00:50:02.569 align:start position:0% script that'll actually do a registration<00:50:01.440> and<00:50:01.619> deposit<00:50:02.040> so<00:50:02.160> you<00:50:02.280> can<00:50:02.400> mess 00:50:02.569 --> 00:50:02.579 align:start position:0% registration and deposit so you can mess 00:50:02.579 --> 00:50:05.870 align:start position:0% registration and deposit so you can mess with<00:50:02.760> it<00:50:03.420> I'm<00:50:04.200> gonna<00:50:04.440> wrap<00:50:04.680> it<00:50:04.800> up<00:50:04.920> okay 00:50:05.870 --> 00:50:05.880 align:start position:0% with it I'm gonna wrap it up okay 00:50:05.880 --> 00:50:06.890 align:start position:0% with it I'm gonna wrap it up okay um 00:50:06.890 --> 00:50:06.900 align:start position:0% um 00:50:06.900 --> 00:50:08.930 align:start position:0% um but<00:50:07.380> uh<00:50:07.680> yeah<00:50:07.859> cool<00:50:08.160> if<00:50:08.460> we<00:50:08.579> have<00:50:08.700> to<00:50:08.819> stop 00:50:08.930 --> 00:50:08.940 align:start position:0% but uh yeah cool if we have to stop 00:50:08.940 --> 00:50:11.089 align:start position:0% but uh yeah cool if we have to stop there<00:50:09.060> I<00:50:09.240> guess<00:50:09.359> we'll<00:50:09.480> stop<00:50:09.660> there<00:50:09.839> yeah 00:50:11.089 --> 00:50:11.099 align:start position:0% there I guess we'll stop there yeah 00:50:11.099 --> 00:50:15.500 align:start position:0% there I guess we'll stop there yeah cool<00:50:11.520> uh<00:50:12.119> thank<00:50:12.359> you<00:50:12.480> all<00:50:12.720> for<00:50:13.140> listening