►
From YouTube: All Wallet Dev Meeting 3
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
Joining
they
should
have
joined
by
now.
So
I
guess
this
is
the
meeting
number
three
of
all
wallet
devs.
We
do
have
a
very
light
agenda
today.
We're
mostly
just
gonna,
be
talking
about
the
wallet
extension
registry
and
e-5139,
so
zk
doof
wants
me
to
mention
that
any
wallets
who
haven't
already
signed
up
for
the
interoperability
test
event
should
do
so.
A
You
can
find
info
about
it
in
the
test
event
channel
and
with
that
out
of
the
way,
I
guess
we
can
talk
about
wallet
extension
registry,
so
quick,
summary
corbin
who
isn't
here
today
wants
to
come
up
with
a
standard
way
of
having
multiple
browser
extensions
cooperate,
so
they
don't
clobber
windowed
ethereum
and
on
the
last
call,
we
discussed
using
a
completely
different
mechanism
for
registering
wallets
and
that's
using
a
custom
scheme
handler
so
think,
mail,
2,
except
maybe
web3
or
evm,
or
something
along
those
lines
and
every
wallet
or
webpage
registering
a
handler
for
it
and
then
using
webrtc
to
communicate.
A
C
A
It
it
wouldn't
be
so
you'd
still
need
a
way
to
handle
that,
but
I
think
like
wallet,
connect
and
web
and
web3
model
are
already
working
on
getting
rid
of
window.ethereum.
So.
C
C
A
Yeah,
I
think
that's
that's,
definitely
something
we
should
be
concerned
about,
and
and
corbin's
proposal
similarly
had
like
a
check
if
window
dot
ethereum
exists
and
then,
if
it
does
like
chain
to
it
so.
C
Who
is
coordinating
this
effort?
Because
my
idea
was
to
create
a
shared
package
for
the
whole
ecosystem
that
handles
this
problem
and
all
of
our
providers,
and
everybody
could
use
that
package.
I
just
don't
want
to
tie
it
to
telly
or
any
specific
organization.
C
A
Yeah,
so
that's
that's
exactly
what
corporal
was
suggesting
in
the
extension
registry
channel.
I
think
it's
like
the
first
or
second
message,
he's
kind
of
talking
about
how
it
works
and
then
yeah.
We
we'd
want
to
create
like
a
shared
package
for
doing
it.
C
So
I
was
kind
of
working
with
him
when
I
came
up
with
the
solution.
I
was
just
wondering
whether
there
was
any
recent
development
on
this
arrow,
because
I
kind
of
lose
track,
but
that's
my
fault
together.
A
A
Do
you
have
a
repository
or
something
for
what
you
and
corbin
are
working
on
or.
A
Okay,
cool
yeah,
if
you
want
like
to
link
it
or
whatever
in
that
channel
that'd
be
great,
maybe
some
other
wallets
to
look
at
it.
A
I
don't
think
we
have
one
yet,
but
I
can
make
one
if
you
want.
I
would
love
that
sure
yeah
I'll
I'll.
Do
it
I'll
just
call
it
like
ethereal
wallets
for
now
or
something
like
that,
and
we
can
workshop
the
name
offline.
A
B
On
that
note,
like
we,
don't
have
to
use
the
one
I
created,
but
to
that
vein,
that's
what
web3
well
sort
of
was
intended
to
be
like
I'm
yeah
working
with
the
ef
on
a
wallet
thing,
but
it's
yeah.
The
web3
well
was
meant
to
be
somewhat
of
a
neutral
territory.
A
B
Cool
I'll
share
a
link
somewhere.
A
D
A
So
then,
I
guess
we
can
move
on
to
discussing
eep
5139,
which
was
kind
of
a
uniswap
token
lists,
but
for
rpc
providers
eip.
So
this
came
out
of
a
discussion
we
had
on
the
first
and
second,
I
guess
the
previous
two
calls
and
that's
about
how
adding
random
rpc
providers
from
adap
might
not
be
the
most
secure
idea.
A
So
we've
come
up
with
these
curated
rpg
provider,
lists
that
are
stored
on
ens
or
https,
and
so
far
the
feedback
from
metamask
has
been
that
it's
a
lot
of
work
for
not
too
much
security
gain.
So
if
anybody
wants
to
take
a
look
at
that,
the
link
is
in
the
agenda
and
I
can
post
it
again
in
general.
If
you
want
to
review
it,
let
me
know
how
difficult
you
think
it
is
for
your
your
particular
wallet.
Please
do
and
whether
you
think
it's
worthwhile
pursuing
or
not.
E
So
I
read
through
the
youth
mag's
discussion
and
read
the
eip
and
based
on
like
tj
rush's
comment,
so
each
it
was
the
idea
that
each
wallet
provider
would
be
curating.
Their
own
list
like
that
does
sound
kind
of
analogous
to
the
way
uniswap
is
tackling
the
token
list.
Is
that
how
you
envisioned
it.
A
Yeah,
so
so,
right
now,
each
wallet
does
provide
their
own
list
by
default.
It's
just
not
in
a
standard
format,
so
this
would
be
standardizing
that
format
so
that
non-wallet
providers
like
so
like,
let's
say
I
wanted
to
publish
a
list
and
I'm
not
affiliated
with
a
wallet
I'd,
be
able
to
do
it
too.
So
it's
kind
of
just
like
standardizing.
What's
already
there
yeah.
E
A
That
I
think
you
need
to
have
a
like
a
text
field,
I
guess
to
add
a
a
list
and
then
you
also
need
to
add
ipfs
support
to
your
wallet.
So
if
you
don't
already
have
that,
it
might
be
a
little
heavy.
A
E
I
mean
it's
easy
for
us
to
say
so,
we're
you
know
back
end
and
we're
not
really
impacted
by
this,
because
you
know
we're
we're
just
supplementing
the
the
security
of
you
know,
wallet,
extensions
and
other
tools.
It
seems
like
a
good
idea,
just
from
like
a
user
perspective,
providing
support
when
there's
been
periods
of
congestion.
E
The
only
thing
I've
been
able
to
refer
users
to
is
david,
mihal's,
site,
ethereumnodes.com
and
even
then,
like
everyone's,
so
used
to
either
running
their
own
node
or
using
a
default
provider
in
fiera
that,
like
it,
it's
so
rare
that
it
comes
up,
we
always
scramble
to
be
like,
what's
what's
david's,
link
again,
we'll
just
send
them
the
my
crypto
link
for
our
rpc
endpoint,
so
even
just
for
mainnet
having
more
options
baked
in
would
would
be
great
for
users.
E
A
Oh
thanks
so
yeah
I
mean,
I
think,
that's
really
what
it
comes
down
to.
If
any
wallet
devs
here
want
to
speak
up
about
how
useful
they
think
it
is
and
how
likely
they
would
be
to
implement
it.
That'd
be
great.
A
A
So
each
wallet
right
now
already
has
a
list
of
providers
right
like.
A
C
But
the
thing
is
that
the
wall
of
developers
usually
take
care
of
checking
what
providers
they
add
their
scores
good,
because
it's
kind
of
sensitive
and
important.
C
But
if
I
understand
the
proposal
correctly,
the
list
should
be
hosted
on
cloudflare
or
stamina
somewhere
else,
where
a
community
or
somebody
can
take
care
of
updating
the
list,
adding
new
rpc
providers
and
whatnot.
Who
will
be
doing
that
in.
A
A
It
would
just
be
in
this
format,
as
opposed
to
whatever
like
format
they
use
now,
and
then
users
could
switch
to
a
different
list
if
they
want,
but
each
wallet
would
come
with
a
default
list
that
that
wallets
developer
is
curated.
A
A
A
A
Now
is,
if
I
were
to
like
make
a
reference
implementation
of
the
like
fetching
code
like
because
the
way
it
works
is
you
can
have
like
a
base
list,
and
then
you
can
have
extensions
built
on
top
of
it.
That
was
something
that
came
up
in
the
last
meeting
that
a
couple
people
like
wanted.
So
if
I
made
an
implementation
of
that,
would
that
be
useful?
Would
wallet
devs
want
to
implement
their
own?
Like
I
don't
know
what
the
like
nimbyism
is
for
wallet
code.
C
I
think
that
might
be
helpful,
but
a
quick
question:
did
you
design
anything
that,
like
a
list
of
features,
supported,
endpoints
or
something
for
the
rpgc
providers,
because
different
rpc
providers
have
different
different
capabilities
and
I'm
not
sure
how
is
it
for
adorable
does?
But
ours
is
depending
on
custom
functionality
and
I'm
pretty
sure
it's
the
same
for
everybody
else.
A
C
I
can
talk
about
alchemy
specifics,
like
transaction
history
and
scraping
going
back
to
and
finding
transactions
get
token
balances.
These
are
the
two
most
prominent
that
comes
to
mind.
E
Another
one
that
comes
to
mind
you
know-
maybe
you
just
want
to
like
a
notes
field.
In
addition
to
that,
too,
is
like
the
flashbots
rpc.
If
you
just
had
a
drop
down
list
and
people
are
looking
for
a
responsive
rpc
if
there's
some
sort
of
congestion
issue
with
whatever
they're
using,
if
you
switch
to
flashbots
nothing's
going
to
go
through,
because
you
need
to
understand
that
you
need
to
you
know,
put
your
your
base
fee
higher
in
order
to
get
included
in
a
block.
E
A
So
if
we're
going
to
put
it
into
the
list
format,
I
think
it
would
have
to
be
something
that
all
wallets
agree
on,
or
at
least
there's
some
kind
of
like
standard
way
of
asking
for
the
capabilities,
so
that
that
would
be
useful
to
like
make
a
table
or
like
a
list
of
the
things
that
you
check.
For.
A
And
then
the
other
thing
is,
I
think,
there's
a
group
of
people.
I
think
the
wallet
connect,
people
and
micah
would
prefer
like
a
handshake
kind
of
rpc
call
where
you
can
ask
the
rpc
provider
what
it
supports
as
like
an
rpc
endpoint
itself
is
that
is
that
better?
Is
that
worse?
What
do
you
guys
think
about
that.
C
Actually,
I
believe,
if
it's
a
static
quest,
it
will
go
out
of
date
really
soon.
Okay,.
A
So
maybe
we
have
to
come
up
with
a
way
of
doing
like
asking
the
rpc
endpoint
like
once
every
week
or
month
or
when
the
wallet
starts
and
asking
it
what
it
supports.
Okay,
that's
another
option.
I
can.
I
could
look
into
doing
something
like
that,
but
I
again
I
don't
know
anything
about
the
capabilities
that
wallets
need.
So
if
somebody
wants
to
make
a
list
of
what
you
check
for,
that
would
probably
be
a
good
place
to
start.
C
A
Sure
I
think
yeah
there's
the
web3
well,
would
be
a
good
place
to
to
put
that.
I
think.
A
B
Here
I
was
thinking,
and
I
think
I
saw
some
messages
before
about
four
three,
three,
seven
and
potentially
having
a
channel
for
that.
It
doesn't
make
sense-
or
I
I
didn't
see
where
the
rest
of
the
comments
went.
D
D
So
how
do
we,
how
do
we
add
a
channel.
A
D
Yes,
there
is
a
yeah.
There
is
a
server.
There
is
a
separate
server
for
it,
but
since
a
few
people
asked
about
it
on
the
wallet,
I
thought
it
would
be
good
to
have
some
discussions
there.
We
will
put
a
message
there.