WEBVTT
Kind: captions
Language: en

00:00:01.160 --> 00:00:06.690 align:start position:0%
 
[Music]

00:00:06.690 --> 00:00:06.700 align:start position:0%
 
 

00:00:06.700 --> 00:00:12.509 align:start position:0%
 
[Music]

00:00:12.509 --> 00:00:12.519 align:start position:0%
 
 

00:00:12.519 --> 00:00:16.390 align:start position:0%
 
well<00:00:13.519><c> hello</c><00:00:13.960><c> everyone</c><00:00:14.920><c> my</c><00:00:15.080><c> name</c><00:00:15.240><c> is</c><00:00:15.400><c> R</c><00:00:16.000><c> I'm</c><00:00:16.240><c> a</c>

00:00:16.390 --> 00:00:16.400 align:start position:0%
well hello everyone my name is R I'm a
 

00:00:16.400 --> 00:00:19.429 align:start position:0%
well hello everyone my name is R I'm a
software<00:00:16.760><c> engineer</c><00:00:17.160><c> at</c><00:00:17.320><c> box</c><00:00:17.680><c> Scout</c><00:00:18.680><c> and</c><00:00:19.199><c> uh</c>

00:00:19.429 --> 00:00:19.439 align:start position:0%
software engineer at box Scout and uh
 

00:00:19.439 --> 00:00:21.710 align:start position:0%
software engineer at box Scout and uh
which<00:00:19.560><c> is</c><00:00:19.720><c> an</c><00:00:19.880><c> open</c><00:00:20.119><c> source</c><00:00:20.400><c> box</c><00:00:20.960><c> Explorer</c><00:00:21.560><c> and</c>

00:00:21.710 --> 00:00:21.720 align:start position:0%
which is an open source box Explorer and
 

00:00:21.720 --> 00:00:23.870 align:start position:0%
which is an open source box Explorer and
today<00:00:22.359><c> I</c><00:00:22.439><c> want</c><00:00:22.600><c> to</c><00:00:22.760><c> invite</c><00:00:23.000><c> you</c><00:00:23.160><c> to</c><00:00:23.480><c> try</c><00:00:23.680><c> to</c>

00:00:23.870 --> 00:00:23.880 align:start position:0%
today I want to invite you to try to
 

00:00:23.880 --> 00:00:26.870 align:start position:0%
today I want to invite you to try to
verify<00:00:24.599><c> a</c><00:00:24.760><c> couple</c><00:00:25.000><c> of</c><00:00:25.119><c> contracts</c><00:00:25.720><c> along</c><00:00:26.039><c> with</c>

00:00:26.870 --> 00:00:26.880 align:start position:0%
verify a couple of contracts along with
 

00:00:26.880 --> 00:00:30.509 align:start position:0%
verify a couple of contracts along with
me<00:00:27.880><c> uh</c><00:00:28.199><c> let's</c><00:00:28.439><c> start</c><00:00:28.840><c> with</c>

00:00:30.509 --> 00:00:30.519 align:start position:0%
me uh let's start with
 

00:00:30.519 --> 00:00:32.950 align:start position:0%
me uh let's start with
answering<00:00:31.000><c> the</c><00:00:31.320><c> question</c><00:00:32.320><c> what</c><00:00:32.480><c> the</c><00:00:32.599><c> contract</c>

00:00:32.950 --> 00:00:32.960 align:start position:0%
answering the question what the contract
 

00:00:32.960 --> 00:00:35.190 align:start position:0%
answering the question what the contract
verification<00:00:33.600><c> is</c><00:00:34.160><c> when</c><00:00:34.320><c> you</c><00:00:34.480><c> deploy</c><00:00:34.960><c> the</c>

00:00:35.190 --> 00:00:35.200 align:start position:0%
verification is when you deploy the
 

00:00:35.200 --> 00:00:38.190 align:start position:0%
verification is when you deploy the
contract<00:00:36.079><c> uh</c><00:00:36.239><c> onto</c><00:00:36.520><c> the</c><00:00:36.800><c> chain</c><00:00:37.800><c> it</c><00:00:37.960><c> is</c>

00:00:38.190 --> 00:00:38.200 align:start position:0%
contract uh onto the chain it is
 

00:00:38.200 --> 00:00:41.029 align:start position:0%
contract uh onto the chain it is
represented<00:00:38.800><c> as</c><00:00:39.040><c> a</c><00:00:39.360><c> number</c><00:00:39.640><c> of</c><00:00:39.840><c> bytes</c><00:00:40.559><c> which</c>

00:00:41.029 --> 00:00:41.039 align:start position:0%
represented as a number of bytes which
 

00:00:41.039 --> 00:00:44.430 align:start position:0%
represented as a number of bytes which
eum<00:00:41.440><c> v</c><00:00:41.800><c> machine</c><00:00:42.160><c> can</c><00:00:43.000><c> understand</c><00:00:43.239><c> and</c><00:00:43.480><c> execute</c>

00:00:44.430 --> 00:00:44.440 align:start position:0%
eum v machine can understand and execute
 

00:00:44.440 --> 00:00:46.470 align:start position:0%
eum v machine can understand and execute
and<00:00:44.760><c> where</c><00:00:44.920><c> is</c><00:00:45.200><c> where</c><00:00:45.320><c> are</c><00:00:45.480><c> no</c><00:00:45.680><c> solidity</c><00:00:46.239><c> of</c>

00:00:46.470 --> 00:00:46.480 align:start position:0%
and where is where are no solidity of
 

00:00:46.480 --> 00:00:48.709 align:start position:0%
and where is where are no solidity of
wiper<00:00:47.039><c> sources</c><00:00:47.640><c> stored</c><00:00:48.199><c> inside</c><00:00:48.520><c> the</c>

00:00:48.709 --> 00:00:48.719 align:start position:0%
wiper sources stored inside the
 

00:00:48.719 --> 00:00:51.830 align:start position:0%
wiper sources stored inside the
blockchain<00:00:49.399><c> so</c><00:00:50.039><c> when</c><00:00:50.280><c> indexers</c><00:00:51.239><c> uh</c><00:00:51.360><c> index</c><00:00:51.719><c> the</c>

00:00:51.830 --> 00:00:51.840 align:start position:0%
blockchain so when indexers uh index the
 

00:00:51.840 --> 00:00:55.750 align:start position:0%
blockchain so when indexers uh index the
contract<00:00:52.280><c> data</c><00:00:53.039><c> all</c><00:00:53.680><c> way</c><00:00:54.000><c> can</c><00:00:54.800><c> see</c><00:00:55.239><c> are</c><00:00:55.480><c> those</c>

00:00:55.750 --> 00:00:55.760 align:start position:0%
contract data all way can see are those
 

00:00:55.760 --> 00:00:58.189 align:start position:0%
contract data all way can see are those
two<00:00:56.000><c> bite</c><00:00:56.359><c> code</c><00:00:56.640><c> values</c><00:00:57.079><c> which</c><00:00:57.199><c> are</c><00:00:57.520><c> contract</c>

00:00:58.189 --> 00:00:58.199 align:start position:0%
two bite code values which are contract
 

00:00:58.199 --> 00:01:00.069 align:start position:0%
two bite code values which are contract
creation<00:00:58.680><c> code</c><00:00:58.960><c> and</c><00:00:59.120><c> contract</c><00:00:59.519><c> R</c><00:00:59.719><c> time</c>

00:01:00.069 --> 00:01:00.079 align:start position:0%
creation code and contract R time
 

00:01:00.079 --> 00:01:03.029 align:start position:0%
creation code and contract R time
deployed<00:01:00.760><c> codes</c><00:01:01.760><c> uh</c><00:01:02.039><c> but</c><00:01:02.320><c> most</c><00:01:02.480><c> of</c><00:01:02.640><c> the</c><00:01:02.760><c> people</c>

00:01:03.029 --> 00:01:03.039 align:start position:0%
deployed codes uh but most of the people
 

00:01:03.039 --> 00:01:05.630 align:start position:0%
deployed codes uh but most of the people
are<00:01:03.160><c> not</c><00:01:03.359><c> good</c><00:01:03.519><c> in</c><00:01:03.960><c> understanding</c><00:01:04.400><c> what</c><00:01:04.640><c> the</c>

00:01:05.630 --> 00:01:05.640 align:start position:0%
are not good in understanding what the
 

00:01:05.640 --> 00:01:07.310 align:start position:0%
are not good in understanding what the
in<00:01:06.080><c> understanding</c><00:01:06.360><c> the</c><00:01:06.560><c> raw</c><00:01:06.840><c> sequence</c><00:01:07.159><c> of</c>

00:01:07.310 --> 00:01:07.320 align:start position:0%
in understanding the raw sequence of
 

00:01:07.320 --> 00:01:10.230 align:start position:0%
in understanding the raw sequence of
bites<00:01:07.720><c> and</c><00:01:07.840><c> what</c><00:01:08.040><c> we</c><00:01:08.200><c> usually</c><00:01:08.720><c> want</c><00:01:08.880><c> to</c><00:01:09.119><c> see</c><00:01:09.799><c> uh</c>

00:01:10.230 --> 00:01:10.240 align:start position:0%
bites and what we usually want to see uh
 

