►
From YouTube: FVM Space Warp Summit 🛸 Understanding the FVM
Description
Raúl Kripalani of Protocol Labs explains onboarding Ethereum developers to the Filecoin EVM.
Follow us! https://linktr.ee/filecoinio
Subscribe to our newsletter! https://bit.ly/3Oy8J9j
#fvm #filecoin #fevm
A
A
B
Aye
hi
carte
hi,
everybody
very
excited
to
be
here:
I'm
just
gonna
quickly
share
my
screen
and
I'm
gonna
be
talking
through
understanding
the
podcast
ebm
today.
Just
to
give
you
a
little
bit
of
information,
I
know
you
were
all
focused
on
building,
but
it's
ideal
to
have
just
a
second
there
you
go
I
think
I
think
we're
good
with
a
share
now,
fantastic,
all
right.
So
hey
my
name
is
Raul
preplani
I'm,
the
fem
Project
Lead
very
excited
to
be
here
very
excited
about
everything.
B
That's
going
to
happen
over
the
over
the
course
of
the
next
week's
we
have
been
working
on
the
Falcon
project,
for
as
Modi
said,
for
a
little
over
a
year
we
launched
in
July.
Last
year
we
launched
the
fem
to
the
Falcon
Network.
So
really
the
fem
is
already
powering
Old
State,
Transitions
and
mainnet
I'll
talk
more
about
that
in
a
second.
B
But
this
is
the
next
big
milestone
is
just
around
the
corner
40
days
away
fathom
if
everything
goes
right,
febin
will
hit
mainnet
around
in
the
first
week
of
of
March
in
in
that
time
period.
So
yeah
really
excited
to
be
here
and
to
get
all
of
this
ecosystem,
and
this
realm
of
opportunities
are
dick
stride.
B
B
We
don't
really
expect
a
lot
of
Divergence
and
we
don't
expect
a
lot
of
kind
of
like
hey,
what's
going
on
here
moments,
but
I
think
it's
really
important
for
you
to
know
how
things
work
under
the
hood,
because
it
will
make
your
journey
easier
and
more
frictionless
as
your
as
you're
moving
forward.
So
having
said
that,
as
Blondie
mentioned,
the
fem
project
delivers
on
chain
compatibility
to
the
FICO
Network
just
wanted
to
leave
with
that,
and
this
is
basically
what
the
fem
looks
like.
B
B
But
we
will
have
further
runtimes
down
the
line
like,
for
example,
the
wasem
need,
if
we
also
called
it
native
runtime,
secure
my
script
and
other
potential
things
that
could
be
layered
on
top
of
the
fem,
so
that
it's
possible
to
run
different
kinds
of
programs
on
top
of
on
top
of
the
fdm
and
on
the
podcast
Network.
Now
the
fem
itself
is
very
much
inspired
by
the
by
the
Unix
architecture
and
is
built
around
the
concept
of
Sysco.
B
So
basically,
everything
that
is
running
inside
the
fvm
whenever
it
needs
access
to
the
environment
or
it
needs
to
escape
that
sandbox.
It
would
perform
a
Cisco,
and
some
of
those
Primitives
are,
for
example,
data
accesses,
which
all
revolve
around
the
concept
of
my
pld,
which
stands
for
interplanetary
link
data.
That
is,
our
data
model
in
the
Falcon
blockchain.
It
is
also
the
data
model
of
ibfs
and
all
state
reads
and
writes,
translate
into
ibld
States
and
rights
by
assess
goals.
This
also
the
fem
also
has
we're
introducing
foreign
addressing
support.
B
So
this
is
the
ability
for
or
to
assign
addresses
that
are
actually
means
something
that
respects
some
semantics
of
another
Gene
like,
for
example,
if
you're
in
addressing
and
I'll
go
into
that
in
a
second.
It
is
also
prepared
of
repairing
the
way
to
introduce
the
concept
of
abstract
accounts,
and
it
also
has
the
ability
to
to
perform
a
resource
metering
by
a
gas
accounting.
So,
having
said
that,
we're
launching
evm
compatibility
right
and
ebm
compatibility
is
enabled
by
six
key
elements.
B
First
of
all,
the
buy
coin
evm
runtime,
which
we
nickname
febim
for
a
short
name,
ethereum
address,
support,
ethereum,
Account,
Support,
ethereum
transaction
and
signature
support
and
the
the
ethereum
Json
RPC,
which
allows
for
seamless
compatibility
with
tooling
and
libraries
and
also
actual
events.
I'm
gonna
cover
the
first
five,
just
to
kind
of
like
give
you
a
little
bit
of
a
glimpse
into
how
things
work
under
the
hood.
B
A
one
cover
a
one
cup
of
the
sixth,
but
if
you,
if
you
want
more
information
on
how
how
that
works
at
the
protocol
level,
just
pick
me
on
slack
or
a
Discord.
Now,
let's
dive
into
the
Litecoin
evm
runtime.
What
you
need
to
know
is
that
the
evm
runtime
is
basically
an
actor
on
the
five
coin
chain.
An
actor
is
code
that
lives
on
the
chain
on
the
filecoin
chain,
and
it
is
wasn't
code
that
gets
run
within
the
water
run
type
now
the
which
is
the
fem.
B
Now
the
EDM
runtime
itself
is,
as
I
said,
one
more
actor
and
it
contains
a
slim
down,
ebm
interpreter,
which
has
been
specifically,
which
we've
specifically
optimized
for
for
Watson
environments.
It
is
ethecarium
Paris,
Fork
compatible,
and
it
supports
all
note,
codes
and
all
pre-compiles,
so
basically
EDM
bytecode
that
you
deploy
to
the
Five
Point
ebm
runtime
should
just
work,
and
this
is
the
experience
that
we're
really
trying
to
Target.
B
B
Now
it
integrates
with
a
fodcoin
environment,
and
basically
it
performs
reads
and
writes
by
fem
syscalls
I
mentioned
those
earlier
and
it
Maps
the
storage
of
the
evm
storage
into
the
iplt
data
model.
We've
introduced
a
new
data
structure
called
the
camp
to
support
this,
and
it
also
introduces,
besides
the
ethereum
standard
pre-combust
that
are
available
in
the
Paris
Fork.
It
also
introduces
a
number
of
Five
Point,
specific
pre-compiles
that
give
you
access
to
filecoin
specific
system.
Five
point
system
features
I'll
also
cover
those
in
a
sec
in
a
few
minutes.
B
One
important
thing
is
that
the
evm
runtime
does
not
perform
ethereum
gas
accounting.
Everything
related
to,
when
is
your
contract
going
to
hold?
How
is
gas
going
to
be
charged?
How
is
gas
use
going
to
be
measured
and
so
on?
It's
all
based
on
file
coin,
on
Falcon
gas
usage,
this
ebm
runtime
is
introduced
by
the
FIP
by
by
54.
B
So
if
you
want
to
take
a
look
at
that
and
kind
of
like
go
into
the
the
deep
deep
details
of
how
things
work,
that
is
a
really
good
reference
to
you
now
just
to
talk
about
ethereum
addresses.
So
the
T
headline
here
is
that
Phi
coin
is
able
to
work
and
recognize
ethereum
addresses.
How
do
we
make
this
work
fightcoin,
since
the
beginning
has
had
the
ability
to
have
multiple
addressing
schemes,
and
we
use
this
before
the
ebm
already
so
we've
got
F0
addresses
zero
addresses
that
start
with
F0
or
t0.
B
If
you're
working
with
the
test
net
T
stands
for
for
test,
so
F0
t0
are
ID
addresses
F1
addresses
are
SEC,
p256
K1
accounts,
F2
addresses
are
not
a
contactors
and
F3
addresses
are
BLS
accounts.
We've
introduced
a
new
address
class,
which
is
which
is
F4,
so
every
address
that
you
see
prefix
web
F4
belongs
to
this
address
class,
we're
calling
it
the
delegated
address
class.
B
So
basically,
this
address
class
has
F4
and
then
it
has
a
number
which,
in
the
case
of
ethereum,
is
10
and
this
maps
to
the
ID
of
another
actor,
which
is
designated
as
the
address
manager
for
that
entire
space.
So,
basically,
every
address
that
you
see,
starting
with
f
or
one
zero,
is
an
ethereum
address.
So
I've
put
an
example
down
here.
B
This
f
f
port
f410,
address
maps
to
this
ethereum
address
and
it
looks
like
completely
different,
but
really
the
payload
of
that
address
is
exactly
the
same
as
just
encoded
with
base64
and
in
our
case.
So
that's
why
it
looks
slightly
different.
There
are
on
explorers.
Most
explorers
are
actually
prepared
to
display
the
eth
address
to
recognize
each
address
as
as
they
exist.
The
Json
RPC
endpoint
also
recognizes
and
translates
its
IT
addresses
transparently
it
just
it
just
works
so
everywhere
that
you
would
use
an
address.
B
Well,
when
the
protocol
would
create
is
what
we
call
the
placeholder
actor
and
a
placeholder
can
transition
into
an
ethereum
account
or
it
can
transition
into
an
ethereum
contract
depending
on
what
happens
next.
So
if
something
deplies
a
smart
contract
onto
that
address,
it
will
magically
convert
into
an
ethereum
account.
If
that
address
suddenly
sends
a
transaction
that
is
assigned
transaction
to
the
gene,
it
will
automatically
transition
into
into
an
ethereum
account,
and
this
is
completely
transparent.
B
You
don't
need
to
know
about
this,
but
when
you
go
to
an
Explorer
when
you
first
send
funds
to
yourself
through
faucet
and
hyberspace
or
whatever
you
go
to
an
explore
word,
you
will
likely
see
that
your
address
is
a
placeholder
and
the
first
time
that
you
send
a
transaction
from
that
address.
Through
your
metamask
wanted
or
any
other
wallet
it
will
transition
into
an
ethereum
account.
B
Another
thing
worth
mentioning
is
that
we
support
ethereum
transactions
of
type
2.,
so
these
are
rlp
encoded
signed,
ethereum
transactions
with
the
original
SEC,
with
the
original
ecd
DSA
signature
scheme
with
SEC
b256,
and
we
only
support
team
key
mentioning
this.
We
only
support
eip1559
transactions,
and
this
is
because
these
because
file
coins,
since
the
beginning
has
been
using
the
base.
V
model
has
been
using
the
eip1559
in
in
filecoin
terms
and
translated
into
into
the
Falcon
blockchain,
and
that's
why
we
only
support
this
kind
of
transaction.
B
So
if
you
most
tools
and
kits
and
so
on,
that
Zack
and
others
are
going
to
tell
you
about
after
after
this
presentation
already
sending
type
2
transactions
to
to
to
Phi
coin,
but
I
I.
Just
thought
it
would
be
worth
to
mention
here
now
at
the
RPC
level.
We
also
support,
if
has
to
make
gas
Max
priority
feedback,
gas
and
fee
history,
so
I
completely
implemented
and
usually
tools
called
these
methods
to
to
automatically
return
gas
values.
B
Now,
when
you
submit
an
ethereum
transaction
through
the
Json
RPC
endpoint,
these
behind
the
scenes
are
translated
to
flycoin
messages
carrying
a
dedicated
signature
in
the
future.
I
mentioned
that
we're
going
to
be
implementing
account
abstraction.
This
is
a
key
part
of
that
transition
towards
account
structure,
because
in
the
future,
we,
when
we
have
it
when
we
see
when
the
protocol
sees
a
delegated
address,
it
will
just
hand
off
that
signature
validation
to
an
actor
on
Jing,
which
can
be
anything
so
this
will
allow
actors
arbitrary
options
through
work
as
senders.
B
B
So
I
also
mentioned
that
a
key
element
of
making
Phi
coin
work
with
existing
ethereum
tools
and
libraries
so
that
this
so
that
deploying
on
filecoin
can
leverage
the
very
rich
ecosystem
of
tools
and
libraries
that
exist
for
part
coin
automatically.
Is
the
Json
RPC
endpoint
So
Below?
Does
the
reference
implementation
of
the
filecoin
protocol
supports
the
ethereum
Json
RPC
API
Lotus
is
also
the
client.
That's
currently
powering
hyperspace,
the
hyperspace
testnet.
We
expect
other
clients
like
forest
and
Venus
and
so
on.
B
We'll
also
join
that
test
net,
but
for
for
now
we
know
that
notice
is
implementing
this.
This
Json
RPC
as
I
said
this.
This
enables
immediate
ethereum
tool
compatibility
things
like
hard
hat,
remix
Foundry
brownie.
They
just
work
with
fibroid
and
there
are
the
your
the
URLs
for
hyperspace
down
here.
There's
a
list
of
the
methods
that
that
have
been
that
we've
implemented
in
that
in
that
RPC.
If
there
is,
these
are
the
standard
methods.
B
We
are
aware
that
other
ethereum
clients
have
specific
methods
which
then
tools
end
up
relying
on
to
like
what
we
do
specific
things.
If,
at
one
point,
you're
missing
a
method,
then
let
us
know
okay,
so
one
key
another
key
element
that
I
wanted
to
stress
about
the
filecoin
protocol
and
building
on
filecoin
is
that
much
of
five
coins,
verifiable
storage,
crypto
economy
and
basically,
everything
that
happens
at
the
final
coin
today
concentrates
around
the
concept
of
built-in
address.
So
these
are
implicit
smart
contracts
that
exist
in
the
protocol.
B
There's
a
talk
on
YouTube
that
one
of
our
core
devoted
present
gave
a
few
months
ago.
That
goes
into
into
this.
So
if
you
want
to
check
that
out,
he
does
a
really
good
Deep
dive
into
all
of
the
actors
and
how
all
of
this
works
and
I
think
it
could
serve
as
a
really
good
tutorial
to
get
we'll
start
pretty
quickly
now
to
interact
with
these
built-in
actors,
you
might
be
asking
well
how
do
I
hold
out
to
these
built-10
actors?
We
wanted
to
make
it
really
easy.
So
what
do?
B
What
do
we
do?
We
worked
with
zondax
to
build
a
set
of
solidity.
Libraries
that
just
behave
expose
a
number
of
salinity
functions
that
behind
the
hood,
do
all
the
plumbing
work
to
call
these
built-in
actors.
So
basically,
what
you'll
see
this
library
is
pretty
it's
it's!
It's
very
like
a
one-to-one
mapping
with
the
methods
exposed
by
by
built-in
actors.
So
this
means
that
a
slightly
low
level
and
what
I
expect
may
be
happening
as
as
a
result
of
this
hackathon.
B
That's
the
URL
I
know
that
Zach
is
going
to
go
into
this
as
well
after
after
this
talk,
so
I'm
very
excited
to
see
to
see
his
demo
as
well,
because
he's
building
with
the
solidity
hybrids
well,
we've
deployed
so
pour
this
hackathon
and
perpetually
we
have
deployed
a
network
called
hyperspace.
This
is
a
developer.
B
Just
two.
Two
months
ago,
it's
crazy
to
see
how
much
has
happened
in
just
two
months.
They
were
running.
Those
kind
of
like
Alpha
releases
were
were
being
delivered
on
a
Tesla
called
wannabe.
So
if
you
participated
in
hack
febim,
then
you
were
targeting
all
your
development
against
wannabe
there's
an
this
hybrid
space
is
a
new
testnet
that
is
deploying
beta
quantity
releases.
B
So,
while
wannabe
was
deploying
Alpha
quality
releases,
bleeding
edge,
hyperspace
is
deploying
beta
quantity
releases
and
as
a
one
key
one
key
difference
is
that
hyperspace
is
a
test
net
that
will
upgrade
instead
of
resetting.
So
we're
striving
to
preserve
all
of
the
state
and
contracts
without
breakages
that
you
Deploy
on
hybrispace.
B
You've
got
that
channeled
on
Falcon
slack
to
if
you
wanna,
if
you
have
any
problems
with
rpcs
with
explorers
or
with
the
test
net
itself,
availability
or
whatever
transactions
are
slow.
Whatever
just
ping
us
on
on
that
channel,
you
can
very
easily
add
this
network
to
your
metamask
wallet
or
to
other
waters
that
support
that
support.
B
The
web3
library
by
chainless.org,
so
just
go
into
their
search
for
hyperspace
and
tick
include
test
sets,
because
hybrid
hyperspace
is
a
test
that,
to
get
that
you'll
be
able
to
add
it
quickly
and
also
there
is
the
state
the
status
page
for
for
hyperspace,
test
Set.
Two
things
worth
mentioning
is
that
their
hyperspace
has
miners
that
are
very
happy
to
do
deal
making
with
you.
So
if
you're,
a
data,
dialysis
or
whatever
you
need,
you
want
to
have
deals
on
the
network
to
test
against.
B
Then
they
can
work
with
them
because
they'll
be
very
happy
to
to
to
create
deals
for
you,
even
though
there
are
already
a
number
of
deals
in
the
in
the
in
the
network.
So
if
you
go
into
the
Phil
Fox
Explorer,
which
I'll
introduce
next
and
go
into
the
deals,
tab
you'll
see
all
the
deals
that
already
exist
in
the
network.
B
So
these
are
some
of
the
these.
Are
the
explorers
and
hosted
endpoints
that
are
available
for
for
hyperspace,
you've
got
left,
you've
got
barracks
and
you've
got
Phil
Fox
as
explorers
that
are
currently
operating
with
hyperspace.
There
are
other
explorers
that
we
expect
well
also
that
are
currently
that
are
supporting
wannabe,
but
we
expect
them
to
transition
to
to
hyperspace
soon
as
well,
and
there
are
the
URLs
to
for
the
hosted
RPC
endpoint
so
that
we've
got
glyph
serving
and
an
end
pointer.
B
B
People
have
tested
with
Foundry
and
the
reports
are
good,
but
we
would
like,
if,
if
you're
inclined
and
work
with
Foundry,
if
you,
if
you're,
if
you
encounter
any
troubles
with
it,
let
us
know
same
with
brownie
and,
having
said
that,
I
wanted
to
go
into
I,
went
to
kind
of
like
stride,
ending
my
top
with
some
highlighting
some
notable
differences
that
I
think
as
a
developer.
You
need
to
know
when
you
develop
for
a
theater
four
or
five
coins,
four
five
coin
CVO.
B
So
some
notable
differences
with
regards
to
versus
the
ethereum
evm
is
that
concerning
execution
bare
value
sense,
so
this
is
transfer
of
values
which,
in
the
Falcon
protocol,
are
mapped
to
the
method.
Number
zero
of
two
smart
contracts:
well,
not
trade,
our
smart
contract
Lodge,
so
just
a
bear
send
to
a
Smart
contract
logic.
That
is
not
a
method.
Call
will
not
trigger
it
will
not
trigger
any
smart
contract
logic.
This
is
a
small
number
of
cases
that
this
is
a
feature
that
is
already
used
in
in
the
ethereum
protocol.
B
B
In
our
case,
we
because
it's
deprecated,
we
decided
not
to
support
it
and
to
drop
support
for
it,
and
there
are
some
small
differences
with
regards
to
self-destruct
Behavior,
which
we
believe
make
the
behavior
safer
than
it
is
in
ethereum
like,
for
example,
if
a
self-destructured
contract
gets
funds
after
it
calls
self-destruct,
but
before
the
transaction
ends
in
ethereum,
those
funds
would
be
lost
and
flag
when
they're.
Not
so,
and
there
are
some
other
op
codes
that
behave
slightly
differently,
but
it
should
be
things
like
difficulty,
because
we
don't
have
the
concept
of
difficulty.
B
Things
like
coinbase
and
other
things
behave
differently,
but
we
believe
those
should
not
cause
any
functional
Divergence
and
one
big
one
that
I
did
want
to
mention
is
concerning
gas,
gas
metering
and
execution
hold
are
performed
according
to
the
final
coin
gas
model
and
not
according
to
the
ethereum
gas
model.
So
this
means
in
the
Falcon
gas
model,
is
meant
to
be
updated
very
in
a
very
agile,
minor
manner
such
that
it
tracks
with
High
Fidelity,
the
real
execution
costs
of
code
and
as
well.
It
tracks
the
fine
coin.
B
Gas
model
actually
charges
per
bytecode
of
wasm
instruction.
Sorry,
it
charges
per
wasn't
instruction,
which
also
means
that
over
time,
the
ebm
runtime
is
going
to
be
changing
its
bytecode.
As,
as
we
go
through
different
network
upgrades,
it's
going
to
become
more
optimized.
It's
going
to
enter
to
use
new
functionality.
Libraries
are
going
to
change,
so
it
is
not
a
good
idea
to
hard
code,
specific
gas
values
in
ebm,
smart
contracts
that
you
deploy
to
filecoin,
because
the
gas
model
is
very,
very
Dynamic
and
ficon
as
opposed
to
ethereum.
B
So
this
is
a
really
important
point
that
I
wanted
to
highlight
and
a
few
other.
So
that's
the
third
Point
here
alfalcon
gas
costs
are
not
stable
over
Network
upgrades
and
the
second
point
there
is
that
gas
limits
set
when
calling
pre-compiles
do
not
apply
so
just
do
almost
end.
The
stock
and
I'm
a
little
bit
over
time
just
wanted
to
say
there
are
some
Advanced
kind
of
like
functionalities
that
we've
added
to
the
filecoin
evm
implementation
are
file.
Coin
pre-comb
Bots.
B
There
are
four
five
coin:
pre-compans
there
is
resolve,
address
lookup
delegated
address,
contactor
ID.
These
are
exposed
through
the
solidity
Library.
So
that's
you
see
an
example
of
that
on
the
on
the
right
they're
specified
on
this
fit.
If
you
have
any
questions
about
these,
we
will
be
adding
more
documentation
in
the
next
in
the
next
days.
But
if
you
have
any
questions
about
these
for
now,
just
bring
us
on
on
Slack
and
also
there
is
the
ability
to
handle
native
messages.
B
So
if
so
in
Phi
coin,
we
have
this
concept
of
a
method
number,
which
is
part
of
the
message
that
indicates
which
method
in
the
after
should
be
called
and
in
order
to
handle
arbitrary
messages
sent
to
ethereum
contracts
that
carry
method
numbers
arbitrary
method
numbers.
You
need
to
implement
this.
This
function
in
your
solidity,
smart
contract
currently
I
only
expect
this
to
be
necessary
if
you're,
using,
if
you're,
creating
a
deal
client
contract,
because
the
market
actor
will
call
into
the
deal
client
to
validate
the
client.
B
The
deal
proposal
through
a
native
call-
and
there
is
already
a
example
of
repo
in
a
template
that
does
this
for
you,
it's
I,
believe
Zach
is
going
to
be
introducing
it.
But
if
not
ping
us
on
on
slack
it's
it's
the
deal
client
contract.
So
this
you
could
use
the
code
in
that
in
that
contract
to
handle
these
kinds
of
calls
that
are
performed
over
native
calls
into
your
into
your
solidity
spark
contract
cool.
So
that's
everything
from
me.
Good
luck
and
happy
hacks
and
I'll
be
on
slack.