►
From YouTube: KZG-Ceremony Breakout Call #7
Description
A
Hello,
everyone
welcome
to
the
seventh
kcg
ceremony.
Call
we
can
just
jump
right
into
it.
Does
anybody
have
an
update?
They
want
to
start
with
in
the
last
two
weeks,
or
I
guess
four
weeks,
because
I
was
gone
last
week
or
last
time
we
met
so
appreciate
the
notes
kev
for
putting
those
together.
That
was
really
helpful,
but
anybody
have
any
respects.
Maybe
we
could
start
with
the
audit.
That's
wrapping
up
this
week,
kev
if
you
want
to
give
a
perspective
on
where
that's
at
and
your
thoughts
on
everything.
B
Yeah
sure
so
the
audit
has
finished
and
they're
looking
to
write
up
the
report.
They
gave
a
list
of
things
that
they've
noted
in
the
implementation.
It's
mostly
just
cleaning
up
stuff
like
there's
unused
functions.
B
B
There
was
one
issue
which
they
said
that
we
should
fix,
or
we
focused
on,
which
is
where
I
assumed
that
the
srs
was
going
to
be
more
than
two.
So
for
us
this
is
the
case,
but
if
someone
else
tries
to
use
a
library
and
for
some
reason
they
don't
check,
the
srs
is
like
more
than
two
in
size.
B
They
would
get
a
like
a
panic,
so
we're
gonna
fix
that.
I
think
that
was
mainly
the
only
issue
that
came
up
for
the
audit
that
at
least
for
the
implementation.
B
There
were
some
other
notes
on
spec
consistency
with
the
code,
and
I
think
carl
is
gonna,
probably
modify
those
yeah
and
that's
mostly
it
from
the
audit.
So
it
was
looking
good
there's
like
nothing.
B
Nothing!
Nothing
like
big
came
up.
A
B
A
A
A
But
it
doesn't
seem
like
there's
anything
that
would
change
how
that
would
significantly
change
the
other
components
like
the
coordinator
or
the
interface
and
right.
B
Right
exactly
yeah,
there's
nothing
sort
of
major
changing
or
anything
like
this.
We
can
sort
of
just
continue
on
and
just
wait
for
them
to
publish
the
report
and
just
make
the
changes
that
they
requested.
A
Okay,
great
yeah,
then
we
can
move
on
to
the
other
components.
If
you
want
to
talk
about
the
coordinator
and
then
yeah
we
can
jeff
can
talk
about
what
he's
done
and
we'll
cycle
through
everybody.
B
B
It
seems
that
we
should
probably
just
use
a
session
id
like.
I
tried
to
implement
it
with
using
just
jwt
tokens
and
because
you
can't
revoke
them,
you
sort
of
get
into
these
clumsy
edge
cases
where
you
sort
of
just
doing
a
clumsier
version
of
sessions
so
yeah
this
morning,
I've
just
looked
into
try
to
use
sessions
instead
of
jwt
tokens
and
most
of
the
edge
cases
sort
of
just
disappear.
B
I
also
modified
the
way
that
we
do
the
cueing.
I
did
speak
to
jeff
about
it,
just
basically
on
the
coordinator,
not
needing
everybody
in
the
queue
to
ping.
So
we
only
care
about
like
k,
participants
being
online
at
a
specific
time
where
k
can
be
like
100,
for
example.
B
So
I
added
that
change
in
yeah.
That's
mostly
it
on
my
part.
I
can
go
into
any
other
if
you.
If
anyone
has
any
questions,
I
can
go
into
more
details,
yeah.
I
did
also
look
at
the
clay
which
I
thought
was
going
to
be
a
bit
difficult,
because
essentially
we
don't
really
want
people
to
copy
and
paste
if
they
want
to
use
the
client.
B
We
don't
want
them
to
copy
and
paste
the
link
into
the
browser,
but
this
is
actually
an
easy
issue
to
fix
where
the
client
will
just
pop
up
a
web
browser
with
a
sign
in
and
they
just
sign
in
and
then
it
sort
of
disappears
goes
back
to
the
client
and
then
they
just
continue
on
sort
of
contributing.
B
A
C
Already
yeah
that's
great,
so
that
was
the
issue
a
bit.
I
think
what
we
landed
on
is
if,
if
we
only
ask
people
to
to
check
in
when
they're
in
the
last
two
hours
of
the
of
the
queue
in
in
the
case
where
the
queue
is
longer
than
that,
is
that
what
we're
talking
about
kev.
B
Yeah
so
one
I
posted
in
the
public
kcg
ceremony,
so
the
coordinator
base
just
basically
says
I
only
care
about
the
first
100
or
thousand
people
in
the
queue,
and
we
only
need
them
to
ping.
I
also
took
off
the
exponent.
I
don't
know
if
it
was
exponential,
but
the
time
back
off,
so
each
person
just
pings
like
every
three
minutes,
which
is
roughly
the
time
the
upper
bound
that
we
give
each
participant.
B
So,
like
the
coordinator,
the
people
that
he's
watching
he
knows
that,
for
the
last,
at
least
for
the
last
three
minutes,
they've
been
online,
so
it's
like
simpler
to
implement
because
we
just
need
to
check
every
three
minutes
or
whatever
the
upper
bound
is
so
like
the
person
second,
in
line.
I
know
that
they
was
online
three
minutes
ago
at.
C
Least,
yep
yep,
okay,
there's
probably
something
there.
I
haven't
checked
out,
but
I
didn't
get
that
three
minutes.
But
that's
that's
okay.
Where
did
you
say
you
posted
that.
B
It
was
in
the
kzg
ceremony
public.
When
I
was
look.
I
think
I
posted
a
while
back
sorry
to
three
minutes.
It
was
just
the
upper
bound.
I
don't
actually
know
if
it's
three
minutes,
but
each
participant
has
x
amount
of
time
before
they're,
just
taking
that
they're
just
taking
too
long,
and
we
have
to
sort
of
push
them
out
of
the.
C
B
Yeah,
yes,
everybody
checks
in
for
this
amount
of
time,
for
example,
I
don't
know
if
it's
actually
three
minutes
so
yeah.
C
Okay,
go
gotcha
I'll
check
that
out
yeah
I
did.
I
did
make
sure
that
eight
hour
thing
was
in
the
spec,
not
the
area.
The
two-hour
thing
they're
only
checking
in
for
the
last
two
hours.
B
Yeah,
I
guess
I
couldn't
like
I,
I
guess
estimating
time
seemed
to
be
a
bit
erroneous,
because
I
did.
I
didn't
know
how
to
sort
of
estimate
two
hours
unless
we
sort
of
just
put
an
upper
bound
and
just
say
each
participant.
Three
minutes.
C
C
You
know
there'll
be
a
sort
of
normal
distribution,
so
the
average
will
be.
You
know
it
won't
be
too
far
away
from
the
average
contribution
time.
So
so
then
they
go
once
they
hit
the
two
hours.
They
start
going
into
a
more
frequent
cadence
and
it
gets
more
and
more
accurate.
The
closer
they
get
to
the
to
the
deadline
right.
B
C
B
B
C
B
Right,
I,
I
guess
how
how
do
you
determine
how
long
one
person
like
one
person
takes
like
if
I
pretend,
like
I
have
this
two
hour
parameter
and
somebody's
one
falven
is
like
the
one
thousand
person?
How
do
you
sort
of
roughly
estimate
how
long
like
it's
going
to
take
for
them
like
do.
C
To
be
even
more
more
likely
to
converge
converge
to
the
average,
so
you
know
as
long
as
we
get
within
a
couple
of
hours,
we're
good,
because
it's
it's
unlikely
to
be
that
far
away
from
that
from
the
estimate.
B
Maybe
I
should
ask
my
question
by
giving
what
I
think
the
answer
is,
so
I
think
you
take
the
last
100
participants
and
then
see
what
their
average
is
like
if
they
all
took
like
three
minutes,
then
the
average
is
three
minutes
and
then
that's
how
you
figure
out
how
long
everyone
else
is
going
to
take.
C
B
Yeah,
I
don't
know
they
both
seem
like
good
ideas.
You
can
take
the
average
or
you
can
just
set
a
parameter
for
like
200..
I
think
two
hours
would
probably
be
better.
B
B
I
was
going
to
say
something
time
would
be
better
but
yeah.
Maybe
we
should
take
the
offline
because
I
think.
C
B
Right,
my
assumption
was
that
they
would
sort
of
just
keep
pulling
the
coordinator
to
see
where
they
are
in
the
q
and
once
they
get
into
the
200
200
position,
then
they'd
need
to
start
picking
the
coordinator
to
check
in
so
anything
more
than
200.
You
just
don't
need
to
check
in
at
all.
B
C
B
B
But
yeah
yeah
it'd
be
good
to
discuss
the
pros
and
cons
of
both
of
them.
I
I
did
have
a
pro
for
the
time,
but
I
can't
remember
what
it
is
now
so
yeah
take
it
offline.
C
Sure
yeah,
the
other
thing
you
mentioned
session,
ids
okay.
So
so
we
just
we
just.
B
Right
exactly
yeah,
I
tried
to
do
the
jwt
tokens
way
and
well.
The
first
thing
is,
you
can't
have
a
j.
You
can't
have
a
jwt
that
lives
for
a
long
time,
but
it's
just
not
sort
of
recommended.
It's
usually
you
have
a
short-lived
jwt
and
a
long-lived
reef.
Sorry,
a
short-lived
access
token
and
a
long-lived
refresh
token,
but
then
you
sometimes
get
into
these
sort
of
edge
cases.
B
B
You
sort
of
have
these
edge
cases
where
the
coordinator
has
to
sort
of
store
this
state
to
say
that,
although
it
hasn't
expired,
you're
not
allowed
access
anymore,
and
this
this
is
like.
Basically,
you
might
as
well
just
do
sessions
and
just
have
a
coordinator
sort
of
state
so
yeah
I
was,
I
kept
bumping
into
these
sort
of
edge
cases
and
yeah
it
seems
session.
Ids
would
just
be
a
bit
easier
because
of
both
strategies.
C
C
And
takamiti,
if
you've
got
anything,
any
comment
on
that
that
you
can
think
of
then
let
us
know.
D
Okay,
I
will
yeah
take
a
look
into
the
tokens
yep.
C
B
C
B
C
B
Yeah
so
without
sessions
I
was
sort
of
taking
the
id
token.
Then
you
can
give
them
a
coordinator
access
token,
so
an
access
token
to
access
the
coordinator
api,
so
yeah.
So
I
just
swapped
it
out
to
give
them
a
session
id.
B
Instead
but
yeah
I
can
yeah.
If
nico
can
ping
me
on
the
public
channel
that'd
be
good
to
talk
about
that
yeah.
I
guess
the
off
stuff
was
easier
than
expected,
just
because
there's
like
third-party
services
that
just
basically
allow
you
to
click
buttons
and
just
do
ads
sign
in
with
ethereum,
add
github
and
stuff
like
this.
B
So
that
part
was
quite
easy.
I
was
expecting
us
to
sort
of
need
in
to
implement
the
sign
in
with
ethereum
stuff
from
scratch,
or
something
like
this.
A
B
Yeah,
it's
really
nice
that
they've
made
that
they've
made
that
and
yeah
you
don't
need
to.
I
think
they
just
extract
the
public
key
from
having
you
sign
some
sort
of
message.
So
yeah,
it's
really
nice
that
what
they've
done,
I
didn't
add
the
checks
that
are
needed.
B
As
I
understand
there's
a
check
for
ethereum
addresses,
non-smart
and
free
and
github
addresses.
I
think
I
can't
remember
what
a
github
track
was,
but
yeah
yeah.
So
it's
really
nice
that
the
the
api
that
they
have.
A
B
C
Yeah,
I
think
it
was
really
just
it
seemed
to
be
the
well
ethereum
was
a
natural
call
and
then
somewhere
someone
said
we
should
have
github
as
an
alternative
right.
That
was
like
the
second
most
natural
thing
to
go
to
there's,
no
reason
why
we
couldn't
expand
it
to
other
social
ideas
or
whatever
right
right,
but
it's
all
yeah
gotta
balance,
the
the
development
and
effort
and
everything.
But
I
know
with
author,
it's
quite
easy
to
just
add
a
new
yeah
new
source.
C
Isn't
it
yeah,
but
then
are
we
gonna
get
more
participants
by
doing
that
in
huge
numbers
and
what
sort
of
what
sort
of
you
know
each
one
we'd
have
to
devise
a
filter
to
make
to
make
sure
you
know
the
anti-civil
properties
are
still
being
maintained.
B
Yeah
yeah
exactly
yeah,
I
guess
if
I
was
to
say
we
like,
if
I
was
to
suggest
a
different
one
to
add,
probably
discord,
but
then
I
think
there's
a
lot
of
bots
on
this
chord.
I'm
not
really
sure
how
they
yeah,
I'm
not
really
sure
about
discord.
Actually.
A
A
Yeah
yeah
there's
some
people
interested
in
having
github
as
a
sign-in.
So
I
think
that's
fine.
C
Yeah
the
justification
was:
it
was
again
that
thing
that
we
called
you
cold
wallet
was
the
one
with
the
knots
greater
than
three,
so
people
might
be
reluctant
to
get
that
out
of
cold
storage,
and
so
they
want
to
use
the
github
instead,.
A
Question
do
we
have
any
way
of
if
somebody
uses
github
to
sign
in,
we
don't
get
any
information
about
their
ethereum
address?
Do
we.
B
A
A
C
A
C
C
B
I
think
we
can
also
just
tell
them
to
pass
in
an
ethereum
address,
along
with
the
authorization
code,
because
when
they
sign
in
with
github,
oh,
I
see
they
get
an
auth
code
and
then
the
off
code
gets
sent
to
the
coordination
server.
So
if
they
send
the
off
code
plus
an
ethereum
address,
we
can
just
sort
of
put
them
together
like
that.
Got
it
okay,.
E
B
Yeah,
I
don't
really
know
how
the
poep
stuff
is
gonna
work.
If
it's
another
sign
in
with
x,
then
it
might
be
to
do
what
jeff
said
and
just
have
them
sign
in
with
github
again.
But
I.
C
A
F
B
B
Then
you
can
sort
of
hide
all
of
the
http
cookies.
You
can
just
hide
them
from
the
front
end.
Is
that
what
you
guys
also
did.
C
E
B
B
B
B
B
C
I
think
I
think
we
removed
cookies
at
carl's
suggestion
he
doesn't.
C
B
Oh,
so,
if
we
are
avoiding
cookies
and
we
can't
do
sessions
because
the
session
the
cookies
are,
the
session
id
is
stored
inside
of
the
cookie.
C
Yeah
just
for
that
edge
case
where
they
have
to
sign
where
they
want
to
sign
in
sign
back
in
or
in
an
avoid
having
to
go
through
the
signing
signing
with
their
ethereum
address
again.
But
then
you
know,
I
think
kyle
did
have
a
good
point
about.
You
know
trying
to
avoid
appearances
of
of
saving
private
data.
B
Right
yeah,
so
if
we
can't
use
cookies,
then
I
think
we're
back
to
the
sort
of
stateless
approach.
B
C
A
B
Yeah,
so
we
can
still
do
the
session
way.
We
just
have
to
store
it
in
memory
instead,
and
so,
if
I
log
out
the
coordination
server
has
to
eventually
clean
up
my
session.
The
previous
session
that
I
had.
B
C
Oh
well,
so
as
long
as
you
as
long
as
you're,
not
away
for
longer
than
your
your
check-in
duration.
B
Will
not
stay
alive,
but
you
sort
of
have
to
remember
your
qid.
I
guess
which
is
the
session
id
in
this
case.
B
B
A
A
So
chiali
or
chali.
Actually
I
don't
know
how
to
pronounce
your
name
and
takamichi.
If
you
want
to
give
an
intro,
I
act
it's
good
to
meet
you
both
verbally,
but
if
you
want
to
just
I
don't
know
if
you
were
on
the
call
last
week,
but
talk
about
what
you've
been
working
on
and
I
keep
saying
last
week,
it
was
two
weeks
ago
just
give
a
quick
update
to
anything.
You've
been
working
on.
D
Should
I
go
first
sure
yeah
yeah,
hello,
I'm
takamiji
and
I've
joined
this
kcg
trusted
setup
team
from
this
week
actually,
and
I
am
working
on
a
front-end
client
for
the
mvp
of
the
dashboard
and
stuff
yeah
and
yeah.
I
now
dig
into
the
the
existing
code
base
and
try
to
catch
up
all
the
things
yeah
nice
meeting.
You
guys.
G
Hi
so
yeah,
I'm
charlie,
I
think
last
week
I
kind
of
tried
to
show
off
my
design
with
a
couple
of
engineers,
and
I
I
just
realized
I
need
to
make
an
mvp
version
and
I
have
a
kind
of
good
flow
for
now
for
the
mvp
and
it's
in
the
figma.
If
anyone
wanna
see
it,
I
have
a
question
now.
G
The
last
week
I
think
when
I
met
carl
and
cave,
we
were
talking
about
the
intro
p
and
we
say
we
need
to
have
input
for
user
to
to
enter
some
random
secret
in
the
design
I
put
just
eight
digit.
Is
that
okay
or
enough
should
we
have
more
string
or.
B
I
think
preferably
it
should
be
like
unlimited
and
then
we
can
sort
of
just
apply
some.
Maybe
hash
function
on
top
of
it
or
something
like
this.
G
Okay,
yeah
because
I'm
thinking
like
I
don't
have
a
bit
directive
for
to
the
user.
A
Yeah
yeah,
we
can
prompt
them
to
just
type
a
random
string.
We
can
make
it
pretty
explicit
and
like
they
don't
have
to
type
out
a
story
or
anything
about
themselves
personally,
but
we
can.
We
can
guide
them
along
the
path
of
generate
something
random.
That's
not
easy
to
remember
and
yeah.
Hopefully
they
don't
think
too
hard
about
making
something
random.
Okay,.
G
A
B
Yeah,
maybe
we
can
fit
it
into
these
calls.
I
don't
know
how
sort
of
how
long
it
would
take,
but
do
you
think
it's
possible
to
fit
it
into
these
calls,
or
would
it
need,
like
a
whole,
separate.
G
I
was,
I
was
thinking
that,
maybe
if
today
after
everyone's
discussion,
if
we
have
like
15
minutes,
I
can
add
this
work,
we'll
choose
some
design
thinking
and
then
maybe
we
can
do
async
for
now
and
if
we
kind
of
feel
like
okay
everybody's
talking
about
different
things,
maybe
you
can
schedule
a
like
refocus
design
review.
A
I'm
fine
with
that.
I
can.
I
can
stick
around.
I
know
jeff
is
heading
towards
bed,
but
I'm
happy
to
provide
feedback
today.
E
E
F
Yeah-
I
just
I'm
just
here
for
see
to
see
how
you
guys
building
a
good
ceremony,
so
I
prefer
to
listening
to
you.
A
One
thing
that
came
to
mind:
do
we
need
I'm
forgetting
the
name
of
the
library
but
a
while
back?
We
were
talking
about
the
hermes
team,
updating
a
library
that
we
needed
to
use.
Is
that
still
the
case
or
did
they
update
it
for
our
use
case
already.
C
C
See
I
should
probably
update
you
with
the
other
things
sure
go
ahead,
so
the
client
api,
I
think,
is-
is
kind
of
settled
now,
there's
obviously
a
couple
of
things
like
the
things
that
I
was
talking
about
earlier
with
curve
the
few
things
going
to
change,
but
basically
it's
been
it's
been
merged
into
this
into
the
specs.
You
can
find
it
in
the
in
the
kzg
ceremony,
repo
and
yeah.
Expecting
just
sort
of
minor
changes
from
here.
C
Nika
has
been
progressing
on
on
developing
that
api.
It's
going
pretty
well,
we've
got
a
server
under
construction.
We
have
to
have
have
to
be
releasing
something.
C
Well
it's
sometime
soon,
but
before
the
next
one
of
these
meetings
we
should
be
able
to
have
something
to
to
release
for
test
purposes
what
else
yeah
in
the
design
thing,
so
charlie
organized
meetings
on
the
design
function.
So
there
was
input
from
several
of
us
and
that
sort
of
spun
off
a
lot
of
other
discussions,
too,
some
of
which
we've
already
talked
about
yeah.
So
that's
my
update.
A
Great,
thank
you,
and
I
don't
know
if
it
was
talked
about,
or
at
least
broached,
but
the
the
goal
here
for
at
least
timelines
is
that
we'd
want
to
be
able
to
do
contributions
at
defcon.
So
that's
in
mid-october
that
gives
us
a
month
and
a
half
exactly
and
so
a
few
weeks
out
from
devcon
we'd
need
to
at
least
have
something
stable,
that
we
can
be
running
initial
contributions
through
to
make
sure
there
isn't
a
you
know
catastrophic
bug
or
something
that
we
missed.
That
requires
refactoring,
something
like
that.
A
So
if
we
work
backwards
from
defcon
a
couple
weeks
out
so
like
I'd,
say
the
third
in
three
weeks
third
week
of
september,
we
should
probably
have
something
that
we
are
putting
contributions
through
and
is
reasonably
stable.
A
Does
this
seem
feasible
to
everybody?
It's
it's
great
that
we
have
new
people
joining,
but
I
just
want
to
make
sure
that
there's
actually
enough
time
to
complete
this
or
whether
it's
even
feasible.
So
I'm
curious
what
other
people
think.
B
Could
you
clarify
on
the
front
end
part
so
for
the
for
the
dev
for
devcon?
I
guess
we
just
need
the
mvp
front
end
to
be
done,
which
is
really
simple.
I
guess
charlie
can
comment
on
that
part
for
the
coordination
server.
I
think
it
should
be
feasible.
B
B
So
yes,
on
the
front
end,
I
guess
charlie.
If
you
could
comment
on
that
jeff
on
the
coordination
server
is,
does
the
timeline
seem
feasible.
C
F
C
Hits
to
try
and
do
automated
battle
testing,
but
then
yeah
we
probably
need
some
real
life
testing
as
well,
but
yeah.
I
think
I
think
timeline's
very
clear.
B
E
B
B
C
B
Takamichi
said,
I
don't
know
if
people
can
see
the
recording
on
zoom,
I'm
mostly
writing
front-end
code
takamichi.
Do
you
think
that
the
mvp
will
be
for
the
front-end
will
be
done
by
the
times
listed?
D
I
think
the
base
the
basic
functionalities
can
be
in
time,
but
before
you
know,
we
need
some
time
to
like
actually
testing
it,
using
the
like
integration,
wise
testing,
like
3d
different
and
to
the
back
end
and
coordinator
so
yeah.
I
think
if
we
can
take
enough
time
to
test
it
and
maybe
fixing
the
you
know
issues
then
I
think
the
most
mostly.
E
B
B
And
so
I
guess,
as
long
as
the
front-end
ux
uses
the
same
structures
as
the
the
client
is
using,
then
it
should
be.
Okay,.
E
B
But
sorry
but
yeah,
maybe
there's
stuff
around
timeouts
and
stuff
like
this.
That
needs
to
be
expect.
B
B
Yeah,
like
the
tron,
I
think
the
transcript
should
ideally
be
a
part
of
it.
When
I
was
doing
the
the
coordination
server
for
the
most
part,
you
can
implement
it
without
even
by
abstracting
the
transcript.
So
it's
something
that
you
can
sort
of
just
put
in
last
minute,
so
I
don't
think
it
should
be
too
bad
to
add
it
in
jeff.
Could
you
could
you
like
confirm
that.
B
So
for
the
contributions
the
transcripts
stuff
would
be
included.
Sorry.
E
B
C
Yeah,
like
yeah
yeah,
the
things
that
are
not
included,
maybe
not
not
a
fancy
dashboard
and
yeah
yeah,
some
of
some
of
the
other
frills.
B
Right
so
the
mvp
will
basically
just
be
cutting
out
on
ui.
A
B
I
don't
think
it
is
that's.
G
I
think
more,
the
actual
design
file,
the
sigma
one
I
don't
have
like
a
condensed
leaves,
but
I
kind
of
feel
I
already
expressed
all
we
need
for
the
mvp
in
my
design.
So.
G
Yeah,
but
this
transcript
sorry,
this
transcript
thing
is
the.
Is
it
the
same
thing
as
the
hash
jeff.
C
Oh
yeah,
well,
a
hash
is
what
we
used
to
use.
I
think
we're
calling
it
like
a
public
key
in
the
specs.
So
that's
not
really
transcript.
Now.
E
C
C
C
Need
for
an
mvp
for
a
user
to
to
access,
I
mean
the
coordinator
will
be
keeping
that
the
transcript,
but
for
an
mvp,
what
do
we
really
need
to
use
it
to.
B
I
guess
it
depends
on
the
mvp
is
going
to
be
running
after
devcon
as
well,
and
a
lot
of
people
who
are
going
to
be
in
the
mvp.
Will
they
be
basically
a
small
group
of
people
if
the
mvp
is
just
for
devcon,
then
we'd
need
to
also
show
how
to
verify
it.
After,
like
it's
finished,
so
we
show
people
contributings,
then
it
stops,
and
then
we
sort
of
show
how
to
verify
your
contribution.
B
After
the
fact,
if
it's
only
a
closed
group
set
of
people,
then
I
think
the
queuing
mechanism
can
be
simplified
by
just
not
kicking
people
out,
because
we
just
know
where,
like
you're
right
there
like
yeah,
the
cueing
mechanism,
wouldn't
need
to
be
as
complicated,
because
we
don't
need
to
sort
of
account
for
bad
actors.
A
A
Ideally,
there
would
be
a
contribution
live
on
the
main
stage
during
one
of
the
kickoff
keynotes,
and
we
already
have
a
slot
scheduled
and
the
main
the
main
goal
for
why
we
want
to
do
this
is
to
just
get
people
aware
of
it,
give
a
very,
very
basic
intro
to
what
this
ceremony
is
and
that
people
can
expect
it
to
go,
live
for
public
contributions
in
november
and
december
roughly,
but
yeah
there
there
won't
be.
A
We
won't
like
be
accepting
contributions
from
the
broad,
broader
community
it'll,
just
be
like
a
single
it'd,
be
like
danny
or
aya
on
stage
walking
through
it
and
somehow
we'll
get
some
some
crowd
generated.
Randomness
into
this
interface
yeah,
mainly
mainly
just
an
educational
introduction
tool
about
like
what
this
thing
is,
why
it's
important,
probably
no
more
than
10
minutes,
10
or
15
minutes
I'd
say
but
yeah.
B
Right
yeah,
so
if
that's
the
case
for
the
mvp,
you
could
have
a
simpler
queue
and
mechanism,
because
you
can
just
assume
there's
not
going
to
be
any
sort
of
bad
participants.
People
trying
to
dos
it
or
anything.
A
B
Yeah
yeah,
I
think
you
can
create
like
a
username
and
password
and
give
it
out
to
people
like
just
spray
like
100
or
something
I
don't
know
how
many
clothes,
how
big
the
crow's
group
is.
But
I
think
you
can
do
something
like
that.
A
All
right
we're
in
the
last
five
minutes.
Does
anybody
else
have
anything
before
I
guess,
jeff
drops
off
or
other
people
leave.
C
Yeah,
I
might
stay
on
for
the
further
discussion,
but
there's
one
thing:
okay
came
up.
One
thing
that
came
up
was
my
discussion.
I
had
a
call
with
the
guys
from
cryptosat
one
of
the
founders
from
cryptoset
and
just
to
see,
if
you
know
the
kind
of
thing
we're
doing
is
the
kind
of
thing
they
do.
If
there's
some
kind
of
fit
seems
like
there
is
it's
basically,
the
reason
for
their
existence
is
doing
this
kind
of
thing.
C
C
So
I
guess
it
comes
down
to
you
know:
is
this
service
going
to
be
going
to
add
something
to
this
ceremony
and
is
it
worth
the
price
and
it's
I
guess
that
would
fall
into
our
like
crazy
ideas,
phase,
which
is
probably
you
know
towards
the
end
of
the
year
after
the
public
contributions,
but
the
the
the
suggestion
from
from
yan
who
is
the
founder
I
talked
to
there
was
get
get
start
the
discussion
early
because
it's
it
it
gets
a
bit
complicated
and
might
take
a
while
to
work
through
but
yeah.
C
Yeah,
well
I
can,
I
can,
you
know,
continue
that
discussion
with
them
or
we'll
have
it
have
it
move
on
somehow
but
yeah?
I
think
we
would
probably
need
to
first
get
an
idea.
Is
it
is
it
of
value
to
us?
Is
it
going
to
add
a
lot
of
security.
A
Well,
I
mean
like
each
of
these
mark
each
of
these
unique
ceremony
contributions
when
we're
doing
this,
like
you
said
the
the
crazy
ideas
or
the
when
we're
giving
out
grants
for
this
stuff.
I
guess
the
additional
marginal
security
isn't
like
that
significant,
but
it's
more.
These
are
situations
which
are
part
of
the
spectacle
and
part
of
the
the
larger
process.
So
I
mean
I'm
definitely
not
opposed
to
it.
It's
I'm
curious.
What
did
they
give
you?
Any
sort
of
price
range.
A
Yeah
that'd
be
the
first
thing,
I'd
be
curious
about,
but
yeah
we
can
still
start
talking
to
them
and
yeah.
It's
a
good
reminder.
C
Yeah
they
have,
they
have
satellites
they're
like
there's,
cubesats
and
they've
currently
got
one
up
in
space.
So
it's
a
totally
isolated
environment.
C
All
those
communications
up
are
public,
so
we
know
there's
no
sort
of
secrets
being
siphoned
off
or
something
and
there's
no
chance
of
any
side
channel
attacks,
and
that
kind
of
thing.
So
that's
that's.
The
selling
proposition.
B
B
A
All
right
is
there
anything
else
related
to
general
ceremony,
things
that
we
should
be
aware
of
over
the
next
few
weeks.
It
sounds
like
everybody's
on
a
pretty
good
path
towards
getting
an
mvp
interface
stood
up
with
all
the
the
back
end,
plugging
into
it.
So
that's
exciting,
and
if
there's
nothing
else,
we
can
move
into
the
design
review.
E
G
G
Okay,
if
you
guys
prefer
a
figma
file,
there's
a
link
that
just
paste
in
the
chat.
May
I
have
the
permission
to
share
screen.
A
Oh,
you
mean
just
yeah,
just
do
it
verbally.
I
don't
know
if
anybody's
on
mobile,
I
guess
that
might
be
harder.
Oh.
A
G
Okay,
I'm
just
kind
of
lost
my
oh,
my
things:
okay,
that's
fine!
So
after
last
week's
kind
of
quick
design
meeting,
I
removed
a
lot
of
things.
So
basically
just
a
single
page,
I'm
thinking-
and
we
talked
about
how
to
get
this
experience
and
there's
couple
ideas
surface,
like
invitation,
call
or
white
list,
or
sooner
we
talk
about
username
or
password.
G
So
I
think
we
kind
of
need
to
have
a
settlement
here,
because
we
need
to
kind
of
like
have
a
build,
a
logic
here
and
then,
when
user,
then,
on
this
landing
page,
for
example,
if
they
are
in
mobile,
basically
telling
them
this
experience
only
young
this
time
so
kind
of
like
not
continue
from
here
and
the
landing
page
you
can.
You
can
see
a
bit
similar
like
last
time
last
week,
I
do.
G
I
did
add
the
coordinator
online,
just
kind
of
status
here
and
some
kind
of
copy
need
to
refine
and
the
someone
like
not
nice,
so
have
two
people
in
the
queue
and
approach
cannot
give
a
user
how
long
they
have
to
wait
and
talk
about
how
impactful
about
this
ceremony
more
detail
in
here.
Instead
of
like
just
great
vibe
text
after
that
kind
of
showing
how
does
the
ceremony
work
and
kabul
affect
you?
So
this
is
the
landing
page,
so
imagine
user
either
sign
or
get
started.
G
G
So
saying
interior,
you
have
two
choice
or
you
open
the
guitar
alt
model.
Let's
say
today,
I'm
saying
with
metamask
and
then
I
need
to
sign
my
signature,
and
here
kinda
have
a
feedback
like
okay,
it's
it's
checking.
Once
user
sign,
we
will
kind
of
transit
to
this
page,
just
kind
of
inform
again
there's
two
people
in
the
queue
and
are
they
ready
to
to
contribute.
So
this
is
the
question
I
ask
sooner
once
they
click
this
ready
to
go.
G
They
will
get
into
this
screen
where
we
ask
that
kind
of
random
secret
string
or
whatever
we
want
to
call
it,
and
here
I
add
a
message
that
it's
very
important
to
be
online
for
a
certain
period
of
time
and
stuff
like
that
and
once
they
enter
the
secret
message
or
whatever
they
will
enter
queue.
So
when
they
click
this
enter
queue,
they
actually
go
back
to
this
home
page.
G
So
there
will
be
a
couple
of
css
animation.
I
imagine
and
takamiji
can
give
me
a
lot
that
don't
worry
so
here
we
kind
of
have
the
wallet
just
showing
here
and
user
is
in
the
queue.
So
this
can
act
as
a
progress
bar,
so
those
are
20
whatever.
G
Once
it's
two
users
turn,
then
this
will
kind
of
starting
initiative
contribution,
and
actually
this
will
also
transit
to
this
screen,
where
I've
kind
of
progressed
by
here
or
something
I'm
kind
of
thinking,
make
a
nice
animation
with
a
couple
ice
images
here,
but
I'm
not
sure
what
to
do
yet
start
and
then,
when
you
complete,
just
change
your
text
again
and
show
so
previously.
We
have
this
view.
The
hash,
and
sooner
we
talk
about
transcript,
is
this
word
supposed
to
happen
or.
B
Oh,
so
I
think
here
it's
the
public
key
that
they
used
to
contribute
to
the
ceremony,
so
the
randomness
that
they
generated
there's.
A
B
B
That's
what
it
used
to
be,
but
now
it's
basically
just
the
srs.
So
just
the
powers
of
tao.
B
B
B
B
Does
that
make
sense
so
like?
If
all
of
us
contributed,
I
contribute
with
a
transcript.
I
I
contribute
and
then
I
send
the
transcript
and
the
coordinator
basically
takes
one
thing
from
it
and
then
he
sends
maybe
trent
the
next
transcript
trent
contributes
and
modifies
it.
Then
he
sort
of
takes
something
from
there
as
well,
so
he's
sort
of
taking
the
summary
of
each
transcript,
except
for
the
last
one
yeah.
G
And
it's
this,
I
remember,
we
talked
about
the
ceremony
supposed
to
run
like
three
months
or
so
is
the
verification
supposed
to
be
the
end
of
ceremony
or
during
the
ceremony,
because
this
kind
of
just
mvp
just
to
have
let
people
aware
about
this.
G
It's
the
verify
needed
here,
because
if
we,
if
we
rewind
to
the
full
blown
version,
there
was
where
user
come
back
and
verify
and
then
claim
the
pull
up.
That's
kind
of
what
we
said
last
week
is
this
transcript
need
to
be
in
the
this
like
very
simple
mvp
version
or.
B
I
think
if
we're
gonna
show
the
the
the
ceremony
ending
at
devcon,
then
people
wanna
probably
see
like
how
do
we
verify
like?
How
do
we
do
the
verification
process
or
some
way
to
verify,
because
the
the
security
is
sort
of
not
just
based
on
someone
contributing
they
sort
of
have
to
verify
that
their
contribution
was
included?
B
G
So
so
this
this
give
me
a
bit
confusion
here.
The
the
mvp
we
doing
for
devcon
is
it
kind
of
just
a
prototype
version,
or
it's
going
to
be
continuously
used
to
become
an
official
ceremony.
C
Yeah
I
I
was
thinking
along
along
the
lines.
It
would
just
be
a
an
early
version
of
the
one
we
end
up
with.
G
Yeah
I
have
this
in
my
and
I
I
feel
this
transcript
does
demonstrate
the
importance
here
it
just
it
just
if
we
close
it
feel
like
just
this
is
gonna
end
up
as
a
demo,
and
then
I
don't
know
I
I
I'm
just
putting
my
two
server.
You
guys
tell
me
how
to
do
it.
B
Right,
I
guess,
if
you're
verifying
after
the
fact,
one
way
you
could
do
is
just
have
like
a
a
text
box
and
then
it
says,
search
for
this
person's
github
or
search
for
this
person's
ethereum
address,
and
then
that
just
makes
an
api
call
to
the
coordinator
and
then
the
coordinator
just
says
yeah.
This
is,
and
this
is
the
public
key
that
was
so.
This
person
contributed
here's
the
public
key.
B
It
was
at
this
position
and
then
that's
it
like,
for
example,
so
just
a
simple
text
box
that
you
can
sort
of
say
github
or
ethereum,
and
then
it
just
acts
as
the
coordinator.
Did
this
person
contribute
after
the
ceremonies
done
freddie
mvp,
I
think
for
the
front
end.
That
would
be
pretty.
B
B
Or
even
like,
even
here
where
it
says
contributing
completed,
I
guess
if
the
ceremony
is
done,
then
another
button
just
there
that
says
verify
contribution,
because
yeah
in
my
head,
I
feel,
like
the
verification
part,
is
also
quite
important.
Even
for
the
mvp.
B
It
doesn't
really
need
to
look
good.
In
my
opinion,
just
the
information
is
there
to
say
it's
been
verified
and.
G
So
how
about
we,
I
think
in
the
very
previous
version
we
have
a
kind
of
like
at
least
a
table
after
somebody
complete.
It's
is
this
just
good
enough
for
our
mvp
for
defcon.
B
I
guess
for
the
mvp,
this
is
sort
of
something
a
bit
different.
These
are
sort
of,
oh,
it
just
stores
the
transcripts.
I
guess
so.
C
Yeah,
but
in
these
screens
there
is
there's
a
hash
column
and
it
if
we
take
that
as
the
equivalent
of
the
public
key
like
in
in
the
screens
we're
looking
at
for
for
that
zika
one.
That
hash
would
be
the
thing
they're
looking
up
in
that
in
in
the
history
to
make
sure
it's
there
in
the
history,
and
it's
made
it
into
the
final
transcript,
so
our
equivalent
is
to
use
the
public
key
for
that
purpose.
C
I
mean
yeah,
I
think
it
wouldn't
wouldn't
be
a
table
like
this.
It's
just
a
like
a
separate
page
where
it
would
accept
it's
like
a
search
and
accept
either
a
github
idea
or
an
ethereum
address
and
search
for
my
for
that
for
that
identity
and
return
the
public
key
for
that
identity.
G
D
G
E
D
The
I
think
only
by
using
the
text
box
and
like
ask
to
the
coordinator
is
the
simplest
way
to
do
it
so
yeah.
Definitely
it's
visible.
E
G
G
And
so
I
I
guess
I
draw
back
the
question
to
you
guys
like
how
to
how
do
you
guys
point
to
the
the
gated
for
defcon
can
take
offline,
but
it's
up
to
you
guys.
I
need
to
mark
our
screen.
That's
all.
A
A
We
don't
have
to
have
username
and
passwords
that
we
preset
as
a
whitelist
or
anything
okay,
and
then
we
can
just
make
sure
that
we
have
the
ability
to
change
it.
A
B
I
guess
the
coordinator
could
just
store
a
bunch
of
codes,
like
probably
300,
like
200.
I
don't
know
how
many
people,
maybe
100,
is
good
enough.
G
Yeah,
so
those
are
the
mvp
design
I
have
for
now.
I
haven't.
I
haven't
finished
the
graphic
yet
but
kind
of
like
those
type
of
library,
simple
lines
and
yeah.
I
haven't
finished
folding.
It.
A
G
A
I
was
telling
you,
I
think,
it's
great
to
just
be
able
to
see
each
of
the
steps.
It's
really
helpful
for
me
and
then
I'm
going
to
help
you
work
through
what
the
languages
are
or
how
what
the
connection
between
each
step
in
the
processes
and
how
we
write
a
nice
story.
G
Yeah
appreciate
it.
Thank
you
any
other
comment
or
fema.
A
I
guess
at
the
end
we
will
need
some
language
it
about
the
pull-up
of
like
people
will
be
like.
Oh,
what
do
I
do
when
do?
I
come
back
claim
this,
so
we
will
need
some
language
there
and
then
also
it
might
be
nice
to
have
a
twitter,
a
prompt
to
share
on
twitter
like
share
your
contribution
or
invite
others
to
contribute,
and
then
it
can
be
like
a
pre-filled,
pre-filled
tweet
or
something.
G
A
Yeah
yeah
this
yeah
for,
like
the
public
contribution
we'd,
want
to
have
some
sort
of
call
to
action
at
the
end,
just
to
make
sure
the
meme
is
getting
spread
properly
right.
G
A
Yeah
I
mean
the
general
idea.
Is
there?
I
guess
we
wouldn't
have
an
attestation
exactly
like
some
things
are
going
to
be
different,
but
for
people
who
are
signing
him
with
ethereum
but
yeah.
Something
like
this
would
be
perfect.
E
A
A
Okay,
there's
a
question
from
ahmet:
is
the
transcript
a
set
of
messages
that
are
sent
between
the
participating
coordinator?
No,
the
transcript
would
be
the
output
of
the
entire
ceremony.
A
The
transcript
is
sort
of
a
summary
of
everyone's
linked
randomness
or
the
output
of
their
contribution
that
anybody
can
verify
after
the
fact
is
that
correct
somebody,
somebody
double
check
my
plan.
B
Yeah,
I
think
I
think,
that's
correct.
I
also
think
it
is
a
set
of
messages,
so
I
think
it's
both
yeah.
So
I
think
it's
also
a
set
of
messages.
It's
just
one
message.
I
guess
you
can
think
of
it
as
but
may
yeah.
I
think
we
do
have.
A
Okay,
I
thought
he
they
were
asking
about
like
the
back
and
forth
between
an
individual
participant
and
a
coordinator
or
something
but
yeah.
I
guess
you,
if
you
look
at
it
a
different
way.
It
might
also
be
yeah
yeah.
It
could
be
both
things
depending
on
how
you
look
at
it.
B
A
A
Oh
so
less
less
accessible
language,
yeah.
A
If
there's
nothing
else,
we
can
wrap
up
here
thanks
everybody
for
sticking
around
another
30
minutes
to
help
with
the
design,
review
and
charlie
for
presenting.
I
guess.
Oh
one
thing
real
quick
before
we
wrap
up
is
just
like
what
are
people
going
to
be
working
on
the
next
two
weeks
I
can
start
given
given
this?
Is
you
know,
sort
of
the
crunch
time
where
we've
got
a
defined
milestone?
We
want
to
get
to
presenting
the
mvp
at
devcon
and
then
working
back
from
it.
This
is
sort
of
like
we're.
A
We
had
maybe
a
little
bit
more
time,
flexibility
early
when
this
project
started
over
the
last
few
months,
but
now
we're
getting
into
the
area
where
we
really
need
to
not
that
the
work
hasn't
been
getting
done,
but
just
be
mindful
that,
like
the
deadline
is
approaching-
and
we've
just
got
to
be
conscious
of
how
quickly
we're
getting
things
done,
so
I'm
going
to
be
helping
charlie
with
the
the
language
and
some
of
the
graphics
just
helping
to
shape
that
a
little
bit
better
on
the
interface
there's
some
payment
stuff
for
the
first
audit.
A
That
needs
to
be
wrapped
up
and
I
will
also
be
making
sure
we're
better
prepared
for
the
coordinator
audit
with
sigma
prime,
which
is
scheduled
to
start
in
october.
A
Those
are
the
main
things
I'll
be
working
on
making
sure
where
we
have
a
good
idea
of
what's
going
to
happen
at
defcon,
and
I
think
that
might
be
it
for
me.
But
that'll
be
the
few
things
I'm
working
on
over
the
next
few
weeks
before
the
next
call.
C
A
C
B
B
Probably
after
that,
I
might
start
going
on
to
the
command
line
interface,
to
interact
with
the
coordinator
right
now,
we're
sort
of
focused
on
the
website
being
a
client,
but
I
think
we
also
probably
want
a
cly
cli
command
line
interface
to
be
to
be
able
to
interact
with
the
coordinator
as
well
yeah.
I
figured
out
how
to
do
it,
but
I
just
haven't
implemented
sort
of
anything
regarding
that.
B
Just
yet
yeah
and
I'd
probably
just
be
speaking
with
jeff,
and
I
guess
nico
about
this
specs,
some
more
mostly
in
the
public
channel.
Just
so
everyone
can
chip
in
yeah.
That's
it.
A
Great
yeah,
the
cli,
is
something
that
I
would
have
forgotten
about
so
good
good,
remembering
that
there
are
definitely
going
to
be
some
contributors
who
want
to
not
use
the
interface
they
want
to
do
it
on
their
own.
You
know,
especially
for
the
the
special
contribution
period.
I
think
people
will
be
interested
in
that
very
much.
Then.
G
Yeah,
so
I
will
continue
on
the
mvp
and
fill
out
the
imagery
and
the
cable
iteration
there.
They
were
and
supported.
D
I
will
be
mostly
working
on
the
coding
of
the
front-end
stuff
and
mostly,
I
think,
we'll
talk
into
nico
and
shelly
about
the
designs
and
maybe
jeff
about.
E
D
Yeah,
so
that
we
can
show
the
fancy
demo
mvp
to
buy
that
at
the
dev
con
yeah.
A
It
that's
that's
good
to
know
all
right.
Thank
you,
everybody
for
coming.
Those
good
updates-
and
I
think,
really
clear
picture
of
what's
gonna
happen
over
the
next
two
weeks,
so
I
think
that's
it
and
yeah
everyone
will
be
in
the
discord
channel
so
feel
free
to
drop
any
questions
there.
If
people
are
unsure
about
a
specific
thing
and
by
discord
I
mean
the
the
ether
and
the
discord
it's
where
the
public
channel
is,
we
want
to
make
sure
we're
putting
messages
there.