►
From YouTube: NEAR EVM Working Group Update [2020-12-04]
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
A
Myself,
okay,
so
hello,
everybody!
This
is
a
weekly
update
on
the
evm
or
the
evm
work
group.
Sync,
and
today
we
are
going
to
discuss
what
is
the
status
of
the
evm
project.
What
what
is
our
position
and
what
we
have
done
within
this
week
and
discuss
a
little
bit
what
we
are
going
to
do
after
this?
So
so
eugene.
Can
you
give
us
like
an
update
about
the
current
status
and
the
current
goal.
C
Sure
so
we
released
we
merged
evm
branch
to
master
of
new
york,
their
small
issue
that
caused
by
this
branch
with
some
conflict
on
near
sdk
rs
due
to
one
of
the
dependencies
we
currently
trying
to
fix
it.
C
A
So
yeah
just
to
recall
to
everybody:
it
was
not
the
public
call,
but
you
can.
You
can
take
a
look
at
at
the
weekly
update
that
was
done
pretty
recently.
A
It
is
not
that
one
sorry,
so
you
can
go
here
that
was
done
a
couple
of
days
ago
and
you
will
see
lots
of
different
stuff
there,
so
we
are
going
to
update.
We
are
going
to
do
this.
Partly
this
update
is
going
to
intersect
with
that
one.
A
So,
with
regards
to
the
to
the
weekly
updates
arthur,
can
you
can
you
give
us
shows
overview
of
what
you
haven't
done.
A
Okay,
I
can
do
it
yeah.
So
since
last
since
okay-
that's
great,
let's
do
it
the
other
way.
So,
since
the
last
last
update,
I
was
doing
together
with
r2
actually
clean
up
in
github.
Now
for
probably
well
or
hopefully
for
many
people,
it
will
be
easier
to
navigate
through
through
the
evm
project.
A
So
if
you
will
open
the
in
the
near
organization,
you
will
be
able
to
see
projects
here
and
if
you
click
on
the
projects,
you
will
see
the
evm
projects
phase
two
phase
three,
and
if
you
will
go
to
phase
two
you'll
be
able
to
see
and
like
scroll
down
to
through
this
to
do
stuff.
Through
this
simple
stuff,
you
will
be
able
to
see
what
are
the
the
features
here.
A
All
of
them
are
marked
with
not
with
with
the
evm
tag,
and
you
will
see
you
will
be
able
to
see
that
they
are
actually
from
different
repos,
which
is
great.
So
there
is
a
near
core
repo
and
the
near
api
gas,
repo
and
stuff
like
that.
So
we
can.
We
can
work
with
this
and
we
can
track
this
progress
and
this
will
be
visible
to
to
our
community
and
a
big
thanks
to
arto
for
helping
me
cleaning
up
this
stuff.
A
So
that's
the
major
update
since
the
last
since
the
last
week
update.
D
So
I
suppose
we
we
are
doing
two
weeks
of
updates,
since
we
didn't
have
the
call
last
week.
Let
me
see
if
I
can
remember
so
far
back
yeah,
so
I
worked
on
the
crypto
zombies
test
suite
last
week
fleshed
that
out.
That's
that's
now
handed
over
to
frank
I'll
mention
that
soon
I
continued
work
on
integrating
chain
saves,
anemone
conformance
test
suite,
or
I
guess
I
should
mention
I.
I
began
work
on
that
last
week.
I
said
we
didn't
discuss
this
on
discussion
on
this
call
before
so.
D
That's
that's
a
conformance
test
suite
that
has
a
bunch
of
solidity
contracts
for
testing
opcodes
and
edge
cases
in
the
evm.
They've
apparently
found
it
very
useful
in
testing
other
evm
compatible
chains.
D
But
we
will
test
all
these
contracts
and
and
there's
a
bunch
of
them,
and
I
look
them
all
over
and
they
look,
they
look
pretty
good,
so
I'm
riding
the
the
test
runner
for
testing
exercising
each
and
every
one
of
those.
D
D
D
It's
all
recounted
in
issue
3665
on
dear
core,
so
we
began
with
20
failing
tests
and,
as
of
yesterday,
down
to
zero
failures,
discovered
that
the
very
last
failing
test
was
actually
a
genuine
bug
in
the
upstream
test,
suite
itself,
which
I
will
submit
as
a
bug
report,
and
I'm
happy
to
note
that
we
might
can,
I
fix
it
together
much
faster
than
either
one
of
us
could
have
done
separately,
so
very
good
collaboration
there.
D
D
I
submitted
some
related
updates
to
contributor
docs
for
near
core,
as
steve
frank
thinks
he
found
while
getting
set
up,
and
indeed,
as
alex
mentioned
today,
we
did
a
big
to
get
triage
and
and
clean
up
and
whatnot,
and
next
up
for
me
I'll,
be
taking
point
on
the
benchmarking
goals
and
secondary
support
to
both
mike
and
frank
as
needed.
C
A
Created
okay,
so
we
we
actually
did
not
create
a
an
an
issue
for
this,
so
yeah.
Okay,
we're
going
to
to
manage
this.
Okay,
great,
all
right,
great.
E
Sure
happy
too
yeah
I
just
just
got
started
this
week.
I
set
up
the
dev
environment,
submitted
one
small
pull
request
for
the
documentation,
and
basically
I
got
my
new
core
compiled
to
get
the
zombie
test
running
that
auto
already
brought,
and
I'm
now
ready
to
start
adding
more
tests
there
going
through
the
tommy
as
a
crypto
zombies,
tutorial
right
now
and
figuring
out
what
tests
I
could
add.
C
A
Thanks
and
welcome
to
to
our
organization
or
to
this
specific
project.
Thank
you
very
much.
Yeah
happy
that
you
have
joined
us
yeah,
I'm
glad
we're
here.
Okay,
so
I
completely,
we
completely
forgotten
bo
hi
bo.
How
was
your
life.
A
F
It's
great
to
get
back
and
see
many
things
get
unblocked
magically
like
it's
been
on
the
internet
and
balance
the
test
was
passing.
They
were.
These
were
two.
I
think
major
problems
when
two
weeks
ago.
A
Yeah
so
actually
bo.
I
wanted
to
just
a
quick
information
to
you.
I
would
like.
I
would
like
to
ask
you
to
take
a
look
at
some
of
the
pretty
old
issues
that
were
created
by
you,
so,
for
example,
here
evm
test
and
suite,
and
probably
one
of
the
maybe
some
of
the
others
ones.
So
we
just
do
not
want
to
yeah
and
this
one
it's
not
not
really
old.
But
can
you
take
a
look
at
this?
What
is
the
status
of
this
three
five?
A
Five
four,
so
we
just
wanted
to
understand.
What's
the
what's
the
status
of
this,
whether
it
has
a
duplicates
on
something
like
that.
F
A
Okay,
okay,
great
great
so
mike.
What's.
B
Up
yeah,
I
guess
covering
the
past
two
weeks:
it's
been
kind
of
reworking
pet
shop,
which
is
going
to
probably
be
the
first
actually
application
on
on
beta
net.
B
So
we
can
add
it
in
in
later
and
before
this
was
all
merged
to
beta
net.
I
realized
that
it
would
be
very
difficult
for
someone
to
even
review
this
pr
for
pet
shop,
seeing
as
with
this
new
workflow,
you
have
to
log
into
wallet,
and
there
was
no
network
at
all.
This
kind
of
led
me
down
a
path
of
something
that
I've
heard
from
the
community
in
terms
of
setting
up
a
local.
B
You
know
near
node
that
also
can
access
wallets
also,
can
access
explorer-
and
you
know,
there's
a
little
bit
of
setup
in
there
of
setting
up
postgres
databases
making
sure
that
ports
don't
collide
et
cetera,
so
that
that
is
something
that
I
am
going
to
include
in
the
in
the
pet
shop.
Read
me
is
how
to
set
up
the
entire
stack.
B
It's
a
little
bit
kind
of
dirty,
and
you
know
it's
not
like
a
dockerized,
pretty
thing
that
you
can
just
say
docker
compose
up,
but
I
know
that
there's
been
a
lot
of
folks.
Who've
been
asking
about
that.
So
that
is
a
little
bit
of
a
output
that
has
happened
from
this
evm
work
and,
as
ardo
explained
very
well,
we
had
the
issue
with
balancer
tests.
Failing
I,
I
do
think
that
part
of
that
is
a
little
bit
related
to
truffle
and
how
things
work.
B
But
that's
a
that's
a
long,
that's
a
longer
story.
We
look
forward
to
adding,
in
some
some
hard
hat
integrations
as
well,
so
that
we
may
not
run
into
the
same
kind
of
issues
that
we
had
had
with
with
balancer
learn
some
lessons
there
that
will
apply
to
other
projects
and,
lastly,
fix
some
some
issues
that
I've
seen
in
in
web3
provider.
B
In
terms
of
creating
test
accounts,
there
was
yeah
yeah
yeah.
There
were
some.
There
were
some
small
issues
having
to
deal
with
our
key
store
and
how
it
was
trying
to
create
accounts
and
not
counting
them
properly.
B
A
Yeah
yeah,
that's
great,
that's
great
anything
that
we
would
like
to
discuss
marks
any
questions
from
you
because
sometimes.
G
I'm
really
happy
that
this
app
is
getting
organized
as
projects
on
github,
because
github
is
very
friendly
to
the
open
source
community
people
know
how
to
use
it.
G
It's
not
yet
another
tool
thing
that
we
need
to
clarify
is
already
discussed
with
alex
rochamp
is
how
to
measure
velocity
of
individual
team
members
and
of
the
team
overall,
so
that
you
know
we
can
evaluate
and
also
you
know,
do
planning
accordingly,
the
problem
with
github
is
it
kind
of
doesn't
have
this
burn
down,
chart
and
story
points,
and
it's
hard
to
you
know,
compare
issues
when
you
have
one
issue
that
takes
like
three
weeks
versus
another
issue
that
takes
like
one
day.
G
Unless
you
read
the
description,
this
is
something
to
actually
bring
storm
on.
I
know
that
we
have
many
people
in
this
team
who
are
like
very
experienced
with
open
source,
and
I
would
be
like
very
interested
to
know,
for
instance,
opinions
of
arto
and
frank
on
how,
like
other
open
projects,
would
actually
measure
this
kind
of
things.
You
know
because
github
just
doesn't
have
this
features
like
how
would
you
even
go
with
creating
burnout
chart?
Let's
say
for
for
the
project
like
that:
do
you
guys
have
any
ideas.
D
I
I
have
to
say
that
all
the
projects
I
worked
on,
they
that
had
this
level
of
complexity,
they
used
jira,
it's
just
how
how
it's
been.
It's
not.
A
E
D
You
use
a
zen
hub
on
top
of
github
yeah
and
I'm
not
super
familiar
with
that,
but
I
I
I
have
glanced
at
it
in
the
past.
Does
that
help
you
to
what
you
need
to
do,
or
are
you
still
looking
for
something
on
top
of
that?
Well,.
G
I
I
would
like
you
as
a
team
to
decide
what
better
suits
you
as
a
tool
if
it's
zen
hub,
which
would
be
great
because
it's
kind
of
consistent
with
other
pro,
with
other
teams
that
are
working
in
here.
That
can
be
zen
hub.
But
if
jira
is
you
know
better,
then
maybe
it's
going
to
be
jira.
No!
No,
I
don't.
I
don't
think.
Hero
is
necessarily.
A
Yeah,
so
so
I'm
going
to
to
take
a
look
at
zenhub
here
because,
like
what
we
have
discussed
about
max
because,
as
you
can
see,
I
enabled
the
zenhub
extension
to
chrome
and
now,
for
example,
what
we
can
see
with
the
issues
is
the
story
points
that
are
attached
to
these
issues.
A
If
we
will
go
there,
we
also
can
see
that
there
is
like
there
is
an
estimate
here
and
like
and
lots
of
other
different
stuff,
which
is
not
common
to
the
plain
github
interface,
which
is
good
so
so,
and
it
still
sits
in
the
same
in
the
same
interface.
So
maybe
we
can.
You
can
see
here
the
main
net
guild,
which
is
like
we
probably
need
to
have
something
different,
which
is
called
the
workspace.
A
We
need
to
have
a
different
workspace
for
us,
so
let
me
play
with
it
during
the
next
week
and
if
everything
will
be
okay,
then
we
are
going
to
to
use
it,
and
hopefully
this
is
going
to
be
a
tool
for
for
the
managers
not
for
for
the
engineers,
because
everything
will
will
kept
will
be
kept
inside
of
github,
absolutely
the
same
way
how
it
is
right
now
yeah
that
sounds.
E
Good
cool
yeah.
I
think
it's
important
for
other
contributors
to
be
able
to
see
us
all
the
issues
and
stuff
like
that.
So
if
we
would
move
to
jira,
then
we
would
lose
the
visibility
there
again.
Yeah.
D
G
Yeah,
like
our
house
like
very
very
high
priority,
is
to
make
sure
stuff
what
we're
doing
is
open
to
the
community
and,
as
we
also
discussed,
you
know,
maybe
open
more
stuff-
that
we
discussed
in
slack
to
the
community
too.
For
this,
whatever
discord
or
maybe
discussions
in
a
github
actually
maybe
something
to
also
brainstorm
as
a
team.
C
Yeah,
I
think
it's
a
good
idea
actually
to
move
from
slack
to
edm
right
now.
We,
let's
basically
on
slack,
create
something
like
evm
secret
in
case.
We
need
to
discuss
something
in
private
and
you
will
always
think
like
hey.
Do
I
need
to
go
into
secret
mode
or
it
actually
should
be
just
a
regular
edm
channel
and
let's
move
to
discord
discord
has.
G
C
Interface,
you
don't
need
to
install
anything,
and
it
should
be
a
good
way
to
like
communicate.
It
has
somewhat
like
a
lacking
amount
of
threats
and
has
a
one
kind
of
line
with
replies,
but
it
should
be
sufficient
for
the
amount
of
people
we
have
and
like
discussions
that
we
usually
have.
They
don't
really
need
threads.
D
Go
ahead
no
girlfriend,
and
also,
of
course,
the
difference.
Maybe
in
any
case
should
we
should
be
formulated
as
github
issues,
for
example,
for
example.
One
good
good
example
is
3665
mics
and
my
investigation
into
the
balancer
tests
that
could
have
been
that
could
have
been
all
on
on
a
slack,
but
that
would
be
kind
of
wasted.
It's
now
it's
it's
recorded
for
posterity
and
I'm
sure
it
will
help
somebody
else
who
has
similar
problems.
C
A
Okay,
so
maybe
maybe
then,
if
if
everybody,
let's-
let's
do
the
following:
let's
let's
take
the
next
week
for
to
to
make
the
final
decision
and
then
if,
if
we're
going
to
decide
to
move
to
discord,
then
just
let's
do
it
starting
the
next
week?
Well,
not
not
the
beginning,
but
in
the
end
of
the
next
weekend
on
the
school
we
can
tell
to
everybody
that
we
are
doing
this.
A
D
D
There's
a
there's,
a
bunch
of
tickets,
on
that,
I
need
to
read
those
and
link
those
to
the
balance
of
issues
and
and
good
comment
comment
there.
So
I
just
wanted
to
mention
that
one
more
structural
error
issue.
G
I
think
the
status
of
structural
issues
is
that
it
has
been
implemented
in
the
near
core.
It's
like
a
very
old
pull
request
or
something
that
we
need
to
find.
The
problem
is
that
they
have
not.
We
haven't
written
like
javascript
adapters
for
the
near
iphs.
G
A
A
D
D
C
A
Okay,
eugene.
Can
you
also
create
a
github
issue
for
this?
Because
we
have
we
have
another
issue
but
like
the
bigger
one,
not
not
the
erc20
benchmark
but
like
the
big
one.
D
B
I
think
we
can
loop
in
danny
on
that.
I
was
talking
to
her
about
that.
A
bit
just
want
to
mention
that.
A
Okay,
so
seems
like
we
are
good.
Let's
let
us
can
somebody
take
a
look
at
at
youtube
whether
there
are
so
many
questions.
A
So
yeah
hello
to
everybody,
hello
to
mr
stark
proton,
we're
glad
that
you're
watching
us
so
yeah.
If
no
questions
thanks,
everybody
for
this
call
have
a
great
weekend
and
see
you
next
week,
bye.