►
Description
A virtual meetup hosted by Hyperledger Denver on October 28, 2021 featuring Todd Little, Chief Architect for the Oracle Blockchain Cloud Service. This session covers the features of the Oracle Blockchain Platform (OBP) based on Hyperledger Fabric including the enhancements Oracle has made to Fabric.
More about the event is at: https://www.meetup.com/Hyperledger-Denver/events/281144972/
----
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
----
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 #HyperledgerMeetup #Blockchain
A
You
know
today
I
want
to
get
in
and
really
talk
about
performance
and
scale.
As
far
as
one
of
the
questions
I'll
have
today
and
then
you
know,
todd
is
also
the
chief
architect
for
tuxedo
in
the
oracle
fusion
middleware
development
organization
and
really
define
the
technical
strategy
and
direction
for
the
tuxedo
part
product
family.
A
B
All
right,
truly
thanks
john.
I
appreciate
the
introduction
so
yeah
I've
been
been
in
this
business
for
a
long
time.
I
won't
indicate
how
many
years,
but
you
can
tell
from
the
gray
it's
been
a
few,
so
I've
been
working
with
tuxedo
since
1997,
I
was
acquired
from
digital
equipment
by
bea
systems
and
then
oracle
acquired
va
systems
in
2008,
so
I've
just
been
sort
of
getting
dragged
along
and
so
tuxedo.
B
So
we
decided
we
should
create
a
blockchain
offering
we
made
a
proposal
to
our
management
got
shot
down
because
I
think
they
thought
it
was
bitcoin
and
because
that's
what
everybody
thought
blockchain
was
bitcoin
and
blockchain
were
basically
identical.
So
anyway,
it
took
a
year
before
we
were
able
to
then
get
a
go
ahead,
and
so
we
spent
2017
building
our
platform
on
hyperledger
fabric
and
we've
been
enhancing
that
ever
since.
B
So
what
I
want
to
talk
about
today
is
a
little
bit
about
our
product
and
our
offerings
and
as
well,
some
of
the
enhancements
we've
been
making
to
hyperledger
fabric
both
directly
to
fabric
code,
as
well
as
to
tools
and
stuff
like
that.
We've
built
something
called
the
blockchain
app
builder.
So
with
that,
why
don't
I
get
started
here
and
we'll
get
going.
B
So
what
I'm
going
to
cover,
as
I
get
my
mouse
over
here,
is-
I
want
to
first
cover
a
little
bit
about
what
our
blockchain
offerings
are.
So
we
have
several
different
products
in
the
blockchain
space
and
then
talk
a
little
very
briefly
about
some
customer
adoption,
some
of
our
partner
solutions
and
then
largely
I'm
going
to
spend
most
of
time
on
some
of
the
updates
that
we've
made
some
and
some
of
the
more
recent
changes
that
we've
added
to
our
service
and
then
finally,
a
q
a
session.
B
We
see,
we
see
blockchain
as
being
relatively
pervasive
many
many
industries,
all
of
our
verticals,
are
looking
at
blockchain
solutions,
so
we're
we're
working
with
a
number
of
different
partners,
we're
working
with
our
own
internal
sas
organizations
for
what
we
have
fusion
apps
and
their
interest
in
blockchain.
I'll
talk
a
little
bit
about
some
of
the
work
they've
done
to
integrate
in
with
our
blockchain
service
into
their
sas
offerings,
and
you
know
our
our
strategy
basically,
is
they
make
it
quick
and
easy?
B
We
want
to
build
a
market
leading
platform
for
blockchain
adoption,
and
we
also
recognize
that
you
know
people
want
to
do
this
both
in
the
cloud,
but
they
also
need
to
do
it.
On-Premise
and
oracle
has
a
large
number
of
regions
for
our
cloud
offering,
but
we
don't
we're
not
in
every
country
we
probably
would
never
be
in
every
country.
B
These
were
the
separate
data
centers,
so
things
like
data,
residency
and
stuff
like
that,
require
that
you
have
an
on-premise
version
as
well,
so
we
offer
this
product
basically
in
two
forms:
one
is
a
cloud
service
and
one
is
a
on-premise
service
and
I'll
explain
a
little
bit
about
each
of
those
and
how
they
how
they
function.
As
I
mentioned
as
well,
you
know
our
sas
offerings
they've
picked
up
for
our
cloud
erp
application.
They
have
something
they
call
intelligent,
track
and
trace,
and
this
does
tr.
B
I
can
trace
based
upon
transactions
that
are
recorded
in
our
blockchain
platform
and
then
as
well,
our
database
team,
of
which
I'm
part
of
by
the
way
the
blockchain
team
is
part
of
the
database
team.
We
have
something
that
we're
calling
our
cryptosecure
database,
so
this
is
moving
or
leveraging
some
of
blockchain
technology
in
the
oracle
core
database.
B
It's
a
separate
control
plane,
though,
because
we
can't
use
the
oci
control
plane
in
an
on-premise
offering
so
they
we
provide
a
vm
that
acts
as
the
control
plane.
And
then
it's
used
to
manage
a
set
of
vms
that
are
provided
by
the
customer,
and
then
we
have.
We
run
docker
containers
and
docker
swarm
in
that
and
deploy
basically
the
same
kind
of
elements.
B
So
our
admin
console
our
our
api
gateway,
which
I'll
talk
about
in
a
minute
and
as
well
as
integration
in
with
identity
management,
because
that's
something
that
doesn't
come
out
of
the
box
with
fabric.
You
need
to
integrate
basically
into
an
identity
management
system,
typically
through
that's
done
through
your
fabric
ca.
So
we've
integrated
that
with
the
identity
cloud
service
for
our
cloud
offering
and
we
for
the
on-premise
offering
we
support
things
like
ldap
or
ad
for
identity
management.
B
As
I
mentioned,
we
have
also
this
intelligent
track
and
trace.
So
this
is
pre-built
sas
applications
that
are
leveraging
our
blockchain
technology
and
they're
used
for
things
like
this
to
be
able
to
to
get
visibility
into
your
supply
chains,
to
be
able
to
do
things
like
tracking
the
shipments
of
goods
potentially
cold
items,
you
know
so
things
that
have
to
be
refrigerated,
so
those
are
being
monitored.
B
All
that
stuff
is
being
monitored,
then
by
our
cloud-based
services,
but
leveraging
our
blockchain
to
be
able
to
record
this
information
and
then
finally,
we
have
these
that
what
we're
calling
the
cryptosecure
database.
So
this
is
using
blockchain
technology
in
the
database.
We
create
what
we
call
blockchain
tables,
so
a
blockchain
table
is
a
table
that
can
be
insert
only
and
each
row
is
chained
and
hashed
to
the
the
next
row
as
well
that
the
rows
can
be
signed.
Cryptographically
signed,
so
you
know
who
made
the
modification
or
who
inserted
it.
B
B
B
B
We
have
the
ability
to
be
able
to
do
what
we
call
off
chain
data
sync,
so
we
can
automatically
pump
data
into
other
environments
like
oracle
data,
oracle,
data
warehouse
and
I'll
give
a
little
bit
of
example
about
why
we
did
that.
What
kind
of
use
cases
we
have
so?
The
advantages
I
say
is
that
it's
pre-assembled
you
don't
you
don't
go
grab
a
bunch
of
containers
and
try
to
build
this
yourself.
It's
open
and
say
we're
based
upon
hyperledger
fabric.
We
adhere
to
all
the
fabric
code,
standards
and
stuff
it.
B
B
This
is
something
that
we
felt
was
absolutely
necessary
for
integration
purposes.
Very
few
existing
applications
can
make
grpc
calls
they
can
easily
make
rest
calls,
though,
so
rest
tends
to
be
the
integration
standard
that
is
used.
So
we
provide
a
proxy
that
basically
takes
rest
requests
and
turns
those
into
fabric
invocations,
either
queries
or
transaction
submission,
as
well
as
things
like
administration
stuff
like
that.
So
we
have
a
full
set
of
rest
services
to
be
able
to
do
that.
It's
enterprise
grade
when
you,
when
you
create
the
appropriate
shape
whatever
we
we
spread.
B
The
instances
around
availability,
domains
or
across
fault
domains
within
the
oracle
cloud-
and
you
know
we
also
then
do
the
devops.
It's
a
fully
managed
service.
So
oracle
takes
care
of
the
patching,
the
management,
the
the
ensuring
that
the
system
is
up
and
running
upgrade.
So
when
we
go
from
one
version
of
fabric
to
another
version
of
fabric,
oracle
takes
care
of
all
that
those
operations
for
you.
So
it
makes
it
much
easier
for
customers
to
be
able
to
adopt
blockchain
as
a
service,
yeah,
say
the
enterprise
edition.
B
This
is
essentially
the
same
set
of
bits,
they're
just
packaged
in
a
different
way,
and
the
main
difference,
as
I
say,
is
that
we
can't
use
the
oci
control
plane.
So
we
built
our
own
control
plane
that
runs
in
a
vm
and
then
that
control
plane
is
used
to
manage
the
other
vms
that
are
provided
to
it
to
deploy
things
such
as
your
peers.
Your
proxies,
the
console,
all
the
various
hyper
electric
components
and
our
components
are
all
get
deployed,
then,
to
this
cluster
of
vms
that
are
provided
to
the
control
plane.
B
So
we
provide
you
know
it's
it's
feature,
parity
with
the
oracle
blockchain
cloud
service,
and
so
this
is
one
of
the
things
that
we
did.
This
is
to
say
because
of
things
like
data
sovereignty,
issues
and
those
sorts
of
things.
So
we
do
support.
You
know
multi-pistol
cloud
environments,
multiple
on-premise
deployments,
so
you
have
your
choice
of
where
you
want
to
run
the
various
members
of
your
organization
or
of
your
network,
what
kind
of
environment
they
want
to
run
in.
B
So
it's
easy
to
deploy,
because
I
say
it's
all
predis
pre-assembled.
You
essentially
answer
three
or
four
questions
in
the
oci
console
and
wait
a
little
bit
and
your
blockchain
instance
will
be
up
and
running,
so
it
makes
it
really
easy
to
experiment.
With
this
we
say
because
of
the
rest
apis
and
the
client
sdks.
B
We
can
integrate
with
many
many
other
systems,
including
you
know,
third-party
apps,
on-premise
apps
other
applications
as
well,
which
is
really
critical
by
the
way,
because
oftentimes
blockchain
is
used
an
integration
mechanism
between
different
systems
of
record,
and
so
you
know
having
these
kinds
of
integration
capabilities
makes
a
big
difference.
Identity
management-
that's
something
that
you
know,
fabric
doesn't
really
provide,
doesn't
provide
an
identity
management
solution.
They
have
the
fabric
ca,
but
as
far
as
being
able
to
you
know,
I
take
care
of
the
registration
enrollment
passwords,
all
that
sort
of
stuff.
B
So
it's
also,
as
I
say
it's
easy
to
manage
and
monitor.
We
provide
a
a
console,
a
set
of
interfaces
that
allow
you
to
see
what
the
activity
is
going
on
to
be
able
to
monitor
the
the
state
of
the
various
nodes
to
be
able
to
as
well.
That
console
is
based
upon
a
set
of
rest
apis.
So
all
those
apis
can
be
used
by
your
own
tooling.
B
Is
that
something
we
call
the
blockchain
app
builder,
so
the
blockchain
app
builder
is
if
you,
if
you're
familiar
with
composer
the
old
composer
project
in
fabric
that
was
sort
of
the
idea,
and
that
gave
us
the
idea
for
this
tool.
It's
fairly
different,
though
composer
was
built
upon
the
idea
that
you
created
a
model
and
then
from
that
model
you
would
then
generate
smart
contracts
and
the
like
in
this
case
here.
B
What
we
do
is
we
start
with.
What's
called
a
specification
file
that
defines
your
assets
or
tokens,
and
then
we
generate
code
and
scaffold
projects
for
you
that
you
can
then
use
something
like
vs
code
to
be
able
to
edit,
as
well
as
a
vs
code
extension,
and
if
I
get
a
chance
I'll
demo,
a
little
bit
of
that
we'll
see
if
I've
got
time
and
as
well
with
something
we've
just
recently
added
to
the
app
builder
is
the
support
for
tokens.
B
So
the
idea
here
is
that
you
can
define
in
the
specification
file
that
some
of
the
assets
are
tokens
and
we
follow
the
token
token
taxonomy
framework
ttf,
which
is
an
open
standard
for
defining
tokens.
And
then
we
implement
basically
all
the
methods
that
the
token
tokens
support.
So
is
it
mintable
burnable
can?
Is
it
fungible
or
non-fungible
at
the
moment,
we're
only
supporting
fungible
tokens,
but
the
plans
are
to
shortly
soon
to
be
able
to
support
non-fungible
tokens
as
well.
B
So
the
basic
flow
is
to
say:
is
you
start
with
this
thing
called
a
specification
file?
It's
either
a
yaml
or
json
file
that
defines
the
assets,
they're
properties,
things
like
the
field
requirements,
so
you
can
specify
that
a
field
is
a
string
and
it
has
to
be
no
more
than
15
characters
or
you
can
match
it
against
a
regular
expression.
B
So
we
have
a
variety
of
validation
techniques
that
we
can
validate
the
fields,
so
they
make
sure
that
the
data
is
already
is
correct
before
it
gets
entered
into
the
blockchain
and
as
well
as
it
describes
sort
of
you
know
the
structure
of
all
your
assets,
field,
names
and
other
properties
and
the
like
from
that.
Then
we
scaffold
a
project.
So
this
creates
a
smart
contract
project
that
you
can
use
to
build
your
smart
contract
and
either
go
or
in
typescript,
and
so
we
can
take
care
of
all
the
code
generation.
B
We
we
generate
the
project
artifacts,
we
do
all
that
sort
of
work
and
you
basically
have
a
ready
to
go
smart
contract,
typically
you're
gonna,
add
custom
methods
because
we
generate
crud
methods.
So
you
automatically
get.
You
know
create
an
asset
update,
the
lead
read
an
asset,
but
typically
you
want
more
than
that
in
your
blockchain.
So
you
know
things
like
in
the
marbles
example
is
trader
marble
or
biomarble,
or
you
know
any
of
those
sorts
of
custom
methods.
B
You
can
define
their
interface
in
the
spec
file,
but
the
actual
implementation
has
to
be
provided
by
the
developer
once
once,
you've
added
your
custom
methods.
You
can
then
deploy
this
locally
to
a
local
fabric
instance
that
we
start
up
and
manage
for
you
and
that's
that's
typically
how
customers
test
and
get
ready
to
go
and
then
once
you've
got
your
contract
ready,
you
can
from
the
app
builder
you
can
automatically
deploy
this
then
to
an
obp
network
or
any
fabric
network.
For
that
better,
oh
yeah,
it
should
be
any
fabric
network.
B
B
So
you
can
then
say
you
can
compile
and
run
your
smart
contracts
and
run
those
in
in
our
in
our
blockchain,
but
in
our
blockchain
platform,
and
so
you
then,
from
from
their
tooling,
you
can
do
things
like
invoke
the
smart
contract,
but
you
can
also,
then,
because
we
expose
all
of
the
smart
contract
operations
through
a
set
of
rest
apis.
You
can
invoke
all
these
through
rest,
so
here's
an
example
of
being
able
to
invoke
a
solidity
chain
code
and
some
arguments
have
been
passed
to
it,
using
curl
command.
B
So
we
also
say
it
is
a
team
sport.
We
like
to
say
that
fabric
is
a
team
or
blockchain's
a
team
sport,
and
we
mean
that
in
a
couple
different
ways.
One
is
clearly
that
you
know.
Typically,
you
have
multiple
organizations
right.
A
single
organization.
Blockchain
network
is
not
particularly
interesting,
although
we
have
a
number
of
customers
who
are
doing
that,
but
we
typically
see
where
there
are
multiple
organizations
and
there
are
probably
multiple
instances
of
fabric
running
and
even
different.
B
You
know
under
different
environments,
so
one
of
the
projects
we
did
with
a
company
pasa.
So
this
is
a
a
blockchain
network,
that's
deployed
across
oracle,
ibm
and
microsoft,
azure
nodes
and
as
well.
We
have
another
customer
cargo,
smart
who's
tested
this
and
you
know,
operates
without
la
clouds
blockchain
as
a
service.
B
Now
we
also
support
demo
through
third-party
integration,
so
we
can
run
demo
smart
contracts
and
solidity
as
well,
as
I
mentioned
before,
using
the
evm
as
well.
We
have
another
partner
called
over
ledger
and
so
over
ledger
provides
essentially
as
a
way
to
be
able
to
do
cross-ledger
transaction
integration.
B
B
Real
quickly
here
some
examples
of
what
we
have
in
in
you
know:
sort
of
production
or
whatever.
So
we
have
a
large
number
of
customers
that
are
doing
a
variety
of
things.
So
we
have,
you
know
a
lot
of
the
financial
services
things
like
know.
Your
customer
applications
point
of
sale
for
ekyc,
so
a
number
of
different
things
in
the
financial
services
area.
B
In
the
in
the
supply
chain
area.
We
have
a
number
of
us
customers
ever
ledger.
You
may
have
heard
of
they
track
the
provenance
of
diamonds
from
the
time
they're
mined
until
their
time
they're
sold
in
a
retail
store.
Abbott
is
using
it
for
coping
19
test
results.
So
we're
seeing
this
in
a
number
of
different
areas
and
then
as
well,
we've
got
things
like
we're
doing
for
certificate
of
origin.
I
think
cargosmart
is
building
their
global
business
shipping
network.
B
This
is
network
based
upon
hyperledger
fabric
and
our
our
instances
certified
origin
tracks.
Olive
oil
from
the
time
that
the
olives
are
harvested,
pressed
about
the
process
and
bottled
and
delivered
to
the
store
circular
is
doing
the
same
thing
for
for
cobalt
batteries
and
the
like.
So
you
see
we
have
we
have.
This
is
only
this
is
only
a
small
fraction
of
the
of
the
customers
we
have
and
the
kinds
of
things
that
they're
using
our
blockchain
platform
for
as
well.
B
We
also
have
a
set
of
partners,
so
industry
partners
here
that
are
building
their
applications
on
our
bot
on
our
platform.
So
sydema
is
using
this
for
doing
what's
called
non-performing
loans.
So
how
do
you?
How
do
you?
What
do
you
deal
with
a
non-performing
loan?
So
they
create
a
marketplace
for
other
financial
institutions
to
be
able
to
buy
these
non-performing
loans?
B
B
B
B
So
what
some
of
the
things
that
we've
taken
care
of?
Are
things
like
the
provisioning?
So,
as
I
say,
you
know,
we
take
care
of
provisioning,
you're
in
a
cloud
environment
or
as
well
an
on-premise
environment
by
providing
a
local
control
plane
in
the
oracle
cloud.
This
is
all
done
through
the
normal
oci
cloud
management
console.
So
you
can
create
containers.
B
We
we
manage
it,
which
is
a
really
is
a
critical
point.
If
you've
ever
managed
a
fabric
network,
it's
a
lot
of
work,
keeping
up
with
patches
making
changes
upgrades,
especially
you
know,
recovering
from
certain
kinds
of
failures
and
stuff
like
that.
We
provide
tools
to
be
able
to
help
with
that
an
example
that
might
be
is
that
you
end
up
with
a
non-deterministic
chain
code
that
you
didn't
realize
and
that
doesn't
necessarily
show
up
right
away
until
your
peers
start
to
start
to
result
with
different
results.
B
So
we
have
a
mechanism
to
basically
be
able
to
detect
some
of
that
and
basically
be
able
to
rebuild
the
the
ledger
once
the
the
the
the
non-determinism
has
been
removed.
We
also
take
care
of
them
taking
backups
of
the
configuration
we
provide
backups
of
the
ledger,
so
we
can
recover
from
failures.
We
have
integration
with
they
mentioned
with
the
identity
management.
So
that's
already
taken
care
of.
We
do
provide
an
audit.
B
We
provide
this
bi-directional
api
gateway.
So
that's
as
mentioned
before
what
we
call
a
rest
proxy.
So
this
supports
essentially
a
set
of
rest
calls
to
be
able
to
interact
with
your
fabric
network.
It
also
allows
things
like
event
notifications,
so
you
can
specify
that
you
want
to
get
a
call
back
when
an
event
is
generated
by
a
fabric
chain
code,
so
this
makes
it
really
easy
to
integrate
in
with
other
systems.
It
also
makes
it
easy
to
test.
You
can
simply
use
a
curl
command
and
test
against
your
rest
proxy.
B
The
console
takes
care
of,
let's
say
many,
of
the
administrative
tasks.
So
when
you
want
to
see
what
the
performance
is
like
you'll
want
to
examine
the
ledger,
you
want
to
add
new
peers
deploy
chain
codes.
All
that
stuff
can
all
be
done
through
our
console
that
app
builder
I'll
get
more
into,
and
talk
a
little
bit
about
that.
The
most
recent
thing
that
we've
added
here,
as
I
say,
is
the
the
token
support.
B
So
this
is
a
completely
new
set
of
features
that
we've
added
to
oracle
the
app
app
builder
watching
that
builder-
and
we
think,
there's
going
to
be
a
lot
of
interest
in
this,
because
there's
huge
interest
in
tokens
right
now-
and
we've
also
done
some
optimizations
around
that.
So
I'll
talk
a
little
bit
about
how
we
handle
tokens
in
a
an
environment
where
we
use
a
balance
base,
as
opposed
to.
B
I'll
think
of
the
term
I've
gotten
anyway,
something
else
we
did
very
early
on
is
we
replaced
the
ledger
db
and
the
couchdb
options
for
world
state.
We
replaced
those
with
berkeley
db
and
the
reason
we
did
that
is
that
berkeley
db
has
a
sequel
light
driver
that
it
can
be
used
on
top
of
bdb,
and
so
this
only
means
that
you
can
do
full
sql
queries
inside
your
chain
code,
which
is
much
more
powerful
than
the
couchdb
query
language.
B
Although
we
do
support
the
couch
query
language,
we
transform
that
into
a
sql
statement,
basically
and
then
return.
The
results
as
couch
would
return
them.
This
is
significantly
faster
than
couch
because
light
level
db
berkeley
db
is
a
in-memory
basically
database.
So
it's
not
a
client
server
database
like
couches.
B
B
We
maintain
basically
the
the
transaction
records
themselves
and
we
maintain
the
state,
so
you
can
go
back
and
do
rich
queries
using
standard
sql
against
the
oracle
database
instance
to
be
able
to
do
queries
about
the
state
of
the
database
as
well
as
about
you
know
the
transaction
history,
and
this
includes
the
actual,
the
full
transaction
history.
It's
not
like
the
transaction
history,
that's
provided
by
fabric,
which
just
provides
you
an
index
into
the
ledger
to
be
able
to
get
something.
This
returns,
the
actual
actual
transaction
information.
B
B
We
say
we
we
allow
you
up
to
16
nodes,
for
instance,
that's
probably
an
artificial
limit,
but
it's
what
we're
supporting
right
now
we
can
create
new
channels.
You
can
add
members
to
channels
all
that
stuff
is
done
through
the
the
admin
console,
that's
provided
and
then
as
well.
This
is
a
so.
The
oci
takes
care
of
all
the
deployment.
So
this
is
the
control
plane,
but
the
data
plane
is
where
we
have
all
the
administration
operations
for
the
various
components.
B
So
here's
here's
a
picture
of
the
console
and
up
in
the
upper
right
here.
So
it's
saying
that
the
the
instance
is
healthy.
What
the
utilization
looks
like
what
kind
of
activity
is
going
on,
then
you
can
drill
down
into
your
channels
your
peers,
ordering
services,
nodes
and
other
organizations
that
you
may
have
joined
into
your
network.
B
B
We
also
take
care
of
the
smart
contract
lifecycle
management.
So
you
we
can
deploy
smart
contract
packages
from
the
console
to
take
care
of
things
like
defining
your
private
data
collections
and
mapping
transient
data
the
like
and
I'm
going
to
say.
We
also
provided
this
the
sort
of
the
monitoring
and
troubleshooting.
So
you
can
do
your
topology.
You
can
see
the
status
of
all
of
your
components.
B
So
the
rich
query
support.
I
already
mentioned
a
little
bit
about
this.
This
is
to
say
that
there's
a
replacement
for
couch,
so
we
can
use
full
sql,
select,
statement,
capabilities,
and
so
this
this
gives
us
the
speed
of
level
db,
but
gives
us
the
query
capability
of
couchdb
or
much
more
than
the
couchdb.
B
Actually
another
thing
that
we
that
this
provides
us
as
well
is
that
bdb
supports
through
the
sql
lite
interface
provides
record
level
locking,
and
so
we
can
do
concurrent
endorsements
and
commits
at
the
same
time
normally
fabric
locks
the
database
and
does
only
commits
or
endorsements.
It
doesn't
do
them
simultaneously.
B
We
can
interleave
these,
so
we
get
better
performance,
lower
latency
things
like
that.
Like
I
say
so,
this
ability
to
do
select
statements.
You
can
you
can
you
can
do
an
awful
lot
in
a
select
statement?
Put
it
that
way
and
that's
all
supported
out
of
the
box
and
as
I
say,
we
also
then
we'll
do
we'll.
Take
the
crowd.
Query,
syntax
as
well,
provide
that
and
then
we
translate
that
into
sql
statement.
B
Another
huge
benefit
here
to
what
we've
done
is
that
we
revalidate
the
query
at
commit
time.
So
if
you
use
a
couchdb
as
an
example
and
you
make
a
query
and
you
use
those
results
in
a
transaction
to
make
a
modification,
you
suffer
the
possibility
of
dirty
reads
because
the
the
query
is
not
re-executed
at
commit
time.
We
re-execute
the
query
at
commit
time,
and
so
we
can
verify
that
the
query
return
the
exact
same
results.
We
basically
compute
a
merkle
tree
and
get
a
hash
of
that.
So
we
get
we
get.
B
B
So
we
define
a
schema
that
is
used
inside
the
database
once
that
schema
is
created,
then
we
will
update
the
oracle
database
history
database
at
the
same
time
that
basically,
the
information
is
being
committed
inside
the
peer.
So
we
model
this
using.
You
know
json
in
the
oracle
database,
and
what
that
does,
though,
is
this
makes
us
available
for
other
tools,
so
you
can
use
things
like
analytics
tools
and
stuff
like
that
to
be
able
to
analyze
your
blockchain
transactions
or
some
other
uses
and
I'll
show
that
share
those
in
a
minute.
A
B
Let
me
finish
up:
that's
on
the
risk
history.
I've
just
got
a
couple
examples
here
and
then
then
then,
we'll
take
a
break
for
some
questions
and
then
continue
so
okay.
So,
as
I
say
what
happens
here
is
when
a
block
goes
to
get
committed.
The
peer
that's
associated
with
this
that
receives
this
and
has
been
configured
for
this
rich
history.
B
So
now
inside
the
oracle
database,
we
have
the
ledger
as
well
as
the
state,
the
state
database,
because
we
do
the
same
thing.
We
maintain
that
state
information
in
the
oracle
database,
just
as
it
would
be
maintained
in
the
the
state
db
that
the
pure
is
maintaining
so
that
once
you've
got
this
data
here
you
can,
do
you
know
visualizations,
you
can
run
analytics.
You
can
export
this
to
some
other
application.
B
It
gives
you
essentially
a
copy
of
the
data
without
having
to
do
things
like
query
operations.
Now
it
may
lag
a
little
bit
because
you
know
we,
we
commit
this
in
asynchronously
against
the
the
database,
so
it
may
lag
behind
under
high
volume,
but
we
have
a
number
of
customers
who
are
using
this
for,
like
read
queries
so,
instead
of
performing
a
query
operation
against
the
blockchain,
they
simply
hit
the
oracle
database
instance
and
get
the
information
so
analytics.
B
You
can,
you
know,
say
now
that
it's
in
in
a
relational
database,
there
are
tons
of
tools
to
be
able
to
analyze
this
data.
High
volume
reads:
this
was
the
one
of
the
cases
one
of
our
customers,
where
they
do
a
significant
volume
of
reads.
They
don't
need
all
those
to
be
to
occur
on
the
the
blockchain
itself.
They're
happy
to
you
know
have
a
copy
of
that
data
that
they
can
read
against.
A
Let's
see
okay,
todd,
let's
jump
in
and
I'm
not
gonna
take
them
in
you
know
the
way
they
were
put
in,
I'm
gonna
take
them
in
kind
of
a
interesting
order
here.
So
okay,
they
were
talking
about
hybrid
cloud
versus
let's
say
on
premise
or
you
know.
Let's
say:
blockchain
is
a
service
cloud.
Do
you
support
hybrid
cloud
for
any
of
the
blockchain
service
that
you
offer.
B
Well,
I'm
not
sure
what
they
mean
by
hybrid
cloud.
We
we
do
support.
You
know
we
and
we've
shown
that
we
can
integrate
in
with
you
know,
other
blockchain
cloud
services
that
are
built
on
fabric
as
well.
You
can
integrate
in
with
the
on-premise
version
of
oracle
blockchain
platform,
enterprise
edition,
so.
A
B
Okay,
that's
a
good
question.
Unfortunately,
our
blockchain
platform,
because
of
the
compute
resources
that
it
requires,
is
not
available
as
a
as
a
always
free
service.
You
can
get
a
30-day
free
trial
and
then
you
can
migrate
that
trial
to
to
a
paid
license,
but
are
a
paid.
You
know
service
offering,
but
we
don't
have
this
available
as
a
free
offering
at
the
moment.
B
Yeah
we've
been
monitoring,
cactus
we've
not
been
doing
anything
with
it
at
the
moment.
Over
ledger
is
handling
this
at
a
you
know,
sort
of
a
a
lot
higher
level-
I
guess
and
and
we're
basically
relying
upon
them
to
provide
this
interoperability
with
things
like
ethereum
or
corda
or
the
like.
So
and
I
don't
know
a
ton
about
their
offering,
I
I
will
have
to
admit
so,
but
I
know
we
have
customers
who
are
using
this
to
be
able
to
integrate
our
our
blockchain
platform
with
other
other
blockchain
networks.
A
C
Yeah
hi
hi.
Can
you
guys
hear
me?
Yes,
you
sound
great
hi
thanks!
Thank
you.
So
I
was
just
wondering
if
it
would
be
possible
to
separate
the
the
business
logic.
Smart
contract
automation,
script,
essentially
from
where
the
oracle
blockchain
runs.
So
you
can,
you
can
have
we
don't
want
to
deal
with
the
oracle
maintenance
like
this
is
a
great
platform,
so
we
want
to
maintain
that,
but
we
want
to
keep
the
the
the
smart
contract
logic
and
the
affiliated
data
in
our
own,
our
own.
C
You
know
on-premise
database,
so
there
has
to
be
some
way
of
you
know
port
communication
over
some
tcp
port
connecting
to
to
oracle
database.
Where
you
can,
you
know,
leverage
the
the
blocks
running
on
the
on
the
oracle
cloud.
Is
this
kind
of
setup,
hybrid
setup
possible,
so
yeah?
I
can
have
a
full
control.
B
Over
yeah,
well,
you
have
full
control
over
the
smart
contract.
That's
that
that's
just
standard
fabric
behavior,
the
the
unique
part
here
that
we
provide,
as
I
say,
is
this
sort
of
data
pump
into
the
oracle
database.
So
the
fabric
doesn't
use
well,
our
our
version
of
fabric
says
it
doesn't
use
a
client
server
database.
So
you
can't
run
your
smart
contract
in
the
cloud
and
have
it
use
a
database.
That's
in
your
data
center
right!
That's
all.
C
B
B
A
C
Thanks
john,
I
just
want
to
follow
up
on
that
question
from
umit.
I'm
pretty
sure
he's
referring
to
the
external
chain
code
model,
that's
available
in
fabric
2.0,
where
changer
doesn't
have
to
be
deployed
to
the
pr
at
all.
It
can
be
run
somewhere
else
and
then
just
need
to
be
provided
the
endpoint
url
to
the
to
the
chaincode
spec
on
the
pier
to
be
deployed.
That
way.
B
B
So
what
another
thing
that
we
we
encountered
was
that
customers
want
better
control
over
the
access
to
the
assets,
to
the
what's
their
story
in
their
blockchain.
So
we
we
provide
a
what
we're
calling
a
fine
grain
access
control
list.
So
this
is
a
library
of
smart
contract
functions
that
can
be
used
to
maintain
access,
control
lists
and
these
assets
control.
This
can
be
applied
virtually
to
almost
anything
they
can
be
applied
to
the
invocation
of
an
operation
on
your
smart
contract.
B
They
can
be
used
to
control
access
to
specific
assets,
and
all
this
stuff
is
maintained
in
the
ledger.
So
you
have,
you
know,
complete
visibility
of
the
kinds
of
access
control
lists
and
who
can
do
what?
Who
can?
Who
can't
do
things
so
it
is
stored
in
the
world
state
database,
and
so
you
use
these
functions
inside
your
smart
contract
to
be
able
to
manage
the
access
to
the
assets
that
your
smart
contract
is
using.
B
So
the
app
builder-
this
is
what
I
want
to
get
a
bit
into.
So
this
is
this:
is
our
console
showing
up
our
developer
tools,
so
we
provide
you
know
as
part
of
it.
We
provide
a
set
of
examples.
We
provide
tools
to
be
able
to
interact
with
your
your
smart
contract,
so
a
lot
of
that's
done
through
either
the
app
builder
visual
studio
code
extension.
So
we
have
an
extension
for
vs
code
that
you
can
use
that.
B
B
We
make
it
really
easy
to
onboard
low-tech
members,
so
they
there's
a
ability
within
our
platform
to
be
able
to
onboard
client
organizations
that
don't
have
their
own
infrastructure,
so
they
they
rely
upon
the
infrastructure,
that's
by
one
of
the
other
members
of
the
organizat
of
the
network,
and
then
these
are
what
we
call
client
only
and
that
that
helps
a
lot
of
cases
where
not
every
member
wants
to
bring
their
own
infrastructure
and
bring
their
own
compute
resources.
Basically
to
to
manage
an
instance.
B
B
So
you
can
deploy
the
the
control
plane
vm
and
then
you
deploy
more
copies
of
that
vm
as
workers
that
are
going
to
be
used
to
deploy
your
your
fabric,
instances
and
your
fabric
components,
and
it
supports
a
variety
of
different
shapes.
And
so
you
see
typically,
what
happens
is
if
you
want
an
enterprise,
then
you
you
create
a
three
plus
one
vms,
so
three
vms
for
peers
and
cas
and
the
like,
and
one
vm
for
smart
contract
deployment.
B
So
this
shows
the
platform
manager
vm,
that's
our
control
plane,
so
we
can
manage
instances.
You
know
it
locally
that
you
provide
the
vms,
it
could
be
in
the
data
center.
Basically,
all
we
need
is
access
to
the
the
connection
between
our
container
and
our
vm
and
a
network
connection
to
the
instance
vm,
which
is
where
the
data
plane
runs.
B
So
this
is
showing
a
little
bit
more
into
our
app
builder,
so
you
can
see
over
the
right
here.
This
is
showing
some
asset
definition.
So
in
the
middle
here
is,
the
asset
is
called
a
distributor.
It's
got
a
property,
so
it's
got
its
id,
there's
a
bunch
of
properties
on
the
properties
or
assets
properties
on
the
asset
fields.
So
you
have
things
like
you
know.
This
has
got
products
to
be
shipped.
It's
a
number
product
shipped
is
also
a
number
of.
B
It's
got
a
minimum
value
of
three,
so
you
can
see
there's
a
variety
different
validations
here
that
can
be
provided
as
well.
As
you
know,
different
data
types
that
are
supported
for
the
various
properties
of
an
asset
so
from
this
file,
then
you
can
basically
then
scaffold
a
project,
so
this
is
all
supported
within
vs
code.
We
also
provide
command
line
interface
to
provide
these
same
operations
then
from
this
tool
as
well.
B
We
can
then
deploy
to
a
hyperledger
fabric,
local
instance,
or
we
can
deploy
to
a
cloud
instance,
all
that's
supported
from
the
visual
studio
code
extension.
If
you're
running
locally,
you
can
even
do
you
know
a
line-by-line
level
debugging
of
your
smart
contract.
We
don't
support
that
in
the
in
the
when
deployed
to
the
cloud,
only
only
to
do
the
local
instance
at
the
moment,
yeah.
B
B
B
We
take
care
of
the
persistence
of
it,
so
you
treat
these
things
as
as
objects,
so
these
assets
when
you
in
your
smart
contract,
you
simply
say
I
want
to.
I
want
to
get
this
asset
by
its
id.
You
don't
get
back,
you
know
adjacent
or
whatever
you
get.
You
get
back
an
actual
object
in
that
chain
code
language,
so
at
either
a
go
object
or
a
typescript
object,
and
then
so
that's
what
you
deal
with
and
then,
when
you're
done
updating
the
object.
B
B
Something
to
say
we
recently
added,
it
was
tokenization
support,
so
here's
an
example
of
an
asset.
It's
called
my
red
coin,
it's
a
type
of
token
it's
fungible
and
it's
fractional
and
so
and
as
well
divisible.
So
these
are
all
operations
that
can
be
formed
in
this
token
and
we
provide
all
the
code
to
implement
all
these
operations.
B
B
Is
we've
updated
the
the
chaincode
operation
and
commit
validation
code
to
support
the
ability
to
be
able
to
avoid
mvcc
errors?
So
when
you,
when
you
do
deal
with
tokens,
oftentimes
tokens
are
accessed
multiple
times
in
a
block
and
typically
in
fabric,
that
creates
an
mvcc
error.
What
we've
done
is
we've
allowed
your
tokens
to
have
numeric
fields
that
we
identify
and
then
what
we
do
is
when
you
create
operations
against
those
we
create
and
store.
B
B
B
So
here's
an
example:
you
can
token
actions.
You
can
say
I
want
to
issue
tokens,
what
channel
that
team
code
was
on
and
then,
when
you,
when
you
do
this,
we
also
then
check
and
collect
your
queries
and
stuff
like
that,
the
the
parameter
values
and
things
so
we
provide
a
little
screen
to
be
able
to
capture
that
information
so
where,
where
we're
going,
is
more
work
on
tokenization,
especially
supporting
for
nfts.
So
that's
a
one
of
our
things
on
our
next
plan
to
release.
B
You
know
we
we're
trying
to
say
what
we're
trying
to
do
is
make
the
developer
and
administrators
life
easy.
So
the
more
things
we
can
do
to
make
it
easier
for
them
to
be
able
to
integrate,
to
be
able
to
write
their
training
and
test
their
chain
code
to
be
able
to
make
sure
that
their
networks
are
deployed
properly
and
the
like.
Those
are
the
things
that
we
sort
of
focus
on
so
on
the
development
side.
Also
on
the
operations
side.
B
One
of
these
we're
looking
at
is
to
provide
something
like
the
operation
system
chain
code
that's
been
proposed,
so
we've
been
talking
to
that
team
a
little
bit.
We
would
like
to
incorporate
that
into
our
console,
so
you
could
add
new
organizations
remove
organizations.
You
can
do
all
that
on
chain,
as
opposed
to
the
current
mechanism,
which
is
effectively.
You
know
a
whole
lot
of
out
of
band
communication
and
then,
as
well
say
we
are
upgrading
to
fabric
2.2.
That
should
be
done
this
month
or
next.
B
B
So
that's
something
we're
looking
at
is
providing
an
alternative
to
bdb
is
to
use
oracle
database
for
state
database,
we're
looking
at
say.
You
know
ordering
services,
so
we've
got
some
group
within
oracle.
That's
looking
at
bft
consensus,
algorithms
in
particular,
smart
bft
or
libra
bft,
and
trying
to
do
a
formal
proof
on
that
to
verify
that
that
it's
it's
provably
correct.
B
A
B
A
C
C
B
C
B
A
Perfect
and
the
other
one
I
want
to
kind
of
just
touch
base
on
todd.
I
know
you've
done
a
great
job
going
through
this,
but
gopi
had
asked
a
question
about
you
know
the
versions
of
hyperledger
fabric
that
are
supported,
and
so,
let's
just
clarify
that
for
everyone
on
the
call
here
you
know
what's
currently
supported
today
in
the
roadmap.
What's
going
to
be
supported
in
about
a.
B
B
C
Hello,
this
is
gopia
thanks
for
that
information
yeah,
I
do
understand
you
are
going
to
do
it
behind
the
scenes,
since
the
upgrades
and
that
would
have
impact
on
refactoring
the
code,
because
there
are
going
to
be
significant
improvements
in
two
or
two.
That's
why
my
question
was
to
know
when
it's
being
done
that
way,
customers
could
be
aware
of
when
they
could
plan
for
a
code.
Enhancement
on
that.
B
Yeah,
but
for,
as
I
said
during
the
upgrades,
we
will
take
care
of
that
automatically,
although
there
will
be
some
things
because
of
changes
in
fabric
where
there
may
be
changes
that
have
to
be
taken
place
in
your
in
your
smart
contract.
There's
there's
not
a
lot.
We
can
do
about
that
and
especially
if
you
want
to
make
use
of.
Obviously
any
new
2.2
features
you'd
have
to
make
changes,
but
otherwise,
if
the
smart
contract
will
100
2.2,
we
will
take
care
of
the
upgrade
and
things
will
just
run
just
fine.
B
So
we've
been
we've
been
testing
that
extensively.
We
want
to
make
sure
that
we
don't
break
a
whole
lot
of
cloud
instances
but
yeah.
So
we
that's
that's
to
say,
that's
a
huge
advantage.
We
believe
is
that
you
know
you
don't
have
to
worry
about
the
upgrades.
We
take
care
of
that
well,
to
the
extent
that
we
can.
C
Got
scenarios
yeah,
that's
fair
enough.
Thank
you
and
just
one
other
question.
I
have
some
interesting
information
so
about
the
interoperability.
You
have
one
for
ethereum
and
with
other
blockchain
frameworks,
any
any
time
frame
on
when
the
interoperability
would
be
available.
With
you
mentioned
someone
with
ethereum,
which
I
could
see
that
about
the
other
blockchain
frameworks
also.
B
Yeah,
that's
that's
where
overledger
comes
in
so
over
ledger,
as
I
say,
provides
a
solution
that
allows
you
to
be
able
to
integrate
different
blockchain
networks
and
they
support
our
our
fabric
instances.
So
that's
that's
the
extent
of
I
guess
I
would
say
the
interoperability
at
the
moment
for
two
different
ones.
As
you
mentioned
already
ethereum.
Obviously
you
know
we
can
run
solidity.
Smart
contracts
and
stuff
like
that.
Yeah.
C
B
B
So
you
need
something
to
be
able
to
with
your
ca.
You
need.
You
typically
need
integration
with
some
kind
of
identity
management
system,
so
we
did
it
with
idcs
and
ldap
for
our
ee
and
a
and
microsoft
ad
and
we're
looking
at
what
we
can
do
with
divs.
So
we
we
have,
we
have
not
tried
it.
I
think
we've
I
think.
We've
got
some
customers,
though,
who
tried
using
in
indy
with
fabric,
but
we
don't
have
that
support
yet,
but
clearly
that's
something
that
we
wanted.
We
want
to
look
at.
C
B
No,
no
we're
going
to
speak.
We're
not
we're
not
supporting
wallets
at
all.
So
if
you
want
to
do
something
along
that
lines
to
be
able
to,
you
know
manage
your
own
certificates
and
stuff
like
that.
You
can
but
we're
not
providing
anything
that
lines
we're
basically
using
the
existing
identity
management
to
be
able
to
say
who
can
do
what?
So
you
get
a
set
of
roles
to
be
able
to
perform
things
and
so
like,
if
you're
an
admin,
a
role
in
the
identity
management
system,
then
you'll
get
admin
capabilities.
C
C
A
C
B
Or
no,
no,
it's
just
another
cloud
service,
so
you
use
cloud
credits
and
we're
it's
based
upon
the
a
number
of
ocpus.
Basically
that
you
have
so
you
know
it's
our
normal
cloud-based
pricing
and
it's
just
offered
another.
So
I
don't
there's
no
contract
that
I'm
aware
of
that.
You
have
to
do,
but
you
do
you.
After
the
30-day
free
trial,
you
would
need
to
get
purchase
cloud
credits
and
to
be
able
to
continue
using
your
instance.
C
B
Be
yeah:
if
you
go
to
the
the
this
where
it
says,
try,
obp
and
oracle
cloud
free
tier
yeah,
you
should
be
able
to
get
the
information.
The
pricing
there.
It's
it
turns
out
that,
for
like
a
small
configuration,
it's
several
hundred
dollars
a
month.
Something
like
that.
So
I
mean
it's
not
particularly
expensive,
but
it
also
depends
upon
the
size.
A
B
Yeah
so
zoe
offers
an
nft
solution
based
upon
our
platform,
so
they're
a
partner
of
ours
and
that's
who
we're
recommending
right
now
for
nfts,
but
but
we
also
know
customers
want
to
do
you
know
nft
development
and
normal
asset
development
like
so.
That's
why
we're
putting
this
stuff
into
app
builder,
but
right
but
but
zoho
right
now
is
our
our
go-to
partner
for
nfts.