►
From YouTube: All Wallet Dev Meeting 10
Description
CandidWalletDemo
A
A
So,
basically
you
can
go
to
a
security
Tab
and
then
add
the
recovery
contract.
You
can
add
any
essentially
any
ethereum
modeled
on
the
same
network,
we're
not
going
to
be
supporting
email
because
we
use
the
service
called
magiclink
and
the
experience
so
far.
We
cannot
fully
control,
so
we
decided
not
to
go
with
email
in
production,
we're
going
to
be
supporting
family
and
friends
and
another
tab
that
says
Hardware
wallet,
but
essentially
it's
the
same.
You
just
input
an
address
and
we
image
make
sure
to
clarify
that
the
address
is
on
the
same
chain.
A
Yes,
so
the
idea
is
that
you
can
recover
yeah
recover
the
account
in
case
you,
you
lose
your
phone
or
you
delete
the
app
and
then
you
go
to
an
another
interface
and
then,
with
your
guardian
or
recovery
contact,
you
can
change
the
owner
if
they
assign
it
I
think
I
have
trouble
in
the
demo.
Maybe
something
I'm
not
running,
but
I.
Think
you
get
the
idea
here.
It's
unknown
button.
I
can
call
it
like
the
mask
Guardian.
A
You
can
also
remove
a
guardian
in
case.
You
want
to
remove
someone,
let's
say
and
an
ex-girlfriend
you
can
see.
We
have
a
transaction
classic
transaction
history,
something
actually
quite
complex.
That
costs
took
us
some
time
to
like
get
is
monthly
accounts
for
contract
wallets.
So
the
idea
is
that
we
cannot
guarantee
in
the
future
the
same
address
for
a
contract
account
on
a
different
network.
A
So
what
we
did
is
that
on
the
UI
every
time
someone
wants
to
create
an
account
we
specifically
ask
which
which
chain
they
want
to
have
their
account
on
so
I'll,
say
here:
Mark
optimism,
Godly
and
then
we
create
their
accounts
and
we
purposely
never
give
the
same
address
on
a
different
chain.
So
if
I
went
here
and
did
the
created,
onwardly
I'll
I
will
get
a
different
account
and
we
have
a
kind
of
different
UI
than
EOS.
A
Like
users
cannot
just
like
simply
switch
networks,
they
actually
need
to
go
to
their
account
and
select
their
account.
So
I'll
show
you
here,
Mark
quarterly,
and
it's
always
like
a
different
address.
We
don't
let
users
copy
directly.
We
actually
have
a
warning
here
as
well,
so
that
they
don't
consider
the
same
address
on
a
different
Network.
A
It
says
like
basically,
Smart
Control
waters
are
independent.
Even
in
terms
of
security.
You
can
think
of
a
safe.
If
you
have
a
safe
one
with
the
three
owners
on
midnet,
it
can
never
be
the
same
on,
for
example,
optimism,
and
then
we
have
another
warning
here,
so
once
they
copy.
They
should
like
know
that
this
is
only
for
their
this
Network.
A
What
else
yeah
you
can
something
to
take
into
consideration
for
others
or
building
smart
contract
wallets.
We
know
that
if
you're
sending
it
to
an
exchange,
especially
from
I,
don't
have
it
here,
but
especially
from
from
a
contract
account
on
Layer
Two
they're,
not
gonna,
support
native
currency.
So
it's
going
to
be
lost,
so
we
have
warnings.
A
We
have
warnings.
I'm,
not
gonna,
show
it
to
you
here,
but
we
do
have
warnings
in
case
they're,
sending
it
if
they're
sending
erc20
it
does,
does
work
fine.
So
this
is
an
erc20
and
yeah.
It
would
be
something
like
that.
So
we
do
have
one
here:
the
person
I'm
sending
to
has
a
wallet
that
supports
optimism.
A
B
B
A
A
Okay,
yeah
thanks
a
lot
I'll
take
a
look
at
this
we're
yeah.
We're
definitely
worried
that
I
mean
for
now
we're
only
on
autism,
but
we
definitely
worry.
If
someone
sends
to
another
Network
and
we're
not
supporting
it,
then
we
we
don't
let
users
export
their
seed
phrase
as
part
of
the
experience
of
using
the
wallet.
If
someone
that
does
it
I'm,
not
sure
if
you
can
help
them
or
not,
maybe
you
can
have
a
special
build
for
them,
so
yeah
we're
trying
just
to
avoid
that
at
all
costs.
A
A
C
A
C
B
There's
also
the
I
think
it
happened
to
a
nurses
safe
where
they
changed
the
keys
on
maidenet,
but
on
like
to
get
it
to
the
same
address,
you
have
to
deploy
it
initially,
with
the
same
keys
that
the
first
wallet
was
initially
deployed
with,
because
the
Constructor
arguments
are
appended
onto
the
end
of
the
bytecode.
So
that's
also
kind
of
a
security
issue
if
you
want
to
use
the
same
address.
So
it's
probably
a
really
good
idea
to
use
different
addresses
on
each
chain.
Yeah
makes
sense.
D
I'd
argue
for
privacy
reasons
as
well.
These
things
are
actually
better
to
go
different
directions
because
there's
oftentimes
implicit
assumptions
that
are
being
made
because
of
these
types
of
like
address
things
on
the
DAP
side,
so
like,
for
example,
in
sign
in
with
ethereum
today,
there's
an
assumption
that
the
account
that
you
sign
in
with
is
also
the
account
that
you're
going
to
use
funds
from
if
you're
logging
into
like
a
D5
protocol,
and
that's
because
of
the
way
the
API
has
been
designed
and
because
the
account
is
being
reused.
A
Cool
I
think
yeah
I
think
that's
it.
That's
all
the
features
that
we
have
also
the
last
thing
is
the
bundle
cause
I
I
cannot.
I
cannot
have
a
demo
right
now,
but
essentially
I
need
that
can
use
the
multi-call
that
we
have
and
they
can
offer
a
one-clip
experience.
So
the
classic
case
is
a
proven
deposit.
Instead
of
doing
it
one
by
one,
you
can
do
it
in
a
simple
TX
and
we're
working
with
like
a
few
gaps
so
that
they
can
support
it.
A
If
anyone
is
interesting
to
look,
we
have
everything
open
source
from
client
to
contracts,
to
we're
even
building
a
bundle
which
is
a
piece
of
software.
That's
going
to
operate
in
the
P2P
mempo
of
437
in
Python.
So
if
you're
interested
to
contribute
to
the
software
as
well,
then
yeah,
please.
Let
me
know.
A
E
A
I
think
I,
don't
specifically
have
specific
research
on
how
to
write
a
good
proposal,
but,
but
maybe
others
might
have
and
I
would
be
happy
to
take
a
look
as
well
and
then
give
you
feedback.
We
did
make
a
proposal
as
well
and
we
we
asked
feedback
from,
like
others
in
the
space,
and
that
was
helpful.
So
I
can
also
like
help
you
out.