►
A
B
Operations
plug-in
pdid
or
unfortunately
named
pure
id
right
now,
all
right
so
pseudo
pacman
dash
s
y
y
git
git
is
not
installed
on
this
thing
wow
I
had
really
not
gone
far
through
setup.
Then.
B
B
B
B
B
B
B
Docker,
okay,
so
I
think
what
we
can
do
is
we
could
use
our
switch
route.
How
can
we
do
this.
B
How
do
they
do
the
ab
updates
on
android?
I
never
got
that
nailed
down.
B
We'll
just
mount
the
root
directory
as
a
volume
into
there
so
run
it
so
we're
as
if
we're
going
to
treat
the
container
as
if
we're
a
live
image
pointed
at
the
running
system,
so
docker
run
v
root,
mount
okay,
so
we're
mapping
root
to
mount
we're
running
arch,
linux
and
papa's,
a
shell
great.
So
let's
check
out
mount
so
what's
in
there,
it's
our
operation,
not
permitted.
B
B
B
B
I
forgot
to
start
these
with
dash
dash
rm,
rm,
I.t,
arch,
linux,
okay,
ls,
laf,
okay,
so
we're
having
we're
seeing
there's
a
permissions
problems
that
happen
with
docker
every
so
often
we're
running
into
them
right
now,
probably
because
we're
running
on
an
old
version
of
the
kernel
here
or
something
it
doesn't
really
matter,
we're
actually
gonna,
say:
rmti
tail
dash,
f
devnull,
and
this
should
just
leave
the
container
running
for
us
now.
We
should
be
able
to
do
docker
ps,
all
right
there.
It
is
okay!
B
So
now
we
can
do
docker
cp
and
let's
check
out
mount
or
let's
just
ll,
let's
mount
a
ram
disk,
so
we're
going
to
mount
a
ram
disk
and
then
basically
see
it
root
into
the
maram
disk.
B
B
B
Let's
see
what
happens
and
mount
all
right
there.
It
is
okay.
The
question
is:
is
this
running
from
a
ram
disk?
Let's
find
out.
B
B
B
None
of
that
should
have
done
anything
like
that.
It
was
hanging
on
me
hard.
Let's
see
like
really
weird
hanging,
okay,
we're
gonna
sort
of
we're;
gonna
assume
it's
this
weird
docker
process
here.
B
B
B
B
So
we
are
no
longer
going
to
use
this
ssi
import
service
gateway,
so
we're
going
to
modify
our
data
flow
here.
We're
just
going
to
include
this
one
peer
id.
B
One
for
now
so
we're
basically
just
saying
which,
which
one
to
use
and
we're
going
to
comment
out
that
one
and
because
it's
it's
we're
setting
the
config
by
name
as
well.
So
we
need
to
not
do
that.
B
B
It
just
it
just
breaks
and
I'm
also
way
too
cheap
to
buy
new
hardware
or
pay
50
cents
for
a
digital
ocean
droplet.
So,
okay,
maybe
that's
the
root
of
our
problem
here.
Maybe
I
should
just
be
less
cheap,
no
distributed
computer.
B
B
So
we
want
to
create
some
signing
keys,
let's,
let's
mess
with
this
a
little
bit.
So
what
happens?
If
we
change
this
just
see
if
anything
breaks
off
the
bat
okay
now
looks
like
that's
coming
through:
okay
I'll
go
one
resolve
peer
id.
The
id
docs
here
and
I'll
go
as
for
resolve.
Prd
pure
did
resolve
period,
did
pdid
equals
pdid,
algo1,
pdid,
algo1,
okay,
so
these
print
out
the
identifiers
themselves
and
then
look
at
this
algo2
looks
like
it's
actually
using
a
json
web
token.
B
So
what
is
the
difference
here?
So
this
one
used
this
encryption
keys
in
science
key,
so
this
used
this
num
I'll,
go
zero
use
this
inception
key
and
it
said
signing
key
zero
and
then
this
ml
go
to
use,
signing
keys,
okay
and
then
it
it
came
up
with
this
okay.
So
what
do
we
do
here?
B
B
Okay,
two
point:
okay,
so
this
algo2,
I
don't
know
what
the
algo2
significance
is.
What
happens
if
we
remove
this
algo1
signing
key
zero.
B
B
B
B
B
How
do
we
use
this
thing?
How
do
we
use
this
thing?
Okay,
so
I
get
grab
did
doc
peer.
Did
okay,
okay,
we're
not
in
a
gate,
repo
grip,
rn,
pure
d,
id
doc
pdid.
Where
are
we
okay,
we're
on
host
name
we're
on
this
system?
Okay,
so
crazyness
json,
okay,
pure
d
id?
What
is
this
pure
did?
So
I
don't
understand
the
difference
between
pda
id
and
pdid
doc.
I
think
pdid
wraps
did
doc,
create
prd
generates
a
pd;
okay,
no
mal
go
to
according
to
the
second
algorithm.
B
Okay,
for
this
type
of
algorithm
did
doc
can
be
obtained
from
pure
d
id
okay
signing
keys.
Encryption
g
is
json
c
we're
going
to
did
specifications
so
the
did
okay,
so
the
did
doc,
so
it
generates
prd
according
to
zero
algorithm.
Okay,
so
we
need
to
read
this,
for
this
type
of
algorithm
did
document
be
obtained
from
peer
id?
Okay,
so
remember
we
want
a
document
we
want
did
doc
right.
We
want
to
figure
out
how
to
put
our
manifest
in
there.
Okay,
let's
read
this
okay,
so
this
is
oh
yeah.
B
We
had
to
add
this
up.
Okay,
so
here's
our
method,
prefix
num,
algo,
okay,
the
number
of
the
algorithm
okay,
so
there's
version
one
in
version
version
zero,
one
two,
maybe
some
other
ones-
we've
seen
version
zero
and
version
two.
So
far.
Okay,
in
this
version
of
spec
multi
codec
descriptor
for
algo
num
algo
equals
equals.
Zero
is
depending
on
key
type
and
exactly
matches
the
descriptor
that
will
be
used
for
the
same
value
of
did
key.
B
The
multi
multi
codec
description
for
gnome
algo
equals
one
is
bite
pair
blank
blank
blank
1220
hex
1220,
which
says
that
it
falls
shot
to
256
hash,
32
bytes
long
size
is
included
because,
although
shot
256
is
known
to
be
a
good
produce,
32
by
target
checks,
other
hash
algorithms
has
very
little
link.
So
why
don't?
Actually?
Why
don't
we
leverage?
I
think
we
need
to
comment
back.
Let's
comment
back
to
brooklyn
on
that
ucan
thread
where's,
that
discussions;
okay,
where's,
that
you
can
thread.
B
See
this
is
what
I
want
to
be
like
alice
where's.
The
ucan
thread.
Can
you
comment
on
the
ucan
thread?
Just
would
be
great
right.
We're
gonna
make
it
happen.
Okay,
so
kodak
freedom,
okay,
so
so.
B
Okay,
so
I
believe
that's
what
I'm
reading
here
so
method,
specific
identifier,
so
core
characteristics,
method,
name
peer,
okay,
the
id
must
be
gonna
fly
did
pure
okay.
So
this
is
a
pure
d
id
okay,
so,
okay,
so
different!
Oh,
you
can
have
different
distributed.
B
Okay,
okay,
this
makes
more
sense.
Okay,
so
you
have
your
did
spec,
which
is
the
core
of
everything
you
have.
Your
peer
did
spec,
which
really
finds
this
is.
This
is
the
thing
we
care
about
this
linkage
right
and
then
the
tb
decks
folks
they
have
their
message
protocol,
which
would
which
is
using
dids
and
they
care
about
the
coins
that
are
within
the
ids
they're
using
this
json
web
message.
Thank
god!
That's
another
great
thing!
God
all
these
people
are
defining
so
much
stuff
within
like
the
web
space
if
you've
done
web
development.
B
You're-
probably
loving.
All
of
this,
so
okay,
the
id
key,
okay,
okay,
okay,
so
did
key.
Is
that
thing
that
we
saw
from?
We
saw
the
id
key
from
where
was
it
last
night
I
may
have
been
off
the
stream
I
was
poking
around,
but
not
that
much
mostly
just
trying
to
get
things
booting
so
did
key
di
nacl
nacl
is
is
is
is,
is,
is
lightweight
id
method,
complete
with
identity
creation
tools,
encryption
json
web
token?
B
Signing
repository
has
been
arc,
okay,
so
use
the
id
key,
so
basically
forget
about
that.
So
did
key.
Okay,
the
id
key
transmute.
Okay,
let's
grab
this
okay,
the
id
method
specification,
okay,
did
method
which
is
offline,
friendly
love,
beloved
cryptographically
self-certified
requires
no
trusted.
Blockchain
certificate
or
sturdies
is
a
deal
for
ephemeral
use
under
construction.
Okay.
So
we
have
an
ephemeral
use
case
with
these
little
inputs
right
there
they're
there.
B
We
want
to
be
able
to
blow
them
up
when
when
we
want
to
get
rid
of
them
within
the
cached
service,
so
it
looks
like
looks
like
did:
nacl,
okay,
so,
okay,
okay,
to
help
okay,
to
help
us
understand
better
method,
spec
identifier,
so
oops,
okay,.
B
Is
deprecated
in
favor
of
the
id
key
which
will
be
used
by
tb?
Dex
folks
did
is
the
linked
list.
Version
of
the
ids
so
did
peer
okay,
so
these
are
like
package
urls
and
then
each
underneath
them
beautiful,
beautiful
beautiful.
So
basically
you
say
this
is
my
name
space
right,
so
d
id
this
is
a
distributed
identifier.
What
namespace
does
it
exist
in?
How
do
you
interpret
the
format?
So
this
is
a
manifest,
so
the
manifest.
B
B
It
tells
us
format,
version
optionally,
encoded
for
peer
did
encoded
into
numalgo,
which
is
this
method
specific,
which,
which
is
maybe
this
method
specific
identifier.
B
So
we
could
say
pure
the
ids
allow
for
multiple
codex
should
this
should
that
be
considered,
let's
practice
some
followers
in
this
instance.
Okay.
I
think
that
is
what
we
want
to
know
so
method,
specific
identifier,
core
characteristics:
okay,
let's
actually
link
to
core
characteristics,
because
that
is
a
little
bit
more
helpful.
B
B
B
Did
key
method
specification
did
method
which
is
offline
friendly?
Okay.
So
what
is
the
did
method?
I
think
I'm
not
understanding
what
that
is.
Resolution
methods,
okay,
so
dod
method
must
define
exactly
one
message:
specific
did
scheme
that
is
identified
by
exactly
one
method
as
specified
by
the
method
name
of
the
did
syntax.
The
did
method
specification
must
buy.
It's
gonna
specify
how
to
generate
the
method
specific
id
component
of
this
id.
Oh,
this
is
good.
B
B
B
B
B
Should
we
be
looking
at
context?
Authentication,
let's
go
run.
This
thing
again
show
me
what
it
looks
like:
okay,
so
service
key
agreement,
authentication
service,
okay,
so,
okay!
So
I'm
thinking
how
do
we
relate
one
peer
d
id
to
another
period
to
a
non-pure
d
id
we
want
to
relate
it
to
another?
Did
okay,
so
we
want
to
create
distributed.
Identifier.
B
Okay,
so
let's
see
the
software,
we
obvious
studio
connection,
all
right,
so
keys,
it's
going
to
be
used
by
tv.
Dex
peer
is
going
to
be
used
by
us
to
relate
the
ids
okay.
So
this
version
of
the
spec-
okay,
okay,
so,
is
dependent.
So
num,
okay
inverse
this
version
of
respect
to
multi
codec,
descriptor
descriptor,
so
multi-codec
descriptor
where's,
the
multi-codector
script.
Okay,
this
is
just
the
multi-codec
descriptor
for
num.
Algo1
is
dependent
on
the
key
type
in
executive
measures
and
we'll
be
using
the
same
value
in
did
key
okay.
B
So,
basically,
so
when
amalgal
equals
zero,
the
cold
multi
for
this
version
of
spectrum,
no
multi-codec
descriptor
for
gnome,
okay
multi-codec,
is
here
in
the
method.
Specific
identifier,
composition
of
the
pdid
value
is
base
58
to
income
bias.
I
have
no
idea.
I've
never
seen
those
before
transform,
z
means
base,
58,
numeric
bias,
okay
and
invasive
spaces,
and
that's
what
we
said:
okay,
so
multicultural
by
pair,
which
says
that
the
fall.
What
falls
is
okay,
so
multi-codec
descriptor?
B
Okay,
so
this
is
okay,
it's
32
bytes
when
it
when
it
means
sha256
hash,
says
it
policies,
okay!
So
basically,
when
you
see
a
multi-codec.
B
Of
which
is
two
bytes
looks
like
multi-codec
itself
is
the
multi-codec.
Descriptor
is
two
bytes
long.
It's
dependent
on
the
key
type
of
executive
measure.
Descriptor
multi-character
scripture
from
numalca1
is
bypair,
okay,
okay,
so
no
when
it
is
now
mal
goes
zero.
B
B
B
We
should
discrete
treat
the
descriptor
as
if
it
it
conforms
to
the
did
key
spec,
okay,
multi-coded
descriptor
for
number
one.
Is
this
thing
that
signifies
shaft
250
shot
256,
and
it
says
that
the
numeric
basics
that
follows
is
a
shot
256
hash,
which
is
32
bytes
long.
B
B
The
transform
is
base
58,
representative
and
multi-base
prefix
z,
okay
b
to
base
58
btc,
and
the
a
f
means
bitcoin
base
58
character
inventory.
For
brevity,
we
omit
the
expansion,
see
the
rejects
matching
for
details.
The
format
of
the
did
value
is
intended
to
be
future
proof
offering
through
external
self
okay.
So
I
think
we
can
safely
comment
to
brooklyn.
Now.
B
B
B
All
right,
we'll
just
say
we
just
noticed
this
right,
then
she
can
do
whatever
she
wants
with
that
information,
okay,
so
method,
zero
inception,
key
without
doc
method.
One
genesis,
doc,
creator,
genesis
version
of
the
did
text
from
the
did
doc
for
the
the
genesis
version
must
define
a
single
key
with
a
registered
privilege.
The
inception
key
should
is
a
key
that
creates
the
did
and
authenticates
with
exchange
with
the
first
period,
should
also
include
this
enough
state
that
subsequent,
if
evolutions
to
the
dock
are
authorized.
B
Otherwise,
the
dock
is
static,
suitable
only
for
layer,
two
use.
Okay,
we
only
want
a
satellite
dock
right
now.
It
must
not
include
the
did
itself,
either
the
root
id
property
or
its
value.
This
lets
the
dock
be
created
without
knowing
the
did's
value
in
advance,
so
pressing
did
value,
creates
a
stored
variant
of
the
pure
d
id
as
opposed
to
a
resultant
variant.
Okay,
basically,
you
sort
of
get
into
this
problem
of.
B
What's
the
actual
hash
is
my
guess,
for
example,
each
controller
property
of
a
verification
method
that
it
is
owned
by
this
did
would
say.
Controller
id
calculate
the
hash
of
the
bytes
in
the
variant
of
the
genesis
version
of
did
make
the
value
by
hashing
the
stored
variant.
We
avoid
the
circular
problem
at
c
of
the
d
id
that's
in
the
data
that
being
half.
That
means
that
the
prdid
dot
must
be
resolved
by
converting
a
stored
variant
of
the
d80
doc
into
a
resolved
variant.
B
Transfer
version
of
the
id
dock,
the
pid
can
begin
its
lifecycle
with
any
number
of
keys
and
endpoints,
including
protective
m
of
n
policies.
Inception
key
is
part
of
the
genesis
state.
That's
true
bedrock.
The
information
is
optimal.
It
can
be
thought
of
as
a
sort
of
pre-rotation
and
pre-evolution
which
my
insects
trust
for
period
dids
in
this
root
of
trust
for
pdids
in
the
entropy
in
is
the
entropy
and
the
inception.
Key
the
inception,
p
must
be
new,
for
each
gid
must
not
be
ever
be
reused
and
must
okay.
B
B
B
Okay,
multiple
inception
key
without
doc;
okay,
so
that's
version
two
and
that's
what
we
saw
here,
basically
right
and
so
basically
this
looks
like
there's
some
kind
of
number
I'll
go
to
similar
to
zero
ability
to
specify
additional
keys
in
the
generated
did
dock.
This
is
necessary
with
both
the
christian
key
and
signing
key
are
required.
B
First
glance:
it
seems
that
parties
dealing
with
npr
did
doc
should
just
store
raw
did
docs.
However,
this
is
only
viable
answer
for
the
lower
two
layers
of
support
for
pdids
anytime.
A
did
doc
evolves.
Proof
that
the
evolution
is
authorized
must
be
found
in
the
did.
Doc's
previous
state,
an
agent
is
offline
for
an
extended
period,
bonus
loss.
Multiple
evolutions
may
have
occurred
by
the
time
it
reconnects.
It
cannot
accept
the
latest
state
of
the
dock.
B
Without
validating
the
sequence
of
changes
it
underwent
to
get
there,
agents
must
be
able
to
prove
to
one
another
that
the
state
they
hold
is
correct
and
when
they
must
answer
questions
about
what
the
state
used
to
be
and
who
authorized
changes
when
this
means
that
updatable
peer
id
did
docs
need
to
be
associated
with
some
kind
of
backing,
storage
adds
metadata
and
history
to
the
simple
content
of
the
docs
themselves.
Backing
storage
is
updatable
pdid
docs
for
update.
B
B
B
B
B
B
B
B
Let's
make
sure
we
understand
this
ham
event
updated.
It
doesn't
contemplate
custom
authorization
such
as
pierce
might
develop
to
give
each
other
spending
limits
or
access
sensitive
data.
These
matters
are
better
formalized
with
some
of
the
comparable
credential.
This
is
where
we
talked
about
our
provenance
information
right
and
we
can
use
the
dids
and
the
providence
information
together
to
you
know,
build
build
out.
You
know
our
chains
of
trust
and
decide
what
we
want
to
do
with
this
information.
B
B
B
B
B
Objects,
maybe
during
right
out,
okay,
let's
take
a
look
at
the
other
methods,
see
if
somebody.
A
B
The
id
method
method
registry
did
I
put
that
link.
I
did
put
that
link
great
okay,
the
id
we're
all
dude
yeah.
This
is
the
thing
that
I
saw
that
I
was
like.
This
is
great.
That's
how
I
knew
we
liked
this.
So
what
are
methods.
B
B
B
Okay,
there
is
one
there's,
a
repo
that
has
all
of
these
distributed
identifiers
registered.
B
B
Suggest,
including
descriptions
names,
not
entire,
a
helpful
right.
This
is
the
problem
anytime.
You
do
something
like
this,
where
you
let
everybody
create
whatever
identifiers
they
want.
You
end
up
with
several
of
them,
meaning
the
same
thing
usually
so.
Unfortunately,
I'm
worried
that
we're
going
to
go
risk
putting
in.
B
B
B
Yeah,
this
stuff
is
for
sure
the
future
I
mean
the
interoperability
here,
it's
it's
confusing
because
of
all
the
layers
of
indirection
right,
but
the
interoperability,
obviously
the
layers
of
indirection.
This
is
exactly
what
we've
been
doing.
You
know
here
too,
is
just
you
know.
By
introducing
these
layers
of
abstraction,
you
get.
You
know
huge
potential
for
interoperability
right
now.
What
is
this
here?
Just
boxing
for
single
dig
proof
of
specific
address.
Okay,
I
think
let's
go
ahead
and
see
what's
out,
there
did
null.
B
B
Okay
looks
like
pure
dids
do
that
mutations
are
unique,
explainer
that
created
90,
different
protocols
and
data
silos
is
beyond
my
comprehension,
okay,
but
this
is
the
thing
by
this
is
the
prop.
This
is
the
thing
this
is
it's
hard,
but
by
exposing
the
data
model
you
allow
for
people
to
you
allow
for
analysis
to
tell
us
what
is
okay,
we're
gonna
work
on
this.
B
Okay,
salsa,
okay,
deity
documents;
okay,
these
people,
don't
you
write
like
id
uris,
inflates,
identification
with
location,
causing
click,
chaos
and
implementation.
It
says
the
id
string
identifies
the
dna
subject
and
resolves
it
by
creating
a
standard
ui
that
both
it
has
created
a
ridiculous
explosion
of
pet
storage
and
provenance
solutions,
each
one
having
their
own
decentralized
identity
method
and
the
registry
yeah
those
that
you
require
access
to
a
running
node.
B
Okay,
second
flaw
is
ignoring
the
fact
that
test-based
documents
were
chosen
for
byte-sensitive
digitally
assigned
documents.
The
existing
standards
simply
doesn't
meet
the
requirements
of
internet
sales,
provenance,
visual
identity
solution
did
documents
completely
ignore
time
dimension,
but
more
precisely.
They've
provided
no
solution
for
digital
identities
over
time.
B
B
B
Well,
we'll
reach
out
to
dave
and
see
if
he's
been
up
to
anything,
because
we
want
to
make
sure
we
get
his
inputs.
Obviously
he
did
some
thinking
on
this
reach
out
to
dave,
to
see
why
to
see
if
anything
has
been
up
with
his
evolution
off
the
ids
all
right.
So,
let's
just
I
think
the
ids
are.
You
know
we
can
at
least
like
we
talked
about.
If
there's
something
wrong,
it's
okay,
we
just
make
a
did.
B
B
B
A
B
B
B
B
B
The
the
top
level
system
context
will
be
something
that
reads
the
did
in
this
case.
This
is
the
next
contact
we
want
to
know.
Where
do
we
get
this
information
right?
So
let's
go
ahead
and
make
sure
that
our
url
is
what
we,
what
you
know,
other
people
would
think.
So,
let's
do
you
know
diff
mild
dot
or
github
dot
io
slash
to
file
slash,
did.
B
B
B
B
Id
so
maybe
maybe
we
can
oops
sorry
open
architecture,
service,
endpoint,.
B
B
B
Did
I
name
it
run
subflow
somehow,
no
idea.