►
From YouTube: NEAR EVM Working Group Update [2020-11-13]
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
Hello:
everybody,
hello,
hello,
guys,
hello,
everybody
who
is
watching
us
on
the
youtube,
it's
yet
another
weekly
update
of
the
evm
project
and
this
week
I
would
like
to
well
according
to
to
some
of
the
like,
in
order
to
make
this
course
a
little
bit
more
useful
for
our
community.
I
would
like
to
introduce
two
major
things.
So,
first
one
we
are
going
to
a
little
bit
restructure
the
way
how
we
are
discussing
things,
so
we
will
start
with
our
current
goals.
A
We'll
continue
with
the
with
our
like
progress
with
these
goals,
and
then
we
will
go
directly
to
the
discussion.
Who
was
doing
what
and
what
are
the
plans
and
what
are
the
blockers
and
like
the
usual
natural
scrum
stuff?
A
And
another
thing
that
I
would
like
to
do
is
to
move
these
discussions
into
the
better
feature
of
github,
which
is
discussions,
and
if
you
go
to
github
dot
com,
slash
near
slash
near
core
repo,
you
will
see
there
and
I'm
going
to
actually
I'm
going
to
share
the
screen
right
now
max
I
need
to
since
you're
the
host
now
I
need
to.
I
need
to
have
your
permission
today.
You
got
it
thanks
yeah,
so
you
can
see
here.
A
You
can
see
right
right
here
that
in
the
near
core
repo
there
is
the
thin
discussions.
So
this
is
a
better
function.
It
is
not
available
everywhere,
but
here
it
is
here,
and
I've
already
created
the
evm
category,
we're
going
to
put
the
information
there.
So
discussions
are
good
because
people
can
can
comment
on
different
things
there.
So,
for
example,
we
can
go
here
and
see
that
vlad
is
already
using
this.
In
order
to
fill
in
some
information,
people
can
react.
A
This
particular
discussion
is
not
that
intense,
but
some
others
are
so
the
community.
Well,
the
hypothesis
is
that
community
supports
this.
So,
let's,
let's,
let's
try
it
if,
if
it
is
because
of
some
reason
it's
not
working
for
us,
though,
I
believe
this
is
a
great,
a
great
way
how
to
how
to
structure
this
stuff.
Then
we
will
come
back
to
the
to
the
our
old
fashioned
thing
fill
in
the
information
in
into
one
markdown
file
into
the
community
rebel.
A
So,
let's
continue
and
let's,
let's
start
with
with
the
current
goal.
Obviously,
everyone
knows
that
our
current
goal
is
to
to
do
the
better
net
release
of
the
evm
support
so
and
yeah.
What's
what's
the
status
on
this
eugene,
are
you
able
to
comment
at
what
point
we
are.
B
A
tvm
release.
We
currently
merge
most
of
the
changes
that
we
need
for
the
release
into
the
branch,
but
we
trigger
some
weird
ci
bugs
around
features
conflicts.
So
one
of
them
is
around
nightly
protocol
and
with
rpc
test
they
basically
hit
two
conflicting
features.
So
one
one
pass
saying:
it's
not
nightly
protocol
another
pass
saying
it
is
nightly
protocol
and
the
version
is
like
42
and
that's
why
it
conflicts.
A
B
Well,
merchant
to
master
essentially
so
beyond
this
well,
we
will
need
to
merge
a
temporary
fix
for
meta
transaction
for
potential,
just
completely
disabling
them
before
merging
them,
because
it
has
an
overflow
and
bulb
range
is
not
fully
complete
to
be
merged.
A
B
B
We
also
yeah
it's
unclear
how
to
actually
do
this,
because
on
testnet
there's
some
account
on
this
evm,
but
it
has
keys
and
right
now
you
potentially
will
be
able
to
issue
transaction.
If
you
have
a
key
on
this,
given
account
so
yeah,
we
need
to
figure
this
out
on
mainnet.
It's
not
an
issue
and
that's
not
it's
an
issue
on
betternet
likely,
not
an
issue,
because
we
don't
have
vm
there
either
yeah.
B
I
don't
think
we
will
be
able
to
do
this
on
betternet
once
we
have
a
nightly,
because
it's
too
complicated
to
disable
one
feature
enable
another.
Maybe
it's
gonna
work,
but
after
merge,
it's
not
gonna
work
and
yeah.
So
if
testnet,
for
example,
survives
fine,
this
rpc
node
this
feature
disabled,
then
we
should
be
fine.
A
Okay,
okay,
great
nice
status-
hopefully
this
will
be
convenient
to
refer
to
for
our
community.
Let's
go
with
the
weekly
update.
If,
if
you
don't
mind
mike,
what's
your
status,
I
believe
you
were
like
mostly
blocked
by
different
stuff.
C
Yeah,
it
turns
out,
don't
think
I'm
blocked
anymore.
We
decided
to
do
the
upgrade
ability,
I
think
a
bit
differently,
and
so
the
only
breaking
change
was
essentially
for
call
and
view
arguments,
and
I
did
sort
of
confuse
myself
earlier.
I
had
a
sort
of
a
dumb
mistake
with
javascript
that
is
now
fixed
and
so
like
I
can
see
that
pet
shop
is
working
properly.
C
I
think
the
order
of
operations
are
now
for
me
to
go
ahead
and
start
like
making
sure
that
near
api
js
near
web3
provider,
near
cli
branches
can
be
merged,
and
then
we
can
the
and
then,
after
those
things,
we
can
start
working
on
getting
the
pet
shop
kind
of
cleaned
up
for
the
two
use
cases
that
we
identified.
Those
use
cases
are
like
using
wallets,
and
that
is
a
that
is
like
a
little
that's
going
to
be
easier.
C
When
we
have
this
on
betanet,
I
ran
into
a
little
bit
of
issues
setting
up
my
entire
local
environment
to
use
a
local
wallet,
and
then
you
know
a
local
contract
helper
local
explorer,
so
I'm
actually
have
a
meeting
later
so
that
that
will
get
ironed
out.
But
that's
not
really
blocking
the
progress
of
merging
the
pull
requests
that
we
really
need
to
to
get
for
this.
So
that's
my
priority
right.
B
C
After
those
are
kind
of
in
a
good
place
and
I've
bumped
all
the
people
that
need
to
be
bumped
for
the
prs
and
addressed
comments,
then
it'll
go
to
figuring
out
how
to
make
pet
shop
work
for
these
use
cases.
So
that's
on
my
plate.
A
Okay;
okay,
all
these,
the
the
prs
that
you
have
started
before
the
upgradability
discussion
started.
Is
this
correct?
Yes,
okay?
Okay,
great,
do
we
have
bo
with
this
with
us
yeah
bo?
Can
you
update
us
on
on
your
status.
D
Yeah,
so
the
most
important
update
is
making
this
making
no
to
make
make
sure
there
is
no
genesis
change,
even
when
protocol
feature
evm
is
enabled
so
that
there
won't
be
a
hard
fork
after
we
deploy
the
version
of
near
node
into
beta
net
and
that
apr
is
merged.
D
Another
another
api
is
about
taking.
D
Input
of
precompiled
functions
into
a
cost
estimator
and
the
deadlines
also
merge.
A
D
D
D
They
also
the
why
it
is
not
included
in
the
runner
is
because
we
we
are
lacking
the
way
to
generate
to
encoding
the
function,
arguments
from
the
input,
so
so
the
given
input
is
like
in
ilp
encoding,
and
we
need
to
deserialize
that
before
we
can
passing
this
to
the
working
eip712
encoding
function
for
the
entire
meta
transaction.
D
So
we
possibly
don't
do
a
meta
transaction
in
the
better
net
release,
but
that
can
be
done
quickly
and
we
probably
still
still
have
going
to
how
that.
A
Okay,
so
am
I
correct
yeah,
so
please
correct
me
if
I'm
wrong,
so
this
is,
this
part
is
on
the
on
on
the
protocol
site.
So
so
the
meta
transaction
is
signed
with
the
eip
712
from
the
metamask,
and
this
is
this
is
something
that
is
already
in
place.
This
is
something
that
is
working
because
of
the
because
of
the
metamask
is
is
a
support
in
this
feature,
and
now
we
need
to
decode
this
stuff,
and
and-
and
this
is
what
what
you're
talking
about
that
for
now-
it
is
not
yet
implemented.
A
D
Mostly
correct
for
the
decoding
we,
I
had
a
already
fixed
it.
So,
okay,
only
about
the
encoding
ueip712,
that's
missing
the
function,
arguments
encoding
if
you're
only
talking
about
decoding.
I
think
we
can
merge
one
of
my
pr
and
that
already
have
like
erp
712
decoding
and
the
easy
recovery
part
fixed.
A
Okay,
but
why
do
we
need
inco
encoding
in
in
this
format,
on
on
the
protocol
side?.
A
D
A
Okay,
fair
enough
fair
enough
eugene
do
we
have
any
other
utility
for
for
this
are
rather
than
tests.
A
Sure,
okay,
let's,
let's
figure
out
this,
maybe
during
the
next
week-
maybe
we
will
not
just
implement
this,
and
maybe
we
do
not
need
to
have
since
the
decoding
part
is
implemented.
Maybe
we
do
not
need
to
to
do
the
fix
for
the
for
the
metal
transactions.
Okay
bo.
Are
you
finished
with
your
update,
yeah?
E
Sure
thing
so
this
was
a
strange
week.
I
began
working
on
the
the
upgrade
continuing
from
last
week
when
we
upgraded
to
268,
and
then
we
got
a
curveball
thrown
at
us.
This
was
prompted
by
ilia
poking
the
open
ethereum
team
when
we
discovered
that
they
had
been
working
in
another
repository,
instead
of
the
main
one
on
a
release,
310
that
we
didn't
know
anything
about.
E
So
that
would
be
fine,
except
that
it
turns
out
that
three,
three
one,
the
three
one
branches
forked
from
parity
ethereum,
two
point:
five:
they
they
maintained
that
this
is
because
in
parity,
two
six
beta
branch
that
we're
still
on
we
were
still
on
yesterday
and
the
two
seven
stable
branch
there
were
disc
and
memory
issues
introduced
that
they
wanted
to
avoid,
and
the
changes
were
too
big
to
take
them
out.
E
So
instead
they
they
went
back
to
two
five.
Four
credits
are
three
one,
and
that
means
that
our
original
goal
of
upgrading
to
3-0
is
is
a
dead
end.
They're
not
going
to
maintain
3-0
at
all,
so
there's
no
sense
to
upgrade
to
3-0
so
given,
given
that
I
switched
to
to
deep
dive
to
this
3-1
version,
seeing
that
it
had
what
we
needed
and
it
does,
it
does
have
the
istanbul
support
and
it
has.
D
E
However,
as
we
discussed
on
our
on
our
earlier
call
this
week,
it
would
be
pretty
risky
to
to
jump
on
board
of
our
open,
ethereum
31
right
now,
as
in
it's
a
basically
a
new
code
base
by
a
new
team,
it
doesn't
have
any
real
world
use
it.
It
would
just
be
too
risky,
so
we
decided
that
we're
going
to
keep
to
we're
gonna
finish
the
upgrade
to
272,
which
we
have
done
as
of
yesterday.
E
That's
that's
merged
as
of
yesterday
and
that's
the
last
parity
ethereum
version.
After
that,
the
open,
ethereum
guys
took
over
and
that's
a
fairly
given
that
it's
the
last
release
of
parity.
It's
it's
a
fairly
widely
used.
I
don't
know
the
percentages,
I
meant
to
look
them
up,
but
forgot,
but
certainly
there's
a
lot
of
real-world
deployment
of
it,
and
you
know
it's
it's
it's
the
best
option
right
now,
we'll
have
to
consider
very
soon,
as
in
probably
the
january
time
frame.
E
What
we're
gonna
do
most
likely
we'll
have
to
upgrade
to
three
three
one,
but
hopefully
others
will
beat
on
it
before
we
have
to
do
that.
Otherwise,
maybe
we
stay
on
two
seven
and
backboard
some
of
the
berlin
hard
fork
stuff.
The
hard
fork
is
coming
in
january,
and
speaking
of
that
today
was
the
ethereum
core
developers
meeting
number
100.
E
I
listened
in
on
that
via
youtube,
and
I
will
summarize
briefly
I
I
plan
to
attend
on
our
behalf
all
of
these
going
forward
to
know
what's
coming.
They
talked
mostly
about
the
new
block
and
transaction
format
coming
into
berlin,
hard
fork
about
account
abstraction
and
the
unfortunate
incident
of
the
infra
chain
split
this
week.
So
there
wasn't
too
much
relevant
detail
on
this
call.
For
us,
there
was
more
on
the
previous
call.
E
The
open,
ethereum
team
did
reporting
and
they
they
did
say
that
they
are
basically
ready
for
yolo
v2,
the
ephemeral
distance.
So
that's
about
the
evm,
given
that
we
we
are
on
272,
and
this
now
no
obvious
upgrade
right
now.
That
makes
sense.
I
switched
over
to
working
on
validation
and
right
now,
I'm
working
to
fix
the
crypto
zombies
test.
I
ticketed
that
that's
hold
on.
Let
me
paste
the
links
here,
that's
ticket
3611
and
I'm
digging
digging
into
it
to
to
find
the
root
cause.
E
I
have
the
approximate
course
as
in
we
are
calling.
We
are
calling
a
a
function
in
the
contract
which
returns
surprisingly
zero
length
response
and
our
test
bales
on
that,
so
I'm
figuring
out
why
that's
happening
and
I
hope
to
resolve
that
at
the
beginning
of
the
week.
Let's
just
I
think,
that's
pretty
much
my
update,
I'm
I'm
I'm
going
to
need
something
else
in
the
validation
realm
after
the
crypto
zombies
is
fixed.
E
A
Yeah
yeah
it
is,
it
is
public
already
I'm
going
to
put
here
in
the
discussions.
Also
some
some
kind
of
just
one
separate
discussion
with
some
major
outline
goals
and
stuff
like
that:
okay,
eugene,
your
update.
B
Okay,
so
this
week
I
spent
mostly
emerging
branches
and
fixing
tests.
B
B
B
So
that
for
evm
we
added
some
changes
to
estimate
gas
in
the
config
in
param
estimator.
It
was
not
guarded
by
features
internally,
so
so
that
param
estimator
expected
the
feature
to
be
on
by
default,
which
is
probably
okay,
because
it's
not
part
of
master,
but
it
might
start
to
affect
the
rest
of
the
stuff.
If
you
run
it
and
don't
expect
the
game
to
be
there.
B
B
B
A
A
So
for
for
the
evm,
I
was
preparing
the
the
set
of
tags
that
will
go
directly
into
into
the
business
development
department
and
they
will
create
out
of
it
a
test,
a
form
that
our
partners
are
going
to
submit.
Using
this
form,
we
would
be
able
to
collect
some
statistics
on
what
features
are
requested
and
what
not
so,
for
example,
like
the
need
for
the
for
the
hard
fork
support
stuff
like
that
yeah.
A
Let
us
let
me
take
a
look
at
at
the
the
youtube
channel.
So
potentially
we
have
some
some
people
who
are
watching
us
and.
A
A
Yeah
they
these
sessions
are
public.
We
potentially
can
market
this.
Once
again,
I
mean
put
some
links
into
the
official
communication
channels,
but
in
general
these
are
the
these
are
like
public.
So.
F
F
So
what
we
should
do,
like
like
every
tl
and
alex
fuschenko,
should
learn
how
to
use
restream,
which
automatically
will
broadcast
it
not
only
on
our
youtube
channel,
but
on
our
twitter
and
and
there
people
are
have
better
chances
to
notice
it,
and
then
we
should
also
communicate
with
marketing
and
denny
on
whether
they
want
to
like
maybe
have
a
scheduled
link
in
advance
so
that
they
can
market
it
and
not
just
like
have
a
five
second
ahead
of
time
notification
yeah.
B
A
Okay,
let
let
me
work
with
ash
on
this,
maybe
maybe
they
will
and
and
marketing
team.
Maybe
they
will
will
come
up
with
with
a
good
solution
for
this.
E
B
A
B
E
B
B
Okay,
thanks.
A
Everyone
yeah
yeah.
This
means
that
we
have
closed
all
of
the
things
already
thanks.
Everybody
take
a
look
at
how
discussions
are
go.
Look
like
on
the
github,
we'll
do
awesome
all
right.