00:01:10.240 --> 00:01:12.070 align:start position:0%
bites and what we usually want to see uh
what<00:01:10.360><c> is</c><00:01:10.520><c> represented</c><00:01:10.960><c> in</c><00:01:11.080><c> the</c><00:01:11.240><c> picture</c><00:01:11.520><c> below</c>

00:01:12.070 --> 00:01:12.080 align:start position:0%
what is represented in the picture below
 

00:01:12.080 --> 00:01:16.230 align:start position:0%
what is represented in the picture below
so<00:01:12.320><c> we</c><00:01:12.560><c> ask</c><00:01:12.960><c> our</c><00:01:13.520><c> developers</c><00:01:14.360><c> to</c><00:01:15.360><c> send</c><00:01:15.960><c> those</c>

00:01:16.230 --> 00:01:16.240 align:start position:0%
so we ask our developers to send those
 

00:01:16.240 --> 00:01:19.789 align:start position:0%
so we ask our developers to send those
sources<00:01:16.640><c> to</c><00:01:16.880><c> us</c><00:01:17.479><c> and</c><00:01:17.799><c> we</c><00:01:18.799><c> recompile</c><00:01:19.439><c> them</c><00:01:19.680><c> and</c>

00:01:19.789 --> 00:01:19.799 align:start position:0%
sources to us and we recompile them and
 

00:01:19.799 --> 00:01:22.870 align:start position:0%
sources to us and we recompile them and
check<00:01:20.159><c> that</c><00:01:20.920><c> those</c><00:01:21.320><c> actually</c><00:01:21.680><c> correspond</c><00:01:22.560><c> to</c>

00:01:22.870 --> 00:01:22.880 align:start position:0%
check that those actually correspond to
 

00:01:22.880 --> 00:01:26.030 align:start position:0%
check that those actually correspond to
the<00:01:23.400><c> onchain</c><00:01:24.240><c> code</c><00:01:24.759><c> values</c><00:01:25.320><c> and</c><00:01:25.479><c> this</c><00:01:25.600><c> is</c><00:01:25.759><c> the</c>

00:01:26.030 --> 00:01:26.040 align:start position:0%
the onchain code values and this is the
 

00:01:26.040 --> 00:01:29.030 align:start position:0%
the onchain code values and this is the
contact<00:01:26.560><c> verification</c><00:01:27.560><c> and</c><00:01:27.759><c> today</c><00:01:28.200><c> I</c><00:01:28.320><c> want</c><00:01:28.520><c> to</c>

00:01:29.030 --> 00:01:29.040 align:start position:0%
contact verification and today I want to
 

00:01:29.040 --> 00:01:31.429 align:start position:0%
contact verification and today I want to
to<00:01:29.240><c> verify</c><00:01:29.920><c> a</c><00:01:30.000><c> couple</c><00:01:30.200><c> of</c><00:01:30.280><c> contracts</c><00:01:30.680><c> with</c><00:01:30.880><c> you</c>

00:01:31.429 --> 00:01:31.439 align:start position:0%
to verify a couple of contracts with you
 

00:01:31.439 --> 00:01:34.030 align:start position:0%
to verify a couple of contracts with you
so<00:01:31.680><c> let's</c><00:01:31.880><c> start</c><00:01:32.119><c> with</c><00:01:32.280><c> the</c><00:01:32.399><c> simple</c><00:01:32.880><c> one</c><00:01:33.880><c> uh</c>

00:01:34.030 --> 00:01:34.040 align:start position:0%
so let's start with the simple one uh
 

00:01:34.040 --> 00:01:37.069 align:start position:0%
so let's start with the simple one uh
represented<00:01:34.600><c> by</c><00:01:34.840><c> those</c><00:01:35.200><c> two</c><00:01:36.040><c> code</c><00:01:36.439><c> values</c>

00:01:37.069 --> 00:01:37.079 align:start position:0%
represented by those two code values
 

00:01:37.079 --> 00:01:39.350 align:start position:0%
represented by those two code values
here<00:01:37.640><c> what</c><00:01:37.880><c> do</c><00:01:37.960><c> we</c><00:01:38.079><c> need</c><00:01:38.280><c> from</c><00:01:38.520><c> the</c><00:01:38.720><c> user</c><00:01:39.119><c> to</c>

00:01:39.350 --> 00:01:39.360 align:start position:0%
here what do we need from the user to
 

00:01:39.360 --> 00:01:42.030 align:start position:0%
here what do we need from the user to
verify<00:01:39.759><c> the</c><00:01:39.920><c> contract</c><00:01:40.720><c> first</c><00:01:40.920><c> of</c><00:01:41.040><c> all</c><00:01:41.439><c> we</c><00:01:41.720><c> need</c>

00:01:42.030 --> 00:01:42.040 align:start position:0%
verify the contract first of all we need
 

00:01:42.040 --> 00:01:44.950 align:start position:0%
verify the contract first of all we need
the<00:01:42.320><c> source</c><00:01:42.960><c> files</c><00:01:43.960><c> themselves</c><00:01:44.320><c> of</c><00:01:44.479><c> course</c>

00:01:44.950 --> 00:01:44.960 align:start position:0%
the source files themselves of course
 

00:01:44.960 --> 00:01:46.550 align:start position:0%
the source files themselves of course
and<00:01:45.280><c> let's</c><00:01:45.520><c> assume</c><00:01:45.759><c> that</c><00:01:46.000><c> this</c><00:01:46.200><c> tricky</c>

00:01:46.550 --> 00:01:46.560 align:start position:0%
and let's assume that this tricky
 

00:01:46.560 --> 00:01:49.109 align:start position:0%
and let's assume that this tricky
storage<00:01:47.040><c> contract</c><00:01:47.960><c> uh</c><00:01:48.079><c> is</c><00:01:48.280><c> our</c><00:01:48.560><c> potential</c>

00:01:49.109 --> 00:01:49.119 align:start position:0%
storage contract uh is our potential
 

00:01:49.119 --> 00:01:51.550 align:start position:0%
storage contract uh is our potential
candidate<00:01:50.119><c> uh</c><00:01:50.240><c> it</c><00:01:50.360><c> is</c><00:01:50.479><c> a</c><00:01:50.640><c> tricky</c><00:01:51.159><c> just</c><00:01:51.360><c> because</c>

00:01:51.550 --> 00:01:51.560 align:start position:0%
candidate uh it is a tricky just because
 

00:01:51.560 --> 00:01:53.469 align:start position:0%
candidate uh it is a tricky just because
it<00:01:51.719><c> add</c><00:01:51.920><c> some</c><00:01:52.119><c> magic</c><00:01:52.399><c> number</c><00:01:52.799><c> before</c><00:01:53.079><c> storing</c>

00:01:53.469 --> 00:01:53.479 align:start position:0%
it add some magic number before storing
 

00:01:53.479 --> 00:01:56.510 align:start position:0%
it add some magic number before storing
it<00:01:53.640><c> inside</c><00:01:53.960><c> the</c><00:01:54.119><c> storage</c><00:01:54.880><c> that's</c><00:01:55.079><c> it</c><00:01:56.000><c> uh</c><00:01:56.280><c> also</c>

00:01:56.510 --> 00:01:56.520 align:start position:0%
it inside the storage that's it uh also
 

00:01:56.520 --> 00:01:58.469 align:start position:0%
it inside the storage that's it uh also
we<00:01:56.640><c> need</c><00:01:56.799><c> the</c><00:01:57.000><c> compiler</c><00:01:57.759><c> version</c><00:01:58.200><c> which</c><00:01:58.360><c> the</c>

00:01:58.469 --> 00:01:58.479 align:start position:0%
we need the compiler version which the
 

00:01:58.479 --> 00:02:00.709 align:start position:0%
we need the compiler version which the
contract<00:01:58.880><c> has</c><00:01:59.000><c> been</c><00:01:59.200><c> compiled</c><00:01:59.640><c> with</c><00:02:00.079><c> and</c><00:02:00.399><c> the</c>

00:02:00.709 --> 00:02:00.719 align:start position:0%
contract has been compiled with and the
 

00:02:00.719 --> 00:02:03.389 align:start position:0%
contract has been compiled with and the
compilation<00:02:01.719><c> settings</c><00:02:02.719><c> uh</c><00:02:02.840><c> with</c><00:02:03.039><c> all</c><00:02:03.200><c> that</c>

00:02:03.389 --> 00:02:03.399 align:start position:0%
compilation settings uh with all that
 

00:02:03.399 --> 00:02:06.069 align:start position:0%
compilation settings uh with all that
information<00:02:04.320><c> our</c><00:02:04.560><c> next</c><00:02:04.799><c> first</c><00:02:05.119><c> step</c><00:02:05.439><c> is</c><00:02:05.799><c> just</c>

00:02:06.069 --> 00:02:06.079 align:start position:0%
information our next first step is just
 

00:02:06.079 --> 00:02:08.830 align:start position:0%
information our next first step is just
to<00:02:06.320><c> combine</c><00:02:07.280><c> all</c><00:02:07.479><c> of</c><00:02:07.640><c> that</c><00:02:07.960><c> into</c><00:02:08.200><c> the</c><00:02:08.440><c> standard</c>

00:02:08.830 --> 00:02:08.840 align:start position:0%
to combine all of that into the standard
 

