►
From YouTube: NEAR EVM Working Group Update [2021-02-12]
Description
Follow the latest from NEAR Protocol on,
Website: https://nearprotocol.com/
Discord: https://near.ai/discord
Medium: https://near.ai/medium
Twitter: https://near.ai/twitter
GitHub: https://near.ai/github
#WhiteboardSeries #Blockchain #FutureIsNEAR
B
C
B
B
Okay,
so
the
current
goal
we
are
working
towards
this
remains
the
destiny
released
by
the
end
of
q1
and,
more
specifically,
we
are
working
looking
through
the
architectural
changes
we
decided
on
on
in
the
previous
weeks
and
a
little
bit
upset
to
the
roadmap,
but
can
still
be
accommodated
and
we
are
preparing
the
protocol
upgrade
and
bug
bounty
this
week.
This
week's
updates
alex.
Why
don't
you
begin.
A
Yeah
sure
so
from
my
from
my
side,
not
a
lot
of
the
updates.
On
the
evm
side,
we
were
working
together
with
you
on
the
on
the
project
aurora
code
name,
so
this
is
like
when
it
was
requiring
a
bit
of
thinking
and
time
yeah
and
probably
that's
it.
So
I
I
spent
the
majority
of
this
week
on
on
on
the
bridge.
B
B
So,
hopefully
it's
going
to
move
forward
and
I
joined
the
contract
runtime
meeting
this
week
to
discuss
the
performance
questions
really
had
raced.
That
might
be
another
discussion
and
then,
as
as
with
alex,
we
are
working
on
rebranding,
ebm
and
bridge
under
under
a
single
name
and
something
better
than
an
acronyms
look
like
near
evm.
B
D
C
Okay,
so
to
give
you
the
background,
we
are
I'm
building
a
stress,
testing
tool
for
the
evm
called
the
evm
bully,
and
I
started
working
on
that.
So
I
set
up
a
server.
We
can
use
to
stress
test
evm,
I
synced
all
the
test
nets
and
then
I
started
implementing
the
evm
bully
tool
which
is
written
in
go
so
we
can
leverage
the
go
ethereum
code
base
and
what
we
have
so
far
is
basically
the
ability
to
read
to
read
the
blocks
from
ethereum
database.
B
C
E
D
E
Went
through
a
few
of
the
tutorials
read
a
few:
the
research
documentation.
Sorry,
I'm
going
too
quickly.
I
just
realized
you're
writing
this
out.
Yep
read
tutorials,
not
all
of
them
yet,
but
the
ones
to
do
the
first
couple
ones
documentation
some
of
the
research
documents
that
were
that
are
hosted
up
on
the
website
and
that's
about
that's
about
it
right
now,
just
going
through
those
documents
and
getting
caught
up
and
everything.
F
B
B
E
Of
course,
ethereum
came
out
as
proof
of
work,
but
yeah
did
that
for
the
first
year
then
worked
on
a
couple
other
projects,
notably
the
last
four
years.
We
did
a
mining
project
collaboration
with
the
few
different
companies
and
it
was
more
so
to
get
mining
done
in
in
very
remote
regions
and
that
we
did
really
well.
E
It
was
really
really
fun
project
to
do,
but
as
mining
has
gotten
so
intense
now,
we've
backed
out
of
that,
and
I
I
parted
ways
with
with
that
with
that
company
now
so
yeah.
I'm
I'm
glad
that
I
that
I
found
near
and
I'm
glad
to
be
here
and
I'm
glad
to
be
back
in
the
proof
of
stake
realm,
because
it's
definitely
a
technology
that
I've
always
thought
would
be
absolutely
like
a
protocol
to
actually
outlast
and
yeah.
It's
cool
cool
to
be
here.
E
E
The
guy
came
over
and
somehow
recognized
me
like
it's
so
rare
that
someone
recognized
me,
but
this
guy
of
all
people
recognized
me.
So
I
got
some
pictures
that
I
could
actually
show
you
guys
and
be
siding
one
of
the
plates
and
putting
it
up
on
the
wall
but
yeah.
It
says
one
of
the
godfathers
of
purpose
steak
on
it.
So
oh
yeah,
I
I.
B
E
Yeah,
yes,
I
used
to
be
well
connected
with
the
with
the
chinese
side,
but
that's
kind
of
dwindled
off
but
yeah.
I
spoken
at
huawei
events
and
and
okay
coin
events,
and
I
know
a
lot
of
a
lot
of
the
guys
down
there
in
singapore,
too
and
I'll
know
a
lot
of
guys.
But
korea,
that's
always
been
like
it's.
We
call
it
like
a
self-contained
kind
of
kind
of
market.
It's
always
difficult
to
to
really
get
in
on,
but
yeah.
B
B
So
I'm
working
on
upgrading
the
contract
to
the
latest
sputnik
vm,
because
the
the
errors
I
will
run
was
running
into.
I
believe
they
are
just
incidental
bugs
some
of
them.
I
think
the
the
vm
wasn't
really
ready
to
go
in
in
all
regards
there's
been
a
lot
of
development
since
then,
and
we
need
a
new
upstream
version.
B
B
Okay
and
yes,
let's
talk
about
the
most
important,
then
topic
here,
ndp
141
so
specifically
now
nfp
141,
despite
what
we
discussed
on
the
last
call
as
in
to
give
background
on
the
last
call,
we
had
backed
off
from
nap
141
because
there
was
a
concern
that
it
wasn't
actually
ready
to
go
as
in
immediately
usable
implementable,
alex.
Have
you
had
a
chance
to
to
review
eugene's
comments
in
that
regard?.
A
A
A
A
So
literally
literally,
we
have
so
how
it
works
in.
In
the
fungible
token,
connector
we
have
a
factory
account,
which
is
this.
This
is
a
contract.
This
is
like
complicated
contract
and
this
contract.
It
just
deploys
some
ordinary
nap21
tokens,
and
these
tokens
are
extended
with
some
additional
functionality
and
the
additional
functionalities
is
the
withdraw
method
that
enables
people
to
withdraw
the
funds
to
ethereum.
A
So
something
like
this
can
be
done
also
with
with
f
connector.
So
what
we
are
going
to
have
is
just
an
extension
to
the
to
the
reference
implementation
with
some
additional
functions
and
in
terms
of
the
the
connector
itself,
the
logic
of
the
connector.
It
will
not
be
like
highly
dependent
on
this
yeah,
so
so
the
standard
once
again
yeah
drawing
the
line
here.
The
standard
is
there,
minor
changes
are
going
to
be
there
that
are
just
connected
with
the
reference,
implementation
and
testing
of
this.
B
A
A
So
we
have
simplified
and
yeah,
and
the
major
problem
with
this
is
that
these
these
methods
increase
in
storage
on
your
side
and
on
here
in
order
to
keep
up
with
with
this,
you
need
to
stake
near
tokens,
so
they
account
that
increased
storage
needs
to
have
enough
near
tokens
on
its
balance.
So
literally,
we
would
confuse
users
if
we
would
use
this
model,
because
we
would
ask
users
to
pay
if
they
are
doing
the
transaction
with
nap21.
A
B
A
A
The
problem
of
this
approach
is
when
skating,
so
in
some
some
point
in
time.
In
a
year
from
now
when
we
would
like
to
deploy
additional
evms
or
somebody
would
like
to
deploy
additional
evms,
he
will
not
be
able
to
so.
He
will
encounter
the
problem
of
the
of
the
accounts
of
the
of
the
different
balances
of
f
in
different
evms
yeah.
So
so
that's
that's
the
only
problem
here.
B
Yeah,
I'm
leaning
that
way
too.
I
think
we
do
want
to
concentrate
the
network
effects
on
our
on
on
the
let's
call
it
the
default
evm
deployment
and
people
people
who
deploy
their
own
evm.
They
are
opting
out
of
those
network
effects
for
whatever
reasons
they
may
have,
but
those
reasons
could
include
at
the
best
of
them,
so
if
that
can
be
in
some
sense,
parameter
reliable
for
them
that
that
will
be
fine
alex.
What
do
you
think.
A
A
Unfortunately,
we
are
like
not
doing
the
separation
of
concerns
in
between
different
smart
contracts
here,
so
we
are
not
splitting
it.
It
would
be
so
we
will
have
a
bigger
single,
bigger,
smart
contract,
but
I
think
that
it
is
okay
at
the
moment.
So
I
I
do
not
see
any
major
concerns
and
I
believe
it
might
be
a
bit
a
bit
easier
in
the
development
at
the
moment.
So,
let's
ship
it
faster
and
yeah,
let's
do
it
as
a
simple
contract.
Well,.
B
F
B
B
B
F
D
B
A
Okay
from
this
from
this
part-
yes,
but
also
we
need
to-
we
need
to
in
a
specific
way,
create
the
execution
outcomes.
So
we
we
need
to
have.
We
already
have
a
withdraw
and
deposit
methods
in
in
the
evm
smart
contract.
This
was
previously
used
to
do
withdrawing
and
deposit
in
near.
So
now
we
need
to
rewrite
this
code,
and
we
need
this
thing
not
to
not
to
deposit
stuff
but
withdraw.
It
needs
to
specif
in
a
special
way
construct
the
the
receipts
and
the
well
the
execution
outcomes.
A
So
these
receipts
can
be
checked
on
the
ethereum
site,
for
unlocking,
f
and
deposit
needs
to
need
needs
to
be
rewritten
and
to
the
deposit.
We
need
to
pass
a
proof
of
the
effect
of
locking
on
the
ethereum
site,
so
it
is,
it
is
not
going
to
be
any
near
attached
to
it,
it's
just
it's
just
the
proof
and
and
somewhere
in
the
evm.
We
would
need
to
also
to
have
a
link
to
the
to
the
bridge
to
the
current
bridge
deployment.
F
Yeah,
so
I
I
would
suggest
we,
while
on
this
also
add
like
some
kind
of
owner
account
or
somebody
who
can
pretty
much
like
upgrade
and
change
the
like
parameters
in
this
case.
What
is
the
bridge
like?
Where
is
the
bridge
prover,
and
so
then
yeah
like
so
right
now?
Actually
in
the
new
contract,
there's
no
deposit
resources,
they
need
to
be
written
but
yeah,
no,
their
their
function.
Signature
will
change
as
alex
ochenko
just
suggested,
but
yeah.
B
A
A
There
is
like
a
plan
how
to
do
this,
and
everything
starts
with
a
very
simple
upgrade
ability,
which
is
the
proof
of
authority
or
credibility
where
we
are
just
saying
that
hey
on
the
on
the
on
the
near
side
like
everything
we
we
can
just
we
just
keep
in
our
hands
the
full
access
key
again.
We
can
redeploy
it
in
order
just
so
it's
it's
absolutely
well.
So
this
is
the
beginning
of
all
of
the
stuff
and
especially
like
we
can.
A
We
can
change
it
over
time
at
the
moment
when
we
will
be
closer
to
the
maintenance.
No
problem
with
this,
however,
the
idiot's
suggestion
for
for
the
ethereum
side
of
the
smart
contract,
because
obviously
ethereum
connector
also
needs
to
to
be
pointing
to
to
the
near
client
and
near
prover
yeah,
and
this.
A
This
is
something
that
we
need
to
pass
on
the
init
function
or
like
in
the
constructor,
but
it
will
be
a
good
thing
to
have
this
update
and
updating
updating
methods
and
actually,
for
the
fungible
token
contractor
fundable
token
connector.
At
the
moment,
there
is
no
these
update
methods
and
we
we
encountered
the
problem
with
the
robson
deployments,
and
then
we
actually
just
created
an
issue
during
this
week.
For
for
heaven
for
adding
these
functions
there
and
yeah-
I
mean
all
of
this
stuff
with
the
owner
yeah.
F
Yeah,
I
think
the
simplest
thing
is
just
yeah:
have
an
owner
account
and
then
that
owner
account
is
allowed
to
hit
some
method
which
is
like
config
or
set
config
or
whatever,
which
yeah
like
is
instead
of
these
parameters
like
which,
what
is
the
account
for
that?
What
is
the
account
for
that?
What
is.
A
Whatever
yeah
yeah
the
the
only
difference
with
that
in
near
we
have
more
so
we
literally
have
already
the
proxy
there,
because
we
are
able
to
upload
to
the
same
account
the
different
codes.
So
we
do
not
need
to
take.
We
don't
need
to
think
about
this,
and
that's
it
it's
not.
It
is
not
there
by
default
in
ethereum.
B
A
D
D
Okay,
I
I'm
also
like
trying
to
to
make
the
upgradability
process
smoother,
and
I
also
took
a
look
at
the
upgradability
plan
that
was
created
by
alex
it's
not
yet
published.
As
far
as
I
know,
and
I'm
for
my
approach
of
upgradability,
I'm
trying
to
follow
like
the
unstructured
storage
path
of
upgrading
the
smart
contracts.
B
F
F
There's
like
a
huge
discussion
there,
but
there's
actually
supposed
to
be
the
actual
like
it
should
it's
it's
a
commit
into
the
nomicon,
it's
106.,
okay,
yeah
yeah,
so
so
yeah.
If
we
can
add
just
like
yeah
list
of
these
methods
like
the
ones
we
already
have
for
evm
the
12500
token,
the
ones
with
the
bridge
and
ones
for
like
upgradability
ownership
configuration
just
so
we
have
like
and
and
like
what
they
do.
This
first
of
all
will
be
great
documentation,
but
second
yeah.
B
Yeah,
that's
good.
I
will.
I
will
take
that
on
and
next
next
week,
as
as,
hopefully
we
get
the
balance
of
test
fixed,
we
have
a
good
idea
of
what
that
side
of
things
looks
like.
I
think
the
contract
interface
will
be
sufficient
and
and
then
we
will
work
with
eurogani
girl
on
our
credibility
and
handle
the
deposit
withdrawal
signatures
yeah.
I
think
we
can.
We
can
start
drafting
that
next
week
and
actually,
with
that
in
mind,
let
me
see
if
I
can
find
my
controls
here.
D
A
B
B
We
have
here
from
a
previous
meeting
the
outline
of
the
roadmap
for
the
evm.
Now
some
things,
of
course,
already
changed
as
in
we
are
not
going
for
an
open,
ethereum
upgrade.
In
any
case,
it
was
actually
a
badly
badly
boarded
item
which
should
have
said
berlin
hard
fork
support
instead
of
open,
ethereum
yeah.
But
if
you're
doing
some
detail
right
so
alex
also
actually
on
that
point,
yeah.
B
A
Yeah,
I'm
I
I
was-
I
unfortunately
wasn't
having
enough
time
this
week
to
do
this.
I
was,
I
was
put
doing
the
the
step-by-step
guide
for
for
the
breach,
and
I
was
preparing
the
upgradability
solution
for
the
bridge,
but
I'm
going
to
work
on
this
during
the
weekend
and
on
monday,
I
believe
we
are
going
to
post
it
there,
basically
the
things
that
we
are,
that
we
that
I
I
think
that
we
need
to
lay
out
there
is
to
is
to
convey
to
everybody.
A
What
is
our
decision
process
how
we
are
going
to
move
on
with
the
with
the
evm
upgrades?
We
need
to
say
to
everybody
that
this
is
going
to
be
a
protocol
upgrade
so
so,
for
example,
the
validators
they
they
need
to
be
aware
of
this.
So
this
is
the
beginning
of
the
conversation
of
what
community
would
like
to
have
in
front
of
them
before
we
are
actually
roll
out
this
upgrade.
So
this
is
this
is
what
we
were
like
putting
in
that
some
information
about
how
people
would
like
to
to
test
it.
A
What
types
of
functionality
they
would
like
to
have
by
that
moment,
so
yeah.
So
we're
just
I
I
I
I
would
like
to
to
do
this
pause,
the
408
so
yeah,
so
we
we
are
proposing
something
that
we
would
like
to
do
these
this,
and
that-
and
here
is
the
plan
for
it
for
the
rollout.
What
do
you
think-
and
you
have
one
month
for
for
thinking
about
this
and
proposing
some
alternatives
or
like
upgrades
to
this
stuff?
B
B
A
B
B
Yeah,
okay
and
yeah,
so
the
the
rest
of
the
near-term
objectives
here
or
the
milestones.
I
think
we
we
are
on
track
still
for
the
for
the
upgrade,
but
it's
it's
gonna
be
a
little
tight
because
the
spotlight
doesn't
have
berlin,
hard
fork
support
currently,
and
it
may
have
some
bugs.
We
need
to
fix.
Overall,
we
will
find
out
in
the
next
days
what
the
exact
situation
is.
B
For
this
right
now,
not
necessarily
not
necessarily,
I
mean,
after
all,
it's
not
activated
yeah,
but
of
course
we
have
it
on
the
roadmap,
so
we're
aiming
for
it.
So
the
the
balance
s
balances.
This
is
what
we
discussed
about
the
afghanistan
and
the
eth.
Connector
is
collaboration.
New
guinea
alexandrial
sounds,
like
frank,
is
on
track
to
complete
the
replayer
and
well.
Actually,
one
one
thing
that
you
had
mentioned
somewhere
alex
is
that
maybe
the
bug
bounty
timeline
is
is
gonna
have
to
change.
A
I
well
it
depends
on
what
we
are
going
to
put
in
there
and
and
and
what
what
tools
are
we
going
to?
What
tools
are
going
to
be
available
at
that
moment
in
time
with
with
the
with
the
evm?
If
we
would
be
able
to,
you
know,
give
people
an
ability
to
to
upload
the
contracts
there
and
and
and
do
the
stuff
on
the
betternet,
where
we
can
introduce
a
quick
hack
that
the
execution
is
we
were
discussing
this,
the
the
execution
is
not
consuming
any
well.
A
A
So
during
the
the
past
week
we
have
found
a
very
specific
and
not
easily
detectable
bug
on
bridge,
and
we
were
like
quick
fixing
it
and
like
just
just
like
I.
I
can
say
that,
well,
we
can
put
as
a
small
bug
bounties
there,
but
it's
not
it's
not
going
to
give
us
the
effect
that
we
would
like
to
get
yeah.
We
would
like
to
get
with
the
bug
bounties.
A
So
there
are
plenty
not
very
big
and
not
critical
bugs
so
like
some
some
things
there
and
we
still
can
fix
this
before,
like
the
the
big
guys
and
like
some,
some
great
people
are
going
to
come
and
hack
and
try
to
find
severe
vulnerabilities
there.
So
yeah
and-
and
this
is
like
this
is
at
the
moment-
this
is
only
in
my
head.
B
And,
given
that
we
should
keep
the
bug,
bounties
aligned
as
its
starting
dates,
aligned
already
for
organizational
reasons,
we
should
discuss
that
next
week,
yeah
yeah,
let's
do
it:
okay,
yeah
and
a
reminder.
The
road
mapping
visual
form
is
available
also
showing
the
dependencies
between
between
milestones,
okay,
so
there's
actually,
given
that
we
we
have
a
little
bit
more
more
time
than
I
thought
after
discussion.
I
will
mention
also
to
everybody
a
little
bit
about
the
contract
runtime.
I
think
that
I
did
so.
B
There
were
basically
a
few
few
issues
that
I
wanted
to
bring
up
on.
The
runtime
call
one
was
to
to
make
sure
that
the
team
was
aware
of
our
needs
from
them,
given
that
we
are
moving
back
to
to
a
hybrid
contract,
contract-based
approach,
architecture,
and
they
were,
they
were
happy
to
hear
from
us
and
are
happy
to
accommodate
us
in
this
regard.
B
It
is
specifically
working
on
the
performance
questions,
so
I
presented
the
two
two
items
that
we
would
like
addressed.
One
is
that
we
would
like
to
white
list
the
evm
in
such
a
way
that,
as
in
the
default
vm
contract,
that
it
will
always
be
retained
in
memory,
meaning
that
we
can
avoid
any
any
performance
impact
due
to
loading
the
contract-
and
this
was
this-
was
well
received
and
and
would
be
done
perhaps
as
early
as
next
week.
B
The
the
idea
is
that
there
will
be
a
pull
request
by
the
end
of
next
week.
The
other
other
item
was
that
the
evm
contract,
ideally
when
possible,
would
would
get
compiled
using
higher
optimizations
as
in
using
an
llvm
backend
instead
of
the
single
pass,
and
this
this
also,
they
are
planning
to
do
so
so
earlier,
just
fyi
those
those
things
are
moving.
B
F
Yeah
I'm
curious,
like
we
have
a
couple
calls
that
I
saw
that
like
take
100
tera
gas
like
would
be
good
to
kind
of
dive.
In
I
mean
yeah.
Obviously,
like
you
know,
white
listing
and
compiling
faster
is
all
great,
but
like
yeah,
it's
just
one
thing
is
like
if,
if,
if
there's
either
optimizations
or
yeah
some
gas
miscalculations
that
okay,
let
me
let
me.
F
F
B
Yeah
we
discussed
that
so
bo
basically
believes
he
has
everything
he
needs
if
he
didn't
feel
like
he
needed
anything
more
from
us
in
that
regard.
I
remember
he
spent
months
on
the
evm
team,
so
he's
pretty
familiar
so
so
he
he
actually
took
a
new
vm.
He
even
did
a
few
pull
requests
for
that
and
he
he
believes
he
has
what
he
needs
in
that
regard
he's
running
code,
I
believe
to
test
things.
A
F
A
F
Like
I,
I
posted
in
one
of
the
chats
it's
like
100
100
tera
gas
were
taking
like
25
milliseconds
40
tera
gas
was
taking
like
17
milliseconds.
You
know,
tender
gas
was
taking
like
six
months
like
it's
not
correlated
like
between
the
milliseconds
and
gas,
like
at
least
on
my
machine
and
so
like.
I
would
just
want
to
make
sure
that
we
compute
like
this
is
not
related
to
vm
as
much
as
like
our
gas
should
be,
like.
You
know,
confusion
reasonably
yeah
consistently,
but
also
we
should.
F
We
should
also
know
why
it's
taking
500
tera
gas,
like
ideally
you
know
like
in
in
in
ethereum.
You
can
kind
of
point
out
that,
like
I'll
just
p,
you
know
because
of
this.
This
is
taking
this
much
because
this
is
taking
as
much
yeah.
We
need
tooling.
For
that
we
need.
We
need
them
like.
We
need
know-how
and
tooling
how
to
do
this
and
it's
useful
for
not
again
not
just
for
edm
but
for
everyone.
So
so
I
think,
like
contract
runtime
can
be
like
focused
on
this.
B
B
On
that,
it's
whitelist
evm
retain
in
memory
and
of
the
optimizing
compiler
okay.
Well
with
that,
I
think
we're
out
of
time.
I
will
fill
in
the
the
next
week
from
from
what
everybody
said
afterwards
and
yeah.
That's
that's
enough
for
today.
Thank
you,
everybody
and
alex.
Can
you
can
you
check?
Do
you
have
any
questions
on
youtube.