►
Description
This technical workshop will get you completely up to speed on what is happening in the world of self-sovereign identity development. Specifically, you will learn everything there is to know about Hyperledger Aries Framework JavaScript, an all batteries included toolkit for exchanging verifiable credentials. In recent times, this framework had evolved a lot due to active community involvement and EU funding. It is now one of the most mature tools in the Aries ecosystem. Aries Framework JavaScript specializes in multiplatform development and accessibility for developers starting out in the world of self-sovereign identity.
During this 1.5 hour workshop, Berend and Karim from Animo Solutions will go over the primary focal points of the framework as well as its current capabilities. They will give an overview of the roadmap ahead, with demonstrations of some of the solutions that have been built using the framework. After this, they will demonstrate how it feels to work with the framework by doing a live coding session.
You will enjoy this workshop if you are interested in self-sovereign identity, Web 3 tech stacks, open source development, JavaScript/TypeScript, Multiplatform development and practical tech-minded meet-ups.
More about the Aries Framework JavaScript is at: https://wiki.hyperledger.org/display/ARIES/Aries+Framework+JavaScript
----
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
Discord: https://discord.gg/rVCn4j7UFd
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #Blockchain
License
Creative Commons Attribution license (reuse allowed)
B
And
so
what
I'd
like
to
say
is
we're
going
to
try
a
little
bit
of
pushing
you
into
the
discord
channel.
So
if
anyone
hasn't
picked
up
the
discord
link
here
or
we
can
look
toward
engagement
in
the
hyperledger
discord
channel,
I'm
going
to
repost
it
right
now
and
then
I'd
like
to
also
do
is
just
offer.
If
you
don't
have
access
to
discord,
go
ahead
and
raise
your
hand
if
you'd
like
to
speak
or
go
ahead
and
post
into
the
zoom
chat.
C
C
I
will
try
to
keep
an
eye
on
the
chat
while
we're
doing
this
presentation,
because
the
first
part
will
be
a
presentation
and
then,
after
that
we
will
try
to
do.
We
will
then
use
something
and
we
will
do
a
parent
we'll
do
a
live
coding
session,
but
john,
please.
If,
if
I'm
missing
any
questions
or
any
questions,
you
know
don't
hesitate
to
jump
in.
C
Perfect
and
then
at
the
end,
we'll
have
a
q
a
as
well.
So
if
there
are
any
questions
left,
then
we'll
gladly
answer
them
so
yeah
once
again.
Thank
you
all
for
joining
it's
good
to
see
that
there's
so
much
interest
in
this
actually
next
to
me,
but
you
can
see
that
is
a
parent
sleepless
and
I'm
korean
stakeholder,
and
we
are
both.
C
So
a
little
bit,
can
you
yeah
a
little
bit
about
us
again
we're
from
animal
solutions?
Our
company
is
about
two
years
old
a
little
over
two
years.
We
are
based
in
utrecht,
the
netherlands,
and
currently
we
we
build
sni
solutions
and
we
help
other
companies
to
build
ssi
solutions.
So
we
also
do
a
bit
of
consultancy.
C
Our
main
mission
is
to
to
to
drive
the
adoption
of
self-serving
identity.
So
that's
also
one
of
the
reasons
that
we're
here
from
the
beginning.
From
the
moment
we
started
this
company
we've
been
mostly
active
in
the
hyperledger
aries
community
and,
more
specifically,
we
try
to
focus
on
hyperledger
or
every
stream
of
javascript.
C
I'm
not
sure
if
everybody
knows
what
self-serving
identity
is,
I'm
assuming
that
most
do,
but
for
those
who
don't,
I
will
quickly
introduce
the
concept
of
self-driving
identity
and
why
we
think
we
need
that
then
a
short
introduction
on
what
hyperledger
aries
is
per
se
or
exactly
is.
I
can
imagine
that
a
lot
of
you
come
from
other
hyperledger
projects
fabric,
so
a
small
or
short
introduction,
I
think,
would
be
good
too
much
background
noise
yeah.
C
C
How
does
a
solution
look
like
that
is
actually
built
with
with
aries
framework
javascript
we'll
go
a
bit
over
the
the
documentation
that
is,
that
is
fairly
new
and
here
at
the
end,
we'll
do
a
live
coding
session,
because
the
whole
point
of
this
presentation
of
the
session
workshop.
However,
you
might
call
it
is
to
to
show
you
that
ssi
can
actually
be
quite
easy.
C
Here
you
for
every
interaction
with
or
every
relationship
you
maintain
digitally,
so
that
could
be
with
twitter,
with
google,
with
your
bank,
whatever
you
use,
something,
that's
called
a
shared
secret,
which
is
a
striped
secret,
is
just
a
basically
a
fancy
word
for
something
like
a
password.
So
if
I
register
at
a
certain
website,
for
instance,
I
give
them
a
little
secret,
usually
a
password
and
the
next
time
I
come
around,
they
will
ask
me
for
a
secret.
C
C
You
preferably
don't
use
the
same
password
for
everything
which,
sadly,
is
the
result
often,
so,
if,
if
you
would
do
it
directly,
you
would
have
to
manage
a
lot
of
different
credentials,
different
passwords,
but
it
also-
and
this
is
something
that
a
lot
of
people
I
think
is
overlooked.
A
lot
is
that
it
requires
every
organization
to
in
a
way,
be
a
security
expert
like
you're,
giving
them
some
sensitive
information.
C
So
they
need
to
be
able
to
protect
that
and
well.
The
examples
on
this
slide
here
are
facebook,
twitter
and
google.
You
can
assume
that
they
have
that
in
place,
but
a
small
webshop
might
not
okay.
So
the
next
step
is
another
model,
the
federated
model,
also
known
as
the
identity
provider
model
or
single
sign-on.
C
C
So
you
don't
have
to
bother
about
it
or
deal
with
it.
We
will
do
that
for
you,
so
you
authenticate
with
google
and
if
everything
is
all
right,
google
will
tell
the
website
you're
trying
to
interact
with
hey.
This
is,
in
my
case,
green,
which
is
a
it's
a
it's
a
step
forward,
because
now
we
don't
have
to
manage
all
these
credentials.
We
just
have
one
or
a
few:
the
identity
provider
again
in
this
case
in
this
example
that
google
has
to
handle
the
sensitive
data.
C
So
it
doesn't
require
everybody
to
be
a
security
expert
in
that
sense,
but
it
has
major
downsides
as
well.
We
basically
place
a
third
party
between
every
interaction
we
have
so
in
this
example.
Every
time
we
log
in
to
a
certain
website
using
google
google
knows
about
it,
and
we
all
know
that
they
are
they
love
to
have
the
data
and
they're,
not
always
too
ethical
with
it.
C
If
somebody
cracks
my
google
account
now
they
have
access
to
many
many
services,
whereas
previously
they
wouldn't-
and
I
think,
probably
in
the
decentralized
world
the
most
important
one
is.
We
have
a
intermediate
priority:
we're
not
we're
not
communicating
peer-to-peer
and
that
party
potentially
could
say.
No,
we
don't
like
korean
anymore.
So
if
I'm
trying
to
log
in
they
just
say
no,
so
you
give
an
external
party
the
power
to
deny
access
to
certain
services,
which
is
it's
a
bad
thing.
C
C
In
this
case,
we
call
the
government
the
issuer
because
they
issue
you
a
passport
and
you
are
in
control
over
the
passport.
You
have
that
with
you
and
you
decide
who
sees
the
passport
and
who
doesn't
so.
If
I
have
to
fly
usually
customs
will
ask
me
for
my
passport.
I
can
disclose
that
to
them,
but
it's
not
under
control
of
another
priority,
like
the
previous
models
had
so
in
a
sense,
it
also
really
gives
back
control
over
your
identity
to
you.
C
So
we
call
you
the
holder,
and
if
I
go
to
customs,
they
verify
the
credential,
so
we
call
them
the
verifier.
Now
very
important
thing
is
it's
decentralized,
so
we
don't
have
vendor
lock
in
it's,
not
that
we
use
some
kind
of
service,
and
if
that
service
goes
down,
we
now
are
are
not
able
to
identify
ourselves
to
others,
it's
decentralized.
So
whatever
vendor
party
comes
and
goes,
which
should
be
okay,
ssi
or
self-sovereign.
C
Identity
is
based
on
open
standards
very
important
and
the
two
most
notable
ones
are
decentralized
amplifiers,
which
are
basically
you
can
view
them
sort
of,
as
as
as
urls
for
entities
for
things.
So
a
url
you
put
into
your
browser
takes
you
to
a
certain
document
online,
and
this
identifies
a
thing,
a
person,
an
animal
etc
and
the
most
important
one
I
think,
or
both
very
important,
but
very
interesting.
C
C
C
That
is,
that
is
written
down
in
the
in
the
credential.
Secondly,
I
can
be
pretty
sure
that
it's
issued
to
the
holder
so
to
the
person,
that's
giving
me
the
credential
and,
lastly,
that
that
person
didn't
alter
any
information,
because
you
can
imagine
if
somebody
gives
me
a
passport
and
they
they
alter
their
age.
Now
they
have
different
rights,
so
that
is
ssi
in
in
very
short,
there's
there's
lots
more
to
it,
but
we
are
trying
to
move
on
so
then
what
is
hyperledger
areas?
Well,
it's!
C
This
is
a
hyperledger
meetup.
So
most
of
you
know
what
hyperledger
is,
I
think,
but
hyperledger
areas
is,
is
a
is
the
identity,
decentralized
identity
project
under
the
whole
hyperledger
umbrella
and
it's
sort
of
is
part
of
what
I
call.
I
don't
know
if
that
is
an
official
term,
but
the
hyperledger
identity
stack
so
ssi,
sometimes
not
always,
but
usually
relies
on
a
blockchain,
and
the
blockchain
side
of
things
is
another
hyperledger
project
which
you
see
all
the
way
at
the
bottom.
C
C
Should
or
or
can,
can
work
and,
and
specifically
software
that
is
meant
to
handle
all
these
credentials.
So
it's
really
a
set
of
standards
you
can
use
and
follow
to
create
hyper
or
ssi
software,
because,
as
you
can
imagine
doing,
all
these
cryptographic
calculations
out
of
your
head
is
a
bit
a
bit
tedious.
C
So
we
need
software
for
that,
and
hyperledger
areas
defines
standards
to
create
that
software
all
the
way
on
the
left.
We
see
hyperledger
ursa,
which
probably
a
lot
of
you,
are
familiar
with.
It's
a
critical
library,
also
under
the
hyperledger
umbrella
and
both
hyperledger
areas
and
hybrid
gnd
rely
on
populator
ursa
for
their
crypto
stuff.
C
So
to
yeah
yep,
it
went
to
quickly
summarize.
So
what
is
hyperledger
areas
itself?
It
is
it's
a
it's.
It's
a
sweet
for
creating
self-serving
identity,
agents
and
agents
is
if
we
have
a
piece
of
software
that
does
self-solving
identity
interactions
for
us.
We
call
that
an
agent
and
it's
important
to
note
that
it
is
not
a
technical
implementation
itself.
C
It's
a
set
of
standards,
so
it's
a
set
of
rfcs
instead
set
of
protocols
that
are
written
down
and
they
can
be
used
to
create
technical
implementations,
and
there
are
various
technical
implementations
out
there
that
follow
these
standards
that
are
listed
below.
We
have
irish
club
agent
python,
which
is
a
which
is
a
server
that
can
be
used
to
which
exposes
a
rest
api.
You
can
call
to
perform
self-serving
identity
actions.
C
B
C
Yeah,
so
I
see
one
is
hi:
how
how
does
the
verifier
make
sure
the
credentials
are
legit?
So
that
is
for
me,
a
bit
a
bit
a
bit
too
much
to
explain
because
I'm
not
a
cryptographic
genius,
but
there
are
all
kinds
of
cryptographic
things
in
a
verifiable
credential,
so
you
usually
all
base
it
on
signatures
on
cryptographic.
Signatures
and
a
verifier
can
check
if
a
signature
was
made
by
a
certain
did,
in
this
case
the
issue
or
pid.
C
C
C
Yeah
recovery
is
is
still
of
credentials,
so
the
question
here
says
credentials
are
stored
somewhere
on
the
phone
or
wherever
on
a
server,
but
what,
if
you
lose
those
credentials
and
and
all
the
cryptographic
things
that
go
along
with
it?
This
is
a
difficult
question.
There
are
a
lot
of
projects
that
that
are
working
on
this
and
that's
try
to
solve
this,
but
indeed
right
now.
C
C
For
instance,
the
verifier
asked
me:
am
I
older
than
21
and
the
zero
knowledge
proof
is
a
way
to
to
basically
prove
that
without
disclosing
my
birthday
or
my
age,
so
they
basically
get
a
boolean.
That
says
yes,
no
and
they
are
able
to
trust
this
again
cryptographic
magic.
I
hope
that
answers
your
question
and
we
do
have
ace
a
credential
format
in
the
credential
format
or
unknown
threads,
that
that
does
support
that
cool.
C
I
will
now,
I
think,
go
on
just
for
the
sake
of
time
yeah,
so
those
I
pledge
alleys
now
we
are
here
obviously
to
talk
about
hyperledger,
aries
or
aries
framework
javascript,
which
is
again
the
javascript
implementation
of
hyperledger
aries
oops.
There
we
go
so
why
did
we
choose
this
framework
as
a
company,
as
opposed
to
all
the
other
ones
that
are
out
there,
and
that
has
mostly
to
do
with
our
mission,
which
I
mentioned
previously
at
the
beginning?
C
Non-Ssi
developers
have
to
be
able
to
understand
it
right
now.
It's
really
complex,
but
if
you
think
about
it
like
identity
is
in
is
everywhere
every
app
used
to
some
form
of
identity.
Most
websites
do
so
it's
everywhere,
and
the
developers
of
these
websites
are
not
it's
not
their
their
core,
their
core
business
to
to
do
identity
stuff.
So
they
don't.
C
They
don't
want
to
spend
a
half
a
year
or
more
to
learn
this
stuff
enable
to
be
able
to
use
it,
so
they
usually
fall
back
to
the
other
models
we
just
discussed
because
they're
just
easier.
We
think
it
has
to
be
easy.
We
we
have
to
make
sort
of
an
identity,
easy
at
least
as
easy
as
possible
for
it
to
really
to
really
become
something
and
javascript
is
among
or
the
most
popular
language
out
there.
I
think,
still
according
to
stack
up
overflow,
the
most
popular
one.
C
C
Secondly,
is
with
frameworks
or
solutions.
Like
react,
native
node.js,
you
can
use
javascript
on
multiple
platforms,
so
using
react
native.
We
can
write
ssi
solutions
for
for
mobile
apps,
so
both
android
and
ios,
but
you
can
use
that
same
framework
to
make
server-side
solutions
which
I
think
is
really
valuable.
You
don't
have
to
learn
three
frameworks
in
order
to
to
get
your
ssi
stuff
done.
C
Through
another,
but
it
started
with
every
framework
javascript
and
the
framework
and
things
around
it
have
gained
quite
some
traction
lately,
so
it
we
have
some
other
things
outside
of
the
framework
itself
that
emerged
and
as
you
can
see
in
the
particular
screen
here
is
in
blue.
We
have
the
framework
itself,
so
the
framework
contains
a
core
package
which
has
all
the
fun
the
ssi
functionality
you
need
in
order
to
create
connections
between
two
parties
to
exchange
credentials.
All
that
goodness,
then
we
have
two
packages
that
are
really
platform
specific.
C
So
we
have
a
react
native
package,
node.js
package
they
are
based.
They
basically
contain
all
the
dependencies
you
would
need,
depending
on
the
platform
you're
working
in.
So
if
you
are
going
to
make
a
react
native
app,
you
would
install
the
core
package
and
the
native
dependencies
package
the
same
for
node,
but
then
you
would
obviously
use
the
node
package
down
one
once
up
down
in
red.
We
have
the
aries
framework,
javascript
extensions,
it's
another
repository
and
that
basically
contains
stuff.
C
That
would
help
us
to
do
common
common
things,
not
so
common
that
they
belong
in
the
course
of
framework.
So,
for
instance,
if
you
want
to
have
a
rest
api
around
your
agent,
we
have
a
an
extension
you
can
plug
into
the
framework
that
gives
you
a
rest
api,
the
same
for,
if
you're,
creating
a
react
native
solution,
so
a
mobile
wallet
or
app
and
you'd
like
to
have
some
push
notification
support.
There
is
an
extension
for
that.
C
C
C
If
you
can
help
me
so
we
have
or
one
of
my
excuse
me-
lovely
colleagues,
made
a
a
demo
which
you
can.
If
you
want
to
follow
along
you
can
it
takes
the
set
it
takes?
It
takes
a
bit
of
time
because
you
need
to
download
the
wallet,
but
it's
basically
it's
a
website
that
you
can
use
to
get
a
credential
issue
to
you
and
then
present
that
credential
to
others.
It's
quite
trying
to
fix
some
technical
issues
here,
because
we're
trying
to
stream
my
phone
as
well.
C
C
All
right,
you
can
choose
a
character
and
a
character
has
a
little
bit
of
a
story
behind
it.
So
one
is
a
student.
When
is
the
it's
not
gonna
work
like
this,
then
I
have
to
just
show
it
in
the
camera,
which
is
terrible,
but
I
will
have
to
do
that
so,
okay,
the
streaming
of
my
phone
to
the
screen
doesn't
work.
So
forgive
us
please,
but
so
this
is
the
demo.
You
can
visit
yourself
or
do
it
later.
C
It's
demo.animo.id
and
first
thing
it
will
tell
us-
is
to
to
run
through
the
setup,
which
basically
means
to
do
this.
You
need,
you
need
a
phone
with
a
wallet
on
it
and
now
there
are
two
wallets
here:
they're,
both
not
made
by
us
one,
one
intrinsic
probably
a
familiar
company
and
the
other
is
lizzy
wallet
which
is
made
by
a
german
company.
C
C
C
It
will
issue
us
a
animal
id
card,
we
call
it,
but
it
basically
tries
to
simulate
a
base
credential
you
would
normally
get
from
the
government
or
something
that
states
your
name,
your
age,
for
instance.
Let
me
see
so.
The
first
thing
we
need
to
do
is
create
a
because
it's
pretty
beer.
I
have
my
phone
here.
C
C
Great
we
are
connected.
I
have
a
connection
with
animal
and
okay.
Now
it's
visible
here.
There
are
two.
I
have
two
little
modifications
saying
hey.
I
want
to
give
you
this
credential
these
credentials
in
this
case,
because
it's
another
use
case
kfs2
the
animal
id
card,
so
the
base
id
and
a
credit
card
we
can
use,
and
I
will
accept
them
both
and,
as
you
can
see
on
the
screen,
it
says
that
I
accepted
it
and
there
goes
the
other
one
boom.
C
So
I
both
in
my
wallet
now
I
can
go
on
to
the
next
step,
and
now
it
basically
gives
me
a
few
options.
So
a
few
routes
in
this
in
this
in
this
example-
and
it
also
lists
you'll-
be
asked
for
this
credential
this
credential
exponential.
In
this
case
I
will
just
take.
The
conference
example-
gives
me
a
little
overview
you're
connecting
with
this
sexual
company
or
or
organization.
C
C
C
I
would
like
to
have
two
pieces
of
information
from
you,
your
name
and
your
nationality.
So
I
can
now
say:
send
it's
fine
and,
as
you
can
see,
that
just
appeared
here
so
the
first
step
was
the
the
issuer.
Now
they
just
verified
us
and
now
they
this
this
conference
becomes
the
issue
of
another
pass
and
again
I
have
a
little
notification
and
I
can
accept
it
now.
C
There
are
more
and
more
and
more
way,
more
steps
in
this
demo
with
the
two,
but
for
the
sake
of
time
I
will
stop
here.
I'm
gonna
go
back
to
the
presentation
there.
Yes,
but,
as
you
can
see,
I
hope
this
just
gave
you
sort
of
an
introduction
on
how
this
looks.
So
in
this
case
the
app
was
not
built
because
we're
using
a
third-party
app.
C
This
was
not
built
with
a
streamer
javascript,
but
it
could
have
could
have
been
an
app
that
was
built
with
with
this
framework
and
the
the
the
website
you
saw
ran
the
framework,
so
it
was
built
with
nodejs
so
bearing
well
now
so
now
you
have
an
introduction
to
the
framework.
I
hope
you
have
an
idea
of
what
it
what
it
has
and
baron
will
now
go
over
the
current
state
of
the
framework
and
and
give
you
a
slight
look
of
the
roadmap
ahead.
A
A
We
do
already
support
some
features
of
aip2.,
which
includes
issue
credential
v2,
so
that's
the
improved
version
of
it.
This
allows
for
a
lot
more
credential
formats,
but
we
currently
only
support
the
indie
credential
format,
which
is
the
same
used
in
the
or
in
the
issue.
Credential
v1
protocol
we're
working
hard
with
everyone
in
the
afj
community
to
support
the
json
ld
credentials
defined
by
w3c,
but
that
is
coming
in
the
next
slide.
A
We
also
support
out
of
band
and
did
exchange
out
of
band
simply
means
here
is
that,
in
order
for
us
to
establish
a
secure
channel
between
two
agents
that
we
can
use
to
talk
to
each
other,
we
first
have
to
send
one
message
that
is
not
in
this
channel
to
establish
that
communication
channel
and
that
exchange
just
means
the
communication
between
the
two
agents
within
the
channel.
So
when
it
is
established
in
order
to
fully
test
the
aip
specs.
A
So
the
wonder
and
the
2.0
we
created
or,
as
in
the
aries
community,
created
the
aries
asian
test,
harness
which
is
a
quite
a
nice
test
harness
which
just
tests
all
the
framework
against
each
other.
So
this
basically
gives
us
a
way
to
check
the
interoperability
between
different
agents,
because
sometimes
you
can
implement
the
stack
spec
and
understand
it
in
the
different
way
implemented
incorrectly
and
then
you're
actually
not
completely
following
specification,
and
this
would
break
interrupt.
A
A
You
know
one
of
the
biggest
features
of
afj
is
that
it
simply
supports
the
rig
native
environment
and
the
node.js
environment.
This
would
mean
that
you
can
create
a
mobile
agent
like
bifold,
or
you
can
create
a
restful
api
like
we
used
in
the
demo
before
that
uses
that
is
running
in
the
node.js
environment.
This
really
makes
us
allows
us
to
capture
the
entire
ecosystem
of
software,
while
still
containing
in,
like
one
code
base
and
keeping
it
very
consistent
between
the
different
implementations.
A
A
This
is
also
something
that
we're
working
towards
to
not
only
be
interoperable
with
other
ares
agents,
but
with
any
kind
of
self-sovereign
identity,
a
agent
that
you
can
think
of
we're
also
working
on
percent
proof.
We
do.
This
includes
the
indie
credentials,
as
mentioned
before,
and
the
new
ld
proof
credentials
so
that
we
can
also
verify
them.
Ditkum
v2
is
also
required
for
this.
This
is
I'm
not
too
sure
on
the
details,
but
this
is
just
the
improved
version
of
the
com
v1,
with
some
benefits
and
generalization
outside
of
the
aap
2.0
spec.
A
We
also
want
to
just
improve
the
framework.
This
includes
multi-tenancy.
So
if
you
want
to,
for
example,
create
a
sas
platform,
so
software
as
a
service,
then
you
could
have
an
one
single
agent
instance
that
could
create
infinite
amount
of
wallets,
for
example,
for
people
that
want
to
use
this
platform.
A
We
also
found
that
the
afj
is
starting
to
become
quite
bulky
in
terms
of
dependencies
that
we
use,
for
example,
for
the
bbs
plus
credentials.
We
have
a
dependency
for
any.
We
have
a
separate
dependency
and
we
notice
that
not
every
implementation
needs
all
the
specific
dependencies
so
we're
trying
to
modularize
the
framework
so
that
you
can
basically
pick
and
choose
from
like
okay.
I
want
to
support
pbs
and
ld
proofs,
but
I
don't
want
indie
because
they're
mad,
because
I
don't
I
don't
want
to
have
any
specific
reason
what
you
want.
A
So
this
would
allow
us
to
a
bit
more
plug
and
play
framework
and
we're
also
looking
towards
integrating
with
more
blockchains.
This
would
include
like
the
checked
network,
for
example.
What
could
you
mention
before,
and
I
believe
some
party
is
working
on
fabric
support,
so
that
would
also
be
really
nice.
I
mean
there
are
tons
of
other
blockchains
that
we
would
like
to
integrate
with,
so
that
is
definitely
on
the
roadmap
to
just
make
it
at
support
for
as
many
as
possible.
A
C
C
Then
you
also
have
the
frameworks,
so
every
framework
obviously
is
built
a
little
differently
and
yeah.
One
of
the
things
we
struggled
with
a
lot
is
that
there
was
very
few
no
documentation
at
all
or
outdated
or
which
makes
it
very
difficult
for
people
to
get
started.
Basically
and
well
again,
the
whole
point
or
our
our
mission
is
to
to
to
drive
adoption
in
this
ecosystem.
So
definitely
solid.
Documentation
will
help
with
that.
C
We
have
also
seen
from
our
community,
and
that
has
grown
a
lot
lately
that
that
they
struggle
with
this.
You
have
to
dive
through
the
code,
which
is
not
always
the
best
way
or
to
get
started
really
fast.
So
indeed,
as
bern
mentioned
a
few
weeks
ago,
we
we
started
writing
documentation,
so
we
we
recently,
I
think,
yesterday
this
website
came
online,
which
is
basically
it
tries
to
to
be
a
sort
of
one-stop
shop
for
for
any
documentation.
C
You
might
need
on
not
just
a
framework,
but
anything
inside
of
the
inside,
of
the
ecosystem.
It
is
really
new,
really
incomplete,
so
we're
still
it's
still
under
heavy
development,
so
don't
expect
too
much,
but
the
whole
idea
behind
this
documentation
is
not
to
just
give.
You
know
api
talks,
not
like
okay.
Here,
you
have,
you
know
this
function
and
it
it
it
wants
these
these
parameters
in
these
arguments
now
we
want
to
really
put
it
in
a
more
of
a
hands-on
tutorial
way.
C
So
here
we
have
a
little
screenshot
of
issue.
Credential
visual
credential
is
a
use
case
that
a
lot
of
people
making
ssi
solutions
once
it's
something
that
is
quite
common
in
ssi
to
issue
a
credential.
So
we
tried
to
write
this
documentation
in
a
way
in
a
sort
of
tutorial
fashion.
So
this
is
what
you
need
to
get
set
up.
C
So
really
more
in
a
in
a
tutorial
uh-ish
way.
Don't
please
don't
look
at
the
callers
here,
they're
terrible,
we're
working
on
them,
but
now
the
colors
indicate
the
different
sides,
because
we
in
an
issue,
credential
interaction,
you
obviously
have
the
the
issuer
and
the
holder,
so
the
issuer
sends
a
credential
or
issues
a
credential
to
the
holder,
so
they
both
need
a
piece
of
software
and
that's
why
these
code
blocks
are
colored
differently
to
indicate
the
roles
but
yeah
again.
C
This
is
not
perfect
at
all
and
if
anyone
would
like
to
dive
into
the
afj
or
aries
javascript
ecosystem,
especially
beginners,
your
remarks
and
comments
are
more
than
welcome
because,
as
we
have
been
working
with
this
framework
for
for
about
three
three
years
now,
it's
it's
not
always
obvious.
What
is
not
obvious
to
people
who
are
starting
out.
C
A
A
Just
have
to
set
everything
up
correctly
and
yes,
we
can
go
so
right
here.
I
have
a
completely
empty
project.
Just
one
file
in
there,
which
is
an
agent
in
here,
is
just
some
simple,
boilerplate
functions
or
code,
which
is
not
really
that
important.
It
contains
the
genesis
transaction
of
the
ledger
that
we
want
to
connect
to
we're
setting
the
logs
on
because
we
want
to
you
know,
show
a
bit
more
of
what
the
framework
is
doing.
There's
an
agent
label.
A
A
This
is
the
ledger
that
we're
connecting
with
this
is
our
public
dead
seat,
and
this
on
this
seat
is
our
public
death
based?
You
can
use
it,
it
does
network.
So
there's
no
secrecy
here
and
we're
using
an
angry
tunnel
here
right
now,
because
we're
using
a
local
server.
So
we
have
to
expose
it
to
the
public
so
that
our
mobile
agent
can
connect
with
it
can
connect
with
it,
and
here
we're
just
registering
some
outbound
and
inbound
transports.
This
is
our
way
of
communicating.
A
B
A
A
A
Just
something
that
we
forgot
to
mention
so
right
here
in
the
index,
we
will
pull
in
the
get
agent
from
the
agents
file
in
here
we
will
create
a
simple
main
function
in
which
we
can
define
all
our
cool
codes
in
this
function.
First,
we
have
to
get
our
agent,
which
is
just
agent,
get
agents
with
a
label
which
will
be
a
hyper
ledger
issuer
demo.
A
Okay,
so
now
that
we
have
our
agent,
we
will
have
to
create
a
schema
on
the
ledger,
and
this
schema
basically
defines
how
our
credential
is
going
to
look
like
with
which
attributes,
so
we
can
create
it
like
this
schema
suite
agent
dot
ledger.
This
is
a
ledger,
interaction
and
we're
going
to
register
the
schema
in
here
we
can
specify
some
attributes.
A
So
here
we
have
the
credential
definition
and
chem
agents,
ledger
interaction,
so
credential
definition
in
here
we
have
to
pass
in
the
schema.
We
do
not
support
verification
right
now
or
we're
not
going
to
support
verification
for
this,
but
that's
where
you
would
put
it
if
you
support
replication
for
this
credential
definition.
A
After
this,
we
have
to
create
the
invitation
which
will
be
an
out
of
band
record
and
the
invitation,
and
it
will
be
done
on
agent.ob,
which
stands
for
out
event,
of
course,
and
we'll
create
a
legacy
invitation.
We're
creating
a
legacy
invitation
here
and
not
like
the
newest
invitation
is
because
our
wallet
that
we're
going
to
use
for
this
does
not
support
is
not
aip2
compliant.
So
we
have
to
use
the
old
connections
protocol
and
that's
why
we
also
have
a
separate
invitation
here.
A
A
A
A
A
A
A
A
A
Okay,
now
to
quickly
go
over
it
again,
we
created
the
schema.
We
created
the
credential
definition.
Then
we
created
a
connection
with
a
qr
code
to
communicate
with
mobile
agents.
We
get
the
connection
id
and
then
we
offer
a
credential
and
if
I
did
not
make
any
mistakes,
we
have
a
very
simple
issuer
service
now.
For
this
part,
I
have
to
take
my
terminal
to
a
very
small
font
size.
A
A
So
I'll
start
it
here's
some
debug
information
to
see,
that's
actually
doing
something.
It
just
registered
the
credential
definition
of
the
schema
and
there's
the
big
qr
code
is
now
trying
to
scan
it.
But
qr
codes
are
always
difficult,
yeah,
okay,
so
there's
a
connection
and
in
this
mess
of
logs
it
says
that
there
is
a
credential
issued.
Let's
see
if
I
can
yeah,
let's
see
if
we
can
show
it
actually
yeah
here,
it
says,
offer
message
successfully
created
and
we've
offered
a
credential.
C
C
A
A
C
B
A
A
Of
course
teemo,
but
yeah
right
now,
we're
mainly
focused
on
the
area
specifications.
So
I
can't
myself
really
give
a
concrete
comparison
to
other
frameworks.
We
are
definitely
trying
to
move
more
towards
being
interoperable
with
them
and
creating
less
of
a
difference
between
them.
So
for
me
at
least
it's
very
difficult
to
say
what
the
comparison
is.
Maybe
getting
us
something.
C
C
How
how
which
messages,
what
what
do
those
messages
contain,
et
cetera,
et
cetera?
How
is
a
credential
structured,
everybody
can
think
of
their
own
their
own
structure,
but
that
wouldn't
work
because
we're
not
interoperable
and
so
aries
sort
of
is
a.
I
guess,
an
umbrella
of
of
these
standards,
and
I
guess
other
frameworks
implement
their
own
standards
outside
of
the
area's
ecosystem
or
in
the
in
the
ares
ecosystem,
because
they're
kind
of
tightly
coupled
a
lot
of
people
are
relying
on
w3c
verifiable
credentials.
C
So
I
think
that
that
that's
the
big
difference
we
follow
mostly
or
we
have
followed
mostly
every
standard
and
are
now
moving
towards
w3st
standards
to
also
incorporate
those
and
other
other
solutions
have
their
own
have
their
own
standards.
What
I
think
is
good
about
aries
is
that
there
are
multiple
implementations
that
all
follow
the
same
standards.
B
Yeah,
I
have
a
question
for
you
just
around
the
walls
that
you
showed
earlier.
If
I
saw
that
you
know
you
had
friendship
wallet
and
then
you
had
another
wallet
that
was
from
germany
yeah.
So
is
there
any
one
that
you
prefer
and
if
there's
one
that
you
prefer?
Why
is
that,
and
you
know,
are
both
of
them
active
and
engaged
with
the
aries
community.
C
So
well
I
mean
they
are
interoperable
with
our
demo,
so
yeah
they
are
at
forensic,
especially
they
I
think
they
built
the
majority
of
the
net
framework.
There
is
net
framework,
so
that
is
built.
On
top
of
of
that,
I
believe
it's
xamarin
app
lizzie.
I'm
not
I'm
not
too
sure
what
they,
what
what
it's,
what
they
used
to,
build
it,
but
definitely
yeah
they
are
interoperable.
C
C
That
are
that
if
everybody
follows
or
implements
the
same
compliant
with
the
same
profile,
then
then
it
should
be
okay
to
then
you
should
be
interoperable
if,
but
but,
but
as
with
standards,
always
not
everybody
does
it
exactly
how
it
should
should
have
been
done.
So
so
sometimes
you
I
you
know,
there's
a
little
bit
difference
like
hey.
Okay,
when
I'm
issuing
a
credential,
it
works
and
connections
work,
but
presenting
a
proof
there's
a
little.
B
C
Definitely,
as
someone
I
know
well
from
the
aries
community,
he
works
a
lot
on
bifold.
So
iris
by
fault
is
a
I
think,
little
over
almost
one
and
a
half
years
old.
I
think,
and
it's
a
it's
a
it's
an
open
source,
maybe
parent!
You
can
look
for
the
link
and
post
it
in
the
chat.
It's
it's
well.
Bifold
was
sort
of
the
old
name.
Now
the
repository
is
called
aries.
C
Mobile
agent
react
native,
which
also
was
in
one
of
the
slides,
and
that
is
an
open
source
wallet
completely
open
sourced
built
on
afj,
so
it
uses.
Fj
only
relies
on
afj
for
for
ssi
stuff
and
the
cool
thing
is
it's
a
it's
a
white
label
app,
so
it
it's
not
tied
to
any
company
itself,
but
you
can
just
clone
it.
C
You
can
customize
it
and
you
can
make
your
own
wallet
if
you
wanted
to
and
we're
trying
or
the
the
by
fault
community
is
trying
to
make
it
more
customizable
every
day.
So
I
believe
now
we
have
it's
possible
to
provide
your
own
team,
so
it
would
be
a
little
bit
stupid
if
everybody
using
this
project
that
they're
have
exactly
the
same.
The
same
wallet
with
exactly
the
same,
look
and
feel
so
bifur
can
be
used
to.
B
Okay,
one
of
the
things
I
just
want
to
touch
base
on
here
with
everyone
is
just
after
we
wrap
up
this
nice
workshop
here.
Anyone
who
wants
to
engage
with
the
aries
javascript
team
definitely
go
back
on
the
discord
and
really
get
involved,
and
I
think
they're
always
looking
for
new
maintainers
and
people
to
help
the
project.
So
if
you're
interested
definitely
reach
out
to
them,
they
posted
their
emails
here
and
definitely
go
onto
discord.
B
B
C
Yeah,
I
mean
there's
always
a
lot
of
work
to
do
so.
We
have
been
working
lately
on
getting
into
aip2,
which
is
which
is
easier,
said
than
done,
and
there's
quite
a
lot
of
work
involved
in
that
so
definitely
developers
who
want
to
to
to
contribute,
but
also,
as
I
mentioned
earlier,
we
are
trying
to
make
this
thing,
as
is
usable
and
and
easy
for,
for
people
outside
of
the
ssi
community.
C
So
we
have
this
documentation
stuff
and
we
we
really
especially
people
like
we're
coming
into
this
space,
who
don't
know
everything
and
I
think
it's
very
valuable
to
to
one-
have
comments
on
the
documentation.
That
is
there,
but
it's
also.
I
think
it's
also
great
if
people
who
are
learning
and
who
are
discovering
this
works
like
this.
This
this.
C
This
works
like
that,
our
our
these
people
are
also
able
to
to
contribute
because
they
are
able
to
to
to
digest
and
this
stuff
and
and
and
probably
able
to
put
it
into
simple
terms
which
which
becomes
a
bit
more
difficult.
If
you,
if
you've
been
in
this
space
for
a
while,
so
definitely
that
I
think
documentation,
but
also
what
is
the
extension
repository,
we
have
it's
basically
a
place
for
anything
that
is
not
really
hardcore
ssi
itself,
but
is
something
that
is
interesting
to
other
people.
C
So
so,
let's
say
this
notification,
this
push
notification
extension
a
lot
of
people
building
wallets
mobile
wallets,
probably
won't
push
notifications,
so
also
in
that
regard,
if
you
have
a
nice
idea-
or
you
think
that
I
would
like
to
build
this,
you
can
definitely
contribute
on
that
side.
I
hope
I'm
answering
the
right
question,
but
yeah
no
more
help
is
always
welcome.
C
Regarding
the
framework
itself,
we
have
a
weekly
call
on
on
thursdays,
so
today
there
was
one
which,
if
you're,
coming
into
this
and
you'd
like
to
introduce
yourself
or
or
ask
questions
you
can
always
do
that.
I
don't
know
the
exact
times
in
all
the
times
it
don't,
but
we
can
post
a
link
to
it
to
it
later
so
yeah
contributions
are
definitely
welcome.
C
B
A
A
It's
mainly
been
bundled
in
bundled
braking
changes,
so
we
don't
like
push
braking
changes
all
the
time
and
bundle
features.
So
you
know
once
you
go
one
up,
you
get
a
good
amount
of
features.
Maybe
timo
can,
if
he's
here
at
least
come
post
a
chat
yeah
there
we
go
exactly
so
that
is
a
guide
for
updating
the
agents
to.
A
You
have
to
check
if
that
public,
the
id
is
actually
registered
by
a
an
issuer
that
you
trust
so,
for
example,
our
government
here
in
the
netherlands,
they
would
register
their
public
bid
and
they
would
be
able
to
issue
me
a
driver's
license.
And
then,
if
my
co-worker
kareem
would
issue
me,
they
would
use
different
public
vids
and
therefore
you
would
not
trust
the
one
that
kareem
issued
me.
Of
course,.
C
So,
just
to
go
on
on
that
a
little
bit
like,
I
think,
there's
a
there's,
there's
quite
a
good
comment
on
this.
It's
it's
not
something
that
is
solved
by
by
a
a
framework
or
whatever
I
mean
you're,
not
gonna.
This
is
this
is,
of
course,
this
is
mainly,
I
guess,
a
blockchain
community,
but
you're,
not
an
identity.
You're
not
gonna,
get
to
a
trustless
scenario
and
that's
fine.
C
You
do
take
away
a
bit
of
trust,
though,
like
as
a
holder,
if
I
receive
the
credential
from
an
issuer,
it
doesn't
really
matter.
If
I
trust
that
issue
or
yes
or
no,
I
get
a
credential,
I
can
see
what's
inside
it
and
if
he
gave
me
like,
if
he
said
my
name
is
baiden,
which
is
not
like.
Remember,
that's
him
and
I'm
covering
and
then
I'll
just
throw
that
credential
away
it.
C
It
does
take
away
the
for
a
good
part,
the
the
trust
that
is
needed
between
the
holder
and
the
verifier.
Like
you,
don't
have
to
trust
this
document
now
you
can
actually
verify
it
cryptographically,
which
is
a
good
thing,
but
then-
and
this
is
something
you
will-
I
guess
always
have-
is
there's
always
a
trust
relationship
between
a
verifier
and
the
insurer.
C
If
it's
issued
by
the
by
by,
in
my
case,
the
dutch
government
customs
will
probably
trust
that
credential
because
they
have
the
trust
relationship.
There
is
there's
a
trust
relationship
between
the
customs
so
and
and
the
dutch
government,
if
I
present
the
credential
that
was
given
to
me
by
by
their
end
customs,
will
probably
be
like
yeah.
I
don't
know
so.
C
C
C
C
A
Yeah
the
test
net
from
bc
governing,
which
is
always
quite
stable,
and
they
clean
it
up,
sometimes
maybe
once
per
month
or
something
but
yeah
you
can
with
the
in
the
sdk
guides,
you
can
set
up
a
local
network
relatively
easily
with
docker
as
well,
but
for
this
demo
we
didn't
we
just
then
we
would
also
have
the
wallet
to
support
the
local
ledger.
So
we
just
chose
for
bc
government
because
they
always
have
quite
quite
stable
networks.
C
C
I
believe,
with
with
the
genesis
transaction
right,
you
did
it
in
the
example
you
can
connect
to
it
and
and
and
then
you
are
free
to
to
to
upload
the
schema
just
like
he
did,
and
the
credential
definition
as
well
yeah
by
the
way
beer
and
somebody
asked
like
or
multiple
people
asked
if
we
could
put
this
code
in
a
repo,
so
they
can
follow
along
later.
I
think
that's
a
that's
a
good
idea.
C
C
If
you
wanna
wanna
wanna,
try
this
out
for
yourself
definitely
try
the
demo
again.
I
will
can
you
post
the
the
url?
It's
just
just
it's
a
public.
It's
a
public
website.
You
can,
you
can
try
it
at
home.
It
will
guide
you
through
downloading
a
wallet
and
you
can
run
through
through
all
the
use
cases
just
to
get
a
to
get
a
feel
of
it
yeah.
Indeed,
thank
you
all
for
listening
for
being
here.
One
last
call
for
questions.
I
guess
and
if
not,
then
we'll
wrap
it
up.
B
Okay.
Well,
gentlemen:
you
did
a
wonderful
job
on
this
presentation.
I
really
appreciate
it
looks
like
we've
come
to
the
end
and
please
go
out
to
the
hyperledger
youtube
channel
if
you'd
like
to
watch
any
other
portion
of
this
video
or
any
other
videos
on
hyperledger
that
would
be
relevant
to
the
aries
network
so
have
a
great
day,
everyone
and
we'll
catch
up
on
the
next
workshop
that
we
go
through
take
care.