►
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
A
Let's
move
on
last
week
we
worked
on
last
week,
we've
been
working
on
block
sink
down,
so
that's
part
of
the
that's
the
overall
phase
that
we're
really
working
on
working
towards
a
demo
of
our
block
synchronization.
So
the
part
that
we're
currently
and
happened
for
the
last
couple
of
weeks
working
on
is
the
is
the
fast
download
and
we're
also
showing
the
EVM
functionality
forward
as
well.
A
B
Okay,
so
I'm
going
to
start
the
application
now
I've
added
a
few
booths
short
notes
that
it
should
connect
to
and
in
a
short
while,
you
should
see
that
it
actually
starts
sinking
with
multiple
Pierce,
so
I've
prepared
a
small
status
update
output
that
we
could
track.
So
you
can
see
the
number
of
blocks
download
that,
by
the
way,
don't
pay
attention
to
the
exceptions
that
are
frowned.
B
These
are
the
messages
that
we
don't
have
implemented
yet
so
this
is
not
relevant
and
you
can
see
that
we
were
actually
downloading
the
blocks
from
53
a
maximum
of
eight
peers.
At
the
moment
and
aside
the
downloading
blogs,
we
will
be
also
downloading
the
state
tree
it's
actually
implemented,
but
the
processing
performance
isn't
really
great
at
the
moment
so
for
the
purpose
of
the
demo
I
disabled
it
so
that
we
can
better
see
that
we're
actually
getting
the
blocks
from
from
multiple
peers.
So
we
also
have
the
functionality
of
blacklisting
appear.
B
That
means
if,
for
example,
the
pier
disappoints
us
like
this
one
here
I
can
probably
stop
it
now
I.
Will
we
requested
the
black
bodies
from
one
of
the
piers,
but
he
didn't
respond
us
within
30
seconds,
so
we
decided
to
blacklist
it
and
we're
not
going
to
use
it
for
for
that
period,
and
after
that
we
can
try
to
sync
with
him
again.
This,
of
course,
can
be
adjusted
to
like
few
minutes.
My
beasts
is
the
highest
blacklist
period.
I
would
say
it's
reasonable
and
yeah
that
that's
basically
it
do.
A
B
A
B
B
At
the
moment
we
have
like
we
maintain
a
list
of
the
visitors,
the
tears
that
I
will
send
a
request
and
we
are
waiting
for
the
response
and
the
other
pool
is
available
Pierce.
These
are
the
ones
that
we're
not
waiting
for
the
response
from
them,
so
the
available
Pierce.
We
ask
them
for
the
next
stuff.
A
C
C
C
B
C
And
here
I'm
going
to
ask
for
an
end
point:
it's
in
the
air
pc
work
in
progress
and
I'm
going
to
ask
for
or
specific
blog
the
blog
it's
not
there,
and
this
is
a
this-
is
I'm
going
to
show
you
the
application
logs
there?
You
will
see
that
the
block
has
arrived
so
once
I
asked
for
that
block
I
can't
retrieve
it
and
now
I'm
going
to
stamp
application
and
stop
the
parity
known.
C
C
A
C
Can
show
you
a
small
tool
that
we
haven't
created
and
I'm
going
to
share
my
screen
again.
Sorry
for
that
and
asuma
now,
some
a
few
clients
a
John,
come
with
a
tool
in
order
to
query
and
to
operate
chance
against
it.
For
example,
gear
it
provides
a
JavaScript
console,
but
a
party
doesn't
so
far.
We
have
pull.
You
can
install
it.
It's
already
on
mbm
side,
it's
called
well
three
and
a.
C
C
A
A
A
A
Part
of
a
sign
transaction
is
the
is
the
point
sign
which,
according
to
the
documentation
going
to
the
yellow
paper,
really
should
have
a
value,
27
or
or
28.
But
that's
that's
not
really
the
case
Adam
you.
You
discovered
that
there's
there's
other
values
that
are
floating
around
there
on
the
net
and
why?
Yes,.
E
So
this
is
because
the
there
was
possibility
of
replying
transaction
from
one
chain
on
an
on
another,
so
there
was
improvement
proposal
introduced.
That
is
for
mitigating
this
issue,
but
there
is
no
for
block
number
for
this.
Yet
so
it's
I
think
work
in
progress.
It's
idiom
improvement
proposal,
155
but
parity
and
get
already
implemented
this
functionality.
E
So
we
decided
to
also
add
it
to
our
client
to
not
ignore
the
transaction
that
may
be
correct
in
the
future.
But
what
concerns
us
is
that
this
new
implementation,
some,
I
may
say,
violates
the
yellow
paper,
which
requires
certain
length
of
the
point.
Sign
beats
to
be
used
and
it's
about
five
bits
and
the
implementation
use
eight
bits
which
makes
some
values
overflow.
E
For
example,
the
new
point
sign
is
calculated
by
using
something
called
chain
ID,
which
was
introduced
and,
for
example,
for
ET
rien
classic
the
chain
ID
that
was
taken
is
61,
so
this
new
formula
gives
a
number
bigger
than
max
value
of
22
to
25
and
even
2
to
the
8.
So
there
is
an
overflow
and
we
are
receiving
transactions
that
have
point
sign
like
minus
ninety,
nine
or
minus
ninety
eight.
A
A
E
D
Rather
whether
we
did
with
a
really
good,
because
so
anything
today,
because
we
have-
we
did
a
lot
of
work
during
the
last
week,
but
managed
to
finish
only
one
thing
actually:
phenolic
finished
whole
gas
calculation
logic.
So
now
we
are
able
to
down
our
programs
on
now
any
p.m.
and
check
what
I
will
see
how
much
gas
such
program
consumed
so
I,
a
very
simple
test
which
generates
random
programs.
You
can
see
them
here
in
the
first
column,
for
example,
it's
such
a
randomly
generated
program
consisting
of
seven
opcodes.
D
This
program
was
run
on
the
PM
in
second
column.
Nip
you
can
see
how
much
gas
each
operation
consumed
equals
just
say
that
equality
Wilmot
is
more
typical,
multiplication,
medulla,
etc
and
infrared
column.
You
can
see
a
cow
stock
was
changed,
a
size
of
the
stack,
for
example,
multi,
notation,
medulla,
post
three
items
from
the
start
and
pushes
one
item
back.
So
we
can
see
the
difference
of
of
two
and
for
each
round
of
the
test.
D
There
are
no
like
10
programs
did
like
that.
You
can
sit
in
here
and
some
very
basic
tests
are
run
on.
It.
I'll
try
to
write
it
once
again.
It's
sometimes
sometimes
files
like.
Oh,
it
worked
again
so
this
time,
let's
see
much
simpler
program
consisting
only
of
photo
op
codes
yeah.
So
this
is
it
we
can
see
our
other
programs
already
done
more
or
less
flawlessly
on
BBM
they
consumed
as
they
flow
either
spots,
while
it's
very,
very
rare.
D
A
Thanks
young
so
yeah,
it's
like
you've
generated
a
few
random
op
codes
and
put
them
together
and
just
shown
the
shown
the
gas
used,
yeah,
ok,
cool
and
I.
Guess,
as
you've
said,
there
were
sort
of
we've
done,
probably
most
of
the
most
of
the
opcodes
and
some
of
the
more
tricky
ones
we're
now
we're
going
to
have
to
approach.
Probably
next.
D
A
A
No
okay,
thanks
thanks
guys
for
for
the
demos
and
stuff
on
the
EVM
and
yeah.
That's
that's
about
it.
As
I
said
at
the
start
of
the
meeting,
I
think
we're
roughly
tracking
and
the
only
other
thing
too
I
guess
mention.
Is
we
got
together
in
Warsaw
for
Thursday
and
Friday
of
last
week
and
I
have
elicited
some
feedback
and
I
think
it
went
fairly
well,
I
think
everybody
thinks
it
went
fairly.
A
Well,
we
spent
quite
a
bit
of
time
with
the
whiteboard
and
filled
in
a
lot
of
the
any
of
the
rough
edges
that
might
be.
That
might
be
there
in
terms
of
each
other's
understanding
and
we
went
over
I
guess
the
the
big
picture
in
terms
of
the
sort
of
phases
and
and
how
we
intend
to
proceed
so
overall
I
think
it
went
very
well,
and
it
was
very,
very
useful
and
yeah
thanks
guys
for
for
showing
me
a
little
bit
of
Warsaw
as
well
and.
A
That's
it
for
next
week,
we're
still
working
towards
as
I
mentioned
is
the
third
time
I
mentioned
we're
still
working
towards
our
block.
Sank
demo.
We
do
have
a
bunch
of
tasks
in
the
in
the
backlog.
I
guess
two
of
the
big
ones
will
be
looking
at
will
be
acting
as
a
host
for
blocks,
so
distributing
blocks
from
our
particular
cache
and
then
the
second
will
be
some
of
the
more
the
more
significant
and
evm
colds
that
involve
as
young
mentioned
driving
at
the
the
API.