00:02:08.840 --> 00:02:11.270 align:start position:0%
to combine all of that into the standard
Json<00:02:09.239><c> input</c><00:02:09.599><c> format</c><00:02:10.520><c> uh</c><00:02:10.640><c> which</c><00:02:10.840><c> has</c><00:02:11.000><c> all</c>

00:02:11.270 --> 00:02:11.280 align:start position:0%
Json input format uh which has all
 

00:02:11.280 --> 00:02:14.190 align:start position:0%
Json input format uh which has all
information<00:02:11.720><c> just</c><00:02:11.879><c> in</c><00:02:12.040><c> one</c><00:02:12.480><c> file</c><00:02:13.480><c> uh</c><00:02:13.640><c> we</c>

00:02:14.190 --> 00:02:14.200 align:start position:0%
information just in one file uh we
 

00:02:14.200 --> 00:02:17.589 align:start position:0%
information just in one file uh we
submit<00:02:14.720><c> this</c><00:02:15.239><c> Json</c><00:02:15.800><c> to</c><00:02:16.080><c> the</c><00:02:16.599><c> compiler</c><00:02:17.440><c> and</c>

00:02:17.589 --> 00:02:17.599 align:start position:0%
submit this Json to the compiler and
 

00:02:17.599 --> 00:02:19.509 align:start position:0%
submit this Json to the compiler and
what<00:02:17.720><c> it</c><00:02:17.959><c> returns</c><00:02:18.160><c> us</c><00:02:18.400><c> back</c><00:02:18.680><c> is</c><00:02:18.840><c> the</c><00:02:19.120><c> standard</c>

00:02:19.509 --> 00:02:19.519 align:start position:0%
what it returns us back is the standard
 

00:02:19.519 --> 00:02:22.229 align:start position:0%
what it returns us back is the standard
Json<00:02:20.000><c> output</c><00:02:20.920><c> which</c><00:02:21.160><c> is</c>

00:02:22.229 --> 00:02:22.239 align:start position:0%
Json output which is
 

00:02:22.239 --> 00:02:25.350 align:start position:0%
Json output which is
um<00:02:23.239><c> uh</c><00:02:24.160><c> quite</c><00:02:24.360><c> big</c><00:02:24.599><c> usually</c><00:02:24.959><c> but</c><00:02:25.080><c> what</c><00:02:25.200><c> is</c>

00:02:25.350 --> 00:02:25.360 align:start position:0%
um uh quite big usually but what is
 

00:02:25.360 --> 00:02:27.030 align:start position:0%
um uh quite big usually but what is
important<00:02:25.720><c> here</c><00:02:25.840><c> for</c><00:02:26.040><c> us</c><00:02:26.280><c> is</c><00:02:26.440><c> that</c><00:02:26.560><c> it</c><00:02:26.840><c> returns</c>

00:02:27.030 --> 00:02:27.040 align:start position:0%
important here for us is that it returns
 

00:02:27.040 --> 00:02:28.830 align:start position:0%
important here for us is that it returns
to<00:02:27.200><c> bite</c><00:02:27.440><c> code</c><00:02:27.640><c> values</c><00:02:28.040><c> compiled</c><00:02:28.480><c> creation</c>

00:02:28.830 --> 00:02:28.840 align:start position:0%
to bite code values compiled creation
 

00:02:28.840 --> 00:02:31.309 align:start position:0%
to bite code values compiled creation
and<00:02:29.000><c> compiled</c><00:02:29.360><c> CL</c><00:02:29.519><c> time</c><00:02:29.680><c> code</c><00:02:30.080><c> values</c><00:02:30.920><c> so</c><00:02:31.200><c> what</c>

00:02:31.309 --> 00:02:31.319 align:start position:0%
and compiled CL time code values so what
 

00:02:31.319 --> 00:02:33.509 align:start position:0%
and compiled CL time code values so what
we<00:02:31.480><c> have</c><00:02:31.640><c> to</c><00:02:31.760><c> do</c><00:02:32.000><c> here</c><00:02:32.200><c> is</c><00:02:32.319><c> to</c><00:02:32.599><c> just</c><00:02:33.040><c> take</c><00:02:33.319><c> those</c>

00:02:33.509 --> 00:02:33.519 align:start position:0%
we have to do here is to just take those
 

00:02:33.519 --> 00:02:36.150 align:start position:0%
we have to do here is to just take those
two<00:02:33.720><c> bite</c><00:02:34.000><c> codes</c><00:02:34.440><c> and</c><00:02:34.720><c> compare</c><00:02:35.239><c> them</c><00:02:35.800><c> do</c><00:02:36.000><c> they</c>

00:02:36.150 --> 00:02:36.160 align:start position:0%
two bite codes and compare them do they
 

00:02:36.160 --> 00:02:41.110 align:start position:0%
two bite codes and compare them do they
match<00:02:36.720><c> yep</c><00:02:37.000><c> they</c><00:02:37.200><c> matches</c><00:02:37.680><c> so</c><00:02:38.160><c> that's</c><00:02:38.640><c> it</c><00:02:40.120><c> uh</c>

00:02:41.110 --> 00:02:41.120 align:start position:0%
match yep they matches so that's it uh
 

00:02:41.120 --> 00:02:42.750 align:start position:0%
match yep they matches so that's it uh
actually<00:02:41.480><c> is</c><00:02:41.599><c> it</c><00:02:41.760><c> always</c><00:02:42.120><c> that</c><00:02:42.319><c> easy</c><00:02:42.599><c> to</c>

00:02:42.750 --> 00:02:42.760 align:start position:0%
actually is it always that easy to
 

00:02:42.760 --> 00:02:44.589 align:start position:0%
actually is it always that easy to
verify<00:02:43.080><c> the</c><00:02:43.200><c> context</c><00:02:43.560><c> well</c><00:02:44.000><c> let's</c><00:02:44.200><c> look</c><00:02:44.360><c> at</c><00:02:44.480><c> a</c>

00:02:44.589 --> 00:02:44.599 align:start position:0%
verify the context well let's look at a
 

00:02:44.599 --> 00:02:46.270 align:start position:0%
verify the context well let's look at a
little<00:02:44.800><c> bit</c><00:02:44.920><c> more</c><00:02:45.120><c> complex</c><00:02:45.519><c> example</c><00:02:46.000><c> here</c>

00:02:46.270 --> 00:02:46.280 align:start position:0%
little bit more complex example here
 

00:02:46.280 --> 00:02:49.589 align:start position:0%
little bit more complex example here
which<00:02:46.400><c> is</c><00:02:47.319><c> uh</c><00:02:47.680><c> where</c><00:02:48.120><c> we</c><00:02:48.280><c> used</c><00:02:48.840><c> as</c><00:02:49.159><c> external</c>

00:02:49.589 --> 00:02:49.599 align:start position:0%
which is uh where we used as external
 

00:02:49.599 --> 00:02:51.070 align:start position:0%
which is uh where we used as external
library<00:02:50.000><c> for</c><00:02:50.239><c> making</c><00:02:50.519><c> the</c><00:02:50.720><c> addition</c>

00:02:51.070 --> 00:02:51.080 align:start position:0%
library for making the addition
 

00:02:51.080 --> 00:02:52.830 align:start position:0%
library for making the addition
operation<00:02:51.519><c> and</c><00:02:51.720><c> external</c><00:02:52.080><c> libraries</c><00:02:52.519><c> as</c><00:02:52.680><c> the</c>

00:02:52.830 --> 00:02:52.840 align:start position:0%
operation and external libraries as the
 

00:02:52.840 --> 00:02:55.190 align:start position:0%
operation and external libraries as the
contact<00:02:53.280><c> codes</c><00:02:54.040><c> which</c><00:02:54.159><c> are</c><00:02:54.360><c> deployed</c><00:02:54.760><c> once</c><00:02:55.040><c> at</c>

00:02:55.190 --> 00:02:55.200 align:start position:0%
contact codes which are deployed once at
 

00:02:55.200 --> 00:02:57.270 align:start position:0%
contact codes which are deployed once at
some<00:02:55.440><c> address</c><00:02:55.879><c> and</c><00:02:56.040><c> then</c><00:02:56.239><c> our</c><00:02:56.519><c> contracts</c><00:02:56.959><c> can</c>

00:02:57.270 --> 00:02:57.280 align:start position:0%
some address and then our contracts can
 

00:02:57.280 --> 00:03:01.030 align:start position:0%
some address and then our contracts can
link<00:02:58.120><c> where</c><00:02:58.440><c> addresses</c><00:02:59.120><c> in</c><00:03:00.319><c> inside</c>

00:03:01.030 --> 00:03:01.040 align:start position:0%
link where addresses in inside
 

00:03:01.040 --> 00:03:04.070 align:start position:0%
link where addresses in inside
themselves<00:03:01.840><c> and</c><00:03:02.280><c> uh</c><00:03:02.480><c> reuse</c><00:03:03.440><c> where</c><00:03:03.720><c> functions</c>

00:03:04.070 --> 00:03:04.080 align:start position:0%
themselves and uh reuse where functions
 

00:03:04.080 --> 00:03:06.990 align:start position:0%
themselves and uh reuse where functions
by<00:03:04.239><c> delegate</c><00:03:04.640><c> call</c><00:03:04.879><c> up</c><00:03:05.120><c> code</c><00:03:06.080><c> so</c><00:03:06.560><c> we</c><00:03:06.640><c> will</c><00:03:06.799><c> do</c>

