►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everybody
and
welcome
to
the
team
grothendieck
weekly
status
meeting
today
is
tuesday,
the
seventh
of
februari.
So
this
meeting
is
slightly
unusual
in
that
it's
it's
going
to
be
the
first,
it's
the
first
one
that's
going
to
be
available
to
the
general
public.
So
with
that
in
mind,
my
name
is
Alan
McSherry.
A
We
have
Adam
Allen,
Bergner,
mukesh,
yan
and
Radek
here
so
I'll
just
give
a
brief
introduction
and
talk
a
little
bit
about
what
what
phase
were
currently
in
the
there
are
four
phases
really
in
the
in
the
timeline
for
for
this
release,
the
current
to
that
were
working
on
our
block
chain
synchronization.
So
that's
the
etherium
classic
blockchain
download
and
everything
to
do
with
that,
and
coupled
with
that
is
the
is
transaction
execution.
A
So
that's
when
you
do
download
your
block
full
of
transactions
that
you
execute
them
all
and
get
your
state
up
to
date,
which
is
really
the
the
EVM
and
the
main
engine
of
that
of
the
blockchain.
So,
within
that,
for
the
last
week,
what
we've
been
working
on
is
is
to
support
fast,
download
and
we've
worked
with
in
the
transaction
execution
and
also
so
fast
download,
Adam
I
think
you
were
going
to
give
us
a
demonstration
of
where
we're
at
there.
C
B
B
The
kind
of
download,
when
you
pick
the
target
block
and
until
this
block
you
exit
you,
do
not
execute
transaction,
but
only
download
blocks,
receipts
and
state
three
from
the
other
nodes,
believing
that
they
are
correct
and
you
can
check
this
discrepancy
shows
that
are
in
the
block
chain
and
then
from
the
block.
You
just
sync
our
money,
so
you
execute
the
transaction.
So
what
I
would
like
to
show
is
that
we
I
use
this
helium
classic
browser
to
pick
up
be
trotted
block
in
the
past
is
from
today
like
three
hours
before.
B
To
be
sure
that
is,
there
is
no
fork
in
the
block
in
the
chain,
and
then
I
set
this
blog
as
a
target
as
long
that
I
won't
sink
to
in
application
and
then,
after
after
I
run
the
application,
the
application
will
download
will
try
to
download
all
the
blocks
from
Genesis
block
to
this
target
blog
and
also
will
download
MPG
stage
three
four,
the
fourth
at
target
block.
Actually
it
takes
a
little
died,
actually
the
substantial
amount
of
time
to
download
all
blocks.
B
B
So
here
we
starting-
and
this
is
the
sink
running-
not
too
exciting-
so
maybe
stop
here,
and
then
I
have
this
long
in
this
occurred
in
the
separate
file,
and
I
feel
I
have
the
parts
that
are
required
for
required
to
the
demo
download
this
song
I'm
printing.
The
blocks
block
elements,
motion
elements
with
this
message
so
when
I
receive
complete,
sets
of
block
heaters,
work,
receipt,
Android
bodies
and
print
them
here.
So
here
are
the
10
block
bodies
because
we
download
them
in
chunks
of
10.
We
can
configure
that
to
other
number.
B
We
do
not
download
the
Genesis
book,
because
this
is
this-
was
one
of
the
difference
between
parity
client
and
go
ET.
Rien
client
that
they
handle
this
request
differently.
Mainly
the
receipts
for
the
Genesis
block
is
provided
to
us
by
Goethe,
Liam
client
and
the
polity.
Client
returned
empty
messages,
so
for
Goethe
Liam
we
got
an
empty
added
the
list
and
for
it
for
party.
B
We
get
nothing,
and
this
was
sort
of
the
issue
of
issue
for
us,
because
we
assume
that
the
parity
would
behave
in
the
same
way
and
we
treated
this
as
a
failure
in
sync.
So
this
is
this
and
why
we
do
not
download
it,
and
I
would
also
like
to
show
that
we
actually
have
some
EVN
called
downloaded
for
the
contracts
by
this.
B
One
I
think
is
the
EDM
code
of
the
particular
contract
that
was
in
the
state
three
and
maybe
example
of
the
contract
storage,
because
it
is
also
different
because
the
contract
storage
is
preserved
in
the
same
structure,
the
same
type
of
structure
as
the
MPT
state,
but
in
the
leaf
nodes
that
are
value
stored
by
contracts,
not
the
accounts
and
in
the
NP
key
stage.
Three
in
the
leaf
node
there
are
accounts.
B
Not
all
right,
it's
not
like
not
this
is
it
okay,
so
we
got
this
load
of
NPT
so
not
empty,
but
contact
state
three
with
the
value
of
this
and
I
think
it's
I
can
also
show
that
we
got
some
accounts,
while
downloading,
which
are
encoded
in
the
which
I
adult
in
RL
can
coated
so
not
much
to
see
here,
but
we
are
based
on
this
account.
We
then
it
can
download
the
ATM
code
and
the
storage
if
it's
provided
inside
them,
so
I
think
it's
pretty
much.
It.
A
Okay,
pretty
good,
and
it
was
good
to
hear
someone
in
the
background-
got
super
excited
about
getting
the
leaf
node
that
was
nice
to
hear.
Okay.
Does
anyone
have
any
questions?
Four
for
Adam.
A
B
D
A
Okay:
okay,
thanks.
Anyone
have
any
questions
for
Adam,
okay,
great
thanks
a
lot
and
just
to
say
that
that's
that's
part
of
the
the
blockchain
sync
sort
of
phase
which
we'd
expect
to
we'd
expect
to
come
in
and
sometime
in
March,
that's
the
overall
phase.
So
so
that's
what
we're
going
to
working
on
the
other
phase
that
were
working
on
is
the
transaction,
execution
and
I
think
we
have
a
little.
We
have
a
demonstration
of
where
we're
at
this
week
from
braddock.
Please.
E
Yes,
hi,
so
I've
been
working
for
the
past
several
days
on
providing
gas
consumption
to
to
all
the
implemented
op
codes
that
we
have
and
I'd
like
to
demonstrate.
The
results.
A
E
E
It's
either
it
has
two
functions:
I
either
calculate
a
new,
a
new
Fibonacci
number
or
get
the
one
that
has
been
stalled
and
in
the
contract
storage
we
also
have
a
have
a
small
tool,
but
enables
us
to
to
run
the
EVM
code
in
isolation
from
the
rest
system.
So
it
uses
a
solidity
compiler
and
needs
to
to
compile
the
code
and
to
get
its
avi,
which
enables
us
to
invoke
the
functions
in
that
human
friendly
way.
A
E
Yes,
of
course,
so
ballots.
E
Let
the
channel
machine
spin
up.
Okay,
we
have
the
results,
and
so,
as
you
can
see
you,
we
have
a
program
returned
calculate
number,
the
fifth
number
of
the
signal
sequence
and
we
have
and
the
gas
spends
here
the
other.
The
second
function
invocation
just
simply
retrieving
this
toad
and
number
is,
is
much
cheaper
than
that.
E
Now,
let
me
let
me
show
you
the
young
again.
If
you
ever
tried
to
calculate
Fibonacci
numbers,
you
might
notice
that
this
is
not
the
most
efficient
way
to
do
that.
In
fact,
it's
like
an
academic
example
of
how
not
to
do
it,
and
the
reason
is
that
this,
this
partial
summation
is,
is
performed
multiple
times
redundantly.
E
E
I
forgot
one
thing
and
I've
added
this:
this
second
parameter
to
and
to
dig
it
was
asked
to
specify
the
gas
and
never
mind
the
intuitive
way
of
providing
that
it's
just
for
the
purpose
of
this
demo,
and
so
here
I'm
providing
a
10
million
gas
and
so
to
run
that
particular
function,
so
yeah
and
I'm,
and
the
arguments
are
in
from
0
to
20
in
in
the
intervals
of
four.
So,
okay,
let's.
C
E
E
D
E
A
E
E
E
B
A
Okay,
that's
that's
pretty
cool,
so
you've
got
the
the
shape
of
the
of
the
evm
together
and
you've
got
several
opcodes
implemented
and
you've
got
some
of
the
gas
calculation
sorted
as
well.
So
then,
with
that
in
place,
it's
a
it's
a
question
of
taking
on
some
of
the
completing
some
of
the
other
opcodes
and
spinning
at
completion.
Is
that
that's
about
right?
Yes,
exactly.
A
No
okay,
that's
great
thanks
a
lot
attic
and
just
in
terms
of
the
TX,
the
transaction
execution.
That
phase
should
also
be
coming
in
in
sometime
in
march,
and
there's
a
bit
of
there's
a
bit
of
leeway
there
just
in
terms
of
some
of
the
risk,
as
as
a
lot
of
you
know,
we
haven't
done
this
before
so
so
that
that's
a
fairly
broad
window,
but
I
would
expect
some
time
in
in
march,
so
mr.
Allen
Verner,
we
have
you
have
something
that
you're
going
to
show
us
with
respect
to
the
block
at
dumping.
A
D
D
D
D
D
Ok,
so
here
you
will
see
that
and
your
damping,
they
hunting
on
lists
and
the
transactions
and
stuff,
and
how?
How
are
you
using
this?
Ok
I
can
show
you
hear
from
sampler.
We
have
the
code,
we
use
to
validate
blocks,
and
this
is
the
testing
that
we
have
great.
It
is
fine
and
we
can
copy
paste
information
that
we
have
done
so
we
can
create
this
that
use
actual
real
data,
a
very
unique
in
our
environment,
so
I
think.
A
Ok,
pretty
cool
and
I'm
gonna
have
to
have
a
closer
look
at
that
yeah
I
I,
haven't
I,
haven't
actually
looked
at
that,
as
of
yet
I
did
manage
to
clone
it,
but
not
look
at
it
closely.
Ok,
thanks
very
much,
and
so
that's
the
demos
for
today.
So
then,
and
just
to
recap,
I
guess.
Last
week
we
were
working
on
supporting
fast
download
and
we
did
the
the
the
framework
I
guess
for
the
transaction
execution.
A
The
overall
phase
is
that
those
things
are
in
should
both
be
coming
in
in
March
the
following
on
phases
after
that
are
related
to
new
block
creation,
which
includes
mining
and
then
the
command
and
query
interface,
which
is
which,
of
course
is,
is
what
makes
the
whole
thing
tick.
So
that
concludes
the
jason
or
pc
and
and
stuff
like
that,
so
that
will
be
coming
after
that
and
for
the
next
week
in
particular,
we're
going
to
continue
working
on
support
fast
on
supporting
the
fast
download,
because
we
have
to
include
our
persistence.
A
We
have
to
spin
out
some
of
them.
Some
of
the
more
complicated
op
codes
so
create
would
be
one
and
I
think
we
included
suicide
in
as
another
op
code
that
needs
to
go
in.
So
that's
those
basically
more
of
the
same
is
what's
on
the
agenda
for
for
next
week
for
next
week.
Does
anyone
have
any
questions.
C
May
I
ask
some
more
general
questions
regarding
the
project
milestones
for
the
future.
Is
that
an
appropriate
time?
Allen
yeah?
Yes,
please,
nickel.
Could
you
give
us
a
brief
overview
of
where
the
client
is
right
now
and
what
kind
of
high-level
feature
will
be
introduced
in
the
next
few
weeks
and
months.
A
Yes,
certainly
so
really,
there's
four
major
feature
areas
that
we're
looking
at
one
is
blockchain
synchronization.
So
that's
how
to
get
the
blockchain
from
another
peer
to
our
peer
on
how
to
give
the
blockchain
to
another
peer
from
our
peer.
That
phase
is,
is,
is
ongoing
at
the
moment
and
should
we
were
working
towards
demonstration
which
has
been
specified
and
that
should
come
in
sometime
in
March
and
others.
So
I,
there's
no
exact
date
for
that.
But
we'd
expect
spend
some
time
in
march
in
parallel
with
that.
A
We're
working
on
the
transaction
execution
which
includes
the
EVM
and
the
result
of
that,
will
again
be
a
demonstration
which
will
which
will
show
that
we
are
able
to
take
every
transaction
from
the
from
the
Genesis
block
and
come
up
with
a
state.
Try
that's
the
same
as
the
state
try
for
every
other
client.
A
So
that
would
be
our
how
we
show
that,
where
I
will
execute
all
of
those
transactions
correctly,
that
phase
is
also
ongoing
and
should
come
in
in
March
as
well,
and
then
the
other
two
phases
are
related
to
are
called
new
block
creation
and
command
and
query
interface.
So
the
new
block
creation
is
related
to
to
mining
and
everything
that
that's
involved
in
generating
a
a
new
block.
A
Is
that
are
needed
to
connect
up
the
client
to
two
useful
browsers
so
yeah,
that's
those
are
really
the
four
before
phases
and
then,
when
we
have
that
we'd
expect
to
to
start
looking
at
some
optimizations
and
some
security,
auditing
and
stuff,
like
that.
Until
we
can
get
to
a
point
where
we
can
say.
This
is
a
we're
happy
that
this
is
1.0
and.
C
We
will
be
able
to
publish
this
milestones,
to
high-level
milestones,
of
course,
on
average
case
website,
so
everybody
from
the
uterine
classic
community
was
following
could
have
a
bit
of
a
guideline
of
what
to
expect
what
within
reason.
Of
course,
software
can
take
longer
than
one
expects,
and
sometimes
I
get
shorter,
but
it's
the
minority
of
times
is
that
is
that
a
fair
assessment
yeah.
A
Absolutely
absolutely
exactly,
as
you've
said,
you
know
you
aim,
for
we
aim
for
to
pull
that
in
a
bit,
but
history
has
taught
us
you
know
not
to
not
to
over
promise.
Okay.