►
From YouTube: Identity Management in Hyperledger FireFly
Description
Nicko Guyer, FireFly Community Lead, and Peter Broadhurst, Co-founder and Head of Engineering at Kaleido, provide an overview of how the Hyperledger FireFly project works to orchestrate event-driven flows with built-in identity management.
When doing off-chain transfers of data, you need to know who you’re transacting with. FireFly comes out of the box with a multi-party system mode that has a built-in network map. The system uses DID syntax to represent verified identities. FireFly is then able to interact with other blockchain solutions that use a self-sovereign identity system backed by DID.
Hyperledger FireFly is a complete stack for enterprises to build and scale secure Web3 applications. As an open source project, anyone who is interested in Hyperledger FireFly is welcome to use the code, ask questions in the project's forums and join the community and contribute to the project.
Join us on the Hyperledger FireFly Discord:
https://discord.gg/Fy7MJuqw86
Download the Hyperledger FireFly CLI:
https://github.com/hyperledger/firefly-cli
Hyperledger FireFly GitHub:
https://github.com/hyperledger/firefly
Hyperledger FireFly Wiki:
https://wiki.hyperledger.org/display/FIR/Hyperledger+FireFly+Home
----
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)
A
Great,
thank
you
very
much
jar,
so
I
I
think
I'm
going
to
kick
things
off.
I'm
just
going
to
give
so
quick,
quick
agenda
of
kind
of
what
we
wanted
to
go
through.
I'm
just
going
to
give
a
very
brief,
very
brief
overview
of
what
firefly
is
what
the
project
is,
how
it's
used
and
kind
of
the
a
brief
snapshot
of
the
roadmap
of
what
we're
working
on
currently
and
then
that
will
kind
of
segue
into
peter
talking
about
how
identity
works
in
within
firefly
and
then,
hopefully
from
there.
A
We
could
kind
of
open
it
up
and
and
have
discussion
about
it.
So
my
my
other
disclaimer
is
that
before
about
a
couple
hours
ago
this
morning
I
didn't
realize
this
was
going
to
be
a
presentation.
I
was
thinking
it
was
more
of
a
conversation,
so
so
that
there's
my
disclaimer
I'm
going
to
go
ahead
and
share
my
screen,
because
I
do
have
some
slides
to
go
through
here
and
we'll
jump
right
in.
A
So
I
just
kind
of
want
to
give
folks
if
you're
not
familiar
with
the
firefly
project,
like
I
said,
a
very
brief
overview
of
what
it
is.
I
could
talk
for
a
really
long
time
about
this,
but
I'm
going
to
try
to
keep
this
short,
so
we
describe
hyperledger
firefly
as
a
super
node
and
it
we
described
that
as
a
complete
stack
for
enterprises
to
build
and
scale
secure,
web3
applications.
So
what
does
that
mean?
Well,
that
means
firefly
is
not
a
dlt.
A
It
sits
a
layer
above
the
blockchain,
and
it
is
a
platform
that
you
can
build
web3
blockchain-powered
apps
on
top
of.
So
what?
What
does
that?
Give
you
as
as
a
developer?
What's
the
the
benefit
when
you
look
at
the
landscape
of
open
source
projects?
There's
a
lot
of
projects
down
kind
of
at
the
at
this
low
level
of
of
blockchains
dlts.
All
these
you
know
tools
for
for
doing
stuff.
On
the
blockchain.
That's
great!
There's,
there's
lots
of
you
know!
A
There's
there
may
be
lots
of
stuff
at
the
top
layer
too.
You
know
where
you
have
your
user
interface
and
there's
there's
lots
of
great
open
source
frameworks
for
building
flashy
cool
web
apps.
But
if
you
want
to
build
an
enterprise,
web3
application,
there's
all
kinds
of
things
that
sit
in
between
those
layers
that
you
have
to
build,
and
one
of
the
things
as
peter
was
saying.
This
is
firefly
sort
of
came
out
of
the
journey
of
collido.
You
know
at
collido
as
we
built
more
and
more
web
3
applications.
A
So
that's
that's
what
hyperledger
firefly
does
it's
meant
to
fill
this
gap,
to
give
you
a
common
platform
with
a
an
easy,
concise
set
of
apis
that
you
can
build
an
application
on
so
so
it
sits,
like
I
said,
a
layer
above
the
blockchain
itself
and
let's
the
developer
focus
on
the
thing:
that's
really
of
ultimate
value
to
their
business,
which
is
solving
their
business
problem.
So
the
developers
can
focus
on
the
the
logic
of
their
of
their
business
app.
They
don't
have
to
spend
time
thinking
about.
A
A
So
so
those
are
like
the
main
sets
of
things
that
it
lets
you
do
and
build.
Those
are
powered
by
the
firefly
core
fireflight
core
is
has
an
orchestration
engine
in
it
that
is
sort
of
the
the
brain
and
the
connector
and
the
the
organizer
for
for
all
of
these
different
systems
that
it's
connecting
and
what
are
all
those
systems?
Well,
there's
there's,
obviously
a
blockchain
node.
A
All
of
this,
of
course,
is
done
with
security.
This
is
enterprise
ready,
so
there's
you
know,
there's
security
running
through
all
these
layers,
there's
also
a
really
robust
set
of
tools.
You
kind
of
have
on
the
chart
over
here
there's
a
an
sdk
for
node.js,
it's
written
in
typescript,
so
it
has
great
type
definitions.
There
are
more
sdks
coming,
that's
the
one
that
we
have
today
readily
available
on
npmjs.com.
A
There
is
a
command
line
interface
that
can
be
used
to
create
a
local
development
environment
on
your
machine
that
will
start
all
this
stuff
up
and
lets
you
play
with
it
with
just
a
few
commands
and
obviously
there's
a
fantastic
api
for
for
all
of
this
stuff.
There's
a
web
ui.
The
explorer
I
forgot
to
mention
here
up
at
the
top.
The
explorer
is
a
fantastic
user
interface
that
lets
you
see
what's
going
on
inside
firefly
and
and
all
of
this
is
designed
in
a
cloud-native
modern,
distributed
architecture
in
mind.
A
So
it's
meant
to
run
in
kubernetes.
It
has
prometheus
monitoring
built
right
in
and
and
it's
great
so,
let's
kind
of
break
down
kind
of
these
apps
flows
and
digital
assets
and
describe
a
little
bit
more
in
detail.
What
we
mean
on
each
of
those.
So
one
of
the
really
cool
features
that
firefly
has
is
that
it
will
let
you
build
http
apis
from
smart
contracts,
so
you
can
import
a
a
custom,
smart
contract.
A
If
it's
ethereum,
you
could
provide
an
ethereum
api
and
firefly
will
generate
on
the
fly,
an
api
for
it.
So
it
lets
you
sort
of
rapidly
build,
integrations
and
applications.
It
also
stores
information
about
the
about
the
the
api
on
the
chain
and
could
broadcast
that
to
other
parties
as
well,
so
other
you
can
inform
other
parties
about
a
certain
contract.
A
That's
on
chain
and
there's
some
some
really
cool
features
there,
including
the
ability
to
subscribe
to
events
being
emitted
by
those
contracts
to
index
those
events
and
be
able
to
query
them
and
get
state
out
of
the
contract
as
well
all
through
fireflies
api
firefly
is
one
of
the
the
main
use
cases
for
it,
and
this
is
a
use
case
that
is
growing.
There's
a
lot
of
functionality
being
built
into
it
right
now
is
to
use
it
as
a
web.
3
gateway.
A
What
do
we
mean
by
that?
So,
for
example,
if
an
enterprise
has
they
want
to
build
a
an
app
powered
by
blockchain,
but
they
need
to
have
a
control
point
or
a
one
point
in
their
it
infrastructure
that
is,
can
communicate
with
a
public
chain,
for
instance,
communicate
outside
the
business
network.
That
needs
to
be
in
a
very
specific
area
of
the
network.
A
Firefly
can
can
fill
that
role,
so
firefly
becomes
the
gateway
to
the
web
3
world
in
the
same
way
that
an
internet
gateway
is
a
mechanism
for
applications
inside
a
network
to
reach
out
to
systems
outside
of
the
private
business
network.
A
firefly
can
act
in
the
same
role
for
the
web
3
world
so
and
this
can
go
both
ways
as
well,
so
everything
coming
to
and
from
the
blockchain
goes
through
firefly
and
to
a
a
web
3
app.
A
So
so
this
provides
a
lot
of
power
for
businesses,
one
of
the
other
use
cases
or
or
sort
of
usage
patterns.
I
should
say
that
is
it's
much
broader
than
a
specific
use
case,
but
what
we
described
as
a
usage
pattern
is
for
consortiums
or
multi-party
networks,
as
we
refer
to
them
as
sometimes
so,
and
this
was.
This
was
really
like
one
of
the
the
very
first
usage
patterns
that
was
built
out
robustly
in
firefly.
A
So
a
lot
of
the
demos
that
you,
if
you've,
seen
the
demo
already
of
firefly,
it
was
probably
the
the
consortium
multi-party
usage
pattern
demo,
where
you
have
multiple
organizations
that
are
interacting
with
each
other
through
the
blockchain
they're
broadcasting
data
throughout
the
whole
organization.
Hashing,
it
pinning
it
to
the
blockchain,
maybe
they're,
privately,
sharing
more
sensitive
pieces
of
data
directly
between
members
and
they
can
perform
transactions
with
with
custom.
A
Okay
and
that
that
third
box
was
digital
assets,
so
firefly
also
comes
out
of
the
box
with
really
robust
apis
for
tokens,
which
are
one
of
the
fundamental
building
blocks
of
a
web.
3
app
of
a
blockchain
app
tokens
could
be
fungible
or
non-fundable.
There
are
patterns
for
both
in
firefly
and
it
is,
it
doesn't
actually
matter
which
specific
token
contract
you
use.
It
could
be
a
vanilla,
off-the-shelf,
open,
zeppelin
erc
contract,
whether
that's
erc20
erc-721.
A
It
could
be
a
completely
custom
token
contract
and
as
long
as
it
implements
the
ability
to
mint
transfer
and
burn
tokens,
it
and
firefly
also
has
the
ability
for
token
approvals
as
well.
There
are
first
class
apis
built
right
into
firefly,
there's
a
fantastic
dashboard
that
lets
you
inspect
everything.
This
is
a
little
screenshot
of
the
the
firefly
explorer
the
firefly
ui
that
shows
kind
of.
What's
going
on
inside
this
particular
token
pool,
but
there's
great
support
for
tokens
right
out
of
the
box
makes
it
super
convenient.
A
You
know,
stateless
web
3
app
and
the
the
firefly
core
orchestration
engine
takes
a
lot
of
that
for
them.
So
it's
it's
coordinating
between
things
that
are
on
chain
data,
that's
being
pinned
to
the
chain
or
or
tokens
or
events
that
are
are
coming
off
the
chain
and-
and
it's
also
coordinating
that
with
with
off
chain
data
as
well,
whether
that's
documents
that
are
stored
in
ipfs,
whether
that's
private
messages
that
are
sent
directly
from
node
to
node
and
and
all
kinds
of
things
like
that.
A
So
I've
touched
on
a
couple
of
different
places
that
the
firefly
stores
data
it
has
a
like.
I
said
it
has
a
database
that
firefly
stores,
network
and
chain
state
in
it
also
works
with
a
shared
storage
system.
Right
now,
the
implementation
for
that
out
of
the
box
is
ipfs,
and
it
also
has
a
private
data
exchange
as
well.
A
Firefly
has
like,
I
said,
a
lot
of
tools
with
it.
Here's
another
screenshot
of
the
the
explorer
from
the
dashboard.
I've
touched
on
quite
a
few
of
these
already
the
cli,
the
api
and
the
sdk.
So
I
won't
belabor
the
point,
but
it
has
a
lot
of
tools
and
and
they're
really
great.
They
make
using
it
easy
and
I,
I
think,
an
enjoyable
experience
for
developers.
A
It's
it's
all
like.
I
said
cloud
ready,
modern
distributed
architecture
design,
one
of
the
other
really
cool
things
about
it
and
we'll
talk
more
about
plugins
here
in
just
a
little
bit.
Is
that
it's
one
of
the
points
I
haven't
touched
on
is
that
it's
a
very
pluggable
architecture,
so
not
only
is
firefly
itself
distributed
into
many
microservices.
A
The
the
orchestration
engine
has
a
really
robust
plug-in
system
that
allows
the
implementation
for
any
of
those
services
to
be
swapped
out.
So,
if,
if
you
know
the
out
of
the
box,
implementation
of
shared
storage
is
ipfs,
but
if
you
have
a
specific
need
to
use
a
different
shared
storage
mechanism-
maybe
it's
you
know
amazon,
s3
or
some
other.
Maybe
it's
some
on
premise:
data
storage
system
that
can
easily
be
swapped
out
via
a
plug-in
to
the
firefly
core,
to
talk
to
a
completely
different
storage
service
that
sits
outside
of
firefly
core.
A
At
the
same
time,
so
I
talked
about
kind
of
the
gateway
and
the
the
multi-party
usage
patterns
allowing
firefly
to
to
operate
in
both
of
those
modes
at
the
same
time
in
different
name
spaces
with
different
sets
of
plug-ins,
and
so
so
all
three
of
these
active
development
bullet
points
are
very
much
related.
So
I
also
commented
on
that.
You
know:
there's
there's
a
lot
of
work
going
in
right
now
to
enhancing
firefly's
web
3
gateway
capabilities
and
giving
operators
more
control.
A
More
granularity
of
how
their
their
firefly
node
interacts
with
the
rest
of
the
blockchain
world
coming
up
soon
we're
working
on
more
samples,
more
sdks
and
looks
like
I
had
a
duplicated
bullet
point.
The
web3
gateway
was
supposed
to
be
on
the
left
side.
Sorry
about
that
also
plugable,
api
security
and
plugable
identity
management
are
are
coming
up
very
soon,
and
so
those
are.
Those
are
things
that
that
people
are
really
excited
about
as
well
and
so
speaking,
of
plugable
identity
management.
B
B
B
And,
like
I
say
you
can
you
can
pick
pick
your
blockchain
there
and
also
a
bunch
of
tooling,
so
you
get
a
sandbox,
which
is
a
sort
of
an
exerciser
for
blockchain
constructs
so
being
able
to
play
with
tokens,
create
your
launch
your
own.
Your
own
token,
on
your
on
your
laptop
transferments,
mint
and
burn
tokens
interact
with
smart
contracts
of
any
description
on
the
blockchain
itself.
So
you've
got
some
custom
fabric
chain
codes.
B
I
don't
need
to
tell
this
group
that
that's
a
that's
a
reality
of
life
in
the
blockchain
space.
That's
a
a
hex
string.
An
ethereal
address
is
not
great
for
business
to
know
who
they're
transacting
with
so
so.
Firefly
does
come
out
of
the
box
when
you're
using
it
in
the
multi-party
system
mode,
where
you're
assuming
everybody
else
is
running
offline.
I
think
that's
an
important
point,
because
fireflies
of
technology
does
not
make
that
decision
that
assumption.
That
does
provide
that
as
an
option
for
you.
B
Then
it
comes
with
a
sort
of
built-in
network
map,
a
system
of
identity
just
out
of
the
box
inside
of
inside
a
firefly.
So
just
before
we
I
started
talking,
I
sent
I
sent
her
a
message
that
came
from
another
party
in
the
in
the
system.
They
need
to
see
who
it
came
from
then
I
actually
get
to
see
the
the
identity
that
came
that
that
message
came
in
on.
B
So
if
I
open
up
the
message
here,
we'll
see
that
we
represent
identity
in
firefly
using
the
dod
syntax,
and
I
I
want
to
put
it
that
way,
because
we
firefly
is
itself
just
like
with
every
blockchain
technology,
not
trying
to
be
the
full
implementation
of
a
core
blockchain
construct.
Firefly
is
not
a
dlt.
It
lets
you
plug
into
fabric
ethereum.
Even
there's
called
a
quarter
support
there,
connect
to
all
of
those
remote
block
chains
that
you
might
be
connecting
to.
B
Varied
as
bitcoin
are
connect
are,
you
know,
fit
into
the
pattern
of
firefly
off-chain
pipes.
Well,
maybe
you're
using
you
know
just
the
open
source
mutual
tls
connectivity,
peer-to-peer,
maybe
you're
using
a
cueing
technology
like
rather
than
queue
or
nats
or
or
kafka
or
jms
provider,
but
all
of
that
can
can
plug
in.
B
So
that
was
the
reason
for
choosing
did
to
be
the
way
that
we
represent
an
identity
of
something
that
you've
received
in
this
particular
case,
a
piece
of
broadcast
data
that
was
pinned
to
the
blockchain
with
a
blockchain
transaction
of
the
hash.
As
with
all
sensible
solutions,
the
data
itself
didn't
go
onto
the
blockchain.
B
And
if
you
go
to
the
network
map,
you'll
see
that
there
are
these
sort
of
constructs
like
organizations
knows
and
customer
identities
which
I
don't
have,
any
of
which
are
a
which
are
a
a
simple
built-in,
with
a
sort
of
profile
way
of
advertising.
Your
identity
within
the
network,
which
is
backed
by
performing
a
simple
verification
using
a
key,
and
I
don't
have
an
example
of
it
here.
But
if
there
was
a
child
identity
like
I
created
a
custom
identity,
then
it
wouldn't
just
be
the
identity
you
would.
B
You
would
have
had
to
the
the
key
that
you're
using
yourself
to
prove
that
you
have
ownership
of.
There
would
also
be
a
verification
by
whoever
you're
saying
is
the
the
next
identity
of
the
tree.
So
a
very
simple
system.
You
know
a
lot
like
a
pki
system
where
there
are
some
router
densities
in
the
system
that
are
trusted
because
they
just
established
themselves
through
sort
of
a
gatekeeping
construct.
They
came
on
board
and
then
a
claimant
verification
system
to
generate
other
identities.
B
B
Why
not
have
other
resolvers
right?
Why
not
have
firefly
in
much
more
sort
of
in
that
gateway
mode?
Where
you're
just
connecting
to
ecosystems
that
exist
where
some
of
the
members
are
getting
the
acceleration
of
using
a
stack
of
technology
like
firefly?
Other
members,
you
know,
maybe
built
everything
from
scratch
and
really
want
to
use
the
lowest
level
technologies
and
being
able
to
join
that
community
and
participate
in
it
using
a
sort
of
middleware
stack.
That
makes
it
much
easier
for
you
to
connect
your
applications
and
call
systems
to
us.
B
Well,
that
would
mean
you'd
need
to
work
with
whatever
the
identity
system
is
of
that
group
of
participants.
So
that's
why
we
chose
the
id
we're
not
choosing
did
because
we
want
to
be
a
self-sovereign
identity
provider.
We're
choosing
did
because
we
want
to
be
a
accelerator
for
solutions,
regardless
of
what
technology
choices
they've
made
in
the
blockchain
space,
and
that
means
that
projects
where
there.
A
B
Self-Sovereign
identity
system
or
other
identity
system
involved,
that's
backed
by,
did
being
able
to
plug
that
in
and
say,
don't
resolve
this
inside
of
firefly
with
the
multi-party
system.
Built-In
thing
resolve
this
using
the
plug-in
and
the
plug-in
doesn't
need
to
be
you
know
just
because
maybe
firefly
core
is
go,
doesn't
need
to
be
rewritten
in
go
right.
That
can
be
any
existing
system.
B
For
this
community,
because
I
didn't
want
to
give
any
impression
that
what
we've
tried
to
do
is
you
know
that
there's,
I
think,
there's
a
great
synergy
with
projects
like
aries
and
an
indie
and
software,
not
a
not
a
contention
rhythm.
This
is
this
is
about
an
accelerator
that
helps
particularly
focus
on
enterprise
projects.