►
From YouTube: Hyperledger In-depth: SIMBA Chain: Connect Supplier & DoD Blockchains for Transparent Part Tracking
Description
Blockchains have been around for more than ten years, and since 2015, a plethora of systems have been launched to target more flexible use cases. More recently, several enterprise blockchain systems, such as Consensys Quorum and Hyperledger Fabric, have been launched to make blockchain simpler to apply in complex organizational configurations. In this discussion, Hyperledger member SIMBA Chain will identify a specific Department of Defense use case, extrapolate requirements, and perform a thorough assessment of the different layers of the blockchain stack to identify the existing state of the art and undertake a gap analysis of the technology for this context. SIMBA Chain will describe a platform that meets many of these challenges and show how they architected, designed, and implemented a solution for this use case for deployment at NAVAIR connecting transactions from two separate blockchain systems, Consensys Quorum and Hyperledger Fabric and use a graph-based approach that preserves privacy while enabling full transparency across the military and supplier networks.
In the “Hyperledger In-depth: An hour with… .” series, Hyperledger members share learnings from their projects and try to answer all the hard questions about the pains of working with DLTs. It is not yet another webinar: participants will be encouraged to take part, come with prepared questions and voice opinions. Expect live demos and tutorials, stories from the battle field and hopefully some heated discussions. Let's get out of the zoom fatigue and engage to share experiences and build a stronger community.
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #HyperledgerGlobalForum2021 #Blockchain
A
All
right
welcome
everyone.
Thank
you
for
joining
us
for
the
hyperledger
in
depth
an
hour
with
our
member
simba
chain.
Today,
I'm
very
excited
about
today's
session.
We
have
three
wonderful,
actually,
four
wonderful
speakers
from
the
simba
chain
team
and
that
includes
anjon
roy
who's,
the
vp
of
simba
chain,
a
joel
nydic,
who
is
our
the
ceo
and
jeff
curtis,
who
is
the
vp
of
defense
and
supply
chain,
and
we
also
have
ian
taylor
from
summit
chain.
So
today,
they'll
be
talking
about
connecting
supplier
and
department
of
defense,
blockchains
for
transparent
part
tracking.
A
We
welcome
them
and
want
to
remind
everyone.
Some
housekeeping
rules,
number
one
is
that
all
linux
foundation,
hyperledger
meetings
and
events
are
covered
under
our
antitrust
policy.
So
please,
if
you
have
any
questions,
see
the
full
policy
on
the
hyperledger
or
the
linux
foundation
site,
but
just
you
know
for
for
a
reminder.
Please
don't
share
any
competitive
information
that
you
shouldn't
be
sharing.
A
Another
couple
reminders:
this
is
as
interactive
as
you're
gonna
get
with
the
simba
team.
Normally
we
would
see
each
other
in
person
at
an
event.
You'll
have
you,
they
would
give
a
talk
and
you
would
come
over
and
have
questions
and
meet
with
them
in
the
hallway,
but
we
have
an
opportunity
to
interact
with
each
other.
Raise
your
hand
if
you
have
questions
and
we
can
promote
you
to
speak.
A
If
you
have
any
questions,
you
can
also
pop
them
into
the
q,
a
which
is
just
a
regular
zoom
q,
a
and
in
the
chat
and
if
it
would
be
great
right
now,
we
have
a
lot
of
participants.
If
you
can
go
ahead
and
just
say
hello,
and
where
you
are
zooming
in
from
today,
that
would
be
great
to
see
kind
of
the
coverage
around
the
world.
So
without
further
ado,
I
am
going
to
send
it
over
to
the
simba
team.
C
Yeah,
thank
you
very
much
everyone
and
thank
you
daniella
for
for
inviting
us
in
the
hyperledger
community
here.
So
I'm
going
to
go
ahead
and
share
the
screen.
I
think
I
think
we
need
to
be
in
it
says:
host
disabled
screen
sharing.
I
wonder
if
it's
I
think
she
has
to
make
you.
I
think
I
have
to
be
made
a
host
or
a
panelist.
C
There
goes
there,
we
go
okay,
fabulous
well,
thank
you
very
much
and
you
know
what
we're
going
to
get
things
started,
and
you
know
with
this
this
project.
We
wanted
to
talk
about
and
also
a
paper
that
was
recently
published
and
we're
lucky
to
have
three
of
the
three
of
the
four
or
three
of
the
authors
and
co-authors
of
that
paper.
C
D
Yeah
yeah,
I
think
every
I'll
have
everybody
introduce
themselves.
So
my
name
is
joel
neidige,
I'm
the
ceo
of
simba
chain
co-founded
with
dr
ian
taylor
here
and
it's
been
very
exciting.
You
know
somebody
changed
started
to
build
out.
You
know
solutions
for
blockchain
and
make
it
really
simplistic
for
different
organizations,
and
we
found
a
great
place
in
government
that
is
needing
authenticity
and
auditability
and
traceability.
D
And
so
this
project
came
about
from
the
u.s
navy
and
currently
funded
by
navair,
and
it's
been
really
exciting.
It
came
out
of
a
paper
that
we've
been
working
on
with
the
university
of
notre
dame
boeing
and
navy
and
other
partners
like
itmco,
and
so
we'll
be
going
over
how
this
how
this
project
came
about,
what
we've
been
doing
in
it
so
far,
and
also
the
paper
that
is
very
much
more
extensive
than
we
can
go
over
in
a
webinar
setting.
D
But
it's
it's
there
we'll
show
the
link
where
you
can
go
and
look
at
that
paper.
That's
been
published
and
it's
been
peer
reviewed.
So
it's
pretty
it's
a
very
great
paper
to
understand
about
how
blockchain
can
be
used
in
supply
chain
and
even
in
a
government
setting
as
as
there's
a
lot
of
complexity
in
moving
parts
and
stakeholders
that
are
involved
that
need
to
know
and
have
that
verifiability.
E
B
Thanks
ian
I'm
jeff
curtis
I've
been
with
summit
chain
about
a
year
and
a
half,
I'm
the
vice
president
of
the
defense
and
supply
chain.
I
came
to
simba
after
about
33
years
at
dod,
about
30
at
the
defense
logistics
agency
and
in
the
last
three
and
a
half
four
years
with
the
office
of
the
secretary
of
defense,
anjin
joel
thanks.
C
Jeff,
great
yes,
so
hi
and
I'm
anja
roy
here
vice
president
simba
chain
and
well,
I'm
also
the
vice
chair
of
the
public
sector,
sig
working
group
here
at
the
hyperledger
foundation.
So
again,
this
is
related
to
that
because
at
least
is
semi-related
to
the
public
sector,
a
part
of
it.
So
this
is
certainly
exciting
and-
and
thank
you
all
for
coming,
so
you
know
we'll
get
right
into
some.
You
know
the
overall
goal
of
this
project.
You
know
joel
yeah,.
D
So
the
the
overall
goal
we
wanted
to
track
the
parts
that
were
coming
from
an
oem
so
that
there's
visibility
into
the
dod
supply
chain,
we've
all
been
through
covid.
We
understand
the
fragility
of
our
supply
chains
we
have
to.
We
have
to
now
come
together
and
realize
that
there's
vulnerabilities
in
our
supply
chains-
and
so
what's
what's
really
fantastic
about
this
project,
is
we
actually
started
it
before
covent?
So
we
actually
had
been
able
to
provide
a
lot
of
value,
as
code
was
happening
to
the
navy,
it
was
really
exciting.
D
The
me,
the
maintenance,
repair
and
operations
of
those
different
items
sharing
that
information
using
fabric
blockchain.
So
this
is,
you
know
this
is
obviously
a
hyperledger
fabric
webinar.
We
are
using
hyperledger
fabric
in
this
project
and
it's
been
a
great
open
source
tool
to
be
able
to
communicate
the
value
of
what
blockchain
or
distributed
ledger
technologies
can
provide
to
government
and
stakeholders
within
their
supply
chain.
D
So
then,
navair,
then,
would
receive
these
updates
to
gain
more
view
into
the
into
the
entire
end
process
so
that
they
can
make
decisions
and
have
a
better
collaborative
way
of
communicating
with
the
you
know,
oems
and
very
significant
partners
that
are
in
the
supply
chain.
So
the
parts
we're
tracking
are
tail
hooks
and
wings
from
the
f-18
aircraft.
So
you
can
go
to
the
next.
E
D
So
I'll
go
over
this
and
then
ian
feel
free
to
or
jeff
you
know
you
guys
can
hop
in
to
say
anything
that
I
might
be
missing,
but
the
maintenance,
repair
and
overhaul
is
about
the
replacement
and
test
measurements.
I'm
not
sure
you
know
everybody.
That's
on
this
call
so
I'll.
You
know.
If
some
of
you
may
I
completely
understand
this
you're,
you
have
a
manufacturing
background.
You
have
a
supply
chain
background,
but
we're
going
to
kind
of
dive
into
this
a
little
bit.
So
the
preventive
maintenance
are
tasks
that
are
scheduled
regularly.
D
So
they
you
know
it
could
be.
Regarding,
in
the
you
know,
updated
design
of
a
component
that
continues
to
fail.
It
could
be
in
the
equipment.
You
know
the
functioning.
How
well
is
it
functioning
and
and
providing
that
so
that
it's
ready?
You
know,
readiness
is
a
big
thing.
Sustainment
is
a
big
thing
within
the
military
and
we
have
to
be
ready
to
whatever
you
know
may
come
come
their
way,
so
the
corrective
maintenance
are
tasks
that
are
performed.
That
failure
occurs.
D
So
it's
like
fixing
of
an
overhaul
of
the
equipment,
the
machinery,
the
components
that
maybe
involve
that
assemblies
that
go
into
that,
so
it's
very
complex
assembly,
so
we're
digging
down
into
the
build
materials
of
these
items
and
providing
that
non-repeatability
the
predictive
maintenance.
So
now
we're
you
know
wondering
okay,
how
do
we
now
analyze?
You
know
if
something's
gonna,
if
the
failure
might
might
take
place,
how
many
flight
hours
does
this?
Have
you
know
what
what
are
those
different?
D
B
Now
I
just
want
to
weigh
in
a
little
bit.
I
appreciate
that
thanks
joel,
the
corrective
maintenance
becomes
more
and
more
of
a
challenge,
especially
as
a
lot
of
these
assets
are
older
than
we
ever
anticipated.
They
would
get
so
that
just
becomes
an
increasing
challenge
of
things.
Breaking
that
you
didn't
anticipate
would
break.
There,
may
not
be
a
supplier
base
and
so
on.
B
C
D
So
there
are
different
levels
of
the
mro
process
and-
and
this
is
all
detailed
in
the
in
the
white
paper
that
we
published,
like
I
said
in
elsevier-
the
blockchain
journal
so
and
I
know,
there's
a
lot
of
discussion
about
blockchain
distributed
technology
for
this
all
sense
of
purposes.
We're
using
these
for
this
for
this
session,
because
we
actually
have
connected
with
a
block.
We've
done
some
cross
communication
between
blockchains.
D
So
that's
why
we're
using
the
blockchain
and
dlt
interchangeably,
because
we've
done
connectivity
of
both
so
you'll
see
that
later
in
the
diagrams
of
what
we've
been
working
on
here.
So
there's
an
o
level
maintenance
that
occurs
in
the
organizational
level
of
the
you
know
of
the
navy,
and
you
know
it
could
be
a
single
maintenance
squadron
it's
responsible
for
the
parts
and
the
intermediary
eye
level.
Maintenance
occurs
when
it
is
specialized.
D
So
now
we're
looking
at
kind
of
like
the
you
know,
there
might
be
some
kind
consuming
diagnostics
that
are
involved
and
some
like
back.
You
know
there
might
be
a
job
shop,
that's
kind
of,
like
you
know,
back
in
the
back
corner
that
you
know
they're
working
they're,
specifically
good
at
like
welding
or
something
specific
like
that
or
one's
great
at
bearing
analysis
like
oh
this.
Bearing
is
about
to
fail
this
pin
in
this
tail
look,
is
you
know
things
like
that,
so
the
other
level
is
the
depot
level.
D
So
this
is
where
the
maintenance
occurs,
and
this
is
a
very
highly
specialized
off-site
repair,
so
they
might
even
be
into
the
fact
that
they
actually
have
the
diagnostic
equipment
that
is
specifically,
and
they
may
have
a
as
opposed
to
just
a
welder.
They
may
have
a
materials
engineer,
so
they
might
have
a
metal
or
just
or
something
like
specific.
That
is
like
they
are
like
really
almost
down
to
like
how
the
original
design
was
intended,
and
things
like
that.
So
that's
that's
kind
of
where
these
so
just
defining
these
different
levels.
D
So
people
understand
like
where
this
is
taking
place
and
you
can
start
seeing
like
wow.
This
is
where
smart
contracts-
and
you
know,
having
non-reputability
and
there's
a
lot
of
things
that
go
wrong
and
if
we
can't
immediately
like
pull
up
a
system
and
say
I
know
right
on
the
shadow
of
doubt
that
this
happened
at
this
date
and
it's
been
time
stamped
basically
notarized,
then
you
can
kind
of
start
seeing
how
communication
can
break
down.
D
So
you
can
even
imagine
in
large
organizations
when
you
know
boeing
or
navy
that
nobody
even
knows
you-
you
probably
are
working
on
systems
that
you
don't
even
know
who
the
other
person
on
the
other
end
is.
This
is
obviously
normal
in
a
lot
of
different
settings,
but
we
have
to
have
a
a
moment
of
trust
that,
like
you
know,
somebody's
getting
in
a
plane,
that's
you
know
gonna
fly.
D
I
need
to
know
that
this
the
maintenance
worker
had
signed
off
and
that
this
is
all
checked
and
everything's
great
so
having
those
capabilities
and
then
even
knowing
that
the
even
down
the
line
to
the
manufacturing
and
the
sub-tier
supply
chains
that
things
have
been
done
properly.
That's
that's
very
important.
So
next
slide
so
ian.
Do
you
want
to
talk
to
me
about
the
high-level
flow
just
briefly
and
then
maybe
a
little
about
the
paper.
E
Yeah,
I
just
posted
the
paper
actually
in
the
in
the
chat,
so
everybody
has
a
link
to
it
great
yeah
I
mean
from
the
previous
side.
This
gets
pretty
complicated,
but
essentially
this
is
how
the
high
level
flow
of
what
I
have
things
work.
So
we
created
a
28-page
document
that
describes
this
end-to-end
flow.
But
roughly
what
happens?
E
Is
you
know
using
those
things
from
the
last
slide
at
the
o
level,
so
at
the
the
carrier,
aircraft
carrier
they'll,
look
at
an
a
f-18
they'll
inspect
the
tail
hook,
for
example,
that'll
be
the
o
level.
If
they
can,
you
know
make
a
repair
there.
They
will,
if
they
don't
they'll,
take
it
to
the
eye
level.
The
eye
level
may
have
some.
You
know
equipment
to
be
able
to
repair
depending
on
what
what
goes
wrong.
E
If
they
can't
repair
it,
then
it
goes
to
the
d
level,
which
is
basically
the
repair
shops
across
the
country
like
frc,
south
west
and
southeast
and
so
forth.
So
so
the
the
part
then
will
get
transported
using
a
carrier
from
the
car
yeah
using
a
transport
carrier
from
the
aircraft
carrier
to
the
the
depot.
E
The
depot
will
go
through
that
process
of
overhauling
that
part
or
ordering
a
new
one,
and
then
that
will
go
back
to
the
carrier
and
it'll
be
installed
by
the
oi
level.
So
so
this
is
a
complex
process
and
it
touches
a
lot
of
data
systems.
So
we
went
through
the
entire
process.
End-To-End
analyzing,
all
the
data
systems
involved,
there's
about
30
different
data
systems
involved
in
this
entire
end-to-end
process,
with
200
plus
decision
making
points
across
that
process.
E
E
So
by
doing
that
analysis
and
going
for
this
process,
we
essentially
you
know,
found
the
data
we
needed,
rather
than
using
the
97.5
that
we
didn't
need
so
next
slide,
so
that
that's
the
kind
of
outline
of
the
problem
we
thought
we'd
go
through
and
give
some
slides
about
simultaneous
how
it
kind
of
addresses
these
sorts
of
problems.
So
this
is
sort
of
a
a
flow
of
how
simply
chain
is
used
and
essentially
on
the
on
the
left.
Here.
E
E
So
by
specifying
that
with
those
relationships,
we
actually
write
those
relationships
into
the
smart
contracts,
so
the
smart
contracts
are
kind
of
annotated,
so
they
have
relationships
explicitly
between
the
different
methods
in
the
smart
contracts
and
what
that
enables
us
to
do
on
the
back
end.
The
data
that
is
recorded
contains
those
relationships,
so
it
contains.
Essentially,
you
could
think
of
them.
As
you
know,
a
method
and
insulin
you,
for
example,
have
a
pointer
to
another
method
that
it
relates
to
so
or
in
fabric.
E
E
We
can
query
as
a
single
system,
but
we
can
have
off-chain
data
in
the
graph
database
and
we
can
also
have
on-chain
data
referenced
within
the
database
to
the
underlying
blockchain
and
we
can
bring
those
together
in
one
query
so
from
an
application.
They're
querying
a
system
where
some
of
that
is
tracked
and
some
of
it
is
not,
and
in
the
dod
we
will
put
you
know,
flight
critical
components
on
that.
E
You
know
as
part
of
they'll
be
the
ones
tracked
on
the
blockchain,
the
rest
of
the
components
that
may
be
involved
in
the
entire
process,
but
but
not
flight.
Critical,
maybe
off-chain,
for
example,
so
next
slide
so
simple
chain
that,
aside
from
the
the
modeling
we
do
on
the
input,
the
output.
These
are
the
various
components
in
the
system.
E
Just
to
give
you
an
idea
of
the
sort
of
the
the
I
guess
issues
we
address
with
with
symbol
chain
in
the
you
know
in
the
blockchain
kind
of
life
cycle,
so
I'll
just
go
through
this
real
quick.
So
at
the
center
there's
different
this
blockchain,
we
support
eight
different
blockchains
hyperledger
fabric.
We
support
that
natively
now,
so
we
map
from
these
smart
contract,
well
conceptual
smart
contract
models
directly
to
fabric
native.
E
A
little
bit
later
and
then
sort
of
on
the
front
end
of
this.
We
have
transaction
validation
and
resilience.
So
as
transactions
come
in,
we
validate
the
the
actual
content
as
opposed
to
kind
of
the
method
signature.
So
if
you
try-
and
you
know,
cut
a
massive
integer
into
a
unt,
you
know
that
something
that's
more
than
32
bits.
For
example,
it'll
it'll
complain
at
that
level,
rather
than
clogging
up
the
blockchain,
and
then
we
also
have
a
synchronous
workers
that
run
for
each
each
transaction
where
we
need
to
so.
E
In
other
words,
if
a
lot
of
transactions
come
in
and
the
blockchain
can't
keep
up
we'll
we'll
farm
out
these
workers
and
they
basically
monitor
the
transactions
until
they
get
a
receipt
and
then
those
are
exposed
through
very
simple
apis.
So
we
for
for
each
smart
contract,
we
spin
up
a
rest
interface
that
is
used
to
interact
with
the
smart
contracts
in
blockchain
and
so
from
a
from
an
application
standpoint.
E
You
just
write
into
a
rest,
api,
a
post
will
put
data
on
chain
and
a
query
will
search
the
the
data
or
on
chain
scope
by
that
particular
method
or
the
smart
contract,
and
on
the
back
end
we
have
a
transaction
cache.
This
essentially
every
transaction.
That
is,
as
has
a
receipt,
that's
recorded
on
chain.
We
cache
in
a
database
and
then
we
have
a
application
that
runs
all
of
the
time.
E
Checking
the
consistency
of
that
check,
cache
and
then,
when
querying
you
can
use
that
cache
or
you
can
go
directly
to
chain
depends
on.
You
know
which
mode
you
want
to
use,
but
using
the
cache
it
becomes
super
quick
and
then
we
can
search
using
graphql
or
graph
databases
or
or
we
can
search
using
direct
queries
to
those
endpoints
and
filtering.
E
Those
are
all
brought
together
in
the
dashboard
and
we
have
their
sdks
to
interact
with
all
this
stuff
and
we
also
support
transaction
subscriptions
which
I'll
touch
on
later
and
the
ability
to
off
chain
data.
So
you
can
add
a
file
to
a
transaction
when
you
put
it
on
chain
and
that
will
you
can
retrieve
that
later
and
that's
that
file
will
be
stored
in
a
an
off-chain
file
system
and
banned
on
chain
using
a
hash
code.
E
So
next
slide
and
of
course
we
have
auth
around
all
of
that
which,
for
the
in
the
dod
use
case,
we're
using
cat
cards
for
authorized
authentication
to
to
the
platform
so
yeah,
so
next
slide
yeah.
I
think
we
can
skip
this
one
so
just
to
kind
of
talk
about
the
model
I
touched
on
that
earlier.
Essentially,
we
have
assets
which
you
can
think
of
like
as
a
line
of
a
business
process
and
transactions
or
transitions.
We
call
them
a
verbs
or
relationships.
E
So
so
in
this
case
the
assets
would
be
a
wing
or
a
tail
hug
and
the
transitions
would
be.
You
know
the
status
from
boeing
about.
You
know
what
what
is
the
progress
between
zero
and
a
hundred
percent
of
that
wing
and
they
provided
that
information
in
real
time
and
that
they're
querying
their
local
systems
to
do
that
and
then
they're
they're,
adding
that
to
hyper
ledger
fabric
to
you
know
to
transmit
to
navair.
E
So
this
this
model
can
be
deployed
in
any
support.
Blockchain,
as
I
mentioned,
we
have
several
now
and
then
an
api
is
generated.
So
if
you
guess
the
next
slide,
we'll
show
how
that
kind
of
works.
The
the
graph
model
as
well.
This
will
come
in
later,
enables
us
to
do
these
versions
and
and
connect
to
different
blockchains.
E
I'm
going
to
show
an
example
of
that
later
so
next
slide,
and
so
once
you
define
your
model
and
have
the
you
know
generate
the
smart
contract
or
even
just
import
a
smart
contract-
that's
written
elsewhere,
you
know
by
through
using
remix
or
whatever
we
can
import
those
too,
and
we
go
through
this
process
so
that
the
process
of
you
know
trying
deploying
the
smart
contract
is
quite
simple.
Basically,
you
choose
the
blockchain
network.
You
want
to
deploy
it
on
in
this
case.
It's
ethereum
and
a
private
ethereum
network
called
circle
of
life.
E
And
then
the
next
phase
is:
do
you
want
off
chain
data
and
there's
several
sources
there
for
where
you
can
store
off
chain
data?
If
that
is
relevant
to
this
particular
application?
Next,
then,
you
choose
a
smart
contract.
You
want
to
deploy
an
assembly
enterprise
enterprise
platform.
You
actually
can
select
several
smart
contracts
here.
So
per
application
is
basically
a
container
for
multiple,
smart,
smart
contracts
that
each
have
rest
apis.
So
so
this
is
just
shoes,
choosing
a
container
demo
here
and
then
next
slide.
E
This
is
smart
contract
designer
just
to
give
you
a
feel
for
what
that
looks
like.
So
here
is
a
additive
manufacturing
example.
We
have
a
am
component,
the
red,
a
rectangle
box
there.
Those
are
the
assets
and
the
ellipses.
The
blue
ellipses
are
the
transitions,
so
you
can
kind
of
without
writing
any
code.
You
can
drag
and
drop
these
boxes
in
a
web
ui.
So
you
can
pick
up
a
component.
You
can
say:
okay,
the
component
needs
to
be
manufactured.
It's
delivered
it's
received
somewhere
and
it's
installed
in
the
case
of
mro.
E
That
would
be
the
kind
of
process,
but
a
component
in
an
manufacturing
example
that
actually
points
to
a
design,
an
stl
file
or
a
build
file
for
for
that
process,
which
can
be
updated.
So
just
by
you
know,
creating
this.
These
different
relationships
about
how
you
know
these
different
things
interact,
builds
up
a
model
of
how
what
the
data
looks
like,
and
it
gives
a
conceptual
model
about
how
that
data
should
be
crewed
after
the
fact
so
click
next,
each
of
these
boxes.
If
you
double
click
on
you
can
specify
the
parameters.
E
So
so
the
boxes
represent
methods,
for
example
in
the
parameters
represent.
You
know
the
payload
of
those
next
slide
click
next
and
then
you
click
a
button
at
the
bottom
and
that
auto
generates
the
the
code,
the
smart
contract
code.
This
is
this
is
an
example
in
solidity,
where
it
works
a
similar
way
for
fabric
generating
the
chain
code
and
then
next
slide,
okay,
so
in
the
back
to
the
nava
scenario.
E
So
what
do
we
do
here?
And
this
kind
of
bubbles
up
into
a
more
high-level
architecture
in
a
little
bit,
but
essentially
the
way
we're
connecting
the
oems
with
the
dod
is
through
two
separate
blockchains.
We
have
a
quorum.
In
fact,
we
have
three
blockchains
in
the
scenario
in
total
and
I'll
and
I'll
give
an
example
about
the
connectivity
later.
E
But
essentially
we
have
a
consensus,
quorum
blockchain
within
the
dod
that
is
basically
bringing
in
the
data
from
the
mro
process
we
described
earlier,
and
then
we
have
a
that
is
connected
to
you
know.
So.
The
dod
have
assembled
chain
platform
that
can
access
that
network,
for
example,
and
then
the
oem
network
is
hyperledger
fabric
so
that
we
have
that
fabric
network
set
up
now
and
that
can
that
is
providing
you
know.
E
Boeing
is
transacting
kind
of
data
onto
that
fabric
network
to
share
with
you
know
with
now
there,
so
those
two
blockchains
are
connected
through
a
single
instance
of
summer
chain,
so
what
whatnot
are
able
to
do
there
is
create
both
blockchains
simultaneously
and
the
way
they're
connected
is
essentially
through
a
po
order.
So
a
po
order,
ordering
like
a
tail,
herc
or
or
weighing,
for
example,
from
boeing,
is
tied
to
a
po
order
parameter.
E
E
We
we
started
off
when
we
initially
connected
with
boeing.
We
started
off
ingesting
csv
files
and
writing
those
to
hyperledger
fabric.
This
was
partly
due
to
you
know.
There
was
a
delay
in
gaining
that
connectivity
with
hyperledger
fabric,
getting
the
right
certain
permissions
from
the
boeing
side,
so
this
was
essentially
a
temporary
way
to
test
the
system.
So
what
happened?
E
E
So
now
we
can
do
this
without
using
these
csv
files
anymore,
but
this
was
kind
of
the
journey
we
went
through
in
this
in
this
project,
so
the
next
slide,
and
that
this
is
the
overall
kind
of
architecture
for
how
this
works.
So
essentially,
on
the
left
side.
Here
we
have
the
the
data
from
the
oems,
so
the
the
way
that
works
is
they
have
a
data
collector
component
that
queries
their
erp
systems
for
the
information
which
basically
is
extracting
the
status
of
a
particular.
E
You
know
particular
part,
for
example,
a
wing
can
take
months
to
make
for
under
progress,
but
there's
progress
within
that
time
frame.
So
from
navajo's
perspective
they
place
an
order
and
they
wait
until
that
order
is
filled
and
and
they
can
use.
You
know
historical
data
to
understand
roughly
when
that
happens,
but
then,
when
other
orders
come
in
within
bone,
for
example,
which
are
super
urgent,
that
might
delay
schedules,
and
so
this
this
information
changes
so
they're
querying
their
underlying
system
and
they're.
E
So
there's
you
know
that
goes
in.
It
goes
into
synchronous
transfer,
transaction
chain.
They
wait
for
the
receipt
when
it
kind
of
gets
catched.
So
all
of
that
process
goes
on
all
of
the
time
and
then
from
the
navair
systems.
They
have
a
similar
flow.
They
have
already
basically
multiple
multiple
levels
of
flows
that
collect
all
of
this
data
from
various
places
and
then
at
the
bottom.
These
are
the
the
structure
of
the
different,
you
know:
networks
and
the
oem.
E
The
potential
is
kind
of
coming
from
now
there
and
then
the
the
part
supplier
info
and
updates,
let's
cover
from
the
oems
so
next
slide-
and
this
is
the
two
smart
contracts
we
we
we
were
looking
at
using.
So
this
is
from
the
navajo
side,
looking
at
different
work
orders
and
connecting
data
through
the
mro
process,
which
then
bubbles
up
into
the
pos
that
go
out
of
the
system.
If
we
go
to
the
next
slide,
that
shows
kind
of
a
how
we
connected
this.
E
So
this
is
maybe
a
little
bit
hard
to
see,
but
essentially
what
this
is
showing
here.
I
tried
to
draw
a
line
between
these
two
networks.
So,
on
the
right
hand,
side
here
you've
got
the
hyperledger
fabric,
so
this
this
is
running
basically
on
the
oem
network
and
that's
providing
updates
from
the
oems
to
now
there
about
the
progress
of
of
the
particular
parts
and
then
what
we
we
did,
which
I
I
mentioned
the
third
blockchain
earlier-
and
we
we'd
written
a
a
parser
or
injester.
E
Maybe
for
publoc,
which
is
public
information
about
every
transaction.
A
oem
has
with
the
dod
there's
a
public
database.
It
turns
out
with
all
these
transactions
in
so
we
we
wrote
a
parser
for
those
for
another
project
and
ingested
information
from
public
public
about
the
status
of
these
various
parts,
and
we
we.
We
ran
that
process
to
extract
information
about
the
parts
that
were
involved
in
in
this
process
of
the
wings
and
the
tail
steps
and
so
forth.
So
we
pre-loaded
this
blockchain
with
this
information
and
we
connected
these
two
together.
E
So
we
connected
through
using
the
po
we
connected
these
two
together
and
what
that
enabled
us
to
give
is
to.
We
were
able
to
take
those
parts
and
automatically
lock
up
all
the
suppliers
for
those
parts
or
take
that
part
and
look
up
a
particular
supplier
for
that
part
and
even
get
the
zip
code
and
look
where,
where
that
supply
was.
So
all
this
public
information
really
enhanced
kind
of
the
the
graph
of
information
that
is
flowing
through
the
system.
E
And
then,
at
the
back
end,
we
have
these
search
and
access
apis
I'll.
Just
if
you
go
to
the
next
slide,
I'll
just
show
how
the
graphql
works.
So
this
is
our
graphql
interface
so
based
on
the
relationships
we
defined
earlier-
and
this
is
basically
showing
some
of
the
the
you
know-
the
interactions-
this
is
more
aligned
with
publoc,
but
but
the
general
idea
here
is,
you
know
we
have
a
supplier
part
here,
which
has
which
has
a
relationship
with
the
part
which
has
a
relationship
with
the
part
extra
detail.
E
It
also
has
a
relationship
with
the
supplier,
and
it
also
has
a
relationship
with
whether
there's
a
non-conforming
record
of
this
particular
part,
and
if
you,
the
system
we
we've
created
for
for
query
and
basically
enables
the
user
just
to
walk
through
that
process,
so
you
just
kind
of
like
click
on
the
data
and
click
on
the
the
you
know
the
data
set
you
want
to
extract
in
the
query.
So
here
I
click
supply.
E
Apart
on
the
left
here
and
the
green,
the
green
color,
there
is
saying
basically
those
are
the
things
that
are
selectable
from
here
here.
So
so
it's
giving
you
a
hint
about
where
you
can
go
in
the
graph
in
order
to
select
data,
so
those
are
selectable.
Now,
if
you
click
on
a
part
for
example,
then
that
makes
the
part
detail
also
selectable,
because
that
has
a
direct
relationship,
but
it
wasn't
selectable
from
the
supplier
part
directly.
So
you
can
use
this
process
to
go.
E
Walk
through
the
graph
select
the
journey
you
want
for
in
terms
of
the
query
you
want
and
on
the
right
hand
side
here,
you
can
select
the
parameters
from
those
those
transactions
that
you
want
to
extract,
and
then
you
can
also
add
filters.
So
you
can
do
things
like
you
know,
okay,
ex
query,
this
part
of
the
graph,
but
just
give
me
information
when
an
n
a
certain
thing
or
give
me
information.
E
If
a
you
know,
if
the
part
name
contains,
you
know
tail
hack,
for
example,
so
you
can
do
queries
like
that
and
that
extracts
the
data.
And
then,
when
you
quit
you,
you
hit
the
query
on
that
you'll
get
data
back.
So
if
you
go
to
the
next
slide,
the
data,
then
is
click
through
bold,
because
it's
a
structured
embedding
right.
E
It's
a
graphql
structure.
It's
not
a
true
graph
per
se,
but
in
this
example,
but
you
know,
the
first
level
gives
you
that
first
box
on
the
previous
slide,
so
that'll
give
you
all
the
supplier
parts
and
then
at
the
bottom
of
those
you'll
have
related
information
that
you
can
click
through.
So
in
this
case
you
click
through
to
the
part
in
this
in
the
second
level,
and
then
that's
the
part
information
there
and
then
you
click
again
for
the
part
detail,
and
that
goes
through
the
next
level
of
the
data
structure.
E
In
order,
so
you
can
see
the
detail
of
each
level.
So
this
is
the
kind
of
querying
that
the
you
know
that
is
capable
in
that
graph,
and
you
can
do
this
across,
like
I
said
across
those
two
or
three
blockchains
that
we're
connecting
together
and
retrieve
information
connect
data
across
those.
So
you
can
enhance
the
experience
and
then.
B
Next
slide
ian,
if
I
could,
for
you
just
very
simple
chart
the
one
of
the
things
that
from
what
he
was
talking
about
about
visualizing
when
we
talk
about
supply
chain
risk
management,
a
lot
of
times,
we
end
up
in
a
position
still
across
dod
and
across.
I
think
even
commercial
suppliers
of
pay
and
chase
you
buy
something
it
shows
up,
and
then
you
find
out
that
it's
not
what
you
wanted.
B
What
have
we
bought
from
them
in
the
past
has
any
been
have
any
been
non-conforming?
Where
do
they
come
from
as
this
grows?
You
know,
hopefully
you
have
multiple
upstream
suppliers.
You
know
up
to
you
know
supplier
number,
one.
Then
all
the
way
to
n
and
see
this
one
we've
never
had
a
problem
with
or
we
have
had
problems
with,
and
I
can
assure
you
every
time
you
use
your
credit
card
they're
doing
that
when
you
swipe
that
card.
B
B
This
gives
you
the
tools
to
start
to
head
in
that
direction,
and
it's
just
a
great
thing
that
you
know
I
did
many
years
at
dla
and
I
don't
know
where
they
are
with
this
now,
but
we
were
heading
towards
the
part
of
you
know.
Looking
at
item
supplier
and
price
is
the
price
way
out
of
line.
Is
this
an
item
that
has
a
history
of
challenges?
B
Is
the
supplier,
somebody
that
could
be
cage
hopping
or
is
sharing
an
address
with
nine
other
companies,
doing
lots
of
other
different
things
in
some
wyoming
suburb
which,
by
the
way
has
happened?
So
this
is
a
way
to
get
in
front
of
things
and
to
visualize
something
that
otherwise
you'd
just
be
looking
at
very
bland
data
and
there's
a
good
chance.
You
would
miss
something
that
was
there,
but
this
allows
you
to
take
that
and
really
turn
it
into
something.
B
That
would
be
much
more
useful
kind
of
turning
data
into
information,
which
is
something
before
I
see
anja
and
joey
and
ray
talk.
They've
heard
me
say
so
many
times
that
so
many
of
us
are
data
rich
and
information
poor.
Can
we
turn
it
into
information,
and
that
leads
us
in
that
direction,
and
I
will
pause
there
and
take
a
breath
yeah.
D
D
You
will
have
now
a
basically
an
oracle
service
that
you
can
know
and
there
people
can
come
to
complete
agreement
and
consensus
on
items
because,
right
now
it's
there's
it's
it's
continually
adjudication.
Just
like
jeff
spent,
probably
this
majority
of
his
career
adjudicating.
You
know
more
majority
of
items.
You
know
that
just
were
problem
childs
and
different
things
like
that.
So
anyway,
going
yeah,
jeff
people
want
to
say
something.
B
No,
I
was
just
saying
you
mentioned
the
adjudication
by
the
time
I
ended
my
career
and
I
was
in
a
pretty
senior
position,
but
my
lives
were
just
kind
of
out
or
my
days
were
kind
of
hellish,
because
by
the
time
anything
came
to
me,
nobody
had
solved
it
and
they
had
tried.
So
I
only
got
things
and
you,
as
ceo
of
the
company,
I'm
sure,
are
going
to
are
going
through
the
same
thing
by
the
time
they
get
to
you
or
to
me,
or
to
whomever
other
folks
have
tried.
B
E
Okay,
yeah,
I
think.
Well,
if
you
go
to
the
previous
slide,
this
is
just
an
example
of
a
graph
using
the
same
data.
So
this
is
our
graph
we're
actually
using
neo4j
from
a
technical
standpoint,
but
this
enables
us
to
essentially
create
a
graph
of
the
data
which
can,
in
the
case
of
supply
chain.
You
know
graph
enables
you
to
represent
a
supplier
and
then
have
a
supplier
point
to
another.
E
You
know
this
graph
and
populate
it
in
a
simplified
user
interface
and
where
you
know
we're
using
kind
of
simple
user
interfaces,
essentially
at
the
side
of
things
and
then
the
next
slide,
just
as
kind
of
really
the
last
thing
to
touch
on
is
is
the
subscription.
So
one
of
the
one
of
the
parts
of
the
tool,
the
sim
chain,
enterprise
platform
that
I
touched
on
earlier,
was
the
ability
to
do
subscriptions.
E
C
E
Interface
to
that,
so
you
know
it's
a
very
similar
idea.
You
choose
basically
what
you
want
to
what
you
want
to
filter
on
and
you
choose
the
conditions
about
how
that
happens,
and
then
you
click
subscribe
and
then
that
you
just
get
notifications
as
data
that
meets
that
those
conditions
come
into
the
network.
B
Not
surprisingly,
I
had
another
comment.
You
know
every
time
when
ian
was
walking
through
this,
there
were
so
many
pieces
of
information
flowing
in
so
many
directions,
and
so
many
literal
physical
parts
moving
around
every
one
of
those
tends
to
be
a
chance
for
a
hiccup
and
for
things
to
become
unmatched,
but
with
blockchain
hyperledger
you're
talking
immutability,
things
are
going
to
match,
and
you
know
back
to
one
of
my
catchphrases
that
I
learned
at
dla
was
single
version
of
the
truth.
B
I'm
presuming
we
have
some
folks
on
here
from
dod.
You
know
we
all
lived
the
dream
and
continued
to
do
so
of
reaching
financial
auditability,
and
that
doesn't
mean
we
were
wasting
money
or
that
we
were
losing
stuff.
It
just
means
that
the
books
didn't
necessarily
balance
the
way
they
should,
according
to
generally
accepted
accounting
principles.
B
This
can
help
go
a
long
way
towards
making
sure
things
line
up.
There
is
one
version
of
the
truth,
which
is
the
right
number
of
versions
of
the
truth,
and
sometimes
you
know
you
can
look
at
medical
records
within
dod.
You
can
look
at
book
to
floor
and
florida
book
in
depot
systems
you're
going
to
have
mismatches,
and
this
will
help
reduce
that
a
lot
significantly
so
I'll
pause.
There.
C
Thank
you,
jeff,
and
you
know
I
know:
we've
had
some
good
engagement,
the
chat
box
great
to
see
everyone
from
all
over
the
world.
I
see
california,
munich,
germany
represented,
but
we
do
have
a
question
from
nicholas
and
and
thank
you
and
for
the
the
feedback
there.
This
is
we're
glad
that
you
think
this
is
a
great
presentation.
A
question
nicholas
does
ask,
is
you
know
what
are
the
tangible
benefits?
You
know
in
terms
of
dollar
savings
or
department
of
defense
boeing,
other
vendors?
C
You
know
it
may
not
always
be
about
dollars.
Like
you
said
jeff,
you
know
you
know
it's,
but
it
may
be
about
may
be
about
availability.
You
know,
which
is
a
type
of
risk.
It
may
be
about
auditability.
You
know,
which
you
know
the
dod.
You
know
struggles
with,
but
but
tries
to
get
a
little
better
and
that's
obviously
kind
of
worms.
C
D
D
I
have
an
article
coming
out
here
soon
about
this
in
one
of
the
manufacturing
magazines,
but
about
15
of
items
total
scrap
and
what
we've
been
able
to
determine
is
we
can
improve
that,
if
not
eliminate
a
lot
of
majority
of
it,
because
some
of
it
is
actually
due
to
non
traceability.
They
actually
throw
things
away
because
they
can't
actually
show
provenance
of
where
it
came
from.
They
literally
just
throw
it
away,
and
so
you
know
you
have
a
heat
treat
coat
that
just
didn't
get
put
on
previous
at
the
heat
tree.
D
Well,
there's
a
lot
of
things
we
can
do
to
to
type
purchase,
orders,
geolocation
and
identification
and
to
to
find
out
when
that
heat
code
that
heat
lot
came
from.
So
that's
just
an
example
like
a
heat-treated
component
material
example
and
and
providing
a
immutable
and
non-reputable
like
hyperledger
fabric
can
provide
a
connectivity
with
your
supply
chain.
D
You
can
then
immediately
be
able
to
verify
and
validate
the
query
and
find
out
where
this,
where
these
items
came
from,
so
that's
the
value
that
we
can
bring
and
I
think
about
40
of
there's
the
just.
To
give
an
example,
the
the
tail
hooks
about
you
know
40
000,
plus,
potentially
with
combining
of
the
of
the
components
and
about
forty
thousand
dollars
worth
of
that
item.
D
Forty
percent
of
it's
like
paperwork.
So
as
we
get
to
more
of
a
digital
world
and
provide
a
more
digital
footprint
capability,
queryability
instant,
real-time
notifications,
you
can
really
start
saving.
You
know
a
lot
of
dollars
on
those
different
things
so
about
at
the
end
of
this
project.
I'm
sure
we'll
have
a
very
detailed
thing,
but
I
was
just
trying
to
give
this
an
anecdotal
and
then
onboarding
that
government
customer.
Obviously
this
takes
large
partnerships
a
lot
of
time.
D
B
B
D
C
C
It's
not
if,
if
the
question
was
more
about
the
technology,
the
onboarding
of
new
vendors
or
new
network
participants,
is
it's
a
very
different
conversation
if
all
the,
if
all
the
contracts
and
the
bureaucracy
and
the
human
decisions
are,
are
abstracted
the
way
which
of
course
is
not
reality,
but
if
they
were
the
actual,
you
know
the
the
the
the
actual
technical
plumbing
is
pretty
fast
right.
You.
D
Know,
yeah
and
the
dod
is
fast
moving
towards
the
zero
trust
infrastructure
so
that
we
can
not.
You
know
these
centralized
certs
and
different
things
like
that
are
causing
very
much
problems,
especially
so
to
get
to
more
of
a
zero
trust
capability,
open
source
where
it's
very
transparent,
hyperledger
fabric,
linux
foundation,
you
know
and
all
the
other
you
know
hyperledger
sawtooth.
We
support
that
too,
and
hyperledger
burrow
as
ian
also
described
so
just
different
capabilities
and
and
kind
of
bringing
partners
together.
But
yes,
definitely,
the
onboarding
can
be
fast.
D
D
Different
things,
especially
if
you're
going
to
rdt
network,
that's
thought
more
complex,
so
it's
a
little
bit
long
time
for
their
risk
management
framework
and
atos
that
have
to
get
processed
so
to
try
and
move
towards
more
cloud
infrastructures.
Obviously
a
lot
faster
onboarding.
So
I
think
we
have
another
question:
okay,.
C
A
Yeah
just
a
reminder
to
everyone:
if
you
want
to
ask
questions,
please
go
ahead,
you
can
put
in
the
chat,
you
can
put
it
in
the
q
a
or
just
raise
your
hand
and
I'll
go
ahead
and
promote
you
to
permit
talking.
So
it
would
be
great.
You
have
an
opportunity
to
ask
some
questions.
I
do
have
a
question
and
this
is
something
that
we've
been
getting
very
often
specific
to
consensus
quorum.
D
Yeah
and
then
the
b
su
is
java
based,
I
believe
I
think
yes
yeah,
so
they
and
consensus
obviously
we're
very
close
to
consensus.
So
we
use
we're
a
great
partner
of
ours
because
we
use
our
technology
and
they
are
no
they're
cl
they're
moving.
I
know
they're
moving.
The
idea
is
to
continue
to
merge
those
kind
of
more
and
more
together
to
kind
of
build
this
capability,
where
bisu
and
the
go
consensus
quorum
can
continue
to
come
together.
D
A
D
So
the
dod
is
continuing
to
research.
Obviously
they're,
not
the
fastest,
adapt
adopters
of
the
technology,
but
they
continue
to
provide.
You
know
build
out
specific
solutions.
This
is
what
they're
looking
for,
and
I
think
eventually
there'll
be
mandates
for
different
blockchain
networks
like
I'm.
What
we
envision
is
that
department
of
defense
within
navy
air
force
marines
just
like
there,
a
lot
of
them
have
multiple
different
cloud.
D
Multi-Cloud,
there's
gonna
be
multi-blockchain,
so
multi-cloud,
you
know,
there's
not
just
like
we've
seen
with
jedi
there's
not
to
be
like
okay,
one
group's
going
to
have
even
an
open
source
world
is
going
to
have
one
capability.
So
there's
going
to
be
multi-cloud
capabilities,
we
have
lots
of
collaboration
and
we
know
that
we
think
the
partner
of
commerce
will
have
something
department
of
energy.
We'll
have
something
treasury
we're
seeing
this
with
central
bank
digital
currencies.
D
So
all
these
different
things-
and
I
think
there
will
be
mandates
coming
out-
and
you
know,
summit
chains
agnostic.
We
are
an
agnostic
platform.
We
just
connect
to
different
we're
an
api
layer,
so
we
just
utilize
we're
not
at
the
protocol
level.
We,
what
you
know,
hyperledger
fabric
figure
out
the
protocol
items
and
we
just
connect
and
help
you
know
build
applications.
So
that's
our
that's
our
mission
to
make
it
easy.
Yeah.
C
C
What
we
can
probably
assume
is
that
you
know
certainly
interoperability
and
that's
that
could
mean
a
hundred
different
things,
there's
so
many
gradations
of
interoperability,
but
to
the
extent
that
there
is
some
type
of
you
know,
because
then
it
goes
to
the
the
spirit
of
kind
of
open
solutions
versus
kind
of
wall,
gardens
and
closed
solutions.
So,
to
the
extent
that
there
can
be
interoperability
to
some
greater
degree,
one
would
think
that
that
would
be
seen
more
favorably
by
this
particular
institution.
You
know
or
any
government
institution.
I.
D
Requirements
that
have
to
be
stood
up,
containerized
requirements
and
a
lot
of
that
is
the
continuous
authority
to
operate
authority
to
operate
risk
management
framework.
All
that
has
to
be
done.
We
are.
We
are
working
very
hard
to
be
able
to
publish
what
we've
done.
We
don't
have
all
that
information
allowed
to
be
shared,
but
we
hope
to
publish
that
to
the
community,
so
everybody
can
now
go
yeah.
C
D
This
is
how
I
do
a
stig
hyperledger
fabric
implementation.
You
know
what
not
so
that's
that's.
Our
goal
is
like
keep
continue
to
give
back
to
the
community.
We've
done
some
updates
on
showing
users
how
to
do
hyper,
ledger,
evm,
2.1
installations
and
helping
like
writing
scripts
and
making
that
a
lot
more
manageable,
different
things
like
that.
So
we
we
continue
to
provide
that
open
source.
You
know
we
as
much
as
we
can.
A
C
C
And
some
of
the
hardest
was
the
approval,
and
ian
can
speak
to
that.
Well,
if
he,
if
he
wants
to
it's,
he
had
to
do
a
lot
of
that
approving
and
re-editing,
so
we're
certainly
on
the
gas
pedal
trying
to
get
as
much
of
this
out
as
possible.
So
please
do
check
out
that
paper,
because
that
was
that
went
through
a
lot
of
approvals
to
get
it
and
and
we're
trying
to
you
know,
shed
a
light
and
make
as
much
of
this
public
as
we
can
and.
D
B
D
A
C
C
You
can
get
me
a
gmail
as
well,
but
cynthiachain.com
and
I'm
I'm
one
of
the
hyper
liaisons
here
at
simba
chain.
So
you're
welcome
to
reach
out
to
me-
and
I
can
put
you
in
touch
with
the
right
person
at
zimba
chain
that
that
that
you
can
be
speaking
with
and
certainly
daniella
has.
The
rest
of
the
community
here
has
has
my
contact
information
and
we
talk
all
the
time
so.
D
C
A
I
want
to
thank
the
simba
chain
team
today
for
this
presentation,
for
sharing
the
work
and,
very
importantly,
and
joel
just
mentioned
this-
the
contributions
that
simba
chain
has
done
back
into
the
community
right,
it's
not
just
about
using
the
code,
it's
about
sharing
the
opportunity,
you
know
code
and
bugs
and
stuff
like
that.
So
we
really
appreciate
your
your
your
contributions
to
our
open
source
community
as
well.
So
I
want
to
thank
everyone
for
attending
today.
A
A
So
once
again
make
sure
that
you
check
out
the
global
forum,
we
do
have
some
great
content
from
our
july
global
public
conference
with
lots
of
supply
chain
use
cases
as
well
as
others,
to
take
a
look
at
public
sector
et
cetera.
So
please
do
look
at
those
sessions
that
are
available
online
and,
as
always,
please
get
involved.
There's
lots
of
ways
to
get
involved
within
our
hyperledger
community.
A
The
special
interest
groups,
the
working
groups,
the
technical
projects
themselves,
the
meetup
community
is
strong
and
we
are
starting
to
see
some
meetup
communities
getting
together
in
person,
so
hopefully
we'll
be
seeing
you
all
in
person
as
well
at
events
and
meetups
around
the
globe.
So
once
again,
thank
you
for
watching
this
will
be
posted
on
youtube,
as
well
as
on
our
website
and
we'll
provide
additional
details
for
everyone
via
email.
So,
thanks
again
and
have
a
wonderful
day.