WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:02.270 align:start position:0% I<00:00:00.240> talked<00:00:00.810> today<00:00:00.930> is<00:00:01.199> about<00:00:01.469> the<00:00:02.040> kitchen 00:00:02.270 --> 00:00:02.280 align:start position:0% I talked today is about the kitchen 00:00:02.280 --> 00:00:05.059 align:start position:0% I talked today is about the kitchen suites<00:00:02.550> and<00:00:02.970> how<00:00:03.389> one<00:00:04.020> bytes<00:00:04.259> can<00:00:04.770> add<00:00:04.890> a<00:00:04.920> lot 00:00:05.059 --> 00:00:05.069 align:start position:0% suites and how one bytes can add a lot 00:00:05.069 --> 00:00:07.070 align:start position:0% suites and how one bytes can add a lot more<00:00:05.250> context<00:00:05.819> to<00:00:05.940> all<00:00:06.720> of<00:00:06.839> our<00:00:06.930> smart 00:00:07.070 --> 00:00:07.080 align:start position:0% more context to all of our smart 00:00:07.080 --> 00:00:10.009 align:start position:0% more context to all of our smart contracts<00:00:07.589> so<00:00:08.370> a<00:00:08.700> little<00:00:09.000> bit<00:00:09.090> about<00:00:09.210> me<00:00:09.389> I'm 00:00:10.009 --> 00:00:10.019 align:start position:0% contracts so a little bit about me I'm 00:00:10.019 --> 00:00:12.680 align:start position:0% contracts so a little bit about me I'm Brooklyn<00:00:10.740> zelicah<00:00:11.190> or<00:00:11.370> EXPEED<00:00:12.120> basically 00:00:12.680 --> 00:00:12.690 align:start position:0% Brooklyn zelicah or EXPEED basically 00:00:12.690 --> 00:00:15.230 align:start position:0% Brooklyn zelicah or EXPEED basically everywhere<00:00:12.990> on<00:00:13.080> the<00:00:13.170> Internet's<00:00:13.549> I<00:00:14.549> am<00:00:14.940> the 00:00:15.230 --> 00:00:15.240 align:start position:0% everywhere on the Internet's I am the 00:00:15.240 --> 00:00:18.080 align:start position:0% everywhere on the Internet's I am the CEO<00:00:16.020> and<00:00:16.230> chief<00:00:16.320> scientist<00:00:16.830> of<00:00:16.980> the<00:00:17.609> special 00:00:18.080 --> 00:00:18.090 align:start position:0% CEO and chief scientist of the special 00:00:18.090 --> 00:00:19.370 align:start position:0% CEO and chief scientist of the special projects<00:00:18.420> in<00:00:18.480> decentralized<00:00:18.930> engineering 00:00:19.370 --> 00:00:19.380 align:start position:0% projects in decentralized engineering 00:00:19.380 --> 00:00:21.679 align:start position:0% projects in decentralized engineering company<00:00:19.710> or<00:00:19.859> Spade<00:00:20.160> Co<00:00:20.340> we<00:00:21.210> are<00:00:21.330> in<00:00:21.510> the 00:00:21.679 --> 00:00:21.689 align:start position:0% company or Spade Co we are in the 00:00:21.689 --> 00:00:24.980 align:start position:0% company or Spade Co we are in the Tachyon<00:00:22.289> cohort<00:00:22.710> with<00:00:23.340> consensus<00:00:23.910> to<00:00:24.689> fund 00:00:24.980 --> 00:00:24.990 align:start position:0% Tachyon cohort with consensus to fund 00:00:24.990 --> 00:00:28.910 align:start position:0% Tachyon cohort with consensus to fund specifically<00:00:25.920> this<00:00:26.160> work<00:00:26.599> we<00:00:27.599> were<00:00:28.199> entirely 00:00:28.910 --> 00:00:28.920 align:start position:0% specifically this work we were entirely 00:00:28.920 --> 00:00:32.690 align:start position:0% specifically this work we were entirely an<00:00:29.130> open-source<00:00:29.580> and<00:00:29.970> our<00:00:30.300> grant<00:00:30.599> based<00:00:30.810> I<00:00:31.700> my 00:00:32.690 --> 00:00:32.700 align:start position:0% an open-source and our grant based I my 00:00:32.700 --> 00:00:34.310 align:start position:0% an open-source and our grant based I my main<00:00:33.210> background<00:00:33.420> is<00:00:33.690> I'm<00:00:33.780> a<00:00:33.809> programming 00:00:34.310 --> 00:00:34.320 align:start position:0% main background is I'm a programming 00:00:34.320 --> 00:00:37.400 align:start position:0% main background is I'm a programming language<00:00:34.399> theorist<00:00:35.399> and<00:00:35.579> practice<00:00:35.940> nerd<00:00:36.410> and 00:00:37.400 --> 00:00:37.410 align:start position:0% language theorist and practice nerd and 00:00:37.410 --> 00:00:39.110 align:start position:0% language theorist and practice nerd and was<00:00:38.040> previously<00:00:38.219> working<00:00:38.610> on<00:00:38.760> security 00:00:39.110 --> 00:00:39.120 align:start position:0% was previously working on security 00:00:39.120 --> 00:00:41.240 align:start position:0% was previously working on security tokens<00:00:39.570> and<00:00:39.899> a<00:00:40.230> formally<00:00:40.620> verified<00:00:40.649> language 00:00:41.240 --> 00:00:41.250 align:start position:0% tokens and a formally verified language 00:00:41.250 --> 00:00:44.840 align:start position:0% tokens and a formally verified language at<00:00:41.520> thin<00:00:42.059> Haven 00:00:44.840 --> 00:00:44.850 align:start position:0% 00:00:44.850 --> 00:00:46.430 align:start position:0% I'm<00:00:45.360> also<00:00:45.510> the<00:00:45.600> primary<00:00:45.870> author<00:00:46.110> of<00:00:46.260> a<00:00:46.350> couple 00:00:46.430 --> 00:00:46.440 align:start position:0% I'm also the primary author of a couple 00:00:46.440 --> 00:00:50.420 align:start position:0% I'm also the primary author of a couple ERC's<00:00:47.070> including<00:00:48.680> 1066<00:00:49.680> now<00:00:49.890> Scotia<00:00:50.190> sirs 00:00:50.420 --> 00:00:50.430 align:start position:0% ERC's including 1066 now Scotia sirs 00:00:50.430 --> 00:00:53.049 align:start position:0% ERC's including 1066 now Scotia sirs what<00:00:50.550> we'll<00:00:50.700> be<00:00:50.760> talking<00:00:50.910> about<00:00:51.030> mostly<00:00:51.239> today 00:00:53.049 --> 00:00:53.059 align:start position:0% what we'll be talking about mostly today 00:00:53.059 --> 00:00:55.639 align:start position:0% what we'll be talking about mostly today and<00:00:54.059> community<00:00:55.050> stuff<00:00:55.199> if<00:00:55.410> your<00:00:55.530> ever 00:00:55.639 --> 00:00:55.649 align:start position:0% and community stuff if your ever 00:00:55.649 --> 00:00:58.189 align:start position:0% and community stuff if your ever happened<00:00:56.190> to<00:00:56.250> be<00:00:56.309> around<00:00:56.520> Vancouver<00:00:56.989> I'm<00:00:57.989> the 00:00:58.189 --> 00:00:58.199 align:start position:0% happened to be around Vancouver I'm the 00:00:58.199 --> 00:00:59.990 align:start position:0% happened to be around Vancouver I'm the founder<00:00:58.949> and<00:00:59.070> organizer<00:00:59.370> of<00:00:59.489> the<00:00:59.670> functional 00:00:59.990 --> 00:01:00.000 align:start position:0% founder and organizer of the functional 00:01:00.000 --> 00:01:02.689 align:start position:0% founder and organizer of the functional programming<00:01:00.300> meetup<00:01:00.840> out<00:01:00.960> there<00:01:01.199> and<00:01:01.670> run<00:01:02.670> the 00:01:02.689 --> 00:01:02.699 align:start position:0% programming meetup out there and run the 00:01:02.699 --> 00:01:04.820 align:start position:0% programming meetup out there and run the technical<00:01:03.329> white<00:01:03.420> paper<00:01:03.629> Club<00:01:03.899> which<00:01:04.559> we<00:01:04.739> are 00:01:04.820 --> 00:01:04.830 align:start position:0% technical white paper Club which we are 00:01:04.830 --> 00:01:07.070 align:start position:0% technical white paper Club which we are hoping<00:01:04.979> to<00:01:05.220> move<00:01:05.339> online<00:01:05.670> so<00:01:06.150> please<00:01:06.330> watch 00:01:07.070 --> 00:01:07.080 align:start position:0% hoping to move online so please watch 00:01:07.080 --> 00:01:08.539 align:start position:0% hoping to move online so please watch for<00:01:07.290> announcements<00:01:07.409> on<00:01:07.740> that<00:01:07.799> and<00:01:08.130> join<00:01:08.369> us 00:01:08.539 --> 00:01:08.549 align:start position:0% for announcements on that and join us 00:01:08.549 --> 00:01:12.830 align:start position:0% for announcements on that and join us for<00:01:08.909> the<00:01:09.270> live<00:01:09.390> stream<00:01:09.630> so<00:01:11.510> cerium<00:01:12.510> is<00:01:12.600> in 00:01:12.830 --> 00:01:12.840 align:start position:0% for the live stream so cerium is in 00:01:12.840 --> 00:01:15.440 align:start position:0% for the live stream so cerium is in super<00:01:13.380> early<00:01:13.650> days<00:01:13.909> which<00:01:14.909> means<00:01:15.090> that<00:01:15.299> there 00:01:15.440 --> 00:01:15.450 align:start position:0% super early days which means that there 00:01:15.450 --> 00:01:18.350 align:start position:0% super early days which means that there is<00:01:15.509> a<00:01:15.540> lot<00:01:15.810> of<00:01:15.840> pain<00:01:16.140> points<00:01:16.759> which<00:01:17.759> broadly 00:01:18.350 --> 00:01:18.360 align:start position:0% is a lot of pain points which broadly 00:01:18.360 --> 00:01:20.780 align:start position:0% is a lot of pain points which broadly fall<00:01:18.900> into<00:01:19.080> three<00:01:19.259> categories<00:01:19.290> and<00:01:20.250> user 00:01:20.780 --> 00:01:20.790 align:start position:0% fall into three categories and user 00:01:20.790 --> 00:01:22.340 align:start position:0% fall into three categories and user feedback<00:01:21.030> is<00:01:21.330> almost<00:01:21.509> non-existent<00:01:21.720> you 00:01:22.340 --> 00:01:22.350 align:start position:0% feedback is almost non-existent you 00:01:22.350 --> 00:01:25.640 align:start position:0% feedback is almost non-existent you either<00:01:22.470> get<00:01:22.790> back<00:01:23.790> that<00:01:24.000> it<00:01:24.150> succeeded<00:01:24.509> or<00:01:24.930> it 00:01:25.640 --> 00:01:25.650 align:start position:0% either get back that it succeeded or it 00:01:25.650 --> 00:01:29.480 align:start position:0% either get back that it succeeded or it failed<00:01:25.979> and<00:01:26.280> that's<00:01:26.790> pretty<00:01:27.630> much<00:01:27.750> it<00:01:28.490> the 00:01:29.480 --> 00:01:29.490 align:start position:0% failed and that's pretty much it the 00:01:29.490 --> 00:01:32.090 align:start position:0% failed and that's pretty much it the developer<00:01:29.820> experience<00:01:30.710> leaves<00:01:31.710> something<00:01:31.979> to 00:01:32.090 --> 00:01:32.100 align:start position:0% developer experience leaves something to 00:01:32.100 --> 00:01:35.240 align:start position:0% developer experience leaves something to be<00:01:32.220> desired<00:01:33.560> debuggers<00:01:34.560> are<00:01:34.680> very<00:01:34.799> low<00:01:34.920> level 00:01:35.240 --> 00:01:35.250 align:start position:0% be desired debuggers are very low level 00:01:35.250 --> 00:01:36.800 align:start position:0% be desired debuggers are very low level you<00:01:35.909> just<00:01:36.030> have<00:01:36.119> a<00:01:36.180> step<00:01:36.390> through<00:01:36.540> debugger 00:01:36.800 --> 00:01:36.810 align:start position:0% you just have a step through debugger 00:01:36.810 --> 00:01:39.740 align:start position:0% you just have a step through debugger you<00:01:37.290> get<00:01:37.439> you<00:01:37.770> know<00:01:37.860> core<00:01:38.130> dumps<00:01:38.750> that's 00:01:39.740 --> 00:01:39.750 align:start position:0% you get you know core dumps that's 00:01:39.750 --> 00:01:41.899 align:start position:0% you get you know core dumps that's pretty<00:01:40.590> much<00:01:40.710> it<00:01:40.950> you<00:01:41.130> have<00:01:41.400> almost<00:01:41.700> no 00:01:41.899 --> 00:01:41.909 align:start position:0% pretty much it you have almost no 00:01:41.909 --> 00:01:45.740 align:start position:0% pretty much it you have almost no feedback<00:01:42.680> we're<00:01:43.680> writing<00:01:44.040> for<00:01:44.399> the<00:01:45.360> machine 00:01:45.740 --> 00:01:45.750 align:start position:0% feedback we're writing for the machine 00:01:45.750 --> 00:01:48.560 align:start position:0% feedback we're writing for the machine and<00:01:46.110> not<00:01:46.409> for<00:01:46.560> humans<00:01:46.860> code<00:01:47.130> should<00:01:47.399> be<00:01:47.549> -<00:01:47.820> yes 00:01:48.560 --> 00:01:48.570 align:start position:0% and not for humans code should be - yes 00:01:48.570 --> 00:01:50.240 align:start position:0% and not for humans code should be - yes communicate<00:01:49.290> with<00:01:49.409> the<00:01:49.470> computer<00:01:49.649> but<00:01:50.100> it's 00:01:50.240 --> 00:01:50.250 align:start position:0% communicate with the computer but it's 00:01:50.250 --> 00:01:51.980 align:start position:0% communicate with the computer but it's also<00:01:50.430> for<00:01:51.240> communicating<00:01:51.630> with<00:01:51.810> other 00:01:51.980 --> 00:01:51.990 align:start position:0% also for communicating with other 00:01:51.990 --> 00:01:53.569 align:start position:0% also for communicating with other developers<00:01:52.560> so<00:01:52.860> that<00:01:52.890> when<00:01:53.130> you<00:01:53.250> leave<00:01:53.430> the 00:01:53.569 --> 00:01:53.579 align:start position:0% developers so that when you leave the 00:01:53.579 --> 00:01:54.920 align:start position:0% developers so that when you leave the project<00:01:54.000> other<00:01:54.180> people<00:01:54.450> can<00:01:54.570> understand 00:01:54.920 --> 00:01:54.930 align:start position:0% project other people can understand 00:01:54.930 --> 00:01:58.069 align:start position:0% project other people can understand what's<00:01:55.079> happening<00:01:55.549> and<00:01:56.549> even<00:01:57.509> when<00:01:57.960> you're 00:01:58.069 --> 00:01:58.079 align:start position:0% what's happening and even when you're 00:01:58.079 --> 00:01:59.420 align:start position:0% what's happening and even when you're doing<00:01:58.320> a<00:01:58.469> pull<00:01:58.770> request<00:01:58.799> you<00:01:59.280> should 00:01:59.420 --> 00:01:59.430 align:start position:0% doing a pull request you should 00:01:59.430 --> 00:02:03.050 align:start position:0% doing a pull request you should understand<00:01:59.909> everybody<00:02:00.360> else's<00:02:00.600> code<00:02:02.060> and 00:02:03.050 --> 00:02:03.060 align:start position:0% understand everybody else's code and 00:02:03.060 --> 00:02:05.749 align:start position:0% understand everybody else's code and solidity<00:02:03.750> and<00:02:04.290> other<00:02:04.710> languages<00:02:05.159> are<00:02:05.369> still 00:02:05.749 --> 00:02:05.759 align:start position:0% solidity and other languages are still 00:02:05.759 --> 00:02:07.310 align:start position:0% solidity and other languages are still not<00:02:05.850> mature<00:02:06.149> yet<00:02:06.180> they're<00:02:06.899> changing<00:02:07.170> a<00:02:07.229> lot 00:02:07.310 --> 00:02:07.320 align:start position:0% not mature yet they're changing a lot 00:02:07.320 --> 00:02:09.710 align:start position:0% not mature yet they're changing a lot which<00:02:07.530> means<00:02:07.740> that<00:02:07.860> we're<00:02:07.950> getting<00:02:08.450> new<00:02:09.450> cool 00:02:09.710 --> 00:02:09.720 align:start position:0% which means that we're getting new cool 00:02:09.720 --> 00:02:12.170 align:start position:0% which means that we're getting new cool things<00:02:10.050> that<00:02:10.259> are<00:02:10.470> making<00:02:10.590> life<00:02:10.800> better<00:02:11.180> but 00:02:12.170 --> 00:02:12.180 align:start position:0% things that are making life better but 00:02:12.180 --> 00:02:13.070 align:start position:0% things that are making life better but we're 00:02:13.070 --> 00:02:13.080 align:start position:0% we're 00:02:13.080 --> 00:02:16.490 align:start position:0% we're there's<00:02:14.040> quite<00:02:14.880> a<00:02:14.910> bit<00:02:15.090> more<00:02:15.210> left<00:02:15.510> to<00:02:15.570> do<00:02:15.810> so 00:02:16.490 --> 00:02:16.500 align:start position:0% there's quite a bit more left to do so 00:02:16.500 --> 00:02:18.530 align:start position:0% there's quite a bit more left to do so just<00:02:16.740> this<00:02:16.950> year<00:02:17.220> we<00:02:17.790> got<00:02:17.820> constructors 00:02:18.530 --> 00:02:18.540 align:start position:0% just this year we got constructors 00:02:18.540 --> 00:02:20.780 align:start position:0% just this year we got constructors syntax<00:02:18.870> and<00:02:19.020> solidity<00:02:19.320> revert<00:02:20.310> with<00:02:20.430> message 00:02:20.780 --> 00:02:20.790 align:start position:0% syntax and solidity revert with message 00:02:20.790 --> 00:02:23.090 align:start position:0% syntax and solidity revert with message and<00:02:21.060> a<00:02:21.300> bunch<00:02:21.480> more<00:02:21.540> changes<00:02:22.110> and<00:02:22.320> then<00:02:22.980> the 00:02:23.090 --> 00:02:23.100 align:start position:0% and a bunch more changes and then the 00:02:23.100 --> 00:02:26.660 align:start position:0% and a bunch more changes and then the third<00:02:23.370> area<00:02:23.730> is<00:02:24.260> smart<00:02:25.260> contracts<00:02:25.800> they 00:02:26.660 --> 00:02:26.670 align:start position:0% third area is smart contracts they 00:02:26.670 --> 00:02:28.280 align:start position:0% third area is smart contracts they should<00:02:26.940> be<00:02:27.150> these<00:02:27.360> autonomous<00:02:27.690> pieces<00:02:28.170> of 00:02:28.280 --> 00:02:28.290 align:start position:0% should be these autonomous pieces of 00:02:28.290 --> 00:02:30.470 align:start position:0% should be these autonomous pieces of code<00:02:28.500> that<00:02:28.970> understand<00:02:29.970> how<00:02:30.150> to<00:02:30.210> react 00:02:30.470 --> 00:02:30.480 align:start position:0% code that understand how to react 00:02:30.480 --> 00:02:32.620 align:start position:0% code that understand how to react autonomously<00:02:31.020> with<00:02:31.380> very<00:02:31.650> little<00:02:31.980> human 00:02:32.620 --> 00:02:32.630 align:start position:0% autonomously with very little human 00:02:32.630 --> 00:02:36.800 align:start position:0% autonomously with very little human involvement<00:02:34.010> but<00:02:35.010> we're<00:02:35.130> not<00:02:35.250> there<00:02:35.430> yet<00:02:35.490> so<00:02:36.030> I 00:02:36.800 --> 00:02:36.810 align:start position:0% involvement but we're not there yet so I 00:02:36.810 --> 00:02:38.150 align:start position:0% involvement but we're not there yet so I think<00:02:37.110> I<00:02:37.140> can<00:02:37.290> sum<00:02:37.440> this<00:02:37.530> up<00:02:37.650> by<00:02:37.770> saying<00:02:37.980> that 00:02:38.150 --> 00:02:38.160 align:start position:0% think I can sum this up by saying that 00:02:38.160 --> 00:02:41.860 align:start position:0% think I can sum this up by saying that lack<00:02:38.760> of<00:02:38.790> context<00:02:39.480> is<00:02:40.050> the<00:02:40.230> mind<00:02:40.410> killer 00:02:41.860 --> 00:02:41.870 align:start position:0% lack of context is the mind killer 00:02:41.870 --> 00:02:45.080 align:start position:0% lack of context is the mind killer so<00:02:42.870> a<00:02:43.230> quick<00:02:43.560> motivating<00:02:44.070> example<00:02:44.490> a<00:02:44.670> lot<00:02:45.000> of 00:02:45.080 --> 00:02:45.090 align:start position:0% so a quick motivating example a lot of 00:02:45.090 --> 00:02:47.360 align:start position:0% so a quick motivating example a lot of this<00:02:45.180> work<00:02:45.360> comes<00:02:45.600> out<00:02:45.840> of<00:02:46.040> the<00:02:47.040> security 00:02:47.360 --> 00:02:47.370 align:start position:0% this work comes out of the security 00:02:47.370 --> 00:02:51.170 align:start position:0% this work comes out of the security token<00:02:48.770> platform<00:02:49.770> we<00:02:49.830> were<00:02:49.920> building<00:02:50.190> at<00:02:50.490> my 00:02:51.170 --> 00:02:51.180 align:start position:0% token platform we were building at my 00:02:51.180 --> 00:02:55.850 align:start position:0% token platform we were building at my previous<00:02:51.930> employer<00:02:52.440> Finn<00:02:52.740> Haven<00:02:54.050> so<00:02:55.050> we 00:02:55.850 --> 00:02:55.860 align:start position:0% previous employer Finn Haven so we 00:02:55.860 --> 00:02:58.340 align:start position:0% previous employer Finn Haven so we needed<00:02:56.100> to<00:02:56.340> do<00:02:56.490> a<00:02:56.520> lot<00:02:56.820> of<00:02:57.350> authorization 00:02:58.340 --> 00:02:58.350 align:start position:0% needed to do a lot of authorization 00:02:58.350 --> 00:03:04.190 align:start position:0% needed to do a lot of authorization checking<00:03:00.500> so<00:03:01.500> a<00:03:02.100> bit<00:03:02.790> of<00:03:02.910> context<00:03:03.300> first<00:03:03.540> this 00:03:04.190 --> 00:03:04.200 align:start position:0% checking so a bit of context first this 00:03:04.200 --> 00:03:05.990 align:start position:0% checking so a bit of context first this is<00:03:04.260> what<00:03:04.350> a<00:03:04.440> validator<00:03:04.890> looks<00:03:05.100> like<00:03:05.310> you<00:03:05.910> have 00:03:05.990 --> 00:03:06.000 align:start position:0% is what a validator looks like you have 00:03:06.000 --> 00:03:09.350 align:start position:0% is what a validator looks like you have a<00:03:06.030> caller<00:03:06.470> which<00:03:07.470> might<00:03:07.680> be<00:03:07.830> a<00:03:08.070> human<00:03:08.670> a<00:03:08.910> smart 00:03:09.350 --> 00:03:09.360 align:start position:0% a caller which might be a human a smart 00:03:09.360 --> 00:03:11.480 align:start position:0% a caller which might be a human a smart contract<00:03:09.780> or<00:03:10.080> another<00:03:10.560> validator<00:03:11.010> that<00:03:11.250> calls 00:03:11.480 --> 00:03:11.490 align:start position:0% contract or another validator that calls 00:03:11.490 --> 00:03:12.890 align:start position:0% contract or another validator that calls a<00:03:11.610> check<00:03:11.790> function<00:03:11.970> and<00:03:12.360> then<00:03:12.450> returns<00:03:12.750> a 00:03:12.890 --> 00:03:12.900 align:start position:0% a check function and then returns a 00:03:12.900 --> 00:03:16.220 align:start position:0% a check function and then returns a status<00:03:13.260> back<00:03:13.880> and<00:03:14.880> then<00:03:15.720> that's<00:03:15.870> the<00:03:16.020> actual 00:03:16.220 --> 00:03:16.230 align:start position:0% status back and then that's the actual 00:03:16.230 --> 00:03:19.610 align:start position:0% status back and then that's the actual code<00:03:16.800> obviously<00:03:17.690> here's<00:03:18.690> a<00:03:18.750> quick<00:03:19.410> reference 00:03:19.610 --> 00:03:19.620 align:start position:0% code obviously here's a quick reference 00:03:19.620 --> 00:03:21.710 align:start position:0% code obviously here's a quick reference implementation<00:03:20.430> just<00:03:20.460> to<00:03:20.760> give<00:03:21.360> you<00:03:21.450> a<00:03:21.510> sense 00:03:21.710 --> 00:03:21.720 align:start position:0% implementation just to give you a sense 00:03:21.720 --> 00:03:24.670 align:start position:0% implementation just to give you a sense of<00:03:21.780> how<00:03:21.900> this<00:03:22.020> actually<00:03:22.260> works<00:03:23.210> so<00:03:24.210> we<00:03:24.420> have 00:03:24.670 --> 00:03:24.680 align:start position:0% of how this actually works so we have 00:03:24.680 --> 00:03:28.430 align:start position:0% of how this actually works so we have this<00:03:25.680> is<00:03:25.740> just<00:03:25.890> a<00:03:26.010> you<00:03:26.250> know<00:03:26.400> bog-standard<00:03:27.440> ERC 00:03:28.430 --> 00:03:28.440 align:start position:0% this is just a you know bog-standard ERC 00:03:28.440 --> 00:03:31.220 align:start position:0% this is just a you know bog-standard ERC 20<00:03:28.710> token<00:03:29.400> that<00:03:29.430> we've<00:03:29.670> added<00:03:29.910> one<00:03:30.270> line<00:03:30.990> to 00:03:31.220 --> 00:03:31.230 align:start position:0% 20 token that we've added one line to 00:03:31.230 --> 00:03:33.290 align:start position:0% 20 token that we've added one line to this<00:03:31.560> is<00:03:31.620> okay<00:03:32.130> and<00:03:32.460> then<00:03:32.640> the<00:03:32.760> validation 00:03:33.290 --> 00:03:33.300 align:start position:0% this is okay and then the validation 00:03:33.300 --> 00:03:35.390 align:start position:0% this is okay and then the validation call<00:03:33.510> and<00:03:33.840> the<00:03:34.320> validate<00:03:34.680> itself<00:03:35.040> is<00:03:35.190> just<00:03:35.340> a 00:03:35.390 --> 00:03:35.400 align:start position:0% call and the validate itself is just a 00:03:35.400 --> 00:03:37.280 align:start position:0% call and the validate itself is just a helper<00:03:35.670> function<00:03:35.840> that<00:03:36.840> calls<00:03:37.050> into<00:03:37.200> a 00:03:37.280 --> 00:03:37.290 align:start position:0% helper function that calls into a 00:03:37.290 --> 00:03:41.240 align:start position:0% helper function that calls into a validator<00:03:37.710> and<00:03:38.310> is<00:03:38.520> okay<00:03:39.140> checks<00:03:40.250> if 00:03:41.240 --> 00:03:41.250 align:start position:0% validator and is okay checks if 00:03:41.250 --> 00:03:44.840 align:start position:0% validator and is okay checks if something<00:03:41.700> is<00:03:42.440> is<00:03:43.440> allowed<00:03:43.800> if<00:03:44.040> it's<00:03:44.160> true<00:03:44.550> or 00:03:44.840 --> 00:03:44.850 align:start position:0% something is is allowed if it's true or 00:03:44.850 --> 00:03:46.970 align:start position:0% something is is allowed if it's true or in<00:03:45.480> the<00:03:45.660> later<00:03:45.840> version<00:03:46.260> which<00:03:46.500> we'll<00:03:46.620> see<00:03:46.740> in 00:03:46.970 --> 00:03:46.980 align:start position:0% in the later version which we'll see in 00:03:46.980 --> 00:03:49.520 align:start position:0% in the later version which we'll see in the<00:03:47.130> later<00:03:47.250> slide<00:03:47.610> if<00:03:48.300> the<00:03:48.660> status<00:03:48.990> code<00:03:49.230> is<00:03:49.410> in 00:03:49.520 --> 00:03:49.530 align:start position:0% the later slide if the status code is in 00:03:49.530 --> 00:03:52.070 align:start position:0% the later slide if the status code is in the<00:03:49.620> ok<00:03:49.890> range<00:03:50.390> so<00:03:51.390> here's<00:03:51.570> the<00:03:51.660> naive<00:03:51.930> version 00:03:52.070 --> 00:03:52.080 align:start position:0% the ok range so here's the naive version 00:03:52.080 --> 00:03:56.180 align:start position:0% the ok range so here's the naive version the<00:03:52.890> first<00:03:53.010> version<00:03:53.310> that<00:03:53.340> we<00:03:53.490> had<00:03:53.580> built<00:03:55.190> you 00:03:56.180 --> 00:03:56.190 align:start position:0% the first version that we had built you 00:03:56.190 --> 00:03:57.910 align:start position:0% the first version that we had built you have<00:03:56.310> your<00:03:56.430> token<00:03:56.760> and<00:03:57.030> it<00:03:57.420> needs<00:03:57.570> to<00:03:57.630> talk<00:03:57.750> to 00:03:57.910 --> 00:03:57.920 align:start position:0% have your token and it needs to talk to 00:03:57.920 --> 00:04:00.710 align:start position:0% have your token and it needs to talk to validate<00:03:58.920> or<00:03:59.010> a<00:03:59.130> guard<00:03:59.370> and<00:03:59.700> you<00:04:00.150> say<00:04:00.330> hey<00:04:00.510> am<00:04:00.630> I 00:04:00.710 --> 00:04:00.720 align:start position:0% validate or a guard and you say hey am I 00:04:00.720 --> 00:04:02.300 align:start position:0% validate or a guard and you say hey am I allowed<00:04:00.840> to<00:04:00.900> do<00:04:01.080> this<00:04:01.230> and<00:04:01.560> it<00:04:01.830> needs<00:04:01.980> to<00:04:02.130> talk 00:04:02.300 --> 00:04:02.310 align:start position:0% allowed to do this and it needs to talk 00:04:02.310 --> 00:04:03.890 align:start position:0% allowed to do this and it needs to talk to<00:04:02.490> some<00:04:02.820> others<00:04:03.090> because<00:04:03.510> you<00:04:03.540> might<00:04:03.720> have<00:04:03.840> a 00:04:03.890 --> 00:04:03.900 align:start position:0% to some others because you might have a 00:04:03.900 --> 00:04:05.090 align:start position:0% to some others because you might have a white<00:04:04.110> list<00:04:04.320> that's<00:04:04.590> maintained<00:04:04.950> between 00:04:05.090 --> 00:04:05.100 align:start position:0% white list that's maintained between 00:04:05.100 --> 00:04:06.380 align:start position:0% white list that's maintained between several<00:04:05.430> parties<00:04:05.820> and<00:04:06.060> you<00:04:06.120> don't<00:04:06.240> to 00:04:06.380 --> 00:04:06.390 align:start position:0% several parties and you don't to 00:04:06.390 --> 00:04:07.700 align:start position:0% several parties and you don't to duplicate<00:04:06.750> that<00:04:06.780> data<00:04:07.050> over<00:04:07.380> and<00:04:07.470> over<00:04:07.620> and 00:04:07.700 --> 00:04:07.710 align:start position:0% duplicate that data over and over and 00:04:07.710 --> 00:04:09.020 align:start position:0% duplicate that data over and over and over<00:04:07.800> again<00:04:07.980> so<00:04:08.130> you<00:04:08.430> need<00:04:08.550> to<00:04:08.610> check<00:04:08.790> with 00:04:09.020 --> 00:04:09.030 align:start position:0% over again so you need to check with 00:04:09.030 --> 00:04:14.890 align:start position:0% over again so you need to check with several<00:04:11.270> several<00:04:12.270> different<00:04:12.660> organizations 00:04:14.890 --> 00:04:14.900 align:start position:0% several several different organizations 00:04:14.900 --> 00:04:17.210 align:start position:0% several several different organizations worst<00:04:15.900> possible<00:04:16.290> example<00:04:16.739> but<00:04:16.890> to<00:04:17.010> kind<00:04:17.130> of 00:04:17.210 --> 00:04:17.220 align:start position:0% worst possible example but to kind of 00:04:17.220 --> 00:04:19.190 align:start position:0% worst possible example but to kind of give<00:04:17.340> you<00:04:17.430> a<00:04:17.489> flavor<00:04:17.640> is<00:04:18.030> Equifax<00:04:18.720> could 00:04:19.190 --> 00:04:19.200 align:start position:0% give you a flavor is Equifax could 00:04:19.200 --> 00:04:21.170 align:start position:0% give you a flavor is Equifax could maintain<00:04:20.160> a<00:04:20.340> whitelist<00:04:20.640> of<00:04:20.760> people<00:04:21.060> that 00:04:21.170 --> 00:04:21.180 align:start position:0% maintain a whitelist of people that 00:04:21.180 --> 00:04:22.190 align:start position:0% maintain a whitelist of people that they've<00:04:21.299> checked<00:04:21.510> their<00:04:21.690> ID<00:04:21.810> and<00:04:22.049> now<00:04:22.140> you 00:04:22.190 --> 00:04:22.200 align:start position:0% they've checked their ID and now you 00:04:22.200 --> 00:04:24.020 align:start position:0% they've checked their ID and now you have<00:04:22.380> your<00:04:22.410> kyc<00:04:22.919> done<00:04:23.100> without<00:04:23.400> you<00:04:23.700> having<00:04:23.910> to 00:04:24.020 --> 00:04:24.030 align:start position:0% have your kyc done without you having to 00:04:24.030 --> 00:04:26.750 align:start position:0% have your kyc done without you having to do<00:04:24.440> do<00:04:25.440> that<00:04:25.470> check<00:04:25.770> yourself<00:04:26.100> so 00:04:26.750 --> 00:04:26.760 align:start position:0% do do that check yourself so 00:04:26.760 --> 00:04:28.760 align:start position:0% do do that check yourself so it<00:04:26.910> delegates<00:04:27.270> this<00:04:27.450> call<00:04:27.780> on<00:04:28.020> and<00:04:28.440> we<00:04:28.620> get 00:04:28.760 --> 00:04:28.770 align:start position:0% it delegates this call on and we get 00:04:28.770 --> 00:04:30.440 align:start position:0% it delegates this call on and we get back<00:04:28.920> a<00:04:29.580> No 00:04:30.440 --> 00:04:30.450 align:start position:0% back a No 00:04:30.450 --> 00:04:35.600 align:start position:0% back a No but<00:04:30.690> it's<00:04:30.900> not<00:04:31.080> a<00:04:31.530> an<00:04:32.460> actual<00:04:33.950> exception<00:04:34.950> right 00:04:35.600 --> 00:04:35.610 align:start position:0% but it's not a an actual exception right 00:04:35.610 --> 00:04:38.270 align:start position:0% but it's not a an actual exception right it's<00:04:35.910> just<00:04:36.120> a<00:04:36.240> false<00:04:36.540> so<00:04:37.380> don't<00:04:37.650> explode<00:04:38.010> just 00:04:38.270 --> 00:04:38.280 align:start position:0% it's just a false so don't explode just 00:04:38.280 --> 00:04:40.850 align:start position:0% it's just a false so don't explode just say<00:04:38.370> no<00:04:38.580> they're<00:04:38.760> not<00:04:38.880> on<00:04:39.060> our<00:04:39.300> list<00:04:39.600> so<00:04:40.560> you<00:04:40.620> go 00:04:40.850 --> 00:04:40.860 align:start position:0% say no they're not on our list so you go 00:04:40.860 --> 00:04:42.290 align:start position:0% say no they're not on our list so you go and<00:04:40.950> you<00:04:41.040> check<00:04:41.220> some<00:04:41.370> more<00:04:41.550> and<00:04:41.850> this<00:04:42.180> one 00:04:42.290 --> 00:04:42.300 align:start position:0% and you check some more and this one 00:04:42.300 --> 00:04:44.750 align:start position:0% and you check some more and this one says<00:04:42.420> yep<00:04:42.660> and<00:04:42.990> then<00:04:43.560> you<00:04:43.860> have<00:04:44.190> to<00:04:44.310> also<00:04:44.460> check 00:04:44.750 --> 00:04:44.760 align:start position:0% says yep and then you have to also check 00:04:44.760 --> 00:04:47.930 align:start position:0% says yep and then you have to also check everybody<00:04:45.690> else<00:04:45.870> too<00:04:46.710> because<00:04:47.010> we<00:04:47.550> just<00:04:47.700> don't 00:04:47.930 --> 00:04:47.940 align:start position:0% everybody else too because we just don't 00:04:47.940 --> 00:04:49.640 align:start position:0% everybody else too because we just don't really<00:04:48.150> have<00:04:48.270> enough<00:04:48.720> context<00:04:49.290> so<00:04:49.380> when<00:04:49.470> I<00:04:49.500> say 00:04:49.640 --> 00:04:49.650 align:start position:0% really have enough context so when I say 00:04:49.650 --> 00:04:51.860 align:start position:0% really have enough context so when I say 203<00:04:50.310> is<00:04:50.370> probably<00:04:50.610> good<00:04:50.760> enough<00:04:50.880> and<00:04:51.510> we<00:04:51.690> turn 00:04:51.860 --> 00:04:51.870 align:start position:0% 203 is probably good enough and we turn 00:04:51.870 --> 00:04:53.440 align:start position:0% 203 is probably good enough and we turn you<00:04:52.020> up<00:04:52.080> they're<00:04:52.260> allowed<00:04:52.410> to<00:04:52.500> do<00:04:52.620> that<00:04:52.710> thing 00:04:53.440 --> 00:04:53.450 align:start position:0% you up they're allowed to do that thing 00:04:53.450 --> 00:04:57.350 align:start position:0% you up they're allowed to do that thing great<00:04:55.340> there's<00:04:56.340> this<00:04:56.460> great<00:04:56.700> Conor<00:04:57.000> McBride 00:04:57.350 --> 00:04:57.360 align:start position:0% great there's this great Conor McBride 00:04:57.360 --> 00:05:00.850 align:start position:0% great there's this great Conor McBride quotes<00:04:58.400> that<00:04:59.400> about<00:04:59.940> boolean<00:05:00.240> blindness 00:05:00.850 --> 00:05:00.860 align:start position:0% quotes that about boolean blindness 00:05:00.860 --> 00:05:03.650 align:start position:0% quotes that about boolean blindness boolean<00:05:01.860> czar<00:05:02.070> great<00:05:02.310> but<00:05:03.150> they<00:05:03.270> just<00:05:03.450> don't 00:05:03.650 --> 00:05:03.660 align:start position:0% boolean czar great but they just don't 00:05:03.660 --> 00:05:07.070 align:start position:0% boolean czar great but they just don't give<00:05:03.840> you<00:05:03.930> enough<00:05:04.280> context<00:05:05.810> you<00:05:06.810> need<00:05:06.960> to 00:05:07.070 --> 00:05:07.080 align:start position:0% give you enough context you need to 00:05:07.080 --> 00:05:10.490 align:start position:0% give you enough context you need to understand<00:05:07.650> the<00:05:08.070> exact<00:05:08.690> situation<00:05:09.690> in<00:05:10.320> which 00:05:10.490 --> 00:05:10.500 align:start position:0% understand the exact situation in which 00:05:10.500 --> 00:05:13.760 align:start position:0% understand the exact situation in which the<00:05:11.250> boolean<00:05:11.430> was<00:05:11.700> generated<00:05:12.240> to<00:05:12.810> know<00:05:12.990> what 00:05:13.760 --> 00:05:13.770 align:start position:0% the boolean was generated to know what 00:05:13.770 --> 00:05:17.740 align:start position:0% the boolean was generated to know what it<00:05:13.860> actually<00:05:13.890> means 00:05:17.740 --> 00:05:17.750 align:start position:0% 00:05:17.750 --> 00:05:24.230 align:start position:0% hence<00:05:18.950> your<00:05:20.150> 1066<00:05:21.150> fission<00:05:21.480> codes<00:05:23.060> which<00:05:24.060> help 00:05:24.230 --> 00:05:24.240 align:start position:0% hence your 1066 fission codes which help 00:05:24.240 --> 00:05:25.820 align:start position:0% hence your 1066 fission codes which help us<00:05:24.360> do<00:05:24.600> smart<00:05:24.900> contracts<00:05:25.350> that<00:05:25.560> look<00:05:25.680> more 00:05:25.820 --> 00:05:25.830 align:start position:0% us do smart contracts that look more 00:05:25.830 --> 00:05:30.380 align:start position:0% us do smart contracts that look more like<00:05:25.890> this<00:05:27.950> so<00:05:28.950> it's<00:05:29.070> something<00:05:29.220> like<00:05:29.390> HTTP 00:05:30.380 --> 00:05:30.390 align:start position:0% like this so it's something like HTTP 00:05:30.390 --> 00:05:34.190 align:start position:0% like this so it's something like HTTP set<00:05:30.630> HTTP<00:05:31.380> status<00:05:31.560> codes<00:05:32.930> it<00:05:33.930> gives<00:05:34.110> you 00:05:34.190 --> 00:05:34.200 align:start position:0% set HTTP status codes it gives you 00:05:34.200 --> 00:05:36.070 align:start position:0% set HTTP status codes it gives you something<00:05:34.470> more<00:05:34.620> than<00:05:34.890> true/false<00:05:35.310> or<00:05:35.580> revert 00:05:36.070 --> 00:05:36.080 align:start position:0% something more than true/false or revert 00:05:36.080 --> 00:05:41.210 align:start position:0% something more than true/false or revert and<00:05:38.540> a<00:05:39.540> nice<00:05:40.080> analogy<00:05:40.380> for<00:05:40.560> this<00:05:40.680> is<00:05:40.920> if<00:05:41.130> you 00:05:41.210 --> 00:05:41.220 align:start position:0% and a nice analogy for this is if you 00:05:41.220 --> 00:05:43.670 align:start position:0% and a nice analogy for this is if you think<00:05:41.430> of<00:05:41.550> your<00:05:41.880> smart<00:05:42.360> contract<00:05:42.810> as<00:05:42.990> nodes<00:05:43.260> in 00:05:43.670 --> 00:05:43.680 align:start position:0% think of your smart contract as nodes in 00:05:43.680 --> 00:05:49.580 align:start position:0% think of your smart contract as nodes in a<00:05:43.800> graph<00:05:43.830> of<00:05:45.410> halls<00:05:47.570> this<00:05:48.570> is<00:05:48.720> the<00:05:48.840> edges<00:05:49.290> and 00:05:49.580 --> 00:05:49.590 align:start position:0% a graph of halls this is the edges and 00:05:49.590 --> 00:05:52.190 align:start position:0% a graph of halls this is the edges and the<00:05:50.190> smart<00:05:50.970> contracts<00:05:51.420> are<00:05:51.540> the<00:05:51.690> nodes<00:05:51.900> so 00:05:52.190 --> 00:05:52.200 align:start position:0% the smart contracts are the nodes so 00:05:52.200 --> 00:05:53.420 align:start position:0% the smart contracts are the nodes so today 00:05:53.420 --> 00:05:53.430 align:start position:0% today 00:05:53.430 --> 00:05:55.760 align:start position:0% today typical<00:05:54.270> flow<00:05:54.420> is<00:05:54.570> you<00:05:54.690> take<00:05:54.930> a<00:05:55.140> bunch<00:05:55.410> of<00:05:55.560> open 00:05:55.760 --> 00:05:55.770 align:start position:0% typical flow is you take a bunch of open 00:05:55.770 --> 00:05:58.370 align:start position:0% typical flow is you take a bunch of open Zeppelin<00:05:56.750> contracts<00:05:57.750> kind<00:05:57.960> of<00:05:58.050> snap<00:05:58.200> them 00:05:58.370 --> 00:05:58.380 align:start position:0% Zeppelin contracts kind of snap them 00:05:58.380 --> 00:05:59.840 align:start position:0% Zeppelin contracts kind of snap them together<00:05:58.530> to<00:05:58.890> create<00:05:59.040> one<00:05:59.280> we're<00:05:59.700> saying 00:05:59.840 --> 00:05:59.850 align:start position:0% together to create one we're saying 00:05:59.850 --> 00:06:01.960 align:start position:0% together to create one we're saying that's<00:06:00.030> great<00:06:00.330> fully<00:06:00.930> compatible<00:06:01.200> with<00:06:01.470> that 00:06:01.960 --> 00:06:01.970 align:start position:0% that's great fully compatible with that 00:06:01.970 --> 00:06:04.370 align:start position:0% that's great fully compatible with that but<00:06:02.970> if<00:06:03.120> you<00:06:03.240> need<00:06:03.420> to<00:06:03.510> have<00:06:03.570> two<00:06:03.810> or<00:06:04.080> three<00:06:04.110> or 00:06:04.370 --> 00:06:04.380 align:start position:0% but if you need to have two or three or 00:06:04.380 --> 00:06:06.140 align:start position:0% but if you need to have two or three or four<00:06:04.530> of<00:06:04.650> those<00:06:04.740> talk<00:06:04.950> to<00:06:05.070> each<00:06:05.160> other<00:06:05.370> it 00:06:06.140 --> 00:06:06.150 align:start position:0% four of those talk to each other it 00:06:06.150 --> 00:06:07.670 align:start position:0% four of those talk to each other it would<00:06:06.240> be<00:06:06.330> good<00:06:06.510> to<00:06:06.600> have<00:06:06.690> some<00:06:06.900> more<00:06:07.050> context 00:06:07.670 --> 00:06:07.680 align:start position:0% would be good to have some more context 00:06:07.680 --> 00:06:09.170 align:start position:0% would be good to have some more context about<00:06:07.740> what's<00:06:07.950> happening<00:06:08.340> on<00:06:08.520> those<00:06:08.940> other 00:06:09.170 --> 00:06:09.180 align:start position:0% about what's happening on those other 00:06:09.180 --> 00:06:11.630 align:start position:0% about what's happening on those other nodes<00:06:09.500> much<00:06:10.500> like<00:06:10.650> you<00:06:10.770> would<00:06:10.860> have<00:06:10.980> in<00:06:11.340> say<00:06:11.610> a 00:06:11.630 --> 00:06:11.640 align:start position:0% nodes much like you would have in say a 00:06:11.640 --> 00:06:16.250 align:start position:0% nodes much like you would have in say a microservice<00:06:12.240> architecture<00:06:12.780> on<00:06:12.960> the<00:06:12.990> web<00:06:15.260> so 00:06:16.250 --> 00:06:16.260 align:start position:0% microservice architecture on the web so 00:06:16.260 --> 00:06:19.250 align:start position:0% microservice architecture on the web so this<00:06:16.410> is<00:06:16.560> a<00:06:17.030> common<00:06:18.030> vocabulary<00:06:18.450> for<00:06:19.050> smart 00:06:19.250 --> 00:06:19.260 align:start position:0% this is a common vocabulary for smart 00:06:19.260 --> 00:06:22.210 align:start position:0% this is a common vocabulary for smart contracts<00:06:19.770> I<00:06:20.010> gives<00:06:20.610> us<00:06:20.760> richer<00:06:21.150> context 00:06:22.210 --> 00:06:22.220 align:start position:0% contracts I gives us richer context 00:06:22.220 --> 00:06:25.190 align:start position:0% contracts I gives us richer context about<00:06:23.220> what's<00:06:23.970> happened<00:06:24.390> on<00:06:24.750> the<00:06:24.900> other<00:06:25.020> side 00:06:25.190 --> 00:06:25.200 align:start position:0% about what's happened on the other side 00:06:25.200 --> 00:06:27.830 align:start position:0% about what's happened on the other side of<00:06:25.290> a<00:06:25.350> function<00:06:25.650> call<00:06:25.830> you<00:06:26.730> can<00:06:26.850> tag<00:06:27.090> arguments 00:06:27.830 --> 00:06:27.840 align:start position:0% of a function call you can tag arguments 00:06:27.840 --> 00:06:29.990 align:start position:0% of a function call you can tag arguments or<00:06:27.990> return<00:06:28.350> data<00:06:28.590> with<00:06:29.130> some<00:06:29.310> metadata<00:06:29.730> about 00:06:29.990 --> 00:06:30.000 align:start position:0% or return data with some metadata about 00:06:30.000 --> 00:06:32.390 align:start position:0% or return data with some metadata about what<00:06:30.300> it<00:06:30.420> means<00:06:30.660> and<00:06:31.290> expose<00:06:32.190> information 00:06:32.390 --> 00:06:32.400 align:start position:0% what it means and expose information 00:06:32.400 --> 00:06:34.160 align:start position:0% what it means and expose information about<00:06:32.910> an<00:06:33.000> internal<00:06:33.240> Michigan<00:06:33.600> State<00:06:33.870> for 00:06:34.160 --> 00:06:34.170 align:start position:0% about an internal Michigan State for 00:06:34.170 --> 00:06:36.230 align:start position:0% about an internal Michigan State for example<00:06:34.260> this<00:06:34.950> ICO<00:06:35.310> is<00:06:35.400> not<00:06:35.580> open<00:06:35.820> yet<00:06:35.940> but<00:06:36.120> it 00:06:36.230 --> 00:06:36.240 align:start position:0% example this ICO is not open yet but it 00:06:36.240 --> 00:06:40.129 align:start position:0% example this ICO is not open yet but it will<00:06:36.330> be<00:06:36.480> later 00:06:40.129 --> 00:06:40.139 align:start position:0% 00:06:40.139 --> 00:06:43.649 align:start position:0% and<00:06:41.139> yes<00:06:42.249> similar<00:06:42.699> to<00:06:42.819> HTTP<00:06:43.240> status<00:06:43.389> codes 00:06:43.649 --> 00:06:43.659 align:start position:0% and yes similar to HTTP status codes 00:06:43.659 --> 00:06:46.649 align:start position:0% and yes similar to HTTP status codes it's<00:06:43.840> a<00:06:43.870> different<00:06:44.139> problem<00:06:44.289> space<00:06:44.849> so<00:06:45.849> we 00:06:46.649 --> 00:06:46.659 align:start position:0% it's a different problem space so we 00:06:46.659 --> 00:06:50.129 align:start position:0% it's a different problem space so we don't<00:06:46.840> have<00:06:47.050> you<00:06:47.409> know<00:06:47.439> 404<00:06:48.310> not<00:06:49.029> found<00:06:49.090> or<00:06:49.539> 500 00:06:50.129 --> 00:06:50.139 align:start position:0% don't have you know 404 not found or 500 00:06:50.139 --> 00:06:54.029 align:start position:0% don't have you know 404 not found or 500 you<00:06:50.740> know<00:06:50.770> error<00:06:51.159> with<00:06:51.960> you<00:06:52.960> know<00:06:53.050> internal 00:06:54.029 --> 00:06:54.039 align:start position:0% you know error with you know internal 00:06:54.039 --> 00:06:56.670 align:start position:0% you know error with you know internal errors<00:06:55.080> because<00:06:56.080> it's<00:06:56.349> a<00:06:56.469> different 00:06:56.670 --> 00:06:56.680 align:start position:0% errors because it's a different 00:06:56.680 --> 00:06:58.649 align:start position:0% errors because it's a different different<00:06:57.610> platform<00:06:58.090> with<00:06:58.210> different<00:06:58.479> needs 00:06:58.649 --> 00:06:58.659 align:start position:0% different platform with different needs 00:06:58.659 --> 00:07:04.290 align:start position:0% different platform with different needs so<00:07:01.289> a<00:07:02.289> lot<00:07:03.249> more<00:07:03.279> information<00:07:03.520> about<00:07:03.819> this<00:07:04.090> is 00:07:04.290 --> 00:07:04.300 align:start position:0% so a lot more information about this is 00:07:04.300 --> 00:07:08.489 align:start position:0% so a lot more information about this is at<00:07:04.479> fission<00:07:05.259> dock<00:07:05.439> codes<00:07:06.659> and<00:07:07.659> this<00:07:08.319> was 00:07:08.489 --> 00:07:08.499 align:start position:0% at fission dock codes and this was 00:07:08.499 --> 00:07:10.589 align:start position:0% at fission dock codes and this was previously<00:07:08.800> titled<00:07:09.789> if<00:07:10.029> their<00:07:10.180> name<00:07:10.270> status 00:07:10.589 --> 00:07:10.599 align:start position:0% previously titled if their name status 00:07:10.599 --> 00:07:12.869 align:start position:0% previously titled if their name status codes<00:07:10.840> I<00:07:11.379> will<00:07:11.770> talk<00:07:11.889> about<00:07:12.009> why<00:07:12.219> we<00:07:12.759> changed 00:07:12.869 --> 00:07:12.879 align:start position:0% codes I will talk about why we changed 00:07:12.879 --> 00:07:15.420 align:start position:0% codes I will talk about why we changed the<00:07:13.029> name<00:07:13.090> a<00:07:13.180> little<00:07:13.300> bit<00:07:13.449> later<00:07:14.430> backronym 00:07:15.420 --> 00:07:15.430 align:start position:0% the name a little bit later backronym 00:07:15.430 --> 00:07:17.070 align:start position:0% the name a little bit later backronym czar<00:07:15.699> awesome<00:07:16.029> so<00:07:16.330> this<00:07:16.509> is<00:07:16.659> the<00:07:16.810> fluid 00:07:17.070 --> 00:07:17.080 align:start position:0% czar awesome so this is the fluid 00:07:17.080 --> 00:07:19.019 align:start position:0% czar awesome so this is the fluid interface<00:07:17.439> for<00:07:18.009> scalable<00:07:18.370> smart<00:07:18.610> contract 00:07:19.019 --> 00:07:19.029 align:start position:0% interface for scalable smart contract 00:07:19.029 --> 00:07:21.209 align:start position:0% interface for scalable smart contract interoperable<00:07:19.539> networks<00:07:20.009> not<00:07:21.009> to<00:07:21.159> be 00:07:21.209 --> 00:07:21.219 align:start position:0% interoperable networks not to be 00:07:21.219 --> 00:07:25.290 align:start position:0% interoperable networks not to be confused<00:07:21.460> with<00:07:21.610> the<00:07:21.699> fluent<00:07:22.090> interface<00:07:24.300> we 00:07:25.290 --> 00:07:25.300 align:start position:0% confused with the fluent interface we 00:07:25.300 --> 00:07:27.059 align:start position:0% confused with the fluent interface we have<00:07:25.419> some<00:07:25.539> organic<00:07:25.659> traction<00:07:26.349> so<00:07:26.919> it's 00:07:27.059 --> 00:07:27.069 align:start position:0% have some organic traction so it's 00:07:27.069 --> 00:07:29.760 align:start position:0% have some organic traction so it's already<00:07:27.279> required<00:07:27.759> by<00:07:28.090> three<00:07:29.020> RCS<00:07:29.439> nine<00:07:29.650> to 00:07:29.760 --> 00:07:29.770 align:start position:0% already required by three RCS nine to 00:07:29.770 --> 00:07:31.170 align:start position:0% already required by three RCS nine to two<00:07:29.919> fourteen<00:07:30.250> hundred<00:07:30.490> and<00:07:30.580> fourteen<00:07:30.909> sixty 00:07:31.170 --> 00:07:31.180 align:start position:0% two fourteen hundred and fourteen sixty 00:07:31.180 --> 00:07:33.779 align:start position:0% two fourteen hundred and fourteen sixty to<00:07:31.650> 1404<00:07:32.650> is<00:07:32.800> exploring<00:07:33.310> it<00:07:33.430> in<00:07:33.520> the<00:07:33.580> github 00:07:33.779 --> 00:07:33.789 align:start position:0% to 1404 is exploring it in the github 00:07:33.789 --> 00:07:38.029 align:start position:0% to 1404 is exploring it in the github issue<00:07:34.349> we've<00:07:35.349> been<00:07:35.469> talking<00:07:35.770> to<00:07:35.860> a<00:07:35.889> couple 00:07:38.029 --> 00:07:38.039 align:start position:0% issue we've been talking to a couple 00:07:38.039 --> 00:07:40.969 align:start position:0% issue we've been talking to a couple well-known<00:07:39.039> major<00:07:39.400> players<00:07:39.729> in<00:07:39.849> the<00:07:40.210> space 00:07:40.969 --> 00:07:40.979 align:start position:0% well-known major players in the space 00:07:40.979 --> 00:07:43.469 align:start position:0% well-known major players in the space we're<00:07:41.979> just<00:07:42.189> waiting<00:07:42.460> on<00:07:42.550> the<00:07:42.729> okay<00:07:43.029> to<00:07:43.060> make 00:07:43.469 --> 00:07:43.479 align:start position:0% we're just waiting on the okay to make 00:07:43.479 --> 00:07:45.450 align:start position:0% we're just waiting on the okay to make those<00:07:43.659> announcements<00:07:43.839> so<00:07:44.349> keep<00:07:45.189> an<00:07:45.339> eye<00:07:45.430> on 00:07:45.450 --> 00:07:45.460 align:start position:0% those announcements so keep an eye on 00:07:45.460 --> 00:07:47.850 align:start position:0% those announcements so keep an eye on our<00:07:45.639> website<00:07:46.089> and<00:07:47.020> we<00:07:47.469> are<00:07:47.529> part<00:07:47.710> of<00:07:47.740> the 00:07:47.850 --> 00:07:47.860 align:start position:0% our website and we are part of the 00:07:47.860 --> 00:07:50.670 align:start position:0% our website and we are part of the consensus<00:07:48.430> tachyon<00:07:48.870> accelerator<00:07:49.870> through 00:07:50.670 --> 00:07:50.680 align:start position:0% consensus tachyon accelerator through 00:07:50.680 --> 00:07:54.629 align:start position:0% consensus tachyon accelerator through the<00:07:50.800> open<00:07:51.550> source<00:07:51.639> R&D<00:07:52.089> grant<00:07:52.300> program<00:07:53.639> we're 00:07:54.629 --> 00:07:54.639 align:start position:0% the open source R&D grant program we're 00:07:54.639 --> 00:07:55.980 align:start position:0% the open source R&D grant program we're working<00:07:54.849> on<00:07:54.969> integration<00:07:55.270> with<00:07:55.479> common<00:07:55.719> tools 00:07:55.980 --> 00:07:55.990 align:start position:0% working on integration with common tools 00:07:55.990 --> 00:07:58.800 align:start position:0% working on integration with common tools we<00:07:56.409> have<00:07:56.649> a<00:07:56.680> fourth<00:07:57.069> version<00:07:57.339> of<00:07:57.580> my<00:07:58.389> crypto 00:07:58.800 --> 00:07:58.810 align:start position:0% we have a fourth version of my crypto 00:07:58.810 --> 00:08:00.540 align:start position:0% we have a fourth version of my crypto that<00:07:59.740> I'll<00:07:59.830> be<00:07:59.889> showing<00:08:00.009> you<00:08:00.159> some<00:08:00.219> slides 00:08:00.540 --> 00:08:00.550 align:start position:0% that I'll be showing you some slides 00:08:00.550 --> 00:08:03.389 align:start position:0% that I'll be showing you some slides from<00:08:00.930> later<00:08:01.930> that<00:08:02.500> will<00:08:02.589> be<00:08:02.710> pull<00:08:02.949> requesting 00:08:03.389 --> 00:08:03.399 align:start position:0% from later that will be pull requesting 00:08:03.399 --> 00:08:05.129 align:start position:0% from later that will be pull requesting into<00:08:03.610> them<00:08:03.729> and<00:08:03.969> we're<00:08:04.839> looking<00:08:05.080> at 00:08:05.129 --> 00:08:05.139 align:start position:0% into them and we're looking at 00:08:05.139 --> 00:08:08.670 align:start position:0% into them and we're looking at integrating<00:08:05.589> more<00:08:06.009> broadly<00:08:06.250> as<00:08:06.490> well<00:08:07.680> and 00:08:08.670 --> 00:08:08.680 align:start position:0% integrating more broadly as well and 00:08:08.680 --> 00:08:10.589 align:start position:0% integrating more broadly as well and we've<00:08:09.159> had<00:08:09.639> a<00:08:09.669> few<00:08:09.849> bounties<00:08:10.210> and<00:08:10.240> more<00:08:10.479> are 00:08:10.589 --> 00:08:10.599 align:start position:0% we've had a few bounties and more are 00:08:10.599 --> 00:08:12.119 align:start position:0% we've had a few bounties and more are coming<00:08:10.719> so<00:08:11.110> what<00:08:11.500> does<00:08:11.589> this<00:08:11.680> actually<00:08:11.919> look 00:08:12.119 --> 00:08:12.129 align:start position:0% coming so what does this actually look 00:08:12.129 --> 00:08:14.550 align:start position:0% coming so what does this actually look like<00:08:12.719> so<00:08:13.719> this<00:08:13.839> that<00:08:14.020> slide<00:08:14.259> I<00:08:14.289> showed<00:08:14.529> before 00:08:14.550 --> 00:08:14.560 align:start position:0% like so this that slide I showed before 00:08:14.560 --> 00:08:16.619 align:start position:0% like so this that slide I showed before and<00:08:15.520> we're<00:08:15.639> saying<00:08:15.789> that<00:08:15.879> we<00:08:16.149> can<00:08:16.270> take<00:08:16.419> these 00:08:16.619 --> 00:08:16.629 align:start position:0% and we're saying that we can take these 00:08:16.629 --> 00:08:18.240 align:start position:0% and we're saying that we can take these boolean<00:08:17.259> x'<00:08:17.349> and<00:08:17.589> turn<00:08:17.770> them<00:08:17.889> into<00:08:17.919> something 00:08:18.240 --> 00:08:18.250 align:start position:0% boolean x' and turn them into something 00:08:18.250 --> 00:08:20.129 align:start position:0% boolean x' and turn them into something a<00:08:18.279> little<00:08:18.370> bit<00:08:18.550> more<00:08:18.669> context<00:08:19.300> so<00:08:19.839> that<00:08:19.930> we<00:08:20.020> can 00:08:20.129 --> 00:08:20.139 align:start position:0% a little bit more context so that we can 00:08:20.139 --> 00:08:22.740 align:start position:0% a little bit more context so that we can do<00:08:20.229> things<00:08:20.409> like<00:08:20.560> skip<00:08:21.189> checks<00:08:21.490> if<00:08:21.879> you<00:08:22.659> know 00:08:22.740 --> 00:08:22.750 align:start position:0% do things like skip checks if you know 00:08:22.750 --> 00:08:24.959 align:start position:0% do things like skip checks if you know for<00:08:22.960> example<00:08:23.020> this<00:08:23.349> is<00:08:23.500> an<00:08:23.620> age<00:08:23.770> range<00:08:24.039> we 00:08:24.959 --> 00:08:24.969 align:start position:0% for example this is an age range we 00:08:24.969 --> 00:08:25.950 align:start position:0% for example this is an age range we don't<00:08:25.120> need<00:08:25.240> to<00:08:25.300> do<00:08:25.419> this<00:08:25.509> middle<00:08:25.779> check 00:08:25.950 --> 00:08:25.960 align:start position:0% don't need to do this middle check 00:08:25.960 --> 00:08:28.490 align:start position:0% don't need to do this middle check anymore<00:08:26.199> and<00:08:26.649> we<00:08:26.860> can<00:08:26.889> also<00:08:27.189> recontextualize 00:08:28.490 --> 00:08:28.500 align:start position:0% anymore and we can also recontextualize 00:08:28.500 --> 00:08:32.870 align:start position:0% anymore and we can also recontextualize responses<00:08:29.500> back<00:08:29.680> so<00:08:30.129> this<00:08:30.839> bottom<00:08:31.839> writes 00:08:32.870 --> 00:08:32.880 align:start position:0% responses back so this bottom writes 00:08:32.880 --> 00:08:34.829 align:start position:0% responses back so this bottom writes image<00:08:33.880> where<00:08:34.180> we<00:08:34.209> have<00:08:34.419> the<00:08:34.510> little<00:08:34.690> graph 00:08:34.829 --> 00:08:34.839 align:start position:0% image where we have the little graph 00:08:34.839 --> 00:08:37.230 align:start position:0% image where we have the little graph saying<00:08:35.199> you<00:08:35.409> know<00:08:35.500> this<00:08:35.709> is<00:08:35.890> in<00:08:36.760> a<00:08:36.820> certain 00:08:37.230 --> 00:08:37.240 align:start position:0% saying you know this is in a certain 00:08:37.240 --> 00:08:39.689 align:start position:0% saying you know this is in a certain range<00:08:37.769> the<00:08:38.769> further<00:08:38.979> down<00:08:39.130> the<00:08:39.310> call<00:08:39.459> stack 00:08:39.689 --> 00:08:39.699 align:start position:0% range the further down the call stack 00:08:39.699 --> 00:08:42.569 align:start position:0% range the further down the call stack you<00:08:39.849> get<00:08:40.089> it<00:08:40.390> you<00:08:41.380> tend<00:08:41.680> to<00:08:41.800> lose<00:08:42.070> context 00:08:42.569 --> 00:08:42.579 align:start position:0% you get it you tend to lose context 00:08:42.579 --> 00:08:44.159 align:start position:0% you get it you tend to lose context about<00:08:42.640> the<00:08:42.760> broad<00:08:43.029> picture<00:08:43.269> right<00:08:43.870> you<00:08:44.050> go 00:08:44.159 --> 00:08:44.169 align:start position:0% about the broad picture right you go 00:08:44.169 --> 00:08:46.949 align:start position:0% about the broad picture right you go from<00:08:44.380> the<00:08:44.529> forest<00:08:45.160> to<00:08:45.370> the<00:08:45.399> trees<00:08:45.699> and<00:08:46.060> as<00:08:46.660> that 00:08:46.949 --> 00:08:46.959 align:start position:0% from the forest to the trees and as that 00:08:46.959 --> 00:08:48.329 align:start position:0% from the forest to the trees and as that propagates<00:08:47.410> back<00:08:47.620> up<00:08:47.829> you<00:08:47.980> may<00:08:48.069> want<00:08:48.279> to 00:08:48.329 --> 00:08:48.339 align:start position:0% propagates back up you may want to 00:08:48.339 --> 00:08:49.559 align:start position:0% propagates back up you may want to recontextualize<00:08:48.610> with<00:08:49.180> something<00:08:49.420> that's 00:08:49.559 --> 00:08:49.569 align:start position:0% recontextualize with something that's 00:08:49.569 --> 00:08:52.290 align:start position:0% recontextualize with something that's more<00:08:49.720> about<00:08:49.870> your<00:08:50.140> specific<00:08:50.410> use<00:08:50.769> case<00:08:51.060> so<00:08:52.060> in 00:08:52.290 --> 00:08:52.300 align:start position:0% more about your specific use case so in 00:08:52.300 --> 00:08:53.400 align:start position:0% more about your specific use case so in this<00:08:52.420> case<00:08:52.630> we<00:08:52.779> go<00:08:52.899> from 00:08:53.400 --> 00:08:53.410 align:start position:0% this case we go from 00:08:53.410 --> 00:08:55.920 align:start position:0% this case we go from change<00:08:53.529> logic<00:08:54.040> to<00:08:54.399> permission<00:08:55.060> logic<00:08:55.480> to 00:08:55.920 --> 00:08:55.930 align:start position:0% change logic to permission logic to 00:08:55.930 --> 00:09:00.960 align:start position:0% change logic to permission logic to something<00:08:56.740> comparable<00:08:57.009> within<00:08:57.339> ERC<00:08:57.639> 20<00:08:59.970> we're 00:09:00.960 --> 00:09:00.970 align:start position:0% something comparable within ERC 20 we're 00:09:00.970 --> 00:09:02.579 align:start position:0% something comparable within ERC 20 we're very<00:09:01.120> focused<00:09:01.269> on<00:09:01.569> developer<00:09:02.139> experience 00:09:02.579 --> 00:09:02.589 align:start position:0% very focused on developer experience 00:09:02.589 --> 00:09:05.400 align:start position:0% very focused on developer experience design<00:09:03.569> we<00:09:04.569> need<00:09:04.600> to<00:09:04.870> have<00:09:04.990> a<00:09:05.019> very<00:09:05.259> low 00:09:05.400 --> 00:09:05.410 align:start position:0% design we need to have a very low 00:09:05.410 --> 00:09:07.139 align:start position:0% design we need to have a very low cognitive<00:09:05.649> load<00:09:06.129> make<00:09:06.519> this<00:09:06.639> not<00:09:06.819> hard<00:09:07.089> for 00:09:07.139 --> 00:09:07.149 align:start position:0% cognitive load make this not hard for 00:09:07.149 --> 00:09:10.050 align:start position:0% cognitive load make this not hard for people<00:09:07.509> to<00:09:07.600> use<00:09:07.810> and<00:09:08.740> easy<00:09:09.040> for<00:09:09.399> developers<00:09:09.699> to 00:09:10.050 --> 00:09:10.060 align:start position:0% people to use and easy for developers to 00:09:10.060 --> 00:09:12.319 align:start position:0% people to use and easy for developers to meet<00:09:10.269> to<00:09:10.569> communicate<00:09:11.170> with<00:09:11.290> each<00:09:11.410> other<00:09:11.529> I 00:09:12.319 --> 00:09:12.329 align:start position:0% meet to communicate with each other I 00:09:12.329 --> 00:09:14.100 align:start position:0% meet to communicate with each other I would<00:09:13.329> do<00:09:13.420> this<00:09:13.509> by<00:09:13.660> adding<00:09:13.810> a<00:09:13.990> lot<00:09:14.079> of 00:09:14.100 --> 00:09:14.110 align:start position:0% would do this by adding a lot of 00:09:14.110 --> 00:09:15.960 align:start position:0% would do this by adding a lot of structure<00:09:14.529> which<00:09:15.189> means<00:09:15.339> that<00:09:15.519> you<00:09:15.639> have<00:09:15.759> less 00:09:15.960 --> 00:09:15.970 align:start position:0% structure which means that you have less 00:09:15.970 --> 00:09:20.040 align:start position:0% structure which means that you have less memorization<00:09:17.069> fewer<00:09:18.120> lookups<00:09:19.120> and<00:09:19.389> your<00:09:19.689> code 00:09:20.040 --> 00:09:20.050 align:start position:0% memorization fewer lookups and your code 00:09:20.050 --> 00:09:23.069 align:start position:0% memorization fewer lookups and your code can<00:09:20.529> help<00:09:20.980> you<00:09:21.129> out<00:09:21.279> a<00:09:21.310> lot<00:09:21.519> more<00:09:21.699> because<00:09:22.079> you 00:09:23.069 --> 00:09:23.079 align:start position:0% can help you out a lot more because you 00:09:23.079 --> 00:09:25.019 align:start position:0% can help you out a lot more because you can<00:09:23.230> decompose<00:09:23.649> what<00:09:23.860> the<00:09:23.949> code<00:09:24.100> is<00:09:24.129> and<00:09:24.430> make 00:09:25.019 --> 00:09:25.029 align:start position:0% can decompose what the code is and make 00:09:25.029 --> 00:09:29.280 align:start position:0% can decompose what the code is and make smart<00:09:25.750> decisions<00:09:25.779> based<00:09:26.319> on<00:09:26.470> that<00:09:27.779> we<00:09:28.779> have<00:09:29.019> a 00:09:29.280 --> 00:09:29.290 align:start position:0% smart decisions based on that we have a 00:09:29.290 --> 00:09:32.340 align:start position:0% smart decisions based on that we have a human<00:09:30.069> readable<00:09:30.600> code<00:09:31.600> helpers<00:09:32.079> in<00:09:32.290> the 00:09:32.340 --> 00:09:32.350 align:start position:0% human readable code helpers in the 00:09:32.350 --> 00:09:35.639 align:start position:0% human readable code helpers in the library<00:09:33.300> it<00:09:34.300> is<00:09:34.480> compatible<00:09:35.139> with<00:09:35.319> existing 00:09:35.639 --> 00:09:35.649 align:start position:0% library it is compatible with existing 00:09:35.649 --> 00:09:39.300 align:start position:0% library it is compatible with existing patterns<00:09:36.720> is<00:09:37.720> fully<00:09:38.079> compatible<00:09:38.350> with<00:09:38.589> revert 00:09:39.300 --> 00:09:39.310 align:start position:0% patterns is fully compatible with revert 00:09:39.310 --> 00:09:41.160 align:start position:0% patterns is fully compatible with revert for<00:09:39.610> example<00:09:40.029> so<00:09:40.449> you<00:09:40.540> don't<00:09:40.720> it's<00:09:40.930> not<00:09:40.990> an 00:09:41.160 --> 00:09:41.170 align:start position:0% for example so you don't it's not an 00:09:41.170 --> 00:09:45.629 align:start position:0% for example so you don't it's not an either/or<00:09:41.560> distinction<00:09:42.779> and<00:09:44.459> let's<00:09:45.459> talk<00:09:45.579> a 00:09:45.629 --> 00:09:45.639 align:start position:0% either/or distinction and let's talk a 00:09:45.639 --> 00:09:46.980 align:start position:0% either/or distinction and let's talk a little<00:09:45.699> bit<00:09:45.850> about<00:09:45.939> the<00:09:46.240> structure<00:09:46.720> in<00:09:46.899> the 00:09:46.980 --> 00:09:46.990 align:start position:0% little bit about the structure in the 00:09:46.990 --> 00:09:52.100 align:start position:0% little bit about the structure in the layout<00:09:48.449> so<00:09:49.449> a<00:09:50.079> nibble<00:09:50.560> is<00:09:50.920> a<00:09:51.279> half<00:09:51.670> byte 00:09:52.100 --> 00:09:52.110 align:start position:0% layout so a nibble is a half byte 00:09:52.110 --> 00:09:54.210 align:start position:0% layout so a nibble is a half byte because<00:09:53.110> programmers<00:09:53.439> in<00:09:53.769> the<00:09:53.860> seventies 00:09:54.210 --> 00:09:54.220 align:start position:0% because programmers in the seventies 00:09:54.220 --> 00:09:55.829 align:start position:0% because programmers in the seventies like<00:09:54.399> the<00:09:54.490> puns 00:09:55.829 --> 00:09:55.839 align:start position:0% like the puns 00:09:55.839 --> 00:10:01.579 align:start position:0% like the puns so<00:09:56.829> here's<00:09:57.600> hex<00:09:58.600> 41<00:09:59.550> breaks<00:10:00.550> out<00:10:00.759> like<00:10:00.939> this 00:10:01.579 --> 00:10:01.589 align:start position:0% so here's hex 41 breaks out like this 00:10:01.589 --> 00:10:06.540 align:start position:0% so here's hex 41 breaks out like this the<00:10:02.589> upper<00:10:03.519> nibble<00:10:03.790> is<00:10:04.029> your<00:10:04.420> category<00:10:05.079> so 00:10:06.540 --> 00:10:06.550 align:start position:0% the upper nibble is your category so 00:10:06.550 --> 00:10:08.900 align:start position:0% the upper nibble is your category so [Music] 00:10:08.900 --> 00:10:08.910 align:start position:0% [Music] 00:10:08.910 --> 00:10:11.610 align:start position:0% [Music] things<00:10:09.910> like<00:10:10.149> you<00:10:10.930> know<00:10:11.019> this<00:10:11.110> is<00:10:11.259> time-based 00:10:11.610 --> 00:10:11.620 align:start position:0% things like you know this is time-based 00:10:11.620 --> 00:10:14.280 align:start position:0% things like you know this is time-based logic<00:10:11.980> or<00:10:12.130> as<00:10:12.220> an<00:10:12.370> authorized<00:10:13.029> ation<00:10:13.269> etc<00:10:13.750> the 00:10:14.280 --> 00:10:14.290 align:start position:0% logic or as an authorized ation etc the 00:10:14.290 --> 00:10:14.579 align:start position:0% logic or as an authorized ation etc the lower 00:10:14.579 --> 00:10:14.589 align:start position:0% lower 00:10:14.589 --> 00:10:19.319 align:start position:0% lower nibble<00:10:15.040> is<00:10:15.220> the<00:10:15.399> reason<00:10:16.829> which<00:10:17.829> is<00:10:18.240> you<00:10:19.240> know 00:10:19.319 --> 00:10:19.329 align:start position:0% nibble is the reason which is you know 00:10:19.329 --> 00:10:21.420 align:start position:0% nibble is the reason which is you know this<00:10:19.870> passed<00:10:20.079> this<00:10:20.410> fail<00:10:20.649> are<00:10:20.949> we<00:10:21.069> waiting<00:10:21.370> on 00:10:21.420 --> 00:10:21.430 align:start position:0% this passed this fail are we waiting on 00:10:21.430 --> 00:10:24.420 align:start position:0% this passed this fail are we waiting on somebody<00:10:21.759> else<00:10:22.470> is<00:10:23.470> somebody<00:10:23.829> waiting<00:10:23.949> on<00:10:24.220> you 00:10:24.420 --> 00:10:24.430 align:start position:0% somebody else is somebody waiting on you 00:10:24.430 --> 00:10:32.249 align:start position:0% somebody else is somebody waiting on you etc<00:10:27.509> and<00:10:29.939> we<00:10:30.939> get<00:10:31.089> this<00:10:31.209> extra<00:10:31.540> nice<00:10:31.779> property 00:10:32.249 --> 00:10:32.259 align:start position:0% etc and we get this extra nice property 00:10:32.259 --> 00:10:36.120 align:start position:0% etc and we get this extra nice property of<00:10:32.290> the<00:10:32.889> general<00:10:33.430> category<00:10:34.300> zero<00:10:34.899> is<00:10:35.230> the<00:10:35.949> same 00:10:36.120 --> 00:10:36.130 align:start position:0% of the general category zero is the same 00:10:36.130 --> 00:10:40.650 align:start position:0% of the general category zero is the same thing<00:10:36.399> as<00:10:36.639> not<00:10:37.600> having<00:10:38.850> the<00:10:39.850> upper<00:10:39.970> nibble<00:10:40.389> at 00:10:40.650 --> 00:10:40.660 align:start position:0% thing as not having the upper nibble at 00:10:40.660 --> 00:10:43.049 align:start position:0% thing as not having the upper nibble at all<00:10:41.279> it's<00:10:42.279> just<00:10:42.430> the<00:10:42.490> same<00:10:42.670> thing<00:10:42.699> as<00:10:42.880> the 00:10:43.049 --> 00:10:43.059 align:start position:0% all it's just the same thing as the 00:10:43.059 --> 00:10:48.420 align:start position:0% all it's just the same thing as the reason<00:10:43.300> alone<00:10:46.230> so<00:10:47.230> the<00:10:47.350> code<00:10:47.500> table<00:10:47.709> if<00:10:48.339> you 00:10:48.420 --> 00:10:48.430 align:start position:0% reason alone so the code table if you 00:10:48.430 --> 00:10:51.230 align:start position:0% reason alone so the code table if you think<00:10:48.610> of<00:10:48.670> it<00:10:48.759> as<00:10:48.850> a<00:10:48.880> two-dimensional<00:10:50.160> grid 00:10:51.230 --> 00:10:51.240 align:start position:0% think of it as a two-dimensional grid 00:10:51.240 --> 00:10:54.389 align:start position:0% think of it as a two-dimensional grid it's<00:10:52.240> like<00:10:52.420> this<00:10:52.569> the<00:10:53.220> columns<00:10:54.220> are 00:10:54.389 --> 00:10:54.399 align:start position:0% it's like this the columns are 00:10:54.399 --> 00:10:59.939 align:start position:0% it's like this the columns are categories<00:10:54.970> and<00:10:56.639> the<00:10:57.639> reasons<00:10:58.000> are<00:10:58.180> rows<00:10:58.949> it 00:10:59.939 --> 00:10:59.949 align:start position:0% categories and the reasons are rows it 00:10:59.949 --> 00:11:03.389 align:start position:0% categories and the reasons are rows it makes<00:11:00.430> it<00:11:00.519> very<00:11:00.579> easy<00:11:00.699> to<00:11:00.910> look<00:11:01.149> up<00:11:01.709> a<00:11:02.709> code 00:11:03.389 --> 00:11:03.399 align:start position:0% makes it very easy to look up a code 00:11:03.399 --> 00:11:04.889 align:start position:0% makes it very easy to look up a code that<00:11:03.579> you're<00:11:03.699> looking<00:11:03.970> for<00:11:04.149> or<00:11:04.360> to<00:11:04.449> decompose 00:11:04.889 --> 00:11:04.899 align:start position:0% that you're looking for or to decompose 00:11:04.899 --> 00:11:06.870 align:start position:0% that you're looking for or to decompose a<00:11:04.959> code<00:11:05.290> that<00:11:05.439> you've<00:11:05.620> received<00:11:05.769> so 00:11:06.870 --> 00:11:06.880 align:start position:0% a code that you've received so 00:11:06.880 --> 00:11:08.999 align:start position:0% a code that you've received so in<00:11:07.000> this<00:11:07.149> case<00:11:07.389> we're<00:11:08.199> awaiting<00:11:08.500> and 00:11:08.999 --> 00:11:09.009 align:start position:0% in this case we're awaiting and 00:11:09.009 --> 00:11:10.470 align:start position:0% in this case we're awaiting and something<00:11:09.250> with<00:11:09.370> search<00:11:09.579> or<00:11:09.790> matching<00:11:10.089> logic 00:11:10.470 --> 00:11:10.480 align:start position:0% something with search or matching logic 00:11:10.480 --> 00:11:13.110 align:start position:0% something with search or matching logic let's<00:11:10.870> say<00:11:11.050> in<00:11:11.319> a<00:11:11.529> Dex<00:11:12.250> you're<00:11:12.610> waiting<00:11:12.880> to<00:11:12.970> be 00:11:13.110 --> 00:11:13.120 align:start position:0% let's say in a Dex you're waiting to be 00:11:13.120 --> 00:11:15.660 align:start position:0% let's say in a Dex you're waiting to be matched<00:11:13.509> in<00:11:13.720> the<00:11:13.839> order<00:11:14.079> book<00:11:14.370> that's<00:11:15.370> two 00:11:15.660 --> 00:11:15.670 align:start position:0% matched in the order book that's two 00:11:15.670 --> 00:11:15.990 align:start position:0% matched in the order book that's two three 00:11:15.990 --> 00:11:16.000 align:start position:0% three 00:11:16.000 --> 00:11:23.400 align:start position:0% three awaiting<00:11:16.420> match<00:11:21.060> here's<00:11:22.230> examples<00:11:23.230> of<00:11:23.319> some 00:11:23.400 --> 00:11:23.410 align:start position:0% awaiting match here's examples of some 00:11:23.410 --> 00:11:26.939 align:start position:0% awaiting match here's examples of some of<00:11:23.470> the<00:11:23.560> helper<00:11:24.839> helper<00:11:25.839> code<00:11:26.019> so<00:11:26.470> we<00:11:26.860> have 00:11:26.939 --> 00:11:26.949 align:start position:0% of the helper helper code so we have 00:11:26.949 --> 00:11:30.870 align:start position:0% of the helper helper code so we have enums<00:11:27.310> for<00:11:27.519> category<00:11:27.970> and<00:11:28.120> reason<00:11:29.310> ways<00:11:30.310> to<00:11:30.670> do 00:11:30.870 --> 00:11:30.880 align:start position:0% enums for category and reason ways to do 00:11:30.880 --> 00:11:32.850 align:start position:0% enums for category and reason ways to do inclusions<00:11:31.540> so<00:11:31.779> to<00:11:31.839> take<00:11:32.079> two<00:11:32.319> of<00:11:32.350> these<00:11:32.560> and 00:11:32.850 --> 00:11:32.860 align:start position:0% inclusions so to take two of these and 00:11:32.860 --> 00:11:34.949 align:start position:0% inclusions so to take two of these and stick<00:11:33.009> them<00:11:33.130> together<00:11:33.279> either<00:11:34.060> the<00:11:34.389> enum<00:11:34.720> or 00:11:34.949 --> 00:11:34.959 align:start position:0% stick them together either the enum or 00:11:34.959 --> 00:11:38.850 align:start position:0% stick them together either the enum or just<00:11:35.319> a<00:11:35.470> raw<00:11:36.160> number<00:11:36.899> and<00:11:37.899> you'll<00:11:38.319> see<00:11:38.529> the<00:11:38.649> the 00:11:38.850 --> 00:11:38.860 align:start position:0% just a raw number and you'll see the the 00:11:38.860 --> 00:11:41.430 align:start position:0% just a raw number and you'll see the the third<00:11:38.980> one<00:11:39.160> there<00:11:39.279> says<00:11:39.490> app<00:11:39.670> code<00:11:40.230> there<00:11:41.230> is<00:11:41.410> a 00:11:41.430 --> 00:11:41.440 align:start position:0% third one there says app code there is a 00:11:41.440 --> 00:11:43.400 align:start position:0% third one there says app code there is a way<00:11:41.649> of<00:11:41.680> if<00:11:42.399> you<00:11:42.610> structure<00:11:42.970> your<00:11:43.149> application 00:11:43.400 --> 00:11:43.410 align:start position:0% way of if you structure your application 00:11:43.410 --> 00:11:49.290 align:start position:0% way of if you structure your application specific<00:11:45.959> enums<00:11:47.250> in<00:11:48.250> the<00:11:48.459> same<00:11:48.670> way<00:11:48.850> as<00:11:49.060> the 00:11:49.290 --> 00:11:49.300 align:start position:0% specific enums in the same way as the 00:11:49.300 --> 00:11:52.920 align:start position:0% specific enums in the same way as the reasons<00:11:49.690> then<00:11:50.910> you<00:11:51.910> can<00:11:52.089> embed<00:11:52.360> that<00:11:52.480> in<00:11:52.690> and 00:11:52.920 --> 00:11:52.930 align:start position:0% reasons then you can embed that in and 00:11:52.930 --> 00:11:55.230 align:start position:0% reasons then you can embed that in and automatically<00:11:53.620> get<00:11:53.860> a<00:11:54.550> status<00:11:55.120> code 00:11:55.230 --> 00:11:55.240 align:start position:0% automatically get a status code 00:11:55.240 --> 00:11:57.090 align:start position:0% automatically get a status code generated<00:11:55.690> without<00:11:55.779> having<00:11:56.230> to<00:11:56.350> say<00:11:56.560> this<00:11:56.949> is 00:11:57.090 --> 00:11:57.100 align:start position:0% generated without having to say this is 00:11:57.100 --> 00:11:58.710 align:start position:0% generated without having to say this is an<00:11:57.190> application<00:11:57.310> specific<00:11:57.759> code<00:11:58.300> he<00:11:58.480> was<00:11:58.600> the 00:11:58.710 --> 00:11:58.720 align:start position:0% an application specific code he was the 00:11:58.720 --> 00:12:01.980 align:start position:0% an application specific code he was the a<00:11:58.750> at<00:11:59.079> the<00:11:59.199> beginning<00:12:00.300> you<00:12:01.300> just<00:12:01.329> use<00:12:01.750> the<00:12:01.870> app 00:12:01.980 --> 00:12:01.990 align:start position:0% a at the beginning you just use the app 00:12:01.990 --> 00:12:05.249 align:start position:0% a at the beginning you just use the app code<00:12:02.230> function<00:12:03.480> we<00:12:04.480> have<00:12:04.569> functions<00:12:04.899> to<00:12:05.050> pull 00:12:05.249 --> 00:12:05.259 align:start position:0% code function we have functions to pull 00:12:05.259 --> 00:12:07.889 align:start position:0% code function we have functions to pull apart<00:12:05.589> status<00:12:06.220> codes<00:12:06.459> so<00:12:07.180> to<00:12:07.240> decompose<00:12:07.720> them 00:12:07.889 --> 00:12:07.899 align:start position:0% apart status codes so to decompose them 00:12:07.899 --> 00:12:09.930 align:start position:0% apart status codes so to decompose them to<00:12:08.230> make<00:12:08.440> smart<00:12:08.740> decisions<00:12:08.769> on<00:12:09.310> things<00:12:09.490> so<00:12:09.850> you 00:12:09.930 --> 00:12:09.940 align:start position:0% to make smart decisions on things so you 00:12:09.940 --> 00:12:12.110 align:start position:0% to make smart decisions on things so you can<00:12:09.970> say<00:12:10.209> I'm<00:12:10.389> only<00:12:10.540> really<00:12:10.930> concerned<00:12:11.290> about 00:12:12.110 --> 00:12:12.120 align:start position:0% can say I'm only really concerned about 00:12:12.120 --> 00:12:14.189 align:start position:0% can say I'm only really concerned about authentication<00:12:13.120> everything<00:12:13.779> else<00:12:13.930> should<00:12:14.139> be 00:12:14.189 --> 00:12:14.199 align:start position:0% authentication everything else should be 00:12:14.199 --> 00:12:19.110 align:start position:0% authentication everything else should be a<00:12:14.290> fail<00:12:14.579> and<00:12:15.579> my<00:12:16.149> reason<00:12:16.540> should<00:12:16.779> be<00:12:16.839> in<00:12:18.120> you 00:12:19.110 --> 00:12:19.120 align:start position:0% a fail and my reason should be in you 00:12:19.120 --> 00:12:23.840 align:start position:0% a fail and my reason should be in you know<00:12:19.620> 0<00:12:20.620> 1<00:12:20.889> through<00:12:21.339> 0<00:12:21.699> for<00:12:21.939> range<00:12:22.509> let's<00:12:22.990> say 00:12:23.840 --> 00:12:23.850 align:start position:0% know 0 1 through 0 for range let's say 00:12:23.850 --> 00:12:26.879 align:start position:0% know 0 1 through 0 for range let's say and<00:12:24.850> we're<00:12:25.180> doing<00:12:25.449> it<00:12:25.720> you<00:12:25.870> know<00:12:25.990> playing<00:12:26.800> with 00:12:26.879 --> 00:12:26.889 align:start position:0% and we're doing it you know playing with 00:12:26.889 --> 00:12:28.980 align:start position:0% and we're doing it you know playing with masks<00:12:27.370> etc<00:12:27.759> just<00:12:28.360> to<00:12:28.449> keep<00:12:28.600> things<00:12:28.750> very 00:12:28.980 --> 00:12:28.990 align:start position:0% masks etc just to keep things very 00:12:28.990 --> 00:12:33.480 align:start position:0% masks etc just to keep things very efficient<00:12:29.910> and<00:12:31.769> again<00:12:32.769> totally<00:12:33.310> compatible 00:12:33.480 --> 00:12:33.490 align:start position:0% efficient and again totally compatible 00:12:33.490 --> 00:12:35.249 align:start position:0% efficient and again totally compatible with<00:12:33.850> require<00:12:34.209> statements<00:12:34.689> so<00:12:34.930> this<00:12:35.139> is 00:12:35.249 --> 00:12:35.259 align:start position:0% with require statements so this is 00:12:35.259 --> 00:12:38.069 align:start position:0% with require statements so this is require<00:12:35.560> okay<00:12:35.920> which<00:12:36.189> means<00:12:36.430> that<00:12:36.639> the<00:12:37.079> code 00:12:38.069 --> 00:12:38.079 align:start position:0% require okay which means that the code 00:12:38.079 --> 00:12:41.220 align:start position:0% require okay which means that the code must<00:12:38.259> end<00:12:38.500> in<00:12:38.649> a1<00:12:38.920> otherwise<00:12:39.670> it<00:12:39.910> reverts<00:12:40.230> with 00:12:41.220 --> 00:12:41.230 align:start position:0% must end in a1 otherwise it reverts with 00:12:41.230 --> 00:12:43.710 align:start position:0% must end in a1 otherwise it reverts with a<00:12:41.259> hard<00:12:41.500> coded<00:12:41.680> message<00:12:42.069> the<00:12:42.910> reason<00:12:43.120> that<00:12:43.240> in 00:12:43.710 --> 00:12:43.720 align:start position:0% a hard coded message the reason that in 00:12:43.720 --> 00:12:45.179 align:start position:0% a hard coded message the reason that in the<00:12:43.870> slide<00:12:44.050> it<00:12:44.199> says<00:12:44.350> message<00:12:44.829> and<00:12:45.040> then<00:12:45.160> a 00:12:45.179 --> 00:12:45.189 align:start position:0% the slide it says message and then a 00:12:45.189 --> 00:12:49.230 align:start position:0% the slide it says message and then a little<00:12:45.339> star<00:12:45.850> is<00:12:47.100> the<00:12:48.100> next<00:12:48.430> phase<00:12:48.610> of<00:12:48.939> this 00:12:49.230 --> 00:12:49.240 align:start position:0% little star is the next phase of this 00:12:49.240 --> 00:12:51.030 align:start position:0% little star is the next phase of this project<00:12:49.870> which<00:12:49.959> we'll<00:12:50.079> be<00:12:50.170> talking<00:12:50.319> about<00:12:50.500> in 00:12:51.030 --> 00:12:51.040 align:start position:0% project which we'll be talking about in 00:12:51.040 --> 00:12:52.999 align:start position:0% project which we'll be talking about in a<00:12:51.160> moment<00:12:51.189> we<00:12:51.939> can<00:12:52.060> do<00:12:52.149> automatic 00:12:52.999 --> 00:12:53.009 align:start position:0% a moment we can do automatic 00:12:53.009 --> 00:12:57.749 align:start position:0% a moment we can do automatic translations<00:12:54.009> in<00:12:54.279> any<00:12:54.790> language<00:12:55.480> with<00:12:56.110> no<00:12:56.759> no 00:12:57.749 --> 00:12:57.759 align:start position:0% translations in any language with no no 00:12:57.759 --> 00:13:00.600 align:start position:0% translations in any language with no no extra<00:12:58.000> code<00:12:58.149> from<00:12:58.300> the<00:12:58.449> programmer<00:12:59.459> so<00:13:00.459> let's 00:13:00.600 --> 00:13:00.610 align:start position:0% extra code from the programmer so let's 00:13:00.610 --> 00:13:08.819 align:start position:0% extra code from the programmer so let's look<00:13:00.730> at<00:13:00.910> one<00:13:01.209> example<00:13:01.920> code<00:13:02.920> flow<00:13:07.529> so<00:13:08.529> this<00:13:08.680> is 00:13:08.819 --> 00:13:08.829 align:start position:0% look at one example code flow so this is 00:13:08.829 --> 00:13:11.490 align:start position:0% look at one example code flow so this is a<00:13:08.860> Dex<00:13:09.389> you<00:13:10.389> have<00:13:10.509> a<00:13:10.540> token<00:13:10.839> which<00:13:11.170> is<00:13:11.290> the<00:13:11.380> low 00:13:11.490 --> 00:13:11.500 align:start position:0% a Dex you have a token which is the low 00:13:11.500 --> 00:13:14.490 align:start position:0% a Dex you have a token which is the low money<00:13:11.680> bag<00:13:11.860> the<00:13:12.810> exchange<00:13:13.810> in<00:13:13.930> the<00:13:13.990> middle<00:13:14.199> and 00:13:14.490 --> 00:13:14.500 align:start position:0% money bag the exchange in the middle and 00:13:14.500 --> 00:13:19.199 align:start position:0% money bag the exchange in the middle and then<00:13:14.649> the<00:13:15.209> robot<00:13:16.209> icon<00:13:16.689> is<00:13:17.079> a<00:13:17.470> proxy<00:13:18.339> for<00:13:18.790> a 00:13:19.199 --> 00:13:19.209 align:start position:0% then the robot icon is a proxy for a 00:13:19.209 --> 00:13:20.659 align:start position:0% then the robot icon is a proxy for a person 00:13:20.659 --> 00:13:20.669 align:start position:0% person 00:13:20.669 --> 00:13:22.379 align:start position:0% person interaction<00:13:21.669> interacting<00:13:21.999> with<00:13:22.119> it<00:13:22.209> let's 00:13:22.379 --> 00:13:22.389 align:start position:0% interaction interacting with it let's 00:13:22.389 --> 00:13:24.929 align:start position:0% interaction interacting with it let's say<00:13:22.479> wallet<00:13:22.809> and<00:13:23.559> we<00:13:23.679> say<00:13:23.919> I'd<00:13:24.519> like<00:13:24.699> to<00:13:24.819> buy 00:13:24.929 --> 00:13:24.939 align:start position:0% say wallet and we say I'd like to buy 00:13:24.939 --> 00:13:28.969 align:start position:0% say wallet and we say I'd like to buy some<00:13:25.299> of<00:13:25.389> the<00:13:25.479> stokin<00:13:25.839> and<00:13:26.619> that<00:13:27.039> goes<00:13:27.249> through 00:13:28.969 --> 00:13:28.979 align:start position:0% some of the stokin and that goes through 00:13:28.979 --> 00:13:32.159 align:start position:0% some of the stokin and that goes through says<00:13:29.979> hey<00:13:30.419> cashes<00:13:31.419> then<00:13:31.569> says<00:13:31.779> hey<00:13:31.899> I'll<00:13:32.019> call 00:13:32.159 --> 00:13:32.169 align:start position:0% says hey cashes then says hey I'll call 00:13:32.169 --> 00:13:33.749 align:start position:0% says hey cashes then says hey I'll call you<00:13:32.289> back<00:13:32.379> when<00:13:32.559> I'm<00:13:32.679> ready<00:13:32.709> right<00:13:33.339> don't<00:13:33.579> call 00:13:33.749 --> 00:13:33.759 align:start position:0% you back when I'm ready right don't call 00:13:33.759 --> 00:13:34.409 align:start position:0% you back when I'm ready right don't call us<00:13:33.879> we'll<00:13:33.909> call<00:13:34.089> you 00:13:34.409 --> 00:13:34.419 align:start position:0% us we'll call you 00:13:34.419 --> 00:13:37.649 align:start position:0% us we'll call you and<00:13:35.609> I<00:13:36.609> guess<00:13:36.759> propagated<00:13:37.239> back<00:13:37.329> up<00:13:37.479> to<00:13:37.569> the 00:13:37.649 --> 00:13:37.659 align:start position:0% and I guess propagated back up to the 00:13:37.659 --> 00:13:39.179 align:start position:0% and I guess propagated back up to the user<00:13:37.809> and<00:13:38.139> the<00:13:38.229> Dex<00:13:38.439> knows<00:13:38.649> that<00:13:38.769> it's<00:13:38.919> waiting 00:13:39.179 --> 00:13:39.189 align:start position:0% user and the Dex knows that it's waiting 00:13:39.189 --> 00:13:46.139 align:start position:0% user and the Dex knows that it's waiting around<00:13:42.299> some<00:13:43.299> time<00:13:43.479> goes<00:13:43.689> by<00:13:43.719> and<00:13:44.939> the<00:13:45.939> users 00:13:46.139 --> 00:13:46.149 align:start position:0% around some time goes by and the users 00:13:46.149 --> 00:13:48.119 align:start position:0% around some time goes by and the users getting<00:13:46.389> impatient<00:13:46.629> so<00:13:46.929> it<00:13:47.019> says<00:13:47.169> hey<00:13:47.349> is<00:13:48.069> that 00:13:48.119 --> 00:13:48.129 align:start position:0% getting impatient so it says hey is that 00:13:48.129 --> 00:13:50.099 align:start position:0% getting impatient so it says hey is that done<00:13:48.459> yet<00:13:48.639> we<00:13:49.119> don't<00:13:49.239> have<00:13:49.389> to<00:13:49.629> check<00:13:49.899> the 00:13:50.099 --> 00:13:50.109 align:start position:0% done yet we don't have to check the 00:13:50.109 --> 00:13:52.079 align:start position:0% done yet we don't have to check the token<00:13:50.439> we<00:13:50.619> can<00:13:50.769> just<00:13:51.009> automatically<00:13:51.849> revert 00:13:52.079 --> 00:13:52.089 align:start position:0% token we can just automatically revert 00:13:52.089 --> 00:13:53.909 align:start position:0% token we can just automatically revert and<00:13:52.209> say<00:13:52.329> no<00:13:52.509> we'll<00:13:53.499> call<00:13:53.649> you<00:13:53.769> back<00:13:53.859> when 00:13:53.909 --> 00:13:53.919 align:start position:0% and say no we'll call you back when 00:13:53.919 --> 00:13:57.239 align:start position:0% and say no we'll call you back when we're<00:13:54.159> ready<00:13:55.709> later 00:13:57.239 --> 00:13:57.249 align:start position:0% we're ready later 00:13:57.249 --> 00:13:58.679 align:start position:0% we're ready later the<00:13:57.519> token<00:13:57.729> is<00:13:57.999> now<00:13:58.239> open<00:13:58.539> for<00:13:58.629> business 00:13:58.679 --> 00:13:58.689 align:start position:0% the token is now open for business 00:13:58.689 --> 00:14:01.139 align:start position:0% the token is now open for business somebody<00:13:59.139> flips<00:13:59.649> that<00:13:59.769> bit<00:14:00.039> that<00:14:00.819> can<00:14:00.999> now 00:14:01.139 --> 00:14:01.149 align:start position:0% somebody flips that bit that can now 00:14:01.149 --> 00:14:06.509 align:start position:0% somebody flips that bit that can now talk<00:14:01.689> to<00:14:01.899> the<00:14:01.989> Dex<00:14:02.199> and<00:14:02.379> say<00:14:02.559> hey<00:14:02.799> I'm<00:14:03.669> ready<00:14:05.519> it 00:14:06.509 --> 00:14:06.519 align:start position:0% talk to the Dex and say hey I'm ready it 00:14:06.519 --> 00:14:08.099 align:start position:0% talk to the Dex and say hey I'm ready it can<00:14:06.579> then<00:14:06.819> say<00:14:06.999> bye<00:14:07.149> for<00:14:07.209> all<00:14:07.779> of<00:14:08.019> these 00:14:08.099 --> 00:14:08.109 align:start position:0% can then say bye for all of these 00:14:08.109 --> 00:14:10.709 align:start position:0% can then say bye for all of these different<00:14:08.489> users<00:14:09.489> because<00:14:09.999> it<00:14:10.149> still<00:14:10.389> hasn't 00:14:10.709 --> 00:14:10.719 align:start position:0% different users because it still hasn't 00:14:10.719 --> 00:14:12.839 align:start position:0% different users because it still hasn't heard<00:14:10.989> a<00:14:11.139> cancel<00:14:11.559> order<00:14:11.919> on<00:14:12.099> them<00:14:12.309> it<00:14:12.519> says<00:14:12.669> yep 00:14:12.839 --> 00:14:12.849 align:start position:0% heard a cancel order on them it says yep 00:14:12.849 --> 00:14:14.359 align:start position:0% heard a cancel order on them it says yep cool<00:14:13.329> that's<00:14:13.539> a<00:14:13.599> greeting<00:14:13.749> completed 00:14:14.359 --> 00:14:14.369 align:start position:0% cool that's a greeting completed 00:14:14.369 --> 00:14:18.089 align:start position:0% cool that's a greeting completed propagates<00:14:15.369> that<00:14:15.519> back<00:14:15.669> to<00:14:15.819> the<00:14:15.909> user<00:14:15.939> and<00:14:17.099> the 00:14:18.089 --> 00:14:18.099 align:start position:0% propagates that back to the user and the 00:14:18.099 --> 00:14:19.849 align:start position:0% propagates that back to the user and the user<00:14:18.129> can<00:14:18.789> be<00:14:18.819> alerted<00:14:19.209> with<00:14:19.299> a<00:14:19.359> message 00:14:19.849 --> 00:14:19.859 align:start position:0% user can be alerted with a message 00:14:19.859 --> 00:14:26.339 align:start position:0% user can be alerted with a message directly<00:14:20.859> in<00:14:21.069> their<00:14:21.729> wallet<00:14:25.049> so<00:14:26.049> I<00:14:26.109> believed 00:14:26.339 --> 00:14:26.349 align:start position:0% directly in their wallet so I believed 00:14:26.349 --> 00:14:28.139 align:start position:0% directly in their wallet so I believed it<00:14:26.439> too<00:14:26.499> a<00:14:26.529> few<00:14:26.619> times<00:14:26.949> now<00:14:27.149> translations 00:14:28.139 --> 00:14:28.149 align:start position:0% it too a few times now translations 00:14:28.149 --> 00:14:32.339 align:start position:0% it too a few times now translations because<00:14:28.959> we<00:14:29.079> have<00:14:29.259> one<00:14:29.559> byte<00:14:29.799> 256<00:14:30.699> codes<00:14:31.349> that 00:14:32.339 --> 00:14:32.349 align:start position:0% because we have one byte 256 codes that 00:14:32.349 --> 00:14:40.529 align:start position:0% because we have one byte 256 codes that is<00:14:32.709> a<00:14:32.979> reasonable<00:14:33.429> number<00:14:33.459> to<00:14:33.789> translate<00:14:39.539> so 00:14:40.529 --> 00:14:40.539 align:start position:0% is a reasonable number to translate so 00:14:40.539 --> 00:14:43.079 align:start position:0% is a reasonable number to translate so we<00:14:40.659> have<00:14:40.779> a<00:14:40.989> theory<00:14:41.289> my<00:14:41.499> general-purpose<00:14:42.089> code 00:14:43.079 --> 00:14:43.089 align:start position:0% we have a theory my general-purpose code 00:14:43.089 --> 00:14:46.429 align:start position:0% we have a theory my general-purpose code to<00:14:43.239> human<00:14:43.539> translations<00:14:44.079> in<00:14:44.529> any<00:14:45.189> language 00:14:46.429 --> 00:14:46.439 align:start position:0% to human translations in any language 00:14:46.439 --> 00:14:49.559 align:start position:0% to human translations in any language anybody<00:14:47.439> can<00:14:47.799> create<00:14:48.249> translation<00:14:48.909> and<00:14:49.179> you 00:14:49.559 --> 00:14:49.569 align:start position:0% anybody can create translation and you 00:14:49.569 --> 00:14:51.479 align:start position:0% anybody can create translation and you can<00:14:49.720> use<00:14:49.899> whichever<00:14:50.289> translation<00:14:51.189> you<00:14:51.279> like 00:14:51.479 --> 00:14:51.489 align:start position:0% can use whichever translation you like 00:14:51.489 --> 00:14:53.479 align:start position:0% can use whichever translation you like so<00:14:51.939> this<00:14:52.059> is<00:14:52.179> a<00:14:52.209> bring<00:14:52.419> your<00:14:52.449> own<00:14:52.629> translation 00:14:53.479 --> 00:14:53.489 align:start position:0% so this is a bring your own translation 00:14:53.489 --> 00:14:57.419 align:start position:0% so this is a bring your own translation situation<00:14:54.659> or<00:14:55.659> you<00:14:55.959> can<00:14:56.079> use<00:14:56.169> one<00:14:56.379> of<00:14:56.409> the<00:14:56.649> in 00:14:57.419 --> 00:14:57.429 align:start position:0% situation or you can use one of the in 00:14:57.429 --> 00:14:59.129 align:start position:0% situation or you can use one of the in big<00:14:57.819> scare<00:14:58.059> quotes<00:14:58.179> official<00:14:58.720> ones<00:14:58.899> that 00:14:59.129 --> 00:14:59.139 align:start position:0% big scare quotes official ones that 00:14:59.139 --> 00:15:01.949 align:start position:0% big scare quotes official ones that we're<00:14:59.229> producing<00:15:00.269> create<00:15:01.269> your<00:15:01.419> own<00:15:01.599> share 00:15:01.949 --> 00:15:01.959 align:start position:0% we're producing create your own share 00:15:01.959 --> 00:15:03.210 align:start position:0% we're producing create your own share them<00:15:02.109> with<00:15:02.139> your<00:15:02.289> friends<00:15:02.409> write<00:15:02.919> lists<00:15:03.159> of 00:15:03.210 --> 00:15:03.220 align:start position:0% them with your friends write lists of 00:15:03.220 --> 00:15:08.029 align:start position:0% them with your friends write lists of curations<00:15:04.470> you<00:15:05.470> know<00:15:05.559> etc<00:15:06.189> make<00:15:06.970> an<00:15:07.089> emoji<00:15:07.299> one 00:15:08.029 --> 00:15:08.039 align:start position:0% curations you know etc make an emoji one 00:15:08.039 --> 00:15:11.519 align:start position:0% curations you know etc make an emoji one it's<00:15:09.039> all<00:15:09.220> in<00:15:09.429> utf-8<00:15:10.059> and<00:15:10.419> we<00:15:11.409> are 00:15:11.519 --> 00:15:11.529 align:start position:0% it's all in utf-8 and we are 00:15:11.529 --> 00:15:13.499 align:start position:0% it's all in utf-8 and we are standardizing<00:15:12.099> on<00:15:12.429> printf<00:15:12.909> style<00:15:13.149> template 00:15:13.499 --> 00:15:13.509 align:start position:0% standardizing on printf style template 00:15:13.509 --> 00:15:15.899 align:start position:0% standardizing on printf style template strings<00:15:13.809> doing<00:15:14.799> string<00:15:15.220> interpolation<00:15:15.399> on 00:15:15.899 --> 00:15:15.909 align:start position:0% strings doing string interpolation on 00:15:15.909 --> 00:15:24.379 align:start position:0% strings doing string interpolation on chain<00:15:16.329> is<00:15:16.569> very<00:15:16.749> expensive<00:15:17.609> but<00:15:19.709> the<00:15:20.709> ERC<00:15:21.549> 1444 00:15:24.379 --> 00:15:24.389 align:start position:0% 00:15:24.389 --> 00:15:27.059 align:start position:0% specifies<00:15:25.389> doing<00:15:25.659> this<00:15:25.809> in<00:15:26.259> the<00:15:26.409> clients<00:15:26.859> so 00:15:27.059 --> 00:15:27.069 align:start position:0% specifies doing this in the clients so 00:15:27.069 --> 00:15:30.210 align:start position:0% specifies doing this in the clients so there's<00:15:27.339> a<00:15:27.419> standard<00:15:28.419> way<00:15:28.569> of<00:15:28.799> returning<00:15:29.799> up 00:15:30.210 --> 00:15:30.220 align:start position:0% there's a standard way of returning up 00:15:30.220 --> 00:15:32.849 align:start position:0% there's a standard way of returning up to<00:15:30.519> the<00:15:30.609> client<00:15:30.939> to<00:15:31.409> the<00:15:32.409> wallet<00:15:32.679> or<00:15:32.799> the 00:15:32.849 --> 00:15:32.859 align:start position:0% to the client to the wallet or the 00:15:32.859 --> 00:15:34.050 align:start position:0% to the client to the wallet or the clients 00:15:34.050 --> 00:15:34.060 align:start position:0% clients 00:15:34.060 --> 00:15:35.550 align:start position:0% clients the<00:15:34.180> template<00:15:34.480> string<00:15:34.750> and<00:15:34.960> the<00:15:35.080> arguments 00:15:35.550 --> 00:15:35.560 align:start position:0% the template string and the arguments 00:15:35.560 --> 00:15:39.950 align:start position:0% the template string and the arguments and<00:15:35.740> then<00:15:35.950> you<00:15:36.460> can<00:15:36.580> do<00:15:36.670> that<00:15:36.760> all<00:15:36.970> in<00:15:37.330> the<00:15:37.450> UI 00:15:39.950 --> 00:15:39.960 align:start position:0% 00:15:39.960 --> 00:15:42.870 align:start position:0% revert<00:15:40.960> over<00:15:41.380> the<00:15:41.470> last<00:15:41.590> year<00:15:41.980> the<00:15:42.580> beginning 00:15:42.870 --> 00:15:42.880 align:start position:0% revert over the last year the beginning 00:15:42.880 --> 00:15:44.910 align:start position:0% revert over the last year the beginning of<00:15:42.970> the<00:15:43.090> year<00:15:43.240> you<00:15:44.230> really<00:15:44.500> just<00:15:44.620> gotten<00:15:44.830> out 00:15:44.910 --> 00:15:44.920 align:start position:0% of the year you really just gotten out 00:15:44.920 --> 00:15:45.570 align:start position:0% of the year you really just gotten out of<00:15:44.980> gas 00:15:45.570 --> 00:15:45.580 align:start position:0% of gas 00:15:45.580 --> 00:15:49.410 align:start position:0% of gas error<00:15:45.910> which<00:15:46.510> was<00:15:46.630> not<00:15:46.780> very<00:15:46.810> helpful<00:15:48.420> some 00:15:49.410 --> 00:15:49.420 align:start position:0% error which was not very helpful some 00:15:49.420 --> 00:15:51.210 align:start position:0% error which was not very helpful some time<00:15:49.570> went<00:15:49.750> on<00:15:49.870> and<00:15:50.020> we<00:15:50.110> gots<00:15:50.290> revert<00:15:51.100> with 00:15:51.210 --> 00:15:51.220 align:start position:0% time went on and we gots revert with 00:15:51.220 --> 00:15:54.030 align:start position:0% time went on and we gots revert with reason<00:15:51.580> so<00:15:51.940> you<00:15:52.000> can<00:15:52.180> hard<00:15:52.420> code<00:15:52.480> a<00:15:53.020> message 00:15:54.030 --> 00:15:54.040 align:start position:0% reason so you can hard code a message 00:15:54.040 --> 00:15:56.100 align:start position:0% reason so you can hard code a message typically<00:15:54.910> in<00:15:55.090> English<00:15:55.450> I've<00:15:55.690> also<00:15:55.840> seen 00:15:56.100 --> 00:15:56.110 align:start position:0% typically in English I've also seen 00:15:56.110 --> 00:15:59.190 align:start position:0% typically in English I've also seen Chinese<00:15:57.510> that<00:15:58.510> you<00:15:58.780> know<00:15:58.870> in<00:15:58.960> this<00:15:59.050> case 00:15:59.190 --> 00:15:59.200 align:start position:0% Chinese that you know in this case 00:15:59.200 --> 00:16:02.220 align:start position:0% Chinese that you know in this case player<00:15:59.560> doesn't<00:15:59.920> exist<00:16:00.310> that's<00:16:01.090> great<00:16:01.930> but 00:16:02.220 --> 00:16:02.230 align:start position:0% player doesn't exist that's great but 00:16:02.230 --> 00:16:03.780 align:start position:0% player doesn't exist that's great but not<00:16:02.350> everybody<00:16:02.710> speaks<00:16:02.830> English<00:16:03.010> especially 00:16:03.780 --> 00:16:03.790 align:start position:0% not everybody speaks English especially 00:16:03.790 --> 00:16:06.560 align:start position:0% not everybody speaks English especially if<00:16:04.090> you<00:16:04.150> want<00:16:04.330> to<00:16:04.390> make<00:16:04.510> this<00:16:04.690> a<00:16:04.870> truly<00:16:05.350> global 00:16:06.560 --> 00:16:06.570 align:start position:0% if you want to make this a truly global 00:16:06.570 --> 00:16:10.560 align:start position:0% if you want to make this a truly global system<00:16:07.570> usable<00:16:07.990> for<00:16:08.170> anyone<00:16:09.240> this<00:16:10.240> needs<00:16:10.480> to 00:16:10.560 --> 00:16:10.570 align:start position:0% system usable for anyone this needs to 00:16:10.570 --> 00:16:14.460 align:start position:0% system usable for anyone this needs to be<00:16:10.920> localized<00:16:11.920> internationalized<00:16:13.050> so<00:16:14.050> using 00:16:14.460 --> 00:16:14.470 align:start position:0% be localized internationalized so using 00:16:14.470 --> 00:16:17.070 align:start position:0% be localized internationalized so using this<00:16:14.590> system<00:16:14.830> and<00:16:15.550> then<00:16:16.270> an<00:16:16.360> integration<00:16:16.870> into 00:16:17.070 --> 00:16:17.080 align:start position:0% this system and then an integration into 00:16:17.080 --> 00:16:19.080 align:start position:0% this system and then an integration into a<00:16:17.110> wallet<00:16:17.490> you<00:16:18.490> can<00:16:18.640> have<00:16:18.730> something<00:16:18.940> like 00:16:19.080 --> 00:16:19.090 align:start position:0% a wallet you can have something like 00:16:19.090 --> 00:16:22.710 align:start position:0% a wallet you can have something like this<00:16:20.010> where<00:16:21.010> it's<00:16:21.340> not<00:16:21.550> just<00:16:21.610> that<00:16:22.330> has<00:16:22.480> failed 00:16:22.710 --> 00:16:22.720 align:start position:0% this where it's not just that has failed 00:16:22.720 --> 00:16:24.900 align:start position:0% this where it's not just that has failed and<00:16:23.140> doesn't<00:16:23.560> just<00:16:23.710> tell<00:16:23.830> you<00:16:23.980> why<00:16:24.250> it<00:16:24.610> does<00:16:24.760> it 00:16:24.900 --> 00:16:24.910 align:start position:0% and doesn't just tell you why it does it 00:16:24.910 --> 00:16:28.620 align:start position:0% and doesn't just tell you why it does it in<00:16:25.150> whichever<00:16:26.050> language<00:16:26.200> and<00:16:27.450> contextual<00:16:28.450> to 00:16:28.620 --> 00:16:28.630 align:start position:0% in whichever language and contextual to 00:16:28.630 --> 00:16:32.820 align:start position:0% in whichever language and contextual to your<00:16:28.780> specific<00:16:29.170> use<00:16:29.290> case<00:16:31.560> so<00:16:32.560> how<00:16:32.650> do<00:16:32.710> we 00:16:32.820 --> 00:16:32.830 align:start position:0% your specific use case so how do we 00:16:32.830 --> 00:16:35.100 align:start position:0% your specific use case so how do we actually<00:16:32.980> make<00:16:33.250> that<00:16:33.430> happen<00:16:33.840> this<00:16:34.840> is<00:16:34.900> the 00:16:35.100 --> 00:16:35.110 align:start position:0% actually make that happen this is the 00:16:35.110 --> 00:16:38.250 align:start position:0% actually make that happen this is the broad<00:16:35.620> architecture<00:16:36.570> you<00:16:37.570> have<00:16:37.630> a<00:16:37.720> requester 00:16:38.250 --> 00:16:38.260 align:start position:0% broad architecture you have a requester 00:16:38.260 --> 00:16:40.200 align:start position:0% broad architecture you have a requester which<00:16:38.500> is<00:16:38.620> either<00:16:38.740> a<00:16:38.860> person<00:16:39.280> or<00:16:39.490> a<00:16:39.520> smart 00:16:40.200 --> 00:16:40.210 align:start position:0% which is either a person or a smart 00:16:40.210 --> 00:16:42.360 align:start position:0% which is either a person or a smart contract<00:16:40.330> a<00:16:40.960> singleton<00:16:41.740> localization 00:16:42.360 --> 00:16:42.370 align:start position:0% contract a singleton localization 00:16:42.370 --> 00:16:46.260 align:start position:0% contract a singleton localization preference<00:16:44.160> instance<00:16:45.160> on<00:16:45.430> chain<00:16:45.730> and<00:16:46.090> then<00:16:46.180> a 00:16:46.260 --> 00:16:46.270 align:start position:0% preference instance on chain and then a 00:16:46.270 --> 00:16:49.050 align:start position:0% preference instance on chain and then a number<00:16:46.480> of<00:16:46.570> localizations<00:16:47.610> so<00:16:48.610> typical 00:16:49.050 --> 00:16:49.060 align:start position:0% number of localizations so typical 00:16:49.060 --> 00:16:51.240 align:start position:0% number of localizations so typical financial<00:16:49.240> agent<00:16:49.750> flow<00:16:49.980> here<00:16:50.980> we<00:16:51.070> have<00:16:51.190> the 00:16:51.240 --> 00:16:51.250 align:start position:0% financial agent flow here we have the 00:16:51.250 --> 00:16:52.560 align:start position:0% financial agent flow here we have the user<00:16:51.430> like<00:16:51.820> you<00:16:51.910> get<00:16:52.090> something<00:16:52.300> back<00:16:52.420> in 00:16:52.560 --> 00:16:52.570 align:start position:0% user like you get something back in 00:16:52.570 --> 00:16:54.090 align:start position:0% user like you get something back in Japanese<00:16:52.930> and<00:16:53.410> they're<00:16:53.560> talking<00:16:53.710> to<00:16:53.830> a<00:16:53.890> smart 00:16:54.090 --> 00:16:54.100 align:start position:0% Japanese and they're talking to a smart 00:16:54.100 --> 00:16:57.000 align:start position:0% Japanese and they're talking to a smart contract<00:16:54.250> and<00:16:54.850> we<00:16:55.720> have<00:16:55.840> a<00:16:55.870> wallet<00:16:56.080> in<00:16:56.440> the 00:16:57.000 --> 00:16:57.010 align:start position:0% contract and we have a wallet in the 00:16:57.010 --> 00:16:59.520 align:start position:0% contract and we have a wallet in the middle<00:16:57.250> so<00:16:57.370> I'm<00:16:57.430> gonna<00:16:57.550> be<00:16:57.610> very<00:16:58.150> clear<00:16:58.530> we 00:16:59.520 --> 00:16:59.530 align:start position:0% middle so I'm gonna be very clear we 00:16:59.530 --> 00:17:01.680 align:start position:0% middle so I'm gonna be very clear we don't<00:16:59.650> have<00:16:59.830> a<00:16:59.860> meta<00:17:00.040> mask<00:17:00.250> integration<00:17:00.940> yet 00:17:01.680 --> 00:17:01.690 align:start position:0% don't have a meta mask integration yet 00:17:01.690 --> 00:17:03.450 align:start position:0% don't have a meta mask integration yet we're<00:17:02.680> going<00:17:02.830> to<00:17:02.890> be<00:17:02.950> doing<00:17:03.130> a<00:17:03.280> pull<00:17:03.430> request 00:17:03.450 --> 00:17:03.460 align:start position:0% we're going to be doing a pull request 00:17:03.460 --> 00:17:04.920 align:start position:0% we're going to be doing a pull request against<00:17:04.000> them<00:17:04.120> but<00:17:04.270> this<00:17:04.360> isn't<00:17:04.630> to<00:17:04.690> imply 00:17:04.920 --> 00:17:04.930 align:start position:0% against them but this isn't to imply 00:17:04.930 --> 00:17:07.980 align:start position:0% against them but this isn't to imply that<00:17:04.960> they're<00:17:05.520> that<00:17:06.520> this<00:17:06.730> exists<00:17:07.420> with<00:17:07.810> them 00:17:07.980 --> 00:17:07.990 align:start position:0% that they're that this exists with them 00:17:07.990 --> 00:17:08.310 align:start position:0% that they're that this exists with them today 00:17:08.310 --> 00:17:08.320 align:start position:0% today 00:17:08.320 --> 00:17:12.900 align:start position:0% today it's<00:17:09.190> just<00:17:09.340> when<00:17:10.000> we<00:17:10.090> use<00:17:10.240> the<00:17:11.520> the<00:17:12.520> emoji 00:17:12.900 --> 00:17:12.910 align:start position:0% it's just when we use the the emoji 00:17:12.910 --> 00:17:13.980 align:start position:0% it's just when we use the the emoji which<00:17:13.060> is<00:17:13.180> the<00:17:13.240> little<00:17:13.390> purse<00:17:13.600> people<00:17:13.840> gets 00:17:13.980 --> 00:17:13.990 align:start position:0% which is the little purse people gets 00:17:13.990 --> 00:17:17.240 align:start position:0% which is the little purse people gets confused<00:17:14.940> so<00:17:15.940> you<00:17:16.210> send<00:17:16.390> a<00:17:16.450> transaction<00:17:16.750> over 00:17:17.240 --> 00:17:17.250 align:start position:0% confused so you send a transaction over 00:17:17.250 --> 00:17:19.380 align:start position:0% confused so you send a transaction over that<00:17:18.250> makes<00:17:18.580> a<00:17:18.700> request<00:17:18.880> and<00:17:19.120> it's<00:17:19.240> not<00:17:19.360> a 00:17:19.380 --> 00:17:19.390 align:start position:0% that makes a request and it's not a 00:17:19.390 --> 00:17:21.300 align:start position:0% that makes a request and it's not a contract<00:17:19.750> and<00:17:20.050> then<00:17:20.200> we<00:17:20.290> get<00:17:20.410> back<00:17:20.470> a<00:17:20.800> status 00:17:21.300 --> 00:17:21.310 align:start position:0% contract and then we get back a status 00:17:21.310 --> 00:17:23.310 align:start position:0% contract and then we get back a status code<00:17:21.460> which<00:17:22.390> is<00:17:22.480> not<00:17:22.600> very<00:17:22.780> human<00:17:23.020> readable 00:17:23.310 --> 00:17:23.320 align:start position:0% code which is not very human readable 00:17:23.320 --> 00:17:27.740 align:start position:0% code which is not very human readable that<00:17:23.850> part<00:17:24.850> if<00:17:25.150> it's<00:17:25.360> a<00:17:25.510> mutating<00:17:26.140> request<00:17:27.040> and 00:17:27.740 --> 00:17:27.750 align:start position:0% that part if it's a mutating request and 00:17:27.750 --> 00:17:30.090 align:start position:0% that part if it's a mutating request and you<00:17:28.750> know<00:17:28.840> they've<00:17:29.140> been<00:17:29.170> charged<00:17:29.620> gasps<00:17:29.830> we 00:17:30.090 --> 00:17:30.100 align:start position:0% you know they've been charged gasps we 00:17:30.100 --> 00:17:32.250 align:start position:0% you know they've been charged gasps we don't<00:17:30.250> want<00:17:30.370> to<00:17:30.510> incur<00:17:31.510> a<00:17:31.540> gas<00:17:31.750> cost<00:17:32.050> for<00:17:32.230> doing 00:17:32.250 --> 00:17:32.260 align:start position:0% don't want to incur a gas cost for doing 00:17:32.260 --> 00:17:33.810 align:start position:0% don't want to incur a gas cost for doing translation<00:17:32.890> which<00:17:33.070> is<00:17:33.100> just<00:17:33.400> purely<00:17:33.700> a 00:17:33.810 --> 00:17:33.820 align:start position:0% translation which is just purely a 00:17:33.820 --> 00:17:37.170 align:start position:0% translation which is just purely a lookup<00:17:34.120> so<00:17:34.270> we<00:17:34.360> do<00:17:34.450> a<00:17:34.510> second<00:17:34.780> request<00:17:36.150> to<00:17:37.150> that 00:17:37.170 --> 00:17:37.180 align:start position:0% lookup so we do a second request to that 00:17:37.180 --> 00:17:39.120 align:start position:0% lookup so we do a second request to that singleton<00:17:37.900> it<00:17:38.110> looks<00:17:38.290> up<00:17:38.470> the<00:17:38.620> transaction 00:17:39.120 --> 00:17:39.130 align:start position:0% singleton it looks up the transaction 00:17:39.130 --> 00:17:41.220 align:start position:0% singleton it looks up the transaction origin<00:17:39.490> the<00:17:39.700> user<00:17:40.120> that's<00:17:40.720> actually<00:17:41.020> looking 00:17:41.220 --> 00:17:41.230 align:start position:0% origin the user that's actually looking 00:17:41.230 --> 00:17:44.100 align:start position:0% origin the user that's actually looking for<00:17:41.440> this 00:17:44.100 --> 00:17:44.110 align:start position:0% 00:17:44.110 --> 00:17:46.440 align:start position:0% it<00:17:44.380> looks<00:17:44.830> up<00:17:45.010> what<00:17:45.490> their<00:17:45.820> translation 00:17:46.440 --> 00:17:46.450 align:start position:0% it looks up what their translation 00:17:46.450 --> 00:17:47.549 align:start position:0% it looks up what their translation preference<00:17:46.780> is 00:17:47.549 --> 00:17:47.559 align:start position:0% preference is 00:17:47.559 --> 00:17:50.909 align:start position:0% preference is as<00:17:47.620> a<00:17:47.710> proxy<00:17:47.950> for<00:17:48.990> words<00:17:49.990> that<00:17:50.080> on<00:17:50.320> to<00:17:50.679> the 00:17:50.909 --> 00:17:50.919 align:start position:0% as a proxy for words that on to the 00:17:50.919 --> 00:17:53.789 align:start position:0% as a proxy for words that on to the correct<00:17:51.249> translation<00:17:52.529> returns<00:17:53.529> the<00:17:53.740> string 00:17:53.789 --> 00:17:53.799 align:start position:0% correct translation returns the string 00:17:53.799 --> 00:17:56.600 align:start position:0% correct translation returns the string and<00:17:54.370> that<00:17:54.700> bubbles<00:17:55.029> back<00:17:55.179> up<00:17:55.419> to<00:17:55.870> the<00:17:55.960> user<00:17:56.139> and 00:17:56.600 --> 00:17:56.610 align:start position:0% and that bubbles back up to the user and 00:17:56.610 --> 00:18:02.269 align:start position:0% and that bubbles back up to the user and then<00:17:57.610> looks<00:17:58.210> something<00:17:58.419> like<00:17:58.539> this 00:18:02.269 --> 00:18:02.279 align:start position:0% 00:18:02.279 --> 00:18:04.350 align:start position:0% translating<00:18:03.279> revert<00:18:03.610> so<00:18:03.909> let's<00:18:04.059> say<00:18:04.179> you're 00:18:04.350 --> 00:18:04.360 align:start position:0% translating revert so let's say you're 00:18:04.360 --> 00:18:07.139 align:start position:0% translating revert so let's say you're doing<00:18:05.279> developments<00:18:06.279> and<00:18:06.549> you<00:18:06.639> don't<00:18:06.850> you 00:18:07.139 --> 00:18:07.149 align:start position:0% doing developments and you don't you 00:18:07.149 --> 00:18:08.340 align:start position:0% doing developments and you don't you know<00:18:07.240> you<00:18:07.330> just<00:18:07.539> want<00:18:07.690> to<00:18:07.720> get<00:18:07.840> this<00:18:07.990> directly 00:18:08.340 --> 00:18:08.350 align:start position:0% know you just want to get this directly 00:18:08.350 --> 00:18:13.860 align:start position:0% know you just want to get this directly in<00:18:08.470> the<00:18:08.559> console<00:18:10.289> it's<00:18:11.289> pretty<00:18:11.559> similar<00:18:12.870> right 00:18:13.860 --> 00:18:13.870 align:start position:0% in the console it's pretty similar right 00:18:13.870 --> 00:18:17.430 align:start position:0% in the console it's pretty similar right do<00:18:14.049> the<00:18:14.169> thing<00:18:14.379> here's<00:18:15.100> a<00:18:15.190> transaction<00:18:16.440> then 00:18:17.430 --> 00:18:17.440 align:start position:0% do the thing here's a transaction then 00:18:17.440 --> 00:18:18.989 align:start position:0% do the thing here's a transaction then internally<00:18:18.039> to<00:18:18.129> the<00:18:18.220> smart<00:18:18.399> contract<00:18:18.549> it<00:18:18.879> says 00:18:18.989 --> 00:18:18.999 align:start position:0% internally to the smart contract it says 00:18:18.999 --> 00:18:21.749 align:start position:0% internally to the smart contract it says revert<00:18:19.299> with<00:18:19.480> this<00:18:19.779> code<00:18:20.100> so<00:18:21.100> it's<00:18:21.519> going<00:18:21.669> to 00:18:21.749 --> 00:18:21.759 align:start position:0% revert with this code so it's going to 00:18:21.759 --> 00:18:24.989 align:start position:0% revert with this code so it's going to look<00:18:21.879> up<00:18:22.029> the<00:18:22.119> string<00:18:22.619> look<00:18:23.619> at<00:18:23.740> the<00:18:23.999> the 00:18:24.989 --> 00:18:24.999 align:start position:0% look up the string look at the the 00:18:24.999 --> 00:18:29.070 align:start position:0% look up the string look at the the originator<00:18:25.480> of<00:18:25.600> the<00:18:25.899> transaction<00:18:27.929> grab<00:18:28.929> the 00:18:29.070 --> 00:18:29.080 align:start position:0% originator of the transaction grab the 00:18:29.080 --> 00:18:35.340 align:start position:0% originator of the transaction grab the text<00:18:29.259> and<00:18:29.970> back<00:18:30.970> up<00:18:31.149> it<00:18:31.269> goes<00:18:31.649> in<00:18:32.649> a<00:18:32.769> revert<00:18:34.350> so 00:18:35.340 --> 00:18:35.350 align:start position:0% text and back up it goes in a revert so 00:18:35.350 --> 00:18:37.970 align:start position:0% text and back up it goes in a revert so we<00:18:36.309> have<00:18:36.429> some<00:18:36.549> further<00:18:36.669> directions<00:18:37.179> as<00:18:37.299> well 00:18:37.970 --> 00:18:37.980 align:start position:0% we have some further directions as well 00:18:37.980 --> 00:18:43.200 align:start position:0% we have some further directions as well for<00:18:38.980> the<00:18:39.039> future<00:18:41.190> because<00:18:42.190> this<00:18:42.340> is<00:18:42.519> fairly 00:18:43.200 --> 00:18:43.210 align:start position:0% for the future because this is fairly 00:18:43.210 --> 00:18:45.509 align:start position:0% for the future because this is fairly portable<00:18:43.919> what<00:18:44.919> we<00:18:44.980> have<00:18:45.100> today<00:18:45.309> is<00:18:45.399> we<00:18:45.490> have 00:18:45.509 --> 00:18:45.519 align:start position:0% portable what we have today is we have 00:18:45.519 --> 00:18:51.299 align:start position:0% portable what we have today is we have etherium<00:18:45.970> we<00:18:46.720> have<00:18:46.990> GRC<00:18:47.710> 1066<00:18:48.340> and<00:18:49.019> 1444<00:18:50.309> which 00:18:51.299 --> 00:18:51.309 align:start position:0% etherium we have GRC 1066 and 1444 which 00:18:51.309 --> 00:18:53.970 align:start position:0% etherium we have GRC 1066 and 1444 which gives<00:18:51.549> us<00:18:51.990> translation<00:18:52.990> and<00:18:53.320> integrations 00:18:53.970 --> 00:18:53.980 align:start position:0% gives us translation and integrations 00:18:53.980 --> 00:18:58.039 align:start position:0% gives us translation and integrations with<00:18:54.129> wallets<00:18:54.519> and<00:18:54.940> gaps<00:18:55.450> and<00:18:55.779> you<00:18:56.049> know<00:18:56.139> so<00:18:56.379> on 00:18:58.039 --> 00:18:58.049 align:start position:0% with wallets and gaps and you know so on 00:18:58.049 --> 00:19:00.989 align:start position:0% with wallets and gaps and you know so on being<00:18:59.049> one<00:18:59.320> bytes<00:18:59.590> that<00:19:00.039> runs<00:19:00.429> on<00:19:00.610> every 00:19:00.989 --> 00:19:00.999 align:start position:0% being one bytes that runs on every 00:19:00.999 --> 00:19:04.529 align:start position:0% being one bytes that runs on every computer<00:19:01.450> ever<00:19:02.369> so<00:19:03.369> we<00:19:04.210> can<00:19:04.330> do<00:19:04.419> this 00:19:04.529 --> 00:19:04.539 align:start position:0% computer ever so we can do this 00:19:04.539 --> 00:19:07.889 align:start position:0% computer ever so we can do this entertain<00:19:04.929> and<00:19:05.999> do<00:19:06.999> message<00:19:07.330> passing<00:19:07.360> across 00:19:07.889 --> 00:19:07.899 align:start position:0% entertain and do message passing across 00:19:07.899 --> 00:19:10.680 align:start position:0% entertain and do message passing across to<00:19:08.289> you<00:19:09.190> know<00:19:09.249> let's<00:19:09.399> say<00:19:09.519> the<00:19:09.759> et<00:19:10.299> Cie<00:19:10.480> Peace 00:19:10.680 --> 00:19:10.690 align:start position:0% to you know let's say the et Cie Peace 00:19:10.690 --> 00:19:17.749 align:start position:0% to you know let's say the et Cie Peace Bridge<00:19:10.869> or<00:19:11.309> across<00:19:12.309> to<00:19:12.610> our<00:19:12.909> chain<00:19:13.350> etc<00:19:14.350> and 00:19:17.749 --> 00:19:17.759 align:start position:0% 00:19:17.759 --> 00:19:22.109 align:start position:0% with<00:19:18.759> the<00:19:18.909> web<00:19:19.440> because<00:19:20.440> we<00:19:20.559> can<00:19:20.679> map<00:19:21.119> 256 00:19:22.109 --> 00:19:22.119 align:start position:0% with the web because we can map 256 00:19:22.119 --> 00:19:25.169 align:start position:0% with the web because we can map 256 status<00:19:22.419> codes<00:19:22.659> into<00:19:22.869> the<00:19:23.080> 63<00:19:23.919> or<00:19:24.159> so<00:19:24.399> HTTP 00:19:25.169 --> 00:19:25.179 align:start position:0% status codes into the 63 or so HTTP 00:19:25.179 --> 00:19:27.659 align:start position:0% status codes into the 63 or so HTTP codes<00:19:25.419> that<00:19:26.200> there<00:19:26.350> are<00:19:26.499> we<00:19:27.369> can<00:19:27.399> have 00:19:27.659 --> 00:19:27.669 align:start position:0% codes that there are we can have 00:19:27.669 --> 00:19:32.730 align:start position:0% codes that there are we can have automatic<00:19:28.889> HTTP<00:19:30.450> aetherium<00:19:31.450> to<00:19:31.749> HTTP<00:19:32.559> web 00:19:32.730 --> 00:19:32.740 align:start position:0% automatic HTTP aetherium to HTTP web 00:19:32.740 --> 00:19:38.999 align:start position:0% automatic HTTP aetherium to HTTP web bridge<00:19:33.809> and<00:19:35.519> sessions<00:19:36.519> possible<00:19:37.740> sessions<00:19:38.740> or 00:19:38.999 --> 00:19:39.009 align:start position:0% bridge and sessions possible sessions or 00:19:39.009 --> 00:19:45.779 align:start position:0% bridge and sessions possible sessions or multi<00:19:39.600> transaction<00:19:40.600> sessions<00:19:40.960> as<00:19:41.110> well<00:19:44.789> so 00:19:45.779 --> 00:19:45.789 align:start position:0% multi transaction sessions as well so 00:19:45.789 --> 00:19:50.340 align:start position:0% multi transaction sessions as well so here's<00:19:46.179> a<00:19:46.740> list<00:19:47.740> of<00:19:47.830> links<00:19:49.049> awesome<00:19:50.049> thank<00:19:50.320> you 00:19:50.340 --> 00:19:50.350 align:start position:0% here's a list of links awesome thank you 00:19:50.350 --> 00:19:59.769 align:start position:0% here's a list of links awesome thank you so<00:19:50.440> much 00:19:59.769 --> 00:19:59.779 align:start position:0% 00:19:59.779 --> 00:20:01.840 align:start position:0% you