►
From YouTube: NEAR EVM Working Group Update [2021-03-05]
Description
https://gov.near.org/t/2021-03-05-evm-update/848
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
Yeah,
so
I
have
no
major
things
on
the
on
the
evm
lots
of
focus
on
the
bridge
right
now.
The
only
thing
yeah.
Actually,
the
only
thing
that
I
can
report
here
is
that,
together
with
the
evgeny
hanap
and
kareel
abramov,
we
are
working
on
the
earth
connector.
So
it
seems
like
so
f.
Connector
is
the
guys
the
guys
already
made
pretty
good
progress,
and
this
week
they
were
able
to
send
the
transaction
in
from
ethereum
to
near
in
one
in
one
direction.
A
All
right
on,
on
my
end,
this
was
still
a
split
split
week
for
attention
dealing
with
some
healthcare
issues,
but
normalizing
on
that
and
beginning
to
get
back
into
the
flow
of
things.
A
C
A
And
repositories
of
relevance
are
moving
moving
here.
Let's
discuss
this
topic
in
the
discussion
segment
and
add
it
to
the
agenda.
I
fixed
some
regressions
in
the
provider.
A
A
The
formerly
near
fr
pc
is
now
called
relayer
and
I
improved
the
usability
after
some
feedback
from
frank
on
on
difficulties
he
had
in
in
using
that
the
usual
review
and
merge
of
a
bunch
of
pull
requests
and
supported
our
new
hire
mat,
who
will
welcome
soon
and
frank
and
joshua
and,
most
importantly,
I'll
continue
working
on
the
near
evm
talk
about
that
in
a
bit.
C
We
successfully
test
robston
network
and
near
destination
ros
connector
also,
we
discussed
with
alex
chuchenka
some
small
things
to
improve
our
contracts.
All
of
the
things
I
implemented,
but
currently
we
have
one
really
small
issue
for
new
event
format
for
for
our
new
testing.
So
I
think
today
we
will
fix
all
the
things
and,
after
that,
we,
I
believe
we
complete
our
testing
for
robson
and
near
test,
and
and
after
that
we
can
move
forward.
A
Okay,
which
testnet
is
a
drop
system.
C
A
C
D
Yeah,
basically,
I
focused
exclusively
on
the
bully
this
week,
looked
for
the
stack
of
the
eth
rpc
and
the
web
3
provider
and
ran
into
some
issues
there
and
had
a
few
pull
requests
and
then,
after
discussing
with
otto,
decided
that
it's
probably
better
easier
and
also
more
performant.
D
If
we
just
skip
all
of
that
and
talk
directly
to
the
near
core
rpc
and
so
basically
cut
out
all
the
the
layers
in
between
talk
directly
to
the
near
ep,
neocore
rpc,
because
it's
also
more
performant
and
then
brought
the
basically
some
go
rpc
layer
which
at
some
point
we
might
want
to
factor
out.
But
it's
not
complete.
So
basically
what
we
have
as
near
api
gs.
D
I
tried
I
started
building
that
as
near
api.
Go
and
use
that
to
connect
to
near
core
did
some
test
things
like
retrieving
block
status,
retrieving
state
of
an
account.
D
I
have
pausing
formatting
of
near-mounts
reading
the
keys
from
the.
D
Key
store
of
the
near
cli
and
sending
a
transaction
also,
the
the
api
call,
is
there
and
then
the
next
step
is
basically
building
the
transactions
and
then
sending
them
to
the
contract.
D
So,
what's
what's
missing
on
the
bully
side,
basically
is
taking
the
ethereum
transactions
kind
of
wrapping
them
into
a
near
transactions
and
submitting
them
to
near
core
directly
to
the
contract,
and
what
we
have
to
then
do
on
the
on
the
contract
side
is
that
we
kind
of
have
to
compile
an
evm
with
these
two
additional
calls
we
have
to
add.
One
is
to
set
the
genesis
state
and
one
is
to
also
submit
the
context.
D
A
I
see
you
also
started
the
discussion
for
the
podcast,
so
you
can
okay,
so
this
is
three
four
five
six
in
there
for,
if
somebody
has
any
any
comments
on
this,
how
we're
going
to
simulate
block
cache
and
that's
our
ebm
opcode-
that
we
that
we
need
to
support.
D
Yeah,
basically,
what
if
jenny
carpoon
suggests
that
I
put
it
in
there
and
suggest
that
we
add
another.
We
also
put
the
chart
hash
and
or
the
account
hash
and
the
account
id
into
the
hash,
because
we
can
have
more
than
one
evm
and
then
that
way,
the
block
hashes
are
unique
for
the
evms.
A
C
Yeah,
you
know
I
was
just
helping
a
little
bit
like
some
of
the
contracts
were
in
there,
so
just
out
of
them,
but
yeah
nothing
much!
It's
just
like
some
cleanup.
A
Yeah,
okay,
all
right-
and
I
believe,
do
we
have
joshua
with
us
he's.
I
know,
he's
sick,
so
he
might
not
have
joined
anybody
see.
The
attendance
list
is
a
little
bit
harder
than
screen
sharing
to
see
it.
A
Okay,
all
right,
let
me
give
you
his
his
updates
that
he
wrote
me
so
he
he
was
working
on
the
helping
helping
ilia
on
on
the
upgrade
functionality,
adding
solving
some
cargo
cargo
issues
there
and
beginning
to
add,
sim
tests
he's
a
little
bit
blocked
on
that,
but
he
just
messaged
me
prior
to
the
call
that
he
has
managed
to
unblock
himself
and
would
would
continue
so
also
not
to
you
yeah.
A
He
just
planned
to
pull
blue
on
that
and
he's
let's
see
here
right,
so
he
noted
that
the
evm
contract
can't
exactly
use
the
the
sdk
sim.
It
has
to
be
just
a
wee
bit
lower.
A
What
they
said
is
that
the
evm
contract
can't
exactly
use
the
sdk
sim
yeah.
It
needs
to
be
just
a
little
bit
lower,
yeah,
okay,
yeah,
so
all
right,
so
he
said
that
he
he
should
have
the
same
test
by
monday.
He
he
figured
out
what
the
crucial
mistakes
now
in
the
meantime,
while
he
was
blocked
on
that,
I
assigned
him
to
work
on
3954.
A
So
this
is
the
host
function,
additions
to
to
the
math
api
in
nearcore
and
there's
still
a
bunch
that
needs
to
be
done
there
and
there
might
be
a
good
task
for
him
to
take
over.
So
I
I
supported
him
to
get
started
on
the
game
or
yesterday,
actually
so
I'll
write
his
updates
here
after
after
the
call.
A
A
Do
we
have
math
on
the
call?
Yes,
thank
you.
Hey,
hey,
matt
hi!
So
matt
is
joining
us
this
week
he
will
be
helping
alex
on
the
product
side.
Matt
is
a
very
experienced
product
person,
as
we
coders
call
them,
and
I
worked
with
him
on
and
off
for
15
years.
I
believe
a
lot
of
projects,
including
for
for
google,
the
us
navy
and
the
european
space
agency,
so
matt,
I
believe,
is
fully
you're
already
on
all
the
relevant
slack
channels.
C
Okay,
well
on
discord.
I
don't
think
I've
been
given
any
any
roles
yet
so
I
think
I'm
just.
D
B
A
B
Yeah,
so
the
procedure
was
was
shifting
a
bit.
So
I'm
not
sure
that
is
right
now
the
same
as
it
was
so.
A
Okay,
yeah,
that's
true:
okay,
I'll
get
it
sorted
out
for
you.
In
any
case,
I
understand
that
you,
you
are
assigned
not
to
the
bridge
team
chiefly,
but
that
you
would
plan
to
attend.
Also
evm
calls
when
you
can
yeah.
Okay
sounds
good
okay.
So
let's
talk
about
aurora
as
a
codename,
since
we
already
got
some
questions
on
on
twitter
after
after
max
tweeted
about
it.
A
So
very,
very
briefly:
codename
aurora
is
what
we
are
calling
the
combined
end
user
solution
of
the
bridge
and
evm
as
in
the
ethereum
solution,
ethereum
compatible
solution,
because,
after
all,
users
are
unlikely
to
care
about
the
distinctions
between
that
technical
component
and
this
technical
component.
A
A
So
you
can.
You
can
find
it
here
on
on
github
and
I
do
believe
we
have
a
a
brand
new.
Yes,
a
brand
new
twitter
account
with
no
followers
in
case.
Somebody
wants
to
follow
that,
specifically
for
more
targeted
messaging
about
evm
and
bridge
any
any
questions
on
that
from
here
or
the
audience
on
youtube.
C
I
had
one
question
arto
just
related
to
the
bridge.
It
is
currently
bridging
into
the
into
the
evm.
Is
that
a
separate
thing?
What's
the
state
of
that
with
respect
to
bridging
into
native
near.
B
Is
not,
it
is
not
done,
it
is
not.
It
is
not
working
at
the
moment,
so
the
rainbow
bridge
is
capable
of
bridging
to
the
native
here
at
the
moment
and
the
earth
connector.
So
there
are
also
things
to
discuss
there.
But
at
the
moment
what
what
we
are
doing
with
fconnect
is
an
ability
to
bridge
f
from
ethereum
accounts
to
near
accounts
in
order
to
breach
stuff
from
from
ethereum
to
evm
runtime.
A
We
do
actually
have
if
we
go
to
the
discussions.
We
have.
B
Alex
the
discussion
about
about
what
about
this.
B
A
Nope
not
too
easily
findable
probably
need
to
collect
the
muscle
than
just
in
the
corners.
Maybe
maybe
it's
even
further
back
could
be.
A
December,
oh
there's
something
at
least
okay.
This
was
okay
18th
of
december,
so
here
we
here
we
have
a
little
something
showing
okay,
but
this
was
not
actually
about
the.
A
C
There's
pretty
much
two
options:
one
is
the
evm
itself
has
logic
to
verify
proofs
and
so,
like
the
evm
contract
becomes
a
fungible
token
contract
as
well
for
for
ease
or
the
other
option
is
having
a
separate
fungible.
Talking
standard
find
your
token
contract,
and
then
you
bridge
it
between
these
two
contracts.
B
Yeah,
so
arthur,
probably
no
no
good
place
where,
where
there
is
stated,
we
were
discussing
it
for
for
some
time,
but
no
good
place
to
read
about
this,
but
yeah.
So
in
general,
like
the
the
most.
The
most
simple
thing
in
terms
of
the
bridging
in
between
two
runtimes
is
f
itself,
because
evm
is
going
to
implement
the
the
fungible
token
interface.
So
evm
contract
is
going
to
be
a
token,
which
is
a
bridged.
F.
B
Well,
we
will
have
only
one
conventional
f
balance
for
everybody
on
the
near
blockchain,
those
who
are
the
near
native
users
or
near
native
accounts
and
the
ones
who
are
having
the
accounts
only
inside
of
the
near
evm,
but
there
is
no
easy
way
how
to
bridge
breach
tokens
ear
situations
from
directly
inside
of
the
evm,
especially
taking
into
account
that
the
rainbow
bridge
approach
says
that
we
are
having
the
the
factory
that
deploys
these
contracts
as
nfp
141
contracts
on
on
the
near
native
runtime.
B
So
bridge
tokens
are
ndp,
141,
which
is
the
near
native
standard
for
fungible
tokens,
and
it
means
that
we
need
and
these
contracts
are
handling
or
they
are
holding
the
information
about
who
owns
what
and
now
in
order
to
be
compliant
with
the
evm
and
with
all
of
the
other
contracts
that
I
would
like
to
use.
B
I
would
like
to
use
these
tokens.
We
need
to
to
construct
something
that
is
going
to
tell
to
the
evm
that
that
we
need
to
transfer
these
tokens
from
this
nap141
contract
into
the
some
kind
of
year
c20
contracts
inside
of
the
near
evm
and
yeah
lots
of
things
to
be
discussed
here.
It's
not
on
our
plate
for
this
quarter,
so
yeah
at
some
point
in
time.
We
would
need
to
start
this
discussion,
but
right
now,
it's
not
working.
A
Yeah
matt
I'll
go
ahead
and
send
you
links
to
the
relevant
discussions
that
we
do
have
and
system
diagrams
and
so
on.
We
also
did
a
little
presentation
at
some
point
that
can
can
be
useful,
okay,
so
the
s
connector.
B
So
I
believe
there
is
a
an
ethereum
side
of
the
connector
already
there.
There
is
a
giant
pr
by
evgeny
for
the
near
side
of
this
connector
in
order
to
enable
transfers
from
ethereum
to
near
on
on
wednesday.
B
It
was
like
we
decided
that
there
are
like
a
couple
of
minor
things
that
need
to
be
added,
and
I
believe
since
then,
you've
gained
already
implemented
this,
and
since
he
was
saying
that
everything
is
good
and
everything
is
the
transfers
are,
are
done,
then
all
good,
and
there
were
a
little
bit
more
on
the
guinness
plates
to
do
in
order
to
enable
the
transfers
back.
C
All
changes
implemented,
but
real
today
changed
events
fields,
so
I
can
fix
that
for
testing.
B
Okay,
so
so
you,
you
need
to
also
to
update
the
the
events
that
that
your
that
you
are
getting
on
the
connect
on
the
on
the
near
side.
Connector.
Is
this
correct,
or
it's
only
for
testing,
okay,
so
yeah?
So
what
I?
What
I
suggest
is
to
do
the
following.
I
suggest
you
get
into
to
do
the
final
changes
and
and
deploy
together
with
kirill.
This
contracts
to
to
the
robstone
well
drops
an
end
to
near
test
net.
B
Since
we
have
already
working
bridge
in
between
these
two
and
yeah,
and
then
I
can
over
the
course
of
the
weekend,
I
would
be
able
to
work
a
bit
on
on
the
cli
guide
that
that
I
have
for
for
the
ear
c20
connector
and
I'm
going
to
test
to
test
this
connector.
But
I
believe
we
are
pretty
close
for
the
connector
to
actually
work,
which
is
good.
A
Okay,
now
after
it
it
does
work,
we
still
have
the
question
of
reintegrating
it
into
the
contract
and,
let's
see
how
this
looked
currently
for
the
dependencies,
what
are
we?
What
are
we
using
here.
A
Okay,
you
can
you
have
you,
have
you
already
given
thought
to
to
how
you
would
convert
it
to
use
no
std
and
no
sdk.
C
Yes,
I'm
looking
to
some
examples
for
how
to
do
that,
and
we
can
implement
that.
I
I
can
estimate
how
it
about
time,
but
it
possible.
Also.
I
want
to
tell
about
function
related
to
withdraw.
We
discussed
with
alex
that
in
that
time
we
implement
the
invisible
only
for
near,
but
for
serum
we
will
implement
later.
B
Yeah,
so
so
there
is,
there
is
a
one
specific
for
this
contract
is.
As
I
said,
there
are
some
some
users
who
who
are
going
to
own
f,
and
these
users
are
on
the
both
sides
and
the
bus,
runtimes,
the
linear
accounts
and
ethereum
accounts,
and
that's
why
we
would
need
to
have
two
maps
inside
of
this
contract.
B
One
is
for
one
side
and
one
for
the
other,
so
we
need
to
handle
correctly
the
transfers-
you
know
all
the
stuff,
so
so
at
the
moment,
yeah
and
and
the
problem
with
with
with
the
ethereum
users,
is
that
in
order
to
withdraw,
they
need
to
schedule
an
eap
712.
B
They
need
to
send
an
eap,
712
message
of
the
specified
format
which
is
not
yet
now
fixed,
then
send
it
to
the
json
rpc.
That
is,
that
need
to
wrap
it
into
the
near
transaction
and
send
it
to
to
to
the
near
blockchain.
So
just
because
we
do
not
have
all
of
this
functionality
already
there.
So
we
decided
to
to
limit
us
right
now
for
this
connector
only
to
to
near
accounts
only.
B
I
believe
this
is
going
to
be
an
okay
approach
to
cash
state
when
we
can
merge
both
and
once
we
have
the
and
then
and
then
we
need
to
start
the
discussion
of
the
formats
of
the
of
the
712
messages
and
how
they,
how
how
they
are
going
to
be
processed
by
the
rpc
proxy
and
and
and
in
the
end.
We
would
need
to
have
our
pc
proxy
to
work
with
these
messages.
B
A
C
B
A
So,
let's
call
it
the
relayer
these
days.
Since
that's
what
we're
doing
okay,
I
need
to
discuss
those
okay,
but
so
how
does
it
look
for
for
schedule?
A
You
said
you're
getting
that
you
can
approximately
estimate
network.
How
do
you
feel
about
that.
C
I
can
estimate
in
monday-
well
I'm
sorry,
tuesday,.
A
We'll
do
all
right,
let's
come
back
to
that
then
so
for
the
for
the
bully
frank,
are
you
blocked
on
anything.
D
A
D
Yes,
so
finishing
exactly
finishings
of
submitting
the
transaction
directly
to
neocore
and
the
the
evm
contract.
There
are
no
blockers
there
and
it
should
be
done
next
week
and
then
the
contract
itself
has
to
be
extended
behind
the
feature
flag.
With
this,
these
extra
functions-
and
I
haven't
started
looking
into
that.
So
I
see
I
think.
A
I
think
I
think,
that's
probably
best
for
me
to
support
yeah.
Otherwise
you
will
have
a
learning
curve
there
yeah,
because
we
need
to
start
the
replaying
soonest.
So
I
will.
I
will
support
that
next,
victim
cool
okay.
So
assuming
that
you
got
the
necessary
contract
changes,
when
do
you
think
you
you
would
be
able
to
start
replaying.
A
A
Okay,
so
on
disk
get
15
gigabytes,
okay,
that'll
be
interesting,
I'm
sure
we
will
discover
many
many
things
of
note
and
interest
in
that
exercise.
A
Okay,
okay,
any
anything
else
to
discuss
today
sounds
like
we
are
in
a
bit
of
a
intermediate
stage
for
everything
right
now.
Nothing
really
completed
this
week
just
need
to
continue
work.
A
No
well
then,
this
will
be
a
nice
short
meeting.
So,
let's,
let's
try
to
wrap
up
the
the
bully,
I
think
get
it
get
it
going
over
the
course
of
next
week.
I
think,
hopefully
we
can
report
that
on
the
call
a
week
from
now
and
for
the
f
connector,
we
have
the
well.
A
We
have
the
big
big
question
of
how
long
the
integration
will
take
into
the
contracts,
which
also
needs
the
contract
to
be
in
a
state
to
be
ready
to
be
integrated,
which
I'm
I'm
working
on
so
yeah
next
next
week,
we'll
have
more
updates,
let's
continue
work
and
give
a
nice
update
a
week
from
now.
A
Nothing
then
I
wish
everybody
a
very
happy
weekend
and
talk
to
you
next
week.