►
From YouTube: Public Sector SIG: Self-Sovereign Identity in Govtech for Financial & Healthcare Inclusion
Description
Self-Sovereign Identity in Govtech for Financial & Healthcare Inclusion
Identity is the permission to begin any relationship. With the wide availability of internet digital identity has become the most significant technology trends on the planet. However contrary to so much advancement of technology the authentication and online sharing of personal data models have hardly undergone any changes in last few decades. Data leaks and unauthorized sharing of personal data have raised many security breaches costing billions to organizations.
Blockchain and Biometrics together bring the perfect universal solution that is decentralized, transparent, tamperproof, efficient and highly scalable to help organizations in their journey embracing next-gen authentication. This session would give an insight to the flaws in existing identity architectures and how the nextgen identity solution would give rise to many new business models and use cases especially for financial and healthcare inclusion in public sector.
Speaker: Debajani Mohanty
Debajani Mohanty, one of the top 30 Blockchain Influencers of India (Singapore Fintech news) is a Solution Architect and author of 5 Amazon bestseller Blockchain books some of which are translated to German and Chinese to reach the wider mass. Pioneer Blockchain solutions developed by Debajani in different verticals have attracted global attention. Debajani works as an Self Sovereign Identity expert at EarthId, Honorary Faculty with Amity University and is a keynote speaker at many national and international innovation summits.
Follow her on twitter: https://twitter.com/debimr75
Follow her on LinkedIn: https://www.linkedin.com/in/debajanimohantypmp
----
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
A
The
recording
and
with
that
our
topic
today
is
actually
an
important
one.
We've
got
self-sovereign
identity
and
government
technology
for
financial
and
healthcare
inclusion,
and
I
couldn't
think
of
a
topic
that
has
more
relevance
for
everybody
around
the
world
in
terms
of
both
the
economies
and
that
we
operate
in
the
societies
that
we
work
in
and
live
in
and
then
finally
related
to
healthcare
as
well.
A
So
with
that
we
are
now
streaming
our
session
live,
so
I
want
to
turn
our
recession
over
to
the
johnny
mahonte,
who
is
not
only
a
blockchain
expert
but
she's
written
five
books,
and
certainly
when
it
comes
to
self-sovereign
identity,
identity
in
general,
she's,
a
leading
expert
around
the
world.
So
with
that
johnny?
Can
I
turn
it
over
to
you.
B
B
So,
let's
start
with
the
issue
and
need
of
global
identity
for
every
human
and
not
not
only
human,
also
for
machines
and
for
animals
in
future,
because
in
coming
days
you
know,
we
are
already
aware
how
the
iot
works.
So
even
you
know,
every
human
being
would
be
needing
more
than
one
identity
each
for
their
devices
and
even
for
farming
you
would
be
needing
identities
for
animals
in
future.
So
that
is
why
it's
a
it's
a
huge
opportunity.
B
So
what
the
world
needs
at
the
moment
is
the
efficient
digital
identity
infrastructure
that
can
help
to
reduce
fraud
and
protects
rights
and
increase
transparency,
so
digital
identity
also
holds
the
promise
of
enabling
economic
value
creation
for
each
of
these
three
groups.
I
just
mentioned
here
by
fostering
increased
financial,
health
and
educational
inclusion.
B
So,
first
let
me
introduce
you
to
this
digital
identity.
So
what
is
digital
identity?
It
is
any
personal
data
that
identifies
us
online
like
we
use
our
digital
identity
for
onboarding
and
registration
propers
to
websites
any
kind
of
identity,
management,
authentication
authorization
and
access
to
online
data
or
de-registration.
B
B
So
what
is
correlation?
It's
like.
You
know,
let's
say
that
I'm
sharing
my
health
care
data
with
my
hospital,
I'm
sharing
my
financial
data
with
my
bank
and
my
educational
data
with
the
university.
So
when
sharing
this
data,
then
I'm
using
perhaps
my
email
id,
which
is
common
tool,
or
maybe
maybe
my
contact
number,
which
is
common
to
all.
Then
it
is
also
possible
that
they
can
use
that
particular
you
know.
Email
id
or
contact
number
to
know
know
that
what
is
I
mean?
B
It
is
also
possible,
like
you,
they
can
correlate
and
trace
back
to
me
that
I'm
the
journey-
and
this
is
my
health
care
data.
This
is
my
bank
in
a
financial
data,
and
this
is
my
educational
data,
so
this
is
called
identity
correlation,
so
we
need
a
model
which
can
actually
you
know,
solve
all
these
issues,
which
is
there
in
the
current
digital
identity
system.
B
Now
how
we
are
managing
our
digital
identity
that
also
has
evolved
over
the
years.
The
first
one
is
siloed
or
centrally
managed
identity,
which
has
been
there
in
the
market
for
last
three
decades
or
more,
like
even
it's
used
in
many
applications.
Today
you
are
sending
a
user
id
and
password-
or
maybe
let's
say
when
you
are
registering
with
the
website.
The
website
is
creating
a
user
id
and
password
for
you.
Perhaps
you
are
choosing
a
user
id,
but
then
the
website
is
keeping
that
data
with
themselves.
B
So
for
each
application
you
are
having
a
different
set
of
credentials,
so
they
might
be
using
a
database
or
ldap
or
active
battery.
But
this
is
the
way
they
are
saving
your
credentials
and
then
the
second
one
is
a
federated
identity
model
where
the
user
is.
Actually
I
mean
that
is
the
identity
provider.
So
here
there
is,
the
server
is
not
giving
the
information
the
credential
information,
rather
identity
provider,
is
doing
that
job.
So
you
are
logging
into
that
identity
provider.
B
First,
it's
actually,
you
know
responding
with
a
token,
then
you
are
using
that
token
to
get
access
to
different
third
parties,
so
this
model
works
in
sso.
This
model
works
in
open
id
and
all
so
in
both
these
models.
We
have
centralized
server
because
here
in
the
federated
identity
in
the
identity,
provided
is
the
centralized
server.
So
these
two
models
are
prone
to
mass
hacking
and
single
point
of
failure
now
coming
to
self-sovereign
identity.
So
ssi
is
a
new
decentralized
model
to
manage
this
digital
identity.
B
Here
we
have
an
issuer
organization
that
issues
verified
credentials.
We
usually
call
it
vc
to
the
user
that
is
saved
securely
in
the
user's
mobile
device.
At
the
same
time,
the
issuer
is
also
sending
a
signed
reference
hash
to
a
public
blockchain
and
it's
being
signed
using
its
own
private
key.
Now
the
user
can
share
the
whole
earth
part
of
the
data
to
the
verify
organization,
along
with
the
issuers
public
decentralized
identity.
B
Now
the
verifier
can
convert
this
data
to
a
hash
and
check
if
this
has
on
the
data
matches
with
that
on
the
blockchain
to
know
that
if
it
is
valid,
so
this
example
can
be
can
be
a
scenario
where
the
issuer
is
the
passport
office
and
the
verifier
is
the
visa
office.
So
the
user
can
share
their
data
with
the
verifier.
So
now
how
it's
happening,
the
users
are
sharing.
B
You
know
in
a
traditional
model,
they
are
sharing
that
you
know
printed
copy
of
their
passport
and
the
verifier
is
again
doing
a
background
verification.
So
there
is
no
direct
way
to
know
that,
whether
it's
a
verified,
credential
or
not.
So,
with
this
kind
of
architecture,
we
can
do
that
on
the
spot
and
at
a
later
point
of
day,
if
the
issuer
wants
to
revoke
the
verified
credential
they
can,
they
can
send
a
new
person
to
the
blockchain
so
that
the
hash
should
not
match
any
longer.
B
So
the
verifier
would
know
that
it
is
revoked
or
maybe
the
shared
credential
is
not
valid.
So
this
is
kind
of
the
60
000
ft
view
of
this
architecture,
but
how
exactly
it
happens?
Let's
go
down
a
little
bit
and
see
that
how
this
entire
thing
works,
step
by
step
like
if
some
of
you
want
to
implement
it
in
real
life.
How
exactly?
What
are
the
steps
that
you
have
to
follow?
B
The
first
thing
is
the
issue
organization
has
to
create
a
schema
or
data
structure
like
let's
say
that
the
passwords
office
says
that
these
are
the
data
that
I'm
going
to.
You
know
print
on
your
passport.
You
know
so.
Similarly,
you
have
to
create
a
schema
for
the
vc
creation
and
and
the
issuer
has
to
create
a
public
and
private
key
pair
and
a
public
date
associated
with
it.
B
So
this
public
date
is
actually
public,
so
this
is
a
decentralized
id,
so
this
is
similar
to
a
user
id,
but
this
is
public
and
it
is
visible
to
everyone
like
they
can.
You
can
publish
it
on
the
website,
so
the
what
the
user
is
doing
for
each
set
of
vc,
the
user
is
creating
a
public
and
private
key
pair
and
a
private
date.
So
for
each
vc
it
there
is
a
separate
private
need
of
private
identifier.
B
B
It's
actually
checking
that
whether
the
token
is
right
so
that
you
know
if
it,
what
is
the
actual
public
key
of
the
user
and
then
converting
the
vc
to
a
hash
and
signing
it
with
its
with
their
own
private
key
and
writing
it
to
a
blockchain
and
the
vc
is
written
back
to
the
user,
so
that
vc
is
actually
a
combination
of
digital
data.
Now
what
the
user
can
do?
B
The
user
can
share
the
public
key
on
public
key,
as
well
as
the
issuer's,
deed
or
decentralized
identity
and
a
token
signed
with
its
own
private
key
along
with
the
vc.
So
what
the
verifier
would
check
that
from
the
token,
the
verifier
would
know
that
you
know,
because
the
public
key
is
available
so
using
the
public
key.
The
verifier
can
decrypt
the
token
to
know
that
whether
this
is
the
this
is
the
public
key
of
the
user
so
and
then
because
it's
signed
by
the
user.
B
The
second
thing
it
would
do
is
to
is
to
convert
that
data
to
a
hash
and
check
on
the
blockchain
that
whether
it
is
signed
by
this
issue,
because
the
date
of
the
issue
is
available,
so
whether
it's
signed
by
the
issue,
whether
the
issuer
is
valid
and
whether
the
issue
the
dc,
is
valid.
So
there
are
so
many
things
which
are
verified
and
ultimately
the
vc
is
verified
successfully.
So
this
is
the
entire
flow.
B
So
here
at
a
later
point
of
time,
if
needed,
then
the
issuer
can
also
revoke
the
vc.
So
this
kind
of
architecture
ensures
integrity
of
the
data
ownership,
privacy
and
security
and
validity
of
the
data
are
checked
all
right.
So
there
are
it's.
Actually
you
can
see
that
the
ssi
network
is
pretty
complex.
B
So
what
I
showed
you
is
only
the
ssi
layer,
but
then
then
there
are
other
layers
also
which
you
have
to
handle.
You
have
to
handle
the
web
standards,
the
authentication
standard.
So
how
how
somebody
is
getting
access
to
this
kind
of
ssi
network?
That
also,
you
know
you
have
to
think
of
a
authentication
mechanism,
then
also
a
open,
blockchain
and
a
decentralized
identity
network.
So
all
these
things
you
have
to
handle
on
the
top.
Now,
let's
see
how.
B
So
there
are
different
layers
in
ssi
at
the
heart
of
it.
As
I
showed
you,
there
is
a
public
ledger.
Then
there
is
a
private
and
identity
storage.
Is
there
then
agent
on
half,
so
agents
are
needed
for
message.
Transfers
and
hubs
are
needed,
for
you
know
having
a
replication
of
the
data
and
then
client
devices,
so
there
are
so
many
different
layers
that
you
have
to
handle.
Let
me
show
you
how
so
here
so
here
you
can
see
that
alice
is
a
user.
B
So
c
is
having
a
mobile
device
so
from
the
mobile
device
she
can
connect
to
a
public
dlt,
and
here
she
is
she's
carrying
all
her
personal
data
here,
which
is
not
only
alphanumeric.
It
could
be
biometrics
data
also,
and
then
there
is
bob
who
is
having
his
personal
data
in
his
mobile
device.
At
the
same
time,
he
is,
you
know,
sharing
a
copy
to
a
cloud
storage
so
that
later
on,
if
the
mobile
device
is
stolen
or
broken
or
large,
whatever
whatsoever,
he
can
create
another
copy
and
revive.
B
You
know
his
position.
There
then
again,
there
is
a
issuer
organization
here,
and
the
issuer
organization
is
keeping
all
the
data
in
the
cloud
storage.
So
you
can
keep
all
your
data
either
in
its
natural
format
or
in
encrypted
format
as
needed.
So
encrypted
would
work
a
little
slower,
but
then
it's
it
gives
you
additional
security,
and
then
there
is
a
public
dlt
which
is
responsible
for
creation
of
all
the
digital
identities.
B
B
B
Then
she
is
joining
a
school
and
she
is
producing
both
her
birth
certificates
and
her
national
identity
number
and
she
is
getting
admission
to
the
school
or
the
university
and
finally
says
joining
an
organization
and
where
she
has
to
produce
all
the
previous
certificates
depending
upon
the
requirement
and
then
see.
Ultimately,
she
passes
out
from
the
college
or
university
and
finally,
maybe
c
would
be
joining
a
workplace.
So
here
you
can
see,
there
are
different.
Set
of
certificates
are
being
issued
by
different
organizations.
B
So
this
actually
works
like
a
chain
like
you
are
carrying
the
first
certificate
to
the
second
organization,
then
the
second
organic
from
the
second
organization
you
are
carrying
it
to
the
third
organization
like
that.
So
and
each
organization
can
walk
dual
like
each
organization
can
be
issued
as
well
or
under
verified.
So
usually
they
are
very
fire
first
and
the
issuer
later,
but
this
is
in
this
kind
of
chain.
B
The
responsibility
of
the
first
you
know
issued
is
maximum,
so
usually
it
is
good
that
if
the
first
issuer
is
a
government
based
organization,
so
each
of
this
data,
the
user
can
carry
in
his
mobile
device
and
as
per
need,
the
user
can
share
it
to
different
verifiers,
and
this
personal
data
can
be
shared
in
many
different
modes
like
traditional
data.
Traditional
way
of
sharing,
like
I'm
sharing
my
name
as
it
is
that
johnny
mahanti,
the
second
one
is
selective
disclosure
like.
I
don't
want
to
share
all
the
data
in
my
passport.
B
Perhaps
there
are,
there
is
some
data,
maybe
your
marital
status,
or
maybe
I
mean
what
what
kind
of
information
is
the
certain
kind
of
information
which
you
don't
want
to
disclose?
So
then,
then
there
is
zero
knowledge
proof.
That
means
that
you
are
sharing
your
data.
Let's
say
that
there
is
a
website
who
doesn't
want
to
who
sells
alcohol
only
to
somebody
who's
ever
waiting.
So
how
would
I
prove
that
I
am
above
writing.
B
Should
I
disclose
my
data
bar,
but
data
birth
is
a
private
information,
so
I
would
just
reply
in
yes
or
no
or
true
or
false
and
the
verified
using
cryptology.
That
can
also
be
checked.
You
know
the
verifier
can
change
that,
whether
the
information
that
I
am
providing
is
correct
or
not.
So
this
is
called
zero
knowledge,
proof
and
then
self-adhesive
there's
some
data
that
doesn't
need
somebody's
attestation.
Like
let's
say
I
am
sharing
my
hobby
to
somebody.
So
no
nobody
needs
to
certify
it.
B
B
So
the
australian
government
is
delivering
digital
identity,
a
program
that
will
allow
government
services
to
be
easily
available
to
people
and
businesses
online.
At
any
time,
so
so
their
plan
is
to
cover
many
services
through
one
national
level,
identity
for
each
citizen
of
the
country.
Also,
most
of
the
paper
based
checks
would
be
transferred
to
digital
experiences.
So,
like
you
can
see
in
the
right
hand
side,
so
they
are
going
to
cover
you
know:
taxation,
welfare,
health,
business,
education,
social
services,
banking,
etc.
B
So
so
using
the
user's
biometrics
and
liveness
detection
test,
the
user
can
be
authenticated
to
use
these
services,
so
they
are
using
a
decentralized
identity
model
and
this
project
is
still
under
development.
The
second
one
is
singapore.
If
I
am
not
wrong,
this
is
no
longer
in
pilot.
This
might
have
gone
to
production.
I
have
to
make
sure
again,
so
singapore
is
authenticating.
B
Four
million
of
its
citizens
online,
with
facial
verification
supplied
by
there
is
a
organization
called
iproof
and
so
they're
using
simple
face
biometrics
check,
so
the
users
can
get
secure
online
access
to
government
services
and
private
organizations
can
also
take
advantage
of
this
national
digital
identity
infrastructure.
To
authenticate
customers
online
then
then
comes
canada,
so
in
canada
they
are
providing
this.
This.
B
This
project
name
is
called
taylor
swan,
so
users
can
the
citizens,
can
you
know
upload
their
certificates
online
and
the
government
can
use
it
again
and
again,
depending
on
that
requirement,
they
won't
ask
the
the
citizens
again
and
again
and
on
the
top
of
that,
the
government
is
also
providing
certificates
to
start-ups.
Like
let's
say,
let's
say
there
is
a
start-up
in
canada,
so
this
project
is
actually
in
british
columbia.
So
so,
let's
say
that
there
is
a
start-up
and
they
want
to
work
with
with
the
organization
in
india.
B
So
how
I'm
an
organization
in
india?
How
do
I
know
that,
whether
that
organization
is
fake
or
real
genuine?
So
I
would
trust
the
canada
government,
so
that's
why
I
would
trust
any
certificate
issued
by
canada
government
to
that
particular
startup.
So
this
is
how
even
even
india
is
considering
a
similar
project.
Now
now
this
is
a
very
interesting
use
case.
This
is
called
I
respond.
B
B
B
Now,
if
the
child
is
trying
to
cross
the
border
at
the
same
time,
the
border
officers
would
check.
You
know
whether
the
decentralized
id
is
a
valid
one
and
whether
the
biometrics
associated
with
that
is
matching
with
the
child
and
the
custodian
who
is
escorting,
the
child
and
again
there
would
be
a
need
of
a
consent
by
the
legal,
the
guardian.
So
if
all
these
things
are
working,
fine,
then
only
the
child
can,
you
know,
would
be
able
to
cross
the
border
along
with
the
legal
guardian.
B
B
So
digital
identity
is
the
hot
cave
of
today's
world.
You
can
see
in
the
picture
how
most
countries
in
the
world
are
doing
some
research
or
other
like
here.
You
can
see.
There
are
so
many
initiatives,
but
not
all
of
them
are
decentralized
but,
like
I
said,
australia
is
working
on
it.
Singapore
is
working
on
it
and
then
there
are
certain
countries
in
africa.
B
Uk
perhaps
is
working
on
a
government
dot
uk
is
working
on
very
fire.
Credential
british
columbia
in
in
north
america
is
working
on
it.
So
many
of
these
countries
are
working
and
not
only
that
they
actually
can
they
help
to
implement
the
privacy
laws
like
the
gdpr,
pdp,
pdpv,
etc,
and
by
implementation
of
ssi.
You
can
actually
adhere
to
all
the
standards
and
also
by
year,
2023
65
of
the
world's
population
will
have
its
personal
information
covered
under
modern
privacy
regulation
of
from
10
today.
B
B
Then
I'll
I'll
cover
some
area
of
research
in
ssi.
So
there
are
so
many
ssi
protocols
available
in
the
market,
so
hyperledger
has
got
its
own.
A
protocol
called
indie
and
aries
ethereum
has
got
civic
and
u-port,
and
microsoft
has
is
coming
with
iron,
which
is
still
under
development,
and
I'm
currently
working
with
earth
id
and
we
are
using
hashgraph.
So
these
are
the
different
protocols
and
there
are
many
more
you
can.
B
You
can
visit
w3c
site
and
you
can
find
many
more
possible
ssi
protocols
and
you
don't
have
to
abide
by
any
particular
one.
You
can
just
see
that
which
one
sitting
here.
So
this
is
the
architecture
of
art
id
that
I'm
currently
working
on.
So
here
you
can
see
in
the
right
hand,
side
we
are
using
hashgraph,
but
you
can
use
anything.
B
B
Okay,
so
here
you
can
see
that
in
the
right
hand,
side
we
are
using
hashgraph,
but
but
you
can
use
hyperledger
indio
here
or
ethereum
over
here,
depending
upon
your
project's
needs
and
also
you
can
see
in
the
left
hand,
side,
we
are
not
only
creating
this
kind
of
architecture
only
for
in
human
beings,
but
also
for
iot
applications
iot
devices
in
future.
So
this
is
the
roadmap
and
also
the
like.
I
said
the
user
starter,
personal
data
can
be
saved
on
device
or
it
might
be
stored
as
a
copy
on
iphone.
B
B
First
of
all,
you
have
to
you
have
to
know
that
what
kind
of
technology,
what
kind
of
public
key
infrastructure
that
you
are
doing,
you're
using
whether
it's
scalable
your
your
solution
is
scalable
and
whether
the
throughput
is
good
because,
unlike
b2b
blockchains,
the
ssi
needs
you
know,
the
requirements
of
ssi
is
very
different
because
you
are
trying
to
cater
to
the
needs
of
not
hundreds
of
thousands
but
millions
and
billions
of
people.
So
that
is
why
it
has
to
be
scalable
extremely
scalable.
The
cyber
security
should
be
good
enough.
B
It
should
be
interoperable
so
that
you
know,
even
if
you
are
on
different
platforms,
somebody
is
working
on
indie
or
iris,
somebody's
working
on
ethereum
somebody
working
on
on
some
like
we
are
working
with
hashgraph,
so
that
could
be
different,
blockchain
platforms.
You
know
identities
created
on
different
platforms,
but
still
they
should
be
interoperable.
B
What
kind
of
data
sharing
technology
are
you
using
how
effective
they
are?
So
like?
I
already
discussed
about
selective
disclosure
and
zero
knowledge
group,
who
are
your
validated
nodes,
so
what
it
means
that
so
the
consensus
model,
because
this
is
ssi,
is
associated
with
the
blockchain,
so
that
blockchain
is
should
should
not
be
something
like
bitcoin
or
you
know,
ethereum
one
where
we
have
proof
of
work
which
is
extremely
slow,
and
so
you
cannot,
you
know,
work
on
that
kind
of
technology.
B
B
With
finality
in
seconds
then
cyber
security
hashgraph
is
resistance
against
ddos
cyber
and
spoofing
attacks.
Then,
in
terms
of
interoperability,
it
can
be
easily
integrated
with
other
date,
networks
and
selective
disclosure,
knowledge
proof.
We
are,
you
know,
trying
to
cover
each
and
every
possibility
like
greater
than
equal
to
less
than
equal
to
greater
than
less
than
so.
B
When
it
comes
to
validated
nodes.
Hashgraphs
valid
nodes
are
industry
leaders
in
different
verticals,
like
google,
you
know
ibm,
we
pro
russia
telecom,
fia
strata
telecom,
so
these
are
the
validated
nodes
or
stewards
or
the
students
of
hashgraph
network.
So
in
that
sense
also,
this
is
good
and
integration
of
biometrics.
We
are
trying
to
integrate
with
different
kind
of
biometrics,
which
are
physiological
as
well
as
vibram.
We
are
trying
with
a
face.
We
have
already
completed,
we
are
also
trying
by
iris
and
fingerprint
and
in
future
we
have.
B
B
Now
I'll
just
cover
one
use
case,
which
is
next-gen,
authentication
and
authorization
architecture.
I
think
that
most
of
you
might
have
heard
of
fido.
So
fido
is
on
device
authentication
without
the
need
of
otp
or
password.
So
now
we
are
gradually
moving
towards
a
passwordless
model,
but
what
I
am
discussing
is
even
ahead
of
it,
so
I'm
going
to
discuss
decentralized
biometrics,
so
first
we
need
to
understand
a
little
bit
on
why
this
is
needed.
B
So
what
are
the
different
personal
data
management?
You
know
methodologies
as
of
today.
How
are
you
getting
access
to
your
online
data?
So
there
are
three
different
ways:
one
is
knowledge
base.
One
is
position
based
and
then
inheritance
base.
The
first
is
knowledge
base.
That
means
you
know
your
password.
So
that
is
why
you
are
who
you
claim
to
be,
or
maybe
you
are
able
to
produce
a
otp,
or
maybe
you
are
using
a
hybrid
model
among
these
two.
You
are
providing
a
password
as
well
as
your
otp.
B
Second,
one
is
your
position.
That
means
you
have
you
purchase
a
smart
card,
so
that
is
why
you
are
what
you
are
claiming
to
be
or
third
one
is
so
because
this
knowledge
and
knowledge,
you
know
your
password
can
be
stolen.
Your
otp
can
be
stolen.
Your
position,
can
you
know
your
smart
card
could
be
stolen,
but
the
third
one
is
inheritance
basis.
So
that
means
something
which
is
god
given.
So
your
inheritance
is
your
biometrics,
so
this
that
is
why
biometrics
is
considered
safer
than
any
other
previous
technologies.
B
B
A
B
Yeah
so
first
we
use
a
scanner
to
scan
the
user's
biometrics,
such
as
face
finger,
iris,
retina,
palm
brain,
etc.
Then
we
extract
some
unique
features
out
of
that
biometrics
that
image
and
map
them
and
save
them
as
biometric
templates.
So
biometric
template
looks
like
this
0
1
0
1
like
that,
so
it's
binary
and
we
save
it
to
our
template
database.
B
This
part
is
similar
to
registration,
where
we
can
create
a
unique
user
rate
and
password
so
at
a
later
date
the
user
can
log
in
using
the
same
biometric
and
the
system
matches
it
against
the
biometric
database.
It
has
so
this
matching
is
little
different
from
matching
user
rate
and
password,
so
this
biometry,
actually
the
matching
would
come
up
with
a
score
like
what
is
the
probability
of
matching?
What
is
I
mean?
Is
it
ninety
percent?
Is
it
fifty
percent?
Is
it
forty
percent?
B
So,
on
the
basis
of
some
threshold
value
you
can
you
can
finalize
whether
the
my
matrix
is
matching
so
again,
wherever
there
is
biometrics,
there
is
photing.
So
swiffing
is
a
method
of
fooling
the
biometrics
identity
system,
where
an
artificial
object
like
the
fingerprint
mold
can
be
used
fingerprint
mode.
I
don't
know
how
many
of
you
have
heard
of
it.
You
can
also
create
a
fingerprint
mold
out
of
silicon
and
you
can
present
it
to
the
scanner.
B
So
how
would
you
make
sure
that
somebody
is
not
using
a
3d
mouse
or
a
photo
or
a
video
or
others
like
makeup
or
surgery?
So
there
is
a
sensor
associated
with
the
with
the
camera,
or
maybe
there
is
a
challenge
which
is
which
is
asked.
Somebody
is
asking
you
to
do
like
the
app
can
ask
you
to
smile,
or
you
know,
change
your
facial
expression
from
happiness
to
sadness
and
do
some
head
movements.
B
So
this
is
called
active,
likeness
detection
test
so
which
you
have
to
do
the
the
mobile
device
has
to
do
then.
Also,
there
is
passive,
liveness
detection
test.
Where
you
know
there
is
algorithm
ml
based
algorithm,
which
you
check,
that
it
is
a
real
im,
a
person
and
not
a
3d
mask
or
a
video
or
something
so
so
there
are
different
anti-swoofing
technologies,
so
ssi,
along
with
biometrics,
have
been
have
become
very
popular
nowadays
and
there
are
companies
like
q
ledger,
which
is
a
credit
union
in
us.
B
They
are
using
this
kind
of
combination,
but
actually
it
is
not
decentralized
biometrics.
They
are
using
biometrics
for
on-device
authentication,
which
is
fido
based,
and
then
they
are
using
ssi
for
data
sharing,
and
then
there
is
gemalto
and
group.
They
are
also
doing
a
very
similar
model
for
their
banking
clients.
So
here
in
queue
ledger
you
can
see
once
the
user
is
logged
into
the
credit
union,
then
all
the
banks
which
are
associated
with
the
credit
union.
They
can
also
give
access
to
the
user,
so
it
works
on
sso
model.
B
B
So
in
r30,
first,
the
user
captures
the
biometrics
after
active,
likeness
detection,
check
and
converts
it
to
a
template.
Then
the
user
sends
the
data,
the
personal
data.
That
means
it's
and
the
biometric
template,
so
it
could
be
like
your
name,
your
data
birth,
all
these
things,
along
with
your
biometric
template
to
a
issuer
organization.
B
Now
the
issue
organization
can
optionally
do
a
background,
verification
or
deduplication.
If
there
is
a
need
of
deep
duplication
or
there
is
a
need
to
save
the
template
like
something
like
a
national
identity
program,
then
they
can
do
it
in
a
centralized
biometric
template
database,
which
is
not
a
mandate.
So
you
can
completely
ignore
this
step
and
then
the
issuer
would
convert
that
data
to
a
hash
and
signing
it
with
a
the
issuer's
own
private
key.
The
issuer
can
write
it
to
a
public
blockchain.
B
So
on
a
later
point
of
time,
if
the
user
wants
to
log
in
the
user
can
log
in
again
with
live
by
sorry
biometrics,
which
should
again
undergo
liveness
detection
test,
and
then
the
user
can
send
all
these
data
the
data,
the
personal
data,
as
well
as
the
live
biometric
template
and
the
issuer
details
that
who
are
the
who
is
the
issuer?
Who
has
certified
this
so
now
here
the
verifier
could
be
the
same
operation
or
a
different
organization.
B
So
now
this
model
would
for
please
note
that
this
model
would
work
on
the
fly.
So
that
means
that
you-
because
there
is
no
centralized
database
over
here,
so
any
organization
can
come
and
check
if
they
trust
the
issue
organization,
then
they
would
trust
the
user
and
they
can
get
access.
They
can
give
access
to
the
user
to
their
ecosystem.
B
So
the
issue
is
validated
and
the
vc
is
validated,
and
the
user
is
also
validated
that
whether
the
same
certification
has
been
allocated
to
the
user,
who
is
carrying
the
same
public
key
as
they
are
sending
a
token
also
here
and
if
all
goes
fine,
then
the
user
is
authenticated
so
yeah.
So
this
is
the
model
that
actually
most
of
the
work
is
done
for
face
as
of
now
where
we
are
also
trying
with
the
finger
and
maybe
in
future,
we'll
be
coming
up
with
more.
B
A
So
johnny
jim
here
I
just
want
to
thank
you.
That
was
an
awesome
presentation.
I
apologize
for
not
having
scheduled
you
for
an
eight
hour
session
and
only
one
because
obviously
the
material
you
covered
was
a
tremendous
amount
of
material
in
a
short
amount
of
time
on
a
lot
of
different
topics
related
to
ssi,
but
you
did
a
great
job
between
covering
the
sort
of
the
basic
concepts
of
ssi,
as
well
as
some
of
the
applications
and
where
it's
headed,
so
that
was
really
awesome.
A
C
C
C
C
A
Yeah
jen.
That's
a
great
point,
though,
about
the
trust,
overrip
organization,
and
it's
not
just
trust
rip.
I
know,
there's
other
I'll
call
it
identity,
organizat,
other
organizations
focus
on
identity,
ietf,
w3c,
dif,
there's
so
many
of
them,
but
trust
over
ip.
I
think
is
the
one
that
fundamentally
to
me
and
correct
me
if
I'm
wrong,
but
I
look
at
it
as
the
organization
first
focused
on
what
I
call
connectivity
and
usage
of
identity
models
more
than
anything
else.
A
You
know
I
mean
they're
not
focused
on
what
I
call
data
storage
as
much
as
they
are
on
coming
up
with
real
world
use
cases
for
using
identities
and
credentials
in
practice,
and
that's
a
big
deal
I'll
just
throw
out
two
things.
I
one
one
thing
that
was
touched
on
in
the
presentation
of
scale
and
having
led
a
an
ssi
project
that
was
successful
for
a
state
in
u.s
that
wants
to
go
unnamed.
A
At
this
point,
we
did
a
pilot
that
worked
out
well
sort
of
met,
all
the
objectives
and
sort
of
set
the
stage
for
going
to
the
next
level
of
a
quota
production
pilot
so
and
we
did
use
india
aries.
All
that
worked
fine,
but
looking
forward
with
there
are
many
challenges
in
getting
this
implemented.
Well,
one
of
the
questions
that
was
raised.
What
about
blockchains
you
know
comparing
or
communicating
between
blockchains.
A
If
you
look
at
the
models
that
are
being
used
in
the
areas
and
and
the
other
frameworks,
the
key
for
interoperability
is
really
just
common
protocols
and
common
agents.
If
you
will
and
common
message
architecture
and
that's
it
those
three
things
where
you
store
it
and
what
your
resources
behind
that
aren't
really
critical
for
sure.
But
those
three
things:
the
protocol,
the
agents
and
the
message
formats
do
matter
and
india
certainly
has
done
a
lot
of
work
in
that
regard.
A
A
The
thing
I
looked
at
my
project
was
successful
because
we
went
to
I'll
call
it
the
concept
of
I'll
quote:
five
million
potential
identities
and
our
we
could
have
handled.
We
can
handle
that
scale.
What
I
couldn't
have
handled
in
the
way
we
implemented
our
project
was
a
scale
of
greater
than
5
million
identities,
and
it's
more
than
just
the
speed
of
storage
on
hashgraph
and
finality
stuff.
But
you
look
at
the
in
an
ssi
model.
You
have
forgetting
the
identities
of
people.
A
As
deb
johnny
said
you
have
devices,
and
you
have
you
know
you
can
add
animals
into
that.
But
really
devices
are
much
larger
in
terms
of
the
identity
space
but
then
ultimately
credentials
credentials
aren't
just
that.
I
graduated
from
the
university
credentials
could
be
that
jim
said.
I
can,
you
know,
go
into
his
house
on
saturday
afternoon
to
borrow
the
lawnmower
that
could
be
a
credential,
so
anything
could
become
a
credential
and
in
that
world
scale
becomes
a
super
challenge.
So
any
thoughts,
deb
johnny
on
scale,
going
forward.
A
Thoughts
on
how
to
scale
I'm
not.
I
I'm
not
concerned
about
what
I
call
the
graph
storage
model
for
blockchain.
You
know
which
hashgraph
does
different
than
the
merkle
tree
model,
that
fabric
uses-
or
you
know
other
blockchains,
that's
more
of
an
internal
implementation
and
I'm
not
so
concerned
of
that.
I'm
just
looking
in
the
real
world-
and
you
pointed
out
the
real
world
I'll
blame
you,
because
you
used
the
term
real
world.
A
In
reality,
when
you
start
looking
at
I'll
call
it
authorization
to
anything
like
I
said,
if
I'm
going
to
go
to
jim's
house
to
borrow
his
lawnmower
on
a
saturday
afternoon,
he
could
issue
me
a
credential
that
I
could
get
into
his
house
on
an
afternoon.
That
could
be
actually
a
credential
so
credentials,
although
it
could
be
in
a
sense
much
much
higher
in
concept
in
the
way
they're
traditionally
shown
and
that's
a
represents.
B
Yeah
yeah
sure,
actually
we
are
doing.
I
mean
we
have
just
started
doing
load
testing
at
the
moment,
and
I
believe
that
is
the
area
that
I'm
not
sure
I
mean
you
can
update
me
whether
indian
aries
have
come
up
with
any
figures
like
what
kind
of
what
kind
of
scalability
they
have.
What
kind
of
do
they
have
any
figures
at
the
moment,
I'm
not
very
sure,
but
we
are.
A
C
A
What
is
more,
critical
is,
in
a
sense,
the
network
capacity.
If
you
will-
and
I
don't
just
mean
bandwidth
but
more
than
that-
in
a
sense,
you
know
what
are
the
devices
hooked
that
are
the
running
the
agents?
What
what
is
the
capability
for
the
protocol?
What's
the
network?
What
are
the
nodes
I'm
going
through
where's,
the
congestion?
All
of
those
things
are
far
more
critical,
where
I
can
just
expand
on
the
back
end
capacity
as
I
needed
for
storage,
that's
usually
for
and
also
in
a
sense
make
that
asynchronous
as
well.
A
So
there's
a
lot
of
easy
things
on
the
back
end
to
handle
capacity,
but
on
the
network
side,
when
you're
trying
to
do
things,
you
have
to
decide.
Is
this
a
real-time
message
that
needs
to
be
dealt
with,
or
is
this
something
that
can
be
asynchronous
from
a
response
perspective?
And
so
you
do
have
different
types
of
message:
traffic,
but
it's
that
network
congestion
capacity
and
priority
for
messages
that
really
are
going
to
be
the
hub.
A
I
think
of
where
performance
is
going
to
come
into
this
and
scale,
and
my
project
just
like
yours,
I
didn't
have
any
problem
using
india
areas
to
scale
for
everything
that
we
looked
at.
My
problem
is
that
again
I
was
looking
at
a
state
where
we
might
issue
roughly
in
the
near
term
five
million
identities.
A
We
would
have
many
more
credentials,
but
the
india
aries
the
aries
wallet
easily
handled
that
that
wasn't
the
problem
at
all,
for
what
we
did
the
the
challenges
going
forward.
Where
I
see
this
thing
exponentially
increasing
from
a
load
perspective,
I
don't
see
this
gradually
increasing.
I
think
the
concept
that
the
strength
of
what
I
call
the
identity
and
the
credentialing
for
what
it's
worth
and
the
security
around
that
is
so
much
stronger
than
the
other
alternatives
that,
once
you
in
a
sense,
have
the
technology.
A
It's
kind
of
like
the
internet.
You'd
expect
it
to
explode
in
terms
of
its
usage,
and
I
think,
there's
a
challenge
there
and
the
only
other
thing
I'll
throw
out
that
I
saw
in
my
project
when
we
looked
at
moving
to
a
full
production
thing.
Is
it's
easy
to
have
these
digital
wallets?
If
you
will,
the
problem
is
managing
in
a
sense.
The
wallets
logically
means
that
you
have
to
have
them
recoverable.
A
So
if
I
steal
your
phone,
you
know
how
many
minutes
are
we
going
to
allow
before
you
can,
in
a
sense,
re-establish
your
identity
to
the
network,
digitally
if
I
have
things
like
key
rotation
that
have
to
happen
as
part
of
security,
how
am
I
going
to
manage
automatically
things
like
queries
with
key
rotation,
so
there's
a
whole
bunch
of
issues
that
pop
up?
That
are
what
I
look
like
to
me
anyway,
in
progress
on
solutions,
but
there
are
there's
a
lot
of
technology
behind
it,
as
you
pointed
out
in
the
presentation
for
sure.
B
B
You
know,
and
if
you,
your
mobile
phone,
is
stolen
or
broken
like
I
said,
then
how
would
you
create
a
replication
set
somewhere
in
the
on
the
cloud
perhaps
and
or
maybe
ipfs,
and
how
we
can
do
that
and
how
quickly
you
can
do
that,
and
also
because
we
are
using
blockchain.
Then
what
is
the
time?
Because
you
are
writing,
let's
say
the
issuer
is
writing
to
the
blockchain
or
issuing
the
vc
to
the
blockchain,
and
you
are
reading
so
in
in
none
of
the
blockchain.
You
can
do
it
immediately.
B
There
would
be
some
time
lag,
so
you
have
to
frame
your
use
case
as
per
that
like
in
hashgraph.
It
is
a
three
second
time
lag.
One
node
is
writing
it
and
the
another
node
is
trying
to
read
it.
So
there
is
a
time
lag
of
three
to
five
seconds,
so
you
have,
to
you
know,
develop
your
use
case
in
such
a
way
that
this
kind
of
this
kind
of
lagging
can
also
be
taken
care
of.
So
there.
A
Yeah
good
point,
I
think,
but
again
I'm
never
worried
ever
as
an
engineer.
I
never
worry
about
the
storage
models
ever
because
I
know
I
can
engineer
around
those
every
time
for
a
use
case.
The
challenge
is
always
more
the
messaging
side
of
it
on
the
networking
piece
and
the
priority
of
the
messages.
So
again,
like
an
example,
I
want
you
to
prove
me
for-
or
I
want
jim
to
approve
me
for
access
to
his
house
on
a
saturday
afternoon.
A
That
is
not
a
message
that
needs
to
be
answered
in
the
next
30
minutes.
You
know
it's
saturday
is
the
point
you
know.
Maybe
I
want
to
know
from
my
calendar,
but
it's
not
a
critical
message,
but
there
are
critical
messages.
I
worked
on
moby,
which
is
the
mobility
open,
blockchain
initiative,
where
we're
looking
at
vehicles
and
trying
to
do
in
a
sense
where
does
blockchain
fit
in
managing
real-time
traffic
issues,
and
things
like
that,
like
somebody
crossing
the
street,
if
I'm
going
to
have
an
automated
driving
scenario,
how
do
I?
A
How
do
I
recognize
that
person
and
not
hit
them
in
a
crosswalk?
There's
a
lot
on
the
vehicle
technology
side,
but
then
you
say:
okay,
we're
going
to
add
blockchain
into
that.
Looking
at
those
what
I
call
more
critical
time
things
in
terms
of
response
again:
it's
not
the
storage
side,
it's
the
messaging
side
and
the
priority
of
the
messages
and
handling
them
that
really
differentiates
everything
over
there.
A
The
other
thing
that
you
brought
up
well
in
your
model,
you
showed
the
triangular
trust
right
from
the
issuer,
the
holder
and
the
verifier
and
one-
and
this
is
going
actually
more
to
trust
over
ip
and
their
their
work.
I
think,
but
one
of
the
questions
that
does
come
up.
If
you
you
presented
all
of
the
what
I
call
the
major
hacks
that
it
occurred
right
in
traditional
stuff.
A
You
know
for
centralized
identities,
ebay
and
equifax
and
all
of
those
target
and
everybody
else
of
which
there's
quite
a
few,
and
obviously
we
have
major
problems
there.
But
if
you
look
at
an
automated
trust
environment
with
ssi
on
the
bottom
side
of
it,
where
trust
or
ip
defines
it,
you
really
have
a
governance
question
right
and
that's
actually
a
bigger
issue.
I
think
I'll
say
even
bigger
than
regulations
like
gdpr
is
the
governance
model?
It's
who
do
you
trust
you
know.
Do
you
trust
facebook
to
hold
your
identities?
A
Do
you
trust
microsoft
to
be
the
owner
of
your
identity
system,
which
you
do
today?
Certainly
if
you
have
a
microsoft
account
or
an
apple
account,
but
going
forward.
Is
that
the
right,
in
a
sense
holder
of
your
identity?
I'm
not
sure
if
that's
the
case,
the
the
answer-
and
I
do
think
at
least
trust
overrp
is
trying
to
attack.
That
is
the
governance
model.
C
A
Yeah-
and
this
is
a
great
point-
and
I
really
think
I
really
think
yeah
I'll-
give
gdpr
credit
and
eu
a
european
commission
for
the
work
they've
done
on
I'll
call
it
blockchain
regulations
and
so
on
and
digital
assets
and
all
that
stuff,
but
separately,
I
do
think
the
concept
of
getting
governance
right
is
has
not
been
well
addressed,
and
I
do
think
that
is
a
little
bit.
I
know
I'll
say
trust
over
ip
at
least
seems
to
be
leading
in
that
area
period
to
define
that
governance
is
a
bigger
thing.
A
Who
do
you
really
trust
as
organizations?
It's
not
me
jim,
the
holder
who
claims
I
graduated
cornell,
it's
more
importantly.
How
do
you
know
that's
really
cornell
and
how
do
you?
How
well
do
you
trust
cornell,
to
be
somebody
that
verifies
that
jim?
Are
they
a
good
organization
to
trust,
to
say
that
jim
is
really
you
know
whatever
strong
in
child?
Psychology
is
an
example.
If
that's,
what
my
degree
is
in,
you
know
what
I
mean
so
the
the
whole
trust
model
related
to
governance.
A
A
If
I
had
to
give
myself
a
title,
I'll
call
myself
the
chief
doctor
of
failure
on
planet
earth
every
time
I
go
into
these
groups,
whether
it
be
moby
or
somebody
else,
I'm
always
looking
at
failure,
combinations
and
I'm
not
seeing
what
I
call
the
requirements
for
failure
driven
hard
enough
into
a
lot
of
these
solutions.
So
when
I
was
looking
at
the
ssi
model
and
we
were
trying
to
figure
out
well
for
a
production
solution
in
the
state,
what
do
we
really
want
to
say?
A
How
long
should
your
recovery
from
losing
your
digital
id
take
it
should
it
be?
You
know,
days
weeks
minutes
where
should
it
be,
and
it's
like?
Well,
if
your
digital
id
is
your
passport
to
everything
and
you're,
whatever
a
diabetic
and
you
need
insulin,
you
got
a
prescription
at
the
drug
store
and
that
your
digital
id
is
key
to
get
it.
How
long
am
I
going
to
make
you
wait
to
recover
something
like
that?
So
I
think
setting
use
cases
for
this
stuff
on
the
top
end
is
really
important
and
again
I'll,
say.
C
No
actually,
I
agree
100
and
I
appreciate
the
advertisement.
I
think
it
was
a
great
summary
and
especially
the
emphasis
on
on
the
governance
side
being
a
huge
part
of
contributing
to
moving
the
trust
model
forward,
so
whether
it's
earth
id
or
indie,
aries
or
microsoft,
ion
whatever
just
just
being
able
to
enable
or
or
sovereign
foundation
for
their
work,
just
enabling
the
principles
of
ssi,
built
on
on
the
trust,
framework
and
governance.
B
One
of
the
questions
my
client
had
that,
let's
say
there
is
a
ssi
chain
in
most
of
the
projects
I
have
worked
in
ssi.
There
is
a
chain
that
means
there
is
a
first
issue.
Then
there
is
a
second
here.
Then
that
is
the
third
issue.
Now
the
first
issuer
is
having
the
bearing
the
maximum
responsibility.
The
second
issuer
is
actually
first
the
verifier
and
then
they're
they're
issuing
the
second
set
of
certificate,
and
third
one
is
relying
on
the
second.
B
So
here
let's
say
there
is
some
issue
in
with
the
first
issue,
maybe
by
some
means
the
user.
Can
you
know
trick?
The
first
issuer
to
you
know,
issue
the
certificate
so
now
the
second
and
third
are
actually
relying
on
the
first
issues.
I
mean
in
a
direct
or
indirect
way.
So
now,
at
a
point
of
time,
the
first
issue
realizes
that
the
user
actually
has
tricked
them
trick
them.
So
they
revoke
it,
but
even
if
it
is
revoked,
because
this
is
a
decentralized
ecosystem.
C
A
B
A
Second
visitor,
so
you
know
maybe
I'm
an
employer
and
I
hire
you
jim
because
they
say
oh
you're,
a
harvard
graduate,
I'm
relying
on
your
harvard
credential
and
now
I'm
giving
you
a
formal
credential
from
that,
and
her
idea
was
that
yes,
there's
a
chain
of
quote
issuers
who
are
relying
on
prior
issuers
integrity.
If
you
will,
you
know
for
what
they
were
issued
and
there's
a
risk
there.
That's
all
and-
and
her
point
is
that
rarification
as
well.
C
You
describe
so
well
jim
rules
around
revocation
and
then
and
then
how
secondary
and
tertiary
implications
for
attributes
so
to
to
your
model.
I'm
I'm
an
employee
with
my
employer
and
one
of
the
key
aspects
of
being
an
employee
is
I
have
this
harvard
degree,
but
but
that
credential
has
some
sort
of
of
relationship
with
that
harvard
credential
such
that,
if
it's,
if
it's
revoked,
that
revocation
creates
some
sort
of
of
need
for
revisit
or
or
reauthorization
for
the
employee
credentials.
Example.
A
Yeah,
so
in
our
world
in
the
aries
world
that
we
implemented
at
the
state,
we
were
doing
I'll
call
it
real-time
verification,
checking
and
what
I
realized
is
like
message:
priorities
for
alcoholic
content.
You
really
need
to
prioritize
that
you
can't
just
say
it's
unlimited.
So
in
our
world,
it
all
worked
because
we
were
we
weren't
upward,
a
massive
thing
taking
planet
earth.
We
had
a
smaller
population,
but
the
revocation
stuff
clearly
has
challenges,
and
I
think
you
wind
up
with
the
idea
that
some
revocations
need
to
be
real
time.
A
You
know
the
example
would
be
my
driver's
license
if
I'm
a
drunk
driver-
and
you
know
I'm
arrested-
maybe
my
driver's
license
is
suspended
immediately
and
that
credential
should
be
immediately
quoted,
verified
and
checked
if
it's
a
driver's
license.
On
the
other
hand,
if
it's
you
know
whatever
some
other
kind
of
a
thing,
a
credential
for
some
other
thing,
that's
less
critical,
then
maybe
that
credential
would
have
been
uploaded
more
of
an
expiration
period
as
opposed
to
a
real-time
revocation
check,
if
that
makes
sense
to
try
to
reduce.
C
A
Yep
yeah
great
excellent,
so
deb
johnny
any
other
critical
things.
I
know
it
were
way
over
time.
I
apologize
to
the
whole
audience
here
for
having
yeah
I'm
blaming
deb
johnny
for
actually
picking
a
really
great
topic
that
she
knows
a
lot
about
and
sharing
a
lot
of
information
that
leads
to
a
lot
of
interest.
So
it's
all
your
fault,
not
my
fault
that
we're
over
time,
but
any
other
critical
thought
step.
Johnny.
B
Well,
I
think
I'll
come
up
with
more,
maybe
in
a
couple
of
months
time,
like
I'm
saying
that
we
are
doing
a
lot
of
load
testing
as
well
as
this
governance.
Stuff
is
also
there
so
and
interoperability.
Of
course,
you
know,
because
in
in
future
we
also
have
the
plan
of
having
some
other
blockchain,
not
only
this
one,
something
else
so
that
no,
maybe
there
is
scope
of
improvement.
So,
let's
see,
and
maybe
I'll
come
up
with
something
pretty
soon
again.
A
Great
all
right,
so
I'm
gonna
thank
everybody
who
was
here
today.
I
really
appreciate
you,
everybody
staying
out
and
the
great
comments,
jim
and
everybody
else,
and
certainly
deb
johnny.
You
know
your
expertise
is
really
really
up
there
in
this
space,
and
certainly
you
are
a
great
resource
for
all
of
us.
So
I
look
forward
to
seeing
more
of
your
work
and
and
being
able
to
access
more
of
your
content.
With
that
said,
I'm
going
to
push
our
recording
up.
We
did
live
stream.
A
A
Great
thanks
any
final
comments
from
anyone
before
I
close
the
meeting
great
all
right.
Well,
thank
you.
Everybody.
It's
been
a
great
session
again
deb
johnny,
can't
thank
you
enough
and
jim.
You
know
certainly
appreciate
your
expertise
today
as
well,
and
thank
you
all
for
attending
and
have
a
good
week.
Thank
you.