►
From YouTube: Core Unit Tools #01: Gnosis Safe - March 1, 2021
Description
Core Unit Tools #01: Gnosis Safe
John and Anna from Gnosis Safe join the first Core Unit Tools call to discuss what Gnosis is, what a multisig is, what its use cases are, and how to actually use it!
Agenda: https://forum.makerdao.com/t/core-unit-tools-01-through-gnosis-safe-march-1st-17-00-utc/6757
Governance Forum:
https://forum.makerdao.com/
Disclaimer: These calls and the summaries are produced and hosted by MakerDAO community members. Content produced by the community are not the statements or views of the Maker Foundation.
A
Hi,
everyone
welcome
to
core
unit
tools
number
one
first
session,
where
we
try
to
help
core
units
set
up
different
tools
that
might
be
useful
for
for
their
management
and
the
first
one
we
chose
is
gnosis,
safe
yeah.
We
believe
that
a
multisig
can
play
a
crucial
role
in
in
multiple
core
units
and
it's
interesting
to
know
how
to
do
it
properly
right.
A
So
today,
I'm
well
I'm
here
with
john
ennis
from
the
gnosis
safe
ecosystem
development,
and
he
will
briefly
go
through
what
gnosis
is
what
a
multi-stick
is,
what
the
use
cases
are
and
how
to
actually
use
it.
So
again,
as
always,
if
you
have
any
questions,
please
shoot,
and
hopefully
you
can
answer
to
to
of
all
of
our
doubts
without
more
john.
Please.
B
Thanks
very
much
juan
and
thanks
everyone
for
joining
as
well.
You
know
I'm
delighted
that
we
I
got
that
I
get
the
opportunity
to
speak
about
the
safe.
You
know
safe
and
noses,
and
the
safe
in
particular,
so
yeah
might.
As
what
I'm
saying
my
title
is
ecosystem
development.
I
know
this
is
safe
and
I
joined
the
nurses
last
year,
but
I've
been
you
know,
tinkering
with
blockchain
since
2015,
since
the
since,
since
ethereum
really,
you
know,
was
created
and
got
going
so
a
little
bit
about
gnosis
as
company.
I
won't.
B
Before
I
go
into
the
notice
safe
and
the
multi-stake
in
particular,
I
just
want
to
draw
you
know
the
draw
the
line
between
the
sand,
essentially
between
what
I
thought.
What
I
mean
by
externally
owned
accounts
versus
contract
wallets
so
generally
on
blockchains,
there's
two
ways
to
manage
funds,
there's
externally
owned
accounts
which
is
compatible
with,
for
example,
metamask.
B
B
What
the
gnosis?
What
multisig
means
is
you
know
it's
it's
it's
used
in
even
outside
the
blockchain
world.
Today
it
just
means
it's
a
type
of
digital
signature
that
makes
it
possible
for
two
or
more
users
to
sign
documents
as
a
group
and
a
real
like
an
end
more.
A
traditional
example
of
a
multisig
is
actually
docusign,
since
a
lot
of
people
are
agreeing
on
one
document
or
one
transaction
together,
and
they
all
sign
there
thereafter.
B
So
what
a
multisig
does
is
enable
you
to
define
you
know
how
many
owners
you
want
in
your
setup
as
well
as
how
many
signers
you
want
in
your
setup.
So
I've
got
four
owners
here.
Sarah
alice
bob
tim,
you
know
sarah
and
tim
use
metamask
as
their
main.
You
know
wallet
and
bob
and
alice
use
power,
wallets,
ledger
and
tresor.
B
B
Inherently,
actually,
you
know
compromised
it
yourselves
in
a
way,
since
you
know
you
don't
have
the
ability
to
do
four,
four
signatures,
so
that's
why
it's
always
kind
of
a
good
way
when
you're
setting
up
multi-signature
wallets
that
you
have
just
your
your
signing.
Threshold
is
just
below
one
of
your
owners,
so,
for
example,
three
out
of
four
or
four
out
of
five
or
two
and
three,
for
example,.
B
If
you
follow
so
yeah
quick
fact
about
moses,
safe
this,
we
have
about
15
billion
worth
of
ether
and
erc20s
being
stored
using
those
safe
contracts
at
the
moment
again.
To
reiterate
this
is
all
in
self-custody.
Those
have
no
control
of
these
these
funds
and
here's
a
few
examples
of
you
know
key
projects
or
companies
that
are
working
that
actually
use
their
noses
safe
and
bifinx,
for
example,
as
a
centralized
exchange,
uni
swap
as
a
decentralized
exchange
and,
of
course,
maker
used
the
gnosis
safe
for
a
couple
of
use
cases.
B
One
one
key
use
case
I
believe
maker
are
using
the
notes
to
save,
for
is
the
the
grants
program.
I
believe
that's
that's
going
to
be
that's
going
to
be
coming,
or
I
think
it's
probably
active
right
now,
but
yeah.
I
think
I
believe
that
that's
where
the
safe
is
one
of
one
of
those
safes
use
cases
right
now
and
of
course,
hopefully,
there's
gonna-
be
some
future
use
cases.
A
Yeah,
so
the
grant
was
being
run
by
the
maker
foundation,
and
now
we
are
migrating
that
towards
the
the
dao.
So
so
for
sure
this
is
one
of
the
use
cases
where
we'll
be
seeing
it
and
the
other
one
well
most
of
most
of
the.
The
probably
viewers
know
this,
but
governance
is
using
that
to
manage
the
budget
that
is
received
from
the
tao
to
assign
that
to
the
different
invoices
or
or
expenses,
but
yeah.
B
B
We
have
dao's
enterprises
and
institutions
that
are
also
using
safe,
since
they
all
share
the
same
key
requirement,
which
is
they
don't
want
a
single
point
of
failure
in
their
phone
setup
and
a
good
analogy
that
I
was
told
about.
You
know
why
multisigs
should
be
used
almost
nearly
all
the
time
is
because
I
think
it
was
the
bitco
ceo.
I
think
his
name
is
mike
belsha
and
you
know
he
was.
He
was
involved
in
bitcoin
wallets,
you
know
2013,
and
he
always
said
that
he
would
he
he'd.
B
He
would
always
use
a
multi-stake
as,
like
you
know,
as
the
as
his
first
and
only
implementation,
because
he
was
always
terrified
that,
if
his,
even
if
his
son
downstairs,
for
example,
got
a
hold
of
their
hardware
wallet
and
threw
it
at
the
window
or
spilled
a
lot
of
water,
you
know
on
his
notepad
that
contained
all
his
seed
phrases.
You
know
he
was
always
terrified
of
that
and
he
never
wanted
that
to
be
the
case,
for
you
know,
what's
how
how
his,
how
his
phones
could
be
compromised.
B
So
as
a
as
a
rule,
he
would
always
have
you
know
some
sort
of
multi-sig
set
up
for
his
funds,
and
I
think
that's
quite
true
today.
I
think
with
people
still
are
kind
of
that,
especially
in
d5
people
are
still
kind
of
of
the
opinion
that
you
know
if
they
use
metamask
and
metamask
alone
with
one
seed
phrase,
they'll
be
fine
in
the
long
run,
but
I
think
well,
there's
definitely
there's
definitely
more
secure
ways
to
do
this,
depending
on
the
use
case
right
and
yeah.
B
So,
unfortunately,
there's
no
single
best
answer
to
all
three,
but
because
it
depends
on
the
use
case.
But
there
are
some.
You
know
some
key
pointers
to
take
into
account,
and
we
were
discussing
this
briefly,
which
is
it's
advisable
to
use
more
than
one
owner
account.
Okay
and
that's
right,
so
I
shouldn't
just
create
a
safe
and
just
have
one
owner.
That's
a
meta
mask
account,
a
kind
of
you're
kind
of
defeating
that
you're
kind
of
defeating
the
purpose
of
having
you
know.
B
Extra
security
attributed
to
your
nurses,
safe,
so
use
more
than
one
owner
and
always
have
a
threshold
higher
than
one
and
what
trash,
what
a
threshold
higher
than
one
results
in
is.
It
means
you
have
essentially
a
maker
checker
process.
You
have
always
a
second
pair
of
eyes,
checking
every
transaction
and
that's
very
the
key.
You
know
security
consideration
there
is
that
if
it
protects
you
against
a
malicious
actor
that
was
in
your
setup,
for
example,
say
if
you
were
in
a
team
of
four
and
you
only
had
a
threshold
of
one.
B
So
your
setup
was
one
out
of
four.
If
one
of
your
team
members,
for
example,
wanted
to
steal
all
the
phones,
they
could,
because
the
threshold
is
only
one.
So
that's
why
it's
always
advisable
in
team
setups
and
even
in
individual
setups,
to
have
a
threshold
higher
than
one
so
at
two
three,
four
etcetera.
B
It
is
the
like.
It
is
a
good,
a
good.
A
good
standard
to
take
is,
you
know,
use
the
use,
the
wallet
that
your
owners
are
most
familiar
with,
but
also
strike
a
mix
between
hardware
and
software
wallets
and
if,
if
you're,
if
the
owners
are
familiar
with
hardware
wallets
and
the
use
of
hardware
wallets
and
that's
and
a
common
setup,
we
see-
let's
say,
for
you-
know,
groups
collectively.
B
Managing
funds,
is
you
have
one
owner
account
per
individual
and
then
use
a
threshold
of
three
so
which
means
you
know
all
transactions
are
double
checked
by
two
others,
and,
and
that's
that's,
definitely
a
it's.
It's
kind
of
at
a
time
a
common
set
of
pc
and
it
it
doesn't.
Actually
it's
it
enables
you
to.
Actually,
you
know
execute
transactions
at
a
at
a
better
pace
than
you
know
having
a
lot
of
owners,
you
know,
with
with
multiple
different
signing
accounts
against
that
safe.
I
think
it's
that's.
A
B
B
The
only
difference
really
is
that
its
private
key
is
actually
you
know
it's
been
abstracted
to
represent,
you
know
the
multisig
policy
and
then
once
all
the
multisig
policies,
once
the
criteria
is
met
by
the
multisig
policy,
say,
for
example,
all
the
metamask
or
the
hardware
hardware
owner
sign,
then
that
gives
you
access
to
the
to
the
private
key.
So
it's
abstract
to
that.
B
I
yeah
I
I
use
this
and
I
use
it
when
I'm
using
so
a
low
amount
of
funds,
and
I
definitely
use
a
multisig
with
just
one
out
of
one,
because
it's
the
most
efficient
way
and
it's
actually
a
great
way
for
me
to
interact
with
smart
contracts
and
just
from
a
ui
perspective
and
I'll
I'll
demonstrate
this.
Now
that
it's
a
there's
a
lot
more
features
enabled
because
it's
a
smart
contract
account
as
opposed
to
an
externally
owned
account
such
as
you
know,
metamask,
for
example,
and
I'll
I'll
I'll
run
through
that
here.
C
This
isn't
exactly
what
you've
been
talking
about
so
far,
so
you're
going
to
cover
it
later,
wanna
pass
fight,
that's
totally
fine,
but
I
know
one
of
the
considerations
we've
been
talking
about
with
multi-sigs
within
makers
in
the
future.
We
may
want
to
use
them
for,
like
certain
permission,
actions
like
putting
a
group
in
charge
of
you
know
changing
rates,
or
you
know
something
down
the
line
where
we
say.
Okay,
we're
going
to
trust
this
group
and
delegate
it
off.
B
You
know
connect
up
with
your
your
notes,
it's
safe,
but
the
reason
why
we
don't
the
reason
why
we
haven't
done
that
in
the
past.
Yet
is
because
you
need
we
need
we're,
we're
very
security
focused.
So
we
audit
all
the
contracts-
and
you
know
we
even
do
mathematical
proofs
against
those
contracts
as
well,
such
as
formal,
formal
verification.
So
if
you
add
a
module
that
we
haven't
audited,
you
know
we
we
it's
it's
not
as
secure
as
using.
You
know
the
the
open
source
solution.
B
B
Yeah,
absolutely
let's
go,
let's
do
it,
so
this
is.
This
is
essentially
the
the
gnosis
safe
application
interface.
This
is
a
web
interface,
but
you
can
access
notice,
safe.
You
know,
via
the
web,
via
a
downloadable
desktop
app
or
via
our
mobile
app,
which
is
compatible,
which
is
available
on
ios
and
android
for
even
the
more
tech
savvy
users.
Some
of
them
actually
just
interact
with
our
contracts
via
the
command
line.
That's
it
that's
so
you're,
that's
essentially
so
there
and
it
so
they
can.
B
Exactly
but
yeah
this
is
this:
is
this:
this
web
interface
is
accessible
via
you
know,
just
googling
notices,
safe
and
clicking
open,
open
app
from
our
website,
and
this
is
where
you
start
to
either.
You
know,
create
a
safe
or
load.
An
existing
state
that
you
have-
and
the
first
thing
I
have
to
do-
is
actually
connect
a
wallet
to
the
gnosis
safe
interface.
A
A
B
I
don't
want
to
over
complicate,
but
you
can
also
have
nested
gnosis
safes.
So
you
have
you,
have
a
safe,
that's
an
owner
of
a
safe.
If
you
follow-
and
that's
that's
completely
possible,
but
it's
always
recommended
that
in
those
setups
that
you
have
at
least
one
thing:
that's
not
a
safe,
for
example,
as
a
signer
as
a
signer
yeah,
okay.
So
I'm
going
to
connect
up
here.
So
I
just
click
connect
my
wallet.
I
can
choose
from
a
variety
of
different.
B
B
So
I
in
this
example
I'm
going
to
connect
via
my
meta
mask,
which
I'm
logged
in
currently
in
micro
as
a
chrome
extension
and
from
here
I
can
then
create
a
new
save
for
a
load
and
existing
safe.
So
imagine
I
was
I'm
a
member
of
a
team
and
my
team
has
asked
me
to
create
the
safe
on
behalf
of
our
team,
so
I
click
create
new
safe.
I'm
going
to
call
this
maker
team
safe.
B
I
copy
and
I
paste
it
in
here
and
you
can
see,
as
I
add
another
owner,
my
the
level
of
owners
go
up
as
well
as
I
can
change
the
policy
associated
with
that
as
well
as
we
were
discussing
so
then
for
this
example.
I'm
going
to
add
one
more
address
to
the
multisig.
I
want
to
make
it
a
two
out
of
three
team
three
and
then
you
can
see
once
again
we've
bumped
up
to
three.
I
want
to
beat
two
out
of
three
owners.
B
That's
well
a
ledger
using
metamask,
as
well
as
a
a
different,
a
different
wallet
and
yeah.
We
don't
take
any
transaction
fees,
not
as
notice
of
the
company.
The
only
transaction
fees
of
a
safe
is
the
inherent
gas
that's
needed
and
the
the
gas
increases
to
more
signers.
You
have
on
your
multi-sig
setup
so,
for
example
like
in
the
more
owners
the
more
expensive
it
is
in
gas
and
because
you're
assigning
different
addresses
to
the
smart
contract
and
I'm
actually
submit
and
gas
prices
are
quite.
B
B
I
I
could
have
used
wrinkly
there
to
show
you,
but
I
think,
there's
not
much
else
to
show
it
like.
Once
once
I
execute
that
transaction,
I'm
going
to
go
into
the
you
know
the
the
same
setup
as
I
have
with
all
my
current
safes
right
here.
So
I
kind
of
wanted
to
give
you
a
main
net,
a
main
net
version
to
show
that
it's
you
know
to.
C
B
C
B
B
Yeah
exactly
exactly
the
good
old
days,
so
I'm
going
to
quickly
just
load
up
an
existing
safe.
I
have,
and
so
this
is
the
an
example,
for
example,
safebd
address
that
I
have
and
the
after
I've
created
the
safe.
This
is
the
first
landing
page
that
I
land
on
anyway,
which
is
the
essentially
the
token
list
page
which
just
gives
you
a
list
of.
You
know
what
current
tokens
you
have
currently.
B
B
Correct
that's
correct,
so
you
would
have
to
start
sending
some
some
ether
to
this
address,
which
is
in
the
corner
here.
You
have,
you
have
the
link
to
ether
scan
or
you
can
just
copy
the
address
and
get
a
team
members
or
yourself
to
send
that
sense.
Some
tokens-
and
actually
you
know
you
start
using
the
safe
as
the
the
method
of
fund
storage,
an
example
here
I
can.
I
need
some
tokens
in
the
manage
list
corner
here.
B
As
I
have
that
contract
address
for
it's
a
similar
functionality
to
metamask
as
long
as
I
have
the
token
contract
address,
I've
got
the
token
symbol
then
I
can
add
any
custom
token
to
that's
erc20,
compliant
to
the
gnosis
safe
and
from
here
I
can.
This
is
where
I
can
start
sending
my
transactions
say.
For
example,
I
wanted
to
send
ether
out.
B
This
would
be
to
go
click
into
transactions
and
you
would
see
the
queue
of
transactions,
and
so,
if
I
had
any
transactions
that
were
pending
a
signature
for
myself
or
I
had
transactions
that
are
just
waiting,
I've
signed
a
transaction,
but
I'm
just
waiting
for
it
to
execute.
You
will
see
it
in
the
queue
here
and
for
any
and
a
historical
view
of
transactions
that
have
been
made.
You
just
click
the
history
tab
and
look
through.
You
know
all
the
various
different
transactions
that
have
taken
place,
be
it
you
know,
custom
contract
interactions.
B
A
Regarding
this
john
sorry,
yes,
when,
when
I
sign
when
I'm
a
co-signer,
I
see
the
unknowns
go
up
and
I'm
not
paying
any
gas.
So
someone
told
me
yeah,
that's
because
it's
not
denounced
on
your
wallet.
It's
announced
on
the
on
the
smart
contract
of
the
safe,
but
how?
How
does?
How
does
that
happen?
From
a
technical
point
of
view
like
how
come
I'm
signing
something
that
nonce
is
going
up
and
it's
not
there's
no
gas
being
moved
there?
I
don't
know
if
that's
a
clear
question.
I
hope
it
is.
B
No,
no,
I
I
get
you
and
I
I
would
I
would
it
gets
into
more
technical
details
here,
but
we
have
implemented
a
feature
called
gasless
signatures,
which
means
you
know
you
can
actually
sign
transactions
without
actually
you
know
incorporating
any
gas
and
that's
what
actually
that's
that's
what
increased
the
nons
but
yeah
I'll
have
to
with
that
quest.
You
know
a
little
technical,
a
tactical
answer
for
you,
because
yeah
there's
some
there's
some
good
code.
That
was
done
here
that
I
can't
add.
A
B
B
You
know
the
last
signer
is
executing
transaction,
but
we
can
also
you
can
also
sign
without
executing
the
transaction
so
say,
for
example,
I'm
the
last
signer
I
can
still
sign
and
validate
transaction,
but
I
can
choose
that
not
to
be
the
one
that
executes
it
and
in
that
case
someone
else
would
have
to
go
back
into
their
safe
via
their
desktop
or
their
mobile
to
actually
execute
and
pay
that
gas
and
that's
the
whole
kind
of
cast
castle.
Signature
points
once
again.
A
B
B
A
B
B
B
You
know
that
I
know
that
you
know
my
og
safe
or
my
safe
pd
addresses
are
here
and
I
can
you
know
I've
transacted
with
them
in
the
past,
and
I
have
them
readily
available
to
to
make
some
quick
to
make
some
quick
transactions
too,
and
I
can
also
create
entries
as
well
into
my
address
book.
So
it's
like
a
little
contact
list.
B
Now,
yes,
the
more
interesting
thing
is
the
safe
apps
section
and
what
safe
apps
are
is
essentially
it's
like
our
app
store
and
that
we
allow
third
parties
to
you
know
create
their
essentially
create
their
own
add
their
own
dapps
to
our
noses
safe
interface,
and
this
can
be
you
know
a
either
well-known
projects
or
even
just
a
developer.
You
know
creating
a
safe
app
for
a
very
specific
feature,
so
this
is
our
default
list
of
safe
apps
at
the
moment.
B
But
of
course,
if
you
have
a
custom
app
that
you
like,
you
can
simply
type
in
the
app
url
give
it
an
app
name-
and
you
know
agree
that
it's
a
third
party
and
simply
add
it
to
our
interface
and
that
simply
lets
you.
You
know
interact
with
that
dap
directly
from
within
the
gnosis,
safe
interface
and
there's
there
isn't
a
maker
there
isn't
a
maker
safe
app
yet,
but
we're
planning
on
you
know
when
the
grants
process
updates
again
we're
planning
to
make
a
proposal
to
get
another.
B
I
make
a
maker
safe
app
in
here
directly
but,
as
you
can
see
here
right
now,
for
example,
I
can
click
into
you
know
a
the
one-inch
exchange
disemployed
on
ipfs.
So
it's
you
know
even
if
one
inch
stop
hosting
their
own
interface,
so
I
can
still
interact
with
the
contracts
and
I
can
you
know,
exchange
directly
my
my
tokens
using.
C
B
A
C
B
B
Correct,
I
think
maker
actually
use
requests
right
now,
yeah
for
for
their
safe,
so
it
did.
That's
request
is
a
particularly
helpful
app
as
well
as
a
sablier,
for
you
know,
streaming
payments
to
a
dev,
a
developer
for,
for
example,
is
working
with
your
protocol
for
a
specified
amount
of
time.
You
know
we
have.
We
have
plenty
of
people
using
save
your
safe
app
to
stream
those
payments
from
the
safe
another.
A
B
Important
one
that
I
would
like
to
touch
on
is
the
wallet
connect
safe
app,
so,
if
you
so
for
any
other,
you
know
the
central
decentralized
application
under
adap.
That's,
that
is,
that
supports
wallet
connect.
All
you
have
to
do
is
simply.
You
know
copy
that
qr
code
or
uri
that
they
display
when
you're,
connecting
up
to
adap
and
paste
it
in
here,
and
it
can
automatically
connect
to
the
ear
your
nose
is
safe.
B
B
A
B
That's
the
same,
that's
that's.
A
wallet
connect
feature
right
there.
So
that's!
If
I'd.
If
I
wanted
to
interact
with
a
dap
outside
this
safe
apps
interface
in
the
native
dap,
I
would
use
what
connect
lca
as
a
first
and
foremost
okay
quickly
to
go
into
settings
now.
Here
I
can,
of
course
this
is.
This,
is
my
current.
I
can
look
at
my
current
owner
setup.
B
You
can
see
here.
That's
only
one
site,
one
owner
on
one
signer.
I
can
of
course
add
new
owners
to
this
safe
account,
safe
or
even
remove
it
or
even
remove
one,
for
example.
So
say
someone
from
my
team
has
left
and,
and
we
don't-
we
no
longer
want
them
to
use
a
use
be
assigned
on
our
safe.
We
can
remove
them
or
also
add
new
owners,
as
team
members
come
on
board
and
we
can
also
change
the
policy
associated
with
there
with
that
as
well
so
say.
B
If
I've
got
two
new
guys
coming
on
my
team-
and
my
I
want
to-
I
want
to
actually
up
my
security
and,
you
know,
add
an
up,
add
an
extra
person
to
the
policy
and
add
an
extra
signer,
and
I
can
do
that
by
changing
my
policy
using
the
safe
and
adding
a
new
owner
and
and
doing
that.
There
thereafter
back
to
someone's
question
about
the
modules
and
we
there's
a
couple
of
open
source
modules
right
now,
but
we
haven't
fully
audited
them.
B
Yet
it
was
created
by
the
community,
but
one
module
that
we
did
add
and
we
got
fully
audited
with
our
contracts.
Is
the
spending
limits
module
and
what
the
spending
limits
module
enables
you
to
do
is
say.
For
example,
in
my
setup
and
I
had
one
almost-
I
had
one
guy
a
part
of
the
team
that
is
a
almost
a
trader
he's
doing
daily
transactions
with
a
low
amount
or
even
a
high
amount,
and
we
don't.
B
We
want
him
to
kind
of
bypass
the
multisig
policy,
because
you
know
it's
it's
too
much
of
a
burden
to
get
four
or
three
people
to
sign
every
time.
Even
though
he's
interacting
with
a
very
low
amount
of
ether
or
any
token,
I
can
assign
that
specific
person
a
spending
limit,
so
I
can
choose,
you
know
who
you
know
who
are?
The
owners
gets
this
spending
limit
and
I
can
select
the
assets
so
ether.
Let's
say
they
get
a
specific
amount
of
ether
to
you
know
per
day
or
per
week
or
per
month.
B
B
And
you
need
the
you
need
the
multisig
policy
to
add
this
spending
limit
so
say
my
current
policy
is,
you
know
one
out
of
one
or
two
out
of
three
or
four
out
of
five.
I,
whatever
policy
is,
you
know,
is
attributed
to
that
safe.
At
that
moment
of
time.
That's
what's
needed
to
to
assign
this
beneficiary
or
spending
limit
so
you'd
have
to
you
always
have
to
follow
the
policy,
essentially
that.
A
B
B
That
says
one
day
at
a
time:
yeah,
it's
like
exactly
one
point,
one:
eighth:
every
day.
I
know
it
sets
after
a
day
yeah-
and
here
is
in
the
advanced
section.
This
is
where
again,
safe
modules
comes
into
play,
so
we'll
be,
you
know,
there's
currently
some
extra
modules
out
there
that
are
open
source.
You
can
learn
more
about
them
here,
but
this
is
where
you
can
get.
B
You
know:
extra
access,
control,
permissioned
access,
control,
permissions
and
add
them
integrate
that
with
your
current
safe
setup,
but
the
once
again,
we
have
to
kind
of
stipulate
that
the
community
version
right
now
is
has
all
the
audits,
all
the
audits.
The
full
solution
has
been
audited,
but
if
you're
adding
modules
that
haven't
been
audited,
then
of
course
your
there
could
be
some.
There
could
be
some
additional
security
considerations
that
yeah
it
should
definitely
be
considered.
B
So
we
recommend
that,
but
soon
we'll
have
you
know
an
extra
module
like
the
spending
limit
fully
audited
with
the
whole
safe
stack,
so
you'll
see
them
in
the
community
version,
then,
as
they
come
through
and
we
respond
to
the
pro
we
respond
to
the
product
backlog.
That's
given
from
our
community
to
this
yeah.
A
B
B
So
we
we
offered
a
safe
on
xdy
right
now,
that's
so
we
hope
and
we
host
the
the
safe
web
interface
on
xdi
as
well.
That's
our
that's
the
current,
that's
current
main
layer,
two
that
we
are
deployed
on
and
it's
the
only
one
that
gnosis
have
done.
Binance
smart
chain
have
actually
you
know,
deployed
our
contracts
to
binance
smart
chain
and
but
they're
hosting
it
themselves
we're
not
hosting
that,
but
we're
open
source.
So
you
know
that
that
is
allowed
to
be
done
and
it's
yeah.
B
B
Definitely
definitely
and
we're
we're
actively
looking
at
our
layer,
layer,
2
strategy
as
well
as
you
know,
other
twos,
where,
as
other
twos
come
out
and
you
know,
gain
significant
adoption
and
you
know
technical
maturity.
We
definitely
will
look
at
that
and
respond
to.
You
know
the
requests
that
we're
getting
from
the
community
on
that
yeah.
C
I
guess
are:
are
there
I
mean
there's,
obviously
a
lot
of
ways
you
could
use
your
your
multi-seg
right
so
probably
hard
to
have
a
one
size
fits
all,
but
are
there
any
sort
of
best
practices
around
number
of
signers?
We
obviously
like
n
minus
one,
for
instance,
but
when
writing
like
our
latest
multi-segment?
I
didn't
want
to
be
too
restrictive,
so
I
said
at
least
two-thirds
of
signers,
but
no
idea.
If
that
was
good,
recommended,
remember
good
recommendation
or
not.
B
I
I
think
so
I
think
so
again.
It's
it
take
into
account
a
number
of
transactions
that
you
expect
every
day
and
yeah.
I
think
I
think,
through
two-thirds,
two
and
a
two-thirds
of
of
signers
out
of
owners
is
a
good
practice
as
well
as
you're
going
up
the
level
as
you're
going
up
above
you
know
five
owners
or
six
owners.
Yes,
that's
that's
good,
but
again
yeah
the
the
most
common
setup
we
see
out
of
other
teams.
B
Is
this
two
out
of
three
and
three
out
of
four
set
up,
but
of
course,
when
you
have
bigger
you
know,
when
you
have
bigger
implementations,
you
can
have
five
out
of
seven,
that's
a
very
common
one.
We
see
as
well
and
we
theoretically,
we
support.
You,
know
an
unlimited
amount
of
owners,
but
it
gets
to
a
case
like
I
think,
at
about
40
owners
or
40
signers
that
it
gets.
Quite
you
know
quite
resource
resource
heavy
from
the
from
a
performance
perspective.
B
B
A
B
Again,
I
I
I,
I
would
definitely
point
you
to
into
this
help
center
article,
for
you
know
kind
of
refreshing
what
what
should
be
the
best
setup
but
yeah.
It's
it's
down
to.
You
know
your
use
cases
and
how
many
you
know,
members
who
want
to
be
owners
and
who
want
to
actively
actually
be
signers
as
well,
because
you
do
have
to
take
into
account.
You
know
how
how
savvy
or
how
familiar
they
are
with
using
owner
wallets.
B
You
know,
and
we
see
a
lot
of
we
see
a
lot
of
companies
wanting
to
you
know,
set
up
set
up
a
note,
safe
with
owners
that
have
very
little
insight
at
all
into
into
into
you
know,
blockchain
applications
and
ethereum,
which
is
definitely
something
that
you
know
it's.
We
wouldn't
really
recommend
we.
You
would
we're
still
we're
still
getting
to
that
place
where
that
user
experience,
where
anybody
can
do
it,
but
you
do
need
some
sort
of
knowledge
about.
A
D
Hey
john,
you
mentioned
that,
so,
if
you
have
five
individuals
participating
in
the
multi-sig,
you
said
you
could
send
out
a
text
message
is
that
right?
So
in
the
case
of
an
emergency
right
say
we
need
some
kind
of
action
taken.
I
guess.
How
would
that
work?
If
say,
one
of
the
multisig
individuals
is
in
tulum
mexico
having
himself
a
margarita
and
it's
not
responding
to
the
to
the
to
the
text.
Messages.
B
Yeah
yeah,
that's
a
very,
very
good
point,
a
very
good
question
and
sorry,
it
says
my
internet
connection
is
unstable.
Can
you
guys
hear
me?
Yes,
oh
perfect,
perfect,
no,
that's
a
great
question
and
we,
the
mobile
app,
gives
push
notifications,
which
is
which
is
always
useful,
and
so,
if
you're
signing,
if
you
have
a,
if
you
have
a
signer,
that's
you
know
inherently
using
the
mobile
application.
They
will
always
receive
notifications
when
they
have
transactions
to
sign.
B
But
in
terms
of
solving
that
mexico,
margarita
example
we're
still
trying
to
we're
just
trying
to
like
you
know,
take
on
how
exact,
what's
the
best
way
to
solve
that,
because
I
think
that's
a
communication
issue
right
is
in
if
they're
not
looking
if
they're
not
looking
at
their
laptop
or
their
phone.
How
do
you
get
in
contact
with
someone
right?
Do
you
send
it?
Do
you
give
them
a
pager?
You
know
it's
a
it's.
B
I
think
it's
a
communication
problem,
but
in
terms
of
what
we
see
in
no
safe
implementations,
a
lot
of
people
talk
offline
via
whatever,
via
signal,
via
slack
via
telegram,
in
terms
of
hey,
I'm
after
proposing
this
transaction.
Can
you
sign
this,
for
example,
or
even
you
know,
in
the
multi,
in
a
mobile
application,
you
know
you
have
someone
constantly
checking
their
phone
or
someone
constantly
logging
into
their
notice
safe
to
check
their
queue
and
also
check
the
notifications.
B
B
Yeah
and
that's
that's
that
and
that
goes
outside
the
safe,
for
example,
like
we
don't
have
any
you
know,
communications
being
triggered
to
mobile
phones
or
email
addresses
via
the
safe
work
or
trustless.
We
want
to
be
as
trustless
as
possible,
so
we
would
leave
that
in
the
hands
of
the
teams
themselves
offline,
how
they
want
to
communicate
with
each
other
about
that.
But
as
far
as
we're
concerned,
we
communicate
about
transactions
via
the
nosa
safe
interface
as
well.
As
you
know,
the
desktop
version
and
the
mobile
app
version.