►
From YouTube: All Wallet Dev Meeting 5
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
So,
let's
skip
over
the
wallet
feature
demos.
We
can
do
that
at
the
end,
if
people
are
still
joining.
Let's
talk
about
the
merge
anything
interesting
from
the
wallet
perspective.
Anything
you
guys
noticed
or
want
to
discuss.
A
For
the
people
who
just
joined
open
the
floor
for
merge
comments,
if
anybody
has
any,
if
not,
we
can
move
on
to
Sam
talking
about
an
EIP
governing
how
wallets
manage
in
browser
sessions
within
their
own
app.
A
Is
the
eip5593
which
a
developer
from
the
brave
wallet
has
raised
it's
it's
kind
of
a
set
of
guidelines
on
when
and
how
wallets
should
inject
window.etherium
I
think
it's
a
great
opportunity
for
wallet
developers
to
coordinate
on
an
EIP
and
I
think
you
could
really
use
input
from
you
guys,
which
are
all
experts
on
the
subject.
So
again,
that's
55.93.
There's
a
link
in
the
proposals,
chat,
yeah,
that's
it!
Anybody
have
any
features
they
want
to
demo.
B
That,
as
a
note,
hi
I
actually
want
to
do
yeah,
hi
I'm
new
here.
This
is
my
first
time
actually.
B
Yep
so
I've
been
working
on
creating
an
SDK
for
4337,
oh
I'm,
working
on
is
my
screen.
Visible
Yep
looks
good
to
me
all
right,
so
the
idea
is
to
allow
people
to
actually
be
able
to
create
smart
contract,
wallets
and
support
like
be
able
to
give
create
pay
masters
and
sponsor
gaskets
using
eip437,
which
is
the
future
of
wallets
all
right.
So
this
is
a
fair,
simple
I,
just
published
it
on
NP
npm
I'll
be
updating
this
documentation
and
sharing
it.
B
So
you
can
easily
create
your
smart
contract
wallet
using
any
owner
if
you
want
to
bundle
some
transaction,
you
can
bundle
transaction
like
this,
so
this
will
allow
our
dap
developers
to
actually
bundle
multiple
transactions
like
approving
and
then
transferring
your
C20
tokens.
B
Then,
if
let's
say
you
want
to
have
cashless,
then
we
are
working
on
that
as
well,
where
you
can
just
attach
your
paymaster
here
to
the
smart
contract
wallet
and
once
you
have
done,
it
will
start
sponsoring
the
gas
fees.
So
this
is
what
I've
been
doing.
I
have
I
have
actually
deployed
a
demo
today,
so
you
once
you
connect
the
wallet.
It
will
show
you
that
hey
this
is
the
owner.
B
This
is
on
getting
disconnect
right
now,
oh,
so
this
is
the
owner,
so
I'm
the
owner.
Actually,
then,
you
can
you'll
get
your
smart
contract
wallet
address
you'll
get
a
deployment
status.
You
can
definitely
do
balance
so
I
have
created
a
small
app
where
you
can
actually
test
transaction
bundle,
transaction
and
sponsor
test.
Sponsor
transaction
I
will
be
sharing
the
SDK
and
the
docs
with
everyone
soon.
B
So
I
think
this
is
what
I
wanted
to
wanted
to
show
everyone.
What
I've.
A
B
Currently
I'm
using
the
Infinity
bundler,
which
is
okay,
I'll,
be
deployed
like
which
is
still
in
beta
phase,
so
I'm
using
this
I'm,
using
mostly
this
plus
the
a
the
normal
construction
Library
ideas
upon
this,
then
I'll
be
adding
multiple
smart
contract
wallets
and
allow
users
to
actually
create
new
smart
contract
wallets
and
also
sponsor
gas
fees.
So
the
idea
started
with
sponsoring
gas
fees,
and
currently
it
is
changed
like
changed
or
or
I
would
say,
progressed
into.
A
Cool,
what
what
license
is
this
available
under.
B
It
is
under
MIT
license,
so
it.
A
B
A
B
About
it,
I
think
the
project
is
still
very
early.
The
documentation
are
still
spots,
I
think
one
side
to
the
documentation,
I
think
within
the
next
week,
then
I'll
probably
again
reach
you
out
for
the
further
Edition
cool.
A
B
A
A
Yeah-
and
you
know
we
can
just
open
it
up
for
regular
chat
now,
unless
somebody
else
wants
to
talk
about
something
in
particular,
but
yeah.
We
can
just
hang
out
for
a
few
minutes
or
take
off
that's
everything
we
have
scheduled.
A
A
It's
like
a
standard
for
composing,
multiple
contracts
together
behind
a
single
interface
like
a
facade.
C
Fancy
yeah
sounds
pretty
cool
I
had
a
thing
that
might
be
interesting
for
the
ethonline
hackathon
I've
been
helping
out
some
hackers
work
on
some
projects
and
a
friend
of
mine.
Actually
we
had
it
on
our
list
of
like
projects
to
build
for
hackathons
started
working
on
npm
package
to
classify
ethers
transactions.
A
C
It's
it's
essentially
an
npm
package
that
turns
any
transaction
into
a
standardized
format
if
that
makes
sense.
So
obviously
you
know
transactions
are
different
with
each
wallet
and
there's
internal
transactions.
C
There's
events
there's
all
sorts
of
weird
stuff,
but
currently
it's
just
limited
to
transactions,
and
the
idea
is
that,
like
there's,
some
wallets
out
there
right
now
that
have
like
super
fancy
features
where,
if
you
let's
say,
register
any
s
name
it
instead
of
saying
the
transaction
and
the
contract
you
interacted
with
Etc,
it
shows
that,
but
it
also
shows
registered
loosemans.eath,
for
example,
right.
C
A
human
readable-
oh
that's
cool
yep,
so
it's
one
npm
package
that
you
can
like
modularly
pick
and
choose
which
things
you
want
to
support
and
the
idea
is,
you
can
just
give
it
a
list
of
NF
or
ens
of
like
other
modules
that
are
built
or
you
can
build
your
own
module
and
then
you
can
just
throw
transactions
at
it,
and
then
it
will
either
output
an
unknown
transaction
and
give
you
the
data
back
where
it
will
tell
you
exactly
what
transaction
it
is
and
do
some
fancy
typescript
magic
to
like
IDE
support
and
all
sorts
of
cool
stuff.
A
So
how
does
it
work?
How
does
it
tell
what
a
what
a
transaction
is.
C
Yeah,
so
it's
so
that
simple,
it's
literally
just
doing
a
for
Loop,
essentially
and
it's
looping
through
all
the
modules
and
then
running
a
the
modules
functions
to
try
and
detect
whether
or
not
it
belongs.
Yeah.
A
Okay,
so
something
I
think
would
be
really
exciting
to
come
from.
This
would
be
and
I
think
it
I
might
be
mistaken,
but
it
could
exist
already,
but
a
standard
way
of
describing
transactions
in
like
Jason
I,
think
that
exists
somewhere.
C
C
Hop
in
here
on
my
computer
and
do
a
quick
screen
share,
so
you
can
see
what
I'm
talking
about.
Oh.
B
C
B
C
So
this
is
the
like
GitHub
repository
I'm
gonna,
see
if
I
can
just
copy
past
some
of
the
code
here,
real,
quick,
the
Oink
and
then
it
should
be
able
to
do
that.
And
then
this
would
have
ethers
needed
I
think.
Is
it
ethers
or
either
JS,
no
100,
sure
I,
don't
know
the
the
long
story
short
is
that
you
should
be
able
to
do.
C
Oh,
it's
The,
Ether,
setup
code,
I,
don't
know,
let's
just
even
bingo,
that's
what
I
was
looking
for.
Okay,
so
this
should
allow
I,
don't
think
that
works.
C
Modules,
slash
there
we
go,
does
that
do
typescript,
I,
don't
know
so
the
the
idea
is
as
follows.
You
essentially
you
specify
the
classifier
once
right,
so
you
say
modules
and
then
you
can
specify
Which
models.
You
want
So.
Currently
he
supports
ens,
polygon
and
super
fluid.
So
let's
say
I
add
super
fluid
as
well
is
this?
Are
we
going
to
Auto
format?
C
C
Let's
see,
let
me
quickly
add
some
linting
here.
So
it's
going
to
look
nice.
So
essentially
the
idea
is
very
simple:
you
you
take
any
transaction,
so
this
could
be
looping
through
each
list
of
transactions.
I
think
this
is
registering
our
organization
name
on
ens
I'm,
not
100
sure,
and
then
you
just
run
the
classify
function
that
came
from
your
your
Builder
up
here.
C
Obviously
feeding
it,
your
your
ethers
provider,
so
it's
just
a
wrapper
on
top
of
ethers.
Basically,
so
if
your
library
is
using
there,
we
go
is
using
ethers
in
the
back
end,
then
or
in
the
front
end
or
anywhere
like
that.
You
can
use
it
like
this
and
then
the
idea
is
as
follows
that
now
you
can
do
data
Dot
and
then
you
can
look
at
the
type.
For
example.
C
C
I
can
go
ahead
and
say:
oh
in
case
it
isn't
approve
or
commit
a
reclaim
a
register
or
register
with
configure
renew
a
safe
transfer
from
a
transfer
firmware.
I,
don't
know
right.
C
So
in
the
event
that
somebody
registers
an
ens
name,
they
can,
you
know,
show
this
components,
blah
blah
blah
it's
getting
mad
at
me
because
the
thing
and
then
for
polygon.
It
would
automatically
know
that,
like
data.action,
sorry
for
using
dark
lighting
by
the
way,
let's
see
if
I
can
do
that,
maybe
that's
better
on
your
eyes
and
then
for
hello.
C
C
Currently,
what
we're
seeing
is
that
a
lot
more
wallets
are
are
implementing
fancy
like
parsing
features
right,
so
the
ability
to
see
an
ens
registration
or
see
a
transfer
using
the
polygon
Bridge
like
in
this
case
a
deposit
ether
right
or
a
deposit
four,
but
it
will
like
do
all
sorts
of
typescript
generic
magic
and
automatically
use
type
erroring
to
figure
out
when
you're
inside
of
the
polygon.
C
If
statement
or
the
quick
case
or
whatever
it'll
automatically
adjust
the
types
and
then
you'll
know
that
the
data
can
only
be
in
this
case,
a
polygon
transaction
or
a
subset
of
the
polygon
transactions
right
and
you'll
know
that
type
will
always
be
polygon.
So
it
does
all
sorts
of
fancy
type
narrowing.
C
If
you
hover
over
this,
you
can
see
that
it's
either
an
ens
transaction,
a
polygon,
transaction
or
I
think
the
super
fluid
one
is
still
glitched,
but
a
super,
fluid
transaction
or
an
unknown
transaction
but
say
I
didn't
want
to
support
polygon
for
some
reason.
I
could
just
remove
it
and
then
it
would
immediately
start
complaining
at
me
because
polygon
doesn't
exist
and
it's
not
a
valid
type.
So
I
can
immediately
remove
it.
Typescript
will
start
throwing
errors.
C
So
if
you're
using
typescript
in
your
project,
it'll
be
smart
about
everything,
and
you
can
immediately
see
that
now
it's
either
an
ens
transaction
or
super
fluid
transaction
and
say
you
don't
like
super
fluid
for
some
reason,
you
can
just
remove
it
as
well,
and
now
it's
only
an
ens
transaction
or
another
transaction
right.
So
it
does
fancy
typescript
magic.
In
the
background.
C
Extra
complexity,
it's
purely
IDE
integration,
essentially
without
needing
any
extensions
or
whatever,
because
it's
typescript.
A
C
Yes,
so
so
the
reason
this
was
initially
built
is
because,
like
a
lot
of
wallets
out,
there
are
moving
to
like
designing
systems
like
these,
but
obviously
it's
an
absolute
pain
to
maintain
a
million
different
modules,
and
in
addition
to
that,
obviously,
every
wallet
wants
to
be
the
best
right,
and
that
comes
with
some
trade-offs.
That
means
that
some
wallets
will
be
closed.
Source
some
wallets
will
keep
this
code
private
in
particular.
C
So
with
each
classify,
the
goal
is
to
just
lower
the
barrier
of
Entry
to
make
a
wallet
with
such
fancy
features
and
to
allow
any
wallet
to
easily
say:
okay
yeah.
We
want
to
show
a
custom
react
component
for
ens
transactions
or
a
custom
component
for
super
fluid
transactions
or
whatever,
so
your
transaction
history
won't
just
be
I
talked
to
this
address.
I
called
this
contract
function,
I
did
x,
y
and
z,
it
will
be
you
registered
in
ens
name.
You
did
this
unknown
thing,
but
fine.
C
We
can't
classify
it
because
you
sent
money
or
something,
and
so
it
will
just
default
to
a
regular
entry
right.
So
it
can
make
your
wallet,
history
or
transaction
history.
A
lot
more
Rich,
if
that
makes
sense,
without
requiring
you
to
scroll
down
in
the
ens
docs
and
figure
out
what
the
freaking
deployed
addresses
on
mainnet
and
what
the
address
is
on
other
chains
and
how
this
works
and
parse
it
all
yourself
right.
A
And
oh
yeah
I'm
just
saying
like
a
lot
of
like.
Hopefully
we
expand
Beyond,
just
JavaScript
and
typescript
wallets
in
the
future.
Oh.
C
Yeah
for
sure,
for
sure,
and
and
hopefully
that
is
the
case,
I
don't
think
right
now
there
are
plans
to
build
other
stuff
because
we're
addicted
to
typescript
and.
C
C
You
but
I'm
I'm
sure
there
there
can
be
other
initiatives
or
we
can
turn
this
into
a
a
Docker
container
that
can
convert
the
e-transaction,
backend,
wise
or
stuff
like
that
yeah.
Okay,
that
makes
sense,
cool
fuel
a
database
or
something
like
that
and
it's
over
they.
They
have
some
there's
some
pretty
okay
documentation,
including
how
to
write
your
own
module.
C
If
you're
like
you,
got
an
nft
project
or
a
smart
contract
project,
and
you
want
to
show
it
right
and
it's
licensed
under
lgpl,
which
means
that
essentially,
anybody
can
use
it
as
long
as
you
use
it
as
a
library.
C
If
you
make
improvements
to
it,
those
must
be
done
publicly
and
must
be
contributed
or
at
least
contained
the
the
original
Source.
If
that
makes
sense,
yeah-
and
this
is
a
hackathon
project-
so
I
don't
know
how
I'll
end
up,
but
it's
pretty
promising.
C
Yes,
so
they're
they're,
not
too
fancy
at
the
moment,
I
think.
But
let's
have
a
quick
look.
The
ens
one
looks
like
this.
So
essentially,
this
is
a
these.
He
made
separate
functions
for
the
base,
registrar
for
the
reverse,
registrar,
Etc,
but
I
think
the
bottom
line
is
just
exporting
this.
C
There's
a
check
function
and
a
resolve
function.
That's
all!
You
need
to
basically
export
the
check
function,
just
checks
if
it's
not
a
mainnet
return
false
and
then,
if
it's
one
of
the
ens
addresses
then
return
true,
otherwise
return
false.
This
is
simply
just
a
quick
match
to
see
if
it's
part
of
ens
or.
C
And
then
base
depending
on
which
address
it
was
interacting
with
he
does
different
parsing
for
each
right.
So
this
way
anybody
that
has
their
own
project,
such
as,
in
this
case
the
ens
one,
which
is
I
think
still
written
by
him.
I,
don't
think
we
made
this.
C
C
C
Write
these
and
what's
in
here,
he's
throwing
apis
in
here,
okay
yeah!
So
that's
the
the
NS
module.
Let's
have
a
quick
look
at
the
super
fluid
one
I
think
he's
worked
on
that
a
bit
as
well
in
the
polygon
one
polygon,
one
yeah,
so
the
polygon
one
as
well
has
a
polygon
module
with
check,
and
the
resolve
logic
is
all
in
here
and
just
outputs
like
that.
So
it's
not
that
bad!
Honestly,
it's
71
lines
and.
C
Yeah-
and
it
also
allows
I
mean
there-
is
some
documentation
here
at
the
bottom
on
how
to
write
one,
because
you
have
to
just
implement
the
is
it
the
check
function
and
the
resolve
function,
but
the
the
the
final
idea
there
is
that,
basically
anybody
can
write
their
own
module
or
directly
like
smack
it
in
there.
You
know,
like
I,
did
with
the
module
stuff
polygon,
for
example.
C
A
Well,
I,
guess:
that's
it!
Thanks
for
coming
out
everyone
and
we'll
see
you
in
about
a
month.