►
From YouTube: Sovrin: Public, Permissioned and Still Decentralized - Nathan George, Sovrin Foundation
Description
Lighting talk with Nathan George (Sovrin CTO) taking the audience through a high-level look at the Sovrin DLT, how it can be public/permissioned yet still decentralized, and why this is right for identity solutions.
----
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
I'm
gonna
talk
a
little
bit
about
a
system
called
sovereign,
which
is
built
on
top
of
the
code
base
of
hyper
ledger.
Indy,
that's
hosted
here
in
hyper
ledger.
Sovereign
is
a
system
that
does
digital
identity,
and
this
is
a
classic
cartoon
or
out
digital
identity
and
that
on
the
internet,
no
one
knows
you're.
A
dog
digital
identity
is
a
really
interesting
construct,
because
when
we
talk
about
identity
in
the
real
world,
we
often
talk
about
the
idea
of
who
someone
is.
And
how
do
you
know?
A
What
do
you
know
about
someone
that
tells
you
that
they
are
the
real
authentic
person
that
has
interacted
with
you
in
the
past?
So
here's
a
few
correlative
lastra
buttes
about
me
and
in
this
slide
deck
I
have
a
couple
of
links
to
places
where
you'll
also
see
this
same
biometric,
the
same
picture
to
verify
that
these
attributes
really
are
mine,
and
this
is
who
I
am.
But
when
you
start
talking
about
people
that
you've
only
met
online
people
that
you've
only
interacted
with
at
a
distance.
What
does
it
mean
that
they
have
continuity?
A
What
does
it
mean
that
they
present
themselves?
The
same
way,
what
does
it
mean
that
they
have
an
identity?
How
do
you
match
what
that
person
is
with
what
you
know
about
that
person
and
obviously
people
change
over
time?
You
know
these
attributes
weren't
true
about
me
some
years
ago
and
of
course,
the
things
that
I'm
working
on
will
change
over
time
as
well.
A
So
when
we
talk
about
sovereign
we're
talking
about
a
building,
a
global
platform
that
we
can
accomplish
digital
identity,
meaning
that
we
can
create
webs
of
trust
and
we
can
walk
those
webs
of
trust-
discover
things
that
we
have
confidence
in.
We
can
exchange
signed
and
verifiable
information,
which
sounds
a
lot
like
what
blockchains
do
doesn't
it?
A
You
know
we
have
cryptographic,
keys
and
we're
storing
state
and
we're
transforming
state,
but
it
turns
out
the
identity
problem,
although
it
has
a
lot
in
common
with
what
we
do
in
a
blockchain
has
a
lot
of
insidious
differences
with
what
we
typically
do.
When
we
talk
about
blockchain
and
hyper
ledger,
indie
and
sovereign
as
an
instance,
that's
deployed
globally
up
hyper
ledger.
Indie
deals
primarily
with
those
sorts
of
things.
A
This
is
the
basic
stack
model
that
we
use
for
sovereign
and
that
the
hyper
leader
Indy
implements
and
there's
some
interesting
things
about
what
happens
in
this
stack.
We
have
the
configuration
ledger
in
the
Poole
Ledger's
that
deal
with
kind
of
the
mechanics
of
a
blockchain,
but
we
also
have
a
domain
ledger
that
deals
with
the
sorts
of
information
that
you
need
to
do
to
in
order
to
exchange
identity
information.
A
But
you
don't
want
to
put
everything
on
the
blockchain,
because
the
blockchain
is
just
used
to
publish
things
globally
and
when
it
comes
to
identity,
identity
is
not
about
who
I
am
globally.
It's
about
who
I
present
myself
to
be
in
the
relationship
at
hand
right
you're,
not
the
same
person
with
your
family
that
you
are
with
your
business.
Colleagues
that
you
are
with
your
you
know,
political
associations,
that
you
are
in
other
interactions,
and
it's
not
that
you're
trying
to
be
duplicitous.
A
So
when
we
talk
about
the
second
layer
of
identity,
we're
talking
about
how
do
I
have
strong
authentication
or
how
do
I
know
that
you
are
the
same
unit
of
context
that
I
dealt
with
last
time
and
how
that
you
are
trying
to
present
the
same
unit
of
context
back
to
me
this
time.
I
knew
how
this
is
typically
accomplished.
At
a
website
is
a
username
and
a
password,
but
that
identity
doesn't
exist
in
the
users
domain.
A
A
Do
you
know
someone
personally
at
your
driver's
license
division,
but
nevertheless
we
trust
the
driver's
licenses
that
we
get
from
that
relationship
all
the
time.
So
this
basic
layer
of
trust
is
formed
by
being
able
to
exchange
signed
information
not
on
the
blockchain
but
being
able
to
validate
things
based
on
what
is
anchored
to
the
blockchain.
So
the
blockchain
isn't
performing
all
the
transactions.
It's
not
acting
as
the
system
of
record
or
as
a
source
of
truth.
A
It's
acting
as
a
route
of
trust,
so
I
don't
have
to
have
interoperability
with
every
system
of
every
issuer.
All
I
need
to
be
able
to
do
is
validate
the
credentials
based
on
the
protocol.
That's
established
in
hi
pearl
is
your
entity,
so
here's
some
of
the
code
base
that
we
use
in
order
to
do
this,
we've
been
working
on
the
hyper
laser
ursa
library,
which
I
hope
if
any
of
you
are
working
with
cryptographers
or
have
cryptographic,
teams
that
are
involved
in
blockchain
at
all
the
goop.
A
That's
working
on
ursa
is
a
really
great
group
and
there's
a
lot
of
interesting
things
going
on.
There.
We've
been
thinking
about
sponsoring
that
perhaps
the
shared
wallet
project,
so
if
shared
crypto
wallets
as
clients
to
block
chains,
is
something
that's
interesting
to
you.
Please
come
talk
to
me
about
that
and
then,
of
course,
the
things
in
green
and
blue
are
the
code
base.
A
That's
currently
hosted
under
hyper
ledger
Andy
and
the
tools
that
we
use
in
order
to
accomplish
the
platform
of
sovereign
and
there's
a
couple
of
pieces
that
are
very
particular
to
the
public
governance
of
the
sovereign
network
that
we
maintain
inside
of
the
sovereign
foundation.
Github
repository
all
of
it
under
the
Apache
2
license
we're
a
non-profit
foundation
that
supports
making
a
global
public
utility
for
identity
that
everyone
can
use.
There's
a
lot
of
new
stuff,
that's
going
on
too.
A
So,
if
you're
interested
in
getting
involved,
one
of
the
things
that's
really
great
about
high4
Ledger's,
we
have
lots
of
people
working
on
lots
of
different
things
and
we
get
along
and
we
get
a
lots
of
interesting
things
done.
So
please
plug
yourself
into.
What's
going
on
in
indy
and
we'd
love
to
have
you
there's
often
a
lot
of
confusion
about
what
sovereign
is
relative
to
what
hyper
ledger
india's
this
diagram
may
not
make
it
actually
clearer,
but
at
least
it
explains.
A
What's
going
on
you'll
notice,
we
have
a
lot
of
different
vendors
that
are
contributing
to
the
open
source
ecosystem
and
they
contribute
in
terms
of
building
things
for
the
code
and
that's
the
thing
that
you
see
a
lot
of
inside
of
the
hyper
ledger
community,
because
we're
primarily
focused
on
the
technology
for
the
code.
But
sovereign
is
also
working
to
accomplish
the
governance
of
a
system
that
can
work
at
scale
and
can
stay
decentralized
over
time.
And
so
there
is
an
independent,
sovereign
community.
A
The
way
we
need
it
for
individual
people
to
be
able
to
control
or
manage
their
relationships,
so
the
sovereign
community
facilitates
and
sponsors
that
effort
and
I
work
for
the
sovereign
foundation
is
CTO
and
I
do
a
lot
of
things
to
help
companies
that
are
trying
to
use
sovereign
and
are
trying
to
use
the
hyper
ledger
in
decode
base.
So
what
I
tell
everybody
who
needs
to
learn
the
system?
Is
you
come
you
use
my
time?
A
We
love
to
help
people
get
it
started
and
get
involved
in
the
community,
and
if
you
want
to
get
more
of
my
time,
then
give
me
more
of
yours
because
we
are
an
open
source
community.
So,
just
like
any
open
source
project,
you
can't
just
complain
about
something
without
having
some
work
to
do
to
fix
it,
which
brings
us
to
this
idea
of
decentralization
and
really
the
purpose
of
what
the
sovereign
foundation
is
for
is
even
if
you
have
a
system
that
can
be
strongly
specified
in
terms
of
its
rules.
A
And
anyone
can
audit
and
validate
that
the
the
permission
entities
are
acting
correctly.
You
don't
have
to
rely
on
those
permissions
for
the
day-to-day
operation
of
the
chain,
and
you
don't
have
to
rely
on
those
permissions
in
order
to
know
that
the
identity
is
yours
and
that
you
own
and
control
it.
A
What
you're,
relying
on
the
permissions
to
do
is
to
make
it
so
that
no
one
can
betray
the
rules
of
the
network
and
that
it
can
run
really
cheaply
and
efficiently,
because,
instead
of
having
to
use
proof
of
work
and
do
things
to
accomplish
global
scale
through
brute
force,
we
can
instead
leverage
the
permissioning
system
of
the
network
to
make
sure
it's
fully
BFT
to
protect
and
secure
your
keys
and
to
make
it
so
that
it
can
operate
at
a
higher
scale.
Even
though
we're
operating
in
a
fully
public
mode.
A
But
this
also
means
that
there's
some
entity
that
we
need
in
order
to
establish
that
those
rules
have
continuity,
because
if
it
was
just
someone
like
me
that
declared
that
this
was
so.
How
could
you
trust
that
it
wouldn't
change?
How
could
you
trust
that
I
wouldn't
change
my
mind,
because
I
wanted
to
move
on
to
a
different
project
or
a
different
idea,
and
to
do
this,
the
indie
community
doesn't
directly
control
the
code
that
exists
on
the
sovereign
network.
A
We
also
have
a
board
of
trustees
that
represents
the
users
interests
and
the
user
advocacy
that's
necessary
to
make
sure
that
their
interests
are
preserved
over
time.
And
then
we
have
lots
of
businesses
and
organizations
that
run
the
nodes
on
the
network.
That
are
the
the
permissioned
entities
that
are
the
validator
nodes,
and
all
of
these
parties
have
decision-making
power
inside
of
the
system
so
that
they
can
act
as
checks
and
balances
on
one
another
and
preserve
the
decentralization
of
what
goes
on.
A
So
we
talked
a
little
bit
about
the
idea
that
we
have
trustees
all
over
the
world.
We
have
technical
governance
members
all
over
the
world
for
the
technical
governance
board.
We
also
have
validator
notes
all
over
the
world
and
I
hope
that
some
of
you
are
noticing
that
your
geography
is
underrepresented
and
I
hope.
You
will
also
use
that
as
an
invitation
to
come
talk
to
me
about
what
you
could
do
to
maybe
get
involved
in
making
the
network
more
robust
and
helping
enhance
the
concept
of
defuse
trust
inside
of
sovereign.
A
A
We
are
clearly
trying
to
imply
that
the
software
that
manages
your
keys
and
helps
you
handle
your
digital
interactions,
has
a
responsibility
to
answer
to
you
and
only
to
you
and
when
I
say
you
that
could
be
a
thing
that
could
be
an
organization
that
could
be
a
person
that
could
be
a
decentralized
concept
like
a
public
blockchain
or
a
private
permission.
Blockchain.
A
A
When
an
issuer
issues
our
credential,
they
have
a
public
reputation,
so
they
create
a
credential
definition
on
the
ledger
and
then
they
start
issuing
credentials.
They're,
not
writing
any
data
at
the
blockchain
to
do
that.
They're
simply
asking
in
your
pairwise
relationship.
So
I
have
public
keys
for
my
public
reputation,
but
then
we've
formed
private
keys
to
have
a
private
interaction,
and
then
you
can
blind
a
secret
to
say
that
this
credential
is
uniquely
issued
to
you,
and
only
you
and
I
can
issue
a
credential.
A
That's,
instead
of
it
being
bound
to
the
D
ID
relationship
that
we
have
for
authentication.
It's
instead
bound
to
your
wallet
using
your
mechanism
of
choice.
That
way,
you
can
selectively
associate
all
the
attributes
that
you
have
against
any
pairwise
relationship
that
you
happen
to
have
across
the
network
and
across
the
system,
and
in
this
way
we
create
a
system
where
you
can
reduce
the
amount
of
correlate
able
information
that
you
share
instead
of
having
to
have
a
single
D
ID,
which
is
a
decentralized
identifier
that
you're
using
for
all
your
relationships.
A
It's
also
often
called
an
anonymous
credential
so
that
the
issuer
issues
a
credential
to
the
holder
and
then,
instead
of
proving
something
directly
by
disclosing
the
signed
data
which
would
be
transferable
to
any
party.
Who
could
get
a
copy
of
it?
They
instead
prove
things
in
zero
knowledge
so
that
the
information
that's
shared
is
not
transferable
to
other
parties
and
that
the
identity
holder
can
retain
their
control
for
disclosing
the
information
over
time.
A
A
But
I
would
really
like
to
drive
the
rest
of
the
time
that
we
have
here
together
before
the
next
presenter
comes
in
based
on
what
your
questions
are
and
what
you
would
like
to
talk
about
in
terms
of
what
hyper
ledger
in
India
is
up
to
and
what
we're
hoping
to
do
next
and
what
we've
done
so
far.
So
I'll
take
questions.
B
A
So
we
just
took
all
of
the
idea
of
credentials
or
information
sharing,
and
we
said
that
that's
all
about
key
management,
because
now
we're
as
we're
using
cryptography
for
all
information
exchange.
We
just
took
all
the
idea
of
relationships
and
individual
context
and
we
said
you're
not
gonna
have
one
identity
in
one
cryptographic:
key
you're
gonna
have
one
per
context
and
per
relationship.
Well,
key
management
is
hard
enough.
We
just
made
key
management
that
much
harder
didn't
we,
because
now
we
put
key
management
in
the
middle
of
absolutely
every
layer
of
the
system.
A
That's
part
of
why
the
brain
diagram
of
your
agent,
working
as
your
brain,
has
so
many
weird
colored
dots
in
it,
because
the
idea
is
you're.
Gonna
have
a
lot
of
cryptographic
keys.
Now.
There's
some
interesting
insights,
though,
when
you
start
approaching
it
as
an
identity
problem,
instead
of
strictly
a
blockchain
problem.
A
The
first
is
that,
because
keys
are
now
about
context,
we're
using
key
management
as
a
unit
of
relationship
which
it
turns
out,
our
human
brains
are
pretty
good
at
dealing
with
relationships
and
who
we
know
and
who
we
interact
with
and
they're
really
bad
at
dealing
with
cryptographic,
problems
and
cryptographic
keys.
So,
instead
of
thinking
about
your
cryptographic,
keys
as
I
have
a
key
and
I
need
to
rotate
it
and
I
have
to
not
forget
it.
A
You
can
start
thinking
about
your
keys
as
a
contact
list,
and
the
software
can
start
to
automate
a
lot
of
the
details
around
how
keys
work
and
how
you
interact
with
those
keys.
The
other
thing
that's
really
interesting
about
this
model
is
now
we
have
both
the
idea
that
you
have
keys
as
the
controlling
agent,
which
is
like
what
you
would
think
of
when
you
think
of
your
keys
for
a
Bitcoin
or
aetherium,
but
we
also
have
this
idea
of
an
identity
agent.
A
That's
acting
on
your
behalf
and
you're
delegating
control
to
it,
and
we
have
the
idea
of
all
the
people
who
are
issuing
your
credentials
and
they're
interacting
with,
and
they
all
have
keys
too
now.
Think
of
this,
it's
an
identity
platform
identity
is
about
the
relationships
that
you
have
in
your
relationships
want
to
help.
A
You
continue
to
be
you
because
they
find
value
in
interacting
with
you,
so
we
have
multiple
layers
of
the
system
that
helped
us
build
what
we
call
decentralized,
key
management
for,
managing
and
recovering
how
to
recover
your
keys
and
there's
no
magic
or
secret
sauce
to
that
it's
the
same
things.
We've
talked
about
for
a
long
time
in
terms
of
schmear
secret
sharing
in
terms
of
s
growing
in
terms
of
things
like
zero
knowledge
proof.
A
So
in
order
to
be
able
to
prove
possession
of
recovery
secrets
and
hints-
and
we
have
a
public
blockchain
that
can
serve
as
a
public
Oracle,
but
when
we
have
these
multiple
layers
that
we
we
have
trust
relationships
with,
we
can
use
one
layer
to
help
recover
all
of
the
others.
And
that's
really
what
we
talk
about
when
we
start
talking
about
decentralized
key
management.
A
Okay,
the
key
the
the
question
was
around
key
management
that
we've
essentially
turned
all
these
problems
into
a
key
management
problem
and
the
other
piece
that
was
asked
was
I've
heard
about
things
like
master
secrets
and
and
pairwise
secrets.
The
idea
is,
we
have
keys
that
we
use
to
talk
to
one
another.
We
usually
call
those
pairwise,
decentralized,
identifiers
and
decentralized
identifiers.
The
idea
is,
in
some
decentralized
system,
you've
registered
that
you
own
a
particular
identifier
and
there's
a
key
associated
with
that
identifier.
So
the
idea
is
that
you
have
keys
for
your
relationships.
A
You
have
keys
for
being
an
issuer,
and
then
you
have
keys
associated
with
the
credentials
that
you
share
with
zero
knowledge
proof,
and
so
there's
a
lot
of
different
kinds
of
information
that
go
into
wallet.
I.
Think
that's
the
end
of
our
time.
So
thank
you
very
much
everybody
and
you
can
find
me
in
the
hallway
track
for
whatever
you'd
like.