00:03:06.990 --> 00:03:07.000 align:start position:0%
by delegate call up code so we will do
 

00:03:07.000 --> 00:03:09.110 align:start position:0%
by delegate call up code so we will do
the<00:03:07.120><c> same</c><00:03:07.319><c> Transformations</c><00:03:08.080><c> as</c><00:03:08.360><c> before</c><00:03:08.959><c> and</c>

00:03:09.110 --> 00:03:09.120 align:start position:0%
the same Transformations as before and
 

00:03:09.120 --> 00:03:11.710 align:start position:0%
the same Transformations as before and
we'll<00:03:09.400><c> get</c><00:03:09.599><c> two</c><00:03:10.239><c> up</c><00:03:10.519><c> COD</c><00:03:10.799><c> two</c><00:03:11.040><c> bite</c><00:03:11.280><c> codes</c><00:03:11.599><c> as</c>

00:03:11.710 --> 00:03:11.720 align:start position:0%
we'll get two up COD two bite codes as
 

00:03:11.720 --> 00:03:15.030 align:start position:0%
we'll get two up COD two bite codes as
well<00:03:12.599><c> but</c><00:03:12.799><c> do</c><00:03:12.959><c> we</c><00:03:13.120><c> match</c><00:03:13.959><c> well</c><00:03:14.480><c> we</c><00:03:14.640><c> can</c><00:03:14.760><c> see</c>

00:03:15.030 --> 00:03:15.040 align:start position:0%
well but do we match well we can see
 

00:03:15.040 --> 00:03:16.910 align:start position:0%
well but do we match well we can see
that<00:03:15.200><c> there</c><00:03:15.360><c> is</c><00:03:15.560><c> a</c><00:03:15.799><c> strange</c><00:03:16.159><c> not</c><00:03:16.319><c> even</c><00:03:16.480><c> a</c><00:03:16.640><c> hex</c>

00:03:16.910 --> 00:03:16.920 align:start position:0%
that there is a strange not even a hex
 

00:03:16.920 --> 00:03:19.070 align:start position:0%
that there is a strange not even a hex
part<00:03:17.159><c> inside</c><00:03:17.440><c> the</c><00:03:17.599><c> compiled</c><00:03:18.080><c> creation</c><00:03:18.560><c> code</c>

00:03:19.070 --> 00:03:19.080 align:start position:0%
part inside the compiled creation code
 

00:03:19.080 --> 00:03:21.030 align:start position:0%
part inside the compiled creation code
which<00:03:19.319><c> does</c><00:03:19.480><c> not</c><00:03:19.840><c> M</c><00:03:20.000><c> correspond</c><00:03:20.440><c> to</c><00:03:20.560><c> the</c>

00:03:21.030 --> 00:03:21.040 align:start position:0%
which does not M correspond to the
 

00:03:21.040 --> 00:03:23.509 align:start position:0%
which does not M correspond to the
onchain<00:03:22.040><c> value</c>

00:03:23.509 --> 00:03:23.519 align:start position:0%
onchain value
 

00:03:23.519 --> 00:03:26.630 align:start position:0%
onchain value
so<00:03:24.519><c> why</c><00:03:24.680><c> it</c><00:03:24.879><c> happens</c><00:03:25.280><c> actually</c><00:03:25.640><c> this</c><00:03:25.760><c> is</c><00:03:25.920><c> the</c>

00:03:26.630 --> 00:03:26.640 align:start position:0%
so why it happens actually this is the
 

00:03:26.640 --> 00:03:28.270 align:start position:0%
so why it happens actually this is the
place<00:03:26.959><c> where</c><00:03:27.120><c> the</c><00:03:27.400><c> Library</c><00:03:27.799><c> address</c><00:03:28.120><c> should</c>

00:03:28.270 --> 00:03:28.280 align:start position:0%
place where the Library address should
 

00:03:28.280 --> 00:03:31.190 align:start position:0%
place where the Library address should
be<00:03:28.439><c> put</c><00:03:28.879><c> at</c><00:03:29.400><c> but</c><00:03:30.040><c> as</c><00:03:30.239><c> we</c><00:03:30.439><c> haven't</c><00:03:30.720><c> provided</c><00:03:31.080><c> it</c>

00:03:31.190 --> 00:03:31.200 align:start position:0%
be put at but as we haven't provided it
 

00:03:31.200 --> 00:03:32.789 align:start position:0%
be put at but as we haven't provided it
to<00:03:31.360><c> the</c><00:03:31.519><c> compiler</c><00:03:31.920><c> during</c><00:03:32.159><c> the</c><00:03:32.319><c> compilation</c>

00:03:32.789 --> 00:03:32.799 align:start position:0%
to the compiler during the compilation
 

00:03:32.799 --> 00:03:34.509 align:start position:0%
to the compiler during the compilation
it<00:03:32.959><c> just</c><00:03:33.080><c> don't</c><00:03:33.319><c> know</c><00:03:33.560><c> what</c><00:03:33.640><c> to</c><00:03:33.799><c> put</c><00:03:34.000><c> inside</c>

00:03:34.509 --> 00:03:34.519 align:start position:0%
it just don't know what to put inside
 

00:03:34.519 --> 00:03:38.309 align:start position:0%
it just don't know what to put inside
and<00:03:35.120><c> uh</c><00:03:36.120><c> uh</c><00:03:36.840><c> Place</c><00:03:37.280><c> some</c><00:03:37.519><c> place</c><00:03:37.959><c> holder</c>

00:03:38.309 --> 00:03:38.319 align:start position:0%
and uh uh Place some place holder
 

00:03:38.319 --> 00:03:40.509 align:start position:0%
and uh uh Place some place holder
instead<00:03:39.280><c> so</c><00:03:39.519><c> and</c><00:03:39.720><c> our</c><00:03:39.959><c> question</c><00:03:40.159><c> is</c><00:03:40.280><c> how</c><00:03:40.400><c> to</c>

00:03:40.509 --> 00:03:40.519 align:start position:0%
instead so and our question is how to
 

00:03:40.519 --> 00:03:42.710 align:start position:0%
instead so and our question is how to
verify<00:03:40.840><c> such</c><00:03:41.120><c> contracts</c><00:03:41.760><c> luckily</c><00:03:42.120><c> for</c><00:03:42.319><c> us</c>

00:03:42.710 --> 00:03:42.720 align:start position:0%
verify such contracts luckily for us
 

00:03:42.720 --> 00:03:44.350 align:start position:0%
verify such contracts luckily for us
there<00:03:42.879><c> is</c><00:03:43.040><c> a</c><00:03:43.200><c> special</c><00:03:43.519><c> section</c><00:03:43.920><c> inside</c><00:03:44.200><c> the</c>

00:03:44.350 --> 00:03:44.360 align:start position:0%
there is a special section inside the
 

00:03:44.360 --> 00:03:47.190 align:start position:0%
there is a special section inside the
standard<00:03:44.720><c> Json</c><00:03:45.560><c> output</c><00:03:46.159><c> which</c><00:03:46.280><c> is</c><00:03:46.480><c> named</c><00:03:46.879><c> link</c>

00:03:47.190 --> 00:03:47.200 align:start position:0%
standard Json output which is named link
 

00:03:47.200 --> 00:03:49.869 align:start position:0%
standard Json output which is named link
references<00:03:47.920><c> and</c><00:03:48.319><c> which</c><00:03:48.680><c> for</c><00:03:48.959><c> each</c><00:03:49.159><c> unlink</c>

00:03:49.869 --> 00:03:49.879 align:start position:0%
references and which for each unlink
 

00:03:49.879 --> 00:03:51.500 align:start position:0%
references and which for each unlink
Library<00:03:50.400><c> contains</c>

00:03:51.500 --> 00:03:51.510 align:start position:0%
Library contains
 

00:03:51.510 --> 00:03:52.750 align:start position:0%
Library contains
[Music]

00:03:52.750 --> 00:03:52.760 align:start position:0%
[Music]
 

00:03:52.760 --> 00:03:56.030 align:start position:0%
[Music]
the<00:03:53.760><c> some</c><00:03:53.920><c> information</c><00:03:54.439><c> how</c><00:03:54.680><c> to</c><00:03:55.680><c> where</c><00:03:55.879><c> where</c>

00:03:56.030 --> 00:03:56.040 align:start position:0%
the some information how to where where
 

00:03:56.040 --> 00:03:58.470 align:start position:0%
the some information how to where where
this<00:03:56.200><c> Library</c><00:03:56.560><c> address</c><00:03:56.879><c> should</c><00:03:57.079><c> be</c><00:03:58.040><c> placed</c>

00:03:58.470 --> 00:03:58.480 align:start position:0%
this Library address should be placed
 

00:03:58.480 --> 00:04:01.710 align:start position:0%
this Library address should be placed
inside<00:03:59.280><c> uh</c><00:03:59.400><c> especially</c><00:04:00.000><c> is</c><00:04:00.120><c> the</c><00:04:00.560><c> first</c><00:04:00.959><c> BTE</c>

00:04:01.710 --> 00:04:01.720 align:start position:0%
inside uh especially is the first BTE
 

