►
From YouTube: IPFS Community Meetup - May 2021
Description
This month we have quite a range of guests lined up that we are happy to introduce to the IPFS community. We hope you join us for talks from:
- Yiannis Psarras of ResNetLab, to present “ResNetLab on Tour,” as well as provide an update on the upcoming DI2F Workshop.
- Wayne Chang of Spruce Systems, to present how Spruce Systems is reimagining trusted interactions through the creation of new identity infrastructure.
Register to attend so you don’t miss out!
https://protocol.zoom.us/meeting/register/tJAsde-spj0uH9bHZh2b3lW66hogMAFzeOmd
A
A
A
A
A
But
okay,
so
I
think
we
are
ready,
we're
ready
to
to
start
to
meet
up
really
happy
to
have
you
here.
So
a
few
reminders,
this
event
divides
by
the
ipfs
community
code
of
conduct.
You'll
be
able
to
find
more
about
it
in
the
chat.
Please
ask
all
the
questions
in
the
chat.
Look
it
on
the
right
hand,
side
of
your
screen.
The
speakers
will
be
able
in
the
team.
I
will
be
able
to
answer
all
the
questions
there.
A
If
you
like
to
watch
our
past
events
or
actually,
if
you'd
like
to
watch
this
event
again,
it
will
be
available
on
ipfs,
youtube,
page
and
we'll
also
be
linked
below
and
if
you're
interested
in
speaking
our
future
ipfs
meetup,
you
can
email
us
as
well.
We
love
you
to
have
you
and
to
know
more
about
the
project
you're
working
on
and
for
today
we
have
three
amazing
presentations.
B
A
C
C
C
D
E
F
F
Okay,
hello,
everyone.
Let
me
start
then,
and
I'm
going
to
start
with
this
great
magic
bus,
which
is
a
bus
that
took
us
on
a
while
tour
during
20,
late,
2019
and
2020,
and
the
rest
net
lab
members.
Resilient
networks
lab
members
from
protocol
labs,
we've
been
to
several
different
conferences
and
event
where
we
presented
the
web.
3
stack
talked
about
ipfs,
sleep,
b2b
and
all
these
great
work
that
is
happening
in
this.
In
this
community
we
talked
to
thousands
of
academics
and
phd
students
and
researchers.
F
F
These
are
all
20
minutes,
20
to
30,
minute
tutorials,
which
you
can
find
on
this
page.
There
are
several
like
lots
of
resources
around
for
each
module.
You
can
find
related
links.
You
can
find
a
list
of
our
open
problems
where
we're
looking
for
other
community
members
and
researchers
and
university
labs,
but
not
only
to
come
and
work
with
us
to
solve
these
problems.
So
there
are
lots
of
links
here.
F
You
can
also
find
the
slides
of
every
module
which
you're
free
to
download
and
reuse.
If
you
are
organizing
a
lecture
or
a
meetup
or
any
related
events,
you
feel
free
to
get
the
slides
and
reuse
them
and
we
are
going
to
have
more
coming.
So
we
have
the
core
modules
that
talk
about
the
core
of
the
ipfs
and
the
web.
3
stack,
but
we're
going
to
go
a
step
further
and
talk
about
more
in
depth
about
some
of
the
parts
of
of
those
types.
F
F
What
you
can
also
find
is
a
list
of
the
blog
posts
that
we've
written
after
every
event
we've
been
at,
which
is
a
great
resource
because
we
are
answering
there
all
the
questions
and
answers
that
we
get
from
the
audience
and
it's
great
to
follow
up.
There
is
lots
of
material
there
that
you
can.
You
can
find
out
about
ipfs
and
every
module
that
we
are
basically
presenting.
F
So
this
is
just
a
snapshot
of
the
places
that
where
we've
been
and
we're
populating
it
as
we
as
we
go
along
you
can,
there
is
a
form
if
you
want
to
get
in
touch
and
invite
us
or
others
in
the
community
to
come
and
present
those
those
modules
to
your
audience,
and
there
is
a
github
discussion
repository
where
you
can.
You
can
start
discussions,
ask
more
questions,
make
suggestions
and,
and
so
on,
I'll
post
all
those
links
in
the
chat
afterwards.
F
For
now,
I
would
like
to
jump
to
the
second
part.
I
come
as
a
three-in-one,
so
I'm
going
to
be
presenting
two
things
in
in
one
slot.
So
that's
the
second
one.
We
are
organizing
a
workshop
alongside
a
big
conference
in
computer
networks,
which
is
called
ifip.
Networking
is
hosted
by
ifip
and
the
title
of
the
workshop
is
decentralizing
the
internet
with
ipfs
and
filecoin.
It
takes
place
on
the
21st
of
june
2021
and
there
are
going
to
be
several
interesting
topics
covered.
We
have
eight
paper
presentations.
F
F
Of
course,
after
the
event
it's
going
to
last
for
a
couple
of
weeks,
there
are
going
to
be
prizes.
The
details
again
are
not
set
in
stone
yet,
but
they
are
going
to
be
in
the
next
couple
of
weeks,
so
stay
in
touch
register
in
order
to
receive
all
the
updates
and
get
in
touch.
If
you
have
any
questions,
thank
you
very
much.
That's
me.
A
C
A
C
A
C
Good
good,
so
hello,
everyone,
my
apologies
for
the
connection
problems
prior
on
a
previous
opportunity,
so
welcome
to
everyone
to
almonds.
I'm
going
to
just
gonna
quickly
tell
you
what
it
does
and
what
we
do,
who
we
are
and
the
presentation
is
divided
into
into
two
parts:
one,
I'm
gonna
talk,
I'm
gonna
be
talking
about
the
non-technical
parts
of
it
and
the
the
second
part
which
will
be
covered
will
be
by
mohammed.
C
C
So
we
so
what
we
mean
by
that
it
means
we
we're
trying
to
decentralize
a
piece
of
internet,
bringing
a
little
bit
more
value
in
the
censorship,
resistant
areas
and
privacies,
as
well
as
the
robot
robustness
of
the
of
the
technologies
that
lays
behind
the
ipfs
or
ens
yep.
So
you
can
see
that
my
name
is
christopher
levos
and
I
am
a
co-founder
as
well
as
our
lead
operation.
Mohammed
is
another
co-founder
as
well,
and
he
is
a
technical
lead.
C
C
C
C
Sorry
websites,
as
you
can
see,
there
is
a
if
you
go
to
harmony.eth.link
the
first
thing.
What
you
see
is
actually
a
decentralized
website
itself
and
it's
our
search
engine.
It
is
just
the
basic
version
of
the
search
engine.
It
works
quite
okay,
but
we
haven't
spent,
spend
so
much
time
on
it
only
because
we
realized
how
important
for
us
actually
is
to
create
another
tool
that
actually
will
will
help
all
users
across
the
globe
to
easily
access
the
decentralized
web,
but
also
help
them
create
decentralized
websites.
C
C
C
C
C
It
is
also
decentralized.
So
that
means
there
is
no
single
point
involved.
It
is
also
censorship.
Resistant.
No
one
can
sense
that
the
content
apart
from
its
members
and
what
most
important
there's
no
technical,
no
technic,
no
technicality
needed
in
order
to
use
it.
So
no
developer
skills
and
anyone
can
go
in
and
just
create
a
decentralized
website
in
a
few
and
easy
steps.
C
C
So
what
exactly
alpres
is
offering
operas
is
offering
you
know
it
combines
three
different
technologies.
One
technology
behind
it
is
ipfs
for
storage
services,
but
also
ens
for
the
domains,
but
also
as
well.
The
dow
and
the
dao
in
this
case
is
actually
presented
as
a
str.
So
ens
and
ipfs
technologies
are
the
core
technologies
behind
the
behind
the
the
rps
project.
C
What
most
important
as
well
is
that
anyone
can
use
it,
and
it's
really
so
easy
to
to
create
an
account
within
the
address.
All
you
need
is
just
a
quick
access
to
the
metamask
via
the
metamask
wallet
in
order
to
complete
couple
of
simple
transactions,
and
the
registration
process
is
really
really
easy.
E
E
It
stands
for
the
centralized
autonomous
organization,
so
it's
like
a
sort
of
a
decentralized
business
model
and
let's
use
also
users
of
all
press
to
govern
any
idea,
assets
or
decisions
by
giving
them
erotic
power,
and
this
is
the
part
which
transforms
our
press
to
self-governing
organizations
simply
with
built-in
self-moderation
mechanism,
and
today
I
will
only
demo
you
to
the
web
application
part
from
the
point
of
regular
web
user.
It
just
looks
like
a
traditional
web
application,
as
you
can
see,
but
the
main
difference
is
nothing
belong
to.
E
The
all
press
runs
on
any
centralized
server
means
the
application
request
goes
only
to
ipfs
and
ethereum
nodes,
no
analytics,
no
tracking
tracking
is
involved
with
it
to
interact
with
the
application.
Each
users
needs
just
a
wallet
and
currently-
and
unfortunately
we
only
support
metamask
at
this
stage
and
the
user
needs
some
test.
Eternium
tested
area
ether
simply
for
account
purchase,
and
if
anyone
wants
to
try
it
trade
out,
I
can.
I
can
try
to
be
helpful
about
that.
E
Login
and
registration
is
done
over
a
simple
button.
If
you
already
have
an
account,
the
application
will
take
you
to
your
account
and
if
not,
you
will
be
welcomed
with
registration,
wizard
and
currently
in
here
I
created
a
one
account
for
ipfs
and
I
have
to
test
it
here
and
when
I
click
the
connect,
because
I
don't
have
any
account,
it
will
just
take
me.
E
Each
user
has
a
username
as
we
call
it
handle
the
handles.
Are
the
subdomains
and
the
usernames
in
the
platform
it's
unique
for
each
user
and
every
account
can
have
only
one
handle
users
can
reach
their
profile
via
handle.
That's
I'll
press
that
t-e-t-h
or
e-t-h
or
e-d-h-dot
link
for
future.
Currently
we
are
just
using
ens
on
the
rink
by
test
nets,
so
it's
not
available
for
public.
E
Here
you
fill
your
auto
information.
Those
information
doesn't
have
to
be
correct,
we'll
leave
it
for
your
needs
or
to
your
imagination.
I
will
just
call
it
ipfs
and
I
will
pick
your
logo
and
let's
get
this
community,
look
call
it
like
that
and
after
filling
it
we
are
just
signing
up
and
metamask
pops
up.
We
just
confirm
the
transaction,
it
may
say
it
may
take
some
time
and
when
it's
done,
we
will
be
signed
into
our.
E
D
E
E
E
E
Soon
we
want
to
eliminate
this
multiple
transactions
via
ipns,
so
we
don't
have
to
update
our
ens
content
hash
each
time,
because
the
the
how
it
works
is
simply
whenever
we
publish
something
we
generate
a
new
content
hash
and
update
the
ens
with
the
transactions.
We
don't
want
to
do
that
after
the
registration
and
as
you
can
see,
this
is
our
first
first
block
and
when
I
go
inside,
it's
just
a
regular
block-
and
this
is
our
profile
simply
ipfs21
I'll
I'll
press,
the
th.
E
E
E
A
C
Yes,
absolutely
thank
you,
so
basically
I
just
wanted
to
to
let
you
know
that,
obviously,
it's
a
really
really
cool
project.
It's
aiming
to
change
quite
a
bit.
You
know
and
in
a
nutshell,
it
is
also
worth
mentioning
that
the
sgo
model,
that
is
behind
the
alpress,
you
know
it's
it's
it's
a
new
type
of
organization
that
operates
within
the
internet
boundaries.
It
is
owned
and
governed
by
its
by
its
users.
It's
an
alternative
to
commercial
control
of
the
internet.
C
We
could
clearly
we
could
even
say
that
it
brings
democracy
in
the
internet
and
the
unique
value
proposition
of
that
is
that
it
gives
back
the
users
the
power
to
decide
whatever
the
matter
is
to
be
discussed
or
published
and
not
the
corporations.
So
I
think
this
is
the
kind
of
big
big
step
for
us
to
to
see
if
we
can
actually
achieve
something
about
that
and
yeah,
so
this
is
ours.
A
Amazing,
thank
you,
so
yeah
feel
free
to
answer
any
questions
in
the
chat.
Amazing.
Thank
you
for
joining
us.
So
our
last
speaker
for
today
is
wayne
from
spruce
systems
to
present
house.
First
systems
is
reimagining
trusted
interactions
through
the
creation
of
new
identity
infrastructure
wayne
welcome
hi.
B
So
I'm
here
to
talk
to
you
about
kepler
kepler
is
a
decentralized
storage
network,
organized
around
data,
overlays
called
orbits,
and
it's
built
using
ipfs.
It
supports
many
different
kinds
of
storage
back-ends
and
the
goals
of
it
are
to
provide
permissioning.
For
example.
How
do
you
delete
stuff
from
ipfs
today?
There's
probably
a
lot
of
answers
that
we
can
figure
out,
but
we
want
to
figure
out
a
pretty
canonical
way
to
control
that
for
people
who
do
need
to
delete
things
to
comply
with
things
like
gdpr
or
the
ccpa
here
in
the
states.
B
So
that
means
we
need
some
kind
of
permissioning.
Ideally
if
it's
a
key
based
and
also
capability
space
and
I'll
get
into
that
in
a
bit
and
the
ability
to
talk
about
where
you
actually
want
the
data
to
live
right.
What,
if
you
have
ipfs
nodes
everywhere?
How
do
we
constrain
it
to
a
single
country
or
a
single
building?
Maybe
your
basement,
you
know
how
do
we
make
sure
your
iot
data
can
kind
of
stay
in
your
house
and
not
get
eaten
up
by
a
cloud
provider
or
something
like
that
right?
B
D
B
So
what's
an
orbit
well,
an
orbit
is
something
it's
a
data
overlay
defined
by
an
orbit
manifest
resolved
by
what
we
call
an
orbit
identifier.
So
they
can
live
in
a
bunch
of
places.
We
like
smart
contracts
because
it
actually
solves
a
lot
of
the
problems
such
as,
if
you're
setting
permissioning
who's
the
orbit
commander
who's
in
charge.
Here,
they
can
set,
who
can
read
and
write
it,
and
you
can
actually
just
use
the
smart
contract
itself
to
gain
the
access
to
changing
the
base.
B
Permissions
updateable
dhts,
as
we
see
ipfs
and
ipfs
log
from
the
orbitdb
project,
not
really
it's
kind
of
related
to
kepler
and
orbits,
but
a
different
project.
I
spoke
to
the
orbit
db
team
and
you
know,
thankfully
it
seems
that
they're
not
too
upset
that
we
decided
to
call
capital
orbits
orbits,
but
they
are
different,
but
orbit
manifest
live
there.
They
could
live
as
ceramic
documents.
Textile
instances
even
carry
event
logs
in
the
decentralized
identity
community.
B
There
is
something
called
carry
the
key
event
received
infrastructure
that
can
also
serve
this
purpose.
The
idea
is
that
we
have
a
new
url
where
the
hosts
are
actually
defined
in
a
smart
contract
controlled
by
the
user.
So
you
truly
own
your
data,
in
that
you
can
direct
people
where
to
find
the
hosts
authorized
to
host
your
data,
and
then
we
use
content
identifiers,
as
you
might
expect
in
ipfs.
B
So
this
way
and
there's
some
other
information
too,
that
define
aspects
of
the
orbit
such
as.
What's
the
base
permission
model,
as
I
mentioned,
when
we
issue
capabilities,
what's
the
valid
validity
status
there,
either
a
certificate
revocation
list
or
a
cryptographic
accumulator
can
be
used
and
then
content
state.
What's
the
latest
merkle
root
hash
of
content?
What's
our
consistency
strategy
and
what
are
the
authentication
methods?
We
support?
Here's
some
example
of
identifiers
this
might
this
one
is
based
on
the
tesla's
blockchain
has
an
account
has
a
predefined
host.
B
You
can
have
implicit
parameters
as
part
of
the
orbit
identifier,
so
you
don't
even
have
to
deploy
a
smart
contract
if
to
be
able
to
have
some
strict
defaults.
You
can
also
use
a
smart
contract
and
just
source
it
from
there.
That's
fine
too,
and
then,
in
order
to
turn
a
kepler
identifier
to
kepler
url,
you
either
put
the
identifier
as
is,
or
you
hash
it,
and
then
you
can
refer
to
the
content
identifier.
B
B
This
is
an
example
of
some
of
the
data
that
you
might
find
in
the
orbit
manifest
that
you
resolve
from
your
favorite
block,
shade
from
ceramic
from
textile
any
of
these
services
that
support
this
kind
of
document,
update
methodology,
so
you
might
find
out
who
the
orbit
commanders
are.
Who
is
really
in
charge
of
all
the
stuff?
Who
can
read
and
write?
Who
can
delegate
those
permissions
as
capabilities
and
who
can
manage
the
host
list?
B
The
host
list
and
orbit
manifest
can
have
a
list
of
a
public
key
derived
identifier
to
ip
addresses
or
even
an
onion
address
content.
Hash
can
be
the
merkle
root
and
we
might
have
a
revocation
state.
We
need
to
maintain
what
capabilities
we've
issued
are
valid
or
not,
and
we
might
have
consistency
strategies.
Let's
say
you
don't
want
to
wait
for
a
merger
root
update.
You
want
a
faster
system
running
on
top
of
it-
maybe
byzantine
fault,
tolerant
across
all
the
hosts
in
the
orbit.
B
Well,
that
that
it
can
be
specified
also
with
the
policy
we
separate
content
and
policy
policy
changes
being.
If
you
want
a
lot
of
readers
or
something
you
don't
want
to
store
them
all
in
the
manifest,
because
it's
expensive
to
store
in
a
layer,
one
blockchain,
you
know
you
might
want
a
different
consistency
strategy
for
that
data.
We
try
to
separate
policy
and
content.
We
also
have
different
authentication
methods,
including
w3c,
verifiable
presentations
and
blockchain
specific
ones.
B
We
also
want
to
support
a
bunch
of
other
authentication
methods
from
web
authento,
feto2,
blockchain
wallet
signing
so
anything
anytime.
You
can
sign
something
with
a
blockchain
wallet
that
should
you
can
build
an
authentication
method
out
of
that
ssh
off
and
gbt
keys
are
good
and
even
looking
at
some
enterprise
people
who
want
x,
509
family
of
things
in
mutual
tls
being
able
to
configure
these
per
orbit.
So
it's
really
tailored
to
the
use
case.
B
The
capability,
it's
the
ability
to
do
something
like
right
to
an
orbit
up
to
500
megabytes.
Maybe
someone
wants
to
give
you
file
they're,
like
how
do
I
give
it
to
you?
You
can
give
them
a
capability
and
they
can
write
to
your
orbit
within
the
scope
of
that
capability
being
able
to
read
or
write
a
specific
content
hash
to
an
orbit
or
delegate
an
ability
to
someone
else
to
be
able
to
do
that.
B
So
we
wanted
capabilities
to
be
pretty.
We
wanted
them
to
be
secure.
We
wanted
them
to
be
expressive
and
we
wanted
them
to
be
pretty
useful
to
people.
So
we
have
something
called
cryptoscript
that
we're
working
on.
That
is
a
statically
typed
non
turing,
complete
dsl.
We
don't
like
turn
completeness
when
we're
just
trying
to
describe
things-
and
you
know
the
bitcoin
authors
and
a
bunch
of
other
folks
who
use
reduced
languages
for
security
purposes
and
simplicity,
that
we
took
inspiration
from.
D
B
But
being
able
to
check,
let's
say
an
nft's
owner
on
the
blockchain
make
sure
that
it
matches
with
the
person
authenticating
with
request
and
then
only
letting
the
nft
owner
download
the
content
for
that
nft
right.
That's
the
kind
of
permissioning
expression
that
we
want
to
be
able
to
have
here.
So
what
does
cryptoscript
look
like?
B
Well,
we
have
some
primitives.
Let's
say
that
we
want
to
convert
a
sec,
p256
k1
pub
key
to
a
bitcoin
address.
There's
a
pretty
deterministic
way
to
do
this,
that
a
lot
of
people
already
know
but
being
able
to
express
it
clearly
and
then
make
sure
that
it's
not
an
attorney-complete
language
makes
it
a
lot
easier
to
formally
verify
if
you
want
to
or
even
compile
to
an
implementation
in
a
different
language
such
as
cryptal
or
rust,
or
whatever
you
like,
so
you'd,
be
able
to
push
things
onto
the
stack.
B
Take
the
hashes
duplicate
things
as
necessary.
This
is
a
fourth
instared
stack
based
language,
but
it's
not
determined
if
it
needs
to
be
stacked
based
or
not
take
a
certain
number
of
bytes
concatenate
stuff
and
encode
it
with
base
58
check.
That's
how
you
get
a
bitcoin
address
from
a
public
key
of
this
type,
tezos
and
ethereum,
pretty
similar
even
simpler
for
tezos.
You
might
want
to
take
the
blade,
2b
hash.
B
D
B
And
you
drop
the
first
12
bytes
and
then
you'd
encode
it
in
base
58
check,
see
we
we're
basically
describing
how
to
get
from
point
a
to
b
in
a
very
crisp
and
unambiguous
way,
when
you're
trying
to
actually
write
c
and
like
work
with
pointers
or
borrow
checkers
and
rust
like
it
can
get
a
little
hairy
there.
So
having
this
pure
expression
of
it
is,
I
think,
a
very
useful
way
to
represent
it,
but
you
can
also
kind
of
talk
to
the
outside
world.
In
the
world
of
decentralized
identity.
B
We
have
something
called
the
did.
Web
did
method,
and
this
this
is
a
form
of
decentralized
identifier
resolution
where
you
just
query
a
website
over
tls,
and
you
can
implement
that
actually
with
cryptoscript.
If
you
have
a
few
libraries
that
understand
http
clients,
you
might
be
able
to
push
the
expected
path
past
the
method
specific
identifier,
concatenate,
the
two
strings
resolve
it
https
and
presumably
the
did
module
would
provide
a
validation
function
for
you
to
check.
D
B
Before
you
give
them
access
to
this
really
adorable
cat
picture
or
something
that's
large,
the
original
you
might
have
instructions
specific
to
those
assets
that
consume
the
asset.
Address
and
asset
identifier
pushes
an
address
onto
the
stack.
If
and
only
if,
successful,
and
then
you
might
take
the
vp
signer,
the
verified
presentation,
signer,
convert
that
to
a
public
key
hash
address
for
blockchain
and
then
assert
equivalence
between
the
two
addresses
on
the
stack
and
if
you
clear
it,
you
can
give
access.
B
But
if
you
don't
clear,
then
you
throw
an
exception
and
it's
denied
and
you
might
even
want
to
explain
to
people
why
you
denied
them
so
we're
taking
a
lot
of
bitcoin
and
blockchain
inspired
technology
based
on
the
lock
unlock
functionality
and
turning
it
into
something
that
can
cross
multiple,
blockchains
and
cryptographic
systems,
so
that
we
can
specify
very
clearly.
You
know
what
it
is,
we're
trying
to
check
here
and
then.
Finally,
in
the
future,
we
imagine
these
orbit
relationships
where
you
can
store
a
bunch
of
things
into
orbits.
B
This
is
really
inspired
by
bs
freebsd's
geo.
There's
a
brilliant
article
there
that
I
can
share
the
zoom.
After,
but
if
we
have
two
orbits,
what
if
we
could
have
such
a
copy
and
write
relationship
between
orbit,
one
and
two,
where
you
only
have
read
access
to
orbit
one
and
you
want
to
be
able
to
write
to
it
somehow,
so
you
make
an
orbit
three,
that's
copy
and
write
one
and
two
and
all
your
changes
are
stored
to
orbit
two
orbit.
B
B
You
might
even
have
a
copy
and
write
over
that
set
that
you
just
made
in
orbit
six.
You
might
have
a
specific
content
hash
that
you
pin
the
order
that
and
you
want
to
copy
and
write
against
that
with
this
new
orbit,
7,
where
you
would
store
all
your
changes
and
then
finally,
we
really
just
rely
on
content
object
stores.
We
don't
actually
have
a
concept
of
metadata
like
s3.
Does
you
can
update
s3
metadata
in
the
headers?
B
For
example,
so
for
content
metadata
here
you
might
be
able
to
specify
a
metadata
companion
orbit
like
this,
and
it
would
store
the
metadata
there.
You
could
build
an
index
over
both
orbits
and
have
some
kind
of
key
value
functionality
like
s3
and
then.
Finally,
if
we
have
orbit
with
streaming
objects,
maybe
by
default
streaming
objects
are
very
bare
in
kepler,
where
you
just
receive
exactly
once
delivery
and
what?
B
So
that's
a
bit
about
orbits.
So
far
we
this
project
didn't
exist
like
a
month
or
two
ago,
and
we've
made
a
lot
of
headway
since
and
it's
built
in
rost
on
top
of
ipfs
in
bed.
Thank
you,
ipfs
and
bed
team.
It's
been
great
to
use
that
as
a
modular
toolkit,
ipf
srs
also
looks
great
too,
and
they
seem
very
compatible.
So
I'm
impressed
at
that
and
then
basically
oops
we
have
crud
create,
read,
update,
delete
with
blockchain
wallet
signing
and
we
drafted
this
architectural
design.
B
I
just
presented
working
on
now
permission
replication
to
multiple
instances.
Multiple
types
of
order
manifests
basically
what
would
look
like
with
ipfs
log
or
an
upgradable,
dht,
multiple
authentication
method,
so
you
can
use
the
ub
key
and
then
being
able
to
implement
cryptoscript
and
these
orbit
relationships
we're
talking
about.
So
that's
what
we're
working
on
for
the
rest
of
the
year.
One
example
we
have
live
right
now
is
tesla's
profiles,
long
story
short:
you
get
verifiable
credentials
that
ties
your
twitter
account
to
your
tesla's
address.
Where
do
you
store
this
credential
right?
B
B
So
that's
basically
all
I
have
to
share
about
orbitz
right
now
and
I
thank
you
for
listening.
We
have
a
github,
it's
open
source,
apache
too.
If
you
want
to
hear
more
about
how
the
products
architecture
you
can
read
the
code
or
we
have
architecture
and
product
requirements
documents
in
the
repo.
If
you
want
to
hear
about
how
it's
built
or
the
problem
space
we're
trying
to
solve
and
always
love
to
chat
about,
kepler
decentralized
identity.
Dm
me
on
twitter
at
wikid
is
my
favorite
unix
tool,
a
very
dangerous
one
and
then
telegram
or
linkedin.
A
A
A
Okay,
so
thank
you.
Thank
you
wayne.
Thank
you.
Everyone
for
presenting
before
we
finish
I'd
like
you
to
invite
you
to
the
two-day
hackathon
we're
running
this
weekend
with
his
global
to
build
an
experiment
with
nfts
games,
audio
video
and
data
markets
we'll
be
giving
away
over
50k
in
prices.
Anyone
who
uses
ipfs
or
filecoin
will
be
eligible
to
win
filecoin
in
the
prize.
Pool
and
registrations
at
well
is
at
web3.ethglobal.com,
and
you
have
till
thursday
to
register.
A
And
we
will
gonna
see
you
next
month
we
have
another
amazing
meetup
planned.
You
can
follow
the
updates
on
our
twitter
or
on
youtube.
So
yeah.
I
hope
to
see
you
there
register
on
meetup.com
in
advance
and
if
you're
interested
in
speaking,
there's
also
a
link
there
for
a
type
form
where
you
can
share
more
about
your
project,
what
you're
working
on
and
we
can
be
in
touch
to
plan
your
talk
with
us.