►
From YouTube: Hyperledger FireFly 1.0 is here! Build full-stack Web3 apps faster with FireFly SuperNodes
Description
It’s no secret that building Web3 apps is hard. There are protocols to master, new constructs like tokens and smart contracts to understand, and then the challenge of integrating it all with existing systems, which may be the hardest part of all.
That’s why our community created Hyperledger FireFly, the first open-source Supernode: a complete stack for enterprises to build and scale secure Web3 applications.
Learn more about FireFly at https://hyperledger.github.io/firefly/ and https://wiki.hyperledger.org/display/fir
Join the discussion about FireFly in the #firefly channel on Hyperledger's Discord server at: https://discord.gg/hyperledger
----
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
B
B
B
B
B
Let
us
know
where
you
are
zooming
in
from
I'm
zooming
in
from
san
francisco
this
morning
and
it's
great
to
see
everyone
and
our
instead,
our
panelists
as
well,
which
I
will
introduce
in
a
second
today
as
as
usual,
if
you've
attended
other
hyperledger
foundation
webinars,
we
just
have
some
housekeeping.
So
first
of
all,
all
are
welcomed
here
in
the
hyperledger
community,
we're
here
to
create
a
safe
and
welcoming
community
for
all.
B
So
please
follow
the
hyperledger
code
of
conduct
when
interacting
with
one
another
and
when
talking
to
others
in
the
community
as
well
a
couple
of
housekeeping
rules
once
again,
all
hyperledger
foundation,
project
meetings,
webinars
etc
are
held
under
our
linux
foundation,
antitrust
policy.
So
please
read
the
policy.
If
you
have
any
questions
around
things
that
you
should
or
should
not
say,
do
let
someone
on
staff
know
or
you
can
contact
our
legal
firm
by
following
that
full
policy
link.
B
Today
we
do
have
a
jam
pack
webinar
with
lots
of
speakers,
so
we're
going
to
ask
that
you
put
your
questions
and
answers
into
the
question
and
answer
box
for
those
of
you
who
are
new
to
zoom
webinars,
there's
a
box
in
the
middle
that
says
q
a
as
that
image
indicates
go
ahead
and
put
your
questions
and
answers
there.
You
can
also
put
your
your
questions
into
the
chat
and
we
will
get
to
them
either
through
the
presentation
or
at
the
end
as
well.
B
For
those
of
you
who
perhaps
have
a
question
that
doesn't
get
answered,
we
also
encourage
you
to
join
our
discord
channel
and
we'll
put
that
into
the
chat
in
a
little
bit
and
feel
free
to
ask
your
questions
there
after
the
fact,
and
we
will
get
through
them
as
time
permits.
So
once
again,
stay
active,
get
the
most
out
of
it.
We're
here
to
educate
you
to
teach
you
what
is
happening
in
our
ecosystem
and,
more
importantly,
get
you
familiar
with
in
this
case
hyperledger
firefly.
B
Many
that
you'll
speak
today
do
about
building
a
community
around
firefly
has
really
been
amazing,
and
it's
really
one
of
the
things
that
companies,
when
they
think
about
bringing
their
open
source
projects
to
a
foundation,
really
find
powerful
to
bring
it
to
the
hyperledger
foundation,
where
we
can
create
these
open
source
communities.
So,
once
again,
from
a
panelist
perspective,
we're
gonna
have
three
parts
of
our
panelists.
B
So
I
am
looking
forward
to
that
discussion
and
then
we're
going
to
close
off
with
nico,
who
is
one
of
the
maintainers
at
collido
and
really
one
of
the
leaders
in
our
community
in
our
hyperledger
firefly
community.
So
we're
looking
forward
to
hearing
from
him
and
he's
going
to
give
you
some
demos
on
how
to
get
started.
So
once
again,
please
add
your
questions
as
we
go
along
in
the
q
a
form
and
we
look
forward
to
the
scrape
panels
steve
over
to
you.
C
All
right
well,
thank
you.
Everyone
happy
to
to
see
everyone
today,
I'm
going
to
start
the
screen
share
and
we'll
jump
in
we're
on
the
east
coast
of
the
u.s
in
sunny
raleigh
north
carolina
nice
spring
afternoon,
where
the
high
is
85
degrees,
that's
about
30
degrees
celsius.
If
my
math
is
correct,
see
my
screen.
Okay,
all
right!
Thank
you!
Daniella!
You
already
covered
the
agenda,
so
I'm
going
to
jump
right
in
but
before
we
get
into
1.0
and
what's
new
and
exciting.
C
C
You
know
realizing
that
the
future
is
really
a
multi-chain
world.
You
you
want
a
higher
level
of
you,
know
accuracy
and
resiliency,
or
so
things
like
audit
trails
for
that
data
that
can't
go
on
chain.
You
have
to
figure
out
how
to
transfer
it.
If
it's
a
b2b
use
case
amongst
counterparties,
error
handling
is
quite
complex
and
then,
of
course,
actually
integrating
with
existing
systems
is
always
the
hardest
problem.
Isn't
it
no
matter
what
the
project
is?
C
Well,
good
news.
There
is,
and
that's
that's
what
high
firefly
really
does
and
and
what
the
community
is
really
excited
about,
and
the
purpose
of
it
it
handles
out
of
the
box
support
for
multiple
different
protocols
and
chains.
It
has
native
support
for
things
like
tokens
and
digital
assets.
It's
very
plugable,
so
you
can
bring
your
own
wallet
custody
key
management
solutions.
C
C
Your
project,
as
we
know,
that's
a
concern
and
how
firefly
can
help
there.
So
again,
just
a
quick
glance
on
at
the
timeline
daniella
mentioned
the
projects.
Almost
a
year
old
now
started
with
a
contribution
of
of
some
code
from
collido.
Primarily
you
know
about
four
months
later,
the
the
project
moved
up
from
a
lab
to
an
incubating
project
and
now
we're
here
today
hitting
another
significant
milestone,
1.0
launch.
C
I
want
to
call
out
you
know
the
community
and
the
developers
really
hats
off
over
200
000
lines
of
code
today
across
12
repos
and
growing,
just
really
impressive,
to
see
the
community
rallying
around
this.
This
technology
stack
this
promising
project.
I
listed
off
a
few
things
on
the
right,
but
we're
going
to
get
into
some
of
those
details
presently
about
what
a
firefly
is
and
what
it
does
in
in
more
detail.
C
C
The
world
doesn't
need
another
blockchain
protocol,
in
my
opinion,
or
another
l2
or
whatever
else,
but
the
the
world
could
really
use
rich,
reliable
connectivity
and
integration
into
the
the
web
3
space
and
that's
what
the
firefly
super
node
is
here
to
do
really
at
the
core
is
firefly
core
and
the
orchestration
enter
engine
is
at
the
center
of
that
all
backed
by
a
scalable
event.
Bus
the
core.
Also
has
a
rich
data
layer
which
I'll
unpack
a
bit
in
a
minute.
It
includes
both
your
private
data
as
well
as
data.
C
That's
been
shared
to
you
and
broadcast
across
a
network
and
through
shared
storage
like
ipfs
as
well
as
chain
data
as
well.
Firefly
is
also
tracking
your
state
along
the
way
you
know
so
both
network
state
and
chain
state
it
has
a
rich
security
pillar
as
well.
You
know
we'll
talk
about
identity
and
how
that
fits
in
always
a
deep
topic,
as
well
as
api
security
and
end-to-end
encryption.
C
C
C
So
now,
I'm
gonna
step
into
some
of
these
pillars
in
a
little
bit
more
detail.
For
a
few
minutes,
so
this
really
is
a
gen
2
approach
to
building
out
a
web
3
app
or
a
dapp
or
a
blockchain
application,
eliminating
tons
of
custom
code.
You
know
we
found
at
collido
companies
that
port
over
to
firefly
eliminate
over
80
percent
of
the
code
of
the
application.
C
C
You
know
zooming
in
a
little
bit
to
the
different
layers
that
that
are
within
firefly,
with
your
application
on
the
left
and
all
of
the
web.
3
type
connectivity
and
runtime
systems
on
the
right
in
the
middle
is
is
firefly
with
the
simple
apis
that
I
was
just
talking
about
a
second
ago
but
backing
that
is
a
really
reliable.
C
You
know
high
concurrency
system
of
an
event
bus
and
then
a
connection
manager,
that's
managing
all
the
connectivity
and
raw
rpc
connections
out
to
you
know
the
blockchain
nodes
and
the
other
technologies
that
you're,
using
as
moving
on
to
data
flows
for
a
minute.
This
is
really
about
on
chain
and
off
chain
working
together
hand
in
hand.
You
know
a
lot
of
times.
We
see
consortium
type
networks
start
with
b2b
use
cases
b2b.
You
know,
use
cases
almost
always
have
data
flows,
documents
moving
amongst
different
organizations
or
counterparties
in
a
consortium
network.
C
So,
in
addition
to
the
blockchain
there's
an
ipfs
layer,
that's
there
for
broadcast
and
in
shared
storage,
there's
also
a
private
data
bus,
so
completely
off-chain,
but
the
apis
are
there
to
tie.
You
know:
off-chain
data
track,
transfers.
On-Chain,
you
can
move
messages,
you
can
move
entire
documents.
C
You
know
things
like
chunking
those
documents
up,
end-to-end
encryption,
other
features,
it's
part
of
the
data
bus
and
then,
of
course,
the
the
hashes,
the
the
proofs
go
on
chain
and
all
of
that
just
works
end
to
end
moving
into
the
third
pillar
for
a
minute
digital
assets.
You
know:
there's
lots
of
new
functionality
here
in
in
v1
really
to
manage
tokens
at
an
institutional
scale.
C
So
moving
from
doing
that
poc
with
one
token
into
thinking
about
hundreds
and
thousands
of
digital
assets,
a
lot
of
the
the
you
know,
customers
and
users
of
firefly
in
in
the
financial
services.
Space
are
really
thinking
about
that
end
game.
So
a
rich
native
token
api
for
coins,
nfts
1155
as
as
well
as
well
as
a
rich
audit
trail
so
having
the
full
lineage
of
a
token
whether
it's
minted
through
firefly
or
not,
firefly
can
listen,
it
can
learn.
C
It
can
late,
join
two
tokens
that
already
exist
out
in
public
chains
and
so
on,
and
then
also
really
important
to
the
digital
asset
stack.
Is
your
strategy
around
wallets
and
custody
of
those
wallets?
There's?
No
one!
There's
no
one
answer,
but
firefly
makes
it
easy
to
integrate.
Regardless
of
your
solution,
there
dropping
down
a
layer
for
a
second
into
core.
C
It's
really
about
orchestration
and
and
data
orchestration
at
the
end
of
the
day.
So
the
engine
is
almost
like
the
brain.
That's
that's!
Really
power
powering
this
event-driven
system.
You
know
things
like
batching
of
of
transactions
are
are
a
native
part.
Sequencing,
of
course,
is
extremely
important.
You
know
you
you
want
to
deposit
before
you
withdraw
the
classic
example.
C
C
You
know,
use
cases
and
enabling
those-
and
that's
what
firefly
helps
you
do
also
in
the
core:
the
data
management
layer,
there's
a
lot
going
on
at
at
this
layer,
structured
and
unstructured
data
in
that
core
data
store,
as
well
as
the
digital
asset
manager.
That's
that's
keeping
you
know
transaction
indexes
as
well
on
the
chain,
state
side
and
blockchain
event
index,
so
that
correlation
happens
again
within
sort
of
the
the
brain
of
the
orchestration
layer
and
then
on
the
network
side.
C
We
haven't
talked
a
lot
about
the
network
map,
like
in
a
b2b
network,
an
address
book.
The
fact
that
you
have
an
organizational
identity
which
may
be
different
than
you're
on
on
chain
identity
and
how
you,
as
an
organization,
keep
track
of
that
that
broader
network
map
of
your
counterparties,
that's
also.
C
C
C
Firefly
is
cloud
ready.
It's
modern
software.
We
started
on
on
kubernetes
day
one.
This
really
helps
you
as
an
organization
build
modern
software.
On
top
of
it,
you
want
to
build
next
generation
stuff,
so
you
want
to
be
on
the
latest
technology
stack,
it's
cloud
ready,
sort
of
born
in
the
cloud,
whether
that's
a
public
cloud
or
your
own
private
cloud.
C
There
are
also
our
hosted
options
available
through
vendors
that
are
involved
in
the
firefly
space
and
it's
designed
to
scale.
So
it's
a
it's
fundamentally
a
microservice
architecture.
So
it's
stateless
where
it
should
be
stateless.
It
helps
you
achieve
again.
A
modern
architecture
goes
without
saying
in
this
hyperledger
call
that
it
is
enterprise
ready,
open
source.
It
is
highly
extensible
and
pluggable.
So
you
can
take
this
and
some
of
the
other
firefly
users
that
I'm
aware
of
and
work
with,
are
thinking
about.
Okay,
a
firefly
has
this
rich
connector
layer.
C
I
want
to
build
a
custom
connector
to
connect
off
to
this
custom
system.
You
can
totally
do
that
with
the
apache
2
license
and
and
it's
it's
built
that
way
so
that
you
can
continue
to
stay
updated
with
firefly
going
forward.
So
what
will
you
do
with
firefly
right
is?
Are
you
thinking
about
a
b2c
use
case?
Your
customers?
You
want
to
build
them
new
digital
experience
with
them.
Are
you
thinking,
b2b
and
more
of
a
consortium
network
and
you're
thinking
about
data
flows?
C
C
You
know
things
that
are
that
are
immediately
on
the
truck.
The
community
is
kind
of
already
prioritized
into
active
development.
You
know
more
support
for
public
blockchains.
There
are
nuances.
You
know
whether
you're
looking
at
ethereum
layer,
2
versus
mainnet
ethereum.
There
are
many
other
protocols
out
there
as
well,
so
lots
of
interest
in
more
public
connectivity
and
that
connector
framework's
just
going
to
scale
and
allow
more
connectivity
to
drop
in,
of
course,
more
samples
additional
documentation
is
coming
soon.
C
C
You
know
enhancing
the
web
3
gateway
with
with
even
more
tools
to
help
you
manage
all
of
that
connectivity
tr.
You
know
get
to
the
root
of
any
issues
that
that
occur
and
manage
those
in
in
real
time
and
then,
of
course,
security
is,
is
a
journey
as
well
and
we'll
be
adding
more
plug
points
into
the
api
security
and
doing
more
things
along
the
way?
C
E
D
You
know
we
work
with
a
lot
of
leaders
in
their
respective
industries
and
pat
in
the
insurance
industry.
Kyle
and
healthcare
really
have
done
quite
extraordinary
things
and
bring
a
lot
of
true
business
and
technical
leadership
and
how
they're
approaching
sort
of
guiding
their
respective
networks.
So
I
just
wanted
to
do
some
brief
interest,
but
have
pat
and
kyle
introduce
themselves
and
also
share
a
little
bit
about
their
respective
initiatives.
E
Sure,
thanks
for
thanks
for
having
me
here
today,
my
name
is
pat
schmidt.
I
am
the
vice
president
of
the
institute's
restraint
collaborative.
We
are
a
blockchain
consortium
and
within
the
insurance
industry
we
serve
both
the
property
casualty
market
and
life
and
annuities
a
little
bit
of
background
on
myself.
I
came
up
with
the
initial
concept
for
the
restream
collaborative
and
implemented
it.
My
role
is
to
oversee
our
different
departments
within
restream
or,
basically,
our
core
business
background.
E
Isn't
I'm
a
phd
economist
and
I've
been
working
in
the
insurance
industry
for
about
15
years,
a
little
bit
more
on
risk
stream
itself?
We're
the
largest
blockchain
consortium
and
insurance,
we're
backed
by
an
organization
called
the
institutes
which
is
formed
out
of
wharton
100
years
ago,
provides
property,
casualty,
education,
services
and
research
to
the
industry
and
is
backed
by
a
board
of
about
40
to
50
ceos
that
represent
about
60
to
70
percent
of
domestic
insurance
premium
volume.
So
we
are
implementing
blockchain
technology
within
the
insurance
industry
to
streamline
flow
and
verification
of
insurance.
A
Hello,
my
name
is
kyle
culver,
I'm
a
director
of
emerging
technology
with
humana,
I'm
a
co-founder
of
the
synaptic
health
alliance.
I
come
from
an
engineering
background.
I've
been
with
humana
about
10
years
and
been
leading
into
the
blockchain
healthcare
space
since
kind
of
the
2015-22
time
frame.
Synaptic
really
came
out
of
some
conversations
with
a
group
of
healthcare
leaders
and
looking
at
the
technology
and
saying
that
these
technologies
are
really
beneficial
for
us
to
collaborate
and
not
really
beneficial.
A
You
know
within
the
organization
and
so
looking
for
opportunities
that
were
lower
risk
to
get
started
and
begin
learning
together,
and
so
we
picked
a
use
case
to
be
able
to
crowdsource
public
data
that
we
were
spending
a
lot
of
time
on,
and
resources
on
to
improve
that
quality.
So,
like
dr
smith,
is
on
market
street
and
is
available
at
this
address
and
phone
number.
A
Those
data
elements
are
very
difficult
for
the
healthcare
industry
to
maintain
a
high
quality
and
there's
a
lot
of
resources
spent
on
that
roughly
around
two
billion
dollars,
and
so
that's
the
use
case
that
we
came
together
and
said.
This
is
something
we
can
learn
on
and
those
learnings
will
really
be
applicable
to
other
types
of
collaborative
activities
in
the
future.
So
that's
where
you
know,
we've
met
some
of
these
other
folks
here
and
really
excited
to
see
what
the
community's
been
doing
with
firefly.
D
Thanks
thanks
kyle,
I
you
mentioned
just
some
choices
about
getting
started
and
how
you
approach
that
I
was
wondering
pat
if
you
could
share
some
thoughts
just
on
trade-offs.
As
you
know,
from
a
building
perspective
and
looking
at
writing
your
own
custom
code,
whether
that's
with
an
internal
technical
team
or
working
with
consultants
and
systems
integrators
for
a
blockchain
solution
versus
using
a
project
like
hyperledger
powerfly,.
E
Yes,
it's
a
great
question.
You
know,
within
the
wrist
stream
collaborative
we're
aiming
to
create
this
ecosystem,
with
risk
management
to
leverage
enterprise
blockchain,
to
streamline
the
flow
and
verification
of
data
between
these
different
parties,
in
a
variety
of
multi-party
business
processes
and
through
our
journey
leveraging
blockchain,
which
probably
began
late
2016
2017
we've
explored
a
variety
of
different
elements
related
to
the
technology
early.
B
B
E
E
In
addition
to
that,
the
firefly
gives
us
some
potential
to
leverage
tokens
which
can
help
with
economic
incentives
providing
incentives
for
competitors
to
want
to
share
information
with
one
another
when
theoretically,
they
may
not
want
to
do
that.
Otherwise
and
then
finally,
it
allowed
us
to
establish
some
best
practices
which
allow
the
consortium
to
move
faster.
D
Thanks,
pat,
I
think
that's
a
great
answer
and
one
one
thing:
I
think
that
is
a
good
bridge
to
a
question
I
wanted
to
ask.
Kyle
was
when
you
brought
up
the
token
capabilities
that
that
are
built
in
and
how
those
could
be
used.
I
know
you
have
an
economist's
background,
so
you're
you're
thinking
about
different
economic
models
kyle.
I
know
that
synaptic
looked
at
ways
to
incentivize
the
right
behavior
because
you
have
a
number
of
payers.
D
You
know
some
sensor
competitors
or
could
be
seen
as
competitors,
but
here
they're
collaborating
and
how
do
you
get
the
right
sorts
of
behaviors
and
alignment
in
a
network
which
is
completely
decentralized,
there's
no
central
entity,
everyone's
just
collaborating
and
working
together.
So
I
think
it
might
be
useful
for
everyone
to
understand
how
you
used
in
synaptic.
The
health
alliance
used
the
token-based
model
to
help
accomplish
that.
A
You
know
kind
of
validated
and
then
sharing
like
the
divide
and
conquer
approach,
and
so
when
we
look
at
those
activities,
you
know
we
were
able
to
pull
out.
These
are
the
different
activities
that
we
want
to
incentivize.
We
didn't,
you
know
believe
from
you
know,
looking
at
other
alliances
across
healthcare,
that
an
altruistic
approach
would
work.
There
is
a
lot
of
effort
that
goes
into
curating
this
data,
and
so
we
really
wanted
to
make
it
to
where
the
incentives
were
in
place
to
where
we
could.
A
You
know
kind
of
have
that
market
place
there
for
people
that
are
sources
of
data
and
firms
that
are
sources
of
data
as
well
as
consumers
of
data
and
then
that
they're
allowed
to
participate
as
they
see
fit,
so
we're
not
forcing
an
organization
to
share
all
of
its
data
or
share
these
types
of
data.
But
we
have
the
incentives
really
there
to
drive
that
behavior
and
we
see
that
that's
been
successful.
A
D
Thanks
kyle,
I
think
it's
pretty
exciting
to
see
these
token-based
models
being
used
in
an
enterprise
setting
and
solving
some
really
challenging
projects
about
some
challenging
issues.
Projects
have
run
into
as
they're
trying
to
get
this
new
type
of
collaboration.
Blockchain
is
really
a
team
sport,
so
getting
that
off
the
ground
and
into
production
people
sort
of
aligned
to
the
right
outcomes.
D
I
was
curious
and
this
is
for
either
pat
or
kyle
if
thoughts
about
scaling
now
that
you've
got
some
initiatives
that
are
in
production
and
you're
looking
to
grow
the
network.
I
know
that
you
have
conversations
with
people
who
aren't
part
of
that
initial
group
and
what
are
some
considerations
as
they
look
to
join
and
does
it
help
them
through
their
consideration,
set
to
know
that
you
know
this.
These
initiatives
are
running
on
industry
standards
and
open
source
as
well,
since
some
of
them
might
have
separate
plot
projects.
D
D
Yeah
and
if
as
people
consider
joining
something
that's
already
in
flight
and
in
production,
what
are
their
thoughts
about
trade-offs
with
you
know,
being
based
on
open
source
versus
a
more
custom
like
proprietary,
ip
approach,
and
does
that
help
or
hurt
people
as
they're?
You
know
looking
at
them,
they
might
be
running
their
own
blockchain
projects
and
they're
looking
to
join
this
particular
initiative
because
there's
business
benefits
to
them.
But
I'm
curious
if
that
comes
up
in
the
conversations
or
not.
E
Yeah,
it
absolutely
does.
I
mean
to
be
honest
with
you.
There's
always
concern
we're
dealing
with
very
risk-averse
folks
at
within
the
wrist
stream,
collaborative
as
you
can
imagine,
it's
an
insurance
blockchain
consortium,
yeah
they're
they're,
constantly
looking
at
the
potential
risk
of
a
different
projects
and
an
open
source
technology
showcases
a
little
bit
more
transparency
with
the
industry,
which
I
think
allows
participants
to
feel
more
comfortable
that
if
they
ever
were
in
the
needs
to
off
board
from
a
network
that
that
would
be
easily
done.
E
In
addition
to
that,
it
showcases
a
little
bit
more
of
alignment
with
the
underlying
technology
itself,
that
it's
more
of
a
network-based
approach
to
things
and
for
a
risk
stream
really
does
align
with
us
too,
as
an
industry
not-for-profit
bringing
these
various
parties
together,
we're
not
trying
to
profit
ourselves
over
on
the
wrist
stream
side,
we're
trying
to
allow
the
industry
to
operate
more
efficiently.
So,
yes,
I
think
it's
it's
certainly
been
brought
up
before
sofia.
A
Yeah,
it
definitely
is
a
message
that
that
resonates,
that
transparency
aspect,
the
community
aspect,
you
know
or
things
that
the
synaptic
was
built
upon
from
the
beginning.
You
know
as
well
and
then
so
saying:
hey
we're
going
to
work
with
this
open
source.
You
know
so
there's
not
that
fear
of
vendor
lock-in
and
then
also
you
know
for
our
ability
to
deliver.
We
have
to
be
very
focused
on
a
narrow
use
case.
You
know
we
have
a
number
of
players
and
so
we're
focusing
on
this
narrow
use
case.
A
However,
we
understand
that
technology
is
changing
really
fast
and
that
the
companies
you
know
the
people
working
on
this
aren't
exposed
to
everything
that's
going
on
and
so
having
the
comfort
that
this
community
is
working
on
things
and
learning
from
different
projects
of
things
that
we
may
not
need
now,
but
we
need
in
the
future
or
problems
that
we
didn't
even
know.
We
had
that
now
we
may
need
to
be
able
to
avoid.
A
I
think
is
an
important
message
versus
us
trying
to
build
our
own,
and
so
I
think,
there's
a
lot
of
value
there
as
we
look
to
scale
and
then
you
have
a
lot
of
people
that
just
want
to
be
able
to
you
know
plug
and
play,
and
so
they
don't
care
that
it's
blockchain,
it
creates
value
for
them.
They
want
to
be
able
to
deliver
it
and
trust
that
that's
running,
and
so
I
think
that's
another
good
message
as
well.
D
Thanks
so
much
kyle
and
pat,
I
think
we've
come
to
the
end
of
our
panel
time
period,
but
very
honored
to
have
you
both
join
us
today.
It's
always
great
to
hear
your
perspectives
and
really
very
excited
about
what
you're
doing
in
the
insurance
and
healthcare
spaces.
So
thanks
again
thank
you
and
with
that
I'm
going
to
pass
it
over
to
nico.
We
wanted
to
leave
a
few
minutes
for
questions
at
the
end,
although
we'll
also
go
to
discord
afterwards
for
following
questions,
but
I
know
there
is
a
chat.
D
F
Okay,
hello,
everyone
can
you
all
hear
me?
Okay,
I
think
so.
Okay,
great,
my
name
is
nico
guyer.
I
am
a
maintainer
on
the
hyperledger
firefly
project
and
also
the
open
source
community
lead.
I'm
super
excited
to
show
you
firefly
in
action
here
today.
I've
got
a
lot
of
stuff
to
cover,
so
I'm
going
to
jump
right
in
I'm
going
to
go
ahead
and
share
my
screen
and
you
should
be
able
to
see
my
slides
now.
F
F
We
wanted
a
developer
experience,
it's
quick
and
easy
for
anyone
to
get
started,
whether
you
are
a
seasoned
web
3
developer-
or
this
is
your
first
web3
project.
We
wanted
it
to
be
powerful
enough
to
meet
the
needs
of
experienced
developers,
but
also
approachable.
We
wanted
to
use
familiar
tools
and
patterns
that
developers
could
just
pick
up
quick
quickly
and
easily
and
we
wanted
the
whole
thing
to
be
able
to
run
offline
on
a
laptop,
and
so
that's
the
experience
that
I'm
going
to
walk
you
through
today.
F
It
was
around
in
our
original
launch
last
year
and
it's
come
a
long
way
since
then
it
has
a
lot
more
features,
but
this
is
the
tool
that's
going
to
set
up
the
environment
on
our
laptop.
I've
already
run
it
and
I
have
an
environment
running.
So
we
don't
have
to
wait
for
that.
But
I'll
walk
you
through
what
I
did
there.
The
in
a
nutshell.
It
uses
docker
compose
to
run
all
of
the
components
of
a
super
node
right
on
your
laptop.
F
I've
left
the
link
to
the
firefly
cli
at
the
bottom
of
the
page.
There
these
slides
will
be
available
afterwards.
So
if
you
want
to
click
on
the
link
afterward
and
and
see
where
you
can
go
to
get
this
tool
that
will
be
available.
So
I
have
this
installed
on
my
machine.
I
run
it.
I've
set
up
a
network,
so
a
firefly
stack
on
a
local
development
machine
is
made
up
of
multiple
super
nodes.
So
steve
did
a
great
job
walking
us
through.
You
know
what
is
a
super
node?
F
What
are
the
types
of
things
that
it
does?
We
had
a
great
diagram
where
we
laid
out
all
the
functionality
and
value
of
a
super
node.
This
is
a
different
view
of
like
what
are
the
pieces
that
are
in
a
super
node
that
are
going
to
be
running
on
my
laptop.
So
we
have
I'm
going
to
be
running
a
network
of
three
different
nodes.
F
The
goal
is
that
I
can
set
up
an
environment
all
on
my
laptop
that
is
essentially
a
distributed
network
that
would
normally
in
production,
be
deployed
in
multiple
data
centers
by
multiple
organizations
worldwide.
But
I
can
run
it
all
on
my
laptop
and
I
can.
I
have
different
api
endpoints
for
each
one
that
I
can
hit
that
have
separate
addresses
so
that
I
can
build
applications
that
know
how
to
talk
to
multiple
super
nodes
if,
if
necessary.
F
In
addition,
we
also
have
a
new,
a
brand
new
thing
which
I'm
super
excited
to
demo
today,
which
is
the
firefly
sandbox.
The
firefly
sandbox
is
also
going
to
be
running
inside
docker
compose
it's
not
necessarily
part
of
the
the
super
node
in
a
strict
sense,
in
that
it
is
designed
as
an
application
as
an
example
of
an
end
user
application.
It
exercises
the
firefly
api
from
the
perspective
of
a
user's
application
and
we'll
build
some
some
code
snippets
of
like
hey.
F
This
is
how
you
do
this
type
of
thing
in
firefly,
so
it'll
make
more
sense
when
I
show
it,
but
we're
gonna.
So
the
the
two
main
things
that
I'm
gonna
be
walking
you
through
are
the
firefly
sandbox,
which
is
an
example
of
an
end
user
application
and
the
firefly
explorer
or
the
firefly
ui,
which
lives
inside
the
firefly
core.
F
This
is
what
the
the
sandbox
looks
like
and
in
just
a
second
I
will
stop
sharing,
and
actually
you
know
what,
let's,
let's
hop
over
right
now,
I'm
gonna
slide
over
to
this
side.
Okay,
so
here
I'll
pull
up
my
terminal,
the
font
size
is
probably
too
small
to
see,
especially
for
those
watching
on
youtube.
I
apologize,
but
this
is
just
a
you
can't
see
that
desktop.
Okay,
thank
you
hang
on
just
a
second.
F
Okay,
there
we
go
sorry
about
that
screen.
Sharing
I
pushed
I
shared
the
wrong.
I
shared
the
desktop
instead
of
the
entire
screen.
Okay,
so
I've
just
run
firefly
command
line.
To
start
my
stack,
I've
started
it
with
three
members
for
convenience
and
to
help
people
follow
along.
I
have
named
them
red,
green
and
blue,
and
I
have
three
different
browsers
here.
I
have
a
red
browser,
a
green
black,
green
browser
and
a
blue
browser,
and
so
each
of
these
represents
a
distinct
organization
and
node
within
the
firefly
network.
F
F
F
So
now,
I'm
gonna
show
you
the
sandbox,
so
so
this
is
what
we're
gonna
we're
gonna
be
going
back
to
this
view,
the
the
firefly
explorer
to
see
things
as
they're
happening
in
firefly,
I'm
going
to
pop
over
to
the
sandbox,
though-
and
this
again
is
an
example
of
an
end
user
application.
So
this
is
going
to
be
a
program
that
sits
outside
the
super
node.
F
That's
accessing
the
api
to
send
messages,
perform
token
transfers
and
all
that
good
stuff
cool
thing
here
is
so
there's
a
form
off
to
the
left-hand
side,
and
I
can
fill
out
this
form
and
it
will.
It
will
generate
the
code
snippet
that
I
would
need
to
put
in
my
application
if
I
were
building
an
application
that
needed
to
do
this
functionality,
so
here
we're
going
to
send
a
broadcast
message.
F
So
I
could
type
in
hello,
everyone
and
you
can
see
that
updates
in
real
time
over
here.
This
is
a
code
snippet
that
is
using
our
brand
new
node.js
sdk,
and
this
this
particular
example
is
in
typescript,
and
so
it's
going
to
have
nice
rich
type
information
as
well,
and
when
I
hit
run
here,
what's
going
to
happen,
is
there's
a
the
back
end.
F
Server
application
of
the
firefly
sandbox
is
going
to
make
a
request
to
firefly
to
broadcast
a
message,
so
I'm
going
to
hit
run
and
then
we'll
see.
I
immediately
get
a
response
from
the
server
and
it
is
a
type
message
and
it
has
an
id.
I
got
a
202
accepted,
so
that
means
firefly
has
accepted
the
message
and
then
it
will
send
it.
F
This
happens
to
be
a
broadcast
message,
so
it's
going
to
be
using
the
the
blockchain
to
hash
and
pin
that
message
and
it
will
be
using
ipfs
to
actually
transmit
the
the
payload
to
all
the
members
in
the
network.
So
here
I
can
see
on
the
right
hand,
side.
I
can
see
all
the
events
that
were
related
to
the
action
that
I
just
took
by
broadcasting
that
message.
So
I
can
see
there
was
a
transaction
that
was
submitted.
F
A
blockchain
event
was
received
when
we
hashed
that
message
and
pinned
it
to
the
blockchain,
and
then
I
can
also
see
that
the
other
members
of
the
network
have
confirmed
that
message
as
well.
So
if
I
hop
over
to
my
other
browsers
now,
let's
take
a
look
at
the
green
one.
I
can
refresh
the
firefly
dashboard
and
we
can
see
that
there
was
one
message
we
can
go
into
the
blockchain
dashboard.
F
We
can
see
that
there
was
a
blockchain
event
and
the
blockchain
event
just
says
that
something
was
hashed
and
it
was
pinned
to
the
blockchain.
If
we
want
to
see
the
actual
payload
of
the
message,
we
can
go
to
the
off
chain
section
and
look
at
the
data
tab,
and
here
we
can
see
there
was
a
a
message
here.
F
So
so
that's
a
broadcast,
I'm
conscious
that
we
are
running
up
on
time.
I
really
want
to
show
some
of
the
other
cool
things
like
tokens,
so
I'm
going
to
kind
of
really
quickly
just
show
you
some
of
the
things
that
are
in
the
sandbox,
I'm
not
going
to
have
time
to
do
all
of
them.
Unfortunately,
but
I
can
also
send
private
messages
here.
I
can
pick
which
recipients
I
want
to
send
the
private
message
to,
and
you
know
I
can.
I
could
just
do
this
really
fast.
F
This
is
a
message
I'm
going
to
send
this
one
from
the
green
node
only
to
the
blue
node.
So
the
red
node
should
not
see
this
message
so
we'll
send
that
I'll
hop
over
to
the
blue
node.
Look
here.
Indeed,
we
have
a
message:
I'm
going
to
go
to
the
off
chain,
tab
to
look
at
the
data
and
we
can
see
this
is
a
message
that
was
the
private
message
that
was
sent
from
green
to
blue
and
if
we
go
look
at
red,
if
we
look
at
data
red
does
not
see
that
data
at
all.
F
It
would
see
the
blockchain
event
that
something
was
pinned
to
the
blockchain,
but
this
is
you
know
one
example
of
one
of
the
ways
to
maintain
data
privacy
in
hyperledger,
firefly
and
sending
private
messages,
and
because
we
can
see
here,
the
red
node
had
no
visibility
to
the
actual
payload
of
that
message
that
was
sent
okay.
I
really
want
to
show
off
some
of
the
tokens
capabilities
because
I
think
they're
they're
really
compelling
so
firefly
has
the
concept
of
token
pools.
F
Token
pools
are
a
a
grouping
of
tokens,
whether
they're,
fungible
or
non-fungible,
and
it's
just
a
way
to
organize
things
in
here.
So
I'm
first,
I'm
going
to
create
a
fungible
token,
I'm
going
to
call
this
ffc
for
firefly
coin
and
I'm
going
to
make
the
pool
symbol
ffc
as
well,
and
we're
going
to
hit
run
so
that
will
just
create
the
token
pool
it
doesn't
create
any
tokens
yet,
but
we
can
see
that
has
been
successful.
Now,
I'm
going
to
mint
some
tokens,
let's
start
with
minting
30.
F
So,
what's
happening
is
behind
the
scenes
when
I
set
up
my
firefly
stack,
there
is
an
erc
1155,
a
contract
that
was
already
deployed
to
the
blockchain
forming
and
that's
what
we're
utilizing
here.
So
you
may
have
noticed
I
could
choose
between
fungible
or
non-fungible.
That's
that's
what
we
were
seeing
there
and
so
minted.
I
have
30
tokens.
F
F
F
And
we
could
see
that
a
token
transfer
failed
now,
so
this
this
is
great
that
we
get
this
event
in
real
time
through
the
websocket
connection
we
have
here
in
the
sandbox,
if
we
hop
over
to
the
firefly
dashboard
and
reload,
we'll
see
that
we
get
a
little
notification
up
here
in
the
corner
that
something
has
failed
all
right.
Let's
take
a
look
at
that.
F
We
can
see
that
it
was
a
token
transfer
that
failed.
We
can
click
on
that
and
get
more
details
about
it
and
scroll
down.
Look
at
the
output
and
we'll
just
expand
the
message
here
and
we
can
see
that
it
says
that
there
was
an
insufficient
balance
for
transfer,
so
I
intentionally
failed
something
here
so
that
we
could
see
what
that
would
look
like
in
the
firefly
explorer
just
to
get
a
glimpse
of
how
powerful
this
explorer
is
in
being
able
to
understand.
F
What's
going
on
inside
your
supernode,
I
also
want
to
show
off
the
the
tokens
dashboard
real
quick,
because
it's
it's
super
cool.
So
let's
go
expand
the
token
section
here,
we'll
look
at
the
dashboard,
so
we
can
see.
There's
there's
been
some
activity,
there's
been
transfers
over
here
again
we
had
one
failed
up
here
that
which
is
what
we're
expecting.
F
We
have
three
different
account
balances,
so
I
started
with
30
and
I
sent
10
to
each
of
the
other
two
members,
so
we
have
an
even
balance
across
them.
I
can
click
into
the
token
pool
and
I
can
see
all
the
details
of
that
token
pool.
I
can
see
when
transfers
have
taken
place
who
they
were
to
who
they
were
from.
You
know,
let's
mentor
or
let's
let's
burn
one
too
just
so.
We
can
see
what
that
looks
like
I'll,
just
burn
one,
I'm
going
to
reload
this
page
here
and.
F
Click
burn
come
back
to
the
dashboard,
and
now
we
can
see
that
we've
burned
one.
So
that's
also
reflected
in
our
balance
here
of
this.
The
red
members
account
only
has
nine
now
nine
firefly
coins,
so
there's
just
lots
of
really
cool
stuff.
You
could
do
all
of
this
works
with
non-fungible
tokens
as
well,
and
that
is
that's
really
cool.
I
wish
I
had
time
to
walk
you
through
every
little
detail
of
all
of
the
cool
things
that
it
can
do.
F
F
I
I
have
a
command
here,
ready
to
go
to
deploy
just
an
example
contract.
I'm
gonna
breeze
through
this
really
fast,
because
I
know
we're
running
out
of
time.
I
apologize
that
I'm
having
to
kind
of
jump
through
a
lot
of
this
really
fast
firefly,
as
steve
talked
about
earlier,
has
a
really
cool
concept
of
a
way
to
describe
a
custom.
Smart
contract
interface,
that
is,
is
actually
blockchain
agnostic.
F
It
still
encapsulates
important,
blockchain
specific
details,
but
it's
not
bound
to
any
one
particular
blockchain
implementation,
and
we
call
that
the
firefly
interface,
so
I
can
create
a
firefly
interface
by
uploading,
some
some
json
of
it.
I
can
also,
if
I
have
an
ethereum
api
for
a
smart
contract
that
I
already
have.
F
Now
that
I
have
deployed
the
contract,
I
have
told
firefly
what
the
interface
is
and
I
have
defined
an
api
at
simple
dash
storage.
I
can
click
this
button
here
and
it
just
opens
up
a
swagger
ui
that
describes
all
of
the
functions
on
that
smart
contract.
I
can
invoke
the
the
smart
contract
right
from
here.
Actually,
so
I
can
call
the
the
set
function
and
click
try
it
out.
Let's
set
it
to
42.
F
F
F
F
all
right.
There's
a
lot
more
that
I
wish
I
could
show
you.
I
wish
I
had
time
to
to
go
through
the
rest
of
it.
I
just
wanted
to
wrap
up
by
encouraging
people
to
get
involved
the
best
place
to
get
involved.
I
know
a
number
of
people
have
asked
like
hey.
How
do
I
connect
with
you?
The
best
place
by
far
is
discord.
I
am
there
every
day,
as
are
a
bunch
of
the
maintainers.
F
If
you
join
discord,
I
I
believe
that
link
should
take
you
straight
to
the
firefly
channel
and
discord,
if
not
scroll
down
on
the
left
side,
that
the
discord
server
is
for
all
of
the
hyperledger
foundation.
So
you'll
see
lots
of
projects
in
there
but
come
find
us
on
the
firefly
channel.
We
would
love
to
connect
happy
to
to
help
people
answer
questions
if
you're
curious
about
how
firefly
works
or
if
you
need
help
with
something
I
would
love
to
connect
with
you.
F
There
and
also
fireflies
open
source
go
go
download
the
code
go
play
around
with
it
open
a
pull
request,
contribute
something
we
would
love
to
to
work
with
you
and
that
that
is
it.
Thank
you
everyone.
I
really
appreciate
everyone
coming
out
today.
I'm
not
sure
who
I'm
supposed
to
hand
it
back
over
to
now.
Probably.
B
Danielle,
I
can,
I
am
going
to
see
it
now,
so
the
good
news
is
that
you
can
learn.
More
nico
will
be
doing
a
workshop
in
the
firefly
project
team
on
april
20th,
and
that
is
going
to
be
a
virtual
event
at
10
a.m.
Eastern,
so
please
sign
up
we're
going
to
put
that
link
right
in
the
chat
room.
So
please
grab
that
and
and
chat
that
and
join
us
there.
So
you
can
learn
more
you'll
have
more
time
to
to
dig
dig
in
and
answer
any
of
your
questions.
B
B
If
you
have
questions
on
twitter
and
we'll
get
to
those
as
well
multi
multi
channels,
these
links
will
be
in
the
presentation
that
will
pres
when
we
put
the
video
up
and
I'll
go
on
up
very
shortly,
so
that
you
can
access.
Thank
you
sophia
for
linking
those
into
the
chat
room
and
once
again
the
hyperledger
discord
as
nico
and
the
rest
of
them
said.
Please
do
follow
us
there
a
couple
other
things
we
do
have
some
upcoming
hyperledger
foundation,
member
webinars.
B
These
are
in-depth
webinars
with
our
member
companies
around
the
products
and
services
that
they're
building
using
hyperledger
technology,
including
intellect
eu
chain
yard
and
krypsi
in
the
upcoming
months.
So
please
do
join
us
there
and
go
to
hyperledger.org
events
to
register.
Last
but
not
least,
I
am
sure
there's
going
to
be
a
lot
of
firefly
presentations.
B
Maybe
kyle
and
patrick
will
see
you
in
dublin
as
well,
and
it
will
be
a
great
opportunity
for
us
to
meet
in
person.
The
hyperledger
global
forum
is
happening
september,
12th
to
end
and
12th
and
13th,
and
on
the
14th,
we'll
have
some
workshops
in
dublin,
ireland
and
we
are
very
excited
to
see
everybody
in
person.
B
The
call
for
presentations
is
now
open
through
april
29th,
so
please
submit
your
talks,
get
get
playing
around
and
building
stuff
with
firefly
and
submit
a
firefly
talk,
and
we
look
forward
to
seeing
you
in
dublin.
I
want
to
thank
the
panelists
once
again:
patrick
kyle,
steve
nico
and
sophia,
a
great
presentation
jam-packed.
We
look
forward
to
attending
the
webinar
and
to
reading
and
deep
diving
a
little
bit
more
about
firefly.
So
thank
you
all
for
watching
and
we
will
see
you
again
soon.