00:04:01.720 --> 00:04:03.550 align:start position:0%
inside uh especially is the first BTE
where<00:04:02.120><c> it</c><00:04:02.239><c> should</c><00:04:02.400><c> be</c><00:04:02.560><c> placed</c><00:04:02.879><c> at</c><00:04:03.159><c> and</c><00:04:03.360><c> its</c>

00:04:03.550 --> 00:04:03.560 align:start position:0%
where it should be placed at and its
 

00:04:03.560 --> 00:04:05.710 align:start position:0%
where it should be placed at and its
length<00:04:03.920><c> which</c><00:04:04.000><c> is</c><00:04:04.120><c> always</c><00:04:04.360><c> 20</c>

00:04:05.710 --> 00:04:05.720 align:start position:0%
length which is always 20
 

00:04:05.720 --> 00:04:08.350 align:start position:0%
length which is always 20
bytes<00:04:06.720><c> so</c><00:04:07.079><c> what</c><00:04:07.200><c> we</c><00:04:07.319><c> need</c><00:04:07.439><c> to</c><00:04:07.560><c> do</c><00:04:07.760><c> is</c><00:04:07.959><c> just</c><00:04:08.120><c> to</c>

00:04:08.350 --> 00:04:08.360 align:start position:0%
bytes so what we need to do is just to
 

00:04:08.360 --> 00:04:11.750 align:start position:0%
bytes so what we need to do is just to
take<00:04:08.959><c> the</c><00:04:09.280><c> specified</c><00:04:09.840><c> offset</c><00:04:10.319><c> value</c><00:04:11.239><c> uh</c><00:04:11.400><c> when</c>

00:04:11.750 --> 00:04:11.760 align:start position:0%
take the specified offset value uh when
 

00:04:11.760 --> 00:04:15.110 align:start position:0%
take the specified offset value uh when
take<00:04:11.959><c> the</c><00:04:12.159><c> next</c><00:04:12.400><c> 20</c><00:04:12.799><c> bytes</c><00:04:13.120><c> from</c><00:04:13.599><c> the</c><00:04:14.599><c> on</c><00:04:14.840><c> chain</c>

00:04:15.110 --> 00:04:15.120 align:start position:0%
take the next 20 bytes from the on chain
 

00:04:15.120 --> 00:04:18.629 align:start position:0%
take the next 20 bytes from the on chain
code<00:04:15.560><c> and</c><00:04:15.920><c> the</c><00:04:16.680><c> substitute</c><00:04:17.400><c> it</c><00:04:17.759><c> inside</c><00:04:18.199><c> the</c>

00:04:18.629 --> 00:04:18.639 align:start position:0%
code and the substitute it inside the
 

00:04:18.639 --> 00:04:21.990 align:start position:0%
code and the substitute it inside the
compiled<00:04:19.160><c> code</c><00:04:19.799><c> so</c><00:04:20.079><c> do</c><00:04:20.400><c> those</c><00:04:21.160><c> two</c><00:04:21.440><c> by</c><00:04:21.720><c> code</c>

00:04:21.990 --> 00:04:22.000 align:start position:0%
compiled code so do those two by code
 

00:04:22.000 --> 00:04:25.270 align:start position:0%
compiled code so do those two by code
match<00:04:22.320><c> now</c><00:04:22.840><c> yes</c><00:04:23.040><c> we</c><00:04:23.280><c> do</c><00:04:23.919><c> Lu</c><00:04:24.320><c> for</c><00:04:24.479><c> us</c><00:04:24.720><c> so</c><00:04:24.960><c> here</c><00:04:25.160><c> we</c>

00:04:25.270 --> 00:04:25.280 align:start position:0%
match now yes we do Lu for us so here we
 

00:04:25.280 --> 00:04:27.749 align:start position:0%
match now yes we do Lu for us so here we
are<00:04:25.479><c> just</c><00:04:25.680><c> verify</c><00:04:26.080><c> the</c><00:04:26.199><c> second</c><00:04:26.520><c> contract</c><00:04:26.880><c> for</c>

00:04:27.749 --> 00:04:27.759 align:start position:0%
are just verify the second contract for
 

00:04:27.759 --> 00:04:30.430 align:start position:0%
are just verify the second contract for
today<00:04:28.759><c> uh</c><00:04:29.240><c> in</c><00:04:29.400><c> general</c>

00:04:30.430 --> 00:04:30.440 align:start position:0%
today uh in general
 

00:04:30.440 --> 00:04:33.629 align:start position:0%
today uh in general
such<00:04:31.400><c> uh</c><00:04:31.800><c> Replacements</c><00:04:32.800><c> we</c><00:04:32.960><c> name</c><00:04:33.199><c> them</c><00:04:33.360><c> code</c>

00:04:33.629 --> 00:04:33.639 align:start position:0%
such uh Replacements we name them code
 

00:04:33.639 --> 00:04:35.270 align:start position:0%
such uh Replacements we name them code
Transformations<00:04:34.520><c> and</c><00:04:34.639><c> those</c><00:04:34.840><c> are</c><00:04:35.039><c> some</c>

00:04:35.270 --> 00:04:35.280 align:start position:0%
Transformations and those are some
 

00:04:35.280 --> 00:04:37.029 align:start position:0%
Transformations and those are some
actions<00:04:35.759><c> which</c><00:04:36.199><c> may</c><00:04:36.360><c> be</c><00:04:36.520><c> applied</c><00:04:36.800><c> to</c><00:04:36.880><c> the</c>

00:04:37.029 --> 00:04:37.039 align:start position:0%
actions which may be applied to the
 

00:04:37.039 --> 00:04:39.990 align:start position:0%
actions which may be applied to the
compiled<00:04:37.479><c> code</c><00:04:38.080><c> uh</c><00:04:38.479><c> before</c><00:04:38.840><c> or</c><00:04:39.240><c> after</c><00:04:39.680><c> during</c>

00:04:39.990 --> 00:04:40.000 align:start position:0%
compiled code uh before or after during
 

00:04:40.000 --> 00:04:42.469 align:start position:0%
compiled code uh before or after during
the<00:04:40.160><c> deployment</c><00:04:40.840><c> process</c><00:04:41.680><c> and</c><00:04:41.840><c> which</c><00:04:42.039><c> changes</c>

00:04:42.469 --> 00:04:42.479 align:start position:0%
the deployment process and which changes
 

00:04:42.479 --> 00:04:44.790 align:start position:0%
the deployment process and which changes
its<00:04:42.759><c> bite</c><00:04:43.039><c> code</c><00:04:43.240><c> a</c><00:04:43.320><c> little</c><00:04:43.520><c> bit</c><00:04:43.840><c> but</c><00:04:44.039><c> which</c>

00:04:44.790 --> 00:04:44.800 align:start position:0%
its bite code a little bit but which
 

00:04:44.800 --> 00:04:46.870 align:start position:0%
its bite code a little bit but which
Remains<00:04:45.000><c> the</c><00:04:45.160><c> functionality</c><00:04:45.759><c> the</c><00:04:45.919><c> same</c><00:04:46.639><c> and</c>

00:04:46.870 --> 00:04:46.880 align:start position:0%
Remains the functionality the same and
 

00:04:46.880 --> 00:04:49.029 align:start position:0%
Remains the functionality the same and
there<00:04:47.039><c> are</c><00:04:47.199><c> currently</c><00:04:47.720><c> five</c><00:04:48.039><c> of</c><00:04:48.240><c> social</c><00:04:48.800><c> such</c>

00:04:49.029 --> 00:04:49.039 align:start position:0%
there are currently five of social such
 

00:04:49.039 --> 00:04:51.029 align:start position:0%
there are currently five of social such
Transformations<00:04:49.759><c> we</c><00:04:50.120><c> know</c><00:04:50.440><c> about</c><00:04:50.759><c> and</c>

00:04:51.029 --> 00:04:51.039 align:start position:0%
Transformations we know about and
 

00:04:51.039 --> 00:04:53.270 align:start position:0%
Transformations we know about and
support<00:04:52.039><c> uh</c><00:04:52.280><c> and</c><00:04:52.560><c> we</c><00:04:52.759><c> talk</c><00:04:53.000><c> about</c><00:04:53.160><c> the</c>

00:04:53.270 --> 00:04:53.280 align:start position:0%
support uh and we talk about the
 

00:04:53.280 --> 00:04:56.950 align:start position:0%
support uh and we talk about the
libraries<00:04:53.919><c> but</c><00:04:54.440><c> where</c><00:04:54.639><c> are</c><00:04:55.600><c> four</c><00:04:55.960><c> more</c><00:04:56.720><c> we</c>

00:04:56.950 --> 00:04:56.960 align:start position:0%
libraries but where are four more we
 

00:04:56.960 --> 00:04:59.870 align:start position:0%
libraries but where are four more we
don't<00:04:57.240><c> have</c><00:04:57.479><c> time</c><00:04:58.120><c> to</c><00:04:58.320><c> talk</c><00:04:58.560><c> about</c><00:04:58.880><c> today</c><00:04:59.759><c> but</c>

00:04:59.870 --> 00:04:59.880 align:start position:0%
don't have time to talk about today but
 

00:04:59.880 --> 00:05:01.110 align:start position:0%
don't have time to talk about today but
if<00:05:00.000><c> you</c><00:05:00.080><c> are</c><00:05:00.240><c> interested</c><00:05:00.639><c> you</c><00:05:00.759><c> might</c><00:05:01.000><c> just</c>

