WEBVTT Kind: captions Language: en 00:00:00.120 --> 00:00:13.810 align:start position:0% [Music] 00:00:13.810 --> 00:00:13.820 align:start position:0% 00:00:13.820 --> 00:00:17.910 align:start position:0% [Music] 00:00:17.910 --> 00:00:17.920 align:start position:0% 00:00:17.920 --> 00:00:20.230 align:start position:0% leus 00:00:20.230 --> 00:00:20.240 align:start position:0% leus 00:00:20.240 --> 00:00:23.189 align:start position:0% leus carpetas<00:00:21.240> he'll<00:00:21.480> be<00:00:21.640> speaking<00:00:21.960> on<00:00:22.199> soraa 00:00:23.189 --> 00:00:23.199 align:start position:0% carpetas he'll be speaking on soraa 00:00:23.199 --> 00:00:28.950 align:start position:0% carpetas he'll be speaking on soraa ethereum<00:00:23.760> meets<00:00:24.320> the 00:00:28.950 --> 00:00:28.960 align:start position:0% 00:00:28.960 --> 00:00:34.389 align:start position:0% outdoors 00:00:34.389 --> 00:00:34.399 align:start position:0% 00:00:34.399 --> 00:00:37.709 align:start position:0% hello 00:00:37.709 --> 00:00:37.719 align:start position:0% 00:00:37.719 --> 00:00:41.869 align:start position:0% uh<00:00:38.719> yeah<00:00:39.079> waiting<00:00:39.320> for<00:00:39.440> the 00:00:41.869 --> 00:00:41.879 align:start position:0% 00:00:41.879 --> 00:00:44.950 align:start position:0% slides<00:00:42.879> great<00:00:43.280> so<00:00:44.079> uh<00:00:44.200> my<00:00:44.320> name<00:00:44.440> is<00:00:44.600> leis 00:00:44.950 --> 00:00:44.960 align:start position:0% slides great so uh my name is leis 00:00:44.960 --> 00:00:47.389 align:start position:0% slides great so uh my name is leis caretas<00:00:45.680> I<00:00:45.800> will<00:00:46.039> be<00:00:46.199> talking<00:00:46.480> to<00:00:46.640> you<00:00:46.840> about 00:00:47.389 --> 00:00:47.399 align:start position:0% caretas I will be talking to you about 00:00:47.399 --> 00:00:49.990 align:start position:0% caretas I will be talking to you about um<00:00:47.719> a<00:00:47.879> pet<00:00:48.120> project<00:00:48.360> of<00:00:48.520> mine<00:00:48.719> called<00:00:49.000> sorka 00:00:49.990 --> 00:00:50.000 align:start position:0% um a pet project of mine called sorka 00:00:50.000 --> 00:00:52.189 align:start position:0% um a pet project of mine called sorka where<00:00:50.280> ethereum<00:00:50.920> meets<00:00:51.199> the 00:00:52.189 --> 00:00:52.199 align:start position:0% where ethereum meets the 00:00:52.199 --> 00:00:54.790 align:start position:0% where ethereum meets the outdoors 00:00:54.790 --> 00:00:54.800 align:start position:0% outdoors 00:00:54.800 --> 00:00:58.189 align:start position:0% outdoors um<00:00:55.800> first<00:00:56.039> I<00:00:56.160> think<00:00:56.320> a<00:00:56.480> few<00:00:56.680> things<00:00:56.920> about<00:00:57.199> me 00:00:58.189 --> 00:00:58.199 align:start position:0% um first I think a few things about me 00:00:58.199 --> 00:00:59.509 align:start position:0% um first I think a few things about me uh<00:00:58.440> I<00:00:58.559> have<00:00:58.680> been<00:00:58.800> an<00:00:58.960> ethereum<00:00:59.280> core 00:00:59.509 --> 00:00:59.519 align:start position:0% uh I have been an ethereum core 00:00:59.519 --> 00:01:01.990 align:start position:0% uh I have been an ethereum core developer<00:01:00.000> since<00:01:00.199> 2014<00:01:01.160> I've<00:01:01.359> mostly<00:01:01.680> worked 00:01:01.990 --> 00:01:02.000 align:start position:0% developer since 2014 I've mostly worked 00:01:02.000 --> 00:01:04.469 align:start position:0% developer since 2014 I've mostly worked in<00:01:02.120> the<00:01:02.280> C++<00:01:02.920> core<00:01:03.160> and<00:01:03.280> the<00:01:03.399> solidity 00:01:04.469 --> 00:01:04.479 align:start position:0% in the C++ core and the solidity 00:01:04.479 --> 00:01:06.789 align:start position:0% in the C++ core and the solidity compiler<00:01:05.479> uh<00:01:05.640> more<00:01:05.880> recently<00:01:06.439> I<00:01:06.560> have 00:01:06.789 --> 00:01:06.799 align:start position:0% compiler uh more recently I have 00:01:06.799 --> 00:01:09.230 align:start position:0% compiler uh more recently I have contributed<00:01:07.320> a<00:01:07.400> lot<00:01:07.560> to<00:01:07.680> the<00:01:07.840> Dow<00:01:08.320> and<00:01:08.720> the 00:01:09.230 --> 00:01:09.240 align:start position:0% contributed a lot to the Dow and the 00:01:09.240 --> 00:01:12.310 align:start position:0% contributed a lot to the Dow and the aftermath<00:01:09.720> and<00:01:09.840> the<00:01:09.920> cleanup<00:01:10.439> after<00:01:11.200> um<00:01:11.640> the 00:01:12.310 --> 00:01:12.320 align:start position:0% aftermath and the cleanup after um the 00:01:12.320 --> 00:01:15.030 align:start position:0% aftermath and the cleanup after um the haug<00:01:13.320> um<00:01:13.799> my<00:01:13.960> general<00:01:14.240> interest<00:01:14.560> is<00:01:14.680> in 00:01:15.030 --> 00:01:15.040 align:start position:0% haug um my general interest is in 00:01:15.040 --> 00:01:17.510 align:start position:0% haug um my general interest is in compiler<00:01:15.520> design<00:01:16.000> AI<00:01:16.360> smart<00:01:16.680> contracts<00:01:17.159> and 00:01:17.510 --> 00:01:17.520 align:start position:0% compiler design AI smart contracts and 00:01:17.520 --> 00:01:20.590 align:start position:0% compiler design AI smart contracts and general<00:01:18.040> tinkering<00:01:18.680> with<00:01:19.040> uh 00:01:20.590 --> 00:01:20.600 align:start position:0% general tinkering with uh 00:01:20.600 --> 00:01:23.830 align:start position:0% general tinkering with uh software<00:01:21.600> uh<00:01:21.759> so<00:01:22.360> what<00:01:22.479> is<00:01:22.640> sorka<00:01:23.479> in<00:01:23.640> the 00:01:23.830 --> 00:01:23.840 align:start position:0% software uh so what is sorka in the 00:01:23.840 --> 00:01:26.109 align:start position:0% software uh so what is sorka in the Polish<00:01:24.159> language<00:01:24.759> it<00:01:24.880> is<00:01:25.320> uh<00:01:25.479> this<00:01:25.680> particular 00:01:26.109 --> 00:01:26.119 align:start position:0% Polish language it is uh this particular 00:01:26.119 --> 00:01:27.870 align:start position:0% Polish language it is uh this particular bird<00:01:26.880> I<00:01:26.960> think<00:01:27.079> in<00:01:27.200> English<00:01:27.479> it's<00:01:27.600> called<00:01:27.799> the 00:01:27.870 --> 00:01:27.880 align:start position:0% bird I think in English it's called the 00:01:27.880 --> 00:01:30.469 align:start position:0% bird I think in English it's called the Blue<00:01:28.119> tit<00:01:28.680> bird<00:01:29.680> um<00:01:30.000> and<00:01:30.119> that's<00:01:30.240> where<00:01:30.360> the 00:01:30.469 --> 00:01:30.479 align:start position:0% Blue tit bird um and that's where the 00:01:30.479 --> 00:01:31.910 align:start position:0% Blue tit bird um and that's where the name<00:01:30.680> comes 00:01:31.910 --> 00:01:31.920 align:start position:0% name comes 00:01:31.920 --> 00:01:35.830 align:start position:0% name comes from<00:01:32.920> um<00:01:33.600> for<00:01:33.840> ethereum<00:01:34.240> sorka<00:01:34.880> is<00:01:35.200> a<00:01:35.399> system 00:01:35.830 --> 00:01:35.840 align:start position:0% from um for ethereum sorka is a system 00:01:35.840 --> 00:01:37.469 align:start position:0% from um for ethereum sorka is a system that<00:01:36.159> facilitates<00:01:36.759> deploying<00:01:37.200> smart 00:01:37.469 --> 00:01:37.479 align:start position:0% that facilitates deploying smart 00:01:37.479 --> 00:01:39.950 align:start position:0% that facilitates deploying smart contracts<00:01:37.920> in<00:01:38.079> Real<00:01:38.280> World<00:01:38.960> locations 00:01:39.950 --> 00:01:39.960 align:start position:0% contracts in Real World locations 00:01:39.960 --> 00:01:43.069 align:start position:0% contracts in Real World locations essentially<00:01:40.799> it<00:01:41.000> allows<00:01:41.360> people<00:01:41.960> to<00:01:42.960> uh 00:01:43.069 --> 00:01:43.079 align:start position:0% essentially it allows people to uh 00:01:43.079 --> 00:01:45.389 align:start position:0% essentially it allows people to uh interact<00:01:43.520> with<00:01:43.840> contracts<00:01:44.840> in<00:01:45.000> physical 00:01:45.389 --> 00:01:45.399 align:start position:0% interact with contracts in physical 00:01:45.399 --> 00:01:48.990 align:start position:0% interact with contracts in physical locations<00:01:46.399> and<00:01:46.560> it<00:01:47.320> uh<00:01:47.479> does<00:01:47.759> so<00:01:48.159> by<00:01:48.399> providing 00:01:48.990 --> 00:01:49.000 align:start position:0% locations and it uh does so by providing 00:01:49.000 --> 00:01:51.630 align:start position:0% locations and it uh does so by providing something<00:01:49.680> uh<00:01:49.840> I<00:01:49.960> call<00:01:50.280> the<00:01:50.920> proof<00:01:51.200> of 00:01:51.630 --> 00:01:51.640 align:start position:0% something uh I call the proof of 00:01:51.640 --> 00:01:53.069 align:start position:0% something uh I call the proof of presence<00:01:52.000> you<00:01:52.119> know<00:01:52.320> like<00:01:52.479> we<00:01:52.640> really<00:01:52.840> like 00:01:53.069 --> 00:01:53.079 align:start position:0% presence you know like we really like 00:01:53.079 --> 00:01:56.109 align:start position:0% presence you know like we really like proofs<00:01:53.520> in<00:01:53.799> uh<00:01:54.159> in<00:01:54.719> blockchain<00:01:55.719> uh<00:01:55.799> so<00:01:55.960> that 00:01:56.109 --> 00:01:56.119 align:start position:0% proofs in uh in blockchain uh so that 00:01:56.119 --> 00:01:59.069 align:start position:0% proofs in uh in blockchain uh so that the<00:01:56.240> user<00:01:56.520> can<00:01:57.079> uh<00:01:57.360> prove<00:01:58.039> indeed<00:01:58.439> that<00:01:58.600> he's 00:01:59.069 --> 00:01:59.079 align:start position:0% the user can uh prove indeed that he's 00:01:59.079 --> 00:02:01.429 align:start position:0% the user can uh prove indeed that he's uh<00:01:59.439> present<00:01:59.920> in<00:01:59.960> a<00:02:00.079> physical 00:02:01.429 --> 00:02:01.439 align:start position:0% uh present in a physical 00:02:01.439 --> 00:02:03.670 align:start position:0% uh present in a physical location<00:02:02.439> potential<00:02:02.920> applications<00:02:03.360> of<00:02:03.520> such 00:02:03.670 --> 00:02:03.680 align:start position:0% location potential applications of such 00:02:03.680 --> 00:02:06.709 align:start position:0% location potential applications of such a<00:02:03.799> system<00:02:04.159> are<00:02:04.560> many<00:02:05.560> uh<00:02:05.719> for<00:02:05.920> example<00:02:06.479> uh 00:02:06.709 --> 00:02:06.719 align:start position:0% a system are many uh for example uh 00:02:06.719 --> 00:02:08.790 align:start position:0% a system are many uh for example uh loyalty<00:02:07.240> programs<00:02:07.880> that<00:02:08.000> would<00:02:08.319> provide<00:02:08.599> a 00:02:08.790 --> 00:02:08.800 align:start position:0% loyalty programs that would provide a 00:02:08.800 --> 00:02:10.910 align:start position:0% loyalty programs that would provide a discount<00:02:09.360> to<00:02:09.599> users<00:02:10.039> that<00:02:10.200> visit<00:02:10.560> specific 00:02:10.910 --> 00:02:10.920 align:start position:0% discount to users that visit specific 00:02:10.920 --> 00:02:13.550 align:start position:0% discount to users that visit specific locations<00:02:11.760> um<00:02:12.319> for<00:02:12.640> a<00:02:12.800> coffee<00:02:13.120> shop<00:02:13.440> a 00:02:13.550 --> 00:02:13.560 align:start position:0% locations um for a coffee shop a 00:02:13.560 --> 00:02:17.470 align:start position:0% locations um for a coffee shop a supermarket<00:02:14.360> or<00:02:14.720> something<00:02:15.239> else<00:02:16.280> um<00:02:17.280> to 00:02:17.470 --> 00:02:17.480 align:start position:0% supermarket or something else um to 00:02:17.480 --> 00:02:19.509 align:start position:0% supermarket or something else um to prove<00:02:17.720> your<00:02:17.920> attendance<00:02:18.519> in 00:02:19.509 --> 00:02:19.519 align:start position:0% prove your attendance in 00:02:19.519 --> 00:02:22.350 align:start position:0% prove your attendance in um<00:02:20.519> in<00:02:20.599> a<00:02:20.760> specific<00:02:21.120> location<00:02:21.640> for<00:02:22.120> um 00:02:22.350 --> 00:02:22.360 align:start position:0% um in a specific location for um 00:02:22.360 --> 00:02:25.430 align:start position:0% um in a specific location for um administrative<00:02:23.200> purposes<00:02:24.200> such<00:02:24.480> as<00:02:24.879> um<00:02:25.280> an 00:02:25.430 --> 00:02:25.440 align:start position:0% administrative purposes such as um an 00:02:25.440 --> 00:02:27.990 align:start position:0% administrative purposes such as um an example<00:02:25.760> would<00:02:25.920> be<00:02:26.879> uh<00:02:27.120> if<00:02:27.200> you<00:02:27.360> have<00:02:27.480> to<00:02:27.680> visit 00:02:27.990 --> 00:02:28.000 align:start position:0% example would be uh if you have to visit 00:02:28.000 --> 00:02:30.030 align:start position:0% example would be uh if you have to visit your<00:02:28.280> local<00:02:28.599> unemployment<00:02:29.200> office<00:02:29.480> once 00:02:30.030 --> 00:02:30.040 align:start position:0% your local unemployment office once 00:02:30.040 --> 00:02:32.070 align:start position:0% your local unemployment office once month<00:02:30.440> to<00:02:30.680> get<00:02:30.800> your<00:02:31.000> unemployment 00:02:32.070 --> 00:02:32.080 align:start position:0% month to get your unemployment 00:02:32.080 --> 00:02:34.350 align:start position:0% month to get your unemployment benefit<00:02:33.080> um<00:02:33.400> or<00:02:33.599> something<00:02:33.879> that<00:02:34.040> I<00:02:34.200> really 00:02:34.350 --> 00:02:34.360 align:start position:0% benefit um or something that I really 00:02:34.360 --> 00:02:36.430 align:start position:0% benefit um or something that I really like<00:02:34.720> augmented<00:02:35.200> reality<00:02:35.560> games<00:02:35.800> in<00:02:35.959> ethereum 00:02:36.430 --> 00:02:36.440 align:start position:0% like augmented reality games in ethereum 00:02:36.440 --> 00:02:38.190 align:start position:0% like augmented reality games in ethereum like<00:02:36.760> that<00:02:36.879> would<00:02:37.000> be<00:02:37.080> really<00:02:37.239> awesome<00:02:37.599> right 00:02:38.190 --> 00:02:38.200 align:start position:0% like that would be really awesome right 00:02:38.200 --> 00:02:41.070 align:start position:0% like that would be really awesome right something<00:02:38.480> like<00:02:38.720> Pokemon<00:02:39.159> go<00:02:39.640> but<00:02:40.040> uh<00:02:40.640> in<00:02:40.800> the 00:02:41.070 --> 00:02:41.080 align:start position:0% something like Pokemon go but uh in the 00:02:41.080 --> 00:02:43.149 align:start position:0% something like Pokemon go but uh in the ethereum<00:02:41.440> smart 00:02:43.149 --> 00:02:43.159 align:start position:0% ethereum smart 00:02:43.159 --> 00:02:47.670 align:start position:0% ethereum smart contract<00:02:44.280> um<00:02:45.280> so<00:02:45.480> what<00:02:45.599> is<00:02:45.879> proof<00:02:46.040> of<00:02:46.680> presence 00:02:47.670 --> 00:02:47.680 align:start position:0% contract um so what is proof of presence 00:02:47.680 --> 00:02:50.790 align:start position:0% contract um so what is proof of presence we<00:02:47.800> can<00:02:48.159> prove<00:02:48.480> that<00:02:49.000> um<00:02:49.360> a<00:02:49.519> user<00:02:49.879> is<00:02:50.239> indeed<00:02:50.640> in 00:02:50.790 --> 00:02:50.800 align:start position:0% we can prove that um a user is indeed in 00:02:50.800 --> 00:02:53.869 align:start position:0% we can prove that um a user is indeed in a<00:02:50.959> in<00:02:51.040> a<00:02:51.200> location<00:02:51.760> using<00:02:52.120> various<00:02:52.879> methods 00:02:53.869 --> 00:02:53.879 align:start position:0% a in a location using various methods 00:02:53.879 --> 00:02:56.790 align:start position:0% a in a location using various methods some<00:02:54.080> of<00:02:54.200> them<00:02:55.040> um<00:02:55.959> well<00:02:56.159> actually<00:02:56.440> almost<00:02:56.680> all 00:02:56.790 --> 00:02:56.800 align:start position:0% some of them um well actually almost all 00:02:56.800 --> 00:02:58.710 align:start position:0% some of them um well actually almost all of<00:02:56.959> them<00:02:57.159> can<00:02:57.319> be<00:02:57.480> spoofed<00:02:58.080> so<00:02:58.280> maybe<00:02:58.519> a 00:02:58.710 --> 00:02:58.720 align:start position:0% of them can be spoofed so maybe a 00:02:58.720 --> 00:03:01.110 align:start position:0% of them can be spoofed so maybe a combination<00:02:59.239> of<00:02:59.360> them<00:02:59.480> should<00:02:59.640> be<00:02:59.959> used<00:03:00.959> the 00:03:01.110 --> 00:03:01.120 align:start position:0% combination of them should be used the 00:03:01.120 --> 00:03:03.270 align:start position:0% combination of them should be used the most<00:03:02.000> usual<00:03:02.360> one<00:03:02.519> would<00:03:02.680> be<00:03:02.760> to<00:03:02.879> use<00:03:03.080> the 00:03:03.270 --> 00:03:03.280 align:start position:0% most usual one would be to use the 00:03:03.280 --> 00:03:05.390 align:start position:0% most usual one would be to use the mobile<00:03:03.599> geolocation<00:03:04.319> data<00:03:04.599> so<00:03:04.799> the<00:03:04.920> latitude 00:03:05.390 --> 00:03:05.400 align:start position:0% mobile geolocation data so the latitude 00:03:05.400 --> 00:03:06.710 align:start position:0% mobile geolocation data so the latitude and<00:03:05.560> the<00:03:05.640> longitude 00:03:06.710 --> 00:03:06.720 align:start position:0% and the longitude 00:03:06.720 --> 00:03:08.430 align:start position:0% and the longitude coordinates 00:03:08.430 --> 00:03:08.440 align:start position:0% coordinates 00:03:08.440 --> 00:03:11.509 align:start position:0% coordinates um<00:03:09.440> a<00:03:09.560> challenge<00:03:10.000> question<00:03:10.239> and<00:03:10.400> an<00:03:10.560> answer<00:03:11.280> so 00:03:11.509 --> 00:03:11.519 align:start position:0% um a challenge question and an answer so 00:03:11.519 --> 00:03:13.830 align:start position:0% um a challenge question and an answer so that<00:03:12.000> if<00:03:12.120> a<00:03:12.319> user<00:03:12.599> is<00:03:12.799> present<00:03:13.080> in<00:03:13.159> a<00:03:13.319> location 00:03:13.830 --> 00:03:13.840 align:start position:0% that if a user is present in a location 00:03:13.840 --> 00:03:17.350 align:start position:0% that if a user is present in a location only<00:03:14.159> he<00:03:14.599> can<00:03:15.080> um<00:03:15.480> answer<00:03:16.000> this<00:03:16.400> um<00:03:16.680> challenge 00:03:17.350 --> 00:03:17.360 align:start position:0% only he can um answer this um challenge 00:03:17.360 --> 00:03:19.750 align:start position:0% only he can um answer this um challenge question<00:03:18.360> a<00:03:18.480> bit<00:03:18.599> more<00:03:18.799> advanced<00:03:19.159> would<00:03:19.280> be<00:03:19.440> to 00:03:19.750 --> 00:03:19.760 align:start position:0% question a bit more advanced would be to 00:03:19.760 --> 00:03:22.309 align:start position:0% question a bit more advanced would be to analyze<00:03:20.400> the<00:03:20.799> data<00:03:21.120> of<00:03:21.480> uh<00:03:21.640> the<00:03:21.760> video<00:03:22.159> at 00:03:22.309 --> 00:03:22.319 align:start position:0% analyze the data of uh the video at 00:03:22.319 --> 00:03:24.670 align:start position:0% analyze the data of uh the video at deployment<00:03:22.879> and<00:03:23.080> compare<00:03:23.599> with<00:03:24.080> um<00:03:24.280> the<00:03:24.400> image 00:03:24.670 --> 00:03:24.680 align:start position:0% deployment and compare with um the image 00:03:24.680 --> 00:03:27.589 align:start position:0% deployment and compare with um the image feed<00:03:25.200> at<00:03:25.360> user 00:03:27.589 --> 00:03:27.599 align:start position:0% feed at user 00:03:27.599 --> 00:03:30.309 align:start position:0% feed at user interaction<00:03:28.599> uh<00:03:28.760> for<00:03:28.879> a<00:03:29.000> bit<00:03:29.159> more<00:03:29.319> security 00:03:30.309 --> 00:03:30.319 align:start position:0% interaction uh for a bit more security 00:03:30.319 --> 00:03:32.429 align:start position:0% interaction uh for a bit more security um<00:03:30.560> we<00:03:30.640> can<00:03:30.799> go<00:03:30.920> to<00:03:31.080> specialized<00:03:31.599> Hardware<00:03:32.120> so 00:03:32.429 --> 00:03:32.439 align:start position:0% um we can go to specialized Hardware so 00:03:32.439 --> 00:03:35.350 align:start position:0% um we can go to specialized Hardware so we<00:03:32.560> could<00:03:32.840> have<00:03:33.080> a<00:03:33.360> QR<00:03:33.760> code<00:03:34.760> a<00:03:34.840> sticker<00:03:35.159> with<00:03:35.280> a 00:03:35.350 --> 00:03:35.360 align:start position:0% we could have a QR code a sticker with a 00:03:35.360 --> 00:03:37.589 align:start position:0% we could have a QR code a sticker with a QR<00:03:35.599> code<00:03:35.799> on<00:03:35.920> top<00:03:36.080> of<00:03:36.200> it<00:03:36.560> and<00:03:36.680> that<00:03:36.799> would<00:03:37.000> be 00:03:37.589 --> 00:03:37.599 align:start position:0% QR code on top of it and that would be 00:03:37.599 --> 00:03:39.149 align:start position:0% QR code on top of it and that would be uh<00:03:37.760> on<00:03:38.000> location<00:03:38.400> and<00:03:38.519> then<00:03:38.640> the<00:03:38.760> user<00:03:38.959> would 00:03:39.149 --> 00:03:39.159 align:start position:0% uh on location and then the user would 00:03:39.159 --> 00:03:42.949 align:start position:0% uh on location and then the user would have<00:03:39.239> to<00:03:39.360> scan<00:03:40.280> or<00:03:40.560> also<00:03:41.519> um<00:03:42.519> same<00:03:42.720> thing<00:03:42.840> with 00:03:42.949 --> 00:03:42.959 align:start position:0% have to scan or also um same thing with 00:03:42.959 --> 00:03:46.149 align:start position:0% have to scan or also um same thing with an<00:03:43.120> RF<00:03:43.400> id<00:03:43.640> tag<00:03:44.120> and<00:03:44.239> an<00:03:44.400> RF<00:03:44.720> id<00:03:45.000> reader<00:03:46.000> or 00:03:46.149 --> 00:03:46.159 align:start position:0% an RF id tag and an RF id reader or 00:03:46.159 --> 00:03:48.910 align:start position:0% an RF id tag and an RF id reader or going<00:03:46.439> even<00:03:46.680> further<00:03:47.239> A<00:03:47.560> specialized<00:03:48.159> tiip 00:03:48.910 --> 00:03:48.920 align:start position:0% going even further A specialized tiip 00:03:48.920 --> 00:03:50.710 align:start position:0% going even further A specialized tiip for<00:03:49.159> example<00:03:49.480> that<00:03:49.599> would<00:03:49.720> be<00:03:49.840> on<00:03:50.080> location 00:03:50.710 --> 00:03:50.720 align:start position:0% for example that would be on location 00:03:50.720 --> 00:03:53.270 align:start position:0% for example that would be on location and<00:03:51.080> would<00:03:51.239> allow<00:03:51.519> people<00:03:51.799> to<00:03:52.439> um<00:03:52.799> interact 00:03:53.270 --> 00:03:53.280 align:start position:0% and would allow people to um interact 00:03:53.280 --> 00:03:56.470 align:start position:0% and would allow people to um interact with<00:03:53.959> um<00:03:54.959> uh<00:03:55.159> the<00:03:55.319> tip<00:03:55.680> via<00:03:55.920> Bluetooth<00:03:56.319> or 00:03:56.470 --> 00:03:56.480 align:start position:0% with um uh the tip via Bluetooth or 00:03:56.480 --> 00:03:58.710 align:start position:0% with um uh the tip via Bluetooth or something<00:03:56.760> like 00:03:58.710 --> 00:03:58.720 align:start position:0% something like 00:03:58.720 --> 00:04:00.350 align:start position:0% something like that 00:04:00.350 --> 00:04:00.360 align:start position:0% that 00:04:00.360 --> 00:04:04.350 align:start position:0% that so<00:04:00.720> C<00:04:01.239> works<00:04:01.439> very<00:04:01.599> very<00:04:01.760> simple<00:04:02.560> um<00:04:03.560> contracts 00:04:04.350 --> 00:04:04.360 align:start position:0% so C works very very simple um contracts 00:04:04.360 --> 00:04:06.270 align:start position:0% so C works very very simple um contracts uh<00:04:04.519> have<00:04:04.680> to<00:04:04.799> follow<00:04:05.040> a<00:04:05.200> specific 00:04:06.270 --> 00:04:06.280 align:start position:0% uh have to follow a specific 00:04:06.280 --> 00:04:10.190 align:start position:0% uh have to follow a specific interface<00:04:07.280> um<00:04:07.840> and<00:04:08.280> um<00:04:09.239> the<00:04:09.439> application<00:04:09.959> or 00:04:10.190 --> 00:04:10.200 align:start position:0% interface um and um the application or 00:04:10.200 --> 00:04:12.270 align:start position:0% interface um and um the application or the<00:04:10.319> system<00:04:10.640> allows<00:04:11.280> um<00:04:11.480> the<00:04:11.599> user<00:04:11.840> to<00:04:11.959> search 00:04:12.270 --> 00:04:12.280 align:start position:0% the system allows um the user to search 00:04:12.280 --> 00:04:14.670 align:start position:0% the system allows um the user to search for<00:04:13.000> contracts<00:04:13.480> that<00:04:13.640> follow<00:04:13.959> this<00:04:14.120> interface 00:04:14.670 --> 00:04:14.680 align:start position:0% for contracts that follow this interface 00:04:14.680 --> 00:04:16.349 align:start position:0% for contracts that follow this interface and<00:04:14.920> are<00:04:15.360> around 00:04:16.349 --> 00:04:16.359 align:start position:0% and are around 00:04:16.359 --> 00:04:19.349 align:start position:0% and are around them<00:04:17.359> uh<00:04:17.479> when<00:04:17.680> a<00:04:17.840> user<00:04:18.120> deploys<00:04:18.519> a<00:04:18.680> contract 00:04:19.349 --> 00:04:19.359 align:start position:0% them uh when a user deploys a contract 00:04:19.359 --> 00:04:21.430 align:start position:0% them uh when a user deploys a contract uh<00:04:19.880> a<00:04:20.000> sorka<00:04:20.440> contract<00:04:20.840> he<00:04:20.959> also<00:04:21.160> has<00:04:21.320> to 00:04:21.430 --> 00:04:21.440 align:start position:0% uh a sorka contract he also has to 00:04:21.440 --> 00:04:24.629 align:start position:0% uh a sorka contract he also has to provide<00:04:21.720> the<00:04:21.840> API<00:04:22.680> so<00:04:23.280> uh<00:04:23.400> the<00:04:23.520> system<00:04:23.880> knows 00:04:24.629 --> 00:04:24.639 align:start position:0% provide the API so uh the system knows 00:04:24.639 --> 00:04:27.469 align:start position:0% provide the API so uh the system knows uh<00:04:24.800> what<00:04:25.000> kind<00:04:25.199> of<00:04:25.639> methods<00:04:26.639> um<00:04:26.919> the<00:04:27.040> contract 00:04:27.469 --> 00:04:27.479 align:start position:0% uh what kind of methods um the contract 00:04:27.479 --> 00:04:29.110 align:start position:0% uh what kind of methods um the contract provides<00:04:27.840> in<00:04:27.960> order<00:04:28.520> for<00:04:28.680> the<00:04:28.800> user<00:04:29.000> to 00:04:29.110 --> 00:04:29.120 align:start position:0% provides in order for the user to 00:04:29.120 --> 00:04:30.430 align:start position:0% provides in order for the user to interact<00:04:29.479> with<00:04:29.600> it 00:04:30.430 --> 00:04:30.440 align:start position:0% interact with it 00:04:30.440 --> 00:04:31.950 align:start position:0% interact with it and<00:04:30.639> also<00:04:30.919> he<00:04:31.039> has<00:04:31.160> to<00:04:31.320> provide<00:04:31.600> proof<00:04:31.800> of 00:04:31.950 --> 00:04:31.960 align:start position:0% and also he has to provide proof of 00:04:31.960 --> 00:04:34.990 align:start position:0% and also he has to provide proof of presence<00:04:32.400> as<00:04:32.880> I<00:04:33.160> explained 00:04:34.990 --> 00:04:35.000 align:start position:0% presence as I explained 00:04:35.000 --> 00:04:37.189 align:start position:0% presence as I explained before<00:04:36.000> so<00:04:36.160> the<00:04:36.280> contract<00:04:36.639> interface<00:04:37.000> looks 00:04:37.189 --> 00:04:37.199 align:start position:0% before so the contract interface looks 00:04:37.199 --> 00:04:39.430 align:start position:0% before so the contract interface looks something<00:04:37.479> like<00:04:37.680> this<00:04:37.960> at<00:04:38.039> the<00:04:38.199> moment<00:04:39.199> I<00:04:39.320> have 00:04:39.430 --> 00:04:39.440 align:start position:0% something like this at the moment I have 00:04:39.440 --> 00:04:40.950 align:start position:0% something like this at the moment I have to<00:04:39.520> mention<00:04:39.840> this<00:04:39.919> is<00:04:40.039> all<00:04:40.199> a<00:04:40.479> very<00:04:40.639> early 00:04:40.950 --> 00:04:40.960 align:start position:0% to mention this is all a very early 00:04:40.960 --> 00:04:42.670 align:start position:0% to mention this is all a very early prototype<00:04:41.440> since<00:04:41.800> I<00:04:41.919> was<00:04:42.080> really<00:04:42.280> busy<00:04:42.560> with 00:04:42.670 --> 00:04:42.680 align:start position:0% prototype since I was really busy with 00:04:42.680 --> 00:04:44.510 align:start position:0% prototype since I was really busy with the<00:04:42.840> Dow<00:04:43.080> aftermath<00:04:43.520> so<00:04:43.800> right<00:04:43.960> now<00:04:44.199> this<00:04:44.320> is 00:04:44.510 --> 00:04:44.520 align:start position:0% the Dow aftermath so right now this is 00:04:44.520 --> 00:04:47.749 align:start position:0% the Dow aftermath so right now this is this<00:04:44.600> is<00:04:44.759> really<00:04:45.000> new<00:04:46.000> um<00:04:46.759> so<00:04:47.080> a<00:04:47.199> user<00:04:47.479> has<00:04:47.600> to 00:04:47.749 --> 00:04:47.759 align:start position:0% this is really new um so a user has to 00:04:47.759 --> 00:04:50.590 align:start position:0% this is really new um so a user has to provide<00:04:48.000> a<00:04:48.120> name<00:04:48.280> for<00:04:48.440> the<00:04:48.600> contract<00:04:49.600> um 00:04:50.590 --> 00:04:50.600 align:start position:0% provide a name for the contract um 00:04:50.600 --> 00:04:52.629 align:start position:0% provide a name for the contract um latitude<00:04:51.039> and<00:04:51.160> longitude<00:04:51.600> coordinates<00:04:52.479> which 00:04:52.629 --> 00:04:52.639 align:start position:0% latitude and longitude coordinates which 00:04:52.639 --> 00:04:55.270 align:start position:0% latitude and longitude coordinates which are<00:04:52.960> in<00:04:53.720> integer<00:04:54.160> approximation<00:04:54.800> since<00:04:55.160> uh 00:04:55.270 --> 00:04:55.280 align:start position:0% are in integer approximation since uh 00:04:55.280 --> 00:04:57.550 align:start position:0% are in integer approximation since uh solidity<00:04:55.759> does<00:04:55.919> not<00:04:56.039> allow<00:04:56.320> floats 00:04:57.550 --> 00:04:57.560 align:start position:0% solidity does not allow floats 00:04:57.560 --> 00:05:00.270 align:start position:0% solidity does not allow floats yet<00:04:58.560> um<00:04:58.800> the<00:04:59.080> question<00:04:59.720> so<00:04:59.840> the<00:04:59.919> challenge 00:05:00.270 --> 00:05:00.280 align:start position:0% yet um the question so the challenge 00:05:00.280 --> 00:05:02.189 align:start position:0% yet um the question so the challenge question<00:05:00.479> for<00:05:00.680> the<00:05:00.759> proof<00:05:01.000> of<00:05:01.160> presence<00:05:01.720> and 00:05:02.189 --> 00:05:02.199 align:start position:0% question for the proof of presence and 00:05:02.199 --> 00:05:04.790 align:start position:0% question for the proof of presence and um<00:05:03.199> the<00:05:03.360> H<00:05:03.600> of<00:05:03.759> the<00:05:03.880> answer<00:05:04.240> since<00:05:04.440> we<00:05:04.600> really 00:05:04.790 --> 00:05:04.800 align:start position:0% um the H of the answer since we really 00:05:04.800 --> 00:05:06.990 align:start position:0% um the H of the answer since we really don't<00:05:04.960> want<00:05:05.160> to<00:05:05.360> give<00:05:05.600> the<00:05:06.199> plain<00:05:06.520> answer<00:05:06.840> in 00:05:06.990 --> 00:05:07.000 align:start position:0% don't want to give the plain answer in 00:05:07.000 --> 00:05:10.590 align:start position:0% don't want to give the plain answer in in<00:05:07.120> plain<00:05:07.360> text<00:05:07.600> in<00:05:08.160> ethereum 00:05:10.590 --> 00:05:10.600 align:start position:0% 00:05:10.600 --> 00:05:13.870 align:start position:0% transaction<00:05:11.600> um<00:05:12.199> we<00:05:12.360> have<00:05:12.479> a<00:05:12.600> modifier<00:05:13.440> like 00:05:13.870 --> 00:05:13.880 align:start position:0% transaction um we have a modifier like 00:05:13.880 --> 00:05:17.309 align:start position:0% transaction um we have a modifier like like<00:05:14.160> this<00:05:14.520> so<00:05:14.919> that<00:05:15.240> people<00:05:15.560> can<00:05:16.039> um 00:05:17.309 --> 00:05:17.319 align:start position:0% like this so that people can um 00:05:17.319 --> 00:05:19.430 align:start position:0% like this so that people can um essentially<00:05:18.319> um<00:05:18.479> use<00:05:18.720> this<00:05:18.840> modifier<00:05:19.280> in 00:05:19.430 --> 00:05:19.440 align:start position:0% essentially um use this modifier in 00:05:19.440 --> 00:05:22.790 align:start position:0% essentially um use this modifier in their<00:05:19.759> sorka<00:05:20.240> contracts<00:05:20.759> to<00:05:21.479> um<00:05:21.840> allow<00:05:22.680> the 00:05:22.790 --> 00:05:22.800 align:start position:0% their sorka contracts to um allow the 00:05:22.800 --> 00:05:25.189 align:start position:0% their sorka contracts to um allow the user<00:05:23.120> to<00:05:23.319> prove<00:05:23.680> that<00:05:23.880> he<00:05:24.039> is<00:05:24.199> in<00:05:24.360> the<00:05:24.479> location 00:05:25.189 --> 00:05:25.199 align:start position:0% user to prove that he is in the location 00:05:25.199 --> 00:05:28.270 align:start position:0% user to prove that he is in the location so<00:05:25.440> all<00:05:25.560> it<00:05:25.720> does<00:05:25.919> is<00:05:26.240> check<00:05:26.880> the<00:05:27.880> the<00:05:28.000> sub 00:05:28.270 --> 00:05:28.280 align:start position:0% so all it does is check the the sub 00:05:28.280 --> 00:05:30.510 align:start position:0% so all it does is check the the sub three<00:05:28.560> of<00:05:28.720> the<00:05:28.840> answer<00:05:29.160> if<00:05:29.280> it<00:05:29.720> mates<00:05:30.000> the<00:05:30.160> has 00:05:30.510 --> 00:05:30.520 align:start position:0% three of the answer if it mates the has 00:05:30.520 --> 00:05:33.189 align:start position:0% three of the answer if it mates the has and<00:05:30.720> calculates<00:05:31.199> the<00:05:31.360> distance<00:05:31.759> if<00:05:31.880> it's<00:05:32.360> um 00:05:33.189 --> 00:05:33.199 align:start position:0% and calculates the distance if it's um 00:05:33.199 --> 00:05:35.110 align:start position:0% and calculates the distance if it's um within<00:05:33.479> a<00:05:33.720> specific<00:05:34.120> parameter<00:05:34.880> then<00:05:35.000> it 00:05:35.110 --> 00:05:35.120 align:start position:0% within a specific parameter then it 00:05:35.120 --> 00:05:38.189 align:start position:0% within a specific parameter then it allows<00:05:35.440> the<00:05:35.520> user<00:05:35.720> to<00:05:35.840> interact<00:05:36.120> with<00:05:36.240> the 00:05:38.189 --> 00:05:38.199 align:start position:0% allows the user to interact with the 00:05:38.199 --> 00:05:41.309 align:start position:0% allows the user to interact with the contract<00:05:39.199> um<00:05:40.199> the<00:05:40.319> owners<00:05:40.680> of<00:05:40.800> the<00:05:40.960> contract 00:05:41.309 --> 00:05:41.319 align:start position:0% contract um the owners of the contract 00:05:41.319 --> 00:05:44.790 align:start position:0% contract um the owners of the contract should<00:05:41.680> change<00:05:42.120> their<00:05:42.960> um<00:05:43.360> Talent<00:05:44.199> answer<00:05:44.520> and 00:05:44.790 --> 00:05:44.800 align:start position:0% should change their um Talent answer and 00:05:44.800 --> 00:05:46.469 align:start position:0% should change their um Talent answer and qu<00:05:45.039> question<00:05:45.280> and<00:05:45.440> answer<00:05:45.960> quite<00:05:46.160> often 00:05:46.469 --> 00:05:46.479 align:start position:0% qu question and answer quite often 00:05:46.479 --> 00:05:48.390 align:start position:0% qu question and answer quite often because<00:05:46.680> the<00:05:46.840> situation<00:05:47.199> on<00:05:47.319> the<00:05:47.479> ground<00:05:48.120> uh 00:05:48.390 --> 00:05:48.400 align:start position:0% because the situation on the ground uh 00:05:48.400 --> 00:05:52.110 align:start position:0% because the situation on the ground uh is<00:05:48.560> volatile<00:05:49.720> so<00:05:50.720> um<00:05:51.240> something<00:05:51.600> could<00:05:51.800> change 00:05:52.110 --> 00:05:52.120 align:start position:0% is volatile so um something could change 00:05:52.120 --> 00:05:53.909 align:start position:0% is volatile so um something could change and<00:05:52.319> they<00:05:52.479> should<00:05:52.720> update<00:05:53.080> it<00:05:53.280> so<00:05:53.479> that<00:05:53.600> users 00:05:53.909 --> 00:05:53.919 align:start position:0% and they should update it so that users 00:05:53.919 --> 00:05:57.550 align:start position:0% and they should update it so that users can<00:05:54.039> still<00:05:54.280> interact<00:05:54.680> with<00:05:55.120> with<00:05:55.199> a 00:05:57.550 --> 00:05:57.560 align:start position:0% 00:05:57.560 --> 00:05:59.749 align:start position:0% contract<00:05:58.560> um<00:05:58.759> so<00:05:58.960> to<00:05:59.080> see<00:05:59.199> an<00:05:59.319> example 00:05:59.749 --> 00:05:59.759 align:start position:0% contract um so to see an example 00:05:59.759 --> 00:06:01.430 align:start position:0% contract um so to see an example contract<00:06:00.120> of<00:06:00.319> which<00:06:00.479> we<00:06:00.600> will<00:06:00.720> see<00:06:00.919> a<00:06:01.120> demo 00:06:01.430 --> 00:06:01.440 align:start position:0% contract of which we will see a demo 00:06:01.440 --> 00:06:05.189 align:start position:0% contract of which we will see a demo video<00:06:02.000> afterwards<00:06:03.000> this<00:06:03.199> is<00:06:03.600> um<00:06:04.520> a<00:06:04.720> discount 00:06:05.189 --> 00:06:05.199 align:start position:0% video afterwards this is um a discount 00:06:05.199 --> 00:06:08.589 align:start position:0% video afterwards this is um a discount token<00:06:05.560> for<00:06:06.160> a<00:06:07.160> uh<00:06:07.440> loyalty<00:06:07.960> program<00:06:08.280> let's<00:06:08.440> say 00:06:08.589 --> 00:06:08.599 align:start position:0% token for a uh loyalty program let's say 00:06:08.599 --> 00:06:12.350 align:start position:0% token for a uh loyalty program let's say of<00:06:08.840> a<00:06:09.039> coffee<00:06:09.440> shop<00:06:10.840> where<00:06:11.840> you<00:06:12.080> have<00:06:12.240> the 00:06:12.350 --> 00:06:12.360 align:start position:0% of a coffee shop where you have the 00:06:12.360 --> 00:06:15.309 align:start position:0% of a coffee shop where you have the usual<00:06:12.639> sorka<00:06:13.120> interface<00:06:13.639> plus<00:06:14.199> um<00:06:14.960> a<00:06:15.080> number 00:06:15.309 --> 00:06:15.319 align:start position:0% usual sorka interface plus um a number 00:06:15.319 --> 00:06:18.350 align:start position:0% usual sorka interface plus um a number of<00:06:15.520> tokens<00:06:15.840> to<00:06:16.000> reward<00:06:16.520> to<00:06:16.720> each<00:06:17.160> user<00:06:18.039> and<00:06:18.199> the 00:06:18.350 --> 00:06:18.360 align:start position:0% of tokens to reward to each user and the 00:06:18.360 --> 00:06:21.790 align:start position:0% of tokens to reward to each user and the duration<00:06:18.800> of<00:06:19.039> the<00:06:19.560> uh<00:06:19.680> loyalty<00:06:20.199> program<00:06:20.919> in<00:06:21.400> um 00:06:21.790 --> 00:06:21.800 align:start position:0% duration of the uh loyalty program in um 00:06:21.800 --> 00:06:23.589 align:start position:0% duration of the uh loyalty program in um Unix 00:06:23.589 --> 00:06:23.599 align:start position:0% Unix 00:06:23.599 --> 00:06:26.150 align:start position:0% Unix timestamp<00:06:24.599> uh<00:06:24.759> so<00:06:25.000> this<00:06:25.120> is<00:06:25.319> the<00:06:25.800> the<00:06:25.880> simple 00:06:26.150 --> 00:06:26.160 align:start position:0% timestamp uh so this is the the simple 00:06:26.160 --> 00:06:28.870 align:start position:0% timestamp uh so this is the the simple interaction<00:06:26.680> function<00:06:27.120> where<00:06:27.400> the<00:06:27.520> user<00:06:28.400> just 00:06:28.870 --> 00:06:28.880 align:start position:0% interaction function where the user just 00:06:28.880 --> 00:06:30.189 align:start position:0% interaction function where the user just claims<00:06:29.199> the<00:06:29.360> token 00:06:30.189 --> 00:06:30.199 align:start position:0% claims the token 00:06:30.199 --> 00:06:32.670 align:start position:0% claims the token using<00:06:30.800> um<00:06:31.120> the<00:06:31.240> proof<00:06:31.440> of<00:06:31.560> present<00:06:31.880> modifier 00:06:32.670 --> 00:06:32.680 align:start position:0% using um the proof of present modifier 00:06:32.680 --> 00:06:36.430 align:start position:0% using um the proof of present modifier and<00:06:32.880> as<00:06:33.000> soon<00:06:33.240> as<00:06:33.639> um<00:06:34.639> um<00:06:35.120> his<00:06:35.440> presence<00:06:35.960> is 00:06:36.430 --> 00:06:36.440 align:start position:0% and as soon as um um his presence is 00:06:36.440 --> 00:06:38.189 align:start position:0% and as soon as um um his presence is indeed<00:06:37.160> verified<00:06:37.599> that<00:06:37.720> he's<00:06:37.880> in<00:06:38.039> that 00:06:38.189 --> 00:06:38.199 align:start position:0% indeed verified that he's in that 00:06:38.199 --> 00:06:40.749 align:start position:0% indeed verified that he's in that location<00:06:38.639> then<00:06:38.759> he<00:06:38.919> gets<00:06:39.199> his 00:06:40.749 --> 00:06:40.759 align:start position:0% location then he gets his 00:06:40.759 --> 00:06:49.589 align:start position:0% location then he gets his tokens<00:06:41.759> uh<00:06:41.960> so<00:06:42.280> now<00:06:42.840> here<00:06:43.240> is<00:06:44.000> um<00:06:45.000> um<00:06:45.800> the<00:06:46.280> demo 00:06:49.589 --> 00:06:49.599 align:start position:0% 00:06:49.599 --> 00:06:54.150 align:start position:0% video<00:06:50.599> so<00:06:51.199> um<00:06:52.199> this<00:06:52.319> is<00:06:52.520> in<00:06:52.720> in<00:06:52.840> Berlin<00:06:53.800> um<00:06:54.039> this 00:06:54.150 --> 00:06:54.160 align:start position:0% video so um this is in in Berlin um this 00:06:54.160 --> 00:06:55.550 align:start position:0% video so um this is in in Berlin um this is<00:06:54.240> a<00:06:54.360> very<00:06:54.479> touristic<00:06:54.880> location<00:06:55.240> it's<00:06:55.400> the 00:06:55.550 --> 00:06:55.560 align:start position:0% is a very touristic location it's the 00:06:55.560 --> 00:06:58.469 align:start position:0% is a very touristic location it's the Brandenburg<00:06:56.400> gate<00:06:57.400> uh<00:06:57.520> it's<00:06:57.639> a<00:06:57.919> very<00:06:58.160> nice 00:06:58.469 --> 00:06:58.479 align:start position:0% Brandenburg gate uh it's a very nice 00:06:58.479 --> 00:07:00.510 align:start position:0% Brandenburg gate uh it's a very nice place<00:06:58.680> to<00:06:58.840> put<00:06:59.000> an<00:06:59.160> adver<00:06:59.680> M<00:06:59.879> contract<00:07:00.319> let's 00:07:00.510 --> 00:07:00.520 align:start position:0% place to put an adver M contract let's 00:07:00.520 --> 00:07:05.070 align:start position:0% place to put an adver M contract let's say<00:07:01.440> so<00:07:01.840> you<00:07:02.479> as<00:07:02.759> the<00:07:03.360> the<00:07:03.479> owner<00:07:03.840> of<00:07:04.120> the<00:07:04.840> of 00:07:05.070 --> 00:07:05.080 align:start position:0% say so you as the the owner of the of 00:07:05.080 --> 00:07:08.469 align:start position:0% say so you as the the owner of the of the<00:07:05.759> of<00:07:05.879> the<00:07:06.000> coffee<00:07:06.639> shop<00:07:07.039> would<00:07:07.479> open<00:07:07.759> the 00:07:08.469 --> 00:07:08.479 align:start position:0% the of the coffee shop would open the 00:07:08.479 --> 00:07:11.909 align:start position:0% the of the coffee shop would open the application<00:07:09.479> and<00:07:09.639> try<00:07:09.840> to<00:07:09.960> deploy<00:07:10.240> a<00:07:10.319> new 00:07:11.909 --> 00:07:11.919 align:start position:0% application and try to deploy a new 00:07:11.919 --> 00:07:13.990 align:start position:0% application and try to deploy a new contract<00:07:12.919> then<00:07:13.080> you<00:07:13.199> would<00:07:13.360> search<00:07:13.720> around 00:07:13.990 --> 00:07:14.000 align:start position:0% contract then you would search around 00:07:14.000 --> 00:07:16.309 align:start position:0% contract then you would search around the<00:07:14.160> location<00:07:14.599> and<00:07:14.800> and<00:07:14.960> try<00:07:15.120> to<00:07:15.280> find<00:07:16.000> um<00:07:16.160> the 00:07:16.309 --> 00:07:16.319 align:start position:0% the location and and try to find um the 00:07:16.319 --> 00:07:19.350 align:start position:0% the location and and try to find um the place<00:07:16.520> to<00:07:16.680> put<00:07:17.000> the<00:07:17.280> ethereum<00:07:18.120> hexagon<00:07:19.120> where 00:07:19.350 --> 00:07:19.360 align:start position:0% place to put the ethereum hexagon where 00:07:19.360 --> 00:07:20.430 align:start position:0% place to put the ethereum hexagon where where<00:07:19.479> you<00:07:19.560> would<00:07:19.759> like<00:07:19.879> to<00:07:20.039> place<00:07:20.240> your 00:07:20.430 --> 00:07:20.440 align:start position:0% where you would like to place your 00:07:20.440 --> 00:07:22.510 align:start position:0% where you would like to place your contract<00:07:20.879> so<00:07:21.039> the<00:07:21.120> brandur<00:07:21.599> gate<00:07:21.759> is<00:07:21.840> a<00:07:22.000> nice 00:07:22.510 --> 00:07:22.520 align:start position:0% contract so the brandur gate is a nice 00:07:22.520 --> 00:07:26.469 align:start position:0% contract so the brandur gate is a nice nice 00:07:26.469 --> 00:07:26.479 align:start position:0% 00:07:26.479 --> 00:07:28.710 align:start position:0% location<00:07:27.479> uh<00:07:27.599> you<00:07:27.720> have<00:07:27.840> to<00:07:28.000> give<00:07:28.240> a<00:07:28.360> name<00:07:28.560> to 00:07:28.710 --> 00:07:28.720 align:start position:0% location uh you have to give a name to 00:07:28.720 --> 00:07:31.589 align:start position:0% location uh you have to give a name to identify<00:07:29.120> the<00:07:29.199> contract<00:07:30.000> with<00:07:31.000> since<00:07:31.360> we<00:07:31.479> have 00:07:31.589 --> 00:07:31.599 align:start position:0% identify the contract with since we have 00:07:31.599 --> 00:07:32.950 align:start position:0% identify the contract with since we have a<00:07:31.680> coffee<00:07:31.919> shop<00:07:32.120> and<00:07:32.240> this<00:07:32.360> is<00:07:32.440> a<00:07:32.639> coffee 00:07:32.950 --> 00:07:32.960 align:start position:0% a coffee shop and this is a coffee 00:07:32.960 --> 00:07:34.670 align:start position:0% a coffee shop and this is a coffee discount<00:07:33.400> token<00:07:33.720> let's<00:07:33.919> just<00:07:34.080> call<00:07:34.240> it<00:07:34.400> coffee 00:07:34.670 --> 00:07:34.680 align:start position:0% discount token let's just call it coffee 00:07:34.680 --> 00:07:36.629 align:start position:0% discount token let's just call it coffee discount<00:07:35.039> I'm<00:07:35.160> sorry<00:07:35.400> I<00:07:35.520> misspelled<00:07:35.960> coffee<00:07:36.479> I 00:07:36.629 --> 00:07:36.639 align:start position:0% discount I'm sorry I misspelled coffee I 00:07:36.639 --> 00:07:38.749 align:start position:0% discount I'm sorry I misspelled coffee I can't<00:07:36.879> remake<00:07:37.199> the 00:07:38.749 --> 00:07:38.759 align:start position:0% can't remake the 00:07:38.759 --> 00:07:42.550 align:start position:0% can't remake the video<00:07:39.960> um<00:07:40.960> there<00:07:41.080> is<00:07:41.199> an<00:07:41.360> exhibition<00:07:41.919> right 00:07:42.550 --> 00:07:42.560 align:start position:0% video um there is an exhibition right 00:07:42.560 --> 00:07:45.029 align:start position:0% video um there is an exhibition right next<00:07:42.759> to<00:07:42.919> it<00:07:43.520> and<00:07:43.720> it<00:07:43.879> has<00:07:44.120> the<00:07:44.319> poster<00:07:44.639> of<00:07:44.919> uh 00:07:45.029 --> 00:07:45.039 align:start position:0% next to it and it has the poster of uh 00:07:45.039 --> 00:07:48.589 align:start position:0% next to it and it has the poster of uh someone<00:07:45.479> called<00:07:45.720> Kesler<00:07:46.280> this<00:07:46.400> is<00:07:46.720> the<00:07:47.599> the 00:07:48.589 --> 00:07:48.599 align:start position:0% someone called Kesler this is the the 00:07:48.599 --> 00:07:50.309 align:start position:0% someone called Kesler this is the the the<00:07:48.720> name<00:07:48.879> of<00:07:49.000> the<00:07:49.120> artist<00:07:49.360> of<00:07:49.479> the<00:07:49.599> exhibition 00:07:50.309 --> 00:07:50.319 align:start position:0% the name of the artist of the exhibition 00:07:50.319 --> 00:07:52.270 align:start position:0% the name of the artist of the exhibition and<00:07:50.720> um<00:07:51.240> so<00:07:51.479> if<00:07:51.599> you<00:07:51.680> are<00:07:51.879> there<00:07:52.039> you<00:07:52.120> would 00:07:52.270 --> 00:07:52.280 align:start position:0% and um so if you are there you would 00:07:52.280 --> 00:07:54.029 align:start position:0% and um so if you are there you would have<00:07:52.440> seen<00:07:52.680> it<00:07:52.840> so<00:07:53.039> we<00:07:53.159> are<00:07:53.319> asking<00:07:53.720> in<00:07:53.879> the 00:07:54.029 --> 00:07:54.039 align:start position:0% have seen it so we are asking in the 00:07:54.039 --> 00:07:55.430 align:start position:0% have seen it so we are asking in the question<00:07:54.560> what's<00:07:54.759> the<00:07:54.879> last<00:07:55.080> name<00:07:55.199> of<00:07:55.319> the 00:07:55.430 --> 00:07:55.440 align:start position:0% question what's the last name of the 00:07:55.440 --> 00:07:58.270 align:start position:0% question what's the last name of the exhibition's<00:07:56.280> uh 00:07:58.270 --> 00:07:58.280 align:start position:0% exhibition's uh 00:07:58.280 --> 00:08:04.589 align:start position:0% exhibition's uh artist<00:07:59.280> uh<00:07:59.680> yeah<00:07:59.840> so<00:08:00.000> the<00:08:00.159> answer<00:08:00.440> would<00:08:00.599> be 00:08:04.589 --> 00:08:04.599 align:start position:0% 00:08:04.599 --> 00:08:07.230 align:start position:0% Kesler<00:08:05.599> so<00:08:05.840> now<00:08:06.280> um<00:08:06.440> the<00:08:06.560> user<00:08:06.840> can<00:08:07.039> just 00:08:07.230 --> 00:08:07.240 align:start position:0% Kesler so now um the user can just 00:08:07.240 --> 00:08:09.149 align:start position:0% Kesler so now um the user can just choose<00:08:07.599> his<00:08:07.759> source<00:08:08.039> code<00:08:08.319> I<00:08:08.440> have<00:08:08.560> a<00:08:08.680> template 00:08:09.149 --> 00:08:09.159 align:start position:0% choose his source code I have a template 00:08:09.159 --> 00:08:10.350 align:start position:0% choose his source code I have a template here<00:08:09.360> and<00:08:09.479> then<00:08:09.599> we're<00:08:09.840> deploying<00:08:10.199> the 00:08:10.350 --> 00:08:10.360 align:start position:0% here and then we're deploying the 00:08:10.360 --> 00:08:13.950 align:start position:0% here and then we're deploying the contract<00:08:11.159> waiting<00:08:11.440> for<00:08:11.599> it<00:08:11.720> to<00:08:11.840> get<00:08:12.319> mined<00:08:13.319> um 00:08:13.950 --> 00:08:13.960 align:start position:0% contract waiting for it to get mined um 00:08:13.960 --> 00:08:15.309 align:start position:0% contract waiting for it to get mined um that's<00:08:14.120> a<00:08:14.240> bit<00:08:14.360> fast<00:08:14.599> forward<00:08:14.879> it<00:08:15.039> because<00:08:15.199> it 00:08:15.309 --> 00:08:15.319 align:start position:0% that's a bit fast forward it because it 00:08:15.319 --> 00:08:18.350 align:start position:0% that's a bit fast forward it because it takes<00:08:15.560> a<00:08:15.720> bit<00:08:16.440> for<00:08:16.720> the<00:08:17.599> contract<00:08:18.039> address<00:08:18.280> to 00:08:18.350 --> 00:08:18.360 align:start position:0% takes a bit for the contract address to 00:08:18.360 --> 00:08:21.749 align:start position:0% takes a bit for the contract address to be<00:08:18.440> verified<00:08:18.840> and<00:08:18.960> there<00:08:19.080> is<00:08:19.159> our<00:08:19.680> address<00:08:20.759> um 00:08:21.749 --> 00:08:21.759 align:start position:0% be verified and there is our address um 00:08:21.759 --> 00:08:24.029 align:start position:0% be verified and there is our address um then<00:08:22.120> we<00:08:22.280> can<00:08:22.680> uh<00:08:23.080> start<00:08:23.479> searching<00:08:23.800> for 00:08:24.029 --> 00:08:24.039 align:start position:0% then we can uh start searching for 00:08:24.039 --> 00:08:26.070 align:start position:0% then we can uh start searching for contracts<00:08:24.520> around 00:08:26.070 --> 00:08:26.080 align:start position:0% contracts around 00:08:26.080 --> 00:08:30.070 align:start position:0% contracts around us<00:08:27.080> and<00:08:27.599> um<00:08:28.479> after<00:08:28.720> the<00:08:28.800> Google<00:08:29.039> Maps<00:08:29.240> a 00:08:30.070 --> 00:08:30.080 align:start position:0% us and um after the Google Maps a 00:08:30.080 --> 00:08:35.269 align:start position:0% us and um after the Google Maps a um<00:08:31.039> um<00:08:32.200> load<00:08:33.200> we<00:08:33.360> can<00:08:33.880> um<00:08:34.479> see<00:08:34.719> the<00:08:34.880> ethereum 00:08:35.269 --> 00:08:35.279 align:start position:0% um um load we can um see the ethereum 00:08:35.279 --> 00:08:37.190 align:start position:0% um um load we can um see the ethereum hexagon<00:08:35.760> where<00:08:35.919> that<00:08:36.320> um<00:08:36.680> shows<00:08:37.000> that<00:08:37.120> there 00:08:37.190 --> 00:08:37.200 align:start position:0% hexagon where that um shows that there 00:08:37.200 --> 00:08:38.790 align:start position:0% hexagon where that um shows that there is<00:08:37.320> a<00:08:37.479> contract<00:08:37.760> deployed<00:08:38.159> at<00:08:38.640> this 00:08:38.790 --> 00:08:38.800 align:start position:0% is a contract deployed at this 00:08:38.800 --> 00:08:40.310 align:start position:0% is a contract deployed at this particular<00:08:39.200> location<00:08:39.640> we<00:08:39.760> can<00:08:39.880> see<00:08:40.080> that<00:08:40.240> this 00:08:40.310 --> 00:08:40.320 align:start position:0% particular location we can see that this 00:08:40.320 --> 00:08:42.750 align:start position:0% particular location we can see that this is<00:08:40.440> the<00:08:40.560> coffee<00:08:40.880> discount<00:08:41.719> uh<00:08:42.399> that<00:08:42.599> we 00:08:42.750 --> 00:08:42.760 align:start position:0% is the coffee discount uh that we 00:08:42.760 --> 00:08:44.790 align:start position:0% is the coffee discount uh that we deployed<00:08:43.159> and<00:08:43.240> we<00:08:43.320> can<00:08:43.479> interact<00:08:43.839> with<00:08:44.000> it 00:08:44.790 --> 00:08:44.800 align:start position:0% deployed and we can interact with it 00:08:44.800 --> 00:08:47.110 align:start position:0% deployed and we can interact with it using<00:08:45.080> the<00:08:45.200> ABI<00:08:45.760> uh<00:08:45.880> sorry<00:08:46.279> uh<00:08:46.440> we<00:08:46.720> we<00:08:46.880> get<00:08:47.040> the 00:08:47.110 --> 00:08:47.120 align:start position:0% using the ABI uh sorry uh we we get the 00:08:47.120 --> 00:08:49.430 align:start position:0% using the ABI uh sorry uh we we get the proof<00:08:47.320> of<00:08:47.480> presence<00:08:47.880> challenge<00:08:48.320> question<00:08:49.080> we 00:08:49.430 --> 00:08:49.440 align:start position:0% proof of presence challenge question we 00:08:49.440 --> 00:08:51.030 align:start position:0% proof of presence challenge question we saw<00:08:49.760> that<00:08:49.880> the<00:08:50.000> name<00:08:50.160> of<00:08:50.279> the<00:08:50.399> artist<00:08:50.680> is 00:08:51.030 --> 00:08:51.040 align:start position:0% saw that the name of the artist is 00:08:51.040 --> 00:08:53.509 align:start position:0% saw that the name of the artist is Kesler<00:08:52.040> so<00:08:52.399> that's<00:08:52.560> the<00:08:52.680> correct<00:08:52.959> answer<00:08:53.279> yay 00:08:53.509 --> 00:08:53.519 align:start position:0% Kesler so that's the correct answer yay 00:08:53.519 --> 00:08:57.070 align:start position:0% Kesler so that's the correct answer yay we<00:08:53.720> get<00:08:54.040> the<00:08:54.320> API<00:08:54.920> of<00:08:55.040> the<00:08:55.399> contract<00:08:56.399> we<00:08:56.720> can 00:08:57.070 --> 00:08:57.080 align:start position:0% we get the API of the contract we can 00:08:57.080 --> 00:09:01.630 align:start position:0% we get the API of the contract we can actually<00:08:57.440> claim<00:08:57.720> a<00:08:57.839> token<00:08:58.440> now 00:09:01.630 --> 00:09:01.640 align:start position:0% 00:09:01.640 --> 00:09:04.030 align:start position:0% and<00:09:02.040> we<00:09:02.160> we<00:09:02.279> send<00:09:02.480> the 00:09:04.030 --> 00:09:04.040 align:start position:0% and we we send the 00:09:04.040 --> 00:09:05.870 align:start position:0% and we we send the transaction<00:09:05.040> so<00:09:05.240> the<00:09:05.360> transaction<00:09:05.760> is 00:09:05.870 --> 00:09:05.880 align:start position:0% transaction so the transaction is 00:09:05.880 --> 00:09:08.870 align:start position:0% transaction so the transaction is successful<00:09:06.800> now<00:09:06.959> we<00:09:07.040> can<00:09:07.440> go<00:09:07.640> back<00:09:07.880> and<00:09:08.079> and 00:09:08.870 --> 00:09:08.880 align:start position:0% successful now we can go back and and 00:09:08.880 --> 00:09:10.710 align:start position:0% successful now we can go back and and use<00:09:09.000> a<00:09:09.200> different<00:09:09.480> method<00:09:09.839> and<00:09:10.079> we<00:09:10.160> can<00:09:10.360> check 00:09:10.710 --> 00:09:10.720 align:start position:0% use a different method and we can check 00:09:10.720 --> 00:09:12.509 align:start position:0% use a different method and we can check the<00:09:11.000> the<00:09:11.360> the<00:09:11.480> balances<00:09:11.880> for<00:09:12.040> example<00:09:12.320> of<00:09:12.399> the 00:09:12.509 --> 00:09:12.519 align:start position:0% the the the balances for example of the 00:09:12.519 --> 00:09:15.310 align:start position:0% the the the balances for example of the contract<00:09:13.480> and<00:09:13.600> we<00:09:13.720> can<00:09:13.880> see<00:09:14.240> that<00:09:14.640> um<00:09:15.079> we 00:09:15.310 --> 00:09:15.320 align:start position:0% contract and we can see that um we 00:09:15.320 --> 00:09:19.870 align:start position:0% contract and we can see that um we actually<00:09:16.079> do<00:09:16.320> have<00:09:16.800> 100<00:09:17.440> um<00:09:18.079> discount<00:09:18.480> tokens 00:09:19.870 --> 00:09:19.880 align:start position:0% actually do have 100 um discount tokens 00:09:19.880 --> 00:09:22.269 align:start position:0% actually do have 100 um discount tokens now<00:09:20.880> so<00:09:21.240> this<00:09:21.360> is<00:09:21.480> a<00:09:21.640> process<00:09:21.880> that<00:09:22.040> can 00:09:22.269 --> 00:09:22.279 align:start position:0% now so this is a process that can 00:09:22.279 --> 00:09:25.750 align:start position:0% now so this is a process that can continue<00:09:23.079> you<00:09:23.200> can<00:09:23.720> go<00:09:24.440> uh<00:09:25.000> somewhere<00:09:25.360> else 00:09:25.750 --> 00:09:25.760 align:start position:0% continue you can go uh somewhere else 00:09:25.760 --> 00:09:27.990 align:start position:0% continue you can go uh somewhere else right<00:09:26.680> this<00:09:26.839> building<00:09:27.240> which<00:09:27.360> is<00:09:27.560> very<00:09:27.760> close 00:09:27.990 --> 00:09:28.000 align:start position:0% right this building which is very close 00:09:28.000 --> 00:09:29.829 align:start position:0% right this building which is very close to<00:09:28.079> the<00:09:28.160> brandur<00:09:28.680> gate<00:09:29.079> and<00:09:29.360> employ<00:09:29.640> at 00:09:29.829 --> 00:09:29.839 align:start position:0% to the brandur gate and employ at 00:09:29.839 --> 00:09:32.190 align:start position:0% to the brandur gate and employ at another<00:09:30.120> contract<00:09:30.560> we<00:09:30.680> can<00:09:30.880> just<00:09:31.040> call<00:09:31.200> it<00:09:31.720> the 00:09:32.190 --> 00:09:32.200 align:start position:0% another contract we can just call it the 00:09:32.200 --> 00:09:34.190 align:start position:0% another contract we can just call it the bundes<00:09:32.839> contract<00:09:33.279> because<00:09:33.519> it's<00:09:33.839> right<00:09:34.040> next 00:09:34.190 --> 00:09:34.200 align:start position:0% bundes contract because it's right next 00:09:34.200 --> 00:09:38.190 align:start position:0% bundes contract because it's right next to<00:09:34.360> the<00:09:34.440> bundes<00:09:35.000> building<00:09:35.399> in<00:09:35.880> um<00:09:36.720> in<00:09:37.200> Berlin 00:09:38.190 --> 00:09:38.200 align:start position:0% to the bundes building in um in Berlin 00:09:38.200 --> 00:09:41.430 align:start position:0% to the bundes building in um in Berlin and<00:09:38.640> uh<00:09:39.480> if<00:09:39.600> you<00:09:39.760> go<00:09:40.000> to<00:09:40.760> search<00:09:41.079> for<00:09:41.240> more 00:09:41.430 --> 00:09:41.440 align:start position:0% and uh if you go to search for more 00:09:41.440 --> 00:09:44.230 align:start position:0% and uh if you go to search for more contract<00:09:41.839> around<00:09:42.160> you<00:09:42.279> can<00:09:42.880> uh 00:09:44.230 --> 00:09:44.240 align:start position:0% contract around you can uh 00:09:44.240 --> 00:09:50.110 align:start position:0% contract around you can uh still<00:09:45.240> uh<00:09:45.440> see<00:09:46.360> once<00:09:46.720> the<00:09:47.600> uh<00:09:48.000> contact<00:09:48.480> with<00:09:49.120> uh 00:09:50.110 --> 00:09:50.120 align:start position:0% still uh see once the uh contact with uh 00:09:50.120 --> 00:09:53.590 align:start position:0% still uh see once the uh contact with uh Google<00:09:50.440> is<00:09:51.079> established<00:09:52.079> that<00:09:52.519> you<00:09:52.720> have<00:09:53.120> both 00:09:53.590 --> 00:09:53.600 align:start position:0% Google is established that you have both 00:09:53.600 --> 00:09:54.829 align:start position:0% Google is established that you have both uh<00:09:53.760> contracts<00:09:54.200> there<00:09:54.320> and<00:09:54.440> you<00:09:54.519> can<00:09:54.640> check 00:09:54.829 --> 00:09:54.839 align:start position:0% uh contracts there and you can check 00:09:54.839 --> 00:09:58.310 align:start position:0% uh contracts there and you can check their 00:09:58.310 --> 00:09:58.320 align:start position:0% 00:09:58.320 --> 00:10:01.389 align:start position:0% names 00:10:01.389 --> 00:10:01.399 align:start position:0% 00:10:01.399 --> 00:10:04.310 align:start position:0% um<00:10:02.399> there<00:10:02.519> is<00:10:03.320> yeah<00:10:03.519> so<00:10:03.839> this<00:10:04.000> this<00:10:04.120> whole 00:10:04.310 --> 00:10:04.320 align:start position:0% um there is yeah so this this whole 00:10:04.320 --> 00:10:06.550 align:start position:0% um there is yeah so this this whole process<00:10:04.640> is<00:10:04.839> can<00:10:05.040> continue<00:10:05.680> so<00:10:05.880> this<00:10:06.000> is<00:10:06.200> still 00:10:06.550 --> 00:10:06.560 align:start position:0% process is can continue so this is still 00:10:06.560 --> 00:10:09.269 align:start position:0% process is can continue so this is still another<00:10:06.880> location<00:10:07.480> in<00:10:07.600> in<00:10:07.839> Berlin<00:10:08.839> um<00:10:09.040> this<00:10:09.160> is 00:10:09.269 --> 00:10:09.279 align:start position:0% another location in in Berlin um this is 00:10:09.279 --> 00:10:12.269 align:start position:0% another location in in Berlin um this is Alexander<00:10:09.720> PLS<00:10:10.680> you<00:10:10.800> can<00:10:11.240> just<00:10:11.839> put<00:10:12.040> more 00:10:12.269 --> 00:10:12.279 align:start position:0% Alexander PLS you can just put more 00:10:12.279 --> 00:10:13.509 align:start position:0% Alexander PLS you can just put more contracts<00:10:12.680> here<00:10:12.839> with<00:10:13.000> with<00:10:13.200> different 00:10:13.509 --> 00:10:13.519 align:start position:0% contracts here with with different 00:10:13.519 --> 00:10:17.350 align:start position:0% contracts here with with different parameters<00:10:14.240> uh<00:10:14.480> different<00:10:15.120> uh<00:10:15.959> uh<00:10:16.360> questions 00:10:17.350 --> 00:10:17.360 align:start position:0% parameters uh different uh uh questions 00:10:17.360 --> 00:10:19.710 align:start position:0% parameters uh different uh uh questions uh<00:10:17.519> and<00:10:17.760> the<00:10:17.880> whole<00:10:18.200> point<00:10:18.399> of<00:10:18.560> this<00:10:18.760> is<00:10:18.959> that 00:10:19.710 --> 00:10:19.720 align:start position:0% uh and the whole point of this is that 00:10:19.720 --> 00:10:22.509 align:start position:0% uh and the whole point of this is that it<00:10:19.800> would<00:10:19.959> be<00:10:20.120> nice<00:10:20.360> if<00:10:20.560> in<00:10:20.720> every<00:10:21.000> city<00:10:21.720> um<00:10:22.200> we 00:10:22.509 --> 00:10:22.519 align:start position:0% it would be nice if in every city um we 00:10:22.519 --> 00:10:25.190 align:start position:0% it would be nice if in every city um we we<00:10:22.720> we<00:10:22.839> started<00:10:23.160> seeing<00:10:23.560> Maps<00:10:24.000> like<00:10:24.440> like<00:10:24.760> this 00:10:25.190 --> 00:10:25.200 align:start position:0% we we started seeing Maps like like this 00:10:25.200 --> 00:10:27.670 align:start position:0% we we started seeing Maps like like this that<00:10:25.519> essentially<00:10:26.320> are<00:10:26.519> full<00:10:26.760> of<00:10:27.200> ethereum 00:10:27.670 --> 00:10:27.680 align:start position:0% that essentially are full of ethereum 00:10:27.680 --> 00:10:29.430 align:start position:0% that essentially are full of ethereum hexagons<00:10:28.279> or<00:10:28.480> pyramids<00:10:29.000> however<00:10:29.120> you<00:10:29.200> would 00:10:29.430 --> 00:10:29.440 align:start position:0% hexagons or pyramids however you would 00:10:29.440 --> 00:10:31.870 align:start position:0% hexagons or pyramids however you would want<00:10:29.600> to<00:10:29.720> call<00:10:29.880> it<00:10:30.680> and<00:10:31.120> where<00:10:31.320> people<00:10:31.680> can 00:10:31.870 --> 00:10:31.880 align:start position:0% want to call it and where people can 00:10:31.880 --> 00:10:34.190 align:start position:0% want to call it and where people can have<00:10:32.040> fun<00:10:32.200> and<00:10:32.399> interact<00:10:32.880> with<00:10:33.279> um<00:10:33.800> ethereum 00:10:34.190 --> 00:10:34.200 align:start position:0% have fun and interact with um ethereum 00:10:34.200 --> 00:10:36.310 align:start position:0% have fun and interact with um ethereum smart<00:10:34.440> contracts<00:10:34.800> all<00:10:34.959> around 00:10:36.310 --> 00:10:36.320 align:start position:0% smart contracts all around 00:10:36.320 --> 00:10:43.389 align:start position:0% smart contracts all around them<00:10:37.320> uh<00:10:37.480> so<00:10:37.800> that's<00:10:38.040> the 00:10:43.389 --> 00:10:43.399 align:start position:0% 00:10:43.399 --> 00:10:46.500 align:start position:0% video<00:10:44.399> um<00:10:44.720> so 00:10:46.500 --> 00:10:46.510 align:start position:0% video um so 00:10:46.510 --> 00:10:49.750 align:start position:0% video um so [Music] 00:10:49.750 --> 00:10:49.760 align:start position:0% 00:10:49.760 --> 00:10:53.190 align:start position:0% for<00:10:50.760> thank<00:10:51.040> you<00:10:52.040> thank 00:10:53.190 --> 00:10:53.200 align:start position:0% for thank you thank 00:10:53.200 --> 00:10:56.389 align:start position:0% for thank you thank you<00:10:54.200> um<00:10:54.519> so<00:10:54.760> for<00:10:55.279> this<00:10:55.480> this<00:10:55.600> is<00:10:55.959> like<00:10:56.079> a<00:10:56.200> very 00:10:56.389 --> 00:10:56.399 align:start position:0% you um so for this this is like a very 00:10:56.399 --> 00:11:00.269 align:start position:0% you um so for this this is like a very very<00:10:56.600> early<00:10:57.079> prototype<00:10:58.079> uh<00:10:58.880> for<00:10:59.440> to<00:10:59.600> be<00:11:00.000> really 00:11:00.269 --> 00:11:00.279 align:start position:0% very early prototype uh for to be really 00:11:00.279 --> 00:11:03.910 align:start position:0% very early prototype uh for to be really really<00:11:00.880> um<00:11:01.720> uh<00:11:02.680> a<00:11:02.800> workable<00:11:03.200> application<00:11:03.800> we 00:11:03.910 --> 00:11:03.920 align:start position:0% really um uh a workable application we 00:11:03.920 --> 00:11:05.670 align:start position:0% really um uh a workable application we have<00:11:04.040> to<00:11:04.160> integrate<00:11:04.480> with<00:11:04.600> the<00:11:04.680> light<00:11:04.920> client 00:11:05.670 --> 00:11:05.680 align:start position:0% have to integrate with the light client 00:11:05.680 --> 00:11:08.269 align:start position:0% have to integrate with the light client and<00:11:06.040> from<00:11:06.360> what<00:11:06.680> we<00:11:06.800> saw<00:11:07.000> today<00:11:07.480> that's<00:11:08.079> very 00:11:08.269 --> 00:11:08.279 align:start position:0% and from what we saw today that's very 00:11:08.279 --> 00:11:10.829 align:start position:0% and from what we saw today that's very close<00:11:08.560> and<00:11:08.720> I'm<00:11:08.880> very<00:11:09.079> very<00:11:09.440> excited<00:11:10.440> uh<00:11:10.600> do 00:11:10.829 --> 00:11:10.839 align:start position:0% close and I'm very very excited uh do 00:11:10.839 --> 00:11:12.389 align:start position:0% close and I'm very very excited uh do publish<00:11:11.120> the<00:11:11.200> mobile<00:11:11.480> app<00:11:11.639> in<00:11:11.760> the<00:11:11.839> Android 00:11:12.389 --> 00:11:12.399 align:start position:0% publish the mobile app in the Android 00:11:12.399 --> 00:11:15.790 align:start position:0% publish the mobile app in the Android store<00:11:13.399> um<00:11:14.079> improve<00:11:14.480> the<00:11:14.639> proof<00:11:14.839> of<00:11:15.000> presence 00:11:15.790 --> 00:11:15.800 align:start position:0% store um improve the proof of presence 00:11:15.800 --> 00:11:19.430 align:start position:0% store um improve the proof of presence um<00:11:16.639> algorithm<00:11:17.160> with<00:11:17.600> um<00:11:17.880> the<00:11:18.000> methods<00:11:18.720> that<00:11:18.839> I 00:11:19.430 --> 00:11:19.440 align:start position:0% um algorithm with um the methods that I 00:11:19.440 --> 00:11:21.750 align:start position:0% um algorithm with um the methods that I explained<00:11:20.440> um<00:11:20.680> and<00:11:20.920> probably<00:11:21.200> integrate<00:11:21.600> with 00:11:21.750 --> 00:11:21.760 align:start position:0% explained um and probably integrate with 00:11:21.760 --> 00:11:23.710 align:start position:0% explained um and probably integrate with an<00:11:22.360> uh<00:11:22.639> existing<00:11:22.959> wallet<00:11:23.279> for<00:11:23.440> account 00:11:23.710 --> 00:11:23.720 align:start position:0% an uh existing wallet for account 00:11:23.720 --> 00:11:25.030 align:start position:0% an uh existing wallet for account management<00:11:24.200> since<00:11:24.440> this<00:11:24.560> is<00:11:24.680> not<00:11:24.839> something 00:11:25.030 --> 00:11:25.040 align:start position:0% management since this is not something 00:11:25.040 --> 00:11:28.069 align:start position:0% management since this is not something that<00:11:25.160> I<00:11:25.240> would<00:11:25.360> like<00:11:25.519> to<00:11:25.800> do<00:11:26.800> uh<00:11:27.000> myself<00:11:27.720> and 00:11:28.069 --> 00:11:28.079 align:start position:0% that I would like to do uh myself and 00:11:28.079 --> 00:11:31.150 align:start position:0% that I would like to do uh myself and also<00:11:28.720> integrate<00:11:29.120> with<00:11:29.320> an<00:11:29.440> existing<00:11:29.800> identity 00:11:31.150 --> 00:11:31.160 align:start position:0% also integrate with an existing identity 00:11:31.160 --> 00:11:34.150 align:start position:0% also integrate with an existing identity system<00:11:32.160> so<00:11:32.399> yeah<00:11:32.639> that's<00:11:32.839> my<00:11:33.000> 10-minute<00:11:33.519> talk 00:11:34.150 --> 00:11:34.160 align:start position:0% system so yeah that's my 10-minute talk 00:11:34.160 --> 00:11:35.990 align:start position:0% system so yeah that's my 10-minute talk um<00:11:34.920> if<00:11:35.040> you<00:11:35.120> want<00:11:35.279> more<00:11:35.440> updates<00:11:35.760> you<00:11:35.880> can 00:11:35.990 --> 00:11:36.000 align:start position:0% um if you want more updates you can 00:11:36.000 --> 00:11:38.030 align:start position:0% um if you want more updates you can follow<00:11:36.240> me<00:11:36.399> on<00:11:36.600> Twitter<00:11:37.040> or<00:11:37.320> on 00:11:38.030 --> 00:11:38.040 align:start position:0% follow me on Twitter or on 00:11:38.040 --> 00:11:40.990 align:start position:0% follow me on Twitter or on GitHub<00:11:39.040> uh<00:11:39.200> and<00:11:39.839> the<00:11:39.959> website<00:11:40.320> for<00:11:40.440> sorka<00:11:40.920> is 00:11:40.990 --> 00:11:41.000 align:start position:0% GitHub uh and the website for sorka is 00:11:41.000 --> 00:11:42.430 align:start position:0% GitHub uh and the website for sorka is coming<00:11:41.240> soon<00:11:41.519> I<00:11:41.639> just<00:11:41.760> didn't<00:11:42.000> have<00:11:42.120> the<00:11:42.279> time 00:11:42.430 --> 00:11:42.440 align:start position:0% coming soon I just didn't have the time 00:11:42.440 --> 00:11:45.710 align:start position:0% coming soon I just didn't have the time to<00:11:42.639> to<00:11:42.800> make<00:11:42.959> it<00:11:43.519> so<00:11:43.839> yeah<00:11:44.120> that's<00:11:44.440> that's<00:11:44.720> all 00:11:45.710 --> 00:11:45.720 align:start position:0% to to make it so yeah that's that's all 00:11:45.720 --> 00:11:47.320 align:start position:0% to to make it so yeah that's that's all thank<00:11:45.880> you<00:11:46.000> very<00:11:46.120> much<00:11:46.360> thank<00:11:46.480> you 00:11:47.320 --> 00:11:47.330 align:start position:0% thank you very much thank you 00:11:47.330 --> 00:11:49.389 align:start position:0% thank you very much thank you [Music] 00:11:49.389 --> 00:11:49.399 align:start position:0% [Music] 00:11:49.399 --> 00:11:53.440 align:start position:0% [Music] lus<00:11:50.399> thank<00:11:50.560> you<00:11:50.760> very<00:11:51.000> much