►
From YouTube: Hyperledger In-depth with Indicio: Indicio Proven – Scaling verifiable digital credentials
Description
Sometimes called “self-sovereign identity,” “user-centric identity,” or “reusable identity,” the open source technologies of Hyperledger Indy, Hyperledger Ursa, and Hyperledger Aries provide an authoritative way to authenticate any data without having to check in with the source of that data — or go through a third party. Introducing Indicio Proven™ – a complete, decentralized ecosystem for using verifiable credentials to create, share, and verify data of any kind while preserving privacy and enhancing security. In this webinar, we’ll demonstrate how Proven is designed to be a complete starter kit for creating your own Trusted Digital Ecosystem, containing all the components needed to create, share, and verify data through verifiable credentials. Learn from Indicio, Hyperledger member company, how to integrate interoperable, verifiable digital credentials and implement them into your existing systems.
In the “Hyperledger In-depth with… .” series, Hyperledger Foundation members share learnings from their projects and try to answer all the hard questions about the pains of working with DLTs. It is not yet another webinar: participants will be encouraged to take part, come with prepared questions and voice opinions. Expect live demos and tutorials, stories from the battle field and hopefully some heated discussions. Let’s get out of the zoom fatigue and engage to share experiences and build a stronger community.
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Discord: https://discord.gg/rVCn4j7UFd
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
License
Creative Commons Attribution license (reuse allowed)
B
B
C
B
First,
all
of
everybody
is
welcome
in
our
hyperledger
Global
Community.
We
are
striving
to
create
a
safe
and
welcoming
environment
for
all.
So
please
follow
the
hyper
Ledger
code
of
conduct
when
interacting
with
each
other
and
while
talking
to
other
in
the
community
as
well.
You
can
find
our
cone
of
conduct
on
our
weekly
on
all
and
also
on
our
webpage.
B
C
B
B
Now
we
encourage
these
sessions
to
be
as
active
and
engaging
as
possible.
So
please
raise
the
hand
and
you
raise
the
hand
button
to
an
S
to
get
unmuted
and
I
will
do
so
and,
of
course,
the
more
activity
and
participation
we
will
have
the
better
experience
everyone
will
have.
You
can
also
post
questions
in
the
chat
while
I
enable
it
and
the
Q
a
box,
and
this
will
be
then
relate
to
our
panelists
at
the
end
of
the
session.
B
For
those
of
you
whose
questions
will
not
get
answered,
we
will
also
encourage
you
to
join
our
Discord
Channel,
which
I
will
also
share
at
the
end
of
the
presentation
and
ask
your
questions
there
now
without
further
Ado,
I'm,
very
happy
to
introduce
our
panelists,
which
is
James,
who
is
the
vice
president
of
Business
Development
at
indicion,
and
also
Mike,
who
is
an
Enterprise
software
lead?
We
are
looking
very
much
forward
to
this
webinar
and
James
and
Mike
over
to
you.
D
D
So
yeah
thanks
thanks
for
joining
today,
we're
very
excited
to
be
here
to
demo
dco
proven
as
Thomas
had
mentioned.
This
is
a
solution
that
we
recently
released
it's
built
on
open
source
technology
and
can
be
used
by
Enterprises
by
organizations
by
individuals
to
get
started
with
verifiable
credentials
and
decentralized
identity
technology.
It
can
be
used
to
create
a
complete
open
source
trusted
digital
ecosystem
and
can
be
configured
to
specific
use
cases
or
pain
points
at
your
organization
or
your
customers
are
are
dealing
with.
D
We
are
very
excited
and
proud,
proud.
Member
of
the
hyper
Ledger
Foundation
are
thankful
to
the
the
support
that
we
get
from
the
foundation
as
well
as
other
contributors
in
the
community.
We
happily
contribute
back
to
the
community
as
well,
and
we
we
think
that
collaboration
and
the
open
source
contributions
from
individuals
and
organizations
in
the
space
is
really
what's
leading
to
the
adoption
and
driving
forward
of
this
of
this
technology.
D
The
the
problem
that
this
solves
regarding
digital
identity
stems
from
the
the
well-known
fact
that
originally
the
internet
was
created
without
that
critical
identity,
layer
for
people,
entities
and
things
and
as
the
world
becomes
more
increasingly
digital,
especially
in
the
last
two
and
a
half
years
with
the
global
pandemic,
people
migrating
to
a
more
online
Centric
or
digital
Centric
lifestyle.
Digital
identity
becomes
a
crucial
piece
to
making
everyday
life
possible
and
for
interactions
to
happen
online,
there
needs
to
be
trust
between
between
people
places
and
things.
D
So
it's
it's
a
major
major
pain
Point.
Not
only
is
it
painful,
it
costs
a
lot
of
money
for
businesses
for
Enterprises
and
for
customers.
It
just
makes
for
a
a
cruddy
experience
for
businesses,
for
example,
dealing
with
the
hacks
and
breaches
that
come
as
a
result
of
not
being
able
to
verify
who
it
is,
on
the
other
side
that
you're
dealing
with
the
loss
of
productivity
of
of
employees
having
to
change
their
passwords
or
deal
with
cumbersome.
You
know
two-factor,
authentication,
three-factor,
authentication
and
just
earlier
today,
I
saw
a
four-factor
authentication.
D
There
was
a
recent
report
that
the
annual
cost
for
the
global
economy
as
a
result
of
digital
identity
related
fraud,
hacks
breaches,
all
those
sorts
of
things-
is
5.38
trillion
here
in
the
United
States
alone.
Last
year
it
was
upwards
of
52
billion
dollars
for
for
businesses
and
Enterprises
private
organizations
dealing
with
identity
related
challenges.
So
it's
a
a
major
pain
Point.
It's
it
costs
lots
of
money,
and
so
it's
something
that
organizations
are
looking
to
to
figure
out.
D
I'm
sure
a
lot
of
you
are
familiar
with
what
what
some
refer
to
as
the
trust
triangle.
We
we
think
this
is
a
basic
diagram
of
what
a
trusted
digital
ecosystem
looks
like.
So
you
have
the
main
participants
being
issuers
here
on
the
left.
You
have
your
holder
or
the
the
person
receiving
the
credential
up
at
the
top,
and
then
you
have
your
verifying
organizations
down
at
the
bottom
involved
in
that
is
is
a
form
of
a
of
a
registry
for
for
verifiable
data.
D
There's
the
issuer
organization
who
has
taken
efforts
to
establish
identity
and
through
some
manner,
either
performing
kyc
or
having
improved
some
sort
of
aspect
about
an
entity
or
a
person
and
package
that
into
a
verifiable
credential
and
then
anchoring
the
the
schemas
and
the
the
dids
of
those
entities
down
to
The
Ledger
and
then
issuing
that
credential
to
the
holder,
where
it's
then
held
in
some
sort
of
digital
wallet,
whether
that's
a
cloud
hosted
wallet
or
on
device
or
a
community
type
wallet.
There's
different
variations
of
it.
D
Checking
the
checking
the
keys
on
the
network,
verifying
that
the
origin
original
location
of
the
issuer
is
a
trusted
organization
in
their
in
their
opinion
or
according
to
their
ecosystem.
Rules
can
know
that
the
information
being
presented
to
them
is
correct
and
that
allows
for
the
holder
to
make
some
sort
of
transaction
or
participate
in
some
service
or
get
access
to
some
some
type
of
thing.
D
So,
let's
take
a
bank,
for
example,
issuing
a
customer
credential
to
customer
a
customer
can
take
that
credential
either
back
to
the
bank
to
be
verified
or
if
the
bank
has
partnering
organizations
who
have
chosen
to
accept
that
credential
can
and
trust
that
bank
as
an
issuer
can
allow
that
that
customer
to
participate
in
some
activity
on
their
end
as
well.
So
that's
the
the
gist
of
a
trusted
digital
ecosystem.
Now
the
the
software
behind
it
is
what
we're
going
to
see
today
with
proven
that
makes
all
of
this
possible
based
on
open
source.
D
But
right
now
we'll
do
a
little
context
on
currently
the
landscape
of
the
verifiable
credential.
The
space.
Some
of
the
challenges
have
been
one-off
type,
Solutions
or
or
the
lack
of
interoperability
between
wallets
or
ecosystems
or
providers
that
focus
on
one
thing,
and
so
we
noticed
that
a
lot
of
Enterprises
were
struggling
to
find
a
complete
ecosystem
that
they
could
Implement
and
use
right
off
the
bat.
D
So
this
is
where
in
dco
proven
comes
in
based
on
the
hyperledger
Indie,
Aries
and
Ursa
protocols
based
on
that
open
source
technology.
It's
a
complete
ecosystem
that
comes
with
all
the
components
needed
to
issue
hold
and
verify
digital
credentials
based
on
a
hyperledger,
Indie
Network
and
using
an
Aries
based
wallet
which
we'll
see
demonstrated
today.
D
So
it's
a
it's
a
complete
starter
kit.
So
organizations
can
pick
it
up
and
integrate
it
into
the
systems
that
they
already
have.
They
don't
need
to
spin
up
their
own
or
create
their
own
issuing
agents
or
verifier
agents.
Everything
in
the
package
comes
with
what
they
need.
It
comes
with
what
they
need
to
start
issuing
credentials
right
away
based
on
their
their
credential
needs,
it's
capable
of
being
customized
and
you
can
add
new
functionality
into
it
as
needed
and,
as
you
scale
up
your
your
use
case.
D
D
The
holder,
who
now
has
that
credential
can
present
it
and
then
use
a
The
Proven
verifier
to
verify
the
credential
that
they
received.
Today's
demonstration
is
based
on
the
indicio
test
Network
or
a
demo
Network
and
showcases.
How
and
how
the
hyperledger
Indie
Network
can
can
be
used
for
this
in
general,
The
Proven
ecosystem
can
be
connected
with
any
hyperledger
Indie
network
of
choice.
D
Any
of
the
existing
networks
or
a
private
Network
can
be
spun
up
to
be
connected
to
it
as
well,
because
it
is
based
on
those
open
source
protocols
in
the
areas
in
Ursa.
It's
interoperable
with
other
areas,
wallets
other
areas,
related
ecosystems
and
other
Indie
Networks.
So
looking
down
at
The,
Proven
issuer
agent,
as
well
as
the
proven
verifier
agent,
or
what
we
call
Enterprise
agents
they're
based
on
the
hyperledger
areas,
protocols,
so
they're
they're
using
acapai
various
Cloud
agent,
python,
they're,
server-based
agents
with
a
JavaScript
controller.
D
D
D
The
nice
thing
about
it
is
that
it
it
allows
for
organizations
to
interact
with
with
individuals
in
a
way
that
doesn't
violate
their
privacy,
so
respecting
HIPAA
regulation,
gdpr
CPR
in
California
and
the
pending
Hiatus
2.0
out
of
the
the
European
Union,
which
hasn't
officially
been
ratified.
Yet
there
are
amendments
in
the
works,
but
this
puts
you
in
a
great
position
to
be
able
to
accommodate
those
coming
regulations
and,
and
the
sensitivities
are
and
liabilities
that
are
involved
with
those
between
the
issuers
and
verifiers.
D
There
doesn't
need
to
be
a
direct
database
integration
on
the
back
end.
So,
let's
say
you
as
an
organization
are,
is
showing
a
credential
to
your
to
your
individual
or
entity
that
you're
identifying
and
they
take
that
credential
to
either
be
issued
by
another
organization
or
internally
within
your
own.
They
can
do
that
without
having
to
connect
into
some
sort
of
database
on
your
end
to
they
don't
have
to
phone
home
and
create
another
layer
of
friction
there.
D
It
uses
secure
encrypted
peer-to-peer
communication
and
we'll
also
see
that
in
the
the
demo
today
with
the
holder
wallet
how
communication
can
occur
between
two
two
wallets,
but
there
is
also
the
that
secure
transfer
of
information
between
the
Enterprise
agents
and
the
the
agent
itself.
So
it's
a
very,
very
light
ecosystem.
D
It's
not
a
proprietary
platform
that
they're
locked
into
as
much
as
we
love
working
with
organizations,
and
we
would
love
for
them
to
continue
to
work
with
us
they're,
not
stuck
with
with
a
single
provider.
So
they
could,
you
know,
continue
to
either
work
on
it
internally
on
their
own.
We
can
support
it
or
they
can
work
with
other
vendors
to
continue
to
build
out
the
the
functionality.
D
So
that's
the
beauty
of
working
on
the
hyperledger
open
source
protocols,
as
mentioned
we're
going
to
see
a
small
Showcase
of
holder
plus,
which
is
a
digital
wallet
based
on
the
hyperledger
areas,
bifold
project,
which
the
industry
team
has
been
contributing
heavily
to,
and
we're
excited
to
have
a
few
members
of
the
community
here
today.
That
have
also
contributed
to
that.
So
thank
you
to
the
community
for
for
making
the
interoperability
of
these
wallets
possible.
D
D
But,
as
mentioned
we'll
go
ahead
and
we'll
do
a
a
demo
of
proven,
Mike
will
will
share
a
screen
and
walk
through
that
and
as
you're
watching
this
presentation.
Think
of
the
use
cases
you
have
in
mind
where
verified
identity
could
be
useful
to
either
reduce
friction,
reduce
cost.
You
know
solve
for
liability
in
your
particular
use
case,
so
Mike
I'll
hand
it
off
to
you
to
show
proven.
A
A
So
besides
you
know,
the
the
stuff
that
James
has
already
mentioned
proven
takes
care
of
a
bunch
of
things
for
you.
That
can
be
a
pain
when
you're
trying
to
get
a
digital
ecosystem
up
and
running
so,
for
example,
proven
comes
with
a
Docker
compose
set
up
with
various
containers,
so
you
can
post
your
Solution
on
any
server
that
supports
the
docker
or
have
it
run
reliably
on
a
local
development.
A
It
comes
with
the
ndco
public
mediator
and
test
net
set
up
by
default,
comes
with
keys
for
various
encryption
points,
already
pre-configured
or
easy
to
set
up
there's
a
first
time
setup
script
so
that,
instead
of
having
to
walk
through
a
lot
of
different
steps
manually,
you
can
run
the
first
time
setup
script
and
it
will
help
you
get
everything
set
up.
As
you
go
includes
an
initial
schema,
an
email
schema
and
comes
with
a
database
system
that
includes
migrations.
A
It's
got
a
controller
and
a
UI
written
in
node.js
with
Express
on
the
back
end
and
react
on
the
front
end.
Manage
management
manages
agent
state,
so
acupai
does
a
good
job
of
being
an
agent,
but
sometimes
it's
tricky
to
get
the
state
of
your
connections
or
your
list
of
credentials,
Etc
out
of
acupai,
and
so
we've
provided
some
ways
to
make
that
a
little
easier.
A
A
So
here
is
the
proven,
issuer
home
screen
and
includes
a
help
section
and
then
allows
you
to
configure
the
agent
in
some
ways.
So,
for
example,
you
can
change
the
display
names
of
the
agent
here
you
can
change
the
logo
and
icons
that
are
displayed.
Some
applications
that
you
know
refer
to
a
web
application.
Some
operating
systems
or
devices
use
a
web
app
manifest.
So
you
can
configure
those
settings
here.
A
Some
of
the
workflows
around
the
email
involve
sending
an
email
and
there's
also
user
management
system,
so
you
can
configure
an
email
account
for
sending
email
and
you
can
white
label
the
agent
by
adjusting
either
those
logos
or
icons
for
any
of
these
common
colors
that
are
in
the
application.
So,
for
example,
if
we
want
our
buttons
to
be
red,
we
could
pick
a
nice
red,
color
and
change
them.
Oh,
that's
an
orange
color.
A
Let's
see
what
else
is
in
here,
okay,
so
we
mentioned
that
it
helps.
You
manage
your
state,
so
it
includes
a
list
of
contacts.
Somebody
yep,
oh
there
we
go.
So
we
have
a
couple
testing
contacts
in
here
and
you
can
go
ahead
and
view
more
information
about
a
particular
contact.
So,
for
example,
we
can
see
that
when
I
was
testing
the
system
I
was
able
to
issue
myself
with
credential.
We
view
the
credentials
issued
to
a
particular
individual.
A
You
can
also
view
the
full
list
of
credentials
and
it
would
fill
into
any
particular
one.
So
here's
one
that
I
issued
in
myself
earlier
right
now.
This
list
of
credentials
only
shows
email
credentials,
but
if
you
had
other
types
in
your
system,
those
would
all
be
shown
in
one
place.
So
you
know
proven
is
not
limited
to
just
email
credentials,
but
that's
what
it
comes
with
configured
out
of
the
box
or
you
know
proof
of
concept
and
demonstration
purposes.
So
you
can
get
a
feel
for
how
things
work.
A
The
code
includes
what
you
need
to
manage
browser
sessions
and
websocket
connections
and
we're
working
on
an
HTTP
API.
So
some
of
the
calls
already
exist.
So,
for
example,
you
can
create
invitations,
you
can
issue
credentials
and
you
can
request
presentations
at
the
moment
we're
working
on
adding
additional
protocols
so
that
you
have
access
to
the
full
power
of
acupai,
but
through
an
API
that
helps
make
it
easy
all
right.
So
those
are
some
of
the
the
technical
details
to
what
proven
offers.
A
So
we're
going
to
take
three
main
steps:
we're
going
to
prove
that
I
control,
a
particular
email
address,
we're
going
to
issue
myself,
an
email,
credential
and
then
we're
going
to
take
that
email,
credential
from
my
holder
to
our
verifier
and
present
that
credential
to
verify
that
it's
correct
and
accurate
and
came
from
the
issuer.
So
we're
going
to
simulate
being
just
me
and
the
demonstration
comes
with
a
self-serve
email,
credential
system.
So
I'm
going
to
type
in
my
email
address
here
and
once.
A
C
A
Right
and
share
the
screen
again,
so
you
can
see
here
that
there's
a
an
invitation
in
my
email
account
we'll
zoom
in
a
little
bit.
The
text
does
not
want
to
sit
scale
all
right,
so
we'll
follow
that
link
and
you
can
see
my
unique
code
in
the
URL
and
now
I
have
a
unique
invitation
for
receiving
an
email
credential.
A
So
the
next
thing
to
do
is
use
holder
to
ex
to
connect
to
our
Enterprise
issuer
and
receive
a
credential
offer
so
on
the
right
here.
You'll
see,
holder,
Plus,
that's
like
James
mentioned
it's
built
on
afj
and
bifold
and
can
be
white
labels.
So
you
could
swap
out
this
logo
an
icon
and
text
Etc,
and
it's
got
a
little
bit
of
an
intro
for
people
to
understand
what
a
wallet
is
go
ahead
and
get
started
and
scroll
through
these
terms.
A
A
All
right
so
now
we're
connected
to
proven
and
we've
received
our
credential
offer.
So
you
can
see
the
pieces
of
my
email
address,
so
they
have
them
separated
and
combined
and
a
verified
timestamp,
so
I'm
happy
to
receive
this
credential
some.
You
know
this
is
a
basic
credential,
but
you
could
use
it
in
various
contexts
like
so.
A
For
example,
if
you
are
trying
to
communicate
with
a
customer,
if
you
are
trying
to
have
one
part
of
your
business
prove
to
another
system
in
your
business,
that
someone
is
has
legitimate
participation
in
your
business
accounts
and
systems.
You
could
use
it
with
some
extension
to
set
up
a
login
system.
A
number
of
things
like
that
so
I'm
going
to
accept
my
credential
and
it's
been
added
to
my
wallet.
A
A
All
right,
so
we
can
see,
we've
got
two
contacts
proven
in
The,
Proven,
verifier
and
there's
a
some
information
requested.
So
the
verifier
is
asking
for
my
email,
you'll
notice
that
it's
a
selective
disclosure,
it's
not
asking
for
all
of
the
fields.
So
that's
an
example
that
shows
that
you
can
do
things
to
help
preserve
privacy.
Only
ask
for
the
information
that
you
need
so
I'm
going
to
go
ahead
and
share
that.
A
A
So,
like
we
said
earlier,
this
is
just
a
simple
demonstration,
but
you
know
with
the
apis
that
are
available.
For
example,
the
verifier
has
an
API
where
you
could
link
with
an
external
system
and
send
a
notification
that
says
yeah
the
verification
occurred
and
this
email
is
kosher,
so
go
ahead
and
Trigger
additional
actions
that
are
part
of
your
existing
systems.
A
A
Connect
to
this
other
wallet
here
toward
John
Doe
wallet,
so
John
Doe
is
going
to
display
a
QR
code
on
his
wallet
and
then
Mike
Ebert
is
going
to
scan
his
QR
code
from
his
and
so
now
I
have
a
new
contact
of
John
Doe
here.
So
I'm
gonna
two
handles
here.
One
one
phone
in
each
hand
and
so
John
is
going
to
type
me
a
message
and
say:
hi
and
since
I'm
feeling
a
little
bit
mischievous,
I'm
gonna
switch
and
I'm
gonna.
A
And
this
is
cool,
because
these
these
two
wallets
have
generated
an
invitation
and
exchanged
their
pairwise
dids
they're
communicating
over
didcom
and
the
messages
are
encrypted.
So
we
have
a
peer-to-peer
connection
here
and
it's
all
secure
and
happy
they're
each
using
their
own
mediator
and
all
the
exchanges
is
going
just
fine
and
now
they
can
chat
in
a
secure
context.
So
that's
a
cool
feature.
That
holder
includes
that
we've
recently
added
that
we're
pretty
excited
about.
A
One
of
the
examples
here
is:
you
could,
for
example,
say
we're
going
to
connect
to
an
agent
we're
going
to
request
their
their
email,
credential,
and
then
this
the
server-based
agent,
you
know,
could
also
have
a
messaging
box
like
this,
and
you
could
communicate
securely
between
a
customer
or
an
employee
over
secure
channels
and
and
not
worry
about
your
information
getting
lost.
So
with
that
I'm
going
to
turn
some
time
back
over
to
James
here,
because
the
demo
is
complete.
A
D
Okay,
so
yeah
as
Mike
just
demonstrated
what
comes
in
the
Box?
Here's
a
quick
summary
of
what
you
just
saw.
So
it
comes
with
a
verifiable
credential
schema.
So
a
flexible
Cloud
hosted
template
for
creating
a
verifiable
credential
comes
with
the
issuer
and
verifier
agents,
and
it
also
comes
with
the
along
with
the
mobile
app,
the
digital
wallet
and
the
mediator
agent
or
agents
that
are
needed
to
support.
D
It
also
comes
with,
as
default,
the
connection
to
a
distributed.
Ledger
Network,
an
indie
network
of
of
choice,
comes
with
support
and
training
offered
offered
by
our
team,
along
with
maintenance
and
updates,
to
make
sure
that
you
have
the
most
up-to-date
system,
especially
as
the
open
source
community
and
standards
evolve.
Having
that
ongoing
support
is
is
a
good
way
to
stay
interoperable
with
with
other
systems
as
well
as
mentioned.
D
So
some
of
the
top
use
cases,
as
you
can
imagine,
are
in
Industries,
where
it's
highly
regulated
and
there's
a
lot
of
liability
if
identity
can't
be
established
so
Banking
and
finance,
for
example,
satisfying
those
kyc
requirements
needed
for
customers
to
be
able
to
do
certain
things
with
them
or
interact
with
them.
Transfer
money
open
up
new
accounts,
those
those
sorts
of
those
sorts
of
actions,
travel.
Obviously,
there's
a
lot
of
different
areas
where
identity
comes
into
play.
D
D
Interestingly
enough
in
the
healthcare
space,
there
are
organizations
that
don't
want
anything
to
do
with
a
customer's
Health
Care
information,
but
have
have
to
in
some
way
interact
with
it.
This
is
where
verifiable
credentials
are
nice,
because
that
that
information
remains
with
the
holder
of
the
credential
and
doesn't
have
to
be
stored
by
a
third
party
in
some
sort
of
centralized
database,
putting
them
at
some
sort
of
risk
of
a
breach
of
that
information.
D
So
those
are
those
are
some
examples
of
organizations
that
are
using
it,
and
those
organizations
have
approached
us
and
the
feedback
that
we've
we've
gotten
that
led
to
proven
was
they're
looking
for
a
way
to
quickly
set
up
an
ecosystem,
they
want
to
start
issuing
credentials
and
they
want
to
start
verifying
credentials,
and
they
don't
want
to.
You
know,
have
to
do
all
the
Dirty
Work
of
figuring
out
how
to
make
it
interoperable
having
to
dig
through
all
the
repos
they
just
want
to.
They
just
want
to
solve
their
pain
point.
D
They
just
want
to
be
able
to
make
it
easier
for
their
customers
or
internally,
for
whichever
department
needs
to
needs
to
handle
that
so
I
I
hope
that
answers
the
question.
But
it's
across
many
Industries,
where
identity
plays
a
role
not
just
with
people,
but
also
with
with
devices
being
able
to
identify
a
machine
or
an
iot
device
and
and
allowing
for
secure
access
to
that
device
as
well.
So
we're
seeing
traction
with
with
iot
the
spatial
web
area
too.
D
So
lots
of
different
ways
to
use
proven
and
integrate
into
your
system
and
dco
provides
support
options
to
install
it
to
help
integrate
it,
or
we
can
simply
provide
training
on
how
to
do
that
provide
instructions.
We
can
help
configure
if
there's
any
customized
capability
that
you
need
that
could
be
added
on.
On
top
of
that,
it
can
be
a
white
labeled
solution,
rebranded
how
for
you
or
for
your
customers.
D
However,
you
need
it
and
we
can
help
yeah
curate
it
in
a
way
that
solves
not
only
your
problems,
but
your
partners
and
anyone
who
you
add
into
your
your
ecosystem.
You
have
that
base
ecosystem
of
issuers
holders
and
verifiers
and
then,
as
it
expands,
there
will
be
other
organizations
that
want
to
consume
the
credentials
that
that
your
organization
offers
that
opens
up.
A
We
thought
let's
focus
on
issuing
and
verifying
the
credentials
that
are
important
to
the
business
use
case
first
and
we'll
just
go
with
a
simple
existing
flow
for
users,
but
we're
working
on
making
dids
or
credentials
the
defaults
for
logging
into
the
proven
admin
screens
as
well.
So
that's
that's
coming.
That's
a
good
thought.
A
Another
question
was:
is
there
a
way
to
see
the
did,
which
is
generated
for
the
user,
so
in
the
Enterprise
agent
in
the
list
of
contacts
it
would
be
relatively
straightforward
to
display
that
did
and
then
I
don't
know
if
we
would
want
to
in
a
mobile
agent
for
making
it
user
friendly
for
end
users
as
much
but
theoretically,
that's
possible
as
well.
If
it's
something
that
you
wanted
to
do
and
then
finally,
Kyle
asked
is
proven
a
hosted
service
run
by
indicio.
A
B
A
Looks
like
question
about
web
3.0
web
3.0
is
supposed
to
have
blockchain
slash
security
built
in
admittedly,
my
understanding
of
3.0
is
weak.
Could
you
talk
about
your
relationship
to
web
3.0?
Is
it
competition
or
does
it
facilitate
in
dco
so
often
when
people
think
of
web
3.0,
they
think
of
all
of
the
use
cases
that
have
to
do
with
the
common
blockchains
that
people
are
familiar
with
like
Bitcoin
and
ethereum
coin?
A
You
know
cryptocurrencies
and
smart
contracts
and
things
like
that,
and
that
technology
is
really
useful
for
things
that
are
need
to
be
verified
publicly
and
that
you're,
okay,
with
being
out
on
a
ledger
that
everyone
can
read
and
those
those
Solutions
put
all
of
their
data
out
out
on
those
blockchain
ledgers.
The
identity
use
case
that
we
have
here
relies
somewhat
on
some
of
the
same
technology,
so
the
the
did
and
the
keys
and
the
relationship
of
an
issuer
to
a
particular
schema
and
the
schemas.
A
Those
are
stored
on
a
ledger
where
everyone
can
view
them
and
get
that
get
at
them
at
any
time
and
that's
a
the
the
public
component
of
the
solution
that
helps
make
this
work
really
smoothly.
But
all
of
the
sensitive
private
data
that
is
issued
by
the
issuer
lives
in
just
inside
the
credential
that
the
holder
has
and
it's
secure
and
under
their
control.
So
in
some
ways
they
utilize
some
of
the
complementary
Technologies
some
of
the
same
things,
but
because
the
use
cases
private
versus
public.
A
D
And
what's
interesting
here
with
the
blockchain,
the
blockchain's
involvement
in
a
trusted
digital
ecosystem?
It
is
really
the
most
boring
part
about
it.
The
really
cool
stuff
is
happening
at
the
agent
level
between
the
organizations
that
are
able
to
verify
identity
on
the
end,
the
Ledger's
purpose
is
obviously
just
for
the
the
anchoring
some
call
it
a
trust,
anchor
of
sorts,
the.
So
a
lot
of
the
Enterprises
that
we
work
with.
You
know
we
when
they
hear
the
term
blockchain,
there's
a
lot
of
misconceptions
or
preconceived
notions.
D
They
have
that
come
from
the
crypto
world,
where
you
know,
there's
the
speculative
aspect
of
it,
where
you
know
cryptocurrency
involved
in
this
case.
It's
it's
not
it's
not
like
that.
So
you
know.
Sometimes
we
avoid
the
term
blockchain
because
it
could
be
confusing,
or
you
know,
go
down
a
tangent
that
that
we
wouldn't
necessarily
want
to
go
down
to
go
down
so
decentralized
identity,
Network
or
Ledger,
because
in
this
case
there's
not
any
sort
of
you
know
proof
of
work
or
mining
going
on
it's
just.
D
A
I
know
your
customer
process,
and
once
you
go
through
that
process,
it's
really
nice
to
use
a
non-creds
and
Aries
wallets
for
recording
that
information,
because
you
can
record
it
in
a
way
where
you
can
verify
who
issued
it
and
prove
that
it
wasn't
tampered
with.
So
you
can
rely
on
the
issuing
party
to
say:
I
can
trust
this
kyc
to
data,
because
someone
already
looked
into
it.
Someone
reliable
proved
that
this
data
was
there
and
using
a
non-creds
and
Aries
wallets,
there's
a
level
of
holder
bindings.
A
So
you
know
that
that
credential
was
issued
to
this
particular
wallet
originally
and
has
not
been
fiddled
with
or
moved
to
another
wallet.
So
as
long
as
you
trust
the
wallet
you
know,
perhaps
the
wallet
uses
a
fingerprint
or
a
face
scan
or
something
like
that.
Just
to
tie
this
to
the
individual,
then
you
can
rely
on
that
kyc
to
verify
data
to
to
still
be
relevant,
so
you
don't
have
to
go
through
the
kyc
process
over
and
over
again.
So
that's
the
case
with
with,
like
say,
banking,
with
the
travel
use
case.
A
It's
public
knowledge
that
we're
doing
work
on
the
digital
travel
Prudential
and
making
that
work
with
a
non-cred
equivalent
so
that
you
can
travel
and
prove
your
identity
based
on
your
passport.
So
those
are
most
of
the
use.
Cases
are
starting
with
identity,
but
there
are
some
other
use
cases
that
that
go
beyond
that
to
say
there's
you
know
perhaps
accounting
data
where
you
want
the
data
to
be
verifiable,
but
you
know
for
a
private
organization
shouldn't
be
published.
Broadly
we're
also
working
on
some
mixed
use.
D
A
D
Be
a
better
question
for
you,
but
one
thing
that
comes
to
mind
is
one
of
the
amendments
in
Hiatus
2.0
that
is
calling
for
zkp
capability,
as
well
as
selective
disclosure.
That's
one
of
the
reasons
that
we
use
a
non-creds
as
a
way
to
satisfy
those
requirements.
Although
they're
not
officially
ratified
or
Idis,
isn't
you
know
officially
in
place
yet,
but
that's
the
the
the
power
of
an
on-creds
you
know
shows
how
that
can
be
handled
so.
A
Some
of
the
European
privacy
concerns
and
and
legislations
are
to
they.
They
want
people
to
be
able
to
privately
hold
their
data.
They
are
asking
for
a
selective
disclosure,
so
you
only
disclose
what
you
need
to
disclose.
There's
some
situations
that
require
zero
knowledge
proofs
and
there
are
lots
of
credential
formats.
A
Some
of
them
are
not
they're
they're
working
towards,
but
aren't
ready
to
do,
selective,
disclosures
or
or
predicate
or
non-disclosing
proofs,
like
that,
zero
knowledge,
proofs
and
then
the
holder
binding,
is
another
thing
that
some
other
Solutions
struggle
with
a
little
bit.
So
if
the
the
latest
European
privacy
legislation
that's
being
considered
if
it
were
ratified
right
this
second,
as
far
as
I'm
aware,
a
non-creds
are
the
only
credential
format
that
meets
all
of
those
privacy
concerns.
A
So
we're
going
to
make
available
code
that
will
be
able
to
read
those
those
governance
files
and
interpret
what's
encoded
there
to
look
at
we're,
starting
with
who
are
the
trusted
issuers
and
verifiers,
and
eventually
we'll
be
adding
other
roles
and
the
ability
to
script.
Some
workflows
some
actions
and
we'll
be
working
on
how
to
publish,
discover,
share
ingest
expert
support,
Etc
work
with
those
files
that
make
those
workflows,
trustworthy
and
understandable
for
ecosystems
and
overlapping,
overlapping
and
interconnected
ecosystems.
B
Well,
thank
you
very
much
Mike
and
thank
you
very
much
James.
We
are
at
the
time,
so
I
think
we
need
to
wrap
up,
but
thank
you
very
much.
You
covered
a
lot
of
very
interesting
and
useful
information
and
thank
you
to
everybody
joining
us.
If
you
have
any
questions
for
either
us
or
indicio
team,
please
feel
free
to
to
reach
out
to
us
or
the
indicio
team,
and,
as
mentioned
all
of
the
recording
and
also
the
the
slides
will
be
available
on
the
hyper
manager.
Webinar
Library
now
before
we
say
goodbye.