00:05:01.110 --> 00:05:01.120 align:start position:0%
if you are interested you might just
 

00:05:01.120 --> 00:05:05.390 align:start position:0%
if you are interested you might just
follow<00:05:01.400><c> the</c><00:05:01.560><c> QR</c><00:05:01.880><c> link</c><00:05:02.720><c> and</c><00:05:03.320><c> uh</c>

00:05:05.390 --> 00:05:05.400 align:start position:0%
follow the QR link and uh
 

00:05:05.400 --> 00:05:09.189 align:start position:0%
follow the QR link and uh
see<00:05:06.400><c> some</c><00:05:06.639><c> more</c><00:05:06.800><c> information</c><00:05:07.360><c> about</c>

00:05:09.189 --> 00:05:09.199 align:start position:0%
see some more information about
 

00:05:09.199 --> 00:05:12.590 align:start position:0%
see some more information about
so<00:05:10.199><c> also</c><00:05:10.560><c> I</c><00:05:10.639><c> think</c><00:05:10.800><c> the</c><00:05:10.960><c> last</c><00:05:11.160><c> slide</c><00:05:11.600><c> my</c>

00:05:12.590 --> 00:05:12.600 align:start position:0%
so also I think the last slide my
 

00:05:12.600 --> 00:05:15.070 align:start position:0%
so also I think the last slide my
presentation<00:05:13.280><c> title</c><00:05:13.680><c> was</c><00:05:14.039><c> verifier</c><00:05:14.560><c> Alliance</c>

00:05:15.070 --> 00:05:15.080 align:start position:0%
presentation title was verifier Alliance
 

00:05:15.080 --> 00:05:18.150 align:start position:0%
presentation title was verifier Alliance
the<00:05:15.240><c> first</c><00:05:15.440><c> part</c><00:05:15.680><c> of</c><00:05:15.840><c> it</c><00:05:16.440><c> and</c><00:05:16.919><c> uh</c><00:05:17.560><c> I</c><00:05:17.680><c> don't</c><00:05:18.039><c> I</c>

00:05:18.150 --> 00:05:18.160 align:start position:0%
the first part of it and uh I don't I
 

00:05:18.160 --> 00:05:20.309 align:start position:0%
the first part of it and uh I don't I
haven't<00:05:18.400><c> talked</c><00:05:18.680><c> about</c><00:05:19.000><c> that</c><00:05:19.400><c> a</c><00:05:19.560><c> lot</c><00:05:19.960><c> but</c><00:05:20.199><c> if</c>

00:05:20.309 --> 00:05:20.319 align:start position:0%
haven't talked about that a lot but if
 

00:05:20.319 --> 00:05:22.189 align:start position:0%
haven't talked about that a lot but if
you<00:05:20.440><c> are</c><00:05:20.680><c> interested</c><00:05:21.160><c> in</c><00:05:21.360><c> that</c><00:05:21.639><c> part</c><00:05:21.840><c> as</c><00:05:21.960><c> well</c>

00:05:22.189 --> 00:05:22.199 align:start position:0%
you are interested in that part as well
 

00:05:22.199 --> 00:05:24.870 align:start position:0%
you are interested in that part as well
you<00:05:22.400><c> may</c><00:05:22.759><c> be</c><00:05:23.520><c> you</c><00:05:23.840><c> you're</c><00:05:24.039><c> welcome</c><00:05:24.400><c> to</c><00:05:24.560><c> the</c>

00:05:24.870 --> 00:05:24.880 align:start position:0%
you may be you you're welcome to the
 

00:05:24.880 --> 00:05:27.270 align:start position:0%
you may be you you're welcome to the
panel<00:05:25.199><c> which</c><00:05:25.360><c> will</c><00:05:25.520><c> take</c><00:05:25.759><c> place</c><00:05:26.000><c> today</c><00:05:26.919><c> at</c>

00:05:27.270 --> 00:05:27.280 align:start position:0%
panel which will take place today at
 

00:05:27.280 --> 00:05:30.070 align:start position:0%
panel which will take place today at
5:30<00:05:27.840><c> p.m.</c><00:05:28.560><c> where</c><00:05:28.759><c> box</c><00:05:29.000><c> cloud</c><00:05:29.199><c> Source</c><00:05:29.440><c> f</c><00:05:29.759><c> Road</c>

00:05:30.070 --> 00:05:30.080 align:start position:0%
5:30 p.m. where box cloud Source f Road
 

00:05:30.080 --> 00:05:32.790 align:start position:0%
5:30 p.m. where box cloud Source f Road
scan<00:05:31.000><c> the</c><00:05:31.240><c> members</c><00:05:31.560><c> of</c><00:05:31.720><c> this</c><00:05:31.919><c> verify</c><00:05:32.319><c> Alliance</c>

00:05:32.790 --> 00:05:32.800 align:start position:0%
scan the members of this verify Alliance
 

00:05:32.800 --> 00:05:35.990 align:start position:0%
scan the members of this verify Alliance
initiative<00:05:33.880><c> will</c><00:05:34.880><c> describe</c><00:05:35.360><c> you</c><00:05:35.639><c> this</c><00:05:35.880><c> a</c>

00:05:35.990 --> 00:05:36.000 align:start position:0%
initiative will describe you this a
 

00:05:36.000 --> 00:05:37.510 align:start position:0%
initiative will describe you this a
little<00:05:36.240><c> bit</c><00:05:36.400><c> more</c><00:05:36.759><c> and</c><00:05:37.000><c> talk</c><00:05:37.240><c> about</c>

00:05:37.510 --> 00:05:37.520 align:start position:0%
little bit more and talk about
 

00:05:37.520 --> 00:05:40.110 align:start position:0%
little bit more and talk about
verification<00:05:38.080><c> as</c><00:05:38.240><c> well</c><00:05:39.080><c> thank</c><00:05:39.360><c> you</c><00:05:39.720><c> I</c><00:05:39.800><c> think</c>

00:05:40.110 --> 00:05:40.120 align:start position:0%
verification as well thank you I think
 

00:05:40.120 --> 00:05:41.909 align:start position:0%
verification as well thank you I think
that's

00:05:41.909 --> 00:05:41.919 align:start position:0%
that's
 

00:05:41.919 --> 00:05:52.390 align:start position:0%
that's
it<00:05:42.919><c> thank</c><00:05:43.160><c> you</c><00:05:43.720><c> R</c><00:05:44.520><c> do</c><00:05:44.639><c> we</c><00:05:44.840><c> have</c><00:05:45.680><c> questions</c><00:05:46.199><c> for</c>

00:05:52.390 --> 00:05:52.400 align:start position:0%
 
 

00:05:52.400 --> 00:05:55.710 align:start position:0%
 
Rim<00:05:53.400><c> oh</c>

00:05:55.710 --> 00:05:55.720 align:start position:0%
 
 

00:05:55.720 --> 00:05:58.390 align:start position:0%
 
okay<00:05:56.720><c> is</c><00:05:56.840><c> this</c><00:05:56.960><c> a</c><00:05:57.080><c> mic</c><00:05:57.319><c> too</c><00:05:57.759><c> this</c><00:05:57.880><c> is</c><00:05:58.120><c> this</c><00:05:58.240><c> is</c>

00:05:58.390 --> 00:05:58.400 align:start position:0%
okay is this a mic too this is this is
 

00:05:58.400 --> 00:06:00.309 align:start position:0%
okay is this a mic too this is this is
pretty<00:05:58.639><c> awesome</c><00:05:59.000><c> actually</c>

00:06:00.309 --> 00:06:00.319 align:start position:0%
pretty awesome actually
 

00:06:00.319 --> 00:06:03.510 align:start position:0%
pretty awesome actually
um<00:06:01.000><c> why</c><00:06:01.199><c> is</c><00:06:01.360><c> it</c><00:06:01.639><c> so</c><00:06:02.319><c> difficult</c><00:06:02.520><c> to</c><00:06:02.759><c> have</c>

00:06:03.510 --> 00:06:03.520 align:start position:0%
um why is it so difficult to have
 

00:06:03.520 --> 00:06:06.029 align:start position:0%
um why is it so difficult to have
decentralized<00:06:04.520><c> contract</c><00:06:05.160><c> verification</c>

00:06:06.029 --> 00:06:06.039 align:start position:0%
decentralized contract verification
 

00:06:06.039 --> 00:06:08.150 align:start position:0%
decentralized contract verification
right<00:06:06.360><c> we</c><00:06:06.479><c> we</c><00:06:06.560><c> use</c><00:06:06.759><c> service</c><00:06:07.199><c> Bo</c><00:06:07.599><c> Scout</c><00:06:07.800><c> ether</c>

00:06:08.150 --> 00:06:08.160 align:start position:0%
right we we use service Bo Scout ether
 

00:06:08.160 --> 00:06:10.710 align:start position:0%
right we we use service Bo Scout ether
scan<00:06:08.919><c> but</c><00:06:09.400><c> why</c><00:06:09.639><c> after</c><00:06:09.880><c> all</c><00:06:10.080><c> these</c><00:06:10.280><c> years</c><00:06:10.520><c> is</c>

00:06:10.710 --> 00:06:10.720 align:start position:0%
scan but why after all these years is
 

