►
Description
The Baseline Protocol team takes you through the code of the v0.1 update.
Previous video: https://youtu.be/lsZQwiE2glA
Next video: https://youtu.be/0vXoSb5bVks
Go to https://baseline-protocol.org for more information.
A
B
A
B
What
you're
talking
about
is
that,
once
you
have
once
you
have
when
you're
setting
up
once
you've
got
a
work
group
you're
going
to
set
up
your
work
low
right,
which
is
a
set
of
of
logical
steps
between
these
companies
and
in
order
to
do
that
under
in
in
do
that
on
chain
under
zero
knowledge,
you're
going
to
have
to
run
a
setup.
Is
that
correct.
A
It
is,
and
so
we
have
this
izk
snark
circuit
provider,
which
is
the
interface
for
that.
You
know
that
we
see
to
be
very
standard
for
creating
vk
circuits,
regardless
of
what
front
end
and
back
end
you're,
using
whether
that's
like
socrates
and
bellman,
or
something
else,
you
should
be
able
to
use
this
interface
interchangeably
with
zero.
You
know
zk
snark
circuits,
and
because
of
that
you
know
so
like,
for
example,
the
example
app
has
a
method
called
deploy,
work
group
and
what
that
method
does.
A
A
It's
a
one-liner
to
get
to
get
back
the
the
trusted
setup
artifact,
which
is
the
which
is
an
identifier,
a
uuid.
Basically,
that
is
used
in
a
protocol
message
later
and
also
within
the
the
the
circuit
registry.
If
you
will
to
keep
the
the
key
pair
itself
and
then
the
solidity
source
code
for
the
verifier
contract.
So.
B
Once
you
call
in
context,
this
is
all
so
it's
important
for
for
everybody
to
know
that
what's
happening
is,
and
this
is
for
the
j.
So
the
first
thing
you
would
do
you're
setting
up
the
work
group
second
thing
is
you're
you're
going
to
have
you're
going
to
either
use
a
generalized,
the
generalized
socrates
or
or
zero
knowledge
circuit,
which
is
effectively
just
hey
everything's
the
same.
B
You
know
it's
a
consistency,
check
or
you're
going
to
have
some
more
sophisticated,
zero
knowledge
circuits
that
you're
going
to
want
to
set
up
already
set
up
for
this
particular
workflow.
This
particular
application
right
so
step
one
get
together
with
the
companies
you
want
to
get
together
with
step,
two
decide
whether
you
want
just
consistency,
machine
or
something
more
or.
B
Right,
okay,
so
yeah
like
in
the
radish
demo,
we
have
a
master
service
agreement
circuit
that
has
more
business
logic
in
it
than
just
consistency,
so
you
would
set
all
that
up
first
and
then
you
would
run
what
you
just
described:
right,
yeah
yeah!
All
this
is
so
that
we
can
basically
do
this
this.
This
confirmation
of
consistency
on
chain
with
under
under
zero
knowledge
and
privacy.
A
Yeah
and
I
think
this
will
extend
really
nicely
to
other
other
use
cases-
it's
very
it's
application
agnostic,
so
you
know
it'll
scale,
I
think
quite
well.
Karthik,
you
know
have
been
working
with
him
on
theorizing,
a
design
on
how
to
make
how
to
make
these
become
chainable,
and
so
we
have
a
very
generic
one
up
front,
and
then
we
can
maybe
look
we're
looking
into
how
to
chain
that,
with
other
with
additional
circuits.