►
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
Quite
a
few
people
have
been
off,
so
there's
been
a
bit
of
reduced
capacity,
but
some
work
has
still
gotten
done
so,
where
we're
at
over
the
last
little
while
is
we've
been
taking
some
of
the
results
of
the
extended
testing
that
we
did
in
preparation
for
the
beta
I'm
working
through
some
of
the
things
that
didn't
make
it
into
the
release
that
we
wanted
to
to
do.
We've
also
continued
with
the
etherium
test
suite
trying
to
run
that
across
our
code
and
also
looking
at
the
next.
B
B
How
the
actually
virtual
machine
should
work,
so
this
is
the
second
iteration
of
going
through
the
III
test
suite
and
previously
me
that
the
portion
and,
as
was
noted,
those
tests
didn't
really
test
the
eight
instructions.
B
B
A
B
They
do
not
run
all
of
them
all
those
those
tests
have
been,
firstly
designed
for
CPP
a
the
etherium
and
so
the
clients
only
leverage
them
so
I
guess
I.
Guess
at
this
point
CP
theorem,
should
it
should
be
a
stand-up
that
we
that
we
look
up
to
and
finally
at
least
I
have
some
knowledge
of
C++,
which
can
be
said
about
rust
or
go.
B
B
A
B
Not
sure
if
I
think
medium
is
quite
slow
to
be
honest,
I'm
not
sure
relative
to
I
have
to
find
out,
but
either
way
I
need
that
I
need
to
run
a
good
IDE
on
that
machine.
So
maybe,
if
I
somehow
set
up
SSH
FS
fact
file
system
over
SSH-
maybe
maybe
difficult
well
done,
but
but
I
would
need
a
really
solid
machine
for
that
to
be
a
speed,
improvement.
Okay,.
A
A
So,
just
on
the
you
know,
speaking
about
the
reference
client
I
mean
obviously
there's
three
there's
several
clients
for
four
aetherium,
and
so
these
edge
cases,
though,
that
we
were
actually
dealing
with
I
mean
ultimately
the
the
absolute
truth
is,
is
in
the
bytes
that
are
produced
by
the
bytes
that
are
produced
by
processing
a
transaction
right,
so
I
mean
it's
kind
of
these
edge
cases.
If
they
come
up
either
all
the
clients
produce
the
same
bytes
or
or
there's
a
there's,
a
problem
right
well,
yeah.
B
And
it's
interesting
whether
actually
all
the
three
existing
clients
are
consistent
with
those
edge
cases,
because
I
saw
some
like
parity
and
and
Gath
simply
excluding
some
of
the
tests
from
that
sweet.
Yes,
I
saw,
that's
ethion
can
run
them
off,
but
then
who
really
uses
cpp
interview
for,
for
the
actual,
looks
for
the
actual
note
well.
A
A
We're
just
we're
not
there
yet,
but
we
might
be
again
I
guess
what
I'm
saying
is
that
I
mean
if
we,
if
we're
talking
about
using
CPP
as
a
as
a
reference
client,
and
we
have
good
familiarity
with
parity,
you
know
for
some
of
these
edge
cases.
Could
we
create
a
transaction
that
you
know
that
splits
the
network,
not
that
we
would
do
that
on
purpose,
but
in
terms
of
testing
whether
the
implementations
are
identical.
B
A
C
A
C
Yes,
exactly
I
was
diabetes,
new
code
bases,
I,
remember
and
first
part
of
the
skit
was
establishing
the
best
sweet,
best
picture
to
run
all
of
the
old
of
tests
and
now
I'm
going
in
the
second
part
of
this
task,
as
fixing
is
failing
test
one
by
one
a
static
mention.
Sometimes
we
are
failing
consumer
really
educating
edge
cases
like,
for
example,
he,
for
example,.
C
A
Ok,
great,
hey
thanks
Konrad,
so
I'm,
just
gonna,
say
hello
to
Merkel
Mirko.
Have
you
got
your
M?
Have
you
got
a
working
and
microphone
today.
A
No
not
to
worry
and
welcome
Merkel.
This
is
actually
your
first
I
guess
day,
so
also
your
first
status
meeting.
So
just
yeah.
That's
that's
fine!
All
right!
No
problem!
That's
that's
perfect!
Thanks,
Michael
and
ok,
so
I
wanna
Nico,
you
guys
have
been
have
also
been
a
little
bit
busy.
Island
you've
been
you've,
been
back
since
Wednesday
right.
D
It's
time,
I
returned
last
Wednesday
and
I've
been
taking
dust
from
the
catalog
and
they
won
remarkable
once
I
can
mention.
Now
is
I'm
tracking
down
an
issue
with
leveldb
and
it's
a
tough
one
but
I'm
doing
it
from
progress
and
I
was
at
least
I
was
able
to
reproduce
the
error
several
times.
So
yes,
yes,
so
it's
not
like
it's
kind
of
it
seems
to
be
an
Aurora
in
terms
of
maybe
concurrency
or
something
related
a
lot
like
that.
D
A
D
It
is
faster
because
it's
not
executing
blobs
or
it's
not
processing
the
blockchain,
but
it's
using
the
metal
Patricia
try
a
lot,
and
so
yes,
it's
faster,
but
it's
because
it's
doing
something
else.
Okay,
the
error
was,
it
usually
happens
when
trying
to
access
11
DB
file.
That
was
not
presented
file
system
yeah
and
we
are
not
sure
what
the
error
comes
from.
It
has
been
reported
on
level
de
it
have
repo.
D
A
And
I
guess
I
mean
we're
not
too
surprised
that
there
are
that
there
may
be
to
me
that
there's
a
bug
in
them
in
that
level
DB
ports,
because
it
was
a
I
think
it
was
pretty
much
an
automated
semi,
automated
port
that
wasn't
really
worked
on
once
it
actually
began.
You
know
it
wasn't
really
tested
in
anger.
Shall
we
say
yes.
D
But
let
me
say
that
it
has
several
tests
at
least
like
like
a
t-test
and
there
there
being
some
fixes
related
to
this
so
not
recently,
but
there
were
some
fixes
who
are
made.
So
yes,
it's
a
just,
as
you
say,
but
I
don't
know
some.
Some
work
has
been
done
at
this
library,
so
maybe
just
a
really
edge
case.
D
A
A
E
So
well,
a
in
the
last
weeks,
or
so
I
mean
looking
at
several
a
reskin
I
know,
I've
been
looking
at
several
a
bug
that
we
had
reported.
Some
of
them
were
really
fixing
our
code
base
as,
for
example,
a
port
cuts
in
receiving
transactions
from
parity
and
center
section
party.
It
seems
to
have
been
fixed
during
the
disfavored
report,
I
think
a
couple
a
month
ago.
E
So
during
the
audience
middle
pass
fix
I
mean
also
recently
we
can
look
at
Jason
HTTP
support,
which
is
billed
for
the
a
supporting
add
a
loss
bullet
for
this
yesterday.
Well,
some
testing
of
this
was
done
using
a
self-signed
certificate
and
there's
no
purpose
for
for
this,
and
a
another
important
test
that
I'm
been
looking
at
is
a.
E
There
was
a
report
that
our
fullness
of
the
multiple
different
tree
wasn't
very
good,
and
it
seemed
that
this
well
most
of
the
time
spent
during
the
years
of
ml
/
3
is
with
database,
but
there
I
created
a
small
improvement,
that
of
a
caching.
They
some
that
I
obtained
from
the
nodes
which
a
optimizes
the
use
of
the
map
initiative
and
what
those
who
are
some
of
the
important
tasks
that
they've
been
working
on
there.
Okay,.
D
A
E
A
Know,
that's.
That
seems
like
a
good
improvement.
I
mean
that's
roughly
20
percent,
so
so
not
bad
I
mean
obviously
that's
that's
just
a
single.
You
know
that
doesn't
that
doesn't
exercise,
maybe
the
use
case
that
we're
actually
experiencing
when
we
use
in
there,
but
it's
still
a
significant
improvement.
A
Okay
and
the
other
one
you
mentioned
was
the
was
an
HTTP
which,
as
you
correctly
say,
is,
is
part
of
this
support
for
the
wallet
integration,
so
that
leads
us
nicely
on
to
the
future.
So
as
a
just
to
recap,
we
have
basically
between
between
being
out
and
fixing
other
stuff,
which
is
not
quite
finished.
Yet
we
still
to
fix
a
few
bits
and
pieces.
We're
now
gearing
up
for
the
next
important
part,
which
is
the
Daedalus
integration
wallet
and
there's
there's
tasks.
A
Integration
with
the
Daedalus
wallet,
I
should
say
and
there's
tasks
on
the
on
the
board.
For
that
and
that
will
has
already
started.
It'll
continue
certainly
this
week
and
we
have
some
I
guess
external
dependencies
that
we
need
to
sort
out
in
that
we,
the
Installer,
is,
is
probably
beyond
our
control
and
also
we
need
to
get
some.
A
We
need
to
interact
with
the
with
the
Daedalus
team,
so
that's
all
coming
up
this
week
as
well
as
hopefully
getting
to
the
bottom
of
any
more
performance
and
issues
and
bugs
that
we
have
that
we
have
found
so
far.
Ok,
so
that
is
I
think
the
status
for
this
week
almost
at
full
strength
again
Mukesh
is
that
for
the
rest
of
this
week,
but
we'll
be
back
for
next
Monday
I.
Think,
ok,
any
questions
from
anyone
before
I
am
wrap
it
up.