►
From YouTube: Hyperledger Member Webinar: Tackling Scalability and Moving into Production – Simbachain
Description
While DLTs are no longer a mystery to most enterprises, we still have not yet figured out how to build and scale production grade projects. It is easy to build a POC, but moving to the real world with real customers is a whole different issue. Moreover, the young age of the DLT space shows in lack of tooling. Hyperledger Member, Simbachain, created SIMBA: Smart Contract as a Service and Blockchain Innovation Platform to rapidly design, build and scale production DLT applications using Hyperledger Fabric. The centerpiece of the presentation will include a live demo.
Slides: https://www.hyperledger.org/wp-content/uploads/2020/10/Webinar-Hyperledger-Simba_v2.pdf
----
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 #Blockchain
A
We
have
a
quite
a
bit
to
cover
and
we
also
want
to
leave
some
time
at
the
end
for
questions
and
still
finish
before
the
top
of
the
top
of
the
next
hour.
We
know
that
your
time
is
valuable
and
you
probably
spend
a
lot
of
time
on
zoom
and
your
computers
nowadays,
given
the
state
of
the
world,
and
so
we
appreciate
you
prioritizing
this.
I
should
also
state
that
simba
chain
is
very,
very
thrilled
to
be
part
of
this
community.
A
A
Our
new
enterprise
release
that
that
just
came
out
and
adam's
going
to
speak
then,
specifically
and
to
and
show
you
specific
demonstrate,
the
hyperledger
portion
of
the
platform,
an
example
as
well
as
how
our
graph-based
approach
elucidates
that
further
and
and
further
extends
our
traditional
approach.
So
taking
a
breath
here
and
you
just
you
know,
if
we
look
at
blockchain
and
I'm
using
blockchain
and
dlt
technologies
here
interchangeably-
I
I
know,
I've
noticed
one
thing
just
being
part
of
the
community.
A
That
dlt
is
is
definitely
more
in
favor
as
a
terminology
within
hyperledger.
So
these
these
kind
of
multi-party
systems,
so
to
speak,
the
ecosystem
has
many
moving
parts
and
they're.
Subject:
kind
of
hyper
specializations
with
you
know,
even
within
the
community,
because
because,
if
you
think
about
blockchain,
you
know
where
and
you
think
about
dlt,
you
know
you're
mixing
in
cryptography.
You're
mixing
in
you
know,
consensus,
algorithms,
decentralized
databases.
A
That
challenge
you
know,
but
on
the
other
hand,
being
able
to
you,
know
utilize
and
optimize
and
coordinate
across
these
component
parts.
You
know
is
critical
for
sex
success,
so
you
know
yes,
you've
got
hyper
specializations
that
presents
a
challenge,
but
if
you're
going
to
get
the
real
value
out
of
it,
you
need
to
be
able
to
bring
these.
A
You
know
these
component
parts
and
these
hyper-specialized
specializations
and
hyper
specialists
together
and
and
that's
where
the
real
kind
of
you
know
return,
you
know
return
on
investment
is
and
to
you
know,
if
you're
implementing
dlt
technologies
and
then
on
top
of
that
you
know,
blockchain
is
is
complicated.
You
know,
as
we
said,
you
know,
you've
got
just
a
few
things
that
a
business
needs
to
understand.
You've
got
libraries,
you've
got
you've,
got
wallets
course,
cryptography
the
networks
themselves.
A
You
know,
there's
so
much
focus
on
the
network
and
then
on
top
of
that
off
chaining
of
off
chaining
of
file
systems.
That's
a
very
key
part.
You
know,
particularly
if
you're
talking
about
smart
contract
based
and
more
complex
implementations
and,
of
course,
smart
contracts
themselves-
and
this
is
just
you
know,
and
even
this
is
just
a
snapshot
of
what
you
need
to
understand.
So
so
what
do
you
have?
You
have
a
lot
of
moving
parts.
A
You
have
a
a
discipline
that
is
prone
to
hyper-specialization
and,
on
top
of
that,
being
able
to
coordinate
across
those
moving
parts
and
and
leverage
your
personnel
and
and
knowledge
across.
These
specializations
is
really
key
to
success.
So
that's
that
that's
certainly
a
challenge
if
you're
dealing
with
dlt
technologies,
particularly
if
you're
talking
about
production
applications
and
really
going
into
the
real
world
and
changing
that
as
opposed
to
you,
know
an
isolated
poc.
You
know
so
a
little
bit
of
history
of
us.
You
know
in
an
introduction
to
simba.
A
It
came
out
of
a
darpa
phase,
one
sbir
contract
that
was
awarded
to
two
entities
in
northern
indiana
atemco,
a
manufacturing
firm,
that's
been
around
since
the
1950s.
That's
always
been
on
the
kind
of
a
leading
edge
when
it
came
to
cad
and
other
digital
tools,
bringing
digital
into
manufacturing,
they've
been
doing
it
for
decades
and
then
notre
dame's
center
for
research
computing.
A
So
they
came
together
and
they
applied
for
this
darpa
sbir,
small
business
innovation,
research
contract
with
the
the
famed
institute
darpa
that
many
of
you
may
be
familiar
with.
They
do
really
a
lot
of
the
primary
basic
research
going
back
to
the
1950s.
I
mean
the
internet
itself
came
out
of
darpa
or
the
old
arpanet
that
some
of
you
may
be
familiar
with.
A
In
the
you
know,
the
first
computer
switch
and
then
more
recently
autonomous
vehicles
and
and
a
lot
of
other
research,
so
darpa
came
out
with
what
was
one
of
their
first,
either
first
or
second
ever
blockchain
solicitations
and
this
team
came
together,
competed
for
it
and
won
it,
and
it
was
developed
a
secure,
unhackable,
messaging
and
transaction
platform
for
the
for
the
us
military
and
one
of
the
lessons
that
came
out
of
that
that
experience
was.
This
is
really
hard
to
do.
A
You
know
the
team
kind
of
backward
engineered,
like
the
conclusions
that
we
kind
of
came
up
with
there,
and
I
shared
with
you
in
the
last
few
slides
is-
is
born
from
not
just
theory
not
just
reading
others.
Research,
although
that's
part
of
it,
but
really
living
it
and
experiencing
it,
and
in
experiencing
it
from
day
one
from
being
able
to
develop
something
like
this,
and
this
is
a
time
that
there
were
no
tools
you,
you
know
you,
you
had
a
pretty
much,
or
at
least
no
very
little
in
the
way
of
blockchain
specific
tools.
A
So
they
had
to
do
built
this
from
scratch
and
the
conclusion
was
this
is
hard
and
it
can
be
easier
and
it
should
be
easier
because
you're
spending
a
lot
of
time,
just
building
kind
of
basic
component
blocks.
If
we
can
just
give
people
that
give
people
a
leg
up,
then
that's
going
to
be
that
then
that's
going
to
you
know,
really
increase
their
chance
of
chance
of
success
and
be
able
to
kind
of
lower
the
barrier
to
adoption.
So
you
know,
since
that
time
the
company's
grown.
A
You
know
we
do
quite
a
bit
in
government
contracts
do
work.
On
the
you
know:
commercial
side.
Our
community
also
includes
individual
developers.
You
know
we
have
a
freemium
line
and
enterprise
sectors
and
and
the
education
sector
as
well,
is
a
major
focus
area.
But
in
all
these
cases,
what
we
found
in
all
these
communities,
whether
it's
governments,
whether
it's,
whether
it's
individual
developers,
whether
it's
universities
or
there's
traditional
commercial
enterprises-
is
you
know
the
the
is
the
importance
of
of
simplification,
the
importance
of
being
being
able
to
do
that.
A
A
We
develop
a
smart
contract
around
that
or
the
intelligence
that
can
be
shared
kind
of
across
the
network,
and
then
we
generate
a
rest-based
api
which
can
then
connect
to
your
connect
to
the
network
and
connect
to
the
off
chain,
and
that's
the
real
kind
of
that's
this
and
it's
clearly
it's
more
complicated
than
that,
but
the
if
we
were
to
really
boil
it
down
to
take
the
most
simplified
explanation
of
our
simplified
approach.
That's
really
it!
And
why
do
we
take
this
api
based
approach
because
we
see
the
api
this
dynamic
api?
A
That's
very
contextual,
very
use
case
specific,
as
kind
of
the
efficient
point.
Sometimes
we
call
it
the
pareto
optimus
optimize
point
where
it's
it's
on
that
right
point
between
customization
and
and
kind
of
turnkey.
You
know
if
something
is
too
turnkey
and
you're
talking
about
real
kind
of
no
code
solutions.
A
The
problem
there
is
that
you
have
to
for
they're,
not
custom.
You
know,
and
on
top
of
that
you're
bringing
a
lot
a
lot
of
contextual.
You
have
to
bring
a
lot
of
complexity
into
the
system.
At
that
point,
you
know
learning
you
know.
No
code
tools
can
be
like
incredibly
complicated
if,
if
they're
going
to
be
robust,
on
the
other
hand,
if
you're
starting
from
scratch,
then
well
you're
starting
from
scratch,
and
then
at
that
point
you
know
you're
not
getting
getting
the
efficiency
gains
and
lowering
the
barriers
to
adoption.
A
Those
who
are
maybe
maybe
adjacent
to
the
technology
sector
of
technology
roles
getting
those
who
are
subject
matter,
experts
getting
them
into
the
the
development
process,
particularly
when
you're
talking
about
dlt
systems,
multi-party
systems
with
a
lot
of
moving
parts.
It's
very
important
that
we're
able
to
democratize
through
education
and
get
those
who
are
outside
of
kind
of
the
the
more
traditional
technology
disciplines
into
the
process.
So
democratization
is
key.
Then,
of
course,
we
know
we
got
to
accelerate
prototypes.
A
You
know,
because
at
the
end
of
the
day
you
know,
if
you're,
if
you're,
if
you're
kind
of
doing
blue
sky
or
leading
edge
kind
of
work,
you
can,
you
can
only
theorize.
So
far
at
some
point,
you
have
to
build
something
ideally
quickly
at
at
at
a
at
a
at
a
reasonable
cost
and
to
see
how
it
works.
You
know
you
know,
because,
because
the
end
of
it,
you
know
you
need
the
data,
you
you
don't
know.
A
You're
operating
in
a
cloud
of
uncertainty
and
the
only
way
to
to
bring
certainty
to
the
cloud
of
uncertainty
is
to
go
out
and
do
something
and
try
it
and
learn
from
it
and
then
and
then
iterate
on
it.
So
you
got
to
accelerate.
Then
you
got
to
connect
to
the
broader
ecosystem.
You
know
because
we're
not
doing
dlt
in
a
vacuum
and-
and
I
think
this
is
where
the
the
the
hyperledger
community
will
understand.
You
know
most
of
this
community.
A
A
If
you
look
at
the
you
know,
tradition
the
traditional
technology,
you
know
hype
cycle,
you
know
you
know
I
like
to
say
you
know,
maybe
practical
revolutionaries
or
another
term
I
heard
was
revolutionaries
revolutionaries
that
actually
work
and
so
hyper
ledger
is
out
of
all
those
out
of
all
the
kind
of
dlt
communities.
I
think
will
appreciate
our
approach
and-
and
this
approach
is
a
suggestion
of
lowering
the
barriers
to
entry
accelerating
connecting
with
the
broader
system
accepting
the
world,
as
is,
but
then
scaling
within
that
and
then
changing.
A
B
So
so
with
that
being
said,
web
one,
you
know
it
was
all
about
posting
data.
Web
2
was
more
about
posting
and
consuming
data,
and
then
web
2
was
a
more
about
your
ability
to
post
data
and
be
your
own
publisher,
but
you're
publishing
it
for
somebody
else
right
like
facebook
or
youtube
or,
and
they
kind
of
owns
your
data.
So
how
can
we
get
ownership
of
that
particular
transactional
data?
The
individual
pictures
that
we're
putting
up
and
things
like
that?
B
Things
like
that.
That's
all
more
front
end
right
right,
because
the
front
end
piece
is
where
we're
finding
those
pain
points
with
with
inputs
and
outputs.
And
so
that's
that's
where
we're
gonna
see
a
lot
of
disruption
there,
but
then,
in
the
middle
tier,
we're
gonna
see
the
disruption
with
making
modifications
to
those
static,
algorithms
that
we're
constantly
using
and
modifying
those,
so
that
it's
more
of
a
fluid
architecture,
so
that
the
inferences
on
those
inputs
can
change
dynamically.
B
And
so
that's
going
to
be
more.
The
big
big
disruption
we'll
find
at
the
middle
tier,
but
then
the
disruption
we're
seeing
and
that's
what
our
focus
is
is
on
the
back
end,
where
we
need
to
have
immutable
data.
We
need
to
have
distributed
data
so
that
not
one
individual
owns
all
the
keys
to
the
data
set.
B
We
need
to
have
micro
service
architectures
that
might
be
tokenized
so
that
we
can
confirm
that
that
was
the
actual
kubernetes
cluster
that
actually
took
that
particular
input
right
and
it
conformed
to
that
that
input
data
type
right.
So
so
you
can.
You
can
start
to
have
truth
in
data
right,
and
so
that's
something
that
traditionally
has
been
a
big
pain
point
with
any
distributed
computing
model
or
really
any
distributing
workforce
model.
B
And
so
what
we
believe
in
in
simba
is
is
that,
instead
of
trying
to
focus
on
figuring
out
how
to
fit
all
those
pieces
together,
maybe
just
figure
out
where
you
need
to
have
immutability
in
your
data
structure
and
then
and
then
we'll
help
you
index
that
and
start
to
digitize
your
data
and
then
start
to
figure
out
how
you
can
prepare
yourself
for
the
disruption
that
we
think
is
coming.
And
so
I
I
did
kind
of
brief.
B
B
C
Okay,
thanks
tommy,
and
I'm
going
to
ask
tom
if
you
can
see
my
screen.
Okay,
it's
sharing.
Okay,
all
right,
perfect!
All
right!
So
I'm
going
to
talk
a
little
bit
about
hyperledger,
I'm
going
to
talk
some
more
in
detail
about
our
graph
model
that
we
use.
Why
we
use
it
and
then,
after
that,
I'm
going
to
show
you
a
demo.
C
So,
first
of
all,
before
I
get
into
the
demo
before
I
get
into
the
graph
model,
I'm
going
to
show
you
later
on
that
we're
using
solidity,
and
so
I
just
want
to
show
you
how
we're
using
hyper
ledger,
specifically
the
fact
that
we
are
using
something
called
fabric
evm
chain
code.
So
we
can
deploy
solidity
onto
the
hyper
ledger
fabric
distributed
ledger.
C
So,
historically,
all
of
our
tools
were
built
for
solidity
and
they
were
built
for
running
on
ethereum,
and
so
this
includes
the
our
smart
contract
designer.
It
includes
the
the
restful
api
generator
that
angen
touched
on
earlier
in
the
talk,
and
it
includes
our
graph
model
and
everything.
It
was
kind
of
built
built
around
this
idea
that
we
are,
we
are
using
solidity
to
define
our
assets
and
transactions
and
we're
pretty
much
using
you
know,
historically
just
evm,
and
so
in
order
to
support
hyperledger
fabric.
C
There's
a
couple
of
projects
out
there
number
one
is
hyperledger
burrow,
and
that
is
a
completely
evm-based
private
distributed
ledger,
and
so
we
support
that
fully,
but
then
there's
fabric
2.2,
which
is
not
evm
based,
but
there's
a
project
out
there
called
fabric
uvm
chaincode
that
actually
takes
components
of
from
hyperledger
burrow
and
uses
those
in
chain
code
that
can
be
deployed
directly
to
fabric
and
then
what
we
do
is
we
put
a.
I
call
it
an
evm
proxy,
it's
a
fab,
three
proxy.
C
We
put
that
in
front
of
the
ledger
that
communicates
with
that
fabric
evm
chain
code
and
the
fab
three
proxy
is
essentially
if
anybody
has
worked
with
web3
before
or
try
to
deploy
solidity
using
like
programmatically,
then
you'll
know
what
web
three
is
web.
Three
is
a
library
that
allows
you
to
just
programmatically
interact
with
the
ethereum
and
to
interact
with
the
solidity
smart
contracts
that
you
deploy
to
ethereum
the
fab.
3
proxy
is
kind
of
like
a
play
on
that.
It's
a
it
basically
takes
commands
as
though
it
were
a
web
3
library.
C
So
you
could
send
the
same
commands
to
it.
You
can
interface
with
it
as
though
you're
interfacing
with
web3,
and
so
the
tooling
that
we
built
for
you
know
for
solidity,
can
now
work
directly
with
with
hyperledger
fabric.
So
you
can
see
this
diagram
here
of
proxy
the
chain
code.
Then
the
solidity
that's
deployed
to
the
ledger
and
a
couple
of
of
things
came
out
of
this
effort
number
one.
We
did
kind
of
help
with
the
fab
3
proxy.
There
was
a
minor
bug
fix
that
came
out
of
this
effort.
C
In
addition
to
that,
we
did
write
some
documentation
on
how
you
can
deploy
the
evm
chain
code
to
later
versions
of
fabric
like
fabric
2.2
or
2.21,
and
later,
okay,
okay.
So
I'm
going
to
talk
about
a
little
bit
about
the
graph
model
that
we
have
at
simba.
So
this
is
well
first
of
all,
so
the
problem
to
think
about
here
and
the
reason
why
we
have
this
graph
model
is
to
define
relationships
between
assets
and
transactions
and
and
also
between
the
different
transactions
on
the
ledger
and
so
blockchains
and
distributed
ledgers.
C
You
know
the
question
is,
how
do
I
know
the
relationships
between
these
different
transactions
that
I'm
reading
from
the
ledger
and
oftentimes?
These
relationships
are
defined
either
off-chain
or
they're,
defined
or
interpreted
by
a
high
level,
a
higher
level
application.
That's
reading
those
transactions
from
the
ledger,
and
what
we
want
to
do
is
we
kind
of
want
to
ingrain
those
relationships
onto
the
distributed
ledger
that
way
it
stays
distributed,
and
so
there's
it's
not
open
to
interpretation.
We
know
this
is
an
asset
and
we
know
that
this
transaction
actually
belongs
to
this
asset.
C
C
So
we
have
this
graph
based
model.
We
have.
We
also
have
a
gui
that
can
construct
smart,
smart
contracts
and
through
this
gui
you
don't
have
to
know
how
to
annotate
your
smart
contract.
It's
done
automatically
for
you.
You
just
basically
say
I
want
this
business
model.
I
want
this
asset.
I
want
this
transaction
to
relate
to
this
and
then
our
gui,
our
designer,
will
automatically
construct
those
annotations
in
the
contract
for
you
and
then
once
it's
ready.
C
C
Let's
say
that
has
to
have
view
on
both
these
channels,
and
so
how
do
we
link
that
across?
How
do
we
graph
that
across,
of
course-
and
so
we
extended
this
further
so
that
we
can
actually
graph
across
different
blockchains
and
relate
the
relate
two
different
channels
or
blockchains
together
and
then
we've
extended
it
actually
to
relate
two
different
versions
of
the
same
contract,
because
you
know
like
the
business,
the
problem
that
you're
trying
to
solve
on
a
distributed
ledger?
Is
it
it's
not
static?
It's
not.
You
know
permanent.
C
It
changes
over
time,
and
so
you
want
to
be
able
to.
If
I
have
to
update
my
smart
contract,
I
don't
want
to
lose
my
interface
to
all
the
previous
data.
That's
that's
been
transacted
onto
the
blockchain
through
that.
Instead,
I
want
to
kind
of
graph
those
together
and
keep
those
together,
and
so
we've
we've
extended
the
graph
model
to
do
that
as
well.
C
C
C
It
can
consist
of
nodes
which
are
could
just
be
blockchains.
The
nodes
could
be
smart
contracts,
different
versions
of
smart
contracts
and
then
the
relationships
are,
of
course,
the
edges
between
all
of
these
nodes,
so
graphqreal
just
kind
of
kind
of
fits
into
that.
We
want
to
do
okay,
so
then,
I'm
going
to
stop
sharing
here
for
just
a
moment
and
I'm
going
to
share
the
demo
and
I'm
going
to
share
my
screen
for
the
demo.
But
I
did.
A
C
Yeah,
why
don't
we
do
that?
Okay
and
then
I'm
again
going
to
ask
tommy?
Can
you
give
me
a
thumbs
up?
You
can
see
my
screen.
Okay,
all
right,
perfect,
okay.
So
let
me
just
log
in
here
real
quick
and
I'm
going
to
show
you
what
we
have
here.
So
this
is.
This
is
a
very
simple
smart
contract
in
it
there's
there's
four
assets:
those
are
the
supplier
depot
part
stock
item.
This
is
just
a
very
basic
supply
chain:
smart
contract,
it's
not
too
complicated.
We
have
one
transaction
or
one
event.
C
So
I'm
going
to
show
you
the
code,
real
quick
and
I
talked
about
annotations.
This
is
just
a
very,
very
simple
example
of
annotations,
but
if
you
look
at
the
part
function
here
on
line
six,
we
have
as
a
parameter.
We
have
underscore
underscore
part.
So
this
is
an
example
of
an
annotation
and
then
we
have
down.
If
you
look
down
here
at
the
bottom,
for
a
supply
event,
you
can
see
that
it
actually
refers
to
depo
supplier
part.
C
So,
basically,
when
you
stamp
onto
the
blockchain
or
register
a
part
on
the
ledger,
it
comes
back
with
a
transaction
hash.
So
anytime,
you
do
a
invoke
a
supply
event.
We
actually
take
and
remember
that
supply.
We
remember
that
transaction
hash
and
we
kind
of
refer
that
refer
back
to
that,
as
that
is
the
part
that
this
supply
event
refers
to,
and
so
this
is
what
I
mean
when
I
say
we're
kind
of
ingraining
relationships
onto
the
blockchain,
and
then
we
can
graph
that
back.
C
There's.
Of
course,
I
just
showed
you
the
graph
view
here
and
I'm
going
to
open
up
this
graphql
tool.
So
you
can
see
what
this
looks
like,
so
I'm
going
to
click
on
supply,
all
right,
wait
for
it
to
load
okay.
So
this
is
the
query
builder,
so
we
call
the
query
builder.
This
I
mean
the
view
looks
just
like
what
I've
just
shown
you,
you
can
see
the
relationships
between
the
different
assets
and
transactions
at
a
very
simple,
a
very
simple
query.
C
I
can
just
select
one
asset
hit
query,
and
then
it
shows
me
the
results
of
all
the
supply
events
that
have
occurred
on
the
blockchain,
including
some
of
the
information
like
what
you
would
normally
see.
If
you
were
to
read
the
directly
from
the
blockchain,
you
would
have
like
receipts,
and
you
can
see
that
information
here
as
well
and
if
I
click
up
here
at
the
very
top
and
those
kind
of
small
icons
are
a
little
bit
small
but
there's
an
icon
there
at
the
top
right.
C
If
I
click
on
that,
it
actually
shows
me
the
graphql
query
that
was
constructed
and
then
let
me
go
back
here.
Okay,
so
that's
a
that's
a
very
simple
query.
Now,
let's
say
I
want
to
take
you
know:
stock
item
supplier
supply
and
I
can
actually
filter
on.
Let
me
find
it.
Let
me
just
find
one
stock
item
here
that
I
can
filter
on.
C
So
I'm
gonna
grab
this
stock
item.
Here,
for
example,
I'm
gonna
go
back,
I'm
gonna
relate,
I
wanna
find
all
the
stock
items
that
supplier
has
supplied
for
a
particular
depot.
Perhaps-
and
this
is
kind
of
I
I
give
this
as
an
example
all
the
time,
but
why
would
I
want
to
find
all
the
supply
events
from
supplier
for
a
particular
stock
item
and
this
might
be
useful
for
deposit
warehouses
or
anyone
who
wants
to
track
stock
and
transit?
They
want
to
know
where
it
is
at
any
point
in
the
supply
chain.
C
So
this
is
just
kind
of
a
basic
query
that
we
can
do
so.
I'm
going
to
take
that
stock
item
and
you
can
see
here
I
can
project
on
the
fields
that
are
in
the
smart
contract
that
we
saw
before
and
then
I
can
filter
on
those
fields-
and
I
said
stock
item
contains
very
nice
save
now.
If
I
hit
query,
should
give
me
there's
the
stock
item
and
then
from
here
I
can
drill
down,
and
I
can.
I
can
find
all
the
relationships
linked
to
this
particular
stock
item.
C
You
know
that
I've
chosen
so
I
could
say:
okay
well
who's
the
who
are
the
suppliers,
and
we
can
see
there's
there's
multiple
suppliers
that
actually
supply
the
stock
item.
Most
of
these
are
just
examples,
of
course,
they're.
Not
real
and
then
I
can,
I
can
drill
down
even
further
into
all
the
supply
events,
including
their
dates
and
when
they
were
supplied.
You
see
this
is
acme
debug
and
a
fake
warehouse
where
this
was
supplied
to,
and
so
you
could
say
this,
this
could
be
like
a
pseudo
depot.
C
B
C
Yeah,
that's
true,
so
this
is
exactly
why
we
have
this
this
tool
here.
So
if
you
click
on
that
up
at
the
top,
you
can
actually
get
the
the
very
graphql
query
that
was
used
and
you
can
copy
paste
this
and
reuse
this,
and
so
we
have
tools.
You
can
either
download
this.
You
can
copy
paste
this
and
reuse
that
yeah
yeah.
So
there's
some
other
features
here.
C
I
talked
briefly
because
this
is
a
very
simple
example
right,
but
before
again,
going
back
to
the
issue
of
scalability
and
the
issue
of
scalability
is
you
have
your
business
is
growing?
Now
you
have
multiple
channels.
Now
you
have
multiple
blockchains.
They
have
multiple
versions
of
a
smart
contract
and
we
use
you
know
in
the
same
way
that
we
annotate
these
transactions
and
grain
them
onto
the
blockchain.
We've
extended
that
graph
model.
So
now
you
could
you
know
if
you
scale
out
to
multiple
channels
or
scale
out
to
multiple
smart
contracts.
A
B
We
had
two
that
came
up
in
the
chat
window
and
we'll
go
ahead
and
just
take
a
look
at
those
real,
quick,
so
one
the
first
question
is
kind
of
two
questions
in
one,
but
basically
why?
Why
would
did
we
add
a
hyperledger
as
an
optional
foundation
for
one
of
the
distributed
ledger
texts
and
then
what
attributes
would
be
the
driving
choice
between
ethereum
and
hyper
ledger?
So
so,
if
you
want
to
go
ahead
adam
and
then,
if
you
know,
if
you
have
any,
I
can
add
some
to
that.
C
So
so
what
we
were
seeking
in
terms
of
is
when,
when
we
added
hypothesis-
so
I
we
were
actually
thinking
of
throughput-
is
number
one
and
the
fact
that
hyperledger
fabric,
our
choice,
that
for
for
blockchain,
actually
has
baked
in
security
right,
and
so
it's
private.
The
identities
and
roles
that
that
exist
within
the
fabric
network
are
all
governed
by
the
organization.
C
And
if,
even
if
you,
if
you
link
like
two
autonomous
organizations
together,
so
you
have
somebody
out
there
that
has
their
own
hyperledger
fabric
network
and
we
have
our
own
high
budget
fabric
network.
They
can
still
govern
their
own
identities
and
then
they
come
together
with
like
a
peering
relationship
or
a
business
relationship
and
they're
able
to
kind
of
choose.
Okay,
I
want
this
identity
to
part,
be
part
of
the
channel.
C
B
I
would
say
that,
probably,
generally
speaking,
it
would
be
some
where
you
don't
want
want
to
have
an
anonymous
application,
it's
more
of
where
you
have
to
have
a
secure
identity
before
you
can
get
gain
entry.
That
might
be
a
good,
a
good
attribute
that
might
drive
you
towards
hyperledger
versus
ethereum.
B
C
C
A
And
I'll
add
to
that,
and
thanks
for
your
questions,
charles
you
know,
yeah
I
mean
we're,
I
you
know
I'd,
say
architecturally
as
well.
Strategically
you
know
we
we
we
do
have
that.
You
know
we.
We
we
have
that
room
that
can
be
added,
but
put
to
your
first
question
on
to
bring
it
back
to
hyperledger
and
versus
ethereum.
I
mean
I
I
think,
just
broadly
speaking,
you
know
that
there
is
a
reason
why
hyperledger
has
has
a
footprint
it
does.
A
You
know,
has
a
real
estate
is
does
in
in
enterprises
and
kind
of
traditional
enterprises
and
other
organizations
and
institutions,
and
it's
well
suited
for
that
and
an
example
in
a
very.
If
you
go
one
layer
deep,
that's
exactly
what
adam
said:
it's
the
security
aspect
and
those
types
of
properties
of
hyperledger
that
are
going
to
be
important
to
traditional
institutions
and
organizations
and
and
and
and
so
that
clearly
drives
a
choice.
A
You
know
I
mean
we're
getting
into
probably
a
much
bigger
debate
of
between
protocols
and
ethereum
and
hyperledger
and
there's
probably
you
know,
passionate
debates
that
you
know
take
place.
You
know
on
that
topic,
but
but
but
clearly
you
know,
there's
you
know
hyper
ledger,
you
know
is
strong
in
the
enterprises
and
there's
reasons
for
it
and
the
other
thing
about.
As
you
know,
adam
you
mentioned,
you
know
secure
channels,
I
mean
that
being
able
to
do,
you
know,
communicate
across
channels.
A
You
know
so
kind
of
collaborate
securely
or
safely
within
a
secure
environment
so
to
having
these
kind
of
layers
of
of
security,
and
these
layers
of
collaboration
being
able
to
do
cross
chat
like
certain
amount
of
autonomy
within
a
channel,
a
certain
amount
of
flexibility
across
channel.
All
of
that
is
well
suited
to
hyper
ledger
and
is
a
an
important
need
for
enterprises.
So,
and
that's
probably
why
this
community
is
is,
you
know,
is
strong,
you
know
within
traditional
institutions.
B
C
Yeah,
so
this
is
something
that
we're
actually
working
on
in
terms
of
exporting
the
data
that
that
is
the
goal
here,
because
we
want
to
find
the
whole
purpose
of
this
tool
is
to
find
insights
that
aren't
really
obvious
right
away,
and
we
we
are
looking
into
adding
another
data
analytics
tool
to
our
tool
chain.
It
could
be
tableau,
it
could
be.
Something
else
could
be
something
that's
kind
of
homegrown,
but
the
idea
there
is
yes,
you
can
actually
export
this
data
out
of
this
tool
and
then
visual
visualize
that
somewhere
else.
C
So
yeah
so
chain
code
in
terms
of,
for
example,
if
you're
writing
chain
code
for
for
hyperledger
fabric.
So,
like
I
said
before,
we
kind
of
the
tool
chain
itself
is,
is
it's
it's
based
off
of
solidity?
So
what
we
do
is
we've
installed
the
evm
chain
code
and
that's
something
that's
already
done,
and
then
you
would
construct
your
solidity
smart
contract
and
deploy
that
through
the
evm
chain
code.
So,
but
in
terms
of
your
question
like
how
to
install
or
instantiate
sharing
code,
the
tool
itself
doesn't
generate
the
chain
code.
A
Great,
thank
you.
We
have
a
question.
It's
it's
more
of
a
comment.
I'd
say
from
oliver:
where
does
hyperledger
basu
fall
into
this?
It's
not
so
much
ethereum
versus
hyperledger
anymore.
If
base
who
supports
it
during
main
net,
as
well
as
permission
channels
he's
asking
us
to
comment
on
this.
You
know
it's
really
more
of
a
comment.
So
do
you
guys
care
to
make
a
comment
here.
C
Yeah,
so
basu
is
like
the
java
based
client
for
ethereum
right.
So
it's
a
lot
like
in
terms
of
you
have
geth,
which
is
go
ethereum
and
you
have
this
written
in
golang
and
you
have
a
parody
as
well.
So
basu
is
just
a
java
based
version
of
that
yeah.
It
is.
It
can't
support
permission
channels
and
we
are
actually
going
to
support
basu.
That's
this
next
and
so
in
terms
of
it's
not
so
much
ethereum
versus
hyperledger
anymore.
I
never
thought
of
it
as
as
ethereum
versus
hyperledger.
C
To
be
honest,
but
we
you
know
we're.
Obviously
their
hyper
ledger
is,
is
working
on
their
own
tool
set
to
support
all
kinds
of
ethereum-based
stuff.
Just
like
I
said
in
the
in
the
previous
slides,
I
was
showing
hyperledger
burrow,
for
example,
which
is
a
private
evm
based
distributed,
ledger
built
on
tinderment.
I
think
it's
called
tinderment
consensus,
algorithm
and
so
yeah
we're
I
mean
I
don't
I
don't
know,
I
don't
see
it
as
ethereum
versus
hyperledger
really
and
we
are
working
on
supporting
basic
in
the
future.
A
Great,
I
don't
think
we
have
any
questions
now
but
feel
free
if
you
have
more
questions
to
to
put
them
into
the
chat.
One
thing
that
we
could
do
is
because
we
do
have
a
little
bit
of
extra
time
until
some
more
questions
trickle
in
did
you
want
to
talk
a
little
bit
about
another
slide
we
had
in
reserve
adam
on
on,
because
this
is
a
question
that
has
come
up
in
the
past
in
the
hyperledger
community
related
to
fabric.
C
C
Basically,
this
is
showing
something
I
would
call
them
autonomous
fabric
networks
or
autonomous
msps,
and
what
I
mean
by
that
is:
let's
say
you
have
several
organizations
and
they've
already
have
their
established
networks
and
they
may
even
have
you
know.
Their
networks
are
already
paired
up
with
with
clients
of
their
own,
and
I,
I
think
one
relationship
you
could
think
about.
Is
you
have
tiers
of
suppliers?
You
have
a
major
supplier
and
then
they
have
their
own
sub-tier
suppliers
applying
to
them,
but
then
they
also
have
their
customers
right.
C
So
maybe
there's
a
pre-established
fabric
network
that
exists
and
the
difficulty.
The
challenge
is:
how
do
you
connect
these
together?
That
is
how
do
you
peer
them
together?
If
you
have
all
these
different
self-governed,
msps
and
identities,
and
there's
like
some
alternative,
there's
like
different
ways,
you
could
do
this.
Obviously
so
hyperledger
fabric
has
like
cascading
cas.
You
have
a
root
ca
and
then
you
could
establish
intermediate
cas
between
the
different
organizations
and
you
can
establish
identities
and
channels
through
that
through
that
methodology,
there's
there's
other
ways
of
doing
it.
C
I've
heard
of
people
using
cloud
native
solutions
such
as
azure,
ad
or
key
vaults,
and
things
like
that
for
the
we
we
had
a
particular
challenge
which-
and
I
won't
go
into
too
much
detail.
Oh
there's,
a
third
one.
You
could
also
use
ibm
blockchain
platform,
of
course,
to
do
to
do
this
and
you
can
set
up
all
of
your
networks
inside
of
the
the
ibm
blockchain
platform.
C
So
without
going
into
too
much
detail,
though,
these
three
forms
of
peering
were
not
really
an
option
to
us.
There's
a
bit
of
a
challenge,
and
so
I
was
just
showing
you,
you
know:
how
do
you
do
it
if
you
have
all
these
different
self-governed
msps
and
you
want
to
pair
them
together?
How
do
you
do
that?
C
Because
you
have
to
somehow
export
the
certificates
of
the
identities
that
you
want
to
enroll
into
your
channel
from
the
other
organization,
and
I
was
just
going
to
show
you
know
just
briefly
how
we've
done
this
so
we've
actually
come
up
with
a
secure
messaging
system
or
secure
file
exchange
system
really
is
what
this
is,
and
so
these
autonomous
msps
I
want
to
appear
together.
They
would
export
and
share.
C
You
know
their
certificates,
other
secrets,
and
we
would
share
that
and
then
be
able
to
vet
one
another
and
then
connect
one
another
through
that,
so
that
the
the
file
exchange
is,
you
know,
used
very
frequently
right.
It's
used
only
to
to
share
these
secrets
and
crypto
material,
and
then,
after
that,
we
have
secure
channels
that
can
that
between
endorsers
we
set
up
secure
channels
between
endorsers
and
then
those
endorsers
using
a
secure
channel
can
vet
outside
msps
and
bring
them
in
and
and
help
them
join
the
network.
C
This
way,
so
this
is
kind
of
like
you
know,
there's
different
ways
of
doing
this,
but
I
do
know,
after
talking
with
a
lot
of
people,
that
this
this
happens
to
be
a
question
on
a
lot
of
people's
minds
in
terms
of
how
do
you
connect
two
different
networks
together,
I
just
wanted
to
share.
This
is
how
we're
doing
it
on
our.
D
C
It
does
support
private
data
collection,
yes,
so
that
the
tool
chain
that
we've
developed,
we
actually
developed
something
called
it's
an
etl.
I'm
calling
it
kettle,
but
the
this
etl
actually
allows
you
to
push.
So
we
would
deploy
this
within
your
own
network
or
within
your
own
infrastructure,
completely
private
to
you.
You
manage
it
and
you're
able
to
push
private
data
through
the
etl
onto
a
private
or
secure
channel,
and
so
we
we
have
that
it's
there's
there's
other
ways
of
doing
it.
We
also
have
connectors.
C
C
Yeah,
so
the
so
that
this
tool,
because
it's
the
most
the
tools
were
kind
of
built
on
solidity,
so
we
don't
generate
chain
code
directly.
What
we
do,
though,
is
for
hyperledger
fabric.
In
particular,
we
deploy
the
evm
chain
code
onto
that
ledger,
the
hyperledger
fabric
or
the
hyperledger
fabric
that
we
that
we
support
and
then
the
tools
that
we
have
actually
construct
a
solidity
smart
contract
and
deploy
that
to
to
the
ledger
through
that
chain
code.
So
it
doesn't
actually
generate
chain
code.
D
D
D
D
If
you
are
looking
for
more
content-
and
you
are
looking
to
for
more
videos-
please
check
out
our
youtube
channel.
We
have
some
very
good
recordings
from
our
hyperledger
global
forum.
There
also
all
of
the
presentations
slides,
are
available
through
our
sketch
and
please
do
get
involved.
We
love
participation
from
the
community
and
everybody
is
welcome
in
hyperledger
community,
so
jump
on
the
chat,
email,
us
and
we'll
help
help
you
get
started
so
again.
Thank
you,
so
much
adam
tom
anjon
and
I'm
looking
forward
to
seeing
you
again
soon
stay
safe.