00:06:10.720 --> 00:06:13.670 align:start position:0%
scan but why after all these years is
the<00:06:10.919><c> experience</c><00:06:11.599><c> still</c><00:06:11.880><c> so</c><00:06:12.240><c> bad</c><00:06:12.720><c> in</c>

00:06:13.670 --> 00:06:13.680 align:start position:0%
the experience still so bad in
 

00:06:13.680 --> 00:06:17.469 align:start position:0%
the experience still so bad in
general<00:06:14.759><c> uh</c>

00:06:17.469 --> 00:06:17.479 align:start position:0%
general uh
 

00:06:17.479 --> 00:06:21.670 align:start position:0%
general uh
well<00:06:18.479><c> I</c><00:06:18.599><c> think</c><00:06:19.520><c> uh</c><00:06:20.440><c> it</c><00:06:20.599><c> happens</c><00:06:20.880><c> a</c><00:06:21.000><c> lot</c><00:06:21.240><c> because</c>

00:06:21.670 --> 00:06:21.680 align:start position:0%
well I think uh it happens a lot because
 

00:06:21.680 --> 00:06:23.270 align:start position:0%
well I think uh it happens a lot because
you<00:06:21.840><c> have</c><00:06:21.960><c> to</c><00:06:22.080><c> store</c><00:06:22.440><c> this</c><00:06:22.599><c> contct</c><00:06:22.919><c> somewhere</c>

00:06:23.270 --> 00:06:23.280 align:start position:0%
you have to store this contct somewhere
 

00:06:23.280 --> 00:06:25.350 align:start position:0%
you have to store this contct somewhere
first<00:06:23.479><c> of</c><00:06:23.560><c> all</c><00:06:23.960><c> and</c><00:06:24.120><c> we</c><00:06:24.440><c> sofware</c><00:06:24.919><c> which</c><00:06:25.080><c> tries</c>

00:06:25.350 --> 00:06:25.360 align:start position:0%
first of all and we sofware which tries
 

00:06:25.360 --> 00:06:27.270 align:start position:0%
first of all and we sofware which tries
to<00:06:25.599><c> decentralize</c><00:06:26.199><c> the</c><00:06:26.319><c> storage</c><00:06:26.840><c> process</c>

00:06:27.270 --> 00:06:27.280 align:start position:0%
to decentralize the storage process
 

00:06:27.280 --> 00:06:30.710 align:start position:0%
to decentralize the storage process
itself<00:06:27.919><c> and</c><00:06:28.639><c> uh</c><00:06:28.800><c> but</c><00:06:29.720><c> actually</c><00:06:30.360><c> what</c><00:06:30.440><c> is</c><00:06:30.560><c> more</c>

00:06:30.710 --> 00:06:30.720 align:start position:0%
itself and uh but actually what is more
 

00:06:30.720 --> 00:06:31.990 align:start position:0%
itself and uh but actually what is more
important<00:06:31.080><c> here</c><00:06:31.280><c> there</c><00:06:31.400><c> are</c><00:06:31.599><c> a</c><00:06:31.720><c> lot</c><00:06:31.840><c> of</c>

00:06:31.990 --> 00:06:32.000 align:start position:0%
important here there are a lot of
 

00:06:32.000 --> 00:06:37.110 align:start position:0%
important here there are a lot of
different<00:06:32.680><c> formats</c><00:06:33.680><c> uh</c><00:06:33.960><c> and</c><00:06:34.560><c> uh</c><00:06:35.680><c> all</c><00:06:36.680><c> like</c>

00:06:37.110 --> 00:06:37.120 align:start position:0%
different formats uh and uh all like
 

00:06:37.120 --> 00:06:39.070 align:start position:0%
different formats uh and uh all like
different<00:06:37.560><c> explorers</c><00:06:38.080><c> use</c><00:06:38.680><c> their</c><00:06:38.880><c> own</c>

00:06:39.070 --> 00:06:39.080 align:start position:0%
different explorers use their own
 

00:06:39.080 --> 00:06:41.270 align:start position:0%
different explorers use their own
formats<00:06:39.479><c> to</c><00:06:39.599><c> store</c><00:06:39.840><c> this</c><00:06:40.080><c> data</c><00:06:40.400><c> inside</c><00:06:41.199><c> uh</c>

00:06:41.270 --> 00:06:41.280 align:start position:0%
formats to store this data inside uh
 

00:06:41.280 --> 00:06:44.870 align:start position:0%
formats to store this data inside uh
Source<00:06:41.800><c> uses</c><00:06:42.160><c> its</c><00:06:42.280><c> own</c><00:06:42.560><c> data</c><00:06:43.280><c> and</c><00:06:44.000><c> one</c><00:06:44.240><c> of</c><00:06:44.440><c> the</c>

00:06:44.870 --> 00:06:44.880 align:start position:0%
Source uses its own data and one of the
 

00:06:44.880 --> 00:06:48.469 align:start position:0%
Source uses its own data and one of the
thisy<00:06:45.479><c> lines</c><00:06:45.759><c> initiative's</c><00:06:46.639><c> idea</c><00:06:47.120><c> was</c><00:06:47.479><c> to</c>

00:06:48.469 --> 00:06:48.479 align:start position:0%
thisy lines initiative's idea was to
 

00:06:48.479 --> 00:06:52.790 align:start position:0%
thisy lines initiative's idea was to
develop<00:06:49.000><c> the</c><00:06:49.840><c> schema</c><00:06:50.840><c> uh</c><00:06:51.400><c> we</c><00:06:51.680><c> in</c><00:06:51.880><c> which</c><00:06:52.400><c> uh</c><00:06:52.560><c> all</c>

00:06:52.790 --> 00:06:52.800 align:start position:0%
develop the schema uh we in which uh all
 

00:06:52.800 --> 00:06:56.189 align:start position:0%
develop the schema uh we in which uh all
contracts<00:06:53.240><c> should</c><00:06:53.440><c> be</c><00:06:53.639><c> sted</c><00:06:54.160><c> that</c><00:06:55.039><c> and</c>

00:06:56.189 --> 00:06:56.199 align:start position:0%
contracts should be sted that and
 

00:06:56.199 --> 00:06:59.390 align:start position:0%
contracts should be sted that and
uh<00:06:57.199><c> with</c><00:06:57.479><c> that</c><00:06:57.960><c> actually</c><00:06:58.479><c> we</c><00:06:58.879><c> are</c><00:06:59.039><c> going</c><00:06:59.240><c> to</c>

00:06:59.390 --> 00:06:59.400 align:start position:0%
uh with that actually we are going to
 

00:06:59.400 --> 00:07:00.110 align:start position:0%
uh with that actually we are going to
have

00:07:00.110 --> 00:07:00.120 align:start position:0%
have
 

00:07:00.120 --> 00:07:02.909 align:start position:0%
have
at<00:07:00.800><c> just</c><00:07:01.120><c> one</c><00:07:01.639><c> database</c><00:07:02.120><c> of</c><00:07:02.280><c> all</c><00:07:02.479><c> verified</c>

00:07:02.909 --> 00:07:02.919 align:start position:0%
at just one database of all verified
 

00:07:02.919 --> 00:07:05.550 align:start position:0%
at just one database of all verified
contracts<00:07:03.639><c> shared</c><00:07:04.120><c> between</c><00:07:04.960><c> different</c>

00:07:05.550 --> 00:07:05.560 align:start position:0%
contracts shared between different
 

00:07:05.560 --> 00:07:06.990 align:start position:0%
contracts shared between different
verification

00:07:06.990 --> 00:07:07.000 align:start position:0%
verification
 

00:07:07.000 --> 00:07:09.869 align:start position:0%
verification
providers<00:07:08.000><c> uh</c><00:07:08.319><c> and</c><00:07:08.639><c> I</c><00:07:08.759><c> hope</c><00:07:09.160><c> that</c>

00:07:09.869 --> 00:07:09.879 align:start position:0%
providers uh and I hope that
 

00:07:09.879 --> 00:07:13.270 align:start position:0%
providers uh and I hope that
will<00:07:10.879><c> help</c><00:07:11.199><c> to</c><00:07:11.960><c> increase</c><00:07:12.400><c> the</c>

00:07:13.270 --> 00:07:13.280 align:start position:0%
will help to increase the
 

00:07:13.280 --> 00:07:15.670 align:start position:0%
will help to increase the
decentralization<00:07:14.280><c> of</c><00:07:14.440><c> this</c><00:07:14.720><c> data</c><00:07:15.240><c> so</c><00:07:15.560><c> we're</c>

00:07:15.670 --> 00:07:15.680 align:start position:0%
decentralization of this data so we're
 

00:07:15.680 --> 00:07:18.430 align:start position:0%
decentralization of this data so we're
going<00:07:15.840><c> to</c><00:07:15.960><c> share</c><00:07:16.280><c> some</c><00:07:16.720><c> Market</c><00:07:17.160><c> dams</c><00:07:17.520><c> for</c><00:07:17.800><c> that</c>

00:07:18.430 --> 00:07:18.440 align:start position:0%
going to share some Market dams for that
 

00:07:18.440 --> 00:07:21.309 align:start position:0%
going to share some Market dams for that
uh<00:07:18.599><c> op</c><00:07:19.039><c> access</c><00:07:19.280><c> to</c><00:07:19.400><c> the</c><00:07:19.560><c> database</c><00:07:20.039><c> maybe</c><00:07:20.840><c> and</c>

