►
Description
In this session, Ariel Gentile, Berend Sliedrecht and Karim Stekelenburg will share the 0.4.0 release of Aries Framework JavaScript. The demo will include what's new in AFJ and through the lens of a well-defined use case, they will lead you through the steps of setting up an agent, connecting it to a ledger, and issuing and verifying credentials. By the end, you will be able to use your own cloud agent to issue a credential to a holder, which in turn creates a proof of a credential that your cloud agent can verify. This demo is aimed at everyone that has worked with JavaScript/TypeScript in the past. Specific knowledge with Aries Framework JavaScript or self-sovereign identity is not required.
For more information about the Aries Framework JavaScript 0.4.0 release, check out the blog post at:
https://www.hyperledger.org/blog/2023/07/06/introducing-hyperledger-aries-framework-javascript-0-4-0
For any questions about the workshop, feel free to ask in the #aries-javascript channel on Hyperledger's Discord server. Details on how to join Hyperledger's Discord server are at:
https://chat.hyperledger.org/
----
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
Welcome
everybody
to
the
hyperledger
foundation,
Workshop
hyperledger,
Aries
framework,
JavaScript
0.4.0,
release
setting
up
an
agent
and
issuing
credentials.
Thank
you
all
for
joining
us.
This
session
is
being
recorded.
It
is
going
to
be
and
it
is
being
live
streamed
on
the
hyperledger
YouTube
channel,
I'm
gonna
post
some
links
in
a
second
in
the
chat
once
we
kick
this
off,
but
I
want
to
thank
everybody
for
joining
us
as
with
all
Linux
Foundation
meetings.
This
is
held
under
the
Linux
Foundation
Anti-Trust
policy.
B
If
you
have
any
questions
about
these
matters,
please
contact
your
company
Council
or,
if
you're,
a
member
of
the
Linux
Foundation,
feel
free
to
contact
Andrew
updegrove
of
the
firm
gesmer
up
the
Grove
LLP
I
would
really
like
to
thank
the
three
organizers
of
this
Workshop
Ariel
Karim.
Oh,
come
on
Ariel
Kareem
and
baron.
B
All
of
hyperledger
is
powered
by
contributors
and
maintainers
and
users
of
this
software.
If,
if
these
folks
didn't
exist,
we
wouldn't
exist,
and
we
cannot
thank
them
enough
for
sharing
their
knowledge
and,
quite
frankly,
all
the
hard
work
they've
put
into
Aries
framework
JavaScript
just
in
general,
but
also
to
get
us
to
the
0.4
point
Zero
release
and
with
that
I'm
going
to
stop
sharing
and
turn
it
over
to
Kareem
and
I'm,
going
to
start
putting
some
links
into
chat
Kareem.
It's
all
yours.
A
A
Let
me
see
if
this
works
nope
that
didn't
work
so
but
overview
of
what
we're
gonna
do.
I'll
start
off
with
a
well
a
small
introduction
as
this
as
this
is
about
the
zero
four
zero
release.
Specifically,
we
will
have
an
overview
of
the
release
where,
after
we
will
appearance
will
show
you
a
little
demo
that
he
has
prepared.
A
After
that,
it
will
show
you
a
few
code.
Examples
like
how
does
it
actually
look
to
work
with
the
zero
four
zero
release?
We'll
have
a
strong
look
at
the
documentation,
I
look
ahead.
What
is
on
the
roadmap?
And
what's
next
and
at
the
end
we
will
have
a
question
and
answer
session,
which
we
did
this
last
year,
a
similar
session
for
the
zero
three
zero
release,
and
there
was
a
lot
of
there
were
a
lot
of
questions
and
we
had
to
cut
it
short.
A
So
we
expect
to
to
have
some
or
to
to
spend
quite
some
time
on
the
on
the
on
the
question
answering
session.
So
we
can
answer
all
the
questions
you
might
have.
So,
first
of
all,
introduction,
hyperledger
I
believe
well,
a
global
hyperledger
Meetup
I
want
to
quickly
touch
on
what
hyperledger
every
framework
JavaScript
is
what
it
isn't.
A
Oh
sorry,
I
see
that
I
don't
have
my
camera
on
open
now,
so
yeah,
a
quick
introduction
on
what
hyper
major
areas
from
a
JavaScript
is
I
will
not
go
into
the
details
of
self-driven
identity
and
all
the
well
yeah
all
the
things
and
Concepts
around
that.
If
you
are
interested
in
that,
then
I
encourage
you
to
to
look
up
the
the
previous
session.
We
did
on
the
zero
three
zero
release,
because
that
goes
more
in
depth
into
what
serving
identity
is
in
general.
A
But
this
is
really
worth
specific
to
the
zero
four
zero
release.
So,
let's
summarize
to
quickly
go
over
it
average
framework
JavaScript
is
a
it's
a
framework
for
implementing
self-solving
or
decentralized
identity.
Solutions
I
use
both
terms
because
I
think
decentralized.
Identity
is
the
more
popular
term.
Nowadays,
it
is
based
on
hyperledger
area
standards,
which
is
a
collection
of
rsvs
or
standards
that
are
implemented
in
multiple
languages.
A
You
also
have
Aries
Cloud
agent
python,
for
instance,
and
but
this
obviously
is
the
JavaScript
version
of
it
and
which
will
be
done
a
little
bit
more
relevance,
a
few
slides
ahead,
but
I
pledge
it.
Aries
was
born
in
the
hyperledger
in
the
project
originally
so
because
it's
a
a
JavaScript
framework,
the
cool
thing,
I
think
what
is
cool
about
it
is
that
it's
a
it's
a
multi-platform
solution.
A
So
that
means
basically,
you
can
run
on
the
server
side
through
node.js
and
also
on
mobile
devices.
If
you
use
react
native
yep,
so
this
is
the
typical
again
I'm
not
going
to
go
into
the
details
of
it,
but
this
is
a
typical
SSI
diagram.
You
I'm
sure
you
have
seen
if
you
are
someone
familiar
with
SSI,
they
have
indeed
SSI
which
self-service
identity
in
the
entire
ecosystem.
You
have
usually
have
three
rules,
so
you
have
a
holder,
someone
who
receives
credentials,
a
verifiable
credential.
A
You
have
an
issue
where
someone
who
issues
them
and
a
verifier
for
this
interested
in
verifying
it.
And
additionally,
you
see
it's
well
sort
of
middle
in
the
middle,
the
bottom
middle
I
guess
the
verifiable
data
registry,
and
that
is
often
a
blockchain,
but
it
doesn't
have
to
be
it
has
to
be
a
blockchain
per
se
and,
as
I
mentioned
on
the
previous
slide,
it
is
a
multi-platform
system
and
the
cool
thing
about
that
is
is
that
it
can
well
yeah
it
can
help.
A
You
create
solutions
for
all
these
roles
right,
because
a
holder
in
a
lot
of
cases
has
a
wallet,
a
mobile
application.
So
for
that
you
would
use
react
native,
but
in
issue
we're
going
to
verifier
often
run
some
kind
of
server
architecture.
But
then
again
you
can
use
the
node.js
runtime
for
for
those
kind
of
solutions,
so
it
really
covers
all
of
these
things
and
by
we
really
do
our
best
to
keep
to
well
the
features
that
we
Implement
to
make
sure
that
they
run
on
all
platforms.
A
So
if
you
use
every
firmware
JavaScript,
which
will
I
will,
by
the
way
abbreviate
by
afj
a
lot
in
this
presentation.
But
if
you
use
afj
for
for
well
your
holder
or
your
issuer
and
your
verifier,
then
you
should
be
well
yeah.
They
should
be
interruptable
automatically
because
it's
the
same
framework
and
next
yeah.
So
let's
go
over
the
release
overview
and
the
the
most
primary
thing
is
modularization.
A
That
is
with
a
lot
of
work
in
making
the
framework
more
modular
and
that
work
already
started
before
so
in
the
zero
I
believe
zero,
two
zero
everything
was
one
big
package
and
in
the
zero
three
zero
release.
We
already
started
like
well
implementing
new
features
in
different
different
packages,
different
modules.
A
As
you
can
see,
we
have
extended
that
work
quite
drastically
in
industry
of
for
the
release,
so
I
will
quickly
go
over
go
over
a
few
of
these
components
and
not
all
of
them,
because
they
are
not
all
that
relevant.
But
on
the
left
you
see
in
blue
the
core
and
the
core
is
just
well
as
it
says
the
core
it's
a
framework.
It
is
everything
you
need
to
run
a.
A
They
want
to
run
the
framework
below
that
uc2
direct
native
package
and
the
node
package
to
the
two
and
gray.
Those
are
basically
the
dependencies
you
would
need
for
each
platform.
So
if
you're
running
or
if
you're
creating
a
mobile
application,
you
would
you
would
use
the
react
native
dependency,
the
react
native
package
and
if
you
are
running
a
server-side
application,
then
you
would
use
the
node
one
next
whoops
so
I
mean
this
is
this
is
just
a
copy
of
the
of
the
the
right
side
of
the
previous
slide.
A
A
So
for
those
who
don't
know,
as
I
previously
mentioned,
indie
or
Aries
was
born
in
the
Indian
ecosystem
and
in
the
is
a
well
right
now,
I
would
say
it's
a
it's
a
ledger:
a
identity,
specific
Ledger
under
the
hyperledger
umbrella,
but
they
realized
the
maintenance
of
the
ND
realized.
At
some
point,
hey
we
need
just
the
blockchain
is
not
enough
right.
A
We
also
need
software
standards,
protocols
for
agents,
so
the
well
the
issuers,
the
holders,
the
verifiers
they
need
to
exchange
information,
they
need
to
exchange
credentials
and
we
need
protocols
and
specifications
for
that.
So,
along
with
Indie
and
I
should
say,
Indie
node,
which
is
a
separate
software
components
they
created.
Indeed,
in
the
SDK
and.
C
A
A
But
initially
it
also
does
it
also
takes
care
of
storage,
so
the
credentials
and
and
other
well
related
data
objects
and
models.
They
are
stored
encrypted,
and
that
is
also
something
that
DND
s2k
did
for
you.
So
it
basically
also
provided
Secure
Storage.
It's
it
provided
cryptographic,
yeah
functionality
that
we
needed
under
the
hoods.
It
would
call
Ursa,
which
is
another
hyperledger
project,
and
it
also
took
care
of
a
lot
of
Uno
credits,
related
functionality
and
Arnold.
A
A
lot
has
happened
in
the
meantime,
among
credits,
the
animal
crit
credential
format,
so
the
in
the
credential
format
would
appears
to
be
ability
in
the
financial
format
that
got
sort
of
separated
from
the
whole
Indie
stack
and
has
been
renamed
to
announce
and
now
is
really
a
standalone,
credential
format
standard
and
in
the
meantime
we
have-
and
there
was
already
the
case
in
the
conservative
three
zero
release.
I
believe
we've
added
support
for
other
credential
formats,
like
the
the
famous
w3c
credential
formats,
and
we
have.
A
We
have
added
support
for
Json
LD
back
then
so
a
lot
of
movement
here
and
as
a
result
of
Indie
being
this
one
giant
rust
dependency.
That
does
everything
basically
and
the
result
of
that
is
that
if
you
would
have
used
every
framework
JavaScript
you
just
issue
and
and
or
verify
or
hold
or
whatever,
but
specifically
w3c
Json
LD
credentials.
Well,
yeah,
you
need
it
in
the
SDK
to
store
stuff.
So
you
would
automatically
also
include
the
logic
that
is
related
to
communicated
to
an
indie
Network.
A
Well,
maybe
you
do
not
communicate
with
Mindy
Network
at
all.
You
would
also
need
to
include
autocrats
the
logic
related
to
the
battlecreds
credential
format,
while
you
well,
you
might
not
use
that
because
you
are
just
focusing
on
the
w3c
Jason
obey
format,
so
yeah
you're,
basically
pulling
in
a
lot
of
codes.
You're
making
your
package
not
bigger
than
is
necessary,
and
this
is
yeah.
A
That
was
not
something
we
wanted
to
continue
with
next
slide,
please
yeah,
and
so-
and
this
is
not
an
effort
that
is
totally
or
not
even
mostly
done
by
us,
but
the
Irish
Community.
They.
They
chose
to
basically
introduce
three
new
components:
Aries
Oscar,
individr
and
anodegrads,
and
these
three
components
together
can
be
used
basically
as
a
replacement
for
the
ND
SDK.
So
they
take
care
of
they
each
take
care
of
a
subset
of
what
the
nsdk
is
to
do
now.
A
There
are
some
other
differences
there,
which
I
don't
I'm
not
going
to
go
into,
because
that
is
beyond
scope
of
this
presentation.
But
so
we
have
a
new
component
that
is
in
the
Oscar,
which
takes
care
of
storage
and
cryptography.
Then
we
have
ndvdr,
which
is
infinia,
is
verifiable
data
registry.
So
it's
really
the
component
that
takes
care
of
The
Ledger
communication
and
we
have
the
Anno
grades
package,
which
is
again
it's
it's
the
standard
itself,
the
credential
format
itself.
So
it's
a
package
that
takes
care
of
everything
surrounding
that.
C
C
So
if
you
look
at
the
the
zero
three
zero,
we
will
have
the
in
the
core,
the
functionality
related
to
Indie
and
and
Ledger
that
has
been
moved
out
and
extract
it
out
and
and
went
to
to
the
unknown
credits
and
and
the
ndsdk
library
so
module.
So
if
you
want
to
build
an
equivalent
agent,
I
mean
with
an
exact
same
features,
but
with
zero
four
zero.
C
You
will
need
to
use
in
your
project
the
the
core
and
also
the
unknown
credits,
which
is
the
which
is
a
a
module
that
adds
the
main
functionality
and
the
credential
format
and
and
the
the
interfaces
products
and
the
in
the
SDK.
That
provides
the
implementation
that
Karim
mentioned
before
about
the
the
Secure
Storage,
the
lecture
connection
and
and
the
cryptography.
C
So
in
this
case
we
will,
we
will
need
to
use
five
different
packages,
the
core,
the
anoncrest
unencrypts,
arrays
Oscar
and
in
the
vdr.
What
will
be
the
difference
between
both
actually
I
will
say
that
it
will
be
better
to
use
the
the
new
one.
I
mean
the
the
one
under
on
the
right,
because
the
the
new
unencrest
libraries
are
a
bit
faster
are
more
flexible.
C
You
can
add,
also
support
for
other
lectures
if
you
want-
and
you
can-
and
especially
because
it
also
supports
the
fully
support
the
the
new
and
credits
specification,
something
that
we
will
talk
a
little
bit
later
right
by
the
way.
If
you,
if
you
look
at
the
core,
you
will
see
that
there
are
still
a
lot
of
sub
modules
right.
C
C
By
the
ascar
package,
but
it
there
is
room
to
also
provide
a
different
one.
You
can
also
Implement
your
own
wallet
as
long
as
it
complies
with
the
wallet
interface
that
basically
needs
to
to
implement
some
methods
for
opening
a
wallet,
closing
VidCon
message
packing
if
needed,
storage
and
and
so
on,
and
that
give
us
the
possibility
of
in
our
near
future.
C
So
we
will
talk
about
that
later
in
the
by
the
end
of
the
of
this
session.
So
we
can
continue
in
the
slides
yeah
there
are.
There
are
a
few
more
differences,
also
as
a
consequence
of
of
removing
this
dependency
on
on
credits
and
in
the
SDK
was
that
previously
we
had
some
some
properties
on
the
Asian
configuration
like
this
public.
The
IDC
is
on
public
did
was
used
mainly
for
Indie
to
to
create
the
objects
and
The
Ledger
and
that
stuff,
and
now
we
are
not
using
that
anymore.
C
C
C
A
Yeah
so
the
next
section
about
Beyond
areas
as
it
is,
as
it's
called
so
as
you
might
have
seen
in
the
beginning,
somewhere
in
components,
we
have
started
work
for
implementing
protocols
that
are
outside
of
the
typical
Aries
ecosystems.
In
other
words,
as
I
mentioned
earlier,
Aries
is
comprised
of
a
set
of
various
rfcs,
but
the
space
is
evolving.
A
Recently.
This
year,
both
the
European
commission
and
the
Department
of
Homeland
Security
have
announced
weather
preferences
or
they've
hinted
on
the
standards
they
will.
They
will.
They
will
start
to
adopt.
Nothing
is
in
a
stone
yet,
but
they
are
yeah
they're
looking
at
a
certain
set
of
standards
and
they
are
not
all
Aries
related.
A
A
So,
for
instance,
the
credential
formats
that
they
will
use
are
MDOC,
which
is
an
ISO
standard
for
proximity,
flows
and
w3c
verifiable
credentials,
and
then
the
SD
jwp
variant
of
that
for
for
for
remote
flows,
and
that
is
for
the
financial
format
itself.
But
then
we
also
have
exchange
protocols.
So
in
the
areas
exists,
we
use
didcom
mainly
to
well
to
did
come
as
a
as
a
mechanism
to
to
issue
credentials
to
present
proof
and
to
do
a
variety
of
other
things
as
well.
A
But
the
European
commission
has
chosen
to
to
focus
on
the
well
the
bits
bit:
newer,
open,
ID
for
verifiable
credentials,
stack
so
on
the
left
top
left.
You
can
see
that
they
for
issuance
have
the
open
ID
for
verifiable
credential
issuance
protocol
and
for
for
the
verification
side
of
things
it
is
open,
ID
for
a
verifiable
presentations
and
sky
on
three
two.
A
The
second
point
is
a
little
bit
cut
off
of
forgive
me
for
that,
but
when
I
was
intended
to
say,
there's
a
relevance
outside
of
well
yeah,
let's
say
Geographic
areas
where
Aries
is
the
choice.
I
know
Canada,
for
instance,
really
really
goes
for
the
for
animal
credits,
for
instance,
but
again
EU
other
other
choices
are
being
made,
so
this
yeah
extending
this
report
to
other
ecosystems,
makes
it
relevant
also,
for
instance,
for
in
Europe,
but
this
all
this
modularization
and
and
adopting
understandings.
A
If
they
become
more
relevant
and
in
interesting
feature
of
this
is,
and
one
is
already
possible,
is
it
could
and
how
feasible
that
is
if
I'm
I'm
I
don't
want
to
make
make
a
judgment
about
that,
but
it
could
facilitate
interoperability
between
different
ecosystems
and
stacks
Etc
so
and
a
example
of
that
is
which
you
could
do
now.
I
have
not
done
it
yet,
but
in
theory
you
could
get
a
credential
issued
over
open
ID
for
clarifiable
credential
issues
and
then
present
proof
that
prudentialover
did
come.
A
C
C
C
So
yeah
we
are
going
to
talk
a
little
bit
more
about
the
or
more
in
details
about
the
lecture
Diagnostic
and
on
credits,
which
does
is
not
something
religious.
But
it's
about
how
these,
how
these
the
Hindi
credential
format
was
evolved,
especially
last
year
when
they
became
a
standalone
project
because
we
did
the
community
so
that
there
was.
There
was
a
lot
of
value
in
the
atom
credits
specification
in
format,
let's
say
because
of
the
the
unique
properties
that
has
this
kind
of
format.
C
But
the
issue
for
implementers
was
that
it
was
highly
tied
to
the
in
The
Ledger,
which
was
something
that
was
not
very
appropriate
for
every
case.
So
the
community
started
this
this
Standalone
project,
where
the
idea
was
to
standardize
the
specification,
because
at
that
moment
it
was
just
a
part
of
the
in
the
in
the
SDK
code
and
and
was
almost
nothing
was
formally
specified.
C
That's
called
the
anocrats
arrays,
which
has
some
wrappers
for
Python
and
JavaScript
and
of
course
we
have
implemented
our
package
on
based
on
these
wrappers.
Actually,
we
developed
the
routers,
but
that's
another
story.
I
will
say
that
I
can
probably
say
that
afj
fully
supports.
These
are
great
specification.
Sorry,
if
there
are
some
people
from
akapai
Community,
but
as
far
as
I
know,
AFC
is
the
only
framework
that
fully
supports
these
new
libraries,
but
I
put
this
star
there
in
the
fully
because
we
don't.
C
C
We
have
specific
cryptography
and
also
to
connecting
to
the
to
the
appropriate
lectures
to
to
get
and
create
the
the
objects.
So
the
idea
is
that
we
we
have
foreign
for
an
agent
to
work.
There
should
be
a
module
that
implements
these
these
services
for
for
holder
for
issuer
for
verifier,
and
at
least
one
module.
That
ads
are
what
we
call
the
registry,
which
is
actually
it's
a
it's
an
interface
to
the
actual
to
to
a
given
video.
So
the
idea
is
that
we
can.
C
We
can
register
one
or
more
Registries
in
order
to
support
one
or
more
lectures,
it's
more.
Something
like
it's
something
analogous
to
what
we
have
in.
In
the
in
the
Deeds
we
can
support
different
methods,
so
we
can
register
different
resolvers
and
registers,
and
in
this
case
we
we
can
support
different
kind
of
of
bdrs.
C
C
C
C
So
we
support
the
in
the
did
method,
which
works
with
both
Legacy
and
indeeds,
and
also
with
a
new
in
the
did
in
the
method,
and
they
checked,
as
I
mentioned,
that
was
contributed
by
the
check
team,
which
is
which
was
a
major
contributor
on
in
in
all
these
stuff,
about
making
an
upgrades.
Let's
see
agnostic,
so
yeah
we
can
maybe
continue
quite
a
bit
more
so
yeah.
The
idea
is
that
if
you
want
to
add
to
add
some
more
some
more
support
for
other
vdr,
it's
quite
simple.
C
C
So
there
are
a
few
methods
already
supported
or
in
or
in
development,
on
the
development
by
the
community,
which
are
the
cardano
made
by
Roots
ID,
and
they
did
web
support
that
we
are
using,
which
allows
to
store
and
manage
and
on
credits
without
the
need
of
using
any
blockchain
at
all.
So
we
can
put
them
directly
in
our
in
any
web
server
and
just
use
the
the
Island
grades
Library.
So,
for
instance,
in
our
case,
in
our
application
we
are
not
using
individr.
We
are
just
using
an
uncreates
arrays.
D
D
It
is
built
for
a
Dutch
project
which
tries
to
create
a
minimal
set
of
requirements
as
like
a
subset
of
the
ARF.
What
green
just
mentioned.
So
we,
the
ARF,
still
leaves
some
like
like
holes
in
there.
First
implementation
or
document,
and
we
decided
to
now
fill
in
those
gaps,
make
some
decisions,
and
then
we
created
a
wallet
for
it
together
with
other
companies
who
also
contributed
to
the
project
and
I
will
give
a
quick
demo
of
this
wallet
right
now
so
see.
D
We
I
think
we
can
give
some
links
to
the
wallet,
so
you
can
play
around
with
it
yourself,
but
basically
this
leverages
the
open
ID
for
VC
specifications,
so
we
use
open
ID
for
VCI
for
credential
issuance
sign
up
and
open
ID
for
VP
to
present
these
credentials-
and
this
is
just
a
very
nice
simple,
login
flow
again,
very
demo
environment.
So
no
additional
security
is
provided
here.
D
Here
we
see
a
QR
codes,
hopefully
on
the
first
one
to
scan
this,
and
here
we
can
see
the
credential.
We
also
have
a
little
displayer,
which
is
all
from
the
w3c
Json
LD
specifications.
We
get
this,
and
this
is
the
content
of
the
credential
which
we
can
accept
and
now
I
have
three
attendance
credentials
which
might
be
a
bit
much,
but
it's
a
demo
and
then
we
can
go
back
and
use
this
QR
codes
to
log
in
which
basically
does
a
proof
request
of
the
credential
which
we
can
see
here.
D
We
want
to
first
name
the
email
and
ID
last
name
and
the
event,
and
if
I
click
accept
it
will
share
it
and
I
am
logged
in
right
now,
which
can
be
seen
here
so
yeah
I
can
see
here.
I
am
logged
out
again
very
very
much
demo
environment
fun
to
play
around
with,
but
it
shows
the
specific
demo
quite
shows
very
well
that
the
open
idea
for
VCI
group
of
specifications
is
is
very,
very
simple,
built
on
top
of
a
lot
of
standards
that
already
exist
and
yeah
it.
D
It
removes
quite
some
overhead
to
map
to
to
issue
credentials
more
quickly
and
I'll.
Show
you
that
right
now,
so,
if
I
go
to
the
slides
from
a
holder
perspective,
this
is
basically
the
color
code
that
you
need
basically
with
a
massive
Asterix,
because
of
course,
it's
more
set
up
with
State
Management
and
everything
we're
not
going
to
go
into
that.
D
So
we
we
can
set
up
an
agent
and
we
add
a
new
module
called
the
open
ID
for
VC
client
module.
This
is
specifically
for
the
wallet
side
which
in
open
ID
for
VCC
terms,
is
the
client,
and
we
also
need
a
wallet
here,
but
it's
all
left
out.
So
we
can
make
a
nice
little
example
we're
not
throwing
a
lot
of
and
on
module
tattoo
and
right
here
below
we
initialize
the
agents
quickly,
and
then
we
call
the
methods
request
credentials
using
pre-authorized
code.
D
So
with
the
open
ND
for
VC
specifications,
you
have
like
a
you,
have
a
pre-authorized
code
flow
and
a
authorized
code
flow
for
this
demo.
We
rely
on
the
pre-authorized
code
flow
here.
We
just
pass
in
the
data
which
we
scanned
as
the
issuer
URI
we're
given
a
couple
of
additional
Fields,
also
the
the
proof
of
possession
verification
method.
Resolver.
We
love
our
long
names.
D
D
D
Afterwards,
we
we
offer
a
credential
from
the
issuer
using
the
the
new
anocrats
model
once
that
is
received
by
the
holder,
we
actually
migrate,
the
holder
to
the
new
shared
components.
The
underlying
database
structure
for
India
is
quite
a
bit
different
than
for
Oscar,
so
we
wrote
a
custom
migration
script
which
I
think
we'll
touch
upon
more
later,
but
the
gist
of
it
is
so.
D
You
can
reuse
your
in
SDK
agent
credentials
and
everything
that
they're
stored
in
there
with
the
new
short
components
and
then
afterwards,
at
plus
that
we
present
a
credential
to
a
verifier
with
the
newly
migrated
agents
to
showed
up
everything
still
works
as
it's
supposed
to
be,
and
I
will
slide
to
the
codes
which
is
open
right
here.
I
hope
it's
big
enough.
I
can
make
it
bigger
if
it's
not
big
enough
for
some
people,
so
we'll
just
quickly
go
through
the
code
and
then
see
what
it's
doing
again.
D
D
D
The
area
of
the
island
press
RS
module,
which
is
a
module
around
the
annum
credits,
JavaScript
wrapper,
which
is
for
node.js.
It
uses
spear
ffi
bindings
and
for
react
native.
It
uses
thermal
modules
for
tits.
We
only
need
the
in
need,
resolver
as
the
holder
and
for
the
nvdr.
We
we
Supply
a
network
which
is
the
PC
operating
test
Network,
which
is
just
a
simple
Genesis
transaction
and
some
information
like
if
it's
a
production
Network.
D
D
So
here
we
want
Auto,
accept
connections
to
True,
which
basically
means
that
if
we
want
to
establish
a
connection,
we
don't
have
to
go
through
the
entire
process
manually
of
the
multiple
steps
and
most
time
users
just
want
a
single
like
accept
or
decline,
and
it
helps
a
lot
with
that
below.
We
have
the
new
credentials
module
same
configuration.
As
for
the
connections,
we
can
Auto
accept
credentials.
D
D
If
it's
true
or
not,
we
just
accept
it
works
very
well
for
demos,
definitely
not
recommended
for
production
environments
and
below
that
we
register
some
credential
protocols,
which
is
for
now
only
the
V1
protocol,
which
uses
the
anacrits
credential
format
service
and
right
here
you
would
specify
like
a
Json,
LP,
credential
format,
surface
or
a
legacy
in
the
credential
format.
Surface.
To
support
all
of
all
of
them,
but
for
this
we
try
to
keep
the
modules
as
minimal
as
possible.
D
So
that's
the
holder
and
we
initialize
it
and
with
initializing
you
just
you
initialize
the
wallet
you
set
up
the
transports,
I
think
people
that
are
familiar
with
afj
know
exactly
what
it
does,
but
it's
just
setting
everything
up
for
you
right
now,
as
some
of
you
who
might
notice,
who
migrated
to
zero
four
zero
already
is
you
have
to
create
a
link
secret?
Now
the
industry
I
think
put
that
under
the
hood.
D
Most
notably
here
is
Oscar
instead
of
the
in
the
SDK
again
the
new
crypto
and
storage
implementation,
which
is
required.
If
we
don't
use
any
SDK,
we
have
entered
this
module.
We
also
have
a
registrar
because
we
are
an
issuer
and
we
have
to
register
our
debt.
We
can
also
import
it,
but
Ariel
mentioned
so
you
don't
really
have
you
don't
need
a
registrar,
but
for
this
we
we
don't
import
it.
D
So
you
have
to
register
it
ourselves,
Network
again,
BC
over
and
test
Network
and
the
rest
is
all
the
same
so
below
we
actually
get
to
some
functionality,
which
is
creating
and
registering
a
did.
Indie
codes
for
this
is
is
fairly
simple.
It
is
a
test
Network,
so
feel
free
to
copy
this
seat.
It's
it's
all
fine.
D
Basically,
what
we
do
here
is
PC
over.
It
has
like
a
web
UI
where
you
can
create
it
and
then
right
here
we
copy
the
seed
that
we
use
there.
This
is
the
date
that
came
out,
so
we
also
put
it
here.
This
would
be
equally
qualified,
which
is
also
something
we
do
from
zero.
Three
zero:
two
zero
four
zero.
As
we
move
through
qualified
identifiers
for
indie,
and
here
we
have
the
import
function,
which
basically
sets
all
of
this
up.
D
It
might
look
a
bit
weird
that
we
use
the
same
as
the
private
key
I
had
a
discussion
a
while
ago
why
this
was
the
case.
I
forgot
it,
but
I
think
it
was
required,
because
this
is
just
how
the
industry
did
it
and
for
escar
we
need
to
keep
records
compatibility,
so
this
was
done
there
as
well.
That's
the
seat
is
actually
the
private
key
foreign.
D
D
D
D
Let's
go
there,
credential
definition
and
again
yeah
everyone
already
familiar
with
this,
probably
the
only
right
now,
but
here
we
simply
just
register
to
credential
definition
with
the
schema
same
interface
again,
nice
and
consistent.
If
you
don't
want
to
interface,
you
know
them
all,
and
you
will
just
return
it
and
right
here
we
actually
establish
a
connection
between
the
issuer
and
the
in
SDK
holder.
D
D
D
D
So
if
we
go
back
then
here
we
can
initialize
the
shared
components
folder
and
we
also
initialize
a
verifier,
and
then
we
create
another
connection
between
the
verifier
and
the
holder,
and
we
request
a
an
autocrest
proof
using
this.
So
again
the
connection
ID,
and
here
we
basically
create
a
an
upgrade
specific
request.
D
So
that's
around
the
goats
I
think
I
can
go
here
and
then
we
can
just
simply
run
the
yarn
starts
and
it
will
go
through
the
code.
If
you
try
to
run
this
after
a
workshop,
every
single
step
requires
an
Enterprise,
so
we
can
go
through
it.
So
I'll
just
press
enter
it's
initializing,
the
holder,
creating
link
secrets
and
initializing
the
issuer.
D
And
the
credential
definition
always
takes
some
time,
but
there
it
is
I.
Think
if
you
go
to
the
the
the
the
test
Network,
you
can
see
these
objects
now
in
the
web
interface
and
now
it
creates
a
connection
between
the
issuer
and
the
holder
that
we
offer
to
the
credential
and
it's
accepted
by
the
holder,
which
is
again
all
automatic.
D
Don't
really
have
to
do
any
steps
in
between
which
is
extremely
nice
for
just
quickly
developing
something
then
we're
shutting
down
in
the
holder
and
now
we're
gonna
migrate
it
to
the
neutral
components.
So
all
the
any
credentials
are
moved
into
the
infrastructure.
The
keys
are
moved
everything
that
you
would
need
essay,
holder
or
mediator.
A
Wow,
it's
not
that
new
anymore,
but
I
did
want
to
mention
it
because
we
have
updated
it
significantly.
Can
you
go
to
the
next
one
yeah,
so
in
the
last
for
those
who
were
there
in
the
last
presentation,
I
think
about
a
year
ago
about
the
zero
three
zero
release
that
was
I
think
when
we
first
introduced
the
documentation
website.
So
if
you
go
to
Vegas
I'll
send
it
in
the
chats
you
can
follow
along
aries.js.org.
A
Yep
there
it
is,
and
then
we
introduced
that
documentation
website
it
was
very,
very
minimal
back
then,
and
it
still.
Sadly,
not
everything
has
been
documented,
but
I
think
we
yeah
we're
getting
somewhere,
and
the
first
thing
I
want
to
point
out
is
that
we
have
version
documentation.
So
if
you
are
still,
we
didn't
replace
everything
with
the
zero
four
zero
docs.
So
if
you
are
still
working
in
020,
that
is
no
problem.
A
So
the
apis
change
here
and
there,
the
script
appearance
just
showed
you
was
really
about
the
storage,
so
the
yeah
the
models
or
the
objects
that
are
stored.
They
are
slightly
different
in
in
terms
of
yeah
different
data
structures.
So
there
needs
to
be
some
migration
there
for
that
you
can
use
the
script,
but
these
migration
documentation
or
Pages.
Here
they
are
really
like.
Okay,
what
that
we
have
the
the
zero
three
zero
API
versus
the
um040
API
and
how
to
migrate?
Basically,
what
what
the
lines
of
codes?
A
What
lines
of
codes
do
you
need
to
change?
How
do
you
need
to
change
them?
So
we
we
really
try
to
guide
you
through
that
there
and
yeah.
Lastly,
when
I
want
to
point
out
about
the
documentation
which
I
think
is
quite
cool,
is
we
have
these
beautiful
little
tabs
here,
as
you
can
see
in
the
middle,
so
we
have
an
indie
and
Anna
grad
step,
for
instance
there.
This
is
just
one
example.
A
There
are
many
which
basically
tells
you,
okay,
if
you're
still
using
it
yesterday,
then
this
is
how
you
should
call
this
function.
But
if
you
are
using
atom
credits,
then
you
can
use
well,
then
the
function
calls
should
look
like
this
I
think
we
can
move
on.
That
was
about
the
documentation.
Yeah
then
I
think
it
is
time
to
talk
about
the
roadmap.
C
So
so
yeah,
actually
we
we
are
already
supporting
server
side
actually
in
our
in
both
animal
and
us
are
using
quite
extensively
the
afsha
for
for
for
the
back
ends.
But
this
is
something
that
we
will
want
to
focus
on
in
the
in
the
incoming
releases.
So
that's
why
we
wanted
to
to
put
it
here
right,
but
something
that
we
want
to
say
was
that
even
if
afsha
is
mostly
known
for
for
for
for
mobile
environments
or
or
the
holder
side,
we
believe
that
we
think
that
this
would
is
worth
measuring.
C
We
cannot
push
notification,
so
we
have
the
tools
to
to
make
an
FJ
mediator
to
to
work
or
to
build
a
basis
of
a
mediator
that
is
compatible
with
with
any
with
all
the
protocols
that
are
defined
for
that
and
same
for
the
credential
issuance,
because
we
usually
usually
use
afj
for
for
holler
and
verifier
roles,
but
we
can
also
issue
credentials
in
various
formats
in
the
case
of
the
anoncreds.
It's
true
that
we
don't
currently
support
revocable
credentials,
but
we
are
very
close
to
to
that.
C
C
Some
reasons
for
that
okay-
this
is
this
is
mainly.
These
are
mainly
our
our
reasons
for
choosing
afj,
because
we
have
a
very
small
team.
You
know
that
it's
hard
to
find
skill
developers
nowadays,
so
we
wanted
to
share
as
much
as
we
could
of
the
code
base,
and
so
the
good
thing
about
using
aha
for
both
sides
is
that
we
don't
have
to
master
two
different
languages.
C
This
is
not
only
a
problem
when
you
are
dealing
with
the
with
the
with
high
level
code,
but
also
if
you
need
to
adapt
a
low
level
Library,
because
you
will
need
to
also
create
wrappers,
and
you
know
that
it's
it's
not
very
straightforward,
sometimes
to
create
them.
So
if
we
can
make
the
whole
team
to
work
on
the
same
environment
with
the
same
tools,
it
will
be
usually
faster,
especially
in
small
teams
and
also
the
other
reason
is
that
we
wanted
to
create
custom
features.
I
mean
custom
protocols,
for
instance,
in
our
project.
C
We
are
using
VidCon
for
for
chat,
so
we
are
using.
We
have
created
some
protocols
to
send
media
to
other
to
other
parties,
profile
pictures
and
that
stuff,
so
for
us,
was
a
lot
easier
if
we
should,
if
we
just
made
a
single
extension
for
for
FJ
and
instead
of
having
to
create
two
extensions
for
I,
mean
one
for
for
for
the
server
side
and
another
for
the
for
the
the
client
side,
and
also
some
other
nice
features
of
if
Shea
are
the
storage
backend.
C
As
mentioned
in
the
beginning
of
the
this
conversation,
to
use
a
browser
or
or
whatever
so,
and
also
something
that
as
Kareem
already
answered
in
the
in
the
chat
is
that
we
have.
We
do
have
an
extension
in
the
iris
framework,
JavaScript
text,
repo
that
provides
a
provides,
a
rest
interface.
So
we
you
can.
You
can
easily
set
up
an
agent
with
a
rest,
AP
API.
So
that's
our
some
of
the
good
things
about
using
afj
on
the
server
side
and
that's.
D
So
one
question
that
I
think
I
got
from
the
beginning
when
I
started
to
work
on
afj
was
when
will
we
have
web
wallets,
which
is
a
very
good
question?
I
think
web
wallets?
They
they
serve
a
very
nice
purpose
and
for
me
it's
always
I.
Think
always
demos
came
to
mind
like
just
a
quick
demo.
You
don't
need
to
host
the
server
for
it.
D
It's
very
simple
and
with
what
we
talked
about
with
modularizing
the
the
framework
we
basically
every
every
module
we
we
separate
we
get
closer
to
full
web
support
because,
right
now
the
main
issue
is
with
the
framework.
Is
we
just
have
too
many
dependencies
on
Note
specific
items
or
react
native
specific
libraries,
and
they
are
just
not
provided
for
the
web
and
before
that
within
the
SDK,
there
was
just
no
like
web
replacement
for
the
entire
esdk.
D
Separating
everything
out
into
their
own
module
makes
it
a
lot
easier
and
more
manageable
to
replace
smaller
parts
with
a
browser
implementation,
for
example,
for
a
demo,
you
can
probably
create
a
an
implementation
of
escar
for
afj,
with
using
local
storage
and
browser.
Crypto
I
think
that
that
would
be
relatively
manageable.
D
There
is
also,
of
course,
a
web
assembly
which
could
use
wasi
as
a
for
storage.
This
is,
of
course,
more
of
like
a
full
like
actual
web
wallet,
and
not
just
a
demo.
Environment
like
you,
wouldn't
use
local
storage
to
to
store
your
credentials,
but
once
you
would
could
actually
provide
a
way
to
store
credentials
when
your
local
device
and
access
them
from
the
browser
packages
like
autocrats
are
compatible
to
webassembly
as
well.
D
D
In
the
back
of
our
mind
like
as
long
as
core
remains
platform
agnostic,
we
can
create
modules
for
everything
that
we
need,
and
then
we
can
slowly
move
to
a
first
aid
demo
environment
for
afj,
where
you
can
just
have
a
local
credential,
and
you
can
just
be
a
holder
in
the
browser
and
afterwards
we
can
move
into
more
serious,
actual
production
implementations,
for
example,
with
YZ
or
with
decentralized
web
nodes,
which
would
be
a
great
thing
to
add
to
afj
to
sports.
Secure
Storage
like
that.
D
So
afj
also
really
aims
to
support
at
least
the
required
fields
of
the
architecture,
reference
framework,
which
is
the
European
document
that
screen
mentioned
before
we
are
relative
or
relatively
far
with
that
we
have
quite
some
some
basic
setup
for
that.
So
you
know
storage
rule.
So
you
always
need
storage,
but
there
are
still
some
items
that
we
miss.
D
So,
for
example,
the
first
one
is
JWT
credentials
with
select
disclosure.
This
is
something
that
Karim
and
I
actually
have
been
working
on
for
bits
to
add
it
to
afj.
So
this
is
something
that
might
already
be
there
in
the
041
release.
Then
there
is
ISO
18013,
which
is
the
mdl.
Mdoc
MSO
object
group
of
specifications.
This
is
mainly
required
for
the
proximity
flow,
so
share
your
credentials
over
NFC
and
Bluetooth.
D
This
is
something
we
would
love
to
add
to
afj,
but
it's
just
not
something
that
we
have
a
lot
of
experience
in
so
we're
sort
of
waiting
for
a
typescript
implementation.
For
this
that
we
can
reuse
in
our
framework
and
parties
are
working
on
that.
So
we
would
love
to
have
this
before
a
zero
five
zero
release
and
to
be
more
compliant.
We
would
also
need
to
support
basically
all
the
open
ID
for
VC
protocols.
D
So
my
issuance
and
presentation,
the
demo
that
I
just
showed
you
with
the
wallet
that
had
all
those
items,
but
they
are
right
now
they're,
not
inside
afj,
yet
mainly
because
we
we
had
to
do
it
a
bit
quicker
and
we
didn't
want
to
now
think
about
all
the
architectural
things
that
we're
doing
for
this
project,
but
they
will
be
backboarded
into
afj
to
fully
support
the
open
ID
for
VC
stack,
which
is
a
very
nice
thing
to
optionally.
Add
to
your
agent
and
the
last
item
is
the
ARF
mentions.
D
I
think
it's
required
that
all
wallets
that
are
compliant
need
a
secure,
Enclave
or
Hardware
support
or
Hardware
security,
module
or
I.
Think
Android.
It's
called
it's
shared
sure.
It's
secure
stores
or
something
I
forgot,
but
you
basically
need
Hardware
bounce
crypto,
which
is
extremely
interesting
and
some
like
something.
We
definitely
also
would
like
to
add.
D
We
don't
have
a
clear
way
to
do
this
yet,
but
it's
it's
definitely
something
we're
looking
forward
to
for
other
parties
to
help
us
with
or
for
for
us
to
implement
and
also
like,
even
with
outside
of
the
ARF.
This
is
just
a
massive
benefit
to
storage.
If
you
don't
have
to
deal
with
exposing
your
your
keys
in
memory
and
being
vulnerable
to
all
kinds
of
attacks
with
that.
A
A
D
So
this
is
something
that
we
we
know
is
is
a
problem
and
that
we
are
working
on.
Some
of
that
work
would
includes
reworking
your
wallet
a
bit.
I
think
this
is
mainly
about
separating
crypto
from
the
storage,
but
Ariel
might
be
able
to
fill
in
in
the
end.
If
I
missed
something
it,
we
also
would
like
to
make
the
core
a
lot
smaller
right
now.
D
There
is
still
a
lot
of
items
in
the
core
very
become
specific
and
just
some
things
that
we
would
like
the
user
to
be
able
to
provide
instead
of
the
core
providing
it
to
you
and
not
all
use
cases
need
everything
and
we
want,
especially
when
working
with
like
native
libraries.
We
want
their
app
to
be
as
small
as
possible
and
not
everyone
needs
a
new
vdr
or
not.
Everyone
needs
the
sdka
for
storage
when
Oscar
or
your
own
implementation
of
react.
D
So
basically,
here
we
would
say
like
okay,
a
very
common
use
case
is
Bitcoin
V2
anokrats
in
vdr,
Oscar
and
yeah.
Maybe
some
configuration
for
your
connections
or
a
mediator
or
something
so
we
can
create
packages
that
would
just
contain
that
and
then
you
could
plug
it
in
and
then
your
agent
setup
would
be
back
to
just
one
line
of
code,
for
example,
also
think
of
like
an
ARF
agents.
D
C
A
All
right,
well
This,
was
a
brief
overview
of
well.
Was
it
brief?
No,
it
was.
It
was
not
brief
at
all.
It
was
80
minutes.
This
was
an
80
minutes
overview
of
the
zero
four
zero
release.
There
are
a
lot
of
questions
in
chat.
Some
have
been
answered,
some
haven't,
so
the
rest
of
the
time
is
really
up
to
for
questions
so
Sean
I,
don't
know
if
you
want
to.
B
I'm
happy
to
we've
been
as
as
the
presenters
you
Kareem
Ariel
and
baron
have
been
fantastic
about
answering
questions
in
progress,
so
we
can
probably
get
into
some
more
questions
now.
Denver
I
did
want
to
make
a
point.
You
just
asked
about
the
meetings,
so
those
are
Community
calls
every
Thursday
they're,
not
like
a
presentation
like
what
the
team
put
on
today,
but
also
we
have
the
asynchronous
discussions
that
happen
in
Discord.
B
We
have
other
workshops
and
I'm
gonna
put
a
link
to
that
right
now
in
chat
workshops
for
and
on
creds
Stephen
Koran,
who
was
on
the
call
a
few
minutes
ago
he's
gone
now.
Stephen
Curran
did
a
fantastic
workshop
on
area
on
an
oncreds,
and
we
have
some
previous
workshops
on
Indian
Aries
that
are
Hands-On.
B
A
Definitely
so
I
mean
it
is
right
now
that
is
also
possible
right,
so
I
mean
we
have
is
currently
still
part
of
the
the
core.
So
you
can
see.
Ditcon
has
two
or
yeah.
It
has
two
I
guess
different
facets.
You
have
the
actual
VidCon
core
of
logic
right
and
then
you
have
protocols
that
are
built
on
top
of
that
and
let
me
quickly
find
how
to
go
back
all
these
flights.
Is
that
easily
done?
Yeah
I
think
here.
A
So,
as
you
can
see
here,
some
and
I
think
that
is
the
plan
to
do
in
the
end
with
what,
in
the
in
the
coming
months
is,
for
instance,
these
here
these
to
the
action
menu
and
the
question
and
answer
protocols.
Those
are
both
dead
com
protocols.
They
are
I,
find
a
separate
modules
because
you
don't
like
it
is
not
every
not
everyone
needs
those
right.
A
Not
everyone
needs
VidCon
as
a
whole,
especially
now
with
with
the
introduction
of
open
ID
for
VCI
and
well
open
ID
for
verifiable
credentials
as
a
whole,
you
might
not
want
to
include
Deadpool
So.
The
plan
is
to
move,
did
come
out
out
of
the
core
as
well,
so
it
is
basically
an
optional
dependency.
You
can
include
or
not
and
then,
with
a
separate
bitcom
module
you'd
be
able
to
Define
other
yeah
other
modules
that
basically
extend
the
network
or
built
on
top
of
that
digital
module
yeah.
B
Cool
and
and
did
come
is
the
reason
why
I
got
involved
in
decentralized
identity.
To
begin
with,
so
all
I
want
to
do
is
make
is
never
have
to
use
LinkedIn
again
thanks
to
come.
Someone
just
asked.
Yes,
dozen
on
credits
package
support
any
nist
approved
crypto.
This
is
an
afj
call
and
Stephen
has
left.
Can
anybody
answer
that
question.
D
So
I
think
this.
The
very
short
answer
is
no.
We
use
RSA
bacl
signatures,
I,
I,
think
Stephen
or
Mike,
probably
or
Andrew,
can
give
away
better
answer
on
this,
but
yeah.
The
answer
is
no
I
think
there
are
looking
for
that's
V2
for
PS
signatures,
which
might
be
es256
based,
but
I'm
I'm,
making
a
very
big
assumption.
There.
I
haven't
looked
at
the
specification
for
that,
but
I
do
know
that
that
V2
is
looking
to
to
broaden
their
crypto
Suite.
A
C
A
Supportive,
but
you
can
you
can
prove
that
that
your
credential
hasn't
been
revoked.
Yet
as
a
holder
for
because
replica
I
mean
they
have
different
flavors,
if
you
will
of
revocation
so
for
for
w3c,
you
also
have
like
the
status
list
2020
one
two
I,
don't
remember
that
is
not
yet
supported
so,
but
that
will.
A
C
A
B
B
A
D
B
Worries
Niall
just
asked
following
up
on
an
earlier
thread,
so
the
Anon
creds
and
ndvdr
modules
aren't
necessary
in
ndsdk,
for
example,
and
then
I'm
sorry,
I
just
noticed,
Ariel
replied
all
right
great
and
then
there's
a
GitHub
link.
Okay
in
Denver
asked
in
terms
of
setup.
There
are
quite
a
number
of
issues
for
yarn,
install
on
Windows
for
node
version,
16
and
18.
are
those
being
recognized
and
is
it
affecting
anyone
else
in
terms
of
the
demo
running?
Oh
that's
answered.
C
A
D
Yeah
so
I
I,
yeah
I
assume
it's
about
sex
closure
and
zika
peace.
So
nothing
really
changed
between
zero,
three
zero
and
zero
four
zero.
We
still
support
all
the
autocrats.
Zero
knowledge
proof
way,
so
we
predicates
selective
disclosure.
All
of
that
is
still
in
there
for
Json,
LD,
issuance
or
verification
I.
Think
we
don't
yet,
but
that's
mainly
because
of
presentation,
proof
V2
support,
but
we
do
support
the
underlying
crypto
to
selectively
disclosure
with
Jason
Aldean.
D
D
We
all
moved
to
the
shared
component,
so
I
I,
left
at
work
I
think
it's
definitely
doable
that
that
now
provides
a
xfi
interface
by
by
default
or
a
way
to
do
that
and
notes
doesn't
really
so
I
think
that
would
definitely
be
something
cool
and
also
yeah.
Definitely
something
we're
open
for
for
contributions.
B
B
B
I
have
a
question
from
Denver
from
earlier.
What
nope
somebody
just
answered
that
will
it
be.
Is
the
last
open
question
that
I
can
find?
Will
it
be
possible
to
have
more
frequent,
meetups
nope?
Yes,
we
are
every
week
she
meets
and
and
that
that's
it's
less
of
like
a
a
demonstration
and
a
presentation
like
today
Denver,
but
it's
the
the
team
is
definitely
meeting
and
they're,
always
having
conversations
on
Discord.
A
B
C
D
Yeah,
so
it's
only
mobile
so
specifically
for
the
English
Decay
to
escar.
It's
only
mobile
sqlite,
so
well
only
mobile
ish.
We
also
have
support
for
for
mediators,
because,
basically,
we
currently
don't
support
migrating.
The
schema
and
the
credential
definition,
so
a
holder
or
mediator
would
be
perfectly
fine
to
migrate
with
that.
D
You
can
directly
migrate
from
the
India
sk030
to
the
shared
components
with
zero
four
zero,
but
there
is
a
specific
order
in
which
you
need
to
run
the
escar
migration
script
and
the
afj
storage
updater,
which
is
all
explained
in
the
documentation,
from
migrating
to
from
zero
three
zero
to
zero
four
zero
and
also
migrating
from
the
SDK
to
Oscar.
So
the
docs
will
probably
give
you
everything
every
bit
every
bit
of
information
you
need.
B
All
right,
I
would
like
to
thank
everybody
for
joining
us
today,
and
I
would
really
like
to
thank
the
presenters,
Arielle,
Behrend
and
Kareem
for
doing
such
a
great
job
of
both
going
into
detail
on
what's
new
in
Aries
0.4.0,
but
also
you
know
the
how
and
the
why
and
the
wherefore
how
things
work.
It
was
really
a
great
presentation
and
thank
you,
as
I
mentioned
at
the
start.
Hyperledger
is
powered
by
the
contributors
and
maintainers
who
make
all
these
projects
work.
We
would
love
your
contribution.
We
would
love
you
to
be
involved.
B
C
B
We
do
a
workshop
like
this
I
generally
for
folks
who
registered
I'll,
send
out
a
a
thank
you
note,
I'm
going
to
put
these
links
as
well
as
a
link
to
a
to
the
Wiki
page
for
this
Workshop
in
both
the
YouTube
video
as
well
as
in
the
thank
you
note
in
case.
You
want
to
share
the
video
or
share
the
deck
with
your
colleagues
or
co-workers
or
project
Partners,
whatever
you're
doing
so,
that's
going
to
go
out.
B
Probably
you
know,
YouTube
is
going
to
encode
the
video
over
the
course
of
a
half
hour,
45
minutes
and
then
I'll,
hopefully
be
able
to
get
that
out
by
either
end
of
day
today
or
first
thing
tomorrow
morning,
but
I
really
like
to
thank
everyone
for
attending,
but,
most
importantly,
thank
you
Kareem.
Thank
you,
Baron.
Thank
you,
Ariel
for
doing
such
a
great
job.
Thank.