►
From YouTube: Open Matters: Baseline V0.1--Showcasing Blockchain as a Way of Keeping Systems of Record in Sync
Description
Co-Founder of the Baseline Protocol and seasoned enterprise executive, John Wolpert, joined Guy Martin for second episode of Open Matters.
Launched in March of this year, the Baseline Protocol uses advances in peer-to-peer messaging, zero-knowledge cryptography and blockchain technology to coordinate complex, confidential workflows between enterprises without moving company data out of traditional systems of record. Today, over 600 companies and individuals are actively participating in this initiative.
Most recently, the group completed a major milestone with the launch of v0.1, designed to showcase that blockchain can serve as a valuable way of keeping systems of record in sync without the common concerns around data and business logic privacy. It combines great tools and guidance for data reconciliation in the world of integrated enterprise systems.
V0.1 will bring a new set of state-of-the-art business process automation standards that have the attention of some of the biggest brands in the world!
This one-on-one conversation addresses:
√ The history of Baseline and the impetus to create it;
√ The unique value Baseline brings to OASIS open source & open standards;
√ The plan to ensure Baseline is widely adopted (beyond the Ethereum community) & a plan to attract complimentary blockchain and DLT work.
A
Hi
everybody
and
welcome
to
open
matters.
I'm
your
host
guy,
martin,
the
executive
director
of
oasis,
open-
and
this
is
the
second
installment
in
our
ongoing
series
of
shows,
dedicated
to
exploring
the
interplay
between
open
standards
and
open
source
and
the
communities
that
power
them.
This
forum
is
designed
to
showcase
great
discussions,
debates
and
collaborations
as
we
work
to
unify
the
whole
open
development
ecosystem
and,
if
you're
interested
in
automating
business
processes
across
companies
with
blockchain
you're,
going
to
be
very
interested
in
what
today's
guest
john
wallpark
has
to
say.
A
B
Hi,
I'm
john
wolpert
and
yeah
my
work
on
the
oasis,
ethereum
oasis
baseline
protocol
initiative,
which
is
an
open
standards,
open
source
project
and
we'll
talk
about
that
more
soon.
Before
that
I
was
at
well
right
now,
I'm
the
executive
in
charge
of
maine
net
maine
ecosystems
and
for
the
blockchain
for
consensus,
and
before
that
I
was
at
ibm
and
I
helped
found
ibm
blockchain
and
hyperledger
fabric.
A
Awesome
thanks
john.
So
before
we
get
started
everybody
some
quick
housekeeping
questions
will
be
held
until
the
end
and
attendees
may
raise
their
hand
to
ask
their
question
live
or
if
you
prefer,
you
can
insert
it
into
the
q,
a
box
and
one
more
quick
reminder
that
this
session's
being
recorded
for
later
playback.
So
with
that,
let's
get
started
so
john.
You
hinted
at
it
earlier
and
I
know
as
an
engineer
it's
hard
to
describe
your
baby
in
just
a
few
words.
But
can
you
explain
what
baseline
is
and
why
it's
important.
B
Well,
the
baseline
protocol-
and
we
often
refer
to
it
as
baselining
and
I'll
explain.
Why
is
really
kind
of
interestingly
boring.
It
is
a
a
a
framework,
a
methodology,
a
technique,
that's
why
we
call
it
a
protocol
because
it
used
to
be
that
we,
when
we,
when
we
called
something
a
protocol,
it
was
a
protocol
and
a
technique,
not
what
often
people
are
calling
a
protocol
now
like
a
chain
or
a
platform
or
some
of
some
kind.
This
is
a
protocol.
B
You
have
to
have
some
kind
of
common
frame
of
reference
and
we're
saying
hey
yeah,
the
public
blockchain,
if
done,
if
used
correctly,
is
a
pretty
good,
always-on
state
machine
that
can't
you
can't
tamper
with
and
you
can't
lock
you
out
of
valid
operations.
So
it's
like
the
internet
of
state
or
the
stateful
internet.
B
What
we
call
the
main
net
capital
m,
so
the
baseline
protocol
is
the
first
official
protocol,
the
project
or
a
standard
project
where
we're
getting
everybody
to
make
sure
that
we're
all
using
three
pronged
plugs
and
220
volts
so
that
we
can
talk
to
each
other.
We
can
work
with
each
other,
regardless
of
what
components
or
systems
we're
using
to
baseline.
B
So
that's
why
I
usually
don't
say
the
word
baseline.
It
sounds
like
a
product
or
a
chain
or
a
token
or
a
scheme
or
a
platform,
or
what
have
you?
It's?
Not
it's
just
a
technique
that
we
all
need
to
do
roughly
the
same
way
cool
you
should
you
should
hear
sap
or
oracle
saying
yes,
sap
is
now
baseline
native
oracle's
baseline
data,
and
all
that
means
is
they
they
can
talk
to
each
other
without,
according
to
a
pretty
easy
standard,.
B
It
was
a
huge
milestone
for
two
reasons.
First,
was
that
it
is
now
abstracted
to
the
point
where
it
would
be
fairly
easy
for
anyone
practicing
the
art
of
reading
and
writing
code
to
figure
it
out
and
deploy
it
activate.
It
run
it
use
it
extend
it
tinker
with
it
and
before
that
it
was
really
a
a
specification
in
demo
form.
So
there
was
a
set
of
demo
code
that
was
that
needed
to
be
generalized
and
abstracted.
B
So
don't
let
me
forget
about
because
that's
that's
really
is
the
moment
of
of
doing
that,
that
the
fact
that
we're
really
defining
interfaces
in
code
which
embody
the
standard
or
and
also
inform
the
standard,
so
it
goes
back
yeah
so
that
that
was
why
the
work
on
that
was
important.
The
second
reason
was
important.
Is
that,
unlike
things,
I've
done
in
the
past,
like
like
hyperledger
fabric,
which
was
we,
I
think
we
launched
in
december
17
2015.
B
A
B
Yeah,
decent
guy
and,
and
so
that
was
fun,
but
it
wasn't
hard,
but
in
that
in
that
process
we
didn't
really
embody.
We
didn't
go
after
a
standard
and
the
other
thing
was,
you
know,
we
said:
hey
code
talks
we're
just
going
to
write
code.
That's
fine!
There's
nothing
wrong
with
that.
I
like
what
we're
doing
with
the
oasis
fund
oasis
program
better,
because
it's
both
code
and
standards
and
if
you
do
it
right,
you
don't
have
to
bog
either
of
them
down,
but
I
think.
A
So
john,
do
you
just
want
me
to
ask
you
that
question
that
sounds
like
you're
kind
of
leading
there
anyway,
because
because
you
know,
obviously
here
at
oasis,
open
we're
about
both
open
source
and
open
standards,
and
I
know
you
mentioned
you're
taking
a
multiple
implementation
strategy.
How
do
you
think
this
plays
with
the
future
of
the
specification
work
you're
trying
to
do.
B
B
Underneath
that
you
have
baseline
reference
implementation
one
and
there
will
be
two
and
three
and
four
and
five
and
those
can
be
more
opinionated,
they
can
say
yeah.
We're
gonna
use
our
stack
in
this
way.
With
these
interfaces,
oh
and
the
way
we're
using
it
is
informing
something
new
that
we
should
consider
as
a
new
interface,
and
we
should
write
that
that's
probably
a
signal
that
needs
to
be
also
part
of
the
standard,
so
another
folder
docs
standards.
A
A
B
A
B
B
I
think
I
think
a
lot
of
people
avoid
the
standards
and
software
because
they
assume
kind
of
like
government
that
it's
going
to
go
badly
and
what
you
need
is
smart
government.
You
need,
and
you
need
to
start
with
smart
standards,
development
and
I
think
the
smartest
way
to
go
is
to
have
the
code
and
the
you
know
all
the
work
should
be.
You
know
whether
you're,
whether
you're
writing
in
a
human
language
or
you're
writing
in
code.
You
should
be
doing
that.
B
Considering
that
you
know
part
of
the
same
activity,
which
is
why
the
standards
leadership
like
anaeso,
frank,
who's,
fantastic,
is
part
of
the
maintainer's
body
as
well.
So
we
don't
distinguish
between.
You
know
whether
you're
writing
standards
or
you're
writing
code
or
you're
checking
both
of
those
things
have
to
be
checked
in
yeah.
So
that's,
I
think,
that's
a
good
press
best
practice
in
software
standards.
A
B
I
have
for
the
branding,
because
yeah
ethereum
needs
to
be
all
ethereum.
It's
not
just
enterprises
versus
everybody
else.
It's
it's
all
the
theorem.
Everybody
agrees
on
that,
and
so
I
think
that'll
be
a
shift
and
as
that
shift
comes,
you
know
we.
We
really
need
to
be
focused
on
all
ethereum
standards,
all
without
bogging
down
people
who
really
don't
want
to
be
talking
about
standards.
B
B
You
want
them
kind
of
zipping
along,
but
you
got
to
get
your
ear
real
close
to
the
ground
and
know
what
they're
doing
and
and
then
house
projects
that
are
specific.
Like
baseline,
socrates
would
be
a
good
one.
Other
kinds
of
projects
where
you
know
you
not
only
do
you
need
to
write
code,
but
you
need
to
and
implement
it.
You
also
need
to
be
able
to
say
everybody's
gotta.
You
know
no
matter
who
what
product
you're
using
if
it's,
if
it's
using
this
standard,
it's
we
can
expect
the
same
things
from
it.
A
B
Well,
the
first,
the
first
part
of
it
if
even
before
you
get
to
that
is,
is
dealing
with
the
fact
that
most
standards,
organizations
and
some
open
source
organizations
are
very
concerned
about,
or
they
they
don't
want.
They
have
it's
a
member's
club
right
and
the
problem
with
that
with
any
kind
of
open
thing
like.
B
If
you
know
the
mainnet
is
that
you,
if
you're,
not
gonna,
you
could
just
be
writing
words
on
a
page
if
you're
writing
standards-
and
you
are
not
listening
to
the
development
community-
who
may
not
be
members
of
your
association
and
in
listening
also
having
some
some
ability
for
them
to
listen
to
you
because
they're,
the
ones
that
are
going
to
write
the
code-
and
so
you
could
write,
you
know,
must
do
this
and
they'll.
Never,
maybe
ever
read
it
right
unless
you're.
B
You
can't
right
they're
the
kinds
of
standards
that
simply
require,
or
at
least
will
enforce
that
only
the
people
that
are
paid
members
have
any
say
in
them
in
the
standard.
This
is
not
what
we're
doing
right.
So
what
we're
doing
requires
having
big
ears
and
and
some
heft
with
the
community,
and
it
they
can't
be
based
on
them,
paying
us
money
right.
B
A
Right
yeah,
I
know
I
like
that
governance
model
and
and
honestly
it's
one
of
the
things.
The
reasons
why
I
was
interested
in
coming
to
oasis
is
because
I
I
did
see
that
I
saw
that
that
focus
on
community
that
focus
on
openness,
right
and-
and
you
know,
we're
actually
referring
to
ourselves
as
oasis
open,
which
has
always
been
the
legal
name
of
the
org,
and
now
we're
really,
I
think,
putting
putting
effort
behind
that
in
the
brand.
So
actually
that
leads
kind
of
to
my
next.
A
My
next
question
you
sort
of
touched
on
it
a
little
bit,
but
you
know
if
you
had
just,
could
wave
your
magic
wand
and
say:
hey
oasis,
I'd
like
oasis,
open.
Excuse
me
I'd
like
you
to
do
more
of
this
or
less
of
this
to
encourage
other
open
projects,
efforts
or
or
even
open
standards
efforts.
What
would
be
your
advice.
B
But
I
mean
what
you
needed:
people
that
are
specifically
what
the
attributes
of
jury
that
are
really
important.
Are
you
have
somebody
who
knows
how
to
manage
a
community
knows
how
to
knows
how
to
guide
understands
the
open
source
process.
I
mean
she's.
Even
tipped
me
from
you
know
on
the
side:
hey
you
know
you
might
want
to
do
more
of
that.
You
might
want
to
do
less
of
that.
As
a
new
chair,
that's
fantastic,
to
have
that
kind
of
to
have
somebody.
B
You
know,
checking
your
six
right
right
like
that,
so
that
I
mean
those
are
the
soft
powers.
The
hard
powers
are,
you
know
somebody
who
actually
writes
code
and
can
actually
do
it
at
the
wires
level
has
saved
us
over
and
over
again.
So
jury's,
you
know
not
simply
organizing
these
communities
and
setting
them
up.
She
actually,
you
know,
is
a
talented.
You
know
engineer
or
I
t
person.
A
A
B
Else,
the
other
two
things
are,
I
should
say,
are
one:
you
know
what
what
has
been
astounding
is
how
carol
and
team
have
been
able
to
actually
bring
in
new
members
who
we
never
would
have
thought
to
talk
to
yeah.
We
we
assumed
going
into
this,
that
we
would
have
to
bring
everything
you
know
every
every
every
member
and
that
would
be
our
job
to
convince
them
or
get
them
involved
now
carol's
been
every
bit,
I
mean,
I
think
we
might.
B
We
might
be
50
50
at
this
point
in
terms
of
the
companies
that
are
coming
in.
Not
only
who
are
sponsoring,
but
are
just
simply,
you
know
getting
involved.
We
have
a
you
know.
Google
is
now
there's
a
google
candidate
for
the
technical
steering
committee
and
carol
was
instrumental
in
in
making
the
case
for
them.
We
both
were
so
that
that
was
surprising.
A
Cool
and
by
the
way
for
those
who
don't
know,
that's
carol,
geyer
head
of
business
development
who
another
one
of
the
awesome
staff
I
get
to
work
with
so
really
excited
about
that.
So
john
we're
gonna
kind
of
wrap
up
here
to
leave
some
room
for
questions
so
kind
of
one
final
question
I
have
for
you
for
those
that
are
interested
in
baseline
and
interested
in
the
things
you've
talked
about.
How
would
you
suggest
that
they
get
involved?
What's
the
best
way
for
them
to
kind
of
get
into
this.
B
Get
the
click
on
the
slack
channel
or
slack
inviter,
or
if
you're,
a
telegraph
person
use
that
jory
and
and
one
of
our
team,
our
community
members
set
up
so
that
if
there's
a
channel
in
slack
that,
if
you
use
that
you're
getting
to
every
channel
that
we,
you
know
whether
it's
discord
or
telegram,
which
is
pretty
cool
and
just
join
the
conversation.
It's
a
live
conversation
there's
about
700
people
in
there
and
and
they're
very
friendly.
So
you
can
really
get
involved
and
talk
and
go
what.
A
B
B
B
A
B
A
B
I've
been
looking
at
iso
gtc
one.
Thank
you
for
talking
about
that.
You
know
guys.
I
just
said
one
of
the
things
that's
great
about
working
in
oasis
is
that
you
are
a
feeder
into
a
variety
of
termination
points,
iso
being
one
of
them,
and
it
strikes
me
that
yeah,
you
know
this
is
where
deduping
is
always
a
big
problem
in
standards.
Right,
you
say
well,
deduping
has
problem
with
everything
right,
but
yeah
are
there.
B
Is
there
significant
overlap
and
the
fact
that
we're
out
there
in
the
community
means
that
somebody
can
ask
that
question
so
that
if
I
didn't
know
about
that,
if
I
hadn't
already
had
my
eyes
on
that
and
our
team,
you
know
now
we
would
so
thank
you
for
the
question
and
yeah.
I
think
good.
I
don't
think
any
nobody
likes
too
much
redundancy
a
little
redundancy
is
okay,
but
too
much
is
too
much
and
so
yeah.
If
it's
completely
overlapping
standard.
That
said,
I
think
a
lot
of
times.
B
A
So
obviously
you
said
you
know
we,
we
have
great
relationships
with
all
these.
These
termination
points
nicely
being
one
of
them
and
so
yeah,
obviously
from
our
side.
We
want
to
help,
however,
that
makes
sense
for,
for
for
us
to
be
the
best
help
to
baseline
on
other
projects,
so
cool
dee.
Do
we
have
some
more
questions.
B
Oh
well,
that's
pretty
simple,
remember
back
in
well.
Some
remember
folks
who
remember
the
90s
will
remember
that
there
was
a
time
when
everyone
needed
a
website
or
web
page,
and
then
there
was
a
time
that
everyone
needed
a
spinning
logo
on
the
web
page
and
then
there
was
there.
Then
there
was
the
catalog.
You
needed
your
catalog
on
the
web
page
and
then
you
wanted
to
sell
the
stuff.
That's
in
your
catalog
on
the
web
page
and
then
you
want
to
connect
it
to
your
back-ends
and
et
cetera.
B
B
This
is
more
of
a
horizontal
specific.
The
specificity
is
around
the
horizontal,
which
is
e-commerce
right.
So,
if
you
need
in
this
case
it's
you
might
call
the
e-commerce
that
it's
it's,
the
pipelines
of
where
companies
need
to
share
information
that
they
can
verify
as
identical
and
that
was
derived
identically
without
subjecting
themselves
to
the
hegemony
of
either
of
the
per
any
of
the
participants
or
some
new.
Third,
you
know
centralized
entity
so
b2b
process.
Automations
rise
is
what
we're
really
about.
It's,
not
about
it's
less
about
blockchain
at
all.
B
It's
just
saying:
hey,
yeah,
there's
this
mainnet
thing
that's
always
on,
and
you
can
use
as
a
bulletin
board,
nothing
really
to
see
here,
but
it
means
you
don't
have
to
stand
one
up
every
time
you
have
a
new
partner,
a
new
group
and
and
spend
that
million
bucks.
Doing
that
and
increase
that
amount
of
complexity,
because
now
you're
managing
all
these
little
silos,
you
can
say
no
we're
always
using
the
main
net
for
this,
because
we're
not
leaking
any
information
to
the
main
net.
B
C
I
think
so
I
think
so.
Okay,
we've
got
a
few
more
very
specific
ones.
I'm
going
to
try
and
run
through
them
quickly
and
folks
feel
free
to
drop
off
whenever
you'd
like,
but
I'm
going
to
go
ahead
and
continue
with
the
questions.
We've
got
good
ones,
okay,
baseline
and
ethereum
chain.
You
work
with
both
describe
themselves
as
enterprise
level
technology.
B
It
means
that
the
un,
unlike
a
lot
of
new
early
stage,
blockchain
projects
where
you
said
well,
let's,
let's
get
this
whole
new
stack
this
effectively
we're
five
years
we've
been
treating
blockchains
as
databases,
we've
said:
yeah,
they're,
they're
and
the
point
managers
will
say
they're.
They
are
safer
databases,
they're,
not
they're,
actually
less
safe
databases,
because
now
administrators,
if
you're
doing
it
correctly
and
you're
doing
it
actually
in
a
way
that
requires
a
blockchain
in
any
way.
B
Don't
put
data
on
blockchains
any
kind
of
blockchain,
private
or
public,
and
so,
where
is
where's
the
work
being
done
in
sap,
which
is
an
enterprise
grade
production
system
in
oracle
in
dynamics?
In
you
know
your
database,
and
even
in
your
spreadsheet
there
yeah,
where
those
are
appropriate
neo4j,
you
know
any
kind
of
data
system.
B
Dpms
is
where
the
work
is
getting
done
and
then
we're
putting
a
little
bit
of
standardized
glue
on
the
outside
that
you
know
with
a
crud
access
that
says.
Okay,
I'm
going
to
process
this
in
in
such
a
way
that,
when
I
sent
when
we
send
this
record
to
these
other
guys
we're
going
to
also
record
a
proof
that
they
received
it
that
they
could
process
it
consistently
and
digitally
signed
so
that
we
have
not
only
proof
of
existence.
C
B
Oh
well,
yes,
right
now
there
are
a
number
of
feature
and
function
and
performance
or
non-functional
requirement
initiatives
increasing
the
scale
we
can
do
about
several
million
baseline
events.
Conf
confirmations
on
chain
in
a
month.
That's
gonna,
get
us
well
into
2021
and
then
with
e2.
That
should
bring
it
up.
Another
100
x,
but
also
we
have
batching
and
some
other
mutex
type
stuff
that
we
can
work
on.
That
will
bring
that
up.
B
Another
100x
and
then
you're
getting
into
basically
an
an
entire
industry
could
be
doing
baselining
on
a
good
chunk
of
their
most
or
all
of
their
business
business.
To
business
events,
you
know
with
baselining
globally,
so
getting
to
scale
is,
is
good
and
then
there's
all
sorts
of
really
cool
projects.
There's
one
where
you
just
get
a
docusign
and
you
click
on
that.
You
get
to
baseline
that
record
into
your
system,
or
you
could
create
an
imagine
somebody
saying
for
9.95
a
month.
B
A
Yeah
no
tons
of
opportunity,
john,
really
really
appreciate
you
being
on
yeah
thanks
john.
This
has
been
fantastic
and
you
know
I
know
when
I
first
joined
oasis,
open
baseline
was
was
one
of
the
things
that
I
first
saw
and
was
called
out
as
a
great
example
of
the
power
of
the
open
projects,
initiative
that
we've
put
out
there-
and
I
know
we're
all
incredibly
thankful
for
for
your
encouragement
and
support
and
everything
you've
done
so
thanks,
everybody
out
there
for
joining
us
until
next
time,
thanks
for.