►
From YouTube: The Baseline
Description
The weekly office hours for the Baseline Protocol open source community. Learn more at https://baseline-protocol.org.
A
All
right,
hi
everybody,
it's
john
walter
here
with
the
baseline
protocol,
and
here
we
are
once
again
with
our
esteemed
panelists
and
and
conversationalists
about
talking
about
the
baseline
protocol.
If
you
go
to
baseline-protocol.org,
you
will
learn
all
that.
You
need
to
know
about
baseline
protocol,
which
is
not
a
coin,
not
a
not
a
platform,
not
a
product,
not
a
what
does.
I
always
say,
not
a
not
all
those
things,
it's
a
standard.
It's
a
thing.
A
It's
a
design
pattern
or
making
sure
that
you
can
that
your
system
of
record
and
your
counterparty
system
of
record
are
in
a
state
of
synchronicity
using
blockchain
as
a
as
a
not
as
a
database,
but
as
a
message
bus.
So
with
that,
it's
great
to
see
everybody
we're
gonna
make
this,
I
think,
a
pretty
short
day
or
a
short
time.
We
do
this
every
wednesday
morning,
us
eastern
at
10
a.m
or
every
every
noon
wednesday.
A
Us,
eastern
and
we've
we've
had
a
request
to
start
one
up
in
in
time
zones
that
are
friendly
to
india.
So
I'm
I
was
very
excited
about
that
and
the
person
that
stood
up
on
that
I'm
hoping
we'll
follow
through
that
would
be
really
cool
to
have
one
of
those.
It
would
be
a
major
expansion,
lots
of
cool,
great
news
coming
about
baseline,
but
right
now
we
want
to
make
sure
that
anybody
is
tuning
in
here
knows
to
dump
us
now
and
go
right
over
to
the
erinston
young
event.
A
That's
happening
right
now
and
if
somebody
can
put
that
in
chat,
so
you
know
so
you
can
get
registered
over
there.
That
would
be
great,
but
you
know
we
we
don't
want
to
break
our
our
perfect
run
on
the
show.
A
I
think
this
is
our
maybe
55th,
I
don't
know
I
gotta
I
gotta
go
and
do
an
actual
count,
but
we've
done
a
lot
of
these
and
we've
done
one.
I
think
every
single
week
since
we
started
you're
over
a
year
ago.
So
it's
good
to
see
everybody
thanks
for
coming
over
here.
I
know
more
than
a
few
of
you.
You
know
jumped
out
of
the
ny
to
come
over
here.
Let's
all
jump
back
as
soon
as
possible.
There's
some
really
interesting
events.
Nick
you've
been
tracking
it.
B
Get
off
mute
today,
it's
all
about
public
finance
and
public
finance
management.
You
know
the
days
seem
to
be
organized
lately
around
kind
of
option,
so
public
finance
friday's
a
technology
day
et
cetera,
so
lots
of
good
content,
lots
of
great
speakers
and
it's
all
available
through
the
web
and
they
charge
very,
very
nominal
heat-
to
join
virtually
literally
nothing.
A
You
mean
to
to
to
start
using
ops
chain
or
to
oh,
you
mean
to
to
get
to
join
the
conference.
Yes,
free
conference
yeah,
you
think
it'll
it'll
be
free
when
they,
when
they
run
in
vegas
again,
you
know
or
wherever
they
you
know.
Whenever
we
go
live
again,
you
think
it'll,
the
the
little
state,
of
course.
B
B
C
C
So,
nick
and
john,
are
you
guys
doing
the
nft
proof
of
attendance.
A
C
I
did
I
did.
I
did.
B
A
From
me
you're
a
collector
yeah,
I
never.
I
never
did
it.
I
I
don't
know
I
just
I
couldn't
figure.
I
mean
I
just
yeah.
Okay,
I'm
not
going
to
make
any
comments.
I
mean
dude,
you
are
going
to
wallet.
C
C
B
Over
the
last
24
hours,
many
of
the
exchanges
have
been
having
technology
issues
right
with
the
market
doing
what
it
is,
and
you
know
obviously
people
the
volume
of
trading
is
probably
going
up
as
people
are
trying
to
either
consolidate
their.
C
Positions
or
what
have
you
get
buy
more
or
what
have
you
so
so,
if
you're,
using
an
exchange-based
application.
A
Hey
we're
getting
we're
getting
a
sound
yeah
yeah
folks
are
saying
that
the
sound
is
is
light
again,
so
let
me
very
quickly.
Yep
levels
should
be
okay,
oh
I
know.
What's
going
on,
oh
yeah,
all
right
that
should
be
okay.
Can
somebody
do
a
sound
check,
go
off
and
make
sure
so.
A
All
right,
yeah,
it's
the
it's,
the
it's
the
yeah,
it's
I'm
choppy
too,
so
everybody
hold
on
for
a
second.
B
D
D
B
D
Like
like
nft,
that's
actually
pretty
pretty
pretty
cool
they,
they
they're
one
one
one
proof
for
600
000,
minted
nfts.
They
they
did
last
month
so
which
was
actually
pretty
cool,
so
they
they're
they're.
They
also
did
did
the
the
reddit
bake
off
challenge
and
they
also
had
had
also
did
did
like
600
000
transfers
in.
A
Cool
crazy,
so
we
got
a
lot
of
folks
on,
but
you
know,
as
I
said,
we'll
say
it
again.
The
ernst
young
global
blockchains
summit
is
happening,
live
right
now,
over
at
ernst
young's
channel,
we
put
the
the
link
in
chat
and
it's
pretty
easy
to
find
under
any
circumstances,
so
go
ahead
and
get
over
there
lots
of
really
good
stuff
and
nick.
Why
don't
you
go
ahead
and
do
that
again?
What
for
folks
that
couldn't
hear
you?
What
is
the?
B
Well
there,
if
you
look
at
the
agenda,
oh
all
up
right,
it's
certainly
giving
you
ey's
perspective
on
the
enterprise
blockchain
market,
which
is
always
very,
very
pointed
and
very
timely,
and
then
each
day
kind
of
follows.
Some
of
the
modules
within
ops
chain
and
today
is
public
finance.
Fridays
are
all
about
technology
and
scalability.
B
There's
actually
a
session
later
today
about
complex
business
processes
on
the
blockchain
and
smart
contracts
with
karthik
one
of
our
buddies
here
in
the
community.
So.
A
One
of
the
original
folks
that
designed
the
baseline
protocol,
so
that's
great
yeah
and.
B
And
they
just
posted
the
replays
from
day
one.
So
if
you
missed
it,
you
can
go
back
and
see
john
and
kyle
and
and
many
of
our
friends
talking
about
the
the
power
of
the
baseline
protocol
and
defy
enterprise
d5,
which
is,
as
you
know,
a
market
that
we're
very
fond
of.
A
Yeah
yeah
there
was
some
really
good
stuff
on
the.
I
think
the
worst
thing
from
yesterday
was
was
wolpert's.
Actually,
I
have
to
say
I
thought
it
was
my
worst
ever.
You
know
monologue
and
I'm
kind
of
getting
sick
of
my
monologue.
So
I
gotta
get
some
new
material,
but
yeah
it
was.
It
was
just.
I
was
kind
of
droning
on
about
blockchains
being
bad
databases.
Everybody's
heard
it
before
so
yeah.
A
It's
all
that
ballet
dancing.
You
know
practice.
A
Okay,
so
what
have
we
we
we
have
been?
We
can
do
one
of
two
things
right
now.
We
can
kind
of
I'll
ask
this
of
our
youtube
studio
audience.
You
know,
shall
we
jump
over
to
ey
and
call
it
a
day
here
or
shall
we
do
a
little
bit
of
talking
about
the
road
map,
as
we've
been
doing
last
few
weeks,.
D
So
I
have
a
question
really
and
that
has
to
do
with
like
data
and
storage,
primarily
storage,
right.
A
D
And,
and
and
and
the
orchestration
so
so
so
off-chain
data
is,
is
it
like?
I
do.
We
think
that
is
it's.
It's
a
requirement
that
the
that
the
that
all
off
chain
data
needs
to
be
partially
persistent,
which
means
write
ones,
read
many.
B
D
I've,
let
me
rephrase
it
it.
The
data
staff
chain
data
store
is
is
is,
is
append
only.
D
A
No,
but
why
why,
because
the
whole
point
is
to
say
yeah,
you
know,
certainly
at
the
admin
level
I
should
be
able
to
mess
with
that
data
right.
It's
a
it
is
a
database,
not
a
blockchain
right.
If
we
need
it,
if
we
wanted
the
respective
databases
to
be
locked
down.
First
of
all,
I
don't
know
how
you'd
enforce
it
and
second,
you
know
just
use
a
blockchain
right
and
and
and
then
you've
got
the
isn't
it
funny
how
computer
science
is
always
a
game
of
whack-a-mole
right.
A
C
A
A
Thing-
and
you
know
in
terms
of
inventory,
I
was
quite
impressed
by
the
way.
Don't
let
me
get
too
orthogonal
here,
but
I
was
impressed
with
the
ey
demonstration
on.
I
thought
it
was
pretty
cool,
at
least
the
the
ey
demonstration
of
ops
chain
managing
inventory
and
quote
unquote
tokenizing
it.
Although
paul
was
quick
to
point
out
that
in
their
quote-unquote
tokenizing
they're,
not
putting
any
data
about
that
inventory
on
chain
in
any
way.
So
that
was
good.
A
I
didn't
know
exactly
how
they're
doing
that,
and
they
did
say
that
they're
supporting
the
baseline
protocol,
but
I
haven't
seen
the
actual
code
behind
that
to
know
what
what
that's
about
but
the
but
it
you
know
that
looked
pretty
cool,
so
I
guess
maybe
we
could
maybe
that's
what
the
marketers
will
do
is
start
calling
baselined
records
tokenized.
A
D
You
mean
what
why
why
why
I
throw
out
that
question
well,
first!
Well
for
once
right!
It's
like
it's
like
if
you,
if
you
think
of
it,
if
you,
if
you
think
of
a
of
what
are
the
the
audit
requirements
right,
it's
like
if
I
want
to
change
something
right,
think
about
how
you're
doing
it
in
in
in
an
erp
system.
Today,
right,
you're,
you're,
you're,
you're,
doing
a
correcting
journal
entry
right,
you're,
you're,
you're,
nixing
out
the
wrong
and
then
you're
entering
the
right
right
yeah.
D
B
D
D
A
there's
a
mean,
there's
a
mean
thing
behind
my
behind
my
behind
my
my
question
and
there
there's
there's
not
a
straightforward
answer
because,
but
I'm
I
was
more
provocative
in
a
way
to
to
to
get
people
thinking
about
about
about
the
requirements
around
data
malleability
and
yeah.
A
A
The
the
original
record
needs
to
be
changed,
and
you
know
you
can
do
that
today,
but
we've
been
talking
about
how
to
make
it
easier
better
in
v1
and
and
then
somebody
else,
I've
been
bringing
this
up,
but
I
was
on
a
call
with
a
prospective
client
and
they
brought
this
up
without
without
even
being
prompted
that
they
that
it's
very
important
that
to
them
that
if
somebody's
data
does
get
changed
out
of
band
or
out
of
off
base,
you
might
say
ooh
off
base.
A
See
that's
where
well,
if
only
I
knew
sports,
so
the
so
it
changing.
You
know
if
you
change
that
there
is
a
an
argument
that
a
compliant
system-
and
I
think,
andreas
this
kind
of
falls
down
the
path
of
what
you
were
talking
about
a
compliant
system.
Do
you
want
to
be
able
to
say
this
compliant
system
you're
out
of
compliance?
If
you
make
a
change
that
is
off
base,
that
is
it's
no
longer.
A
You
know
that
record
is
no
longer
able
to
pass
its
shot
with,
with
the
baseline
proof
should.
Should
you
have
to
inform
the
other
counterparties
or
counterparty
that,
depending
that
that
that
you
are
no
longer
inconsistency
right
now
you
you
can't
there's
there
are
times
when
standards
can
tell
you
you
have
to
you.
Should
you
have
to
do
that
you'd
be
out
of
compliance,
there's
nothing
technically
that
we
can
do
to
prevent
you
from
messing
around
with
your
own
database.
A
You
could
actually
pull
the
plug
on
the
server
and
the
whole
database
is
offline
right.
You
know
you
can
do
that.
That's
the
whole
point
is
we're
not
trying
to
do
hard
cons.
You
know
we're
not
doing
a
consensus
algorithm
across
a
bunch
of
traditional
databases,
we're
simply
making
sure
that
properly
running
databases
are
have
records.
That
can
be
said
to
be
consistent
and
if
they
are
not
consistent,
you
know
who's
wrong.
D
A
But
should
you
be
polling
is
the
question
they
they
brought
up
and
it
was
the
one
I've
been
bringing
up
and
I'm
this
might
be
signal
bias
because
I've
been
bringing
it
up,
but
I
was
like
I
was
struck
by
somebody
cold.
You
know
bringing
it
to
me,
you
know
bringing
it
up,
never
heard
me
say
that,
and
I
was
like.
D
But
still,
if
you
do,
if
you
cannot
generate
a
valid
proof,
then
I
on
the
other
side
or
my
my
multiple
personalities,
don't
really
care
right,
because
it's
if,
if
you
want
to
change,
if
you
want
to
propose
a
state
change
right,
you
need
to
you
need
to.
You
need
to
generate
a
valid
proof
that
your
new
proposed
state
object
is
in
compliance
with,
with
with
what
we've
already.
A
Yeah,
when
you
get
to
the
next
work
step,
the
point
that
they
were
making
is
that
they,
they
they've
in
the
real
world,
experienced
terrible
trouble
with
the
systems
that
they've
been
dealing
with
because
they
get
out
of
sync
long
before
then,
and
it's
a
mess
by
the
time
they
catch
it.
So
they
want
they
want
much.
They
want
to
know.
C
C
So
if
I
have
an
internal
set
of
procedures
that
yield
an
outcome
which
is
interesting
to
the
baseline,
but
but
not
all
the
three
steps,
then
my
data
is
going
to
mutate
up
until
the
point
where
it
hits
that
next
workflow
hydration
and
says
yes,
this
is
where
it
picks
back
up,
and
this
is
where
the
proof
gets
interesting
again.
But
before
that
happens,
I
don't
want
all
that
memorialized,
because
it
could
be
a
hundred
steps
of
noise
to
get
to
that.
D
Is
indeed
true,
so
so
think
of
it
like
a
swim
line?
Diagram
right,
the
only
thing
that's
relevant
for
for
the
for
for
for
baseline
is
the
is
is.
Is
the
data
that's
on
the
attached
to
the
arrow
that
goes
from
from
from
from
an
internal
to
an
external
swim
lane?
That's
that's
pretty
much,
that's
pretty
much
it,
and
that
should
be
a
commercial
document,
because
otherwise
you
you
will
run
into
into
legal
trouble.
D
C
D
A
contract
boundary
is
represented,
as
as
your
as
your
as
your
state
objects,
right
and
and
and
there
and
and
how
that
state
evolves
by
by
by
adding
by
adding
multiple
commercial
documents.
On
top
of
that
right
and
and
and
your
your
your
your
think
of
it,
you
know
it's
like
you
know
as
a
tree
and
you're,
adding
all
these
documents
and
the
and
the
the
the
tree
changes
and
evolves
over
time.
D
D
You
can
pull
you
can
you
can
you
can
take
a
copy
of
whatever
you
have
and
you
can
you
can
sync
it
up
and
then
your
you
run,
your
whatever
you
run
on
your
side
of
the
of
the
of
the
with
the
the
the
baseline
protocol
instance.
Boundary
is
entirely
correct
to
you
right.
It's
like
it's
like
you.
Can
you
can
you
can
you
can
put
a
piano
around
your
neck
and
and
if
that
suits
you,
I
I
don't
care
right.
D
What
what
I
do
care
about
right
is
is,
if
you
are,
if
you're,
trying
to
actually
actively
change
the
the
the
state
the
agreed
upon
state
right,
but
if
you
need
to
right
change
the
state
of
an
object
that
is
like
you
know
in
the
past,
right
for
whatever
legitimate
reason
right.
You
make
that
as
a
state
change
proposal,.
D
That
that
allows
you
to
to
to
you
know,
revert
certain
state
items
as
long
as
you
have
agreed
upon,
and-
and
it's
been
codified,
that
hey
guys,
we
actually
need
to
think
about
what
happens
if
we,
if,
if
something
changes
well.
A
A
I
mean
I,
you
know:
there'll
probably
be
more
clauses
out
there,
but
right
now,
they're,
the
one
that
I
think
about,
especially
since
open
law
has
kind
of
gone
into
the
world
of
eloy
laos
claus
is
the
one
that
I
think
about
when
saying
I
want
to
have
a
human,
readable
contract,
and
I
want
to
then
turn
that
contract
into
machine
business
logics
that
then,
can
be
converted
into
in,
at
least
in
some
cases,
into
zero
knowledge
circuits
and
go
into
the
baseline
process
right.
A
So
that
would
be
you
you
want
to
put
that
in
there
from
a
contracting
perspective,
but
regardless
of
that,
you
want
in
the
business
logic
and
I'm
looking
at
sam
and
ryan
and
the
other
technical
folk
on
the
on
the
call
dhruv,
especially
dhruv
you'd,
want
to
be
able
to
say
I'll,
be
pleased
when
I
start
seeing
this
in
implementations-
and
we
should
be
talking
about
this-
on
the
standards
committee
andreas
and
on
the
in
the
maintainers
team.
A
As
we
decide
what
goes
into
v1
this,
this
this
topic
keeps
on
coming
up.
Who
gets
the
ball?
Who
gets
to
make
the
change
right?
You
know,
nick
it's
it's
back
to
row
level,
locking
for
all
of
us
right
and
oracle.
You
know
what
what
what
kind
of
approximation
of
that
kind
of
locking
business
and
and
permission
to
change
do
we
want
to
implement
in
sam's
original
design?
A
A
Well
say
you
did
have
one,
though,
that
it
was
that
you
needed
the
data
insurance.
That's
certainly
true,
and
I
like,
where
lucas
has
been
going
with
that
idea
right.
You
know
you
just
you
kind
of
anchor
the
top
of
the
workflow
in
the
bottom
of
work
or,
and
you
have
these
exit
points
for
the
workflow
and
then
you
string,
the
you
know,
sub
workflows
together
right
so
you'd
say
so.
You
didn't
have
to
every
single
work
step
doesn't
have
to
necessarily
be
on.
You
have
a
proof
on
chain.
A
C
A
A
They
need
to
be
able
to
say
in
fact,
even
a
contracting
system.
I
remember
in
the
early
days
of
open
law.
People
were
like
well.
I
can't
use
this
right
now
because
it
doesn't
have
a
a
way
of
of
allowing
us
to
make
changes
three
four
five,
a
hundred
times
before
we
all.
Finally,
you
know
lock
in
this
is
even
more.
You
know
this
is
it's
been
baseline
but,
subsequent
to
the
baselining,
somebody
noticed
that
the
record's
wrong.
A
C
I
guess
in
order
to
to
perhaps
nullify
an
agreement
or
restructure
an
agreement
in
a
multi-party
situation
like-
and
this
is
hypothetical
I
mean
if
you
look
at
kona
and
if
you
are
trying
to
set
up
a
you-
know,
multi
multi-party
agreement
on
on
on
certain
kind
of
certain
number
of
supplies
or
certain
quality.
You
know
certain
dates
of
you
know.
Delivering
one
party
can't
do
that
or
one
or
two
parties
can't
comply
with
that
and
they
want
to
renegotiate
that
delivery
date.
C
How
would
would
you
is
that
sort
of
an
out-of-band
negotiation
and
then
within
the
system,
baseline
system,
and
then
that
says:
okay,
now
I'm
going
to
let
you
change
I'm
going
to
offer
the
change
of
ownership
in
order
to
change
the
terms
I
mean
I
I
didn't
quite
get
that
so.
The
the
the
problem
closing
here
is:
what
is
the
criteria
of
the
change
of
ownership
and
what
are
the
conditions
under
which
and
a
change
of
ownership
happens,
and
how
does
it
happen?.
A
In
this
case
ownership,
isn't
I
mean
you
know
you
can
own
an
invoice?
You
can
own
a
bowl
of
lading,
but
you
don't
really
think
of
owning
an
rfp
or
another
kind
of
document
right
so
but
the
you
could
use
the
ownership.
This
was
sam's
original
design.
You
used
the
ownership
designator
in
the
contract
to
to
decide
who
got
to
make
changes
to
the
array,
and
it's
an
older
design,
we're
using
that.
A
But
I
keep
on
thinking
about
it,
sam,
because
it
gives
me
kind
of
clarity
on
the
problem
at
a
high
level
so
but
bottom
line.
You
know
what,
whatever
methods
you're
using
there
needs
to
be
a
way
of
indicating
who
gets
to
initiate
a
change,
and
I
I
we
we
did
a
little
research
can't
find
a
case
where
more
than
one
counterparty
needs
the
right.
At
the
same
time,
it's
always
one.
A
C
A
Yeah
yeah,
whether
whatever
mechanism
you
use
yeah
somebody's
got
to
be
able
to
say
yep,
I'll
change
it
and
whether
that's
a
conversation
out
of
band
or
I
mean
like
if
I
was
writing
an
ar
a
baseline
to
a
ip
system.
I
would
also
set
up
a
like
a
chat
system
so
that
I
could
you
know
like
be
live
chatting
with
my
counterparty.
C
That
would
make
sense,
because
then
you
could
essentially
catch.
You
know
sort
of
just
baseline,
the
the
discussion
and
say,
based
on
this
discussion,
the
the
the
ownership
was
assigned
to
this
particular
individual.
C
C
A
D
Yes,
it
is
of
course
section
we
we,
we
like
we
like
haggled
over
that
that
that
stuff
about
authorization
and
delegation
and
and
and
and
agreement
section
2.4,
if
I,
if,
if
memory
serves
me
yeah.
A
My
internal
memory
is
off
base.
Apparently
us.
A
Would
you
do
us
a
favor?
Do
me
a
favor
andreas?
Could
you
bring
that
that
clause
up
sure,
maybe
referencing,
I
think
it's
it.
Well,
it's
not
public.
Is
it.
C
Yeah,
I
I
do
so
sitting
here
looking
at
this
in
a
real
world
scenario
and
stuff,
and
so
if
I
make
a
change
to
a
baseline
workflow
say,
I've
got
to
change
last
minute,
give
an
additional
discount
because
of
competitive
environment,
or
you
know
whatever
and
everything
I
have
to
I'm
now,
no
longer
baseline.
A
Something
and
you
just
you
know
you
change
it
and,
and
it's
not
you
haven't,
you
haven't,
run
through
whatever
appropriate
procedure
to
get
everybody
on
the
same
page,
again:
okay,
right,
then
yeah
then
you're
out
of
then,
then
you
were
inconsistent
with
the
proof
exactly
you're
going
to
fail.
The
proof
somebody
says
hey
who's
right
about
this,
but
we
don't
want
to
get
it
to
that
point
right.
We
don't
want
to
get
to
the
point
where
somebody
has
to
go
into
a
dispute
and
run
proof
proofing.
A
You
want
to
be
able
to
say
yeah
we're
all
you
know.
If
if
somebody
goes
off
then
I
know
it.
C
Right
so
something's
off
I've
got
to
reproof
and
stuff.
Do
we
have
the
mechanism
so
that
those
successor
proofs
are
managed
that
we
still
have
okay
previously
baseline?
We
went
off
base,
we
debased,
we
went
baseline
false
now
we
have
redone.
Do
we
make
sure
that
we
still
have
that
unbroken
continuity.
A
A
And
rebasing
is
a
is
a
work
in
progress
in
the
standards
committee.
We
had
an
argument
about
it,
the
other
last
week
or
two
weeks.
I
have
an
argument,
meaning
a
respectful.
A
D
Then
I
can
shh
not
quite
yet
nope.
Someone
needs
to
enable
me
nope.
D
A
I've
been
I've
been
an
your
enabler
for
a
long
part,
two,
no
I'm
just
kidding,
and
that
should
work.
Thank.
A
B
A
D
It's
it's
all
good.
Am
I
good
all
right?
Okay
cool,
so
this
is
section
2.42
commercial
documents-
I'm
not
going
to
go
through
that,
but
it's
like
it's
like.
So
it
talks
about
commercial
documents.
Commercial
state
object
to
be
transacted
on
must
be
based
on
a
specific
commercial
document.
Commercial
document
must
be
derived
from
a
legally
binding
contract.
A
commercial
document
must
be
represented,
as
an
electronic
record.
Commercial
document
must
be
represented
on
a
bpi
between
the
counterparties,
commercial
document,
bpi
being
a
baseline
protocol
instance.
A
A
Didn't
we
made
that
this
is
in
the
case
of
a
commercial
document,
as
I
recall,
we
made
that
argument
right
that
this
is
only
in
the
case
of
it.
It's
not
like
you
have
to
do
that
for
every
baseline
event,
but
it.
But
it's
saying
that
it
should
that
baseline
event
be
involved
in
a
commercial
and
legally
binding
document.
D
A
This
is
important
andreas,
but
I'm
not
drawing
a
connection
between
this
and
what
we
were
just
discussing
about
debasing
and
rebasing
that
you
you
have
the
same
problem,
regardless
of
whether
it's
a
commercial
document
or
not
we're
talking
about
we're.
Just
talking
about
hey
I've.
I've
got
a
record
and
we've.
A
A
commercial
document-
let's
just
say
I
you
know
the
the
message-
the
record
is
hi
and
you're,
and
I
need
you
and
I
both
have
the
word
hi
in
our
databases.
There's
no
commercial
document
there,
it's
not
a
legal
situation.
It's
simply
that
we,
for
whatever
reason,
want
to
make
sure
that
we've
baselined
the
word
hi
in
our
respective
databases
and
and
then
you
change
it
from
high
to
hello.
A
C
Okay,
so
the
value
prop
of
the
whole
baseline
thing
is
basically
aligning
the
two
parties
that
don't
want
to
share
any
other.
You
know
sensitive
data
and
stuff,
we
want
to
say
well,
one
side
has
made
a
change.
The
other
side
needs
to
be
aware
of
it
and
by
you
know,
all
of
a
sudden.
If
you
go
back
to
you,
know
the
workflow,
it's
going
to
come
up
baseline,
false
are
you
know,
it's
no
longer
done
so.
Yeah.
A
C
D
No,
the
point
is,
you
cannot
finalize
a
state
change,
let
let's
be
really
really
clear.
This
is
entirely
the
it's
it's
the
requirement
is
and
the
state
it
needs
to
be
entirely
deterministic,
which
means
and
and
requires
agreement
from
all
from
from
all
counterparties,
right
that
that's
that's
in
there
and
at
the
at
the
pr
that
I'm
currently
working
on
on
the
agreement
execution
there
is,
there
is
a
that
is
flowing
through
the.
Where
am.
C
A
Right
so
you
know
from
the
user
experience
perspective.
I
need
to
be
able
to
have
an
instrument
that
says
all
right.
Oh,
I
don't
have
the
right
to
change
this
one
right
now.
You
know,
but
I
need
to
right,
but
at
the
same
time-
and
so
how
do
I
get
the
ball.
C
A
It
may
not
cure
costs
if,
if
we
employ
the
method,
that
lucas
was
talking
about
where
we're
chaining
or
you
know,
he's
calling
an
entanglement
from
one
work
step
to
another.
You
you
may
not
go
on
chain
for
any
of
those
changes
also
necessarily
depends
on
where
it
is
and
what
what
the
purpose
of
it
is,
but
even
if
it
were,
if
it's
going
on
l2
is
probably
you
know,
rounding
error
so.
C
A
A
D
So
you
can,
you
can
go
through
that
and
just
the
the
blue
ones
here
are
strictly
around
the
agreement.
Agreement
execution,
I'm
just
I'm
just
finishing
up
the
the
I'm
just
finishing
up
I've.
I've
done
everything.
I'm
now
here
on
store
on
storage
and
then
I
need
to
write
the
state
management
and
that's
that's
it
and
the
pr
is
ready.
I
hope
to
do
that
today
and
then
I
can
I
can
I
can.
I
can
push
that
out
there.
D
There
is,
however,
already
in
the
in
the
in
the
we
have
it.
When
we
talk
about
the
bpi,
let's
do
the
lesser
dlt
same
liveness,
functional
requirements,
commercial
counterparties.
C
Guys,
I'm
going
to
need
a
drop,
but
I
would
say
for
the
next
baseline
that
we
definitely
have
yeah.
D
A
Yeah,
I've
brought
it
up
a
bunch
of
times
that
one's,
certainly
in
the
list
of
stuff,
and
so
you
know
in
as
we've
discussed
by
you
know
june
in
the
june
you
know
first
half
of
june.
We
want
to
have
taken
we're
going
to
lock
down
sort
of
new
proposals
unless
something
really
urgent
comes
up
and
try
to
get
it
all
into
the
work
cycle
for
v1
in
june
sam
I'm
looking
at
you
on
that
and
right
and
that's
we've
discussed
that
so
we're
gonna.
A
D
So
these
are
the
these:
are
the
relevant
things
right?
What
you're,
what
about
about
changing
things
right
so
22
through
20,
20,
27
right,
so
counterparties
must
validate
the
correctness
of
a
of
a
state
object
based
on
a
parenthesis.
State
change
against
the
transaction
business
logic,
logic
in
the
applicable
bpi,
workflow
and
workshop.
A
D
I
think
the
counterparties
must
generate
the
proof
of
correctness
of
a
state
object
based
on
on
a
in
parentheses
commercials,
so
state
change
that
can
be
validated
against
the
bpi
transact
transaction
business
logic.
Any
new
state
between
counterparties
must
be
recorded
on
the
bpi
between
them.
Any
counterparty,
having
received
a
proof
of
correctness
of
a
state
change,
must
be
able
to
validate
that
proof
of
correctness
against
the
bpi.
D
A
All
looks
right
but
that,
but
I
think
that
the
the
the
new
point
or
the
p,
the
point
for
rebasing
and
debasing
is:
should
there
also
be
at
least
one
more,
perhaps
two
more
counterparties
should
you
know,
use
your
language
but
I'll
say
keep
an
eye
on
the
the
state
of
of
their
local
data
versus
the
proof,
and
if,
at
the
time
of
you
know
they
fail
the
pro
you
know,
the
shah
then
must
or
should
they
inform
the
counterparties.
A
I
think
it's
cut,
probably
a
should
in
this
case,
because
there
may
be
lots
of
examples
of
cases
where
maybe
many,
where
counterparties
just
don't
care
and
don't
want
to
implement
that.
But
you
know
that's
that's
really.
What
what's
being
brought
up
here?
Andreas
is.
A
D
Nothing
going
on
no
one!
No
one
cares
because,
because,
because
the
counterparties,
I
don't
care,
if
you
have
issues
with
your
erp
system,
you
cannot
send
me
anything
that
is
not
aligned
with
with
with
with
what
we've
agreed
upon.
You
cannot.
I
know
right
because
because
you
so
so
I
don't
care
what
you're
doing
on
your
side,
if
you're,
if
you,
if,
if,
if
you're,
screwed
up
you're
screwing
up,
I
don't
care
that.
A
D
No
because
their
experience
was
they're
sending
us
and
then
we
incur
liability,
because
because
because
someone
someone
someone
fat
fat
finger,
something
the
point
is
you
can't
even
send
to
people
that
incurs
a
liability
because
because
you're?
Because
the
system
will
not
allow
you
to
it's,
it's
not
possible
right.
So
it's
like.
D
B
Let
me
give
you
an
example:
you're
you're
shipping,
a
box
to
a
from
a
manufacturer
directly
to
a
customer,
you
baseline
between
the
manufacturer,
who's
shipping,
the
box
and
you
who
is
selling
the
box.
The
customer
address
boom.
It's
baseline.
Everybody
knows
customers
at
100
main
street.
The
customer
then
notifies
you
that
you
know
as
it's
going
through
the
process.
In
parallel,
the
customer
notifies
you
they
move
to
200
main
street,
so
you
can
change
that
there.
D
A
B
Let
me
ask
you
this:
let
me
ask
you
this
so
now
the
box
has
been
delivered
to
100
main
that's
great.
The
client
then
moves
notifies
you
that
they've
moved
but
they're,
not
shipping.
Anything.
You
don't
need
to
notify
the
manufacturer
that
they've
moved
until
they
want
to
ship
again
all.
A
B
D
Yeah,
it's
it's!
It's
again.
It's
like
it's
like
it's
like
you
write.
This
is
my.
These
are
the
addresses
these
are.
The
addresses
that
are
that
are
this
is
the
commercial
state
right
an
address
is
part
of
the
commercial
state.
You
change
that
what
happens
is
like
it's
like
what
what
john
is
referring
to
and
what
probably
in
coke
coke's
case
is.
That
is
that
is
that
someone,
someone
went
out
of
band
and,
and-
and
you
know,
fat
fat
finger,
10
000,
instead
of
a
thousand
cases,
no.
A
D
D
Corrupted
and
the
agreement
says
I
need
to
have
a
shipping
notice,
a
correct
shipping
shipping
notice
that
is
validated.
I
will
not
be
able
to
generate
that
yeah
that
shipping
notice,
so
I
on
the
other
side,
I
don't
care,
I'm
only
going
to
call
you
like
dude
where's,
my
where's,
my
where's,
my
where's,
my
shipment,
and
then
you
have
to
say
I'm
sorry,
we
screwed
up
our
our
our
data
and
then
you're
gonna,
say:
okay,
I'll
just
short
pay!
You
fine
right!
It's
like
it's!
It's
it's
the
it's
the!
But
it's
it's!
D
What
you
do
on
your
side
with
your
data
is
completely
irrelevant
to
the
standard
and
it's
completely
irrelevant
to
the
to
the
to
the
to
the
to
the
agreed
upon
commercial
state
between
the
two
entities.
It's
like
what
you
do
here
and
screw
up.
It's
like.
I
don't
care!
It's
like!
You
have
a
commercial.
You
have
a
legal
obligation
that
you
need
to
fulfill.
If
you
can't
do
that,
the
contract
exactly
tells
us,
tells
us
exactly
what's
well.
A
C
D
D
A
Yeah,
I
see
your
point
and-
and
I
think
that's
this
is
the
dial.
This
is
the
question
is,
should
it
be
a
a
practice
around
baselining
to
say
you
know
yeah,
it's
a
normal,
you
know,
you'd,
be
kind
of
you
know
in
certain
kinds
of
implementations,
you'd
be
kind
of
dumb
to
not
have
a
heartbeat
running,
but.
A
That's
right,
but
the
question
is
then:
should
we
put
a
should
in
there
to
say
in
these
conditions?
Just
like
you
did
with
the
contracting
thing
you
should
say
under
these
conditions,
you
should
be
aware
that
you
should
implement
this
in
such
a
way
that
if
and
when
your
data
for
any
reason
gets
out
of
sync,
the
counterparties
are
informed.
D
D
But
you
don't
you,
don't
you
don't
you
know
it's
like
you
should
should
not
have
to
do
that
if
it's,
if,
if
it's
not,
if
it's
not
required,
it's
not
even
a
requirement,
let
alone
a
must.
It's
like
it's
like
it's
an
it's
an
it's.
An
implementation
guide
recommendation
it's
it's,
because
it
does
not
technically
impact
the
baseline
protocol
implementation
whatsoever.
If
it
were,
I
would
agree
with
you,
but
it
doesn't.
D
It's
just
it's
just
where,
where
are
you
drawing?
Where
are
you
drawing
the
boundary
for
for
a
baseline
implementation
that
needs
to
be
standard?
That
needs
to
be
exactly
the
same
implemented
across
everywhere
for
baseline
to
work
versus
where,
where
what
is
this
is
this
is
an
additional
service.
That's
a
that's
entirely
nice
to
have
it
it
does
not.
It
doesn't
have
to
be
the
same
like
everywhere,.
A
Right
now
so
we're
getting
top
of
the
hour.
We
did
have
a
whole
hour
on
this.
Hopefully
we
drove
everybody
away
with
this
boring
conversation
and
sent
them
over
to
ey.
For
those
of
you
who
are
holding
on
then
good
on
you,
you
guys
are
true.
You
get
to
wear
your
geek
uniform
with
pride
today
ryan.
I
like
I
liked
where
you're
going
with
some
stuff
there,
I'm
gonna
have
to
go
back
and
review
the
game
tape
there.
A
I
like
some
of
the
comment
you
made
dale
foster.
I
haven't
seen
you
here
before
good
to
see
you
bishwashri.
If
you
don't
know
the
your
your
friend
who's
in
india,
while
working
on
an
indian
time
zone
baseline,
show,
let
me
know
and
I'll
I'll
get
you
guys
connected,
and
anyone
else
like
to
say
anything
before
we
drop
off.
A
No
andreas
always
a
pleasure.
It's
good
to
see
everybody
and
and
we'll
see
you
next
week
on
the
baseline,
show.