►
From YouTube: Identity Proofing Solution Combining HL Indy and Fabric - Mark Rakhmilevich, Oracle & Mike Vesey
Description
Identity Proofing Solution Combining HL Indy and Fabric - Mark Rakhmilevich, Oracle & Mike Vesey, IdRamp
The need for trusted identity is growing with remote workforce and online government services due to the pandemic and risk of fraud and data leaks. Decentralized verifiable identity meets this need with a strong trust model. Speakers will demo identity proofing and issuance of verifiable credentials to a city resident. Oracle Blockchain Platform (HL Fabric) manages data gathering & audit logging. IdRamp services based on HL Indy/Aries running in the Oracle Cloud ensure interoperability & protect PII. In the demo a resident requests city credentials by scanning physical documents for automated and human verification, then uses their credentials for verified access to a court hearing. Verifiable credentials support universal access to city services and, with self-sovereign approval, can be shared with other jurisdictions, avoiding additional physical proofing and the risk of sharing PII.
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/j3em
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
B
A
We're
going
to
talk
today
about
identity
proofing,
solution
that
oracle
and
idram
have
put
together
combining
the
hyperledger
indie
platform
with
hyperledger
fabric,
we're
going
to
explain
why
we're
actually
using
two
separate
distributed
ledges
and
why
that
makes
the
solution
stronger
and
we'll
actually
see
a
live
demo
as
well.
That
michael
shares
us
so
we'll
begin
by
talking
a
little
bit
about
what
id
proofing
is
and
why
it's
important.
A
B
Perfect,
thanks
mark
so
throughout
the
presentation
and
demonstration.
Today
we're
going
to
be
talking
about
identity
proofing,
why
it's
important
and,
more
importantly,
how
we
can
use
those
proven
identities
to
really
transform
existing
processes.
As
we
know
it,
as
mark
said,
we'll
get
into
a
technical
discussion
of
an
architecture
of
how
we
developed
this.
And
why
and
that's
really
exciting
before
we
really
talk
about
identity
proofing,
I
want
to
break
down
and
just
explain
the
verifiable
credentials
in
a
little
bit
because
we'll
be
seeing
that
throughout
the
presentation
and
demonstration
as
well.
B
B
So
why
is
identity
proofing
important,
go
ahead
and
go
to
the
next
slide
mark
and
I'll
I'll
set
this
up
a
little
bit?
So
so?
The
first
and
foremost
thing
that
we're
going
to
talk
about
today
is
really
the
reduction
in
fraud.
By
going
through
a
tight
identity
proofing
process,
we
can
eliminate
bad
actors
and
really
try
to
strengthen
those
services.
B
B
A
Right
sure,
thanks
mike,
so
you
know
as
you
as
you
saw,
a
lot
of
those
focuses
on
requirements
from
government
agencies
could
be
in
a
local
city.
Government
state
could
be
a
federal
agency,
but
equally
we
think
this
translates
into
some
of
the
enterprise
requirements
as
well
and
so
working
with
you
know,
a
number
of
customers
like
that,
certainly
see
a
key
requirement.
A
A
The
idea
is
to
enable
you
know:
cto,
state
residents
and
or
members
of
particular
organization
to
enroll
submit
some
kind
of
verification
documents
right
for
proofing
that
in
fact
they
have
a
particular
residence
or
is
they
a
member
of
particular
organization,
online
numbers
in
a
touchless
manner,
and
then
on
the
back
end,
there
needs
to
be
an
administrative
interface
for
tracking
and
managing
the
process.
Some
of
those
documents
can
be
verified
at
the
market,
for
example,
if
one
of
them
has
a
driver's
license.
A
One
of
the
key
requirements
is
to
make
the
chatting
self-sovereign
name
is
that
the
users
are
going
to
be
asked
to
approve
somebody
accessing
that
particular
profile
and
they
can
accept
or
reject
that
request
and,
of
course
accept
the
request.
Then
that
access
is
granted,
but
it's
also
logged
in
an
immutable
audio
trail.
A
So
the
entire
process
from
the
documents
being
submitted,
verified
and
then
the
you
know,
access
to
the
credentials
and
a
grant
of
permission
to
access
those
credentials
all
need
to
be
logged
in
an
immutable
ledger.
So
this
is
sort
of
a
collection
of
key
requirements
around
the
solutions
that
we've
been
working
on.
A
A
Really
the
best
in
class
solution
would
combine
the
benefits
of
both
platforms.
So
on
the
top
you
see
here
two
key
components
of
the
application:
there's
credential
manager,
application.
This
is
doing
the
proofings,
the
onboarding
process
and
then
there's
user
wallet
based
on
aries
hyperledgeris
project,
so
they're,
using
indeed
to
essentially
maintain
the
dads
decentralized
identities
and
the
issue
identity
status
of
the
credentials.
A
A
That
access
the
portal,
in
any
case,
in
a
for
any
of
those
services
when
the
user
is
accessing.
For
the
first
time,
they're
going
to
be
asked
to
set
up
the
credentials
through
the
idram
credential
application
on
the
right
here
that
does
actual
verification
and
distribution
and
it's
connected
to
both
fabric
network
and
indian
network.
A
The
identity
is
created
in
oracle
identity
cloud
service
that
then
enables
password-free
login
for
variety
of
the
services,
using
the
user
wallet
right,
so
credentials
actually
sent
to
the
user's
wallet
and
then
verified
users
can
access
the
applications
through
the
portal
directly
with
a
wallet
and
you're
going
to
see
that
in
a
demo,
in
a
minute
here
being
used
to
provide
the
qr
code
essentially,
is
that
they're
going
to
give
them
access
from
a
user
perspective?
The
process
is
very
straightforward.
A
A
Some
of
those
steps
will
be
automated
and
others
may
require
manual
procedures.
Once
the
documents
have
been
verified,
then
the
credentials
are
created
and
two
things
happen.
Credentials
are
distributed
into
the
wallet
and
there's
also
accounts
created
in
the
identity
management
system,
such
as
in
oracle,
identity,
cloud
or
maybe
federated
directory
services
etc.
A
A
A
All
of
the
departments
within
the
entity
cto
state
will
be
consistently
using
the
same
proofing
practices
so
for
different
types
of
accounts.
You
might
require
different
type
of
proofing
documents
that
could
be
flexibly
configured
as
well,
and,
of
course
you
could,
you
know,
do
some
value-add
services
for
some
of
the
related
jurisdictions.
You
know
here,
for
example,
in
the
bay
area.
There
are
specific,
you
know,
city
services,
for
each
city,
but
then
there
are
bay,
area-wide
organizations,
entities
agencies
where
they
might
want
to
also
use
the
same
identity.
A
B
It's
good
all
right,
okay,
so
this
is
as
we
went
through
in
the
illustrations.
Previously,
this
is
a
resident
services
portal
and
we
developed
this
for
a
poc
and
it's
going
to
demonstrate
everything
that
that
mark
just
went
through
architecturally
and
we'll
we'll
pause
throughout
this.
This
recorded
demo
to
explain
how
some
of
these
pieces
are
moving
through
through
the
system.
So
the
first
thing
with
this
resident
service
you
can
imagine
and
when
I'm
sharing
a
mobile
device
on
the
right
here.
B
That's
that
has
that
that
wallet
up
that
we
talked
about
and
we're
going
to
show
the
process
of
onboarding
basically
into
the
resident
services
portal
and
then
we're
going
to
show
the
the
ability
to
traverse
a
couple
of
these
different
services
using
that
identity
instead
of
creating
a
separate
identity
in
each
in
each
silo
or
each
stack.
So
let's
get
started
with
this
and
I'll
pause
it
throughout.
B
So
we
can
see
the
first
thing
we're
going
to
do
is
we're
going
to
come
in
and
say
we
want
to
go
to
jobs
in
unemployment
and
we
want
to
file
an
unemployment
claim.
Well,
the
first
thing
we
need
to
do
is
get
our
resident
id.
So
in
order
to
do
that,
we're
going
to
start
a
new
verification
request
and
that's
going
to
allow
me
as
the
resident
to
to
validate
to
upload
and
validate
some
existing
information
and
from
that
we're
going
to
create
a
credential.
B
So
as
we
go
through
this
process,
we're
going
to
require
a
driver's
license.
Maybe
a
social
security
number
we're
going
to
upload
the
information
you
can
see.
All
that
information
is
pre-filled
put
in
the
social
security
number
and
submit
it
okay.
So
what
happens
here
so
at
this
point?
All
of
that
information
has
been
recorded
and,
as
mark
indicated,
we're
pushing
that
out
to
a
fabric
based
system,
storing
that
information
and
that
information
is
going
to
be
used
then
for
a
verification
request.
B
So
as
the
resident
I
see
now
that
I
have
a
pending
request,
that
is
that
that
is
proving
out
my
driver's
license
and
my
address,
and
that
is
going
to
now
be
verified.
So
someone
on
the
other
end
of
this
on
the
admin
side
is
going
to
make
the
rules
and
determine
how
that
verification
happens.
In
this
case,
we're
going
to
verify
the
driver's
license
through
an
api,
as
as
mentioned,
we'll
see
that
it's
it's
pending.
B
If
we
go
in
here
and
look
we're
going
to
see
that
the
driver's
license
has
already
been
automatically
verified
through
an
api
call
to
the
dmv,
we
can
still
look
at
the
details
of
that.
If
we'd
like
and
see
the
information
that
was
submitted,
there's
all
the
driver's
license
information
and
now
we
can
go
and
we
can
do
the
same
thing
with
the
social
security
number.
B
Maybe
that's
a
manual
verification
so
there
I
just
provided
the
manual
verification
of
that
service,
and
now
we
have
all
of
our
required
elements
that
have
been
verified
and
and
it's
and
we're
ready
now
to
issue
that
resident
id
or
those
those
set
of
credentials
to
the
to
the
end
user.
So
important
thing
to
note
here
is
the
end
user
is,
is
they're
not
going
through
this
process
right?
This
is
the
administrative
process.
The
end
user
is
done.
They
uploaded
their
documentation.
B
We're
sharing
that
end
user
wallet
on
the
right
here
and
what's
going
to
happen
now,
is
we're
going
to
do
a
couple
of
things?
The
first
thing
we're
going
to
do
is
push
a
message
down
this
connection
to
that
user,
saying
that
all
their
information
has
been
verified
and
we're
ready
to
issue
that
credential
so
we'll
send
that
message.
B
It
happens
through
the
aries
actually
is
what's
delivering
this,
and
it's
sending
that
message
now
and
saying
that
you
know
that
all
the
credentials
has
been
verified
and
you're
going
to
receive
some
credentials
here
very
shortly.
So
when
we
issue
that
same
thing,
we're
going
to
use
that
connection
and
we're
going
to
deliver
a
resident
id
street
address
and
an
identification
number
resident
id
number
and
we're
gonna
a
driver's
license,
we
verified
that
as
well.
B
So
now
we
have
three
credentials
that
have
been
sent
and
issued
into
the
into
the
holders
into
the
the
the
resident's
wallet.
Here
you
can
see
the
street
address
identification
and
driver's
license
now.
So
we
have
all
that
information.
Now,
here's
the
really
cool
thing
about
what's
happening
as
we
go
back
to
those
city
services
to
provide
verification
into
those
service
city
services.
B
B
And
this
will
take
us
to
like
say
a
job
center.
Now
we're
going
to
go
back
to
the
jobs
and
unemployment
that
we
were
trying
to
get
into
originally
this
time
now
to
log
in.
We
just
scan
this
qr
code,
and
you
can
see
here
what
it's
asking
for
to
log
into
jobs
and
unemployment.
It's
asking
for
first
name
last
name
and
a
social
security
number
right,
so
obviously
a
highly
sensitive
site
and
we're
sending
a
social
security
number.
B
B
If
they
come
back
to
the
resident
portal
and
say
they
want
to
access
court
service,
they
can
use
the
same
exact
process,
so
they
don't
have
to
change
their
process.
They
don't
have
to
go,
look
for
a
different,
username
or
different
password.
They
go
through
the
same
exact
process
this
time
when
they
scan
this
qr
code.
B
The
health
and
human
services
department.
Here
is
asking
for
a
completely
different
set
of
information.
They
don't
require
social
security
number.
They
require
the
id
number
and
a
driver's
license
number
and
a
date
of
birth.
So
again
the
end
user
doesn't
have
to
go
and
find
that
information
or
do
anything.
It's
all
been
issued
to
them
from
the
onboarding
request.
All
they
have
to
do
is
decide
if
it's
okay,
they
send
the
information
it
sends
it
back
to
the
court
services
and
they're
logged
in
to
their
to
their
court
services
site.
B
B
Certainly
yeah
so
so
using
the
same
structure,
if
you
will
really
simplify
the
cross
department
federations,
you
know,
if
you're
looking
at
ways
to
get
through
different
identity,
silos,
identity
stacks.
This
provides
you
a
common
way
to
traverse.
Those
passwordless
login,
obviously,
is
is
that
the
biggest
thing
here
that
probably
came
through
in
this
demo
is
that
there
is
no
password
we're
not
masking
the
password
it.
There
is
no
password.
The
password
is
your
identity.
B
So
that's
anywhere
that
you
have
those
services
where
you
really
need
a
strong
identity
proofing
and
then
and
a
and
you
know,
zero
trust
is
getting
kicked
around
my
my
impression
this
is
where
zero
trust
starts
right.
Let's
remove
those
passwords,
not
mask
them,
let's
remove
them,
and,
and
so
this
this
solution,
this
technology
lends
itself
very
well
to
that
fraud
reduction.
We
talked
about
a
little
bit
building
a
system
that
is,
you
know
that
that
does
a
better
job
of
proving
who
we're
talking
to
and
better
know.
B
Your
customer
elements
is
going
to
reduce
fraud
and
then
mixing
and
matching.
As
I
mentioned,
the
idp
solutions,
you
really
eliminate
two-factor
solutions.
You
can
integrate
consent
forms
all
kinds
of
stuff
on
top
of
this
technology,
using
the
same
platform
that
we
just
talked
about,
because
you
have
a
strong
auditing
capability
as
well
as
a
strong
identity
data.
B
B
Id
ramp,
obviously
we're
focused
on
decentralization
of
identity,
really
removing
passwords
and
any
kind
of
a
zero
trust
implementation.
We
worked
with
american
electric
power,
reduced
johnson
third
party
fraud
prediction
projects:
pricewaterhousecoopers
is
doing
a
zero
trust,
webcasting
solution
using
verifiable
credentials
to
to
gain
access.
We
actually
really
excited
about
a
platform
similar
to
hop
in
here
called
kiko
chat
that
is,
is
using
is
using
passwordless
self-sovereign
identity
to
log
into
their
platform.
So
you
don't
have
to
register
for
an
account.
B
You
just
go
in
and
use
your
verify
email
credential
to
log
in
so
it's
really
cool
stuff.
We
are
we're
laser
focused
and
in
zero
trust
solutions
and
really
all
things
that
that
are
around
the
decentralized
identity
spectrum.
So
the
solution
like
we
just
went
through
and
just
demonstrated,
are
things
that
our
platform
does
very
natively
and-
and
so
it's
it's
an
exciting
time
for
identity
for
sure
so
mark
I'll.
Let
you
I'll
let
you
take
over
and
go
a
little
bit
more
on
id
on
that
oracle.
A
Yeah
sure,
thanks
mike
so
a
little
bit
about
oracle
blockchain
platform.
Obviously,
as
you
saw
here,
hyperledger
fabric
piece
of
the
solution
is
actually
a
leveraging
oracle
blockchain
platform,
which
is
fabric
based
the
cloud
service
also
available,
and
the
presentation
on
premises.
It's
pre-assembled
platforms
that
can
interpret
with
other
fabric
nodes.
We
have
a
number
of
deployments
where
oracle
fabric
nodes
and
mixed
in
with
ibm
or
microsoft,
azure
ozos
others
in
various
multi-cloud
deployments,
as
well
as
with
on-premise
nodes
as
well,
so
provide
a
lot
of
flexible
topologies.
A
A
lot
of
enterprise,
great
features.
It's
really
focused
on
simplifying
the
whole
experience
of
adopting
blockchain
from
a
deployment
perspective
through
ease
of
integration
with
a
powerful
api
gateway,
is
easy
to
secure
with
membership
management
and
fine-grained
access
control,
very
powerful
operational
sets
of
tools
and
apis
and
easy
extensibility,
as
I
mentioned,
with
either
oracle
nodes
or
third-party
nodes
running
fabric,
and
in
addition,
we
have
released
recently
a
number
of
new
capabilities
focusing
on
the
application.
Space
right.
A
Making
infrastructure
and
operations
easier
is
great,
but
then
there
are
people
who
are
going
to
also
want
to
understand
how
to
quickly
build
applications
or
use
existing
applications.
So
we
have
a
number
of
isv
and
the
size
solutions
in
our
portfolio
of
partners
and
then
we've
released
some
development
tooling
as
well:
a
blockchain
application
builder
that
speeds
up
the
custom
application
development
effort.
A
It
increases
productivity
and
development
and
testing,
but
also
can
automatically
generate
chain
code
from
declarative
specifications,
and
so
this
basically
provides
a
low
code
environment
and
in
fact,
a
session
tomorrow
morning
at
I
believe,
1
10
p.m.
Eastern
standard
time,
where
we're
going
to
be
presenting
the
blockchain,
upbuilder
and
local
development
platform
for
hyperledger
fabric.
So
you
might
want
to
attend
that
and
if
interested
in
development
and
low
code
with
that
there's
a
lot
of
other
information
that
you
can
access.
A
We
appreciate
you
participating
in
the
session
on
the
left
hand
side
here,
you
see
various
links
for
oracle,
blockchain
information,
our
web
pages
blogs
at
a
very
active
developer
site
and
a
number
of
videos
available
on
youtube
and
oracle
tube
and
on
the
right-hand
side.
This
contact
information
for
a
drop
as
well
with
that,
let's
go
ahead
and
take
some
questions
here,
we'll
be
happy
to
answer
anything
that
you
have.
I
think
we
have
about
10
minutes
or
so
so.
B
A
B
Sure
so
a
couple
of
them
I
responded
to
already
I'm
trying
to
keep
up
here.
End
users
need
to
be
online.
I
posted
that
in
there.
Basically,
those
messages
will
queue
up
and
be
pushed
out
when
the
device
becomes
active
again.
So
that
is
part
of
the
aries
communication.
Respect
that
that
mediator
will
hold
those
messages
and
push
them
out.
B
Hopefully
that
answers
that
question
the
credential
schema
that
we
showed
is
is
actually
an
indie-based
schema,
so
that's
defined
on
the
indie
network.
The
schema
for
the
credentials
that
go
out
so
fabric
doesn't
know
about
that.
There's
no
correlation
between
those
two,
which
is
a
good
thing
actually,
and
you
know
at
any
time
that
that
that
the
the
the
correlation
can
be
severed
by
the
by
the
end
user
at
any
time
to
basically,
you
know
change
that.
B
B
Yeah
so
so
david
asked
a
question
about
verifiable
credentials
being
issued
by
a
trusted
issuer
and
yeah.
That's
a
great
point
dude.
So
what
is
happening?
What
we?
What
we?
What
will
happen
right
in
the
very
near
future
as
as
states
and
governments,
and-
and
this
is
certainly
moving
a
lot
faster
in
europe
than
it
is
here
in
the
us,
but
the
issuance
that
we're
doing
here
is
is
an
issuance
based
on
a
endorsement
agreement.
B
B
On
behalf
of
some
other
organization
and
the
demonstration
here,
we
showed
a
couple
different
ways
of
doing
that
right.
So
we
do
have
a
trusted
issuer
in
the
state
because
we
used
a
dmv
api
to
automatically
validate
that
the
information
on
that
uploaded
driver's
license
was
valid
and,
of
course,
that
process
is
is
getting
better
all
the
time
scanning
physical
documents
require
a
liveness.
You
know
test,
and-
and
all
of
that
is
baked
in.
B
B
We
can
do
a
utility
bill,
we
can
do
whatever
and
we
can
cross-reference
all
of
that
information
to
make
sure
that
we
are
finding
that
identity,
as
that
evolves,
that
there
will
be
a
lot
more
ways
of
capturing
that
information
and
doing
that
that
identity,
verification
before
it's
bound
and
that's
yeah.
That's
a
very
important
piece
of
the
of
the
process
for
sure.
A
And
of
course
you
know
now
that
information
is
verified
through
some
additional
machine
learning
tools
to
ensure
that
the
images
are
matching
properly
and
they're
trying
to
detect
false
images.
You
know
somebody's
trying
to
falsify
you
know
something
on
the
documents
of
the
signatures,
etc.
So
there
is
a
number
of
verification
means
in
the
back
end
that
can
be
applied
to
different
documents,
and
you
know
facial
scans,
etc.
A
The
framework
that
we
showed
here
is
very
flexible,
and
so
it
can
easily
be
adopted
to
leverage
whatever
additional
back-end
verification
might
be
necessary,
depending
on
where
you're,
creating
the
identity.
Right,
if
you
are
in
opening
a
bank
account,
if
you
are
going
to
getting
a
library
card,
there's
all
kinds
of
different
requirements
and
each
organization
can
decide
the
level
of
verification
necessary
and
then
plug
in
those
mechanisms.
B
So,
if
they're
asking
for
a
social
security
number,
that's
coming
from
a
credential
that
was
much
much
more
tightly
scrutinized
on
the
front
end,
so
the
the
process
will
will
naturally
make
sure
that
the
beholder
of
those
credentials
has
been
through
the
required
process
to
do
the
binding
of
their
identity.
You
know
at
those
different
levels.
A
Let's
see
what
are
the
there's
a
question
here?
How
do
you
ensure
that
the
data
extracted
from
the
scanned
document
is
reliable?
You
may
not
want
to
share
the
scanned
document
entirely
only
subset
of
the
data.
Well
again,
there
is
techniques
that
can
apply
depending
on
the
document.
Sometimes
it
involves
some
machine
learning
work.
In
other
cases,
you
actually
have
the
document
verifies
through
apis
with
the
issuer.
B
B
So
yeah
there's
that
question
about
there's
a
question
about
passwords.
There
is
no
password
there's
just
the
private
public
key
you're,
correct
public.
The
private
key
is
only
held
on
the
mobile
device
in
the
in
the
in
the
credential
demonstration
that
we
showed,
and
if
that
key
is
lost,
there
are
ways
of
recovering,
so
you
can,
as
an
end
user,
choose
to
back
up
you
know
or
or
restore
so
there
are
ways
of
recovering
that
or
you
simply
go
through
the
proofing
process.
Again
right.
That
is
a
you.
B
Don't
have
to
go
through
the
whole
process,
but
you
can
go
back
to
the
you
know:
the
credential
manager,
the
application.
If
you
will
and
say
hey,
I
lost
my
identity.
They
could
go
through
a
an
abbreviated,
identity,
proof
and
then
just
reissue
through
that
same
type
of
connection
right,
you
make
the
connection,
push
the
credential
back
down.
So
it's
it's
not
it's!
It's
actually
no
different
than
rebuilding
your
physical
process.
Today
you
know,
if
you
lose
your
driver's
license,
how
do
you
do.
A
B
It's
actually
easier
than
that,
because
you
don't
go
through
the
physical
process
of
going
into
to
have
it
issued
again,
but
but
it
can
be
rebuilt
that
exact
same
way:
lots
of
questions
about
yeah,
personal
identities
and
and
binding.
How
do
you
know
who
the
person
is,
and
I
think
we
answered
that
that
process
is
getting
getting
better
every
day
and
we
incorporate
multiple,
obviously
to
to
make
sure
that
we
can
meet
all
the
business
requirements.
A
A
All
of
the
other
information
we
talked
about
that's
stored
around
granting
access,
permissions
on
request
and
then
whoever's
actually
accessing
the
data
that's
all
stored,
but
with
the
user.
Obviously,
as
an
attribute,
there
may
be
situations
where
it's
beneficial
to
actually
have
a
separate
enrollment
for
each
user
so
that
they
become
actually
like
a
client
organization
member
in
the
fabric
network,
in
some
rare
cases,
but
in
most
cases
that's
not
required.
A
B
B
B
Well,
there
is
on
the
on
the
on
the
indy
ledger
side.
There's
that
that
endorsement
capability-
I
was
talking
about
so
you
build.
You,
have
your
ledger
and
and
in
order
to
make
those
transactions
or
call
those
transactions,
there's
a
there's,
a
specific
endorser
agreement.
That
has
to
be
so
there's
it's
kind
of
a
governance
question
if
you
put
it
on
a
on
a
ledger
that
you
have
to
have
a
specific
endorsement
capability
in
order
to
write
to
that
ledger,
so
so
there's
no
way
that
you
could
emulate
that
transaction.
B
A
A
You
know
as
far
as
the
permissions-
and
you
know,
if
you're
talking
about
the
people
who
are
doing
the
administration
on
the
back
end,
the
application
will
obviously
enroll
them
as
a
client
user,
so
those
people
will
have
certificates
and
they
only
allow
doctors.
Assuming
that
you
know
they
are
in
charge
of
verifying
certain
documents.
A
B
Right,
the
really
important
takeaway
from
the
presentation-
and
the
demonstration
here
is:
how
is
the
mix
of
technologies
to
form
a
really
simple,
to
integrate
solution
right
for
the
services?
It's
very
easy
to
integrate
and
build
this
build
this
dynamic
verification
system
and
we're
providing
some
significant
benefit
to
the
end
user
by
making
it
simpler
and
easier
for
them
to
interact
so
the
the
this
you
know
what
really
makes
the
project
special
and
the
solution
special.
B
Is
that
we're
not
trying
to
fix
everything
with
a
single
tool
right,
we're
using
the
best
best
of
class
solutions,
as
mark
indicated
earlier,
to
really
provide
the
best
experience
for
both
the
data
integrity
security
as
well
as
the
user.
Friction
the
user
experience
to
make
that
you
know
to
make
that
solution
right.
B
A
A
A
B
Yep
and
same
with
me,
you
can
find
me
on
linkedin
or
find
it
on
our
website.
Idramp.Com
has
a
lot
of
other
podcasts
and
stuff
that
we've
recorded
and
and
some
demonstrations
of
kind
of
different
things
that
we're
doing
with
the
platform.
So
please
reach
out.
We
always
love
talking
about
this
solution
in
particular,
because
it's
using
such
great
technology
in
an
interesting
way
so
yeah
reach
out.
A
All
right,
so
I
think
at
this
point
thanks
everybody
for
attending
the
deck
itself
is
available
on
the
schedule.
App.
If
you
go
to
the
schedule
and
find
the
session,
you
will
be
able
to
download
the
presentation
and
we'd
love
to
hear
from
you.
If
you
have
any
follow-up
questions,
please
shout
out
to
mike
or
myself
thank.