►
From YouTube: KZG-Ceremony Breakout Call #9
Description
A
We
can
probably
just
get
started
I
get
in
the
habit
of
awkward
ifs
where
we
wait
like
three
minutes,
but
this
is
a
small
enough
group
wow
a
lot
of
new
people.
A
Why
don't
we
just
start
with
the
overview
of
where
the
people
working
on
sequencer
stuff
have
gotten
Remco
slash
Carl,
whichever
you'd
like
to
go
there?
Okay,.
B
Sure
I
could
take
it,
so
we've
been
making
good
progress
on
the
sequence.
Third,
we
have
a
test
instance
up
and
running
and
we're
kind
of
implementing
the
final
things.
I
guess
from
my
side,
the
biggest
missing
thing
is
the
entropy
generation.
I
actually
know
this
is
client-side
stuff
from
the
library.
A
C
So
I
think
one
important
information
is
I've,
updated,
end-to-point
documentation
in
sequencer
specs,
but
we
still
haven't
finalized
all
of
the
fields
that
are
coming
in
the
requests
and
response
bodies.
So
if
you're
doing
client
work
and
want
to
interface
with
sequencer,
you
should
probably
use
the
and
the
version
is
deployed
to
fly.
I
o
to
make
sure
that
the
data
that
you're
getting
makes
sense.
D
I
I
just
have
a
comment
there
on
the
front
end
part
we
are
integrating
it
and
everything
is
going
good.
A
the
only
thing
that
we
were
having
some
issues
with
the
deployed
version
was
the
the
redirect.
We
need
a
you
guys
from
the
back
end
to
authorize
us
on
on
the
domain
to
to
redirect
you
right
is
that
did
I
express
myself
correctly.
B
Yeah
I
think
this
makes
sense.
The
redirect
might
actually
be
defaulted
to
localhost,
where
it
should
be
now
also
allowing
the
fly.
I
o
redirect.
E
I
was
I
was
responding
about
that
on
telegram
yesterday,
so
the
redirect
us
URL
doesn't
really
matter
because
the
front-end
can
make
it
whatever
they
want,
but
Remco
you
need
to.
You
need
to
whitelist
them
in
in
the
applications
you
have
configured
so
the
the
application
that
you
are
running
on
GitHub
and
the
one
inside
ethereum.org.
You
need
to
whitelist
all
the
URLs
that
the
front-ends
will
be
using.
B
Yeah,
isn't
this
problematic
because
this
makes
it
closed?
Can
we
instead
just
whitelist
the
sequencer
and
then
have
the
sequencer
do
another
redirect
to
whatever
the
front
end
wants.
E
We
could
do
that.
I
was
proposing
that
a
few
weeks
back
and
then
kept
suggested
that
we
skip
it
for
now,
but
we
can
get
back
to
this.
E
I
mean
you
can
just
rub
the
old
flow
so
that
it
makes
it's
it's
easier
for
the
front
ends
to
use
because
yeah,
if
you
want
to
be
truly
decentralized,
you
probably
want
to
have
independent
contents
without
needing
to
whitelist
each
of
them.
F
No
I
mean
like
there's
like
specific
oauth
standard
flows
and
I.
Don't
think
that's
one
of
them.
If
you
want
to
do
like
arbitrary
front
ends,
it's
either
a
white
listing
them
or
you
have
to
have
the
people
running
the
front
end
on
their
Local
Host.
B
No,
this
is
great.
This
is
like
why
we
need
to
why
we
need
to
have
an
additional
redirect
outside
of
oauth
to
to
circumvent
this
oauth
limitation.
E
G
F
I
I
probably
suggest
to
look
at
the
oau
wolf
standard
fluids
that
they
have
because
they
have
like
a
lot
of
standards
and
they've
sort
of
made
things
the
way.
The
way
to
this
or
I
don't
know
about
security,
if
we're
doing
something
outside
of
the
standard.
C
So
so,
once
you
sign
in
with
GitHub,
you
receive
a
secret
token
right
and
by
default
it
goes
to
the
front-end
app.
But
now
what?
What
matching
suggesting
is
that
you
go
to
sequencer
and
then
that
sequencer
would
forward
that
secret
token
back
to
the
front
and
that's
initiated
the
call.
E
F
E
Try
to
build
the
proof
of
concept
today
or
tomorrow
tomorrow
and
then
let
you
guys
know
in
the
diagram
if
it
works,
and
then
you
can
take
a
look
if
you
find
it
insecure
in
any
way.
F
All
right,
thank
you.
Yeah,
on
my
end,
I
was
trying
to
test
out
the
end
points.
I
couldn't
get
the
flight.io
version,
working
I
think
I
was
getting
an
invalid
CRF
token,
so
I
was
doing
it
offline.
Instead,
I
did
just
to
make
sure
everything
was
interoperable.
I
used
the
cryptography
library
at
the
sequence
it
was
using
and
it
seemed
to
be
slow
on
the
clay.
F
I
think
from
what
I
was
using.
I
was
doing
ad
entropy,
which
is
doing
validation,
checks
before
the
the
contributor
added
the
entropy.
So
I
think
they
were
sanity
checks.
Some
of
them
are
not
in
the
spec
like
ensuring
that
all
of
the
srs's
are
unique
and
there's
another
comment
to
say
that
the
public
Keys
need
to
be
distinct,
I
think
some
of
these
checks
we
did
say
we
were
not
going
to
include
and
I
think
most
of
the
checks
anyways
should
be
done
after
the
contribution
is
done.
B
H
B
Have
the
full
transcript
you
do
have
some
uniqueness
checks.
You
can
do,
for
example,
unless
you're
the
very
first
contributor.
All
the
points
should
be
distinct,
otherwise
you're
in
some
small
order,
subgroup,
which
you
want
to
avoid.
H
B
H
F
Great
I'm,
so
my
question
towards
this
is:
aren't
all
of
this.
On
all
of
these
things
covered
by
the
subgroup
checks
and
the
structure
checks
that
we
do
and.
B
J
B
I
mean
this
is
just
going
the
extra
mile
and
we
can
remove
it
if
you
don't
consider
it
necessary
or
otherwise
dangerous,
but
what
I'm
doing
is
I'm
just
like
I'm,
just
taking
the
raw
binary
encoding
of
all
the
points
and
I
just
make
sure
that
all
of
them
are
distinct,
and
what
this,
for
example
covers
that
is
not
otherwise
covered.
Is
that
if
Tau
ends
up
being,
let's
say
some
root
of
unity,
of
small
order?
B
That
would
pass
all
the
order
checks,
but
it
would
result
in
a
repeating
sequence
of
values
in
your
ceremony
instead
of
distinct
values.
Well,.
J
But
I
mean
any
participant
who,
like
I
mean
there
are
many
ways
in
which
I
can
add
no
entropy
right.
I
can
do
it
by
just
setting
my
secret
equals
one.
I
can
do
it
by
setting
it
equal
to
a
root
of
unity.
J
B
I
agree
this.
B
I
I
agree:
these.
These
checks
are
not
there
to
guard
against
any
particularly
sophisticated
attack.
They're
more
sanity
attacks
that
guard
against
stupid
mistakes,
so
to
say,
or
implements.
B
Something
you
could
have
two
participants
colluding
and
like
one
multiplies
by
a
random
factor
and
the
other
multiplies
by
the
inverse.
There
are
tricks
around
that,
but
you.
J
B
J
G
J
H
J
Then
you
are
not
not
an
honest
participant.
H
So
the
people
in
front
of
you
use
roots
of
unity
and
then
you
add
on
the
first
valid
contribution.
On
top
of
that.
J
H
B
Okay,
it
also
costs
very
little.
I
I
see
this
more
as
assertions
things.
You
know
that
should
pass,
and
should
they
not
pass
you're
very
happy
that
your
application
crashed
crashed
instead
of
proceeding
come
on.
F
I
wrote
them
up
just
because
when
sorry,
when
the
code
gets
audited,
there
might
ask:
why?
Is
there
a
difference
between
what's
implemented
and
what
the
specs
specify.
B
F
C
F
I
think
was
this
Benchmark
because
for
me
on
the
clients
like
taking
quite
a
long
time
to
validate
all
of
it,.
B
Yes,
it
the
subgroup
check
is
about
half
the
time
consumed.
It
uses
the
endomorphism
optimization.
So
it's
decently,
efficient,
I,
think
blsd
is
a
bit
faster
here.
So
when
we
have
the
working
blsd
back
end
that
might
be
preferred
by
clients,
although
we
haven't
done
a
proper
Benchmark
yet
in
in
a
multi-threaded
awesome
environment.
F
Oh
no
I'm,
so
I'm
implementing
Clay
did
you
have
any
numbers
for
Clive,
because
maybe
my
numbers
are
just
off
right.
It.
H
F
I
haven't
sort
of
benchmarked
specific
numbers,
but
they
were
like
noticeable.
I
could
say
like
five,
maybe
seven
seconds
so
I
think
maybe
if
something's
off
on
my
setup,
all.
F
F
Yeah
could
be
actually
I'm
running
an
Intel
Mac,
eight
core
Intel
I9
foreign
yeah
I
need
to
debug
what's
happening
there.
K
B
F
B
You
did
you
get
substantially
better
performance
with
the
with
your
own
powers
of
Tao
lip.
F
Yeah
but
I
wasn't
doing
any
subgroup
checks
up
front.
Okay,.
B
Now,
just
those
are
expensive
that
could
explain
the
difference.
F
B
F
Right
I
think
I
brought
this
up
as
well
and
I.
Think
me
and
Dan
Kratz
said
we
was
on
Telegram
and
it
was
agreed
to
not
do
this.
Okay,
because
it's
just
an
over
Edge
case.
Sorry.
B
Oh
okay,
checking
that
the
puppies
are
distincts
to
just
catch
implementers
that
use
the
same
Tower
point
in
each
sub-ceremony,
which
seems
like
a
obvious
front-end
mistake
and
catching
that
might
help
build
better
front
ends.
H
Yes,
this
was
a
discussion
we
had
earlier.
It
was
less
in
the
context
of
front-end
mistakes,
but
more
on
doing
it
like
maliciously,
and
then
it
was
argued
that
that's
no
different
from
just
leaking
your
secret
and
also
they're
like
more
complicated
ways
such
that,
like
combining
multiple
contributions,
could
add
up
to
being
the
same
for
one
contribution,
etc,
etc,
but
as
a
way
of
catching
people.
This
might
be
something
worth
adding
to
the
sequencer
as
and
as
you're
saying
hardening
front
ends.
F
H
But
I'm
saying
I'm
saying
like
as
a
way
of
hardening
front
ends.
I
could
see
the
argument
for
it.
B
Yeah,
maybe
maybe
we
can
leave
these
enabled
for
the
test
version,
while
people
are
developing
and
then
just
remove
them
for
the
production
version
or
for
the
audit
yeah.
F
Yeah,
that
makes
sense
just
to
make
sure
implementations
aren't
accidentally
not
being
compliant.
H
F
B
My
Approach
here
has
been
values
need
to
be
distinct
unless
I
can
come
up
with
an
argument
why
they
should
so,
like
all
all
G2
points
in
the
whole
ceremony
and
transcript
file
need
to
be
distinct
unless
the
they're
not
demands.
Otherwise,
that's
that's
kind
of
my
Approach
towards
these
energy
checks.
It's
basically
like
taking
it
from
the
other
direction,
but.
G
B
In
this,
in
this
particular
case,
it
catches
a
number
of
things
like,
for
example,
the
the
roots
of
unity
or
like
cosets
thereof,
but
also
so
you
know,
of
course,
that's
not
work
anyway,
but
also
contributing
the
same
Tau
value.
B
F
Right
I
guess
it's
sort
of
hard
to
catch
all
of
the
edge
cases
and
you
can
sort
of
do
like
what,
if
for
the
transcript
I,
don't
know,
I
think
that
would
probably
be
something
we
should
skip
just
because
that's
it
goes
linearly
with
the
number
of
contributions,
but
for
a
particular
contribution.
H
Yeah
I
think
like
again,
I,
don't
think
room
crackery.
It
makes
sense
at
some
level
and
we
should
see
uniqueness
here.
But
it's
sort
of
hard
to
argue
for
this
as
being
good
standard
Behavior.
If
it's
not
in
the
specs-
and
it
seems
a
bit
weird
to
specify.
K
A
Yeah
I
can
just
jump
in
I
think
the
generally
given
we
have
a
high
profile
demo
in
a
couple
weeks.
I'd
rather
leave
any
other
changes
out
for
now
and
just
get
to
the
simplest
working
interface
with
sequencer
that
we
can
and
then
I
think
post
Devcon.
A
We
should
have
like
a
week
or
two
just
to
tighten
everything
up
and
get
it
ready
for
the
public
reveal
and
then
maybe
we
can
add
anything
else
at
that
point,
but
for
now
I
think
we
should
probably
limit
any
other
last
mile
things,
though
it
though
it
is
appreciated,
Remco.
B
Sure
now
it
can
be
can
be
disabled
I
can
I
can
see
two
ways
forward
here.
So
definitely
disable
in
production
I
can
feature
flag
it
in
Rust
and
just
have
the
code
be
disabled
for
the
production
person,
or
do
you
prefer
to
have
it
actually
physically
removed
just
so
it's
obvious
for
Auditors
or
whatever.
F
I
think
probably
removed
just
less
code
if
it's
not
going
to
be
used
in
production,
unless
someone
else
thinks
it
should
sleep.
F
Yeah
sorry
back
to
what
Trent
said
so
back
on
this
double
Eve
sign-in
thing:
that's
not
going
to
be
included
in
the
the
demo
is
that
correct,
I
haven't
actually
implemented
it
in
the
clay
or
looked
into
implementing
it.
A
Sorry,
yeah,
you
mean
the
where
you
sign
your
contribution
through.
H
H
Basically,
on
the
one
side,
it's
a
eip712
signature
shout
out
dremco
of
the
the
four
public
keys
that
you're
using
and
the
other
way
around
they're,
just
a
BLS
signature
of
your
identity,
which
is
just
either
eth
appended
to
your
name
or
GitHub
appended
to
your
GitHub
address.
It's
the
the
I've
got
some
argumentation
as
to
why
we
only
basically
there's
only
a
double
signature
for
the
eth
stuff
and
for
GitHub.
H
It
doesn't
really
matter
so
in
terms
of
implementation,
it's
just
being
able
to
to
sign
and
verify
each
signatures,
plus
the
BLS
stuff
BLS
signature
should
already
be
in
the
BLS
libraries.
People
are
using
the
one
complexity
here
being
for
the
sequencer
whether
we
can
find
a
decent
hash.
H
The
Curve
implementation
for
artworks
either
just
copying
the
copying
hash
the
curve
out
of
blast
or
something
like
that
or
using
one
of
these
other
implementations,
particularly
if
it's
running
in
parallel,
that
seems
okay,
but
that
becomes
a
bit
more
complicated
than
for
the
wasn't
blob.
H
What
are
we
doing
for
Azure
curve
there
and
then
the
other
side
is
the
the
ecdsa
signatures,
but
most
web
free
apis,
slash,
Json
apis
should
offer
sign
type
data
by
now
the
exception
here
being
web3.js,
but
I
see
that
the
the
ZK
party
front
end
is
using
ethers,
so
I
think
we
should
be
all
right
on
that
front.
F
Right
but
for
Dev
component
seems
like
there's,
probably
not
enough
time
to
include
this
double
signing
like
it
probably
be
a
bit
of
a
stretch
to
get
everything
done
with
the
double
signing.
F
B
I
think
sequencer,
and
we
move
really
fast
that
should
yeah.
That
should
not
be
a
concern.
H
So,
on
the
sequencer
side,
assuming
you
can
get
around
the
hashtag
thing
and
you
guys
are
doing
the
awesome
stuff
as
well,
so
the
hashtag
things
on
your
side.
There,
too,
the
changes
should
just
be
calling
like
two
extra
API
calls.
That's
fairly
simple
on
the
I
guess,
there's
more
effort
on
the
front-end
side.
H
Again,
it's
two
API
calls.
So
that's
relatively
simple:
it's
I
guess
just
incorporating
it
into
the
user
flow
as
one
extra
step.
D
Wrong
to
implement
that,
but
we
we
were
considering
that
you
call.
H
Yeah
kind
of
just
just
like:
what's
if,
if
is
there
something
you
think
you
that
that
could
be
done
in
time?
I
guess
you?
Don't
you
don't
know
the
specs?
So
it's
hard
to
see,
but
assuming
it's
like
three
lines
of
of
code
or
five
lines
of
code
in
terms
of
like
spec
logic
is:
is
there
something
that
we
could
see
done
by
Devcon,
because
I
think
it
would
be
really
nice.
D
I
I
think
we
can
do
it
on
okay.
So,
regarding
the
the
front
end,
we
have
all
the
entropy
input,
interaction
that
is
Charlie's
doing
a
really
nice
animation
work.
A
I
am
I
already
have.
The
contribution,
like
I,
am
using
the
rust
code
using
a
router.
So
if
everything
changed
from
the
original
code,
I
can.
F
D
K
H
It's
it's
not
it's
not
even
that
the
basically
what
it
is
is
you
take
either
the
user's
GitHub
handle
or
the
their
ethereum
address,
feed
into
a
function
which
gives
you
the
byte
encoding
of
that,
like
the
the
standardized
byte
encoding
and
then
call
a
function
that
requests
a
signature
from
the
user's
wallet
which
exists
in
in
ethos.
K
H
So
that
the
work
here
is
more
just
that
it's
a
an
extra
step,
that's
sort
of
like
after
entropy
generation,
but
before
you
start
like
before,
you
start
pinging
the
coordinator
to
try
contribute
that
you
need
to
get
an
extra
ecdsa
signature
from
the
user.
A
H
I'll
push
the
specs,
probably
two,
two
or
so
hours
after
this
call,
and
we
can.
We
can
have
a
discussion
I'm
happy
to
help
run
people
through
it,
see
what
whatever
like
wherever
the
pain
points.
Are
that
kind
of
thing,
and
hopefully
we
can.
We
can
make
a
final
call
by
the
end
of
today,
but
then
I'm
gonna
operate
under
the
assumption
that
this
is
not
too
difficult
to
implement
and
therefore
we
can
do
it.
A
A
So
that's
Charlie,
Nicholas
Jeff,
takamichi.
K
Oh
yeah,
so
yeah
so
takamichi
has
been
working
on
that
on
implementing
design,
as
as
design
change
has
gone
through.
C
K
Has
been
working
on
the
bosom
stuff,
as
he
mentioned
question
about
the
wasm.
If
we
end
up
with
blft
version
should,
should
we
be
looking
to
use
that
or
at
the
moment
we're
implementing
kids
code
and
and
when
we
do
include
the
subgroup
checks,
it
does
add
quite
a
bit
to
the
time.
K
So
should
we
and
we
haven't,
got
a
good
feeling
for
how
that's
going
to
pan
out
at
the
moment,
you
haven't
done
all
the
checks
to
see
if
the
multi-threading
is
yeah
working
properly
and
everything,
but
still
we'd,
be
looking.
F
H
Argument
here
is
it's
basically
optimistic
contribution,
so
that,
in
terms
of
the
queue
processing
speed,
it
doesn't
get
added.
As
in
you,
you
already
upload
the
file
once
you've
contributed
without
having
done
the
subgroup
checks
and
because
the
sequencer
is
signing
everything
you
can
chat
about
it
after
the
fact
that
signed
messages
from
the
sequencer
if
they
sent
you
something
where
the
subgroup
checks
don't
pass.
H
It's
a
like.
It
feels
like
a
slightly
weird
thing
to
do,
but
because,
like
a
because
we're
trusting
the
sequencer
not
to
try
screw
with
everyone
and
B,
if
you
do
be
managed
to
pick
up
something
here,
that
means
something
dramatic
has
gone
wrong
and
we
have
a
like
authenticated
way
of
proving
this
happened
with
the
the
signature
from
the
the
sequencer,
then
that
seems
yeah.
This
was
deemed
acceptable.
B
Makes
sense,
yeah
I'm
just
wondering
if,
if
adding
Tau
by
itself
doesn't
Force
the
points
out
of
the
subgroup.
H
H
Like
if,
if
you
multiply
a
point
by
some
random
number-
and
this
point
has
is
a
part
of
a
load-
a
subgroup
was
a
lot
of
subgroup
component
mixed
in.
Is
it
still?
Does
it
still
have
that
low
order
subgroup
component
in
there?
And
my
answer
is
yes,
you.
F
J
Sorry,
what
are
what
are
we
doing
are
we
are?
We
are
we
talking
about
so
Omega?
How
many
guys
in
the
water
field
element
right
and
we
have
omega
times
G,
and
now
we
take
a
random
number
R
and
compute
R
times
Omega
times
d.
Is
that
what
we're
talking
about.
J
J
F
J
Well,
yes,
yeah
yeah,
so
okay,
right
well,
yeah
I
mean
that
depends
on
your
definition
of
the
curve.
I
mean
it's.
H
J
Solution
to
the
elliptic
curve-
equations?
Yes,
yes,
okay,
right,
yeah,.
H
J
B
I'm
saying
this
is
this:
is
about
whether
it
changes
anything
if
we
move
the
subgroup
check
on
the
contributor
side
to
after
adding
the
new
Tau
value,
but
what
it
is
the.
H
J
H
J
Okay,
but
I
mean
I
was
saying
like
we're
running
out
of
storage
here
or
what
like
I
mean
like
just
store,
just
store
it
and
then
do
the
check
that
seems
trivial
right,
I
agree
with
you,
yeah
I
would
I
mean
I.
Would
just
do
it
on
the
original
first
it's
signed,
so
we
need
to
do
it
on
the
original
and
second
there's
a
small
chance
that
your
contribution
might
erase
the
like.
F
H
B
H
In
that
case,
can
we
add
a
signature
to
the
the
the
Json
message?
Basically,
that
gets
sent
the
the
contribution
file.
F
K
F
F
Usually,
once
you
do
the
oauth,
the
sequencer
gets
back
your
GitHub
ID
and
then
he
sends
it
back
to
the
client
with
a
couple
other
information
and
that
used
to
be
signed.
Whereas
now
that's
not
signed,
so
the
sequencer
could
just
say
like
you're
consent,
because
like
collude
of
two
people
and
say
you're,
vitalik
or
something
and
then
yeah,
that's
mainly
the
attack
director.
You
can
just
basically
say
I,
didn't
send
you
the
GitHub
ID
vitalik,
but
it.
H
F
No
it's
not
over.
It
was
just
that
the
ID
token
was
signed,
but
I'm
thinking
through
the
attack,
vector
and
I,
think
that,
because
they
send
the
receipt
it
doesn't
matter
because
they
have
to
sign
a
receipt
at
the
end.
E
I
mean
I
can
always
lie
about
having
authenticated
a
user
without
them,
unless
I'm
doing
some
action
that,
like
unless
I'm
I'm
posting
something
on
your
GitHub
account,
I
can
always
say
that
I
authenticated
you
I,
don't
know
how.
How
would
you
define
defend
against
it?
It's
just
an
ID
right
like
it's
a
string
that
I
can
make
up
always.
F
Well,
if
you're
assigning
your
lives,
I
could
say
that
you
lied.
If
you're
just
not
signing
your
lies,
then
you
could
say
it
wasn't
me.
You
sent
it
to
you,
but
like
back
to
the
original
I,
think
it
doesn't
matter
because
the
receipts
are
signed.
So
once
you
contribute
I
sign
your
receipt,
which
includes
the
ID
token,
so
it
doesn't
matter
actually.
H
F
E
H
F
Right,
but
in
this
in
the
GitHub
case,
still
because
we
signed
a
receipts
which
include
the
ID
token,
you
can
at
least
hold
the
sequencer
accountable.
H
Yeah
sure
this
is
an
additional
way
of
holding
them
accountable.
I
guess.
F
F
H
H
F
Come
over
here,
yeah
I
did
have
a
few
comments
on
some
sequence
of
stuff,
but
I
think
we
can
probably
do
it
async,
since
they
don't
affect
most
people.
F
C
A
K
A
If
you
want
to
write
that
up
for
the
interface
people
to
check
on
that'd
be
good
Charlie,
do
you
want
to
do
a
quick
demo.
A
Yeah
up
to
you,
takamichi
on
my
side,
I've
been
working
on
a
sort
of
a
some
adjustments
to
the
interface,
so
it's
just
has
a
little
bit
of
a
different
graphic
style,
and
so
this
won't
show
that.
So
it's
on
me
to
get
that
done,
ASAP
and
properly
transferred
over
to
the
interface
team,
but
takamichi.
If,
if
you
want
to
do
a
demo
now
that
that'd
be
fine
or
any
other
interface
comments,
if
you'd
like
to
bring
them
up
now,
yeah.
K
G
Okay,
so
I
can
show
some
quick
demo
now
and
actually
it's
not
complete
yet
so.
G
But
for
now
it
it
can
sign
in
and
contribute
to
contribute
to
the
sequencer
calculate
calculating
the
contribution
using
the
Watson
web
worker.
So
for
that
part,
I
can
show
the
the
quick
demo
right.
G
A
How
about
that
I
made
you
co-host?
Yes,.
G
All
right,
so
here
is
a
the
front
end
of
the
the
ceremony.
Trust
is
set
up.
Yep
here
is
a
landing
page
and
it
has
descriptions
of
the
trust
is
set
up
and
there's
a
if
AQ
section
here
and
some
footer
yep
and
it's.
G
And
so
here
is
a
design
in
page
and
once
you
click
the
sign
name
for
the
ethereum,
can
you
see
the
key
pop-up
of
the
assignment.
G
K
K
G
This
pop-up
will
show
and
you
can
proceed
by
assign
sign.
Indeed
the
old
provider
yeah,
then
the
entropy
input
page
shows
and,
as
you
can
see
here,
is
the
progress
board
that
they
capture
the
mouse,
Movement
Like,
This
and
also
here's
a
some
problem.
But
and
once
the
the
progress
are
complete,
you
can
enter
to
the
lobby.
G
And
now
so.
J
G
Okay
so
now
it
automatically
pulling
the
the
try
contribution,
API
endpoint
and
once
it
gets
accepted
it
automatically
start
calculating
the
contribution.
Backend
I
mean
the
in
the
washroom
webworker.
Then
this
is
going
to
take
a
while.
So
maybe
we
can
I
can
stop
here,
but
yeah
after
this
finished
and
posting
to
the
the
sequencer
endpoint
yeah.
That
contribution
is
done.
F
G
Yes,
yeah
I
need
to
I
need
to
fetch
the
user
data
from
the
old
provider,
but
yeah
for
now.
I
am
recording
yes,.
F
They
give
you
back
an
ID
token,
which
includes
the
GitHub
like
there's
a
something
called,
a
nickname
for
affirm
it's
the
firm
address
and
for
GitHub
it's
the
GitHub
user
ID.
Thank.
G
A
Great
yeah,
echoing
that
it's
nice
to
see,
feels
like
90
we're
almost
there,
which
is
great,
given
how
close
we
are.
Are
there
any
big
blockers
or
challenges
you're
having
implementing
stuff
it
that
haven't
been
brought
up
yet.
G
I
think
there's
not
that
big
blocker
for
now
yeah,
but
I
I
need
to
modify
I
needed
to
modify
some
sequencer
code
like
adding
some
course
layer
to
the
Axiom
or
the
the
disabled
right,
limiting
the
body
size
of
the
the
API
or
something
like
that.
But
it's
I
think
it's
not
that
program
and
yeah
everything
is
going.
Fine,
I!
Think,
okay,.
A
Great,
if
you
need
help
or
you're
falling
behind
just
say
it
sooner
rather
than
later,
so
that
we
can
find
some
more
people
to
help
you
or
any
anybody
on
the
interface
team,
yeah
yeah.
Thank.
G
F
Could
you
pay
me
about
the
rate
limit
disabling
that
you
did?
I
saw
that
you
used
an
experiment,
dress
which
looked
like
it
was
new,
so
I'm
guessing
you
also
disabled
the
validation
checks.
F
G
Actually,
what
I
meant
was
the
the
body
size
limit
of
the
post
requests?
So
it's
it's
not
about
the
the
limiting
The
Ether
others
from
the
same
ethernet
address.
F
Okay,
yeah
sorry
I
brought
up
two
two
two
issues
and
just
skipped
over
so
for
the
first
one,
the
rate
limit.
Could
you
ping
me
about
that?
Okay,.
G
F
G
No
for
for
the
sequencer
I
I'm
resetting
the
database
every
time
I
try
so.
E
Also,
it
would
be,
it
would
be
great
if
you
could
open
GitHub
issues
or
write
on
telegram
or
in
any
other
way.
Let
us
know
that
there
are
problems
you
are
facing
with
the
sequencer.
F
Yeah,
sorry
about
that
I
was
sort
of
collecting
them.
F
E
Yeah
I
agree,
so
yeah
open
a
GitHub
issue
or
a
request,
but
if,
if
you
actually
fixed,
it
would
be
great
to
to
have
it
working
please.
So
the
issues
who
gets
found.
A
All
right,
we
are
at
time
really
quickly
given,
given
how
close
we
are
to
Defcon
I
think
it
might
make
sense
to
have
another
call.
Next
week,
just
optional
I
mean
these
are
all
optional,
but
if
people
want
to
show
up-
and
hopefully
we'll
have
a
demo
by
then-
or
we
can
do
this-
the
same
type
of
demo
next
week
same
time,
and
that
would
be
good
just
to
continue
ironing
out
any
issues
that
come
up.
A
I'll
go
first,
but
over
the
next
few
days,
really
I'm
gonna
be
really
pushing
hard
on
any
of
the
interface
updates
to
get
them
to
the
people
working
on
that
as
soon
as
possible.
So
they
can
make
the
modifications
anybody
else
have
some
pressing
concerns
other
than
like
getting
stuff
done
in
preparation
for
this
demo.
If
anybody
wants
to
say
what
they're
going
to
be
working
on
now
would
be
the
time.
I
So
I
I,
don't
I
I'm,
pretty
sure
I
haven't
met
most
of
you
guys,
but
I
did
an
implementation
of
both
the
sequencer
and
a
client
for
each
Prague
and
I
would
like
to
do
at
least
the
client
part
for
the
real
ceremony
as
well.
I've
been
just
trying
to
go
through
the
specs,
the
the
open,
API
ones
and
there's
a
lot
of
stuff
missing
or
kind
of
weird
in
it.
I
H
I
I
Yeah,
like
the
data
types,
are
not
really
specified,
or
some
endpoints
lack
the
data
types
that
I
would
suspect.
H
Yes,
that
is
correct.
I
think
this
is
also,
but
because
there
was
Debaters
to
what
should
be
included
in
that,
but
yeah
I,
don't
I,
don't
know
if
the
sequence
of
people
have
a
have
a
comment
on
that.
E
I
would
just
say
once
once
again
write
it
in
a
GitHub
issue
or
in
either
the
specs
repo
or
in
the
in
the
sequencer
repo,
and
then
we
can.
If
you
find
any
discrepancy
between
between
the
documentation
and
the
actual
Behavior,
we
will
reconcile
it
by
changing
one
of
them.
E
K
F
I
think
this
is
a
something
that
needs
to
be
added
to
this
specs.
The
open,
API
yeah
added
the
status
but
I
didn't
add
it
into
the
specs.
H
Yeah
no
you're
you're
correct
here,
Mars,
that's
a
that's
a
great
in
general!
There's
this
other
repo,
which
has
got
links
to
everything
else.
You
should
need
to
find
Marius,
but
the
two
replays
you
have
now
should
be
sufficient.
B
Marius,
the
other
work
you've
done
at
eat
proc
public
somewhere,
and
can
you
share.
I
I'll
put
a
link
in
chat.
Thank.
H
A
All
right,
so
it
sounds
like
yeah,
there's
still
still
some
work
to
be
done,
like
I
said
we'll
plan
to
meet
again
next
week,
even
though
it's
usually
every
two
weeks
we'll
meet
again
next
week
and
everybody
will
probably
continue
with
the
the
regular
async
coms
over
the
next
few
days
in
the
Discord
telegram
Etc.
A
A
There
are
three
speakers
and
we
are
just
before
vitalik,
so
this
is
going
to
be
very
high
profile,
very
visible
and
hopefully
get
a
lot
of
people
exposed
to
what
we've
been
working
on
for
the
past
few
months-
and
you
know
it'll
be
nice
to
have
the
work
visible
by
so
many
people
in
the
ethereum
community
on
such
a
high
profile
place.
So
great
work,
everybody.
So
far.
A
We
are
at
the
the
last
stretch
before
the
public
sees
this,
and
then
you
know
it's
going
to
be
really
exciting.
I'm
I'm,
pretty
stoked
so
I
was
talking
with
Carl
and
I.
Think
if
we
can
make
it
happen,
if
you're
in
Bogota,
while
we're
doing
this
presentation,
we'd
be
happy
to
have
you
on
the
stage
logistic
issues
assuming
we
can,
we
can
work
it
out,
but
it
would
be
really
cool
to
have
people
on
stage
that
worked
on
this.
A
So
that's
where
I'll
leave
it
we're
a
couple
minutes
over
thanks
everybody
for
sticking
around
and
we'll
see
you
next
week.