►
From YouTube: KZG-Ceremony Breakout Call #2
Description
A
A
Let's
see
where
do
we
want
to
let's
work
backwards
in
time
here,
so
the
intent
is
to
have
this
ready
in
advance
of
shanghai
shanghai
is
the
next
upgrade
after
the
merge.
You
know,
let's
say
q2,
of
2023
optimistically,
depending
on
what
goes
into
it.
So
I
mean
that's
more
than
enough
time
to
complete
a
ceremony
and
actually.
A
You
know
make
sure
that
we
run
it.
Well,
I'm
sorry,
I'm
distracted
for
a
second
there's
some
noise
in
the
background,
so
yeah
working
backwards
from
shanghai.
We
have
more
than
enough
time.
Oh
right,
so
there's
audits
that
we
have
slotted
in
for
august
and
october,
one
with
sigma
prime
sigma
prime
is
in
october
around
defcon
and
the
other
is
in
august
with
sec
bit
and
those
are
also.
Obviously,
these
are
kind
of
key
milestones
that
we
have
to
hit.
A
B
B
So
I
think
that
would
be
a
good
timeline
to
sort
of
aim
for
in
terms
of
having
a
fully
audited
and
robust
set
of
implementations.
For
all
of
this,
and
so
the
ceremony
going
flat
out
three
months
is,
I
think,
the
minimum
I'd
like
to
allow
for
for
general
participation,
particularly
given
that
some
of
this
would
be
over
the
the
end
of
your
holiday
period.
B
So
I
think
that
still
gives
us
enough
time
that
no
one
can
really
complain
that
they
weren't
they
weren't
included
or
were
unable
to
participate,
and
then
this
this
this
lines
up
nicely
with
the
the
august
audits,
which
would
be
sort
of,
like
so
sorry,
audits.
And
if,
if
we
we
aim
to
have
everything
ready
by
the
start
of
october,
then
we
have
devcon
audits
in
the
first
three
weeks
of
october,
and
then
we
use
the
last
week
to
implement
any
changes
suggested
in
the
audits.
B
So
I
think
that's
sort
of
a
a
good
rough
timeline
for,
and
that
would
be
the
sigma
prime
audit.
The.
What
what
my
current
thought
process
is
here
is
to
try,
have
try,
have
the
two
audits
target
slightly
different
aspects
of
the
protocol,
so
using
the
the
first,
the
first
orbit
or
audit
in
august
as
an
audit
of
the
sort
of
stuff
happening
on
the
crypto
side
of
things?
B
Make
sure
that,
like
the
idea
being
that
we
have
this
like
isolated,
crypto
api,
that
would
be
used
by
the
the
coordinator
software
and
the
sort
of
default
implementation
of
a
participant?
And
we
check
that,
like
sort
of
sanity
check,
that
this
pass?
Does
all
the
things
in
the
specifications
and
that
basically,
the
the
the
crypto
stuff
is
compliant
with
with
with
the
specs
I've
written
and
then
the
second
order.
B
In
october,
we
use
to
target
the
the
coordinator
to
itself
and
make
sure
that
it's
not
doing
things
like
censoring,
and
then
there
aren't
any
obvious
deadlocks
and
and
those
kinds
of
things,
and
we
just
assumed
at
that
point
that
the
the
crypto
has
been
correctly
audited.
So
this
is
sort
of
my
what
I
have
roughly
in
my
head
right
now
for
for
these
targets.
A
Yeah
that
makes
sense-
and
I
think
probably
we
should
just
write
it
down
somewhere
and
adjust
if
anything
does
change
it
in
that.
In
that
timeline,
I
was
gonna
say
when
you
first
said
you
know
three
months
to
run
it.
My
first
instinct
was
like
wow,
that's
incredibly
long
for
given,
given
what
I've
read
about
and
the
projects
that
I've
participated
in
three
months
is
like
an
eternity
it
feels
like,
but
on
the
other
hand
it
you
know
this
is
a
pretty
significant
change.
A
I
don't
think
ethereum
has
had
a
trusted
setup
like
this
put
into
the
base
layer
so
yeah.
I
guess
we
definitely
do
want
to
give
enough
time,
like
you
said,
make
sure
people
have-
or
at
least
the
developers
have
can
point
to
this
and
saying
look.
We
gave
a
pretty
significant
amount
of
time.
I
think
when
I
was
doing
research.
You
know
ceremonies
typically
ran
for
like
two
weeks
to
a
month.
B
Yeah,
so
I
I
agree
agree
with
all
of
those
things
I
think
what's
what's
what's
different
here
is
I'd
like
for
just
many
more
participants,
and
I
like
I'd
like
it
to
be
such
that
people
can
forget
that
we're
doing
this
and
then
sort
of
be
reminded
and
still
being
able
to
come
in
later
and
participate.
I
don't
want
it
to
be
like
oh,
I
must
I
miss
this
this
particular
month
or
these
two
weeks.
B
I
want
it
just
to
be
basically
on
stress
for
everyone,
but
also
gives
us
more
time
to
sort
of
include
and
help
sell
the
narrative
to
to
more
people.
So
I
think
that's
that's
a
better
way
of
doing
it.
Also,
if
our
cues
queues
start
to
get
long,
then
people
can
come
back
at
a
later
time
if
that
works
better
for
them.
B
As
possible
is
fine,
and
in
fact
I
would
say
we
should
even
start
running
it
before
we
finish
all
the
orders,
particularly
of
the
sort
of
the
the
coordinator
audits.
We
can
start
running
things
before
before
that
on
a
smaller
scale,
not
the
get
anyone
to
get
involved,
but
like
a
bit
of
stress,
testing
it
and
that
kind
of
thing
internally
and
start
getting
our
participation
going
positively
a
month
a
month
before,
before
we
open
it
to
the
public.
A
It's
all
good,
all
right,
okay,
so
then
we
can
just
move
into
general
updates
about
the
rest
of
the
things
listed
there.
I
guess
we
can
start
with
kev
if
you
have
any
changes
from
two
weeks
ago,
with
the
the
rust
implementation
or
you're
kind
of
sitting,
waiting
for
waiting
for
some
other
things
to
be
concluded.
What
what's
up
on
your
end.
D
D
B
I've
had
some
discussions
with
other
cryptographers
who,
just
like
they
had
an
idea
of
how
this
would
go
just
based
on
what
they've
seen
in
the
past
and
that's
slightly
different
to
what
we're
doing
here.
So
I
think
we
should.
We
should
make
some
effort
to
explain
that,
so
that
should
be
going
up
soon
and
then
the
other
thing
is
the
checks
for
a
secret
being
common
across
all
of
the
the
the
sub-ceremonies,
the
the
the
uniqueness
of
pub
key,
I'm
going
to
remove
those
checks.
E
B
E
E
D
B
B
E
D
You
sort
of
just
need,
like
the
witness,
but
carl,
I
think
when
I
look
at
the
specs.
It
seems
that
it
does
sort
of
imply
that
we
need
the
old
powers
because
it
says
ceremony,
which
is
a
list
of
transcripts
and
the
transcripts
holds
like
a
list
of
g1
and
g2
powers
in
the
powers
of
term
that
that's
not
the
transcripts.
That
I
mean.
E
B
E
B
A
Yeah
one
thing
we'll
definitely
want
to
do
is
make
sure
that
is
part
of
the
website
or
the
interface
that
there's
also
a
a
clear
path
for
people
to
explore,
verifying
the
transcript
and
maybe
like
a
couple
different
levels
of
explanation
for
what
it
is
and
how
people
can
actually
verify
it
themselves,
but
we're
a
little
early
for
getting
into
the
ui
stuff.
I
guess.
A
C
A
A
Got
it
carl
another
thing
which
came
to
mind
about
the
ceremony
is,
I
think
we
should
probably
have
some,
like
you
said,
we'll
be
doing
testing
iteratively,
as
you
know,
before
a
big
public
launch
would
be.
Can
we
coordinate
any
of
this
around
defcon
and
have
maybe
like
some
some
space
on
the
main
stage
to
introduce
the
concept,
and
I
guess
formally
kick
things
off,
and
maybe
even
one
thing
that
would
be
really
cool
is
to
include
some
sort
of.
A
If,
if
not,
I
guess,
what
would
be
really
awesome
is
as
a
way
to
incorporate
some
randomness
from
the
crowd
either
like
a
photo.
I
I
don't
know
if
I
guess
the
interface
would
have
to
support
this.
I've
seen
some
setups
where
you
do
like
mashing
of
a
keyboard,
and
then
that
gets
that's
your
your
source
of
randomness.
B
B
Do
that
and
yeah
could
definitely
drop
some
some
some
some
exciting
things.
I
think
we
can
have
some
some
discussions
offline
to
try
to
decide
exactly
how
we
do
this
to
get
as
much
like
crowd,
involvement
excitement
as
as
possible,
but
I
think
that'd
be
a
good
starting
point
for
for
all
these
things
at
that
point.
Hopefully,
a
few
of
us
have
participated
already
in
the
background,
and
maybe
we
can
collect
some
some
people's
participation
already
at
devcon,
while
they're
there.
C
A
Yeah,
I
just
remembered
that
I
mean
I
don't
wanna
we're
still
super
early,
but
I'm
already
like
thinking
ahead
to
these
these
exciting
bits
where
we
actually
start
getting
contributions.
But
I
I
know
defcon
isn't
having
sponsors
this
year
and
instead
they're
having
like
community
project
booths
and
it
might
be
really
cool
just
to
have
a
booth
throughout
the
whole
week
where
people
can
come
and
do
contributions
and
learn
about
it.
But
yeah
I'm
getting
ahead
of
myself
here.
B
A
A
All
right.
We
kind
of
jumped
around
the
agenda
a
little
bit,
but
we
can
does
anybody
else
have
any
updates
have
already
talked.
I
guess
one
thing,
that's
sort
of
near
in
time
would
be
the
any
any
updates
on
the
circum
side
of
things.
I
know
I
think
carl
you
mentioned
that
someone
had
started
talking
to
jordy
and
they
were
able
to
contribute
to
this.
B
Yeah
a
little
bit
a
little
bit
of
discussion
there,
the
that's,
that's
mostly
just
needing
a
a
crypto
library
for
for
all
jeff
stuff
to
plug
into.
We
had
some
discussions
earlier
about
exactly
what
that
looks
like
right
now.
The
snook
js
stuff
is
just
too
slow.
Well,
I
mean
it's
fine.
We
can
make
it
work,
but
it's
it's
slow
than
expected
as
and
it
takes
multiple
minutes
for
just
for
participation
and
a
like
decent
multi-threaded
wars
and
blob
should
be,
should
be
fair,
but
quicker
than
that.
C
Yeah,
so
I
I've
booked
case
code
and
put
in
the
wasm
build
code
and
got
it
got
a
building
to
wasm
and
but
only
with
a
single
threaded
model
haven't
got
multi-threaded
it's
compiling,
but
it's
it's
not
working
in
the
browser,
but
I'm
sure
that
can
that
can
be
got
going
and
even
with
single
threaded.
It's
like
one
minute
muslim.
B
Yeah,
I
think
we
should.
We
should
definitely
do
some
some.
Some
benchmarking
of
the
various
libraries
what's
different
in
comparison
to
most
of
the
benchmarks
that
already
exist
is
that
most
of
them
are
favoring
like
how
long
it
takes
to
do
pairings
and
what
we
care
about
is
like
scalar
multiplication.
B
B
B
I
guess
that
the
other
thing
we
we
care
about
in
these
these
implementations
is
how
quick
they
can
do.
The
the
subgroup
checks
right
and
there
could
be
large
variants
here,
based
on
what
the
implementation
looks
like
on
the
background,
the
back
end,
whether
it's
the
naive
for
more
complicated
ones-
and
I
don't
know
what
what
the
existing
libraries
use.
D
D
D
D
D
B
D
B
D
D
D
D
B
D
F
B
D
A
All
right,
we,
I
guess
we're
coming
close
to
the
end
of
the
hour
things
we
haven't
touched
on
yet
are
the
the
non-spec
stuff
really
so
I
guess
the
queuing
identification
stuff
that
jeff
you've
been
working
on.
Is
there
any
update
on
that
end
or
you're?
I
guess
you
also
mentioned
you
were
working
on
some
other
stuff
over
the
past
week.
Anything
you
want
to
update
with
regard
to
that.
Yes,.
C
Yeah
so
queuing,
I
think
we've
we've
settled
on
a
simpler
queuing
mechanism
in
talking
about
it
with
carl
yeah.
We
we've
found
some
simplifications.
It
should
be
a
very
simple
just
just
simple
queue.
None
of
these
time
slots
or
anything
because
we're
getting
because
the
contributions
going
to
be
pretty
quick,
so
we
can
it'll,
we
can
get
through
participants
pretty
quickly.
C
Can
you
give
me
a
question
quick
summary
of
like
what
the
differences
are?
Oh,
so
the
document
as
it
stands
has
time
slots
being
allocated
and
then
participant
would
request
the
time
slot
and
that
that
they'd
come
back
at
that
time
and
then
would
in
advance
of
it
and
be
ready
for
their
contribution.
C
C
C
So
if
anyone
has
any
thoughts
on
that,
we
like
to
hear
them,
it
means
that
someone
could
participate
with
their
ethereum
address
and
then
sign
on
with
with
their
github
and
do
another
contributions
but,
and
they
end
up
doing
you
know
a
small
number
of
contributions.
I
don't
think
that's
a
serious
problem.
C
B
High
nonsense,
yeah,
so
we're
not
like
we're
not
trying
to
have
this
perfect,
simple
resistance
system
here.
It's
just
that
we
can't
be
dust,
it's
the
goal.
So
if
you,
if,
if
like
someone
wants
to
put
in
the
effort
to
figure
out
a
way
to
participate
five
times,
then
that's
okay
as
long
as
like
not
everyone
does
that
and
you
can't
like
spin
up
bots
to
do
it,
then
that's
all
right,
the
other.
B
The
other
thing
I
think
it's
the
reason
I
think
it's
important
to
do.
Github
is
I'd
like
to
be
able
to
include
community
members
that
aren't
a
part
of
that
they
don't
use
ethereum
right
now
or
don't
have
ethereum
accounts,
and
I
think
it's
it's
sort
of
easier
to
extend
beyond
like
out
that
our
direct
vicinity
using
github
or
something
similar
in
addition
to
all
the
ethereum
stuff,
how
many.
B
A
E
A
E
A
B
Yeah
I
mean
assuming
that
we're
not
running
into
bottlenecks
with
like
length
of
cues
and
participation
time,
then
absolutely
I
mean.
Hopefully
your
one
contribution
is
sufficient.
You
shouldn't
need
to
contribute
more
than
one
times,
but
if
you
have
any
reason
to
doubt
the
security
of
your
setup,
then
I'd
welcome
a
second
participle
like
a
second
entry
from
someone.
E
A
B
E
A
A
This
is
like
we're
early
we're
very
early
on
this,
but
I'll
make
sure
that
they're
they
reserve
us
a
slot
at
the
beginning
of
defcon
and
start
to
talk
about
having
a
booth
where
we
can
explain
what
this
thing
is
over
the
course
of
devcon
and
maybe
get
some
contributions
from
people
that'll,
be
something
that
I
make
sure
to
do
over
the
next
week,
or
I
guess
it'll
be
two
weeks.
Let's
call
us
every
two
weeks,
carl.
A
What
are
you
gonna
be
up
to
I'd
like
to
if
we
can
start
to
put
the
the
spec
out
there
a
little
bit
more?
If
you
don't
think
we're
ready,
that's
fine,
but
I
think
we
should
start
moving
towards
that
of
like
publicizing
it
and
sending
it
to
some
of
the
other
teams
that
have
done
trusted
setups
to
get
start
to
get
their
eyes
on
it.
Unless
you've
already
done
this.
B
Yeah
sure
so
I
might
start
on
a
publish
like
timelines,
so
that
everyone's
on
the
same
page
on
what's
been
done
when
the
stuff
I
was
discussing
at
the
beginning
on
the
spec
side,
the
one
or
two
little
cleanups,
I
want
to
do
let's
say
today
tomorrow
and
over
the
weekend,
so
on
monday
we
can
start
publicizing
things.
That's
that
sounds
good
to
me.
I
want
to
write
some
of
the
clarifying
documentation.
B
But
if,
if
we
end
up
with
long
queues,
that
might
might
not
be
so
so
friendly
and
it
might
make
it
worse
like
having
to,
I
was
trying
to
get
entirely
a
restful
api.
But
that
might
make
things
worse.
So
jeff
jeff
once
was
proposing
to
go
with
amqp,
which
I'm
not
familiar
enough
with
the
comments.
But
that's
one
of
the
things
I'll
look
into
over
the
next
few
days.
B
E
E
You
have
like
this
code
coverage
built
into
the
test
cases,
so
we
can
easily
figure
out
which
which
code
is
tested
and
which
code
is
not
tested,
at
least
in
our
code,
not
in
the
libraries
but
yeah.
So
we
can
create
some
test
cases
where,
like
I
don't
know,
the
subgroup
check
checks
fail,
or
I
don't
know
something
with
with
this
happening,
and
I
would
like
to
create
some
of
those.
B
For
the
that'd
be
cool
and
I'd
like
to
then
like
murder,
like
any
cool
test
cases,
you
come
up
with
I'd
like
to
have
in
a
fold
on
on
our
repo.
Unfortunately,
we
don't
like
for
the
the
subgroup
check
in
particular,
I
don't
think
we,
we
know
any
low
order
or
non-prime
group
elements
to
to
fail
that
check,
but.
D
A
C
A
A
Great,
I
think
that's
it.
Thank
you,
everybody
for
keeping
working
on
this
quietly,
while
it's
still
quiet,
eventually,
it'll,
be
pretty
big
and
we'll
look
back
fondly
on
these
small
calls
with
five
people
but
yeah.
Thanks
for
the
work
everybody's
done,
and
I
guess
we'll
talk
in
the
chat
and
then
in
two
weeks
for
the
next
update.