►
Description
Stephen Curran, CloudCompass Computing, Inc. & John Jordan, Province of British Columbia
A hands-on workshop covering both business and technical aspects of an organization becoming a participant in the Verifiable Organizations Network (VON). Attendees will gain insight into both business and technical aspects of a Hyperledger Indy based solution.
The attendees will work in groups to deploy an organizational Hyperledger Indy based VON-X Issuer/Verifier service so they can learn about what it would take to on-board a permit service onto VON. Their service will issue Verifiable Credentials to TheOrgBook and enable a permitting workflow. The attendees will consider the business context - how would this affect existing workflows within their organizations, what would the value be to their business? They’ll also see the technical components in action - what’s involved in becoming an organization that consumes Verifiable Claims, and that issues Credentials.
Bring your laptop!
----
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 #HyperledgerGlobalForum2018 #Blockchain
A
All
right
so
we're
gonna
do
sort
test.
P
solving
network
is
down.
We
allocated
some
more
resources
to
rebooted
everything
that
didn't
come
back
up
and
we
need
to
SSH
into
the
box,
but
access
for
that.
So
what
I'm
gonna
do
for
the
period
this
afternoon
is
on
this
kind
of
demo.
The
workshop
I've
set
up
my
play
with
docker
to
connect
to
our
development
environment.
A
We're
gonna
record
a
video
of
it
as
well,
so
that
it
will
post
that
sometime
within
the
next
week
or
so
we've
got
another
workshop
tomorrow.
We're
gonna
try
beefing
up
our
be
sovereign
network
to
handle
more
load.
So
you
try
coming
around
plus
I'm
gonna
be
around
this
afternoon
and
tomorrow
afternoon.
So
if
you
find
me
or
just
ping
me
on
whenever
one
of
our
many
communications,
then
I
can
answer
questions
over
the
next
couple
of
days
as
well.
So
what
I've
done
just
to
confirm
everything
actually
works
is
I.
A
I've
set
my
my
hostname,
so
I've
done
the
first
couple
of
steps,
I
set
my
hostname
and
then
I
ran
the
init
script
in
it
dot
SH
to
set
my
did
so.
My
new
organ
a
is
e'en
kovash.
You
were
Mach
two
on
December
14th
and
it's
registered.
They
did
at
my
did
on
the
ledger,
so
my
my
did
so
based
on
this
seed,
my
did
is
f29
blah
blah
blah
and
then
it
went
through
and
it
updated
all
of
the
configuration
files
so
that
they're
all
now
configured
for
for
my
environment.
A
So
we
went,
we
went
through
the
configuration
files
earlier,
so
I'm
not
gonna.
Do
that
again,
but
I'll
just
go
to
the
config
I'll
open
the
schemas,
and
you
can
see
now
that
the
the
name
of
the
schema
now
has
Mayorga
name
in
it
that
I
specified
through
the
Annette.
So
all
of
the
schemas
are
now
unique
to
me.
So
when
they
show
up
in
the
orc
book,
they'll
show
up
under
me
and
for
services
have
set
the
issue
renamed
to
Ian
code,
December,
14th
workshop
issue
or
second
try.
A
B
A
C
C
A
A
So
if
you
do
ever
decide,
you
want
to
build
the
whole
thing
on
your
own,
then
there's
other
repositories
that
are
all
under
BC,
gov
and
they've
all
got
a
similar
structure,
so
there's
they're
all
docker
based
and
they're
all
based
on
this
manage
command.
So
if
I
do
manage,
build
it
downloads,
a
pile
of
stuff
and
builds
my
local
docker
images.
So
this
is
installing
the
agent
software
on
my
local
machine
using
docker
based
installation.
A
So
there's
there's
a
base,
docker
image
that
includes
all
of
the
Indy
SDK
Python
wrapper
our
Postgres
wallet
software,
as
well
as
the
software
that
we
use
for
the
agent
agent
communication.
So
there's
a
software
that
we
call
Vaughn
axe
and
essentially
it's
a
peer
as
a
peer
to
peer
agent.
So
the
father,
actually
Vaughn
axe,
runs
in
the
orc
buck
and
Vaughn
axe
runs
in
the
agent.
So
when
you're
issuing
credentials
or
you
know
creating
scheme
as
an
issue
and
crunch
holes,
then
it's
the
Vaughn
axe
pieces
that
are
actually
talking
to
each
other.
A
E
D
E
C
C
C
Internet,
we
don't
really
know
where
we
load
a
Genesis
transaction
file
that
tells
us
who
to
talk
to
and
how
to
talk
to
that.
So
it's
just
out
there,
the
ledgers
out
there
somewhere
on
the
Internet,
as
well
as
a
person
who
uses
the
website
and
can
be
other
other
clients
that
are
just
using
the
org
book
API,
so
they're
just
doing
queries
about
companies
and
and
what
credentials
they
have
and
so
on.
C
So
that's
the
internet
side
of
it
that,
if
you
were,
is
up
here
so
this
is
an
example
of
the
BC
registries
issuer.
So
in
this
case
they
have
their
own
system
and
they've
got
a
oracle
enterprise
database
that
they
manage
all
their
data
in
what
we
did
is
again
we're
trying
not
to
change
their
world
at
all,
we're
trying
to
be
as
light
and
touch
as
possible
until
they
see
the
value
and
want
to
increase
that.
C
So
what
we
did
was
we
just
used
a
Postgres
data
wrapper
which
allows
us
to
have
a
read-only
view
into
their
database
and
then
what
we
do
is
we've
got
an
event
processor
that
monitors
the
database
for
when
an
event
occurs.
Hey
a
company
was
just
incorporated
in
British
Columbia
and
oh
these
two
companies
dissolved
and
joint
merged
together
to
create
a
new
entity,
and
this
company
just
had
did
not
renew,
and
now
they
are
no
longer
a
valid
company.
C
E
E
C
C
There's
also
did
off
going
on
here,
so
one
of
the
things
that
BC
dub
did
was
they
put
a
bounty
on
creating
an
implementation
of
did
off
and
those
in
the
community
might
know
Marcus
a
Videla
or
peacekeeper,
as
he's
called
in
the
ad
community
and
various
other
communities
w3c
and
and
if
he's
the
guy
who
created
the
universal
resolver,
so
he
won
that
bounty.
He
created
a
did
off
mechanism
so,
each
time
these
components
talk,
they
offer
they
authenticate
via
the
dibs
and
there's
a
whitelist
right.
C
Now,
it's
just
a
whitelist
over
here
that
we
maintain
of
what
bids
do
we
want
to
allow
to
talk
to
us?
So
if
you're,
if
you're,
not
an
issue
where
that
we
know
about,
you
will
not
be
able
to
issue
to
the
oral
book
credentials
until
we
add
that
in
so
that's
a
piece
we
have
right
now
is
just
to
experiment
with
the
did
off
capability
in
that
it's
a
pretty
early
implementation,
but
it
actually
went
in
really
smoothly
and
we
just
keep
using
it
and
don't
touch
it.
A
lot.
E
C
So
again,
we
have
another
component
of
Vaughn
EXO
they're,
just
talking
to
each
other
and
I've
had
a
couple
of
people.
I've
talked
to
about
protocols
and
agent
agent
protocol,
we're
kind
of
short
cutting
it,
because
we're
controlling
both
sides
of
it
we're
just
having
part
of
a
proprietary
discussion.
C
Api
will
then
basically
parse
the
elements
of
the
claim
within
the
credential
will
figure
out
based
on
the
mapping
that
you
provide
and
that's
part
of
the
configuration
that
is
going
over
today.
What
fields
are
relevant
for
searching?
What's
a
name,
the
or
book
searches
on
names
and
allows
people
to
search
on
name?
So
when
we
issue
a
credential,
the
issuer
has
to
say
this
field.
C
Here,
that's
a
name
and,
and
people
should
be
able
to
search
on
that,
and
so
that's
how
it
understands
the
mapping
from
the
credential
into
a
generic
data
structure
that
the
oral
book
understands
and
that's
how
we
do
you
know,
make
it
generic
so
that
it
can
handle
its
agnostic
of
any
specific
credential
type.
So
there's
not
any
specific,
BC
definition
of
a
credential
in
here
it
just
says
you
tell
us
what
your
credential
look
like
and
how
it
maps
into
the
search
capabilities
that
we
provide
and
we'll
go
from.
C
There
fires
it
into
a
database
and
get
a
four
JavaScript
web
interface
on
the
front
of
that.
So
all
of
this
in
our
world
is
running
on
open
shift,
and
so
what
we
can
do
is
these
are
containers.
Basically,
the
API
is
the
container
bond
acts
as
a
container
Postgres
is
a
container,
so
what
we
were
able
to
do
in
loading.
C
We
talked
a
bit
about
this
on
the
on
the
the
other
day,
ten
days
to
load
our
first
pass
at
loading
all
of
the
data
in
using
a
non
Postgres
database
and
using
you
know,
just
sort
of
single
instances
of
things.
We
had
us
about
two
sprints
one-and-a-half
sprints
to
two
sprints
by
the
end
of
the
second
sprint:
we've
gotten
up
to
2600
credentials
per
minute
being
issued
by
BC
registries
and
then
being
consumed
by
the
or
book
so
we're
down
to
twelve
hours
to
load
all
of
the
companies
at
British
Columbia.
E
C
E
B
D
D
A
While
we're,
while
we're
discussing
I'm
just
gonna,
go
on
to
the
next
step
so
built
all
my
local
docker
images,
I'm
just
gonna
start
up
the
environment
right
now
when
it
starts
up
it
registers
all
of
its
schemas
and
credential
definitions.
So
it
does
take
a
minute
or
so
so
I
don't
know.
If
you
want
to
just
kind
of
continue.
The
discussion.
E
Is
it
big
older?
They
thought
the
holder
trooper,
that's
big
difference
between
the
original
personal
and
multi-subject.
Normally,
the
holder
holds
credentials
that
single-subject
meet.
In
this
case,
the
holder
is
Berkowitz
holding
credentials
about
millions
of
subjects,
organizations
that
are
created
in
the
jurisdiction.
E
C
C
So
we
would
in
a
public
one,
we
would
never
put
any
versatile
baby.
So
all
of
the
data
you're
seeing
here
is
public
data.
So
this
is
the
information
that
is
those
on
the
wall
of
our
restaurant.
One
of
the
reasons
we
started
there
is
cuz.
We
don't
why
they
with
public
beta
yet
well,
we
learned
predicated
so
don't
want
to
be
580
and
well.
We
learn
now
that
privately
we
never
go
into
a
public
repository
the
weird
box
entities
we're
building
a
decentralized
system.
E
C
C
A
She
answered
my
question
back
to
the
demo.
This
is
mo
now
so
I've
started
out
my
local
agent
and
it's
registered
the
schemas
on
the
on
the
be
sovereign
network.
So
this
is
the
interface
for
the
development
version.
So
if
I
go
into
the
transaction
browser
and
type
in
Mach
2,
which
was
part
of
my
work
name,
then
it
will
filter
on
anything
related
to
an
organization
name,
something
like
Mach
2.
So
this
has
my
my
div
so
that
this
is
a
know.
A
C
D
E
A
C
C
A
F
E
E
B
E
G
A
Okay,
so
I've
started
up
my
so
I
have
now
an
agent
running
on
the
plane
with
docker,
and
it's
talking
to
the
board,
which
is
running
in
the
DC
government,
development,
environment
and
there's
two
parts
that
are
exposed.
Five.
Four
three
five
is
the
wallet
database
which
is
used
locally,
so
we're
not
really
interested
in
that
one.
Five
thousand
one
is
the
port
that's
exposed
by
the
web
and
the
rest
services.
So
when
I
connect
to
that
one.
C
A
So
we
don't,
we
don't
have
anything
configured
on
the
kind
of
the
route
it
configures
a
web
page
for
each
of
the
credentials
and
it
configures
the
web
services.
This
isn't
really
we're
not
really
intending
the
agent
to
be
used
to
build
web
interfaces.
The
the
interface
there
was
more
just
for
for
a
demo
to
be
integrated
within.
You
know
the
agencies,
the
issue
agencies,
other
software
and
primarily
what
we
found
is
the
people.
We've
talked
to
they've
got
other
systems
that
produce
the
credentials,
and
then
they
interact
by
web
service.
G
H
G
A
A
For
so
what
I'll
do
is
I'll
just
jump
into
D
flow
I'll
be
refreshed,
hopefully
my
credentials
and
show
up
here,
walk
to
so
my
credentials
that
I
just
issued
automatically
are
showing
up
in
D
flow,
because
it's
getting
that
information
from
the
org
book
and
from
the
ledger.
So
I
can
pick
one
of
the
credentials
that
I
want
to
create.
I,
don't
have
an
existing
company
that
I
want
to
create
so
or
good.
A
I
want
to
update
I
just
want
to
create
a
new
one,
so
I
click
on
begin
and
then
it
will
show
me
a
graph
of
the
credential
that
I
want
to
create
and
the
dependencies
and
the
let
me
walk
through
the
the
sequence
of
steps
to
create
each
of
them,
so
that
this
is
the
one
that
I
want
to
create.
There's
dependencies
that
I
don't
have
so
I'm
starting
from
square
one
with
brand
new,
so
I
will
go
test.
Co,
just
number
14
walk
to.
A
It
just
tells
me
pop-up
and
not
very
helpful
message,
but
it
does
say
success
and
then
it
gives
me
back
an
identifier.
I
can
use
this
identifier
if
I
want
to
like
this
is
the
same
information
you'd
get
back
from
a
web
service
call,
and
then
you
can
take
this
identifier
and
you
can
store
it
in
your
agency
issue
a
database
and
then
you've
got
a
reference
to
the
credential
that
you
just
created.
A
C
C
C
E
A
F
H
A
Okay,
yeah,
okay,
so
I've
I've
gone
I've
created
a
new
one
again
so
I
mentioned
the
result
that
comes
back
is
the
actual
ID
of
the
credential
that
we
created
so
I'm.
Just
gonna
grab
that
for
now
and
what
I'm
gonna
do
is
I'll
go
back
to
my
agent,
and
so
I
mentioned
that
if
I
try
to
go
to
mine
or
tax,
it's
not
going
to.
Let
me
create
it
because
I
need
to
provide
the
prerequisites.
So
what
I
can
do
here
is
I
can
give
it.
A
A
So
then,
when
I
go
in
when
I'm
providing
a
prerequisite,
Prudential
ID
to
satisfy
the
proof
request,
then
it
lets
me
in,
and
it
gives
me
the
opportunity
to
obtain
a
tax
number,
and
it
also
gives
me
a
summary
of
the
proof
that
was
done
and
because
it
ran
that
proof,
that's
able
to
pre-fill
the
registration
ID,
which
is
the
identifier
that
was
created
when
I
created
the
initial
registration
credential
and
the
legal
name,
which
is
also
coming
from
that
initial
credential.
So
ideally,
these
two
should
be
read-only.
I
shouldn't
be.
C
C
Food
food
was
over,
it
got
proved
back
and
verified
that
proofs,
or
whatever
contacts
the
ledger
to
see.
If
you
were
that's,
the
issue
who
are
expected
to
tea
then
extract
the
planes,
the
data
elements
from
that,
and
it
filled
those
data
elements
in
up
there
as
the
basis
of
the
information
for
issuing
the
new
credential
and
then.
D
B
C
The
issuer
said:
India
proof,
request
acceptance,
the
Oracle
your
book,
that
is
credentials,
databases
that
you
want
a
little
company
XYZ.
Here's
a
proof
that
that's
right,
synth
proof
directly
to
the
verifier.
This
issue,
a
verifier.
It
dans
looked
at
the
proof
and
as
necessary
to
the
ledger
to
check
any
other
information
necessary,
but
primarily
it's
between
the
two.
They.
C
C
C
C
C
That
group
request,
the
other
thing
is
that
you
can
take
and
say:
I
want
claims
with
four
different
credentials
and
I
want
the
one
proof
request
to
get
all
of
those
credentials
to
show
that
you
want
all
of
them
and
the
particular
claims,
without
also
you
can
cross
over
provincials
and
things
like
that.
That's
the
magic
that
it'd
be
really
great,
that
some.
C
Credentialing
systems,
so
some
of
them
give
you
a
credential
and
they
give
you
the
ability
to
prove
the
entire
credential.
So
you
can't
break
it
down.
You
get
the
credential
and
you
prove
the
connection
so
that
really
got
signed
to
credential
you
sign
and
countersign
the
credential,
and
then
you
can't
go
off,
but
that's
all
of
the
information.
C
A
Just
to
run
through
that
from
our
example
so
I'm
in
now
the
services
dot
Yama
file.
So
this
is
how
we
configure
this
within
the
agent.
So
we've
got
four
schemas,
so
we've
got
the
registration
schema
with
a
bunch
of
stuff.
We've
got
the
tax,
we've
got
liquor
and
then
we've
got
the
last
one,
which
is
just
called
my
credential
and
each
each
one
of
these.
With
the
exception
of
the
first
one
has,
it
depends
on
for
a
proof
request,
so
the
tax
depends
on
having
a
registration.
A
The
liquor
depends
on
having
a
registration
and
then
the
test
their
last
one
depends
on
something
that
we're
calling
liquor
in
tax.
And
what
does
that
mean
when
we
scroll
down
to
the
end?
We
see
that
we've
got
a
section
where
we
defined
what
our
proof
requests
are
so
registration,
which
we
referred
to
earlier.
A
We
identify
what
the
schemas
are
that
we're
depending
on
and
what
the
attributes
so
that
for
the
first
one
registration,
we
identify
the
schema,
the
registration
schema
and
we
identify
the
registration
ID
in
the
legal
name.
And
then
those
are
the
two
fields
that
we
showed
being
prefilled
on
the
form,
the
second
one.
So
the
liquor
and
the
tax
each
depend
on
the
registration
and
then
the
last
one
we
just
said
well
we're
going
to
depend
on
all
of
the
credentials
that
we've
got
so
liquor
and
tax
depends
on
having
the
registration,
tax
and
liquor.
G
A
So
so
gesture
to
identify
another
one.
So
so
these
proof
requests
can
cross
issuers
as
well.
So
we've
got
examples
down
here
which
thank
you
which
we
may
not
get
to,
but
we
can
issue
a
credential
that
depends
on
a
schema
that
is
from
a
different
issuer.
So
these
last
two
are
from
an
issuer
called
D
flow,
which
is
the
the
sample
ones
that
we
have.
So
we
can.
We
can
define
a
new
scheme,
learning
credential.
That
depends
on
something
someone
else
issued.
A
But
you
can
see
how
the
graph
that
we're
building
depends
on
the
proof
requests.
So
we
have
the
first
credential
first
schema
the
first
credential
that
doesn't
depend
on
anything.
That's
what
we
call
the
foundation
credential
the
liquor
and
the
tax
which
we
said
they're,
depending
on
the
proof,
request
called
registration
which
says
you
have
to
have
a
registration,
credential
and
then
the
last
one.
My
credential
depends
on
having
all
of
the
other
three.
A
So
that
gives
D
flow,
the
information
to
lay
out
the
map,
and
if
we
give
it
a
company
and
then
it
should
also
be
able
to
say,
hey,
you've
got
a
you've
got
a
registration.
You've
got
a
tax,
so
it
will
show
those
as
blue
and
then
the
other
two.
You
know
now
you've
got
the
dependencies,
so
you
can
even
like
to
create
them
so
just
kind
of
mentally.
Imagine
that
D
floor
working.
C
C
E
A
A
A
Right
now
is
that
on
the
on
the
web
page,
if
you're
doing
it
through
the
web
page,
we
will
do
some
auto
generation,
so
we
can
automatically
generate
an
identifier
for
the
company,
well,
we're
doing
it
through
the
through
the
rest
web
service,
we're
assuming
that
you've
got
some
system,
some
agency
issuer
system,
that's
providing
all
that
information.
So,
in
this
case,
like
for
the
PC
registries,
BC
registries
has
a
company
number,
so
they
provide
that
company
number
to
us
and
then
that's
what
we
use
for
the
registration
ID
for
the
company.
A
A
So
then
I'll
save
that
and
if
you're
familiar
with
Jason,
you
can
send.
You
can
send
multiple
of
these
in
the
same
request.
So
you
can
just
get
a
group
of
a
group
of
credentials
and
then
just
post
them
all
the
ones.
For
example,
that
might
look
like
this
is
hard
to
read,
but
it's
an
example
that
I
use
when
I'm
doing
my
local
testing
I've
got
a
registration
credential.
A
The
tax
credential
liquor,
my
credential
and
then
I
also
send
cycle
through
a
couple
of
versions
of
each
of
the
credentials,
so
that
I
can
see
what
happens
when
I'm
issuing
the
crash.
All
that
it
already
has.
So
it's
just
just
an
example.
So
I'll
save
this
and
then
that
is
in
this
location.
Ronix
agent,
test
data
sample
registration,
Jason,
so
I
can
just
copy
and
paste
this
curl
command
into
my
daugher
I'll
control.
C
there.
If
I
control
see
the
the
docker
containers
are
still
running,
we're
still
running
until
I,
specifically
shut
them
down.
A
So
here
there's
a
whole
pile
of
stuff
that
happened,
but
at
the
end
I
got
success.
True
and
the
result
again
is
the
identifier
of
the
potential
that
was
created
in
the
org
book
for
that
request,
if
I
send
multiple
credentials,
and
it
gives
me
back
an
array
of
results
that
might
look
something
like
something
like
this
success.
True
success,
true,
so
then
I
just
need
to
remember
what
order
I
issued
the
credentials
in
because
then
the
results
are
coming
back
in
the
same
order
and
I
just
have
to
match
them
up.
A
So
then,
if
I
go
into
the
or
Clark,
if
I
do
my
mock
to
search
again,
then
this
is
the
one
that
I
just
created
by
the
rest
service.
So
it's
exactly
the
same
as
in
once
the
or
book
gets.
It
is
the
same.
That's
just
through
the
through
the
through
the
web
interface
there's
some
fields
that
we
can
generate
automatically
through
the
rest
service.
Everything
has
to
come
from
the
the
issuing
agency's
system,
whoever's
generating.
C
C
A
C
C
C
E
C
A
Now,
if
you
reassure
a
credential,
then
if
there's
an
existing
one,
it'll
automatically
expire,
the
previous
one
based
on
the
initiative
of
the
England-
and
you
can
also
you
can
you
can
revoke
so
you
can
issue
a
credential
and
say
it's
not
a
new
credential.
It's
just
got
an
end
date,
so
you
can
issue
it
and
say
that
it's
being
ended
at
a
certain
point.
H
A
There's
there's
two
approaches
for
that:
I
can't
remember
what
Oh
pop
open.
There
can't
remember
exactly
what
we've
got
in
our
configuration,
but
so
there's
there's
two
business
cases
right.
So
one
business
case
is
that
you
want
to
issue
a
credential.
That's
only
valid
for
a
certain
period
of
time.
So
in
that
case
you
put
in
the
credential
I
think
I've
got
it
in
the.
A
My
schema
so
we've
got
a
an
effective
and
expiry
date.
Essentially,
so
those
are
just
dates.
They
go
into
the
schema
and
then
from
a
business
point
of
view.
When
you
check
that
credential
you
have
to
validate
those
days,
so
the
credential
itself
isn't
going
to
expire.
But
it's
got
a
date
beyond
which
the
credential
isn't
going
to
be
accepted
by
the
business.
So
as
a
business
rule
and
that's
something
that
you
have
to
deal
with
on
the
business
side.
E
A
Be
the
verifier,
so
we've
also
got.
We've
also
got
an
effect
of
an
expiry
date
for
the
credential
itself.
So
if
you
post
a
credential
with
an
expiry
date,
then
that
credential
is
expired
and
when
you
look
at
it
in
the
org
book,
it'll
say
you
know
sorry,
this
credential
is
expired.
You
can't
use
it
for
proof,
so
there's
kind
of
two
different
approaches
to
it.
From
these.
These
two
dates
the
effective
date
and
the
expiry
date.
A
They
don't
have
to
be
called
that
there's
another
configuration
in
the
services
where
you
say
you've
got
a
credential,
effective
date
and
a
credential
expiry
date
or
a
revocation
date.
Rather
so
you
can
based
on
the
data
that
and
the
field
names
that
you
want.
Then
you
can
configure
if
you've
got
a
credential,
effective,
the
expiry
date
and
what
which
attributes
those
correspond
to.
C
C
A
E
E
C
E
Service
has
been
accurately
that
in
their
database
right
now,
because
they're,
relying
on
the
business
people
to
type
in
the
right
name
and
I,
absolutely
a
percent
guarantee
they
don't
do
it
right
if
I
personally
witnessed
it
and
then
in
certain
times
is
bad
because
inefficient
contract
and
it
has
the
wrong
legal
name
which
case
the
contract
is
non-binding
or
you
know
other
permits
and
licenses.
So
part
of
it
is
just
access
to
accurate
data.
But
you.
E
E
It's
a
proof-of-concept.
In
that
sense,
this
is
like
a
production
system.
We
happen
to
think.
We've
found
helpful
service
along
the
way,
but
we're
gonna
keep
going
until
we
get
to
like
personal
identity
being
able
to
associate
a
person
to
a
business
in
a
way
that
they
can
control
the
business.
They
can
delegate
authority
to
arbitrary
other
people,
so
it's
kind
of
on
the
top.
We
only
spent
we
spent
about
a
million
dollars.
E
E
C
A
Yeah,
so
so
this
is
just
kind
of
the
the
first
step.
The
first
quarter
was
just
kind
of
looted,
putting
up
an
agent
with
all
of
the
graduals
that
we
had
previously
defined.
So
we've
got
three
examples,
so
one
of
them
shows
just
creating
a
schema.
That's
got
a
dependency
on
something
that
some
other
agency
created.
The
second
one
was
the
the
site.
A
The
second
example
we
add
a
new
attribute,
so
we
we
take
an
existing
example
and
we
just
add
a
new
attribute
to
it
fairly
simple
and
the
third
one
is
multiple
cardinality
or
multi.
Cardinality
is
any
one,
so
that
just
means
that
you
can
have
more
than
one
credential
of
the
same
credential
played
so
normally
when
you're
issuing
a
credential
like
a
registration
there's
only
one,
so
a
company
can
have
one.
A
A
D
C
F
B
A
Yeah,
so
this
is
this
is
how
this
is,
how
we've
configured
it
so
I'm
coming
to
my
orc
attacks,
so
there's
the
schema
name
corresponding
to
that
URL
as
the
attacks
schema
and
for
the
tax
schema.
We
have
a
proof
request,
link
to
it,
which
the
proof
request
we
looked
at
earlier
is
depending
on
another
credential.
So
what
the
what
the
software
is
doing
is
it's
saying?
Oh,
this
is
the
credential
that
you
want
to
issue.
A
You
know
prove
to
me
that
you
you're
allowed
to
issue
this
credential,
so
I
haven't
given
it
any
any
evidence
that
I'm
actually
allowed
to
have
this
credential
or
that
I'm
allowed
to
issue
this
credential
or
not.
So
if
I
go
back
to
this
screen
and
I
say
credential
IDs
equals
and
I
give
it
the
number
of
the
current
of
the
credential.
This
is
the
credential
I
just
created
through
that
rest
web
service.
A
So
then
what
happens
is
so
it's
basically
the
same
thing
so
now
the
software
is
saying:
okay
well,
now,
you've,
given
me
a
credential
ID,
let
me
see
if
I
can
talk
to
the
org
block
and
get
a
proof
request.
So
the
org
book,
so
that
the
agent
is
now
saying
this
is
the
credential
I
want
to
create,
and
the
orc
book
is
saying
prove
to
me
that
you're
allowed
to
do
it
and
then
I
construct
a
request
with
this
credential
and
send
it
back
and
say:
here's
my
proof.
F
C
E
B
C
C
The
wallet
itself
has
a
set
of
keys
so
that
the
primary
keys
that
we
really
have
to
watch
are
the
ones
that
print
the
wallet.
So
the
keys
that
connects
the
ledger
are
in
the
wallet
and
they're
encrypted,
but
the
and
that
encryption
of
the
wallet
is
what
we
have
to
watch.
So
that's
the
from
an
enterprise
perspective
to
the
key
management
perspective.
Right
now
is
it's
making
sure
that
we
can
that
we
know
we
have
the
keys
for
the
wall,
you
know
lose
them
and
that
we're
doing
proper,
backups
and
proper.
A
There's
basically
so
we've
got
the
information
that
when
we
receive
a
credential,
we
store
the
credential
and
the
wallet
and
that's
kind
of
the
hyper
ledger
in
the
model.
So
all
the
information
is
in
the
wallet.
We
also
keep
there's
a
second
database
that
we
keep
some
information
in
for
searching
because
searching
through
the
wallet
for
certain
types
of
searches
is
just
very
inefficient
and
we've
got
like
a
solar
search
engine
as
well.
So
we
keep
all
of
that
information
outside,
but
we've
got
the
capability
of
rebuilding
all
of
that.
A
E
E
C
If
the
revocation
was
because
they
just
reissued
a
new
one,
they
would
probably
say:
hey
I
revoked
it,
but
here's
a
new
one
you
can
have
and
that
person
would
request
again
the
best
kind
of
the
bottle
that
he
has
when
the
person
goes
to
prove
that
potential
again
ticket
prove
that
it
was
issue
they
approved.
That
was
issued
to
them.
C
C
C
On
medication-
and
why
had
directed
the
paper
versus
what
we've
accomplished
to
tell
any
finding
right,
they
get
issued
me
a
proof
request.
A
bear
claw
could
send
the
approve
requests.
I
can
prepare
an
approved
and
after
I
send
it.
The
issue
were
repulsive
at
that.
Second,
the
verifier
is
going
to
think
it's
not
been
revoked.
So
there's
this
fight.
We
know
moment
that
comes
into
it
against
busy.