►
From YouTube: NEAR EVM Working Group Update [2021-01-29]
Description
https://gov.near.org/t/2021-01-29-evm-update/530
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
A
To
the
evm
working
groups,
weekly
public
updates
today
looks
like
we're.
Gonna
have
not
too
many
people.
A
B
A
All
right:
well,
let's
do
that
again.
So
hello,
everyone
welcome
to
the
evm
working
groups
weekly
update.
Today,
we
are
not
going
to
have
a
very
long
call.
I
think
we
don't
have
too
many
too
many
people
joining
us
today.
B
B
A
Hackmd,
okay
right,
so
we
had
planned
a
bigger
agenda
for
today,
but
many
many
people
had
conflicts
and
personal
matters
to
attend
to
so
this
will
be
a
short
call.
So
today,
let's
go
over
the
current
goal.
The
updates-
and
I
don't
think
we
have
too
much
discussion
with
just
us
today-.
A
A
We
had
two
team
members
join
us
last
week
and
I
hope
we
will
have
one
more
join
us
next
week
and-
and
we
are,
we
have
finished
the
the
robot
planning
with
with
alex
and
are
now
tasking
out
the
things
that
need
to
be
done.
Let's
talk
about
those
in
a
bit.
A
So
team
updates
effects.
You
can
begin.
A
B
Yeah,
so
in
general
I
was
working.
The
main.
The
main
thing
that
I
was
working
during
this
week
was
the
roadmap.
These
were
the
roadmap
for
both
bridge
and
evm
project,
and
this
is
something
that
arthur
is
going
to
share
with
in
in
in
some
time,
and
there
were
also
some
organizational
work.
B
Sorry,
some
organizational
work
connected
to
the
to
the
governance
forum,
so
not
big
of
that
some
comments.
Some
reading
going
a
little
bit
different
in
some
some
of
the
discussions,
a
little
bit
of
the
organization
of
their
the
categories
and
stuff
like
that
yeah
and
still
a
bit
of
hiring.
I
was
spending
some
some
time,
but
mostly
for
this
was
this
is
related
for
the
bridge.
B
Yeah
some
some
calls
with
the
partners
with
potential
partners
things
like
that:
yeah,
okay.
So
no,
not
not
that
much
to
report,
but
lots
of
small
tasks
that
just
needed
to
to
be
done.
A
B
A
Same
same
thing
here,
this
this
week
has
has
not
been
any
coding,
so
I
miss
coding
by
now
recruiting
took
up
the
most
of
my
time
this
week
and-
and
I
think
we
have
some
good
results
on
that
to
announce
soon.
A
C
Yes,
from
my
side,
I
read
a
lot
of
documentation
and
specifically,
I
started
reading
an
er
protocol,
documentation
and
and
deep
dive
into
it,
and
I
investigate
that.
A
lot
of
recommendations
probably
ought
to
be
related
and
some
page
is
not
exist,
but
it's
okay,
because
I
did
dive
into
near
core
quad
and
I
look
into
structures
and
I
understand
how
currently
probably
it's
work,
and
I
want
to
say
that
for
me,
it's
really
interesting
and
I
really
excited
how
it
works.
C
And,
additionally,
I
want
to
say
that
currently
properly,
I
understand
more
deeply.
How
blockchain
and
runtime
are
working,
I'm
not
sure
that
that
understanding
is
completed,
but
from
my
side
I
want
to
in
my
free
time,
reading
the
documentation,
because
for
me
it's
a
really
interesting
addition.
I
want
to
say
that
I
spent
time
to
play
with
tutorials
and
from
my
side
I
started
to
test
validation
knob.
Currently
I
investigate
the
process
because
for
me
it's
interesting
too,
and
how
it
works
us
how
specifically
work
service
network
so
on.
C
A
Okay,
great
yeah:
let's
let's
talk
about
if
you're
ready
to
take
on
some
tasks
next
week,
how
do
you
feel
about
that.
A
Okay,
so
let's,
let's
discuss
after
the
call
some
some
tests
that
can
be
good
to
start
with.
Thank
you
and
frank
is
not
able
to
join
us
today
because
of
personal
reasons,
but
his
updates
are
that
he
finished
well.
He
has
a
draft
pull
request
for
for
benchmarks,
esp721
benchmarks
relating
to
the
cryptos
on
this
contract
and
the
there
is
an
issue
still
before
we
can
merge.
It
he's
getting
an
unexpected
revert
from
the
evm,
which
he
can't
reproduce
outside
of
our
evm.
So
that's
something
to
investigate.
A
D
Yeah,
so
this
week's,
I
would
say,
I'm
still
on
boarding
stage
and
I'm
getting
myself
familiarized
within
the
whole
new
ecosystem
itself
and
exploring
the
forum
articles
discussions
about
the
near
about
the
base
talking
for
the
bridge,
etc,
and
I'm
also
exploring
the
videos
and
for
anyone
who
is
interested
in
here.
I
can
definitely
recommend
to
take
a
look
at
the
lunch
and
learn
series
that
is
that
are
also
mentioned
in
our
own
boarding
guides
and
the
near
overview
by
maxine.
D
D
This
week
I
also
passed
through
some
tutorials
that
were
on
boarding
guides
and
still
continue
this,
because
quite
a
lot
of
them
there,
and
I
also
started
exploring
the
and
near
smart
contract
on
the
solid
data
side
and
researching
the
possibilities
for
the
upgradability
for
this
contract
and
reviewing
the
possible
solutions
for
that,
including
the
open
zeppelin
one
that
we
have
just
recently
discussed
to
be
like
a
good
idea
to
look
for-
and
I
will
continue
with
this
part
on
the
next
week
and
probably
test
some
use
cases
and
comparing
some
of
the
approaches
for
that
upgradability
and
also
yesterday,
we
discussed
with
alex
chuchenko.
D
My
probably
first
starts
so
for
the
following
week
and
I'm
also
started
on
this
today
and
working
the
first
one
will
be
to
work
to
work
over
the
randall
bridge,
documentation
and
check.
If,
if
everything
is
correct
is
is
everything
is
launchable?
Do
we
have
any
issues
with
this
in?
If
we
have
to
correct
this
and
then
I
will
start
to
move
more
refactoring
on
changing
some
some
parts
of
the
bridge
related
contracts.
These
are
the
following
tasks,
so
I
will
start
with
them.
D
A
Okay,
thank
you
and
mike
mike
can't
join
us
today.
He
has
a
scheduling
conflict,
but
I
think
he
he
didn't
have
any
any
updates
for
this
week.
Okay,
let
me
actually
change
the
agenda
a
little
bit
since
we've
been
asked
to
to
provide
also
the
concept
for
the
next
week.
Let's
make
our
channel
like
this,
so
we
we
discussed
the
current
goal
this
week
today,
specifically
we'll
talk
about
the
road
map
and
then
the
high
level
tasking
for
next
week,
already
a
little
bit
touched
on
so
roadmap.
A
So
we
have.
We
have
here
a
a
roadmap
assume
I
shared
my
screen,
not
the
tab,
so
you
guys
can
see
the
roadmap
right.
Somebody
can
confirm
yeah,
okay,
so
we
we
have
a
a
roadmap
roughly
outlined.
A
A
Where
are
we
there?
We
are
okay,
so
I've
been
doing
a
little
bit
diagramming
with
alex
in
terms
of
how
the
task
dependencies
for
milestone
dependencies
work,
look
like,
and
this
this
is
the
result.
We
also
have
one
for
the
bridge,
but
that's
for
that's
alex
to
to
present
on
the
next
call.
A
A
We
can't
have
too
many
curveballs
thrown
at
us
if
we're
going
to
make
this
objective
right
now,
there's
a
bit
of
a
curveball
in
terms
of
the
potential
architectural
changes
that
ilia
would
like
to
make,
which
we
need
to
discuss
latest
on
next
week's
call
and
settle.
But
we
have
a
lot
of
things
we
can.
We
can
proceed
on
in
any
case
now
the
critical
path,
as
indeed
the
most
critical
path
through
this
diagram
looks
like
this.
A
We
have
a
bug
bounty
that
we
need
to
start
in
a
month
for
the
beta
nets
and
about
three
weeks
after
that
we
need
to
take
a
decision
for
whether
we
are
going
to
in
terms
of
what
the
bug
bounty
result
is
they're
going
to
have
to
take
a
decision.
Can
we
go
to
testnet
if
we
can
well,
the
bug
bounty
program
will
run
in
any
case
a
little
bit
longer.
A
A
That
version
doesn't
exist
as
yet
it's
a
in
the
works
branch,
but
it
will
exist
soon
and
we
need
to
get
onboard
that
branch
and
the
reason
we
need
this,
for
the
bug
bounty
program
is
that
otherwise
we
are.
We
are
testing
with
a
fundamentally
different
virtual
machine,
as
in
the
the
difference
between
what
we
are
using
right
now
and
open
ethereum
32
is
vast,
so
we
we
better
get
on
to
this
branch
as
soon
as
possible.
A
For
this
bug
bounty
to
be
meaningful
now
secondary.
Nobody
can
really
work
on
this
bug.
Bounty
or
few
people
can
work
on
this
bug
bounty.
If
we
haven't
properly
documented
how
to
use
the
bitternet
now,
mike's
already
done
a
great
job
on
that
we
have
a
ton
of
ton
of
material
on
it,
but
we
need
we
need
a
little
bit
more
still.
A
A
Now
what
we
don't
need
for
the
bug
bounty,
we
don't
need
esc
20.
Bridging
by
the
way,
is
everybody
able
to
see
the
text
in
screen
sharing.
It
can
be
a
little
bit
small,
I'm
gonna
zoom
in
so
zooming
in
a
little,
so
we
we
don't
need
for
the
bug
bound
to
the
esc,
20
bridging,
that's
a
separate
matter
that
fits
into
the
eventual
destiny
release
a
shared
call
with
the
bridge
team.
A
What
we
do
need
most
likely
this.
This
is
not
necessarily
a
given.
We
probably
need
the
s
connector
so
that
we
can
move
over
liquidity
in
some
form
from
let's
say,
an
ethereum
testnet
to
to
debug
bounty.
A
This
is
not
a
hard
dependency,
because
we
could.
We
could
conceive
of
other
ways
to
give
people
balances,
but
at
the
very
least
we
need
we
need
the
upgrade
and
we
need
documentation
on
how
to
how
to
work
with
it.
Now
towards
the
towards
the
quarterly
objective,
the
test
net
release.
There
are
other
things
we
need:
some
are
not
very
hard
dependencies.
A
So,
for
example,
we
will
ask
at
the
end
of
the
quarter,
the
partners
who
have
played
with
the
better
net
evm,
how
they
feel
about
it
if
they,
if
they
feel
it's
ready
or
not,
to
go
to
disneyland.
On
the
other
hand,
this
is
not
a
hard
dependency,
because
feedback
is
fussy
and
it
can
potentially
be
addressed
after
the
test
net
release,
but
in
any
case
it's
it's
it's
there
things
we,
we
definitely
need.
A
In
order
to
do
the
desktop
release,
we
need
more
information
for
the
sra
team
or
the
infrastructure
team
on
on
how
to
how
to
handle
any
any
problems
that
might
arise
now.
You
might
think
this
would
also
be
good
before
the
beta
net
bounty,
when
everybody's
trying
to
break
up
bit
on
it.
And,
yes,
you
will
be
correct,
but
it's
not
a
hard
dependency
there.
It
is
a
hard
dependency
for
a
test
net
release.
A
We
also
have
have
to
involve
the
community.
Of
course,
we
can't
just
willy-nilly
upgrade
this
net
ourselves.
Anything
that
goes
to
this
net
is
slated
for
maintenance
and
we
need
to
have
a
proper
conversation
about
it.
So
about
two
weeks
from
now,
we
should
put
up
a
proposal
in
the
governance
forum
and
and
get
start
to
get
some
some
discussion
and
ultimately
approval
from
stakeholders.
A
We
can't
we
can
schedule
the
upgrade
without
that.
We
also
have
concerns
about
performance.
So
right
now
the
evm
is
entirely
unbenchmarked.
A
We
also
have
other
things
that
are
needed
for
this
to
be
usable
on
testnet
such
as
the
the
rainbow
bridge
front
end
I
think,
alex.
Actually,
this
is
probably
out
of
date.
We
discussed,
we
don't
necessarily
need
the
front
end.
We
just
need
the
connector
to
work
right.
B
They
would
be
able
to
go
step
by
step
with
the
connectors
from
from
command
line,
interface
and
schedule
in
some
like
and
and
simple
scripts
right.
A
So
this
is
the
preliminary
program
there
are.
There
are
many
things
that
are
implicit
here,
for
example,
in
terms
of
the
feature
completeness,
that's
not
really
explicitly
addressed
here,
except
in
terms
of
let's
say
the
upgrade
to
open
ethereum.
We
have
more.
A
We
have
more
things
we
could
add
here,
but
this
is
this:
is
the
general
outline
of
how
we're
going
to
get
to
a
testament
to
release
this
will
be
published
later
today
in
in
the
forum
on
the
evm
category
on
the
forum,
and,
I
believe,
alex
plans
to
do
the
same
for
the
bridge
for
the
bridge
roadmap,
and
then
then
we
will.
We
will
be
able
to
share
this
with
the
marketing
department
and
and
others
who
have
an
interest
in
it,
including
all
external
stakeholders.
A
A
I
take
the
rationale:
okay,
now
in
terms
of
the
near-term
near-term
priorities
we
have,
we
have
a
few
things
that
should
be
done.
Pretty
much
immediately
so
alex
is
alex,
is
working
on
the
on
the
back
bounty
arranging
the
bug
bounty.
A
However,
a
difference
between
the
two
teams
is
or
the
black
bounties
is
that
the
evm
is
for
bug
bounties
for
the
bigger
net
and
the
bridge
teams,
bug
bounties
for
the
distance,
something
we'll
have
to
try
and
make
clearing
in
our
communications.
On
that,
I
am
going
to
tackle
the
upgrade
to
open
ethereum
as
of
next
week,
even
though
it
is
not
a
final
branch.
Yet
we
we
better
get
on
to
that
branch
and
handle
handling
issues
that
come
up
as
soon
as
including
communication
with
the
upstream.
A
I'm
I'm
hoping
every
tuesday
on
on
calls
with
the
open
ethereum
team.
They
have
a
community
call
where
they
can
give
feedback
and
what's
not
on
this
road
map,
because
it
it
kind
of
came
extempora
are
the
architectural
changes
that
ilia
is
experimenting
with
and
proposing,
and
we
will
have
to
work
through
decision
points
on
those
next
week
in
order
for
any
of
this
to
be
feasible.
A
So
I
hope
I
hope
we
can
have
a
good
conversation
about
those
decisions
next
week
or
friday,
so
you're
gonna.
What
I
would
propose
that
you
could
tackle
now
you
remember,
we
had
discussed
that
you
and
kirill
would
tackle
the
the
bridge
f
connector
from
sort
of
both
sides
of
the
of
the
team
dividers
in
kiro
from
the
bridge
side
and
you
from
the
evm
side,
and
that
probably
makes
makes
sense.
A
Although
the
timeline
is
pretty
short
and-
and
I
know
you
guys
are
only
half
time
currently
so,
but
what
we'll
probably
have
to
do
here
is
that
we'll
split
up
this
work
a
little
bit
so
again,
these
are
not
tasks.
These
are
milestones
so
we'll
split
up
the
the
task
in
here
a
little
bit
and
let's,
let's
get
you
get
you
on
to
this
in,
in
whatever
form
you're
comfortable
with
we'll
discuss
that
on
the
on
the
monday
call
latest
for
for
curio.
A
I
think
you
already
had
your
tasks
from
alex
and
for
frank.
We're
gonna
have
to
pull
frank
off
benchmarking.
Now
we
we
still
need
frank
on
performance,
but
we're
gonna
have
to
pull
him
to
the
replayer
as
of
next
week.
So
frank
will
will
work
on
the
on
the
current
pull
request
that
he
opened
today
the
work
in
progress.
A
Now,
let's
see
what
was
the
name
of
that
right,
so
his
pull
request
is
three
eight
six
six
and
he
needs
to
finish
that
he
has
to
the
thing
has
to
has
to
troubleshoot
with
that
which
could
take
some
time,
but
after
that
we
need
to
pull
him
to
the
replayer
so
that
we
can
deploy
it
a
month
from
now,
given
that
he's
also
half
time
currently.
A
And
I'll
add
the
diagram
and
information
here
for
for
next
week,
though,
that
means
that,
let
me
consult
my
notes.
A
Here,
right
so
frank,
frank
on
the
replayer
for
evgeny,
we
would
need
to
to
to
figure
out
in
terms
of
the
onboarding
guide.
Have
you
have
you
set
up
already
the
the
local
setup?
There
was
the
local
setup
for
the
pet
shop,
which
is
actually
a
lot
of
work.
It
can
take
hours
and
hours.
Do
you
already
have
all
of
that
set
up.
A
All
right,
so
I
would
say
that
the
the
first
focus
there
would
be
to
to
work
through
the
ethereum
compatibility
tutorials.
So
we
we
need
you
to
understand
all
of
that
material
to
be
able
to
work
on
this
and
those
are
all
currently
written
up
to
taurus.
We
don't
have
any
any
video
on
that
and
they
are
all
from
mike.
So
in
case
of
any
feedback
talk
to
mike
directly
for
the
pet
shop.
The
new
pet
shop
on
evm
example,
which
I
think
is
the
most
useful
one
to
try
to
fully
understand.
A
There's
two
two
ways:
you
can
run
that
you
can.
You
can
use
it
on
bayonet,
which
is
super
simple.
It
only
takes
a
few
minutes
to
get
started
if
you
have
a
better
wallet
and
that's
good
to
work
through,
but
ultimately
you
need
the
local
setup
and
the
local
setup
is
open
in
the
ass.
It's
no
question
about
it.
It
will
take
some
some
hours
to
figure
out
now
you
you
had
to
set
up
everything
in
your
dev
environment
with
docker
that
might
or
might
not
be
reasonable.
A
Try
to
have
a
look
at
the
instructions,
see
see
how
much
work
that
would
be
to
do
in
docker
versus
a
local
virtual
machine.
It
can
be
that
the
local
virtualbox
or
something
like
this
could
be
a
lot
faster
than
figuring
out
how
to
how
to
get
that
dockerized.
A
So
in
any
case,
let's
talk
about
those
on
the
monday
call
latest
now,
curiel
alex
has
guided
and
on
on
my
my
side,
I'll
work
on
the
open,
ethereum
change
to
begin
with,
and
then
then
deal
with
the
base
token,
with
in
coordination
with
ilya
and
alex.
Maybe
you
want
to
speak
yourself
what
your
plan
was
for
next
week.
B
Yeah
so
my
plan
yeah,
unfortunately
this
week
I
was
not
able
to
do
to
do
a
deep
dive
into
zen
hub.
This
is
something
that
is
already
a
long-standing
thing
to
do,
so
I'm
going
to
do
that
and
yeah
I'm
going
to
go
straight
into
the
the
governance
questions
because,
like
there
are
two
points,
two
things:
the
governance
of
the
bridge
and
the
the
the
rollout
of
the
evm,
which
both
of
these
things
should
be
prepared.
Pretty
quick-
and
I
think
that
is
in
parallel
with
this-
is
the
preparation
of
the
bug,
bounty
programs.
B
So,
like
multiple
things
here,
I'm
going
to
to
see
what
what
is
going
to
move
faster,
yeah
and
still
have
a
bit
of
coordination
of
the
of
the
beta
testing
community
on
the
bridge
side.
So
this
also
can
take
some
time.
Okay,.
A
Okay
sounds
about
right
and
from
mike
in
case
is
available.
We
will
try
to
figure
out
what
needs
to
be
done
for
the
bug,
bounty
in
terms
of
documentation
and
tooling,
and
then
actually
task.
That's
those
things
out
and
yeah,
of
course,
alex.
A
We
both
have
to
to
get
a
little
bit
more
organized
with
zen
hub.
Okay,
all
right,
so
I
think
that's
pretty
much
the
the
our
required
agenda.
We
managed
to
fit
into
half
an
hour.
Do
we
have
anything
to
discuss
with
the
set
of
people
here?
I
would
generally
prefer
we
would
have
more
people
for
discussion,
but
can
we
discuss
anything
useful.
B
We
have
some
people
joined.
Actually
I
would
like
to
bring
to
to
attention
of
the
of
the
whole
evm
team,
the
discussion
that
is
happening
right
now
with
regards
to
the
accounting
for
the
storage,
and
I
believe
our
inputs
here
will
be
pretty
important.
B
So
the
idea
is
that
currently
storage
takes
quite
a
lot
of
near
tokens
to
be
locked
and,
for
example,
for
the
two
to
fa
for
the
smart,
for
the
for
the
accounts
of
of
the
users
it
takes
around
36
year,
which
is
a
current
price,
is,
is
ridiculous,
so
there
is
an
idea
to
to
lower
this
down
yeah,
and
the
reason
for
for
such
high
cost
was
that
it
was
just
the
model
for
it
was
calculated
some
some
time
ago.
B
Since
then,
the
the
price
changed
and
also
like
there
are
some
kind
of
changes
in
in
the
amount
of
what,
in
the
places
in
the
in
the
storage
requirements
of
the
smart
contracts
stuff
like
that.
So
this
needs
to
be
reconsidered,
and
this
is
something
that
is
happening
at
the
moment.
B
This
is
extremely
important
because
the
current
model
for
for
evm
team,
because
the
current
model
that
nir
is
using,
is
orthogonal
to
ethereum
approached
where
people
are
just
paying
doing
a
one-time
payment
in
gas
for
for
the
storage.
Obviously,
if
the
storage
is
is
free,
then
people
are
getting
some
gas
back,
but
this
is
something
that
is
not
widely
used
at
the
moment
and
potentially
which
we
can
just
like
skip
that
type
of
functionality.
B
So
there
is
an
idea
of
bringing
these
two
worlds
yeah,
and
obviously
this
means
that
accounting
for
storage
should
be
in
case.
We
are
keeping
things
as
is
in
in
near
and
in
in
evm.
B
This
means
that
accounting
for
storage
are
different
in
these
runtimes.
So
so
that's
the
problem.
So
it's
not
uniform
across
the
the
chain
yeah.
So
I
I'm
I'm
like
encouraging
everyone
to
go
well,
especially
from
the
tech
team,
to
go
a
little
bit
deeper
into
into
the
discussion
express
his
own
opinion
on
this
yeah.
B
A
A
Plus
we
have
the
question
that
if,
if
we
are
going
to
implement
elias
proposed
architectural
changes,
then
that
does
muddy
the
borders
a
little
bit
with
regards
to
the
storage
accounting
as
in
that
that
moves
back
to
the
normal
native
web
assembly
contract
side,
which
then
might
make
it
too
expensive,
yeah.
So
there's
certainly
some
things
to
work
through
there.
Anything
else
to
discuss
today.
A
So,
let's
see
here,
we,
let's,
let's
check
for
questions
on
on
youtube
as
well.
A
Okay,
okay!
Well,
then,
then,
I
wish
everybody
a
happy
weekend
and
we
have
some
busy
weeks
ahead
of
us.
Let's
soon
come
monday
on
what
we're
actually
going
to
do
and
how
okay
bye-bye.