►
Description
If you're looking to supercharge your Web3 development, watch this informative webinar to learn how the EOS EVM can help you bridge the best of both worlds!
The EOS EVM allows developers to port and run Solidity-based tools on the EOS blockchain. Get ready to experience your Solidity smart-contracts in almost real time, with negligible gas fees on the high performance EOS ecosystem.
Speakers:
Adam Bouktila, CPO, Zaisan
Nathan James, Head of Developer Relations, ENF
Matias Romeo, Senior Engineer, ENF
DISCUSSION POINTS
- Adoption expectations and target audience.
- Development process of the EVM, the funding, and maintenance.
- Potential beneficiaries and real-world use cases.
- Transactions paid in EOS. Implications for community and project alike.
- Block time and its impact.
- Possible smart contract adjustments for block-based timing.
- Necessity of EVM with ChatGPT's Solidity-to-C++ rewriting capabilities
- A live demonstration of deploying a Solidity smart contract on EOS EVM.
Harness the accessible resources of the Ethereum community while taking advantage of the powerful performance of the EOS Network. Don't miss this opportunity to learn from expert panelists about this highly sought-after feature for developers.
KEY LEARNINGS
Understanding the EOS EVM
Real-world use cases and beneficiaries
Performance comparison and unique features
Getting started with EOS EVM
---
The EOS Network Foundation coordinates financial and non-financial support to encourage the growth and development of the EOS Network. We’re harnessing the power of decentralization to chart a coordinated future for the EOS Network as a force for positive global change.
// EOS Network Foundation //
https://www.eosnetwork.com
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosnetwork.com
#EOS #Web3
A
And
we
are
live
so
welcome
everybody,
let's
just
give
a
minute
or
so
for
some
more
attendees
to
join,
but
for
those
of
you
that
were
patiently
waiting.
Thank
you
very
much
really
excited
for
this
one
today,
but
as
I
say,
let's
give
a
couple
of
seconds
here
and
we
will
get
kicked
off
with
today's
session.
A
A
Okay,
guys.
Thank
you
very
much
for
joining
us
and
Welcome
to
our
video
series.
The
Ledge.
This
is
our
video
webinar
Series,
where
we
dive
into
all
things.
Web3.
Last
time
we
had
a
great
session
on
tokenization
of
real
world
assets
with
Alejandro
from
de
facto.
Anybody
who
missed
that
can
catch
it
on
demand
and
that's
very
much.
The
way
we'll
do
this.
A
Anybody
who
can't
join
us
live
we'll
make
sure
to
host
them
on
the
zyzen
website,
for
anybody
who'd
like
to
catch
up
so
without
further
Ado
I'm
going
to
introduce
today's
episodes,
and
we
do
have
a
special
one,
we'll
be
speaking
with
our
friends
and
partners
at
the
EOS
Network
Foundation,
and
today
we're
going
to
be
talking
about
the
new
EOS
evm
I
am
very
excited
for
this.
One
I've
been
a
huge
supporter
of
EOS
since
launch
I
was
speaking
with
Matthias
before
this
unfortunately,
I
had
a
lot
more
here.
B
A
This
world
we
could
spend
hours
talking
about
the
history
of
of
EOS
and
how
we
got
here,
but
despite
all
of
that,
I've
always
believed
in
the
capability
of
the
technology,
formerly
known
as
eosio
now
known
as
antelope
So
I
entered
the
community
more
of
a
kind
of
commercially
focused
person.
I
was
always
interested
in
the
potential
daps
and
tools
that
could
be
launched
on
on
EOS
and
that's
what
kind
of
got
me
to
can
my
real
job
and
go
into
this
wonderful
world
full
time.
A
So
that
was
about
five
years
ago
now
and
although,
since
then,
like
antelope
technology
has
always
been
solid.
There
was
one
thing
that
was
missing
and
that
was
an
EOS
evm
to
allow
developers
and
teams
to
solve
some
of
the
costs
and
scalability
issues
that
can
exist
on
eat
so
to
introduce
the
enf,
enf
or
ES
Network
Foundation
they're.
Now
the
lead,
developer
and
driving
force
behind
the
ecosystem,
and
it
is
super
refreshing
to
see
some
activity
and
forward
momentum
in
the
community.
A
We
at
zyzen
we
were
proud
to
partner
with
the
enf
during
the
road
show
last
year,
Nathan
and
I,
and
some
of
the
other
team
went
around
to
some
of
the
major
events
introducing
the
enf
talking
about
some
of
the
major
developments
that
were
coming
and
I.
Think
one
of
the
key
things
that
people
were
asking
about
was
the
evm.
So
I
am
really
excited
to
talk
about
that
today.
So
with
that
said,
I
do
want
to
shut
up
and
introduce
myself.
We
have
Nathan
James
and
Matthias.
A
B
It's
a
pleasure
to
be
able
to
be
here
today
and
talk
about
the
evm.
For
those
that
don't
know,
my
name
is
Nathan.
James
I've
been
with
the
EOS
Network
Foundation
for
about
a
year
now,
but
I've
been
with
the
EOS
Network
since,
before
it
launched
I
guess
it's
five
years
ago
now,
a
lifetime
ago,
I
created
scatter,
which
was
the
first
wallet
for
Eos
that
helped
launch
the
chain
and
serve
the
community
for
many
years
after
I
also
spent
the
last
couple
years
before
joining
the
enf
doing.
B
C
Thanks
Nathan
well
for
those
that
don't
doesn't
know
me,
my
name
is
Matthew
Romeo
I'm
originally
joined
the
EOS
ecosystem,
working
for
the
es,
Argentina
block
producer
and
a
couple
of
Hunter
goes.
I
joined
the
dnf
formally
as
a
software
engineer,
particularly
working
on
the
evm
compatibility
layer.
Well,
my
history
of
crypto
is
I
started
like
everyone
in
Bitcoin
I
I'm
from
Argentina,
so
Bitcoin
has
real
value
here
because
we
have
been
through
so
many
economic
experiments
over
the.
B
C
So
basically,
Bitcoin
catch
up
really
fast
here
and
one
of
the
conferences,
a
friend
of
mine,
told
me,
hey,
you
should
look
at
pictures.
It
has
some
interesting
stuff
like
stable
coins
and
and
I
saw
well.
I
would
start
looking
into
that
and
I
fall
into
into
that
rabbit
hole
and
from
there
I
started
working
on
pictures,
then
Steam
and
finally,
EOS
I
was
pretty
very
excited
to
have
a
general
proposed
platform
based
on
Depots.
C
A
Excellent,
thank
you
very
much
guys.
I
really
appreciate
it
and
I
guess
to
give
well.
First
I
do
want
to
introduce.
We
have
some
polls
that
we're
going
to
run
throughout
this,
so
the
first
of
the
polls
is
open
and
we
do
just
want
to
know.
What's
your
current
level
of
experience
with
the
EOS
Network
seems
we're
getting
some
great
interactions
already
and
most,
it
seems
to
say,
have
some
experience
with
the
US
there's
not
a
lot
saying
that
they're
an
expert
not
a
lot
saying
that
they're
completely
new.
So
that's
that's
good.
A
We
do
encourage
some
of
this
interaction.
It
really
helps
us
a
lot.
So
if
you
guys
check
out
the
polls
there
and
fill
in
that
would
be.
That
would
be
amazing,
so
I
guess
before
diving
in
I
mentioned
earlier.
You
know
EOS
Network,
it's
layer,
one
blockchain
super
fast
transaction
speeds
fast
finality,
but
we're
not
here
to
talk
about
the
EOS
Network
per
se.
If
you
guys
would
like
to
know
more
about
the
network
and
its
features,
I
suggest
you
check
out
the
enf
website.
A
So
that's
www.eosnetwork.com
and
I
have
to
say
the
team
has
been
doing
a
great
job,
on
updating
documentation
being
really
transparent
on
the
developments
and
the
updates.
So
please
do
check
that
out,
but
today
it's
all
about
the
evm.
What
is
if
how
it
works?
Why
it's
good
for
the
community
and
the
the
ecosystem
as
a
whole?
So
look,
let's
start
with
you
and
maybe
let's
zoom
out
a
little
bit,
and
even
not
even
just
the
EOS
evm.
But
what
is
an
evm?
Why
is
having
one
on
EOS
a
good
thing.
B
Okay,
I
guess:
there's
two
questions
there:
a
virtual
machine,
so
the
second
part
of
BBM
virtual
machine
is
just
a
Sandbox
runtime
environment
that
executes
code
in
the
case
of
blockchain.
That
code
would
be
a
smart
contract.
The
evm
or
the
ethereum
virtual
machine
is
specifically
crafted
sandbox
that
follows
the
ethereum
specifications.
B
So
if
you
look
at
most
of
the
top
chains,
they're
either
evm
chains,
meaning
they're
they're,
specifically
created
around
the
evm
specification
or
they
support
evm
development
because
of
that
most
developers
in
The
Wider
web
3
ecosystem
are
evm
developers.
They
know
solidity,
they
use
hard
hat
or
truffle
Foundry
huge
amount
of
other
tools
which
are
available
for
evm
development,
and
now
they
can
use
those
tools
they
already
know
and
are
maintained
by
dozens
of
decentralized
teams
to
build
on
EOS.
A
Awesome
awesome
so
and
I
mean,
of
course,
ethereum
has
such
a
rich
developer
ecosystem,
the
tooling
that
you
mentioned
as
well,
so
I
guess
trying
to
reduce
or
remove
any
barriers
or
additional
learnings
for
developers.
They
don't
have
to
learn
C
plus
plus,
if
they
don't
know,
if
that's
huge
right,
that's
huge
for
potential
adoption
and,
as
you
said,
for
being
able
to
Port
over
existing
projects
right.
So
that's
that's
awesome.
A
B
B
So
they
take
a
percentage
of
the
gas
fees
for
that
transaction
on
the
evm
side
in
order
to
re-up
themselves
for
what
they
spent
I
think
right
now,
it's
it's
10
and
I
know,
there's
discussions
of
potentially
increasing
that
in
the
future
and
we'll
talk
about
what
the
other
90
is
in
a
second
so
from
the
EOS
node.
The
next
component
is
the
EOS
contract
which
lives
within
the
EOS
Network,
so
the
ethereum
virtual
machine
that
we
spoke
of
before
runs
inside
the
EOS
virtual
machine.
B
You
can
think
of
this
kind
of
like
a
Super
Nintendo
emulator
running
on
the
Nintendo
switch,
we're
able
to
run
the
evm
compatible
smart
contracts
by
emulating
that
environment
in
which
they
run.
Naturally,
this
means
they're
also
using
EOS
native
resources
like
RAM,
for
the
storage
of
the
evm
state,
which
is
which
is
where
the
rest
of
the
fees
for
the
transactions
on
evm
go
to
automatically
purchase
that
RAM
on
the
native
side,
but
once
those
transactions
are
included
in
blocks,
they're
still
EOS
transactions
around
it
right.
B
So
we
have
to
take
that
information
and
wrap
it
into
something
which
is
useful
for
evm
tooling,
which
is
the
next
part
of
this
stack,
the
EOS,
evm,
node
and
RPC.
This
component
takes
the
EOS.
Formatted
information
transforms
it
into
evm,
formatted
information.
It
then
exposes
all
the
routes
that
evm
tooling
expect
to
exist,
which
enables
full
combat
ability
with
all
existing
AVM
software
that
lets
you
specify
custom
endpoints,
at
least
so.
Things
like
hard
hat,
truffle,
remix
metamask,
all
of
Etc.
B
All
work
out
of
the
box
with
El,
CBM
and
smart
contracts
also
do
not
need
any
special
modifications
to
work
with
the
lcbm
I
guess.
The
final
piece
of
this
is
probably
tokenomics
sure
we're
tokenomics
of
the
elcvm
are
quite
simple.
It's
a
base,
token
of
the
elcvm,
is
also
just
EOS,
so
it's
the
same
as
the
native
Network.
B
There
was
no
new
token
created
or
minted
specifically
for
the
evm
and
in
order
to
get
EOS
on
the
evm,
you
have
to
bridge
it
over
through
a
native
from
the
Native
network,
using
the
on-chain
trustless
bridge,
which
is
a
contract.
That's
also
that's
the
contract
deployed
on
the
es
Network
and
it
simply
forwards
your
EOS
to
an
evm
address
that
you
specify.
So
there
are
no
third-party
oracles
required
or
centralized
services
that
you
typically
see
on
other
chains
that
have
that
kind
of
bridge.
B
This
also
means
that
any
exchange
that
supports
withdrawing
tokens,
EOS
native
also
well
at
least
as
long
as
they
don't
have
a
contract
on.
It
also
supports
withdrawing
El
CBM
tokens
directly
on
an
ethereum
address
now,
so
exchanges
don't
have
to
do
any
additional
Integrations.
They
don't
have
to
do
anything
to
support
withdrawals
directly
to
your
new
ercvm
address
on
on
EOS.
So
all
exchanges
that
basically
supported
EOS
now
also
support
the
evm
as
well.
B
C
So
that's
one
of
the
things
that
the
ABM
runs
inside
the
sandaliers
contract,
meaning
that
any
Improvement
in
the
layer,
one
EOS
that
will
make
an
impact
also
in
the
ebm
contract
performance.
So
whenever
we
have
there's
a
roadmap
for
instant
finality
for
transactions.
So
by
the
time
the
underlying
layer
has
that
that
will
also
impact
the
ABN
transactions
and,
on
the
other
hand,
the
ucbm,
node
and
RPC.
A
B
B
C
Yeah,
it's
it's
a
new
standard
and
I
think
it.
It
was
a
great
idea
for
the
network,
EOS
Network
Foundation,
to
support
this.
This
kind
of
compatibility
layer
besides
besides
the
inefficiency,
I
ended
up
that
we
can
talk
about
the
the
evm
the
way
it
was
assigned
compared
to
the
runtime
that
we
have
natively
on
on
EOS.
There
are
pretty
big
differences,
but
the
ebm
is:
is
the
standard
one?
C
A
Very
well
said:
I
I
have
to
Echo
that,
from
a
zison
point
of
view,
we've
been
speaking
with
teams
and
companies
for
the
past
four
or
five
years
and
a
lot
of
the
times.
It's
a
question
we
get
asked
straight
up
is:
is
a
DVM
compatible
and
that
sometimes
has
been
a
blocker
when
we
were
getting
people
trying
to
Port
some
of
their
games
or
some
of
their
applications
over
to
EOS
and
and
hopefully
now
with
evm
that
that's
no
longer
the
case
and
and
I
think
you
said
it
really
well.
A
A
Thankfully
dnf
has
been
and
I
think
it
started
with
all
of
the
the
blue
papers
right,
getting
a
lot
of
the
community
thinking
about
some
of
these
gaps,
how
they
might
be
filled
from
there.
You
know
roll
into
to
projects
which
we
can
see
come
to
life
now,
which
is
fantastic,
so
I
know
you
did
mention
the
tokenomics
and
how
the
transactions
work.
We
can
dive
into
that
a
little
bit
later,
I
just
question
that
came
to
my
mind.
Let's
say.
C
A
C
You
just
think
in
terms
of
gas
price
and
and
gas
execution
and
gas
used.
So
yes,
it's
exactly
the
same
way
that
I
used
to
interact
with
an
ebm
chain
and
in
fact
we
we,
the
the
the
EPM
version
that
it's
deployed
right
now,
it's
the
the
London
Fork.
So
you
should
expect
the
exact
same
gas
usage
for
a
contract
that
is
running
on
any
other
dbm
on
other
platform,
then
the
one
that
you
have
on
EO
CBM
song.
C
Yes,
that's
a
really
interesting
point
because
I'm
pretty
big
fan
of
EOS
like
because
I
I,
like
the
platform
I
like
the
technology,
but
that
doesn't
mean
that
it's
kind
of
complicated
when
you
yes,
we
you
want
to
like
interact
in
some
high
level
way
so
having
to
think
about
the
resources
of
ram
net
and
CPU,
sometimes
make
your
life
a
little
bit
difficult.
Besides
the
thing
that
you
need
to
write
in
C,
plus
plus
or
any
other
language
that
can
translate
to
awesome.
C
A
Excellent,
that's
exactly
the
way
to
go
because
again
that
that's
been
I'm
trying
to
just
think
through
the
years.
All
of
the
friction
points
or
questions
which
I
had
been
gotten.
A
lot
of
a
lot
of
this
can
be,
as
you
said,
very
well
abstracted
away
or
simplified.
So
somebody
who
understands
the
development
in
a
certain
way
in
a
certain
technology
with
a
certain
set
of
tools.
They
can
still
do
that
and
that's
what
it's
all
about.
C
Right
right
and
and
also
take
into
account
that
the
EOS
has
a
really
great
throughput,
really
great
performance
and
also
has
been
working
like
without
interruption
of
service
for
many
years
by
having
this
compatibility
layer
on
top
that
makes
life
simple
for
developers
and
also
for
projects
to
move
in
a
easy
way
to
do
this
new
platform.
I
think
that
it's
a
good
combination
now.
A
Yes,
thank
you
very
much
for
that
guys
and
again,
just
directing
the
audience
we
do
have
some
polls
running
at
the
moment.
So
there's
an
introduction
poll
where
we'd
like
to
know
your
current
level
of
experience
with
EOS
but
I've
also
opened
another
question
which
is
How
likely.
Are
you
to
adopt
evm
for
for
some
of
your
dapps?
If
you
are
indeed
a
developer
or
a
builder,
and
it's
great
we've
got
40
of
the
the
responders
are
saying
that
they're
very
likely.
A
That's
now
gone
up
to
50
as
I've
been
so,
which
is
great
and
in
terms
of
the
the
level
of
experience
it
seems,
we've
got
about
60
of
people
saying
that
they
have
some
experience
with
EOS.
Some
we've
got
26
saying
that
they're
completely
new
to
to
EOS.
So
again,
if
you
missed
me
saying
at
the
beginning,
please
check
out
some
of
the
the
documentation
that
the
enf
has
been
working
on.
That
will
certainly
bring
you
up
to
speed
up.
A
You
know,
plus
the
GitHub
Etc,
if
you'd
like
to
catch
up
on,
what's
been
built
there.
So
I
do
really
appreciate
you
guys
giving
us
this.
This
breakdown
of
really
really
clear,
I
guess
I,
do
want
to
dive
a
little
bit
more
into
well
the
development
process
of
the
evm,
and
how
did
we
get
to
this
point?
I
guess
so,
let's
dive
into
that.
C
Well,
as
you
said
before,
it
was
it
all
started
with
the
blue
papers
that
were
put
forward
by
the
enf,
and
by
that
time
we
were
invited
to
work
on
a
blue
paper
related
to
wallets
and-
and
we
said
that
we
don't
see
that
we
can
provide
much
value
there.
But
we
wanted
to
focus
on
the
on
the
ebm
compatibility
layer
and
that
was
taken
by
the
enf
and
make
a
specific
group
a
working
group
to
to
work
towards
that
idea.
That
was
having
a
compatibility,
evm
compatibility
layer
on
top
of
EOS.
C
C
But
at
some
point
in
in
the
future,
we
decided
to
go
back
and
and
use
the
the
native
years
token,
which
basically
for
me,
was
a
the
right
decision
to
make,
because
all
that
also
impacts
on
the
demand
of
the
EOS
token
and
the
usage
of
the
use
Network.
So,
for
me
was
a
the
right.
Is
the
right
decision
to
take
I?
Don't
know
if
Nathan
wants
to
add
something
there
sure.
B
Yeah
the
I
mean
the
development
I
think
of
the
evm
predated
me
coming
into
the
enf,
so
it's
it's
been
in
the
process
for
a
while,
and
it
was
like
a
huge
undertaking
by
a
bunch
of
contributors
from
across
the
ecosystem.
It's
also
open
source
now,
so
anyone
can
browse
the
history
of
that
GitHub
repository,
which
is
really
nice.
The
development
process
is
actually
also
open
source
and
from
it's
on
GitHub
and
I.
B
There's
from
my
understanding,
there's
going
to
be
a
public
roadmap
published
soon,
which
will
also
provide
a
bit
of
clarity
on
what's
coming
down
the
pipeline
in
the
future
in
terms
of
feature
and
functionalities,
I
guess
it's
probably
also
important
to
note
that
EOS
is
our
only
target.
So
though
this
is
open
source
and
any
other
chain
can
adopt
it
and
get
the
benefits
of
the
wonderful
work
that
we're
doing
on
this.
We
aren't
offering
any
slas
or
support
to
any
chain
that
does
adopt
it.
A
B
A
Okay-
oh
thanks
to
that
that
was
a
follow-up
question
was
about
the
the
support
and
maintenance
going
forward
and
I
guess.
As
you
say,
we've
got
a
road
map
coming
which
please
everybody
keep
your
eye
out
for
that,
and
also
great
to
hear
that
it
is
open
source,
so
anybody's
able
to
go
check
the
histories
Fork
it
play
with
it.
B
C
B
In
web
3,
we
try
not
to
do
that.
We
try
to
get
something
out
as
quickly
as
possible
to
the
public
so
that
we
can
iterate
on
the
feedback
of
our
communities,
because
we
are
driven
by
these
huge
massive
communities
who
care
about
the
products
that
we're
creating
and
I.
Think
it's
a
much
better
way
to
drive
an
ecosystem
than
trying
to
make
this
own
bubble
in
our
head
and
then
yeah
only
release
it.
When
it's
super
ready
to
pop
correct.
A
You're,
absolutely
right:
excellent
I
mean
I'm,
so
moving
on,
this
is
kind
of
the
as
I
mentioned
earlier
on.
This
is
where
I
get
excited:
I'm
I'm,
not
a
techie
I'm,
a
commercial
guy
I'm,
an
ideas
guy
I
like
to
think
about
real
world
use
cases
and
and
kind
of
potential
benefits.
So
if,
if
we
were
talking
about
real
world
use
cases
or
ideal
project
types
that
that
should
come
in
and
utilize
this,
what
do
your
guys
take
on
that?
Let's
start
with
you,
Matthias.
C
Well,
I
have
the
perspective
most
of
the
developers,
so
I
will
say
that
any
project
that
is
looking
for
a
reliable
layer,
one
also
compatible
with
with
the
AVM,
can
benefit
from
from
this
platform.
But
thinking
in
terms
of
what
EOS
the
value
proposition
of
fears,
which
is
speed,
reliability,
you
you
get
by
that
really
cheap
transaction
price,
so
I
would
say
that
maybe
some
non-financial
applications
or
or
applications
that
that
the
transaction
cost
should
be
low
because
maybe
wheelchuber
dies.
C
Their
business
model
can
benefit
from
having
a
not
only
a
nibm.
That
is
cheap
to
say
something,
but
also
is
kind
of
predictable,
in
a
way
that
how
the
price
will
move
along
the
time
based
on
the
on
the
concession
of
the
network
and
that's
also
a
differentiation
for
a
differentiation.
For
me,
foreign
Nathan.
B
Well,
anything
that
you
could
potentially
do
on
blockchain.
You
can
now
do
on
this
right,
but
I
I
do
think
that,
because
of
the
speed
well
taking
the
speed
specifically
and
the
speed
of
EOS
evm,
specifically,
there
are
a
couple
other
possibilities
which
are
now
possible
on
EOS
that
aren't
necessarily
possible
in
others.
So
I
like
here's,
the
two
things
I
I
like
most
I,
like
social
media
and
I
like
games
in
terms
of
like
you,
know,
blockchain
applications
and
I.
B
Think
that
there's
a
couple
of
genres
of
games
that
you
can
now
do
on
EOS
that
you
can't
necessarily
do
on
other
chains.
So
even
something
as
simple
as
an
RPG
where
you
can
put
every
hit
of
a
mob
onto
the
chain,
that's
actually
possible
now,
whereas
it
would
be
incredibly
expensive
on
some
other
chains,
obtusely
slow
on
on
most
of
them.
A
Oh
excellent,
no
doubt
I
mean
when
I
when
typing
up
this
question.
Certainly
gaming
was
one
of
the
first
ones
that
came
to
mind.
We
had
from
from
a
zeizen
perspective,
in
working
with
a
lot
of
Studios
games
that
had
run
into
either
cost
or
scalability
issues,
or
even
things
that
it
was
a
game
that
maybe
had
let's
say
a
million
users
on
the
web
2
world,
and
they
were
really
concerned
about.
How
can
they
actually.
B
A
You
know
with
asset
classes
like
gold,
where
you
don't
need
a
lot
of
transactions,
maybe
not
necessarily,
but
something
that's
really
high
throughput
trade,
Finance
or
invoice
financing.
You
certainly
need
that
speed
so
that
when
I
was
thinking
about
this,
certainly
it's
use.
Cases
like
that
and
I
would
invite
you
know
D5
protocols
games
to
come
test
this
out.
Let's
see
what's
possible,
you.
B
A
Yes,
yeah
and
I
guess
just
sticking
with
performance.
It
leads
me
into
the
next
question
and
that's
I,
guess
benchmarking
or
performance
features
in
in
comparison,
so
I'm,
assuming
you
guys,
have
run
some
tests.
I've
seen
some
stuff
out
there.
How
are
the
numbers
looking
or
talk
to
us
a
little
about
that
I.
B
B
The
presentation,
but
basically
so
we
ran
some
tests
which
measured
the
speed
of
swaps
per
second,
which
is
the
same
methodology
as
a
company
called
dragonfly.
Research
did
for
a
variety
of
other
chains,
it's
actually
quite
known
and
standard,
and
that
paints
the
swaps
per
second
metric
paints
a
better
picture
of
reality
than
just
token
transfers,
which
are
often
the
most
performant
transactions
on
a
network,
but
not
necessarily
the
most
frequently
done
so.
B
The
results
of
that
was
the
EOS
evm
hit
814
swaps
per
second,
whereas
the
closest
competitor
which
was
Solana
came
in
at
273..
Polygon
was
at
47
avax
at
31
and
I.
Think
ethereum
was
at
nine,
so
this
provided
us
data
to
like
back
up
the
claims
that
this
is,
if
not
one
of
the
most
performant
EOS
or
evm
in
existence.
C
C
B
True
from
my
understanding
of
all
other
EVMS,
at
least
the
ones
that
I
play
with,
they
do
have
some
small
differences.
We
are
missing
some
elements
like
websocket
and
graphql,
which
will
open
the
door
to
many
more
applications
being
able
to
be
migrated
over
to
the
CVM.
So
we
have
some
ways
to
open
those
doors
in
the
near
future.
There
are
also
other
peripherals
as
well,
which
we
were
identifying,
based
on
developer
and
user
feedback,
we're
taking
stock
of
that
with
what
we'd
lack
to
make
sure
that
we
provide
better
experiences
than
other
EVMS.
C
B
A
B
B
A
And
yeah
also
I'll
give
everybody
a
call
to
action
to
join
one
of
the
the
weekly
Fireside
Chats
as
well,
which
which
enf
runs,
and
that
always
gives
a
good
insight
into
what's
happening,
plus
the
Discord
channels,
as
well
too,
so
so
be
sure
to
do
that.
But
on
the
performance,
that's
really
impressive,
Nathan.
So
if
I
can
quick
math,
it's
almost
100
times
100
times
quicker
in
terms
of
swaps
per
second
than
ethereum
and
almost
three
times
faster
than
Solana
right.
So
if.
C
Well,
I,
as
I
was
mentioning
before
at
the
at
the
beginning
of
the
project.
The
the
the
idea
that
we
had
was
to
use
the
EOS
token
the
native
use
token
for
to
to
pay
for
transactions.
Then
we
were
playing
around
the
idea
of
having
like
multiple
tokens
to
to
to
use
as
as
the
gas
token,
but
we
we
ran
to
a
limitation
of
wallets,
which
they
only
use
the
native
token
of
the
platform.
B
C
At
the
end
of
the
time
we
we,
the
the
enf,
decided
to
go
the
the
native
years
route
and
and
well
that,
for
me,
is
again
it's
the
right
decision.
I'm
I'm,
it's
like
yes,
it's
the
right
decision
me
because
it
will
make
them
the
demand
for
the
EOS
token,
like
you,
can
think
of
the
evm,
the
evm
platform
as
the
new
dap
on
top
of
fields
right,
a
popular,
a
popular
tab.
C
So
every
traffic
that
you
get
into
that
into
that
execution
environment
will
demand
the
EOS,
so
that
will
will
result
in
in
some
demand
some
extra
demand
for
and
also
you
have,
the
possibility.
The
enf
is
running
a
minor
so
that
you
have
the
possibility
to
burn
some
tokens
like
the
the
ones
that
you
have
been
collecting
as
as
the
fees,
so
it
open
UPS
a
lot
of
possibilities
and
I
think
that
it's
it's
for
me
that
I'm
happy
to
have
the
database
token
as
a
as
a
transaction
token.
B
So
we've
also
opened
up
not
only
new
utilities
but
new
earning
mechanisms.
So
there's
there's
a
couple
different
ways
to
look
at
that.
So,
like
Matia
said
we're
also
running
a
minor
and
that
that
burn
is
kind
of
important
to
us
as
well,
because
many
other
chains
in
the
industry
have
introduced
deflationary
models
and
we've
seen
this.
You
know
people
really
care
about
this.
B
B
A
A
No,
that's
a
good
point
and
I
mean
when
we
were
doing
the
the
Roadshow.
Last
year
we
were
in
in
Dubai
and
web
Summit
Etc,
and
at
this
point
there
was
still
talk
of
having
that
second
token
or
new
token
and
right
to
be
honest,
it
did
cause
a
little
bit
of
confusion
like
when
we
were
talking
to
some
potential
members
of
the
community
or
people
who
knew
EOS
from
from.
A
B
Thank
you
for
I
think
there
is
one
last
there's
one
last
part
there.
So
the
project
itself.
How
does
this
like
impact
the
project?
What
are
the
implications
of
that
so
for
the
project?
There's
a
lot
of
benefits
to
this
decision
right,
so
the
EOS
token
is
on
basically
every
Exchange
in
existence
right.
So
you
don't.
We
don't
have
to
worry
about
the
network
and
the
projects
having
to
wait
for
that
new
evm
token
to
be
on
some
exchange,
so
there's
some
liquidity
and
the
ability
for
people
to
purchase
into
it.
B
It's
also
on
other
things
like
what
are
they
called
moonpay,
so
you
can
instantly
buy
the
EOS
evm
token
with
like
a
credit
card,
so
we
have
immediate
on
on-ramp,
tooling
and
I.
Think
that's
really
important
for
these
projects
to
be
able
to
migrate
over
and
instantly
have
availability
for
their
for
their
applications
in
terms
of
gas
fees
and
just
onboarding
of
users.
Yes,.
A
Oh
well
said
well
said:
I
really
appreciate
it
guys.
As
I
said
we
I
know,
we've
touched
on
it
a
couple
times,
but
it's
nice
to
be
able
to
dive
into
it
a
little
bit
and
another
thing
that
we
mentioned
a
couple
times
which
is
coming
soon,
but
that's
that
instant
finality
and
and
I
did
want
to
talk
about
the
the
impact
of
that
or
what.
How
will
that
impact?
The
evm
and
Matthias
I?
Think
you
were.
You
were
touching
on
a
little
bit
earlier
on.
C
Yes,
well,
as
we
were
saying
before
any
Improvement
on
the
base
layer
of
EOS,
that
will
impact
the
ABM
directly
so
because,
as
when
Nathan
was
explaining
how
how
the
transaction
flow
Works
every
ebm
transaction
is
wrapped
around
an
EOS
transaction.
So
basically,
you
end
up
running
an
es
transaction
that
execute
on
the
ABM
smart
contract,
and
so
by
the
time
you
we
get
instant
finality,
you
will
get
instant
ebm
finality
it's
a
TBM
transaction
finality.
C
So
that's
a
really
good
value
proposition,
even
if
EOS
has
like
we
can
say
like
one
second
finality
probabilistic
probabilistic
finality
Because
by
the
time
it
gets
into
a
block
the
probability
that
it
get
forked
or
or
that
you
need
to
to
resend.
The
transaction
is
pretty
low,
but
you
will
get
that
level
of
certainty
by
protocol.
C
C
Well,
as
we
we
said,
the
ebm
is
a
contract
inside
EOS,
so
in
the
NEOS
happens
to
have
0.500
millisecond
blocks
right.
So
at
the
very
beginning
of
the
of
the
design
decisions
on
the
ebm,
we
were
thinking
about.
Okay,
maybe
we
can
have
a
ratio
between
x
amount
of
EOS
blocks
are
one
ebm
block,
so
in
the
early
testing
we
were
doing
like
10
blocks,
onions,
one
block
on
the
VM.
C
So
basically
we
were
having
five
seconds
five
seconds
CBN
blocks,
but
then
we
starting
to
depart
from
that
from
that
idea
of
having
a
a
specific
relationship
between
the
amount
of
years
block
chamber
related
to
the
ABM
block
number
and-
and
we
started
thinking
about
time
right.
So
we
because
I,
don't
I'm,
not
saying
that
this
will
happen
in
the
future.
But
if,
for
some
reason
the
U.S
Network
decides
to
go
lower,
500
milliseconds
like
250
well,
that
will
increase
the
frequency
of
the
evm.
C
If
we
have
it,
that's
trigger
that
constant
relationship
between
blocks,
so
we
depart
from
that
and
said:
okay,
let's
trust,
let's
trust
time
and
by
the
time
we
decide
to
go
for
for
time.
Well,
we
have
the
option.
Since
they're
at
the
lane
layer
has
sub
second
blocks.
We
can
go
that
way
also
and
have
a
sub
second
blocks
on
the
ebm.
C
Second
is
not
that
much
because
you
have
all
the
throughput
of
the
network
like
in
that
one
second
ebm
block:
you
have
all
the
throughput
of
the
two
blocks
on
the
ebm
on
the
radio
side,
so
you
are
not
losing
any
throughput,
so
you
will
say:
okay,
but
the
the
latency
is
increasing
Because.
By
the
time
you
make
a
state,
a
change
in
the
state
of
DVM.
You
will
have
to
weigh
500
more
milliseconds.
C
B
B
I
think
it's
even
so
I
I
like
front
end.
That's
my
that's!
My
like
toolkit
right,
I'm,
a
full
stack
developer,
but
I
prefer
front-end
and
I
heard
this
initially
and
I
was
like
the
heck.
Does
this
matter
because
as
a
front-end?
Okay,
let's,
let's
take
this
back
20
years
ago,
the
internet
was
slow.
So
the
expectation
of
people
was
that
you
click
a
button
and
nothing
happens
for
a
while
yeah
right.
But
that's
not
true
anymore,
because
the
internet
is
fast.
B
So
we,
the
developers,
have
accustomed
ourselves
to
our
end
users
like
what
they
expect
their
expectations
and
the
second
that
you
click
a
button.
If
there
is
a
response,
that's
over
50,
milliseconds,
you're,
adding
a
loader
or
a
spinner
or
something
to
it,
because
you
want
people
to
be
able
to
understand
that
feedback.
B
Yes,
so
what's
the
actual
difference
here,
there's
500
milliseconds,
which
Network
time
so
the
return
trip
time
of
that
is
probably
like
700
milliseconds,
and
then
you
have
a
thousand
milliseconds
which
will
turn
that
into
a
thousand
two
hundred
milliseconds.
So
the
difference
between
700
milliseconds
and
1
200
milliseconds
you're
not
going
to
notice
that
you'd
notice
if
it
was
like
the
difference
between
50
milliseconds
and
300
milliseconds.
C
B
Okay,
let's
now
now
that
we
know
that,
let's
put
that
aside,
if
you're
doing
any
of
that
stuff,
you're-
probably
a
bad
front-end
developer
anyway,
because
what
you
really
want
to
do
is
you
want
to
unblock
the
user
instantly?
You
go.
It's
like
AWS
right.
If
I
go
and
provision
a
server
for
myself,
I
don't
sit
around
there
for
five
minutes
waiting
for
my
server
to
be
provisioned.
It
says:
okay,
well,
go!
B
Do
something
else,
we're
going
to
provision
your
server
and
when
it's
ready
we'll
let
you
know-
and
that's
that's
really-
the
best
kind
of
flow
for
any
kind
of
web3
application.
That's
what
we
should
be
leaning
on
is
that
fire
and
forget
and
then
come
back
with
a
resolution
later.
If
it
fails,
you
still
have
that
transaction
ready
to
reprocess.
You
have
all
of
the
information
required
for
it,
so
it's
not
like
you're
losing
State.
You
just
have
to
re-push
that.
A
B
C
B
The
block
Cadence
is
different
than
the
ethereum
specifications
block
Cadence
that
messes
with
their
contracts
it
potentially
messes
with
their
tooling
and
I.
Think
that's
really
the
decision.
The
best
part
about
the
decision
that
was
made
that
it's
never
going
to
interfere
with
any
of
that
stuff.
Sure.
A
No
excellent
excellent!
That's
thank
you.
Thank
you
very
much
for
touching
on
that
I
do
see.
We
have
a
lot
of
interactions
with
the
polls
which
is
which
is
great.
They
have
I,
have
opened
up
a
new
question
about
challenges
or
perceived
challenges
from
the
audience.
What
do
they
think
will
be
the
the
biggest
challenge
in
transitioning
their
ethereum
adapts
to
to
evm?
So
please
get
involved
in
that.
It's
great
to
see.
A
The
interactions
coming
in
I
do
have
kind
of
a
final
kind
of
a
fun
type
question,
but
with
all
of
the
I
guess,
hype
around
AI
tools,
if
you
want
to
call
them
Ali
I
know
that
that's
another,
that's
another
conversation,
but
the
necessity
of
evm
now
chat.
Gpt
does
have
a
solidity.
The
C
plus
plus
writing
capability,
I
I
heard
some
crazy
statistics,
like
50
of
all
new
code
going
on
GitHub
was
written
by
AI
like
yeah
talk
to
me
a
little
bit
about
this
crazy
world.
That's
a.
B
B
It's
kind
of
like
code,
incest
right
if
you
have
this
code,
which
is
only
learning
from
the
own,
its
own
code,
that
it's
written
without
a
developer
actually
going
through
and
be
like.
Oh
that's
wrong!
Then
it's
reiterating
on
the
fact
that
that
was
code
that
it
can
then
learn
from
and
then
give
back
to
another
developer.
It
does
it
goes
to
that
cycle
again.
It
like
deep
learns
itself
through
that
bad
code.
That's
a
scary
thought
that
you
just
brought
up
so
I
hope.
That's
not
true!
That
at.
A
A
B
B
B
C
But
anyway,
like
stressing
the
question
there
like,
let's
think
that
you
have
a
perfect
mapping
between
solidity
and
C
plus
plus,
and
it
also
supports
the
unique
test
for
the
contract.
Etc.
That's
only
part
of
the
things,
because
you
also
have
some
back-ends
and
also
have
some
indexers
and
some
you
have
a
lot
of
stuff
surrounding
the
your
your
your
your
dab
deployment.
C
So
that's
only
one
of
the
one
part
of
the
of
of
the
stack,
and
so
even
if
you
have
a
perfect
map,
translation
between
solidity
to
C,
plus
plus
there's
a
lot
of
things
that
you
will
also
will
have
to
translate
and
I.
Don't
at
this
point,
I.
Don't
think
that
maybe
I
will
regret
this
five
years.
But
no
at
this.
B
How
does
this
stuff
work?
It
knows
outputs
based
on
previous
inputs
inputs
right.
That's
that's
just
how
AI
works
so
you're
if
you're
doing
anything
novel.
Basically,
you
have
to
know
what
you're
doing
or
you're
going
to
miss
something,
and
it's
it's
kind
of
like
it's
going
to
be
bad.
It's
gonna
be
bad
bro
and.
C
And
also
the
translation
of
them.
We
are
talking
about
language
here,
like
from
soliti
to
C,
plus
plus,
but
then,
when
you
translate
to
Solita
from
C
plus
plus
well,
you
will
basically
try
to
run
a
dab
that
was
thought
to
be
running
on
ebm
on
top
of
EOS,
and
maybe
the
capabilities
are
not
the
same.
Maybe
you
are
trying
you.
You
need
something
that
the
ABM
platform
provides,
that
it
doesn't
exist
on
NEOS
or
all
the
way
around
also
so
it's.
C
B
It's
probably
another
really
big
thing
here,
which
is
just
you,
wouldn't
open
the
door
to
tooling
right.
So
if
there
was
no
evm-
and
you
were
just
you
know-
rewriting
your
your
stuff
to
solidity-
to
C,
plus
plus
from
solidity-
you
wouldn't
be
able
to
use
metamask.
You
would
then
have
to
rewrite
your
back
end.
Like
you
said
right,
you
wouldn't
be
able
to
use
all
of
the
hard
hat
and
and
Etc
you'd.
A
C
A
A
Absolutely
and
look:
we
will
be
actually
we're
planning
to
do
some
some
sessions
on
this
going
forward
as
well.
So
just
talking
about
the
potential
implications
of
AI
into
web3
and
what
that
might
mean
so
we'll
yeah,
we'll
we'll
get
working
I
do
appreciate
it
guys,
as
I
said,
a
fun
question,
but
I
just
wanted
to
get
here,
get
your
take
on
it.
C
A
A
A
B
A
As
the
guys
had
said
earlier
on,
this
is
open
source
right,
so
people
can
take
it
and
build
it
and
utilize
it
from
there.
But
this
particular
ELC
VM
is
built
and
is
going
to
be
maintained
for
the
EOS
Network.
But
again
it's
it's
open
source
code,
so
you
can
take
it,
deploy
it
and
other
chains.
For
example,
at.
C
A
A
A
C
When
we
are
talking
about
transaction
finality
that
it's
one
of
the
efforts
that
the
NF
is
working
on,
we
are
talking
about
protocol
finality
that
the
transaction
can't
be
reverted.
So,
basically,
if
the
transaction
is
finalized,
it
can't
be
enough
for
a
later
time.
So
it's
final,
the
the
the
the
the
state
modifications
that
that
transaction
made
remains
there
in
the
canonical
chain
on.
B
C
It
will
reduce
the
amount
of
that
default
is
possible
right.
Yes,
yes,
yes,
sure
sure.
So,
basically
you
would
when
new
transaction
is
final,
it's
not
possible
for
that
transaction
to
be
reverted.
Is
it
final
by
protocol?
Yes,
I
already
have
that,
like
you,
have
the
Lefty
reversible
block?
Yes,
which
means
that
any
transaction
that
is
behind
that
block
is
not
possible
to
be
reverted.
That
finality
time
is
like
it's
more
than
two
minutes
for
now,
but.
C
A
I
hope
that
answers
your
question.
You
did
have
a
follow-up
saying
that
you
think
the
main
challenges
will
be
adapting
to
the
adapting
the
tooling
for
backend,
so
smart
contracts
and
testing
and
front
end
and
also
having
the
financial
interest
to
do
it
because
the
EOS
price
hasn't
been
inviting.
But
you
do
leave
a
nice
note
here
to
say
the
community
is
the
strong
point,
since
it's
full
of
this
OG
energy
make
the
Earth
again
I
love
it
absolutely
love
it,
and
so
thank
you
for
that.
Ricardo
I
really
appreciate
it.
A
C
Yeah
sure,
if
you
take
the
evm
code,
that
is
open
source
as
Nathan
was
saying,
there's
a
configuration
setting,
which
is
now
relies
on
a
table
that
you
can
put
whatever
gas
price
you
want
there
like.
If
you
want
to
process
free
transaction,
no
gas,
you
can
do
it
well,
you
will
be
responsible
for
paying
that
resource
on
the
for
the
underlying
chain.
But
yes,
of
course
you
can.
You
can
make
that
number
zero,
which.
B
Is
interesting
because
the
ethereum
network
is
actually
trying
to
work
on
something
like
this,
not
specifically
this,
but
the
account
abstraction
EIP,
which
is
trying
to
go
a
different
route
for
that.
So
this
evm
already
has
the
capability
of
doing
something
that
is
only
being
worked
on
on
other
EVS,
which
I
think
is
really
interesting.
Oh.
A
Nice,
that's
cool,
excellent,
so
Lauren.
Thank
you
so
much
for
the
question.
I
hope,
I,
hope
that
was
answered
for
you
and
we
do
still
have
some
interactions
coming
in,
which
is
which
is
great.
44
of
the
people
have
said,
they're
very
likely
to
adopt
or
use
the
EOC
VM
for
for
their
dapps,
which
is
awesome,
I
think
that's
great
and
we
did
have
on
on
the
challenges.
38
of
people
were
saying
that
one
of
their
biggest
challenges
in
transitioning
would
be
learning
EOS,
specific
development
skills.
A
C
There
yeah
no,
no,
that
was
one
of
the
the
driving
decisions.
Therefore,
the
person
that
people
don't
need
to
understand
anything
about
years
and
URL,
where
they
have
to
point
their
metamask
or
their
development
tooling,
and
that's
it
and
the
address
of
the
block
Explorer
and
a
way
to
launch
their
own
node,
but
basically
EOS
is
transparent
for
them.
And,
yes,
it's
absolutely.
B
A
And
I
think
the
other
40
is
basically
people
saying
they
want
understanding
the
differences
between
ELC,
VM
and
other
evm
implementations,
and
what
I
would
say
is
again
I'd
invite
people
to
come
in
and
test
right,
go
in
see
what
you
can
do
see
what
you
like.
Please
give
feedback
on
the
channels
which
Nathan
talked
about
earlier
on
and
again,
as
we
said,
move
fast
and
break
things.
Let's
do
it.
A
Okay,
that's
good
to
hear
and,
as
I
said
from
from
the
beginning,
this
is
something
that
was
badly
needed,
sorely
needed
now.
It's
here,
I
hope
we
can.
You
know
Circle
back.
We
at
Zion
will
certainly
be
circling
back
to
a
lot
of
projects
we
spoke
to
over
the
years
to
say
you
know
come
on
down.
Please
try
this
as
I
mentioned.
D5
projects
I'm
involved
with
also
will
be
coming
in
to
try
to
test
this.
So
now
this
this
is
really
exciting
and
I'm
yeah
super
happy.
A
You
guys
could
could
join
us
as
we
move
to
some
kind
of
closing
remarks.
I
guess
you
know
key
takeaways.
Here
is
guys.
As
we
said,
we
want
people
on
here
using
it
testing
it
providing
feedback
that
is
is
so
key.
I
did
just
want
to
ask
a
question.
So
let's
Blue
Sky
it
here.
If
you
are
a
developer,
specifically
looking
to
explore
the
evm
where,
where
would
you
begin?
What's
what's
step?
One?
Oh.
B
B
So
if,
if
here's
the
wonderful
thing
about
this
there's
a
plethora,
there's
just
a
large
amount
of
educational
material
for
evm
development,
and
now
all
of
that
stuff
applies
to
EOS,
which
is
it's
it's
harder
to
find
a
non-evm
chain
than
to
find
an
EVN
chain,
and
we've
now
joined
those
ranks.
So
all
of
that
educational
material
that
was
available
for
everybody
else
is
now
also
available
for
us.
So
if
you
want
to
develop
specifically
on
the
EOS
Network
docs.usnetwork.com,
you
have
all
your
migration
guides.
B
A
Like
to
hear
it
because
Donna
is
where
people
should
be
building
in
silos,
I
think
you
know
the
the
CEO
of
the
enf
eve.
He
said
it
quite
well.
The
future
is
multi-chain
right
and,
and
we
have
to
have
these
tools
available.
Of
course,
we
didn't
even
touch
on,
say
things
like
IBC
see,
but
having
these
things
available
are
just
so
important
for
adoption
and
if
we
could
I'm
really
hoping
start
to
abstract
away
a
lot
of
this
technical
complexity,
move
it
to
the
back
end
where
it's
supposed
to
live.
A
A
Really
appreciate
it
guys,
it's
a
really
great
energy.
As
I
said,
please
check
out
everything.
Enf
have
been
doing
check
out
the
docs.
Please
come
in
and
try
to
test
things
if
there
are
any
teams
that
would
like
some
consulting
or
support,
please
reach
out
to
zyzen
we've
got
a
great
team,
can
help
you
guys
get
started,
but
look
as
Ricardo
said:
there's
an
awesome
Community
there.
There
are
a
lot
of
ogs.
Some
of
them
are
coming
back,
which
is
always
great
to
see.
A
So
please
yeah
keep
into
the
the
developments
as
they
come.
I
did
want
to
thank
you
guys
so
much
for
joining
me.
I'm
sure
this
is
not
going
to
be
the
last
ledge
video
which
will
feature
some
of
our
friends
from
enf,
so
Nathan
Matthias.
Thank
you
very
much
excellent.
Thank
you
guys
and
we
will
see
you
on
the
next
one.