►
From YouTube: NEAR EVM Working Group Update [2020-11-20]
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
That's
great,
hello,
everybody!
This
is
a
weekly
evm
work
group
call
now
on
this
call.
We
are
discussing
our
weekly
progress
on
the
evm
project
in
newer
protocol.
A
Our
current
goal
is
to
deploy
the
working
evm
to
the
beta
net,
and
this
is
something
that
we
are
already
doing
for
some
time
and
hopefully
we
are
pretty
close
to
the
actual
release.
So
I
I'm
going
to
share
my
screen
going
to
okay
max.
Can
you
please
give
me
an
option
just
to
share
the
screen?
The
permission?
A
Okay?
So
thanks,
so
I'm
going
to
share
the
screen.
So,
as
you
can
see,
we
are
putting
the
information
about
this
weekly
calls
to
the
discussion
section
of
the
new
york
core
repo,
and
you
can
find
that
you
can
find
all
of
the
related
discussions
under
the
category
evm.
So
here
you
actually
can
see
everything
and
this
this
discussion
will
be
posted
shortly
after
the
call
so
eugene
as
a
tl.
Can
you
update
us
on
like
the
global
status
of
where
we
are
with
this
goal?.
B
Sure
so
we're
getting
pretty
close.
We
have
a
branch
that
is
ready
to
be
merged
and
we
have.
B
I
sent
it
for
reviews
to
people
outside
of
this
team
to
make
sure
everything
looks
good,
so
the
biggest
problem
was
around
features
and
how
to
guard
evm
change
behind
the
feature
and
the
protocol,
like
the
relative
behind
the
nightly
protocol,
which
is
subset
like
it's.
A
kind
of
new
features
that
currently
don't
make
it
into
production
networks
such
as
mainnet
and
testnet,
and
can
be,
can
be
changed
without
a
problem
of
having
to
do
hard
work
on
the
real
network.
B
We
resolved
all
known
to
us
issues
that
were
blocking
the
release
and
pretty
much
currently
only
depends
on
the
reviews,
and
once
we
get
enough
reviews,
we
can
merge
it
and
it
will
be
enabled
on
betternet
behind
their
nightly
protocol.
A
Okay-
so
that's
great,
so
it
seems
like
yeah.
We
are
pretty
close
to
to
this
point.
I
believe
that
quite
a
lot
of
people
are
scheduled
for
the
review
from
the
core
engineers.
Is
this
correct.
B
Yeah
I
asked
for
people
we
really
need
like
three.
So,
okay.
B
You
need
max
and
ideally
for
all
to
take
a
look,
so
we
are
not
blocked
on
the
not
blocking
our
pc
and
that's
still
pending
on
the
request
changes
from
max
max
has
to
do.
You
actually
need
my
review,
because
I
think
everyone
is
duplicating
me
now.
Actually
I
think
you
you
at
some
point
rejected
this.
B
These
request
changes
it
will
be
blocking,
but
it
would
be
still
good
to
like
if
you
want
to
double
check
some
items
but
yeah,
it's
pretty
big
change
and,
like
I
don't
think
we
should.
You
should
go
into
like
inner
details,
but.
C
A
Okay,
great
so
maybe
then
we
can
go
like
a
little
bit
deeper
with
the
weekly
updates.
So
you
can,
since
you
have
started
already,
maybe
you
can
okay.
B
So
the
biggest
change
that
we
did
to
unblock
it
is
to
wrap
near
evm
runner
behind
the
protocol
feature
evm.
Even
so,
it
was
an
optional
dependency
that
required
a
feature
to
to
be
active.
B
What
it's
called
interest
workspace?
Yes,
which
leaked
a
feature
of
interdependency;
workspace
which
affected
tests
of
and
compilation
of
other
crates,
so
that
created
conflicts
when
even
when
the
feature
was
off.
If
you
include
this
into
a
list
of
members,
so.
D
Can
I
ask
a
question
yeah
sure,
so
it
sounds
like
there's
like
some
of
the
features
got
a
little
bit
reworked
because
of
the
dependency
issue.
Does
that
mean
that
when
we
go
to
make
documentation,
is
it
still
just
protocol
feature
evm,
comma
nightly
protocol
features.
B
You
don't
need
product
of
features,
you
you
need
two
things
you
need
nightly.
Protocol
and
protocol
feature
evm
or
nightly.
Protocol
features
for
one
of
two.
D
A
Okay-
okay,
that's
great!
So
do
you
want,
do
you
want
to
have
like
some
kind
of
random
order
in
people
within
the
people
who
are
like
doing
the
the
updates?
What
do
you
think
or
like
it's
better
to
stick
with
with
one
specific.
B
A
Yeah,
okay,
so
I
can
do
it,
I
can
do
it
so
my
update
on
the
evm
is
pretty
it.
It
doesn't
have.
Actually
anything
mostly.
I
was
working
on
the
bridge
side.
I
was
trying
yeah
we're
doing
different
product
management
thing
was
doing
only
the
probably
a
couple
of
interviews
that
are
related
to
the
evm
yeah
and
mostly
was
was
present
on
the
calls.
E
Sure
yeah,
so,
let's
see
this
this
week,
I
switched
to
working
on
validation,
so
I
fixed
first
of
all,
the
crypto
zombies
test
which
have
been
failing
for
about
three
weeks.
It
turned
out
to
be
a
regression
introduced
in
the
beginning
of
november,
and
that's
that's
all
good.
Now
the
test
passes,
then
I
wrote
a
bunch
of
more
tests
for
the
evm
standard
pre-compact
contracts.
There
are
about
nine
three
compiles
in
istanbul.
E
There
will
be
more
in
berlin,
but
for
now
nine
they
are
useful
functions
for
hashing
and
cryptography
electric
curve
and
delight,
and
we
have
now
a
solidity
contract
that
exercises
all
of
those
pre-compiles,
and
I
submitted
the
pr
for
that-
that's
not
yet
merged.
If
maybe
you
could
have
a
look
today.
E
The
next
item
is
we
discussed
jason
jason,
rpc
endpoint
sync
with
chainsafe
peter
connected
me
with
aidan
today
at
chainsaws
and
I'm
hoping
to
have
a
call
with
him
before
thanksgiving,
I'm
also
working
on
extending
the
zombie
cryptozombies
test.
E
A
lot
of
people
will
be
will
be
trying
near
evm
with
something
like
crypto,
crypto
zombies,
and
if
we
can,
if
we
can
claim
that
we
support
the
whole
tutorial,
I
think
that'd
be
a
pretty
good
thing,
both
from
a
validation
viewpoint
as
well
as
just
you
know,
being
able
to
say
that
being
able
to
claim
that
also
as
the
lowest
priority,
I
have
a
local
checkout
of
the
documentation
and
I'm
working
on
adding
more
contributor
documentation,
which
probably
makes
sense.
E
Given
that
the
newest
team
member
and
you
know
I
have
to
figure
out
some
things,
the
hard
way
so
there's
some
some
things
that
should
go
in
the
documentation.
I
I
plan
to
send
a
pr
next
week
on
touch.
That's
how
they'll
pay
for
me.
C
C
It's
surprisingly
difficult,
that
you
make
this
part
comprised
under
that
part
of
workspace.not,
so
that
overall
it
will
take
like
three
or
four
days,
and
while
doing
this,
I,
as
we
discussed
last
week,
we
don't
need
a
uip
cell,
not
the
ip7,
but
we
do
not
need
decoding
the
function.
Parameters.
C
In
the
right
side
right
now,
we
only
need
to
pass
in
the
function,
the
the
input
arguments
of
evm
function
to
the
runner
and
did
not
do
any
like
parsing.
C
So
I
finalized
the
pr
to
do
the
I
easy
recover
and
the
manual
eip712
encoding
given
already
encoded
evm
args
and
the
resolve
conflicts
as
the
protocol
features.
The
the
major
pr
unblocked
protocol
features
so
that
so
the
uip712pr
can
also
pass
all
ci
tests
and
address
some
comments
from
youtube.
So
I
think
that
one
is
good
to
merge
now.
C
Not
many
not
many
other
things.
D
Made
some
minor
changes
to
near
web3
provider
pushed
a
recent
patch
version,
mostly
clean
up
and
removed
some
logging
and
been
focusing
on
getting
the
pet
shop
example
ready
for
people.
Basically
before
we
had
a
single
node.
D
That
was
a
google
cloud
platform
instance
and
so
like
have
to,
for
instance,
like
remove
those
settings
I
and
figure
out
how
to
keep
some
of
the
logic
that
I
think
is
worth
keeping
for
meta
transactions
when
they
eventually
come,
but
like
keep
the
logic
but
hide
it
in
the
interface
and
have
information
inside
the
code.
You
know
showing
people
that
they
can
try
this
out
if
they,
if
they
want
to,
and
then
there's
some
usability
issues
that
I'm
realizing
happen
with
wallet
that
I'm
going
to
be
fixing
for
pet
shop.
D
But
it's
basically
like
99
there.
I
have
the
pr
open.
Still
I
plan
to
probably
merge
that
today
I
can
post
it
in
our
channel,
but
it's
looking
good
and
still
need
a
lot
of
like
documentation
on
that
in
the
process
of
getting
ready
for
this.
I
also
let
some
internal
folks
know
that
I
believe
beta
net
was
kind
of
reset.
After
stake
wars-
and
that
means
you
it's
reset
reset,
so
you
can't
actually
create
accounts
on
it.
D
D
That's
that's
the
main
update.
I
spent
a
little
bit
of
time
yesterday,
looking
into
hard
hat,
which
is
the
new
biddler,
which
is
similar
to
truffle,
but
kind
of
an
improved
version
with
some
debugging
aspects
to
it
and
whatnot,
and
early
on
me
and
ilya
were
looking
at
a
few
projects
that
we're
using
biddler,
which
is
now
hard
hat,
and
I
think
it'd
be
really
great
to
go
back
to
those.
D
I
think
molech
is
one
of
them
because
now
there's
the
ability
to
plug
in
a
custom
provider,
and
that
wasn't
the
case
in
september
october,
when
we
were
talking
to
some
partners
so
there
there
may
be
a
lot
more
projects
that
we
can
run
tests
on
that
we
couldn't
a
couple
months
ago.
So
that
is
also
kind
of
something
I
want
to
mention.
That's
on
the
radar.
A
Is
this
a
tool
for
for
the
people
that
are
going
to
to
deploy
their
smart
contracts
in
our
evm
or
is
the
tool
for
us.
D
B
D
But
yes,
I
guess
there
will
be
presumably
a
migrate
function
inside
biddler
similar
to
truffle,
so
that.
A
E
Evm,
let
me
let
me
add
that
a
lot
of
people
are
switching
from
truffle
to
hard
hat.
So
just
in
terms
of
supporting
the
best
of
class
future
tooling,
it
makes
sense
to
emphasize
hard
hat
support.
D
Sure
yeah,
I
think-
and
I
were
talking
about
just
the
the
idea
of
like
having
some
kind
of
pet
peeve
days-
slash
like
maybe
two
or
three
days
a
month
to
address
some
tech
debt
and
also
just
kind
of
play
around
with
the
evm.
I
think
that
would
be
a
really
interesting
thing
for
this,
for
this
team
to
to
try
out.
So
if
we
can
talk
more
internally
about
that
in
our
other
calls,
but
that's
something
that
yeah
we
discussed
with
some
excitement.
D
Sure,
yeah
and
and
just
kind
of
have
a
little
bit
of
a
sandbox
time
to
grab
something.
Try
it
out.
If
we
see
something
that
kind
of
annoys
us
with
the
current
workflow
patch,
it.
A
Absolutely
yeah
well
from
my
point
of
view
yeah.
I
think
yes,
and
something
tells
me
that
eugene
is
going
also
to
vote
for
this,
taking
into
account
the
berry
club,
dot,
io.
B
A
A
Yeah,
okay,
any
additional
stuff.
A
So
I
think
that,
like
the
discussion,
the
decision
of
this
we
can
make
like
async
in
the
chat
but
like
I'm,
I'm
not
against
it.
At
least
at
least
me.
B
No,
I
think
it's
a
great
idea
think
I
actually
spent
every
friday
when
there
is
no
fire
to
to
actually
build
something.
A
Absolutely
yeah
look.
Actually
I
have
one
thing
to
discuss
so,
hopefully,
the
better
net
release
is
going
to
happen
next
week.
In
case
the
guys,
the
core
engineers
are
going
to
review
the
changes
pretty
fast.
A
Now.
What
is
our
next
thing
to
do?
What
do
we
expect
to
do?
It's
like
fixing
the
the
beta
net
and
trying
to
make
end-to-end
tests
work
in
there
or
what
it
is.
B
Yes,
I
think
the
next
goal
would
be
to
actually
do
some
benchmarks:
add
more
tests
and
end-to-end
tests
and
spam
examples
that
actually
use
an
idiom.
That's
tricky
because
of
potentially
frequent
forks
on
betternet
and
losing
state
possible,
but
it
shouldn't
be
a
big
deal.
A
B
A
D
See,
let's
do
it.
I
I
think
to
answer
your
question
too,
like
I
was
talking
to
ardo
about
this
a
bit
as
well
as
like.
We
have
some
tests
that
are
running
like
crypto,
zombies
and
and
whatnot,
which
is
cool
because
it's
like
you
know,
a
fun
example
picked
up
online.
It
may
be
worth
also
just
writing
straight
solidity.
Contracts
that
do
odd
things,
like
you
know,
do
do
an
assert.
Do
a
river.
Do
things
that
we
think
may
just
you
know,
find
the
edges
a
little
bit
better
than
the
crypto
zombies
thing.
D
So
that
would
be
something
that
may
be
interesting
to
do
is
first,
look
at
the
routes
that
we
need
to
still
implement
in
near
web3
provider
and
see
if
that
kind
of
gives
us
a
clue
on
what
things
in
solidity
may
have
issues
and
just
start
writing
contracts
that
will
find
those
edges
a
little
bit
easier.
E
B
Integration
side
is
near
like
that
the
account
has
the
proper
balances
and
stuff
like
this.
For
example,
one
tricky
part
that
you
do
is
you
can
issue
a
vehicle
which
has
a
deposit,
but
you
don't
need
to
attach
the
deposit.
You
just
say:
hey
my
vehicle
has
a
million
near
and
tvm
is
okay.
Business
like
it
just
attaches
this
balance
to
to
your
account
for
for
the
duration
of
vehicle.
B
E
E
B
Sounds
stuff
around
like
gas
limits
and
like
not
attaching
enough
gas
make
sure
we
handle
limits
properly
and
done
like,
for
example,
over
spend
gas,
which
is
okay,
but
we
just
need
to
be
properly
reporting
it.
So
there
is
no
deficit
on
how
much
you
attach
and
how
much
you
burnt
so
like.
If
you
report
that
you
burn
more,
then
it
will
panic,
you
need
to
make
sure
we
don't
face
any
of
this.
A
Okay,
okay,
yeah,
so
let
me
do
only
the
last
thing.
Let
me
check
that
that's
during
the
other
is
there
any
questions
here.