►
Description
A virtual meetup hosted by Hyperledger Toronto where Tomisin from SecureKey will present 'The Future of Digital Identities'. In brief, this talk will discuss how Hyperledger Aries can make digital identity management simpler and more scalable which will ultimately improve user experience.
More about the event is at: https://www.meetup.com/Hyperledger-Toronto/events/272860707/
----
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
C
B
Okay,
cool
so
good
evening.
Everyone
welcome
to
hyperledger
toronto
meetup,
so
today
we'll
invite
thompson
from
security
to
talk
about
the
future
of
digital
identities.
So
I
wonder
if
and
any
of
you
work
with
hyper
ledger
ares
so
have
ledger
aoes,
it's
a
decentralized
identity
management
platform.
So
thompson
will
talk
about
how
avs
can
make
digital
editing
management
simpler
and
more
scalable
that
will
improve
user
experience
before
we
start.
B
A
D
D
I
joined
the
blockchain
industry
during
the
crypto
rush,
which
happened
a
few
years
ago
and
I'm
sure
many
people
are
familiar
with,
and
at
that
point
I
realized
there
was
more
to
it
than
just
cryptocurrencies
and
I
was
really
interested
in
the
underlying
technologies
and
then
I
started
working
with
startups
and
other
companies
around
the
world
and
decided
to
actually
take
the
leap
and
do
this
full
time.
So
in
that
time,
I've
come
across
different
kinds
of
technologies
and
implementations
and
realized
the
importance
of
digital
identity.
D
So,
most
recently
and
with
respect
to
aries
I've
worked
at
efforts
with
and
contributed
to
the
aries
framework
gold
library,
which
is
the
golang
implementation
of
hyperledger
aries,
which
was
developed
and
is
still
maintained
by
security
technologies
and
is
also
open
source.
So
anyone
in
the
community
is
free
to
contribute
to
this
project.
D
D
So
that
was
my
focus
and
the
components
of
this.
What
areas
agent
mobile
is
about
or
is
about?
Is
it
provides
native
mobile
bindings
for
the
golang
library?
So
that's
aries
from
our
go,
and
by
native
I
mean
it's
only
for
android
and
ios
applications
that
are
built
with
java
or
coplane
on
the
android
side
or
objective
c
and
swift
on
the
ios
side,
and
this
actually
supports
local
and
remote
agents.
D
So
you
can
actually
use
this
aries
agents
mobile
to
generate
android,
sdks
and
ios
sdks
and
within
those
sdks
you
have
the
ability
to
run
an
agent
on
your
device
or
to
connect
to
an
agent
running
somewhere
else,
so
the
aries
from
where
go
can
also
be
used
to
start
a
router
or
to
start
a
server
and
finally
aries
interest.
Mobile
has
custom
handlers.
D
It
supports
custom
handlers
for
events
notifications
so
later
on,
we'll
discuss
about
ditcon
and
communications
between
agents
within
the
protocol,
and
this
mobile
library
allows
you
to
have
your
own
handlers
for
events
that
come
in
okay,
so
tonight's
we'll
primarily
be
looking
at
three
things.
First,
we
will
go
over
the
existing
solutions
of
digital
identity
today
and
by
existing
I'm
referring
to
blockchain
solutions.
D
Then
we'll
look
at
digital
identity.
As
I
see
it's
for
the
future
and
then
we'll
briefly
discuss
about
how
we
can
get
there,
how
can
we
get
to
this
promised
land
and
codes?
Okay?
So
today's
solutions,
identities
on
current
blockchains
usually
come
in
two
forms:
the
first
you'd
see
in
privates
or
permission
networks
like
hyperledger
fabric
and
corda,
where
you
have
x509
certificates.
D
These
are
very
similar
to
what
exists
on
what
you
would
see
in
your
browser
or
on
a
server
in
a
traditional
application,
and
we
have
the
bitcoin
and
ethereum
style
which
uses
asymmetric
public
keys.
Let's
do
symmetric
keys
and
what
we,
what
you
notice
is
that
these
usually
are
accessible
via
a
node
or
a
central
back
end.
D
So,
in
the
deployments
of
fabric,
you
would
have
some
an
entity
called
the
certificates
authority,
so
this
certificate
authority
operates
usually
operates
within
the
context
of
one
organization
and
that
allows
the
organizations
to
control
the
issuance
of
identities
that
can
represent
them.
So
you
can
see
this
ca
issues
a
certificate,
a
digital
certificate
and
there's
a
public
private
key
accompanying
it
and,
of
course
the
principal
would
initially
first
request
the
certificates
and
it
can
be
issued
cas
as
such
authorities
can
also
revoke
certificates.
D
This
all
this
allows
them
to
control
these
identities.
However,
in
the
context
of
ethereum,
there
isn't
really
a
revocation
list
on
the
blockchain
itself.
You
can
create
a
relocation
list
within
your
smart
contract,
for
example,
a
simple
map
in
your
ethereum
solidity,
smart
contracts
to
prevent
certain
addresses
from
accessing
it.
However,
the
main
idea
is
to
use
asymmetric
key
cryptography,
so
you
own
ethereum
and
bitcoin
and
similar
blockchains-
you
usually
have
identities
represented
with
privates
and
public
key
pairs.
D
So
here
we
see
alice,
signing
a
document
using
a
private
key
that
generates
a
ciphertext
that
can
be
verified
by
bob
using
alice's
public
key.
So,
as
you
know,
the
private
key
is
something
sacred.
That's
anders
keeps
never
publishes
to
any
to
the
network,
but
the
public
key
is
available
for
everyone's
use.
D
Then
we
have
the
context
of
browser
extension
extension
wallets,
so
we're
getting
into
the
phase
of
user
adoption,
so
the
previous
slides
have
described
the
low
level
protocol
layers.
However,
not
everyone
has
the
capacity
or
should
access
the
lower
level.
So
we
have
the
application
layer
with
which
is
the
browser
in
this
case,
which
will
have
a
crypto
wallet
installed
in
this
browser.
D
D
So
typically,
this
is
what
to
look
like
in
this
two-tier
architecture,
which
was
sort
of
popular
between,
let's
say,
2016
and
2018.
The
misconception
that
we
had
in
the
industry
was
that
this
was
enough
to
have
a
client
that
would
connect
directly
to
the
blockchain.
So,
of
course,
everyone
is
familiar
with
the
streets
here,
where
you
have
the
application.
D
You
have
the
presentation,
layer,
application
and
data
layer.
What's
ethereum
provided
with
the
evm
and
smart
contracts
was
a
combination
of
both
application
and
data
layer,
so
smart
contract
logic
was
combined
with
data
on
the
blockchain
and
what
we
assumed
back
then
was
that,
with
by
injecting
a
wallet
into
the
browser,
we
could
have
direct
access
to
blockchain.
So
it
does
work.
D
It
takes
quite
some
time,
sometimes
after
several
minutes
to
get
the
transaction
confirmed,
and
some
of
these
wallets
rely
on
centralized
nodes,
running
ethereum
and
one
example
of
them
is
inferior,
which
is
used
by
metamask.
Metamask
is
the
logo
that
you
just
saw
apart
from
this?
It's
also
not
secure,
because
it
depends
on
the
browser's
security
and
the
application
security,
so
many
browser
applications.
Web
apps
will
be
built
to
javascript
javascript.
So
this
means
any
attack
that
can
happen
with
javascript.
D
D
Also,
this
doesn't
provide
a
native
mobile
experience.
The
reality
is
that
we're
heading
to
points
where
most
experiences
for
services
for
services
provided
by
companies
are
delivered
through
mobile
devices
and
not
through
web
websites.
What
this
means
is
that
we
also
need
to
find
a
way
to
connect
mobile
devices
to
the
blockchain.
D
However,
when
you
have
something
really
slow,
you
have
an
application.
That's
really
slow.
It's
really
difficult
and
frustrating
for
existing
to
interact
with
your
application
and
your
product
as
a
company,
apart
from
not
providing
mobile
experience
apart
from
being
slow.
What
you'd
see
happening
is
that
many
of
these
mobile
wallets
are
actually
just
browsers:
they're
they're,
they
are
mobile
apps,
but
the
mobile
app
is
a
browser
with
a
javascript
wallet
injected
in
there.
D
So
what's
actually
happening
is
you're
not
really
really
using
a
mobile
app
you're,
just
using
a
browser
and
accessing
different
dapps
decentralized
applications,
so
you're
just
switching
between
websites.
So
what
you're
really
doing
is
using
a
responsive
view
of
your
website
on
your
mobile
device.
So
that's
not
really
a
native
mobile
experience,
then
to
in
order
to
address
the
scalability
issues.
D
Suggestions
were
made
to
modify
the
protocols
themselves
so
with
bitcoin.
There's
the
concept
of
segregation
wallets,
which
are
segregated
witnesses,
the
witness
really
is
the
transaction
signature.
So
the
idea
here
was
that,
in
order
for
the
users
to
connect
directly
for
the
mobile
apps
to
connect
directly
to
the
blockchain,
the
easiest
thing
to
do
was
to
reduce
the
amount
of
data
they
have
to
store,
which
then
means
that
you
have
to
in
this
approach.
The
transaction
signature
is
removed.
D
D
D
However,
this
can
also
lead
to
fraud.
So
one
thing
interesting
thing
about
spp
is
that
it
was
included
in
the
original
bitcoin
white
paper.
So
these
are
all
different
approaches
to
scaling
a
blockchain
application
blockchains
to
make
it
easier
for
mobile
apps
mobile
devices
to
connect
to
a
decentralized
ledger.
D
Then,
finally,
we
have
the
api
wallets.
So
the
api
wallets
are
the
more
centralized
approach.
You'd
have
your
client's
application
that
connects
to
a
central
back
end,
run
by
a
private
company
whose
code
is
not
open,
source
and
and
within
that
server,
my
backend
there
will
be
connections
to
the
blockchains.
D
Now
what
this
means
is
that
the
keys
are
not
stored
with
the
clients.
The
key
is
actually
stored
in
some
data
store
or
database
on
this
backend
on
this
server.
So
if
you
don't
have
the
keys
they're,
actually
not
yours,
you
may
have
an
account
that
maps
to
some
key
in
the
database.
But
as
long
as
you
don't
have
the
private
key,
it's
not
yours,
which
means
it's
not
your
cryptocurrency,
which,
in
the
concept
of
self-serving
identity,
means
it's
not
your
digital
identity.
D
What
this
means
is
that
we
reach
a
we
reach
a
certain
scalability
trim.
We
reach
a
trailer
or
a
dilemma:
it's
called
the
blockchain
scalability
trademark,
which
is
popularized
by
ethereum's
founder
of
italian
bizarre,
and
what
this
treatment
says
is
that
out
of
three
items,
you
can
only
pick
two.
So
the
three
items
are
decentralization
security
and
scalability,
so
it
says
that
you
can
have
decentralization
as
security,
but
not
scalability.
D
So
on
this
side
you
see
networks
like
ethereum
bitcoin.
They
are
secure
and
decentralized,
but
they're,
not
scalable.
Bitcoin
has
only
can
only
output
about
seven
transactions
per
second,
you
can
have
scalability
and
security,
but
you
can't
have
decentralization
and
then
you
can
have
scalability
and
decentralization,
but
you
can
have
that
security,
so
this
trailer
makes
it
really
difficult
to
build
applications
that
use
blockchain
technology
and
also
build
them
without
having
the
users
have
intimate
knowledge
of
the
underlying
protocol.
D
D
Hyperledger
aries
is
a
project
that
is
focused
on
the
creation
of
agents
that
allow
mobile
devices
or
any
other
kind
of
device
to
send
documents
verifiable
documents
without
having
an
intimate
relationship
with
an
intimate
connection
to
a
decentralized
ledger.
This
means
the
hyperledger
aries
is
blockchain
agnostic
and
can
be
used
on
top
of
any
distributed
data
store,
so
it
doesn't
even
have
to
be
a
bitcoin
ethereum
or
fabric.
It
could
also
be
some
decentralized
ledger
now.
D
The
key
concepts
of
aries
include
dids,
did
documents
dead,
resolvers,
verifiable
credentials,
verifiable
present
presentations,
agents
and,
of
course,
did
communication,
so,
firstly,
decentralized
identifiers.
So
we
need
to
look
at
the
difference
between
an
identity
and
an
identifier.
An
identity
is
an
individual.
It's
it's
a
subject.
It's
it's!
It's
you
and
I
that's
that's
the
identity.
D
An
identifier
is
what
we
publicly
use
it's
a
name
or
some
other
reference
to
an
identity.
So
my
name,
for
example,
thomas
in
general.
That
is
an
identifier.
My
driver's
license
is
not
my
dense
fire.
My
driver's
license
is
an
attestation
made
by
the
government,
which
says
I
can
do
x,
y
z
and
I
have
the
role
of
a
driver,
maybe
g1
or
g2,
and
so
on
and
so
forth,
so
by
understanding
identifiers.
D
D
So
these
documents-
this
did
documents
are
data
that
describes
the
subject
that
we
did
and
they
can
contain
attributes
or
claims
such
as,
like
I
mentioned
before,
like
a
driver's
license,
for
example,
or
even
things
like
that
say:
okay
thomason
has
completed
a
bachelor
of
science
in
computer
science
and
this
is
an
example
of
what's
the
documents
could
look
like.
So
these
are
just
implementation,
details
and
the
at
the
level
of
the
protocol
and
in
the
code
this
is
what
will
be
passed
around.
D
Then
we
have
date,
resolvers
we've
spoken
about
how
dids
maps
or
did
documents
well.
How
is
that
mapping
going
on?
How
is
that
function?
What
is
that
function
that
does
the
mapping,
so
it
did
resolvers
really
just
performed
the
retrieval
of
it
did
document
that
is
identified
by
did
so
in
a
possible
deployments.
This
is
what
you'd
have
you'd
have
the
application
that
has
that
receives.
That
has
an
idea
of
that
knows
it
did
a
specific
did
and
then
it
points
to
some
resolver.
This
is
one
example
of
resolver.
D
This
is
universal
resolver,
that's
resolves
any
kind
of
that
is
designed
to
resolve
any
kind
of
date,
so
this
resolver
will
will
have
its
implementation
detail
within
its
implementation.
It
should
know
how
to
find
the
specific
data
registry
where
the
document
should
be
so
this
app
is
trying
to
get
a
specific
did
the
documents,
so
it
passes,
and
it
did
here
and
then
the
resolver
will
figure
out
how
to
retrieve
this
document
and
how
to
present
it
to
the
client.
D
D
Now
we
have
the
concept
for
verifiable
credentials,
so
very
private
credentials
usually
contain
these
components,
but
are
not
limited
to
these
components.
You
have
some
metadata
there.
You
have
the
actual
claim
and
the
proof
of
this
claim
so
in
real
life.
A
credential
contains
information
that
tells
you
something
about
an
identity,
or
that
tells
you
something
that
identity
has
done
so
a
verifiable
credential
is
a
digital
representation
of
a
physical
credential,
and
this
digital
representation
can
contain
the
same
amount
of
information
that
is
in
the
physical
one.
D
The
advantage
here
is
that
it
can
be
cryptographically
verified,
which
means
that
it's
tamper-proof
and
it
can
be
used
to
build
a
verifiable
presentation.
So
what
would
that
be
so
verifiable
presentations
or
vps
have
this
structure
again?
There's
some
metadata.
It
contains
a
verifiable
credential
and
then
there's
some
proof
in
there.
D
So
a
verifier
representation
would
not
contain
data.
That
is,
that
does
not
need
to
be
disclosed.
For
example,
the
context
is
me
presenting
my
driver's
license,
my
verified
presentation
and
in
the
co
in
that
context,
all
if
all
they
need
to
check
is
my
driver's
id.
The
presentation
would
not
contain
data
about
my
dates
of
birth
or
country
of
origin,
or
things
like
that.
D
So
what
this
means
is
that
they
can
hold
cryptographic
keys
to
prove
this
responsibility,
so
these
agents
would
usually
live
on,
maybe
a
mobile
device
or
some
cloud
service.
But
the
advantage
here
is
that
by
having
them
on
your
mobile
device,
you
can
be
sure
that
you're
in
control
of
the
keys,
that
represents
your
identity
and
not
a
centralized
service
and
agents,
have
the
ability
to
interact
with
each
other
over
a
protocol
known
as
ditcom.
D
So
ditcom
is
shows
for
data
communication,
and
it's
ensures
secure
and
non-direct
human
communication
and
by
non-direct
what
we
mean
is
that
you
could
have
two
users,
maybe
alice
and
paul
and
alice,
might
just
click
on
the
button,
and
that
would
send
some
information
from
her
mobile
app
to
bob's
jumbo
app
and
both
of
these
apps
can
have
agents
in
them.
This
means
that
they
will
just
be
communicating
back
and
forth
through
a
series
of
events
and
passing
documents
with
each
other,
so
did
com
usually
would
have.
A
D
Rely
on
trust
to
humans,
so
the
lord
that's
layer,
one
we
have
the
actual
public,
blockchains
or
even
private
blockchains.
We
have
these
blockchain
or
decentralized
distributed,
ledger
technologies.
That
are
the
actual
data
stories
then,
just
above
that
we
have
public
dates
and
in
layer
two.
This
is
where
you
had
bitcoin
protocol.
D
So
we
did
like
we've
just
explained.
You
have
agents
that
are
sending
information
back
and
forth.
So
agents
can
have
connections
to
multiple
agents.
So,
within
this
mobile
app
on
this
mobile
device,
you
do
what
you
have
is
an
agent
plus
a
wallet.
So
it's
in
the
wallets.
You
have
the
cryptographic
material
that
represents
the
identity
of
the
mobile
app
user.
D
D
The
issue
will
issue
this
verified
credential
on
their
behalf
and
the
verifiable
credential
will
be
converted
into
a
verifiable
presentation
which
would
contain
a
proof
that
is
then
sent
to
a
verifier,
and
the
verifier
is
able
to
approve
this
presentation
because
they
trust
the
issuer,
so
each
of
these
entities
will
have
their
own
agents
and
finally,
at
the
top
layer.
This
is
where
you
have
the
governance
frameworks,
so
the
governance
frameworks
really
just
define
how
within
how
the
mechanisms
and
incentives
for
how
a
specific
system
should
run.
D
So
we
have
some
trust
action
inquiries,
our
credential
registries.
We
have
auditors
at
this
layer.
So
on
the
top
two
layers,
we
really
rely
on
human
trust
and
down
here
we
rely
on
cryptographic
trusts
and
what's
the
benefits
of
that,
there
are
very
few
things
that
could
there
are
fewer
things
that
could
go
wrong
at
this
layer,
because
all
that
is
happening
now
on
layer.
Three
is
just
the
exchanger
credential,
the
management
of
the
identity
or
the
implementation
and
the
storage
of
the
wallets
of
the
keys
and
the
wallets
is
now
handled
by
aries.
D
So
the
first
project
in
the
hyperledger
coming
community
or
garden
to
go
after
identity
was
ending
and
indy
was
a
is
a
composites
and
all-in-one
did
project,
so
it's
actually
spanned
across
layer,
one
two
and
three.
So
the
problem
with
this
was
that
it's
made.
Many
developers
and
institutions
feel
that
there
was
a
large
learning
curve
and
that
digital
identity
with
hyperledger
could
only
be
handled
with
indie.
D
D
So
what
this
means?
In
this
example,
we
have
an
employer,
who's
issuing
some
credential,
possibly
proof
of
employment
and
analysts.
Here
the
credential
holder
takes
that
credential
and
generates
a
verified
presentation
and
presents
this
proof
to
the
verifier.
The
verifier
is
then
able
to
validate
that.
This
proof
is
about
it,
and
everything
is
have
everything
that
happens
at
this
credential
exchange
layer.
D
The
agents
would
go
through
the
distributed
ledger
or
the
underlying
technology
and
do
whatever
resolve
resolution
of
documents
and
verificational
identities
that
are
required.
Now
you
look
at
this
and
you
can,
you
might
think?
Okay.
So
what's
the
benefits
of
this
over
the
previous
flows
with
bitcoin
wallets
web-based
ethereum
wallets
and
the
advantage
really
here
is
that
there's
less
there's
less
there's
a
less
need
for
the
prices
involved
to
have
any
idea
about
what
blockchain
is
so
that
really
improves
the
experience,
because
with
web
wallets,
what
you'd
have
to
do?
D
You
know
the
browser
web
wallets.
All
you'd
have
to
do.
Is
you
know,
connect
to
your
wallets,
create
a
new
account,
create
a
seed
phrase,
store
the
seed
first
somewhere
figure
out.
If
you
have
a
hardware
wallet,
I
figure
out
how
to
connect
that
hardware
wallet
to
the
web
wallet
and
you
know
really
go
through
all
this
learning
curve.
D
D
So
in
our
deployments
we'll
have
an
organization
that
represents
the
employer.
We
also
have
an
organization
that
represents
the
verifier
and
we
would
have
there
an
organization
that
provides
a
service
for
everyone
who
is
like
on
this.
So
it's
all
of
these
organizations
that
will
control
their
identity.
D
D
D
D
The
problem
is
getting
from
the
early
adults
to
the
early
majority,
because
the
early
majority
are
the
individuals
and
companies
who
have
access
to
the
mainstream
markets,
but
they
won't
adopt
the
technology
unless
someone
has
already
proved
that
there's
some
products
market
threats
so
by
so.
In
order
to
cross
this
chasm,
there
needs
to
be
a
product
market
fit.
D
So
what
are
some
possible
ideas
to
do
this?
We
can
really
focus
on
the
allegation
of
pains
or
presenting
credentials,
for
example,
showing
up
to
renew
your
driver's
license
going
back
to
school,
calling
people
to
get
some
documents
when
you
no
longer
have
their
contacts,
or
maybe
even
those
people
who
are
stopped
working
with
those
organizations.
D
So
this
means
having
lots
of
partnerships,
because
the
reality
is
that
blockchain
is
a
team
sports.
There
isn't
just
a
group
of
software
engineers
in
in
their
basements
or
something
that
will
write
software
and
get
it
delivered
to
the
world.
There
needs
to
be.
We
need
to
get
out
of
the
office
as
steve.
C
D
Something
like
that
yeah,
so
the
aries
agents
mobile,
supports
every
controller
that
aries
from
our
go
does,
and
one
of
that
is
the
mediator.
So
there's
messaging
as
well,
there's
out
of
band
there's
a
data
exchange,
presents
proof,
issue,
credentials
and
lots
more
so
mediator
is
one
of
the
bindings
is
one
of
the
controllers
which
are
included
in
the
mobile
bindings.
C
D
Okay,
let
me
understand
the
question,
so
you
mean
on
express
so
sovereign
just
for
the
just
for
everyone.
Sovereign
is
one
of
these
as
a
company
that
also
has
solutions
for
digital
identity
and,
I
believe,
they're
a
main
contributor
to
applicator.
Indeed,
so
it's
a
question
that
how
can
we
prevent
specific,
specific
companies
from
being
the
sole
controllers
of
how
documents
are
resolved?
Is
that
your
question.
C
D
So
I
haven't
looked
into
that,
but
if
I
was
presented
with
that
problem,
all
working,
what
I'll
try
to
find
out
is
if
there's
a
way,
if
there's
some
common
thing,
that's
some
common
components
that
both
you
know
both
pools
are
referred
to.
So
it
is.
If
nd
is
not
just
you
know,
storing
documents
or
whatever
if
indi
has
access
to
something.
D
If
it
points
to
some
other
external
registry
or
if
there's
some
other
product
or
alternative
to
indie
that
points
to
an
external
registry,
then
it
could
be
possible
to
use
that
as
sort
of
the
general
layer.
But
I
think
that
I
think
this
is
more
of
an
implementation
detail,
but
it's
not
something
I've.
I've
worked
with.
C
D
So
one
of
the
so
something
else
being
developed,
I
know
that
did
method
being
developed
is
did
trials.
Walk
trustwork
is
also,
I
believe,
some
of
the
members
are
actually
here
tonight
too.
Trust
block
is
an
initiative
open
source
initiative
that
actually
builds
on
high
preventure
areas,
so
my
work
with
aries
has
mostly
been
with
the
development
and
extension
of
the
platform
to
run
on
mobile
devices.
C
D
Yeah,
well,
I
think,
okay,
so
in
that
scenario,
that
might
be
a
legitimate
implementation,
because
even
with
something
like
a
theorem,
if
someone
is
operating
a
smart
contract
on
a
test,
they
shouldn't
be
able
to
cross
over
assets
or
current
or
value
or
even
currency,
to
the
main
network.
So
it
might
be
because
in
in
that
specific
scenario,
they
want
to
focus
on.
You
know:
separation
of
concerns
with
the
data,
so,
for
example,
a
main
network
is
meant
to
be.
C
So
if
I
get
the
governor
of
ontario
to
issue
a
driver's
license
on
the
canadian
credential
network
and
if
let's
say
the
bank
of
montreal
wants
to
use
that
and
they're
using
the
sovereign
network,
then
they
won't
be
able
to
verify
this.
The
credential,
because
the
credential
has
a
it's,
got
a
did
inside
it,
which
is
going
to
point
to
the
government
of
ontario
which
isn't
going
to
sit
on
the
soccer
network.
C
Yeah,
if
there's
multiple
networks,
there's
no
interoperability,
and
so
I
we're
starting
to
see
regional
networks
poke
up.
Finland
has
one
holland
has
one
there's
a
couple
in
germany,
there's
sovereign
out
of
the
u.s
and
there's
another
one
out
of
the
u.s.
I
think
what
they're
called,
but
none
of
these
are
interoperable
now,
okay,
so
it
seems
like
this
needs
to
be
a
problem
that
needs
to
be
solved.
I
was
just
wondering
if
maybe
your
team
was
aware
of
some
sort
of
work
on
that.
D
A
Hi
dave
this
is
troy.
One
of
the
very
screaming
go
contributors
just
to
address
that
specific
question.
Aries
framework
go
is
not
tied
to
a
specific
did
method.
It
supports
generic
methods.
In
two
ways
you
can
include
your
did
resolver
code
inside
the
framework
by
injecting
it
into
into
the
framework
when
you
instantiate
it
in
your
code.
A
It
also
supports,
did
resolution
through
an
external
service,
so
you
can,
alternatively,
configure
the
framework
to
reach
out
to
a
rest
service
and
ask
it
to
con
to
to
resolve
the
did
for
you.
So
in
that
way
a
particular
agent
can
support,
as
many
did
methods
as
you
wish,
and
we
have
tested
it
against
several
different
methods.
Ourselves.
C
A
Yeah,
that's
that's
correct!
So
if,
whichever
did
method
you
that
you're,
using
as
long
as
that
agent
is
configured
to
resolve
it,
it
will
get
a
compatible
did
document
back
and
from
there
can
find
the
keys
that
you
have
registered
into
that.
The
public
keys
that
you've
registered
into
that
div
document
and
the
framework
abstracts.
All
of
that.
A
Yeah
yeah,
so
that's
the
easiest.
So
when
you
have
it
in
a
in
a
a
service
like
the
universal
resolver,
that's
the
easiest
to
configure.
There
are
some
caveats
that
you
probably
might
be
be
wanting
to
run
your
own,
so
you
can
trust
the
code.
That's
running
on
that
service.
That's
that's!
Certainly
the
easiest
path.
A
Sorry
dave,
were
you
saying
something
we
lost
your
audio?
Oh
I'm
sorry,
sorry!
So
I
said
the
easiest
way
yes,
is
to
include
the
did
resolution
capability
into
a
service
like
universal
resolver.
The
caveat
is,
you
should
probably
be
running
your
own
universal
resolver
or
using
it
from
someone.
You
trust
very
much.
A
C
C
A
A
C
A
It
yes
trust
block
is,
is
a
is,
it
is
a
dead
method,
it
is
an
open
specification
and
the
the
resolution
is
open
source.
It's
based
on
a
decentralized
identity
foundation,
protocol
called
cytree,
so
it's
basically
layering
on
the
discovery
aspects
on
top
of
the
side
tree
spec
yeah,
and
it's
it's
open
to
use.
A
So
it's
that's
a
tough
one
for
me
to
answer,
because
I'm
a
trust
plot
contributor,
so
we
we
we
did
that
method
specifically.
So
we
could
have
discoverability
on
top
of
sidetree
and
sidetree
is
a
protocol
that
you
can
layer
on
top
of
any
blockchain
and
distributed
decentralized
content.
Addressable
stores
like,
for
example,
some
of
the
did
methods
layer,
sorry,
some
of
the
side,
free
methods,
layer
on
top
of
bitcoin
and
ipfs
or
ethereum
and
ipfs
we've
layered
on
top
of
fabric.