►
From YouTube: Global Identity Solution Leveraging Blockchain
Description
A recording of a virtual meetup hosted by Hyperledger Hyderabad with Debajani Mohanty, author of “Blockchain for Self-Sovereign Digital Identity”. 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.
More about the event is at: https://www.meetup.com/Hyperledger-Hyderabad/events/275929453/
----
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 #HyperledgerMeetups #Blockchain
A
B
A
B
B
A
A
B
Today
we
would
cover
the
issues
in
global
identity
and
I
don't
think
that
I
need
to
do
an
introduction
to
blockchain,
because
all
of
you
are
well,
you
know,
educated
in
blockchain.
So
that's
that's
fine,
I
I'll
probably
I'll
introduce
ssi
or
self-sovereign
identity
and
a
little
bit
on
biometric
and
finally,
we
would
explore
some
global
initiatives
in
identity
and
certain
use
cases.
So
a
brief
introduction
regarding
myself,
I'm
the
johnny
mohanty
doctor
30
blockchain
influencers
from
india
is
quoted
by
singapore.
Fintech
news.
B
B
So
today's
session
is
about
digital
identity.
So,
let's
start
with
the
issue
and
the
need
of
a
global
identity
for
every
human
and
every
machine
in
the
world.
Probably
I
mean
we
are
starting
with
every
human,
but
in
future
it
would
be
also
machines,
because
every
person
in
the
modern
world
might
have
more
than
one
machines
or
devices
along
with
them
smart
devices,
and
they
also
need
to
have
their
identity,
and
they
also
need
to
you
know,
share
information
with
each
other
with
at
most
security
and
privacy.
B
So
these
people
are
called
the
invisible
people
who
are
mostly
women
and
children
from
parts
of
asia,
africa
and
latin
america,
and
officially
they
do
not
exist.
They
lead
their
daily
lives
without
any
proof
of
identity.
So
this
concludes
that
13
of
the
global
population
do
not
have
any
identification
document.
B
B
You
can
see
in
the
left
image
that
there
are
3.4
million,
who
have
some
sort
of
identity,
but
they
are,
I
mean
their
uses
is
limited
and
they
are
not
able
to
use
it
in
appropriate
appropriately
in
the
digital
world,
and
then
there
are
3.2
billion
who
have
legally
recognized
identity
and
they
participate
in
the
digital
economy,
but
they
do
not
have
the
capability
to
use
it
effectively
and
efficiently
online.
So
please
note
I'm
saying
online.
B
B
B
If
you
talk
about
all
the
identity
projects,
then
maybe
aadhar
is
the
biggest
one,
but
in
couple
of
years,
in
ten
years
time,
you'll
find
that
perhaps
id
4d
would
be
the
biggest
project
on
identity
in
the
world,
because
every
person
would
have
their
identity.
So
so,
let's
now
get
introduced
to
digital
identity.
So
I
believe
that
all
of
you
deal
with
digital
identity
in
some
way
or
the
other.
So
digital
identity
is
about
personal
data
that
identifies
you
online.
B
B
B
So
so?
Basically,
the
first
one
is
centralized,
centralized
server
and
the
second
one
is
weak
password.
So
and
obviously
there
are
other
issues
also
like
phishing
attack
and
sharing
the
data
users.
Data
without
permission
like
I
am
providing
my
data
to
organization-
I'm
you
know,
I'm
the
user
in
and
they
are
sharing
the
data
without
my
permission,
so
that
can
always
happen
with
the
current
model
and
then
also
unintentional
sharing.
B
That's
a
close
group,
but
they
are
sharing
with
somebody
else,
and
people
are
able
to
know
that
what
is
your
databar
and
then,
if
they
know
that
how
old
you
are,
then
they
would
come
to
know
that
what
is
your
exact
date
of
birth
and
that
that
data
birth
is
a
private
information
using
which
you
know
it
is
also
possible
that
people
can
get.
You
know
access
to
your.
You
know
banking
website
so
and
also
there
is
one
issue
called
identity
correlation.
B
So
what
it
means
is,
let's
say
that
you
are
using
some
kind
of
user
id,
which
is
because
there
are
so
many
apps
you
might
be
using.
Then
people
have
got
the
habit
of
using
the
same
user
id
again
and
again,
and
I
mean
many
people
use
their
mobile
number
as
their
user
id
many
people
use
their
prime
email
id
as
their
user
id.
B
So
let's
say
that
I'm
sharing
my
email
id
as
my
user
id
with
my
bank
and
also
with
my
with
my
hospital
and
with
my
employer,
my
employer
or
with
my
university,
where
I
study
so
everywhere.
My
same
email
id
goes
as
a
user
id.
Then
it
is
also
possible
that
people
can
know
that
if
they,
you
know,
shake
their
hands.
If
these
organizations
want
to
deal
with
you
just
all
data,
then
they
can.
B
B
That
means
that
how
we
are
managing
our
digital
identity
and
over
the
so
many
years
so
people
there
might
be
people
in
this
group
who
are
you,
know
old-timers
like
me,
who
have
been
in
the
industry
for
20
years
or
even
more
so
people
know
that
the
way
digital
identity
started.
You
know
the
way
we
handled
it.
B
The
first
model
is
called
the
centralized
identity
model,
so
here
the
user
might
log
into
different
websites
or
different
servers
and
for
each
servers
the
user
has
to
remember
a
separate
set
of
user
id
and
password.
So
you
might
be
using,
I
mean
in
the
background
you
might
be
using
the
server
might
be
using
a
database
model,
rdbms
model
or
ldap
model
or
active
battery
model,
but
everywhere
they
are
using
a
centralized
database
to
store
users,
user
id
and
password
and
all
the
users
id
and
password
are
in
one
place.
B
So
this
is
a
this
is
a
siloed
model
or
centralized
identity
model.
The
second
model
is
a
federated
identity
model,
so
this
is
very
popular
nowadays.
Many
people
use
this.
So
in
this
model
we
have
a
identity
provider
who
is
handling
your
login,
so
once
you
log
into
to
this
identity
provider,
it
actually
provides
you
with
the
token
now
you
are
sharing
this
token
with
different
third
parties
and
you
don't
have
to
log
into
them
again
and
again.
Just
like
you
know
you
are.
B
Let's
say
you
are
logging
into
google
and
you
don't
have
to
log
in
again
to
gmail
or
google
drive.
So
there
are
so
many
services
who
which
you
can
access
just
with
one
login.
So
this
is
a
federated
identity
model,
but
here
also
so
maybe
it
is
easier
for
the
user,
because
user
doesn't
have
to
remember
so
many
different
sets
of
user
written
password.
But
then
again
there
is
a
centralization
of
your
digital
identity.
So
here
the
centralized
area
is
your
identity
provider.
B
Where
you
know
this,
they
save
the
users,
all
the
users
credentials
in
one
place.
So
in
these
two
models,
I'm
not
going
to
use
a
centric
identity.
This
is
a
first
approach
for
decentralization,
but
this
is
a
failure,
so
I
would
directly
jump
to
self-sovereign
identity,
but
these
two
models
I
just
discussed
about
central,
centralized
identity
model
and
federated
identity
model.
These
two
with
these
two
models.
Mass
hacking
is
possible
because
all
the
data
is
in
one
place
and
single
point
of
failure
is
possible.
B
So
that
is
why
we
are
you
know:
learning
about
ssi
or
self-sovereign
identity,
so
self-serving
identity
is
a
new
decentralized
model
to
manage
digital
identity.
Here
we
have
an
issuer
that
issues
verified
credential
to
the
user.
That
is
set
securely
on
the
user's
mobile
device.
It
might
be
a
mobile
phone
or
it
might
be
a
tab
or
it
might
be
even
your
laptop,
but
this
has
to
be
the
user's
own
device
which
the
user
is
not
sharing
with
others.
B
At
the
same
time,
the
issuer
is
sending
a
signed
reference
hash
to
a
public
blockchain
and
the
issuer
is
signing
it
with
their
own
private
key.
So
the
issuer
is
the
organization
and
issuer
is,
is
sending
the
data
the
verified
credential
to
the
data
it
might
be.
The
user
can
store
it
as
it
is
like
the
name:
data,
birth
cost
or
tax
certificate.
You
know
address.
You
know
these.
B
B
It
needs
to
know
that
whether
the
data
is
valid
and
also
who
has
validated
this
so
now
the
verifier
can
convert
the
data
to
a
hash
and
check
that
if
the
hash
of
the
data
matches
with
that
on
the
blockchain
and
if
it
is
valid,
the
example
can
be
the
scenario
where
the
issuer
is
a
passport
office
and
the
verifier
is
a
visa
office
and
the
user
is
sharing
as
much
data
needed.
The
user
might
not
need
to
share
it.
All
like.
B
Let's
say
that
my
password
has
got
20
different
information,
but
maybe
the
verifier
doesn't
need
all
of
them,
so
I
would
just
share
because
it
is
digital.
I
have
the.
I
have
the
capacity
to
share
as
much
data
as
needed,
so
this
at
at
a
later
point
of
time.
If
that,
if
there
is
a
need,
then
the
issuer
can
revoke
the
hash
by
altering
a
small
piece
of
data,
and
the
verifier
would
know
that
the
data
is
no
longer
valid.
B
So
this
architecture
ensures
integrity,
ownership,
privacy,
security
and
validity
of
the
data.
So,
and
please
note
that
in
this
architecture
there
is
no
centralized
repository,
you
may
say
that
the
issuer
can
retain
the
data,
but
actually
or
what
we
try
is.
The
issuer
would
not
retain
any
data
with
them
and
also
you
know.
I
don't
have
that
much
time
to
explain
it
all.
B
You
can
read
my
book
where
I
have
explained
that
for
every
relationship
or
every
user
to
a
issue,
relations
say
for
the
every
user
to
a
verify,
relationship
or
different
id
is
used.
This
is
called
a
private
date,
so
there
is
a
public
date
like
which
every
every
organization
would
have
a
public
date
with
which,
with
whose
reference
they
would
sign,
with
their
private
key.
B
At
the
same
time,
that
is
a
private
date
for
every
organization
to
use
a
relationship
so
so
that
there
is
no
need
to
have
a
unique
reference
number
which
should
be
available
to
all.
No,
you
don't
need
to
share
that
unique
reference
number
of
the
user
to
all,
so
that
is
more
complex,
but
all
right,
so
so
how
the
ssi
works
in
real
life.
In
real
life
there
are
multiple
issuers
or
certifying
bodies
or
organizations.
So
here
you
can
see
in
the
top.
B
Just
I
have
I
I
try
to
do
it
in
a
chronological
order.
So
in
the
top
you
see
the
hospital,
then
there
is
a
government
and
there
is
a
there
is
a
university
and
finally
there
is
a
office.
So
let's
say
that
alice
is
born
in
the
hospital
and
the
hospital
is
issuing
the
first
set
of
certificate,
which
is
the
birth
certificate.
The
health
care
vc
is
going
to
the
user.
The
second
then
she
joins
up.
She
is
going
to
government
for
her
national
id
so
like
even
in
india.
B
The
children
can
have
that
her
id.
So
this
is
the
second
set
of
certificate.
The
third
set
of
certificate
comes
from
her
educational
organization
and
then,
finally,
when
she
is,
you
know
old
enough,
she
is
joining
organization
to
be
employed,
so
the
first
set
of
certificate
is
coming
to
the
user
from
four
different
issuers,
or
that
could
be
even
more.
B
Then
the
user
is
saving
all
this
information
to
his
mobile
device
most
secretly.
So
you
can
see
that
there
are
different
set
of
certificates,
one
coming
from
the
hospital,
then
from
the
government,
then
from
the
educational
organization,
the
in-city
and
finally,
from
the
employer
and
the
user
then
can
share
whole
of
the
data
or
part
of
the
data
or
any
kind
of
combination.
B
Two
different
verifiers
so
like
let's
say
that
alice
is
applying
for
a
loan,
so
she
needs
to
provide
a
certificate
of
her
age
and
her
national
identity,
because
she's
a
citizen
she
can
go
for
a
loan
and
what
is
her
education
level
if
that
is
a
requirement,
and
also
if
she
is
employed
and
what
is
her
salary
of
if
the
salary
is
more
than
a
particular
amount.
So
all
these
letters
he
needs
to
gather
from
different
organizations
and
share
as
much
as
needed
to
different
verifiers.
B
And
then
the
user
can
share
this
data
in
three
different
modes.
They
are
known
as
the
traditional
mode,
the
zero
knowledge
proof
and
selected
disclosure,
more
or
self-adjusted
mode.
So
in
traditional
mode
like
let's
say,
I'm
designing
and
I'm
sharing
my
name
as
it
is
the
johnny
mahanti.
So
I
have
that
capability.
B
B
B
Let's
say
that
I'm
applying
for
a
job
and
the
employer
wants
to
know
that
what
is
what
are
my
hobbies,
so
I
don't
need
any
anyone
to
certify
that
certain
information
which
doesn't
need
any
certification,
so
so
for
that
sort
of
data
that
is
called
self-adjusted
mode
of
sharing.
The
user
can
do
that
as
well,
and
there
would
be
a
publicly
available
blockchain
where
the
issuer
would
send
their
reference
classes
and
the
verifier
can
read
and
check
if
this
is
valid.
B
So
so
the
ssi
ecosystem
is
usually
pretty
complex
where
you
need
to
handle
so
many
different
different
standards.
So
because
you
know
what
I
just
showed,
you
is
basically
only
the
ssi
part,
but
we
are
discussing
about
digital
identity
and
that
to
online,
so
how
this
entire
ecosystem
would
fit
in
a
way
world
or
you
know,
on
internet.
How
can
we
make
this
safe
enough?
So
and
of
course,
we
are
not
doing
it
with
the
centralized
any
kind
of
database
or
centralized
model.
So
let's
look
into
that.
B
So
obviously
there
are
so
many
different
standards
that
we
need
to
look
into.
We
have
to
see
to
the
web
standards
and
then
how
to
authenticate
authenticated
to
this
kind
of
ecosystem
that
also
we
have
to
see
what
kind
of
blockchain
we
need
to
use
that
also.
We
have
to
see
and
also
what
kind,
how
to
handle
this
decentralized
identity
network,
so
the
deed
creation
and
the
deactivation
how
all
these
things
can
be
looked
into.
So
basically
in
ssi
there
are
different
layers.
B
There
is
a
public
ledger
and
or
a
dlt
or
a
blockchain.
Then
there
is
a
private
identity
storage
like
for
each
device
and
each
individual
or
each
organization.
There
should
be
identity,
storage.
We
have
to
handle
that
and
also
we
need
to
have
a
agent
or
hub
layer
which
is
responsible
for
the
message:
communication
between
different
kind
of
users
and
also
there
are
client
devices
we
need
to
handle.
I
was
just
talking
about
the
this
device
part
also
so
so
this
is
the
system
architecture,
so
in
self-serving.
B
B
B
Bob
is
actually
keeping
a
separate
copy
on
the
cloud
so
he's
having
his
data
on
his
mobile
device
and
also
in
a
cloud
storage
so
that
if
the
mobile
is
lost
or
if
the
mobile
is
stolen,
broken
whatever
it
is,
he
can
get
it
sorted
with
another
mobile
in
no
time,
but
please
note
that
when
it
comes
to
biometrics,
I
will
come
to
the
biometric
part
a
little
later.
So
when
it
comes
to
the
biometrics,
then
all
the
data
is
on
the
mobile
device
itself.
B
B
Thank
you,
and
also
there
is
a
public
dlt
where
all
the
decentralized
identities
of
the
organizations
are
created
and
all
the
reference
has
against
all
the
claims
are
going
and
also
there
is
a
revocation
registry
mechanism.
How
do
you
revoke?
I
was
just
telling
about
how
to
revoke
a
verified
credential
if
there
is
a
need,
so
this
is
handled
by
the
public
dlt
all
right
now,
let's
discuss
some
of
the
use
cases,
so
the
first
one
is
the
next
gen
authentication
and
authorization
architecture.
B
So
please
note
that
there
could
be
many
different
use
cases
across
many
different
verticals,
but
mostly
how
ssi
is
used
are
in
two
you
know
biggest
areas.
One
is
the
authentication
authorization
area,
the
other
one
is
verified,
credential
area.
So
now,
first,
let's
talk
about
the
you
know,
authentication
and
authorization
architecture,
so
how
this
can
be
handled,
let's
see
so
to
discuss
this
first.
B
Let's
think
that
how
what
is
the
best
option?
You
know
to
prove
yourself
online,
how
another
personal
data
for
digital
identity
can
be
proved
like.
Let's
say
I
want
to
prove
online
that
I
am
the
journey.
So
how
do
you
know
that?
I
am
the
journey
mohanty,
maybe
because
I
switched
on
my
video
and
you,
you
saw
my
picture
before
and
you
can
relate
to
that,
and
you
know
that
I
am
the
same
person.
So
basically,
there
are
three
different
ways
to
prove
it.
One
is
knowledge.
The
second
one
is
position.
B
The
third
one
is
biometrics,
so
how
you
knew
that
I'm
the
journey
is
through
my
metric,
even
if
you
know
I
joined
as
the
johnny
monty,
but
anybody
can
join
us
literally.
So
you,
you
saw
my
picture
on
my
video
and
you
knew
on
the
journey.
So
the
first
model
is
is
knowledge.
That
means
you
know
some
kind
of
password
using
a
username
and
password,
which
is
in
your
knowledge,
and
you
are
logging
in
to
a
system.
B
The
second
one
is
sorry
in
this.
In
the
knowledge
section
itself,
the
second
model
is
otp.
That
means
you
are
sent
a
one-time
password
to
your
mobile
device
and
you
are
using
that
otp.
There
are
time
bound
otps.
Also,
most
of
you
might
have
used
it
and
then
you
are
getting
access
to
some
kind
of
services
and
then
nowadays
people
are
also
going
for
mfa
or
multi-factor
authentication.
B
Where
there
is
a
hybrid
model,
you
are
providing
a
unknown
password
and
also
there
is
a
otp
that
is
sent
to
you
and
using
both
of
them.
You
are
logging
in,
but
please
note
that
the
password
can
be
hacked.
There
are
so
many
different
processes.
I
don't
need
to
tell
you
so
many
different
processes
made
may
be
fishing
or
maybe
you
know
man
in
the
middle
there's.
So
many
different
ways
of
you
know:
gathering
somebody's
password
and
also
the
otps.
B
If
your
mobile
is
stolen,
somebody
can
get
access
to
your
otvs
also,
so
the
knowledge
factor
can
be
bypassed.
The
second
one
is
position
so
smart
cards,
you
know,
if
you
have
your
smart
card,
you
just
put
you
know
you
just
showcase
it
somewhere
to
get
access
to
your
services.
Like
you
know,
let's
say
that
you
have
your,
it
might
not
be.
It
might
not
be
possible
before
to
do
online,
but
nowadays
I'll
come
to
that.
Also.
B
So
in
smart
card
you
use
your
smart
card
for
getting
access
to
your
card
or
maybe
your
atm
cards.
You
know
these
are
smart
cards
used
for,
but
then
biometric
is
something
that
you
don't
need
to
know
something.
You
don't
need
to
remember
your
password
or
something
you
need
to
purchase
it.
Your
biometric
is
always
with
you.
You
don't
need
to
remember
it
right.
So
biometrics
is
one
quick
solution,
one
easy
solution
and
it
is
always
with
you.
B
B
You
know
if
you
want
to
go
for
shopping
or
something
you
can
carry
these
cards
so
no
longer,
they
would
ask
for
passwords
because
password
somebody
knows
your
password
and
if
they
steal
your
your
card,
then
they
can
use
it
so
now.
Instead,
you
know
these
cards
are
issued
and
they
are
becoming
very
popular.
B
So
there
are
many
different,
hybrid
models
which
are
coming
up
so
because
I'm
discussing
authentication
because
I'm
discussing
ssi,
so
I
must
discuss
biometrics
also
so
all
right,
so
so
all
right,
so
how
biometrics
works?
I
think
that
most
of
you
might
be
having
some
knowledge,
so
your
biometrics,
like,
I
believe
that
most
of
you
might
be
knowing
that
biometrics
are
broadly
categorized
into
two
different
types.
One
is
physiological
and
one
is
behavioral.
So
in
physiological
is
something
like
your
face.
B
Your
fingerprint,
your
iris,
retina,
your
palm
head
and
behavioral
is
something
like
your
voice.
The
way
you
work
the
way
you
sign,
so
these
are
behavioral.
So
in
both
models,
what
we
need
is
a
sensor.
So
there
is
a
sensor
and
in
front
of
which
you,
you
know
you
get
your
biometrics
gets
kind
so
and
then
then
we
exp
extract
some
unique
features
out
of
it
and
then
we
map
and
save
them
as
biometric
templates.
B
So
if
you,
if
you
are
not
aware
how
a
biometric
template
looks
like
it
looks
like
this,
so
it's
just
a
binary
data,
zero
one
zero
one
like
that,
and
then
this
biometric
template
gets
saved
to
our
template
biometric
template
database.
So
you
can
see
in
this
image
below
that
the
user
is
the
first
time
you
know
this
is
the
first
time
when
the
user
is
doing.
It
is
very
similar
to
the
registration
process
with
the
user
id
and
password.
B
The
user
is
enrolling
with
the
biometrics
and
it's
getting
converted
to
a
biometric
database.
Sorry
biometric
template
and
goes
to
a
template
database.
The
second
time
is
identification
or
it
is
very
similar
to
how
we
do
login.
So
here
you
can
do
it
again
and
again
and
again,
the
user
is
again
providing
the
same
biometrics
and
it's
again
getting
converted
to
a
biometric
template
and
there
is
a
matching.
B
So
this
is
a
one
two
and
this
is
called
a
one
to
n
matching
and
there
is
a
there
is
a
way
to
do
one
to
one
matching
also.
So
if
you
are
matching
it
with
a
centralized
database,
then
it
is
called
a
one
to
end
matching.
So
this
matching
is
not
as
perfect
as
you
do
the
password
model,
so
in
user
id
and
password
model.
B
If
because
there
are
string
comparisons,
then
it
would
always
if
you,
if
you
provide
the
right
user,
writing
password,
there
would
be
always
a
hundred
percent
match,
but
in
case
of
this
yeah
there
might
be
a
you
know:
small
differences.
So
every
time
you
do
a
biometric
login,
there
would
be
a
machine
learning
based
comparison
with
the
existing
template
db
and,
and
that
would
you
know
the
system
would
come
up
with
the
score.
B
B
But
whenever
we
talk
about
biometrics
we
must
talk
about
the
spoofing
part
as
well.
So
spoofing
is
a
method
I
believe
many
of
you
might
have
heard.
It
is
a
method
of
fooling
a
biometric
identity
system,
so
where
an
artificial
object
like
a
fingerprint
mold
made
up
of
silicon,
is
presented
to
the
scanner
which
leads
to
the
hacker
to
get
access
to
the
authorized
data
and
services
originally
made
for
the
rightful
owner.
B
So
here
you
can,
in
the
right
hand,
side
you
can
see
this
image,
so
there
are
when
the
biometric
comparison
happens.
There
are
so
many
different
stages.
So
so
we
can
broadly
define
divide
this
into
two
different
categories.
One
is
presentation,
attack
and
indirect
data.
There
are
two
different
categories
of
attack
which
can
happen
on
a
biometrics
database.
So
first
one
is
presentation
attack.
B
So
in
this
presentation
at
times
you
know
people
create
silicon
molds.
Out
of
you
know,
people
you,
you
know,
get
your
finger
print
by
some
hook
or
crook,
and
then
they
convert
it
to
a
silicon
mold
and
use
that
mold
to
you
know
log
into
the
system
impersonating
as
you
yeah,
you
know.
If
you
are
using
face,
then
they
may
use
3d
mask
or
photo
or
a
video
or
even
makeup
for
surgery.
B
So
now
most
of
the
attacks
happen
in
this
layer
presentation
attack
which
happens
in
the
sensor
area,
but
when
it
comes
to
the
inside
like
like,
when
you
are
doing
the
processing,
if
somebody
gets
access
to
your
database,
then
that
is
a
different
kind
of
attack.
That
is
the
indirect
attack
which
can
happen
in
so
many
different
stages,
but
I
would
call
it
now
if
we
are
using
ssi
I'll
come
to
that.
If
we
we
are
using
a
self-serving
identity,
then
that
can
be
also
minimized
to
a
great
extent.
B
So
there
are
many
anti-spoofing
techniques
so
to
avoid
the
presentation
attack
because
the
other
part
the
indirect
attacks
we
can
handle
through
ssi,
but
how
to
handle
this
presentation
attacks.
This
is
through
anti-smoking
techniques.
I
believe
that
many
of
you
might
have
heard
about
liveness
detection
test
where
the
system
is
actually
providing
you,
the
user,
with
a
challenge.
So
if
you're
using
your
face,
then
the
scanner
would
ask
you
to
smile
or
to
turn
your
head.
B
If
you're
using
iris,
then
it
would
ask
you
perhaps
to
blink
your
eyes
if
you're
using
a
fingerprint,
the
sensor
would
check
the
temperature
and
pressure
of
your
thumb,
and
there
is,
of
course,
matching
learning
algorithm
to
study
the
high
quality
images.
Just
I
was
just
telling
you
about
the
you
know
this
in
the
previous.
I
think
this
one
so
here
this
this
payment
cards
are
coming
off
with
biometric.
You
know
facilities.
B
So
here
all
the
comparison
everything
happens
on
the
card
itself:
it's
not
going
anywhere
and
also
this.
There
is
a
sensor
which
also
checks
the
the
fingerprint
and
it's
also
checks
the
temperature
and
the
pressure
of
your
fingerprint
to
figure
out
that,
whether
it's
a
and
the
thumb
of
a
real
human
being
or
it's
a
silicon,
mold
or
something.
So
so
all
these
things
you
have
to
craft
on
your
on
your
sensor
level.
B
Now
I'm
going
to
discuss
my
organization,
arthritis
is
next-gen
authentication
solution
with
decentralized
biometrics,
so
at
r30
we
are
blending
biometrics
and
self-sovereign
identity
for
the
next
gen
authentication
system,
so
the
so
the
user's
biometric
would
only
be
saved
on
the
device.
It
won't
be
shared
with
third
parties
again
and
again.
So,
let's
see
how
it
have
how
it
happens.
B
The
time
is
won't
allow,
but
actually
we
are
trying
to
you
know,
abide
by
the
fido
standards
so
that
you
know
the
the
biometrics
would
be
saved
on
the
mobile
device
itself.
So
the
issue
would
send
sorry
here.
First,
the
user
is
capturing
the
biometrics
after
liveness
detection
check
and
converting
this
to
our
template,
which
is
which
is
stored
on
the
mobile
device
itself.
B
Now
the
user,
along
with
its
biometrics,
it's
also
sending
some
personal
data
to
an
issuer,
so
the
biometrics
could
be
many
different
types
so
like
here
we
are
using,
you
know,
thumb
the
fingerprint
iris
face
and
and
then
we
are
also
trying
to
come
up
with
voice
gate
or
the
way
a
person
walks
and
also
palm
vein,
and
what
the
issue
is
doing.
If
there
is
a
need,
then
there
would
be
a
centralized
biometric
template
database
against
which
the
user
would
be
matched.
B
So
this
is
an
optional
part,
so
which
would
be
needed
only
if
you
are
going
for
a
national
identity
program
where
there
is
a
need
of
doing
a
one
to
n
comparison.
So
otherwise,
you
know
this
part
is
not
needed,
so
the
issuer
would
send
a
reference
hash
to
the
blockchain.
So
this
reference,
as
is
only
for
the
personal
data
not
for
the
biometric
template
and
then
issued,
confirms
the
certification
to
the
user.
B
Now
the
user
is
trying
to
login
to
any
third
party.
So
here
the
user
is
doing
the
login
to
the
to
to
the
device
using
the
my
metrics
every
time.
So
that
is
a
one-to-one
matching
and
the
user
is
sharing
different
kind
of
personal
data
with
the
third
parties
or
the
the
data
that
is
issued
by
the
issuer
and
also
the
issue
details
that
that
means
who
is
the
organization
who
has
certified
me
and
then
this
verifies
this
verifier
could
be
the
same
issuer
or
a
different
issue.
B
That
means
let's
say
that
the
issuer
actually
wants.
You
to
login
at
a
later
point
of
date,
because
the
issuer
is
not
saving
any
of
the
users,
personal
data,
so
how
they
should
know
that
whether
the
person
is
actually
a
legitimate
user.
So
the
use
issue
would
even
if
it's
the
same
issue
or
maybe
a
different
issue
who
trust
the
first
issue
or
sorry
or
different
organization
who
trust
the
first
issue
organization.
B
They
would
convert
that
personal
data
to
a
hash
and
search
for
the
data
on
blockchain
and
to
check
that
whether
it's
really
issued
by
the
issuer
and
signed
by
their
private
key
and
if
it
matches,
then
the
user
can
log
in
all
right.
So
this
is
once
again,
very
briefly:
can
you
can
you
revise
points
from
one
to
nine,
okay,
yeah,
all.
B
Now
the
user
is
sending
the
austra
the
personal
data
and
the
biometric
template
to
a
issuer.
So
if
there
is
a
need,
then
the
issuer
would
do
a
background.
Verification,
deduplication
and
and
the
template
would
be
stored
in
a
centralized
biometric
database.
So
this
is
an
optional
part.
Like
I
said,
perhaps
you
know
when
you
are
going
for
aadhaar,
let's
say
so
in
aadhaar:
they
are
actually
every
time
they
are
checking
it,
and
then
they
also
need
to
make
sure
that
the
user
is
not
creating
multiple
fake
identities
for
themselves.
B
So
there
is
a
need
for
one
to
end
matching
in
this
kind
of
scenario,
but
not
in
all
scenarios.
So
not
in
all
scenarios.
The
issuer
need
to
do
a
do.
A
deduplication
part,
so
one
to
n
matching
is
a
optional
optional
probability
and
then
the
issuer
is
converting
this
to
a
hash
and
sent
to
the
blockchain.
So
the
hash
is
of
the
personal.
B
A
B
Now,
the
user
next
time
the
user
wants
to
log
in
so
the
user
logs
in
with
liveness
detection
test,
and
the
user
is
sharing
the
personal
data
with
the
with
some
verifier.
Now
this
verifier
could
be
the
same
organization
or
a
different
organization.
So,
like
I
told
you
that
in
this
modern,
the
issue
is
not
keeping
because
this
this
step
three
is
the
optional
part.
B
So
maybe
the
issue
is
not
keeping
the
user's
details
so
every
time
it
there
is
no
one
to
end
match
so,
every
time
the
user
logs
in
the
user
is
not
sending
their
biometric
again
and
again.
So
it
is
only
the
personal
data
that
the
user
is
sending
and
the
verifier
is
converting
it
to
a
hash.
Like
I
said,
the
verified
could
have
the
same
same
organization
or
a
different
organization.
B
It
is
a
use
of
biometrics
to
secure
personal
data.
Biometrics
is
to
login.
How
do
you
log
into
the
system?
Okay?
So
because
you
know
we
are
talking
about
decentralization,
why
should
we
again
go
for
the
same
user
id
and
password
model
for
the
login
to
this
kind
of
system?
Now
people
are
still
doing
it.
You
can
see
that
there
are
many
organizations
who
are
using
a
user
id
and
password
to
log
into
ssi,
but
we
are
not
doing
that.
A
B
B
A
B
A
Hi
ma'am,
so
one
question:
how
to
our
application
will
support
multiple
ways
of
identity.
Right
now
we
have
seen
we
can
access
the
application
using
the
mobile
using
the
laptop
or
so
many
smart
devices,
also
so
right
now.
So
what
I
understood
this
user
will
share
has
any
data.
It
might
be
other
card
or
any
any
number
based
on
the
country,
and
it
would
be
once
it
will
be
approved
by
the
issuer.
Then
it
will
be
stored
in
the
blockchain.
B
B
A
Any
application
that,
let's
take
the
example
of
any
jamato
you
can
use
using
the
jamat
or
any
google
also
gmail
also,
so
there
are
multiple
ways
like
the
multi-factor
authentication
of
the
general
passwords
from
the
mobile
number
also.
Similarly,
I
believe
this
will
be
all
the
it
will
be
always
already.
Yes,.
B
A
B
Right,
that's
right,
I'll,
come
to
any
okay,
only
only
14
minutes
late
now
yeah.
So
there
are
a
couple
of
examples
I
can
tell
you
one
is
I
mean,
live
use
cases
which
have
gone
to
production?
The
first
one
is
a
few
ledgers
member
pass.
So
q
ledger
is
a
credit
union
in
us
and
it
has
got
many
banks
and
cooperative
societies.
You
know
working
together
so
so
they
have
come
up
with
this
model,
so
this
works
pretty
much
like
sso
single
sign-on,
so
the
user.
B
Once
the
user
is
logged
in
to
this
credit
union
or
q
ledger,
then
all
the
banks
or
and
all
the
other
organizations
who
trust
the
credit
union
they
allow
the
user
with
the
same
access
level.
So
this
is
by
sovereign
and-
and
this
is
in
production,
the
the
model
this
product
is
called
member
pass
and
this
is
devised
by.
I
think
this
is
device
by
everyone,
so
you
can
search
on
on
google
on
this.
So
this
is
a
product
which
is
live.
B
If
I'm
not
wrong,
so
this
also
has
gone
to
production
pretty
recently,
when
I
say
pretty
recently,
it's
just
like
two
three
months
so
within
that
now
now
you
know
I
just
talked
about
authentication
part.
Now.
Let
me
talk
about
you
know
yeah.
This
one
is
also
authentication
yeah.
So
this
is
a.
This
is
a
use
case
by
the
government
of
australia,
and
this
is
still
in
in
in
research
page.
B
I
don't
think
that
they
have
gone
to
production,
but
they
are
working
on
this
project
for
last
one
or
two
years,
so
australia
government
is
delivering
a
digital
identity
product
a
program
that
will
allow
government
services
to
be
easily
available
to
people
and
business
online
at
any
time.
So
the
plan
is
to
cover
many
services
through
one
national
level,
identity
for
each
citizen
of
the
country.
Also,
most
paper
based
identity
checks
would
be
transferred
to
digital
experience.
B
So
some
of
the
services
you
can
see
here
are
like
taxation,
welfare,
health
care,
business,
education,
social
services,
banking,
etc.
So
they
are
also
using
biometrics
and
liveness
detection
check
for
authentication
users
to
services.
Just
like
what
I
told
you,
so
you
can
go
and
search
for
trusted
digital
identity
framework
by
australia.
So
this
is
this
project
can
go
online,
maybe
in
2021,
because
digital
projects
are,
you
know,
you
know
everyone
is
a
hurry
to
deliver
the
digital
identity
project
scenes.
B
So
here
also,
you
can
see
that
the
government
is
providing
some
mechanism
or
sso
mechanism,
a
decentralized,
ssr
mechanism.
So
once
the
user
is
logged
into
the
government
services,
then
there
are
many
third
parties
who
would
let
the
user
login
to
their
systems.
So
similarly,
no,
this
government
of
singapore,
so
singapore
is
authenticating
four
million
of
its
citizens
online
with
facial
verification,
so
they
are
using
facial
verification
and
supplied
by
this
is
a
product
called.
I
prove
you
can
search
for
iproof
and
simple
facial
biometrics.
Cheek
is
sorry.
B
Sorry,
simple
phase
biometric
cheek
provides
singaporean
with
secure
online
access
to
government
services
and
private
enterprises
also
the
same
model.
The
private
enterprises
are
able
to
take
advantage
of
this
model
of
this
digital
identity
infrastructure
to
authenticate
customers
online.
So
this
means
that
government
would
be
the
first
issuer.
B
So
if
you
ask
me
that
who
should
be
the
first
issuer
because
it
works
like
a
chain
right,
I
just
showed
you
that
if
there
are
multiple
issues,
then
sometimes
you
know,
I
have
worked
in
projects,
so
the
first
issue
is
government
and
then
the
second
issuer
would
always
ask
that.
Can
you
please
share
me
your
previous
data,
so
it
would
be
first,
the
verified
and
then
the
issue,
so
it
would
work
like
a
chain.
The
first
issue
is
having
them
bearing
the
maximum.
B
You
know
the
maximum
responsibility
and
the
other
ones
would
just
check
and
you
know,
provide
their
set
of
certificate.
So
then
the
next
one
is
canada,
so
the
so
in
this
project.
It's
a
very
interesting
project.
This
project
is
called
tell
us
wants.
So
here
the
project
is
today
to
reduce
the
relative.
Sorry,
the
the
agent
of
this
project
is
to
is
red
type
reduction
or
to
get
rid
of
excess
administrative
burden
associated
with
administration
of
small
business.
The
project
is
called
taylor
swans.
B
We
should
require
any
user
to
upload
their
data
only
once
so.
Data
would
be
certified
by
the
designated
issuers
and
then
the
user
can
share
it
again
and
again
to
different
service
providers.
It
works
on
a
very
similar
model,
so
also
there
is
a
very
you
know,
interesting
use
case,
so
the
government
is
issuing
licenses
to
organizations
especially
startups
using
which
they
can
work
with
others.
B
So
like,
let's
say
that
you
know
in
a
supply
chain
project,
I'm
a
I'm
a
buyer
and
I
want
to
buy
something
from
canada.
Let's
say
so.
This
project
is
by
british
columbia.
You
can
see
over
here,
so
so
sorry,
so
I'll
just
go
and
search
for
all
the
startups
in
canada
who
are
supplying
that
kind
of
material
which
I
need
and
they
are
certified
by
the
government,
because
you
know
there
could
be
a
possible.
B
A
lot
of
you
know
fake
projects,
fake
organizations,
so
the
government
is
providing
them
certificate
and
they
can
share
that
with
third
parties.
So
it's
really,
you
know
a
good
way
for
a
great
way
for
edge
of
business.
Then
there
is
the
project
called.
I
response
so
this
I.
I
really
love
this
project
so
here.
A
B
B
This
project
is
especially
for
third
world
countries,
poor
countries
in
africa
and
maybe
latin
america,
where
there
is
a
lot
of
child
trafficking.
The
children
are
kidnapped
and
taken
across
the
border
and
they
get
exploited
so
every
time,
the
user.
Sorry
the
child
is
trying
to
cross
the
border.
Then
there
would
be
a
border
security
officers
who
would
ask
for
the
child's
verification,
so
they
would
need
the
consent
of
the
guardian
or
the
or
the
local,
the
legal
guardian.
So
how
that
would
happen?
B
B
So
they
would
just
check
that,
whether
it's
the
same
child
from
the
date,
they
would
get
a
reference
and
they
would
combat
the
biometrics
and
see
that
whether
it's
the
same
child
and
whether
it's
the
same
guardian
and
also
their
digital
consent
would
be
needed
to
cross
the
border.
So
this
is
a
project
which
currently
is
an
e-wade.
It's
still
not
in
production.
I
believe-
and
this
is
this-
is
a
you
know,
ngo.
I
respond
you
can
search
for
this
and
this
a
very
similar
use
case
can
be
created
for
elderlies.
B
So
you
can
also
have
more
than
one
guardian
in
such
cases.
So
digital
identity
is
a
hot
cake
in
today's
world.
You
can
see
in
this
picture
how
many
different
countries
in
the
world
are
doing
some
research
or
other
and
digital
identity,
and
especially
ssi.
So
you
can
see
so
many
different
digital
identity
projects.
Not
all
of
them
are
decentralized,
but
I
can
tell
you
like
the
australia.
One
is
decentralized.
The
government
uk
one
is
decentralized,
and
singapore
one
is
decentralized,
so
they're
all
yeah
british
columbia.
B
I
just
I
just
told
you
about
this
use
case
right.
So
all
these
use
cases
I
mostly
I
covered
so
they
are
using
decentralized
identity
model
for
for
identity
for
of
their
citizens
or
something
of
that
sort
and-
and
also
there
are
new
privacy
laws
like
gdpr,
who
hasn't
heard
of
gdpr
pdpa
pdpa
is
a
privacy.
You
know
you
just
started
related
to
privacy
of
user
starter
in
singapore
in
india.
Pdpb
is
going
to
be
you
know.
Perhaps
it
would
get
the
green
signal
buddies
soon.
B
65
percent
of
world's
population
will
have
its
personal
information
covered
under
modern
privacy
laws
and
now
coming
to
the
area
of
research,
because
I
told
so
much
on
the
on
the
architecture,
but
I
need
to
tell
you
that
what
are
the
different
ssi
protocols
available
in
the
market,
because
we
are
in
the
hyperledger
group,
so
you
can
search
the
one
which
is
very
popular
in
the
market-
is
high,
pleasure,
indie
and
aries.
You
can
search
for
them.
B
If
you
are
on
ethereum,
then
you
got
civic,
and
you
put
please
note
that
indian
aries
they
are
platforms,
whereas
civic
and
newport,
I
think
they
are.
They
have
apps
also,
so
you
do
not
have
to
do
any
any
development
you
just
you
can
directly
use
their
app.
Then
there
is
a
project
called
microsoft's
iron,
so
microsoft's
ion
is
created
by
microsoft
and
that
is
still
not
online,
so
it
would
be
online
pretty
soon
and
then
I'm
working
with
r3d
and
we
are
using
hashgraph
as
the
public
blockchain.
B
So
please
note
that
if
you
are
using
hyperledger
indeed,
then
your
public
blockchain
would
be
provided
by
the
indie.
You
know
is
available
on
backed
up
backed
by
sovereign
foundation,
so
the
success
factor
of
ssi
you
can
see
over
here.
How
do
you
make
sure
that
your
project
is
successful,
so
so
the
first
one
is
how
good
your
biometrics
integration
has
happened.
You
need
to
have
a
very
good
biometrics
with
the
safety
and
security.
B
Scalability
is
scalability
and
throughput
is
very
crucial
because
we
are
talking
about
a
p2p
model,
not
a
b2b
model.
Regular
blockchain
might
be
slow,
it
doesn't.
Nobody
cares,
but
identity
platform
has
to
be.
You
know,
have
to
be
highly
scalable
and
throughput,
because
you
have
to
cater
to
the
need
of
not
hundreds
but
not
thousands
but
millions
or
billions
in
future.
Cyber
security
should
be
strong,
interoperable.
It
should
be
interoperable
and
integrate
different
identity
networks
should
be,
you
know,
integratable
with
others,
selective
disclosure.
B
I
just
discussed
that
how
different
kind
of
data
sharing
can
happen,
and
that
is
that
is
a
area.
One
should
invest
on
and
validated
nodes
that,
because
we
are
not
working
on
proof
of
work
model.
We
are
working
on
something
like
proof
of
stake
model
which
so
that
it
is
fast.
It
is
file,
throughput
and
scalability.
B
So
who
are
the
validated
nodes
or
who
are
the
people?
Who
are?
You
know
violating
the
transactions?
That
is
that
would
conclude
that,
how
safe
and
sick
or
and
how
successful
your
ssi
model
is.
So
we
are
working
with
r30.
We
are
using,
like
I
said,
hashgraph
and
we
are
catering
to
because
hashgraph
is
a
very
highly
scalable
one.
B
A
B
So
there
is,
we
are
trying
to
do
that.
Actually,
the
research
is
going
on
and
we
are
trying
to
make
it
interoperable.
It
doesn't
matter
that
whether
you
have
used
microsoft
or
whether
you
have
used
hashgraph,
whether
you
have
used
indie
but
maybe
in
near
future,
because
digital
identity
is
moving
pretty
fast.
So
in
near
future,
you
can
see
a
day
would
come
when,
even
if
you
are
on
a
different
identity
model,
but
they
would
be
able
to
interact
with
each
other.
B
A
So
how
they
will
enter
complicate
might
be
through
the
services
or
it
might
be
possible,
I'm
working
on
any
any
pro
any.
You
know
blockchain
private
blockchain
and
somebody
is
working
on
the
public,
blockchain
blockchain.
So
how
that
particular
communication,
whether
it
will
be
through
the
web
services
or
the
microservices.
B
You
are
sharing
your
data
over
there,
so
you
are
not
sharing
all
your
data,
only
the
data
that
is
needed.
No,
your
there
won't
be
any.
There
won't
be
any
security
checking
there
won't
be
any
you
know
regular
onboarding
process.
Nobody
is
going
to
stop
you
because
you
know
from
a
distance.
You
would
be
able
to
do
it
right,
so
that
would
be
sensors.
Who
would
see
your
biometrics
and
there
would
be
sensors?
Who
do
you
know,
receive
your
data
and
see
that
it
is
already
genuine
data.
B
A
Okay,
okay,
it's
like
similar,
like
we
have
correct,
but
it
will
be
kind
of
a
different
kind
of
modules
through
which
they
will,
for
the
issuer,
they'll
be
very
different.
The
screen
will
be
there.
They
will
come
like
in
normal
application,
I'm
asking
in
normal.
If
you
sure
they
will
just
give,
she
can
see
the
list
of
the
pending
document.
They
can
approve
it
and
once
it
got
approved,
then
it
proceed
to
the
blockchain.
B
It
is
a
role
you
got
a
website
now
you
are
saying
that
you
can
apply
for
your
certificates
here
now,
like
let's
say
you
are
applying
for
your
passport,
so
there
is
a
website.
So
similarly
you
are,
you
are
sending
your
data
to
that
website.
Now
that
website
there
would
be.
Of
course
there
would
be
a
background
notification.
People
might
come
to
your
place
and
obviously
I
mean
the
same
same
process
would
happen
for
the
issuers,
because
they
are
doing
a
background
verification.
They
are
doing
a
deduplication.
B
There
would
be
capturing
of
your
biometrics,
so
those
things
would
happen
and
then
they
would
issue
a
certificate
to
you
as
well
as
they
would
send
a
hash
copy
to
a
public
blockchain.
Now
you
are
visiting
another
website
and
they
are
saying
that.
Can
you
share
all
this
verified
data
with
me
now?
They
would
all
should
be
either
from
this
issue
or
from
this
issue
or,
like
you
know,
in
certain
cases
they
said
that
we
would
approve
only
your
pan
or
your
passport.
Three
four
things
right.
A
Thank
you,
mom.
Thank
you,
hi
ma'am
srinivas.
Here
I
have
two
questions.
You
are
presented:
multiple
systems
under
development
or
whatever
in
the
production.
What
are
the
limitations
from
all
these
systems
that
you
have
identified?
This
is
the
first
question
and
second
question
is,
since
this
is
digital
identity.
A
B
B
B
B
So
maybe
when
organizations
are
starting
with
solutions,
they
won't
be
able
to
make
out
that
this
might
happen,
but
with
time
when
more
and
more
users
join-
and
maybe
in
future,
like
I
said,
one
user
might
be
having
multiple
devices,
so
we
have
to
come
up
with
a
solution
where
which
is
highly
scalable
and
through
photo,
should
be
good.
Those
things
we
are
yet
to
see.
So
that
is
why
we
are
going
for
hashgraph,
but
we
can
also
try
with
hyperledger
indie.
B
So
you
have
to
see
what
kind
of
what
kind
of
users
you
are
catering
to
like
what?
What
is
your
user
base?
So
if
it
is
very,
very
big,
like
you
are
going
for
a
national
identity
program,
so
obviously
your
number
of
users
should
be
very
high,
so
what
kind
of
solution
would
work
there?
You
have
to
do
a
lot
of
testing.
A
I
have
two
questions.
The
first
question
is
like
when
we
talk
about
like
sharing
the
identity,
so
it
may
vary
based
on,
like
the
I
mean
verify.
For
example,
if
I'm
presenting
my
data
to
an
educational
institution
for
background
check,
I
may
probably
have
to
share
my
life.
Okay,
smart
certificates,
okay,
get
off,
but
another
thing,
but
the
same
thing
may
vary
when
I'm
going
for
a
bank,
I
mean
loan
approval.
So
how?
How?
How
is
that?
Like?
A
B
Yeah
yeah,
so
that
is
a
very
interesting
question.
In
fact,
you
know
many.
Many
of
my
clients
ask
me
this
question,
but
the
answer
varies
from
scenario.
To
scenario
like
let's
say
you
are,
I
mean
who
is
paying
for
it?
It
could
be
the
issue,
it
could
be
the
user
or
it
could
be
the
verifier
depending
upon
the
use
case.
There
is
no
one
solution
that
fails
fits
all
like.
Let's
say
that
organization
is
creating
an
authentication
model
for
all
its
all
its
users
or
all
its
employees.
B
So
in
that
case
the
organization
is
the
issue
and
the
organization
would
pay
for
this
model.
Now,
let's
say
that,
let's
say
that's
a
okay:
there
is
a
matrimonial
site,
then
the
metabolism.
You
need
to
figure
out
whether
the
person
is
saying
that
I
have
passed
from
this
organization.
I
I
am
working
with
this
first
salary,
then,
who
is
paying
for
that?
Maybe
maybe
the
the
person
who
is
purchasing
it
right,
so
it
it
varies
from
scenario
to
scenario
yeah
that
helps
thanks.
Man.
A
A
B
B
A
B
Yeah
right
so
in
that
kind
of
model
the
what
we
need
is
different,
but
in
most
of
the
cases
in
hydrogen
fabric
or
in
so
it
is
a
b2b
space
and
we
log
into
that
kind
of
system
through
user
editing
password.
Don't
we
like,
let's
say
there
is
there,
is
coda
right.
So
in
coda
fabric
we
have
different
organizations.
No,
and
there
are,
there,
are
nodes
representing
different
organization.
Now
each
organization
might
be
having
1000
employees
right
who
have
access
to
that
node
right.
B
B
So
that
means
that
let's
say
that
you
got
the
coda
node
or
a
ledger:
your
fabric,
node.
Now
you
want
1000,
you
have
1
000
employees
in
your
organization
and
one
node
you
just
you
just
show
one
node
on
the
on
your
network
on
your
b2b
network.
Now
those
1000
employees
might
be
having
different
kind
of
labels
correct.
So
this
they
should
not
get
access
to
all
the
different
flows
right.
B
A
Okay,
okay,
got
it
and
regarding
the
reputation
so
probably
tomorrow,
once
I
get
the
earth
id
with
which
anyone
can
identify
me
as
an
individual
on
any
platform,
probably
on
any
digital
platform.
So
so
what?
If
someone
again
keep
tracks
of
where
this
id
identity
has
been
used
across
across
the
digital
world
or
digital
applications?
That.
B
Is
not
as
simple
see,
I
won't
say
that
biometrics
cannot
be
hacked.
Parameters
can
be
hacked,
but
it's
very
difficult
if
in
comparison
to
username
and
password,
so
it
is
likely
to
say
if
my
husband
tries
then
he
can
definitely
know
my
password
right.
If
my
children
know
try,
then
they
would
definitely
they
would
just
my
daughter
just
keeps
an
eye
on
my
my
finger.
You
know
the
way
I
use
my
fingers
and
seek
tells
me
what
my
password
is
right,
but
it's
not
that
simple
to
do
with
biometrics
yeah.
B
A
B
See
here
I'm
talking
about
only
the
authentication
and
authorization
part
now
where
those
data
are
used
are
something
different
and
also
perhaps
I
did
not
discuss
a
lot
about
private
dates.
So
what
a
private
deal
is
that
let's
say
I
have
a
issuer
and
one.
I
have
a
verifier
now
my
data
when
I'm
sharing
with
my
issuer
and
I'm
creating
a
separate
date
for
that.
That
is
a
private
date,
and
that
is
known
only
to
me
and
my
issuer.
B
B
So,
okay
yeah,
so
even
if
you
are
able
to
see
there
is
an
identifier,
but
that
identifier
would
be
different.
So
it's
not
that
easy.
I
mean.
If
you
go
to
the
standards,
it
says
that
it
is
not
completely
correlation
pro,
but
at
least
earlier
it
was
like
100
percent
correlation
was
possible.
Now,
maybe
you
know,
five
percent
correlation
would
still
be
possible,
but
it
would
be.
I
mean
we
are
trying
to
make
it
correlation.
True.
A
A
B
B
Yeah
I
mean
these
questions
are
asked
to
me
again
and
again,
so
we
are
actually
trying
to
follow
a
standard
when
you
say
node.
So
that
means
that
the
node
is
in
this
model.
The
user
is
not
interacting
with
the
blockchain.
It
is
only
the
organization
user
is
only
reading
it
right
right
right
that
you
then
work
right.
A
B
So
if
you
are
creating
a
node,
if
your
organization
in
and
you
approach
earth
id
to
create
a
node
on
your
behalf,
then
we
will
do
that
for
you,
so
we
are
working
in
two
different
levels.
We
are
working
on
platform
level
also
and
we
are
working
in
app
label
also.
So
if
you
want
to
purchase
our,
I
mean
platform
level,
then
it's
entirely
up
to
you.
If
you
want
to
create
a
node
on
your
own,
that
also
you
can
do.
B
B
Okay,
so
I'm
saying
that
we
you,
you
can
work
with
this
platform
on
a
platform
level
also
on
an
app
level
also
so,
depending
upon
the
requirement
of
the
client,
we
can
create
a
node
for
them
or
they
can
create
a
node
for
themselves.
Also
with
our
with
our
sort
of
you
know
our
the
way
we
work
we
just,
we
can
just
advise
them.
A
B
B
B
B
A
B
Sorry,
what
was
the
question
yeah
about
the
data
laws
right
yeah?
So
I,
as
I
said,
this
is
a
new
area
very
new
area.
So
if
you
go
for
any
ssi
network,
they
would
say
the
same
thing.
They
are
researching
in
this
area,
but
actually
we
are
trying
to
work
on
different
data
laws
like
in
india.
We
got
pdpb,
it
is
still
not
approved,
but
I
believe
that
it
would
be
approved
in
2021.
A
B
There
are
different
data
nerves,
privacy
protection
that
are
lost.
Like
I
said
in
you,
europe
gdpr
is
already
online.
Perhaps
in
singapore,
pdpa
is
already
online
in
india.
Pdp
would
be
approved,
it
is
still
a
bill,
but
it
would
be
approved
pretty
pretty
soon,
maybe
in
2021,
and
there
are
different
consumer
laws
anyway.
So,
depending
upon
the
area
that
you
are
working,
we
can
study
that
and
make
it
100
percent
compatible
to
that
data
that
no
personal
data
law.
A
Yes,
thank
you,
man,
hello.
This
is
vishwas.
I
have
got
two
questions
first,
like
as
you
said
that
public
blockchain
will
be
used
for
this
society.
So
if,
as
we
all
know
that
public
blockchains
are
works
on
instant
device
model
so
like,
if
we
are
going
to
bring
people
everyone,
we
are
going
to
kind
of
give
a
sovereign
identity
to
everyone.
So
in
public
model
they
have
to
kind
of
pay
for
every
transaction.
They
are
doing.
A
B
Me
let
me
come
back
to
this
slide
again,
so
we
are
not
using
public
blockchain.
Here
we
are
using
sorry
sorry,
we
are
using
probably
blockchain,
but
not
with
proof
of
work
consensus
model.
We
are
working
on
proof
of
author
authority
or
which
is
a
you
know,
which
is
a
model
like
proof
of
stake
in
proof
of
stake.
You
got
your
stake
or
your
money
involved,
but
here
all
the
validated
nodes.
B
They
are
not
individuals,
if
they're
not
something
like
in
a
bitcoin
in
bitcoin
everyone,
every
user
is
a
is
a
decision
maker.
No,
but
here
only
the
transactions
would
be
only
validated
by
certain
organizations
and
they
work
on
a
proof
of
authority
model
and
these
organizations
are
actually
the
ones
whom
people
would
trust
like
in
hashgraph.
We
got
because
we
are
relying
on
hashgraph
for
for
the
validation.
Hashgraph
is
a
dlt
which
works
in
a
very
different
model
than
than
bitcoin.
So
this
is
not
even
proof
of
stake.
B
This
is
proof
of
authority.
So
what
are
validated
nodes?
They
are
industry
leaders
like
google
ibm,
you
can
see
in
the
in
the
in
the
middle.
You
can
see
their
google
ibm,
wepro
dash,
telegram,
fia,
starter
telecom
wipro,
so
some
of
the
biggest
names-
and
they
are
the
biggest
name
in
each
of
the
verticals,
so
whom
people
trust.
B
A
B
B
B
B
A
B
I'm
sharing
to
everyone,
you
can
click
on
this,
so
there
is
a.
There
is
a
way
to
create
leads,
and
there
are
so
yeah
you
can.
You
can
read
it
in
your
free
time,
so
there
is
a
way
to
and
we
are
following
two
different
models.
One
is
on
w3c
for
date,
creation
and
also
fido
model
for
handling
the
biometrics.
B
So
here
they
tell
you
that
how
to
create
the
how
to
create
the
decentralized
identity.
How
it
looks
like
is,
you
know
it
starts
with
d.
I
d
then
hyper,
then
colon
and
then
the
name
of
the
the
organization
and
then
colon
and
alpha
numeric
like
that,
and
this
date
can
be
of
two
different
types.
It
could
be
a
public
date
or
a
private
date,
so
the
public
date
are
created
by
organizations.
B
Now,
whenever
a
user
is
sharing
some
data
with
any
organization,
be
it
a
issue
or
a
beta
verifier,
then
they
would
create
a
private
date
and
all
the
users
data
would
be
stored
against
that
private
date,
so
that
private
date
is
not
visible
to
other
organizations,
so
that
would
be
visible
only
to
that
organization.
So
that
means,
if
let's
say
I-
I
have
collected
data
from
five
different
issuers,
then
all
these
issues
would
be.
B
The
data
would
be
saved
with
the
different
did
names,
so
I
mean
the
private
date
and
the
public
did
they
look
alike,
but
their
usage
is
different.
Similarly,
with
the
verifier
or
different
private
date
would
be
created,
so
the
verifier
would
never
be
able
to
know
that
you
know
if
that,
even
if
they're
sharing
the
two
different
verifiers
and
sharing
the
data
with
each
other
to
know
that,
because
you
you
cannot
stop
or
verify
or
issue
to
retain
your
data
right,
I
mean
we
can
do
it
that
way,
but
you
know
they
can.
B
A
B
B
B
So
in
that
case,
what's
gonna
happen
that
the
user
can
have
five
different
devices
and
for
each
of
them
there
will
be
a
different
private,
key
and
public
key,
of
course,
and
that
would
be
also
associated
with
your
identity
so
like.
If,
if
you
got
a
car
which,
what
do
you
call
it
auto,
auto
self-driving
car
and
there
is
an
accident,
then
that
should
be
somebody
who
is
responsible
right
so
so.
That
is
why
I
know
that
would
be
associated.
B
Obviously
that
would
be
associated
with
the
with
the
individual's
identity
and
that
that
should
be
somebody
who
is
the
owner
who
is
responsible
for
handling
them,
so
obviously
that
we
would
be
using
that
public
key
infrastructure
over
here,
but
that
there
is
some
time
to
it.
So
more
research
needed
to
be
done
and
perhaps
in
future
in
two
months
time
I
will
come
up
with
another
session
where
I
can
share
how
the
iot
devices
can
work.
So
this
would
be
very
helpful
in
many
different
verticals.
B
Like
let's
say
you
can
do
it
not
only
for
machines,
you
can
also
do
it
for
for
animals,
like
you
know,
hurting
you
know,
hurting
and
tracking
animals,
or
you
know
every
animal.
I
think
I
I
just
shared
a
picture
a
couple
of
days
back.
I
just
created
it
and
shared
it
on
on
linkedin,
so
there
are
different
animals
in
in
a
farm,
and
each
animal
is
having
a.
B
They
have
a
what
you
call
tag
on
the
on
the
ear
and
what
they
call
iot
device
so
that
that
iot
device
would
tell
that
that
location.
At
the
same
time
they
could
have
information
on
the
vaccination,
and
maybe
if
it
is
a
milking
cow,
then
the
milk,
the
time
of
the
milking,
has
has
approached
there's
so
many
different
informations
that
it
can
share
with
their
owner
or
or
the
person
nearby.
B
B
A
Just
last
one,
as
you
said
that
biometrics
will
be
stored
on
blockchain
on
mobile
devices
only
and
it
will
be
used
only
for
login
purpose.
So
it's
just
like
biometric,
which
we
used
to
do
which
we,
which
we
used
to
login
into
mobile,
or
something
like
that.
It's
just
a
normal
use
of
biometrics
right,
it's
nothing
more
than
that.
B
B
So
I
don't
know
how
many
of
you
have
heard
of
the
payment
cards,
the
new
payment,
the
smart
cards,
which
has
got
a
sensor,
so
you
you
login
within
that
device
and
you
are
doing
a
one
to
one
matching,
not
one
to
name.
You
cannot
do
one
to
n
on
your
on
your
device
or
on
your
card
smart
card,
so
that
entire
matching
process
happens
on
your
device.
B
B
As
I
told
you,
header
is
known
for
its
high
scalability
and
throughput
number
one.
So
I
mean
you
tell
me
any
other
network
which
can
cater
to
10
000
conjunctions
per
second
and
1.5
million
transactions.
For
a
day
I
mean
that
can
be
more,
but
hydra
is
very
famous,
and
also
who
are
the
validator
nodes.
It's
working
on
a
proof
of
authority
model
right.
So
if
you,
if
you
see
that
who
are
the
validated
nodes,
they
are
the
industry
leaders
in
each
and
every
vertical
right.
B
B
I
would
trust
the
one
which
is
issued
by
government
right,
because
government
is
somebody
everyone
trusts.
So
that
is
why
we
trust
the
pan.
We
trust
the
passport
right,
because
the
government
is
doing
that
right.
You
can
show
me
your
you
know
certificate.
Maybe
I
mean
people's
people
have
got
fake
certificates
from
organizations
from
universities
that
they're
fake
universities,
they're
fake
organizations.
We
who
can
certify
that
this
person
has
worked
with
my
organization
for
five
years
right,
so
people
trust
different
organizations
to
different
levels.
B
B
Security
features
should
be
good,
but
then
who
are
the
validated
nodes
if
the
validated
nodes
are
big
companies
like,
let's
say
facebook,
libra,
facebook
libra,
I
believe
most
of
you
have
heard
of
it.
Facebook
libra
actually
got
the
idea
of
this
kind
of
architecture
from
hashgraph
itself,
because
you
know
today,
facebook
libra
is
having
1200
fortune
500
companies
as
their
validator
known.
So
that
is
why
that
is
bringing
that
trust
level
to
this
network.
Right
I
mean
I
want
to
have
half
of
my
money
on
cash
fuel
brand.
B
A
A
A
What's
up
and
yeah,
I
think
yeah
one
question,
and
even
I
have
the
same
question.
Maybe
you
have
answered,
but
still
I
am
I
want
to
know
there
is
this
guy
rishikesh.
He
is
also
a
solution.
Architect,
novartis.
You
have
written
this
question
in
chat.
You
can
just
see
when
it
comes
to
enterprise
adoption.
How
would
enterprise
marry
that
means
interpret
interpretability
their
existing
interests
if
there
is
an
existing
infrastructure,
and
this
is
the
new
adoption
other?
This
is
a
new
thing.
B
Yeah,
I
think
first
thing
first,
is
that
you
need
to
update
your
authentication
models,
so
the
the
username
password
you
know,
modification
from
you
know,
moving
away
from
united
password
to
a
decentralized
authentication
system
is
something
that
would
fit
into
any
existing
applications
so
for
any
existing
application.
Wherever
you
are
using
user
id
and
password,
you
can
adopt
this
kind
of
architecture
and
just
replace
it.
B
So
that
would
work
so
this
would
fit
in
any
vertical
in
or
in
any
application,
especially
whenever
there
is
a
you
know,
a
banking
websites
or
whether
high
liquidity,
high
security
and
high
privacy
is
needed.
So
I
would
say
that
they
should
be
the
first
one
to
go
for
this.
So
obviously
I
mean
the
industry,
which
is
showing
maximum
interest,
is
something
like
the
fintechs,
the
banks,
payment
providers
yeah.
B
So
I
just
did
a
one
of
the
one
of
the
biggest
payment
providers
yeah,
so
they
like
they're
doing
this,
I
mean
all
the
payment
providers
because
they
are
losing
money
right
wherever
there
is
a
chance
of
fraud
and
whatever
that
is
cost,
you
know
costing
the
whatever
that
is
hitting
the
pocket.
Then
you
know
they
would
definitely
do
this.
A
One
one
small
doubt
like
from
a
developer's
point
of
view
how
how
this
is,
and
I'm
not
sure
how
hydera
has
graph
work
is,
but
I
am
just
thinking
about
how
do
you
map
all
the
data
like
in
how
many
smart
contracts
are
there
different,
different,
different,
smart
contracts?
We
have
to
write
for
different
different
organizations.
B
Now
see,
smart
contracts
are
not
used
in
identity
network,
so
you
can.
Smart
contracts
are
where
smart
contracts
are
needed.
Smart,
smart
contracts
are
contracts
like
logics,
so
here
it
is,
there
is
no
logical
search,
you
are
giving
access
or
you
are
not
giving
access.
That's
it
for
different
organizations.