►
Description
Join Yiannis Psaras and Hugo Dias for an overview of the novel features that the FIL Spec platform integrates and run through the process of editing the specification. Lastly, we’ll set the future plans and vision for the Filecoin Specification.
Join us for Filecoin Liftoff Week, an action-packed series of talks, workshops, and panels curated by the web3 community to celebrate the Filecoin mainnet launch and chart the network’s future. https://liftoff.filecoin.io/
Events take place all week, October 19-23, 2020. #FilecoinLiftoff
For more information on Filecoin
- visit the project website: https://filecoin.io/
- or follow Filecoin on Twitter: https://twitter.com/Filecoin
Get Filecoin community news and announcements in your inbox, monthly: http://eepurl.com/gbfn1n
A
So
our
effort
was
kind
of
focused
around
this
area,
of
keeping
everything
in
one
place
so
that
we
can
make
everyone's
life
easier,
and
you
know
the
process
should
be
that
someone
should
read
the
spec
first
and
then
go
and
write
the
implementation
then
test
the
implementation
and
there
and
then
release
release
the
code.
So
this
is
the
ideal
thing,
but
in
order
to
do
that,
we
need
to
start
from
the
spec
first.
A
This
project
had
two
kind
of
different
different
goals:
different
directions.
One
was
to
build
the
platform
to
allow
for
the
teams
to
discuss,
protocol
design
and
improvements,
and
you
know
everything
that
comes
around
such
a
big
protocol
as
filecoin
and,
on
the
other
hand,
to
update
the
the
content
itself.
A
So
we
had
to
go
through
everything
that
existed
there
up
until
the
point
that
we
started
this
project,
but
because
the
file
going,
you
know
the
development
is
moving
with
lightning
speed.
Several
parts
had
run
out
of
date,
so
we
had
to
go
back
and
review
everything
and
update
the
the
existing
text
in
the
middle.
We
had
to
go
back
and
forth
with
several
stakeholders,
which
was
the
community.
A
It
was
the
file
going
teams
and
we
had
to
design
I
trade
in
order
to
get
feedback
for
all
the
features
that
we
wanted
and
those
that
we're
going
to
present
today,
but
also,
of
course,
the
content
itself.
And
you
know
we
had
to
review
to
verify
if
something
is
correct
by
talking
to
the
teams
by
checking
the
code
and
updating
what
was
there
before.
A
A
A
You
can
see
on
the
right
hand,
side
this
down
here,
where
you
have
whether
it
is
stable,
reliable
working
progress,
but
you
can
also
see
linked
links
to
the
report.
So
the
audit
reports,
so
many
of
the
parts
of
filecoin
have
been
going
through
audits,
either
external
or
internal
or
whatever,
and
there
we're
linking
to
those
reports
so
that
everything
can
be
in
one
place
and
it's
very
easy
to
navigate
through.
A
Another
thing
we
did
is
a
similar
dashboard,
but
for
the
implementation
part,
so
there
are
several
different
implementations
that
the
content
of
the
spec
I
should
mention
is
implementation
agnostic.
So
it's
not
focusing
on
lotus
or
venus
or
forest
or
any
of
those.
It's
the
general
protocol
design
that
every
one
of
those
implementations
should
use.
A
What
we
did
there
is
that
we
integrated
very
nice
features
such
as
ci
integration
and
test
coverage,
so
that
this
dashboard
is
getting
automatically,
is
pulling
information
from
other
repositories
and
is
updating
this
this
implementation
dashboard,
so
that
someone
can
see
you
know
what
is
the
test
coverage?
What
is
the
if
the
tests
are
passing
and
so
on
and
so
forth?
This
is
a
very
nice
feature,
I
think.
A
Finally,
we
had
a
progress
bar
stabilization
progress
bar,
which
shows
you
know
up
to
which
point
we
have
reached
so
far.
We
can
see
that
you
know
the
stable
and
reliable,
basically
all
the
details
that
someone
needs
is
more
than
80,
and
you
know
we're
looking
to
improve
that
even
further
and
get
it
all
to
blue
and
a
hundred
percent.
A
So
with
this
I
would
like
to
pass
over
to
hugo
who
is
going
to
talk
a
little
bit
more
in
detail
about
how
you
can
use
the
the
spec
repo,
how
you
can
update
the
spec
itself
and
all
the
interesting
features
that
it
includes,
including
you
know.
You
should
think
why
you
can
use
it
as
well.
You
can
you
can
get
the
repository
and
use
it
for
your
own
specification.
A
B
So
first
I
want
to
go
I'll
talk
a
little
bit
about
how
we
started
all
this.
So
we
wanted
to
go
to
kind
of
do
the
the
1.0
version
of
the
the
spec
repo
and
we
tried
to
focus
on
the
user
experience,
and
this
is
basically
to
make
this
the
the
spec
repository
the
best
place
to
write
specification
content.
B
So
we
can
have,
like
keanu,
said
a
single
source
of
truth
for
the
for
the
implementation
for
the
protocol
for
everything
about
the
falcon
system.
So
we
we
kind
of
created
three
core
objectives.
So
first
we
went
with
it
needs
to
be
easy.
Writing
content
needs
to
be
just
marked
down
and
some
file
structure.
It
needs
to
be
really
easy,
so
it's
it
doesn't
take
too
long.
It
doesn't
take
too
too
much
time
with
like
tooling
and
running
and
getting
errors
don't
know,
and
the
writers
don't
know
what
to
do.
B
B
But
if
someone,
if,
if
a
writer
right
does
something
wrong,
he
needs
to
get
an
error
that
explains
exactly
what's
going
on
and
in
the
e
and
it
explains
easily
how
to
fix
it
and
the
third
one
is
it's
enabling.
So
we
want.
We
want
to
get
to
a
point
where
we
have
a
stable
base,
but
we
also
want
to
get
to
add
new
features,
new
advanced
features,
but
those
need
to
be
easy
to
maintain
need
to
be
easy
to
integrate
with
the
the
content,
the
text,
content
and
all
that.
B
So
we
went,
we
started
with
this,
like
our
planning
started
from
this,
and
I'm
going,
I'm
gonna
go
through
each
of
these
and
show
you
some
of
the
features
and
the
tooling
that
we
have
so
first,
the
easy
part.
So
you
have
here
some
images
with
examples.
So
basically
almost
every
feature
is
like
is
based
on
the
on
simple,
normal
markdown
syntax,
and
we
also
have
a
comprehensive
documentation
for
all
of
those.
B
B
You
just
need
to
do
these
two
steps
on
the
left,
like
npm,
install
npm
start,
and
you
have
a
real
time
preview
in
the
browser,
and
you
can
see
exactly
how
your
content
exchange
is
changing
the
the
website,
or
you
can
even
just
edit
directly
on
github
and
the
continuous
intuition
system
takes
care
of
all
the
boring
stuff.
Everything
is
taken
care
of
you
either
get
an
error
that
explains.
B
What's
going
on
and
tells
tells
you
what
how
to
fix
it
or
you
pass
and
everything
is
ready
to
to
deploy
to
production,
so
the
consistent
parts?
This
is
about
like
the
errors.
As
I
I
was
telling
you.
The
system
behind
the
spec
includes
all
kinds
of
validation
linking
formatting
features,
and
this
is
to
really
ensure
consistency.
B
It's
really
important
for
us
to
like
not
have
like
broken
links,
broken
images
in
the
in
the
spec
websites
and
all
these
tools.
All
this
validation
basically
ensures
that
and
also
enables
like
an
easier
review,
because
the
linking
everyone
uses
same
linking
everyone
uses
the
same
formatting,
so
they
can
forget
about
all
of
that
and
just
focus
on
the
content
and
all
the
boring
stuff
is
handled
by
the
tooling,
the
ci
and
everything
else
and
the
writers
can
just
focus
on
the
content
and
discussing
the
content
and
reviewing
the
content.
B
So
the
third
is
about
enabling.
So
we
also
wanted.
You
already
saw
some
of
those
features
like
the
gita
integration.
We
wanted
to
to
create
some
cool
advanced
features,
but
they
need
to
be
they
they
need
to
integrate
seamlessly
with
the
content.
You
need
to
be
easy
to
maintain
so
one
of
those
this
one,
the
first
one.
I
really
like
this
one,
because
we
it's
kind
of
a
it's
called
embeds
with
symbol,
lookup
and
comments
extraction.
B
What
this
does
is
you
can
basically
import
from
github
directly
from
a
file
in
a
repo.
Like
the
example
here
from
the
go
data
transfer
repo,
you
can
import
the
file,
but
you
know
you
don't
embed
you.
If
you
don't
need
to
embed
the
full
file,
you
can
look
up
for
a
symbol,
so
in
this
example,
you're
just
seeing
you're
just
embedding
the
website
the
interface
itself
and
nothing
else
on
the
file,
and
you
can
we
can
even
do
a
comment
extraction.
B
B
B
The
third
one
is
is
more
about
like
assets
pipeline,
so
really
important
thing
to
kind
of
explain
how
protocol
works
is
like
having
a
a
way
to
process
diagrams
in
different
formats.
Like
we
support
mermaid,
we
support
graphics,
but
you
don't
need
to
know
anything
like
how
to
embed
these
types
of
diagrams
how
to
render
those
types
of
diagrams
in
the
website.
So
you
just
use
the
normal
image.
Syntax
and
everything
is
handled
automatically,
there's
a
watcher
for
the
files.
B
B
We
had
at
least
one
of
the
the
proofs
that
had
like
a
big,
big,
huge,
actually
ktx
content,
which
uses
like
basically
all
of
the
features
that
ktek
supports
and
we
were
able
to
integrate
it
in
the
website.
Everything
gets
rendered
properly.
Everything
is
clear:
every
you
can
see
no
rendering
issues.
Everything
is
perfect
and
it's
easy
for
the
writers
that
need
this.
This
syntax
to
to
use
it.
That's
the
main
thing
it
needs
to
be
easy
to
use.
B
So
now
for
the
future.
As
I
was
telling
you
about,
it's
really
important
to
have
a
good
base
to
build
upon
and
to
build
new
features.
So
we
have
a
lot
of
like
the
building
blocks
are
already
there.
We
already
have
like
the
building
blocks
for
new
feature
that
we
want
to
add
to
the
spec
and
to
the
spec
website,
and
some
of
those
are
the
like:
integra
integration
with
the
fibs
process.
B
B
Contents
plus
the
the
whole,
the
tooling
and
the
the
the
full
context
of
how
that
content
has
evolved
through
time
in
the
in
one
place
in
one
website,
and
you
can
see
it
all,
you
can
navigate
it
all
in
a
nice
and
easy
way.
One
other
feature
that
it's
really
important
is
also
to
add
more
context,
and
this
is
about
the
tests.
B
The
oni
team
did
a
great
job,
doing
a
bunch
of
a
bunch
of
tests
that
spectres
and
all
that
multiple
implementations
are
already
using
those,
and
we
want
to
create
visibility
in
the
spec
website
about
these
tests
and
how
they
run
if
they
pass
and
how
they
evolve.
Also
and
yeah.
That's
our
vision
for
the
future
and
the
new
features
that
we
want
to
have
to
the
to
the
spec
ripple.
So
yeah,
please
check
out
the
our
website
inspec
falcon
rao.
B
A
No
really
just
to
say
that
in
this
github
repository
specs
repository,
there
is
a
very
detailed
readme,
where
you're
going
to
find
everything
that
you
need
in
order
to
run
the
whole
thing
locally.
And
you
know
all
the
different
commands
in
order
to
do
all
the
great
stuff
that
hugo
was
just
talking
about.