►
From YouTube: All Wallet Dev #12
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
Yeah
so
I'm
just
going
to
jump
into
a
demo
of
wallet,
test
framework,
Nikki
and
I
have
been
building
this
for
a
couple
weeks
now
and
yeah.
We'll
just
just
want
to
show
you
where
we're
at
so,
let's
see
if
this
works
window.
A
All
right
is
that
is
that
working.
A
Okay,
so,
as
you
can
probably
tell
neither
of
us
are
front-end
developers,
so
if
anybody
wants
to
come
along
and
make
this
look,
like
you
know,
a
real
application
that
might
be
nice,
but
it
works.
So
this
is
kind
of
the
the
layout
of
the
the
testing
application
on
the
left.
We
have
the
test
results
that
uses
mocha
in
the
middle.
We
have
a
section
to
input,
events
that
your
wallet
is
displayed
and
then
on
the
right.
A
We
have
instructions
for
the
user
to
follow
to
you
know,
interact
with
prompts
in
the
wallet,
so
this
is
called
the
manual
glue
and
the
idea
is
that
down
the
road,
each
wallet
can
Implement
their
own
automated
glue,
so
you
don't
have
to
type
this
stuff
manually,
but
for
now
it's
manual
so
right
now
we
have
a
add
a
3M
chain
request.
So
you
click
the
add,
ethereum
chain
request
button
and
you
fill
it
out.
So
this
is
four
five:
nine
five
zero.
It
is
named
this.
A
B
I
see
and
that's
the
idea
here
is
this-
is
your:
it
will
verify
that's
what
it.
A
A
There
so
no
idea
what
happened
there,
definitely
something
to
look
into,
but
on
the
left
we
have
our
results,
so
this
is
actually
going
through
and
running
against,
mocha
in
the
background
or
sorry
against
ganache.
In
the
background
and
yeah,
the
requests
are
proxied
from
metamask
or
from
the
DAP
this
page
into
metamask
through
a
back-end
server,
that's
running
on
Heroku
right
now
and
then
back
into
this
webpage
back
into
this
web
page.
So
there's
no
surface-side
component
really
no
well
at
least
no
no
heavy
processing
on
the
server.
A
A
So
that's
about
it
on
wallet
test
framework,
any
any
questions
yeah
go
for
it.
A
So,
let's
start
with
Bumble
fudge:
if
you
have
your
hand
up
there.
D
I'm
wondering
when
you're
making
those
calls
which
I
are
you
comparing
them
against
some
outputs
that
you
expect,
and
you
have
some
kind
of
documentation,
that
what
is
what
you
are
like
expecting.
Please
is
I.
Think
for
some
of
those
costs.
The
different
ethereum
nodes
are
producing
bit
different
outputs
and
I
was
wondering
what
is
the
correct
one.
A
So
we
are
testing
against
ganache,
so
whatever
ganache
outputs
is
considered
the
correct
output,
but
if
there's
ever
any
ambiguity
so
far,
we've
tested
frame,
wallet
and
metamask
and
so
far
they
handle
ganache
fairly
well.
But
if
there's
ever
ever
any
ambiguity,
we'll
we'll
bring
it
up
in
the
channel
to
figure
out
what
the
correct
thing
is:
I.
A
Okay,
so
would
you
I
guess
the
the
option
there
would
be
to
specify
a
different
test
change
or
run
against.
D
A
Yeah,
we
can
definitely
look
into
that
right
now.
I
think
we're
just
looking
for
some
kind
of
a
test
suite
and
we
aren't
experts
in
you-
know
node,
RPC
or
in
how
wallets
are
supposed
to
handle
these
things,
so
we're
just
going
with
the
one
implementation.
But
if,
if
there
is
a
comprehensive
dog
like
Doc
or
spec
on
this
stuff
or
somebody
writes
one,
we
will
absolutely
follow
it.
C
B
C
Was
gonna
I
was
just
gonna
say
that
I
I?
If,
if
your
question
is
about
the
like
ethereum
execution,
API
like
what
the
node
should
return
for
each
function,
I
I
think
that
the
place
to
look
like
that
there
is
a
group
in
ethereum
land
working
on
this
and
it's
the
the
open,
RPC
guys
and
I
think
there
are
a
few
little
discrepancies
like
different
maximum
values
or
one
returns
a
float.
One
returns
an
integer,
those
little
things
like
I.
C
If
that's,
what
you're
asking
about
I
would
say,
maybe
figure
out
who
those
people
are
I
only
have
one
name
and
I'd
have
to
look
it
up.
I,
don't
know,
I
can't
remember
off
the
top
of
my
head,
but
it,
but
it
sounds
like
maybe
you're
talking
about
a
different
discrepancy
or
or
standard.
E
D
Request,
if
you
make
RPS,
he
requests
to
different
notes.
They
are
returning
a
bit
differently
and
then,
when
you're
making
also
some
of
the
wallet
calls.
They
also
kind
of
even
wanted
to
be
a
bit
differently,
and
some
documentations
also
say
about
some
things.
But
then
that
must
behave
differently.
For
example,.
C
C
Api
open,
RPC
people
about
little
discrepancies
between
like
how
it's
written
in
the
EIP
and
how
metamask
handles
the
wallet
namespace
functions,
but
the
node
functions
I
think
there's
no
one
else
to
coordinate
with,
like
the
the
the
the
go
team
and
and
the
different
node
teams
are
already
pretty
closely.
You
know
aware
of
these
discrepancies
and
working
on
them.
As
far
as
I
know,
I
can't
speak
for
work
I'm
not
doing,
but.
C
Oh,
no
sorry,
the
I
shared
the
link
in
the
jitsi
chat
to
oh
wait.
No,
that's
the
playground,
but
I'll
try
to
find
it
on
GitHub
somewhere.
There's
the
there's
a
giant.
You
know
it's
like
a
sorry,
I
I
bet,
I'll
leave
for
two
months:
I,
don't
remember
any
proper
names
or
technical
terms.
They
there's
like
a
like
a
Swagger
dock
for
the
execution
apis.
B
A
So
I
guess
to
to
specifically
answer
your
question
from
earlier.
If
someone
gives
us
an
authoritative
spec
that
we
can
verify
against,
we
will
use
that.
A
So
because
of
the
way
that
the
tests
work,
where
you
know
you
have
to
generate
a
block
on
demand
or
or
those
kind
of
things,
it
won't
run
on
maintenance
and
it
does
use
the
like
back-end
RPC.
That
ganache
supports
for
like
minor
block
now,
or
you
know,
transfer
funds
from
this
account
to
that
account
so
that
that
is
using
the
gadash
back
end,
but
any
any
API
provider
that
supports
that
additional
back,
like
RPC
endpoints,
will
work.
A
Yeah
Victor,
that's
kind
of
yeah,
exactly
yeah,
whoever
just
raised
their
hand.
I
can't
see
your
name.
F
A
Oh
yeah,
it's
just-
we
haven't
written
them
yet
so
yeah.
So
we
just
finished
the
glue
about
two
weeks
ago.
So
now
we
can
actually
you
know
pop
up
dialogues
and
stuff.
So
now
we
can
start
writing
interactive
tasks.
Tests
like
let's
say,
sign
message
or
send
transaction.
A
A
All
right,
so
if
there
aren't
any
other
comments
or
questions
on
wallet,
test
framework,
I'd
like
to
mention
Eep
6963,
that's
the
Pedro's
proposal
for
a
new
wallet,
Discovery
mechanism.
If
Pedro
is
here
and
they'd
like
to
talk
about
it,
please
do
if
not
links
in
the
Discord
and
you
can
follow
along
there.
C
All
right,
I,
don't
see.
Pedro
I
know
that
this
is
a
hard
time
for
him
in
his
time
zone.
If
he's
back
home
but
yeah
I
have
worked
with
him
on
it
a
little
bit
so
I
I
could
maybe
answer
a
few
very
easy
questions
on
his
behalf.
Laughs.
C
Your
your
overview
would
probably
be
better
aforementioned
month
into
leave.
Don't
remember
anything.
A
Yeah
so,
instead
of
injecting
window.otherium
into
every
page,
this
uses
an
event
style
interface
on
the
window,
object
to
inform
the
application
that
wallets
exist.
A
It
still
requires
injecting
into
the
page,
but
it
does
support
multiple
wallet
providers.
So
that's
definitely
an
improvement.
That's
about
all
I
know
about
it.
So
definitely
take
a
look
at
eip6963.
If
you're
curious.
C
Yeah
I
would
I
would
maybe
add
that
the
the
main
problem
this
solves
is
different,
while
it's
overwriting
or
race,
conditioning
for
the
windowed
out
ethereum,
like
it,
the
the
sort
of
lack
of
a
namespace
to
allow
multiple
to
coexist,
I
think
was
the
driver
and
there's
a
a
couple.
Other
there's
like
a
a
an
older,
not
much
older.
A
few
months,
older
EIP
by
the
second
author
listed
I.
Don't
know
how
to
pronounce
this
as
his
or
her
name,
but
I.
C
Think
it's
kasala,
himachandra,
there's
a
I
can't
remember
the
number
outside
my
head,
but
I'll.
Look
it
up
and
put
it
in
the
chat
yeah
exactly
from
encrypt,
so
this
and
that
are
similar,
so
yeah
exactly
thanks
everyone
so
that
had
a
few
little
differences
and
there's
been
a
big
group
chat
for
a
few
months.
Hashing
them
out
and
I.
C
Think
kasala
wanted
to
co-author
this
one
because
they
have
a
lot
in
common
and
it's
sort
of
a
let's
propose
both
and
see
what
the
market
prefers
kind
of
thing.
So
yeah,
that's
Maybe,
useful
context
for
people
just
hearing
about
it.
Now
I'll
I'll
get
some
links
going
here.
A
Great
thanks
so
much
I
think
that's
a
great
segue
into
the
next
topic
here,
which
is
shadow
or
draft
pre-draft
EIP
7039,
which
is
using
a
custom
scheme
handlers
to
accomplish
the
exact
same
thing
as
6963
Link
in
the
agenda.
I've
been
talking
about
this
for
a
while.
If
you
aren't
aware
of
the
upsides
and
downsides
of
this
proposal,
let
me
know
now,
but
it's
very,
very
similar
just
uses
a
slightly
different
method
to
connect
to
to
wallets
yeah.
A
This
is
I,
just
put
it
up
earlier
today,
so
it's
pull
request:
7039,
thanks,
yeah
and,
and
it
uses
register
protocol
Handler
API.
A
So
the
same
thing
that
lets
websites
handle
mail
to
links
and
they
manager
that
is,
it
uses
the
browser's
native
UI
for
choosing
between
wallets.
It
leaks
very
little
information.
If
you
don't
approve
a
connection,
you
can't
even
tell
a
wallet
is
installed
and
web
extensions.
There's
no
additional
permissions
required
Beyond.
A
Yes,
on
Chrome,
it's
it
only
so
like
there's,
no
easy,
UI.
A
D
B
A
We
figured
this
out
so
if
a
desktop
app
hosts
a
page
on
localhost
so
like
the
the
app
has
a
button,
you
click
on
and
then
it
opens
a
page
in
in
your
browser.
You
can
click
a
button
there
to
register
a
protocol.
Handler
that
uses
the
native
application.
B
A
B
A
A
It
wouldn't
yeah,
so
a
mobile
wallet.
Could
you
like
you?
You
could
go
to.
Let's
say
you
know
my
wallet.com
click
a
button
and
it
would
register
my
wallet.com
as
a
Handler
and
then
proxy
to
your
mobile
wallet
but
yeah.
It's
not
exactly
smooth.
A
D
F
Thought
process
and
like
some
of
the
advantages
that
that
it
might
have
over
69
63.
A
So
wallets
no
longer
have
to
inject
like
any
content
scripts
into
the
page.
They
require
no
permission
to
to
view
or
modify
Pages,
which
I
think
is
a
huge
Plus
for
me
on
scene
browsers.
It
supports
multiple
wallets
at
the
same
time
and
on
last
scene
wallets
like
Chrome.
A
It's
not
hard
to
implement
a
dialog
that
lets
you
choose
between
the
two
handlers,
so
that
I
think
has
an
equally
likely
chance.
It's
externally
connectable
and
it's
a
whole
other
story,
but
suffice
it
to
say
it's
not
impossible
to
get
this
feature
into
Chrome
pretty
easily.
A
It
works
fairly
well
for
mobile
and
desktop
wallets
as
well.
F
B
B
A
C
But
by
by
the
scheme,
do
you
you
mean,
like
the
the
syntax
of
the
Uris?
That
would
start
with
I.
Don't
know
a
theory
of
colon
slash
slash.
Is
that
what
exactly.
A
B
A
B
A
But
yeah
we
like,
we
can
choose
anything
I,
don't
care.
Web3
is
technically
registered
as
a
Ina
scheme
that
we
could
use.
We
could
also
go
and
register
ethereum
I,
don't
care
I.
Remember
somebody
objected
to
ethereum
because
this
also
works
for
optimism
and
other
chains,
so
I
just
went
with
evm
but
yeah.
It's
really
just
bike
shedding.
A
B
E
A
I've
learned
a
lot
of
typescript
in
JavaScript
since
then,
so
forgive
how
absolutely
terrible
they
are.
D
A
E
Yeah
I
was
waiting
if
someone
want
to
speak
about
other
things,
but
yeah.
Thank
you.
Thanks
Sam
for
the
opportunity
just
want
to
quickly
share,
there's
a
new
initiative
that
we're
trying
to
bring
up,
which
is
called
ERC
deaf.
E
This
is
a
web
play
of
all
core
deaf
or
a
lot
of
deaf
thanks
for
all
the
predecessors,
and
we
want
to
bring
this
period
where
they
lack
the
a
place
for
ERC
authors
and
developers
to
come
together
and
discuss,
and
hence
this
is
a
way
to
do
it.
Of
course,
you
can
do
forums
but
having
a
synchronized
way.
You
can
be
more
efficient.
E
We
just
run
yesterday
and
we're
trying
to
have
one
session
and
it
was
great
to
ERC
authors
come
and
share,
and
then
other
people
give
feedback
and
and
what's
particularly
relevant
to
this
group
I
think
is
that
most
wallets
are
meant
to
be
used
for
assigning
content
transactions
and
interact
with
small
contracts.
So
if
you
want
to
give
get
to
know,
what's
latest
updates
and
ERC
authoring
and
drafts
come
and
learn
about
it,
and
we
definitely
appreciate
your
feedback
and
comments
and
Technical
reviews
from
your
perspective.
E
As
audit
as
well
at
deaf
so
come
here,
I
will
share
the
link
and
wish
to
have
to
see
you
here
as
well.
Thanks
for
the
opportunity
to
bring
this
before
you.
A
And
speaking
as
an
EIP
editor
I
very
much
appreciate
somebody
trying
to
coordinate
the
all
those
cats
that
need
hurting.
E
Yeah
and
wish
that
becomes
a
way
to
even
boost
the
effort
that
you're
putting
forward
for
for
the
work
group
or
rings
of
peer
reviews.
E
Yeah
I
was
I
heard
someone
proposing
yeah
ERC
eips
that
helped
detecting
wallets
I
am
also
I
think
it
would
be
your
interest
to
see
this
efforts
trying
to
have
a
modernized,
a
better
way
to
detect
an
erc's
before
that.
You
probably
know
that
there's
EIP
155,
but
as
we
learned
that
that
is
very
limited,
so
I'm
trying
to
put
up
a
new
standard
which
is
called
erc5269,
trying
to
detect
and
discover
ercs
by
emitting
proper
events
and
then
make
new
assumptions,
for
example
in
EIP
165.
E
Sorry
in
the
ip165.
You
basically
will
learn
that
this
is
the
inter
the
functions
that
it
dispose.
We
anticipate
in
the
future
with
the
design
pattern
of
proxy
design
pattern
of
diamonds.
You
will
see
a
small
contract,
exposing
different
functionalities
to
different
wallets
to
different
accounts,
and
that's
why
we
take
that
into
account
and
in
in
the
in
the
detection.
We
actually
expose
a
a
parameter
to
specify
which
color
is
calling
and
then
it
will
return
EIP
status
of
that
particular
EIP.
E
And
then
we
also
allow
major
EIP
identifier
and
minor
EIP
identifier,
where
major
at
the
API
identifier
will
be
the
numbers
to
make
it
easier
to
identify,
and
then
the
minor
ones
will
actually
be.
You
can
include
different
functionalities
for
eips,
so
I'm
happy
to
have
share
more
in
all
ERC
devs
and
if
you're
interested
and
learn
about
this,
please
come
over
and
and
yeah.
Thank
you
and
your
feedback
is
greatly
appreciated.
I
know
this
is
trying
to
be
a
draft
right
now.
E
A
E
A
A
All
right
so
I
think
that
is
the
last
scheduled
item
we
have
so
now.
We
have
time
for
any
demos
if
wallets
want
to
show
off
any
cool
new
features.
They've
been
working
on
and
if
we
don't
have
any
of
that,
just
some
general
discussion.
A
Then
I
guess
we're
officially
done
for
today.
Thanks
everybody
for
coming
out,
we'll
see
you
all
next
month.