►
From YouTube: KZG-Ceremony Breakout Call #6
Description
A
A
With
updates
from
the
bespec
side,
I
merged
a
fairly
with
a
pr
with
fairly
big
changes,
as
a
pr
number
16,
basically
doing
what
we
discussed
last
week,
which
was
separating
out
like
the
files
that
contributors
receive
from
the
full
transcript
and
so
that
the
the
file
size
is
constant
for
the
contributors.
A
The
the
changes,
I
think
are
fairly
sensible,
I'm
not
entirely
happy
with
the
naming
yet
so
I've
called
the
the
the
father
gets
sent,
sent
around
a
contribution
which
I
see
by
chance
happen
to
line
up
with
jeff's
api
pr,
but
we
can
discuss
that
in
a
moment
and
then
the
full
thing
is
the
transfer,
but
it
gets
a
little
bit
more
confusing
when
we
talk
about
sub
contributions
and
sub
transcripts
for
the
the
various
sub-ceremonies
we're
running,
I
didn't
want
to
use
sub-ceremony
everywhere
for
naming
collisions
anyway.
A
That
is,
I
guess,
fairly
consistent.
I
imagine
most
of
the
things
that
were
changed.
There
would
be,
as
you
would
expect,
except
for
one
potential
thing
and
that's
that's.
The
participant
no
longer
calculates
the
so-called
running
product,
because
this
information
is
just
the
the
the
the
latest
g1
point
or
g2
point
from
the
the
contribution.
So
this
was
an
extra
check.
We'd
have
to
perform.
A
A
A
The
way
I
was
trying
to
check
it,
so
I
also
corrected
that
in
the
pr
and
I'll
send
in
a
moment,
I'll
send
a
branch
which
sort
of
just
has
those
corrections
in
case
you
want
to
see
what
they
are,
but
it
turns
out
that
kev
was
already
doing
it
in
a
slightly
different
way,
which
is
basically
what
myfix
does
anyway.
A
So
the
everything
that
was
sort
of
downstream
of
test
rust
implementation
was
consistent
there.
A
So
that's
cool
to
see,
and
then
the
other
thing
that
happened
this
week
was
the
start
of
the
segment
audit.
A
So
they
are
primarily
checking
the
specifications
and
kev's
rust
implementation,
both
for
on
kev's
side
for
sort
of
panics
and
that
kind
of
thing
and
then
more
generally,
for
correctness
and
yeah
they've
done
a
bunch
of
audits
before
for
these
kinds
of
ceremonies,
and
so
they
specialize
in
zk
stuff
so
we'll
see
what
they
what
they
bring
out
of
the
there,
the
ordered
and
yeah.
Those
are
the
major
updates
from
the
spec
side.
Anyone
have
any
questions,
queries
or
comments.
B
A
Yes,
that's
my
understanding
as
well
for
those
listening.
The
reason
kevin
are
a
little
unclear
on
this.
This
wasn't
a
part
of
the
initial
statement
of
work,
but
they
seemed
pretty
keen
to
just
do
this
anyway,
because
they
thought
it
was
sort
of
minor
extra
overhead
and
provides
extra
clarity.
So
I
guess
we're
fairly
thankful
for
that.
Anyway,
too,.
A
Okay,
should
we
move
on
to
kev?
Do
you
have
anything
that
you
want
to
talk
about
from
about
your
breast
implementation
or
the
the
python
reference
implementation.
B
I
do
need
to
upstream
the
change
where
the
the
running
products,
not
in
the
update
proof
just
on
the
api
part,
but
I
was
just
going
to
wait
for
them
to
basically
come
back
with
changes
first,
so
I
can
just
do
it
all
in
one
turn,.
B
Apart
from
that,
I
did
start
to
peek
into
the
part
on
top
of
the
cryptography,
just
because,
like
a
bit
mentioned
it
in
the
when
we
were
doing
the
kickoff
yeah,
I'm
not
entirely
sure
where
we
are
with
that.
So
it'd
be
good
to
get
some
clarification,
I
think
we
could
do
without
a
ui
right
now,
if
you
just
have
a
page
that
just
shows
the
current
srs,
for
example,
just
no
no
javascript
or
anything
just
show
the
html
of
the
srs.
That
would
be
fine
for
us
to
sort
of
start.
B
Looking
at
any
possible
inconsistencies
and
stuff
like
this
yeah,
that's
it
from
my
side.
I
haven't
done
too
much
looking
into
it,
because
I
don't
know
where
we
are
currently
in
terms
of
code
written
for
that.
A
Okay,
I
think
this
kind
of
segues
listening
to
what
jeff's
just
been
doing.
So
I
guess,
can
we
chat
about
that
then
and
then
like?
If,
if,
if
you
have
still
questions
on
that,
then
can
we
give
back
to
kev?
Okay,
that's
this
doesn't
answer
yeah
yeah
jeff.
C
D
C
Especially
ask
him
to
have
a
a
test
harness
that
we
can
really
handle
this
thing
with
testing,
so
he's
working
on
those
things
progressing
that
what
else
have
I
been
looking
at
yeah?
The
design
framework
has
has
moved
on
in
a
bit
their
wireframe.
C
There
are
a
bunch
of
comments
in
that
wireframe
we're
kind
of
having
discussion
in
charlie
the
sigma
document.
So
everyone's
welcome
to
have
a
look
in
there
and
add
comments.
C
A
Okay,
I
I,
I
think,
there's
still
going
to
be
a
little
bit
of
sort
of
misunderstanding
between
kev
and
you
here.
Kev
do
you
have
questions.
B
Yeah,
so
I
guess
what
is
the
api,
because
I'm
sort
of
in
my
head
the
front
end
the
front
end
sort
of
has
a
back
end
as
well.
It's
like
you
have
the
front
end,
which
is
the
ui.
Then
you
have
the
back
end.
C
E
C
And
downloading
and
uploading
the
the
rs
yeah
so
the
back
end.
C
Yeah
yeah
I
haven't,
I
don't
think
I
included
that
in
my
specs.
C
That
is
something
that
coordinators
will
not
coordinate.
Client
implementations
will
need
to
support
right.
B
And
in
terms
of
back
end
for
the
coordinator,
just
to
make
sure
we're
on
the
same
page
like,
for
example,
they
might
have
a
api
endpoint
that
says
add
to
queue
or
something
like
this
or
register
for
queue
like
for
the
coordinator.
C
C
Oh
no,
so
I'm
calling
I'm
calling
out
the
client
api.
F
A
A
The
sort
of
one
one
api,
I'm
not
quite
sure
the
concept
of
the
backend
api
would
be
but
there's
sort
of
one
api,
which
is
what
jeff
wrote
up
in
the
pr.
I
just
linked
in
the
chat,
pi,
15
right
and
that's
just
sort
of
the
that's
basically
do
exactly
what
you
were
just
talking
about,
kev,
which
is
the
like.
There's
a
there's,
an
auth
and
a
join
and
check
it
like
check,
check
in
and.
D
B
C
C
B
B
Sorry,
sorry
I
mean
by
by
the
code
like
if
I
have
the
code
I
could
choose
to
start
a
coordinator
or
a
or
a
contributor.
Is
that
correct?
No.
A
So
I
guess
I
guess
what
might
just
answer
your
question:
kev
is
like
which
repo
would
you
pull
and
what
would
you
run?
What
did
you
build
and
run
if
you're
trying
to
run
a
coordinator
like
if
the
person
running
the
coordinator
is
trying
to
do
this.
B
And
I
guess
additionally,
because
what
I'm
hearing
is
that
there's
one
api.
So
to
me
it
sounds
like
as
a
coordinate
as
a
coordinator,
I
could
call
into
the
api
for
the
contributor
is.
A
B
I
guess
I'm
a
bit
confused
with
a
client.
What's
the
client
api
done,
is
it
just
an
api.
D
B
C
A
v8
the
api
code
is
not
running
at
the
moment.
It's
just
being
developed
in
local
implementation.
C
A
Yeah,
that's
the
yeah.
C
C
A
Okay,
thank
you
because
I
think
one
of
the
one
of
the
things
that
audit
people
are
a
little
concerned
about
is
exactly
like.
How
is
this
used-
and
we
have
this
sort
of
nice
idea
that
the
the
rust
implementation
of
the
crypto
is
isolated
by
the
sdk
et
cetera,
et
cetera,
but
that's
not
necessarily.
A
B
Yeah
I
was
looking
at
some
previous
ceremonies
and
I
think
the
reason
why
I'm
a
bit
confused
of
the
api
is
because
their
setup
is
slightly
a
bit
different,
where
they
sort
of
have.
For
example,
the
coordinator
runs
the
cryptography
and
then
it
has
an
internal
api
and
then
the
front
end
calls
that
internal
api.
B
So
I
guess
the
reason
they
did.
This
is
just
because
they
didn't
want
to
use
wasm.
C
A
B
No
so
the
coordinator
and
those
setups
don't
use
wasm
at
all.
They
use
like
just
rest,
endpoints,.
B
So
the
coordinator
runs
the
the
the
cryptography
natively
and
then,
like
the
front
end
just
calls
whatever
it
needs
from
the
coordinator
by
arrest,
endpoints
yeah.
I
guess
that's
where
my
confusion
was
from.
I.
A
See
it's
not
immediately
obvious
to
me
what
the
benefits
of
sort
of
hosting
that
internally
would
be
like.
Why
do
you
need
a
restful
api
for
that.
B
A
A
B
Yeah,
you
can
call
to
your.
I
guess
you
can
also
make
it
separate
on
a
different
server.
That's
a
lot
faster,
but
yeah.
I
think
you
wouldn't
need
the
rest.
A
Yeah
for
like
the
separate
server
thing
I
could
understand,
particularly
if
you
could
do
like
like
you
host
in
the
cloud
and
there's
a
separate
instance,
which
you
can
gpu
accelerate
or
something
like
that.
But
my
understanding
is
that
hasn't
really
been
the
case.
Is
it
I
I
I
genuinely.
I
don't
know
I'm
not
trying
to
defend
one
choice
or
another.
I
just
don't
know.
B
Yeah
yeah
yeah,
I
don't
actually
know
which
one's
better
either.
I'm
just
saying
what
I
saw.
I
only
started
from
the
plumer
ceremony
when
I
saw
their
setup.
They
sort
of
had
things
in
this
manner
where
yeah
it
wasn't
all
in
one
server
but
yeah
to
what
you
said.
I
don't
know
if
it
doesn't
make
sense
to
have
a
internal
rest,
api
endpoints.
B
C
Yeah,
the
ceremony
was
quite
complicated.
Wasn't
it
in
terms
lots
of
interaction
like
each
client
received
little
chunks
of
work
to
do
or
something
like
that?
Yeah.
B
B
A
C
Yeah
not
not
super
easy,
as
it
currently
is
separate
at
the
repo
yeah.
That's
something
we
talked
about
doing.
C
But
it's
the
implementation
is
tightly
tightly
bound
with
firebase
that
that's
the
difficulty
like
for
just
to
just
set
this
up
as
a
as
a
something
we
could
easily
swap
from
one
coordinator
to
another.
It's
not
it's
not
really
set
up
that
way
at
the
moment,
but
you
know
I
haven't
put
a
real
lot
of
thought
into.
What's
the
best
way
to
go
about
that,
but
we
are
trying
to
disentangle
ourselves
from
firebase
and
that
will
make
it
easier.
A
Okay,
I
mean
I
I'm
not
funny
enough
for
the
code
base
to
comment
on
the
sort
of
technical
challenges
here,
but
just
intuitively.
It
feels
to
me
that
they
should
be
separate
entities,
particularly
from
a
like
audit
or
just
having
people
who
are
running
the
ceremony
themselves,
who
want
to
see
like
what's
happening
under
the
hood.
A
C
C
So
you
really
think
the
reaper
itself,
having
a
separate
separate
repo
for
the
coordinator,
would
be
advantageous.
A
I
I
think
so
like
to
me
ideally
there's
sort
of
the
like
coordinator,
slash
back
inside
of
things
which
is-
and
I
don't
mean
back-end
doesn't
like
website
but
like
api
back-end,
which
basically
runs
everything
up
to
that
and
then
there's
a
separate,
a
separate
thing
which
is
sort
of
the
the
website
which
serves
like
the
server
that
serves
the
the
the
website
to
you.
Yeah
yeah.
C
Yeah
yeah,
so
we've
talked
about
different
ways
of
selecting
inviting
this
repo,
but
we
were
talking
about
having
a
mono
repo,
but
maybe
maybe
we
should
just
totally.
Maybe
I
can
see
your
point.
Maybe
it's
better
to
totally
separate
out
that
server-side
stuff.
A
To
me,
this
is
also
just
a
little
bit
enhanced
by
the
like.
If
you're
going
to
be
writing
your
own
implementation,
then
it's
like
it
makes
sense
not
to
sort
of
be
seeing
this
combined.
But,
like
again,
I'm
not
familiar
enough
with
your
code
base
to
understand
how
reasonable
of
a
request
or
whatever
this
is.
But
I
would,
I
think
it
would
be
nice
to
see.
B
Get
my
understanding
it's
kind
of
naive,
but
I
I
thought
of
I
sort
of
thought
that,
while
doing
the
server
stuff,
the
first
thing
you'd
probably
do
is
the
coordinator
api.
So
no
no
ui
at
all
just
rest
rest,
endpoints
and
the
coordinator
would
just
need
access
to
a
database
to
probably
store
the
queues
of
people
yeah
the
front
end
would
deal
with
the
oauth
stuff.
I
guess,
and
then
the
coordinator
just
needs
to
plug
into
some
cryptography
library
and
then
does.
B
C
C
D
C
The
the
thing
that's
complicated
is
that
the
stuff
that's
under
client,
which
is
the
web
page.
F
C
Tightly
bound
with
firebase
at
the
moment,
so
that's
so
there's
a
lot
of
common
code
in
in,
what's
currently
in
clients.
F
F
C
Rest
calls
so
it'll
be
a
lot
cleaner
at
that
point
and
then
we
will
further.
You
know
clean
up
the
relationship
between
the
back
end
and
the
database.
F
B
And
the
back
end,
the
coordinator
stuff
in
server
are
the
rest
endpoints
being
served
up
by.
Is
it
been
done
by
firebase?
So
I'm
not
actually.
C
C
And
express
node
express
server.
F
B
Right,
okay,
yeah,
that
makes
sense
yeah.
I
was
looking
at
your
code
I
think
a
month
ago,
and
I
think
one
thing
you
may
have
a
problem
with
is
given
a
progress
bar
for
how
long
things
are
taking,
because
the
cryptography,
basically
just
does
everything
in
one
go.
It
contributes
to
every
everything.
C
Yeah
yeah:
that's
right,
yeah,
it's
not
so
important!
In
this
case.
It's
it's
important.
When
you've
got
a
10
or
15
minute
contribution,
it
would
be
nice
to
have
that
progress
bar
there,
and
maybe
we
can
kind
of
fake
it
or
yeah.
I
don't
know
how
we're
going
to
do
it.
F
B
B
A
I
mean
people
are
generally
happy
with
cues
that
take
less
or
things
that
take
less
time
than
expected,
yeah.
So
some
things,
maybe
something
that
says
this-
should
take
no
longer
than
the
current
timeout,
which
I
believe
is
three
minutes.
So
this
should
take
no
longer
than
three
minutes
and
you
can
update
to
sort
of
like
95
or
whatever.
Just
before
you
start
uploading.
The
the
file
back
to
the
coordinator.
A
Maybe,
okay,
I
I
think
one
other
point
just
a
little
bit
on
what
we're
talking
about
before,
which
is
okay.
If
you
said
that
you
think
the
the
oauth
stuff
shouldn't
be
on
the
coordinator
server
side,
and
I
think
I
disagree
with
you
a
little
bit
there,
because
these
are
like
fundamental
to
the
api.
It's
like
how
you
register
yourself
as
a
a
participant.
B
A
Yeah
yeah
all
right,
then
I
think
with
with
that
language.
I'd
agree
with
that
statement.
B
Yeah,
so
the
coordinator
would
still
need
to
do
the
oauth
yeah
and
probably
did
I
think,
we're
using
jwt.
B
Would
it
help
if
I
started
looking
into
these
things,
because
I
think
we're
gonna
need
separate
servers
eventually
separate
coordinators
eventually.
So
I
don't
know
if
it'd
be
helpful,
to
have
some
second
api
for
this
without
the
oauth
stuff,
because
I'm
not
100
familiar
with
oauth.
B
Or,
should
we
just
wait
until
this
code
is
refactored
and
then
so.
B
No,
I
mean
adding
a
coordinator
api.
Would
it
help
if
I
was
to
start
looking
into
this
so
then.
B
It'd
be
the
same,
no
it'd
be
the
same
api.
It's
just
that
it's
just
a
different,
basically
implementation.
A
So
you're
talking
about
a
second
coordinate
implementation.
A
Yeah
I
mean,
I
think
so
right.
It
should
like
basically
up
to
the
the
the
the
the
the
api
that
that
that
jeff
posted
on
the
repo,
the
pr15.
D
B
F
A
So
the
transcript
itself
should
be
sufficient
for
the
cryptography
side
of
things,
but
sort
of
who
has
and
had
like
the
the
state
of
the
queue
and.
F
B
B
A
Yes
and
people
may
be
that,
if
we've
sort
of
banned
from
contributing
or
whatever,
because
they
were
offline,
malicious,
whatever
yeah
so
like
base
paper,
I
mean
a
file
that
sort
of
looks
like
the
a
mapping
from
an
identity
to
some
kind
of
status,
where
we
can
agree
on
a
few
different
statuses.
F
A
C
A
B
A
B
D
A
So
one
of
the
one
of
the
discussion
points
on
the
the
api
or
these
sort
of
the
some
of
the
file
surrounding
it
is
that
jeff
mentioned
that
the
in
the
transcript
we
bake
in
the
identities.
A
This
is
currently
not
something
that
is
done
there,
but
I
can.
I
can
make
those
I
can
make
those
changes
I'll
open
a
pr
for
that.
The
this
is
not
sufficient,
though,
because
the
people
may
have
sort
of
entered
the
queue
and
then
just
missed
their
slot
or
something
like
that,
and
we
still
need
to
keep
track
of
that.
So
this
is
sort
of
a
separate
thing.
We
need
to
export
out
of
out
of.
B
The
the
identities
are
only
needed
for
the
coordinators,
so
does
it
make
sense
to
put
it
in
the
transcript
as
well.
A
Well
so
this
is
this
is
why
I
left
it
out.
Initially,
I
mean
it's
not
really
only
for
coordinator,
because
it's
also
for
warp
sort
of
like
retroactively
checking
who
particip
like
who
participated.
A
C
A
B
A
B
I
think,
probably
in
my
head,
it'd
probably
be
good
to
have
it
somewhere,
but
probably
not
embedded
in
the
transcript,
because
it's
not
needed
to
verify
the
ceremony
so
like
if
you
could
have
like
github
handle
pointing
to
the
public
key
in
some
separate
file
and
then,
if
later
on,
I
want
to
search
up
for
your
github,
handle
it
points
to
your
public
key
and
from
your
public
key.
I
can
then
see
where
you
contributed
inside
of
the
ceremony.
A
I
mean
we
could
make
the
same
argument
for
the
running
products.
Then
right.
B
Is
that
it
is
a
power,
but
you
do
need
a
running
product
in
order
to
do
the
like.
You
need,
because
you
need
it
also
to
be
a
part
of
so
like
at
the
end.
You
get
the
final
srs.
You
need
the
running
products
to
show
the
transition
from
the
first
one
to
the
last
srs.
A
Yeah,
I
agree
with
that,
but
this
this
doesn't
you
don't
need
for
all
the
intermediate
ones,
plus
all
the
the
pub
keys
involved
in
that.
B
No,
I
think
you
do
to
show
the
transition
right
so
to
go
from
the
first
srs
to
the
final
one.
You
need
the
running
products.
A
But,
but
are
these?
Are
these
meaningful?
What
like
outside
of
knowing
identities
like
what
does
it
mean
to
verify
this?
If
you
don't
have
an
identity
that
you're
verifying
it
against
like?
If
you
know
one
of
the
pub
keys
that
you
trust
in
the
list,
then
absolutely
agree
with,
I
agree
with
you.
B
B
I
guess
I
see
those
as
two
different
sort
of
concerns.
The
first
one
is
that
is
this
srs.
Was
it
correctly
transformed
from
the
first
one
to
the
last
one,
meaning
these
are
all
of
the
individual
contributions
and
then
the
second
concern
is:
did
carl
really
contribute
to
this
ceremony.
A
A
A
A
A
It's
like
part
of
this
is
it's
also.
This
transcript
has
many
like
sub
transcripts
so
like
when
this
is
actually
used
when
like,
if,
if,
if
you're,
putting
if
you're
using
this
in
some
other
code,
you're
also
gonna
only
sort
of
look
at
the
sub
transcripts.
There's
like
multiple
ways,
you
can
verify
this
thing,
which
to
me
also
adds
a
little
bit
of
complexity
and
confusion
around
this.
A
Like
are
you
verifying
the
full
transcript
or
you're,
just
verifying
the
the
sub
transcript
you
care
about
for
your
particular
use
case,
so
so
like
ultimately
right
this
could
this
this
srs
goes
into
client
code
and
these
clients
they're
not
going
to
verify
the
whole
thing
every
time
or
whatever.
A
B
That
seems,
like
the
client
shouldn't
be
doing
that
right.
They
should
be
verifying
that
the
final
srs
is
a
correct
was
correctly
constructed
from
this
initial
srs.
With
these
of
these
contributions,.
A
B
Right
right,
yeah,
I
don't
know,
I
still
see
them
as
two
different
concerns
like
the
first
one,
like
with
the
first
one
that
you're
sure
that
the
coordinator
didn't
just
throw
in
some
random
srs
that
has
the
correct
structure.
B
A
B
A
B
So
does
so
if
we
bake
in
the
github
handle,
does
that
mean
that
when
people
are
verifying
like
the
transcript
at
the
end,
they
can,
instead
of
using
the
pub
key
they'll
use
a
github
handle.
A
I
mean
I
like
the
ultimate
identifier
is
still
the
the
pub
key,
but
this
might
give
you
a
reference
point
to
go.
Look
for
someone
right!
That's
that's!
That's
a
little
bit
where
I
think
this
argument
breaks
down
to
me
is
like
in
and
of
itself.
F
B
B
I
guess
we
just
interpret
that
part
as
just
a
blob
of
text
and
we
just
need
contributors
to
basically
write
it
in
some
standardized
format.
So
like
github,
colon,
github,
name,
twitter,
colon,
twitter
name.
B
Right
and
they
should
only
be
able
to
use
specific,
like
social,
social
media
sites,
which
we
write
down
somewhere.
A
The
api
pr
is
discussing
what
what
is
and
isn't
acceptable
as
auth
right,
I
think,
might
be
a
good
next
thing
to
chat
about
a
little
bit.
B
Right
what,
if
I
don't
want
to
put
my
github
or
twitter,
I
want
to
put
some
random.
A
A
B
Right,
but
I
don't
want
to
put
my
off
inside
of
the
the
file-
is,
that
possible.
A
The
the
there's
like
this
weird
trade-off
here
right,
because,
if
you're
going
to
be
completely
pseudo-anonymous
and
like
you
have
no
identity
attached
to
this,
this
pseudonymity
then
like.
What
are
you
adding
aside
for
convincing
yourself
that
is
secure.
B
A
F
A
Like
some
somehow
we're
authoring
you
anyway
and
like
I
can
get
that
you
might
not
want
to
link
this
to
your
twitter
or
your
github.
That's
that's
fine,
but
like
I,
I
you
still
have
some
kind
of
identity
to
us
that
we've
checked
right
and
like
your
contribution,
is
not
particularly
helpful
if
there's
no
identity
at
all
tied
to
it,
like
you
convince
one
person
that
that
you
participated,
I
mean
which
is
nice
like.
F
B
A
B
B
A
I
mean
I'm
like
if
you
have
ideas
on
what
to
expand
this
to
beyond
what
we
have
like.
If
you
have
other
other
other
auth
anti-dos
mechanisms,
then.
B
Yeah,
I
don't
I
don't
actually
know.
I
just
thought
that
people
would
want
to
contribute
anonymously.
B
Yeah
sort
of
anonymously
without
an
ethereum
address,
but
yeah,
maybe
we're
just
splitting
hairs
here
and
because
it
was
just
a
use
case
that
I
thought
up.
That
might
not
actually
be
something
that
people
want
to
do.
E
Sorry
yeah,
so
I
I
didn't
probably
need
to
kind
of
identify
our
primary
target
user.
So
we
did
some
exercise
in
the
like
u.s
part,
so
we
identified
most
of
people
will
participate
this
ceremony,
I'm
kind
of
familiar
with
ethereum,
so
they
will
probably
most
likely
like
me.
I
wouldn't
be
comfortable
to
sign
up
with
my
twitter,
so
I
will
definitely
use
my
ethereal
address
and
nobody
really
know
that.
That's
me,
so
I
think
for
now.
I
think
we're
pretty
okay.
E
C
A
A
So
in
the
interest
of
moving
on
to
to
other
topics,
because
we
have
six
minutes
left
I'll
open
this
pr,
where
we
add
the
sort
of
ids
to
the
transcript
and
we
can-
we
can
discuss
whether
this
there
should
be
a
flag
for
not
not
tying
your
identity
to
it.
And
we
can
discuss
that.
There.
A
Okay,
then
can
can
king
get
an
update
on
what
the
ui
is
looking
like
sort
of
what
the
progress
is
on
that
front
and
how
we
can
like
what's
the
best
way
to
give
feedback
on
that.
E
Yeah,
sorry,
you
you
are,
do
you
mean
the
figma
decide
for
for
the
moment.
E
Sorry
yeah
yeah
yeah,
so
I
I
was
really
looking
like
how
to
medics
experience
magical
because
I
I
find
can
be
very
fun
and
sensor
jeff
kind
of
telling
me
this
is
high
profile.
So
I
would
like
to
people
contribute,
has
this
magical
feeling
and
they
are?
E
They
are
doing
collectible
collective
powering
to
create
kind
of
art
together.
So
maybe
I
can
share
screen.
If
we
have
only
four
minutes,
I'm
gonna
just
quickly
show
you
guys
how
to
browse
my
file.
If
you
can.
D
D
D
A
E
I
have
actually
two
files,
so
this
is
more
like
ui,
figma
figma
and
I
have
another
file
kind
of
like
white
boarding,
so
in
here
kind
of
wrote
down
the
kind
of
user
journey.
So
let's
meet
someone
in
more,
so
we
have
kind
of
like
persona
we
want
to
target
to
and
some
kind
of
precondition
and
user
journey,
since
we
kind
of
feel
it
might
be
ready
around
defcon.
So
we
kind
of
consider
defcon
as
a
special
case
here
so
people
discovered
about
this
ceremony
in
investigative.
E
This
is
safe
whatsoever
and
start
signing
committee
contribution
and
waiting
in
queue
and
also
all
that
so
feel
free
to
have
a
look
around.
So
this
is
kind
of
like
just
can't
imagine
in
each
phases
what
user
is
doing
and
what
they
might
be
thinking,
and
thus
we
know
what's
our
opportunity
to
help
the
experience
and
reduce
the
confusion
so
that
I
will
leave
you
guys
to
see
so
information
wise.
E
I
have
a
couple
of
pages,
I'm
thinking
so
home
page
basically
kind
of
have
an
intro
and
talk
about
what's
this
about
and
why
users
should
contribute
stuff
like
that,
and
we
have
a
dashboard
which
kind
of
showing
the
real-time
contribution
and
a
record
to
to
see
all
the
complete
contribution
over
time-
and
I
have
I
add
this
page-
which
didn't
show
in
the
previous
trust
setup.
So
basically,
if
I'm
contributed-
and
I
remember
jeff
mentioned
about
possible
of
a
pull-up-
will
be
airdrop
or
user
can
claim.
E
So
I
can
come
back
to
clan
here
and
kind
of
see
my
contribution
again.
So,
let's
basic
idea,
so
those
are
kind
of
like
design
thing
you
can
visit
and
visually.
I'm
really
thinking
like.
I
don't
know
if
you
guys
know
about
this
reddit
wall,
I'm
sorry,
I'm
my
laptop.
That
type
is
a
bit
difficult
to
resume.
So
basically
it's
very
blurred,
so
people
kind
of
contribute
to
create
some
kind
of
art
very,
very
powerful
and
yeah.
I
want
to
create
a
bit
of
magic
feeling
into
the
design
whatsoever.
E
So
this
is
one
file.
This
kind
of,
like
all
the
idea
I
dropped
in
this
board
and
then
in
the
the
other
figma
file.
So
here
I
have
this
landing
page.
E
So
basically,
I
kind
of
title
what
what
what's
happening
here
and
a
big
kind
of
lore
nice
paragraph
to
it
to
give
that
vibe
to
the
user
right
away,
and
then
we
kind
of
explain
what's
this
about
and
why
contribute
and
about
this
trust
about
and
also
the
github
link.
So
user
can
learn
more
there's
a
home
page
and
then
user
can
kind
of
open
this
site
menu
for
sure,
see
the
dashboard
record
and
I
haven't
finished
the
sign
in
flow.
E
So
I
right
now
I
only
have
this
option
to
use
ethereum
address.
Maybe
I
need
to
add
a
github
or
a
trader
if
as
an
option,
so
sign
flow
is
not
completed.
Lastly,
I
want
to
show
this
dashboard.
E
So
basically,
the
idea
is,
if
I'm
a
user
come
from
certain
continents,
I'm
based
in
north
america
and
my
sorry.
E
So
I
will
have
some
kind
of
thing
going
on
here
with
x
or
white,
how
to
say
like
drawing
the
dots
or
whatever
and
maybe
yeah
churchill.
Who
left
me
some
comment
yesterday.
I
probably
would
change
this
type
of
type
of
ui
treatment
here.
The
idea
is
really
like
make
users
feel
they
are
part
of
something
and
they
can
visit
all
the
overtime.
So
that's
why
I
have
kind
of
a
play
bar
here.
They
can
see
all
the
progress
happening
and
yeah.
E
So
I
think
this
is
the
area
I
need
to
kind
of
improve.
I
don't
find
it
magical
enough
and
that's
it
I
think
and
draker
I
don't
have
anything
at
the
moment.
So
if
you
come
here
and
there's
a
button
here,
if
you
haven't
used
finger
before
just
take
this
one
and
then
you
can
kind
of
drop
anywhere,
so
I
feel
this
should
be
whatever
whatever
yeah
that's
pretty
much.
It.
A
Okay,
yeah
thanks
thanks
for
sharing
that
that
is
coming
along
nicely.
I
definitely
have
a
few
thoughts
and
comments,
but
I'll
add
that
to
your
work,
there
yeah.
A
Okay,
thank
you.
Everyone
thanks
for
the
call
yeah
I
agreed,
it
does
look
amazing,
the
and
and
and
I'm
really
liking
the
magical
vibes
you're
going
for
there
yeah,
okay,
so
great,
I
guess
from
a
sort
of
where
do
we
take
this
from
now,
the
I
think
I'd
like
to
check
chat
a
little
bit
more
async
with
you
kev
about
a
second
implementation
or
just
what
what
that
could
look
like.
A
I,
I
think
I'd
like
to
do
another
round
of
feedback
or
two
on
the
api
that
that
you've
been
working
on
there
there,
jeff
and
and
maybe
open
like.
Let's
encourage
some
like
more
public
contribution
in
terms
of
how
we
are
authoring
people
and
what's
what's
the
criteria,
your
various
accounts
need
to
meet.
A
Yeah,
I
think
that's
that's
it
from
my
end.
Does
anyone
else
have
any
interest
any
stuff
that
they'd
like
to
raise
quickly
before
we
terminate
the
call.
B
E
Yeah,
that
would
be
very
helpful.
Thank
you,
yeah.
I
was
not
very
sure
who
I
should
kind
of
collaborate
on
the
front
end
part
so
yeah
you
will
be
very
helpful.
Thank
you.
A
On
that,
on
on
that
topic,
charlie,
do
you
that's
also
not
quite
sure
how
to
pronounce
your
name?
What
time
zone
are
you
in?
I
think
it
might
be,
might
be
helpful
to
do
a
ui
sort
of
discussion
or
call
where
we
can.
We
can
dig
into
these
things
a
little.
E
I'm
bit
in
eastern
time,
north
america,
not
new
york
time,
okay,.
A
A
Fantastic
thanks
all-
and
I
guess
I'll
see,
see
everyone
on
the
the
discord
and
telegrams.