WEBVTT Kind: captions Language: en 00:00:01.640 --> 00:00:17.460 align:start position:0% oh<00:00:15.640> ok<00:00:16.640> good<00:00:17.000> morning 00:00:17.460 --> 00:00:17.470 align:start position:0% oh ok good morning 00:00:17.470 --> 00:00:21.640 align:start position:0% oh ok good morning so<00:00:18.470> swarm<00:00:19.100> city<00:00:19.390> so<00:00:20.390> just<00:00:20.720> as<00:00:20.900> many<00:00:21.380> other 00:00:21.640 --> 00:00:21.650 align:start position:0% so swarm city so just as many other 00:00:21.650 --> 00:00:24.520 align:start position:0% so swarm city so just as many other interior<00:00:22.010> projects<00:00:22.670> who<00:00:22.760> are<00:00:22.880> trying<00:00:23.120> to<00:00:23.530> as 00:00:24.520 --> 00:00:24.530 align:start position:0% interior projects who are trying to as 00:00:24.530 --> 00:00:27.310 align:start position:0% interior projects who are trying to as this<00:00:24.770> one<00:00:24.980> thank<00:00:25.310> you<00:00:25.630> we<00:00:26.630> are<00:00:26.660> this<00:00:27.020> is<00:00:27.170> our 00:00:27.310 --> 00:00:27.320 align:start position:0% this one thank you we are this is our 00:00:27.320 --> 00:00:29.050 align:start position:0% this one thank you we are this is our vision<00:00:27.500> just<00:00:27.890> like<00:00:28.010> many<00:00:28.580> other<00:00:28.670> team 00:00:29.050 --> 00:00:29.060 align:start position:0% vision just like many other team 00:00:29.060 --> 00:00:31.180 align:start position:0% vision just like many other team projects<00:00:29.570> we<00:00:29.750> want<00:00:29.990> to<00:00:30.350> enable<00:00:30.650> humans<00:00:31.130> to 00:00:31.180 --> 00:00:31.190 align:start position:0% projects we want to enable humans to 00:00:31.190 --> 00:00:34.180 align:start position:0% projects we want to enable humans to transact<00:00:31.730> create<00:00:32.450> and<00:00:32.719> share<00:00:33.559> value<00:00:33.980> without 00:00:34.180 --> 00:00:34.190 align:start position:0% transact create and share value without 00:00:34.190 --> 00:00:36.010 align:start position:0% transact create and share value without a<00:00:34.340> middleman<00:00:34.670> or<00:00:35.030> a<00:00:35.060> third<00:00:35.240> party<00:00:35.630> on<00:00:35.720> a<00:00:35.780> global 00:00:36.010 --> 00:00:36.020 align:start position:0% a middleman or a third party on a global 00:00:36.020 --> 00:00:39.930 align:start position:0% a middleman or a third party on a global scale<00:00:36.700> generating<00:00:37.700> contextual<00:00:38.329> reputation 00:00:39.930 --> 00:00:39.940 align:start position:0% scale generating contextual reputation 00:00:39.940 --> 00:00:43.590 align:start position:0% scale generating contextual reputation our<00:00:40.940> mission<00:00:41.570> is<00:00:41.780> to<00:00:42.350> do<00:00:42.530> this<00:00:42.739> in<00:00:42.920> a<00:00:43.010> way<00:00:43.190> where 00:00:43.590 --> 00:00:43.600 align:start position:0% our mission is to do this in a way where 00:00:43.600 --> 00:00:46.150 align:start position:0% our mission is to do this in a way where normal<00:00:44.600> people<00:00:44.630> like<00:00:45.110> our<00:00:45.380> parents<00:00:45.860> actually 00:00:46.150 --> 00:00:46.160 align:start position:0% normal people like our parents actually 00:00:46.160 --> 00:00:49.330 align:start position:0% normal people like our parents actually understand<00:00:47.030> what<00:00:47.660> we<00:00:48.050> are<00:00:48.079> doing<00:00:48.200> so<00:00:48.649> we<00:00:49.190> don't 00:00:49.330 --> 00:00:49.340 align:start position:0% understand what we are doing so we don't 00:00:49.340 --> 00:00:52.870 align:start position:0% understand what we are doing so we don't want<00:00:49.610> to<00:00:50.500> have<00:00:51.500> people<00:00:51.739> experience<00:00:52.070> the 00:00:52.870 --> 00:00:52.880 align:start position:0% want to have people experience the 00:00:52.880 --> 00:00:54.490 align:start position:0% want to have people experience the blockchain<00:00:53.149> basically<00:00:53.840> we<00:00:54.050> want<00:00:54.230> to<00:00:54.290> really 00:00:54.490 --> 00:00:54.500 align:start position:0% blockchain basically we want to really 00:00:54.500 --> 00:00:58.240 align:start position:0% blockchain basically we want to really make<00:00:55.040> it<00:00:55.100> really<00:00:55.399> easy<00:00:55.579> to<00:00:55.700> use<00:00:56.770> today<00:00:57.770> we<00:00:57.980> want 00:00:58.240 --> 00:00:58.250 align:start position:0% make it really easy to use today we want 00:00:58.250 --> 00:01:01.660 align:start position:0% make it really easy to use today we want to<00:00:58.370> discuss<00:00:58.880> two<00:00:59.630> topics<00:01:00.079> we<00:01:01.010> are<00:01:01.040> trying<00:01:01.460> to 00:01:01.660 --> 00:01:01.670 align:start position:0% to discuss two topics we are trying to 00:01:01.670 --> 00:01:05.079 align:start position:0% to discuss two topics we are trying to solve<00:01:01.940> a<00:01:02.630> Tyrian<00:01:03.200> bite<00:01:03.610> problems<00:01:04.610> that<00:01:04.969> we 00:01:05.079 --> 00:01:05.089 align:start position:0% solve a Tyrian bite problems that we 00:01:05.089 --> 00:01:08.110 align:start position:0% solve a Tyrian bite problems that we encounter<00:01:05.600> in<00:01:05.950> creating<00:01:06.950> an<00:01:07.159> app<00:01:07.610> that<00:01:08.090> is 00:01:08.110 --> 00:01:08.120 align:start position:0% encounter in creating an app that is 00:01:08.120 --> 00:01:10.630 align:start position:0% encounter in creating an app that is consumer<00:01:08.750> facing<00:01:09.010> so<00:01:10.010> the<00:01:10.130> first<00:01:10.340> thing<00:01:10.520> we 00:01:10.630 --> 00:01:10.640 align:start position:0% consumer facing so the first thing we 00:01:10.640 --> 00:01:12.190 align:start position:0% consumer facing so the first thing we want<00:01:10.820> to<00:01:10.880> talk<00:01:11.090> about<00:01:11.270> is<00:01:11.600> the<00:01:11.720> IP<00:01:11.870> of<00:01:11.990> s 00:01:12.190 --> 00:01:12.200 align:start position:0% want to talk about is the IP of s 00:01:12.200 --> 00:01:15.730 align:start position:0% want to talk about is the IP of s consortium<00:01:12.920> the<00:01:13.270> second<00:01:14.270> one<00:01:14.450> is<00:01:14.750> the<00:01:15.229> gas 00:01:15.730 --> 00:01:15.740 align:start position:0% consortium the second one is the gas 00:01:15.740 --> 00:01:19.210 align:start position:0% consortium the second one is the gas station<00:01:16.780> so<00:01:17.780> the<00:01:18.290> first<00:01:18.530> thing<00:01:18.710> i<00:01:18.860> PF<00:01:19.070> s 00:01:19.210 --> 00:01:19.220 align:start position:0% station so the first thing i PF s 00:01:19.220 --> 00:01:21.340 align:start position:0% station so the first thing i PF s consortium<00:01:19.820> so<00:01:20.420> if<00:01:20.570> you<00:01:20.659> want<00:01:20.840> to<00:01:20.900> create<00:01:21.200> an 00:01:21.340 --> 00:01:21.350 align:start position:0% consortium so if you want to create an 00:01:21.350 --> 00:01:23.770 align:start position:0% consortium so if you want to create an app<00:01:21.640> like<00:01:22.640> we<00:01:22.820> do<00:01:23.000> that's<00:01:23.240> totally 00:01:23.770 --> 00:01:23.780 align:start position:0% app like we do that's totally 00:01:23.780 --> 00:01:27.190 align:start position:0% app like we do that's totally decentralized<00:01:24.560> you<00:01:25.159> still<00:01:25.610> need<00:01:25.820> storage<00:01:26.330> we 00:01:27.190 --> 00:01:27.200 align:start position:0% decentralized you still need storage we 00:01:27.200 --> 00:01:29.710 align:start position:0% decentralized you still need storage we need<00:01:27.380> to<00:01:27.560> find<00:01:27.799> a<00:01:27.950> way<00:01:28.130> do<00:01:29.000> you<00:01:29.060> have<00:01:29.210> data 00:01:29.710 --> 00:01:29.720 align:start position:0% need to find a way do you have data 00:01:29.720 --> 00:01:33.910 align:start position:0% need to find a way do you have data persistence<00:01:30.200> so<00:01:31.360> even<00:01:32.360> if<00:01:32.450> you<00:01:32.570> do<00:01:32.689> it<00:01:32.840> on<00:01:32.990> ipfs 00:01:33.910 --> 00:01:33.920 align:start position:0% persistence so even if you do it on ipfs 00:01:33.920 --> 00:01:36.700 align:start position:0% persistence so even if you do it on ipfs you<00:01:34.340> have<00:01:34.460> to<00:01:34.610> make<00:01:34.760> sure<00:01:34.970> that<00:01:35.420> your<00:01:36.080> data<00:01:36.290> is 00:01:36.700 --> 00:01:36.710 align:start position:0% you have to make sure that your data is 00:01:36.710 --> 00:01:41.620 align:start position:0% you have to make sure that your data is persisted<00:01:37.189> over<00:01:37.790> time<00:01:39.189> the<00:01:40.189> way<00:01:40.340> we<00:01:40.510> came<00:01:41.510> up 00:01:41.620 --> 00:01:41.630 align:start position:0% persisted over time the way we came up 00:01:41.630 --> 00:01:44.679 align:start position:0% persisted over time the way we came up with<00:01:41.810> that<00:01:41.960> solution<00:01:42.200> is<00:01:42.650> really<00:01:43.689> interesting 00:01:44.679 --> 00:01:44.689 align:start position:0% with that solution is really interesting 00:01:44.689 --> 00:01:46.600 align:start position:0% with that solution is really interesting because<00:01:45.140> it's<00:01:45.500> the<00:01:45.799> way<00:01:45.950> we<00:01:46.100> came<00:01:46.280> up<00:01:46.460> with 00:01:46.600 --> 00:01:46.610 align:start position:0% because it's the way we came up with 00:01:46.610 --> 00:01:49.300 align:start position:0% because it's the way we came up with solution<00:01:47.180> actually<00:01:47.900> is<00:01:48.470> kind<00:01:49.130> of<00:01:49.189> the 00:01:49.300 --> 00:01:49.310 align:start position:0% solution actually is kind of the 00:01:49.310 --> 00:01:49.960 align:start position:0% solution actually is kind of the solution 00:01:49.960 --> 00:01:49.970 align:start position:0% solution 00:01:49.970 --> 00:01:52.539 align:start position:0% solution it's<00:01:50.299> collaboration<00:01:51.229> because<00:01:51.770> it's<00:01:51.950> key<00:01:52.159> in 00:01:52.539 --> 00:01:52.549 align:start position:0% it's collaboration because it's key in 00:01:52.549 --> 00:01:55.899 align:start position:0% it's collaboration because it's key in the<00:01:52.700> blockchain<00:01:52.939> world<00:01:53.330> so<00:01:54.259> we<00:01:55.250> sat<00:01:55.729> together 00:01:55.899 --> 00:01:55.909 align:start position:0% the blockchain world so we sat together 00:01:55.909 --> 00:01:59.109 align:start position:0% the blockchain world so we sat together with<00:01:56.650> givethe<00:01:57.650> in<00:01:57.890> Barcelona<00:01:58.460> and<00:01:58.759> many<00:01:58.939> other 00:01:59.109 --> 00:01:59.119 align:start position:0% with givethe in Barcelona and many other 00:01:59.119 --> 00:02:01.690 align:start position:0% with givethe in Barcelona and many other people<00:01:59.619> and<00:02:00.619> after<00:02:01.430> a<00:02:01.460> night<00:02:01.670> of 00:02:01.690 --> 00:02:01.700 align:start position:0% people and after a night of 00:02:01.700 --> 00:02:03.429 align:start position:0% people and after a night of brainstorming<00:02:02.479> we<00:02:02.720> came<00:02:02.930> up<00:02:03.110> with<00:02:03.290> this 00:02:03.429 --> 00:02:03.439 align:start position:0% brainstorming we came up with this 00:02:03.439 --> 00:02:07.120 align:start position:0% brainstorming we came up with this really<00:02:03.650> simple<00:02:04.220> solution<00:02:04.840> open<00:02:05.840> your<00:02:06.259> data<00:02:06.500> if 00:02:07.120 --> 00:02:07.130 align:start position:0% really simple solution open your data if 00:02:07.130 --> 00:02:10.330 align:start position:0% really simple solution open your data if you've<00:02:07.460> been<00:02:07.670> mined<00:02:08.470> for<00:02:09.470> an<00:02:09.619> in-depth<00:02:10.099> or 00:02:10.330 --> 00:02:10.340 align:start position:0% you've been mined for an in-depth or 00:02:10.340 --> 00:02:12.729 align:start position:0% you've been mined for an in-depth or more<00:02:10.670> in<00:02:10.880> that<00:02:11.060> technical<00:02:11.840> overview<00:02:12.380> of<00:02:12.620> that 00:02:12.729 --> 00:02:12.739 align:start position:0% more in that technical overview of that 00:02:12.739 --> 00:02:15.880 align:start position:0% more in that technical overview of that solution<00:02:13.040> I'll<00:02:13.430> hand<00:02:13.670> it<00:02:13.760> over<00:02:13.880> to<00:02:14.060> Spanish 00:02:15.880 --> 00:02:15.890 align:start position:0% solution I'll hand it over to Spanish 00:02:15.890 --> 00:02:19.040 align:start position:0% solution I'll hand it over to Spanish okay<00:02:16.890> good<00:02:17.459> morning<00:02:17.790> everybody 00:02:19.040 --> 00:02:19.050 align:start position:0% okay good morning everybody 00:02:19.050 --> 00:02:21.559 align:start position:0% okay good morning everybody so<00:02:19.379> the<00:02:19.530> solution<00:02:19.980> we<00:02:20.099> came<00:02:20.310> up<00:02:20.370> with<00:02:20.700> for<00:02:21.510> the 00:02:21.559 --> 00:02:21.569 align:start position:0% so the solution we came up with for the 00:02:21.569 --> 00:02:23.479 align:start position:0% so the solution we came up with for the IP<00:02:21.870> vest<00:02:22.050> consortium<00:02:22.650> is<00:02:22.830> actually<00:02:23.190> that<00:02:23.280> we 00:02:23.479 --> 00:02:23.489 align:start position:0% IP vest consortium is actually that we 00:02:23.489 --> 00:02:26.089 align:start position:0% IP vest consortium is actually that we created<00:02:24.060> smart<00:02:24.840> contracts<00:02:25.440> so<00:02:25.739> by<00:02:25.890> the<00:02:25.950> way 00:02:26.089 --> 00:02:26.099 align:start position:0% created smart contracts so by the way 00:02:26.099 --> 00:02:28.180 align:start position:0% created smart contracts so by the way this<00:02:26.250> works<00:02:26.519> on<00:02:27.239> top<00:02:27.540> of<00:02:27.720> another 00:02:28.180 --> 00:02:28.190 align:start position:0% this works on top of another 00:02:28.190 --> 00:02:31.160 align:start position:0% this works on top of another persistency<00:02:29.420> consortium<00:02:30.420> project<00:02:30.810> by<00:02:30.900> Piper 00:02:31.160 --> 00:02:31.170 align:start position:0% persistency consortium project by Piper 00:02:31.170 --> 00:02:33.229 align:start position:0% persistency consortium project by Piper Mariam<00:02:31.680> so<00:02:32.130> we<00:02:32.250> try<00:02:32.430> to<00:02:32.459> extend<00:02:32.880> it<00:02:33.030> a<00:02:33.060> little 00:02:33.229 --> 00:02:33.239 align:start position:0% Mariam so we try to extend it a little 00:02:33.239 --> 00:02:35.330 align:start position:0% Mariam so we try to extend it a little bit<00:02:33.390> and<00:02:33.569> make<00:02:33.690> it<00:02:33.840> more<00:02:34.019> in<00:02:34.230> general<00:02:34.650> for<00:02:35.010> that 00:02:35.330 --> 00:02:35.340 align:start position:0% bit and make it more in general for that 00:02:35.340 --> 00:02:37.130 align:start position:0% bit and make it more in general for that everybody<00:02:35.700> could<00:02:35.849> use<00:02:36.060> its<00:02:36.269> in<00:02:36.540> like<00:02:36.870> a<00:02:36.900> more 00:02:37.130 --> 00:02:37.140 align:start position:0% everybody could use its in like a more 00:02:37.140 --> 00:02:39.890 align:start position:0% everybody could use its in like a more flexible<00:02:37.319> way<00:02:37.620> so<00:02:38.550> we<00:02:38.880> created<00:02:39.209> a<00:02:39.540> smart 00:02:39.890 --> 00:02:39.900 align:start position:0% flexible way so we created a smart 00:02:39.900 --> 00:02:42.530 align:start position:0% flexible way so we created a smart contract<00:02:40.200> the<00:02:40.739> I<00:02:40.769> previous<00:02:41.160> proxy<00:02:41.610> contract 00:02:42.530 --> 00:02:42.540 align:start position:0% contract the I previous proxy contract 00:02:42.540 --> 00:02:46.130 align:start position:0% contract the I previous proxy contract and<00:02:43.489> this<00:02:44.489> contract<00:02:44.879> will<00:02:45.150> just<00:02:45.390> emit<00:02:45.810> events 00:02:46.130 --> 00:02:46.140 align:start position:0% and this contract will just emit events 00:02:46.140 --> 00:02:48.559 align:start position:0% and this contract will just emit events so<00:02:46.980> we<00:02:47.099> have<00:02:47.280> true<00:02:47.489> to<00:02:47.730> events<00:02:48.030> like<00:02:48.180> hash 00:02:48.559 --> 00:02:48.569 align:start position:0% so we have true to events like hash 00:02:48.569 --> 00:02:50.900 align:start position:0% so we have true to events like hash added<00:02:49.049> so<00:02:49.349> we<00:02:49.380> have<00:02:49.500> an<00:02:49.560> IP<00:02:49.709> this<00:02:50.010> hash<00:02:50.430> gets 00:02:50.900 --> 00:02:50.910 align:start position:0% added so we have an IP this hash gets 00:02:50.910 --> 00:02:52.190 align:start position:0% added so we have an IP this hash gets edit<00:02:51.239> or<00:02:51.360> needs<00:02:51.540> to<00:02:51.630> be<00:02:51.720> added<00:02:51.989> to<00:02:52.019> the 00:02:52.190 --> 00:02:52.200 align:start position:0% edit or needs to be added to the 00:02:52.200 --> 00:02:54.680 align:start position:0% edit or needs to be added to the consortium<00:02:52.670> it<00:02:53.670> has<00:02:53.790> a<00:02:53.819> time<00:02:54.090> to<00:02:54.269> live<00:02:54.450> for 00:02:54.680 --> 00:02:54.690 align:start position:0% consortium it has a time to live for 00:02:54.690 --> 00:02:56.509 align:start position:0% consortium it has a time to live for example<00:02:54.780> and<00:02:55.230> then<00:02:55.319> the<00:02:55.410> IP<00:02:55.530> of<00:02:55.739> s<00:02:55.920> has<00:02:56.099> itself 00:02:56.509 --> 00:02:56.519 align:start position:0% example and then the IP of s has itself 00:02:56.519 --> 00:02:59.030 align:start position:0% example and then the IP of s has itself and<00:02:56.880> the<00:02:57.599> hash<00:02:57.810> removed<00:02:58.290> function<00:02:58.739> so<00:02:58.829> if<00:02:58.920> you 00:02:59.030 --> 00:02:59.040 align:start position:0% and the hash removed function so if you 00:02:59.040 --> 00:03:00.500 align:start position:0% and the hash removed function so if you don't<00:02:59.220> need<00:02:59.340> the<00:02:59.459> data<00:02:59.700> anymore<00:03:00.120> and<00:03:00.329> you<00:03:00.390> want 00:03:00.500 --> 00:03:00.510 align:start position:0% don't need the data anymore and you want 00:03:00.510 --> 00:03:02.960 align:start position:0% don't need the data anymore and you want it's<00:03:00.720> out<00:03:01.349> of<00:03:01.590> the<00:03:01.680> consortium<00:03:02.489> so<00:03:02.700> it's<00:03:02.819> not 00:03:02.960 --> 00:03:02.970 align:start position:0% it's out of the consortium so it's not 00:03:02.970 --> 00:03:06.050 align:start position:0% it's out of the consortium so it's not pinned<00:03:03.269> anymore<00:03:03.690> you<00:03:04.319> can<00:03:04.500> do<00:03:04.620> that<00:03:04.819> then<00:03:05.819> in<00:03:05.940> a 00:03:06.050 --> 00:03:06.060 align:start position:0% pinned anymore you can do that then in a 00:03:06.060 --> 00:03:08.330 align:start position:0% pinned anymore you can do that then in a smart<00:03:06.299> contract<00:03:06.510> itself<00:03:07.019> we<00:03:07.890> implement<00:03:08.280> the 00:03:08.330 --> 00:03:08.340 align:start position:0% smart contract itself we implement the 00:03:08.340 --> 00:03:10.460 align:start position:0% smart contract itself we implement the two<00:03:08.459> functions<00:03:09.030> add<00:03:09.269> hash<00:03:09.599> and<00:03:09.870> remove<00:03:10.200> hash 00:03:10.460 --> 00:03:10.470 align:start position:0% two functions add hash and remove hash 00:03:10.470 --> 00:03:12.710 align:start position:0% two functions add hash and remove hash which<00:03:10.950> basically<00:03:11.280> just<00:03:11.430> emits<00:03:12.150> these<00:03:12.510> two 00:03:12.710 --> 00:03:12.720 align:start position:0% which basically just emits these two 00:03:12.720 --> 00:03:14.809 align:start position:0% which basically just emits these two events<00:03:12.840> so<00:03:13.319> it's<00:03:13.440> very<00:03:13.590> low<00:03:13.890> on<00:03:14.130> gas<00:03:14.370> to 00:03:14.809 --> 00:03:14.819 align:start position:0% events so it's very low on gas to 00:03:14.819 --> 00:03:18.199 align:start position:0% events so it's very low on gas to actually<00:03:15.150> call<00:03:15.930> these<00:03:16.380> two<00:03:16.560> functions<00:03:17.209> then 00:03:18.199 --> 00:03:18.209 align:start position:0% actually call these two functions then 00:03:18.209 --> 00:03:20.539 align:start position:0% actually call these two functions then all<00:03:18.390> these<00:03:18.540> members<00:03:19.049> in<00:03:19.350> the<00:03:19.560> IPS<00:03:19.980> persistence 00:03:20.539 --> 00:03:20.549 align:start position:0% all these members in the IPS persistence 00:03:20.549 --> 00:03:24.590 align:start position:0% all these members in the IPS persistence consortium<00:03:21.269> they<00:03:21.780> will<00:03:22.609> install<00:03:23.609> a<00:03:23.910> script<00:03:24.299> on 00:03:24.590 --> 00:03:24.600 align:start position:0% consortium they will install a script on 00:03:24.600 --> 00:03:27.770 align:start position:0% consortium they will install a script on there<00:03:24.930> respectively<00:03:25.620> respective<00:03:26.519> ipfs<00:03:27.359> notes 00:03:27.770 --> 00:03:27.780 align:start position:0% there respectively respective ipfs notes 00:03:27.780 --> 00:03:29.900 align:start position:0% there respectively respective ipfs notes which<00:03:28.319> is<00:03:28.440> a<00:03:28.470> proxy<00:03:28.799> listener<00:03:29.190> with<00:03:29.400> just<00:03:29.609> a 00:03:29.900 --> 00:03:29.910 align:start position:0% which is a proxy listener with just a 00:03:29.910 --> 00:03:32.270 align:start position:0% which is a proxy listener with just a script<00:03:30.450> that<00:03:31.079> goes<00:03:31.139> and<00:03:31.500> listen<00:03:31.829> to<00:03:32.130> these 00:03:32.270 --> 00:03:32.280 align:start position:0% script that goes and listen to these 00:03:32.280 --> 00:03:35.960 align:start position:0% script that goes and listen to these events<00:03:32.519> on<00:03:33.060> that<00:03:33.209> IP<00:03:33.420> vs<00:03:33.750> proxy<00:03:34.200> contract<00:03:34.970> so 00:03:35.960 --> 00:03:35.970 align:start position:0% events on that IP vs proxy contract so 00:03:35.970 --> 00:03:38.780 align:start position:0% events on that IP vs proxy contract so that's<00:03:36.150> a<00:03:36.239> general<00:03:36.569> set<00:03:36.840> up<00:03:36.959> now<00:03:37.889> there<00:03:38.670> are<00:03:38.730> a 00:03:38.780 --> 00:03:38.790 align:start position:0% that's a general set up now there are a 00:03:38.790 --> 00:03:40.460 align:start position:0% that's a general set up now there are a few<00:03:38.970> more<00:03:39.239> things<00:03:39.540> there<00:03:39.780> for<00:03:39.810> example<00:03:40.200> the 00:03:40.460 --> 00:03:40.470 align:start position:0% few more things there for example the 00:03:40.470 --> 00:03:42.800 align:start position:0% few more things there for example the IPS<00:03:40.889> proxy<00:03:41.220> contract<00:03:41.639> contains<00:03:42.060> a<00:03:42.269> list 00:03:42.800 --> 00:03:42.810 align:start position:0% IPS proxy contract contains a list 00:03:42.810 --> 00:03:44.599 align:start position:0% IPS proxy contract contains a list sort<00:03:43.200> of<00:03:43.230> a<00:03:43.350> white<00:03:43.560> list<00:03:43.829> with<00:03:44.430> all<00:03:44.549> the 00:03:44.599 --> 00:03:44.609 align:start position:0% sort of a white list with all the 00:03:44.609 --> 00:03:47.750 align:start position:0% sort of a white list with all the members<00:03:44.910> of<00:03:45.060> the<00:03:45.299> IPS<00:03:45.810> consortium<00:03:46.530> members<00:03:47.250> so 00:03:47.750 --> 00:03:47.760 align:start position:0% members of the IPS consortium members so 00:03:47.760 --> 00:03:49.640 align:start position:0% members of the IPS consortium members so that<00:03:47.790> means<00:03:48.269> that's<00:03:48.389> all<00:03:48.660> this<00:03:48.810> their<00:03:49.319> public 00:03:49.640 --> 00:03:49.650 align:start position:0% that means that's all this their public 00:03:49.650 --> 00:03:51.890 align:start position:0% that means that's all this their public keys<00:03:49.889> are<00:03:50.190> in<00:03:50.519> there<00:03:50.790> so<00:03:51.329> it<00:03:51.420> can<00:03:51.569> actually 00:03:51.890 --> 00:03:51.900 align:start position:0% keys are in there so it can actually 00:03:51.900 --> 00:03:54.979 align:start position:0% keys are in there so it can actually verify<00:03:52.319> if<00:03:52.889> they<00:03:53.130> call<00:03:53.400> the<00:03:53.609> contracts<00:03:54.180> so 00:03:54.979 --> 00:03:54.989 align:start position:0% verify if they call the contracts so 00:03:54.989 --> 00:03:58.580 align:start position:0% verify if they call the contracts so that<00:03:55.139> only<00:03:55.260> IP<00:03:55.799> this<00:03:56.130> member<00:03:56.810> hashes<00:03:57.810> are<00:03:57.989> pins 00:03:58.580 --> 00:03:58.590 align:start position:0% that only IP this member hashes are pins 00:03:58.590 --> 00:04:01.940 align:start position:0% that only IP this member hashes are pins in<00:03:58.829> the<00:03:58.950> I<00:03:59.099> previous<00:03:59.480> notes<00:04:00.480> itself<00:04:00.930> so<00:04:01.769> there 00:04:01.940 --> 00:04:01.950 align:start position:0% in the I previous notes itself so there 00:04:01.950 --> 00:04:05.360 align:start position:0% in the I previous notes itself so there are<00:04:02.010> different<00:04:02.310> ways<00:04:02.519> of<00:04:02.819> adding<00:04:03.120> your<00:04:04.370> hashes 00:04:05.360 --> 00:04:05.370 align:start position:0% are different ways of adding your hashes 00:04:05.370 --> 00:04:07.789 align:start position:0% are different ways of adding your hashes to<00:04:05.400> the<00:04:05.639> IPS<00:04:06.120> consortium<00:04:06.690> so<00:04:07.170> first<00:04:07.410> of<00:04:07.560> all<00:04:07.680> if 00:04:07.789 --> 00:04:07.799 align:start position:0% to the IPS consortium so first of all if 00:04:07.799 --> 00:04:09.949 align:start position:0% to the IPS consortium so first of all if you<00:04:07.920> have<00:04:08.040> a<00:04:08.069> DAP<00:04:08.370> or<00:04:08.700> a<00:04:08.730> script<00:04:09.120> which<00:04:09.569> one<00:04:09.780> - 00:04:09.949 --> 00:04:09.959 align:start position:0% you have a DAP or a script which one - 00:04:09.959 --> 00:04:13.039 align:start position:0% you have a DAP or a script which one - which<00:04:10.410> wants<00:04:10.709> to<00:04:10.739> pin<00:04:11.060> content<00:04:12.060> you<00:04:12.599> can<00:04:12.780> just 00:04:13.039 --> 00:04:13.049 align:start position:0% which wants to pin content you can just 00:04:13.049 --> 00:04:15.319 align:start position:0% which wants to pin content you can just call<00:04:13.380> the<00:04:13.530> function<00:04:13.950> add<00:04:14.069> hash<00:04:14.430> or<00:04:14.730> remove<00:04:15.060> ash 00:04:15.319 --> 00:04:15.329 align:start position:0% call the function add hash or remove ash 00:04:15.329 --> 00:04:17.210 align:start position:0% call the function add hash or remove ash so<00:04:15.750> that's<00:04:15.930> a<00:04:16.049> way<00:04:16.169> of<00:04:16.200> from<00:04:16.650> doing<00:04:16.919> it<00:04:16.979> from 00:04:17.210 --> 00:04:17.220 align:start position:0% so that's a way of from doing it from 00:04:17.220 --> 00:04:20.690 align:start position:0% so that's a way of from doing it from your<00:04:17.280> tab<00:04:17.639> itself<00:04:18.000> for<00:04:18.329> the<00:04:18.389> front-end<00:04:19.519> but<00:04:20.519> we 00:04:20.690 --> 00:04:20.700 align:start position:0% your tab itself for the front-end but we 00:04:20.700 --> 00:04:23.330 align:start position:0% your tab itself for the front-end but we also<00:04:20.880> expose<00:04:21.660> these<00:04:22.019> ipfs<00:04:22.590> events<00:04:23.070> as<00:04:23.280> a 00:04:23.330 --> 00:04:23.340 align:start position:0% also expose these ipfs events as a 00:04:23.340 --> 00:04:25.250 align:start position:0% also expose these ipfs events as a separate<00:04:23.760> solidity<00:04:24.150> file<00:04:24.510> which<00:04:24.960> you<00:04:25.110> can 00:04:25.250 --> 00:04:25.260 align:start position:0% separate solidity file which you can 00:04:25.260 --> 00:04:27.590 align:start position:0% separate solidity file which you can just<00:04:25.440> include<00:04:25.890> in<00:04:26.580> Iran's 00:04:27.590 --> 00:04:27.600 align:start position:0% just include in Iran's 00:04:27.600 --> 00:04:29.720 align:start position:0% just include in Iran's contract<00:04:28.140> so<00:04:28.260> if<00:04:28.350> you're<00:04:28.500> the<00:04:28.980> the<00:04:29.220> logic<00:04:29.550> of 00:04:29.720 --> 00:04:29.730 align:start position:0% contract so if you're the the logic of 00:04:29.730 --> 00:04:33.020 align:start position:0% contract so if you're the the logic of your<00:04:29.760> DAP<00:04:30.530> actually<00:04:31.530> needs<00:04:31.740> to<00:04:31.860> store<00:04:32.430> IP<00:04:32.730> this 00:04:33.020 --> 00:04:33.030 align:start position:0% your DAP actually needs to store IP this 00:04:33.030 --> 00:04:36.250 align:start position:0% your DAP actually needs to store IP this content<00:04:33.510> from<00:04:34.080> from<00:04:35.040> Unchained<00:04:35.610> basically 00:04:36.250 --> 00:04:36.260 align:start position:0% content from from Unchained basically 00:04:36.260 --> 00:04:38.900 align:start position:0% content from from Unchained basically they<00:04:37.260> can<00:04:37.440> just<00:04:37.650> create<00:04:37.920> your<00:04:37.980> contracts<00:04:38.730> by 00:04:38.900 --> 00:04:38.910 align:start position:0% they can just create your contracts by 00:04:38.910 --> 00:04:41.840 align:start position:0% they can just create your contracts by implementing<00:04:39.480> IDs<00:04:39.990> ipfs<00:04:40.590> events<00:04:41.040> and<00:04:41.220> then 00:04:41.840 --> 00:04:41.850 align:start position:0% implementing IDs ipfs events and then 00:04:41.850 --> 00:04:44.630 align:start position:0% implementing IDs ipfs events and then the<00:04:42.210> consortium<00:04:42.990> members<00:04:43.290> can<00:04:43.620> add<00:04:43.890> their 00:04:44.630 --> 00:04:44.640 align:start position:0% the consortium members can add their 00:04:44.640 --> 00:04:47.000 align:start position:0% the consortium members can add their contracts<00:04:45.270> to<00:04:45.630> the<00:04:45.750> IPAs<00:04:46.260> proxy<00:04:46.650> suite<00:04:46.860> as<00:04:46.980> a 00:04:47.000 --> 00:04:47.010 align:start position:0% contracts to the IPAs proxy suite as a 00:04:47.010 --> 00:04:48.980 align:start position:0% contracts to the IPAs proxy suite as a second<00:04:47.430> list<00:04:47.610> in<00:04:47.790> there<00:04:47.940> and<00:04:48.120> if<00:04:48.600> they<00:04:48.720> added 00:04:48.980 --> 00:04:48.990 align:start position:0% second list in there and if they added 00:04:48.990 --> 00:04:51.620 align:start position:0% second list in there and if they added to<00:04:49.410> the<00:04:49.530> IPAs<00:04:49.950> proxy<00:04:50.370> contracts<00:04:50.910> then<00:04:51.450> these 00:04:51.620 --> 00:04:51.630 align:start position:0% to the IPAs proxy contracts then these 00:04:51.630 --> 00:04:54.110 align:start position:0% to the IPAs proxy contracts then these proxy<00:04:52.050> listener<00:04:52.350> scripts<00:04:52.800> will<00:04:53.370> also<00:04:53.790> start 00:04:54.110 --> 00:04:54.120 align:start position:0% proxy listener scripts will also start 00:04:54.120 --> 00:04:56.810 align:start position:0% proxy listener scripts will also start to<00:04:54.240> listen<00:04:54.480> to<00:04:54.810> these<00:04:55.140> same<00:04:55.410> events<00:04:55.980> in<00:04:56.430> all 00:04:56.810 --> 00:04:56.820 align:start position:0% to listen to these same events in all 00:04:56.820 --> 00:04:59.150 align:start position:0% to listen to these same events in all the<00:04:57.050> specific<00:04:58.050> smart<00:04:58.290> contracts<00:04:58.830> that<00:04:59.010> they 00:04:59.150 --> 00:04:59.160 align:start position:0% the specific smart contracts that they 00:04:59.160 --> 00:05:03.740 align:start position:0% the specific smart contracts that they use<00:05:00.890> now<00:05:01.890> concerning<00:05:02.310> the<00:05:02.550> governance<00:05:03.060> of<00:05:03.360> the 00:05:03.740 --> 00:05:03.750 align:start position:0% use now concerning the governance of the 00:05:03.750 --> 00:05:06.500 align:start position:0% use now concerning the governance of the IPS<00:05:04.170> consortium<00:05:04.800> so<00:05:05.340> we<00:05:05.460> don't<00:05:05.640> want<00:05:05.910> one 00:05:06.500 --> 00:05:06.510 align:start position:0% IPS consortium so we don't want one 00:05:06.510 --> 00:05:09.800 align:start position:0% IPS consortium so we don't want one single<00:05:06.930> owner<00:05:07.170> to<00:05:08.040> manage<00:05:08.280> the<00:05:08.370> consortium<00:05:09.060> so 00:05:09.800 --> 00:05:09.810 align:start position:0% single owner to manage the consortium so 00:05:09.810 --> 00:05:11.750 align:start position:0% single owner to manage the consortium so that's<00:05:09.990> why<00:05:10.110> we<00:05:10.320> added<00:05:10.560> multi-member<00:05:11.550> so 00:05:11.750 --> 00:05:11.760 align:start position:0% that's why we added multi-member so 00:05:11.760 --> 00:05:14.570 align:start position:0% that's why we added multi-member so that's<00:05:12.030> basically<00:05:12.300> the<00:05:12.420> multi<00:05:12.780> C<00:05:12.930> codes<00:05:13.800> to 00:05:14.570 --> 00:05:14.580 align:start position:0% that's basically the multi C codes to 00:05:14.580 --> 00:05:18.170 align:start position:0% that's basically the multi C codes to vote<00:05:14.850> on<00:05:15.090> adding<00:05:15.480> or<00:05:15.690> removing<00:05:15.860> members<00:05:17.180> all 00:05:18.170 --> 00:05:18.180 align:start position:0% vote on adding or removing members all 00:05:18.180 --> 00:05:20.180 align:start position:0% vote on adding or removing members all the<00:05:18.240> members<00:05:18.780> they<00:05:19.140> pledge<00:05:19.410> to<00:05:19.620> persist<00:05:20.010> each 00:05:20.180 --> 00:05:20.190 align:start position:0% the members they pledge to persist each 00:05:20.190 --> 00:05:23.600 align:start position:0% the members they pledge to persist each other's<00:05:20.520> data<00:05:21.050> and<00:05:22.050> they<00:05:22.440> allocate<00:05:23.010> an<00:05:23.310> equal 00:05:23.600 --> 00:05:23.610 align:start position:0% other's data and they allocate an equal 00:05:23.610 --> 00:05:25.760 align:start position:0% other's data and they allocate an equal amount<00:05:23.850> of<00:05:24.030> disk<00:05:24.300> space<00:05:24.630> or<00:05:24.900> they<00:05:25.020> sort<00:05:25.680> of 00:05:25.760 --> 00:05:25.770 align:start position:0% amount of disk space or they sort of 00:05:25.770 --> 00:05:27.770 align:start position:0% amount of disk space or they sort of donate<00:05:26.190> all<00:05:26.640> an<00:05:26.820> equal<00:05:26.940> amount<00:05:27.270> of<00:05:27.480> disk<00:05:27.630> space 00:05:27.770 --> 00:05:27.780 align:start position:0% donate all an equal amount of disk space 00:05:27.780 --> 00:05:30.920 align:start position:0% donate all an equal amount of disk space in<00:05:28.770> the<00:05:28.920> consortium<00:05:29.310> so<00:05:30.240> it's<00:05:30.390> interesting<00:05:30.600> to 00:05:30.920 --> 00:05:30.930 align:start position:0% in the consortium so it's interesting to 00:05:30.930 --> 00:05:34.280 align:start position:0% in the consortium so it's interesting to notice<00:05:31.140> that<00:05:32.240> so<00:05:33.240> we<00:05:33.330> can<00:05:33.510> deploy<00:05:33.930> one<00:05:34.200> of 00:05:34.280 --> 00:05:34.290 align:start position:0% notice that so we can deploy one of 00:05:34.290 --> 00:05:35.930 align:start position:0% notice that so we can deploy one of these<00:05:34.440> contracts<00:05:35.070> which<00:05:35.340> has<00:05:35.490> a<00:05:35.520> certain 00:05:35.930 --> 00:05:35.940 align:start position:0% these contracts which has a certain 00:05:35.940 --> 00:05:38.750 align:start position:0% these contracts which has a certain quota<00:05:36.210> m--<00:05:36.450> and<00:05:36.780> all<00:05:37.020> the<00:05:37.140> members<00:05:37.500> there<00:05:37.770> they 00:05:38.750 --> 00:05:38.760 align:start position:0% quota m-- and all the members there they 00:05:38.760 --> 00:05:41.060 align:start position:0% quota m-- and all the members there they say<00:05:38.910> ok<00:05:39.150> we<00:05:39.330> are<00:05:39.360> going<00:05:39.960> to<00:05:40.170> do<00:05:40.290> this<00:05:40.440> like<00:05:40.740> for 00:05:41.060 --> 00:05:41.070 align:start position:0% say ok we are going to do this like for 00:05:41.070 --> 00:05:42.730 align:start position:0% say ok we are going to do this like for example<00:05:41.130> with<00:05:41.490> the<00:05:41.550> quorum<00:05:41.850> of<00:05:41.940> 10<00:05:42.150> gigabytes 00:05:42.730 --> 00:05:42.740 align:start position:0% example with the quorum of 10 gigabytes 00:05:42.740 --> 00:05:45.620 align:start position:0% example with the quorum of 10 gigabytes but<00:05:43.740> it's<00:05:43.860> very<00:05:43.980> easy<00:05:44.340> to<00:05:44.460> deploy<00:05:44.730> a<00:05:45.150> second 00:05:45.620 --> 00:05:45.630 align:start position:0% but it's very easy to deploy a second 00:05:45.630 --> 00:05:47.960 align:start position:0% but it's very easy to deploy a second contract<00:05:45.870> we<00:05:46.650> then<00:05:46.800> has<00:05:47.010> like<00:05:47.280> for<00:05:47.520> example<00:05:47.580> a 00:05:47.960 --> 00:05:47.970 align:start position:0% contract we then has like for example a 00:05:47.970 --> 00:05:50.270 align:start position:0% contract we then has like for example a quorum<00:05:48.270> of<00:05:48.330> 50<00:05:49.200> gigabyte<00:05:49.620> so<00:05:49.830> you<00:05:49.920> can<00:05:50.040> just 00:05:50.270 --> 00:05:50.280 align:start position:0% quorum of 50 gigabyte so you can just 00:05:50.280 --> 00:05:54.080 align:start position:0% quorum of 50 gigabyte so you can just choose<00:05:50.550> to<00:05:51.300> set<00:05:51.480> up<00:05:51.570> new<00:05:51.600> of<00:05:52.050> these<00:05:53.090> contracts 00:05:54.080 --> 00:05:54.090 align:start position:0% choose to set up new of these contracts 00:05:54.090 --> 00:05:56.330 align:start position:0% choose to set up new of these contracts some<00:05:54.990> of<00:05:55.110> the<00:05:55.200> future<00:05:55.560> enhancements<00:05:56.160> that<00:05:56.250> you 00:05:56.330 --> 00:05:56.340 align:start position:0% some of the future enhancements that you 00:05:56.340 --> 00:05:59.240 align:start position:0% some of the future enhancements that you want<00:05:56.520> to<00:05:56.640> bring<00:05:56.820> is<00:05:57.570> that<00:05:57.690> we<00:05:57.840> can<00:05:57.990> also<00:05:58.250> do 00:05:59.240 --> 00:05:59.250 align:start position:0% want to bring is that we can also do 00:05:59.250 --> 00:06:01.520 align:start position:0% want to bring is that we can also do painting<00:05:59.610> via<00:05:59.790> whisper<00:06:00.270> so<00:06:01.050> the<00:06:01.080> ideas 00:06:01.520 --> 00:06:01.530 align:start position:0% painting via whisper so the ideas 00:06:01.530 --> 00:06:04.280 align:start position:0% painting via whisper so the ideas attitudes<00:06:01.710> just<00:06:02.190> call<00:06:03.000> or<00:06:03.630> create<00:06:03.960> a<00:06:03.990> data 00:06:04.280 --> 00:06:04.290 align:start position:0% attitudes just call or create a data 00:06:04.290 --> 00:06:07.010 align:start position:0% attitudes just call or create a data data<00:06:04.980> payload<00:06:05.310> in<00:06:05.700> whisper<00:06:06.120> which<00:06:06.720> has<00:06:06.900> the 00:06:07.010 --> 00:06:07.020 align:start position:0% data payload in whisper which has the 00:06:07.020 --> 00:06:08.840 align:start position:0% data payload in whisper which has the same<00:06:07.230> commands<00:06:07.680> to<00:06:07.770> add<00:06:07.980> hash<00:06:08.280> and<00:06:08.550> remove 00:06:08.840 --> 00:06:08.850 align:start position:0% same commands to add hash and remove 00:06:08.850 --> 00:06:12.050 align:start position:0% same commands to add hash and remove hash<00:06:09.590> which<00:06:10.590> is<00:06:10.710> the<00:06:10.830> ipfs<00:06:11.250> edge<00:06:11.430> itself<00:06:11.850> and 00:06:12.050 --> 00:06:12.060 align:start position:0% hash which is the ipfs edge itself and 00:06:12.060 --> 00:06:14.390 align:start position:0% hash which is the ipfs edge itself and time-to-live<00:06:12.630> they<00:06:13.350> we<00:06:13.440> create<00:06:13.740> a<00:06:13.770> hash<00:06:14.040> they 00:06:14.390 --> 00:06:14.400 align:start position:0% time-to-live they we create a hash they 00:06:14.400 --> 00:06:16.400 align:start position:0% time-to-live they we create a hash they will<00:06:14.610> actually<00:06:14.760> sign<00:06:15.270> with<00:06:15.870> an<00:06:15.990> elliptic 00:06:16.400 --> 00:06:16.410 align:start position:0% will actually sign with an elliptic 00:06:16.410 --> 00:06:20.330 align:start position:0% will actually sign with an elliptic curve<00:06:16.620> signature<00:06:17.420> this<00:06:18.420> payload<00:06:19.070> and<00:06:20.070> you<00:06:20.190> can 00:06:20.330 --> 00:06:20.340 align:start position:0% curve signature this payload and you can 00:06:20.340 --> 00:06:21.890 align:start position:0% curve signature this payload and you can just<00:06:20.520> send<00:06:20.730> it<00:06:20.820> to<00:06:20.910> a<00:06:20.940> whisper<00:06:21.120> channel<00:06:21.600> and<00:06:21.780> we 00:06:21.890 --> 00:06:21.900 align:start position:0% just send it to a whisper channel and we 00:06:21.900 --> 00:06:24.290 align:start position:0% just send it to a whisper channel and we can<00:06:22.140> have<00:06:22.350> them<00:06:22.530> the<00:06:22.770> script<00:06:23.610> listen<00:06:24.090> to<00:06:24.180> this 00:06:24.290 --> 00:06:24.300 align:start position:0% can have them the script listen to this 00:06:24.300 --> 00:06:26.420 align:start position:0% can have them the script listen to this whisper<00:06:24.630> channel<00:06:24.990> and<00:06:25.860> just<00:06:26.100> pick<00:06:26.310> these 00:06:26.420 --> 00:06:26.430 align:start position:0% whisper channel and just pick these 00:06:26.430 --> 00:06:29.600 align:start position:0% whisper channel and just pick these things<00:06:26.670> up<00:06:27.230> so<00:06:28.230> to<00:06:28.680> give<00:06:28.830> a<00:06:28.860> round<00:06:29.070> up<00:06:29.310> on<00:06:29.490> the 00:06:29.600 --> 00:06:29.610 align:start position:0% things up so to give a round up on the 00:06:29.610 --> 00:06:31.220 align:start position:0% things up so to give a round up on the IPS<00:06:30.030> consortium<00:06:30.660> so<00:06:30.990> we<00:06:31.080> have<00:06:31.170> the 00:06:31.220 --> 00:06:31.230 align:start position:0% IPS consortium so we have the 00:06:31.230 --> 00:06:33.290 align:start position:0% IPS consortium so we have the possibility<00:06:31.590> to<00:06:31.800> do<00:06:32.040> unchained<00:06:32.550> pinning<00:06:32.970> by 00:06:33.290 --> 00:06:33.300 align:start position:0% possibility to do unchained pinning by 00:06:33.300 --> 00:06:35.810 align:start position:0% possibility to do unchained pinning by smart<00:06:33.690> contracts<00:06:34.230> we<00:06:35.070> can<00:06:35.250> do<00:06:35.370> off<00:06:35.520> chain 00:06:35.810 --> 00:06:35.820 align:start position:0% smart contracts we can do off chain 00:06:35.820 --> 00:06:38.090 align:start position:0% smart contracts we can do off chain pinning<00:06:36.210> by<00:06:36.570> the<00:06:36.630> tab<00:06:36.960> or<00:06:37.169> the<00:06:37.200> scripts<00:06:37.650> which 00:06:38.090 --> 00:06:38.100 align:start position:0% pinning by the tab or the scripts which 00:06:38.100 --> 00:06:41.330 align:start position:0% pinning by the tab or the scripts which then<00:06:38.250> perform<00:06:38.640> the<00:06:38.669> transaction<00:06:39.410> we<00:06:40.410> can 00:06:41.330 --> 00:06:41.340 align:start position:0% then perform the transaction we can 00:06:41.340 --> 00:06:42.590 align:start position:0% then perform the transaction we can using<00:06:41.490> the<00:06:41.580> whisper<00:06:41.850> solution<00:06:42.270> also<00:06:42.510> to 00:06:42.590 --> 00:06:42.600 align:start position:0% using the whisper solution also to 00:06:42.600 --> 00:06:46.879 align:start position:0% using the whisper solution also to obtain<00:06:42.810> painting<00:06:43.350> without<00:06:44.040> a<00:06:44.190> transaction<00:06:45.889> so 00:06:46.879 --> 00:06:46.889 align:start position:0% obtain painting without a transaction so 00:06:46.889 --> 00:06:49.100 align:start position:0% obtain painting without a transaction so just<00:06:47.100> buy<00:06:47.430> sign<00:06:47.699> it<00:06:47.880> with<00:06:48.060> your<00:06:48.210> with<00:06:48.870> your<00:06:49.020> own 00:06:49.100 --> 00:06:49.110 align:start position:0% just buy sign it with your with your own 00:06:49.110 --> 00:06:51.290 align:start position:0% just buy sign it with your with your own key<00:06:49.350> we<00:06:50.100> have<00:06:50.190> the<00:06:50.310> multi-member<00:06:50.699> voting<00:06:51.210> to 00:06:51.290 --> 00:06:51.300 align:start position:0% key we have the multi-member voting to 00:06:51.300 --> 00:06:53.150 align:start position:0% key we have the multi-member voting to add<00:06:51.449> and<00:06:51.630> remove<00:06:51.690> participants<00:06:52.440> without<00:06:53.130> a 00:06:53.150 --> 00:06:53.160 align:start position:0% add and remove participants without a 00:06:53.160 --> 00:06:55.370 align:start position:0% add and remove participants without a quotient<00:06:53.699> but<00:06:54.510> on<00:06:54.630> top<00:06:54.810> of<00:06:54.930> that<00:06:55.050> we<00:06:55.260> also 00:06:55.370 --> 00:06:55.380 align:start position:0% quotient but on top of that we also 00:06:55.380 --> 00:06:57.080 align:start position:0% quotient but on top of that we also supports<00:06:55.979> that<00:06:56.460> the<00:06:56.580> network<00:06:56.910> is 00:06:57.080 --> 00:06:57.090 align:start position:0% supports that the network is 00:06:57.090 --> 00:06:58.490 align:start position:0% supports that the network is permissionless<00:06:57.600> maybe<00:06:58.110> I'll<00:06:58.229> give<00:06:58.380> it<00:06:58.470> back 00:06:58.490 --> 00:06:58.500 align:start position:0% permissionless maybe I'll give it back 00:06:58.500 --> 00:07:01.670 align:start position:0% permissionless maybe I'll give it back to<00:06:58.740> King<00:06:58.919> sir<00:06:59.660> so<00:07:00.660> that's<00:07:00.900> that's<00:07:01.320> a<00:07:01.470> really 00:07:01.670 --> 00:07:01.680 align:start position:0% to King sir so that's that's a really 00:07:01.680 --> 00:07:07.159 align:start position:0% to King sir so that's that's a really interesting<00:07:01.710> case<00:07:04.010> so<00:07:05.060> anyone<00:07:06.060> can<00:07:06.449> run<00:07:06.960> this 00:07:07.159 --> 00:07:07.169 align:start position:0% interesting case so anyone can run this 00:07:07.169 --> 00:07:09.200 align:start position:0% interesting case so anyone can run this proxy<00:07:08.010> script<00:07:08.310> at<00:07:08.490> home<00:07:08.699> on<00:07:08.910> their<00:07:09.090> own 00:07:09.200 --> 00:07:09.210 align:start position:0% proxy script at home on their own 00:07:09.210 --> 00:07:12.710 align:start position:0% proxy script at home on their own computers<00:07:09.720> and<00:07:10.050> like<00:07:10.770> we<00:07:10.949> saw<00:07:11.160> in<00:07:11.580> Barcelona<00:07:12.570> a 00:07:12.710 --> 00:07:12.720 align:start position:0% computers and like we saw in Barcelona a 00:07:12.720 --> 00:07:14.210 align:start position:0% computers and like we saw in Barcelona a couple<00:07:13.050> of<00:07:13.110> weeks<00:07:13.320> ago<00:07:13.470> when<00:07:13.800> the<00:07:13.889> Spanish 00:07:14.210 --> 00:07:14.220 align:start position:0% couple of weeks ago when the Spanish 00:07:14.220 --> 00:07:16.400 align:start position:0% couple of weeks ago when the Spanish government<00:07:14.729> tries<00:07:14.940> to<00:07:15.180> block<00:07:15.389> IP<00:07:15.750> FS<00:07:16.169> host 00:07:16.400 --> 00:07:16.410 align:start position:0% government tries to block IP FS host 00:07:16.410 --> 00:07:19.250 align:start position:0% government tries to block IP FS host names<00:07:16.820> that<00:07:17.820> we<00:07:18.060> think<00:07:18.300> it<00:07:18.419> can<00:07:18.750> be<00:07:18.930> powerful 00:07:19.250 --> 00:07:19.260 align:start position:0% names that we think it can be powerful 00:07:19.260 --> 00:07:21.020 align:start position:0% names that we think it can be powerful that<00:07:19.560> many<00:07:19.770> people<00:07:20.160> can<00:07:20.400> actually<00:07:20.700> have<00:07:20.970> a 00:07:21.020 --> 00:07:21.030 align:start position:0% that many people can actually have a 00:07:21.030 --> 00:07:24.050 align:start position:0% that many people can actually have a voice<00:07:21.330> and<00:07:21.690> run<00:07:22.169> this<00:07:22.350> software<00:07:22.820> just<00:07:23.820> on 00:07:24.050 --> 00:07:24.060 align:start position:0% voice and run this software just on 00:07:24.060 --> 00:07:29.330 align:start position:0% voice and run this software just on their<00:07:24.180> own<00:07:24.270> computers<00:07:27.050> currently<00:07:28.050> yep<00:07:28.680> ipfs 00:07:29.330 --> 00:07:29.340 align:start position:0% their own computers currently yep ipfs 00:07:29.340 --> 00:07:32.360 align:start position:0% their own computers currently yep ipfs consortium<00:07:29.910> is<00:07:30.090> of<00:07:30.240> course<00:07:30.500> in<00:07:31.500> kind<00:07:32.310> of 00:07:32.360 --> 00:07:32.370 align:start position:0% consortium is of course in kind of 00:07:32.370 --> 00:07:35.480 align:start position:0% consortium is of course in kind of prototype<00:07:32.940> or<00:07:33.840> or<00:07:34.169> it's<00:07:34.410> it's<00:07:34.650> like<00:07:34.889> we<00:07:35.250> we 00:07:35.480 --> 00:07:35.490 align:start position:0% prototype or or it's it's like we we 00:07:35.490 --> 00:07:38.270 align:start position:0% prototype or or it's it's like we we proved<00:07:35.820> that<00:07:35.970> it<00:07:36.150> works<00:07:36.450> but<00:07:37.050> of<00:07:37.289> course<00:07:37.770> we 00:07:38.270 --> 00:07:38.280 align:start position:0% proved that it works but of course we 00:07:38.280 --> 00:07:40.909 align:start position:0% proved that it works but of course we are<00:07:38.400> inviting<00:07:39.030> everybody<00:07:39.300> to<00:07:39.570> to<00:07:40.169> join<00:07:40.410> us<00:07:40.620> in 00:07:40.909 --> 00:07:40.919 align:start position:0% are inviting everybody to to join us in 00:07:40.919 --> 00:07:42.980 align:start position:0% are inviting everybody to to join us in to<00:07:41.100> make<00:07:41.280> sure<00:07:41.430> that<00:07:41.850> we<00:07:42.000> can<00:07:42.180> have<00:07:42.389> data 00:07:42.980 --> 00:07:42.990 align:start position:0% to make sure that we can have data 00:07:42.990 --> 00:07:46.129 align:start position:0% to make sure that we can have data persistence<00:07:43.380> in<00:07:43.770> at<00:07:43.860> the<00:07:43.949> central<00:07:44.340> point<00:07:45.139> so 00:07:46.129 --> 00:07:46.139 align:start position:0% persistence in at the central point so 00:07:46.139 --> 00:07:48.140 align:start position:0% persistence in at the central point so the<00:07:46.380> second<00:07:46.800> thing<00:07:47.310> we<00:07:47.460> want<00:07:47.490> to<00:07:47.729> talk<00:07:47.970> about 00:07:48.140 --> 00:07:48.150 align:start position:0% the second thing we want to talk about 00:07:48.150 --> 00:07:53.150 align:start position:0% the second thing we want to talk about is<00:07:48.600> the<00:07:48.960> gas<00:07:49.289> station<00:07:51.050> so<00:07:52.050> what<00:07:52.350> we<00:07:52.500> do<00:07:52.680> if<00:07:52.979> we 00:07:53.150 --> 00:07:53.160 align:start position:0% is the gas station so what we do if we 00:07:53.160 --> 00:07:55.940 align:start position:0% is the gas station so what we do if we want<00:07:53.370> people<00:07:53.520> to<00:07:54.330> abort<00:07:55.020> or<00:07:55.229> project<00:07:55.710> of 00:07:55.940 --> 00:07:55.950 align:start position:0% want people to abort or project of 00:07:55.950 --> 00:07:57.350 align:start position:0% want people to abort or project of course<00:07:56.220> we<00:07:56.370> send<00:07:56.580> them<00:07:56.700> some<00:07:56.849> smart<00:07:57.120> city 00:07:57.350 --> 00:07:57.360 align:start position:0% course we send them some smart city 00:07:57.360 --> 00:07:59.750 align:start position:0% course we send them some smart city tokens<00:07:57.840> but<00:07:58.440> then<00:07:58.590> we<00:07:58.740> always<00:07:59.010> have<00:07:59.190> to<00:07:59.550> say 00:07:59.750 --> 00:07:59.760 align:start position:0% tokens but then we always have to say 00:07:59.760 --> 00:08:02.029 align:start position:0% tokens but then we always have to say and<00:08:00.270> you<00:08:00.990> need<00:08:01.139> a<00:08:01.169> little<00:08:01.380> bit<00:08:01.530> of<00:08:01.590> heater<00:08:01.860> to 00:08:02.029 --> 00:08:02.039 align:start position:0% and you need a little bit of heater to 00:08:02.039 --> 00:08:03.200 align:start position:0% and you need a little bit of heater to actually<00:08:02.340> do<00:08:02.490> something<00:08:02.729> with<00:08:02.880> it<00:08:03.120> because 00:08:03.200 --> 00:08:03.210 align:start position:0% actually do something with it because 00:08:03.210 --> 00:08:04.700 align:start position:0% actually do something with it because every<00:08:03.630> transaction<00:08:03.900> and<00:08:04.080> then<00:08:04.380> you<00:08:04.470> have<00:08:04.590> to 00:08:04.700 --> 00:08:04.710 align:start position:0% every transaction and then you have to 00:08:04.710 --> 00:08:06.980 align:start position:0% every transaction and then you have to tell<00:08:04.889> a<00:08:04.919> whole<00:08:05.010> story<00:08:05.160> about<00:08:05.550> gas<00:08:06.240> right<00:08:06.750> so 00:08:06.980 --> 00:08:06.990 align:start position:0% tell a whole story about gas right so 00:08:06.990 --> 00:08:09.589 align:start position:0% tell a whole story about gas right so for<00:08:07.260> for<00:08:07.650> a<00:08:07.680> lot<00:08:07.830> of<00:08:07.889> people<00:08:08.400> like<00:08:08.610> my<00:08:09.150> dad<00:08:09.360> for 00:08:09.589 --> 00:08:09.599 align:start position:0% for for a lot of people like my dad for 00:08:09.599 --> 00:08:11.450 align:start position:0% for for a lot of people like my dad for instance<00:08:09.900> he<00:08:09.990> was<00:08:10.110> like<00:08:10.320> wow<00:08:10.560> why<00:08:10.889> do<00:08:10.950> I<00:08:11.400> need 00:08:11.450 --> 00:08:11.460 align:start position:0% instance he was like wow why do I need 00:08:11.460 --> 00:08:15.370 align:start position:0% instance he was like wow why do I need two<00:08:11.729> coins<00:08:12.090> now<00:08:12.360> or<00:08:12.570> two<00:08:12.780> tokens<00:08:13.580> so<00:08:14.580> our<00:08:14.849> ideal 00:08:15.370 --> 00:08:15.380 align:start position:0% two coins now or two tokens so our ideal 00:08:15.380 --> 00:08:17.659 align:start position:0% two coins now or two tokens so our ideal solution<00:08:16.380> will<00:08:16.530> be<00:08:16.710> that<00:08:16.979> it<00:08:17.099> is<00:08:17.220> a<00:08:17.250> one<00:08:17.639> click 00:08:17.659 --> 00:08:17.669 align:start position:0% solution will be that it is a one click 00:08:17.669 --> 00:08:20.560 align:start position:0% solution will be that it is a one click solution<00:08:17.970> in<00:08:18.870> the<00:08:19.410> front<00:08:19.680> and<00:08:19.919> in<00:08:20.130> the<00:08:20.160> app 00:08:20.560 --> 00:08:20.570 align:start position:0% solution in the front and in the app 00:08:20.570 --> 00:08:23.000 align:start position:0% solution in the front and in the app where<00:08:21.570> people<00:08:21.900> can<00:08:22.080> actually<00:08:22.229> exchange<00:08:22.680> a 00:08:23.000 --> 00:08:23.010 align:start position:0% where people can actually exchange a 00:08:23.010 --> 00:08:27.529 align:start position:0% where people can actually exchange a little<00:08:23.280> bit<00:08:23.430> of<00:08:23.639> their<00:08:23.820> tokens<00:08:24.560> for<00:08:25.560> gas<00:08:26.539> our 00:08:27.529 --> 00:08:27.539 align:start position:0% little bit of their tokens for gas our 00:08:27.539 --> 00:08:30.140 align:start position:0% little bit of their tokens for gas our design<00:08:27.900> process<00:08:28.380> is<00:08:28.650> it's<00:08:29.010> kind<00:08:29.639> of<00:08:29.760> funny<00:08:30.030> I 00:08:30.140 --> 00:08:30.150 align:start position:0% design process is it's kind of funny I 00:08:30.150 --> 00:08:32.240 align:start position:0% design process is it's kind of funny I think<00:08:30.330> because<00:08:31.080> we<00:08:31.200> always<00:08:31.530> use<00:08:31.800> the<00:08:31.950> metaphor 00:08:32.240 --> 00:08:32.250 align:start position:0% think because we always use the metaphor 00:08:32.250 --> 00:08:35.779 align:start position:0% think because we always use the metaphor of<00:08:32.669> the<00:08:32.729> city<00:08:33.120> so<00:08:33.950> if<00:08:34.950> you<00:08:35.159> drive<00:08:35.370> around<00:08:35.430> the 00:08:35.779 --> 00:08:35.789 align:start position:0% of the city so if you drive around the 00:08:35.789 --> 00:08:37.820 align:start position:0% of the city so if you drive around the city<00:08:35.880> you<00:08:36.330> of<00:08:36.479> course<00:08:36.690> need<00:08:36.930> gas<00:08:37.229> and<00:08:37.589> what<00:08:37.740> do 00:08:37.820 --> 00:08:37.830 align:start position:0% city you of course need gas and what do 00:08:37.830 --> 00:08:39.829 align:start position:0% city you of course need gas and what do you<00:08:37.860> do<00:08:38.039> then<00:08:38.250> you<00:08:38.490> go<00:08:38.640> to<00:08:38.700> a<00:08:38.849> gas<00:08:39.120> station 00:08:39.829 --> 00:08:39.839 align:start position:0% you do then you go to a gas station 00:08:39.839 --> 00:08:44.300 align:start position:0% you do then you go to a gas station oh<00:08:40.849> I'm<00:08:41.849> gonna<00:08:42.240> hand<00:08:42.990> it<00:08:43.110> over<00:08:43.229> to<00:08:43.560> spoon<00:08:44.099> ask 00:08:44.300 --> 00:08:44.310 align:start position:0% oh I'm gonna hand it over to spoon ask 00:08:44.310 --> 00:08:47.449 align:start position:0% oh I'm gonna hand it over to spoon ask for<00:08:44.490> this<00:08:44.580> yeah<00:08:45.350> thank<00:08:46.350> you 00:08:47.449 --> 00:08:47.459 align:start position:0% for this yeah thank you 00:08:47.459 --> 00:08:50.150 align:start position:0% for this yeah thank you so<00:08:47.850> the<00:08:48.270> way<00:08:48.420> many<00:08:48.810> of<00:08:48.959> the<00:08:49.500> existing<00:08:49.829> theory 00:08:50.150 --> 00:08:50.160 align:start position:0% so the way many of the existing theory 00:08:50.160 --> 00:08:51.980 align:start position:0% so the way many of the existing theory projects<00:08:50.670> solve<00:08:50.910> it<00:08:51.000> currently<00:08:51.360> is<00:08:51.570> by<00:08:51.720> just 00:08:51.980 --> 00:08:51.990 align:start position:0% projects solve it currently is by just 00:08:51.990 --> 00:08:53.730 align:start position:0% projects solve it currently is by just giving<00:08:52.680> away<00:08:52.920> some<00:08:53.160> freak 00:08:53.730 --> 00:08:53.740 align:start position:0% giving away some freak 00:08:53.740 --> 00:08:56.100 align:start position:0% giving away some freak just<00:08:54.339> sending<00:08:54.730> some<00:08:54.790> guests<00:08:55.330> to<00:08:55.480> a<00:08:55.510> certain 00:08:56.100 --> 00:08:56.110 align:start position:0% just sending some guests to a certain 00:08:56.110 --> 00:08:58.470 align:start position:0% just sending some guests to a certain address<00:08:56.320> which<00:08:56.860> is<00:08:56.890> created<00:08:57.339> in<00:08:57.370> a<00:08:57.490> wallet<00:08:57.670> in 00:08:58.470 --> 00:08:58.480 align:start position:0% address which is created in a wallet in 00:08:58.480 --> 00:09:00.150 align:start position:0% address which is created in a wallet in the<00:08:58.870> hope<00:08:59.080> that<00:08:59.290> they<00:08:59.500> will<00:08:59.620> actually<00:08:59.980> use 00:09:00.150 --> 00:09:00.160 align:start position:0% the hope that they will actually use 00:09:00.160 --> 00:09:03.329 align:start position:0% the hope that they will actually use that<00:09:00.190> gas<00:09:00.779> to<00:09:01.779> perform<00:09:02.230> transactions<00:09:03.070> in 00:09:03.329 --> 00:09:03.339 align:start position:0% that gas to perform transactions in 00:09:03.339 --> 00:09:05.940 align:start position:0% that gas to perform transactions in their<00:09:03.520> ecosystem<00:09:03.730> or<00:09:04.420> to<00:09:04.839> use<00:09:04.990> their<00:09:05.200> app<00:09:05.380> but 00:09:05.940 --> 00:09:05.950 align:start position:0% their ecosystem or to use their app but 00:09:05.950 --> 00:09:07.320 align:start position:0% their ecosystem or to use their app but most<00:09:06.160> of<00:09:06.220> the<00:09:06.310> time<00:09:06.459> it<00:09:06.580> can't<00:09:06.760> be<00:09:06.850> sure<00:09:07.120> if 00:09:07.320 --> 00:09:07.330 align:start position:0% most of the time it can't be sure if 00:09:07.330 --> 00:09:08.910 align:start position:0% most of the time it can't be sure if they<00:09:07.450> will<00:09:07.570> actually<00:09:07.600> use<00:09:08.110> the<00:09:08.260> gas<00:09:08.470> for<00:09:08.740> debts 00:09:08.910 --> 00:09:08.920 align:start position:0% they will actually use the gas for debts 00:09:08.920 --> 00:09:10.680 align:start position:0% they will actually use the gas for debts or<00:09:09.100> to<00:09:09.279> just<00:09:09.490> do<00:09:09.670> some<00:09:09.850> sort<00:09:10.060> of<00:09:10.149> sibling<00:09:10.570> tag 00:09:10.680 --> 00:09:10.690 align:start position:0% or to just do some sort of sibling tag 00:09:10.690 --> 00:09:13.079 align:start position:0% or to just do some sort of sibling tag and<00:09:10.899> just<00:09:11.050> try<00:09:11.260> to<00:09:11.320> collect<00:09:12.100> as<00:09:12.279> much<00:09:12.459> free<00:09:12.880> gas 00:09:13.079 --> 00:09:13.089 align:start position:0% and just try to collect as much free gas 00:09:13.089 --> 00:09:13.769 align:start position:0% and just try to collect as much free gas as<00:09:13.270> possible 00:09:13.769 --> 00:09:13.779 align:start position:0% as possible 00:09:13.779 --> 00:09:15.960 align:start position:0% as possible another<00:09:14.620> problem<00:09:14.920> is<00:09:15.130> also<00:09:15.310> that<00:09:15.550> if<00:09:15.670> your<00:09:15.790> app 00:09:15.960 --> 00:09:15.970 align:start position:0% another problem is also that if your app 00:09:15.970 --> 00:09:17.670 align:start position:0% another problem is also that if your app becomes<00:09:16.149> very<00:09:16.540> successful<00:09:17.170> you<00:09:17.260> have<00:09:17.350> to<00:09:17.470> have 00:09:17.670 --> 00:09:17.680 align:start position:0% becomes very successful you have to have 00:09:17.680 --> 00:09:20.790 align:start position:0% becomes very successful you have to have a<00:09:17.709> lot<00:09:17.890> of<00:09:17.940> eater<00:09:19.140> somewhere<00:09:20.140> just<00:09:20.320> to<00:09:20.440> provide 00:09:20.790 --> 00:09:20.800 align:start position:0% a lot of eater somewhere just to provide 00:09:20.800 --> 00:09:22.889 align:start position:0% a lot of eater somewhere just to provide everybody<00:09:21.070> with<00:09:21.310> some<00:09:21.760> free<00:09:22.060> gas<00:09:22.390> to<00:09:22.720> get 00:09:22.889 --> 00:09:22.899 align:start position:0% everybody with some free gas to get 00:09:22.899 --> 00:09:25.050 align:start position:0% everybody with some free gas to get started<00:09:23.350> so<00:09:24.190> we<00:09:24.279> tried<00:09:24.490> to<00:09:24.520> come<00:09:24.760> up<00:09:24.820> with<00:09:25.000> a 00:09:25.050 --> 00:09:25.060 align:start position:0% started so we tried to come up with a 00:09:25.060 --> 00:09:27.660 align:start position:0% started so we tried to come up with a solution<00:09:25.680> where<00:09:26.680> you<00:09:26.740> can<00:09:26.830> actually<00:09:26.980> just<00:09:27.310> do 00:09:27.660 --> 00:09:27.670 align:start position:0% solution where you can actually just do 00:09:27.670 --> 00:09:29.280 align:start position:0% solution where you can actually just do the<00:09:27.790> exchange<00:09:28.209> we<00:09:28.420> have<00:09:28.510> like<00:09:28.779> durable 00:09:29.280 --> 00:09:29.290 align:start position:0% the exchange we have like durable 00:09:29.290 --> 00:09:30.960 align:start position:0% the exchange we have like durable solution<00:09:29.740> that<00:09:29.860> people<00:09:29.980> just<00:09:30.250> are<00:09:30.520> able<00:09:30.940> to 00:09:30.960 --> 00:09:30.970 align:start position:0% solution that people just are able to 00:09:30.970 --> 00:09:34.230 align:start position:0% solution that people just are able to pay<00:09:31.300> with<00:09:31.330> our<00:09:31.540> tokens<00:09:32.850> for<00:09:33.850> getting<00:09:34.149> the 00:09:34.230 --> 00:09:34.240 align:start position:0% pay with our tokens for getting the 00:09:34.240 --> 00:09:36.600 align:start position:0% pay with our tokens for getting the initial<00:09:34.570> guess<00:09:34.839> so<00:09:35.529> it's<00:09:35.649> always<00:09:35.800> it's<00:09:36.279> also<00:09:36.459> a 00:09:36.600 --> 00:09:36.610 align:start position:0% initial guess so it's always it's also a 00:09:36.610 --> 00:09:39.090 align:start position:0% initial guess so it's always it's also a two-part<00:09:37.270> solution<00:09:37.839> so<00:09:38.560> first<00:09:38.800> of<00:09:38.980> all 00:09:39.090 --> 00:09:39.100 align:start position:0% two-part solution so first of all 00:09:39.100 --> 00:09:42.210 align:start position:0% two-part solution so first of all there's<00:09:39.610> an<00:09:39.760> API<00:09:40.120> which<00:09:41.080> needs<00:09:41.320> to<00:09:41.440> run<00:09:41.680> which 00:09:42.210 --> 00:09:42.220 align:start position:0% there's an API which needs to run which 00:09:42.220 --> 00:09:45.240 align:start position:0% there's an API which needs to run which is<00:09:42.250> gas<00:09:42.640> station<00:09:43.029> service<00:09:43.480> and<00:09:44.160> next<00:09:45.160> to<00:09:45.220> that 00:09:45.240 --> 00:09:45.250 align:start position:0% is gas station service and next to that 00:09:45.250 --> 00:09:48.000 align:start position:0% is gas station service and next to that we<00:09:45.399> have<00:09:45.580> a<00:09:45.970> gas<00:09:46.270> station<00:09:46.540> contracts<00:09:47.529> that's 00:09:48.000 --> 00:09:48.010 align:start position:0% we have a gas station contracts that's 00:09:48.010 --> 00:09:50.940 align:start position:0% we have a gas station contracts that's deployed<00:09:48.399> in<00:09:49.209> lockstep<00:09:49.600> with<00:09:49.720> that<00:09:50.050> so<00:09:50.680> people 00:09:50.940 --> 00:09:50.950 align:start position:0% deployed in lockstep with that so people 00:09:50.950 --> 00:09:54.110 align:start position:0% deployed in lockstep with that so people can<00:09:51.070> actually<00:09:51.220> just<00:09:51.580> run<00:09:52.180> it<00:09:52.330> themselves<00:09:52.450> so 00:09:54.110 --> 00:09:54.120 align:start position:0% can actually just run it themselves so 00:09:54.120 --> 00:09:57.030 align:start position:0% can actually just run it themselves so first<00:09:55.120> of<00:09:55.240> all<00:09:55.360> you<00:09:55.450> decide<00:09:55.779> which<00:09:56.110> ERC<00:09:56.680> 20 00:09:57.030 --> 00:09:57.040 align:start position:0% first of all you decide which ERC 20 00:09:57.040 --> 00:09:59.160 align:start position:0% first of all you decide which ERC 20 token<00:09:57.370> you<00:09:57.430> would<00:09:57.640> like<00:09:58.120> to<00:09:58.240> support<00:09:58.420> so<00:09:59.079> in 00:09:59.160 --> 00:09:59.170 align:start position:0% token you would like to support so in 00:09:59.170 --> 00:10:01.889 align:start position:0% token you would like to support so in our<00:09:59.260> case<00:09:59.470> it's<00:09:59.680> Warren<00:09:59.980> city<00:10:00.160> token<00:10:00.779> and<00:10:01.779> then 00:10:01.889 --> 00:10:01.899 align:start position:0% our case it's Warren city token and then 00:10:01.899 --> 00:10:04.230 align:start position:0% our case it's Warren city token and then you<00:10:02.079> send<00:10:02.350> some<00:10:02.560> initial<00:10:03.250> eater<00:10:03.520> which<00:10:04.029> is 00:10:04.230 --> 00:10:04.240 align:start position:0% you send some initial eater which is 00:10:04.240 --> 00:10:05.639 align:start position:0% you send some initial eater which is this<00:10:04.360> one<00:10:04.600> eater<00:10:04.870> because<00:10:05.110> just<00:10:05.529> about 00:10:05.639 --> 00:10:05.649 align:start position:0% this one eater because just about 00:10:05.649 --> 00:10:07.740 align:start position:0% this one eater because just about providing<00:10:06.459> initial<00:10:06.610> guesses<00:10:07.149> it<00:10:07.480> doesn't 00:10:07.740 --> 00:10:07.750 align:start position:0% providing initial guesses it doesn't 00:10:07.750 --> 00:10:10.380 align:start position:0% providing initial guesses it doesn't need<00:10:07.839> an<00:10:07.990> big<00:10:08.620> amount<00:10:08.890> of<00:10:08.980> feature<00:10:09.190> you<00:10:10.149> send 00:10:10.380 --> 00:10:10.390 align:start position:0% need an big amount of feature you send 00:10:10.390 --> 00:10:12.269 align:start position:0% need an big amount of feature you send it<00:10:10.450> to<00:10:10.540> the<00:10:10.660> gas<00:10:10.810> station<00:10:11.200> to<00:10:11.230> sort<00:10:11.620> of<00:10:11.709> fill<00:10:12.160> it 00:10:12.269 --> 00:10:12.279 align:start position:0% it to the gas station to sort of fill it 00:10:12.279 --> 00:10:15.780 align:start position:0% it to the gas station to sort of fill it up<00:10:12.399> with<00:10:13.149> eater<00:10:14.100> so<00:10:15.100> that's<00:10:15.279> the<00:10:15.399> setup 00:10:15.780 --> 00:10:15.790 align:start position:0% up with eater so that's the setup 00:10:15.790 --> 00:10:19.440 align:start position:0% up with eater so that's the setup if<00:10:16.540> you<00:10:16.720> then<00:10:16.899> have<00:10:17.110> a<00:10:17.140> dab<00:10:17.520> so<00:10:18.520> the<00:10:18.850> use<00:10:19.329> case 00:10:19.440 --> 00:10:19.450 align:start position:0% if you then have a dab so the use case 00:10:19.450 --> 00:10:21.990 align:start position:0% if you then have a dab so the use case here<00:10:19.600> is<00:10:20.410> that<00:10:20.529> you<00:10:20.649> have<00:10:20.740> like<00:10:20.920> a<00:10:21.310> new<00:10:21.730> user 00:10:21.990 --> 00:10:22.000 align:start position:0% here is that you have like a new user 00:10:22.000 --> 00:10:25.050 align:start position:0% here is that you have like a new user who<00:10:22.959> someone<00:10:23.290> just<00:10:23.589> sent<00:10:23.829> some<00:10:24.520> a<00:10:24.700> couple<00:10:25.000> of 00:10:25.050 --> 00:10:25.060 align:start position:0% who someone just sent some a couple of 00:10:25.060 --> 00:10:26.430 align:start position:0% who someone just sent some a couple of this<00:10:25.149> swarm<00:10:25.420> city<00:10:25.660> tokens<00:10:25.990> but<00:10:26.079> it<00:10:26.200> doesn't 00:10:26.430 --> 00:10:26.440 align:start position:0% this swarm city tokens but it doesn't 00:10:26.440 --> 00:10:28.019 align:start position:0% this swarm city tokens but it doesn't have<00:10:26.529> any<00:10:26.680> gas<00:10:26.920> weekend's<00:10:27.490> doing<00:10:27.970> a 00:10:28.019 --> 00:10:28.029 align:start position:0% have any gas weekend's doing a 00:10:28.029 --> 00:10:31.740 align:start position:0% have any gas weekend's doing a transaction<00:10:28.390> yet<00:10:29.730> so<00:10:30.730> the<00:10:31.209> thingy<00:10:31.420> can 00:10:31.740 --> 00:10:31.750 align:start position:0% transaction yet so the thingy can 00:10:31.750 --> 00:10:34.470 align:start position:0% transaction yet so the thingy can calculate<00:10:32.320> is<00:10:32.529> how<00:10:32.680> much<00:10:32.890> way<00:10:33.820> he<00:10:34.329> will 00:10:34.470 --> 00:10:34.480 align:start position:0% calculate is how much way he will 00:10:34.480 --> 00:10:36.510 align:start position:0% calculate is how much way he will actually<00:10:34.839> need<00:10:35.050> to<00:10:35.290> perform<00:10:35.709> you<00:10:36.250> know<00:10:36.279> do<00:10:36.430> the 00:10:36.510 --> 00:10:36.520 align:start position:0% actually need to perform you know do the 00:10:36.520 --> 00:10:37.980 align:start position:0% actually need to perform you know do the first<00:10:36.790> transactions<00:10:37.360> that<00:10:37.450> he<00:10:37.540> wants<00:10:37.750> to<00:10:37.839> do 00:10:37.980 --> 00:10:37.990 align:start position:0% first transactions that he wants to do 00:10:37.990 --> 00:10:41.220 align:start position:0% first transactions that he wants to do to<00:10:38.290> get<00:10:38.680> started<00:10:39.220> so<00:10:40.120> we<00:10:40.209> will<00:10:40.300> ask<00:10:40.540> to<00:10:40.870> the<00:10:41.050> gas 00:10:41.220 --> 00:10:41.230 align:start position:0% to get started so we will ask to the gas 00:10:41.230 --> 00:10:43.860 align:start position:0% to get started so we will ask to the gas station<00:10:41.620> service<00:10:42.040> what<00:10:42.579> is<00:10:42.670> your<00:10:42.790> price<00:10:43.270> for 00:10:43.860 --> 00:10:43.870 align:start position:0% station service what is your price for 00:10:43.870 --> 00:10:46.800 align:start position:0% station service what is your price for this<00:10:43.990> amount<00:10:44.200> of<00:10:44.380> way<00:10:44.620> that<00:10:45.040> I<00:10:45.130> will<00:10:45.310> need<00:10:45.810> the 00:10:46.800 --> 00:10:46.810 align:start position:0% this amount of way that I will need the 00:10:46.810 --> 00:10:49.100 align:start position:0% this amount of way that I will need the gas<00:10:47.020> station<00:10:47.440> you<00:10:47.620> will<00:10:47.740> consult<00:10:48.100> a<00:10:48.250> public 00:10:49.100 --> 00:10:49.110 align:start position:0% gas station you will consult a public 00:10:49.110 --> 00:10:51.660 align:start position:0% gas station you will consult a public price<00:10:50.110> API<00:10:50.560> to<00:10:51.100> see<00:10:51.279> what<00:10:51.399> the<00:10:51.490> current 00:10:51.660 --> 00:10:51.670 align:start position:0% price API to see what the current 00:10:51.670 --> 00:10:54.150 align:start position:0% price API to see what the current exchange<00:10:52.000> rate<00:10:52.420> is<00:10:52.600> for<00:10:52.899> either<00:10:53.320> to<00:10:53.890> swarm 00:10:54.150 --> 00:10:54.160 align:start position:0% exchange rate is for either to swarm 00:10:54.160 --> 00:10:57.480 align:start position:0% exchange rate is for either to swarm city<00:10:54.370> tokens<00:10:54.820> and<00:10:55.480> it<00:10:55.779> will<00:10:55.899> reply<00:10:56.260> to<00:10:56.740> say<00:10:57.160> ok 00:10:57.480 --> 00:10:57.490 align:start position:0% city tokens and it will reply to say ok 00:10:57.490 --> 00:10:59.490 align:start position:0% city tokens and it will reply to say ok this<00:10:57.790> many<00:10:58.000> way<00:10:58.240> would<00:10:58.630> cost<00:10:58.839> you<00:10:59.020> that<00:10:59.260> many 00:10:59.490 --> 00:10:59.500 align:start position:0% this many way would cost you that many 00:10:59.500 --> 00:11:02.910 align:start position:0% this many way would cost you that many swarm<00:10:59.829> city<00:11:00.100> tokens<00:11:01.560> the<00:11:02.560> next<00:11:02.770> thing<00:11:02.890> that 00:11:02.910 --> 00:11:02.920 align:start position:0% swarm city tokens the next thing that 00:11:02.920 --> 00:11:06.240 align:start position:0% swarm city tokens the next thing that happens<00:11:03.400> is<00:11:03.730> that<00:11:03.760> the<00:11:04.600> device<00:11:05.410> itself<00:11:05.829> for 00:11:06.240 --> 00:11:06.250 align:start position:0% happens is that the device itself for 00:11:06.250 --> 00:11:07.140 align:start position:0% happens is that the device itself for the<00:11:06.370> tap 00:11:07.140 --> 00:11:07.150 align:start position:0% the tap 00:11:07.150 --> 00:11:10.110 align:start position:0% the tap will<00:11:07.420> sign<00:11:07.720> an<00:11:08.140> allowance<00:11:08.770> which<00:11:09.279> is<00:11:09.310> a<00:11:09.460> year<00:11:09.940> C 00:11:10.110 --> 00:11:10.120 align:start position:0% will sign an allowance which is a year C 00:11:10.120 --> 00:11:12.900 align:start position:0% will sign an allowance which is a year C 20<00:11:10.510> function<00:11:10.930> to<00:11:11.589> the<00:11:11.710> gas-station<00:11:12.130> contracts 00:11:12.900 --> 00:11:12.910 align:start position:0% 20 function to the gas-station contracts 00:11:12.910 --> 00:11:16.410 align:start position:0% 20 function to the gas-station contracts for<00:11:13.360> that<00:11:13.480> amount<00:11:13.750> of<00:11:13.930> swarm<00:11:14.230> city<00:11:14.500> tokens<00:11:15.420> and 00:11:16.410 --> 00:11:16.420 align:start position:0% for that amount of swarm city tokens and 00:11:16.420 --> 00:11:18.180 align:start position:0% for that amount of swarm city tokens and on<00:11:16.540> top<00:11:16.750> of<00:11:16.779> that<00:11:17.020> you<00:11:17.440> will<00:11:17.560> create<00:11:17.800> an 00:11:18.180 --> 00:11:18.190 align:start position:0% on top of that you will create an 00:11:18.190 --> 00:11:21.269 align:start position:0% on top of that you will create an elliptic<00:11:18.670> curve<00:11:18.940> signature<00:11:19.890> for<00:11:20.890> all<00:11:21.100> these 00:11:21.269 --> 00:11:21.279 align:start position:0% elliptic curve signature for all these 00:11:21.279 --> 00:11:25.290 align:start position:0% elliptic curve signature for all these parameters<00:11:21.910> with<00:11:22.450> the<00:11:22.510> amount<00:11:22.750> of<00:11:24.300> swarms 00:11:25.290 --> 00:11:25.300 align:start position:0% parameters with the amount of swarms 00:11:25.300 --> 00:11:27.630 align:start position:0% parameters with the amount of swarms EPOC<00:11:25.779> is<00:11:25.810> going<00:11:26.050> to<00:11:26.140> give<00:11:26.380> and<00:11:26.980> all<00:11:27.130> that<00:11:27.339> we're 00:11:27.630 --> 00:11:27.640 align:start position:0% EPOC is going to give and all that we're 00:11:27.640 --> 00:11:33.420 align:start position:0% EPOC is going to give and all that we're going<00:11:27.790> to<00:11:27.910> adapt<00:11:29.880> one<00:11:30.880> of<00:11:30.970> the<00:11:31.029> next<00:11:31.180> slides<00:11:32.430> so 00:11:33.420 --> 00:11:33.430 align:start position:0% going to adapt one of the next slides so 00:11:33.430 --> 00:11:35.400 align:start position:0% going to adapt one of the next slides so it<00:11:33.730> will<00:11:33.850> send<00:11:34.029> its<00:11:34.270> Cyan's<00:11:34.810> action<00:11:35.110> back<00:11:35.290> to 00:11:35.400 --> 00:11:35.410 align:start position:0% it will send its Cyan's action back to 00:11:35.410 --> 00:11:37.800 align:start position:0% it will send its Cyan's action back to the<00:11:35.529> gas<00:11:35.680> station<00:11:35.710> service<00:11:36.460> and<00:11:36.700> then<00:11:37.180> the<00:11:37.540> gas 00:11:37.800 --> 00:11:37.810 align:start position:0% the gas station service and then the gas 00:11:37.810 --> 00:11:39.450 align:start position:0% the gas station service and then the gas station<00:11:38.230> service<00:11:38.560> will<00:11:38.740> verify<00:11:39.190> the 00:11:39.450 --> 00:11:39.460 align:start position:0% station service will verify the 00:11:39.460 --> 00:11:41.790 align:start position:0% station service will verify the transaction<00:11:39.820> this<00:11:40.510> will<00:11:40.779> decode<00:11:41.170> it<00:11:41.350> and<00:11:41.589> if 00:11:41.790 --> 00:11:41.800 align:start position:0% transaction this will decode it and if 00:11:41.800 --> 00:11:44.370 align:start position:0% transaction this will decode it and if it<00:11:41.890> all<00:11:42.040> fits<00:11:42.430> all<00:11:43.029> the<00:11:43.240> prerequisites<00:11:44.080> you 00:11:44.370 --> 00:11:44.380 align:start position:0% it all fits all the prerequisites you 00:11:44.380 --> 00:11:46.590 align:start position:0% it all fits all the prerequisites you will<00:11:44.830> actually<00:11:45.100> send<00:11:45.339> gas<00:11:45.670> to<00:11:46.120> that<00:11:46.270> address 00:11:46.590 --> 00:11:46.600 align:start position:0% will actually send gas to that address 00:11:46.600 --> 00:11:49.829 align:start position:0% will actually send gas to that address so<00:11:47.529> the<00:11:47.680> address<00:11:47.950> of<00:11:48.100> the<00:11:48.190> tap<00:11:48.370> to<00:11:49.180> execute<00:11:49.630> the 00:11:49.829 --> 00:11:49.839 align:start position:0% so the address of the tap to execute the 00:11:49.839 --> 00:11:52.440 align:start position:0% so the address of the tap to execute the allowance<00:11:50.200> call<00:11:50.670> when<00:11:51.670> you<00:11:51.760> see<00:11:51.940> that<00:11:52.120> that 00:11:52.440 --> 00:11:52.450 align:start position:0% allowance call when you see that that 00:11:52.450 --> 00:11:55.470 align:start position:0% allowance call when you see that that gas<00:11:52.690> has<00:11:52.720> arrived<00:11:53.350> he<00:11:53.980> will<00:11:54.160> execute<00:11:55.060> the 00:11:55.470 --> 00:11:55.480 align:start position:0% gas has arrived he will execute the 00:11:55.480 --> 00:11:57.000 align:start position:0% gas has arrived he will execute the allowance<00:11:55.839> transaction<00:11:56.290> by<00:11:56.380> just<00:11:56.589> putting<00:11:56.860> it 00:11:57.000 --> 00:11:57.010 align:start position:0% allowance transaction by just putting it 00:11:57.010 --> 00:11:59.250 align:start position:0% allowance transaction by just putting it in<00:11:57.250> the<00:11:57.370> transaction<00:11:58.029> pool<00:11:58.240> and<00:11:59.050> when<00:11:59.170> that 00:11:59.250 --> 00:11:59.260 align:start position:0% in the transaction pool and when that 00:11:59.260 --> 00:12:01.590 align:start position:0% in the transaction pool and when that transaction<00:11:59.800> is<00:11:59.920> mined<00:12:00.220> the<00:12:01.060> gas<00:12:01.240> station 00:12:01.590 --> 00:12:01.600 align:start position:0% transaction is mined the gas station 00:12:01.600 --> 00:12:03.750 align:start position:0% transaction is mined the gas station service<00:12:02.020> will<00:12:02.470> call<00:12:02.740> a<00:12:02.770> function<00:12:03.370> in<00:12:03.490> the<00:12:03.580> gas 00:12:03.750 --> 00:12:03.760 align:start position:0% service will call a function in the gas 00:12:03.760 --> 00:12:07.290 align:start position:0% service will call a function in the gas station<00:12:04.210> which<00:12:04.660> we<00:12:04.870> call<00:12:05.050> push<00:12:05.350> fill<00:12:06.210> so<00:12:07.210> let 00:12:07.290 --> 00:12:07.300 align:start position:0% station which we call push fill so let 00:12:07.300 --> 00:12:09.480 align:start position:0% station which we call push fill so let me<00:12:07.450> quickly<00:12:07.630> show<00:12:07.839> like<00:12:08.560> how<00:12:08.740> it<00:12:08.920> begins<00:12:09.279> it's 00:12:09.480 --> 00:12:09.490 align:start position:0% me quickly show like how it begins it's 00:12:09.490 --> 00:12:11.430 align:start position:0% me quickly show like how it begins it's not<00:12:09.640> a<00:12:09.670> complete<00:12:10.000> function<00:12:10.390> but<00:12:10.540> just<00:12:11.200> to<00:12:11.290> get 00:12:11.430 --> 00:12:11.440 align:start position:0% not a complete function but just to get 00:12:11.440 --> 00:12:13.860 align:start position:0% not a complete function but just to get you<00:12:11.500> to<00:12:12.040> give<00:12:12.580> you<00:12:12.670> an<00:12:12.760> idea<00:12:12.880> about<00:12:13.660> how<00:12:13.839> it 00:12:13.860 --> 00:12:13.870 align:start position:0% you to give you an idea about how it 00:12:13.870 --> 00:12:16.949 align:start position:0% you to give you an idea about how it works<00:12:14.640> so<00:12:15.640> what<00:12:15.790> is<00:12:15.910> it<00:12:16.029> if<00:12:16.180> we<00:12:16.270> push<00:12:16.510> fill<00:12:16.750> so 00:12:16.949 --> 00:12:16.959 align:start position:0% works so what is it if we push fill so 00:12:16.959 --> 00:12:18.690 align:start position:0% works so what is it if we push fill so it<00:12:17.080> provides<00:12:17.410> the<00:12:17.529> token<00:12:17.860> address<00:12:18.130> which<00:12:18.670> is 00:12:18.690 --> 00:12:18.700 align:start position:0% it provides the token address which is 00:12:18.700 --> 00:12:21.060 align:start position:0% it provides the token address which is the<00:12:18.910> ERC<00:12:19.209> 20<00:12:19.660> token<00:12:19.990> it<00:12:20.080> you<00:12:20.200> support<00:12:20.650> or<00:12:21.010> you 00:12:21.060 --> 00:12:21.070 align:start position:0% the ERC 20 token it you support or you 00:12:21.070 --> 00:12:23.519 align:start position:0% the ERC 20 token it you support or you want<00:12:21.250> to<00:12:21.339> exchange<00:12:21.580> it<00:12:22.060> gives<00:12:22.779> you<00:12:22.870> a<00:12:22.900> validity 00:12:23.519 --> 00:12:23.529 align:start position:0% want to exchange it gives you a validity 00:12:23.529 --> 00:12:25.230 align:start position:0% want to exchange it gives you a validity date<00:12:23.950> which<00:12:24.190> is<00:12:24.339> expressed<00:12:24.850> in<00:12:24.970> a<00:12:25.029> block 00:12:25.230 --> 00:12:25.240 align:start position:0% date which is expressed in a block 00:12:25.240 --> 00:12:28.590 align:start position:0% date which is expressed in a block number<00:12:25.600> so<00:12:25.839> this<00:12:26.320> sort<00:12:26.800> of<00:12:26.860> personal<00:12:27.600> exchange 00:12:28.590 --> 00:12:28.600 align:start position:0% number so this sort of personal exchange 00:12:28.600 --> 00:12:32.100 align:start position:0% number so this sort of personal exchange rate<00:12:28.959> is<00:12:29.110> valid<00:12:29.470> as<00:12:29.950> a<00:12:30.010> validity<00:12:30.490> period<00:12:31.110> we 00:12:32.100 --> 00:12:32.110 align:start position:0% rate is valid as a validity period we 00:12:32.110 --> 00:12:33.900 align:start position:0% rate is valid as a validity period we had<00:12:32.230> a<00:12:32.260> random<00:12:32.650> number<00:12:32.980> to<00:12:33.520> create<00:12:33.760> some 00:12:33.900 --> 00:12:33.910 align:start position:0% had a random number to create some 00:12:33.910 --> 00:12:37.110 align:start position:0% had a random number to create some entropy<00:12:34.390> on<00:12:34.600> the<00:12:35.430> but<00:12:36.430> that<00:12:36.700> will<00:12:36.910> come<00:12:37.089> later 00:12:37.110 --> 00:12:37.120 align:start position:0% entropy on the but that will come later 00:12:37.120 --> 00:12:39.630 align:start position:0% entropy on the but that will come later also<00:12:37.510> you<00:12:38.350> will<00:12:38.470> say<00:12:38.740> how<00:12:38.980> many<00:12:39.190> of<00:12:39.490> these 00:12:39.630 --> 00:12:39.640 align:start position:0% also you will say how many of these 00:12:39.640 --> 00:12:42.720 align:start position:0% also you will say how many of these forms<00:12:39.940> the<00:12:40.209> focus<00:12:40.779> you<00:12:40.870> can<00:12:41.080> take<00:12:41.500> from<00:12:41.830> him<00:12:42.010> in 00:12:42.720 --> 00:12:42.730 align:start position:0% forms the focus you can take from him in 00:12:42.730 --> 00:12:45.390 align:start position:0% forms the focus you can take from him in exchange<00:12:43.180> for<00:12:43.240> how<00:12:43.510> many<00:12:43.570> way<00:12:44.410> in<00:12:44.830> eater<00:12:45.160> you 00:12:45.390 --> 00:12:45.400 align:start position:0% exchange for how many way in eater you 00:12:45.400 --> 00:12:47.850 align:start position:0% exchange for how many way in eater you will<00:12:45.520> give<00:12:45.760> them<00:12:45.940> they<00:12:46.930> also<00:12:47.110> provides<00:12:47.589> the 00:12:47.850 --> 00:12:47.860 align:start position:0% will give them they also provides the 00:12:47.860 --> 00:12:49.680 align:start position:0% will give them they also provides the gas<00:12:48.070> tank<00:12:48.339> client<00:12:48.730> which<00:12:48.880> is<00:12:48.910> the<00:12:49.029> address<00:12:49.450> of 00:12:49.680 --> 00:12:49.690 align:start position:0% gas tank client which is the address of 00:12:49.690 --> 00:12:51.360 align:start position:0% gas tank client which is the address of the<00:12:49.810> taps<00:12:50.110> the<00:12:50.380> wallet<00:12:50.620> address<00:12:50.890> from<00:12:51.010> the<00:12:51.190> tap 00:12:51.360 --> 00:12:51.370 align:start position:0% the taps the wallet address from the tap 00:12:51.370 --> 00:12:55.740 align:start position:0% the taps the wallet address from the tap and<00:12:51.610> then<00:12:52.300> the<00:12:52.690> signature<00:12:54.270> so<00:12:55.270> the<00:12:55.390> thing<00:12:55.570> that 00:12:55.740 --> 00:12:55.750 align:start position:0% and then the signature so the thing that 00:12:55.750 --> 00:12:57.960 align:start position:0% and then the signature so the thing that the<00:12:55.930> contract<00:12:56.320> will<00:12:56.470> do<00:12:56.680> it<00:12:57.370> will<00:12:57.550> actually 00:12:57.960 --> 00:12:57.970 align:start position:0% the contract will do it will actually 00:12:57.970 --> 00:13:00.449 align:start position:0% the contract will do it will actually recreate<00:12:58.540> that<00:12:59.020> same<00:12:59.290> hash<00:12:59.620> with<00:13:00.160> all<00:13:00.279> these 00:13:00.449 --> 00:13:00.459 align:start position:0% recreate that same hash with all these 00:13:00.459 --> 00:13:04.230 align:start position:0% recreate that same hash with all these parameters<00:13:01.120> and<00:13:01.890> here<00:13:02.890> he<00:13:03.100> will<00:13:03.220> verify<00:13:03.520> if 00:13:04.230 --> 00:13:04.240 align:start position:0% parameters and here he will verify if 00:13:04.240 --> 00:13:07.050 align:start position:0% parameters and here he will verify if the<00:13:04.600> signature<00:13:05.200> of<00:13:05.380> all<00:13:06.190> these<00:13:06.430> parameters 00:13:07.050 --> 00:13:07.060 align:start position:0% the signature of all these parameters 00:13:07.060 --> 00:13:09.600 align:start position:0% the signature of all these parameters are<00:13:07.300> actually<00:13:07.839> match<00:13:08.620> up<00:13:08.650> to<00:13:08.950> the<00:13:09.070> address<00:13:09.400> of 00:13:09.600 --> 00:13:09.610 align:start position:0% are actually match up to the address of 00:13:09.610 --> 00:13:13.019 align:start position:0% are actually match up to the address of the<00:13:09.760> gas<00:13:09.940> tank<00:13:10.180> lines<00:13:10.450> if<00:13:11.110> so<00:13:11.560> he<00:13:12.040> does<00:13:12.880> the 00:13:13.019 --> 00:13:13.029 align:start position:0% the gas tank lines if so he does the 00:13:13.029 --> 00:13:14.550 align:start position:0% the gas tank lines if so he does the actual<00:13:13.330> exchange<00:13:13.540> so<00:13:13.810> the<00:13:13.900> code<00:13:14.050> is<00:13:14.170> not<00:13:14.200> here 00:13:14.550 --> 00:13:14.560 align:start position:0% actual exchange so the code is not here 00:13:14.560 --> 00:13:19.290 align:start position:0% actual exchange so the code is not here and<00:13:15.520> he<00:13:15.640> will<00:13:15.760> mark<00:13:16.390> that<00:13:16.990> specific<00:13:18.120> would<00:13:19.120> say 00:13:19.290 --> 00:13:19.300 align:start position:0% and he will mark that specific would say 00:13:19.300 --> 00:13:20.380 align:start position:0% and he will mark that specific would say contracts<00:13:19.990> or<00:13:20.170> that 00:13:20.380 --> 00:13:20.390 align:start position:0% contracts or that 00:13:20.390 --> 00:13:22.930 align:start position:0% contracts or that specific<00:13:20.900> configuration<00:13:21.620> to<00:13:22.160> be<00:13:22.280> executed<00:13:22.820> so 00:13:22.930 --> 00:13:22.940 align:start position:0% specific configuration to be executed so 00:13:22.940 --> 00:13:26.110 align:start position:0% specific configuration to be executed so we<00:13:23.030> can't<00:13:23.270> repeat<00:13:23.900> it<00:13:23.960> twice 00:13:26.110 --> 00:13:26.120 align:start position:0% we can't repeat it twice 00:13:26.120 --> 00:13:28.620 align:start position:0% we can't repeat it twice concerning<00:13:26.840> risk<00:13:27.170> mitigation<00:13:27.770> there's<00:13:27.950> one 00:13:28.620 --> 00:13:28.630 align:start position:0% concerning risk mitigation there's one 00:13:28.630 --> 00:13:31.330 align:start position:0% concerning risk mitigation there's one problem<00:13:29.630> because<00:13:29.990> you<00:13:30.080> have<00:13:30.110> to<00:13:30.350> trust<00:13:30.620> the 00:13:31.330 --> 00:13:31.340 align:start position:0% problem because you have to trust the 00:13:31.340 --> 00:13:33.550 align:start position:0% problem because you have to trust the gas<00:13:31.850> station<00:13:32.300> service<00:13:33.170> that<00:13:33.380> it<00:13:33.470> will 00:13:33.550 --> 00:13:33.560 align:start position:0% gas station service that it will 00:13:33.560 --> 00:13:35.140 align:start position:0% gas station service that it will actually<00:13:33.710> also<00:13:34.070> perform<00:13:34.610> the<00:13:34.790> second 00:13:35.140 --> 00:13:35.150 align:start position:0% actually also perform the second 00:13:35.150 --> 00:13:36.580 align:start position:0% actually also perform the second transaction<00:13:35.450> if<00:13:35.990> you<00:13:36.170> give<00:13:36.380> him<00:13:36.440> the 00:13:36.580 --> 00:13:36.590 align:start position:0% transaction if you give him the 00:13:36.590 --> 00:13:39.010 align:start position:0% transaction if you give him the allowance<00:13:37.450> transaction<00:13:38.450> you<00:13:38.510> must<00:13:38.660> be<00:13:38.750> sure 00:13:39.010 --> 00:13:39.020 align:start position:0% allowance transaction you must be sure 00:13:39.020 --> 00:13:42.100 align:start position:0% allowance transaction you must be sure that<00:13:39.680> he<00:13:39.770> actually<00:13:39.890> doesn't<00:13:40.960> does<00:13:41.960> that's 00:13:42.100 --> 00:13:42.110 align:start position:0% that he actually doesn't does that's 00:13:42.110 --> 00:13:45.850 align:start position:0% that he actually doesn't does that's push<00:13:42.560> filled<00:13:42.830> thing<00:13:43.070> so<00:13:43.820> to<00:13:44.300> mitigate<00:13:44.450> that<00:13:44.860> so 00:13:45.850 --> 00:13:45.860 align:start position:0% push filled thing so to mitigate that so 00:13:45.860 --> 00:13:48.010 align:start position:0% push filled thing so to mitigate that so I<00:13:45.890> told<00:13:46.190> you<00:13:46.280> before<00:13:46.700> that's<00:13:46.820> the<00:13:47.150> API<00:13:47.480> service 00:13:48.010 --> 00:13:48.020 align:start position:0% I told you before that's the API service 00:13:48.020 --> 00:13:50.500 align:start position:0% I told you before that's the API service response<00:13:48.800> with<00:13:49.010> so<00:13:49.250> many<00:13:49.370> way<00:13:49.670> because<00:13:50.480> that 00:13:50.500 --> 00:13:50.510 align:start position:0% response with so many way because that 00:13:50.510 --> 00:13:52.930 align:start position:0% response with so many way because that many<00:13:50.840> sworn<00:13:51.170> tokens<00:13:51.620> but<00:13:52.220> actually<00:13:52.580> is<00:13:52.760> also 00:13:52.930 --> 00:13:52.940 align:start position:0% many sworn tokens but actually is also 00:13:52.940 --> 00:13:55.810 align:start position:0% many sworn tokens but actually is also going<00:13:53.210> to<00:13:53.330> give<00:13:53.600> a<00:13:53.800> liquor<00:13:54.800> signature<00:13:55.430> on 00:13:55.810 --> 00:13:55.820 align:start position:0% going to give a liquor signature on 00:13:55.820 --> 00:13:59.140 align:start position:0% going to give a liquor signature on these<00:13:55.970> parameters<00:13:56.570> with<00:13:56.780> his<00:13:57.280> because<00:13:58.280> as<00:13:59.120> a 00:13:59.140 --> 00:13:59.150 align:start position:0% these parameters with his because as a 00:13:59.150 --> 00:14:01.330 align:start position:0% these parameters with his because as a wallet<00:13:59.450> obviously<00:13:59.990> and<00:14:00.830> then<00:14:00.950> we<00:14:01.010> create<00:14:01.250> the 00:14:01.330 --> 00:14:01.340 align:start position:0% wallet obviously and then we create the 00:14:01.340 --> 00:14:02.830 align:start position:0% wallet obviously and then we create the second<00:14:01.760> function<00:14:01.940> which<00:14:02.150> is<00:14:02.300> called<00:14:02.540> push 00:14:02.830 --> 00:14:02.840 align:start position:0% second function which is called push 00:14:02.840 --> 00:14:06.190 align:start position:0% second function which is called push sorry<00:14:03.350> pull<00:14:03.620> fill<00:14:04.210> and<00:14:05.210> it<00:14:05.390> will<00:14:05.540> verify<00:14:05.900> the 00:14:06.190 --> 00:14:06.200 align:start position:0% sorry pull fill and it will verify the 00:14:06.200 --> 00:14:08.410 align:start position:0% sorry pull fill and it will verify the same<00:14:06.530> parameters<00:14:07.160> which<00:14:07.700> will<00:14:07.880> actually<00:14:08.000> just 00:14:08.410 --> 00:14:08.420 align:start position:0% same parameters which will actually just 00:14:08.420 --> 00:14:11.170 align:start position:0% same parameters which will actually just verify<00:14:08.930> if<00:14:09.230> these<00:14:10.070> parameters<00:14:10.730> were<00:14:10.910> signed 00:14:11.170 --> 00:14:11.180 align:start position:0% verify if these parameters were signed 00:14:11.180 --> 00:14:13.060 align:start position:0% verify if these parameters were signed by<00:14:11.330> the<00:14:11.390> owner<00:14:11.510> and<00:14:12.020> this<00:14:12.470> function<00:14:12.860> can<00:14:13.010> be 00:14:13.060 --> 00:14:13.070 align:start position:0% by the owner and this function can be 00:14:13.070 --> 00:14:15.370 align:start position:0% by the owner and this function can be called<00:14:13.370> by<00:14:13.850> the<00:14:13.910> gas<00:14:14.180> station<00:14:14.660> served<00:14:15.200> by<00:14:15.320> the 00:14:15.370 --> 00:14:15.380 align:start position:0% called by the gas station served by the 00:14:15.380 --> 00:14:17.830 align:start position:0% called by the gas station served by the client<00:14:16.040> who<00:14:16.250> uses<00:14:16.430> the<00:14:16.640> gas<00:14:16.790> station<00:14:17.270> so<00:14:17.810> he 00:14:17.830 --> 00:14:17.840 align:start position:0% client who uses the gas station so he 00:14:17.840 --> 00:14:19.630 align:start position:0% client who uses the gas station so he has<00:14:17.990> a<00:14:18.020> certitude<00:14:18.620> that<00:14:18.650> if<00:14:19.220> they<00:14:19.400> do<00:14:19.520> the 00:14:19.630 --> 00:14:19.640 align:start position:0% has a certitude that if they do the 00:14:19.640 --> 00:14:22.090 align:start position:0% has a certitude that if they do the exchange<00:14:19.850> they<00:14:20.150> sort<00:14:20.390> of<00:14:20.420> mutually<00:14:21.050> give<00:14:21.980> the 00:14:22.090 --> 00:14:22.100 align:start position:0% exchange they sort of mutually give the 00:14:22.100 --> 00:14:23.860 align:start position:0% exchange they sort of mutually give the allowance<00:14:22.550> to<00:14:22.700> do<00:14:22.820> exactly<00:14:23.150> that's<00:14:23.450> a 00:14:23.860 --> 00:14:23.870 align:start position:0% allowance to do exactly that's a 00:14:23.870 --> 00:14:26.290 align:start position:0% allowance to do exactly that's a transaction<00:14:24.650> so<00:14:25.550> why<00:14:25.700> would<00:14:25.880> you<00:14:25.910> participate 00:14:26.290 --> 00:14:26.300 align:start position:0% transaction so why would you participate 00:14:26.300 --> 00:14:29.320 align:start position:0% transaction so why would you participate or<00:14:26.780> would<00:14:27.050> you<00:14:27.200> run<00:14:27.470> a<00:14:27.680> gas<00:14:27.890> station<00:14:28.330> because 00:14:29.320 --> 00:14:29.330 align:start position:0% or would you run a gas station because 00:14:29.330 --> 00:14:32.590 align:start position:0% or would you run a gas station because we<00:14:29.480> we<00:14:29.990> can<00:14:30.260> define<00:14:30.620> or<00:14:31.070> you<00:14:31.160> can<00:14:31.340> define<00:14:31.670> an 00:14:32.590 --> 00:14:32.600 align:start position:0% we we can define or you can define an 00:14:32.600 --> 00:14:34.420 align:start position:0% we we can define or you can define an uplift<00:14:32.990> for<00:14:33.170> the<00:14:33.200> price<00:14:33.500> you<00:14:33.770> sell<00:14:33.980> your<00:14:34.190> eater 00:14:34.420 --> 00:14:34.430 align:start position:0% uplift for the price you sell your eater 00:14:34.430 --> 00:14:36.370 align:start position:0% uplift for the price you sell your eater for<00:14:34.820> so<00:14:35.450> it<00:14:35.540> means<00:14:35.720> if<00:14:35.870> you<00:14:35.990> would<00:14:36.140> for<00:14:36.320> example 00:14:36.370 --> 00:14:36.380 align:start position:0% for so it means if you would for example 00:14:36.380 --> 00:14:39.670 align:start position:0% for so it means if you would for example say<00:14:36.830> 10%<00:14:37.130> uplift<00:14:37.970> if<00:14:38.420> your<00:14:38.750> gas<00:14:38.990> station<00:14:39.380> sells 00:14:39.670 --> 00:14:39.680 align:start position:0% say 10% uplift if your gas station sells 00:14:39.680 --> 00:14:41.920 align:start position:0% say 10% uplift if your gas station sells out<00:14:39.920> because<00:14:40.520> the<00:14:40.850> amount<00:14:41.060> feature<00:14:41.330> decreases 00:14:41.920 --> 00:14:41.930 align:start position:0% out because the amount feature decreases 00:14:41.930 --> 00:14:44.080 align:start position:0% out because the amount feature decreases the<00:14:42.050> amounts<00:14:42.320> aren't<00:14:42.530> tokens<00:14:42.920> increases<00:14:43.520> you 00:14:44.080 --> 00:14:44.090 align:start position:0% the amounts aren't tokens increases you 00:14:44.090 --> 00:14:45.760 align:start position:0% the amounts aren't tokens increases you will<00:14:44.210> end<00:14:44.390> up<00:14:44.510> with<00:14:44.720> when<00:14:45.050> you<00:14:45.140> sell<00:14:45.380> over<00:14:45.680> your 00:14:45.760 --> 00:14:45.770 align:start position:0% will end up with when you sell over your 00:14:45.770 --> 00:14:48.010 align:start position:0% will end up with when you sell over your eater<00:14:46.030> with<00:14:47.030> an<00:14:47.120> amount<00:14:47.360> of<00:14:47.510> swarm<00:14:47.750> city 00:14:48.010 --> 00:14:48.020 align:start position:0% eater with an amount of swarm city 00:14:48.020 --> 00:14:50.290 align:start position:0% eater with an amount of swarm city tokens<00:14:48.470> which<00:14:48.680> equals<00:14:49.370> like<00:14:49.520> one<00:14:49.760> point<00:14:50.030> one 00:14:50.290 --> 00:14:50.300 align:start position:0% tokens which equals like one point one 00:14:50.300 --> 00:14:56.950 align:start position:0% tokens which equals like one point one eater<00:14:53.050> so<00:14:54.130> yeah<00:14:55.130> so<00:14:55.940> the<00:14:56.060> result<00:14:56.360> of<00:14:56.510> that<00:14:56.660> is 00:14:56.950 --> 00:14:56.960 align:start position:0% eater so yeah so the result of that is 00:14:56.960 --> 00:14:59.320 align:start position:0% eater so yeah so the result of that is that<00:14:56.990> anybody<00:14:57.500> can<00:14:58.160> just<00:14:58.400> download<00:14:58.640> that<00:14:59.000> API 00:14:59.320 --> 00:14:59.330 align:start position:0% that anybody can just download that API 00:14:59.330 --> 00:15:03.100 align:start position:0% that anybody can just download that API script<00:14:59.690> deploy<00:15:00.200> its<00:15:00.560> own<00:15:01.240> contract<00:15:02.240> primates 00:15:03.100 --> 00:15:03.110 align:start position:0% script deploy its own contract primates 00:15:03.110 --> 00:15:05.620 align:start position:0% script deploy its own contract primates we<00:15:03.260> call<00:15:03.440> it<00:15:03.590> with<00:15:03.770> eater<00:15:04.070> then<00:15:04.940> configure<00:15:05.360> it 00:15:05.620 --> 00:15:05.630 align:start position:0% we call it with eater then configure it 00:15:05.630 --> 00:15:09.640 align:start position:0% we call it with eater then configure it like<00:15:05.990> what<00:15:06.710> ERC<00:15:07.700> 22<00:15:08.360> do<00:15:08.750> you<00:15:08.900> want<00:15:09.140> to<00:15:09.260> accept 00:15:09.640 --> 00:15:09.650 align:start position:0% like what ERC 22 do you want to accept 00:15:09.650 --> 00:15:12.280 align:start position:0% like what ERC 22 do you want to accept in<00:15:09.920> your<00:15:09.980> gas<00:15:10.460> station<00:15:10.670> then<00:15:11.630> tell<00:15:11.870> it<00:15:12.020> how 00:15:12.280 --> 00:15:12.290 align:start position:0% in your gas station then tell it how 00:15:12.290 --> 00:15:14.260 align:start position:0% in your gas station then tell it how much<00:15:12.470> either<00:15:13.160> markup<00:15:13.700> you<00:15:13.790> want<00:15:13.940> to<00:15:14.030> sell<00:15:14.150> it 00:15:14.260 --> 00:15:14.270 align:start position:0% much either markup you want to sell it 00:15:14.270 --> 00:15:17.920 align:start position:0% much either markup you want to sell it for<00:15:14.420> and<00:15:14.690> just<00:15:15.020> start<00:15:15.350> it<00:15:16.420> you<00:15:17.420> can<00:15:17.630> find 00:15:17.920 --> 00:15:17.930 align:start position:0% for and just start it you can find 00:15:17.930 --> 00:15:22.560 align:start position:0% for and just start it you can find everything<00:15:18.560> we<00:15:19.010> are<00:15:19.400> doing<00:15:20.470> these<00:15:21.470> get<00:15:22.130> up 00:15:22.560 --> 00:15:22.570 align:start position:0% everything we are doing these get up 00:15:22.570 --> 00:15:25.330 align:start position:0% everything we are doing these get up links<00:15:23.570> and<00:15:23.810> also<00:15:24.140> on<00:15:24.260> this<00:15:24.410> is<00:15:24.590> dots<00:15:24.800> farm<00:15:25.070> City 00:15:25.330 --> 00:15:25.340 align:start position:0% links and also on this is dots farm City 00:15:25.340 --> 00:15:29.560 align:start position:0% links and also on this is dots farm City you<00:15:26.270> will<00:15:26.300> find<00:15:27.250> more<00:15:28.250> information 00:15:29.560 --> 00:15:29.570 align:start position:0% you will find more information 00:15:29.570 --> 00:15:31.600 align:start position:0% you will find more information there's<00:15:30.110> of<00:15:30.350> course<00:15:30.380> one<00:15:30.860> more<00:15:31.100> thing<00:15:31.339> the 00:15:31.600 --> 00:15:31.610 align:start position:0% there's of course one more thing the 00:15:31.610 --> 00:15:36.249 align:start position:0% there's of course one more thing the time<00:15:31.790> you<00:15:31.940> created<00:15:33.970> so<00:15:34.970> as<00:15:35.269> you<00:15:35.720> see<00:15:35.930> the<00:15:36.079> gas 00:15:36.249 --> 00:15:36.259 align:start position:0% time you created so as you see the gas 00:15:36.259 --> 00:15:38.590 align:start position:0% time you created so as you see the gas station<00:15:36.740> it's<00:15:37.190> at<00:15:37.519> a<00:15:37.579> certain<00:15:37.759> time<00:15:38.120> it<00:15:38.360> needs 00:15:38.590 --> 00:15:38.600 align:start position:0% station it's at a certain time it needs 00:15:38.600 --> 00:15:39.790 align:start position:0% station it's at a certain time it needs some<00:15:38.750> maintenance<00:15:38.930> because<00:15:39.410> it's<00:15:39.560> needs<00:15:39.709> to 00:15:39.790 --> 00:15:39.800 align:start position:0% some maintenance because it's needs to 00:15:39.800 --> 00:15:42.430 align:start position:0% some maintenance because it's needs to be<00:15:39.920> refilled<00:15:40.399> because<00:15:40.970> like<00:15:41.180> the<00:15:41.329> eater<00:15:41.660> gets 00:15:42.430 --> 00:15:42.440 align:start position:0% be refilled because like the eater gets 00:15:42.440 --> 00:15:44.980 align:start position:0% be refilled because like the eater gets depleted<00:15:42.740> in<00:15:43.040> the<00:15:43.070> ends<00:15:43.370> which<00:15:44.360> also<00:15:44.660> try<00:15:44.930> to 00:15:44.980 --> 00:15:44.990 align:start position:0% depleted in the ends which also try to 00:15:44.990 --> 00:15:46.540 align:start position:0% depleted in the ends which also try to solve<00:15:45.320> that<00:15:45.500> and<00:15:45.680> we<00:15:45.769> have<00:15:45.889> like<00:15:46.040> prototype 00:15:46.540 --> 00:15:46.550 align:start position:0% solve that and we have like prototype 00:15:46.550 --> 00:15:48.069 align:start position:0% solve that and we have like prototype code<00:15:46.790> of<00:15:46.940> that<00:15:47.029> which<00:15:47.240> we<00:15:47.449> can<00:15:47.600> you<00:15:47.779> can<00:15:47.930> also 00:15:48.069 --> 00:15:48.079 align:start position:0% code of that which we can you can also 00:15:48.079 --> 00:15:50.920 align:start position:0% code of that which we can you can also find<00:15:48.410> an<00:15:48.709> archetype<00:15:49.300> so<00:15:50.300> we<00:15:50.449> created<00:15:50.779> an 00:15:50.920 --> 00:15:50.930 align:start position:0% find an archetype so we created an 00:15:50.930 --> 00:15:53.019 align:start position:0% find an archetype so we created an integration<00:15:51.470> with<00:15:51.500> eater<00:15:51.829> Delta<00:15:52.310> so<00:15:52.910> the 00:15:53.019 --> 00:15:53.029 align:start position:0% integration with eater Delta so the 00:15:53.029 --> 00:15:54.610 align:start position:0% integration with eater Delta so the thing<00:15:53.209> is<00:15:53.240> that<00:15:53.360> the<00:15:53.690> gas<00:15:53.870> station<00:15:54.230> serve<00:15:54.470> it 00:15:54.610 --> 00:15:54.620 align:start position:0% thing is that the gas station serve it 00:15:54.620 --> 00:15:57.579 align:start position:0% thing is that the gas station serve it itself<00:15:55.009> it<00:15:55.459> contains<00:15:55.910> a<00:15:56.029> wallet<00:15:56.360> so<00:15:57.079> when<00:15:57.470> it's 00:15:57.579 --> 00:15:57.589 align:start position:0% itself it contains a wallet so when it's 00:15:57.589 --> 00:15:59.559 align:start position:0% itself it contains a wallet so when it's it<00:15:58.160> has<00:15:58.190> a<00:15:58.339> certain<00:15:58.610> amount<00:15:58.730> of<00:15:59.029> swarm<00:15:59.329> city 00:15:59.559 --> 00:15:59.569 align:start position:0% it has a certain amount of swarm city 00:15:59.569 --> 00:16:01.569 align:start position:0% it has a certain amount of swarm city tokens<00:16:00.079> it's<00:16:00.230> almost<00:16:00.470> depleted<00:16:00.860> of<00:16:01.130> eater 00:16:01.569 --> 00:16:01.579 align:start position:0% tokens it's almost depleted of eater 00:16:01.579 --> 00:16:04.030 align:start position:0% tokens it's almost depleted of eater the<00:16:02.540> gas<00:16:02.690> station<00:16:03.050> service<00:16:03.440> can<00:16:03.649> actually 00:16:04.030 --> 00:16:04.040 align:start position:0% the gas station service can actually 00:16:04.040 --> 00:16:06.519 align:start position:0% the gas station service can actually look<00:16:04.610> into<00:16:04.850> the<00:16:04.970> eater<00:16:05.120> Delta<00:16:05.690> and<00:16:06.259> try<00:16:06.470> to 00:16:06.519 --> 00:16:06.529 align:start position:0% look into the eater Delta and try to 00:16:06.529 --> 00:16:09.370 align:start position:0% look into the eater Delta and try to find<00:16:06.860> by<00:16:07.160> order<00:16:07.579> for<00:16:07.790> swarm<00:16:08.000> city<00:16:08.300> tokens<00:16:08.779> for 00:16:09.370 --> 00:16:09.380 align:start position:0% find by order for swarm city tokens for 00:16:09.380 --> 00:16:12.910 align:start position:0% find by order for swarm city tokens for eater<00:16:10.329> so<00:16:11.329> when<00:16:11.480> it<00:16:11.600> finds<00:16:11.839> one<00:16:12.139> you<00:16:12.769> will 00:16:12.910 --> 00:16:12.920 align:start position:0% eater so when it finds one you will 00:16:12.920 --> 00:16:14.499 align:start position:0% eater so when it finds one you will actually<00:16:13.069> purchase<00:16:13.759> it<00:16:13.880> because<00:16:14.029> it's<00:16:14.300> like 00:16:14.499 --> 00:16:14.509 align:start position:0% actually purchase it because it's like 00:16:14.509 --> 00:16:16.350 align:start position:0% actually purchase it because it's like anonymous<00:16:15.079> I<00:16:15.199> mean<00:16:15.319> you<00:16:15.380> do<00:16:15.500> need<00:16:15.709> an<00:16:15.800> Accounts 00:16:16.350 --> 00:16:16.360 align:start position:0% anonymous I mean you do need an Accounts 00:16:16.360 --> 00:16:19.780 align:start position:0% anonymous I mean you do need an Accounts or<00:16:17.360> registration<00:16:18.050> or<00:16:18.139> whatsoever<00:16:18.490> so<00:16:19.490> we<00:16:19.579> just 00:16:19.780 --> 00:16:19.790 align:start position:0% or registration or whatsoever so we just 00:16:19.790 --> 00:16:21.100 align:start position:0% or registration or whatsoever so we just created<00:16:20.149> like<00:16:20.480> a<00:16:20.509> machine-to-machine 00:16:21.100 --> 00:16:21.110 align:start position:0% created like a machine-to-machine 00:16:21.110 --> 00:16:25.360 align:start position:0% created like a machine-to-machine trading<00:16:21.949> that<00:16:22.490> actually<00:16:22.910> binds<00:16:23.829> eater<00:16:24.829> in 00:16:25.360 --> 00:16:25.370 align:start position:0% trading that actually binds eater in 00:16:25.370 --> 00:16:27.939 align:start position:0% trading that actually binds eater in exchange<00:16:25.880> for<00:16:26.209> its<00:16:26.540> worm<00:16:26.779> tokens<00:16:27.110> so<00:16:27.860> the 00:16:27.939 --> 00:16:27.949 align:start position:0% exchange for its worm tokens so the 00:16:27.949 --> 00:16:30.370 align:start position:0% exchange for its worm tokens so the thing<00:16:28.130> is<00:16:28.220> you<00:16:28.310> can<00:16:28.459> actually<00:16:28.899> refill<00:16:29.899> or 00:16:30.370 --> 00:16:30.380 align:start position:0% thing is you can actually refill or 00:16:30.380 --> 00:16:32.530 align:start position:0% thing is you can actually refill or automatically<00:16:30.980> refill<00:16:31.850> your<00:16:32.000> gas<00:16:32.269> station 00:16:32.530 --> 00:16:32.540 align:start position:0% automatically refill your gas station 00:16:32.540 --> 00:16:35.139 align:start position:0% automatically refill your gas station with<00:16:33.290> easier<00:16:33.620> to<00:16:33.769> start<00:16:34.010> again 00:16:35.139 --> 00:16:35.149 align:start position:0% with easier to start again 00:16:35.149 --> 00:16:38.470 align:start position:0% with easier to start again and<00:16:35.449> closing<00:16:36.319> that<00:16:36.500> loop<00:16:36.769> and<00:16:37.760> so<00:16:38.029> this<00:16:38.180> can<00:16:38.360> be 00:16:38.470 --> 00:16:38.480 align:start position:0% and closing that loop and so this can be 00:16:38.480 --> 00:16:39.879 align:start position:0% and closing that loop and so this can be fully<00:16:38.750> automated<00:16:38.899> so<00:16:39.380> you<00:16:39.470> don't<00:16:39.740> actually 00:16:39.879 --> 00:16:39.889 align:start position:0% fully automated so you don't actually 00:16:39.889 --> 00:16:42.519 align:start position:0% fully automated so you don't actually need<00:16:40.100> to<00:16:40.190> manage<00:16:40.610> the<00:16:41.449> gas<00:16:41.630> station<00:16:41.990> anymore 00:16:42.519 --> 00:16:42.529 align:start position:0% need to manage the gas station anymore 00:16:42.529 --> 00:16:45.040 align:start position:0% need to manage the gas station anymore you<00:16:42.829> just<00:16:42.889> can<00:16:43.220> have<00:16:43.370> it<00:16:43.490> run<00:16:43.779> when<00:16:44.779> it<00:16:44.899> does 00:16:45.040 --> 00:16:45.050 align:start position:0% you just can have it run when it does 00:16:45.050 --> 00:16:46.569 align:start position:0% you just can have it run when it does the<00:16:45.170> exchange<00:16:45.560> you<00:16:45.709> will<00:16:45.740> actually<00:16:46.220> end<00:16:46.430> up 00:16:46.569 --> 00:16:46.579 align:start position:0% the exchange you will actually end up 00:16:46.579 --> 00:16:48.790 align:start position:0% the exchange you will actually end up with<00:16:47.269> more<00:16:47.510> eater<00:16:47.810> than<00:16:48.050> you<00:16:48.170> started<00:16:48.589> to<00:16:48.709> it 00:16:48.790 --> 00:16:48.800 align:start position:0% with more eater than you started to it 00:16:48.800 --> 00:16:50.620 align:start position:0% with more eater than you started to it so<00:16:49.010> you<00:16:49.699> will<00:16:49.850> end<00:16:49.880> up<00:16:50.149> in<00:16:50.300> this<00:16:50.389> situation 00:16:50.620 --> 00:16:50.630 align:start position:0% so you will end up in this situation 00:16:50.630 --> 00:16:53.590 align:start position:0% so you will end up in this situation with<00:16:51.139> like<00:16:51.290> one<00:16:51.829> point<00:16:52.100> one<00:16:52.339> eater<00:16:52.610> instead<00:16:53.510> of 00:16:53.590 --> 00:16:53.600 align:start position:0% with like one point one eater instead of 00:16:53.600 --> 00:16:56.769 align:start position:0% with like one point one eater instead of one<00:16:53.810> eater<00:16:54.130> so<00:16:55.130> yeah<00:16:55.370> we<00:16:55.790> thought<00:16:56.510> it<00:16:56.569> was 00:16:56.769 --> 00:16:56.779 align:start position:0% one eater so yeah we thought it was 00:16:56.779 --> 00:16:58.389 align:start position:0% one eater so yeah we thought it was appropriate<00:16:56.959> to<00:16:57.470> call<00:16:57.649> that<00:16:57.860> the<00:16:58.069> gift<00:16:58.279> that 00:16:58.389 --> 00:16:58.399 align:start position:0% appropriate to call that the gift that 00:16:58.399 --> 00:17:00.120 align:start position:0% appropriate to call that the gift that keeps<00:16:58.760> on<00:16:58.940> giving 00:17:00.120 --> 00:17:00.130 align:start position:0% keeps on giving 00:17:00.130 --> 00:17:09.020 align:start position:0% keeps on giving so<00:17:01.130> basically<00:17:01.639> that<00:17:02.029> is<00:17:02.180> thank<00:17:02.870> you 00:17:09.020 --> 00:17:09.030 align:start position:0% 00:17:09.030 --> 00:17:16.609 align:start position:0% [Music]