►
From YouTube: All Wallet Devs#6
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).
B
Oh,
so
I
don't
think
they
chose
to
put
it
there.
I
think
it
was
a
side
effect
of
the
way
the
system
was
designed
and
it
was
hard
to
patch
and
the
reason
I
think
this
is
because
they
go
to
Great
Lengths
to
stop
the
plugins
from
actually
injecting
into
the
page
directly
like
when
you
have
a
Content
script.
It
very
intentionally
does
not
go
into
the
pages
namespace.
They
have
a
whole
sandbox
for
that.
That
is
isolated.
B
A
B
C
B
Line
item
for
Dangerous
content,
script
or
something
like,
and
that
would
have
been
significantly
easier
for
everybody
I
think
involved
rather
than
because
the
way
it
works
right
now.
Is
you
inject
a
script
tag
which
happens
to
execute
in
the
context
of
the
page,
rather
than
the
context
of
the
extensions
view
of
the
page,
because
everything
that's
in
the
Dom
executes
within
that
context,
and
that
it
really
feels
to
me
like
an
accident
yeah.
A
Sure
so
welcome
everybody
to
all
Walla
devs
number
five.
A
We
have
two
things
on
the
agenda:
two
official
things
anyways
so
I
wanted
to
talk
to
wallet
devs
about
how
much
appetite
there
would
be
for
the
wallet
shared
testing
framework
for
wallet.
So
we
we
talked
about
it
during
some
of
the
earlier
meetings
and
I'd
love
to
hear.
If,
if
there's
any
interest
in,
perhaps
funding
a
Dev
to
work
on
it
because
I
have
someone
in
mind
foreign.
B
I
think
it'd
be
useful,
but
most
useful
for
dap
developers,
because
right
now,
integrating
with
multiple
wallets
is
hard
because
they
all
have
little
idiosyncrasies
and
it
is
not
clear
where
those
idiosyncrasies
lie
and
having
a
clear
testing
framework
lets.
You
know
this
is
the
set
of
things
that
all
well,
let's
comply
with,
or
at
least
you
can
see
which
well
it's
kind
of
like
when
you
go
to
mdn
and
you
see
the
browser
compatibility
list
or
can
I
use.com
or
report
or
whatever
it
is.
B
More,
it's
potentially
more
incentive
aligned
like
I,
feel
like
new
wallets
our
incentive
aligned
to
participate
in
the
testing,
so
they
can
know
you
know,
do
I
match
the
thing
that
everybody
else
matches
so
I'm,
most
likely
to
work
with
things
adapts
work
with
I
think
it'll
be
very
difficult
to
get
existing
Market
leaders
involved
because
there's
really
no
incentive
for
them.
In
fact,
there's
counter
incentive
for
them.
I
think.
A
No,
that
makes
sense,
I'll
see
what
I
can
find
from
dap
developers.
Then.
A
Me,
oh
yeah,
yeah
and
I
think
I.
Think
it's
totally
possible,
like
I
was
thinking
of
gluing
together,
like
ganache,
with
like
a
thin
server
and
writing
like
your
test
and
typescript
and
maybe
gluing
in
some
kind
of
like
selenium
or
web
driver
thing
to
be
able
to
click
on
buttons
and
I.
Think
that'll
cover
most
wallets.
A
All
right:
well,
that's
it
for
that!
I
guess!
Is
there
anything?
Any
wallet
wants
to
demo
any
new
progress
on
4337
or
BLS,
or
anything
like
that.
D
Oh
hi,
hey
guys.
This
is
my
first
time
to
attend.
I'll
call
that
meeting
or
wallet
that
meeting
yeah.
This
is
judgment
from
so
wallet.
He
just
won
the
best
account
application
price
from
EF
during
the
is
global.
Is
congratulations
yeah,
so
I
guess
for
the
nest,
that's
or
wallet
that
meeting
of
our
developer
will
will
join
and
participate
yeah.
So
just
come
here
to
say:
hi.
A
Yo,
hey
and
welcome
most
things
happen.
Asynchronously
in
the
text
chat,
and
you
know
we
kind
of
just
hang
out
here
once
a
month,
so
yeah.
D
Yeah
sure
all
of
our
demo
is
in
our
Twitter
page,
so
feel
free
to
check
that
out.
I
will
send
that
in
the
general
Channel.
A
D
Oh
I
guess
it's
under
test
net,
so
yeah
I'm,
not
sure
if
it's
ready
or
not,
but
I
will
send
a
recording
video
to
the
general
Channel.
Also
great
thanks.
E
Welcome
Soul
wallet
we
can,
we
can
demo
if
someone
else
just
shared
their
screen.
We
can
let
them
do,
but
we
also
can
demo
our
wallet.
Candid
wallets
we're.
Building
an
erc437,
Mobile
wallet
and
I
can
spin
up
a
demo
on
a
test
Network
and
show
you
what
we
have
been
working
on
in
our
progress.
E
F
E
Okay,
so
I,
so
what
you're
saying
here
is
is
an
already
deployed
wallet.
I'll,
show
you
a
few
transactions
that
we,
it.
E
E
The
features
I
can
show
you
is
I.
Can
let's
start
with
the
scent,
so
I
have
right
now:
I,
don't
have
any
any
other
or
uni.
But
I
do
have
this
test
token
called
Candid
test
token
I
can
just
go
ahead
and
use
a
send
it
to
someone
so
I'll
send
it
to
Andrew.
E
A
E
So
the
ray
layer-
it's
a-
is
the
paymaster.
This
is
the
Smart
contract
that
it's
is
deployed.
It
takes,
can
the
token
as
a
as
as
it
is,
and
it
it
does
swap
it
with
ather.
So
it's
up
to
the
paymaster
to
manage
to
manage
its
its
inventory.
It
could
have
a
little
bit
of
ether
and
a
little
bit
of
candid
test
token
and
then
just
like
accepts
the
amount
of
gas.
What
you
just!
What
you
just
saw
here
actually
is
that
the
user
didn't
pay
for
transaction
fees.
I
did
select.
E
I
did
in
fact
select
to
pay
for
candid
test
tokens,
but
right
now
we're
actually
sponsoring
all
transaction
fees,
so
the
user
didn't
pay
for
any
fees
right
now,
it's
the
paymaster
who
sponsored
it
and
we
can
go
to
see
on
the
entry
point
contract
if
the
that's
the
general
entry
point
contract
that
long
early.
If
the
transaction
went
through
it-
and
you
can
see
here-
this
is
my
my
transfer
transaction.
It
did
send.
Indeed,
0.001
can
the
test
token
to
that
contract.
Address.
E
I
can
also
show
you
the
swap,
but
let's
see
I'll
need
a
little
bit
of
I.
Don't
think!
There's
liquidity
for
this
candid
test
token,
so
I'll,
let
Andrew
send
me
some
ether
and
or
some
or
some
uni
and
I
can
I
can
swap
them
here.
E
The
cool
thing
about
swapping
with
a
smart
contract
wallet
is
that
you
can
batch
multiple
transactions
together.
So
if,
if
I'm,
if
I
were
to
swap
uni
to
ather
the,
what
you
can
the
user
just
need
to
like
submit
it
and
sign
it
once
and
what's
happening,
is
that
there
we're
approving
only
the
amount
of
unit
that
they
want
to
swap
and
and
depositing
it
in
into
the
into
the
uni
swap
contract
and
a
single
in
a
single
transaction.
E
Let's
see
if
I
got
the
uni
as
well.
Okay
I
got
the
uni,
so
let
me
swap
the
unit
up
so
so
right
now
we're
fetching
prices
using
the
units
of
SDK
and
here
we're
sponsoring
the
transaction.
So
you
see
that
the
user
is
not
paying
any
fees
with
our
paymaster
and
you
just
hit
review
reviewing
what
you
have
and
it's
only
a
single
transaction
that
the
user
is
approving.
E
Ben
thanks
one
cool
thing
is
that
we
used
nurses,
social
recovery
module
as
our
social
recovery
mechanism,
so
a
user
can
just
like
they
don't
need
to
keep
a
seat
phrase.
So
I
can
go
here
to
security.
Obviously,
before
I
can
I
can
make
all
this
transactions.
It's
very.
It's
better!
That
I
add
a
guardian.
E
So
I
can
add
anyone
as
a
guardian,
so
I'm
gonna
go
ahead
and
add
myself,
you
can
use
any
wallet
as
a
guardian,
so
metamask
or
Oreo,
Ledger
or
or
another
candid
wallet,
so
I'm
going
to
go
ahead
and
add
the
guardian
here
again
we're
sponsoring
this
transaction
in
our
test
Network,
because
for
now
it
doesn't
cost
us
anything.
E
And
I
just
added
regarding
a
similar
mechanism
to
to
the
to
the
origin
wallet
and
also
it's
the
same.
We
use
the
social
recovery
mechanism
or
contract
from
Moses,
safe.
A
So
so,
how
big
are
the
diffs
on
top
of
gnosis
safe?
Is
this
literally
just
their
contract
or.
E
The
difference
there's
no
real
like
so.
The
difference
is
that
we
use
like
erc437
and
NOS
is
safe
and
it's
the
implementation
of
infinitism
theme
on
as
a
base
wallet
for
gnosis,
but
we
can
go
through
the
contracts
like
quickly
after
the
demo
and
I
can
show
you
the
difference.
Sure.
E
E
I
refresh
so
this
is
kind
of
manually
losing
my
my
wallet
and
you
can
see
here.
I
just
lost
my
wallet,
I
just
need
to
click.
Last
wallet
and
I'll
use
the
recovery
mechanism,
I
have
to
specify
which
wallet
so
I
just
need
to
know
my
public
address
or
my
ens.
If
I
had
one
so
my
public
address
was
I
saved
it
here
in
my
clipboard
and
I'll
create
a
new
password,
I
just
use
the
old
one
I
used
before
and
that
password
like
is
stored
locally,
the
seat
phrases
also
locally.
E
A
recovery
request
was
created
for
this
wallet
in
the
past
hour:
oh
okay,
so
since
I
already
did
like
a
recovery
request,
we
added
this
like
feature
to
meditate
from
spam
attacks.
If
someone
is
more
than
if
someone
tries
to
like
recover
a
wallet
multiple
times,
then
we
actually
limit
how
many
times
you
can
recover.
E
It
I
think
if
I
want
to
show
you
the
recovery
mechanism,
I
can
so
imagine
if,
if
I
already
did
like
execute
recover,
you'd
go
to
our
security
Center,
which
is
this
page
right
there
and
you
can
log
in
with
a
metamask,
so
I'll,
just
like
log
out
here
and
show
you.
E
Okay,
so
now
we
just
initiated
a
recovery
request.
That
requires
a
requests,
so
we
we
have.
We
do
have
a
back
end
for
that.
For
that
piece
we
get
the
recovery
request
and
then
the
user
needs
to
make
sure
that
the
emojis
that
they're
seeing
in
the
screen
matches
the
emojis
that
that
they're
gonna
see
on
the
recovery
page.
So
a
guardian
will
go
in
with
their
metamask
or
any
type
of
wallet
and
they
would
like
type
in
the
public
address
of
the
wallet.
E
So
I
think
that's
the
one
yep
and
once
so,
we
know
that
the
guardian
is
that
person
is
the
metamask
wallet,
and
so
we
can
show
the
the
recovery
Quest
and
the
Emojis
does
indeed
match.
If
there's
another
set
of
emojis,
the
guardian
shouldn't
sign
this
message,
because
that
would
be
another
person
trying
to
recover
the
wallet
and
it
wouldn't
be
the
real
owner,
because
the
Emojis
are
communicated
like
offline
between
the
guardian
and
the
owner
accounts.
So
I'll
go
ahead
and
sign
up
so.
A
Let
me
just
interrupt
for
a
second,
so
one
small
suggestion
I
have
to
make
here
is
instead
of
displaying
the
Emojis
and
asking
them
to
confirm
the
person
who's
supposed
to
check.
The
Emoji
should
choose
between
a
set
of
n
like
random
combinations,
and
they
have
to
pick
the
correct
one
and
that
forces
them
to
actually
verify
it,
as
opposed
to
just
trusting
that
they
verify
it.
Okay,.
E
I
think
yeah,
that's
a
better
idea.
It's
kind
of
a
maybe
adding
a
like
a
set
of
numbers
or
maybe
adding
four
emojis
would
be
better
right.
A
No,
not
adding
more
emojis,
it's
just
like
so
right,
like
the
screen
we're
looking
at
right
now,
the
Emojis
there
are
the
the
ones
that
the
the
recovery
person
is
supposed
to
verify
right.
A
So
if
you
just
added
like
three
more
rows
and
with
two
of
them
having
incorrect
sets
of
emojis
and
one
of
them
having
the
correct
set
of
emoji,
then
the
the
recovery
person
has
to
pick
the
correct
set
of
emojis.
That
forces
them
to
actually
communicate,
as
opposed
to
just
blindly
clicking
the
sign
button,
and
it
makes
for
better
ux
or
better
security.
Anyways.
E
Yeah
I
think
that's
a
that's
a
good
idea,
I
think
we'll
Implement,
that
that
forces
them
to
verify
the
Emoji
sets
exactly
yeah
cool
thanks
a
lot
for
the
feedback.
So
I'll
continue
signing
the
message.
Since
we
I
guess
we
have
to
actually
verify
the
Emojis.
E
B
I
see
okay,
so
if
you're
back
in
this
down,
does
that
mean
recovery
can't
happen
or
is
there
a
way
to
do
it
if
you're
back
and
it
goes
offline.
E
We
can
have
like
on-chain
recovery.
Our
back
end
just
makes
it
easy
for
the
user
to
recover,
but
you
can
also
recover
it
without
the
back
end.
It
just
will
have
to
write
like
a
little
bit
of
documentation
to
do
it,
but
it's
totally
possible
to
recover
it
with
unchain
with,
while
interacting
with
our
contract.
B
It
feels
like
maybe
I'm
missing
something,
but
it
feels
like
this
page
you're
looking
at
below
3000
could
be
done
almost
entirely
without
a
back.
End
am
I
misunderstanding,
something
it
looks
like
the
only
back
end
piece.
Is
that
collection
step?
Is
there
more?
Did
the.
B
I
was
just
thinking
that
like
there's,
so
you
can
still
use
the
back
end
as
like
an
optimistic
thing
and
where
so,
when
the
user
clicks
to
sign
metamask,
it
then
gets
sent
to
the
back
end
within
that
screen.
It
has,
let's
say
it's
a
one
of
one
of
two
right,
so
they
need
to
collect
two
of
them.
The
user
right
on
that
screen
has
two
options:
one
wait
for
a
second
signer
to
be
collected
or
submit
their
signature
on
chain.
So
that
way,
the
next
person
can
then
so.
B
There's
no
need
for
coordination
like
the
two.
The
two
social
recovery
participants
can
both
sign
independently,
submit
their
signatures
on
chain
without
and
the
recovery
would
happen
after
the
second
one
showed
up.
Does
that
make
sense.
E
F
E
F
Think
yeah
and
I
can
I
help
in
this.
Does
this
matter
yeah
actually
yeah?
Actually
our
our
recovery,
our
recovery,
like
we
can
like
this
website
to
the
back
end.
Everyone
can
just
sign
without
submitting
an
actual
transaction
and
then
submit
one
transaction
to
recover
the
to
create
the
full
recovery
or
someone
can
interact
with
each
single
each.
Each
single
Guardian
can
interact
with
a
contract
independently
and
and
add
his
recovery
requests,
and
then
it
can
be
done
and
then
the
last
one
can
submit
the
recovery
transaction.
F
So
yeah
you're
absolutely
right,
it's
better
to
do
it
without
a
back
end
yeah,
but
we
just
thought
that
this
is
maybe
maybe
easier
and
yeah.
We
can
also
try
to
make
like
another
web
app
without
a
back
end.
Yeah.
B
B
My
thinking
is
if,
if
this
page
you're
looking
at
was
ipfs
hosted,
the
entire
thing
could
be
done.
Even
if
you're,
you
know
your
development
team,
all
got,
you
know,
disappeared
for
whatever
reason
or
or
censoring,
or
something
like
that,
and
that
would
at
least
for
me
it
would
give
much
more
confidence
that
I
don't
need
you
guys
to
be
online
and
I
can
still
use
the
UI.
I
can
still
do
all
the
simple
things.
B
Year,
yeah
so
having
it
all
I
think
it
could
all
be
in
one
UI
still,
you
could
still
have
the
back
end
like
you
have
it's
just
if
the
back
end
is
unavailable,
then
fall
back
too
or
if
the
back
end
or
maybe
there's
two
buttons.
One
is
wait
for
other
signers
another
one
thing:
there's
a
button
for
submit
on
chain
or
something
so
that
way.
Maybe
the
back
end
is
up,
but
it's
not
behaving
properly
or
something
like
that,
like
it's
not
actually
aggregating
foreign
give
a
lot
more
confidence.
E
Yeah
I
think
that's
it's
a
good
idea.
We
can,
like
you
said
we
can
implement
it
on
the
same
front-end.
One
one
case
is
that
with
a
backend
it
would
let
you
save
a
little
bit
of
fees,
because
only
one
single
transaction
could
be
submitted,
and
the
other
case,
like
you
said,
is
each
Guardian
can
like
submit
their
own
transaction
and
we
don't
need
the
backend
for
that.
Yeah.
I
Oh
yeah,
okay,
if
you
didn't
considered
yet
how
like
how
to
aggregate
those
that
signatures
I,
I'm
working
on
a
proposal
to
kind
of
standardizing
it
into
it
itself,.
A
Is
that
it
for
the
for
this
demo.
I
I
I'm,
muted
myself,
but
can
you
hear
me.
I
Yeah
yeah,
my
I,
didn't
know
that
my
bike
was
both
live
so
yeah.
If
you
haven't,
decided
how
to
like
a
specific
way
to
determine
the
implementation
for
us.
Aggregating
signature
from
offline
I
am
proposing
an
endorsement
schemes
that
you
can
use
that
as
a
way
to
aggregate.
E
B
Big
difference
or
Victor
probably
have
muted
was
talking,
and
you
just
started
talking
over.
I
E
Okay,
happy
to
talk,
feel
free
to
please
share
the
the
proposal
and
and.
E
The
biggest
difference
or
or
uniqueness
of
of
with
your
wallet
versus
something
like
like
urgent
yeah,
that's
a
good
question
so
Argent
is,
is
a
smart
contract
wallet
that
does
offer
all
these
features,
except
that
you
do
you
don't
need
to
rely
on
all
the
services
that
Arjun
offer
like
they
do
have
their
own,
like
between
codes
for
layer,
which
is
the
equivalent
of
baymaster
that
we're
using
and
without
their
layer.
You
cannot
like
execute
the
features
that
that
comes
in
as
in
like
paying
a
transaction
fees
with
another
token.
E
The
whole
point
of
erc437
is
to
make
things
as
much
decentralized
as
possible,
so
the
paymaster
it
doesn't
have
to
be
our
paymaster
that
gets
that
gets
like
a
used.
You
can
use
any
other
playmaster
service
through
our
wallet
relaying,
so
relaying
the
transaction
and
submitting
them
because
it's
origin
does
have
their
own,
like
between
code
like
bundler.
This
is
this
is
the
case.
They
take
the
transaction
and
submit
them
without
that
relayer.
Your
transaction
cannot
be
executed
with
Arjun,
so
really
without
an
urgent
company.
E
You
cannot
use
your
wallet,
you
can
retrieve
your
tokens
and
then
migrate
elsewhere,
but
your
your
urgent
world
really
cannot
focus
case
of
a
candid
wallet
with
an
erc4337
that
binder
right
now
we're
running
a
private
binder,
but
in
the
future
there
should
be
a
mem
full
of
bunders.
Anyone
can
pick
up
your
transaction
and
submit
them
to
the
actual
mempool
or
the
validator
sequencer
to
process
it.
Does
that
make
sense.
J
I
also
had
a
question
also
thank
you
for
the
demo.
It's
very
cool,
so
I
noticed
that
you
had
email
recovery
as
one
of
the
options.
Could
you
just
explain
how
that
is
supposed
to
work.
E
Yeah,
so
to
just
to
finish
the
demo
we
just
like
recovered
the
wallets
you
can
see
here
like
I
got
access
back
to
my
wallet
without
the
private
key
I
can
remove
the
my
guardian
here.
If
I
want
to
the
on
this,
the
owner
of
the
wallet
always
like
have
access
to
kick
Guardians.
If
they
want
and
you'll
see
here
that
you'll
be
able
to
add
like
an
an
email.
So
the
email
is
an
option
that
we
added
in
you
can
think
of
it
as
an
Institutional
Guardian.
E
So
you
can
think
of
okay.
If
you
wanna,
you
have
the
option
to
use
a
company
as
your
guardian
and
they
will
use
a
type
of
authentication
system,
for
example,
email
and
SMS
or
or
a
I.
Don't
know
a
video
call
with
you,
and
that
can
be
your
guardian
right
now,
we're
just
like
dimming.
In
making
a
demo
with
an
email
recovery,
we
use
the
magic
link
which,
which
is
a
service
that
offer
authentication
it's
very
centralized.
E
So
if
magic
link
disappears,
Your
Guardian
also
disappears
just
keep
in
mind,
but
that's
just
to
showcas,
like
you
can
have
an
institution
as
a
guardian.
We
hope
in
the
future
to
offer
this
type
of
recovery
with
multiple
two-factor
authentication,
with
an
email
and
SMS,
and
you
can
select
the
company
as
candid,
for
example,
as
your
as
one
of
your
guards,
which
is
totally
optional
as
well.
A
E
You
can
mix
institution,
family
and
friends,
you
can
add
as
many
gardening
as
you
want,
you
can
have
a
family
and
friends,
it's
basically
a
wallet,
any
wallet,
any
type
of
wall.
You
can
have
your
Ledger
as
a
friend
of
yours
as
well,
when
we
will
have
a
threshold
for
how
many
Guardians
your
you
need
to
recover.
So
you
can
have
okay,
10,
Guardians
and
maybe
50
percent
of
them.
If
they
assign
the
transaction,
then
they
can
recover
your
wallet.
H
B
Think
one
thing
to
keep
in
mind
and
I'm
very,
very
happy
with
what
you
guys
have
shown
here.
One
thing
to
keep
in
mind
is
figuring
out
how
to
make
sure
users
are
selecting
an
appropriate
Guardian
set.
I
think
this
is
one
of
the
hardest
problems
with
post
recovery
wallets
is
that
your
average
user
is
going
to
be
very
bad
at
choosing
the
right
number
of
Guardians
and
choosing
both
m
and
n
and
who
those
people
are
right
and.
C
B
Making
sure
it's
very
clear
to
the
user
that
and
again
this
is
hard
I,
don't
have
a
solution
for
you.
Just
keep
in
mind,
be
very
clear
to
the
user
that
if
they
put
down
their,
you
know
their
girlfriend
and
their
their
sister
or
whatever
as
their
Guardians.
And
it's
a
one
of
two.
You
know
that's
something
that
I
can
imagine
people
doing
and
that
is
very
insecure.
You're
basically
saying
these,
two
people
have
100
Access
to
all
of
my
money
and.
G
B
You
aren't
going
to
realize
that
on
their
own.
E
I
I
think
you're
you're
right
and
it
would
be
our
job
in
the
content
to
Showcase
that
we
haven't
really
like
showed
it
here
in
the
demo
you're
seeing
but
I
can
imagine
like
really
clarifying
that
the
that
the
guardian
you
select,
we
will
have
like
certain
opinionated
I
guess:
advice
saying
that
it's
better
to
have
at
least
at
minimum
three
Guardians
one
would
be
family
and
friends.
They
shouldn't
know
each
other
I
I
doubt
that
would
be
even
better
that
way
they
wouldn't
coordinate
against.
E
Like
a
wallet
corner,
you
would
have.
We
can
recommend
if
right
now
we're
not
going
to
recommend
an
institution.
But
if
we
have
a
solid
institution
that
that
can
offer
like
a
guardian,
they
can
recommend
one
Guardian
at
least
one
family
and
friends,
and
if
they
do
have
a
ledger,
then
we
can
recommend
a
hardware
wallet
as
their
third
option.
D
Oh
by
the
way,
I
think
Arjun
the
way
Arjun
do.
That
is,
is
really
good.
Oh
compared
to
Michael's
comments
on.
Maybe
people
don't
have
enough
friends
or
when
adding
new
Guardians
is
dangerous.
Yeah
Arjun
so
offer
a
default
Guardians
themselves,
so
for
most
of
the
promo
user
is
a
much
better
experience
and
safer.
E
Yes,
I
I
I
do
like
the
origin
way
as
well.
They
they
do
it
two
ways:
they
have
an
off-chain
recovery.
Basically
they
don't
add
themselves
as
a
guardian.
They
just
add
themselves
in
a
way
that
they
add
your
private
key
encrypted
in
your
iCloud
and
they
have
one
Parts
of
the
private
key
I
I
think
also
encrypted
in
their
server
and
that's
how
they
do
option
recovery.
E
It's
kind
of
the
most
secure
way
to
do
it
like
offshine,
but
I,
think
with
the
guardian
system
and
a
smart
contract
way
it's
it's
much
better.
It
does
cost
a
little
bit
more
than
of
chain,
but
it's
more
secure
and
since
we're
going
to
be
focusing
on
Layer
Two,
we
won't
have
the
problem
of
gas
fees
like
Arjun
did
because
they're
deployed,
maybe
on
mainnet
they're
like
volts,
but
they're,
working
on,
like
ZK
sync
and
start
net
right
now.
So.
B
I've
been
trying
to
pitch
to
know
gnosis
for
a
while
to
add
this,
and
since
you
guys,
fortnite
gnosis
I'm,
now
going
to
pitch
to
you
to
try
to
add
it
actually
time-based
social
records.
So
when
you
go,
if
there's
a
countdown
timer
that
the
user
can
configure
might
be
a
day
might
be
a
week,
maybe
a
month
might
be
a
year
and
the
recovery
doesn't
complete
until
that
timer
has
elapsed
and
anytime,
while
that
timer
is
running,
the
owner
of
the
wallet
can
cancel
the
recovery.
This
makes
it.
B
J
B
Or
maybe
she
gets
compromised
into
the
attacker
tries
to
recover
my
wallet
as
long
as
I
show
up
within
you
know
a
week
or
a
month
or
whatever
I
can
cancel,
but
if
I'm
dead,
then
she
can
successfully
cover
all
my
funds
even
by
herself,
and
so
yes,
please,
please
add
that
I've
been
trying
to
get
this
for
a
long
time
and
they
haven't
so
now
I'm
going
to
push
on
you
guys.
E
Okay,
I
think
that's
a
good
idea.
We,
we
did
think
about
like
what
happens
when
a
person
like
pass
passes
away
or
something
but
I
think
that's
a
good.
That's
it's
a
good
idea
and
we'll
definitely
look
at
it.
Since
we
have
a
the
good
thing
about.
The
wallet
that
we
built
like
with
nose
is
safe
is
that
it
does
come
with
modules
and
the
modules
we
can
have
as
we
go
on
with
time
we
can
like
Implement
modules.
E
Obviously
the
user
have
to
approve
a
module
before
they
can
interact
with
it,
and
we
can
have
like
all
different
applications
like
setting
like
a
daily
limits,
for
example,
on
on
a
contract
similar
to
what
you
do.
As
a
regular
bank
account,
you
can
have
like
weekly
limits
or
daily
limits.
You
can
have
all
different
kind
of
modules.
The
same
modules
that
you
can
build
are
not
so
safe.
You
can
build
it
on
candid.
C
Micah,
could
you
clarify
something
for
me?
What's
stopping
like
imagine
if
your
wall
was
stolen
instead
of
just
loss
right,
then
the
person
is
stolen
and
has
access
to
your
your
signing
key
right.
Then
they
can
like
basically
just
stop
you
from
recovering
it.
No
actually.
B
I
mean
someone
has
access
to
your
private
key.
They
can
drain
your
account.
So
if
you're
at
that
point,
if
an
attacker
gets
access
to
your
your
signing
key,
then
there's
basically
nothing
you
can
do
with
the
exception
of
like,
if
you
have
self-imposed
limits
of
some
kind
that
could
potentially
stop
it.
B
But
General
assumption
here
is
that
I'm
operating
under
is
that
there's
many
situations
where
you
lose
access
to
your
signing
key
either
because
someone
stole
your
phone,
but
they
don't
have
the
ability
to
unlock
your
phone
or
because
you
lost
your
phone
or
whatever
and
in
those
situations
having
that
time
delay
is
very
valuable
and
in
a
situation
where
the
person,
the
attacker,
actually
has
full
access
to
your
phone,
then
you're
already
lost
and
doesn't
matter
how
much
Social
recovery
you
have
here
at
this
game.
B
Over
now,
there
I
will
admit
there
is
one
little
Edge
case
where,
if
an
attacker
steals
your
phone
and
they
somehow
have
access
to
unlock
it,
but
they
have
not
yet
unlocked
it.
So,
like
an
example,
hypothetical
example
of
this
is
like
a
kidnapping
scenario
where
they
kidnap
you
and
they're.
Transporting
you
to
some
undisclosed
location
where
they
can
hit
you
with
wrenches
until
you
unlock
your
phone,
your
social
recovery
could
maybe
take
a
minute.
There's.
E
E
We
also
assume
in
general,
like
the
most
of
the
time
like
most
of
the
possibilities
of
losing
the
seed
phrase,
like
the
user,
usually
wouldn't
like
give
out
his
phone
with
his
password
out.
F
F
H
B
E
If
we
have
so
maybe
I'll,
let
other
people
like
speak
if
they
want,
but
if
he,
if
we
have,
if
you
guys
are
interested,
we
can
show
you
a
bit
like
our
contracts
and
and
the
bundle
that
we
built.
The
wallet
is
going
to
be
completely
open
source
and
for
Kabob.
We
just
need
to
clean
up
things
a
bit
and
then
we'll
push
everything,
but
we
can
show
you
on
a
screenshot
right
now,
if
you're
interested
and
now
a
quick
walkthrough.
A
E
I
I
B
Hover
over
the
voice,
Channel
there's
a
little
chat,
icon
pops
up.
E
A
E
F
Yes,
hello,
everyone
yeah!
If
you
can
go
to
candid
World
contracts,
yeah
yeah,
to
the
separate
recovery
yeah,
we
are
mainly
using
the
Genesis.
The
Genesis
module
is
to
add
the
capability
for
the
for
the
for
Genesis
wallet
to
interact
with
an
entry
point,
and
we
have
added
the
some
modifications
the
same
the
same
with
Genesis
wallet
with
some
modification.
F
F
Also,
we
have
also
we
have
the
the
contracts
are
using
brownie
for
testing
and
and
deployment
also
have
another
Rebel
for
the
bundler.
If
you
can
yeah,
we
are
using
bison,
bison
and
Django
for
the
one
lap
yeah,
so
yeah
yeah
it
can.
It
can
receive
operations
from
yeah
from
the
application
and
it
can
process
it
and
it
can
versus
it.
F
I
can
bundle
it
and
the
consent
with
entry
point
yeah
and
you
have
seen
a
live,
live
demonstration
with
with
the
app
working
with
the
bundler,
also
have
a
master
Service
as
a
one
large
that
can
receive
operations,
and
it
can
decide
if
it
if
it,
if
you
don't
sign,
if
you
don't
sponsor
this
transaction
or
not,
it
can
take
a
decision
yeah.
This
is
that
this
is
this
is
our
bundle
and
contracts
so.
E
We'll
be
we'll
be
publishing
everything,
so
you'll
still
be.
Maybe
taking
a
closer
look
in
details
but
happy
to
like
I
guess
we're
happy
to
answer
any
questions.
F
Yeah
we
are,
we
are
actually
using
the
exactly
you
know.
We
are
universities.
Contract
is
not
even
in
the
you
know,
is
in
our
wallet
because
you
are
using
a
a
proxy
okay
and
the
boxing
just
we
just
passed
the
the
address
of
the
of
of
the
singletonians
contract.
So
we
don't
even
have
the
in
our
Rebel.
We
are
just
having
the
proxy.
We
just
have
the
proxy,
so
our
you
know
our
our
implementation,
it
it's
mainly
based
in
the
in
the
middle
added
to
the
Genesis
wallet
yeah.
F
So
if
you
can't
show
them
the
module
yeah,
there
is
multiple
Parts.
There
is
a
fallback
manager.
There
is
a
module
manager
all
these
contracts
when
added
to
Genesis
wallet.
It
adds
support
for
for
the
entry
point
and
if
you
can
go
to
testing
mark.
A
All
your
modifications
are
implemented
as
like,
like
you
subclass
Genesis,
and
then
do
a
little
bit
of
wrapping
and
that's
it.
F
Yeah,
mainly
yeah
mainly
mini
modules.
Yes,
yes,
yes,
and
you
have
interesting.
If
you
go
to
the.
If
you
go
to
test,
no,
no,
no
outer
test,
yeah
yeah
this
one.
F
Can
you
solve
it
because
there
is
like
detailed.
This
is
the
third
way
so
how
we
can
deploy
the
wallets,
deploy
the
proxy,
how
we
can
add
the
modules,
how
how
you
can
accredit
recovery
recovery
operation.
Also,
you
have
another
test
for
the
bandlas
that
can
work
with
the
number.
If
you
run
the
Builder
service
and
run
the
test,
it
yeah,
it
works
with
the
mandar
with
the
same
contracts.
E
Yeah,
so
it's
made
it's
mostly
like
we
haven't
modified
the
general
system.
That's
the
that
was
one
of
our
goals.
It's
not
too
much
modify
at
all
the
or
even
to
Fork
hypnosis.
It's
actually
to
use
it
and
wrap
it
around.
So
we
can
use
it
and
modify
modify
our
modules,
so
any
modules
that
we
use
we
can
like
build
our
own.
E
E
We
just
need
to
clean
up
things
a
bit
and
we
hopefully
we're
gonna,
be
publishing
the
app
next
week
on
Android
and
iOS.
It's
a
flutter
app
and
we
hope
to
be
accepted
by
Apple
and
Android.
If
there's
no
mistakes,
we
have
a
few
fixes
to
do
before
we
publish
it.
We're
gonna
Deploy
on
quarterly,
so
we'll
be
welcome
any
feedback.
As
you
use
the
wallet
we
wanna
like
make
sure
to
test
it
from
the
from
a
user
perspective.
Read
the
contracts.
E
E
Sorry,
optimism,
maintenance,
so
just
just
optimism.
B
E
We
we
want
to
start
with
optimism
with
the
way
we're
gonna
go
with
deploying
on
multiple
chains
is
going
to
be
really
gradually.
E
E
Any
any
questions
or
other
feedback
we
can
take
I
think
that
was
very
useful.
The
feedback
that
you've
given
us
all
of
it.
E
Which
license
we
I
think
Sharif
knows
which
slices
so
far.
We
use
the
contract
for
a
gpn3.
That's
our
GPL,
okay,
yep.
E
B
I'm
happy
to
see
a
wallet
focusing
on
censorship,
resistance,
decentralization
privacy.
So
it's
it's
nice,
so
many
many
wallets
are
like
urgent
or
very
centralized
and
very
borderline
custodial,
which
is
nice
to
see
different
I.
Think
the
only
other
feedback
would
be
that
if
you
can
make
the
UI
deployed
Deployable
to
ipfs
I,
think
that
would
be
the
last
little
thing
that
might
be
centralized.
If
you're,
not
careful.
Let
me
do
that.
E
I
yeah
I
think
I
think
BB.
We
want
to
plan
to
do
that
because
we
have
to
concentrate.
However,
since
it's
going
to
be
a
web
app
the
on
the
ipfs,
it's
totally
different
from
the
mobile
app
client,
so
it
does
require
a
lot
of
effort,
but
we
do
plan
in
the
future
to
do
it.
It's
just
like
a
step-by-step.
A
I
think
we're
pretty
much
a
time
and
I
have
another
meeting,
but
thanks
everybody
for
coming
out
and
yeah.
Hopefully
we'll
see
you
in
a
month.