►
From YouTube: Fil+ June 28, 2022 Notary Governance Call
Description
The community governance calls to discuss the Filecoin Plus program.
Topics Covered
- Notary Investigations
- FIl+ Day recordings are now online: https://www.youtube.com/playlist?list=PL_0VrY55uV18ug3rpeDnGtATwz-JtxycY
- Links to Application presentations: https://drive.google.com/drive/folders/1pPTb7lVTrmDlt8fBEaTWUNoRIUDahOEn?usp=sharing
- August Notary Call times: https://github.com/filecoin-project/notary-governance/issues/538
- Project Beacon: https://github.com/filecoin-project/notary-governance/issues/564
-LDN Application Update: https://github.com/filecoin-project/notary-governance/issues/565
- Enterprise Working Group Update (Meg @ Holon)
Github:
https://github.com/filecoin-project/notary-governance/issues/560
Slide Deck:
https://docs.google.com/presentation/d/1WCD6pLOblh4Yi3B2yE2_Wo28lvJNrS4yfuGF74tfFKI/edit?usp=sharing
If you would like to attend these meetings LIVE, the Fil+ Notary Governance calendar is available at: https://calendar.google.com/calendar/embed?src=c_k1gkfoom17g0j8c6bam6uf43j0%40group.calendar.google.com&ctz=America%2FLos_Angeles
Follow Filecoin!
Website: https://bit.ly/3ndAg44
Twitter: https://bit.ly/3ObND0x
Slack: https://bit.ly/3HKfFy7
Blog: https://bit.ly/3HFZFNv
Reddit: https://bit.ly/39N4Jmv
Telegram: https://bit.ly/3bkP8Ly
Subscribe to our newsletter! https://bit.ly/3Oy8J9j
#filecoin #ipfs #libp2p #web3 #nft
A
Today
is
the
June
28th
call
and
in
the
rough
agenda
that
we
cover
on
these
calls
kind
of
flows
where
we
take
time
to
welcome
anybody
who
may
be
joining
for
the
first
time
and
wants
to
say
hello.
We
cover
some
metrics
and
look
at
how
the
program
is
doing.
Overall.
As
far
as
data
growth,
we
solicit
any
input
that
you'd
like
to
see
discussed
on
these
calls
for
the
community
discussion,
as
well
as
any
issues
that
the
community
would
like
to
flag
back.
Then
we
save
time
to
discuss
that
as
we
go
through.
A
So
with
that
a
very
warm
friendly
hello,
my
name
is
Kevin.
This
is
your
team
of
gosh
governance
as
we
covered
it's
on
this
call
so
deep,
Galen,
oh
yeah,
for
myself
we'll
cover
any
questions
you
may
have
to
go
down
if
you're
joining
and
you're
dialing
in,
and
you
want
to
make
it
easier
for
us
to
communicate
with
you.
We
put
this
at
the
start
of
all
the
presentations,
sometimes
we'll
get
a
message
from
someone:
that's
like
hey,
iPhone
or
Dragon
Ball
Z
fan,
and
it
makes
a
little
bit
challenging.
A
You
may
be
completely
optional,
but
we're
going
to
post
the
link
here,
gosh,
Galen,
you're,
so
fast
as
always,
this
will
be
able
to
log
that
participation
for
SLA.
We
appreciate
you
doing
this
and
we'll
have
some
updates
about
kind
of
sharing
this
data
on
the
next
governance
call.
It's
been
kind
of
cool
to
collect
this
over
the
past
few
weeks,
so
we
can
see
which
areas
are
dialing
into
which
calls
which
notaries
are
coming
to
the
calls
and
kind
of
share
these
metrics
back.
The
way
we
do.
A
A
So
really
no
change
from
the
average
time
to
data
cap,
which
is
nice
because
now
we're
all
getting
ready
to
go,
ledgers
have
been
verified,
LDN
has
been
rolled
out
and
we're
just
troubleshooting.
The
final
blockers
and
we'll
address
on
this
call
so
it'll
be
neat
to
see
how
fast
we
can
start
to
respond
to
these
as
a
community
and
really
start
to
see
with
more
notaries
in
the
program
how
this
number
gets
driven
down.
So,
applicants
don't
have
such
a
long
wait.
A
This
comes
from
the
starboard
page
and
what
we're
looking
at
on
this
is
the
daily
active
deals.
So
those
of
you
that
are
on
the
call
you're,
no
stranger
to
this
slide,
essentially
The
Field's
in
yellow,
are
the
data
that
the
file
client
plus
program
is
being
in,
and
the
blue
is
the
regular
data
so
overwhelming
growth
that
we
see
from
the
field
plus
program.
So
thank
you
for
your
participation.
A
Thank
you
for
the
quality
data
and
thank
you
for
contributing
to
make
sure
that
this
network
grows
a
very
stable
trend
line,
as
we
see
here
over
the
past
30
days
and
the
same
process
holds
for
the
daily
deal
count
just
right
in
line
just
very
solid,
just
ticking
up
as
we
go
through.
So
we
appreciate
all
that
as
we
go
I'm
going
to
turn
it
over
to
Galen
and
a
recap
of
the
Sprint
cycles
that
we
have.
B
Awesome,
yes,
thank
you
so
showing
this
again
keeping
us
accountable,
we're
trying
out
some
of
these
governance.
Sprints
LDN
V3
is
rolling.
We
have
some
additional
tools
and
trainings
that
we
still
want
to
come
up
with,
but
right
now
we're
sort
of
kind
of,
mostly
in
the
like
testing
and
making
sure
that
it's
functioning
correctly,
the
subsequent
allocation
Bots
appear
to
be
working
as
intended.
So
far.
B
There
are
some
other
unrelated
known
issues
that
we
may
touch
on
that
people
have
had
using
the
app,
but
those
are
not
part
of
the
V3
implementation.
So
that's
where
we
are
with
that
getting
closer
to
that
200
Pips
of
sealed
data
cap,
we're
crossed
we've
crossed
over
the
hundred
and
then
we're
coming
up
with
a
new
way
to
count
the
active
ldns
and
have
a
reliable
source
of
Truth.
For
that
with
the
switch
to
V3.
There's
some
like
different
ways
that
we
need
to
capture
that
metric.
B
B
Thanks
some
more
documentations
the
governance
working
group
proposals
that
is
posted
we've
had
some
good
conversation
back
and
forth
on
that
for
the
e-fill
we
have
some
new
additional
proof
of
concept.
Proposals
from
some
different
community
members,
I
think
would
also
fall
into
this
governance
category,
and
then
we
are
continuing
to
work
on
our
trust
and
safety
team.
That's
sort
of
the
support
for
our
risk
analysis
groups.
B
So
not
a
any
specific
things
to
show
on
this
this
week,
but
we
are
making
progress
on
all
of
them
and
as
we
come
up
with
updates,
we'll
have
them
and
then
like
be
planned
in
that
July
26th
governance
call,
we
should
have
sort
of
missed
it
or
or
finalized
update
on
this
Sprint.
So
thanks
everybody
for
trying
out
this
new
structure.
B
Yep,
so
one
of
the
things
we
care
about
is
days
without
data
cap.
Once
a
client
has
been
approved
as
long
as
they're
continuing
to
operate
in
good
faith,
they
should
not
run
out
of
data
cap,
and
so
that
is
where
that
days
without
data
cap
comes
from,
and
that
has
to
do
with
really.
How
well
is
the
subsequent
allocation
bot
functioning
is
the
timing
on
that
correct?
Are
the
allocation
sort
of
tranches
working
the
way
that
we
intended?
B
If
we
start
to
see
more
and
more
clients
running
out
of
data
cap
and-
and
you
know
needing
like
a
bridge
allocation
or
something
like
that,
then
it
would
be
indicative
that
we
might
have
some
kind
of
issue
breaking
down
in
the
system.
So
we
believe
that
if
a
client
is
has
been
approved
and
is
operating
in
good
faith,
they
should
not
run
out
of
data
cap
unless
they
intend
to,
for
example,
they've
you
know
used
all
that
they
planned
for
whatever
project
they
were
going
to
do
so
good
question.
A
A
So
he
might
speak
on
her
behalf
on
this
call
and
then
she'll
add
additional
details
with
her
project
in
2000
in
a
second,
so
very
full
agenda.
If
there
was
other
items
that
you
wish
to
discuss
that
weren't
on
this
list.
As
a
reminder,
we
Post
in
the
notary
governance
repo
every
week,
so
you
can
say:
hey
I'd
like
to
add
an
item
to
that
agenda
and
we'll
be
sure
to
bake
that
into
this.
So
let's
get
started
yeah.
B
I
can
take
this
one,
so
there
have
been
some
questions
brought
up
about
some
different
notaries
for
round
three.
We've
been
capturing
those
questions
to
the
best
of
our
ability,
putting
those
questions
in
the
notary
applications
themselves.
For
public
transparency.
We
are
continuing
some
ongoing
diligence.
We
don't
yet
have
finalized
results
on
all
of
those
different
questions
that
were
brought
up,
but
once
we
resolve
them
we'll
be
updating
publicly
in
GitHub,
we'll
also
kind
of
announce
those
on
governance
calls
and
in
slack.
B
A
We'll
cover
this
one
big,
thank
you
to
those
of
you
that
either
came
in
person
or
watched.
The
Phil
plus
day
is
a
quick
subtle
plug
there
on
YouTube,
we
shared
the
initial
link
right
now,
just
to
kind
of
keep
you
updated.
We
are
working
with
a
translation
service
and,
with
the
translation
service
is
going
to,
do,
is
add
Mandarin
subtitles
to
the
very
bottom.
A
So
it
should
be
a
nice
time
capsule
of
where
we
were
so
again.
The
link
is
Live
on
YouTube,
we'll
post
this
again
and
I
think
once
the
translations
are
added
all
blasted,
even
more
heavily
in
the
channels.
For
that
all
right.
This
next
one
we
talked
about
on
the
last
call
and
we're
kind
of
soliciting
feedback.
So,
as
you
know,
this
governance
call
runs
twice
a
day
when
we
started
this
field
plus
program
and
the
community
participation.
A
This
used
to
be
a
single
call
during
the
day,
but
there
was
no
way
that
we
could
get
the
time
zone
right,
but
there
wasn't
somebody
that
was
either
dialing
at
very
late
at
night
or
in
the
morning.
It
wasn't
convenient
with
the
time
change.
It's
made
it
a
little
bit
more
complicated,
so
there
was
an
issue
that
was
proposed.
It's
been
open
for
about
three
weeks.
A
This
is
the
second
time
we've
talked
to
it
and
the
question
was:
can
we
adjust
the
second
time
of
the
call
so
that
second
time
call
currently
takes
place
at
4
pm,
Pacific,
2300,
UTC
and
7
A.M
Beijing?
If
you
look
at
the
participants
that
are
dialing
into
this
second
call
you'll
see
that
the
majority
are
coming
from
the
greater
China
region
which
is
hitting
at
that
6
a.m.
A
So
we've
asked
for
feedback,
and
the
last
calls
I
think
that
this
is
gonna,
be
the
final
round
and
the
proposal
that
we're
listening
feedback
on
is
to
Pilot
test
this
in
August,
so
not
to
drastically
change
the
schedule
without
too
much
notice,
we'll
give
it
two
cycles
and
then
in
August
shift
the
time
zones
back
two
hours.
This
would
only
apply
to
the
second
call
and
those
of
you
that
are
dialing
in
for
Beijing.
A
It
would
be
at
zero
900
that
way,
you're
not
having
to
dial
in
super
early
in
the
morning
and
ideally,
those
of
us
that
are
calling
it
from
North
America.
It's
still
within
that
line.
So
if
you
have
any
thoughts
or
feedback,
I
see
some
like
emojis
in
chat,
It's
Kind
of
Perfect.
What
also
really
helps
is,
if
you
come
to
that
issue
538-
and
you
say
yes,
I,
like
that
proposal
or
no
Kevin,
that's
the
silliest
thing.
I've
ever
heard
and
I've
heard
a
lot
of
things.
It
makes
it
really
nice.
A
But
again,
if
you
have
thoughts
on
this,
please
please
write
back
in
that
GitHub
or
try
to
treat
GitHub
is
that
source
of
Truth
and
that
record,
so
we
can
get
an
accurate
count
of
the
times
working
so
again,
galen's
posted
a
link,
really
appreciate
your
feedback
and
what
we're
looking
to
do
is,
in
the
month
of
August
pilot
test,
shifting
that
second
governance
call
two
hours
to
make
it
easier
for
those
of
you
in
the
greater
China
region
to
attend
that
other
call.
So
it's
not
so
long.
B
B
Let
me
get
the
link
to
that
one
as
well,
so
people
can
read
it
or
actually
maybe
deep
can
pull
up
that
link.
Why
yeah
speak
to
it?
Okay,
so
this
is
another
LDN
application
coming
in
from
a
group.
I
would
encourage
everyone
to
go
check
it
out.
It
has
some
interesting
context
and
info.
It
has
some
notary
support
already
it's
very
similarly
following
what
the
seal
project
is
trying
to
do
with
Antarctic
effectively
11
pibs
of
unique
they've
identified
some
different
storage
providers.
C
I
added
some
thoughts
yesterday,
specifically
that
all
the
notaries
that
are
initially
shown
support
were
also
from
the
same
region
or
not
from
that
many
regions,
and
so
I
suggested
Eric,
as
well
as
the
applying
client
and
some
of
the
other
notaries
that
are
involved.
I
think
there's
already
four
of
them
on
the
thread
too.
So,
there's
Eric
for
my
base,
but
there's
also
a
plus
gate
from
bushy
and
Firefly
that
are
engaged
and
so
I
just
asked
that
it's
probably
good
to
have
noticed
from
multiple
regions.
C
So
there
are
actually
four
regions
there,
but
I
think
at
least
getting
notary
approval
outside
of
region
helps
sort
of
validate.
That,
okay,
like
there,
are
people
that
aren't
in
a
region
that
aren't
going
to
directly
benefit
from
this
or
feel
like
there's
any
disproportionate
relationship
and
are
still
able
to
vet
this
to
some
extent,
and
so
generally,
that
seems
to
be
received
well
and
I.
Think
they're
interested
in
being
able
to
chase
that
down
and
so
yeah
I.
C
Think
overall,
this
is,
you
know,
pushing
the
boundary
a
little
bit
once
again,
where
it's
okay.
This
is
encrypted
data
similar
to
Antarctic.
In
this
case,
though,
it's
not
scientific
data,
it's
something
that's
actually
has
to
be
compliant
with
some
government's
policy,
and
that
comes
with
another
tier
of
complications.
C
B
D
I
bet
yeah
thanks
for
the
opportunity,
there's
been
a
lot
of
questions
regarding
Big
Data
exchange,
so
you
know
thank
you
for
giving
me
the
chance
to
clarify
some
of
the
to
address
some
of
the
issues.
So
big
data
exchange
is
a
Marketplace
to
match
storage
providers
with
clients
of
field
plus
deals.
A
lot
of
people
ask
us:
why
are
we
applying
for
ldm
when
we
are
up?
You
know
a
platform
to
match
both
parties?
D
The
number
one
reason
is
that
we
want
to
understand
the
process,
so
we
can
help
onboard
one
crypto
native
clients,
other
data
communities
into
our
ecosystem,
and
the
second
reason
is
that
we,
you
know
we
have
we
launched
three
weeks
ago,
we
have
seen
demand
from
both
sides.
We
have
clients
listening
auction.
We
have
SP
bidding
on
all
these
auctions.
D
We
will
need
to
either
help
them
with
the
field
plus
onboarding
process,
or
we
need
to
do
it
ourselves
first
in
the
short
term
and
use
that
data.
So
that's
something
we
we
want
to
do
that's
what
we're
apply
and
yeah
any
and
I
want
to
emphasize
again.
Any
proceeds
will
be.
Any
proceeds
will
be
donated
to
courses
to
fund
power
coins
mission.
C
C
I
think
the
only
question
I
have
for
you
is
as
part
of
the
educational
and
and
sort
of
experience,
learning
side
of
things.
Is
this
like
something
that
you're
gonna
eventually
turn
into
like
an
offering
for
clients
where
it's
like?
Okay,
like
we'll,
handle
you
to
the
process,
to
make
it
substantively
easier
for
you
to
go,
get
data
cap
and
if
yes,
is
any
of
this
going
to
be
publicly
documented
that
the
community
can
also
benefit
from
as
part
of
you
doing
this
effort
anyway,.
D
Yes,
I
think
what
I
Envision
is
that
in
the
long
term
we
want
to
have
the
offering
and
again
not
to
profit
from
it.
We
want
to
help
to
onboard.
You
know
we
want
to
bring
new
data
communities,
so
I
think
that's
one
way.
We
can
try
doing
that.
You
know
bridging
a
gap
between
the
know-how.
So
that's
something
like
you
say:
we
want
to
offer
and
in
terms
of
documentation.
D
Yes,
if
there
is
a
need
to
we'll,
definitely
do
it
to
benefit
the
whole
Community
again,
our
goal
is
not
to
be
the
gatekeeper
you
know
or
to
I'll
get
go
is
really
just
to
facilitate
the
process.
If
there's
anything,
we
can
do
to
help.
We
want
to
do
that,
because
what
we
want
to
do
is
really
to
create
a
robust
Marketplace.
C
D
C
The
so
this
is
I'm
still
dealing
with
a
bug
on
this
and
I
can't
figure
out.
What's
going
on,
but
I'll
walk
you
through
the
thinking.
So
this
is
a
proposal
565.
The
goal
of
this
is
extremely
simple.
We
currently
have
the
LDN
application
form
as
a
raw
markdown.
Let
me
send
a
link
to
this,
and
what
that
does
is
it
creates
a
significant
opportunity
for
ux
based
mistakes
where
users
who
are
not
correctly
interpreting
what
is
expected
of
them
end
up
like
failing
on
basic,
like
validation.
C
So,
to
give
you
a
concrete
example,
if
you
accidentally
hit
like
a
back
deck
or
you
remove
one
of
them,
while
filling
out
the
application,
because
you're
doing
a
bunch
of
double
clicking
and
typing
the
formatting
of
the
entire
form
breaks
and
the
validation
breaks
or
another.
If
you
look
at
input
fields
and
types
of
data
that
notaries
are
specifically
looking
to
get
so,
for
example,
is
this
application
for
public
or
for
private
data?
C
Those
are
things
that
could
have
been
drop,
downs
or
check
boxes
or
things
that,
like
deterministically,
resulted
in
the
in
the
applying
client,
whether
that's
the
data
owner
themselves
or
somebody
acting
on
behalf
of
the
data
owner
to
inform
the
community
and
inform
the
notaries
correctly
and
so
GitHub
has
this
feature
in
preview
today,
where
they
support
yaml
based
issue
templates,
and
so
we've
experimented
with
this.
We
actually
look
at
the
Lotus
repo,
the
bug
report.
There
is
a
yaml
style
template
and
that's
really
cool.
C
It
has
a
bunch
of
checkboxes
and
you
fill
out
information
and
so
I
was
like
well.
Why
aren't
we
using
this
on
our
end
and
so
I'm
in
the
process
of
sort
of
building
a
a
copy
of
our
existing
LDN
application,
template
plus
added
like
one
or
two
clarification
questions
and
converting
that
into
a
yaml?
So
it
looks
more
like
a
form
when
you
go
to
fill
it
out.
I
think
that
this
could
help
with
improved
user
experience
like
it.
C
You
know
I,
don't
think
it
looks
prettier
necessarily,
but
I
do
think
you're
more
likely
to
put
in
the
right
things
and
see
the
right
questions.
It
gives
us
better
validation,
so
we
can
have
inbuilt
validation,
GitHub
that
says
hey.
If
this
question
has
not
been
filled
out,
you
cannot
proceed
with
the
application,
which
is
really
helpful
because
it
reduces
one
Loop
for
the
client
to
wait
for
the
bot
to
spot
something
and
then
try
and
interpret
what
the
Bots
trying
to
tell
them,
and
then
the
third
and
I
think
the
most
interesting.
C
But
unexplored
thing
is
we're
already
doing
a
bunch
of
like
GitHub,
scraping
for
information
to
popular
dashboards,
and
things
like
that.
This
would
make
that
more
deterministic,
but
then
also
give
us
opportunity
to
collect
different
types
of
data,
because
when
you
create
data
structures
or
you
create
models
that
result
in
more
specific
information,
but
you
can
use
that
in
more
interesting
ways
as
well.
I've
been
a
little
bit
behind
with
a
bunch
of
stuff
in
the
last
week
or
so
so
I'm
catching
up
to
a
ton
of
things.
C
So
this
is
my
like
really
fast,
like
quick
and
dirty
version
of
it.
This
is
absolutely
not
ready
to
be
merged
in,
but
I
wanted
to
flag
it
and
start
to
get
your
early
sort
of
thinking
on
whether
or
not
one
this
makes
sense
do
if
you
think
anything
else
could
be
done
to
improve
it
and
then
three,
if
you
have
any
questions
on
what
I
have
so
far,
it's
still
a
work
in
progress.
C
Needs
I
think
there's
actually
only
one
reason
and
I
completely
agree
that
we're
basically
shoe
warning
effectively
a
solution
that
isn't
natural.
It's
not
like
a
natural
effect
for
the
environment.
They're
in
the
main
reason
is
I
think
that
it
provides
a
public,
accessible,
auditable
workspace,
where
we
can
both
continue
to
share
everything,
that's
happening
with
anybody
in
the
community.
C
That
wants
to
see
it
to
the
best
of
our
ability,
but
then
also
facilitates
an
environment
where
it
changes
to
the
governance
process
or
even
the
application
process
are
easy
for
anybody
to
do
right.
So
very
concretely,
if
somebody
wants
to
go
and
update
the
documentation
or
if
somebody
wants
to
go
and
change
the
application
template
it's
it.
You
just
open
up
a
PR.
It's
not
like
an
extended
process
where
we
then
need
to
do
it
in
two
places.
C
I
agree
that
it's
not
the
best
but
I,
think
it's
been
good
enough
or
there's
been
enough
so
far
to
continue
using
it
for
the
time
being,
I'm
totally
down
to
explore
other
options.
I,
don't
know
if
anybody
in
this
community
feels
super
strong
about
staying
with,
GitHub
actually
cared
again.
If
you
have
thoughts,
would
love
to
hear
them,
but
for
the
time
being,
Alex
like
this
is
a
very
cheap
change.
C
As
I
said
I've,
you
know,
I
even
I've
been
behind
a
bunch
of
stuff
I.
Think
I
did
this
in
like
10
minutes
as
a
proposal
just
to
like
put
it
out
and
see
what
it
would
look
like
and
I
think
implementing.
It
would
also
be
pretty
cheap,
and
so
it
could
be
like
in
lieu
or
in
the
interim
until
we
figure
out
something
better
yeah,
open-minded.
E
Yeah,
I
I,
don't
think
it's
necessarily
easier
because
if
you
think
about
it,
every
tool
that
scans
for
issues
right
now
will
have
to
change
the
implementation,
and
why
not
so
I
think
we,
if,
if
we
got
a
if
we
will
change
how
these
things
are,
are
sent
or
or
dealed
with.
We
I
think
we
gotta
choose
the
right
tool
for
for
this
kind
of
job
and
because
it's
not
so
easy
to
change
every
implementation.
Every
dashboard,
every
data
pipeline
to
to
use
this
new
template.
E
So
if
we
keep
making
changes,
people
were
gonna,
have
a
hard
time
like
building
up
on
our
stuff.
So
I
think
it's
better
if
we
just
pause,
search
for
the
best
do
or
best
whatever,
and
regarding
the
having
to
transparency
and
having
and
now
at
the
trail
or
or
anything
like
that,
we
can
use
any
platform
and
plug
it
in
to
dump
data
onto
the
or
GitHub
repos
and
or
not
so,
I
think
that
that
will
be
a
lot
easier
to
use
the
right
tool
and
then
just
move
the
data.
C
Yeah
so
I
think
the
only
thing
that
I
would
add
to
that
Alex
is
that
the
scraping
stuff
that
we've
been
building
for
the
different
dashboards,
a
lot
of
that
is
just
regular
expression
and
like
text
search
base,
so
I'm
actually
not
changing
any
of
the
text,
so
it
would
just
be
like
looking
at
the
text
and
then
the
next
field.
I
am
curious.
C
How
if
it
has
like
I
think
so
far
the
only
thing
I've
had
to
do
is
I
have
to
remove
like
colons
at
the
end
of
questions,
which
I
think
should
be
a
relatively
minor.
Fixed
I
had
some
brief
conversations,
not
with
everybody.
Just
with
like
one
of
the
teams,
that's
working
on
the
dashboards
and
it
seemed
like
relatively
cheap,
but
I
think
it's
a
fair
flag.
I
can
definitely
do
some
more
investigation.
I
know
you've
been
doing
some
thinking
on
this,
and
so
I
owe
you
some
responses
on
other
stuff.
C
Maybe
we
can
chat
about
this
as
well
and
see
if
we
can
come
back
to
the
community
with
something,
but
it
seemed
to
me
like
not
that
expensive,
maybe
I'm
underestimating
it
and
if
I
am
I'm
open-minded
to
like
not
push
this
one
through
and
instead
focus
on
other
stuff.
I
know
Galen,
you've
added
something
to
the
chat.
Do
you
want
to
share
that.
B
E
Yeah
I
think
one
one
issue
is
that
we
are
by
changing
the
forms
in
in
GitHub.
We
are
making
it
easier
for
us
to
implement
it
but
harder
for
for
third
parties
to
to
like
implement
or
change
things,
because
we
are,
we
are
using
it.
We
are
changing
because
it's
easier
for
us
this
way,
it's
easier
to
change,
it's
easier
to
make
it
like
start
using
right
away,
but
it
makes
it
really
hard
to
to
the
other
other
stakeholders
who
may
be
using
the
the
current
implementation.
E
C
I
think
if
you
can
call
out
like
specific
things
that
you
think
will
be
expensive
to
adjust,
that'd
be
very
helpful.
I,
don't
know
if
I
have
a
super,
confident
stance
to
disagree
or
agree
with
you.
This
is
more
like
I
wanted
to
see
what
the
implications
this
might
be
and
how
it
could
help
with
the
client
on
learning
experience.
C
So,
for
example,
if
you
go
to
plus.fill.org
LDN
dash
application,
there's
like
this
new
UI
that
you
can
fill
out
and
instead
of
sort
of
using
the
GitHub
issue
generation
thing
you
can
go
through
that
we'll
launch
that
more
formally
in
the
in
the
coming
weeks,
but
other
people
have
been
experimenting
with
that
as
well
and
that
that's
really
cool,
because
you
can
basically
just
build
a
layer
on
top.
Instead
of
having
to
modify
like
the
underlying
GitHub
as
a
database
of
applications
problem.
C
However,
yeah
I
just
need
to
figure
out
like
what
the
implications
of
changing
the
yaml
based
templates
would
be
for
that
party
as
well,
so
I
think
there's
two
sets
of
stakeholders
here,
Alex,
it's
the
people
that
are
building
on
top
of
the
application
and
there's
the
people
are
scraping.
The
application
I
have
a
low
confidence
guess
that,
at
least
for
the
latter,
it's
extremely
cheap.
C
But
you
should
correct
that,
because
you're
one
of
those
people
and
so
I
would
love
to
hear
from
you
overall
I
will
say
that
if
you're
asking
that
you
know,
if
you
think
about
it,
overarching
priorities
and
stuff,
at
least
in
my
opinion,
I
would
say:
ease
of
use
for
clients
and
people
filling
out.
This
form
is
way
higher
a
priority
than
ease
of
use
for,
like
the
tooling
that
we
need
to
build
around
that
support.
C
We
have
super
200
people
in
this
ecosystem
that
have
been
doing
a
lot
of
awesome
work
on
the
tracking
and
the
maintenance
and
the
building
of
layers
on
top
and
I'm,
very
confident
in
your
and
other
people's
ability
to
continue
delivering.
Our
job
here
is
to
build
the
lowest
friction
path
to
a
productive,
Falcon
Network.
That
means
making
it
incredibly
easy
for
two
main
stakeholders:
number
one
clients
number
two
notaries.
C
C
C
F
C
Absolutely
I
think
100
of
this
is
something
we
want
to
do,
and
that
is
that's
part
of
the
plan.
I
know
Alex
has
been
thinking
about
it,
a
bunch
as
well.
Other
people
have
as
well
so
definitely
agree.
Why
not
just
for
a
little
bit
of
context
for
you
before
I
know,
Alex
has
a
hand
before
we
chat
about
that
CMS
type
thing
a
little
further.
What
we
do
today
is
we
basically
do
a
bunch
of
scraping
really
right.
C
So
we
dig
we
do
a
combination
of
metadata
and
data
available
on
GitHub,
directly
about
issue
creation
times
commenting
times,
who's,
commenting,
what's
being
posted,
what's
being
shared
and
dump
that
into
a
DB,
and
then
we
correlate
that
because
all
of
the
bot
issues,
for
example,
right
they're,
linked
to
like
an
LDN
multi-stick
address,
so
they're
linked
to
a
client
address,
or
they
Link
at
the
very
least,
to
message.
Cids.
C
So
I
should
say
at
the
very
least
the
client
address
and
mostly
always
message
the
IDS.
And
then
we
correlate
that
with
message
scraping
that
we're
doing
on
chain
and
so
we're
able
to
correlate
the
two
things
and
generate
some
really
awesome,
insights
and
Views
into
what
are
the
notaries
that
are
signing
which
applications
at
what
time.
What
is
the
individual
time
to
data
cap
for
each
of
those
notaries?
Where
like?
What
are
the
high
risk
issues
or
what
are
issues
that
are
receiving
disproportionate
amount
of
traction
and
things
like
that?
C
E
Just
a
quick
tip,
though,
if
you
want
to
know
more
about
some
work
I'm
doing
on
on
that
end,
to
implement
something
like
CRM
and
CMS,
like
together,
I'm
building
a
a
system
to
to
handle
those
things
using
atlassian,
Confluence,
jira,
jira,
service
management
and
that's
all
interconnected.
So
we
have
a
better
way
of
of
knowing
where
to
get
things
and
and
have
all
that
data
like
centralized
or
everyone's
use.
E
F
F
C
D
C
Okay,
cool
separately.
It
might
be
good
as
part
of
that
conversation,
to
also
talk
about
like
what
are
the
tools
that
we're
comfortable
like
taking
a
bet
on
as
like
an
open
working,
Community
versus
ones
that
we
may
not
be
as
down
for,
depending
on
like
either
funding
or
future
path
or
future
Direction,
and
then
the
relative
trade-offs
to
just
something
as
simple
as
GitHub
and
so
yeah.
All
good
stuff,
though,
thank
you.
A
Great
discussion,
all
right,
we
have
one
more
I,
think
I'll
step
in
and
speak
I,
don't
see
Meg
on
the
line.
So
for
those
of
you
that
don't
know,
Meg
is
spearheading
a
project
called
the
Enterprise
proposal,
she's
giving
us
updates
on
the
last
call.
This
is
just
another
one
that
comes
along
and
the
high
level
for
the
Enterprise
proposal
is
right.
Now
they
are
seeking
feedback
on
this
project.
So
one
of
the
reasons
we
shared
this
deck
is
that
you
could
read
this
along
and
get
all
the
details
again.
A
Meg
will
speak
much
more
eloquently
to
this,
but
at
a
very
high
level,
what
this
proposal
is
looking
to
do
is
two
parts
right
now:
the
feedback
stage.
It's
one
get
the
feedback
from
you
on,
as
far
as
like
a
pulse
check
and
what
she's
looking
for
is
notaries
that
want
to
participate
can
give
you
their
input
on
this
plan.
The
second
is,
as
we've
talked
about
on
this
call.
A
So
specifically,
what
she's
looking
for
is
eight
to
ten
notaries
that
would
want
to
dedicate
their
time
to
participating
in
this
I
think
what
she's
looking
for
is
very
active
participants
in
this
that
want
to
look
at
this
as
like
a
side
project,
and
then
how
do
you
offer
that
Enterprise
MVP
proposal
to
kind
of
take
this
cradle
degree?
So
again,
we've
talked
about
this
in
cloudcoin
plus
day.
We've
had
this
come
up
on
the
last
sink,
but
I
think
what
she's
looking
for
right
now
is
a
dedicated
group
of
notaries.
A
Is
this
a
sustainable
model
that
we're
putting
together
for
others
in
the
community?
So
if
you
like,
testing
new
things,
if
you
like
giving
feedback,
this
would
be
the
perfect
group
for
you
again
reach
out
to
make
it
for
one
via
slack
or
the
issue
proposals.
One
of
the
things
that
you
wanted
to
flag
was
the
risks
and
mitigation.
So
one
of
the
big
things
is
any
system
that
we
talked
about
rolling
out
has
to
be
applicable
across
the
board
as
deep
showed
with
the
LDN
application
change.
A
Just
that
one
subtle
change
on
the
application
and
we
had
about
a
15-minute
conversation
looking
at
it.
So
Meg
is
very
mindful
that
any
changes
that
we
make
have
to
be
good
for
the
goose,
as
well
as
the
gander.
So
taking
a
look
at
that
risk,
it
needs
to
be
like
open,
transparent
and
again.
That's
why
she's
looking
for
eight
to
ten
notaries.
D
A
B
Yes,
thanks:
I
was
going
to
touch
on
the
Enterprise
proposal,
because
there
have
been
a
couple
comments
back
and
forth
on
it
and
I'll
also
jump
in
and
comment
on,
the
the
issue
itself,
but
the
comments
have
been
around
whether
or
not
a
FIP
is
necessary
for
this
I
think
that
we
could
go
a
couple
of
different
ways.
Strictly
speaking,
this
can
fit
within
fit
three
and
not
require
a
new
entire
FIP.
B
In
order
for
us
to
run
a
proof
of
concept
like
this,
we
could
draft
an
informational
FIP,
but
this
is
not
as
it
is
being
presented.
This
would
not
require
any
technical
changes
to
the
filecoin
project
as
far
as
I
know,
based
on
what
is
being
pitched
here,
which
has
to
do
with
still
the
type
of
subsidy
that
happens
on
the
network,
so
just
clarifying
that
an
informational
fit
could
be
drafted
but
is
not
required
based
on
how
the
wording
of
fit
three
and
the
wording
of
this
proposal
so
far,
deep.
C
Can
I
come
out
with
an
opinion
here
and
say
that
we
should
not
be
doing
a
fit
for
this,
like
it
doesn't
actually
make
sense
to
me.
Maybe
I'm
missing
something
about
the
value
of
an
informational
FIP
here,
but
we've
made
so
many
changes
to
this
program
since
fit
three
like,
for
example,
even
the
LDN
thing,
let
alone
like
V1
V2
V3
have
not
been
fit
because
it's
just
not
necessary.
It
is
not
a
good
use
of
of
time
and
effort.
C
That
team
is
also
doing
a
bunch
of
stuff
and
there's
a
lot
of
like
things
happening
that
require
changes.
The
protocol
level,
these
things,
don't
we're
running,
scoped
experiments,
we're
building
on
past
experiments
and
it
doesn't
I,
don't
know
please
correct
me
I
think
maybe
I
might
be
missing
something
on
on
like
the
value
prop
of
the
informational
fit
I.
E
Be
easier
for
newcomers
to
understand
how
everything
really
is,
because
if
I,
don't
I,
don't
know
if,
if
necessary,
a
FIP
or
or
something
else,
but
something
that
we
can
go,
look
how
the
system
operates
right
now
and
how
it
it
works
right
now,
instead
of
just
having
to
chase
down
the
information,
I
think
that's
that's
one
of
the
the
main
goals
of
having
a
fee
for
or
something
is
to
have
a
like
a
centralized
way
of
knowing
what
is
happening,
how
it's
happening
and
and
how
everything
works
together.
So,
okay,
that
makes
sense.
E
C
C
E
C
C
G
B
B
I,
don't
know,
I,
think
the
big
I
think
the
big
difference
with
this
is
that
this
proposal
is
specifically
for
storage
providers
to
lead
BD
and
bring
clients.
So
the
storage
provider
is
already
very
aware
of
like
where
this
information
is
in
the
state
and
they
are
going
to
direct
their
client
to
the
information
they
want
them
to
see.
I,
don't
think
that
it
is
reasonable
to
expect
a
client
who
is
trying
to,
like
you
know,
make
a
decision
on
filecoin
to
go
read
through
various
fips.
B
The
storage
provider
will
be
like
go
to
this
doc
watch.
This
YouTube
video,
like
the
storage
providers,
are
going
to
curate
that
experience.
The
client,
who
is
an
Enterprise
like
may,
do
their
own
investigation,
but
landing
on
a
GitHub
issue
in
the
notary
governance.
Repo
I
think
is
just
as
clear
and
likely
as
landing
on
a
GitHub
issue
in
the
fips
repo
for
a
client
who
is
just
coming
to
the
project
and
being
brought
to
the
project
by
an
already
versed
storage
provider.
B
So
that's
my
thing
and
I
think
I
think
that
the
main
reason
to
not
write
a
fit
is
as
deep
says,
the
amount
of
the
amount
that
that
is
going
to
slow
the
project.
This,
like
proof
of
concept
down
and
the
amount
of
traction
that
that
team
is
already
trying
to
get
for
different
network
upgrades
that
having
another
fit
pulls
focus
on
things
that
are
already
in
Flight.
B
And
thirdly,
the
question
of
like.
Does
that
set
a
precedent
that
then
any
new
proof
of
concept
to
the
Falcon
project
like
would
need
to
have
an
informational
fit
so
I
also
have
yet
to
see
the
best
explanation
for
like
when
an
informational
fit
is
necessary,
and
so
since
that
it
makes
a
lot
of
sense
to
me
that,
if
is
required
when
there
is
a
technical
protocol,
change
and
I
think
that
primarily
using
that
platform
for
those
types
of
fips
makes
a
lot
more
sense
to
me.
B
E
That
has
two
points
right,
because
in
one
way
you're
we
are
making
change
move
faster,
but
in
in
the
other
way
we
are.
We
cannot
change
this.
We
are
making
it
harder
to
understand
the
system
and
understand
where
everything
is
I
I
understand
that
it
makes
things
move
faster,
but
it
makes
it
harder
to
understand
the
system
as
well.
So
we
are
having
issues
with
right
now
we're
having
issues
with
fraud,
detection
and
fraud
reports.
E
We
are
having
some
issues
like
people,
don't
really
know
where
to
get
information
where
to
where
to
have
guys
of
how
how
to
become
a
client,
how
to
make
a
request.
How
to
everything.
I
I
am
I,
spend
a
lot
of
time
on
on
the
slack
Channel
across
a
lot
of
like
channels
like
channels
and
and
what
I
see
I
really
don't
see
a
lot
of
people
that
know
really
well
how
things
are,
how
things
work
and
how
to
get
those
things.
E
E
I
see
a
lot
of
people
that
don't
really
know
how
things
work
and
and
have
a
hard
time
finding
the
right
approach
to
make
requests
or
to
make
changes
or
to
understand
what
changes
are
in
effect
or
or
what
are
our
limitations,
how
the
program
works,
who
runs
it
I
see
a
lot
of
issues
like
that
in
in
slack
or
or
GitHub
or
Reddit
or
Twitter
and
and
everything
else
so
I
I
really
don't
see.
How
is
relying
on
on
storage
providers
or
clients
or
or
any
other
stakeholders.
C
F
Yeah
but
but
but
but
the
most
of
the
information
is,
is
just
on
GitHub
on
the
on
the
page,
where
it
states
what
you
need
to
do
for
an
LDN,
what
the
rules
are
for
the
LDN
and
yes,
the
the
rules
are
not
always
complete
and
there
are
some
questions
still
alive,
but
those
can
be
added
on
the
same
GitHub
page.
So
I
don't
understand
why
you
should
make
another
GitHub
page
or
another
fit
or
another
another
source
of
information
that
makes
it
makes
it
more
difficult.
F
Yeah
I
would
just
rather
suggest
to
to
put
this
on
the
GitHub
page
of
the
of
the
of
the
notary,
Channel
or
the
anti
or
the
LDN
GitHub
page
and
put
it
on
on
the
main
page
and
and
make
that
documentation
more
complete.
That
would
be
more
helpful
and
when
you
do
an
onboarding
onboarding
of
an
application
on
GitHub,
you
can
always
direct
the
people
to
that
link
and
say:
okay,
please
read
here
before
you
apply,
makes
it
more
easy
and
more
convenient.
C
Yeah
I
think
Alex.
All
the
stuff
you're
pointing
out
is
like
a
is
a
content
and
discoverability
thing
right,
which
is
like
we
need
to
have
more
consistent
and
more
complete
content,
which
is
also
I,
think
what
Brandon
is
saying
so,
basically
right
now
we
have
we
have
some
with
like
we
used
to
have
like
a
Blog,
slash
landing
page
on
the
foundation
side.
We
have
like
a
a
single
like
dock
in
the
Lotus
docs.
C
We
have
three
different
UW
repos
and
no
like
single
place
to
go,
and
then
we
have
a
website
that
has
some
basic
info
that
shoots
you
off
to
these
different
places.
So
I
completely
agree
that
we
probably
needed.
Not
probably,
we
definitely
need
to
take
a
stab
at
consolidating
the
content
and
explain
this
stuff
somewhere
that
we
can
send
people
with
confidence
and
expect
that
they'll
get
to
know
what
they
need
to
know
to
be
able
to
execute.
C
H
C
E
Yeah
yeah
one
small
comment:
I
I
point
those
things
because
I
I
understand
that
you
have
to
move
fast
and
whatnot
and
I
I.
Don't
I,
don't
know
if
it's
this
this
stuff,
if
is
suitable
for
FIP
or
whatnot,
but
my
comps
are
more
General
in
the
sense
that
we
have
to
be
careful
not
to
just
make
every
change
outside
of
FIP
just
to
make
it
run
faster
because
we
are
basically
I
may
be
wrong.
E
But
my
my
from
seeing
a
lot
of
changes
happen
outside
the
field
makes
me
wonder
if
we
are
not
just
gaming
the
system,
instead
of
going
for
the
right
path
to
make
like
solid
changes,
we
are
just
doing
the
stuff
outside
of
the
right
approach
or
whatnot
to
make
things
move
faster,
but
we
are
actually
like
not
doing
the
the
right
way.
I
I,
don't
I'm,
not
saying
that
this
is
the
case,
but
we
got
to
be
mindful
and
careful
about
yeah,
not.
C
Running
into
that
sure,
I
think
that
there
might
be
a
mismatch
in
like
what
the
expectation
is
for,
like
a
FIP,
Alexa
I
think
it's
possible
that
that
my
interpretation,
because
I
did
send
some
precedence
to
this
and
should
take
blame
for
it.
If
it's
incorrect,
then
my
interpretation
of
when
to
use
it
represent
like
not
right,
I'm,
relatively
confident
that
my
interpretation
of
when
to
use
a
flip
is
right
and
based
on
that
I
would
happily
stake
my
reputation
that
it's
totally
fine
to
proceed.
C
The
way
that
we
have
outside
of
the
FIP
system
happy
to
chat
about
that
further.
It
might
be
worth
like
having
a
conversation
with
Caitlyn
in
the
next
governance
call
even
given
to
chat
about
it.
Maybe
the
way
the
fit
process
is
evolved
in
the
last
several
months
also
means
we
need
to
adjust
and
I
think
that
that's
okay
either
way
all
right.
As
far
as
I
know,
you
know,
unless
there's
a
specific
protocol
level
change,
that's
happening
or
a
spec
level
change.
C
That's
happening,
you're
not
required
to
go
down
the
fifth
path
and
then,
additionally,
all
the
stuff
that
we're
doing
today
is
actually
just
the
same
network
mechanism
right
like.
Ultimately,
these
are
just
different
approaches
to
the
same
network
mechanism
and
so
at
a
protocol
or
spec
or
even
at
like
a
baseline
like
what
is
the
motivation
for
this?
Why
did
we
do
it
like
the
things
that
you
would
expect
in
an
initial
informational
tip?
C
Those
things
have
been
pretty
much
the
same
for
the
last
like
18
months
and
so
yeah
happy
to
chat
about
this
one
further.
It
might
be
worth
bringing
in
somebody
from
that
team
too,
and
and
make
sure
that
any
Baseline
assumptions
at
least
I'm
making
up
that
might
be
extending
to
other
people
in
this
community
are
correct.
C
A
Cool
good
discussion,
we're
at
the
one
hour
mark
So,
I,
think
what
we
can
do
is
we
can
take
that
offline
I
had
just
one
update,
I
wanted
to
say
a
big
thank
you
to
those
of
you
that
flagged
the
issue
with
the
application
signs
and
a
big
thank
you
to
Fabricio
deep
again
for
getting
that
solved.
So
if
you
were
still
having
issues
with
your
assignment
of
applications
or
anything
that
fulfill
registry,
please
let
us
know
and
a
big
thank
you
to
those
of
you
that
posted
in
the
public
Channel.
A
It
made
it
a
lot
easier
to
thread
the
issues
versus
having
them
all
come
through
on
DMs.
So
there's
a
quick
bow
on
that.
That
should
be
tied
up.
Please
let
us
know
if
you
see
anything
else,
we
had
two
applicants
that
submitted
their
videos.
These
are
people
that
would
like
you
to
review
their
process,
but
just
wanted
to
share
this
link,
one
more
time
to
you,
late
joiners.
You
might
have
missed
in
the
beginning.
A
If
you
wanted
to
mark
down
for
SLA
participation
and
those
of
you
that
submitted
your
application,
videos
I'm
going
to
post
this
into
the
application
review
and
the
notary
channel
so
that
they
can
see
you
I
know
that
we
had
a
late
entry.
I
commented
on
the
GitHub
issue:
I'd
invite
you
to
come
back
in
the
next
two
weeks
since
you
missed
this
week's
cut
off,
but
we'll
happily
give
you
time.
So
my
trade
I'll
share
this.
A
So
if
any
of
the
notaries
have
questions,
I
know
the
main
one
outstanding
is
we
were
waiting
for
you
to
verify
an
employmentization
so
with
that
we're
at
the
one
minute
Mark.
If
you
guys
have
any
discussions
or
any
topics
you
want
to
continue
to
unfold,
please,
let's
take
it
over
to
slack
and
we
can
go
from
there.
So
otherwise,
I
want
to
thank
you
all
for
dialing
in
looking
forward
to
seeing
you
on
the
next
call
and
cheers.
A
All
right,
well,
hello,
everybody
Welcome
to
the
second
governance
call
of
the
day
today
is
June
28th
at
a
very
high
level,
if
you're
just
joining
us
for
these
formats,
the
way
we
kind
of
structure
these
is
we
kick
off
with
a
high
level
introduction.
If
this
is
your
first
time
on
the
line,
feel
free
to
say
hello,
we
will
take
a
moment
just
to
kind
of
introduce
the
team.
We
briefly
look
at
the
metrics
just
to
kind
of
check
in
on
the
network
and
its
growth.
A
Then
we
request
Community
discussion
items
via
the
GitHub
repo
and
so
we'll
talk
about
any
of
the
issues
that
you'd
like
to
flag
and
we
save
time
at
the
end
for
anything
that
might
be
on
your
mind
as
we
go
through
it.
So
with
that
a
friendly
hello,
my
name
is
Kevin
on
the
line.
We
also
have
Galen
deep
and
rajef.
What
we
are
is
your
government's
team
trying
to
make
sure
that
the
network
runs
well
for
you
and
any
kind
of
questions
you
may
have.
A
We
kind
of
all
have
our
little
domain
Specialties
to
help
you
out
if
you're
on
the
line-
and
you
have
a
question
for
us
if
you
haven't
introduced
yourself
before
it-
makes
it
really
easy
if
your
Zoom
handle
matches
your
name
so
just
as
a
quick
housekeeping,
sometimes
it
might
connect
for
like
phone.
We
don't
know
how
we
can
kind
of
address
you.
So
if
you
change
your
Zoom
handle,
it
makes
it
a
lot
more
effective
to
help.
A
If
you
have
any
questions
for
introductions
on
this
call-
and
thank
you
again
for
coming
those
of
you
notaries
on
this
to
participate
and
make
sure
that
the
network
is
growing
in
a
stable
way.
Aylin
thanks
for
posting
that
link.
This
is
the
check-in.
This
populates
for
the
SLA
for
the
elections,
just
kind
of
a
quick
way
to
say
hello,
introduce
and
keep
track.
A
If
you
are
not
a
notary-
and
you
still
want
to
sign,
please
do
we'll
look
at
this
in
the
fourth
round
of
Elections,
like
hey,
who
was
coming
to
these
and
participating
and
put
that
on
the
application.
So,
even
if
you
are
not
a
notary
sign
into
this
roster,
let
us
know
below
and
we'll
keep
your
contact
information
all
right.
So
quick,
look
at
metrics
and
then
we'll
move
right
through
the
agenda,
because
we
have
a
big
full
day.
A
We
are
highlighting
four
metrics
that
we've
been
looking
at,
and
that
is
the
average
time
to
data
cap
and
average
time
to
LDN
the
response
from
notaries
and
then
the
size
of
the
network.
So
these
are
really
stable.
There
hasn't
been
a
lot
of
changes.
We
had
a
big
slowdown,
the
last
two
weeks
when
we
were
rolling
out
ldm
V3,
but
the
thing
to
call
out
right
now
is
just
looking
at
it
we're
at
no
change
for
the
average
time
to
data
cap.
A
We
are
right
around
that
five
day,
hovering
Mark
for
the
first
response
from
notaries.
So
this
is
one
of
the
things
we're
kind
of
playing
around
with
we
have
that
filter
bot.
That's
running
we're
kind
of
experimenting
with
some
ways
to
make
that
ping
go
out
to
you
in
a
very
low
friction
way,
so
we'll
be
trying
to
see
what
we
can
do
to
make.
This
response
time
for
notaries,
more
effective,
but
I
think
now
that
we
have
all
of
the
regions
in
the
philplus
sign
in
everyone
can
see
all
of
the
50
notaries.
A
This
should
start
to
drive
itself
down
so
we'll
see
that
and
just
to
call
it,
the
network
strength
we're
a
3.87.
So
this
is
kind
of
like
just
ticking
up.
You
might
see
it
like
0.5
0.3,
and
that
seems
to
be
in
our
standard
deviation
for
like
in
normal
weeks
of
growth,
and
you
can
see
that
growth
here
in
this
slide
right
now,
yellow
is
us
on
the
fill
plus
project
and
I.
Think
what
I
call
out
from
the
last
30
days
is
it's
just
a
very
stable
ramp
up.
A
There's
no
big
Peaks,
there's
no
big
valleys,
so
we're
just
seeing
just
consistent
Network
growth,
which
is
nice
and
the
same
thing
with
percentage
to
Total
Network.
It's
pretty
amazing
to
see
that
fill
plus
constitutes
79
of
all
the
daily
active
deals
and
78
of
that
deal
counts,
so
lots
of
Activity.
Thank
you.
So
much
for
everything
that
you
guys
are
doing
and
looking
forward
to
more
bar
graphs.
As
we
go
through
it
with
this
I'll
turn
it
over
again.
B
Thank
you.
Yes,
we
mentioned
that
we're
trying
to
organize
into
these
sort
of
six-week
sprints,
and
so
we
talked
about
this
at
the
last
governance,
call
just
giving
a
quick
update
and
then,
at
the
end
of
this,
in
July,
we'll
give
more
of
a
like
detailed
sort
of
check-in
on
like
what
we
hit.
Basically
LDN
is
in
Flight.
V3
is
working,
people
are
getting
their
allocations
from
that
new
multi-sig
notary.
It
should
be
showing
up
for
everyone.
B
B
There
is
an
ongoing
issue
that
is
unrelated
to
any
of
these
things
that
has
to
do
with
a
ledger
update
where
people
are
getting
an
unexpected
method
error
and
we're
working
with
The
zondax
Ledger
team
to
address
that,
but
I
still
want
to
do
some
more
tools
and
training
stuff
on
some
of
the
LDN
V3
implementations.
Those
are
still
in
the
works
as
far
as
volume
we're
over
100
Pips.
So
far.
B
This
DWD,
which
we've
talked
about
a
few
times,
but
just
to
clarify
in
case
you
don't
remember,
you're
new,
that's
days
without
data
cap,
it's
one
of
the
things
that
we
care
about
is
once
a
client
has
been
approved
on
on
any
of
the
surfaces,
but
especially
on
large
data
sets.
If
they
continue
to
operate
in
good
faith,
we
want
their
days
without
data
cap
to
be
zero
effectively.
We
want
the
subsequent
allocation
mechanisms
to
be
working
for
good
clients.
B
Then
we
have
some
more
documentation
to
post
around
engagement
and
read
me
updates.
There's
a
working
group
governance
proposal.
That
proposal
has
been
kicked
off
in
the
notary,
governance,
repo
and
we'll
also
be
talked
about
more
in
this
meeting,
and
then
we
are
continuing
to
work
on
our
trust
and
safety.
B
A
Okay,
so
these
are
the
specific
agenda
items
that
were
pulled
from
the
GitHub
repo,
as
well
as
big
ticket
items
to
kind
of
share.
We
had
a
lot
of
discussion
with
these
in
the
morning.
So
if
you
are
joining
for
this
call-
and
you
weren't
here
in
the
morning-
and
you
were
Keen
when
I
post
this
on
YouTube,
there
might
be
a
lot
more
discussion
that
you
were
Keen
to
like
watch.
So
just
as
a
quick
caveat,
there
might
be
a
lot
of
open
as
we
go
through
on
this.
So
let's
kick
off
yes,.
B
There
have
been
a
few
questions
raised
in
a
couple:
different
notary
applications
asking
for
some
more
diligence
and
clarification.
I
just
wanted
to
call
out
that
the
We
are
continuing
some
investigations
into
those
notary
applications.
We
don't
yet
have
concrete
resolutions
on
them,
but
once
we
do
we'll
be
updating
their
GitHub
applications
and
we'll
also
update
here.
So
just
if
you
have
been
curious
about
what's
happening
with
that,
it's
an
ongoing
process
and
I
don't
have
any
like
concrete
details
at
this
time.
So
in
the
works,
stay
tuned.
A
Nice
I
can
speak
to
the
Phil
plus
Day
videos.
So
big
big,
thank
you
for
those
of
you
that
came
big.
Thank
you
to
you,
Meg,
for
speaking
at
the
event,
so
we
have
them
all
posted
on
YouTube,
The
Links
there.
One
of
the
reasons
why
I
haven't
blasted
this
out
really
wide
is
we're
still
in
the
process
of
having
the
videos
added
with
subtitles
in
Mandarin.
So
just
like
the
first
fill
plus
day
that
took
place
last
year,
when
someone
watches
this,
they
can
see
the
English
spoken
and
the
Mandarin
translation.
A
But
if
you
were
curious
to
get
a
jump
on
it,
this
is
kind
of
like
an
early
release
and
then
the
purpose
of
those
Phil
plus
Day
videos
is
we
shot.
Them
was
to
kind
of
have
this
time
capsule
for
someone
joining
the
program
or
wanted
more
information.
They
can
come
and
get
a
bite-sized
bit
of
like
whatever
there
are
so
whether
they
want.
A
Considerations
the
system
overview.
It's
meant
to
be
of
like
a
welcome
guy,
that
we
can
point
new
applications,
new
notaries,
new
storage
providers,
to
learn
more
about
that.
So
once
that
translation
is
complete,
we'll
blast
that
out,
so
you
all
have
copies.
Or
if
you
want
to
see
that
now
we
have
the
link
here
in
the
deck
for
you.
A
A
So
essentially,
what
we're
hearing
is
that
the
time
zones
that
we
have
the
first
governance
meeting
in
the
second,
the
first
call
takes
place
at
around
2300
11
pm
for
Beijing,
and
the
second
call
that
we're
on
now
takes
place
at
seven
in
the
morning
Beijing,
since
a
large
number
of
our
notaries
are
coming
from
that
time
zone.
The
feedback
that
we're
getting
is
it's
difficult
to
make
these
times
work.
The
request
was
to
adjust
the
call
that
we're
on
right
now
to
be
a
little
bit
later.
A
B
Foreign,
a
couple
people
in
the
chat,
I
think
yeah.
One
of
the
questions
is
just
for
those
in
attendance.
Switching
this
to
6
PM
being
out
of
the
you
know,
nine
to
five
work
day
if
you're
you're
here
on
the
West
Coast,
is
that
still
acceptable
and
I?
Think
one
of
the
the
you
know
questions
if
it's
not
is,
could
you
make
the
the
8am
in
that
case,
Danny.
I
B
H
I
B
I
Okay,
it's
not
it's
not
great
for
for
me,
but
I
I
I'll,
see
like
we
may
want
to
think
about
just
pushing
the
8am
one
if
it
starts
not
supporting
yeah.
But
it's
not
great.
Is
it
because
that's
really
the
end
of
the
day
for
CET
as
well,
and
that's
not
even
beginning
to
take
into
account
the
rest
of
Europe,
okay
I'm,
just
going
to
accept
that
the
West
Coast,
the
United
States
is
kind
of
a
not
it's
kind
of
the
worst
place
for
time
zones,
but
okay.
A
A
All
right,
then,
aside
from
anybody
who
might
have
it
I
think
we
have
overwhelming
reception
to
this
I.
Think
we're
going
to
stick
with
that
August
time
frame
just
to
give
people
a
chance
to
like
adjust
schedules,
adjust
calendars
and
we'll
just
advertise
this
in
the
next
two
calls
that
way.
We
don't
catch
anybody
off
guard,
but
it
sounds
like
we
have
consensus
that
this
might
work
to
increase,
so
we'll
take
a
reading
I'll,
let
you
know
how
the
attendance
goes.
I
appreciate
the
feedback.
B
Awesome
yeah
I'll
take
on
this
one
Project
Beacon.
This
is
posted
in
the
governance,
repo
I'm,
going
to
drop
the
link
to
it
here.
I
encourage
all
the
notaries
and
clients
go
check
it
out.
This
is
pretty
similar
to
a
the
proof
of
concept
that
the
Seal
team
has
put
forward
in
Antarctic.
One
of
the
major
differences
with
this
one
so
far
is
that
the
data
set
bylaw
would
need
to
remain
in
China,
and
so
they
have
identified
some
Chinese
storage
providers
that
they
would
be
working
with.
B
They've
also
already
identified
some
notaries
that
they
would
be
working
with.
There
was
some
discussion
this
morning
about
wanting
to
see
some
increased
notaries
from
different
regions
and
already
since
this
morning,
I
think
that
there
have
been
a
few
comments
in
this
proposal
by
notaries,
saying
that
they
would
like
to
support
from
outside
of
that
region.
So
that's
already
great
if
you
are
also
in
that
category,
we'd
love
to
get
your
Buy
in
there
as
well.
So
I
think.
One
of
the
questions
here
is
just
around.
You
know
how?
B
What
can
we
further
learn
from
doing
these
sort
of
out
of
band
large
data
accept
proofs
of
concept?
How
much
do
we
want
to
kind
of
devote
time
and
resources
to
one-off
cases
like
this?
Do
we
feel
that
this
is
enough
evidence
that
we
should
just
change
parts
of
the
LDN
process
entirely
for
everyone
that
sort
of
thing?
So
what
I
would
love
is
to
just
open
the
floor
here
to
see
what
the
notary's
and
attendants
have
to
say
about
this
project
Beacon,
and
hopefully
you
have
either
had
a
chance
to
go.
B
B
E
Thank
you,
then
I,
don't
really
know
if,
if
we're
we're,
we
are
ready
for
dealing
with
this
kind
of
requests
and
whatnot,
because
they
still
have
a
lot
to
do
on
other
fronts
and
I.
Don't
I
it's
it's
really
hard.
If
you
think
about
it,
we
could
be
dealing
with
a
lot
of
potential
compliance
issues
and
privacy
issues
that
may
come
in
the
future
and
and
hit
filecoin
the
whole
pycon
ecosystem
really
hard.
B
How
do
we
put
that
kind
of
into
GitHub
into
a
space
to
say
this
is
the
amount
of
kyc
that
we
have
done,
but
I
think
that's
also
what
can
be
sort
of
tested
with
Pilots
like
this
is
to
ask
those
notaries
to
prove
out
the
authenticity
of
the
client.
So
I
think
this
is
where
opportunity
here
is
to
say
like
what
can
we
learn
from
doing
tests
like
this.
E
D
B
I
think
that
this
is
something
that
I
know
hold
on
has
talked
about
before,
and
we've
heard
from
some
other
SPS
that
there
are
these
regionally
required
encrypted
data
sets
that
need
to
be
archived
for
long
terms
around
things
like
education
or
Health
Data
that
could
open
up
a
very
interesting
product,
Market
fit
for
the
filecoin
network.
I
see
deep
has
a
hand,
so
I'm
gonna,
like
pump
it
over
to
Deep.
C
C
I
think
recently,
it
has
come
to
light
that
it
is
Paramount
that
that
includes
in
its
scope,
support
for
Enterprise
and
private
data
in
complex
scenarios.
That
is
literally
why
Mega's
been
working
for
several
months
to
come
up
with
a
mechanism
that
would
work
and
then
I,
see
Sal
here
and
he's
been
doing
a
ton
of
work
from
the
CEO
storage
perspective
to
sort
of
push
the
boundaries
of
this
program
as
well
and
I.
Think
it's
very
important
for
us
to
dig
this
approach
of
iteration
experimentation
and
learning.
C
It
is
unlikely
that
we
will
ever
arrive
at
a
point
at
which
we
will
never
want
to
change
the
process
or
continue
extending
and
learning
in
the
process.
It
is
likely
that
we
will
arrive
to
a
much
better
process
very
soon,
especially
with
the
work
that
the
Enterprise
tool
plus
working
group
is
doing,
but
it
is
unlikely
that
we're
just
going
to
see
no
applications
coming
in
during
now
in
the
next,
like
several
months
or
whatever
geopolitical
environments
are
complicated.
C
But
that's
part
of
what
like
Falcon
is
about
as
well,
is
like
building
a
storage
layer
that
works
for
use
cases
not
just
for
very
narrow
niches
and
Phil
plus
should
be
prioritizing
serving
the
needs
of
the
many
given
that
that
is
what
we're
here
to
build,
and
so,
when
entities
that
are
coming
up
in
countries
like
China
and
Australia
have
like
specific
data,
ordinances
or
laws.
It's
not
about.
We
can't
do
this,
it's
about.
What
do
we
need
to
do
this
and
that's
kind
of
the
approach
I'd
like
for
us
to
take?
C
It
might
be
that
there
are
cases
where
it's
like
absolutely
impossible,
and
just
so
shady
or
so
impossible
for
us
to
build
like
decentralize
your
distributed,
trust
and
those
cases
I
think
we
should
be
calling
it
out,
but
when
there's
an
option,
I
I
think
we
should
be
trying
and
learning
from
the
option.
You
know
just
for
context.
If
this
one
went
absolutely
bad
like
really
really
really
bad.
That's
60,
probably
bytes
of
data
Gap
we'd,
probably
catch
it
before
it
got
to
60
terabytes.
C
C
That's
been
handed
out
today
and
the
deals
that
are
being
made
on
chain
I'm,
talking
like
single
digit
percentages
here
and
so
I
tend
to
take
the
angle
of
like
be
a
little
bit
more
risk
affiliate
eyes
and
and
experiment
a
little
bit
mostly
because
we're
just
so
early
in
our
life
cycle
and
and
I
really
like
that.
You
know
seal
pushed
us,
and
this
is
pushing
us
to
think
like.
Okay,
like
we're
now
reaching
limitations,
where
data
can't
move
a
Geo,
we
still
want
to
build
trust
outside
that
Geo.
What
does
it
mean?
C
Is
it
a
video
tour
of
a
data
center?
Is
it
like
a
zoom
call
with
a
set
of
notaries
that,
like
the
client,
is
introduced
for
the
translation
service
and
we're
actually
looking
at
the
data?
That's
being
sealed?
Is
it
tools
that
are
being
built
to
track
cids
across
deals
and
networks?
So
we
can
see
the
replication
across
each
SP.
We've
done
some
of
the
stuff
for
slingshot,
where
we
had
to
like
trust
clients
to
take
on
a
role
and
then
represent
them
in
a
data
cap
application,
and
so
we
build
scaffolding
for
this
stuff.
C
That's
flexible
people,
the
meeting
clients
where
they're
at
today
in
their
use
of
the
network
and
then
let's
iterate,
let's
not
just
stop
it,
building
terrible
unscalable
processes
and
that's
kind
of
why
I'm
hoping
those
of
you
that
are
passionate
about
this
topic
will
pair
with
Meg
and
others
in
the
community
to
make
this
better
and
rant.
Thank
you.
E
I
Mode
of
something
like
this
is
some
sort
of
arrangement
going
on
between
every
single
member
of
the
parties
to
to
to
create
a
a
fake
deal
to
Alex's
point
I
mean
I'm,
not
too
worried
about,
but
I
don't
think
the
liability
is
something
that
the
system
I.
Don't
think.
This
raises
a
particular
challenge.
You
know
there
are
questions
about
liability,
but
I
don't
see
the
Falcon
plus
project
as
a
way
of
protecting
people
from
liability
or
assuming
liability
on
the
part
of
the
notaries
or
that
system
as
a
whole.
I
So
it's
not
a
matter
of
checking
the
data.
The
question
about
whether
it
should
about
public
data
versus
encrypted
data
is
simply
that
we
can
look
at
public
data
and
see
whether
it
matches
the
the
claims
of
it
being
useful
data,
whereas
with
encrypted
data
it
could
just
be
noise,
and
that
makes
it
more
easy
for
someone
to
create
a
fake
deal.
I
I
am
I.
I
abstain
from
kind
of
deciding
on
this
like
I.
Just
simply
don't
know,
I
wouldn't
come
in
as
a
notary
to
sign
off
on
it,
but
that's
simply
because
I
don't
know
any
of
the
parties.
I
don't
think
it's
I.
Don't
think
that
we
should
think
of
this
particular
risk
that
I've
described
as
applying
more
just
because
everybody
is
in
the
same
country
or
in
the
same
region.
I
I
My
one
question
and
thing
that
I
would
like
just
to
throw
into
this
is
it's
very
hard
for
me
to
calculate
what
the
financial
reward
is
at
this
much
storage
power
like
I,
don't
know
what
600
Pips
means
for
the
storage
providers
who
get
that
data
cap
and
I.
Think
that
might
put
the
issue
in
context,
because
I
know
that.
I
B
Sorry
yeah
go
ahead
like
the
problem,
with
being
able
to
answer
that
question.
Is
it's
an
incredibly
Dynamic
and
complex,
like
changing
Target
I
think
that
starboard
has
some
Roi
calculators
in
their
dashboards
and
you
can
see
it
but
part
of
the
reason
it's
difficult
to
say,
like
600
pibs,
for
this
many
months
would
equate
to
approximately
this
many
block.
Rewards
is
that
there
you?
You
cannot
calculate
your
relative
power
on
the
network
because
it
is
an
unknown
thing.
So,
if
you're.
B
B
Seen
like
such
changes
in
trajectory
and
I,
think
that's
where
this
issue
is
like
well,
on
average
600
pibs
means
this
is
like
well,
but
that
average
is
like
so
different
from
you
know
six
months
ago
to
now
so
I
think
that
you
could
do
a
quick
calculation
of
like
add
a
snapshot
of
today.
What
would
600
Pips
mean,
but
again,
that's
like
taking
into
account
more
static
Network
than
we
have
deep,
am
I
correct
in
that,
or
did
he.
C
I
Well,
I
I
think
I.
Think
the
thing
that
I've,
that
that's
important
to
emphasize
is
access
to
the
data
or
data
visibility
is
something
that
gives
us
a
clue
into
whether
this
is
a
legitimate
deal
or
not
I
think
sometimes
we
get
into
the
weeds
a
bit
about
whether
we're
trying
to
exclusively
support
public
data
with
the
Falcon
plus
project.
And
for
me,
that's
not
that's.
That's
a
useful
side
goal
that
I
approve
of
in
that
it's
easier
to
get
approval
for
data
cap
in
those
situations.
But
it's
not
it's.
I
It's
not
the
ultimate
goal
so
and
the
same
goes
for
sort
of
creating
a
liability
or
protection
system.
Where,
because
we
know
this
is
good,
data
storage
providers
can
feel
comfortable.
Storing
it
I
don't
think
this
program
is
in
is
the
in
the
job
of
doing
either
of
those
things
but
anyway,
but
okay,
but.
E
E
Yes,
like
you,
you
can
store
it
with
confidence
that
you're
doing
a
writing
sort
of
sort
of
so
yeah
so
that
to
the
point,
I
I
think
I
think
we
are
involved
in
in
the
process
and
and
if
you
think
about
not
only
the
upsides
but
the
downsides
of
being
part
of
something
like
this
at
the
stage
we
are
in
I
think
is
I.
Don't
think
we
are
like
necessary,
necessarily
ready.
I
If
I
can
just
answer
that
directly,
I
really
strongly
think
that
we're
not
those
that
isn't
narrow
and
I
think
that,
for
a
number
of
reasons,
one,
it's
I
feel
that,
like
very
specifically
the
origin
of
the
verified
data
program,
the
Falcon
Plus
data
is
not
to
verify
the
the
validity
of
the
data
to
for
storage
providers.
It
is
to
protect
the
ecosystem
from
self-dealing
and
I
I
kind
of
want
to
keep
pushing
that.
This
is
I,
understand
like
thinking
that
that
is
part
of
the
role
and
I.
I
Don't
think
we
do
enough
to
make
it
clear
that
that's
not
part
of
a
role
and
that's
for
a
number
of
reasons.
Right,
one
is
if,
if
we
are
in
that
role,
the
implication
is,
is
that
storage
providers
are
in
some
way
liable
for
the
content
that
they
store,
particularly
content,
that
they
stole
without
a
verified
deal
and
I
think
we
should
I
think
on
behalf
of
storage
providers.
We
really
have
to
push
back
against
that
idea.
I
That
intermediaries
and
storage
into
major
is
have
some
sort
of
strict
liability
for
the
content
they
store.
That's
not
the
case
for
centralized
storage
providers
like
Amazon,
accepting
some
extremely
narrow
cases,
and
so
it's
it's
it's.
It's
actually
opening
up
story
providers
for
more
liability
if
we
imply
that
we
are
providing
that
service.
I
That
means
that
those
storage
providers
can
potentially
argue
that
they
should
be
able
to
turn
around
and
Sue
the
system
as
a
whole
and
individual
notaries
in
particular
and
again
I.
Don't
think
that
is
good
for
the
system.
It's
not
as
good
for
me
personally,
and
it's
probably
not
good
for
anybody
on
this
call
and
that's
why
I
think
it's
really
worthwhile
emphasizing
the
very
narrow
job
we
have,
which
is
to
make
sure
that
storage
providers
aren't
making
deals
with
themselves
fake
deals
so
that
they
can
get
returns.
C
I
think
the
fake
dios
far
down
is
is
a
bit
of
a
it's
actually
a
symptom
or
like
managing
it's
a
risk
mitigate
into
the
actual
goal.
I,
don't
think
the
actual
goal
is
to
minimize
self-doing
I
think
the
actual
goal
is
to
maximize
the
usefulness
of
the
network,
which
then
people
may
find
to
have
an
abuse
Vector
that
you
then
want
to
mitigate
as
a
risk.
C
C
There
is,
then,
the
consequence
of
choosing
to
abuse
the
system,
because
you
can
and
then
us
mitigating
that
risk
by
Trying
to
minimize
the
abuse
of
that,
and
so
I
actually
think
the
definition
of
like
denoted
at
all,
I
kind
of
disagree
with
a
bit
on
on
the
premise
where
I
think
the
job
of
a
notary
here
is
to
identify
how
we
can
identify
like
how
should
we
figure
out
if
a
client
come
to
the
network?
Is
actually
trying
to
do
something
useful
for
the
network
and
so
I
think
by
design?
C
C
Yes,
it's
more
likely
than
not
that
this
client
is
here
to
use
the
network
in
the
right
way
and
what
that
actually
does
for
us
is
not
necessarily
protect
downside
but
I
would
say,
create
upside.
So,
instead
of
taking
the
pessimistic
angle
on
this,
I
would
instead
say
look
at
all
these
awesome
use
cases.
We
can
unlock.
How
do
we
give
clients
leverage
to
make
storage
providers
actually
build
a
useful
service
by
saying
okay
in
order
to
serve
these
client
needs?
You
need
to
have
a
high
quality
of
service.
C
You
need
certification,
you
need
to
scale
up
your
operation.
You
need
to
deliver
slas
Etc.
So
what
can
we
actually
do
to
create
additional
leverage
for
clients
for
search
providers
to
improve
what
they
are
offering
in
a
decentralized
storage
today,
and
then
three
like
what?
What
are
we
actually
doing
from
a
PR
standpoint
like
who
are
we
able
to
serve?
What
are
we
able
to
do
on
this
network
like?
C
How
do
we
bring
tools
and
consequences
to
keep
that
abuse
as
minimal
as
possible,
but
at
the
same
time
like
our
job
here,
is
to
enable
clients
and
enable
SPS
to
serve
those
clients
as
best
as
possible.
There's
also
a
fourth
angle
here,
which
is
like
the
actual
macroeconomic
state
of
the
network,
where
Falcon
plus
is
actually
one
of
the
only
ways
today,
with
the
way
the
the
economy
is
set
up
for,
like
SP
operations
to
Reliable
really
have
an
incentive
to
stick
around
for
the
long
term.
C
B
Right
sorry,
I
gotta
jump
in
because
we
have
other
topics
on
this
call.
So
as
great
as
these
conversations
are,
I
would
love
to
push
the
like
tactical,
specific
things,
around
Project
Beacon
to
the
GitHub
issue
itself,
and
have
these
like
ongoing
things.
If
you
think
that
there
is
something
out
of
this,
that
should
be
its
own
discussion
topic
I,
encourage
everyone
on
the
call
to
like
go
open
one
of
those
discussion
topics,
but
with
the
14
minutes
we
have
left
okay
rate.
B
C
Speak
to
this
one
yeah
I'll
make
it
real
quick.
Basically,
there
was
some
misconceptions
around
their
actual,
like
LDN
application,
and
so
CB
had
come
to
the
conversation,
because
he
wanted
to
just
have
30
seconds
to
highlight
what
the
misconceptions
were
incorrect.
A
couple
of
assumptions
as
well
as
update
their
LDN
application.
So
a
couple
of
notaries
were
concerned
that,
in
an
actual
exchange,
is
applying
to
be
a
client
on
its
own
exchange,
and
so
the
clarification
points
were
number
one.
C
And
then
the
second
is
effectively
ensuring
that
they
continue
to
bring
on
different
types
of
use.
Cases
onto
the
network
and
like
ensure
that
SPS
at
this
early
phase
are
there's
momentum
effectively
for
them
to
continue
like
using
the
platform,
giving
feedback
and
ensuring
that
they're
improving
it.
So
yeah,
please
feel
free
to
check
out
the
LDN
application
on
Big
Data
exchange
they're
excited
to
onboard
at
least
one
data
set
in
the
near
term.
To
get
these
like
insights
and
develop
some
educational
onboarding
documentation?
C
B
C
Great
D
yeah,
quick
one
on
this,
looking
at
exploring
using
a
form
instead
of
a
instead
of
like
a
standard
issue
template
like
so
instead
of
people,
editing,
markdown
they'd
just
be
able
to
fill
in
a
form.
This
should
help
with
client
ux.
It
should
help
with
validation
of
info.
It
will
result
in
more
flexibility
in
applications
that
we
create
in
the
future.
C
However,
there's
also
flags
that
we
there's
we're
going
to
accrue
technical
debt
here,
where
we
need
to
invest
a
little
bit
more
in
fixing
how
we're
scraping
GitHub
and
we
have
to
change
some
of
the
validation
happening
for
data
sources.
So
discussion
will
continue
to
evolve,
check
out
issue
565.
we're
gonna,
do
some
investigation
and
do
how
much
of
a
band
this
would
be
to
implement
on
the
software
and
Analysis
side
and
do
some
testing
on
on
the
upside
that
we'd
get
from
this
for
for
client,
ux
I.
C
A
C
J
J
A
lot
of
people
have
been
coming
in
with
how
will
this
work
and
what
have
you
thought
about
that
and
the
answer
to
most
of
them
is
no,
but
please
write
it
because
we're
going
to
go
through
those
all
those
discussions
and
whip
them
out
so
that
they
can
be
considerations,
assumptions
or
hypotheses.
So
please.
This
is
your
opportunity
to
provide
some
feedback.
J
Danny
I
want
to
connect
with
you
on
some
of
these,
like
really
important
things
that
you
were
just
raising,
then
they're
really
key,
actually
and
I
had
a
suggestion
which
I
think
the
chat
has
moved
on.
But
before
that
very
large
data
set,
do
you
want
to
do?
We
want
to
re
reskin
it
so
that
it's
smaller
and
then
we
can
deal
with?
We
can
use
that
as
a
use
case
in
this
Enterprise
program.
J
It's
something
to
think
about
like
if
it's
causing
a
depression,
I
can
sort
of
I'm
reading
the
comments.
So
I
can
see
a
fair
amount
of
debate.
If
it's
causing
friction,
we
could
just
create
a
smaller
LDN
that
runs
and
it
is
private,
but
it
has
the
notaries
doing
the
Intensive
due
diligence
and
then
the
larger
set
we
can
talk
about,
but
just
bear
in
mind
that
won't
be
for
a
few
months.
B
Yeah,
you
could
always
pitch
that
in
that
Project
Beacon
proposal
and
see
I
think
Eric
has
been
taking
the
lead
on
communicating
with
that
client
and
I.
Don't
know
the
structure
of
the
client's
data.
I
know
this
was
a
similar
question
that
was
lobbed
to
the
Seal
team
with
their
project
and
one
of
the
issues
was
that
was
the
size
of
data
that
the
client
was
specifying
and
so
that
led
to
some
of
that
fortune
and
I.
J
Be
great
test
case
actually
because
it
starts
to
expand
on
upper
limits
of
thresholds,
the
page
that
k-ray
has
put
on
the
screen
there
for
everyone.
This
some
of
these
are
the
the
high
level.
What
we
think
will
come
out
in
the
program
and
it
doesn't
need
to
alarm
anyone
just
yet.
The
only
things
that
we
needed
decisions,
I
think
summary
level
is
I've,
just
lost.
My
complete
train
I
thought.
J
The
summary
level
is
that
between
Kevin
and
I,
when
we
have
a
look
at
the
project
plan,
we're
going
to
figure
out
what
is
the
best
comms,
Cadence
and
vehicle
for
communicating
some
of
these
really
important
proposals,
and
that
this
blue
page
that
you're
looking
at
this
is
the
service
is
for
the
storage
provider,
says
for
full
transparency.
These
are
some
of
the
big
things
that
they're
going
to
be
considering
and
on.
The
previous
page,
are
the
ones
that
will
come
to
the
governance
community
to
be
to
manage
expectations.
J
B
B
B
So
you
should
see
all
those
ldns
when
you
sign
in
so
at
that
Point
see
a
comment
in
the
chat
from
Stephen
good
architectures
like
three
layers:
clients
on
top
storage,
writer's
bottom
service
layer
in
the
middle-
and
this
is
kind
of
talking
about
some
of
the
new
project
types
that
we're
seeing
like
bde,
Estuary
and
basically
figuring
out
ways
to
keep
that
middle
service
provider,
layer,
auditable
and
independent.
So
I
think
that's
a
very
good
point.
Something
to
hold
on
to
and
capture
now,
there's
nothing
further.
B
B
I
think
that
with
LDN
B3,
it
makes
more
sense
now
that
we
could
remove
that
five
petabyte
ceiling,
because
those
are
coming
from
a
separate
entity.
Part
of
that
five
petabytes
was
around
management
of
all
of
these
different
notary
multisates.
So
it
may
be
time
to
re
-propos,
changing
that
five
petabyte
ceiling
to
allow
clients
to
say
what
is
the
total
amount
for
this
project,
counting
replicas,
that
you
would
expect
across
the
lifetime.
K
Gotcha
cool,
thank
you
and
then
a
question
like
you
know,
so
we're
in
the
middle
of
a
project
period
and
ceiling
is
going
well,
the
like
so
there
there
are
four
of
us.
What
if
one
SP
just
falls
off
the
face
of
the
Earth
and
the
three
of
us
are
kind
of
left
sitting
there
has
that
happened
or
and
and
or
what
would
be
kind
of
the
solution.
B
B
As
far
as
like
has
that
happened,
we
have
seen
SPS
go
offline
for
a
variety
of
reasons,
and
so,
like
yes,
SPS
have
gone
offline,
I,
don't
know
if
that
is
directly
the
same
thing,
because
they
weren't
necessarily
as
part
of
this
proof
of
concept
where
it's
an
impact,
other
SPS
or
distribution,
but
yeah
we've
seen
SPS
go
offline.
If
that
does
happen,
I
think
that,
as
we
have
always
asked
for
its
transparency
and
how
do
we
keep
things
moving
forward
and
work
to
find
another
partner.
K
All
right,
cool
and,
and
then
kind
of
based
on
that
and
to
find
another.
Thank
you
deep.
So,
what's
and
I
know
that
we're
working
on
the
work
via
storage
provider
working
group
for
this
is
like
a
kind
of
a
place
to
find
storage
providers
and
even
like
a
a
certification
kind
of
I
know,
Stu
was
talking
about
espa,
providing
some
level
of
certification,
but
just
that.
K
B
Reputation
system
is
another
tool
where
you
can
see:
stats
on
storage
providers
and
storage
providers,
work
to
get
themselves
moved
up
in
those
rankings,
and
then
we
have
on
the
Falcon
plus
front
end.
We
also
have
a
sports
provider
table
where
you
can
find
contact
info
as
well
and
it
links
to
that
field.
Reputation
score
so
as
far
as
like,
where
can
I
go
to
find
other
storage
providers?
Those
are
two
things
that
are
top
of
mind
to
me.
B
We
also
have
seen
more
and
more
slack
storage
provider
groups
coming
into
there's
a
deal,
Market
Channel
and
then
I'm
blanket
on
the
other
one.
Maybe
maybe
deep
can
remember
it
where
storage
providers
were
doing
more
like
amas
and
asking
it
might
have
actually
just
been
a
general
AMA
channel
that
I'm
thinking
of
yeah.
C
I
would
say,
put
yourself
and
still
do
the
market,
okay
and
then
I
I
didn't
come
into
this
call.
There's
a
recording
button.
A
bunch
of
people
are
going
to
watch
this
and
might
reach
out
to
you
so
I
would
say.
Can
you
give
us
a
call
to
action
for
somebody
who's
interested
in
reaching
out
to
you
to
work
with
you?
How
should
they
get
in
touch
with
you?
C
E
C
E
H
C
C
B
Name,
Gregory
you'll
be
getting
a
ton
of
DMs,
make
sure
you
add
all
kinds
of
animal
names
to
the
end
of
it.
We
are
at
time
so
with
that
I'm
I'm,
gonna
cut
off
the
recording
and
thanks
everybody
for
their
time.
This
afternoon
evening
morning,
middle
of
night,
what
not
and
we'll
see
you
async
and
again
in
two
weeks.