►
From YouTube: The Baseline Protocol Meets Enterprise Supply Chain
Description
In this presentation we will review the various challenges that supply chains face in todays enterprise community. More importantly, we will discuss the blockchain hype in supply chain and identify the difficulties that blockchain has had in gaining mass adoption. Additionally, we will introduce Envision Blockchains participation and experience in the open source Baseline Protocol which aims to overcome enterprise supply chains challenges via the public Ethereum Mainnet. Lastly, we will provide a demo of a supply chain use case that leverages the Baseline Protocol’s open source libraries which will offer attendees a visual understanding as to how the library can be used with current day systems while maintaining privacy and security. Learn more about Envision Blockchain Solutions below.
-------
Envision Blockchain Solutions is a Blockchain Systems Integrator. Our mission is to reshape and align today’s Enterprise systems allowing organizations to recognize the new value in tomorrow’s Industry Vertical Solutions. The management team has years of Fortune 500 experience and has built a team of subject matter experts in Blockchain and Business Transformation Processes within Emerging Technologies. We focus on guiding organizations through 3 major milestones on their Blockchain journey: Use Case Analysis, Proof of Concept Development and Enterprise Scaled Deployments.
System Integration:
✅ Dynamics 365
✅ Custom Applications
Blockchain Services:
✅ PoC & MVP Development
✅ Functional & Technical Requirements
✅ Smart Contract Development & Auditing
✅ Enterprise Tokenization
✅ Mobile and Web UI/UX Development
✅ Solution Testing
✅ Blockchain Migration Services
✅ Post Go-Live Services
✅ Support & Advisory Services
Workshops:
✅ Intro To The Baseline Protocol
✅ Enterprise Blockchain Tokenization
✅ Enterprise Blockchain Immersion
✅ Enterprise Blockchain Discovery
✅ Decentralized Identity Management Workshop
Feel free to reach out to us at:
Email: info@envisionblockchain.com
Website: www.envisionblockchain.com
Phone: (800) 513-8334
A
So
today's
presentation,
the
baseline
protocol,
meets
enterprise
supply
chain,
really
fascinating
topic,
really
fascinating
technology
and
methodologies
that
are
being
brought
to
emerging
technology
and
just
real,
quick,
obviously
envision
blockchain.
We
are
a
Microsoft
Partner
in
the
space
where
a
golden
partner,
proud
enterprises,
theorem
Alliance
members
and
participants,
of
course,
certified
through
the
Linux,
Foundation
and
and
corta
partnered
and
certified
as
well.
A
So
we
play
a
very
active
role
in
the
industry,
and
now
we
play
an
active
role
within
baseline
as
well
as
it
relates
to
the
open
source
which
we're
going
to
spend
some
time
learning
about
here
today.
At
the
same
time,
I'd
like
to
take
this
opportunity
to
to
go
ahead
and
introduce
Karthik
from
from
Ernst
&
Young
who's
actually
on
the
college
here
joining
us
today.
B
My
role
on
baseline
was
that
of
the
tech,
architect
and
solution.
We
work
got
a
chance
to
work
with
Type
O
developers
from
consensus
as
well
as
Microsoft
and
right
now,
I
play
the
role
of
one
of
the
technical
members
on
the
technical
steering
committee
and
maintain
a
one
of
the
maintenance
of
the
github
repository.
A
It's
really
impressive
project.
Thank
you
very
much
and
I
really
appreciate.
You
know
your
your
flexibility
and,
of
course,
ability
to
be
here
today
to
properly
convey
the
various
details
that
we
have
in
store,
especially
you
know,
taking
everybody
through
the
demo
that
that'll
be
towards
the
end.
So
looking
forward
to
maintaining
everybody's
attendance
and
keeping
everybody
present
and
again,
you
know
we'll
be
taking
questions
towards
the
end
of
the
presentation.
A
But
in
the
interim
my
name
is
Jason
Francis
I'm,
the
co-founder
of
envision
blockchain
solutions
and,
at
the
current
time,
I'm
sitting
as
the
co-chair
for
the
enterprise.
A
theorem
Alliance
pledging
sage-
and
that's
it.
You
know.
Supply
chain
is
something
that
that
I
hold
dear
to
art
and
and
passionate
about
and
really
have
taken
a
unique
approach
within
the
Antichrist
blockchain
space
as
it
relates
to
supply
chain,
which
is
drawing
me
to
that
cig
tradition
right
off
the
bat
but
at
the
same
time
the
other
co-founders
here
at
envision
block
Daniel
Norton.
A
So
we
have
a
very
interesting
and
diverse
set
of
representatives
between
envision
blockchain
interns,
young
and
it
would
be
unjust
if
I
didn't
call
out
everybody
else
who
has
played
a
very
active
role
in
ensuring
the
the
progress
that
baseline
has
seen
in
just
you
know
the
cups
in
a
couple
weeks,
since
it's
been
announced,
let
alone,
of
course,
consensus
in
Microsoft
and
hurts
and
young
being
the
founders
they've
had
they've
made
some
incredible
headway
since
the
start
of
this
project
so
again,
Karthik.
Thank
you
so
much
for
for
joining
today.
A
Just
a
brief
plug
envision
blockchain
we're
a
consulting
and
custom
application
development
organization,
I'd
say
we.
You
would
consider
us
more
of
the
the
enterprise
blockchain
systems
integrators.
If
you
will,
and
just
at
the
high
level.
You
know
we
perform
an
array
of
services,
as
you
can
see
there
on
the
left
with
respect
to
consulting
and
custom
development
services,
as
it
relates
to
various
different
components
of
the
modern
cloud.
A
So
when
we
look
at
when
we
look
at
the
the
the
various
array
of
I
guess
challenges
that
supply
chains
have
at
first,
we
kind
of
take
notice
that
there's
various
different,
rising
supply
chain
and
operational
costs
that
we
begin
seeing
as
a
result
of
globalization.
So
when
we
take
a
look
at
International,
International
supply
of
international,
you
know
supplier
sourcing
and
the
various
different
suppliers
that
a
supply
chain
can
now
have.
As
a
result
of
you
know,
global
communications,
peer-to-peer
communications
and
this
24/7
world's
that
we
really
live
in.
A
We
could
theoretically
be
supplying
and
bending
to
areas
different
b2c,
consumer
applications
for
e-commerce
and,
at
the
same
time,
wholesalers
may
be
supplying
through
different
ecommerce
type
platforms
that
are
b2b,
so
fulfillment
has
has
had
its
complexities
as
a
direct
result
and
that
all
leads
to
various
different
complexities
as
it
relates
to
making
proper
decisions,
and
these
specific
decisions
in
a
timely
manner
are
very
costly.
I
can
tell
you
firsthand
dealing
with
ocean
freight
shipping,
air
freight
inland
transportation.
A
You
know
efficient
delivery
times
and
quality
products,
but
in
fact
the
evolutionary
state
of
the
supply
chain
and
the
fact
that
we've
globalized
the
fact
that
we've
been
able
to
create
more
efficient
technologies
has
allowed
for
that
sort
of
a
luxury
where
the
end
consumer,
when
they,
when
they
purchase
something
through
an
e-commerce
platform
like
they
like
Amazon,
and
now
they
have
Amazon
Prime.
They
they
want
Amazon
Prime.
Now,
literally,
you
know
when
they
click
the
button
they
they
they
wanted.
Not
only
now
they
wanted
not
only
today.
A
And
as
a
direct
result,
when
we
began
experimenting
few
years
back
with
enterprise
supply
chain
as
it
relates
to
to
blockchain
what
happened,
is
we
had
this
huge
hype
cycle
and
since
we've
seen
this
diminishing
hype-
and
we
have
this
quote
here
from
from
an
article
that
was
taken
from
Gartner,
where
an
individual
said
that
it's
it's
impossible
for
organizations
to
identify
and
target
specific
high-value
use
cases,
of
course,
relating
to
blockchain
technology?
Instead,
companies
are
forced
to
run
multiple
development,
pilots
using
trial
and
error
to
find
one
that
might
provide
value.
A
That's
that's
very,
very
interesting
and
obviously
leads
to
a
lot
of
different
questions
and
clearly
leads
to
high
overhead
and
and
potential
loss.
So
privacy
has
been
and
always
will
be,
a
major
factor
as
it
relates
to
to
business
processes,
business
data
so
on
and
so
forth.
Of
course,
governance
is
always
going
to
be
a
factor.
A
So,
as
we
begin
to
break
this
down,
we
can
clearly
see
the
elements
that
that
directly
impact
or
concern
privacy
as
a
related
intellectual
property
as
a
relates
data
privacy,
the
various
different
business
processes
that
that
belong
to
any
one
specific
entity
and,
of
course,
the
better
various
suppliers
or
vendors.
That's
that's
it.
That's
a
huge
concern
with
respect
to
to
governance.
You
know,
as
we
begin
taking
a
look
at
establishing
these
these
network.
You
know
and
and
dealing
with
various
different
consortium.
A
All
I
think
about
is
that
you
know
the
days
the
years
the
month,
the
time
in
legal
fees
in
in
kind
of
you
know,
bucking
the
trend
so
to
speak
and
trying
to
get
technology
to
work
amongst
the
various
different
network
participants
that
may
already
be
competitors.
So
you
have
various
different
concerns
within
governments
within
governance,
participant
rights,
software
in
in
and
network
management.
How
often
do
we
iterate
who's
in
charge
of
the
various
updates?
And,
of
course,
then
you
have
to
put
the
participant
politics:
costly
barriers
of
entry,
we're
talking
Geographic
regulatory
variables.
A
What's
legal
in
this
country
may
not
be
in
another
country
which
means
to
to
to
more
legal
challenges
and
potential
barriers
that
may
and
may
prohibit
Network
participants.
Then
you
of
course,
have
the
concept
of
redundant
networks
or
if
this
company
is
doing
it,
then
why
should
I-
and
you
don't
even
know
if
you'll
ever
be
part
of
that
network
to
begin
with,
and
it
was
even
doing
what
you
have?
A
On
the
left
hand,
side,
we
clearly
see
and
we've
just
reviewed
all
of
the
various
different
challenges
that
we've
been
needing
to
overcome
and
on
the
right.
We
have
some
Advil
and
we
have
some
Gatorade
to
help
us
overcome.
You
know
this
blotching
hangover
that
that
we've
just
established-
and
you
know
moving
forward.
Today's
conversation
is
really
going
to
focus
on
solving
these
specific
challenges
and
realistically
we're
really
focused
on
enabling
confidential
and
complex
collaboration
between
enterprises
without
leaving
any
sensitive
data
on
chain.
A
It's
a
very
interesting
concept
because
we've
been,
we
haven't
necessarily
been
looking
through
that
prism
this
entire
time
as
it
relates
to
blockchain
and
supply
chain
and,
of
course,
various
other
industry
verticals
as
well.
So
let's
introduce
the
baseline
protocol
a
way
for
enterprises
to
use
the
main
net,
add
middleware
without
compromising
corporate
information
security
practices
I'm
going
to
briefly
just
run
through
this.
It's
a
lot
of
text,
but
a
lot
of
this
you
know
is,
is
all
open
source,
which
is
an
excellent
thing
and
you
can
go
and
reference.
A
A
The
baseline
protocol
has
has
introduced
and
is
currently
leveraging,
but
is,
of
course,
not
limited
to
the
etherium
being
that
it's
an
important,
it's
an
important
statement
that
that
elects
to
iterate
but
happens
to
be
right
now,
the
most
the
most
effective
and
reliable
common
term
reference
that
that
we've
currently
identified
and,
of
course,
last
but
not
least,
you
know
understanding
that
we're
trying
to
keep
business
as
usual
and
this
concept
of
a
baseline.
It
requires
these
various
different
systems
of
records,
which
are
simply
just
state
machines,
and
this
is
nothing
new.
A
So
realistically,
blockchain
is
exciting,
I
mean
Boren.
This
is
this
is
the
whole
point
watching
is.
It
was,
is,
and
was
a
hype
and
and
it
and
realistically,
let's,
let's
bring
it
back
to
reality.
Let's
what
keep
thing
is
not
exciting.
Let's
keep
things
boring.
Let's
make
sure
that
we
look
at
this
new
emerging
technology,
so
to
speak
as
middleware.
So
the
first,
the
first
component
here
is
to
to
ensure
local
system
of
record
is
baseline
compliance,
we're
talking
about
state
machines.
A
A
Likewise,
you
know
from
there
what
we're
talking
about
after
we've,
we've
established
this
this
system
of
record
and
and
in
its
baseline
compliance.
We
can
then
begin
setting
up
the
various
different
workgroups
and
we
can
begin
sending
sending
messages.
You
know
off
chain
messages,
secure
off
chain
messages.
A
Well
now,
you
can
use
the
main
mat
to
prove
that
to
prove
that
that
your
system,
where
that
data
over
that
workflow
has
been,
has
been
baseline
successfully
and
everything
can
match.
This
is
when
everything
winds
up
being
put
onto
this
main
network,
or
this
or
the
you
know.
This
is
the
system
of
reference
and,
of
course,
tokenization
is
an
interesting
concept.
We're
not
going
to
get
too
much
into
that,
but
this
is
a
huge
area
of
opportunity,
as
it
relates
to
to
decentralize
finance,
where
we're
not
interested.
A
So
the
baseline
protocol
is
a
series
of
open
source
libraries
and
I
just
want
to
reiterate
that
blockchain
isn't
the
issue.
It's
boring
at
this
point
in
time,
we're
looking
at
it,
as
you
know,
as
just
basically
a
reference
common
reference
in
that
our
approach
since
the
beginning
may
have
been
off.
So
these
are
the
various
libraries
from
privacy
messaging
main
that
libraries,
clearing
API
libraries
and,
of
course,
queuing
system,
and
what
we're
taking
a
look
at
here
is
in
the
first
line.
A
You
see,
radish
34
in
this
specific
case
is
leveraging
his
Ock
reduce
with
respect
to
its
your
knowledge
proof.
If
you
have
another
application
that
you'd
like
to
use
and
develop
leveraging
the
baseline
protocol
open
source
libraries,
you
can
feel
free
to
use
which,
whatever
whatever
you'd
like
you
have
your
choice,
the
same
will
go
for
messaging.
The
same
will
go
for
main.
That
I
mean
at
this
point
in
time.
A
Aetherium
main
that
is,
is
the
current
choice,
but
that
is
up
for
discussion
in
the
event
that
anybody
has
any
additional
thoughts
solutions
so
on
and
so
forth.
Again.
This
is
open
source,
likewise
querying
API
libraries
and,
of
course,
the
queuing
system,
and
you
know
moving
forward
I'd
like
to
introduce
Karthik
to
really
go
into
the
details
of
the
reference
implementation
that
leverage
the
open
source,
libraries
that
we
that
were
calling
the
baseline
protocol
named
radish
34
and
I'd
like
to
hand
that
off
to
you
at
this
point,
Karthik.
B
We
see
that
in
most
of
the
communication
is
more
or
less
bilateral,
whereas
in
some
cases
there
it
can
change
in
terms
of
the
communication
being
multilateral,
where
one
party
needs
to
disseminate
multiple
messages,
either
of
the
same
content
or
of
different
content
or
different
folks
or
different
different
participants
or
different
recipients,
but
regardless
from
procurement
point
of
view.
Some
of
the
challenges
we
identified
for
an
implementation
of
procurement
solution
was
any
bilateral
communication.
B
That
means
that
it
can
be
handled,
and
that
does
not
require
the
use
of
blockchain
or
does
not
have
a
business
incentive
to
use.
Blockchain
we've
not
do
so.
They
can
still
be
managed
by
using
a
private
communication,
a
private
communication
channel.
So
this
applies
to,
for
example,
requests
for
proposals
where
request
for
proposal
traditionally,
more
or
less
and
the
email
or
some
sort
of
secure
point-to-point
communication.
B
In
the
case
of
radish,
we
as
an
implementation.
We
used
whispered
as
one
of
the
primary
areas
in
which
the
image
decentralized
secured
communication
can
still
happen
and
there's
not
a
necessity
to
have
any
transaction
or
overall
change
to
the
blockchain
or
the
main
net
itself
then
then
comes
into
the
mass
spect
of
the
agreements
implements
our
business
relationship
terms,
which
are
mutually
attested
and
also
which
required
that
both
parties
are
legally
required.
B
Legally,
it's
required
that
any
parties
are
entering
into
an
agreement
are
indeed
agreeing
to
the
terms
of
the
agreement
and
in
such
a
way
that
there
are
other
concerns
around
revealing.
The
counterparties
involved.
Look,
for
example,
in
a
procured
materials
case.
It
can
so
happen
that
a
buyer
or
a
publisher
of
any
agreements
or
or
RFPs
for
that
matter,
it
would
be
okay
for
will
be
okay
with
them
publishing
the
information,
but
it
is
not
okay
for
the
suppliers
who
are
responding
to
those
buyers
to
be
revealing
their
identity.
B
As
to
what
their
infinite
as
to
what
they
responded
with
or
as
to
what
a
direct
communication
is
with
is
with
the
back
to
the
buyer,
but
at
the
same
time
we
need
to
make
sure
that
all
that
interaction
can
be
is
verifiably
provable.
Finally,
then
comes
in
to
respect
a
doing
another
layer
of
complexity.
B
But
this
I'll
flip
over
to
to
how
the
architecture
of
raddish
34
looks
and
as
we
go
along,
then
walk
through
some
of
the
key
components
of
the
architecture,
as
well
as
a
representational
workflow
as
to
how
we
applied
it
for
how
we
applied
all
the
sub
complex
to
system
to
system
interactions
as
applied
to
this
procurement
use
case
at
a
high
level.
The
workflow,
as
as
we
will
discuss
in
the
challenges
before
rag,
around
agreements,
business,
logic,
validation,
using
the
main
net
in
the
right
manner.
B
And
then
the
beginning
of
ongoing
procurement
processes
approach
is
called
wherein
the
purchase
order
has
to
be
issued
in
such
a
way
that
the
price
of
the
purchase
order
is
based
on
the
terms
mentioned
in
the
terms
agreed
upon
in
the
master
service
agreement
as
a
reference.
The
terms
that
we
are
using
at
this
point
is
a
very,
relatively
standardized:
a
volume
discount
structure.
B
What
I
mean
by
that
is
literally
standardized
volume,
disken
structure
problem
wherein
buyers
and
suppliers
typically
engage
into
some
sort
of
a
standardized
volume
discount
structure
where,
when
by
means
of
business
or
means
of
the
relationship,
the
discounts
are
applied
depending
on
the
volume
ordered
over
a
period
of
time.
So
we've
taken
that
as
a
term
static
term,
or
rather
a
term
that
needs
to
be
as
purchase.
Orders
are
issued,
so
every
subsequent
purchase
order
is
to
be
issued
based
on
the
volume
consumed
when
that
protocol.
B
So,
in
the
in
this
picture,
we
we
see
the
the
different
libraries
that
Jason
was
referring
to
something
we
started
off
in
in
terms
of
the
usage
in
the
raddest
34
implementation,
a
very
high-level
representation
or
function
or
a
functional
representation
of
what
the
different
services
are
in
radish.
It's
localized
infrastructure
there
in
B
it's
a
single
tenant
based
authorized
infrastructure
where
in
each
so
we're
in
each
micro
service
is,
is
continuous.
B
Oh
sorry,
each
micro
service
is
represented
by
these
circles
and
you
can
see
that
there
is
an
API
service
which
is
based
which
figures
graphed
your
line.
Please,
the
choice
of
graph
cable
is
mainly
so
that
it
could
enable
easier
UI
or
external
integration,
but
at
the
same
time
has
has
a
query
in
here
to
be
able
to
run
an
inflator
transformations
or
direct
before
interaction
with
any
form
of
web
services.
Then
we
have
the
API
in
itself:
religious,
a
lightweight
open-source,
queueing
language
called
Blue
Jays.
B
In
reality,
any
other
library
could
be
used,
but
for
the
sake
of
the
use
case,
and
for
the
sake
of
proving
the
principle
of
proving
the
principle
of
having
workflow
steps
that
could
be
modularized,
we've
used
a
lightweight
queueing
system
called
ghujiya,
which
is
run
by
the
buddhist
library,
inherently
the
bull
J's
library
also,
and
for
the
sake
of
the
bulliest
library.
We
also
use
Redis
DB
instance
to
capture
any
interaction
with
the
queuing
system.
B
The
queuing
system,
essentially
orchestrates
sitting
in
the
API
orchestrates
interaction
with
a
secured
messaging
service,
which
is
the
usage
where
we
used
whisper
and
as
a
PPI
zkp
service,
which
is
using
a
specific
form
of
a
toolkit
called
Socrates
which
deals
with
a
specific
form
of
ZK
stock
technology
under
the
sea
KP
family.
So
this
is
the
overall
architecture
and
MDE
all
the
contracts
that
we
deal
with
in
terms
of
business
interactions
or
any
interaction
to
the
main
net
are
captured
over
here
we
use
we
try
to
use
as
much
as
possible.
B
The
open
standards
are
there
in
order
to
know
in
order
to
leverage
the
existing
AI
piece
or
remove
the
existing
at
P.
So
to
speak
so
that
they
could
become
proper
standards
or
extensions
of
standards
that
could
be
relevant
for
different
industries
as
the
protocol
and
keeps
keeps
turning
on.
The
registrar
contract
here
in
reference
is
basically
a
standard
called
IRC,
18
20.
It
is
used
for
registering,
or
it's
basically
in
the
in
the
scope
of
radish
or
as
a
implements
it.
B
It's
a
contract
which
is
a
client
or
a
rapid,
slash
connector
to
NERC
18
20
global
registry.
So
any
new
contracts
that
are
added
are
registered
automatically
with
the
global
registry
for
easy
lookup,
and
also
to
maintain
some
form
of
interface
standards.
The
types
of
contracts
we
have
are
the
organization
registry
contract
more.
So
it's
more
like
a
phone
book
or
equal,
as
in
one
of
the
previous
slides
Jason
was
explaining.
We
had
seen
that
the
order
is
the
workflow
group
and
how
worker
groups
are
set
form
the
basis
of
how
business
relationships
are
formed.
B
So
we
identified
that
as
one
of
the
areas
that
needs
to
be
at
least
abstracted
out
and
represented
in
a
in
a
state
on
the
main
net,
and
that's
where
we
used
obviously
contract,
which
is
more
or
less
a
name
registry
contract.
The
standard
name
registry
contract
that
that
most
of
the
smart
contract
developers
are
aware
of.
But
this
our
collation
registry
contract
is
also
to
specify
a
certain
into
face
for
interacting
with
it
like
in,
as
as
extensions
could
be
made.
B
This
could
be
added
with
other
other
aspects
of
permissions
or
or
access
control
management
in
the
way,
or
even
wallet,
management
or
fund
management,
in
the
way
that
this
organization
registry
contract
acts,
but
in
turn
it's
also.
It's
also
integrated
with
the
global
we
are
seeing
20
contract.
Similarly,
we
use
the
pair
of
shield
and
verifier
contracts.
B
Finally,
we
have
a
token
registry
contract
in
place.
This
is
more
like
a
standard
token
interface.
It
could
be
any
RC
20.
It
could
be
in
RC
721
or
it
could
be
an
X
1155,
a
multi
token,
it's
basically
to
represent
any
form
of
any
form
of
tokens
or
train
form
of
business
assets
or
business
processes
that
have
monetary
value
and
all
the
other
and
satisfy
all
the
other
principles
or
best
practices
of
what
could
be
tokenized
or
what
should
be
tokenized
overall.
The
idea
is
that
this
is
as
we
developed
radish.
B
The
idea
was
that
there
are
components
in
there
that
are
reusable
and
that
could
be
extendable
to
other
use
cases
and
in
such
a
way,
a
baseline
protocol
is
the
creation
or
formation
of
such
practices
or
such
libraries
or
two
wickets
just
to
show
an
additional
reference.
It
is
to
just
indicate
that
the
extends
from
next
students
ability
point
of
view,
radish
ecosystem
or
the
baseline
protocol
extension
could
also
apply
to
any
hosted
environment
or
from
infrastructure
perspective,
but
also
from
a
functional
perspective
could
be
extended
as
well
I.
B
B
We
we
try
to
highlight
some
of
the
components
which
can
undergo
modification
and
which
could
be
ready
used
as
the
months
in
light,
like
green
other
ones,
which
more
like
modifications
or
extensions
that
could
be
built
in
like,
for
example,
and
there's
no
authentication
to
allow
for
custom,
authentication,
libraries
or
packages
to
be
used
for
authentication
authorization,
authentication,
authorization
circumstances
and
similarly,
a
queue
management
is
a
as
an
example
of
how
it
could
be
further
extended
in
the
same
manner.
This
could
be
extended
to
the
rest
of
the
stack.
B
B
In
terms
of
how
we
have
represented
this
or
how
we
have
implemented
this,
we
are
using
a
workflow
based
system
or
a
cube
based
system.
The
idea
is
that
when
buyer
issues,
an
RFP
is
it's
more
like
a
task
or
from
implement
a
interaction
point
of
view.
It's
a
task
of
any
API,
interacting
with
the
queuing
system
to
be
able
to
issue
as
issue
a
payload
and,
and
then
the
same
applies
to
the
response
event
from
the
supplier.
So
more
or
less.
B
This
job
of
issuing
an
RFP,
RFP
and
respond
and
receiving
a
response
is
a
composition
of
QE
q
tasks
that
go
from
intern,
a
interaction
with
whispered
to
be
able
to
inject
a
payload
whisper,
sending
the
payload
and
the
supplier
or
the
recipient
system,
detecting
the
payload
and
emitting
to
local
DB.
So
this
sort
of
task
or
the
overall
workflow
step,
is
something
that
we
have
broken
into
separate
tasks
in
terms
of
system
integrations
the
actual
service
invocation
and
the
acknowledgment
of
that
service
response
itself.
B
Similarly,
for
baseline,
be
a
facility
for
MSA
what
this
things
start
getting
somewhat
more
composed
this.
We
start
with
saying
that
we
want
to
be
able
to
sign
the
come
sign.
The
MSA
document,
where
commitment
is
basically
a
hash
of
the
document,
so
we
are
signing
the
particular
commitment
and
that
signed
commitment
is
again
sent
to
the
center.
The
supplier
supplier
on
receipt
does
the
same
process,
so
here
a
slight
modification
to
the
previous
previous
steps,
in
the
sense
that
now
there
is
a
signature
and
process
involved.
B
This
is
basically
is
basically
the
overall
process
flow
of,
or
some
a
system
from
a
system
sequence
diagram
perspective
as
johar.
We
have
model
this
overall
implementation
itself.
So
from
just
like
how
MSA
works
we
have,
you
can
extend
the
same
indication
even
towards
the
purchase
order
and
as
we
were
as
we
build
this,
we
identify
that
whether
several
components
in
this
that
that
that
stem
from
our
understanding
or
or
our
agreement
on
how
we
want
to
have
the
baseline
protocol
structured
model
from
point
of
view
of
extensibility
and
scalability
I'll.
Take
a
brief
pause.
A
Various
areas
of
information
or
libraries
of
information
from
from
you
know
the
contributors
guide
through
the
reference,
implementation,
res
34
and,
of
course,
all
of
the
information
related
to
the
baseline
protocol.
Most
importantly,
you
know,
because
this
is
this-
is
a
huge
area
of
opportunity
for
for
the
world's
to
really
come
together
and
really
build
out
a
unique
and
once
again
foreign
approach
to
leveraging
this
emerging
technology
that
we
really
rarely
even
discuss.
A
A
We
want
the
innovation,
we
want
the
participation
you
know
and
and
coming
from
an
area
where
I
know
my
colleague,
Dan
Norton,
who
sits
within
the
specification
on
the
specification
steering
committee
and,
of
course,
Karthik
who
we've
had
the
pleasure
of
hosting
here
today,
has
has
properly
explained
the
various
different
workflow
diagrams
and
architecture,
as
it
relates
to
the
reference
implementation,
Bradish
34.
He
sits
on
the
the
technical
steering
committee.
You
know
it's
very
important
to
all
of
the
above
participants
to
to
gather
your
feedback
to.
A
Of
course,
you
know
further
develop
and
enhance
this,
this
open
source
protocol
and,
of
course,
just
a
brief
plug
with
respect
to
envision
blockchain.
We
do
have
a
workshop
that
is
listed
in
the
Microsoft
Azure
marketplace.
You
can
you,
can
you
can
access
this
at?
You
know
the
link
below
or
if
you
just
went
to
the
azure
marketplace
and
just
search
for
envision
blockchain.
There
is
an
array
of
services
that
we
offer.
But
realistically
you
know
you
can
you
know
you
should
be
able
to
find
the
intro
to
the
baseline
protocol
workshop.
A
A
Tons
of
great
minds
have
put
a
lot
of
work
and
effort
into,
and
you
know,
making
making
this
happen
and
have
really
structured
the
governance
and
the
way
that
you
know
this.
This
whole
open-source
set
of
libraries
are
being
managed
I'm
going
to
leave
that
and
open
the
forum.
Now,
with
a
couple
minutes
left
for
people
to
really
dive
in
ask
whatever
questions
you
know,
I
think
it's
important
that
in
the
event
that
anybody
wants
to
see
the
demo,
you
know
we
can
stay,
maybe
a
couple
minutes
afterwards,
but
I
guess
in
the
interim.
C
Hey
guys
I
just
wanted
to
I
want
to
quickly
mention
that
there
was
a
question
that
came
into
the
Q&A
and
I'm,
just
gonna
repeat
this
over
here
for
for
the
purposes
of
the
recording,
because
it
may
not
be
able
to
go
ahead
and
be
put
into
the
chat.
But
but
essentially
you
know
if
anybody
wants
to
contribute-
and
they
may
not
know
exactly
what
should
they
contribute?
C
I
would
say
that
a
good
place
to
start
would
be
to
go
to
would
be
to
to
go
to
the
repo
and
to
open
up
the
issues
tab
and
you
could
see
where
the
current
areas
of
the
opportunities
are
and
then
just
to
call
some
out
and
I.
Think
Karthik
can
can
indefinitely
elaborate
on
this.
Some
of
the
areas
of
improvements
and
the
extensions
are
with
API
is
with
different,
zero
knowledge
proof
with
different
smart
contracts.
I
think
you
can
just
elaborate
on
that.
Just
a
little
bit,
Karthik.
B
So
if
there
are
any
improvements
like,
for
example,
if
the
B
there
is
a
decentralized
energy
management
approach
to
how
we
want
to
manage
organization
history,
that's
a
plug-in
that
could
work
well
with
it.
You
have
C
1820,
acting
as
an
umbrella
or
a
global
registry
of
sorts.
Similarly,
there
are
optimizations
that
can
happen
in
the
shield
contract
or
the
verified
contract,
or
even
for
that
matter,
how
many
shield
a
verifier
contracts?
Do
we
want
to
maintain
for
a
business
relationship?
B
Is
it
just
one
or
two
or
for
every
business
relationship,
or
is
it
one
big
one,
big
massive,
humble
or
registry
of
such
she'll
or
verified
contracts
itself?
So
there
are
those
are
areas
where
we
thought
that
it
will
be
against,
for
it
can
be
developed
a
little
more
in
terms
of
collaboration
with
the
community
and
also
have
community
experts
who
are.
B
It
will
actually
mean
that,
similarly,
for
said,
KP
your
services
we
have,
we
have
that
there
are
apart
from
Socrates
and
other
tools
which
may
be
more
of
interest
or
which
are
other
options
available
out
there
in
terms
of
how
they
work
and
how
they
operate,
and
also
in
terms
of
their
overall
performance
and
ease
of
use
as
well.
So
different
libraries,
how
different
tools
have
their
own
nuances
or
their
own
sort
of
quote,
unquote,
complications
in
terms
of
interaction,
but
the
way
we
try
to
build.
B
This
is
such
a
way
that,
as
long
as
we
can
build
that
as
as
good
out
of
box
restful
interface,
then
the
overall
system
doesn't
listen,
get
compromised
in
terms
of
the
system-to-system
sequence
of
evens
as
well.
So
the
areas
where
you
see
that
there
are
improvements
that
can
happen
in
Socrates.
Are
we?
B
How
do
we
modernized
those
circuits
in
such
a
way
that
we
can
replace
the
hashing
mechanisms
like
right
now?
We
are
doing
classic
shaft,
but
there
are
other
hashing
mechanisms
possible
and
then
there
is
also
the
aspect
of
security
and
performance,
so
in
terms
of
testing
it
out
or
even
improving
the
performance
of
the
overall
setup,
because
the
setup
itself
takes
some
time
and
depending
on
different
types
of
use
cases,
the
setup
times
may
vary.
B
So
there
is
some
amount
of
effort
that
could
be
beneficial
over
there
in
terms
of
either
puddle
computing
it
or
multi-threading
it,
or
even
for
that
matter,
having
it
as
a
good
hosting
service
that
could
be
managed
using
good
CI
systems
or
kubernetes
or
or
message
broker
orchestrations
of
usage
of
a
zero
service
disk.
So
those
are
the
two
broad
areas
and
I
think
these
are
like
the
these
are
some
things
that
we
are
trying
to
discuss.
B
C
All
right,
just
in
just
one
thing
to
mention
over
here
to
is
obviously
you
know.
You
may
see
that
there's
a
lot
of
quote-unquote
issues
that
are
in
the
repo
just
know
that
these
are
the
agenda
points
essentially
that
the
technical
steering
committee
and
what
the
specifications
steering
committee
these
are.
Essentially
what
the
agenda
points
are.
What
we're
going
to
be
discussing
so
definitely
feel
free
to
add,
contribute.
Ask
away.