WEBVTT Kind: captions Language: en 00:00:00.560 --> 00:00:04.249 align:start position:0% hi<00:00:02.370> so<00:00:02.730> my<00:00:02.850> name's<00:00:03.030> tom<00:00:03.330> close<00:00:03.570> i<00:00:03.929> am<00:00:04.049> the 00:00:04.249 --> 00:00:04.259 align:start position:0% hi so my name's tom close i am the 00:00:04.259 --> 00:00:06.589 align:start position:0% hi so my name's tom close i am the founder<00:00:04.559> of<00:00:04.589> magma<00:00:04.979> and<00:00:05.189> we<00:00:05.759> are<00:00:06.059> a<00:00:06.089> state 00:00:06.589 --> 00:00:06.599 align:start position:0% founder of magma and we are a state 00:00:06.599 --> 00:00:09.070 align:start position:0% founder of magma and we are a state channel<00:00:06.990> research<00:00:07.499> and<00:00:07.740> development<00:00:08.189> company 00:00:09.070 --> 00:00:09.080 align:start position:0% channel research and development company 00:00:09.080 --> 00:00:12.560 align:start position:0% channel research and development company and<00:00:10.080> today<00:00:10.530> as<00:00:10.980> the<00:00:11.339> title<00:00:11.519> suggests<00:00:11.999> i<00:00:12.480> am 00:00:12.560 --> 00:00:12.570 align:start position:0% and today as the title suggests i am 00:00:12.570 --> 00:00:14.810 align:start position:0% and today as the title suggests i am going<00:00:12.780> to<00:00:12.839> be<00:00:12.929> talking<00:00:13.349> about<00:00:13.530> building<00:00:14.429> a 00:00:14.810 --> 00:00:14.820 align:start position:0% going to be talking about building a 00:00:14.820 --> 00:00:21.019 align:start position:0% going to be talking about building a state<00:00:15.269> channel<00:00:15.749> application<00:00:17.750> so<00:00:18.750> in<00:00:19.260> fact<00:00:20.029> an 00:00:21.019 --> 00:00:21.029 align:start position:0% state channel application so in fact an 00:00:21.029 --> 00:00:22.790 align:start position:0% state channel application so in fact an alternative<00:00:21.660> title<00:00:22.080> of<00:00:22.140> this<00:00:22.260> talk<00:00:22.320> could 00:00:22.790 --> 00:00:22.800 align:start position:0% alternative title of this talk could 00:00:22.800 --> 00:00:25.550 align:start position:0% alternative title of this talk could actually<00:00:22.980> be<00:00:23.310> this<00:00:23.720> we<00:00:24.720> built<00:00:24.960> a<00:00:25.080> state<00:00:25.289> up 00:00:25.550 --> 00:00:25.560 align:start position:0% actually be this we built a state up 00:00:25.560 --> 00:00:28.429 align:start position:0% actually be this we built a state up channel<00:00:26.189> application<00:00:26.759> and<00:00:27.029> we<00:00:27.839> found<00:00:28.109> it 00:00:28.429 --> 00:00:28.439 align:start position:0% channel application and we found it 00:00:28.439 --> 00:00:32.600 align:start position:0% channel application and we found it really<00:00:28.710> hard<00:00:30.650> it<00:00:31.650> turns<00:00:31.890> out<00:00:32.130> that<00:00:32.340> this<00:00:32.430> is<00:00:32.580> a 00:00:32.600 --> 00:00:32.610 align:start position:0% really hard it turns out that this is a 00:00:32.610 --> 00:00:34.460 align:start position:0% really hard it turns out that this is a pretty<00:00:32.940> accurate<00:00:33.720> description<00:00:33.900> of<00:00:34.410> the 00:00:34.460 --> 00:00:34.470 align:start position:0% pretty accurate description of the 00:00:34.470 --> 00:00:37.790 align:start position:0% pretty accurate description of the situation<00:00:35.390> so<00:00:36.390> this<00:00:36.810> talk<00:00:37.080> is<00:00:37.110> going<00:00:37.440> to<00:00:37.620> be 00:00:37.790 --> 00:00:37.800 align:start position:0% situation so this talk is going to be 00:00:37.800 --> 00:00:41.570 align:start position:0% situation so this talk is going to be partly<00:00:38.670> show<00:00:38.910> and<00:00:39.060> tell<00:00:40.250> it's<00:00:41.250> going<00:00:41.400> to<00:00:41.490> be 00:00:41.570 --> 00:00:41.580 align:start position:0% partly show and tell it's going to be 00:00:41.580 --> 00:00:45.230 align:start position:0% partly show and tell it's going to be partly<00:00:42.000> like<00:00:42.150> group<00:00:42.540> therapy<00:00:42.570> and<00:00:43.970> partly<00:00:44.970> a 00:00:45.230 --> 00:00:45.240 align:start position:0% partly like group therapy and partly a 00:00:45.240 --> 00:00:50.000 align:start position:0% partly like group therapy and partly a call<00:00:45.570> for<00:00:45.840> help<00:00:45.960> so<00:00:48.230> before<00:00:49.230> I<00:00:49.260> go<00:00:49.590> into<00:00:49.620> that 00:00:50.000 --> 00:00:50.010 align:start position:0% call for help so before I go into that 00:00:50.010 --> 00:00:52.940 align:start position:0% call for help so before I go into that let<00:00:50.610> me<00:00:51.300> tell<00:00:51.450> you<00:00:51.570> a<00:00:51.630> little<00:00:51.780> bit<00:00:52.110> more<00:00:52.470> about 00:00:52.940 --> 00:00:52.950 align:start position:0% let me tell you a little bit more about 00:00:52.950 --> 00:00:56.000 align:start position:0% let me tell you a little bit more about who<00:00:53.310> we<00:00:53.460> are<00:00:53.960> because<00:00:54.960> maybe<00:00:55.470> some<00:00:55.710> of<00:00:55.830> this<00:00:55.950> a 00:00:56.000 --> 00:00:56.010 align:start position:0% who we are because maybe some of this a 00:00:56.010 --> 00:00:57.710 align:start position:0% who we are because maybe some of this a little<00:00:56.340> bit<00:00:56.460> relevant<00:00:56.910> to<00:00:57.030> why<00:00:57.240> we<00:00:57.390> found<00:00:57.570> it 00:00:57.710 --> 00:00:57.720 align:start position:0% little bit relevant to why we found it 00:00:57.720 --> 00:00:59.390 align:start position:0% little bit relevant to why we found it hard<00:00:57.900> but<00:00:58.140> maybe<00:00:58.290> some<00:00:58.560> of<00:00:58.590> it<00:00:58.710> isn't<00:00:58.860> and<00:00:59.340> I'll 00:00:59.390 --> 00:00:59.400 align:start position:0% hard but maybe some of it isn't and I'll 00:00:59.400 --> 00:01:02.690 align:start position:0% hard but maybe some of it isn't and I'll talk<00:00:59.580> about<00:00:59.610> that<00:00:59.790> later<00:01:00.030> too<00:01:01.010> so<00:01:02.010> we<00:01:02.580> are<00:01:02.670> a 00:01:02.690 --> 00:01:02.700 align:start position:0% talk about that later too so we are a 00:01:02.700 --> 00:01:06.340 align:start position:0% talk about that later too so we are a team<00:01:03.030> of<00:01:03.390> six<00:01:04.850> researchers<00:01:05.850> and<00:01:06.119> developers 00:01:06.340 --> 00:01:06.350 align:start position:0% team of six researchers and developers 00:01:06.350 --> 00:01:10.310 align:start position:0% team of six researchers and developers so<00:01:07.350> we're<00:01:07.500> all<00:01:07.619> pretty<00:01:07.820> experienced<00:01:08.820> I<00:01:09.329> guess 00:01:10.310 --> 00:01:10.320 align:start position:0% so we're all pretty experienced I guess 00:01:10.320 --> 00:01:11.539 align:start position:0% so we're all pretty experienced I guess we've<00:01:10.500> got<00:01:10.679> like<00:01:10.890> three<00:01:10.920> or<00:01:11.219> four<00:01:11.369> people 00:01:11.539 --> 00:01:11.549 align:start position:0% we've got like three or four people 00:01:11.549 --> 00:01:14.090 align:start position:0% we've got like three or four people who've<00:01:12.030> got<00:01:12.210> like<00:01:12.390> more<00:01:12.600> than<00:01:13.049> five<00:01:13.320> five 00:01:14.090 --> 00:01:14.100 align:start position:0% who've got like more than five five 00:01:14.100 --> 00:01:15.800 align:start position:0% who've got like more than five five years<00:01:14.369> experience<00:01:14.579> developing<00:01:15.479> or 00:01:15.800 --> 00:01:15.810 align:start position:0% years experience developing or 00:01:15.810 --> 00:01:20.499 align:start position:0% years experience developing or insecurity<00:01:16.850> half<00:01:17.850> our<00:01:18.060> team<00:01:18.270> have<00:01:18.539> PhDs<00:01:19.140> but 00:01:20.499 --> 00:01:20.509 align:start position:0% insecurity half our team have PhDs but 00:01:20.509 --> 00:01:22.550 align:start position:0% insecurity half our team have PhDs but we're<00:01:21.509> all<00:01:21.659> new<00:01:21.899> to<00:01:22.020> the<00:01:22.079> blockchain 00:01:22.550 --> 00:01:22.560 align:start position:0% we're all new to the blockchain 00:01:22.560 --> 00:01:25.520 align:start position:0% we're all new to the blockchain so<00:01:23.369> it's<00:01:23.609> this<00:01:23.850> time<00:01:24.149> last<00:01:24.450> year<00:01:24.630> that<00:01:25.499> I 00:01:25.520 --> 00:01:25.530 align:start position:0% so it's this time last year that I 00:01:25.530 --> 00:01:27.679 align:start position:0% so it's this time last year that I started<00:01:25.679> working<00:01:26.340> the<00:01:26.429> blockchain<00:01:26.689> everyone 00:01:27.679 --> 00:01:27.689 align:start position:0% started working the blockchain everyone 00:01:27.689 --> 00:01:30.319 align:start position:0% started working the blockchain everyone else<00:01:27.899> is<00:01:28.229> more<00:01:29.039> recent<00:01:29.249> the<00:01:29.670> blockchain<00:01:29.850> than 00:01:30.319 --> 00:01:30.329 align:start position:0% else is more recent the blockchain than 00:01:30.329 --> 00:01:32.300 align:start position:0% else is more recent the blockchain than I<00:01:30.420> am<00:01:30.539> and<00:01:30.810> more<00:01:31.499> recent<00:01:31.829> to<00:01:31.920> aetherium 00:01:32.300 --> 00:01:32.310 align:start position:0% I am and more recent to aetherium 00:01:32.310 --> 00:01:37.940 align:start position:0% I am and more recent to aetherium obviously<00:01:33.920> so<00:01:36.049> let<00:01:37.049> me<00:01:37.170> now<00:01:37.350> talk<00:01:37.409> a<00:01:37.710> little 00:01:37.940 --> 00:01:37.950 align:start position:0% obviously so let me now talk a little 00:01:37.950 --> 00:01:42.649 align:start position:0% obviously so let me now talk a little bit<00:01:38.159> this<00:01:38.429> show-n-tell<00:01:39.270> part<00:01:40.340> so<00:01:41.340> today<00:01:42.179> we 00:01:42.649 --> 00:01:42.659 align:start position:0% bit this show-n-tell part so today we 00:01:42.659 --> 00:01:46.129 align:start position:0% bit this show-n-tell part so today we have<00:01:42.749> launched<00:01:43.289> this<00:01:44.009> application<00:01:44.990> where<00:01:45.990> you 00:01:46.129 --> 00:01:46.139 align:start position:0% have launched this application where you 00:01:46.139 --> 00:01:48.559 align:start position:0% have launched this application where you can<00:01:46.319> play<00:01:46.499> rock-paper-scissors<00:01:46.880> in<00:01:47.880> state 00:01:48.559 --> 00:01:48.569 align:start position:0% can play rock-paper-scissors in state 00:01:48.569 --> 00:01:53.510 align:start position:0% can play rock-paper-scissors in state channel<00:01:49.340> I<00:01:50.840> can<00:01:51.840> see<00:01:52.229> by<00:01:52.469> the<00:01:52.499> like<00:01:52.740> dumbstruck 00:01:53.510 --> 00:01:53.520 align:start position:0% channel I can see by the like dumbstruck 00:01:53.520 --> 00:01:55.609 align:start position:0% channel I can see by the like dumbstruck silence<00:01:54.090> that<00:01:54.420> everyone<00:01:54.689> is<00:01:54.810> like<00:01:54.990> utterly 00:01:55.609 --> 00:01:55.619 align:start position:0% silence that everyone is like utterly 00:01:55.619 --> 00:01:57.669 align:start position:0% silence that everyone is like utterly amazed<00:01:55.979> by<00:01:56.159> that<00:01:56.369> and<00:01:56.579> to<00:01:56.969> be<00:01:57.090> honest 00:01:57.669 --> 00:01:57.679 align:start position:0% amazed by that and to be honest 00:01:57.679 --> 00:02:00.020 align:start position:0% amazed by that and to be honest rock-paper-scissors<00:01:58.679> is<00:01:59.459> not<00:01:59.729> the<00:01:59.880> most 00:02:00.020 --> 00:02:00.030 align:start position:0% rock-paper-scissors is not the most 00:02:00.030 --> 00:02:03.050 align:start position:0% rock-paper-scissors is not the most exciting<00:02:00.659> game<00:02:01.399> let<00:02:02.399> me<00:02:02.490> just<00:02:02.670> quickly<00:02:02.789> take 00:02:03.050 --> 00:02:03.060 align:start position:0% exciting game let me just quickly take 00:02:03.060 --> 00:02:05.270 align:start position:0% exciting game let me just quickly take you<00:02:03.179> through<00:02:03.420> it<00:02:03.509> how<00:02:03.780> it<00:02:03.899> works<00:02:04.219> I'm<00:02:05.219> not 00:02:05.270 --> 00:02:05.280 align:start position:0% you through it how it works I'm not 00:02:05.280 --> 00:02:07.370 align:start position:0% you through it how it works I'm not going<00:02:05.459> to<00:02:05.520> do<00:02:05.579> a<00:02:05.639> live<00:02:05.819> demo<00:02:06.209> but<00:02:06.420> I<00:02:06.780> do<00:02:06.990> have<00:02:07.350> a 00:02:07.370 --> 00:02:07.380 align:start position:0% going to do a live demo but I do have a 00:02:07.380 --> 00:02:11.030 align:start position:0% going to do a live demo but I do have a little<00:02:07.910> video<00:02:09.080> so<00:02:10.080> here<00:02:10.380> somebody<00:02:10.770> is<00:02:10.890> logging 00:02:11.030 --> 00:02:11.040 align:start position:0% little video so here somebody is logging 00:02:11.040 --> 00:02:12.410 align:start position:0% little video so here somebody is logging into<00:02:11.250> the<00:02:11.400> app<00:02:11.520> they're<00:02:11.970> putting<00:02:12.180> in<00:02:12.300> their 00:02:12.410 --> 00:02:12.420 align:start position:0% into the app they're putting in their 00:02:12.420 --> 00:02:14.360 align:start position:0% into the app they're putting in their name<00:02:12.660> and<00:02:13.050> they're<00:02:13.770> gonna 00:02:14.360 --> 00:02:14.370 align:start position:0% name and they're gonna 00:02:14.370 --> 00:02:16.610 align:start position:0% name and they're gonna eight<00:02:14.489> a<00:02:14.760> challenge<00:02:15.239> for<00:02:16.080> someone<00:02:16.379> else<00:02:16.500> to 00:02:16.610 --> 00:02:16.620 align:start position:0% eight a challenge for someone else to 00:02:16.620 --> 00:02:18.289 align:start position:0% eight a challenge for someone else to join<00:02:16.650> so<00:02:17.159> they're<00:02:17.310> gonna<00:02:17.430> say<00:02:17.760> we're<00:02:18.180> gonna 00:02:18.289 --> 00:02:18.299 align:start position:0% join so they're gonna say we're gonna 00:02:18.299 --> 00:02:19.670 align:start position:0% join so they're gonna say we're gonna play<00:02:18.510> rock-paper-scissors<00:02:18.720> and<00:02:19.260> we're<00:02:19.590> gonna 00:02:19.670 --> 00:02:19.680 align:start position:0% play rock-paper-scissors and we're gonna 00:02:19.680 --> 00:02:22.039 align:start position:0% play rock-paper-scissors and we're gonna play<00:02:19.950> for<00:02:20.280> this<00:02:20.489> match<00:02:20.670> each<00:02:20.879> round<00:02:21.090> they<00:02:21.840> put 00:02:22.039 --> 00:02:22.049 align:start position:0% play for this match each round they put 00:02:22.049 --> 00:02:24.410 align:start position:0% play for this match each round they put that<00:02:22.200> challenge<00:02:22.590> up<00:02:22.739> on<00:02:23.010> the<00:02:23.730> next<00:02:23.940> left<00:02:24.209> side 00:02:24.410 --> 00:02:24.420 align:start position:0% that challenge up on the next left side 00:02:24.420 --> 00:02:26.570 align:start position:0% that challenge up on the next left side we've<00:02:24.720> got<00:02:24.750> player<00:02:25.110> to<00:02:25.379> George<00:02:25.950> he's<00:02:26.250> about<00:02:26.400> to 00:02:26.570 --> 00:02:26.580 align:start position:0% we've got player to George he's about to 00:02:26.580 --> 00:02:30.350 align:start position:0% we've got player to George he's about to login<00:02:26.940> I<00:02:27.150> mean<00:02:28.140> he's<00:02:28.319> gonna<00:02:29.090> accept<00:02:30.090> the<00:02:30.209> first 00:02:30.350 --> 00:02:30.360 align:start position:0% login I mean he's gonna accept the first 00:02:30.360 --> 00:02:33.830 align:start position:0% login I mean he's gonna accept the first player's<00:02:30.659> challenge<00:02:32.090> first<00:02:33.090> player<00:02:33.360> confirms 00:02:33.830 --> 00:02:33.840 align:start position:0% player's challenge first player confirms 00:02:33.840 --> 00:02:36.110 align:start position:0% player's challenge first player confirms and<00:02:34.230> then<00:02:34.860> we<00:02:34.980> get<00:02:35.129> into<00:02:35.370> this<00:02:35.489> state<00:02:35.790> where 00:02:36.110 --> 00:02:36.120 align:start position:0% and then we get into this state where 00:02:36.120 --> 00:02:38.539 align:start position:0% and then we get into this state where your<00:02:36.329> channel<00:02:36.900> wallet<00:02:37.200> comes<00:02:37.440> out<00:02:37.739> and<00:02:38.069> your 00:02:38.539 --> 00:02:38.549 align:start position:0% your channel wallet comes out and your 00:02:38.549 --> 00:02:39.979 align:start position:0% your channel wallet comes out and your channel<00:02:38.879> wallet<00:02:39.120> is<00:02:39.209> something<00:02:39.540> that<00:02:39.750> any 00:02:39.979 --> 00:02:39.989 align:start position:0% channel wallet is something that any 00:02:39.989 --> 00:02:41.839 align:start position:0% channel wallet is something that any state<00:02:40.379> channel<00:02:40.739> application<00:02:41.220> will<00:02:41.370> need<00:02:41.579> if 00:02:41.839 --> 00:02:41.849 align:start position:0% state channel application will need if 00:02:41.849 --> 00:02:44.479 align:start position:0% state channel application will need if you're<00:02:42.569> exchanging<00:02:43.079> States<00:02:43.920> with<00:02:44.129> someone 00:02:44.479 --> 00:02:44.489 align:start position:0% you're exchanging States with someone 00:02:44.489 --> 00:02:47.240 align:start position:0% you're exchanging States with someone those<00:02:44.730> states<00:02:45.120> are<00:02:45.420> as<00:02:45.810> almost<00:02:46.590> as<00:02:46.739> important 00:02:47.240 --> 00:02:47.250 align:start position:0% those states are as almost as important 00:02:47.250 --> 00:02:50.750 align:start position:0% those states are as almost as important as<00:02:47.900> as<00:02:48.900> real<00:02:49.410> money<00:02:49.650> so<00:02:50.160> like<00:02:50.340> if<00:02:50.459> you<00:02:50.489> lose 00:02:50.750 --> 00:02:50.760 align:start position:0% as as real money so like if you lose 00:02:50.760 --> 00:02:52.130 align:start position:0% as as real money so like if you lose your<00:02:50.940> state's<00:02:51.180> you<00:02:51.359> can<00:02:51.390> use<00:02:51.569> everything<00:02:51.810> so 00:02:52.130 --> 00:02:52.140 align:start position:0% your state's you can use everything so 00:02:52.140 --> 00:02:54.530 align:start position:0% your state's you can use everything so you<00:02:52.260> need<00:02:52.440> this<00:02:52.620> wallet<00:02:52.859> thing<00:02:53.250> any<00:02:54.239> state 00:02:54.530 --> 00:02:54.540 align:start position:0% you need this wallet thing any state 00:02:54.540 --> 00:02:56.030 align:start position:0% you need this wallet thing any state channel<00:02:54.810> network<00:02:55.140> will<00:02:55.379> need<00:02:55.560> some<00:02:55.829> sort<00:02:55.950> of 00:02:56.030 --> 00:02:56.040 align:start position:0% channel network will need some sort of 00:02:56.040 --> 00:02:58.430 align:start position:0% channel network will need some sort of channel<00:02:56.340> wallet<00:02:56.609> to<00:02:57.120> manage<00:02:57.540> the<00:02:57.930> states<00:02:58.170> that 00:02:58.430 --> 00:02:58.440 align:start position:0% channel wallet to manage the states that 00:02:58.440 --> 00:03:00.619 align:start position:0% channel wallet to manage the states that are<00:02:58.560> being<00:02:58.680> sent<00:02:58.890> across<00:02:59.150> so<00:03:00.150> here<00:03:00.329> you<00:03:00.480> can 00:03:00.619 --> 00:03:00.629 align:start position:0% are being sent across so here you can 00:03:00.629 --> 00:03:02.899 align:start position:0% are being sent across so here you can see<00:03:00.840> they<00:03:01.079> are<00:03:01.109> depositing<00:03:01.799> into<00:03:02.280> an 00:03:02.899 --> 00:03:02.909 align:start position:0% see they are depositing into an 00:03:02.909 --> 00:03:04.490 align:start position:0% see they are depositing into an Unchained<00:03:03.540> contract 00:03:04.490 --> 00:03:04.500 align:start position:0% Unchained contract 00:03:04.500 --> 00:03:06.920 align:start position:0% Unchained contract so<00:03:04.980> they're<00:03:05.190> both<00:03:05.370> locking<00:03:06.000> some<00:03:06.209> funds<00:03:06.480> up<00:03:06.690> on 00:03:06.920 --> 00:03:06.930 align:start position:0% so they're both locking some funds up on 00:03:06.930 --> 00:03:09.259 align:start position:0% so they're both locking some funds up on chain<00:03:07.290> and<00:03:07.560> those<00:03:08.250> are<00:03:08.430> the<00:03:08.489> funds<00:03:08.730> that<00:03:09.120> we're 00:03:09.259 --> 00:03:09.269 align:start position:0% chain and those are the funds that we're 00:03:09.269 --> 00:03:12.440 align:start position:0% chain and those are the funds that we're going<00:03:09.450> to<00:03:09.510> play<00:03:09.690> for<00:03:09.720> in<00:03:10.319> this<00:03:10.829> game<00:03:11.269> so<00:03:12.269> in<00:03:12.390> a 00:03:12.440 --> 00:03:12.450 align:start position:0% going to play for in this game so in a 00:03:12.450 --> 00:03:13.849 align:start position:0% going to play for in this game so in a moment<00:03:12.569> both<00:03:12.989> those<00:03:13.200> transactions<00:03:13.769> would 00:03:13.849 --> 00:03:13.859 align:start position:0% moment both those transactions would 00:03:13.859 --> 00:03:17.270 align:start position:0% moment both those transactions would have<00:03:13.980> gone<00:03:14.069> through<00:03:14.459> and<00:03:15.680> they<00:03:16.680> can<00:03:16.829> return<00:03:16.980> to 00:03:17.270 --> 00:03:17.280 align:start position:0% have gone through and they can return to 00:03:17.280 --> 00:03:19.339 align:start position:0% have gone through and they can return to the<00:03:17.370> game<00:03:17.549> so<00:03:18.510> you<00:03:18.599> can<00:03:18.630> see<00:03:18.900> we've<00:03:19.049> got<00:03:19.079> this 00:03:19.339 --> 00:03:19.349 align:start position:0% the game so you can see we've got this 00:03:19.349 --> 00:03:21.670 align:start position:0% the game so you can see we've got this state<00:03:19.680> of<00:03:19.709> the<00:03:19.799> game<00:03:19.980> here<00:03:20.430> they've<00:03:20.700> each<00:03:20.819> got 00:03:21.670 --> 00:03:21.680 align:start position:0% state of the game here they've each got 00:03:21.680 --> 00:03:25.400 align:start position:0% state of the game here they've each got five<00:03:22.760> five<00:03:23.760> each<00:03:23.940> as<00:03:24.389> it<00:03:24.599> were<00:03:24.720> and<00:03:24.989> now 00:03:25.400 --> 00:03:25.410 align:start position:0% five five each as it were and now 00:03:25.410 --> 00:03:25.970 align:start position:0% five five each as it were and now they're<00:03:25.590> going<00:03:25.680> to<00:03:25.769> play 00:03:25.970 --> 00:03:25.980 align:start position:0% they're going to play 00:03:25.980 --> 00:03:27.259 align:start position:0% they're going to play rock-paper-scissors<00:03:26.190> so<00:03:26.760> behind<00:03:27.060> the<00:03:27.239> scenes 00:03:27.259 --> 00:03:27.269 align:start position:0% rock-paper-scissors so behind the scenes 00:03:27.269 --> 00:03:31.099 align:start position:0% rock-paper-scissors so behind the scenes here<00:03:27.980> this<00:03:28.980> app<00:03:29.190> is<00:03:29.549> implementing<00:03:30.480> a<00:03:30.720> state 00:03:31.099 --> 00:03:31.109 align:start position:0% here this app is implementing a state 00:03:31.109 --> 00:03:33.740 align:start position:0% here this app is implementing a state channel<00:03:31.410> protocol<00:03:31.889> so<00:03:32.579> it<00:03:32.609> is<00:03:32.819> signing<00:03:33.389> States 00:03:33.740 --> 00:03:33.750 align:start position:0% channel protocol so it is signing States 00:03:33.750 --> 00:03:36.650 align:start position:0% channel protocol so it is signing States and<00:03:34.280> exchanging<00:03:35.280> those<00:03:35.430> states<00:03:35.790> between<00:03:36.359> the 00:03:36.650 --> 00:03:36.660 align:start position:0% and exchanging those states between the 00:03:36.660 --> 00:03:41.119 align:start position:0% and exchanging those states between the users<00:03:39.349> and<00:03:40.349> I'll<00:03:40.530> talk<00:03:40.709> a<00:03:40.739> little<00:03:40.829> bit<00:03:41.099> more 00:03:41.119 --> 00:03:41.129 align:start position:0% users and I'll talk a little bit more 00:03:41.129 --> 00:03:43.159 align:start position:0% users and I'll talk a little bit more about<00:03:41.430> that<00:03:41.489> how<00:03:42.389> we're<00:03:42.540> actually<00:03:42.660> thinking 00:03:43.159 --> 00:03:43.169 align:start position:0% about that how we're actually thinking 00:03:43.169 --> 00:03:45.289 align:start position:0% about that how we're actually thinking about<00:03:43.349> those<00:03:43.470> applications<00:03:44.190> so<00:03:45.090> this<00:03:45.209> is 00:03:45.289 --> 00:03:45.299 align:start position:0% about those applications so this is 00:03:45.299 --> 00:03:46.939 align:start position:0% about those applications so this is built<00:03:45.510> on<00:03:45.629> top<00:03:45.780> of<00:03:45.840> a<00:03:46.049> framework<00:03:46.290> called<00:03:46.680> force 00:03:46.939 --> 00:03:46.949 align:start position:0% built on top of a framework called force 00:03:46.949 --> 00:03:48.740 align:start position:0% built on top of a framework called force move<00:03:47.220> I'll<00:03:47.699> talk<00:03:48.030> a<00:03:48.060> little<00:03:48.269> bit<00:03:48.389> more<00:03:48.540> about 00:03:48.740 --> 00:03:48.750 align:start position:0% move I'll talk a little bit more about 00:03:48.750 --> 00:03:50.599 align:start position:0% move I'll talk a little bit more about how<00:03:48.989> this<00:03:49.199> actually<00:03:49.260> works<00:03:49.680> with<00:03:50.160> force<00:03:50.370> move 00:03:50.599 --> 00:03:50.609 align:start position:0% how this actually works with force move 00:03:50.609 --> 00:03:52.729 align:start position:0% how this actually works with force move later<00:03:50.989> we're<00:03:51.989> just<00:03:52.139> going<00:03:52.290> to<00:03:52.349> go<00:03:52.440> through<00:03:52.650> to 00:03:52.729 --> 00:03:52.739 align:start position:0% later we're just going to go through to 00:03:52.739 --> 00:03:54.920 align:start position:0% later we're just going to go through to the<00:03:52.799> end<00:03:52.949> of<00:03:53.040> the<00:03:53.099> game<00:03:53.280> I<00:03:53.639> think<00:03:54.239> George<00:03:54.660> is<00:03:54.720> on 00:03:54.920 --> 00:03:54.930 align:start position:0% the end of the game I think George is on 00:03:54.930 --> 00:03:58.789 align:start position:0% the end of the game I think George is on a<00:03:54.959> winning<00:03:55.260> streak<00:03:57.349> it's<00:03:58.349> not<00:03:58.470> going<00:03:58.620> to<00:03:58.680> take 00:03:58.789 --> 00:03:58.799 align:start position:0% a winning streak it's not going to take 00:03:58.799 --> 00:04:04.490 align:start position:0% a winning streak it's not going to take much<00:03:58.980> longer<00:04:00.769> hopefully<00:04:03.139> yeah<00:04:04.139> he's<00:04:04.290> getting 00:04:04.490 --> 00:04:04.500 align:start position:0% much longer hopefully yeah he's getting 00:04:04.500 --> 00:04:08.930 align:start position:0% much longer hopefully yeah he's getting there<00:04:06.859> so<00:04:07.859> yeah<00:04:07.980> at<00:04:08.160> the<00:04:08.280> end<00:04:08.310> of<00:04:08.549> the<00:04:08.609> game<00:04:08.730> one 00:04:08.930 --> 00:04:08.940 align:start position:0% there so yeah at the end of the game one 00:04:08.940 --> 00:04:10.159 align:start position:0% there so yeah at the end of the game one of<00:04:08.970> the<00:04:09.090> things<00:04:09.329> about<00:04:09.510> this<00:04:09.720> sort<00:04:09.959> of<00:04:09.989> state 00:04:10.159 --> 00:04:10.169 align:start position:0% of the things about this sort of state 00:04:10.169 --> 00:04:12.500 align:start position:0% of the things about this sort of state general<00:04:10.319> application<00:04:10.980> is<00:04:11.220> we're<00:04:12.000> playing<00:04:12.269> one 00:04:12.500 --> 00:04:12.510 align:start position:0% general application is we're playing one 00:04:12.510 --> 00:04:15.050 align:start position:0% general application is we're playing one game<00:04:12.900> of<00:04:13.470> rock-paper-scissors<00:04:13.790> we<00:04:14.790> needed 00:04:15.050 --> 00:04:15.060 align:start position:0% game of rock-paper-scissors we needed 00:04:15.060 --> 00:04:16.969 align:start position:0% game of rock-paper-scissors we needed one<00:04:15.269> on<00:04:15.480> chain<00:04:15.780> deposit<00:04:16.169> the<00:04:16.260> beginning<00:04:16.739> and 00:04:16.969 --> 00:04:16.979 align:start position:0% one on chain deposit the beginning and 00:04:16.979 --> 00:04:18.920 align:start position:0% one on chain deposit the beginning and what<00:04:17.370> we'll<00:04:17.489> see<00:04:17.609> in<00:04:17.699> a<00:04:17.789> minute<00:04:17.910> is<00:04:18.209> another<00:04:18.660> on 00:04:18.920 --> 00:04:18.930 align:start position:0% what we'll see in a minute is another on 00:04:18.930 --> 00:04:22.940 align:start position:0% what we'll see in a minute is another on chain<00:04:19.229> deposit<00:04:19.739> at<00:04:19.889> the<00:04:19.979> end<00:04:21.800> this<00:04:22.800> is 00:04:22.940 --> 00:04:22.950 align:start position:0% chain deposit at the end this is 00:04:22.950 --> 00:04:24.500 align:start position:0% chain deposit at the end this is something<00:04:23.280> that<00:04:23.310> when<00:04:23.580> we<00:04:23.610> have<00:04:23.880> like<00:04:24.060> virtual 00:04:24.500 --> 00:04:24.510 align:start position:0% something that when we have like virtual 00:04:24.510 --> 00:04:26.209 align:start position:0% something that when we have like virtual channels<00:04:24.840> in<00:04:25.229> state<00:04:25.680> channel<00:04:25.919> networks 00:04:26.209 --> 00:04:26.219 align:start position:0% channels in state channel networks 00:04:26.219 --> 00:04:28.159 align:start position:0% channels in state channel networks you'll<00:04:26.909> be<00:04:27.060> able<00:04:27.150> to<00:04:27.330> get<00:04:27.450> away<00:04:27.630> with 00:04:28.159 --> 00:04:28.169 align:start position:0% you'll be able to get away with 00:04:28.169 --> 00:04:29.450 align:start position:0% you'll be able to get away with one<00:04:28.469> deposit<00:04:28.919> at<00:04:29.009> the<00:04:29.039> beginning<00:04:29.340> of<00:04:29.400> the 00:04:29.450 --> 00:04:29.460 align:start position:0% one deposit at the beginning of the 00:04:29.460 --> 00:04:30.920 align:start position:0% one deposit at the beginning of the month<00:04:29.610> and<00:04:29.909> then<00:04:30.389> you'll<00:04:30.509> be<00:04:30.599> able<00:04:30.689> to<00:04:30.810> play 00:04:30.920 --> 00:04:30.930 align:start position:0% month and then you'll be able to play 00:04:30.930 --> 00:04:32.600 align:start position:0% month and then you'll be able to play multiple<00:04:31.229> games<00:04:31.379> like<00:04:31.740> this<00:04:31.889> opening<00:04:32.490> these 00:04:32.600 --> 00:04:32.610 align:start position:0% multiple games like this opening these 00:04:32.610 --> 00:04:34.939 align:start position:0% multiple games like this opening these channels<00:04:33.060> and<00:04:33.330> closing<00:04:33.780> them<00:04:33.930> off<00:04:34.080> chain<00:04:34.379> so 00:04:34.939 --> 00:04:34.949 align:start position:0% channels and closing them off chain so 00:04:34.949 --> 00:04:36.499 align:start position:0% channels and closing them off chain so that's<00:04:35.099> like<00:04:35.280> an<00:04:35.430> important<00:04:35.849> area<00:04:36.030> of<00:04:36.210> future 00:04:36.499 --> 00:04:36.509 align:start position:0% that's like an important area of future 00:04:36.509 --> 00:04:37.640 align:start position:0% that's like an important area of future research<00:04:36.599> which<00:04:37.080> we'll<00:04:37.229> probably<00:04:37.289> be<00:04:37.560> looking 00:04:37.640 --> 00:04:37.650 align:start position:0% research which we'll probably be looking 00:04:37.650 --> 00:04:41.209 align:start position:0% research which we'll probably be looking at<00:04:37.919> in<00:04:38.430> the<00:04:38.520> future<00:04:39.499> anyway<00:04:40.499> so<00:04:40.620> this<00:04:40.979> is<00:04:41.129> the 00:04:41.209 --> 00:04:41.219 align:start position:0% at in the future anyway so this is the 00:04:41.219 --> 00:04:43.760 align:start position:0% at in the future anyway so this is the demo<00:04:41.490> this<00:04:41.699> is<00:04:41.819> the<00:04:42.199> example<00:04:43.199> app<00:04:43.349> that<00:04:43.650> we've 00:04:43.760 --> 00:04:43.770 align:start position:0% demo this is the example app that we've 00:04:43.770 --> 00:04:48.260 align:start position:0% demo this is the example app that we've put<00:04:43.949> together<00:04:45.590> so<00:04:46.699> you're<00:04:47.699> excited<00:04:47.969> at<00:04:48.210> the 00:04:48.260 --> 00:04:48.270 align:start position:0% put together so you're excited at the 00:04:48.270 --> 00:04:50.540 align:start position:0% put together so you're excited at the beginning<00:04:48.560> you're<00:04:49.560> probably<00:04:49.800> even<00:04:50.159> more 00:04:50.540 --> 00:04:50.550 align:start position:0% beginning you're probably even more 00:04:50.550 --> 00:04:54.100 align:start position:0% beginning you're probably even more overwhelmed<00:04:51.270> now<00:04:51.509> you've<00:04:51.810> seen<00:04:52.050> it<00:04:52.199> in<00:04:52.259> action 00:04:54.100 --> 00:04:54.110 align:start position:0% overwhelmed now you've seen it in action 00:04:54.110 --> 00:04:56.260 align:start position:0% overwhelmed now you've seen it in action I'm<00:04:55.110> seeing<00:04:55.409> a<00:04:55.469> lot<00:04:55.590> of<00:04:55.620> stunned<00:04:55.889> faces 00:04:56.260 --> 00:04:56.270 align:start position:0% I'm seeing a lot of stunned faces 00:04:56.270 --> 00:05:00.350 align:start position:0% I'm seeing a lot of stunned faces clearly<00:04:57.270> a<00:04:57.389> winner<00:04:57.599> so<00:04:58.699> what<00:04:59.699> was<00:04:59.849> hard<00:05:00.120> about 00:05:00.350 --> 00:05:00.360 align:start position:0% clearly a winner so what was hard about 00:05:00.360 --> 00:05:07.369 align:start position:0% clearly a winner so what was hard about this<00:05:02.659> so<00:05:03.659> I<00:05:04.639> guess<00:05:05.639> part<00:05:06.569> of<00:05:06.840> the<00:05:06.990> problems 00:05:07.369 --> 00:05:07.379 align:start position:0% this so I guess part of the problems 00:05:07.379 --> 00:05:09.649 align:start position:0% this so I guess part of the problems where<00:05:07.740> the<00:05:07.919> standard<00:05:08.490> blockchain<00:05:09.060> problems 00:05:09.649 --> 00:05:09.659 align:start position:0% where the standard blockchain problems 00:05:09.659 --> 00:05:11.869 align:start position:0% where the standard blockchain problems that<00:05:10.379> everyone<00:05:10.830> experiences<00:05:11.189> when<00:05:11.789> they're 00:05:11.869 --> 00:05:11.879 align:start position:0% that everyone experiences when they're 00:05:11.879 --> 00:05:13.820 align:start position:0% that everyone experiences when they're new<00:05:12.120> to<00:05:12.150> the<00:05:12.300> blockchain<00:05:12.479> and<00:05:13.139> when<00:05:13.710> they're 00:05:13.820 --> 00:05:13.830 align:start position:0% new to the blockchain and when they're 00:05:13.830 --> 00:05:15.499 align:start position:0% new to the blockchain and when they're trying<00:05:14.189> to<00:05:14.279> develop<00:05:14.699> on<00:05:14.819> the<00:05:14.879> blockchain<00:05:15.120> and 00:05:15.499 --> 00:05:15.509 align:start position:0% trying to develop on the blockchain and 00:05:15.509 --> 00:05:17.929 align:start position:0% trying to develop on the blockchain and I'm<00:05:16.289> not<00:05:16.500> gonna<00:05:16.680> really<00:05:16.979> talk<00:05:17.340> about<00:05:17.639> that 00:05:17.929 --> 00:05:17.939 align:start position:0% I'm not gonna really talk about that 00:05:17.939 --> 00:05:20.629 align:start position:0% I'm not gonna really talk about that aspect<00:05:18.180> of<00:05:18.810> things<00:05:19.110> so<00:05:19.439> much<00:05:19.680> because<00:05:20.339> that's 00:05:20.629 --> 00:05:20.639 align:start position:0% aspect of things so much because that's 00:05:20.639 --> 00:05:25.129 align:start position:0% aspect of things so much because that's common<00:05:21.060> to<00:05:21.089> like<00:05:21.360> all<00:05:21.599> the<00:05:21.779> projects<00:05:23.599> so<00:05:24.599> the 00:05:25.129 --> 00:05:25.139 align:start position:0% common to like all the projects so the 00:05:25.139 --> 00:05:28.219 align:start position:0% common to like all the projects so the problems<00:05:25.560> about<00:05:26.389> setting<00:05:27.389> up<00:05:27.479> your<00:05:27.539> app<00:05:27.960> to 00:05:28.219 --> 00:05:28.229 align:start position:0% problems about setting up your app to 00:05:28.229 --> 00:05:30.439 align:start position:0% problems about setting up your app to work<00:05:28.379> with<00:05:28.589> typescript<00:05:28.860> and<00:05:29.339> integrate<00:05:29.879> with 00:05:30.439 --> 00:05:30.449 align:start position:0% work with typescript and integrate with 00:05:30.449 --> 00:05:32.659 align:start position:0% work with typescript and integrate with truffle<00:05:31.439> or<00:05:31.800> like<00:05:32.129> whichever<00:05:32.400> other 00:05:32.659 --> 00:05:32.669 align:start position:0% truffle or like whichever other 00:05:32.669 --> 00:05:35.329 align:start position:0% truffle or like whichever other developer<00:05:33.270> framework<00:05:33.659> you're<00:05:33.839> using<00:05:34.099> I'm<00:05:35.099> not 00:05:35.329 --> 00:05:35.339 align:start position:0% developer framework you're using I'm not 00:05:35.339 --> 00:05:36.860 align:start position:0% developer framework you're using I'm not going<00:05:35.520> to<00:05:35.580> really<00:05:35.729> touch<00:05:36.029> on<00:05:36.210> that<00:05:36.419> I'm<00:05:36.810> not 00:05:36.860 --> 00:05:36.870 align:start position:0% going to really touch on that I'm not 00:05:36.870 --> 00:05:37.999 align:start position:0% going to really touch on that I'm not going<00:05:37.110> to<00:05:37.169> really<00:05:37.379> touch<00:05:37.589> on<00:05:37.740> like<00:05:37.919> the 00:05:37.999 --> 00:05:38.009 align:start position:0% going to really touch on like the 00:05:38.009 --> 00:05:39.110 align:start position:0% going to really touch on like the problems<00:05:38.250> with<00:05:38.339> meta<00:05:38.550> masks<00:05:38.819> when<00:05:39.000> you're 00:05:39.110 --> 00:05:39.120 align:start position:0% problems with meta masks when you're 00:05:39.120 --> 00:05:40.399 align:start position:0% problems with meta masks when you're developing<00:05:39.330> and<00:05:39.779> having<00:05:39.960> to<00:05:40.050> flick<00:05:40.289> the 00:05:40.399 --> 00:05:40.409 align:start position:0% developing and having to flick the 00:05:40.409 --> 00:05:42.320 align:start position:0% developing and having to flick the network<00:05:40.770> back<00:05:40.979> and<00:05:41.159> forwards<00:05:41.520> and<00:05:41.699> taking<00:05:42.270> a 00:05:42.320 --> 00:05:42.330 align:start position:0% network back and forwards and taking a 00:05:42.330 --> 00:05:44.570 align:start position:0% network back and forwards and taking a while<00:05:42.509> to<00:05:42.539> realize<00:05:42.990> that<00:05:43.020> stuff<00:05:43.589> and<00:05:43.949> like<00:05:44.129> I'm 00:05:44.570 --> 00:05:44.580 align:start position:0% while to realize that stuff and like I'm 00:05:44.580 --> 00:05:45.860 align:start position:0% while to realize that stuff and like I'm not<00:05:44.939> going<00:05:45.089> to<00:05:45.149> definitely<00:05:45.479> are<00:05:45.689> going<00:05:45.810> to 00:05:45.860 --> 00:05:45.870 align:start position:0% not going to definitely are going to 00:05:45.870 --> 00:05:48.619 align:start position:0% not going to definitely are going to talk<00:05:46.020> about<00:05:46.050> the<00:05:46.919> eight<00:05:47.159> weeks<00:05:47.610> we<00:05:48.270> spent 00:05:48.619 --> 00:05:48.629 align:start position:0% talk about the eight weeks we spent 00:05:48.629 --> 00:05:51.980 align:start position:0% talk about the eight weeks we spent debugging<00:05:49.469> solidity<00:05:49.919> by<00:05:50.789> omitting<00:05:51.479> events 00:05:51.980 --> 00:05:51.990 align:start position:0% debugging solidity by omitting events 00:05:51.990 --> 00:05:54.409 align:start position:0% debugging solidity by omitting events before<00:05:52.800> we<00:05:53.189> realized<00:05:53.580> there<00:05:53.909> was<00:05:54.000> a<00:05:54.029> solidity 00:05:54.409 --> 00:05:54.419 align:start position:0% before we realized there was a solidity 00:05:54.419 --> 00:06:02.659 align:start position:0% before we realized there was a solidity debugger<00:05:59.659> so<00:06:00.659> a<00:06:01.080> lot<00:06:01.770> of<00:06:01.800> that<00:06:02.039> is<00:06:02.189> just<00:06:02.219> like 00:06:02.659 --> 00:06:02.669 align:start position:0% debugger so a lot of that is just like 00:06:02.669 --> 00:06:04.309 align:start position:0% debugger so a lot of that is just like part<00:06:03.000> and<00:06:03.149> parcel<00:06:03.569> of<00:06:03.750> developing<00:06:04.199> on 00:06:04.309 --> 00:06:04.319 align:start position:0% part and parcel of developing on 00:06:04.319 --> 00:06:07.070 align:start position:0% part and parcel of developing on aetherium<00:06:05.419> we're<00:06:06.419> interested<00:06:06.870> in<00:06:06.960> learning 00:06:07.070 --> 00:06:07.080 align:start position:0% aetherium we're interested in learning 00:06:07.080 --> 00:06:08.510 align:start position:0% aetherium we're interested in learning from<00:06:07.319> other<00:06:07.529> people<00:06:07.860> in<00:06:07.919> the<00:06:08.009> room<00:06:08.159> how<00:06:08.460> to 00:06:08.510 --> 00:06:08.520 align:start position:0% from other people in the room how to 00:06:08.520 --> 00:06:10.100 align:start position:0% from other people in the room how to better<00:06:08.759> do<00:06:08.969> that<00:06:09.149> we've<00:06:09.389> learnt<00:06:09.750> a<00:06:09.839> lot<00:06:09.990> of 00:06:10.100 --> 00:06:10.110 align:start position:0% better do that we've learnt a lot of 00:06:10.110 --> 00:06:11.570 align:start position:0% better do that we've learnt a lot of this<00:06:10.229> stuff<00:06:10.409> by<00:06:10.589> trial<00:06:10.830> and<00:06:10.889> error<00:06:11.009> but<00:06:11.370> like 00:06:11.570 --> 00:06:11.580 align:start position:0% this stuff by trial and error but like 00:06:11.580 --> 00:06:13.339 align:start position:0% this stuff by trial and error but like they're<00:06:12.419> probably<00:06:12.569> still<00:06:12.839> a<00:06:12.899> load<00:06:13.020> of<00:06:13.110> stuff 00:06:13.339 --> 00:06:13.349 align:start position:0% they're probably still a load of stuff 00:06:13.349 --> 00:06:15.589 align:start position:0% they're probably still a load of stuff we<00:06:13.500> don't<00:06:13.620> know<00:06:13.969> so<00:06:14.969> one<00:06:15.089> of<00:06:15.120> the<00:06:15.210> things<00:06:15.389> I 00:06:15.589 --> 00:06:15.599 align:start position:0% we don't know so one of the things I 00:06:15.599 --> 00:06:16.999 align:start position:0% we don't know so one of the things I wanted<00:06:15.839> to<00:06:15.960> spend<00:06:16.139> the<00:06:16.229> last<00:06:16.469> few<00:06:16.649> minutes<00:06:16.740> of 00:06:16.999 --> 00:06:17.009 align:start position:0% wanted to spend the last few minutes of 00:06:17.009 --> 00:06:19.719 align:start position:0% wanted to spend the last few minutes of this<00:06:17.129> talk<00:06:17.430> talking<00:06:18.089> about<00:06:18.449> is<00:06:18.750> what<00:06:19.259> are<00:06:19.379> the 00:06:19.719 --> 00:06:19.729 align:start position:0% this talk talking about is what are the 00:06:19.729 --> 00:06:22.670 align:start position:0% this talk talking about is what are the essential<00:06:20.729> things<00:06:20.870> the<00:06:21.870> things<00:06:22.110> essential<00:06:22.649> to 00:06:22.670 --> 00:06:22.680 align:start position:0% essential things the things essential to 00:06:22.680 --> 00:06:25.540 align:start position:0% essential things the things essential to state<00:06:23.069> channels<00:06:23.520> that<00:06:24.240> we<00:06:24.389> found<00:06:24.659> difficult 00:06:25.540 --> 00:06:25.550 align:start position:0% state channels that we found difficult 00:06:25.550 --> 00:06:32.360 align:start position:0% state channels that we found difficult and<00:06:26.550> I<00:06:28.879> guess<00:06:29.990> the<00:06:30.990> way<00:06:31.139> I<00:06:31.560> would<00:06:31.949> look<00:06:32.069> at<00:06:32.219> this 00:06:32.360 --> 00:06:32.370 align:start position:0% and I guess the way I would look at this 00:06:32.370 --> 00:06:34.999 align:start position:0% and I guess the way I would look at this I'm<00:06:32.580> going<00:06:32.699> to<00:06:32.759> focus<00:06:32.879> on<00:06:33.120> this<00:06:33.210> one<00:06:33.509> problem<00:06:34.009> a 00:06:34.999 --> 00:06:35.009 align:start position:0% I'm going to focus on this one problem a 00:06:35.009 --> 00:06:37.909 align:start position:0% I'm going to focus on this one problem a hard<00:06:35.610> thing<00:06:35.849> about<00:06:35.939> state<00:06:36.419> channels<00:06:36.810> is<00:06:37.110> state 00:06:37.909 --> 00:06:37.919 align:start position:0% hard thing about state channels is state 00:06:37.919 --> 00:06:41.930 align:start position:0% hard thing about state channels is state and<00:06:38.330> managing<00:06:39.330> state<00:06:39.919> so<00:06:40.919> what 00:06:41.930 --> 00:06:41.940 align:start position:0% and managing state so what 00:06:41.940 --> 00:06:45.800 align:start position:0% and managing state so what mean<00:06:42.180> by<00:06:42.360> that<00:06:43.280> so<00:06:44.280> we<00:06:44.460> were<00:06:44.550> working<00:06:44.810> we're 00:06:45.800 --> 00:06:45.810 align:start position:0% mean by that so we were working we're 00:06:45.810 --> 00:06:47.420 align:start position:0% mean by that so we were working we're building<00:06:46.140> this<00:06:46.230> app<00:06:46.440> on<00:06:46.740> top<00:06:46.950> of<00:06:47.070> the<00:06:47.160> force 00:06:47.420 --> 00:06:47.430 align:start position:0% building this app on top of the force 00:06:47.430 --> 00:06:49.880 align:start position:0% building this app on top of the force move<00:06:47.700> framework<00:06:48.240> and<00:06:48.570> the<00:06:49.440> force<00:06:49.650> move 00:06:49.880 --> 00:06:49.890 align:start position:0% move framework and the force move 00:06:49.890 --> 00:06:53.030 align:start position:0% move framework and the force move framework<00:06:50.400> has<00:06:51.060> a<00:06:51.540> very<00:06:52.020> simple<00:06:52.380> way<00:06:52.710> of 00:06:53.030 --> 00:06:53.040 align:start position:0% framework has a very simple way of 00:06:53.040 --> 00:06:55.400 align:start position:0% framework has a very simple way of managing<00:06:53.490> state<00:06:53.970> and<00:06:54.300> thinking<00:06:54.990> about<00:06:55.080> the 00:06:55.400 --> 00:06:55.410 align:start position:0% managing state and thinking about the 00:06:55.410 --> 00:06:57.800 align:start position:0% managing state and thinking about the state<00:06:55.650> of<00:06:55.800> your<00:06:55.950> state<00:06:56.160> channel<00:06:57.120> and<00:06:57.360> your 00:06:57.800 --> 00:06:57.810 align:start position:0% state of your state channel and your 00:06:57.810 --> 00:06:59.900 align:start position:0% state of your state channel and your state<00:06:58.080> transitions<00:06:58.650> so<00:06:59.430> this<00:06:59.670> is<00:06:59.880> a 00:06:59.900 --> 00:06:59.910 align:start position:0% state transitions so this is a 00:06:59.910 --> 00:07:02.690 align:start position:0% state transitions so this is a representation<00:07:00.780> of<00:07:01.080> rock-paper-scissors<00:07:01.700> in 00:07:02.690 --> 00:07:02.700 align:start position:0% representation of rock-paper-scissors in 00:07:02.700 --> 00:07:05.960 align:start position:0% representation of rock-paper-scissors in the<00:07:03.420> force<00:07:03.600> move<00:07:03.840> framework<00:07:04.400> you<00:07:05.400> have<00:07:05.430> four 00:07:05.960 --> 00:07:05.970 align:start position:0% the force move framework you have four 00:07:05.970 --> 00:07:08.330 align:start position:0% the force move framework you have four different<00:07:06.450> states<00:07:06.720> if<00:07:07.140> you're<00:07:07.980> trying<00:07:08.280> to 00:07:08.330 --> 00:07:08.340 align:start position:0% different states if you're trying to 00:07:08.340 --> 00:07:10.310 align:start position:0% different states if you're trying to program<00:07:08.640> this<00:07:09.090> as<00:07:09.390> a<00:07:09.450> developer<00:07:09.960> building<00:07:10.230> on 00:07:10.310 --> 00:07:10.320 align:start position:0% program this as a developer building on 00:07:10.320 --> 00:07:12.590 align:start position:0% program this as a developer building on top<00:07:10.500> of<00:07:10.560> the<00:07:10.740> framework<00:07:11.160> you're<00:07:12.030> responsible 00:07:12.590 --> 00:07:12.600 align:start position:0% top of the framework you're responsible 00:07:12.600 --> 00:07:14.870 align:start position:0% top of the framework you're responsible for<00:07:12.660> writing<00:07:13.020> a<00:07:13.440> single<00:07:13.920> library<00:07:14.160> contract 00:07:14.870 --> 00:07:14.880 align:start position:0% for writing a single library contract 00:07:14.880 --> 00:07:17.510 align:start position:0% for writing a single library contract with<00:07:15.540> a<00:07:15.570> valid<00:07:15.870> transition<00:07:16.470> function<00:07:16.980> which 00:07:17.510 --> 00:07:17.520 align:start position:0% with a valid transition function which 00:07:17.520 --> 00:07:19.640 align:start position:0% with a valid transition function which defines<00:07:17.940> these<00:07:18.210> states<00:07:18.540> and<00:07:18.870> the<00:07:19.380> valid 00:07:19.640 --> 00:07:19.650 align:start position:0% defines these states and the valid 00:07:19.650 --> 00:07:22.010 align:start position:0% defines these states and the valid transitions<00:07:20.160> between<00:07:20.310> them<00:07:20.690> so<00:07:21.690> in<00:07:21.780> the<00:07:21.840> face 00:07:22.010 --> 00:07:22.020 align:start position:0% transitions between them so in the face 00:07:22.020 --> 00:07:23.870 align:start position:0% transitions between them so in the face of<00:07:22.050> that<00:07:22.410> that<00:07:22.770> seems<00:07:23.070> pretty<00:07:23.250> simple<00:07:23.730> and 00:07:23.870 --> 00:07:23.880 align:start position:0% of that that seems pretty simple and 00:07:23.880 --> 00:07:25.940 align:start position:0% of that that seems pretty simple and it's<00:07:23.970> pretty<00:07:24.180> conceptually<00:07:24.810> simple<00:07:25.230> to<00:07:25.710> think 00:07:25.940 --> 00:07:25.950 align:start position:0% it's pretty conceptually simple to think 00:07:25.950 --> 00:07:27.470 align:start position:0% it's pretty conceptually simple to think about<00:07:26.190> what's<00:07:26.400> happening<00:07:26.790> actually<00:07:27.330> in<00:07:27.420> the 00:07:27.470 --> 00:07:27.480 align:start position:0% about what's happening actually in the 00:07:27.480 --> 00:07:28.760 align:start position:0% about what's happening actually in the state<00:07:27.660> channel<00:07:27.990> and<00:07:28.170> what's<00:07:28.290> happening<00:07:28.680> on 00:07:28.760 --> 00:07:28.770 align:start position:0% state channel and what's happening on 00:07:28.770 --> 00:07:30.860 align:start position:0% state channel and what's happening on the<00:07:28.890> chain<00:07:29.130> and<00:07:29.420> that's<00:07:30.420> one<00:07:30.570> of<00:07:30.660> the<00:07:30.720> nice 00:07:30.860 --> 00:07:30.870 align:start position:0% the chain and that's one of the nice 00:07:30.870 --> 00:07:32.270 align:start position:0% the chain and that's one of the nice things<00:07:30.900> about<00:07:31.320> what<00:07:31.620> we<00:07:31.710> are<00:07:31.770> working<00:07:31.980> with 00:07:32.270 --> 00:07:32.280 align:start position:0% things about what we are working with 00:07:32.280 --> 00:07:33.860 align:start position:0% things about what we are working with it's<00:07:32.670> like<00:07:32.880> one<00:07:33.000> of<00:07:33.030> the<00:07:33.150> simpler<00:07:33.510> state 00:07:33.860 --> 00:07:33.870 align:start position:0% it's like one of the simpler state 00:07:33.870 --> 00:07:38.750 align:start position:0% it's like one of the simpler state channels<00:07:34.230> frameworks<00:07:35.190> to<00:07:35.400> work<00:07:35.550> with<00:07:37.220> but<00:07:38.220> in 00:07:38.750 --> 00:07:38.760 align:start position:0% channels frameworks to work with but in 00:07:38.760 --> 00:07:42.560 align:start position:0% channels frameworks to work with but in terms<00:07:39.570> of<00:07:39.750> your<00:07:39.870> app<00:07:40.520> there<00:07:41.520> are<00:07:41.610> like<00:07:41.760> many 00:07:42.560 --> 00:07:42.570 align:start position:0% terms of your app there are like many 00:07:42.570 --> 00:07:45.260 align:start position:0% terms of your app there are like many many<00:07:42.930> more<00:07:43.260> states<00:07:43.680> so<00:07:44.340> we<00:07:44.490> actually<00:07:44.760> came<00:07:44.970> to 00:07:45.260 --> 00:07:45.270 align:start position:0% many more states so we actually came to 00:07:45.270 --> 00:07:47.320 align:start position:0% many more states so we actually came to like<00:07:45.420> interacting<00:07:46.260> with<00:07:46.290> those<00:07:46.590> four<00:07:46.950> states 00:07:47.320 --> 00:07:47.330 align:start position:0% like interacting with those four states 00:07:47.330 --> 00:07:49.880 align:start position:0% like interacting with those four states force<00:07:48.330> four<00:07:48.750> types<00:07:49.050> of<00:07:49.200> messages<00:07:49.590> that<00:07:49.620> we're 00:07:49.880 --> 00:07:49.890 align:start position:0% force four types of messages that we're 00:07:49.890 --> 00:07:51.950 align:start position:0% force four types of messages that we're sending<00:07:50.070> back<00:07:50.220> and<00:07:50.520> forth<00:07:50.730> we<00:07:51.450> ended<00:07:51.660> up<00:07:51.780> with 00:07:51.950 --> 00:07:51.960 align:start position:0% sending back and forth we ended up with 00:07:51.960 --> 00:07:54.020 align:start position:0% sending back and forth we ended up with this<00:07:52.200> diagram<00:07:52.680> and<00:07:52.919> this<00:07:53.460> doesn't<00:07:53.730> even 00:07:54.020 --> 00:07:54.030 align:start position:0% this diagram and this doesn't even 00:07:54.030 --> 00:07:56.090 align:start position:0% this diagram and this doesn't even include<00:07:54.270> the<00:07:54.960> wallet<00:07:55.260> stuff<00:07:55.530> that<00:07:55.740> we<00:07:55.830> showed 00:07:56.090 --> 00:07:56.100 align:start position:0% include the wallet stuff that we showed 00:07:56.100 --> 00:07:58.010 align:start position:0% include the wallet stuff that we showed all<00:07:56.700> of<00:07:56.880> those<00:07:57.000> wallet<00:07:57.419> states<00:07:57.750> have<00:07:57.930> been 00:07:58.010 --> 00:07:58.020 align:start position:0% all of those wallet states have been 00:07:58.020 --> 00:08:03.650 align:start position:0% all of those wallet states have been collapsed<00:07:58.560> into<00:07:58.860> like<00:07:59.090> dates<00:08:00.090> to<00:08:00.270> the<00:08:00.360> top<00:08:02.660> so 00:08:03.650 --> 00:08:03.660 align:start position:0% collapsed into like dates to the top so 00:08:03.660 --> 00:08:06.740 align:start position:0% collapsed into like dates to the top so I<00:08:04.080> guess<00:08:04.830> why<00:08:05.040> is<00:08:05.100> this<00:08:05.400> this<00:08:05.610> complicated<00:08:06.180> and 00:08:06.740 --> 00:08:06.750 align:start position:0% I guess why is this this complicated and 00:08:06.750 --> 00:08:09.440 align:start position:0% I guess why is this this complicated and I<00:08:07.500> guess<00:08:07.680> if<00:08:07.830> you<00:08:07.890> think<00:08:07.919> about<00:08:08.250> it<00:08:08.430> like<00:08:08.580> back 00:08:09.440 --> 00:08:09.450 align:start position:0% I guess if you think about it like back 00:08:09.450 --> 00:08:11.150 align:start position:0% I guess if you think about it like back in<00:08:09.630> the<00:08:09.720> very<00:08:09.840> early<00:08:10.200> days<00:08:10.230> of<00:08:10.410> the<00:08:10.590> web<00:08:10.830> you 00:08:11.150 --> 00:08:11.160 align:start position:0% in the very early days of the web you 00:08:11.160 --> 00:08:13.010 align:start position:0% in the very early days of the web you had<00:08:11.340> like<00:08:11.490> a<00:08:11.640> user<00:08:11.910> who<00:08:12.419> was<00:08:12.510> interacting<00:08:12.990> with 00:08:13.010 --> 00:08:13.020 align:start position:0% had like a user who was interacting with 00:08:13.020 --> 00:08:15.560 align:start position:0% had like a user who was interacting with a<00:08:13.110> server<00:08:13.410> and<00:08:13.740> that<00:08:13.770> was<00:08:14.640> like<00:08:14.820> pretty<00:08:15.060> simple 00:08:15.560 --> 00:08:15.570 align:start position:0% a server and that was like pretty simple 00:08:15.570 --> 00:08:17.270 align:start position:0% a server and that was like pretty simple like<00:08:15.780> the<00:08:16.110> state<00:08:16.380> was<00:08:16.680> the<00:08:16.860> state<00:08:17.070> that<00:08:17.100> was 00:08:17.270 --> 00:08:17.280 align:start position:0% like the state was the state that was 00:08:17.280 --> 00:08:18.800 align:start position:0% like the state was the state that was stored<00:08:17.460> on<00:08:17.580> the<00:08:17.640> server<00:08:17.820> there's<00:08:18.510> one<00:08:18.630> way<00:08:18.750> of 00:08:18.800 --> 00:08:18.810 align:start position:0% stored on the server there's one way of 00:08:18.810 --> 00:08:20.030 align:start position:0% stored on the server there's one way of interacting<00:08:19.140> with<00:08:19.290> it<00:08:19.500> you<00:08:19.650> put<00:08:19.830> it<00:08:19.860> back<00:08:19.980> on 00:08:20.030 --> 00:08:20.040 align:start position:0% interacting with it you put it back on 00:08:20.040 --> 00:08:21.430 align:start position:0% interacting with it you put it back on the<00:08:20.220> server<00:08:20.460> there's<00:08:20.760> one<00:08:20.910> source<00:08:21.180> of<00:08:21.300> truth 00:08:21.430 --> 00:08:21.440 align:start position:0% the server there's one source of truth 00:08:21.440 --> 00:08:23.870 align:start position:0% the server there's one source of truth now<00:08:22.440> in<00:08:22.620> recent<00:08:23.010> years<00:08:23.370> things<00:08:23.550> have<00:08:23.669> got<00:08:23.850> a 00:08:23.870 --> 00:08:23.880 align:start position:0% now in recent years things have got a 00:08:23.880 --> 00:08:25.220 align:start position:0% now in recent years things have got a bit<00:08:24.060> more<00:08:24.150> complicated<00:08:24.450> so<00:08:24.780> you<00:08:25.110> now<00:08:25.200> have 00:08:25.220 --> 00:08:25.230 align:start position:0% bit more complicated so you now have 00:08:25.230 --> 00:08:27.590 align:start position:0% bit more complicated so you now have front-end<00:08:25.919> JavaScript<00:08:25.980> apps<00:08:26.669> so<00:08:27.270> you've<00:08:27.450> got 00:08:27.590 --> 00:08:27.600 align:start position:0% front-end JavaScript apps so you've got 00:08:27.600 --> 00:08:30.200 align:start position:0% front-end JavaScript apps so you've got like<00:08:27.840> the<00:08:28.650> state<00:08:28.919> your<00:08:29.130> local<00:08:29.490> state<00:08:29.760> and<00:08:29.790> then 00:08:30.200 --> 00:08:30.210 align:start position:0% like the state your local state and then 00:08:30.210 --> 00:08:31.850 align:start position:0% like the state your local state and then you've<00:08:30.360> got<00:08:30.570> the<00:08:30.810> updated<00:08:31.260> state<00:08:31.590> on<00:08:31.770> the 00:08:31.850 --> 00:08:31.860 align:start position:0% you've got the updated state on the 00:08:31.860 --> 00:08:33.500 align:start position:0% you've got the updated state on the server<00:08:32.099> and<00:08:32.550> you're<00:08:32.700> interacting<00:08:33.150> with<00:08:33.450> your 00:08:33.500 --> 00:08:33.510 align:start position:0% server and you're interacting with your 00:08:33.510 --> 00:08:35.480 align:start position:0% server and you're interacting with your local<00:08:33.660> state<00:08:33.870> and<00:08:34.110> maybe<00:08:34.919> somebody<00:08:35.190> else<00:08:35.339> is 00:08:35.480 --> 00:08:35.490 align:start position:0% local state and maybe somebody else is 00:08:35.490 --> 00:08:37.070 align:start position:0% local state and maybe somebody else is interacting<00:08:35.849> with<00:08:35.940> the<00:08:36.000> server<00:08:36.210> and<00:08:36.570> you<00:08:36.630> like 00:08:37.070 --> 00:08:37.080 align:start position:0% interacting with the server and you like 00:08:37.080 --> 00:08:38.750 align:start position:0% interacting with the server and you like can<00:08:37.289> receive<00:08:37.530> updates<00:08:37.919> and<00:08:38.219> then<00:08:38.669> the 00:08:38.750 --> 00:08:38.760 align:start position:0% can receive updates and then the 00:08:38.760 --> 00:08:40.700 align:start position:0% can receive updates and then the blockchain<00:08:39.000> adds<00:08:39.539> an<00:08:39.750> extra<00:08:39.960> dimension<00:08:40.260> into 00:08:40.700 --> 00:08:40.710 align:start position:0% blockchain adds an extra dimension into 00:08:40.710 --> 00:08:43.490 align:start position:0% blockchain adds an extra dimension into that<00:08:40.950> so<00:08:41.909> the<00:08:42.240> blockchain<00:08:42.510> is<00:08:42.690> like<00:08:42.990> another 00:08:43.490 --> 00:08:43.500 align:start position:0% that so the blockchain is like another 00:08:43.500 --> 00:08:44.840 align:start position:0% that so the blockchain is like another player<00:08:43.830> and<00:08:44.039> that<00:08:44.070> maybe<00:08:44.339> you've<00:08:44.520> replaced 00:08:44.840 --> 00:08:44.850 align:start position:0% player and that maybe you've replaced 00:08:44.850 --> 00:08:46.250 align:start position:0% player and that maybe you've replaced your<00:08:45.030> server<00:08:45.240> with<00:08:45.420> the<00:08:45.450> blockchain<00:08:45.690> maybe 00:08:46.250 --> 00:08:46.260 align:start position:0% your server with the blockchain maybe 00:08:46.260 --> 00:08:47.420 align:start position:0% your server with the blockchain maybe you've<00:08:46.410> got<00:08:46.589> a<00:08:46.620> server<00:08:46.890> and<00:08:47.130> you've<00:08:47.280> got<00:08:47.400> a 00:08:47.420 --> 00:08:47.430 align:start position:0% you've got a server and you've got a 00:08:47.430 --> 00:08:50.090 align:start position:0% you've got a server and you've got a blockchain<00:08:48.200> we've<00:08:49.200> now<00:08:49.350> got<00:08:49.560> multiple<00:08:49.920> places 00:08:50.090 --> 00:08:50.100 align:start position:0% blockchain we've now got multiple places 00:08:50.100 --> 00:08:52.220 align:start position:0% blockchain we've now got multiple places these<00:08:50.430> updates<00:08:50.790> can<00:08:50.910> come<00:08:51.089> from<00:08:51.240> and<00:08:51.540> state 00:08:52.220 --> 00:08:52.230 align:start position:0% these updates can come from and state 00:08:52.230 --> 00:08:55.730 align:start position:0% these updates can come from and state channels<00:08:52.680> add<00:08:53.060> yet<00:08:54.060> another<00:08:54.350> place<00:08:55.350> where 00:08:55.730 --> 00:08:55.740 align:start position:0% channels add yet another place where 00:08:55.740 --> 00:08:56.090 align:start position:0% channels add yet another place where those 00:08:56.090 --> 00:08:56.100 align:start position:0% those 00:08:56.100 --> 00:08:57.949 align:start position:0% those dates<00:08:56.310> can<00:08:56.490> come<00:08:56.730> from<00:08:56.880> and<00:08:57.209> in<00:08:57.630> a<00:08:57.720> state 00:08:57.949 --> 00:08:57.959 align:start position:0% dates can come from and in a state 00:08:57.959 --> 00:09:00.110 align:start position:0% dates can come from and in a state channel<00:08:58.319> your<00:08:58.470> whole<00:08:58.649> logic<00:08:58.889> is<00:08:59.250> around<00:08:59.579> I'm 00:09:00.110 --> 00:09:00.120 align:start position:0% channel your whole logic is around I'm 00:09:00.120 --> 00:09:01.910 align:start position:0% channel your whole logic is around I'm receiving<00:09:00.839> these<00:09:01.170> states<00:09:01.500> from<00:09:01.740> my 00:09:01.910 --> 00:09:01.920 align:start position:0% receiving these states from my 00:09:01.920 --> 00:09:04.610 align:start position:0% receiving these states from my counterparty<00:09:02.720> and<00:09:03.720> therefore<00:09:04.259> I<00:09:04.290> can<00:09:04.500> like 00:09:04.610 --> 00:09:04.620 align:start position:0% counterparty and therefore I can like 00:09:04.620 --> 00:09:05.990 align:start position:0% counterparty and therefore I can like reason<00:09:04.920> about<00:09:05.069> what's<00:09:05.279> happening<00:09:05.610> on<00:09:05.730> chain 00:09:05.990 --> 00:09:06.000 align:start position:0% reason about what's happening on chain 00:09:06.000 --> 00:09:08.900 align:start position:0% reason about what's happening on chain and<00:09:06.300> that<00:09:06.630> just<00:09:06.810> gets<00:09:06.990> very<00:09:07.079> complicated<00:09:07.910> to 00:09:08.900 --> 00:09:08.910 align:start position:0% and that just gets very complicated to 00:09:08.910 --> 00:09:11.840 align:start position:0% and that just gets very complicated to think<00:09:09.569> about<00:09:09.810> and<00:09:10.170> stuff<00:09:10.500> so<00:09:10.829> like<00:09:10.980> we're<00:09:11.670> now 00:09:11.840 --> 00:09:11.850 align:start position:0% think about and stuff so like we're now 00:09:11.850 --> 00:09:13.730 align:start position:0% think about and stuff so like we're now thinking<00:09:12.269> about<00:09:12.420> this<00:09:12.870> thinking<00:09:13.440> about<00:09:13.560> how 00:09:13.730 --> 00:09:13.740 align:start position:0% thinking about this thinking about how 00:09:13.740 --> 00:09:15.499 align:start position:0% thinking about this thinking about how we<00:09:13.800> can<00:09:13.980> make<00:09:14.100> it<00:09:14.250> simpler<00:09:14.579> thinking<00:09:15.329> about 00:09:15.499 --> 00:09:15.509 align:start position:0% we can make it simpler thinking about 00:09:15.509 --> 00:09:17.240 align:start position:0% we can make it simpler thinking about how<00:09:15.750> we<00:09:15.810> can<00:09:15.990> take<00:09:16.050> this<00:09:16.500> thing<00:09:16.560> which<00:09:16.920> seems 00:09:17.240 --> 00:09:17.250 align:start position:0% how we can take this thing which seems 00:09:17.250 --> 00:09:20.329 align:start position:0% how we can take this thing which seems in<00:09:17.519> some<00:09:17.730> way<00:09:17.910> inherently<00:09:18.870> complex<00:09:19.110> and<00:09:19.680> work 00:09:20.329 --> 00:09:20.339 align:start position:0% in some way inherently complex and work 00:09:20.339 --> 00:09:21.620 align:start position:0% in some way inherently complex and work with<00:09:20.579> it<00:09:20.699> better<00:09:20.880> think<00:09:21.209> you<00:09:21.329> have<00:09:21.420> better 00:09:21.620 --> 00:09:21.630 align:start position:0% with it better think you have better 00:09:21.630 --> 00:09:24.230 align:start position:0% with it better think you have better ways<00:09:21.899> to<00:09:21.959> manage<00:09:22.440> this<00:09:22.769> complexity<00:09:23.519> in<00:09:23.759> the 00:09:24.230 --> 00:09:24.240 align:start position:0% ways to manage this complexity in the 00:09:24.240 --> 00:09:27.470 align:start position:0% ways to manage this complexity in the applications<00:09:24.949> so<00:09:25.949> final<00:09:26.279> plug<00:09:26.430> so<00:09:26.910> this<00:09:27.089> the 00:09:27.470 --> 00:09:27.480 align:start position:0% applications so final plug so this the 00:09:27.480 --> 00:09:29.960 align:start position:0% applications so final plug so this the code<00:09:27.660> you<00:09:27.779> saw<00:09:27.930> today<00:09:28.079> the<00:09:28.769> demonstration 00:09:29.960 --> 00:09:29.970 align:start position:0% code you saw today the demonstration 00:09:29.970 --> 00:09:32.600 align:start position:0% code you saw today the demonstration it<00:09:30.029> is<00:09:30.449> currently<00:09:30.839> live<00:09:31.079> on<00:09:31.110> Rob<00:09:31.649> stone<00:09:31.889> so<00:09:32.519> you 00:09:32.600 --> 00:09:32.610 align:start position:0% it is currently live on Rob stone so you 00:09:32.610 --> 00:09:37.249 align:start position:0% it is currently live on Rob stone so you can<00:09:32.759> visit<00:09:32.940> it<00:09:33.180> at<00:09:33.389> magno<00:09:33.779> calm<00:09:34.230> slash<00:09:34.649> RPS<00:09:36.259> in 00:09:37.249 --> 00:09:37.259 align:start position:0% can visit it at magno calm slash RPS in 00:09:37.259 --> 00:09:39.230 align:start position:0% can visit it at magno calm slash RPS in case<00:09:37.680> you<00:09:37.829> don't<00:09:37.949> find<00:09:38.220> any<00:09:38.370> friends<00:09:38.790> there<00:09:39.000> we 00:09:39.230 --> 00:09:39.240 align:start position:0% case you don't find any friends there we 00:09:39.240 --> 00:09:41.079 align:start position:0% case you don't find any friends there we have<00:09:39.420> some<00:09:39.630> bots<00:09:39.899> that<00:09:40.050> you<00:09:40.199> can<00:09:40.350> play<00:09:40.529> against 00:09:41.079 --> 00:09:41.089 align:start position:0% have some bots that you can play against 00:09:41.089 --> 00:09:44.300 align:start position:0% have some bots that you can play against they<00:09:42.089> get<00:09:42.269> progressively<00:09:42.509> harder 00:09:44.300 --> 00:09:44.310 align:start position:0% they get progressively harder 00:09:44.310 --> 00:09:47.990 align:start position:0% they get progressively harder the<00:09:44.970> final<00:09:45.389> bot<00:09:45.630> is<00:09:45.899> the<00:09:46.199> psychic<00:09:46.680> bot<00:09:46.920> and<00:09:47.250> if 00:09:47.990 --> 00:09:48.000 align:start position:0% the final bot is the psychic bot and if 00:09:48.000 --> 00:09:49.939 align:start position:0% the final bot is the psychic bot and if you<00:09:48.089> can<00:09:48.269> beat<00:09:48.540> the<00:09:48.720> psychic<00:09:49.170> bot<00:09:49.380> we<00:09:49.620> want<00:09:49.829> to 00:09:49.939 --> 00:09:49.949 align:start position:0% you can beat the psychic bot we want to 00:09:49.949 --> 00:09:53.870 align:start position:0% you can beat the psychic bot we want to hear<00:09:50.130> from<00:09:50.339> you<00:09:50.779> you'll<00:09:51.779> get<00:09:51.959> like<00:09:52.170> I'll<00:09:52.880> give 00:09:53.870 --> 00:09:53.880 align:start position:0% hear from you you'll get like I'll give 00:09:53.880 --> 00:09:55.939 align:start position:0% hear from you you'll get like I'll give you<00:09:53.970> a<00:09:54.029> Twitter<00:09:54.300> shout-out<00:09:54.839> prizes<00:09:55.740> prizes 00:09:55.939 --> 00:09:55.949 align:start position:0% you a Twitter shout-out prizes prizes 00:09:55.949 --> 00:09:58.220 align:start position:0% you a Twitter shout-out prizes prizes are<00:09:56.310> limited<00:09:56.670> but<00:09:56.940> you'll<00:09:57.060> get<00:09:57.209> like<00:09:57.449> small 00:09:58.220 --> 00:09:58.230 align:start position:0% are limited but you'll get like small 00:09:58.230 --> 00:09:59.840 align:start position:0% are limited but you'll get like small fleeting<00:09:58.680> honor<00:09:58.860> in<00:09:59.069> terms<00:09:59.220> of<00:09:59.459> a<00:09:59.519> magnet 00:09:59.840 --> 00:09:59.850 align:start position:0% fleeting honor in terms of a magnet 00:09:59.850 --> 00:10:02.509 align:start position:0% fleeting honor in terms of a magnet Twitter<00:10:00.060> shout-out<00:10:00.509> I<00:10:01.279> think<00:10:02.279> I'm<00:10:02.339> out<00:10:02.459> of 00:10:02.509 --> 00:10:02.519 align:start position:0% Twitter shout-out I think I'm out of 00:10:02.519 --> 00:10:04.249 align:start position:0% Twitter shout-out I think I'm out of time<00:10:02.699> though<00:10:03.300> thanks<00:10:03.630> for<00:10:03.720> listening 00:10:04.249 --> 00:10:04.259 align:start position:0% time though thanks for listening 00:10:04.259 --> 00:10:16.560 align:start position:0% time though thanks for listening you<00:10:04.470> can<00:10:04.589> follow<00:10:04.709> us<00:10:04.949> at<00:10:05.130> magma<00:10:05.459> HQ<00:10:05.880> on<00:10:05.970> Twitter 00:10:16.560 --> 00:10:16.570 align:start position:0% 00:10:16.570 --> 00:10:18.630 align:start position:0% you