WEBVTT Kind: captions Language: en 00:00:14.259 --> 00:00:17.650 align:start position:0% good<00:00:15.259> morning<00:00:15.679> everyone<00:00:15.950> my<00:00:16.580> name<00:00:17.330> is<00:00:17.360> Steve 00:00:17.650 --> 00:00:17.660 align:start position:0% good morning everyone my name is Steve 00:00:17.660 --> 00:00:21.070 align:start position:0% good morning everyone my name is Steve Scheffer<00:00:18.110> I'm<00:00:18.710> an<00:00:18.860> engineer<00:00:19.250> at<00:00:20.240> provenance 00:00:21.070 --> 00:00:21.080 align:start position:0% Scheffer I'm an engineer at provenance 00:00:21.080 --> 00:00:23.980 align:start position:0% Scheffer I'm an engineer at provenance we're<00:00:21.770> software<00:00:22.400> company<00:00:22.790> maybe<00:00:23.480> some<00:00:23.720> of<00:00:23.840> you 00:00:23.980 --> 00:00:23.990 align:start position:0% we're software company maybe some of you 00:00:23.990 --> 00:00:26.680 align:start position:0% we're software company maybe some of you heard<00:00:24.680> of<00:00:24.830> us<00:00:24.950> already<00:00:25.100> or<00:00:25.940> a<00:00:26.000> base<00:00:26.180> in<00:00:26.360> London 00:00:26.680 --> 00:00:26.690 align:start position:0% heard of us already or a base in London 00:00:26.690 --> 00:00:31.860 align:start position:0% heard of us already or a base in London in<00:00:26.810> the<00:00:26.870> UK<00:00:26.960> and<00:00:29.830> basically<00:00:30.830> just<00:00:31.070> summing<00:00:31.520> up 00:00:31.860 --> 00:00:31.870 align:start position:0% in the UK and basically just summing up 00:00:31.870 --> 00:00:34.330 align:start position:0% in the UK and basically just summing up the<00:00:32.870> kind<00:00:33.110> of<00:00:33.140> division<00:00:33.440> behind<00:00:33.770> provenance 00:00:34.330 --> 00:00:34.340 align:start position:0% the kind of division behind provenance 00:00:34.340 --> 00:00:37.360 align:start position:0% the kind of division behind provenance is<00:00:34.490> that<00:00:34.780> every<00:00:35.780> great<00:00:36.170> product<00:00:36.680> should<00:00:37.130> come 00:00:37.360 --> 00:00:37.370 align:start position:0% is that every great product should come 00:00:37.370 --> 00:00:40.530 align:start position:0% is that every great product should come with<00:00:37.579> provenance<00:00:38.030> and<00:00:38.270> what<00:00:38.690> that<00:00:38.840> means<00:00:39.079> is 00:00:40.530 --> 00:00:40.540 align:start position:0% with provenance and what that means is 00:00:40.540 --> 00:00:43.600 align:start position:0% with provenance and what that means is towards<00:00:41.540> trustworthy<00:00:42.380> information<00:00:42.829> and 00:00:43.600 --> 00:00:43.610 align:start position:0% towards trustworthy information and 00:00:43.610 --> 00:00:46.120 align:start position:0% towards trustworthy information and accessible<00:00:44.120> information<00:00:44.530> about<00:00:45.530> the<00:00:45.620> origin 00:00:46.120 --> 00:00:46.130 align:start position:0% accessible information about the origin 00:00:46.130 --> 00:00:48.010 align:start position:0% accessible information about the origin and<00:00:46.370> the<00:00:46.579> journey<00:00:46.850> and<00:00:47.180> the<00:00:47.270> impact<00:00:47.660> of<00:00:47.810> that 00:00:48.010 --> 00:00:48.020 align:start position:0% and the journey and the impact of that 00:00:48.020 --> 00:00:52.810 align:start position:0% and the journey and the impact of that product<00:00:49.010> and<00:00:51.190> basically<00:00:52.190> the<00:00:52.310> way<00:00:52.460> that<00:00:52.489> we 00:00:52.810 --> 00:00:52.820 align:start position:0% product and basically the way that we 00:00:52.820 --> 00:00:54.880 align:start position:0% product and basically the way that we deliver<00:00:53.000> on<00:00:53.450> this<00:00:53.630> vision<00:00:53.840> is<00:00:54.170> that<00:00:54.739> we 00:00:54.880 --> 00:00:54.890 align:start position:0% deliver on this vision is that we 00:00:54.890 --> 00:00:57.430 align:start position:0% deliver on this vision is that we provide<00:00:55.160> a<00:00:55.579> platform<00:00:55.850> for<00:00:56.420> businesses<00:00:56.899> to<00:00:57.230> be 00:00:57.430 --> 00:00:57.440 align:start position:0% provide a platform for businesses to be 00:00:57.440 --> 00:01:00.370 align:start position:0% provide a platform for businesses to be more<00:00:57.470> transparent<00:00:58.220> and<00:00:58.399> share<00:00:58.460> data<00:00:59.450> across 00:01:00.370 --> 00:01:00.380 align:start position:0% more transparent and share data across 00:01:00.380 --> 00:01:03.520 align:start position:0% more transparent and share data across the<00:01:00.530> supply<00:01:00.829> chain<00:01:01.040> and<00:01:01.610> as<00:01:01.880> well<00:01:02.090> as<00:01:02.530> with 00:01:03.520 --> 00:01:03.530 align:start position:0% the supply chain and as well as with 00:01:03.530 --> 00:01:08.770 align:start position:0% the supply chain and as well as with consumers<00:01:05.020> so<00:01:06.020> that's<00:01:06.229> both<00:01:07.270> an<00:01:08.270> access<00:01:08.659> for 00:01:08.770 --> 00:01:08.780 align:start position:0% consumers so that's both an access for 00:01:08.780 --> 00:01:12.100 align:start position:0% consumers so that's both an access for businesses<00:01:09.200> to<00:01:09.350> share<00:01:09.530> it<00:01:09.680> also<00:01:10.720> a<00:01:11.720> consumer 00:01:12.100 --> 00:01:12.110 align:start position:0% businesses to share it also a consumer 00:01:12.110 --> 00:01:15.760 align:start position:0% businesses to share it also a consumer app<00:01:12.380> that<00:01:13.780> consumer<00:01:14.780> can<00:01:14.960> access<00:01:15.350> to<00:01:15.380> learn 00:01:15.760 --> 00:01:15.770 align:start position:0% app that consumer can access to learn 00:01:15.770 --> 00:01:17.620 align:start position:0% app that consumer can access to learn more<00:01:16.010> about<00:01:16.250> the<00:01:16.970> supply<00:01:17.270> chain<00:01:17.450> and<00:01:17.540> the 00:01:17.620 --> 00:01:17.630 align:start position:0% more about the supply chain and the 00:01:17.630 --> 00:01:22.230 align:start position:0% more about the supply chain and the great<00:01:17.840> products<00:01:18.350> that<00:01:18.380> are<00:01:18.590> being<00:01:18.979> made<00:01:20.680> so 00:01:22.230 --> 00:01:22.240 align:start position:0% great products that are being made so 00:01:22.240 --> 00:01:26.230 align:start position:0% great products that are being made so one<00:01:23.240> aspect<00:01:23.659> of<00:01:24.020> this<00:01:24.260> platform<00:01:24.970> has<00:01:25.970> to<00:01:26.119> do 00:01:26.230 --> 00:01:26.240 align:start position:0% one aspect of this platform has to do 00:01:26.240 --> 00:01:27.969 align:start position:0% one aspect of this platform has to do with<00:01:26.390> storytelling<00:01:26.780> because<00:01:27.619> we<00:01:27.740> believe 00:01:27.969 --> 00:01:27.979 align:start position:0% with storytelling because we believe 00:01:27.979 --> 00:01:31.450 align:start position:0% with storytelling because we believe that<00:01:28.540> just<00:01:29.540> disclosing<00:01:30.500> how<00:01:30.950> you<00:01:31.010> make<00:01:31.310> your 00:01:31.450 --> 00:01:31.460 align:start position:0% that just disclosing how you make your 00:01:31.460 --> 00:01:33.370 align:start position:0% that just disclosing how you make your products<00:01:32.000> and<00:01:32.150> and<00:01:32.540> the<00:01:32.630> craft<00:01:32.900> that's<00:01:33.140> put 00:01:33.370 --> 00:01:33.380 align:start position:0% products and and the craft that's put 00:01:33.380 --> 00:01:37.090 align:start position:0% products and and the craft that's put into<00:01:33.740> them<00:01:33.890> is<00:01:34.130> already<00:01:34.970> a<00:01:35.380> good<00:01:36.380> going<00:01:36.979> the 00:01:37.090 --> 00:01:37.100 align:start position:0% into them is already a good going the 00:01:37.100 --> 00:01:38.850 align:start position:0% into them is already a good going the right<00:01:37.220> direction<00:01:37.280> in<00:01:37.850> terms<00:01:37.880> of<00:01:38.150> transparency 00:01:38.850 --> 00:01:38.860 align:start position:0% right direction in terms of transparency 00:01:38.860 --> 00:01:41.640 align:start position:0% right direction in terms of transparency but<00:01:39.860> obviously<00:01:40.220> what<00:01:40.400> I'm<00:01:40.490> going<00:01:40.700> to<00:01:40.729> be 00:01:41.640 --> 00:01:41.650 align:start position:0% but obviously what I'm going to be 00:01:41.650 --> 00:01:45.539 align:start position:0% but obviously what I'm going to be presenting<00:01:42.650> today<00:01:42.799> is<00:01:43.220> more<00:01:43.790> of<00:01:43.909> a<00:01:44.060> verifiable 00:01:45.539 --> 00:01:45.549 align:start position:0% presenting today is more of a verifiable 00:01:45.549 --> 00:01:48.210 align:start position:0% presenting today is more of a verifiable aspects<00:01:46.549> of<00:01:46.729> what<00:01:46.970> we<00:01:47.180> what<00:01:47.659> the<00:01:47.780> platform 00:01:48.210 --> 00:01:48.220 align:start position:0% aspects of what we what the platform 00:01:48.220 --> 00:01:57.700 align:start position:0% aspects of what we what the platform allows<00:01:52.960> so<00:01:53.960> we<00:01:55.090> almost<00:01:56.090> everything<00:01:56.720> we<00:01:56.840> do<00:01:57.020> at 00:01:57.700 --> 00:01:57.710 align:start position:0% allows so we almost everything we do at 00:01:57.710 --> 00:02:00.580 align:start position:0% allows so we almost everything we do at provenance<00:01:58.460> around<00:01:59.119> that<00:01:59.299> is<00:01:59.570> linked<00:02:00.350> to<00:02:00.470> the 00:02:00.580 --> 00:02:00.590 align:start position:0% provenance around that is linked to the 00:02:00.590 --> 00:02:02.850 align:start position:0% provenance around that is linked to the country<00:02:00.950> the<00:02:01.070> concept<00:02:01.460> a<00:02:01.549> verifiable<00:02:01.970> claim 00:02:02.850 --> 00:02:02.860 align:start position:0% country the concept a verifiable claim 00:02:02.860 --> 00:02:05.499 align:start position:0% country the concept a verifiable claim so<00:02:03.860> I'm<00:02:03.950> sure<00:02:04.189> many<00:02:04.460> of<00:02:04.850> you<00:02:05.030> are<00:02:05.150> familiar 00:02:05.499 --> 00:02:05.509 align:start position:0% so I'm sure many of you are familiar 00:02:05.509 --> 00:02:07.860 align:start position:0% so I'm sure many of you are familiar with<00:02:05.900> the 00:02:07.860 --> 00:02:07.870 align:start position:0% with the 00:02:07.870 --> 00:02:11.160 align:start position:0% with the the<00:02:08.200> concept<00:02:08.619> of<00:02:08.679> an<00:02:08.830> identity<00:02:09.250> framework<00:02:10.170> so 00:02:11.160 --> 00:02:11.170 align:start position:0% the concept of an identity framework so 00:02:11.170 --> 00:02:12.600 align:start position:0% the concept of an identity framework so there's<00:02:11.380> been<00:02:11.530> a<00:02:11.590> few<00:02:11.740> presentation<00:02:12.340> at<00:02:12.459> Def 00:02:12.600 --> 00:02:12.610 align:start position:0% there's been a few presentation at Def 00:02:12.610 --> 00:02:14.520 align:start position:0% there's been a few presentation at Def Con<00:02:12.640> already<00:02:13.030> on<00:02:13.209> that<00:02:13.450> and<00:02:13.720> there<00:02:14.260> are<00:02:14.290> many 00:02:14.520 --> 00:02:14.530 align:start position:0% Con already on that and there are many 00:02:14.530 --> 00:02:17.360 align:start position:0% Con already on that and there are many initiatives<00:02:14.740> going<00:02:15.220> on<00:02:15.459> the<00:02:16.000> concept<00:02:16.780> that 00:02:17.360 --> 00:02:17.370 align:start position:0% initiatives going on the concept that 00:02:17.370 --> 00:02:21.420 align:start position:0% initiatives going on the concept that individuals<00:02:18.370> could<00:02:18.730> control<00:02:19.920> their<00:02:20.920> identity 00:02:21.420 --> 00:02:21.430 align:start position:0% individuals could control their identity 00:02:21.430 --> 00:02:23.760 align:start position:0% individuals could control their identity and<00:02:21.610> once<00:02:22.450> they<00:02:22.569> control<00:02:22.900> the<00:02:22.990> identity<00:02:23.500> make 00:02:23.760 --> 00:02:23.770 align:start position:0% and once they control the identity make 00:02:23.770 --> 00:02:26.220 align:start position:0% and once they control the identity make claims<00:02:24.130> about<00:02:24.400> themselves<00:02:24.970> and<00:02:25.300> then<00:02:25.989> have 00:02:26.220 --> 00:02:26.230 align:start position:0% claims about themselves and then have 00:02:26.230 --> 00:02:29.040 align:start position:0% claims about themselves and then have those<00:02:26.410> claims<00:02:26.739> being<00:02:27.640> verified<00:02:27.910> by<00:02:28.480> third 00:02:29.040 --> 00:02:29.050 align:start position:0% those claims being verified by third 00:02:29.050 --> 00:02:30.720 align:start position:0% those claims being verified by third parties<00:02:29.470> or<00:02:29.650> different<00:02:30.010> verification 00:02:30.720 --> 00:02:30.730 align:start position:0% parties or different verification 00:02:30.730 --> 00:02:33.360 align:start position:0% parties or different verification methods<00:02:31.120> so<00:02:31.690> for<00:02:31.840> example<00:02:32.260> you<00:02:32.380> could<00:02:32.560> want<00:02:33.160> to 00:02:33.360 --> 00:02:33.370 align:start position:0% methods so for example you could want to 00:02:33.370 --> 00:02:36.479 align:start position:0% methods so for example you could want to prove<00:02:34.150> that<00:02:34.180> you<00:02:34.690> are<00:02:34.720> over<00:02:35.680> a<00:02:35.709> certain<00:02:35.920> age<00:02:36.220> to 00:02:36.479 --> 00:02:36.489 align:start position:0% prove that you are over a certain age to 00:02:36.489 --> 00:02:39.270 align:start position:0% prove that you are over a certain age to access<00:02:36.760> a<00:02:36.790> particular<00:02:37.300> service<00:02:37.690> and<00:02:38.010> then<00:02:39.010> you 00:02:39.270 --> 00:02:39.280 align:start position:0% access a particular service and then you 00:02:39.280 --> 00:02:41.670 align:start position:0% access a particular service and then you can<00:02:39.459> have<00:02:39.610> that<00:02:39.880> verified<00:02:40.570> by<00:02:40.840> let's<00:02:41.500> say<00:02:41.650> a 00:02:41.670 --> 00:02:41.680 align:start position:0% can have that verified by let's say a 00:02:41.680 --> 00:02:45.600 align:start position:0% can have that verified by let's say a bank<00:02:41.980> or<00:02:42.250> or<00:02:42.670> a<00:02:43.000> peer-to-peer<00:02:44.610> verification 00:02:45.600 --> 00:02:45.610 align:start position:0% bank or or a peer-to-peer verification 00:02:45.610 --> 00:02:48.960 align:start position:0% bank or or a peer-to-peer verification method<00:02:46.170> the<00:02:47.170> important<00:02:47.590> point<00:02:48.040> here<00:02:48.130> is<00:02:48.640> that 00:02:48.960 --> 00:02:48.970 align:start position:0% method the important point here is that 00:02:48.970 --> 00:02:51.330 align:start position:0% method the important point here is that a<00:02:49.630> claim<00:02:50.140> and<00:02:50.350> a<00:02:50.470> verification<00:02:51.070> are<00:02:51.190> two 00:02:51.330 --> 00:02:51.340 align:start position:0% a claim and a verification are two 00:02:51.340 --> 00:02:55.380 align:start position:0% a claim and a verification are two different<00:02:51.670> things<00:02:51.730> and<00:02:52.180> that<00:02:53.970> and<00:02:54.970> what<00:02:55.120> we<00:02:55.269> do 00:02:55.380 --> 00:02:55.390 align:start position:0% different things and that and what we do 00:02:55.390 --> 00:02:58.440 align:start position:0% different things and that and what we do try<00:02:55.750> to<00:02:55.780> keep<00:02:56.140> the<00:02:56.970> verification<00:02:57.970> method<00:02:58.269> as 00:02:58.440 --> 00:02:58.450 align:start position:0% try to keep the verification method as 00:02:58.450 --> 00:03:01.470 align:start position:0% try to keep the verification method as generic<00:02:58.930> as<00:02:59.170> possible<00:02:59.200> so<00:02:59.769> that<00:02:59.880> people<00:03:00.880> can 00:03:01.470 --> 00:03:01.480 align:start position:0% generic as possible so that people can 00:03:01.480 --> 00:03:04.740 align:start position:0% generic as possible so that people can integrate<00:03:01.780> their<00:03:02.080> own<00:03:02.310> verification<00:03:03.750> methods 00:03:04.740 --> 00:03:04.750 align:start position:0% integrate their own verification methods 00:03:04.750 --> 00:03:07.920 align:start position:0% integrate their own verification methods with<00:03:04.959> the<00:03:05.140> system<00:03:06.060> and<00:03:07.060> as<00:03:07.209> you<00:03:07.390> can<00:03:07.540> see<00:03:07.750> what 00:03:07.920 --> 00:03:07.930 align:start position:0% with the system and as you can see what 00:03:07.930 --> 00:03:09.840 align:start position:0% with the system and as you can see what we<00:03:08.110> are<00:03:08.140> trying<00:03:08.739> to<00:03:08.890> do<00:03:09.190> is<00:03:09.370> taking<00:03:09.760> this 00:03:09.840 --> 00:03:09.850 align:start position:0% we are trying to do is taking this 00:03:09.850 --> 00:03:12.539 align:start position:0% we are trying to do is taking this concept<00:03:10.120> of<00:03:10.569> verifiable<00:03:11.110> claims<00:03:11.560> on 00:03:12.539 --> 00:03:12.549 align:start position:0% concept of verifiable claims on 00:03:12.549 --> 00:03:15.449 align:start position:0% concept of verifiable claims on individuals<00:03:13.269> and<00:03:13.480> bring<00:03:13.870> that<00:03:14.110> to<00:03:14.530> the<00:03:15.130> supply 00:03:15.449 --> 00:03:15.459 align:start position:0% individuals and bring that to the supply 00:03:15.459 --> 00:03:18.870 align:start position:0% individuals and bring that to the supply chain<00:03:15.730> I<00:03:15.970> means<00:03:16.480> two<00:03:16.810> businesses<00:03:17.530> and<00:03:17.880> there 00:03:18.870 --> 00:03:18.880 align:start position:0% chain I means two businesses and there 00:03:18.880 --> 00:03:20.940 align:start position:0% chain I means two businesses and there are<00:03:18.970> products 00:03:20.940 --> 00:03:20.950 align:start position:0% are products 00:03:20.950 --> 00:03:23.580 align:start position:0% are products so<00:03:21.519> first<00:03:22.090> let's<00:03:22.540> let's<00:03:22.840> look<00:03:22.989> at<00:03:23.110> businesses 00:03:23.580 --> 00:03:23.590 align:start position:0% so first let's let's look at businesses 00:03:23.590 --> 00:03:25.620 align:start position:0% so first let's let's look at businesses what<00:03:23.890> what<00:03:24.190> type<00:03:24.400> of<00:03:24.549> claims<00:03:24.820> could<00:03:25.570> a 00:03:25.620 --> 00:03:25.630 align:start position:0% what what type of claims could a 00:03:25.630 --> 00:03:29.850 align:start position:0% what what type of claims could a business<00:03:26.049> a<00:03:26.230> business<00:03:27.120> make<00:03:28.120> so<00:03:29.110> one<00:03:29.290> example 00:03:29.850 --> 00:03:29.860 align:start position:0% business a business make so one example 00:03:29.860 --> 00:03:31.080 align:start position:0% business a business make so one example that<00:03:30.010> you<00:03:30.220> could<00:03:30.370> have<00:03:30.519> is<00:03:30.700> that<00:03:30.850> as<00:03:31.060> a 00:03:31.080 --> 00:03:31.090 align:start position:0% that you could have is that as a 00:03:31.090 --> 00:03:33.990 align:start position:0% that you could have is that as a business<00:03:31.480> you<00:03:31.600> want<00:03:31.810> to<00:03:31.890> claim<00:03:32.890> that<00:03:33.790> you're 00:03:33.990 --> 00:03:34.000 align:start position:0% business you want to claim that you're 00:03:34.000 --> 00:03:35.460 align:start position:0% business you want to claim that you're independent<00:03:34.269> or<00:03:34.959> that<00:03:35.170> you're<00:03:35.440> a 00:03:35.460 --> 00:03:35.470 align:start position:0% independent or that you're a 00:03:35.470 --> 00:03:38.520 align:start position:0% independent or that you're a family-owned<00:03:36.100> and<00:03:36.370> in<00:03:37.060> this<00:03:37.239> case<00:03:37.510> the<00:03:38.290> way<00:03:38.470> to 00:03:38.520 --> 00:03:38.530 align:start position:0% family-owned and in this case the way to 00:03:38.530 --> 00:03:41.280 align:start position:0% family-owned and in this case the way to verify<00:03:39.400> that<00:03:39.430> could<00:03:39.850> be<00:03:40.000> for<00:03:40.510> example<00:03:40.570> to<00:03:41.079> link 00:03:41.280 --> 00:03:41.290 align:start position:0% verify that could be for example to link 00:03:41.290 --> 00:03:43.740 align:start position:0% verify that could be for example to link to<00:03:41.440> your<00:03:41.560> business<00:03:41.950> registration<00:03:42.750> that's 00:03:43.740 --> 00:03:43.750 align:start position:0% to your business registration that's 00:03:43.750 --> 00:03:45.810 align:start position:0% to your business registration that's exposed<00:03:44.620> by<00:03:44.829> the<00:03:44.890> government<00:03:45.370> especially<00:03:45.730> in 00:03:45.810 --> 00:03:45.820 align:start position:0% exposed by the government especially in 00:03:45.820 --> 00:03:48.060 align:start position:0% exposed by the government especially in the<00:03:45.910> UK<00:03:46.209> there's<00:03:46.989> companies<00:03:47.410> house<00:03:47.620> that 00:03:48.060 --> 00:03:48.070 align:start position:0% the UK there's companies house that 00:03:48.070 --> 00:03:50.099 align:start position:0% the UK there's companies house that exposes<00:03:48.519> this<00:03:48.640> information<00:03:49.209> and<00:03:49.420> that<00:03:49.450> can 00:03:50.099 --> 00:03:50.109 align:start position:0% exposes this information and that can 00:03:50.109 --> 00:03:52.830 align:start position:0% exposes this information and that can act<00:03:50.620> as<00:03:50.859> a<00:03:51.070> verification<00:03:51.549> that<00:03:51.910> you<00:03:52.480> are<00:03:52.600> for 00:03:52.830 --> 00:03:52.840 align:start position:0% act as a verification that you are for 00:03:52.840 --> 00:03:54.750 align:start position:0% act as a verification that you are for example<00:03:53.170> not<00:03:53.290> owned<00:03:53.530> by<00:03:53.829> another<00:03:53.950> bigger 00:03:54.750 --> 00:03:54.760 align:start position:0% example not owned by another bigger 00:03:54.760 --> 00:03:58.380 align:start position:0% example not owned by another bigger company<00:03:56.340> you<00:03:57.340> could<00:03:57.519> have<00:03:57.730> other 00:03:58.380 --> 00:03:58.390 align:start position:0% company you could have other 00:03:58.390 --> 00:03:59.940 align:start position:0% company you could have other verification<00:03:59.109> methods<00:03:59.470> that<00:03:59.620> could<00:03:59.799> be 00:03:59.940 --> 00:03:59.950 align:start position:0% verification methods that could be 00:03:59.950 --> 00:04:03.000 align:start position:0% verification methods that could be linked<00:04:00.280> that<00:04:01.000> could<00:04:01.120> be<00:04:01.239> based<00:04:01.420> on<00:04:02.010> consumers 00:04:03.000 --> 00:04:03.010 align:start position:0% linked that could be based on consumers 00:04:03.010 --> 00:04:04.560 align:start position:0% linked that could be based on consumers vetting<00:04:03.549> for<00:04:03.730> the<00:04:03.910> businesses<00:04:04.269> that<00:04:04.299> they 00:04:04.560 --> 00:04:04.570 align:start position:0% vetting for the businesses that they 00:04:04.570 --> 00:04:07.349 align:start position:0% vetting for the businesses that they know<00:04:04.750> in<00:04:05.680> the<00:04:05.859> same<00:04:06.040> way<00:04:06.549> in<00:04:06.880> a<00:04:06.970> same<00:04:07.120> kind<00:04:07.299> of 00:04:07.349 --> 00:04:07.359 align:start position:0% know in the same way in a same kind of 00:04:07.359 --> 00:04:11.009 align:start position:0% know in the same way in a same kind of way<00:04:07.540> that<00:04:08.040> TripAdvisor<00:04:09.040> or<00:04:09.430> Yelp<00:04:10.019> functions 00:04:11.009 --> 00:04:11.019 align:start position:0% way that TripAdvisor or Yelp functions 00:04:11.019 --> 00:04:13.920 align:start position:0% way that TripAdvisor or Yelp functions of<00:04:12.010> course<00:04:12.280> not<00:04:12.640> all<00:04:12.880> verification<00:04:13.600> methods 00:04:13.920 --> 00:04:13.930 align:start position:0% of course not all verification methods 00:04:13.930 --> 00:04:15.030 align:start position:0% of course not all verification methods are<00:04:14.049> equal<00:04:14.410> and<00:04:14.620> they<00:04:14.709> provide<00:04:15.010> different 00:04:15.030 --> 00:04:15.040 align:start position:0% are equal and they provide different 00:04:15.040 --> 00:04:17.849 align:start position:0% are equal and they provide different levels<00:04:15.639> of<00:04:15.790> trust<00:04:16.079> and<00:04:17.079> different<00:04:17.470> levels<00:04:17.739> of 00:04:17.849 --> 00:04:17.859 align:start position:0% levels of trust and different levels of 00:04:17.859 --> 00:04:19.140 align:start position:0% levels of trust and different levels of confidence<00:04:18.160> on 00:04:19.140 --> 00:04:19.150 align:start position:0% confidence on 00:04:19.150 --> 00:04:22.920 align:start position:0% confidence on city<00:04:19.419> of<00:04:19.449> the<00:04:19.600> claim<00:04:21.240> another<00:04:22.240> type<00:04:22.540> of<00:04:22.720> claim 00:04:22.920 --> 00:04:22.930 align:start position:0% city of the claim another type of claim 00:04:22.930 --> 00:04:25.170 align:start position:0% city of the claim another type of claim that<00:04:23.250> that's<00:04:24.250> that's<00:04:24.520> really<00:04:24.699> common<00:04:25.000> in 00:04:25.170 --> 00:04:25.180 align:start position:0% that that's that's really common in 00:04:25.180 --> 00:04:28.010 align:start position:0% that that's that's really common in supply<00:04:25.479> chains<00:04:25.720> as<00:04:25.840> that<00:04:26.020> of<00:04:26.259> certification 00:04:28.010 --> 00:04:28.020 align:start position:0% supply chains as that of certification 00:04:28.020 --> 00:04:31.499 align:start position:0% supply chains as that of certification and<00:04:29.020> in<00:04:29.259> this<00:04:29.560> field<00:04:30.340> what<00:04:30.550> we<00:04:30.699> what<00:04:31.000> we<00:04:31.030> did<00:04:31.330> is 00:04:31.499 --> 00:04:31.509 align:start position:0% and in this field what we what we did is 00:04:31.509 --> 00:04:34.350 align:start position:0% and in this field what we what we did is working<00:04:32.199> with<00:04:32.440> the<00:04:32.680> Sioux<00:04:32.800> Association<00:04:33.400> which 00:04:34.350 --> 00:04:34.360 align:start position:0% working with the Sioux Association which 00:04:34.360 --> 00:04:37.580 align:start position:0% working with the Sioux Association which is<00:04:34.389> the<00:04:35.169> first<00:04:35.560> which<00:04:36.220> is<00:04:36.340> the<00:04:36.370> biggest 00:04:37.580 --> 00:04:37.590 align:start position:0% is the first which is the biggest 00:04:37.590 --> 00:04:40.350 align:start position:0% is the first which is the biggest organic<00:04:38.590> search<00:04:38.949> fire<00:04:39.220> in<00:04:39.400> the<00:04:39.520> UK<00:04:39.850> and 00:04:40.350 --> 00:04:40.360 align:start position:0% organic search fire in the UK and 00:04:40.360 --> 00:04:42.629 align:start position:0% organic search fire in the UK and working<00:04:41.139> with<00:04:41.289> them<00:04:41.530> to<00:04:42.100> bring<00:04:42.340> their 00:04:42.629 --> 00:04:42.639 align:start position:0% working with them to bring their 00:04:42.639 --> 00:04:46.320 align:start position:0% working with them to bring their certification<00:04:43.360> to<00:04:43.750> the<00:04:43.870> digital<00:04:44.199> age<00:04:44.430> so<00:04:45.430> what 00:04:46.320 --> 00:04:46.330 align:start position:0% certification to the digital age so what 00:04:46.330 --> 00:04:48.900 align:start position:0% certification to the digital age so what what<00:04:46.570> what<00:04:46.780> does<00:04:46.900> that<00:04:46.930> mean<00:04:47.259> what<00:04:47.470> I<00:04:48.310> think<00:04:48.729> we 00:04:48.900 --> 00:04:48.910 align:start position:0% what what does that mean what I think we 00:04:48.910 --> 00:04:51.060 align:start position:0% what what does that mean what I think we needed<00:04:49.120> a<00:04:49.270> bit<00:04:49.389> of<00:04:49.509> context<00:04:49.990> around<00:04:50.139> what<00:04:50.590> a 00:04:51.060 --> 00:04:51.070 align:start position:0% needed a bit of context around what a 00:04:51.070 --> 00:04:53.189 align:start position:0% needed a bit of context around what a certification<00:04:51.789> process<00:04:52.240> looks<00:04:52.660> like<00:04:52.840> today 00:04:53.189 --> 00:04:53.199 align:start position:0% certification process looks like today 00:04:53.199 --> 00:04:56.460 align:start position:0% certification process looks like today for<00:04:53.500> a<00:04:53.530> sustainability<00:04:54.449> certification<00:04:55.470> so 00:04:56.460 --> 00:04:56.470 align:start position:0% for a sustainability certification so 00:04:56.470 --> 00:04:57.900 align:start position:0% for a sustainability certification so basically<00:04:56.770> as<00:04:56.919> a<00:04:56.949> business<00:04:57.400> if<00:04:57.550> you<00:04:57.669> want<00:04:57.820> to 00:04:57.900 --> 00:04:57.910 align:start position:0% basically as a business if you want to 00:04:57.910 --> 00:05:00.360 align:start position:0% basically as a business if you want to be<00:04:58.000> certified<00:04:58.330> organic<00:04:59.169> you're<00:04:59.889> going<00:05:00.130> to 00:05:00.360 --> 00:05:00.370 align:start position:0% be certified organic you're going to 00:05:00.370 --> 00:05:02.330 align:start position:0% be certified organic you're going to apply<00:05:01.000> for<00:05:01.090> a<00:05:01.449> certification 00:05:02.330 --> 00:05:02.340 align:start position:0% apply for a certification 00:05:02.340 --> 00:05:06.270 align:start position:0% apply for a certification obviously<00:05:03.340> pay<00:05:04.180> a<00:05:04.479> fee<00:05:04.800> which<00:05:05.800> can<00:05:06.010> be<00:05:06.130> quite 00:05:06.270 --> 00:05:06.280 align:start position:0% obviously pay a fee which can be quite 00:05:06.280 --> 00:05:08.390 align:start position:0% obviously pay a fee which can be quite expensive<00:05:06.520> sometimes<00:05:07.000> for<00:05:07.600> small<00:05:07.780> businesses 00:05:08.390 --> 00:05:08.400 align:start position:0% expensive sometimes for small businesses 00:05:08.400 --> 00:05:10.969 align:start position:0% expensive sometimes for small businesses then<00:05:09.400> you're<00:05:09.580> going<00:05:09.760> to<00:05:09.910> be<00:05:10.030> audited<00:05:10.300> by<00:05:10.479> an 00:05:10.969 --> 00:05:10.979 align:start position:0% then you're going to be audited by an 00:05:10.979 --> 00:05:14.700 align:start position:0% then you're going to be audited by an independent<00:05:12.000> auditor<00:05:13.000> and<00:05:13.300> if<00:05:14.020> if<00:05:14.410> all<00:05:14.650> goes 00:05:14.700 --> 00:05:14.710 align:start position:0% independent auditor and if if all goes 00:05:14.710 --> 00:05:17.879 align:start position:0% independent auditor and if if all goes well<00:05:15.330> you<00:05:16.330> are<00:05:16.389> going<00:05:16.690> to<00:05:16.990> be<00:05:17.320> awarded<00:05:17.530> a 00:05:17.879 --> 00:05:17.889 align:start position:0% well you are going to be awarded a 00:05:17.889 --> 00:05:20.100 align:start position:0% well you are going to be awarded a certification<00:05:18.280> what<00:05:19.150> that<00:05:19.389> means<00:05:19.840> in<00:05:20.080> terms 00:05:20.100 --> 00:05:20.110 align:start position:0% certification what that means in terms 00:05:20.110 --> 00:05:22.110 align:start position:0% certification what that means in terms of<00:05:20.410> data<00:05:20.590> is<00:05:20.830> that<00:05:20.979> it's<00:05:21.190> just<00:05:21.370> another<00:05:21.669> record 00:05:22.110 --> 00:05:22.120 align:start position:0% of data is that it's just another record 00:05:22.120 --> 00:05:25.529 align:start position:0% of data is that it's just another record in<00:05:23.050> solar<00:05:23.949> association<00:05:24.460> database<00:05:24.910> that<00:05:25.300> keeps 00:05:25.529 --> 00:05:25.539 align:start position:0% in solar association database that keeps 00:05:25.539 --> 00:05:27.870 align:start position:0% in solar association database that keeps track<00:05:25.660> of<00:05:25.780> all<00:05:26.020> certifications<00:05:26.680> and<00:05:27.010> the<00:05:27.729> way 00:05:27.870 --> 00:05:27.880 align:start position:0% track of all certifications and the way 00:05:27.880 --> 00:05:30.060 align:start position:0% track of all certifications and the way as<00:05:28.270> a<00:05:28.300> business<00:05:28.780> you<00:05:29.050> are<00:05:29.139> going<00:05:29.380> to<00:05:29.500> be<00:05:29.949> able 00:05:30.060 --> 00:05:30.070 align:start position:0% as a business you are going to be able 00:05:30.070 --> 00:05:32.939 align:start position:0% as a business you are going to be able to<00:05:30.250> prove<00:05:30.580> that<00:05:30.849> is<00:05:31.090> through<00:05:31.530> PDF<00:05:32.530> that<00:05:32.800> is 00:05:32.939 --> 00:05:32.949 align:start position:0% to prove that is through PDF that is 00:05:32.949 --> 00:05:35.520 align:start position:0% to prove that is through PDF that is sent<00:05:33.250> to<00:05:33.370> you<00:05:33.550> it's<00:05:34.270> basically<00:05:34.389> a<00:05:34.659> certificate 00:05:35.520 --> 00:05:35.530 align:start position:0% sent to you it's basically a certificate 00:05:35.530 --> 00:05:39.570 align:start position:0% sent to you it's basically a certificate of<00:05:36.419> organic<00:05:37.419> so<00:05:38.289> when<00:05:39.070> you're<00:05:39.190> going<00:05:39.310> to<00:05:39.490> be 00:05:39.570 --> 00:05:39.580 align:start position:0% of organic so when you're going to be 00:05:39.580 --> 00:05:41.550 align:start position:0% of organic so when you're going to be transacting<00:05:40.270> with<00:05:40.780> your<00:05:40.900> business<00:05:41.110> partners 00:05:41.550 --> 00:05:41.560 align:start position:0% transacting with your business partners 00:05:41.560 --> 00:05:42.810 align:start position:0% transacting with your business partners you<00:05:41.710> need<00:05:41.860> to<00:05:41.979> prove<00:05:42.159> to<00:05:42.370> them<00:05:42.490> that<00:05:42.520> you're 00:05:42.810 --> 00:05:42.820 align:start position:0% you need to prove to them that you're 00:05:42.820 --> 00:05:45.750 align:start position:0% you need to prove to them that you're certified<00:05:43.810> organic<00:05:44.139> you<00:05:44.740> end<00:05:44.949> up<00:05:45.159> moving<00:05:45.430> back 00:05:45.750 --> 00:05:45.760 align:start position:0% certified organic you end up moving back 00:05:45.760 --> 00:05:50.339 align:start position:0% certified organic you end up moving back and<00:05:45.909> forth<00:05:46.180> PDFs<00:05:47.110> in<00:05:47.860> a<00:05:47.949> supply<00:05:48.220> chain<00:05:49.349> from 00:05:50.339 --> 00:05:50.349 align:start position:0% and forth PDFs in a supply chain from 00:05:50.349 --> 00:05:52.320 align:start position:0% and forth PDFs in a supply chain from the<00:05:50.440> point<00:05:50.710> of<00:05:50.830> view<00:05:50.889> of<00:05:50.949> the<00:05:51.099> consumer<00:05:51.610> the 00:05:52.320 --> 00:05:52.330 align:start position:0% the point of view of the consumer the 00:05:52.330 --> 00:05:54.029 align:start position:0% the point of view of the consumer the interaction<00:05:52.840> that<00:05:52.870> the<00:05:53.260> consumer<00:05:53.680> would<00:05:53.800> have 00:05:54.029 --> 00:05:54.039 align:start position:0% interaction that the consumer would have 00:05:54.039 --> 00:05:57.420 align:start position:0% interaction that the consumer would have with<00:05:54.580> a<00:05:54.610> sustainability<00:05:55.740> certification<00:05:56.740> most 00:05:57.420 --> 00:05:57.430 align:start position:0% with a sustainability certification most 00:05:57.430 --> 00:06:00.450 align:start position:0% with a sustainability certification most of<00:05:57.550> the<00:05:57.610> time<00:05:57.820> is<00:05:58.030> either<00:05:58.750> through<00:05:59.740> just<00:06:00.220> a 00:06:00.450 --> 00:06:00.460 align:start position:0% of the time is either through just a 00:06:00.460 --> 00:06:04.560 align:start position:0% of the time is either through just a logo<00:06:00.789> unpack<00:06:01.620> or<00:06:02.620> it's<00:06:03.550> going<00:06:03.789> to<00:06:03.849> be<00:06:03.940> a<00:06:04.210> static 00:06:04.560 --> 00:06:04.570 align:start position:0% logo unpack or it's going to be a static 00:06:04.570 --> 00:06:08.250 align:start position:0% logo unpack or it's going to be a static JPEG<00:06:05.500> on<00:06:05.740> on<00:06:06.070> a<00:06:06.099> website<00:06:06.520> for<00:06:06.699> example<00:06:07.260> so 00:06:08.250 --> 00:06:08.260 align:start position:0% JPEG on on a website for example so 00:06:08.260 --> 00:06:09.930 align:start position:0% JPEG on on a website for example so that's<00:06:08.380> where<00:06:08.650> we<00:06:08.800> saw<00:06:09.010> some<00:06:09.340> opportunities 00:06:09.930 --> 00:06:09.940 align:start position:0% that's where we saw some opportunities 00:06:09.940 --> 00:06:11.610 align:start position:0% that's where we saw some opportunities to<00:06:09.970> make<00:06:10.510> that<00:06:10.659> better<00:06:10.870> and<00:06:11.110> make<00:06:11.289> it<00:06:11.320> more 00:06:11.610 --> 00:06:11.620 align:start position:0% to make that better and make it more 00:06:11.620 --> 00:06:14.760 align:start position:0% to make that better and make it more interactive<00:06:11.889> and<00:06:12.400> and<00:06:12.789> and<00:06:13.090> interoperable<00:06:13.840> so 00:06:14.760 --> 00:06:14.770 align:start position:0% interactive and and and interoperable so 00:06:14.770 --> 00:06:17.790 align:start position:0% interactive and and and interoperable so what<00:06:14.979> we<00:06:15.099> did<00:06:15.280> is<00:06:15.810> connecting<00:06:16.810> the<00:06:17.590> solar 00:06:17.790 --> 00:06:17.800 align:start position:0% what we did is connecting the solar 00:06:17.800 --> 00:06:21.270 align:start position:0% what we did is connecting the solar Association<00:06:18.370> certification<00:06:19.470> database<00:06:20.470> to 00:06:21.270 --> 00:06:21.280 align:start position:0% Association certification database to 00:06:21.280 --> 00:06:23.460 align:start position:0% Association certification database to the<00:06:21.400> ethereum<00:06:21.729> blockchain<00:06:21.760> so<00:06:22.750> that<00:06:22.960> directly 00:06:23.460 --> 00:06:23.470 align:start position:0% the ethereum blockchain so that directly 00:06:23.470 --> 00:06:25.529 align:start position:0% the ethereum blockchain so that directly on<00:06:23.919> the<00:06:24.310> theory<00:06:24.520> on<00:06:24.639> blockchain<00:06:24.880> you<00:06:25.300> could 00:06:25.529 --> 00:06:25.539 align:start position:0% on the theory on blockchain you could 00:06:25.539 --> 00:06:28.560 align:start position:0% on the theory on blockchain you could check<00:06:26.260> the<00:06:26.650> status<00:06:27.070> of<00:06:27.340> any<00:06:27.820> certification 00:06:28.560 --> 00:06:28.570 align:start position:0% check the status of any certification 00:06:28.570 --> 00:06:32.450 align:start position:0% check the status of any certification for<00:06:28.779> any<00:06:29.159> licensee<00:06:30.159> of<00:06:30.460> the<00:06:30.940> Soil<00:06:31.150> Association 00:06:32.450 --> 00:06:32.460 align:start position:0% for any licensee of the Soil Association 00:06:32.460 --> 00:06:35.219 align:start position:0% for any licensee of the Soil Association creating<00:06:33.460> a<00:06:33.639> kind<00:06:34.029> of<00:06:34.119> a<00:06:34.240> digital<00:06:34.719> version<00:06:35.110> of 00:06:35.219 --> 00:06:35.229 align:start position:0% creating a kind of a digital version of 00:06:35.229 --> 00:06:39.929 align:start position:0% creating a kind of a digital version of that<00:06:35.860> certification<00:06:38.309> the<00:06:39.309> outcome<00:06:39.669> of<00:06:39.699> this 00:06:39.929 --> 00:06:39.939 align:start position:0% that certification the outcome of this 00:06:39.939 --> 00:06:43.459 align:start position:0% that certification the outcome of this project<00:06:40.869> was<00:06:41.080> that<00:06:41.110> we<00:06:41.289> created<00:06:42.449> material 00:06:43.459 --> 00:06:43.469 align:start position:0% project was that we created material 00:06:43.469 --> 00:06:47.219 align:start position:0% project was that we created material both<00:06:44.469> for<00:06:44.889> point<00:06:45.610> of<00:06:45.699> sale<00:06:45.759> so<00:06:46.389> in<00:06:46.659> the<00:06:46.779> form<00:06:47.050> of 00:06:47.219 --> 00:06:47.229 align:start position:0% both for point of sale so in the form of 00:06:47.229 --> 00:06:49.769 align:start position:0% both for point of sale so in the form of connected<00:06:47.919> labels<00:06:48.279> that<00:06:48.460> you<00:06:48.699> that<00:06:49.270> consumers 00:06:49.769 --> 00:06:49.779 align:start position:0% connected labels that you that consumers 00:06:49.779 --> 00:06:54.899 align:start position:0% connected labels that you that consumers can<00:06:50.759> can<00:06:51.759> scan<00:06:52.180> either<00:06:52.449> by<00:06:52.869> NFC<00:06:53.469> or<00:06:53.740> QR<00:06:54.610> codes 00:06:54.899 --> 00:06:54.909 align:start position:0% can can scan either by NFC or QR codes 00:06:54.909 --> 00:06:57.600 align:start position:0% can can scan either by NFC or QR codes and<00:06:55.029> we're<00:06:55.210> very<00:06:55.419> excited<00:06:55.569> that<00:06:55.960> NFC<00:06:56.529> is<00:06:57.369> now 00:06:57.600 --> 00:06:57.610 align:start position:0% and we're very excited that NFC is now 00:06:57.610 --> 00:07:01.889 align:start position:0% and we're very excited that NFC is now being<00:06:58.360> supported<00:06:58.899> by<00:06:59.339> by<00:07:00.389> the<00:07:01.389> new<00:07:01.509> version<00:07:01.809> of 00:07:01.889 --> 00:07:01.899 align:start position:0% being supported by by the new version of 00:07:01.899 --> 00:07:07.739 align:start position:0% being supported by by the new version of iOS<00:07:04.050> so<00:07:05.050> that<00:07:05.249> consumers<00:07:06.249> can<00:07:06.749> access 00:07:07.739 --> 00:07:07.749 align:start position:0% iOS so that consumers can access 00:07:07.749 --> 00:07:09.929 align:start position:0% iOS so that consumers can access directly<00:07:08.110> is<00:07:08.289> to<00:07:08.529> this<00:07:08.649> information<00:07:08.979> at<00:07:09.490> the 00:07:09.929 --> 00:07:09.939 align:start position:0% directly is to this information at the 00:07:09.939 --> 00:07:12.329 align:start position:0% directly is to this information at the point<00:07:10.119> of<00:07:10.180> sale<00:07:10.389> and<00:07:10.919> when<00:07:11.919> it<00:07:12.039> comes<00:07:12.189> to 00:07:12.329 --> 00:07:12.339 align:start position:0% point of sale and when it comes to 00:07:12.339 --> 00:07:16.219 align:start position:0% point of sale and when it comes to digital<00:07:12.490> space<00:07:13.110> we<00:07:14.110> created<00:07:14.619> embeds<00:07:15.039> that 00:07:16.219 --> 00:07:16.229 align:start position:0% digital space we created embeds that 00:07:16.229 --> 00:07:19.459 align:start position:0% digital space we created embeds that brands<00:07:17.229> that<00:07:17.379> were<00:07:17.559> certified<00:07:18.009> organic<00:07:18.430> can 00:07:19.459 --> 00:07:19.469 align:start position:0% brands that were certified organic can 00:07:19.469 --> 00:07:24.059 align:start position:0% brands that were certified organic can integrate<00:07:20.469> in<00:07:20.919> their<00:07:21.330> online<00:07:22.330> store<00:07:22.889> so<00:07:23.889> that 00:07:24.059 --> 00:07:24.069 align:start position:0% integrate in their online store so that 00:07:24.069 --> 00:07:26.189 align:start position:0% integrate in their online store so that consumers<00:07:24.369> again<00:07:24.789> can<00:07:25.059> access<00:07:25.539> and<00:07:25.809> verify 00:07:26.189 --> 00:07:26.199 align:start position:0% consumers again can access and verify 00:07:26.199 --> 00:07:29.010 align:start position:0% consumers again can access and verify the<00:07:26.259> status<00:07:27.219> of<00:07:27.339> the<00:07:27.459> certification<00:07:28.089> on<00:07:28.779> top 00:07:29.010 --> 00:07:29.020 align:start position:0% the status of the certification on top 00:07:29.020 --> 00:07:31.709 align:start position:0% the status of the certification on top of<00:07:29.169> that<00:07:29.289> the<00:07:29.649> fact<00:07:29.889> that<00:07:30.149> we<00:07:31.149> provided<00:07:31.599> those 00:07:31.709 --> 00:07:31.719 align:start position:0% of that the fact that we provided those 00:07:31.719 --> 00:07:33.779 align:start position:0% of that the fact that we provided those tools<00:07:32.139> to<00:07:32.439> kind<00:07:32.649> of<00:07:32.709> augment<00:07:33.099> the 00:07:33.779 --> 00:07:33.789 align:start position:0% tools to kind of augment the 00:07:33.789 --> 00:07:36.269 align:start position:0% tools to kind of augment the certification<00:07:34.680> allowed<00:07:35.680> to<00:07:35.919> raise<00:07:36.099> awareness 00:07:36.269 --> 00:07:36.279 align:start position:0% certification allowed to raise awareness 00:07:36.279 --> 00:07:39.509 align:start position:0% certification allowed to raise awareness on<00:07:36.759> what<00:07:37.599> the<00:07:38.259> certification<00:07:38.860> actually<00:07:39.279> means 00:07:39.509 --> 00:07:39.519 align:start position:0% on what the certification actually means 00:07:39.519 --> 00:07:41.759 align:start position:0% on what the certification actually means and<00:07:39.789> what<00:07:40.300> it<00:07:40.419> stands<00:07:40.659> for 00:07:41.759 --> 00:07:41.769 align:start position:0% and what it stands for 00:07:41.769 --> 00:07:43.829 align:start position:0% and what it stands for because<00:07:42.189> we<00:07:42.279> believe<00:07:42.490> that<00:07:42.639> just<00:07:42.849> just<00:07:43.240> just<00:07:43.749> a 00:07:43.829 --> 00:07:43.839 align:start position:0% because we believe that just just just a 00:07:43.839 --> 00:07:46.159 align:start position:0% because we believe that just just just a logo<00:07:44.019> unpack<00:07:44.499> it's<00:07:44.769> not<00:07:44.919> enough<00:07:45.189> to<00:07:45.430> convey 00:07:46.159 --> 00:07:46.169 align:start position:0% logo unpack it's not enough to convey 00:07:46.169 --> 00:07:49.170 align:start position:0% logo unpack it's not enough to convey what<00:07:47.169> the<00:07:47.379> audit<00:07:47.649> process<00:07:48.009> was<00:07:48.249> and<00:07:48.580> and<00:07:48.909> what 00:07:49.170 --> 00:07:49.180 align:start position:0% what the audit process was and and what 00:07:49.180 --> 00:07:53.179 align:start position:0% what the audit process was and and what actually<00:07:49.629> the<00:07:49.959> compliance<00:07:50.409> look<00:07:50.559> looks<00:07:51.009> like 00:07:53.179 --> 00:07:53.189 align:start position:0% actually the compliance look looks like 00:07:53.189 --> 00:07:56.639 align:start position:0% actually the compliance look looks like so<00:07:54.189> moving<00:07:54.550> from<00:07:54.930> businesses<00:07:55.930> what<00:07:56.499> we're 00:07:56.639 --> 00:07:56.649 align:start position:0% so moving from businesses what we're 00:07:56.649 --> 00:07:59.639 align:start position:0% so moving from businesses what we're trying<00:07:56.800> to<00:07:56.979> do<00:07:57.099> is<00:07:57.219> also<00:07:57.430> to<00:07:57.990> have<00:07:58.990> verifiable 00:07:59.639 --> 00:07:59.649 align:start position:0% trying to do is also to have verifiable 00:07:59.649 --> 00:08:02.820 align:start position:0% trying to do is also to have verifiable claims<00:07:59.949> on<00:08:00.249> products<00:08:01.319> so<00:08:02.319> when<00:08:02.469> when<00:08:02.740> you 00:08:02.820 --> 00:08:02.830 align:start position:0% claims on products so when when you 00:08:02.830 --> 00:08:04.529 align:start position:0% claims on products so when when you think<00:08:03.039> about<00:08:03.219> a<00:08:03.249> product<00:08:03.550> one<00:08:03.909> verifiable 00:08:04.529 --> 00:08:04.539 align:start position:0% think about a product one verifiable 00:08:04.539 --> 00:08:05.730 align:start position:0% think about a product one verifiable claim<00:08:04.749> that<00:08:04.869> you<00:08:04.990> could<00:08:05.110> have<00:08:05.289> is<00:08:05.439> for<00:08:05.589> example 00:08:05.730 --> 00:08:05.740 align:start position:0% claim that you could have is for example 00:08:05.740 --> 00:08:08.489 align:start position:0% claim that you could have is for example that<00:08:06.129> it's<00:08:06.279> free<00:08:06.669> of<00:08:06.849> a<00:08:07.180> particular<00:08:07.719> allergen 00:08:08.489 --> 00:08:08.499 align:start position:0% that it's free of a particular allergen 00:08:08.499 --> 00:08:11.999 align:start position:0% that it's free of a particular allergen and<00:08:08.649> a<00:08:09.430> way<00:08:09.580> to<00:08:09.610> verify<00:08:10.479> that<00:08:10.719> could<00:08:11.709> be<00:08:11.860> either 00:08:11.999 --> 00:08:12.009 align:start position:0% and a way to verify that could be either 00:08:12.009 --> 00:08:14.609 align:start position:0% and a way to verify that could be either by<00:08:12.279> normal<00:08:12.969> audits<00:08:13.330> but<00:08:13.659> also<00:08:13.899> increasingly 00:08:14.609 --> 00:08:14.619 align:start position:0% by normal audits but also increasingly 00:08:14.619 --> 00:08:17.670 align:start position:0% by normal audits but also increasingly and<00:08:15.039> and<00:08:15.369> and<00:08:15.580> it's<00:08:15.699> getting<00:08:16.149> cheaper<00:08:16.680> through 00:08:17.670 --> 00:08:17.680 align:start position:0% and and and it's getting cheaper through 00:08:17.680 --> 00:08:20.489 align:start position:0% and and and it's getting cheaper through things<00:08:18.069> like<00:08:18.159> DNA<00:08:18.849> testing<00:08:19.300> if<00:08:20.169> we're<00:08:20.349> also 00:08:20.489 --> 00:08:20.499 align:start position:0% things like DNA testing if we're also 00:08:20.499 --> 00:08:24.570 align:start position:0% things like DNA testing if we're also looking<00:08:21.459> at<00:08:21.729> but<00:08:22.539> in<00:08:22.719> this<00:08:22.839> context<00:08:23.289> we<00:08:24.159> saw 00:08:24.570 --> 00:08:24.580 align:start position:0% looking at but in this context we saw 00:08:24.580 --> 00:08:27.839 align:start position:0% looking at but in this context we saw that<00:08:24.729> a<00:08:24.789> very<00:08:25.149> useful<00:08:25.360> tool<00:08:25.839> to<00:08:26.459> prove<00:08:27.459> claims 00:08:27.839 --> 00:08:27.849 align:start position:0% that a very useful tool to prove claims 00:08:27.849 --> 00:08:30.600 align:start position:0% that a very useful tool to prove claims about<00:08:28.330> products<00:08:29.139> was<00:08:29.649> that<00:08:29.889> of<00:08:30.129> a<00:08:30.309> tracking 00:08:30.600 --> 00:08:30.610 align:start position:0% about products was that of a tracking 00:08:30.610 --> 00:08:33.329 align:start position:0% about products was that of a tracking system<00:08:30.909> along<00:08:31.479> the<00:08:31.599> supply<00:08:31.809> chain<00:08:32.339> that's 00:08:33.329 --> 00:08:33.339 align:start position:0% system along the supply chain that's 00:08:33.339 --> 00:08:35.600 align:start position:0% system along the supply chain that's why--that's<00:08:33.490> we<00:08:33.939> we<00:08:34.269> developed<00:08:34.930> a<00:08:35.079> way<00:08:35.259> to 00:08:35.600 --> 00:08:35.610 align:start position:0% why--that's we we developed a way to 00:08:35.610 --> 00:08:38.279 align:start position:0% why--that's we we developed a way to track<00:08:36.610> assets<00:08:36.969> along<00:08:37.509> the<00:08:37.630> supply<00:08:37.839> chain<00:08:38.110> and 00:08:38.279 --> 00:08:38.289 align:start position:0% track assets along the supply chain and 00:08:38.289 --> 00:08:43.139 align:start position:0% track assets along the supply chain and tested<00:08:38.709> that<00:08:38.829> in<00:08:39.149> different<00:08:40.149> pilots<00:08:41.370> so<00:08:42.370> maybe 00:08:43.139 --> 00:08:43.149 align:start position:0% tested that in different pilots so maybe 00:08:43.149 --> 00:08:44.920 align:start position:0% tested that in different pilots so maybe someone<00:08:43.479> in<00:08:43.630> the<00:08:43.750> room<00:08:43.870> so<00:08:44.169> our 00:08:44.920 --> 00:08:44.930 align:start position:0% someone in the room so our 00:08:44.930 --> 00:08:48.280 align:start position:0% someone in the room so our peace<00:08:45.260> on<00:08:45.670> toon<00:08:46.670> a<00:08:46.790> supply<00:08:47.060> chain<00:08:47.290> we 00:08:48.280 --> 00:08:48.290 align:start position:0% peace on toon a supply chain we 00:08:48.290 --> 00:08:50.920 align:start position:0% peace on toon a supply chain we basically<00:08:49.120> studied<00:08:50.120> tunas<00:08:50.660> to<00:08:50.750> play<00:08:50.899> a 00:08:50.920 --> 00:08:50.930 align:start position:0% basically studied tunas to play a 00:08:50.930 --> 00:08:53.290 align:start position:0% basically studied tunas to play a sustainable<00:08:51.649> tuna<00:08:51.830> supply<00:08:52.310> chain<00:08:52.610> over<00:08:52.820> in 00:08:53.290 --> 00:08:53.300 align:start position:0% sustainable tuna supply chain over in 00:08:53.300 --> 00:08:56.769 align:start position:0% sustainable tuna supply chain over in Indonesia<00:08:53.750> and<00:08:54.640> basically<00:08:55.640> the<00:08:56.210> setup<00:08:56.450> was 00:08:56.769 --> 00:08:56.779 align:start position:0% Indonesia and basically the setup was 00:08:56.779 --> 00:08:59.760 align:start position:0% Indonesia and basically the setup was that<00:08:57.250> there<00:08:58.250> there's<00:08:58.700> there<00:08:59.510> was<00:08:59.660> a 00:08:59.760 --> 00:08:59.770 align:start position:0% that there there's there was a 00:08:59.770 --> 00:09:02.980 align:start position:0% that there there's there was a certification<00:09:00.770> over<00:09:01.700> in<00:09:01.790> Indonesia 00:09:02.980 --> 00:09:02.990 align:start position:0% certification over in Indonesia 00:09:02.990 --> 00:09:07.000 align:start position:0% certification over in Indonesia according<00:09:03.740> to<00:09:04.510> sustainability<00:09:06.010> practices 00:09:07.000 --> 00:09:07.010 align:start position:0% according to sustainability practices 00:09:07.010 --> 00:09:09.220 align:start position:0% according to sustainability practices that<00:09:07.310> was<00:09:07.490> certifying<00:09:08.000> specific<00:09:08.810> fishermen 00:09:09.220 --> 00:09:09.230 align:start position:0% that was certifying specific fishermen 00:09:09.230 --> 00:09:13.230 align:start position:0% that was certifying specific fishermen that<00:09:09.770> could<00:09:10.990> that<00:09:11.990> like<00:09:12.320> that<00:09:12.529> could<00:09:12.709> produce 00:09:13.230 --> 00:09:13.240 align:start position:0% that could that like that could produce 00:09:13.240 --> 00:09:16.720 align:start position:0% that could that like that could produce tuna<00:09:14.240> that<00:09:14.390> was<00:09:14.540> certified<00:09:15.430> so<00:09:16.430> that<00:09:16.580> was 00:09:16.720 --> 00:09:16.730 align:start position:0% tuna that was certified so that was 00:09:16.730 --> 00:09:18.490 align:start position:0% tuna that was certified so that was going<00:09:16.970> great<00:09:17.120> but<00:09:17.540> the<00:09:17.720> the<00:09:18.050> problem<00:09:18.470> with 00:09:18.490 --> 00:09:18.500 align:start position:0% going great but the the problem with 00:09:18.500 --> 00:09:21.100 align:start position:0% going great but the the problem with this<00:09:18.830> was<00:09:19.160> that<00:09:19.399> when<00:09:20.330> looking<00:09:20.660> at<00:09:20.779> the<00:09:20.870> supply 00:09:21.100 --> 00:09:21.110 align:start position:0% this was that when looking at the supply 00:09:21.110 --> 00:09:23.769 align:start position:0% this was that when looking at the supply chain<00:09:21.440> there<00:09:21.620> were<00:09:21.740> there<00:09:22.010> was<00:09:22.130> way<00:09:22.459> more<00:09:22.779> fish 00:09:23.769 --> 00:09:23.779 align:start position:0% chain there were there was way more fish 00:09:23.779 --> 00:09:26.410 align:start position:0% chain there were there was way more fish being<00:09:24.370> sold<00:09:25.370> at<00:09:25.580> the<00:09:25.700> end<00:09:25.730> of<00:09:25.880> supply<00:09:26.149> chain 00:09:26.410 --> 00:09:26.420 align:start position:0% being sold at the end of supply chain 00:09:26.420 --> 00:09:29.740 align:start position:0% being sold at the end of supply chain with<00:09:26.720> the<00:09:26.899> certification<00:09:27.430> then<00:09:28.600> there<00:09:29.600> was 00:09:29.740 --> 00:09:29.750 align:start position:0% with the certification then there was 00:09:29.750 --> 00:09:32.910 align:start position:0% with the certification then there was certifications<00:09:30.589> being<00:09:30.890> issued<00:09:31.270> at<00:09:32.270> the<00:09:32.330> start 00:09:32.910 --> 00:09:32.920 align:start position:0% certifications being issued at the start 00:09:32.920 --> 00:09:35.440 align:start position:0% certifications being issued at the start so<00:09:33.920> basically<00:09:34.279> what<00:09:34.850> we<00:09:35.000> were<00:09:35.120> trying<00:09:35.330> to 00:09:35.440 --> 00:09:35.450 align:start position:0% so basically what we were trying to 00:09:35.450 --> 00:09:37.269 align:start position:0% so basically what we were trying to solve<00:09:35.779> with<00:09:36.110> and<00:09:36.680> in<00:09:36.830> this<00:09:37.010> particular 00:09:37.269 --> 00:09:37.279 align:start position:0% solve with and in this particular 00:09:37.279 --> 00:09:39.300 align:start position:0% solve with and in this particular project<00:09:37.850> was<00:09:37.970> the<00:09:38.029> double<00:09:38.480> spending<00:09:38.570> of 00:09:39.300 --> 00:09:39.310 align:start position:0% project was the double spending of 00:09:39.310 --> 00:09:41.170 align:start position:0% project was the double spending of certificate<00:09:40.310> of<00:09:40.399> sustainability 00:09:41.170 --> 00:09:41.180 align:start position:0% certificate of sustainability 00:09:41.180 --> 00:09:45.610 align:start position:0% certificate of sustainability certification<00:09:41.589> claims<00:09:42.589> on<00:09:43.550> tuna<00:09:44.350> so<00:09:45.350> what<00:09:45.470> we 00:09:45.610 --> 00:09:45.620 align:start position:0% certification claims on tuna so what we 00:09:45.620 --> 00:09:48.400 align:start position:0% certification claims on tuna so what we built<00:09:45.860> for<00:09:46.580> that<00:09:46.640> was<00:09:47.240> an<00:09:47.510> interface<00:09:48.020> for 00:09:48.400 --> 00:09:48.410 align:start position:0% built for that was an interface for 00:09:48.410 --> 00:09:50.500 align:start position:0% built for that was an interface for fishermen<00:09:48.890> to<00:09:49.070> register<00:09:49.580> their<00:09:50.029> catch 00:09:50.500 --> 00:09:50.510 align:start position:0% fishermen to register their catch 00:09:50.510 --> 00:09:54.900 align:start position:0% fishermen to register their catch yeah<00:09:51.500> batch<00:09:52.279> of<00:09:52.459> tuna<00:09:52.820> using<00:09:53.420> SMS<00:09:53.870> services 00:09:54.900 --> 00:09:54.910 align:start position:0% yeah batch of tuna using SMS services 00:09:54.910 --> 00:09:56.920 align:start position:0% yeah batch of tuna using SMS services because<00:09:55.910> in<00:09:56.150> the<00:09:56.270> environment<00:09:56.720> we<00:09:56.839> were 00:09:56.920 --> 00:09:56.930 align:start position:0% because in the environment we were 00:09:56.930 --> 00:09:59.260 align:start position:0% because in the environment we were operating<00:09:57.500> in<00:09:57.620> there<00:09:58.400> was<00:09:58.550> even<00:09:59.150> no 00:09:59.260 --> 00:09:59.270 align:start position:0% operating in there was even no 00:09:59.270 --> 00:10:02.800 align:start position:0% operating in there was even no smartphone<00:09:59.830> to<00:10:00.830> use<00:10:01.550> so<00:10:01.730> it<00:10:02.029> had<00:10:02.180> to<00:10:02.390> go 00:10:02.800 --> 00:10:02.810 align:start position:0% smartphone to use so it had to go 00:10:02.810 --> 00:10:06.970 align:start position:0% smartphone to use so it had to go through<00:10:03.050> SMS<00:10:05.050> those<00:10:06.050> catches<00:10:06.500> would<00:10:06.650> be 00:10:06.970 --> 00:10:06.980 align:start position:0% through SMS those catches would be 00:10:06.980 --> 00:10:08.530 align:start position:0% through SMS those catches would be linked<00:10:07.400> to<00:10:07.580> the<00:10:07.700> certification<00:10:08.029> that<00:10:08.450> the 00:10:08.530 --> 00:10:08.540 align:start position:0% linked to the certification that the 00:10:08.540 --> 00:10:11.220 align:start position:0% linked to the certification that the fishermen<00:10:08.990> had<00:10:09.800> been<00:10:09.980> awarded<00:10:10.250> before<00:10:10.580> and 00:10:11.220 --> 00:10:11.230 align:start position:0% fishermen had been awarded before and 00:10:11.230 --> 00:10:14.410 align:start position:0% fishermen had been awarded before and then<00:10:12.230> they<00:10:12.620> were<00:10:12.740> able<00:10:13.130> to<00:10:13.420> transfer 00:10:14.410 --> 00:10:14.420 align:start position:0% then they were able to transfer 00:10:14.420 --> 00:10:18.699 align:start position:0% then they were able to transfer ownership<00:10:14.630> of<00:10:15.140> this<00:10:16.390> these<00:10:17.390> batches<00:10:18.200> down<00:10:18.560> the 00:10:18.699 --> 00:10:18.709 align:start position:0% ownership of this these batches down the 00:10:18.709 --> 00:10:21.850 align:start position:0% ownership of this these batches down the supply<00:10:18.980> chain<00:10:19.010> and<00:10:19.400> at<00:10:20.089> each<00:10:20.330> step<00:10:20.690> a<00:10:21.110> transfer 00:10:21.850 --> 00:10:21.860 align:start position:0% supply chain and at each step a transfer 00:10:21.860 --> 00:10:24.070 align:start position:0% supply chain and at each step a transfer would<00:10:22.010> be<00:10:22.070> a<00:10:22.220> handshake<00:10:22.760> between<00:10:22.940> this<00:10:23.420> sender 00:10:24.070 --> 00:10:24.080 align:start position:0% would be a handshake between this sender 00:10:24.080 --> 00:10:27.699 align:start position:0% would be a handshake between this sender and<00:10:24.260> the<00:10:24.589> receiver<00:10:25.150> agreeing<00:10:26.150> on<00:10:26.510> the<00:10:27.350> details 00:10:27.699 --> 00:10:27.709 align:start position:0% and the receiver agreeing on the details 00:10:27.709 --> 00:10:29.319 align:start position:0% and the receiver agreeing on the details about<00:10:28.100> the<00:10:28.400> fish<00:10:28.550> so<00:10:28.700> that<00:10:28.850> can<00:10:28.970> be<00:10:29.000> the<00:10:29.120> size 00:10:29.319 --> 00:10:29.329 align:start position:0% about the fish so that can be the size 00:10:29.329 --> 00:10:31.120 align:start position:0% about the fish so that can be the size of<00:10:29.420> the<00:10:29.540> batch<00:10:29.750> in<00:10:30.200> vitro<00:10:30.500> certification 00:10:31.120 --> 00:10:31.130 align:start position:0% of the batch in vitro certification 00:10:31.130 --> 00:10:38.769 align:start position:0% of the batch in vitro certification itself<00:10:31.430> and<00:10:31.940> so<00:10:32.480> on<00:10:36.070> another<00:10:37.390> project<00:10:38.390> that<00:10:38.660> we 00:10:38.769 --> 00:10:38.779 align:start position:0% itself and so on another project that we 00:10:38.779 --> 00:10:42.010 align:start position:0% itself and so on another project that we that<00:10:39.320> we<00:10:39.440> did<00:10:39.650> in<00:10:40.279> supply<00:10:40.670> chains<00:10:40.970> was<00:10:41.300> with 00:10:42.010 --> 00:10:42.020 align:start position:0% that we did in supply chains was with 00:10:42.020 --> 00:10:44.230 align:start position:0% that we did in supply chains was with co-op<00:10:42.380> which<00:10:42.709> is<00:10:42.890> the<00:10:43.100> fifth<00:10:43.760> biggest 00:10:44.230 --> 00:10:44.240 align:start position:0% co-op which is the fifth biggest 00:10:44.240 --> 00:10:47.949 align:start position:0% co-op which is the fifth biggest supermarket<00:10:44.990> chain<00:10:45.200> over<00:10:45.800> in<00:10:45.890> the<00:10:45.980> UK<00:10:46.690> and<00:10:47.690> for 00:10:47.949 --> 00:10:47.959 align:start position:0% supermarket chain over in the UK and for 00:10:47.959 --> 00:10:51.130 align:start position:0% supermarket chain over in the UK and for that<00:10:48.110> we<00:10:48.320> extended<00:10:48.770> our<00:10:49.180> our<00:10:50.180> system<00:10:51.020> our 00:10:51.130 --> 00:10:51.140 align:start position:0% that we extended our our system our 00:10:51.140 --> 00:10:53.560 align:start position:0% that we extended our our system our tracking<00:10:51.470> system<00:10:51.829> to<00:10:52.160> support<00:10:52.970> more<00:10:53.180> features 00:10:53.560 --> 00:10:53.570 align:start position:0% tracking system to support more features 00:10:53.570 --> 00:10:56.400 align:start position:0% tracking system to support more features and<00:10:53.839> such<00:10:54.110> as<00:10:54.350> supporting<00:10:55.070> different<00:10:55.220> units 00:10:56.400 --> 00:10:56.410 align:start position:0% and such as supporting different units 00:10:56.410 --> 00:10:58.720 align:start position:0% and such as supporting different units using<00:10:57.410> ipfs<00:10:58.190> method 00:10:58.720 --> 00:10:58.730 align:start position:0% using ipfs method 00:10:58.730 --> 00:11:01.530 align:start position:0% using ipfs method data<00:10:58.910> on<00:10:59.300> the<00:11:00.019> SS<00:11:00.320> more<00:11:00.529> data<00:11:00.800> on<00:11:00.980> the<00:11:01.130> assets 00:11:01.530 --> 00:11:01.540 align:start position:0% data on the SS more data on the assets 00:11:01.540 --> 00:11:06.480 align:start position:0% data on the SS more data on the assets as<00:11:02.540> well<00:11:02.600> as<00:11:03.970> batching<00:11:04.970> splitting<00:11:05.720> of<00:11:05.839> batches 00:11:06.480 --> 00:11:06.490 align:start position:0% as well as batching splitting of batches 00:11:06.490 --> 00:11:09.000 align:start position:0% as well as batching splitting of batches transformation<00:11:07.490> from<00:11:07.760> one<00:11:08.149> asset<00:11:08.329> to<00:11:08.660> another 00:11:09.000 --> 00:11:09.010 align:start position:0% transformation from one asset to another 00:11:09.010 --> 00:11:11.949 align:start position:0% transformation from one asset to another to<00:11:10.010> have<00:11:10.100> to<00:11:10.399> allow<00:11:10.790> for<00:11:10.820> more<00:11:11.180> flexibility<00:11:11.810> in 00:11:11.949 --> 00:11:11.959 align:start position:0% to have to allow for more flexibility in 00:11:11.959 --> 00:11:15.250 align:start position:0% to have to allow for more flexibility in supply<00:11:12.320> chains<00:11:13.149> so<00:11:14.149> what<00:11:14.300> we<00:11:14.420> did<00:11:14.600> with<00:11:14.810> co-op 00:11:15.250 --> 00:11:15.260 align:start position:0% supply chains so what we did with co-op 00:11:15.260 --> 00:11:18.819 align:start position:0% supply chains so what we did with co-op is<00:11:15.910> and<00:11:16.910> what<00:11:17.060> is<00:11:17.180> interesting<00:11:17.570> in<00:11:18.260> comparison 00:11:18.819 --> 00:11:18.829 align:start position:0% is and what is interesting in comparison 00:11:18.829 --> 00:11:21.910 align:start position:0% is and what is interesting in comparison with<00:11:18.949> the<00:11:19.339> previous<00:11:20.019> example<00:11:21.019> is<00:11:21.649> that<00:11:21.829> we 00:11:21.910 --> 00:11:21.920 align:start position:0% with the previous example is that we 00:11:21.920 --> 00:11:24.400 align:start position:0% with the previous example is that we were<00:11:22.010> focusing<00:11:22.519> on<00:11:22.750> claims<00:11:23.750> of<00:11:23.959> proof<00:11:24.230> of 00:11:24.400 --> 00:11:24.410 align:start position:0% were focusing on claims of proof of 00:11:24.410 --> 00:11:27.540 align:start position:0% were focusing on claims of proof of origin<00:11:24.829> so<00:11:25.010> we<00:11:25.730> were<00:11:25.820> trying<00:11:26.089> to<00:11:26.480> prove<00:11:27.199> that 00:11:27.540 --> 00:11:27.550 align:start position:0% origin so we were trying to prove that 00:11:27.550 --> 00:11:30.009 align:start position:0% origin so we were trying to prove that some<00:11:28.550> products<00:11:28.970> that<00:11:29.000> were<00:11:29.209> sold<00:11:29.510> by<00:11:29.660> a<00:11:29.690> co-op 00:11:30.009 --> 00:11:30.019 align:start position:0% some products that were sold by a co-op 00:11:30.019 --> 00:11:32.170 align:start position:0% some products that were sold by a co-op were<00:11:30.589> actually<00:11:30.949> made<00:11:31.130> in<00:11:31.160> the<00:11:31.339> UK<00:11:31.519> so<00:11:31.910> that<00:11:32.060> was 00:11:32.170 --> 00:11:32.180 align:start position:0% were actually made in the UK so that was 00:11:32.180 --> 00:11:34.030 align:start position:0% were actually made in the UK so that was that<00:11:32.449> was<00:11:32.570> a<00:11:32.600> claim<00:11:32.839> we<00:11:32.930> were<00:11:33.230> going<00:11:33.560> for<00:11:33.740> and 00:11:34.030 --> 00:11:34.040 align:start position:0% that was a claim we were going for and 00:11:34.040 --> 00:11:36.670 align:start position:0% that was a claim we were going for and for<00:11:34.910> that<00:11:35.029> we<00:11:35.209> went<00:11:35.389> in<00:11:35.570> co-op<00:11:36.050> supply<00:11:36.410> chain 00:11:36.670 --> 00:11:36.680 align:start position:0% for that we went in co-op supply chain 00:11:36.680 --> 00:11:40.060 align:start position:0% for that we went in co-op supply chain and<00:11:36.920> and<00:11:37.160> and<00:11:37.459> obviously<00:11:38.389> it<00:11:38.510> was<00:11:38.720> a<00:11:38.750> more<00:11:39.560> it 00:11:40.060 --> 00:11:40.070 align:start position:0% and and and obviously it was a more it 00:11:40.070 --> 00:11:42.550 align:start position:0% and and and obviously it was a more it has<00:11:40.250> some<00:11:40.760> degree<00:11:40.940> of<00:11:41.120> digitalization<00:11:41.690> so 00:11:42.550 --> 00:11:42.560 align:start position:0% has some degree of digitalization so 00:11:42.560 --> 00:11:43.930 align:start position:0% has some degree of digitalization so compared<00:11:42.980> to<00:11:43.010> the<00:11:43.130> previous<00:11:43.370> one<00:11:43.519> where<00:11:43.639> was 00:11:43.930 --> 00:11:43.940 align:start position:0% compared to the previous one where was 00:11:43.940 --> 00:11:46.480 align:start position:0% compared to the previous one where was just<00:11:44.180> normal<00:11:44.480> phones<00:11:44.899> they<00:11:45.740> have<00:11:45.949> air<00:11:46.220> peas 00:11:46.480 --> 00:11:46.490 align:start position:0% just normal phones they have air peas 00:11:46.490 --> 00:11:48.490 align:start position:0% just normal phones they have air peas they<00:11:46.790> have<00:11:47.000> systems<00:11:47.389> in<00:11:47.720> supply<00:11:48.019> chain<00:11:48.230> so 00:11:48.490 --> 00:11:48.500 align:start position:0% they have systems in supply chain so 00:11:48.500 --> 00:11:50.410 align:start position:0% they have systems in supply chain so kind<00:11:49.220> of<00:11:49.279> the<00:11:49.430> challenge<00:11:49.639> and<00:11:49.970> the<00:11:50.060> learnings 00:11:50.410 --> 00:11:50.420 align:start position:0% kind of the challenge and the learnings 00:11:50.420 --> 00:11:51.970 align:start position:0% kind of the challenge and the learnings that<00:11:50.510> we<00:11:50.779> had<00:11:50.959> through<00:11:51.170> this<00:11:51.290> experience<00:11:51.829> is 00:11:51.970 --> 00:11:51.980 align:start position:0% that we had through this experience is 00:11:51.980 --> 00:11:55.240 align:start position:0% that we had through this experience is how<00:11:52.160> to<00:11:52.220> integrate<00:11:52.639> with<00:11:53.000> those<00:11:54.070> with<00:11:55.070> their 00:11:55.240 --> 00:11:55.250 align:start position:0% how to integrate with those with their 00:11:55.250 --> 00:11:59.889 align:start position:0% how to integrate with those with their systems<00:11:55.639> and<00:11:56.260> the<00:11:57.260> result<00:11:57.620> of<00:11:57.740> that<00:11:57.800> was<00:11:58.899> was 00:11:59.889 --> 00:11:59.899 align:start position:0% systems and the result of that was was 00:11:59.899 --> 00:12:01.800 align:start position:0% systems and the result of that was was that<00:11:59.930> we<00:12:00.230> created<00:12:00.649> an<00:12:01.160> interface<00:12:01.760> for 00:12:01.800 --> 00:12:01.810 align:start position:0% that we created an interface for 00:12:01.810 --> 00:12:05.889 align:start position:0% that we created an interface for consumers<00:12:02.810> to<00:12:02.839> access<00:12:03.649> the<00:12:04.310> journey<00:12:04.550> of<00:12:04.899> those 00:12:05.889 --> 00:12:05.899 align:start position:0% consumers to access the journey of those 00:12:05.899 --> 00:12:07.269 align:start position:0% consumers to access the journey of those products<00:12:06.260> so<00:12:06.290> in<00:12:06.410> this<00:12:06.589> case<00:12:06.769> it<00:12:06.949> was<00:12:07.069> about 00:12:07.269 --> 00:12:07.279 align:start position:0% products so in this case it was about 00:12:07.279 --> 00:12:10.629 align:start position:0% products so in this case it was about flowers<00:12:07.790> but<00:12:08.000> we<00:12:08.120> also<00:12:09.459> considered<00:12:10.459> other 00:12:10.629 --> 00:12:10.639 align:start position:0% flowers but we also considered other 00:12:10.639 --> 00:12:15.340 align:start position:0% flowers but we also considered other products<00:12:11.569> and<00:12:11.800> we<00:12:12.800> integrated<00:12:13.670> that<00:12:13.970> in<00:12:14.389> to 00:12:15.340 --> 00:12:15.350 align:start position:0% products and we integrated that in to 00:12:15.350 --> 00:12:19.150 align:start position:0% products and we integrated that in to the<00:12:15.860> coop<00:12:16.819> consumer<00:12:17.269> app<00:12:17.449> so<00:12:17.930> that<00:12:18.160> consumer 00:12:19.150 --> 00:12:19.160 align:start position:0% the coop consumer app so that consumer 00:12:19.160 --> 00:12:23.530 align:start position:0% the coop consumer app so that consumer can<00:12:19.310> directly<00:12:21.190> discover<00:12:22.190> this<00:12:22.399> and<00:12:22.850> explore 00:12:23.530 --> 00:12:23.540 align:start position:0% can directly discover this and explore 00:12:23.540 --> 00:12:26.470 align:start position:0% can directly discover this and explore the<00:12:23.990> the<00:12:24.470> journey<00:12:24.709> of<00:12:25.120> the<00:12:26.120> products<00:12:26.449> that 00:12:26.470 --> 00:12:26.480 align:start position:0% the the journey of the products that 00:12:26.480 --> 00:12:30.129 align:start position:0% the the journey of the products that were<00:12:26.630> being<00:12:26.839> sold<00:12:28.300> so<00:12:29.300> the<00:12:29.329> next<00:12:29.630> the<00:12:29.959> next 00:12:30.129 --> 00:12:30.139 align:start position:0% were being sold so the next the next 00:12:30.139 --> 00:12:32.590 align:start position:0% were being sold so the next the next question<00:12:30.529> that<00:12:30.560> we<00:12:30.980> asked<00:12:31.250> was<00:12:31.430> how<00:12:31.880> how<00:12:32.540> we 00:12:32.590 --> 00:12:32.600 align:start position:0% question that we asked was how how we 00:12:32.600 --> 00:12:36.610 align:start position:0% question that we asked was how how we can<00:12:33.760> incentivize<00:12:34.760> good<00:12:35.060> behavior<00:12:35.810> in<00:12:36.410> this 00:12:36.610 --> 00:12:36.620 align:start position:0% can incentivize good behavior in this 00:12:36.620 --> 00:12:38.829 align:start position:0% can incentivize good behavior in this system<00:12:36.800> is<00:12:37.399> I'm<00:12:37.579> sure<00:12:37.819> most<00:12:38.060> of<00:12:38.209> you<00:12:38.329> recognize 00:12:38.829 --> 00:12:38.839 align:start position:0% system is I'm sure most of you recognize 00:12:38.839 --> 00:12:43.569 align:start position:0% system is I'm sure most of you recognize that<00:12:38.870> it's<00:12:39.410> it's<00:12:39.709> not<00:12:39.949> a<00:12:40.010> completely<00:12:42.579> trust 00:12:43.569 --> 00:12:43.579 align:start position:0% that it's it's not a completely trust 00:12:43.579 --> 00:12:45.340 align:start position:0% that it's it's not a completely trust the<00:12:43.730> system<00:12:44.149> and<00:12:44.389> and<00:12:44.600> and<00:12:44.839> they<00:12:45.050> can<00:12:45.110> be 00:12:45.340 --> 00:12:45.350 align:start position:0% the system and and and they can be 00:12:45.350 --> 00:12:49.660 align:start position:0% the system and and and they can be breeches<00:12:46.279> and<00:12:46.550> and<00:12:46.850> and<00:12:47.149> and<00:12:47.750> honest<00:12:48.670> players 00:12:49.660 --> 00:12:49.670 align:start position:0% breeches and and and and honest players 00:12:49.670 --> 00:12:53.170 align:start position:0% breeches and and and and honest players and<00:12:50.000> what<00:12:50.899> we<00:12:50.990> recognize<00:12:51.410> is<00:12:51.649> that<00:12:52.180> linking 00:12:53.170 --> 00:12:53.180 align:start position:0% and what we recognize is that linking 00:12:53.180 --> 00:12:56.410 align:start position:0% and what we recognize is that linking this<00:12:54.019> infrastructure<00:12:54.980> for<00:12:55.220> trusts<00:12:55.670> with<00:12:56.209> the 00:12:56.410 --> 00:12:56.420 align:start position:0% this infrastructure for trusts with the 00:12:56.420 --> 00:12:57.670 align:start position:0% this infrastructure for trusts with the incentives<00:12:56.870> of<00:12:56.959> supply<00:12:57.260> chain<00:12:57.500> especially 00:12:57.670 --> 00:12:57.680 align:start position:0% incentives of supply chain especially 00:12:57.680 --> 00:13:01.949 align:start position:0% incentives of supply chain especially financial<00:12:58.639> incentives<00:12:59.120> could<00:13:00.019> be<00:13:00.199> a<00:13:00.230> way<00:13:00.470> to 00:13:01.949 --> 00:13:01.959 align:start position:0% financial incentives could be a way to 00:13:01.959 --> 00:13:04.990 align:start position:0% financial incentives could be a way to incentivize<00:13:02.959> good<00:13:03.410> behavior<00:13:03.829> so<00:13:04.610> kind<00:13:04.819> of<00:13:04.910> the 00:13:04.990 --> 00:13:05.000 align:start position:0% incentivize good behavior so kind of the 00:13:05.000 --> 00:13:09.360 align:start position:0% incentivize good behavior so kind of the MVP<00:13:05.360> version<00:13:05.870> of<00:13:05.990> that<00:13:06.170> that<00:13:06.980> we<00:13:07.899> developed 00:13:09.360 --> 00:13:09.370 align:start position:0% MVP version of that that we developed 00:13:09.370 --> 00:13:12.100 align:start position:0% MVP version of that that we developed recently<00:13:10.370> was<00:13:11.089> in<00:13:11.300> the<00:13:11.600> frame 00:13:12.100 --> 00:13:12.110 align:start position:0% recently was in the frame 00:13:12.110 --> 00:13:14.620 align:start position:0% recently was in the frame a<00:13:12.500> collaboration<00:13:13.459> that<00:13:13.760> we<00:13:13.940> did<00:13:14.089> with<00:13:14.269> a<00:13:14.300> Dutch 00:13:14.620 --> 00:13:14.630 align:start position:0% a collaboration that we did with a Dutch 00:13:14.630 --> 00:13:18.280 align:start position:0% a collaboration that we did with a Dutch NGO<00:13:15.079> called<00:13:15.320> Fairfield<00:13:16.360> so<00:13:17.360> in<00:13:17.570> this<00:13:17.720> case<00:13:17.959> we 00:13:18.280 --> 00:13:18.290 align:start position:0% NGO called Fairfield so in this case we 00:13:18.290 --> 00:13:21.639 align:start position:0% NGO called Fairfield so in this case we were<00:13:18.380> focusing<00:13:18.860> on<00:13:20.019> coconut<00:13:21.019> supply<00:13:21.380> chains 00:13:21.639 --> 00:13:21.649 align:start position:0% were focusing on coconut supply chains 00:13:21.649 --> 00:13:25.449 align:start position:0% were focusing on coconut supply chains in<00:13:22.029> Indonesia<00:13:23.029> so<00:13:23.329> again<00:13:23.570> Indonesia<00:13:24.279> and<00:13:25.279> the 00:13:25.449 --> 00:13:25.459 align:start position:0% in Indonesia so again Indonesia and the 00:13:25.459 --> 00:13:27.190 align:start position:0% in Indonesia so again Indonesia and the claim<00:13:25.730> that<00:13:25.760> we<00:13:26.149> were<00:13:26.269> trying<00:13:26.480> to<00:13:26.720> prove<00:13:26.959> was 00:13:27.190 --> 00:13:27.200 align:start position:0% claim that we were trying to prove was 00:13:27.200 --> 00:13:30.310 align:start position:0% claim that we were trying to prove was the<00:13:27.320> fair<00:13:27.560> payments<00:13:28.130> to<00:13:28.700> the<00:13:28.820> farmer<00:13:29.209> at<00:13:30.140> the 00:13:30.310 --> 00:13:30.320 align:start position:0% the fair payments to the farmer at the 00:13:30.320 --> 00:13:34.630 align:start position:0% the fair payments to the farmer at the first<00:13:30.529> stage<00:13:31.370> of<00:13:31.670> the<00:13:32.089> of<00:13:32.360> the<00:13:32.480> chain<00:13:32.690> so<00:13:33.640> I'm 00:13:34.630 --> 00:13:34.640 align:start position:0% first stage of the of the chain so I'm 00:13:34.640 --> 00:13:36.160 align:start position:0% first stage of the of the chain so I'm sure<00:13:34.850> you're<00:13:35.000> familiar<00:13:35.149> with<00:13:35.390> the<00:13:35.720> concept<00:13:35.839> of 00:13:36.160 --> 00:13:36.170 align:start position:0% sure you're familiar with the concept of 00:13:36.170 --> 00:13:38.530 align:start position:0% sure you're familiar with the concept of fair<00:13:37.100> trade<00:13:37.370> but<00:13:37.579> in<00:13:37.700> this<00:13:37.820> case<00:13:38.029> we're<00:13:38.240> trying 00:13:38.530 --> 00:13:38.540 align:start position:0% fair trade but in this case we're trying 00:13:38.540 --> 00:13:42.000 align:start position:0% fair trade but in this case we're trying to<00:13:38.690> do<00:13:38.810> it<00:13:38.930> in<00:13:39.079> a<00:13:39.310> completely<00:13:40.360> real-time<00:13:41.360> way 00:13:42.000 --> 00:13:42.010 align:start position:0% to do it in a completely real-time way 00:13:42.010 --> 00:13:46.060 align:start position:0% to do it in a completely real-time way improved<00:13:43.010> on<00:13:43.700> chain<00:13:44.570> so<00:13:45.320> the<00:13:45.440> way<00:13:45.560> it<00:13:45.680> happened 00:13:46.060 --> 00:13:46.070 align:start position:0% improved on chain so the way it happened 00:13:46.070 --> 00:13:49.360 align:start position:0% improved on chain so the way it happened is<00:13:46.250> that<00:13:46.899> we<00:13:47.899> provided<00:13:48.470> again<00:13:48.860> an<00:13:49.010> interface 00:13:49.360 --> 00:13:49.370 align:start position:0% is that we provided again an interface 00:13:49.370 --> 00:13:51.180 align:start position:0% is that we provided again an interface through<00:13:49.640> SMS<00:13:50.060> services<00:13:50.450> because<00:13:50.690> again 00:13:51.180 --> 00:13:51.190 align:start position:0% through SMS services because again 00:13:51.190 --> 00:13:53.319 align:start position:0% through SMS services because again people<00:13:52.190> didn't<00:13:52.459> have<00:13:52.579> access<00:13:52.760> to<00:13:52.970> smart 00:13:53.319 --> 00:13:53.329 align:start position:0% people didn't have access to smart 00:13:53.329 --> 00:13:56.860 align:start position:0% people didn't have access to smart phones<00:13:53.570> where<00:13:53.720> we<00:13:53.839> were<00:13:54.070> operating<00:13:55.070> and<00:13:55.870> we 00:13:56.860 --> 00:13:56.870 align:start position:0% phones where we were operating and we 00:13:56.870 --> 00:13:59.440 align:start position:0% phones where we were operating and we were<00:13:56.959> enabling<00:13:57.500> farmers<00:13:57.950> to<00:13:58.370> register<00:13:58.880> the 00:13:59.440 --> 00:13:59.450 align:start position:0% were enabling farmers to register the 00:13:59.450 --> 00:14:02.170 align:start position:0% were enabling farmers to register the coconuts<00:13:59.870> that<00:13:59.990> they<00:14:00.140> had<00:14:00.380> harvested<00:14:00.890> and<00:14:01.339> as 00:14:02.170 --> 00:14:02.180 align:start position:0% coconuts that they had harvested and as 00:14:02.180 --> 00:14:04.900 align:start position:0% coconuts that they had harvested and as as<00:14:02.510> a<00:14:02.570> batch<00:14:02.839> and<00:14:03.430> then<00:14:04.430> some<00:14:04.730> of<00:14:04.820> the 00:14:04.900 --> 00:14:04.910 align:start position:0% as a batch and then some of the 00:14:04.910 --> 00:14:07.690 align:start position:0% as a batch and then some of the handshakes<00:14:05.390> in<00:14:05.630> the<00:14:05.810> supply<00:14:06.079> chain<00:14:06.550> needed<00:14:07.550> a 00:14:07.690 --> 00:14:07.700 align:start position:0% handshakes in the supply chain needed a 00:14:07.700 --> 00:14:11.019 align:start position:0% handshakes in the supply chain needed a proof<00:14:07.910> of<00:14:08.029> payment<00:14:08.240> to<00:14:09.200> actually<00:14:09.680> happen<00:14:10.029> and 00:14:11.019 --> 00:14:11.029 align:start position:0% proof of payment to actually happen and 00:14:11.029 --> 00:14:13.300 align:start position:0% proof of payment to actually happen and the<00:14:11.209> way<00:14:11.329> that<00:14:11.630> happened<00:14:12.589> in<00:14:12.740> practice<00:14:12.950> is 00:14:13.300 --> 00:14:13.310 align:start position:0% the way that happened in practice is 00:14:13.310 --> 00:14:15.519 align:start position:0% the way that happened in practice is that<00:14:13.550> whenever<00:14:14.450> the<00:14:14.779> next<00:14:14.959> actor<00:14:15.350> in<00:14:15.440> the 00:14:15.519 --> 00:14:15.529 align:start position:0% that whenever the next actor in the 00:14:15.529 --> 00:14:17.470 align:start position:0% that whenever the next actor in the chain<00:14:15.740> so<00:14:16.010> that<00:14:16.160> was<00:14:16.339> the<00:14:16.760> trader<00:14:17.029> that<00:14:17.149> came 00:14:17.470 --> 00:14:17.480 align:start position:0% chain so that was the trader that came 00:14:17.480 --> 00:14:19.560 align:start position:0% chain so that was the trader that came just<00:14:17.720> after<00:14:17.899> the<00:14:18.170> farmer<00:14:18.500> that<00:14:18.589> harvested 00:14:19.560 --> 00:14:19.570 align:start position:0% just after the farmer that harvested 00:14:19.570 --> 00:14:22.300 align:start position:0% just after the farmer that harvested requested<00:14:20.570> ownership<00:14:21.170> of<00:14:21.380> a<00:14:22.040> particular 00:14:22.300 --> 00:14:22.310 align:start position:0% requested ownership of a particular 00:14:22.310 --> 00:14:27.130 align:start position:0% requested ownership of a particular asset<00:14:22.640> the<00:14:24.010> the<00:14:25.010> farmer<00:14:25.459> would<00:14:26.180> get<00:14:26.690> an<00:14:26.839> SMS 00:14:27.130 --> 00:14:27.140 align:start position:0% asset the the farmer would get an SMS 00:14:27.140 --> 00:14:29.259 align:start position:0% asset the the farmer would get an SMS asking<00:14:28.040> them<00:14:28.190> if<00:14:28.310> they<00:14:28.430> got<00:14:28.610> a<00:14:28.670> particular 00:14:29.259 --> 00:14:29.269 align:start position:0% asking them if they got a particular 00:14:29.269 --> 00:14:31.090 align:start position:0% asking them if they got a particular amount<00:14:29.570> that<00:14:30.170> verse<00:14:30.440> that<00:14:30.680> they<00:14:31.010> were 00:14:31.090 --> 00:14:31.100 align:start position:0% amount that verse that they were 00:14:31.100 --> 00:14:32.620 align:start position:0% amount that verse that they were supposed<00:14:31.519> to<00:14:31.579> have<00:14:32.000> got<00:14:32.240> because<00:14:32.540> it's 00:14:32.620 --> 00:14:32.630 align:start position:0% supposed to have got because it's 00:14:32.630 --> 00:14:37.740 align:start position:0% supposed to have got because it's supposed<00:14:32.870> to<00:14:32.930> be<00:14:33.640> basically<00:14:34.640> an<00:14:35.329> exchange<00:14:35.779> and 00:14:37.740 --> 00:14:37.750 align:start position:0% supposed to be basically an exchange and 00:14:37.750 --> 00:14:42.850 align:start position:0% supposed to be basically an exchange and depending<00:14:38.750> on<00:14:38.839> the<00:14:38.959> answer<00:14:39.260> that<00:14:41.529> the<00:14:42.529> farmer 00:14:42.850 --> 00:14:42.860 align:start position:0% depending on the answer that the farmer 00:14:42.860 --> 00:14:45.009 align:start position:0% depending on the answer that the farmer would<00:14:43.010> provide<00:14:43.370> to<00:14:43.640> this<00:14:43.730> question<00:14:44.149> the 00:14:45.009 --> 00:14:45.019 align:start position:0% would provide to this question the 00:14:45.019 --> 00:14:49.139 align:start position:0% would provide to this question the transfer<00:14:45.410> would<00:14:45.800> complete<00:14:46.699> or<00:14:46.910> be<00:14:47.750> rejected 00:14:49.139 --> 00:14:49.149 align:start position:0% transfer would complete or be rejected 00:14:49.149 --> 00:14:52.210 align:start position:0% transfer would complete or be rejected so<00:14:50.149> in<00:14:50.510> terms<00:14:50.690> of<00:14:50.839> the<00:14:50.990> amount<00:14:51.290> that<00:14:51.500> was<00:14:51.949> in 00:14:52.210 --> 00:14:52.220 align:start position:0% so in terms of the amount that was in 00:14:52.220 --> 00:14:55.090 align:start position:0% so in terms of the amount that was in this<00:14:52.430> message<00:14:52.910> the<00:14:53.420> amount<00:14:53.690> was<00:14:54.100> determined 00:14:55.090 --> 00:14:55.100 align:start position:0% this message the amount was determined 00:14:55.100 --> 00:14:59.069 align:start position:0% this message the amount was determined by<00:14:55.540> fair<00:14:56.540> food<00:14:56.750> which<00:14:57.260> was<00:14:57.410> this<00:14:57.529> NGO<00:14:57.920> based<00:14:58.519> on 00:14:59.069 --> 00:14:59.079 align:start position:0% by fair food which was this NGO based on 00:14:59.079 --> 00:15:02.560 align:start position:0% by fair food which was this NGO based on a<00:15:00.079> standard<00:15:00.980> of<00:15:01.250> living<00:15:01.610> income<00:15:02.089> so<00:15:02.480> it 00:15:02.560 --> 00:15:02.570 align:start position:0% a standard of living income so it 00:15:02.570 --> 00:15:05.439 align:start position:0% a standard of living income so it dependent<00:15:02.990> on<00:15:03.820> different<00:15:04.820> parameters 00:15:05.439 --> 00:15:05.449 align:start position:0% dependent on different parameters 00:15:05.449 --> 00:15:07.420 align:start position:0% dependent on different parameters including<00:15:06.050> the<00:15:06.620> size<00:15:06.829> of<00:15:06.949> the<00:15:07.040> batch<00:15:07.190> of 00:15:07.420 --> 00:15:07.430 align:start position:0% including the size of the batch of 00:15:07.430 --> 00:15:11.949 align:start position:0% including the size of the batch of coconuts<00:15:07.820> obviously<00:15:09.519> and<00:15:10.660> what<00:15:11.660> was<00:15:11.839> quite 00:15:11.949 --> 00:15:11.959 align:start position:0% coconuts obviously and what was quite 00:15:11.959 --> 00:15:14.290 align:start position:0% coconuts obviously and what was quite interesting<00:15:12.560> in<00:15:12.680> this<00:15:12.829> case<00:15:13.100> is<00:15:13.850> that<00:15:14.060> we<00:15:14.209> were 00:15:14.290 --> 00:15:14.300 align:start position:0% interesting in this case is that we were 00:15:14.300 --> 00:15:15.850 align:start position:0% interesting in this case is that we were trying<00:15:14.480> to<00:15:14.779> see<00:15:15.260> if<00:15:15.380> we<00:15:15.529> could<00:15:15.680> have<00:15:15.829> some 00:15:15.850 --> 00:15:15.860 align:start position:0% trying to see if we could have some 00:15:15.860 --> 00:15:17.889 align:start position:0% trying to see if we could have some impact<00:15:16.459> on<00:15:16.550> the<00:15:16.699> supply<00:15:17.089> chain<00:15:17.269> itself<00:15:17.570> and 00:15:17.889 --> 00:15:17.899 align:start position:0% impact on the supply chain itself and 00:15:17.899 --> 00:15:19.780 align:start position:0% impact on the supply chain itself and actually<00:15:18.350> among 00:15:19.780 --> 00:15:19.790 align:start position:0% actually among 00:15:19.790 --> 00:15:24.180 align:start position:0% actually among the<00:15:19.940> set<00:15:20.600> of<00:15:20.750> farmers<00:15:21.110> that<00:15:21.140> we<00:15:22.480> considered<00:15:23.480> a 00:15:24.180 --> 00:15:24.190 align:start position:0% the set of farmers that we considered a 00:15:24.190 --> 00:15:29.290 align:start position:0% the set of farmers that we considered a few<00:15:25.190> of<00:15:25.340> them<00:15:25.520> actually<00:15:27.400> answer<00:15:28.400> no<00:15:28.730> to<00:15:28.790> the 00:15:29.290 --> 00:15:29.300 align:start position:0% few of them actually answer no to the 00:15:29.300 --> 00:15:31.540 align:start position:0% few of them actually answer no to the question<00:15:29.630> from<00:15:29.720> the<00:15:29.930> SMS<00:15:30.440> and<00:15:30.560> when<00:15:30.710> we<00:15:30.860> when 00:15:31.540 --> 00:15:31.550 align:start position:0% question from the SMS and when we when 00:15:31.550 --> 00:15:34.420 align:start position:0% question from the SMS and when we when we<00:15:31.580> investigated<00:15:32.420> it<00:15:33.230> appeared<00:15:33.560> that<00:15:33.650> some<00:15:34.340> of 00:15:34.420 --> 00:15:34.430 align:start position:0% we investigated it appeared that some of 00:15:34.430 --> 00:15:36.280 align:start position:0% we investigated it appeared that some of the<00:15:34.520> farmers<00:15:34.820> were<00:15:35.000> actually<00:15:35.420> only<00:15:35.720> being 00:15:36.280 --> 00:15:36.290 align:start position:0% the farmers were actually only being 00:15:36.290 --> 00:15:38.980 align:start position:0% the farmers were actually only being paid<00:15:36.500> a<00:15:36.860> small<00:15:37.190> deposit<00:15:37.640> on<00:15:37.970> their<00:15:38.330> own<00:15:38.660> their 00:15:38.980 --> 00:15:38.990 align:start position:0% paid a small deposit on their own their 00:15:38.990 --> 00:15:41.920 align:start position:0% paid a small deposit on their own their harvest<00:15:39.490> and<00:15:40.490> actually<00:15:40.820> the<00:15:41.030> fact<00:15:41.300> that<00:15:41.420> the 00:15:41.920 --> 00:15:41.930 align:start position:0% harvest and actually the fact that the 00:15:41.930 --> 00:15:44.920 align:start position:0% harvest and actually the fact that the system<00:15:42.110> was<00:15:42.500> in<00:15:42.560> place<00:15:42.980> and<00:15:43.310> and<00:15:43.670> that<00:15:43.850> the<00:15:44.690> the 00:15:44.920 --> 00:15:44.930 align:start position:0% system was in place and and that the the 00:15:44.930 --> 00:15:47.560 align:start position:0% system was in place and and that the the transfer<00:15:45.290> couldn't<00:15:45.590> be<00:15:45.650> completed<00:15:46.120> led<00:15:47.120> to 00:15:47.560 --> 00:15:47.570 align:start position:0% transfer couldn't be completed led to 00:15:47.570 --> 00:15:51.190 align:start position:0% transfer couldn't be completed led to the<00:15:48.200> actual<00:15:48.530> payment<00:15:48.980> to<00:15:49.880> be<00:15:49.970> to<00:15:50.300> be<00:15:50.690> made<00:15:50.990> in 00:15:51.190 --> 00:15:51.200 align:start position:0% the actual payment to be to be made in 00:15:51.200 --> 00:15:55.120 align:start position:0% the actual payment to be to be made in info<00:15:52.780> so<00:15:53.780> it<00:15:53.840> was<00:15:54.140> it<00:15:54.380> was<00:15:54.470> the<00:15:54.560> first<00:15:54.950> sign 00:15:55.120 --> 00:15:55.130 align:start position:0% info so it was it was the first sign 00:15:55.130 --> 00:15:57.640 align:start position:0% info so it was it was the first sign that<00:15:55.190> we<00:15:55.490> can<00:15:55.910> have<00:15:56.060> an<00:15:56.300> impact<00:15:56.450> on<00:15:56.690> how<00:15:56.930> supply 00:15:57.640 --> 00:15:57.650 align:start position:0% that we can have an impact on how supply 00:15:57.650 --> 00:16:00.910 align:start position:0% that we can have an impact on how supply chains<00:15:57.920> operate<00:15:59.170> so<00:16:00.170> I<00:16:00.200> will<00:16:00.500> see<00:16:00.650> that's 00:16:00.910 --> 00:16:00.920 align:start position:0% chains operate so I will see that's 00:16:00.920 --> 00:16:05.080 align:start position:0% chains operate so I will see that's that's<00:16:01.220> still<00:16:02.470> kind<00:16:03.470> of<00:16:03.530> a<00:16:03.700> first<00:16:04.700> first 00:16:05.080 --> 00:16:05.090 align:start position:0% that's still kind of a first first 00:16:05.090 --> 00:16:08.230 align:start position:0% that's still kind of a first first iteration<00:16:05.660> on<00:16:05.810> how<00:16:06.020> we<00:16:06.080> could<00:16:06.610> connect<00:16:07.610> this 00:16:08.230 --> 00:16:08.240 align:start position:0% iteration on how we could connect this 00:16:08.240 --> 00:16:14.560 align:start position:0% iteration on how we could connect this set<00:16:08.630> of<00:16:09.520> claims<00:16:10.520> to<00:16:11.650> fire<00:16:12.650> to<00:16:12.890> to<00:16:13.570> incentives 00:16:14.560 --> 00:16:14.570 align:start position:0% set of claims to fire to to incentives 00:16:14.570 --> 00:16:16.990 align:start position:0% set of claims to fire to to incentives and<00:16:14.690> supply<00:16:15.020> chains<00:16:15.400> and<00:16:16.400> what<00:16:16.670> we<00:16:16.940> are 00:16:16.990 --> 00:16:17.000 align:start position:0% and supply chains and what we are 00:16:17.000 --> 00:16:19.990 align:start position:0% and supply chains and what we are starting<00:16:17.360> to<00:16:17.690> also<00:16:18.290> look<00:16:18.440> at<00:16:18.650> now<00:16:18.980> as<00:16:19.370> a<00:16:19.670> next 00:16:19.990 --> 00:16:20.000 align:start position:0% starting to also look at now as a next 00:16:20.000 --> 00:16:22.750 align:start position:0% starting to also look at now as a next iteration<00:16:20.120> of<00:16:20.600> that<00:16:20.660> is<00:16:21.050> how<00:16:21.560> we<00:16:22.190> can<00:16:22.370> connect 00:16:22.750 --> 00:16:22.760 align:start position:0% iteration of that is how we can connect 00:16:22.760 --> 00:16:25.840 align:start position:0% iteration of that is how we can connect our<00:16:23.230> system<00:16:24.230> with<00:16:24.620> trade<00:16:25.040> finance<00:16:25.460> and 00:16:25.840 --> 00:16:25.850 align:start position:0% our system with trade finance and 00:16:25.850 --> 00:16:30.130 align:start position:0% our system with trade finance and insurance<00:16:26.350> so<00:16:27.350> that<00:16:27.670> as<00:16:28.670> a<00:16:28.730> business<00:16:29.140> any 00:16:30.130 --> 00:16:30.140 align:start position:0% insurance so that as a business any 00:16:30.140 --> 00:16:33.490 align:start position:0% insurance so that as a business any transparency<00:16:30.800> that<00:16:31.700> any<00:16:32.690> transparency<00:16:33.320> and 00:16:33.490 --> 00:16:33.500 align:start position:0% transparency that any transparency and 00:16:33.500 --> 00:16:35.830 align:start position:0% transparency that any transparency and claims<00:16:33.950> that<00:16:34.070> you<00:16:34.340> make<00:16:34.520> that<00:16:35.150> make<00:16:35.330> your 00:16:35.830 --> 00:16:35.840 align:start position:0% claims that you make that make your 00:16:35.840 --> 00:16:38.110 align:start position:0% claims that you make that make your product<00:16:36.350> more<00:16:36.470> transparent<00:16:37.070> should<00:16:37.760> be 00:16:38.110 --> 00:16:38.120 align:start position:0% product more transparent should be 00:16:38.120 --> 00:16:40.150 align:start position:0% product more transparent should be rewarded<00:16:38.660> in<00:16:38.780> terms<00:16:38.810> of<00:16:39.230> better<00:16:39.680> access<00:16:40.130> to 00:16:40.150 --> 00:16:40.160 align:start position:0% rewarded in terms of better access to 00:16:40.160 --> 00:16:42.630 align:start position:0% rewarded in terms of better access to capital<00:16:40.460> or<00:16:40.880> cheaper<00:16:41.780> access<00:16:41.930> to<00:16:42.200> insurance 00:16:42.630 --> 00:16:42.640 align:start position:0% capital or cheaper access to insurance 00:16:42.640 --> 00:16:46.270 align:start position:0% capital or cheaper access to insurance and<00:16:43.640> so<00:16:43.820> on<00:16:43.970> so<00:16:44.780> we're<00:16:44.930> going<00:16:45.050> to<00:16:45.140> be<00:16:45.280> starting 00:16:46.270 --> 00:16:46.280 align:start position:0% and so on so we're going to be starting 00:16:46.280 --> 00:16:47.830 align:start position:0% and so on so we're going to be starting some<00:16:46.430> projects<00:16:46.820> on<00:16:46.910> that<00:16:47.090> and<00:16:47.300> we'll<00:16:47.540> sure 00:16:47.830 --> 00:16:47.840 align:start position:0% some projects on that and we'll sure 00:16:47.840 --> 00:16:49.960 align:start position:0% some projects on that and we'll sure have<00:16:48.200> some<00:16:48.560> announcement<00:16:49.010> and<00:16:49.250> announcements 00:16:49.960 --> 00:16:49.970 align:start position:0% have some announcement and announcements 00:16:49.970 --> 00:16:55.810 align:start position:0% have some announcement and announcements to<00:16:50.750> make<00:16:50.780> on<00:16:51.170> on<00:16:51.500> that<00:16:51.710> soon<00:16:53.890> so<00:16:54.890> yeah<00:16:55.580> that<00:16:55.730> was 00:16:55.810 --> 00:16:55.820 align:start position:0% to make on on that soon so yeah that was 00:16:55.820 --> 00:16:58.320 align:start position:0% to make on on that soon so yeah that was that<00:16:56.060> was<00:16:56.420> pretty<00:16:56.450> much<00:16:56.840> what<00:16:57.440> we've<00:16:57.650> going 00:16:58.320 --> 00:16:58.330 align:start position:0% that was pretty much what we've going 00:16:58.330 --> 00:17:01.510 align:start position:0% that was pretty much what we've going what<00:16:59.330> we've<00:16:59.480> been<00:16:59.660> doing<00:17:00.020> in<00:17:00.650> in<00:17:00.950> in<00:17:01.220> the<00:17:01.310> past 00:17:01.510 --> 00:17:01.520 align:start position:0% what we've been doing in in in the past 00:17:01.520 --> 00:17:05.380 align:start position:0% what we've been doing in in in the past month<00:17:01.850> and<00:17:02.890> yeah<00:17:03.890> please<00:17:04.730> reach<00:17:05.000> out<00:17:05.120> to<00:17:05.300> me 00:17:05.380 --> 00:17:05.390 align:start position:0% month and yeah please reach out to me 00:17:05.390 --> 00:17:07.490 align:start position:0% month and yeah please reach out to me thank<00:17:05.780> you<00:17:05.870> very<00:17:05.990> much<00:17:06.140> for<00:17:06.290> your<00:17:06.380> attention 00:17:07.490 --> 00:17:07.500 align:start position:0% thank you very much for your attention 00:17:07.500 --> 00:17:14.900 align:start position:0% thank you very much for your attention [Applause] 00:17:14.900 --> 00:17:14.910 align:start position:0% [Applause] 00:17:14.910 --> 00:17:22.489 align:start position:0% [Applause] [Music]