►
Description
Join Richard & Barry as they talk us through multisig wallets, how they work, and where they feature in our future plans
A
A
We
all
know
this
transaction
is
done
by
most
clients
like
or
status,
AB
migrated
to
metamath,
etc,
and
they
require
only
a
single
signature
and
were-
and
whoever
has
this
private
key
associated
with
the
address
can
control
the
funds.
That
means
that
you
do
not
require
approval
from
anyone
to
perform
any
transaction
next
slide.
Please.
A
A
A
A
What
signatures
are
required
to
spend
the
funds
relating
preventing
one
supposed
to
spending
the
domani
without
approval
of
the
other?
The
third
use
case,
the
parent
seven
account
for
check
for
a
child
for
kids.
The
kid
can
expend
money
with
with
the
approval
of
either
parent
and
money
cannot
be
taken
away
from
the
child
from
the
child
unless
what
parents
agree
and
the
final
use
case,
the
factor
authentication
world
where
one
private
key
is
on
your
primary
device.
A
B
A
B
So
I'll
talk
a
little
bit
about
now,
some
of
the
use
cases
from
the
perspective
of
an
organization,
especially
since
statuses
and
organization.
So
we
are
thinking
about.
How
are
we
using?
How
does
a
multi-sig
wallet
play
into
what
status
is
trying
to
do
and
where
status
is
going,
but
in
general,
when
you
think
about
how
organizations
have
to
do
things,
especially
around
finance?
Here
are
a
couple
examples
that
that
apply
right.
B
Now,
there's
also-
let's
say
you
know:
buyer
buyer
seller
with
a
trustless
escrow.
So
there's
three
parties
involved,
the
buyer,
the
seller
and
the
escrow
buyer
commits
money
with
this
and
and
with
the
seller
and
a
third-party
arbitrator.
If
the
transaction
goes
smoothly,
then
both
buyer
and
sellers
signed
the
transaction
to
forward
the
money
to
the
seller.
B
If
something
goes
wrong,
they
can
sign
a
transaction
to
refund
the
buyer
if
they
can't
agree,
they
both
appeal
to
the
third
party,
who
will
arbitrate
and
provide
a
second
signature
to
the
party
that
it
deems
deserves
it,
and
the
arbitrator
can't
steal
the
money,
as
they
only
have
one
key.
You
know:
decentralized,
cold
storage,
vault.
Of
course
we
hear
about
how
exchanges
are
hacked,
and
this
is
really
and
usually
when
you
hear
about
it,
it's
it's
because
they
weren't
keeping
their
funds
in
cold
storage.
B
They
usually
were
keeping
in
some
kind
of
a
hot
wallet,
but
the
other
issue
with
cold
storage
is
who's.
Gonna
hold
the
key,
so
you
could
have
a
multi-sig
cold
storage
wallet
where
one
of
the
keys,
let's
say,
for
example,
is
held
in
one
location.
The
other
is
like
in
a
bank
safe
and
copies
of
the
third
key
are
distributed
in
a
different
physical
location
right,
so
even
if
the
any
one
location
gets
compromised,
the
the
key
is
not
it's.
It's
not.
B
It
makes
the
attack
you're
much
harder
right,
so
the
home
vault,
for
example,
is
not
vulnerable
to
raiding
or
burglary,
because
spending
the
money
requires
a
visit
to
either
the
other
location,
the
bank,
the
office
or
whatever
the
case
may
be
also
losing
access
to
one
of
the
locations.
Maybe
in
the
case
of
like
a
fire
or
a
flood,
doesn't
mean
you've
lost
access
to
the
funds
as
well.
So
from
an
organization
perspective.
That's
like
a
good
like
disaster.
B
We
start
to
think
of
these
scenarios,
where
how
are
we
gonna
actually
manage
these
contracts?
Usually
often
when
a
contract
is
deployed,
some
address
usually
the
address
that
deployed.
It
is
the
controller
and
usually
that's
like
in
in
in
our
case
like
when
I
deploy
a
contract
I'm
effectively
the
control
over
that
contract,
and
even
though
the
contract
is
on
is
on
aetherium.
B
It's
not
really
decentralized
if
one
person
can
control
the
contract,
so
the
immediate
solution
to
solve
that
problem
without
really
rethinking
the
whole
architecture
of
the
contract
is
to
transfer
that
controller
or
the
owner
to
a
multi-state
wallet.
So
then,
of
course,
the
next
question
becomes:
okay,
who's
going
to
be
like--just
operationally.
The
next
question
becomes,
who
is
gonna,
be
on
that
multi-sig
wallet
and
how
is
it
going
to
be
used
and
how
our
decisions
going
to
be
made?
B
And
so
all
these
questions
they
arise,
and
we
start
to
realize
that
there's
there's
like
very
simple
things
that
it
seems
like
they
should
be
simple
problems,
but
when
you
actually
need
to
when
you
actually
need
to
get
things
done,
you
realize
that
there's
actually
a
good
amount
of
issues,
and
so
we
also
long
term.
If
we
want
to
become
a
dhow,
we
we
really
have
to
think
about.
Well,
if
have
all
these
issues
right
now,
just
using
multi-sig.
B
B
But
if
you
want
to
have
like
a
doubt
where
the
entire
organization
or
an
entire
community
is
involved
in
decision
making
processes
you
you
really
need
to
think
about.
How
do
we
get
from
where
we
are
to
there
right
and
so
like
I,
don't
know
what
what's
the
possible
evolution
between
here
and
that
and
and
getting
to
a
doubt.
B
We
don't
know,
but
it's
clear
that
we're
still
in
pretty
early
days,
because
when
we
speak
when
we
speak
with
people
and
it's
clear
that
there's
just
not
that
many
people
using
multi-sig
well,
it's
it's
not
something
that's
used
very
commonly,
and
it
seems
like
at
least
that
is
gonna
start
to
change
as
more
contracts
get
deployed
and
people
realize
what
it
means
to.
Actually
people
starts
to
take
decentralization
seriously
and
I
guess
I
guess
the
other.
B
Yet
these
things
are
still
being
tested
and
evaluated
to
see
how
these
different
dau
stacks
for
lack
of
a
better
word
are
secured
and
again,
security
is
sort
of
like
a
broad
term,
because
you
could
have
security
from
from,
in
the
sense
that
the
actual
contracts
don't
work
as
expected
like
they
have
some
kind
of
bugs
or
secure
security
vulnerabilities.
That
would
allow
a
hacker
to
do
something
like
drain
all
the
funds
from
the
wallet,
but
you
also
have
things
where
you
just
may
end
having
some
kind
of
like
gridlock,
where
the
contract
technically
functions.
B
But
you
can
envision
a
future
where
that's
like
a
stepping
stone
to
full-on
dows
okay,
so
that
actually
should
have
showed
the
slide.
Now,
while
I
was
talking
but
yeah
just
just
to
rehash.
You
have
increased
decentralization
speaking
about
our
specific
wallet,
which
we've
been
testing
and
you
can
join
us
in
multi
stage,
evolution
on
slack
our
main
net
wallet
right
now.
It
has
seven
unique
key
holders,
they're
distributed
globally
among
seven
deformations
and
four
continents,
so
you
can
that
provides
pretty
robust,
I,
guess,
distribution
and
decentralization.
B
You
know
against
I
guess
all
kinds
of
different
attack
vectors
all
right
again,
because
in
our
case
we
require,
let's
say
three
of
three
of
us:
three
signatures.
If
one
of
the
key
holders
lost
their
key,
that
doesn't
mean
we've
lost
access
to
the
multi-sig,
so
there's
that
disaster
recovery
that
benefit
that
it
gives
you,
whereas
if
just
one
private
individual
one
individual
held
the
key
and
they
lost
that
key
well,
we
basically
lost
access
to
that
wallet
that
address.
B
But
you
know
with
the
benefits
there.
There
comes
a
lot
of
problems
that
and
that's
really
sort
of
what
we
want
to
highlight
and
and
get
more
people
thinking
about
to
figure
out
what
are
some
possible
solutions,
and
some
of
these
are
a
lot
of
them,
are
like
user
experience
solutions,
but
it
requires
a
lot
of
ad
hoc
coordination
and
we
can
demonstrate
this
in
a
bit
but
effectively
in
order
to
create
a
transaction
in
a
multi-state
wallet.
B
B
B
How
do
you
gather
all
these
people,
especially
when
they're
distributed,
and
make
these
kind
of
decisions
in
a
timely
manner?
There's
there's
really
no
no
good
way
right
now,
and
so
it's
been
very
ad
hoc.
It's
been
just
pinging
on
slack,
it's
kind
of
kind
of
trying
to
marshal
people
around
and
and
and
getting
things
done
that
way.
The
interfaces
for
transactions
and
multi
SIG's
are
pretty
bad
they're,
definitely
not
designed
for
interacting
with
smart
contracts,
so
in
adapt
it
for
our
multi
sick
that
execute
a
transaction.
B
It's
just
not
human,
readable.
It's
it's
very
hard
to
read
for
for
the
average
person
which,
basically
that's
actually
a
little
bit
of
a
security
issue
as
well
right.
But
it's
also,
if
you
are
asking
people
to
confirm
a
transaction,
you
know
how
can
they
they're?
Just
taking
your
word
that
that's
actually
the
transaction,
it
should
be
if
they
can't
clearly
understand
what
the
transaction
they're
confirming
is.
B
Also
the
current
the
current
wallet
is
limited
to
50
key
holders
and
if,
if
we
want
to
expand
that
dice
to
be
changed,
but
that
that
compared
to
some
of
the
other
problems
is
relatively
trivial
that
could
be
expanded,
but
still
given
today,
even
status.
All
status,
for
example,
wouldn't
be
able
to
use
a
single
multi-sig
and
just
to
sum
all
this
up.
It
really
just
leads
to
exponential
coordination
costs.
If
you
have
a
multi
sig
wallet
that
requires
two
confirmations
compared
with
a
multi
sig
wallet
that
requires
three
confirmations.
B
Just
our
experience
has
been
that
it's
been
like
not
it's
been
like
a
to
the
third
power
harder
to
get
three
people
to
sign
off
a
transaction
than
it
is
to
people
to
to
confirm
a
transaction.
So
you
start
to
get
to
like
five
people.
It's
just
it's
exponentially
harder
to
get
five
people
together,
coordinated
to
sign
a
transaction
that
it
is
to
get
to
three
people
together.
B
B
Okay,
so
I
guess
some
of
the
things
we
just
talked
about.
We
can
we
can
demo
right
now.
I
will
share
my
screen.
Well,
we'll
try
to
do
a
live
demo.
If
it
fails,
we
have
a
premade
recording,
but
we'll
we'll
see
how
this
goes.
So,
just
in
the
interest
of
time
as
well,
we'll
do
a
simple,
a
simple
transaction
where
we
just
send
the
transaction,
not
a
smart
contract
transaction
and
so.
B
B
Here
we
can
see,
are
the
owners
of
the
wallet
and
the
it
because
it
because
actually
something
that
should
be
pointed
out,
I
think
one
fundamental
difference.
We
didn't
talk
about
before
in
multi-sig
wallets,
actually
came
first
from
from
Bitcoin
they're
part
of
the
Bitcoin
protocol,
but
they're
not
in
in
aetherium
they're,
actually
not
part
of
the
protocol.
But
that's
okay,
because
in
theory-
and
we
have
something
more
general,
we
have
smart
contracts.
B
So
a
multi-sig
wallet
on
aetherium
is
actually
just
a
smart
contract,
so
that
allows
us
to
do
more
flexible
things
like
actually
change
who
the
owners
of
a
multi-state
wallet
are
or
add
new
owners
to
a
particular
multi-sig
wallet
or
replace
them
or
remove
them,
which
you
could
see
from
from
these
options.
Here
are
so
I'm
gonna
try
sending
a
little
bit
of
eath,
which
is
actually
held
by
the
multi-state
wallet
to
Richard
and
I
will
just
show
how
that
might
might
go.
B
So
we'll
just
then,
let's
say
a
tenth
of
a
nice,
and
this
part
is
very
much
just
like
using
a
standard
wallet
right,
we'll
just
confirm
the
transaction,
and
we
have
our
confirmation
in
meta
mask
and
we'll
just
confirm
it,
and
the
transaction
was
sent
once
it
minds.
It
should
be,
it
should
be
visible
in
the
actual
wallet
and
then
at
that
point
Richard
would
have
to
there.
It
is
so
our
our
transaction
was
mined.
We
see
it's
it's
in
the
wallet
it
has
not
been
executed.
B
It
has
one
confirmation
for
myself
in
our
test
net
wallet.
We
only
require
two
confirmations
for
a
transaction
to
go
through
so
now,
Richard
can
Richard,
basically
or
someone
in
the
wallet
has
to
one
of
these
owners
has
to
has
to
come
in
and
confirm
this
transaction
for
it
to
actually
go
through
Richard.
Do
you
want
to
show
how
you're
gonna
do
that
or
just
go
ahead
and
do
it?
Yeah
I
would
share
my
screen.
Okay,.
C
A
A
A
A
B
Everyone
see
my
screen:
okay,
mm-hmm,
okay,
yeah
and-
and
that's
just
one
of
many
different
multi-sig
type
implementations
that
was
the
gnosis
multi-sig
wallet
that
we
that
we
use
just
because
it's
been
around
for
a
while.
It's
been
proven,
it's
been
tested,
it's
been
audited,
so
we
feel
you
know
fairly
securing
and
using
it.
B
B
Building
their
next
iteration,
which
is
the
safe,
is
user
experience
just
creating
a
much
better
user
experience
for
the
wallet,
but,
of
course,
there's
other
issues
as
well
as
I,
just
Gatsby's,
but
I
think
that
was
their
one
of
their
primary
concerns,
at
least
for
for
safe
yep,
which
so,
after
all
this,
we
can
also
talk
about
other
things,
and
you
know
what's
next,
you
know
for
multi
cities.
Well,
obviously,
UX
improvements
and
the
current
functionality
is
is
like
low
is
just
well
hanging
fruit.
B
That
seems
like
there's
just
a
lot
of
a
lot
of
areas
to
improve
and
just
simple
things
like
being
able
to
interact
with
smart
contracts
in
a
straightforward
way.
The
same
way
that
you
might
interact
just
using
the
status
wallet
or
meta
mask
with
with
the
DAP
is
definitely
very
desired,
but
you
could
also
start
to
see
other
functionality.
That
is
not
implemented,
at
least
in
these
early
versions
of
multi
SIG's.
B
That
start
to
bring
us
closer
to
a
Dow
right
like
what
about
the
opportunity
to
for
right
now,
you
can
basically
either
confirm
a
transaction
or
you
can
abstain
from
confirming
it
or
what
about
giving
someone
the
option
to
deny
a
transaction
where
now,
if
somebody
denies
a
transaction
now
the
threshold
goes
up.
So
if
normally
you
require
two
confirmations,
but
if
one
of
the
key
holders
denies
a
transaction
well
now
you're
going
to
require
five
confirmations,
so
you
could
create
some
kind
of
rules
like
that.
B
You
know
so
that
those
are
some
interesting
areas
to
explore,
which
starts
to
bring
us
again
closer
to
what
we
might
envision
some
some
some
kind
of
roles
inside
of
the
Dow
or
or
perhaps
some
of
the
components
inside
of
a
doubt,
because
I
mean
we
can
we
don't
really
know
what
that
might
look
like
today,
but
it
might
be
a
combination
of
all
kinds
of
things
for
different
types
of
organization.
You
know
components.
B
State
based
voting
is
something
to
consider
right.
In
our
case,
it
might
be
how
much
SNT
does
each
key
holder
have
in
their
wallet
and
you
may
say,
need
to
need
to
get
a
certain
percentage
of
the
total
S&T
allocated
to
a
transaction.
For
example,
if
one
person
holds
no
30
percent,
you
need
to
have,
let's
say
more
than
50%
of
the
S&T-
that
all
the
key
holders
hold
allocated
to
a
transaction.
B
So
if
one
person
holds
one
person
might
hold
30
percent
of
up
to
that
SNT,
another
person
might
hold
ten
percent,
and
so
some
people
will
have
more
weight
in
in
their
vote
to
approve
a
transaction
because
really
right
now,
it's
not
so
much
a
vote.
It's
really
just
a
confirmation,
but
now
we're
talking
about
perhaps
moving
towards
actual
voting
to
get
a
transaction
to
go
through.
We
can
think
about
role
based
rules
right.
Maybe
somebody
who
has
a
role
of
being.
B
Let's
say
a
finance
manager
only
needs
one
other
confirmation
to
do
a
transaction
as
opposed
to
people
who
don't
have
that
role.
They
might
need
three
or
four,
which
is
very
common
today
in
organization.
So
it's
it's
easy
to
see
that
that's
something
that
might
be
needed
might
be
needed.
Value-Based
rules
as
well,
where
it's.
This
is
something
you
usually
see
in
organizations
as
well,
where
checks
they
have
to
be
written
over
a
certain
size
need
multiple
signatures,
so
same
thing.
Here,
transactions
over
a
certain
size
might
need,
let's
say
five
signatures.
B
Instead
of
the
normal
two
or
three
same
thing,
maybe
you
could
do
value
based
on
a
time
period
where,
over
a
given
time
period,
if
the
value
amount
transacted
in
a
multi-sig
well
exceeds
some
threshold,
then
the
amount
of
confirmations
needed
goes
up
right.
So
that's
like
setting
some
kind
of
value-based
quota
for
a
given,
which
again
you
see
in
a
lot
of
organizations
today
as
well,
there's
like
certain
limits
on
on
what
certain
departments
may
be
allowed
to
transact
and
after
that
they
need
additional
authorization.
B
B
D
Thanks
Barry
I've
got
a
couple
of
questions.
If
you
don't
mind,
yeah
sure
cool,
so
the
first
one
is,
we
said:
deploying
contracts
would
be
more
decentralized
with
a
multi
sig
wallet
I
mean.
Are
you
referring
to
contracts
that
have
a
I
guess,
a
specific
role,
we're
by
the
the
person
who
the
or
the
count
that
deployed
the
contract
has
access
to
specific
functions.
B
So
by
now
moving
it
by
transferring
the
ownership
of
a
my
transfer
changing
who
the
controller
is
from
the
individual
to
a
multi
sig
wallet.
Now
one
individual
can't
can't
do
that
there.
There
has
to
be
a
whole
multi-state
process
to
execute
that
transaction
without
changing
the
actual
smart
contract,
because
from
the
smart
contracts
perspective
it's
still
just
one
address
is
the
controller,
but
that
address
happens
to
be
a
multi
sig
wallet
which
no
one
person
has
control
over.
So
that
already
starts
to
decentralize
it,
because
no
one
person
is
the
controller
of
that
contract.
D
B
Right
now
in
in
this
wallet,
anyone
can
create
a
transaction
to
add
or
remove
a
key
holder,
but
you're
gonna
need
the
confirmations
you're
going
to
need.
The
you're
gonna
need
the
other
key
holders
to
confirm
that
transaction
as
per
the
rules
of
that
particular
multi-sig.
You
know
in
our
case
in
in
in
that
test
net
case.
It's
one
other
confirmation
yeah,
but
you
know
these,
since
these
are
again
since
on
a
theorem.
Multi-Sig
wallets
are
really
just
smart
contracts.
D
B
Agree
with
that
I'm,
that's
something
we
we've.
We've
talked
about,
I,
don't
know!
If
it's,
if
like
extensions
as
the
solution,
it
could
be,
you
know,
having
maybe
like
a
dedicated
whisper
channel
around
having
like
a
group
chat
around
the
particular
multi-sig.
That
could
be
an
option.
I
mean
there's
like
right.
It
could
be.
It
could
be
useful
if
you've
got
like
an
actual
status
notification
in
your
app
when
there's
a
confirmation
pending
yeah,
so
I
know,
there's
a
lot
of
there's
a
lot
of
different
ways:
I
I
don't
have
an
answer
to
this.
B
D
B
Well,
the
part
of
this
is
also
I'd
like
to
clarify
it,
but
currently
I'm
currently
like
the
wallet
we
just
demoed,
is
independent
of
of
the
status
wallet
right.
You
could
interact
with
it
using
the
status
wallet,
but
it
doesn't
need
direct
direct
integration
with
it.
Although
to
do
a
smart
contract
transaction
on
mobile
using,
like
status,
would
I
think
be
extremely
difficult,
like
even
significantly
more
difficult
than
it
already
is
on
desktop
just
because
of
getting
the
actual
parameters.
Pasting
them
in
the
ABI.
B
All
that
stuff,
maybe
to
confirm
it
on
mobile,
would
be
pretty
would
be
straightforward.
The
hardest
part
is
creating
the
transaction,
but
there's
there's
definitely
people
thinking
about
it.
I
mean
something
that
I
I
would
love
to
see
is
for
the
user
to
be
able
to
assume
the
role
of
the
actual
multi-sig
when
they're
using
adapt
so
like
you
can
like
in
meta
mask
or
in
status
you
can
choose
which
account
you
want
to
use.
Why
not
be
able
to
choose?
B
Choose
the
multi-sig
as
an
account
and
you're
just
you're
browsing
adapt
as
a
user
of
the
multi-sig,
and
then
it
becomes
really
simple
to
create
a
transaction
in
the
multi-sig
when
you're
using
a
death.
That's
money,
that's
something!
I
personally
think
would
be
helpful,
but
I
don't
know.
If
that
answered
your
question
in
full.
It.
C
C
That's
what
is
exactly
what
you
suggested
that
you
can
take
the
role
as
a
multi-sig
wallet
and
and
interact
with
the
apps
like
in
the
mist
using
that
that
I'm
not
sure
if
it's
two
works
but
because
I
didn't
try.
It
browsing
the
apps
recently
with
mist,
but
it's
use
it
to
work
and
I
suggest
that
this
should
happen
for
in
the
entities
in
States.
So
I
see
that
there
is
these
two
things
there
is
a
multi-sig.
C
That
is,
the
purpose
is
to
bring
different
individuals
sign
a
transaction,
and
there
is
also
in
the
entity,
then
do
something
that
you
mention
it.
That
is
the
two
factoring
authentication.
So
we
plan
to
have
the
two
factor:
intelligent
education
within
the
entities,
so
you
could
like
have
the
these
stages
in
your
desktop
and
in
your
mobile,
so
to
confirm
a
transaction
like
maybe
a
confirmation
from
these
two
devices
so
that
that's
that's.
Why?
When
I
had
to
comment.
B
C
Also
saw
they
notice
a
new
wallet
and
they
have
some
very
nice
improvements
like
Moochie,
send
comment
which
you
can
send
a
batch
of
transactions.
For
example,
let's
say
that
you
will
want
to
do
approved
in
a
cow
parts
for
a
year
seat
when
a
transaction,
so
you
can,
you
can
specify
in
the
in
the
submission
of
the
transaction
organ
as
a
safe,
multiple
transaction
to
do
in
in
bet
order
that
you
specify.
So
when
you
win-win
everyone
confirms
it
is
a
good
sale
in
that
order,
so
it's
safer
in,
of
course,
cheaper.
C
If
you
do,
if
you
batch
this
transaction
because
you
just
have
to
pay
once
they
took
the
minimal
fee
of
a
transaction
also,
they
are,
they
are
also
implementing
gases.
Abstraction,
sometimes
I,
know
P,
as
relating
to
did
their
solution
as
well,
and
as
we
are
doing
for
status
in
that
is
so
I
think
that
maybe
we
should
try
to
move
move
onto
not
safe.
If,
when
we
find
ourselves
comfortable
with
its
security,
I
mean
everything
around
it
because
seems
like
they
are
doing
a
great
job.
B
Yeah
I
definitely
agree
with
that:
I
I,
actually
I'm,
all
forward
for
using
the
gnosis,
safe
I
believe,
like
they
already
released
they're
doing
like
two
versions
of
it
right.
One
is
for
individuals
for
things
like
creating
an
identity
and
the
two-factor
authentication,
which
I
think
they
are
really
released.
I
think
the
only
reason
we
didn't
end
up
using
it
in
internally
for
testing
is
because,
though
the
version
for
organizations
they
they're
still
testing
and
they
they
haven't,
made
the
final
release.
B
C
So
you
said
that
is
really
difficult
to
make
a
transaction
in
the
mood
Zig.
Nothing
would
see.
I
totally
agreed
that
it,
because
that
you
I
was
not
done
for
mobile.
It's
just
that.
I'd
buy
that.
So
you
see
everything
very
soon,
zoomy
that,
like
like
in
a
desktop
and
yeah
in
face
in
the
name
ABI
softly
difficult.
So
we
should.
We
should
do
something
about
this
for
for
the
states
for
our
users,
because
that
s
as
they
you
say,
the
in
presentation.
C
That
was
more
engaged,
but
we
could
also
have
you
also
mentioning
about
voting.
I.
Think
that
that
should
should
we
should
go
more
for
our
democracy
systems
and
then,
like
don't
make
a
contract
like
I'd
like
a
mix
into
the
multi-sig
in
the
mockers
in
a
voting,
democracy
I
think
that
would
feel
a
bit
strange.
I
think
we
should
use
the
mood
to
see
while
we
are
testing
our
dowel
systems
and
when
we
wear
those
systems
are
proven
safe.
B
And
and
those
ideas
that
we
posted
there
when
we
talk
about
multi-sig
evolution,
we're
not
necessarily
saying
that
the
multi-sig
itself
has
to
sort
of
move
in
that
direction,
but
the
thing
about
the
I
guess
the
real
thing
is
also
like.
With
these
dow
based
systems
is
they're
so
different
from
anything
the
average
person,
even
the
average
just
wallet
user
is
used
to
that,
make
it
explaining
it
in
getting
them
to
use
it.
It
may
be
very
complicated.
B
It
may
just
be
so
such
a
large
hurdle
that
they
may
never
even
use
it,
whereas
once
they're
already
used
to
using
a
multi-sig,
then
you
could
say
hey
now
we
have
for
this
particular
contract.
We
have
we're
using
we're
using
this
database
system
or
this
voting
based
system-
and
you
say:
listen,
it's
basically
like
using
your
multi-sig,
but
you
can
now
deny
confirmations
or
it's.
It
I
think
it's
really
just
a
way
of
framing
it
to
say
that
that
these
other
systems,
we
once
you
get
people
using
a
multi-sig
wallet.
B
B
Oh,
it's
like
a
multi-sig,
but
with
this
one
or
two
extra
features,
as
opposed
to,
if
you
just
throw
all
those
features
of
like
liquid
democracy
or
like
some
kind
of
job,
a
system
at
them,
it
may
be
so
much
that
they
just
don't
even
know
where
to
start,
and
they
just
sort
of
don't
even
use
it,
but
yeah
I
think
we're
all
sort
of
thinking
in
the
same
direction.
They're.
Also
you
just
jogged
my
memory.
B
It
might
be
possible
to
design
some
kind
of
a
state
planning
solution
where
maybe
there's
like
the
identity
wallet,
but
maybe
there's
like
some
kind
of
a
heartbeat
function
where,
after
a
certain
amount
of
time
of
someone,
not
interacting
with
that
wallet,
you
may
be
something
equivalent
to
let's
say
two
years
or
a
year
or
something
like
that.
Then
other
key
holders
are
now
able
to
access
that
wallet
that
that
person
designated
like
their
family
or
so
forth.
B
So
I
think
that
could
also
be
a
pretty
big
one,
I
think
just
because
the
space
is
so
young.
There
may
not
have
been
that
many
people
that
have
like
passed
away,
that
this
is
become
an
issue
or
maybe
the
ones
that
have
maybe
their
family
didn't
even
know
that
they
had
crypto
Holdings
to
pass
on,
and
so
this
is
not
such
a
large
issue
that
this
is
not
even
issue.
People
know
that
exists,
but
I,
it's
it's
an
issue
with
traditional
assets,
so
why
would
it
not
be
an
issue
with
crypto
assets
as
well?
C
They
just
these
stages
should
actually
make
some
way
that
when
we
implement
this
in
vain
is
that
people
are
encouraged
to
set
up
these
security
features
to
them.
So,
like
the
friends
record
raid
or
this,
as
you
said,
a
bad
man
switch,
it's
cool
things
that
that
are
really
important
for
social
reason,
because,
like
this
would
lock
in
these
tokens
is
actually
bad
for
the
economy.
C
Let's
say
if
it's
someone
that
he's
too
too
rich,
that's
out
there
talking
who's,
locking
you,
like
you,
reduce
it,
a
the
supply
of
the
these
tokens
that
are
in
circulation,
so
you
you
can
like
in
100
years.
Maybe
you
don't
have
a
city
available
anymore,
because
it's
all
locket
somewhere,
so
it
can
be
a
problem.
So
we
should
think
ahead
to
prevent
these
situations
from
from
happening
in
what
you
said
about
dolls.
Looking
like
a
multi-city
I,
totally
agree
with
you.
C
I
see
that
multisig
is
is
like
one
account
is
a
vault,
but
any
it's
like
a
what
you
see
with
a
doll,
but
instead
of
an
account
is
a
is
that
talking.
That
is
a
vote
and
the
holder
of
the
tokens
sign
for
each
talking,
so
it
is
basically
the
same
way
and
the
amount
of
signatures
needed
is
a
quorum
that
we
we
set
up
to,
but
that's
a
really
interesting.
C
B
C
I-I
think
I
agree
about
the
the
shat
about
the
having
a
group
chat
for
the
multisig.
There
is
a
early
feature
from
status
that
was
chat
bots.
We
might
want
to
resurrect
that
and
bring
that
one
to
two
DS
feature,
because
this
chat
bot
could
be
like
the
the
robot
that
is,
they
made
the
contract
like
and
every
time
I
event
is
fired
on
that
contract.
Then
the
this
robot
to
show
a
message
in
that
group
saying:
oh,
you
need
to
confirm
it
or
that
a
confirmations
require
it.
C
Is
it
cool
to
or
console
add
all
the
designs,
so
we
can
make
some
that
look
like
so
I
use
it
but
she's
a
robot
that
right
that
respond
over
the
events
or
contract
right
that
that
would
be
perfect.
So
but
first
we
need
minutes
the
problems
to
implement
the
group,
shots
that
are
disproved
communication.
C
B
C
The
problem
of
chat,
BOTS
also,
is
that
you
need
a
server
to
run
it,
so
we
don't
use
servers
and
stages.
Instead,
we
use
that
decentralize
it
status
nodes.
So
we
probably
going
to
have
this
instant
devices
running
bots
depending
on
the
type
of
the
bot,
because
if
it's
because
they
haven't
to
receive
an
event,
you
need
to
be
like
synced
in
the
in
the
changing
in
waiting
for
their
pants.
Otherwise,
you
might
might
miss
it
miss
the
of.
B
C
And
when
some
of
someone
want
that
participant
see,
they
can
like
emits
the
shot
bot
message,
but
that
I
think
I
had
that
that
we
actually
would
need
some
something
into
the
stages
note
roading
running,
because
some
some
contracts
like
maybe
you
might
even
need
some
kind
of
automatic
respond,
monster
day
event
and
the
result
of
things
to
to
consider
for
the
future
of
this
shot.
Bus
I
think
that
that
we
should
open
these
discussions
again.
Your
shot
button
I,
don't
know
when
to
implement
that,
because
that's
not
a
variety
for
our
stations
right
now.
C
D
You
guys
were
speaking.
I
am
I
attempted
to
open
the
link
for
the
wallet
inside
of
status,
because
my
my
wallet
address
is
actually
the
on
the
multisig
wallet
is
my
status
whether
to
come
so
I
guess:
I'm
right
that
I
have
to
I,
can't
just
like
open
a
link
and
use
this
generous
wallet.
I
have
to
download
the
software
and
then
open
that
URL
right.
C
You
can
you
can
open
it
in
in
each
your
status
wallet.
You
can
use
the
what
you
do.
You
open
wallet
put
two
noses
like
that
link
and
you
need
the
address
of
the
multi-sig
wallet.
Can
you
face
there?
You
enter
the
name
of
the
wallet,
it
work,
fight,
fine
for
me,
but
as
Barry
said,
it
will
be,
may
be
difficult
to
the
day.
A
new
transaction
should
be
made
a
new
transaction,
but
the
confirm
is
released,
I
confirm
it.
B
C
Is
this
also
the
something
we
should
consider,
for
example,
that
look
that
the
address
field
is
just
a
text
field,
so
maybe,
if
the
status,
while
it's
news
that
that
was
a
address
field,
maybe
it
could
load,
they
did
the
addresses
from
the
contact
list.
Maybe
they
call
we
can
connect
the
contracts
that
there
is
worth
knows
that
that
should
it
should
have,
because
right
now
there
is
no
way
to
the
the
no
noses
wallet
requesting
the
contact
list
from
stages
to
appearing
that.
C
So
maybe
we
should
talk
with
extensions
about
that
and
then
that
you,
at
least
for
volley
transfers,
should
easier
and
also
ENS
called
so
we're
gonna
have
eNOS
names
us
so
having
supporting
eNOS
and
the
others.
Maybe
if
you
try
to
send
I
strange
where
an
address
is
supposed
to
be
then
state
as
well,
let
me
not
try
to
convert
automatically
to
resolve
it.
Sorry,
yeah
I
think
he
is
this.
Thank
you
for
the
presentation
bar.