►
Description
Verified.Me – Building a New Standard for Trust using Hyperledger - Dmitry Barinov, SecureKey Technologies
Digital ecosystems are critical to safeguard and protect data in today’s hyper-connected world. In line with this year’s theme, this demo will showcase the key advantages of blockchain in building a digital identity ecosystem, as highlighted through our launch of the Verified.Me network in Canada – a privacy-enhanced service enabling consumers to conveniently and privately assert identity information using trusted providers. This presentation will also highlight the importance of collaboration to strengthen personal data protection, as organizations navigate the opportunities and challenges that the hyper-connected era brings.
----
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 #HyperledgerGlobalForum2020 #Blockchain
A
1
1,
can
you
hear
me
awesome?
That's
great,
so
my
name
is
Dmitry
Byron
up
I'm
CTO
of
a
company
called
security.
I
have
about
15
minutes,
so
I,
don't
think
I
will
be
able
to
talk
about
everything.
What
I
can
or
should
talk
about
talking
about
how
hypervisor
helped
us
to
develop
the
system
that
we're
in
right
now
over
age
in
life.
But
let's
let
me
try
and
we
have
so.
A
It's
called
verified
me
and
the
idea
was
to
provide
multiple
identity
bundles
from
various
data
providers
to
the
data
consumer
and
to
ensure
that
the
citizen
or
user
of
the
system
is
a
physical
person
can
provide.
It
can
always
provide
it
with
consent.
So
that
was
generic
idea
how
we
came
up
with
the
name.
Well,
it
was
just
because
when
I
say
trust
but
verify
so
many
people,
laughs,
right,
verified
Mevo
was
one
of
the
chosen
things,
but
what
we
decided
to
do.
A
Today,
the
consumer
site,
the
user
would
agree
to
follow
through
the
process,
for
example,
location,
processor,
identity,
proven
process,
then
the
user
would
authenticate
with
a
so
again
strong
authentication
source
and
based
on
that
authentication,
a
number
of
the
identity
claims
associated
with
that
user
could
be
made
either
by
authentication
source
or
by
other
parties
who
trusts
authentication
source
right.
So
in
this
scenario,
I'm
just
sharing
my,
for
example,
the
the
data
from
my
bank,
but
I,
will
show
you
that
in
current
production
system
we
actually
have
a
lot
of
other
data
providers.
A
Who
can
kind
of
understand
that?
Oh
well,
if
the
bank
believes
this
is
Dmytro
bad
enough,
we
believe
that's
Dimitra
bad
enough
as
well,
so
we
associated
some
data
claim
on
that.
Another
important
point
was
obviously
that
to
ensure
that
the
user
can
provide
consent
on
the
flow
and
the
system
itself
has
very
interesting
features
such
as
the
user
can
see
in
the
user
agent
transaction
history.
There
is
obviously
a
transaction
trail.
A
The
data
itself
is
invisible,
so
the
there
were
very
interesting
things
that
we
have
done
so
we
always
have
been
looking
into
so
we
started
this
about
four
years
ago
now
and
now
we
should
be
started
to
create
a
number
of
very,
very
exciting
commercial
use.
Cases
for
for
the
system
that
were,
as
I
said,
we're
running
in
production
has
been
officially
launched
in
the
summer
of
last
year,
so
maybe
a
little
bit
about
budget,
which
is
hyper
laser
bite
which,
which
was
hydrolyzed
fabric,
on
which
the
system
is
run.
A
A
We
wanted
to
ensure
that
this
is
the
system
that
will
build
on
whatever
technology
platform
we
choose
to
use
we'll
have
ability
to
provide
the
transaction
indemnity
integrity
of
the
transactions
that
were
able
to
provide
the
verifiable
auditable
transaction
past
ISO
in
case
of
the
some
disputes
that
could
arise,
we
could
get
the
resolution
of
these
disputes.
Another
very
important
point
was
that
we
wanted
to
ensure
that
we
can
comply
with
strict
privacy
guidelines
because,
typically,
the
identity
sharing
systems
they
well
many
identity,
sharing
systems.
They
can
be
weakened
privacy
right.
A
So
what
we
did,
what
we
built.
We
built
the
system
with
engineering
principles
of
triple
blind
privacy,
where
data
providers
and
data
consumers
can
be
completely
blinded
from
each
other
and
where
the
operators
of
the
network
actually
never
see
the
data
that
passes
through
the
network,
meaning
that
they
might
see
the
data
processors
in
effort,
but
the
data
passes
encrypted
and
they
never
see
the
keys
with
which
data
I
encrypted
right.
So
that's
why
we
built
everything
hypervisor
fabric.
A
Once
again,
the
fact
that
we
wanted
to
have
this
distributed
ledger
was
probably
one
of
the
main
choosen
factors.
Right
fact
that
we
could
write
this
chain
code
and
we
could
write
a
lot
of
logic
into
the
smart
contracts
executed
by
the
chain
code
was
another
very
important
point
for
us
and
obviously
the
fact
that
it's
an
open
source
when
they're
a
kind
of
neutral
platform
right
that
provider
that
can
be
provides
certain
assurances
to
the
companies
who
adopt
the
platform.
That's
obviously
very,
very
good
too.
So
what
we
started
with
right.
A
We
started
with
work
in-house
Canadian
financial
institutions.
The
seven
financial
institutions
that
we
started
to
work
with
the
application
is
available
on
the
network
from
the
data
from
the
partners
who
have
right.
So
we
have
banks,
we
have
actually
quite
a
few
insurance
players.
We
work
in
with
a
number
of
governments
in
various
PC
projects
right
now,
Health
Care's,
their
gel
codes
are
there
right
now
in
Canada
and
so
on,
so
yeah.
A
We
started
a
significant
investment
in
interoperability
associated
with
w3c
standards,
and
I
will
be
talking
about
this
more
tomorrow
about
our
work.
How
we're
doing
this,
how
we
are
working,
how
we
combine
and
how
we
contribute
in
the
code
to
fabric
to
end
to
Ares
to
make
them
compatible
right
so
and
it's
in
itself-
that's
probably
a
topic
for
the
day
right,
not
for
the
15
minutes.
A
So
I
will
talk
about
that
tomorrow
and
if
I
still
have
a
few
minutes,
which
I
do
I'll
just
show
you
a
few
of
the
demos
how
it
runs
in
production
and
what
is
happening.
So
this
one
is
a
simple
demo.
It
once
again
is
just
production
screen,
so
I
want
to
apply
for
the
Sun
Life
Insurance.
You
can
see
that
it's
my
recording
rate,
so
it's
not
very
beautiful,
so
I'm
applying
for
Sun
Life
I
click
on
the
register
is
verified
me.
It
opens
up
very
frightened
me.
A
A
A
It
explains
basically
the
architecture
of
the
system
and
how
the
whole
fabric
is
involved
in
this.
So
I'll
just
start
playing
so
here.
The
first
user
just
installed
the
very
they're,
very
friendly
mobile
application.
Right
now,
we're
tying
that
mobile
application
to
the
bank,
because
the
bank
provides
once
again
a
syndication
factor
and
it
provides
the
route
of
trust
in
the
system,
doesn't
have
to
be
the
bank.
But
that's
what
the
Canadian
implementation
looks
like.
A
So
here
I
would
choose
the
bank
and
when
the
user
chooses
the
bank,
that's
actually
we
start
engaged
and
they're
now
verified
in
the
network
and
hydrology
fabric
network.
So
hopefully
the
video
goes
a
little
bit
faster.
Yeah
I
should
have
started
from
this.
So
this
one
kind
of
shows
the
architecture
how
the
bank,
and
they
into
integrated
into
the
verified
me
system.
We
are
providing
an
adapter
that
is
run
by
the
financial
institution
that
actually
provides
the
integration
to
the
apologi
fabric,
ledger
nodes
distributed
nodes.
A
We
are
registering
the
user
on
the
network
and
you
can
see
what's
happening
on
the
Left
right
there,
I
from
the
user
agent
perspective.
We
are,
after
we
register
an
user
on
the
network
and
then
associated
claims
about
the
user
registrations
are
eaten
into
the
distributed
ledger
of
the
network.
Certain
claims
are
written
in
the
private
ledger
that
just
owned
by
the
this
particular
financial
institution,
and
obviously
there
is
some
root
of
trust
that
is
put
on
the
user
agent
to
identify,
which
is
basically
it's
not
a
cookie
of
course
right.
A
A
We
elimination
a
number
of
efficient
and
other
types
of
attacks
on
the
user
and
on
the
commercial
use
of
the
system
in
that
way,
and
basically,
after
the
user
agent
retrieves
the
request
from
the
network,
which
will
be
there,
the
video
has
a
voice
over
and
that
voice
over
is
done.
A
nice
food,
nice
Awards
and
without
my
terrible
accent.
But
basically
you
can
see
that
we
get
the
request,
details
and
the
user
agent
decrypts
the
request,
and
then
it
displays
their.
A
The
user
provides
the
consent
in
the
user
agent
that
consent
is
interpreted
by
the
chain
code
that
we
are
on
top
of
the
hypervisor
fabric
and
that's
why
we
have
this
immutable
list
of
the
transactions
on
the
fabric
right
after
the
consent
is
done
by
the
user.
Basically
from
the
user
perspective
is
done
right
and
the
data
just
been
transferred
through
the
site.
Three
Oh,
sir
sorry
site
three
said
three
Stroeve
it
for
tomorrow,
private
channel
on
fabric
from
the
data
provider
to
the
data
consumer.
That's
pretty
much
it!
A
A
So
the
motivation
is
twofold
right.
Obviously,
some
organizations
want
to
participate
in
the
identity
networks
right
like,
for
example,
banks.
Financial
institutions
might
feel
that
they're
providing
an
extra
care
for
the
customer
right
same
as
governments
might
feel
like
the
this
is
actually
their
obligation
to
issue
the
citizens
digital
ad
right.
A
So
this
motivation
number
one
motivation
number
two
for
the
other
data
providers.
Right,
such
as,
let's
say,
credit
bureau
right,
oh
great,
we
were
just
wants
to
make
money,
and
typically
the
data
consumer
or
the
land
party
in
this
case
would
be
able
to.
So
there
is
a
billion
mechanism
around
behind
the
network.
A
The
billion
mechanism
is
based
on
the
fabric
logic,
as
well
or
on
the
chain
on
the
chain
code
logic
which
is
executed
to
the
fabric
and
the
basically,
the
data
consumer
in
the
end
is
built
for
the
data
it
received
and
some
of
this
billion
and
there
are
different
billion
models,
but
the
organization's
could
provide
data.
They
either
provided
as
an
enhanced
service
to
the
customer
or
as
a
citizenship
service,
if
they're
governments
or
just
because
this
is
a
convenient
way
for
them
to
share
their
data,
claim
in
a
secure
way.
A
Do
I
have
configuration
for
this
benchmark,
see
I
do
I.
So
let's
be
completely
true
to
this
right.
So
when
we
started
on
fabric,
it
was
0.6
version
right,
so
we
went
through
a
number
of
the
iterations
in
a
number
of
the
improvements
on
fabric
right
who
actually
worked
together
with
ABM
on
some
ideas:
how
to
improve
the
capacity
and
the
throughput
on
fabric
as
well
a
lot
of
the
configuration
and,
in
the
end,
what
we
understood
that
our
biggest
success
and
the
secret
sixth
secret
sauce.
A
If
you
a
mean
it's
not
a
secret
right,
but
our
expertise
is
really
on
how
we
are
able
to
production
allies,
a
system
like
that,
and
was
it
easy?
No,
it
wasn't
easy
from
our
perspective
right
it
took
literally
years
and
how
to
integrate
various
large
organizations
into
the
system.
Right.
That's
why
we
came
up
with
the
idea
of
the
adapter.
That's
why
we
we
spent
quite
quite
a
bit
of
effort
on
production,
lies
and
those
adapters,
these
adapters
a
region
goal,
because
we
just
had
this
environment
right.
A
So
how
do
we
write
a
good
container
container
docker
container?
Is
this
go
adapters
that
speak
fabric,
language
involved
in
one
side
and
normal
restful
api?
In
another
side?
That's
another
one.
We
ran
so
when
and
when
I
showed
10,000
CPS
rate.
10,000
CPS
is
a
fantastic
number
right,
it's
just
it's
great!
A
So
did
we
run
the
system
to
the
10,000
GPS?
No,
because
we
quite
honestly
know
deployed
and
the
hardware
that
would
run
search
volume
right,
but
we
know
how
to
scale
and
we
have
deployed
on
I
and
by
the
way,
I'm
not
I
have
no
affiliation
with
ABM
right,
IBM
people
here
in
the
buildin,
maybe
somebody's
here
in
the
room,
but
we
ran
the
first
version.
A
However,
I
am
right
now
on
IBP,
which
is
a
BM
Gaussian
platform,
which
is
there
a
vm
production
system,
but
we
are
going
to
migrate
from
a
beefy
v12
ABT,
B
I
think
I'm
using
the
right
numbers
there,
which
actually
allows
much
more
interesting
deployment
options
as
well.
So
we
were
literally
our
company
of
100
people.
We
have
probably
20
people
who
are
onion
the
separation
right
now,
yeah.
A
A
A
A
Our
projects,
so
I
will
be
one
skin
talking
a
little
bit
more
about
that
tomorrow
and
showing
actually,
where
we
run
in
the
projects
on
the
github,
but
right
now
what
we
are
doing
with
participation
in
the
project
with
Department
of
Homeland
Security
here
in
the
States,
with
at
least
four
other
companies,
and
we
are
going
to
show
the
Interop
of
verified
me
system
based
on
the
published
w3c
standards
in
end
of
April
at
I'iw.
If
you
know
what
IW
is
which
stands
for
my?
So
it's
exactly.
A
A
A
35:35,
something
like
that
so
for
but
I'll
explain
why
I'm
saying
this
right,
so
we
started
with
three
banks
right
now.
If
you
look
at
that
Massacre
page,
which
has
all
the
institutions
you
can
look
in
with
it-
has
seven
major
banks
or
five
major
banks
plus
two
banks
right
which
whatever
70
banks,
that
I
shown
you
and
it
shows
at
least
10
credit
unions
right
so
credit
unions,
joints
join
and
we
expect
that
they
will
join,
but
it's
they
typically
adopt
into
this
production.
A
Large
production,
integration,
infrastructure
programs
a
little
bit
slower
from
our
experienced
rate
and
we're
talking
to
a
number
of
the
consolidators
of
the
credit
unions
rate
because
for
credit
unions,
the
major
impact
is
how
much
you
invest
into
the
technology
and
what
return
they
will
have
for
their
shareholders
against
Rachel
members.
Members,
that's
the
right
name
so
that
that's
actually
the
main
point
right
and
many
of
them
use
some
standard
technology
platforms
which,
if
you
are
familiar
with
credit
unions,
you
would
know
operate.
A
Yes,
fabric
in
areas:
yes,
oh
boy,
so
we're
based
on
fabric
right
like
we're
based
on
fabric,
we
made
the
conscious
choice
right.
We
believe
it's
an
enterprise
platform
which
is
built
once
again
for
the
enterprise
use
cases
so
and
we
will
keep
used
fabric
for
in
the
next
releases
of
our
product
as
well.
Technically
Ares
is
an
inter
up
bridge
right
as
far
as
we
are
concerned,
so
we
even
Seguin
using
Ares
as
an
interrupt
bridge
for
the
w3c,
because
Aires
is
a
w3c
based.
A
I
am
NOT
that
much
up
to
date
on
where
Indy
is
actually
one
of
the
reasons
I'm
here
I
want
to
hear
this
right
where
India
is
on
w3c
standards.
The
last
time
I
heard
and
I
know
there
is
a
gentleman
who
might
say
that
I
am
right
or
wrong
right
here.
So,
but
the
last
time
I
heard
Indy
was
a
little
bit
late.
I've
been
up
to
date
to
their
latest
w3c
standards,
but
once
again,
I
would
actually
is
that
fair?
So,
and
that
was
the
last
time
I
heard,
which
was
in
November.
A
Yes,
yes,
oh
absolutely,
and
by
the
way,
this
standard,
so
not
ready,
so
I
will
be
the
first
one
to
stand
up
and
say
that
the
standards
are
so
not
ready
and
they
were,
they
will
be
there.
But,
but
once
again,
the
last
time
I
knew
I
heard
India
was
not
in
did
not
have
that
in
their
production
version
right
to
the
cup
drain.