00:07:21.309 --> 00:07:21.319 align:start position:0%
uh op access to the database maybe and
 

00:07:21.319 --> 00:07:22.710 align:start position:0%
uh op access to the database maybe and
hopefully<00:07:21.720><c> that</c><00:07:21.879><c> will</c>

00:07:22.710 --> 00:07:22.720 align:start position:0%
hopefully that will
 

00:07:22.720 --> 00:07:27.430 align:start position:0%
hopefully that will
work<00:07:23.720><c> all</c><00:07:23.840><c> right</c><00:07:24.879><c> shoots</c><00:07:25.879><c> okay</c><00:07:26.560><c> uh</c><00:07:26.800><c> in</c><00:07:27.039><c> the</c>

00:07:27.430 --> 00:07:27.440 align:start position:0%
work all right shoots okay uh in the
 

00:07:27.440 --> 00:07:31.309 align:start position:0%
work all right shoots okay uh in the
verification<00:07:28.240><c> part</c><00:07:28.560><c> for</c><00:07:29.639><c> contracts</c><00:07:30.319><c> that</c><00:07:30.520><c> use</c>

00:07:31.309 --> 00:07:31.319 align:start position:0%
verification part for contracts that use
 

00:07:31.319 --> 00:07:34.909 align:start position:0%
verification part for contracts that use
Library<00:07:32.319><c> looks</c><00:07:32.560><c> like</c><00:07:32.720><c> we</c><00:07:32.840><c> are</c><00:07:33.039><c> using</c><00:07:33.919><c> the</c>

00:07:34.909 --> 00:07:34.919 align:start position:0%
Library looks like we are using the
 

00:07:34.919 --> 00:07:38.790 align:start position:0%
Library looks like we are using the
reference<00:07:35.680><c> by</c><00:07:35.960><c> code</c><00:07:36.280><c> from</c><00:07:36.560><c> the</c><00:07:37.120><c> deploy</c><00:07:37.720><c> by</c><00:07:38.639><c> is</c>

00:07:38.790 --> 00:07:38.800 align:start position:0%
reference by code from the deploy by is
 

00:07:38.800 --> 00:07:40.710 align:start position:0%
reference by code from the deploy by is
that

00:07:40.710 --> 00:07:40.720 align:start position:0%
that
 

00:07:40.720 --> 00:07:44.670 align:start position:0%
that
safe<00:07:41.720><c> uh</c><00:07:42.240><c> yes</c><00:07:42.520><c> that</c><00:07:42.720><c> is</c><00:07:43.039><c> safe</c><00:07:43.919><c> uh</c>

00:07:44.670 --> 00:07:44.680 align:start position:0%
safe uh yes that is safe uh
 

00:07:44.680 --> 00:07:47.710 align:start position:0%
safe uh yes that is safe uh
because<00:07:45.680><c> after</c><00:07:46.120><c> the</c><00:07:46.319><c> compilation</c><00:07:46.919><c> we've</c><00:07:47.159><c> seen</c>

00:07:47.710 --> 00:07:47.720 align:start position:0%
because after the compilation we've seen
 

00:07:47.720 --> 00:07:51.309 align:start position:0%
because after the compilation we've seen
that<00:07:48.159><c> uh</c><00:07:48.800><c> this</c><00:07:49.400><c> 20</c><00:07:49.840><c> bytes</c>

00:07:51.309 --> 00:07:51.319 align:start position:0%
that uh this 20 bytes
 

00:07:51.319 --> 00:07:54.029 align:start position:0%
that uh this 20 bytes
the<00:07:52.319><c> as</c><00:07:52.759><c> that</c><00:07:52.960><c> the</c><00:07:53.080><c> Library</c><00:07:53.479><c> address</c><00:07:53.840><c> was</c>

00:07:54.029 --> 00:07:54.039 align:start position:0%
the as that the Library address was
 

00:07:54.039 --> 00:07:58.189 align:start position:0%
the as that the Library address was
assumed<00:07:54.400><c> to</c><00:07:54.520><c> be</c><00:07:54.720><c> put</c><00:07:55.000><c> inside</c><00:07:55.680><c> those</c><00:07:56.039><c> 20</c><00:07:56.680><c> bytes</c>

00:07:58.189 --> 00:07:58.199 align:start position:0%
assumed to be put inside those 20 bytes
 

00:07:58.199 --> 00:08:02.309 align:start position:0%
assumed to be put inside those 20 bytes
uh<00:07:59.199><c> by</c><00:07:59.599><c> the</c><00:07:59.800><c> contract</c><00:08:00.240><c> code</c><00:08:00.560><c> itself</c><00:08:01.199><c> and</c><00:08:01.720><c> uh</c>

00:08:02.309 --> 00:08:02.319 align:start position:0%
uh by the contract code itself and uh
 

00:08:02.319 --> 00:08:03.990 align:start position:0%
uh by the contract code itself and uh
this<00:08:02.520><c> address</c><00:08:02.800><c> can</c><00:08:02.960><c> be</c><00:08:03.120><c> anything</c><00:08:03.479><c> actually</c><00:08:03.840><c> so</c>

00:08:03.990 --> 00:08:04.000 align:start position:0%
this address can be anything actually so
 

00:08:04.000 --> 00:08:07.350 align:start position:0%
this address can be anything actually so
we<00:08:04.199><c> just</c><00:08:04.479><c> take</c><00:08:05.000><c> uh</c><00:08:05.440><c> the</c><00:08:06.039><c> actual</c><00:08:06.560><c> value</c><00:08:06.919><c> so</c><00:08:07.159><c> we</c>

00:08:07.350 --> 00:08:07.360 align:start position:0%
we just take uh the actual value so we
 

00:08:07.360 --> 00:08:11.029 align:start position:0%
we just take uh the actual value so we
assume<00:08:07.759><c> that</c><00:08:08.360><c> the</c><00:08:08.680><c> onchain</c><00:08:09.199><c> code</c><00:08:10.039><c> is</c><00:08:10.680><c> Al</c>

00:08:11.029 --> 00:08:11.039 align:start position:0%
assume that the onchain code is Al
 

00:08:11.039 --> 00:08:13.029 align:start position:0%
assume that the onchain code is Al
should<00:08:11.319><c> also</c><00:08:11.599><c> contain</c><00:08:12.240><c> the</c><00:08:12.400><c> Library</c><00:08:12.759><c> address</c>

00:08:13.029 --> 00:08:13.039 align:start position:0%
should also contain the Library address
 

00:08:13.039 --> 00:08:15.990 align:start position:0%
should also contain the Library address
at<00:08:13.199><c> this</c><00:08:13.440><c> place</c><00:08:13.759><c> and</c><00:08:13.919><c> take</c><00:08:14.360><c> it</c>

00:08:15.990 --> 00:08:16.000 align:start position:0%
at this place and take it
 

00:08:16.000 --> 00:08:21.589 align:start position:0%
at this place and take it
uh<00:08:17.000><c> as</c><00:08:17.599><c> uh</c><00:08:18.599><c> as</c><00:08:18.759><c> an</c><00:08:19.360><c> well</c><00:08:19.759><c> our</c><00:08:20.159><c> address</c><00:08:21.159><c> so</c><00:08:21.440><c> it</c>

00:08:21.589 --> 00:08:21.599 align:start position:0%
uh as uh as an well our address so it
 

00:08:21.599 --> 00:08:23.629 align:start position:0%
uh as uh as an well our address so it
it's<00:08:21.800><c> it's</c><00:08:22.000><c> actually</c><00:08:22.319><c> safe</c><00:08:22.759><c> just</c><00:08:22.960><c> because</c>

00:08:23.629 --> 00:08:23.639 align:start position:0%
it's it's actually safe just because
 

00:08:23.639 --> 00:08:25.749 align:start position:0%
it's it's actually safe just because
this<00:08:24.159><c> offset</c><00:08:24.639><c> was</c><00:08:24.919><c> in</c>

00:08:25.749 --> 00:08:25.759 align:start position:0%
this offset was in
 

00:08:25.759 --> 00:08:30.990 align:start position:0%
this offset was in
the<00:08:26.759><c> standard</c><00:08:27.199><c> Json</c><00:08:27.800><c> output</c><00:08:28.800><c> section</c>

00:08:30.990 --> 00:08:31.000 align:start position:0%
the standard Json output section
 

00:08:31.000 --> 00:08:33.269 align:start position:0%
the standard Json output section
all<00:08:31.240><c> right</c><00:08:31.759><c> thank</c><00:08:31.960><c> you</c><00:08:32.279><c> so</c><00:08:32.560><c> much</c><00:08:32.839><c> for</c><00:08:33.080><c> this</c>

00:08:33.269 --> 00:08:33.279 align:start position:0%
all right thank you so much for this
 

00:08:33.279 --> 00:08:36.190 align:start position:0%
all right thank you so much for this
session<00:08:33.880><c> please</c><00:08:34.279><c> help</c><00:08:34.519><c> me</c><00:08:35.360><c> appreciate</c><00:08:35.959><c> our</c>

00:08:36.190 --> 00:08:36.200 align:start position:0%
session please help me appreciate our
 

00:08:36.200 --> 00:08:40.640 align:start position:0%
session please help me appreciate our
amazing<00:08:36.640><c> speaker</c><00:08:37.640><c> rain</c>