►
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
Just
yet
I
was
hoping
to
have
it
this
week,
but
we're
still
trying
to
figure
out
if
we
can
squeeze
in
that
that
UI
change
in
the
absence
of
the
UI
change
I
think
we
still
have
plenty
to
offer
in
a
minor
release.
We
have
quite
a
bit
of
work
done
on
the
on
the
performance
last
week.
I
think
one
of
the
risks
that
we
had
was
the
outstanding
POS,
but
the
good
news
is.
A
We
have
Alan,
V
and
Nico
are
back
in
the
office
and
have
started
looking
at
some
of
those
POS,
so
I
think
we
will
be
able
to
cope
once
once
we
once
we
hear
from
those
guys
we'll
be
able
to
assess
the
risk,
the
risk
to
our
ship
date,
which
still
hasn't
changed.
Luckily
enough
is
still
probably
the
second
week
in
in
April,
okay.
A
B
A
There
was
an
interesting
paper
that
was
published
that
showed
how
it
was
possible
to
with
just
two
machines
to
attack
a
eth
node
and,
of
course
the
the
same
protocol
is
specified
for
4
et
Cie.
The
the
cordelia
protocol
has
been
reused
and
Conrad.
You've
had
a
good
long.
Look
at
this
and
I
think
we're
actually
going
to
benefit
from
some
of
the
some
of
the
decisions
that
we
well
maybe
not
decisions
that
we
made
earlier
on.
But
when
we
implemented
our
discovery,
we
didn't
actually
fully
implement
the
it's
honor.
B
Yeah,
you
read
the
paper
and
it
actually
describes
three
attacks.
First
attack
is
I,
don't
know
exclusive
to
get
version
which
is
described
in
paper,
which
weren't
making
difference
between
incoming,
cannot
go
and
go
outgoing
connections,
so
we're
specifying
Mac
Spears
and
there
were
no
difference
between
coming
and
going
so
attacker
could
make
marks
incoming
connections
and
prevent
gate
from
connecting
to
other
peers
yeah.
So
this
was
the
Cygnus
type
of
attack
and
we
are
in
suffering
from
it
because
we
make
that
distinction.
We
have
separate
things
from
for
incoming
connections
and
from
outdoor
connections.
B
So
on
that
part
we
are
safe.
The
second
attack
was
exclusively
to
the
khadiyah
protocol.
It
was
taking
advantage
of
the
metric
distance,
which
khadiyah
takes
for
it's,
not
look
at
risks
or
and
yeah
crafting
then
proper
knows
IDs
can.
Let
me
to
know
to
prefer
some
of
these
crafted
IDs
yes,
connect
to
more
malicious
nodes.
B
B
Yeah
and
not
all
those
messages
and
those
are
probably
safe
from
these
attacks.
We
also
don't
validate
these
time
stamps.
So
that's
first
thing
we
couldn't
say
in
the
full
force
that
our
protocol
is
better
than
Adelia,
but
security
audit,
which
we
have
didn't
pinpoint
and
the
particular
weaknesses
yeah.
A
A
B
Yeah
today
I
merge
one
big
big
ones,
one
of
the
big
ones
which
was
changing
our
fastest
algorithm.
It
was
one
of
the
biggest
one
on
the
table
from
the
peer
the
player.
There
is
only
one
big
one,
which
is
about
the
node
caching
to
speed
up
our
operations
yeah
and
most
of
that,
which
others
are
pretty
easy,
so
they
should
go
down
tomorrow,
but
at
most
yeah,
so
I
think
I.
Think
I
am
worried
about
this
big
one
with
caching
notes.
B
C
Yes,
we
are
looking
at
all
of
them,
as
Conrad
says
they
all
do
with
the
good
like
solid
work.
Maybe
they
gosh.
You
know
it
is
the
most
tricky
one.
I
haven't
pressed
their
proof
button
yet
because
I'm
trying
to
figure
out
if
there
are
is
there
are
some
corner
cases
that
I'm,
missing
and
Nico
is
checking
that
one
as
well,
but
I
feel
completed.
Most
of
the
pull
request
will
go
in
between
today
and
tomorrow.
A
Okay:
okay,
that's
that's
pretty
good!
So
once
we
have
those
in,
we
can
talk
about
as
I
say,
there's
still
the
UI
aspect.
If
we
need
to
whether
or
not
we
need
to
get
whether
we're
gonna
be
able
to
get
that
UI.
A
couple
of
small
UI
changes
in,
but
the
main
thrust
of
the
of
the
release
which
is
is
the
is
the
performance
will
be
I
guess
under
control,
then,
by
the
end
of
this
week
and
we'll
be
starting
to
talk
about
a
test
and
release
cycle.
A
B
Yeah
he
hadn't
come
back
with
any
issues
and
yeah.
That's
all
I
can
say,
because
he
only
mentioned
to
me
that
it
seems
that
the
blocks
are.
It
seems
that
a
blocker
picked
it'll
be
faster
right
and
he
didn't
mention
any
I.
Don't
know
problems
or
hang-ups
or
problems
were
thinking.
So,
okay
go
down
to
because
this
I
love
this
branch.
I'm
a
pro
game
was
night
4p
performance
people
are
merged
together
as
fast
as
possible.
Right.
A
Okay,
I
think
that's
everything
to
to
recap:
we're
still
looking
at
a
1.1
performance
based
release
in
sometime
in
April.
Probably
this
the
second
week
at
this
stage,
the
major
risks
which
are
the
the
POS
that
are
outstanding,
will
be
known,
I,
guess
or
alleviate
it.
Probably
by
the
end
of
this
week
it's
looking
pretty
good
so
far,
a
no
major,
no
major
red
flag,
so
everything
there
is
is
on
course
there
hasn't
been
anything
else
reported
in
github
or
or
anywhere
else.
So
there's
nothing!
A
That's
that's
all
people
on
a
blindside
us
and
the
only
then
issue
is-
is
around
the
small
UI
changes
which,
at
this
stage
we
we
may
actually
end
up
leaving
out
and
then,
finally,
just
to
add,
we've
updated
the
bootstrap
database.
So,
if
anybody's
in
a
particular
hurry
to
and
to
get
up
and
running
with
the
wallet
today,
now
is
an
excellent
time
to
just
go
and
download
the
bootstrap
database,
and
you
should
be
up
and
running
inside
inside
a
half
an
hour.