►
From YouTube: Filecoin Plus - March 14 Notary Governance Calls
Description
The fifth set of Notary Governance calls of 2023 March 14 to discuss the Filecoin Plus program.
Slides and Links: https://docs.google.com/presentation/d/1OCL1e8nsR4MA_5OuaC3197BC2YWj-MKgQUcViLYq45s/edit?usp=sharing
Agenda
Governance
Road Map Introduction
Notary
Notary Onboarding How-to-video
Notary Onboarding FAQ
FIP 0056
Working Group Updates
E-Fil+ Private Data Update
T&T - 829: Conduct update
T&T - 833: KYC update
Accelerator Update https://moon-landing.io/
Proposals
Final Discussions
817, 81, 821, 829
832: Per Dataset application discussion
839: JSON Filetype discussion
Community Discussions
Monthly Community Call https://fil-org.zoom.us/meeting/register/tZMkf-2qpjIqEt3nkeKh_7f7_F6wPm76zbTw
All LDN application presentations are a-sync will be discussed in #fil-plus-application-review SLACK
If you would like to attend these meetings LIVE, the Fil+ Notary Governance calendar is available at: https://calendar.google.com/calendar/u/0/embed?src=c_k1gkfoom17g0j8c6bam6uf43j0@group.calendar.google.com&ctz=America/Los_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
All
right,
well,
hello,
welcome
to
the
first
notary
governance,
call
of
March
14th,
happy
pie
day,
everybody
so
on
this
call.
Today
we
have
the
same
kind
of
set
agenda:
we're
going
to
start
out
with
some
of
the
government's
updates
on
the
road
map
very
quickly
and
then
move
into
notaries,
notaries.
For
you,
we're
going
to
highlight
the
new
training
video
that
Phil
put
together,
we're
going
to
walk
through
some
FAQs
that
we've
been
receiving
in
slack
and
kind
of
update
that
so
everyone
can
benefit.
Then
we're
going
to
move
into
the
proposals.
A
A
For
greater
Heat
I
anticipate
having
time
at
the
end
of
this
call
for
any
discussions
or
open
issues
you
have
so
with
that,
let's
take
a
look
at
what
we
have
on
the
deck
as
a
reminder,
if
you're
ever
looking
to
join
these
notary
calls,
we
post
this
in
the
private.
Excuse
me
the
public
field
channel,
so
you
can
join
that
channel
and
see
all
the
times
that
are
coming
up
and
on
the
agenda.
If
you
add
this
to.
B
A
Google
calendar
you
can
then
follow
the
two
times
that
we
host
every
other
week.
If
there's
an
item
that
you
want
to
see
on
the
agenda
for
future
governance,
calls
we
create
a
repo
in
the
GitHub,
the
links
here
in
the
deck.
If
you
just
leave
a
comment,
hey
Kev
I
would
love
to
discuss
proposal,
One,
Two,
Three
or
a
comment
in
slack,
we'll
be
sure
to
add
it
to
the
agenda.
A
This
will
be
the
last
time
that
we're
using
airtable
for
the
SLA
participation,
so
right
now
in
the
chat
of
this
call,
I
just
dropped.
A
link
to
the
air
table
form.
This
airtable
form
is
what
you'll
use
to
fill
out
the
meeting
time
for
today.
Today's
date,
your
organization,
if
you're
a
notary,
we're
going
to
use
this
for
the
leaderboard
that
we'll
talk
about
shortly,
if
you're
a
storage
provider,
if
you're
an
applicant
if
you're
a
Community
member
joining
or
watching
this
call,
this
is
a
way
that
you
can
kind
of
symbolize.
A
Your
participation
in
the
program-
this
comes
in
really
handy
for
notary
elections
if
you
like
to
participate
in
the
future,
so
notaries
on
the
call
that
link
is
in
the
chat,
go
ahead
and
fill
out
that
airtable
form
starting
in
two
weeks,
though
we're
going
to
start
using
the
actual
leaderboard
for
the
participation
on
these
calls.
So
I
have
a
screenshot
here
of
what
it
looks
like,
and
essentially
the
flow
and
we'll
talk
about
this
in
great
detail
is
that
we
will
send
you
a
token
code
during
this
meeting.
A
You'll
then
sign
into
the
leaderboard
using
your
GitHub
handle
and
your
account
creation
you'll
then
take
that
token
code,
and
then
that
will
Mark
your
attendance
for
this
call
and
it
will
automatically
update
in
the
calls
attendance
section
of
the
leaderboard
we'll
also
go
back
and
pull
all
the
data
from
airtable
and
Port
that
in
there,
so
all
of
your
past
participation
for
2023
is
counted.
But
again
this
will
be
the
last
time
they
were
using
an
airtable
to
kind
of
log.
Our
participation
on
these
calls.
A
So
with
that
here's,
the
governance
update
if
you're
new
to
the
conversation,
we
have
a
series
of
slack
channels.
We
talked
about
these
on
every
call.
So
if
you're
looking
for
a
long
description,
I
recommend
going
back
to
the
YouTube
channel
or
if
you're
new,
just
pull
these
from
the
deck,
and
this
is
how
we're
talking
about
issues
that
impact
the
social
channels
within
Phil
Plus.
A
We
have
a
governance
team.
That's
here
to
support
you,
here's
all
of
our
names
and
our
contact
information,
we're
all
available
on
slack
and
we're
the
governance.
That's
going
to
help
you
onboard
the
data,
unblock
you
if
you're
a
notary
or
answer
any
questions.
If
you're
new
to
the
community,
if
you're,
not
sure
who
to
ping,
you
can
always
reach
out
to
me
and
I'll
route.
A
Your
question
to
the
best
POC
as
we
go
forward,
we
have
been
working
on
a
mission
statement
and
a
road
map
for
quite
some
time
and
on
the
next
call
in
the
two
weeks
on
the
28th.
Galen
will
walk
through
this
in
a
lot
of
detail,
but
essentially
what
the
government's
team
is
putting
together
is
a
road
map
of
the
projects
in
flight,
so
that
you,
as
a
community,
can
kind
of
see
what's
coming
in
development
for
tooling,
for
strategic
changes
or
documentation
and
we're
hoping
that
this
is
a
good
way
to
kind
of
loop.
A
You
in
on
what
you'll
expect
to
see
with
Falcon
Plus
in
2023
and
give
us
input,
as
we
work
to
make
this
as
stable
and
easy
to
use
as
possible.
So
we'll
have
a
real,
detailed
update
on
this
one
in
two
weeks.
Just
wanted
to
make
you
aware,
as
a
community,
that
we're
working
on
this
right
now
and
we'll
have
updates
to
follow
in
the
next
call.
A
A
B
A
A
This
is
a
great
way
for
you
to
weigh
out
of
this
fifth,
if
you
haven't
done
so
already
all
right
notaries
with
that,
let's
get
to
all
your
issues
right
off,
so
in
slack
we
had
three
issues
that
kicked
off
in
the
week,
just
kind
of
giving
you
a
roll-up
of
where
those
issues
stand
and
make
you
aware
the
first
was
the
dashboard.
This
was
flagged
by
Winan,
where
it
was
currently
not
displaying
full
data
cap
allocations.
A
It
went
through
big
shout
out
to
Phil
and
Simon
and
all
the
whole
teams
on
our
contractor
for
fixing
this.
So
this
is
good
to
go
if
you're
still
seeing
issues,
let
us
know,
but
as
of
last
testing
over
the
last
two
days,
this
has
been
fixed.
The
second
issue
that
was
flagged
was
the
glyph
verifier.
So
this
is,
if
somebody
is
requesting
less
than
32
gigs
of
data,
they
can
automatically
just
connect
to
that
data
allocation
request
with
their
GitHub
application,
and
we
had
a
flag
earlier
in
the
week.
A
That
system
was
not
operated
as
intended.
So
thanks
for
flagging
this
again
thanks
to
Phil
and
Simon,
you
guys
running
this
down
and
making
sure
that
it's
all
set.
So
again,
this
should
be
back
up.
If
you
see
any
issues,
let
us
know-
and
the
third
was
just
linking
the
community
Standards
Board
for
any
kind
of
slack
discussion.
We've
kind
of
talked
about
this
on
some
past
calls
is
just
making
sure
that
it
is
we're
communicating
we're
doing
so
like
in
a
business
professional
way.
A
If
we
have
any
discussions
that
might
take
long
term,
it
goes
into
GitHub
and
we're
using
slack
for
like
flagging
issues,
rapid
iteration,
but
we
shouldn't
be
using
any
kind
of
terminology
on
names
or
any
kind
of
derogatory
sling
as
it
goes
off.
So
as
a
friendly
reminder,
if
in
doubt
Trend
to
business
Communications,
it
will
be
good
to
go.
Hey.
D
So
there's
one
more
issue
that
I
want
to
add
and
that's
the
fact
that
the
SSA
bought
since
I
think
this
Friday
was
not
working
properly.
It
wasn't
showing
up.
That
was
because
it
wasn't
getting
data.
It
wasn't
understanding
that
the
wallets
are
are
empty
for
for
many
LDN
applications.
So
that's
why
you
don't
see
the
bot
showing
up
and
that's
because
the
API
that
we're
getting
that
data
from
is
wasn't
working
properly,
so
that
data
was
also
from
glyph.
D
Those
are
all
because
prob
likely
because
glyph
is
making
an
update
for
the
fvm,
it
seems
very
transitory
and
I
think
it
shouldn't
come
up
again.
If
it
does
then
we'll
investigate
it
more
and
we'll
have
like
logs
in
place,
and
we
can
talk
to
the
glyph
team
to
handle
the
situation
yeah.
That's
that's
good!
That's
all!
For
okay,
thanks.
A
With
that,
if
you're
a
new
fourth
round
notary,
this
is
your
first
time
being
added
to
the
LDN
or
the
multi-sig.
Congratulations,
so
Phil
put
together
a
very
detailed
walkthrough
guide
and
it's
hung
on
the
public
YouTube
channel
for
filecoin
plus,
and
what
it
is
is
a
short
five
and
a
half
minute
video
it
just
kind
of
covers
the
basic
steps.
How
do
you
log
into
the
registry
when
you're
in
the
registry?
How
do
you
connect
your
Ledger
once
you've
connected
your
Ledger
and
your
GitHub?
A
How
do
you
find
the
applications
and
go
back
and
sign
up?
So
if
you
were
a
new
notary
and
you're
looking
for
just
like
a
how
do
I
simply
tldr
this
process
to
use
the
tooling
Phil
did
a
great
job,
putting
this
together
as
a
quick
recap,
we're
using
the
registry
to
sign
in
to
view
the
applications
and
select
them
you
can
also,
then,
in
the
registry
open
up
a
GitHub
and
in
GitHub
you
can
then
see
all
of
the
details
on
the
application
who's
the
organization.
How
long
have
they
been
around?
A
Where
are
they
using
the
data?
How
are
they
story
mode,
and
all
of
those
comments
can
populate
in
GitHub,
so
by
using
the
registering
GitHub
you'll
be
really
effective
to
kind
of
go
through
there?
Do
your
diligence
make
sure
that
it's
transparent
and
then
allocate
your
data
cap?
If
you
have
any
questions
on
this
process,
the
fill
private
notaries
channel
is
a
great
way
to
ask
that
question.
It's
a
small
community
of
just
notaries
and
governance
team
and
we'll
unblock
or
answer
anything
that
you
may
have
with
that.
A
These
are
the
FAQs
that
I've
gotten
via
DMS
over
the
last
couple
of
days.
So
I
wanted
to
make
sure
that
this
information
lived
on
past
that
Silo.
So
the
first
question
I
got
was
hey
I'm,
looking
at
an
application
and
I
see
that
another
notary
has
started
diligence
but
has
said
that
they
are
not
going
to
sign
that
application.
For
whatever
reason
does
that
mean
is
I,
as
a
notary
can
no
longer
sign
that
application?
Well,
here's
the
answer!
You
can
still
sign
it.
A
So
in
this
case,
where
you're
looking
at
an
application,
somebody
has
already
said
that
they
won't
sign
it
for
whatever
reason,
that
does
not
mean
that
that
application
is
completely
stopped.
If,
in
the
process
of
your
diligence,
you
uncover
additional
information,
or
you
know
this
provider
or
application
and
you're
able
to
reach
out
and
connect
that
you're
more
than
welcome.
There
will
be
different
standards
within
the
notaries
on
how
they're,
approving
and
reviewing
and
onboarding
this
data.
So
again,
just
because
one
notary
has
said
no
doesn't
mean
that
you
have
to
say
no
as
well.
A
A
The
second
is:
can
you
use
a
form
to
collect
diligence
on
an
application?
Some
of
the
most
really
successful
notaries
that
are
signing
a
lot
of
data
do
in
fact
use
a
form,
so
they've
created
either
a
Google
form,
an
airtable
or
another
setup,
and
it
requests
some
of
the
most
common
information
that
they're
asking
in
GitHub
like
who's,
your
organization.
How
long
have
you
been
in
business?
Where
can
I
find
more
examples
of
the
data,
whatever
you
want
to
put
in
that
form
as
long
as
it
correlates
with
your
data
diligence
plan?
A
So
again,
a
form
is
just
fine.
The
only
thing
that
I
would
caution
is
is
make
sure
that
you
keep
it
transparent.
So
if
you
are
using
that
form
linking
to
it
so
that
the
community
can
see
what
questions
you're
asking
and
if
it
ever
comes
back
and
we're
saying
hey,
can
we
do
some
kind
of
an
audit
on
what
this
form
data
was
you're
able
to
provide
that
at
a
point
in
the
future?
So
again,
a
diligence
form
is
just
fine
in
some
of
the
top.
A
A
So
what
I
mean
by
this
is,
if
you
are
doing
any
Communications,
whether
it's
in
slack
or
whether
it's
an
email
or
any
kind
of
offline
sources
of
communication,
be
sure
to
come
back
into
GitHub
in
that
application
and
leave
a
comment
like
hey
I'm,
Kevin
I
did
diligence
on
this
application
via
an
email
and
talking
with
them.
They
answered
one
two
and
three
questions.
A
This
is
the
diligence
plan
that
I
followed,
so
just
making
sure
that
you're,
mindful
of
increasing
that
transparency
in
GitHub,
will
make
sure
that
you're
putting
that
all
in
the
right
place
and
fourth,
hey
I'm,
a
new
notary
where
do
I
go
to
find
these
applications
to
sign
them.
So
you
have
three
different
places
that
you
can
go.
The
first
is
in
slack
we
have
a
channel
called
fill
plus
applications.
What
we
ask
is
anybody
who
submitted
an
LDN
application
hasn't
seen
it
signed.
A
They
can
then
go
in
that
slack,
Channel
and
say:
hey
my
name's
Kevin,
here's,
my
application,
I'm
looking
for
a
notary
to
sign,
and
when
you
see
those
in
slack
it's
a
little
bit
easier
to
communicate
with
those
applicants,
because
you
know
you
not
only
have
a
GitHub
way
to
contact
them
as
well
as
slack.
So,
if
you're,
a
notary
looking
for
applications
to
get
on
board
with
that's
a
great
place
to
start,
is
just
check
those
applications
and
start
diligence
there.
A
The
second
is
in
the
actual
registry:
it
will
list
the
ldns
that
are
awaiting
signature
right
now,
it's
around
300
and
there's
no
way
to
sort.
So
sometimes
that
makes
it
a
little
bit
confusing
as
a
newer
notary
to
find
out
what
to
actually
go
through.
Phil
addresses
this
in
the
walkthrough
guide
that
he
put
together.
A
But
if
you
actually
wanted
to
see
what
LDN
applications
came
back
going
to
GitHub
and
just
viewing
those
GitHub
applications
is
also
an
easy
way
to
just
kind
of
scan
through
if
something's,
in
your
country
of
origin
or
in
your
wheelhouse
as
far
as
workflows,
that's
a
really
effective
way
to
pull
those
out.
So
these
are
the
four
questions
that
I've
got
recently
via
DMS
wanted
to
flag
it
and
I'll
pause
to
see.
If
anybody
has
any
questions
or
elaborations.
F
A
Because
your
notary
information
is
public
in
the
repository
some
applicants,
May
DM
you
that
is
just
fine.
So
if
an
applicant
DMS
you
and
says
hey,
can
you
please
review
my
application?
That's
good
to
go.
All
I
would
say
is
be
sure
that
you're
doing
the
diligence
in
the
application
means
that
if
Lucky
was
to
message
you
and
say
hey.
Can
you
please
look
at
my
application
and
you
look
at
it
any
kind
of
communication
on
the
application
isn't
taking
place
in
that
slack,
but.
A
A
Okay,
we
launched
the
multi-sig
about
two
weeks
ago.
This
was
eight
three
five.
There
were
some
notaries
that
changed
their
Ledger
address
or
had
technical
blockers
or
I.
Think
we've
had
everyone
complete
the
disclosure.
So
what
we're
doing
right
now
is
we
opened
up
a
two-week
Sprint
to
collect
any
additional
information
on
The
Ledger?
This
is
a
manual
process
that
we
have
to
go
through
now.
To
manually.
Add
you
folks,
so
if
you
were
one
of
the
notaries
that
did
not
have
your
Ledger
at
hand,
we
are
manually
adding
you
in
that
process.
A
What
we're
doing
is
we're
bunching,
those
together
and
putting
them
in
we're
updating
that
GitHub
issue.
835
I
think
this
only
impacts
about
three
or
four
notaries
that
missed
that
initial
Ledger
change
date.
Just
to
let
you
know
we're
going
to
put
this
in
probably
end
of
week
or
early
next
week,
and
then
we'll
maybe
do
one
more
update
batch
after
that.
So
if
you
haven't
verified
your
Ledger,
we
will
manually
add
you
in
everybody
else
who
has
completed
their
disclosure
form
that
has
set
up
their
Ledger
and
verified
it
in
the
registry.
Congratulations
you're!
A
All
set,
we
filled
the
multi-cig
about
a
week
and
a
half
ago
with
data,
and
you
were
cleared
to
start
signing
so
notaries.
You
have
the
onboarding
guide,
you
have
the
FAQ,
you
have
the
data
and
you
have
the
slack
for
whatever
support
we
can
give
you
good
luck,
great
things
and
we're
here
to
support
you.
However,
we
can
so
with
that.
Let's
take
a
look
at
the
next
section
we
have,
which
is
the
open
proposals,
so
we
had
four
issues
that
were
in
the
last
stage.
A
A
A
We
had
this
issue,
we
discussed
it
on
the
last
call.
This
was
flagged
by
the
community.
Thank
you,
and
it's
essentially
saying
if
you
have
multiple
data
sets,
should
they
be
in
one
single
application
or
should
they
be
spread
across?
We
discussed
this
on
length
on
The
Last
Call
on
February
28th.
We
had
some
Lively
chatter
in
this
one
in
the
GitHub
application
itself.
So
just
wanted
to
see
one
last
time
if
anybody
has
any
thoughts
or
any
questions
on
this
application
before
it
kind
of
moves
into
final
review.
A
So
this
proposal
is
to
converting
those
files
to
a
Json
file
to
increase
the
trust
and
transparency
and
standardization
and
reliability.
We
talked
about
this
briefly
on
the
last
call
I'm
going
to
pause,
Phil
I
know
that
you've
been
leading
the
charge,
if
there's
anything,
you'd
like
to
add
to
this
or
anybody
in
the
community.
This
is
a
great
time.
D
D
There
are
pros
and
cons
to
each.
If
it
is
one
big
Json
file,
it
is
easier
to
scrape
since
it's
just
one
file
supposedly
and
well.
It
is
like
it
also
minimizes
the
number
of
files
in
the
GitHub
repo
itself,
because
there
might
be
a
Max
limit
of
Json
files
that
it
can
have
now.
The
problem
with
one
big
Json
file
is
that
there
might
be
merge
conflicts
if
in
case,
we
want
to
edit
two
applications
at
the
same
time.
That
could
lead
to
really
bad.
D
E
A
G
G
So,
as
you
can
see
in
q1
here,
we've
had
11
new
applications
come
in
which-
and
we
kick
this
pilot
off
in
end
of
October.
So
over
a
five
month
period,
we've
had
25
applications,
so
we're
averaging
around.
You
know
five
to
six
applications
per
month.
So
it's
good
to
see
we're
continuing
this
continuing
to
have
applicants
sort
of
apply
and
go
through
the
process
on
the
chart
on
the
right.
You
can
see
the
top
chart,
the
sort
of
shows.
The
phase
is
that
I'm
measuring,
as
applicants
are
going
through
so
they're
expressing
interest.
G
Then
they
register
they
go
through
the
KYB
check.
Some
of
them
have
to
find
SPS
to
complete
the
application,
and
then
they
await
their
first
allocation
of
data
cap
and
then
their
their
onboarding
data.
So
you
can
see
we
have
multiple
clients
right
now,
waiting
on
KYB,
so
they're
going
through
the
process
of
getting
approved
and
also
we
have
nine
applicants
that
have
received
data
cap
and
our
onboarding
data
making
deals
the
other
chart
at
the
bottom
there
on
the
right
is
just
a
snapshot
of
applicant
locations,
so
you
can
see
we
have
I.
G
Have
the
statistics
listed
here:
16
applicants
from
Asia,
five
from
USA
and
four
from
Europe.
So
it's
a
good
distribution
there
we'd
love
to
see
continued
success
across
different
regions
of
the
world
and,
overall,
this
pilot
is
representing
100
plus
pids
potential
beta
cap
to
be
approved
and
allocated.
There's
a
link
there
that
you
can
go
in
and
look
at
each
application
individually.
G
If
you
wish
we're
ongoing
with
testing
for
kyc
and
KYB
so
know
your
customer
know
your
business,
we
have
some
third-party
products
that
we've
been
working
with,
clients
are
utilizing
to
get
approved
and
that
helps
them
build
initial
trust,
especially
if
they're
a
brand
new
actor
in
the
ecosystem.
This
gives
them.
G
We'd
also
like
to
start
automating
some
of
the
processes
that
I'm
manually
managing
right
now.
So
that's
assigning
notaries
following
up
on
on
comments
and
those
types
of
things
and
then
finally
we're
looking
to
increase
the
allocation
request
amounts
again.
This
is
part
of
a
larger
Enterprise
initiative.
So,
as
we
have
larger
data
sets
coming
in
from
Enterprise
customers,
we
want
to
be
able
to
to
allow
them
to
see
datacap
in
larger
allocation
amounts
so
that
they
can
onboard
data
efficiently.
G
So
we're
going
to
test
that
here
at
the
end
of
this
quarter
with
we
have
an
application
from
CERN
via
cosp
they're,
going
to
be
onboarding,
a
small
POC
of
three
and
a
half
Pips,
and
then
once
that's
done,
they're
gonna
we're
gonna
up
the
allocation
request
amount
to
over
six
and
a
half
Pips
times
five
copies,
so
it'll
be
20,
plus
Pips.
So
that's
good.
All
the
details
are
listed
on
the
website
at
the
bottom.
If
anyone
has
any
questions,
you
can
reach
me
in
slack,
Kevin,
Z,
okay,
great
thanks
thanks
Kev
any
questions.
G
I've
been
on
and
off
with,
so
the
calls
are
bi-weekly
every
other
Tuesday
following
the
same
timing
as
the
the
notary
call.
So
it
would
be
next
Tuesday
and
I
will
update
the
calendar.
We'll
likely
have
a
call.
Participation
has
been
quite
low,
so
what
I've
been
doing
is
doing
sort
of
a
an
async
update
in
the
efo
working
group.
Slack
channel
providing
updates
there,
so
I'll
likely
have
a
call
next
week
and
then
we'll
we'll
continue
for
now
yeah.
H
H
Is
the
average
data
cap
yeah,
the
usual
average
I
know
you
the
sample
size
is
not
a
lot,
but
what
is
the
typical
size?
What
is
the
typical
waiting
time?
Because,
as
you
know,
there
are
a
few
clients
that
approach
us
on
a
big
data
exchange
and
some
of
them
they
don't
have
data
cave
yet.
I
just
want
to
manage
your
expectation
on
both
sides.
G
That's
it's
a
great
question.
Actually
I
and
I
think
we're
we're
keeping
those
statistics
on
the
main
statistics.
Page:
okay,
right,
I,
don't
know
if
you
have
the
ability
to
pull
that
up
right
now.
The
interplanetary
statistics
and
it'll
show
you
just
regular
LDN
tied
to
data
cap
and
then
there's
an
e-fill,
a
separate
section.
H
G
A
A
Izzy,
thank
you
for
the
update,
CB
great
question.
Thank
you
for
that
and
Phil
thanks
for
putting
that
waiting
for
everyone
to
see
as
we
go
forward.
If
we
have
any
more
questions
on
e-fill
plus
we'll
have
plenty
of
time
at
the
end
of
the
discussion
to
Circle
back
to
this.
If
anything
comes
to
mind
with
that,
I'll
turn
it
over
to
sweet
RG
for
trust
and
transparency
updates.
I
Thanks
so
much
Carrie,
so
just
a
few
quick
poses
here:
I'll
discuss
them
more
broadly.
Next
week
in
the
ATT
working,
your
calls.
Most
of
the
proposals
were
passed.
So
the
the
issue
that
issue
into
nine-
if
you
go
to
it,
was
about,
do
we
create
a
standalone
code
of
conduct,
and
then
there
was
a
discussion
in
which
some
of
the
folks
here
on
call,
including
Danny
and
put
their
input
so
kind
of
the
the
way
they
move
forward
is
two
parts
one.
I
So
the
second
part
to
this
is
that
there's
there's
a
few
questions
around
okay
who
will
enforce
the
code
of
conduct
so
right
now,
until
the
details
are
on
the
TNT
board
are
finalized
and
the
details
include
the
legal
team
and
Falcon
Foundation
getting
back
to
us
on
the
different
mechanism
designs
for
staking
that
would
propose
and
their
their
recommendations
on
that.
Until
we
have
that
feedback,
we
will
proceed
with
the
current
kind
of
consensus
model.
Where
you
know
we
will
open
a
GitHub
issue.
I
I
These
are
not
exhaustive.
Please
look
out
for
tomorrow
for
the
exhaustive
code
of
conduct.
Most
of
a
lot
of
it
will
be
guidelines
focused.
So
it's
it
won't
say
things
like
you
know.
This
word
isn't
allowed
and
this
word
is
allowed.
I
know
there
was
a
few
questions
on
the
issue
itself
and
that's
not
the
point
of
code
of
conduct.
I
So
the
next
one
is
about
upfront
kyc
This
was
there
was
a
lot
of
positive
comments
on
this,
so
this
proposal
is
considered
past.
The
main
concern
was
were
two
one
was
regarding
kyc
solutions
for
the
Asia
region,
and
then
the
other
concern
was
regarding
the
philippos
governance
team
becoming
a
data
owner.
So
right
now
the
approach
that
we
have
decided
to
take
is
we,
as
the
change
to
working
group
are
recommending
community
members
to
do
so
checks.
I
We
already
have
some
human
community
members
in
Europe
who've
taken
the
initiative
to
create
a
form,
and
you
know
do
these
checks
the
trail
for
that
is
actually
available
on
issue
833.
So
the
way
we
want
to
move
forward
with
this
is
we
want
to.
We
want
to
encourage
other
community
members
from
other
regions
to
take
charge
of
scoping
out
a
third-party
kyc
vendor,
so
that
might
be
trulio
truly
you
which
has
been
mentioned
in
the
issue,
or
that
might
be
another
kyc
vendor
that
we
haven't.
I
But
that's
kind
of
you
know
how
we
want
to
move
forward.
I
think
this
approach
is
decentralized
enough,
if
not
the
best
solution
to
enable
third-party
kyc
and
address.
You
know
upfront
top
of
the
funnel
abuse,
because
one
of
the
big
concerns
that
came
up
in
January
is
we
have
a
lot
of
people
applying
for
data
cap
who
might
be
fake
accounts
for
fake
applications,
and
so
there
needs
to
be
a
cost
associated
associated
with
applying
for
datacap
and
data
cap
is
a
very
novel
resource
in
the
network.
I
I
Yeah,
so
this
is
very
early
on,
but
I'm
just
finding
this
so
I
I
was
told
by
someone
from
the
SP
Grove
team
at
vertical
Labs
at
the
greater
heat,
which
is
a
large
Falcon.
Sp
is
initiating
a
program
to
convert
30
new
30
existing
non-public
miners
to
become
wildcon,
SPS
and
they're,
looking
to
bring
close
200
Pips
of
Rob
by
power
data,
which
roughly
translates
to
1000
Pips
of
data
cap
that
will
be
flowing
and
so
right
now
they.
I
What
I've
been
told
so
far,
is
it's
all
public
data
they're
willing
to
do
kyc,
so
we
will
not
be
using
UFO
Plus
for
this
we
will
be
using
the
the
you
know,
the
normal
LDN
process,
but
I
still
want
to
flag
this,
especially
from
the
TNT
perspective
that
you
know
they.
The
the
new
miners
will
not
get
any
kind
of
special
treatment
in
terms
of
their
deal
making,
but
we
do
want
to
make
sure
that
you
know
their
transition
to
become
Falcon.
I
Miners
is
smooth
and
so
right
now
this
is
just
a
just.
You
know
like
a
FYI
for
the
community
and
I'm
still
waiting
to
hear
on
details
and
I've
requested
the
representative
from
greater
heat
to
create
an
issue
on
GitHub,
and
you
know
publicly
explain
their
project
so
that
there
could
be
full
transparency
on
you
know
what
they're
trying
to
do.
I
think
this
opens
up
a
lot
of
exciting
opportunities
as
well
as
this
pilot
itself.
I
So
if
you
are
kind
of
further
interested
in
this
topic
or
want
to
learn
more,
you
can
just
DM
me
or
wait
for
the
public
issue
to
come
out,
but
yeah.
Those
are
the
three
main
updates
from
trust
and
transparency
and
I'll
be
discussing
all
of
these
three
as
well
as
more
issues.
Next
week
on
Tuesday
at
the
trust
and
transparency
working
group
call.
A
A
A
D
Hey
Carrie
I
want
to
bring
up
one
thing,
one
more
thing
actually,
so
many
of
you
may
or
may
not
know
that
today
is
the
going
to
be
the
launch
of
the
Fem
so
onto
mainnet,
and
so
there's
going
to
be
many
opportunities
for
us
going
forward
to
to
build
stuff
on
the
fvm
for
fill
plus,
for
example,
now
on
the
fvm.
Now
you
can
get
data
cap
as
smart
contracts.
D
D
J
I
lead
a
program
called
moon
landing
and
it
is
a
program
to
also
facilitate
newer
recipes
to
onboard
our
ecosystem
by
storing
large,
open
data
sets
we
used
to
leverage
slingshot,
but
now
I
am
expanding
to
you
know
outside
of
slingshot
data
sets
as
well.
So
you
might
see
some
of
our
moon
landing
participants
acting
as
data
preparers
asking
for
LDN
and
data
cap,
so
that
they
can
work
with
storage
providers
also
participating
in
the
moon,
landing
program
to
store
these
data
sets
and
the
program
replication
incur.
J
A
A
K
K
We
are
launching
our
first
Community
governance,
Town
Hall
so
feel
free
to
join.
If
you
want
to
listen
to
or
if
you
want
to
participate
in.
You
know,
governance
processes
at
that
sleep
level,
as
well
as
understand,
what's
going
on,
discuss
challenges
and
also
share
your
thoughts
in
terms
of
how
we
can
improve
the
governance.
K
For
you
know,
Improvement
proposals
for
filecoin
as
a
protocol
I
will
leave
a
registration
link
feel
free
to
register
it's
commencing
on
the
27th
of
March,
and
you
are
all
welcome
to
join
us
filecoin
community
members.
This
is
definitely
different
from
your
coin.
Plus
governance
calls
so
we
are
just
covering
the
entire
file
coin
ecosystem
and
discussing
fips
file
coin
Improvement
proposals.
K
K
Any
question
so
we
are
it's
the
first.
The
first
call
coming
up
is
definitely
the
inaugural
composition
and
we're
hoping
to
discuss
fifth
of
all
governance
101,
which
is
essentially
letting
community
members
know
what
happens
when
an
improvement
proposal
is
sent
for
for
review
for
The
Wider
community
members.
L
A
K
Definitely
I'm
talking
about
56
I
think
he
also
mentioned
that
earlier.
It's
in
the
last
call
phase.
So
if
you
have
not
already,
you
know
waited
shared
your
comments
or
thoughts.
This
is
another
opportunity
for
you
to
do
so.
It
will
be
in
the
last
call
phase
for
another
two
weeks.
Hopefully
I
think
it
will
leave
the
last
call
phase
on
the
24th
of
March
I
believe
after
which
we'll
be
adopting
a
hybrid
soft
consensus
approach
in
terms
of
reaching
a
decision
on
that
fit.
A
All
right,
well
with
that.
Thank
you
so
much
for
coming
to
this
first
call
of
the
governance.
We'll
have
this
on
YouTube.
Shortly
and
again
as
a
friendly
reminder,
the
next
governance
call
will
take
place.
California,
Pacific,
Time,
6
p.m,
UTC
zero!
One
hundred
thanks
for
coming
guys
all
the
best
we'll
see.
A
All
right,
big,
friendly
hellos
and
welcome
to
the
second
notary
governance
call
of
March
14th.
Let's
take
a
look
at
what
we
have
in
store
for
today,
we're
going
to
kick
off
with
updates
around
notaries.
So
we
have
the
update
around
the
onboarding
guide:
how
to
look
at
that
video
where
to
access
it
and
what
content's
in
it.
A
We
have
a
couple
of
the
FAQs
that
have
come
through
and
slack
to
make
sure
that
you're
getting
the
latest
to
greatest
on
that
and
then
just
helping
with
slack
discussions
that
might
have
missed
your
radar
and
giving
you
an
update
across
those
we'll
move
right
into
proposals.
After
that,
we
had
a
couple
of
outstanding
items
that
have
been
on
the
radar
for
the
last
couple
of
weeks.
A
One
last
final
discussion
opportunity
before
we
move
forward
as
well
as
two
that
were
started
from
the
community
and
Phil
that
we'll
walk
through
and
just
make
sure
that
you
have
a
chance
to
get
these
on
your
radar
and
get
a
chance
to
discuss
as
we
go
forward
for
the
two
working
groups.
We
have
updates
from
the
Enterprise
field
plus,
as
well
as
trust
and
transparency.
Kevin
Z
was
on
the
morning
call
as
well
as
our
gene.
They
kind
of
gave
an
update
in
their
absence.
A
A
This
governance
call
takes
place
on
UTC,
1500
and
0-1
I
think
there
might
be
some
scheduled
conflicts,
so
I
might
reach
out
to
you,
notaries,
in
the
notaries
channel,
to
make
sure
that
this
time
frame
still
works
with
all
of
the
time
zones
taking
place.
Just
making
sure
that
we're
keeping
this
at
a
time
that's
conducive
for
the
majority
of
the
callers
from
around
the
world,
but
we
do
have
this
posted
in
the
Google
Calendar.
A
So
if
you
ever
see
that
there
that'll
be
the
source
of
Truth
and
what
we're
looking
at
and
going
forward
on
that
take
just
one.
Second,
we
also
post
the
agenda
in
GitHub
as
a
quick
reminder.
If
there's
any
topics
that
you
want
to
see,
discussed
or
flagged
or
reviewed,
just
drop
a
comment
in
that
GitHub
issue:
I'll,
pull
that
up
and
then
we'll
go
from
there,
and
then
we
have
the
notary.
Soa
formed
we've
been
using
airtable
for
this
for
the
past
few
months.
A
It's
worked
really
well
to
kind
of
Link
this
back
to
all
the
notaries
that
are
on
the
call
and
give
you
a
chance
to
kind
of
get
your
participation
logged
in
I'm
dropping
the
link
to
airtable.
Now
this
will
be
the
last
week
that
we're
using
airtable
for
the
sign
in
for
these
notary
governance
calls,
as
we
scale
we've
now
getting
ready
to
roll
out
the
notary.
Leaderboard.
A
What's
nice
about
this
leaderboard
is
it
will
have
all
the
stats
as
far
as
like
signing
participation,
so
in
future
sessions
we'll
talk
about
how
to
fill
this
out,
but
it's
a
quick
plug.
What
it
will
mean
is
you'll,
receive
a
token
code
on
the
governance,
call
you'll
sign
into
your
notary,
leaderboard
page
with
that
token
code,
and
that
will
Mark
your
attendance
and
update
automatically
into
this
call
without
the
main
annual
process
of
us
going
on
the
back
end
and
making
sure
that
we
have
the
right
participant.
A
A
A
We
all
specialize
in
one
specific
area,
so,
if
you're
looking
for
help
or
support
reach
out
to
us
and
we'll
be
able
to
help
you
out
if
you're
unsure
who
to
reach
out
to
or
where
that
question
is
best
asked
again,
if
you
send
me
a
friendly
DM,
Kevin,
Dash
FF
I'll
be
happy
to
help
you
out
as
we
go
forward
on
this
one.
If
this
is
the
government's
team
and
we're
here
to
help
you
I'm
sharing
this
we're
going
to
talk
about
this
in
a
lot
more
detail
on
the
call
in
two
weeks.
A
Essentially,
what
this
is
is
the
notary
governance
roadmap
that
we're
working
on.
So
what
this
will
do
is
this
will
outline
the
projects
that
the
team
is
working
on
to
improve
the
project
and
make
it
a
little
bit
more
stable
for
everybody
going
forward.
So
what
we're
kind
of
doing
is
looking
at
these
from
three
aspects,
essentially
the
documentation,
the
tooling
and
then
also
the
Strategic
exchange
proposals
that
go
along
with
these.
A
Now
we
have
a
Community
member
that
started
off.
Excuse
me,
just
the
fif0056
we
talked
about
this
in
detail
in
the
morning
call,
and
we
invited
Lucky
from
the
filecoin
foundation
to
come,
join
us
and
give
a
little
bit
more
clarification
on
this.
Essentially,
what's
going
on
right
now,
with
this
FIP,
it's
in
the
final
call
for
any
kind
of
input,
so
I'm
going
to
drop
the
link
here
in
chat
in
just
a
moment,
but
in
this
discussion
thread,
there's
a
lot
of
communication
on
this
fit.
C
C
A
Pause
to
see
that
nobody
has
any
kind
of
issues
to
bring
up
on
this
one,
it's
kind
of
straightforward,
then
there's
also
a
lot
that
goes
into
it
with
the
sector,
multipliers
and
functions
on
this
one.
There
is
a
community
call
that
happens
monthly
where
they
discuss
this
in
a
lot
of
detail.
They
take
input
from
the
community.
I
shared
the
details
for
that
call
after
the
morning
and
the
fill
plus
slack
Channel
and
the
thread
again,
if
you'd
like
to
join
that
or
get
any
more
questions,
we'll
be
happy
to
flag
it
and
I.
A
A
So
with
that
over
the
notary,
specific
portions
of
the
call,
there
were
a
few
issues
that
came
through
in
slack
just
bringing
these
to
the
top
of
Mind.
In
case
anybody
was
tracking
these
or
had
any
questions.
There
were
essentially
four
Phil
I
know
you're
on
the
call
I
spoke
to
these
in
the
morning.
Would
you
like
to
add
any
clarification
just
to
kind
of
mix
up
the
audio
on
this.
D
M
The
glyph
team
updated
and
compressed
that
file
that
we
use
with,
and
so
without
us,
knowing
knowing
that
we
ended
up
using
that
same
file
and
we
weren't
basically
able
to
show
some
of
the
data
that
people
were
expecting
to
see.
But
overall
everything
is
fixed
now
and
the
dashboard
should
be
updated
so
and
again,
yeah,
like
Phil,
said
thank
you
for
just
like
pointing
this
out
as
well.
D
Also,
finally,
to
add
props
to
Catalin
on
the
dmup
team
for
fixing
all
these
bugs,
like
very
last
minute,
for
example,
for
the
bug
that
Simon
just
mentioned.
He
had
to
make
another
service
just
to
download
the
data
decompress
it
first
before
and
putting
it
to
the
dashboard,
and
you
did
it
within
a
few
hours
so
or
else
it
wouldn't
have
been
fixed
and
yeah.
A
Other
thing,
I'd
like
to
just
say
thanks
to
is
like
just
the
flags
from
the
community.
A
few
months
ago,
we
were
kind
of
getting
our
feet
as
we
grew
as
a
program
and
colleagues
that
are
working
on
this
project
as
far
as
how
we're
communicating
with
each
other.
We
have
re-linked
the
standards
and
we'll
talk
about
this
when
we
get
into
the
trust
and
transparency,
but
just
is
a
call
out
as
far
as
how
we're
communicating
just
that
layer
of
business
professionalism
and
just
trying
to
keep
everything
above
board.
A
So
it's
been
really
helpful,
as
we
all
kind
of
adhere
to
this
and
kind
of
get
in
line
with
how
we're
structuring
that
communication.
So
just
want
to
say
thank
you
for
that,
as
far
as
how
we're
communicating
whether
it's
GitHub
and
slack
you've
kind
of
had
a
marked
improvement
in
that
and
we'll
just
continue
to
strive
on
that,
but
we've
linked
the
standards
as
far
as
what
we're
holding
we'll
talk
more
about
this,
for
how
trust
and
transparency
has
set
their
board
up
to
review
these
things.
A
So,
just
again,
thank
you
for
that
and
as
we
go
forward
and
communicate
so
notaries.
Fourth
round
notaries,
welcome
hello!
You
now
have
data
cap,
we'll
talk
about
that
going
forward
and
we
now
have
a
video,
so
major,
big
props
and
shout
outs
to
Phil
Phil
put
together,
like
a
very
short
succinct,
tldr
on
how
do
you
use
the
registry
to
view
the
applications
and
sign
an
approved
data
cap?
It's
posted
on
YouTube
in
the
Phil
plus
section
of
the
YouTube
channel
for
filecoin
the
links
here
in
the
thread,
and
essentially
what
this
will
walk.
A
You
through
are
step
by
step,
how
to
sign
into
the
registry
how
to
connect
your
Ledger,
how
to
make
sure
that
you're
connected
to
GitHub
how
to
search,
sort
and
see
all
the
applications
in
the
registry
and
then,
as
a
reminder,
you
can
also
log
into
GitHub
to
see
these
applications.
It's
a
good
source
of
Truth
to
kind
of
review
these
on
your
own.
That's
we're
going
to
be
leading
the
diligence
on
these
issues
and
we'll
talk
about
that
in
the
call
and,
if
you're
also
looking
for
this,
we'll
talk
more
about.
A
Where
do
you
find
an
open
application
if
there's
a
lot
of
open
things
and
how
to
see
that
and
go
forward
on
that?
So
again,
this
video
is
on
YouTube
The
Links
here
in
the
deck
which
is
posted
in
the
fill
plus
Channel.
If
you
have
any
questions
big
shout
out
to
Phil
for
not
only
having
a
great
video
but
succinct
but
putting
this
together
in
a
limited
time.
So
thank
you
for
that.
D
Very
quickly,
hey
guys,
so
this
just
came
out
hot
today
in
between
the
governance
call
in
the
morning
and
now
actually
so
Ezra
from
the
Keiko
team
managed
to
very
quickly
optimize
the
field
plus
registry.
So
that's
the
place
where
you
guys
go
in
and
approve
of
applications,
and
now
you
don't
need
to
wait
a
few
minutes
to
to
load
all
the
applications
now,
instead
of
that,
there's
like
a
few
seconds.
D
That's
because
we're
rendering
it
differently
and
as
you
can
see
in
this
GIF
The,
Fill
plus
registry
loads,
very
very
quickly,
so
big
props
to
Ezra
from
the
Keiko
team.
And
of
course,
let
me
know
if
there's
any
bugs,
because
as
with
every
launch
there,
there
may
be
bugs
to
this
and
yeah.
If
you
have
any
anything,
if
you
notice
anything
now,
please
reach
out
to
me
thanks.
D
Oh
and
yeah
I
think
that's
me
too,
so
I
just
wanna
to
acknowledge
and
bring
up
today
that
today's
the
fvm
launch
so
big
props.
If
anyone
is
here
from
the
fvm
team,
big
props
to
them
for
successfully
launching
fevm
to
the
mainnet
I
think
this
is
a
huge
opportunity
for
us
and
it
enables
it
opens
up
many
opportunities
for
the
falcoin
network
for
us
in
particular,
Phil,
plus
there
there's
opportunities
now
of
thinking
of
how
to
automate
the
allocation
of
of
data
cap.
D
There
will
be
many
more
things
on
that
and
coming
soon
right
now,
our
focus
is
to
make
sure
that
there
is
a
pathway
for
smart
contracts
on
the
fevm
to
get
data
cap.
This
is
in
the
works
and
also
just
with
any
upgrade.
There
will
be.
There
may
be
encountered
bugs
like
just
today
with
the
glyph
node
and
this
week
with
also
with
the
glyph
node.
D
A
A
So
the
first
question
came
through
from
a
first
round
or
excuse
me
fourth
round
notary,
that's
signing
for
the
first
time
and
their
question
was:
if
I
look
at
a
data
cap
request
and
I
see
that
in
another
notary
has
decided
to
pass
on
it
for
whatever
reason,
as
a
notary
am
I
prevented
or
blocked
from
moving
forward
with
that
application.
So
the
short
answer
is
no
you're.
Not
you
can
definitely
sign
for
whatever
diligence
you
want
to
provide
if
another
notary
has
decided
to
pass.
A
I
would
say
that
if
this
comes
up,
the
diligence
plan
would
fall
on
you,
so
there
might
be
times
where
a
notary
might
ask
somebody
to
fill
out
a
form,
let's
say,
and
that
data
applicant
did
not
fill
out
that
notaries
form.
Therefore,
that
notary
might
not
move
forward
with
going
forward.
That
doesn't
mean
that
you
can't
sign
it.
A
So
it
is
a
quick
answer
on
this
one
just
because
another
notary
has
passed
on
an
application
for
whatever
standards
review
or
whatever
reason
that
does
not
stop
you
from
performing
your
diligence
and
moving
forward
with
that
application.
As
you
see
fit.
The
second
was
hey
I'm,
a
new
notary
I've,
seen
some
notaries
that
are
in
kind
of
the
top
slots
that
use
some
type
of
a
form
to
do
their
diligence
rather
than
asking
the
same
questions
in
GitHub.
A
Is
that
form
process
allowed
and
the
answer
again
on
this
one
is
yes,
those
have
been
really
successful,
especially
with
some
notaries
that
are
doing
a
lot
of
these
application
reviews,
rather
than
post
these
in
GitHub
again
and
again,
they've
created
their
own
fillable
form
so
that
a
data
applicant
would
go
fill
out.
That
form
provide
the
necessary
information,
then
that
notary
could
review
that
information
and
then
ask
clarifying
questions
to
really
make
sure
that
that
diligence
is
completed.
A
A
So
if
you
are
doing
these
kind
of
steps,
make
sure
that
it
is
open
that
it's
auditable,
that
it
can
be
made
available
for
anybody
who
is
to
ask
these
questions
on
this
application
after
the
fact
If
this
just
goes
into
a
black
box
after
it's
filled
out,
it's
kind
of
the
same
as
an
offline
communication
and
email
or
slack.
So
just
be
mindful
of
that.
A
If
you
are
using
the
form
that
you're
having
some
way
to
share
the
results
of
that
or
share
your
reason
for
approving
that
data
cap
and
that
kind
of
came
down
to
one
of
the
third
questions
that
I
was
getting
it's.
How
do
you
ensure
that
your
diligence
is
transparent?
So
one
of
the
easiest
ways
to
do
this
is
a
new
notary
is
just
to
make
sure
that
you're
communicating
in
GitHub
it
doesn't
have
to
be
the
primary
way.
A
But
what
this
means
is
if
there
was
a
data
applicant
who
messaged
you
on
slack
and
they
say,
hi
I
know
you're
a
notary.
Can
you
please
take
a
look
at
my
application?
Maybe
some
of
the
communication
happens
in
slack
once
you
see
the
application
in
GitHub,
you
fill
out
any
information
and
then
sign
it
in
the
registry.
Make
sure
that
you
leave
a
comment
in
GitHub
about
your
slack
communication,
just
as
something
as
simple
as
hey.
A
A
So
if
you
do
have
these
offline
talks
in
slack
or
an
email
or
other
telegram
channels,
just
be
sure
that
when
you
are
entering
this
comment
in
you're
trying
to
be
as
transparent
as
possible
in
those
applications
just
to
prevent
any
kind
of
questions
later
that
come
down
the
line
and
the
fourth
most
common
question
that
came
through
is
hey
I'm,
a
new
notary.
How
do
I
know
which
applications
to
sign
where
to
find
them
and
how
to
communicate
with
those
applicants?
A
You
don't
know
if
you're
communicating
with
someone,
that's
not
checking
GitHub
regularly.
So
it's
a
new
notary,
that's
a
great
place
to
see
those
applications
then
link
back
to
the
GitHub
and
check
it
out.
Ask
any
diligence
questions
that
you
may
have
before
signing
to
move
forward
so
again
fill
Plus
application
is
a
great
way
to
find
those
applicants.
The
second
is,
if
you
just
check
GitHub
yourself,
you
could
sort
this
and
check
out
by
region
Geographic
by
industries
that
you
may
work
on
or
see
which
applications
were
newer,
older
and
then
sort
by
it.
A
So
you
can
always
go
straight
to
GitHub
to
review
the
applications
without
the
registry.
But
of
course
you
do
have
the
plus.fill.org
registry
website.
That's
your
tool
to
actually
see
these
applications,
it's
linked
to
your
Ledger
and
GitHub,
and
that's
where
you'll
actually
be
assigning
those
so
I'm
going
to
pause
and
for
any
notaries
that
are
on
the
call
that
might
have
any
other
questions
that
they
want
to
ask
and
we'll
just
take
any
time
for
this
onboarding.
Now
that
the
date
has
been
delivered
to
your
Ledger.
A
All
right
anything
changes
we'll
have
plenty
of
time
at
the
end
of
circle
back
to
any
topics
you
may
have.
So
if
you
were
a
notary,
you
completed
the
fourth
round
and
you
did
not
receive
access
to
the
LDN
V
3.1
or
the
new
multi-sig.
We
have
been
collecting
those
manually,
so
some
of
you
have
fallen
into
this
category
were
like
hey.
You
got
a
new
Ledger
since
we
rolled
out
A35.
What
we're
doing
is.
We've
collected
those
in
a
group
and
I
think,
probably
at
the
end
of
this
week
or
early
next.
A
What
we'll
do
is
manually.
Add
you
on
to
that
835..
So
again,
what
we
had
asked
for
on
the
last
call
was
that
if
you
weren't
on
that
issue,
just
to
leave
a
comment,
we're
collecting
all
those
and
we'll
manually
put,
everyone
has
completed
the
disclosures
and
verification.
So
thank
you,
I
think
we're
just
troubleshooting
a
few
that
had
issues
with
their
registry
verification
with
their
Ledger
or
those
of
you
that
received
a
new
Ledger
ID.
So
we'll
be
adding
you
in
a
couple
of
days.
Thank
you
again
for
commenting.
A
If
you
don't
see
your
name,
that's
the
best
way
to
go
on
there
and
then
everybody
else.
The
data
caps
are
live,
so
this
got
sent
I
think
last
week
or
the
week
before.
So
your
LDN
is
fold
up
with
data
cap.
It's
already
been
refreshed.
So
if
you
were
a
new
notary
on
this
call,
you
are
Off
to
the
Races.
You
have
data
cap
to
distribute.
A
You
have
the
video,
the
walkthrough,
the
FAQs,
and
if
you
have
any
questions
as
you
go
through
it
about
an
individual
application,
the
process
anything
whatsoever
feel
free
to
shoot
me
a
DM
or
even
better,
ask
in
the
private
notary
channel.
So
everybody
can
kind
of
see
and
learn
from
that.
Otherwise,
I'll
take
that
and
bake
these
into
future
call,
so
everyone
can
go
but
again,
notaries.
Thank
you
appreciate
it.
You
guys
are
all
set.
Let
me
know
if
we
could
help
you
in
any
way.
A
E
A
Quick,
we
had
this
identical
slide
two
weeks
ago,
we're
giving
it
one
final
voice
before
we
start
to
move
forward
on
these
one.
These
four
issues
were
relatively
low
spice.
They
were
essentially
looking
for
feedback
from
you
as
far
as
like
how
do
we
structure
the
staking
and
really
moving
forward
with
that?
We'll
talk
more
about
that
with
the
trust
and
transparency,
Auto
closing
applications
that
have
been
around
for
more
than
two
weeks.
A
What
is
the
data
cap
removal
process
and
how
should
trust
and
transparency
take
input
on
this
process,
and
then
how
do
we
have
a
code
of
conduct?
So
what's
nice
is
that
TNT
and
these
issues
are
actually
closing
a
lot
of
these
out.
So
we'll
talk
about
TNT
as
we
get
forward
on
the
call,
but
just
again
the
proposals
in
GitHub
are
a
great
way
for
you
to
make
your
voice
heard,
whether
you're
starting
a
new
application
or
just
commenting
on
it
and
for
those
notaries
that
have
selected
SLA,
threes,
fours
and
fives.
A
We're
looking
for
you
to
leave
comments,
feedback
and
input
and
really
help
be
the
thought
leaders
on
how
we
shape
this
road
map
and
these
projects
so
from
the
reminder
to
go
check
these
out
as
we
go
forward
on
it.
The
data
per
request
832.
This
has
been
open
for
a
few
weeks.
I
think
we're
soliciting
the
final
input
on
this
one,
and
this
really
boils
down
to
is:
if
we
have
a
data
set,
that
has
multiple
aspects
to
it.
A
Should
this
have
multiple
applications,
or
can
these
all
be
grouped
into
one
larger
application,
so
pretty
consistent
feedback
on
this
issue?
Just
as
a
friendly
reminder,
this
is
open
on
a32.
The
link
is
right
there
in
the
deck.
If
you
have
any
final
thoughts
before
we
move
to
close
this
out.
This
is
that
final
opportunity
and
we'll
have
time
at
the
end
of
this
call
and
discussion
for
832.
A
If
you
have
final
thoughts
on
if
this
was
not
a
good
idea,
as
far
as
structuring
the
LDN
application
separated
by
the
data
type
or
if
you
want
to
make
sure
that
this
is
something
that
you
agree
with,
giving
it
a
thumbs
up,
is
really
helpful
as
we
take
that
input
and
put
it
into
it
and
then
839
Phil
I
know
that
I
kind
of
stepped
on
you
in
the
morning.
Would
you
like
to
talk
about
this
one.
D
Yeah
sure
so
for
context,
this
application
relates
to
how
we're
moving
we're
good
in
the
future.
We're
going
to
move
away
from
using
comments
to
store
data
about
LDN
applications
into
using
Json
files
and
code
to
store
the
information
of
LDN
applications.
So,
instead
of
posting
a
comment
to
propose
or
posting
a
comment
to
approve
or
an
LDN
application
what's
happening
is
that
we
have
a
Json
file
and
we
have
a
pull
request
right
and
then,
in
that
pull
request.
D
D
So
after
I
posted
it
a
few
weeks
ago,
there
was
more
comments
on
this
application
from
our
engineers
at
Keiko,
we
are
figuring
out
what
how
the
specifics
of
the
Json
files
and
how
we're
going
to
store
this
LDN
application
data,
so
that
would
include
the
size
of
the
Json
file
itself.
Should
we
have
one
big
file
that
stores
all
the
LDN
applications,
or
should
we
have
multiple
small
files,
one
Json
file
for
each
LDN
application?
D
There
are
pros
and
cons
to
each
there's,
also
an
alternative
that
we
thought
of
which
is
kind
of
have
many
Json
files,
but
just
archive
the
old
ones
that
we
haven't
used,
haven't
used
or
interacted
with
in
two
weeks.
That's
also
one
possibility.
This
is
still
an
early
ideation
phase.
This
is
an
open
call
for
anyone
to
contribute
to
this
idea
or
comment
on
this
idea.
If
you
think
this
is
a
Way
Forward,
so
yeah
with
that,
if
anyone
has
any
comments,
please
let
us
know
in
839
yeah.
Thank
you.
E
A
All
right,
let's
take
a
look
at
the
working
groups,
so
KZ
was
on
the
morning
call
I'll
repost
the
link,
so
you
have
the
video
but
deep
Simon
Phil
before
I.
Go
on
with
this
feel
free
to
unmute.
Interrupt
me
if
you'd
like
to
talk
I'm
going
to
pause
for
two
seconds,
otherwise
I'll
just
regurgitate
what
Kevin
was
talking
about
in
the
morning.
A
All
right,
seeing
no
webcam
switch
on
I'll
carry
forward
on
this
one.
So
essentially,
what
the
e-fill
plus
program
is
looking
at,
as
you
know,
is
onboarding
that
private
data,
so
what
KZ
has
been
working
on
is
two
things.
The
first
is
like
a
survey
and
metrics
on
like
what
those
represent.
As
far
as
data
sets,
you
see
on
the
right,
what
they've
been
doing
is
taking
a
look
at
the
count
of
tickets
that
have
been
coming
in
and
trying
to
have
a
benchmark
on
what
the
majority
of
this
is.
A
So,
if
you
can
see
the
two
outliers
and
the
data
requests
that
they're
receiving
are
registered
and
we're
still
waiting
on
KYB,
then
knowing
the
business
and
then
the
client
onboarding
data
like
making
that
move
forward.
So
in
these
statistics
that
they're
pulling
there's
been
22
applications
that
have
come
through
since
October
a
lot
more
than
what
we
expected
this
program.
A
When
KZ
was
pulling
these
metrics,
he
was
trying
to
look
at
the
countries
that
break
down
for
these
requests,
and
that's
what
that
bottom
right
chart
is
telling
you
right
there.
So
you
can
see
of
these
requests
that
were
accepted
to
25
overall,
since
October,
the
majority
of
them
are
coming
from
the
United
States
China,
with
a
little
bit
of
outliers
around
Singapore
and
then
just
a
couple
spatterings
across
the
world.
A
So
what
Casey
is
going
to
be
doing
as
far
as
next
steps
is
he's,
putting
together
a
client
impact
survey,
so
essentially
soliciting
feedback
from
those
of
you
involved
in
Enterprise,
fill
plus
and
these
data
applications
that
are
submitting
and
they're
also
looking
at
how
they
can
streamline
the
tooling
to
make
that
TTD
as
quick
as
possible.
I
think
one
of
their
goals
is
48
hours.
A
There
was
a
request
to
see
where
can
I
find
the
graphs
and
the
metrics
that
have
been
kind
of
referenced
on
the
Civil
plus
I'll
re-share
that
again,
but
if
you
check
the
posts
that
I
put
in
Phil
Plus
in
the
morning,
you'll
see
there's
a
few
links
below
that.
One
of
them
goes
to
the
interplanetary
dashboard,
that's
where
you
can
see
the
graphs,
the
charts
and
the
breakdowns
on
how
this
data
is
collected.
Again,
if
you
have
any
questions
about
the
Enterprise
field,
plus
their
slack
has
all
the
links
and
information
as
it
goes.
A
Folder
trust
and
transparency
has
quite
a
bit
going
on
in
their
world
right
now
again,
open
call
Deep,
Simon
Phil.
If
you
want
to
unmute
and
kind
of
step
in
otherwise
I'll
I'll
try
to
do
RG
as
best
I
can
with
these.
So
the
first
was
looking
at
like
how
does
the
code
of
conduct
really
be
an
effective
use
on
a
trust
and
transparency,
so
they
put
out
a
proposal
eight
to
nine.
A
A
So
in
this
proposal
they
really
outlined
the
steps
for
what
will
be
taken
if
there
was
kind
of
a
reach
of
that
application
or
breach
in
that
disclosure
and
coming
forward
on
that,
and
that's
what
you
see
in
the
bottom
of
the
slide
called
out
a
bullet
point
number
one.
So
essentially,
if
there
isn't
any
kind
of
conduct
review
and
the
trust
and
transparency
user
Step
One
is
giving
like
a
very
public
warning,
we're
working
to
make
this
program
as
reputational
based
with
the
leaderboard,
and
this
really
plays
into
that.
A
So
if
there
is
any
kind
of
violation
on
behalf
of
the
storage
provider,
the
client,
the
notary
and
the
TMT
has
done
their
review
step.
One
is
to
issue
that
public
Mark
of
like
hey
here's,
your
warning.
Do
not
let
this
happen
again.
If
this
carries
forward
or
if
it's
warranted
in
it,
they
have
the
steps
outlined
which
up
to
and
including
blacklisting
of
the
client
address,
removal
of
the
notary
from
the
program
Banning
from
slack
Banning
from
the
GitHub
Banning
from
these
calls.
A
So
as
this
escalates
trust
and
transparency
has
really
tried
to
take
a
stepped
approach
to
it,
with
an
escalation
as
it
goes
forward.
So
since
this
impacts
all
of
us
on
the
call
what
I'll
do
is
pause
before
I
go
on
to
the
next
trust
in
transparency
and
see.
If
anybody
has
any
questions
about
this
code
of
conduct
or
any
thoughts
or
feedback
from
the
community.
A
A
We
referred
to
this
kind
of
like
a
dow,
we're
kind
of
looking
at
this
for
like
how
are
we
making
this
kyc
process
off
the
bat,
so
the
solution
is
not
having
like
a
check
that
goes
into
it,
but
looking
for
different
regions
to
kind
of
vendor
and
process
checks
in
the
community
and
with
that
express
interest
in
it.
So
again,
this
was
issue
that
came
forward.
This
has
been
open
for
a
few
weeks.
A
Trust
and
transparency
is
closing
this
out
this
833,
and
what
they're
essentially
asking
is
that
upfront
kyc
before
moving
forward
with
more
details.
This
one
was
a
lot
more
straightforward
than
the
kyc
for,
like
the
trust
and
transparency
code
of
conduct,
but
again
making
it
mandatory
for
that
process
linked
to
link
to
GitHub,
so
not
skipping
that
step
so
again,
if
anybody
has
any
thoughts
on
this
issue,
this
is
closed
out
officially.
A
A
This,
but
this
is
just
one
more
public
resource
of
data
that
will
soon
be
onboarded
through
this
accelerator
program
that
we'll
see,
and
in
the
morning
session
Cairo
talked
a
little
but
about
the
moon
landing
program
to
try
to
make
this
as
streamlined
as
possible
from
accelerating
that
data
to
get
it
onto
the
filecoin
network.
So
again
we
put
that
link
in
the
slack
channel
for
the
comment
earlier
this
morning
with
all
the
links
on
the
moonshot.
A
All
right
well
I'm,
going
to
open
up
one
line
of
questioning
and
it
has
to
do
with
time
zones.
So
here
in
California,
we
had
spring
forward
that
happened
on
Sunday,
taking
a
look
at
this
time.
I
wanted
to
see
if
this
time
zone
has
any
kind
of
conflict,
we're
probably
going
to
have
a
quick
survey
that
goes
off
in
the
field
plus
channel
for
notaries,
just
making
sure
that
that
time
stays
on
a
consistent
regular
basis,
so
you
can
dial
it
in
basis
around
your
workload.
A
All
right,
we'll
see
nothing
coming
through
I
think
we're
going
to
wrap
a
little
bit
earlier
tonight
again.
Does
anything
last
Alibis
feel
free
to
message
Us
in
slack?
Otherwise,
what
I'll
do
is
I'll
repost
these
on
the
YouTube
channel
and
share
that
link,
as
always
in
the
Phil
plus
public
Channel
wanted
to
thank
you
guys
for
all
dialing
in
Big,
Friendly,
happy
pie
dates
to
all
of
you
still
in
the
14th
time
zone
other
than
that
be
safe,
be
happy
and
we'll
see
you
signing
cheers
everyone.