►
From YouTube: NEAR EVM Working Group Update [2021-03-19]
Description
https://gov.near.org/t/2021-03-19-evm-update/965
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
B
B
C
B
B
A
Most,
I
was
doing
lots
of
stuff
on
the
bridge
side
because
the
bridge
was
just
released
and
actually
the
the
front
end
now
is
available.
We
just
less
than
an
hour
ago.
We
made
it
public.
So
if
you
want
to
use
it,
please
do
it
and
yeah,
but
I
was
actually
having
a
call
with
with
kirill
and
eugenie
on
on
the
connector.
We
were
looking
a
little
bit
into
it,
not
not
much
input.
From
my
side.
I
actually
started
to
test
the
the
current
deployment
of
the
connector.
A
I
managed
to
lock
some
ether
on
the
robson
deployment,
but
unfortunately
not
yet
figured
out
how
to
deposit
it
on
the
near
side
and
obviously
the
the
transfer
back
is
still
not
tested
by
myself.
I
I
know
that
there
are
two
big
yeah,
so
so
that's
from
from
my
side,
there
are
two
big
pr's
that
were
prepared
by
guys
still
need
to
be
reviewed.
I
will
try
to
help
you.
B
B
Okay,
so
on
my
side,
I'm
working
on
the
aurora
engine,
which
is
what
we
are
calling
the
revamped
contracts,
the
evm
even
contracts-
is
here.
So
this
also
towards
elia's
question
earlier
to
me
that
we
are
retiring,
the
near
evm
report.
This
is
this,
contradicts
that
feature
parity
and
beyond.
As
in,
for
example,
we
have
the
raw
transactions
implemented
now,
which
is
a
node
for
frank
as
well.
We
need
stores
for
for
the
bully,
so
I've
been
I've
been
working
hard
at
this.
D
I
successfully
completed
the
pure,
no
std
as
connector.
I
mentioned
you
in
vr
and
it
was
a
lot
of
pitfalls,
but
all
of
them
I
successfully
resolved
and
currently
it's
really
for
testing.
I
I
start
testing
with
manual
testing
with
near
cli
and
I
think
for
next
next
week
we
should
test
it
with
probably
this
integration.
E
Yeah,
it's
looking
good,
so
I
extended
the
bully
that
it
can
handle
the
whole
tester
chain,
so
he
had
it.
I
had
to
add
some
defrosting
option
for
larger
chains
and
also
did
some
caching
so
that
the
startup
time
is
much
reduced
because
we
always
have
to
go
from
the
last
block
until
to
the
first
one,
and
so
I
added
a
cache
there
and
then
I
fixed
this
problem
we
had
was
sending
transactions.
E
B
E
B
E
E
B
D
B
D
D
That
was
just
basically
the
things
that
we
might
invest
in
in
the
in
the
pr
and
fgd,
because
you
call
gave
me
a
plethora
of
information
is
some
stuff
that
we
missed
some
like
config
options
and
whatnot
and
gave
me
some
advice
to
avoid
some
potential
pitfalls
you
might
run
into
so
I
took
a
lot
of
notes,
so
that
was
really
helpful
and
then
I
implemented
the
f
compression
compression
function
as
part
of
our
evm
ap
or
math
api.
So
I
that's
what
I've
been
doing
today.
B
D
B
Okay,
all
right!
So
once
you
once
you
finish
that
there's
plenty
for
plenty
of
work
for
you
on
the
contract
side,
so
we'll
pull
you
back
there
afterwards,
okay,
and
we
still
have
to
bring
over
elias
pr
from
near
evm
for
the
upcredibility,
that's
not
yet
incorporated
in
the
in
the
new
contract
so
that
that
might
be
a
place
for
you
to
start
since
you're
already
familiar
with
that
sure.
Unless.
B
B
B
C
D
C
D
C
Because,
like
specifically
all
the
storage,
manipulations,
etc,
they
already
are
implemented.
It's
like
pretty
much
account.
Management
should
be
implemented
in
evm
kind
of
on
ibm
contract
size
right.
It's
not
it's
not
a
separate
thing.
It's
like
you
know
it's
the
same
balance
that
evm
is
using
and
so
like.
It's
all
should
be
implemented
in
one
kind
of
logic
and
and
then
the
kind
of
logs
parting
like
the
logs
parsing
yourself.
That
can
be
just
left
as
a
library
that
we
just
pull
in,
like
a
separate
cargo
or
whatever.
B
B
At
the
same
time,
though,
the
the
logic
that
you've
implemented,
your
kenny
can
certainly
start
to
be
tested
in
the
standalone
contracts.
If
you
have
somebody
somebody
available
for
that
and
as
a
result
can
be
validated
on
our
independent
track.
From
from
the
the
account
and
storage
integration
into
the
avm
contracts,.
C
B
C
Be
clear
like
the
the
standalone
connector
is
useful
and
so
like
we
can
actually
use
that
instead
of
having
a
wrapped,
e3
or
20
like
that.
That's
one
option
that,
like
I
think
with
bridge
theme,
is
maybe
a
good
good
decision
to
make
like.
Should
we
use
wrap
deeper,
or
should
we
use
this?
This
kind
of
made
easier
representation
on
native
here.
A
Most
probably
they
would
like
to
to
do
the
the
same
storage
management
as
with
any
fungible
token,
and
and
the
reason
why
to
to
have
the
to
have
this
like
condensed
in
inside
of
the
evm
contract-
is
that
then
people
will
be
able
to
move
their
ether
from
like
near
runtime
to
e
to
evm
runtime
seamlessly.
So
they
do
not
need
to
do
anything
with
it
or
in
case
they
want
to
to
transfer
some
ether
to
other
user.
They
are
able
to
do
this.
C
A
C
You
will
try
to
do
a
native
like
transfer
of
ether
inside
a
yen
and
so
there's
obviously
no
like
near
attached
yeah,
but
so
sorry
not
near
that
there's.
Nobody
will
call
like
stories
deposited
on
the
new
year
before
this
transfer
happens,
and
so
the
allocation
will
need
to
happen
kind
of
internally.
A
A
C
A
C
A
C
Like
focus
on
getting
that
and
like
I
mean
I've
got
to
say,
this
is
the
plan
for
next
week
and
I'm
just
like
I'm
just
highlighting
the
things
that
needs
to
be
thought
through
and
specifically
like
account
management
is
the
piece
actually
is
that
upgradability
vr
had
part
of
the
account
management
like
an
ethereum
style.
Account
management,
where
you
kind
of
contribute
the
cost
of
the
storage
expansion
as
part
of
the
transaction
cost
like.
D
C
Actually
kind
of
contains
that,
like
partial
implementation,
so
like
that
kind
of
needs
to
be
like
like
thought,
through
as
a
process
and
and
also
figured
out
like
what
are
the
old
externalities
like
rpc
proxies
and
everything.
That
needs
to
be
like
aware
of
this
and
know
how
to
measure
like
how
much
how
much
storage
will
be
allocated
for
a
specific
call
to
be
able
to
kind
of
attach
the
right
amounts
of
funding
to.
D
C
B
A
C
B
A
B
C
Yeah
I
mean
people
keep
asking
pretty
much
yeah,
what's
kind
of
what
the
religions
are
going
to
be,
so
we
should
have
some
like
I
mean
I
know.
I
know
that
part
of
the
near
bully,
obviously
will
or
whatever
bullies
will
be
kind
of.
I
would
expect
the
outcome
would
be
this
as
well,
but
I
think
like
having
just
like
a
few
numbers
for
like
what
is
the
fun
like
year,
20
transfer.
What
is
the
like?
E
B
C
B
C
B
Thing
sure
yeah,
so
in
terms
of
just
measuring
the
gas
usage,
what
we
could
do
in
in
frank's
suggestion
is.
We
could
take
something
like
the
n
first
blocks
of
girly.
You
know
which
are
never
gonna
change
and,
and
they
take
some
reasonable
amount
of
time
to
run
through
the
bully,
and
we
can
count
the
total
total
gas
consumed
for
that
and
then
over
time
work
to
bring
that
down.
C
I
mean
that's
an
interesting
method
for
sure
I
I
was
thinking
more.
Something
like
people
can
practically
reason
about
it,
which
is
yeah.
There's
like
there's
20
jobs
for
like
something
known
to
people,
but
don't
just
feel
like
yeah.
I
mean
aggregate
aggregate
costs
and
stuff
like
this.
This
is
what's
going
to
show
you
yeah
how
efficient
their
contracts
are.
A
B
Yeah
sure,
so
we
need
to
have
some
some
guidelines
right
now.
What
people
can
expect
to
set
expectations,
but
I
think
in
in
terms
of
our
second
quarter
objectives,
it
might
make
sense
to
start
to
bring
bring
down
the
the
course
the
gas
used
in
in
something
like
the
first
in
blocks
of
berlin,
for
example,
that
that
would
be
a
good
good,
measurable,
objective
there.
B
B
B
I
push
back
a
little
bit
and
we
have
a
little
bit
more
time
for
fog
per
se
next
week
and
the
okay
review
will
will
commence
the
subsequent
week.
But
there
are
some
some
meetings
that
certainly
I
and
alex
need
to
attend,
and
perhaps
perhaps
some
of
some
of
you
guys
as
well.
So
that's
just
something
to
know
that,
starting
next
week
we
we
begin
to
to
evaluate
the
the
q1
okrs,
which
we
already
did
as
a
practice
run
a
few
weeks
ago.
B
If
you
remember,
and
then
we
finalize
the
the
okay
review
for
q1
in
the
first
weeks
of
of
april
and
I'm
beginning
to
do
q2
planning
which
will
consume
a
bunch
of
time
from
everybody
just
in
terms
of
setting
expectations.
But
for
now
we
focus
on
on.
We
have
defined
much
much
29.
So
that's
that's
the
monday.
After
next
we
can
define
that
as
the
launch
date
for
for
the
objective
of
evm
on
testnet,
and
I
think
we
can
certainly
deploy
something
there.
B
A
B
B
Okay,
well,
then,
let
us
get
back
to
book,
there's
a
lot
of
coding
to
be
done,
and
on
monday,
let's,
let's
coordinate,
let's
coordinate
more
on
the
s
integration
you're,
getting
I'll
bring
you
also
today
and
ilya
promised
to
work
on
on
a
few
things
in
the
contract.
You
already
know
which
one
so
upgradability
is
what
you
would
like
to
work
on.