WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:17.510 align:start position:0% [Music] 00:00:17.510 --> 00:00:17.520 align:start position:0% 00:00:17.520 --> 00:00:39.970 align:start position:0% [Applause] 00:00:39.970 --> 00:00:39.980 align:start position:0% 00:00:39.980 --> 00:00:44.390 align:start position:0% okay<00:00:41.180> so<00:00:42.180> hi<00:00:42.750> everyone<00:00:43.020> my<00:00:43.800> name<00:00:43.950> is<00:00:43.980> el<00:00:44.220> gusto 00:00:44.390 --> 00:00:44.400 align:start position:0% okay so hi everyone my name is el gusto 00:00:44.400 --> 00:00:46.310 align:start position:0% okay so hi everyone my name is el gusto I<00:00:44.730> have<00:00:45.239> been<00:00:45.420> working<00:00:45.750> with<00:00:45.930> the<00:00:46.020> Radian 00:00:46.310 --> 00:00:46.320 align:start position:0% I have been working with the Radian 00:00:46.320 --> 00:00:48.740 align:start position:0% I have been working with the Radian project<00:00:46.680> for<00:00:46.860> the<00:00:46.920> past<00:00:47.130> two<00:00:47.309> years<00:00:47.520> and<00:00:47.850> today 00:00:48.740 --> 00:00:48.750 align:start position:0% project for the past two years and today 00:00:48.750 --> 00:00:50.450 align:start position:0% project for the past two years and today I'm<00:00:48.840> going<00:00:48.989> to<00:00:49.050> present<00:00:49.230> to<00:00:49.470> you<00:00:49.590> guys<00:00:49.620> what<00:00:50.309> we 00:00:50.450 --> 00:00:50.460 align:start position:0% I'm going to present to you guys what we 00:00:50.460 --> 00:00:53.330 align:start position:0% I'm going to present to you guys what we have<00:00:50.670> done<00:00:51.600> for<00:00:51.960> the<00:00:52.080> past<00:00:52.200> year<00:00:52.530> and<00:00:52.559> what<00:00:53.220> is 00:00:53.330 --> 00:00:53.340 align:start position:0% have done for the past year and what is 00:00:53.340 --> 00:00:55.580 align:start position:0% have done for the past year and what is included<00:00:53.850> in<00:00:54.030> Developer<00:00:54.510> Preview<00:00:54.660> so<00:00:55.379> for 00:00:55.580 --> 00:00:55.590 align:start position:0% included in Developer Preview so for 00:00:55.590 --> 00:00:57.619 align:start position:0% included in Developer Preview so for those<00:00:55.739> of<00:00:55.920> you<00:00:56.100> that<00:00:56.280> doesn't<00:00:56.489> know<00:00:56.760> our<00:00:57.000> Aidan 00:00:57.619 --> 00:00:57.629 align:start position:0% those of you that doesn't know our Aidan 00:00:57.629 --> 00:00:59.960 align:start position:0% those of you that doesn't know our Aidan is<00:00:58.110> Ana<00:00:58.620> scalability<00:00:58.949> solution<00:00:59.580> that<00:00:59.699> we<00:00:59.820> have 00:00:59.960 --> 00:00:59.970 align:start position:0% is Ana scalability solution that we have 00:00:59.970 --> 00:01:02.180 align:start position:0% is Ana scalability solution that we have built<00:01:00.150> for<00:01:00.390> idiom<00:01:00.900> and<00:01:01.080> it<00:01:01.650> can<00:01:01.800> be<00:01:01.890> scaled<00:01:02.070> to 00:01:02.180 --> 00:01:02.190 align:start position:0% built for idiom and it can be scaled to 00:01:02.190 --> 00:01:04.250 align:start position:0% built for idiom and it can be scaled to a<00:01:02.460> padded<00:01:02.820> million<00:01:03.120> of<00:01:03.570> transactions<00:01:04.199> per 00:01:04.250 --> 00:01:04.260 align:start position:0% a padded million of transactions per 00:01:04.260 --> 00:01:06.980 align:start position:0% a padded million of transactions per second<00:01:04.680> okay<00:01:05.519> so<00:01:06.030> I'm<00:01:06.390> gonna<00:01:06.600> give<00:01:06.869> you<00:01:06.960> a 00:01:06.980 --> 00:01:06.990 align:start position:0% second okay so I'm gonna give you a 00:01:06.990 --> 00:01:09.230 align:start position:0% second okay so I'm gonna give you a quick<00:01:07.200> agenda<00:01:07.440> of<00:01:07.710> my<00:01:07.950> talk<00:01:08.160> this<00:01:08.940> is<00:01:09.000> going<00:01:09.180> to 00:01:09.230 --> 00:01:09.240 align:start position:0% quick agenda of my talk this is going to 00:01:09.240 --> 00:01:11.150 align:start position:0% quick agenda of my talk this is going to be<00:01:09.360> split<00:01:09.540> into<00:01:09.900> parts<00:01:10.229> and<00:01:10.530> the<00:01:10.770> first<00:01:10.979> ten 00:01:11.150 --> 00:01:11.160 align:start position:0% be split into parts and the first ten 00:01:11.160 --> 00:01:12.469 align:start position:0% be split into parts and the first ten minutes<00:01:11.190> I'm<00:01:11.550> going<00:01:11.700> to<00:01:11.759> talk<00:01:11.880> about<00:01:12.030> Radin 00:01:12.469 --> 00:01:12.479 align:start position:0% minutes I'm going to talk about Radin 00:01:12.479 --> 00:01:15.200 align:start position:0% minutes I'm going to talk about Radin and<00:01:12.660> the<00:01:13.110> second<00:01:13.440> half<00:01:13.649> for<00:01:13.979> this<00:01:14.430> the<00:01:15.030> last 00:01:15.200 --> 00:01:15.210 align:start position:0% and the second half for this the last 00:01:15.210 --> 00:01:16.700 align:start position:0% and the second half for this the last ten<00:01:15.360> minutes<00:01:15.509> we<00:01:16.140> are<00:01:16.229> going<00:01:16.350> to<00:01:16.410> talk<00:01:16.590> about 00:01:16.700 --> 00:01:16.710 align:start position:0% ten minutes we are going to talk about 00:01:16.710 --> 00:01:19.550 align:start position:0% ten minutes we are going to talk about the<00:01:16.890> micro<00:01:17.130> rating<00:01:17.430> so<00:01:18.119> for<00:01:18.479> the<00:01:18.630> raiden<00:01:19.320> we're 00:01:19.550 --> 00:01:19.560 align:start position:0% the micro rating so for the raiden we're 00:01:19.560 --> 00:01:22.580 align:start position:0% the micro rating so for the raiden we're gonna<00:01:19.710> talk<00:01:19.979> about<00:01:20.610> the<00:01:20.759> Radian<00:01:21.210> api's<00:01:21.590> rating 00:01:22.580 --> 00:01:22.590 align:start position:0% gonna talk about the Radian api's rating 00:01:22.590 --> 00:01:26.570 align:start position:0% gonna talk about the Radian api's rating is<00:01:22.710> exposing<00:01:23.369> an<00:01:23.910> HTTP<00:01:24.649> restful<00:01:25.649> api<00:01:25.890> so<00:01:26.399> that 00:01:26.570 --> 00:01:26.580 align:start position:0% is exposing an HTTP restful api so that 00:01:26.580 --> 00:01:27.650 align:start position:0% is exposing an HTTP restful api so that you<00:01:26.670> guys<00:01:26.820> can<00:01:27.030> use<00:01:27.180> to<00:01:27.360> build<00:01:27.450> applications 00:01:27.650 --> 00:01:27.660 align:start position:0% you guys can use to build applications 00:01:27.660 --> 00:01:29.690 align:start position:0% you guys can use to build applications on<00:01:28.050> top<00:01:28.229> of<00:01:28.380> it<00:01:28.500> and<00:01:28.710> at<00:01:29.190> the<00:01:29.220> go<00:01:29.399> of<00:01:29.520> my 00:01:29.690 --> 00:01:29.700 align:start position:0% on top of it and at the go of my 00:01:29.700 --> 00:01:31.790 align:start position:0% on top of it and at the go of my presentation<00:01:30.240> today<00:01:30.390> is<00:01:30.690> to<00:01:31.110> explain<00:01:31.170> to<00:01:31.440> of 00:01:31.790 --> 00:01:31.800 align:start position:0% presentation today is to explain to of 00:01:31.800 --> 00:01:34.249 align:start position:0% presentation today is to explain to of you<00:01:32.130> how<00:01:32.729> you<00:01:32.789> can<00:01:32.970> use<00:01:33.180> Radian<00:01:33.539> to<00:01:33.660> be<00:01:33.810> build 00:01:34.249 --> 00:01:34.259 align:start position:0% you how you can use Radian to be build 00:01:34.259 --> 00:01:37.310 align:start position:0% you how you can use Radian to be build apps<00:01:34.560> and<00:01:34.920> of<00:01:35.580> that<00:01:36.360> regard<00:01:36.780> we're<00:01:37.080> going<00:01:37.229> to 00:01:37.310 --> 00:01:37.320 align:start position:0% apps and of that regard we're going to 00:01:37.320 --> 00:01:39.560 align:start position:0% apps and of that regard we're going to talk<00:01:37.530> about<00:01:37.680> how<00:01:38.009> can<00:01:38.070> you<00:01:38.340> join<00:01:38.550> the<00:01:39.420> rail 00:01:39.560 --> 00:01:39.570 align:start position:0% talk about how can you join the rail 00:01:39.570 --> 00:01:41.900 align:start position:0% talk about how can you join the rail network<00:01:39.950> once<00:01:40.950> you<00:01:41.130> have<00:01:41.310> joined<00:01:41.490> the<00:01:41.670> radio 00:01:41.900 --> 00:01:41.910 align:start position:0% network once you have joined the radio 00:01:41.910 --> 00:01:43.760 align:start position:0% network once you have joined the radio network<00:01:42.030> how<00:01:42.810> can<00:01:42.960> you<00:01:43.020> make<00:01:43.170> transfers<00:01:43.560> and 00:01:43.760 --> 00:01:43.770 align:start position:0% network how can you make transfers and 00:01:43.770 --> 00:01:46.130 align:start position:0% network how can you make transfers and how<00:01:44.280> can<00:01:44.340> you<00:01:44.550> react<00:01:44.910> to<00:01:45.270> transfer<00:01:45.630> that<00:01:45.750> you 00:01:46.130 --> 00:01:46.140 align:start position:0% how can you react to transfer that you 00:01:46.140 --> 00:01:46.999 align:start position:0% how can you react to transfer that you know<00:01:46.289> it<00:01:46.349> has<00:01:46.500> received 00:01:46.999 --> 00:01:47.009 align:start position:0% know it has received 00:01:47.009 --> 00:01:49.850 align:start position:0% know it has received so<00:01:47.789> that's<00:01:48.000> agenda<00:01:48.450> so<00:01:49.020> first<00:01:49.410> things<00:01:49.770> first 00:01:49.850 --> 00:01:49.860 align:start position:0% so that's agenda so first things first 00:01:49.860 --> 00:01:52.669 align:start position:0% so that's agenda so first things first the<00:01:50.490> setup<00:01:50.819> phase<00:01:51.030> so<00:01:51.750> written<00:01:52.080> is<00:01:52.200> an<00:01:52.319> open 00:01:52.669 --> 00:01:52.679 align:start position:0% the setup phase so written is an open 00:01:52.679 --> 00:01:54.620 align:start position:0% the setup phase so written is an open source<00:01:52.890> project<00:01:53.160> we<00:01:53.670> have<00:01:53.849> it<00:01:54.000> available<00:01:54.270> in 00:01:54.620 --> 00:01:54.630 align:start position:0% source project we have it available in 00:01:54.630 --> 00:01:57.350 align:start position:0% source project we have it available in github<00:01:54.810> and<00:01:55.259> under<00:01:56.130> the<00:01:56.220> release<00:01:56.490> basic<00:01:57.030> pages 00:01:57.350 --> 00:01:57.360 align:start position:0% github and under the release basic pages 00:01:57.360 --> 00:01:59.870 align:start position:0% github and under the release basic pages we<00:01:57.720> have<00:01:57.929> an<00:01:58.709> app<00:01:58.920> image<00:01:59.250> that<00:01:59.459> any<00:01:59.640> of<00:01:59.789> you 00:01:59.870 --> 00:01:59.880 align:start position:0% we have an app image that any of you 00:01:59.880 --> 00:02:01.999 align:start position:0% we have an app image that any of you guys<00:02:00.000> can<00:02:00.240> use<00:02:00.569> from<00:02:00.780> cell<00:02:00.990> Rayden<00:02:01.319> it's<00:02:01.770> an 00:02:01.999 --> 00:02:02.009 align:start position:0% guys can use from cell Rayden it's an 00:02:02.009 --> 00:02:03.499 align:start position:0% guys can use from cell Rayden it's an executable<00:02:02.520> you<00:02:02.640> can<00:02:02.789> just<00:02:02.940> download<00:02:03.030> and 00:02:03.499 --> 00:02:03.509 align:start position:0% executable you can just download and 00:02:03.509 --> 00:02:06.800 align:start position:0% executable you can just download and start<00:02:03.959> running<00:02:04.830> in<00:02:04.920> your<00:02:05.069> machine<00:02:05.569> right<00:02:06.569> now 00:02:06.800 --> 00:02:06.810 align:start position:0% start running in your machine right now 00:02:06.810 --> 00:02:09.469 align:start position:0% start running in your machine right now Rayden<00:02:07.560> only<00:02:07.830> works<00:02:08.039> on<00:02:08.160> Linux<00:02:08.520> we<00:02:09.090> are<00:02:09.149> fixing 00:02:09.469 --> 00:02:09.479 align:start position:0% Rayden only works on Linux we are fixing 00:02:09.479 --> 00:02:13.040 align:start position:0% Rayden only works on Linux we are fixing some<00:02:09.720> issues<00:02:10.110> with<00:02:10.289> Mac<00:02:10.500> OS<00:02:10.530> in<00:02:11.069> a<00:02:11.459> week<00:02:11.670> in<00:02:12.330> the 00:02:13.040 --> 00:02:13.050 align:start position:0% some issues with Mac OS in a week in the 00:02:13.050 --> 00:02:14.960 align:start position:0% some issues with Mac OS in a week in the next<00:02:13.290> release<00:02:13.530> you<00:02:14.099> should<00:02:14.280> be<00:02:14.400> able<00:02:14.580> to<00:02:14.760> use 00:02:14.960 --> 00:02:14.970 align:start position:0% next release you should be able to use 00:02:14.970 --> 00:02:17.570 align:start position:0% next release you should be able to use Radian<00:02:15.360> on<00:02:15.480> Mac<00:02:15.690> OS<00:02:15.989> q<00:02:16.140> for<00:02:17.069> the<00:02:17.160> moment<00:02:17.430> we 00:02:17.570 --> 00:02:17.580 align:start position:0% Radian on Mac OS q for the moment we 00:02:17.580 --> 00:02:20.930 align:start position:0% Radian on Mac OS q for the moment we don't<00:02:17.730> support<00:02:18.090> Windows<00:02:18.620> and<00:02:19.620> also<00:02:20.430> I<00:02:20.670> want<00:02:20.910> to 00:02:20.930 --> 00:02:20.940 align:start position:0% don't support Windows and also I want to 00:02:20.940 --> 00:02:22.550 align:start position:0% don't support Windows and also I want to point<00:02:21.000> out<00:02:21.270> that<00:02:21.599> Braden<00:02:21.930> is<00:02:22.110> not<00:02:22.290> an<00:02:22.440> eighth 00:02:22.550 --> 00:02:22.560 align:start position:0% point out that Braden is not an eighth 00:02:22.560 --> 00:02:25.760 align:start position:0% point out that Braden is not an eighth note<00:02:23.090> Radian<00:02:24.090> is<00:02:24.239> a<00:02:24.300> separate<00:02:24.989> process<00:02:25.230> that 00:02:25.760 --> 00:02:25.770 align:start position:0% note Radian is a separate process that 00:02:25.770 --> 00:02:27.979 align:start position:0% note Radian is a separate process that communicates<00:02:26.310> within<00:02:26.640> a<00:02:26.700> theory<00:02:26.970> node<00:02:27.180> so<00:02:27.780> to 00:02:27.979 --> 00:02:27.989 align:start position:0% communicates within a theory node so to 00:02:27.989 --> 00:02:29.930 align:start position:0% communicates within a theory node so to use<00:02:28.200> Braden<00:02:28.620> you<00:02:28.830> will<00:02:29.130> also<00:02:29.370> need<00:02:29.700> an 00:02:29.930 --> 00:02:29.940 align:start position:0% use Braden you will also need an 00:02:29.940 --> 00:02:31.280 align:start position:0% use Braden you will also need an ethereal<00:02:30.330> node<00:02:30.510> running<00:02:30.930> on<00:02:31.170> the<00:02:31.260> machine 00:02:31.280 --> 00:02:31.290 align:start position:0% ethereal node running on the machine 00:02:31.290 --> 00:02:34.520 align:start position:0% ethereal node running on the machine that<00:02:32.099> you're<00:02:32.520> working<00:02:32.819> on<00:02:33.060> and<00:02:33.239> for<00:02:34.140> that<00:02:34.260> for 00:02:34.520 --> 00:02:34.530 align:start position:0% that you're working on and for that for 00:02:34.530 --> 00:02:36.619 align:start position:0% that you're working on and for that for the<00:02:34.890> Brayton<00:02:35.099> process<00:02:35.849> to<00:02:36.000> communicate<00:02:36.420> with 00:02:36.619 --> 00:02:36.629 align:start position:0% the Brayton process to communicate with 00:02:36.629 --> 00:02:39.170 align:start position:0% the Brayton process to communicate with the<00:02:37.230> fear<00:02:37.440> node<00:02:37.650> we<00:02:38.040> you<00:02:38.340> will<00:02:38.550> need<00:02:38.730> to<00:02:39.000> enable 00:02:39.170 --> 00:02:39.180 align:start position:0% the fear node we you will need to enable 00:02:39.180 --> 00:02:41.390 align:start position:0% the fear node we you will need to enable JSON<00:02:39.660> RPC<00:02:39.800> because<00:02:40.800> that's<00:02:41.010> the<00:02:41.129> current 00:02:41.390 --> 00:02:41.400 align:start position:0% JSON RPC because that's the current 00:02:41.400 --> 00:02:44.180 align:start position:0% JSON RPC because that's the current interface<00:02:41.670> that<00:02:41.970> we<00:02:42.150> use<00:02:42.330> to<00:02:42.510> communicate<00:02:43.190> so 00:02:44.180 --> 00:02:44.190 align:start position:0% interface that we use to communicate so 00:02:44.190 --> 00:02:46.100 align:start position:0% interface that we use to communicate so once<00:02:44.550> you<00:02:44.670> have<00:02:44.819> this<00:02:44.970> set<00:02:45.120> up<00:02:45.270> then<00:02:45.480> let's 00:02:46.100 --> 00:02:46.110 align:start position:0% once you have this set up then let's 00:02:46.110 --> 00:02:47.840 align:start position:0% once you have this set up then let's decide<00:02:46.410> how<00:02:46.650> to<00:02:47.129> talk<00:02:47.280> about<00:02:47.430> how<00:02:47.640> you've 00:02:47.840 --> 00:02:47.850 align:start position:0% decide how to talk about how you've 00:02:47.850 --> 00:02:49.820 align:start position:0% decide how to talk about how you've written<00:02:48.090> so<00:02:48.780> the<00:02:48.900> first<00:02:49.080> thing<00:02:49.290> that<00:02:49.500> you<00:02:49.650> want 00:02:49.820 --> 00:02:49.830 align:start position:0% written so the first thing that you want 00:02:49.830 --> 00:02:51.620 align:start position:0% written so the first thing that you want to<00:02:49.920> do<00:02:50.070> once<00:02:50.460> you<00:02:50.580> have<00:02:50.610> read<00:02:50.970> installed<00:02:51.420> is 00:02:51.620 --> 00:02:51.630 align:start position:0% to do once you have read installed is 00:02:51.630 --> 00:02:53.420 align:start position:0% to do once you have read installed is you<00:02:52.020> can<00:02:52.140> actually<00:02:52.290> read<00:02:52.650> in<00:02:52.770> network 00:02:53.420 --> 00:02:53.430 align:start position:0% you can actually read in network 00:02:53.430 --> 00:02:55.550 align:start position:0% you can actually read in network and<00:02:53.610> the<00:02:54.150> Raiden<00:02:54.390> Network<00:02:54.720> in<00:02:55.110> the<00:02:55.290> in<00:02:55.470> the 00:02:55.550 --> 00:02:55.560 align:start position:0% and the Raiden Network in the in the 00:02:55.560 --> 00:02:57.710 align:start position:0% and the Raiden Network in the in the rating<00:02:55.830> process<00:02:56.010> we<00:02:56.790> have<00:02:57.000> to<00:02:57.209> api's<00:02:57.510> to 00:02:57.710 --> 00:02:57.720 align:start position:0% rating process we have to api's to 00:02:57.720 --> 00:03:00.020 align:start position:0% rating process we have to api's to connect<00:02:58.170> to<00:02:58.319> the<00:02:58.440> network<00:02:58.620> the<00:02:59.580> first<00:02:59.849> one 00:03:00.020 --> 00:03:00.030 align:start position:0% connect to the network the first one 00:03:00.030 --> 00:03:00.970 align:start position:0% connect to the network the first one that<00:03:00.150> I'm<00:03:00.269> going<00:03:00.299> to<00:03:00.450> present<00:03:00.569> to<00:03:00.810> you<00:03:00.870> guys 00:03:00.970 --> 00:03:00.980 align:start position:0% that I'm going to present to you guys 00:03:00.980 --> 00:03:03.800 align:start position:0% that I'm going to present to you guys it's<00:03:01.980> the<00:03:02.159> endpoint<00:03:02.580> for<00:03:02.730> connections<00:03:03.180> this 00:03:03.800 --> 00:03:03.810 align:start position:0% it's the endpoint for connections this 00:03:03.810 --> 00:03:06.350 align:start position:0% it's the endpoint for connections this is<00:03:04.019> an<00:03:04.470> automatic<00:03:05.040> way<00:03:05.610> of<00:03:05.819> setting<00:03:06.269> up 00:03:06.350 --> 00:03:06.360 align:start position:0% is an automatic way of setting up 00:03:06.360 --> 00:03:08.210 align:start position:0% is an automatic way of setting up channels<00:03:06.750> that<00:03:07.170> rating<00:03:07.560> is<00:03:07.650> going<00:03:07.860> to<00:03:07.980> manage 00:03:08.210 --> 00:03:08.220 align:start position:0% channels that rating is going to manage 00:03:08.220 --> 00:03:11.809 align:start position:0% channels that rating is going to manage for<00:03:08.400> you<00:03:08.489> guys<00:03:08.670> and<00:03:09.680> in<00:03:10.680> the<00:03:11.010> the<00:03:11.310> goal<00:03:11.489> of<00:03:11.610> this 00:03:11.809 --> 00:03:11.819 align:start position:0% for you guys and in the the goal of this 00:03:11.819 --> 00:03:14.259 align:start position:0% for you guys and in the the goal of this this<00:03:12.510> end<00:03:12.720> point<00:03:12.989> is<00:03:13.440> for<00:03:13.739> you<00:03:13.829> guys<00:03:13.860> to 00:03:14.259 --> 00:03:14.269 align:start position:0% this end point is for you guys to 00:03:14.269 --> 00:03:16.880 align:start position:0% this end point is for you guys to configure<00:03:15.269> Raiden<00:03:15.629> telling<00:03:16.110> how<00:03:16.230> much<00:03:16.409> token 00:03:16.880 --> 00:03:16.890 align:start position:0% configure Raiden telling how much token 00:03:16.890 --> 00:03:20.030 align:start position:0% configure Raiden telling how much token Raiden<00:03:17.730> should<00:03:17.970> use<00:03:18.239> to<00:03:18.900> manage<00:03:19.260> and<00:03:19.620> open 00:03:20.030 --> 00:03:20.040 align:start position:0% Raiden should use to manage and open 00:03:20.040 --> 00:03:22.309 align:start position:0% Raiden should use to manage and open channels<00:03:20.430> with<00:03:20.549> the<00:03:20.670> network<00:03:21.060> so<00:03:21.629> our<00:03:21.900> goal<00:03:22.140> is 00:03:22.309 --> 00:03:22.319 align:start position:0% channels with the network so our goal is 00:03:22.319 --> 00:03:24.710 align:start position:0% channels with the network so our goal is to<00:03:22.620> never<00:03:22.799> start<00:03:23.159> using<00:03:23.400> the<00:03:23.730> tokens<00:03:24.090> for<00:03:24.569> that 00:03:24.710 --> 00:03:24.720 align:start position:0% to never start using the tokens for that 00:03:24.720 --> 00:03:26.300 align:start position:0% to never start using the tokens for that account<00:03:24.989> that's<00:03:25.230> configured<00:03:25.530> with<00:03:25.950> Raiden 00:03:26.300 --> 00:03:26.310 align:start position:0% account that's configured with Raiden 00:03:26.310 --> 00:03:28.640 align:start position:0% account that's configured with Raiden without<00:03:26.910> user<00:03:27.239> permission<00:03:27.750> and<00:03:27.870> you<00:03:28.319> need<00:03:28.500> to 00:03:28.640 --> 00:03:28.650 align:start position:0% without user permission and you need to 00:03:28.650 --> 00:03:30.199 align:start position:0% without user permission and you need to use<00:03:28.769> that<00:03:28.799> endpoint<00:03:29.250> telling<00:03:29.760> us<00:03:29.879> how<00:03:30.060> much 00:03:30.199 --> 00:03:30.209 align:start position:0% use that endpoint telling us how much 00:03:30.209 --> 00:03:32.449 align:start position:0% use that endpoint telling us how much funds<00:03:30.510> do<00:03:30.660> you<00:03:30.750> want<00:03:30.930> to<00:03:31.049> use<00:03:31.230> once<00:03:32.190> you<00:03:32.310> have 00:03:32.449 --> 00:03:32.459 align:start position:0% funds do you want to use once you have 00:03:32.459 --> 00:03:35.270 align:start position:0% funds do you want to use once you have used<00:03:32.819> the<00:03:33.000> endpoint<00:03:33.450> Rana<00:03:34.230> knows<00:03:34.470> which<00:03:35.040> funds 00:03:35.270 --> 00:03:35.280 align:start position:0% used the endpoint Rana knows which funds 00:03:35.280 --> 00:03:37.699 align:start position:0% used the endpoint Rana knows which funds you<00:03:35.430> want<00:03:35.640> to<00:03:35.730> use<00:03:35.879> how<00:03:36.450> much<00:03:36.660> of<00:03:36.930> it<00:03:37.470> you're 00:03:37.699 --> 00:03:37.709 align:start position:0% you want to use how much of it you're 00:03:37.709 --> 00:03:39.860 align:start position:0% you want to use how much of it you're allowing<00:03:38.010> Raiden<00:03:38.459> to<00:03:38.609> use<00:03:38.790> and<00:03:39.030> then<00:03:39.510> reading 00:03:39.860 --> 00:03:39.870 align:start position:0% allowing Raiden to use and then reading 00:03:39.870 --> 00:03:41.420 align:start position:0% allowing Raiden to use and then reading will<00:03:40.049> manage<00:03:40.079> channels<00:03:40.769> for<00:03:40.980> you<00:03:41.099> on<00:03:41.370> your 00:03:41.420 --> 00:03:41.430 align:start position:0% will manage channels for you on your 00:03:41.430 --> 00:03:44.210 align:start position:0% will manage channels for you on your behalf<00:03:41.700> so<00:03:42.239> that's<00:03:43.109> the<00:03:43.500> automatic<00:03:43.590> channel 00:03:44.210 --> 00:03:44.220 align:start position:0% behalf so that's the automatic channel 00:03:44.220 --> 00:03:46.039 align:start position:0% behalf so that's the automatic channel management<00:03:44.459> you<00:03:45.000> can<00:03:45.150> use<00:03:45.299> it<00:03:45.480> with<00:03:45.659> the<00:03:45.780> port 00:03:46.039 --> 00:03:46.049 align:start position:0% management you can use it with the port 00:03:46.049 --> 00:03:48.710 align:start position:0% management you can use it with the port verb<00:03:46.290> in<00:03:46.530> the<00:03:46.950> API<00:03:47.340> one<00:03:47.760> connections<00:03:48.269> endpoint 00:03:48.710 --> 00:03:48.720 align:start position:0% verb in the API one connections endpoint 00:03:48.720 --> 00:03:50.869 align:start position:0% verb in the API one connections endpoint if<00:03:49.709> you<00:03:49.859> don't<00:03:50.040> want<00:03:50.220> to<00:03:50.310> use<00:03:50.459> the<00:03:50.609> automatic 00:03:50.869 --> 00:03:50.879 align:start position:0% if you don't want to use the automatic 00:03:50.879 --> 00:03:53.180 align:start position:0% if you don't want to use the automatic management<00:03:51.480> you<00:03:51.900> can<00:03:52.109> open<00:03:52.530> channels<00:03:52.890> by<00:03:52.980> hand 00:03:53.180 --> 00:03:53.190 align:start position:0% management you can open channels by hand 00:03:53.190 --> 00:03:56.030 align:start position:0% management you can open channels by hand that's<00:03:53.819> done<00:03:54.090> by<00:03:54.239> the<00:03:54.269> put<00:03:54.629> a<00:03:54.840> verb<00:03:55.379> in<00:03:55.650> the 00:03:56.030 --> 00:03:56.040 align:start position:0% that's done by the put a verb in the 00:03:56.040 --> 00:03:58.280 align:start position:0% that's done by the put a verb in the channels<00:03:56.430> endpoint<00:03:56.819> and<00:03:57.660> that's<00:03:57.959> basically 00:03:58.280 --> 00:03:58.290 align:start position:0% channels endpoint and that's basically 00:03:58.290 --> 00:03:59.509 align:start position:0% channels endpoint and that's basically the<00:03:58.440> same<00:03:58.590> thing<00:03:58.650> but<00:03:59.069> you're<00:03:59.280> going<00:03:59.430> to 00:03:59.509 --> 00:03:59.519 align:start position:0% the same thing but you're going to 00:03:59.519 --> 00:04:01.550 align:start position:0% the same thing but you're going to manage<00:03:59.760> the<00:03:59.910> channels<00:04:00.239> on<00:04:00.450> your<00:04:00.840> own<00:04:01.049> you<00:04:01.530> just 00:04:01.550 --> 00:04:01.560 align:start position:0% manage the channels on your own you just 00:04:01.560 --> 00:04:03.979 align:start position:0% manage the channels on your own you just specify<00:04:02.010> everything<00:04:02.940> that<00:04:03.269> you<00:04:03.419> want<00:04:03.660> you<00:04:03.780> use 00:04:03.979 --> 00:04:03.989 align:start position:0% specify everything that you want you use 00:04:03.989 --> 00:04:05.449 align:start position:0% specify everything that you want you use in<00:04:04.260> the<00:04:04.349> JSON<00:04:04.560> that's<00:04:04.859> going<00:04:05.040> to<00:04:05.099> be<00:04:05.190> sent<00:04:05.400> to 00:04:05.449 --> 00:04:05.459 align:start position:0% in the JSON that's going to be sent to 00:04:05.459 --> 00:04:08.300 align:start position:0% in the JSON that's going to be sent to the<00:04:05.609> server<00:04:05.790> and<00:04:06.120> the<00:04:06.930> Raiden<00:04:07.260> will<00:04:07.560> use<00:04:08.099> the 00:04:08.300 --> 00:04:08.310 align:start position:0% the server and the Raiden will use the 00:04:08.310 --> 00:04:10.099 align:start position:0% the server and the Raiden will use the data<00:04:08.400> that<00:04:08.549> you<00:04:08.760> provide<00:04:09.060> to<00:04:09.090> it<00:04:09.359> to<00:04:09.840> open 00:04:10.099 --> 00:04:10.109 align:start position:0% data that you provide to it to open 00:04:10.109 --> 00:04:11.930 align:start position:0% data that you provide to it to open channels<00:04:10.560> so<00:04:11.010> everything<00:04:11.430> like<00:04:11.609> the<00:04:11.790> token 00:04:11.930 --> 00:04:11.940 align:start position:0% channels so everything like the token 00:04:11.940 --> 00:04:13.909 align:start position:0% channels so everything like the token address<00:04:12.389> the<00:04:12.540> amount<00:04:12.720> of<00:04:12.810> funds<00:04:13.079> the<00:04:13.560> target 00:04:13.909 --> 00:04:13.919 align:start position:0% address the amount of funds the target 00:04:13.919 --> 00:04:15.800 align:start position:0% address the amount of funds the target know<00:04:14.069> that<00:04:14.280> you're<00:04:14.400> connecting<00:04:14.790> to<00:04:14.819> it's 00:04:15.800 --> 00:04:15.810 align:start position:0% know that you're connecting to it's 00:04:15.810 --> 00:04:19.039 align:start position:0% know that you're connecting to it's defined<00:04:16.139> by<00:04:16.260> you<00:04:16.549> so<00:04:17.599> these<00:04:18.599> are<00:04:18.780> the<00:04:18.900> two 00:04:19.039 --> 00:04:19.049 align:start position:0% defined by you so these are the two 00:04:19.049 --> 00:04:21.979 align:start position:0% defined by you so these are the two api's<00:04:19.410> for<00:04:20.039> connecting<00:04:20.549> to<00:04:20.729> the<00:04:21.299> network<00:04:21.329> once 00:04:21.979 --> 00:04:21.989 align:start position:0% api's for connecting to the network once 00:04:21.989 --> 00:04:23.210 align:start position:0% api's for connecting to the network once you<00:04:22.109> have<00:04:22.260> connected<00:04:22.500> to<00:04:22.800> a<00:04:22.860> network 00:04:23.210 --> 00:04:23.220 align:start position:0% you have connected to a network 00:04:23.220 --> 00:04:24.740 align:start position:0% you have connected to a network you<00:04:23.610> have<00:04:23.789> channels<00:04:24.180> available<00:04:24.270> to<00:04:24.630> be 00:04:24.740 --> 00:04:24.750 align:start position:0% you have channels available to be 00:04:24.750 --> 00:04:27.439 align:start position:0% you have channels available to be managed<00:04:25.160> the<00:04:26.160> way<00:04:26.280> that<00:04:26.460> you<00:04:26.550> can<00:04:26.729> manage<00:04:26.940> the 00:04:27.439 --> 00:04:27.449 align:start position:0% managed the way that you can manage the 00:04:27.449 --> 00:04:29.750 align:start position:0% managed the way that you can manage the channels<00:04:27.780> open<00:04:28.080> with<00:04:28.260> Raiden<00:04:28.620> is<00:04:28.770> by<00:04:29.310> using 00:04:29.750 --> 00:04:29.760 align:start position:0% channels open with Raiden is by using 00:04:29.760 --> 00:04:32.960 align:start position:0% channels open with Raiden is by using the<00:04:29.970> patch<00:04:30.440> keyword<00:04:31.440> the<00:04:31.680> patch<00:04:32.220> verb<00:04:32.580> for<00:04:32.880> the 00:04:32.960 --> 00:04:32.970 align:start position:0% the patch keyword the patch verb for the 00:04:32.970 --> 00:04:35.600 align:start position:0% the patch keyword the patch verb for the HTTP<00:04:33.570> and<00:04:33.750> now<00:04:34.349> you<00:04:34.650> can<00:04:34.830> then<00:04:35.039> patch<00:04:35.310> the 00:04:35.600 --> 00:04:35.610 align:start position:0% HTTP and now you can then patch the 00:04:35.610 --> 00:04:37.100 align:start position:0% HTTP and now you can then patch the current<00:04:35.880> status<00:04:36.090> of<00:04:36.270> your<00:04:36.449> channel<00:04:36.960> and 00:04:37.100 --> 00:04:37.110 align:start position:0% current status of your channel and 00:04:37.110 --> 00:04:39.290 align:start position:0% current status of your channel and increase<00:04:37.949> the<00:04:38.099> deposit<00:04:38.550> if<00:04:38.729> you<00:04:38.910> want<00:04:39.090> you 00:04:39.290 --> 00:04:39.300 align:start position:0% increase the deposit if you want you 00:04:39.300 --> 00:04:41.900 align:start position:0% increase the deposit if you want you have<00:04:39.330> more<00:04:39.840> funds<00:04:40.199> to<00:04:40.349> make<00:04:41.130> more<00:04:41.460> transfers 00:04:41.900 --> 00:04:41.910 align:start position:0% have more funds to make more transfers 00:04:41.910 --> 00:04:43.670 align:start position:0% have more funds to make more transfers or<00:04:42.389> you<00:04:42.539> can<00:04:42.690> change<00:04:43.020> the<00:04:43.199> state<00:04:43.380> of<00:04:43.530> the 00:04:43.670 --> 00:04:43.680 align:start position:0% or you can change the state of the 00:04:43.680 --> 00:04:46.189 align:start position:0% or you can change the state of the channel<00:04:43.860> by<00:04:44.280> closing<00:04:44.550> it<00:04:44.820> once<00:04:45.630> you<00:04:45.780> close<00:04:45.990> the 00:04:46.189 --> 00:04:46.199 align:start position:0% channel by closing it once you close the 00:04:46.199 --> 00:04:48.950 align:start position:0% channel by closing it once you close the channel<00:04:46.729> reading<00:04:47.729> will<00:04:47.970> automatically<00:04:48.630> wait 00:04:48.950 --> 00:04:48.960 align:start position:0% channel reading will automatically wait 00:04:48.960 --> 00:04:50.029 align:start position:0% channel reading will automatically wait for<00:04:49.139> the<00:04:49.229> settlement<00:04:49.530> period 00:04:50.029 --> 00:04:50.039 align:start position:0% for the settlement period 00:04:50.039 --> 00:04:52.460 align:start position:0% for the settlement period letsa<00:04:50.520> period<00:04:50.820> that<00:04:50.940> we<00:04:51.330> have<00:04:51.360> for<00:04:51.810> dispute 00:04:52.460 --> 00:04:52.470 align:start position:0% letsa period that we have for dispute 00:04:52.470 --> 00:04:54.620 align:start position:0% letsa period that we have for dispute resolution<00:04:52.650> and<00:04:53.280> once<00:04:53.729> the<00:04:53.940> dispute<00:04:54.360> is<00:04:54.510> over 00:04:54.620 --> 00:04:54.630 align:start position:0% resolution and once the dispute is over 00:04:54.630 --> 00:04:57.469 align:start position:0% resolution and once the dispute is over Raiden<00:04:55.560> will<00:04:55.770> withdraw<00:04:56.340> your<00:04:56.789> tokens<00:04:57.180> from 00:04:57.469 --> 00:04:57.479 align:start position:0% Raiden will withdraw your tokens from 00:04:57.479 --> 00:04:59.120 align:start position:0% Raiden will withdraw your tokens from the<00:04:57.570> channel<00:04:57.900> using<00:04:58.470> the<00:04:58.530> proofs<00:04:58.740> that<00:04:58.949> was 00:04:59.120 --> 00:04:59.130 align:start position:0% the channel using the proofs that was 00:04:59.130 --> 00:05:01.279 align:start position:0% the channel using the proofs that was available<00:04:59.729> by<00:05:00.060> both<00:05:00.330> of<00:05:00.570> the<00:05:00.720> parties<00:05:01.020> in<00:05:01.169> the 00:05:01.279 --> 00:05:01.289 align:start position:0% available by both of the parties in the 00:05:01.289 --> 00:05:03.740 align:start position:0% available by both of the parties in the in<00:05:01.680> the<00:05:01.860> channel<00:05:02.190> so<00:05:02.880> that's<00:05:03.300> everything<00:05:03.719> that 00:05:03.740 --> 00:05:03.750 align:start position:0% in the channel so that's everything that 00:05:03.750 --> 00:05:05.930 align:start position:0% in the channel so that's everything that we<00:05:03.990> need<00:05:04.140> to<00:05:04.260> know<00:05:04.380> on<00:05:04.680> how<00:05:04.710> to<00:05:05.130> connect<00:05:05.490> to<00:05:05.669> the 00:05:05.930 --> 00:05:05.940 align:start position:0% we need to know on how to connect to the 00:05:05.940 --> 00:05:07.309 align:start position:0% we need to know on how to connect to the radio<00:05:06.719> network 00:05:07.309 --> 00:05:07.319 align:start position:0% radio network 00:05:07.319 --> 00:05:09.529 align:start position:0% radio network and<00:05:07.559> once<00:05:08.069> you<00:05:08.159> have<00:05:08.369> connected<00:05:08.849> to<00:05:09.059> trade<00:05:09.389> and 00:05:09.529 --> 00:05:09.539 align:start position:0% and once you have connected to trade and 00:05:09.539 --> 00:05:11.540 align:start position:0% and once you have connected to trade and networking<00:05:09.899> or<00:05:10.050> have<00:05:10.169> channels<00:05:10.499> opened<00:05:10.770> you 00:05:11.540 --> 00:05:11.550 align:start position:0% networking or have channels opened you 00:05:11.550 --> 00:05:13.760 align:start position:0% networking or have channels opened you can<00:05:11.729> make<00:05:11.879> transfers<00:05:12.300> so<00:05:12.839> to<00:05:13.139> make<00:05:13.289> transfers 00:05:13.760 --> 00:05:13.770 align:start position:0% can make transfers so to make transfers 00:05:13.770 --> 00:05:16.070 align:start position:0% can make transfers so to make transfers you<00:05:14.189> can<00:05:14.339> use<00:05:14.490> the<00:05:14.669> post<00:05:14.909> verb<00:05:15.149> with<00:05:15.479> the 00:05:16.070 --> 00:05:16.080 align:start position:0% you can use the post verb with the 00:05:16.080 --> 00:05:19.399 align:start position:0% you can use the post verb with the transfers<00:05:16.499> and<00:05:16.740> end<00:05:17.279> point<00:05:17.550> and<00:05:17.930> that<00:05:18.930> an<00:05:19.080> end 00:05:19.399 --> 00:05:19.409 align:start position:0% transfers and end point and that an end 00:05:19.409 --> 00:05:21.769 align:start position:0% transfers and end point and that an end point<00:05:19.589> is<00:05:19.770> going<00:05:19.889> to<00:05:19.949> expose<00:05:20.639> you<00:05:20.879> guys<00:05:21.089> hash 00:05:21.769 --> 00:05:21.779 align:start position:0% point is going to expose you guys hash 00:05:21.779 --> 00:05:24.859 align:start position:0% point is going to expose you guys hash time<00:05:22.020> lock<00:05:22.490> mediated<00:05:23.490> transfers<00:05:23.879> so<00:05:24.569> hash 00:05:24.859 --> 00:05:24.869 align:start position:0% time lock mediated transfers so hash 00:05:24.869 --> 00:05:26.929 align:start position:0% time lock mediated transfers so hash time<00:05:25.050> locks<00:05:25.289> are<00:05:25.469> a<00:05:25.499> nice<00:05:25.860> abstraction<00:05:26.520> that 00:05:26.929 --> 00:05:26.939 align:start position:0% time locks are a nice abstraction that 00:05:26.939 --> 00:05:29.359 align:start position:0% time locks are a nice abstraction that we<00:05:27.059> can<00:05:27.300> use<00:05:27.479> and<00:05:27.749> that<00:05:28.289> makes<00:05:28.559> for<00:05:29.339> a 00:05:29.359 --> 00:05:29.369 align:start position:0% we can use and that makes for a 00:05:29.369 --> 00:05:32.149 align:start position:0% we can use and that makes for a concealable<00:05:29.969> and<00:05:30.119> expire<00:05:30.930> both<00:05:31.110> transfers<00:05:31.529> so 00:05:32.149 --> 00:05:32.159 align:start position:0% concealable and expire both transfers so 00:05:32.159 --> 00:05:35.029 align:start position:0% concealable and expire both transfers so that's<00:05:32.399> the<00:05:32.759> best<00:05:33.559> kind<00:05:34.559> of<00:05:34.619> transitions<00:05:35.009> that 00:05:35.029 --> 00:05:35.039 align:start position:0% that's the best kind of transitions that 00:05:35.039 --> 00:05:37.820 align:start position:0% that's the best kind of transitions that we<00:05:35.159> have<00:05:35.460> that<00:05:35.699> expose<00:05:36.089> the<00:05:36.569> nicest<00:05:37.080> error 00:05:37.820 --> 00:05:37.830 align:start position:0% we have that expose the nicest error 00:05:37.830 --> 00:05:39.170 align:start position:0% we have that expose the nicest error model<00:05:38.129> for<00:05:38.490> people<00:05:38.729> to<00:05:38.819> build<00:05:39.029> applications 00:05:39.170 --> 00:05:39.180 align:start position:0% model for people to build applications 00:05:39.180 --> 00:05:43.040 align:start position:0% model for people to build applications on<00:05:39.599> top<00:05:40.219> for<00:05:41.219> making<00:05:41.490> transfers<00:05:41.789> there<00:05:42.749> is<00:05:42.839> an 00:05:43.040 --> 00:05:43.050 align:start position:0% on top for making transfers there is an 00:05:43.050 --> 00:05:45.619 align:start position:0% on top for making transfers there is an important<00:05:43.619> detail<00:05:43.889> that<00:05:44.550> resin<00:05:44.909> is<00:05:45.119> not<00:05:45.300> part 00:05:45.619 --> 00:05:45.629 align:start position:0% important detail that resin is not part 00:05:45.629 --> 00:05:46.549 align:start position:0% important detail that resin is not part of<00:05:45.809> your<00:05:45.990> application 00:05:46.549 --> 00:05:46.559 align:start position:0% of your application 00:05:46.559 --> 00:05:48.589 align:start position:0% of your application Bradon<00:05:46.919> is<00:05:47.039> a<00:05:47.069> server<00:05:47.430> that's<00:05:47.999> running<00:05:48.119> on<00:05:48.539> a 00:05:48.589 --> 00:05:48.599 align:start position:0% Bradon is a server that's running on a 00:05:48.599 --> 00:05:49.579 align:start position:0% Bradon is a server that's running on a computer<00:05:48.689> that<00:05:49.259> you're<00:05:49.379> going<00:05:49.529> to 00:05:49.579 --> 00:05:49.589 align:start position:0% computer that you're going to 00:05:49.589 --> 00:05:52.429 align:start position:0% computer that you're going to communicate<00:05:49.889> through<00:05:50.279> recipe<00:05:50.819> ice<00:05:50.909> and<00:05:51.439> you 00:05:52.429 --> 00:05:52.439 align:start position:0% communicate through recipe ice and you 00:05:52.439 --> 00:05:54.379 align:start position:0% communicate through recipe ice and you need<00:05:52.619> to<00:05:52.709> provide<00:05:52.979> some<00:05:53.219> knowledge<00:05:53.459> or<00:05:53.789> some 00:05:54.379 --> 00:05:54.389 align:start position:0% need to provide some knowledge or some 00:05:54.389 --> 00:05:56.929 align:start position:0% need to provide some knowledge or some application<00:05:55.080> specific<00:05:55.559> data<00:05:55.800> to<00:05:56.399> read<00:05:56.580> in<00:05:56.729> so 00:05:56.929 --> 00:05:56.939 align:start position:0% application specific data to read in so 00:05:56.939 --> 00:05:58.489 align:start position:0% application specific data to read in so that<00:05:57.059> both<00:05:57.330> of<00:05:57.360> the<00:05:57.659> nodes<00:05:57.869> the<00:05:58.050> one<00:05:58.349> that 00:05:58.489 --> 00:05:58.499 align:start position:0% that both of the nodes the one that 00:05:58.499 --> 00:05:59.869 align:start position:0% that both of the nodes the one that Spain<00:05:58.770> and<00:05:58.949> the<00:05:59.009> one<00:05:59.219> that's<00:05:59.399> receiving<00:05:59.789> the 00:05:59.869 --> 00:05:59.879 align:start position:0% Spain and the one that's receiving the 00:05:59.879 --> 00:06:02.540 align:start position:0% Spain and the one that's receiving the payment<00:06:00.089> know<00:06:00.899> what<00:06:01.289> the<00:06:01.469> payment<00:06:01.830> is<00:06:01.919> regards 00:06:02.540 --> 00:06:02.550 align:start position:0% payment know what the payment is regards 00:06:02.550 --> 00:06:04.339 align:start position:0% payment know what the payment is regards you<00:06:02.759> so<00:06:03.330> let's<00:06:03.509> assume<00:06:03.779> that<00:06:03.839> you're<00:06:04.169> building 00:06:04.339 --> 00:06:04.349 align:start position:0% you so let's assume that you're building 00:06:04.349 --> 00:06:05.809 align:start position:0% you so let's assume that you're building an<00:06:04.589> e-commerce<00:06:04.709> application<00:06:05.490> or<00:06:05.610> something 00:06:05.809 --> 00:06:05.819 align:start position:0% an e-commerce application or something 00:06:05.819 --> 00:06:07.820 align:start position:0% an e-commerce application or something that<00:06:06.089> needs<00:06:06.330> to<00:06:06.449> make<00:06:06.569> a<00:06:06.629> payment<00:06:06.839> for<00:06:07.199> the 00:06:07.820 --> 00:06:07.830 align:start position:0% that needs to make a payment for the 00:06:07.830 --> 00:06:09.499 align:start position:0% that needs to make a payment for the e-commerce<00:06:08.099> application<00:06:08.759> you<00:06:08.909> can<00:06:09.059> give<00:06:09.360> an 00:06:09.499 --> 00:06:09.509 align:start position:0% e-commerce application you can give an 00:06:09.509 --> 00:06:11.929 align:start position:0% e-commerce application you can give an identifier<00:06:10.020> to<00:06:10.050> a<00:06:10.559> cart<00:06:10.949> and<00:06:11.189> I<00:06:11.699> use<00:06:11.909> that 00:06:11.929 --> 00:06:11.939 align:start position:0% identifier to a cart and I use that 00:06:11.939 --> 00:06:14.420 align:start position:0% identifier to a cart and I use that identifier<00:06:12.689> as<00:06:12.959> part<00:06:13.229> of<00:06:13.319> the<00:06:13.469> transfer<00:06:13.860> so 00:06:14.420 --> 00:06:14.430 align:start position:0% identifier as part of the transfer so 00:06:14.430 --> 00:06:15.829 align:start position:0% identifier as part of the transfer so that's<00:06:14.669> the<00:06:14.849> way<00:06:14.969> that<00:06:15.149> the<00:06:15.449> client 00:06:15.829 --> 00:06:15.839 align:start position:0% that's the way that the client 00:06:15.839 --> 00:06:18.369 align:start position:0% that's the way that the client application<00:06:15.959> can<00:06:16.529> tell<00:06:16.740> the<00:06:16.919> the<00:06:17.849> part<00:06:18.089> the 00:06:18.369 --> 00:06:18.379 align:start position:0% application can tell the the part the 00:06:18.379 --> 00:06:21.110 align:start position:0% application can tell the the part the node<00:06:19.379> that's<00:06:19.649> being<00:06:19.860> paid<00:06:20.099> what<00:06:20.699> the<00:06:20.819> payment 00:06:21.110 --> 00:06:21.120 align:start position:0% node that's being paid what the payment 00:06:21.120 --> 00:06:24.709 align:start position:0% node that's being paid what the payment is<00:06:21.209> about<00:06:22.099> currently<00:06:23.099> we<00:06:23.309> don't<00:06:23.430> allow<00:06:23.939> in<00:06:24.180> the 00:06:24.709 --> 00:06:24.719 align:start position:0% is about currently we don't allow in the 00:06:24.719 --> 00:06:26.869 align:start position:0% is about currently we don't allow in the current<00:06:25.080> version<00:06:25.379> of<00:06:25.439> the<00:06:25.499> API<00:06:26.039> which<00:06:26.580> is<00:06:26.729> an 00:06:26.869 --> 00:06:26.879 align:start position:0% current version of the API which is an 00:06:26.879 --> 00:06:28.759 align:start position:0% current version of the API which is an arbitrary<00:06:27.419> data<00:06:27.599> that<00:06:28.199> may<00:06:28.349> change<00:06:28.559> in<00:06:28.740> the 00:06:28.759 --> 00:06:28.769 align:start position:0% arbitrary data that may change in the 00:06:28.769 --> 00:06:30.230 align:start position:0% arbitrary data that may change in the future<00:06:28.830> that's<00:06:29.370> just<00:06:29.639> the<00:06:29.699> current<00:06:29.969> transport 00:06:30.230 --> 00:06:30.240 align:start position:0% future that's just the current transport 00:06:30.240 --> 00:06:33.049 align:start position:0% future that's just the current transport that<00:06:30.479> we<00:06:30.599> have<00:06:30.749> available<00:06:31.279> ok<00:06:32.279> so<00:06:32.339> once<00:06:32.759> you've 00:06:33.049 --> 00:06:33.059 align:start position:0% that we have available ok so once you've 00:06:33.059 --> 00:06:35.869 align:start position:0% that we have available ok so once you've made<00:06:33.269> transfers<00:06:34.080> that's<00:06:34.499> two<00:06:35.219> parts<00:06:35.610> of<00:06:35.699> the 00:06:35.869 --> 00:06:35.879 align:start position:0% made transfers that's two parts of the 00:06:35.879 --> 00:06:37.879 align:start position:0% made transfers that's two parts of the agenda<00:06:36.209> the<00:06:36.629> last<00:06:37.019> thing<00:06:37.349> that<00:06:37.379> you<00:06:37.619> want<00:06:37.649> to 00:06:37.879 --> 00:06:37.889 align:start position:0% agenda the last thing that you want to 00:06:37.889 --> 00:06:40.759 align:start position:0% agenda the last thing that you want to do<00:06:38.069> is<00:06:38.279> react<00:06:39.059> to<00:06:39.300> receiving<00:06:39.749> payments<00:06:40.259> for 00:06:40.759 --> 00:06:40.769 align:start position:0% do is react to receiving payments for 00:06:40.769 --> 00:06:42.859 align:start position:0% do is react to receiving payments for the<00:06:40.860> radio<00:06:41.219> network<00:06:41.339> and<00:06:41.849> that<00:06:42.360> can<00:06:42.569> be<00:06:42.749> done 00:06:42.859 --> 00:06:42.869 align:start position:0% the radio network and that can be done 00:06:42.869 --> 00:06:44.899 align:start position:0% the radio network and that can be done by<00:06:43.050> pulling<00:06:43.319> for<00:06:43.949> events<00:06:44.339> in<00:06:44.430> the<00:06:44.519> radio<00:06:44.729> node 00:06:44.899 --> 00:06:44.909 align:start position:0% by pulling for events in the radio node 00:06:44.909 --> 00:06:47.570 align:start position:0% by pulling for events in the radio node we<00:06:45.719> are<00:06:45.749> just<00:06:46.019> providing<00:06:46.199> a<00:06:46.529> simple<00:06:46.740> API<00:06:47.459> for 00:06:47.570 --> 00:06:47.580 align:start position:0% we are just providing a simple API for 00:06:47.580 --> 00:06:49.070 align:start position:0% we are just providing a simple API for the<00:06:47.789> moment<00:06:48.089> with<00:06:48.269> pulling<00:06:48.599> in<00:06:48.749> the<00:06:48.809> future 00:06:49.070 --> 00:06:49.080 align:start position:0% the moment with pulling in the future 00:06:49.080 --> 00:06:51.920 align:start position:0% the moment with pulling in the future view<00:06:49.259> we<00:06:49.979> will<00:06:50.159> add<00:06:50.399> maybe<00:06:51.209> a<00:06:51.330> long<00:06:51.449> pulling<00:06:51.839> or 00:06:51.920 --> 00:06:51.930 align:start position:0% view we will add maybe a long pulling or 00:06:51.930 --> 00:06:53.509 align:start position:0% view we will add maybe a long pulling or a<00:06:51.959> different<00:06:52.289> transport<00:06:52.740> that<00:06:53.009> can<00:06:53.279> push 00:06:53.509 --> 00:06:53.519 align:start position:0% a different transport that can push 00:06:53.519 --> 00:06:56.420 align:start position:0% a different transport that can push events<00:06:54.330> for<00:06:54.479> you<00:06:54.629> but<00:06:55.559> the<00:06:55.860> way<00:06:55.889> that<00:06:56.159> you<00:06:56.279> can 00:06:56.420 --> 00:06:56.430 align:start position:0% events for you but the way that you can 00:06:56.430 --> 00:06:58.549 align:start position:0% events for you but the way that you can react<00:06:56.699> to<00:06:56.759> payments<00:06:57.300> is<00:06:57.659> by<00:06:57.899> watching<00:06:58.319> for<00:06:58.499> the 00:06:58.549 --> 00:06:58.559 align:start position:0% react to payments is by watching for the 00:06:58.559 --> 00:07:00.889 align:start position:0% react to payments is by watching for the even<00:06:58.830> transfer<00:06:59.189> received<00:06:59.610> that<00:07:00.419> even<00:07:00.749> is 00:07:00.889 --> 00:07:00.899 align:start position:0% even transfer received that even is 00:07:00.899 --> 00:07:02.540 align:start position:0% even transfer received that even is emitted<00:07:01.379> every<00:07:01.680> time<00:07:01.860> that<00:07:02.069> you<00:07:02.189> receive<00:07:02.519> a 00:07:02.540 --> 00:07:02.550 align:start position:0% emitted every time that you receive a 00:07:02.550 --> 00:07:04.670 align:start position:0% emitted every time that you receive a payment<00:07:02.789> and<00:07:03.119> then<00:07:03.599> you<00:07:03.719> can<00:07:03.869> react<00:07:04.139> to<00:07:04.259> it<00:07:04.499> and 00:07:04.670 --> 00:07:04.680 align:start position:0% payment and then you can react to it and 00:07:04.680 --> 00:07:07.189 align:start position:0% payment and then you can react to it and that<00:07:05.430> event<00:07:05.699> will<00:07:05.879> have<00:07:06.119> the<00:07:06.360> identifier<00:07:06.930> and 00:07:07.189 --> 00:07:07.199 align:start position:0% that event will have the identifier and 00:07:07.199 --> 00:07:09.320 align:start position:0% that event will have the identifier and the<00:07:07.409> token<00:07:07.740> and<00:07:07.860> the<00:07:07.979> amount<00:07:08.189> of<00:07:08.399> the<00:07:08.999> transfer 00:07:09.320 --> 00:07:09.330 align:start position:0% the token and the amount of the transfer 00:07:09.330 --> 00:07:13.129 align:start position:0% the token and the amount of the transfer that<00:07:09.539> you<00:07:10.349> received<00:07:10.939> so<00:07:11.939> that's<00:07:12.899> everything 00:07:13.129 --> 00:07:13.139 align:start position:0% that you received so that's everything 00:07:13.139 --> 00:07:15.139 align:start position:0% that you received so that's everything that<00:07:13.409> you<00:07:13.499> need<00:07:13.680> to<00:07:13.709> know<00:07:13.949> about<00:07:14.849> the 00:07:15.139 --> 00:07:15.149 align:start position:0% that you need to know about the 00:07:15.149 --> 00:07:17.899 align:start position:0% that you need to know about the endpoints<00:07:15.719> available<00:07:16.379> in<00:07:16.469> Braden<00:07:16.740> and<00:07:17.129> with 00:07:17.899 --> 00:07:17.909 align:start position:0% endpoints available in Braden and with 00:07:17.909 --> 00:07:19.399 align:start position:0% endpoints available in Braden and with that<00:07:18.089> you<00:07:18.209> can<00:07:18.329> be<00:07:18.449> replications<00:07:18.990> on<00:07:19.110> top<00:07:19.259> of 00:07:19.399 --> 00:07:19.409 align:start position:0% that you can be replications on top of 00:07:19.409 --> 00:07:19.699 align:start position:0% that you can be replications on top of it 00:07:19.699 --> 00:07:19.709 align:start position:0% it 00:07:19.709 --> 00:07:20.170 align:start position:0% it that 00:07:20.170 --> 00:07:20.180 align:start position:0% that 00:07:20.180 --> 00:07:22.240 align:start position:0% that payments<00:07:20.600> using<00:07:20.870> the<00:07:20.960> brilliant<00:07:21.229> Network<00:07:21.500> so 00:07:22.240 --> 00:07:22.250 align:start position:0% payments using the brilliant Network so 00:07:22.250 --> 00:07:24.010 align:start position:0% payments using the brilliant Network so if<00:07:22.490> you<00:07:22.580> want<00:07:22.759> your<00:07:22.880> tears<00:07:23.030> Raylan<00:07:23.449> we 00:07:24.010 --> 00:07:24.020 align:start position:0% if you want your tears Raylan we 00:07:24.020 --> 00:07:26.200 align:start position:0% if you want your tears Raylan we currently<00:07:24.590> are<00:07:25.100> doing<00:07:25.130> a<00:07:25.550> Developer<00:07:26.090> Preview 00:07:26.200 --> 00:07:26.210 align:start position:0% currently are doing a Developer Preview 00:07:26.210 --> 00:07:28.749 align:start position:0% currently are doing a Developer Preview so<00:07:27.080> it's<00:07:27.650> not<00:07:27.800> available<00:07:28.190> in<00:07:28.280> the<00:07:28.460> manor 00:07:28.749 --> 00:07:28.759 align:start position:0% so it's not available in the manor 00:07:28.759 --> 00:07:30.550 align:start position:0% so it's not available in the manor it's<00:07:28.970> only<00:07:29.210> available<00:07:29.330> wraps<00:07:29.930> in<00:07:30.139> a<00:07:30.289> test 00:07:30.550 --> 00:07:30.560 align:start position:0% it's only available wraps in a test 00:07:30.560 --> 00:07:32.830 align:start position:0% it's only available wraps in a test network<00:07:30.860> and<00:07:31.100> on<00:07:31.789> the<00:07:31.880> robson<00:07:32.270> that<00:07:32.449> test 00:07:32.830 --> 00:07:32.840 align:start position:0% network and on the robson that test 00:07:32.840 --> 00:07:34.870 align:start position:0% network and on the robson that test network<00:07:33.199> we<00:07:33.350> have<00:07:33.380> deployed<00:07:34.220> hourly<00:07:34.580> rate<00:07:34.759> in 00:07:34.870 --> 00:07:34.880 align:start position:0% network we have deployed hourly rate in 00:07:34.880 --> 00:07:36.850 align:start position:0% network we have deployed hourly rate in our<00:07:35.150> smart<00:07:35.479> contracts<00:07:35.900> and<00:07:36.080> including<00:07:36.710> the 00:07:36.850 --> 00:07:36.860 align:start position:0% our smart contracts and including the 00:07:36.860 --> 00:07:38.980 align:start position:0% our smart contracts and including the Radian<00:07:37.100> test<00:07:37.310> open<00:07:37.639> and<00:07:38.030> with<00:07:38.600> the<00:07:38.720> Braeden 00:07:38.980 --> 00:07:38.990 align:start position:0% Radian test open and with the Braeden 00:07:38.990 --> 00:07:42.070 align:start position:0% Radian test open and with the Braeden test<00:07:39.169> open<00:07:39.440> we<00:07:39.860> have<00:07:40.240> made<00:07:41.240> available<00:07:41.360> a<00:07:41.780> mint 00:07:42.070 --> 00:07:42.080 align:start position:0% test open we have made available a mint 00:07:42.080 --> 00:07:44.110 align:start position:0% test open we have made available a mint method<00:07:42.470> that<00:07:43.039> are<00:07:43.190> you<00:07:43.280> can<00:07:43.430> use<00:07:43.639> to<00:07:43.910> mentor 00:07:44.110 --> 00:07:44.120 align:start position:0% method that are you can use to mentor 00:07:44.120 --> 00:07:46.330 align:start position:0% method that are you can use to mentor yourself<00:07:44.210> some<00:07:44.660> test<00:07:44.900> tokens<00:07:45.229> and<00:07:45.440> use<00:07:46.070> that 00:07:46.330 --> 00:07:46.340 align:start position:0% yourself some test tokens and use that 00:07:46.340 --> 00:07:48.610 align:start position:0% yourself some test tokens and use that test<00:07:46.610> token<00:07:46.940> to<00:07:47.180> make<00:07:47.720> payments<00:07:48.169> in<00:07:48.320> the<00:07:48.440> test 00:07:48.610 --> 00:07:48.620 align:start position:0% test token to make payments in the test 00:07:48.620 --> 00:07:52.060 align:start position:0% test token to make payments in the test network<00:07:48.979> so<00:07:49.970> once<00:07:50.419> you<00:07:50.600> have<00:07:50.800> used<00:07:51.800> the<00:07:51.919> brain 00:07:52.060 --> 00:07:52.070 align:start position:0% network so once you have used the brain 00:07:52.070 --> 00:07:54.219 align:start position:0% network so once you have used the brain best<00:07:52.340> tokens<00:07:52.669> you<00:07:52.789> get<00:07:53.330> yourself<00:07:53.690> some<00:07:53.870> tokens 00:07:54.219 --> 00:07:54.229 align:start position:0% best tokens you get yourself some tokens 00:07:54.229 --> 00:07:56.860 align:start position:0% best tokens you get yourself some tokens in<00:07:54.380> the<00:07:54.470> test<00:07:54.680> Network<00:07:55.009> you<00:07:55.880> can<00:07:55.910> connect<00:07:56.750> you 00:07:56.860 --> 00:07:56.870 align:start position:0% in the test Network you can connect you 00:07:56.870 --> 00:07:59.050 align:start position:0% in the test Network you can connect you some<00:07:57.050> notes<00:07:57.229> and<00:07:57.560> here<00:07:58.039> is<00:07:58.130> a<00:07:58.160> note<00:07:58.400> that<00:07:58.610> you 00:07:59.050 --> 00:07:59.060 align:start position:0% some notes and here is a note that you 00:07:59.060 --> 00:08:01.629 align:start position:0% some notes and here is a note that you may<00:07:59.419> try<00:07:59.720> to<00:07:59.750> use<00:08:00.080> we<00:08:00.590> have<00:08:00.740> made<00:08:00.949> it<00:08:01.099> it's<00:08:01.520> a 00:08:01.629 --> 00:08:01.639 align:start position:0% may try to use we have made it it's a 00:08:01.639 --> 00:08:03.310 align:start position:0% may try to use we have made it it's a programmable<00:08:02.030> node<00:08:02.630> that's<00:08:02.870> just<00:08:03.139> gonna 00:08:03.310 --> 00:08:03.320 align:start position:0% programmable node that's just gonna 00:08:03.320 --> 00:08:05.260 align:start position:0% programmable node that's just gonna reply<00:08:04.130> the<00:08:04.190> transfers<00:08:04.669> that<00:08:04.789> you<00:08:04.880> make<00:08:05.030> to<00:08:05.180> it 00:08:05.260 --> 00:08:05.270 align:start position:0% reply the transfers that you make to it 00:08:05.270 --> 00:08:07.390 align:start position:0% reply the transfers that you make to it with<00:08:05.509> a<00:08:05.539> transfer<00:08:06.080> of<00:08:06.229> the<00:08:06.650> same<00:08:06.830> amount<00:08:07.099> and 00:08:07.390 --> 00:08:07.400 align:start position:0% with a transfer of the same amount and 00:08:07.400 --> 00:08:09.370 align:start position:0% with a transfer of the same amount and same<00:08:07.880> token<00:08:08.120> the<00:08:08.419> case<00:08:08.599> the<00:08:08.750> radiant<00:08:09.050> desktop 00:08:09.370 --> 00:08:09.380 align:start position:0% same token the case the radiant desktop 00:08:09.380 --> 00:08:11.740 align:start position:0% same token the case the radiant desktop and<00:08:09.770> if<00:08:10.639> you<00:08:10.759> want<00:08:10.970> you<00:08:11.120> can<00:08:11.270> actually<00:08:11.599> test 00:08:11.740 --> 00:08:11.750 align:start position:0% and if you want you can actually test 00:08:11.750 --> 00:08:14.170 align:start position:0% and if you want you can actually test and<00:08:11.930> test<00:08:12.349> network<00:08:12.740> using<00:08:13.220> the<00:08:13.310> automatic 00:08:14.170 --> 00:08:14.180 align:start position:0% and test network using the automatic 00:08:14.180 --> 00:08:17.379 align:start position:0% and test network using the automatic connection<00:08:15.160> endpoint<00:08:16.160> we<00:08:17.030> have<00:08:17.210> made 00:08:17.379 --> 00:08:17.389 align:start position:0% connection endpoint we have made 00:08:17.389 --> 00:08:20.550 align:start position:0% connection endpoint we have made available<00:08:17.509> a<00:08:17.930> test<00:08:18.500> network<00:08:18.830> with<00:08:19.160> a<00:08:19.580> hundred 00:08:20.550 --> 00:08:20.560 align:start position:0% available a test network with a hundred 00:08:20.560 --> 00:08:23.379 align:start position:0% available a test network with a hundred reading<00:08:21.560> nodes<00:08:22.099> so<00:08:22.729> when<00:08:22.910> you<00:08:23.000> use<00:08:23.180> the 00:08:23.379 --> 00:08:23.389 align:start position:0% reading nodes so when you use the 00:08:23.389 --> 00:08:25.719 align:start position:0% reading nodes so when you use the automatic<00:08:23.660> connection<00:08:24.530> management<00:08:25.159> you're 00:08:25.719 --> 00:08:25.729 align:start position:0% automatic connection management you're 00:08:25.729 --> 00:08:27.010 align:start position:0% automatic connection management you're probably<00:08:25.940> going<00:08:26.240> to<00:08:26.330> connect<00:08:26.510> to<00:08:26.659> one<00:08:26.840> of<00:08:26.930> our 00:08:27.010 --> 00:08:27.020 align:start position:0% probably going to connect to one of our 00:08:27.020 --> 00:08:29.290 align:start position:0% probably going to connect to one of our nodes<00:08:27.260> and<00:08:27.590> everything<00:08:28.310> is<00:08:28.430> going<00:08:28.610> to<00:08:28.669> work<00:08:28.789> as 00:08:29.290 --> 00:08:29.300 align:start position:0% nodes and everything is going to work as 00:08:29.300 --> 00:08:32.380 align:start position:0% nodes and everything is going to work as expected<00:08:29.570> so<00:08:30.280> these<00:08:31.280> details<00:08:31.639> are<00:08:31.909> I'm<00:08:32.360> not 00:08:32.380 --> 00:08:32.390 align:start position:0% expected so these details are I'm not 00:08:32.390 --> 00:08:34.449 align:start position:0% expected so these details are I'm not gonna<00:08:32.810> focus<00:08:33.500> too<00:08:33.770> much<00:08:33.800> on<00:08:34.039> them<00:08:34.190> they<00:08:34.370> are 00:08:34.449 --> 00:08:34.459 align:start position:0% gonna focus too much on them they are 00:08:34.459 --> 00:08:36.100 align:start position:0% gonna focus too much on them they are all<00:08:34.640> available<00:08:34.880> in<00:08:35.120> the<00:08:35.240> documentation<00:08:35.419> and 00:08:36.100 --> 00:08:36.110 align:start position:0% all available in the documentation and 00:08:36.110 --> 00:08:38.560 align:start position:0% all available in the documentation and as<00:08:36.740> an<00:08:36.890> example<00:08:37.159> of<00:08:37.400> an<00:08:37.729> application<00:08:37.880> built<00:08:38.450> on 00:08:38.560 --> 00:08:38.570 align:start position:0% as an example of an application built on 00:08:38.570 --> 00:08:40.600 align:start position:0% as an example of an application built on top<00:08:38.719> of<00:08:38.779> reading<00:08:39.200> we<00:08:39.620> have<00:08:39.770> built<00:08:40.039> the<00:08:40.219> web<00:08:40.400> UI 00:08:40.600 --> 00:08:40.610 align:start position:0% top of reading we have built the web UI 00:08:40.610 --> 00:08:43.659 align:start position:0% top of reading we have built the web UI so<00:08:41.360> the<00:08:41.479> web<00:08:41.630> UI<00:08:41.900> is<00:08:42.080> one<00:08:42.740> of<00:08:42.860> the<00:08:43.039> UI's<00:08:43.339> that<00:08:43.490> we 00:08:43.659 --> 00:08:43.669 align:start position:0% so the web UI is one of the UI's that we 00:08:43.669 --> 00:08:45.550 align:start position:0% so the web UI is one of the UI's that we have<00:08:43.789> available<00:08:44.480> for<00:08:44.720> the<00:08:44.900> Braden<00:08:45.200> project 00:08:45.550 --> 00:08:45.560 align:start position:0% have available for the Braden project 00:08:45.560 --> 00:08:47.890 align:start position:0% have available for the Braden project and<00:08:45.740> the<00:08:46.250> web<00:08:46.550> UI<00:08:46.760> is<00:08:46.940> available<00:08:47.450> in<00:08:47.720> our 00:08:47.890 --> 00:08:47.900 align:start position:0% and the web UI is available in our 00:08:47.900 --> 00:08:49.930 align:start position:0% and the web UI is available in our source<00:08:48.500> code<00:08:48.620> that<00:08:49.070> you<00:08:49.160> can<00:08:49.310> just<00:08:49.610> find<00:08:49.790> in 00:08:49.930 --> 00:08:49.940 align:start position:0% source code that you can just find in 00:08:49.940 --> 00:08:52.480 align:start position:0% source code that you can just find in the<00:08:50.060> your<00:08:50.330> why<00:08:50.450> folder<00:08:50.810> and<00:08:50.990> that<00:08:51.130> it's<00:08:52.130> built 00:08:52.480 --> 00:08:52.490 align:start position:0% the your why folder and that it's built 00:08:52.490 --> 00:08:54.400 align:start position:0% the your why folder and that it's built using<00:08:52.730> these<00:08:53.060> endpoints<00:08:53.720> that<00:08:54.020> I<00:08:54.050> have<00:08:54.200> showed 00:08:54.400 --> 00:08:54.410 align:start position:0% using these endpoints that I have showed 00:08:54.410 --> 00:08:57.579 align:start position:0% using these endpoints that I have showed you<00:08:54.440> guys<00:08:55.480> so<00:08:56.480> that's<00:08:56.900> everything<00:08:57.290> that<00:08:57.410> I 00:08:57.579 --> 00:08:57.589 align:start position:0% you guys so that's everything that I 00:08:57.589 --> 00:08:59.650 align:start position:0% you guys so that's everything that I have<00:08:57.920> to<00:08:58.070> show<00:08:58.220> you<00:08:58.250> that's<00:08:59.120> how<00:08:59.330> you<00:08:59.390> need<00:08:59.630> to 00:08:59.650 --> 00:08:59.660 align:start position:0% have to show you that's how you need to 00:08:59.660 --> 00:09:02.350 align:start position:0% have to show you that's how you need to note<00:09:00.100> to<00:09:01.100> build<00:09:01.370> applications<00:09:01.850> on<00:09:01.970> top<00:09:02.000> of<00:09:02.240> a 00:09:02.350 --> 00:09:02.360 align:start position:0% note to build applications on top of a 00:09:02.360 --> 00:09:05.230 align:start position:0% note to build applications on top of a Braden<00:09:02.660> and<00:09:03.040> if<00:09:04.040> you<00:09:04.160> want<00:09:04.370> more<00:09:04.579> additional 00:09:05.230 --> 00:09:05.240 align:start position:0% Braden and if you want more additional 00:09:05.240 --> 00:09:07.300 align:start position:0% Braden and if you want more additional details<00:09:05.540> on<00:09:05.720> the<00:09:06.200> format<00:09:06.500> of<00:09:06.529> the<00:09:06.740> JSON<00:09:07.070> files 00:09:07.300 --> 00:09:07.310 align:start position:0% details on the format of the JSON files 00:09:07.310 --> 00:09:10.269 align:start position:0% details on the format of the JSON files the<00:09:08.180> response<00:09:08.600> and<00:09:08.930> different<00:09:09.800> verbs<00:09:10.130> are 00:09:10.269 --> 00:09:10.279 align:start position:0% the response and different verbs are 00:09:10.279 --> 00:09:11.380 align:start position:0% the response and different verbs are different<00:09:10.700> endpoints<00:09:10.850> that<00:09:11.209> we<00:09:11.270> have 00:09:11.380 --> 00:09:11.390 align:start position:0% different endpoints that we have 00:09:11.390 --> 00:09:13.150 align:start position:0% different endpoints that we have available<00:09:11.630> you<00:09:12.230> can<00:09:12.410> go<00:09:12.589> to<00:09:12.650> the<00:09:12.860> read<00:09:13.010> and 00:09:13.150 --> 00:09:13.160 align:start position:0% available you can go to the read and 00:09:13.160 --> 00:09:15.190 align:start position:0% available you can go to the read and network<00:09:13.459> read<00:09:13.670> the<00:09:13.790> docs<00:09:14.000> and<00:09:14.270> we<00:09:14.660> have<00:09:14.810> much 00:09:15.190 --> 00:09:15.200 align:start position:0% network read the docs and we have much 00:09:15.200 --> 00:09:17.050 align:start position:0% network read the docs and we have much more<00:09:15.350> information<00:09:15.500> there<00:09:15.950> including<00:09:16.430> how<00:09:17.000> to 00:09:17.050 --> 00:09:17.060 align:start position:0% more information there including how to 00:09:17.060 --> 00:09:18.670 align:start position:0% more information there including how to deploy<00:09:17.390> your<00:09:17.540> own<00:09:17.720> tokens<00:09:18.200> and<00:09:18.440> use<00:09:18.649> a 00:09:18.670 --> 00:09:18.680 align:start position:0% deploy your own tokens and use a 00:09:18.680 --> 00:09:20.380 align:start position:0% deploy your own tokens and use a different<00:09:19.070> test<00:09:19.399> network<00:09:19.820> if<00:09:19.940> you<00:09:20.029> don't<00:09:20.209> want 00:09:20.380 --> 00:09:20.390 align:start position:0% different test network if you don't want 00:09:20.390 --> 00:09:22.720 align:start position:0% different test network if you don't want you<00:09:20.540> use<00:09:21.170> the<00:09:21.350> rocket<00:09:21.680> robson<00:09:22.190> test<00:09:22.370> network 00:09:22.720 --> 00:09:22.730 align:start position:0% you use the rocket robson test network 00:09:22.730 --> 00:09:25.329 align:start position:0% you use the rocket robson test network so<00:09:23.510> with<00:09:23.899> that<00:09:24.110> I'm<00:09:24.380> just<00:09:24.440> going<00:09:24.860> to<00:09:24.920> live<00:09:25.070> for 00:09:25.329 --> 00:09:25.339 align:start position:0% so with that I'm just going to live for 00:09:25.339 --> 00:09:26.860 align:start position:0% so with that I'm just going to live for blue<00:09:25.640> denim<00:09:26.000> that's<00:09:26.329> going<00:09:26.570> to<00:09:26.630> talk<00:09:26.750> about 00:09:26.860 --> 00:09:26.870 align:start position:0% blue denim that's going to talk about 00:09:26.870 --> 00:09:37.240 align:start position:0% blue denim that's going to talk about micro<00:09:27.320> micro<00:09:27.620> Raylan 00:09:37.240 --> 00:09:37.250 align:start position:0% 00:09:37.250 --> 00:09:46.540 align:start position:0% [Applause] 00:09:46.540 --> 00:09:46.550 align:start position:0% 00:09:46.550 --> 00:09:47.840 align:start position:0% hello 00:09:47.840 --> 00:09:47.850 align:start position:0% hello 00:09:47.850 --> 00:09:50.960 align:start position:0% hello I'm<00:09:48.839> Nora<00:09:49.200> Dunham<00:09:49.620> one<00:09:50.190> of<00:09:50.310> the<00:09:50.459> developers 00:09:50.960 --> 00:09:50.970 align:start position:0% I'm Nora Dunham one of the developers 00:09:50.970 --> 00:09:55.579 align:start position:0% I'm Nora Dunham one of the developers that<00:09:51.120> contributed<00:09:51.779> to<00:09:51.839> micro<00:09:52.529> Radin<00:09:54.589> I'm 00:09:55.579 --> 00:09:55.589 align:start position:0% that contributed to micro Radin I'm 00:09:55.589 --> 00:09:57.829 align:start position:0% that contributed to micro Radin I'm gonna<00:09:55.920> tell<00:09:56.639> you<00:09:56.760> today<00:09:57.060> what<00:09:57.089> is<00:09:57.480> micro 00:09:57.829 --> 00:09:57.839 align:start position:0% gonna tell you today what is micro 00:09:57.839 --> 00:10:00.650 align:start position:0% gonna tell you today what is micro grading<00:09:58.139> for<00:09:58.860> what<00:09:59.100> you<00:09:59.250> can<00:09:59.370> use<00:09:59.639> it<00:09:59.850> and<00:10:00.120> I'll 00:10:00.650 --> 00:10:00.660 align:start position:0% grading for what you can use it and I'll 00:10:00.660 --> 00:10:05.240 align:start position:0% grading for what you can use it and I'll also<00:10:00.899> show<00:10:01.320> you<00:10:01.380> a<00:10:02.180> small<00:10:03.180> live<00:10:03.990> demo<00:10:04.320> of<00:10:04.620> a 00:10:05.240 --> 00:10:05.250 align:start position:0% also show you a small live demo of a 00:10:05.250 --> 00:10:09.500 align:start position:0% also show you a small live demo of a token<00:10:05.670> fueled<00:10:06.120> robot<00:10:07.850> so<00:10:08.850> what<00:10:09.029> is<00:10:09.180> micro 00:10:09.500 --> 00:10:09.510 align:start position:0% token fueled robot so what is micro 00:10:09.510 --> 00:10:13.449 align:start position:0% token fueled robot so what is micro Radin<00:10:10.040> micro<00:10:11.040> Radin<00:10:11.370> is<00:10:11.550> a<00:10:11.610> robust<00:10:12.389> of<00:10:12.690> chain 00:10:13.449 --> 00:10:13.459 align:start position:0% Radin micro Radin is a robust of chain 00:10:13.459 --> 00:10:17.389 align:start position:0% Radin micro Radin is a robust of chain payment<00:10:14.459> channel<00:10:14.790> framework<00:10:15.300> and<00:10:16.170> it's<00:10:17.130> easy 00:10:17.389 --> 00:10:17.399 align:start position:0% payment channel framework and it's easy 00:10:17.399 --> 00:10:22.069 align:start position:0% payment channel framework and it's easy to<00:10:17.490> use<00:10:18.139> off-the-shelf<00:10:19.880> it<00:10:20.880> is<00:10:21.180> good<00:10:21.389> for<00:10:21.600> 80% 00:10:22.069 --> 00:10:22.079 align:start position:0% to use off-the-shelf it is good for 80% 00:10:22.079 --> 00:10:25.759 align:start position:0% to use off-the-shelf it is good for 80% of<00:10:22.529> the<00:10:23.010> use<00:10:23.250> cases<00:10:23.399> that<00:10:24.440> someone<00:10:25.440> can<00:10:25.740> think 00:10:25.759 --> 00:10:25.769 align:start position:0% of the use cases that someone can think 00:10:25.769 --> 00:10:30.500 align:start position:0% of the use cases that someone can think of<00:10:26.310> when<00:10:27.209> they<00:10:27.630> are<00:10:28.610> thinking<00:10:29.610> of<00:10:29.699> using<00:10:29.910> Radin 00:10:30.500 --> 00:10:30.510 align:start position:0% of when they are thinking of using Radin 00:10:30.510 --> 00:10:34.519 align:start position:0% of when they are thinking of using Radin for<00:10:30.870> their<00:10:31.380> own<00:10:31.529> service<00:10:31.980> or<00:10:32.130> business<00:10:33.410> it<00:10:34.410> is 00:10:34.519 --> 00:10:34.529 align:start position:0% for their own service or business it is 00:10:34.529 --> 00:10:36.680 align:start position:0% for their own service or business it is a<00:10:34.680> unidirectional<00:10:35.690> many-to-one 00:10:36.680 --> 00:10:36.690 align:start position:0% a unidirectional many-to-one 00:10:36.690 --> 00:10:39.680 align:start position:0% a unidirectional many-to-one implementation<00:10:37.649> which<00:10:37.920> means<00:10:38.250> we<00:10:38.910> don't<00:10:39.120> need 00:10:39.680 --> 00:10:39.690 align:start position:0% implementation which means we don't need 00:10:39.690 --> 00:10:42.910 align:start position:0% implementation which means we don't need to<00:10:39.839> think<00:10:40.019> about<00:10:40.430> routing<00:10:41.430> issues<00:10:41.579> and 00:10:42.910 --> 00:10:42.920 align:start position:0% to think about routing issues and 00:10:42.920 --> 00:10:46.220 align:start position:0% to think about routing issues and incentivizing<00:10:43.920> fees<00:10:44.310> for<00:10:45.300> users<00:10:45.839> who<00:10:46.019> have 00:10:46.220 --> 00:10:46.230 align:start position:0% incentivizing fees for users who have 00:10:46.230 --> 00:10:48.680 align:start position:0% incentivizing fees for users who have open<00:10:46.620> channels<00:10:47.040> and<00:10:47.279> want<00:10:48.120> to<00:10:48.180> share<00:10:48.480> them 00:10:48.680 --> 00:10:48.690 align:start position:0% open channels and want to share them 00:10:48.690 --> 00:10:53.810 align:start position:0% open channels and want to share them with<00:10:48.720> others<00:10:49.910> that<00:10:50.910> this<00:10:51.149> is<00:10:51.300> why<00:10:51.570> we<00:10:52.560> have<00:10:53.490> off 00:10:53.810 --> 00:10:53.820 align:start position:0% with others that this is why we have off 00:10:53.820 --> 00:10:57.970 align:start position:0% with others that this is why we have off key<00:10:54.029> transactions<00:10:54.720> that<00:10:54.870> are<00:10:54.930> fast<00:10:55.380> and<00:10:55.680> free 00:10:57.970 --> 00:10:57.980 align:start position:0% key transactions that are fast and free 00:10:57.980 --> 00:11:00.860 align:start position:0% key transactions that are fast and free micro<00:10:58.980> Radin<00:10:59.339> is<00:10:59.459> available<00:11:00.000> now<00:11:00.149> on<00:11:00.180> the 00:11:00.860 --> 00:11:00.870 align:start position:0% micro Radin is available now on the 00:11:00.870 --> 00:11:03.530 align:start position:0% micro Radin is available now on the Kelvin<00:11:01.110> test<00:11:01.529> net<00:11:01.769> and<00:11:02.040> will<00:11:02.730> be<00:11:02.880> available<00:11:02.970> on 00:11:03.530 --> 00:11:03.540 align:start position:0% Kelvin test net and will be available on 00:11:03.540 --> 00:11:05.120 align:start position:0% Kelvin test net and will be available on the<00:11:03.810> main<00:11:03.959> net<00:11:04.230> by<00:11:04.589> the<00:11:04.649> end<00:11:04.860> of<00:11:04.949> November 00:11:05.120 --> 00:11:05.130 align:start position:0% the main net by the end of November 00:11:05.130 --> 00:11:10.040 align:start position:0% the main net by the end of November which<00:11:05.760> is<00:11:06.000> by<00:11:06.540> the<00:11:06.600> end<00:11:06.779> of<00:11:06.870> this<00:11:07.019> month<00:11:09.050> so 00:11:10.040 --> 00:11:10.050 align:start position:0% which is by the end of this month so 00:11:10.050 --> 00:11:12.889 align:start position:0% which is by the end of this month so what<00:11:10.230> can<00:11:10.410> you<00:11:10.470> build<00:11:10.769> with<00:11:10.980> micro<00:11:11.370> Radin<00:11:11.899> for 00:11:12.889 --> 00:11:12.899 align:start position:0% what can you build with micro Radin for 00:11:12.899 --> 00:11:14.240 align:start position:0% what can you build with micro Radin for human<00:11:13.230> consumption<00:11:13.649> the<00:11:14.040> most 00:11:14.240 --> 00:11:14.250 align:start position:0% human consumption the most 00:11:14.250 --> 00:11:17.210 align:start position:0% human consumption the most straightforward<00:11:14.490> use<00:11:15.089> case<00:11:15.390> is<00:11:15.860> paper<00:11:16.860> use 00:11:17.210 --> 00:11:17.220 align:start position:0% straightforward use case is paper use 00:11:17.220 --> 00:11:21.620 align:start position:0% straightforward use case is paper use and<00:11:17.579> we<00:11:18.000> already<00:11:18.120> have<00:11:18.630> two<00:11:19.260> demos<00:11:20.300> one<00:11:21.300> with<00:11:21.600> a 00:11:21.620 --> 00:11:21.630 align:start position:0% and we already have two demos one with a 00:11:21.630 --> 00:11:23.840 align:start position:0% and we already have two demos one with a fortune<00:11:22.199> cookie<00:11:22.350> paywall<00:11:23.010> that<00:11:23.459> is<00:11:23.610> online 00:11:23.840 --> 00:11:23.850 align:start position:0% fortune cookie paywall that is online 00:11:23.850 --> 00:11:29.870 align:start position:0% fortune cookie paywall that is online now<00:11:24.149> and<00:11:26.149> an<00:11:27.149> unpleasent<00:11:28.399> alternate<00:11:29.399> world 00:11:29.870 --> 00:11:29.880 align:start position:0% now and an unpleasent alternate world 00:11:29.880 --> 00:11:35.930 align:start position:0% now and an unpleasent alternate world where<00:11:30.209> you<00:11:30.390> pay<00:11:30.930> for<00:11:30.990> Wikipedia<00:11:34.670> but<00:11:35.670> the<00:11:35.760> most 00:11:35.930 --> 00:11:35.940 align:start position:0% where you pay for Wikipedia but the most 00:11:35.940 --> 00:11:38.360 align:start position:0% where you pay for Wikipedia but the most interesting<00:11:36.180> use<00:11:36.569> case<00:11:36.870> is<00:11:37.199> the<00:11:37.529> the 00:11:38.360 --> 00:11:38.370 align:start position:0% interesting use case is the the 00:11:38.370 --> 00:11:40.100 align:start position:0% interesting use case is the the machine-to-machine<00:11:38.819> micro<00:11:39.569> payments<00:11:39.990> that 00:11:40.100 --> 00:11:40.110 align:start position:0% machine-to-machine micro payments that 00:11:40.110 --> 00:11:42.470 align:start position:0% machine-to-machine micro payments that you<00:11:40.170> can<00:11:40.410> do<00:11:40.589> so<00:11:41.190> basically<00:11:41.519> if<00:11:41.790> you<00:11:41.819> have<00:11:42.180> an 00:11:42.470 --> 00:11:42.480 align:start position:0% you can do so basically if you have an 00:11:42.480 --> 00:11:47.389 align:start position:0% you can do so basically if you have an API<00:11:43.069> that<00:11:44.449> you<00:11:45.449> want<00:11:45.690> to<00:11:46.019> monetize<00:11:46.680> you<00:11:47.220> can 00:11:47.389 --> 00:11:47.399 align:start position:0% API that you want to monetize you can 00:11:47.399 --> 00:11:50.280 align:start position:0% API that you want to monetize you can use<00:11:47.550> micro<00:11:47.910> use<00:11:48.870> micro<00:11:49.260> Rayden 00:11:50.280 --> 00:11:50.290 align:start position:0% use micro use micro Rayden 00:11:50.290 --> 00:11:52.439 align:start position:0% use micro use micro Rayden from<00:11:50.620> utilities<00:11:51.130> to<00:11:51.370> data<00:11:51.579> storage<00:11:51.970> to 00:11:52.439 --> 00:11:52.449 align:start position:0% from utilities to data storage to 00:11:52.449 --> 00:11:55.410 align:start position:0% from utilities to data storage to scheduled<00:11:53.170> API<00:11:53.560> queries<00:11:54.160> and<00:11:54.459> we<00:11:54.880> already 00:11:55.410 --> 00:11:55.420 align:start position:0% scheduled API queries and we already 00:11:55.420 --> 00:11:58.769 align:start position:0% scheduled API queries and we already have<00:11:55.990> machine-to-machine<00:11:56.980> demo<00:11:57.670> where<00:11:58.540> we 00:11:58.769 --> 00:11:58.779 align:start position:0% have machine-to-machine demo where we 00:11:58.779 --> 00:12:02.460 align:start position:0% have machine-to-machine demo where we query<00:11:59.490> the<00:12:00.490> price<00:12:00.759> of<00:12:01.029> ether<00:12:01.269> in<00:12:01.720> u.s.<00:12:02.079> dollars 00:12:02.460 --> 00:12:02.470 align:start position:0% query the price of ether in u.s. dollars 00:12:02.470 --> 00:12:06.749 align:start position:0% query the price of ether in u.s. dollars each<00:12:03.190> second<00:12:03.759> and<00:12:04.649> you<00:12:05.649> can<00:12:05.860> see<00:12:06.190> the<00:12:06.459> entire 00:12:06.749 --> 00:12:06.759 align:start position:0% each second and you can see the entire 00:12:06.759 --> 00:12:10.530 align:start position:0% each second and you can see the entire lifecycle<00:12:07.540> of<00:12:07.990> our<00:12:08.680> channel<00:12:09.190> from<00:12:09.759> opening<00:12:10.269> to 00:12:10.530 --> 00:12:10.540 align:start position:0% lifecycle of our channel from opening to 00:12:10.540 --> 00:12:13.230 align:start position:0% lifecycle of our channel from opening to depositing<00:12:11.290> new<00:12:11.440> tokens<00:12:11.889> to<00:12:12.399> closing<00:12:12.880> it<00:12:13.089> and 00:12:13.230 --> 00:12:13.240 align:start position:0% depositing new tokens to closing it and 00:12:13.240 --> 00:12:16.170 align:start position:0% depositing new tokens to closing it and also<00:12:14.110> see<00:12:14.410> the<00:12:14.589> off<00:12:14.800> chain<00:12:15.220> micro<00:12:15.639> payments 00:12:16.170 --> 00:12:16.180 align:start position:0% also see the off chain micro payments 00:12:16.180 --> 00:12:19.699 align:start position:0% also see the off chain micro payments how<00:12:16.779> are<00:12:17.019> they<00:12:17.230> created<00:12:17.800> and<00:12:18.250> received<00:12:19.060> and 00:12:19.699 --> 00:12:19.709 align:start position:0% how are they created and received and 00:12:19.709 --> 00:12:26.610 align:start position:0% how are they created and received and now<00:12:20.709> for<00:12:21.130> the<00:12:21.519> live<00:12:21.699> demo<00:12:22.060> I<00:12:24.990> want<00:12:25.990> you<00:12:26.170> to<00:12:26.319> bear 00:12:26.610 --> 00:12:26.620 align:start position:0% now for the live demo I want you to bear 00:12:26.620 --> 00:12:32.600 align:start position:0% now for the live demo I want you to bear with<00:12:26.740> me<00:12:26.949> a<00:12:26.980> little<00:12:27.220> bit<00:12:29.639> so<00:12:30.639> this<00:12:30.819> is<00:12:31.000> Robo<00:12:31.420> and 00:12:32.600 --> 00:12:32.610 align:start position:0% with me a little bit so this is Robo and 00:12:32.610 --> 00:12:40.170 align:start position:0% with me a little bit so this is Robo and I<00:12:33.610> hope<00:12:34.050> there's<00:12:35.050> a<00:12:35.910> camera<00:12:36.910> yeah<00:12:38.910> Robo<00:12:39.910> has 00:12:40.170 --> 00:12:40.180 align:start position:0% I hope there's a camera yeah Robo has 00:12:40.180 --> 00:12:51.790 align:start position:0% I hope there's a camera yeah Robo has his<00:12:40.509> own<00:12:40.720> aetherium<00:12:41.529> address 00:12:51.790 --> 00:12:51.800 align:start position:0% 00:12:51.800 --> 00:12:55.180 align:start position:0% and<00:12:51.890> he<00:12:52.519> uses<00:12:52.730> micro<00:12:53.420> Raiden<00:12:53.839> to<00:12:54.620> be<00:12:54.740> paid<00:12:54.980> in 00:12:55.180 --> 00:12:55.190 align:start position:0% and he uses micro Raiden to be paid in 00:12:55.190 --> 00:12:58.750 align:start position:0% and he uses micro Raiden to be paid in tokens<00:12:55.730> for<00:12:56.420> his<00:12:56.630> work<00:12:56.899> we<00:12:57.769> already<00:12:58.070> have<00:12:58.610> an 00:12:58.750 --> 00:12:58.760 align:start position:0% tokens for his work we already have an 00:12:58.760 --> 00:13:00.519 align:start position:0% tokens for his work we already have an account<00:12:59.029> here<00:12:59.330> with<00:12:59.510> Robo<00:12:59.930> this<00:13:00.260> is<00:13:00.410> the 00:13:00.519 --> 00:13:00.529 align:start position:0% account here with Robo this is the 00:13:00.529 --> 00:13:03.490 align:start position:0% account here with Robo this is the JavaScript<00:13:00.830> client<00:13:01.220> and<00:13:01.700> we<00:13:01.880> used<00:13:02.180> no<00:13:03.110> dreads 00:13:03.490 --> 00:13:03.500 align:start position:0% JavaScript client and we used no dreads 00:13:03.500 --> 00:13:06.070 align:start position:0% JavaScript client and we used no dreads for<00:13:03.950> this<00:13:04.130> dashboard<00:13:04.399> and<00:13:04.910> we<00:13:05.600> can<00:13:05.750> see<00:13:05.930> that 00:13:06.070 --> 00:13:06.080 align:start position:0% for this dashboard and we can see that 00:13:06.080 --> 00:13:08.560 align:start position:0% for this dashboard and we can see that we<00:13:06.230> already<00:13:06.470> have<00:13:06.890> an<00:13:07.160> open<00:13:07.550> channel<00:13:07.790> with<00:13:08.540> a 00:13:08.560 --> 00:13:08.570 align:start position:0% we already have an open channel with a 00:13:08.570 --> 00:13:10.930 align:start position:0% we already have an open channel with a deposit<00:13:08.930> of<00:13:09.170> 50<00:13:09.560> tokens<00:13:09.769> and<00:13:10.160> a<00:13:10.730> channel 00:13:10.930 --> 00:13:10.940 align:start position:0% deposit of 50 tokens and a channel 00:13:10.940 --> 00:13:13.210 align:start position:0% deposit of 50 tokens and a channel balance<00:13:11.209> of<00:13:11.540> two<00:13:11.720> tokens<00:13:11.899> which<00:13:12.350> means<00:13:12.709> that 00:13:13.210 --> 00:13:13.220 align:start position:0% balance of two tokens which means that 00:13:13.220 --> 00:13:15.790 align:start position:0% balance of two tokens which means that we<00:13:13.399> already<00:13:13.670> paid<00:13:14.060> Robo<00:13:14.899> two<00:13:15.140> tokens<00:13:15.500> for<00:13:15.649> his 00:13:15.790 --> 00:13:15.800 align:start position:0% we already paid Robo two tokens for his 00:13:15.800 --> 00:13:21.190 align:start position:0% we already paid Robo two tokens for his services<00:13:18.760> we<00:13:19.760> have<00:13:20.000> a<00:13:20.029> remote<00:13:20.660> control<00:13:21.050> for 00:13:21.190 --> 00:13:21.200 align:start position:0% services we have a remote control for 00:13:21.200 --> 00:13:23.170 align:start position:0% services we have a remote control for him<00:13:21.410> and<00:13:21.680> the<00:13:21.950> buttons<00:13:22.279> for<00:13:22.550> a<00:13:22.610> forward<00:13:22.820> back 00:13:23.170 --> 00:13:23.180 align:start position:0% him and the buttons for a forward back 00:13:23.180 --> 00:13:26.110 align:start position:0% him and the buttons for a forward back right<00:13:23.990> left<00:13:24.290> back<00:13:24.620> left<00:13:24.649> and<00:13:25.130> back<00:13:25.250> right<00:13:25.579> are 00:13:26.110 --> 00:13:26.120 align:start position:0% right left back left and back right are 00:13:26.120 --> 00:13:30.120 align:start position:0% right left back left and back right are connected<00:13:27.339> to<00:13:28.339> a<00:13:28.370> micro<00:13:28.790> payment<00:13:29.209> endpoint 00:13:30.120 --> 00:13:30.130 align:start position:0% connected to a micro payment endpoint 00:13:30.130 --> 00:13:36.069 align:start position:0% connected to a micro payment endpoint this<00:13:31.130> is<00:13:31.370> the<00:13:31.670> micro<00:13:31.970> Raiden<00:13:32.269> server<00:13:33.670> and<00:13:35.079> we 00:13:36.069 --> 00:13:36.079 align:start position:0% this is the micro Raiden server and we 00:13:36.079 --> 00:13:38.650 align:start position:0% this is the micro Raiden server and we can<00:13:36.260> see<00:13:36.529> that<00:13:37.010> the<00:13:37.130> JavaScript<00:13:37.640> client<00:13:37.790> has 00:13:38.650 --> 00:13:38.660 align:start position:0% can see that the JavaScript client has 00:13:38.660 --> 00:13:41.650 align:start position:0% can see that the JavaScript client has signed<00:13:39.110> a<00:13:39.500> balance<00:13:39.980> proof<00:13:40.220> for<00:13:40.430> us<00:13:40.610> and<00:13:40.910> that 00:13:41.650 --> 00:13:41.660 align:start position:0% signed a balance proof for us and that 00:13:41.660 --> 00:13:44.710 align:start position:0% signed a balance proof for us and that instantly<00:13:42.290> the<00:13:42.890> micro<00:13:43.310> Raiden<00:13:44.089> server<00:13:44.360> has 00:13:44.710 --> 00:13:44.720 align:start position:0% instantly the micro Raiden server has 00:13:44.720 --> 00:13:55.500 align:start position:0% instantly the micro Raiden server has received<00:13:45.290> that<00:13:45.529> payment 00:13:55.500 --> 00:13:55.510 align:start position:0% 00:13:55.510 --> 00:14:00.930 align:start position:0% and<00:13:58.139> sorry<00:13:59.139> I<00:13:59.260> don't<00:13:59.440> have<00:13:59.800> enough<00:14:00.339> time<00:14:00.639> to 00:14:00.930 --> 00:14:00.940 align:start position:0% and sorry I don't have enough time to 00:14:00.940 --> 00:14:04.319 align:start position:0% and sorry I don't have enough time to show<00:14:00.970> you<00:14:01.149> everything<00:14:01.510> sir<00:14:02.190> and<00:14:03.190> you<00:14:03.940> can<00:14:04.120> see 00:14:04.319 --> 00:14:04.329 align:start position:0% show you everything sir and you can see 00:14:04.329 --> 00:14:06.090 align:start position:0% show you everything sir and you can see that<00:14:04.449> the<00:14:04.570> balance<00:14:04.990> has<00:14:05.260> increased<00:14:05.860> with 00:14:06.090 --> 00:14:06.100 align:start position:0% that the balance has increased with 00:14:06.100 --> 00:14:08.069 align:start position:0% that the balance has increased with every<00:14:06.459> press<00:14:06.699> of<00:14:06.850> the<00:14:07.000> button<00:14:07.029> you<00:14:07.389> can<00:14:07.570> of 00:14:08.069 --> 00:14:08.079 align:start position:0% every press of the button you can of 00:14:08.079 --> 00:14:10.920 align:start position:0% every press of the button you can of course<00:14:08.350> do<00:14:08.529> this<00:14:08.760> by<00:14:09.760> timing<00:14:10.089> the<00:14:10.269> robot<00:14:10.690> or 00:14:10.920 --> 00:14:10.930 align:start position:0% course do this by timing the robot or 00:14:10.930 --> 00:14:13.259 align:start position:0% course do this by timing the robot or measuring<00:14:11.380> the<00:14:11.500> distance<00:14:11.949> but<00:14:12.459> this<00:14:12.610> was<00:14:12.910> I 00:14:13.259 --> 00:14:13.269 align:start position:0% measuring the distance but this was I 00:14:13.269 --> 00:14:19.050 align:start position:0% measuring the distance but this was I mean<00:14:13.810> we<00:14:14.019> implemented<00:14:14.769> this<00:14:17.490> very<00:14:18.490> very<00:14:18.730> fast 00:14:19.050 --> 00:14:19.060 align:start position:0% mean we implemented this very very fast 00:14:19.060 --> 00:14:22.410 align:start position:0% mean we implemented this very very fast in<00:14:19.269> a<00:14:19.329> couple<00:14:19.630> of<00:14:19.720> days<00:14:19.930> so<00:14:21.000> it's<00:14:22.000> not<00:14:22.180> that 00:14:22.410 --> 00:14:22.420 align:start position:0% in a couple of days so it's not that 00:14:22.420 --> 00:14:25.340 align:start position:0% in a couple of days so it's not that complicated 00:14:25.340 --> 00:14:25.350 align:start position:0% 00:14:25.350 --> 00:14:30.509 align:start position:0% ok<00:14:27.240> what<00:14:28.240> we<00:14:28.389> can<00:14:28.600> do<00:14:28.870> when<00:14:29.230> we<00:14:29.470> remain<00:14:29.860> or 00:14:30.509 --> 00:14:30.519 align:start position:0% ok what we can do when we remain or 00:14:30.519 --> 00:14:34.280 align:start position:0% ok what we can do when we remain or without<00:14:30.820> tokens<00:14:31.420> is<00:14:31.630> go<00:14:32.470> to<00:14:32.529> our<00:14:32.680> account<00:14:33.190> and 00:14:34.280 --> 00:14:34.290 align:start position:0% without tokens is go to our account and 00:14:34.290 --> 00:14:38.790 align:start position:0% without tokens is go to our account and deposit<00:14:35.290> more<00:14:35.829> and<00:14:37.019> this<00:14:38.019> is<00:14:38.139> an<00:14:38.290> on<00:14:38.529> chain 00:14:38.790 --> 00:14:38.800 align:start position:0% deposit more and this is an on chain 00:14:38.800 --> 00:14:41.189 align:start position:0% deposit more and this is an on chain transaction<00:14:39.430> so<00:14:39.610> what<00:14:39.820> you've<00:14:40.000> seen<00:14:40.199> until 00:14:41.189 --> 00:14:41.199 align:start position:0% transaction so what you've seen until 00:14:41.199 --> 00:14:46.439 align:start position:0% transaction so what you've seen until now<00:14:41.260> are<00:14:43.019> off<00:14:44.019> chain<00:14:44.470> micro<00:14:44.829> payments<00:14:45.279> and<00:14:45.519> to 00:14:46.439 --> 00:14:46.449 align:start position:0% now are off chain micro payments and to 00:14:46.449 --> 00:14:50.160 align:start position:0% now are off chain micro payments and to verify<00:14:46.720> this<00:14:47.339> we<00:14:48.339> can<00:14:48.550> go<00:14:48.730> to<00:14:48.790> either<00:14:49.360> scan<00:14:49.810> and 00:14:50.160 --> 00:14:50.170 align:start position:0% verify this we can go to either scan and 00:14:50.170 --> 00:14:51.829 align:start position:0% verify this we can go to either scan and see<00:14:50.709> that<00:14:50.949> the<00:14:51.070> transaction<00:14:51.579> will<00:14:51.760> be 00:14:51.829 --> 00:14:51.839 align:start position:0% see that the transaction will be 00:14:51.839 --> 00:14:54.689 align:start position:0% see that the transaction will be included<00:14:52.839> in<00:14:52.899> the<00:14:52.990> Box<00:14:53.230> ortley<00:14:53.620> and<00:14:53.920> we<00:14:54.519> can 00:14:54.689 --> 00:14:54.699 align:start position:0% included in the Box ortley and we can 00:14:54.699 --> 00:14:56.569 align:start position:0% included in the Box ortley and we can also<00:14:54.910> see<00:14:55.269> the<00:14:55.480> micro<00:14:55.779> raid<00:14:55.959> and<00:14:56.199> server 00:14:56.569 --> 00:14:56.579 align:start position:0% also see the micro raid and server 00:14:56.579 --> 00:15:00.000 align:start position:0% also see the micro raid and server registering<00:14:57.579> the<00:14:57.760> event<00:14:58.240> for<00:14:58.870> depositing<00:14:59.829> new 00:15:00.000 --> 00:15:00.010 align:start position:0% registering the event for depositing new 00:15:00.010 --> 00:15:06.210 align:start position:0% registering the event for depositing new tokens<00:15:00.459> of<00:15:03.089> course<00:15:04.089> when<00:15:04.510> we've<00:15:05.220> finished 00:15:06.210 --> 00:15:06.220 align:start position:0% tokens of course when we've finished 00:15:06.220 --> 00:15:08.280 align:start position:0% tokens of course when we've finished everything<00:15:06.639> with<00:15:07.000> Robo<00:15:07.389> we<00:15:07.600> can<00:15:07.810> close<00:15:08.079> the 00:15:08.280 --> 00:15:08.290 align:start position:0% everything with Robo we can close the 00:15:08.290 --> 00:15:15.389 align:start position:0% everything with Robo we can close the channel<00:15:08.529> and<00:15:10.139> again<00:15:11.550> we<00:15:12.550> can<00:15:12.760> verify<00:15:13.709> in<00:15:14.709> ether 00:15:15.389 --> 00:15:15.399 align:start position:0% channel and again we can verify in ether 00:15:15.399 --> 00:15:18.329 align:start position:0% channel and again we can verify in ether scan<00:15:16.350> that<00:15:17.350> this<00:15:17.529> is<00:15:17.680> an<00:15:17.860> on<00:15:18.100> chain 00:15:18.329 --> 00:15:18.339 align:start position:0% scan that this is an on chain 00:15:18.339 --> 00:15:22.259 align:start position:0% scan that this is an on chain transaction<00:15:19.089> and<00:15:20.670> the<00:15:21.670> micro<00:15:21.970> radiance 00:15:22.259 --> 00:15:22.269 align:start position:0% transaction and the micro radiance 00:15:22.269 --> 00:15:35.280 align:start position:0% transaction and the micro radiance server<00:15:22.480> has<00:15:22.839> also<00:15:23.260> received<00:15:23.589> this<00:15:27.720> ok<00:15:28.980> going 00:15:35.280 --> 00:15:35.290 align:start position:0% 00:15:35.290 --> 00:15:41.530 align:start position:0% back<00:15:36.290> to<00:15:36.529> the<00:15:36.620> presentation<00:15:40.029> the<00:15:41.029> code<00:15:41.240> for 00:15:41.530 --> 00:15:41.540 align:start position:0% back to the presentation the code for 00:15:41.540 --> 00:15:43.960 align:start position:0% back to the presentation the code for this<00:15:41.720> for<00:15:42.019> the<00:15:42.110> examples<00:15:42.709> are<00:15:42.950> in<00:15:43.279> the<00:15:43.580> micro 00:15:43.960 --> 00:15:43.970 align:start position:0% this for the examples are in the micro 00:15:43.970 --> 00:15:45.310 align:start position:0% this for the examples are in the micro Raiden<00:15:44.300> repositories 00:15:45.310 --> 00:15:45.320 align:start position:0% Raiden repositories 00:15:45.320 --> 00:15:47.139 align:start position:0% Raiden repositories under<00:15:46.130> microwave<00:15:46.519> and<00:15:46.670> microwave<00:15:46.790> and 00:15:47.139 --> 00:15:47.149 align:start position:0% under microwave and microwave and 00:15:47.149 --> 00:15:51.130 align:start position:0% under microwave and microwave and examples<00:15:47.630> and<00:15:48.190> for<00:15:49.190> the<00:15:49.279> robot<00:15:49.640> the<00:15:50.300> token 00:15:51.130 --> 00:15:51.140 align:start position:0% examples and for the robot the token 00:15:51.140 --> 00:15:54.460 align:start position:0% examples and for the robot the token hungry<00:15:51.500> car<00:15:52.180> we<00:15:53.180> will<00:15:53.390> link<00:15:53.630> it<00:15:53.839> in<00:15:53.990> the<00:15:54.019> readme 00:15:54.460 --> 00:15:54.470 align:start position:0% hungry car we will link it in the readme 00:15:54.470 --> 00:15:57.100 align:start position:0% hungry car we will link it in the readme but<00:15:54.800> for<00:15:55.220> now<00:15:55.430> the<00:15:55.940> Jason<00:15:56.300> for<00:15:56.540> setting<00:15:56.839> up<00:15:56.990> the 00:15:57.100 --> 00:15:57.110 align:start position:0% but for now the Jason for setting up the 00:15:57.110 --> 00:16:02.139 align:start position:0% but for now the Jason for setting up the node<00:15:57.290> Reds<00:15:59.019> dashboard<00:16:00.019> is<00:16:00.290> in<00:16:00.940> one<00:16:01.940> of<00:16:01.970> my 00:16:02.139 --> 00:16:02.149 align:start position:0% node Reds dashboard is in one of my 00:16:02.149 --> 00:16:04.860 align:start position:0% node Reds dashboard is in one of my personal<00:16:02.329> repositories<00:16:03.019> so<00:16:03.860> to<00:16:03.920> recap<00:16:04.550> a<00:16:04.610> bit 00:16:04.860 --> 00:16:04.870 align:start position:0% personal repositories so to recap a bit 00:16:04.870 --> 00:16:08.319 align:start position:0% personal repositories so to recap a bit you<00:16:05.870> can<00:16:06.050> open<00:16:06.740> a<00:16:06.829> channel<00:16:07.070> on<00:16:07.430> chain<00:16:07.850> you<00:16:08.149> can 00:16:08.319 --> 00:16:08.329 align:start position:0% you can open a channel on chain you can 00:16:08.329 --> 00:16:10.660 align:start position:0% you can open a channel on chain you can deposit<00:16:08.630> tokens<00:16:09.140> on<00:16:09.350> chain<00:16:09.680> you<00:16:10.070> can<00:16:10.250> close<00:16:10.640> a 00:16:10.660 --> 00:16:10.670 align:start position:0% deposit tokens on chain you can close a 00:16:10.670 --> 00:16:13.300 align:start position:0% deposit tokens on chain you can close a channel<00:16:11.120> on<00:16:11.269> chain<00:16:11.570> but<00:16:12.260> the<00:16:12.709> essence<00:16:13.160> of 00:16:13.300 --> 00:16:13.310 align:start position:0% channel on chain but the essence of 00:16:13.310 --> 00:16:15.759 align:start position:0% channel on chain but the essence of micro<00:16:13.730> Radin<00:16:14.089> are<00:16:14.360> the<00:16:14.779> micro<00:16:15.110> payments<00:16:15.589> that 00:16:15.759 --> 00:16:15.769 align:start position:0% micro Radin are the micro payments that 00:16:15.769 --> 00:16:20.139 align:start position:0% micro Radin are the micro payments that are<00:16:16.010> done<00:16:16.339> off<00:16:16.610> chain<00:16:17.360> fast<00:16:18.170> and<00:16:18.529> free<00:16:19.160> between 00:16:20.139 --> 00:16:20.149 align:start position:0% are done off chain fast and free between 00:16:20.149 --> 00:16:22.329 align:start position:0% are done off chain fast and free between closing<00:16:20.660> between<00:16:21.079> opening<00:16:21.800> and<00:16:21.980> closing<00:16:22.250> a 00:16:22.329 --> 00:16:22.339 align:start position:0% closing between opening and closing a 00:16:22.339 --> 00:16:26.139 align:start position:0% closing between opening and closing a channel<00:16:24.070> I'll<00:16:25.070> try<00:16:25.279> to<00:16:25.339> make<00:16:25.519> it<00:16:25.579> fast<00:16:25.910> a 00:16:26.139 --> 00:16:26.149 align:start position:0% channel I'll try to make it fast a 00:16:26.149 --> 00:16:29.079 align:start position:0% channel I'll try to make it fast a simple<00:16:26.540> explanation<00:16:27.140> of<00:16:27.260> how<00:16:28.010> it<00:16:28.040> works<00:16:28.399> the 00:16:29.079 --> 00:16:29.089 align:start position:0% simple explanation of how it works the 00:16:29.089 --> 00:16:32.319 align:start position:0% simple explanation of how it works the sender<00:16:29.450> and<00:16:29.630> the<00:16:29.690> receiver<00:16:30.050> both<00:16:30.470> keep<00:16:31.399> copies 00:16:32.319 --> 00:16:32.329 align:start position:0% sender and the receiver both keep copies 00:16:32.329 --> 00:16:35.199 align:start position:0% sender and the receiver both keep copies of<00:16:32.360> the<00:16:32.779> channel<00:16:33.110> data<00:16:33.320> which<00:16:33.620> is<00:16:34.209> receiver 00:16:35.199 --> 00:16:35.209 align:start position:0% of the channel data which is receiver 00:16:35.209 --> 00:16:37.449 align:start position:0% of the channel data which is receiver and<00:16:35.450> sender<00:16:35.510> etherium<00:16:36.170> addresses<00:16:36.709> the<00:16:37.279> block 00:16:37.449 --> 00:16:37.459 align:start position:0% and sender etherium addresses the block 00:16:37.459 --> 00:16:38.920 align:start position:0% and sender etherium addresses the block number<00:16:37.640> at<00:16:37.970> which<00:16:38.149> the<00:16:38.390> channel<00:16:38.720> has<00:16:38.899> been 00:16:38.920 --> 00:16:38.930 align:start position:0% number at which the channel has been 00:16:38.930 --> 00:16:42.610 align:start position:0% number at which the channel has been created<00:16:39.140> and<00:16:39.770> the<00:16:40.100> current<00:16:40.579> balance<00:16:41.620> because 00:16:42.610 --> 00:16:42.620 align:start position:0% created and the current balance because 00:16:42.620 --> 00:16:44.590 align:start position:0% created and the current balance because we've<00:16:42.800> seen<00:16:43.130> that<00:16:43.279> the<00:16:43.430> balance<00:16:43.730> increases<00:16:44.240> so 00:16:44.590 --> 00:16:44.600 align:start position:0% we've seen that the balance increases so 00:16:44.600 --> 00:16:49.060 align:start position:0% we've seen that the balance increases so it's<00:16:44.779> the<00:16:45.260> last<00:16:45.529> status<00:16:47.500> and<00:16:48.500> also<00:16:48.950> the 00:16:49.060 --> 00:16:49.070 align:start position:0% it's the last status and also the 00:16:49.070 --> 00:16:51.400 align:start position:0% it's the last status and also the receiver<00:16:49.399> has<00:16:49.730> the<00:16:50.540> last<00:16:50.720> balance<00:16:51.170> proof 00:16:51.400 --> 00:16:51.410 align:start position:0% receiver has the last balance proof 00:16:51.410 --> 00:16:55.569 align:start position:0% receiver has the last balance proof received<00:16:51.950> from<00:16:52.190> the<00:16:52.339> sender<00:16:54.279> what<00:16:55.279> is<00:16:55.430> the 00:16:55.569 --> 00:16:55.579 align:start position:0% received from the sender what is the 00:16:55.579 --> 00:16:57.639 align:start position:0% received from the sender what is the last<00:16:55.760> balance<00:16:56.149> proof<00:16:56.360> it's<00:16:56.959> basically<00:16:57.410> a 00:16:57.639 --> 00:16:57.649 align:start position:0% last balance proof it's basically a 00:16:57.649 --> 00:17:00.460 align:start position:0% last balance proof it's basically a message<00:16:58.399> signed<00:16:59.120> by<00:16:59.329> the<00:16:59.390> sender<00:16:59.990> which 00:17:00.460 --> 00:17:00.470 align:start position:0% message signed by the sender which 00:17:00.470 --> 00:17:02.710 align:start position:0% message signed by the sender which contains<00:17:01.010> the<00:17:01.579> current<00:17:01.790> balance<00:17:02.029> the<00:17:02.510> block 00:17:02.710 --> 00:17:02.720 align:start position:0% contains the current balance the block 00:17:02.720 --> 00:17:05.980 align:start position:0% contains the current balance the block number<00:17:03.140> and<00:17:03.350> the<00:17:03.500> receivers<00:17:03.980> address<00:17:04.990> the 00:17:05.980 --> 00:17:05.990 align:start position:0% number and the receivers address the 00:17:05.990 --> 00:17:08.679 align:start position:0% number and the receivers address the micro<00:17:06.319> payment<00:17:06.800> works<00:17:07.280> like<00:17:07.520> this<00:17:07.699> the<00:17:08.329> sender 00:17:08.679 --> 00:17:08.689 align:start position:0% micro payment works like this the sender 00:17:08.689 --> 00:17:10.929 align:start position:0% micro payment works like this the sender sends<00:17:08.900> all<00:17:09.679> this<00:17:09.890> data<00:17:10.160> along<00:17:10.550> with<00:17:10.610> his 00:17:10.929 --> 00:17:10.939 align:start position:0% sends all this data along with his 00:17:10.939 --> 00:17:14.069 align:start position:0% sends all this data along with his signature<00:17:11.209> to<00:17:11.900> the<00:17:11.990> receiver<00:17:12.490> the<00:17:13.490> receiver 00:17:14.069 --> 00:17:14.079 align:start position:0% signature to the receiver the receiver 00:17:14.079 --> 00:17:17.010 align:start position:0% signature to the receiver the receiver provides<00:17:15.079> the<00:17:15.290> resource<00:17:15.709> and<00:17:16.010> also<00:17:16.579> saves 00:17:17.010 --> 00:17:17.020 align:start position:0% provides the resource and also saves 00:17:17.020 --> 00:17:20.980 align:start position:0% provides the resource and also saves this<00:17:18.020> signed<00:17:18.500> balance<00:17:19.010> proof<00:17:19.780> we<00:17:20.780> also 00:17:20.980 --> 00:17:20.990 align:start position:0% this signed balance proof we also 00:17:20.990 --> 00:17:25.990 align:start position:0% this signed balance proof we also support<00:17:21.770> the<00:17:22.130> ERC<00:17:23.679> 223<00:17:24.679> in<00:17:24.860> work<00:17:25.339> standard 00:17:25.990 --> 00:17:26.000 align:start position:0% support the ERC 223 in work standard 00:17:26.000 --> 00:17:29.650 align:start position:0% support the ERC 223 in work standard along<00:17:26.870> with<00:17:27.110> the<00:17:27.380> ERC<00:17:27.700> 24<00:17:28.700> opening<00:17:29.390> a<00:17:29.480> channel 00:17:29.650 --> 00:17:29.660 align:start position:0% along with the ERC 24 opening a channel 00:17:29.660 --> 00:17:34.650 align:start position:0% along with the ERC 24 opening a channel and<00:17:30.020> depositing<00:17:30.890> tokens<00:17:31.340> because<00:17:32.240> the<00:17:32.390> RC<00:17:32.890> 223 00:17:34.650 --> 00:17:34.660 align:start position:0% and depositing tokens because the RC 223 00:17:34.660 --> 00:17:38.290 align:start position:0% and depositing tokens because the RC 223 offers<00:17:35.660> us<00:17:36.160> the<00:17:37.160> possibility<00:17:37.190> of<00:17:37.700> consuming 00:17:38.290 --> 00:17:38.300 align:start position:0% offers us the possibility of consuming 00:17:38.300 --> 00:17:40.600 align:start position:0% offers us the possibility of consuming less<00:17:38.540> gas<00:17:38.900> because<00:17:39.559> we<00:17:39.710> only<00:17:40.070> do<00:17:40.340> one 00:17:40.600 --> 00:17:40.610 align:start position:0% less gas because we only do one 00:17:40.610 --> 00:17:43.510 align:start position:0% less gas because we only do one transaction<00:17:41.050> instead<00:17:42.050> of<00:17:42.169> two<00:17:42.500> for<00:17:42.980> approving 00:17:43.510 --> 00:17:43.520 align:start position:0% transaction instead of two for approving 00:17:43.520 --> 00:17:46.540 align:start position:0% transaction instead of two for approving and<00:17:43.760> opening<00:17:44.300> a<00:17:44.390> channel<00:17:44.620> I'm<00:17:45.620> going<00:17:46.100> to<00:17:46.280> skip 00:17:46.540 --> 00:17:46.550 align:start position:0% and opening a channel I'm going to skip 00:17:46.550 --> 00:17:48.040 align:start position:0% and opening a channel I'm going to skip this<00:17:46.760> very<00:17:47.090> fast 00:17:48.040 --> 00:17:48.050 align:start position:0% this very fast 00:17:48.050 --> 00:17:49.320 align:start position:0% this very fast maybe<00:17:48.410> tell<00:17:48.679> you<00:17:48.770> a<00:17:48.800> little<00:17:49.040> bit<00:17:49.190> about 00:17:49.320 --> 00:17:49.330 align:start position:0% maybe tell you a little bit about 00:17:49.330 --> 00:17:52.660 align:start position:0% maybe tell you a little bit about closing<00:17:50.330> a<00:17:50.600> channel<00:17:50.990> and<00:17:51.170> we<00:17:51.800> can<00:17:52.010> do<00:17:52.190> this<00:17:52.370> we 00:17:52.660 --> 00:17:52.670 align:start position:0% closing a channel and we can do this we 00:17:52.670 --> 00:17:55.540 align:start position:0% closing a channel and we can do this we can<00:17:52.700> find<00:17:53.120> ourselves<00:17:53.240> in<00:17:53.720> three<00:17:54.110> states<00:17:54.550> one 00:17:55.540 --> 00:17:55.550 align:start position:0% can find ourselves in three states one 00:17:55.550 --> 00:17:58.030 align:start position:0% can find ourselves in three states one is<00:17:55.760> a<00:17:56.000> cooperative<00:17:56.510> closed<00:17:57.020> which<00:17:57.410> is<00:17:57.679> the 00:17:58.030 --> 00:17:58.040 align:start position:0% is a cooperative closed which is the 00:17:58.040 --> 00:18:01.480 align:start position:0% is a cooperative closed which is the best<00:17:58.250> case<00:17:58.460> scenario<00:17:58.840> when<00:17:59.840> the<00:18:00.080> sender<00:18:00.490> where 00:18:01.480 --> 00:18:01.490 align:start position:0% best case scenario when the sender where 00:18:01.490 --> 00:18:03.549 align:start position:0% best case scenario when the sender where is<00:18:01.640> the<00:18:01.760> receiver<00:18:02.120> for<00:18:02.450> a<00:18:02.510> closing<00:18:02.870> signature 00:18:03.549 --> 00:18:03.559 align:start position:0% is the receiver for a closing signature 00:18:03.559 --> 00:18:06.760 align:start position:0% is the receiver for a closing signature and<00:18:03.830> then<00:18:04.760> closes<00:18:05.210> the<00:18:05.330> channel<00:18:05.660> himself<00:18:06.290> by 00:18:06.760 --> 00:18:06.770 align:start position:0% and then closes the channel himself by 00:18:06.770 --> 00:18:08.980 align:start position:0% and then closes the channel himself by providing<00:18:07.190> his<00:18:07.580> balance<00:18:08.000> signature<00:18:08.420> and<00:18:08.630> the 00:18:08.980 --> 00:18:08.990 align:start position:0% providing his balance signature and the 00:18:08.990 --> 00:18:11.169 align:start position:0% providing his balance signature and the receivers<00:18:09.620> closing<00:18:10.550> signature<00:18:11.000> and 00:18:11.169 --> 00:18:11.179 align:start position:0% receivers closing signature and 00:18:11.179 --> 00:18:14.049 align:start position:0% receivers closing signature and everything<00:18:11.720> is<00:18:11.840> well<00:18:12.080> and<00:18:12.260> good<00:18:12.410> if<00:18:13.059> anything 00:18:14.049 --> 00:18:14.059 align:start position:0% everything is well and good if anything 00:18:14.059 --> 00:18:16.090 align:start position:0% everything is well and good if anything goes<00:18:14.270> from<00:18:14.570> we<00:18:14.870> have<00:18:15.050> a<00:18:15.080> challenge<00:18:15.620> period 00:18:16.090 --> 00:18:16.100 align:start position:0% goes from we have a challenge period 00:18:16.100 --> 00:18:18.730 align:start position:0% goes from we have a challenge period where<00:18:17.030> the<00:18:17.630> channel<00:18:17.960> can<00:18:18.110> be<00:18:18.260> closed<00:18:18.530> by<00:18:18.679> the 00:18:18.730 --> 00:18:18.740 align:start position:0% where the channel can be closed by the 00:18:18.740 --> 00:18:21.760 align:start position:0% where the channel can be closed by the receiver<00:18:19.160> by<00:18:19.429> providing<00:18:19.850> that<00:18:20.120> last<00:18:20.770> balance 00:18:21.760 --> 00:18:21.770 align:start position:0% receiver by providing that last balance 00:18:21.770 --> 00:18:25.810 align:start position:0% receiver by providing that last balance proof<00:18:22.040> saved<00:18:22.570> in<00:18:23.570> conclusion<00:18:24.559> my<00:18:25.160> croydon<00:18:25.670> is 00:18:25.810 --> 00:18:25.820 align:start position:0% proof saved in conclusion my croydon is 00:18:25.820 --> 00:18:28.450 align:start position:0% proof saved in conclusion my croydon is ready<00:18:26.300> to<00:18:26.510> use<00:18:26.720> it<00:18:27.080> is<00:18:27.800> the<00:18:27.950> go-to<00:18:28.160> solution 00:18:28.450 --> 00:18:28.460 align:start position:0% ready to use it is the go-to solution 00:18:28.460 --> 00:18:32.470 align:start position:0% ready to use it is the go-to solution for<00:18:29.120> frequent<00:18:29.900> fast<00:18:30.320> and<00:18:30.620> free<00:18:31.160> ERC<00:18:31.970> twenty 00:18:32.470 --> 00:18:32.480 align:start position:0% for frequent fast and free ERC twenty 00:18:32.480 --> 00:18:35.140 align:start position:0% for frequent fast and free ERC twenty token-based<00:18:32.900> of<00:18:33.410> chain<00:18:34.070> micro<00:18:34.429> payments<00:18:34.910> on 00:18:35.140 --> 00:18:35.150 align:start position:0% token-based of chain micro payments on 00:18:35.150 --> 00:18:38.370 align:start position:0% token-based of chain micro payments on the<00:18:35.510> etherium<00:18:35.870> blockchain<00:18:36.320> and<00:18:36.500> don't<00:18:37.460> forget 00:18:38.370 --> 00:18:38.380 align:start position:0% the etherium blockchain and don't forget 00:18:38.380 --> 00:18:47.500 align:start position:0% the etherium blockchain and don't forget robots<00:18:39.380> also<00:18:39.559> won<00:18:39.860> crypto<00:18:46.360> Thank<00:18:47.360> You 00:18:47.500 --> 00:18:47.510 align:start position:0% robots also won crypto Thank You 00:18:47.510 --> 00:18:51.510 align:start position:0% robots also won crypto Thank You Loredana 00:18:51.510 --> 00:18:51.520 align:start position:0% 00:18:51.520 --> 00:19:02.290 align:start position:0% you 00:19:02.290 --> 00:19:02.300 align:start position:0% 00:19:02.300 --> 00:19:09.890 align:start position:0% [Music]