►
From YouTube: Baseline Summit 2020 Track1 Education
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
B
I
also
have
the
live
stream
going
up
right
now
on
youtube,
so
we're
going
to
see
if
we
can
make
the
working
session
from
both
people
that
are
up
on
youtube,
along
with
everyone,
that's
actually
registered
and
in
the
zoom
chat.
So
we'll
give
this
some
time.
I
see
that
we
have
around
18
right
now
that
are
piling
into
the
zoom
chat.
So
that's
cool
and
we
have
six
that
are
on
the
live
stream.
B
So,
let's,
let's
just
wait
a
second
I'm
just
taking
a
look.
I'm
gonna
share
my
screen.
B
And
to
be
honest
with
everyone,
I'm
in
no
rush,
because
we're
gonna
have
this
going
for
the
next.
I
don't
know
what
five
six
seven
hours,
something
like
that
until
until
five
pm
eastern
so
we're
here
to
hang
out
and
do
some
work
and
talk,
let's
see
so
we
are
still
we're
still
collecting.
I
see
that
this
see
that
this
room
is
is
fairly
popular
right
now,
let's
see
what
other
sessions
are
going
on
right
now,.
B
So
here
we're
going
to
be
diving
into
a
little
bit
about.
You
know
what
the
baseline
protocol
is.
We're
going
to
start
to
get
into
the
experience
of
it
we're
going
to
talk
about
the
product
cookbook.
However,
if
you
feel
that
you
want
to
get
right
into
the
blockchain
client
improvement
session,
that's
that's
going
on
right
now,
so
please
feel
free
to
jump
into
there
and,
let's
jump
back
into
our
breakout
one.
B
B
Let's
see
looks
like
looks
like
we
have
a
pretty
sizable
crew
in
here,
so
we're
gonna
go
ahead
and
get
started.
It's
11
o'clock,
eastern.
So
that's
that's
the
kickoff
of
of
the
session.
I
want
to
thank
everyone
that
registered
for
the
baseline
summit
in
general.
Thank
you
so
much
again,
nick
and
team
can't
can't
tell
you
enough,
you
know
thank
you
for
organizing
this
event
and
we're
gonna
go
ahead
and
get
started.
So
my
name
is
dan
orkin
co-founder
here
with
envision
blockchain.
B
Actually
in
the
same
room
with
me,
we
have
another
co-founder.
We
have
jason
pansis,
so
you
might
hear
from
either
of
us
at
the
same
time,
but
just
to
avoid
some
crazy
feedback
over
here.
My
screen
will
be
showing
so
apologize
for
staring
at
my
face
for
the
next
seven
hours
or
so
so
you
know
I'll.
Just
give
you
a
little
bit
of
background
about
myself
and
you
know
I
think
it'll
be
good
I'll.
Just
give
you
a
little
tour
around
the
kegel
chat
around
this
around
this
presentation.
B
The
one
thing
that
I
like
already
is
that
I
see
that
people
are
starting
to
click
around
and
please
feel
free
to
click
around
okay
and
just
to
actually
before
I
talk
about
myself.
Let's
just
talk
about,
you
know
how
to
navigate
around
this
working
session.
What
to
expect
I'm
gonna
call
out
a
whole
bunch
of
things
throughout
this
throughout
this
time.
So
it's
just
good
that
everyone
is
familiar
with
it.
So
naturally
you
have
your
tabs
at
the
top
and
we're
gonna
start
there.
B
So
at
the
very
top
you
have
instructions.
Obviously
I
think
everyone
already
knows
how
to
get
in
here.
I
see
a
whole
lot
of
clicking,
so
that's
great.
We
have
we
have
over
four.
We
have
44
total
people
putting
their.
You
know
mouse
and
clicker
into
these
screens,
which
is
awesome.
I
expect
at
the
end
of
this
day,
content
to
change
and
that's
and
that's
exactly
the
point
of
this
one
right
so
the
next
tab
over
and
I'm
sharing
my
screen
here.
The
next
tab
is
a
session
schedule.
B
If
you
will
starting
from
11
a.m,
to
12
p.m,
again
again,
all
times
or
eastern
here
we're
gonna
be
talking
about
the
intro
to
the
baseline
protocol
and
some
of
the
standards
after
that,
we're
gonna,
really,
you
know,
put
our
hands
into
some
of
the
product
cookbook
and
like
what
nick
mentioned
in
the
opening
opening
speech
is
so,
if
you've
seen
some
of
the
first
demos
that
came
out
with
radish
34,
there
was
a
lot
of
work
within
the
community
that
was
put
out
the
first
demo
with
sap
and
dynamics
365..
B
So
we're
going
to
have
a
working
demo
for
some
brave
souls
to
go
ahead
and
share
their
screen,
we're
going
to
give
them
credentials
and
we're
going
to
actually
have
some
some
some
individuals-
click
through
you
know,
starting
at
the
very
beginning
of
what
the
use
case
says
and
going
through
and
calling
out
what
specific
baseline
you
know.
Components
should
be
realized
at
that
particular
click
and
while
we're
not
necessarily
going
to
be
talking
about
codes,
this
would
be
great
for
system
admins.
B
This
would
be
great
for
those
that
haven't
seen
anything
about
baseline,
but
just
want
to
see
what
things
are
all
about
right,
so
we're
we're
definitely
going
to
do
our
best
to
really
break
it
down
after
that.
What
we're
going
to
do
is
dom
steele
is
going
to
be
introducing
this
baselined
salesforce.
So
so,
just
like
we'll
be
talking
about
this
microsoft
dynamics,
365
baseline
experience,
dom
steel
is
also
going
to
be
talking
about
that
at
3
p.m.
B
Eastern
from
3
p.m,
to
4
p.m,
we're
going
to
be
we're
going
to
be
hosting
stefan
schmidt
who's
going
to
be
talking
about
baseline
sap,
so
that
would
be
really
cool,
definitely
recommend
that
you
stick
around
for
that
and
then,
of
course,
from
4
p.m,
to
5
p.m.
We're
gonna!
Actually,
you
know,
combine
everything
all
together
and
talk
about
this
baseline
cookbook
round
table.
So
we're
going
to
have
avia
myself
we're
going
to
have
kyle
thomas
we're
going
to
have
stephon
schmidt,
dom
steele
and
really
you
know
everybody
else.
B
So
I
just
mentioned
a
couple
of
the
folks
that
helped
and
and
planned
the
session.
But
again,
this
whole
entire
thing
that
we're
talking
about
is
not.
B
For
you
know
it's
not
intended
to
look
like
a
presentation,
but
rather
you
know
it's
it's
really
a
discussion,
so
I
know
that
we
talked
about
the
zoom
etiquette
and
keep
yourself
mute,
but
I
do
want
people
to
unmute
themselves
and
I
do
want
everyone
to
go
ahead
and
chat
within
the
chat
box
and
we're
gonna
be
monitoring
that
also
for
those
that
haven't
registered
to
the
baseline
summit.
You
probably
are
watching
on
youtube.
I'm
checking
my
second
screen
right
here.
B
I
see
that
we
have
16
people
that
are
watching
so
also
just
because
you're
not
registered
doesn't
mean
that
you
can't
participate
if
you
happen
to
be
watching
this
on
youtube
right
now
through
the
live
stream.
I'm
literally
watching
out
for
your
comments
over
here.
So
as
you
comment
and
talk
about
it,
we're
going
to
incorporate
your
feedback.
Okay.
So
again,
so
that's
that's
the
session
schedule,
the
notes.
B
The
notes
is
really
for
everybody
to
put
your
ideas
down.
Put
your
thoughts,
I'm
a
big
fan
of
you
know
the
parking
lot
idea
right.
So
if
there's
an
idea
can't
come
to
no
pawn
can't
come
to
a
consensus
on
this.
If,
if,
if
there's
something,
that's
not
related,
but
it's
still
a
good
point.
Nobody
wants
to
brush
any
of
that
off
and
we're
going
to
go
ahead
and
put
that
into
the
notes.
Section
jamboard
jamboard
is
pretty
cool.
That's
your
virtual
whiteboard
there
was.
B
There
was
a
comment
earlier
during
during
the
opening
comments
on
hey.
Is
anyone
going
to
be
talking
about
4g
anything
to
do
sorry
with
5g
and
telco,
and
while
none
of
the
presentations
talk
about
that
specific
use
case?
What
will
be
interesting
is
that
we
do
want
to
give
some
time
for
that,
and
we
do
want
to
talk
about
that
because
you
know
when
we
talk
about
the
first
reference
implementation,
which
is
radish
34
I'll,
be
talking
a
little
bit
about
the
process
flow
right.
We
start
with.
B
That
needs
to
be
answered
by
a
proposal
to
msa,
then
the
issuance
of
the
po
and
so
on
and
so
forth,
and
these
are
different
workflows
if
you
will
so
different
actors,
and
we
can
use
this
whiteboard
session
to
whiteboard
okay
clicking
out
of
there
getting
onto
the
next
tab
diagrams
and
draw
it's
essentially
the
same
thing
as
jamboard,
except
it's
already
embedded
slides
is
where
we're
going
to
spend
the
majority
of
the
time
within
the
slide
section,
because
if
you
recall
the
schedule
that
we
just
discussed
the
schedule
is
100
aligned
to
these
slides.
B
So
we'll
be
we'll
be
talking
about
the
intro
baseline
protocol,
the
standards
and
monitoring
applications
experiencing
d365
salesforce
sap
et
cetera.
Again.
This
is
your
recipe
for
the
cookbook
in
order
to
make
your
own
products
in
order
to
baseline
the
applications
that
you
use
on
a
you
know,
day
in
and
day
out
basis.
So
we'll
be
talking
about
that
and
last
but
not
least,
probably
the
most
important
tab,
in
my
opinion,
is
the
cookbook
ideation.
B
So
the
cookbook
ideation
is
a
very
simple
embedded
google
sheets,
where
it
it's
exactly
that
it's
your
intake
for
cookbook
ideation.
We
can
take
this
as
we
have
good
ideas
and
we'll
be
having
call
outs
throughout
this
workshop.
Asking
you
to
literally
go
in
here
write
down
your
ideas
that
you
have
write
down.
Your
use
cases
come
up
with
your.
You
know.
As
you
see,
some
of
the
things
that
we'll
be
talking
about,
put
down,
feature
requests,
I'd
love
for
you
to
show
this
or
hey
I've
been
working
on
this.
B
I
think
it
would
fit
really
good
with
there
throw
it
in
here.
Put
down
the
name
of
your
use
case,
put
down
the
name
of
your
feature,
put
down
the
system
that
you
think
that
it
should
work
with
right,
we'll
be
showing
how
things
look
like
in
d365,
we'll
be
showing
how
things
look
like
in
sap,
we'll
be
showing
how
things
look
like
in
salesforce.
B
We
showed
earlier
how
things
look
like
in
google
sheets
excel
is
another
one
that
you
can
do
it
with.
You
know,
there's
going
to
be
a
connector
that
we're
going
to
be
showcasing
there's.
So
many
things
that
so
many
features,
and
so
many
use
cases
that
are
just
important
and
not
all
of
us
thought
about
or
put
put
the
time
and
the
energy
to
it.
B
Just
yet
and
that's
where
the
community
is
so
big
right
and
that's
why
it's
so
great
to
be
part
of
this
open
source
community,
because
that
really
accelerates
time
to
market
it
accelerates
the
ideation
and
so
on
and
so
forth.
B
Want
to
ask
anyone,
and
I'm
looking
here
on
youtube,
looks
like
we're
getting
around
19
right
now
and
not
too
sure
who's.
How
many
that
we
have
in
the
zoom
chat.
But
before
I
continue,
are
there
any
questions
on
how
to
navigate
before
before
we
go
on.
E
B
Anyone
want
to
write
that
into
the
ideation
baselining
brain
thoughts.
I
think
that'd
be
pretty
that'd,
be
pretty
cool.
You
know
what,
for
some
reason,
my
chat
isn't
popping
up
on
here.
So
if
there's
chats
and
jay
or
anyone
else
over
here,
just
let
us
know
happy
to
feel
them
at
any
time.
Honestly
and
I'm
gonna
do
a
whole
lot
of
this
pausing
and
asking
asking
for
feedback
a
little
bit
about
my
background,
just
to
understand
where
I'm
coming
from
and
and
and
and
how
we
got
here
so
again.
B
My
name
is
dan
orkin
with
envision
blockchain
and
we
joined
the
baseline
protocol
fairly
fairly
early
right
when
it
launched
actually
and
happy
to
have
seen
the
evolution
of
it.
All.
I
personally
come
from
a
background
started
out
in
telecom.
B
So
actually,
I'm
pretty
interested
in
that
in
that
in
that,
in
that
comment,
around
4g
5g
and
things
like
that
started
out
with
telecom,
moved
on
to
non-profit,
moved
on,
to
hospitality,
used
to
work
for
windham
worldwide
and
then
had
started
an
I.t
consulting
company
that
focused
in
project
management,
consulting
and
microsoft,
project
online
and
project
server
implementations,
as
as
we
as
we
started,
consulting
with
fortune
500
and
the
offices
of
the
pmo,
ended
up
doing
a
whole
lot
of
integrations
with
sap
systems,
with
jira
systems
to
to
project
online
from
service
now
to
project
online
and
project
server
and
workday
as
well,
so
on
and
so
forth.
B
Jason.
Another
co-founder
I'll
talk
about
him
as
if
he's
not
sitting
right
here,
he
actually
has
a
background
started
out.
Trading
actually
started
out
as
a
commercial
airline
pilot
then
went
on
to
trading
commodities
and
then
went
on
to
supply
chain
and
logistics.
Opening
up
a
whole
series
of
offices
across
across
the
across
the
united
states,
actually
in
2016
something
along
those
lines.
Jason
gave
me
a
call
one
day
and
said:
hey
you
need
to
look
at
this
ethereum
stuff.
B
You
need
to
take
a
look
at
this
bitcoin
stuff.
Maybe
it
was
speculation
at
that
time,
but
I
mean
hey
who
who
didn't
start
out
that
way,
the
more
that
we
looked
into
it
because,
obviously
right
you
have
to
do
your
due
diligence
and
you
look
into
it
the
more
you
do,
your
due
diligence.
You
realize
that
there
is
such
a
great
business
need
to
incorporate
a
blockchain
component
into
a
solution.
So
lo
and
behold
in
early
2018,
we
had
started
envision
blockchain
as
a
blockchain
system.
B
Integrator
specific
with
you
know
the
microsoft
ecosystem,
helping
customers
with
end-to-end
solutions.
So
when
you
know,
as
as
we
had
talks
with
customers,
there
was
stumbling
blocks
that
we
uncovered.
When
discussing.
You
know
private
blockchains,
because,
as
as,
as
we
all
know,
discussing
public
blockchain
with
enterprise
organizations,
it
gets
tricky.
It
gets
tough.
There
is
a
lot
of
education
that
needs
to
come
with
that,
especially
here
in
the
united
states,
maybe
not
so
much
overseas.
B
This
is
how
we
can
start
to
discuss
how
you
can
keep
business
systems
in
check
and
in
sync,
while
still
keeping
all
of
your
business
off
chain
in
the
systems
that
you
probably
spend
a
lot
of
money
implementing,
whether
it's
an
sap
system,
dynamic
system
sequel,
could
also
be
your
system
of
records
so
on
and
so
forth.
B
So,
for
that
is
a
really
quick
intro
into
myself,
and
I
think
it
may
help
out,
as
we
start
to
talk
about
slides,
so
so,
let's
get
into
it
here.
B
B
I
could
open
up
into
you
know
the
main
thing,
but
I
guess
I'm
just
asking
if
I
stay
on
this
slide,
is
that
good
enough
for
everyone?
I
get
the
thumbs
up
over
here
from
jason.
How
about
how
about
some
other
folks.
B
Looks
good
cool
so
I'm
going
to
stay
on
this
one,
because
what
this
is
going
to
do
is
as
we
go
through
these
slides,
I'm
going
to
call
out
other
sessions
where
you
can
actually
get
deeper
into
the
concepts
that
we
start
to
discuss.
Okay,
so
another
thing
is
that
we're
also
keeping
track
of
the
slack
channel.
So
we
have
we
have
the
zoom
chat
going
on.
We
have
kiko
chat.
We
have
the
slack
chat.
We
have
the
live
stream.
B
I
don't
think
that
there's
any
shortage
of
communication
channels,
so
so,
let's
get
into
this
one,
how
to
make
the
most
from
this
breakout
session
first
and
foremost,
let's
be
respectful.
I
don't
think
that
that's
an
issue
so
far,
everyone
in
the
community
has
been
awesome.
Respect
is
always
number
one.
We
want
different
opinions,
though
right,
so
just
because
what
you're
seeing
is
like.
What's
written,
it's
not
the
final,
it's
not
the
ultimate
and
that's
where
number
two
comes
in.
We
need
everyone
to
stay.
Interactive
it'll
get
really
boring.
B
If
I
just
talk
for
for
hours
and
hours
and
hours
on
end
one,
my
voice
can
get
monotone
and
to
it's
just
one
opinion:
just
just
doesn't
make
it
work
right.
Number,
three
iterations
and
ideas
on
all
slides
and
content
would
be
ideal.
B
We've
done
is
we've
combined
and
I'm
speaking
about
envision.
We've
worked
with
folks
within
the
baseline
community
for
the
past.
I
don't
know
how
many,
how
many
months
it's
been
going
on.
I
want
to
say
it
was.
It
was
announced
last
last
last
may
or
something
something
along
those
lines,
maybe
even
before
that
we've
been
working
on
creating
this
content
on
how
to
introduce
the
baseline
protocol,
how
to
showcase
the
smart
contract,
smart
contract
architecture,
how
to
talk
about
the
standards?
B
Why
are
we
talking
about
the
standards?
How
does
that
relate
to
core
interfaces
so
on
and
so
forth?
So
you're
gonna
see
me
doing
this
like
stop
and
go
approach
as
I
get
to
the
slides,
I'm
gonna
stop
and
I'm
gonna
ask
for
people's
opinions
on
that.
We
are.
You
know
this
is
our
first
go
at
doing
this
baseline
summit
as
a
working
session?
B
It's
not
a
presentation,
we're
not
new
to
workshopping
by
any
means
so
consider
this
one
large
workshop,
where
there's
over
50
people
participating
right
now
so
again
we're
going
to
change
these
slides
and
hopefully
that
if
you
haven't
heard
about
the
baseline
protocol-
or
maybe
you
know,
you
need
to
explain
it
to
your
boss
to
your
colleagues
to
your
workers
to
your
you
know
significant
other
whatever
it
is,
hopefully
that
this
deck
is
going
to
be
able
to
be
translated
in
the
way
that
you
want
it
to
be
discussed
each
slide.
B
Each
of
the
slide
sections
are
aligned
to
the
content
outlined
in
the
schedule.
We
already
discussed
that
and
of
course,
continue
the
conversation
on
slack.
This
is
literally
the
slack
channel
that
is
devoted
to
this
breakout.
One
experience
in
the
baseline
protocol
after
the
session
is
done
after
today.
After
tomorrow,
you
know
the
conversation
will
continue
on
slack.
B
That
is,
if
everyone
continues
it
all
right.
So
so,
let's
keep
going
here
working
sessions
to
keep
in
mind
again.
I
just
want
to
call
this
out.
There's
the
core
interfaces:
persistent
messaging
format,
zk
circuit
improvement
and
new
features.
That's
going
on
in
breakout
session
two.
I
see
that
there's
a
couple
folks
there.
I
don't
believe
that
there
is
actually
a
session
happening
right
now,
but
again
that
is
something
the
global
phone
book
project
I
mean.
That's,
that's
a
super
important
one
as
ease
of
discoverability
is
one
of
the
key
attributes
to
leveraging.
G
G
B
And
next
is
scaling
baseline
work
step
throughput,
also
very
important
again,
if
there's
a
low
transaction
throughput-
probably
not
that
important,
but
as
you
start
to
get
more
transactions
that
are
being
posted
on
mainnet
and
we
can
talk
about
what
those
transactions
are
in
a
little
bit.
Scaling
is
always
top
of
top
of
mind.
Now
again,
this
is
use
case
by
use
case.
Specific
some
use
cases
don't
require
that
kind
of
throughput,
and
we
can
discuss
that
as
well.
Tokenization
and
digital
assets
that's
happening
over
here
on
breakout
six.
B
You
see
that
there's
some
folks
over
there
zk
circuit
libraries-
I
don't
know
if
this
was
updated,
but
I'm
willing
to
bet
that's
in
core
interfaces
and
blockchain
client
support
and
baselining.
That
session
is
actually
happening
right
now
and
that's
in
breakout
session.
Seven
you're
gonna
see
that
there's
going
to
be
a
need
not
going
to
be.
There
is
a
need
for
for
for
for
off-chain
communication
to
a
mainnet,
that's
done
via
client.
Of
course.
B
Right
now,
there's
gonna
need
to
be
specific,
let's
say
baseline
parameters
that
need
to
be
configured
for
the
client
in
order
to
work
right.
So
that's
what
that
whole
discussion
is
all
about,
so
without
further
ado,
we're
going
to
go
ahead
and
get
started
into
this.
One
enter
the
baseline
protocol
and
here's
kind
of
how
we
start
talking
about
it
and
again
now
nick
did
a
great
job
introducing
the
baseline
protocol.
B
I'm
gonna
try
to
do
the
same
thing,
but
in
a
little
bit
of
a
different
fashion.
What
we
aim
to
do
is
again
change
the
slides,
there's
different
screen
shots.
If
there's
different
pictures,
you
know,
please
feel
free
to
comment,
we're
going
to
be
monitoring
everything
again.
B
I
J
You
can
you
can
break
the
slides
out
separately
and
go
into
present
mode.
If
you
want
dan.
E
There
I
see,
if
you
scroll
back
down.
B
B
So
I'm
gonna
go
back
and
forth,
but
I
like
this
one
this
this
this
view
is
a
little
bit
bigger,
cool,
all
right
so
again
introducing
the
baseline
protocol
how
to
introduce
the
baseline
protocol
right.
So
this
was
actually
the
date
I
was
looking
for
so
march.
4Th
march
4th
2020
over
here
was
introduced.
This
press
release
microsoft,
ey
consensus,
talk
about
the
new
way
for
big
business
to
use
public
ethereum.
B
B
Let
everyone
know
also
that
the
reason
why
we're
going
through
this
through
the
different
iterations,
because
you
can
literally
just
go
ahead
and
download
the
entire
presentation
we
did
that
on
purpose,
because
again
we
want
people's
input
so
that
we
can
go
ahead
and
make
changes,
and
then
you
can
take
that
back
and
actually
give
it
to
your
boss
and
say
this
is
why
I've
been
this
is.
This
is
the
project
I
want
to
work
on,
and
this
is
how
you
can
start
to
explain
it
again.
B
We
have
a
screenshot
here
of
the
baseline
protocol,
just
kind
of
showcasing
what
the
github
repository
looks
like
again
submit
your
github
over
to
john
walpert.
I
believe
that
it
was
he'll.
He'll
he'll
get
you
access
into
here.
We
really
want
to
promote
the
ability
to
contribute
okay.
B
You
know
one
of
the
ways
that
we've
been
able
to
discuss
this
is
we
start
saying
who
do
you
do
business
like?
Who
do
you
do
business
with
or
who
does
business
with
each
other
right?
We
want
to
be
able
to
identify
counterparties
and
we
want
to
be
able
to
identify
the
systems
of
record
within
those
counterparty
organizations.
B
If
you
will,
let
me
ask
everyone
a
question:
how
else
would
you
recommend
to
start
introducing
the
concept
of
the
baseline
protocol
now,
I'm
assuming
that
folks
are
not
familiar
with
the
baseline
protocol,
sorry
that
that
they
are
familiar
with
the
baseline
protocol,
so
this
is
less
of
a
one-on-one
101,
even
though
it
kind
of
feels
like
it.
Let
me
ask
you
to
the
crowd.
How
else
do
you
start
this
conversation.
F
Establishing
new
inter-enterprise
relationships,
so
thinking
about
you,
know,
who's
really
shelling
out
for
that
onboarding
one-to-one
instantiation,
because
that
party
is
likely
shelling
out
for
a
lot
establishing
a
lot
of
those
relationships
for
each
one-to-one,
and
so
an
opportunity
for
greater
efficiency.
Plugging
into
a
community
would
allow
them
to
significantly
minimize
those
kinds
of
onboarding
costs.
J
How
often
are
you
chasing
other
people
for
information
that
should
just
be
available
through
an
application
or
verifying
information?
Oftentimes
like
at
a
quarter
close
or
a
financial
close
or
daily
close?
You
know,
there's
a
lot
of
of
you
know
chasing
of
information
right,
calling
people
on
the
phone
or
sending
them
email.
Hey!
Is
this
value
right?
Is
this?
You
know
the
right
record,
etc.
E
G
H
I
I
think,
there's
currently
a
lot
of
effort
of
consortia
trying
to
build
blockchain
networks
for
just
a
purpose
or
for
jaztime
consortium,
and
that's
that's
a
lot
of
effort
with
regards
to
infrastructure
management
security.
H
Many
times
those
networks
have
some
lack
of
security
concerns
because
of
of
lack
of
expertise
in
their
teams,
and
you
can
just
use
public
networks
because
they're
already
there.
So
you
can
save
all
that
effort
and
those
networks
are
more
secure
because
they
are
under
a
constant
attack
because
of
the
fact
that
they
are
public.
B
You
know-
and
I
think
that
that's
that's
a
really
that's
a
really
key
point.
You
know
and
and
I'll
share
a
little
bit
of
insight
from
one
of
our
customers
that
we
were
talking
to
before
the
baseline
protocol
was
even
a
thought,
a
thought
in
our
mind.
It
was
when
you
know,
enterprise
organization.
I
don't
think
too
much
has
changed,
have
been
discussing
literally,
you
know
private
blockchains
over
public
blockchains,
and
there
was
this
this
issue
in
their
mind.
B
They
have
this
big
whiteboarding
session
on
well,
what
happens
if
walmart
has
their
private
blockchain
and
their
private
consortium,
and
this
organization
wasn't
allowed
to
be
part
of
it
and
then
what
happens
if
craft
has
theirs
and
then
what
happens
if
another
another
company
has
theirs?
B
Does
this
company
have
to
join
one?
Do
they
have
to
create
one?
How
how
can
they
leverage
this
kind
of
the
values
that
decentralized
networks
provide
without
but
with,
but
but
but
there's
all
these
stumbling
blocks,
and
it's
exactly
like
you
just
mentioned
right.
So
it's
this
ease
of
discovery,
kind
of
like
what
evan
mentioned
as
well
right,
it's
like
who
spends
time
and
money
on
onboarding
these
sort
of
business
participants,
which
also
speaks
to
who
isn't
doing
business
with
each
other
and
should
like
what
are
these
blockers?
B
So
that's
good
we're
going
to
come
back
to
this
one,
but
just
in
the
essence
of
time,
I'm
going
to
keep
this
moving
here.
What
I
hope
to
do
now,
I'm
thinking
about
it-
and
this
group
is
much
more
interactive
than
I
would
have
liked
to
give
credit
for
at
the
beginning
coming
in
because
you
just
never
know.
B
The
next
slide
was
something
that
came
from
a
working
session
that
that
we
had
when
the
baseline
protocol
first
came
out
and
it
was
a
working
session
on
it
was
it
was
literally
called.
There
was
an
epic
that
was
called
like.
Why
now
like.
Why
should
we
care
about
investing
our
time
into
the
baseline
protocol,
when
literally,
we
have
other
initiatives
going
on
right
now
and
I'm
sure
that
everyone
can
speak
to
prioritization
within
your
own
day-to-day
right.
So,
of
course,
with
the
innovative
innovators
dilemma,
we
had
from
clay
christensen.
B
Imagine
you
could
do
x
without
limiting
y,
and
this
is
where
this
idea
of
the
cookbook
really
stemmed
from
it's
like
this
value
cake
where
you
have
layer,
one
and
and
the
layers
aren't
really
in
any
significant
order.
It's
just
you
know
layer.
One
was
just
basically
talking
about.
You
know
when
you
look
at
b
to
c
environments,
they're
much
more
mature
than
b2b
environments,
infrastructure
experience,
just
just
the
ease
right.
B
B
I'm
not
going
to
get
political,
but
the
infrastructure
that
government
voting
is
on
is
is
small,
is
is,
is
not
very
updated,
as
opposed
to
like,
let's
say
the
financial
software
that
we
use
for
trading
right.
You
see
everything
instantly
right.
Now:
bang,
bang,
bang!
So
there's
there's
this
need
for
layer.
B
One
two
to
increase
the
b2b
world
layer
two
is
that
we
wanna
be
able
to
provide
value
to
business
partners
of
all
sizes,
not
just
the
large
ones,
but
also
the
small
companies
that,
for
example,
in
radish
34,
we'll
talk
about
the
procurement
use
case.
What,
if
there's
a
small
company
that
just
doesn't
have
the
it
set
up
ability
as
a
larger
company,
but
they
have
the
supplies
and
they
have
the
good
service
that
as
a
buyer,
you
want
something
to
keep
in
mind.
B
Layer
three
is
that
that
you
ensure
the
expectations
can't
be
changed
whatever
you
agree
upon,
it
happens,
and
you
can't
really
get
that
unless
you
work
in
an
immutable
way
right.
I
think
that
we
all
know
that
I'm
preaching
I'm
preaching
to
the
choir
over
here
layer
four
could
potentially
be
the
most
important.
Maybe
that's
why
it's
on
the
bottom.
I
don't
know.
B
I
know
I
said
that
they're
all
important,
but
we
could
talk
about
this
one
so
layer
two
is
we
provide
a
cso,
compliant
technology
stack
and
there's
a
methodology
behind
that,
and
that
gave
birth
to
the
cookbook
idea
back
in
the
day,
and
the
reason
for
that
is
because
you
can
really
mix
and
mingle
many
different
things
in
order
to
create
the
recipe
for
the
product
that
your
business
needs
right.
So
we'll
we'll
hang
on
this
one
for
just
a
second
in
this
period
of
time,
we'll
just
keep
going
slide.
B
11
here
talks
about
the
baseline
protocol
is
not
a
product,
it's
not
a
solution.
It's
not
a
coin!
You
can't
trade,
it
buy
it
sell
it
doesn't.
You
know,
we've
been
seeing
a
whole
lot
of
funny
things
on
the
slack
channel
people
wanted
to
know.
When
is
it
icoing
when
you
know
none
of
that?
It's
it's
it's!
It's
a
it's
a
pattern,
it's
a
pattern
that
has
really
you
know,
showing
in
the
case
of
radish
34,
there's
really
three
fundamental
b2b
interaction
types.
B
You
have
contractual
agreements,
you
have
business
transactions
and
you
have
this
transfer
of
funds
of
the
assets
or
something
like
that.
So
here
what
we
aim
to
do
is
we
wanted
to
show
a
traditional,
disconnected
system.
You
see,
there's
there's,
there's
edi
connecting
it
and
that's
a
big
piece.
You
have
company
a
company
b,
they're
working
and
then
you
know
just
like
nick
said.
In
the
opening
comments,
you
have
faso
mail,
you
have
email,
you
have
text
message,
you
have
all
these
ways
that
you
discuss
and
contribute.
B
Cool
okay,
yeah!
Thank
you!
So
so
again
here
you
know,
but
then
we
have
the
other
side
the
blockchain
base
right.
So
everyone
is
in
sync:
everyone
stays
in
again
we'll
go
back
to
that
one.
Unless
there's
any
comments
here
on
this
slide,
I
just
I
just
want
to
capture
that.
Is
there
anything
that
you
don't
agree
with
or
anything
that
you
do
agree
with
before
we
continue.
B
B
B
So,
let's
see
all
these
different
things
right,
so
we
have
again
the
core
interfaces
group,
which
is
breakout.
Two,
that's
how
you
connect
your
system
of
record
to
your
baseline
stack,
which
we'll
talk
about
which
would
also
the
connection
to
mainnet,
is
included
in
the
baseline
stack,
but
it's
via
these
core
interfaces
that
allows
the
connectivity
between
your
product,
your
system
of
record,
whether
it's
a
custom
web
app
or
it's
a
dynamics,
365
or
whatever
right,
sap,
salesforce
oracle.
You
connect
via
core
interfaces.
B
How
does
every
company
now
now
we're
going
to
roll
with
this
assumption
right
now
that
each
company
is
operating
on
their
own
system
of
records?
So
we
have
d365
with
one
company
sap
with
another
company
salesforce
with
another
company
oracle
with
another
company.
How
do
they
easily
find
find
each
other?
B
The
blockchain
client
support
just
put
that
right
here
in
the
middle
again,
we
spoke
about
that.
That
session
is
going
on
right
now,
product
cookbook,
we're
talking
about
oracle
systems,
sap
systems,
salesforce
dynamics,
and
we
urge
you
use
this
tab
right
here.
I'm
gonna
fly
around
all
these
different
screens
use
this.
We
got
somebody
in
here.
Someone
said
trans
book
awesome
you
see.
This
is
the
kind
of
interaction
that
we're
talking
about.
So
you
you
see
these
products.
B
We
need
more
of
these
ideas
in
here,
so
that
now
we
can
start
to
put
to
work
and
actually
get
your
get
your
dreams
to
come
true
over
here.
So
you
know
we
need
more
of
these
ideas
and
what
systems
are
being
used
and
and
for
what
they're
being
used
and
what
the
use
case
is
it
so
fill
that
out,
but
again,
that's
part
of
your
product
cookbook
and
as
we
go
through
these
things
over
here,
you're
going
to
see
that
there's
certain
features
that
just
aren't
shown.
B
Maybe
you
want
to
see
something
and
we'll
point
that
out
scaling
baseline
also
is
another
track
which
is
happening
again.
You
could
have,
depending
on
the
session,
not
the
session.
I'm
sorry,
depending
on
the
use
case,
you
could
have
more
transactions
than
than
then
then
scaling
permits
to
happen
right
now
right.
So
for
that
there's
a
session
right
now,
they're
working
on
it
best
minds
in
the
industry
are
putting
their
thoughts
and
their
energy
and
their
effort
into
scaling.
We
all
know
that
scaling
is
an
issue
right
now.
I
don't.
B
B
Okay,
so
we'll
go
through
this
and
we'll
see
if
there's
even
a
better
way
to
go
ahead
and
talk
about
it
now
before
I
go
on
to
the
next
slide,
because
the
next
couple
of
couple
slides
are
gonna
are
gonna
go
kind
of
quick.
Let
me
just
actually
take
a
step
back
right
here,
who
else
can
come
up
with
another
term
or
another
sentence
on
how
to
explain?
B
So
here
I'm
writing.
You
are
baselined
when
two
or
more
systems
store
data
and
run
business
logic
in
a
verified
state
of
consistency
enabling
enabled,
by
using
the
mainnet
as
a
common
frame
of
reference.
B
In
my
opinion
that
doesn't
do
it.
I
think
that
we
need
something
more
sustained
and
that's
just
that's
just
my
opinion.
Let's
see,
I
think
we
have
a
question
over
here
on
the
chat
it's
coming
from
bass.
I'm
sorry,
if
I'm
saying
your
name
right
question
all
these
slides
talk
about
two
parties
with
two
systems
of
reference
talking
to
each
other.
B
Can't
there
be
another
use
case
to
use
baseline
for
a
single
party,
how
about
using
baseline,
to
make
sure
that
the
quotations
and
billings
you
send
out
to
customers
who
are
not
connected
to
baseline
are
still
still
are
correct.
Sorry,
not
the
direction
you
want
to
take
the
talk,
and
no
I
mean
look.
This
session
is
for
everybody,
so
yeah!
No,
let's!
Let's!
B
Let's,
let's
talk
about
it,
you
know
which
is
really
relevant
actually
to
what
we're
talking
about,
because
in
this
system
right
here
we
said
you
are
baseline
when
two
or
more
systems
store
data
you're
asking
is
there
a
potential
that
you
don't
need
two
systems
to
be
baselined,
I'm
gonna
go
on
a
whim
and
start
the
conversation
and
I'm
gonna
say
I
think
you
need
two
systems
in
order
to
have
baseline.
B
Unless
that
the
company
that
you're
sending
the
quotes
and
billings
out
to
is
also
baselining,
that
which
is
what
we're
going
to
be
showing.
But
let
me
ask
what
does
everyone
think
to
that
question?
Do
we
need
a
minimum
of
two
parties,
or
can
we
do
this
with
one
party?
Let's,
let's
start
there.
L
I
mean,
in
my
opinion,
I
guess
it
really
comes
down
to
what
you
define
as
a
party.
Doesn't
it
you
could
have
several
different
departments
within
within
a
single
company
work
as
a
systems
themselves
and
just
try
to
keep
like
internally
the
the
records
straight.
That
makes
any
sense.
B
So
we've
seen
this
that
one
organization
does
have,
let's
say
different
legal
entities
and
they
do
operate
different
systems,
so
maybe
maybe
but
again
I
don't
want
to
be
the
one
to
answer
that
I
want.
I
want
the
rest
of
everyone
to
answer
that.
F
So
daniel,
I
think
you
hit
on
a
really
important
differentiator,
which
is
the
distinct
legal
entity
barrier
between
you
know,
organizations
enterprises,
parties
that
would
require
baselining
in
order
to
keep
their
data
sets
in
sync
or
would
have
you
know,
a
barrier
that
exists
between
them.
That
would
demand
baselining
or
some
other
consensus
mechanism.
I
F
So
so
you
know
that
sort
of
phrasing,
distinct
legal
entities,
I
think,
covers
off
the
example
that
was
that
was
just
mentioned
about
having
you
know:
different
subsidiaries,
perhaps
of
the
same
organization
or
different.
F
You
know
national
groups,
you
know
related
to
different
regions
for
the
same
organization,
but
I
think
what
the
the
the
reasoning
for
that
two
or
more
systems
phrasing
in
the
the
original
sentence
that
you
put
forth,
I
think,
implies
that
there
is
a
necessity
for
baselining
that
such
verified
consistency
cannot
be
otherwise
achieved
due
to
the
current
architecture
or
the
current
state
of
that
data.
So
I'm
sorry,
I
think
we're
going
the
opposite
direction
of
being
more
pithy,
but
just
to
parse
what
we
mean
by
two
or
more.
F
What
we
really
mean
is
unable
you
know.
You
know
a
non-zero
number
of
parties,
so
I
guess
you
know
two
plus
that
are
otherwise
unable
to
maintain
a
verified
state
of
consistency.
E
I
think
that
was
really
well
said,
evan,
and
I
think
you
know
I'll
back
up
a
second
just
the
bass
point.
I
think
you
know
from
from
bass's
standpoint.
You
know.
E
I
think
that,
where
you're
coming
from
bass
is
and
correct
me,
if
I'm
wrong,
is
simply
that
you
know
when
we,
when
we're
sitting
here
talking
about
two
or
more
parties,
we're
also
looking
at
this
as
two
or
more
state
machines
where,
theoretically,
you
are
right,
you
you
are
taking
information
from
your
state
machine
and
providing
a
proof
on
a
mainnet
which
is
another
state
machine,
and
you
have
two
different
state
machines
now,
interacting
with
one
another
where
I
think
baseline
is
trying
to
drive.
E
Value
is
between
two
different
business
entities,
where
the
consistency
and
and
proof
on
mainnet
is
specifically
tied
in
for
a
for
a
business
process
where,
where,
instead
of
having
you
know
a
reconciliation
period
or
instead
of
dealing
with
any
sort
of
verification
of
of
a
business
process,
moving
forward,
all
the
above,
where
two
parties
would
interact,
you
know
that's
that's
kind
of
where
we
see
baselines
value
coming
to
fruition.
E
Where
you
know,
I
think
you
know
just
to
your
point
best,
putting
some
verification
or
proof
on
mainnet,
you
know
is
important
and
may
be
important
to
other
participants
that
that
are
not
necessarily
involved
in
the
baseline
protocol.
E
Just
for
the
just
for
the
simple
sake
of
ensuring
that
there's
some
immutable
proof
of
that
record
moving
forward
is
great,
but
it
doesn't
necessarily
you
don't
necessarily
need
to
incorporate
all
of
the
components
such
as
the
global
phone
book.
You
wouldn't
need
to
incorporate.
E
M
If
I'm
understanding
you're
right,
though
you
might
want
to
differentiate
between
what
you
see
as
baseline's
primary
value
and
what
can
still
be
accomplished
with
it,
I
mean
if
I
could
give
a
really
mundane
example,
if
I
have
two
computers
right
next
to
each
other
in
a
room,
and
I
need
to
move
a
file
from
one
computer
to
the
other.
Oftentimes
I'll
send
an
email
to
myself
if
I'm
logged
in
on
both
computers.
M
That
is
not
what
email
is
meant
to
do.
It's
not
meant
to
be
a
file
transfer
protocol
between
computers,
especially
on
one
internal
network.
I
mean
it's
ridiculous,
like
I
could
be
sending
a
file
to
a
different
continent
just
to
move
it
two
feet,
but
it
is
something
I
I
I
suspect,
I'm
probably
not
the
only
person
on
earth
who
does
that.
M
M
It
I
mean
at
the
end
of
the
day,
if
you
really
distill
it,
it
really
just
is
a
communication
layer
between
data
silos.
Now
you
want
to
do
a
lot
more
with
it.
There's
a
lot
more
you
can
do,
but
if
you
really
strip
it
down
to
its
like
most
basic
function
and
it's
basically
just
a
communication
layer
now.
B
You
know
it's
it's
it's
it's
like
this
right
and-
and
we
can
talk
about
this
a
little
bit
later
as
well,
we'll
the
part
of
what
we're
going
to
be
showing
is
the
reference
implementation,
bri-1
and
there's
1.1,
which
is
coming
out
soon,
which
was
put
out
by
provide-
and
you
know
it's
like.
B
B
You
can
still
send
it
through
email
like
you
mentioned,
however,
if
you
need
to
make
sure
that
that
file
is
the
same
as
the
other
computer,
for
whatever
the
business
purpose
is,
if
that
record
needs
to
stay
the
same,
if
that
mp4
was
never
changed
or
or
something
along
those
lines,
that's
where
that's,
where
baselining
helps,
because
it
keeps
that
state
of
consistency,
and
I
think
that
we've
said
stated
consistency.
You
know
a
couple
different
times
from
a
couple
different
folks.
M
B
Absolutely
right,
and
for
that,
that's
where
the
core
interfaces
session
comes
in,
because
in
the
core
interfaces
session,
as
we'll
show
you
in
experiencing
right,
is
that
you
still
need
to
be
able
to
have
messaging
like
you
can't
you
can't
send
something
without
having
the
right.
I
don't
know
interface
for
the
apis
to
be
able
to
send
things
through
and
just
to
get
a
little
bit
deeper
into
it.
One
of
the
things
that
we've
done
and
we'll
show
you
within
the
product,
cookbook
is
and
I'll
just
share
this
into
this.
B
The
cookbook
ideation
is
the
connector
right.
So
there's
a
need
for
you
to
be
able
to
send
something
and
in
radish
34
that
something
is
an
rfp,
and
just
just
like
the
example
that
you
just
mentioned,
you
can
either
send
the
rfp
via
email
or
you
can
do
it.
The
way
that
we
showcase
and
we're
going
to
show
you
how,
how
we've
done
it
and
talk
about
some
of
you
know
the
technical
components
that
went
into
it.
B
Is
this
connector
piece
so
that
there's
a
proxy
with
a
data
model
that
that
that
sits
in
the
middle
that
can
create
the
objects
that
needs
to
be
created
while
baselining
specific
attributes
where
in
the
radish
34
use
case,
which
is
actually
a
pretty
good
segue?
I'm
gonna
just
move
on
and
we'll
consolidate.
Some
of
these
thoughts
move
on
to
the
next
part
is,
and
here
I'll
just
keep
this
up
here.
I'm
not
gonna,
really,
you
know
go
into
this
one.
B
But
again,
as
we
start
to
talk
about,
I
remember
that
somebody
was
saying
something
around.
You
know:
let's,
let's,
let's
do
telecom
or
let's
do
something
else.
You
know,
let's
make
sure
that
we're
not
doing
things
just
to
do
them
and
they're.
You
know
the
tech
has
business
behind
it
so
that
there's
something
behind
that
right
and
the
procurement
use
case.
Answers
volume,
discounts,
problems,
multilateral
to
bilateral,
compartmentalization
problem,
blind
coordination,
problem,
the
coopetation
problem
so
on
and
so
forth.
B
B
Looks
like
it's
the
inverse.
If
I
shrink
my
screen,
this
gets
bigger,
okay,
so
here's
the
first
workflow
that
was
put
out
for
radish
34
that
we
translated
into
what
we're
going
to
show
you
in
the
next
couple
minutes
over
here.
B
And
basically,
you
can
go
and
check
this
out
at
the
docs,
I'm
just
gonna,
I'm
gonna
open
this
up
just
so,
everyone
could
see
again
more
material.
For
you
to
know
about.
Is
that
all
the
things
that
we're
talking
about
is
already
documented
right
here
in
the
baseline
protocol
docs-
and
this
is
the
workflow
that
we're
talking
about
this.
This
doesn't
really
do
us
any
justice
either,
but
essentially
you
have
company
a
company
b,
and
you
have
these
different
components.
You
have
a
messenger
component,
that's
that's!
B
What
you
were
just
discussing
is
the
need
for
a
messenger
service.
You
have
zero
knowledge
proofs.
You
have
to
get
up
in
here.
You
have
your
database,
you
have
your
wallet
software,
you
have
your
blockchains,
you
have
your!
You,
have
your
api
and,
as
you
start
to
you,
know,
start
this
use
case
at
the
very
beginning,
there's
certain
things
that
need
to
happen.
B
For
example,
you
need
to
have
messaging
in
order
to
send
from
one
computer
to
another
computer
or
from
sap
to
d365
or
from
google
sheets
to
oracle
or
from
you
know,
you
kind
of
get
the
point.
Then,
when
someone
in
radish
34
procurement,
when
they
send
something
back
right,
we
have
these
two
counterparties
that
we
that
we
spoke
about.
B
You
send
something
back.
That's
that's
the
proposal
when
the
msa
happens,
when
you
agree
on
something,
that's
that's
hardened
or
what
they
like
to
call
is
this
new.
Is
this
new
interface
that
we'll
briefly
touch
up
on?
Is
persistence
at
the
ui
level,
again
part
of
the
core
interfaces
workshop?
So
as
we're
talking
through
this,
if
there's
interest
around
that,
please
make
sure
that
you
join
the
core
interface
group
and
speak
up
the
way
that
you've
been
doing
over
here
I
mean,
I
think
that
this
is
really
really
a
great
conversation.
B
That
goes
here
right
and
then,
and
then
their
needs
for
the
the
blockchain
part
doesn't
actually
really
happen
until
somewhere
around
here,
where
you
have
the
verify
key
for
from
from
the
zero
knowledge
proofs
to
be
able
to
be
put
within
the
shield
contract
now
I'll
make
a
quick
comment.
There
was
a
there
was
a
quick
chat
that
was
happening
on
slack
and,
and
the
question
was
on
slack
is
why
can't
we
just
take
a
hash
and
throw
that
up
on
chain?
B
Why
can't
we
just
do
that?
Why
do
we
need
the
baseline
protocol
for
that
and
and
and
and
you
can
but
you're,
not
considering
some
of
the
other
components
like
privacy
that
that
would
be
part
of
it
again.
That's
all
part
of
the
core
interfaces
working
group,
so
you
need
that
shield
contract
in
order
to
give
you-
and
I'm
going
back
into
this
right
here
in
order
to
give
you
this
compartmentalization
issue,
so
that
no
other
party
could
see
what
the
other
party
is
doing.
B
It's
easy
to
see
within
procurement
use
case,
but
again
I'm
urging
everyone
to
go
ahead
and
add
different
use
cases
in
here.
That
could
fit
that
that
could
fit
that
you
know
need
for
privacy
anyway,
going
forward.
This
is
also
part
of
the
cookbook
and
we're
going
to
be
showing
you
this.
You
know
just
just
just
a
couple
minutes
or
so
this
was
a
demo
flow
that
was
done
through
unibrite
provide.
B
B
It's
it's
part
of
the
cookbook
right
so
again
the
cookbook
is
to
give
teams
companies
that
are
developing
product
that
are
looking
to
modernize
their
systems,
looking
to
expand
on
their
systems,
giving
a
recipe
as
to
how
they
can
actually
do
that
with
the
systems
that
they
use
or
the
systems
that
their
business
partners
use.
So
for
that
we
put
together
this
demo
that
showed
from
sap
there
was
this
request
for
proposal
that
got
sent
out
to
the
d365
environment
proposal
then
was
answered
that
went
to
the
purchase
order
from
the
purchase
order.
B
Then
that
has
to
get
approved
that
gets
sent
and
that
creates
a
sales
order.
We
skip
the
msa
part
for
just
ease
of
demo
and
also
that
probably
happens
off
chain
right,
so
that
happens
probably
even
outside
of
your
erp
system
right.
So
you
probably
have
a
document
you
sign.
For
example,
you
sign
the
msa
everything's
locked
in
you
can
store
that
as
an
email.
Okay,
let's
go
on
here.
So
what
we're
going
to
show
you
in
the
next
couple
minutes?
Is
this
d365
to
d365
we're
gonna?
B
B
B
Can
you
give
me
a
little
bit
more
clarity.
B
You
know
I
want
to
say
yes,
but
I
think
we
would
need
to
know
a
little
bit
more
about
that.
Can
you
be
a
little
bit
more
specific,
even.
H
I'm
I'm
trying
to
imagine.
Let's,
let's
say
I,
a
number
of
a
number
of
different
parties
want
to
kind
of
maybe
keep
in
sync
some
kind
of
balance
or
an
inventory,
so
each
each
one
of
them
can
update
the
inventory
on
their
own
and
then
that
inventory
is
synchronized
across
all
the
different
parties.
H
So
I
think,
for
instance,
different
stores
and
and
all
those
stores
have
different
parts
in
in
their
in
their
sites
and
each
site
updates
its
records
and
they
get
replicated
to
all
the
others
so
that
somebody
can
have
a
comprehensive
view
of
what
is
in
the
store
of
the
whole
system.
B
So
we've
seen
some
more
we've
seen
similar
discussions
happening
now
and
that's
kind
of
that's
kind
of
what
we're
going
to
show
you
with
this
radish
34
in
procurement,
because
what
you're
talking
about
is
you're
talking
about
synchronization
of
inventory
between
between
parties,
so
that
maybe
you
could
enable
predictability
and
forecasting.
H
H
Is
is
you
are
constantly
talking
about
party
to
party
and
my
question
is:
can
that
synchronization
happen
multi-party
so
that
one
party
updates
one
record
and
then
all
the
other
parties
get
in
sync.
B
No,
I
don't,
I
don't
see
why
it
can't,
especially
since
their
multi-parties
are
gonna,
have
multiple
different
systems
and
that's
and
that's,
and
that's
the
purpose
of
that.
Let
me
ask
somebody
else:
what
does
someone
else
think
it
looks
like
jason
has
something
to
say:
yeah.
E
I
was,
I
was
actually
just
gonna
agree
that
it
is
definitely
a
multi-party
system.
You
know
with
respect
to
the
procurement
use
case.
What
what
we're
gonna
show
is.
You
know
how
buyer
interacts
with
multiple
suppliers
for
multiple
suppliers
are
shielded
from
each
other
from
having
that
visibility,
although
if
this
was
a
situation
where
I
don't
know,
this
is
a
retail
type
situation,
say
it's
telecom
and
each
store
or
whatever
it
might
be,
each
each
storefront,
maybe
is
its
own.
E
Maybe
it's
not
telecom,
maybe
it's
whatever,
but
each
storefront
you
know
is
in
charge
of
their
own
business,
their
own
books,
they're
their
own
business
entity
and
they're
interested
in
understanding.
E
You
know
the
flow
of
product
or
inventory
in
the
event,
they
need
to
move
inventory
between
stores,
for
whatever
the
case
that
that's
definitely
a
possibility
right,
you
can,
you
can
lift
permissions
or
the
the
ability
to
shield
different
participants
within
a
workflow
that
that's
definitely
something
that's
configurable.
E
E
You
know,
depending
on
a
specific
work
workflow,
so
I
think
to
answer
your
question
yeah.
I
definitely
think
that
baseline
is
is
enabling
a
multi-party
situation
where
we
can
sync
different
state
machines.
That's
exactly
what
we're
doing
for
sure.
B
And
please
go
to
the
sheets
tab
and
you
know
fill
out
the
question
you
just
asked
and
let's,
let's,
let's
put
that
into
the
queue
all
right.
So,
let's
see,
let's,
let's
keep
going
over
here.
We
kind
of
we
kind
of
beat
this
one
all
the
way
down
to
the
ground.
B
So
we
understand
the
radish
34,
we'll
we'll
showcase
that
some
some
some
folks
may
may
just
want
to
understand
a
little
bit
around
the
smart
contract
architecture
and
what
was
diagrammed
out
there
from
from
the
very
beginning,
it
is
using
the
erc,
1820
registrar
contract
that
needs
to
be
deployed
if
there
is
no
1820
register
or
contract
in
place.
If
you're
using
public
blockchain,
which
this
is
the
whole
purpose,
is
to
use
mainnet,
then
you
don't
have
to
deploy
that
in
that
step.
That's
already
done
for
you.
B
B
Organization
management
is
happening
through
the
org
registry
contract,
which
handles
permissions
roles,
etc.
Process
and
privacy
management
is
just
like.
Jason
was
just
talking
about
you:
have
your
shield
contract
your
verifier
contract
and
then
there's
token
management
as
well,
if
that's
part
of
the
use
case
from
erc20
contracts,
erc
721s,
erc
1155.
B
So
definitely
you
know
take
a
look
into
this
one.
This
was
this
particular
slide
needs
to
be
updated,
so
I'm
gonna,
I'm
gonna,
make
a
note
and
I'm
going
to
say
that
this
slide
needs
to
be
updated
with
the
new
core
interfaces.
B
So
let's
just
say
that
this
is
a
slide
that
we'll
work
on
okay
and
then
again
just
some
value
like.
Why
should
we
care?
I
think
that
we
spoke
about
this
a
little
bit
earlier.
We
modernize
systems,
we
synchronize
and
automate
workflows,
see
so
compliant
right
because
everything
happens
off
chain
we're
just
sending
one
hash,
one
hash
to
the
main
net:
that's
hidden
inside
the
shield
contract,
which
again
just
for
those
that
don't
know.
B
I
just
want
to
go
ahead
and
just
say
this
for
the
record
that
shield
that
that
that
shield
contract
is
a
combination
of
ey,
nightfall
and
z
cash
protocol.
So,
taking
really
really,
you
know
really
exceptional
technology
and
and
and
and
minds
in
the
industry
put
that
together
so
we'll
go
back.
If
there's
time
and
we'll
talk
about.
Why
should
we
care
about
that
standards
of
modern
applications?
B
Cool
thanks
mark
for,
for
those
that
haven't
had
the
chance
to
talk
to
anias
and
frank.
Definitely,
we
recommend
that
you
have
a
conversation
with
her
she's
been
leading
the
standards
work.
The
standards
work
is
really
where
this
is
all
about
for
those
that
are
familiar
with.
What
is
it
the
crossing
the
chasm
book
right?
B
The
whole
point
is
that,
with
this
emerging
technology,
the
pragmatists
are
just
really
slow
to
adopt
and
buy,
and
who
is
this
for
this?
Just
for
enterprise
organizations
or
small
companies
or
small
businesses,
but
it's
it's
it's
for
the
business
world
and
people
don't
really
want
to
stick
their
neck
out
with
emerging
technology
when
there's
so
much
uncertainty
around
that.
B
Hence
we
have
standards
and
standards
brings
to
the
table,
a
methodology
that
makes
pragmatists,
I
don't
know,
feel
a
little
bit
more
comfortable
with
the
situation
like
they're,
not
the
first
ones
that
have
you
know,
they're,
not
paying
someone
a
sass
fee
or
a
consulting
fee
to
figure
this
out.
It's
kind
of
already
been
figured
out
and
that's
what
you
know
standard
one
is
standard
two
talks
about:
there's
the
baseline
core,
we're
gonna,
flash
that
and
then
there's
standard
two
which
talks
about
the
baseline
api
and
the
data
model.
B
You're
going
to
see
some
of
these
things
in
work
in
the
next
couple
minutes.
But
like
always,
we
do
want
you
to
know
that,
for
example,
when
we
talk
about
the
standard,
one
hashtag
2020
baseline
summit
definitely
tweet
about
it.
But
the
whole
point
of
putting
this
out
hashtag
2020
baseline
summit
is
because
this
this
the
standard
one,
the
core.
This
is
a
work
in
progress.
B
It's
not
completed
by
any
means
it
takes
into
account
the
api,
the
communication,
the
privacy
and
confidentiality
agreement,
execution,
which
is
really
the
blockchain
ledger:
the
governance,
the
security
and
the
security
considerations
conformance
and,
along
with
baseline
standard.
Two
talks
about
the
api
and
data
model.
There
is
the
baseline
irpc,
there's
the
iregistry,
the
ivault,
the
I
persistence
service,
which
is
a
brand
new
one.
B
Why
do
we
even
care
about
these
standards?
It's
because
of
this?
It's
because
you
know
you're
you're,
probably
here
from
a
development
perspective,
because
you
want
to
know
how
the
heck
are
we
going
to
implement
this
thing
like
okay,
we
have
code,
but
what
does
that
actually
mean?
So
it's
like
three
very
simple
steps
that
takes
time
and
resources
and
and
energy.
But
it's
simple:
you
need
to
start
with
the
use
case,
we're
showing
you
procurement.
That's
the
first
use
case
that
we're
showing
you.
B
Then
you
have
to
build
a
provider.
What's
a
provider,
a
provider
is
a
baseline
stack
that
has
all
of
these
components.
I
baseline
rpc,
iregistry
ivault.
I
persistence.
I
blockchain
service.
It's
got
a
data
model
behind
that.
This
is
how
you
make
it
happen.
Right
so
provide
has,
has
has
put
a
lot
of
energy
into
it.
They
are
a
provider.
B
B
Connect
and
deploy
is
what
we're
about
to
show
you
next
right.
So
we
have
now
the
business
app.
So,
let's,
let's,
let's
kind
of
let's
kind
of
get
into
it
here
so
first,
it
was
a
reference
implementation
of
radish
34.
Now
we're
showing
you
the
reference
implementation
of
bri,
one
which
was
just
put
out
a
couple
weeks
ago.
It's
it's
like
fresh,
and
on
top
of
that,
there's
also
bri
1.1,
which
is
just
coming
out.
B
You
can
see
it's
not
yet
merged
to
maine,
but
it's
something
that
is
really
in
the
works
and
you
can
go
and
even
take
a
look
at
the
code
right
now.
If
you
go
to
the
github,
but
what
it's
doing
is
it's
showing
how
you
start
and
that's
so
important,
especially
like
with
the
global
phone
book?
How
are
you
going
to
initialize
with
the
org
registry?
B
All
right,
so
here's
just
a
quick
little
intro.
This
is
a
three-minute
video.
We
did
this
video
a
little
while
ago
and
it's
essentially
showing
it's
all
cli
stuff.
You
know,
on
the
left
hand
side
you
have
your
environment,
which
is
spinning
up
left-hand
side.
You're
gonna
see
the
requirements
that
are
being
implemented
on
the
right
hand,
side
you
have
all
the
logs
that
are
running
so
that
you
can
actually
see
things
that
are
in
work
and
I'll
just
pause
right
here.
You
see,
you
have
baseline
work
group
creation.
B
B
One
json
object
sits
in
one
environment.
Another
json
object
sits
in
another
object
in
another
environment
and
I'll
just
pause
right
here.
We
could
talk
about
what
we're
seeing
so
as
you
as
you
go
through
this
bri
one.
You
can
notice
that
there's
certain
check
marks
that
happen
should
create.
The
work
group
in
the
local
registry
should
authorize
a
better
token
right.
This
is
all
about
authorization
should
deploy
the
erc
1820
contract
for
the
work
group.
B
B
B
It
could
be
tampered
with
and
you
just
don't
know
things
like
that
happen
all
the
time
right.
So
here
you
go
we're.
Also.
We
have
our
contracts,
that's
being
deployed,
we
have
messaging,
we
have
registration,
we
have
vault
which
deals
with
signatures.
It
deals
with
making
sure
that
addresses,
aren't
being
traced
back
to
the
organization
that
that
that
signed
those
transactions.
B
Okay,
we'll
keep
this
running
we're
about
halfway
through
maybe
a
little
bit
more
now
we're
inviting
participants
to
the
work
group.
This
is
so
important
who
wants
to
do
business
by
themselves,
and
this
is
kind
of
what
we
were
talking
about
before
on.
Can
you
do
this
with
just
one
person
it
kind
of
defeats
the
purpose
of
baseline
right?
So
you
need
to
have
this
interaction
where
you're
sending
an
invite
out
to
those
organizations
that
you're
going
to
participate
without
here.
I
B
B
So
here
we're
still
inviting
the
participants
to
the
work
group.
Now
the
work
group
is
being
owned
by
bob
bob
owns
the
work
group
in
the
case
of
radish
34.
The
buyer
is
the
owner
of
the
work
group.
Okay,
so
alice.
Now
then
she
joins
alice
is
all
set
she's
configured.
She
has
her
smart
contracts
that
are
deployed.
She
has
her
messaging,
that's
all
set
up.
It's
registered.
She
has
her
eye
vault
all
set
up,
and
that's
that
so
bob
and
alice
are
now
baselined
and
now
they
could
do
something.
B
But
that's
not
the
point
of
this
demo
right.
The
point
of
this
video
was
just
to
showcase
how
it
is
that
it
essentially
gets
started,
and
it
starts
with
the
org
registry
being
set
up
and
sending
the
invite
out
and
then
getting
your
counterparties
to
also
join
in
and
then
registering,
for
example,
radish
34.
There
was
the
code
for
whisper
and
then.
Secondly,
then
it
was
gnats
for
the
men
for
for
the
messaging,
but
you
have
to
set
up
your
circuits
and
yada
yada
right
so
that
that
that
got
all
set
up.
B
Okay,
we'll
come
on
down
and
this
kind
of
talks
a
little
bit
about
the
bri
architecture.
Where,
again,
you
could
start
to
see
the
ident
and
the
eye
vault,
and
this
is
all
part
of
the
core
interfaces
again
to
get
down
into
the
code
level.
I
can't
tell
you
enough:
you're
not
gonna,
want
to
miss
this
core
interfaces.
Group.
It
looks
like
the
team
is
already
getting
in
there.
B
So
if
there's
any
questions
around
that,
I
mean
like
leave
this
session
and
go
to
the
core
interfaces
session
and
start
to
dig
into
the
code,
because
that's
that's
that's
where
it's
at
continuing
further.
So
something
interesting
to
note
here
is:
we
just
wanted
to
showcase
this,
so
linking
what
you
just
saw
together
with
standards?
B
Okay,
so
we
have
not.
Everything
is
being
demonstrated
within
this
bri-1
we're
not
showing
conformance
we're
not
showing
security
considerations,
we're
not
showing
governance
and
and
and
but
that's,
but
that's
all
right,
though,
because
we
just
wanted
to
showcase
how
things
actually
look
and
how
things
begin.
So
you
are
being
you
know
you
are
demonstrating
baseline
apis.
B
You
are
demonstrating
communication
right,
I
mean
bob
had
to
send
the
invite
out
to
alice
somehow
and
that's
done
through
these
apis
and
the
communication
and
messaging
there
was,
as
we
saw
there,
was
the
circuit
creation.
So
there
was
the
privacy
and
confidentiality
there
was
the
shield
deployments
with
those
contracts
as
well.
B
So
that
includes
that,
and
then
you
also
have
the
execution
agreement,
which
is
you
know
you
need
the
ledger
to
be
able
to
execute
these
smart
contracts
for
that,
for
that
agreement
so
again
linking
it
back
to
the
core
interfaces
session,
which
is
what
we
aim
to
do.
Is
that
we're
showing
eye
registry
we're
showing
imessaging
we're
showing
eye
vault
izk
snark
is
also
another
one
shield
contract
verifier,
that's
all
being
discussed
over
there,
okay,
so
let's,
let's,
let's
actually,
let's
actually
start
to
experience
this
thing.
B
B
I'm
looking
here
in
the
youtube
chat
looks
like
there
was
some
there's
some
conversation
there.
I
have
18
on
there
any
any
questions.
B
E
Justin
just
asked
a
question
in
the
in
the
zoom
chat.
Isn't.
C
B
E
One
thing,
one
thing
also
to
add
is
that's
that's
100,
correct
and
all
that
we're
using
mainnet,
for
is
just
a
proof,
is
just
simply
to
to
prove
that
that
these
object
packages
are
are
insane.
I
B
I
love
this
format
by
the
way.
I
just
want
to
say
that
I
love
this
format
as
opposed
to
just
giving
a
presentation-
it's
just
so
it's
so
great
to
get
feedback,
and
you
know,
and
and
and
have
this
collaboration
tool
where
we
can
just
see
the
same
things
and
talk
about
the
same
thing
so
again,
nick
awesome
job
setting
this
up
all
right.
We
are
behind
time,
which
I
didn't
actually
think
that
we
were
going
to
be
behind
time.
B
B
What
did
we
want
to
do
jane
did
all
the
hard
work
but
appreciate
the
thanks.
Yeah
look.
I
use
your
name
as
as,
like
the
silver
bullet
for
everyone
that
was
behind
us,
so
so
so,
jane
and
and
everyone
else
that
you
mentioned.
You
know
thank
you
for
that.
Awesome
awesome
experience
I
think
so
far.
B
B
One
thing
that
we
wanted
to
showcase
is
this:
from
a
cookbook
perspective
from
an
enterprise
business
perspective,
100
of
all
of
our
customers,
not
even
like
99
100
of
our
customers
said
hey.
If
we
have
something
and
we
want
to
integrate
blockchain
or
we
want
to
use
blockchain
or
we
want
to
do
blockchain
as
we,
what
we've
heard
sometimes
do
we
have
to
rip
our
system
out
or
can
it
just
run
in
the
background?
B
So
that's
really
what
we
wanted
to
aim
for.
Is
we
wanted
this
system
to
look
like
the
system
that
they
use
day
in
and
day
out,
right,
the
less
organization,
rigor
and
change
management?
That's
involved
the
better
it's
going
to
be,
and
if
you're
working
on
your
system
right
now
looking
to
baseline,
it
make
it
feel
as
if
it's
just
like
blockchain
isn't
even
there.
It's
like
running
in
the
background.
B
So
what
did
we
do
as
it
relates
to
dynamics
365?
Is
we
kept
as
many
out
of
the
box
modules
as
as
physically
possible?
So
when
you
purchase
a
license
for
dynamics
365
for
finance
and
operations
it
actually,
the
sku
has
changed
a
little
bit
now.
There's
finance
and
then
there's
supply
chain
management,
but
it's
neither
here
nor
there
you
get
these
modules
out
of
the
box.
So
there
is
a
procurement
and
sourcing
module
which
handles
your
request
for
quotations.
It
handles
your
purchase,
orders.
You
can
create
your
vendors.
B
You
can
also
manage
all
of
the
product
information
in
here.
Okay
and
same
thing
on
the
supplier
side.
Excuse
me
so,
if
you're
a
supplier
out
of
the
box
you're
gonna,
be
you
know,
you
have
your
request
for
quotations,
your
sales
orders.
You
can
onboard
your
customers,
you
have
your
product
information,
but
what
you
don't
have
is
you
don't
have
baseline.
B
So
what
did
we
do?
Is
we
created
a
custom
module
that
we
call
radish
34
for
purposes
of
this
procurement
demo?
That
incorporates
everything
that
you
see
it
incorporates.
You
know
on
the
back
end
and
incorporates
all
of
these
standards
and
yada
yada
yada
right.
So
this
is
the
only
thing,
that's
new
and
that's
just
a
simple
add-on.
B
If
you
want
to
send
a
po,
you
got
to
be
accounts
payable
manager,
there's
just
there's
just
no
way
around
it,
not
everyone's
going
to
be
a
system
admin
and
a
system.
Admin
then
has
to
be
able
to
install
this.
But
when
it's
installed
you
have
now
this
radish
34
module
that
came
out
of
this
cookbook
right.
B
So
now
here's
how
we
make
it
look
like
so
it
looks
just
like
the
erp
system
that
folks
are
accustomed
to
using
with
one
caveat,
is
that
there
is
a
parameter
section
and
when
you
get
to
the
parameter
section,
that's
where
you
can
actually
go
ahead
and
change
your
connector
q
bus.
Okay,
so
remember,
every
organization
is
going
to
need
to
have
their
own
baseline
stack.
Okay,
so
just
keep
that
in
mind.
So
that
means
that
every
every
baseline
needs
to
be
connected
to
your
system
of
record.
Somehow,
and
for
that.
B
B
Parameter
settings.
Okay,
so
remember
your
baseline
provider
is
your
baseline
stack
and
the
parameter
settings
are.
How
are
you
actually
going
to
connect
from
that
particular
baseline
stack
to
the
erp,
or
vice
versa?
Whichever
way
you
want
to
think
about
it?
Okay,
so
that's
on
that
screen.
The
next
screen
global
phone
book,
please,
if
this
is
of
interest
to
you,
you're
gonna,
want
to
check
out
the
global
phone
book
session.
B
You
gotta
have
to
onboard
new
vendors.
If
you
are
a
procurement
purchasing
agent,
you're
gonna
need
to
onboard
your
suppliers
and
vice
versa.
B
How
much
time
do
you
think
that
we'll
be
able
to
save
companies
by
doing
something
like
that
anyway?
That
was
more
of
a
rhetorical
question,
but
it
was
also
a
plug
for
the
global
phone
book
to
give
even
more
context
of
the
plug
kale
from
microsoft
is
going
to
be
talking
about
how
the
global
phone
book
works
together
with
azure
active
directory,
which
is
just
like
perfect
for
this
d365
scenario,
because
d365
actually
runs
on
azure.
B
Likewise,
johnny
from
consensus
is
going
to
be
talking
about
ui
implications
and
ux
implications
with
dealing
with
the
global
phone
book
and
dealing
with
dids.
I
definitely
recommend
you
check
it
out.
They
showed
me
what
they
were
working
on
yesterday,
I'm
not
going
to
steal
their
thunder
that
just
wouldn't
be
wouldn't
be
fair,
but
man.
It
is
so
cool
to
see
this
stuff
actually
being
worked
on
and
they'll
show
you
so
again
global
phone
book.
B
This
is
where
it's
at
right
over
here,
no
one's
in
there
right
now.
The
session
isn't
happening
now,
but
when
it
does
that's
where
you're
going
to
be
able
to
tie
it
all
together.
Okay,
another
screenshot
I'll
show
you
and
again
I'm
showing
you
this
from
the
admin
perspective,
because
when
we're
going
to
do
the
experience
over
here
in
just
a
minute,
you're
not
going
to
be
able
to
see
all
that
the
session
begins
at
1
pm.
Mark
I
see
you
is
that
the
session
for
for
for
the
global
phone
book.
B
Cool
so
yeah,
so
at
1pm,
if
you
get
bored
with
this,
I
recommend
you
go
to
the
1pm
session
and
check
out
the
global
phone
book
because
man
they
got
some.
They
got
some
cool
stuff
over
there
to
show
and
we
need
your
help
to
actually
put
your
input
into
how
it
should
actually
look
from
a
ux
perspective.
B
How
are
we
going
to
make
you
know
what
I
was
just
about
to
speak
about
their
session
and
I'm
going
to
keep
my
mouth
closed
because
then,
what's
the
point
of
going
there,
this
next
slide
talks
about
this.
Sorry,
let
me
go
back
here
when
you're
done
onboarding
your
vendor
you're
gonna
need
a
way
to
connect
it
to
the
actual
connector
right.
So
you
have
a
system
of
record.
You
onboard
your
vendor.
How
are
you
going
to
make
sure
that
you're
actually
connected
to
your
provider?
B
B
I
may
be
able
to
show
you
a
screenshot
how
this
looks
like
once
we
get
into
the
experience,
and
this
is
cool.
We
wanted
to
showcase
this
just
again
to
get
the
juices
flowing
and
the
ideation
happening
so
again
to
talk
more
about
this
particular
connector
and
what
we
did
and
I'm
talking
about
this
not
from
like
a
sales
perspective,
but
more
from
like
here's,
here's
how
we
did
it
and
we
recommend
that
you
put
something
into
your
ideation
funnel
as
well.
B
So
again
out
of
the
box
and
keeping
everything
native
is
what
we
really
wanted
to
do
and
something
that's
native
to
dynamics.
365
is
something
called
business
events
you
can
send
messages
out,
http
you
can
send
messages
out
with
web
sockets,
etc.
Web
hooks
or
d365
native
out
of
the
box
comes
with
business
events.
B
Excuse
me
that
provider
stack
has
all
of
these
core
interfaces
that
allows
you
to
connect
what
you
need
to
connect.
So
that's
what
we
did
over
here
and
we
put
that
into
cool.
I
see
that
some
of
this
going
over
here
and
we
put
that
in
here
the
the
connector
and
I'm
just
going
to
make
a
note
here,
because
I'm
just
thinking
out
loud
so
native
to
the
system
record.
Okay.
What
else
do
we
show
here
before
we
get.
P
B
How
do
you
lock
certain
fields
from
a
zero
knowledge
proof
perspective
once
your
trusted
setup
happens
and
you
compile
what
you
need
to
compile
the
data
points
in
order
to
create
the
zero
knowledge
proof
formula
right
for,
for
those
that
are
familiar
with
zk
circuits,
it
basically
spits
out
a
true
or
false
right.
If
it's
true
it's
good.
If
it's
false,
then
you're
missing
something
something's,
not
computing
right.
B
What
we're
showing
over
here
from
a
product
cookbook
perspective
is
that
d365
has
the
ability
to
lock
these
particular
things.
The
things
that
we
could
lock
based
on
business
process
is
forms
tables
and
fields,
there's
different
ways
that
we
can
lock
it,
but
that's
done
again
at
the
code
level
when
you're
configuring
these
systems
right,
so
there's
all
sorts
of
custom
scripts
that
you
can
put
in,
but
you
can
now
start
to
imagine
how
zero
knowledge
circuits
will
actually
look
like
on
the
front
end
of
an
erp
system.
B
So
I
know
the
dom
is
going
to
be
talking
a
little
bit
about
how
they
lock
things
down
in
salesforce.
That's
how
we
lock
things
down
in
d365,
just
to
show
you
a
little
snippet
of
code
over
here,
showing
you
that
you
can
either
allow
create,
allow
edit
allow
delete
do
not.
Allow
is
also
a
function
right.
B
B
O
O
B
Mark
brave
soul,
all
right,
I'm
going
to
ask
you
to
do
a
couple
things
here:
I'm
going
to
stop
sharing
my
screen,
okay
and
and
when
I
stop
sharing
the
screen.
What
I'm
also
going
to
ask
you
to
do
is
make
sure
that
make
sure
that
you
don't
have
anything
important
on
your
screen.
B
Make
sure
you
don't
have
anything
important
on
your
screen,
make
sure
that
what's
it
called
that
that
that
it's,
that
that
you're
able
to
share
your
screen?
Okay,
so
let's
see
what
we're
gonna
do
now?
B
Is
I'm
going
to
send
mark
and
frederick
your
your
top
secret
passwords,
because
we
can
only
have
one
person
in
at
the
time,
otherwise
it's
going
to
get
a
little
it's
going
to
get
a
little
messy.
So
just
give
me
a
second
and
let
me
load
something
up,
so
both
of
you
can
navigate
to
this
url.
B
O
B
It
should
allow
you
to
just
go
log
in,
or
maybe
you
might
need
to
be
in,
like
a
private
browser.
Q
B
Okay,
so
let's,
let's
start,
let's
start
with:
let's
start
with
mark
so
mark
after
you're
signed
in,
can
you
can
you
share
your
screen.
O
I
R
B
B
B
Well,
to
the
right
all
the
way
to
the
right
usmf,
you
see
right
there.
If
you
click
on
that,
that'll
just
show
you
that
that's
that's
the
company
that
you're
signed
in
with
right.
So
so
usmf
is
the
buyer
and
frederick.
If
you
can
confirm
yours
should
say
uspi
all
right,
good,
okay,
so
we're
gonna
go
ahead
and
just
get
started
and
and
what
I,
what
what
we're
going
to
do
is
kind
of
pick
up
where
bri
one
left
off
right.
B
So
if
we
recall
bri,
1
initialized
the
whole
thing
right,
so
we're
going
to
already
assume
that
usmf
is
already
set
up
and
in
sync
together
with
uspi
okay.
So
the
first
thing
that
we're
gonna
do
as
per
radish
34
is
we're
going
to
go
ahead
and
create
a
new
proposal
so,
on
the
left
hand,
side
there's
kind
of
like
this
hamburger
menu.
B
So
if
you
can
make
that
hamburger
menu
a
little
bit
bigger
right
there
and
you
want
to
click
on
the
modules
and
scroll
down
to
where
you
see
procurement
and
sourcing
exactly
so
again,
this
is
like
everyday
business
right
if
you're
developing
a
baseline
product-
and
you
want
to
make
it
look
like
it
is-
or
this
is
all
out
of
the
box.
So
let's
go
and
click
on
all
request
for
quotations.
B
Perfect
now
we're
just
going
to
click
on
the
the
ok
button,
but
you
could
start
to
see
a
couple
things
here
right.
You
can
start
to
see
that
you
can
change
currency,
yada
yada.
This
has
nothing
to
do
with
baseline.
This
is
just
a
system
of
record
okay.
So
let's
go
ahead
and
click.
Ok,
the
baseline
stuff
is
about
to
start
happening
first
things
first,
is
I
want
everyone
to
notice
a
couple
things
you
see
that
we
have
under
see
where
item
number
is
see.
Item
number
is
kind
of
red
right
here.
B
Right
item
number
see
the
next
the
next,
the
next
field.
If
you
scroll
down
a
little
bit,
you
see,
item
number
is
in
red.
Let
me
ask
the
let
me
ask
the
team
over
here.
Where
else
would
something
like
that,
where
it
pops
up
red
or
there's,
you
know
an
asterisk
or
something?
Where
would
that
be
helpful?
B
How
about
the
zero
knowledge
proof
part
all
right
how
about
if
somebody
tries
to
change
something
there
is
a
red
mark
that
comes
up
and
says
you
can't
change
it
right
or
maybe,
if
something
is
grayed
out,
like
you
see
on
the
top,
you
see
under
process
on
the
very
top
of
the
ribbon
there's
process
and
it's
grayed
out
you
know
or
or
or
you
know,
the
word
cancel
or
create
or
finalize
the
very
top
that
those
are
all
the
things
that
you
could
do,
based
on
your
business
process
on
whether
or
not
the
workflow
can
execute
or
get
to
the
next
state
or
not
again,
that's
that's
where
persistence
is
really
coming
into
play.
B
So
if
there's
curiosity
around
persistence
and
how
to
lock
certain
things
out,
that's
the
working
session.
That
would
be
good
for
you,
okay.
So
let's
continue
so
under
item
number.
Let's
go
ahead
and
hit
the
drop
down
and-
and
we
configure
this
a
certain
way
that
the
two
companies
are
that
they
have
the
same
same
same
skew
and
the
same
product.
So,
let's
scroll
down
until
we
see
like
the
phone
battery,
I
think
you
just
missed
it.
B
It
was
at
the
very
top-
oh
very
top,
very
top,
so
one
more
line
down
right
here,
yep.
So
let's
say
that
you
are
procuring
a
phone
battery.
Okay
and
you
can
go
to
site
and
you
can
change
the
site.
That's
like
the
site
of
where,
where
the
product
is
so
you,
so
you
can
click
on
any
one
of
that.
It
really
doesn't
matter
and
you
can
pick
which
warehouse.
B
Okay
and
the
only
other
thing
that
we're
going
to
need
to
change
over
here
go
to
the
right.
Is
you
can
change
your
quantity?
So
let's
say
that
you
want
to
order.
I
don't
know,
however,
many
pieces
of
that
phone
battery,
and
just
remember
your
number
here
so
say
you
want
three
of
them.
You
can
even
put
in
the
price
if
you
want.
If
you
want
to
send
out
the
bid
and
say
I
want
it
at
this
price
right,
you
can
put
in
put
in
the
unit
price
90
bucks
perfect.
B
Now
the
next
thing
that
we
have
to
do
is
assign
a
vendor.
So
so,
let's
go
ahead
and
in
in
if
you
move
your
cursor
to
the
right,
there
is
a
thing
that
says:
header
click
on
that
header
over
to
the
right
up,
a
little
bit
up
up
up
a
little
bit
more
higher
and
right
there
and
click
on
header.
B
Just
just
where
your
cursor
is
there
you
go
there.
You
go
and
scroll
down
a
little
bit
until
you
see
the
vendor
tab
right
there
and
let's
click
on
the
vendor,
account
and
we're
looking
for
the
company
called
whale
wholesalers,
so
scroll
down,
and
you
should
see
whale
wholesalers
right
there
now
again.
This
would
be
a
lot
easier
if
there
was
the
global
phone
book
all
all
put
into
it.
You
may
still
need
to
you.
B
You
may
still
need
to
go
ahead
and
manually
enter
the
vendors
that
you're
sending
it
out
to
right
the
business
process
business
process.
But
if
you
had
the
global
phone
book
and
you
put
up
a
generic
rfp,
you
could
have
different
suppliers
like
whale
wholesalers,
go
ahead
and
just
easily
discover
you
and
that's
what
we're
aiming
for.
B
Okay.
So,
let's
go
ahead
and
let's,
let's,
let's
go
hit
the
hit
the
save
button.
B
Now,
let's
wait
a
second,
because
this
dynamics
takes
a
little
bit
of
time.
Okay,
now
you
can
go
ahead
and
take
a
look
at
this
notification
bar
there's
a
there's
like
a
button
that
popped
up
and
let's
just
see
what
happens
so
operation
completed.
Rfq
has
been
sent.
Where
else
would
the
notification
bar
be
handy
in
the
context
of
baselining.
B
Tampering
all
right,
so
you
could
think
about
it.
A
couple
different
ways
right:
we
can
either
lock
everything
or
we
can
make
it
unlockable
and
people
can
make
mistakes,
but
you
still
need
to
be
able
to
have
some
sort
of
notifications
that
send
somebody
something
when
something
has
been
tampered
with.
B
Okay,
we're
almost
done
with
your
part
mark
I
appreciate
it.
All
that
I
want
you
to
do
now.
Is
click
on
that
hamburger
menu
again
on
the
left
hand,
side
and
what
I
would
like
for
you
to
do.
Is
you
see
under
modules,
look
for
radish
34.
B
And
just
scroll
down
on,
on
the
left,
hand,
side
scroll
down
until
you
see
radish
34
perfect.
Now,
let's
just
stop
here
for
a
second.
What
the
purpose
of
this?
For
what
the
purpose
of
this
is
it's
it's!
It's
there's
no
other
way
to
show
you
how
to
put
together
the
product
cookbook
than
to
actually
show
you
a
product
that
was
cooked
up.
So
everything
here
is
out
of
the
box
in
dynamics
365,
except
for
this
radish
34
custom
module
that
when
you
click
on
the
service
operations,
tab.
B
Okay,
I
want
to
be
aware
of
a
couple
different
things,
so
we
included
a
couple
buttons
here.
There's
certain
things
that
come
out
of
the
box
or
certain
things:
it's
not
the
ability
to
send
something
out
is
native,
but
it's
not
native
in
the
fact
that
it
follows
the
flow
and
it
doesn't
have
connections
to
all
these
core
interfaces
of
what
you're
talking
about
for
purposes
of
the
demonstration
we
turned
the
running
in
the
background
off.
B
But
if
you
click
on
the
run
in
the
background,
you
could
see
that
you
can
also
set
up
that
that
there
is
a
periodic
batch
processing
that
can
go
as
as
as
as
as
frequently
as
down
to
the
one
minute
time
and
with
custom
coding.
You
can
go
even
further,
but
we're
just
going
to
push
this
button
so
so
go
ahead
and
push
the
ok
button.
B
Okay,
so
that's
that's
just
the
one
thing
that
we
wanted
to
showcase
that
there
needs
to
be
a
way
if
you're
going
to
develop
a
product
to
be
able
to
take
those
messages
and
then
create
those
objects
in
the
counterparty's
environment
and
that's
done
via
proxy
model.
That's
done
via
provider
services,
so
on
and
so
forth.
So
let's
just
hang
out
here
for
just
one.
Second,
until
this
looks
like
the
request
is
done,
it
takes.
It
takes
a
little
bit
of
time
at
this
moment.
But
frederick,
are
you
ready.
B
Yep
all
right
cool,
so
it
looks
like
you're
done
over
here
mark
if
you
can
stop
sharing
and
fredrick.
Let's
have
you
share.
B
Awesome
so
now
you're
playing
the
role
of
the
supplier,
so
so
the
permission
rolls
like
the
buyer
had
had.
We
had
to
give
them
permissions
again,
I'm
just
letting
you
know
from
an
administrator
perspective.
They
had
to
get
access
to
the
custom,
radish
34
module
that
was
developed,
but
also
they
had
procurement
agent
payroll
manager.
They
also
have
procurement
manager,
you
have
sales
clerk,
sales
manager,
sales,
representative,
accounts
payable
and
also
the
radish
34
module.
Again.
Keep
this
in
mind.
B
You
know
what
I'm
going
to
add
another
tab,
I'm
going
to
add
another
idea
to
the
to
the
cookbook
ideation.
We
also
need
to
take
into
consideration
take
into
consideration
system
of
record
security
rules.
B
Okay,
so
now
what
we're
going
to
do
is
because
I
showed
you
before
that
we
have
this,
this
periodic
sink.
That
happens.
We
have
it
off
for
demo
purposes.
So
what
I
want
you
to
do
is
go
back
into
the
hamburger
menu
that
we
were
showing
at
the
beginning,
go
into
your
modules,
scroll
down.
Until
you
see
the
radish
34
product
go
into
service
operations.
B
And
now
we're
going
to
hang
out
for
a
second
until
until
this
goes
through
so
what's
happening
here.
Is
that
the
connector
that
we
built
in
order
to
interact
with
the
provider
service?
Remember
when
we're
implementing
the
baseline
protocol
just
checking
the
time
looks
like
we
have
an
hour
here,
which
is
plenty
when
you
implement
the
baseline
protocol
into
your
into
your
system.
B
You
have
messages
that
are
going
out
into
the
proxy
and
then
and
then
they
need
to
be
retrieved.
So
what
you're
essentially
doing
right
now
is
you
are
retrieving
the
message
that
is
coming
in
from
the
buyer,
so
you're
the
supplier,
so
you're.
Essentially,
you
know
starting
your
day,
because
you
have
this.
B
You
have
this
thing
in
a
real
world
that
would
be
just
running
constantly:
24
7.,
you're
gonna.
You
start
your
day.
You
got
your
cup
of
coffee
and
then
you're
gonna
go
ahead
and
you're
gonna
check
out
which
rfps
that
you
have
coming
in
now.
Everything
should
be
good,
and
you
know
so
far.
It's
so
good,
I'm
knocking
on
wood.
I
don't
have
much
wood,
except
for
my
head
right
here,
so
not
going
to
have
wood
everything
works.
B
If
you
can
do
us,
a
favor
go
into
the
hamburger
menu
again
go
into
your
radish
34
module,
which
you're
there
and
now
since,
since
you
are
receiving
it,
you're.
Looking
for
that's
exactly
right,
incoming
request
for
proposals,
okay,
scroll
all
the
way
down,
and
if
everything
works
well,
if
everything's
works
right,
if
you
click
on
the
bottom
one,
it
should
show
you
the
rfp
that
was
created
by
mark
it
looks
like
it
looks
like
it
is
right,
because,
if
we
scroll
over,
I
believe
that
the
price
was
something
like
90.
B
B
The
unipride
is
not
the
same,
but
the
quantity
is
the
same
right.
Quantity
is
yes,
so
so
what
happened?
Is
it
it
defaulted?
I
guess
it's
something
that
we
have
to
take
a
look
into:
it
defaulted
to
the
unit
price
that
we
are
normally
selling
it
at
or
our
volume
purchase
agreement
or
a
volume
purchase
agreement
exactly
so
at
least
we
know
that
we're
dealing
with
the
right
thing,
so
that's
good!
Okay.
So
now
what
we're
going
to
do
is
is.
Is
we're
going
to
basically
see
if
you're?
Okay
with
this?
B
B
So,
if
you're,
okay
with
it,
what
we're
going
to
do
is
just
go
ahead
and
under
the
generate
button,
click
the
send
quotation,
really
really.
The
sales
guy's
job
is
already
done
over
to
the
left
and
you're
gonna
hit
the
send
no
yep
send
quotation.
Q
B
B
B
And
again,
we're
going
to
not
gonna
run
a
background.
We're
just
gonna
click.
Okay,
so
you
can
see
what's
happening
here.
Right
is
is,
is
you
need
to
be
able
to
come
up
with
some
sort
of
a
method
that
can
be
native
to
the
system
that
you're
using
whether
it's
apis
in
this
case?
It's
business
events
to
be
able
to
take
messages
and
send
it
across
to
a
provider
stack?
B
The
provider
stack
will
take
care
of
the
rest,
we'll
go
and,
and
and-
and
you
know
if
it's
done
the
right
way-
you
have
your
zero
knowledge
proof
set
up.
You
have
your
zk
circuits
that
are
set
up.
You
have
your
verifier
key,
which
is
hidden
within
the
shield
contract.
B
Perfect,
okay!
So
now,
once
again,
you
probably
got
the
gist
over
here
now
we
have
to
go
and
retrieve
the
message
again
we're
doing
this
like
the
scenic
route
right,
you
can
either
do
it
quickly
or
we
could
just
you
know,
take
the
scenic
graph
and
that's
and
that's
what
we're
doing
so
go
into
your
service
operations.
B
And
let's
go
ahead
and
hit
okay,
let's
give
this
a
second.
So
now
you
know
just
to
kind
of
talk
about.
What's
what's
happening
in
in
the
meantime,
is
the
data
model
is
really
really
important
within
the
proxy
service
right
within
this
connector
service,
so
that
these
objects
are
being
delivered
and
are
populating
in
the
right
spot
for
the
right
in
this
case,
for
the
right,
you
know
product
the
skew
the
volume
tiers
you
know
so
on
and
so
forth.
B
So
when
we're
talking
about
the
data
model
within
the
standards,
I
mean-
that's,
that's
all
part
of
it
with
the
api
with
the
data
model
how
the
provider
service
is
taking
it,
you
know
so
so
the
way
that
we
were
doing
it
with
sap
with
unibrite.
We
were
doing
it
with
provide
it's
all.
It's
all
nicely
integrated,
it's
all
it's
all
connected,
so
that
you
know
it's
like
I'm
just
showing
you
the
long
route
in
the
real
world
when
you're
developing
this
out
for
your
businesses,
it's
just
working
in
the
background
anyway.
B
Let's
go
ahead
and
again
open
that
up,
but
this
time
nope
nope
nope,
but
but
this
time,
what
we're
going
to
do
is
we're
going
to
actually
check
on
our
rfp.
So
if
you
can
go
back
into
your
procurement
and
sourcing
module,
which
again
just
comes
out
of
the
box
right
and
let's
go
into
all
requests
for
quotations
now,
if
you're
a
manager
right,
you
are
the
one
that
can
actually
accept
or
deny
the
different
purchases.
B
So
so
one
of
our
good
friends
is
actually
a
purchasing
agent
for
a
fairly
fairly
large
chemical
company
they're,
an
agent
all
that
they
could
do
is
send
out
rfps,
but
they
can't
approve
it.
Workflows
need
to
get
then
sent
to
the
manager
the
manager
has
to
then
approve
it.
It's
just
it's
just
how
it
goes
so
scroll
down
to
the
rfp
that
you
created
earlier
mark.
B
Okay,
you
can
click
on
that.
So
now
what
we're
doing
is
now
what
we
want
to
do
is
we
want
to
manage
the
replies
that
came
back
from
the
vendor.
So
if
you
look
at
the
very
top
and
the
ribbon,
there
is
the
replies
and
go
click
on
manage
replies
now,
in
this
case.
Okay,
in
this
case,
there
was
only
one
vendor
whale
hall
sales
that
we
sent
this
out
to.
Okay,
there
was
a
question
earlier,
you
know,
does
baseline
lend
itself
to
multi-party.
The
answer
is
absolutely
right.
I
mean
when
you
have.
B
The
way
that
radish
34
was
first
shown
was
that
there
was
just
one
buyer,
two
suppliers
or
three
suppliers,
or
something
in
real
life.
You're
gonna
have,
if
you're
easily
discovered
through
this
global
phone
book
and
a
supplier
or
10
suppliers
at
30
suppliers
have
that
particular
phone
battery
that
you're
looking
for
I
mean
you're
gonna
have
tons
of
replies
anyway.
Let's
just
say
that
you're,
okay,
with
whatever
that
it
is
right-
and
you
can
go
ahead
now
and
where
is
it
we
want
to
click
approve?
B
I
believe
that
it
is.
You
want
to
go
under
process
and
select,
accept.
B
B
Done
and
let
me
see
from
this
system
admin
side,
you
might
be
missing
the
thing.
Let
me
just
sign
in
really
quick.
I
knew
I
knew
there
was
going
to
be
something
there's
always
something
in
their
header
just
one
second
here
I
think
I
just
have
to
give
the
right
the
right
permissions,
just
one
sec,
I'm
signing
in
on
the
admin
side
from
my
side.
B
Looks
like
you
do.
Have
the
right
thing:
let's
just
click
the
back
button.
B
And
let's:
let's:
let's
go
back
into
the
procurement
module
that
we
were
just
at.
Let
me
see
if
it's
there
and
let's
go
to
all
requests
for
quotations.
B
And
yep,
that's
that's
just
where
we
were
interesting,
there
should
be
a
button
for
approve.
Let's
see
manage
manage
replies
is
where
we
definitely
want
to
be.
B
Up
and
up
on
the
top
you
see
you
see
you
have
the
ribbon
on
the
top.
Let's
click
on
manage
replies.
B
B
Okay
and
we're
gonna
wait
for
this
one
to
go
through.
You
could
see
now
you
can
click
on
click
on
the
notification
bar,
and
this
is
now
these
workflows
that
happen
right.
So
now,
you're
you're,
essentially
posting
what's
happening
and
the
purchase
order
has
been
created.
So
that's
so
that's
good!
That's
that's
exactly
that's
exactly
what
we
want
to
see
for
tokenization
right.
So
how?
How
can
we
create
these
tokens?
B
Well,
it
could
be
argued
that
in
this
particular
step,
right
now,
you're
minting
the
token
you're,
just
not
issuing
it
right
so
just
kind
of
think
through
this
stuff.
As
you
start
to
see
this,
and
now
you
know
and
and
I'm
gonna
go
back
into
the
cookbook
ideation
and
I'm
I
think,
I'm
just
gonna
write
down
tokenization.
B
Workflows:
okay,
cool
cool,
okay;
so
so
now
from
now
from
that
point,
what
I
would
like
for
you
to
do
now:
we're
gonna
go
ahead
and
issue
the
po.
So
can
you
just
click
on
click
on
the
general
button
and
the
on
on
the
very
top
yep
and
click
on
purchase
order.
B
B
B
To
the
right
over
to
the
right,
it's
like
right,
dab
in
the
middle
there
you
go,
you
can
hit
confirm
you
can
let
this
go
through
now.
Here's
an
interesting
thing
to
know
see
now
you're
done,
you
know
how
we
went
back
and
forth
and
we
always
click
the
service
operations
in
order
to
send
and
pull
all
of
our
messages
to
and
from
our
provider
stack
well.
This
is
one
that
comes
native
out
of
the
box
so
for
purchase
orders
you
actually
don't
need
to
click
on
the
service
operations.
B
For
that
particular
thing,
it
just
automatically
goes
right
into
the
connector
queue
and
it
goes
right
into
the
provider
service
which
in
this
case
would
be
the
provide
stack.
Okay,
so
just
just
know
that
there's
certain
things
that
are
native
and
there's
certain
things
that
need
to
be
custom
configured
sending
a
po
just
happens
to
be
one
of
these
things
that
is
built
out
of
the
box.
B
Okay,
so
mark
really
really
appreciate
that
your
your
your
job
is
done.
You
sent
out
a
po
and
the
whole
thing
you
deserve
yourself,
a
coffee.
So
thank
you
for
that.
B
And
let's
finish
up
this
workflow
very
cool,
so
if
you
can
now,
let's
go
back
in
and
let's
run
the
service
operations
again,
so
so
open
up
the
open
up
that
that
hamburger
menu,
let's
go
to
the
radish
34
module,
which
looks
like
you're
already
open
to
it.
Let's
go
to
the
service
operations
perfect
and
let's
go
hit.
B
So
let's,
let's
wait
for
this
to
go
through
and
again
all
these
records
are
being
created
and
and
and
I'll
show
you
a
couple
things
from
from
the
system
admin
side
to
when
when
we're
done
with
this
use
case.
But
it
looks
like
we're
almost
through.
B
Awesome
so
let's
go
back
into
our
radis34
module
and
if
you've
noticed
now
now
go
to
outgoing
proposals
because
you
sent
it
out
and
let's
scroll
down.
So
if
you
notice
that
there's
two
different
things
that
we
were
using,
one
was
the
the
custom
module
that
we
built
again
product
cookbook.
B
B
I
think
it
was
40
cheaper
than
the
sales
price.
So
congratulations.
Your
boss
is
going
to
be
really
proud
of
you
if
you
can
click
on
the
sales
order.
So
what
happened
is
now
when,
when,
when
that
gets
approved,
the
po
on
your
side
turns
into
a
sales
order,
so
you
can
click
on
the
sales
order
and
looks
like
everything
seems
to
be.
Everything
seems
to
check
out
right.
You
can
go
ahead
and
double
check,
but
the
beauty
about
this
is
that
it's
going
to
be
wrapped
up
within
the
zero
knowledge
circuits.
B
So
there's
nothing
really
for
you
to
check
right.
It's
like
it's
all,
it's
all
there,
so
you
can
actually
even
automate
the
workflow
to
just
confirm
the
sales
order
and
up
on
the
very
top
up
in
the
very
top
you
scroll
to
the
right
a
little
bit
more
a
little
bit
more
and
you
can
confirm
sales
order
right
to
the
left
to
the
left
right
there
and
that's
essentially
it
so
you
can
go
ahead,
hit
okay
and
then,
from
that
point
on
you
know
you
could
post
a
document
without
printing.
B
It
select
ok
to
continue,
and
that's
that
so
you
know
from
here
on
out.
We
can
extend
it
and
we
can
now
go
into
baselining.
You
know
the
actual
pick
pack
and
the
shipping
and
and
the
receiving
between
the
two
companies,
but
we're
going
to
stop
right
here,
because
that's
essentially
what
radish
34
was
aiming
to
you
know
show
it
was
showcasing
these
two
companies,
buyer
and
supplier
kind
of
working
together
and
and
and
what
we
wanted
to
show
here
is,
and
then,
if
you
can,
you
can
stop
sharing
your
screen.
B
Frederick
really
really
appreciated
mark.
Thank
you
so
much
for
not
making
me
look
silly
here
and
nobody
is
knowing
no
one
is
participating,
so
I
mean
that
was
that
was
cool.
Thank
you.
Q
Question
can
how
could
that
be
used
to
show
the
supply
chain
as
well?
So,
as
the
buyer
mark
may
I
wanted
to
like,
I
don't
know,
make
sure
that
some
of
the
suppliers
that
I
would
use-
maybe
I
don't
know
I
in
the
u.s
or
something
like
that-
is
that
something
that
can
be
done
there
here
as
well
with,
like,
I
don't
know,
zero
knowledge
proof
or
something
so
that
they
don't
show
everything
as
a
supplier.
B
Q
Could
mark
may
have
a
requirement
that
every
part
is
being
made
in
the
u.s
so
but
his
only
connection
is
through
me
right
and
me,
I
may
have
some
suppliers
as
well
and,
and
so,
if
I'm
also
using
if
I'm
baselined
with
my
or
so
suppliers
can
can,
can
something
flow
back
up
to
mark
where
you
could
see
that?
Yes,
all
my
suppliers
are
producing
things
from
the
us.
B
So
so,
let's
just
say
that
in
the
cookbook
ideation,
what
I
just
did
was
I
just
wrote
down
in
line
22
track
and
trace
is
a
feature
that
you're
that
you're
discussing
and
and
the
answer
that
I'm
going
to
quickly
ida.
The
answer
is
most
likely
yes
and
it
comes
down
from
the
requirement.
So
you
know
you
can
include
the
zero
knowledge
proofs
into
there
so
that
you
know
what
where
wherever
the
data
points
are
coming
from,
is
that
you
can
probably
include
some
geo
locale
in
there.
O
So
I
mean
would
that
be
one
of
the
requirements
within
the
volume
purchasing
agreement,
along
with
the
price
it
could.
Q
I
B
I
know
with
100
certainty,
for
example,
you
know
in
the
us,
if
you
get
contracted
by
you
know,
through
a
government
contract,
you
have
to
have
u.s
citizens
on
it
and
then
the
certifications
happen
afterwards,
but
you
do
have
to
prove
it.
O
Well-
and
you
could
actually
take
that
out
to
say
you
know
that
we're
contracted
that
we
only
use
a
certain
shipper
like
they
say,
dhl
within
europe,
just
because
you
know
fedex
or
ups
may
not
serve
all
the
geographies
but
dhl.
You
know
it's
definitely
in
there,
so
they
can
say
you
know
and
we
have
a
volume.
O
You
know
a
volume
pricing
agreement
with
dhl
and
so
in
order
to
you
know,
honor
the
pricing.
You
know
for
the
for
the
units.
You
know
we
want
to
contemplate
that
you're
using
that
and
if
you
insist
on
using
a
different,
you
know
common
carrier.
B
B
So
here
looks
like
we
have
looks
like
we
have
have
a
couple
extra
minutes
here,
so
here,
let's
just
showcase
a
couple
things.
B
B
Going
well
so
yeah,
so
so,
just
to
give
dom
a
little
bit
of
intro
he's
going
to
be
going
on
a
little
bit
he's
going
to
be
talking
about.
You
know
what
he
did.
His
company
did
with
regards
to
baseline
salesforce
and
is
gonna.
You
know
look
I
mean
this
whole
cookbook
idea.
B
B
B
B
B
Good
I'm
good.
I
just
wanted
to
see
if
there's
any,
if
there's
any
thoughts
that
you
had
with
regards
to
things
that
things
that
we're
showing
any
ideas
that
you
think
that
we
can
write
into
you
know
our
our
our
backlog
of
ideation
how's.
Everything
going
here
for
you.
S
You
know
it
really
looks
like
you
guys
are
covering
so
much.
I
don't
actually
have
anything
to
add.
My
only
note
would
be
that,
in
addition
to
adding
coordination
and
just
kind
of
these
ideas,
I
want
to
bring
up
the
fact
that
this
should
be
from
a
user
experience
standpoint,
something
we
we
talk
about.
You
know
like
how
can
we
make
this
easier
for
people
to
use?
How
can
we
integrate
this
into
workflows,
and
so,
as
we
have
these
ideas,
I
think
we
should
also
talk
about.
S
B
I
think
that's
spot
on.
You
know,
I
think
that's
100
really
couldn't
have
said
it
better
myself.
I
mean,
as
as
we
were,
showing
some
of
these
modules
right
within
the
d365
environment.
You
know
the
reason
why
we're
showing
these
modules
is
just
to
further
reiterate
the
fact
that
you
know
like
let's
say
that
you
work
for
a
large
company,
I'm
gonna
make
one
up.
Let's
say
that
you
work
for
coca-cola,
it's
like
my
favorite
company
to
make
up
and
they
and
they
happen
to.
B
They
happen
to
be
the
first
ones
that
say
that
they're
using
a
baseline
protocol
with
kona.
So
that's
awesome,
but
let's
say
that
you
have
this
large
right
and
you
hey,
I'm
gonna,
I'm
gonna
develop
something
whatever
it
is.
Change
management
is
so
serious
right,
so
you're
going
to
you're
going
to
think
it
through
and
they
want
to
see.
Well.
How
could
we
make
this
a
great
user
experience
for
our
users
for
our
customers
so
that
there's
little
rigor
involved
on
the
other
end
of
it?
B
B
B
You
know,
and
with
that
in
mind
here,
I'll
just
continue
sharing
my
screen
right
here.
So,
let's
see
with
that
in
mind,
let's,
let's
kind
of
take
a
step
back
now
you
kind
of
see
where
we're
coming
from
with
this
slide
of
business
use
case
design
starts
at
the
beginning
provider,
build
is
kind
of
happening
there
and
you
know
it's
like
sequential,
and
then
you
need
to
be
able
to
connect
and
deploy.
B
So
this
whole
connection
and
deploy
aspect
is
where
we're
talking
about
having
a
great
ux,
because
who
cares
what's
happening
on
the
back
right
and
I'm
not
saying
this
to
undermine
the
need
of
a
provider
service
I
mean
without
a
provider,
service
baseline
doesn't
work
right.
It's
just
a
you
know
it's
nothing,
but
once
you
have
these
things
in
there
right.
B
Are
you
going
to
really
go
to
your
to
your
boss,
your
manager,
your
customer,
your
point
of
contact,
your
prospect,
your
lead,
whatever
the
story
is
and
you're
going
to
say,
hey,
I'm
going
to
give
you
this.
You
know
cli
based
something
you
know
it's
gonna
you're
gonna
be
confronted
with
with
some
sort
of
a
rigor.
So
that's
where,
when
you
wanna
connect
and
deploy,
I
mean
things
have
to
look.
Things
have
to
look
like
out
of
the
box.
B
It's
got
to
be
easy
for
people
to
just
jump
in
and
go
and
and-
and
I
know
going
back
to
going
back
to
oh
yeah,
look
at
this-
we
got
we
got
tons
of
sessions
happening
now.
That's
awesome!
B
If
you
go
back
to
the
global
phone
book
project,
I
mean
that's,
that's
where
that's
where
a
lot
of
this
magic
is
happening
along
with
this
core
interfaces,
where
you
know
you
have
everything,
wired
up
things,
look
and
smell
and
feel
just
like
they
normally
are
and
even
getting
set
up
right.
You
have
a
simple
way
that
you
can
either
get
verified
credentials
or
issue
verified
credentials.
So
I
mean
that's
on
that
tip.
B
Let's
see
so
we
have
around
30
minutes
here.
We've
experienced
that.
Let
me
ask
you:
let
me
ask
you
from
mark's
perspective,
frederick's
perspective,
if
you're
still
here,
some
of
the
other
ones
that
happen
to
you
know,
staying
watch
this
whole
experience.
You
know
dynamic
365..
What's
your
feedback
on
that?
B
Q
Some
it's
something
that
I'm
not
quite
sure
yet
is
what
is
like
really
the
baseline
part.
So
I
think
it's
just
the
radish
module
section
versus
what
is
something
that
was
developed
on
the
microsoft
platform.
Just
for
this
for
doing
procurement,
I'm.
D
Q
Quite
sure
oh
like
if
I
wanted
to
do
to
take
that
and
become
like
a
supplier
like
in
my
in
my
organization.
Can
I
just
access
all
of
that
or
just
the
radish
module
good.
B
B
There's
a
couple
ways
to
look
at
it
from
an
admin
perspective.
The
first
part
that
comes
with
baseline
is
this
custom.
Radish
34
module,
if
you
will,
or
as
they
call
it
in
microsoft
e365,
they
call
it
a
workspace.
B
B
B
B
All
they
need
to
do
is
go
to
the
microsoft,
app
store
and
download
it
when
they
install
radish
34
all
the
services
pop
up
right.
It's
all!
It's
all
done.
It's
like
it's
like
we
like
to
say
around
here.
It's
like
the
easy
button.
You
click,
you
click
the
button
and
then
you
go
from
a
development
perspective.
B
What
we
needed
to
also
do
from
a
baseline
perspective,
too,
is
we
needed
to
come
up
with
the
way
that
we
were
going
to
create
these
parameters
in
order
to
connect
these
services,
the
backend
services
to
this
d365
world?
So
this
is
where
the
baseline
stuff
begins
to
come
in
that
we
needed
to
come
up
with
a
way
to
come
up
with
a
connector
that
connects
to
a
provider
stack
in
this
case
it
was
again
the
provide
the
provider
shuttle
services.
B
Okay,
the
next
thing
that
we
want
to
showcase
is
while
the
global
phone
book
is
not
implemented
yet
right,
it's
like
right
now,
the
only
way
to
do
it
like
right
now,
right
now,
literally,
if
somebody
said
we
want
to
create
this
buyer
supplier
network,
we
would
need
to
wire
things
up
right
now,
manually
to
a
certain
degree
where,
where
baselining
comes
in
from
a
conceptual
perspective-
and
this
is
why
we're
here
in
this
workshop-
is
because,
as
you
start
to
add
new
suppliers
or
add
new
vendors
or
depending
on
what
your
counterparty
is
right,
you
need
to
add
them
to
the
org
registry
right.
B
You
have
your
work
group,
so
that's
where
the
global
phone
book
comes
in,
because
you
see
how
manual
this
process
is
right
now.
This
has
nothing
to
do
about
baseline,
but
it
has
everything
to
do
about
baseline
right
now,
because
if
there
was
a
way
that
we
can
create
a
way
to
query
all
the
dids
that
are
part
of
this
global
phone
book,
everything
makes
everything
is
easier
from
discoverability
to
just
like
onboarding
and
off-boarding.
B
B
You
literally
click
this
new
button
and
you
have
to
go
through
all
these
steps,
and
you
have
this
paperwork
here
in
front
of
me,
like,
like
literally
a
family
member
of
mine,
that
that
was
his
job.
I
worked
for
a
large
chemical
company.
Onboarded
individuals
had
a
stack
of
paper
literally
just
you
know,
data
entry
mistakes
happen
and
when
you
type
in
the
wrong
address,
the
po
gets
sent
to
the
wrong
place,
for
example,
and
that's
just
one
of
the
issues.
B
So
what
we're
urging
everyone
to
think
about
is
like,
while
this
screen
isn't
baseline,
yet
it's
got
everything
to
do
with
baseline,
because
we
need
to
find
a
way
that
we
can
create
this
global
phone
book,
make
a
data
schema
behind
this
behind
the
dids
and
actually
sync
that
up
with
this
did
right
with
that
decentralized
identifier,
from
a
verified
credenti
from
from
a
from
a
legitimate
source
and
have
all
that
pre-populate
like
it's
done.
You
know
and
that's
and
that's
the
key
for
that
one.
B
The
other
thing
that
we
want
to
showcase
is
the
core
interfaces,
so
as
we
as
we
onboard
the
new
vendor
or
the
new
customer
or
the
new
counterparty,
depending
on
your
use
case,
and
we
go
ahead
and
need
to
connect
them,
you
need
the
core
interfaces.
Part.
If
you
don't
have
the
core
interfaces,
part
you're
not
going
to
be
able
to
see
baseline
and
it's
kind
of
tricky
in
a
way
frederick,
because
what
we
wanted
to
showcase
is
that
there's
no
blockchain
really
in
this
right.
B
It's
like
yeah,
there's
blockchain,
that's
running
in
the
background
and
baselining
is
running
in
the
background,
but
from
a
user
experience
like
avia
was
talking
about
you,
don't
really
want
to
show
all
that
stuff
right.
You
want
people
to
be
where
they
normally
are.
So
all
of
this
stuff
is
in
the
background.
S
Also
add
one
to
that
as
well.
I
think
one
of
the
things
that
we
talk
about
a
lot
in
baseline
is
how
boring
it
is
in
some
ways:
it's
not
boring
it's
exciting,
but
how
boring
it
looks
and
I
think,
for
a
lot
of
people-
that's
very
comforting,
especially
in
an
enterprise
system,
and
so
we
love
that
kind
of
thing
and
I
think
that's
actually
a
unique
aspect
of
baseline.
S
So
if
people
have
ideas
about
how
to
implement
a
system
kind
of
like
what
you
were
doing
talking
about
before
with
the
phone
book
where
it's
like
a
double
dip,
you're
automating
something
to
reduce
error
and
you're,
making
this
more
usable.
So
we
love
that
and
new
ideas
for
how
to
do.
That
would
be
incredible
if
anyone
wants
to
suggest
some
or
put
some
in
the
sheet.
B
Yeah
again
great
great
call
to
action,
I
mean
you
know,
frederick,
as
you're
coming
up
with
your
thoughts.
Don't
let
your
thoughts
go
to
waste,
put
them
in
the
sheet.
You
know
put
them
in
the
notes.
Put
them
anywhere
put
them
in
the
powerpoint
presentation
and
we'll
and
we'll
gather
it,
and
we
will
reconvene
and
come
up
with
ways,
but
you
know
just
to
further
reiterate
now
that
we
saw
it
and
we
can
go
back.
B
You
know
this
envision,
connector
that
we
had
to
develop
in
order
to
make
the
connection
between
the
user
interface
and
the
provider
stack.
That
was
also
something
that
again
is
just
running
in
the
background.
It's
it's
not
something
that
should
be
seen
unless
the
company
requires
for
it
to
be
seen.
So
what
you're,
seeing
over
here
right,
you're,
seeing
the
cues
and
the
messages
that's
coming
through
through
through
the
azure
service
bus?
That's
that's
what
our
connector
is
built
on.
B
You
know
it's
like
if
you're,
if
you're
an
admin
to
your
azure
environment,
you're
gonna,
see
this
if
you're
a
purchasing
agent.
The
last
thing
you
care
about
is
seeing
you
know
these
spikes
and
dips.
I
mean
people
are
going
to
think
like
like
they're
trading,
something
or
something
over
here.
You
know
it's.
The
purchasing
agent
just
doesn't
care,
they
want
to
just
send
something
out.
They
want
to
get
their,
they
want
to
get
their
rfp
filled
and
go
on
to
the
next
one,
and
then
they
want
to
hammer
you
down
on
price.
B
B
But
again,
all
of
this
is
just
not
possible
unless
the
core
was
developed
out
and
that's
again,
the
product
cookbook
is
like
the
big
funnel
of
ideas
of
what
could
you
know
again,
I'm
just
kind
of
reiterating
it
so
again,
zero
knowledge
proofs,
is
this
concept
and
is
so
techy
and
you're,
dealing
with
fields
and
you're
dealing
with
formulas
and
and
and
and
equations
and
mathematical
equations
and
things
it's
complicated.
B
You
know,
and
yeah
socrates,
as
as
as
a
as
a
protocol,
has
has
abstracted
all
that
to
make
it
easy
for
folks
that
don't
understand
zero
knowledge
proves
to
start
developing
out
with
socrates,
but
there's
other
there's
other.
You
know,
and
it's
not
to
say
that
socrates
is
the
only
the
only
protocol
out
there,
and
I
think
that
the
zk
interface
group
over
there
is
talking
about
options
and
what's
out
there.
B
But
what
I'm
talking
about
here
is
that
at
the
user
experience
level
like,
like
obvious,
said,
we
need
to
make
it
easy
for
everyone
to
just
to
just
do
right
or
to
not
do,
and
what
I
mean
by
that
is
that
there
needs
to
be
a
way
to
lock
down
certain
fields.
Certain
tables
certain
forms,
even
at
the
whole
form
level
and
here's
just
like
a
snippet
of
code
of
of
what
we
did
obviously
just
to
enable
things.
B
But
what
we
can
do
is,
depending
on
business
processes,
to
lock
certain
things
out,
and
I
know
that
dom's
going
to
talk
a
lot
about
that
too.
So
you'll
hear
it
from
me
and
then
you'll
hear
it
from
him
and
we'll
all
be
able
to
kind
of
put
our
ideas
together
so
that
we
accelerate
and
that's
and
that's
really
that's
really
what
it's
all
about.
So
so
frederick.
You
know
just
to
kind
of
recap.
A
lot
of
what
you
saw
is
baseline
running,
underneath
everything.
Q
Okay
and
and
the
radish
is,
is
like
the
the
like.
The
procurement
use
case
right,
exactly
meaning
like
when
you
talk
about
like
the
formulas
and
all
that
is
basically
all
the
all
the
dk
proof
formulas
used
for
for
procurement.
Q
B
Would
be
something
else
yeah,
it
would
be
like
carrot
85.
I
just
made
that
up,
but
you
know
the
radish
34
is
specific.
It's
a
specific
use
case,
that's
specific
to
the
procurement.
You
know
reference
implementation
that
was
first,
that
was
first
launched
when
baseline
protocol
was
launched
and
it
was
showcased
on
a
you
know
like
like.
I
could
show
you
here,
go
to
the
screen.
B
Radish
34
was
this.
Buyer
and
supplier
use
case
that
showcased
rfp
proposal
po.
There
was
an
msa
step
as
well
in
between,
and
it
was
first
showcased
with
the
custom
web
app
and
what
we
aim
to
do
over
here
between
unibrite
and
provide
and
envision
between
us
is
to
showcase
how
you
could
take
this
custom
web
app
and
then
put
that
to
you
know
a
real
powerful
erp
that
has
you
know
multi-million
dollar
implementations
tied
be
tied
behind
them.
It.
B
It
just
furthers
the
proof
that
you
could
do
it
with
this
with
the
erp
or
you
could
do
it
with
the
web
app
or
like
lime
change
showed.
You
could
do
that
with
google
sheets
right.
It's
just
anything.
That
is
a
state
machine
that
captures
it.
You
can
baseline
that
against
something
else.
So
what
we're?
What
we're
striving
for
in
this
session
is
to
ideate
around
what
other
use
cases
would
be
beneficial
for
baselining,
like
procurement.
S
B
So
okay
looks
like
we
have
around
20
minutes
here
until
until
dom's
presentation
dom
do
you
want
to
go
now?
If
you
want
some
more
time
or
or
do
you
want
to,
or
do
you
want
to
wait
until
your
session?
How
do
you
want
to
handle
that.
P
Oh
it's
up
to
you.
I
mean
it's
up
to
the
group
here
I
mean
whatever
everyone
wants
to
spend
next
20
minutes
on.
I
you
know
I
can
start
early
or
if
we
want
to
just
you
know,
keep
the
general
discussion
going
or
maybe
do
kind
of
like
a
segue
conversation
into
the
session.
It's
yeah
completely
up
to
you.
B
Yeah,
I
mean
that's,
that's
actually
a
really
good
point
right.
So
what
does?
What
does
everybody
want
to
talk
about?
Now
right?
We
have.
I
actually
thought
that
this
whole,
you
know,
screen
sharing
and
having
people.
Click
through
was
going
to
take
a
lot
longer
than
it
actually
did
really
glad
that
the
demo
worked.
B
I'm
really
glad
that
mark
volunteered
and
frederick
as
well.
That
was
awesome
and
there
was
really
no
snags
or
issues.
It
was
pretty
sweet.
Let
me
take
a
look
at
the
youtube
chat.
What's
what's
what's
going
on,
what's
going
on
on
youtube,
so
we
see
we
see
here
that
there
was
a
couple
comments
around.
B
What
would
be
the
selling
point
for
orgs
to
push
towards
baselining
their
current
system?
What
other
erp
systems
will
be
offered
in
the
future?
By
baseline,
I
mean
let
me
just
like,
like
bars,
I
appreciate
you
asking
that,
but
it's
up
to
you
it's
up
to
it's
up
to
everyone
in
this
room.
What
would
be
the
next?
What
would
be
the
next
erp
system
that
is
offered
you
know?
Baseline
is
not
a
company
right,
it's
not
a
product,
it's
a
methodology!
B
So,
literally
whatever
it
is,
it's
community
driven
all
right.
So
if
I
could
just
answer
that
by
taking
a
look,
let's
go
do
a
quick,
quick
session
on
the
ideation,
so
here
some
of
the
systems
so
d365
we
just
showed
you
sap.
We
talked
about
stefan's,
going
to
jump
in
soon
salesforce
dom
is
dom,
is
on
deck
and
ready
to
go.
B
Google
sheets
we
showed
excel,
we
didn't
show,
but
you
might
as
well
just
group
that
together
with
sheets
it's
basically
the
same
functionality,
transbook,
that's
another
one.
Somebody
said
many,
especially
in
a
gdpr
regulated
country.
Then
we
have
multiple,
multiple,
multiple,
multiple.
What
I
would
ask,
instead
of
writing
multiple.
B
I
don't
know
if
anyone
is
here
that
actually
wrote
that
in
there
instead
of
writing
multiple,
let's
be
specific
pick
one
pick
two
write
them
out
there
so
that
all
of
us
have
a
better
idea-
and
maybe
maybe
you
know
as
as
a
community-
we
come
together
and
you
know
the
community
really
depends.
You
know
decides
what
is
the
next
erp
system,
I'm
just
looking
at
the
second
screen
here.
So
you
know
I
don't
want
to
make.
It
seem
as
if
there
is
it's
it's
like
it's.
B
It's
it's
a
specific
product
offering
by
a
company.
You
know
it
just
so
happens
that
envision.
You
know
our
company
over
here.
It
just
so
happened
that
we're
showing
the
d365
one
it
just
so
happened.
That
unibrite
was
showing
was
showing
the
sap
that
dom
and
his
company
were
showing
salesforce.
That
lime
chain
was
showing
google
sheets
that
provide
with
showing
how
they
provide
a
provider
service.
B
P
I
think
we
can
also
talk
to
the
fact
that
a
lot
of
us
are
using
the
same,
provide
stack
and
though
today
we
haven't
done
like
a
dynamics,
the
sales
source-
it's
actually
you
know,
I
think,
very
doable
in
a
short
amount
of
time,
given
that
we
are
using
the
provide
stack
with
and
working
with
kyle.
P
B
I
O
And
one
thing
that
you
come
to
find
out
is
you've
got
certain
people
that
are
saying
hey.
We
love
our
sales
force,
we
love
our
dynamics,
we
love
our
whatever
and
we're
not
getting
rid
of
it
and
we're
not
asking
that
you
have
to
get
rid
of
it.
You
can
basically
sit
there
and
sync
it
up,
and
this
goes
back
to
where
I
think
what
you
were
talking
about,
and
I
was
the
one
that
put
in
those
four
right
there,
beginning
with
enterprise
risk
management.
O
Where
I
put
multiple-
and
this
was
something
that
we
talked
about
in
the
first
hour
where
you're
gonna
have
people
within
the
within
an
enterprise-
and
this
goes
back
to
does
it
have
to
be
multiple
enterprises?
Can
it
be
within
a
single
enterprise,
and
I
would
say
absolutely
because
you're
going
to
have
people
within
there
that
need
that
holistic
view
of
everything
going
on
within
the
enterprise
at
any
given
moment.
O
Mainly
that's
going
to
be
your
risk
managers,
it's
going
to
be
your
chief
risk
officers,
basically
people
that
need
to
find
out
what
is
the
health?
What
is
the
movement?
How
is
everything
you
know
going
on
and
they
benefit
from
knowing
all
of
that
in
real
time,
and
you
know
right
now.
One
thing
that
hamstrings
a
lot
of
the
risk
managers
are
the
people
monitoring.
All
that
is
the
gatekeeping.
O
Maybe
they're
gonna
have
a
there's,
gonna,
be
one
one
platform,
maybe
payroll
or
finance
that
is
gonna
batch
update.
You
know
at
midnight
every
night,
so
they're
gonna
have
a
lag
time
and
having
that
real
time,
data
that
they
need
or
you're
going
to
have
logistics
or
your
dispatchers,
that
say
hey
can
I
go
ahead
and
ship
this
has
it
already
been
paid
and
they
need
to
go
ahead
and
have
that
real
time
that
real-time
data
and
baseline
will
allow
for
that.
O
B
You
know
and
mark
if
I
could
just
call
you
out
for
a
second.
You
know
something
that
you
said:
I've
just
been
taking
a
couple
notes,
so
multiple
organizations
versus
one
batch
financing
finance
batch
updating
logistics
dispatchers,
showing
the
real-time
data.
This
one
right
here.
The
logistics
dispatchers
showing
real-time
data,
sounds
to
me
like
a
very
similar
discussion
that
was
discussed
along
with
the
track
and
trace
to
show
the
locations
of
the
suppliers.
While
it's
not
showing
the
locations,
you
want
to
really
show
inventory
or
assets
on
the
move.
You
know.
O
Right
well,
right
and
and
the
way
that
I
was
I
was
actually
working
as
within
a
single
enterprise,
because
that
was
the
original
discussion
that
we
had
is.
Do
you
need?
Can
this
happen
within
a
single
enterprise,
and
I
would
say
absolutely
and
you.
O
And
that
was
actually
one
of
the
first
use
cases
that
I
you
know
had
started
working
on
and
they
wanted
to
look
at.
O
You
know,
within
fabric
and
within
a
private
blockchain
within
an
enterprise
is
it
was
you
know
basically
unifying
having
that
unifying
mechanism
of
all
these
siloed
platforms
that
each
different
each
different
department
was
going
to
be
using,
and
you
know
you
had
to
basically
start
putting
together
that
api
management
to
where
you
know
that
at
least
the
risk
manager
or
the
controller
could
on
a
dashboard
in
a
risk.
O
Management
from
information
system
could
actually
see
all
of
that
and
have
that
real
time
data,
and
you
know
it's
one
of
those
where
you
know
doing
it
within
a
private
blockchain.
You
could
do
it,
but
you
know
it.
It
did
not
outperform
the
current.
O
So
that's,
where
baseline
really
offers
a
distinct
advantage,
where
you
are
actually
having
that
you
know,
demonstrated
consistency
between
these
silent
architectures
and
it's
very
interesting
yeah,
and
it's
for
the
benefit
of
the
people
that
you
know,
like
your
chief
risk
officers,
like
your
risk
managers
that
need
that
real
time
holistic
view
of
the
entire
organization.
As
far
as
what's
going
on,
I
I
liken
their
their
role
to
almost
being
like
an
air
traffic
controller.
They
need
to
know.
Where
is
everything
right
now.
B
Yeah-
and
you
know
just
to
speak
to
the
single
organization
thing,
it's
kind
of
interesting
one
of
one
of
our
earlier
clients
is
an
automobile
manufacturer
and
they
have
the
way
that
they're
set
up
is
that
they
acquired
many
many
many
many
different
offices
across
the
world
and
their
systems
were
all
different.
Every
every
every
office
across
the
different
globe
had
its
own
accounting
department
and
the
accounting
department
all
had
their
own
choice
over
what
software
they
would
use.
B
So
there
was
this
crazy
reconciliation
issue
that
they
had,
and
that
was
one
of
the
things
that
they
were
looking
at
was
improving
the
reconciliation
time
to
the
point
where
they
they.
You
know,
some
of
the
some
of
the
kpis
was
on
time
time
to
reconcile.
B
Yeah
yeah,
you
know
we
did
a
case
study
on
well.
There
was
a
case
that
I'd
say
that
we
did
it.
We
did
a
webinar
a
couple
a
couple
months
back
and
we
spoke
about
the
acquisition
that
revlon
did
so
so
revlon
a
makeup
provider
went
through
and
they
acquired
elizabeth
arden.
It
was
a
really
interesting.
B
B
They
wanted
to,
I
mean
I'll,
just
say
I'll
just
say
it
like
it
was
so
revlon
was
using
d365,
I
want
to
say,
and
elizabeth
arden
was
using,
it
was
oracle
or
maybe
it
was
the
other
way
around.
I
think
it
was
revlon
was
oracle,
the
other
one
was
d365
and
what
happened
was
that
they
they
they
merged
through
that
acquisition,
and
in
that
merger
they
decided
not
to
keep
the
same
erp
system
but
actually
move
to
another
one.
B
It
was
an
sap
system
that
they
decided
to
it.
Wasn't
sap's
fault
that
it
went
down.
It
was
the
actual
to
your
point
mark.
It
was
the
implementation
of
that.
So
there
was
this
crazy
crossover
between
changing
their
systems
up
and
when
they
crossed
over.
The
systems
went
down
for
a
period
of
time
and
they
literally
lost
out
on
millions
and
millions
and
millions
of
requests
to
fill
their
their
their
stores,
the
the
people
that
would
buy
from
them
with
orders
they
lost.
B
B
Exactly
so
so
they
lost
money
on
fulfilling
the
orders
through
expedited
shipping
people
didn't
want
to.
B
You
know
people
found
other
suppliers
to
go
and
get
from
or
this
and
that
so
anyway,
long
story
short
is
that
would
they
have
been
better
instead
of
just
changing
their
systems,
keep
the
same
system
that
they
were
fine,
but
just
baselining
the
records-
maybe
maybe,
but
but
this
is
but
but
but
this
is
a
point
to
speak
at
from
a
you
know,
like
an
implementation
perspective,
that
there
is
new
technology
out
there
like
baseline
and
the
product
cookbook.
That
allows
you
to
actually
modernize
the
way
that
you're
doing
the
systems
you
can.
B
We
can
now
start
to
think
a
little
bit
different
and
I
think
that's
that's
kind
of
where
we're
at,
and
it
might
even
be
a
good
segue
over
here
to
kind
of
kick
this
off
to
dom.
So
here
we
showed
you
what's
going
on
with
d365.
I
think
you
know
with
four
minutes
to
spare.
I
think
dom.
That
would
be
a
great
time
for
me
to
pass
the
torch
to
you
and
take
us
through
what
you
got
awesome.
P
P
C
P
All
right,
so
I
want
to
be
mindful
so
we'll
start
at
a
time
here
in
a
few
minutes,
but
can
just
give
some
a
brief
background
on
the
company
and
what
we've
been
doing
in
the
baseline
community
for
the
last
couple
months
here.
P
P
We
started
working
on
this
and
the
main
idea
was
essentially
to
connect
salesforce
as
a
platform
to
ethereum,
as
this
kind
of
a
new
emerging
protocol,
and
I
think,
prior
to
this
I
had
worked
in
the
salesforce
ecosystem
at
an
isv
was
focused
on
the
middle
office,
a
company
called
aptus
and
mostly
focus
on
like
contract
life
cycle
management,
kind
of
middle
office
processes
between
companies.
P
But
I
saw
at
the
same
time
kind
of
in
these
different
customer
engagements
on
salesforce.
There
was
always
kind
of
a
silo
whether
it
was
even
salesforce
or
to
salesforce,
or
there
was
kind
of
this
process
silo
that
these
companies
had
whether
it
was
sending
a
contract
back
and
forth,
and
even
if
they
were
from
the
same
company
provider
or
the
same
application
provider,
there
was
still
this
kind
of
reconciliation
process
that
had
to
happen,
and
meanwhile,
blockchain
and
ethereum
and
smart
contracts
are
kind
of
on
the
rise
and
okay.
P
Maybe
there
is
something
here.
I
think
one
of
the
problems
we
identified
early
on,
though,
was
that
a
lot
of
the
data
was
public
right.
So
if
you're
posting
an
msa
or
an
nda
to
ethereum
right
all
the
input
data
is
going
to
be
public.
So
you
know
fast
forward.
P
Here
we
are
three
years
later
baseline
protocol
gets,
you
know,
created
it
solves
a
lot
of
these
privacy
issues,
and
so
we
saw
it
as
an
opportunity
to
essentially
extend
everything
we
had
already
built
on
the
salesforce
platform
and
leverage
the
new.
You
know
features
of
baseline
to
essentially
kind
of
build
out
this
plug-in
for
the
salesforce
ecosystem,
so
they
can
communicate
with
the
other.
P
The
other
plugins,
like
the
one
that
envisions
worked
on
and
unibrite
team
and
so
yeah,
so
that's
kind
of
been
our
journey
over
the
last
couple
months
been
positive.
If
there's
any
questions
before
I
jump
into
the
actual
into
the
actual
demo.
P
And
also
to
kind
of
just
keep
in
the
same
format
that
dan's
been
doing
I'll
fill
in
the
the
cookbook
ideation,
as
well
as
we're
walking
through
this
happy
to
answer
any
questions
at
all.
So
as
I'm
going
through
the
demo,
you
know
feel
free
to
stop
me
or
you
know,
kind
of
put
something
in
the
chat
and
I'll
I'll.
Take
a
look
at
that
as
we're
going
through
this
as
well.
P
There,
before
I
start
is
there
anyone
specifically
on
the
call
that
has
worked
in
the
salesforce
ecosystem
or
is
currently
using
salesforce
today
and
has
come
to
kind
of
explore
some
of
the
ways
that
we're
doing
this.
P
Okay,
got
it
got
it
yep,
so
we'll
show
classic
and
lightning.
Today
I
will
show
kind
of
a
record
being
locked,
that's
been
baselined
in
classic
and
we
can
show
lightning
as
well.
P
Right,
okay,
so
the
first
thing
I'll
do
we'll
kick
it
off.
So
the
first
thing
we'll
do
is
we'll
talk
about
the
manage
package
and
how
to
essentially
install
this
in
your
salesforce
environment
and
dap.
Suite
is
available
on
the
sales
for
up
exchange.
We
just
released
the
new
version
with
the
baseline
functionality
a
couple
days
ago,
and
so
this
is
now
available
on
the
app
exchange.
First
thing
you
can
do,
is
you
install
the
app
and
we
have
what
you
call
the
connected
app?
P
P
You
know
you
can
even
take
a
look
at
the
middleware.
If
you
want
it
is
available
on
github
as
an
open
source
repo
that
has
some
of
the
baseline.
You
know
kind
of
rpc
methods
that
we've
been
looking
at
and
also
some
of
the
implementation
we've
done
with
the
provide
team.
P
So
if
you
want
to
take
a
look
at
the
middleware,
you
can
also
host
it
yourself
locally
or
on
heroku
or
whatever
platform
you
want.
We
have
a
managed
version
ourselves
that
runs
at
dapsuite.network
and
this
is
kind
of
our
managed
version
that
you
get
out
of
the
box.
So
if
you
want
to
host
the
middleware
yourself,
you
can
do
that.
P
If
not,
you
can
also
just
leverage
the
managed
version
that
we
have
so
the
first
thing
I'll
look
at
today,
we'll
talk
about
three
different
ways
that
we're
talking
or
thinking
about
baselining
different
systems
of
record,
and
I
think
the
version
that
we've
done
with
salesforce
is
leveraging
kind
of
the
clicks.
Not
code
clicks,
not
code,
declarative
model,
which
I
think
a
lot
of
the
salesforce
ecosystem.
P
P
So
you
know
how
can
we
baseline
a
record
in
process
builder?
How
can
we
do
this
using
global
actions?
P
So
if
we
go
back
here,
we'll
see
we
have
like
a
global
action
which
again
you
don't
have
to
code
up.
You
know
a
ton
of
things
you
can
pretty
much
just
declaratively
select
which
work
group
you
want
to
create
and
also
what
contract
you
want
to
baseline
and
then
the
last
method
will
be
a
little
bit
more
kind
of
deeper
into
the
code
and
using
apex
sales
versus
kind
of
native.
You
know
run-of-the-mill
object,
oriented,
programming,
language
and
we'll
show
how
we
can
actually
do
baselining
using
apex
there.
P
All
right
looks
like
all
good,
I'm
checking
the
chat
and
that's
good
okay.
So
the
first
thing
we'll
do
is
we'll
take
that
we'll
take
a
look
at
how
we
actually
baseline
a
record
natively,
so
this
would
be
native
functionality
and
actually
using
just
a
checkbox
on
the
the
record
itself.
So
if
we
go
over
here,
this
is
the
standard
contract
record
and
what
we
can
do
is
we
can
say
we
have
a
new
contract.
P
P
P
If
we
go
into
our
process
builder,
we'll
see
here
baseline
contract
msa
process,
so
we
can
go
to
the
standard
contract
object
when
the
record's
created
or
edited.
If
that
baseline
field,
which
was
that
checkbox
that
says
baseline
record
is
equal
to
true,
then
we
want
to
do
two
immediate
actions
and
the
first
action
is
just
baselining
the
record,
and
so
this
is
an
invocable
method
that
we've
created
and
this
invokable
method
is
what's
actually
calling
out
to
to
our
middleware,
which
then
brokers
the
message
to
the
to
the
shield
contract.
P
So
this
is
interesting
in
that
you
don't
actually
have
to
go
through
and
code
this
out,
every
single
time
the
valuables
or
the
variables
that
are
part
of
this
will
be
kind
of
structured.
So
if
we
do
look
at
this,
let's
take
a
look
at
like
how
we
could
actually
edit
this
and
we
go
to
baseline
record.
You
can
add
rows
and,
if
you've
seen
the
radish
demo
before
we've
actually
just
taken
the
same
structure,
fields
that
are
part
of
the
radish
demo,
so
purchase
unit
purchase,
quantity,
purchase
price.
P
These
are
kind
of
all
of
your
the
fields,
and
then
you
can
actually
link
these
to
fields
that
are
part
of
the
standard
object.
So
you
can
look
at
the
contract
objects,
and
you
can
say
you
know
I
want
the
contract
id
to
be
pulled
in,
and
so
these
are
the
different
fields
that
you
can
actually
pull
into
this
call
out,
and
so
what
this
will
happen
will
basically
say:
okay,
once
this
record
is
the
checkbox
is
true.
P
We
want
to
make
this
call
out
to
to
the
middleware,
and
then
the
middleware
is
essentially
brokering
this,
as
the
json
object.
P
Questions
looks
good
here
on
chat
as
well.
Okay,
the
second
action
that
we
want
to
take
is
actually
locking
the
record.
So
this
is
another
piece
of
apex
called
the
locking
is
basically
a
piece
of
apex
that
actually
will
lock
the
record,
and
so
those
are
the
two
actions
that
we
want
to
take
the
first
one
is:
we
want
to
make
sure
that
we
do
the
call
out
to
the
middleware
so
that
it
hits
ethereum.
The
second
action
we
want
to
take
is
we
want
to
con
lock
the
contract
record
now.
P
The
important
thing
to
note
here
is,
if
you're
going
to
do
this
yourself.
There
is
a
setting
that
you
have
to
enable
which
is
right
here
this
in
process
automation,
settings
kind
of
in
your
salesforce
setup
in
order
to
lock
records,
but
via
apex.
So
in
the
use
case
that
we're
using
you
have
to
make
sure
this
checkbox
is
checked.
So
if
you're,
like
a
system
administrator-
and
you
did
want
to
use
apex
to
essentially
lock
the
record
after
it's
been
baselined,
this
is
the
correct
kind
of
way
to
do
that.
P
So
that
would
be
the
kind
of
the
first
iteration
that
we've
we've
seen
the
other
way
you
could
do.
This
is
via
platform
events,
and
so
you
can
either
do
in
this
instance
we're
just
saying
if
the
standard
contractor
edit
exchanger
contract
object
is
created
or
edited,
we
want
to
essentially
baseline
it
and
lock
the
record.
That's
the
standard
kind
of
way.
We've
done
this
on
a
single
object.
P
The
other
way
is
there's
a
feature
on
salesforce
called
platform
events
and
platform
events.
These
can
be
configured
and
kind
of
either
called
via
a
web
hook
called
via.
Really,
you
can
call
a
view
api
and
there's
this
platform
event
can
actually
also
can
actually
instantiate
this
same
sort
of
like
process
builder,
and
so
we
can
say
you
know,
conditions
based
on
the
platform
event
and
in
this
instance,
we're
actually
going
to
be
sending
out
the
same
structured
protocol
message.
P
That
is
part
of
the
baseline
reference
implementation
one,
and
so
you
can
see
here
it
has
the
op
code,
the
recipient,
the
shield
contract
id
identifier.
So
this
is
kind
of
your
structured
object,
instead
of
it
being
like
the
radish
object,
which
we
are
looking
at
here,
which
is
those
fields
that
we
saw
earlier.
I
like
purchase
quantity,
purchase
price.
You
can
actually
also
use
the
structured
apex
variables
that
are
part
of
or
the
structured
variables
that
are
part
of
the
baseline
reference
implementation.
P
And
if
we
look
at
this
here
in
the
protocol
message,
factory
you'll
see
these
are
the
exact
same.
You
know
op
codes
that
we
see
here
in
that
invocable
method
call
out
from
salesforce.
So
if
this
is
kind
of
your
structured
object
for
how
you
send
a
message
via
that
and
via
this
baseline
implementation,
this
is
our
way
of
calling
out
to
that
with
that
same
structure
data.
P
So
those
are
the
two
methods
we've
implemented
so
far
in
terms
of
kind
of
a
declarative
way
to
to
call
out-
and
I
would
say
this
is
probably
long
term-
something
that
we'll
put
more
time
into,
given
that
it's
going
to
be
using
the
reference
implementation
and
the
reference
kind
of
structured
object.
P
So
flow
is
another
iteration
kind
of
same
kind
of
process,
builder
type
of
integration,
but
you
can
do
the
same
exact
thing,
so
you
can
go
through,
create
an
action.
We
look
for
baseline.
P
You
can
do
that
same
thing
post.
You
know,
protocol
message
to
baseline
select
the
different
variables
that
you
would
like
and
then
in
a
kind
of
more
declarative
way.
These
all
come
as
part
of
the
managed
package.
You
can
then
select
to
include
these
or
not
in
your
flow
diagram.
So
let's
just
call
this
baseline
flow.
P
And
then
this
is
another
way
that
you
can
actually
kind
of
go
through
that
same
process.
If
you
don't
want
to
use
process
builder,
I,
like
I,
like
process
builder
better.
I
think
it's
a
little
bit
easier
to
set
up
than
flow,
but
either
of
these
work
and
can
leverage
the
call
outs
that
we've
put
in
the
manage
package
there
I'll
pause
there
for
a
second.
Are
there
any
questions
on
process
builder
flow,
the
invocable
methods,
anything
that
we've
covered
so
far.
P
So
one
of
the
things
that
we've
added
in
the
functionality
is
the
ability
to
actually
write
different
contracts
or
socrates
in
salesforce.
So
this
is
not
necessarily
on
the
process
side,
but
this
is
actually
more
like
on
our
on
just
the
core
platform
we've
built
out.
So
one
of
the
features
will
be
built
in
to
start
is
you
can
go
in
and
kind
of
just
create
and
compile
solidity
in
the
platform?
P
So
if
you
go
like
network
token
and
you
upload
a
contract-
let's
see
here
if
we
go
into
the
library
I'll,
just
pull
the
number
one
that
we
have
here.
P
P
You
can
go
and
you
can
actually
start
writing
your
own
socrates
circuits
or
if
you
have
someone
that
is
going
to
be
writing
those
you
could
write
those
and
save
them
here
in
salesforce,
so
the
compiler
right
now
is
looking
at
I'll
show
kind
of
briefly
how
this
works
so
compiles
a
contract
directly
in
here
and
we're
going
to
be
extending
this
to
essentially
call
out
to
the
socrates
js
library
that
will
also
be
part
of
our
middleware,
and
so,
as
we
compile
this
this
basically
will
it
takes
a
few
seconds
here:
it'll,
basically
spit
out
the
the
abi
code,
the
abi
and
the
byte
code,
specifically
for
this
contract.
P
Okay,
so
essentially,
this
is
yeah
it's.
This
is
the
the
output
of
it
would
be
your
byte
code
for
that
particular
contract
and
then
the
abi-
and
this
becomes
important
as
we
want
to
essentially
store
this
information.
We
can
then
leverage
it
later
in
the
smart
contract
interface,
and
this
interface
allows
us
to
essentially
deploy
contracts
that
have
been
saved
on
the
platform.
So
if
you
did
want
to
actually
deploy
the
workgroup
contracts
or
anything
from
this,
this
is
possible.
P
We're
not
actually
doing
that
we're
leveraging
the
provide
stack
to
kind
of
launch
all
the
required
underlying
infrastructure
in
order
to
baseline
your
instance,
but
just
to
kind
of
give
some
background.
This
is
also
something
that
we're
aiming
to
do
is
essentially
build
out
the
circuits
in
the
circuit
registry,
using
this
compiler,
where
you'll
be
able
to
compute
the
witness,
save
the
verifier
contract
and
then
actually
save
those
into
a
library
here
on
salesforce.
P
So
this
is
kind
of
more
roadmap
that
we're
getting
to,
but
it
is
something
that
I
wanted
to
bring
up
today
on
the
call
as
well.
P
Okay,
so
I
think
this
is
a
good
way
we
could
segue
into
kind
of
looking
more
at
the
code
of
what
we've
been
doing
so
at
first.
I
wanted
to
keep
it
more
on
the
declarative
side,
and
this
is
kind
of
the
flows
that
we've
set
up
in
process
builder.
You
know,
locking
the
different
records
and
then
the
last
thing
or
the
kind
of
looking
at
the
flip
side
of
this
is
what
about
like.
How
are
we
actually
making
these
call
outs?
P
So
if
we
look
at
the
baseline
record
and
we
go
in
and
we
set
different
variables,
you
know
these
have
to
come
from
somewhere
right.
So
where
is
that
actually
being
set?
P
So
if
we
go
into
the
middleware,
we
can
see
here,
there's
a
baseline
protocol
message
call
out,
so
this
invocable
method
is
actually
taking
like
the
structured
object
that
we
talked
about
and
it
takes
it
in
a
wrapper
and
essentially
is
making
a
call
out
to
the
middleware,
and
then
it
says:
here's
the
route
which
is
dispatch,
protocol
message
and
so
we're
looking
at
this
as
how
can
we
take
in
these
different
variables
from
salesforce
and
then
make
a
post
a
call
out
or
http
callout
from
salesforce
in
a
declarative
way
from
processbuilder
using
this
method.
P
So
one
thing
you
know
kind
of
going
back
to
how
this
got
started,
so
we,
you
know,
filed
this
integration
on
the
zen
hub,
but
pretty
much.
This
is
back
in
june
and
so
over
the
last
couple
of
months.
This
is
essentially
our
first
integration
or
implementation
on
salesforce,
like
I
said,
this
is
implemented
on
the
salesforce
app
exchange
as
well,
and
the
idea
really
that
we
want
to
get
across
is
that
we
can
leverage
out
of
the
box
today.
P
A
lot
of
the
salesforce
functionality,
like
process
builder,
like
flow
to
essentially
synchronize
your
system
of
record
in
standard
objects
without
having
to
set
up
a
separate
network.
You
know
you
can
leverage
ethereum
as
it's
kind
of
always
on
it's
neutral.
You
don't
necessarily
have
to
set
up
the
underlying
infrastructure.
P
You
can
just
kind
of
keep
your
existing
system
a
record
leverage
standard
functionality
within
that
system
for
record,
like
process
builder,
like
flow
like
approvals
to
lock
records
and
from
doing
in
doing
so,
you
can
actually
synchronize
these
different
systems
in
a
fairly
effective
way
and
it
costs.
P
Without
you
know,
spending
months
and
months
in
etls
spending
months.
You
know
trying
to
connect
the
dots
between
one
system
and
another,
so
we
see
it
as
a
massive
advancement
in
using
kind
of
public
blockchains
to
synchronize.
These
different
systems
of
record,
which
we've
heard
from
customers
for
a
while,
is
a
major
pain
point
for
them.
P
Okay,
so
is
there
any
questions
I
can
cover?
I
know
you
know
been
talking
for
a
few
minutes
here.
Daniel
kyle.
Do
you
guys
want
to
add
anything
in
in
terms
of
kind
of
or
anything
like
you
want
to
cover
as
well?
P
P
So,
okay,
so
what
I'd
like
to
do
now?
I
can
pull
up
a
few
decides
on
what
we
covered
and
then,
lastly,
we'll
go
into
kind
of
what's
on
our
roadmap
in
terms
of
baselining
and
on
salesforce.
So
let
me
pull
up.
M
P
Okay,
so
again,
this
is
what
we
covered.
You
can
baseline
salesforce
today
using
process
builder
in
a
clix,
not
code
configuration
this
can
work
on
standard
or
custom
objects
and
in
our
use
case
we
have
conditional
logic
which
is
basically
based
on
just
that
checkbox.
So
it
can
be
any
kind
of
field
that
you
want
and
then
the
lock
method
is
also
using
baseline,
but
you
do
need
to
enable
that
kind
of
in
the
system
admin
settings
if
you
want
to
be
able
to
lock
records
using
apex.
P
So
those
are
this
is
on
the
process
builder.
I
would
say
one
of
the
easier
ways
to
to
start
baselining.
The
second
thing
we
looked
at
is
the
global
action,
and
so
this
baseline
new
record
this
actually
deploys
the
workgroup
contract.
We
didn't
show
this
on
today's
demo,
but
this
deployment
we
showed
this
on
the
office
hours.
This
essentially
calls
out
to
a
method
that
deploys
the
shuttle
contracts,
so
you
can
instantiate
who's
the
the
name.
P
What's
the
work
group
name
and
then
eventually,
you
can
send
out
these
contracts
directly
to
the
ord,
regular
sheet
contracts
to
the
network
from
sales
source
and
that's
leveraging
the
provide
stack
and
then,
lastly,
we
looked
at
the
civility
compiler
in
the
zocrates
compiler
and
again
this
is
we
want
to
get
to
the
socrates
circuit
library
in
the
future,
but
for
now
it's
pretty
much
just
it's
compiling
solidity,
but
we
could
see
in
the
future.
P
As
you
know,
zero
knowledge
proof
become
more
and
more
mainstream,
especially
given
that's
a
core
component
of
the
baseline
protocol
that
systems
admins
users
salesforce
developers
eventually
could
be
writing
these.
You
know
maybe
in
saving
those
directly
on
salesforce,
it
might
be
a
little
early
for
up,
but
in
the
future
you
know
that
could
be.
You
know
something
that
these
system
developers
are
or
salesforce
developers
could
be
doing
using
dot
suite
right.
P
This
is
on
custom
settings,
and
I
have
mentioned
this
on
the
office
hours
a
few
weeks
ago
as
well,
which
is
how
are
we
managing
a
lot
of
the
secrets
for
this
baseline
protocol
like
how
are
we
making
sure
that
these
callouts
are
proper?
So
this
is
something
else
that
I
think
from
a
like
product.
Cookbook's
perspective
is
super
important
and
so
there's
a
feature
that
salesforce
has
and
I'm
sure,
there's
other
kind
of
ways
that
sap
or
dynamics
or
other
company
or
other
platforms
do.
This
is
manage
kind
of
protected
thing.
P
You
know
protected
api
settings
protected.
You
know
really
anything
that
you
need
to
be
secret,
but
also
you
can
update
as
an
application
provider
as
an
isv.
So
if
you
wanted
to,
you
know
store,
for
example,
like
your
infuriate
settings,
your
baseline
settings,
one
thing
that
we
use
is
called
protected,
custom
metadata
types,
and
this
is
a
very
standard.
You
know
kind
of
best
practice
for
sales,
protecting
data
within
the
salesforce
platform.
P
So
one
thing
that
we
can
see
here
that
we've
been
implementing
is
kind
of
baseline
settings
and
this
could
be
for
setting
if
you
did
want
to
have
your
workgroup
in
org
and
vault
actually
configured
inside
of
your
sales
restore
you
can
use
custom
metadata
types
to
essentially
set
those
variables
in
the
same
manner.
P
We
also
are
leveraging
this
to
manage
our
inferior
settings,
so
you
can
see
here
that
if
you
want
to
set
up
how
you're
you're
calling
up
to
mainnet
or
robston
or
your
actual
url,
this
is
basically
how
we're
configuring
our
custom
metadata
types
to
to
essentially
set
up.
Here's
where
our
inferior
endpoints
are
right
so
and
even
if
you
have
api
keys
to
call
inferior,
they
could
also
be
you
know,
set
up
here
in
custom
metadata
types.
P
So
when
we're
setting
up
baseline,
this
is
a
you
know,
kind
of
an
important
part
of
something
that
we
had
to
do.
It's
not
you
know
the
ux
side,
but
it's
definitely
something
from
a
cookbook's
perspective
is
how
are
you
going
to
be
able
to
store
secrets?
You
know
kind
of
natively
on
the
platform.
Custom
edited
types
is
a
really
good
way
on
the
sales
source
side,
and
then
you
can
query
these.
You
know
on
in
apex
to
essentially
pass
these
secrets
along
with
http
callouts
or
anything
along
those
lines.
P
You
also
use
it's
some
properties
or
custom
settings.
I
think
custom
metadata
types
is
like
the
preferred
way,
but
custom
settings
also
works,
and
this
is
for
other.
G
P
Have
other
settings
as
well
for
key
settings?
Node
settings,
I
would
say
the
preferred
way,
or
the
kind
of
the
way
that
the
salesforce,
I
would
say
recommends
is
using
custom
metadata
types
to
do
all
secret
management,
whether
using
it
for
blockchain
or
not.
So
this
is
something
else
that
we
want
to
make
sure
that
our
users
know
says
it's:
how
we're
protecting
everything
from
a
security
standpoint
from
a
record,
locking
standpoint,
I
think
we
covered
that
earlier.
The
different
ways.
P
So
one
of
the
things
that
we
also
did
here
so
we
filed
this
back
in
it
was
like
I
said
it
was
in
june,
and
the
initial
thing
that
we
focused
on
was
basically
how
we're
going
to
extend
salesforce
to
use
baseline,
and
you
know
over
the
last
couple
months
we
we
basically
this
is
the
the
result
of
it
was.
You
know
I
just
composed
this
pretty
recently,
but
it's
now
available
on
app
exchange.
P
One
of
the
other
things
we're
looking
at
doing
is:
how
do
we
kind
of
do
this
inter-company
kind
of
transactions
and
in
a
way,
use
different
messaging
protocols
to
do
so,
and
so
I'll
show
here
just
another
kind
of
example,
of
what
we're
seeing
in
terms
of
this
is
different
companies,
but
also
leveraging
you
know
all
within
one
salesforce
system
or
record,
but
on
different
instances.
So
I
think
to
earlier
questions
like.
Could
this
be
used
for
other
things
absolutely
or
between
different
companies,
but
even
a
single
company?
P
And
we
send
a
po
out,
and
so
the
pl
get
sent
out
we'll
see
in
the
first
one
here
at
the
bottom,
it'll
show
a
new
po
and
request,
and
so
what
we're
looking
at
doing
is
we
can
leverage
this
so
see.
Here's
the
new
order.
If
we
go
into
the
other
orgs
we'll
see
that
this
is
complete
currently
is.
P
Can
we
actually
call
out
to
baseline
in
between
these
different
flows,
and
so
this
actually
isn't
using
that
this
is
actually
using
the
quarta
flows,
and
so
what
we're
looking
at
doing
is.
Could
we
essentially
take
this
same
sort
of
process
and
save
the
record
of
these
state
changes
directly
using
the
mainnet
and
so
as
we're
going
through
here
and
we're
synchronizing,
these
different
salesforce
orgs?
P
Could
we
actually
go
through
and
each
state
chains
call
out
to
the
ethereum
network?
So
what
I'll
show
here?
This
is
another
one
of
the
things
that
we're
working
on,
doing,
which
is
essentially
going
here
to
our
next
thing,
which
would
basically
be
you
know,
kind
of
a
quarter.
Baseline
integration
is
essentially
sending
the
output
of
the
flow
transaction
between
different
orgs
to
the
baseline
to
the
ethereum
mainnet
and
basically
just
keep
track
of
each
state
change
directly
from
from
the
full
framework
as
well.
P
So
this
is
something
else
we're
working
on
it
kind
of
in
that
same
on
salesforce
how
we
could
effectively
use
the
flow
framework,
but
also
make
sure
that
each
one
of
those
iterations
is
completely
locked,
is
complete
and
is
posted
to
the
baseline.
So
this
is
again
kind
of
roadmap,
of
what
we're
gonna
get
to
eventually,
but
also
on
the
salesforce
platform.
You
know
we're
looking
at
how
we
can
synchronize
and
make
sure
that
all
state
changes
are.
You
know
directly
integrated
with
each
other
between
different
counterparties.
P
Is
there
any
any
questions
so
far
on
on
the
last
and
last
couple
components
of
the
demo.
O
Yeah,
no,
I
mean
it
was
one
of
those
where
you
know
I
was
product
director,
basically
kind
of
the
at
that
intersection
between
the
business
and
technical
domains,
and
we
did
a
lot
within
salesforce
just
so.
I
could
gain
a
lot
of
my
intel
as
far
as
what
we
were
working
on,
and
this
was
I
was
involved
basically
when
we
were
doing
the
migration
from
platform
to
lightning.
I
O
Yep,
it's
it's
basically
been
my
experience
that
no
one
gets
rid
of
salesforce,
really
they,
basically
they
come
in
they're,
so
used
to
using
it
and
stuff.
You
know
some
people
may
have
some
complaints
about
it
as
far
as
you
know,
user
experience
or
whatever,
but
they
get
over
that
pretty
quickly.
It's
not
enough
that
you
know
where
they
say.
You
know
we're
getting
rid
of
salesforce
and
we're
gonna
we're
gonna
go
to
pega
or
anything
like
that.
O
P
Yeah
there's
a
mass
margin.
I
think
salesforce
is
up
to
150
or
200
000
customers
globally,
and
then
you
know
millions
of
developers.
So
I
think
when
we
originally
created
like
the
dap
suite
package,
it
was.
The
idea
was
basically
that
we
could
bring
a
lot
of
the
ethereum
development
to
those
salesforce
developers
and
administrators,
and
I
think
this
is
kind
of
an
extension.
Of
that
same
thing
is
how
do
we
leverage
baseline
protocol,
bring
baseline
protocol
to
the
salesforce
ecosystem,
but
in
a
way
where
it's
lit,
it's
leveraging
the
native
functionality?
P
It's
not
going
to
be
super
super
complex,
zero
knowledge
proves
it
should
just
be
the
same
kind
of
declarative
clicks,
not
code.
You
know,
platform
that
a
lot
of
salesforce
admins
are
used
to.
So
I
think
that's
what
you
know
what
we
really
want
to
go
for.
O
And
I
know
salesforce
you
know
was
working
on
their
own
internal
blockchain.
You
know
they
had
their
own
internal
blockchain
implementation
that
they
had
built
on
sawtooth.
I
believe
it
was,
and
I
haven't
really
paid
much
attention
you
know
probably
within
the
past.
I
want
to
say
eight
months
probably,
but
I
think
they're
probably
come
to
the
realization
that
you
know
the
private.
The
private
network
is
not
the
way
to
go.
O
P
Yeah,
I
think
yeah
I
I
agree.
I
think
baseline
has
solved
one
of
the
major
one
of
the
major
thing
it
solves
is
kind
of
the
neutral,
having
kind
of
a
new
trap
neutral
component
of
it,
and
to
the
question
of
like
do,
I
I
think
daniel
was
saying
earlier.
Do
I
have
to
join
this
network?
Do
I
have
to
join
this
blockchain
network
or
how
are
this
going
to
work?
P
I
think
that
baseline
kind
of
from
just
a
general
adoption
standpoint,
if
you
can,
you
know,
take
for
the
first
premise
that
the
data
and
processes
will
be
private.
The
second
really
important
thing
is
that
it's
neutral
versus
some
of
the
setup
required.
P
Where
are
things
hosted
for
if
you're
gonna
run
like
a
private
chain,
where
things
hosted?
Who
actually
has
the
like
system
admin
capabilities
over
it?
Is
it
one
single
massive
company
that
has
a
kind
of
a
number
of
other
subsidiaries
that
are
trying
to
join
the
network?
I
think
baseline
handles
that
very
well,
given
that
ethereum
is,
for
the
most
part,
really
is
usual.
O
Yeah
the
way
I
put
it
it
doesn't,
it
doesn't
move
around
the
furniture
right.
It
basically
just
keeps
everything
where
it
was
before
and
that's
that
sidesteps.
So
many
you
know
cultural.
You
know
things
that
you
have
to
navigate.
You
know
not
only
on
the
business
side
but
also
the
technical
side.
Basically
saying
hey,
we
are
actually
you
know
showing
where
you
know
everything
can
prove
where
they
are
synced
up
so
cycle
times.
O
Go
from
you
know
from
you
know,
weeks
or
months
I
mean
to
to
seconds
or
minutes
I
mean
it,
it
moves
it
moves
the
needle
so
far
so
quickly.
Yep,
I
mean
it's
common.
You
know,
because
I
I
I
really
got
into
blockchain,
where
you
know
on
the
foundation
layer
to
where
everyone
was
going
about
it
at
the
approach
where
we
are
going
to
completely
rework
the
entire
it
infrastructure
for
a
private
blockchain
network,
and
you
know
I
was
probably
eight
or
nine
months
into
it
and
I
started
to
realize
some.
N
O
You
know
so
you
know
trying
to
use
blockchain
as
the
entire
backend
database
is
just.
I
mean
it's
first
of
all,
it's
it's
it's
it's
nuts
and
it's
it's
way
too
too
expensive,
and
you
know
it's
it's
one
of
those.
As
with
any
emerging
technology,
it's
got
to
demonstrate
that
it
can
outperform
the
current
technology
and
do
so
cost
effectively,
and
so
you
know.
I
O
T
B
Yeah
so
so
kind
of
on
that
topic.
What
are
you
going
to
use
it
for
so
so,
let's
kind
of
have
a
little
bit
of
ideation
session.
Are
you
are
you
I
might
have?
I
might
have
interrupted
your
flow
dom,
though
no.
P
B
Man,
that's
that's
such
a
such
a
cool
presentation
and
you
know
salesforce
is
just
such
a
force
to
be
reckoned
with
regarding
systems
that
you
know
are
being
used.
Let
me
put
my
my
video
back
on
here.
You
know,
you
know
it's
it's!
It's
such
a
powerful
system
of
record
that
small
companies
use
large
companies
use.
I
remember
back
when
I
used
to
work
at
windham.
I
was
part
of
the
rollout
of
salesforce
to
to
our
to
our
to
our
team,
which,
which
kind
of
brings
up
the
question
right.
B
So
would
we
use
salesforce
back
when
I
was
working
at
windham
worldwide?
They
had
so
so
they
had
actually
hired
me
specifically
because
they
had
acquired
14
satellite
offices
across
the
country.
There
was
no.
There
was
no
management
of
these
new
offices
that
were
acquired
essentially,
so
they
needed
some
sales
management
and
support,
and
things
like
that,
so
they
had
no
way
to
keep
their
records.
You
know
up-to-date
easily
accessible
from
everyone
in
the
organization
up
and
down.
B
So
that's
what
they
were
using
salesforce
for,
and
it
was
also
used
within
the
context
of
vacation
rental
property
management.
All
right.
So
almost
like
air,
airbnb
and
vrbo
were
our
competitors
at
the
time.
That's
that's
what
we
were
doing
so
I
worked
for
wyndham
vacation,
rentals,
north
america.
That
was,
that
was
the
business
unit
from
wyndham
worldwide.
B
What
interesting
use
cases
have
you
seen?
Salesforce
be
applied
for.
P
Yeah,
I
think
middle
office
processes
like
pos
contracts,
proposals,
you
know
sending
rfps
out
to
multiple
suppliers
and
then
getting
back
that,
at
least
from
the
baseline
perspective,
proof
that
these
multiple
rfps
were
in
fact
the
same
rfp
sent
out
to
each
supplier.
I
think
that
was
use
case
john
and
I
spoke
about
originally.
We
were
showing
talking
about
this,
I'm
I'm
bullish
on
the
middle
office
component
of
it
and
there
is
a
massive
ecosystem
on
salesforce
already
a
middle
office.
B
Do
you
explain
that
actually,
the
middle,
the
middle.
P
Office,
can
you
go
through
that
yeah?
So
if
you
have
your
front
office
right
is
like
your
accounts.
Contacts
leads
pretty
much
everything
up
to
an
opportunity
and
you
have
your
back
office
would
be
right
like
ar
ap.
You
know
invoice
payments,
all
that
middle
office
is
all
of
the
actual
revenue
driving
processes
that
today
are
fairly.
You
know,
fairly
standardized
within
one
company
at
larger
companies
right
like
creating
quotes,
making
sure
that
you
have
pricing,
rules
done
contracts
or
contract
based
pricing.
P
You
have
multiple
suppliers,
you
know
actually
generating
an
order
or
an
input.
So
those
like
four
or
five
middle
office
processes
can
kind
of
be
broken
down
on
salesforce.
P
In
terms
of
you
know,
they
have
cpq
companies,
they
have
which
do
configuration,
they
have
contract
management
companies
and
then
even
more
so
focus
on
like
order
management,
I
think
that
baseline
could
be
applied
to
that
those
middle
office
processes
specifically
on
salesforce
and
I
think,
prior
to
baseline.
P
You
know,
I
think,
a
key
part
where
baseline
could
be
applied,
at
least
within
the
salesforce
ecosystem.
Interesting.
B
So
so,
with
regards
to
the
middle
office-
and
I
know
that
you
quickly
fired
off
a
couple
of
them-
you
know
I'm
just
I'm
just
kind
of
thinking
through
and
now
I'm
going
into
our
tab
over
there
into
the
cookbook
ideation
tab
and
I
wrote
down
middle
office,
but
now
I'm
starting
to
think
that
middle,
maybe
middle
office
is
a
little
too
generic
of
a
use
case.
Right
so
can
you
can
you
help
us
with
being
a
little
bit
more
defined
as
to
which
use
case
within
the
middle
office
process?.
P
I
would
say
like
just
standard
if
we
just
looked
at
the
standard
contract
object
in
salesforce
or
the
standard
order
object,
if
we
just
kept
it
to
those
standard,
if
we're
able
to
synchronize
a
standard
contract,
object
between
one
org
to
another
sales
source,
org
or
one
or
two,
an
sap
or
one
or
two
dynamics,
and
ensure
that
these
two
records
are
completely
synchronized,
ensure
that
these
two
order
records
completely
synchronize,
whether
that's
an
rfp,
whether
that's
you
know
an
msa
that
has
specific
pricing
tied
to
it.
P
P
I
think,
drilling
down
kind
of
into
what
we've
showed
is
just.
How
do
we
do
the
standard
object?
So
I
think
from
that
there's
a
lot
more
details,
but
you
know
like
our
use.
Csa
was
just
on
the
standard
contract
object,
but
this
can
be
applied
anywhere
really
and
on
salesforce.
Any
standard
or
custom
object.
B
Yeah
and
like
you
know
the
business
apps
that
the
business
apps
that
we're
showcasing
and
how
we
turn
them
into
baseline
apps
right,
it's
like
dynamics
started
very
similarly,
where,
where
dynamics
big
thing
was
the
crm
and
that's
kind
of
what
salesforce
was
at
the
beginning,
they
were
you
know,
a
very
popular,
very
configurable
crm,
which
gave
way
for
more
for
more
right.
I
mean
people
want
to
use
their
their
applications.
That
already
has
these
entities.
B
If
you
will
like
contacts
and
accounts
and
leads-
and
things
like
that,
and
now
we
have
a
need
to
be
able
to
kind
of
expand
and
explore
different
business
processes
and
in
the
context
of
baselining.
You
know
we
had
this
conversation
a
little
bit
earlier,
where
we
went
through
a
really
quick
identification
process
of
where
your
counterparties
are-
and
you
know,
business
apps
like
salesforce
just
like
dynamics
gives
you
that
highly
configurable
environment
to
meet
these
use
cases
right.
C
P
I
think
the
combination
of
retaining
the
system
of
record
leveraging
native
functionality
and
then
calling
out
to
like
a
neutral,
you
know
kind
of
neutral
like
bulletin
board
right,
you
know,
zom,
I
think
john
pledges.
You
know
that
combination
seems
to
be.
You
know
that
what
will
take
you
know
kind
of
get
the
most
adoption
in
the
near
term,
because
it
does
address
a
lot
of
the
issues
that
companies
face
today
when
they're
exploring
blockchain
and
to
the
point
around
contracts
as
well.
I
think
I
can
pull
up
something
too.
P
This
is
something
that
we've
been
working
on
and
we
still
need
to
kind
of
finalize
this
in
our
next,
the
next
version,
but
even
doing
integrations
like
we're
thinking
down
the
road.
We
could
do
things
with
like
open
law
and
and
use
kind
of
the
open
law
framework
and
markup
language
that
their
specific
dsl
and
then
somehow
tie
that
together
with
baseline.
You
know
we
just
this
is
again
this
kind
of
next.
P
Our
next
release
will
have
this,
but
we
could
do
something
like
that,
where
you're
using
open
law
for
like
the
dsl
language
to
include
city
and
then
using
baseline,
plus
this
to
kind
of
create
a
more
a
little
bit
more
auto
executing
environment
around
middle
office
and
in
a
secure
and
privacy
preserving
way
which
a
lot
you
know
a
lot
of
these
companies
need
to
have.
B
Yes,
I
mean,
with
that
in
mind,
as
part
of
our
ideation
goal
out
of
this
cookbook
breakout
one
session.
What
I
just
did
based
on
what
you
just
said,
I
mean
line
number
29
over
here.
You
know
contract
services.
You
know,
I
think
that
contract
services
is
something
that
really
lends
itself.
I
mean
I'm
using
contract
services,
it's
probably
the
wrong
verbiage,
but
something
to
do
with
contracts
right.
It
really
lends
itself
to
two
parties.
B
P
Even
I
did
a
contract
in
the
contract.
Lifecycle
is
another.
I
mean
massive
market
within
salesforce
right,
so
even
contract
lifecycle
management
could
benefit
from
you
know.
Having
you
know,
a
zero
knowledge
proof,
you
know
verify
every
state
change
which
today,
I
think
you
know
a
lot
of
it's
done.
You
know
using
kind
of
standard.
You
can
use
standard
apex.
You
can
use
a
different
like
workflow
or
process
builder
type.
You
know
rule
engines
on
salesforce,
but
I
think
the
zero
knowledge
proof
aspect
to
it
really
does
add.
P
B
That's
in
this
room,
stefan
schmidt
is
from
unibright,
is
going
to
be
joining
in
about
15
or
so
minutes
he's
going
to
be,
you
know,
just
just
just
like
I
went
through
what's
going
on
in
d365,
dom
went
through
what's
going
on
with
salesforce,
stefan
is
going
to
go
through
what's
going
on
with
sap,
so
I
think
that's
going
to
be
cool
to
see,
but
you
know
just
kind
of
taking
a
step
back
and
looking
holistically
what
we've
been
doing
within
this
cookbook.
B
It
makes
things
easier
from
an
isv
perspective
to
selling
it
to
an
enterprise
company
and
the
reason
I
say
that
is
because
you
know
just
like
just
like
we've
been
saying
this,
you
know
dom.
I
heard
you
say
this
many
times
in
your
presentation
and-
and
I
say
this
until
I'm
just
blue
in
the
face-
it's
like-
we
don't
want
to
replace
the
system
right.
A
company
is
using
salesforce,
they
love
salesforce.
B
Large
companies
have
to
go
through
so
many
security
checks
from
penetration
testing
and
disaster
recovery
plans,
and
so
on
and
so
forth.
Where
you
know,
compliance
is
already
verified.
It's
it's.
It's
already
like
it's
done
with
salesforce.
B
If
a
company
is
already
using
salesforce
and
same
thing
with
dynamics,
same
thing
with
sap
same
thing
with
anything:
that's
like
azure
based
or
aws,
based
or
google
cloud,
it's
like.
B
P
And
I
think
there's
a
second
guys.
The
native
functionality
does
allow
for
a
lot
of
things
that
you
would
have
to
build
custom
outside
of
kind
of
a
course
system
or
record.
I
think
one
of
the
things
like
john
mentioned
after
the
blast
based
on
call
was
like
just
locking
records
could
be
somewhat
complex
down
the
field
level
if
and
you,
but
you
know,
salesforce
makes
it
fairly
easy.
P
P
You
can
go
in
make
all
of
these
records
read
only
right
and
then
basically,
you
know
just
set
up
a
quick
workflow
rule
so
that,
if
you
know,
if
is
equal
to
true,
not
only
do
we
want
to
rock
lock
the
record,
but
we
also
want
to
assign
this
new
baseline
layout,
which
is
basically
to
say,
baseline
record,
equals
true
we're
going
to
change
the
record
type
to
baseline
and
from
there
I
mean
this
is
all
standard.
P
You
know,
wait
for
the
next
work
step
in
the
baseline
flow,
so
it's
it's
a
using
the
standard
functionality
of
a
platform
like
salesforce.
You
can
do
a
lot
of
this,
but
at
the
same
time
not
you
know,
zero
knowledge
groups
aren't
native
to
salesforce,
so
you
still
need
to
kind
of
do
that
call
out
and
that's
where
you
know
what
we
build
is
it
comes
in,
but
you
know
you
know
best
of
both
worlds
for
a
lot
of
these
processes.
B
And
you
know
from
just
kind
of
taking
a
step
back
and
just
thinking
through
some
of
the
some
of
the
conversations
that
we've
had
from
the
onset
of
baseline
to
to
kind
of
now,
and
some
of
the
talks
that
we've
had
with
partners
and
customers
alike.
B
We
still
have
an
issue
and
that
aligns
with
standards
and
and
part
of
the
standards.
Is
you
know
it's
like
I'm
kind
of
retracting
a
little
bit
of
what
I
just
said
kind
of
like
it
makes
it
easy
for
us
that
you're
still
using
your
salesforce
system,
you're
using
what's
native,
or
are
you
still
using
your
dynamic
system
or
your
sap
or
after
this
session?
B
B
But
it's
not,
and
what
I
mean
by
that
is,
you
know
just
just
just
kind
of
telling
a
story
where
we
were
talking
with
a
fairly
large
government
contracting
organization
honestly
about
a
month
or
so
ago,
and
they
really
like
the
concept
right
and
and
they're,
obviously
looking
at
ways
to
leverage
blockchain
like
most
companies
that
are
building
things
with
their
technology
or
whatever
they're
looking
for
advancement
and
modernization
initiatives,
one
of
the
things
that
is
coming
up.
B
That's
an
issue
is
around
like
nist
compliance
and
part
of
the
issue.
Why
blockchain
as
a
whole?
Well,
let's
just
say,
ethereum
right-
why?
Why
ethereum
isn't
this
compliant?
It's
because
of
this
elliptic
curve
now
granted,
there's
some
work
being
done
literally
right
now
within
the
core
interfaces
with
the
zk
circuit
improvements
session.
But
that's
not
necessarily
the
point
of
that
right.
The
point
is
that
you
know
they're
there.
B
There
still
needs
to
be
considerations
around
what
components
we
can
put
into
this
baseline
stack
as
part
of
our
cookbook
to
make
it
compliant.
You
know
so,
for
example,
if
there
is
some
elliptic
curves
that
doesn't
work
with
ethereum,
for
example,
I
believe
it's
the
kicack
one
right.
The
keycap
curve
isn't
compliant
together,
like
it's
just
literally
just
not
on
the
nist
list
right.
B
If
it
was
on
this
list,
we'd
be
fine
and
when
you
think
about
it,
it's
like,
if,
if
if,
if
it
hits
that
compliant
level,
then
like
everything
else,
will
be
fine,
but
we're
missing
out
on
that.
But
there's
things
that
we
could
do
because
of
the
modular
nature
of
the
baseline
protocol
and
the
ability
to
have
these
different
microservices
like
what
provide
was
showing
right.
It's
like
you,
can
mix
and
match
different
components
of
what
you
need.
B
B
And
I
mean
that's:
that's
like
like
just
just
kind
of
talking
about
that
for
a
second
and
taking
a
little
bit
of
you
know
a
side
glance
at
it
on
one
way
it
is
compliant,
because
what
we're
doing
is
we're
not
doing
anything
on
chain
when
you
think
about
it
right,
it's,
like
all
of
the
processing,
happens
off
chain
all
the
encryption
with
the
zero
knowledge
proof,
that's
all
off
chain.
B
The
only
thing
that's
on
chain
is
the
verifier
key,
the
vk
key
right.
So
I
feel
with
regards
to
the
nist
compliant
we're
like
almost
there,
but
we're
not
quite
there,
but
we
have
the
ability
to
get
there,
and
I-
and
I
think
that
that's
that's-
that's
a
really,
really
important
thing
to
note
right.
It's
like
we
use
these
systems,
but
we
still
need
to
have
a
modular
methodology
that
allows
for
this.
P
Yeah,
I
think
it's
a
good
segue
to
some
of
the
kind
of
modular
like
with
provide
too.
I
know
we
talked
about
the
beginning
of
the
call,
but
you
know
we're
we're
happy
that
we're
partnering
with
provide
on
all
the
infrastructure
for
this,
because
you
know
we
can
focus
on
the
salesforce
side,
and
you
know
at
the
hub
kind
of
it
was
like
a
hub
and
spoke
model
like
envisions
like
that
spoke
with
dynamics.
Were
you
know
we
built?
P
The
first
spoke
with
salesforce,
and
so
I
think
provide
has
done
a
really
great
job
and
it's
been
work.
You
know
good
working
with
kyle
on
how
we
can
accelerate
all
this
development,
and
you
know
we
don't
have
to
do
everything
from
scratch.
You
know
every
time
we
you
know
we're
we're
focused
on
the
salesforce
side
we
can
partner
with
provide
to
to
accelerate.
You
know
general
adoption
and
join
customers
for
using
this
technology,
so
I
think
around
standards.
P
It
really
helps
and
just
around
like
making
sure
that,
if
we're
using
the
same
underlying
stack,
then
you
know
even
the
dynamics.
The
salesforce
demo
that
we
talked
about
should
be
doable.
You
know
fairly
fairly
soon
so
yeah,
it's.
I
think
it's
another
really
important
part
about
the
standards
and
you
know
how
we're
using
provide
together
as
well.
I
P
Was
a
follow-up
because
I
know
yeah,
stefan
and
you
guys
did
the
first.
That
was
actually
the
first
kind
of
reason
why
I
reached
out
to
john
and
the
team
was
kind
of
seeing
after
what
you
guys
have
done.
P
So
it's
been
interesting
to
see,
kind
of
and
learn
more
go
down
the
baseline
rabbit
hole
and
see
now
that,
like
there's
other
systems
of
record
that
we'll
be
joining,
I
think
in
the
next
couple
quarters
so
it'll
be
interesting
to
see
where
we
are
a
year
from
now
in
terms
of
what
people
are
doing.
B
What
a
great
question
so
so
we
have
stefan
who's
going
to
be
joining.
I
know
that
he
sent
me
a
message
he's
he.
He
was
just
in
another
another
session
right
now
and
then
he's
gonna
be
making
his
way
over.
But
what
a
good
question
dom,
if
I
can
ask
if
I
can
ask
the
crew
right
here,
where
would
you
like
to
see
baseline
be
one
year
from
now
one
year,
I'm
gonna
what
a
what
a?
What
a
thought
provoking
topic
I'll.
J
J
J
So
if
I'm
like,
I
said
if
I'm
using
ey's,
wonderful
ops
chain,
network
procurement
product
and
I
need
to
do
an
rfp
or
procurement
process
with
somebody
else-
that's
running
you
know
sap
or
even
quickbooks
for
crying
out
loud.
It
would
be
great
if
you
know
I
could
just
go
to
the
phone
book
find
them.
J
You
know
make
the
handshake
agree,
what
information
we're
going
to
be
sharing,
and
then
it
just
works
right
that
you
know
it
would
create
network
effects
kind
of
more
broadly
less
around
an
individual
application
and
more
around
kind
of
a
business
process
in
the
interaction
of
that
anyway,
that's
just
my
holy
grail
get
on
it.
Dan.
B
Who
else
who
else
wants
to
take
a
stab
at
this?
I
I
I
want
to.
I
want
to
go
through
this
exercise
because,
where
we
are
now
is
where
we
are
now,
but
if
we
don't
know
where
we
want
to
go,
how
can
we
get
there?
B
O
I
I
basically
would
sit
there
and
say
right
now
that
baseline,
you
know
we
are
going
for
the
low
hanging
fruit,
which
is
you
know,
a
lot
of
network
procurement
supply
chain,
but
there
are
other
industries
that
really
could
benefit
greatly
from
baseline
protocol,
primarily
within
healthcare.
I
mean
within
claims
adjudication
between
payers
providers
and
patients
right
now,
20
cents
of
every
healthcare
dollar
is
pretty
much
gone
from
broad
waste
or
abuse,
and
most
of
that
you
know,
comes
from
the
lag
time
and
the
friction
trying
to
get
siloed
databases.
O
You
know
working
together
because
right
now,
given
the
spiderweb
of
hipaa
and
pii
privacy
laws,
they
pretty
much
are
not
able
to
really
move
the
needle
much
because
they
have
to
anytime.
You
have
any
type
of
unifying.
You
know
I
guess
initiative
and
stuff.
It
brings
up
the
the
problem
when
it
comes
to
reporting
and
if
you're,
a
participant
within,
say
a
healthcare
ecosystem,
and
you
you
know
just
join
the
the
consortium
or
the
network.
O
You
then
become
part
of
the
the
reporting
requirement
and
that
creates
an
extra
burden
on
that,
and
you
know
right
now.
O
You
know
right
now,
it's
so
big
and
it's
so
fragmented
that
baseline
can
basically
come
in
and
contribute
so
much
because
of
you
know:
you're,
demonstrating
that
proof
of
consistency
between
the
state
machines
that
everything
has
to
stay
very
locked
up
and
walled
off,
probably
the
biggest
opportunity
I
see
there
is
in
health
care
claims
adjudication
I
mean
if
you,
if
anyone
has
a
procedure,
let's
just
say
a
colonoscopy,
so
you
get
a
colonoscopy
and
let's
just
assume
that
all
of
the
people,
all
of
all
the
participants,
are
in
your
payer
network
everything's
in
network.
L
O
Colonoscopy
you're
done
everything's
fine
you're,
going
to
get
within
a
week,
you're
going
to
get
a
minimum,
a
minimum
of
seven
pieces
of
mail
you're
going
to
get
from
each
legal
entity
that
participated
in
your
episode
of
care,
yeah
and
they're
all
going
to
basically
say
this
is
not
a
bill
but
they're
going
to
basically
assert
their
presence
in
whatever
service
they
provided
so
you're
going
to
get
a
bill
from
the
clinic,
the
gastroenterologist
from
the
the
lab,
the
pathologist,
the
anesthesiologist
who's
gonna
bill,
you
twice
one
for
the
service
and
one
for
the
medication
and
then
you're
gonna
get
a
you
know
an
explanation
of
benefits
from
your
healthcare
payer.
O
If
you
could,
actually,
you
know
have
that
type
of
proof
of
consistency
between
all
of
these
siloed
architectures.
You
can
have
that
claim.
You
know
paid
settled
and
closed
in
a
fraction
of
the
time
and
at
the
same
time,
you're
preserving
you
know.
As
we
talk
about
volume,
purchase
agreements
payers
are
going
to
have.
You
know
specific
reimbursement
agreements
with
different
providers.
O
Patients
are
going
to
have
their
co-pays,
their
underwrote
deductibles.
You
know
that
entire
just
mine
field,
that
you
have
to
navigate
within
your
your
health
insurance
company-
you
know
tying
all
of
these
together,
so
that
they
can
at
least
have
that
common
frame
of
reference.
You
will
go
ahead
and
get
that.
You
know
that
that
claim
settled
and
closed.
B
You
know
mark
I,
I
love
I
love
where
you're
coming
from,
because
you
know
I
said
this
in
the
beginning
of
the
session.
It's
like,
we
don't
want
to
just
build
stuff
just
to
build
stuff
right.
We
want
to
be
able
to
build
stuff
so
that
it
provides
the
world
some
sort
of
a
benefit
right
now,
I'm
using
the
world
as
a
very
exaggerated
point,
but
I
mean
look,
I
mean
the
the
you
know
I
was
laughing,
but
I
was
not
not
laughing
to
make
light
of
it.
B
I
was
laughing
because
these
are
real,
serious
issues
that
that
are.
You
know
we
can
spot
these
inefficiencies
and
really
drive
home.
You
know
and
that's
and
that's
the
point-
and
you
know
you're
speaking
about
healthcare,
so
shout
out
to
consensus
health,
I'm
not
sure
if
anyone
is
here
from
consensus,
health,
we've
seen
them
in
the
baseline
specifications,
steering
committees
and
so
on
and
so
forth.
So
I
think,
if
you
have
a
chance,
you
can
definitely
chat
with
them.
I
know
that
they
would
love
to
hear
about
it.
Yeah.
B
P
B
Awesome
cool
all
right.
Well,
I'm
going
to
give
somebody
else,
one
more
chance,
because
I
really
just
want
to
hear
you
know.
Stefan,
I'm
not
trying
to
dig
into
your
session
over
here
we're
going
to
give
you
the
spotlight
in
a
second
but
somebody
else.
Where
else
would
you
like
to
see
from
a
product
cookbook
perspective?
D
Yeah
thanks
hi
everybody.
I
hope
you
can
hear
me
well,
yep,
jumping
a
little
bit
between
different
sessions
and
every
time
setting
up
my
audio
device
is
new,
so
yeah
good
good
evening
from
from
germany
at
least
it's
9
p.m.
D
Here,
and
I
was
I
was
following
the
last
minutes
of
the
discussion,
and
perhaps
I
want
to
to
follow
up
on
what
nick
said,
because
I
really
like
that
as
a
vision,
especially
that
out
of
the
box
approach,
and
although
my
presentation,
I'm
also
joined
by
uni,
bright's,
ceo
and
my
co-founder,
martin
is
about
sap.
D
All
of
these
face
the
same
challenges,
and
it
does
not
matter
so
much
if
you
are
talking
about
an
sap
system
or
perhaps
dynamics
or
salesforce,
and
we
we
had
already
great
detailed
presentations
on
on
these
specific
ones
earlier
on
this
track.
D
What
I
think
the
great
thing
about
baseline
that
sums
it
up
is
that
it's
not
driven
by
one
of
the
mentioned
big
erp
players,
but
that
it's
really
coming
from
the
protocol
point
of
things
and
that's
actually
the
chance.
So
my
wish
for
for
baseline
one
year
from
today
would
be
actually
that
the
world
gets
to
know
about
the
advantages
of
an
integration
approach
that
is
not
driven
mainly
by
one
of
the
big
players,
but
rather
is
coming
from
a
from
a
community
from
an
integration
community.
D
As
as
I
understand
it,
because
this
really
gives
the
the
opportunity
to
include
and
integrate
all
players,
not
only
those
who
are
able
to
run
a
big
erp
system,
but
perhaps
integrate
their
google
sheets
or
their
local
database
or
their
proprietary
self-development
solution,
but
still
be
part
of
a
network
that
enables
to
put
additional
trust
into
business
processes.
So
that's
what
what
I
hope
that
one
year
from
now
many
individuals,
companies,
associations,
enterprises,
developers,
integration
companies,
understand
the
the
power
that
is
behind
the
idea
of
baseline,
actually.
B
Thank
you,
stefan
and
martin,
so
really
quickly
before
before
we
pass
this
off.
B
What
I
want
to
do
is
just
you
know:
I'm
not
gonna
start
from
the
beginning
and
go
all
over,
because
I
would
take
a
couple
hours,
but
what
I
want
to
do
is
just
kind
of
provide
a
recap,
because
we're
actually
almost
at
the
end
of
the
breakout
session,
and
we
had
a
lot
of
good
discussions
and
just
you
know,
I
see
I
see
a
bunch
of
new
faces
in
in
this
room,
so
just
quickly
setting
the
stage
here
this
this
breakout
session
is
intended
for
those
that
are
developers
our
business
users,
our
administrators
are
into
code
or
into
use
cases
etc,
or
just
want
to
learn
about
what
the
baseline
protocol
is
really
all
about.
B
B
We
went
into
the
standards
of
the
modern
audit,
the
standards
of
modern
applications,
but
really
it's
the
standards
of
the
baseline
protocol,
as
as
it
relates
to
all
the
different
core
interfaces
and
again
just
to
shout
that
out
we
have
the
core
interfaces
breakout
session
too,
then
what
I
did
was
went
into
a
baseline,
microsoft
dynamics,
365
environment,
which
started
out.
Actually,
you
know
with
the
unibright
team
and
provide
and
envision
and
others,
and
we
and
we
got
together-
and
you
know,
put
together
this
demo.
B
We
had
people
log
into
the
d365
environment.
So
stefan
and
martin,
you
guys
weren't
here
we
showed
them
a
d365
to
another
d365
environment.
They
clicked
around.
They
got
to
experience
what
it
would
be
like
to
send
things
out.
We
kind
of
we
kind
of
highlighted
some
some
some.
You
know
some
some
of
the
points
that
also
is
documented
in
the
eminent
task
force.
B
Hackathon
2
so
feel
free
to
talk
about
that
one,
how
we
use
the
out
of
the
box
out
of
the
box
modules
and
then
we
just
tied
together
some
of
the
you
know,
product
cookbook
ideas,
how
we
would
integrate
with
the
global
phone
book
where
the
core
interfaces
came
in
and
and
how
integration
really
looks
like
it
like
it's
native
out
of
d365
and
dom
did
the
same
thing.
So
then.
D
Thanks
then
perfect,
I
can
share
my
screen.
I
guess.
D
Yes,
yes,
we
did
thanks
tom.
I
want
to
perhaps
first
take
a
step
back.
D
This
presentation
was
initially
also
considered
to
be
part
of
the
of
the
cookbook
session
that
is
now
part
of
the
round
table
later
and
for
that
cookbook
session,
understanding,
a
cookbook
as
something
that
changed
the
slide
cookbook
to
create
recipes
for
available
ingredients
and
where
the
recipes
can
be
best
practices
or
reference
implementations
like
the
one
that
dan
just
mentioned
in
context
of
the
ea
eminent
task
force,
hackathons
and
the
ingredients
can
be
the
defining
parameters
of
your
specific
business
process.
D
So,
if
you're
talking
about
a
cookbook
that
somebody
would
have
a
look
into,
if
you
knows
some
of
the
ingredients
he
has-
and
he
perhaps
knows
his
favorite
favorite
dish-
then
he
can
take
a
look
into
the
cookbook
on
how
actually
find
the
right
way
or
the
right
algorithm
to
or
the
right
workflow
steps
to
baseline
a
process
and
before
we
we
get
to
the
details
of
of
sap.
It's
really
important
for
for
me
personally,
and
also
for
for
our
unipride
team
that
we
take
this
on
a
little
bit
on
a
generic
level.
D
Every
every
party
that
wants
to
be
a
part
of
a
or
a
participant
in
the
baseline
process
somehow
has
the
same
challenges,
as
I
mentioned
just
before.
There
are
different
systems
of
record
involved.
There's
a
specific
document
flow
to
the
process
that
should
be
baselined
and
all
the
end
users.
I
mean
we.
We
should
not
forget
about
that.
It's,
of
course,
baseline,
is
a
protocol
and
it's
a
it's
a
great
protocol.
D
It's
also
really
fun
to
dive
into
the
specifics
of
a
protocol,
on
the
very
say,
lowest
technical
layer,
but
in
the
end,
if
we
are
talking
about
a
vision
on
who
will
use
baseline
in
one
year
from
now,
then
in
the
end,
it's
about
making
a
customer
experience
for
the
end
users
of
a
respective
erp
system.
That
is
part
of
a
baseline
process.
So
we
have
to
ask
the
question,
no
matter
if
it's
a
sap
system
or
if
it's
just
a
custom,
built
a
small
database.
D
Database
based
application
at
what
layer
do
participants
need
to
view
the
baseline
status
and
the
messages,
and
what
are
the
integration
points?
So
our
approach
at
the
hackathons
we
are
been
running
and
also
at
the
client
projects
we
are
currently
doing
with,
for
example,
kona
and
and
fraunhofer
is
exactly
answering
these.
D
These
questions
first,
before
we
dive
into
the
details
on
how
sap
can
baseline
say
a
purchase
order
and
something
that
we
always
promoted
and
also
something
that
we
learned
in
the
in
the
baseline
context,
to
be
even
more
important,
is
to
talk
about
the
right
domain
models.
So
just
a
short
short
side
note
on
how
unibright
is
doing
it
together
with
provide.
We
are
building
products
around
the
baseline
pattern.
We
have
been
building
a
no
code,
blockchain
framework
already
before
that,
and
this
is
now
getting
adapted
to
to
baseline
and
the.
D
The
first
point
here
is
the
visual
definition
of
domain
models,
and
that's
actually
already
the
the
central
point
of
our
of
our
approach
that
if
you
want
to
have
an
integration
happening
between
different
parties,
you
have
to
have
something
both
parties
or
all
parties
can
rely
on.
D
No
matter
what
the
underlying
system
of
record
may
look
like-
and
this
is
what
we
understand
as
as
common
domain
models,
so
at
least
the
most
important
fields,
attributes
or
states
or
methods,
for
example,
a
purchase
order,
and
it
may
be
that
there
is
a
leading
system
in
a
process
and
that
you
just
take
the
say,
sap
model
of
a
purchase
order
as
as
the
domain
model
that
all
parties
have
to
rely
on.
D
So
everything
we
do,
the
visual
definition
of
processes
and
circuits
in
the
baseline
context,
code
generation
deployment,
automatic
mapping
from
domain
models
to,
for
example,
to
sap
and
or
even
proxy
generation
api
generation.
All
this
is
relying
on
the
common
understanding
of
a
domain
model
of
the
objects
that
you
want
to
baseline
yeah.
T
I
mean
I
mean
stefan
perhaps
I
can
add
something
to
it.
It's
it's
martin
from
uni
bright
here,
as
we
so
much
emphasize
on
domain
models.
It's
it's
not
only
about
the
the
technical
side
of
things,
but
about
the
process
side
of
things
as
well.
I
mean
for
our
customers.
We
know
that
they
live
and
they
think
in
in
their
processes.
T
So
it's
super
vital
that
we,
when
we
have
a
let's
say,
a
purchasing
scenario,
we
need
on
a
technical
level.
We
need
functions
or
api,
calls
that
somehow
do
things
like
send
a
purchase
order
or
receive
a
quote,
but
this
is
vital
too,
for
all
the
people
that
design
the
distributed
business
processes
within
a
company
that
we
get
onto
this
level.
Because
that's
where
these
people
are,
we
we
can't
do
or
we
can't
have
any
blockchain
specifics
on
this
level,
because
these
people
are
just
they
are
not
known
to
it.
T
D
Exactly-
and
I
think
this
is
also
great
potential
for
for
baseline,
because
now
with
baseline,
you
have
an
argumentation
towards
using
blockchain
in
enterprise
processes,
where
blockchain
is
really
used
for
that
part
of
the
implementation
logic
where
it
really
provides
the
most
benefit
in
an
enabling
trust,
but
perhaps
not
on
replacing
everything
that
a
local
enterprise
erp
system
is
able
to
do
it.
D
I
mean
that
was
more
more
of
the
pitch
of
the
last
say
or
three
years
ago,
when
it
came
to
the
idea
that
we
could
just
replace
every
erp
system
by
that
big
distributed
database
called
blockchain
or
one
year
later,
we
could
replace
every
custom-built
business
logic
by
a
world
computer
with
smart
contracts.
D
And
the
first
one
is
the
project
that
we're
doing
together
with
with
kona
and
without
getting
too
much
into
the
details
is
still
still,
as
this
is
still
work
in
progress,
as
in
all
projects
when
it
comes
to
baselining
that
we
are
currently
working
at
it's
about
an
object
sequence
that
has
that
is
established
already.
So
I
mean
this
process
is
not
new
with
with
baseline.
D
It's
been
there
for
for
decades,
for
example,
in
this
case,
placing
purchase,
orders
and
sending
them
to
potential
vendors,
which
will
then
turn
purchase.
Orders
into
sales
orders
in
a
later
point
in
time
create
delivery
notifications
that
reference
these
sales
orders,
and
then
you
have
an
ongoing
object,
sequence
or
document
flow,
as
you
would
call
it
an
sap
from
shipment
over
goods
issues,
because
receipts
until
you
have
something
like
a
billing
document,
an
invoice
that
could
even
be
tokenized
afterwards.
D
So
the
object
sequence
can
be
as
complex
or
as
long
as
the
as
the
case
desires.
But
the
thing
with
baseline
is
that
you
can
baseline
each
of
the
of
the
states
of
these
of
this
workflow.
D
So
each
of
the
documents
that
represent
a
workflow
step
in
a
complete
process
from
ordering
to
to
invoicing
and
have
multiple
parties
agreeing
on
the
same
state
that
is
represented
in
their
respective
erp
system,
and
this
is
just
one
example
where,
where
you
can
see
that,
if
you
start
a
project
with
a
customer,
it's
not
so
much
about
baselining
in
the
first
place.
It's
not
so
much
about
explaining
zero
knowledge
proofs
on
saying
a
sales
order.
T
Yeah
but,
but
I
think,
that's
the
great
potential-
I
mean
it's
as
you
said
stuff
and
it's
it's
all.
These
processes
that
already
exist
and
every
big
company
does,
for
example,
some
purchasing,
and
so
we
always
have
these
options
object
sequences
we
can
baseline
so
by
enabling
these
already
existing
business
processes.
To
do
something
unique,
let's
say,
use
the
trusted
middleware
that
we
can.
We
can
add,
with
baseline,
doing
it
that
way
that
we
can.
T
We
can
really
focus
on
getting
this
unique
addition
to
distributed
business
processes,
it's
much
easier
than
starting
with
pitching
blockchain
or
starting
with
zero
knowledge
proofs,
it's
much
easier
to
have
this
business
process
in
place
and
then
tell
the
customer.
Oh
now
we
can
have
this
this
great
technical
edition
that
wasn't
possible
before.
D
Exactly
and
it's
it's
also
showing
the
potential
in
terms
of
that
many
unsolved
problems
still
have
to
do
with
that.
Some
players
are
kept
out
of
an
integration
process,
because
I
mean
every
participant
in
a
say:
a
procurement
process
knows
his
his
business.
He
knows
how
he's
creating
the
the
goods
receipts
he's
know.
D
He
knows
how
his
daily
process
looks
like
and
perhaps
the
the
issue
of,
not
being
part
of
a
say,
a
supplier
network,
or
something
is
not
because
they
don't
understand
the
process
or
they
would
not
be
able
to
deliver
the
desired
quality,
but
rather
that
they
are
not
able
to
be
part
of
a
digital
and
automa
automated
process.
D
D
We
can
take
a
look
at
what
this
should
look
like
for
when
it
really
comes
to
to
the
roll
out
of
a
new
project.
This
is
also
an
example
from
the
from
the
kona
project
and
also
from
the
fraunhofer
project
that
we're
doing.
D
Currently,
when
we
are
starting
a
new
project,
we
spent
most
of
the
time
in
the
really
like
hours,
days
or
weeks
in
the
design
time
so
defining
the
models
and
also
the
the
mappings
to
existing
systems
and
to
get
the
process
right
and
once
that
project
is
up
and
running,
or
at
least
in
a
in
a
state
where
you
can
roll
out
a
better
version,
including
some
pilot
suppliers
or
whatever
it
always
comes
to
the
to
an
easy
deployment,
which
is
also
important
in
a
in
a
scenario
that
is
built
in
a
way
that
new
participants
should
be
able
to
join
at
any
time.
D
So
in.
In
our
case,
building
this
together
with
provide.
We
have
design
time
we
have
the
unibright
modeling
tools
and
to
deploy
time
the
the
provide
shuttle
tools
to
to
have
an
automatic
setup
so
that
in
runtime
you
can
rely
on
all
these
previously
designed
and
and
published
parts
of
the
system.
D
We
have
different
containers
representing
the
the
unibride,
the
provide
stack
and
and
the
actual
baseline
stack,
but
it's
important
to
to
show
that
understanding
first,
because
we
get
now
into
details
of
an
sap
implementation,
how
we
did
it
there,
but
it's
important
to
understand
that
the
sap
implementation
comes
into
the
picture
earliest
at
the
deploy
time
and
then,
of
course,
at
runtime,
but
that
many
integration
projects
fail
or
because
there's
not
enough
effort
or
not
enough
time
or
resources
or
yeah
domain
specialists
during
the
design
time
of
the
process.
D
D
Okay,
so
also
one
high
level
example
how
we,
how
we
did
this
in
in
the
corner
project,
so,
let's
just
for
an
example,
take
a
purchase
order
that
comes
out
of
a
sap
system
and
is
due
to
be
sent
to
different
vendors
that
are
part
of
that
process.
D
We
had
the
feeling
that
it's
or
not
the
feeling
we
are
convinced
that
it's
better
for
the
client
that
there's
a
certain
level
of
control
of
the
data
flow
towards
a
new,
say,
tech,
stack
or
technology
when
it
comes
to
running
in
sap.
So
of
course,
we
could
just
offer
the
baseline
apis
as
they
are
currently
there
in
the
great
reference
implementations
which
work
just
fine,
but
still
in
the
in
the
daily
project.
D
So
what
we
did
is
that
the
the
complete
message
control
and
also
a
part
that
that
we
defined-
or
we
designed
with
our
unibride
subconnector,
where
you
can
model
different
workflow
steps
within
the
sap
which
then
get
baseline.
So
on
the
left
side,
everything
we
need
to
stay
within
sap
is
is
also
code
wise,
it's
still
in
sap,
because
there
we
model
the
actual
process
from
the
leading
system.
D
You
find
again
the
domain
objects
here
on
the
on
the
right
side,
and
this
is,
of
course,
by
by
purpose,
because
everybody
who
would
not
be
able
to
run
an
sap
system
would
still
rely
on
the
same
underlying
stack
from
the
baseline
message
over
yeah,
more
meaningful
object
away
from
the
from
the
from
the
message
layer
and
then
mapped
into
a
purchase
order.
D
Domain
object
in
this
case,
and
this
is
also
the
entry
point
where
every
other
erp
could
could
be
integrated,
and
this
finally
leads
to
what
what
we
wanted
to
talk
about
when
we
when
we
said
that
sap
is
just
one
example.
All
these
questions
that
we
have
and
answered
in
sap
with
an
internal
workflow
management
with
status
management
with
or
or
like
daniel,
showed
earlier
within
dynamics,
with
specific
ui
elements
that
show
a
certain
baseline
status.
D
All
these
questions
still
have
to
be
answered
on
a
ui
level
or
on
an
end
system
level
for
for
for
every
party
that
wants
to
be
baselined,
but
all
these
questions
can
be
answered
based
on
at
least
the
domain
object
model
that
is
common
with
all
the
participants
of
a
work
group.
That's
the
idea
behind
this
message.
Flow
and
component
structure.
T
Yeah,
I
just
had
the
idea
that
I
mean
this
slide
is
I
think
it's
the
core
slide
on
integration.
Stefan
perhaps
this
would
be
a
good
point
in
time
to
ask
for
for
any
questions
I
mean
just.
L
T
The
screen
no
current
questions
or
chat,
but
perhaps
someone
wants
to
add
something
I
mean
just
to
rephrase
what
is
very
important
to
me
being
visualized
by
this
slide.
Is
I
don't
know
if
everyone
is
familiar
with
this
term?
Idoc
orders
o5
in
the
second
box.
T
On
the
left
hand
side
I
mean
this
is
the
the
standard,
edi
format
or
standard
edi
document
that
is
used
within
sap,
so
it's
nothing
special
to
to
blockchain
or
to
anything
it's
just
like
kona
is
using
is
using
idocs
today
for
the
electronic
data
exchange,
and
so
we
just
stay
in
that
domain.
They
already
know
how
to
exchange
order,
orders
or
five
idocs,
and
then
it
makes
it
much
easier
for
them.
T
If
we
just
stay
there,
take
that
eye
doc
and
then
convert
it
into
a
json
representation
and
then
get
it
into
our
own
stack.
So,
from
a
customer's
perspective,
that's
much
healthier
than
exposing
any
techie
api
calls.
Yeah.
D
D
We
are
building
multiple
pocs
at
a
time,
but
as
as
often
it
turns
out
that
eighty
percent
or
around
eighty
percent
of
different
processes
are
still
comparable
and
the
last
twenty
percent
need
some
customization
on
on
client
level
and
finding
that
right
line
between
the
80
and
the
20
should
in
our
in
our
opinion,
or
at
least
that's
our
approach,
and
our
hope
should
be
exactly
the
line
between
these
two
two
stacks.
So,
for
example,
if
we
take
a
look
this,
this
was
the
kona
example.
D
If
we
take
a
look
at
the
fraunhofer
case,
we're
currently
working
on
just
to
give
some
context,
it's
it's
about
a
3d
laser
printing
device
that
is
equipped
with
iot
sensors
that
continuously
deliver
data
about
the
performance
of
the
machine.
D
This
protocol
data
is
sent
to
sap
as
measurement
documents,
and
the
idea
behind
is
to
have
these
protocol
data
aggregated
and
baselined,
for
example,
once
a
day
and
send
out
to
all
potential
suppliers
that
may
be
able
to
to
deliver
a
specific,
maintaining
service
or,
for
example,
cooling
liquid.
If
the
if
the
machine
is
or
the
sensor
of
the
machine
is
notifying
that
there's
a
problem
with
with
with
cooling
liquid
and
as
soon
as
specific
values.
In
that
protocol
messages
are
surpassing
specific
thresholds.
D
Then
we
automatically
have
a
maintenance
message
that
and
then
we
are
again
inside
an
sap
workflow,
which
is
not
which
is
independent
from
if
the
underlying
or
the
following
integration
technique
is
baselined
or
not,
which
is
triggering
an
internal
sap
workflow
on
mapping
the
the
maintenance
message
to
the
right
service
or
product,
finding
potential
vendors
for
this
service
or
product
triggering
a
request
for
quotation
process.
D
Quotations
and
purchase
orders
following
after
that,
so
I
mean
the
the
setup
is
something
completely
different
than
talking
about
purchase
orders
in,
for
example,
in
the
coca-cola
world,
but
from
a
baseline
perspective,
as
soon
as
it
comes
to
document
flows
or
object,
sequences
that
are
baselined,
it's
quite
comparable,
at
least
on
the
eighty
percent
of
how
to
connect
an
erp
system
to
to
the
baseline
stack,
and
this
is
also
why
we,
we
are
often
asked
okay,
what
are
the
use
cases
for
baseline
and
which
industries
can
can
baseline
serve,
and
our
answers
is
that
baseline
should
be
something
that's
more
in
our
understanding,
that's
more
or
less
use
case
independent,
because
it's
it's
really
more.
D
An
integration
pattern
or
a
document,
sequence
trust,
adding
pattern
and
not
so
much.
It
should
not
be
narrowed
down
to
specific
cases
like
supply
chain.
We
all
need
these
cases
and
these
projects
and
these
pocs
to
show
the
the
power
of
something
like
baseline
but
baseline,
is
not
narrowed
down
or
reduced
to
specific
use
cases.
If
you
understand
it
the
way
that
we
try
to
understand
it
as
a
tool
to
add
trust
to
existing
processes.
That
have
a
specific
object,
sequence
or
document
flow.
T
D
Yeah
and
perhaps
just
to
to
close
that
idea
or
that
that
presentation
also
I
mean
we
I'm
sure
that
dan
touched
the
sap
d365
integration
demo
earlier,
and
it
would
also
be
very
interesting
to
to
do
a
re
recap
or
a
re-demo
of
that,
given
the
current
state
of
the
implementation
of
of
the
baseline
protocol
hint
hint
daniel.
Let's
do
something
together
here,
but.
T
A
It
looks
first
of
all
great
presentation,
but
the
it
looks
from
what
you're
showing
that
you
took
the
idoc,
which
is
an
edi
standard,
moved
it
to
json
and
then
put
it
through
the
provide
stack.
So
you
didn't
have
to
agree
on
the
actual
data,
because
the
suppliers
are
already
prepared
for
that
information
coming
from
kona.
D
Yeah,
but
perhaps
if
you
think
about
widening
the
supplier
network-
let's
perhaps
not
not
make
this
too
specific
about
kona,
because
I
I
would
rather
have
andre
and
colleagues,
of
course,
going
into
the
details
of
death
of
that
in
another
presentation.
But
of
course
you
are
limited
in
terms
of
integration.
If
not
anybody
in
the
ecosystem
has
has
something
in
place
like,
for
example,
sapi
or
other
mappers
or
translators.
D
When
it
comes
to
just
reading
idoc
messages,
I
mean
martin
and
me
have
been
doing
these
kind
of
integration
projects
for
for
15
years
prior
to
baseline,
and
it
was
in
90
of
the
cases-
is
what
it
was
always
about-
mapping,
for
example,
eye
docs
or
other
standards
to
the
specific
environment
of
a
smaller
player,
and
in
that
case
it's
not
so
much
helpful
if
you're.
Only
if
you
have
to
send
out
or
receive
eye
docs
here,
it's
not
only
the
the
translation
of
an
idec
into
a
json.
D
This
is
rather
a
technical
challenge
that
can
easily
be
solved,
but
it's
also
the
the
common
way
of
setting
up
the
the
tech
stacks
that
are
used
for
integration
and
especially
enabling
to
have
that
integration
layer
in
all
user
interface
layers.
That's
that's
what
I
was
wanted
to
show
in
that
slide
here.
D
D
All
this
is
also
part
of
the
integration,
and
this
is
what
an
idoc
itself,
of
course,
could
not
is
not
capable
of
of
showing
to
the
different
participants
of
an
integration
process.
T
Yeah
yeah,
I
think
that's
just
just
one
addition.
I
think
that's
the
the
core.
I
mean
we
use
idocs
in
the
beginning
and
in
the
end
of
every
process,
just
as
a
data
format
that
is
standardized,
but,
of
course,
all
the
nice
things
and
all
the
magic
of
baseline.
It
still
happens
within
the
provided,
write
stack
so
to
say
everything
about
circles
and
zero
knowledge,
proofs
and
agreements
and
baseline
work
groups
agreeing
on
things.
That,
of
course,
still
happens.
T
It's
just
like
as
soon
as
we
touch
an
off-chain
system
like,
for
example,
sap
system
or
a
microsoft
erp
system,
then
we
use
the
standards
that
are
in
place
there
and
that
are
used
to
to
the
customers.
If
that's
right,.
I
D
Yeah,
so
so
much
for
the
for
the
scope
of
baseline
and
sap,
I
mean
there
are
tons
of
or
thousands
of
approaches
how
to
how
to
tackle
that
it
was.
D
Our
idea
was
to
show
a
little
bit
on
the
hands-on
projects
that
we
are
currently
working
on,
how
we
understand
baseline
in
that
context,
and
also
understanding
this
session
as
a
preparation
for
the
everything
around
the
cookbook,
where
it's
actually
about
participation,
we
would,
or
we
would
love
to
see
one
of
these
sessions
contributing
to
to
the
list
of
say,
desired
systems
of
record
that
should
be
baseline.
D
That
gives
a
preparation
to
actually
jump
on
the
part,
also
for
tomorrow.
Reading
john's
comment
here
in
the
chat
to
have
more
hands-on
conversations
on
yeah.
Let's
work,
something
out
what
should
be
the
content
of
a
cookbook
that
say
one
year
from
now,
somebody
that
has
not
heard
about
baseline
until
then,
who.
D
I
don't
know,
but
perhaps
there
are
still
people
left
so
that
they
have
something
in
their
hands
like
a
cookbook
okay,
how
do
I
approach
my
existing
system
and
my
existing
processes
to
check
if
they
are
base
lineable
and,
if
so,
with?
What
should?
I
start.
K
Yeah,
like
I
mean,
if
you
think
about
I
mean
sap
and
dynamics,
are
a
little
different
this
way.
But
if
you
think
about
systems
like
like,
like
intuit
quickbooks,
you
know
you'd
want
to
build
a
user
experience
into
that
that
that
took
advantage
of
baseline
attributes
and
events
in
a
way
that
you,
you
couldn't
do
from
the
open
source
side
right
on
the
you
know.
K
That
needs
to
be
done
in
the
application
user
experience
so
be
nice
to
be
able
to
have
a
bit
of
a
cookbook
that
helped
you
you're
gonna
have
to
write
that
code
in
your
environment.
K
To
your
environment,
but
it'd
be
nice
to
have
patterns
and
that
sort
of
thing
that'd
be
that's
what
I
think
of
as
a
cookbook.
By
the
way,
I
want
to
say
about
bob's
question
about
edi.
Unless
it
was
I've
been
flipping
back
and
forth,
because
I'm
sort
of
the
av
specialist
for
this
whole
event.
But
if
it
wasn't
mentioned,
there's
a
pretty
interesting
project,
that's
happening
in
the
next
actually
was
supposed
to
drop
right
now,
but
kind
of
pushed
it
off
because
of
the
event
around
edi
and
border
and
customs.
K
So
that's
yet
another
case
of
edi
work.
You
know
with
baseline
and
I
think,
there's
a
lot
of
speculation.
That
baseline
will
be
useful
in
opening
up
the
idea
of
multi-multi-party,
practical,
multi-party
edi
or
at
least
making
that
more
straightforward
and
tractable
so
more
to
come
here
bob.
I
I'm
definitely
starting
to
get
all
my
old
friends
from
like
the
best
buy
supply
chain
folks
and
guys
like
rick
rummel.
I
gotta
call
him
up
and
say:
hey
it's
time,
it's
time
to
get
going.
S
Yeah
and
I'd
also
like
to
jump
in,
and
just
mention
really
quick
in
regards
to
the
cookbook
and
and
putting
together
some
ideas
that
people
can
look
to
and
really
implement
in
the
future.
I
think,
if
there's
ever
an
opportunity
for
us
to
double
dip
and
like
automate
something
to
fix
another
problem
in
the
process,
we
should
do
that,
if
possible
kind
of.
S
K
Thank
you
now
for
something
completely
different
if
you
just
for
complete
fun,
if
this
is
a
good
breaking
point,
I'll
put
this
in,
if
you
want
to
get
a
real,
kick
go
to
that
link
in
the
chat
and
open
up
two
or
three
of
the
tabs
that
are
that
are
where
people
are
active
and
then
run
audio
on
all
of
them
at
the
same
time,
and
you'll
get
a
sense
of
how
this
could
be
actually
a
way
cooler,
a
way
of
doing
real
conferences.
K
K
You
know
they've
all
been
just
webinars
with
people
talking.
That
was
the
best
experience
ever
so
do
that
for
each
other
and
just
grab
somebody
go.
I
want
to
talk
to
you
and
go
into
a
private
room
and
you
know
do
that,
but
it's
also
fun
to
listen
to
all
of
the
different
work
happening
simultaneously.
It's
the
best.
K
K
Awesome
by
the
way,
all
of
these,
what
we'll
do
with
these
sessions
your
daniel
this
session,
it
will
have
will
probably
be
by
far
the
largest,
because
it's
got
so
much
content
running
across
the
streams,
but
we'll
we'll
take
the
live
streams
and
hopefully
cut
them
down.
Hopefully,
nothing
goes
wrong
with
those
live
streams,
because
that's
how
we're
recording
this
as
well,
because
it's
gonna
be
30
hours
of
of
eight
streams
simultaneously.
So
hopefully
nothing
goes
wrong
with
youtube
and
then
we'll
be
able
to
cut
those
down.
K
J
U
Hi
everyone
yeah-
it
was
kind
of
carrying
on
from
a
previous
question
where
I
I
just
thought
of
the
analogy
of
baseline
as
a
set
of
metadata
or
headers
that
get
stumped
on
top
of
standardized
business
messages,
whether
these
are
edi
or
something
else,
and
then
kyle
responded-
and
this
was
kind
of
me-
responding
to
kyle.
D
D
T
U
F
U
D
Yeah
then
you're
totally
right,
because
this,
if,
if
you
talk
about,
let's
call
it
local
metadata
that
one
baseline
participant
uses
to
when
receiving
a
message
from
the
baseline
stack
retranslating
it
properly
into
the
specific
model
of
say
sap,
then
of
course
you
even
you
even
should
enrich
that
domain
model
object
with
a
with
current
state
or
log
messages,
so
to
make
the
integration
easier.
D
This
could
be
one
idea.
The
other
idea
is
just
to
to
reading
it
every
time
you
want
to
have
access
to
it
from
the
from
the
api
and
looking
back
into
other
persistence
layers
or
mechanisms
that
are
in
place
on
the
baseline
stack.
But
if
you,
if
you
talk
about
the
point
where
a
domain
model
leaves
the
baseline
stack
to
reside
again
in
the
in
the
erp
system
or
in
the
system
of
record
of
one
participant,
then
you
are
totally
right
this.
This
is
one
way
it
could
be
done.
K
Can
I
have
a
couple
minutes
to
talk
about
something,
that's
been
in
my
mind
about
this.
If
you
don't
mind,
can
you
guys
hear
me,
okay
by
the
way,
okay,
I'm
getting
weird
feedback
in
my
head?
Okay,
that's
because
I've
got
like
15
different
broadbands
running
at
the
same
time
on
one
machine.
K
It's
crazy,
I've
got.
I've,
got
eight
azure
instances
with
remote
desktop
top
running
on
this
machine.
I'm
surprised
it
hasn't
caught
fire.
So
on
this
we
we
used
to
talk
a
lot
back
in
the
early
part
of
last
or
the
middle
of
last
year
about
this
idea
of
a
code
book
and
yeah.
I
think
we
started
calling
it.
I
call
it
that
after
watching,
I
was
watching
a
documentary
about
apollo
missions
and
how
compute
was
done
on
those
on
those
spacecraft
and
it's
like
all
right
call
code.
K
K
It
seems
to
me
what
I
want
to
do
is
I
want
it.
Maybe
this
is
a
good
thing
that
we're
doing
baselining
in
the
age
of
containers
as
as
containers
mature,
because
what
I
want
to
be
able
to
do
is
say
I'm
going
to
write
in
whatever
language.
I
want
to
write.
I'm
going
to
write
this.
This
logic
circuit,
I'm
going
to
say
I'm
going
to.
I
want
to
do
here.
K
My
conditionals,
here's,
my
loops,
etcetera,
I'm
going
to
write
that
that
little
program,
maybe
it's
a
lambda
function,
or
you
know
that
sort
of
thing
and
then
not
only
do
I
want
the
data
on
both
my
system
and
your
system
to
be
verifiably
consistent.
I
want
the
code
to
have
been
run
consistently
and
to,
of
course,
result
generate
the
same
result,
and
then
all
I
need
is
a
zero
knowledge
circuit
to
enforce
the
consistency
of
that
container
right
so
in
a
world
before
containers.
K
K
I
wonder
if
that
isn't
something
that
needs
to
be
part
of
the
standard,
as
we
go
is
to
say
yep,
I'm
not
only
passing
you
some
data
via
this
messaging
layer,
I'm
also
going
to
pass
you
a
container
you're
going
to
execute
that
container,
I'm
going
to
execute
the
container
we're
going
to
run
the
baseline
process
through
that
and
now
I've
got.
I
can
construct
works,
workflows
and
in
business
logic
that
I
can
handle
where
I
don't
have
to
pay
a
you
know
a
mathematician
to
write
circuits
for
every
single
bit.
K
D
Yeah
makes
sense,
but
I
also
think
that,
even
in
the
first,
if
the
first
step,
if
you're
just
just
exchanging
messages
in
a
way
that
they
are
adding
to
the
state
of
a
system
of
record,
even
if
there
is
no
additional
code
needed,
that
needs
to
be
executed
already
provides
value.
And
that's
all
and
that's
a
good
thing
to
start
because
the
the
more
we
we
didn't
touch
that
in
detail
in
our
presentation.
D
But
one
of
the
ideas,
for
example
in
in
the
kona
context,
is
not
only
the
message
flow
and
the
sequence
of
documents,
but
also
the
versioning
of
them.
So,
for
example,
if
you
come
to
the
point
where
you
have
delivery
notifications
that
have
to
be
turned
into
a
payment
advice
or
an
invoice,
and
you
don't-
you
are
not
able
yet
to
agree
on
the
payment
terms
on
the
exact
payment
terms
or
perhaps
on
the
delivery
terms,
which
makes
the
delivery
more
expensive.
And
then
you
would
have
to
change
the
invoice
again.
D
All
this
would
be
an
example
where
you
need
some
small
packages,
defining
the
say,
the
next
stage
of
delivery
costs,
and
you
could
run
this
or
you
could
send
this
code.
This
part
of
the
code
book
over
to
the
participant
he's
executing
his
in
his
machine
and
then
he
can.
He
can
verify
that
both
parties
come
to
the
same
conclusion
in
terms
of
delivery
costs,
so
it's
very
very
exciting
in
the
say,
step
1.5.
D
Yeah,
that's
that's
totally
totally
fine,
but
I
I
I
think
that's
a
good
thing
actually
about
baseline,
that
it
already
adds
real
value
already
in
version
1.0,
when
it
only
comes
to
message,
exchange
or
object,
sequence,
baselining
and
all
the
stuff
that
you're
mentioning,
of
course
is
is
the
very
exciting
part
that
should
be
added
right
after
that.
K
Yeah,
it
has
to
be
thinking,
especially
if
you
guys
look
at
a
company
like
claws.
Clusc,
they
have
become
a
pretty
good
partner
with
docusign
and
they
they,
you
know,
I
don't
love
some
things
about
the
way
they
implement.
They've
got
they're
using
fabric,
and
I
I
will
make
fun
of
them
for
that,
because
it's
fun,
but
you
know,
I
think
that
they're
they've
become
very
successful
at
generating
these
little
code.
Snippets
out
of
legal
legal
documents,
so
they've
become
the
sort
of
you.
I
K
Docusign
started
with
effectively,
you
know,
signing
pdfs,
it's
what
you
effectively
had
right.
You
had
a
pdf
and
assigned
signed
one
now
now,
and
then
they
moved
to
you,
okay,
you
can,
you
can
mark
those
pdfs
up
with
fields
and
okay.
Now
you
can
jack
those
fields
into
your
salesforce
system
and
now
with
claws.
They
they
they're,
adding
business
logic.
They're,
saying
this,
this
agreement
has
business
logic
associated
with
it,
which
will
execute,
and
that's
what
got
me
thinking
about
that.
I'm
saying!
K
Well,
if
that's
the
case
now,
I've
got
a
master
service
agreement
with
business
logic,
and
I
need
your
machine
and
my
machine
to
verifiably
run
that
same
business
logic
without
having
to
rely
on
yeah.
The
the
you
know,
more
sas
style
of
doing
that,
because
you're
trusting
a
sas
organization
to
run
that,
for
both
of
you.
P
Yeah
john
just
add
quickly:
yeah,
we
looked
at
doing
something
similar
with
the
open
law,
integrations
and
kind
of
adding
their
dsl
into
different
contracts
and
then
eventually,
seeing
if
we
can
do
both
yeah,
add
the
dsl
and
then
make
them
compatible
with
the
baseline
for
call
messages.
I
think
that's
definitely
a
pattern.
Work
we're
looking
at
during
the
next
couple
quarters.
K
P
Yeah,
I
think
some
very
similar
kind
of
embedding
logic
with
the
dsl
inside
the
actual
contract,
which
is
doing
the
entire
msa
in
like
solidity.
B
All
right
all
right:
well,
it's
not
who's
next,
where
next,
all
of
us,
it's
what
we're
here
for
right,
so
so
just
kind
of
keeping
up
with
this
right.
We
have
about
another
hour
until
the
closing
remarks
and
happy
hour
and
the
the
baseline
summit
reception,
which
is
going
to
be
happening
just
right
after
the
closing
remarks
right,
john
nick.
B
Oh
good
good,
good,
baseline
bourbon,
you
can
send
it
this
way.
Baseline
bourbon
has
a
very
nice
ring
to
it.
It
does
actually
so
all
right.
We
have
the
unibright
team
over
here
we
have
avia,
we
have
dom.
I
think
I
see
I
see,
let's
see,
I'm
trying
to
look
through
the
participants,
and
I
know
that
kyle
was
supposed
to
supposed
to
say
a
little
something
at
the
very
end.
B
But
look
I
mean
one
of
one
of
the
aims
of
what
we
tried
to
do
today,
just
to
kind
of
bring
everyone
back
here.
Let
me
share
my
screen.
B
Is
throughout
the
course
of
the
day,
what
we
wanted
to
do
is
on
this
last
tab
right
here
is
this
cookbook
ideation?
If
you
will
right
so
we
asked
everyone
at
different
points
throughout
the
breakout
session
to
to
write
down
what
system
they
see,
what
use
case
or
feature
that
they
think
and
write
write
some
notes
about
it.
So,
realistically
this
this
last
section
was
really
used.
Let
me
go
back
over
here.
Oh
I
like
this
over
here.
This.
B
This
last
section
is
really
just
a
round
table
for
us
to
go
through
the
use
cases
list
that
we
saw
and
to
go
through
the
different
features,
and
we
could
talk
about
it
and
and
and
see
you
know
which
of
these
makes
sense
if
we
want
to
assign
a
prioritization
to
it.
If
we
wanted
to
see
which
ones
we
should
be
attacking
first,
I
mean
throughout
the
day
I
think
we
heard
everybody
say
that
they
want
to
see
salesforce
and
d365
integrated
and
see
a
demo
with
that.
B
We're
obviously
all
for
that.
I
love
it.
You
know,
but
let's
hear
from
everybody
else,
I
mean
you
know
open
law
and
baseline.
I
see
that
someone
just
just
had
written
that
in
there
we
have
quickbooks
provider.
So
look
what
I'll
do
I'll
go
through
I'll
read
some
of
these
use
cases,
and
I
really
want
someone
to
interrupt
me
and
let's
just
talk
about
them
right,
so
we
have
procurement
as
the
use
case.
Obviously
we
we
showcased
that
literally
all
day,
basically
the
connector.
B
That
was
something
that
was
something
that
we
showcased
as
well.
You
know
something
that
looks
native
to
the
system
of
record
to
be
able
to
take
on
these
core
interfaces,
to
be
able
to
read
these
apis
and
connect
to
the
provider
service,
which
is
which
is
the
core
of
the
baseline
protocol.
And
then
we
have
ecmr.
B
Not
there
and
then
we
had
another
one
sharing
a
confidential
document.
Well,
we
kind
of
showcased
that,
through
through
sap
right
through
d365,
through
salesforce
radish
34,
the
sensitive
document
that
we
were
looking
to
share
was,
or
is
the
proposal
right?
The
the
answer
back
from
the
rfp,
the
rfp
necessarily
is
not
necessarily
confidential,
but
the
answers
coming
back
would
be
confidential.
B
B
Let
me
know
what
everyone
thinks
about
this
we've.
You
know
envisioned
blockchain,
I'm
talking
about
us
specifically.
Here
we
have
jason
in
the
room
with
me
as
well.
You
know
we
try
to
stop
people
when
they
say
that
they're
sharing
this
information
right
because
are
we
sharing
the
information
right
when
from
like
from
like
a
messaging
perspective?
B
Are
we
sharing
things
because
we're
not
really
sending
the
information
through
mainnet
right
we're?
Not
that's.
That's
one
of
the
main
things
that
we
ended
up
not
doing
is
not
putting
anything
on
chain
and
making
it
queryable
right.
We
have
this
hash,
which
is
the
representation
of
what
it
is
instead
of
sharing
confidential
data
instead
of
sending
confidential
data,
I
feel,
like
you
know,
I'm
looking
at
jason
right
now
talking
among
us
right.
We
always
have
that
conversation
with
clients.
Are
we?
B
B
Yeah
so,
for
example,
right
in
in
in
the
in
the
d365
example
that
we
showed
you,
you
know
remember
when
we
were
using
the
service
operations
to
be
able
to
send
information
from
one
organization
to
another
right,
we're
not
necessarily
sending
information,
but
really
it's
that
proxy
data
model,
which
is
building
that
record
in
the
in
the
next
system
of
record
right
you're,
not
sending
it
it's
more
like
it's
a
creation
based
on
something
that
happened.
B
How
can
we
easily
and
quickly
say
like
we're
not
sending
the
confidential
document,
even
though
it
appears
to
be
like
that.
O
I
would
say
that
goes
back
to
when
a
lot
of
us
were
putting
together
blockchain
in
the
very
beginning-
and
I
think
you
know
just
by
default-
we
were
looking
at
you
know
private
blockchains,
as
kind
of
that
database
of
record
and
in
there
you
did
have
a
sharing
within
baseline,
we're
basically
saying
my
record
matches
yours
and
I'm
proving
it.
O
O
B
C
C
Hi,
can
you
hear
me
if
you
need
to
convince
people
that,
yes,
you
are
in
oh
you're,
holding
the
information
and
you
have
the
confidential
information
from
the
document.
You
can
prove
that
you
have
it
without
making
that
information
not
confidential
in
a
public
way.
Really
that's
the
whole
thing
of
the
zero
knowledge
proof.
R
Right
so
yeah,
if
I,
if
I
can
add
so
yeah,
I
I
kind
of
wrote,
I
I
added
this
line
to
the
document
and
in
the
notes
I
kind
of
had
that
one
of
the
kind
of
the
small
things
that
that
I
had
in
mind
is
being
able
to
confirm
and
to
validate
the
format
of
the
document
that
that
is
about
like
to
be
sent
to
like
the
receiving
erp
like
without
having
access
to
the
document,
because
you
don't
like
don't
want
to
share
the
document
to
send
it.
O
O
You
know
vendor
supplier
arrangement
to
where
there
is
some
enforcement
of
that
trust
to
say
hey.
If
all
of
a
sudden,
I
decide
that
I
don't
trust
you
anymore,
I
can.
I
can
actually
bite
you
back
as
it
were.
If
you
have
someone,
this
is
a
brand
new
relationship
that
you're
just
kind
of
feeling
each
other
out.
O
Baselining,
the
the
information
between
state
machines
goes
a
long
way
in
a
very
short
period
of
time
of
you
know
instilling
that
trust,
because
if
someone
says,
if
I
don't
believe
you
someone
can
say
well,
I
can
prove
to
you
that
what
I
said
you
can
actually
take
the
bank
or-
or
you
know,
make
it
actionable
about
whatever
I
just
told
you
without
you
having
to
wait
to
say.
Well,
I
don't
know
if
I
believe
you
send
me
this
send
me
the
receipt.
B
You
know-
and
I
think
you
know
between
everyone
that
just
commented
here,
makes
a
really
great
point
right,
because
when
we're,
when
we're
sharing
information,
it's
almost
like
we're
literally,
you
know
taking
a
piece
of
data
and
then
giving
it
to
somebody
else,
but
realistically
through
baselining,
what
we're
doing
is
proving
it
just
like
brian
had
mentioned
with
you
know:
zero
knowledge
proofs.
The
whole
point
is
proof
right.
B
Cool
okay,
hr
data
is
anyone
here
that
wrote
that
one
in.
O
Actually,
daniel,
I
have
another
question
before
we
actually
dig
into
that.
Second,
one
there,
let's
say
I'm
one
of
your
counterparties
and
we're
doing
something
very
sensitive.
Are
you
know
something
that's
really
important
to
both
of
us,
and
I
say
I
need
to
know
that
you
know
your
state
machine
matches
mine
and
you
send
me
a
zero
knowledge,
approved
basically
saying
that,
yes,
it
will.
What
does
that
look
like?
O
How
do
I
have
the
confidence
that
what
you
just
sent
me
was,
you
know
not
a
bunch
of
you
know
just
gobbledygook
I
mean
how
do
I
have
that
confidence
I
mean
other
than
you
know.
We
all
understand.
What's
your
knowledge
proofs
look
like,
but
the
average
you
know,
procurement
director,
you
know
is
like.
I
have
no
idea
what
that
I
mean.
What
does
that
look
like,
and
how
is
that?
How
do
I
get
to
the
point
to
where
I
trust
that
implicitly.
K
C
K
Right,
how
do
you
know
setting
up
so
we
need
a
protocol
for
that
right
to
say
yep.
You
know
this
isn't
gonna
fall
over
as
I
push
it
at
you
and
you
can
do
that
right
now.
You
do
that
manually
right,
like
I'm
sure,
with
with
provide
unit
right.
That's
probably
what
they're
doing
each
of
those
bottlers
are
they're
manually,
making
sure
that
those
interface,
those
those
records
are
gonna,
be
sensible
to
each
other
right
but
yeah.
K
Now
this
is
a
middleware
problem
for
the
ages
and
there
are
ways
to
deal
with
it.
I
think
again,
it's
kind
of
like
the
container
thing
I
was
mentioning
earlier.
K
You
know
it
might
be
good
that
we're
doing
this
baselining
stuff
now,
because
there's
maturity
around
the
api
economy
and
knowing
that
you
have
good,
I
mean
that
introspection
metaphorically
introspection
across
you
know
to
the
other
party.
So.
B
So
so
I
have
an
interesting
way
to
to
to
attack
that
point
and
we've
seen
it
now
a
couple
different
times
throughout
this
breakout
session,
and
you
know,
like
you,
said
right:
the
the
manager
at
that
business
department,
for
whatever
procurement
software
or
whatever
software
that
happens
to
adopt
this
technology.
They
don't
know
zero
knowledge
proofs,
nor
do
they
care
to
know
about
it.
They
just
want
to
know
that
right.
It's
like
there's,
there's
benefits
that
come
with
that.
B
B
So,
while
somebody
that's
an
admin,
let's
say
for
salesforce
that
dom
is
showing
that
there's
ways
that
you
can
lock
the
field
or
lock
the
form
you
know
a
way
to
describe
it
to
those
folks
is
you
know,
look
your
business
process
can't
move
forward
unless
certain
criteria
is
met
and-
and
I
think
that'll
vary
a
little
bit
based
on
what
the
what
the
actual
you
know,
software
is
whether
it's
d365,
sometimes
you
see
you
know
like
I
was
showing
in
the
presentation
earlier
there's
like
that
red
box
that
can
come
outside
of
the
field.
B
You
can
lock
the
field
it
shows
like
there's
like
it
literally
shows
on
the
ux
that
there's
like
a
little
lock
on
it
right
or
maybe
there
can
be
notifications
that
come
up
that
says,
hey
something,
something's
been
tampered
with
or
something
doesn't
match.
B
O
Well-
and
it's
also
kind
of
like
in
in
the
early
days
of
ethereum,
you
know
we
used
to
say:
code
is
law,
and
now
here
we
are,
you
know
as
john's
kind
of
taking
us
forward.
You
know
code,
don't
lie
and
but
again
yeah
it's
one
of
those.
You
have
to
instill
that
that
that
trust,
where
people
sit
there
and
say
yes,
I
know
that
that
you
know
I
can
basically
accept
this
and
then
approve.
You
know
our
whatever.
The
next
step
within
the
transaction
is
going
to
be.
B
You
know
it's
like
it
can
even
be
further,
where
you
know
it's
just
like
I'll
just
say
the
inverse
of
what
you
said
it's
like.
If,
if,
if
something
doesn't
match
up,
then
the
workflow
just
doesn't
happen
or
the
business
process
can't
move
on
to
the
next
step,
whether
you
lock
that
down
via
zk
circuits
or
you
lock
that
down
right
now
I
mean
we
could
lock
it
right
now
without
anything
to
do
with
zk
without
anything
to
do
with
blockchain
or
anything
right.
K
Well,
I
mean
yeah
part
of
the
it's
a
weird
benefit,
but
it
is
a
benefit.
You
know,
if
you're,
an
administrator
you're
supposed
to
be
able
to
change
the
record
and
you're
supposed
to
know
at
that
moment
that
you've
debased
that
record
yeah
all
right.
So
that's
a
great
example
of
a
yeah.
I
think
that's
what
you're
getting
at
right.
That's
a
good
cookbook
item
is
to
say
yeah.
O
K
Know:
here's
the
cookbook
for
making
sure
that
your
administrator
knows
and
your
user,
perhaps
and
in
some
cases,
know
that
for
one
reason
or
another,
that
record
is
no
longer
consistent
with
the
things
that
was.
It
thought
it
was
supposed
to
be
consistent
with
also
I.
I
should
think
that
I
I
want
to
something
like
a
more
fancy
tool
tip.
You
know
a
lot
of
applications
to
be
able
to
mouse
over
something
or
whatever
the
interface
is
to
see
with
whom
is
this
funny
colored?
K
You
know
if
you
color
the
record
differently
for
being
baseline,
for
example,
I
mean
you
know
you
might
do
that
as
a
very
bad
designer,
I'm
sure
there's
a
better
way
to
do
that.
We've
good
designers
on
the
team
here,
but
you
know
you,
you
look
at
it
and
you,
okay,
well,
who
okay,
I
see
that
this
is
baseline
with,
whom
is
it
baselined?
K
Is
everybody
still
baselined
right?
Do
I
have
some
kind
of
a
heartbeat
there
and
yeah
no
is
this?
Is
this
is
airtight
as
a
blockchain
enthusiast
from
the
last
five
years
would
like
new,
but
you
have
to
be
in
a
digital
nudist
colony
to
make
that
work,
and
most
of
us
don't
want
to
live
in
that?
Well,
certainly
I
don't
that
would
be
horrible,
so.
O
But
a
lot
of
times
it's
like
okay!
Well,
what
is
it
that
people
have?
You
know
have
that
trust
now
you're
either
sending
me
a
copy
of
you
know,
maybe
a
receipt
you're
sending
me
a
bill
of
lading,
saying
proving
that
I
sent
it
you're
you're,
getting
a.
I
guess,
pulling
up
a
screenshot
of
a
fedex
tracking.
A
O
K
Have
we
discussed,
you
know
the
the
corollary
to
that
which
is
I'm
I'm
consistent.
I've
got
to
make
my
sap,
or
my
sql
record,
consistent
with
the
your
record,
which
is
in
neo4j,
is
one's
a
graph
database
and
one's
a
sql
database
seriously.
That's
quite
an
interesting
topic.
I
A
K
K
G
K
A
Right
right,
I
mean
this-
this
baseline,
I
think,
is,
is
a
step
up
for
sure,
and
I
I
think
you
know
this,
this
transmitting
edi
documents
back
and
forth.
You
know
it's
30,
40
years
old
right.
What
what
we
should,
I
can
send
you
an
email
faster
and
get
things
done
right,
whereas
with
baseline,
I'm
building
on
that
and
transmitting,
and
at
least
I'm
incorporating
in
the
zero
knowledge
proof.
I
think
that
it
leads
to
these
other
things
that
you're
bringing
up.
K
There's
nothing
there's
nothing
that
would
stop
you
from
setting
up
a
like
two
excel
spreadsheet
instances
where
I
baseline
a
cell
in
that
excel
spreadsheet
and
then
send
you
via
email
as
the
messaging
layer,
the
the
the
material
and
then
baseline
it
from
that
you
don't
actually
need
you,
don't
technically
need
to
use
gnats
or
something
like
that
and.
A
I
think
a
lot
I
think
a
lot
of
people
are
actually
doing
that
because
it's
not
easy
enough
to,
which
is
where
baseline,
I
think,
is,
has
piqued.
My
interest
is
that
this
this
gets
to
the
heart
of
the
matter
on
what
what
information
or
what
metadata
or
what,
what
zero
knowledge
proof
you're
going
to
pass
so
that
you
can
use
this
public
main
net.
A
Just
like
the
transportation
industry
uses
the
roads,
we
we
standardize
the
roads
and
the
the
red
and
the
green
and
the
yellow
lights
right
so
that
we
trust
when
we
come
to
that
intersection
that
you're
going
to
stop
at
the
red
light.
I
I
have.
I
have
a.
I
don't
know
if
I
have
a
zero
knowledge
proof,
but
I
have
the
idea
that
you're
going
to
stop
at
that
red
light
right.
L
K
Yeah,
I
would
I
I
have
to
think
that
there's
somebody
like
maybe
that
carnegie
mellon
guy
is
gonna
say:
oh
yeah,
this
is
lovely,
I'm
just
gonna
containerize
it.
You
know
too,
because
that's
just
the
obvious
next
step.
I
don't
think
anybody's
tried
that.
Yet,
although
it's
getting
hard
to
know
what
people
have
tried,
because
so
many
people
are
trying
trying
things.
K
No
somebody
was
like
there
are
no
dumb
ideas.
I'm
like
I
love
dumb
ideas.
They're
my
favorite
thing:
they
they
lead
to
smart
ideas.
So
no,
I
was
just
blightly
pondering
over
the
notion
of
what.
If
what
you're
sending
to
people
is
not
you
know
json
what,
if
you're
sending
what
if
we
just
standardize
and
say
yeah,
you
send
it,
you
send
containers
and
the
container
might
contain
just
data
or
it
might
contain.
You
know
what
we
were
calling
a
code
book
before
right.
You
might
contain.
K
You
know
some
some
business
logic
and
is
there
a
way
to
to
get
a
say,
say:
I'm
running
one
system,
you're
running
a
different
system,
completely
different
systems.
I
send
you
a
container,
you
know
docker
container,
you
execute
it.
I
execute
it
we're
executing
into
completely
different
environments,
but.
N
K
N
Yeah,
I
can
see
that
I
can
see
the
container
execution
being
an
input
to
like
a
an
input
to
the
circuit.
N
K
If
I'm
in,
like
linux
and
you're
in
something
else
and
and
there's
different
environment,
fac
environment
factors,
would
there
be
a
way
to
this
is
my
limit
of
understanding
on
containers?
I
used
to
know
more,
but
could
you
get
this
the
same?
Could
you
get
a
signature
from
both
or
all
the
parties?
What.
N
I
N
I
mean
there
probably
are
edge
cases
where
the
signature
would
break
but
or
like
the
output
would
not
be
not
the
same.
B
Just
to
be
devil's
advocate
over
here,
why
would
you
need
baseline
to
pass
through
a
container
pull
if
you
will,
as
opposed
to
just
giving
you
you
know
the
url
to
do
it.
N
K
N
N
B
Containers
so
so
just
kind
of
just
kind
of
continuing,
because
it's
actually
spurring
some
interesting
conversations.
So
we
were
talking
about
the
sharing
approving
of
confidential
documents.
Somebody
else
wrote
down
we're
just
kind
of
doing
like
a
debriefing
of
things
that
people
wrote
down.
You
know
we
have
hr
data
being
sent
many,
especially
in
a
gdpr,
regulated
country.
J
J
C
B
Oh,
this
is
good
right
because
you
know
we're
all
attacking
this
from
different
perspectives
of
experience
that
we've
had
in
the
past.
So
you
know
it's
all.
It's
all
really
good
right.
The
next
next
line
over
here
is
multi-party
state
machine,
synchronization
consortium
or
multiple
companies
serving
a
bigger
one,
for
instance,
inventories.
B
J
Yeah,
that's
so
one
of
the
things
we've
identified
with
baseline
right.
We've
got
a
lot
of
examples
of
two
parties.
Baselining
stuff.
You
know
the
next
leap
would
be
a
multi-party
kind
of
baseline,
where
your
work
group
has
three
or
more
participants.
I
N
B
You
know
the
next
one,
after
that
there
was
enterprise
risk
management
there.
This
wasn't
necessarily
a
use
case
or
a
feature:
enterprise
risk
management,
in
my
opinion,
it's
more
of
like
a
practice,
but
I
think
I
think,
mark
that
was
you
right.
O
I
did
yeah
so
basically
looking
at
this
from
yeah.
If
you
look
at
it
from
a
from
an
enterprise
standpoint
to
where
you
have
someone
in
there
and
actually
what
gave
rise
to
this
was
the
conversation
that
we
had
is.
Do
you
have
to
have
two
or
more
parties
in
a
baseline
transaction?
O
Could
it
be
just
one
using
baseline,
and
I
said
absolutely,
my
thoughts
were
absolutely
because
if
you
look
like
within
enterprise
risk
management,
if
you
look
at
the
role
of
a
risk
manager
or
a
chief
risk
officer
or
whoever
is
tasked
with
monitoring
holistically
the
entire
enterprise
at
any
given
time
they're
having
to
rely
upon
data
that
comes
from
disparate
siloed,
you
know,
platforms
inventory
is
going
to
be
on,
one
payroll
will
be
on
one.
O
Logistics
will
be
on
another
each
one
of
those
are
going
to
have
gatekeepers
and
they
don't
have
that
real
time
reliable.
You
know
window
of
what's
going
on
and
that's
one
thing
that
they
in
their
role
pretty
much.
You
know
it's
a
huge
advantage
if
they
have
real-time
actionable
trusted
data,
so
you
baselining
these
different
systems.
It
would
you
know
it
basically
eliminates
or
at
least
reduces
the
gatekeeping.
O
You
know,
because
you
know,
if
I
got
you
know
if
I
could
get
payroll
data
from
a
cfo,
the
cfo.
You
know
he
may
be,
you
know
kind
of
self-important
and
it's
like
yeah
I'll
go
ahead
and
get
you
that
update
and
he'll
take.
You
know
a
week
to
ten
days
to
do
it
because
he's
a
cfo
and
what
are
you
gonna
do,
and
this
is
a
way
of
saying
I
need
that
reliable
data
right
now,
so
you
have
the
gatekeeping.
I
mean
this
happens.
O
You
know
in
an
earlier
career
I
was
setting
up
these
risk
management
information
systems
and
we're
using
api
calls.
You
know
to
pull
from
all
these
different
all
these
different
silo
platforms
and
you
know
all
of
them.
You
know
some
would
you
know
batch
update.
You
know
nightly
someone
batch
update
every
week.
You
know
that
sort
of
stuff,
and
you
know
right
now,
there's
a
lot
of
you
know,
permissioning
to
say:
hey.
Can
you
give
me
that
data
and
with
baseline,
they
can
say?
O
Well,
you
know
I
can
have
that
data
now
and
I
feel
comfortable
giving
it
to
you,
because
I
know
that
it's
only
it's
going
to
be
your
eyes
only
and
you
know
you're
able
to
actually
you
know
have
that
real-time.
You
know
viewpoint.
A
K
K
Maybe
you
have
this
spreadsheet,
but
we
have
a
colleague
who
did
a
financial
modeling
on
what
it
costs
to
stand
up
a
private
consortium
and
what
it
costs
on
a
you
know
ongoing
basis.
You
know
both
marginal
and
capital
costs
and
when
you
do
that,
when
you
ran
the
math
out,
if
our
numbers
on
baselining
are
anything
like
close
to
where,
where
we
think
they
are,
I
think
what
what
was
the
cause
it
was
baselining
was
was:
do
you
remember
the
the
number
nick?
I
can't.
K
A
five
in
there
it
was,
it
was
significantly
less,
maybe
a
fifth
of
the
cost,
and
don't
quote
me
on
that,
but
but
you
had
to
take
into
account
a
lot
of
overheads
and-
and
you
know,
there's
still
a
lot
of
speculation
on
that.
Like.
J
So
one
of
my
former
colleagues
at
oracle,
steve
cox,
wrote
a
book
around
kind
of
the
next
evolution
of
best
practices
for
enterprise
systems,
and
one
of
the
things
he
talks
about
is
the
financial
close
right
and
how
you
know
oracle
is
trying
to
integrate
their
existing
erp
suite
to
the
point
where
they
can
get
a
final,
an
annual
financial,
close
done
in
less
than
five
business
days.
J
He
says
today,
even
with
the
best
integrated
systems,
there's
there's
a
lot
of
chasing
and
waiting,
and
that's
exactly
what
mark
was
talking
about
right.
You
know
you
call
your
procurement
department
to
verify
some
data
and
you
got
to
wait
right
if
that
person's
out
for
lunch
or
gone
for
a
week
or
whatever
right
can
take
you
time
and
bob
you
hit
on
it
right.
You
know.
J
A
J
I
F
B
You
know
just
kind
of
thinking
out
loud
back
in
the
day
I
used
to
work
for
this
nonprofit
organization
was
called
financial
executives
international,
where
it
was
a
member-driven
organization
for
senior
financial
executives,
so
people
were
pitching
their
software
to
all
these
offices
of
the
cfo.
B
The
financial
close
was
always
top
of
their
mind,
and
you
know
that
there's
these
companies
like
work,
eva,
was
one
of
them.
W
desk,
I
believe,
is
one
highland,
softwares
and
other
that
they
provided
this
sort
of
accounting
software.
Maybe
those
would
also
be
ripe
for
baselining.
A
A
A
But
I
think
multiple
multiple
parties
you,
the
one
to
one
party
is,
is
the
start,
but
it
to
me
to
me
it's
going
to
work,
I'm
not
really
concerned.
Actually,
I
think
it's
going
to
work,
but
you
know,
and
when
a
supplier
gets
a
purchase
order,
then
the
agreement
is
made
with
the
retailer,
maybe
supplying
a
retailer.
The
transportation
company
is
involved
and
the
financial
company
is
involved.
A
A
B
Yeah
and
and
there's
been
a
lot
of
conversations
happening
around
baselining
and
edi
specifically
and
how
you
know:
there's
there's
a
very
big
value,
proposition
of
potentially
saving
costs
and
not
using
a
van.
A
Right,
that's,
that's
really!
The
you
know
we
did
use
big
companies.
We
used
our
own
edi
group
which
I
ran,
but
the
we
also
used
vans
because
it
got
to
all
the
little
players
and
that's
what
baselining
evens
that
out
for
everybody
and
we
don't
need
the
van
small
players
should,
even
if
they,
even
if
they
were
using
an
excel
spreadsheet,
they
could
probably
talk
right
and
then
adding
john's
ideas
on
there.
A
Yeah,
the
edi
has
already
had
a
has
agreed
upon
syntax
and
in
semantics
already
in
the
data
model,
you
can
use
that
and
leverage
that
and-
and
I
was
heavily
involved
in
those
standards,
work
and
we
had
to
agree
across
industries
not
only
within
transportation
but
across
industries,
but
the
mechanism.
You
know
you
each
had
to
have
a
translator
and
everybody
did
it
differently.
A
B
O
I
did
yeah
basically
inventory
logistics
and
finance,
and
you
know
bob
might
be
able
to
kind
of
echo
a
little
bit
on
this
and
stuff,
but
the
whole
logistics
industry
has
really
transformed,
within
the
past
15
20
years
to
where
you
you
know
really
having
that
just-in-time
delivery
that
just
that
less
than
less
than
load.
O
You
know
way
of
really
managing
how
you
know.
Physical
goods
are
moved
through
a
supply
chain,
and
you
know
one
of
the
risks
that
they
commonly
come
into
is
do
they
ship
something
that
hasn't
been
paid
for
yet,
and
you
know
that's
where
we
need
to
have
that
just
saying:
hey,
yeah,
we've
gotten
paid
go
ahead
and
ship
it
or
again
you
know
having
to
do
the
basically
the
supply
chain.
Having
to
have
these.
You
know
different
platforms
say
yep
go
ahead,
we're
we're
good
here.
O
You
can
go
ahead
and
do
what
you
want
to
it's
that
whole.
If
else,
you
know
thing
that
pretty
much
keeps
going
on
so
so
yeah
that
was
the
one
over
there.
Second
one.
I
came
up
with
this
healthcare
claims
adjudication,
and
this
is
one
that's
really
kind
of
been
really
interesting
and
it
can
be
a
little
bit
complex
to
explain.
O
I've
got
four
slides
that
I've
got
spooled
up.
If
anybody
wants
to
see
it
that
really
can
just
giving
you
the
visual
aids,
it's
actually
can
show
you
how
it
works.
Do
you
guys
wanna
wanna
share
it
up.
B
B
O
Okay,
all
right-
and
this
is
this-
is
something
that
I've
that
I've
just
recently
worked
on
all
right.
This
is
basically
looking
at
healthcare
claims
adjudication
and
you
know
you've
got
a
care
scenario.
They
call
it
an
episode
of
care
and
you're
going
to
have
multiple
providers.
Even
if
you
get
a
checkup
you're
going
to
have
multiple,
you
know:
healthcare
providers,
that's
your
your
doctors,
your
nurses,
it
doesn't
have
to
be
a
human,
it
could
be
a
lab
or
a
hospital.
O
Those
are
all
providers
and
you're
all
going
they're
all
being
paid
by
your
health
care
payer.
Your
health
insurance
company
and
the
health
insurance
company
is
going
to
have
to
find
payment
agreements
with
each
of
their
providers.
O
You
know
whatever
their
formulary
is
going
to
be,
and
you
know
patient
is
going
to
have
a
copay
they're
going
to
have
maybe
a
deductible
that
will
erode
over
time
and
all
of
that
has
to
be
accounted
for,
and
so,
whenever
you're,
having
a
claim,
you
know
you
get
a
procedure
done
it's
an
extremely
friction
process,
because
let's
say
you
get
a
colonoscopy
something
fairly
simple
and
I
use
this
within
my
care
scenario.
Here:
you're
gonna
get
at
least
seven
pieces
of
mail.
O
I
mean
because
you're
gonna
have
probably
five
care
providers.
You're
gonna
have
your
primary
care
physician
who
basically
ordered
it.
You've
got
the
gastroenterologist
who's
gonna
perform
it.
That's
the
specialist
there's
the
facility
where
he's
gonna
perform
it.
There's
gonna
be
well
on
this.
I
had
a
radiologist,
but
there's
going
to
be
a
pathologist,
that's
going
to
look
at
it
and
then
there's
going
to
be
an
anesthesiologist
who
gave
you
the
anesthesia.
O
While
you
got
that
I'm
sure
you
would
elect
to
have
it
but
he's
going
to
bill,
you
twice
he's
going
to
bill
you
for
his
service,
but
also
for
the
medication.
That's
just
how
it's
done
so
you're
going
to
get
seven
pieces
of
mail
minimum
within
a
week
after
this
episode
of
care.
So
what's
going
to
happen
here
is
the
claims
adjudication
process
starts.
O
O
But
what
you
want
to
do
is
have
someone
collate
this
into
a
single
event
and
that
everyone
can,
you
know,
come
together,
and
you
know
really
organize
all
of
the
record
keeping
between
between
the
payer,
the
provider
and
and
the
patient,
and
the
goal
here
is
to
basically
determine
what
is
everyone's
ultimate
financial
obligation
to
everyone
else.
You
know
what
is
the
payer
or
the
provider?
What
is
the
patient?
Who
do
I
pay
and
to
whom,
and
what
is
it
that
I
gotta
pay?
O
O
You're
also
going
to
get
an
explanation
of
benefits
from
your
from
your
health
care
payer,
and
this
is
the
stuff
that
I'm
sure
you're
gonna
be
paying.
You
know
close
attention
to
it's
a
very
friction
process
and
20
cents
of
every
healthcare
dollar
is
wasted
just
beyond
this
process,
waste
also
fraud
and
abuse.
O
But
that's
where,
having
that
record,
sharing
our
record
validation
between
these
different
siloed
participants
becomes.
It
takes
care
of
a
lot
of
that.
So
what
you
want
to
do
is
you
want
to
basically-
and
this
can
be
done
to
a
you-
know-
to
a
patient
being
an
app
or
a
web
portal
and
basically
say
this
is
where
everything
you
know
comes
together.
O
This
is
who
owes
what
to
whom
this
plane
can
be
settled
and
closed
in
a
fraction
of
the
time,
and
then
everybody
can
just
go
and
move
back,
and
you
know
the
current
looks
kind
of
like
this.
It's
just
this.
You
know
every
everything
is
just
you
know
a
mess
and
no
wonder
that
it
that
that
doesn't
go
well.
O
Let's
see
what
am
I
going
to
do
so
yeah,
and
so
basically,
what
you
want
to
do
is
using
this
right
here
to
where
everything
is
put
on
the
same
page
or
at
least
the
same
leg
ledger.
But
the
problem
we
run
into
here
is
the
record.
Keeping
no
one
is
going
to
share
anything.
You
know
that's
within
their
own
database,
just
due
to
hipaa
requirements,
they're
not
able
to
do
it
and
the
other
people
saying
and
don't
send
it
to
me,
because
then
that
adds
to
my
reporting
requirement.
O
You
know
under
hipaa
guidelines
so
right
now
we
just
want
to
be
able
to
prove
that
everybody's
record
shows
the
same
thing
and
that
we
can
then
go
ahead
and
determine
where
does
every
participant?
What
do
they
need
to
do?
Who
do
they
need
to
pay
and
then
settle
and
close
the
claim
so
20
cents
of
every
healthcare
dollar
care
in
the
u.s
is
13
trillion
roughly
so
they
can
send
so
20
is
around.
O
You
know:
300
billion
you're
talking
real
money,
so
this
is
just
the
example
that
I
had
for
healthcare
claims
adjudication.
So
did
that
resonate
with
anybody.
J
K
Yeah
mark,
I
I
think
that
I
was
about
to
tell
you
you
know
it's
not
so
much
logistics
x
or
y,
it's
a
but
you
you
went
down
into
the
satisfying
level
of
detail,
which
is,
I
think,
what
we
need
to
do
in
general,
and
maybe
we
can
pick
it
back
up
tomorrow
with
a
much
more
deep
dive
on
the
code
base
as
well.
K
I
I'm
hearing
you
know
people
need
in
the
other
tracks
or
or
especially
the
newbies
or
you
know
they
need
to
know
yeah
just
just
to
have
a
survey
course.
If
this
core
interface
does
this,
this
core
interface?
Does
this
here's
where
they
are?
You
know,
and
so
you
know
that
level
of
detail
for
the
code,
but
also
down
to
you
know
in
use
cases.
I
the
reason
I
hate
saying
use
case
is
because
it's
always
up
at
the
you
know
whenever
somebody
says
use
case.
K
K
A
use
case
is:
there's
a
guy
in
this
company
down
in
the
basement,
who's
going
to
burn
that
building
down
because
he
hates
his
life
so
much
because
he
has
to
hit
this
button
over
over
and
over
again-
and
you
know
it's
meaningless
and
we
got
to
make
his
life
suck
less
specifically
right,
you
know.
So
when
we
talk
about
the
logistics,
I
think
about
specifically,
where
are
the
consistency
problems
in
something
like,
and
you
brought
this
up
on
a
previous
call
mark.
K
K
O
Well
and
and
another
thing
that
I
and
actually
I
saw,
I
read
an
article
somewhere
that
microsoft
has
actually
formed
a
team
to
try
and
actually
address
this,
but
warranties
and
spares
you
know
when
it
comes
to
all
the
products
being
sold.
What
happens
when
you
know
some
of
it
might
be
defective
and
okay.
K
I
K
River
runs
through
it
right
half
as
long,
you
know
and
they
come
yeah.
The
writer
comes
back
with
that.
You
know
shorter
page
and
then
half
as
long
from
there
and
half
as
long.
You
know
so
that's
specific,
what's
specific,
underneath
that,
like
like
warranty
yeah,
so
what
particular
step
in
warranties
is
the
part
the
place
where
consistency
gets
filed.
O
Right
if
it's
going
to
be
a
repair
or
if
it's
a
replace,
because
if
you
have
a
repair,
you
still
have
you
know
remaining
part
of
the
original
warranty.
But
if
it's
a
replace
well
that
starts
the
warranty
clock
again,
because
it's
a
new
unit.
O
Well,
and
then
you're
going
to
have
another
thing
is,
is
also
data
formats.
You
know
taking
a
look
at
healthcare,
you
know
it's,
it's
a
horror
show
of
different
data
formats.
You
have
a
lot
that
is
still
on
paper.
That's
stored
in
you,
know,
iron
mountain
type,
you
know
facilities
and
stuff
and
somebody's
gotta
go
and
retrieve
that
and
pull
it
out,
and
then
you
know
either
you
know
copy
it
and
then
backs
it.
You
know
this.
This
still
happens
here
in
2020.
O
O
A
I
actually
working
with
the
reverse
logistics
association,
about
potentially
using
a
blockchain
for
that
issue
that
mark
brought
up
and
and
the
industry
has
to
agree
on
some
things.
They
they
can't.
They
can't
even
serial
numbers
on
electronic
products
are,
are
the
same
across
different
vendors
right,
oems.
A
A
K
A
Right,
let's
get
them
a
little
bit,
but
I
think
that's
why
that's
exactly
where
I
was
going.
I
think
baselining
right
brings
in
like
they're,
currently
moving
data
now
through
excel
spreadsheets
and
all
kinds
of,
and
they
they
manipulate
data
to
try
and
work
it
out.
But
but
baselining
starts
to
bridge
them
onto
a
system
of
record
and
do
because
without
the
blockchain
they
they're
not
forced
to
fix
these
problems
because
yeah
and
save
these
guys.
K
They're
gonna
they're
gonna
write
a
shared,
spread,
they're,
going
to
write
a
shared
database
and
they're
going
to
lock
themselves
into
that,
because
it's
going
to
exhaust
their
imagination
just
doing
that
right.
So
everybody's
going
to
be
tired
after
they
finish
that
mess
of
a
project
and
they're
not
going
to
want
to
do
any
more
blockchain
project
and
they
won't
have
the
energy
left
to
do
it
to
do
it
right
later.
A
A
Right,
you
could
use
the
you
could
just
exchange,
which
is
really
to
solve
the
problem
with
exchanging
data
as
it
moves
through
the
refurbish
or
reclaim
supply
chain
at
the
end
of
the
tail
right.
So
if
they
could
use
something
like
baseline
and
the
public
mainnet,
and
they
still
have
to
work
out
the
data
issues
right
because,
unlike
transportation,
they
don't
have
an
agreement.
K
Honestly,
if
it's
okay
for
these
guys
at
this
point,
maybe
this
is
where
we've
come
in
in
industry
and
in
society.
Maybe
we've
come
to
the
place
where
hyper
collaboration
is
more
important
than
secret
information
in
our
own
companies.
That's
fine!
But
then
it's
still
better.
K
If
that's,
where
they're
at
hire
an
admin,
create
that
that
that
that
consortium
that
they're
going
to
create
right,
which
is
going
to
be
a
jv,
which
means
you
can
have
an
admin,
have
that
admin
set
up
a
sas
system
right
in,
and
you
have
a
better
control
system
for
half
for
a
tenth
of
the
cost,
and
if
that's
okay,
for
them
to
have
all
the
data
in
one
place,
super
duper.
I
don't
think
that's
the
case.
I
think
everybody
sobers
up
and
goes
wait
a
minute.
K
O
O
You
know,
and
and
they
had
you
know,
since
they
were
a
plant
holder,
they
were,
I
guess,
one
of
the
owners
or
whatever,
and
you
know
it
becomes
a
wait.
A
minute.
A
K
A
Right
right,
I
I
know
I
was
there
in
my
former
time
a
year
or
two
ago,
and
yes,
we
we
said,
are
you
kidding
us?
You
want
us
to
and
then
sign
all
these
agreements,
but,
but
I
I
I
think,
the
sharing
and
collaboration
which
was
the
point
right,
which
is
coming
all
of
a
sudden,
full
steam
ahead.
We
need
answers
now
right
which
baseline
can
provide
now
right
in
using
current.
A
My
question
is:
what
do
we
use
to
collaborate
for
the
the
visual
domain
models
and
the
processes?
There's
there
almost
needs
to
be.
We
have
github
for
the
it
guys
which
my
former
life,
but
we
need
like
bizhub
right
to
collect
these
business
processes
right,
which
is
what
we
were
doing
in
edi.
We
were
coming
in
with
a
business
process.
We
would
agree
on
the
data,
stick
it
into
an
edi
and
then
everybody
went
back
home
and
did
it
on
their
own
edi
translator.
Maybe
over
a
van.
K
Hey
nick,
do
you
remember
that
what
was
that
called
fr?
Yeah
frtbs
right?
K
What
I
came
up
with
a
really
good
brand
for
a
product
for
frtbs
would
be
fart
based
right,
frt
base.
So
here's
the
problem
with
frtbs
is
a
arcane
thing
in
finance.
K
You've
got
a
trading
desk
and
you've
got
a
risk
desk
in
a
in
a
financial
organization
and
you'll,
see
where
this
is
sailing
in
a
second
and
the
financial
desk.
The
training
desk
has
a
book
right.
They
have
a
spreadsheet
basically
and
they
of
of
their
trades
with
counterparties,
and
then
the
risk
desk
ascertains
through
a
bunch
of
modeling,
so
that
effectively
they
mark
up
and
and
expand
on
this.
Theoretically,
technically
should
be
you
take
the
trading
desk
data
and
expand
it
in
this.
I
K
Record
or
in
this
other
spreadsheet
and
and
basically
work
out
whether
how
much
risk
you
have
as
an
organization
for
folks
not
paying
up,
and
you
know
thinking
you
have
an
asset
and
you
don't
have
as
much
of
an
asset
as
you
think
you
are
all
right,
so
that's
and
and
and
regulations
coming.
That
will
require
one
model
if
you
have
less
risk
and
more
one
another
model,
if
you
have
more
risk
in
a
nutshell,
point
of
that
is
people
are
like.
Oh
yeah.
K
We
need
a
blockchain
because
the
trading
desk
doesn't
want
to
you
know
and,
and
the
and
the
risk
desk
don't
want
to
use
each
other's.
You
know
the
training
guests
like
use
our
database
and
the
wrist
desk
is,
like
you
know,
use
our
database
and
and
they're
like
we
need
a
blockchain
for
that,
I'm
like
no,
you
don't
you
need
git,
you
need
git
right,
you
know,
git
would
be
better
all
right,
just
set
up
a
gift
server
and
then
both
of
them
get
to
think
that
they
have
their
own
database.
K
A
But
this
sharing
even
between
two
departments
in
the
same
company,
then
when
you
get
to
this
collaboration,
everybody
said
well
with
covet
now:
we've
got
to
collaborate
more
well,
we'll
see
how
long
this
lasts
right,
but
that's
truly
the
way
you
get
done
faster.
I
mean
we
were
doing
working
on
edi
standards.
A
They
don't
understand
the
technology,
but
then
when
they
start
to
understand
it-
and
they
say
you're
going
to
share
all
this
data,
then
everybody
starts
losing
it
right,
but
but
I
think
back
to
baseline
this
this
leveraging
what
we
already
have
and
dealing
with
what
we
can
brings
everybody
up
one
level
anyway
right
and
say:
oh,
it
is
possible
to
share
this
without
sharing
the
secret
right.
So
I
think
the
work
you're
doing
is
is
outstanding.
K
Sure
I'm
glad
you're
here
I
mean
it's
it's
one
thing
you
know
you
spend
enough
time
working
in
middleware
and
in
in
technology,
and
you
start
to
get
hungry,
like
my
brother's
at
you
know,
at
a
big
pharmaceutical,
that's
working
on
covid
right
now
and
way,
I'm
envious
of
him
because
he
he's
down
dirty
in
in
a
in
a
real
subject
with
real
nitty-gritty
problems,
and
he
deals
with
that
every
day.
He
knows
exactly
why
he's
getting
up
in
the
morning
and
what
he's?
K
What
problem
he's
solving
you
know
it
when
you're
in
technology,
you
kind
of
you're
sitting
once
one
chair
away
from
the
problem
you're
trying
to
help
somebody
solve,
and
it
can
be
an
odd
experience
right.
You
feel
a
little
bit
of
vertigo
from
there
right.
A
K
Is
exactly
what
we're
doing
you
forget
about
that
longshoreman
or
that
that
that
certified
agent
on
the
dock
in
oakland
freezing
his
his
back?
You
know
his
yeah
he's
just
freezing.
You
know
and
dropped
the
tablet
in
the
in
the
ocean
and
yeah
yeah
forget
about
these
things.
J
Gentlemen,
I
hate
to
interrupt,
but
I
need
to
jump
to
the
plenary
session.
We've
got
a
wrap
up
a
daily
kind
of
checkpoint,
scheduled
john.
I
would
love
if
you
could
make
it
over
there
to
to
give
your
impressions
and
and
kind
of
rally
the
troops
for
tomorrow.
All
right
thanks
thanks.
Everyone
sounds.