►
From YouTube: Extending the Operations Smart Contract for Hyperledger Fabric to Support Consortia G... Todd Little
Description
Extending the Operations Smart Contract for Hyperledger Fabric to Support Consortia Governance - Todd Little, Oracle
As consortium blockchains move to decentralized governance, the complexity and cost of operations rise significantly for adding members, updating chaincodes, channel management. These require policy definitions, multi-party approvals, implementation - plus the ability to audit it all. Today it's all out-of-band, but on-chain automation can simplify network scale out & reduce costs. The Operations Smart Contract (OpsSC) for Fabric 2.x is a Hyperledger Labs project for on-chain governance focused on the Fabric 2.0 chaincode lifecycle and channel configs. It enables the chaincode updates to be agreed and recorded in the ledger, but it doesn’t handle membership governance - who can be added, what rights do they have, their information sharing, and overall policy management is missing. This session will discuss ideas for extending the OpsSC to address these issues of consortia governance.
To learn more about Hyperledger, the open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments. Which serves as a neutral home for various distributed ledger frameworks including Hyperledger Fabric, Sawtooth, Indy, as well as tools like Hyperledger Caliper and libraries like Hyperledger Ursa click here: https://www.hyperledger.org/
Session Details & Slides (if available)- https://sched.co/j3ep
Access All Sessions: https://events.linuxfoundation.org/hyperledger-global-forum/program/schedule/
----
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
Good
morning,
good
afternoon,
good
evening,
all
appreciate
you
joining
this
session.
What
I'm
gonna
be
talking
about
today
is
a
proposal
we're
making
to
extend
the
operation
smart
contract
for
hyperledger
fabric
to
support
consortium
governance.
So
this
is
a
proposal
for
work
activity
to
be
done,
something
that
we're
at
oracle
definitely
interested
in,
because
we
see
consortia
formation
and
governance
as
being
a
major
issue
when
it
comes
to
blockchains.
A
So
what
I
want
to
cover
today
is
a
little
bit
of
just
a
really
brief
intro
about
what
I
said.
What
is
a
consortia
a
little
bit
about
the
what
the
operations
smart
contract,
hyperledger
labs
project
is
all
about,
and
then
some
information
about
consortium
governance,
some
voting,
enhancements,
we'd
like
to
see
and
as
well
then
the
summary.
A
A
But
then
you
lose
much
of
the
capabilities
and
much
of
the
advantages
of
having
a
decentralized
environment.
So
a
consortium
basically
is
just
an
association
of
businesses,
so
it's
one
or
more
businesses
that
want
to
get
together
and
be
able
to
conduct
business
together
for
some
mutual
benefit
that
consortium's
been
around
for
a
long
time.
That's
nothing
new!
So
what
we're
looking
at
is
how
do
we
solve
some
of
the
issues
associated
with
forming
a
consortium?
There's
a
number
of
them
that
are
business
related
issues.
A
A
A
lot
of
blockchains
have
that
right
now,
where
there's
one
organization
that
essentially
formed
the
network
and
it's
roughly
in
control,
what
we'd
like
to
propose
is
something
that's
a
bit
more
decentralized
than
that
and
as
well
we've
just
like.
We.
We
think
that
decisions
and
any
actions
that
take
place
in
the
blockchain
network
need
to
be
auditable.
So
they've
got
to
be
recorded
in
the
le
on
a
ledger
or
some
place
where
they
can
be
verified.
A
So
a
little
bit
of
introduction
to
the
operation,
smart
contract
or
opssc.
This
is
a
hyperledger
labs
project
that
was
contributed
by
hitachi.
There
was
a
session
on
this
or
a
demo
of
this
on
tuesday.
I
believe,
and
what
it
consists
of,
is
several
several
different
components.
So
the
first
two
major
components
are
there's
two
smart
contracts.
One
smart
contract
is
used
to
maintain
the
chain
code,
life
cycle
or
manage
the
chainsaw
machine
code,
lifecycle
and
another
one
to
manage
channel
management.
A
So
adding
members
to
channel
that
sort
of
those
sort
of
operations
and-
and
largely
this-
is
all
around
workflow.
So
it's
trying
to
automate
and
and
simplify
these
operations,
which
are
right
now
largely
manually,
done
and
have
to
be.
You
know
done
by
each
organization.
That's
that's
participating!
So
what
these
these
smart
contracts
do.
Is
they
manage
the
state
transition?
So
you
know
from
a
proposing
of
a
chain
code
deployment
to
or
proposing
new
member
to
a
channel
or
changing
the
channel
configuration.
A
A
So
when
an
agreement
is
made
to,
let's
say,
deploy
on
a
or
upgrade
a
new
chain
code,
the
agent
gets
notification
that
when
sufficient
members
have
agreed
to
this,
and
so
they
meet
the
the
policy
associated
with
updating
or
deploying
a
new
chain
code,
and
then
the
agent
does.
Is
it
automates
that
for
each
individual
organization?
A
So
that's
an
optional
thing.
You
don't
have
to
use
that,
but
the
agent
then
definitely
takes
care
of
of
automating
much
of
the
operations
and
then
there's
also
an
api
server.
So
the
api
server
is
what
manages
the
state
of
the
workflow.
So
it
provides
a
set
of
rest
apis
to
be
able
to
access
those
chain
codes,
the
the
chain
code
for
life
cycle
chain
code
and
the
channel
management
chain
code,
and
what
it
does
is.
A
It
basically
accepts
things
like
proposals
to
do
some
of
these
operations,
and
then
it
also
accepts
boats
from
the
various
members
and
again
it
runs
as
a
separate
server
in
each
organization's
instance
or
somewhere
within
their
organization.
And
again,
I
want
to
focus
to
say
that
this
is
focused
largely
on
automation,
not
on
enforcement.
A
I'll
talk
a
little
bit
about
enforcement
because
some
of
that
will
require
some
changes
to
the
way
fabric,
manages
the
decision-making
process
and
agreements
so
for
chain
code
operations
and
the
current
ops
sc
is
that
an
organization
proposes
a
new
or
upgraded
chain
code,
but
calls
its
api
server.
So
it
makes
a
request
to
the
api
server.
A
The
api
server
in
turn
then
invokes
the
chain
code
up
the
channel
channel
or
that
smart
contract
chain
code
to
record
the
proposal
once
that
proposal
is
recorded,
the
operation
system
chain
code
chain
code
emits
an
event
and
that
event
is
listened
to
by
all
the
organizations
that
are
part
of
the
consortium
and
then
operates
on
those
events.
So,
in
the
case
of
let's
say
it
was
a
proposal
to
you
know
to
update
a
chain
code
as
each
organization
then
votes
for
that.
A
That
information
is
also
done
by
invoking
their
api
server,
which
which
records
the
vote
using
the
op
c
chain
code
and
as
well.
Then
the
op
c
system
chain
code
emits
an
event
for
each
of
those
such
that,
once
enough
votes
have
been
achieved
to
be
able
to
meet
the
the
policy
associated
with
upgrading
and
deploying
new
chain
code
that
those
operations
can
proceed
automatically.
A
So
let's
say
once
the
vote
passes
the
organization
one
agent
will
download,
install
and
approves
and
commits
the
chain
code
and
the
other
two
to
agents
and
say
in
the
three
organization
network
would
download,
install
and
approve
the
chain
code
as
well,
and
then
this
takes
this
happens
automatically,
but
based
upon
once
the
necessary
criteria.
Voting
has
been
met.
A
Channel
operations
operate
in
a
similar
fashion,
so
one
organization
proposes
a
config
update
in
a
machine
in
a
human,
readable
format
which
is
important,
and
it
does
that
by
then
calling
its
api
server
with
this
human
readable
update
proposal.
The
api
server
then
invokes
the
the
channel
chain
code
to
record
the
proposal.
It
converts
that
proposal
into
a
configuration
transaction
and
then
he
also
emits
an
event
so
that
all
the
other
organizations
that
are
associated
with
the
smart
contract
can
receive
the
notification
that
a
proposal
has
been
made.
A
Once
sufficient
votes
have
been
recorded,
then
one
of
the
agents
will
take
that
converted
configuration
transaction
and
then
I
perform
the
channel
update
operation.
So
that'll
include
having
all
the
various
signatures.
That'll
be
part
of
what
the
voting
operation
is
is
to
record
the
signature
of
each
organization
as
they
approve
the
vote.
A
So
so,
what's
missing,
so
what's
missing
from
our
perspective,
is
this
notion
of
consortium
governance
so
who
are
the
members
of
the
consortium?
What
are
they
allowed
to
do?
How
do
you
add
or
remove
or
alter
the
what
members
can
do
so
all
this
issue
about
membership
and
what
they're
able
to
do
and
and
who's
responsible
for
what?
So
we
think
that's
one
major
piece
and
I'll
get
into
more
about
what
we
our
proposal
is
to
address
this
and
as
well.
We
believe
that
we
need
some
voting
enhancements
right
now.
A
A
A
So
what's
needed,
then,
are
some
extensions,
then,
to
the
opsi
system
chain
code
to
be
able
to
support
these
governance
operations.
And
again
I
say
this
is
largely
focused
on
automation.
Supporting
you
know.
The
enforcement
of
it
is
something
that
will
have
to
be
done
as
well
with
not
only
within
the
chenko,
but
also
inside
a
fabric
itself
and
I'll
get
into
some
details
of
what
kind
of
enhancements
we
need
to
be
able
to
support
that
in
a
minute.
A
So
what
we're
trying
to
do
is
let's
say,
move
from
these
oftentimes
these,
what
we
call
founder-led
consortium
to
a
more
decentralized
governance
and
initially
not
going
to
change
the
enforcement
policies
within
fabric.
Ideally,
we
want
to
do
that
such
that
we
can
provide
some
of
these
things,
like
potentially
veto
capabilities
or,
as
I
say,
asymmetric
voting
capabilities-
that's
not
necessarily
part
of
the
initial
proposal,
but
something
that
we
believe
ought
to
be
done
so
there's
to
say:
there's
nothing
that
we're
proposing
right
now
to
prevent
members
from
using
standard
fabric
capabilities.
A
A
Something
else
is
that
we
want
to
support,
as
I
mentioned
before,
is
that
that
all
members
are
not
necessarily
equal,
so
yeah.
In
many
cases
you
say,
you'll
have
consortiums
where,
for
whatever
reason,
some
members
have
more
rights
or
different
rights
than
others,
and
so
we
want
to
be
able
to
support
that
kind
of
capability
in
the
voting
mechanisms
and
and
how
it's
determined
as
to
what
members
can
propose
and
do
what
so
we
want
to
support.
A
You
know
say
non-voting
members,
so
members
who
are
basically
they
don't
get
a
say
they
have
to
go
along
with
whatever
the
agreements
are
that
are
made
by
the
voting
members
and
as
well.
You
know
we
the
proposals
to
be
able
to
change,
who
can
do
what,
whose
members
are
those
sorts
of
things
are
something
that
we
also
feel
should
should
be
supported,
and
then
again,
as
I
mentioned
earlier,
that
all
these
decisions
and
all
these
actions
need
to
be
recorded
in
the
ledger.
So
they're
auditable
and
it
can
be.
A
So
one
of
the
issues
is
one
of
the
probably
the
major
issues
in
forming
the
course
distortion
is.
How
do
you
exchange
the
information
right
now?
There
are
no
mechanisms
to
do
that
per
se,
so
to
form
the
consortium
everything's
got
to
be
done
out
of
band,
meaning
that
it's
not
recorded
in
the
ledger.
A
There's
as
there
is
no
network,
yet
they're
still
forming
the
network,
and
so
what
we're
proposing
is
that
this
be
done
partially
out
of
band
and
I'll
explain
a
little
bit
more
about
that
in
a
second,
but
it
has
to
do
with
a
bootstrapping
issue.
How
do
you,
how
do
you
put
something
in
place
that
people
can
use
to
come
to
agreement
before
before?
Everything
is
settled
so
and
then
you
know
what
information
has
to
be
exchanged,
we
believe
at
least
minimally
for
each
member
organization.
A
We
need
the
msp
information,
so
we
can
verify
signatures
and
the
like,
and
we
also
will
need
some
information
about
the
ordering
service
network
that
the
participants
will
use
and
then,
finally,
in
terms
of
you
know,
for
the
consortium
members,
what
actions
are
they
each
allowed
to
perform?
So
this
is
something
that
has
to
get
decided
up
front
and
a
proposal
made
to
be
able
to
to
create
this
kind
of
a
network.
A
So
what
is
being
proposed
is
that
when
somebody
proposes
the
formation
of
consortia-
or
you
know
knows
how
do
you
bootstrap
a
consortium,
there's
going
to
be
a
single
member
that
at
least
or
in
theory
a
member?
That's
what
we're
calling
the
proposer,
and
so
the
proposer
is
the
one
that
would
create
the
ordering
service
and
the
initial
ordering
service
nodes.
It
would
create
the
ops
channel.
So
this
is
the
channel
over
which
the
various
consortium
actions
would
be
recorded
and
voted
on
deploys
the
two
chain
codes.
I
mentioned.
A
Actually
the
three
chain
codes
now,
because
we're
proposing
adding
an
additional
one.
There's
the
chain
code,
ops,
there's
the
channel,
ops
and
then
there'd
be
a
consortia
ops
chain
code
that
would
be
deployed
as
well
for
managing
these
consortium
operations
and
then,
finally,
the
the
proposer
starts
its
own
agent
and
its
own
api
server.
A
A
A
Obviously
there's
other
mechanisms
that
he
used
here
to
exchange
that
email
just
a
proposed
mechanism.
There
are
probably
other
more
secure
mechanisms.
That
would
be
desirable,
but
this
is
at
least
initial
go
and
then,
as
the
other
organizations
will
get
this
information
they'll
connect
to
the
api
server
and
they'll
provide
their
msp
information
and
then
the
agent
then
will
then
update
the
ops
channel
with
their
information
and
have
them
join
that
channel.
A
Finally,
the
other
organizations
they
say:
they'll
use
the
the
initial
members
or
the
proposers
api
server.
They
will
download
their
control
and
perform
formation
proposal
and
use
the
information
in
there,
such
as
the
osn
information,
the
the
proposers
msp
information
that
sort
of
stuff
to
configure
a
minimal
instance
in
their
network
or
in
their
in
their
environment.
A
And
then,
if
they
decide
they're
going
to
join
the
network,
they
would
as
well
provide
their
msp
info
through
the
initial
members
api
server.
So
once
all
that's
once
that's
been
done,
then
the
initials
members
agent
can
add
the
msp
information
to
the
the
opposite,
ops,
channel
and
install
then
the
ops
game
code
and
start
up
a
local
opposite
agent.
Api
server.
A
What
we're
thinking
in
terms
of
what
would
be
in
this
initial
consortium
formation
proposal
would
be
some
information
about
the
consortium
itself,
so
this
would
be
things
like
the
name
description,
a
list
of
who
the
initial
organizations
are
that
are
being
proposed.
What
the
voting
policy
is
for
the
consortium.
A
So
this
is
like
what
is
the
policy
that
and
what
that
has
to
be
met
to
be
able
to
change
the
configuration
of
the
consortium
and
then
that's
in
terms
like
you
know,
like
voting
policies
and
other
information,
but
then
we'd
also
have
a
membership
voting
policy.
So
what's
it,
what
is
it
required
by
the
existing
members
to
be
able
to
add
or
remove
members?
So
that
may
be?
That's
we're
envisioning
that
as
potentially
a
separate
policy
and
then
for
each
organization
what's
required,
then
is
we
would
need
the
name?
A
We
obviously
want
some
contact
information
because
the
email
address
of
administrators
or
operators,
what
number
of
votes
are
provided
if
we're
using
asymmetric
voting
and
what
permissions
they
have
are
they
allowed
to
perform?
You
know
a
chain
code
upgrade:
are
they
allowed
to
do
any
other
sort
of
operations?
That
would
all
be
listed
as
a
set
of
permissions
that
that
each
organization
is
allowed
and
then
and
also
as
part
of
the
initial
proposal,
the
proposing
organization
would
need
to
provide
its
msp
info.
So
the
other
organizations
can
then
join
the
ops
channel.
A
So
a
little
bit
also
as
well
right
about
about
voting.
So
you
know
voting
is
basically
an
issue
about.
How
is
it,
how
is
agreement
achieved
so
right
now
in
fabric
fabric,
uses
signature
policies
for
approving
or
endorsing
or
allowing
the
submission
of
transaction
and
committing
those
transactions,
as
well
as
for
things
like
channel
config
updates,
so
the
config
tx
transactions
and
a
signature
policy
is
is
nothing
more
than
an
expression
of
one
or
more
principles.
A
So
as
an
example,
here
I
have
an,
and
so
it
says
this
is
an
end
of
org,
one,
member
and
or
two
member.
So
that
means
that,
if
that's
the
policy,
then
both
a
member
of
org
one
and
a
member
of
org
two
would
need
to
sign
the
the
proposal.
There's
a
here's
a
more
complicated
one
where
we
have
and
of
either
org,
one
or
or
two
signing,
as
well
as
org,
three
admin
signing.
A
So
what
is
missing
so
in
in
the
operation
system
chain
code
itself
related
to
voting,
there's,
no
ability
to
abstain,
there's
no
ability
to
veto-
and
you
know
abstention-
is
valuable
in
terms
of
being
able
to
know
whether
an
organization
is
voted
or
not.
So
it
would
be
valuable
to
have
recorded
as
part
of
the
voting
operations
that
some
organization
abstained,
just
to
know
that
they
have
voted
that,
then
they
don't
really
have
an
issue
with
whatever
the
decision
is.
A
You
still
need
to
support,
whatever
the
the
policy
is,
but
they're
just
indicating
that
this
is
something
that
was
not
of
interest
to
them
or
they
want
to.
Let
people
know
they're
not
going
to
vote
for
or
against
it.
The
current
thing
only
supports
a
single
vote
for
organization,
basically
a
signature
and
there's
to
say:
there's
no
veto
capability,
so
in
some
forms
of
consortiums
there
are
certain
members
that
would
have
veto
capabilities.
A
I
mean,
if
you
look
at
something
like
you
know:
the
united
nations,
not
necessarily
that's
a
consortia,
but
certain
organizations
or
members
have
veto
capabilities
and
others
do
not
in
fabric
then
there's
also,
then
we
need.
We
would
need
additional
changes,
then
to
be
able
to
support
additional
voting
policies
here
so
right
now.
The
only
thing
that's
supported
in
fabric
is
what
we
would
call
a
four
vote.
A
So
what
we'd
like
to
propose
in
in
fabric
is
that
we
and
actually
in
the
operation
system
chain
code,
is
the
ability
to
support
these
consortiums,
the
formation
of
them
and
the
administration
of
them,
so
that
would
entail
creating
another
chain
code
to
support
consortium.
Just
like
there's
a
chain
code
for
channel
operations
and
a
chain
chenko
for
chain
code
operations.
We'd
have
another
one
for
formation
and
administration
of
consortia.
A
A
So
there
are
changes
that
will
be
required,
both
in
ops
c
as
well
as
in
fabric,
and
then,
ideally,
it
would
be
helpful
to
take
something
like
the
sc
agent
right
now
and
integrate
that
with
a
deployment
tool
such
as
something
like
hyperledger
cello,
that
can
be
used
to
then
create
the
initial
deployment,
because
right
now
to
create
this
a
network.
It's
largely
up
to
each
individual
member
to
take
care
of
all
the
all
the
manual
steps
that
have
to
be
taken
with
something
like
integrations
with
the
op
system
code
and
cello.
A
So,
in
summary,
let's
say
we
think,
and
our
experience
has
been
that
consortium
formation
is
difficult
and
often
has
been,
you
know,
led
by
a
single
organization.
So
it's
not
particularly
decentralized
we'd,
like
the
formation
and
management
of
the
consortium
to
be
much
more
decentralized
and
and
much
more
automated,
because,
right
now
largely
to
say
it's
a
manual
set
of
steps.
A
We
want
to
leverage
the
existing
operation
system
chain
code
as
it
provides.
You
know
much
of
what
we
needed
and
if
it's
a
model
that
we
believe
makes
sense
for
consortium
management
provides,
you
know,
say
the
mechanisms
to
be
able
to
automate
stuff
to
be
able
to
come
to
agreement
on
decisions
that
affect
the
network
and
that's
all,
that's
all
in
place
right
now.
A
What's
missing
is
sort
of
the
consortium
side
of
that,
and
especially
the
consortium
forming
portion
of
that,
and
you
know,
the
ultimate
goal
here
is
to
simplify
and
automate
the
the
formation
of
a
consortium
based
upon
hyperledger
fabric
to
join
in.
If
you
like,
to
comment
like
to
help,
do
whatever
you'd
like
there's
a
a
rocket
chat
channel
for
the
operation
system
chain
code,
the
link
is
provided
there
on
the
slide
and
as
well.
The
source
code
for
that
project
is
located
in
github
as
a
hyperledger
labs
project.
A
A
A
So
the
question
was
mahesh.
I
asked
is
oracle
to
provide
any
of
these
features
as
part
of
the
oracle
blockchain
as
a
service
or
oracle
blockchain
platform.
I
I
have
to
be
careful
here.
I
don't
have
a
safer,
harbor
statement
here.
All
I
can
say
is
that
we
are
proposing
this.
This
is
in
line
with
with
our
thinking
about
how
consortium
should
be
formed
and
managed.
I
obviously
I
can't
make
any
commitment
to
say
that
we're
going
to
provide.
A
A
What
kind
of
peter
asked
what
kind
of
storage
would
the
initial
out
of
bounds
out
of
band?
I'm
assuming
you
mean
bootstrap,
could
use.
So
this
is
the
idea
that
the
out-of-band
mechanism
is
is
what
we're
proposing
using
these,
these
temporary
credentials,
where
the
proposing
organization
would
grant
temporary
access
limited
access
to
its
api
server,
so
that
those
organizations
could
then
provide
the
information,
that's
necessary
to
bootstrap
the
organization,
so
that
would
all
be
stored
on
chain
and
initially
it
would
only
be
in
in
the
proposer's
network.
A
But
as
that
network
then
is
expanded
and
other
other
members
joined.
The
network
agreed
to
be
a
participant.
Then
they
would
automatically
get
a
copy
of
that
ledger
as
well.
So
there's,
no
really.
The
intent
here
is
there's
little
to
no
out
of
band
storage
that
that
all
the
storage
would
be
maintained
in
the
chain
code
operations
and
mark
mark.
Mark
williams
asks
how
it
handling
dropping
members
out
of
the
consortium
if
they
leave
again.
This
would
be
based
upon
the
the
voting
policies
that
are
for
the
consortium
membership
itself.
A
So
this
would
be
something
where
members
might
have
to
be
careful
that
you
don't
get
yourself
you
know
hit.
You
know.
The
issue
right
now
is
like
in
fabric.
If
you
have
an
endorsement
policies
is
that
every
organization
must
endorse
a
transaction
to
be
accepted
and
one
of
those
organizations
drops
out
you're.
You
can't
get
a
valid
set
of
signatures
to
be
able
to
perform
a
config
transaction
to
alter
the
the
channel
membership.
A
Besides
the
rest,
api
for
agents,
is
there
a
front
end
for
the
agents
being
open
sourced
at
at
the
moment?
There's
that's
not
part
of
the
ops
sc
system
chain
code
project,
but
I
could
envision
that
being
something
the
issue
there
is
that
that
probably
needs
to
integrate
in
with
whatever
sort
of
you
know
front
end
the
platform
that
you're
using
requires.