►
From YouTube: Filecoin Virtual Community Meetup - April 13 2021
Description
We’re excited to gather the Filecoin community for another monthly meetup! Our community meetups are an opportunity to meet the people behind the many tools and projects being built in the Filecoin ecosystem. We have a wonderful lineup of speakers in store and we can't wait to see you there!
Presentations:
00:00 Emily, Filecoin Team (Announcements)
5:24 Maksim (Soramitsu) - FUHON
13:23 Aayush and Why (PL) - LOTUS
35:20 Amer Ameen (ChainSafe) - FOREST
52:01 Max Inden (PL) - RUST LIBP2P
1:08:19 Steven Li (IPFSForce) - VENUS
THIS EVENT ABIDES BY THE FILECOIN COMMUNITY CODE OF CONDUCT: https://github.com/filecoin-project/community/blob/master/CODE_OF_CONDUCT.md
A
So,
hey
everyone
and
welcome
back
to
the
monthly
filecoin
community
meetup
series.
My
name
is
emily
and
I
will
be
your
host
for
today.
As
usual.
Today
we
have
an
extremely
exciting
themed
meetup
today,
entirely
focused
on
the
filecoin
implementations,
which
are
venus
forest
lotus,
fujon
and
a
special
feature
from
rust,
lib
p2p
as
well
as
always
before.
We
begin
I'd
like
to
remind
you
of
the
filecoin
community
code
of
conduct
that
is
linked
in
the
chat
and
by
joining
us
today.
A
A
A
For
this
first
season,
decrypt
has
partnered
with
nft
artists
across
the
web
3
ecosystem.
The
theme
for
these
digital
artworks
is
is
decentralization
and
each
artist
has
interpreted
the
theme
differently
to
help
showcase
the
size
and
the
scale
of
the
topic
aligned
with
both
the
values
of
decrypt
and
filecoin.
We
are
also
excited
to
announce
that
live.
A
Pier
is
launching
a
co-mining
pilot
with
filecoin
to
enable
filecoin
miners
to
become
live
peer,
video
miners,
while
continuing
to
mine
on
the
filecoin
network
by
storing
transcoded
video
data,
this
co-mining
pilot
will
identify
the
requirements
for
miners
interested
in
co-mining,
as
well
as
identify
the
recommended
path
for
miners
that
are
interested
in
co-mining
next
up.
We
have
the
file
coin
and
chain
link
integration,
which
was
announced
last
month,
and
it
will
enable
bi-directional
connections
between
file
clean
network
and
smart
contract
enabled
blockchains
such
as
ethereum.
A
Next,
we
have
truffle
suite,
which
launched
an
nft
development
template
with
filecoin
box
and
now
devs
can
get
started
with
the
filecoin
box
and
have
everything
that
they
need
to
create
a
decentralized
art
gallery.
You
can
now
try
the
filecoin
box
via
the
link
in
the
chat
additionally
late
last
week,
ok
x,
newly
ok
x's
newly
founded
block
dream
fund,
has
announced
a
collaboration
with
the
filecoin
network.
A
Block
dream
fund
will
provide
10
million
dollars
of
dedicated
capital
and
resources
to
support
highly
high
quality
ecosystem
projects
from
programs
like
filecoin
slingshot,
the
filecoin
launchpad
accelerator
that
was
led
by
tachyon
and
the
filecoin
frontier
accelerator
led
by
longhashventures
and
many
more
now.
Lastly,
in
terms
of
announcements,
videocoin
announced
last
week
that
it
is
integrating
its
decentralized
video
processing
network
with
filecoin,
to
build
the
first
platform
specifically
designed
for
creating
and
trading
video
nfts,
a
highly
compelling
segment
of
the
emerging
global
marketplace
for
digital
collectibles.
A
Now.
Lastly,
before
we
begin,
I
would
like
to
cordially
invite
you
to
the
filecoin
frontier
accelerator
demo
day
in
which
11
projects
will
be
presenting
and
pitching
to
you.
The
projects
span.
The
projects
span
from
an
nft
marketplace
to
a
decentralized
video
conferencing
solution.
Now,
if
you
want
to
learn
more
about
them,
visit
at
longhashvc
on
twitter
and
they
will
be
announcing
each
and
every
startup
leading
up
to
the
demo
day,
project
founders
will
be
pitching
to
you
at
9,
am
gmt
plus
8
on
the
23rd
of
april
just
10
days
away.
A
So
you
can
scan
the
qr
code
in
the
slide
right
here
to
sign
up.
So
that
is
all
from
me
today
and
let's
begin
first
up,
we
have
maxim
from
sora
mitsu.
He
is
the
fujon
team
lead
and
he
has
done
engineering
manner
managership
with
previous
six
years
of
experience.
As
a
software
engineer
today,
he
will
be
presenting
on
the
state
of
fujon.
Thanks
maxim,
you
can
go
ahead
and
get
started.
B
Okay,
so,
let's
start
then
again,
hi
everyone,
my
name
is
maxim
skorikov.
I
am
a
team
with
fujon,
the
c
plus
plus
implementation
of
filecoin
protocol,
and
today
I
want
to
present
you
with
our
project,
where
is
it
in
the
file
coin,
ecosystem,
our
achievements,
goals
and
as
well
as
future
plans
for
the
project?
B
B
B
B
What
do
one
mean
when
they
say
that
they're
implementing
file
filecoin
protocol,
this
picture
shows
simplified
view
on
what
exactly
could
be
meant
by
protocol
implementation,
so
fully
implemented.
Protocol
should
include
node
itself,
which
is
downloading
and
uploading
the
data
to
the
network
and
providing
api
to
other
components,
storage
and
retrieval
markets
which
implemented
storage,
storage
and
retrieval
deals,
flows
and
the
miner
component,
which
is
feeding
the
node
with
newly
mined
blocks.
B
B
Even
though
it
is
not
as
easy
to
keep
up
with
lotus
changes-
and
we
are
doing
our
best
to
do
so
so
now-
it
is
more
clear
on
what
are
the
goals
of
the
project.
Let's
see,
where
are
we
now
exactly
as
of
today,
fujon
has
its
node
fully
implemented.
It
is
able
to
sync
to
the
mainnet,
provide
an
api
for
miners
and
markets,
both
slotus
and
fujon.
B
However,
it
is
not
ready
to
release
due
to
several
reasons
I
will
mention
later.
It
should
be
noted
that,
due
to
several
changes
in
actors
versions
and
our
focus
on
releasing
and
and
our
focus
on,
releasing
the
node
as
soon
as
possible,
we've
made
the
decision
to
make
a
shortcut
and
to
introduce
the
same
actors.
Lotus
is
currently
using
via
sigo
bridge,
and
this
approach
actually
worked
quite
well
for
us,
I
noticed
spicing,
all
the
conformance
testing
seems
to
be
relatively
stable
from
the
virtual
machine
perspective.
B
I
marked
all
the
other
components
as
antler
development,
even
though
main
development
activities
have
already
finished.
I
did
so
because
we
didn't
have
a
chance
to
properly
test
the
components
against
latest
changes
and
well.
They
have
it
needed
to
be
done.
This
is
something
we'll
be
actually
focusing
after
the
initial
node
release.
B
B
After
that,
we
will
have
to
start
preparing
to
security
audit
and
spread
efforts
on
the
road
testing
of
minor
and
markets,
as
well
as
continuing
developing
cbp
actors
for
our
own
shipless,
plus
written
virtual
machine.
So
a
source
mentioned
in
the
deadline
for
the
1.1
is
subject
to
changed
as
actors.
V4
are
actually
already
planned
for
june,
and
our
previously
our
previous
plan
introduced,
includes
only
actors
v2,
so
we
will
have
to
introduce
v3
and
v4
migration
somewhere
to
the
1.1
release.
B
B
A
Thanks
maxa,
it
was
awesome
so
exciting
to
see
what
you
guys
have
upcoming
and
the
future
fujon
as
he
mentioned.
If
you
have
any
questions,
please
put
them
directly
in
the
chat,
and
I
know
that
he
is
also
on
slack
on
the
filecoin
community
slack.
So
if
you
have
any
questions,
then
you
can
connect
there
as
well.
A
So
far,
I
don't
see
any
questions
for
you,
but
if
they
come
up,
we
can
take
them
later.
So
next
up,
we
actually
have
two
very
familiar
faces
on
the
protocol
labs
side.
We've
got
ayush
and
y
ayush
is
a
software
engineer
who
helped
build
the
lotus
implementation
of
filecoin
and
he
wishes
that
the
internet
had
been
built
more
fairly.
The
cryptography
was
easier
to
understand
and
that
canada
was
less
cold.
A
C
C
Excellent
yeah,
so
we're
kind
of
the
the
boring
ones
here
and
that
we've
kind
of
been
around
for
longer
and
if
you
have
interacted
with
a
file
coin,
blockchain
you've
probably
been
going
through
the
lotus
implementation.
So
we're
not
we're
not
new
and
shiny,
like
like
the
other
implementations,
so
yeah.
C
So
we
can
kind
of
get
into
a
q
a
a
bit
that
yeah
lotus
is
a
reference
implication
of
the
five
point
specification,
we're
hoping
that'll,
stop
being
true
once
the
other
implementations
gain
more
traction,
but
for
now,
if
you
kind
of
look
at
filecoin
documentation,
the
kind
of
examples
that
you'll
see
are
all
lotus
examples
and
you
can
go
to
filecoin.io
for
for
those
in
terms
of
what?
What
a
lotus
note
does
kind
of
what
you'd
expect?
C
I
split
these
into
the
first
two
points,
which
is
basically
the
core
functionality.
What
any
implementation
of
file
coin
or
really
any
blockchain
protocol
has
to
do,
which
is
it
needs
to
find
other
nodes
on
the
network.
It
needs
to
talk
to
them,
it
needs
to
receive
blocks
from
them
and
it
needs
to
be
able
to
validate
those
blocks
and
connect
to
the
right.
The
right
chip
set
in
filecoin
parlance,
the
right,
the
right
block
height.
Basically
so
that's
kind
of
the
core
functionality
of
lotus.
C
Some
of
the
other
odds
and
ends
that
all
implementations,
kind
of
have
lotus
has
an
internal
wallet.
That's
used
for
key
management.
This
is
especially
useful
if
you're
also
running
a
lotus
miner,
because
you
need
to
miners
need
to
be
signing
their
blocks,
which
requires
you
to
have
your
key,
easily
accessible
lots
of
api,
api,
endpoints
and
cli
tools
to
interact
with
the
blockchain
or
kind
of
a
inspector
chain
and
then
kind
of
the
two
other
critical
pieces
that
are
both
that
are
separate
processes.
C
That
lotus
can
help
you
with,
which
is
the
markets
aspect
of
the
filecoin
network,
which
is
how
you
make
deals.
So
if
you
have
data
lotus
can
help
you
import
that
data
find
a
miner,
a
storage
provider,
who's
willing
to
store
that
data
figure
out
how
much
they
want
and
help
you
make
that
deal
with
them,
which
involves
you
know,
sending
messages
on
chain
and
so
on,
and
the
other
kind
of
big
players
in
the
falcon
ecosystem,
which
is
storage
providers
and
miners.
C
C
The
thinker
kind
of
directly
uses
the
state
manager
and
the
virtual
machine,
which
are
the
bits
that
do
the
validation
of
state
and
kind
of
remember
what
the
state
tree
is
so
how
much
money
every
account
has
and
that
kind
of
thing,
the
repository,
which
is
a
giant
database.
That's
getting
bigger
with
every
passing
day,
unfortunately,
which
is
where
all
of
your
information
is
the
message
pool
which,
if
you've
ever
tried
sending
a
message
using
a
lotus
note.
You've
probably
had
some
fun
with
that's.
C
Basically,
a
it's
a
it's
a
pool
where
every
message
that's
waiting
to
get
on
chain
kind
of
sits
around
and
miners
select
messages
from
that
message
pool
when
they
are
forming
their
blocks.
They
basically
pick
messages.
It
will
give
them
a
lot
of
money
or
as
much
money
as
possible,
and
then
you
there's
a
peer
manager,
that's
taking
care
of
all
of
your
peer
connections
and
an
rpc
endpoint.
C
Where
that
you
can
that
you
can
hit
up
if
it's,
if
it's
taking
requests
to
inspect
the
chain
and
there's
a
whole
bunch
of
requests
that
you
can
make
there
cool,
yeah,
so
jeremy,
johnson,
here
who's,
a
falcon
tech,
lead
and
also
kind
of
kicked
off.
The
lotus
project
he's
a
great
person
to
kind
of
give
us
some
insight
into
into
how
lotus
was.
I
don't
like
this
word.
C
It
was
architected
because,
like
I
said,
there's
there's
many
ways
to
go
about
implementing
any
blockchain
protocol
and
especially
the
firefight
protocol,
which
is
quite
complex
and
heavy
so
way
back
over
a
year
ago.
Now,
when
the
lotus
project
kind
of
began,
I'm
curious
what
were
what
were
the
things
that
were
front
of
mind
when
you
were
designing
this
new
implementation.
E
So,
initially
in
designing,
I
wanted
a
lot
of
the
pieces
to
be
very
separate
kind
of
a
bunch
of
little
modules,
that
kind
of
interact
with
each
other
and
have
nice
clean
boundaries,
and
we
still
see
a
lot
of
this
in
the
current
design.
The
lotus
miner,
for
example,
you
know,
interacts
entirely
with
your
lotus
note
over
an
api.
E
The
wallet,
for
example,
is
also
optionally
can
be
a
separate,
separate
process.
We're
working
we're
working
on
actually
having
the
markets
itself,
be
an
entirely
separate
module
and
there's
even
a
lot
more
pieces
that
we
could
pull
out
of
separate
modules.
Some
of
them
we
don't
just
because
well
that
would
just
be
more
operational
overhead,
but
the
internal
design
of
a
lot
of
it
allows
you
to
like
pretty
easily
like
piece
things
apart
and
just
have
one
individual
component.
That
does
this
one
thing.
E
It
also
makes
it
makes
setting
up
a
lotus
node,
like
kind
of
logically
simple,
so
as
you're
thinking
about
like
the
different
pieces
that
need
to
come
together
and
how
they
tie
in
you
just
have
a
bunch
of
little
blobs
with
references
to
each
other
and
yeah.
It's
it's
made
development
like
quite
a
bit
nicer.
C
E
View
for
everything,
it's
kind
of
an
odd
question,
because,
like
there's
there's
a
lot
of
different
things
that
could
be
an
implementation
could
target.
I
think
like
one.
One
of
them
that
I
don't
see
lotus
is
targeting
a
whole
lot
is
being
like
a
very
nice
deal.
Client,
so,
like
lotus,
isn't
going
to
be
like
a
dbl
and
all
tool
for
like
managing
and
storing
all
of
your
data.
It
will
definitely
be
the
back
end
to
such
a
process,
but
itself
is
not
going
to
do
any
sort
of
management.
E
Lotus
prob,
you
know,
is
going
to
provide
a
decent
wallet
interface,
but
the
actual
like
management
and
display
of
transactions
and
indexing
of
things
is
something
that
you
know
would
be
on
top
and
so
the
I
think,
a
lot
of
the
goals
with
lotus
is
to
provide
a
very
stable
core,
a
very
stable
center,
that
everything
can
use
and
interact
with
and
build
on
top
of,
but
not
to
necessarily
be.
You
know
the
best
end
user
experience
for
any
particular
thing.
E
C
It'll
be
interesting
as
yeah
as
time
goes
on
as
more
implementations
join
as
the
ecosystem
grows,
as
it's
growing
every
day
to
see
to
see
if
lotus
does
wind
up
kind
of
specializing
in
some
departments,
while
other
departments
there
are
other
leaders
in
the
ecosystem,
which
will
be
cool.
One
thing
you
think
you
did
wrong.
What's
one
thing
you
think
that's
really
messy
about
lotus
or
you
wish
you'd
done
differently.
E
In
that,
like
you
know,
we
we
decided
to
for
what
we
thought
initially
was
expediency
design.
You
know
all
of
the
actors
and
stuff
and
go
natively
and
run
them.
I
think
overall,
it
would
have
been
much
nicer
if
we
just
bit
the
bullet
and
spent
a
month.
You
know
figuring
out
a
vm
pulling
like
you
know
the
wasm
life
vm
or
whatever
off
the
shelf
and
plugging
that
in
the
right
way.
There's
just
I
don't
know
it
would
have
definitely
saved
way
more
time
than
it's
cost
overall.
E
So
that's
that's
one
of
the
things
like
we
should
have
done
that
and
there's
a
few
other
like
design
like
broader
file
coin
design,
decisions
that
you
know
it's
probably
should
have
done.
It's
kind
of
not
easy
to
know
ahead
of
time.
What's
going
to
pay
off
or
not,
but
I
think
like
some
stuff
around
like
ideals,
ideas
around
a
a
different
minor
type
to
manage
redundancy
and
repairing
the
deals
like
the
filecoin
protocol
as
it
does
this
today
doesn't
have
any
repair
functionality.
It
doesn't
have
any
like.
E
C
Yeah
and
things
get
harder
to
change
or
to
introduce
once
you
have
a
live
network,
but
those
are
all
changes
that
still
can
be
made.
I
think
the
the
wildlings
is
potentially
like
on
the
roadmap
further
down
right,
yeah,
yeah,
cool
yeah
that
we're
doing
good
for
time.
That's
like
way
as
well
into
kind
of
the
next
steps
that
I
wanted
to
talk
about
yeah.
C
So
in
terms
of
what
what
comes
next
for
lotus
kind
of
the
key
thing
that
like
kind
of
the
evergreen
goal
for
us
right
now
is
to
because
lotus
is
so
central
to
the
existing
falcon
network.
It
needs
to
any
any
like
high
priority,
bugs
are
found
kind
of
need
to
get
fixed
immediately,
because
it's
it's
not
just
a
lotus
bug.
C
It
becomes
a
file
point
network
security
bug,
but
really
hoping
that
having
more
implementations
join,
the
network
will
alleviate
some
of
that
so
that
that's
kind
of
the
evergreen
goal
it
takes
always
seems
to
take
up
a
lot
of
a
lot
of
time.
But
it's
it's
becoming
less
as
as
time
as
things
get
more
stable
one.
So
the
single
focus
right
now
I'd
say
for
the
lotus
team
and
everyone
engineering
around
lotus
is
improving
that
deal-making
process.
That
jeremy
was
talking
about
which
works
right
now.
C
It
doesn't
work
well
where
we
think
there's
a
lot
of
scope
for
improvement
there.
Basically,
we
want
to
get
to
a
place
where
you
know,
there's
very
high
confidence
that,
if
you're
trying
to
make
a
deal,
if
you're
trying
to
store
some
data
with
someone
that
that
works,
that
that
it
succeeds-
and
you
don't
have
to
be-
you
know
either
very
familiar
with
the
file
coin
protocol
or
like
a
tech,
wizard
or
you
know
very
patient
like
we
want.
C
We
want
that
process
to
become
easier
because
that's
what's
going
to
affect
the
usability
of
lotus
from
for
as
a
as
a
markets,
module
and
again,
because
lotus
is
critical
to
five
coins.
That's
what
makes
falcon
usable
or
not
right
now
so
increasing
the
success
rate.
Improving
the
overall
ux
well
right
now,
there's
a
lot
of
things
that
are
somewhat
counterintuitive
or
confusing
things
like
improv,
improving
documentation
around.
C
It
also
falls
in
here
and
then
as
improvements
land
in
the
file
code
protocol
itself,
we'll
be
keen
to
kind
of
pull
them
in
into
the
lotus
implementation.
And
then
we've
got
a
lot
of
technical
debt
to
paid
out
pay
down.
We
were
sprinting
towards
maine
at
launch
last
year,
but
now
we
can
afford
to
to
repair
some
of
that
damage.
So
this
is
just
stuff
like
refactors
that
are
badly
needed
right.
C
More
tests
improve
yeah,
improve
the
performance
of
our
core
sub
modules
so
that
that's
kind
of
the
secondary
theme
to
what's
next
for
lotus,
and
then
the
five
phone
protocol
itself
is
always
evolving
and
that
involves
implementation
work.
I'm
sure
the
other
implementations
will
agree
and
maximum
kind
of
alluded
to
that
already,
but
that's
that
that's
as
a
500
map
evolves
and
as
new
things
as
we
hit
new
milestones
that
becomes
lotus
work
as
well.
C
So
that's
kind
of
what
the
the
next
few
quarter
next
couple
quarters
are
going
to
look
like
for
lotus
work,
but
yeah.
It's
very
exciting
that
you
know
so
many
people
use
lotus
every
day
and
it's
central
to
such
an
exciting
part
of
the
broader
kind
of
web
3
space.
So
it's
been,
it's
been
good.
Do
we
have
any
questions
very
happy
to
answer
them.
E
I
can
answer
that.
It's
any
different
implementation
of
file
coin
just
communicates
over
the
same
underlying
lib
pdp
protocols
to
the
network.
They
should
look
roughly
the
same.
So
if
you're,
just
you
know,
on
the
filecoin
network
somewhere
and
you're,
looking
at
a
bunch
of
different
filecoin
nodes,
the
only
way
you
would
know
that
it's
one
implementation
or
another
is
if
it
tells
you
otherwise,
it's
you
know
following
the
protocols
and
doing
the
thing.
E
A
Okay,
awesome.
Thank
you.
Let's
see,
I
believe
that
that
is
all
of
the
questions
for
today,
but
you
can
find
why
and
I
use
on
the
file
coin
slack
and
I'm
sure
they'd
be
happy
to
answer
any
questions
there
as
well,
and
then,
if
you
come
up
with
any
questions
as
you're,
you
know
going
along
through
the
meeting
up,
you
can
ask
them
in
the
chat
well.
E
It
looks
like
there's
one
more
here:
people
asking
about
reducing
output,
which
is
like
no
file
coin,
reduces
output
on
every
block.
It's
like
a
very
gradual,
decaying
curve.
There's
not
any
big,
like
you
know
the
block
reward
halves
like
in
bitcoin.
It
happens
on
every
block.
It
decreases
by
just
a
little
bit
at
a
rate
that
over
six
years
it
will
be
half.
So
it's
not
like
you
know
at
the
six
year
point
it
goes
to
half
it's
over
six
years.
It
decreases
to
half
so
no
big
shocks
to
the
network.
There.
A
E
Yeah
for
retrieval,
I
think,
it'd
be
very
important.
Also
for
storage
really
like,
since
the
main,
the
main
bottleneck
for
data
storage
is
basically
bandwidth
right.
You
have
say
you
know
normal
users
with
normal
amounts
of
data
you'll
be
in
like
the
gigabytes
range
right
that
it
doesn't
matter
too
much
where
you
are,
because
the
internet
can
pretty
easily
absorb
a
few
gigabytes
here
and
there,
but
once
you
get
into
like
the
terabyte
range
or
tens
of
terabytes
that
you're
wanting
to
store
bandwidth
like
cross-sectional
bandwidth,
becomes
a
huge
problem.
E
E
So
the
closer
you
are
to
your
miner,
the
more
likely
you
are
to
have
a
strong
connection
to
them
and
on
the
retrieval
side,
the
closer
you
are,
the
lower
latency
you're
going
to
get
so,
for
you
know
you
wanting
fast
retrievals
and
a
good.
You
know
internet
browsing
experience.
That's
you
know,
file
coin
powered
distance
matters.
C
Yeah
there's
a
couple
of
interesting
things
there,
where
right
now,
we've
had
from
an
ecosystem
perspective,
we've
placed
a
lot
of
emphasis
on
ensuring
that
our
storage
providers
are
kind
of
distributed
globally,
but
in
order
in
order
for
that
to
play
out,
it's
also
important
that
storage
clients
are
are
supported
in
various
in
various
regions.
I
guess
also
from
from
an
improving
lotus
or
other
implementations
perspective.
I
think
a
miner's
location
is
currently
something
that's
not
considered
in
any
in
any
way
when
trying
to
figure
out
a
deal.
C
So
potentially
you
know
having
minor
sort
of
register
for
for
regions
and
then
that
being
factored
in
in
some
kind
of
off-chain
process
will
improve
deal
success
rates
as
well,
because,
right
now
we
just
picked
the
miner.
That
seems
to
be
offering
the
best
price
and
has
the
best
overall
reputation
but
geography
matters
here
as
well
to
their
scope
for
improvement.
There
potentially.
A
Awesome,
thank
you
guys,
okay
last
question
and
then
we
have
to
move
on
what
are
the
best
ways
to
start
to
contribute
to
your
project,
even
in
the
simplest
ways.
I
just
graduated
a
programming
boot
camp
and
I'm
intimidated,
but
I
want
to
start
with
filecoin.
I
have
some
docs
that
I
can
share
in
the
chat,
but
I
would
love
to
hear
what
ayush
and
why
would
suggest
here.
A
C
First
off,
thank
you
for
your
interest
and
I
can
totally
understand
why
file
client
is
intimidating
but
but,
like
I
think,
it's
we're
very
interested
in
creating
kind
of
good
entry
points
for
for
people
who
are
interested
to
to
make
to
feel
like
they
can
be
a
part
of
the
project,
whether
that's
in
small
or
big
ways.
So
a
couple
things
that
I'll
say:
number
one:
we
are
working
on
yeah
on
developing
something
like
hey.
Are
you
interested
in
contributing
to
filecoin?
C
Here
are
some
more
concrete
steps
where
right
now
right
now,
the
lotus
implementation
of
alcohol,
in
particular,
I
should
say
here-
are
some
some
concrete
steps
that
we're
hoping
to
get
out
within
the
next
couple
weeks.
So
I
think
definitely
look
for
that
and
we'll
be
happy
to
send
that
your
way.
The
other
thing
that
I
think
is
great
is
the
lotus
implementation.
C
Has
you
know
about
900
issues
opened
against
its
repo
that
we
tried
to
stay
on
top
of
and
try
to
filter
or
try
to
triage
and
keep
in
a
relatively
good
place.
So
there's
a
good
first
issue
label.
I
think
that's
what
it's
called
the
jennifer
can
correct
me
if
I'm
wrong,
so
this
is
a
if
you're,
if
you're
new
to
lotus,
if
you're
someone
new
to
programming.
C
These
are
issues
that
we
have
explicitly
flagged,
as
we
kind
of
feel
like
anyone
can
come
in
here,
explore
around
a
little
bit,
ask
questions
and
get
support
from
kind
of
the
lotus
team
and
make
code
contributions
that
way,
if
that's
what
you're
interested
in.
So
that's
what
comes
to
mind,
jeremy,
I
don't
know
what
what
do
you
think
so.
E
I've
been
involved
in
open
source
communities
for
a
long
time
now,
and
you
know
the
the
general
the
general
advice
is
roughly.
What
I
use
gave
of
you
know,
look
for
good
first
issues
and
find
some
small
bug
to
fix.
I
think
there's
some
pieces
there
that
get
missed
a
lot
in
common
advice
of
how
to
get
started
in
a
project
and
it
falls
down
into
two
things.
E
One
is
just
talk
to
people
like
get
on
slack
and
talk
to
people,
ask
questions,
figure
things
out
and
ask
what
you
can
do,
ask
what
you
can
look
into
and
then
the
second
one
which
I
think
was
really
the
biggest
one
from
me.
Seeing
people
getting
involved
in
projects
is
use.
The
software
like
use
it
to
do
things,
try
to
do
something
with
it
like
try
to
build
something.
On
top
of
it.
E
Try
to
do
something
different
with
it
like
any
sort
of
different
thing
and
when
you
run
into
problems,
go
fix
it
and
now
that's
that's
easier,
said
than
done
right.
You
notice
something
it's
not
even
clear
if
it's
a
problem
generally,
if
you
notice
it
and
it
seems
off,
it's
probably
a
problem
like
by
somebody's
definition
of
a
problem.
So
if
you
find
something
that
like
is
getting
in
your
way-
and
you
are
messing
around
with
the
software-
then
go
ask
somebody
like
hey.
E
How
would
I
go
about
fixing
this
and
try
to
dive
in
that
way,
because
that
gives
you
a
bit
of
motivation
a
bit
of
context
and
like
a
clear
reward
to
yourself
of
when
you
finish
like
hey,
you
did
the
thing
you've
made
your
own
life,
better,
you've
made
everybody
else's
lives
better
and,
like
that's,
I
think.
That's
one
of
the
best
ways
to
really
get
involved
is
to
like
have
an
intrinsic
reason
to
work
on
something
versus
you
know
just
being
told
to
do
a
thing,
because
an
issue
has
a
label.
C
Yeah,
I
think
that
makes
a
lot
of
sense
if
you're,
not
in
the
file
point
slack,
I
would
strongly
recommend
you
join
and
feel
free
to
give
us
a
shout.
You
can
find
all
of
us
on
the
lotus
team,
including
jeremy
and
myself
in
there,
so
feel
free
to
do
that.
We'd
love
to
hear
from
from
folks
who
are
interested.
A
Perfect,
thank
you
guys.
Okay,
that's
it
for
questions
today
for
iosh
and
y,
and
I
will
also
link
the
filecoin
slack
in
the
chat.
So
you
can
join
if
you
are
not
there
already,
thanks
again
guys
that
was
awesome
and
so
fun
to
hear
all
of
your
answers
to
those
questions
as
well
as
what's
next
for
lotus,
okay.
So
next
up
we
have
ammar,
who
is
from
chainsafe
and
he
will
be
presenting
on
forest
the
rust
implementation
of
the
filecoin
protocol.
A
F
Awesome,
okay,
so
today
you
know
I'll,
try
and
give
you
a
quick
intro
to
both
chainsafe
and
the
work
that
we're
doing
on
our
coin
implementation.
So
I
will
start
off
by
shilling
chain
safe
for
a
bit.
So,
first
of
all,
who
are
we?
We
are
a
community
of
kind
and
value
driven
people
who
love
each
other
very
much,
and
I
think
that's
important
to
note
because
it
reflects
in
the
work
that
we
do
and
we
also
happen
to
love
blockchain
too.
F
F
Lotus
does,
and
essentially
you
know
forest
does
the
same
things,
and
so
you
know
it
begs
the
question:
why
are
we
building
this
and
you
know,
client
diversity
on
a
blockchain
network
helps
improve
the
robustness
and
resiliency
of
any
network
and
specifically,
in
this
case,
the
filecoin
network
and
a
couple
of
ways
that
happens.
Is
you
know
if
you
have
different
protocol
implementations,
if
there's
say
a
bug
in
one
implementation?
F
Another
implementation
actually
makes
sure
that
you
know
we
are
checking
that
the
the
protocol
is
being
followed
according
to
the
spec.
The
other
reason
we're
building
this
implementation
is
to
leverage
the
benefits
of
the
russ
language,
so
those
two
primarily
are
memory,
safety
and
performance,
and
a
core
contributor
to
the
forest
project.
F
Austin
gave
a
great
talk
at
a
conference
we
held
in
december
that
dives
more
into
the
details
of
you
know
how
we
are
leveraging
the
rus
language
and
why
it
is
beneficial
for
a
protocol
implementation,
so
I've
linked
it
in
my
slides,
which
I
will
share
after
I
give
this
talk
and-
and
you
can
go
check
that
out,
I
highly
recommend
it.
One
thing
to
note
about
forest
is
that
it
is
modular.
F
F
You
see
the
rpc
server
and
that's
what
we
use
to
communicate
with
the
lotus
miner
and
the
markets
and
any
other
dev
tooling
that
exists,
and
mostly
in
the
middle,
you
see
all
the
components
that
contribute
to
our
ability
to
sync
and
and
verify
the
blocks
and
and
yeah.
This
is
this
is
all
available
I'll
share
this
afterwards,
if
you're
curious
in
diving
in
in
more
into
like
the
architecture
of
our
specific
implementation,.
F
So
so,
where
are
we
at
right
now?
So
so
the
major
milestones
that
sort
of
we've
hit
in
in
recent
time
are
the
following.
First,
we've
mainly
focused
on
verifying
the
correctness
of
our
virtual
machine,
so
the
virtual
machine
basically
gives
us
the
state
transition
logic
for
falcoin
and
and
the
way
that
we
actually
verify.
This
is
a
couple
of
ways.
F
Passing
all
those
test
factors
was
definitely
the
first
step
in
ensuring
that
our
virtual
machine
was
implemented
correctly
and
then
the
second
thing
that
we
did
in
order
to
verify
the
correctness
of
our
vm
was
to
import
an
export
of
of
the
blockchain
from
mainnet.
So
we
basically
took
all
the
blocks
and
all
the
transactions
from
mainnet
and
actually
tried
to
import
them
into
our
own
implementation
and
then
in
that
process,
if
there
were
any
errors
or
any
discrepancies,
we
would
investigate
them
and
fix
them.
F
And
basically,
by
doing
that
iterative
process,
we
were
able
to
eventually
resolve
all
the
discrepancies
and
then
become
interoperable
with
lotus.
The
second
thing
that
was
a
major
milestone
over
the
last
few
months
was
integrating
the
storage
miner.
So,
as
I
mentioned
before,
we
we
didn't
implement
the
storage
miner
in
rust.
F
This
is
working.
We've
had
a
few
net
nodes
running
consistently
for
the
last
few
months.
Just
a
word
of
warning.
This
is
not
production
ready,
yet
there's
still
some
work
that
needs
to
be
done
before
we're
ready
to.
You
know
recommend
this
for
public
use,
but
it
does
work
and
if
you
just
want
to
test
it
out
and
see,
see
how
it
looks
feel
free
to
do
that.
F
So
our
goal
is
to
get
both
of
those
done
before
the
security
audit
and
then
hopefully,
after
the
security
audit
is
done
and
we
address
any
issues
that
are
brought
up
by
the
audit
soon.
After
that,
we
can,
we
can
launch
for
production
use,
which
is
our
medium
term
goal,
and
so
we're
aiming
to
do
that
summer
sometime
in
the
summer
of
of
this
year,
and
then
our
long-term
goal
so
thinking
more
over
the
next
year
or
two
is
really
to
differentiate
forest
from
the
other
implementations.
F
Oriented
implementation,
and
you
know
we're
still
sort
of
planning
out
what
that
looks
like,
and
we
will
share
more
details
as
we
figure
that
all
out,
but
that
is
definitely
the
long-term
plan,
and
then
we
do
have
a
quick
demo
as
as
requested
by
emily.
This
is
a
video
that
eric
our
tech
lead
made
when
we
first
connected
to
mainnet
and
I'll
just
quickly
play
this.
So
you
get
an
idea
of
what
it
actually
looks
like
when
you
run
a
node
and
connect
to
mainnet.
G
Hey
hey:
what's
up
it's
eric
from
the
chainsafe
forest
team
and
today
I'm
just
making
a
short
one
to
two
minute:
clip
showing
forrest
sinking
up
to
mainnet,
so
I'm
just
gonna
share
my
screen
right
now
so
yeah.
As
you
can
see
here,
we
have
a
forest
file
coin
node
running
on
an
aws
instance
in
the
cloud
on
the
left
here.
You'll
see,
you
know
all
the
logs
that
we
are
currently
printing
out
for
forest,
so
this
is
force
running
on
the
top
right.
G
I
just
have
h-top
running
to
look
at
memory,
usage
and
cpu
usage
and
then
on
the
bottom
right
here.
I'm
just
looking
at
you
know
the
current
you
know
latest
blocks
coming
in
and
all
of
that
I
could
look
at
the
logs,
but
I'm
printing
more
stuff
than
just
you
know.
What
tip
sets
and
blocks
are
coming
in,
for
example,
like
you'll
see
some
some
logs
from
the
vm
and
all
of
that
so
yeah.
G
So,
as
you
can
see
here,
we're
currently
caught
up
to
head
we're
processing
blocks
as
they
come
in
and
yeah
we've
been
able
to
run
these
nodes
pretty
well.
For
you
know
a
few
days
at
a
time
we
haven't
really
tried
running
it
any
much
longer
than
that,
because
you
know
I've
been
you
know,
making
some
commits,
and
then
I
wanted
to
test
them
outside
to
stop
the
machines,
but
I'm
sure
it
could
run.
G
G
I
just
have
some
flags
or
some
environment
variables
here
to
to
kind
of
show
what
logs
I
want
to
show,
and
you
just
run
the
force
binary
straight
up
like
that
and
you
just
hit
enter
and
takes
a
minute
or
two
to
kind
of
start
up,
but
currently
working
on.
You
know
minimizing
that
time
yeah,
as
you
can
see
here
on
startup
it
kind
of
fires,
all
of
the
cpus
on
you
know
full
cylinder,
but
on
all
cylinders
but
yeah.
G
G
G
Alrighty
so
yeah,
as
you
can
see
here,
we're
starting
to
receive
blocks
over
gossip
sub.
We
got
you
know
the
latest
block
at
six
five,
three,
three,
six,
six,
eight
and
we're
doing
a
catch
up.
Sync
right
now
and
we
should
be
up
to
head
shortly.
We're
currently
three
epochs
behind
and
yeah
force
is
chugging
along.
F
Cool
so
I'll
just
stop
that
there,
but
that's
just
a
quick
demo
of
you
know:
forest
getting
booted
up.
This
was
recorded
in
march,
so
the
block
numbers
and
all
that
is-
are
a
bit
outdated
and
we've
had
a
node
running
for
a
lot
longer
than
a
couple
days
but
yeah.
I
just
wanted
to
share
forest
in
action.
F
Just
also,
if
you
wanted
to
read
more
about
sort
of
what
we've
been
up
to,
I
would
recommend
this
article
written
by
our
communications,
lead
tim,
like,
which
goes
into
a
lot
more
depth,
yeah
about
what
we
were
talking
about,
and
you
can
find
this
on
our
medium
chain,
safes
medium
and
that's
about
it.
So
you
know
if
you're
interested
in
contributing
or
getting
involved,
check
out
our
github
and
look
for
issues
to
a
good
first
issue
and
feel
free
to
connect
with
myself
or
train
safe
on
twitter.
F
A
Awesome
thanks
chain,
safe
team
and
thanks
eric
for
being
here
as
well
and
for
the
demo.
I
love
that
if
anyone
has
any
questions,
amer
or
eric
can
answer
them
just
put
them
in
the
chat,
otherwise,
yeah
definitely
check
out
the
new
announcement
that
they
released
on
medium
yesterday.
I
actually
tweeted
it
out
from
the
final
queen
handle
as
well.
Oh
and
tim
put
it
in
the
chat,
so
that
is
awesome.
A
Okay,
guys,
we
are
running
a
little
bit
short
on
time.
So
if
there
are
no
questions,
let's
move
right
along
and
if
not
as
I've
said,
both
of
the
folks
here
today
from
chainsafe
are
on
the
file
queen
slack,
so
you
can
find
them
there
as
well.
Okay.
So
next
up,
we
actually
have
another
rust
implementation.
A
Max
is
here
with
us
today
from
protocol
labs,
and
he
will
be
discussing
the
state
of
rust
lib
p2p
max
is
a
software
developer
interested
in
distributed
systems,
type
theory
and
consensus
at
protocol
labs
he's
working
on
the
lib
p2p
project.
Maintaining
the
rust
implementation
previously
max
was
working
on
the
monitoring
system
prometheus
as
a
core
maintainer,
focusing
on
its
integration
within
the
kubernetes
orchestrator.
A
A
H
H
So
what
I
would
like
to
talk
about
today
is
wrestling
pvp,
so
we'll
we'll
talk
a
little
bit
about
what
lip
up
is
why
why
we
have
this
talk
in
general,
we'll
go
a
little
bit
into
like
what
wrestling
brings
to
this
ecosystem,
where
restlep
is
at
right
now
and
then
also,
let's
look
a
little
bit
into
the
future
of
rest
of
the
pvp.
Of
course.
That
also
is
the
future
of
wwe
as
a
shared
across
all
the
languages
yeah
and
then.
H
Lastly,
we
can
dive
a
little
bit
into
maybe
how
you
can
use
wrestling
p
or
maybe
even
how
you
can
get
involved
in
university
cool.
I
think
I
can
I
can
skip
the
introduction,
as
emily
already
did
that
cool.
Thank
you
very
much
for
that
feel
free
to
reach
out
to
me,
either
in
private
or
in
public
either.
One
is
fine
happy
to
to
answer
question
and
yeah
talk
to
the
community
around
us
all
right.
H
So
before
we
talk
about
rush
qp,
let's
talk
a
little
bit
about
lipip,
so
I
just
copied
the
the
description
from
the
specs
repository.
Let's
not
reinvent
the
wheels
here,
so
liberty
is
a
modular
system
of
protocols,
specifications
and
libraries
that
enable
the
development
of
peer-to-peer
network
applications
so
yeah.
H
To
summarize
like,
if
you
want
to
build
a
peer-to-peer
application,
you
likely
don't
want
to
reinvent
the
wheel
and
also,
if
you
buy
into
the
lip
up
ecosystem,
you
get
a
system
of
protocols
which
are
well
designed
the
specification
of
those
protocols
and
also
multiple
implementations
in
different
languages
and
one
of
those
languages
being
rust,
restful
people
cool.
So
where
is
libyp
coming
from?
Well,
it
grew
out
of
the
ipfs
project.
H
At
some
point
it
was
separated
out
of
the
project
being
its
own
project.
There
were
many
implementations,
as
I
said
earlier,
like
there's
the
golang
implementation,
which
is
driving
most
of
the
innovation
nowadays
as
like.
They
have
the
least
restricted
platform
in
the
end
and
also
protocol
apps
driving
the
growing
implementation.
H
Of
course,
there's
a
javascript
implementation
for
both
browser
and
node.js.
There
is
well,
obviously
you
saw
the
talk
title
so
there's
rustling,
there's
python,
there's
c
plus,
I
think,
there's
also
a
java
implementation.
Someone
also
started
a
haskell
implementation,
so
a
lot
a
lot
of
those
yeah
in
various
languages
cool.
What
is
lippy
used
for?
Well,
we
are
at
the
falcon
meetup
and
you
just
saw,
for
example,
forest
so
for
sure
yeah
it's
used
for
the
falcon
network.
It
grew
out
of
the
ipfs
network
and
still
used
in
there
heavily.
H
Of
course,
there
is
polka
dot
and
kusama,
for
example,
as
two
networks
there's
ethereum
two,
which
is
based
on
gpp,
the
general
library
framework
and
many
many
more
projects.
So
this
is
really
highly
adopted,
which
makes
this
very
exciting,
as
all
of
them
interrupt,
are
somewhat
interoperable
on
the
networking
layer
cool
so
not
to
talk
about
lip
up
today.
H
So
if
you're
interested
in
lip3
in
general
check
out
the
pvp.io,
I
think
that's
a
really
cool
website
which
will
get
you
started
on
the
general
project:
okay,
cool,
so
wrestling
pb,
so
obviously
wrestling
bb
is
an
implementation
of
the
lippy
specification
of
rust.
We
don't
have
all
these
fancy
names.
Like
the
all
the
file
coin
implementations.
H
It
was
started
in
2017
but
tightly
working
together
with
protocol
labs
and
the
whole
liberty
community
to
not
make
yet
another
peer-to-peer
library
but
actually
make
yeah
an
implementation
of
the
library
specification
in
west
cool
yeah.
I
don't
think
we
we
have
a
lot
of
time
and
while
I
would
love
to
do
a
whole
talk
on
rust,
that's
for
sure.
H
It's
still,
I
think,
an
important
idea
to
to
quickly
talk
about
why
a
certain
language,
I
think
it's
very
important
not
to
yeah,
write
the
hype
wave,
but
instead
really
come
back
to
that
question
quite
often,
so
in
general,
why?
Why
is
wrestling
bv?
Why
is
the
rest
implementation
of
the
lippy
v
important?
Well,
you
could
just
say:
well,
we
wrote
the
upper
layer
stack
and
rest,
so
we
really
need
a
language
underneath,
but
you
could
just
do
ffi
to
go
or
things
like
that.
H
So
instead,
let's
look
at
why
rust
for
a
liberty,
p,
implementation
cool,
so
in
general,
rust
tries
to
achieve
this
trifecta
of
performance
safety,
safe
concurrency.
We
already
saw
that
in
the
earlier
talk
on
forest,
and
why
is
that
important
for
networking?
Well,
first
of
all,
we
especially
in
networking
but
also
in
php
and
networking.
We
need
to
go
very
low
level
in
the
sense
that
we
have
to
directly,
of
course,
interact
with
the
operating
system
or
with
the
platform
that
we're
running
in.
H
We
have
to
be
somewhat
performant,
as
you
would
expect
that
for
a
networking
library,
we
need
a
certain
sense
of
safety
in
the
sense
that,
as
a
library
first
off,
you
want
a
certain
sense
of
safety
as
like
users
of
that
library,
trust
you
and
you
want
a
lot
of
safety
and
networking
in
general,
as
you're
handling
untrusted
data
and
last
in
a
peer-to-peer
networking
fashion.
You
want
to
be
extra
safe
as,
like
you
likely
also
don't
know
the
person
that
you're
just
receiving
that
untrusted
data
from
okay.
H
H
So
that
makes
it
very
versatile
and
very
exciting
in
general,
as
it
covers
the
whole
stack
cool
enough
of
wrestling
rust
in
general.
Sorry
to
do
this
little
detour,
let's
talk
about
rustly
pvp
and
what
I
want
to
get
across
is
basically
yeah
where
we're
at
and
also
who's
using
rusty
blue.
So
I
just
cut
a
new
version
of
recipe
actually
two
hours
so
now
we're
at
62
main
versions.
H
We
have
around
half
a
million
downloads
on
the
main
package
manager.
After
all,
I
have
a
small
disclaimer.
Of
course.
That's
a
lot
of
cia
systems,
but
still,
I
think
that's
that
shows
quite
a
lot
of
adoption
for
this
library.
We
have
a
lot
around
a
thousand
downloads
per
day
and
while
this
has
been
mostly
driven
by
parity
as
a
single
company,
there
are
like
92
contributors
in
total
on
the
wrestler
project
over
there
since
2017,
which
yeah
makes
this
quite
a
striving
community.
H
I
think
cool
who
is
using
it's
quite
an
important
question,
and
I
mean
we.
We
just
had
a
full
talk
about
one
user
and
which
we'll
come
to
in
a
little
bit,
but
first
of
all
like
of
course,
parity.
The
one
driving
the
implementation,
mostly
so
the
implementation
substrate
in
polka
dot,
then
yeah.
We
have
forest,
so
we
have
a
fico
and
implementation
using
wrestlery.
We
have
the
ethereum
two
network
using
wesley
pv
via
sigma
prime's
lighthouse.
H
We
have
various
ipfs
implementations
in
rust,
using,
of
course,
the
wrestler
implementation.
We
have
the
commit
network,
but
also
what
is
quite
exciting.
We're
not
in
libby
b
in
general
and
russell
b
in
specific,
is
not
only
used
in
this
decentralization
blockchain
space,
but
also
outside,
so
we're
taking
peer-to-peer
networking
somewhere
else
as
well,
which
in
this
case
is
actics
what
they
do
is
they
bring
iot
peer-to-peer
networking
to
industry
production
plans,
yeah
and
rustly
be
running
there
as
well
cool.
H
I
think
I
got
a
couple
more
minutes
what
we
can
cover
and
I
think
what
we
should
cover
a
little
bit
is
as
you,
as
you
just
saw
like.
A
lot
of
people
are
using
russell
b
today
and
it's
being
used
on
live
networks,
it's
on
par
in
a
lot
of
regards
with
the
go
lippy
p
implementation
again:
gold,
mostly
driving
the
innovations
in
liberty
in
general,
but
there
are
for
sure
some
shortcomings.
For
example,
rescue
pvp
does
not
yet
offer
quick.
So
quick.
H
The
transport
protocol,
but
emerits
of
other
protocols
just
want
to
highlight
a
couple
of
course
costs
up
for
falcon
and
ethereum.
Two
that's
very
important.
We
have
cadembia
and
we
also
have
a
nice
optimization
on
cademnia,
which
is
escademlia,
which
brings
you
some
extra
security
concerns
in
terms
of
when
you're
exploring
the
dht.
H
H
We
have
a
bunch
on
transports
again,
no
quick,
sadly,
but
after
all
we
have
tcp.
You
can
wrap
that
with
various
encryption
mechanisms
and
you
can
also
build
websockets.
On
top
of
that,
why
is
websockets
important?
Well,
you
want
to
talk
to
browsers,
and
you
might
even,
of
course,
want
to
talk
to
browsers
which
run
rustly
pvp
compiled
to
webassembly
in
the
browser,
cool
yeah,
there's
a
lot
of
recent
developments,
but
I
think
I'm
gonna
skip
on
those
and
we
we
can
come
back
to
those
either
in
the
questions
or
some
other
time.
H
I
wanted
to
highlight
those,
but
we
we
don't
have
that
much
time.
I'd
rather
talk
about
the
future
of
rescue
pvp,
and
maybe
the
pv
in
general,
and
I
think
the
the
number
one
thing
for
rust,
lbp
to
catch
up
on
is
net
reversal.
After
all,
it's
a
peer-to-peer
library
and
right
now
it
does
not
support
net
reversal
in
a
good
enough
way.
I
think
you
can
in
a
turn
style,
so
you
can
relay
your
traffic,
but
after
all,
like
net
hole.
H
Punching,
I
think,
is
a
must-have
in
peer-to-peer
which
we're
lacking
on
right.
Now
there
is
a
quick
effort
to
to
bring
quick
to
wrestling
pv.
It
would
be
very
cool
to
bring
webrtc
to
wrestlers.
So
that's
definitely
something
we'll
look
into
weber
to
see
just
a
small
reminder
like
that's
the
way
to
do
peer-to-peer
in
the
web
as
like.
The
browser
brings
support
for
it,
which
makes
this
yeah
really
exciting,
and
then,
lastly,
like
I've,
been,
as
you
might
know,
I've
been
very
involved
in
the
prometheus
ecosystem.
H
What
I
did
recently
is
a
bunch
of
user
interviews
with
the
main
users
for
first
dp
in
case
you
are
using
wrestling
pv,
and
you
would
like
to
tell
us
what
you
like
what
you
don't
like,
what
you're
missing
and
so
on.
Just
hit
me
up
and
I'm
happy
to
schedule
a
call
around
that
cool
all
right,
so
getting
started
on
rusty
pvp.
H
Well,
obviously,
you
could
use
one
of
the
implement
or
one
of
the
projects
using
rustybv,
but
you
can
also
dive
into
libpdp
in
general
via
docs.libib.io,
and
you
can
dive
into
rust
library,
which
you'll
find
all
the
details
on
the
main
readme,
and
this
is
an
open
source
project.
So
if
you
want
to
get
involved
in
general,
only
p2p
things,
I
think
the
best
place
is
to
start
on
the
specs
repo.
H
So
on
the
specifications,
if
you
want
to
dive
into
a
specific
implementation
like,
for
example,
rest
dpp,
I
think
most
of
the
projects
do
getting
started
labels.
The
rest
implementation
definitely
does
so
get
started.
There
get
involved
with
the
community
and
talk
to
us
cool
last
slide.
Yeah
again,
some
some
contact
details
in
general
communicate
with
us
over
the
repositories,
ask
questions.
We
have
a
discussion
forum
both
for
wrestling
pv
and
lippy
in
general
and
yeah
we're
happy
to
to
to
have
everyone
involved
in
the
project
cool.
That's
it
for
my
site.
A
Let's
see,
I'm
not
sure
if
there
are
any
questions
at
the
moment,
but
austin
actually
put
something
in
the
chat,
a
github
issue
on
wrestling
pdp
and
then
yeah
max.
If
you
have
any
other
links
that
you
would
like
to
share,
just
put
them
in
the
chat
and
people
can
get
started.
Building
on
wrestling,
p2p,
yeah.
A
A
I
A
D
G
I
A
I
A
I
D
F
I
Firstly,
we
need
to
do
yeah
to
make
it
to
make
it
interoperate
with
doterra
so
yeah,
because
lotus
is
a
reference
of
the
falcon
specification,
as
I
just
mentioned,
and
of
course
we
need
to
integrate
with
the
latest
consensus
and
to
follow
any
change
of
the
specification
and
also
the
expectators
and
yeah,
because
the
kill
falcon
and
yeah
also
corvilles
and
actually
was
developed
before
the
latest
specification.
We
have
a
lot
of
sense
to
change
to
be
complete
with
your
mechanisms,
so
we
have
done
some
data
structure
change.
I
I
D
I
In
general
is
a
little
bit
higher
the
average
of
the
network,
which
is
very
good,
so
our
next
step
is
to
have
a
route
and
have
a
due
date
to
support
many
pool
which
is
called
a
disability
medical
instead
of
currently
meaning
miners
are
running
the
cluster
bending
pool.
So
our
tactic
is
to
support
more
many
meaning
and
yeah
small
miners
and
yeah
to
to
help
them
to
be
more
competitive
in
this
network.
I
I
I
So
I
want
to
show
you
one
by
one
very
quickly,
as
I
mentioned,
the
shield
module,
which
can
yeah
serve
for
many
miners,
which
is
compatible
with
the
falcon
falcon
protocol,
of
course,
and,
very
importantly,
which
is
interoper
yeah
interoperable
with
lotus
api.
So
it
could
support
a
mix
deployment
with
lotus
components
too,
and
I
want
to
mention
that
we
have
the
common
component
and
and
the
unified
os
and
module
under
the
development.
I
I
And
next
one
is
available
miner,
which
is
important
and
which
is
different
than
the
lotus
miner,
a
because
which
could
support
the
disability
demanding
poor
and
to
support
many
many
actors.
You
know
many
many
manners
and
each
manner
could
be
32,
gigabytes
circuit,
size,
minor
or
yeah,
six
or
64
in
gigabytes,
yeah,
section
salesman,
which
doesn't
matter
actually
and
we
have.
I
D
I
We
have
a
multiple
chance
of
the
block
in
one
epoch
and
yeah
so
that
we
yeah
we
could
have
we
yeah.
We
could
avoid
the
message
and
duplicate
and
enos
blocks
and
to
improve
the
their
performance
and
also
called
support.
What
we
imposed
yeah,
improving
okay
as
the
next
one,
is
a
maintenance
messenger,
and
we
have
the
version
1.0
launch
it,
which
can
support
the
report
wattage
and
can
support
the
mode
and
recognize
the
storage.
I
You
could
have
many
years
to
manage
your
yeah,
your
minor
and
orders,
and
you
want
to
control
the
security
and,
for
example,
for
the
controller
and
addresses
you
may
only
want
the
controller
addresses
only
to
send
the
proving
messages
instead
of
any
other
messages.
So
you
could
configure
the
yes,
the
security
policy
to
to
filter
out
or
any
other
messages
yeah
for
you
for
signature,
and
we
also
provide
the
encrypted
and
the
private
key
and
for
the
case
store
and
to
improve
the
security.
I
Okay,
next
one
is
about
the
bayless
center,
which
is
very
important
is
because
we
want
to
have
the
vanilla
center
to
support
multiple
and
smaller
workers
and
which
is
still
in
progress.
The
development-
and
you
know
which
and
of
course,
quote
work
together
with
the
common
modules,
as
I
mentioned,
yeah
in
previous
pages,
and
which
could
support
yeah
diversified,
your
storage.
I
Okay,
so
after
I
introduced
all
of
this,
I
was
our
target
in
this
month,
and
next
month
is
to
have
a
jury
needs
1.0
and
yeah.
By
the
way,
we
are
also
in
the
pros
the
progress
of
security
audit,
so
we
plan
to
complete
the
audit
in
this
month
too,
and
we
will
have
a
new
release.
After
this,
we
could
have
a
widespread.
I
Deployment,
so
we
will
try
to
run
the
first
pool
with
three
to
five
miners
yeah,
together
with
the
common
services
to
serve
all
these
manners
yeah
within
these
months
and
you
may
we,
you
were
planning
to
run
in
more
ports,
yeah
very
smoothly.
That's
our
target,
okay,
so
yeah.
Let's
work
together
to
build
a
better
falcon
so
and
here
yeah.
We
also
want
anyone
who
want
to
contribute
or
to
join
the
venus
and
your
development,
and
you
are
very,
very
and
welcome.
Yeah.
I
A
It
doesn't
look
like
we
do,
but
thank
you
for
joining
us
stephen.
I
know
that
it
is
extremely
early
your
time,
so
I
hope
you're
getting
a
jump
start
on
your
day
at
least,
but
that
actually
concludes
our
meetup
for
today.
Thank
you
all
for
joining
the
april
filecoin
virtual
meetup,
and
as
always,
thank
you
to
all
of
our
incredible
speakers
for
taking
the
time
to
share
your
expertise
and
your
projects
with
us
today
and
always
for
displaying
what
an
amazing
ecosystem
that
we're
building
together.