►
From YouTube: libp2p weekly sync - March 23, 2020
Description
A
Alright,
hello,
everybody
welcome
to
the
March
23rd
lit
b2b
wheatley,
sync
eye-popping.
The
notes
in
the
chat
feel
free
to
add
your
async
updates.
If
you
have
any
agenda
items
anything
you
want
to
talk
about,
go
ahead
and
add
those
and
we'll
try
to
make
sure
we
prioritize
the
beginning
lists.
So
we
make
do
we
get
through
them.
There
are
a
bunch
of
people
on
the
DHT
teams
crunching
away,
so
they
may
not
make
it
to
this
meeting,
but
hopefully
we'll
have
a
release
this
week
of
the
DHT.
B
Hale
so
once
TARDIS
lands
I
rest,
some
reviews
from
last
week
and
the
examples
and
integration
appears
for
J
slippage
be
and
is
just
a
bit
fest
the
other
PR
Dryad
with
the
doctor
filing
parameters
instrumentation
was
merged.
This
will
allow
an
easy
deploy
post
for
the
lipid
spiritomb
and
for
our
years
there's
a
want
to
deploy
their
own
server.
B
B
It
is
an
issue
if
anyone
who
wants
to
check
it
out
or
provide
basically
I,
also
created
two
sube
issues
containing
some
proposals
and
design
decisions
for
some
of
the
milestones,
I'm
still
creating
the
other
ones
as
the
time
passes
and
I
started
working
also
on
the
initial
milestone,
which
basically
will
decouple
the
our
beer
store,
which
currently
is
just
a
map
with
all
the
peer
information
of
each
beer
into
an
address
book
and
the
proto
book.
So
for
this
week,
I
want
to
F
the
final
release
of
starters.
B
This
is
just
spending
some
final
reviews
on
the
examples
and
after
that,
I
will
ask
machi,
which
is
under
call
to
release
it,
and
I
will
also
sink
with
a
little
bit
me
in
freedom,
so
that
we
can
have
a
couple
of
servers
deployed
and
other
than
that.
I
will
continue
working
on
your
start
carrying
this
week.
We
are
with
the
milestone
one
and
continue
working
on
proposals
for
the
remaining
milestones
and
that's
it
for
me.
Any
questions
see.
C
B
Yes,
it
will
be
released,
but
then
we
will
need
to
wait
for
the
server's
to
get
deployed
in
order
to
like
guide
people,
to
use
our
examples
and
just
point
to
the
servers,
instead
of
they
having
to
run
their
own,
which
will
be
easier
for
them
to
start.
But
then,
in
a
production
level
they
should
have
their
own,
but
yet
for
being
used
usable.
It
will
be
this
week.
I.
Oh.
A
Okay,
our
planning
I
think
the
big
thing
that
I'm
gonna
be
looking
at
working
on
in
q2
is
kind
of
an
overhaul
to
the
jslabbee
to
be
crypto,
because
we
need
to
make
sure
that
we
have
support
for
noise
and
edie
to
five
one
nine
keys
and
without
bloating
bundle
sighs.
It's
gonna
require
a
over
halter
to
cleaning
up
the
crypto
repo,
otherwise
GS
ipfs
and
J
slippity
P
bundles
will
be
gigantic,
so
I'll
be
working
on
that
likely
over
the
next
few
weeks.
Any
questions
for
me.
F
Next
up,
Yusuf
and
so
I've,
mostly
just
been
doing
the
gossip
side
test
ground
setup
work
past
about
two
weeks,
I
guess
ish
and
we're
now
at
the
point
where
we're
starting
be
able
to
run
tests
and
get
results,
but
there's
not
yet
much
to
say
about
it,
except
that
it
looks
promising,
see
and
then
I
might
need
to
do
list.
I'm,
just
sort
of
like
slapping
myself
for
not
having
finished
the
Edit
to
the
noise
spec,
which
I
ought
to
have
done
weeks
ago
and
hopefully,
by
saying
this
out
loud.
F
G
F
A
H
Next
up
will
we
guy
thinks
just
even
an
auto
NAT
sort
of
Waypoint
milestone,
so
there's
a
sub
release
and
what
p2p
will
use
it,
so
some
follow
up
key
ours
there
and
then
trying
to
spend
some
time
getting
metrics
and
collection
of
that
stuff,
a
little
bit
better
shape
and
then
responding
to
PRS
and
figuring
out.
What
else
needs
to
happen
for
a
point?
Five.
G
G
So
it's
gonna
be
a
bunch
of
work
around
that
last
week,
also
where
Jones
came
in
Redis,
as
you
most
of
you
saw
when
in
tests
within
the
docker
environment,
and
also
Trinity
so
with
with
Anton
I
added
Prometheus
instrumentation
to
this
thing,
service,
which
I
think
it's
gonna
be
very
valuable
for
instances
where
we
think
that
the
same
service
is
stuck
and
did
very
little,
it
b2b
per
se
in
itself
focus
mostly
on
test
ground
and,
as
this
week,
I'm
gonna
be
producing
a
technical
design
for
test
ban
management.
This
is
basically
the
idea.
G
It's
kind
of
like
it's
gonna,
be
a
larger
the
architecture
of
test
ground,
in
the
sense
that
we
need
to
very
clearly
defined
the
roles
of
a
demon
and
a
client
who's
gonna
be
building
building
things
who's
gonna.
What
are
the
manifests?
Actually
gonna
be
used
for?
Are
they
just
use
on
the
client
side
to
provide
a
nice
porcelain,
or
are
they
also
used
on
the
demon
side
of
things?
G
How
we
gonna
ship
go
to
the
demon
there's.
Ideally,
we
want
the
demon
to
not
be
owning
any
code
if
we
want
code
to
be
test
Banco
to
be
picked
up
from
and
sourced
from
different
places
than
it
should
not
be
managed
by
the
demon,
which
is
the
way
that
it
works
right
now.
So
all
these
things,
I'm
going
to
be
writing
in
technical
design
for
I'm
gonna,
be
reviewing
the
gossips
of
hardening
PR
as
well.
The
visa
has
put
up
I
committed
to
it
already.
Also
gonna
be
finishing.
G
A
I
I
Metrics
are
looking
pretty
good
with
the
new
DHT
need
to
make
sure
that
all
the
results
are
real
and
not.
You
know
test
artifacts,
but
they're,
looking
much
better
than
with
the
priority
HT
code,
hoping
to
lend
the
async
queries.
Pr,
like
you
know
the
next
day
or
two
and
just
do
more
testing
and
get
closer
and
closer
to
the
various
real-world
test
that
we
want
to
simulate
and
yeah
anything
else
that
is
in
the
way
of
getting
the
DHT
like
release,
so
that
ipfs
can
do
an
RC
is
this
week
for
me.
J
I
K
D
L
L
J
Yeah
so
last
week
wasn't
the
like
most
productive
weeks
for
me,
but
things
are
good
now
and,
like
things
should
be
smooth
going
ahead,
however,
I'm
to
fix
some
like
the
bugs
and
the
race
conditions
in
the
routing
table
management
logic
that
will
come
up
for
the
content,
routing
work,
basically,
the
race
conditions
between
handling
new
connections,
handling
replacement
candidates,
etc.
I
also
finished
reviewing
the
a
sync
query:
work
that
Dean
mentioned.
I
am
currently
writing
the
tests
for
it,
and
it
looks
and
really
really
good
shape
and
I
finished.
J
Reviewing
the
identify,
signed,
records,
work
and
I'll
take
it
to
completion
after
0.5
scurred,
because
it's
not
really
on
the
critical
path,
but
basically
I'll
be
retaking
it
over
from
yourself
yeah.
It's
also
looking
pretty
good.
Next
is
yeah
remove
disjoint
parts
logic.
We
don't
need
disjoint
queries
anymore,
as
we
discussed
with
like
iodine
and
pit
or
discussed
it
today.
Is
that
weak?
J
It
makes
a
very
slow
adds
a
lot
of
complexity
and
doesn't
give
us
much
in
return
now,
yeah,
and
also
we
set
a
goal
of
writing
a
test
with
thousand
nodes
on
the
ground
cleared
cluster
I.
Still
don't
know
which
test,
but
definitely
some
tests
to
help
out
with
content,
routing
testing
effort.
That's
going
to
be
my
main
focus
going
ahead
and
yeah
I've
created
some
issues
for
fixing
some
content.
Rounding,
0.5,
TechNet
stuff
that
we
mixed,
missed
outs
of
didn't
have
time
to
put
in
so
I
mean
I.
Guess
after
0.5
goes
in.
A
C
Just
so
on
the
kind
of
content,
routing
work
stream
side,
we're
kind
of
intentionally
as
folks
pretory
release,
giving
content
routing
a
little
bit
of
an
extension
for
planning,
q2,
ok,
ours
that
doesn't
give
anyone
else.
An
extension,
but
I
know
that
part
of
landing,
oh
top
5
release,
is
starting
to
think
about
a
short
sweet,
focused,
Oh,
dot,
six
release
that
can
actually
get
us
back
on
the
release
train
of
every
six
weeks
having
having
a
release.
So
the
the
planning
for
that
probably
should
should
start
before
o
dot.
C
Five
is,
is
actually
shipped
out
the
door
so
that
anyone
who
frees
up
from
Oh
dot
five
testing
can
start
working
on
the
things
to
land
in
Oh
dot.
Six
so
curious
if
there's
a
a
time
plan
or
an
async
spot
where
people
can
start
dropping
some
of
the
ODOT
six
recommendations.
Just
in
case
anyone
does
magically
free
up
from
release
testing
yeah.
A
If
anybody
has
any
items
that
we
haven't
previously
covered
in
the
plan,
I'm
gonna
work
on
updating
that
this
week,
so
that
I
can
kind
of
like
prep
for
the
planning,
406
and
the
q2
or
k
ours
and
so
I'll
share
that
out.
And
then,
if
anybody
has
any
items
that
they
would
like
to
attempt
to
add
or
kick
something
else
out.
Let
me
know,
but
yeah
we'll
try
to
keep
it,
try
to
keep
it
small
and
compact
and
move
non-critical
things
into
ODOT
seven.
So
we
can
get
on
the
regular
release
cycle.
Yeah.
A
Yeah
so
I'll
be
updating
that
and
then
sharing
that
out
for
everybody
to
to
add
to
you
great
anything
else
once
twice
sold
all
right,
everybody
that
is
it.
We
will
see
you
all
next
week
and
next
week,
Europe
will
have
daylight
savings
time,
so
we
will
be
back
for
Europe
folks
at
6:30
p.m.
UTC
all
right.
Well,
how
doesn't
break
the
news
before.