►
From YouTube: Baseline Protocol Explainer Session
Description
Watch Ernst & Young, ConsenSys, Microsoft and a host of questioners go through the basics of the baseline protocol approach to enterprise mainnet / blockchain in this first live Q&A session, held on March 12, 2020...a few days before the open source repo opens to public contribution at https://github.com/ethereum-oasis/bas.... For more information and to get involved in the baseline community, join us at http://baseline-protocol.org
Special thanks to our partners: AMD, ChainLink, ConsenSys, Core Convergence, Duke University, Envision Blockchain, EY, MakerDAO, Microsoft, Neocova, Splunk, Unibright, Provide, and W3BCLOUD.
A
You
have
a
lot
of
folks
in
here.
I
think
we're
going
to
get
right
to
it,
because
this
will
be
recorded,
we'll
be
putting
this
out
to
to
youtube
and
such
will
we'll
get
right
into
it,
and
Paul
Brodie
from
Ernst
&
Young
is
is
first
up.
So
Paul
would
like
to
say
a
few
words
and
York
I,
just
unmuted
you
so
that
you
can
I,
think
yeah,
mute
and
unmute
yourself.
A
C
A
That
was
Paul
Brody
everybody
from
nursing
young
one
of
the
founders
of
this
project
and
we're
gonna
have
a
lot
more
folks
coming
in
and
Nick.
It
would
be
great
if
you
kept
an
eye
on
and
be
grateful
if
you
could
keep
an
eye
on
questions
and
raising
hands.
We're
looking
forward
to
those
comments,
and
we
will
paste
the
comments
into
the
public
slack
at
the
close
of
this
right.
So
real,
quick.
A
D
A
We
sure
glad
or
glad
you're
here
and
it's
for
the
record.
Not
a
lot
of
this
wouldn't
be
happening
if,
if
you
hadn't
used
your
good
offices
to
get
the
team
together,
so
thank
you
for
that
all
right,
so
we're
gonna
go
through
the
radish
34
demo
and
baseline
protocol.
Very
briefly
talk
about
wins
and
how's
how
you
get
involved.
Really.
A
The
purpose
of
this
is
to
make
sure
that,
when
the
repo
is
released
in
before
the
end
of
March,
that
you're
not
surprised
by
what
you
see
that
you're
you're
excited
that
you
can
get
involved,
you
know
where
to
go,
what
to
do
and
how
you
can
get
value
out
of
this
for
yourself
and
I'd
like
to
say
just
before
we
get
into
this.
Our
thoughts
are
with
all
the
everybody's
families
and
and
folks
who
are
worrying
about
what's
happening
in
the
out
there
in
the
world.
A
So
with
that
quick
feet
overview
of
the
announcement,
the
announcement
last
week,
if
you
didn't
catch,
it
was
yeah,
Ursa,
young
and
and
and
consensus
put
out,
two
press
releases
that
generated
260
articles
in
a
epic
1.2
billion
in
reach,
with
an
effective
in
other
word,
get
that
kind
of
reach.
You'd
spend
11
million
dollars
in
advertising
that
is
I
haven't
seen
those
kinds
of
numbers
in
a
long
time.
It's
it's
remarkable
and,
what's
even
more
remarkable,
is
by
comparison
to
some
other
announcements
that
generated
more
articles
like
twice
many.
A
They
usually
the
ones
that
we
looked
at
generated
about
tenth
of
the
reach,
and
that
speaks
to
the
power
of
the
message
and
I
think
the
message
is
powerful.
So
that's
the
first
thing
we
want
to
go
over.
It
is
now
it
really
is
time
to
to
say
something
about
the
teams
and
some
of
the
folks
on
those
teams.
Who've
gotten
us
to
this
place.
Obviously
Paul
Brodie
and
his
team
at
Ernst
&
Young
are.
A
They
should
be
an
already
legendary
that
they
got
a
organization
the
likes
of
a
hundred
year
old
accounting
firm
to
do
such
a
remarkable
R&D
with
such
a
amazing
amount
of
commitment
and
effort
and
money
spent
folks
like
Karthik
Isola
promos,
on
the
on
the
call
and
we'll
be
speaking
later,
great
leadership
on
the
technology
side,
Brian
Chamberlain
who's.
Also
on
the
call
just
one
of
the
you
know,
solid
developer
lead
developers
out
there.
A
Many
folks
to
thank
and
no
time
to
do
it
so
I'll
leave
it
at
that
also
York
Rhodes,
who
you
know
it's
not
heard
earlier
from
Microsoft,
whose
good
offices
really
did
get
Ernst
and
Young
and
consensus
together,
where
it
might
not
have
happened
otherwise
and
supported
us
throughout
the
process
and
then
for
the
many
firms
that
have
come
forward.
Fourteen
which
is
three
short
of
what
hyper
ledger
launched
within
in
2015
and
all
we
have
receives
since
then.
Are
more
companies
notable
ones
that
want
to
get
involved
want
to
know.
A
What's
going
on
calling
for
briefings,
major
major
US
bank
having
a
briefing
with
us
later
today,
it's
been
astounding,
be
the
reaction.
They've
have
been
saying
if
you,
if
you
can
think
of
a
big
company,
there's
a
good
chance
that
they
called
us
in
the
last
week
and
the
etherium
foundation
and
the
EEA
both
supporting
the
Oasis
organization,
which
is
has
been
amazing
at
getting
us
to
organize
organize
so
that
we
have
a
proper
open
source
operation.
A
It's
one
thing
to
put
out
an
open-source
repo
on
get
or
on
github.
It's
another
thing
to
have
a
real
organization.
Behind
it
and
Oasis
is
legendary,
if
you
know
sgml
and
sam'l
and
other
major,
you
know,
standards
in
the
Internet
Oasis
was
there,
they
have
been
around
forever,
and
so
there
this
project
would
be
kind
of
akin.
To
hyper
ledger
is
to
Linux
Foundation
what
we
are
Oh
ASA
s--
and
the
enterprise
or
the
etherium
Oasis
project.
Wichitawx
RIA
might
get
you
to
talk
about
a
little
bit
later.
A
If
we
have,
if
we
have
time
I
know,
people
have
a
lot
of
questions,
so
I'll
move
on
from
there
all
right,
the
radish,
34
and
baseline
protocol,
so
radish
34
was
a
product
or
project
that
envisions
what
it
would
be
like
for
a
supply
chain
product
and
an
SCM
supply
chain
management
product
in
particular,
or
several
of
them
to
baseline
themselves.
Now
we
started
by
saying
just
simply:
we
don't
have
the
notion
of
baseline.
We
just
said
we
have.
A
We
think
we
have
the
technology
now
and
the
know-how
to
do
things
with
the
public
aetherium
main
net.
That
would
be
acceptable
to
the
likes
of
the
of
a
conservative
security
minded
corporate
technology,
executive
officer
and
paul
brodie
and
team
are
so
experienced
in
supply
chain
that
we
chose
supply
chain
in
particularly
procurement
as
the
use
case
for
this
POC.
The
learning
from
that
POC
was
amazing
and
it
became
clear
towards
the
fourth
quarter
of
last
year
that
a
protocol
and
open
source
open
standards
protocol
in
particular
needed
to
happen
right.
C
A
C
C
A
Thanks
for
that,
I'd
like
to
double
down
on
that
that
yes,
the
tokenization
is,
is
an
important
concept,
even
in
baselining,
but
the
important
thing
is
to
do
tokenization
in
such
a
way
that
you're
not
giving
away
secrets
to
your
competitors
and
I
think
that,
as
we
get
into
the
baseline
protocol,
you'll
see
that
that
is
that
that
the
technique
of
doing
that
is
is
not
only
private
but
stealthy
and
but
still
conferring
the
same
benefits
of
tokenization.
That
you
would
normally
expect
the
the
repo
will
release
before
the
end
of
the
month.
A
As
we've
said,
and
task
groups
will
be
forming
to
address
technical
priorities
and
vertical
cases,
we
will
have
a
technical
steering
committee
of
eleven
members.
We've
decided
that's
the
number.
We
considered
seven
nine
eleven,
many
more
11s
the
right
number
I
won't
go
into
the
details
of
that,
but
it
you
know,
that's
the
number
and
we
already
have
oversubscribed
the
number
of
people
that
want
to
be
technical
steering.
Committee
members
is
double
that
and
we're
going
through
a
process
that
we
didn't
really
expect
to
have
to
do.
A
A
Anybody
who's
been
involved
in
an
open-source
project
before
will
know
that
the
real
power
and
the
real
activity
is
with
the
maintainer
z'
and
the
committers
the
TF
seeds.
Job
is
mainly
to
deal
with
market
failures,
where
the
commuters
can't
maintain
errs,
can't
agree
on
something
and
they
need,
or
they
need
bootstrapping
to
get
the
initial
maintainer
z'
in
in
right,
but
and
and
set
goals
like
how
many
maintainer
x'
are
needed
to
to
commit
a
pea
in
a
pull
request,
etc.
A
And
it's
really
important
to
note
I,
don't
know
if
Josh
Dean's
is
on
yet,
but
this
is
really
a
joint
effort
with
the
EEA
main
that
were
the
enterprise,
aetherium
Alliance
main
networking
group,
which
itself
is
a
joint
effort
with
the
etherium
foundation,
so
we're
all
kind
of
getting
together
here-
and
this
is
an
epic
moment
right-
this
isn't
a
sea-change
and
how
things
have
been
going
up
over
the
last
five
years.
We've
had
all
this
bifurcation
all
this
Byzantine,
you
know
different.
A
You
know,
you
know
there
was
a
Cambrian
explosion
in
blockchains
there
was
a
Cambrian
explosion
in
philosophies
around
blockchain
and
you
had
public
versus
private.
You
had
Enterprise
versus
up-and-comers,
and
this
is
a
great
example
of
not
that
this
is
a
great
example
of
convergence
of
working
together
of
saying
well
I'm,
I'm
startup,
but
I
also
have
the
same
issues
and
interests
and
needs
as
many
inner
enterprises
I'm
in
the
ethereal
fountain
in
the
etherium
foundation
you're
in
the
AEA.
A
A
Why
baseline
your
systems
and
offerings
is
the
fifth
so
future
proofing
your
legacy
systems
without
major
modification
and
increasing
their
utility?
By
going
from
not
simply
being
able
to
tell
you
what
you
know
but
being
able
to
on
a
good
day
when
you
get
the
data
right
and
even
factoring
that
finger
and
entry
to
not
only
knowing
what
you
know
with
greater
reliability,
but
also
on
a
record
by
record
basis
on
a
business
process
by
business
process
basis,
knowing
with
confidence
with
validation.
A
We
call
that
atomic
compartmentalization,
but
because
we're
doing
that
on
the
main
net
we
have
no
silos
so
work
workflows
can
interoperate
without
having
to
call
a
network
administrator
and
figure
out
whose
blockchain
is
gonna
win
the
which
blockchain
are
we
going
to
use
contest?
What
is
not
baseline
baseline
is
not
a
product,
it's
not
a
platform,
it's
not
a
change,
not
a
coin.
It's
not
a
scheme,
if
think
of
it
more
as
a
design
pattern
that
anybody's
product
can
can
employ,
and
frankly,
a
competent
team
could
deploy
tantamount
to
in
production
today.
A
A
It's
the
main
that
is
a
set
up
is
a
specification
unto
itself
saying
we
need
something.
That's
always
on
that.
Doesn't
can't
lock
you
out
of
valid
operations,
is
always
running
and
is
as
proof
as
possible
against
some
group
taking
it
over
changing
history
or
preventing
you
from
doing
things
as
possible,
a
public
good
and
yes
for
our
money
right
now.
A
So
putting
data
on
the
main
that
isn't
necessarily
a
great
idea,
but
using
the
main
net,
its
ability
to
have
data
and
have
expressive
smart
contracts
in
tokenization
to
serve
as
in
a
as
a
form
of
middleware,
in
particular,
Enterprise
Service
bus
between
entities
when
you're
doing
business
process
integration
across
companies
and
we'll
talk
about
that
in
a
minute.
They're
great
explainers
here
at
this
link,
I
know
that
you
can't
click
that
link.
A
So
if
you
have
a
product,
don't
worry
about
baseline
being
another
product,
you
have
to
worry
about,
it's,
not
your
the
product
and
we
will
support
you
as
a
community
if
you
are
using
baselining
in
powerful
ways.
So
that's
the
way
to
think
about
this
I
hope.
Everybody
understands
I'm
going
to
look
at
some
questions
here.
Real
quick.
B
A
Notification
message:
bus
for
streaming
parties
have
accepted
reviews.
This
is
a
pretty
advanced
question,
so
Clemens.
Maybe
we
can
get
to
that.
But
keep
me
honest.
Let's
make
sure
we
get
to
that
question,
but
I
think
to
answer
it
right
now
we
might
be
blowing
a
past
up
some
some
basics:
okay,
fair
enough
yeah,
let's
see
also
a
three-part
transaction
where
one
transactions
failed
because
of
a
timeout.
It
stranded
both
money
and
the
data
interesting
in
Scott.
A
C
A
C
Only
other
thing
I
would
add.
Karthik,
maybe
is
whether
using
the
notarization
functions
are
creating
and
moving
tokens
right.
You
know,
even
when
the
network
is
congested,
you're
still,
you
know
have
a
fairly
significant
amount
of
time
that
you
could
use
to
get
things
done
and
the
price
transactions
are
and
and
we're
not
talking
about
sort
of
Wall
Street
trading
transactions.
Most
enterprise
transactions
are
kind
of
as
I
like
to
joke.
You
know
the
30
in
that
30
is
days
right.
A
That's
well
said:
I,
agree
and
Karthik
I
just
made
you
a
co,
so
you
can
you
can
chime
in
it
will,
let's
get
into
the
the
architecture
very
simply
and
and
you'll
see
that
if
you,
if
you
go
to
this
explainer,
there's
there's
some
great
stuff.
Paul
Paul
did
a
really
great
piece
and
then
I
wanted
to
not
do
another
piece
elsewhere.
So
I
put
it
right
underneath
his
piece
sort
of
a
my
sense
of
the
transaction
workflow.
This
is
a
kind
of
a
pretty
picture,
or
at
least
a
unnecessarily.
A
Is
it
I
like
the
picture?
It
kind
of
gives
you
something
to
look
at,
but
it
does
ask
for
some
explaining
so
yeah
baseline
server
is
a
is
again
as
a
specification.
You
could
be
say
s
AP
or
ops
chain,
which
is
Eli's
product
or
any
other
product
in
the
space.
That's
doing
ERP,
CRM
SCM.
Anything
like
that
and
you
could
make
your
system
baseline
enabled.
Then
you
wouldn't
need
a
separate
server,
but
you
know
we're.
A
We
have
defined
a
set
of
server
components
that
anybody
could
make
a
product
out
of
or
could
integrate
into
their
product.
So
again,
it's
a
specification
and
a
reference
implementation
that
can
be
used
by
anybody
and
it
is
public
domain
and
what's
involved
in
that
is
a
is
some
pretty
normal.
You
know
think
of
it
like
Legos
right,
the
Legos
themselves
are
pretty
known,
boring,
except
for
one
and
we'll
discuss
that
one
and
it's
the
composition
of
those
boring
Legos.
That
makes
it
an
interesting
pattern.
A
So
messaging
is
something
we
know
EDSA
as
digital
signatures
or
something
we
know,
system
record
integration,
translation
things
we
know
and
we
know
smart
contracts
and
we
know
the
main
net.
We
know
blockchain
and
we
also
come
to
know
zero
knowledge
proof.
These
are
all
Legos
that
we've
assembled
in
a
certain
way
so
that
we're
not
simply,
as
you
might
expect,
hashing
data
onto
a
blockchain
or
onto
the
New
York
Times,
classified
section
to
you
know,
say
to
have
proof
of
existence.
A
This
is
more
like
proof
of
entanglement
or
proof
of
consistency,
and
that
right
away
gives
you
proof
against
repudiation.
So
if
anybody
is
familiar
with,
you
know,
businesses,
you
know
being
able
to
say,
hey,
I
didn't
get
that
memo
or
I
didn't
you
know,
I
didn't
agree
to
that
is
a
trillion
dollar
problem
right
there
and
you
can
solve
that
with
digital
signatures,
but
having
a
common
frame
of
reference
where
those
the
proofs
that
those
digital
signatures
goes
is
important,
but
it's
only
the
first
step
that
would
be.
A
D
I
can
still
unyu
yeah
I
made
you
close
yeah,
that's
great,
so
I
mean
I,
I.
Think
there's
a
there's
a
lot
of
flexibility
here
in
the
system
to
be
determined
additional
capabilities
there.
You
know
it's
really
designed,
as
as
John
said
earlier,
a
pattern
and
a
template.
That
is
a
good
jumping-off
point
for
people
to
take
it
further,
and
this
is
the
reason
why
we've
bundled
it
under
the
umbrella
that
we've
done
so
that
that
is
it
possible
to
happen.
D
As
an
example,
I,
don't
know,
I
didn't
hear
you
mention
this
before
John,
but
there
actually
is
a
messaging
task
force.
That's
spinning
up
inside
the
main
networking
group
in
the
enterprise
at
theorem,
Alliance,
specifically
to
look
at
Enterprise
requirements
for
messaging
capability
to
replace
or
enhance
whisper
as
an
example.
So.
A
That
that's
right,
so
the
the
messaging
protocol
in
particular,
is
very
important.
We
did
use
whisper
to
begin
with,
because
it
was
there
and
I've
said
before
I
think
publicly.
You
know
I
think
one
of
the
things
that
could
be
really
exciting
is
to
go
into
the
core
de
flows,
public,
open
source,
repo
and
and
take
some
tricks
from
that
and
I'd
love
to
see
a
day
where
you
know
Corte
flows.
Our
the
messaging
protocol
for
aetherium
that
would
I
would
enjoy
that.
A
B
A
Theorem
is
a
pretty
good
candidate
for
that
I,
for
one
will
go
to
whatever
becomes
a
better
candidate
for
that.
That
is
also
going
to
win
hearts
and
minds
and
become
a
standard
which
I
think
the
etherium
community,
just
simply
Trump's
all
on
that
matter.
So
and
it's
stay
its
continuing,
which
is
remarkable.
It's
staying
innovative.
In
other
words,
you
know
it's
not
locked
in
to
just
protecting
the
value
of
its
coin
or
whatever
it
is.
It's
got
a
great
roadmap.
A
This
obviously
tracks
with
eath
too,
but
I
will
hasten
to
say
that
you
can
use
baselining
approach
with
each
one.
Just
fine,
you
know
it's
not
going
to
be
as
fast
and
you're
gonna
have
to
deal
with.
Maybe
some
concerns
about
a
noisy
neighbor,
but
as
Paul
birdie
will
point
out,
though,
a
lot
of
those
are
trumped
up
and
not
as
big
of
a
deal
as
you'd
think,
certainly
depending
on
the
use
case
max.
B
A
A
From
that
perspective,
you
know,
my
point
of
view
is:
is
simply
that
the
most
important
thing
to
have
a
name
that
is
the
is
proof,
is
being
an
expressive,
backplane
and
expressive
bulletin
board
that
you
can
do
things
with,
but
that
is
proof
against
getting
taken
over
by
two
loving
trolls,
locking
you
out
or
changing
history.
It
can
be
pretty
slow
frankly
compared
to
other
kinds
of
state
machines.
A
As
long
as
it's
really
good
at
that,
one
thing
show
me
something:
that's
better
than
aetherium
at
that,
and
does
that
mean
that
we
can't
improve
in
theorem
absolutely
not
there's
already
a
project
going
on
to
get
enterprises
into
the
act
of
helping
maintain
the
integrity
of
the
ledger
by
mining
and
staking
as
known
entities?
Think
of
that
for
a
minute.
B
A
Ledger
is,
first
of
all,
when
you
say
hyper,
ledger
I
mean
which
project
in
hyper
ledger.
Are
you
asking
about,
and
you
know
hyper
ledger
Bess
who
is
an
aetherium
client
and
I
should
expect
that
the
standards
from
baseline
protocol,
if
we
do
our
jobs
right,
we'll
go
into
things
like
hyper
ledger,
Basu,
but
also
I
could
see
it
going
into
many
other
hyper
ledger
projects,
because
it's
just
a
sensible
pattern.
A
You
know
that
would
it
would
further
obfuscate
the
you
know
if
you're,
if
you're
sniffing
around
on
a
particular
fabric
channel-
and
you
see,
activity
and
you're
in
a
very
small
group,
you
can
figure
out
a
lot
of
things.
Even
if
you
have
this
privacy
group
going
I
was
going
through
that
code
the
other
day
and-
and
so
that's
a
perfectly
good
pattern.
It's
not
dissimilar
to
the
way
baselining
works,
but
working
together
would
be
even
better
I.
E
So
when
we
designed
the
baseline
protocol,
one
of
the
things
that
we
also
took
into
consideration
was
when
we're,
even
when
we
are
interacting
with
the
main
that
we
don't
necessarily
put
any
parts
of
the
business
logic,
on
the
mean
that
business
logic
or
the
data
that
is
used
is
to
be
used
for
the
enterprises
that
never
enters
the
main
net
or
for
that
matter.
If,
even
if
it's
a
different
ledger
it,
the
point
is
to
not
let
these
data
or
logically
the
legacy
systems
or
the
legacy
landscape.
E
So
in
that
regard
any
of
the
troponins
that
we
have
as
John
and
Colin
were
pointing
out
and
Yoko
pointing
out
earlier.
This
is
these
are
extensions
that
could
be
replaced
like,
for
example,
as
it
was
pointed
out,
messaging
could
be
replaced
by
a
better
messaging
protocol
or
a
bedroom
is
written
as
a
distributed
system.
Similarly,
where
we
are
using
privacy
aspects
like
zero
knowledge
groups,
there
are.
E
There
are
ways
to
even
take
your
knowledge
groups
and
actually
interoperate
them
across
other
legends
as
well,
so
in
short,
I,
just
having
color
to
what
John
was
saying,
is
that
this
Lim
protocol
is
more
of
an
approach,
how
we
can
rationalize
efforts
on
moving
away
from
multiple
private
blockchains
and
interoperability.
Efforts
to
it's
a
common
standard
in
the
Komen
public
infrastructure.
Could
that
make
sense.
A
Thank
you
thanks
perfectly
I
think
that's
well
said.
Important
thing
to
remember
is
that
there
are,
there
are,
is
a
series
of
components
and
I
think
we
should
go
through
them
right
now
and
maybe
Karthik
you
maybe
go
off
mic
or
off
mute,
and
you
and
I
can
come
walk
folks
through
this.
Maybe
we
can
have
buddy
system
this.
A
So
you
know
the
workflow
here.
I
have
a
record
in
my
ERP
system,
I'm
gonna
baseline,
that
and
to
you
you're
my
counterparty.
It's
a
we're.
Gonna
share,
we're
gonna,
agree
on
a
master
service
agreement
for
purchasing
we're
gonna
agree
on
a
tiered
pricing
structure
for
a
volume
discount,
so
anything
under
100
units
I
get
no
discount
over
100
years.
I'm
gonna
get
a
10%
discount.
A
We're
gonna
agree
to
that,
it's
in
a
record
and
then,
instead
of
putting
that
on
a
blockchain
or
on
some
other
system,
we're
going
to
you're
gonna
I'm
gonna
leave
it
in
my
database,
I'm
gonna
message
it
to
you
by
a
secret
messenger
I'm
going
to
send
with
it
some
other
components
in
the
payload
that
will
allow
you
to
deposit
that
in
your
database
run.
Some
process
now
you're
running
the
same
process
as
I
am
verifiably
you're,
gonna
digitally
sign
that
send
it
back
to
me.
A
My
baseline
server
will
will
use
its
zero-knowledge
service
to
verify
that
that
we
both
did
the
same
thing
and
have
the
same
thing.
Then
we're
sent
a
proof
and
some
other
payload
up
to
the
main
net
into
a
shield
contract
which
was
set
up
dirt
when
we
set
up
our
relationships,
so
that
could
be
with
a
bunch
of
other
companies
or
just
you,
and
I
we're
three
smart
contracts
were
put
on
to
the
main
net
by
a
registrar
factory
karthik.
You
want
to
take
it
away
from
there
yeah.
E
So,
as
jim
was
saying,
one
of
the
aspects
of
the
baseline
protocol
is
how
we
had
classifying
or
categorizing
different
different
pieces
on
different
label
blocks.
If
you
think
about
the
procurement
example
like,
as
as
john,
was
pointing
out,
one
of
the
things
that
we
did
was
a
good
use
of
baseline
protocol,
good
views
of
a
good
way
to
manifest
a
base-10
protocol
is
to
apply
to
a
Wailord
a
nice
case,
which
is
spans
across
industries,
but
also
something
have
there.
E
We
can
test
out
or
emphasized
importance
of
some
of
the
core
concepts
that
we
deal
with
on
a
day
to
day
basis
and
when
it
comes
to
block
chain
like
motorisation,
traceability
tokenization
are
some
of
the
core
concepts
that
we
come
across
and
block
chain
which
have
which
have
enterprise
value
of
latent
enterprise
value.
So
when
we
talk
about
hood
the
procurement
process,
the
baby
we
came
about
came
up
with
it
was
that
there
are
processes
there
there.
There
are
negotiations
between
the
parties
processes
where
there
are
with
the
notarization
Zoar.
E
You
know
cosines
or
mutual
agreements
that
that
basically
posit
the
future
processes
or
subsequent
processes,
and
there
are
processes
that
which
have
material
value
or
or
monitor
monetary
value.
So,
in
that
regard,
what
we
started
off,
it
is
saying
that
RFP,
we
pretty
much
like
try
to
layer
it
up
with
each
process,
but,
for
example,
when
we
started
off
with
another
RFP
is
basically
without
any
other
bells,
and
whistles
at
the
core.
Rfp
is
a
process
where
two
bodies
interact
with
each
other
to
exchange
documents,
and
in
this
process
we
thought
we
said.
E
Okay,
the
most
basic
way
to
use
this
is
you
shall
use
something
like
a
secure
messaging
protocol?
So
that's
the
most
inclined
of
this
line
is
that
you
want
to
exchange
documents
in
the
clear
or
rather
exchange
documents
in
a
private
manner
in
a
private
channel
in
the
future,
the
RFP
can
more
can
actually
be
extended
to
more
and
more
bearings,
such
as
negotiations
and
other
constraints
that
may
come
from
X
accepting
rfp's,
but
RFP
is
like
the
most
fundamental
process
where
we
started
off
like
trying
to
explain.
E
E
Keeping
aside
all
the
nuances
of,
but
there
are
FB
comes
first
or
MSA
comes
first
or
the
lifetime
of
an
MSA
and
so
on
and
so
forth.
Msa
is
an
agreement
or
assent
by
say
a
buyer,
to
a
supplier
to
say
that
these
are
the
terms
of
contract
or
the
terms
of
our
relationship
and
this
terms
of
business
relationship,
and
these
terms
are
something
that
both
of
them
have
to
sign.
But
at
the
same
time
we
want
to
make
sure
that
we
do
not
reveal
the
identity
of
who's
signing
the
counterparty.
A
There
I
think
right.
Let
me
just
interrupt
you
very
quickly.
There's
a
couple
of
questions
that
are
interesting,
they're,
apropos
to
what
you're
saying
right
now.
Could
you
could
you
tune
this
to
kind
of
the
elephant
in
the
room?
Is
why
do
we
need
zk
for
this
process?
Why
isn't
digital
signature
is
sufficient.
So
if
you
want
to
answer
that
in
your
in
your
comments,
I
didn't
want
to
lose
the
opportunity
keep
going
so.
E
A
E
But
when
we
talk
about
zkp,
one
of
the
main
things,
what
they're
looking
at
is:
how
can
we
make
sure
that
the
information
of
the
of
the
information
of
the
counterparty
is
not
revealed
like
the
identity
of
the
counterparty
is
not
revealed,
but
I
can
prove
or
I
can
rather
verify
to
any
party
on
the
main
net
or
any
party?
On
the
on
the
on
the
on
the
ledger,
such
that
the
sign,
the
document
has
actually
been
signed
by
a
legitimate
counterparty
who
has
actually
agreed
upon
to
these
terms
and.
A
E
What
it
wants,
yeah,
absolutely
that's
where
I
think
things
start
getting
more
interesting
with
and
I'll
allude
to
the
question
that
Gary
Mensah
asked
also
about
whether
MSA
can
be
an
F
T.
That's
actually
a
great
point,
the
reason
it
could
be
an
NF
T
and
that's
where
I
think
we
went
to
that
NF
t
crosses
or
a
tokenization
process
and
a
subsequent
step
going
from
MSA
to
a
purchase
order
so
in
a
purchase
order.
E
So
that's
why
we
we
took
the
concept
of
MSA
notarization
and
extended
it
to
say
that
there's
also
state
marker
and
he
state
markers
act
as
a
code,
encode
trace
or
traceability
or
validation,
to
prove
that
Theo
is
starting
off
or
any
purchase
or
restart
from
a
correct
starting
state,
and
the
additional
bearings
that
we
had
over
there
was.
That
feel,
is
something
that
is,
that
is,
that
could
be
tradable.
That
could
be
monetizable
and
that's
where
Pio
can
be
treated
as
an
NFC
token.
So
the.
A
Cool
thing
here:
isn't
it
karthick
that
you
I
mean
that
Pio,
if
to
POS,
try
to
update
themselves
from
say
the
original
state
of
zero
right?
So
there's
zero
orders
and
there's
a
rate
table
that
says
over
a
hundred
I'll
get
a
discount
if
I,
if
I've
got
two
or
three
POS
that
try
to
calculate
from
zero.
I
have
a
problem
in
that
in
traditional
systems
today,
as
Paul
probably
knows
very
well,
because
he
taught
us
this,
he
really
pushed
this
issue.
A
Revenue
recognition
becomes
a
real
problem
and
you
have
to
take
a
lot
of
time
and
that
time
is
cash
in
Bank
for
small
business
right
so
being
able
to
sit
to
say
the
main
that
is
gonna.
Prevent
me
from
trying
to
update
the
state
of
the
MSA
twice
is
important
right
because
then
I
can
get
to
revenue.
Recognition
faster,
I've
got
two
POS
for
twenty
I
need
the
third
Pio
to
calculate
from
forty,
not
from
zero
or
twenty
again,
and
you
could.
A
A
E
A
Other
thing
is
probably,
and
we
do
have
to
wrap
because
we're
coming
up
on
five
minutes
before
the
end
of
the
hour,
and
we
will
do
these
more.
The
other
thing
that
might
be
very
interesting
is
a
industry
standards.
Bodies
might
be
very
interested
in
these
libraries
of
of
zero
knowledge
circuits
right
so
that
you
can
say.
Not
only
do
we
have
the
st.
did
we
execute
the
same
code.
We
executed
the
same
code
verifiably
in
accordance
with
standard
X.
A
So
if
I'm
a
regulated
company,
I
can
say
that
we
can
say
not
only
are
my
counterparties
and
I
in
sync,
but
we
did
it
in
the
way
that
the
industry
requires
to
be
compliant,
and
that's
really
cool
I
mean
it's
clearly.
A
using
snarks
is
somewhat
more
expensive,
although
thanks
to
Ian
Weis
efforts
much
less
expensive
than
it
was,
but
it
you
know
in
a
lot
of
cases
where
you
need
to
be
compliant,
a
little
extra
expense
could
go
a
long
way
right,
hey.
D
D
It's
York
yeah,
so
max
basically
said
the
PERT.
So
the
purpose
of
the
zero
knowledge
proof
is
to
prove
to
everyone
else
that
the
parties
agreed
to
something
without
revealing
what
they
agreed
to
and
I
think
the
nuance
as
I
understand
it
is.
Actually
you
don't
want
other
people
to
know
that
you
necessarily
agree
to
something
with
another
party
I'll.
A
D
A
Right
and
so
if
you
tried
to
throw
a
different,
if
you
change
your
a
database
in
the
interim
and
now
you
you
have
a
different
from
the
MSA
and
you
you're,
calculating
from
75
and
and
there's
never
been
75
units
ordered
your.
You
will
not
be
able
to
place
your
new
proof
or
nullify
the
original
MSA
state
on
the
main
net,
because
you
won't
be
able
to
so
I
mean
you
can
change
your
own
database.
All
you
want.
We
value
are
no
longer
in
a
state
of
consistency.
Let.
D
Me,
let
me
just
wind
back
the
question
again
John,
because
it
because
you
answered
something
different
there.
The
question
is
what
is
exposed
on
this
main
net.
That
would
allow
other
parties
to
see
that
these
two
parties
are
working
together
or
to
see
what
volume
of
something
some
types
of
transactions
they
might
have
is.
A
And
the
point
is
you
could
point
a
you
know
the
way
we're
doing
it,
especially
if
you
do
it
properly
and
you
have
some
and
you
have
the
right,
you're
doing
it
on
a
cadence
with
some
chaff,
an
AI
looking
at
the
main
net,
trying
to
figure
out
who's
doing
what
or
trying
to
get
some
kind
of
classifier
off
of
relationships,
you're
conducting
or
just
to
figure
out
what
you're
doing
and
what
your
business
activities
are.
What
your
relationships
are
that
you
know
to
them.
A
So
that's
what
goes
on
the
main
net,
but
what's
not
what's
interesting,
isn't
the
hash
its?
How
the
hash
got
there
and
yeah
and
it
should
look
like
nothing
to
anybody
who
isn't
involved
in
it.
It
should
look
like
sameness.
Think
you're,
like
oh
there's,
there's
a
hash
there.
Somebody
put
a
hash
on
the
main
that
whatever
I
don't
know.
Well,
you
know,
and
if
you
do
it
right,
you
don't
know
which
hash
is
mean
anything
at
all,
so
most
of
them
any
of
them
might
mean
nothing.
A
Okay,
I
want
to
I,
want
to
switch
gears
here
and
talk
about
what
you're
going
to
expect
to
see
in
when
we
release
the
repo.
So
this
is
one
of
the
things
we're
working
real
feverishly
on
right
now,
as
you
can
imagine
documentation,
the
best
documentation
comes
right
at
the
end,
so
you
start
wiggling.
Those
fingers
are
really
fast.
So
you
know
this
is
this:
was
what
you'll
see
them
in
when
we
liven
up
the
repo
and
I'd
love
to
see
by
the
way
kudos
to
everybody?
That's
been
using
the
chat
so
well.
A
We
will
put
that
into
the
slack
the
baseline
slack
channel,
which
you
can
get
to
by
going
to
baseline
protocol
org,
and
you
can
sign
up
for
the
slack
and
we'll
put
this
into
the
slack
right
Tory.
We
can
do
that
and
and
we
can
keep
the
conversation
going
from
there,
because
this
is
great
questions
in
here.
We
won't
have
time
to
go
into,
but
I
wanted
to
show
you
this
so
that
we
can.
A
So
you
can
comment
and
say:
hey
you're,
missing
something
you
know
that's
what
we
want
to
make
sure
is
that
that
you
aren't
surprised
by
what
you
see
and
that
you're
getting
the
information
you
need
to
do
things
when
it
goes
live.
So
we
have
getting
started
with
you
know.
So
we're
going
to
start
with
the
radish
demo.
You'll
be
able
to
go
into
the
actual
both
figma
and
live
demo
you'll
be
able
to
build
the
demo
and
you'll
you
can
you
know,
like
I,
don't
know
anybody
who's
code?
A
Who
saw
it's
the
only
code,
you
love
is
the
code.
You
wrote
yourself
right
so
I'm
sure
that
a
lot
of
people
have
points
of
view
about
the
code.
That
was
that's
in
there
remember
it's
POC
code.
It
needs
to
be
abstracted
and
then
it
needs
to
be
generalized,
and
that
is
the
job
of
the
community.
That's
what
we're
here
to
do
so
everything
about
this
documentation
should
be
preparing
you
to
to
lead
in
your
section
of
that
world.
As
you
know,
whatever
benefits
you
get
started
a
visualization
modifying
things.
A
So
so,
where
could
you
mod
this
like?
If
you
wanted
to
write
an
invoice
procedure,
how
would
you
mod
what
we
have
in
the
current
demo
to
make
it
work
for
invoices
and
then
going
from
demo
to
protocol
well
talking
about
how
you
do
that?
Looking
at
the
time
here,
my
screen
doesn't
have
a
time
on
it,
but
so
baseline
protocol
I
see
what
languages
were
used.
A
Karthik,
you
might
want
to
discuss
that
I
mean
one
thing
that
is
notable.
Is
that
we're
using
graph
QL
for
that?
For
a
lot
of
this,
we
have
an
OPA,
so
the
baseline
protocol
open
source
community
how
to
get
involved.
What
are
the
you
know,
guidelines
for
contributing
the
baseline
process,
something
more
or
less
what
we
just
discussed,
stats
and
specs
so
like?
A
A
In
order
to
pay
for
their
trains
for
their
the
gas
on
on
running
these
proofs
and
barriers
to
enterprise
adoption
of
public
blockchain,
which
you
can
find
on
the
on
the
web
from
the
main
networking
group
sort
of
the
list
of
ten
top
reasons,
we've
got
a
road
map,
section
components
right:
the
server
messenger,
zero-knowledge
service
api's,
and
this
we're
getting
into
what
we
want
to
do.
Build
these
components
off
of
the
radish
POC
work.
A
So
we're
gonna,
take
the
radish
POC
work
and
build
a
generalized
server
or
a
more
abstract,
idsurvey
and
added
a
more
abstract
and
set
of
interfaces
for
messaging,
etc.
Making
this
something
that
that
any
ERP,
CRM
SCM
or
any
other
system
of
record
could
integrate
into
their
own
product
and
sell
quickly.
A
And
then
you
know
how
to
baseline
your
product
supply
chain
management,
ERP,
core
banking,
Enterprise
middleware.
We
actually
have
a
core
banking
team
on
already
in
neo
Cova,
so
I'm,
hoping
that
they'll
do
some
work
in
there
and
then
baseline
basics
go
glossary
and
FAQ
and
such
please
send
us
any
comments
about
things.
The
other
things,
topics
that
you'd
like
to
see
in
the
documentation
be
grateful
for
that.
B
A
C
A
A
good
idea,
so
I'd
say
you
know,
maybe
as
early
as
next
Friday,
but
not
before
next
Friday
and
we'll
figure
that
out
going
forward
and
you
again
Jory
and
team
on
the
Oasis
team,
we'll
make
sure
everybody
is
notified.
You
know,
I've
been
I
used,
Twitter
a
lot
I
didn't
use
to,
but
I've
been
for
this.