►
From YouTube: NEAR EVM Working Group Update [2020-10-09]
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
C
So
the
progress
this
week
is
figuring
out
how
ec
recover
works
for
eip
712,
and
I
didn't
realize
that
we
needed
to
use
basically
abi
dot,
encode
pact
and
I
got
a
got
a
javascript
version
of
that
working.
So
that
means
that
I
can,
I
can
figure
I
can
figure
out
who
the
address
is
based
on
that,
so
there
there's
also
the
relayer
that
was
set
up.
That's
a
very
simple
like
express,
js
app,
and
so
we're
going
to
be
sending
these
meta
transactions
to
the
relayer.
C
The
relayer
is
going
to
do
a
couple
of
things,
but
they
also
want
to
like
ensure
that
the
signature
is
valid
first
of
all
before
it
actually
wants
to
process
it,
and
I
think
it'll
make
sense
for
it
to
also
use
this
ec
recover
on
on
that.
So
the
relayer
is
live.
I've
pushed
up
the
or,
I
guess
live
by.
C
I
push
up
to
github
repo
on
that
I
ran
into
some
issues
with
truffle
contract,
so
I'm
now
using
web
3's
contract
class,
and
so
that's
going
okay
and
I'm
able
to
get
the
nonce
from
the
front
end
of
the
evm
account
id
on
the
near
uvm
so
that
that
is
actually
working
out.
I
had
some
issues
with
that
before,
so
what
I
need
to
do
next
is
a
couple
of
small
tasks
like
promisify
all
the
functions.
A
lot
of
the
stuff
works
with
callbacks
and
we'd.
C
C
I
think
like
as
we're
onboarding
and
as
I'm
doing
this
very
basic
example
we're
just
going
to
do
it
for
free.
You
know
for
the
pet
shop
kind
of
things,
but
we
want
to
build
this
in
right
now
saying
I'm
going
to
pay
through
a
fungible
token.
So
knowing
that
information,
I
need
to
change
a
little
bit
of
the
structure
and
how
I'm
doing
this.
C
I
was
basically
saying,
like
here's
the
amount,
here's
the
token
contract,
here's
the
dog
you're
adopting
and
then
I
think
something
else,
and
we
need
to
make
that
into
a
different
format.
It's
called
near
tx,
and
that
is
what
the
evm
is
expecting.
So
that
isn't
a
very
big
change,
but
that's
going
to
be,
I
need
to.
C
I
need
to
reformat
that
essentially
what
they're
going
to
be
signing
and
then
also
in
terms
of
the
re-layer
right
now
is
super
basic
as
I'm
understanding
this
it's
all
in
one
file,
including
like
the
routing
and
everything
so
need
to
make
that
much
more
robust,
possibly
use
typescript
all
that
stuff.
One
cons,
kind
of
concern
that
I
have
now
is
so
the
pet
shop.
The
way
it
works
is
once
you
finally
adopt
a
pet,
then
it
will
print
out
a
link
to
the
explorer
where
you
can
see
that
this
has
happened.
C
A
second
reason
why
we
really
need
this
is,
I
believe,
once
it's
reformatted
in
terms
of
the
gas
station
network.
We
want
a
user
to
be
able
to
say
I'm
gonna
use
metamask
to
adopt
this
pet
or
I'm
gonna
log
in
with
near
wallet
and
then
suddenly
you're
logged
in
it
can
see
like
okay,
if
they're
logged
into
near
then,
let's
just
send
it
directly
to
to
near
using
the
near
web3
provider.
If
they're
not
logged
in
then,
let's
you
know
kind
of
go
the
embedded
or
go
the
metamask
route.
C
So
that
also
means
that
we
need
what
wallet
set
up.
So
I'm
kind
of
stuck
on
like
how
far
away
are
we
from
all
right,
I'm
not
blocked
at
all
by
the
way,
but
I
I
am
kind
of
stuck
in
terms
of
like
figuring
out:
should
we
try
to
implement
wallet
and
explorer
and
the
indexer
on
the
gcp
node
or
just
like?
Are
we
at
the
finish
line
of
merging
some
of
this
stuff?
So
we
can
have
it
on
a
like
kind
of
a
live
network.
A
C
C
D
A
D
A
I
think
there
is
ambiguity
like
mike
might
want
it
just
to
see
some
transactions
not
like
he.
He
wanted
to
see
the
transactions
are
going
through.
I
think
that's
what
he
wanted
to
see
right
and
what
area
might
have
meant
is
that
you
know
you
have
a
parsed,
evm
transaction
with.
You
know
like
how
you
see
it
and
ether
scan.
D
Yeah
and
and
mike
a
quick
comment
to
the
to
the
g
to
the
g
sanji
san
actually
has
priya
like
I
have
read
through
the
post,
and
I
have
into
the
way
how
they
implemented
that,
just
because
it's
a
pretty
important
thing
for
the
meta
transactions
infrastructure.
How
to
how
to
implement
this.
So
I
believe
we
will
not
implement
everything
the
same
way
how
they
did
just
because
they
have
a
very
like
strong.
They
have
a
separate
contract
for
the
discovery
of
the
relays.
D
They
have
a
slashing
mechanism
for
the
relays
that
are
not
behaving
correctly
and
lots
of
additional
stuff.
I
do
not
think
that
we
are
going
to
implement
this
at
the
very
beginning,
just
because
it
is
a
pretty
good
decentralized
architecture,
but
let's,
let's
put
it
offline
and
discuss
with
you,
and
actually
I
just
wanted
to
mention.
You
probably
have
seen
mike
the
doc
that
I
can
post
on
on
the
meta
transactions.
D
A
B
Anybody,
no,
no,
I
think,
okay,
the
the
the
fixes,
I'm
still
pretty
sure,
you're
very
far
and
I'll
be.
I
would
prefer
to
to
run
this
network
for
like
a
few
months
before
going
to
magnet,
but
so
you'll
probably
need
a
new
change
of
preview
and
have
like
large
enough
bounty
to
break
it.
Some
people
can
try
to
like
break
abuse
it
before
we
can
merge
it
to
tomato
just
because.
B
A
B
B
B
So
so
we
can
leverage
community
that
is
kind
of
mad
and
actually
get
them
so
like
yeah
test
net
community
is
pretty
much
right
now,
so
so,
if
we
can
at
least
get
them
to
run
like
ibm
network
and
have
rewards
for
just
doing
it
like
something
just
for
being
a
validator
and
like
continuously
hitting
like
a
hard,
forks
and
stuff
like
that,
I
think
this
is
should
be
a
rollout
plan,
but
this
hard
fork
they
pretty
much,
will
preserve
the
state.
I
think
so.
B
B
We
can
have
some
side
effects
that
might
and
like
upgrades
that
we
do
to
not
be
a
protocol
change.
So,
for
example,
once
we
need
to
introduce
evm
in
vm
configuring
it
that
yeah
that
they
could
either
have
to
be
a
different
substructure
or
like
so
and
like
it
is
a
separate
branch,
at
least
at
the
beginning.
We
can
be
less
careful.
B
To
to
to
merge
faster
and
iterate
faster
versus,
like
my
net,
has
to
be
like
super
careful
like
so
maybe
yeah.
Maybe
we
can
start
to
separate
branch
and
eventually,
once
we
have
some
confidence
of
no
new
features,
configures
merge,
we
introduce
my
net
upgrade
to
to
introduce
new
fields
into
configs
and
like
and
then
hide
and
define
the
vlog
stuff
like
this.
A
There
is
also
one
blocker
from
evm
to
the
bridge,
which
is
contracts,
co,
the
token
transfer
from
ethereum
to
evm
directly,
I
mean
through
the
through
the
wasm
and
it's
a
blocker,
because
it
requires
code,
modifications
to
the
token
connectors
inside
the
bridge,
because
they're
going
to
be
hard
linked,
I
mean
stuff
that
you
deploy
inside
the
evm
token
connector
and
inside
wasn't
they're
going
to
be
hard
linked
to
each
other.
So
it's
like.
I
think
that
we
want
to
test.
A
You
know
with
the
bridge
yeah,
so
evm
is
kind
of
creating
dependency
here
for
the
bridge
and
if
you
say
you
want
to
run
it
for,
like,
let's
say
two
months
for
safety
and
before
we
launch
it
on
the
main
net.
That
means
we
need
to
have
it
ready
like
in
a
month
from
now,
which
means
we
need
to
iterate,
like
you're
iterating
with
ilia
right
now.
D
A
D
D
So
if
we
are
going
to
send
the
transaction
to
the
like
connector
part,
that
is
located
inside
the
evm
and
then
this
this
contract
is
calling
the
nav21
contract,
then
then,
obviously
this
is
this
is
something
or
out
or
another
thing.
If
we
would
like
to
send
an
ear
c20
to
the
contracts
which
is
nap
21,
then
this
is
a
direct
call
outside
of
it.
So
like
at
some
point
in
time.
D
B
D
Imagine
the
situation,
a
normal
use
user
that
is
used
to
use
evm,
so
he
has
like
his
dapps
migrated
to
the
near
evm
and
he's
signing
his
transactions
with
the
with
the
with
the
meta
mask.
So
what
he's
doing
is
actually
issuing
a
transfer
transaction
inside
of
the
near
evm,
and
this
somehow
needs
to
be
transferred
to
the
to
his
near
account.
D
B
D
D
B
The
problem
is,
the
problem
is,
evm
is
synchronous
and
it
will
have
to
complete
before
it
can
do
anything
outside
of
evm,
which
means
you
have
to
rely
on
logs
and
to
rely
on
logs.
You
need
to
either
re
layers
that
monitor
this
logs
from
evm
or
that
they
have
to
be
like
initiated
by
outside
of
evm.
That
will
receive
a
callback
on
the
completion
of
ibm.
A
There
is
some
weird
stuff
that
he
noticed
with
with
our
guest
counting.
Is
that
the
costs
in
in
near
gas
I
mean
or
like
cpu
instructions
when
you
deploy
a
solidity
contract
is
not
proportional
to
the
size
of
solid
contract
like
it's
all
over
the
place.
There
is
no
linear,
color
correlation.
It's
not
a
smooth
dependencies.
There's
some
weird
stuff
happening
in
there,
so
he
is
going
to
be
investigating
that
too.