►
From YouTube: KZG-Ceremony Breakout Call #4
Description
A
B
B
Great,
let
me
let's
wait
one
more
minute
and
then
get
started,
but
this
is
probably
all
the
people
that
will
be
showing
up.
B
F
Also,
I
apologize
involved
for
bad
audio
quality
on
the
cafe
in
paris.
F
Yeah
we
melted,
we
melted
it
but
two
days
ago,
but
today's
today's
not
too
bad.
F
Conference
five's
definitely
shifting.
I
feel
like
in
a
post,
dev
connect
worlds,
there's
like
now
technical
conferences
and
not
technical
conferences,
and
this
feels
like
it's.
It's
strap
straddling
the
line,
but
it's
by
thinking,
what's
not
technical,
at
least
in
comparison
to
previous
years.
So
that's
a
bit
interesting.
B
All
right,
I
think
we
can
get
started.
There
are
some
new
people
on
the
call.
Do
you
want
to
introduce
yourself?
Okay,
so
to
start
this
is
the
kcg
ceremony
call
we're
building
we're
crafting
the
trusted
setup,
implementation
and
the
coordinator
software.
That's
going
to
make
kcg's
trusted
setup
possible
which
will
provide
a
foundation
for
thanks,
sharding
prototype
sharding
sometime
next
year,
so
we're
getting
started
early
on
this
in
advance
of
when
we'll
need
it
yeah
it.
G
Okay,
so
hi,
I'm
daniel.
Some
of
you
already
know
me
from
eve
break
where
I
implemented
together
with
mario's
our
small
prototype
of
the
specifications
provided
by
carl
and
I'm
here
to
catch
back
up
with
everything.
That's
been
happening
in
the
meantime,
yeah.
D
Yeah,
hello,
guys,
I
am
from
netherland
pro
developer,
I'm
here
due
to
some
interesting
points
in
agenda.
I
like
to
follow
our
other
clients
updates.
So
maybe.
B
All
right,
why
don't
we
get
started
with
just
general
updates
from
the
last
two
weeks
what
people
worked
on
general
state
of
things,
any
major
updates,
carl,
let
me
start
with
you.
C
F
On
my
side
has
mostly
been
more
worrying
about
things
like
how
do
the
satchel
stations
work?
What
does
that
look
like?
I
don't
know
if
I've
discussed
on
these
polls
before
the
idea
of
sort
of
linking
attestation
back
like
double
linking
it.
F
For
participants
who
don't
want
to
implement
the
full
api,
I've
sent
some
messages
about
that.
That's
that's
mostly
what
I've
been
thinking
about,
slash
working
working
on,
but
I
guess
those
are
less
updating
things
and
more
researchy
things
we
can
discuss
later.
B
H
Yeah
hi,
I'm
guillaume
core
dev
at
the
indigo
ethereum
team,
I'm
interested
in
potentially
writing
a
zig
implementation
because
I
figured
wasm
would
be
a
nice
target,
so
I'm
mostly
here
to
figure
out
if
daniel
is
going
to
proceed
with
his
rust
implementation
yeah.
So
that's
roughly
my
goal
and
interests.
H
B
Cool
jeff
did
you
have
any
update
on
things
you've
been
working
on.
I
Okay,
yeah.
D
I
What
else
I
have
a
developer
started
a
couple
of
days
ago,
who's
hoping
he's
going
to
be
helping
out
and
for
the
time
being,
he's
just
catching
up
on
the
tools
that
we're
using
and
that
kind
of
thing
he's
got
a
lot
to
learn.
So
yeah,
that's,
what's
been
going
on.
B
Is
he
or
she
this
developer?
Are
they
part
of
the
pse
team,
or
did
you
hire
them?
Yes,
the
contractor
for
this
okay
cool.
I
I
A
yeah
like
a
three-month
trial.
I
Yeah
he's
basically
on
on
the
on
the
pse
team,
see
anything
all
goes
well.
Yeah.
B
Great,
that's
good
to
hear
you
mentioned
it
briefly,
but
do
you
want
to
talk
more
about
the
test
test
site?
I
did
try
to
do
it
myself,
chrome
on
windows,
but
I
think
it
never
actually
went
through.
Is
this
something
that
you
want
to
get
more
people
to
test,
or
is
the
small
group
enough.
I
Yeah,
we've
only
had
a
few
a
few
trials,
successful
trials
so
yeah.
I
think
this.
The
system
is
a
bit
clunky
like.
If
someone's
contribution
fails
it
doesn't.
I
I
haven't,
got
all
the
bits
and
pieces
in
to
recover
from
that.
So
a
normal
contribution
would
would
just
be
ready
to
accept
the
next
one,
but
I
haven't
put
the
failsafe
in
there
so
yeah
it's
going
to
be
a
bit
clunky.
I've
got
from
those
who
have
contributed.
I
We've
got,
maybe
you
know
six
or
eight
or
ten
valid
contra
contributions
which
gives
us
an
idea
of
the
range
of
of
you
know
of
of
what
the
performance
is
going
to
be
and,
and
importantly,
we've
hit
a
few
of
those
those
configurations
that
don't
work
that
we
know
we
need
to
work
on.
C
B
Nothing
beyond
it,
just
kind
of,
I
think
it's,
I
don't
remember
the
terminology,
it
just
said
it
was
basically
it's.
It
seemed
like
it
was
always
stuck
in
the
startup
phase,
or
maybe
that
was
doing
the
computation
and
it
for
some
reason
never
concluded,
or
at
least
as
long
as
I
kept
checking
it.
It
never
concluded.
F
I
can
try,
I
can
try
it
again
so
there's
I.
I
encountered
a
simple
thing
like
this
and
had
to
have
to
refresh
on
one
one
of
my
my
runs,
so
I
got
through
the
queue
got
to
the
front
of
the
queue,
and
then
there
was
sort
of
a
like
preparing
or
something
phase
before
I
could
doc
before
it
even
downloaded
the
transcript,
and
it
just
never
got
through
that.
B
I
F
Okay,
I
the
the
the
logs
weren't
particularly
helpful,
and
the
networking
reflection,
was
something
that
everything
wasn't
helpful
either
in
terms
of
seeing
what
went
wrong.
So
I
don't
actually
know
what
the
failure
case
was,
but
I
think
I
could
just
look
back
to
trent.
G
B
I
Oh
so,
finally,
implementation
there'll
be
a
lot
of
different
stuff
behind
the
scenes.
There'll
be
the
api.
That's
got
to
be
built,
the
the
actual
user
experience,
probably
not
all
that
different.
I
D
I
Code
for
the
website
yeah,
I
think
those
links
are
in
the
telegram
channel,
both
the
with
the
test
site
itself
and
the
code.
Let
me
draw
oh
drop
it
in
there
anyway,.
I
F
Things
I
saw
when
I
was
playing
around
your
thing
here:
jeff
is
that
it
talked
about
a
p-tower
file,
which
is
the
standard
used
by
some
other
ceremonies.
Is
that
just
what
console
console
log
is
saying,
or
are
they
actually
stuff
being
converted
in
and
out
of,
the
ptal
format
behind
the
scenes.
I
It's
it's
just
using
that!
Well,
no,
it's
just
it's
not
even
it's
just
using
a
file
that
happens
to
ends
in
p
tower,
because
that's
what
the
previous
implementation
was
using
and
it's
not
using
your
your
format,
it's
just
it's!
The
for
the
data
is
the
original
version
of
kev's
code.
F
F
And
so
then
there
aren't
any
major
the
reason
I
mentioned
the
anti-major
sort
of
computation
time
or
speed
differences
between
that
and
the
json
modulo,
the
json
encoding.
It's
not
like
we're
re-encoding
into
a
weird
format.
D
I
Oh
no,
we
have
seen
five
second
and
ten
second
contributions.
I
They
I'm
guessing
that's
a
typical
one
is
going
to
be
about
10
seconds.
I
Yeah
one
interesting
point
on
that,
though,
is
I
mean
carl
asked
for
what
what's
the
typical
range
of
of
times
we
see
from
previous
ceremonies.
So
I
did
some
analysis
on
that.
The
comments
are
in
that
document
where
carl
was
asking
the
questions,
but
there
is
a
a
very
large
range.
It's.
D
I
F
Okay,
this
is
some
implications
in
terms
of
of
how
we
set
time
marks
yeah,
if
I
ever
just
say
15
seconds
and
we
need
whatever
150
seconds
and
even
that
might
not
be
enough
to
capture
capture
everyone
based
on
I
mean
I
assume
you
don't
have
numbers
for
this,
so
just
based
on
your
intuition.
Do
you
think
this
is
due
to
people
using
their
own
slash,
different
implementations,
or
is
this
a
hardware
thing.
I
Yeah,
this
is
all
in
a
in
a
single
implementation,
so
it's
purely
the
hardware
or
whatever
platform
factors
come
into
it.
I
did
a
separate
in
our
analysis
for
internet
times,
upload
download.
So
that's
that's
excluded
and
it's
pretty
much
just
the
hardware.
Variations.
F
Yikes:
okay,
that's
interesting
and
is
this
running
wasm
in
the
browser.
D
D
F
D
I
Some
hardware
will
allow
four
threads.
Some
will
eight
more
so.
F
Yeah,
I
would
almost
expect
less
than
that
it
should
be.
It
should
be
blazingly
fast
on
the
server
side,
the
the
big
difference
between
what
you,
your
implementation,
marius,
and
this
is
that
you
can.
You
can
batch
the
pairing,
so
it's
only
one
pairing,
there's
one
one
pairing
in
total,
plus
one
multiplication
per
point.
F
Sorry,
one
one
multiplication,
one
addition
per
point
so
it'll
be
very
cheap.
F
Morris,
do
you
need?
Are
you
guys
going
to
try
implement
the
the
verification
as
well
as
then?
Would
it
be
helpful
for
like
do
you
know
how
to
do
the
the
batch
verification?
There
would
be
helpful
to
have
a
doc
explaining
that,
for
you
guys.
B
B
You
machine
works
with
oboe.
If
people
are
familiar,
do
you
want
to
just
give
a
short
intro.
J
B
Cool
glad
to
have
you
cheers
thanks,
john
the
two
things
going
back
through
the
chat.
Well,
there's
the
api.
I
think
we
already
talked
about
jeff
had
written
some
stuff
up
about
that,
but
there
carl
you
had
mentioned
doing
an
alternate
queuing
system.
Do
you
want
to
talk
about
that?
Just
summarize
it
and
where
you
landed
on
that.
F
This
interactive
check-in
queue
to
a
system
where
you
just
you,
you
call
the
api
and
it
gives
you
a
slot
of
a
longer
period
of
time,
and
this
is
for
people
who
want
to
use
their
own
implementations
or
people
who
know
they
have
really
slow
hardware
or
trying
to
do
some
weird
stuff,
with
sgx,
et
cetera,
et
cetera,
it's
sort
of
distinct
from
what
I'm
seeing
as
the
like
intro.
The
interesting
experimental
contributions
like
that'll
be
later,
and
that's
more
about
the
ceremony
around
the
randomness
and
destroying
it.
F
This
is
just
for
different
implementations
in
the
message
I
sent
I
was
proposing
saying,
like
maybe
every
eighth
day.
We
do
this,
but
I've
like
since
decided.
That's
that's
a
little
bit
ridiculous
and
makes
the
ux
very
hard
to
to
come
around
on.
So
maybe
at
the
towards
the
end
of
the
general
contribution,
like
general
public
contribution
or
at
the
beginning,
then
we
should.
We
should
have
a
period
like
this,
so
what
that
means
is.
A
F
Sorry
then
realize
I
still
muted
the
existing
system.
You
have
to
sort
of
you
check
in
and
then
it
gives
you
a
new
time
and
you
have
to
check
in
by
that
new
time
and
then
once
you've
done,
that
it
gives
you
a
new
time,
etc,
etc
until
we
get
into
30
second
intervals
right
before
your
your
contribution.
F
F
This
is
really
good
for
the,
like
general
contributions,
we're
a
little
bit
worried
about
speed,
so
a
little
bit
worried
about
how
easy
it
is
to
to
implement.
So
I'm
wanting
to
offer
a
separate
endpoint
where
you
will
apply,
and
it
will
give
you
a
time.
So
it
will
say
like
come,
come
back
at
3
pm
tomorrow
and
then
there's
no
more
checking
in
you
have
to
do
you
just
log
in
at
3
pm
tomorrow
and
say:
hey
give
me
the
the
latest
ceremony.
F
G
Okay
and
as
closer
you
become
to
the
specified
point
in
time,
the
intervals
in
which
the
participants
are
supposed
to
poll,
the
current
state
is
getting
shorter.
G
Has
there
been
some
investigation
into
something
like
having
the
participants
connect
to
like
a
websocket
endpoint,
so
they
do
not
have
to
pull,
but
instead
the
the
coordinator
pushes
the
I
say,
let's
say
current
current
transcript
to
them
as
soon
as
they
are
supposed
to
yeah.
F
I
think
you've
missed
in
the
past
and
that's
like
we're
trying
to
move
away
from
this
too,
to
coach
and
quite
simplify
the
api.
F
The
like
the
checking
version
is
not
extremely
complicated
or
it's
not
aggressive,
pulling
like
it's
going
to
be,
if
I
start
every
few
hours
and
they
get
down
to
every
30
seconds,
so
it's
nothing.
The
server
shouldn't
be
able
to
handle.
F
F
Not
for
me
at
this
point,
unless
people
have
any
ideas
as
to
whether
this
is
a
thing,
that's
necessary,
I'm
sort
of
torn
on
it,
because
it's
not
actually
that
complicated
to
just
do
the
whole
interactive
system.
To
me
where
it
it
shines,
for
maybe
people
who
want
to
have
an
air
gap
solution
or
something
like
that.
I
I
I
I
like
the
idea,
I
think
it's
it'll
it'll
be
easy
to
to
switch
and
once
we're
over
the
initial
mad
rush,
there
won't
be.
We
won't
expect
long
queues
or
so
yeah
we
get
more
flexibility
in
and
we
can
cater
for
all
those
experimental,
more
experimental
implementations
sounds
good
to
me.
E
Yeah,
it's
also
like,
if
we're
running
out
of
time
on
the
implementation
front,
we
can
implement
this
after
the
system's
already
gone,
live
like
we
can
add
this
to
the
other
queueing
system.
I
Yes,
it's
it's
two
and
they'll
have
a
token.
The
token
will
be
validated
on
every
request,
but
it
it'll
last
for
a
good
length
of
time.
So
I
don't
think
you'll
need
to
be
renewed.
I
F
G
J
G
Fulfilled
by
that
account
so
or
or
can
I
just
generate
more
accounts
if
I
like
and
use
them
to
participate
multiple
times.
I
Yeah,
so
we
are
talking
about
criteria
like
such
as
nonce
greater
than
or
equal
to
three.
Some
people
have
floated
other
ideas
like
having
a
pull
up,
or
at
least
one
leaf
in
the
account,
so
some
reasonable
barrier
to
entry
for
sure.
F
I
would
like
to
start
having
a
place
where
we
can
discuss
these
these
things
a
bit
further,
exactly
like
what
are
these
contributions
like?
What
are
our
auth
methods,
just
for,
like
general
general
discussion,
I've
had
a
few
people
like
come
to
me
quite
worried
about
what
what
are
and
aren't
the
criteria.
So
if
we
could
have
this
in
a
like
easy
to
access
public
case,
that'd
be
good,
so
jeff
you
wrote
up
some
of
those
those
your
ideas
originally
in
that
laptop.
That's,
that's!
F
That's
pretty
good,
but
I'd
like
to
like
put
this
into
a
repo
or
some
other
public
forum.
That's
a
little
bit
easier
for
multiple
people
to
contribute
to
and
have
discussions
about,
and
also
just
a
place
where
we
can
point
others
towards
if
they're
interested
or
have
ideas
on
what
should
be
included.
F
F
C
F
No
they're
they're
welcome
on
the
calls
it's
it's
more
just
that
they're
like
not
really
wanting
to
to
fully
follow
this
process,
but
they
just
have
some
opinions
that
watch
initially
included
and
I'd
like
to
accommodate
them.
Also
just
have
a
canonical
list
and
to
actually
have
the
debates
like
does
the
non
sequel,
three
five
or
two
kind
of
thing
and
like
just
just
have
this
out
loud?
Have
this
in
a
easy-to-follow
place.
B
Yeah,
no,
I
think,
that's
great
the
more
we
can
do
to
open
up
discussion
to
people
the
earlier.
The
better
part
of
the
reason
we
have
a
public
discord
channel
is
because
we
want
more
people
engaged
and
asking
questions
and
figuring
out
how
they
can
participate,
because
that's
gonna,
yeah
it'll
help
us
in
the
long
run.
B
And
this
is
something
different
to
what
kev
had
mentioned
last
week.
He
was
talking
about
another.
Let
me
see
what
he
said.
Another.
D
B
He
was
talking
about
making
another
repo
with
rationale,
type
documents.
Oh.
F
B
Yeah,
does
anybody
know
if
he
worked
on
that
or
has
an
update.
B
Okay,
then
I'll
just
reach
out
and
see
I'll
dm
him
yeah,
and
then
you
also
mentioned
the
the
sdk.
Is
there
any
update
on
that.
F
I've
sent
some
stuff
hold
on
back
back
with
kev,
I'm
just
trying
to
figure
out
exactly
what
that
looks
like,
but
nothing,
nothing,
nothing
major
or
helpful
there
I
mean
what
what
this
actually
looks
like
is
basically
just
like
what
once
cam's
happy
like
kev
and
I
are
happy
there's.
I
guess
not
too
much
discussion
on
this.
Unless
jeff
has
any
feedback
so
like
it
doesn't
affect
the
wider
implementations
for
now.
I
B
Let
me
see
okay,
it
looks
like
I'm
just
going
through
the
things
that
we
said
two
weeks
ago
we
were
going
to
take
care
of.
So
you
had
said
final
decisions
on
api
sounds
like
that.
Had
some
progress
I
don't
know
if
we're
at
like
final
final
decisions,
but
you
made
progress
on
it
right.
F
Yeah
jeff
skipped
the
stuff
jeff
did
was.
That
was
pretty
much
that
I'd
like
to
now
sort
of
just
integrate
this
into
the
repo,
and
then
we
can
yeah.
F
No,
I
I
unfortunately,
I
I'm
away
for
the
next
two
weeks.
Oh
right,
yeah,
not
not
all
of
it,
but
enough
of
it
that
I
can't
I'm
not
gonna,
make
promises
about
this.
G
B
General
comments
that
I
saw
in
the
chat
or
general
discussion
points
that
we
can
pull
forward.
There's
that
four
eight
four
four,
I
think
that's
the
right
number,
the
prototank
starting
call
on
the
29th,
but
I'm
guessing
you're,
going
to
be
away
for
that
carl,
so
I'll,
try
to
join
and
just
provide
a
small
update,
but
yeah
we've
gone
through
everything
I
had
on
the
list.
It
sounds
like
there
was
definitely
some
good
progress.
B
This
test
site
was
really
nice
to
see
that
we're
getting
it
out,
putting
cobbling
together
the
pieces
and
figuring
out
how
it's
breaking
what's
good
to
do
earlier.
B
Carl,
if
you
is
there
any
update
to
the
timeline,
as
you
see
it,
are
we
still
on
track
anything
that
you're
worried
about
as
we're
heading
towards
the
audit
in
september
or
august?
I
always
get
this
messed
up.
B
Okay,
so
the
second
half
of
the
second
half
of
august
is
what
we
have
yeah.
F
E
F
In
in
terms
of
the
actual
amount
of
work
that
needs
to
be
done,
there's
not
very
much
but
like
there's
a
bunch
of
agreement
stuff
on
like
small
things
that
need
to
be
sorted.
So
I'm
a
little
bit
worried
about
the
about
that.
B
B
A
little
more
than
two
weeks,
two
weeks
away,
is
there
anything
that
so
I
I
it
sounds
like
you're
trying
to
yeah
you've
got
a
lot
of
things
on
your
plate
at
the
moment.
Is
there
any
way
we
can
get?
Is
there
anyone
we
can
get
to
help
you
with
sdk,
or
is
this
something
that
you
just
need
to
do
yourself?
F
That
that
that's
that's
my
issue,
right,
okay,
I'm
just
I'm
I'm!
I
must
think
about
this.
We
can
check.
Should
we
control
the
sync
things.
E
B
Is
there
anything
else
on
the
agenda?
We
didn't
cover
or
sorry
something
that's
not
on
the
agenda
that
somebody
would
like
to
bring
up
or
something
I
missed
from
the
agenda.
I
With
our
psc
designers,
because
I
figured
the
design
thinking
could
happen
in
parallel
with
development
and
spec
development,
particularly
thinking
of
things
like
a
dashboard,
so
we
can
display
progress,
and
so
the
designers
our
designers
got
in
touch
spontaneous
with
the
ethereum
designers
and
they
seem
to
have
formed
a
you
know,
team
to
work
on
it,
but
how?
How
do
we
want
them
to?
How
do
we
want
to
get
engaged
with
them
going
forward?
Do
we
want
to
should
we
have
them
on
these
calls
or
that's
the
best
way
to
do
it.
B
This
seems
something
maybe
more
suited
for
my
non-uh
cryptography
skill
set.
So
I'm
happy
to
help
here,
engage
with
them
and
provide
feedback
on
the
interface
stuff,
like
that
yeah.
Definitely
at
a
minimum,
I'd
love
to
have
them
engaging
in
the
kcg
ceremony
channel
and
then
yeah.
They
can
give
updates
here
as
well.
I
don't
know
what
time
zone
they're
in
but
yeah
they're
welcome
to
join
here.
B
Okay,
I
can
I'll
message
you
after
to
get
there.
I
I'm
assuming
they
have
a
chat
somewhere
where
they're
talking
and
collaborating
so
we'll
just
figure
out
what
that
is.
They
have.
I
F
Yeah,
I
think
it's
let's
combine
for
now
and
if
it
gets
too
much
or
the
discussion
like
we
run
another
time,
then
we
can
split
up
later,
but
yeah
pronounce
that
that
seems
to
make
sense.
B
All
right,
I
think,
we're
kind
of
tapped
out
on
things
to
talk
about.
Unless
there's
anything
somebody
wants
to
bring
up.
F
Yeah
so
I'll
be,
I'm
sorry
go
ahead.
I
E
C
I
Gonna
say
I
have
a
speaking
slot
at
east
seoul
and
that's
early
august.
I
was
gonna
talk
about
this
and
flirt
a
few
hackathon
ideas.
F
Yeah
that
sounds
awesome.
Please
go
ahead
like
part
of
my
push
to
keep
this
so
simple
is
that
this
really
should
be
doable
in
a
hackathon,
so
yeah
that
sounds
fantastic,
yeah,
the
more
implementations
the
better.
F
F
So
the
the
the
standard
way
you
attest
is
you
go
on
twitter
or
your
favorite
at
the
station
platform,
and
you
say
this
contribution
number
27
was
me
and
that's
fine,
but
what
happens
if
someone
else
claims
to
also
be
contribution
27,
so
my
proposal
for
this
is
that
we
could
have
what
we
can
include
in
the
the
transcript
itself,
a
reference
back
to
some
kind
of
identity,
for
you
be
that
your
ens
or
an
address,
or
something
like
that,
so
the
transcript
itself
would
be
contain
a
signature
of
say,
called
beak.if,
and
then
I
would
also
claim
on
twitter
or
with
the
transaction,
that
I
was
contribution.
F
27
and
now
we
have
the
sort
of
double
back
to
this
double
link
system
between
the
two,
which
is
which
is
quite
nice
in
terms
of
the
actual
security
model.
It
does
not
change
a
thing
which
is
kind
of
interesting.
So
if
you
are
prepared
to
trust
you
trust,
marius
and
marius
says
on
twitter,
he
has
contribution
number
69,
then
that
should
be
all
that
you
ever
need
for
for
the
trust
model.
F
So
I
had
mixed
feelings
on
this
and
then
I'd
also
add
some
complexity
and
adds
a
little
bit
of
space
to
the
transcript.
But
I
did
the
math
on
it.
That's
that's
not
too
complicated,
but
I've
subsequently
decided
against
this
idea,
primarily
because
we've
decided
to
do
the
the
node.
Also,
the
the
subgroup
checks
after
the
contribution,
and
this
would
have
to
be
done
before
you
can
do
the
subgroup
checks,
which
would
mean
that
the
contribution
would
contain
a
signature
of
say
carl
beat.if
before
you've
done.
F
F
That's
an
idea
that,
like
hasn't
been
done
in
any
ceremony
before
and,
as
I
said
like,
doesn't
add
anything
from
a
actual
security
standpoint.
But
this
double
linked
idea
does
add
a
bit
more
like
authenticity
to
contributions
that
we
would
see
it
would
like
help.
People
trust
that
I
think,
if
you,
if
you
could
see
these
double
links,
even
if,
like
statistically
attribute.
C
F
So
the
the
complexity
itself
is
is
basically
free
because
you
already
like
it's,
it
would
be
a
bls
signature,
and
this
is
all
over
the
bls,
the
bls
curves
anyway,
and
the
signature
is
just
one
multiplication,
and
so
the
only
quote.
Unquote
addition
to
that
you
would
need
is
the
hashtag
which
for
like,
if
you're
using
someone
else's
vls
library
will
already
come
included.
But
if
you're
running
your
own
library,
which
actually
should
be
pretty
doable,
then
this
is
quite
a
bit
of
overhead.
F
Know
I
I
I
think,
issue
number
one
on
the
specs
repo
refers
to
this
one
of
the
low
numbers
like
one
or
two
refers
to
this
and
like
it
does
it
it
does
before
the
optimistic
idea.
So
it
doesn't
include
that
argument
against
it,
but
it
should
be
there,
but
I
think
more.
The
reason
I'm
raising
this
is:
I
want
to
say
that
I've
sort
of
gone
back
on
this
being
a
reasonable
idea
in
the
first
place,
and
so
just
for
the
public
record.
I
think
we
should.
G
B
Just
we
can
end
with
what
people
plan
to
work
on
over
the
next
two
weeks.
Obviously
the
audit
is
coming
up
and
carl
is
going
to
be
away
for
part
of
that,
so
we'll
figure
that
out
jeff.
What
do
you
want
to
get
done
in
the
next
two
weeks?.
I
Try
and
make
some
progress
on
the
the
the
issues
with
the
competition
there's
failing
cases.
I
I
think
my
next
two
weeks
are
going
to
be
fairly
busy
I'll,
be
traveling.
I
A
week,
so
I'm
not
sure
there'll
be
too
much
other
progress,
but
nico
is
is
working
on
on
issues
and
I've
been
converting.
I
B
Great
is
there
anybody
that
you
I
mean
vitalik
was
in
the
chat
talking
about
some
of
the
participant
id
strategies.
Is
there
anybody
that
you
feel
you'd
like
to
have
review
these
strategies
before
we
move
forward
or
like
engage
in
the
discussion.
I
Oh,
no
so
I'll
I'll
I'll
put
this
into
a
repo
as
carl
suggested
and
yeah.
Then
people
can
contribute
in
there.
F
F
That's
the
main
thing
is
it's
not
necessarily
the
specific
people
that
we
need
to
contribute
to.
We
just
need
to
have
have
the
discussions
in
public
make
sure
enough.
People
have
had
the
opportunity
to
voice
their
opinions
on
this
and
then
decide
on
exactly
what
is
the
list
of
methods
here.
B
Okay,
yeah,
I
can
that's
definitely
useful
to
have
them
in
a
repo
that
everyone
can
see,
and
will
that
be
all
of
your.
So
I
think
you
have
like
three
notion
pages.
Are
you
gonna
move
all
three
of
those
to
yeah?
Okay,
awesome.
B
All
right
anything
else,
jeff
or
is
that
it.
I
B
Okay,
on
my
side,
we
probably
have
some
paperwork.
We
need
to
do
relative
to
the
audit,
I'm
going
to
try
to
interface
with
the
designers
that
are
getting
up,
speed
and
see
if
we
can
start
sketching
out
some
ideas
and
just
figure
out
how
they're
going
to
integrate
with
the
process-
and
I
guess
those
are
yeah.
Those
are
the
two
main
things
that
I'll
be
doing
over
the
next
two
weeks.
Relative
to
this,
I
don't
know
if
we
mentioned
it,
but
yeah
we're
also
trying
to
there's
a
chance.
B
We
might
do
assuming
everything
goes
well,
we
might
do
a
live
contribution
at
devcon,
so
I've
been
talking
with
the
organizers
about
what
that
would
look
like
how
much
time
we
would
need
things
like
that.
Just
making
sure
they're
aware
of
what
this
project
is
and
trying
to
see
if
we
can
get
it
get
a
slot
on
the
main
stage
during
kickoff.
B
Yeah
we're
thinking
of
doing
it
is
well,
it
depends
on
what
the
the
random
inputs
are
and
how
that's
figured
in,
but
something
like
taking
a
picture
of
the
the
main
hall
and
then
that's
the
that's.
The
randomness
input.
F
Yeah,
I
think,
no
matter
what
we
end
up
doing
it's
not
going
to
be
actually
a
very
meaningfully
secure
contribution,
but
it's
more
just
for
the
fun
and
ceremonial,
but
that's
cool
too
right
right,
yeah,
exactly
we're
not
pretending!
This
is
the
be
all
and
end
all
and
yeah.
B
All
right,
we
can
probably
rap
here-
I
will
connect
with
kev,
just
see
what
he
was
up
to
for
the
since
the
last
meeting,
and
then
yeah,
and
one
thing
I
mentioned
to
carl
and
maybe
also
on
the
last
call-
is
that
ideally,
we
start
to
have-
I
mean
last
week
was
good,
but
we
want
to
make
sure
we're
having
discussions
in
public
moving
stuff
to
repo
is
also
really
good,
but
the
more
discussions
we
can
have
in
that
public
discord
channel
the
better
for
people
who
jump
in
a
month
or
two
from
now
and
are
trying
to
catch
up
yeah.
B
All
right.
Honestly,
anybody
wants
to
jump
and
interrupt
me.
We
can
wrap
here.
Thank
you.
Everybody,
for
this
is
the
fourth
call.
I
think,
thanks
for
joining
the
fourth
ceremony
call,
this
early
planning
stuff
is
crucial
to
you
know,
making
the
ceremony
work
at
all
and
in
long
term
the
producting
sharding
and
things
other
constructions
like
that.
So
it's
important
work.
It
might
feel
like
a
like
just
another
bi-weekly
meeting,
but
this
is
this
is
really
crucial
stuff.
So
thank
you.