►
From YouTube: NEAR EVM Working Group Update [2020-11-06]
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).
B
A
Okay,
great
well,
then,
let's,
let's
kick
off
hello,
everybody,
the
ones
that
are
on
the
call,
the
ones
that
are
listening
to
us.
So
this
is
another
evm
work
group
meeting,
a
weekly
group
meeting
and
let's
discuss
where
we
are
at
this
moment,
I'm
going
to
yeah.
It
is
hard
for
me
to
like
stream.
My
at
the
same
moment
change
take
a
look
at
the
view
and
and
and
change
the
the
markdown
file.
A
So
I'm
not
going
to
share
the
the
screen
since
also
after
after
the
call,
I'm
also
doing
some
some
changes
in
the
in
the
text
like
making
it
look
a
little
bit
better.
So
I'm
not
going
to
do
it,
let's,
let's
go
on
with
the
with
the
updates
and
what
what
is
happening
there.
A
So,
with
regards
to
the
action
point
list
from
the
last
time,
we
have
had
only
one
action
that
was
not
closed
and
it
was
action
for
me
to
loop
in
sandy
for
better
net
setup
and
deployment
of
evm
yeah.
I
did
it
and
now
we
have
a
chat
for
three
of
us
with
sandy
and
eugene
and
and
eugene.
A
So
so
there
were
several
questions
to
you
in
the
chat,
but
once
you
are
available
you
can
you
can
take
a
look
in
there
so
not
going
to
to
go
too
deep
into
this.
Let's
go
with
the
updates.
If
you
yeah
one
one
additional
thought.
As
you
know,
we
are
like
in
front
of
a
major
milestone,
which
is
the
better
net
release
and
yeah.
A
So
please,
please
take
a
deeper
look
into
into
what
you're
doing
with
regards
to
this
milestone,
because
obviously
we
would
like
to
to
make
it
faster
than
the
longer
from
now
and
it
seems
like
we
are
like
on
the
edge
of
this
of
this
moment
yeah.
So,
let's,
let's
go
with
the
updates
mike.
Do
you
have
anything
that
that
you
would
like
to
to
tell
to
us
sure.
C
Yeah
yeah
this
week
is
going
to
be
a
little
bit
short.
On
my
end,
I
am
waiting
for
some
upgradeability
to
happen
to
really
fill
out
the
tooling.
I
have
done
a
lot
of
like
health
work
on
all
the
different
various
pr's
and
made
sure
that
they
are
marked
as
draft
if
they're
not
to
be
reviewed
anymore.
As
soon
as
the
upgradability
is
done,
then
we
can
start
basically
merging
and
publishing
various
packages
and
so
that
we're
not
using
branches
upon
branches,
so
that
is
that
is
coming
up
pretty
soon.
C
The
only
other
thing
that
I
haven't
mentioned
on
this
meeting
is,
I
did
reach
out
to
like
an
oracle
system
about
the
possibility
of
price
feeds
like
inside
of
the
evm,
and
that
will
be
possible.
It's
kind
of
a
longer
conversation,
but
that's
the
only
other
thing
I
would
say
I've
been
I've
been
working
on
in
terms
of
edm
is.
A
C
I
I
think,
I
think
it's
fine,
it's
in
terms
of
a
chain
link
using
price
feeds
for
inside
the
evm,
which
sounds
like
that's
going
to
be
actually
an
easier
ask
than
than
otherwise
but
yeah
again.
That
that
part
is
sort
of
a
longer
conversation.
A
Mm-Hmm,
okay,
okay,
yeah
and
for
everybody
yeah,
as
you
know,
we
have.
We
have
a
separate
sinks
that
are
not
public.
So
this
couple
of
calls
that
we
have
during
the
week.
We
obviously
not.
We
need
to
a
little
bit
repeat
the
info
that
was
on
that
calls,
so
everyone
would
be
able
to
to
have
the
access
to
this
information
too.
So
keep
keep
that
in
mind.
So
so
your
today's
update
is
not
update
is
an
update
for
the
whole
week,
not
the
update
from
from
yesterday,
okay
bo.
A
Okay,
so
let
me
then
yeah
I
was
seeing
that
I
I'm
just
was
curious.
Maybe
he
was
was
able
to
join
us.
A
So
let
me
let
me
then
just
say
to
everybody:
what
is
the
update
of
bo,
so
he
finished
the
the
guest
price
pr
and
the
new
one,
which
is
the
to
bring
in
the
evm
the
gas
calculation
that
is
based
on
the
inputs,
so
so
the
the
can,
the
gas
costs
are
not
constant,
now
are
but
are
are
calculated
dynamically
depending
on
the
input.
A
This
pr
is
in
the
open
state
and
as
far
as
I
see
it,
so
it
needs
it
needs
to
be
reviewed
and
and
actually
fixed.
So
it
is
already
reviewed,
but
it
needs
to
be
fixed
and
he
also
started
an
additional
pull
request
on
the
parser
and
I'm
not
sure
who
eugene
are
you
able
to
comment
on
them
on
the
person?
Oh
okay,
I
got
it
so
this
is
not
complete,
yeah,
okay,
so
this
is.
A
A
B
I'm
doing
good
okay,
so
let
me
let
me
recap
the
previews.
I
delivered
the
upgrade
to
open
ethereum
268
this
week.
You
can
merge
that
last
night
and
that's
the
most
significant
upgrade,
because
that
gets
us
to
the
istanbul
hanfork.
B
B
You
know,
theoretically
able
to
run
all
contracts
without
throwing
an
invalid
or
code
error
and
encounter
these
newer
contracts,
and
I
completed
that
cross
reference
for
you
that
you
requested
on
which,
which
versions
of
solidity
compile
to
which
targets
yeah.
So
we
can
easily
tell
partners
that
that
we
can
support
what
they're
doing
and,
let's
see
I've.
B
I've
read
most
of
the
near
evm
runner
code
base
and
it's
about
four
four
thousand
lines
of
code,
and
so
that
I
understand
what
we
are
working
on
overall
and
now,
I'm
working
on
the
upgrade
to
open
ethereum
272,
which
is
the
last
of
the
two
point
x
series
and
that's
that's
important,
because
the
268
is
basically
a
beta
version.
They
call
the
whole
26
series
of
beta
beta
series
and
2
7
is
the
first
stable
version
after
that.
B
D
B
272
there's
some
there's
some
issues,
some
some
build
issues.
They
seem
to
have
to
do
with
the
primitive
types
crates
which
gives
us
the
128-bit,
256-bit
integers
and
I'm
figuring
those
out
it
seems
to
be
more
more
dependency,
depends
dependency,
management
and
and
feature
toggles.
That's
going
to
solve
that,
not
not
so
much
any
code
changes.
B
I
I
hope
to
to
wrap
that
up
for
one
day,
but
I'm
not
I'm
not
really
sure
what
the
reason
is
yet
so
can
take
longer
and
in
in
other
news
I'll
be
I'll
be
available
from
next
week.
Full-Time.
A
A
Just
just
trying
to
to
put
some
some
notes
on
this
okay.
So
what
what
additional
eugen
eugene
can
you
can
you
give
your
update
so
right.
D
So
upgraded
the
branch
rebase
the
branch
on
master
trying
to
get
fixed
from
both,
so
we
can
pass
ca.
There
was
like
a
dog
test
failing
because
it
cannot
find
the
vm
feature.
D
D
D
E
D
D
And
so.
E
I
thought
we
agreed
that
you
don't
need
to
do
the
upgrade.
No,
that's
that's.
D
D
I
think
once
basically,
I
pick
a
full
branch
and
we
should
be
able
to
compile
this
binary
around
it
against
the
baton
it,
but
maybe
there's
some
other
particle
version
that
is
not
picked
by
better.
Not
yet
so
the
idea
is,
I
want
to
be
able
to
verify
that
we
don't
leak,
features
by
running
to
embed
on
it
for
a
while
to
make
sure
it
syncs
correctly
and.
A
D
No,
this
is
not
a
blocker
like
the
biggest
blocker
before
we
can
merge
to
master,
is
actually
pricing
ci
and
make
sure
we
don't
affect
non
nightly
so
like
if
our
features
off,
we
didn't
change
any
logic
in
the
protocol.
So
that's
the
only
blocker
okay,
but.
D
A
A
Isn't
it
about
like
putting
some
some
configs
and
like
mark
in
that
you
need
to
enable
evm
feature
and
that's
it,
because
I
thought
that
that
this
is
the
only
thing
that
we
need
to
do.
D
No,
I
think,
need
to
modify
a
macro
that
we
use
for
nightly,
so
it
expects
a
key
to
be
present.
E
E
E
D
E
Yeah,
so
if
you
you
know,
if
you
just,
if
you
don't
need
to
to
to
do
the
things
differently
depending
on
the
protocol,
then
at
protocol
version,
then
I
mean
you,
don't
really
need
that.
I
mean
I
mean
you
will
eventually
need
it
right,
but.
D
E
Yeah,
so
so
my
I
think
I
would
suggest,
like
you
card
all
the
evm
code,
by
feature
as
much
as
much
as
possible.
So
I
think
the
ideally
you
don't
want
to
leak
anything
even
like
even
things
like
you
know,
introducing
new
structs
and
like
I
mean,
even
though
those
are
fine,
it's
like,
I
think,
still
a
better
practice
to
try
to
you
know
seal
them
under
the
features
so
that
we
don't
have
like
accidental,
like
use
of
you,
know
things
that
are
only
available.
D
D
A
D
D
To
make
sure
that
the
future
changes
to
vm
are
not
I'm
not
breaking
the
current
logic,
so
either
disable
the
script,
a
zombies
test
or
do
something
else
ideally
fix
it
just
need
to
figure
out.
B
D
B
B
C
A
D
Well,
but
it
depends,
it
depends
on
this
upgrade
so
like
they
don't
need
to
be
changed
once
once
you
introduce
this.
C
C
No,
so
I
so
I
haven't,
it
should
probably
be
small
changes.
I'm
guessing
that
there's
like
one
extra
argument
that
we
would
be
passing
or
something
of
getting
is
that
right,
just.
C
A
Okay,
sure,
okay,
okay,
then
great.
What
else
do
you
want
to
discuss
anyway?
Additional
questions,
evgeny
kapoon
thanks
for
joining?
Maybe
you
have
something
that
you
want
to
know
or
bowen
or
anybody.
B
C
I
have
one
like
tiny
question
and
this
is
something
that
maybe
eugene
max
and
bowen
know
immediately,
but
we
talked
about
having
this
being
kind
of
a
special
shard,
and
I
don't
know
what
that
looks
like.
But
I
just
want
to
make
sure
that
we
haven't
mentioned
that
in
a
little
while.
So
if
this
is
something
to
do
that's
easier
to
do
earlier
than
later
than
just
like
keep
track
of
that.
E
D
E
E
Well,
I
mean
it's
not
like.
Basically,
if
you
do
that
change
without
then,
basically,
we
already
enable
starting.
If
we
do
that
change,
because
you
just
have
two
shards
and
everyone
needs
to
track
and
then
like
it
does
have
some
implications
for
like
tunings
and
rpc
and
all
this
stuff,
and
we
need
to
make
sure
that
actually
that
all
works
properly,
so
that
can
also
take
some
time.
So
I
I
wouldn't
suggest
we
you
know,
do
that.
B
I've
created
a
nice
short
link
for
that.
I
just
put
it
in.
D
So
here
our
three
main
objectives,
so
we
want
to
launch
stable,
secure
nearer
vm
as
discussed,
and
it
should
be
up
on
par
with
ethereum,
vm
and
partners
with
existing
is
doesn't
work.
I
need
to
press
space,
doesn't
work
on
this
thing,
so
they
need
to
be
able
to
build,
deploy
and
use
near
evm.
D
A
D
D
Correctly
estimated
there
might
be
some
challenges
and
we
cannot
really
measure
the
discrepancy,
but
the
idea
is,
we
should
be
able
to
run
a
sustainable.
D
D
Attach
no
so
now
because
the
mapping
is
defined,
it's
not
like
we
can
both
evm
gas
is
predefined
by
ethereum
gas
metering
or
like
evm
metering.
So
we
don't
change
this.
D
We
only
change
the
way
we
now
take
their
gas,
a
kvm
gas
and
convert
it
to
near
gas
using
our
formulas
so
and
if
we
incorrectly
estimate
this
conversion
it
means
we
can
find
the
transaction
that
runs.
Gas
pays
less
near
gas,
but
executes
more
compute.
That's
supposed
to
do
so.
We
underestimate,
or
if
we
overestimate,
then
we
just
pull
from
tps,
so
it's
safer
to
overestimate,
but
at
the
same
time
deliver
gps.
A
D
Yeah,
this
metrics
are
okay.
I
mean
this
is
ambitious
to
have
90
percent
of
pass
coverage.
I
would
probably
change
this
from
past
to
entry
points.
Well,
I
think
I
would
say
hundred
percent
of
pdm
entry
point
cover
this
test,
so
this
means,
when
you
collect,
for
example,
function
call.
We
cover
this
test,
yeah,
okay,
so
this
is
here
then
possibly
caught.
D
D
Okay,
so,
finally,
around
some
recent
version
we
can
quantify
what
is
the
recent
version
yeah
our
traditional?
D
Okay,
so
this
is
done.
Meta
transaction
works
first
and
use
metamask.
A
I
believe
the
scope
is
not
yet
fixed
in
the
previous
one
because,
like
it
depends
on
whether
the
app
is
is
paying
for
the
relaying
of
the
transaction
or
not.
So
there
might
be
like
different
things
inside,
but.
D
A
D
D
D
So,
basically,
you
want
to
know
the
difference.
How
much
you
can
pull
on
the
air,
how
much
gas
it
costs
for
every
action
like
cursive
and,
if
token
uniform,
like
some
complicated
swaps
in
near
gas
and
a
result,
how
many
transactions
per
second
we
can
do
for
this
consider
and
we
can
sustain
loads.
So
we
not
over,
underestimate
guess.
A
D
So
well,
gps.
We
basically
want
to
have
a
minimum
target,
it's
not
about
performance.
Yet
on
this
quarter
we
can
do
optimization
for
performance
later,
but
we
just
need
to
make
sure
that
feature
wise.
We
can
achieve
this
and
how
much
it
costs-
and
this
is
basically
right-
and
this
is
saying
we
want
to
know
exactly.
D
Yeah
real,
basically
based
on
a
few
of
these
goals.
We
can
guard
this
particular
piece
that
we're
not
just
like
throwing
out,
because
we
need
to
achieve
performance
from
stable
and
secure
version.
First,.
A
A
So
near
cli,
api
gs,
and
so
I
put
that
all
of
them
need
to
support.
But.
D
At
the
same
time
like
how
much
support
of
this
so,
for
example,
nearby
tree
provider,
do
we
mark
them
as
comparing
them
to
on
par
with
web
3.js
or
what.
A
I
don't
know
because,
like
our
web,
3
provider
is
not
able
to
provide
all
of
the
functionality
of
the
ethereum
web3
provider,
because
some
of
the
things
are
just
absent,
the
other
things
are
present
and
and
we
need
to
to
have
new
new
methods
there,
so
yeah
so
the
scope.
It
would
be
hard
like
if
we're
not
going
too
deep
inside,
then
it
will
be
hard
to
to
express
it.
A
Sure
yeah,
I
think
that
this
is
something
that
is
given
to
us
in
the
in
the
objective
itself,
so
we
are
stating
that
the
objective
that
the
partners
needs
need
to
need
to
be
able
to
use
their
contracts
yeah.
So
this
is
our
like
general
benchmark,
whether
the
people
that
are
using
the
near
apiges
and
near
web3
provider.
A
They
are
like
going
to
us
and
say
and
constantly
that
something
is
not
working.
Then
probably
it
is
not
yet
there,
but
you
know,
putin
as
a
key
result.
I
don't
know
the
amount
of
the
amount
of
support
calls
stuff
like
that.
Well,
that
this
is,
I
don't
know.
Maybe
we
can
do
this,
but
it's
not
like
depicting
what
what
we
actually
want
to
achieve
right.
C
I
I
believe
is
that
going
to
disrupt
someone's
behavior
from
the
front
end
to
a
smart
contract,
probably
not
so
like
something
along
those
lines
like
an
app
can
can
perform
all
the
normal
functionality,
interacting
with
the
blockchain.
But
then
that's
still
a
little
bit.
D
So
we
didn't
talk
at
all
about
like
exploring
the
work
like
development
process.
Do
you
think
that,
like
debugging,
is
it
part
of
travel
building,
deploy,
process.
A
D
No,
no,
no,
I'm
more
like
in
terms
of
so
truffle
just
talks
about
like
just
you
should
be
able
to
run
tests
like
compile
and
run
tests.
D
Talk
about
like
how
would
you
actually
try
to
use
it?
Maybe
this
can
be
here,
visibility
to
debug
or
like
I
like
that,
because
you
want
to
be
able
to
actually
understand
what
happens.
So,
it's
not
just
like
okay,
failed
or
like
zero,
and
you
don't
know
success
or
failure.
A
D
D
So
we
marked
it
that
you
owning
it
here,
yeah
title,
so
that
should
be
fine,
so
this
is
on
me
right
now,
but
we'll
see
probably
bo
and
you
my
own
in
this,
I
I
can.
Basically,
I
think
bobo
works
on
a
rust
site.
So
I
don't
know
if
you
might
want
to
lead
this
effort
to,
and
you
pretty
much
own
in
three
of
this
okay
and
some
of
these
items
like
test
coverage.
I
think
I
can
ask
also
arthur,
like
just.
D
D
So
this
is
likely
gonna
be
bo
who
owned
this
item,
but
my
owning
this
part
on
on
your
cell
and
your
api,
just
kind
of
like
transferring
this
part
and
then
button
that
that
makes
sense
for
me
sustained
load.
This
is
going
to
be
blowing
me
on
well
on
gas
and
performance
and
finally,
benchmarking
ball.
I
think
that's
okay!
For
now,.
D
D
Well,
documentation
we
can
not
documentation,
but
so
documentation.
We
need
to
contribute
all
of
us,
and
tutorial
is
also.
Maybe
it's
on.
You
might
to
basically
explain
the
pattern.
For
example,.
C
Yeah
and
I'm
looking
at
this
now,
I
feel
like
these
are
things
that
I
could
definitely
start
working
on
next
week.
Even
if
there's
a
little
bit
of
a
delay
with
upgradeability
so
I'll,
keep
that
in.
A
D
Yeah
I
like
it
overall,
I
think
so,
test
coverage.
I
think
we
can
add
also.
D
D
A
Yeah,
it
looks
good
to
me
and
yeah.
The
only
thing
yeah
with
the
with
the
exception
of
I
don't
know
we're
not
covering
like
tons
of
different
small
things
that
we
need
to
do,
but
in
general,
in
the
in
the
in
the
release
checklist
the
the
long
list
of
the
different
stuff,
but
I
believe
we
might
not
put
in
this
inside.
So
we
just
put
here
only
the
big
stones.
D
D
D
D
A
D
Let's
not
say
we
actually
released
it,
but
we
schedule
it.
So,
even
if
you
don't
have
time
it's
a
good
goal
that
you
hit
yep
yeah.
B
E
A
All
right
thanks
everybody
thanks
for
reviewing
this
and
yeah
and
have.