►
From YouTube: All Wallet Dev Meetings #16
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
Welcome
to
all
wallet,
devs,
don't
think
we
have
a
ton
on
the
agenda
this
week
or
this
month,
but
yeah
we
can
hang
out
and
chat
a
little
bit
and
if
we
run
out
of
things
to
talk
about,
we
can
meet
again
next
month.
A
I'll
kick
this
off
with
a
little
bit
about
wallet,
test
framework,
we've
kind
of
been
quiet.
Since
the
last
update,
not
a
ton
to
report,
we
have
a
few
changes
that
we're
getting
done
in
Geth
now
to
support
each
call
without
a
block,
number
and
I
think
that's
pretty
much
the
only
the
only
major
update
with
WTF
which
to
plug
you
away
on
tests
and
yeah
we're
looking
for
integrators.
If
any
of
you
are
interested
to
use.
B
A
Test
framework
in
your
own
CI,
let
me
know,
and
with
that,
if
anybody
else
wants
to
talk
about
anything,
please
feel
free.
B
So
I
was
about
to
cook
up
some
some
examples
for
my
proposal,
but
since
there's
no
other
update
or
it's
open
for
I
just
sign
up
so
the
proposal
here
is
that
we're
trying
to
address
the
problem
of
address
phishing,
which
I
can
give
an
example
here
so
generally,
there's
probably
a
common
problem
of
wallet
user.
When
you
see
a
long
address,
you
don't
know
whether
they
are
your
the
address
that
you
intend
to
interact
with
or
the
one
that
you
trust.
B
Of
course,
there
are
other
ways
that
can
be
can
be
solved
to
can
be
used
to
reduce
the
potential
of
phishing,
but
it
would
be
nice
if
the
developer
of
wallet
Community
could
come
up
with
the
solutions
to
find
the
way
that
we
will
agree
to
shorten
the
address.
One
of
the
way
is
to
so,
as
we
see
in
the
existing
approach,
the
ens,
the
2.0
is
using
a
few
zeros
in
the
front
and
then
uni
swap
is
doing
similar
things.
B
So
so
long
as
we
make
it
hard
enough
to
generate
these
amount
of
zeros,
and
it
takes
long
enough
time
then
adding
like
even
two
more
two
more
accounts,
adding
even
more
two
more
characters,
so
of
hack
screen
is
60k
harder
than
generating
those
zeros.
Assuming
this
is
one
day
like
you
take
the
current
time
of
one
day
to
generate
two
more
digital.
B
Two
more
characters
will
take
100
years
to
do
that,
so
four
digits
plus
a
number
of
zero
could
be
one
way
one
easy
way
to.
We
do
to
make
it
super
hard
to
fish
addresses.
So
this
is
a
general
concept.
B
Just
wanna
like
put
on
the
table
for
people
to
to
give
feedback,
and
if
people
like
the
idea
or
not
like
the
idea,
we
can
come
up
with
an
alternative,
but
I
think
some
kind
of
standardization
would
be
helpful
to
avoid
phishing
in
general
and
so
with
that
hope.
To
borrow
some
wisdom
from
the
wallet
Builders
here.
B
A
B
B
So
if
we
display
it
in
this
way,
anyone
who
has
a
lot
of
zeros
in
front
will
benefit
from
this,
and
then
it
can
make
them
make
anyone
trying
to
fish
it
much
harder.
B
A
I
think
coming
up
with,
like
a
series
of
recommendations
or
guidelines
on
how
to
display
addresses
is
a
great
idea
like
you
should
always
display
them
beside
like
a
blocky
or
some
visual
representation
like
that's.
That's
a
decent
idea,
maybe
having
a
short
form
notation
for
repeated
characters
like
at
the
beginning
or
end,
would
also
be
useful
and
always
be
able
to
see
the
full
expanded
address,
not
not
naming
anybody
in
particular
but
yeah
that
that
would
also
be
a
a
good
recommendation.
A
B
To
anyone
else,
I
I'm,
taking
down
the
feedback
from
from
Sam.
B
B
If
not,
then
thank
you
for
the
feedback.
I'll
come
up
with
a
document
and
then
post
on
the
theme
on
the
forum
for
asynchronized
feedback.
A
Sure
so
I
guess
another
thing:
that's
kind
of
come
up
that
I
can
talk
a
little
bit
about
the
EIP.
Editors
are
kind
of
restructuring
how
they
organize
documents
and
we're
creating
this
concept
of
working
groups
and
I
think
it
would
be
beneficial
to
wallets
to
have
one
of
these
working
groups
to
work
on
standards
and
documents
like
these
guidelines.
That
Victor
was
talking
about
so
I.
A
A
Cool
so
I
guess
we
could
just
hang
out
for
a
few
minutes
feel
free
to
chat
or
do
whatever
and
if
not,
then
I
guess.
This
is
the
end
of
the
official
meeting.