►
From YouTube: NEAR EVM Working Group Update [2021-04-02]
Description
https://gov.near.org/t/2021-04-02-evm-update/1123
Follow the latest from NEAR Protocol on,
Website: https://near.org/
Discord: https://near.chat
Blog: https://near.org/blog/
Twitter: https://near.ai/twitter
GitHub: https://near.ai/github
#Blockchain #FutureIsNEAR #NEAR #NEARProtocol
A
A
B
B
A
Right
so
on,
on
my
end,
it's
been
a
very,
very
relentless
week,
a
bunch
of
things,
so
I've
worked
on
the
our
engine.
Of
course
we
have
a
lot
of
other
stuff
going
into
here,
including
all
the
other
things
around
around
it,
such
as
continuous
integration
and
and
so
on,
and
to
facilitate
development
and
testing.
A
Those
are
those
are
there,
but
we
need
to
still
get
those
ports
open,
waiting
waiting
on
the
certain
team
on
that
and
yes,
that's
not
mysterious
destiny,
hard
fork
to
be
discussed,
and
indeed,
yesterday
deployed
deployed
contract.
We
could
actually
have
a
look
at
the
concrete
accounts
from
here,
so
here
in
the
in
the
main
repo
we
have
links
to
the
explorer
on
the
various
nets
and
mainnet
has
nothing,
of
course,
as
here
as
yet.
A
B
C
A
C
A
B
C
C
C
A
C
D
D
Gonna
go
full
time
with
this
other
project
and
poke
my
head
around
once
in
a
bit
so
yeah,
I
found
it
fairly
easy
to
fix
some
of
the
ci
issues
as
the
ones
that
you
needed
me
to
fix
up.
Then
I
ran
into
some
issues
with
the
ec
recovery,
so
they
were
a
bit
confusing
at
first,
but
then
I
found
out
that
the
easy
recovery
implementation
was
not
completely
correct.
A
A
D
D
A
A
A
Cool
okay,
good.
So
let's
talk
about
things.
Let's
talk
about
first,
why
we
did
a
disney
hard
fork,
which
may
be
some
some
are
curious
about,
so
we
we
did
a
hard
focal
reboot
of
this
net
last
last
night
and
the
the
reason
was
that
when
we
started
to
want
to
deploy
the
contract,
we
came
across
an
unexpected
issue
that
the
let
me
see
if
I
can
find
the
link
here,
the
the
top
top
level
account.
A
A
I'm
starting
the
process
with
the
foundation
for
claiming
the
top-level
account
on
mainnet
as
well.
There's
a
general
concern
about
the
top-level
accounts
that
I
should
probably
mention.
While
while
we
have
elia
on
the
phone
as
well
as
in
this,
probably
this
was
probably
not
the
only
top-level
account-
that's
left
over,
let's
say
from
from
old
old
times,
testing
on
on
testnet
and
at
the
point
when
the
registrar
for
top-level
names
will
be
activated
on
on
mainnet.
A
A
B
A
No
and
okay,
so
that
was
the
hard
fork
and
this
net
is
still
stabilizing
from
it,
as
in
protocol
upgrade
still
ongoing,
but
should
be
sorted
by
end
of
the
day.
The
next
item,
we
have
a
couple
of
requests
to
reschedule
this
meeting
this
weekly
weekly
friday
update.
How
does
everybody
feel
about
that?
I
think
to
suggest
to
us
most
recently
alex
elia,
correct
me.
If
I'm
wrong,
we
would
reschedule
this
two
hours
earlier,
which
makes
it
a
lot
easier
for
people
in
asia.
A
A
A
D
A
A
So
this
is
now
not
for
yet.
This
is
not
I'm
not
showing
something
very
relevant
to
end
users
of
aurora
right
now,
just
showing
something
for
developers
of
the
contract.
So
I
trust
you
can
see
my
terminal
and
what
I'm
going
to
do
is
I'm
going
to
basically
go
through
the
examples
from
the
readme.
We
have
pretty
good
examples
in
the
readme
for
how
to
use
the
tooling,
so
you
can
follow.
Follow
along
in
the
aurora
engine.
A
A
A
A
B
A
A
Okay,
all
right
well,
look
like
I.
I
messed
it
up.
Let's
come
back
to
that
after
this
starts
up.
If
it
does
I'll
check
on
it,
oh
there
there
we
go
okay,
let's
see
that
looks
better
yeah,
so
once
you're
pointing
at
the
right
end
point,
apparently
I
must
have
had
a
environment
variable
pointing
at
something
else,
perhaps
bit
on
it,
which
seems
to
be
having
trouble
yeah.
A
So
once
once,
you've
got
your
environment
variable
setup
deploying
a
new
release
is
as
easy
as
aurora
install
and
you
can
configure
the
parameters
there
like
the
chain
id
and
the
owner
of
the
contract.
So
we
have
here
some
parameters
that
can
be
sent
and
then
then
let's
actually
show
some
of
the
ways
you
can
call
the
contract.
So
you
get
all
the
all
the
methods
on
the
contract
exposed
as
cli
commands
that
you
can
call.
A
Deploy
uvm
contracts
as
in
ethereum,
solid
contracts-
let's
see
here
so
there's
a
deploy
code
command
for
which
you
can
give
a
file
name
or
you
can
give
it
directly
bytecode.
So
the
file
name
form
looks
like
it
looks
like
this.
I
don't
actually
have
a
file
there,
so
I'm
going
to
deploy
and
a
simple
contract,
so
not
too
much
bytecode,
but
you
can
just
give
it
the
bytecode
like
that
and
you
get
back
the
contract
address.
A
A
A
B
B
A
A
A
B
A
A
Each
each
host
is
running
the
respective
near
core
directly
on
the
host
and
then
running
the
aurora
relayer.
On
top
of
that,
the
earlier
code
base
is
here
and
we'll
put
those
up
at
public
public
urls
as
soon
as
we
get
the
supports,
router
done
and
open,
which
should
be
later
today.
I
hope
documentation
updates,
like
you
saw,
are
in
the
books,
and
I
think
we
discovered
with
frank
while
we
were
doing
documentation,
updates
that
this
there's
a
bunch
of
work
there.
A
So
this
is
still
published.
It's
the
old
documentation
which
works
for
bit
on
it
depending
on
it.
Old
contract
is
called
evm
instead
of
aurora,
and
all
of
this
documentation
is
in
terms
of
that.
I'm
gonna
have
a
talk
with
mike
about
recording
some
new
videos.
This
this
whole
videos
will
not
be
entirely
applicable
and
also
as
frank
mentioned,
we
need
to
well.
We
need
to
convert
some
some
jpegs
into
actual
code
code
examples,
so
bunch
of
works
to
do
on
the
documentation.
A
A
So
those
are
the
the
main
main
aspects
of
what
we
still
need
to
do
before
we
can.
Let
people
add
it.
Then,
of
course
we
we're
missing
features,
always
missing
features
with
missing
a
few
pre-compiles
which
joshua
is
tackling,
and
we
have.
We
have
some
failures
in
in
terms
of
the
balancer
test
suite
and
a
couple
of
other
internal
test
suites
that
we
had.
A
You're,
pretty
sleeping
okay
yeah,
so
we
have
a
lot
of
work
to
do
around
the
contract
around
the
the
engine.
The
deployment
was
just
the
first
first
part
and
at
the
same
time,
beginning
to
plan
what
we
want
to
do
in
q2
and
what
we
want
to
do
in
q2.
I
think,
most
importantly,
is
fairly
soon
deploy
this
to
maintenance,
probably
sooner
than
than
we've
communicated
before
and
we'll
work
out
in
the
next
week.
What
that
might
look
like
how?
What
is
a
realistic
timeline
for
it.
B
B
A
A
I
can
share
a
roadmap
on
that
for
for
now
we
need
to
wrap
up
this,
releasing
in
every
way
so
quality
assurance
relays,
documentation
and
so
on,
which
I
think
will
be
able
to
do
in
the
next
week
and
and
then
then
we're
going
to
start
on
bullying
the
this
net
or
maybe
not
the
disney,
but
the
the
the
bit
on
it
aurora
engine
once
the
once.
The
bullet
is
ready
to
go
and
integrate
the
the
connector.
So
those
are
the
near-term
directions
there.
B
No,
I
think
we
are
too
late
on
this,
so
this
is
yeah.
I
think
we
are.
We
are
going
to
to
do
as
a
separate
communication-
okay
understood,
but
for
sure
it's
it's
better
to
do
it,
maybe
not
maybe
in
a
simple
way
yeah.
So
this
is
a
test
net.
This
is
not
the
main
net.
Maybe
we
can.
We
can
do
some
some
kind
of
transform
some
of
the
blog
posts,
some
like
the
or
the
evm
blog
post
into
sorry
governance
forum
post
into
the
blog
post
and
then
that's
it.
B
A
A
A
B
A
Yeah
and
of
course,
as
we
showed
with
the
aurora
climb,
we
care
not
only
about
the
end
user's
developer
experience,
but
also
our
own.
It
was
getting
a
little
frustrating
to
interact
with
the
contracts,
so
I
had
to
create
some
tooling
okay.
Well,
then,
that's
everything
for
today
and
talk
to
most
of
you
on
monday
again.