►
From YouTube: A New Open Standard for Universal IT State Synchronization in Multiparty Workflows Over the Internet
Description
---John Wolpert, Consensys Mesh
A New Open Standard for Universal IT State Synchronization in Multiparty Workflows Over the Internet - The Baseline Protocol
All Things Open 2021
A
All
right,
I'm
going
to
start
off
with
a
movie,
because
who
doesn't
want
that
at
recess?
My
name
is
john
wolpert.
I
am
the
the
chair
of
the
current
chair,
at
least
for
a
few
more
days
unless
I
get
voted
out
of
the
technical
steering
committee
for
the
baseline
protocol,
which
is
a
joint
one
of
the
projects
of
a
joint
arrangement
between
the
oasis,
open
standards
body
and
the
the
enterprise
ethereum
alliance
and
I'll
go
into
a
lot
more
detail
on
that
project
in
a
bit.
A
What
I
want
to
talk
about
today
is
something
that
that
is
near
and
dear
to
the
baseline
protocol
community,
which
is
getting
large
and
growing,
and
that
has
to
do
with
interop
and
synchronization
of
data
of
data
and
state
between
different
systems
of
record
run
by
different,
legally
separate
entities.
A
B
Look
there
know
what
that
is
why
it's
a
brand
new
piece
of
information
hi
there
little
one,
I
think
I'll
call
you
bit
bit
is
important
bit-
represents
real
value,
real
things.
We
better
put
you
somewhere
safe
little
bit.
There
you
go
into
your
own,
secure
information
management
system
run
by
the
company
that
loves
you.
B
It
used
to
be
that
bit
could
live
its
whole
life
comfortably
inside
its
own
walled
garden
inside
one
company
today
bits
real
power
is
how
it's
shared
between
different
companies,
letting
them
automate
and
synchronize
their
operations
to
produce
goods
and
services
together
forbid
to
do
its
job.
It
needs
to
make
sure
that
everyone
has
the
same
bits.
Somehow
every
copy
of
bit
needs
to
be
in
sync
with
the
others,
but
here's
the
thing
about
bits:
it's
easy
to
change,
one
without
changing
the
other
copies
running
on
other
machines.
B
B
Now
big
companies
with
a
lot
of
cash
to
spare,
have
known
for
years
how
to
keep
bit
from
running
amok,
but
they
all
involved
either
making
one
machine
the
primary
source
of
truth
or
spending
capital
on
dedicated
integration
machines.
All
these
methods
created
more
information
silos
to
manage
what
a
mess
poor
little
bit.
A
different
approach
is
to
keep
bits
in
sync
in
a
loosely
coupled
way.
B
All
the
bits
have
to
do
is
subscribe
to
the
same
spot
on
a
common
bulletin
board
and
they
can
be
sure,
they're
updating
together
as
they
should
a
special
cryptographic
symbol
called
a
proof
is
placed
on
the
board
so
that
fit
can
stay
in
sync
without
exposing
any
information
to
anyone
else.
That
may
have
access
done
right.
It's
impossible
for
observers
to
know
who
is
depositing
proofs
on
the
bulletin
board
or
even
to
discover
rates
of
actual
activity.
B
There's
nothing
new
about
this
design
pattern,
but
until
now,
companies
had
to
spend
capital
to
set
up
these
proprietary
bulletin
boards
for
every
new
set
of
partners.
That's
expensive,
unlike
those
old
bespoke
bulletin
boards,
the
public
blockchain
is
supremely
tamper.
Resistant
which
means
bit
doesn't
have
to
worry
about
someone
changing
or
deleting
the
proof
it's
using
to
stay
in
sync,
and
remember
it
does
this
without
putting
any
actual
information
on
any
kind
of
blockchain
the
industry
standard
for
using
the
public
blockchain.
A
All
right,
so
let
me
run
up
to
the
top
of
this
and
we'll
get
the
slideshow
underway.
I
I
don't
know
if
we're
broadcasting
yet
or
not,
or
are
we
good
all
right?
Well,
hi,
everybody
out
there
in
in
zoom
land
or
what
wherever
they
are,
and
it's
good
to
see
everybody
here
I
know
it's
a
sparse
room,
but
that's
because
we
have
all
those
all
the
seats
spaced
far
apart.
A
The
baseline
protocol
is
is
almost
what
is
it
almost
two
years?
It's
certainly
a
year
and
a
half
old.
Now
it's
one
of
the
it
was
voted.
One
of
the
oasis
opens
best
new
standards
projects,
as
I
recall.
Did
I
get
that
right,
the
best
I
like
that,
even
better,
and
what
is
it?
A
It's
a
standard
for
universal
verified,
state,
synchronization
and
multi-party
coordination
under
zero
knowledge,
and
if
that
sounds
super
boring,
it
was
just
we
deliberately
intended
for
it
to
be
super
boring,
because
we
wanted
to
avoid
all
the
hype
around
things
like
blockchain
and
nfts,
or
you
know
all
that
sort
of
thing.
There
is
a
little
bit
of
a
blockchain
story
in
here,
but
I
want
to
for
especially
for
this
crowd.
I
want
to
be
careful
to
say
this
is
about
state
synchronization
and
I.t
issues.
A
It's
not
about
cryptocurrencies
or
or
even
private
blockchains,
which
are,
in
my
view.
Simply
you
know,
fancy
shared
databases,
so
the
problem.
Yesterday
we
made
a
lot
of
money
on
bpm
for
single
parties.
Anybody
here
make
a
lot
of
money.
On
that
I
know
I
used
to
work
for
ibm.
We
made
a
lot
of
money
on
that
stuff,
right
business
process,
automation,
you
buy
a
company,
they
have
a
different
system.
You've
got
to
get
them
to
work
together.
A
You've
got
integration
work
to
do,
but
that's
all
a
lot
of
that
was
inside
a
single
entity
and
now
what
we're
seeing
is
a
world
that
depends
on
global
networks
of
large
and
small
organizations.
Working
together,
we've
got
multi-party
workflow
problems.
Is
anybody
living
with
that
living
the
life
of
that?
Yet?
Yes,
yes,
yes,
I
know
I
am
well
the
consequences
of
inconsistency,
get
really
big
in
multi-party
workflows.
A
I
used
to
work
for
a
big
retailer
and
my
buddy,
who
was
a
merch,
tells
me
the
story
about
how
he
would
call
up
a
you
know.
A
little
vendor
who
was
put
you
know,
got
lucky
enough
to
put
a
product
on
an
end
cap
and
call
him
up
and
say
where
the
heck's,
our
product,
it's
not
on
our
loading
dock
and
the
company
would
say.
Well
it's
supposed
to
be
there
two
weeks
from
now
he's
like
I
don't
care
when
you
think
it's
supposed
to
be
here.
I've
got
advertising.
I've
got
end
caps,
open.
A
I've
got
people
expecting
to
see
your
stuff
on
the
rack.
I've
got
an
empty
rack,
so
you
will
do
whatever
you
have
to
to
get
your
stuff
here
tomorrow
or
you
don't
have
to
do
business
with
us
anymore,
sound
like
a
fun
day
for
that
vendor
right,
even
if
that
vendor
was
right,
it
doesn't
matter
because
the
big
retailer's
database
is
always
right
right.
So
that's
a
problem.
A
Another
kind
of
problem
is
where
you
have
a
your
retailer
system,
says
or
yeah.
Well
that
in
this
case
I'm
sorry
jumping
forward
to
the
next
slide.
So
here
you've
got
millions
of
dollars
of
make
good,
even
or
or
you've
got
to
spend
a
ton
of
money
on
x
by
expediting
or
both
right.
Anybody
experienced
the
joy
of
that
sort
of
experience
before
yeah
there's
another
problem.
I
call
it
the
coordination
conundrum
we
want
to
share,
we
have
to
share,
but
we
can't
share.
A
You
see
this
in
everything,
and
this
is
where
the
punchline
of
all
this
is
zero
knowledge.
You
know
working
a
coordination
under
zero
knowledge
is
what
I
like
to
call
it,
and
that
is
a
a
rising
form
or
area
of
crypto
cryptography,
not
cryptocurrency,
but
cryptography
born
largely
or
at
least
rising
up
on
the
back
of
things
like
blockchain
work.
But
it's
also
separate
from
that.
You
know
zero
knowledge.
Work
doesn't
require
blockchains
and
it's
not
about
blockchains,
but
blockchains
tend
to
use
them.
A
We
need
everybody's
inventory
data
to
find
where
the
bad
radish
is
right,
so
you
might
have
heard
of
like
walmart's
food
safety
network,
but
what
it's
a
fairly
trivial
problem
to
find
the
contaminated
produce.
If
you
have
a
big
honey
pot,
full
of
data
with
every
company's
inventory
information
in
it.