WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:12.070 align:start position:0% [Music] 00:00:12.070 --> 00:00:12.080 align:start position:0% 00:00:12.080 --> 00:00:15.350 align:start position:0% this<00:00:13.080> is<00:00:13.139> a<00:00:13.320> workshop<00:00:13.740> will<00:00:14.040> be 00:00:15.350 --> 00:00:15.360 align:start position:0% this is a workshop will be 00:00:15.360 --> 00:00:17.990 align:start position:0% this is a workshop will be talking<00:00:15.900> about<00:00:16.260> using<00:00:16.859> agent-based<00:00:17.580> models 00:00:17.990 --> 00:00:18.000 align:start position:0% talking about using agent-based models 00:00:18.000 --> 00:00:21.290 align:start position:0% talking about using agent-based models for<00:00:18.480> analyzing<00:00:19.140> D5<00:00:19.500> protocol<00:00:20.180> and<00:00:21.180> the 00:00:21.290 --> 00:00:21.300 align:start position:0% for analyzing D5 protocol and the 00:00:21.300 --> 00:00:23.570 align:start position:0% for analyzing D5 protocol and the examples<00:00:21.840> will<00:00:22.140> be<00:00:22.320> we'll<00:00:22.740> be<00:00:22.920> using<00:00:23.279> is 00:00:23.570 --> 00:00:23.580 align:start position:0% examples will be we'll be using is 00:00:23.580 --> 00:00:25.990 align:start position:0% examples will be we'll be using is through<00:00:23.820> the<00:00:24.060> Vega<00:00:24.420> Market<00:00:24.600> simulator 00:00:25.990 --> 00:00:26.000 align:start position:0% through the Vega Market simulator 00:00:26.000 --> 00:00:28.550 align:start position:0% through the Vega Market simulator we<00:00:27.000> do<00:00:27.180> a<00:00:27.300> quick<00:00:27.480> introduction<00:00:27.960> and<00:00:28.260> then<00:00:28.380> I'm 00:00:28.550 --> 00:00:28.560 align:start position:0% we do a quick introduction and then I'm 00:00:28.560 --> 00:00:30.769 align:start position:0% we do a quick introduction and then I'm going<00:00:28.740> to<00:00:28.859> jump<00:00:29.279> to<00:00:29.699> a<00:00:29.820> slide<00:00:30.119> which<00:00:30.300> will<00:00:30.480> show 00:00:30.769 --> 00:00:30.779 align:start position:0% going to jump to a slide which will show 00:00:30.779 --> 00:00:32.210 align:start position:0% going to jump to a slide which will show you 00:00:32.210 --> 00:00:32.220 align:start position:0% you 00:00:32.220 --> 00:00:34.250 align:start position:0% you where<00:00:32.759> to<00:00:33.000> go<00:00:33.120> on<00:00:33.239> GitHub<00:00:33.600> so<00:00:33.840> that<00:00:34.020> you<00:00:34.140> can 00:00:34.250 --> 00:00:34.260 align:start position:0% where to go on GitHub so that you can 00:00:34.260 --> 00:00:36.410 align:start position:0% where to go on GitHub so that you can hack<00:00:34.440> along<00:00:34.680> I<00:00:35.219> really<00:00:35.460> assuming<00:00:36.120> it's<00:00:36.239> a 00:00:36.410 --> 00:00:36.420 align:start position:0% hack along I really assuming it's a 00:00:36.420 --> 00:00:37.790 align:start position:0% hack along I really assuming it's a workshop<00:00:36.719> right<00:00:36.899> so<00:00:37.140> I'm<00:00:37.260> expecting<00:00:37.620> everyone 00:00:37.790 --> 00:00:37.800 align:start position:0% workshop right so I'm expecting everyone 00:00:37.800 --> 00:00:40.250 align:start position:0% workshop right so I'm expecting everyone to<00:00:38.160> have<00:00:38.280> a<00:00:38.460> computer<00:00:38.579> in<00:00:38.940> front<00:00:39.120> of<00:00:39.239> them<00:00:39.840> and 00:00:40.250 --> 00:00:40.260 align:start position:0% to have a computer in front of them and 00:00:40.260 --> 00:00:43.729 align:start position:0% to have a computer in front of them and start<00:00:40.500> hacking<00:00:40.980> but<00:00:41.820> if<00:00:42.000> not<00:00:42.180> then<00:00:42.719> hey<00:00:43.440> you 00:00:43.729 --> 00:00:43.739 align:start position:0% start hacking but if not then hey you 00:00:43.739 --> 00:00:45.889 align:start position:0% start hacking but if not then hey you know<00:00:44.280> you<00:00:44.760> can<00:00:44.820> just<00:00:45.000> stay<00:00:45.180> along<00:00:45.420> for<00:00:45.719> the 00:00:45.889 --> 00:00:45.899 align:start position:0% know you can just stay along for the 00:00:45.899 --> 00:00:49.130 align:start position:0% know you can just stay along for the chit<00:00:46.140> chat<00:00:46.500> so 00:00:49.130 --> 00:00:49.140 align:start position:0% chit chat so 00:00:49.140 --> 00:00:51.889 align:start position:0% chit chat so my<00:00:49.559> name<00:00:49.680> is<00:00:49.800> David<00:00:49.980> I've<00:00:50.760> been<00:00:50.940> with<00:00:51.059> Vega<00:00:51.600> for 00:00:51.889 --> 00:00:51.899 align:start position:0% my name is David I've been with Vega for 00:00:51.899 --> 00:00:55.729 align:start position:0% my name is David I've been with Vega for the<00:00:52.200> last<00:00:52.440> four<00:00:53.399> years<00:00:53.640> I<00:00:54.480> mainly<00:00:54.960> look<00:00:55.140> after 00:00:55.729 --> 00:00:55.739 align:start position:0% the last four years I mainly look after 00:00:55.739 --> 00:00:57.290 align:start position:0% the last four years I mainly look after the 00:00:57.290 --> 00:00:57.300 align:start position:0% the 00:00:57.300 --> 00:01:00.590 align:start position:0% the kind<00:00:57.899> of<00:00:58.079> Financial<00:00:58.860> Risk<00:00:59.579> and<00:00:59.940> economic 00:01:00.590 --> 00:01:00.600 align:start position:0% kind of Financial Risk and economic 00:01:00.600 --> 00:01:03.590 align:start position:0% kind of Financial Risk and economic design<00:01:00.899> game<00:01:01.320> theory<00:01:01.739> analysis<00:01:02.420> and<00:01:03.420> together 00:01:03.590 --> 00:01:03.600 align:start position:0% design game theory analysis and together 00:01:03.600 --> 00:01:06.350 align:start position:0% design game theory analysis and together with<00:01:03.960> me<00:01:04.199> is<00:01:04.920> Tom<00:01:05.220> who<00:01:05.760> is<00:01:05.880> coming<00:01:06.000> from 00:01:06.350 --> 00:01:06.360 align:start position:0% with me is Tom who is coming from 00:01:06.360 --> 00:01:08.630 align:start position:0% with me is Tom who is coming from traditional<00:01:06.840> Finance<00:01:07.320> he's<00:01:07.619> a<00:01:08.100> Quant<00:01:08.400> with 00:01:08.630 --> 00:01:08.640 align:start position:0% traditional Finance he's a Quant with 00:01:08.640 --> 00:01:11.390 align:start position:0% traditional Finance he's a Quant with Vega<00:01:09.000> help<00:01:09.119> working<00:01:09.720> on<00:01:10.020> the<00:01:10.260> working<00:01:10.979> on<00:01:11.280> the 00:01:11.390 --> 00:01:11.400 align:start position:0% Vega help working on the working on the 00:01:11.400 --> 00:01:13.550 align:start position:0% Vega help working on the working on the research<00:01:11.760> team<00:01:12.000> and<00:01:12.900> one<00:01:13.140> of<00:01:13.260> the<00:01:13.380> speakers 00:01:13.550 --> 00:01:13.560 align:start position:0% research team and one of the speakers 00:01:13.560 --> 00:01:16.070 align:start position:0% research team and one of the speakers Mark<00:01:13.979> isn't<00:01:14.460> isn't<00:01:14.760> here<00:01:14.939> but<00:01:15.299> he's<00:01:15.600> done<00:01:15.840> a 00:01:16.070 --> 00:01:16.080 align:start position:0% Mark isn't isn't here but he's done a 00:01:16.080 --> 00:01:18.530 align:start position:0% Mark isn't isn't here but he's done a lot<00:01:16.200> of<00:01:16.320> the<00:01:16.619> a<00:01:17.040> lot<00:01:17.220> of<00:01:17.340> the<00:01:17.460> RL<00:01:17.820> stuff<00:01:18.119> so<00:01:18.299> he's 00:01:18.530 --> 00:01:18.540 align:start position:0% lot of the a lot of the RL stuff so he's 00:01:18.540 --> 00:01:20.690 align:start position:0% lot of the a lot of the RL stuff so he's the<00:01:18.840> main<00:01:18.960> brain<00:01:19.260> behind<00:01:19.560> that 00:01:20.690 --> 00:01:20.700 align:start position:0% the main brain behind that 00:01:20.700 --> 00:01:28.249 align:start position:0% the main brain behind that so<00:01:21.299> I'm<00:01:21.540> going<00:01:21.840> to<00:01:22.080> jump<00:01:22.500> to 00:01:28.249 --> 00:01:28.259 align:start position:0% 00:01:28.259 --> 00:01:32.830 align:start position:0% I<00:01:28.799> think<00:01:28.920> here 00:01:32.830 --> 00:01:32.840 align:start position:0% 00:01:32.840 --> 00:01:35.870 align:start position:0% so<00:01:33.860> yeah<00:01:34.860> we'll<00:01:34.979> go<00:01:35.159> back<00:01:35.280> to<00:01:35.400> introducing 00:01:35.870 --> 00:01:35.880 align:start position:0% so yeah we'll go back to introducing 00:01:35.880 --> 00:01:39.109 align:start position:0% so yeah we'll go back to introducing what<00:01:36.060> Vega<00:01:36.540> is<00:01:36.659> in<00:01:37.200> a<00:01:37.320> minute<00:01:37.439> but<00:01:37.740> given<00:01:38.579> I 00:01:39.109 --> 00:01:39.119 align:start position:0% what Vega is in a minute but given I 00:01:39.119 --> 00:01:40.310 align:start position:0% what Vega is in a minute but given I don't<00:01:39.240> know<00:01:39.360> how<00:01:39.420> fast<00:01:39.600> the<00:01:39.780> Wi-Fi<00:01:40.020> is<00:01:40.140> going 00:01:40.310 --> 00:01:40.320 align:start position:0% don't know how fast the Wi-Fi is going 00:01:40.320 --> 00:01:41.330 align:start position:0% don't know how fast the Wi-Fi is going to<00:01:40.380> be<00:01:40.439> in<00:01:40.560> here 00:01:41.330 --> 00:01:41.340 align:start position:0% to be in here 00:01:41.340 --> 00:01:43.789 align:start position:0% to be in here um<00:01:41.460> just<00:01:41.640> running<00:01:41.820> through<00:01:42.060> a<00:01:42.299> few<00:01:42.799> firsts 00:01:43.789 --> 00:01:43.799 align:start position:0% um just running through a few firsts 00:01:43.799 --> 00:01:46.789 align:start position:0% um just running through a few firsts that<00:01:44.100> set<00:01:44.520> up<00:01:44.700> steps<00:01:45.119> that<00:01:45.299> we<00:01:45.540> can<00:01:45.720> get<00:01:46.619> going 00:01:46.789 --> 00:01:46.799 align:start position:0% that set up steps that we can get going 00:01:46.799 --> 00:01:48.590 align:start position:0% that set up steps that we can get going with<00:01:46.979> while<00:01:47.220> we're<00:01:47.460> presenting<00:01:48.060> uh<00:01:48.479> for 00:01:48.590 --> 00:01:48.600 align:start position:0% with while we're presenting uh for 00:01:48.600 --> 00:01:50.149 align:start position:0% with while we're presenting uh for anyone<00:01:48.840> who<00:01:48.960> hasn't<00:01:49.200> noticed<00:01:49.380> there<00:01:49.560> is<00:01:49.740> Wi-Fi 00:01:50.149 --> 00:01:50.159 align:start position:0% anyone who hasn't noticed there is Wi-Fi 00:01:50.159 --> 00:01:52.910 align:start position:0% anyone who hasn't noticed there is Wi-Fi specifically<00:01:50.939> for<00:01:51.180> the<00:01:51.360> workshops<00:01:51.899> uh<00:01:52.740> called 00:01:52.910 --> 00:01:52.920 align:start position:0% specifically for the workshops uh called 00:01:52.920 --> 00:01:55.069 align:start position:0% specifically for the workshops uh called Defcon<00:01:53.460> workshop<00:01:53.880> and<00:01:54.119> the<00:01:54.299> password<00:01:54.360> is<00:01:54.720> was 00:01:55.069 --> 00:01:55.079 align:start position:0% Defcon workshop and the password is was 00:01:55.079 --> 00:01:57.830 align:start position:0% Defcon workshop and the password is was it<00:01:55.320> built<00:01:55.680> build<00:01:56.040> it<00:01:56.280> 22. 00:01:57.830 --> 00:01:57.840 align:start position:0% it built build it 22. 00:01:57.840 --> 00:01:59.630 align:start position:0% it built build it 22. so 00:01:59.630 --> 00:01:59.640 align:start position:0% so 00:01:59.640 --> 00:02:01.910 align:start position:0% so give<00:02:00.060> that<00:02:00.240> a<00:02:00.299> go<00:02:00.420> if<00:02:00.479> the<00:02:00.600> Wi-Fi's<00:02:00.960> being<00:02:01.079> slow 00:02:01.910 --> 00:02:01.920 align:start position:0% give that a go if the Wi-Fi's being slow 00:02:01.920 --> 00:02:06.050 align:start position:0% give that a go if the Wi-Fi's being slow uh<00:02:02.640> so<00:02:03.000> this<00:02:03.659> uh<00:02:04.439> repo<00:02:04.920> at<00:02:05.340> the<00:02:05.460> top<00:02:05.520> here<00:02:05.700> Vega 00:02:06.050 --> 00:02:06.060 align:start position:0% uh so this uh repo at the top here Vega 00:02:06.060 --> 00:02:08.570 align:start position:0% uh so this uh repo at the top here Vega Market<00:02:06.180> Sim<00:02:06.420> should<00:02:06.899> be<00:02:07.079> open<00:02:07.560> if<00:02:08.160> you<00:02:08.280> go<00:02:08.399> over 00:02:08.570 --> 00:02:08.580 align:start position:0% Market Sim should be open if you go over 00:02:08.580 --> 00:02:10.370 align:start position:0% Market Sim should be open if you go over there<00:02:08.819> clone<00:02:09.539> that 00:02:10.370 --> 00:02:10.380 align:start position:0% there clone that 00:02:10.380 --> 00:02:12.830 align:start position:0% there clone that that's<00:02:10.860> your<00:02:11.160> your<00:02:11.340> first<00:02:11.580> step<00:02:11.819> you're<00:02:12.599> also 00:02:12.830 --> 00:02:12.840 align:start position:0% that's your your first step you're also 00:02:12.840 --> 00:02:16.250 align:start position:0% that's your your first step you're also going<00:02:12.959> to<00:02:13.080> need<00:02:13.200> go<00:02:14.000> uh<00:02:15.000> 19<00:02:15.239> I<00:02:15.660> think<00:02:15.840> it's 00:02:16.250 --> 00:02:16.260 align:start position:0% going to need go uh 19 I think it's 00:02:16.260 --> 00:02:19.910 align:start position:0% going to need go uh 19 I think it's necessary<00:02:16.819> python<00:02:17.819> ideally<00:02:18.300> 310<00:02:18.840> 39<00:02:19.560> might 00:02:19.910 --> 00:02:19.920 align:start position:0% necessary python ideally 310 39 might 00:02:19.920 --> 00:02:23.270 align:start position:0% necessary python ideally 310 39 might work<00:02:20.160> and<00:02:21.060> poetry<00:02:21.720> just<00:02:22.260> because<00:02:22.440> it's 00:02:23.270 --> 00:02:23.280 align:start position:0% work and poetry just because it's 00:02:23.280 --> 00:02:26.270 align:start position:0% work and poetry just because it's probably<00:02:24.180> the<00:02:24.480> better<00:02:24.660> uh<00:02:25.500> package<00:02:25.800> manager 00:02:26.270 --> 00:02:26.280 align:start position:0% probably the better uh package manager 00:02:26.280 --> 00:02:28.270 align:start position:0% probably the better uh package manager probably<00:02:26.879> there's<00:02:27.360> a 00:02:28.270 --> 00:02:28.280 align:start position:0% probably there's a 00:02:28.280 --> 00:02:29.990 align:start position:0% probably there's a requirements.txt<00:02:29.280> if<00:02:29.580> you<00:02:29.700> just<00:02:29.760> need<00:02:29.879> that 00:02:29.990 --> 00:02:30.000 align:start position:0% requirements.txt if you just need that 00:02:30.000 --> 00:02:31.610 align:start position:0% requirements.txt if you just need that as<00:02:30.120> well<00:02:30.300> we<00:02:30.720> can<00:02:30.959> go<00:02:31.260> through<00:02:31.440> actually 00:02:31.610 --> 00:02:31.620 align:start position:0% as well we can go through actually 00:02:31.620 --> 00:02:33.350 align:start position:0% as well we can go through actually setting<00:02:32.040> it<00:02:32.160> up<00:02:32.220> in<00:02:32.640> a<00:02:32.760> bit 00:02:33.350 --> 00:02:33.360 align:start position:0% setting it up in a bit 00:02:33.360 --> 00:02:36.410 align:start position:0% setting it up in a bit uh<00:02:34.080> then<00:02:34.260> if<00:02:34.500> you<00:02:34.620> want<00:02:35.040> to<00:02:35.160> be<00:02:35.580> able<00:02:35.700> to<00:02:35.819> view 00:02:36.410 --> 00:02:36.420 align:start position:0% uh then if you want to be able to view 00:02:36.420 --> 00:02:39.229 align:start position:0% uh then if you want to be able to view our<00:02:37.080> sort<00:02:37.500> of<00:02:37.620> front-end<00:02:38.160> console 00:02:39.229 --> 00:02:39.239 align:start position:0% our sort of front-end console 00:02:39.239 --> 00:02:41.150 align:start position:0% our sort of front-end console you'll<00:02:39.720> also<00:02:39.959> need<00:02:40.080> some<00:02:40.260> some<00:02:40.440> UI<00:02:40.800> framework 00:02:41.150 --> 00:02:41.160 align:start position:0% you'll also need some some UI framework 00:02:41.160 --> 00:02:45.770 align:start position:0% you'll also need some some UI framework yarn<00:02:42.000> and<00:02:42.360> NVM<00:02:42.900> for<00:02:43.280> node<00:02:44.280> management<00:02:44.819> and<00:02:45.599> if 00:02:45.770 --> 00:02:45.780 align:start position:0% yarn and NVM for node management and if 00:02:45.780 --> 00:02:48.410 align:start position:0% yarn and NVM for node management and if you<00:02:45.840> want<00:02:45.959> to<00:02:46.080> try<00:02:46.500> some<00:02:46.860> RL<00:02:47.519> at<00:02:47.760> the<00:02:47.940> end<00:02:48.060> then 00:02:48.410 --> 00:02:48.420 align:start position:0% you want to try some RL at the end then 00:02:48.420 --> 00:02:51.290 align:start position:0% you want to try some RL at the end then Pi<00:02:49.140> torch<00:02:49.500> is<00:02:50.099> a<00:02:50.400> good<00:02:50.640> starting<00:02:50.819> point<00:02:51.120> to 00:02:51.290 --> 00:02:51.300 align:start position:0% Pi torch is a good starting point to 00:02:51.300 --> 00:02:53.750 align:start position:0% Pi torch is a good starting point to download<00:02:51.420> so 00:02:53.750 --> 00:02:53.760 align:start position:0% download so 00:02:53.760 --> 00:02:56.690 align:start position:0% download so broadly<00:02:54.360> if<00:02:54.480> everyone<00:02:54.720> can 00:02:56.690 --> 00:02:56.700 align:start position:0% broadly if everyone can 00:02:56.700 --> 00:02:59.150 align:start position:0% broadly if everyone can make<00:02:57.300> a<00:02:57.420> note<00:02:57.540> of<00:02:57.720> that<00:02:57.840> URL<00:02:58.260> before<00:02:58.620> we<00:02:58.920> switch 00:02:59.150 --> 00:02:59.160 align:start position:0% make a note of that URL before we switch 00:02:59.160 --> 00:03:02.390 align:start position:0% make a note of that URL before we switch back<00:02:59.459> and<00:03:00.420> then<00:03:00.720> we<00:03:01.440> will<00:03:01.620> start<00:03:02.040> on<00:03:02.220> actually 00:03:02.390 --> 00:03:02.400 align:start position:0% back and then we will start on actually 00:03:02.400 --> 00:03:06.410 align:start position:0% back and then we will start on actually presenting 00:03:06.410 --> 00:03:06.420 align:start position:0% 00:03:06.420 --> 00:03:14.330 align:start position:0% is<00:03:06.780> everyone<00:03:06.959> good 00:03:14.330 --> 00:03:14.340 align:start position:0% 00:03:14.340 --> 00:03:17.210 align:start position:0% cool 00:03:17.210 --> 00:03:17.220 align:start position:0% 00:03:17.220 --> 00:03:18.890 align:start position:0% we'll<00:03:17.640> have<00:03:17.819> an<00:03:17.940> actual<00:03:18.120> break<00:03:18.239> for<00:03:18.480> setting 00:03:18.890 --> 00:03:18.900 align:start position:0% we'll have an actual break for setting 00:03:18.900 --> 00:03:26.390 align:start position:0% we'll have an actual break for setting everything<00:03:18.959> up<00:03:19.140> in<00:03:19.319> a<00:03:19.379> bit<00:03:19.500> but 00:03:26.390 --> 00:03:26.400 align:start position:0% 00:03:26.400 --> 00:03:28.009 align:start position:0% yeah<00:03:26.640> so<00:03:27.000> we're<00:03:27.180> back<00:03:27.420> to<00:03:27.540> the<00:03:27.659> introduction 00:03:28.009 --> 00:03:28.019 align:start position:0% yeah so we're back to the introduction 00:03:28.019 --> 00:03:31.850 align:start position:0% yeah so we're back to the introduction but<00:03:28.319> it's<00:03:28.500> it's<00:03:28.800> sort<00:03:29.280> of<00:03:29.400> a<00:03:29.580> workshop<00:03:29.940> and 00:03:31.850 --> 00:03:31.860 align:start position:0% but it's it's sort of a workshop and 00:03:31.860 --> 00:03:33.530 align:start position:0% but it's it's sort of a workshop and if<00:03:32.159> you<00:03:32.280> need<00:03:32.459> help<00:03:32.640> the<00:03:32.879> person<00:03:33.060> who<00:03:33.300> isn't 00:03:33.530 --> 00:03:33.540 align:start position:0% if you need help the person who isn't 00:03:33.540 --> 00:03:35.030 align:start position:0% if you need help the person who isn't speaking<00:03:33.840> can<00:03:34.080> actually<00:03:34.260> come<00:03:34.500> and<00:03:34.680> help<00:03:34.920> you 00:03:35.030 --> 00:03:35.040 align:start position:0% speaking can actually come and help you 00:03:35.040 --> 00:03:36.710 align:start position:0% speaking can actually come and help you with<00:03:35.220> your<00:03:35.400> you<00:03:35.640> know<00:03:35.760> whatever<00:03:36.060> it<00:03:36.360> is<00:03:36.480> you're 00:03:36.710 --> 00:03:36.720 align:start position:0% with your you know whatever it is you're 00:03:36.720 --> 00:03:38.990 align:start position:0% with your you know whatever it is you're trying<00:03:36.900> to<00:03:37.140> do<00:03:37.319> within<00:03:38.280> this<00:03:38.459> framework<00:03:38.760> and 00:03:38.990 --> 00:03:39.000 align:start position:0% trying to do within this framework and 00:03:39.000 --> 00:03:40.970 align:start position:0% trying to do within this framework and if<00:03:39.180> you're<00:03:39.599> not<00:03:39.720> having<00:03:39.900> luck<00:03:40.140> then<00:03:40.379> we<00:03:40.620> can 00:03:40.970 --> 00:03:40.980 align:start position:0% if you're not having luck then we can 00:03:40.980 --> 00:03:42.830 align:start position:0% if you're not having luck then we can see<00:03:41.159> if<00:03:41.700> one<00:03:41.879> of<00:03:42.000> us<00:03:42.120> will<00:03:42.239> have<00:03:42.420> better<00:03:42.599> luck 00:03:42.830 --> 00:03:42.840 align:start position:0% see if one of us will have better luck 00:03:42.840 --> 00:03:43.910 align:start position:0% see if one of us will have better luck and<00:03:43.019> there<00:03:43.080> are<00:03:43.200> not<00:03:43.319> so<00:03:43.440> many<00:03:43.500> of<00:03:43.680> us<00:03:43.739> and 00:03:43.910 --> 00:03:43.920 align:start position:0% and there are not so many of us and 00:03:43.920 --> 00:03:46.610 align:start position:0% and there are not so many of us and we've<00:03:44.159> got<00:03:44.280> I<00:03:44.940> think<00:03:45.060> two<00:03:45.299> hours<00:03:45.540> so<00:03:46.260> we've<00:03:46.440> got 00:03:46.610 --> 00:03:46.620 align:start position:0% we've got I think two hours so we've got 00:03:46.620 --> 00:03:47.930 align:start position:0% we've got I think two hours so we've got plenty<00:03:46.980> of<00:03:47.040> time<00:03:47.220> to<00:03:47.459> actually<00:03:47.519> get<00:03:47.760> everyone 00:03:47.930 --> 00:03:47.940 align:start position:0% plenty of time to actually get everyone 00:03:47.940 --> 00:03:50.089 align:start position:0% plenty of time to actually get everyone going<00:03:48.299> and<00:03:48.540> hacking 00:03:50.089 --> 00:03:50.099 align:start position:0% going and hacking 00:03:50.099 --> 00:03:52.850 align:start position:0% going and hacking so<00:03:50.640> in<00:03:50.760> terms<00:03:50.940> of<00:03:51.000> what<00:03:51.180> we'll<00:03:51.420> cover<00:03:51.860> we'll 00:03:52.850 --> 00:03:52.860 align:start position:0% so in terms of what we'll cover we'll 00:03:52.860 --> 00:03:55.729 align:start position:0% so in terms of what we'll cover we'll quickly<00:03:53.220> introduce<00:03:53.580> Vega<00:03:54.060> protocol<00:03:54.500> then<00:03:55.500> I 00:03:55.729 --> 00:03:55.739 align:start position:0% quickly introduce Vega protocol then I 00:03:55.739 --> 00:03:58.250 align:start position:0% quickly introduce Vega protocol then I will<00:03:55.920> try<00:03:56.159> to<00:03:56.340> make<00:03:56.580> sense<00:03:56.819> for<00:03:57.420> agent-based 00:03:58.250 --> 00:03:58.260 align:start position:0% will try to make sense for agent-based 00:03:58.260 --> 00:04:00.729 align:start position:0% will try to make sense for agent-based simulations<00:03:58.680> in<00:03:59.099> in<00:03:59.459> the<00:03:59.819> context<00:04:00.299> of 00:04:00.729 --> 00:04:00.739 align:start position:0% simulations in in the context of 00:04:00.739 --> 00:04:04.250 align:start position:0% simulations in in the context of analyzing<00:04:01.739> D5<00:04:02.159> protocols 00:04:04.250 --> 00:04:04.260 align:start position:0% analyzing D5 protocols 00:04:04.260 --> 00:04:07.250 align:start position:0% analyzing D5 protocols and<00:04:04.739> then<00:04:04.920> you<00:04:05.580> know<00:04:05.640> we<00:04:05.760> will<00:04:05.879> introduce<00:04:06.720> what 00:04:07.250 --> 00:04:07.260 align:start position:0% and then you know we will introduce what 00:04:07.260 --> 00:04:09.050 align:start position:0% and then you know we will introduce what you<00:04:07.680> already<00:04:07.799> started<00:04:08.220> setting<00:04:08.580> up<00:04:08.700> which<00:04:08.940> is 00:04:09.050 --> 00:04:09.060 align:start position:0% you already started setting up which is 00:04:09.060 --> 00:04:10.910 align:start position:0% you already started setting up which is the<00:04:09.180> Vega<00:04:09.599> markets<00:04:09.959> in<00:04:10.140> which<00:04:10.319> is<00:04:10.439> relying<00:04:10.799> on 00:04:10.910 --> 00:04:10.920 align:start position:0% the Vega markets in which is relying on 00:04:10.920 --> 00:04:13.789 align:start position:0% the Vega markets in which is relying on something<00:04:11.159> called<00:04:11.519> vegan<00:04:11.939> all<00:04:12.180> chain<00:04:12.360> will 00:04:13.789 --> 00:04:13.799 align:start position:0% something called vegan all chain will 00:04:13.799 --> 00:04:15.949 align:start position:0% something called vegan all chain will um we'll<00:04:14.400> explain<00:04:14.580> what<00:04:14.939> that<00:04:15.120> is 00:04:15.949 --> 00:04:15.959 align:start position:0% um we'll explain what that is 00:04:15.959 --> 00:04:18.170 align:start position:0% um we'll explain what that is and<00:04:16.440> then<00:04:16.560> once<00:04:16.859> we<00:04:16.979> have<00:04:17.160> that<00:04:17.340> we<00:04:17.639> will<00:04:17.820> sort 00:04:18.170 --> 00:04:18.180 align:start position:0% and then once we have that we will sort 00:04:18.180 --> 00:04:20.090 align:start position:0% and then once we have that we will sort of<00:04:18.299> explain 00:04:20.090 --> 00:04:20.100 align:start position:0% of explain 00:04:20.100 --> 00:04:22.670 align:start position:0% of explain how<00:04:20.820> to<00:04:20.940> use<00:04:21.180> the<00:04:21.419> market<00:04:21.600> same<00:04:21.959> how<00:04:22.199> it's<00:04:22.560> set 00:04:22.670 --> 00:04:22.680 align:start position:0% how to use the market same how it's set 00:04:22.680 --> 00:04:24.290 align:start position:0% how to use the market same how it's set up<00:04:22.800> you<00:04:22.979> know<00:04:23.100> what<00:04:23.220> what<00:04:23.460> environment<00:04:24.000> is 00:04:24.290 --> 00:04:24.300 align:start position:0% up you know what what environment is 00:04:24.300 --> 00:04:27.469 align:start position:0% up you know what what environment is there<00:04:24.620> uh<00:04:25.620> what<00:04:25.860> agents<00:04:26.340> are<00:04:26.520> there<00:04:26.759> and<00:04:27.300> what 00:04:27.469 --> 00:04:27.479 align:start position:0% there uh what agents are there and what 00:04:27.479 --> 00:04:31.370 align:start position:0% there uh what agents are there and what you<00:04:27.660> can<00:04:27.840> do<00:04:28.100> and<00:04:29.100> at<00:04:29.699> the<00:04:29.880> end<00:04:30.000> we're<00:04:30.479> gonna 00:04:31.370 --> 00:04:31.380 align:start position:0% you can do and at the end we're gonna 00:04:31.380 --> 00:04:33.230 align:start position:0% you can do and at the end we're gonna show<00:04:31.680> you<00:04:31.740> how<00:04:32.040> you<00:04:32.160> can<00:04:32.400> you<00:04:32.699> know<00:04:32.820> train 00:04:33.230 --> 00:04:33.240 align:start position:0% show you how you can you know train 00:04:33.240 --> 00:04:35.270 align:start position:0% show you how you can you know train reinforcement<00:04:33.960> learning<00:04:34.380> agents<00:04:34.800> on<00:04:34.979> top<00:04:35.160> of 00:04:35.270 --> 00:04:35.280 align:start position:0% reinforcement learning agents on top of 00:04:35.280 --> 00:04:37.490 align:start position:0% reinforcement learning agents on top of this<00:04:35.520> and<00:04:36.180> why<00:04:36.419> you<00:04:36.660> might<00:04:36.780> possibly<00:04:37.139> want<00:04:37.380> to 00:04:37.490 --> 00:04:37.500 align:start position:0% this and why you might possibly want to 00:04:37.500 --> 00:04:38.930 align:start position:0% this and why you might possibly want to do<00:04:37.740> that 00:04:38.930 --> 00:04:38.940 align:start position:0% do that 00:04:38.940 --> 00:04:43.430 align:start position:0% do that so<00:04:39.360> that's<00:04:39.600> that's<00:04:39.900> the<00:04:40.139> plan 00:04:43.430 --> 00:04:43.440 align:start position:0% 00:04:43.440 --> 00:04:46.730 align:start position:0% so<00:04:43.860> we<00:04:43.979> start<00:04:44.100> with<00:04:44.280> what<00:04:44.460> is<00:04:44.639> Vega<00:04:45.000> protocol 00:04:46.730 --> 00:04:46.740 align:start position:0% so we start with what is Vega protocol 00:04:46.740 --> 00:04:49.430 align:start position:0% so we start with what is Vega protocol so<00:04:47.160> Vega<00:04:47.580> protocol<00:04:47.880> is<00:04:48.600> a<00:04:48.900> layer<00:04:49.320> one 00:04:49.430 --> 00:04:49.440 align:start position:0% so Vega protocol is a layer one 00:04:49.440 --> 00:04:53.870 align:start position:0% so Vega protocol is a layer one blockchain<00:04:50.040> for<00:04:51.020> derivatives<00:04:52.020> trading<00:04:52.880> it's 00:04:53.870 --> 00:04:53.880 align:start position:0% blockchain for derivatives trading it's 00:04:53.880 --> 00:04:57.170 align:start position:0% blockchain for derivatives trading it's uh<00:04:54.720> set<00:04:55.259> up<00:04:55.440> from<00:04:55.680> the<00:04:55.860> ground<00:04:55.979> up<00:04:56.280> for<00:04:56.699> trading 00:04:57.170 --> 00:04:57.180 align:start position:0% uh set up from the ground up for trading 00:04:57.180 --> 00:05:00.590 align:start position:0% uh set up from the ground up for trading margins<00:04:57.660> products<00:04:58.340> and<00:04:59.340> the<00:04:59.820> price<00:04:59.940> Discovery 00:05:00.590 --> 00:05:00.600 align:start position:0% margins products and the price Discovery 00:05:00.600 --> 00:05:02.990 align:start position:0% margins products and the price Discovery is<00:05:01.080> either<00:05:01.320> through<00:05:01.620> limit<00:05:01.860> order<00:05:02.160> books<00:05:02.639> or 00:05:02.990 --> 00:05:03.000 align:start position:0% is either through limit order books or 00:05:03.000 --> 00:05:06.770 align:start position:0% is either through limit order books or through<00:05:03.860> auctions<00:05:05.000> where<00:05:06.000> do<00:05:06.240> the<00:05:06.419> auctions 00:05:06.770 --> 00:05:06.780 align:start position:0% through auctions where do the auctions 00:05:06.780 --> 00:05:08.090 align:start position:0% through auctions where do the auctions come<00:05:06.900> in<00:05:07.020> typically<00:05:07.380> when<00:05:07.620> you're<00:05:07.740> setting<00:05:08.040> up 00:05:08.090 --> 00:05:08.100 align:start position:0% come in typically when you're setting up 00:05:08.100 --> 00:05:10.189 align:start position:0% come in typically when you're setting up a<00:05:08.280> new<00:05:08.400> market<00:05:08.639> you<00:05:09.600> don't<00:05:09.660> know<00:05:09.840> what<00:05:10.020> the 00:05:10.189 --> 00:05:10.199 align:start position:0% a new market you don't know what the 00:05:10.199 --> 00:05:12.110 align:start position:0% a new market you don't know what the price<00:05:10.380> is<00:05:10.620> so<00:05:10.979> initially<00:05:11.400> there<00:05:11.639> it's<00:05:11.940> running 00:05:12.110 --> 00:05:12.120 align:start position:0% price is so initially there it's running 00:05:12.120 --> 00:05:14.510 align:start position:0% price is so initially there it's running in<00:05:12.360> an<00:05:12.479> auction<00:05:12.740> the<00:05:13.740> auction<00:05:13.979> determines 00:05:14.510 --> 00:05:14.520 align:start position:0% in an auction the auction determines 00:05:14.520 --> 00:05:16.010 align:start position:0% in an auction the auction determines what<00:05:14.699> the<00:05:14.880> opening<00:05:15.240> price<00:05:15.360> should<00:05:15.660> be<00:05:15.840> and 00:05:16.010 --> 00:05:16.020 align:start position:0% what the opening price should be and 00:05:16.020 --> 00:05:17.629 align:start position:0% what the opening price should be and then<00:05:16.139> if<00:05:16.320> everything<00:05:16.620> goes<00:05:17.040> well<00:05:17.160> it's<00:05:17.460> it's 00:05:17.629 --> 00:05:17.639 align:start position:0% then if everything goes well it's it's 00:05:17.639 --> 00:05:19.550 align:start position:0% then if everything goes well it's it's running<00:05:17.880> as<00:05:18.120> a<00:05:18.240> limit<00:05:18.360> order<00:05:18.600> book 00:05:19.550 --> 00:05:19.560 align:start position:0% running as a limit order book 00:05:19.560 --> 00:05:22.730 align:start position:0% running as a limit order book if<00:05:20.160> there<00:05:20.400> are<00:05:20.639> big<00:05:21.120> price<00:05:21.419> moves<00:05:22.020> according 00:05:22.730 --> 00:05:22.740 align:start position:0% if there are big price moves according 00:05:22.740 --> 00:05:24.590 align:start position:0% if there are big price moves according to<00:05:22.919> the<00:05:23.039> risk<00:05:23.340> model<00:05:23.460> it<00:05:23.820> might<00:05:24.000> switch<00:05:24.240> to<00:05:24.419> a 00:05:24.590 --> 00:05:24.600 align:start position:0% to the risk model it might switch to a 00:05:24.600 --> 00:05:26.749 align:start position:0% to the risk model it might switch to a protective<00:05:25.020> auction<00:05:25.320> to<00:05:26.100> make<00:05:26.220> sure<00:05:26.400> that<00:05:26.639> the 00:05:26.749 --> 00:05:26.759 align:start position:0% protective auction to make sure that the 00:05:26.759 --> 00:05:29.570 align:start position:0% protective auction to make sure that the big<00:05:26.880> price<00:05:27.060> move<00:05:27.419> is<00:05:27.720> really<00:05:28.440> you<00:05:29.039> know<00:05:29.160> what's 00:05:29.570 --> 00:05:29.580 align:start position:0% big price move is really you know what's 00:05:29.580 --> 00:05:31.070 align:start position:0% big price move is really you know what's happening<00:05:29.940> economically<00:05:30.539> it's<00:05:30.720> not<00:05:30.900> someone 00:05:31.070 --> 00:05:31.080 align:start position:0% happening economically it's not someone 00:05:31.080 --> 00:05:33.469 align:start position:0% happening economically it's not someone with<00:05:31.380> a<00:05:31.620> fat<00:05:31.740> finger<00:05:32.160> you<00:05:32.820> know<00:05:32.880> for<00:05:33.060> getting<00:05:33.240> a 00:05:33.469 --> 00:05:33.479 align:start position:0% with a fat finger you know for getting a 00:05:33.479 --> 00:05:36.110 align:start position:0% with a fat finger you know for getting a zero<00:05:33.840> on<00:05:34.080> an<00:05:34.380> order<00:05:34.500> and<00:05:34.800> or<00:05:35.220> adding<00:05:35.580> a<00:05:35.699> zero<00:05:36.000> on 00:05:36.110 --> 00:05:36.120 align:start position:0% zero on an order and or adding a zero on 00:05:36.120 --> 00:05:40.550 align:start position:0% zero on an order and or adding a zero on an<00:05:36.300> order<00:05:36.419> and<00:05:36.720> causing<00:05:37.440> causing<00:05:38.160> Mayhem<00:05:38.580> uh 00:05:40.550 --> 00:05:40.560 align:start position:0% an order and causing causing Mayhem uh 00:05:40.560 --> 00:05:42.830 align:start position:0% an order and causing causing Mayhem uh anyone<00:05:41.160> can<00:05:41.400> create<00:05:41.580> a<00:05:41.820> market<00:05:42.000> what<00:05:42.479> it<00:05:42.600> means 00:05:42.830 --> 00:05:42.840 align:start position:0% anyone can create a market what it means 00:05:42.840 --> 00:05:44.689 align:start position:0% anyone can create a market what it means is<00:05:42.960> you<00:05:43.199> submit<00:05:43.500> a<00:05:43.620> market<00:05:43.740> proposal<00:05:44.340> to<00:05:44.580> the 00:05:44.689 --> 00:05:44.699 align:start position:0% is you submit a market proposal to the 00:05:44.699 --> 00:05:46.189 align:start position:0% is you submit a market proposal to the blockchain<00:05:45.120> and<00:05:45.360> then<00:05:45.539> it<00:05:45.660> goes<00:05:45.900> through<00:05:46.020> the 00:05:46.189 --> 00:05:46.199 align:start position:0% blockchain and then it goes through the 00:05:46.199 --> 00:05:48.529 align:start position:0% blockchain and then it goes through the governance<00:05:46.560> and<00:05:46.800> it's<00:05:47.039> and<00:05:47.639> it's<00:05:47.820> voted<00:05:48.180> on<00:05:48.360> so 00:05:48.529 --> 00:05:48.539 align:start position:0% governance and it's and it's voted on so 00:05:48.539 --> 00:05:49.969 align:start position:0% governance and it's and it's voted on so that's<00:05:48.720> what's<00:05:48.900> meant<00:05:49.199> by<00:05:49.320> permissionless 00:05:49.969 --> 00:05:49.979 align:start position:0% that's what's meant by permissionless 00:05:49.979 --> 00:05:52.730 align:start position:0% that's what's meant by permissionless here<00:05:50.340> and<00:05:51.120> what<00:05:51.360> kind<00:05:51.539> of<00:05:51.660> markets<00:05:52.259> at<00:05:52.440> the 00:05:52.730 --> 00:05:52.740 align:start position:0% here and what kind of markets at the 00:05:52.740 --> 00:05:55.730 align:start position:0% here and what kind of markets at the moment<00:05:52.979> it's<00:05:53.400> it's<00:05:53.880> a<00:05:54.240> supports<00:05:55.020> cash<00:05:55.320> settled 00:05:55.730 --> 00:05:55.740 align:start position:0% moment it's it's a supports cash settled 00:05:55.740 --> 00:05:56.689 align:start position:0% moment it's it's a supports cash settled futures 00:05:56.689 --> 00:05:56.699 align:start position:0% futures 00:05:56.699 --> 00:05:59.450 align:start position:0% futures there<00:05:57.539> is<00:05:57.660> roadmap<00:05:58.199> for<00:05:58.440> supporting<00:05:58.979> any<00:05:59.220> kind 00:05:59.450 --> 00:05:59.460 align:start position:0% there is roadmap for supporting any kind 00:05:59.460 --> 00:06:02.150 align:start position:0% there is roadmap for supporting any kind of<00:05:59.580> derivative<00:06:00.180> through<00:06:00.660> a<00:06:01.380> derivative 00:06:02.150 --> 00:06:02.160 align:start position:0% of derivative through a derivative 00:06:02.160 --> 00:06:04.010 align:start position:0% of derivative through a derivative payoff<00:06:02.580> language<00:06:02.759> which<00:06:03.240> which<00:06:03.300> will<00:06:03.900> be 00:06:04.010 --> 00:06:04.020 align:start position:0% payoff language which which will be 00:06:04.020 --> 00:06:05.990 align:start position:0% payoff language which which will be probably<00:06:04.259> basm<00:06:04.860> based<00:06:05.220> but<00:06:05.460> that's<00:06:05.699> that's 00:06:05.990 --> 00:06:06.000 align:start position:0% probably basm based but that's that's 00:06:06.000 --> 00:06:07.730 align:start position:0% probably basm based but that's that's just<00:06:06.300> on<00:06:06.479> the<00:06:06.600> roadmap<00:06:06.960> for<00:06:07.199> now<00:06:07.380> it's<00:06:07.560> it's 00:06:07.730 --> 00:06:07.740 align:start position:0% just on the roadmap for now it's it's 00:06:07.740 --> 00:06:10.550 align:start position:0% just on the roadmap for now it's it's cash<00:06:07.979> settled<00:06:08.400> Futures<00:06:08.820> and<00:06:09.660> so<00:06:09.840> basically<00:06:10.199> if 00:06:10.550 --> 00:06:10.560 align:start position:0% cash settled Futures and so basically if 00:06:10.560 --> 00:06:12.170 align:start position:0% cash settled Futures and so basically if you<00:06:10.680> can<00:06:10.800> find<00:06:10.979> an<00:06:11.160> oracle 00:06:12.170 --> 00:06:12.180 align:start position:0% you can find an oracle 00:06:12.180 --> 00:06:14.210 align:start position:0% you can find an oracle for<00:06:12.600> the<00:06:12.720> market<00:06:12.900> then<00:06:13.259> you<00:06:13.500> can<00:06:13.620> then<00:06:13.860> you<00:06:14.100> can 00:06:14.210 --> 00:06:14.220 align:start position:0% for the market then you can then you can 00:06:14.220 --> 00:06:16.010 align:start position:0% for the market then you can then you can propose<00:06:14.580> the<00:06:14.820> market 00:06:16.010 --> 00:06:16.020 align:start position:0% propose the market 00:06:16.020 --> 00:06:17.330 align:start position:0% propose the market and 00:06:17.330 --> 00:06:17.340 align:start position:0% and 00:06:17.340 --> 00:06:19.790 align:start position:0% and it<00:06:17.759> will<00:06:17.940> run 00:06:19.790 --> 00:06:19.800 align:start position:0% it will run 00:06:19.800 --> 00:06:21.290 align:start position:0% it will run um<00:06:19.919> it's<00:06:20.100> got<00:06:20.280> a<00:06:20.400> bespoke<00:06:20.759> liquidity 00:06:21.290 --> 00:06:21.300 align:start position:0% um it's got a bespoke liquidity 00:06:21.300 --> 00:06:22.909 align:start position:0% um it's got a bespoke liquidity provision<00:06:21.720> mechanism<00:06:22.139> because<00:06:22.500> it's<00:06:22.740> it's 00:06:22.909 --> 00:06:22.919 align:start position:0% provision mechanism because it's it's 00:06:22.919 --> 00:06:25.309 align:start position:0% provision mechanism because it's it's not<00:06:23.220> based<00:06:23.639> on<00:06:23.699> now<00:06:24.000> ever<00:06:24.780> so<00:06:25.080> popular 00:06:25.309 --> 00:06:25.319 align:start position:0% not based on now ever so popular 00:06:25.319 --> 00:06:27.469 align:start position:0% not based on now ever so popular constant<00:06:25.979> product<00:06:26.220> markets 00:06:27.469 --> 00:06:27.479 align:start position:0% constant product markets 00:06:27.479 --> 00:06:29.930 align:start position:0% constant product markets but<00:06:28.199> it's<00:06:28.500> based<00:06:28.800> on<00:06:28.919> a<00:06:29.039> limit<00:06:29.220> order<00:06:29.520> book<00:06:29.819> so 00:06:29.930 --> 00:06:29.940 align:start position:0% but it's based on a limit order book so 00:06:29.940 --> 00:06:31.249 align:start position:0% but it's based on a limit order book so you<00:06:30.120> have<00:06:30.240> to<00:06:30.300> do<00:06:30.419> something<00:06:30.720> slightly 00:06:31.249 --> 00:06:31.259 align:start position:0% you have to do something slightly 00:06:31.259 --> 00:06:33.170 align:start position:0% you have to do something slightly different<00:06:31.440> to<00:06:31.740> bond<00:06:32.100> liquidity<00:06:32.639> to<00:06:32.880> a<00:06:33.060> limit 00:06:33.170 --> 00:06:33.180 align:start position:0% different to bond liquidity to a limit 00:06:33.180 --> 00:06:36.409 align:start position:0% different to bond liquidity to a limit order<00:06:33.419> book<00:06:33.720> so<00:06:34.020> it<00:06:34.199> does<00:06:34.380> that<00:06:34.759> and<00:06:35.759> at<00:06:36.300> the 00:06:36.409 --> 00:06:36.419 align:start position:0% order book so it does that and at the 00:06:36.419 --> 00:06:39.110 align:start position:0% order book so it does that and at the moment<00:06:36.600> the<00:06:36.960> the<00:06:37.199> assets<00:06:37.740> that<00:06:38.160> have<00:06:38.880> value 00:06:39.110 --> 00:06:39.120 align:start position:0% moment the the assets that have value 00:06:39.120 --> 00:06:41.150 align:start position:0% moment the the assets that have value that<00:06:39.479> you<00:06:39.600> would<00:06:39.720> use<00:06:39.900> a<00:06:40.259> settlement<00:06:40.620> asset<00:06:41.039> on 00:06:41.150 --> 00:06:41.160 align:start position:0% that you would use a settlement asset on 00:06:41.160 --> 00:06:44.090 align:start position:0% that you would use a settlement asset on Vega<00:06:41.580> they're<00:06:42.060> bridged<00:06:42.539> from<00:06:42.780> ethereum 00:06:44.090 --> 00:06:44.100 align:start position:0% Vega they're bridged from ethereum 00:06:44.100 --> 00:06:46.189 align:start position:0% Vega they're bridged from ethereum though<00:06:44.699> in<00:06:45.060> the<00:06:45.180> future<00:06:45.360> that<00:06:45.720> there<00:06:45.900> will<00:06:46.080> be 00:06:46.189 --> 00:06:46.199 align:start position:0% though in the future that there will be 00:06:46.199 --> 00:06:49.249 align:start position:0% though in the future that there will be other<00:06:46.380> Bridges<00:06:46.800> but<00:06:47.340> uh<00:06:48.060> ethereum<00:06:48.900> bridge<00:06:49.080> is 00:06:49.249 --> 00:06:49.259 align:start position:0% other Bridges but uh ethereum bridge is 00:06:49.259 --> 00:06:53.029 align:start position:0% other Bridges but uh ethereum bridge is there<00:06:49.560> you<00:06:50.520> can<00:06:50.699> on<00:06:51.240> Vega<00:06:51.780> before<00:06:52.259> proposing<00:06:52.919> a 00:06:53.029 --> 00:06:53.039 align:start position:0% there you can on Vega before proposing a 00:06:53.039 --> 00:06:54.650 align:start position:0% there you can on Vega before proposing a market<00:06:53.220> if<00:06:53.520> you<00:06:53.639> wanted<00:06:53.819> to<00:06:54.060> settle<00:06:54.419> in<00:06:54.539> some 00:06:54.650 --> 00:06:54.660 align:start position:0% market if you wanted to settle in some 00:06:54.660 --> 00:06:56.390 align:start position:0% market if you wanted to settle in some other<00:06:54.840> asset<00:06:55.199> that's<00:06:55.380> not<00:06:55.620> there<00:06:55.800> yet<00:06:56.039> you<00:06:56.280> can 00:06:56.390 --> 00:06:56.400 align:start position:0% other asset that's not there yet you can 00:06:56.400 --> 00:06:58.850 align:start position:0% other asset that's not there yet you can propose<00:06:56.759> the<00:06:57.000> asset<00:06:57.360> the<00:06:58.139> asset<00:06:58.440> will<00:06:58.560> then<00:06:58.740> be 00:06:58.850 --> 00:06:58.860 align:start position:0% propose the asset the asset will then be 00:06:58.860 --> 00:07:01.129 align:start position:0% propose the asset the asset will then be bridged<00:06:59.220> from<00:06:59.340> ethereum<00:06:59.880> so<00:07:00.539> you<00:07:00.840> can<00:07:00.960> imagine 00:07:01.129 --> 00:07:01.139 align:start position:0% bridged from ethereum so you can imagine 00:07:01.139 --> 00:07:03.950 align:start position:0% bridged from ethereum so you can imagine that<00:07:01.560> there<00:07:01.680> will<00:07:01.800> be<00:07:01.919> usdc<00:07:02.819> tether<00:07:03.300> ethereum 00:07:03.950 --> 00:07:03.960 align:start position:0% that there will be usdc tether ethereum 00:07:03.960 --> 00:07:06.110 align:start position:0% that there will be usdc tether ethereum whatever<00:07:04.259> people<00:07:04.620> want<00:07:04.979> to<00:07:05.100> do<00:07:05.280> is<00:07:05.759> that<00:07:06.000> if 00:07:06.110 --> 00:07:06.120 align:start position:0% whatever people want to do is that if 00:07:06.120 --> 00:07:07.730 align:start position:0% whatever people want to do is that if you're<00:07:06.419> designing<00:07:06.960> something<00:07:07.199> like<00:07:07.500> a 00:07:07.730 --> 00:07:07.740 align:start position:0% you're designing something like a 00:07:07.740 --> 00:07:11.450 align:start position:0% you're designing something like a trading<00:07:08.100> platform<00:07:08.580> some<00:07:09.419> of<00:07:09.600> the<00:07:10.220> goals<00:07:11.220> that 00:07:11.450 --> 00:07:11.460 align:start position:0% trading platform some of the goals that 00:07:11.460 --> 00:07:13.610 align:start position:0% trading platform some of the goals that you<00:07:11.580> might<00:07:11.699> have<00:07:11.940> in<00:07:12.240> the<00:07:12.419> design 00:07:13.610 --> 00:07:13.620 align:start position:0% you might have in the design 00:07:13.620 --> 00:07:16.309 align:start position:0% you might have in the design really<00:07:14.580> sort<00:07:15.180> of<00:07:15.300> run<00:07:15.479> at<00:07:15.720> Cross<00:07:15.900> purposes 00:07:16.309 --> 00:07:16.319 align:start position:0% really sort of run at Cross purposes 00:07:16.319 --> 00:07:19.309 align:start position:0% really sort of run at Cross purposes between<00:07:16.680> a<00:07:17.039> general<00:07:17.160> purpose<00:07:17.639> blockchain<00:07:18.319> and 00:07:19.309 --> 00:07:19.319 align:start position:0% between a general purpose blockchain and 00:07:19.319 --> 00:07:20.870 align:start position:0% between a general purpose blockchain and uh<00:07:19.620> you<00:07:19.860> know<00:07:19.919> what<00:07:20.160> do<00:07:20.280> you<00:07:20.340> what<00:07:20.580> you<00:07:20.699> would 00:07:20.870 --> 00:07:20.880 align:start position:0% uh you know what do you what you would 00:07:20.880 --> 00:07:23.510 align:start position:0% uh you know what do you what you would ideally<00:07:21.360> like<00:07:21.660> for<00:07:21.900> a<00:07:22.080> trading<00:07:22.440> platform 00:07:23.510 --> 00:07:23.520 align:start position:0% ideally like for a trading platform 00:07:23.520 --> 00:07:27.230 align:start position:0% ideally like for a trading platform so<00:07:24.240> the<00:07:24.660> things<00:07:25.080> that<00:07:25.319> I<00:07:25.500> picked<00:07:25.800> out<00:07:25.919> are<00:07:26.759> you 00:07:27.230 --> 00:07:27.240 align:start position:0% so the things that I picked out are you 00:07:27.240 --> 00:07:29.210 align:start position:0% so the things that I picked out are you know<00:07:27.300> a<00:07:27.479> general<00:07:27.660> purpose<00:07:28.080> blockchain<00:07:28.560> you 00:07:29.210 --> 00:07:29.220 align:start position:0% know a general purpose blockchain you 00:07:29.220 --> 00:07:31.070 align:start position:0% know a general purpose blockchain you you<00:07:29.340> need<00:07:29.639> something<00:07:29.880> like<00:07:30.180> a<00:07:30.360> gas<00:07:30.539> mechanism 00:07:31.070 --> 00:07:31.080 align:start position:0% you need something like a gas mechanism 00:07:31.080 --> 00:07:33.950 align:start position:0% you need something like a gas mechanism for<00:07:31.919> people<00:07:32.460> to<00:07:32.819> pay<00:07:33.000> for<00:07:33.240> the<00:07:33.479> cost<00:07:33.599> that 00:07:33.950 --> 00:07:33.960 align:start position:0% for people to pay for the cost that 00:07:33.960 --> 00:07:35.510 align:start position:0% for people to pay for the cost that whatever<00:07:34.259> transaction<00:07:34.800> the<00:07:35.160> chain<00:07:35.340> is 00:07:35.510 --> 00:07:35.520 align:start position:0% whatever transaction the chain is 00:07:35.520 --> 00:07:37.969 align:start position:0% whatever transaction the chain is processing<00:07:35.940> for<00:07:36.240> them<00:07:36.840> you<00:07:37.319> know<00:07:37.440> the<00:07:37.680> cost 00:07:37.969 --> 00:07:37.979 align:start position:0% processing for them you know the cost 00:07:37.979 --> 00:07:40.010 align:start position:0% processing for them you know the cost has<00:07:38.220> to<00:07:38.340> be<00:07:38.460> covered<00:07:38.759> by<00:07:39.000> the<00:07:39.180> gas 00:07:40.010 --> 00:07:40.020 align:start position:0% has to be covered by the gas 00:07:40.020 --> 00:07:43.070 align:start position:0% has to be covered by the gas and<00:07:40.680> if<00:07:41.039> you're<00:07:41.160> trading<00:07:41.520> this<00:07:41.880> is<00:07:42.000> really<00:07:42.300> you 00:07:43.070 --> 00:07:43.080 align:start position:0% and if you're trading this is really you 00:07:43.080 --> 00:07:45.770 align:start position:0% and if you're trading this is really you know<00:07:43.220> really<00:07:44.220> sub-optimal<00:07:45.000> in<00:07:45.240> in<00:07:45.419> the<00:07:45.599> sense 00:07:45.770 --> 00:07:45.780 align:start position:0% know really sub-optimal in in the sense 00:07:45.780 --> 00:07:48.170 align:start position:0% know really sub-optimal in in the sense that<00:07:45.960> there<00:07:46.800> are<00:07:46.919> transactions<00:07:47.699> that<00:07:48.060> you 00:07:48.170 --> 00:07:48.180 align:start position:0% that there are transactions that you 00:07:48.180 --> 00:07:50.210 align:start position:0% that there are transactions that you want<00:07:48.419> to<00:07:48.660> include<00:07:49.199> and<00:07:49.560> you<00:07:49.740> don't<00:07:49.860> want<00:07:50.099> to 00:07:50.210 --> 00:07:50.220 align:start position:0% want to include and you don't want to 00:07:50.220 --> 00:07:52.730 align:start position:0% want to include and you don't want to penalize<00:07:51.000> them<00:07:51.180> by<00:07:51.419> charging<00:07:51.780> for<00:07:52.020> them<00:07:52.199> you 00:07:52.730 --> 00:07:52.740 align:start position:0% penalize them by charging for them you 00:07:52.740 --> 00:07:54.050 align:start position:0% penalize them by charging for them you know<00:07:52.860> if<00:07:52.979> someone<00:07:53.160> wants<00:07:53.460> to<00:07:53.520> post<00:07:53.699> a<00:07:53.880> limit 00:07:54.050 --> 00:07:54.060 align:start position:0% know if someone wants to post a limit 00:07:54.060 --> 00:07:55.969 align:start position:0% know if someone wants to post a limit order<00:07:54.360> that's<00:07:55.080> good<00:07:55.319> they're<00:07:55.560> providing 00:07:55.969 --> 00:07:55.979 align:start position:0% order that's good they're providing 00:07:55.979 --> 00:07:57.409 align:start position:0% order that's good they're providing liquidity<00:07:56.460> you<00:07:56.819> really<00:07:56.940> don't<00:07:57.120> want<00:07:57.300> to 00:07:57.409 --> 00:07:57.419 align:start position:0% liquidity you really don't want to 00:07:57.419 --> 00:07:59.570 align:start position:0% liquidity you really don't want to discourage<00:07:57.840> them<00:07:58.020> if<00:07:58.800> someone<00:07:58.919> cancels<00:07:59.460> an 00:07:59.570 --> 00:07:59.580 align:start position:0% discourage them if someone cancels an 00:07:59.580 --> 00:08:01.189 align:start position:0% discourage them if someone cancels an order<00:07:59.759> that's<00:08:00.240> good<00:08:00.479> they're<00:08:00.720> providing 00:08:01.189 --> 00:08:01.199 align:start position:0% order that's good they're providing 00:08:01.199 --> 00:08:02.570 align:start position:0% order that's good they're providing price<00:08:01.380> information<00:08:01.740> you<00:08:02.160> probably<00:08:02.340> don't 00:08:02.570 --> 00:08:02.580 align:start position:0% price information you probably don't 00:08:02.580 --> 00:08:04.370 align:start position:0% price information you probably don't want<00:08:02.759> to<00:08:02.880> discourage<00:08:03.240> that<00:08:03.419> either 00:08:04.370 --> 00:08:04.380 align:start position:0% want to discourage that either 00:08:04.380 --> 00:08:07.490 align:start position:0% want to discourage that either so<00:08:05.280> you<00:08:06.000> know<00:08:06.060> that's<00:08:06.419> in<00:08:06.900> products<00:08:07.319> they're 00:08:07.490 --> 00:08:07.500 align:start position:0% so you know that's in products they're 00:08:07.500 --> 00:08:08.990 align:start position:0% so you know that's in products they're effectively<00:08:07.919> promises<00:08:08.400> right<00:08:08.580> if<00:08:08.819> someone 00:08:08.990 --> 00:08:09.000 align:start position:0% effectively promises right if someone 00:08:09.000 --> 00:08:10.189 align:start position:0% effectively promises right if someone doesn't<00:08:09.240> look<00:08:09.479> like<00:08:09.599> they're<00:08:09.840> going<00:08:10.020> to<00:08:10.080> keep 00:08:10.189 --> 00:08:10.199 align:start position:0% doesn't look like they're going to keep 00:08:10.199 --> 00:08:11.689 align:start position:0% doesn't look like they're going to keep their<00:08:10.380> promise<00:08:10.680> you<00:08:10.919> want<00:08:11.039> to<00:08:11.160> close<00:08:11.280> them<00:08:11.520> out 00:08:11.689 --> 00:08:11.699 align:start position:0% their promise you want to close them out 00:08:11.699 --> 00:08:14.749 align:start position:0% their promise you want to close them out immediately<00:08:12.319> ideally<00:08:13.319> you<00:08:13.560> don't<00:08:13.680> want<00:08:13.919> it 00:08:14.749 --> 00:08:14.759 align:start position:0% immediately ideally you don't want it 00:08:14.759 --> 00:08:17.029 align:start position:0% immediately ideally you don't want it farmed<00:08:15.479> out<00:08:15.599> to<00:08:16.020> some<00:08:16.139> Bots<00:08:16.380> that<00:08:16.680> are<00:08:16.860> running 00:08:17.029 --> 00:08:17.039 align:start position:0% farmed out to some Bots that are running 00:08:17.039 --> 00:08:18.589 align:start position:0% farmed out to some Bots that are running somewhere<00:08:17.520> because<00:08:17.699> then<00:08:18.000> you're<00:08:18.180> opening 00:08:18.589 --> 00:08:18.599 align:start position:0% somewhere because then you're opening 00:08:18.599 --> 00:08:20.990 align:start position:0% somewhere because then you're opening yourself<00:08:18.720> up<00:08:19.080> to<00:08:19.259> Mev<00:08:19.740> and<00:08:19.979> on<00:08:20.220> a<00:08:20.340> whole<00:08:20.639> whole 00:08:20.990 --> 00:08:21.000 align:start position:0% yourself up to Mev and on a whole whole 00:08:21.000 --> 00:08:23.450 align:start position:0% yourself up to Mev and on a whole whole host<00:08:21.300> of<00:08:21.539> other<00:08:21.720> problems<00:08:22.259> so<00:08:23.099> you<00:08:23.220> can<00:08:23.340> have 00:08:23.450 --> 00:08:23.460 align:start position:0% host of other problems so you can have 00:08:23.460 --> 00:08:25.309 align:start position:0% host of other problems so you can have Atomic<00:08:23.940> closeouts 00:08:25.309 --> 00:08:25.319 align:start position:0% Atomic closeouts 00:08:25.319 --> 00:08:27.850 align:start position:0% Atomic closeouts again<00:08:25.800> for<00:08:26.099> margin<00:08:26.520> you<00:08:26.759> want<00:08:27.000> to<00:08:27.120> do 00:08:27.850 --> 00:08:27.860 align:start position:0% again for margin you want to do 00:08:27.860 --> 00:08:30.350 align:start position:0% again for margin you want to do potentially<00:08:28.860> quiet<00:08:29.160> Maps<00:08:29.639> heavy<00:08:29.940> risk<00:08:30.300> of 00:08:30.350 --> 00:08:30.360 align:start position:0% potentially quiet Maps heavy risk of 00:08:30.360 --> 00:08:31.670 align:start position:0% potentially quiet Maps heavy risk of computations 00:08:31.670 --> 00:08:31.680 align:start position:0% computations 00:08:31.680 --> 00:08:33.589 align:start position:0% computations and<00:08:32.159> you<00:08:32.339> don't<00:08:32.520> want<00:08:32.700> to<00:08:32.820> be<00:08:32.940> paying<00:08:33.240> for<00:08:33.360> gas 00:08:33.589 --> 00:08:33.599 align:start position:0% and you don't want to be paying for gas 00:08:33.599 --> 00:08:35.269 align:start position:0% and you don't want to be paying for gas for<00:08:33.899> those<00:08:34.080> on<00:08:34.260> a<00:08:34.680> general<00:08:34.800> purpose 00:08:35.269 --> 00:08:35.279 align:start position:0% for those on a general purpose 00:08:35.279 --> 00:08:36.529 align:start position:0% for those on a general purpose blockchain 00:08:36.529 --> 00:08:36.539 align:start position:0% blockchain 00:08:36.539 --> 00:08:39.230 align:start position:0% blockchain you<00:08:37.260> can<00:08:37.440> try<00:08:37.800> to<00:08:38.099> do 00:08:39.230 --> 00:08:39.240 align:start position:0% you can try to do 00:08:39.240 --> 00:08:43.190 align:start position:0% you can try to do Fair<00:08:39.899> ordering<00:08:40.560> or<00:08:41.219> as<00:08:41.700> Fair<00:08:41.940> as<00:08:42.419> your 00:08:43.190 --> 00:08:43.200 align:start position:0% Fair ordering or as Fair as your 00:08:43.200 --> 00:08:45.650 align:start position:0% Fair ordering or as Fair as your definition<00:08:43.380> of<00:08:43.800> fairness<00:08:44.219> allows<00:08:44.820> Fair 00:08:45.650 --> 00:08:45.660 align:start position:0% definition of fairness allows Fair 00:08:45.660 --> 00:08:48.170 align:start position:0% definition of fairness allows Fair ordering<00:08:46.080> of<00:08:46.200> orders<00:08:46.580> and<00:08:47.580> you<00:08:47.820> know<00:08:47.880> you<00:08:48.000> you 00:08:48.170 --> 00:08:48.180 align:start position:0% ordering of orders and you know you you 00:08:48.180 --> 00:08:50.449 align:start position:0% ordering of orders and you know you you have<00:08:48.420> one<00:08:48.600> specific<00:08:48.899> application<00:08:49.440> in<00:08:49.800> mind<00:08:49.980> so 00:08:50.449 --> 00:08:50.459 align:start position:0% have one specific application in mind so 00:08:50.459 --> 00:08:52.009 align:start position:0% have one specific application in mind so you<00:08:50.580> can<00:08:50.700> optimize<00:08:51.060> for<00:08:51.300> latency<00:08:51.660> for 00:08:52.009 --> 00:08:52.019 align:start position:0% you can optimize for latency for 00:08:52.019 --> 00:08:54.530 align:start position:0% you can optimize for latency for instance<00:08:52.260> rather<00:08:52.980> than<00:08:53.100> optimizing<00:08:53.820> for<00:08:54.180> you 00:08:54.530 --> 00:08:54.540 align:start position:0% instance rather than optimizing for you 00:08:54.540 --> 00:08:56.329 align:start position:0% instance rather than optimizing for you know<00:08:54.600> data<00:08:55.019> throughput<00:08:55.440> so<00:08:56.040> you're<00:08:56.160> not 00:08:56.329 --> 00:08:56.339 align:start position:0% know data throughput so you're not 00:08:56.339 --> 00:08:58.310 align:start position:0% know data throughput so you're not fighting<00:08:56.820> at<00:08:57.060> Cross<00:08:57.240> purposes<00:08:57.779> with<00:08:58.140> other 00:08:58.310 --> 00:08:58.320 align:start position:0% fighting at Cross purposes with other 00:08:58.320 --> 00:09:00.650 align:start position:0% fighting at Cross purposes with other applications<00:08:58.860> that<00:08:59.220> would<00:08:59.339> be<00:08:59.519> running<00:08:59.760> on 00:09:00.650 --> 00:09:00.660 align:start position:0% applications that would be running on 00:09:00.660 --> 00:09:02.090 align:start position:0% applications that would be running on top<00:09:00.779> of<00:09:00.959> a<00:09:01.080> general<00:09:01.200> purpose<00:09:01.680> blockchain 00:09:02.090 --> 00:09:02.100 align:start position:0% top of a general purpose blockchain 00:09:02.100 --> 00:09:03.590 align:start position:0% top of a general purpose blockchain which<00:09:02.279> would<00:09:02.459> have<00:09:02.640> other<00:09:02.760> design<00:09:03.060> goals<00:09:03.540> in 00:09:03.590 --> 00:09:03.600 align:start position:0% which would have other design goals in 00:09:03.600 --> 00:09:04.490 align:start position:0% which would have other design goals in mind 00:09:04.490 --> 00:09:04.500 align:start position:0% mind 00:09:04.500 --> 00:09:06.889 align:start position:0% mind and<00:09:05.040> one<00:09:05.220> one<00:09:05.459> thing<00:09:05.700> that<00:09:05.880> I<00:09:06.060> didn't<00:09:06.180> put<00:09:06.540> on 00:09:06.889 --> 00:09:06.899 align:start position:0% and one one thing that I didn't put on 00:09:06.899 --> 00:09:08.329 align:start position:0% and one one thing that I didn't put on the<00:09:07.019> slide<00:09:07.260> but<00:09:07.500> that's<00:09:07.680> also<00:09:07.980> a<00:09:08.040> very<00:09:08.160> good 00:09:08.329 --> 00:09:08.339 align:start position:0% the slide but that's also a very good 00:09:08.339 --> 00:09:10.130 align:start position:0% the slide but that's also a very good reason<00:09:08.519> is<00:09:08.820> that<00:09:09.060> sharding<00:09:09.480> is<00:09:09.660> actually<00:09:09.839> much 00:09:10.130 --> 00:09:10.140 align:start position:0% reason is that sharding is actually much 00:09:10.140 --> 00:09:13.670 align:start position:0% reason is that sharding is actually much easier<00:09:10.500> in<00:09:11.279> the<00:09:11.459> context<00:09:11.700> of<00:09:11.940> trading<00:09:12.360> because 00:09:13.670 --> 00:09:13.680 align:start position:0% easier in the context of trading because 00:09:13.680 --> 00:09:15.530 align:start position:0% easier in the context of trading because something<00:09:14.220> happening<00:09:14.700> on<00:09:14.880> this<00:09:15.060> market<00:09:15.240> and 00:09:15.530 --> 00:09:15.540 align:start position:0% something happening on this market and 00:09:15.540 --> 00:09:17.150 align:start position:0% something happening on this market and something<00:09:15.779> happening<00:09:16.200> on<00:09:16.440> that<00:09:16.560> market<00:09:16.740> can 00:09:17.150 --> 00:09:17.160 align:start position:0% something happening on that market can 00:09:17.160 --> 00:09:19.250 align:start position:0% something happening on that market can be<00:09:17.339> completely<00:09:17.760> separate<00:09:18.240> apart<00:09:19.019> from 00:09:19.250 --> 00:09:19.260 align:start position:0% be completely separate apart from 00:09:19.260 --> 00:09:20.990 align:start position:0% be completely separate apart from Talking<00:09:19.560> together<00:09:20.100> through<00:09:20.459> a<00:09:20.640> treasury 00:09:20.990 --> 00:09:21.000 align:start position:0% Talking together through a treasury 00:09:21.000 --> 00:09:24.410 align:start position:0% Talking together through a treasury chart<00:09:21.240> so<00:09:22.140> you<00:09:22.260> have<00:09:22.680> a<00:09:22.860> very<00:09:22.980> simple<00:09:23.160> use<00:09:23.519> case 00:09:24.410 --> 00:09:24.420 align:start position:0% chart so you have a very simple use case 00:09:24.420 --> 00:09:26.750 align:start position:0% chart so you have a very simple use case in<00:09:25.019> the<00:09:25.080> sense<00:09:25.260> of<00:09:25.500> what<00:09:25.980> needs<00:09:26.339> to<00:09:26.399> know<00:09:26.519> about 00:09:26.750 --> 00:09:26.760 align:start position:0% in the sense of what needs to know about 00:09:26.760 --> 00:09:29.449 align:start position:0% in the sense of what needs to know about what<00:09:27.180> you<00:09:27.779> can<00:09:27.899> design<00:09:28.080> charting<00:09:28.740> relatively 00:09:29.449 --> 00:09:29.459 align:start position:0% what you can design charting relatively 00:09:29.459 --> 00:09:32.269 align:start position:0% what you can design charting relatively easily 00:09:32.269 --> 00:09:32.279 align:start position:0% 00:09:32.279 --> 00:09:35.870 align:start position:0% okay<00:09:32.760> so<00:09:33.000> that<00:09:33.180> was<00:09:33.360> that<00:09:33.600> was<00:09:33.720> Vega<00:09:34.680> Now<00:09:35.459> sort 00:09:35.870 --> 00:09:35.880 align:start position:0% okay so that was that was Vega Now sort 00:09:35.880 --> 00:09:37.730 align:start position:0% okay so that was that was Vega Now sort of<00:09:36.060> more<00:09:36.300> General 00:09:37.730 --> 00:09:37.740 align:start position:0% of more General 00:09:37.740 --> 00:09:41.630 align:start position:0% of more General case<00:09:38.279> for<00:09:38.940> doing 00:09:41.630 --> 00:09:41.640 align:start position:0% case for doing 00:09:41.640 --> 00:09:43.490 align:start position:0% case for doing just<00:09:41.880> trying<00:09:42.120> to<00:09:42.300> get<00:09:42.420> rid<00:09:42.540> of<00:09:42.660> the<00:09:42.839> mouse<00:09:42.959> more 00:09:43.490 --> 00:09:43.500 align:start position:0% just trying to get rid of the mouse more 00:09:43.500 --> 00:09:45.490 align:start position:0% just trying to get rid of the mouse more General<00:09:43.740> case<00:09:44.040> for<00:09:44.220> doing 00:09:45.490 --> 00:09:45.500 align:start position:0% General case for doing 00:09:45.500 --> 00:09:47.690 align:start position:0% General case for doing agent-based<00:09:46.500> simulations<00:09:46.920> in<00:09:47.279> in<00:09:47.459> the 00:09:47.690 --> 00:09:47.700 align:start position:0% agent-based simulations in in the 00:09:47.700 --> 00:09:49.910 align:start position:0% agent-based simulations in in the context<00:09:47.940> of<00:09:48.180> D5<00:09:48.600> so 00:09:49.910 --> 00:09:49.920 align:start position:0% context of D5 so 00:09:49.920 --> 00:09:52.370 align:start position:0% context of D5 so you<00:09:50.519> know<00:09:50.580> we've<00:09:51.180> all<00:09:51.300> seen<00:09:51.540> various<00:09:51.959> D5 00:09:52.370 --> 00:09:52.380 align:start position:0% you know we've all seen various D5 00:09:52.380 --> 00:09:55.009 align:start position:0% you know we've all seen various D5 protocols<00:09:53.220> and<00:09:53.700> uh<00:09:54.180> we've<00:09:54.540> seen<00:09:54.720> you<00:09:54.899> know 00:09:55.009 --> 00:09:55.019 align:start position:0% protocols and uh we've seen you know 00:09:55.019 --> 00:09:56.690 align:start position:0% protocols and uh we've seen you know when<00:09:55.200> things<00:09:55.380> go<00:09:55.620> well<00:09:55.800> it's<00:09:56.100> great<00:09:56.339> and<00:09:56.580> then 00:09:56.690 --> 00:09:56.700 align:start position:0% when things go well it's great and then 00:09:56.700 --> 00:09:59.449 align:start position:0% when things go well it's great and then when<00:09:56.940> things<00:09:57.180> don't<00:09:57.480> go<00:09:57.720> well<00:09:57.899> it's<00:09:58.860> called<00:09:59.100> a 00:09:59.449 --> 00:09:59.459 align:start position:0% when things don't go well it's called a 00:09:59.459 --> 00:10:03.710 align:start position:0% when things don't go well it's called a hack<00:10:00.000> or<00:10:00.180> an<00:10:00.360> exploit<00:10:00.779> but<00:10:01.200> quite<00:10:01.980> often<00:10:02.279> it's 00:10:03.710 --> 00:10:03.720 align:start position:0% hack or an exploit but quite often it's 00:10:03.720 --> 00:10:06.769 align:start position:0% hack or an exploit but quite often it's not<00:10:04.200> an<00:10:04.560> exploit<00:10:05.279> of<00:10:05.459> a<00:10:05.580> code<00:10:06.060> bug<00:10:06.300> though<00:10:06.540> that 00:10:06.769 --> 00:10:06.779 align:start position:0% not an exploit of a code bug though that 00:10:06.779 --> 00:10:09.350 align:start position:0% not an exploit of a code bug though that can<00:10:06.959> happen<00:10:07.140> it's<00:10:07.440> it's<00:10:07.620> simply<00:10:08.040> an<00:10:08.360> exploit 00:10:09.350 --> 00:10:09.360 align:start position:0% can happen it's it's simply an exploit 00:10:09.360 --> 00:10:11.509 align:start position:0% can happen it's it's simply an exploit of<00:10:09.779> of<00:10:09.839> the<00:10:10.200> mechanism<00:10:10.560> design<00:10:10.860> you<00:10:11.220> know<00:10:11.339> you 00:10:11.509 --> 00:10:11.519 align:start position:0% of of the mechanism design you know you 00:10:11.519 --> 00:10:12.829 align:start position:0% of of the mechanism design you know you you<00:10:11.760> go 00:10:12.829 --> 00:10:12.839 align:start position:0% you go 00:10:12.839 --> 00:10:15.650 align:start position:0% you go you<00:10:13.320> want<00:10:13.440> to<00:10:13.560> design<00:10:13.740> a<00:10:14.100> protocol<00:10:14.420> you<00:10:15.420> start 00:10:15.650 --> 00:10:15.660 align:start position:0% you want to design a protocol you start 00:10:15.660 --> 00:10:17.570 align:start position:0% you want to design a protocol you start you<00:10:15.959> you<00:10:16.080> think<00:10:16.440> what<00:10:16.680> incentives<00:10:17.160> should<00:10:17.459> I 00:10:17.570 --> 00:10:17.580 align:start position:0% you you think what incentives should I 00:10:17.580 --> 00:10:19.130 align:start position:0% you you think what incentives should I create<00:10:17.760> so<00:10:18.060> that<00:10:18.240> I've<00:10:18.360> got<00:10:18.540> the<00:10:18.720> desired 00:10:19.130 --> 00:10:19.140 align:start position:0% create so that I've got the desired 00:10:19.140 --> 00:10:22.610 align:start position:0% create so that I've got the desired behaviors<00:10:19.620> and<00:10:20.519> you<00:10:20.640> do<00:10:20.880> it<00:10:21.000> in<00:10:21.180> isolation<00:10:21.779> you 00:10:22.610 --> 00:10:22.620 align:start position:0% behaviors and you do it in isolation you 00:10:22.620 --> 00:10:24.350 align:start position:0% behaviors and you do it in isolation you really<00:10:22.800> try<00:10:23.040> to<00:10:23.160> think<00:10:23.339> it<00:10:23.580> through<00:10:23.760> right<00:10:24.060> you 00:10:24.350 --> 00:10:24.360 align:start position:0% really try to think it through right you 00:10:24.360 --> 00:10:26.690 align:start position:0% really try to think it through right you you<00:10:24.540> take<00:10:25.440> the<00:10:25.620> smartest<00:10:26.040> people<00:10:26.220> you<00:10:26.459> can 00:10:26.690 --> 00:10:26.700 align:start position:0% you take the smartest people you can 00:10:26.700 --> 00:10:27.949 align:start position:0% you take the smartest people you can find<00:10:26.880> there<00:10:27.180> are 00:10:27.949 --> 00:10:27.959 align:start position:0% find there are 00:10:27.959 --> 00:10:30.470 align:start position:0% find there are you<00:10:28.560> know<00:10:28.680> dozens<00:10:29.279> hundreds<00:10:29.760> of<00:10:29.880> incredibly 00:10:30.470 --> 00:10:30.480 align:start position:0% you know dozens hundreds of incredibly 00:10:30.480 --> 00:10:33.110 align:start position:0% you know dozens hundreds of incredibly smart<00:10:30.720> people<00:10:31.019> in<00:10:31.260> defy<00:10:31.800> they<00:10:32.519> do<00:10:32.640> their<00:10:32.880> best 00:10:33.110 --> 00:10:33.120 align:start position:0% smart people in defy they do their best 00:10:33.120 --> 00:10:35.269 align:start position:0% smart people in defy they do their best they<00:10:33.779> do<00:10:33.899> what<00:10:34.080> makes<00:10:34.320> sense 00:10:35.269 --> 00:10:35.279 align:start position:0% they do what makes sense 00:10:35.279 --> 00:10:37.009 align:start position:0% they do what makes sense they<00:10:35.760> think<00:10:35.880> it<00:10:36.060> through<00:10:36.300> as<00:10:36.540> much<00:10:36.660> as<00:10:36.779> they 00:10:37.009 --> 00:10:37.019 align:start position:0% they think it through as much as they 00:10:37.019 --> 00:10:38.210 align:start position:0% they think it through as much as they can 00:10:38.210 --> 00:10:38.220 align:start position:0% can 00:10:38.220 --> 00:10:41.449 align:start position:0% can but<00:10:39.060> uh<00:10:39.480> it's<00:10:39.959> difficult<00:10:40.320> it's<00:10:41.040> really<00:10:41.220> really 00:10:41.449 --> 00:10:41.459 align:start position:0% but uh it's difficult it's really really 00:10:41.459 --> 00:10:43.790 align:start position:0% but uh it's difficult it's really really difficult<00:10:41.880> to<00:10:42.060> think<00:10:42.300> through<00:10:42.779> all<00:10:43.680> the 00:10:43.790 --> 00:10:43.800 align:start position:0% difficult to think through all the 00:10:43.800 --> 00:10:46.190 align:start position:0% difficult to think through all the consequences<00:10:44.420> especially<00:10:45.420> if<00:10:45.600> you<00:10:45.899> have<00:10:46.019> one 00:10:46.190 --> 00:10:46.200 align:start position:0% consequences especially if you have one 00:10:46.200 --> 00:10:48.829 align:start position:0% consequences especially if you have one incentive<00:10:46.980> mechanism<00:10:47.399> here<00:10:47.760> and<00:10:48.360> other<00:10:48.540> Hair 00:10:48.829 --> 00:10:48.839 align:start position:0% incentive mechanism here and other Hair 00:10:48.839 --> 00:10:51.530 align:start position:0% incentive mechanism here and other Hair Design<00:10:49.260> maybe<00:10:49.620> in<00:10:49.980> isolation<00:10:50.519> and<00:10:51.360> now 00:10:51.530 --> 00:10:51.540 align:start position:0% Design maybe in isolation and now 00:10:51.540 --> 00:10:53.150 align:start position:0% Design maybe in isolation and now they're<00:10:51.779> interacting 00:10:53.150 --> 00:10:53.160 align:start position:0% they're interacting 00:10:53.160 --> 00:10:54.290 align:start position:0% they're interacting right 00:10:54.290 --> 00:10:54.300 align:start position:0% right 00:10:54.300 --> 00:10:56.930 align:start position:0% right yeah 00:10:56.930 --> 00:10:56.940 align:start position:0% 00:10:56.940 --> 00:11:00.350 align:start position:0% oh<00:10:57.540> vendor<00:10:58.079> is<00:10:58.260> a<00:10:58.380> name<00:10:58.500> of<00:10:58.740> Claus's<00:10:59.519> fairness 00:11:00.350 --> 00:11:00.360 align:start position:0% oh vendor is a name of Claus's fairness 00:11:00.360 --> 00:11:03.470 align:start position:0% oh vendor is a name of Claus's fairness pre-protocol<00:11:01.140> for<00:11:01.560> transaction<00:11:01.980> ordering<00:11:02.940> he 00:11:03.470 --> 00:11:03.480 align:start position:0% pre-protocol for transaction ordering he 00:11:03.480 --> 00:11:05.930 align:start position:0% pre-protocol for transaction ordering he can<00:11:03.720> tell<00:11:03.839> you<00:11:03.959> all<00:11:04.140> about<00:11:04.320> that<00:11:04.680> he's<00:11:05.459> there 00:11:05.930 --> 00:11:05.940 align:start position:0% can tell you all about that he's there 00:11:05.940 --> 00:11:12.530 align:start position:0% can tell you all about that he's there the<00:11:06.240> the 00:11:12.530 --> 00:11:12.540 align:start position:0% 00:11:12.540 --> 00:11:17.630 align:start position:0% you<00:11:13.019> can<00:11:13.200> just<00:11:13.260> go<00:11:13.440> and<00:11:13.560> show<00:11:13.680> him<00:11:13.800> no 00:11:17.630 --> 00:11:17.640 align:start position:0% 00:11:17.640 --> 00:11:19.190 align:start position:0% yeah 00:11:19.190 --> 00:11:19.200 align:start position:0% yeah 00:11:19.200 --> 00:11:21.050 align:start position:0% yeah yeah so<00:11:19.740> you<00:11:19.920> you<00:11:20.100> put<00:11:20.399> two<00:11:20.579> incentives 00:11:21.050 --> 00:11:21.060 align:start position:0% yeah so you you put two incentives 00:11:21.060 --> 00:11:22.550 align:start position:0% yeah so you you put two incentives mechanisms<00:11:21.660> together<00:11:21.839> if<00:11:22.200> they<00:11:22.320> were 00:11:22.550 --> 00:11:22.560 align:start position:0% mechanisms together if they were 00:11:22.560 --> 00:11:24.769 align:start position:0% mechanisms together if they were designed<00:11:22.920> in<00:11:23.040> isolation<00:11:23.519> it's<00:11:23.820> it's<00:11:24.000> not<00:11:24.360> you 00:11:24.769 --> 00:11:24.779 align:start position:0% designed in isolation it's it's not you 00:11:24.779 --> 00:11:26.870 align:start position:0% designed in isolation it's it's not you know<00:11:24.839> completely<00:11:25.380> clear<00:11:25.620> that<00:11:26.279> the<00:11:26.459> combined 00:11:26.870 --> 00:11:26.880 align:start position:0% know completely clear that the combined 00:11:26.880 --> 00:11:28.490 align:start position:0% know completely clear that the combined effect<00:11:27.060> is<00:11:27.360> actually<00:11:27.540> what<00:11:27.779> you've<00:11:28.079> desired 00:11:28.490 --> 00:11:28.500 align:start position:0% effect is actually what you've desired 00:11:28.500 --> 00:11:30.410 align:start position:0% effect is actually what you've desired and<00:11:29.100> then<00:11:29.220> of<00:11:29.399> course<00:11:29.519> D5<00:11:29.940> is<00:11:30.120> all<00:11:30.300> about 00:11:30.410 --> 00:11:30.420 align:start position:0% and then of course D5 is all about 00:11:30.420 --> 00:11:33.710 align:start position:0% and then of course D5 is all about composability<00:11:31.260> they<00:11:31.560> love<00:11:31.800> that<00:11:32.060> but<00:11:33.060> once 00:11:33.710 --> 00:11:33.720 align:start position:0% composability they love that but once 00:11:33.720 --> 00:11:35.630 align:start position:0% composability they love that but once you<00:11:33.779> introduce<00:11:34.140> composability<00:11:34.860> you're 00:11:35.630 --> 00:11:35.640 align:start position:0% you introduce composability you're 00:11:35.640 --> 00:11:38.269 align:start position:0% you introduce composability you're introducing<00:11:36.120> another<00:11:36.320> disproof<00:11:37.320> stuff<00:11:37.560> you 00:11:38.269 --> 00:11:38.279 align:start position:0% introducing another disproof stuff you 00:11:38.279 --> 00:11:40.190 align:start position:0% introducing another disproof stuff you set<00:11:38.459> up<00:11:38.579> a<00:11:38.760> hypothesis<00:11:39.360> which<00:11:39.600> is<00:11:39.720> testable 00:11:40.190 --> 00:11:40.200 align:start position:0% set up a hypothesis which is testable 00:11:40.200 --> 00:11:42.889 align:start position:0% set up a hypothesis which is testable you<00:11:40.980> will<00:11:41.100> never<00:11:41.279> prove<00:11:41.760> that<00:11:42.180> it's<00:11:42.360> true<00:11:42.600> but 00:11:42.889 --> 00:11:42.899 align:start position:0% you will never prove that it's true but 00:11:42.899 --> 00:11:45.050 align:start position:0% you will never prove that it's true but you<00:11:43.079> can<00:11:43.260> set<00:11:43.380> it<00:11:43.560> up<00:11:43.740> so<00:11:43.920> that<00:11:44.220> you<00:11:44.700> run<00:11:44.820> the 00:11:45.050 --> 00:11:45.060 align:start position:0% you can set it up so that you run the 00:11:45.060 --> 00:11:46.610 align:start position:0% you can set it up so that you run the experiments<00:11:45.600> that<00:11:45.720> should<00:11:45.899> disprove<00:11:46.380> it<00:11:46.500> if 00:11:46.610 --> 00:11:46.620 align:start position:0% experiments that should disprove it if 00:11:46.620 --> 00:11:47.870 align:start position:0% experiments that should disprove it if you<00:11:46.740> try<00:11:46.920> their<00:11:47.160> best<00:11:47.339> and<00:11:47.519> you've<00:11:47.760> not 00:11:47.870 --> 00:11:47.880 align:start position:0% you try their best and you've not 00:11:47.880 --> 00:11:50.150 align:start position:0% you try their best and you've not disproved<00:11:48.420> it<00:11:48.540> then<00:11:49.079> you'll<00:11:49.440> then<00:11:49.740> you<00:11:49.920> let 00:11:50.150 --> 00:11:50.160 align:start position:0% disproved it then you'll then you let 00:11:50.160 --> 00:11:52.190 align:start position:0% disproved it then you'll then you let the<00:11:50.279> hypothesis<00:11:50.880> stand<00:11:51.180> still 00:11:52.190 --> 00:11:52.200 align:start position:0% the hypothesis stand still 00:11:52.200 --> 00:11:54.889 align:start position:0% the hypothesis stand still they'll<00:11:52.800> prove<00:11:53.100> an<00:11:53.160> otherwise 00:11:54.889 --> 00:11:54.899 align:start position:0% they'll prove an otherwise 00:11:54.899 --> 00:11:57.590 align:start position:0% they'll prove an otherwise and<00:11:55.740> if<00:11:56.339> you're<00:11:56.459> wondering<00:11:56.820> what<00:11:57.060> this<00:11:57.300> is 00:11:57.590 --> 00:11:57.600 align:start position:0% and if you're wondering what this is 00:11:57.600 --> 00:11:59.389 align:start position:0% and if you're wondering what this is you've<00:11:58.440> probably<00:11:58.560> most<00:11:58.920> of<00:11:59.040> you<00:11:59.160> have 00:11:59.389 --> 00:11:59.399 align:start position:0% you've probably most of you have 00:11:59.399 --> 00:12:01.310 align:start position:0% you've probably most of you have probably<00:11:59.579> seen<00:11:59.880> Game<00:12:00.180> of<00:12:00.360> Life<00:12:00.540> it's<00:12:00.899> it's<00:12:00.959> the 00:12:01.310 --> 00:12:01.320 align:start position:0% probably seen Game of Life it's it's the 00:12:01.320 --> 00:12:03.050 align:start position:0% probably seen Game of Life it's it's the idea<00:12:01.560> that<00:12:01.800> you<00:12:01.980> know<00:12:02.040> you<00:12:02.160> you<00:12:02.339> can<00:12:02.640> take<00:12:02.820> a 00:12:03.050 --> 00:12:03.060 align:start position:0% idea that you know you you can take a 00:12:03.060 --> 00:12:06.350 align:start position:0% idea that you know you you can take a bunch<00:12:03.180> of<00:12:03.420> very<00:12:04.260> very<00:12:04.440> simple<00:12:04.740> rules<00:12:05.339> and<00:12:06.180> they 00:12:06.350 --> 00:12:06.360 align:start position:0% bunch of very very simple rules and they 00:12:06.360 --> 00:12:08.389 align:start position:0% bunch of very very simple rules and they can<00:12:06.540> lead<00:12:06.720> to<00:12:06.959> very<00:12:07.200> very<00:12:07.380> complex<00:12:07.800> behavior 00:12:08.389 --> 00:12:08.399 align:start position:0% can lead to very very complex behavior 00:12:08.399 --> 00:12:10.790 align:start position:0% can lead to very very complex behavior and<00:12:08.700> sort<00:12:09.120> of<00:12:09.240> agent-based<00:12:09.959> models<00:12:10.260> are<00:12:10.380> one 00:12:10.790 --> 00:12:10.800 align:start position:0% and sort of agent-based models are one 00:12:10.800 --> 00:12:12.949 align:start position:0% and sort of agent-based models are one thing<00:12:11.040> that<00:12:11.760> will<00:12:11.880> allow<00:12:12.240> you<00:12:12.360> to<00:12:12.540> analyze 00:12:12.949 --> 00:12:12.959 align:start position:0% thing that will allow you to analyze 00:12:12.959 --> 00:12:17.210 align:start position:0% thing that will allow you to analyze this<00:12:13.140> complex<00:12:13.440> Behavior 00:12:17.210 --> 00:12:17.220 align:start position:0% 00:12:17.220 --> 00:12:20.569 align:start position:0% so<00:12:17.820> yeah<00:12:18.500> uh<00:12:19.500> definition<00:12:19.740> of<00:12:20.220> what<00:12:20.399> an 00:12:20.569 --> 00:12:20.579 align:start position:0% so yeah uh definition of what an 00:12:20.579 --> 00:12:23.110 align:start position:0% so yeah uh definition of what an agent-based<00:12:21.180> model<00:12:21.360> is<00:12:21.600> from<00:12:22.019> from<00:12:22.260> Wikipedia 00:12:23.110 --> 00:12:23.120 align:start position:0% agent-based model is from from Wikipedia 00:12:23.120 --> 00:12:26.449 align:start position:0% agent-based model is from from Wikipedia and<00:12:24.120> everyone's<00:12:24.959> favorite<00:12:25.140> agent<00:12:25.740> and<00:12:26.220> quite 00:12:26.449 --> 00:12:26.459 align:start position:0% and everyone's favorite agent and quite 00:12:26.459 --> 00:12:28.069 align:start position:0% and everyone's favorite agent and quite often<00:12:26.700> you<00:12:26.820> want<00:12:27.000> a<00:12:27.120> lot<00:12:27.240> of<00:12:27.360> Agents<00:12:27.720> or<00:12:27.839> a<00:12:28.019> lot 00:12:28.069 --> 00:12:28.079 align:start position:0% often you want a lot of Agents or a lot 00:12:28.079 --> 00:12:31.670 align:start position:0% often you want a lot of Agents or a lot of<00:12:28.140> similar<00:12:28.500> agents<00:12:28.920> so<00:12:29.700> uh<00:12:30.660> agent<00:12:31.260> Smith<00:12:31.440> is 00:12:31.670 --> 00:12:31.680 align:start position:0% of similar agents so uh agent Smith is 00:12:31.680 --> 00:12:33.530 align:start position:0% of similar agents so uh agent Smith is good<00:12:31.860> I've<00:12:32.399> used<00:12:32.640> this<00:12:32.820> I've<00:12:33.000> used<00:12:33.360> this 00:12:33.530 --> 00:12:33.540 align:start position:0% good I've used this I've used this 00:12:33.540 --> 00:12:35.750 align:start position:0% good I've used this I've used this picture<00:12:33.720> actually<00:12:34.019> twice<00:12:34.440> I<00:12:34.680> I<00:12:34.860> was<00:12:35.100> when<00:12:35.640> you 00:12:35.750 --> 00:12:35.760 align:start position:0% picture actually twice I I was when you 00:12:35.760 --> 00:12:37.610 align:start position:0% picture actually twice I I was when you talk<00:12:35.940> about<00:12:36.120> civil<00:12:36.540> attacks<00:12:36.959> I<00:12:37.019> like<00:12:37.320> to<00:12:37.500> talk 00:12:37.610 --> 00:12:37.620 align:start position:0% talk about civil attacks I like to talk 00:12:37.620 --> 00:12:39.410 align:start position:0% talk about civil attacks I like to talk I<00:12:38.040> like<00:12:38.160> to<00:12:38.279> use<00:12:38.399> that<00:12:38.640> picture<00:12:38.820> but<00:12:39.060> here<00:12:39.300> it's 00:12:39.410 --> 00:12:39.420 align:start position:0% I like to use that picture but here it's 00:12:39.420 --> 00:12:41.269 align:start position:0% I like to use that picture but here it's not<00:12:39.600> about<00:12:39.720> civil<00:12:40.140> attacks<00:12:40.560> here<00:12:41.040> they're 00:12:41.269 --> 00:12:41.279 align:start position:0% not about civil attacks here they're 00:12:41.279 --> 00:12:42.769 align:start position:0% not about civil attacks here they're good<00:12:41.579> agents<00:12:41.880> who<00:12:42.060> are<00:12:42.300> stressing<00:12:42.660> your 00:12:42.769 --> 00:12:42.779 align:start position:0% good agents who are stressing your 00:12:42.779 --> 00:12:46.670 align:start position:0% good agents who are stressing your protocol 00:12:46.670 --> 00:12:46.680 align:start position:0% 00:12:46.680 --> 00:12:48.949 align:start position:0% so<00:12:47.160> in<00:12:47.279> terms<00:12:47.579> of<00:12:47.700> you<00:12:47.940> know<00:12:48.060> what<00:12:48.360> type<00:12:48.779> of 00:12:48.949 --> 00:12:48.959 align:start position:0% so in terms of you know what type of 00:12:48.959 --> 00:12:50.990 align:start position:0% so in terms of you know what type of Agents<00:12:49.380> you<00:12:49.440> you<00:12:49.620> would<00:12:49.800> find<00:12:50.040> in<00:12:50.220> agent-based 00:12:50.990 --> 00:12:51.000 align:start position:0% Agents you you would find in agent-based 00:12:51.000 --> 00:12:54.050 align:start position:0% Agents you you would find in agent-based modeling<00:12:51.440> there<00:12:52.440> are<00:12:52.620> the<00:12:53.100> the<00:12:53.220> simplest<00:12:53.820> ones 00:12:54.050 --> 00:12:54.060 align:start position:0% modeling there are the the simplest ones 00:12:54.060 --> 00:12:56.629 align:start position:0% modeling there are the the simplest ones are<00:12:54.240> what<00:12:54.420> I<00:12:54.779> call<00:12:54.959> zero<00:12:55.440> intelligence<00:12:55.980> which 00:12:56.629 --> 00:12:56.639 align:start position:0% are what I call zero intelligence which 00:12:56.639 --> 00:12:59.150 align:start position:0% are what I call zero intelligence which is<00:12:56.760> a<00:12:56.880> bit<00:12:57.000> insulting<00:12:57.480> but<00:12:57.839> uh<00:12:58.200> what<00:12:58.800> it<00:12:58.920> what 00:12:59.150 --> 00:12:59.160 align:start position:0% is a bit insulting but uh what it what 00:12:59.160 --> 00:13:00.590 align:start position:0% is a bit insulting but uh what it what it<00:12:59.279> means<00:12:59.579> is<00:12:59.700> that<00:12:59.940> they're<00:13:00.060> not<00:13:00.300> learning 00:13:00.590 --> 00:13:00.600 align:start position:0% it means is that they're not learning 00:13:00.600 --> 00:13:02.449 align:start position:0% it means is that they're not learning and<00:13:00.779> they're<00:13:00.959> not<00:13:01.139> optimizing<00:13:01.680> you<00:13:01.920> just<00:13:02.160> say 00:13:02.449 --> 00:13:02.459 align:start position:0% and they're not optimizing you just say 00:13:02.459 --> 00:13:04.970 align:start position:0% and they're not optimizing you just say this<00:13:03.300> is<00:13:03.480> the<00:13:03.660> state<00:13:03.899> of<00:13:04.200> the<00:13:04.380> world<00:13:04.560> and<00:13:04.800> if 00:13:04.970 --> 00:13:04.980 align:start position:0% this is the state of the world and if 00:13:04.980 --> 00:13:06.350 align:start position:0% this is the state of the world and if this<00:13:05.160> is<00:13:05.279> the<00:13:05.399> state<00:13:05.579> then<00:13:05.820> they're<00:13:06.000> gonna<00:13:06.120> do 00:13:06.350 --> 00:13:06.360 align:start position:0% this is the state then they're gonna do 00:13:06.360 --> 00:13:07.670 align:start position:0% this is the state then they're gonna do this<00:13:06.540> and<00:13:06.779> if<00:13:06.959> the<00:13:07.079> state<00:13:07.200> is<00:13:07.440> something 00:13:07.670 --> 00:13:07.680 align:start position:0% this and if the state is something 00:13:07.680 --> 00:13:09.829 align:start position:0% this and if the state is something different<00:13:07.980> they're<00:13:08.399> going<00:13:08.579> to<00:13:08.700> do<00:13:08.820> that<00:13:09.000> so 00:13:09.829 --> 00:13:09.839 align:start position:0% different they're going to do that so 00:13:09.839 --> 00:13:11.690 align:start position:0% different they're going to do that so you<00:13:10.139> know<00:13:10.200> they're<00:13:10.440> agents 00:13:11.690 --> 00:13:11.700 align:start position:0% you know they're agents 00:13:11.700 --> 00:13:14.449 align:start position:0% you know they're agents that<00:13:12.240> have<00:13:12.420> hard-coded<00:13:13.079> actions 00:13:14.449 --> 00:13:14.459 align:start position:0% that have hard-coded actions 00:13:14.459 --> 00:13:16.310 align:start position:0% that have hard-coded actions and<00:13:15.000> that's<00:13:15.120> what<00:13:15.360> they<00:13:15.480> do<00:13:15.660> they're<00:13:15.899> the 00:13:16.310 --> 00:13:16.320 align:start position:0% and that's what they do they're the 00:13:16.320 --> 00:13:17.990 align:start position:0% and that's what they do they're the simplest<00:13:16.680> to<00:13:16.860> set<00:13:16.980> up<00:13:17.160> they're<00:13:17.399> the<00:13:17.639> simplest 00:13:17.990 --> 00:13:18.000 align:start position:0% simplest to set up they're the simplest 00:13:18.000 --> 00:13:19.430 align:start position:0% simplest to set up they're the simplest to<00:13:18.240> understand 00:13:19.430 --> 00:13:19.440 align:start position:0% to understand 00:13:19.440 --> 00:13:21.949 align:start position:0% to understand and<00:13:20.279> of<00:13:20.820> course<00:13:20.940> if<00:13:21.120> you<00:13:21.300> hard<00:13:21.480> code<00:13:21.720> the 00:13:21.949 --> 00:13:21.959 align:start position:0% and of course if you hard code the 00:13:21.959 --> 00:13:23.990 align:start position:0% and of course if you hard code the optimal<00:13:22.440> actions<00:13:22.860> then<00:13:23.100> they're<00:13:23.519> perfectly 00:13:23.990 --> 00:13:24.000 align:start position:0% optimal actions then they're perfectly 00:13:24.000 --> 00:13:25.069 align:start position:0% optimal actions then they're perfectly good 00:13:25.069 --> 00:13:25.079 align:start position:0% good 00:13:25.079 --> 00:13:27.110 align:start position:0% good if<00:13:25.560> you<00:13:25.680> don't<00:13:25.860> then<00:13:26.220> they're<00:13:26.399> only<00:13:26.579> as<00:13:26.820> useful 00:13:27.110 --> 00:13:27.120 align:start position:0% if you don't then they're only as useful 00:13:27.120 --> 00:13:28.790 align:start position:0% if you don't then they're only as useful as<00:13:27.300> the<00:13:27.660> actions<00:13:28.019> that<00:13:28.139> you've<00:13:28.320> that<00:13:28.560> you've 00:13:28.790 --> 00:13:28.800 align:start position:0% as the actions that you've that you've 00:13:28.800 --> 00:13:30.410 align:start position:0% as the actions that you've that you've hard-coded 00:13:30.410 --> 00:13:30.420 align:start position:0% hard-coded 00:13:30.420 --> 00:13:32.509 align:start position:0% hard-coded and<00:13:30.839> so<00:13:31.019> the<00:13:31.200> next<00:13:31.320> level<00:13:31.560> you<00:13:31.860> you<00:13:32.040> can<00:13:32.399> think 00:13:32.509 --> 00:13:32.519 align:start position:0% and so the next level you you can think 00:13:32.519 --> 00:13:34.550 align:start position:0% and so the next level you you can think okay<00:13:32.760> you<00:13:33.060> know<00:13:33.180> each<00:13:33.420> agent<00:13:33.839> I'm<00:13:34.019> not<00:13:34.440> going 00:13:34.550 --> 00:13:34.560 align:start position:0% okay you know each agent I'm not going 00:13:34.560 --> 00:13:36.769 align:start position:0% okay you know each agent I'm not going to<00:13:34.740> hard<00:13:34.980> code<00:13:35.220> the<00:13:35.459> actions<00:13:35.820> a<00:13:36.000> priori<00:13:36.540> but 00:13:36.769 --> 00:13:36.779 align:start position:0% to hard code the actions a priori but 00:13:36.779 --> 00:13:40.009 align:start position:0% to hard code the actions a priori but I'm<00:13:36.959> gonna<00:13:37.139> tell<00:13:37.500> the<00:13:38.459> agent<00:13:38.880> exactly<00:13:39.779> what 00:13:40.009 --> 00:13:40.019 align:start position:0% I'm gonna tell the agent exactly what 00:13:40.019 --> 00:13:42.110 align:start position:0% I'm gonna tell the agent exactly what the<00:13:40.200> environment<00:13:40.680> what<00:13:41.220> the<00:13:41.399> rules<00:13:41.700> of<00:13:41.880> the 00:13:42.110 --> 00:13:42.120 align:start position:0% the environment what the rules of the 00:13:42.120 --> 00:13:44.030 align:start position:0% the environment what the rules of the environment<00:13:42.540> that<00:13:42.839> they're<00:13:43.200> in 00:13:44.030 --> 00:13:44.040 align:start position:0% environment that they're in 00:13:44.040 --> 00:13:47.150 align:start position:0% environment that they're in are<00:13:44.940> exactly<00:13:45.420> what<00:13:45.660> the<00:13:45.839> rewards<00:13:46.680> are<00:13:46.980> for 00:13:47.150 --> 00:13:47.160 align:start position:0% are exactly what the rewards are for 00:13:47.160 --> 00:13:48.470 align:start position:0% are exactly what the rewards are for interacting<00:13:47.700> with<00:13:47.880> this<00:13:48.060> environment 00:13:48.470 --> 00:13:48.480 align:start position:0% interacting with this environment 00:13:48.480 --> 00:13:50.210 align:start position:0% interacting with this environment according<00:13:49.019> to<00:13:49.139> the<00:13:49.380> rules 00:13:50.210 --> 00:13:50.220 align:start position:0% according to the rules 00:13:50.220 --> 00:13:51.949 align:start position:0% according to the rules and<00:13:50.700> I'm<00:13:50.820> going<00:13:51.000> to<00:13:51.120> optimize<00:13:51.480> in<00:13:51.720> other<00:13:51.839> words 00:13:51.949 --> 00:13:51.959 align:start position:0% and I'm going to optimize in other words 00:13:51.959 --> 00:13:54.410 align:start position:0% and I'm going to optimize in other words I'm<00:13:52.260> going<00:13:52.560> to<00:13:52.740> solve<00:13:53.339> for<00:13:53.760> the<00:13:54.000> optimal 00:13:54.410 --> 00:13:54.420 align:start position:0% I'm going to solve for the optimal 00:13:54.420 --> 00:13:56.690 align:start position:0% I'm going to solve for the optimal actions<00:13:54.959> and<00:13:55.740> that's<00:13:55.860> something<00:13:56.100> that<00:13:56.399> comes 00:13:56.690 --> 00:13:56.700 align:start position:0% actions and that's something that comes 00:13:56.700 --> 00:13:58.670 align:start position:0% actions and that's something that comes under<00:13:56.880> you<00:13:57.480> know<00:13:57.600> the<00:13:57.779> name<00:13:57.899> either<00:13:58.200> mark<00:13:58.500> of 00:13:58.670 --> 00:13:58.680 align:start position:0% under you know the name either mark of 00:13:58.680 --> 00:14:00.170 align:start position:0% under you know the name either mark of decision<00:13:58.980> processes<00:13:59.639> if<00:13:59.820> you're<00:13:59.940> doing 00:14:00.170 --> 00:14:00.180 align:start position:0% decision processes if you're doing 00:14:00.180 --> 00:14:02.930 align:start position:0% decision processes if you're doing discrete<00:14:00.720> time<00:14:00.899> steps<00:14:01.380> or<00:14:01.680> control<00:14:02.339> theory 00:14:02.930 --> 00:14:02.940 align:start position:0% discrete time steps or control theory 00:14:02.940 --> 00:14:06.230 align:start position:0% discrete time steps or control theory stochastic<00:14:03.480> control<00:14:04.040> theory<00:14:05.040> it's<00:14:05.820> it's<00:14:05.880> a 00:14:06.230 --> 00:14:06.240 align:start position:0% stochastic control theory it's it's a 00:14:06.240 --> 00:14:08.750 align:start position:0% stochastic control theory it's it's a reasonably<00:14:06.600> well<00:14:06.839> established<00:14:07.380> field 00:14:08.750 --> 00:14:08.760 align:start position:0% reasonably well established field 00:14:08.760 --> 00:14:10.430 align:start position:0% reasonably well established field and<00:14:09.420> you<00:14:09.600> know<00:14:09.720> there<00:14:09.959> are<00:14:10.139> a<00:14:10.200> bunch<00:14:10.320> of 00:14:10.430 --> 00:14:10.440 align:start position:0% and you know there are a bunch of 00:14:10.440 --> 00:14:12.170 align:start position:0% and you know there are a bunch of algorithms<00:14:11.040> I<00:14:11.279> could<00:14:11.459> spend<00:14:11.700> hours<00:14:11.880> talking 00:14:12.170 --> 00:14:12.180 align:start position:0% algorithms I could spend hours talking 00:14:12.180 --> 00:14:13.790 align:start position:0% algorithms I could spend hours talking about<00:14:12.420> algorithms<00:14:13.139> that<00:14:13.320> they<00:14:13.500> have<00:14:13.620> for 00:14:13.790 --> 00:14:13.800 align:start position:0% about algorithms that they have for 00:14:13.800 --> 00:14:16.310 align:start position:0% about algorithms that they have for solving<00:14:14.220> problems<00:14:14.700> there<00:14:15.120> is<00:14:15.300> there<00:14:16.019> are<00:14:16.139> a 00:14:16.310 --> 00:14:16.320 align:start position:0% solving problems there is there are a 00:14:16.320 --> 00:14:17.990 align:start position:0% solving problems there is there are a few<00:14:16.440> problems<00:14:16.920> that<00:14:17.160> you<00:14:17.279> can<00:14:17.399> actually<00:14:17.579> solve 00:14:17.990 --> 00:14:18.000 align:start position:0% few problems that you can actually solve 00:14:18.000 --> 00:14:19.910 align:start position:0% few problems that you can actually solve by<00:14:18.240> hand<00:14:18.360> one<00:14:18.779> of<00:14:18.899> the<00:14:19.019> most<00:14:19.200> popular<00:14:19.440> is<00:14:19.740> the 00:14:19.910 --> 00:14:19.920 align:start position:0% by hand one of the most popular is the 00:14:19.920 --> 00:14:22.009 align:start position:0% by hand one of the most popular is the linear<00:14:20.220> quadratic<00:14:20.760> regulator<00:14:21.060> which 00:14:22.009 --> 00:14:22.019 align:start position:0% linear quadratic regulator which 00:14:22.019 --> 00:14:23.329 align:start position:0% linear quadratic regulator which you<00:14:22.680> know 00:14:23.329 --> 00:14:23.339 align:start position:0% you know 00:14:23.339 --> 00:14:24.710 align:start position:0% you know um together<00:14:23.700> with 00:14:24.710 --> 00:14:24.720 align:start position:0% um together with 00:14:24.720 --> 00:14:27.050 align:start position:0% um together with the<00:14:25.200> Kalman<00:14:25.500> filter<00:14:25.800> was<00:14:26.459> one<00:14:26.700> of<00:14:26.820> the<00:14:26.940> great 00:14:27.050 --> 00:14:27.060 align:start position:0% the Kalman filter was one of the great 00:14:27.060 --> 00:14:29.269 align:start position:0% the Kalman filter was one of the great successes<00:14:27.420> of<00:14:27.720> of<00:14:27.839> signs<00:14:28.500> of<00:14:28.620> the<00:14:28.740> 60s<00:14:29.100> you 00:14:29.269 --> 00:14:29.279 align:start position:0% successes of of signs of the 60s you 00:14:29.279 --> 00:14:31.610 align:start position:0% successes of of signs of the 60s you know<00:14:29.399> Blended<00:14:29.880> on<00:14:30.000> the<00:14:30.120> moon<00:14:30.240> and<00:14:30.480> all<00:14:30.600> that<00:14:30.779> so 00:14:31.610 --> 00:14:31.620 align:start position:0% know Blended on the moon and all that so 00:14:31.620 --> 00:14:34.970 align:start position:0% know Blended on the moon and all that so you<00:14:32.040> know<00:14:32.579> good<00:14:33.000> stuff<00:14:33.240> and<00:14:34.079> then<00:14:34.200> sort<00:14:34.500> of<00:14:34.620> the 00:14:34.970 --> 00:14:34.980 align:start position:0% you know good stuff and then sort of the 00:14:34.980 --> 00:14:36.590 align:start position:0% you know good stuff and then sort of the the<00:14:35.279> fancy<00:14:35.700> new<00:14:35.880> stuff<00:14:36.120> is<00:14:36.240> is<00:14:36.420> the 00:14:36.590 --> 00:14:36.600 align:start position:0% the fancy new stuff is is the 00:14:36.600 --> 00:14:37.970 align:start position:0% the fancy new stuff is is the reinforcement<00:14:37.139> learning<00:14:37.560> where<00:14:37.800> you 00:14:37.970 --> 00:14:37.980 align:start position:0% reinforcement learning where you 00:14:37.980 --> 00:14:39.230 align:start position:0% reinforcement learning where you actually<00:14:38.100> don't<00:14:38.339> have<00:14:38.459> to<00:14:38.639> tell<00:14:38.760> the<00:14:38.940> agents 00:14:39.230 --> 00:14:39.240 align:start position:0% actually don't have to tell the agents 00:14:39.240 --> 00:14:40.930 align:start position:0% actually don't have to tell the agents what<00:14:39.420> their<00:14:39.600> environment<00:14:40.019> is<00:14:40.260> they<00:14:40.680> just 00:14:40.930 --> 00:14:40.940 align:start position:0% what their environment is they just 00:14:40.940 --> 00:14:43.370 align:start position:0% what their environment is they just repeatedly<00:14:41.940> interact<00:14:42.360> with<00:14:42.480> it<00:14:42.720> observe<00:14:43.260> the 00:14:43.370 --> 00:14:43.380 align:start position:0% repeatedly interact with it observe the 00:14:43.380 --> 00:14:45.110 align:start position:0% repeatedly interact with it observe the outcomes<00:14:43.740> of<00:14:43.920> their<00:14:44.100> actions<00:14:44.459> observe<00:14:44.940> the 00:14:45.110 --> 00:14:45.120 align:start position:0% outcomes of their actions observe the 00:14:45.120 --> 00:14:47.930 align:start position:0% outcomes of their actions observe the rewards<00:14:45.600> and<00:14:46.199> update<00:14:46.500> their<00:14:46.680> behaviors<00:14:47.160> so 00:14:47.930 --> 00:14:47.940 align:start position:0% rewards and update their behaviors so 00:14:47.940 --> 00:14:49.550 align:start position:0% rewards and update their behaviors so these<00:14:48.180> are<00:14:48.300> these<00:14:48.600> are<00:14:48.720> the<00:14:48.899> type<00:14:49.019> of<00:14:49.199> Agents 00:14:49.550 --> 00:14:49.560 align:start position:0% these are these are the type of Agents 00:14:49.560 --> 00:14:50.930 align:start position:0% these are these are the type of Agents you<00:14:49.680> might<00:14:49.860> want<00:14:50.040> to<00:14:50.160> run 00:14:50.930 --> 00:14:50.940 align:start position:0% you might want to run 00:14:50.940 --> 00:14:53.269 align:start position:0% you might want to run you<00:14:51.540> know<00:14:51.660> on<00:14:52.079> top<00:14:52.199> of<00:14:52.320> your<00:14:52.500> environment<00:14:52.920> to 00:14:53.269 --> 00:14:53.279 align:start position:0% you know on top of your environment to 00:14:53.279 --> 00:14:54.829 align:start position:0% you know on top of your environment to see<00:14:53.459> what<00:14:53.639> is<00:14:53.760> happening<00:14:54.060> and<00:14:54.240> of<00:14:54.420> course<00:14:54.540> what 00:14:54.829 --> 00:14:54.839 align:start position:0% see what is happening and of course what 00:14:54.839 --> 00:14:56.629 align:start position:0% see what is happening and of course what is<00:14:55.019> what<00:14:55.260> is<00:14:55.440> appropriate<00:14:55.860> and<00:14:56.040> what<00:14:56.279> you<00:14:56.399> need 00:14:56.629 --> 00:14:56.639 align:start position:0% is what is appropriate and what you need 00:14:56.639 --> 00:14:59.449 align:start position:0% is what is appropriate and what you need will<00:14:57.300> very<00:14:57.720> much<00:14:57.839> depend<00:14:58.320> on<00:14:59.160> what<00:14:59.339> you're 00:14:59.449 --> 00:14:59.459 align:start position:0% will very much depend on what you're 00:14:59.459 --> 00:15:01.250 align:start position:0% will very much depend on what you're trying<00:14:59.760> to<00:14:59.940> simulate<00:15:00.300> what<00:15:00.540> you're<00:15:00.720> trying<00:15:00.959> to 00:15:01.250 --> 00:15:01.260 align:start position:0% trying to simulate what you're trying to 00:15:01.260 --> 00:15:04.370 align:start position:0% trying to simulate what you're trying to test<00:15:01.459> but<00:15:02.459> basically<00:15:02.940> this<00:15:03.180> is<00:15:03.300> your<00:15:03.480> zoo<00:15:03.720> and 00:15:04.370 --> 00:15:04.380 align:start position:0% test but basically this is your zoo and 00:15:04.380 --> 00:15:06.470 align:start position:0% test but basically this is your zoo and then<00:15:04.500> the<00:15:04.980> typical<00:15:05.220> setup<00:15:05.699> for<00:15:05.880> for<00:15:06.120> these 00:15:06.470 --> 00:15:06.480 align:start position:0% then the typical setup for for these 00:15:06.480 --> 00:15:08.449 align:start position:0% then the typical setup for for these things<00:15:06.660> sort<00:15:07.199> of<00:15:07.320> you<00:15:07.440> you<00:15:07.620> understand<00:15:08.040> you 00:15:08.449 --> 00:15:08.459 align:start position:0% things sort of you you understand you 00:15:08.459 --> 00:15:11.810 align:start position:0% things sort of you you understand you you<00:15:08.639> have<00:15:09.000> the<00:15:09.120> agent<00:15:09.480> agent<00:15:10.320> takes<00:15:10.620> action<00:15:10.980> it 00:15:11.810 --> 00:15:11.820 align:start position:0% you have the agent agent takes action it 00:15:11.820 --> 00:15:13.430 align:start position:0% you have the agent agent takes action it changes<00:15:12.240> the<00:15:12.480> environment<00:15:12.839> in<00:15:13.199> the<00:15:13.320> sense 00:15:13.430 --> 00:15:13.440 align:start position:0% changes the environment in the sense 00:15:13.440 --> 00:15:15.050 align:start position:0% changes the environment in the sense that<00:15:13.620> it<00:15:13.740> moves<00:15:14.040> it<00:15:14.160> from<00:15:14.399> the<00:15:14.579> current<00:15:14.699> state 00:15:15.050 --> 00:15:15.060 align:start position:0% that it moves it from the current state 00:15:15.060 --> 00:15:17.629 align:start position:0% that it moves it from the current state to<00:15:15.420> the<00:15:15.540> next<00:15:15.720> state<00:15:16.019> so<00:15:16.740> sort<00:15:17.040> of<00:15:17.160> new<00:15:17.339> state 00:15:17.629 --> 00:15:17.639 align:start position:0% to the next state so sort of new state 00:15:17.639 --> 00:15:20.509 align:start position:0% to the next state so sort of new state comes<00:15:18.060> out<00:15:18.180> a<00:15:18.959> reward<00:15:19.260> comes<00:15:19.680> out 00:15:20.509 --> 00:15:20.519 align:start position:0% comes out a reward comes out 00:15:20.519 --> 00:15:22.610 align:start position:0% comes out a reward comes out and<00:15:21.060> the<00:15:21.240> agent<00:15:21.600> takes<00:15:21.779> in<00:15:21.959> the<00:15:22.139> reward<00:15:22.380> and 00:15:22.610 --> 00:15:22.620 align:start position:0% and the agent takes in the reward and 00:15:22.620 --> 00:15:24.170 align:start position:0% and the agent takes in the reward and the<00:15:22.800> state<00:15:22.980> and<00:15:23.220> again<00:15:23.399> chooses<00:15:23.880> the<00:15:24.060> next 00:15:24.170 --> 00:15:24.180 align:start position:0% the state and again chooses the next 00:15:24.180 --> 00:15:26.389 align:start position:0% the state and again chooses the next action<00:15:24.480> and<00:15:24.720> and<00:15:24.899> you<00:15:25.199> repeat<00:15:25.380> and<00:15:26.160> of<00:15:26.279> course 00:15:26.389 --> 00:15:26.399 align:start position:0% action and and you repeat and of course 00:15:26.399 --> 00:15:28.430 align:start position:0% action and and you repeat and of course you<00:15:26.639> can<00:15:26.820> have<00:15:27.060> you<00:15:27.600> know<00:15:27.660> these<00:15:27.899> setups<00:15:28.320> that 00:15:28.430 --> 00:15:28.440 align:start position:0% you can have you know these setups that 00:15:28.440 --> 00:15:30.050 align:start position:0% you can have you know these setups that you<00:15:28.620> repeat 00:15:30.050 --> 00:15:30.060 align:start position:0% you repeat 00:15:30.060 --> 00:15:32.269 align:start position:0% you repeat sort<00:15:30.600> of<00:15:30.720> Forever<00:15:31.079> Until<00:15:31.440> Infinity<00:15:31.800> maybe 00:15:32.269 --> 00:15:32.279 align:start position:0% sort of Forever Until Infinity maybe 00:15:32.279 --> 00:15:33.949 align:start position:0% sort of Forever Until Infinity maybe with<00:15:32.519> some<00:15:32.760> discounting<00:15:33.360> or<00:15:33.600> maybe<00:15:33.720> you 00:15:33.949 --> 00:15:33.959 align:start position:0% with some discounting or maybe you 00:15:33.959 --> 00:15:35.329 align:start position:0% with some discounting or maybe you assume<00:15:34.320> that<00:15:34.440> there<00:15:34.560> is<00:15:34.680> some<00:15:34.860> steady<00:15:35.160> state 00:15:35.329 --> 00:15:35.339 align:start position:0% assume that there is some steady state 00:15:35.339 --> 00:15:37.430 align:start position:0% assume that there is some steady state or<00:15:36.000> there<00:15:36.180> will<00:15:36.360> be<00:15:36.480> a<00:15:36.600> terminal<00:15:36.899> time<00:15:37.199> when 00:15:37.430 --> 00:15:37.440 align:start position:0% or there will be a terminal time when 00:15:37.440 --> 00:15:39.889 align:start position:0% or there will be a terminal time when the<00:15:37.620> Game<00:15:37.800> Stops<00:15:38.339> or<00:15:38.579> whatever<00:15:39.000> problem 00:15:39.889 --> 00:15:39.899 align:start position:0% the Game Stops or whatever problem 00:15:39.899 --> 00:15:41.569 align:start position:0% the Game Stops or whatever problem finishes<00:15:40.500> then<00:15:40.680> you<00:15:40.860> evaluate<00:15:41.339> how 00:15:41.569 --> 00:15:41.579 align:start position:0% finishes then you evaluate how 00:15:41.579 --> 00:15:43.610 align:start position:0% finishes then you evaluate how everything<00:15:41.760> then<00:15:42.720> whether<00:15:43.019> it<00:15:43.260> will<00:15:43.380> end<00:15:43.500> well 00:15:43.610 --> 00:15:43.620 align:start position:0% everything then whether it will end well 00:15:43.620 --> 00:15:46.129 align:start position:0% everything then whether it will end well or<00:15:43.800> badly<00:15:44.579> and<00:15:44.940> then<00:15:45.000> one<00:15:45.300> thing<00:15:45.420> I<00:15:45.660> wanted<00:15:45.839> to 00:15:46.129 --> 00:15:46.139 align:start position:0% or badly and then one thing I wanted to 00:15:46.139 --> 00:15:48.230 align:start position:0% or badly and then one thing I wanted to point<00:15:46.500> out<00:15:46.680> here<00:15:46.980> is<00:15:47.220> because<00:15:47.519> it<00:15:47.820> will<00:15:48.060> be 00:15:48.230 --> 00:15:48.240 align:start position:0% point out here is because it will be 00:15:48.240 --> 00:15:49.850 align:start position:0% point out here is because it will be relevant<00:15:48.540> if<00:15:48.720> you're<00:15:49.019> looking<00:15:49.199> at<00:15:49.380> any<00:15:49.500> of<00:15:49.740> the 00:15:49.850 --> 00:15:49.860 align:start position:0% relevant if you're looking at any of the 00:15:49.860 --> 00:15:52.490 align:start position:0% relevant if you're looking at any of the code<00:15:50.100> that<00:15:50.279> we're<00:15:50.820> providing<00:15:51.420> is<00:15:52.139> that<00:15:52.380> the 00:15:52.490 --> 00:15:52.500 align:start position:0% code that we're providing is that the 00:15:52.500 --> 00:15:55.250 align:start position:0% code that we're providing is that the agent<00:15:52.860> as<00:15:53.100> it<00:15:53.519> learning<00:15:53.880> it<00:15:54.120> sort<00:15:54.360> of<00:15:54.480> it's<00:15:55.079> in 00:15:55.250 --> 00:15:55.260 align:start position:0% agent as it learning it sort of it's in 00:15:55.260 --> 00:15:58.009 align:start position:0% agent as it learning it sort of it's in a<00:15:55.440> state<00:15:55.560> it<00:15:55.980> takes<00:15:56.220> an<00:15:56.459> action<00:15:56.899> collects<00:15:57.899> the 00:15:58.009 --> 00:15:58.019 align:start position:0% a state it takes an action collects the 00:15:58.019 --> 00:15:59.750 align:start position:0% a state it takes an action collects the reward 00:15:59.750 --> 00:15:59.760 align:start position:0% reward 00:15:59.760 --> 00:16:02.090 align:start position:0% reward sees<00:16:00.480> the<00:16:00.660> new<00:16:00.779> state<00:16:01.079> and<00:16:01.440> decides<00:16:01.860> on<00:16:01.980> the 00:16:02.090 --> 00:16:02.100 align:start position:0% sees the new state and decides on the 00:16:02.100 --> 00:16:04.370 align:start position:0% sees the new state and decides on the new<00:16:02.279> action<00:16:02.579> and<00:16:03.240> if<00:16:03.360> you<00:16:03.540> record<00:16:03.720> this<00:16:04.139> that 00:16:04.370 --> 00:16:04.380 align:start position:0% new action and if you record this that 00:16:04.380 --> 00:16:05.810 align:start position:0% new action and if you record this that that's<00:16:04.560> sort<00:16:04.740> of<00:16:04.860> all<00:16:04.980> the<00:16:05.160> data<00:16:05.459> that<00:16:05.639> you 00:16:05.810 --> 00:16:05.820 align:start position:0% that's sort of all the data that you 00:16:05.820 --> 00:16:08.389 align:start position:0% that's sort of all the data that you need<00:16:05.940> to<00:16:06.240> train<00:16:06.420> the<00:16:06.660> agent<00:16:07.079> sort<00:16:07.800> of<00:16:07.920> offline 00:16:08.389 --> 00:16:08.399 align:start position:0% need to train the agent sort of offline 00:16:08.399 --> 00:16:10.009 align:start position:0% need to train the agent sort of offline separate<00:16:08.940> from<00:16:09.120> the<00:16:09.300> environment<00:16:09.660> if<00:16:09.899> you 00:16:10.009 --> 00:16:10.019 align:start position:0% separate from the environment if you 00:16:10.019 --> 00:16:12.410 align:start position:0% separate from the environment if you collect<00:16:10.320> these<00:16:10.560> sarsa<00:16:11.040> sequences<00:16:11.519> then<00:16:12.180> you 00:16:12.410 --> 00:16:12.420 align:start position:0% collect these sarsa sequences then you 00:16:12.420 --> 00:16:14.509 align:start position:0% collect these sarsa sequences then you can<00:16:12.480> train<00:16:12.660> the<00:16:12.959> agent<00:16:13.320> separate<00:16:14.160> from<00:16:14.339> your 00:16:14.509 --> 00:16:14.519 align:start position:0% can train the agent separate from your 00:16:14.519 --> 00:16:17.569 align:start position:0% can train the agent separate from your from<00:16:14.820> your<00:16:15.000> environment 00:16:17.569 --> 00:16:17.579 align:start position:0% 00:16:17.579 --> 00:16:19.610 align:start position:0% okay<00:16:18.000> so<00:16:18.300> that's<00:16:18.540> that's<00:16:18.779> not<00:16:19.079> so<00:16:19.260> important 00:16:19.610 --> 00:16:19.620 align:start position:0% okay so that's that's not so important 00:16:19.620 --> 00:16:21.230 align:start position:0% okay so that's that's not so important now<00:16:19.800> it<00:16:20.040> will<00:16:20.279> be<00:16:20.519> more<00:16:20.639> useful<00:16:21.000> information 00:16:21.230 --> 00:16:21.240 align:start position:0% now it will be more useful information 00:16:21.240 --> 00:16:23.930 align:start position:0% now it will be more useful information later 00:16:23.930 --> 00:16:23.940 align:start position:0% 00:16:23.940 --> 00:16:26.990 align:start position:0% right<00:16:24.480> and<00:16:25.260> I<00:16:25.500> think<00:16:25.620> I'll<00:16:25.800> hand<00:16:26.040> over<00:16:26.279> to<00:16:26.820> Tom 00:16:26.990 --> 00:16:27.000 align:start position:0% right and I think I'll hand over to Tom 00:16:27.000 --> 00:16:28.129 align:start position:0% right and I think I'll hand over to Tom now 00:16:28.129 --> 00:16:28.139 align:start position:0% now 00:16:28.139 --> 00:16:31.329 align:start position:0% now who<00:16:28.620> will<00:16:28.940> evoke<00:16:29.940> you<00:16:30.120> through 00:16:31.329 --> 00:16:31.339 align:start position:0% who will evoke you through 00:16:31.339 --> 00:16:35.210 align:start position:0% who will evoke you through the<00:16:32.339> you<00:16:32.760> know<00:16:32.880> the<00:16:33.120> Vega<00:16:33.480> Market<00:16:33.660> Sim 00:16:35.210 --> 00:16:35.220 align:start position:0% the you know the Vega Market Sim 00:16:35.220 --> 00:16:36.110 align:start position:0% the you know the Vega Market Sim um 00:16:36.110 --> 00:16:36.120 align:start position:0% um 00:16:36.120 --> 00:16:37.850 align:start position:0% um it's<00:16:36.600> a<00:16:36.720> workshop<00:16:37.019> so<00:16:37.199> if<00:16:37.380> you<00:16:37.500> have<00:16:37.620> questions 00:16:37.850 --> 00:16:37.860 align:start position:0% it's a workshop so if you have questions 00:16:37.860 --> 00:16:39.829 align:start position:0% it's a workshop so if you have questions I<00:16:38.339> think<00:16:38.639> the<00:16:38.820> gentleman<00:16:39.120> there<00:16:39.420> already<00:16:39.600> said 00:16:39.829 --> 00:16:39.839 align:start position:0% I think the gentleman there already said 00:16:39.839 --> 00:16:41.449 align:start position:0% I think the gentleman there already said yeah<00:16:40.139> you're<00:16:40.380> setting<00:16:40.680> a<00:16:40.800> perfect<00:16:40.920> example 00:16:41.449 --> 00:16:41.459 align:start position:0% yeah you're setting a perfect example 00:16:41.459 --> 00:16:46.490 align:start position:0% yeah you're setting a perfect example keep<00:16:41.880> asking<00:16:42.300> questions 00:16:46.490 --> 00:16:46.500 align:start position:0% 00:16:46.500 --> 00:17:09.650 align:start position:0% oh<00:16:46.860> do<00:16:46.980> we<00:16:47.160> need<00:16:47.279> a<00:16:47.399> microphone 00:17:09.650 --> 00:17:09.660 align:start position:0% 00:17:09.660 --> 00:17:11.630 align:start position:0% you<00:17:10.020> think 00:17:11.630 --> 00:17:11.640 align:start position:0% you think 00:17:11.640 --> 00:17:20.809 align:start position:0% you think thank<00:17:12.000> you<00:17:12.179> hello 00:17:20.809 --> 00:17:20.819 align:start position:0% 00:17:20.819 --> 00:17:22.669 align:start position:0% hello 00:17:22.669 --> 00:17:22.679 align:start position:0% hello 00:17:22.679 --> 00:17:27.110 align:start position:0% hello um<00:17:23.179> do<00:17:24.179> state<00:17:25.140> space 00:17:27.110 --> 00:17:27.120 align:start position:0% um do state space 00:17:27.120 --> 00:17:28.970 align:start position:0% um do state space approaches<00:17:27.780> have<00:17:28.140> any<00:17:28.319> role<00:17:28.620> to<00:17:28.679> play<00:17:28.799> in 00:17:28.970 --> 00:17:28.980 align:start position:0% approaches have any role to play in 00:17:28.980 --> 00:17:33.590 align:start position:0% approaches have any role to play in parameter<00:17:29.400> optimization 00:17:33.590 --> 00:17:33.600 align:start position:0% 00:17:33.600 --> 00:17:36.169 align:start position:0% like<00:17:34.500> a<00:17:34.679> control<00:17:34.860> control<00:17:35.340> theory<00:17:35.820> based 00:17:36.169 --> 00:17:36.179 align:start position:0% like a control control theory based 00:17:36.179 --> 00:17:38.990 align:start position:0% like a control control theory based approach<00:17:36.419> for<00:17:36.660> optimizing<00:17:37.380> a 00:17:38.990 --> 00:17:39.000 align:start position:0% approach for optimizing a 00:17:39.000 --> 00:17:41.330 align:start position:0% approach for optimizing a ffected<00:17:39.600> yeah<00:17:39.720> so<00:17:40.020> so<00:17:40.200> you<00:17:40.559> would<00:17:40.679> set<00:17:40.860> up<00:17:41.039> you 00:17:41.330 --> 00:17:41.340 align:start position:0% ffected yeah so so you would set up you 00:17:41.340 --> 00:17:43.549 align:start position:0% ffected yeah so so you would set up you know<00:17:41.400> your<00:17:41.520> environment<00:17:42.240> which<00:17:42.660> in<00:17:43.260> you<00:17:43.440> know 00:17:43.549 --> 00:17:43.559 align:start position:0% know your environment which in you know 00:17:43.559 --> 00:17:45.529 align:start position:0% know your environment which in you know in<00:17:43.799> in<00:17:43.919> the<00:17:44.100> case<00:17:44.220> which<00:17:44.640> we<00:17:44.880> will<00:17:45.059> show<00:17:45.240> would 00:17:45.529 --> 00:17:45.539 align:start position:0% in in the case which we will show would 00:17:45.539 --> 00:17:47.870 align:start position:0% in in the case which we will show would be<00:17:45.720> you<00:17:46.559> know<00:17:46.679> the<00:17:46.919> whole<00:17:47.100> Market<00:17:47.280> how<00:17:47.640> the 00:17:47.870 --> 00:17:47.880 align:start position:0% be you know the whole Market how the 00:17:47.880 --> 00:17:49.669 align:start position:0% be you know the whole Market how the trades<00:17:48.120> happen<00:17:48.299> how<00:17:48.600> the<00:17:48.780> orders<00:17:49.080> are<00:17:49.260> matched 00:17:49.669 --> 00:17:49.679 align:start position:0% trades happen how the orders are matched 00:17:49.679 --> 00:17:51.890 align:start position:0% trades happen how the orders are matched and<00:17:50.280> then<00:17:50.400> you<00:17:50.580> run<00:17:50.760> that<00:17:51.059> whole<00:17:51.660> thing 00:17:51.890 --> 00:17:51.900 align:start position:0% and then you run that whole thing 00:17:51.900 --> 00:17:53.630 align:start position:0% and then you run that whole thing through<00:17:52.140> the<00:17:52.320> simulation<00:17:52.799> see<00:17:53.160> what<00:17:53.400> happens 00:17:53.630 --> 00:17:53.640 align:start position:0% through the simulation see what happens 00:17:53.640 --> 00:17:55.549 align:start position:0% through the simulation see what happens and<00:17:54.299> then<00:17:54.419> you<00:17:54.600> want<00:17:54.720> my<00:17:54.900> want<00:17:55.140> to<00:17:55.320> do<00:17:55.380> the 00:17:55.549 --> 00:17:55.559 align:start position:0% and then you want my want to do the 00:17:55.559 --> 00:17:57.890 align:start position:0% and then you want my want to do the optimization<00:17:56.039> on<00:17:56.340> top<00:17:56.460> of<00:17:56.640> that<00:17:56.820> right<00:17:57.660> but 00:17:57.890 --> 00:17:57.900 align:start position:0% optimization on top of that right but 00:17:57.900 --> 00:17:59.510 align:start position:0% optimization on top of that right but that's<00:17:58.200> a<00:17:58.380> agent-based<00:17:59.100> approach<00:17:59.340> right 00:17:59.510 --> 00:17:59.520 align:start position:0% that's a agent-based approach right 00:17:59.520 --> 00:18:02.510 align:start position:0% that's a agent-based approach right there's<00:18:00.000> you<00:18:00.360> could<00:18:00.480> you<00:18:00.900> could<00:18:01.020> use<00:18:01.320> a 00:18:02.510 --> 00:18:02.520 align:start position:0% there's you could you could use a 00:18:02.520 --> 00:18:05.270 align:start position:0% there's you could you could use a uh<00:18:03.179> like<00:18:03.480> a<00:18:03.780> analytical<00:18:04.500> solution<00:18:04.860> so<00:18:05.039> that's 00:18:05.270 --> 00:18:05.280 align:start position:0% uh like a analytical solution so that's 00:18:05.280 --> 00:18:08.029 align:start position:0% uh like a analytical solution so that's let's<00:18:05.820> call<00:18:06.179> it<00:18:06.360> an<00:18:06.780> agent-based<00:18:07.559> approach<00:18:07.860> a 00:18:08.029 --> 00:18:08.039 align:start position:0% let's call it an agent-based approach a 00:18:08.039 --> 00:18:11.630 align:start position:0% let's call it an agent-based approach a numerical<00:18:08.580> approach<00:18:09.059> but<00:18:10.020> a<00:18:10.799> control<00:18:11.039> theory 00:18:11.630 --> 00:18:11.640 align:start position:0% numerical approach but a control theory 00:18:11.640 --> 00:18:14.210 align:start position:0% numerical approach but a control theory approach<00:18:12.600> yes<00:18:13.140> if<00:18:13.380> you<00:18:13.500> could<00:18:13.679> if<00:18:13.919> you<00:18:14.100> could 00:18:14.210 --> 00:18:14.220 align:start position:0% approach yes if you could if you could 00:18:14.220 --> 00:18:16.310 align:start position:0% approach yes if you could if you could if<00:18:14.580> you<00:18:14.700> have<00:18:14.820> an<00:18:14.940> environment 00:18:16.310 --> 00:18:16.320 align:start position:0% if you have an environment 00:18:16.320 --> 00:18:18.529 align:start position:0% if you have an environment which<00:18:16.860> is<00:18:17.039> sort<00:18:17.400> of<00:18:17.520> sufficiently<00:18:18.240> simple 00:18:18.529 --> 00:18:18.539 align:start position:0% which is sort of sufficiently simple 00:18:18.539 --> 00:18:21.230 align:start position:0% which is sort of sufficiently simple that<00:18:18.900> you<00:18:19.140> can<00:18:19.200> really<00:18:19.440> write<00:18:19.860> down<00:18:20.220> you<00:18:21.179> know 00:18:21.230 --> 00:18:21.240 align:start position:0% that you can really write down you know 00:18:21.240 --> 00:18:23.390 align:start position:0% that you can really write down you know all<00:18:21.480> that<00:18:21.720> state<00:18:22.020> transition<00:18:22.440> equations<00:18:22.980> then 00:18:23.390 --> 00:18:23.400 align:start position:0% all that state transition equations then 00:18:23.400 --> 00:18:25.850 align:start position:0% all that state transition equations then you<00:18:23.580> can<00:18:23.700> go<00:18:23.940> and<00:18:24.120> solve<00:18:24.480> it<00:18:24.600> through<00:18:25.020> you<00:18:25.799> know 00:18:25.850 --> 00:18:25.860 align:start position:0% you can go and solve it through you know 00:18:25.860 --> 00:18:28.130 align:start position:0% you can go and solve it through you know either<00:18:26.039> pen<00:18:26.340> and<00:18:26.520> paper<00:18:26.700> if<00:18:27.179> you're<00:18:27.539> supremely 00:18:28.130 --> 00:18:28.140 align:start position:0% either pen and paper if you're supremely 00:18:28.140 --> 00:18:30.110 align:start position:0% either pen and paper if you're supremely lucky<00:18:28.380> or<00:18:28.679> from<00:18:28.919> through<00:18:29.160> something<00:18:29.400> like<00:18:29.760> I 00:18:30.110 --> 00:18:30.120 align:start position:0% lucky or from through something like I 00:18:30.120 --> 00:18:31.490 align:start position:0% lucky or from through something like I mean<00:18:30.240> you<00:18:30.360> can<00:18:30.480> policy<00:18:30.780> iteration<00:18:31.260> value 00:18:31.490 --> 00:18:31.500 align:start position:0% mean you can policy iteration value 00:18:31.500 --> 00:18:34.669 align:start position:0% mean you can policy iteration value iteration<00:18:32.600> something<00:18:33.600> like<00:18:33.840> Matlab<00:18:34.260> rather 00:18:34.669 --> 00:18:34.679 align:start position:0% iteration something like Matlab rather 00:18:34.679 --> 00:18:36.650 align:start position:0% iteration something like Matlab rather well<00:18:35.400> that's<00:18:35.700> actually<00:18:35.880> numerical<00:18:36.299> but<00:18:36.480> you 00:18:36.650 --> 00:18:36.660 align:start position:0% well that's actually numerical but you 00:18:36.660 --> 00:18:37.909 align:start position:0% well that's actually numerical but you could<00:18:36.720> use 00:18:37.909 --> 00:18:37.919 align:start position:0% could use 00:18:37.919 --> 00:18:40.730 align:start position:0% could use um<00:18:37.980> software<00:18:38.700> obviously<00:18:39.120> to<00:18:39.299> yes<00:18:40.140> yeah<00:18:40.440> and 00:18:40.730 --> 00:18:40.740 align:start position:0% um software obviously to yes yeah and 00:18:40.740 --> 00:18:43.549 align:start position:0% um software obviously to yes yeah and there<00:18:41.160> is<00:18:41.280> software<00:18:41.520> out<00:18:41.760> there<00:18:41.880> yeah 00:18:43.549 --> 00:18:43.559 align:start position:0% there is software out there yeah 00:18:43.559 --> 00:18:46.909 align:start position:0% there is software out there yeah uh<00:18:44.100> does<00:18:44.340> this<00:18:44.580> work<00:18:44.700> for<00:18:44.880> creating<00:18:45.120> bots 00:18:46.909 --> 00:18:46.919 align:start position:0% uh does this work for creating bots 00:18:46.919 --> 00:18:48.950 align:start position:0% uh does this work for creating bots trading<00:18:47.580> Bots<00:18:47.760> yeah<00:18:48.299> I<00:18:48.419> mean<00:18:48.600> like<00:18:48.720> the<00:18:48.840> whole 00:18:48.950 --> 00:18:48.960 align:start position:0% trading Bots yeah I mean like the whole 00:18:48.960 --> 00:18:52.190 align:start position:0% trading Bots yeah I mean like the whole framework<00:18:49.320> you<00:18:49.440> have<00:18:49.620> here<00:18:50.220> yeah<00:18:50.820> so<00:18:51.240> we're<00:18:51.480> I 00:18:52.190 --> 00:18:52.200 align:start position:0% framework you have here yeah so we're I 00:18:52.200 --> 00:18:54.110 align:start position:0% framework you have here yeah so we're I mean<00:18:52.320> Tom<00:18:52.919> will<00:18:53.160> talk<00:18:53.400> through<00:18:53.580> that<00:18:53.760> so<00:18:53.940> so 00:18:54.110 --> 00:18:54.120 align:start position:0% mean Tom will talk through that so so 00:18:54.120 --> 00:18:56.150 align:start position:0% mean Tom will talk through that so so I'll<00:18:54.660> jump<00:18:54.840> a<00:18:55.020> bit<00:18:55.140> but<00:18:55.380> basically<00:18:55.740> you<00:18:56.039> know 00:18:56.150 --> 00:18:56.160 align:start position:0% I'll jump a bit but basically you know 00:18:56.160 --> 00:18:58.310 align:start position:0% I'll jump a bit but basically you know the<00:18:57.000> environment<00:18:57.360> on<00:18:57.600> its<00:18:57.780> own<00:18:57.840> if<00:18:58.020> it's<00:18:58.140> just 00:18:58.310 --> 00:18:58.320 align:start position:0% the environment on its own if it's just 00:18:58.320 --> 00:19:00.409 align:start position:0% the environment on its own if it's just the<00:18:58.500> market<00:18:58.679> you<00:18:59.460> know<00:18:59.520> it's<00:18:59.700> an<00:18:59.940> empty<00:19:00.240> Market 00:19:00.409 --> 00:19:00.419 align:start position:0% the market you know it's an empty Market 00:19:00.419 --> 00:19:03.650 align:start position:0% the market you know it's an empty Market it<00:19:01.260> hasn't<00:19:01.620> even<00:19:01.740> gone<00:19:01.980> out<00:19:02.220> of<00:19:03.120> the<00:19:03.299> opening 00:19:03.650 --> 00:19:03.660 align:start position:0% it hasn't even gone out of the opening 00:19:03.660 --> 00:19:05.570 align:start position:0% it hasn't even gone out of the opening auction<00:19:03.840> if<00:19:04.140> no<00:19:04.320> one<00:19:04.440> proposes<00:19:05.039> anything<00:19:05.280> so 00:19:05.570 --> 00:19:05.580 align:start position:0% auction if no one proposes anything so 00:19:05.580 --> 00:19:07.669 align:start position:0% auction if no one proposes anything so so<00:19:05.820> you<00:19:06.240> automatically<00:19:06.780> need<00:19:07.020> bots<00:19:07.320> so<00:19:07.559> we 00:19:07.669 --> 00:19:07.679 align:start position:0% so you automatically need bots so we 00:19:07.679 --> 00:19:09.950 align:start position:0% so you automatically need bots so we will<00:19:07.860> talk<00:19:08.100> a<00:19:08.700> bit<00:19:08.820> about<00:19:09.059> the<00:19:09.299> Bots<00:19:09.419> that<00:19:09.780> are 00:19:09.950 --> 00:19:09.960 align:start position:0% will talk a bit about the Bots that are 00:19:09.960 --> 00:19:12.289 align:start position:0% will talk a bit about the Bots that are provided<00:19:10.500> as<00:19:11.280> part<00:19:11.460> of<00:19:11.640> the<00:19:11.820> environment<00:19:12.179> and 00:19:12.289 --> 00:19:12.299 align:start position:0% provided as part of the environment and 00:19:12.299 --> 00:19:14.390 align:start position:0% provided as part of the environment and of<00:19:12.539> course<00:19:12.660> you<00:19:12.840> can<00:19:13.020> write<00:19:13.140> your<00:19:13.380> own<00:19:13.559> Bots 00:19:14.390 --> 00:19:14.400 align:start position:0% of course you can write your own Bots 00:19:14.400 --> 00:19:17.510 align:start position:0% of course you can write your own Bots uh<00:19:15.179> that<00:19:15.539> can<00:19:15.720> do<00:19:16.020> you<00:19:16.559> know<00:19:16.679> well<00:19:17.100> whatever 00:19:17.510 --> 00:19:17.520 align:start position:0% uh that can do you know well whatever 00:19:17.520 --> 00:19:19.730 align:start position:0% uh that can do you know well whatever they<00:19:17.820> want<00:19:18.000> to<00:19:18.059> do<00:19:18.240> we've<00:19:18.660> got<00:19:18.840> uh 00:19:19.730 --> 00:19:19.740 align:start position:0% they want to do we've got uh 00:19:19.740 --> 00:19:21.710 align:start position:0% they want to do we've got uh we've<00:19:20.280> got<00:19:20.400> some<00:19:20.580> basic<00:19:20.880> Market<00:19:21.120> making<00:19:21.419> Bots 00:19:21.710 --> 00:19:21.720 align:start position:0% we've got some basic Market making Bots 00:19:21.720 --> 00:19:23.450 align:start position:0% we've got some basic Market making Bots we've<00:19:22.020> got<00:19:22.200> some<00:19:22.380> basic<00:19:22.679> you<00:19:23.160> know<00:19:23.220> price 00:19:23.450 --> 00:19:23.460 align:start position:0% we've got some basic you know price 00:19:23.460 --> 00:19:26.930 align:start position:0% we've got some basic you know price taking<00:19:23.760> Bots<00:19:24.179> we've<00:19:24.600> got<00:19:24.799> some<00:19:25.799> basic 00:19:26.930 --> 00:19:26.940 align:start position:0% taking Bots we've got some basic 00:19:26.940 --> 00:19:29.810 align:start position:0% taking Bots we've got some basic um<00:19:27.440> momentum<00:19:28.440> Traders 00:19:29.810 --> 00:19:29.820 align:start position:0% um momentum Traders 00:19:29.820 --> 00:19:31.610 align:start position:0% um momentum Traders but<00:19:30.179> Don<00:19:30.419> will<00:19:30.660> talk<00:19:30.840> more<00:19:31.020> about<00:19:31.200> that<00:19:31.440> so 00:19:31.610 --> 00:19:31.620 align:start position:0% but Don will talk more about that so 00:19:31.620 --> 00:19:34.250 align:start position:0% but Don will talk more about that so I'll<00:19:31.860> hand<00:19:32.039> over<00:19:32.220> to<00:19:32.400> him 00:19:34.250 --> 00:19:34.260 align:start position:0% I'll hand over to him 00:19:34.260 --> 00:19:37.070 align:start position:0% I'll hand over to him just<00:19:34.860> a<00:19:35.039> quick<00:19:35.220> question<00:19:35.400> so<00:19:35.820> if 00:19:37.070 --> 00:19:37.080 align:start position:0% just a quick question so if 00:19:37.080 --> 00:19:39.830 align:start position:0% just a quick question so if this<00:19:37.320> type<00:19:37.500> of<00:19:37.679> systems<00:19:38.220> do<00:19:39.059> you<00:19:39.299> take<00:19:39.600> the 00:19:39.830 --> 00:19:39.840 align:start position:0% this type of systems do you take the 00:19:39.840 --> 00:19:41.870 align:start position:0% this type of systems do you take the code<00:19:40.080> from<00:19:40.500> what<00:19:40.799> you<00:19:40.980> are<00:19:41.160> testing<00:19:41.520> for 00:19:41.870 --> 00:19:41.880 align:start position:0% code from what you are testing for 00:19:41.880 --> 00:19:43.669 align:start position:0% code from what you are testing for instance<00:19:42.059> for<00:19:42.240> the<00:19:42.419> Vega<00:19:42.720> protocol<00:19:42.960> I<00:19:43.440> just 00:19:43.669 --> 00:19:43.679 align:start position:0% instance for the Vega protocol I just 00:19:43.679 --> 00:19:45.890 align:start position:0% instance for the Vega protocol I just quickly<00:19:44.100> check<00:19:44.340> that<00:19:44.520> it's<00:19:44.700> it's<00:19:45.000> all<00:19:45.299> go<00:19:45.539> code 00:19:45.890 --> 00:19:45.900 align:start position:0% quickly check that it's it's all go code 00:19:45.900 --> 00:19:49.669 align:start position:0% quickly check that it's it's all go code right<00:19:46.740> okay<00:19:47.700> so<00:19:48.059> do<00:19:48.360> you<00:19:48.600> take<00:19:48.960> this<00:19:49.260> code<00:19:49.440> and 00:19:49.669 --> 00:19:49.679 align:start position:0% right okay so do you take this code and 00:19:49.679 --> 00:19:51.650 align:start position:0% right okay so do you take this code and run<00:19:49.980> it<00:19:50.160> inside<00:19:50.340> your<00:19:50.640> simulation<00:19:51.059> or<00:19:51.360> do<00:19:51.480> you 00:19:51.650 --> 00:19:51.660 align:start position:0% run it inside your simulation or do you 00:19:51.660 --> 00:19:54.370 align:start position:0% run it inside your simulation or do you create<00:19:51.840> a<00:19:52.080> model<00:19:52.260> of<00:19:53.160> that 00:19:54.370 --> 00:19:54.380 align:start position:0% create a model of that 00:19:54.380 --> 00:19:58.430 align:start position:0% create a model of that okay<00:19:55.380> and<00:19:56.039> do<00:19:56.700> you<00:19:56.820> think<00:19:57.059> that<00:19:57.360> that's<00:19:57.720> that 00:19:58.430 --> 00:19:58.440 align:start position:0% okay and do you think that that's that 00:19:58.440 --> 00:20:01.610 align:start position:0% okay and do you think that that's that scalable<00:19:59.039> if<00:19:59.280> you<00:19:59.460> want<00:19:59.700> to<00:19:59.940> if<00:20:00.780> you<00:20:01.020> want<00:20:01.440> to 00:20:01.610 --> 00:20:01.620 align:start position:0% scalable if you want to if you want to 00:20:01.620 --> 00:20:03.070 align:start position:0% scalable if you want to if you want to simulate 00:20:03.070 --> 00:20:03.080 align:start position:0% simulate 00:20:03.080 --> 00:20:06.710 align:start position:0% simulate thousands<00:20:04.080> of<00:20:04.260> millions<00:20:04.799> of<00:20:05.480> Agents<00:20:06.480> because 00:20:06.710 --> 00:20:06.720 align:start position:0% thousands of millions of Agents because 00:20:06.720 --> 00:20:09.890 align:start position:0% thousands of millions of Agents because perhaps<00:20:07.440> you<00:20:07.679> need<00:20:07.860> you<00:20:08.280> need<00:20:08.460> that<00:20:08.760> or<00:20:09.539> do<00:20:09.720> you 00:20:09.890 --> 00:20:09.900 align:start position:0% perhaps you need you need that or do you 00:20:09.900 --> 00:20:11.630 align:start position:0% perhaps you need you need that or do you think<00:20:10.020> it<00:20:10.260> it<00:20:10.500> should<00:20:10.740> be 00:20:11.630 --> 00:20:11.640 align:start position:0% think it it should be 00:20:11.640 --> 00:20:14.029 align:start position:0% think it it should be more<00:20:12.360> in<00:20:12.660> some<00:20:12.720> cases<00:20:12.960> you<00:20:13.200> need<00:20:13.380> a<00:20:13.500> model<00:20:13.679> of 00:20:14.029 --> 00:20:14.039 align:start position:0% more in some cases you need a model of 00:20:14.039 --> 00:20:19.450 align:start position:0% more in some cases you need a model of what<00:20:14.340> you<00:20:14.640> are<00:20:14.820> actually<00:20:15.240> testing 00:20:19.450 --> 00:20:19.460 align:start position:0% 00:20:19.460 --> 00:20:22.250 align:start position:0% the<00:20:20.460> microphone<00:20:20.940> so<00:20:21.480> so<00:20:21.600> we're<00:20:21.840> running<00:20:22.020> the 00:20:22.250 --> 00:20:22.260 align:start position:0% the microphone so so we're running the 00:20:22.260 --> 00:20:24.350 align:start position:0% the microphone so so we're running the whole<00:20:22.440> Vega<00:20:22.860> stack<00:20:23.100> again<00:20:23.340> Tom<00:20:23.880> will<00:20:24.179> show 00:20:24.350 --> 00:20:24.360 align:start position:0% whole Vega stack again Tom will show 00:20:24.360 --> 00:20:26.150 align:start position:0% whole Vega stack again Tom will show that<00:20:24.539> but<00:20:24.780> you're<00:20:24.960> absolutely<00:20:25.380> right<00:20:25.620> and<00:20:25.919> in 00:20:26.150 --> 00:20:26.160 align:start position:0% that but you're absolutely right and in 00:20:26.160 --> 00:20:28.490 align:start position:0% that but you're absolutely right and in some<00:20:26.280> situations<00:20:26.840> especially<00:20:27.840> we<00:20:28.080> want<00:20:28.260> to<00:20:28.380> do 00:20:28.490 --> 00:20:28.500 align:start position:0% some situations especially we want to do 00:20:28.500 --> 00:20:30.529 align:start position:0% some situations especially we want to do reinforcement<00:20:29.100> learning<00:20:29.580> having<00:20:30.240> a 00:20:30.529 --> 00:20:30.539 align:start position:0% reinforcement learning having a 00:20:30.539 --> 00:20:32.390 align:start position:0% reinforcement learning having a simplified<00:20:30.900> model<00:20:31.320> on<00:20:31.620> which<00:20:31.799> you<00:20:31.980> can<00:20:32.160> train 00:20:32.390 --> 00:20:32.400 align:start position:0% simplified model on which you can train 00:20:32.400 --> 00:20:33.950 align:start position:0% simplified model on which you can train before<00:20:32.760> you<00:20:33.000> actually<00:20:33.179> go<00:20:33.419> on<00:20:33.600> to<00:20:33.720> the<00:20:33.840> full 00:20:33.950 --> 00:20:33.960 align:start position:0% before you actually go on to the full 00:20:33.960 --> 00:20:36.650 align:start position:0% before you actually go on to the full stack<00:20:34.320> which<00:20:34.679> will<00:20:34.919> be<00:20:35.240> inevitably<00:20:36.240> slower 00:20:36.650 --> 00:20:36.660 align:start position:0% stack which will be inevitably slower 00:20:36.660 --> 00:20:38.270 align:start position:0% stack which will be inevitably slower than<00:20:36.960> you<00:20:37.080> would<00:20:37.260> like<00:20:37.440> because<00:20:37.799> things<00:20:38.100> are 00:20:38.270 --> 00:20:38.280 align:start position:0% than you would like because things are 00:20:38.280 --> 00:20:40.430 align:start position:0% than you would like because things are never<00:20:38.520> as<00:20:38.820> fast<00:20:39.000> as<00:20:39.360> you<00:20:39.539> want 00:20:40.430 --> 00:20:40.440 align:start position:0% never as fast as you want 00:20:40.440 --> 00:20:42.409 align:start position:0% never as fast as you want would<00:20:40.980> be<00:20:41.160> useful<00:20:41.400> but<00:20:41.580> we<00:20:41.820> don't<00:20:42.120> have<00:20:42.240> that 00:20:42.409 --> 00:20:42.419 align:start position:0% would be useful but we don't have that 00:20:42.419 --> 00:20:44.330 align:start position:0% would be useful but we don't have that at<00:20:42.660> the<00:20:42.960> moment<00:20:43.140> we're<00:20:43.440> learning<00:20:44.039> on<00:20:44.160> the 00:20:44.330 --> 00:20:44.340 align:start position:0% at the moment we're learning on the 00:20:44.340 --> 00:20:46.010 align:start position:0% at the moment we're learning on the whole<00:20:44.460> thing<00:20:44.700> that's<00:20:45.240> why<00:20:45.480> it's<00:20:45.600> important 00:20:46.010 --> 00:20:46.020 align:start position:0% whole thing that's why it's important 00:20:46.020 --> 00:20:48.049 align:start position:0% whole thing that's why it's important that<00:20:46.260> we<00:20:46.380> use<00:20:46.860> an<00:20:47.039> algorithm<00:20:47.400> which<00:20:47.640> collects 00:20:48.049 --> 00:20:48.059 align:start position:0% that we use an algorithm which collects 00:20:48.059 --> 00:20:50.390 align:start position:0% that we use an algorithm which collects the<00:20:48.179> sarsa<00:20:48.660> sequences<00:20:49.140> and<00:20:49.799> so<00:20:49.919> then<00:20:50.100> I<00:20:50.280> can 00:20:50.390 --> 00:20:50.400 align:start position:0% the sarsa sequences and so then I can 00:20:50.400 --> 00:20:51.830 align:start position:0% the sarsa sequences and so then I can learn<00:20:50.520> offline<00:20:50.880> but<00:20:51.120> we<00:20:51.299> don't<00:20:51.480> have<00:20:51.600> model 00:20:51.830 --> 00:20:51.840 align:start position:0% learn offline but we don't have model 00:20:51.840 --> 00:20:53.870 align:start position:0% learn offline but we don't have model there<00:20:52.679> are<00:20:52.799> reinforcement<00:20:53.400> learning 00:20:53.870 --> 00:20:53.880 align:start position:0% there are reinforcement learning 00:20:53.880 --> 00:20:55.549 align:start position:0% there are reinforcement learning techniques<00:20:54.299> which<00:20:54.539> sort<00:20:54.780> of<00:20:54.900> build<00:20:55.080> up<00:20:55.320> model 00:20:55.549 --> 00:20:55.559 align:start position:0% techniques which sort of build up model 00:20:55.559 --> 00:20:57.470 align:start position:0% techniques which sort of build up model from<00:20:55.919> observations<00:20:56.520> and<00:20:56.880> you<00:20:57.000> can<00:20:57.120> do<00:20:57.299> a<00:20:57.419> lot 00:20:57.470 --> 00:20:57.480 align:start position:0% from observations and you can do a lot 00:20:57.480 --> 00:20:59.690 align:start position:0% from observations and you can do a lot of<00:20:57.660> clever<00:20:58.380> stuff<00:20:58.620> but<00:20:58.919> but<00:20:59.039> I'm<00:20:59.340> far<00:20:59.520> from 00:20:59.690 --> 00:20:59.700 align:start position:0% of clever stuff but but I'm far from 00:20:59.700 --> 00:21:01.490 align:start position:0% of clever stuff but but I'm far from being<00:20:59.880> an<00:21:00.059> expert<00:21:00.360> on<00:21:00.600> that<00:21:00.720> okay<00:21:01.020> thank<00:21:01.380> you 00:21:01.490 --> 00:21:01.500 align:start position:0% being an expert on that okay thank you 00:21:01.500 --> 00:21:04.490 align:start position:0% being an expert on that okay thank you so<00:21:01.919> so<00:21:02.039> one<00:21:02.700> thing<00:21:02.940> that<00:21:03.539> I<00:21:03.720> didn't<00:21:03.840> say<00:21:04.020> is<00:21:04.200> one 00:21:04.490 --> 00:21:04.500 align:start position:0% so so one thing that I didn't say is one 00:21:04.500 --> 00:21:07.010 align:start position:0% so so one thing that I didn't say is one reason<00:21:04.679> why<00:21:04.980> D5<00:21:05.400> is<00:21:05.640> so<00:21:05.760> good<00:21:05.940> for<00:21:06.240> agent-based 00:21:07.010 --> 00:21:07.020 align:start position:0% reason why D5 is so good for agent-based 00:21:07.020 --> 00:21:08.210 align:start position:0% reason why D5 is so good for agent-based modeling<00:21:07.260> is<00:21:07.380> you<00:21:07.559> know<00:21:07.620> you<00:21:07.799> can<00:21:07.860> try<00:21:08.039> and 00:21:08.210 --> 00:21:08.220 align:start position:0% modeling is you know you can try and 00:21:08.220 --> 00:21:09.490 align:start position:0% modeling is you know you can try and people<00:21:08.400> have<00:21:08.580> been<00:21:08.760> talking<00:21:09.000> about 00:21:09.490 --> 00:21:09.500 align:start position:0% people have been talking about 00:21:09.500 --> 00:21:11.630 align:start position:0% people have been talking about agent-based<00:21:10.500> modeling<00:21:10.860> in<00:21:11.039> the<00:21:11.220> in<00:21:11.400> the<00:21:11.520> real 00:21:11.630 --> 00:21:11.640 align:start position:0% agent-based modeling in the in the real 00:21:11.640 --> 00:21:13.370 align:start position:0% agent-based modeling in the in the real economy<00:21:12.000> and<00:21:12.179> economists<00:21:12.660> would<00:21:12.840> love<00:21:13.020> to<00:21:13.200> do 00:21:13.370 --> 00:21:13.380 align:start position:0% economy and economists would love to do 00:21:13.380 --> 00:21:15.169 align:start position:0% economy and economists would love to do that<00:21:13.559> but<00:21:14.160> they<00:21:14.280> don't<00:21:14.400> have<00:21:14.520> the<00:21:14.700> environment 00:21:15.169 --> 00:21:15.179 align:start position:0% that but they don't have the environment 00:21:15.179 --> 00:21:17.930 align:start position:0% that but they don't have the environment on<00:21:15.360> which<00:21:15.539> to<00:21:15.780> execute<00:21:16.200> it<00:21:16.380> and<00:21:17.039> in<00:21:17.220> D5<00:21:17.520> we<00:21:17.760> do 00:21:17.930 --> 00:21:17.940 align:start position:0% on which to execute it and in D5 we do 00:21:17.940 --> 00:21:19.850 align:start position:0% on which to execute it and in D5 we do have<00:21:18.120> that<00:21:18.360> because<00:21:18.900> things<00:21:19.260> are<00:21:19.440> typically 00:21:19.850 --> 00:21:19.860 align:start position:0% have that because things are typically 00:21:19.860 --> 00:21:22.250 align:start position:0% have that because things are typically open<00:21:20.100> source<00:21:20.640> you<00:21:21.299> know<00:21:21.360> I<00:21:21.600> can<00:21:21.720> go<00:21:21.900> and<00:21:22.080> take 00:21:22.250 --> 00:21:22.260 align:start position:0% open source you know I can go and take 00:21:22.260 --> 00:21:24.470 align:start position:0% open source you know I can go and take the<00:21:22.500> smart<00:21:22.679> contract<00:21:23.220> and<00:21:23.940> run<00:21:24.179> things 00:21:24.470 --> 00:21:24.480 align:start position:0% the smart contract and run things 00:21:24.480 --> 00:21:25.909 align:start position:0% the smart contract and run things through<00:21:24.720> the<00:21:24.900> smart<00:21:25.020> contract<00:21:25.440> I<00:21:25.620> don't<00:21:25.799> have 00:21:25.909 --> 00:21:25.919 align:start position:0% through the smart contract I don't have 00:21:25.919 --> 00:21:27.470 align:start position:0% through the smart contract I don't have to<00:21:26.039> create<00:21:26.220> the<00:21:26.460> environment<00:21:26.880> I<00:21:27.120> just<00:21:27.299> say 00:21:27.470 --> 00:21:27.480 align:start position:0% to create the environment I just say 00:21:27.480 --> 00:21:29.390 align:start position:0% to create the environment I just say okay<00:21:27.660> I<00:21:27.960> care<00:21:28.080> about<00:21:28.260> how<00:21:28.980> this<00:21:29.220> smart 00:21:29.390 --> 00:21:29.400 align:start position:0% okay I care about how this smart 00:21:29.400 --> 00:21:31.789 align:start position:0% okay I care about how this smart contract<00:21:29.880> interacts<00:21:30.360> with<00:21:30.480> this<00:21:30.720> one<00:21:30.900> I<00:21:31.559> take 00:21:31.789 --> 00:21:31.799 align:start position:0% contract interacts with this one I take 00:21:31.799 --> 00:21:33.770 align:start position:0% contract interacts with this one I take whatever<00:21:32.039> ganache<00:21:32.820> hard<00:21:32.940> head<00:21:33.179> I<00:21:33.419> put<00:21:33.600> it 00:21:33.770 --> 00:21:33.780 align:start position:0% whatever ganache hard head I put it 00:21:33.780 --> 00:21:35.930 align:start position:0% whatever ganache hard head I put it there<00:21:34.020> I<00:21:34.500> set<00:21:34.679> it<00:21:34.799> up<00:21:34.980> as<00:21:35.100> my<00:21:35.340> environment<00:21:35.700> and 00:21:35.930 --> 00:21:35.940 align:start position:0% there I set it up as my environment and 00:21:35.940 --> 00:21:37.909 align:start position:0% there I set it up as my environment and I<00:21:36.480> pump<00:21:36.659> thousands<00:21:37.320> and<00:21:37.440> thousands<00:21:37.799> of 00:21:37.909 --> 00:21:37.919 align:start position:0% I pump thousands and thousands of 00:21:37.919 --> 00:21:40.070 align:start position:0% I pump thousands and thousands of simulations<00:21:38.400> through<00:21:38.760> that<00:21:39.000> I<00:21:39.720> can't<00:21:39.840> do<00:21:39.960> it 00:21:40.070 --> 00:21:40.080 align:start position:0% simulations through that I can't do it 00:21:40.080 --> 00:21:41.930 align:start position:0% simulations through that I can't do it in<00:21:40.140> the<00:21:40.260> real<00:21:40.380> economy<00:21:41.039> but<00:21:41.220> here<00:21:41.400> we<00:21:41.580> can<00:21:41.760> so 00:21:41.930 --> 00:21:41.940 align:start position:0% in the real economy but here we can so 00:21:41.940 --> 00:21:43.430 align:start position:0% in the real economy but here we can so it's<00:21:42.120> awesome 00:21:43.430 --> 00:21:43.440 align:start position:0% it's awesome 00:21:43.440 --> 00:21:49.910 align:start position:0% it's awesome okay<00:21:43.919> more<00:21:44.280> questions 00:21:49.910 --> 00:21:49.920 align:start position:0% 00:21:49.920 --> 00:21:52.370 align:start position:0% [Music] 00:21:52.370 --> 00:21:52.380 align:start position:0% [Music] 00:21:52.380 --> 00:21:54.169 align:start position:0% [Music] okay<00:21:52.500> are<00:21:53.400> you<00:21:53.520> really<00:21:53.640> looking<00:21:53.820> at<00:21:54.059> things 00:21:54.169 --> 00:21:54.179 align:start position:0% okay are you really looking at things 00:21:54.179 --> 00:21:57.710 align:start position:0% okay are you really looking at things like<00:21:54.419> protocol<00:21:54.780> solvency<00:21:55.640> or<00:21:56.720> profitability 00:21:57.710 --> 00:21:57.720 align:start position:0% like protocol solvency or profitability 00:21:57.720 --> 00:21:59.930 align:start position:0% like protocol solvency or profitability of<00:21:58.080> certain<00:21:58.320> agents<00:21:58.980> that<00:21:59.400> are<00:21:59.520> performing 00:21:59.930 --> 00:21:59.940 align:start position:0% of certain agents that are performing 00:21:59.940 --> 00:22:02.270 align:start position:0% of certain agents that are performing trades<00:22:00.539> or<00:22:00.960> kind<00:22:01.440> of<00:22:01.620> what<00:22:01.740> are<00:22:01.860> the<00:22:01.980> reward 00:22:02.270 --> 00:22:02.280 align:start position:0% trades or kind of what are the reward 00:22:02.280 --> 00:22:03.770 align:start position:0% trades or kind of what are the reward metrics<00:22:02.700> so<00:22:02.940> I'm<00:22:03.059> assuming<00:22:03.299> they're<00:22:03.480> not<00:22:03.600> like 00:22:03.770 --> 00:22:03.780 align:start position:0% metrics so I'm assuming they're not like 00:22:03.780 --> 00:22:06.590 align:start position:0% metrics so I'm assuming they're not like bugs<00:22:04.200> but<00:22:04.380> more<00:22:04.559> financial<00:22:04.860> kind<00:22:05.700> of<00:22:05.820> outcomes 00:22:06.590 --> 00:22:06.600 align:start position:0% bugs but more financial kind of outcomes 00:22:06.600 --> 00:22:09.710 align:start position:0% bugs but more financial kind of outcomes so<00:22:07.140> so<00:22:07.200> for<00:22:07.679> us<00:22:07.860> it's<00:22:08.640> very<00:22:08.880> problem<00:22:09.120> problem 00:22:09.710 --> 00:22:09.720 align:start position:0% so so for us it's very problem problem 00:22:09.720 --> 00:22:11.930 align:start position:0% so so for us it's very problem problem specific<00:22:10.320> so<00:22:10.559> for<00:22:10.799> example<00:22:11.039> if<00:22:11.220> we<00:22:11.640> want<00:22:11.820> to 00:22:11.930 --> 00:22:11.940 align:start position:0% specific so for example if we want to 00:22:11.940 --> 00:22:13.730 align:start position:0% specific so for example if we want to test<00:22:12.299> you<00:22:12.600> know<00:22:12.720> what<00:22:13.080> some<00:22:13.260> of<00:22:13.440> the<00:22:13.559> network 00:22:13.730 --> 00:22:13.740 align:start position:0% test you know what some of the network 00:22:13.740 --> 00:22:16.310 align:start position:0% test you know what some of the network parameters<00:22:14.520> should<00:22:14.760> be<00:22:14.940> we<00:22:15.780> set<00:22:15.960> up<00:22:16.140> an 00:22:16.310 --> 00:22:16.320 align:start position:0% parameters should be we set up an 00:22:16.320 --> 00:22:17.930 align:start position:0% parameters should be we set up an environment<00:22:16.740> and<00:22:17.100> and<00:22:17.220> then<00:22:17.460> we<00:22:17.640> look<00:22:17.820> at 00:22:17.930 --> 00:22:17.940 align:start position:0% environment and and then we look at 00:22:17.940 --> 00:22:20.570 align:start position:0% environment and and then we look at things<00:22:18.240> like<00:22:18.720> you<00:22:19.620> know<00:22:19.679> if<00:22:19.799> if<00:22:19.980> I've<00:22:20.220> got<00:22:20.400> a 00:22:20.570 --> 00:22:20.580 align:start position:0% things like you know if if I've got a 00:22:20.580 --> 00:22:23.029 align:start position:0% things like you know if if I've got a rationally<00:22:20.880> behaving<00:22:21.419> Market<00:22:21.659> maker<00:22:22.260> and<00:22:22.799> the 00:22:23.029 --> 00:22:23.039 align:start position:0% rationally behaving Market maker and the 00:22:23.039 --> 00:22:25.610 align:start position:0% rationally behaving Market maker and the parameter<00:22:23.520> is<00:22:23.640> X<00:22:24.000> what<00:22:24.780> is<00:22:24.900> their<00:22:25.080> return<00:22:25.320> on 00:22:25.610 --> 00:22:25.620 align:start position:0% parameter is X what is their return on 00:22:25.620 --> 00:22:26.630 align:start position:0% parameter is X what is their return on Capital 00:22:26.630 --> 00:22:26.640 align:start position:0% Capital 00:22:26.640 --> 00:22:28.250 align:start position:0% Capital and<00:22:27.120> I'm<00:22:27.299> thinking<00:22:27.539> well<00:22:27.720> you<00:22:28.020> know<00:22:28.080> maybe 00:22:28.250 --> 00:22:28.260 align:start position:0% and I'm thinking well you know maybe 00:22:28.260 --> 00:22:30.230 align:start position:0% and I'm thinking well you know maybe this<00:22:28.559> is<00:22:28.740> letting<00:22:29.100> them<00:22:29.280> earn<00:22:29.820> too<00:22:29.940> much<00:22:30.120> money 00:22:30.230 --> 00:22:30.240 align:start position:0% this is letting them earn too much money 00:22:30.240 --> 00:22:32.630 align:start position:0% this is letting them earn too much money it<00:22:30.480> doesn't<00:22:30.659> make<00:22:30.840> sense<00:22:31.559> but<00:22:32.100> in<00:22:32.280> terms<00:22:32.520> of 00:22:32.630 --> 00:22:32.640 align:start position:0% it doesn't make sense but in terms of 00:22:32.640 --> 00:22:35.090 align:start position:0% it doesn't make sense but in terms of the<00:22:32.880> reinforcement<00:22:33.539> learning<00:22:33.960> guys 00:22:35.090 --> 00:22:35.100 align:start position:0% the reinforcement learning guys 00:22:35.100 --> 00:22:36.770 align:start position:0% the reinforcement learning guys you<00:22:35.640> you<00:22:35.820> would<00:22:36.000> typically<00:22:36.360> look<00:22:36.600> at 00:22:36.770 --> 00:22:36.780 align:start position:0% you you would typically look at 00:22:36.780 --> 00:22:39.110 align:start position:0% you you would typically look at Financial<00:22:37.020> rewards<00:22:37.799> and<00:22:38.159> then<00:22:38.280> yeah<00:22:38.580> you<00:22:38.760> can 00:22:39.110 --> 00:22:39.120 align:start position:0% Financial rewards and then yeah you can 00:22:39.120 --> 00:22:40.490 align:start position:0% Financial rewards and then yeah you can either<00:22:39.240> run<00:22:39.480> it<00:22:39.659> thinking<00:22:39.960> of<00:22:40.020> it<00:22:40.140> you<00:22:40.380> know 00:22:40.490 --> 00:22:40.500 align:start position:0% either run it thinking of it you know 00:22:40.500 --> 00:22:41.570 align:start position:0% either run it thinking of it you know maybe<00:22:40.620> you're<00:22:40.799> thinking<00:22:41.100> they're<00:22:41.220> trading 00:22:41.570 --> 00:22:41.580 align:start position:0% maybe you're thinking they're trading 00:22:41.580 --> 00:22:43.730 align:start position:0% maybe you're thinking they're trading perpetuals<00:22:42.240> so<00:22:42.419> it's<00:22:42.539> just<00:22:42.780> forever<00:22:43.140> or 00:22:43.730 --> 00:22:43.740 align:start position:0% perpetuals so it's just forever or 00:22:43.740 --> 00:22:45.049 align:start position:0% perpetuals so it's just forever or you're<00:22:43.860> thinking<00:22:44.159> that<00:22:44.340> they're<00:22:44.460> trading<00:22:44.940> a 00:22:45.049 --> 00:22:45.059 align:start position:0% you're thinking that they're trading a 00:22:45.059 --> 00:22:47.090 align:start position:0% you're thinking that they're trading a settlement<00:22:45.419> market<00:22:45.780> and<00:22:46.500> so<00:22:46.620> the<00:22:46.799> reward 00:22:47.090 --> 00:22:47.100 align:start position:0% settlement market and so the reward 00:22:47.100 --> 00:22:50.270 align:start position:0% settlement market and so the reward comes<00:22:47.460> at<00:22:47.580> settlement<00:22:48.380> but<00:22:49.380> it's<00:22:49.559> it's<00:22:49.799> very 00:22:50.270 --> 00:22:50.280 align:start position:0% comes at settlement but it's it's very 00:22:50.280 --> 00:22:51.470 align:start position:0% comes at settlement but it's it's very much<00:22:50.400> something<00:22:50.640> that<00:22:50.940> you<00:22:51.059> have<00:22:51.179> to<00:22:51.299> design 00:22:51.470 --> 00:22:51.480 align:start position:0% much something that you have to design 00:22:51.480 --> 00:22:53.990 align:start position:0% much something that you have to design for<00:22:51.960> the<00:22:52.140> specific<00:22:52.440> purpose<00:22:53.039> that<00:22:53.700> you<00:22:53.820> have 00:22:53.990 --> 00:22:54.000 align:start position:0% for the specific purpose that you have 00:22:54.000 --> 00:22:55.610 align:start position:0% for the specific purpose that you have in<00:22:54.120> mind<00:22:54.299> this<00:22:54.539> is<00:22:54.659> sort<00:22:54.840> of<00:22:54.900> more<00:22:55.020> the<00:22:55.200> toolbox 00:22:55.610 --> 00:22:55.620 align:start position:0% in mind this is sort of more the toolbox 00:22:55.620 --> 00:22:58.190 align:start position:0% in mind this is sort of more the toolbox and<00:22:56.280> I'm<00:22:56.400> gonna<00:22:56.580> you<00:22:57.059> know<00:22:57.120> wrap<00:22:57.840> up<00:22:57.960> the 00:22:58.190 --> 00:22:58.200 align:start position:0% and I'm gonna you know wrap up the 00:22:58.200 --> 00:23:00.049 align:start position:0% and I'm gonna you know wrap up the questions<00:22:58.380> hand<00:22:58.980> over<00:22:59.159> to<00:22:59.400> Tom<00:22:59.580> and<00:22:59.820> then<00:22:59.940> you 00:23:00.049 --> 00:23:00.059 align:start position:0% questions hand over to Tom and then you 00:23:00.059 --> 00:23:02.090 align:start position:0% questions hand over to Tom and then you can<00:23:00.240> ask<00:23:00.440> afterwards<00:23:01.440> because<00:23:01.620> I<00:23:01.860> have<00:23:01.980> a 00:23:02.090 --> 00:23:02.100 align:start position:0% can ask afterwards because I have a 00:23:02.100 --> 00:23:03.409 align:start position:0% can ask afterwards because I have a field<00:23:02.220> at<00:23:02.400> with<00:23:02.520> the<00:23:02.760> questions<00:23:02.880> we're<00:23:03.179> sort 00:23:03.409 --> 00:23:03.419 align:start position:0% field at with the questions we're sort 00:23:03.419 --> 00:23:05.570 align:start position:0% field at with the questions we're sort of<00:23:03.480> jumping<00:23:03.840> ahead<00:23:04.080> a<00:23:04.200> bit<00:23:04.320> so<00:23:04.500> I<00:23:04.919> I<00:23:05.280> want<00:23:05.460> to 00:23:05.570 --> 00:23:05.580 align:start position:0% of jumping ahead a bit so I I want to 00:23:05.580 --> 00:23:09.049 align:start position:0% of jumping ahead a bit so I I want to hand<00:23:05.700> over<00:23:05.940> thank<00:23:06.840> you 00:23:09.049 --> 00:23:09.059 align:start position:0% 00:23:09.059 --> 00:23:10.870 align:start position:0% okay 00:23:10.870 --> 00:23:10.880 align:start position:0% okay 00:23:10.880 --> 00:23:14.750 align:start position:0% okay so<00:23:12.080> yeah<00:23:13.080> discussing<00:23:13.980> the<00:23:14.220> market<00:23:14.400> simulator 00:23:14.750 --> 00:23:14.760 align:start position:0% so yeah discussing the market simulator 00:23:14.760 --> 00:23:17.029 align:start position:0% so yeah discussing the market simulator will<00:23:15.059> get<00:23:15.240> to<00:23:15.419> doing<00:23:16.260> so<00:23:16.440> ourselves<00:23:16.860> in<00:23:16.980> a 00:23:17.029 --> 00:23:17.039 align:start position:0% will get to doing so ourselves in a 00:23:17.039 --> 00:23:18.289 align:start position:0% will get to doing so ourselves in a minute<00:23:17.100> but<00:23:17.280> first<00:23:17.460> I<00:23:17.640> think<00:23:17.760> it's<00:23:17.820> useful<00:23:18.120> to 00:23:18.289 --> 00:23:18.299 align:start position:0% minute but first I think it's useful to 00:23:18.299 --> 00:23:22.010 align:start position:0% minute but first I think it's useful to go<00:23:18.539> through<00:23:18.840> and<00:23:19.679> yeah<00:23:19.799> to<00:23:20.159> cover<00:23:20.580> again 00:23:22.010 --> 00:23:22.020 align:start position:0% go through and yeah to cover again 00:23:22.020 --> 00:23:23.510 align:start position:0% go through and yeah to cover again slightly<00:23:22.559> more<00:23:22.679> technically<00:23:22.980> some<00:23:23.340> of<00:23:23.460> the 00:23:23.510 --> 00:23:23.520 align:start position:0% slightly more technically some of the 00:23:23.520 --> 00:23:25.669 align:start position:0% slightly more technically some of the some<00:23:23.760> of<00:23:23.880> the<00:23:24.000> questions<00:23:24.120> how<00:23:24.659> we<00:23:24.960> are<00:23:25.200> how<00:23:25.559> we 00:23:25.669 --> 00:23:25.679 align:start position:0% some of the questions how we are how we 00:23:25.679 --> 00:23:27.770 align:start position:0% some of the questions how we are how we run<00:23:25.860> these<00:23:26.039> simulations 00:23:27.770 --> 00:23:27.780 align:start position:0% run these simulations 00:23:27.780 --> 00:23:28.970 align:start position:0% run these simulations um<00:23:27.840> and<00:23:28.080> how 00:23:28.970 --> 00:23:28.980 align:start position:0% um and how 00:23:28.980 --> 00:23:32.330 align:start position:0% um and how how<00:23:29.340> we<00:23:29.700> get<00:23:30.299> interesting<00:23:30.780> results<00:23:30.960> out<00:23:31.340> so 00:23:32.330 --> 00:23:32.340 align:start position:0% how we get interesting results out so 00:23:32.340 --> 00:23:35.330 align:start position:0% how we get interesting results out so the<00:23:32.820> vegan<00:23:33.120> market<00:23:33.240> simulator<00:23:33.860> broadly<00:23:34.860> the 00:23:35.330 --> 00:23:35.340 align:start position:0% the vegan market simulator broadly the 00:23:35.340 --> 00:23:38.990 align:start position:0% the vegan market simulator broadly the way<00:23:35.460> that<00:23:36.380> Vega<00:23:37.380> itself<00:23:37.620> is<00:23:37.860> set<00:23:38.039> up<00:23:38.220> we<00:23:38.880> run 00:23:38.990 --> 00:23:39.000 align:start position:0% way that Vega itself is set up we run 00:23:39.000 --> 00:23:41.990 align:start position:0% way that Vega itself is set up we run with<00:23:39.539> a<00:23:39.780> tenement<00:23:40.140> consensus<00:23:40.740> layer<00:23:41.100> for 00:23:41.990 --> 00:23:42.000 align:start position:0% with a tenement consensus layer for 00:23:42.000 --> 00:23:43.850 align:start position:0% with a tenement consensus layer for those<00:23:42.179> who<00:23:42.299> don't<00:23:42.539> know<00:23:42.659> tenement<00:23:43.080> is<00:23:43.440> it's<00:23:43.679> a 00:23:43.850 --> 00:23:43.860 align:start position:0% those who don't know tenement is it's a 00:23:43.860 --> 00:23:47.090 align:start position:0% those who don't know tenement is it's a cosmos<00:23:44.220> based<00:23:44.900> consensus<00:23:45.900> the<00:23:46.740> problem<00:23:46.860> with 00:23:47.090 --> 00:23:47.100 align:start position:0% cosmos based consensus the problem with 00:23:47.100 --> 00:23:48.590 align:start position:0% cosmos based consensus the problem with that<00:23:47.280> is<00:23:47.520> that 00:23:48.590 --> 00:23:48.600 align:start position:0% that is that 00:23:48.600 --> 00:23:51.830 align:start position:0% that is that it's<00:23:49.500> generally<00:23:50.400> tied<00:23:50.700> to<00:23:51.059> our<00:23:51.480> block<00:23:51.659> time 00:23:51.830 --> 00:23:51.840 align:start position:0% it's generally tied to our block time 00:23:51.840 --> 00:23:53.690 align:start position:0% it's generally tied to our block time which<00:23:52.020> is<00:23:52.140> about<00:23:52.200> a<00:23:52.380> second<00:23:52.500> so<00:23:53.220> if<00:23:53.400> you<00:23:53.520> run 00:23:53.690 --> 00:23:53.700 align:start position:0% which is about a second so if you run 00:23:53.700 --> 00:23:56.510 align:start position:0% which is about a second so if you run the<00:23:53.880> whole<00:23:54.000> thing<00:23:54.260> you<00:23:55.260> can<00:23:55.380> watch<00:23:55.980> the<00:23:56.280> market 00:23:56.510 --> 00:23:56.520 align:start position:0% the whole thing you can watch the market 00:23:56.520 --> 00:23:58.490 align:start position:0% the whole thing you can watch the market going<00:23:56.820> second<00:23:57.120> by<00:23:57.419> second<00:23:57.600> and<00:23:58.260> you<00:23:58.380> can 00:23:58.490 --> 00:23:58.500 align:start position:0% going second by second and you can 00:23:58.500 --> 00:24:00.230 align:start position:0% going second by second and you can interact<00:23:58.799> with<00:23:58.919> it<00:23:59.100> but 00:24:00.230 --> 00:24:00.240 align:start position:0% interact with it but 00:24:00.240 --> 00:24:02.390 align:start position:0% interact with it but you<00:24:00.780> can't<00:24:00.840> run<00:24:01.140> as<00:24:01.740> the<00:24:01.980> question<00:24:02.159> in<00:24:02.280> the 00:24:02.390 --> 00:24:02.400 align:start position:0% you can't run as the question in the 00:24:02.400 --> 00:24:05.090 align:start position:0% you can't run as the question in the back<00:24:02.460> said<00:24:02.640> thousands<00:24:03.539> of<00:24:03.600> scenarios<00:24:04.080> run<00:24:04.980> it 00:24:05.090 --> 00:24:05.100 align:start position:0% back said thousands of scenarios run it 00:24:05.100 --> 00:24:07.610 align:start position:0% back said thousands of scenarios run it through<00:24:05.280> a<00:24:05.520> year<00:24:05.700> do<00:24:06.419> all<00:24:06.600> these<00:24:06.780> things<00:24:06.960> so 00:24:07.610 --> 00:24:07.620 align:start position:0% through a year do all these things so 00:24:07.620 --> 00:24:10.130 align:start position:0% through a year do all these things so what<00:24:07.799> we<00:24:07.980> do<00:24:08.100> we<00:24:08.220> strip<00:24:08.400> that<00:24:08.640> out<00:24:08.820> we<00:24:09.539> run<00:24:09.720> what 00:24:10.130 --> 00:24:10.140 align:start position:0% what we do we strip that out we run what 00:24:10.140 --> 00:24:12.470 align:start position:0% what we do we strip that out we run what we<00:24:10.260> call<00:24:10.380> a<00:24:10.559> null<00:24:10.740> chain<00:24:10.980> entirely<00:24:11.760> on<00:24:11.940> on<00:24:12.240> one 00:24:12.470 --> 00:24:12.480 align:start position:0% we call a null chain entirely on on one 00:24:12.480 --> 00:24:17.390 align:start position:0% we call a null chain entirely on on one PC<00:24:12.980> and<00:24:13.980> this<00:24:14.520> just<00:24:14.760> broadly<00:24:15.440> accepts<00:24:16.440> any 00:24:17.390 --> 00:24:17.400 align:start position:0% PC and this just broadly accepts any 00:24:17.400 --> 00:24:20.210 align:start position:0% PC and this just broadly accepts any transactions<00:24:17.940> it's<00:24:18.120> sent<00:24:18.360> it<00:24:19.260> will<00:24:19.500> it<00:24:19.980> still 00:24:20.210 --> 00:24:20.220 align:start position:0% transactions it's sent it will it still 00:24:20.220 --> 00:24:21.470 align:start position:0% transactions it's sent it will it still checks<00:24:20.520> they're<00:24:20.700> valid<00:24:20.940> it<00:24:21.059> still<00:24:21.240> runs 00:24:21.470 --> 00:24:21.480 align:start position:0% checks they're valid it still runs 00:24:21.480 --> 00:24:26.210 align:start position:0% checks they're valid it still runs through<00:24:21.659> the<00:24:21.900> whole<00:24:22.080> Vega<00:24:22.860> core<00:24:23.100> logic<00:24:23.760> but 00:24:26.210 --> 00:24:26.220 align:start position:0% through the whole Vega core logic but 00:24:26.220 --> 00:24:28.310 align:start position:0% through the whole Vega core logic but um just<00:24:26.520> adds<00:24:26.940> into<00:24:27.059> a<00:24:27.240> block<00:24:27.360> allows<00:24:28.080> you<00:24:28.140> to 00:24:28.310 --> 00:24:28.320 align:start position:0% um just adds into a block allows you to 00:24:28.320 --> 00:24:31.610 align:start position:0% um just adds into a block allows you to control<00:24:28.640> time<00:24:29.640> forwarding<00:24:30.179> so<00:24:30.360> you<00:24:30.659> can<00:24:30.840> it'll 00:24:31.610 --> 00:24:31.620 align:start position:0% control time forwarding so you can it'll 00:24:31.620 --> 00:24:33.890 align:start position:0% control time forwarding so you can it'll just<00:24:31.919> sit<00:24:32.220> and<00:24:32.640> do<00:24:32.760> nothing<00:24:32.940> until<00:24:33.360> you<00:24:33.659> tell 00:24:33.890 --> 00:24:33.900 align:start position:0% just sit and do nothing until you tell 00:24:33.900 --> 00:24:36.169 align:start position:0% just sit and do nothing until you tell it<00:24:34.140> to<00:24:34.260> run<00:24:34.679> forwards<00:24:35.159> or<00:24:35.580> fill<00:24:35.760> up<00:24:35.880> a<00:24:36.059> block 00:24:36.169 --> 00:24:36.179 align:start position:0% it to run forwards or fill up a block 00:24:36.179 --> 00:24:39.049 align:start position:0% it to run forwards or fill up a block and<00:24:36.900> so<00:24:37.080> you<00:24:37.380> can<00:24:37.559> inspect<00:24:38.280> at<00:24:38.520> any<00:24:38.700> point<00:24:38.880> in 00:24:39.049 --> 00:24:39.059 align:start position:0% and so you can inspect at any point in 00:24:39.059 --> 00:24:39.890 align:start position:0% and so you can inspect at any point in time 00:24:39.890 --> 00:24:39.900 align:start position:0% time 00:24:39.900 --> 00:24:41.690 align:start position:0% time for<00:24:40.200> however<00:24:40.440> long<00:24:40.559> you<00:24:40.740> want 00:24:41.690 --> 00:24:41.700 align:start position:0% for however long you want 00:24:41.700 --> 00:24:43.250 align:start position:0% for however long you want what's<00:24:42.059> going<00:24:42.299> on 00:24:43.250 --> 00:24:43.260 align:start position:0% what's going on 00:24:43.260 --> 00:24:45.529 align:start position:0% what's going on then<00:24:43.919> on<00:24:44.460> top<00:24:44.580> of<00:24:44.700> this<00:24:44.760> once<00:24:45.120> we've<00:24:45.240> got<00:24:45.360> that 00:24:45.529 --> 00:24:45.539 align:start position:0% then on top of this once we've got that 00:24:45.539 --> 00:24:46.549 align:start position:0% then on top of this once we've got that running 00:24:46.549 --> 00:24:46.559 align:start position:0% running 00:24:46.559 --> 00:24:49.789 align:start position:0% running we<00:24:46.980> have<00:24:47.100> in<00:24:47.340> Python<00:24:47.900> an<00:24:48.900> API<00:24:49.200> layer<00:24:49.559> which 00:24:49.789 --> 00:24:49.799 align:start position:0% we have in Python an API layer which 00:24:49.799 --> 00:24:51.610 align:start position:0% we have in Python an API layer which lets<00:24:50.220> you<00:24:50.280> express 00:24:51.610 --> 00:24:51.620 align:start position:0% lets you express 00:24:51.620 --> 00:24:54.110 align:start position:0% lets you express your<00:24:52.620> trading<00:24:53.100> actions<00:24:53.460> your<00:24:53.820> agents 00:24:54.110 --> 00:24:54.120 align:start position:0% your trading actions your agents 00:24:54.120 --> 00:24:56.450 align:start position:0% your trading actions your agents behaviors<00:24:54.600> in<00:24:55.260> much<00:24:55.380> more<00:24:55.620> Market<00:24:55.860> Primitives 00:24:56.450 --> 00:24:56.460 align:start position:0% behaviors in much more Market Primitives 00:24:56.460 --> 00:24:58.730 align:start position:0% behaviors in much more Market Primitives without<00:24:57.059> having<00:24:57.419> to<00:24:57.600> worry<00:24:57.840> about<00:24:58.020> the<00:24:58.620> fact 00:24:58.730 --> 00:24:58.740 align:start position:0% without having to worry about the fact 00:24:58.740 --> 00:24:59.690 align:start position:0% without having to worry about the fact that<00:24:58.860> you're<00:24:58.980> running<00:24:59.100> on<00:24:59.280> a<00:24:59.400> blockchain 00:24:59.690 --> 00:24:59.700 align:start position:0% that you're running on a blockchain 00:24:59.700 --> 00:25:02.450 align:start position:0% that you're running on a blockchain occasionally<00:25:00.600> it<00:25:00.900> still<00:25:01.260> Creeps<00:25:01.620> in<00:25:01.740> because 00:25:02.450 --> 00:25:02.460 align:start position:0% occasionally it still Creeps in because 00:25:02.460 --> 00:25:05.210 align:start position:0% occasionally it still Creeps in because that's<00:25:03.059> the<00:25:03.299> way<00:25:03.480> well<00:25:03.720> but<00:25:04.200> you<00:25:04.799> can<00:25:04.919> broadly 00:25:05.210 --> 00:25:05.220 align:start position:0% that's the way well but you can broadly 00:25:05.220 --> 00:25:07.669 align:start position:0% that's the way well but you can broadly talk<00:25:05.400> about<00:25:05.580> an<00:25:06.000> agent<00:25:06.240> trading<00:25:06.600> on<00:25:06.659> a<00:25:06.840> market 00:25:07.669 --> 00:25:07.679 align:start position:0% talk about an agent trading on a market 00:25:07.679 --> 00:25:09.529 align:start position:0% talk about an agent trading on a market without<00:25:08.039> having<00:25:08.340> to<00:25:08.520> worry<00:25:08.640> about 00:25:09.529 --> 00:25:09.539 align:start position:0% without having to worry about 00:25:09.539 --> 00:25:11.029 align:start position:0% without having to worry about what<00:25:09.840> Block<00:25:10.080> it's<00:25:10.260> in<00:25:10.440> whether<00:25:10.679> it's<00:25:10.919> been 00:25:11.029 --> 00:25:11.039 align:start position:0% what Block it's in whether it's been 00:25:11.039 --> 00:25:13.370 align:start position:0% what Block it's in whether it's been confirmed<00:25:11.460> and<00:25:11.640> this<00:25:11.820> kind<00:25:11.940> of<00:25:12.059> thing 00:25:13.370 --> 00:25:13.380 align:start position:0% confirmed and this kind of thing 00:25:13.380 --> 00:25:16.250 align:start position:0% confirmed and this kind of thing once<00:25:13.799> we've<00:25:13.919> got<00:25:14.100> that<00:25:14.280> we<00:25:14.820> then<00:25:15.000> build<00:25:15.299> out 00:25:16.250 --> 00:25:16.260 align:start position:0% once we've got that we then build out 00:25:16.260 --> 00:25:18.350 align:start position:0% once we've got that we then build out our<00:25:16.559> scenarios<00:25:17.039> and<00:25:17.220> our<00:25:17.340> tests<00:25:17.640> so<00:25:18.240> I'll 00:25:18.350 --> 00:25:18.360 align:start position:0% our scenarios and our tests so I'll 00:25:18.360 --> 00:25:19.850 align:start position:0% our scenarios and our tests so I'll cover 00:25:19.850 --> 00:25:19.860 align:start position:0% cover 00:25:19.860 --> 00:25:21.830 align:start position:0% cover possibly<00:25:20.400> next<00:25:20.580> slide<00:25:20.880> exactly<00:25:21.539> what<00:25:21.659> a 00:25:21.830 --> 00:25:21.840 align:start position:0% possibly next slide exactly what a 00:25:21.840 --> 00:25:25.970 align:start position:0% possibly next slide exactly what a scenario<00:25:22.140> is<00:25:22.320> but<00:25:23.299> we<00:25:24.299> can<00:25:24.539> with<00:25:25.500> a<00:25:25.679> range<00:25:25.860> of 00:25:25.970 --> 00:25:25.980 align:start position:0% scenario is but we can with a range of 00:25:25.980 --> 00:25:29.269 align:start position:0% scenario is but we can with a range of composable<00:25:26.400> Agents<00:25:27.120> composable<00:25:27.659> setups 00:25:29.269 --> 00:25:29.279 align:start position:0% composable Agents composable setups 00:25:29.279 --> 00:25:30.830 align:start position:0% composable Agents composable setups build<00:25:29.820> out 00:25:30.830 --> 00:25:30.840 align:start position:0% build out 00:25:30.840 --> 00:25:33.350 align:start position:0% build out scenarios<00:25:31.559> to<00:25:31.799> investigate<00:25:32.220> and<00:25:32.340> test 00:25:33.350 --> 00:25:33.360 align:start position:0% scenarios to investigate and test 00:25:33.360 --> 00:25:36.289 align:start position:0% scenarios to investigate and test either<00:25:34.140> certain<00:25:34.740> parameters<00:25:35.340> test<00:25:35.880> that<00:25:36.120> the 00:25:36.289 --> 00:25:36.299 align:start position:0% either certain parameters test that the 00:25:36.299 --> 00:25:39.049 align:start position:0% either certain parameters test that the market<00:25:36.419> doesn't<00:25:36.779> explode<00:25:37.500> test<00:25:37.980> this<00:25:38.220> the 00:25:39.049 --> 00:25:39.059 align:start position:0% market doesn't explode test this the 00:25:39.059 --> 00:25:41.090 align:start position:0% market doesn't explode test this the core<00:25:39.299> itself<00:25:39.600> doesn't<00:25:39.779> explode<00:25:40.140> or<00:25:40.919> if<00:25:40.980> you 00:25:41.090 --> 00:25:41.100 align:start position:0% core itself doesn't explode or if you 00:25:41.100 --> 00:25:42.350 align:start position:0% core itself doesn't explode or if you just<00:25:41.220> wanted<00:25:41.340> to<00:25:41.520> build<00:25:41.640> an<00:25:41.760> agent<00:25:42.000> you<00:25:42.299> can 00:25:42.350 --> 00:25:42.360 align:start position:0% just wanted to build an agent you can 00:25:42.360 --> 00:25:44.330 align:start position:0% just wanted to build an agent you can try<00:25:42.600> and<00:25:42.779> have<00:25:43.080> a<00:25:43.200> realistic<00:25:43.620> market<00:25:43.799> and 00:25:44.330 --> 00:25:44.340 align:start position:0% try and have a realistic market and 00:25:44.340 --> 00:25:48.950 align:start position:0% try and have a realistic market and throw<00:25:44.760> yours<00:25:45.120> in<00:25:45.240> there 00:25:48.950 --> 00:25:48.960 align:start position:0% 00:25:48.960 --> 00:25:52.610 align:start position:0% how<00:25:49.320> this<00:25:49.500> all<00:25:49.620> works<00:25:50.039> is<00:25:50.460> your<00:25:51.360> python<00:25:51.840> layer 00:25:52.610 --> 00:25:52.620 align:start position:0% how this all works is your python layer 00:25:52.620 --> 00:25:55.750 align:start position:0% how this all works is your python layer manages<00:25:53.340> we've<00:25:54.120> got<00:25:54.240> two<00:25:54.419> different<00:25:54.600> kinds<00:25:55.140> of 00:25:55.750 --> 00:25:55.760 align:start position:0% manages we've got two different kinds of 00:25:55.760 --> 00:25:58.010 align:start position:0% manages we've got two different kinds of interfaces<00:25:56.760> at<00:25:56.880> the<00:25:57.000> moment<00:25:57.120> a<00:25:57.539> Vega<00:25:57.900> service 00:25:58.010 --> 00:25:58.020 align:start position:0% interfaces at the moment a Vega service 00:25:58.020 --> 00:26:00.409 align:start position:0% interfaces at the moment a Vega service null<00:25:58.320> which<00:25:58.620> spins<00:25:58.919> up<00:25:59.100> this<00:25:59.460> as<00:25:59.940> I<00:26:00.120> mentioned 00:26:00.409 --> 00:26:00.419 align:start position:0% null which spins up this as I mentioned 00:26:00.419 --> 00:26:04.430 align:start position:0% null which spins up this as I mentioned a<00:26:00.840> service<00:26:01.440> entirely<00:26:01.980> on<00:26:02.159> your<00:26:02.340> machine<00:26:03.440> or 00:26:04.430 --> 00:26:04.440 align:start position:0% a service entirely on your machine or 00:26:04.440 --> 00:26:06.110 align:start position:0% a service entirely on your machine or what<00:26:04.919> we've<00:26:05.159> recently<00:26:05.520> created<00:26:05.760> which<00:26:06.000> is 00:26:06.110 --> 00:26:06.120 align:start position:0% what we've recently created which is 00:26:06.120 --> 00:26:08.570 align:start position:0% what we've recently created which is Vegas<00:26:06.299> Network<00:26:07.080> and<00:26:07.919> that<00:26:07.980> allows<00:26:08.340> you<00:26:08.400> to 00:26:08.570 --> 00:26:08.580 align:start position:0% Vegas Network and that allows you to 00:26:08.580 --> 00:26:11.710 align:start position:0% Vegas Network and that allows you to connect<00:26:08.880> to<00:26:09.179> a<00:26:10.140> running<00:26:10.340> external<00:26:11.340> network 00:26:11.710 --> 00:26:11.720 align:start position:0% connect to a running external network 00:26:11.720 --> 00:26:14.750 align:start position:0% connect to a running external network and<00:26:12.720> run<00:26:13.559> the<00:26:13.980> same<00:26:14.100> agents<00:26:14.400> that<00:26:14.520> you've<00:26:14.640> just 00:26:14.750 --> 00:26:14.760 align:start position:0% and run the same agents that you've just 00:26:14.760 --> 00:26:15.950 align:start position:0% and run the same agents that you've just been<00:26:14.820> running<00:26:15.000> locally 00:26:15.950 --> 00:26:15.960 align:start position:0% been running locally 00:26:15.960 --> 00:26:18.830 align:start position:0% been running locally but<00:26:16.500> on<00:26:16.799> the<00:26:17.039> real<00:26:17.460> Network<00:26:17.700> that's<00:26:18.179> going<00:26:18.659> on 00:26:18.830 --> 00:26:18.840 align:start position:0% but on the real Network that's going on 00:26:18.840 --> 00:26:21.529 align:start position:0% but on the real Network that's going on so<00:26:19.320> that<00:26:19.919> can<00:26:20.039> be<00:26:20.100> useful<00:26:20.340> in<00:26:20.460> some<00:26:20.580> cases<00:26:20.880> too 00:26:21.529 --> 00:26:21.539 align:start position:0% so that can be useful in some cases too 00:26:21.539 --> 00:26:23.450 align:start position:0% so that can be useful in some cases too it<00:26:21.900> allows<00:26:22.200> us<00:26:22.380> for<00:26:22.679> example<00:26:22.860> on<00:26:23.039> our<00:26:23.159> test<00:26:23.340> net 00:26:23.450 --> 00:26:23.460 align:start position:0% it allows us for example on our test net 00:26:23.460 --> 00:26:26.029 align:start position:0% it allows us for example on our test net we<00:26:23.820> can<00:26:24.059> run<00:26:24.840> agents<00:26:25.320> and<00:26:25.380> simulations<00:26:25.740> that 00:26:26.029 --> 00:26:26.039 align:start position:0% we can run agents and simulations that 00:26:26.039 --> 00:26:27.950 align:start position:0% we can run agents and simulations that other<00:26:26.279> real<00:26:26.580> people<00:26:26.880> can<00:26:27.179> interact<00:26:27.539> with<00:26:27.659> and 00:26:27.950 --> 00:26:27.960 align:start position:0% other real people can interact with and 00:26:27.960 --> 00:26:30.649 align:start position:0% other real people can interact with and see<00:26:28.140> how<00:26:28.260> that's<00:26:28.380> working 00:26:30.649 --> 00:26:30.659 align:start position:0% see how that's working 00:26:30.659 --> 00:26:35.029 align:start position:0% see how that's working um<00:26:30.720> we'll<00:26:31.440> demo<00:26:31.919> all<00:26:32.640> that<00:26:32.940> in<00:26:33.240> a<00:26:33.299> bit 00:26:35.029 --> 00:26:35.039 align:start position:0% um we'll demo all that in a bit 00:26:35.039 --> 00:26:39.830 align:start position:0% um we'll demo all that in a bit um<00:26:35.159> so<00:26:35.580> yeah<00:26:36.240> back<00:26:36.779> to<00:26:36.960> setting<00:26:37.500> things<00:26:37.679> up 00:26:39.830 --> 00:26:39.840 align:start position:0% um so yeah back to setting things up 00:26:39.840 --> 00:26:41.390 align:start position:0% um so yeah back to setting things up and<00:26:40.440> viewing 00:26:41.390 --> 00:26:41.400 align:start position:0% and viewing 00:26:41.400 --> 00:26:43.070 align:start position:0% and viewing I'll<00:26:42.000> go<00:26:42.299> through<00:26:42.419> the<00:26:42.539> viewing<00:26:42.779> in<00:26:42.840> a<00:26:42.960> second 00:26:43.070 --> 00:26:43.080 align:start position:0% I'll go through the viewing in a second 00:26:43.080 --> 00:26:45.409 align:start position:0% I'll go through the viewing in a second but<00:26:43.380> yeah 00:26:45.409 --> 00:26:45.419 align:start position:0% but yeah 00:26:45.419 --> 00:26:47.210 align:start position:0% but yeah yeah<00:26:45.900> I<00:26:46.020> was<00:26:46.140> gonna<00:26:46.320> gonna<00:26:46.679> break<00:26:46.860> here<00:26:47.039> anyway 00:26:47.210 --> 00:26:47.220 align:start position:0% yeah I was gonna gonna break here anyway 00:26:47.220 --> 00:26:50.210 align:start position:0% yeah I was gonna gonna break here anyway so<00:26:47.580> yeah<00:26:48.480> so 00:26:50.210 --> 00:26:50.220 align:start position:0% so yeah so 00:26:50.220 --> 00:26:52.310 align:start position:0% so yeah so um<00:26:50.279> we're<00:26:50.580> back<00:26:50.700> here<00:26:50.880> I<00:26:51.419> don't<00:26:51.900> know<00:26:52.020> how<00:26:52.200> many 00:26:52.310 --> 00:26:52.320 align:start position:0% um we're back here I don't know how many 00:26:52.320 --> 00:26:54.049 align:start position:0% um we're back here I don't know how many people<00:26:52.440> have<00:26:52.620> managed<00:26:52.919> to<00:26:53.039> get<00:26:53.580> to<00:26:53.700> the<00:26:53.820> end<00:26:53.940> of 00:26:54.049 --> 00:26:54.059 align:start position:0% people have managed to get to the end of 00:26:54.059 --> 00:26:56.090 align:start position:0% people have managed to get to the end of this<00:26:54.179> but<00:26:54.539> I<00:26:54.960> think<00:26:55.020> we'll<00:26:55.200> probably<00:26:55.440> take<00:26:55.740> a 00:26:56.090 --> 00:26:56.100 align:start position:0% this but I think we'll probably take a 00:26:56.100 --> 00:26:58.010 align:start position:0% this but I think we'll probably take a sort<00:26:56.340> of<00:26:56.400> 10<00:26:56.520> minute<00:26:56.700> break<00:26:56.940> to<00:26:57.240> catch<00:26:58.020> up 00:26:58.010 --> 00:26:58.020 align:start position:0% sort of 10 minute break to catch up 00:26:58.020 --> 00:26:59.390 align:start position:0% sort of 10 minute break to catch up anyone<00:26:58.380> who<00:26:58.440> has<00:26:58.620> them<00:26:58.740> we<00:26:58.919> can<00:26:59.039> wander<00:26:59.279> around 00:26:59.390 --> 00:26:59.400 align:start position:0% anyone who has them we can wander around 00:26:59.400 --> 00:27:02.870 align:start position:0% anyone who has them we can wander around and<00:26:59.820> see<00:27:00.779> whether<00:27:01.679> everyone<00:27:01.860> will<00:27:02.220> manage<00:27:02.520> and 00:27:02.870 --> 00:27:02.880 align:start position:0% and see whether everyone will manage and 00:27:02.880 --> 00:27:05.330 align:start position:0% and see whether everyone will manage and then<00:27:03.059> 10<00:27:03.900> 15<00:27:04.200> minutes<00:27:04.440> we<00:27:04.740> can<00:27:04.860> come<00:27:04.980> back<00:27:05.100> and 00:27:05.330 --> 00:27:05.340 align:start position:0% then 10 15 minutes we can come back and 00:27:05.340 --> 00:27:07.070 align:start position:0% then 10 15 minutes we can come back and continue<00:27:05.520> with<00:27:06.059> doing<00:27:06.659> something<00:27:06.900> more 00:27:07.070 --> 00:27:07.080 align:start position:0% continue with doing something more 00:27:07.080 --> 00:27:08.750 align:start position:0% continue with doing something more interesting<00:27:07.380> with<00:27:07.500> it<00:27:07.679> if<00:27:08.279> you<00:27:08.400> think<00:27:08.520> you've 00:27:08.750 --> 00:27:08.760 align:start position:0% interesting with it if you think you've 00:27:08.760 --> 00:27:12.070 align:start position:0% interesting with it if you think you've got<00:27:08.880> it<00:27:09.000> set<00:27:09.179> up<00:27:09.299> try<00:27:09.840> and<00:27:10.020> run<00:27:10.200> these 00:27:12.070 --> 00:27:12.080 align:start position:0% got it set up try and run these 00:27:12.080 --> 00:27:15.049 align:start position:0% got it set up try and run these uh<00:27:13.080> scripts<00:27:13.799> at<00:27:13.860> the<00:27:14.039> bottom<00:27:14.159> we<00:27:14.640> can<00:27:14.820> also 00:27:15.049 --> 00:27:15.059 align:start position:0% uh scripts at the bottom we can also 00:27:15.059 --> 00:27:16.250 align:start position:0% uh scripts at the bottom we can also tell<00:27:15.299> you<00:27:15.480> something<00:27:15.600> more<00:27:15.779> interesting<00:27:16.080> to 00:27:16.250 --> 00:27:16.260 align:start position:0% tell you something more interesting to 00:27:16.260 --> 00:27:18.230 align:start position:0% tell you something more interesting to run<00:27:16.380> if<00:27:16.620> if<00:27:16.860> you're<00:27:17.100> stuck 00:27:18.230 --> 00:27:18.240 align:start position:0% run if if you're stuck 00:27:18.240 --> 00:27:39.950 align:start position:0% run if if you're stuck um<00:27:18.360> I<00:27:18.539> think<00:27:18.720> I<00:27:18.840> had<00:27:18.960> a<00:27:19.080> question<00:27:19.200> yes 00:27:39.950 --> 00:27:39.960 align:start position:0% 00:27:39.960 --> 00:27:43.310 align:start position:0% so<00:27:40.440> I<00:27:40.620> can<00:27:40.740> then<00:27:40.919> more<00:27:41.400> uh<00:27:42.120> in<00:27:42.600> a<00:27:42.779> more<00:27:42.840> real<00:27:43.020> way 00:27:43.310 --> 00:27:43.320 align:start position:0% so I can then more uh in a more real way 00:27:43.320 --> 00:27:47.810 align:start position:0% so I can then more uh in a more real way basically<00:27:44.220> test<00:27:44.640> my<00:27:45.120> uh<00:27:46.020> my<00:27:46.320> ideas<00:27:46.820> it's 00:27:47.810 --> 00:27:47.820 align:start position:0% basically test my uh my ideas it's 00:27:47.820 --> 00:27:49.610 align:start position:0% basically test my uh my ideas it's actually<00:27:48.000> it's<00:27:48.419> something<00:27:48.659> we're<00:27:49.140> pretty 00:27:49.610 --> 00:27:49.620 align:start position:0% actually it's something we're pretty 00:27:49.620 --> 00:27:51.049 align:start position:0% actually it's something we're pretty much<00:27:49.740> currently<00:27:50.039> working<00:27:50.220> on<00:27:50.460> yeah<00:27:50.640> is<00:27:50.880> being 00:27:51.049 --> 00:27:51.059 align:start position:0% much currently working on yeah is being 00:27:51.059 --> 00:27:53.690 align:start position:0% much currently working on yeah is being able<00:27:51.299> to<00:27:51.419> better<00:27:51.960> snapshot 00:27:53.690 --> 00:27:53.700 align:start position:0% able to better snapshot 00:27:53.700 --> 00:27:55.669 align:start position:0% able to better snapshot an<00:27:54.179> existing<00:27:54.539> running<00:27:54.720> chain<00:27:55.020> and<00:27:55.260> be<00:27:55.380> able<00:27:55.500> to 00:27:55.669 --> 00:27:55.679 align:start position:0% an existing running chain and be able to 00:27:55.679 --> 00:27:58.549 align:start position:0% an existing running chain and be able to totally<00:27:56.100> restore<00:27:56.880> from<00:27:57.059> that<00:27:57.240> weird<00:27:58.020> there<00:27:58.320> is 00:27:58.549 --> 00:27:58.559 align:start position:0% totally restore from that weird there is 00:27:58.559 --> 00:28:01.010 align:start position:0% totally restore from that weird there is there's<00:27:59.460> the<00:27:59.700> capability<00:27:59.940> currently<00:28:00.419> to<00:28:00.659> you 00:28:01.010 --> 00:28:01.020 align:start position:0% there's the capability currently to you 00:28:01.020 --> 00:28:03.830 align:start position:0% there's the capability currently to you can<00:28:01.140> run<00:28:01.260> your<00:28:01.500> simulation<00:28:01.980> and<00:28:02.600> save<00:28:03.600> that 00:28:03.830 --> 00:28:03.840 align:start position:0% can run your simulation and save that 00:28:03.840 --> 00:28:05.570 align:start position:0% can run your simulation and save that and<00:28:04.020> rerun<00:28:04.440> the<00:28:04.559> same<00:28:04.679> thing<00:28:04.860> so<00:28:05.039> you<00:28:05.279> can<00:28:05.400> have 00:28:05.570 --> 00:28:05.580 align:start position:0% and rerun the same thing so you can have 00:28:05.580 --> 00:28:06.409 align:start position:0% and rerun the same thing so you can have a 00:28:06.409 --> 00:28:06.419 align:start position:0% a 00:28:06.419 --> 00:28:08.390 align:start position:0% a an<00:28:06.779> example<00:28:07.200> that<00:28:07.559> you<00:28:07.679> run<00:28:07.860> and<00:28:08.159> then<00:28:08.279> run 00:28:08.390 --> 00:28:08.400 align:start position:0% an example that you run and then run 00:28:08.400 --> 00:28:10.130 align:start position:0% an example that you run and then run your<00:28:08.580> things<00:28:08.760> after<00:28:08.940> we<00:28:09.659> don't<00:28:09.840> currently 00:28:10.130 --> 00:28:10.140 align:start position:0% your things after we don't currently 00:28:10.140 --> 00:28:11.930 align:start position:0% your things after we don't currently have<00:28:10.260> a<00:28:10.320> way<00:28:10.440> to<00:28:10.620> pull<00:28:10.799> from<00:28:11.460> an<00:28:11.640> existing 00:28:11.930 --> 00:28:11.940 align:start position:0% have a way to pull from an existing 00:28:11.940 --> 00:28:12.710 align:start position:0% have a way to pull from an existing Network 00:28:12.710 --> 00:28:12.720 align:start position:0% Network 00:28:12.720 --> 00:28:23.890 align:start position:0% Network okay<00:28:13.200> thank<00:28:13.500> you<00:28:13.620> very<00:28:13.740> much 00:28:23.890 --> 00:28:23.900 align:start position:0% 00:28:23.900 --> 00:28:26.450 align:start position:0% that<00:28:24.900> people<00:28:25.200> should<00:28:25.620> be<00:28:25.740> using<00:28:26.039> in<00:28:26.279> their 00:28:26.450 --> 00:28:26.460 align:start position:0% that people should be using in their 00:28:26.460 --> 00:28:28.610 align:start position:0% that people should be using in their protocol<00:28:26.760> and<00:28:27.539> I<00:28:27.659> tend<00:28:27.900> to<00:28:27.960> tell<00:28:28.140> them<00:28:28.260> that 00:28:28.610 --> 00:28:28.620 align:start position:0% protocol and I tend to tell them that 00:28:28.620 --> 00:28:30.950 align:start position:0% protocol and I tend to tell them that they<00:28:29.100> can<00:28:29.279> more<00:28:29.940> easily<00:28:30.240> solve<00:28:30.720> for 00:28:30.950 --> 00:28:30.960 align:start position:0% they can more easily solve for 00:28:30.960 --> 00:28:32.870 align:start position:0% they can more easily solve for tokenomics<00:28:31.620> problems<00:28:32.039> by<00:28:32.340> including<00:28:32.700> a 00:28:32.870 --> 00:28:32.880 align:start position:0% tokenomics problems by including a 00:28:32.880 --> 00:28:35.390 align:start position:0% tokenomics problems by including a market<00:28:33.000> mechanism<00:28:33.600> to<00:28:34.020> optimize<00:28:34.440> and<00:28:34.679> let<00:28:34.919> you 00:28:35.390 --> 00:28:35.400 align:start position:0% market mechanism to optimize and let you 00:28:35.400 --> 00:28:36.950 align:start position:0% market mechanism to optimize and let you know<00:28:35.580> the<00:28:35.700> market<00:28:35.880> do<00:28:36.240> those<00:28:36.419> kinds<00:28:36.659> of<00:28:36.720> things 00:28:36.950 --> 00:28:36.960 align:start position:0% know the market do those kinds of things 00:28:36.960 --> 00:28:40.130 align:start position:0% know the market do those kinds of things like<00:28:37.919> example<00:28:38.340> uniswap<00:28:39.059> V3<00:28:39.419> solves<00:28:39.900> the<00:28:40.020> hard 00:28:40.130 --> 00:28:40.140 align:start position:0% like example uniswap V3 solves the hard 00:28:40.140 --> 00:28:42.470 align:start position:0% like example uniswap V3 solves the hard problem<00:28:40.380> of<00:28:40.860> how<00:28:41.159> to<00:28:41.400> set<00:28:41.760> the<00:28:41.940> curve<00:28:42.240> by 00:28:42.470 --> 00:28:42.480 align:start position:0% problem of how to set the curve by 00:28:42.480 --> 00:28:45.230 align:start position:0% problem of how to set the curve by allowing<00:28:42.840> concentrated<00:28:43.380> liquidity<00:28:44.000> so<00:28:45.000> my 00:28:45.230 --> 00:28:45.240 align:start position:0% allowing concentrated liquidity so my 00:28:45.240 --> 00:28:47.210 align:start position:0% allowing concentrated liquidity so my question<00:28:45.419> is<00:28:45.740> do<00:28:46.740> you<00:28:46.919> guys<00:28:46.980> have<00:28:47.100> an 00:28:47.210 --> 00:28:47.220 align:start position:0% question is do you guys have an 00:28:47.220 --> 00:28:49.789 align:start position:0% question is do you guys have an intuition<00:28:47.640> for<00:28:48.059> which<00:28:48.539> kind<00:28:48.840> of<00:28:49.080> simulation 00:28:49.789 --> 00:28:49.799 align:start position:0% intuition for which kind of simulation 00:28:49.799 --> 00:28:52.190 align:start position:0% intuition for which kind of simulation like<00:28:50.100> which<00:28:50.460> kind<00:28:50.700> of<00:28:50.820> systems<00:28:51.659> require<00:28:51.960> a 00:28:52.190 --> 00:28:52.200 align:start position:0% like which kind of systems require a 00:28:52.200 --> 00:28:55.070 align:start position:0% like which kind of systems require a simulation<00:28:52.620> and<00:28:52.799> which<00:28:52.980> kind<00:28:53.159> don't 00:28:55.070 --> 00:28:55.080 align:start position:0% simulation and which kind don't 00:28:55.080 --> 00:28:58.490 align:start position:0% simulation and which kind don't oh<00:28:55.740> good<00:28:56.100> question<00:28:56.360> I<00:28:57.360> I<00:28:57.720> guess<00:28:57.960> I'd<00:28:58.140> go<00:28:58.380> back 00:28:58.490 --> 00:28:58.500 align:start position:0% oh good question I I guess I'd go back 00:28:58.500 --> 00:29:00.049 align:start position:0% oh good question I I guess I'd go back to<00:28:58.679> as<00:28:59.039> David<00:28:59.220> was<00:28:59.400> saying<00:28:59.640> earlier<00:28:59.820> it 00:29:00.049 --> 00:29:00.059 align:start position:0% to as David was saying earlier it 00:29:00.059 --> 00:29:02.390 align:start position:0% to as David was saying earlier it depends<00:29:00.419> on<00:29:00.480> how<00:29:00.779> well<00:29:00.900> you<00:29:01.200> can<00:29:01.380> if<00:29:02.159> you<00:29:02.340> can 00:29:02.390 --> 00:29:02.400 align:start position:0% depends on how well you can if you can 00:29:02.400 --> 00:29:04.010 align:start position:0% depends on how well you can if you can solve<00:29:02.700> it<00:29:02.820> mathematically<00:29:03.539> that's<00:29:03.840> probably 00:29:04.010 --> 00:29:04.020 align:start position:0% solve it mathematically that's probably 00:29:04.020 --> 00:29:06.049 align:start position:0% solve it mathematically that's probably always<00:29:04.200> going<00:29:04.440> to<00:29:04.559> be<00:29:04.620> optimal<00:29:05.520> but<00:29:05.700> when<00:29:05.880> it 00:29:06.049 --> 00:29:06.059 align:start position:0% always going to be optimal but when it 00:29:06.059 --> 00:29:09.230 align:start position:0% always going to be optimal but when it reaches<00:29:06.480> a<00:29:06.600> certain<00:29:06.779> point<00:29:06.960> of<00:29:07.140> complexity 00:29:09.230 --> 00:29:09.240 align:start position:0% reaches a certain point of complexity 00:29:09.240 --> 00:29:11.510 align:start position:0% reaches a certain point of complexity um<00:29:09.299> yeah<00:29:09.840> I<00:29:10.080> don't<00:29:10.260> know<00:29:10.500> how<00:29:11.039> you<00:29:11.159> would<00:29:11.279> do<00:29:11.400> it 00:29:11.510 --> 00:29:11.520 align:start position:0% um yeah I don't know how you would do it 00:29:11.520 --> 00:29:13.370 align:start position:0% um yeah I don't know how you would do it without<00:29:11.640> either<00:29:12.059> an<00:29:12.480> agent-based<00:29:13.020> simulation 00:29:13.370 --> 00:29:13.380 align:start position:0% without either an agent-based simulation 00:29:13.380 --> 00:29:14.630 align:start position:0% without either an agent-based simulation or 00:29:14.630 --> 00:29:14.640 align:start position:0% or 00:29:14.640 --> 00:29:16.130 align:start position:0% or casting<00:29:15.179> modeling<00:29:15.539> or<00:29:15.659> that<00:29:15.779> kind<00:29:15.960> of<00:29:16.020> thing 00:29:16.130 --> 00:29:16.140 align:start position:0% casting modeling or that kind of thing 00:29:16.140 --> 00:29:18.110 align:start position:0% casting modeling or that kind of thing is<00:29:16.799> there<00:29:16.919> an<00:29:17.039> upper<00:29:17.340> limit<00:29:17.460> to<00:29:17.760> the<00:29:17.880> kind<00:29:18.000> of 00:29:18.110 --> 00:29:18.120 align:start position:0% is there an upper limit to the kind of 00:29:18.120 --> 00:29:19.610 align:start position:0% is there an upper limit to the kind of complexity<00:29:18.539> that<00:29:18.779> you<00:29:18.899> can<00:29:18.960> model<00:29:19.140> in<00:29:19.440> this 00:29:19.610 --> 00:29:19.620 align:start position:0% complexity that you can model in this 00:29:19.620 --> 00:29:21.350 align:start position:0% complexity that you can model in this because<00:29:19.860> I'd<00:29:20.039> imagine<00:29:20.220> like<00:29:20.520> in<00:29:20.940> this<00:29:21.059> example 00:29:21.350 --> 00:29:21.360 align:start position:0% because I'd imagine like in this example 00:29:21.360 --> 00:29:23.269 align:start position:0% because I'd imagine like in this example of<00:29:21.480> using<00:29:21.779> a<00:29:21.899> market<00:29:22.020> mechanism<00:29:22.559> that<00:29:22.919> adds<00:29:23.159> a 00:29:23.269 --> 00:29:23.279 align:start position:0% of using a market mechanism that adds a 00:29:23.279 --> 00:29:24.710 align:start position:0% of using a market mechanism that adds a lot<00:29:23.399> of<00:29:23.460> additional<00:29:23.820> complexity<00:29:24.299> is<00:29:24.539> that 00:29:24.710 --> 00:29:24.720 align:start position:0% lot of additional complexity is that 00:29:24.720 --> 00:29:27.169 align:start position:0% lot of additional complexity is that like<00:29:24.899> would<00:29:25.260> that<00:29:25.380> be<00:29:25.559> an<00:29:25.679> issue<00:29:26.039> in<00:29:26.640> the<00:29:26.820> Vega 00:29:27.169 --> 00:29:27.179 align:start position:0% like would that be an issue in the Vega 00:29:27.179 --> 00:29:29.450 align:start position:0% like would that be an issue in the Vega simulation 00:29:29.450 --> 00:29:29.460 align:start position:0% simulation 00:29:29.460 --> 00:29:32.029 align:start position:0% simulation in<00:29:30.179> terms<00:29:30.419> of<00:29:30.480> complexity<00:29:31.080> well<00:29:31.620> for<00:29:31.919> the 00:29:32.029 --> 00:29:32.039 align:start position:0% in terms of complexity well for the 00:29:32.039 --> 00:29:33.710 align:start position:0% in terms of complexity well for the simulation<00:29:32.340> yeah<00:29:32.760> I<00:29:32.940> mean<00:29:33.059> it<00:29:33.120> multiplies<00:29:33.539> the 00:29:33.710 --> 00:29:33.720 align:start position:0% simulation yeah I mean it multiplies the 00:29:33.720 --> 00:29:36.169 align:start position:0% simulation yeah I mean it multiplies the number<00:29:33.840> of<00:29:33.960> agents<00:29:34.380> in<00:29:34.559> the<00:29:34.740> in<00:29:34.919> the<00:29:35.159> system 00:29:36.169 --> 00:29:36.179 align:start position:0% number of agents in the in the system 00:29:36.179 --> 00:29:38.029 align:start position:0% number of agents in the in the system um<00:29:36.240> by<00:29:36.480> like<00:29:36.659> orders<00:29:37.080> of<00:29:37.260> magnitude<00:29:37.620> if<00:29:37.860> you 00:29:38.029 --> 00:29:38.039 align:start position:0% um by like orders of magnitude if you 00:29:38.039 --> 00:29:40.610 align:start position:0% um by like orders of magnitude if you have<00:29:38.279> to<00:29:38.460> use<00:29:38.700> a<00:29:38.880> market<00:29:39.059> to 00:29:40.610 --> 00:29:40.620 align:start position:0% have to use a market to 00:29:40.620 --> 00:29:43.010 align:start position:0% have to use a market to um Source<00:29:41.159> lots<00:29:41.520> more<00:29:41.640> participants 00:29:43.010 --> 00:29:43.020 align:start position:0% um Source lots more participants 00:29:43.020 --> 00:29:45.350 align:start position:0% um Source lots more participants ladies<00:29:43.500> I<00:29:43.740> guess<00:29:43.980> is<00:29:44.700> there<00:29:44.940> is<00:29:45.120> there<00:29:45.299> an 00:29:45.350 --> 00:29:45.360 align:start position:0% ladies I guess is there is there an 00:29:45.360 --> 00:29:46.669 align:start position:0% ladies I guess is there is there an upper<00:29:45.600> limit<00:29:45.720> to<00:29:45.960> the<00:29:46.080> kind<00:29:46.200> of<00:29:46.380> complex 00:29:46.669 --> 00:29:46.679 align:start position:0% upper limit to the kind of complex 00:29:46.679 --> 00:29:48.769 align:start position:0% upper limit to the kind of complex system<00:29:47.039> that<00:29:47.460> the<00:29:47.760> Vega<00:29:48.120> Market<00:29:48.240> simulation 00:29:48.769 --> 00:29:48.779 align:start position:0% system that the Vega Market simulation 00:29:48.779 --> 00:29:50.330 align:start position:0% system that the Vega Market simulation can<00:29:49.080> handle 00:29:50.330 --> 00:29:50.340 align:start position:0% can handle 00:29:50.340 --> 00:29:53.690 align:start position:0% can handle uh<00:29:51.240> well<00:29:51.559> practically<00:29:52.559> I<00:29:53.279> guess<00:29:53.399> there<00:29:53.580> is 00:29:53.690 --> 00:29:53.700 align:start position:0% uh well practically I guess there is 00:29:53.700 --> 00:29:56.210 align:start position:0% uh well practically I guess there is enough<00:29:53.820> limit<00:29:54.059> we<00:29:54.600> are<00:29:54.860> the<00:29:55.860> the<00:29:56.039> system 00:29:56.210 --> 00:29:56.220 align:start position:0% enough limit we are the the system 00:29:56.220 --> 00:29:57.950 align:start position:0% enough limit we are the the system itself<00:29:56.640> we're<00:29:57.179> hoping<00:29:57.419> we'll<00:29:57.600> be<00:29:57.720> able<00:29:57.840> to 00:29:57.950 --> 00:29:57.960 align:start position:0% itself we're hoping we'll be able to 00:29:57.960 --> 00:30:00.529 align:start position:0% itself we're hoping we'll be able to scale<00:29:58.140> to<00:29:58.380> many<00:29:58.620> thousands<00:29:59.340> of<00:29:59.399> people<00:29:59.520> so 00:30:00.529 --> 00:30:00.539 align:start position:0% scale to many thousands of people so 00:30:00.539 --> 00:30:03.049 align:start position:0% scale to many thousands of people so that<00:30:01.080> should<00:30:01.260> also<00:30:01.440> scale<00:30:01.740> to<00:30:02.039> to<00:30:02.700> the<00:30:02.940> number 00:30:03.049 --> 00:30:03.059 align:start position:0% that should also scale to to the number 00:30:03.059 --> 00:30:05.990 align:start position:0% that should also scale to to the number of<00:30:03.179> Agents<00:30:03.539> so<00:30:03.659> I<00:30:03.779> guess<00:30:03.899> it's<00:30:04.140> it's<00:30:04.919> a 00:30:05.990 --> 00:30:06.000 align:start position:0% of Agents so I guess it's it's a 00:30:06.000 --> 00:30:08.450 align:start position:0% of Agents so I guess it's it's a a<00:30:06.299> goal<00:30:06.720> of<00:30:06.779> both<00:30:07.020> the<00:30:07.500> Vega<00:30:07.919> protocol<00:30:08.100> itself 00:30:08.450 --> 00:30:08.460 align:start position:0% a goal of both the Vega protocol itself 00:30:08.460 --> 00:30:10.490 align:start position:0% a goal of both the Vega protocol itself and<00:30:08.880> the<00:30:09.059> market<00:30:09.299> Sim<00:30:09.600> thankfully<00:30:10.260> have 00:30:10.490 --> 00:30:10.500 align:start position:0% and the market Sim thankfully have 00:30:10.500 --> 00:30:13.190 align:start position:0% and the market Sim thankfully have similar<00:30:11.279> things<00:30:11.460> because<00:30:11.960> ultimately<00:30:12.960> what 00:30:13.190 --> 00:30:13.200 align:start position:0% similar things because ultimately what 00:30:13.200 --> 00:30:14.510 align:start position:0% similar things because ultimately what we<00:30:13.320> want<00:30:13.440> to<00:30:13.500> do<00:30:13.620> is<00:30:13.679> build<00:30:13.919> a<00:30:14.100> realistic 00:30:14.510 --> 00:30:14.520 align:start position:0% we want to do is build a realistic 00:30:14.520 --> 00:30:17.149 align:start position:0% we want to do is build a realistic market<00:30:14.640> so<00:30:15.179> if<00:30:15.779> you<00:30:16.020> can<00:30:16.140> build<00:30:16.320> as<00:30:16.799> long<00:30:16.980> as<00:30:17.039> we 00:30:17.149 --> 00:30:17.159 align:start position:0% market so if you can build as long as we 00:30:17.159 --> 00:30:18.710 align:start position:0% market so if you can build as long as we can<00:30:17.279> run<00:30:17.399> a<00:30:17.520> realistic<00:30:17.880> Market<00:30:18.059> on<00:30:18.299> Vega 00:30:18.710 --> 00:30:18.720 align:start position:0% can run a realistic Market on Vega 00:30:18.720 --> 00:30:20.090 align:start position:0% can run a realistic Market on Vega protocol<00:30:18.960> itself<00:30:19.320> which<00:30:19.679> should<00:30:19.860> be<00:30:19.980> able<00:30:20.039> to 00:30:20.090 --> 00:30:20.100 align:start position:0% protocol itself which should be able to 00:30:20.100 --> 00:30:30.230 align:start position:0% protocol itself which should be able to do<00:30:20.220> in<00:30:20.340> the<00:30:20.460> simulation<00:30:20.820> cool<00:30:21.659> thank<00:30:21.960> you<00:30:22.080> guys 00:30:30.230 --> 00:30:30.240 align:start position:0% 00:30:30.240 --> 00:30:32.330 align:start position:0% something 00:30:32.330 --> 00:30:32.340 align:start position:0% something 00:30:32.340 --> 00:30:34.870 align:start position:0% something they're<00:30:32.820> exactly 00:30:34.870 --> 00:30:34.880 align:start position:0% they're exactly 00:30:34.880 --> 00:30:37.789 align:start position:0% they're exactly going<00:30:35.880> back<00:30:36.120> to<00:30:36.240> the<00:30:36.840> going<00:30:37.320> back<00:30:37.559> to<00:30:37.679> the 00:30:37.789 --> 00:30:37.799 align:start position:0% going back to the going back to the 00:30:37.799 --> 00:30:39.169 align:start position:0% going back to the going back to the points<00:30:38.039> that<00:30:38.159> we<00:30:38.279> were<00:30:38.399> making<00:30:38.580> I<00:30:38.820> absolutely 00:30:39.169 --> 00:30:39.179 align:start position:0% points that we were making I absolutely 00:30:39.179 --> 00:30:41.750 align:start position:0% points that we were making I absolutely agree<00:30:39.539> that<00:30:39.779> if<00:30:40.140> you 00:30:41.750 --> 00:30:41.760 align:start position:0% agree that if you 00:30:41.760 --> 00:30:44.210 align:start position:0% agree that if you uh<00:30:42.419> if<00:30:42.600> you're<00:30:42.960> designing<00:30:43.440> tokenomics<00:30:44.039> or 00:30:44.210 --> 00:30:44.220 align:start position:0% uh if you're designing tokenomics or 00:30:44.220 --> 00:30:46.190 align:start position:0% uh if you're designing tokenomics or protocol<00:30:44.580> novel<00:30:45.120> then<00:30:45.360> either<00:30:45.539> you<00:30:45.779> can<00:30:45.960> prove 00:30:46.190 --> 00:30:46.200 align:start position:0% protocol novel then either you can prove 00:30:46.200 --> 00:30:47.510 align:start position:0% protocol novel then either you can prove that<00:30:46.320> it<00:30:46.500> works<00:30:46.799> or<00:30:46.919> you<00:30:47.100> can<00:30:47.220> use<00:30:47.340> this 00:30:47.510 --> 00:30:47.520 align:start position:0% that it works or you can use this 00:30:47.520 --> 00:30:49.730 align:start position:0% that it works or you can use this agent-based<00:30:48.120> simulation<00:30:48.539> to<00:30:48.899> sort<00:30:49.080> of 00:30:49.730 --> 00:30:49.740 align:start position:0% agent-based simulation to sort of 00:30:49.740 --> 00:30:52.430 align:start position:0% agent-based simulation to sort of not<00:30:50.159> prove<00:30:50.460> that<00:30:50.580> it<00:30:50.760> works<00:30:51.120> but<00:30:51.480> show<00:30:52.080> that<00:30:52.260> it 00:30:52.430 --> 00:30:52.440 align:start position:0% not prove that it works but show that it 00:30:52.440 --> 00:30:54.110 align:start position:0% not prove that it works but show that it doesn't<00:30:52.620> and<00:30:52.919> go<00:30:53.220> back<00:30:53.399> to<00:30:53.520> the<00:30:53.640> drawing<00:30:53.940> board 00:30:54.110 --> 00:30:54.120 align:start position:0% doesn't and go back to the drawing board 00:30:54.120 --> 00:31:06.470 align:start position:0% doesn't and go back to the drawing board yeah 00:31:06.470 --> 00:31:06.480 align:start position:0% 00:31:06.480 --> 00:31:09.889 align:start position:0% so<00:31:07.140> in<00:31:08.100> in<00:31:08.279> terms<00:31:08.520> of<00:31:08.580> training<00:31:09.059> though<00:31:09.240> there 00:31:09.889 --> 00:31:09.899 align:start position:0% so in in terms of training though there 00:31:09.899 --> 00:31:11.570 align:start position:0% so in in terms of training though there are<00:31:10.020> two<00:31:10.140> questions<00:31:10.320> I<00:31:10.799> I<00:31:10.919> can<00:31:11.159> have<00:31:11.279> the 00:31:11.570 --> 00:31:11.580 align:start position:0% are two questions I I can have the 00:31:11.580 --> 00:31:13.909 align:start position:0% are two questions I I can have the environment<00:31:12.059> sort<00:31:12.419> of<00:31:12.539> I<00:31:13.320> can<00:31:13.620> have<00:31:13.740> some 00:31:13.909 --> 00:31:13.919 align:start position:0% environment sort of I can have some 00:31:13.919 --> 00:31:15.230 align:start position:0% environment sort of I can have some agents<00:31:14.340> that<00:31:14.460> are<00:31:14.580> better<00:31:14.760> you<00:31:15.000> know<00:31:15.120> the 00:31:15.230 --> 00:31:15.240 align:start position:0% agents that are better you know the 00:31:15.240 --> 00:31:16.669 align:start position:0% agents that are better you know the agents<00:31:15.539> take<00:31:15.659> their<00:31:15.899> actions<00:31:16.260> quickly<00:31:16.559> and 00:31:16.669 --> 00:31:16.679 align:start position:0% agents take their actions quickly and 00:31:16.679 --> 00:31:19.370 align:start position:0% agents take their actions quickly and get<00:31:17.340> on<00:31:17.460> with<00:31:17.640> it<00:31:17.820> but<00:31:18.480> of<00:31:18.659> course<00:31:18.779> the<00:31:19.140> moment 00:31:19.370 --> 00:31:19.380 align:start position:0% get on with it but of course the moment 00:31:19.380 --> 00:31:21.230 align:start position:0% get on with it but of course the moment you<00:31:19.620> have<00:31:19.860> more<00:31:20.159> than<00:31:20.279> one<00:31:20.460> optimizing<00:31:21.059> and 00:31:21.230 --> 00:31:21.240 align:start position:0% you have more than one optimizing and 00:31:21.240 --> 00:31:23.690 align:start position:0% you have more than one optimizing and learning<00:31:21.779> agent<00:31:22.200> then<00:31:22.860> it's<00:31:23.100> the<00:31:23.340> whole<00:31:23.460> you 00:31:23.690 --> 00:31:23.700 align:start position:0% learning agent then it's the whole you 00:31:23.700 --> 00:31:25.430 align:start position:0% learning agent then it's the whole you know<00:31:23.760> Game<00:31:24.059> Theory<00:31:24.480> and<00:31:24.779> and<00:31:24.960> you<00:31:25.140> know<00:31:25.260> that 00:31:25.430 --> 00:31:25.440 align:start position:0% know Game Theory and and you know that 00:31:25.440 --> 00:31:27.289 align:start position:0% know Game Theory and and you know that they're<00:31:25.740> probably<00:31:25.919> and<00:31:26.520> and<00:31:26.700> then<00:31:26.880> it's<00:31:27.059> also 00:31:27.289 --> 00:31:27.299 align:start position:0% they're probably and and then it's also 00:31:27.299 --> 00:31:29.029 align:start position:0% they're probably and and then it's also very<00:31:27.539> difficult<00:31:27.779> to<00:31:28.080> set<00:31:28.260> up<00:31:28.440> or<00:31:28.860> very 00:31:29.029 --> 00:31:29.039 align:start position:0% very difficult to set up or very 00:31:29.039 --> 00:31:30.289 align:start position:0% very difficult to set up or very difficult<00:31:29.340> you<00:31:29.520> have<00:31:29.700> to<00:31:29.760> think<00:31:29.940> carefully 00:31:30.289 --> 00:31:30.299 align:start position:0% difficult you have to think carefully 00:31:30.299 --> 00:31:32.750 align:start position:0% difficult you have to think carefully about<00:31:30.720> how<00:31:30.960> you<00:31:31.140> set<00:31:31.320> it<00:31:31.440> up<00:31:31.620> you<00:31:32.039> know 00:31:32.750 --> 00:31:32.760 align:start position:0% about how you set it up you know 00:31:32.760 --> 00:31:36.529 align:start position:0% about how you set it up you know because<00:31:33.539> is<00:31:34.200> the<00:31:34.380> is<00:31:34.620> your<00:31:35.100> is<00:31:35.340> Agent<00:31:35.820> a<00:31:36.059> also 00:31:36.529 --> 00:31:36.539 align:start position:0% because is the is your is Agent a also 00:31:36.539 --> 00:31:38.389 align:start position:0% because is the is your is Agent a also trying<00:31:36.840> to<00:31:37.020> learn<00:31:37.200> the<00:31:37.440> optimal<00:31:37.860> response<00:31:38.279> of 00:31:38.389 --> 00:31:38.399 align:start position:0% trying to learn the optimal response of 00:31:38.399 --> 00:31:41.389 align:start position:0% trying to learn the optimal response of Agent<00:31:38.760> B<00:31:38.940> so<00:31:39.240> that<00:31:39.419> it<00:31:39.600> can<00:31:39.960> anticipate 00:31:41.389 --> 00:31:41.399 align:start position:0% Agent B so that it can anticipate 00:31:41.399 --> 00:31:43.310 align:start position:0% Agent B so that it can anticipate Etc<00:31:41.520> and<00:31:41.880> then<00:31:42.179> you<00:31:42.539> know<00:31:42.659> they<00:31:42.840> can<00:31:42.960> end<00:31:43.140> up 00:31:43.310 --> 00:31:43.320 align:start position:0% Etc and then you know they can end up 00:31:43.320 --> 00:31:45.409 align:start position:0% Etc and then you know they can end up chasing<00:31:43.740> themselves<00:31:44.100> in<00:31:44.399> circles<00:31:44.880> and<00:31:45.059> all 00:31:45.409 --> 00:31:45.419 align:start position:0% chasing themselves in circles and all 00:31:45.419 --> 00:31:47.930 align:start position:0% chasing themselves in circles and all sorts<00:31:45.779> of<00:31:45.840> weird<00:31:46.559> and<00:31:46.799> wonderful<00:31:47.159> things<00:31:47.640> can 00:31:47.930 --> 00:31:47.940 align:start position:0% sorts of weird and wonderful things can 00:31:47.940 --> 00:31:51.049 align:start position:0% sorts of weird and wonderful things can happen<00:31:48.120> you<00:31:48.539> know<00:31:48.659> it's<00:31:49.140> uh<00:31:49.679> game<00:31:50.340> game<00:31:50.399> theory 00:31:51.049 --> 00:31:51.059 align:start position:0% happen you know it's uh game game theory 00:31:51.059 --> 00:31:53.810 align:start position:0% happen you know it's uh game game theory and<00:31:51.240> NRL<00:31:52.020> comes<00:31:52.320> in<00:31:52.440> and<00:31:52.860> uh 00:31:53.810 --> 00:31:53.820 align:start position:0% and NRL comes in and uh 00:31:53.820 --> 00:31:56.269 align:start position:0% and NRL comes in and uh it's<00:31:54.240> it's<00:31:54.240> very<00:31:54.659> problem<00:31:54.899> specific<00:31:55.500> but<00:31:55.860> you 00:31:56.269 --> 00:31:56.279 align:start position:0% it's it's very problem specific but you 00:31:56.279 --> 00:31:58.190 align:start position:0% it's it's very problem specific but you can<00:31:56.399> you<00:31:56.640> can<00:31:56.820> end<00:31:57.000> up<00:31:57.120> with<00:31:57.360> situations<00:31:57.779> that 00:31:58.190 --> 00:31:58.200 align:start position:0% can you can end up with situations that 00:31:58.200 --> 00:31:59.510 align:start position:0% can you can end up with situations that they<00:31:58.500> don't<00:31:58.620> learn 00:31:59.510 --> 00:31:59.520 align:start position:0% they don't learn 00:31:59.520 --> 00:32:01.430 align:start position:0% they don't learn where<00:32:00.000> you<00:32:00.120> can<00:32:00.299> end<00:32:00.480> up<00:32:00.600> in<00:32:00.720> situations<00:32:01.080> then 00:32:01.430 --> 00:32:01.440 align:start position:0% where you can end up in situations then 00:32:01.440 --> 00:32:03.110 align:start position:0% where you can end up in situations then they<00:32:01.620> take<00:32:01.919> a<00:32:02.100> lot<00:32:02.220> longer<00:32:02.520> to<00:32:02.700> learn<00:32:02.820> because 00:32:03.110 --> 00:32:03.120 align:start position:0% they take a lot longer to learn because 00:32:03.120 --> 00:32:08.169 align:start position:0% they take a lot longer to learn because there<00:32:03.419> is<00:32:03.539> more<00:32:03.659> than<00:32:03.779> one<00:32:03.960> learning 00:32:08.169 --> 00:32:08.179 align:start position:0% 00:32:08.179 --> 00:32:10.250 align:start position:0% can<00:32:09.179> I<00:32:09.299> have<00:32:09.360> a<00:32:09.480> show<00:32:09.539> of<00:32:09.659> hands<00:32:09.899> of<00:32:09.960> the<00:32:10.080> people 00:32:10.250 --> 00:32:10.260 align:start position:0% can I have a show of hands of the people 00:32:10.260 --> 00:32:12.169 align:start position:0% can I have a show of hands of the people who<00:32:10.440> are<00:32:10.500> actually<00:32:10.620> trying<00:32:10.919> to<00:32:11.100> set<00:32:11.340> it<00:32:11.520> up<00:32:11.760> on 00:32:12.169 --> 00:32:12.179 align:start position:0% who are actually trying to set it up on 00:32:12.179 --> 00:32:14.930 align:start position:0% who are actually trying to set it up on their<00:32:12.360> computer<00:32:12.919> okay<00:32:13.919> okay<00:32:14.159> okay<00:32:14.220> so<00:32:14.760> so 00:32:14.930 --> 00:32:14.940 align:start position:0% their computer okay okay okay so so 00:32:14.940 --> 00:32:17.149 align:start position:0% their computer okay okay okay so so we're<00:32:15.179> we're<00:32:15.480> sort<00:32:15.960> of<00:32:16.080> now<00:32:16.440> is<00:32:16.620> the<00:32:16.799> time<00:32:16.980> to 00:32:17.149 --> 00:32:17.159 align:start position:0% we're we're sort of now is the time to 00:32:17.159 --> 00:32:18.710 align:start position:0% we're we're sort of now is the time to take<00:32:17.279> the<00:32:17.520> break<00:32:17.640> and<00:32:17.940> we're<00:32:18.240> going<00:32:18.419> to<00:32:18.480> have<00:32:18.600> a 00:32:18.710 --> 00:32:18.720 align:start position:0% take the break and we're going to have a 00:32:18.720 --> 00:32:20.230 align:start position:0% take the break and we're going to have a have<00:32:18.960> a<00:32:19.080> look<00:32:19.140> around 00:32:20.230 --> 00:32:20.240 align:start position:0% have a look around 00:32:20.240 --> 00:32:22.730 align:start position:0% have a look around Okay<00:32:21.240> so 00:32:22.730 --> 00:32:22.740 align:start position:0% Okay so 00:32:22.740 --> 00:32:24.350 align:start position:0% Okay so I<00:32:23.100> think<00:32:23.159> a<00:32:23.340> few<00:32:23.460> people<00:32:23.580> have<00:32:23.760> it<00:32:23.940> running<00:32:24.059> at 00:32:24.350 --> 00:32:24.360 align:start position:0% I think a few people have it running at 00:32:24.360 --> 00:32:27.169 align:start position:0% I think a few people have it running at least<00:32:24.539> uh<00:32:25.080> we're<00:32:25.260> gonna<00:32:25.440> I'm<00:32:26.399> gonna<00:32:26.520> crack<00:32:26.880> on 00:32:27.169 --> 00:32:27.179 align:start position:0% least uh we're gonna I'm gonna crack on 00:32:27.179 --> 00:32:29.389 align:start position:0% least uh we're gonna I'm gonna crack on and<00:32:27.539> then<00:32:27.779> we'll<00:32:28.500> have<00:32:28.740> another<00:32:28.860> break<00:32:29.100> in<00:32:29.279> a 00:32:29.389 --> 00:32:29.399 align:start position:0% and then we'll have another break in a 00:32:29.399 --> 00:32:30.529 align:start position:0% and then we'll have another break in a minute<00:32:29.520> for 00:32:30.529 --> 00:32:30.539 align:start position:0% minute for 00:32:30.539 --> 00:32:32.389 align:start position:0% minute for doing<00:32:30.840> the<00:32:31.080> next<00:32:31.200> bit<00:32:31.380> so<00:32:31.620> we<00:32:31.860> can<00:32:31.980> keep<00:32:32.220> going 00:32:32.389 --> 00:32:32.399 align:start position:0% doing the next bit so we can keep going 00:32:32.399 --> 00:32:34.190 align:start position:0% doing the next bit so we can keep going around<00:32:32.520> for<00:32:32.760> anyone<00:32:32.940> who's<00:32:33.179> who's<00:32:33.720> stuck<00:32:34.020> on 00:32:34.190 --> 00:32:34.200 align:start position:0% around for anyone who's who's stuck on 00:32:34.200 --> 00:32:36.110 align:start position:0% around for anyone who's who's stuck on this<00:32:34.380> bit<00:32:34.500> but 00:32:36.110 --> 00:32:36.120 align:start position:0% this bit but 00:32:36.120 --> 00:32:37.430 align:start position:0% this bit but I<00:32:36.480> want<00:32:36.600> to<00:32:36.720> give<00:32:36.779> more<00:32:36.960> interesting<00:32:37.260> things 00:32:37.430 --> 00:32:37.440 align:start position:0% I want to give more interesting things 00:32:37.440 --> 00:32:40.190 align:start position:0% I want to give more interesting things to<00:32:37.679> do<00:32:37.799> on<00:32:37.980> top<00:32:38.159> of<00:32:38.279> that<00:32:38.399> so 00:32:40.190 --> 00:32:40.200 align:start position:0% to do on top of that so 00:32:40.200 --> 00:32:43.190 align:start position:0% to do on top of that so a<00:32:40.620> quick<00:32:40.740> aside<00:32:41.100> once<00:32:41.640> once<00:32:42.240> the 00:32:43.190 --> 00:32:43.200 align:start position:0% a quick aside once once the 00:32:43.200 --> 00:32:44.630 align:start position:0% a quick aside once once the the 00:32:44.630 --> 00:32:44.640 align:start position:0% the 00:32:44.640 --> 00:32:47.029 align:start position:0% the null<00:32:45.120> chain<00:32:45.360> is<00:32:45.539> up<00:32:45.720> and<00:32:45.779> running<00:32:45.960> the<00:32:46.860> micro 00:32:47.029 --> 00:32:47.039 align:start position:0% null chain is up and running the micro 00:32:47.039 --> 00:32:49.250 align:start position:0% null chain is up and running the micro SIM<00:32:47.220> is<00:32:47.399> up<00:32:47.520> and<00:32:47.580> running<00:32:47.700> you<00:32:48.419> see 00:32:49.250 --> 00:32:49.260 align:start position:0% SIM is up and running you see 00:32:49.260 --> 00:32:50.630 align:start position:0% SIM is up and running you see anyone<00:32:49.679> who<00:32:49.860> got<00:32:49.919> it<00:32:50.039> working<00:32:50.159> would<00:32:50.460> have 00:32:50.630 --> 00:32:50.640 align:start position:0% anyone who got it working would have 00:32:50.640 --> 00:32:53.269 align:start position:0% anyone who got it working would have seen<00:32:50.760> something<00:32:50.940> like<00:32:51.240> on<00:32:52.020> the<00:32:52.200> right<00:32:52.320> here 00:32:53.269 --> 00:32:53.279 align:start position:0% seen something like on the right here 00:32:53.279 --> 00:32:55.250 align:start position:0% seen something like on the right here which<00:32:54.059> it<00:32:54.240> is 00:32:55.250 --> 00:32:55.260 align:start position:0% which it is 00:32:55.260 --> 00:32:57.529 align:start position:0% which it is it's<00:32:55.559> a<00:32:55.740> printed<00:32:55.980> output<00:32:56.220> log<00:32:56.399> of<00:32:56.820> some<00:32:57.299> stuff 00:32:57.529 --> 00:32:57.539 align:start position:0% it's a printed output log of some stuff 00:32:57.539 --> 00:32:59.450 align:start position:0% it's a printed output log of some stuff that's<00:32:57.840> going<00:32:58.020> on<00:32:58.200> inside 00:32:59.450 --> 00:32:59.460 align:start position:0% that's going on inside 00:32:59.460 --> 00:33:03.110 align:start position:0% that's going on inside markets<00:33:00.179> him<00:33:00.360> exposes<00:33:01.320> various<00:33:01.860> apis<00:33:02.820> for 00:33:03.110 --> 00:33:03.120 align:start position:0% markets him exposes various apis for 00:33:03.120 --> 00:33:06.110 align:start position:0% markets him exposes various apis for this<00:33:03.240> but<00:33:04.140> often<00:33:04.980> you<00:33:05.640> don't<00:33:05.700> want<00:33:05.880> to<00:33:06.000> just 00:33:06.110 --> 00:33:06.120 align:start position:0% this but often you don't want to just 00:33:06.120 --> 00:33:09.470 align:start position:0% this but often you don't want to just have<00:33:06.299> to<00:33:06.600> manually<00:33:07.260> call<00:33:08.039> python<00:33:08.880> apis<00:33:09.240> for 00:33:09.470 --> 00:33:09.480 align:start position:0% have to manually call python apis for 00:33:09.480 --> 00:33:10.490 align:start position:0% have to manually call python apis for every<00:33:09.600> single<00:33:09.840> thing<00:33:10.020> that<00:33:10.140> you<00:33:10.260> might<00:33:10.380> want 00:33:10.490 --> 00:33:10.500 align:start position:0% every single thing that you might want 00:33:10.500 --> 00:33:11.710 align:start position:0% every single thing that you might want to<00:33:10.620> experience 00:33:11.710 --> 00:33:11.720 align:start position:0% to experience 00:33:11.720 --> 00:33:15.590 align:start position:0% to experience so<00:33:12.720> we've<00:33:13.140> got<00:33:13.320> a<00:33:13.559> couple<00:33:13.679> of<00:33:14.059> useful<00:33:15.059> portals 00:33:15.590 --> 00:33:15.600 align:start position:0% so we've got a couple of useful portals 00:33:15.600 --> 00:33:18.590 align:start position:0% so we've got a couple of useful portals portals<00:33:16.140> on<00:33:16.260> your<00:33:16.380> data<00:33:17.220> you<00:33:17.940> can<00:33:18.059> if<00:33:18.419> you've 00:33:18.590 --> 00:33:18.600 align:start position:0% portals on your data you can if you've 00:33:18.600 --> 00:33:21.230 align:start position:0% portals on your data you can if you've set<00:33:18.720> up<00:33:18.899> the<00:33:19.080> UI<00:33:19.440> components<00:33:19.980> as<00:33:20.100> well<00:33:20.279> change 00:33:21.230 --> 00:33:21.240 align:start position:0% set up the UI components as well change 00:33:21.240 --> 00:33:25.730 align:start position:0% set up the UI components as well change a<00:33:21.779> flag<00:33:22.399> uh<00:33:23.399> this<00:33:23.580> run<00:33:23.820> with<00:33:24.000> console 00:33:25.730 --> 00:33:25.740 align:start position:0% a flag uh this run with console 00:33:25.740 --> 00:33:27.529 align:start position:0% a flag uh this run with console equals<00:33:26.460> true 00:33:27.529 --> 00:33:27.539 align:start position:0% equals true 00:33:27.539 --> 00:33:30.169 align:start position:0% equals true in<00:33:28.860> generally<00:33:29.399> wherever<00:33:29.700> you<00:33:29.820> happen<00:33:29.940> to<00:33:30.059> be 00:33:30.169 --> 00:33:30.179 align:start position:0% in generally wherever you happen to be 00:33:30.179 --> 00:33:33.769 align:start position:0% in generally wherever you happen to be running<00:33:30.419> your<00:33:30.659> Vega<00:33:31.159> uh<00:33:32.159> null<00:33:32.640> chain<00:33:32.880> that 00:33:33.769 --> 00:33:33.779 align:start position:0% running your Vega uh null chain that 00:33:33.779 --> 00:33:37.130 align:start position:0% running your Vega uh null chain that will<00:33:33.960> bring<00:33:34.260> up<00:33:34.440> in<00:33:35.279> a<00:33:35.399> web<00:33:35.700> browser<00:33:36.059> the<00:33:36.240> nice 00:33:37.130 --> 00:33:37.140 align:start position:0% will bring up in a web browser the nice 00:33:37.140 --> 00:33:38.630 align:start position:0% will bring up in a web browser the nice console<00:33:37.679> that<00:33:37.980> you<00:33:38.100> see<00:33:38.220> at<00:33:38.279> the<00:33:38.399> front<00:33:38.460> there 00:33:38.630 --> 00:33:38.640 align:start position:0% console that you see at the front there 00:33:38.640 --> 00:33:41.690 align:start position:0% console that you see at the front there that<00:33:39.059> is<00:33:39.240> the<00:33:39.419> same<00:33:39.539> console<00:33:39.960> that<00:33:40.500> people<00:33:41.279> use 00:33:41.690 --> 00:33:41.700 align:start position:0% that is the same console that people use 00:33:41.700 --> 00:33:44.450 align:start position:0% that is the same console that people use on<00:33:42.360> Vega<00:33:42.720> protocol<00:33:43.019> itself<00:33:43.380> so<00:33:44.039> that<00:33:44.220> has 00:33:44.450 --> 00:33:44.460 align:start position:0% on Vega protocol itself so that has 00:33:44.460 --> 00:33:46.070 align:start position:0% on Vega protocol itself so that has theoretically<00:33:45.179> pretty<00:33:45.419> much<00:33:45.539> everything<00:33:45.779> you 00:33:46.070 --> 00:33:46.080 align:start position:0% theoretically pretty much everything you 00:33:46.080 --> 00:33:48.830 align:start position:0% theoretically pretty much everything you need<00:33:46.260> you<00:33:46.919> can<00:33:47.039> even<00:33:47.240> trade<00:33:48.240> manually<00:33:48.600> through 00:33:48.830 --> 00:33:48.840 align:start position:0% need you can even trade manually through 00:33:48.840 --> 00:33:50.509 align:start position:0% need you can even trade manually through that<00:33:49.019> as<00:33:49.200> well<00:33:49.320> if<00:33:49.440> you<00:33:49.559> want<00:33:49.679> you<00:33:49.980> can<00:33:50.039> log<00:33:50.279> in 00:33:50.509 --> 00:33:50.519 align:start position:0% that as well if you want you can log in 00:33:50.519 --> 00:33:53.149 align:start position:0% that as well if you want you can log in as<00:33:51.000> your<00:33:51.600> agents<00:33:52.019> that<00:33:52.140> you've<00:33:52.320> set<00:33:52.500> up 00:33:53.149 --> 00:33:53.159 align:start position:0% as your agents that you've set up 00:33:53.159 --> 00:33:56.590 align:start position:0% as your agents that you've set up uh<00:33:53.940> we'll<00:33:54.419> probably<00:33:55.019> demo<00:33:55.380> it<00:33:55.500> a<00:33:55.620> bit<00:33:55.740> in<00:33:55.860> a<00:33:56.100> bit 00:33:56.590 --> 00:33:56.600 align:start position:0% uh we'll probably demo it a bit in a bit 00:33:56.600 --> 00:33:59.330 align:start position:0% uh we'll probably demo it a bit in a bit you<00:33:57.600> also<00:33:58.080> can 00:33:59.330 --> 00:33:59.340 align:start position:0% you also can 00:33:59.340 --> 00:34:00.889 align:start position:0% you also can is<00:33:59.700> actually<00:33:59.940> always<00:34:00.120> launched<00:34:00.539> if<00:34:00.659> you<00:34:00.779> take 00:34:00.889 --> 00:34:00.899 align:start position:0% is actually always launched if you take 00:34:00.899 --> 00:34:02.330 align:start position:0% is actually always launched if you take the<00:34:01.080> logs 00:34:02.330 --> 00:34:02.340 align:start position:0% the logs 00:34:02.340 --> 00:34:06.110 align:start position:0% the logs there<00:34:02.820> will<00:34:03.000> be<00:34:03.120> this<00:34:03.779> graphql<00:34:04.320> port<00:34:05.100> and<00:34:06.000> if 00:34:06.110 --> 00:34:06.120 align:start position:0% there will be this graphql port and if 00:34:06.120 --> 00:34:08.990 align:start position:0% there will be this graphql port and if you<00:34:06.240> go<00:34:06.419> there<00:34:06.600> and<00:34:07.200> you<00:34:07.380> know<00:34:07.500> graphql<00:34:08.040> you 00:34:08.990 --> 00:34:09.000 align:start position:0% you go there and you know graphql you 00:34:09.000 --> 00:34:12.829 align:start position:0% you go there and you know graphql you can<00:34:09.200> query<00:34:10.200> the<00:34:10.980> entire<00:34:11.159> system<00:34:11.399> with<00:34:11.940> a 00:34:12.829 --> 00:34:12.839 align:start position:0% can query the entire system with a 00:34:12.839 --> 00:34:14.329 align:start position:0% can query the entire system with a fairly 00:34:14.329 --> 00:34:14.339 align:start position:0% fairly 00:34:14.339 --> 00:34:17.930 align:start position:0% fairly hopefully<00:34:14.879> clear<00:34:15.179> graphql<00:34:16.139> queries<00:34:16.940> there's 00:34:17.930 --> 00:34:17.940 align:start position:0% hopefully clear graphql queries there's 00:34:17.940 --> 00:34:21.829 align:start position:0% hopefully clear graphql queries there's on<00:34:19.320> um<00:34:19.379> what<00:34:19.800> is<00:34:19.980> it<00:34:20.099> docs.vega<00:34:20.820> dot<00:34:21.419> XYZ 00:34:21.829 --> 00:34:21.839 align:start position:0% on um what is it docs.vega dot XYZ 00:34:21.839 --> 00:34:23.690 align:start position:0% on um what is it docs.vega dot XYZ there's<00:34:22.080> a<00:34:22.260> link<00:34:22.440> in<00:34:22.740> a<00:34:22.919> bit 00:34:23.690 --> 00:34:23.700 align:start position:0% there's a link in a bit 00:34:23.700 --> 00:34:25.490 align:start position:0% there's a link in a bit the<00:34:24.300> entire<00:34:24.599> sort<00:34:24.899> of<00:34:24.960> structure<00:34:25.260> of<00:34:25.379> your 00:34:25.490 --> 00:34:25.500 align:start position:0% the entire sort of structure of your 00:34:25.500 --> 00:34:29.210 align:start position:0% the entire sort of structure of your graphql<00:34:25.859> queries<00:34:26.339> you<00:34:26.580> want<00:34:26.760> as<00:34:26.940> well 00:34:29.210 --> 00:34:29.220 align:start position:0% 00:34:29.220 --> 00:34:30.770 align:start position:0% so 00:34:30.770 --> 00:34:30.780 align:start position:0% so 00:34:30.780 --> 00:34:32.629 align:start position:0% so for<00:34:30.960> anyone<00:34:31.260> who<00:34:31.379> has<00:34:31.440> good<00:34:31.619> at<00:34:31.740> running<00:34:31.919> for 00:34:32.629 --> 00:34:32.639 align:start position:0% for anyone who has good at running for 00:34:32.639 --> 00:34:37.070 align:start position:0% for anyone who has good at running for more<00:34:33.000> interesting<00:34:33.659> scenario<00:34:34.200> that's 00:34:37.070 --> 00:34:37.080 align:start position:0% more interesting scenario that's 00:34:37.080 --> 00:34:38.930 align:start position:0% more interesting scenario that's something<00:34:37.619> you<00:34:37.800> can<00:34:37.919> try<00:34:38.040> out<00:34:38.159> running<00:34:38.339> I'll 00:34:38.930 --> 00:34:38.940 align:start position:0% something you can try out running I'll 00:34:38.940 --> 00:34:40.849 align:start position:0% something you can try out running I'll leave<00:34:39.119> it<00:34:39.300> up<00:34:39.899> um<00:34:39.960> actually<00:34:40.200> let<00:34:40.500> me<00:34:40.619> skip<00:34:40.679> to 00:34:40.849 --> 00:34:40.859 align:start position:0% leave it up um actually let me skip to 00:34:40.859 --> 00:34:43.070 align:start position:0% leave it up um actually let me skip to the<00:34:40.919> next<00:34:41.040> thing 00:34:43.070 --> 00:34:43.080 align:start position:0% the next thing 00:34:43.080 --> 00:34:45.950 align:start position:0% the next thing this<00:34:43.500> is<00:34:43.619> what<00:34:43.740> I'm<00:34:43.919> going<00:34:44.040> to<00:34:44.099> talk<00:34:44.220> through 00:34:45.950 --> 00:34:45.960 align:start position:0% this is what I'm going to talk through 00:34:45.960 --> 00:34:47.510 align:start position:0% this is what I'm going to talk through with<00:34:46.260> this<00:34:46.440> app<00:34:46.619> so<00:34:46.740> anyone<00:34:47.040> can<00:34:47.099> type<00:34:47.220> it<00:34:47.399> up 00:34:47.510 --> 00:34:47.520 align:start position:0% with this app so anyone can type it up 00:34:47.520 --> 00:34:50.329 align:start position:0% with this app so anyone can type it up so<00:34:48.240> the<00:34:48.659> components<00:34:49.200> that 00:34:50.329 --> 00:34:50.339 align:start position:0% so the components that 00:34:50.339 --> 00:34:53.629 align:start position:0% so the components that Vega<00:34:51.060> itself<00:34:51.540> runs<00:34:52.440> on<00:34:52.619> a<00:34:52.740> on<00:34:52.980> a<00:34:53.220> validated 00:34:53.629 --> 00:34:53.639 align:start position:0% Vega itself runs on a on a validated 00:34:53.639 --> 00:34:55.609 align:start position:0% Vega itself runs on a on a validated node<00:34:54.060> that<00:34:54.599> we're<00:34:54.780> also<00:34:55.080> going<00:34:55.260> to<00:34:55.379> be<00:34:55.440> running 00:34:55.609 --> 00:34:55.619 align:start position:0% node that we're also going to be running 00:34:55.619 --> 00:34:57.109 align:start position:0% node that we're also going to be running locally 00:34:57.109 --> 00:34:57.119 align:start position:0% locally 00:34:57.119 --> 00:34:59.570 align:start position:0% locally that<00:34:57.780> the<00:34:58.080> null<00:34:58.260> service<00:34:58.440> spins<00:34:58.800> up<00:34:58.980> there<00:34:59.460> are 00:34:59.570 --> 00:34:59.580 align:start position:0% that the null service spins up there are 00:34:59.580 --> 00:35:00.950 align:start position:0% that the null service spins up there are a<00:34:59.640> few<00:34:59.760> different<00:34:59.880> ones<00:35:00.180> we've<00:35:00.420> got<00:35:00.480> Vega 00:35:00.950 --> 00:35:00.960 align:start position:0% a few different ones we've got Vega 00:35:00.960 --> 00:35:04.250 align:start position:0% a few different ones we've got Vega which<00:35:01.260> is<00:35:01.440> the<00:35:01.740> core<00:35:01.859> process<00:35:02.400> that's<00:35:02.760> the 00:35:04.250 --> 00:35:04.260 align:start position:0% which is the core process that's the 00:35:04.260 --> 00:35:06.650 align:start position:0% which is the core process that's the um go 00:35:06.650 --> 00:35:06.660 align:start position:0% um go 00:35:06.660 --> 00:35:09.349 align:start position:0% um go blockchain<00:35:07.380> client<00:35:07.980> that<00:35:08.700> does<00:35:08.940> all<00:35:09.119> of<00:35:09.240> your 00:35:09.349 --> 00:35:09.359 align:start position:0% blockchain client that does all of your 00:35:09.359 --> 00:35:11.450 align:start position:0% blockchain client that does all of your transaction<00:35:09.839> processing<00:35:10.380> and<00:35:10.859> outputs<00:35:11.339> your 00:35:11.450 --> 00:35:11.460 align:start position:0% transaction processing and outputs your 00:35:11.460 --> 00:35:13.069 align:start position:0% transaction processing and outputs your States 00:35:13.069 --> 00:35:13.079 align:start position:0% States 00:35:13.079 --> 00:35:15.670 align:start position:0% States that<00:35:13.680> is<00:35:14.220> obviously<00:35:14.579> it's<00:35:14.700> a<00:35:14.880> point<00:35:15.060> in<00:35:15.240> time 00:35:15.670 --> 00:35:15.680 align:start position:0% that is obviously it's a point in time 00:35:15.680 --> 00:35:19.670 align:start position:0% that is obviously it's a point in time proceeding<00:35:16.680> thing<00:35:17.000> so<00:35:18.000> we<00:35:18.359> also<00:35:18.599> want<00:35:19.020> the 00:35:19.670 --> 00:35:19.680 align:start position:0% proceeding thing so we also want the 00:35:19.680 --> 00:35:22.990 align:start position:0% proceeding thing so we also want the data<00:35:20.099> node<00:35:20.339> which<00:35:20.700> is<00:35:21.200> listens<00:35:22.200> to<00:35:22.320> external 00:35:22.990 --> 00:35:23.000 align:start position:0% data node which is listens to external 00:35:23.000 --> 00:35:26.150 align:start position:0% data node which is listens to external events<00:35:24.000> output<00:35:24.720> by<00:35:25.079> the<00:35:25.320> note<00:35:25.500> core<00:35:25.859> node 00:35:26.150 --> 00:35:26.160 align:start position:0% events output by the note core node 00:35:26.160 --> 00:35:29.450 align:start position:0% events output by the note core node itself<00:35:26.540> and<00:35:27.540> saves<00:35:28.320> those<00:35:28.440> into<00:35:28.619> a 00:35:29.450 --> 00:35:29.460 align:start position:0% itself and saves those into a 00:35:29.460 --> 00:35:31.490 align:start position:0% itself and saves those into a a<00:35:29.760> postgres<00:35:30.119> database<00:35:30.599> and<00:35:30.960> allows<00:35:31.320> you<00:35:31.380> to 00:35:31.490 --> 00:35:31.500 align:start position:0% a postgres database and allows you to 00:35:31.500 --> 00:35:32.829 align:start position:0% a postgres database and allows you to query<00:35:31.680> all<00:35:31.920> of<00:35:32.099> that 00:35:32.829 --> 00:35:32.839 align:start position:0% query all of that 00:35:32.839 --> 00:35:34.790 align:start position:0% query all of that historic<00:35:33.839> data 00:35:34.790 --> 00:35:34.800 align:start position:0% historic data 00:35:34.800 --> 00:35:36.349 align:start position:0% historic data and<00:35:35.280> that's<00:35:35.460> generally<00:35:35.940> what<00:35:36.060> you'll<00:35:36.240> be 00:35:36.349 --> 00:35:36.359 align:start position:0% and that's generally what you'll be 00:35:36.359 --> 00:35:38.510 align:start position:0% and that's generally what you'll be using<00:35:36.540> when<00:35:36.720> you're<00:35:36.839> querying<00:35:37.320> any<00:35:37.980> data<00:35:38.339> from 00:35:38.510 --> 00:35:38.520 align:start position:0% using when you're querying any data from 00:35:38.520 --> 00:35:41.690 align:start position:0% using when you're querying any data from Vega 00:35:41.690 --> 00:35:41.700 align:start position:0% 00:35:41.700 --> 00:35:43.490 align:start position:0% storage<00:35:42.000> layer<00:35:42.420> additionally<00:35:43.020> there's<00:35:43.320> a 00:35:43.490 --> 00:35:43.500 align:start position:0% storage layer additionally there's a 00:35:43.500 --> 00:35:45.470 align:start position:0% storage layer additionally there's a couple<00:35:43.619> of<00:35:43.740> extra<00:35:44.520> things<00:35:44.820> there's<00:35:45.000> a<00:35:45.180> console 00:35:45.470 --> 00:35:45.480 align:start position:0% couple of extra things there's a console 00:35:45.480 --> 00:35:48.349 align:start position:0% couple of extra things there's a console as<00:35:45.720> I<00:35:45.900> mentioned<00:35:46.140> previously<00:35:46.500> that<00:35:47.460> isn't 00:35:48.349 --> 00:35:48.359 align:start position:0% as I mentioned previously that isn't 00:35:48.359 --> 00:35:50.690 align:start position:0% as I mentioned previously that isn't necessary<00:35:48.660> but<00:35:49.140> it's<00:35:49.560> very<00:35:49.800> useful<00:35:50.099> front<00:35:50.460> end 00:35:50.690 --> 00:35:50.700 align:start position:0% necessary but it's very useful front end 00:35:50.700 --> 00:35:53.990 align:start position:0% necessary but it's very useful front end there's<00:35:51.480> also<00:35:51.839> the<00:35:52.380> Vega<00:35:52.740> wallet 00:35:53.990 --> 00:35:54.000 align:start position:0% there's also the Vega wallet 00:35:54.000 --> 00:35:57.290 align:start position:0% there's also the Vega wallet the<00:35:55.079> wallet<00:35:55.740> is<00:35:55.859> basically<00:35:56.300> size 00:35:57.290 --> 00:35:57.300 align:start position:0% the wallet is basically size 00:35:57.300 --> 00:35:59.870 align:start position:0% the wallet is basically size transactions<00:35:57.960> and<00:35:58.200> ensures<00:35:58.619> that 00:35:59.870 --> 00:35:59.880 align:start position:0% transactions and ensures that 00:35:59.880 --> 00:36:02.270 align:start position:0% transactions and ensures that any<00:36:00.540> sort<00:36:00.780> of<00:36:00.900> custom<00:36:01.079> signing<00:36:01.859> we<00:36:02.040> have<00:36:02.160> some 00:36:02.270 --> 00:36:02.280 align:start position:0% any sort of custom signing we have some 00:36:02.280 --> 00:36:04.069 align:start position:0% any sort of custom signing we have some proof<00:36:02.579> of<00:36:02.640> work<00:36:02.820> to<00:36:03.060> stop<00:36:03.240> spam<00:36:03.599> attacks<00:36:03.960> and 00:36:04.069 --> 00:36:04.079 align:start position:0% proof of work to stop spam attacks and 00:36:04.079 --> 00:36:05.930 align:start position:0% proof of work to stop spam attacks and stuff<00:36:04.200> and<00:36:04.440> that<00:36:04.500> handles<00:36:04.800> all<00:36:04.980> that<00:36:05.160> it's 00:36:05.930 --> 00:36:05.940 align:start position:0% stuff and that handles all that it's 00:36:05.940 --> 00:36:08.690 align:start position:0% stuff and that handles all that it's optional<00:36:06.359> here<00:36:06.540> because<00:36:06.920> for<00:36:07.920> the<00:36:08.280> null<00:36:08.460> chain 00:36:08.690 --> 00:36:08.700 align:start position:0% optional here because for the null chain 00:36:08.700 --> 00:36:11.150 align:start position:0% optional here because for the null chain what<00:36:08.940> we<00:36:09.000> actually<00:36:09.119> do<00:36:09.300> is<00:36:09.480> Skip<00:36:10.260> all<00:36:10.859> of<00:36:11.040> our 00:36:11.150 --> 00:36:11.160 align:start position:0% what we actually do is Skip all of our 00:36:11.160 --> 00:36:14.450 align:start position:0% what we actually do is Skip all of our validation<00:36:11.960> so<00:36:12.960> that<00:36:13.140> it<00:36:13.380> will<00:36:13.560> blindly 00:36:14.450 --> 00:36:14.460 align:start position:0% validation so that it will blindly 00:36:14.460 --> 00:36:16.370 align:start position:0% validation so that it will blindly accept<00:36:14.640> if<00:36:15.359> you<00:36:15.420> send<00:36:15.540> a<00:36:15.720> transaction<00:36:16.020> and<00:36:16.260> say 00:36:16.370 --> 00:36:16.380 align:start position:0% accept if you send a transaction and say 00:36:16.380 --> 00:36:18.290 align:start position:0% accept if you send a transaction and say it's<00:36:16.560> from<00:36:16.740> whoever<00:36:17.099> it<00:36:17.640> believes<00:36:18.060> it's<00:36:18.180> from 00:36:18.290 --> 00:36:18.300 align:start position:0% it's from whoever it believes it's from 00:36:18.300 --> 00:36:20.450 align:start position:0% it's from whoever it believes it's from whoever<00:36:18.599> so<00:36:19.440> you<00:36:19.740> don't<00:36:19.859> necessarily<00:36:20.220> need 00:36:20.450 --> 00:36:20.460 align:start position:0% whoever so you don't necessarily need 00:36:20.460 --> 00:36:23.210 align:start position:0% whoever so you don't necessarily need that<00:36:21.180> what<00:36:21.480> it<00:36:21.660> will<00:36:21.780> spin<00:36:22.079> up<00:36:22.200> is<00:36:22.500> if<00:36:22.859> you<00:36:23.040> spin 00:36:23.210 --> 00:36:23.220 align:start position:0% that what it will spin up is if you spin 00:36:23.220 --> 00:36:25.250 align:start position:0% that what it will spin up is if you spin up<00:36:23.339> a<00:36:23.520> console<00:36:23.820> the<00:36:24.300> two<00:36:24.480> interact<00:36:24.900> and<00:36:25.079> a<00:36:25.200> lot 00:36:25.250 --> 00:36:25.260 align:start position:0% up a console the two interact and a lot 00:36:25.260 --> 00:36:27.890 align:start position:0% up a console the two interact and a lot together<00:36:25.440> so<00:36:25.920> we<00:36:26.579> use<00:36:26.760> a<00:36:27.000> full<00:36:27.180> wallet<00:36:27.720> for 00:36:27.890 --> 00:36:27.900 align:start position:0% together so we use a full wallet for 00:36:27.900 --> 00:36:30.470 align:start position:0% together so we use a full wallet for that 00:36:30.470 --> 00:36:30.480 align:start position:0% 00:36:30.480 --> 00:36:31.730 align:start position:0% so 00:36:31.730 --> 00:36:31.740 align:start position:0% so 00:36:31.740 --> 00:36:34.430 align:start position:0% so once<00:36:32.400> we've<00:36:32.579> got<00:36:32.760> our<00:36:33.119> our<00:36:33.599> Market<00:36:33.780> Sim<00:36:34.079> set<00:36:34.320> up 00:36:34.430 --> 00:36:34.440 align:start position:0% once we've got our our Market Sim set up 00:36:34.440 --> 00:36:37.190 align:start position:0% once we've got our our Market Sim set up how<00:36:34.980> do<00:36:35.099> we<00:36:35.220> actually<00:36:35.339> run<00:36:35.579> our<00:36:36.180> scenarios 00:36:37.190 --> 00:36:37.200 align:start position:0% how do we actually run our scenarios 00:36:37.200 --> 00:36:40.910 align:start position:0% how do we actually run our scenarios there<00:36:38.460> set<00:36:39.060> up<00:36:39.240> as 00:36:40.910 --> 00:36:40.920 align:start position:0% there set up as 00:36:40.920 --> 00:36:43.370 align:start position:0% there set up as ideally<00:36:41.520> Plug<00:36:41.760> and<00:36:41.940> Play<00:36:42.060> components<00:36:42.599> the 00:36:43.370 --> 00:36:43.380 align:start position:0% ideally Plug and Play components the 00:36:43.380 --> 00:36:44.270 align:start position:0% ideally Plug and Play components the overall 00:36:44.270 --> 00:36:44.280 align:start position:0% overall 00:36:44.280 --> 00:36:46.130 align:start position:0% overall thing<00:36:44.640> we<00:36:44.760> set<00:36:44.940> up<00:36:45.060> is<00:36:45.240> we<00:36:45.420> call<00:36:45.540> a<00:36:45.720> scenario 00:36:46.130 --> 00:36:46.140 align:start position:0% thing we set up is we call a scenario 00:36:46.140 --> 00:36:48.770 align:start position:0% thing we set up is we call a scenario that<00:36:46.859> consists<00:36:47.280> of<00:36:47.339> an<00:36:47.940> environment<00:36:48.300> which<00:36:48.599> is 00:36:48.770 --> 00:36:48.780 align:start position:0% that consists of an environment which is 00:36:48.780 --> 00:36:50.990 align:start position:0% that consists of an environment which is your<00:36:49.619> background<00:36:50.160> environment<00:36:50.579> and<00:36:50.880> your 00:36:50.990 --> 00:36:51.000 align:start position:0% your background environment and your 00:36:51.000 --> 00:36:53.210 align:start position:0% your background environment and your Vegas<00:36:51.240> setup<00:36:51.720> so<00:36:52.440> that<00:36:52.619> will<00:36:52.800> include<00:36:53.040> things 00:36:53.210 --> 00:36:53.220 align:start position:0% Vegas setup so that will include things 00:36:53.220 --> 00:36:55.790 align:start position:0% Vegas setup so that will include things like<00:36:53.400> how<00:36:53.579> many<00:36:53.760> steps<00:36:54.119> you<00:36:54.240> want<00:36:54.359> to<00:36:54.480> run<00:36:54.800> your 00:36:55.790 --> 00:36:55.800 align:start position:0% like how many steps you want to run your 00:36:55.800 --> 00:36:57.589 align:start position:0% like how many steps you want to run your simulation<00:36:56.520> for 00:36:57.589 --> 00:36:57.599 align:start position:0% simulation for 00:36:57.599 --> 00:37:00.530 align:start position:0% simulation for uh<00:36:58.500> how<00:36:58.740> your<00:36:58.920> Vega<00:36:59.339> is<00:36:59.460> set<00:36:59.579> up 00:37:00.530 --> 00:37:00.540 align:start position:0% uh how your Vega is set up 00:37:00.540 --> 00:37:02.810 align:start position:0% uh how your Vega is set up and<00:37:01.440> sort<00:37:01.920> of<00:37:02.040> what<00:37:02.160> kind<00:37:02.280> of<00:37:02.400> logging<00:37:02.700> you 00:37:02.810 --> 00:37:02.820 align:start position:0% and sort of what kind of logging you 00:37:02.820 --> 00:37:04.670 align:start position:0% and sort of what kind of logging you want<00:37:02.940> that<00:37:03.240> kind<00:37:03.359> of<00:37:03.480> background 00:37:04.670 --> 00:37:04.680 align:start position:0% want that kind of background 00:37:04.680 --> 00:37:07.430 align:start position:0% want that kind of background detail<00:37:05.460> we<00:37:06.180> then<00:37:06.359> plug<00:37:06.599> in<00:37:06.780> the<00:37:07.200> various 00:37:07.430 --> 00:37:07.440 align:start position:0% detail we then plug in the various 00:37:07.440 --> 00:37:09.770 align:start position:0% detail we then plug in the various agents<00:37:07.859> some<00:37:08.400> of<00:37:08.520> whom<00:37:08.700> will<00:37:09.000> be<00:37:09.240> setting 00:37:09.770 --> 00:37:09.780 align:start position:0% agents some of whom will be setting 00:37:09.780 --> 00:37:13.490 align:start position:0% agents some of whom will be setting prices<00:37:09.960> they<00:37:10.560> could<00:37:10.740> be<00:37:10.980> acting<00:37:11.880> randomly<00:37:12.780> and 00:37:13.490 --> 00:37:13.500 align:start position:0% prices they could be acting randomly and 00:37:13.500 --> 00:37:15.349 align:start position:0% prices they could be acting randomly and each<00:37:13.800> of<00:37:13.920> them<00:37:14.099> will<00:37:14.339> have 00:37:15.349 --> 00:37:15.359 align:start position:0% each of them will have 00:37:15.359 --> 00:37:17.510 align:start position:0% each of them will have something<00:37:15.900> they<00:37:16.140> do<00:37:16.380> you'll<00:37:16.980> see<00:37:17.160> when<00:37:17.339> you 00:37:17.510 --> 00:37:17.520 align:start position:0% something they do you'll see when you 00:37:17.520 --> 00:37:19.370 align:start position:0% something they do you'll see when you build<00:37:17.940> one<00:37:18.119> yourself<00:37:18.359> in<00:37:18.599> a<00:37:18.720> bit<00:37:18.780> something<00:37:19.200> to 00:37:19.370 --> 00:37:19.380 align:start position:0% build one yourself in a bit something to 00:37:19.380 --> 00:37:21.470 align:start position:0% build one yourself in a bit something to do<00:37:19.500> with<00:37:19.619> startup<00:37:20.040> often<00:37:20.579> they'll<00:37:20.880> force<00:37:21.359> it 00:37:21.470 --> 00:37:21.480 align:start position:0% do with startup often they'll force it 00:37:21.480 --> 00:37:22.670 align:start position:0% do with startup often they'll force it themselves<00:37:21.780> some<00:37:21.839> tokens<00:37:22.200> that<00:37:22.440> kind<00:37:22.560> of 00:37:22.670 --> 00:37:22.680 align:start position:0% themselves some tokens that kind of 00:37:22.680 --> 00:37:24.770 align:start position:0% themselves some tokens that kind of thing<00:37:23.280> and<00:37:23.820> then<00:37:24.000> they've<00:37:24.420> just<00:37:24.540> got<00:37:24.660> a 00:37:24.770 --> 00:37:24.780 align:start position:0% thing and then they've just got a 00:37:24.780 --> 00:37:26.210 align:start position:0% thing and then they've just got a function<00:37:25.020> and<00:37:25.380> each<00:37:25.500> step<00:37:25.740> call<00:37:26.040> that 00:37:26.210 --> 00:37:26.220 align:start position:0% function and each step call that 00:37:26.220 --> 00:37:28.550 align:start position:0% function and each step call that function<00:37:26.520> and<00:37:27.180> it<00:37:27.839> does<00:37:27.960> whatever<00:37:28.140> it<00:37:28.380> wants 00:37:28.550 --> 00:37:28.560 align:start position:0% function and it does whatever it wants 00:37:28.560 --> 00:37:29.990 align:start position:0% function and it does whatever it wants to<00:37:28.619> do<00:37:28.740> it<00:37:28.980> pulls<00:37:29.280> in<00:37:29.339> data<00:37:29.640> from<00:37:29.760> the<00:37:29.880> market 00:37:29.990 --> 00:37:30.000 align:start position:0% to do it pulls in data from the market 00:37:30.000 --> 00:37:34.370 align:start position:0% to do it pulls in data from the market it<00:37:30.660> trades<00:37:31.140> they<00:37:31.500> do<00:37:31.619> whatever 00:37:34.370 --> 00:37:34.380 align:start position:0% 00:37:34.380 --> 00:37:38.089 align:start position:0% so<00:37:35.040> scenario<00:37:36.000> environment 00:37:38.089 --> 00:37:38.099 align:start position:0% so scenario environment 00:37:38.099 --> 00:37:39.829 align:start position:0% so scenario environment you'll 00:37:39.829 --> 00:37:39.839 align:start position:0% you'll 00:37:39.839 --> 00:37:42.349 align:start position:0% you'll see<00:37:40.560> that<00:37:40.800> when<00:37:41.040> we<00:37:41.160> go<00:37:41.339> in<00:37:41.700> a<00:37:41.880> minute<00:37:42.000> to<00:37:42.180> the 00:37:42.349 --> 00:37:42.359 align:start position:0% see that when we go in a minute to the 00:37:42.359 --> 00:37:44.750 align:start position:0% see that when we go in a minute to the agents<00:37:42.660> themselves<00:37:43.020> so<00:37:43.980> yeah<00:37:44.280> what's<00:37:44.579> an 00:37:44.750 --> 00:37:44.760 align:start position:0% agents themselves so yeah what's an 00:37:44.760 --> 00:37:46.730 align:start position:0% agents themselves so yeah what's an agent<00:37:45.060> it's<00:37:45.300> it's<00:37:45.540> fairly<00:37:45.960> simple<00:37:46.079> ultimately 00:37:46.730 --> 00:37:46.740 align:start position:0% agent it's it's fairly simple ultimately 00:37:46.740 --> 00:37:49.370 align:start position:0% agent it's it's fairly simple ultimately it's<00:37:47.220> an<00:37:47.640> initialized<00:37:48.119> step<00:37:48.420> where<00:37:49.020> they 00:37:49.370 --> 00:37:49.380 align:start position:0% it's an initialized step where they 00:37:49.380 --> 00:37:52.069 align:start position:0% it's an initialized step where they generally<00:37:49.619> force<00:37:49.980> it<00:37:50.099> sometimes<00:37:50.880> they<00:37:51.240> will 00:37:52.069 --> 00:37:52.079 align:start position:0% generally force it sometimes they will 00:37:52.079 --> 00:37:54.710 align:start position:0% generally force it sometimes they will um<00:37:52.140> do<00:37:52.680> things<00:37:52.920> so<00:37:53.220> we'll<00:37:53.460> have<00:37:53.640> an<00:37:53.820> agent<00:37:54.119> that 00:37:54.710 --> 00:37:54.720 align:start position:0% um do things so we'll have an agent that 00:37:54.720 --> 00:37:56.930 align:start position:0% um do things so we'll have an agent that sets<00:37:55.260> up<00:37:55.320> all<00:37:55.500> the<00:37:55.619> assets<00:37:55.859> because<00:37:56.160> you<00:37:56.700> start 00:37:56.930 --> 00:37:56.940 align:start position:0% sets up all the assets because you start 00:37:56.940 --> 00:37:58.550 align:start position:0% sets up all the assets because you start with<00:37:57.060> a<00:37:57.240> blank<00:37:57.480> blockchain<00:37:58.140> you<00:37:58.380> don't<00:37:58.500> have 00:37:58.550 --> 00:37:58.560 align:start position:0% with a blank blockchain you don't have 00:37:58.560 --> 00:38:00.230 align:start position:0% with a blank blockchain you don't have any<00:37:58.740> assets<00:37:59.160> any<00:37:59.339> markets<00:37:59.880> that<00:38:00.000> kind<00:38:00.180> of 00:38:00.230 --> 00:38:00.240 align:start position:0% any assets any markets that kind of 00:38:00.240 --> 00:38:02.990 align:start position:0% any assets any markets that kind of thing<00:38:00.359> so<00:38:00.720> there's<00:38:01.680> you<00:38:02.160> may<00:38:02.280> see<00:38:02.460> if<00:38:02.700> you<00:38:02.880> look 00:38:02.990 --> 00:38:03.000 align:start position:0% thing so there's you may see if you look 00:38:03.000 --> 00:38:05.810 align:start position:0% thing so there's you may see if you look through<00:38:03.300> a<00:38:03.780> market<00:38:03.960> manager<00:38:04.560> who<00:38:05.339> does<00:38:05.640> all 00:38:05.810 --> 00:38:05.820 align:start position:0% through a market manager who does all 00:38:05.820 --> 00:38:09.829 align:start position:0% through a market manager who does all this<00:38:05.940> setup<00:38:06.240> for<00:38:06.420> you<00:38:07.079> then<00:38:08.040> they'll<00:38:08.579> have<00:38:09.300> a 00:38:09.829 --> 00:38:09.839 align:start position:0% this setup for you then they'll have a 00:38:09.839 --> 00:38:11.569 align:start position:0% this setup for you then they'll have a function<00:38:10.440> that's<00:38:10.680> called<00:38:10.920> every<00:38:11.160> scenario 00:38:11.569 --> 00:38:11.579 align:start position:0% function that's called every scenario 00:38:11.579 --> 00:38:14.990 align:start position:0% function that's called every scenario step<00:38:11.839> however<00:38:12.839> many<00:38:12.960> steps<00:38:13.680> you<00:38:13.800> do<00:38:14.000> generally 00:38:14.990 --> 00:38:15.000 align:start position:0% step however many steps you do generally 00:38:15.000 --> 00:38:16.490 align:start position:0% step however many steps you do generally will<00:38:15.240> sort<00:38:15.480> of<00:38:15.540> randomly<00:38:15.839> shuffle<00:38:16.079> them<00:38:16.380> so 00:38:16.490 --> 00:38:16.500 align:start position:0% will sort of randomly shuffle them so 00:38:16.500 --> 00:38:17.510 align:start position:0% will sort of randomly shuffle them so that<00:38:16.619> you're<00:38:16.740> not<00:38:16.859> always<00:38:17.040> getting<00:38:17.220> the<00:38:17.400> first 00:38:17.510 --> 00:38:17.520 align:start position:0% that you're not always getting the first 00:38:17.520 --> 00:38:19.970 align:start position:0% that you're not always getting the first agent<00:38:17.880> called<00:38:18.119> First<00:38:18.660> in<00:38:18.900> any<00:38:19.079> step 00:38:19.970 --> 00:38:19.980 align:start position:0% agent called First in any step 00:38:19.980 --> 00:38:22.810 align:start position:0% agent called First in any step and<00:38:20.579> then<00:38:20.700> a<00:38:20.940> finalized<00:38:21.359> method<00:38:21.660> that<00:38:22.440> most 00:38:22.810 --> 00:38:22.820 align:start position:0% and then a finalized method that most 00:38:22.820 --> 00:38:26.150 align:start position:0% and then a finalized method that most mostly<00:38:23.820> you<00:38:24.060> can<00:38:24.180> ignore<00:38:24.480> but<00:38:24.920> uh<00:38:25.920> often 00:38:26.150 --> 00:38:26.160 align:start position:0% mostly you can ignore but uh often 00:38:26.160 --> 00:38:27.410 align:start position:0% mostly you can ignore but uh often you'll<00:38:26.339> want<00:38:26.520> one<00:38:26.640> to<00:38:26.760> sort<00:38:26.940> of<00:38:27.000> settle<00:38:27.240> the 00:38:27.410 --> 00:38:27.420 align:start position:0% you'll want one to sort of settle the 00:38:27.420 --> 00:38:30.109 align:start position:0% you'll want one to sort of settle the market<00:38:27.540> and<00:38:28.020> things<00:38:28.260> so<00:38:28.619> that's<00:38:29.579> how<00:38:29.760> you<00:38:29.880> you 00:38:30.109 --> 00:38:30.119 align:start position:0% market and things so that's how you you 00:38:30.119 --> 00:38:31.849 align:start position:0% market and things so that's how you you want<00:38:30.300> to<00:38:30.359> set<00:38:30.480> up<00:38:30.599> your<00:38:30.720> agent<00:38:31.020> there's<00:38:31.680> one 00:38:31.849 --> 00:38:31.859 align:start position:0% want to set up your agent there's one 00:38:31.859 --> 00:38:33.410 align:start position:0% want to set up your agent there's one more<00:38:32.040> thing<00:38:32.280> I<00:38:32.760> mentioned<00:38:33.000> earlier<00:38:33.240> that 00:38:33.410 --> 00:38:33.420 align:start position:0% more thing I mentioned earlier that 00:38:33.420 --> 00:38:35.270 align:start position:0% more thing I mentioned earlier that sometimes<00:38:33.839> the<00:38:34.380> blockchain<00:38:34.740> does<00:38:34.980> have<00:38:35.160> to 00:38:35.270 --> 00:38:35.280 align:start position:0% sometimes the blockchain does have to 00:38:35.280 --> 00:38:37.849 align:start position:0% sometimes the blockchain does have to bleed<00:38:35.520> back<00:38:35.700> in<00:38:35.880> you'll<00:38:36.720> see<00:38:36.960> scattered 00:38:37.849 --> 00:38:37.859 align:start position:0% bleed back in you'll see scattered 00:38:37.859 --> 00:38:38.870 align:start position:0% bleed back in you'll see scattered throughout<00:38:38.099> occasionally<00:38:38.400> you'll<00:38:38.579> wait<00:38:38.760> for 00:38:38.870 --> 00:38:38.880 align:start position:0% throughout occasionally you'll wait for 00:38:38.880 --> 00:38:41.450 align:start position:0% throughout occasionally you'll wait for total<00:38:39.240> catch<00:38:39.780> up<00:38:39.839> function<00:38:40.320> basically<00:38:41.280> what 00:38:41.450 --> 00:38:41.460 align:start position:0% total catch up function basically what 00:38:41.460 --> 00:38:43.609 align:start position:0% total catch up function basically what this<00:38:41.579> ensures<00:38:41.880> is<00:38:42.119> that<00:38:42.420> you're<00:38:42.960> getting<00:38:43.320> a 00:38:43.609 --> 00:38:43.619 align:start position:0% this ensures is that you're getting a 00:38:43.619 --> 00:38:45.950 align:start position:0% this ensures is that you're getting a good<00:38:43.800> view<00:38:44.339> of<00:38:44.579> the<00:38:44.760> market<00:38:44.880> currently<00:38:45.359> you 00:38:45.950 --> 00:38:45.960 align:start position:0% good view of the market currently you 00:38:45.960 --> 00:38:47.450 align:start position:0% good view of the market currently you haven't 00:38:47.450 --> 00:38:47.460 align:start position:0% haven't 00:38:47.460 --> 00:38:49.670 align:start position:0% haven't um<00:38:47.579> thrown<00:38:48.359> way<00:38:48.780> too<00:38:48.960> many 00:38:49.670 --> 00:38:49.680 align:start position:0% um thrown way too many 00:38:49.680 --> 00:38:52.190 align:start position:0% um thrown way too many uh<00:38:50.280> transactions<00:38:50.820> at<00:38:51.000> it<00:38:51.180> everything's<00:38:52.020> in 00:38:52.190 --> 00:38:52.200 align:start position:0% uh transactions at it everything's in 00:38:52.200 --> 00:38:53.750 align:start position:0% uh transactions at it everything's in sync<00:38:52.500> that<00:38:52.740> kind<00:38:52.859> of<00:38:52.980> thing<00:38:53.040> so<00:38:53.400> it<00:38:53.579> just 00:38:53.750 --> 00:38:53.760 align:start position:0% sync that kind of thing so it just 00:38:53.760 --> 00:38:56.450 align:start position:0% sync that kind of thing so it just ensures<00:38:54.060> that<00:38:54.740> your<00:38:55.740> more<00:38:56.099> real<00:38:56.280> world 00:38:56.450 --> 00:38:56.460 align:start position:0% ensures that your more real world 00:38:56.460 --> 00:38:58.550 align:start position:0% ensures that your more real world modeling<00:38:56.940> rather<00:38:57.599> than<00:38:57.839> trying<00:38:58.079> to<00:38:58.260> ensure 00:38:58.550 --> 00:38:58.560 align:start position:0% modeling rather than trying to ensure 00:38:58.560 --> 00:39:00.050 align:start position:0% modeling rather than trying to ensure that<00:38:58.680> you<00:38:58.800> can<00:38:58.920> get<00:38:59.040> everything<00:38:59.160> in 00:39:00.050 --> 00:39:00.060 align:start position:0% that you can get everything in 00:39:00.060 --> 00:39:02.870 align:start position:0% that you can get everything in one<00:39:00.540> nanosecond<00:39:01.140> through 00:39:02.870 --> 00:39:02.880 align:start position:0% one nanosecond through 00:39:02.880 --> 00:39:04.370 align:start position:0% one nanosecond through so 00:39:04.370 --> 00:39:04.380 align:start position:0% so 00:39:04.380 --> 00:39:05.630 align:start position:0% so um 00:39:05.630 --> 00:39:05.640 align:start position:0% um 00:39:05.640 --> 00:39:09.109 align:start position:0% um I'm<00:39:06.000> gonna<00:39:06.180> now<00:39:06.480> talk<00:39:07.079> through<00:39:07.700> building<00:39:08.700> one 00:39:09.109 --> 00:39:09.119 align:start position:0% I'm gonna now talk through building one 00:39:09.119 --> 00:39:10.910 align:start position:0% I'm gonna now talk through building one of<00:39:09.180> these<00:39:09.300> agents<00:39:09.599> a<00:39:09.780> really<00:39:09.960> simple<00:39:10.140> one<00:39:10.440> it's 00:39:10.910 --> 00:39:10.920 align:start position:0% of these agents a really simple one it's 00:39:10.920 --> 00:39:13.550 align:start position:0% of these agents a really simple one it's just<00:39:11.160> gonna<00:39:11.780> do<00:39:12.780> a<00:39:12.900> bit<00:39:13.020> of<00:39:13.079> training<00:39:13.320> I<00:39:13.440> guess 00:39:13.550 --> 00:39:13.560 align:start position:0% just gonna do a bit of training I guess 00:39:13.560 --> 00:39:15.589 align:start position:0% just gonna do a bit of training I guess and 00:39:15.589 --> 00:39:15.599 align:start position:0% and 00:39:15.599 --> 00:39:17.630 align:start position:0% and then<00:39:15.839> we'll<00:39:16.200> break<00:39:16.380> again<00:39:16.560> and<00:39:17.040> hopefully<00:39:17.520> you 00:39:17.630 --> 00:39:17.640 align:start position:0% then we'll break again and hopefully you 00:39:17.640 --> 00:39:22.609 align:start position:0% then we'll break again and hopefully you can<00:39:17.760> put<00:39:17.940> together<00:39:18.119> your<00:39:18.720> own<00:39:18.839> a<00:39:19.079> bit 00:39:22.609 --> 00:39:22.619 align:start position:0% 00:39:22.619 --> 00:39:25.010 align:start position:0% where<00:39:23.220> you're 00:39:25.010 --> 00:39:25.020 align:start position:0% where you're 00:39:25.020 --> 00:39:30.829 align:start position:0% where you're thank<00:39:25.500> you<00:39:25.740> Simmons 00:39:30.829 --> 00:39:30.839 align:start position:0% 00:39:30.839 --> 00:39:32.630 align:start position:0% Okay<00:39:31.440> so 00:39:32.630 --> 00:39:32.640 align:start position:0% Okay so 00:39:32.640 --> 00:39:34.790 align:start position:0% Okay so for<00:39:33.000> anyone<00:39:33.180> who<00:39:33.300> has<00:39:33.480> it<00:39:33.599> set<00:39:33.780> up<00:39:33.900> we've<00:39:34.680> got 00:39:34.790 --> 00:39:34.800 align:start position:0% for anyone who has it set up we've got 00:39:34.800 --> 00:39:38.150 align:start position:0% for anyone who has it set up we've got this<00:39:35.099> run<00:39:35.640> simple<00:39:35.880> agent<00:39:36.420> in 00:39:38.150 --> 00:39:38.160 align:start position:0% this run simple agent in 00:39:38.160 --> 00:39:40.970 align:start position:0% this run simple agent in exam<00:39:39.000> reinforcement<00:39:39.599> run<00:39:39.839> symbol<00:39:40.200> agent<00:39:40.500> I'll 00:39:40.970 --> 00:39:40.980 align:start position:0% exam reinforcement run symbol agent I'll 00:39:40.980 --> 00:39:43.790 align:start position:0% exam reinforcement run symbol agent I'll put<00:39:41.220> up<00:39:41.400> on<00:39:41.520> the<00:39:41.579> screen<00:39:41.700> after<00:39:41.880> this 00:39:43.790 --> 00:39:43.800 align:start position:0% put up on the screen after this 00:39:43.800 --> 00:39:45.770 align:start position:0% put up on the screen after this to<00:39:43.980> pass<00:39:44.220> to<00:39:44.400> these<00:39:44.579> files 00:39:45.770 --> 00:39:45.780 align:start position:0% to pass to these files 00:39:45.780 --> 00:39:47.810 align:start position:0% to pass to these files and<00:39:46.320> then<00:39:46.440> in<00:39:46.680> agents 00:39:47.810 --> 00:39:47.820 align:start position:0% and then in agents 00:39:47.820 --> 00:39:49.310 align:start position:0% and then in agents we<00:39:48.300> have 00:39:49.310 --> 00:39:49.320 align:start position:0% we have 00:39:49.320 --> 00:39:51.410 align:start position:0% we have our<00:39:49.619> simple<00:39:49.800> agent<00:39:50.700> so<00:39:50.880> what<00:39:51.060> run<00:39:51.240> simple 00:39:51.410 --> 00:39:51.420 align:start position:0% our simple agent so what run simple 00:39:51.420 --> 00:39:55.190 align:start position:0% our simple agent so what run simple agent<00:39:51.839> does<00:39:52.020> is<00:39:52.140> it<00:39:52.320> sets<00:39:52.619> up<00:39:52.740> a<00:39:53.280> scenario 00:39:55.190 --> 00:39:55.200 align:start position:0% agent does is it sets up a scenario 00:39:55.200 --> 00:39:56.870 align:start position:0% agent does is it sets up a scenario um I<00:39:55.380> can<00:39:55.500> discuss<00:39:55.680> the<00:39:55.859> actual<00:39:56.160> arguments 00:39:56.870 --> 00:39:56.880 align:start position:0% um I can discuss the actual arguments 00:39:56.880 --> 00:39:58.430 align:start position:0% um I can discuss the actual arguments with<00:39:57.060> people<00:39:57.240> but 00:39:58.430 --> 00:39:58.440 align:start position:0% with people but 00:39:58.440 --> 00:40:01.010 align:start position:0% with people but which<00:39:58.859> we<00:39:59.040> call<00:39:59.220> curve<00:39:59.520> Market<00:39:59.700> maker 00:40:01.010 --> 00:40:01.020 align:start position:0% which we call curve Market maker 00:40:01.020 --> 00:40:02.390 align:start position:0% which we call curve Market maker and<00:40:01.500> that 00:40:02.390 --> 00:40:02.400 align:start position:0% and that 00:40:02.400 --> 00:40:05.810 align:start position:0% and that a 00:40:05.810 --> 00:40:05.820 align:start position:0% 00:40:05.820 --> 00:40:07.250 align:start position:0% H jump<00:40:06.119> into<00:40:06.300> marketing<00:40:06.660> basically<00:40:07.079> that 00:40:07.250 --> 00:40:07.260 align:start position:0% H jump into marketing basically that 00:40:07.260 --> 00:40:10.250 align:start position:0% H jump into marketing basically that contains<00:40:07.800> an<00:40:08.460> agent<00:40:08.760> who<00:40:09.300> ensures<00:40:10.079> that 00:40:10.250 --> 00:40:10.260 align:start position:0% contains an agent who ensures that 00:40:10.260 --> 00:40:12.410 align:start position:0% contains an agent who ensures that there's<00:40:10.440> a<00:40:10.619> nice<00:40:10.740> shape<00:40:11.220> of<00:40:11.400> the<00:40:11.520> market<00:40:11.640> and<00:40:12.240> a 00:40:12.410 --> 00:40:12.420 align:start position:0% there's a nice shape of the market and a 00:40:12.420 --> 00:40:13.849 align:start position:0% there's a nice shape of the market and a few<00:40:12.540> who<00:40:12.780> just<00:40:12.960> sort<00:40:13.079> of<00:40:13.200> randomly<00:40:13.500> buy<00:40:13.740> and 00:40:13.849 --> 00:40:13.859 align:start position:0% few who just sort of randomly buy and 00:40:13.859 --> 00:40:16.730 align:start position:0% few who just sort of randomly buy and sell<00:40:14.119> so<00:40:15.119> they're<00:40:15.540> very<00:40:15.780> dumb<00:40:16.020> theoretically 00:40:16.730 --> 00:40:16.740 align:start position:0% sell so they're very dumb theoretically 00:40:16.740 --> 00:40:18.050 align:start position:0% sell so they're very dumb theoretically you<00:40:16.920> should<00:40:17.040> be<00:40:17.160> able<00:40:17.280> to 00:40:18.050 --> 00:40:18.060 align:start position:0% you should be able to 00:40:18.060 --> 00:40:20.990 align:start position:0% you should be able to agent<00:40:18.780> which<00:40:19.260> is<00:40:19.380> what<00:40:19.740> hopefully<00:40:20.579> we're 00:40:20.990 --> 00:40:21.000 align:start position:0% agent which is what hopefully we're 00:40:21.000 --> 00:40:24.470 align:start position:0% agent which is what hopefully we're going<00:40:21.180> to<00:40:21.300> build 00:40:24.470 --> 00:40:24.480 align:start position:0% 00:40:24.480 --> 00:40:26.150 align:start position:0% that<00:40:25.020> runs 00:40:26.150 --> 00:40:26.160 align:start position:0% that runs 00:40:26.160 --> 00:40:27.589 align:start position:0% that runs this<00:40:26.820> simple<00:40:27.000> agent<00:40:27.300> that<00:40:27.420> we've<00:40:27.540> got 00:40:27.589 --> 00:40:27.599 align:start position:0% this simple agent that we've got 00:40:27.599 --> 00:40:28.849 align:start position:0% this simple agent that we've got together<00:40:27.720> here<00:40:28.020> so 00:40:28.849 --> 00:40:28.859 align:start position:0% together here so 00:40:28.859 --> 00:40:32.390 align:start position:0% together here so what<00:40:29.280> I've<00:40:29.400> put<00:40:29.579> together<00:40:29.700> is<00:40:30.180> a<00:40:30.540> few 00:40:32.390 --> 00:40:32.400 align:start position:0% what I've put together is a few 00:40:32.400 --> 00:40:35.569 align:start position:0% what I've put together is a few nice<00:40:33.200> template<00:40:34.200> functions<00:40:34.800> that<00:40:35.040> is<00:40:35.339> without 00:40:35.569 --> 00:40:35.579 align:start position:0% nice template functions that is without 00:40:35.579 --> 00:40:36.890 align:start position:0% nice template functions that is without having<00:40:35.880> to<00:40:35.940> worry<00:40:36.060> too<00:40:36.240> much<00:40:36.359> about<00:40:36.480> any<00:40:36.720> of 00:40:36.890 --> 00:40:36.900 align:start position:0% having to worry too much about any of 00:40:36.900 --> 00:40:38.690 align:start position:0% having to worry too much about any of this<00:40:37.020> works<00:40:37.320> you<00:40:37.980> should<00:40:38.099> be<00:40:38.220> able<00:40:38.339> to<00:40:38.400> cut<00:40:38.579> and 00:40:38.690 --> 00:40:38.700 align:start position:0% this works you should be able to cut and 00:40:38.700 --> 00:40:42.050 align:start position:0% this works you should be able to cut and paste<00:40:39.060> these<00:40:39.359> into<00:40:40.200> our<00:40:40.680> step<00:40:40.920> function 00:40:42.050 --> 00:40:42.060 align:start position:0% paste these into our step function 00:40:42.060 --> 00:40:43.849 align:start position:0% paste these into our step function which<00:40:42.240> is<00:40:42.359> down<00:40:42.599> here 00:40:43.849 --> 00:40:43.859 align:start position:0% which is down here 00:40:43.859 --> 00:40:46.069 align:start position:0% which is down here we've<00:40:44.160> got<00:40:44.280> the<00:40:44.400> simple<00:40:44.520> agent 00:40:46.069 --> 00:40:46.079 align:start position:0% we've got the simple agent 00:40:46.079 --> 00:40:48.530 align:start position:0% we've got the simple agent and<00:40:46.380> you<00:40:46.500> can<00:40:46.619> see<00:40:46.740> it's<00:40:46.920> got<00:40:47.520> the<00:40:47.760> structure 00:40:48.530 --> 00:40:48.540 align:start position:0% and you can see it's got the structure 00:40:48.540 --> 00:40:49.609 align:start position:0% and you can see it's got the structure as<00:40:48.660> described<00:40:49.020> earlier<00:40:49.260> we've<00:40:49.380> got<00:40:49.500> our 00:40:49.609 --> 00:40:49.619 align:start position:0% as described earlier we've got our 00:40:49.619 --> 00:40:52.550 align:start position:0% as described earlier we've got our initialize<00:40:50.099> where<00:40:50.400> it's<00:40:50.579> finding<00:40:51.359> the<00:40:51.480> market 00:40:52.550 --> 00:40:52.560 align:start position:0% initialize where it's finding the market 00:40:52.560 --> 00:40:55.010 align:start position:0% initialize where it's finding the market finding<00:40:53.099> the<00:40:53.160> asset<00:40:53.940> and<00:40:54.240> minting<00:40:54.660> itself<00:40:54.839> an 00:40:55.010 --> 00:40:55.020 align:start position:0% finding the asset and minting itself an 00:40:55.020 --> 00:40:55.910 align:start position:0% finding the asset and minting itself an asset 00:40:55.910 --> 00:40:55.920 align:start position:0% asset 00:40:55.920 --> 00:40:58.550 align:start position:0% asset and<00:40:56.280> then<00:40:56.400> say 00:40:58.550 --> 00:40:58.560 align:start position:0% and then say 00:40:58.560 --> 00:41:04.250 align:start position:0% and then say submit<00:40:59.280> the<00:40:59.400> market<00:40:59.520> order 00:41:04.250 --> 00:41:04.260 align:start position:0% 00:41:04.260 --> 00:41:23.930 align:start position:0% from<00:41:04.560> that 00:41:23.930 --> 00:41:23.940 align:start position:0% 00:41:23.940 --> 00:41:55.970 align:start position:0% check<00:41:24.359> her<00:41:24.599> positions 00:41:55.970 --> 00:41:55.980 align:start position:0% 00:41:55.980 --> 00:41:57.770 align:start position:0% is<00:41:56.400> it<00:41:56.579> almost<00:41:56.700> gonna<00:41:56.940> buy 00:41:57.770 --> 00:41:57.780 align:start position:0% is it almost gonna buy 00:41:57.780 --> 00:42:00.290 align:start position:0% is it almost gonna buy it is<00:41:58.380> currently<00:41:58.619> always<00:41:58.740> going<00:41:58.920> to<00:41:58.980> buy<00:41:59.099> so 00:42:00.290 --> 00:42:00.300 align:start position:0% it is currently always going to buy so 00:42:00.300 --> 00:42:13.569 align:start position:0% it is currently always going to buy so 50<00:42:00.660> 50<00:42:00.720> chance<00:42:01.140> of<00:42:01.320> making<00:42:01.500> money 00:42:13.569 --> 00:42:13.579 align:start position:0% 00:42:13.579 --> 00:42:16.490 align:start position:0% Okay<00:42:14.579> so 00:42:16.490 --> 00:42:16.500 align:start position:0% Okay so 00:42:16.500 --> 00:42:19.550 align:start position:0% Okay so uh<00:42:17.280> they're<00:42:17.520> down<00:42:17.940> to<00:42:18.420> the<00:42:18.660> relay<00:42:18.960> just<00:42:19.380> the 00:42:19.550 --> 00:42:19.560 align:start position:0% uh they're down to the relay just the 00:42:19.560 --> 00:42:21.410 align:start position:0% uh they're down to the relay just the hardcore<00:42:19.920> Workshop<00:42:20.400> participants<00:42:21.060> you<00:42:21.359> know 00:42:21.410 --> 00:42:21.420 align:start position:0% hardcore Workshop participants you know 00:42:21.420 --> 00:42:23.290 align:start position:0% hardcore Workshop participants you know you're<00:42:21.660> the<00:42:22.079> ones<00:42:22.320> who<00:42:22.500> prevailed<00:42:22.859> with<00:42:23.040> us 00:42:23.290 --> 00:42:23.300 align:start position:0% you're the ones who prevailed with us 00:42:23.300 --> 00:42:26.150 align:start position:0% you're the ones who prevailed with us despite<00:42:24.300> Python<00:42:24.900> and<00:42:25.020> its<00:42:25.200> foibles<00:42:25.619> and<00:42:25.800> the 00:42:26.150 --> 00:42:26.160 align:start position:0% despite Python and its foibles and the 00:42:26.160 --> 00:42:27.470 align:start position:0% despite Python and its foibles and the slow<00:42:26.339> internet 00:42:27.470 --> 00:42:27.480 align:start position:0% slow internet 00:42:27.480 --> 00:42:30.829 align:start position:0% slow internet so<00:42:28.619> I'm<00:42:29.160> going<00:42:29.339> to<00:42:29.579> crack<00:42:29.760> on<00:42:30.060> if<00:42:30.480> you're<00:42:30.660> if 00:42:30.829 --> 00:42:30.839 align:start position:0% so I'm going to crack on if you're if 00:42:30.839 --> 00:42:33.890 align:start position:0% so I'm going to crack on if you're if you're<00:42:31.020> coding<00:42:31.440> keep<00:42:31.619> coding<00:42:32.160> uh<00:42:32.820> you<00:42:33.000> know<00:42:33.119> if 00:42:33.890 --> 00:42:33.900 align:start position:0% you're coding keep coding uh you know if 00:42:33.900 --> 00:42:35.870 align:start position:0% you're coding keep coding uh you know if you<00:42:33.960> have<00:42:34.140> questions<00:42:34.380> there<00:42:35.040> will<00:42:35.339> be<00:42:35.460> time<00:42:35.640> to 00:42:35.870 --> 00:42:35.880 align:start position:0% you have questions there will be time to 00:42:35.880 --> 00:42:38.390 align:start position:0% you have questions there will be time to ask<00:42:36.060> questions<00:42:36.359> and<00:42:37.320> what<00:42:37.500> we<00:42:37.680> went<00:42:37.859> to<00:42:38.040> what 00:42:38.390 --> 00:42:38.400 align:start position:0% ask questions and what we went to what 00:42:38.400 --> 00:42:40.490 align:start position:0% ask questions and what we went to what we<00:42:38.579> want<00:42:38.700> to<00:42:38.880> get<00:42:39.000> to<00:42:39.180> now<00:42:39.480> is 00:42:40.490 --> 00:42:40.500 align:start position:0% we want to get to now is 00:42:40.500 --> 00:42:42.050 align:start position:0% we want to get to now is just<00:42:40.800> to<00:42:41.040> show<00:42:41.160> you<00:42:41.339> a<00:42:41.460> little<00:42:41.579> bit<00:42:41.700> more<00:42:41.880> of 00:42:42.050 --> 00:42:42.060 align:start position:0% just to show you a little bit more of 00:42:42.060 --> 00:42:43.670 align:start position:0% just to show you a little bit more of you<00:42:42.359> know<00:42:42.420> what<00:42:42.540> the<00:42:42.780> agents<00:42:43.140> that<00:42:43.320> that<00:42:43.500> you 00:42:43.670 --> 00:42:43.680 align:start position:0% you know what the agents that that you 00:42:43.680 --> 00:42:45.410 align:start position:0% you know what the agents that that you have<00:42:43.859> there<00:42:44.040> you<00:42:44.339> know<00:42:44.400> the<00:42:44.579> market<00:42:44.700> maker<00:42:45.300> Etc 00:42:45.410 --> 00:42:45.420 align:start position:0% have there you know the market maker Etc 00:42:45.420 --> 00:42:47.510 align:start position:0% have there you know the market maker Etc that<00:42:45.720> you're<00:42:45.900> interacting<00:42:46.320> with<00:42:46.440> a<00:42:47.339> little 00:42:47.510 --> 00:42:47.520 align:start position:0% that you're interacting with a little 00:42:47.520 --> 00:42:49.010 align:start position:0% that you're interacting with a little bit<00:42:47.640> the<00:42:47.820> ideas<00:42:48.000> that<00:42:48.300> they're<00:42:48.420> based<00:42:48.780> on<00:42:48.839> and 00:42:49.010 --> 00:42:49.020 align:start position:0% bit the ideas that they're based on and 00:42:49.020 --> 00:42:51.710 align:start position:0% bit the ideas that they're based on and then<00:42:49.320> move<00:42:49.619> on<00:42:49.800> to<00:42:50.160> the<00:42:50.720> reinforcement 00:42:51.710 --> 00:42:51.720 align:start position:0% then move on to the reinforcement 00:42:51.720 --> 00:42:56.510 align:start position:0% then move on to the reinforcement learning<00:42:52.200> part<00:42:52.440> so 00:42:56.510 --> 00:42:56.520 align:start position:0% 00:42:56.520 --> 00:42:58.609 align:start position:0% you<00:42:57.000> know<00:42:57.060> as<00:42:57.240> part<00:42:57.599> of<00:42:57.720> the<00:42:57.900> environment<00:42:58.319> as 00:42:58.609 --> 00:42:58.619 align:start position:0% you know as part of the environment as 00:42:58.619 --> 00:43:00.470 align:start position:0% you know as part of the environment as Tom<00:42:59.040> was<00:42:59.220> saying<00:42:59.460> if<00:42:59.579> you<00:42:59.940> just<00:43:00.060> set<00:43:00.240> it<00:43:00.359> up 00:43:00.470 --> 00:43:00.480 align:start position:0% Tom was saying if you just set it up 00:43:00.480 --> 00:43:02.390 align:start position:0% Tom was saying if you just set it up there<00:43:00.660> is<00:43:00.780> nothing<00:43:00.900> it's<00:43:01.200> it's<00:43:01.319> the<00:43:01.920> empty 00:43:02.390 --> 00:43:02.400 align:start position:0% there is nothing it's it's the empty 00:43:02.400 --> 00:43:04.430 align:start position:0% there is nothing it's it's the empty Vega<00:43:02.819> blockchain<00:43:03.240> as<00:43:03.540> it<00:43:03.780> would<00:43:03.900> as<00:43:04.079> it<00:43:04.260> would 00:43:04.430 --> 00:43:04.440 align:start position:0% Vega blockchain as it would as it would 00:43:04.440 --> 00:43:06.770 align:start position:0% Vega blockchain as it would as it would be<00:43:04.619> when<00:43:05.280> it<00:43:05.460> launches<00:43:05.819> live<00:43:06.060> you<00:43:06.420> know<00:43:06.540> no 00:43:06.770 --> 00:43:06.780 align:start position:0% be when it launches live you know no 00:43:06.780 --> 00:43:09.290 align:start position:0% be when it launches live you know no assets<00:43:07.200> no<00:43:07.500> markets<00:43:08.099> everything<00:43:08.700> has<00:43:09.060> to<00:43:09.180> be 00:43:09.290 --> 00:43:09.300 align:start position:0% assets no markets everything has to be 00:43:09.300 --> 00:43:10.970 align:start position:0% assets no markets everything has to be created<00:43:09.599> through<00:43:09.839> governance 00:43:10.970 --> 00:43:10.980 align:start position:0% created through governance 00:43:10.980 --> 00:43:13.250 align:start position:0% created through governance and<00:43:11.760> you<00:43:12.000> know<00:43:12.119> once<00:43:12.420> the<00:43:12.540> asset<00:43:12.780> is<00:43:12.960> created 00:43:13.250 --> 00:43:13.260 align:start position:0% and you know once the asset is created 00:43:13.260 --> 00:43:15.109 align:start position:0% and you know once the asset is created once<00:43:13.680> the<00:43:13.800> market<00:43:13.920> is<00:43:14.220> voted<00:43:14.579> through<00:43:14.760> which 00:43:15.109 --> 00:43:15.119 align:start position:0% once the market is voted through which 00:43:15.119 --> 00:43:17.270 align:start position:0% once the market is voted through which you<00:43:15.300> know<00:43:15.420> the<00:43:15.599> python<00:43:16.200> sort<00:43:16.440> of<00:43:16.500> expedites 00:43:17.270 --> 00:43:17.280 align:start position:0% you know the python sort of expedites 00:43:17.280 --> 00:43:19.190 align:start position:0% you know the python sort of expedites for<00:43:17.460> you<00:43:17.640> you<00:43:18.359> will<00:43:18.540> still<00:43:18.720> have<00:43:18.839> just<00:43:19.020> an 00:43:19.190 --> 00:43:19.200 align:start position:0% for you you will still have just an 00:43:19.200 --> 00:43:20.990 align:start position:0% for you you will still have just an empty<00:43:19.440> market<00:43:19.680> right<00:43:19.920> no<00:43:20.160> liquidity<00:43:20.640> on<00:43:20.880> it 00:43:20.990 --> 00:43:21.000 align:start position:0% empty market right no liquidity on it 00:43:21.000 --> 00:43:22.849 align:start position:0% empty market right no liquidity on it nothing<00:43:21.180> no<00:43:21.599> activity 00:43:22.849 --> 00:43:22.859 align:start position:0% nothing no activity 00:43:22.859 --> 00:43:24.069 align:start position:0% nothing no activity so 00:43:24.069 --> 00:43:24.079 align:start position:0% so 00:43:24.079 --> 00:43:27.770 align:start position:0% so effectively<00:43:25.079> the<00:43:25.619> code<00:43:25.800> provides<00:43:26.780> various 00:43:27.770 --> 00:43:27.780 align:start position:0% effectively the code provides various 00:43:27.780 --> 00:43:30.470 align:start position:0% effectively the code provides various versions<00:43:28.560> of<00:43:28.800> of<00:43:29.040> market<00:43:29.339> makers<00:43:29.880> that<00:43:30.060> are 00:43:30.470 --> 00:43:30.480 align:start position:0% versions of of market makers that are 00:43:30.480 --> 00:43:32.030 align:start position:0% versions of of market makers that are based<00:43:30.900> on<00:43:31.020> some<00:43:31.319> stochastic<00:43:31.740> control 00:43:32.030 --> 00:43:32.040 align:start position:0% based on some stochastic control 00:43:32.040 --> 00:43:34.130 align:start position:0% based on some stochastic control problems<00:43:32.579> that<00:43:32.819> are<00:43:33.000> pre-solved<00:43:33.540> coded<00:43:33.960> up 00:43:34.130 --> 00:43:34.140 align:start position:0% problems that are pre-solved coded up 00:43:34.140 --> 00:43:36.650 align:start position:0% problems that are pre-solved coded up and<00:43:34.920> basically<00:43:35.339> running<00:43:35.579> and<00:43:35.940> then<00:43:36.240> some<00:43:36.480> sort 00:43:36.650 --> 00:43:36.660 align:start position:0% and basically running and then some sort 00:43:36.660 --> 00:43:38.930 align:start position:0% and basically running and then some sort of<00:43:36.780> hacks<00:43:37.260> where<00:43:37.500> you<00:43:37.800> know<00:43:37.920> the<00:43:38.520> optimal 00:43:38.930 --> 00:43:38.940 align:start position:0% of hacks where you know the optimal 00:43:38.940 --> 00:43:40.430 align:start position:0% of hacks where you know the optimal solution<00:43:39.359> of<00:43:39.599> the<00:43:39.780> stochastic<00:43:40.140> control 00:43:40.430 --> 00:43:40.440 align:start position:0% solution of the stochastic control 00:43:40.440 --> 00:43:42.470 align:start position:0% solution of the stochastic control problem<00:43:40.740> is<00:43:41.040> used<00:43:41.220> as<00:43:41.400> a<00:43:41.579> heuristic<00:43:42.119> and<00:43:42.300> then 00:43:42.470 --> 00:43:42.480 align:start position:0% problem is used as a heuristic and then 00:43:42.480 --> 00:43:44.390 align:start position:0% problem is used as a heuristic and then you<00:43:42.599> put<00:43:42.780> something<00:43:42.960> on<00:43:43.200> top<00:43:43.380> of<00:43:43.560> that 00:43:44.390 --> 00:43:44.400 align:start position:0% you put something on top of that 00:43:44.400 --> 00:43:47.150 align:start position:0% you put something on top of that and<00:43:45.180> you<00:43:45.420> know<00:43:45.540> there<00:43:46.380> are<00:43:46.500> you<00:43:46.800> can<00:43:46.920> you<00:43:47.099> can 00:43:47.150 --> 00:43:47.160 align:start position:0% and you know there are you can you can 00:43:47.160 --> 00:43:48.650 align:start position:0% and you know there are you can you can have<00:43:47.280> liquidity<00:43:47.760> Trader<00:43:48.300> you<00:43:48.480> can<00:43:48.599> have 00:43:48.650 --> 00:43:48.660 align:start position:0% have liquidity Trader you can have 00:43:48.660 --> 00:43:50.270 align:start position:0% have liquidity Trader you can have liquidity<00:43:49.200> takers<00:43:49.619> it<00:43:49.800> just<00:43:49.920> means<00:43:50.160> they 00:43:50.270 --> 00:43:50.280 align:start position:0% liquidity takers it just means they 00:43:50.280 --> 00:43:53.030 align:start position:0% liquidity takers it just means they Place<00:43:50.460> random<00:43:51.000> Market<00:43:51.240> buy<00:43:51.599> and<00:43:51.780> sell<00:43:51.900> orders 00:43:53.030 --> 00:43:53.040 align:start position:0% Place random Market buy and sell orders 00:43:53.040 --> 00:43:55.849 align:start position:0% Place random Market buy and sell orders you<00:43:53.640> can<00:43:53.760> have<00:43:54.000> informed<00:43:54.720> Traders<00:43:55.200> what<00:43:55.680> does 00:43:55.849 --> 00:43:55.859 align:start position:0% you can have informed Traders what does 00:43:55.859 --> 00:43:57.829 align:start position:0% you can have informed Traders what does it<00:43:56.040> mean<00:43:56.280> well<00:43:56.819> you<00:43:57.060> just<00:43:57.240> tell<00:43:57.359> them<00:43:57.480> what<00:43:57.660> the 00:43:57.829 --> 00:43:57.839 align:start position:0% it mean well you just tell them what the 00:43:57.839 --> 00:43:59.690 align:start position:0% it mean well you just tell them what the price<00:43:57.960> will<00:43:58.200> be<00:43:58.319> at<00:43:58.500> the<00:43:58.619> next<00:43:58.800> step<00:43:59.040> right<00:43:59.400> you 00:43:59.690 --> 00:43:59.700 align:start position:0% price will be at the next step right you 00:43:59.700 --> 00:44:01.010 align:start position:0% price will be at the next step right you know<00:43:59.819> maybe<00:44:00.060> they<00:44:00.359> they<00:44:00.420> have<00:44:00.839> inside 00:44:01.010 --> 00:44:01.020 align:start position:0% know maybe they they have inside 00:44:01.020 --> 00:44:03.670 align:start position:0% know maybe they they have inside information<00:44:01.640> or<00:44:02.640> whatever 00:44:03.670 --> 00:44:03.680 align:start position:0% information or whatever 00:44:03.680 --> 00:44:05.750 align:start position:0% information or whatever and<00:44:05.099> um 00:44:05.750 --> 00:44:05.760 align:start position:0% and um 00:44:05.760 --> 00:44:07.790 align:start position:0% and um there<00:44:06.240> are<00:44:06.359> the<00:44:06.540> momentum<00:44:06.900> Traders<00:44:07.380> through<00:44:07.619> a 00:44:07.790 --> 00:44:07.800 align:start position:0% there are the momentum Traders through a 00:44:07.800 --> 00:44:11.930 align:start position:0% there are the momentum Traders through a library<00:44:08.000> so<00:44:09.000> you<00:44:09.119> you<00:44:09.300> can<00:44:09.980> uh<00:44:10.980> you<00:44:11.520> can<00:44:11.640> trade 00:44:11.930 --> 00:44:11.940 align:start position:0% library so you you can uh you can trade 00:44:11.940 --> 00:44:13.730 align:start position:0% library so you you can uh you can trade on<00:44:12.240> on<00:44:12.420> all<00:44:12.660> the<00:44:12.780> patterns<00:44:13.200> that<00:44:13.500> these 00:44:13.730 --> 00:44:13.740 align:start position:0% on on all the patterns that these 00:44:13.740 --> 00:44:15.230 align:start position:0% on on all the patterns that these chartist<00:44:14.160> people<00:44:14.400> have<00:44:14.640> you<00:44:14.819> know<00:44:14.940> there<00:44:15.119> are 00:44:15.230 --> 00:44:15.240 align:start position:0% chartist people have you know there are 00:44:15.240 --> 00:44:17.270 align:start position:0% chartist people have you know there are these<00:44:15.420> vomiting<00:44:15.780> camels<00:44:16.260> and<00:44:16.619> I<00:44:16.980> don't<00:44:17.160> know 00:44:17.270 --> 00:44:17.280 align:start position:0% these vomiting camels and I don't know 00:44:17.280 --> 00:44:19.790 align:start position:0% these vomiting camels and I don't know what<00:44:17.520> else<00:44:17.640> you<00:44:18.540> know<00:44:18.660> you<00:44:18.900> you<00:44:19.140> can<00:44:19.319> code<00:44:19.560> up 00:44:19.790 --> 00:44:19.800 align:start position:0% what else you know you you can code up 00:44:19.800 --> 00:44:22.940 align:start position:0% what else you know you you can code up agents<00:44:20.220> that<00:44:20.339> trade<00:44:20.579> on<00:44:20.760> that