►
From YouTube: The Baseline Protocol - July 2022 General Assembly
Description
The monthly General Assembly meeting of the Baseline Protocol open source standards body community.
https://baseline-protocol.org
Agenda:
1) Outreach [01:00]
2) Sponsorship [08:40]
3) Core Devs [09:06]
4) TSC Updates [11:30]
5) Grants [13:17]
6) Standards [30:26]
6) Open Floor [32:29]
7) Requirements Deep Dive [39:55]
B
Hello,
everybody
and
welcome
to
our
july
baseline
general
assembly,
where
we
will
go
through
our
updates
from
the
community,
and
today
we
will
go
through
outreach
updates
sponsorship,
core
devs.
The
tsc
and
roadmap
updates
grants
where
we
will
have
some
grant
recipients,
give
us
an
update
on
their
work
and
hopefully
a
demo
as
well
then
standards,
and
then
we
will
have
an
open
floor.
B
So
with
that
I
will
first
hand
over
it
to
mark
cattle
to
give
the
first
of
our
outreach
updates.
C
Okay,
well,
the
first
of
we've
been
working
on
within
the
outreach
team
and
we've
kind
of
split
into
a
couple
of
little.
You
know
side,
work
groups
and
dedicated
on
you
know
basic
research
as
well
as
market
updates.
As
far
as
you
know
how
this
would
you
know,
you
start
to
put
together
a
a
solution
stack
around
baseline
and
to
that
event,
you
know
to
that
point:
we're
also
covering
different
events.
We
have
been
approved
as
a
speaker
for
the
fintech
devcon.
C
That's
gonna
be
held
in
denver,
the
23rd
through
the
26th
of
august,
and
we
are
added
to
the
main
stage.
Our
time
slot
is
at
1,
40
p.m.
On
that
thursday,
the
26th
so
we're
still
putting
together
a
lot
of
behind-the-scenes
work
on
that,
but
really
good
to
have
this
type
of
this
region
and
exposure
for
baseline
I'll
be
giving
the
the
talk
so.
C
This
and
the
thing
about
fintech
devcon
is:
they
are
very
adamant
about
that.
This
is
education
heavy.
This
is
not
really
a
place
for
sales
pitches,
where
everybody's
trying
to
talk
about
how
every
their
product
is
better
than
everybody
else's.
This
is
all
this
is
these.
Are
you
know,
processes
and
techniques
that
we
use
to
advance?
C
You
know
different
technologies
and
baseline
has
been
very
enthusiastically
received
so
also
upcoming
events.
Oasis
is
gonna,
have
a
booth
at
black
hat
in
august
and
they're
going
to
be.
You
know,
really
representing
oasis
and
the
suite
of
their
open
products,
projects
which
baseline
is
one
of
the
one
one
of
the
key
ones
there.
C
They
also
have
some
upcoming
gartner
conferences
and
we're
really
starting
to
distill
down
where
we
can.
You
know
find
out
where
we
can
have
the
most
impact
for
for
baseline.
So
you
know
watch
this
space
to
see
how
we
go
forward
and
then,
of
course,
you
know,
the
we've
also
applied
for
speaking
slots
for
the
big
devcon
in
october,
which
is
that
in
new
york.
C
Bogota,
oh
that's
right,
bogota
colombia,
yeah
so
applying
for
speaking
slots
on
that.
Still
you
know
putting
together
a
lot
of
the
submission
materials
and
stuff
there.
So
we
will
see
how
that
moves
forward.
But
you
know
it's
it's.
You
know.
C
We've
been
really
excited.
You
know
to
be
selected
for
this
fintech
devcon
in
denver
in
august.
So
that's
what
we've
got
going
on
right
now.
Awesome.
B
We
did
a
lot
of
digging
beforehand
to
find
a
resource
similar
to
this,
for
our
own
materials
that
we're
creating
and
have
not.
So
that
is
why
we
are
moving
forward
to
fund
our
own
within
the
baseline
community,
and
we
hope
this
report
will
be
complete
by
the
end
of
the
year.
So
far
we
are
on
track,
so
we'll
continue
providing
updates
on
the
idc
report.
B
Another
outreach
item
is
a
discussion
we
recently
had
was
about
new
member
onboarding
and
some
updates.
We
can
do
to
the
website
to
have
a
really
solid
landing
page
for
new
members
that
are
directed
to
our
site,
because
we
are
creating
new
stickers
and
collateral
with
a
qr
code
to
our
website
for
our
events
coming
up
this
year.
So
we
want
to
make
sure
we
really
address
what
people
are
looking
for
when
they
enter
our
website
and
also,
I
will
hand
over
to
mark
rimza
for
some
updates
on
our
work
groups
within
the
outreach
team.
D
Thank
you
yeah
mark
mentioned.
There
are
a
couple
work
groups
going
on
right
now.
The
first
one
is
the
research
work
group.
We
we
meet
every
other
week
and
we're
working
right
now
on
a
group
effort,
which
is
the
alternative,
baseline
solutions
matrix
where
we're
comparing
and
contrasting
various
services
and
protocols,
some
of
them
included,
are
edi
trusted
third
parties,
value-added
networks.
D
If
they're
interested
in
that
and
the
questions
this
person
would
ask
like
how
does
this
impact
my
existing
infrastructure
and
this
matrix
is
going
to
be
used
as
a
reference
for
what
resources
still
need
to
be
created
within
the
appropriate
lens
of
the
personas
that
we're
targeting
for
the
protocol
and
we
hope
to
get
some
good
deliverables
out
of
this
in
the
future,
and
on
top
of
this,
our
group
is
working
on
a
master
enablement
deck
that
can
be
used
to
highlight
the
overall
value
proposition
of
baseline
using
data,
and
we
hope
to
share
this
deck
in
the
future
on
a
future
baseline,
show
and
publish
it
on
the
website
and
another
deliverable
that
started
is
a
business
executive,
brief
brief,
and
this
will
ideally
become
a
one-pager
also
for
business
executives
whenever
they're
making
the
decision
to
implement
baseline
or
not
and
I'll
pass
it
back
over
to
sonal
to
talk
about
sponsorship.
B
B
Alrighty-
and
I
will
cover
sponsorship
quickly,
carol
guyer
from
oasis
is
unavailable
for
the
call
today,
but
the
outreach
team
is
working
on
increasing
baseline
sponsorship
by
connecting
with
companies
related
to
the
technologies
or
uses
of
baseline.
So
we
are
working
on
a
prospects
list
and
carol
is
reaching
out
to
these
companies
explaining
the
protocol
and
why
they
should
be
interested
and
I
will
hand
over
to
yoaf
for
a
core
dev
update.
A
Yeah,
thank
you
sono.
So
the
major,
I
guess,
piece
of
development
that
the
core
devs
are
working
on
right
now
is
the
simple
reference
implementation
or
the
sri,
which
is
kind
of
the
main
focus
of
the
road
map
for
the
the
end
of
this
year.
A
So
this
is
currently
being
developed
by
a
team
of
core
devs
that
meet
weekly
they've
split
the
work
into
the
initial
phase
of
five
separate
components
being
zk
bpi,
subject
and
account
work,
groups,
messaging
and
storage.
A
A
Tomorrow,
I
believe,
is
that
meeting
where
they
can
provide
input
and
everybody
can
decide
how
to
move
forward
and
once
that,
once
that
meeting
concludes
and
everybody
is
able
to
get
their
proposal
approved
by
the
rest
of
the
group,
efforts
will
begin
to
implement.
So
that's
where
the
real,
the
real
development
work
will
kind
of
kick
off
to
track.
All
of
that
there
are
issues
that
have
been
already
opened
in
the
baseline
repo,
which
is
public
for
anybody
to
see
where
we're
at
and
moving
forward.
A
That's
where
we'll
keep
track
of
everything
we'll
be
opening
issues
as
well
as
grant
requests
for
anything
relevant
to
you
know
big
enough
pieces
of
work,
that's
worthy
of
requesting
a
grant
for,
and
that
way
the
tsc
can
also
keep
track
of
where
the
roadmap
progress
is
being
made.
A
Finally,
the
last
thing
I
wanted
to
mention
is
that
one
of
our
core
devs
vibhov,
who
is
on
this
call
and
will
kind
of
get
a
chance
a
little
bit
later
in
this
call,
is
working
on
the
baseline
calendar
still,
which
is
a
blip
that
originated
from
the
amster-based
bounty
hunt
event,
and
so
I
think,
a
little
bit
later
in
this
call
he'll
get
a
chance
to
demo
what
he
has
so
far,
which
is
I'm
excited
for.
E
Thank
you
and
thank
you
so
much
mark
and
you
are
mark.
I
think
I
think
it's
it's
it's
it's
hearty
to
listen
to
all
these
updates,
and
especially
on
the
on
the
on
the
monthly
channel
assemblies.
Amazing
work
is
going
into
into
building
baseline
as
it
stands.
E
We
are
definitely
looking
for
more.
So,
as
the
tfc
I
mean,
I
think
I
think
I
can
just
on
the
behalf
of
the
psg
is.
Thank
you
guys.
First
of
all,
keith
I
saw
your
recent
proposal
on
the
on
on
accountability
of
all
proposals
which
are
coming
in.
I
think
that's
amazing,
how
detailed
you
know
how
it
should
be
captured,
so
that's
cool
and
then
on
the
specifically
on
the
psc
updates.
E
First
thing,
very
importantly,
we've
hit
mid
of
the
year
july
is
like
the
second
half
and
then
so.
We
should
be
focusing
on
dispersing
all
the
grand
money
that
we
have
so
once
again
request
for
all
do
participate
in
the
grant
proposals
and
and
do
do
chime
in
you
know
if,
if
you
can
bring
in
any
sponsors,
nothing
like
it,
you
know
the
bigger
the
pool
the
more
opportunity
we
have
to
build
this
thing
better.
E
So
that's
all
from
my
side,
anything
that
I
missed
or
not.
D
B
Yes,
me
too,
we
can
use
your
help
there
as
well
awesome
all
right
and
we
will
move
into
grant
updates.
So
one
of
our
grant
recipients-
boy
who
is
working
on
the
website
maintenance
was
unable
to
join
us
today,
but
the
outreach
team
is
working
with
him
on
a
second
iteration
of
the
website,
with
updates
to
the
ui
ux
designs
and
overall
messaging.
So
if
anyone
on
call
or
listening
would
like
to
be
interested
in
this
effort,
please
join
us.
B
We
need
some
creative
minds
on
this
and
then
also
we
have
vaibhav
with
us
today,
who
is
a
baseline
core
dev
working
on
the
calendar,
grant.
Thank
you
for
joining
us
five
buff
and
over
to
you
to
give
us
an
update
and
a
demo.
F
Yeah
yeah,
so
as
I
yeah
so
I
would
like
to
first
of
all
tell
that
baseline
calendar
is
going
on
good,
so
the
basic
idea
was
to
create
a
calendar
like
calendly,
like
application,
which
would
allow
people
to
schedule
appointments
in
such
a
way
that
protects
their
privacy,
and
I
will
go
ahead
and
quickly
share
my
screen.
E
G
F
F
F
I
will
just
log
in
so
in
order
to
log
in
yeah.
Just
give
me
a
second
yeah,
so
in
order
to
login,
I
need
to
create
this
signature
which
is
based
on
this
is
basically
metamask
signature.
F
Yeah,
basically,
I
would
have
to
sign
it
wait
just
a
second.
F
So
so
I
am
signing
one
time
nonce,
and
so
the
current
nonce
would
be.
F
F
F
Given
the
right
beer
token
is
presented,
so
these
two
and
yeah,
so
the
request
is
for
scheduling
an
appointment
so
once
I
would
have
to
go
ahead
and
create
another
user,
and
it
will
also
create
time
availability
for
that
specific
person,
and
then
I
I
just
match
the
time
availabilities
and
yeah,
so
that
is
also
done
over
here
and
yeah
yeah.
F
So
this
specific
part
is
kind
of
a
small
part.
Is
the
scheduling
part
is
appointment.
Part
is
left
just
the
post
api.
Apart
from
that,
everything
is
just
done
from
the
time
appointment
scheduling
is
still
pending
and
the
circum
circuit
is
what
I'm
working
on.
B
F
The
front
end
part
would
be
the
next
stage
of
this
and
just
finishing
the
appointment,
api
and
the
front
end
part.
H
Actually,
I
have
a
question,
so
what
was
the?
What
was
the
the?
Can
you
maybe
like
reiterate
the
two
things,
a
reiterate
sort
of
like
the
the
the
the
basic
idea
behind
it,
because
people
who
are
watching
might
not
be.
You
know
intimately
familiar
with
that
and
then.
Secondly,
what
was
sort
of
like
the
most
challenging
thing
you've
encountered
so
far.
F
Okay,
so
there
are
two
things
like,
so
there
are
two
aspects,
so
the
idea
was
that
let's
say
that
person
a
is
available
on
three
things.
So
three
specific
time
schedules
and
person
b
is
available
on
three
different.
Three
different
time
schedules
say:
8
30
to
9
9
32
10..
So
the
idea
was
not
to
give
the
entire
availability
of
person
a
to
person
b
when
he
has
to
suppose
it
supposed
to
schedule
an
appointment
with
him.
F
That's
what
the
difference
between
this
and
so
what
the
idea
was
to
use
zk,
circom
circuit
and
hide
the
information.
Obviously,
the
statement
here
would
be
that
the
person
can
go
ahead
and
use
this
system
to
brute
force
for
every
time
availability.
But
then
there
would
be
certain
trust
that
you
would
have
to
establish
while
you're
giving
the
link
to
someone
so
over
here.
What
I'm
doing
over
here
is
that
anyone
who
goes
ahead
and
registered
on
the
website
would
go
ahead
and
give
their
the
few.
F
There
would
be
a
pop-up
on
front
end,
and
that
would
give
so.
This
is
the
back
end,
which
I
just
showed
on
the
front
end.
F
There
would
be
a
pop-up
where
it
would
go
ahead
and
display
different
to
different
to
different
time
slots,
so
nine
to
nine
thirty,
nine
three,
two
ten
something
like
that
and
the
person
would
go
ahead
and
select
five
or
ten
of
these
time
slots
when
he's
available,
and
that
would
register
in
the
database
and
the
same
thing
would
happen
with
the
other
person
and
the
matching
part
would
happen
by
a
circum
circuit
in
order
to
see
if.
F
Yeah,
so
in
order
to
see
whether
those
are
available
or
not
so
yeah-
that's
about
it.
So
these
are
the
so
the
idea
is
to
protect
the
privacy
of
the
person
who
is
sharing
their
calendars.
F
That
was
the
basic
idea,
and
the
most
challenging
aspect
of
this
was
largely,
I
think,
understanding
how
circum
circuit
works
and
like
just
understanding
how
zk
can
be
used
in
this
application
was
like
kind
of
challenging,
because
it
was
very
new
to
me.
H
What
was
the,
what
was
the
idea
behind
using
circum
in
particular,
and
not
any
other
library.
F
Well,
so
the
like
a
lot
of
examples
like
the
baseline
protocol.
I
looked
at
the
battleship
as
a
reference
to
my
work
like
the
battleship
code
that
has
been
already
written,
and
I
was
able
to
understand
that
very
well.
So
I
just
yeah,
I
I
found
sircom
quick
to
learn
and
understand.
At
the
same
time,
it
served
the
purpose
that
was
needed
over
here.
H
Excellent
great
example
of
how
how
you
know
previous
work
is,
is
being
utilized
in
in
in
the
work.
So
it's
it's.
It's
just
a
proof
that
how
important
these
type
of
efforts
are.
B
A
B
Alrighty,
so
with
that,
I
will
quickly
go
through
the
rest
of
the
grant
updates,
so
we
do
still
have
two
open
rfps
for
the
digital
asset
wallets.
We
have
one
open
grant
request
for
the
first
rfp,
that's
being
discussed
with
the
tsc
and
the
requester
at
this
time,
and
we
are
encouraging
those
who
want
to
make
a
valuable
contribution
to
the
blockchain
ecosystem
to
make
a
request
for
this
work,
so
we
can
get
it
accounted
for
as
soon
as
possible
in
this
year.
B
Any
further
comments
on
that
andreas
and
the
two
rfps.
H
Speak
sure
we've
we've
already
put
it:
we've
already
put
that
on
on
on
twitter
linkedin
people,
we,
those
are
very
important
pieces
of
work
because
they
allow
you
to
do
two
things
number
one.
They
allow
you
to
be
compliant
with
the
with
the
with
the
standard
for
this
for
a
non-custodial
solution
between
bits
and
so
integrating
the
ids
and
and
verifiable
credentials
and,
on
the
other
hand,
eddsa
signatures
or
keys
are
super
important
because
they're
utilized
in
the
zero
knowledge
circuits.
H
As
well
and
I
have
an
inkling
that
enterprises
are
not
really
keen
on
third
parties
managing
their
private
keys,
so
it
is
badly
needed
not
only
within
the
baseline
community,
but
in
the
blockchain
community
at
large
and
the
ef
is
very
keen
on
this
being
done
and
yeah.
So
we
we
call
out
golf.
H
It's
like
there's,
there's
stuff
out
there
that
already
exists
that
you
can
build
on.
That
is
that
is
relatively
straightforward.
To
do.
H
Knowing
understanding
how
ditson
vc's
work
be
familiar
with
with
some
of
those
implementations
that
exist
out
there
from
from
from
company
like
open,
bazaar
and
transmute-
and
you
know
it's
like
be
familiar
with
with
what
what
the
work
that's
being
done
in
the
decentralized
identity
foundation
and
on
the
one
hand,
the
other
hand,
you
know
it's
like
no,
no,
no,
no
js
right
just
like
because
because
any
any
current
open
source
digital
asset
wallet
relies
on
that
and
then
for
the
other
grant
yeah
you
will
have
to
understand.
H
You
know
edds
a
signatures,
even
though
there's
there's
a
lot
of
implementations
already
out
there
that
you
can,
you
know,
steal
from,
and
it's
just
putting
things
together,
putting
stuff
together
that
already
exists
in
one
solution.
So
it's
it's!
It's
you
don't
have
to
really
build
anything
from
scratch.
B
Awesome,
thank
you,
and
the
last
grant
update
is
that
we
have
two
other
grant
requests
in
the
queue
by
the
same
grant.
Recipient
one
is
for
hosting
the
baseline
show,
going
forward
to
line
up
speakers
and
topics
as
well
as
do
follow-up
after
the
show
to
those
who
join
us
and
the
second
one
is
for
conducting
research
around
the
protocol.
So
we'll
work
directly
with
the
research
work
group
and
hopefully
those
grant
requests
will
be
updated
and
approved
in
the
coming
weeks
and
last
but
not
least,
would
be
our
standards
updates.
H
Sure,
thank
you
give
me
give
me
sorry,
I'm
I'm
I'm
I'm
doing
multiple
things.
At
the
same
time,
I
apologize
it's
unfortunate,
but
that's
my
life
yeah,
so
standards
centers
update.
There
is
still
one
pr
out
there
calling
on
john
walper
to
look
and
approve
part
of
your
job
wink
wink
that
has
that
has
sort
of
like
the
final
editorial
additions
to
the
to
the
to
the
draft,
and
so
that's
that's
one.
The
other
is
that
work
coming
out
of
the
sri
is
there's.
H
There
will
be
issues
a
new
issue
and
then
subsequent
pr
on
the
api
standard,
so
which
is
great,
because
people
are
now
starting
to
look
at
that
as
well,
which
is
which
is
which
is
awesome.
You
know
there
was.
There
was
a
there
was
a
a
very
much
hot
needle
effort
and
you
know
was
sure
that
things
were
were
to
be
missed,
and
now
that
is
born
out.
So
this
is
awesome
that
we
have
you
know,
onion
and
and
and
and
stuff
on
and
so
forth.
B
Alrighty
so
really
quickly,
we
will
have
an
open
floor
and
then,
with
the
remaining
time,
we're
officially
going
to
do
the
segment
that
has
been
discussed
in
the
past
on
going
through
singular
requirements
and
the
standards
and
talking
through
it
and
seeing
what
questions
we
have
and
just
discussing
each
standard
that
exists
and
we'll
see
how
many
years
it
takes
us.
B
E
I
have
I
have
an
update
on
the
baseline
india
show,
so
we
are
going
to
be
hosting
the
hyperledger
gang
tomorrow
on
the
baseline,
show,
india
and
yeah
I
mean
I
don't
have
complete
yet,
but
I
have
60
who
will
be
joining
us
tomorrow.
So
I'm
going
to
be
posting
on
social
media
as
well
very
soon
so
and
if
you
were
interested
to
join
in,
please
do
it's.
I
know
it's
pretty
early
in
the
us,
but
still
to
try.
H
So
I
have
one
one
additional
update,
which
is
a
really
positive
one.
The
w3c
I
did
core
spec
was
approved.
The
objections
by
google,
mozilla
et
cetera,
were
overruled,
and
the
did
spec
is
now
an
official
w3c
specification,
which
is
a
big
big
thing,
because
now
this
is
an
official
standard.
Together
with
with
the
fair
public
credential
standard
is,
is
the
foundation
for
for
for
everything
going
forward
around
being
able
to
tie
identities
to
to
digital
assets
in
a
in
a
way.
H
It's
required,
no,
it
does
not,
per
se
require
require
a
blockchain
for
security
reasons.
You
would
want
to,
because
you
need
to
have
a
provable
sequence
of
used
keys
right.
That's
critical,
yeah.
G
That
have
missed
coming
down
on
this,
or
are
they
weighing
in
at
all.
H
G
H
They
have,
they
have
a
they
have
a
they
have
a
a
a
competition
ongoing.
That's
now
in
the
final
round
for
the
for
the
algorithms
to
be
selected
that
are
considered
to
be
post,
quantum
secure,
which
is
going
to
be
a
a
big
d.
Big
deal
b
is
gonna
spur
a
lot
of
work
and
spending
in
the
it
industry,
because
you
have
to
change
everything,
and
I
mean
everything.
G
G
The
most
exciting
thing
I've
read
recently
is
that
mongodb
just
published
queryable
encryption,
meaning
that
you
can
search
at
high
speeds
of
production,
scales
and
they're
just
putting
out
the
open
source
and
demo
of
this
tomorrow,
or
maybe
it
was
tuesday
that
allows
you
to
basically
query
data
sets
without
decrypting
them
quickly
and
and
at
scale.
This
is
a
big
deal.
In
fact,
I
really
could
have
used
this
years
ago
when
I
was
running
the
innovation
exchange.
G
You
know
where
we
had
data
sets
from
many
different
companies
and
we
wanted
to
find
various
things
between
them,
but
we
couldn't
expose
the
data
sets
to
each
other
very
exciting
and
and
relevant
to
to
what
we
do
here.
H
That's
correct.
It's
like
if
you're
the
the
key
question
is,
is
like
it's
like
it's
like:
what's
the
what's
the
what's
the
provenance
of
your
of
your
encrypted
records?
Again,
it's
it's
a
question
of
of
of
of
of
your
root
of
trust.
That's
all.
G
G
Applications
don't
care
that
much
about
super
heavy-duty
non-repudiation
protocols
where
you
know
there's
just
no
way
to
you
know
spoof
it.
If
I'm
querying
your
database-
and
I
know
you
know-
I'm
fine
right
so,
but
I
love
the
idea
that
again,
if
it
were
talking
about
orchestrating
multi-party
automations
without
exposing
data
which
is
to
me
the
most
interesting
and
important
thing
about
baselining
these
days
is
yeah.
That
is
very
much
aided
by
something
like
that
with.
G
If
you
could
do
that
right,
because
then
you
can,
you
can
make
a
query
from
one
state
machine
to
the
other
without
exposing
the
data
and
say
well,
I
need
to
know
that
this
happened.
I
need,
I
need
to
you,
know,
be
able
to
search
this
date
range
for
something
without
without
have
without
requiring
the
other
party
to
reveal
the
data
to
me
in
clear
text.
Big
deal.
B
All
right,
so,
let's
go
through
a
standard
requirement.
Super
super
fun
all
right,
so
we're
gonna
go
through
all
the
requirements
in
order
just
so,
we
can
keep
track
of
where
we
are
how
many
requirements
are.
There
is
my.
B
B
One
transacting
counterparties
must
have
an
agreement
specifying
minimally
the
transactions
to
be
performed
between
the
transacting
counterparties
before
a
transactable
state
of
an
agreement
can
be
instantiated
within
a
bpi
note
that
an
agreement
in
the
context
of
this
document
may
or
may
not
be
a
commercial
agreement,
as
defined
in
requirement
number
24
commercial
agreements
below
all
right.
So
can
we
talk
about
what
this
means
or
what
questions
we
have
about
this
requirement
and
I
will
paste
it
in
chat
as
well.
H
B
A
A
A
H
Sure
so
you
know
so
we're
we're
already
at
in
2.3.
So
there's
some
stuff
that
you
know
it's
about
talking
about
counterparty
right,
so
transacting
counterparties
are-
or
you
know,
alice
and
bob
right
there
that
trying
to
to
to
make
it
very,
very
specific,
there's,
alice
and
bob,
and
they
must
have
an
agreement
right.
So
an
agreement
has
they
they
have.
They
have
agreed
on
rules
right
and
they
need
to.
These
rules
need
to
specify
minimally,
so
at
least
one
rule,
the
transaction
to
be
performed
between
them
right.
H
So,
if
I'm,
if
alice
pays
bob,
there
must
be
an
agreement
that
says
alice
pays
bob
when
x
is
true
right.
When
you
know
it's
like
alice,
has
received
the
good
from
bob
and
confirms
it
right.
That
is
before
a
transaction.
Transactable
state
of
an
agreement
can
be
instantiated
within
a
bpi.
That
means,
if
you
want
to
do
something,
if
you
want
to
implement
that
that
logic
in
the
bpi,
such
that
your
your
baseline,
your
baseline
implementation
based
on
protocol
implementation,
can
use
that
logic
right.
H
H
A
Yeah
we
get
this
question
a
lot.
You
know.
How
do
you
in
your
mind?
Imagine
these
parties
and
parties
going
about
really.
You
know
coming
to
an
agreement,
of
course
that
parts
kind
of
obviously
didn't
already,
but
then
taking
that
from
you
know
making
the
agreement
to
like
a
codified
version
of
it.
H
Yeah,
so
that's
the
art
right,
that's
that's!
How
how
you,
how
you,
how
you
translate
the
the
the
agreement,
the
logic,
the
business
logic?
That's
that's
encoded
in
there
and
words.
Typically
how
that
is
translated
to
to
to
typically
a
constrained
within
within
a
zero
zero
zero
knowledge
circuit.
H
Right
so
that
that
how
do
you
implement
that?
And
on
the
one
hand,
on
the
other
hand,
it
also
then
specifies
what
type
of
data
needs
to
be
stored
or
needs
to
be
made
available
in
terms
of
to
agree
what
a
state
is
right.
H
So
what
is
the
state
you
know
in
this
in
our
example
prepayment
and
then
post
payment
right,
because
because
you
might
have
yet
another
payment
happening
because
there
was
a
yet
another,
you
know
exchange
of
goods
between
alice
and
bob
right,
and
that
might
so
it's
it's
not
necessarily
a
one-off
right.
You
very
often
have
the
situation
where
you
have.
You
know
long-running
contracts
that
basically
say
the
same
thing
and
that
runs
over
a
year
or
two
or
three
and
you're
processing.
H
You
know
hundreds
of
of
of
commercial
transactions
through
that
agreement
right,
which
means
you
need
to
be
able
to
keep
track
of
of
all
the
states.
You
know
so
one
builds
on
builds
on
top
of
the
other
right.
So
it's
it's
a
very
foundational
thing,
not
only
for
one-off
situations,
but
for
for
you
know,
it's
like
long-running
contracts
or
agreements.
A
So
what
do
you
think
the
process
will
look
like
in
real
life
when
we
get
a
large
amount
of
parties
coming
together?
You
know
they,
they
have
an
agreement
and
they
decide
to
put
it
into
code,
and
then
they
all
have
to
like
sign
off
to
say
yeah
this
this,
what
we've
codified.
This
is
what
we
all
agree
on.
You
know.
That's
just.
H
H
You
have
you
know
you
have
the
you
have
the
actual
users
they
have
to
sign
off
on
yep,
that's
it
and
then
there's
there's
going
to
be
a
test
right
that
you
define
on
around
that
that
that
business
users
can
can
check
that.
Oh
yep,
that's
it
for
that
expected
input
for
this
input.
This
is
the
expected
outcome.
Yep
that
works
all
good.
G
On
the,
I
would
say
that,
on
the
when
you
get
into
commercialization
of
this
notion,
it
becomes,
wouldn't
you
say,
andreas
more
published
rules
right,
so
he's
you
you,
you
don't
have
to
de
novo
set
that
rule
up.
Every
time
you
can
say:
hey,
look
you're
coming
into
our
orbit,
you're
going
to
be
doing
this
thing.
Watch
for
this
location
on
the
blockchain
on
this
ccsm
and
and
here's
the
rule.
You
know
you
have
to
test
for
right.
G
G
Just
yeah
to
your
api
yeah,
you
could
say:
here's
your
api
and
whether
you
implement
this
in
dids
or
or
in
traditional
api.
You
could,
you
could
say
you
know,
here's
the
here's,
the
set
of
requirements,
there's
a
rule
set
and
here's
the
circuit.
H
G
So
that's
that's
how
I
think
it
would
be
practically
applied
most
of
the
time
as
opposed
to
like
you
know,
calling
back
and
forth
between
two
or
three
counterparties
to
say:
hey,
we're
all
going
to
agree
on
that
alice
is
going
to
do
this
then
bob's
going
to
do
this
charlie's
going
to
do
this
right.
G
You
can
say
you
know
any
charlie
can
come
in
and
say:
hey
I'm
new
charlie.
I
need
I
need
to
be
sure
that
alice
and
bob
the
new
alice
and
bob's
did
these
things
that
they
have
consistent
information
that
the
part
of
that
information
adheres
to
this.
To
this
requirement
you
know
x
is
bigger
than
y,
and
if
so,
then
I
will
do
my
thing.
A
I
couldn't
got
some
burning
questions.
C
Not
questions
just
just
some
input.
I
think
this
is
really
great,
because
I
think
I
I
do
a
lot
of
requirements.
Writing
and
I
did
in
the
past
quite
a
bit
on
counterparty.
So
so
that's
really
give
you
like
a
good
gives
you
a
very
good
path.
I
mean
actually
writing
the
detailed
requirements
or
the
contracts
between
the
counterparties.
C
G
C
G
Yeah
this
reminds
me
boris
of
back.
You
know.
In
the
early
days
of
baselining,
I
was
very
keen
to
see
open
law,
which
is
was
still
open
law
in
those
days
and
not
you
know
dows
and
laos
and
stuff,
which
you
know
obviously
was
a
good
pivot
for
them.
They
made
a
lot
of
money,
but
you
know
open
law
and
and
clause
were
both
going
after
this
idea
of
of
sort
of
docusign
meets
instrumentable
agreements
right
and,
and
the
clause
actually
was
bought
by
docusign.
G
A
friend
of
mine,
dan
selman
ran
that
and
they
he
got
bought
good
for
him.
But
I
haven't
seen
a
lot
since
then
about
this,
but
I
still
think
that
that's
probably
how
this
happens
in
the
future
right
or
and
that's
how,
if
I
was
building
something
right
now
that
needed
this
I'd,
be
one
I'd
want,
basically
to
have
a
docusign.
G
Have
the
back
end
of
that
docusign
have
instrumental
code,
a
smart
contract
or
circuits
be
rendered
into
circuits
so
that
I
could
then
just
simply
sign
the
docusign
and
agree
to
the
both
the
human
language
agreement
and
the
circuit
requirement
right
and
then
and
then
implement.
As
I
will
right
with
an
api
and
the.
H
H
G
H
G
On
their
their
roadmap.
H
G
Well,
yeah
generate
it
would
generate
the
actual
code.
You
know
the
the
the
executable
part
of
the
contract.
If
so-and-so
does
this,
then
so-and-so.
G
Couldn't
and
then
to
interpret
that
into
zero
knowledge
circuit
would
be
the
next
step,
and
that
could
all
be
one
single
workflow.
H
Oh
yeah,
I
mean
yes,
but
that's
that's
like
that's
like
it's.
It's
that's
that's
to
to
to
to
parse
to
parse
commercial
agreements
is
un
unless
they're,
plain,
vanilla
and
and
translate
that
into
into
implementable
ckp
circuits
that
that's
a
that's
a
very,
very,
very
long,
leap
yeah
about
dsls.
G
B
Okay,
awesome
well,
thank
you
for
that
discussion
and
thanks
for
talking
us
through
that
requirement
super
fun.
We
got
through
one
and
that's
honestly
what
I
expected,
but
this
was
an
awesome
general
assembly.
Thank
you
to
our
viewers,
as
well
as
those
on
the
call
with
us
today,
and
we
will
see
you
next
week
on
our
baseline
show.