►
From YouTube: Fil+ Legal Considerations
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
So
my
name
is
Alex.
Pierce
I've
been
working
on
this
project
for
over
two
years
now,
so
this
is
I.
Think
relative
OG
status
I
do
a
couple
I
I'm,
sort
of
myself
a
decentralized
entity.
So
I
do
a
couple
different
things:
I
run
a
a
company
called
murmuration
Labs,
which
started
with
the
question
of
what
about
what's
in
the
files
and
what
are
the
risks
associated
with
the
contents
of
the
files
that
we're
storing?
A
And
so
that's
the
thing
that
I've
been
working
on
for
over
a
decade
now
really
like
the
worst
stuff
on
the
internet,
which
makes
me
a
lot
of
fun
at
parties
and
I.
A
Also
am
a
board
advisor
to
filecoin
I'm,
a
lawyer
and
I'm,
a
legal
advisor
to
protocol
Labs
too,
and
so
I've
been
thinking
a
bunch
about
the
different
types
of
risks
that
are
entailed
with
what
we're
doing
and
I
have
a
couple
of
slides
which
may
or
may
not
show
up,
but
I
thought
I'd
offer
some
sort
of
broad
points
and
also
some
some
address.
A
Some
of
the
specific
questions
I've
been
getting
which,
which
Meg
is
kind
of
generously
raised
very
hopefully
and
then
spend
most
of
the
time
on
questions
really
so
I
guess
to
back
up
for
a
second
there's
like
the
quite
the
question
is
now
emerging
and
I'm
going
to
talk
about
this
from,
like
the
notary
perspective,
and
then
also
really
the
broader
storage
provider
perspective,
because
we're
all
dealing
with
complying
with
the
same
laws
and
dealing
with
the
same
risks.
A
So
I
guess
a
couple
things.
I
guess
thing:
one
is
that
compliance
when
you're
in
in
the
decentralized
mood
is
a
little
bit
different
and
it's
it's
one
of
the
challenges
that
we
have
because
sort
of
in
a
conventional
like
lawyering
or
compliance
situation.
As
as
those
of
you
who've
dealt
with
lawyers,
you
know,
like
part
of
the
strategy,
is
to
offload
risk.
A
That's
great,
let's
externalize
it
to
some
third
place,
but
when
you're
running
a
decentralized
network,
we're
all
sort
of
in
it
together
and
we
all
sort
of
care
about
each
other's
Fates
and
so
offloading
risk
to
a
counterparty
or
our
offloading
risk
to
other
parties
in
the
network
is
not
necessarily
what
you
want
to
do,
because
you
want
everybody
else
to
succeed
also,
but
at
the
same
time
you
can't
tell
other
people
what
to
do
right.
A
So
we're
in
this
we're
in
the
situation
where
we
have
interlocking
incentives,
but
we
also
want
to
put
the
risk
where
it
belongs,
but
we
also
are
not
trying
to
like.
Have
everybody
screw
attempt
to
have
a
race
to
the
bottom,
where
everybody
is
screwing
everyone
else
over,
and
then
everybody
winds
up
with
like
a
tragedy
of
a
common
situation
where
we
haven't
complied
or
we've
like
put
it
on
other
people
cool
so
does
that?
A
You
know
person
who
who's
like
you
know
cutting
class
as
frequently
as
is
permitted,
but
no,
no,
more,
no
less
cool.
So
one
of
the
hard
Parts
is
like
there's
a
lot
of
different
laws.
A
A
They
are
disparate,
obviously,
depending
on
what
country,
you're
sitting
in
I
looked
up
the
22
or
so
notaries
and
you're
all
in
different
countries,
of
course,
and
so
there
are
different
jurisdictions
which
want
different
things
from
us.
Meg
pointed
out
that
the
Australian
government
increasingly
wants
more
and
more
from
us.
Those
of
you
who
are
dealing
with
Europe
know
that
you
know
because
of
this
law
the
gdpr
that
any
anything
that
touches
the
precious
data
of
European
snowflakes
must
be,
must
be
protected
and
safeguarded
with
great
care.
A
So
there's
and-
and
that
is
to
say
even
if
you're,
located
in
the
US
or
you're
located
in
China.
If
you're
dealing
with
the
data
of
a
European,
citizen
or
resident
you're
still
implicating
that
gdpr
law,
and
so
often,
even
though
law
is
territorial
by
nature
and
it's
sort
of
still
stuck
in
the
literal-minded
20th
century
of
the
nation
state,
it
still
traverses
territorial
boundaries
and
new
responsibilities
can
be
multiple,
depending
on
what
you're
dealing
with
so
but
I
thought.
A
I
would
sketch
at
least
the
main
areas
that
are
of
concern
to
us,
and
so
the
first
one,
and
maybe
the
biggest
one,
is
probably
privacy
and
data,
and
this
is
a
thing
that
was
a
long
time
coming,
but
it's
not
going
to
go
away
when
you're
dealing
with
data.
The
questions
of
things
like
do.
People
have
the
right
to
delete
their
data.
Do
people
have
the
right
to
modify
their
data?
Are
you
transferring
it
in
a
manner
that's
acceptable?
Who
has
which
responsibilities?
A
In
what
role
you
know,
as
as
part
of
this
like
Skirmish
over
responsibility
and
there's
many
other
aspects
of
that
including
sort
of
data
localization
laws,
sometimes
which
say
like
if
you're
dealing
with
the
data
of
a
particular
set
of
citizens
from
a
particular
country.
You
should
keep
the
data
in
that
country
and
not
send
it
overseas
unless
you've
specifically
done
some
other
steps.
A
So
there's
a
lot
of
complexity
there
right
increasingly
since
Ukraine
and
Russia
people
have
been
noting
that
sanctions
law
and
is
a
thing,
and
so
normally
you
get
into
the
kyc
know
your
customer
anti-money
laundering
sort
of
questions
around
like
financial
institution
questions
and
kyc
really
sounds
maybe
onerous
and
scary,
but
it
really
is
just
like
who
are
you
I
would
say,
like
the
basic
point
is
like
do,
I
know
who
you
are
and
then-
and
it's
really
for
the
it's
multiple
it's
for
the
protection
of
multiple
parties,
because
you
want
to
know
who
people
are
so
that
you
can
protect
them
from
fraud.
A
But
then
you
also
want
to
make
sure
that
you're
not
transacting
with
somebody
who's
on
a
sanctions
list
or
transacting
with
somebody
in
a
country.
That's
on
a
sanctions
list,
so,
like
I,
said
because
of
Russian
Ukraine.
This
has
become
more
top
of
mind
for
people,
and
so
this
is
another
separate
set
of
questions
of
like
how
much
should
we
be
invested
in
the
identities
of
who
we're
dealing
with?
What
should
we
require
from
them?
A
Those
sorts
of
things
and
then
the
final
one
is
illegal
content,
and
this
is
the
thing
that
I
could
talk
all
day
about
on
just
this
bullet,
but
I'll
be
brief,
which
is
that,
whatever
you
probably
think
it
is,
it
is
more
complicated
than
that
thing,
although
it
might
seem
simple
and
there's
a
real
there's,
a
bunch
of
complicated
questions
here,
but
the
maybe
the
most
core
one
for
us
is,
you
can
really
generally
do
you
can't
do
nothing,
because
there
are
certain
types
of
things
that
are
so
illegal
and
so
taboo
that
it
would
be
disastrously
legal
to
have
it
on
hand,
stored
and
also
be
pretty
bad
for
the
network
to
become
known
as
a
place.
A
That
is
a
Haven
for
this,
and
so
the
go-to
example
that
everybody
always
has
for
this
is
what
is
called
in
the
industry
csam,
which
stands
for
child
sexual
abuse,
material
as
which
is
like
sort
of
illegal
in
taboo
everywhere.
Nobody
wants
it.
Nobody
wants
to
host
it.
If
you
do
host
it,
you
want
to
get
rid
of
it
and
there's
like
a
set
of
protocols
around
that,
and
then
another
category
is
what
the
kids
are:
calling
t-vec
terrorism
or
violent
extremist
content,
which
was
initially
sort
of
tended
to
be.
A
This
is
not
a
web
3
issue,
but
this
is
like
an
internet
issue
is
increasingly
politicized,
and
so,
if
you
think
about
the
way
that
the
Facebooks
and
the
twitters
of
the
world
for
10
or
15
years
now
have
been
called
upon
to
you
know,
take
this
thing
down.
It's
bad!
Take
this
thing
down!
It's
abuse!
Take
this
thing
down!
It's
harassment!
Take
this
thing
down!
It's
a
pirate
movie
Etc!
A
If
you're,
looking
the
last
two
to
five
years,
increasingly
the
godaddies
and
the
cloud
flares
and
the
registrars,
the
DNS
layer,
this
and
and
the
storage
layer
are
being
called
upon
to
make
interventions,
and
this
is-
and
this
can
be
politically,
you
know
it
could
be
oh
you're
hosting
an
a
directory
of
abortion
providers.
This
this
group
wants
you
to
take
that
down
or
it
could
be
on
the
other
side.
Like
you
know,
you're
hosting
you
know,
you're
hosting
your
directory
of
you
know
black
lives
matter
headquarters.
A
So
there's
all
sorts
of
things
where
political
pressure
is
increasingly
coming
towards
the
storage
layer
of
the
stack,
and
we
can
expect
that
from
governments
as
well
as
activist
groups
and
others,
and
you
really
have
to
have
an
answer
for
what
to
do
about
this
stuff.
So
those
are
sort
of
like
the
general
risks,
so
the
the
mood
of
it
like
I
was
saying
earlier.
Is
you
can't
in
lawyering
we're
old-fashioned
folks,
and
you
can't
be
What's
called
the
lawyer
for
a
situation
tempting
as
it
may
be?
A
But
this
decentralized
collaboration
mood
puts
us
in
a
strange
footing
there,
but
nevertheless
we
still
have
to
deal
with
that
conventional
aspect
of
legal
ethics
and
the
reason
this
is
tricky
is
because
the
foundation
and
I've
talked
with
Matt
and
Lauren
about
this,
who
are
like
the
foundation's
lawyers
and
with
me
as
murmuration
like
we
want
to
help.
But
we
don't
want
to
tell
you
what
to
do
and
day
and
day
right.
A
So
there's
there's
this
complicated
modality
of
like
we
are
here
to
help
we're
here
to
we're
here
to
provide
tools,
we're
here
to
provide
suggestions,
and
we
want
to
go
really
as
far
as
we
can
in
hoping,
because
we
want
the
whole
thing
to
succeed.
A
But
then
we
will
hit
a
point
where,
like
we
will
tap
like
any
lawyer,
will
tap
out
and
say
like
well
at
the
end
of
the
day,
not
your
lawyer,
sorry,
so
so,
and
so
that
can
be
like
a
sort
of
sad
and
obnoxious
moment
to
be
like
what
I
thought
we
were
in
this
together
and
one
of
my
former
colleagues
had
a
signature
file.
That
said:
if,
if
this
were
legal
advice,
it
would
include
a
bill.
A
So
so
we
don't
want
to
generally
be
helpful.
So
that's
I
think
that's
like
the
really
the
nub
of
like
what
we're
trying
to
accomplish
in
helping,
but
not
being
your
lawyers,
so
some
so,
but
nevertheless,
we've
been
talking
about
like
some
general
principles
and
some
things
we
want
to
do
to
help
so
I'll
rush
through
those
and
then
we
can
talk,
and
one
of
them
is
that
we
want
to
have
opt-in
compliance
right.
A
This
is
why
I'm
saying
like,
instead
of
mandating
things
whenever
possible,
sort
of
in
the
web,
3
spirit
and
spirit
of
this
project
want
to
say
like
okay,
here's,
here's
how
we
think
you
can
comply.
We
suggest
you
do
this,
we're
not
going
to
make
you,
but
maybe
we
will
make
it
transparent
when
you
do
so,
if
you
are
complying
with
X
laws,
maybe
we
have
a
badge
or
maybe
we
have
a
listing
in
the
directory
or
in
in
sort
of
like
the
deal
software
where
it's
like?
Okay,
these
are
the
gold
star
providers.
A
A
Now.
There's
a
point
past,
which
there's
a
danger
of
recentralization,
I.
Think
and
Danny
and
I
have
talked
about
this,
a
bunch
which
is
everybody.
Please
follow
the
leader.
Then
you
wind
up
with
the
same
result
as
a
centralized
system,
which
is
like
everybody,
winds
up
copying
everybody
else,
and
then
you
don't
have
diversity
and
maybe,
in
some
situations,
that's
okay,
so
like
with
csam,
nobody
wants
it,
nobody
should
have
it
great,
let's
not
have
it
and
then
in
other
areas.
A
So
I
said
we
can
provide
templates
and
software
Tools,
in
fact
murmuration
Labs.
If
you
go
to
our
GitHub,
we
have
what
we
were
calling
kits,
which
is
like
sample
content
policies
like
we're,
making
sort
of
like
what
I
think
of
as
like
your
starter,
wardrobe
like
this
is
like
your
first
content
policy,
your
first
privacy
policy.
This
is
like
you
know
what
it
what
it
looks
like
if
you
buy
it
off
the
rack
and
then
you
can
have
your
lawyer
customize
it.
A
If
you
want-
or
you
can
have
us
help,
you
customize
it
not
customize
it
so
much
that
it
breaks
the
network
but
customize
it
somewhat
to
your
needs,
depending
on
where
you're,
located
and
stuff
like
that,
we
may
get
to
a
point
where
we
go
from
these
manual
agreements
to
something
that's
more
click,
wrappy,
I,
think
that
would
be.
You
know
in
the
sense
that
we
will
create
a
bottleneck
somewhere
in
the
software.
A
You
know,
option
one
two,
three
sort
of
like
the
Chipotle
model,
and
then
you
can
pick
whichever
ones
of
those
you
want
insert
it
into
your
flow
and
then
sort
of
make
it
clear
to
your
deal
Partners
like
which,
which
float,
which
one
of
these
that
you're
using
so
that's,
that's,
sort
of
where
I
want
to
go
with
this
and
like
I
said
you
can
sort
of
modify
them,
but
then
beyond
a
certain
point,
then
it
might
create
problems.
A
Okay,
at
the
next
slide,
we're
about
10
minutes:
okay,
okay,
so
I,
so
I
tried
to
sketch
out
some
of
each
of
these
substantive
areas,
but
like
with
privacy,
for
example,
we've
been
doing
something
on
this,
where
we're
going
with
this
and
we'll
make
some
like
documents
available
for
starters,
is
like
under
this
sort
of
gdpr
model,
for
example,
we
want
the
clients
to
be
what's
called
like
the
the
controller
and
then
for
you
and
then
for
notaries
of
storage
providers
to
be
the
processor.
A
We
think
what
will
work
best
for
the
network
is
this
architecture,
and
then
then
we
can
have
like
a
dialogue
and
discussion
on
like
how
does
this
play
out
for
some
of
you
so
like
if
you're
located
in
some
countries,
it
might
be
harder
for
you
because
of
data
localization
laws.
Etc,
if
you
happen
to
have
a
client
say
from
Brazil,
then
you
have
a
problem
because
Brazil
has
its
own
set
of
laws,
and
now
you
need
to
figure
out
what
to
do
to
comply
with
Brazilian
privacy
laws
as
well
as
European
privacy
laws
Etc.
A
So
that's
sort
of
like
all
going
to
be
the
fun
part.
Take
me
to
the
next
slide
for
kyc,
and
so
this
is.
This
is
another
thing
that
we're
sort
of
experimenting
with,
which
is
we
can
have
the
foundation
provide
some
of
these
templates.
We
can
have
murmuration
provide
some
of
these
templates
and
then
in
some
cases
we
could
make
a
software
tool
if
it
is
useful,
so
I'm
interested
to
know
if
people
think
it
is
useful.
It's
like
with
kyc
one
of
the
challenges.
A
Is
you
generally
need
to
get
an
identity
document
right?
So
you
need
to
get
a
passport
or
a
driver's
license,
or
something-
and
so
this
is
like
the
this-
is
like
the
Crazy
Glue
problem
of
Privacy
Law,
which
is
like
whenever
you
try
to
comply
with
Privacy
Law,
you
wind
up
requesting
more
and
more
private
data,
and
then
you
have
like
great
now:
I
have
to
store
secure
copies
of
people's
passports.
Now
what
so,
then?
A
So
so
in
cases
like
that,
we
would
want
to
provide
something
that
is
secure
to
do
the
work
that
is
compliant.
So
this
is
like
Gail's
donning
from
his
prior
work.
This
is
a
rookie
rookie
mistake.
You
like
get
copies
of
everybody's
passport
and
then
you're
like
dope,
like
I'm,
storing
in
a
non-compliant
storage,
so
so
I'm
interested
to
know
how
much
help
people
might
want
on
this,
and
we
can
figure
out
whether
memoration
is
the
ideal
compliance
partner
there
or
whether
some
new
entity
that
does
like
compliance
as
a
service.
A
A
I
thought
I
would
plug
what
we
do
have,
though
so
this
is.
This
is
if
you
go
to
bitscreen.co.
This
is
the
first
thing
that
we
shipped,
which
is
a
deal
filter
so
to
the
extent
that
you
have
bad
cids
like
if
you
know
that
cids
are
bad.
If
you
got
a
letter
threading
letter,
you
can
plug
the
CID
into
this
filter
and
then
you
it
will
decline
further
deals,
both
storage
and
retrieval
deals
and
it'll.
A
Allow
you
to
look
at
other
storage
providers
like
you,
know
bad
lists
and
share
them
and
copy
them
back
and
forth,
so
you
can
sort
of
adopt
them
and
the
things
that
we're
working
on
is
one
of
them
over
the
very
short
version.
But
there's
like
a
database
out
there
of
known
csam
and
there's
complicated
security
problems
here,
because
they
don't
want
to
just
like
give
it
out.
But
we
are
trying
to
make
this
hash
database
interoperate
with
the
CID
namespace.
So
that's
for
notary
or
for
a
storage
provider.
A
B
A
So
it's
a
free,
it's
a
free
web
app.
So
if
you
just
go
there,
you
can
log
in
with
the
metamask
wallet
we
figured,
everybody
would
have
one
of
those
and
it's
and
then
you
can
just
use
it.
We
also
have
the
code
up
on
GitHub.
So
if
you
want
to
do
your
own
run,
your
own
instance
of
it
you're
also
welcome
to
do
that,
but
we
we're
running
it
for
free
I,
see.